draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-11.txt   draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-12.txt 
CCAMP Working Group E. Bellagamba, Ed. CCAMP Working Group E. Bellagamba, Ed.
Internet-Draft L. Andersson, Ed. Internet-Draft L. Andersson, Ed.
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: June 15, 2013 P. Skoldstrom, Ed. Expires: December 22, 2013 P. Skoldstrom, Ed.
Acreo AB Acreo AB
D. Ward D. Ward
Cisco Cisco
A. Takacs A. Takacs
Ericsson Ericsson
December 12, 2012 June 20, 2013
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-11 draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-12
Abstract Abstract
This specification describes the configuration of pro-active MPLS-TP This specification describes the configuration of pro-active MPLS-TP
Operations, Administration, and Maintenance (OAM) Functions for a (MPLS-Transport Profile) Operations, Administration, and Maintenance
given LSP using a set of TLVs that are carried by the RSVP-TE (OAM) Functions for a given LSP using a set of TLVs that are carried
protocol. by the GMPLS RSVP-TE protocol based on [OAM-CONF-FWK].
This document is a product of a joint Internet Engineering Task Force This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication (IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network. 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 June 15, 2013. This Internet-Draft will expire on December 22, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Contributing Authors . . . . . . . . . . . . . . . . . . . 4 1.1. Contributing Authors . . . . . . . . . . . . . . . . . . 4
1.2. Requirements Language . . . . . . . . . . . . . . . . . . 4 1.2. Requirements Language . . . . . . . . . . . . . . . . . . 4
2. Overview of MPLS OAM for Transport Applications . . . . . . . 4 2. Overview of MPLS OAM for Transport Applications . . . . . . . 4
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 . . . . . . . . . . . . 5
3.1.2. Configuration of Performance Monitoring . . . . . . . 6 3.1.2. Configuration of Performance Monitoring . . . . . . . 6
3.1.3. Configuration of Fault Management Signals . . . . . . 7 3.1.3. Configuration of Fault Management Signals . . . . . . 7
3.2. OAM Configuration TLV . . . . . . . . . . . . . . . . . . 7 3.2. MPLS OAM Configuration sub-TLV . . . . . . . . . . . . . 7
3.3. BFD Configuration sub-TLV . . . . . . . . . . . . . . . . 8 3.3. BFD Configuration sub-TLV . . . . . . . . . . . . . . . . 9
3.3.1. BFD Identifiers sub-TLV . . . . . . . . . . . . . . . 10 3.3.1. BFD Identifiers sub-TLV . . . . . . . . . . . . . . . 11
3.3.2. Negotiation Timer Parameters sub-TLV . . . . . . . . . 11 3.3.2. Negotiation Timer Parameters sub-TLV . . . . . . . . 12
3.3.3. BFD Authentication sub-TLV . . . . . . . . . . . . . . 12 3.3.3. BFD Authentication sub-TLV . . . . . . . . . . . . . 13
3.4. Performance Monitoring sub-TLV . . . . . . . . . . . . . . 13 3.4. Performance Monitoring sub-TLV . . . . . . . . . . . . . 14
3.4.1. MPLS OAM PM Loss sub-TLV . . . . . . . . . . . . . . . 14 3.4.1. MPLS OAM PM Loss sub-TLV . . . . . . . . . . . . . . 15
3.4.2. MPLS OAM PM Delay sub-TLV . . . . . . . . . . . . . . 15 3.4.2. MPLS OAM PM Delay sub-TLV . . . . . . . . . . . . . . 16
3.5. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . . . 16 3.5. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . . 18
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 4. Summary of MPLS OAM configuration errors . . . . . . . . . . 19
5. BFD OAM configuration errors . . . . . . . . . . . . . . . . . 18 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21
7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 7. Security Considerations . . . . . . . . . . . . . . . . . . . 22
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.1. Normative References . . . . . . . . . . . . . . . . . . . 19 8.1. Normative References . . . . . . . . . . . . . . . . . . 22
8.2. Informative References . . . . . . . . . . . . . . . . . . 20 8.2. Informative References . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction 1. Introduction
This document describes the configuration of pro-active MPLS-TP This document describes the configuration of pro-active MPLS-TP
Operations, Administration, and Maintenance (OAM) Functions for a (MPLS-Transport Profile) Operations, Administration, and Maintenance
given LSP using TLVs carried by RSVP-TE [RFC3473]. In particular it (OAM) Functions for a given LSP using TLVs using GMPLS RSVP-TE
specifies the mechanisms necessary to establish MPLS-TP OAM entities [RFC3473]. The use of GMPLS RSVP-TE for the configuration of OAM
at the maintenance points for monitoring and performing measurements functions is defined in a technology agnostic way in [OAM-CONF-FWK].
on an LSP, as well as defining information elements and procedures to This document specifies the additional mechanisms necessary to
configure pro-active MPLS-TP OAM functions running between LERs. establish MPLS-TP OAM entities at the maintenance points for
Initialization and control of on-demand MPLS-TP OAM functions are monitoring and performing measurements on an LSP, as well as defining
expected to be carried out by directly accessing network nodes via a information elements and procedures to configure pro-active MPLS-TP
management interface; hence configuration and control of on-demand OAM functions running between LERs. Initialization and control of
OAM functions are out-of-scope for this document. on-demand MPLS-TP OAM functions are expected to be carried out by
directly accessing network nodes via a management interface; hence
configuration and control of on-demand OAM functions are out-of-scope
for this document.
The Transport Profile of MPLS must, by definition [RFC5654], be MPLS-TP, the Transport Profile of MPLS, must, by definition
capable of operating without a control plane. Therefore there are [RFC5654], be capable of operating without a control plane.
several options for configuring MPLS-TP OAM, without a control plane Therefore, there are several options for configuring MPLS-TP OAM,
by either using an NMS or LSP Ping, or with a control plane using without a control plane by either using an NMS or LSP Ping, or with a
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- Pro-active MPLS-TP OAM is performed by four different protocols, Bi-
directional Forwarding Detection (BFD) [RFC6428] for Continuity directional Forwarding Detection (BFD) [RFC6428] for Continuity Check
Check/Connectivity Verification, the delay measurement protocol (DM) /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 8 skipping to change at page 4, line 5
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 Transport Profile (MPLS-TP) describes a profile of MPLS that MPLS-TP describes a profile of MPLS that enables operational models
enables operational models typical in transport networks, while typical in transport networks, while providing additional OAM,
providing additional OAM, survivability and other maintenance survivability and other maintenance functions not currently supported
functions not currently supported by MPLS. [RFC5860] defines the by MPLS. [RFC5860] defines the requirements for the OAM
requirements for the OAM functionality of MPLS-TP. functionality of MPLS-TP.
This document is a product of a joint Internet Engineering Task Force This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication (IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network. capabilities and functionalities of a packet transport network.
1.1. Contributing Authors 1.1. Contributing Authors
This document is the result of a large team of authors and This document is the result of a large team of authors and
skipping to change at page 5, line 25 skipping to change at page 5, line 19
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
RSVP-TE, or alternatively LSP Ping [LSP-PING-CONF], can be used to GMPLS RSVP-TE, or alternatively LSP Ping [LSP-PING-CONF], can be used
simply enable the different OAM functions, by setting the to simply enable the different OAM functions, by setting the
corresponding flags in the "OAM Functions TLV". For a more detailed corresponding flags in the "OAM Function Flags sub-TLV" [OAM-CONF-
configuration one may include sub-TLVs for the different OAM FWK]. For a more detailed configuration one may include sub-TLVs for
functions in order to specify various parameters in detail. the different OAM functions in order to specify various parameters in
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. The sub-TLV MAY be present if a flag is set in intermediate nodes, but only acted upon by nodes capable of
the "Function Flags sub-TLV", see section [3.2. OAM Configuration transmitting FMS signals into the LSP being established. The sub-TLV
TLV]. 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
"OAM MEP entities desired" flags (described in [OAM-CONF-FWK]) in the
"LSP Attributes Flags TLV" MUST be set and the entire OAM
Configuration TLV placed either in the LSP_REQUIRED_ATTRIBUTES object
or in the LSP_ATTRIBUTES object ensure that capable intermediate
nodes process the configuration. If placed in LSP_ATTRIBUTES nodes
that are not able to process the OAM Configuration TLV will forward
the message without generating an error, this is not the case if
placed in the LSP_REQUIRED_ATTRIBUTES object.
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
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 - Asynchronous mode, where both sides should be in active mode
- Unidirectional mode - Unidirectional mode
In the simplest scenario RSVP-TE, or alternatively LSP Ping [LSP- In the simplest scenario, RSVP-TE, or alternatively LSP Ping [LSP-
PING-CONF], is used only to bootstrap a BFD session for an 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 make every BFD Control packet carry an SHA1 hash of itself This would ensure that every BFD Control packet carries an SHA1 hash
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-TLV". The "BFD Authentication sub-TLV" is used to specify which sub-TLV". The "BFD Authentication sub-TLV" is used to specify which
authentication method that should be used and which pre-shared key / authentication method should be used and which pre-shared key /
password that should be used for this particular session. How the password should be used for this particular session. How the key
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 functions TLV", or a customized the respective flags in the "OAM Function Flags sub-TLV", or a
configuration. To customize the configuration one would set the customized configuration. To customize the configuration, one would
respective flags in the including the respective Loss and/or Delay set the respective flags and including the respective Loss and/or
sub-TLVs). Delay sub-TLVs).
By setting the PM Loss flag in the "OAM Functions TLV" and including By setting the PM/Loss flag in the "OAM Function Flags sub-TLV" and
the "MPLS OAM PM Loss sub-TLV" one can configure the measurement by including the "MPLS OAM PM Loss sub-TLV", one can configure the
interval and loss threshold values for triggering protection. measurement interval and loss threshold values for triggering
protection.
Delay measurements are configured by setting PM Delay flag in the Delay measurements are configured by setting PM/Delay flag in the
"OAM Functions TLV" and including the "MPLS OAM PM Loss sub-TLV" one "OAM Function Flags sub-TLV", and by including the "MPLS OAM PM Loss
can configure the measurement interval and the delay threshold values sub-TLV", one can configure the measurement interval and the delay
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 Monitoring Signals and their refresh time the FMS To configure Fault Management Signals and their refresh time, the FMS
flag in the "OAM Functions TLV" MUST be set and the "MPLS OAM FMS flag in the "OAM Function Flags sub-TLV" MUST be set and the "MPLS
sub-TLV" included. When configuring Fault Monitoring Signals it can OAM FMS sub-TLV" included. When configuring Fault Management
be chosen either the default configuration (by only setting the Signals, two options are possible, default configuration is enabled
respective flags in the "OAM functions TLV") or a customized by setting the respective flags in the "OAM Function Flags sub-TLV",
configuration (by including the "MPLS OAM FMS sub-TLV"). the default settings MAY be customized by including the "MPLS OAM FMS
sub-TLV".
If an intermediate point is meant 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. OAM Configuration 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 [OAM-CONF-FWK], specifies the
OAM functions that are used for the LSP. This TLV is carried in the OAM functions that are used for the LSP. This document extends the
LSP_ATTRIBUTES object in Path and Resv messages. "OAM Configuration TLV" by defining a new OAM Type: "MPLS OAM"
(suggested value 2, IANA to assign) from the "RSVP-TE OAM
Configuration Registry". The "MPLS OAM" type is set to request the
establishment of OAM functions for MPLS-TP LSPs. The specific OAM
functions are specified in the "OAM Function Flags sub-TLV" as
depicted in [OAM-CONF-FWK].
This document extends the "OAM Configuration TLV" by defining a new When an egress LSR receives an "OAM Configuration TLV" indicating the
OAM Type: "MPLS OAM" (suggested value 2, IANA to assign) from the MPLS OAM type, it first will process any present "OAM Function Flags
"RSVP-TE OAM Configuration Registry". The "MPLS OAM" type is set to sub-TLV" and then MUST process technology specific configuration
request the establishment of OAM functions for MPLS-TP LSPs. The TLVs. This document defines a new sub-TLV, the "MPLS OAM
specific OAM functions are specified in the "Function Flags" sub-TLV Configuration sub-TLV" that is carried in the "OAM Configuration
as depicted in [OAM-CONF-FWK]. TLV". IANA is requeted to assign type 33 from the sub-TLV space
maintained in the RSVP-TE OAM Configuration Registry.
The receiving edge LSR when the MPLS-TP OAM Type is requested should 0 1 2 3
check which OAM Function Flags are set in the "Function Flags TLV" 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
(also defined in [OAM-CONF-FWK]) and look for the corresponding +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
technology specific configuration TLVs. | MPLS OAM Conf. sub-TLV (33) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ sub-TLVs ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Additional corresponding sub-TLVs are as follows: Type: 33, the "MPLS OAM Configuration sub-TLV".
Length: indicates the total length including sub-TLVs.
The following MPLS OAM specific sub-TLVs MAY be included in the the
"MPLS 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 MUST carry a and/or the CV OAM Function flag is set. This sub-TLV carries
"BFD Local Discriminator sub-TLV" and a "Timer Negotiation additional sub-TLVs, failure to include the correct sub-TLVs MUST
Parameters sub-TLV" if the N flag is cleared. If the I flag is result in an error being generated: "OAM Problem/Configuration
set, the "BFD Authentication sub-TLV" may be included. Error". The sub-TLVs are:
- "MPLS OAM PM Loss sub-TLV" within the "Performance Monitoring - "BFD Identifiers sub-TLV", MUST always be included.
sub-TLV", which MAY be included if the PM/Loss OAM Function flag
is set. If the "MPLS OAM PM Loss sub-TLV" is not included,
default configuration values are used. Such sub-TLV MAY also be
included in case the Throughput function flag is set and there is
the need to specify measurement interval different from the
default ones. In fact the throughput measurement make use of the
same tool as the loss measurement, hence the same TLV is used.
- "MPLS OAM PM Delay sub-TLV" within the "Performance Monitoring - "Timer Negotiation Parameters sub-TLV", MUST be included if
sub-TLV", which MAY be included if the PM/Delay OAM Function flag the N flag is not set.
is set. If the "MPLS OAM PM Delay sub-TLV" is not included,
default configuration values are used.
- "MPLS OAM FMS sub-TLV", which MAY be included if the FMS OAM - "BFD Authentication sub-TLV", MAY be included if the I flag
Function flag is set. If the "MPLS OAM FMS sub-TLV" is not is set.
included, default configuration values are used.
Moreover, if the CV Flag is set, the CC flag MUST be set as well. - "Performance Monitoring sub-TLV", which MUST be included if any
of the PM/Delay, PM/Loss or PM/Throughput flags are set in the
"OAM Function Flag sub-TLV". This sub-TLV MAY carry additional
sub-TLVs:
- "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
included, default configuration values are used. The same sub-
TLV MAY also be included in case the PM/Throughput OAM Function
flag is set and there is the need to specify measurement
interval different from the default ones. Since throughput
measurements use the same tool as loss measurements the same
TLV is used.
- "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"
is not included, default configuration values are used.
- "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,
default configuration values are used.
Moreover, if the CV Flag is set, the CC flag SHOULD be set as well.
The format of an MPLS-TP CV/CC message is shown in [RFC6428] and it 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 requires, together with the BFD Control packet information, the "LSP
MEP-ID". The "LSP MEP-ID" contain four identifiers: MEP-ID". The "LSP MEP-ID" contain four identifiers:
- MPLS-TP Global_ID - MPLS-TP Global_ID
- MPLS-TP Node Identifier - MPLS-TP Node Identifier
- Tunnel_Num - Tunnel_Num
- LSP_Num - LSP_Num
These values need to be correctly set by both ingress and egress when These values need to be correctly set by both ingress and egress when
transmitting a CV packet and both ingress and egress needs to know transmitting a CV packet and both ingress and egress needs to know
what to expect when receving a CV packet. Most of these values can what to expect when 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 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 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. Therefor the full LSP MEP-ID cannot be derived by the ingress node. Therefore, the full LSP MEP-
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.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 "OAM Configuration TLV". TLV" is carried as a sub-TLV of the "MPLS OAM Configuration sub-TLV".
This TLV accommodates generic BFD OAM information and carries sub- This TLV accommodates generic BFD OAM information and carries sub-
TLVs. TLVs.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BFD Conf. Type (3) (IANA) | 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: indicates a new type, the "BFD Configuration sub-TLV" (IANA to Type: 1, the "BFD Configuration sub-TLV".
define, suggested value 3).
Length: indicates the total length including sub-TLVs. Length: indicates the total length including sub-TLVs.
Version: identifies the BFD protocol version. If a node does not Version: identifies the BFD protocol version. If the egress LSR does
support a specific BFD version an error must be generated: "OAM not support the version an error MUST be generated: "OAM Problem/
Problem/Unsupported OAM 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.
Symmetric session (S): If set the BFD session MUST use symmetric Symmetric session (S): If set the BFD session MUST use symmetric
timing values. timing values.
Integrity (I): If set BFD Authentication MUST be enabled. If the Integrity (I): If set BFD Authentication MUST be enabled. If the
"BFD Configuration sub-TLV" does not include a "BFD Authentication "BFD Configuration sub-TLV" does not include a "BFD Authentication
sub-TLV" the authentication MUST use Keyed SHA1 with an empty pre- sub-TLV" the authentication MUST use Keyed SHA1 with an empty pre-
shared key (all 0s). shared key (all 0s). If the egress LSR does not support BFD
Authentication an error MUST be generated: "OAM Problem/BFD
Authentication unsupported".
Encapsulation Capability (G): if set, it shows the capability of Encapsulation Capability (G): if set, shows the capability of
encapsulating BFD messages into G-Ach channel. If both the G bit and encapsulating BFD messages into The G-Ach channel. If both the G bit
U bit are set, configuration gives precedence to the G bit. 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
Capabilities an error MUST be generated: "OAM Problem/Unsupported BFD
Encapsulation format".
Encapsulation Capability (U): if set, it shows the capability of Encapsulation Capability (U): if set, 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. bit are set, configuration gives precedence to the G bit. If the
egress LSR does not support any of the ingress LSR Encapsulation
Capabilities an error MUST be generated: "OAM Problem/Unsupported 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. In
the second case, the source node does not expect any Discriminator 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 specification and 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
skipping to change at page 10, line 28 skipping to change at page 11, line 25
The "BFD Configuration sub-TLV" MUST include the following sub-TLVs The "BFD Configuration sub-TLV" MUST include the following sub-TLVs
in the Resv message: in the Resv message:
- "BFD Identifiers sub-TLV;" - "BFD Identifiers sub-TLV;"
- "Negotiation Timer Parameters sub-TLV" if: - "Negotiation Timer Parameters sub-TLV" if:
- the N and S flags are cleared, or if: - the N and S flags are cleared, or if:
- the N flag is cleared and the S flag is set, and the - the N flag is cleared and the S flag is set, and the
Negotiation Timer Parameters sub-TLV received by the egress "Negotiation Timer Parameters sub-TLV" received by the egress
contains unsupported values. In this case an updated contains unsupported values. In this case an updated
Negotiation Timer Parameters sub-TLV, containing values "Negotiation Timer Parameters sub-TLV", containing values
supported by the egress node, is returned to the ingress. 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 ident. Type (1) (IANA) | 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: indicates a new type, the "BFD Identifiers sub-TLV" (1) (IANA
to define). Type: 1, "BFD Identifiers sub-TLV".
Length: indicates the TLV total length in octets. (8) Length: indicates the TLV total length in octets. (8)
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.
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) (IANA) | 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: indicates a new type, the "Negotiation Timer Parameters sub- Type: 2, "Negotiation Timer Parameters sub-TLV".
TLV" (IANA to define, suggested value 2).
Length: indicates the TLV total length in octets. (16) Length: indicates the TLV total length in octets. (16)
Acceptable Min. Asynchronous TX interval: in case of S (symmetric) Acceptable Min. Asynchronous TX interval: If the S (symmetric) flag
flag 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
receiving edge LSR can not support such value, it SHOULD reply with egress LSR can not support the value, it SHOULD reply with a
an interval greater than the one proposed. supported interval.
In case of S (symmetric) flag 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 a edge LSR intends to transmit BFD periodic microseconds) at which the ingress LSR intends to transmit BFD
control packets in its transmitting direction. periodic control packets.
Acceptable Min. Asynchronous RX interval: in case of S (symmetric) Acceptable Min. Asynchronous RX interval: If the S (symmetric) flag
flag set in the "BFD Configuration sub-TLV", this field MUST be equal is set in the "BFD Configuration sub-TLV", this field MUST be equal
to "Acceptable Min. Asynchronous TX interval" and has no additional to "Acceptable Min. Asynchronous TX interval" and has no additional
meaning respect to the one described for "Acceptable Min. meaning with respect to the one described for "Acceptable Min.
Asynchronous TX interval". Asynchronous TX interval".
In case of S (symmetric) flag 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 edge LSRs can receive BFD periodic control packets. In case which the ingress/egress LSRs can receive periodic BFD control
this value is greater than the "Acceptable Min. Asynchronous TX packets. If this value is greater than the "Acceptable Min.
interval" received from the other edge LSR, such edge LSR MUST adopt Asynchronous TX interval" received from the ingress/egress LSR, the
the interval expressed in this "Acceptable Min. Asynchronous RX receiving LSR MUST adopt the interval expressed in the "Acceptable
interval". Min. 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 [RFC5880] sect. 6.8.9. 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 receiving system can support the receipt of BFD Echo packets. If the LSR node cannot
not support this value an error MUST be generated "Unsupported BFD TX support this value it SHOULD reply with a supported value (which may
rate interval". 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) (IANA) | Length | | BFD Auth. Type (3) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Auth Type | Auth Key ID | Reserved (0s) | | Auth Type | Auth Key ID | Reserved (0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: indicates a new type, the "BFD Authentication sub-TLV" (IANA to Type: 3, "BFD Authentication sub-TLV".
define).
Length: indicates the TLV total length in octets. (8) Length: indicates the TLV total length in octets. (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. 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
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. 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
Authentication 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 functions TLV" has either the L (Loss), D (Delay) or T If the "OAM Function Flags sub-TLV" has either the PM/Loss, PM/Delay
(Throughput) flag set, the "Performance Monitoring sub-TLV" MUST be or PM/Throughput flag set, the "Performance Monitoring sub-TLV" MUST
present. be present in the "MPLS OAM Configuration sub-TLV". Failure to
include the correct sub-TLVs MUST result in an "OAM Problem/
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", "MPLS OAM PM Loss sub-TLV" MAY "Performance Monitoring sub-TLV" MAY include the following sub-TLVs:
include the following sub-TLVs:
- "MPLS OAM PM Loss sub-TLV" if the L flag is set in the "OAM - "MPLS OAM PM Loss sub-TLV" if the PM/Loss and/or PM/Throughput
functions TLV"; flag is set in the "OAM Function Flags sub-TLV";
- "MPLS OAM PM Delay sub-TLV" if the D flag is set in the "OAM - "MPLS OAM PM Delay sub-TLV" if the PM/Delay flag is set in the
functions 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 "OAM Functions 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(4) (IANA)| 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: indicates a new type, the "Performance Monitoring sub-TLV" Type: 2, "Performance Monitoring sub-TLV".
(IANA to define, suggested value 4).
Length: indicates the TLV total length in octets. Length: indicates the TLV total length in octets.
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) - D: Delay inferred/direct (0=INFERRED, 1=DIRECT). If the egress
LSR does not support specified mode an "OAM Problem/Unsupported
Delay Mode" error MUST be generated.
- L: Loss inferred/direct (0=INFERRED, 1=DIRECT) - L: Loss inferred/direct (0=INFERRED, 1=DIRECT). If the egress
LSR does not support specified mode an "OAM Problem/Unsupported
Loss Mode" error MUST be generated.
- J: Delay variation/jitter (1=ACTIVE, 0=NOT ACTIVE) - J: Delay variation/jitter (1=ACTIVE, 0=NOT ACTIVE). If the
egress LSR does not support Delay variation measurements and the J
flag is set, an "OAM Problem/Delay variation unsupported" error
MUST be generated.
- Y: Dyadic (1=ACTIVE, 0=NOT ACTIVE) - 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
mode unsupported" error MUST be generated.
- K: Loopback (1=ACTIVE, 0=NOT ACTIVE) - K: Loopback (1=ACTIVE, 0=NOT ACTIVE). If the egress LSR does
not support Loopback mode and the K flag is set, an "OAM Problem/
Loopback mode unsupported" error MUST be generated.
- C: Combined (1=ACTIVE, 0=NOT ACTIVE) - C: Combined (1=ACTIVE, 0=NOT ACTIVE). If the egress LSR does
not support Combined mode and the C flag is set, an "OAM Problem/
Combined mode unsupported" 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.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) (IANA) | 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: indicates a new type, the "MPLS OAM PM Loss sub-TLV" (IANA to Type: 1,"MPLS OAM PM Loss sub-TLV".
define, suggested value 1).
Length: indicates the length of the parameters in octets (20). Length: indicates the length of the parameters in octets (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. in [RFC6374]. By default it is set to IEEE 1588 version 1. If the
egress LSR cannot support this value an "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 - 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 (DSCP value), and 0 otherwise. When set to 1, the
DS field of the message indicates the measured traffic class. By DS field of the message indicates the measured traffic class. By
default it is set to 1. default it is set to 1.
- B: Octet (byte) count. When set to 1, indicates that the - B: Octet (byte) count. When set to 1, 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,
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 specification and 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 on both directions. If
the edge LSR receiving the Path message can not support such value, the egress LSR cannot support the value, it SHOULD reply with a
it SHOULD reply with a higher interval. By default it is set to supported interval. By default it is set to (100) as per [RFC6375].
(100) as per [RFC6375].
Test Interval: test messages interval in milliseconds as described in Test Interval: test messages interval in milliseconds as described in
[RFC6374]. By default it is set to (10) as per [RFC6375]. [RFC6374]. By default it is set to (10) as per [RFC6375]. If the
egress LSR cannot support the value, it SHOULD 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 of the "Performance Monitoring sub-TLV". TLV of the "Performance Monitoring sub-TLV".
0 1 2 3 0 1 2 3
skipping to change at page 15, line 38 skipping to change at page 17, line 4
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 of the "Performance Monitoring sub-TLV". 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) (IANA) | 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: indicates a new type, the "MPLS OAM PM Loss sub-TLV" (IANA to Type: 2,"MPLS OAM PM Loss sub-TLV".
define, suggested value 2).
Length: indicates the length of the parameters in octets (20). Length: indicates the length of the parameters in octets (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. in [RFC6374]. By default it is set to IEEE 1588 version 1. If the
egress LSR cannot support this value an "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 - 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 (DSCP value), and 0 otherwise. When set to 1, the
DS field of the message indicates the measured traffic class. By DS field of the message indicates the measured traffic class. By
default it is set to 1. default it is set to 1.
- B: Octet (byte) count. When set to 1, indicates that the - B: Octet (byte) count. When set to 1, 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,
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 specification and 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 edge LSR receiving the Path message can not support such value, the egress LSR cannot support the value, it SHOULD reply with a
it can reply with a higher interval. By default it is set to (1000) supported interval. By default it is set to (1000) as per [RFC6375].
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]. in [RFC6374]. By default it is set to (10) as per [RFC6375]. If the
egress LSR cannot support the value, it SHOULD 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 "OAM Configuration sub-TLV". When both working and protection the "MPLS OAM Configuration sub-TLV". When both working and
paths are signaled, both LSPs SHOULD be signaled with identical protection paths are signaled, both LSPs SHOULD be signaled with
settings of the E flag, T flag, and the refresh timer. identical settings of the E flag, T flag, and the refresh timer.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MPLS OAM FMS Type (5) (IANA) | 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: indicates a new type, the "MPLS OAM FMS sub-TLV" (IANA to
define). Type: 3, "MPLS OAM FMS sub-TLV".
Length: indicates the TLV total length in octets. (8) Length: indicates the TLV total length in octets. (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). (enabled). If the egress MEP does not support FMS signal
generation an "OAM Problem/Fault management signaling unsupported"
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 the client LSP. Default value is 0 (disabled). signals on client LSPs. Default value is 0 (disabled). If a
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
/Unable to create fault management association" error MUST 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 edge LSR specified for the Refresh Timer field in [RFC6427]. If the egress
receiving the Path message can not support the value it SHOULD reply LSR cannot support the value it SHOULD reply with a supported timer
with a higher 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. IANA Considerations 4. Summary of MPLS OAM configuration errors
This document specifies the following new TLV types: In addition to error values specified in [OAM-CONF-FWK] this document
defines the following values for the "OAM Problem" Error Code:
- "BFD Configuration" type: 3; - If an egress LSR does not support the specified BFD version, an
error MUST be generated: "OAM Problem/Unsupported BFD Version".
- "Performance Monitoring" type: 4; - If an egress LSR does not support the specified BFD
Encapsulation format, an error MUST be generated: "OAM Problem/
Unsupported BFD Encapsulation format".
- "MPLS OAM FMS" type: 5. - If an egress LSR does not support BFD Authentication, and it is
requested, an error MUST be generated: "OAM Problem/BFD
Authentication unsupported".
sub-TLV types to be carried in the "BFD Configuration sub-TLV": - If an egress LSR does not support the specified BFD
Authentication Type, an error MUST be generated: "OAM Problem/
Unsupported BFD Authentication Type".
- "BFD Identifiers" sub-TLV type: 1; - If an egress LSR is not able to use the specified Authentication
- "Negotiation Timer Parameters" sub-TLV type: 2. Key ID, an error MUST be generated: "OAM Problem/Mismatch of BFD
Authentication Key ID".
- "BFD Authentication" sub-TLV type: 3. - If an egress LSR does not support the specified Timestamp
Format, an error MUST be generated: "OAM Problem/Unsupported
Timestamp Format".
sub-TLV types to be carried in the "Performance monitoring sub-TLV": - If an egress LSR does not support specified Delay mode, an "OAM
Problem/Unsupported Delay Mode" error MUST be generated.
- "MPLS OAM PM Loss" type: 1; - If an egress LSR does not support specified Loss mode, an "OAM
Problem/Unsupported Loss Mode" error MUST be generated.
- "MPLS OAM PM Delay" type: 2; - If an egress LSR does not support Delay variation measurements,
and it is requested, an "OAM Problem/Delay variation unsupported"
error MUST be generated.
5. BFD OAM configuration errors - If an egress LSR does not support Dyadic mode, and it is
requested, an "OAM Problem/Dyadic mode unsupported" error MUST be
generated.
In addition to error values specified in [OAM-CONF-FWK] and [ETH-OAM] - If an egress LSR does not support Loopback mode, and it is
this document defines the following values for the "OAM Problem" requested, an "OAM Problem/Loopback mode unsupported" error MUST
Error Code: be generated.
- "MPLS OAM Unsupported Functionality"; - If an egress LSR does not support Combined mode, and it is
requested, an "OAM Problem/Combined mode unsupported" error MUST
be generated.
- "OAM Problem/Unsupported TX rate interval"; - If an egress LSR does not support Fault Monitoring Signals, and
it is requested, an "OAM Problem/Fault management signaling
unsupported" error MUST be generated.
- "OAM Problem/Unsupported RX rate interval"; - If an intermediate server MEP supports Fault Monitoring Signals
but is unable to create an association, when requested to do so,
an "OAM Problem/Unable to create fault management association"
error MUST be generated.
- "OAM Problem/Unsupported unsupported Authentication Type"; 5. IANA Considerations
- "OAM Problem, mismatch of Authentication Key ID ". 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
RSVP-TE OAM Configuration Registry. IANA is also requested to assign
type (2) for MPLS OAM from the OAM Type space of the same registry.
6. Acknowledgements RSVP-TE OAM Configuration Registry
OAM Type Description
------------------- -----------------------------------
2 MPLS OAM
Sub-TLV Type Description
------------------- -----------------------------------
33 MPLS OAM Configuration Sub-TLV
IANA is requested to maintain an MPLS TLV Type space in the "RSVP-TE
OAM Configuration Registry" for the sub-TLV types carried in the
"MPLS OAM Configuration sub-TLV". This document defines the
following types:
MPLS TLV Type Description
------------------- -----------------------------------
0 Reserved
1 BFD Configuration sub-TLV
2 Performance Monitoring sub-TLV
3 MPLS OAM FMS sub-TLV
4- Reserved
IANA is requested to maintain an BFD Configuration Type space in the
"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
------------------- ------------------------------------
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
the "RSVP-TE OAM Configuration Registry" for the sub-TLV types
carried in the "Performance Monitoring sub-TLV". This document
defines the following types:
Perf. Mon. TLV Type Description
------------------- ------------------------------------
0 Reserved
1 MPLS OAM PM Loss sub-TLV
2 MPLS OAM PM Delay sub-TLV
3- Reserved
The following values need to be assigned under the "OAM Problem"
Error Code [OAM-CONF-FWK]: "OAM Problem/Unsupported BFD Version",
"OAM Problem/Unsupported BFD Encapsulation format", "OAM Problem/BFD
Authentication unsupported", "OAM Problem/Unsupported BFD
Authentication Type", "OAM Problem/Mismatch of BFD Authentication Key
ID", "OAM Problem/Unsupported Timestamp Format", "OAM Problem/
Unsupported Delay Mode", "OAM Problem/Unsupported Loss Mode", "OAM
Problem/Delay variation unsupported", "OAM Problem/Dyadic mode
unsupported", "OAM Problem/Loopback mode unsupported" "OAM Problem/
Combined mode unsupported", "OAM Problem/Fault management signaling
unsupported", "OAM Problem/Unable to create fault management
association".
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 7. 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. targeting a single network element as discussed in [OAM-CONF-FWK] and
[RFC6060].
8. References 8. References
8.1. Normative References 8.1. Normative References
[OAM-CONF-FWK] [OAM-CONF-FWK]
Takacs, A., Fedyk, D., and J. van He, "OAM Configuration Takacs, A., Fedyk, D., and J. van He, "OAM Configuration
Framework for GMPLS RSVP-TE", 2009, Framework for GMPLS RSVP-TE", 2009, <draft-ietf-ccamp-oam-
<draft-ietf-ccamp-oam-configuration-fwk>. 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 20, line 4 skipping to change at page 23, line 20
Switched Paths (LSPs)", RFC 5884, June 2010. Switched Paths (LSPs)", RFC 5884, June 2010.
[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.
[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.
[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, Administration, and Maintenance (OAM)", RFC 6427, November
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", Defect Indication for the MPLS Transport Profile", RFC
RFC 6428, November 2011. 6428, November 2011.
8.2. Informative References 8.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, Extensions for Ethernet OAM Configuration", 2012, <draft-
<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, Functions Using LSP Ping", 2012, <draft-ietf-mpls-lsp-
<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.
[RFC5921] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. [RFC5921] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L.
Berger, "A Framework for MPLS in Transport Networks", Berger, "A Framework for MPLS in Transport Networks", RFC
RFC 5921, July 2010. 5921, July 2010.
[RFC6371] Busi, I. and D. Allan, "Operations, Administration, and [RFC6371] Busi, I. and D. Allan, "Operations, Administration, and
Maintenance Framework for MPLS-Based Transport Networks", Maintenance Framework for MPLS-Based Transport Networks",
RFC 6371, September 2011. RFC 6371, September 2011.
[RFC6375] Frost, D. and S. Bryant, "A Packet Loss and Delay [RFC6375] Frost, D. and S. Bryant, "A Packet Loss and Delay
Measurement Profile for MPLS-Based Transport Networks", Measurement Profile for MPLS-Based Transport Networks",
RFC 6375, September 2011. RFC 6375, September 2011.
[RFC6435] Boutros, S., Sivabalan, S., Aggarwal, R., Vigoureux, M., [RFC6435] Boutros, S., Sivabalan, S., Aggarwal, R., Vigoureux, M.,
skipping to change at page 21, line 10 skipping to change at page 24, line 26
[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 Torshamnsgatan 48
Kista, 164 40 Kista 164 40
Sweden Sweden
Email: elisa.bellagamba@ericsson.com Email: elisa.bellagamba@ericsson.com
Loa Andersson (editor) Loa Andersson (editor)
Ericsson Ericsson
Torshamnsgatan 48 Torshamnsgatan 48
Kista, 164 40 Kista 164 40
Sweden Sweden
Phone:
Email: loa.andersson@ericsson.com Email: loa.andersson@ericsson.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 8 6327731
Email: pontus.skoldstrom@acreo.se Email: pontus.skoldstrom@acreo.se
Dave Ward Dave Ward
Cisco Cisco
Phone:
Email: dward@cisco.com Email: dward@cisco.com
Attila Takacs Attila Takacs
Ericsson Ericsson
1. Laborc u. 1. Laborc u.
Budapest, Budapest
HUNGARY HUNGARY
Phone:
Email: attila.takacs@ericsson.com Email: attila.takacs@ericsson.com
 End of changes. 132 change blocks. 
268 lines changed or deleted 432 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/