draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-12.txt   draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-13.txt 
CCAMP Working Group E. Bellagamba, Ed. CCAMP Working Group E. Bellagamba, Ed.
Internet-Draft L. Andersson, Ed. Internet-Draft G. Mirsky, Ed.
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: December 22, 2013 P. Skoldstrom, Ed. Expires: June 3, 2015 L. Andersson, Ed.
Huawei Technologies Co.
P. Skoldstrom, Ed.
Acreo AB Acreo AB
D. Ward D. Ward
Cisco Cisco
A. Takacs A. Takacs
Ericsson Ericsson
June 20, 2013 November 30, 2014
Configuration of Pro-Active Operations, Administration, and Maintenance Configuration of Pro-Active Operations, Administration, and Maintenance
(OAM) Functions for MPLS-based Transport Networks using RSVP-TE (OAM) Functions for MPLS-based Transport Networks using RSVP-TE
draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-12 draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-13
Abstract Abstract
This specification describes the configuration of pro-active MPLS-TP This specification describes the configuration of pro-active MPLS-TP
(MPLS-Transport Profile) Operations, Administration, and Maintenance (MPLS-Transport Profile) Operations, Administration, and Maintenance
(OAM) Functions for a given LSP using a set of TLVs that are carried (OAM) Functions for a given LSP using a set of TLVs that are carried
by the GMPLS RSVP-TE protocol based on [OAM-CONF-FWK]. by the GMPLS RSVP-TE protocol based on the OAM Configuration
Framework for GMPLS RSVP-TE.
This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 22, 2013. This Internet-Draft will expire on June 3, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
Copyright (c) 2014 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 . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Contributing Authors . . . . . . . . . . . . . . . . . . 4 1.1. Conventions used in this document . . . . . . . . . . . . 4
1.2. Requirements Language . . . . . . . . . . . . . . . . . . 4 1.1.1. Terminology . . . . . . . . . . . . . . . . . . . . . 4
2. Overview of MPLS OAM for Transport Applications . . . . . . . 4 1.1.2. Requirements Language . . . . . . . . . . . . . . . . 5
2. Overview of MPLS OAM for Transport Applications . . . . . . . 5
3. Theory of Operations . . . . . . . . . . . . . . . . . . . . 5 3. Theory of Operations . . . . . . . . . . . . . . . . . . . . 5
3.1. MPLS-TP OAM Configuration Operation Overview . . . . . . 5 3.1. MPLS-TP OAM Configuration Operation Overview . . . . . . 5
3.1.1. Configuration of BFD sessions . . . . . . . . . . . . 5 3.1.1. Configuration of BFD sessions . . . . . . . . . . . . 6
3.1.2. Configuration of Performance Monitoring . . . . . . . 6 3.1.2. Configuration of Performance Monitoring . . . . . . . 7
3.1.3. Configuration of Fault Management Signals . . . . . . 7 3.1.3. Configuration of Fault Management Signals . . . . . . 7
3.2. MPLS OAM Configuration sub-TLV . . . . . . . . . . . . . 7 3.2. MPLS OAM Configuration sub-TLV . . . . . . . . . . . . . 8
3.3. BFD Configuration sub-TLV . . . . . . . . . . . . . . . . 9 3.2.1. CV Flag Rules of Use . . . . . . . . . . . . . . . . 10
3.3.1. BFD Identifiers sub-TLV . . . . . . . . . . . . . . . 11 3.3. BFD Configuration sub-TLV . . . . . . . . . . . . . . . . 10
3.3.2. Negotiation Timer Parameters sub-TLV . . . . . . . . 12 3.3.1. BFD Identifiers sub-TLV . . . . . . . . . . . . . . . 12
3.3.3. BFD Authentication sub-TLV . . . . . . . . . . . . . 13 3.3.2. Negotiation Timer Parameters sub-TLV . . . . . . . . 13
3.4. Performance Monitoring sub-TLV . . . . . . . . . . . . . 14 3.3.3. BFD Authentication sub-TLV . . . . . . . . . . . . . 14
3.4.1. MPLS OAM PM Loss sub-TLV . . . . . . . . . . . . . . 15 3.4. Performance Monitoring sub-TLV . . . . . . . . . . . . . 15
3.4.2. MPLS OAM PM Delay sub-TLV . . . . . . . . . . . . . . 16 3.4.1. MPLS OAM PM Loss sub-TLV . . . . . . . . . . . . . . 16
3.5. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . . 18 3.4.2. MPLS OAM PM Delay sub-TLV . . . . . . . . . . . . . . 18
4. Summary of MPLS OAM configuration errors . . . . . . . . . . 19 3.5. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . . 19
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 4. Summary of MPLS OAM configuration errors . . . . . . . . . . 20
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
7. Security Considerations . . . . . . . . . . . . . . . . . . . 22 5.1. MPLS OAM Type . . . . . . . . . . . . . . . . . . . . . . 21
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.2. MPLS OAM Configuration sub-TLV . . . . . . . . . . . . . 22
8.1. Normative References . . . . . . . . . . . . . . . . . . 22 5.3. MPLS OAM Configuration Sub-TLV Types . . . . . . . . . . 22
8.2. Informative References . . . . . . . . . . . . . . . . . 23 5.4. BFD Configuration Sub-TLV Types . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 5.5. Performance Monitoring sub-TLV Types . . . . . . . . . . 23
5.6. New RSVP-TE error codes . . . . . . . . . . . . . . . . . 23
6. Contributing Authors . . . . . . . . . . . . . . . . . . . . 24
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24
8. Security Considerations . . . . . . . . . . . . . . . . . . . 24
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
9.1. Normative References . . . . . . . . . . . . . . . . . . 25
9.2. Informative References . . . . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27
1. Introduction 1. Introduction
This document describes the configuration of pro-active MPLS-TP This document describes the configuration of pro-active MPLS-TP
(MPLS-Transport Profile) Operations, Administration, and Maintenance (MPLS-Transport Profile) Operations, Administration, and Maintenance
(OAM) Functions for a given LSP using TLVs using GMPLS RSVP-TE (OAM) Functions for a given LSP using TLVs using GMPLS RSVP-TE
[RFC3473]. The use of GMPLS RSVP-TE for the configuration of OAM [RFC3473]. The use of GMPLS RSVP-TE for the configuration of OAM
functions is defined in a technology agnostic way in [OAM-CONF-FWK]. functions is defined in a technology agnostic way in [RFC7260]. This
This document specifies the additional mechanisms necessary to document specifies the additional mechanisms necessary to establish
establish MPLS-TP OAM entities at the maintenance points for MPLS-TP OAM entities at the maintenance points for monitoring and
monitoring and performing measurements on an LSP, as well as defining performing measurements on an LSP, as well as defining information
information elements and procedures to configure pro-active MPLS-TP elements and procedures to configure pro-active MPLS-TP OAM functions
OAM functions running between LERs. Initialization and control of running between LERs. Initialization and control of on-demand MPLS-
on-demand MPLS-TP OAM functions are expected to be carried out by TP OAM functions are expected to be carried out by directly accessing
directly accessing network nodes via a management interface; hence network nodes via a management interface; hence configuration and
configuration and control of on-demand OAM functions are out-of-scope control of on-demand OAM functions are out-of-scope for this
for this document. 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 either using an NMS or LSP Ping, or with a
control plane using signaling protocols such as RSVP-TE. control plane using signaling protocols such as RSVP-TE.
Pro-active MPLS-TP OAM is performed by four different protocols, Bi- MPLS-TP describes a profile of MPLS that enables operational models
directional Forwarding Detection (BFD) [RFC6428] for Continuity Check typical in transport networks, while providing additional OAM,
/Connectivity Verification, the delay measurement protocol (DM) survivability and other maintenance functions not currently supported
by MPLS. [RFC5860] defines the requirements for the OAM
functionality of MPLS-TP.
Pro-active MPLS-TP OAM is performed by three different protocols, Bi-
directional Forwarding Detection (BFD) [RFC6428] for Continuity
Check/Connectivity Verification, the delay measurement protocol (DM)
[RFC6374] for delay and delay variation (jitter) measurements, and [RFC6374] for delay and delay variation (jitter) measurements, and
the loss measurement protocol (LM) [RFC6374] for packet loss and the loss measurement protocol (LM) [RFC6374] for packet loss and
throughput measurements. Additionally there is a number of Fault throughput measurements. Additionally there is a number of Fault
Management Signals that can be configured. Management Signals that can be configured.
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
detect data plane failures of MPLS-TP point-to-point and might also detect data plane failures of MPLS-TP point-to-point and might also
skipping to change at page 4, line 5 skipping to change at page 4, line 17
can be calculated. Current throughput can be calculated from the can be calculated. Current throughput can be calculated from the
packet loss measurements by dividing the number of packets sent/ packet loss measurements by dividing the number of packets sent/
received with the time it took to perform the measurement, given by received with the time it took to perform the measurement, given by
the timestamp in LM header. Combined with a packet generator the 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.
MPLS-TP describes a profile of MPLS that enables operational models 1.1. Conventions used in this document
typical in transport networks, while providing additional OAM,
survivability and other maintenance functions not currently supported
by MPLS. [RFC5860] defines the requirements for the OAM
functionality of MPLS-TP.
This document is a product of a joint Internet Engineering Task Force 1.1.1. Terminology
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network.
1.1. Contributing Authors BFD - Bidirectional Forwarding Detection
This document is the result of a large team of authors and CV - Connectivity Verification
contributors. The following is a list of the co-authors:
Gregory Mirsky CC - Continuity Check
John Drake DM - Delay Measurement
Benoit Tremblay FMS - Fault Management Signal
1.2. Requirements Language G-ACh - Generic Associated Channel
GMPLS - Generalized Multi-Protocol Label Switching
LER - Label switching Edge Router
LM - Loss Measurement
LSP - Label Switched Path
LSR - Label Switching Router
MEP - Maintanence Entity Group End Point
MPLS - Multi-Protocol Label Switching
MPLS-TP - MPLS Transport Profile
NMS - Network Management System
PM - Performance Measurement
RSVP-TE - Reservation Protocol Traffic Engineering
1.1.2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. Overview of MPLS OAM for Transport Applications 2. Overview of MPLS OAM for Transport Applications
[RFC6371] describes how MPLS-TP OAM mechanisms are operated to meet [RFC6371] describes how MPLS-TP OAM mechanisms are operated to meet
transport requirements outlined in [RFC5860]. transport requirements outlined in [RFC5860].
[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, 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 as well as Continuity Check. supporting Connectivity Verification (CV) as well as Continuity Check
(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).
skipping to change at page 5, line 21 skipping to change at page 5, line 49
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" [OAM-CONF- corresponding flags in the "OAM Function Flags sub-TLV" [RFC7260].
FWK]. For a more detailed configuration one may include sub-TLVs for For a more detailed configuration one may include sub-TLVs for the
the different OAM functions in order to specify various parameters in different OAM functions in order to specify various parameters in
detail. detail.
Typically intermediate nodes should not process or modify any of the Typically intermediate nodes should not process or modify any of the
OAM configuration TLVs but simply forward them to the end-node. OAM configuration TLVs but simply forward them to the end-node.
There is one exception to this and that is if the "MPLS OAM FMS sub- There is one exception to this and that is if the "MPLS OAM FMS sub-
TLV" is present. This sub-TLV has to be examined even by TLV" is present. This sub-TLV has to be examined even by
intermediate nodes, but only acted upon by nodes capable of intermediate nodes, but only acted upon by nodes capable of
transmitting FMS signals into the LSP being established. The sub-TLV transmitting FMS signals into the LSP being established. The sub-TLV
MAY be present the FMS flag is set in the "OAM Function Flags sub- MAY be present the FMS flag is set in the "OAM Function Flags sub-
TLV". If this sub-TLV is present the "OAM MIP entities desired" and TLV". If this sub-TLV is present the "OAM MIP entities desired" and
"OAM MEP entities desired" flags (described in [OAM-CONF-FWK]) in the "OAM MEP entities desired" flags (described in [RFC7260]) in the "LSP
"LSP Attributes Flags TLV" MUST be set and the entire OAM Attributes Flags TLV" MUST be set and the entire OAM Configuration
Configuration TLV placed either in the LSP_REQUIRED_ATTRIBUTES object TLV placed either in the LSP_REQUIRED_ATTRIBUTES object or in the
or in the LSP_ATTRIBUTES object ensure that capable intermediate LSP_ATTRIBUTES object ensure that capable intermediate nodes process
nodes process the configuration. If placed in LSP_ATTRIBUTES nodes the configuration. If placed in LSP_ATTRIBUTES nodes that are not
that are not able to process the OAM Configuration TLV will forward able to process the OAM Configuration TLV will forward the message
the message without generating an error, this is not the case if without generating an error, this is not the case if placed in the
placed in the LSP_REQUIRED_ATTRIBUTES object. LSP_REQUIRED_ATTRIBUTES object.
Finally, if the "MPLS OAM FMS sub-TLV" is not included only the "OAM Finally, if the "MPLS OAM FMS sub-TLV" is not included only the "OAM
MEP entities desired" flag is set and the OAM Configuration TLV may MEP entities desired" flag is set and the OAM Configuration TLV may
be placed in either LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES. be placed in either LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES.
3.1.1. Configuration of BFD sessions 3.1.1. Configuration of BFD sessions
For this specification, BFD MUST be run in either one of the two For this specification, BFD MUST be run in either one of the two
modes: modes:
skipping to change at page 7, line 15 skipping to change at page 7, line 45
Delay measurements are configured by setting PM/Delay flag in the Delay measurements are configured by setting PM/Delay flag in the
"OAM Function Flags sub-TLV", and by including the "MPLS OAM PM Loss "OAM Function Flags sub-TLV", and by including the "MPLS OAM PM Loss
sub-TLV", one can configure the measurement interval and the delay sub-TLV", one can configure the measurement interval and the delay
threshold values for triggering protection. threshold values for triggering protection.
3.1.3. Configuration of Fault Management Signals 3.1.3. Configuration of Fault Management Signals
To configure Fault Management Signals and their refresh time, the FMS To configure Fault Management Signals and their refresh time, the FMS
flag in the "OAM Function Flags sub-TLV" MUST be set and the "MPLS flag in the "OAM Function Flags sub-TLV" MUST be set and the "MPLS
OAM FMS sub-TLV" included. When configuring Fault Management OAM FMS sub-TLV" included. When configuring Fault Management
Signals, two options are possible, default configuration is enabled Signals, an implementation can enable the default configuration by
by setting the respective flags in the "OAM Function Flags sub-TLV", setting the FMS flag in the "OAM Function Flags sub-TLV". If an
the default settings MAY be customized by including the "MPLS OAM FMS implementation wishes to modify the default configuration it includes
sub-TLV". a "MPLS OAM FMS sub-TLV".
If an intermediate point is intended to originate fault management If an intermediate point is intended to originate fault management
signal messages, this means that such an intermediate point is signal messages, this means that such an intermediate point is
associated to a server MEP through a co-located MPLS-TP client/server associated to a server MEP through a co-located MPLS-TP client/server
adaptation function. Such a server MEP needs to be configured by its adaptation function. Such a server MEP needs to be configured by its
own RSVP-TE session (or, alternatively, via an NMS or LSP-ping). own RSVP-TE session (or, alternatively, via an NMS or LSP-ping).
However, by setting the "Fault Management subscription" flag in the However, by setting the "Fault Management subscription" flag in the
"MPLS OAM FMS sub-TLV", a client LSP can indicate that it would like "MPLS OAM FMS sub-TLV", a client LSP can indicate that it would like
an association to be created to the server MEP(s) on any intermediate an association to be created to the server MEP(s) on any intermediate
nodes. nodes.
3.2. MPLS OAM Configuration sub-TLV 3.2. MPLS OAM Configuration sub-TLV
The "OAM Configuration TLV", defined in [OAM-CONF-FWK], specifies the The "OAM Configuration TLV", defined in [RFC7260], specifies the OAM
OAM functions that are used for the LSP. This document extends the functions that are used for the LSP. This document extends the "OAM
"OAM Configuration TLV" by defining a new OAM Type: "MPLS OAM" Configuration TLV" by defining a new OAM Type: "MPLS OAM" (TBA1).
(suggested value 2, IANA to assign) from the "RSVP-TE OAM The "MPLS OAM" type is set to request the establishment of OAM
Configuration Registry". The "MPLS OAM" type is set to request the functions for MPLS-TP LSPs. The specific OAM functions are specified
establishment of OAM functions for MPLS-TP LSPs. The specific OAM in the "OAM Function Flags sub-TLV" as depicted in [RFC7260].
functions are specified in the "OAM Function Flags sub-TLV" as
depicted in [OAM-CONF-FWK].
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, it first will process any present "OAM Function Flags MPLS OAM type, the LSR will first process any present "OAM Function
sub-TLV" and then MUST process technology specific configuration Flags sub-TLV" and then it MUST process technology specific
TLVs. This document defines a new sub-TLV, the "MPLS OAM configuration TLVs. This document defines a sub-TLV, the "MPLS OAM
Configuration sub-TLV" that is carried in the "OAM Configuration Configuration sub-TLV" which is carried in the "OAM Configuration
TLV". IANA is requeted to assign type 33 from the sub-TLV space TLV".
maintained in the RSVP-TE OAM Configuration Registry.
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 (33) | Length | | MPLS OAM Conf. sub-TLV (TBA2) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ sub-TLVs ~ ~ sub-TLVs ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 33, the "MPLS OAM Configuration sub-TLV". Type: TBA2, the "MPLS OAM Configuration sub-TLV".
Length: indicates the total length including sub-TLVs. Length: indicates the total length in octets, including sub-TLVs as
well as the Type and Length fields.
The following MPLS OAM specific sub-TLVs MAY be included in the the The following MPLS OAM specific sub-TLVs MAY be included in the "MPLS
"MPLS OAM Configuration sub-TLV": OAM Configuration sub-TLV":
- "BFD Configuration sub-TLV", which MUST be included if the CC - "BFD Configuration sub-TLV", which MUST be included if the CC
and/or the CV OAM Function flag is set. This sub-TLV carries and/or the CV OAM Function flag is set. This sub-TLV carries
additional sub-TLVs, failure to include the correct sub-TLVs MUST additional sub-TLVs, failure to include the correct sub-TLVs MUST
result in an error being generated: "OAM Problem/Configuration result in an error being generated: "OAM Problem/Configuration
Error". The sub-TLVs are: Error". The 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
skipping to change at page 9, line 9 skipping to change at page 9, line 35
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 Function flag is set. If the "MPLS OAM PM Delay sub-TLV" OAM Function flag is set. If the "MPLS OAM PM Delay sub-TLV"
is not included, default configuration values are used. is not included, default configuration values are used.
- "MPLS OAM FMS sub-TLV" MAY be included if the FMS OAM Function - "MPLS OAM FMS sub-TLV" MAY be included if the FMS OAM Function
flag is set. If the "MPLS OAM FMS sub-TLV" is not included, flag is set. If the "MPLS OAM FMS sub-TLV" is not included,
default configuration values are used. default configuration values are used.
Moreover, if the CV Flag is set, the CC flag SHOULD be set as well. Following are some additional rules of processing MPLS OAM
The format of an MPLS-TP CV/CC message is shown in [RFC6428] and it Configuration sub-TLV:
requires, together with the BFD Control packet information, the "LSP
MEP-ID". The "LSP MEP-ID" contain four identifiers:
- MPLS-TP Global_ID - MPLS OAM Configuration sub-TLV? MAY be empty, i.e. have no
Value. Then its Length MUST be 8. Then all OAM functions that
have their corresponding flags set in the ?OAM Function Flags sub-
TLV? MUST be assigned their default values or left disabled.
- MPLS-TP Node Identifier - sub-TLV that doesn't have corresponding flag set MUST be
silently ignored;
- Tunnel_Num - 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
ignored.
- LSP_Num However, not all the values can be derived from the standard RSVP-TE
objects, in particular the locally assigned Tunnel ID at the egress
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-
TLV" in the Path message and the egress LSP MEP-ID in the same way in
the Resv message.
3.2.1. CV Flag Rules of Use
Moreover, if the CV flag is set, the CC flag MUST be set as well as
performing Connectivity Verification implies performing Continuity
Check. The format of an MPLS-TP CV/CC message is shown in [RFC6428]
and it requires, together with the BFD Control packet information,
the "LSP MEP-ID". The "LSP MEP-ID" contain four identifiers:
MPLS-TP Global_ID
MPLS-TP Node Identifier
Tunnel_Num
LSP_Num
These values need to be correctly set by both ingress and egress when These values need to be correctly set by both ingress and egress when
transmitting a CV packet and both ingress and egress needs to know transmitting a CV packet and both ingress and egress needs to know
what to expect when receving a CV packet. Most of these values can what to expect when receving a CV packet. Most of these values can
be derived from the Path and Resv messages [RFC3473], which uses a be derived from the Path and Resv messages [RFC3473], which uses a
5-tuple to uniquely identify an LSP within an operator's network. 5-tuple to uniquely identify an LSP within an operator's network.
This tuple is composed of a Tunnel Sender Address, Tunnel Endpoint This tuple is composed of a Tunnel Sender Address, Tunnel Endpoint
Address, Tunnel_ID, Extended Tunnel ID, and (GMPLS) LSP_ID. Address, Tunnel_ID, Extended Tunnel ID, and (GMPLS) LSP_ID.
However, not all the values can be derived from the standard RSVP-TE
objects, in particular the locally assigned Tunnel ID at the egress
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-
TLV" in the Path message and the egress LSP MEP-ID in the same way in
the Resv message.
3.3. BFD Configuration sub-TLV 3.3. BFD Configuration sub-TLV
The "BFD Configuration sub-TLV" (depicted below) is defined for BFD The "BFD Configuration sub-TLV" (depicted below) is defined for BFD
OAM specific configuration parameters. The "BFD Configuration sub- OAM specific configuration parameters. The "BFD Configuration sub-
TLV" is carried as a sub-TLV of the "MPLS OAM Configuration sub-TLV". TLV" is carried as a sub-TLV of the "MPLS OAM Configuration sub-TLV".
This TLV accommodates generic BFD OAM information and carries sub- This TLV accommodates generic BFD OAM information and carries sub-
TLVs. TLVs.
0 1 2 3 0 1 2 3
skipping to change at page 10, line 8 skipping to change at page 11, line 4
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BFD Conf. Type (1) | Length | | BFD Conf. Type (1) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Vers.| PHB |N|S|I|G|U|B| Reserved (set to all 0s) | |Vers.| PHB |N|S|I|G|U|B| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ sub-TLVs ~ ~ sub-TLVs ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1, the "BFD Configuration sub-TLV". Type: 1, the "BFD Configuration sub-TLV".
Length: indicates the total length including sub-TLVs. Length: indicates the total length in octets, including sub-TLVs as
well as the Type and Length fields.
Version: identifies the BFD protocol version. If the egress LSR does Version: identifies the BFD protocol version. If the egress LSR does
not support the version an error MUST be generated: "OAM Problem/ not support the version an error MUST be generated: "OAM Problem/
Unsupported BFD Version". Unsupported BFD Version".
PHB: Identifies the Per-Hop Behavior (PHB) to be used for periodic PHB: Identifies the Per-Hop Behavior (PHB) to be used for periodic
continuity monitoring messages. continuity monitoring messages.
BFD Negotiation (N): If set timer negotiation/re-negotiation via BFD BFD Negotiation (N): If set timer negotiation/re-negotiation via BFD
Control Messages is enabled, when cleared it is disabled. Control Messages is enabled, when cleared it is disabled.
skipping to change at page 11, line 40 skipping to change at page 12, line 37
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 Identfiers 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". Type: 1, "BFD Identifiers sub-TLV".
Length: indicates the TLV total length in octets. (8) Length: indicates the TLV total length in octets, including the Type
and Length fields (20).
Local Discriminator: A unique, nonzero discriminator value generated Local Discriminator: A unique, nonzero discriminator value generated
by the transmitting system and referring to itself, used to by the transmitting system and referring to itself, used to
demultiplex multiple BFD sessions between the same pair of systems. demultiplex multiple BFD sessions between the same pair of systems as
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
skipping to change at page 12, line 33 skipping to change at page 13, line 32
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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". Type: 2, "Negotiation Timer Parameters sub-TLV".
Length: indicates the TLV total length in octets. (16) Length: indicates the TLV total length in octets, including Type and
Length fields (16).
Acceptable Min. Asynchronous TX interval: If the S (symmetric) flag Acceptable Min. Asynchronous TX interval: If the S (symmetric) flag
is set in the "BFD Configuration sub-TLV", it expresses the desired is set in the "BFD Configuration sub-TLV", it expresses the desired
time interval (in microseconds) at which the ingress LER intends to time interval (in microseconds) at which the ingress LER intends to
both transmit and receive BFD periodic control packets. If the both transmit and receive BFD periodic control packets. If the
egress LSR can not support the value, it SHOULD reply with a egress LSR can not support the value, it SHOULD reply with a
supported interval. supported interval.
If the S (symmetric) flag is cleared in the "BFD Configuration sub- If the S (symmetric) flag is cleared in the "BFD Configuration sub-
TLV", this field expresses the desired time interval (in TLV", this field expresses the desired time interval (in
microseconds) at which the ingress LSR intends to transmit BFD microseconds) at which the ingress LSR intends to transmit BFD
periodic control packets. periodic control packets.
Acceptable Min. Asynchronous RX interval: If the S (symmetric) flag Acceptable Min. Asynchronous RX interval: If the S (symmetric) flag
is set in the "BFD Configuration sub-TLV", this field MUST be equal is set in the "BFD Configuration sub-TLV", this field MUST be set
to "Acceptable Min. Asynchronous TX interval" and has no additional equal to "Acceptable Min. Asynchronous TX interval" on transmit and
meaning with respect to the one described for "Acceptable Min. MUST be ignored on receipt since it has no additional meaning with
Asynchronous TX interval". respect to the one described for "Acceptable Min. Asynchronous TX
interval".
If the S (symmetric) flag is cleared in the "BFD Configuration sub- If the S (symmetric) flag is cleared in the "BFD Configuration sub-
TLV", it expresses the minimum time interval (in microseconds) at TLV", it expresses the minimum time interval (in microseconds) at
which the ingress/egress LSRs can receive periodic BFD control which the ingress/egress LSRs can receive periodic BFD control
packets. If this value is greater than the "Acceptable Min. packets. If this value is greater than the "Acceptable Min.
Asynchronous TX interval" received from the ingress/egress LSR, the Asynchronous TX interval" received from the ingress/egress LSR, the
receiving LSR MUST adopt the interval expressed in the "Acceptable receiving LSR MUST adopt the interval expressed in the "Acceptable
Min. Asynchronous RX interval". Min. Asynchronous RX interval".
Required Echo TX Interval: the minimum interval (in microseconds) Required Echo TX Interval: the minimum interval (in microseconds)
skipping to change at page 13, line 38 skipping to change at page 14, line 38
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". Type: 3, "BFD Authentication sub-TLV".
Length: indicates the TLV total length in octets. (8) Length: indicates the TLV total length in octets, including Type and
Length fields (8).
Auth Type: indicates which type of authentication to use. The same Auth Type: indicates which type of authentication to use. The same
values as are defined in section 4.1 of [RFC5880] are used. If the values as are defined in section 4.1 of [RFC5880] are used. If the
egress LSR does not support this type an "OAM Problem/Unsupported BFD egress LSR does not support this type an "OAM Problem/Unsupported BFD
Authentication Type" error MUST be generated. Authentication Type" error MUST be generated.
Auth Key ID: indicates which authentication key or password Auth Key ID: indicates which authentication key or password
(depending on Auth Type) should be used. How the key exchange is (depending on Auth Type) should be used. How the key exchange is
performed is out of scope of this document.If the egress LSR does not performed is out of scope of this document.If the egress LSR does not
support this Auth Key ID an "OAM Problem/Mismatch of BFD support this Auth Key ID an "OAM Problem/Mismatch of BFD
Authentication ID" error MUST be generated. Authentication Key ID" error MUST be generated.
Reserved: Reserved for future specification and set to 0 on Reserved: Reserved for future specification and set to 0 on
transmission and ignored when received. transmission and ignored when received.
3.4. Performance Monitoring sub-TLV 3.4. Performance Monitoring sub-TLV
If the "OAM Function Flags sub-TLV" has either the PM/Loss, PM/Delay If the "OAM Function Flags sub-TLV" has either the PM/Loss, PM/Delay
or PM/Throughput flag set, the "Performance Monitoring sub-TLV" MUST or PM/Throughput flag set, the "Performance Monitoring sub-TLV" MUST
be present in the "MPLS OAM Configuration sub-TLV". Failure to be present in the "MPLS OAM Configuration sub-TLV". Failure to
include the correct sub-TLVs MUST result in an "OAM Problem/ include the correct sub-TLVs MUST result in an "OAM Problem/
Configuration Error" error being generated. Configuration Error" error being generated.
The "Performance Monitoring sub-TLV" provides the configuration The "Performance Monitoring sub-TLV" provides the configuration
information mentioned in Section 7 of [RFC6374]. It includes support information mentioned in Section 7 of [RFC6374]. It includes support
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 In case the values need to be different than the default ones the
"Performance Monitoring sub-TLV" MAY include the following sub-TLVs: "Performance Monitoring sub-TLV" includes the following sub-TLVs:
- "MPLS OAM PM Loss sub-TLV" if the PM/Loss and/or PM/Throughput - "MPLS OAM PM Loss sub-TLV" if the PM/Loss and/or PM/Throughput
flag is set in the "OAM Function Flags sub-TLV"; 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 - "MPLS OAM PM Delay sub-TLV" if the PM/Delay flag is set in the
"OAM Function Flags sub-TLV"; "OAM 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".
skipping to change at page 14, line 49 skipping to change at page 15, line 49
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|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". Type: 2, "Performance Monitoring sub-TLV".
Length: indicates the TLV total length in octets. Length: indicates the TLV total length in octets, including sub-TLVs
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 - 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 specified mode an "OAM Problem/Unsupported
Delay Mode" error MUST be generated. Delay Mode" error MUST be generated.
- L: Loss inferred/direct (0=INFERRED, 1=DIRECT). If the egress - L: Loss inferred/direct (0=INFERRED, 1=DIRECT). If the egress
LSR does not support specified mode an "OAM Problem/Unsupported LSR does not support specified mode an "OAM Problem/Unsupported
skipping to change at page 16, line 8 skipping to change at page 17, line 21
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Interval | | Measurement Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Test Interval | | Test Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Loss Threshold | | Loss Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1,"MPLS OAM PM Loss sub-TLV". Type: 1,"MPLS OAM PM Loss sub-TLV".
Length: indicates the length of the parameters in octets (20). Length: indicates the length of the parameters in octets, including
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 - 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
skipping to change at page 17, line 17 skipping to change at page 18, line 29
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 Loss sub-TLV". Type: 2,"MPLS OAM PM Delay sub-TLV".
Length: indicates the length of the parameters in octets (20). Length: indicates the length of the parameters in octets, including
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 - 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
skipping to change at page 18, line 25 skipping to change at page 19, line 38
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MPLS OAM FMS Type (3) | Length | | MPLS OAM FMS Type (3) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E|S|T| Reserved (set to all 0s)| Refresh Timer | PHB | |E|S|T| Reserved (set to all 0s)| Refresh Timer | PHB |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 3, "MPLS OAM FMS sub-TLV". Type: 3, "MPLS OAM FMS sub-TLV".
Length: indicates the TLV total length in octets. (8) Length: indicates the TLV total length in octets, including Type and
Length fields (8).
FMS Signal Flags are used to enable the FMS signals at end point MEPs FMS Signal Flags are used to enable the FMS signals at end point MEPs
and the Server MEPs of the links over which the LSP is forwarded. In and the Server MEPs of the links over which the LSP is forwarded. In
this document only the S flag pertains to Server MEPs. this document only the S flag pertains to Server MEPs.
The following flags are defined: The following flags are defined:
- E: Enable Alarm Indication Signal (AIS) and Lock Report (LKR) - E: Enable Alarm Indication Signal (AIS) and Lock Report (LKR)
signalling as described in [RFC6427]. Default value is 1 signalling as described in [RFC6427]. Default value is 1
(enabled). If the egress MEP does not support FMS signal (enabled). If the egress MEP does not support FMS signal
generation an "OAM Problem/Fault management signaling unsupported" generation an "OAM Problem/Fault management signaling unsupported"
error MUST be generated. error MUST be generated.
- S: Indicate to a Server MEP that its should transmit AIS and LKR - S: Indicate to a Server MEP that its should transmit AIS and LKR
signals on client LSPs. Default value is 0 (disabled). If a signals on client LSPs. Default value is 0 (disabled). If a
Server MEP which is capable of generating FMS messages is for some Server MEP which is capable of generating FMS messages is for some
reason unable to do so for the LSP being signalled an "OAM Problem reason unable to do so for the LSP being signalled 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 the configuration of a specific
timer value. Default value is 0 (disabled). timer value. Default value is 0 (disabled).
- Remaining bits: Reserved for future specification and set to 0. - Remaining bits: Reserved for future specification and set to 0.
Refresh Timer: indicates the refresh timer of fault indication Refresh Timer: indicates the refresh timer of fault indication
messages, in seconds. The value MUST be between 1 to 20 seconds as messages, in seconds. The value MUST be between 1 to 20 seconds as
specified for the Refresh Timer field in [RFC6427]. If the egress specified for the Refresh Timer field in [RFC6427]. If the egress
LSR cannot support the value it SHOULD reply with a supported timer LSR cannot support the value it SHOULD reply with a supported timer
value. value.
PHB: identifies the per-hop behavior of packets with fault management PHB: identifies the per-hop behavior of packets with fault management
information. information.
4. Summary of MPLS OAM configuration errors 4. Summary of MPLS OAM configuration errors
In addition to error values specified in [OAM-CONF-FWK] this document In addition to error values specified in [RFC7260] this document
defines the following values for the "OAM Problem" Error Code: defines the following values for the "OAM Problem" Error Code:
- If an egress LSR does not support the specified BFD version, an - If an egress LSR does not support the specified BFD version, an
error MUST be generated: "OAM Problem/Unsupported BFD Version". error MUST be generated: "OAM Problem/Unsupported BFD Version".
- If an egress LSR does not support the specified BFD - If an egress LSR does not support the specified BFD
Encapsulation format, an error MUST be generated: "OAM Problem/ Encapsulation format, an error MUST be generated: "OAM Problem/
Unsupported BFD Encapsulation format". Unsupported BFD Encapsulation format".
- If an egress LSR does not support BFD Authentication, and it is - If an egress LSR does not support BFD Authentication, and it is
skipping to change at page 20, line 28 skipping to change at page 21, line 38
it is requested, an "OAM Problem/Fault management signaling it 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 - 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 "OAM Problem/Unable to create fault management association" an "OAM Problem/Unable to create fault management association"
error MUST be generated. error MUST be generated.
5. IANA Considerations 5. IANA Considerations
5.1. MPLS OAM Type
This document specifies new the "MPLS OAM Type". IANA is requested
to allocate a new type (TBA1) from the OAM Type space of the RSVP-TE
OAM Configuration Registry.
+------+-------------+---------------+
| Type | Description | Reference |
+------+-------------+---------------+
| TBA1 | MPLS OAM | This document |
+------+-------------+---------------+
Table 1: OAM MPLS Type
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 is
requested to allocate a new type (33) from the sub-TLV space of the requested to allocate a new type (TBA2) from the technology-specific
RSVP-TE OAM Configuration Registry. IANA is also requested to assign sub-TLV space of the RSVP-TE OAM Configuration Registry.
type (2) for MPLS OAM from the OAM Type space of the same registry.
RSVP-TE OAM Configuration Registry +------+--------------------------------+---------------+
| Type | Description | Reference |
+------+--------------------------------+---------------+
| TBA2 | MPLS OAM Configuration sub-TLV | This document |
+------+--------------------------------+---------------+
OAM Type Description Table 2: MPLS OAM Configuration sub-TLV Type
------------------- -----------------------------------
2 MPLS OAM
Sub-TLV Type Description 5.3. MPLS OAM Configuration Sub-TLV Types
------------------- -----------------------------------
33 MPLS OAM Configuration Sub-TLV
IANA is requested to maintain an MPLS TLV Type space in the "RSVP-TE IANA is requested to create an "MPLS OAM sub-TLV Types" sub-registry
OAM Configuration Registry" for the sub-TLV types carried in the in the "RSVP-TE OAM Configuration Registry" for the sub-TLVs carried
"MPLS OAM Configuration sub-TLV". This document defines the in the "MPLS OAM Configuration sub-TLV". Values from this new sub-
registry to be allocated through IETF Review except for the Reserved
for Experimental Use range. This document defines the following
types:
+-------------+--------------------------------+---------------+
| Type | Description | Reference |
+-------------+--------------------------------+---------------+
| 0 | Reserved | This document |
| 1 | BFD Configuration sub-TLV | This document |
| 2 | Performance Monitoring sub-TLV | This document |
| 3 | MPLS OAM FMS sub-TLV | This document |
| 4-65532 | Unassigned | |
| 65533-65534 | Reserved for Experimental Use | This document |
| 65535 | Reserved | This document |
+-------------+--------------------------------+---------------+
Table 3: MPLS OAM Configuration sub-TLV Types
5.4. BFD Configuration Sub-TLV Types
IANA is requested to create a "BFD Configuration sub-TLV Types" sub-
registry in the "RSVP-TE OAM Configuration Registry" for the sub-TLV
types carried in the "BFD Configuration sub-TLV". Values from this
new sub-registry to be allocated through IETF Review except for the
Reserved for Experimental Use range. This document defines the
following types: following types:
MPLS TLV Type Description +-------------+-------------------------------------+---------------+
------------------- ----------------------------------- | Type | Description | Reference |
0 Reserved +-------------+-------------------------------------+---------------+
1 BFD Configuration sub-TLV | 0 | Reserved | This document |
2 Performance Monitoring sub-TLV | 1 | BFD Identifiers sub-TLV | This document |
3 MPLS OAM FMS sub-TLV | 2 | Negotiation Timer Parameters sub- | This document |
4- Reserved | | TLV | |
| 3 | BFD Authentication sub-TLV | This document |
| 4-65532 | Unassigned | |
| 65533-65534 | Reserved for Experimental Use | This document |
| 65535 | Reserved | This document |
+-------------+-------------------------------------+---------------+
IANA is requested to maintain an BFD Configuration Type space in the Table 4: BFD Configuration Sus-TLV Types
"RSVP-TE OAM Configuration Registry" for the sub-TLV types carried in
the "BFD Configuration sub-TLV". This document defines the following
types:
BFD Conf. TLV Type Description 5.5. Performance Monitoring sub-TLV Types
------------------- ------------------------------------
0 Reserved
1 BFD Identifiers sub-TLV
2 Negotiation Timer Parameters sub-TLV
3 BFD Authentication sub-TLV
4- Reserved
IANA is requested to maintain an Performance Monitoring Type space in IANA is requested to create a "Performance Monitoring sub-TLV Type"
the "RSVP-TE OAM Configuration Registry" for the sub-TLV types sub-registry in the "RSVP-TE OAM Configuration Registry" for the sub-
carried in the "Performance Monitoring sub-TLV". This document TLV types carried in the "Performance Monitoring sub-TLV". Values
defines the following types: from this new sub-registry to be allocated through IETF Review except
for the Reserved for Experimental Use range. This document defines
the following types:
Perf. Mon. TLV Type Description +-------------+-------------------------------+---------------+
------------------- ------------------------------------ | Type | Description | Reference |
0 Reserved +-------------+-------------------------------+---------------+
1 MPLS OAM PM Loss sub-TLV | 0 | Reserved | This document |
2 MPLS OAM PM Delay sub-TLV | 1 | MPLS OAM PM Loss sub-TLV | This document |
3- Reserved | 2 | MPLS OAM PM Delay sub-TLV | This document |
| 3-65532 | Unassigned | |
| 65533-65534 | Reserved for Experimental Use | This document |
| 65535 | Reserved | This document |
+-------------+-------------------------------+---------------+
Table 5: Performance Monitoring sub-TLV Types
5.6. New RSVP-TE error codes
The following values need to be assigned under the "OAM Problem" The following values need to be assigned under the "OAM Problem"
Error Code [OAM-CONF-FWK]: "OAM Problem/Unsupported BFD Version", Error Code [RFC7260 by IETF Review process:
"OAM Problem/Unsupported BFD Encapsulation format", "OAM Problem/BFD
Authentication unsupported", "OAM Problem/Unsupported BFD +-----------------+---------------------------------+---------------+
Authentication Type", "OAM Problem/Mismatch of BFD Authentication Key | Error Value | Description | Reference |
ID", "OAM Problem/Unsupported Timestamp Format", "OAM Problem/ | Sub-codes | | |
Unsupported Delay Mode", "OAM Problem/Unsupported Loss Mode", "OAM +-----------------+---------------------------------+---------------+
Problem/Delay variation unsupported", "OAM Problem/Dyadic mode | TBA3 | Unsupported BFD Version | This document |
unsupported", "OAM Problem/Loopback mode unsupported" "OAM Problem/ | TBA4 | Unsupported BFD Encapsulation | This document |
Combined mode unsupported", "OAM Problem/Fault management signaling | | format | |
unsupported", "OAM Problem/Unable to create fault management | TBA5 | Unsupported BFD Authentication | This document |
association". | | Type | |
| TBA6 | Mismatch of BFD Authentication | This document |
| | Key ID | |
| TBA7 | Unsupported Timestamp Format | This document |
| TBA8 | Unsupported Delay Mode | This document |
| TBA9 | Unsupported Loss Mode | This document |
| TBA10 | Delay variation unsupported | This document |
| TBA11 | Dyadic mode unsupported | This document |
| TBA12 | Loopback mode unsupported | This document |
| TBA13 | Combined mode unsupported | This document |
| TBA14 | Fault management signaling | This document |
| | unsupported | |
| TBA15 | Unable to create fault | This document |
| | management association | |
+-----------------+---------------------------------+---------------+
Table 6: MPLS OAM Configuration Error Codes
6. Contributing Authors
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
6. Acknowledgements
The authors would like to thank David Allan, Lou Berger, Annamaria The authors would like to thank David Allan, Lou Berger, Annamaria
Fulignoli, Eric Gray, Andras Kern, David Jocha and David Sinicrope Fulignoli, Eric Gray, Andras Kern, David Jocha and David Sinicrope
for their useful comments. for their useful comments.
7. Security Considerations 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 [OAM-CONF-FWK] and targeting a single network element as discussed in [RFC7260] and
[RFC6060]. [RFC6060].
8. References 9. References
8.1. Normative References
[OAM-CONF-FWK] 9.1. Normative References
Takacs, A., Fedyk, D., and J. van He, "OAM Configuration
Framework for GMPLS RSVP-TE", 2009, <draft-ietf-ccamp-oam-
configuration-fwk>.
[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.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, December 2001. Tunnels", RFC 3209, December 2001.
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Functional Description", RFC 3471, (GMPLS) Signaling Functional Description", RFC 3471,
skipping to change at page 23, line 28 skipping to change at page 26, line 15
[RFC6427] Swallow, G., Fulignoli, A., Vigoureux, M., Boutros, S., [RFC6427] Swallow, G., Fulignoli, A., Vigoureux, M., Boutros, S.,
and D. Ward, "MPLS Fault Management Operations, and D. Ward, "MPLS Fault Management Operations,
Administration, and Maintenance (OAM)", RFC 6427, November Administration, and Maintenance (OAM)", RFC 6427, November
2011. 2011.
[RFC6428] Allan, D., Swallow Ed. , G., and J. Drake Ed. , "Proactive [RFC6428] Allan, D., Swallow Ed. , G., and J. Drake Ed. , "Proactive
Connectivity Verification, Continuity Check, and Remote Connectivity Verification, Continuity Check, and Remote
Defect Indication for the MPLS Transport Profile", RFC Defect Indication for the MPLS Transport Profile", RFC
6428, November 2011. 6428, November 2011.
8.2. Informative References [RFC7260] Takacs, A., Fedyk, D., and J. He, "GMPLS RSVP-TE
Extensions for Operations, Administration, and Maintenance
(OAM) Configuration", RFC 7260, June 2014.
9.2. Informative References
[ETH-OAM] Takacs, A., Gero, B., and H. Long, "GMPLS RSVP-TE [ETH-OAM] Takacs, A., Gero, B., and H. Long, "GMPLS RSVP-TE
Extensions for Ethernet OAM Configuration", 2012, <draft- Extensions for Ethernet OAM Configuration", 2014, <draft-
ietf-ccamp-rsvp-te-eth-oam-ext>. ietf-ccamp-rsvp-te-eth-oam-ext>.
[LSP-PING-CONF] [LSP-PING-CONF]
Bellagamba, E., Andersson, L., Ward, D., Drake, J., and P. Bellagamba, E., Andersson, L., Ward, D., Drake, J., and P.
Skoldstrom, "Configuration of pro-active MPLS-TP Skoldstrom, "Configuration of pro-active MPLS-TP
Operations, Administration, and Maintenance (OAM) Operations, Administration, and Maintenance (OAM)
Functions Using LSP Ping", 2012, <draft-ietf-mpls-lsp- Functions Using LSP Ping", 2014, <draft-ietf-mpls-lsp-
ping-mpls-tp-oam-conf>. ping-mpls-tp-oam-conf>.
[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
Label Switched (MPLS) Data Plane Failures", RFC 4379, Label Switched (MPLS) Data Plane Failures", RFC 4379,
February 2006. February 2006.
[RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G. [RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G.
Heron, "Pseudowire Setup and Maintenance Using the Label Heron, "Pseudowire Setup and Maintenance Using the Label
Distribution Protocol (LDP)", RFC 4447, April 2006. Distribution Protocol (LDP)", RFC 4447, April 2006.
skipping to change at page 24, line 25 skipping to change at page 27, line 17
Loopback Functions", RFC 6435, November 2011. Loopback Functions", RFC 6435, November 2011.
[RFC6669] Sprecher, N. and L. Fang, "An Overview of the Operations, [RFC6669] Sprecher, N. and L. Fang, "An Overview of the Operations,
Administration, and Maintenance (OAM) Toolset for MPLS- Administration, and Maintenance (OAM) Toolset for MPLS-
Based Transport Networks", RFC 6669, July 2012. Based Transport Networks", RFC 6669, July 2012.
Authors' Addresses Authors' Addresses
Elisa Bellagamba (editor) Elisa Bellagamba (editor)
Ericsson Ericsson
Torshamnsgatan 48
Kista 164 40
Sweden
Email: elisa.bellagamba@ericsson.com Email: elisa.bellagamba@ericsson.com
Loa Andersson (editor) Gregory Mirsky (editor)
Ericsson Ericsson
Torshamnsgatan 48
Kista 164 40
Sweden
Email: loa.andersson@ericsson.com Email: Gregory.Mirsky@ericsson.com
Loa Andersson (editor)
Huawei Technologies Co.
Email: loa@mail01.huawei.com
Pontus Skoldstrom (editor) Pontus Skoldstrom (editor)
Acreo AB Acreo AB
Electrum 236 Electrum 236
Kista 164 40 Kista 164 40
Sweden Sweden
Phone: +46 8 6327731 Phone: +46 70 7957731
Email: pontus.skoldstrom@acreo.se Email: pontus.skoldstrom@acreo.se
Dave Ward Dave Ward
Cisco Cisco
Email: dward@cisco.com Email: dward@cisco.com
Attila Takacs Attila Takacs
Ericsson Ericsson
1. Laborc u.
Budapest
HUNGARY
Email: attila.takacs@ericsson.com Email: attila.takacs@ericsson.com
 End of changes. 80 change blocks. 
215 lines changed or deleted 336 lines changed or added

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