draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-14.txt   draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-15.txt 
CCAMP Working Group E. Bellagamba, Ed. CCAMP Working Group E. Bellagamba
Internet-Draft G. Mirsky, Ed. Internet-Draft A. Takacs
Intended status: Standards Track Ericsson Intended status: Standards Track G. Mirsky
Expires: June 21, 2015 L. Andersson, Ed. Expires: July 15, 2015 Ericsson
Huawei Technologies Co. L. Andersson
P. Skoldstrom, Ed. Huawei Technologies
P. Skoldstrom
Acreo AB Acreo AB
D. Ward D. Ward
Cisco Cisco
A. Takacs January 11, 2015
Ericsson
December 18, 2014
Configuration of Pro-Active Operations, Administration, and Maintenance Configuration of Pro-Active Operations, Administration, and Maintenance
(OAM) Functions for MPLS-based Transport Networks using RSVP-TE (OAM) Functions for MPLS-based Transport Networks using RSVP-TE
draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-14 draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-15
Abstract Abstract
This specification describes the configuration of pro-active MPLS-TP This specification describes the configuration of pro-active MPLS-TP
(MPLS-Transport Profile) Operations, Administration, and Maintenance (MPLS-Transport Profile) Operations, Administration, and Maintenance
(OAM) Functions for a given LSP using a set of TLVs that are carried (OAM) Functions for a given LSP using a set of TLVs that are carried
by the GMPLS RSVP-TE protocol based on the OAM Configuration by the GMPLS RSVP-TE protocol based on the OAM Configuration
Framework for GMPLS RSVP-TE. Framework for GMPLS RSVP-TE.
Status of This Memo Status of This Memo
skipping to change at page 1, line 43 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 21, 2015. This Internet-Draft will expire on July 15, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 33 skipping to change at page 2, line 33
3.1. MPLS-TP OAM Configuration Operation Overview . . . . . . 5 3.1. MPLS-TP OAM Configuration Operation Overview . . . . . . 5
3.1.1. Configuration of BFD sessions . . . . . . . . . . . . 6 3.1.1. Configuration of BFD sessions . . . . . . . . . . . . 6
3.1.2. Configuration of Performance Monitoring . . . . . . . 7 3.1.2. Configuration of Performance Monitoring . . . . . . . 7
3.1.3. Configuration of Fault Management Signals . . . . . . 7 3.1.3. Configuration of Fault Management Signals . . . . . . 7
3.2. MPLS OAM Configuration sub-TLV . . . . . . . . . . . . . 8 3.2. MPLS OAM Configuration sub-TLV . . . . . . . . . . . . . 8
3.2.1. CV Flag Rules of Use . . . . . . . . . . . . . . . . 10 3.2.1. CV Flag Rules of Use . . . . . . . . . . . . . . . . 10
3.3. BFD Configuration sub-TLV . . . . . . . . . . . . . . . . 10 3.3. BFD Configuration sub-TLV . . . . . . . . . . . . . . . . 10
3.3.1. BFD Identifiers sub-TLV . . . . . . . . . . . . . . . 12 3.3.1. BFD Identifiers sub-TLV . . . . . . . . . . . . . . . 12
3.3.2. Negotiation Timer Parameters sub-TLV . . . . . . . . 13 3.3.2. Negotiation Timer Parameters sub-TLV . . . . . . . . 13
3.3.3. BFD Authentication sub-TLV . . . . . . . . . . . . . 14 3.3.3. BFD Authentication sub-TLV . . . . . . . . . . . . . 14
3.4. Performance Monitoring sub-TLV . . . . . . . . . . . . . 15 3.3.4. Traffic Class sub-TLV . . . . . . . . . . . . . . . . 15
3.4.1. MPLS OAM PM Loss sub-TLV . . . . . . . . . . . . . . 16 3.4. Performance Monitoring sub-TLV . . . . . . . . . . . . . 16
3.4.2. MPLS OAM PM Delay sub-TLV . . . . . . . . . . . . . . 18 3.4.1. MPLS OAM PM Loss sub-TLV . . . . . . . . . . . . . . 17
3.5. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . . 19 3.4.2. MPLS OAM PM Delay sub-TLV . . . . . . . . . . . . . . 19
4. Summary of MPLS OAM configuration errors . . . . . . . . . . 20 3.5. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . . 20
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 4. Summary of MPLS OAM configuration errors . . . . . . . . . . 21
5.1. MPLS OAM Type . . . . . . . . . . . . . . . . . . . . . . 21 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
5.2. MPLS OAM Configuration sub-TLV . . . . . . . . . . . . . 22 5.1. MPLS OAM Type . . . . . . . . . . . . . . . . . . . . . . 22
5.3. MPLS OAM Configuration Sub-TLV Types . . . . . . . . . . 22 5.2. MPLS OAM Configuration sub-TLV . . . . . . . . . . . . . 23
5.4. BFD Configuration Sub-TLV Types . . . . . . . . . . . . . 22 5.3. MPLS OAM Configuration Sub-TLV Types . . . . . . . . . . 23
5.5. Performance Monitoring sub-TLV Types . . . . . . . . . . 23 5.4. BFD Configuration Sub-TLV Types . . . . . . . . . . . . . 24
5.6. New RSVP-TE error codes . . . . . . . . . . . . . . . . . 23 5.5. Performance Monitoring sub-TLV Types . . . . . . . . . . 24
6. Contributing Authors . . . . . . . . . . . . . . . . . . . . 24 5.6. New RSVP-TE error codes . . . . . . . . . . . . . . . . . 25
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24 6. Contributing Authors . . . . . . . . . . . . . . . . . . . . 25
8. Security Considerations . . . . . . . . . . . . . . . . . . . 24 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 8. Security Considerations . . . . . . . . . . . . . . . . . . . 26
9.1. Normative References . . . . . . . . . . . . . . . . . . 25 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 26
9.2. Informative References . . . . . . . . . . . . . . . . . 26 9.1. Normative References . . . . . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 9.2. Informative References . . . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27
1. Introduction 1. Introduction
This document describes the configuration of pro-active MPLS-TP This document describes the configuration of pro-active MPLS-TP
(MPLS-Transport Profile) Operations, Administration, and Maintenance (MPLS-Transport Profile) Operations, Administration, and Maintenance
(OAM) Functions for a given LSP using TLVs using GMPLS RSVP-TE (OAM) Functions for a given LSP using TLVs using GMPLS RSVP-TE
[RFC3473]. The use of GMPLS RSVP-TE for the configuration of OAM [RFC3473]. The use of GMPLS RSVP-TE for the configuration of OAM
functions is defined in a technology agnostic way in [RFC7260]. This functions is defined in a technology agnostic way in [RFC7260]. This
document specifies the additional mechanisms necessary to establish document specifies the additional mechanisms necessary to establish
MPLS-TP OAM entities at the maintenance points for monitoring and MPLS-TP OAM entities at the maintenance points for monitoring and
skipping to change at page 4, line 43 skipping to change at page 4, line 43
GMPLS - Generalized Multi-Protocol Label Switching GMPLS - Generalized Multi-Protocol Label Switching
LER - Label switching Edge Router LER - Label switching Edge Router
LM - Loss Measurement LM - Loss Measurement
LSP - Label Switched Path LSP - Label Switched Path
LSR - Label Switching Router LSR - Label Switching Router
MEP - Maintanence Entity Group End Point MEP - Maintenance Entity Group End Point
MPLS - Multi-Protocol Label Switching MPLS - Multi-Protocol Label Switching
MPLS-TP - MPLS Transport Profile MPLS-TP - MPLS Transport Profile
NMS - Network Management System NMS - Network Management System
PM - Performance Measurement PM - Performance Measurement
RSVP-TE - Reservation Protocol Traffic Engineering RSVP-TE - Reservation Protocol Traffic Engineering
TC - Traffic Class
1.1.2. Requirements Language 1.1.2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. Overview of MPLS OAM for Transport Applications 2. Overview of MPLS OAM for Transport Applications
[RFC6371] describes how MPLS-TP OAM mechanisms are operated to meet [RFC6371] describes how MPLS-TP OAM mechanisms are operated to meet
transport requirements outlined in [RFC5860]. transport requirements outlined in [RFC5860].
skipping to change at page 6, line 13 skipping to change at page 6, line 15
For a more detailed configuration one may include sub-TLVs for the For a more detailed configuration one may include sub-TLVs for the
different OAM functions in order to specify various parameters in different OAM functions in order to specify various parameters in
detail. detail.
Typically intermediate nodes should not process or modify any of the Typically intermediate nodes should not process or modify any of the
OAM configuration TLVs but simply forward them to the end-node. OAM configuration TLVs but simply forward them to the end-node.
There is one exception to this and that is if the "MPLS OAM FMS sub- There is one exception to this and that is if the "MPLS OAM FMS sub-
TLV" is present. This sub-TLV has to be examined even by TLV" is present. This sub-TLV has to be examined even by
intermediate nodes, but only acted upon by nodes capable of intermediate nodes, but only acted upon by nodes capable of
transmitting FMS signals into the LSP being established. The sub-TLV transmitting FMS signals into the LSP being established. The sub-TLV
MAY be present the FMS flag is set in the "OAM Function Flags sub- MAY be present when the FMS flag is set in the "OAM Function Flags
TLV". If this sub-TLV is present the "OAM MIP entities desired" and sub-TLV". If this sub-TLV is present, then the "OAM MIP entities
"OAM MEP entities desired" flags (described in [RFC7260]) in the "LSP desired" and "OAM MEP entities desired" flags (described in
Attributes Flags TLV" MUST be set and the entire OAM Configuration [RFC7260]) in the "LSP Attributes Flags TLV" MUST be set and the
TLV placed either in the LSP_REQUIRED_ATTRIBUTES object or in the entire OAM Configuration TLV placed either in the
LSP_ATTRIBUTES object ensure that capable intermediate nodes process LSP_REQUIRED_ATTRIBUTES object or in the LSP_ATTRIBUTES object in
the configuration. If placed in LSP_ATTRIBUTES nodes that are not order to ensure that capable intermediate nodes process the
able to process the OAM Configuration TLV will forward the message configuration. If placed in LSP_ATTRIBUTES object, nodes that are
without generating an error, this is not the case if placed in the not able to process the OAM Configuration TLV will forward the
LSP_REQUIRED_ATTRIBUTES object. message without generating an error. If the ?MPLS OAM FMS sub-TLV?
been placed in the LSP_REQUIRED_ATTRIBUTES object a node that
supports the RFC 7260 but does not support the "MPLS OAM FMS sub-TLV"
MUST generate PathErr message with "OAM Problem/Configuration Error"
[RFC7260]. Otherwise, if the node doesn't support the RFC 7260, it
will not raise any errors as described in the Section 4.1 [RFC7260].
Finally, if the "MPLS OAM FMS sub-TLV" is not included only the "OAM Finally, if the "MPLS OAM FMS sub-TLV" is not included only the "OAM
MEP entities desired" flag is set and the OAM Configuration TLV may MEP entities desired" flag is set and the OAM Configuration TLV may
be placed in either LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES. be placed in either LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES.
3.1.1. Configuration of BFD sessions 3.1.1. Configuration of BFD sessions
For this specification, BFD MUST be run in either one of the two For this specification, BFD MUST be run in either one of the two
modes: modes:
skipping to change at page 7, line 46 skipping to change at page 8, line 4
"OAM Function Flags sub-TLV", and by including the "MPLS OAM PM Loss "OAM Function Flags sub-TLV", and by including the "MPLS OAM PM Loss
sub-TLV", one can configure the measurement interval and the delay sub-TLV", one can configure the measurement interval and the delay
threshold values for triggering protection. threshold values for triggering protection.
3.1.3. Configuration of Fault Management Signals 3.1.3. Configuration of Fault Management Signals
To configure Fault Management Signals and their refresh time, the FMS To configure Fault Management Signals and their refresh time, the FMS
flag in the "OAM Function Flags sub-TLV" MUST be set and the "MPLS flag in the "OAM Function Flags sub-TLV" MUST be set and the "MPLS
OAM FMS sub-TLV" included. When configuring Fault Management OAM FMS sub-TLV" included. When configuring Fault Management
Signals, an implementation can enable the default configuration by Signals, an implementation can enable the default configuration by
setting the FMS flag in the "OAM Function Flags sub-TLV". If an setting the FMS flag in the "OAM Function Flags sub-TLV". In order
implementation wishes to modify the default configuration it includes to modify the default configuration the "MPLS OAM FMS sub-TLV" MUST
a "MPLS OAM FMS sub-TLV". be included.
If an intermediate point is intended to originate fault management If an intermediate point is intended to originate fault management
signal messages, this means that such an intermediate point is signal messages, this means that such an intermediate point is
associated to a server MEP through a co-located MPLS-TP client/server associated with a server MEP through a co-located MPLS-TP client/
adaptation function. Such a server MEP needs to be configured by its server adaptation function and the ?Fault Management subscription?
flag in the ?MPLS OAM FMS sub-TLV? been set as indication of the
request to create the association at each intermediate node of the
client LSP. Corresponding server MEP needs to be configured by its
own RSVP-TE session (or, alternatively, via an NMS or LSP-ping). own RSVP-TE session (or, alternatively, via an NMS or LSP-ping).
However, by setting the "Fault Management subscription" flag in the
"MPLS OAM FMS sub-TLV", a client LSP can indicate that it would like
an association to be created to the server MEP(s) on any intermediate
nodes.
3.2. MPLS OAM Configuration sub-TLV 3.2. MPLS OAM Configuration sub-TLV
The "OAM Configuration TLV", defined in [RFC7260], specifies the OAM The "OAM Configuration TLV", defined in [RFC7260], specifies the OAM
functions that are used for the LSP. This document extends the "OAM functions that are used for the LSP. This document extends the "OAM
Configuration TLV" by defining a new OAM Type: "MPLS OAM" (TBA1). Configuration TLV" by defining a new OAM Type: "MPLS OAM" (TBA1).
The "MPLS OAM" type is set to request the establishment of OAM The "MPLS OAM" type is set to request the establishment of OAM
functions for MPLS-TP LSPs. The specific OAM functions are specified functions for MPLS-TP LSPs. The specific OAM functions are specified
in the "OAM Function Flags sub-TLV" as depicted in [RFC7260]. in the "OAM Function Flags sub-TLV" as depicted in [RFC7260].
skipping to change at page 9, line 38 skipping to change at page 9, line 44
OAM Function flag is set. If the "MPLS OAM PM Delay sub-TLV" OAM Function flag is set. If the "MPLS OAM PM Delay sub-TLV"
is not included, default configuration values are used. is not included, default configuration values are used.
- "MPLS OAM FMS sub-TLV" MAY be included if the FMS OAM Function - "MPLS OAM FMS sub-TLV" MAY be included if the FMS OAM Function
flag is set. If the "MPLS OAM FMS sub-TLV" is not included, flag is set. If the "MPLS OAM FMS sub-TLV" is not included,
default configuration values are used. default configuration values are used.
Following are some additional rules of processing MPLS OAM Following are some additional rules of processing MPLS OAM
Configuration sub-TLV: Configuration sub-TLV:
- MPLS OAM Configuration sub-TLV? MAY be empty, i.e. have no - MPLS OAM Configuration sub-TLV MAY be empty, i.e. have no Value.
Value. Then its Length MUST be 8. Then all OAM functions that Then its Length MUST be 8. Then all OAM functions that have their
have their corresponding flags set in the ?OAM Function Flags sub- corresponding flags set in the "OAM Function Flags sub-TLV" MUST
TLV? MUST be assigned their default values or left disabled. be assigned their default values or left disabled.
- sub-TLV that doesn't have corresponding flag set MUST be - sub-TLV that doesn't have corresponding flag set MUST be
silently ignored; silently ignored;
- if multiple copies of a sub-TLV are present, then only the first - if multiple copies of a sub-TLV are present, then only the first
sub-TLV MUST be used and the remaining sub-TLVs MUST be silently sub-TLV MUST be used and the remaining sub-TLVs MUST be silently
ignored. ignored.
However, not all the values can be derived from the standard RSVP-TE However, not all the values can be derived from the standard RSVP-TE
objects, in particular the locally assigned Tunnel ID at the egress objects, in particular the locally assigned Tunnel ID at the egress
cannot be derived by the ingress node. Therefore, the full LSP MEP- cannot be derived by the ingress node. Therefore, the full LSP MEP-
ID used by the ingress has to be carried in the "BFD Identifiers sub- ID used by the ingress has to be carried in the "BFD Identifiers sub-
TLV" in the Path message and the egress LSP MEP-ID in the same way in TLV" in the Path message and the egress LSP MEP-ID in the same way in
the Resv message. the Resv message.
skipping to change at page 10, line 10 skipping to change at page 10, line 17
However, not all the values can be derived from the standard RSVP-TE However, not all the values can be derived from the standard RSVP-TE
objects, in particular the locally assigned Tunnel ID at the egress objects, in particular the locally assigned Tunnel ID at the egress
cannot be derived by the ingress node. Therefore, the full LSP MEP- cannot be derived by the ingress node. Therefore, the full LSP MEP-
ID used by the ingress has to be carried in the "BFD Identifiers sub- ID used by the ingress has to be carried in the "BFD Identifiers sub-
TLV" in the Path message and the egress LSP MEP-ID in the same way in TLV" in the Path message and the egress LSP MEP-ID in the same way in
the Resv message. the Resv message.
3.2.1. CV Flag Rules of Use 3.2.1. CV Flag Rules of Use
Moreover, if the CV flag is set, the CC flag MUST be set as well as If the CV flag is set, then the CC flag MUST be set as well because
performing Connectivity Verification implies performing Continuity performing Connectivity Verification implies performing Continuity
Check. The format of an MPLS-TP CV/CC message is shown in [RFC6428] Check as well. The format of an MPLS-TP CV/CC message is shown in
and it requires, together with the BFD Control packet information, [RFC6428]. In order to perform Connectivity Verification the CV/CC
the "LSP MEP-ID". The "LSP MEP-ID" contain four identifiers: message MUST contain the ?LSP MEP-ID? in addition to the BFD Control
packet information. The "LSP MEP-ID" contains four identifiers:
MPLS-TP Global_ID MPLS-TP Global_ID
MPLS-TP Node Identifier MPLS-TP Node Identifier
Tunnel_Num Tunnel_Num
LSP_Num LSP_Num
These values need to be correctly set by both ingress and egress when These values need to be correctly set by both ingress and egress when
transmitting a CV packet and both ingress and egress needs to know transmitting a CV packet and both ingress and egress needs to know
what to expect when receving a CV packet. Most of these values can what to expect when receiving a CV packet. Most of these values can
be derived from the Path and Resv messages [RFC3473], which uses a be derived from the Path and Resv messages [RFC3473], which uses a
5-tuple to uniquely identify an LSP within an operator's network. 5-tuple to uniquely identify an LSP within an operator's network.
This tuple is composed of a Tunnel Sender Address, Tunnel Endpoint This tuple is composed of a Tunnel Sender Address, Tunnel Endpoint
Address, Tunnel_ID, Extended Tunnel ID, and (GMPLS) LSP_ID. Address, Tunnel_ID, Extended Tunnel ID, and (GMPLS) LSP_ID.
3.3. BFD Configuration sub-TLV 3.3. BFD Configuration sub-TLV
The "BFD Configuration sub-TLV" (depicted below) is defined for BFD The "BFD Configuration sub-TLV" (depicted below) is defined for BFD
OAM specific configuration parameters. The "BFD Configuration sub- OAM specific configuration parameters. The "BFD Configuration sub-
TLV" is carried as a sub-TLV of the "MPLS OAM Configuration sub-TLV". TLV" is carried as a sub-TLV of the "MPLS OAM Configuration sub-TLV".
This TLV accommodates generic BFD OAM information and carries sub- This TLV accommodates generic BFD OAM information and carries sub-
TLVs. TLVs.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BFD Conf. Type (1) | Length | | BFD Conf. Type (1) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Vers.| PHB |N|S|I|G|U|B| Reserved (set to all 0s) | |Vers.|N|S|I|G|U|B| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ sub-TLVs ~ ~ sub-TLVs ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1, the "BFD Configuration sub-TLV". Type: 1, the "BFD Configuration sub-TLV".
Length: indicates the total length in octets, including sub-TLVs as Length: indicates the total length in octets, including sub-TLVs as
well as the Type and Length fields. well as the Type and Length fields.
Version: identifies the BFD protocol version. If the egress LSR does Version: identifies the BFD protocol version. If the egress LSR does
not support the version an error MUST be generated: "OAM Problem/ not support the version an error MUST be generated: "OAM Problem/
Unsupported BFD Version". Unsupported BFD Version".
PHB: Identifies the Per-Hop Behavior (PHB) to be used for periodic
continuity monitoring messages.
BFD Negotiation (N): If set timer negotiation/re-negotiation via BFD BFD Negotiation (N): If set timer negotiation/re-negotiation via BFD
Control Messages is enabled, when cleared it is disabled. Control Messages is enabled, when cleared it is disabled.
Symmetric session (S): If set the BFD session MUST use symmetric Symmetric session (S): If set the BFD session MUST use symmetric
timing values. timing values.
Integrity (I): If set BFD Authentication MUST be enabled. If the Integrity (I): If set BFD Authentication MUST be enabled. If the
"BFD Configuration sub-TLV" does not include a "BFD Authentication "BFD Configuration sub-TLV" does not include a "BFD Authentication
sub-TLV" the authentication MUST use Keyed SHA1 with an empty pre- sub-TLV" the authentication MUST use Keyed SHA1 with an empty pre-
shared key (all 0s). If the egress LSR does not support BFD shared key (all 0s). If the egress LSR does not support BFD
skipping to change at page 13, line 39 skipping to change at page 14, line 12
Type: 2, "Negotiation Timer Parameters sub-TLV". Type: 2, "Negotiation Timer Parameters sub-TLV".
Length: indicates the TLV total length in octets, including Type and Length: indicates the TLV total length in octets, including Type and
Length fields (16). Length fields (16).
Acceptable Min. Asynchronous TX interval: If the S (symmetric) flag Acceptable Min. Asynchronous TX interval: If the S (symmetric) flag
is set in the "BFD Configuration sub-TLV", it expresses the desired is set in the "BFD Configuration sub-TLV", it expresses the desired
time interval (in microseconds) at which the ingress LER intends to time interval (in microseconds) at which the ingress LER intends to
both transmit and receive BFD periodic control packets. If the both transmit and receive BFD periodic control packets. If the
egress LSR can not support the value, it SHOULD reply with a egress LSR cannot support the value, it SHOULD reply with a supported
supported interval. interval.
If the S (symmetric) flag is cleared in the "BFD Configuration sub- If the S (symmetric) flag is cleared in the "BFD Configuration sub-
TLV", this field expresses the desired time interval (in TLV", this field expresses the desired time interval (in
microseconds) at which the ingress LSR intends to transmit BFD microseconds) at which the ingress LSR intends to transmit BFD
periodic control packets. periodic control packets.
Acceptable Min. Asynchronous RX interval: If the S (symmetric) flag Acceptable Min. Asynchronous RX interval: If the S (symmetric) flag
is set in the "BFD Configuration sub-TLV", this field MUST be set is set in the "BFD Configuration sub-TLV", this field MUST be set
equal to "Acceptable Min. Asynchronous TX interval" on transmit and equal to "Acceptable Min. Asynchronous TX interval" on transmit and
MUST be ignored on receipt since it has no additional meaning with MUST be ignored on receipt since it has no additional meaning with
skipping to change at page 14, line 48 skipping to change at page 15, line 25
Length: indicates the TLV total length in octets, including Type and Length: indicates the TLV total length in octets, including Type and
Length fields (8). Length fields (8).
Auth Type: indicates which type of authentication to use. The same Auth Type: indicates which type of authentication to use. The same
values as are defined in section 4.1 of [RFC5880] are used. If the values as are defined in section 4.1 of [RFC5880] are used. If the
egress LSR does not support this type an "OAM Problem/Unsupported BFD egress LSR does not support this type an "OAM Problem/Unsupported BFD
Authentication Type" error MUST be generated. Authentication Type" error MUST be generated.
Auth Key ID: indicates which authentication key or password Auth Key ID: indicates which authentication key or password
(depending on Auth Type) should be used. How the key exchange is (depending on Auth Type) should be used. How the key exchange is
performed is out of scope of this document.If the egress LSR does not performed is out of scope of this document. If the egress LSR does
support this Auth Key ID an "OAM Problem/Mismatch of BFD not support this Auth Key ID an "OAM Problem/Mismatch of BFD
Authentication Key ID" error MUST be generated. Authentication Key ID" error MUST be generated.
Reserved: Reserved for future specification and set to 0 on Reserved: Reserved for future specification and set to 0 on
transmission and ignored when received. transmission and ignored when received.
3.3.4. Traffic Class sub-TLV
The Traffic Class sub-TLV is carried as a sub-TLV of the "BFD
Configuration sub-TLV" or "Fault Management Signal sub-TLV"
Section 3.5 and is depicted in Figure 1.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Class sub-Type (4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TC | Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Traffic Class sub-TLV format
Type: 3, "Traffic Class sub-TLV".
Length: indicates the length of the Value field in octets . (4)
TC: Identifies the Traffic Class (TC) [RFC5462] for periodic
continuity monitoring messages or packets with fault management
information.
If TC sub-TLV is present, then the value of the TC field MUST be used
as the value of the TC field of an MPLS label stack entry. If the TC
sub-TLV is absent from "BFD Configuration sub-TLV" or "Fault
Management Signal sub-TLV", then selection of the TC value is local
decision.
3.4. Performance Monitoring sub-TLV 3.4. Performance Monitoring sub-TLV
If the "OAM Function Flags sub-TLV" has either the PM/Loss, PM/Delay If the "OAM Function Flags sub-TLV" has either the PM/Loss, PM/Delay
or PM/Throughput flag set, the "Performance Monitoring sub-TLV" MUST or PM/Throughput flag set, the "Performance Monitoring sub-TLV" MUST
be present in the "MPLS OAM Configuration sub-TLV". Failure to be present in the "MPLS OAM Configuration sub-TLV". Failure to
include the correct sub-TLVs MUST result in an "OAM Problem/ include the correct sub-TLVs MUST result in an "OAM Problem/
Configuration Error" error being generated. Configuration Error" error being generated.
The "Performance Monitoring sub-TLV" provides the configuration The "Performance Monitoring sub-TLV" provides the configuration
information mentioned in Section 7 of [RFC6374]. It includes support information mentioned in Section 7 of [RFC6374]. It includes support
skipping to change at page 19, line 33 skipping to change at page 20, line 33
The "MPLS OAM FMS sub-TLV" depicted below is carried as a sub-TLV of The "MPLS OAM FMS sub-TLV" depicted below is carried as a sub-TLV of
the "MPLS OAM Configuration sub-TLV". When both working and the "MPLS OAM Configuration sub-TLV". When both working and
protection paths are signaled, both LSPs SHOULD be signaled with protection paths are signaled, both LSPs SHOULD be signaled with
identical settings of the E flag, T flag, and the refresh timer. identical settings of the E flag, T flag, and the refresh timer.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MPLS OAM FMS Type (3) | Length | | MPLS OAM FMS Type (3) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E|S|T| Reserved (set to all 0s)| Refresh Timer | PHB | |E|S|T| Reserved | Refresh Timer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ sub-TLVs ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 3, "MPLS OAM FMS sub-TLV". Type: 3, "MPLS OAM FMS sub-TLV".
Length: indicates the TLV total length in octets, including Type and Length: indicates the TLV total length in octets, including Type and
Length fields (8). Length fields (8).
FMS Signal Flags are used to enable the FMS signals at end point MEPs FMS Signal Flags are used to enable the FMS signals at end point MEPs
and the Server MEPs of the links over which the LSP is forwarded. In and the Server MEPs of the links over which the LSP is forwarded. In
this document only the S flag pertains to Server MEPs. this document only the S flag pertains to Server MEPs.
The following flags are defined: The following flags are defined:
- E: Enable Alarm Indication Signal (AIS) and Lock Report (LKR) - E: Enable Alarm Indication Signal (AIS) and Lock Report (LKR)
signalling as described in [RFC6427]. Default value is 1 signaling as described in [RFC6427]. Default value is 1
(enabled). If the egress MEP does not support FMS signal (enabled). If the egress MEP does not support FMS signal
generation an "OAM Problem/Fault management signaling unsupported" generation an "OAM Problem/Fault management signaling unsupported"
error MUST be generated. error MUST be generated.
- S: Indicate to a Server MEP that its should transmit AIS and LKR - S: Indicate to a Server MEP that it should transmit AIS and LKR
signals on client LSPs. Default value is 0 (disabled). If a signals on client LSPs. Default value is 0 (disabled). If a
Server MEP which is capable of generating FMS messages is for some Server MEP which is capable of generating FMS messages is for some
reason unable to do so for the LSP being signalled an "OAM reason unable to do so for the LSP being signaled an "OAM Problem/
Problem/Unable to create fault management association" error MUST Unable to create fault management association" error MUST be
be generated. generated.
- T: Set timer value, enabled the configuration of a specific - T: Set timer value, enabled the configuration of a specific
timer value. Default value is 0 (disabled). timer value. Default value is 0 (disabled).
- Remaining bits: Reserved for future specification and set to 0. - Remaining bits: Reserved for future specification and set to 0.
Refresh Timer: indicates the refresh timer of fault indication Refresh Timer: indicates the refresh timer of fault indication
messages, in seconds. The value MUST be between 1 to 20 seconds as messages, in seconds. The value MUST be between 1 to 20 seconds as
specified for the Refresh Timer field in [RFC6427]. If the egress specified for the Refresh Timer field in [RFC6427]. If the egress
LSR cannot support the value it SHOULD reply with a supported timer LSR cannot support the value it SHOULD reply with a supported timer
value. value.
PHB: identifies the per-hop behavior of packets with fault management FMS sub-TLV MAY include Traffic Class sub-TLV Section 3.3.4. If TC
information. sub-TLV is present, the value of the TC field MUST be used as the
value of the TC field of an MPLS label stack entry for FMS messages.
If the TC sub-TLV is absent, then selection of the TC value is local
decision.
4. Summary of MPLS OAM configuration errors 4. Summary of MPLS OAM configuration errors
In addition to error values specified in [RFC7260] this document In addition to error values specified in [RFC7260] this document
defines the following values for the "OAM Problem" Error Code: defines the following values for the "OAM Problem" Error Code:
- If an egress LSR does not support the specified BFD version, an - If an egress LSR does not support the specified BFD version, an
error MUST be generated: "OAM Problem/Unsupported BFD Version". error MUST be generated: "OAM Problem/Unsupported BFD Version".
- If an egress LSR does not support the specified BFD - If an egress LSR does not support the specified BFD
skipping to change at page 23, line 13 skipping to change at page 24, line 22
following types: following types:
+-------------+-------------------------------------+---------------+ +-------------+-------------------------------------+---------------+
| Type | Description | Reference | | Type | Description | Reference |
+-------------+-------------------------------------+---------------+ +-------------+-------------------------------------+---------------+
| 0 | Reserved | This document | | 0 | Reserved | This document |
| 1 | BFD Identifiers sub-TLV | This document | | 1 | BFD Identifiers sub-TLV | This document |
| 2 | Negotiation Timer Parameters sub- | This document | | 2 | Negotiation Timer Parameters sub- | This document |
| | TLV | | | | TLV | |
| 3 | BFD Authentication sub-TLV | This document | | 3 | BFD Authentication sub-TLV | This document |
| 4-65532 | Unassigned | | | 4 | Traffic Class sub-TLV | This document |
| 5-65532 | Unassigned | |
| 65533-65534 | Reserved for Experimental Use | This document | | 65533-65534 | Reserved for Experimental Use | This document |
| 65535 | Reserved | This document | | 65535 | Reserved | This document |
+-------------+-------------------------------------+---------------+ +-------------+-------------------------------------+---------------+
Table 4: BFD Configuration Sus-TLV Types Table 4: BFD Configuration Sus-TLV Types
5.5. Performance Monitoring sub-TLV Types 5.5. Performance Monitoring sub-TLV Types
IANA is requested to create a "Performance Monitoring sub-TLV Type" IANA is requested to create a "Performance Monitoring sub-TLV Type"
sub-registry in the "RSVP-TE OAM Configuration Registry" for the sub- sub-registry in the "RSVP-TE OAM Configuration Registry" for the sub-
skipping to change at page 23, line 45 skipping to change at page 25, line 8
| 3-65532 | Unassigned | | | 3-65532 | Unassigned | |
| 65533-65534 | Reserved for Experimental Use | This document | | 65533-65534 | Reserved for Experimental Use | This document |
| 65535 | Reserved | This document | | 65535 | Reserved | This document |
+-------------+-------------------------------+---------------+ +-------------+-------------------------------+---------------+
Table 5: Performance Monitoring sub-TLV Types Table 5: Performance Monitoring sub-TLV Types
5.6. New RSVP-TE error codes 5.6. New RSVP-TE error codes
The following values need to be assigned under the "OAM Problem" The following values need to be assigned under the "OAM Problem"
Error Code [RFC7260 by IETF Review process: Error Code [RFC7260] by IETF Review process:
+-----------------+---------------------------------+---------------+ +-----------------+---------------------------------+---------------+
| Error Value | Description | Reference | | Error Value | Description | Reference |
| Sub-codes | | | | Sub-codes | | |
+-----------------+---------------------------------+---------------+ +-----------------+---------------------------------+---------------+
| TBA3 | Unsupported BFD Version | This document | | TBA3 | Unsupported BFD Version | This document |
| TBA4 | Unsupported BFD Encapsulation | This document | | TBA4 | Unsupported BFD Encapsulation | This document |
| | format | | | | format | |
| TBA5 | Unsupported BFD Authentication | This document | | TBA5 | Unsupported BFD Authentication | This document |
| | Type | | | | Type | |
skipping to change at page 24, line 31 skipping to change at page 25, line 36
| TBA12 | Loopback mode unsupported | This document | | TBA12 | Loopback mode unsupported | This document |
| TBA13 | Combined mode unsupported | This document | | TBA13 | Combined mode unsupported | This document |
| TBA14 | Fault management signaling | This document | | TBA14 | Fault management signaling | This document |
| | unsupported | | | | unsupported | |
| TBA15 | Unable to create fault | This document | | TBA15 | Unable to create fault | This document |
| | management association | | | | management association | |
+-----------------+---------------------------------+---------------+ +-----------------+---------------------------------+---------------+
Table 6: MPLS OAM Configuration Error Codes Table 6: MPLS OAM Configuration Error Codes
The "Sub-codes - 40, OAM Problem" sub-registry is located in the
"Error Codes and Globally-Defined Error Value Sub-Codes" registry.
6. Contributing Authors 6. Contributing Authors
This document is the result of a large team of authors and This document is the result of a large team of authors and
contributors. The following is a list of the co-authors: contributors. The following is a list of the co-authors:
John Drake John Drake
Benoit Tremblay Benoit Tremblay
7. Acknowledgements 7. Acknowledgements
skipping to change at page 26, line 23 skipping to change at page 27, line 28
9.2. Informative References 9.2. Informative References
[LSP-PING-CONF] [LSP-PING-CONF]
Bellagamba, E., Andersson, L., Ward, D., Drake, J., and P. Bellagamba, E., Andersson, L., Ward, D., Drake, J., and P.
Skoldstrom, "Configuration of pro-active MPLS-TP Skoldstrom, "Configuration of pro-active MPLS-TP
Operations, Administration, and Maintenance (OAM) Operations, Administration, and Maintenance (OAM)
Functions Using LSP Ping", 2014, <draft-ietf-mpls-lsp- Functions Using LSP Ping", 2014, <draft-ietf-mpls-lsp-
ping-mpls-tp-oam-conf>. ping-mpls-tp-oam-conf>.
[RFC5462] Andersson, L. and R. Asati, "Multiprotocol Label Switching
(MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic
Class" Field", RFC 5462, February 2009.
[RFC6371] Busi, I. and D. Allan, "Operations, Administration, and [RFC6371] Busi, I. and D. Allan, "Operations, Administration, and
Maintenance Framework for MPLS-Based Transport Networks", Maintenance Framework for MPLS-Based Transport Networks",
RFC 6371, September 2011. RFC 6371, September 2011.
[RFC6375] Frost, D. and S. Bryant, "A Packet Loss and Delay [RFC6375] Frost, D. and S. Bryant, "A Packet Loss and Delay
Measurement Profile for MPLS-Based Transport Networks", Measurement Profile for MPLS-Based Transport Networks",
RFC 6375, September 2011. RFC 6375, September 2011.
Authors' Addresses Authors' Addresses
Elisa Bellagamba (editor) Elisa Bellagamba
Ericsson Ericsson
Email: elisa.bellagamba@ericsson.com Email: elisa.bellagamba@ericsson.com
Gregory Mirsky (editor) Attila Takacs
Ericsson
Email: attila.takacs@ericsson.com
Gregory Mirsky
Ericsson Ericsson
Email: Gregory.Mirsky@ericsson.com Email: Gregory.Mirsky@ericsson.com
Loa Andersson (editor) Loa Andersson
Huawei Technologies Co. Huawei Technologies
Email: loa@mail01.huawei.com Email: loa@mail01.huawei.com
Pontus Skoldstrom (editor)
Pontus Skoldstrom
Acreo AB Acreo AB
Electrum 236 Electrum 236
Kista 164 40 Kista 164 40
Sweden Sweden
Phone: +46 70 7957731 Phone: +46 70 7957731
Email: pontus.skoldstrom@acreo.se Email: pontus.skoldstrom@acreo.se
Dave Ward Dave Ward
Cisco Cisco
Email: dward@cisco.com Email: dward@cisco.com
Attila Takacs
Ericsson
Email: attila.takacs@ericsson.com
 End of changes. 37 change blocks. 
84 lines changed or deleted 137 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/