draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-16.txt   rfc7487.txt 
CCAMP Working Group E. Bellagamba Internet Engineering Task Force (IETF) E. Bellagamba
Internet-Draft A. Takacs Request for Comments: 7487 A. Takacs
Intended status: Standards Track G. Mirsky Category: Standards Track G. Mirsky
Expires: July 28, 2015 Ericsson ISSN: 2070-1721 Ericsson
L. Andersson L. Andersson
Huawei Technologies Huawei Technologies
P. Skoldstrom P. Skoldstrom
Acreo AB Acreo AB
D. Ward D. Ward
Cisco Cisco
January 24, 2015 March 2015
Configuration of Pro-Active Operations, Administration, and Maintenance Configuration of
(OAM) Functions for MPLS-based Transport Networks using RSVP-TE Proactive Operations, Administration, and Maintenance (OAM) Functions
draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-16 for MPLS-Based Transport Networks Using RSVP-TE
Abstract Abstract
This specification describes the configuration of proactive MPLS-TP This specification describes the configuration of proactive MPLS
(MPLS-Transport Profile) Operations, Administration, and Maintenance Transport Profile (MPLS-TP) Operations, Administration, and
(OAM) Functions for a given LSP using a set of TLVs that are carried Maintenance (OAM) functions for a given Label Switched Path (LSP)
by the GMPLS RSVP-TE protocol based on the OAM Configuration using a set of TLVs that are carried by the GMPLS RSVP-TE protocol
Framework for GMPLS RSVP-TE. based on the OAM Configuration Framework for GMPLS RSVP-TE.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on July 28, 2015. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7487.
Copyright Notice Copyright Notice
Copyright (c) 2015 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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................4
1.1. Conventions used in this document . . . . . . . . . . . . 4 1.1. Conventions Used in This Document ..........................5
1.1.1. Terminology . . . . . . . . . . . . . . . . . . . . . 4 1.1.1. Terminology .........................................5
1.1.2. Requirements Language . . . . . . . . . . . . . . . . 5 1.1.2. Requirements Language ...............................6
2. Overview of MPLS OAM for Transport Applications . . . . . . . 5 2. Overview of MPLS OAM for Transport Applications .................6
3. Theory of Operations . . . . . . . . . . . . . . . . . . . . 5 3. Theory of Operations ............................................7
3.1. MPLS-TP OAM Configuration Operation Overview . . . . . . 5 3.1. MPLS-TP OAM Configuration Operation Overview ...............7
3.1.1. Configuration of BFD sessions . . . . . . . . . . . . 6 3.1.1. Configuration of BFD Sessions .......................8
3.1.2. Configuration of Performance Monitoring . . . . . . . 7 3.1.2. Configuration of Performance Monitoring .............8
3.1.3. Configuration of Fault Management Signals . . . . . . 7 3.1.3. Configuration of Fault Management Signals ...........9
3.2. MPLS OAM Configuration sub-TLV . . . . . . . . . . . . . 8 3.2. MPLS OAM Configuration Sub-TLV .............................9
3.2.1. CV Flag Rules of Use . . . . . . . . . . . . . . . . 10 3.2.1. CV Flag Rules of Use ...............................11
3.3. BFD Configuration sub-TLV . . . . . . . . . . . . . . . . 10 3.3. BFD Configuration Sub-TLV .................................12
3.3.1. BFD Identifiers sub-TLV . . . . . . . . . . . . . . . 12 3.3.1. BFD Identifiers Sub-TLV ............................14
3.3.2. Negotiation Timer Parameters sub-TLV . . . . . . . . 13 3.3.2. Negotiation Timer Parameters Sub-TLV ...............15
3.3.3. BFD Authentication sub-TLV . . . . . . . . . . . . . 14 3.3.3. BFD Authentication Sub-TLV .........................16
3.3.4. Traffic Class sub-TLV . . . . . . . . . . . . . . . . 15 3.3.4. Traffic Class Sub-TLV ..............................17
3.4. Performance Monitoring sub-TLV . . . . . . . . . . . . . 16 3.4. Performance Monitoring Sub-TLV ............................17
3.4.1. MPLS OAM PM Loss sub-TLV . . . . . . . . . . . . . . 17 3.4.1. MPLS OAM PM Loss Sub-TLV ...........................19
3.4.2. MPLS OAM PM Delay sub-TLV . . . . . . . . . . . . . . 19 3.4.2. MPLS OAM PM Delay Sub-TLV ..........................21
3.5. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . . 20 3.5. MPLS OAM FMS Sub-TLV ......................................22
4. Summary of MPLS OAM configuration errors . . . . . . . . . . 21 4. Summary of MPLS OAM Configuration Errors .......................23
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 5. IANA Considerations ............................................25
5.1. MPLS OAM Type . . . . . . . . . . . . . . . . . . . . . . 22 5.1. MPLS OAM Type .............................................25
5.2. MPLS OAM Configuration sub-TLV . . . . . . . . . . . . . 23 5.2. MPLS OAM Configuration Sub-TLV ............................25
5.3. MPLS OAM Configuration Sub-TLV Types . . . . . . . . . . 23 5.3. MPLS OAM Configuration Sub-TLV Types ......................26
5.4. BFD Configuration Sub-TLV Types . . . . . . . . . . . . . 24 5.4. BFD Configuration Sub-TLV Types ...........................26
5.5. Performance Monitoring sub-TLV Types . . . . . . . . . . 24 5.5. Performance Monitoring Sub-TLV Types ......................27
5.6. New RSVP-TE error codes . . . . . . . . . . . . . . . . . 25 5.6. New RSVP-TE Error Codes ...................................28
6. Contributing Authors . . . . . . . . . . . . . . . . . . . . 25 6. Security Considerations ........................................28
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25 7. References .....................................................29
8. Security Considerations . . . . . . . . . . . . . . . . . . . 26 7.1. Normative References ......................................29
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 26 7.2. Informative References ....................................30
9.1. Normative References . . . . . . . . . . . . . . . . . . 26 Acknowledgements ..................................................31
9.2. Informative References . . . . . . . . . . . . . . . . . 27 Contributors ......................................................31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 Authors' Addresses ................................................32
1. Introduction 1. Introduction
This document describes the configuration of proactive MPLS-TP (MPLS- This document describes the configuration of proactive MPLS-TP OAM
Transport Profile) Operations, Administration, and Maintenance (OAM) functions for a given LSP using TLVs that use GMPLS RSVP-TE
Functions for a given LSP using TLVs using GMPLS RSVP-TE [RFC3473]. [RFC3473]. [RFC7260] defines use of GMPLS RSVP-TE for the
[RFC7260] defines use of GMPLS RSVP-TE for the configuration of OAM configuration of OAM functions in a technology-agnostic way. This
functions in a technology agnostic way. This document specifies the document specifies the additional mechanisms necessary to establish
additional mechanisms necessary to establish MPLS-TP OAM entities at MPLS-TP OAM entities at the maintenance points for monitoring and
the maintenance points for monitoring and performing measurements on performing measurements on an LSP, as well as defining information
an LSP, as well as defining information elements and procedures to elements and procedures to configure proactive MPLS-TP OAM functions
configure proactive MPLS-TP OAM functions running between LERs. running between Label Edge Routers (LERs). Initialization and
Initialization and control of on-demand MPLS-TP OAM functions are control of on-demand MPLS-TP OAM functions are expected to be carried
expected to be carried out by directly accessing network nodes via a out by directly accessing network nodes via a management interface;
management interface; hence configuration and control of on-demand hence, configuration and control of on-demand OAM functions are out
OAM functions are out-of-scope for this document. of scope for this document.
MPLS-TP, the Transport Profile of MPLS, must, by definition MPLS-TP, the Transport Profile of MPLS, must, by definition
[RFC5654], be capable of operating without a control plane. [RFC5654], be capable of operating without a control plane.
Therefore, there are several options for configuring MPLS-TP OAM, Therefore, there are several options for configuring MPLS-TP OAM
without a control plane by either using an NMS or LSP Ping, or with a without a control plane by using either a Network Management System
control plane using signaling protocols such as RSVP-TE. (NMS), an LSP Ping, or signaling protocols such as RSVP-TE in the
control plane.
MPLS-TP describes a profile of MPLS that enables operational models MPLS-TP describes a profile of MPLS that enables operational models
typical in transport networks, while providing additional OAM, typical in transport networks while providing additional OAM
survivability and other maintenance functions not currently supported survivability and other maintenance functions not currently supported
by MPLS. [RFC5860] defines the requirements for the OAM by MPLS. [RFC5860] defines the requirements for the OAM
functionality of MPLS-TP. functionality of MPLS-TP.
Proactive MPLS-TP OAM is performed by three different protocols, Bi- Proactive MPLS-TP OAM is performed by three different protocols:
directional Forwarding Detection (BFD) [RFC6428] for Continuity Bidirectional Forwarding Detection (BFD) [RFC6428] for Continuity
Check/Connectivity Verification, the delay measurement protocol (DM) Check / Connectivity Verification, the Delay Measurement (DM)
[RFC6374] for delay and delay variation (jitter) measurements, and protocol [RFC6374] for delay and delay variation (jitter)
the loss measurement protocol (LM) [RFC6374] for packet loss and measurements, and the Loss Measurement (LM) protocol [RFC6374] for
throughput measurements. Additionally, there is a number of Fault packet loss and throughput measurements. Additionally, there are a
Management Signals that can be configured [RFC6427]. number of Fault Management signals that can be configured [RFC6427].
BFD is a protocol that provides low-overhead, fast detection of BFD is a protocol that provides low-overhead, fast detection of
failures in the path between two forwarding engines, including the failures in the path between two forwarding engines, including the
interfaces, data link(s), and to the extent possible the forwarding interfaces, data link(s), and (to the extent possible) the forwarding
engines themselves. BFD can be used to track the liveliness and engines themselves. BFD can be used to track the liveliness and to
detect data plane failures of MPLS-TP point-to-point and might also detect the data plane failures of MPLS-TP point to point and might
be extended to support point-to-multipoint connections. also be extended to support point-to-multipoint connections.
The delay and loss measurements protocols [RFC6374] use a simple The delay and loss measurement protocols [RFC6374] use a simple
query/response model for performing bidirectional measurements that query/response model for performing bidirectional measurements that
allows the originating node to measure packet loss and delay in both allows the originating node to measure packet loss and delay in both
directions. By timestamping and/or writing current packet counters directions. By timestamping and/or writing current packet counters
to the measurement packets at four times (Tx and Rx in both to the measurement packets four times (Tx and Rx in both directions),
directions) current delays and packet losses can be calculated. By current delays and packet losses can be calculated. By performing
performing successive delay measurements the delay variation (jitter) successive delay measurements, the delay variation (jitter) can be
can be calculated. Current throughput can be calculated from the calculated. Current throughput can be calculated from the packet
packet loss measurements by dividing the number of packets sent/ loss measurements by dividing the number of packets sent/received
received with the time it took to perform the measurement, given by with the time it took to perform the measurement, given by the
the timestamp in LM header. Combined with a packet generator the timestamp in LM header. Combined with a packet generator, the
throughput measurement can be used to measure the maximum capacity of throughput measurement can be used to measure the maximum capacity of
a particular LSP. It should be noted that here we are not a particular LSP. It should be noted that here we are not
configuring on-demand throughput estimates based on saturating the configuring on-demand throughput estimates based on saturating the
connection as defined in [RFC6371]. Rather, we only enable the connection as defined in [RFC6371]. Rather, we only enable the
estimation of the current throughput based on loss measurements. estimation of the current throughput based on loss measurements.
1.1. Conventions used in this document 1.1. Conventions Used in This Document
1.1.1. Terminology 1.1.1. Terminology
BFD - Bidirectional Forwarding Detection AIS - Alarm Indication Signal
CV - Connectivity Verification BFD - Bidirectional Forwarding Detection
CC - Continuity Check CC - Continuity Check
CV - Connectivity Verification
DM - Delay Measurement DM - Delay Measurement
FMS - Fault Management Signal FMS - Fault Management Signal
G-ACh - Generic Associated Channel G-ACh - Generic Associated Channel
GMPLS - Generalized Multi-Protocol Label Switching GMPLS - Generalized Multi-Protocol Label Switching
LER - Label switching Edge Router LDI - Link Down Indication
LER - Label Edge Router
LKR - Lock Report
LM - Loss Measurement LM - Loss Measurement
LOC - Loss Of Continuity
LSP - Label Switched Path LSP - Label Switched Path
LSR - Label Switching Router LSR - Label Switching Router
MEP - Maintenance Entity Group End Point MEP - Maintenance Entity Group End Point
MIP - Maintenance Entity Group Intermediate 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 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].
skipping to change at page 5, line 20 skipping to change at page 6, line 30
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].
[RFC6428] specifies two BFD operation modes: 1) "CC mode", which uses [RFC6428] specifies two BFD operation modes: 1) "CC mode", which uses
periodic BFD message exchanges with symmetric timer settings, periodic BFD message exchanges with symmetric timer settings
supporting Continuity Check, 2) "CV/CC mode" which sends unique supporting Continuity Check, and 2) "CV/CC mode", which sends unique
maintenance entity identifiers in the periodic BFD messages maintenance entity identifiers in the periodic BFD messages
supporting Connectivity Verification (CV) as well as Continuity Check supporting CV as well as CC.
(CC).
[RFC6374] specifies mechanisms for performance monitoring of LSPs, in [RFC6374] specifies mechanisms for Performance Monitoring of LSPs, in
particular it specifies loss and delay measurement OAM functions. particular it specifies loss and delay measurement OAM functions.
[RFC6427] specifies fault management signals with which a server LSP [RFC6427] specifies fault management signals with which a server LSP
can notify client LSPs about various fault conditions to suppress can notify client LSPs about various fault conditions to suppress
alarms or to be used as triggers for actions in the client LSPs. The alarms or to be used as triggers for actions in the client LSPs. The
following signals are defined: Alarm Indication Signal (AIS), Link following signals are defined: Alarm Indication Signal (AIS), Link
Down Indication (LDI) and Lock Report (LKR). Down Indication (LDI), and Lock Report (LKR).
[RFC6371] describes the mapping of fault conditions to consequent [RFC6371] describes the mapping of fault conditions to consequent
actions. Some of these mappings may be configured by the operator, actions. Some of these mappings may be configured by the operator
depending on the application of the LSP. The following defects are depending on the application of the LSP. The following defects are
identified: Loss Of Continuity (LOC), Misconnectivity, MEP identified: Loss Of Continuity (LOC), Misconnectivity, MEP
Misconfiguration and Period Misconfiguration. Out of these defect Misconfiguration, and Period Misconfiguration. Out of these defect
conditions, the following consequent actions may be configurable: 1) conditions, the following consequent actions may be configurable: 1)
whether or not the LOC defect should result in blocking the outgoing whether or not the LOC defect should result in blocking the outgoing
data traffic; 2) whether or not the "Period Misconfiguration defect" data traffic; 2) whether or not the "Period Misconfiguration defect"
should result in a signal fail condition. should result in a signal fail condition.
3. Theory of Operations 3. Theory of Operations
3.1. MPLS-TP OAM Configuration Operation Overview 3.1. MPLS-TP OAM Configuration Operation Overview
GMPLS RSVP-TE, or alternatively LSP Ping [LSP-PING-CONF], can be used GMPLS RSVP-TE, or alternatively LSP Ping [LSP-PING-CONF], can be used
to simply enable the different OAM functions, by setting the to simply enable the different OAM functions by setting the
corresponding flags in the "OAM Function Flags sub-TLV" [RFC7260]. corresponding flags in the OAM Function Flags Sub-TLV [RFC7260]. 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 MUST be examined even by intermediate TLV is present. This sub-TLV MUST be examined even by intermediate
nodes that support these extensions, but only acted upon by nodes nodes that support these extensions but only acted upon by nodes
capable of transmitting FMS signals into the LSP being established. capable of transmitting FMS signals into the LSP being established.
The sub-TLV MAY be present when the FMS flag is set in the "OAM The sub-TLV MAY be present when the FMS flag is set in the OAM
Function Flags sub-TLV". If this sub-TLV is present, then the "OAM Function Flags Sub-TLV. If this sub-TLV is present, then the "OAM
MIP entities desired" and "OAM MEP entities desired" flags (described MIP entities desired" and "OAM MEP entities desired" flags (described
in [RFC7260]) in the "LSP Attributes Flags TLV" MUST be set and the in [RFC7260]) in the LSP Attribute Flags TLV MUST be set and the
entire OAM Configuration TLV placed either in the entire OAM Configuration TLV placed either in the
LSP_REQUIRED_ATTRIBUTES object or in the LSP_ATTRIBUTES object in LSP_REQUIRED_ATTRIBUTES object or in the LSP_ATTRIBUTES object in
order to ensure that capable intermediate nodes process the order to ensure that capable intermediate nodes process the
configuration. If placed in LSP_ATTRIBUTES object, nodes that are configuration. If placed in the LSP_ATTRIBUTES object, nodes that
not able to process the OAM Configuration TLV will forward the are not able to process the OAM Configuration TLV will forward the
message without generating an error. If the "MPLS OAM FMS sub-TLV" message without generating an error. If the MPLS OAM FMS Sub-TLV has
been placed in the LSP_REQUIRED_ATTRIBUTES object a node that 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" supports RFC 7260 but does not support the MPLS OAM FMS Sub-TLV MUST
MUST generate PathErr message with "OAM Problem/Configuration Error" generate a PathErr message with "OAM Problem/Configuration Error"
[RFC7260]. Otherwise, if the node doesn't support the RFC 7260, it [RFC7260]. Otherwise, if the node doesn't support RFC 7260, it will
will not raise any errors as described in the Section 4.1 [RFC7260]. not raise any errors as described in the Section 4.1 of [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:
- Asynchronous mode, where both sides should be in active mode o Asynchronous mode, where both sides should be in active mode; or
- Unidirectional mode o Unidirectional mode.
In the simplest scenario, RSVP-TE, or alternatively LSP Ping [LSP- In the simplest scenario, RSVP-TE (or alternatively LSP Ping
PING-CONF], is used only to bootstrap a BFD session for an LSP, [LSP-PING-CONF]), is used only to bootstrap a BFD session for an LSP
without any timer negotiation. without any timer negotiation.
Timer negotiation can be performed either in subsequent BFD control Timer negotiation can be performed either in subsequent BFD Control
messages (in this case the operation is similar to LSP Ping based messages (in this case the operation is similar to LSP-Ping-based
bootstrapping described in [RFC5884]) or directly in the RSVP-TE bootstrapping described in [RFC5884]) or directly in the RSVP-TE
signaling messages. signaling messages.
When BFD Control packets are transported in the G-ACh they are not When BFD Control packets are transported in the G-ACh, they are not
protected by any end-to-end checksum, only lower-layers are providing protected by any end-to-end checksum; only lower layers are providing
error detection/correction. A single bit error, e.g. a flipped bit error detection/correction. A single bit error, e.g., a flipped bit
in the BFD State field could cause the receiving end to wrongly in the BFD State field, could cause the receiving end to wrongly
conclude that the link is down and in turn trigger protection conclude that the link is down and, in turn, trigger protection
switching. To prevent this from happening the "BFD Configuration switching. To prevent this from happening, the BFD Configuration
sub-TLV" has an Integrity flag that when set enables BFD Sub-TLV has an Integrity flag that, when set, enables BFD
Authentication using Keyed SHA1 with an empty key (all 0s) [RFC5880]. Authentication using Keyed SHA1 with an empty key (all 0s) [RFC5880].
This would ensure that every BFD Control packet carries an SHA1 hash This would ensure that every BFD Control packet carries a SHA1 hash
of itself that can be used to detect errors. of itself that can be used to detect errors.
If BFD Authentication using a pre-shared key / password is desired If BFD Authentication using a pre-shared key / password is desired
(i.e. authentication and not only error detection), the "BFD (i.e., authentication and not only error detection), the BFD
Authentication sub-TLV" MUST be included in the "BFD Configuration Authentication Sub-TLV MUST be included in the BFD Configuration Sub-
sub-TLV". The "BFD Authentication sub-TLV" is used to specify which TLV. The BFD Authentication Sub-TLV is used to specify which
authentication method should be used and which pre-shared key / authentication method should be used and which pre-shared key /
password should be used for this particular session. How the key password should be used for this particular session. How the key
exchange is performed is out of scope of this document. exchange is performed is out of scope of this document.
3.1.2. Configuration of Performance Monitoring 3.1.2. Configuration of Performance Monitoring
It is possible to configure Performance Monitoring functionalities It is possible to configure Performance Monitoring functionalities
such as Loss, Delay, Delay variation (jitter), and Throughput as such as Loss, Delay, Delay variation (jitter), and Throughput, as
described in [RFC6374]. described in [RFC6374].
When configuring Performance monitoring functionalities it is When configuring Performance Monitoring functionalities, it is
possible to choose either the default configuration, by only setting possible to choose either the default configuration (by only setting
the respective flags in the "OAM Function Flags sub-TLV", or a the respective flags in the OAM Function Flags Sub-TLV) or a
customized configuration. To customize the configuration, one would customized configuration. To customize the configuration, one would
set the respective flags and including the respective Loss and/or set the respective flags and include the respective Loss and/or Delay
Delay sub-TLVs). sub-TLVs.
By setting the PM/Loss flag in the "OAM Function Flags sub-TLV" and By setting the PM/Loss flag in the OAM Function Flags Sub-TLV and by
by including the "MPLS OAM PM Loss sub-TLV", one can configure the including the MPLS OAM PM Loss Sub-TLV, one can configure the
measurement interval and loss threshold values for triggering measurement interval and loss threshold values for triggering
protection. protection.
Delay measurements are configured by setting PM/Delay flag in the Delay measurements are configured by setting the PM/Delay flag in the
"OAM Function Flags sub-TLV", and by including the "MPLS OAM PM Loss OAM Function Flags Sub-TLV; by including the MPLS OAM PM Loss Sub-
sub-TLV", one can configure the measurement interval and the delay 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
OAM FMS sub-TLV" included. When configuring Fault Management FMS Sub-TLV included. When configuring Fault Management signals, an
Signals, an implementation can enable the default configuration by implementation can enable the default configuration by setting the
setting the FMS flag in the "OAM Function Flags sub-TLV". In order FMS flag in the OAM Function Flags Sub-TLV. In order to modify the
to modify the default configuration the "MPLS OAM FMS sub-TLV" MUST default configuration, the MPLS OAM FMS Sub-TLV MUST be included.
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 with a server MEP through a co-located MPLS-TP client/ associated with a server MEP through a co-located MPLS-TP client/
server adaptation function and the "Fault Management subscription" server adaptation function, and the "Fault Management subscription"
flag in the "MPLS OAM FMS sub-TLV" been set as indication of the flag in the MPLS OAM FMS Sub-TLV has been set as an indication of the
request to create the association at each intermediate node of the request to create the association at each intermediate node of the
client LSP. Corresponding server MEP needs to be configured by its client LSP. The corresponding server MEP needs to be configured by
own RSVP-TE session (or, alternatively, via an NMS or LSP-ping). its own RSVP-TE session (or, alternatively, via an NMS or LSP Ping).
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" (3). The
The "MPLS OAM" type is set to request the establishment of OAM MPLS OAM type is set to request the establishment of OAM functions
functions for MPLS-TP LSPs. The specific OAM functions are specified for MPLS-TP LSPs. The specific OAM functions are specified in the
in the "OAM Function Flags sub-TLV" as depicted in [RFC7260]. OAM Function Flags Sub-TLV as depicted in [RFC7260].
When an egress LSR receives an "OAM Configuration TLV" indicating the When an egress LSR receives an OAM Configuration TLV indicating the
MPLS OAM type, the LSR will first process any present "OAM Function MPLS OAM type, the LSR will first process any present OAM Function
Flags sub-TLV" and then it MUST process technology specific Flags Sub-TLV, and then it MUST process technology-specific
configuration TLVs. This document defines a sub-TLV, the "MPLS OAM configuration TLVs. This document defines a sub-TLV, the MPLS OAM
Configuration sub-TLV" which is carried in the "OAM Configuration Configuration Sub-TLV, which is carried in the OAM Configuration TLV.
TLV".
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 Conf. sub-TLV (TBA2) | Length | | MPLS OAM Conf. Sub-TLV (33) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ sub-TLVs ~ ~ sub-TLVs ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: TBA2, the "MPLS OAM Configuration sub-TLV". Figure 1: MPLS OAM Configuration Sub-TLV Format
Length: indicates the total length in octets, including sub-TLVs as Type: 33, the MPLS OAM Configuration Sub-TLV.
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.
The following MPLS OAM specific sub-TLVs MAY be included in the "MPLS The following MPLS-OAM-specific sub-TLVs MAY be included in the MPLS
OAM Configuration sub-TLV": OAM Configuration Sub-TLV:
- "BFD Configuration sub-TLV", which MUST be included if either o BFD Configuration Sub-TLV MUST be included if either the CC, the
the CC, the CV or both OAM Function flags being set in the OAM CV, or both OAM Function flags are being set in the OAM Function
Function Flags Sub-TLV [RFC7260]. This sub-TLV carries additional Flags Sub-TLV [RFC7260]. This sub-TLV carries additional sub-
sub-TLVs, failure to include the correct sub-TLVs MUST result in TLVs; failure to include the correct sub-TLVs MUST result in an
an error being generated: "OAM Problem/Configuration Error". The error being generated: "OAM Problem/Configuration Error". The
sub-TLVs are: sub-TLVs are:
- "BFD Identifiers sub-TLV", MUST always be included. * BFD Identifiers Sub-TLV MUST always be included.
- "Timer Negotiation Parameters sub-TLV", MUST be included if * Timer Negotiation Parameters Sub-TLV MUST be included if the N
the N flag is not set. flag is not set.
- "BFD Authentication sub-TLV", MAY be included if the I flag * BFD Authentication Sub-TLV MAY be included if the I flag is
is set. set.
- "Performance Monitoring sub-TLV", which MUST be included if any o Performance Monitoring Sub-TLV, which MUST be included if any of
of the PM/Delay, PM/Loss or PM/Throughput flags are set in the the PM/Delay, PM/Loss, or PM/Throughput flags are set in the OAM
"OAM Function Flag sub-TLV" [RFC7260]. This sub-TLV MAY carry Function Flag Sub-TLV [RFC7260]. This sub-TLV MAY carry
additional sub-TLVs: additional sub-TLVs:
- "MPLS OAM PM Loss sub-TLV" MAY be included if the PM/Loss OAM * MPLS OAM PM Loss Sub-TLV MAY be included if the PM/Loss OAM
Function flag is set. If the "MPLS OAM PM Loss sub-TLV" is not Function flag is set. If the MPLS OAM PM Loss Sub-TLV is not
included, default configuration values are used. The same sub- included, default configuration values are used. The same sub-
TLV MAY also be included in case the PM/Throughput OAM Function TLV MAY also be included in case the PM/Throughput OAM Function
flag is set and there is the need to specify measurement flag is set and there is the need to specify measurement
interval different from the default ones. Since throughput intervals different from the default ones. Since throughput
measurements use the same tool as loss measurements the same measurements use the same tool as loss measurements, the same
TLV is used. TLV is used.
- "MPLS OAM PM Delay sub-TLV" MAY be included if the PM/Delay * MPLS OAM PM Delay Sub-TLV MAY be included if the PM/Delay OAM
OAM Function flag is set. If the "MPLS OAM PM Delay sub-TLV" Function flag is set. If the MPLS OAM PM Delay Sub-TLV is not
is not included, default configuration values are used. included, default configuration values are used.
- "MPLS OAM FMS sub-TLV" MAY be included if the FMS OAM Function o MPLS OAM FMS Sub-TLV MAY be included if the FMS OAM Function flag
flag is set. If the "MPLS OAM FMS sub-TLV" is not included, is set. If the MPLS OAM FMS Sub-TLV is not included, default
default configuration values are used. configuration values are used.
Following are some additional rules of processing MPLS OAM The following are some additional rules of processing the MPLS OAM
Configuration sub-TLV: Configuration Sub-TLV:
- MPLS OAM Configuration sub-TLV MAY be empty, i.e. have no Value. o The MPLS OAM Configuration Sub-TLV MAY be empty, i.e., have no
Then its Length MUST be 8. Then all OAM functions that have their Value. If so, then its Length MUST be 8. Then, all OAM functions
corresponding flags set in the "OAM Function Flags sub-TLV" MUST that have their corresponding flags set in the OAM Function Flags
be assigned their default values or left disabled. Sub-TLV MUST be assigned their default values or left disabled.
- Sub-TLV that doesn't have corresponding flag set MUST be o A sub-TLV that doesn't have a corresponding flag set MUST be
silently ignored. silently ignored.
- If multiple copies of a sub-TLV are present, then only the first o 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.
3.2.1. CV Flag Rules of Use 3.2.1. CV Flag Rules of Use
If the CV flag is set in the OAM Function Flags Sub-TLV [RFC7260], If the CV flag is set in the OAM Function Flags Sub-TLV [RFC7260],
then the CC flag MUST be set as well because performing Connectivity then the CC flag MUST be set as well because performing Connectivity
Verification implies performing Continuity Check as well. The format Verification implies performing Continuity Check as well. The format
of an MPLS-TP CV/CC message is shown in [RFC6428]. In order to of an MPLS-TP CV/CC message is shown in [RFC6428]. In order to
perform Connectivity Verification the CV/CC message MUST contain the perform Connectivity Verification, the CV/CC message MUST contain the
"LSP MEP-ID" in addition to the BFD Control packet information. The "LSP MEP-ID" in addition to the BFD Control packet information. The
"LSP MEP-ID" contains four identifiers: "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 need to know
what to expect when receiving 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 use 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
TLV" is carried as a sub-TLV of the "MPLS OAM Configuration sub-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.|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". Figure 2: BFD Configuration Sub-TLV Format
Length: indicates the total length in octets, including sub-TLVs as Type: 1, the BFD Configuration Sub-TLV.
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".
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-
sub-TLV" the authentication MUST use Keyed SHA1 with an empty pre- TLV, the authentication MUST use Keyed SHA1 with an empty pre-shared
shared key (all 0s). If the egress LSR does not support BFD key (all 0s). If the egress LSR does not support BFD Authentication,
Authentication an error MUST be generated: "OAM Problem/BFD an error MUST be generated: "OAM Problem/BFD Authentication
Authentication unsupported". unsupported".
Encapsulation Capability (G): if set, shows the capability of Encapsulation Capability (G): If set, it shows the capability of
encapsulating BFD messages into The G-Ach channel. If both the G bit encapsulating BFD messages into The G-Ach channel. If both the G bit
and U bit are set, configuration gives precedence to the G bit. If and U bit are set, configuration gives precedence to the G bit. If
the egress LSR does not support any of the ingress LSR Encapsulation the egress LSR does not support any of the ingress LSR Encapsulation
Capabilities an error MUST be generated: "OAM Problem/Unsupported BFD Capabilities, an error MUST be generated: "OAM Problem/Unsupported
Encapsulation format". BFD Encapsulation format".
Encapsulation Capability (U): if set, shows the capability of Encapsulation Capability (U): If set, it shows the capability of
encapsulating BFD messages into UDP packets. If both the G bit and U encapsulating BFD messages into UDP packets. If both the G bit and U
bit are set, configuration gives precedence to the G bit. If the bit are set, configuration gives precedence to the G bit. If the
egress LSR does not support any of the ingress LSR Encapsulation egress LSR does not support any of the ingress LSR Encapsulation
Capabilities an error MUST be generated: "OAM Problem/Unsupported BFD Capabilities, an error MUST be generated: "OAM Problem/Unsupported
Encapsulation format". BFD Encapsulation Format".
Bidirectional (B): if set, it configures BFD in the Bidirectional Bidirectional (B): If set, it configures BFD in the Bidirectional
mode. If it is not set it configures BFD in unidirectional mode. In mode. If it is not set, it configures BFD in unidirectional mode.
the second case, the source node does not expect any Discriminator In the second case, the source node does not expect any Discriminator
values back from the destination node. values back from the destination node.
Reserved: Reserved for future specification and set to 0 on Reserved: Reserved for future specifications; set to 0 on
transmission and ignored when received. transmission and ignored when received.
The "BFD Configuration sub-TLV" MUST include the following sub-TLVs The BFD Configuration Sub-TLV MUST include the following sub-TLVs in
in the Path message: the Path message:
- "BFD Identifiers sub-TLV";
- "Negotiation Timer Parameters sub-TLV" if the N flag is cleared. o BFD Identifiers Sub-TLV; and
The "BFD Configuration sub-TLV" MUST include the following sub-TLVs o Negotiation Timer Parameters Sub-TLV if the N flag is cleared.
in the Resv message:
- "BFD Identifiers sub-TLV;" The BFD Configuration Sub-TLV MUST include the following sub-TLVs in
the Resv message:
- "Negotiation Timer Parameters sub-TLV" if: o BFD Identifiers Sub-TLV; and
- the N and S flags are cleared, or if: o Negotiation Timer Parameters Sub-TLV if:
- the N flag is cleared and the S flag is set, and the * the N and S flags are cleared; or if
"Negotiation Timer Parameters sub-TLV" received by the egress * the N flag is cleared and the S flag is set and the Negotiation
contains unsupported values. In this case an updated Timer Parameters Sub-TLV received by the egress contains
"Negotiation Timer Parameters sub-TLV", containing values unsupported values. In this case, an updated Negotiation Timer
supported by the egress LSR, MUST be returned to the ingress. Parameters Sub-TLV containing values supported by the egress
LSR MUST be returned to the ingress.
3.3.1. BFD Identifiers sub-TLV 3.3.1. BFD Identifiers Sub-TLV
The "BFD Identifiers sub-TLV" is carried as a sub-TLV of the "BFD The BFD Identifiers Sub-TLV is carried as a sub-TLV of the BFD
Configuration sub-TLV" and is depicted below. Configuration Sub-TLV and is depicted below.
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 Identfiers Type (1) | Length | | BFD Identifiers Type (1) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Discriminator | | Local Discriminator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MPLS-TP Global_ID | | MPLS-TP Global_ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MPLS-TP Node Identifier | | MPLS-TP Node Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tunnel_Num | LSP_Num | | Tunnel_Num | LSP_Num |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1, "BFD Identifiers sub-TLV". Figure 3: BFD Identifiers Sub-TLV Format
Length: indicates the TLV total length in octets, including the Type Type: 1, the BFD Identifiers Sub-TLV.
Length: Indicates the TLV total length in octets, including the Type
and Length fields (20). and Length fields (20).
Local Discriminator: A unique, nonzero discriminator value generated Local Discriminator: A unique, non-zero discriminator value generated
by the transmitting system and referring to itself, used to by the transmitting system and referring to itself; it is used to de-
demultiplex multiple BFD sessions between the same pair of systems as multiplex multiple BFD sessions between the same pair of systems as
defined in [RFC5880]. defined in [RFC5880].
MPLS-TP Global_ID, Node Identifier, Tunnel_Num, and LSP_Num: all set MPLS-TP Global_ID, Node Identifier, Tunnel_Num, and LSP_Num: All set
as defined in [RFC6370]. as defined in [RFC6370].
3.3.2. Negotiation Timer Parameters sub-TLV 3.3.2. Negotiation Timer Parameters Sub-TLV
The "Negotiation Timer Parameters sub-TLV" is carried as a sub-TLV of The Negotiation Timer Parameters Sub-TLV is carried as a sub-TLV of
the "BFD Configuration sub-TLV" and is depicted below. the BFD Configuration Sub-TLV and is depicted below.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Nego. Timer Type (2) | Length | | Nego. Timer Type (2) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Acceptable Min. Asynchronous TX interval | | Acceptable Min. Asynchronous TX interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Acceptable Min. Asynchronous RX interval | | Acceptable Min. Asynchronous RX interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Required Echo TX Interval | | Required Echo TX Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 2, "Negotiation Timer Parameters sub-TLV". Figure 4: Negotiation Timer Parameters Sub-TLV Format
Length: indicates the TLV total length in octets, including Type and Type: 2, the Negotiation Timer Parameters Sub-TLV.
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 flag is set in the
is set in the "BFD Configuration sub-TLV", it expresses the desired BFD Configuration Sub-TLV, it expresses the desired time interval (in
time interval (in microseconds) at which the ingress LER intends to microseconds) at which the ingress LER intends to both transmit and
both transmit and receive BFD periodic control packets. If the receive BFD periodic control packets. If the egress LSR cannot
egress LSR cannot support the value, it SHOULD reply with a supported support the value, it SHOULD reply with a supported interval.
interval.
If the S (symmetric) flag is cleared in the "BFD Configuration sub- If the S flag is cleared in the BFD Configuration Sub-TLV, this field
TLV", this field expresses the desired time interval (in expresses the desired time interval (in microseconds) at which the
microseconds) at which the ingress LSR intends to transmit BFD 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 flag is set in the
is set in the "BFD Configuration sub-TLV", this field MUST be set BFD Configuration Sub-TLV, this field MUST be set equal to
equal to "Acceptable Min. Asynchronous TX interval" on transmit and "Acceptable Min. Asynchronous TX interval" on transmit and MUST be
MUST be ignored on receipt since it has no additional meaning with ignored on receipt since it has no additional meaning with respect to
respect to the one described for "Acceptable Min. Asynchronous TX the one described for "Acceptable Min. Asynchronous TX interval".
interval".
If the S (symmetric) flag is cleared in the "BFD Configuration sub- If the S flag is cleared in the BFD Configuration Sub-TLV, it
TLV", it expresses the minimum time interval (in microseconds) at expresses the minimum time interval (in microseconds) at which the
which the ingress/egress LSRs can receive periodic BFD control ingress/egress LSRs can receive periodic BFD Control packets. If
packets. If this value is greater than the "Acceptable Min. this value is greater than the "Acceptable Min. Asynchronous TX
Asynchronous TX interval" received from the ingress/egress LSR, the interval" received from the ingress/egress LSR, the receiving LSR
receiving LSR MUST adopt the interval expressed in the "Acceptable MUST adopt the interval expressed in the "Acceptable Min.
Min. Asynchronous RX interval". Asynchronous RX interval".
Required Echo TX Interval: the minimum interval (in microseconds) Required Echo TX Interval: The minimum interval (in microseconds)
between received BFD Echo packets that this system is capable of between received BFD Echo packets that this system is capable of
supporting, less any jitter applied by the sender as described in supporting, less any jitter applied by the sender as described in
[RFC5880] sect. 6.8.9. This value is also an indication for the Section 6.8.9 of [RFC5880]. This value is also an indication for the
receiving system of the minimum interval between transmitted BFD Echo receiving system of the minimum interval between transmitted BFD Echo
packets. If this value is zero, the transmitting system does not packets. If this value is zero, the transmitting system does not
support the receipt of BFD Echo packets. If the LSR node cannot support the receipt of BFD Echo packets. If the LSR node cannot
support this value it SHOULD reply with a supported value (which may support this value, it SHOULD reply with a supported value (which may
be zero if Echo is not supported). be zero if Echo is not supported).
3.3.3. BFD Authentication sub-TLV 3.3.3. BFD Authentication Sub-TLV
The "BFD Authentication sub-TLV" is carried as a sub-TLV of the "BFD The BFD Authentication Sub-TLV is carried as a sub-TLV of the BFD
Configuration sub-TLV" and is depicted below. Configuration Sub-TLV and is depicted below.
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 Auth. Type (3) | Length | | BFD Auth. Type (3) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Auth Type | Auth Key ID | Reserved (0s) | | Auth Type | Auth Key ID | Reserved (0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 3, "BFD Authentication sub-TLV". Figure 5: BFD Authentication Sub-TLV Format
Length: indicates the TLV total length in octets, including Type and Type: 3, the BFD Authentication Sub-TLV.
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 are used as are defined in Section 4.1 of [RFC5880]. 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
Authentication Type" error MUST be generated. BFD 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 performed is out of scope of this document. If the egress LSR does
not 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 specifications; set to 0 on
transmission and ignored when received. transmission and ignored when received.
3.3.4. Traffic Class sub-TLV 3.3.4. Traffic Class Sub-TLV
The Traffic Class sub-TLV is carried as a sub-TLV of the "BFD The Traffic Class Sub-TLV is carried as a sub-TLV of the BFD
Configuration sub-TLV" or "Fault Management Signal sub-TLV" Configuration Sub-TLV or Fault Management Signal Sub-TLV
Section 3.5 and is depicted in Figure 1. (Section 3.5) and is depicted in Figure 6.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Class sub-Type (4) | Length | | Traffic Class Sub-Type (4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TC | Reserved (set to all 0s) | | TC | Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Traffic Class sub-TLV format Figure 6: Traffic Class Sub-TLV Format
Type: 3, "Traffic Class sub-TLV". Type: 4, the Traffic Class Sub-TLV.
Length: indicates the length of the Value field in octets . (4) Length: Indicates the length of the Value field in octets (4).
TC: Identifies the Traffic Class (TC) [RFC5462] for periodic
Traffic Class (TC): Identifies the TC [RFC5462] for periodic
continuity monitoring messages or packets with fault management continuity monitoring messages or packets with fault management
information. information.
If TC sub-TLV is present, then the value of the TC field MUST be used If the Traffic Class Sub-TLV is present, then the value of the TC
as the value of the TC field of an MPLS label stack entry. If the TC field MUST be used as the value of the TC field of an MPLS label
sub-TLV is absent from "BFD Configuration sub-TLV" or "Fault stack entry. If the Traffic Class Sub-TLV is absent from BFD
Management Signal sub-TLV", then selection of the TC value is local Configuration Sub-TLV or Fault Management Signal Sub-TLV, then
decision. selection of the TC value is a 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
be present in the "MPLS OAM Configuration sub-TLV". Failure to present in the MPLS OAM Configuration Sub-TLV. Failure to include
include the correct sub-TLVs MUST result in an "OAM Problem/ the correct sub-TLVs MUST result in an "OAM Problem/Configuration
Configuration Error" error being generated. Error" message 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
for the configuration of quality thresholds and, as described in for the configuration of quality thresholds and, as described in
[RFC6374], "the crossing of which will trigger warnings or alarms, [RFC6374], "the crossing of which will trigger warnings or alarms,
and result reporting and exception notification will be integrated and result reporting and exception notification will be integrated
into the system-wide network management and reporting framework." into the system-wide network management and reporting framework."
In case the values need to be different than the default ones, the
Performance Monitoring Sub-TLV includes the following sub-TLVs:
In case the values need to be different than the default ones the o MPLS OAM PM Loss Sub-TLV if the PM/Loss and/or PM/Throughput flag
"Performance Monitoring sub-TLV" includes the following sub-TLVs: is set in the OAM Function Flags Sub-TLV; and
- "MPLS OAM PM Loss sub-TLV" if the PM/Loss and/or PM/Throughput
flag is set in the "OAM Function Flags sub-TLV";
- "MPLS OAM PM Delay sub-TLV" if the PM/Delay flag is set in the o MPLS OAM PM Delay Sub-TLV if the PM/Delay flag is set in the OAM
"OAM Function Flags sub-TLV"; Function Flags Sub-TLV.
The "Performance Monitoring sub-TLV" depicted below is carried as a The Performance Monitoring Sub-TLV depicted below is carried as a
sub-TLV of the "MPLS OAM Configuration sub-TLV". sub-TLV of the MPLS OAM Configuration Sub-TLV.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Perf. Monitoring Type(2) | Length | | Perf. Monitoring Type (2) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|D|L|J|Y|K|C| Reserved (set to all 0s) | |D|L|J|Y|K|C| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ sub-TLVs ~ ~ sub-TLVs ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 2, "Performance Monitoring sub-TLV".
Length: indicates the TLV total length in octets, including sub-TLVs Figure 7: Performance Monitoring Sub-TLV Format
Type: 2, the Performance Monitoring Sub-TLV.
Length: Indicates the TLV total length in octets, including sub-TLVs
as well as Type and Length fields. as well as Type and Length fields.
Configuration Flags, for the specific function description please Configuration Flags (for the specific function description please
refer to [RFC6374]: refer to [RFC6374]):
- D: Delay inferred/direct (0=INFERRED, 1=DIRECT). If the egress o D: Delay inferred/direct (0=INFERRED, 1=DIRECT). If the egress
LSR does not support specified mode an "OAM Problem/Unsupported LSR does not support the specified mode, an "OAM Problem/
Delay Mode" error MUST be generated. Unsupported Delay Mode" error MUST be generated.
- L: Loss inferred/direct (0=INFERRED, 1=DIRECT). If the egress o L: Loss inferred/direct (0=INFERRED, 1=DIRECT). If the egress LSR
LSR does not support specified mode an "OAM Problem/Unsupported does not support the specified mode, an "OAM Problem/Unsupported
Loss Mode" error MUST be generated. Loss Mode" error MUST be generated.
- J: Delay variation/jitter (1=ACTIVE, 0=NOT ACTIVE). If the o J: Delay variation/jitter (1=ACTIVE, 0=NOT ACTIVE). If the egress
egress LSR does not support Delay variation measurements and the J LSR does not support Delay variation measurements and the J flag
flag is set, an "OAM Problem/Delay variation unsupported" error is set, an "OAM Problem/Delay variation unsupported" error MUST be
MUST be generated. generated.
- Y: Dyadic (1=ACTIVE, 0=NOT ACTIVE). If the egress LSR does not o Y: Dyadic (1=ACTIVE, 0=NOT ACTIVE). If the egress LSR does not
support Dyadic mode and the Y flag is set, an "OAM Problem/Dyadic support Dyadic mode and the Y flag is set, an "OAM Problem/Dyadic
mode unsupported" error MUST be generated. mode unsupported" error MUST be generated.
- K: Loopback (1=ACTIVE, 0=NOT ACTIVE). If the egress LSR does o K: Loopback (1=ACTIVE, 0=NOT ACTIVE). If the egress LSR does not
not support Loopback mode and the K flag is set, an "OAM Problem/ support Loopback mode and the K flag is set, an "OAM Problem/
Loopback mode unsupported" error MUST be generated. Loopback mode unsupported" error MUST be generated.
- C: Combined (1=ACTIVE, 0=NOT ACTIVE). If the egress LSR does o C: Combined (1=ACTIVE, 0=NOT ACTIVE). If the egress LSR does not
not support Combined mode and the C flag is set, an "OAM Problem/ support Combined mode and the C flag is set, an "OAM Problem/
Combined mode unsupported" error MUST be generated. Combined mode unsupported" error MUST be generated.
Reserved: Reserved for future specification and set to 0 on Reserved: Reserved for future specifications; set to 0 on
transmission and ignored when received. transmission and ignored when received.
3.4.1. MPLS OAM PM Loss sub-TLV 3.4.1. MPLS OAM PM Loss Sub-TLV
The "MPLS OAM PM Loss sub-TLV" depicted below is carried as a sub-TLV The MPLS OAM PM Loss Sub-TLV depicted below is carried as a sub-TLV
of the "Performance Monitoring sub-TLV". of the Performance Monitoring Sub-TLV.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PM Loss Type (1) | Length | | PM Loss Type (1) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OTF |T|B| Reserved (set to all 0s) | | OTF |T|B| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Interval | | Measurement Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Test Interval | | Test Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Loss Threshold | | Loss Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1,"MPLS OAM PM Loss sub-TLV". Figure 8: MPLS OAM PM Loss Sub-TLV Format
Length: indicates the length of the parameters in octets, including Type: 1, the MPLS OAM PM Loss Sub-TLV.
Length: Indicates the length of the parameters in octets, including
Type and Length fields (20). Type and Length fields (20).
OTF: Origin Timestamp Format of the Origin Timestamp field described Origin Timestamp Format (OTF): Origin Timestamp Format of the Origin
in [RFC6374]. By default it is set to IEEE 1588 version 1. If the Timestamp field described in [RFC6374]. By default, it is set to
egress LSR cannot support this value an "OAM Problem/Unsupported IEEE 1588 version 1. If the egress LSR cannot support this value, an
Timestamp Format" error MUST be generated. "OAM Problem/Unsupported Timestamp Format" error MUST be generated.
Configuration Flags, please refer to [RFC6374] for further details: Configuration Flags (please refer to [RFC6374] for further details):
- T: Traffic-class-specific measurement indicator. Set to 1 when o T: Traffic-class-specific measurement indicator. Set to 1 when
the measurement operation is scoped to packets of a particular the measurement operation is scoped to packets of a particular
traffic class (DSCP value), and 0 otherwise. When set to 1, the traffic class (Differentiated Service Code Point (DSCP) value) and
DS field of the message indicates the measured traffic class. By zero otherwise. When set to 1, the Differentiated Services (DS)
default it is set to 1. field of the message indicates the measured traffic class. By
default, it is set to 1.
- B: Octet (byte) count. When set to 1, indicates that the o B: Octet (byte) count. When set to 1, it indicates that the
Counter 1-4 fields represent octet counts. When set to 0, Counter 1-4 fields represent octet counts. When set to 0, it
indicates that the Counter 1-4 fields represent packet counts. By indicates that the Counter 1-4 fields represent packet counts. By
default it is set to 0. default, it is set to 0.
Reserved: Reserved for future specification and set to 0 on Reserved: Reserved for future specifications; set to 0 on
transmission and ignored when received. transmission and ignored when received.
Measurement Interval: the time interval (in milliseconds) at which Measurement Interval: The time interval (in milliseconds) at which
Loss Measurement query messages MUST be sent on both directions. If Loss Measurement query messages MUST be sent in both directions. If
the egress LSR cannot support the value, it SHOULD reply with a the egress LSR cannot support the value, it SHOULD reply with a
supported interval. By default it is set to (100) as per [RFC6375]. supported interval. By default, it is set to 100 milliseconds as per
[RFC6375].
Test Interval: test messages interval in milliseconds as described in Test Interval: Test messages interval (in milliseconds) as described
[RFC6374]. By default it is set to (10) as per [RFC6375]. If the in [RFC6374]. By default, it is set to 10 milliseconds as per
egress LSR cannot support the value, it SHOULD reply with a supported [RFC6375]. If the egress LSR cannot support the value, it SHOULD
interval. reply with a supported interval.
Loss Threshold: the threshold value of measured lost packets per Loss Threshold: The threshold value of measured lost packets per
measurement over which action(s) SHOULD be triggered. measurement over which action(s) SHOULD be triggered.
3.4.2. MPLS OAM PM Delay sub-TLV 3.4.2. MPLS OAM PM Delay Sub-TLV
The "MPLS OAM PM Delay sub-TLV" depicted below is carried as a sub- The MPLS OAM PM Delay Sub-TLV depicted below is carried as a sub-TLV
TLV of the "Performance Monitoring sub-TLV". of the Performance Monitoring Sub-TLV.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PM Delay Type (2) | Length | | PM Delay Type (2) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OTF |T|B| Reserved (set to all 0s) | | OTF |T|B| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Interval | | Measurement Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Test Interval | | Test Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delay Threshold | | Delay Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 2,"MPLS OAM PM Delay sub-TLV". Figure 9: MPLS OAM PM Delay Sub-TLV Format
Length: indicates the length of the parameters in octets, including Type: 2, the MPLS OAM PM Delay Sub-TLV.
Length: Indicates the length of the parameters in octets, including
Type and Length fields (20). Type and Length fields (20).
OTF: Origin Timestamp Format of the Origin Timestamp field described OTF: Origin Timestamp Format of the Origin Timestamp field described
in [RFC6374]. By default it is set to IEEE 1588 version 1. If the in [RFC6374]. By default, it is set to IEEE 1588 version 1. If the
egress LSR cannot support this value an "OAM Problem/Unsupported egress LSR cannot support this value, an "OAM Problem/Unsupported
Timestamp Format" error MUST be generated. Timestamp Format" error MUST be generated.
Configuration Flags, please refer to [RFC6374] for further details: Configuration Flags (please refer to [RFC6374] for further details):
- T: Traffic-class-specific measurement indicator. Set to 1 when o T: Traffic-class-specific measurement indicator. Set to 1 when
the measurement operation is scoped to packets of a particular the measurement operation is scoped to packets of a particular
traffic class (DSCP value), and 0 otherwise. When set to 1, the traffic class (Differentiated Services Code Point (DSCP) value)
DS field of the message indicates the measured traffic class. By and zero otherwise. When set to 1, the Differentiated Service
default it is set to 1. (DS) field of the message indicates the measured traffic class.
By default, it is set to 1.
- B: Octet (byte) count. When set to 1, indicates that the o B: Octet (byte) count. When set to 1, it indicates that the
Counter 1-4 fields represent octet counts. When set to 0, Counter 1-4 fields represent octet counts. When set to 0, it
indicates that the Counter 1-4 fields represent packet counts. By indicates that the Counter 1-4 fields represent packet counts. By
default it is set to 0. default, it is set to 0.
Reserved: Reserved for future specification and set to 0 on Reserved: Reserved for future specifications; set to 0 on
transmission and ignored when received. transmission and ignored when received.
Measurement Interval: the time interval (in milliseconds) at which Measurement Interval: The time interval (in milliseconds) at which
Delay Measurement query messages MUST be sent on both directions. If Delay Measurement query messages MUST be sent on both directions. If
the egress LSR cannot support the value, it SHOULD reply with a the egress LSR cannot support the value, it SHOULD reply with a
supported interval. By default it is set to (1000) as per [RFC6375]. supported interval. By default, it is set to 1000 milliseconds as
per [RFC6375].
Test Interval: test messages interval (in milliseconds) as described Test Interval: Test messages interval (in milliseconds) as described
in [RFC6374]. By default it is set to (10) as per [RFC6375]. If the in [RFC6374]. By default, it is set to 10 milliseconds as per
egress LSR cannot support the value, it SHOULD reply with a supported [RFC6375]. If the egress LSR cannot support the value, it SHOULD
interval. reply with a supported interval.
Delay Threshold: the threshold value of measured two-way delay (in Delay Threshold: The threshold value of measured two-way delay (in
milliseconds) over which action(s) SHOULD be triggered. milliseconds) over which action(s) SHOULD be triggered.
3.5. MPLS OAM FMS sub-TLV 3.5. MPLS OAM FMS Sub-TLV
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
protection paths are signaled, both LSPs SHOULD be signaled with paths are signaled, both LSPs SHOULD be signaled with identical
identical settings of the E flag, T flag, and the refresh timer. 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 | Refresh Timer | |E|S|T| Reserved | Refresh Timer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ sub-TLVs ~ ~ Sub-TLVs ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 3, "MPLS OAM FMS sub-TLV". Figure 10: MPLS OAM FMS Sub-TLV Format
Length: indicates the TLV total length in octets, including Type and Type: 3, the MPLS OAM FMS Sub-TLV.
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 MEPs and the
and the Server MEPs of the links over which the LSP is forwarded. In server MEPs of the links over which the LSP is forwarded. In this
this document only the S flag pertains to Server MEPs. 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)
signaling as described in [RFC6427]. Default value is 1 signaling as described in [RFC6427]. The 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
error MUST be generated. unsupported" error MUST be generated.
- S: Indicate to a Server MEP that it 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. The 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
reason unable to do so for the LSP being signaled an "OAM Problem/ some reason unable to do so for the LSP being signaled an "OAM
Unable to create fault management association" error MUST be Problem/Unable to create fault management association" error MUST
generated. be generated.
- T: Set timer value, enabled the configuration of a specific T: Set timer value, enabled by the configuration of a specific
timer value. Default value is 0 (disabled). timer value. The Default value is 0 (disabled).
- Remaining bits: Reserved for future specification and set to 0. Remaining bits: Reserved for a future specification and set to 0.
Refresh Timer: indicates the refresh timer of fault indication Refresh Timer: Indicates (in seconds) the refresh timer of fault
messages, in seconds. The value MUST be between 1 to 20 seconds as indication messages. 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.
FMS sub-TLV MAY include Traffic Class sub-TLV Section 3.3.4. If TC The Fault Management Signals Sub-TLV MAY include the Traffic Class
sub-TLV is present, the value of the TC field MUST be used as the Sub-TLV (Section 3.3.4.) If the Traffic Class Sub-TLV is present,
value of the TC field of an MPLS label stack entry for FMS messages. the value of the TC field MUST be used as the value of the TC field
If the TC sub-TLV is absent, then selection of the TC value is local of an MPLS label stack entry for FMS messages. If the Traffic Class
decision. 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 o 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 o If an egress LSR does not support the specified BFD Encapsulation
Encapsulation format, an error MUST be generated: "OAM Problem/ format, an error MUST be generated: "OAM Problem/Unsupported BFD
Unsupported BFD Encapsulation format". Encapsulation format".
- If an egress LSR does not support BFD Authentication, and it is o If an egress LSR does not support BFD Authentication and it is
requested, an error MUST be generated: "OAM Problem/BFD requested, an error MUST be generated: "OAM Problem/BFD
Authentication unsupported". Authentication unsupported".
- If an egress LSR does not support the specified BFD o If an egress LSR does not support the specified BFD Authentication
Authentication Type, an error MUST be generated: "OAM Problem/ Type, an error MUST be generated: "OAM Problem/Unsupported BFD
Unsupported BFD Authentication Type". Authentication Type".
- If an egress LSR is not able to use the specified Authentication o If an egress LSR is not able to use the specified Authentication
Key ID, an error MUST be generated: "OAM Problem/Mismatch of BFD Key ID, an error MUST be generated: "OAM Problem/Mismatch of BFD
Authentication Key ID". Authentication Key ID".
- If an egress LSR does not support the specified Timestamp o If an egress LSR does not support the specified Timestamp Format,
Format, an error MUST be generated: "OAM Problem/Unsupported an error MUST be generated: "OAM Problem/Unsupported Timestamp
Timestamp Format". Format".
- If an egress LSR does not support specified Delay mode, an "OAM o If an egress LSR does not support the specified Delay mode, an
Problem/Unsupported Delay Mode" error MUST be generated. "OAM Problem/Unsupported Delay Mode" error MUST be generated.
- If an egress LSR does not support specified Loss mode, an "OAM o If an egress LSR does not support the specified Loss mode, an "OAM
Problem/Unsupported Loss Mode" error MUST be generated. Problem/Unsupported Loss Mode" error MUST be generated.
- If an egress LSR does not support Delay variation measurements, o If an egress LSR does not support Delay variation measurements and
and it is requested, an "OAM Problem/Delay variation unsupported" it is requested, an "OAM Problem/Delay variation unsupported"
error MUST be generated. error MUST be generated.
- If an egress LSR does not support Dyadic mode, and it is o If an egress LSR does not support Dyadic mode and it is requested,
requested, an "OAM Problem/Dyadic mode unsupported" error MUST be an "OAM Problem/Dyadic mode unsupported" error MUST be generated.
generated.
- If an egress LSR does not support Loopback mode, and it is o If an egress LSR does not support Loopback mode and it is
requested, an "OAM Problem/Loopback mode unsupported" error MUST requested, an "OAM Problem/Loopback mode unsupported" error MUST
be generated. be generated.
- If an egress LSR does not support Combined mode, and it is o If an egress LSR does not support Combined mode and it is
requested, an "OAM Problem/Combined mode unsupported" error MUST requested, an "OAM Problem/Combined mode unsupported" error MUST
be generated. be generated.
- If an egress LSR does not support Fault Monitoring Signals, and o If an egress LSR does not support Fault Monitoring signals and it
it is requested, an "OAM Problem/Fault management signaling is requested, an "OAM Problem/Fault management signaling
unsupported" error MUST be generated. unsupported" error MUST be generated.
- If an intermediate server MEP supports Fault Monitoring Signals o If an intermediate server MEP supports Fault Monitoring signals
but is unable to create an association, when requested to do so, but is unable to create an association when requested to do so, an
an "OAM Problem/Unable to create fault management association" "OAM Problem/Unable to create fault management association" error
error MUST be generated. MUST be generated.
5. IANA Considerations 5. IANA Considerations
5.1. MPLS OAM Type 5.1. MPLS OAM Type
This document specifies new the "MPLS OAM Type". IANA is requested This document specifies the new MPLS OAM type. IANA has allocated a
to allocate a new type (TBA1) from the OAM Type space of the RSVP-TE new type (3) from the "OAM Types" space of the "RSVP-TE OAM
OAM Configuration Registry. Configuration Registry".
+------+-------------+---------------+ +------+-------------+-----------+
| Type | Description | Reference | | Type | Description | Reference |
+------+-------------+---------------+ +------+-------------+-----------+
| TBA1 | MPLS OAM | This document | | 3 | MPLS OAM | [RFC7487] |
+------+-------------+---------------+ +------+-------------+-----------+
Table 1: OAM MPLS Type Table 1: MPLS OAM Type
5.2. MPLS OAM Configuration sub-TLV 5.2. MPLS OAM Configuration Sub-TLV
This document specifies the "MPLS OAM Configuration sub-TLV", IANA is This document specifies the MPLS OAM Configuration Sub-TLV. IANA has
requested to allocate a new type (TBA2) from the technology-specific allocated a new type (33) from the OAM Sub-TLV space of the "RSVP-TE
sub-TLV space of the RSVP-TE OAM Configuration Registry. OAM Configuration Registry".
+------+--------------------------------+---------------+ +------+--------------------------------+-----------+
| Type | Description | Reference | | Type | Description | Reference |
+------+--------------------------------+---------------+ +------+--------------------------------+-----------+
| TBA2 | MPLS OAM Configuration sub-TLV | This document | | 33 | MPLS OAM Configuration Sub-TLV | [RFC7487] |
+------+--------------------------------+---------------+ +------+--------------------------------+-----------+
Table 2: MPLS OAM Configuration sub-TLV Type Table 2: MPLS OAM Configuration Sub-TLV Type
5.3. MPLS OAM Configuration Sub-TLV Types 5.3. MPLS OAM Configuration Sub-TLV Types
IANA is requested to create an "MPLS OAM sub-TLV Types" sub-registry IANA has created an "MPLS OAM Configuration Sub-TLV Types" sub-
in the "RSVP-TE OAM Configuration Registry" for the sub-TLVs carried registry in the "RSVP-TE OAM Configuration Registry" for the sub-TLVs
in the "MPLS OAM Configuration sub-TLV". Values from this new sub- carried in the MPLS OAM Configuration Sub-TLV. Values from this new
registry to be allocated through IETF Review except for the Reserved sub-registry are to be allocated through IETF Review except for the
for Experimental Use range. This document defines the following "Reserved for Experimental Use" range. This document defines the
types: following types:
+-------------+--------------------------------+---------------+ +-------------+--------------------------------+-----------+
| Type | Description | Reference | | Type | Description | Reference |
+-------------+--------------------------------+---------------+ +-------------+--------------------------------+-----------+
| 0 | Reserved | This document | | 0 | Reserved | [RFC7487] |
| 1 | BFD Configuration sub-TLV | This document | | 1 | BFD Configuration Sub-TLV | [RFC7487] |
| 2 | Performance Monitoring sub-TLV | This document | | 2 | Performance Monitoring Sub-TLV | [RFC7487] |
| 3 | MPLS OAM FMS sub-TLV | This document | | 3 | MPLS OAM FMS Sub-TLV | [RFC7487] |
| 4-65532 | Unassigned | | | 4-65532 | Unassigned | |
| 65533-65534 | Reserved for Experimental Use | This document | | 65533-65534 | Reserved for Experimental Use | [RFC7487] |
| 65535 | Reserved | This document | | 65535 | Reserved | [RFC7487] |
+-------------+--------------------------------+---------------+ +-------------+--------------------------------+-----------+
Table 3: MPLS OAM Configuration sub-TLV Types Table 3: MPLS OAM Configuration Sub-TLV Types
5.4. BFD Configuration Sub-TLV Types 5.4. BFD Configuration Sub-TLV Types
IANA is requested to create a "BFD Configuration sub-TLV Types" sub- IANA has created a "BFD Configuration Sub-TLV Types" sub-registry in
registry in the "RSVP-TE OAM Configuration Registry" for the sub-TLV the "RSVP-TE OAM Configuration Registry" for the sub-TLV types
types carried in the "BFD Configuration sub-TLV". Values from this carried in the BFD Configuration Sub-TLV. Values from this new sub-
new sub-registry to be allocated through IETF Review except for the registry are to be allocated through IETF Review except for the
Reserved for Experimental Use range. This document defines the "Reserved for Experimental Use" range. This document defines the
following types: following types:
+-------------+-------------------------------------+---------------+ +-------------+--------------------------------------+-----------+
| Type | Description | Reference | | Type | Description | Reference |
+-------------+-------------------------------------+---------------+ +-------------+--------------------------------------+-----------+
| 0 | Reserved | This document | | 0 | Reserved | [RFC7487] |
| 1 | BFD Identifiers sub-TLV | This document | | 1 | BFD Identifiers Sub-TLV | [RFC7487] |
| 2 | Negotiation Timer Parameters sub- | This document | | 2 | Negotiation Timer Parameters Sub-TLV | [RFC7487] |
| | TLV | | | 3 | BFD Authentication Sub-TLV | [RFC7487] |
| 3 | BFD Authentication sub-TLV | This document | | 4 | Traffic Class Sub-TLV | [RFC7487] |
| 4 | Traffic Class sub-TLV | This document | | 5-65532 | Unassigned | |
| 5-65532 | Unassigned | | | 65533-65534 | Reserved for Experimental Use | [RFC7487] |
| 65533-65534 | Reserved for Experimental Use | This document | | 65535 | Reserved | [RFC7487] |
| 65535 | Reserved | This document | +-------------+--------------------------------------+-----------+
+-------------+-------------------------------------+---------------+
Table 4: BFD Configuration Sus-TLV Types Table 4: BFD Configuration Sub-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 has created a "Performance Monitoring Sub-TLV Type" sub-registry
sub-registry in the "RSVP-TE OAM Configuration Registry" for the sub- in the "RSVP-TE OAM Configuration Registry" for the sub-TLV types
TLV types carried in the "Performance Monitoring sub-TLV". Values carried in the Performance Monitoring Sub-TLV. Values from this new
from this new sub-registry to be allocated through IETF Review except sub-registry are to be allocated through IETF Review except for the
for the Reserved for Experimental Use range. This document defines "Reserved for Experimental Use" range. This document defines the
the following types: following types:
+-------------+-------------------------------+---------------+ +-------------+-------------------------------+-----------+
| Type | Description | Reference | | Type | Description | Reference |
+-------------+-------------------------------+---------------+ +-------------+-------------------------------+-----------+
| 0 | Reserved | This document | | 0 | Reserved | [RFC7487] |
| 1 | MPLS OAM PM Loss sub-TLV | This document | | 1 | MPLS OAM PM Loss Sub-TLV | [RFC7487] |
| 2 | MPLS OAM PM Delay sub-TLV | This document | | 2 | MPLS OAM PM Delay Sub-TLV | [RFC7487] |
| 3-65532 | Unassigned | | | 3-65532 | Unassigned | |
| 65533-65534 | Reserved for Experimental Use | This document | | 65533-65534 | Reserved for Experimental Use | [RFC7487] |
| 65535 | Reserved | This document | | 65535 | Reserved | [RFC7487] |
+-------------+-------------------------------+---------------+ +-------------+-------------------------------+-----------+
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 have been assigned under the "OAM Problem" error
Error Code [RFC7260] by IETF Review process: code [RFC7260] by IETF Review process:
+-----------------+---------------------------------+---------------+ +------------------+------------------------------------+-----------+
| Error Value | Description | Reference | | Error Value Sub- | Description | Reference |
| Sub-codes | | | | Codes | | |
+-----------------+---------------------------------+---------------+ +------------------+------------------------------------+-----------+
| TBA3 | Unsupported BFD Version | This document | | 13 | Unsupported BFD Version | [RFC7487] |
| TBA4 | Unsupported BFD Encapsulation | This document | | 14 | Unsupported BFD Encapsulation | [RFC7487] |
| | format | | | | format | |
| TBA5 | Unsupported BFD Authentication | This document | | 15 | Unsupported BFD Authentication | [RFC7487] |
| | Type | | | | Type | |
| TBA6 | Mismatch of BFD Authentication | This document | | 16 | Mismatch of BFD Authentication Key | [RFC7487] |
| | Key ID | | | | ID | |
| TBA7 | Unsupported Timestamp Format | This document | | 17 | Unsupported Timestamp Format | [RFC7487] |
| TBA8 | Unsupported Delay Mode | This document | | 18 | Unsupported Delay Mode | [RFC7487] |
| TBA9 | Unsupported Loss Mode | This document | | 19 | Unsupported Loss Mode | [RFC7487] |
| TBA10 | Delay variation unsupported | This document | | 20 | Delay variation unsupported | [RFC7487] |
| TBA11 | Dyadic mode unsupported | This document | | 21 | Dyadic mode unsupported | [RFC7487] |
| TBA12 | Loopback mode unsupported | This document | | 22 | Loopback mode unsupported | [RFC7487] |
| TBA13 | Combined mode unsupported | This document | | 23 | Combined mode unsupported | [RFC7487] |
| TBA14 | Fault management signaling | This document | | 24 | Fault management signaling | [RFC7487] |
| | unsupported | | | | unsupported | |
| TBA15 | Unable to create fault | This document | | 25 | Unable to create fault management | [RFC7487] |
| | management association | | | | 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 The "Sub-Codes - 40 OAM Problem" sub-registry is located in the
"Error Codes and Globally-Defined Error Value Sub-Codes" registry. "Error Codes and Globally-Defined Error Value Sub-Codes" registry.
6. Contributing Authors 6. Security Considerations
This document is the result of a large team of authors and
contributors. The following is a list of the co-authors:
John Drake
Benoit Tremblay
7. Acknowledgements
The authors would like to thank David Allan, Lou Berger, Annamaria
Fulignoli, Eric Gray, Andras Kern, David Jocha and David Sinicrope
for their useful comments.
8. Security Considerations
The signaling of OAM related parameters and the automatic The signaling of OAM-related parameters and the automatic
establishment of OAM entities introduces additional security establishment of OAM entities introduces additional security
considerations to those discussed in [RFC3473]. In particular, a considerations to those discussed in [RFC3473]. In particular, a
network element could be overloaded if an attacker were to request network element could be overloaded if an attacker were to request
high frequency liveliness monitoring of a large number of LSPs, high frequency liveliness monitoring of a large number of LSPs,
targeting a single network element as discussed in [RFC7260] and targeting a single network element as discussed in [RFC7260] and
[RFC6060]. [RFC6060].
Additional discussion of security for MPLS and GMPLS protocols can be Additional discussion of security for MPLS and GMPLS protocols can be
found in [RFC5920]. found in [RFC5920].
9. References 7. References
9.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3473] Berger, L., Ed., "Generalized Multi-Protocol Label
(GMPLS) Signaling Resource ReserVation Protocol-Traffic Switching (GMPLS) Signaling Resource ReserVation Protocol-
Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. Traffic Engineering (RSVP-TE) Extensions", RFC 3473,
January 2003, <http://www.rfc-editor.org/info/rfc3473>.
[RFC5654] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed.,
and S. Ueno, "Requirements of an MPLS Transport Profile", Sprecher, N., and S. Ueno, "Requirements of an MPLS
RFC 5654, September 2009. Transport Profile", RFC 5654, September 2009,
<http://www.rfc-editor.org/info/rfc5654>.
[RFC5860] Vigoureux, M., Ward, D., and M. Betts, "Requirements for [RFC5860] Vigoureux, M., Ed., Ward, D., Ed., and M. Betts, Ed.,
Operations, Administration, and Maintenance (OAM) in MPLS "Requirements for Operations, Administration, and
Transport Networks", RFC 5860, May 2010. Maintenance (OAM) in MPLS Transport Networks", RFC 5860,
May 2010, <http://www.rfc-editor.org/info/rfc5860>.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, June 2010. (BFD)", RFC 5880, June 2010,
<http://www.rfc-editor.org/info/rfc5880>.
[RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, [RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow,
"Bidirectional Forwarding Detection (BFD) for MPLS Label "Bidirectional Forwarding Detection (BFD) for MPLS Label
Switched Paths (LSPs)", RFC 5884, June 2010. Switched Paths (LSPs)", RFC 5884, June 2010,
<http://www.rfc-editor.org/info/rfc5884>.
[RFC6060] Fedyk, D., Shah, H., Bitar, N., and A. Takacs, [RFC6060] Fedyk, D., Shah, H., Bitar, N., and A. Takacs,
"Generalized Multiprotocol Label Switching (GMPLS) Control "Generalized Multiprotocol Label Switching (GMPLS) Control
of Ethernet Provider Backbone Traffic Engineering (PBB- of Ethernet Provider Backbone Traffic Engineering (PBB-
TE)", RFC 6060, March 2011. TE)", RFC 6060, March 2011,
<http://www.rfc-editor.org/info/rfc6060>.
[RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport
Profile (MPLS-TP) Identifiers", RFC 6370, September 2011. Profile (MPLS-TP) Identifiers", RFC 6370, September 2011,
<http://www.rfc-editor.org/info/rfc6370>.
[RFC6374] Frost, D. and S. Bryant, "Packet Loss and Delay [RFC6374] Frost, D. and S. Bryant, "Packet Loss and Delay
Measurement for MPLS Networks", RFC 6374, September 2011. Measurement for MPLS Networks", RFC 6374, September 2011,
<http://www.rfc-editor.org/info/rfc6374>.
[RFC6427] Swallow, G., Fulignoli, A., Vigoureux, M., Boutros, S., [RFC6427] Swallow, G., Ed., Fulignoli, A., Ed., Vigoureux, M., Ed.,
and D. Ward, "MPLS Fault Management Operations, Boutros, S., and D. Ward, "MPLS Fault Management
Administration, and Maintenance (OAM)", RFC 6427, November Operations, Administration, and Maintenance (OAM)", RFC
2011. 6427, November 2011,
<http://www.rfc-editor.org/info/rfc6427>.
[RFC6428] Allan, D., Swallow Ed. , G., and J. Drake Ed. , "Proactive [RFC6428] Allan, D., Ed., Swallow Ed., G., and J. Drake Ed.,
Connectivity Verification, Continuity Check, and Remote "Proactive Connectivity Verification, Continuity Check,
Defect Indication for the MPLS Transport Profile", RFC and Remote Defect Indication for the MPLS Transport
6428, November 2011. Profile", RFC 6428, November 2011,
<http://www.rfc-editor.org/info/rfc6428>.
[RFC7260] Takacs, A., Fedyk, D., and J. He, "GMPLS RSVP-TE [RFC7260] Takacs, A., Fedyk, D., and J. He, "GMPLS RSVP-TE
Extensions for Operations, Administration, and Maintenance Extensions for Operations, Administration, and Maintenance
(OAM) Configuration", RFC 7260, June 2014. (OAM) Configuration", RFC 7260, June 2014,
<http://www.rfc-editor.org/info/rfc7260>.
9.2. Informative References 7.2. Informative References
[LSP-PING-CONF] [LSP-PING-CONF]
Bellagamba, E., Andersson, L., Ward, D., Drake, J., and P. Bellagamba, E., Mirsky, G., Andersson, L., Skoldstrom, P.,
Skoldstrom, "Configuration of proactive MPLS-TP Ward, D., and J. Drake, "Configuration of Proactive
Operations, Administration, and Maintenance (OAM) Operations, Administration, and Maintenance (OAM)
Functions Using LSP Ping", 2014, <draft-ietf-mpls-lsp- Functions for MPLS-based Transport Networks using LSP
ping-mpls-tp-oam-conf>. Ping", Work in Progress, draft-ietf-mpls-lsp-ping-mpls-tp-
oam-conf-09, January 2015.
[RFC5462] Andersson, L. and R. Asati, "Multiprotocol Label Switching [RFC5462] Andersson, L. and R. Asati, "Multiprotocol Label Switching
(MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic
Class" Field", RFC 5462, February 2009. Class" Field", RFC 5462, February 2009,
<http://www.rfc-editor.org/info/rfc5462>.
[RFC5920] Fang, L., "Security Framework for MPLS and GMPLS [RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS
Networks", RFC 5920, July 2010. Networks", RFC 5920, July 2010,
<http://www.rfc-editor.org/info/rfc5920>.
[RFC6371] Busi, I. and D. Allan, "Operations, Administration, and [RFC6371] Busi, I., Ed. and D. Allan, Ed., "Operations,
Maintenance Framework for MPLS-Based Transport Networks", Administration, and Maintenance Framework for MPLS-Based
RFC 6371, September 2011. Transport Networks", RFC 6371, September 2011,
<http://www.rfc-editor.org/info/rfc6371>.
[RFC6375] Frost, D. and S. Bryant, "A Packet Loss and Delay [RFC6375] Frost, D., Ed. and S. Bryant, Ed., "A Packet Loss and
Measurement Profile for MPLS-Based Transport Networks", Delay Measurement Profile for MPLS-Based Transport
RFC 6375, September 2011. Networks", RFC 6375, September 2011,
<http://www.rfc-editor.org/info/rfc6375>.
Acknowledgements
The authors would like to thank David Allan, Lou Berger, Annamaria
Fulignoli, Eric Gray, Andras Kern, David Jocha, and David Sinicrope
for their useful comments.
Contributors
This document is the result of a large team of authors and
contributors. The following is a list of the contributors:
John Drake
Benoit Tremblay
Authors' Addresses Authors' Addresses
Elisa Bellagamba Elisa Bellagamba
Ericsson Ericsson
Email: elisa.bellagamba@ericsson.com EMail: elisa.bellagamba@ericsson.com
Attila Takacs Attila Takacs
Ericsson Ericsson
Email: attila.takacs@ericsson.com EMail: attila.takacs@ericsson.com
Gregory Mirsky Gregory Mirsky
Ericsson Ericsson
Email: Gregory.Mirsky@ericsson.com EMail: Gregory.Mirsky@ericsson.com
Loa Andersson Loa Andersson
Huawei Technologies Huawei Technologies
Email: loa@mail01.huawei.com EMail: loa@mail01.huawei.com
Pontus Skoldstrom 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
 End of changes. 257 change blocks. 
643 lines changed or deleted 682 lines changed or added

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