draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-07.txt   draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-08.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: May 3, 2012 P. Skoldstrom, Ed. Expires: October 15, 2012 P. Skoldstrom, Ed.
Acreo AB Acreo AB
D. Ward D. Ward
Juniper Juniper
A. Takacs A. Takacs
Ericsson Ericsson
October 31, 2011 April 13, 2012
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-07 draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-08
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 Operations, Administration, and Maintenance (OAM) Functions for a
given LSP using a set of TLVs that are carried by the RSVP-TE given LSP using a set of TLVs that are carried by the RSVP-TE
protocol. protocol.
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
skipping to change at page 1, line 46 skipping to change at page 1, line 46
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 May 3, 2012. This Internet-Draft will expire on October 15, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 30 skipping to change at page 2, line 30
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 OAM Configuration Operation Overview . . . . . . . . 5 3.1. MPLS 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 . . . . . . 6 3.1.3. Configuration of Fault Management Signals . . . . . . 6
3.2. OAM Configuration TLV . . . . . . . . . . . . . . . . . . 7 3.2. OAM Configuration TLV . . . . . . . . . . . . . . . . . . 7
3.3. BFD Configuration sub-TLV . . . . . . . . . . . . . . . . 9 3.3. BFD Configuration sub-TLV . . . . . . . . . . . . . . . . 9
3.3.1. Local Discriminator sub-TLV . . . . . . . . . . . . . 10 3.3.1. Local Discriminator sub-TLV . . . . . . . . . . . . . 11
3.3.2. Negotiation Timer Parameters sub-TLV . . . . . . . . . 11 3.3.2. Negotiation Timer Parameters sub-TLV . . . . . . . . . 11
3.3.3. BFD Authentication sub-TLV . . . . . . . . . . . . . . 12 3.3.3. BFD Authentication sub-TLV . . . . . . . . . . . . . . 12
3.4. Performance Monitoring sub-TLV . . . . . . . . . . . . . . 13 3.4. Performance Monitoring sub-TLV . . . . . . . . . . . . . . 13
3.4.1. MPLS OAM PM Loss sub-TLV . . . . . . . . . . . . . . . 14 3.4.1. MPLS OAM PM Loss sub-TLV . . . . . . . . . . . . . . . 14
3.4.2. MPLS OAM PM Delay sub-TLV . . . . . . . . . . . . . . 15 3.4.2. MPLS OAM PM Delay sub-TLV . . . . . . . . . . . . . . 15
3.5. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . . . 16 3.5. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . . . 16
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
5. BFD OAM configuration errors . . . . . . . . . . . . . . . . . 17 5. BFD OAM configuration errors . . . . . . . . . . . . . . . . . 18
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18
7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 7. Security Considerations . . . . . . . . . . . . . . . . . . . 18
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.1. Normative References . . . . . . . . . . . . . . . . . . . 18 8.1. Normative References . . . . . . . . . . . . . . . . . . . 19
8.2. Informative References . . . . . . . . . . . . . . . . . . 19 8.2. Informative References . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21
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 Operations, Administration, and Maintenance (OAM) Functions for a
given LSP using TLVs carried by RSVP-TE [RFC3209]. In particular it given LSP using TLVs carried by RSVP-TE [RFC3209]. In particular it
specifies the mechanisms necessary to establish MPLS-TP OAM entities specifies the mechanisms necessary to establish MPLS-TP OAM entities
at and points for monitoring and performing measurements on an LSP, at the maintenance points for monitoring and performing measurements
as well as defining information elements and procedures to configure on an LSP, as well as defining information elements and procedures to
pro-active MPLS OAM functions runnineg between LERs. Initialization configure pro-active MPLS OAM functions running between LERs.
and control of on-demand MPLS OAM functions are expected to be Initialization and control of on-demand MPLS OAM functions are
carried out by directly accessing network nodes via a management expected to be carried out by directly accessing network nodes via a
interface; hence configuration and control of on-demand OAM functions management interface; hence configuration and control of on-demand
are out-of-scope for this document. OAM functions are out-of-scope for this document.
The Transport Profile of MPLS must, by definition [RFC5654], be The Transport Profile of MPLS must, by definition [RFC5654], be
capable of operating without a control plane. Therefore there are capable of operating without a control plane. Therefore there are
three options for configuring MPLS-TP OAM, without a control plane by several options for configuring MPLS-TP OAM, without a control plane
either using an NMS or LSP Ping, or with a control plane using GMPLS by either using an NMS or LSP Ping, or with a control plane using
(specifically RSVP-TE) . signaling protocols RSVP-TE and/or T-LDP. Use of T-LDP for
configuration of MPLS-TP OAM is outside of scope of this document.
Pro-active MPLS OAM is performed by three different protocols, Pro-active MPLS OAM is performed by three different protocols,
Bidirectional Forwarding Detection (BFD) [RFC5880] for Continuity Bidirectional Forwarding Detection (BFD) [RFC6428] for Continuity
Check/Connectivity Verification, the delay measurement protocol (DM) 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
skipping to change at page 4, line 22 skipping to change at page 4, line 23
(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
contributors. The following is a list of the co-authors: contributors. The following is a list of the co-authors:
Gregory Mirsky
John Drake John Drake
Benoit Tremblay Benoit Tremblay
1.2. Requirements Language 1.2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
skipping to change at page 8, line 29 skipping to change at page 8, line 31
- "MPLS OAM PM Delay sub-TLV" within the "Performance Monitoring - "MPLS OAM PM Delay sub-TLV" within the "Performance Monitoring
sub-TLV", which MAY be included if the PM/Delay OAM Function flag sub-TLV", which MAY be included if the PM/Delay OAM Function flag
is set. If the "MPLS OAM PM Delay sub-TLV" is not included, is set. If the "MPLS OAM PM Delay sub-TLV" is not included,
default configuration values are used. default configuration values are used.
- "MPLS OAM FMS sub-TLV", which MAY be included if the FMS OAM - "MPLS OAM FMS sub-TLV", which MAY be included if the FMS OAM
Function flag is set. If the "MPLS OAM FMS sub-TLV" is not Function flag is set. If the "MPLS OAM FMS sub-TLV" is not
included, default configuration values are used. included, default configuration values are used.
Moreover, if the CV or CC flag is set, the CC flag MUST be set at the Moreover, if the CV or CC flag is set, the CC flag MUST be set as
same time. The format of an MPLS-TP CV/CC message is shown in [BFD- well. The format of an MPLS-TP CV/CC message is shown in [BFD-CCCV]
CCCV] and it requires, together with the BFD control packet and it requires, together with the BFD control packet information,
information, the "Unique MEP-ID of source of BFD packet". [MPLS-TP- the "Unique MEP-ID of source of BFD packet". [MPLS-TP-IDENTIF]
IDENTIF] defines the composition of such identifier as: defines the composition of such identifier as:
<"Unique MEP-ID of source of BFD packet"> ::= <"Unique MEP-ID of source of BFD packet"> ::=
<src_node_id><src_tunnel_num><lsp_num> <src_node_id><src_tunnel_num><lsp_num>
Note that support of ITU IDs is out-of-scope.
GMPLS signaling [RFC3473] uses a 5-tuple to uniquely identify an LSP GMPLS signaling [RFC3473] uses a 5-tuple to uniquely identify an LSP
within an operator's network. This tuple is composed of a Tunnel within an operator's network. This tuple is composed of a Tunnel
Endpoint Address, Tunnel_ID, Extended Tunnel ID, and Tunnel Sender Endpoint Address, Tunnel_ID, Extended Tunnel ID, and Tunnel Sender
Address and (GMPLS) LSP_ID. Address and (GMPLS) LSP_ID.
Hence, the following mapping is used without the need of redefining a Hence, the following mapping is used without the need of redefining a
new TLV for MPLS-TP proactive CV purpose. new TLV for MPLS-TP proactive CV purpose.
- Tunnel ID = src_tunnel_num - Tunnel ID = src_tunnel_num
- Tunnel Sender Address = src_node_id - Tunnel Sender Address = src_node_id
- LSP ID = LSP_Num - LSP ID = LSP_Num
"Tunnel ID" and "Tunnel Sender Address" are included in the "SESSION" "Tunnel ID" and "Tunnel Sender Address" are included in the "SESSION"
object [RFC3209], which is mandatory in both Path and Resv messages. object [RFC3209], which is mandatory in both Path and Resv messages.
"LSP ID" will be the same on both directions and it is included in "LSP ID" will be the same on both directions and it is included in
the "SENDER_TEMPLATE" object [RFC3209] which is mandatory in Path the "SENDER_TEMPLATE" object [RFC3209] which is mandatory in Path
messages. messages.
skipping to change at page 9, line 26 skipping to change at page 9, line 31
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 "OAM Configuration 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (3) (IANA) | Length | | BFD Conf. Type (3) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Vers.| PHB |N|S|I| 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: indicates a new type, the "BFD Configuration sub-TLV" (IANA to
define). define).
Length: indicates the total length including sub-TLVs. Length: indicates the total length including sub-TLVs.
skipping to change at page 10, line 24 skipping to change at page 10, line 29
Encapsulation Capability (U): if set, it shows the capability of Encapsulation Capability (U): if set, it shows the capability of
encapsulating BFD messages into UDP packets. If both the G bit and U encapsulating BFD messages into UDP packets. If both the G bit and U
bit are set, configuration gives precedence to the G bit. bit are set, configuration gives precedence to the G bit.
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
transmission and ignored when received.
The "BFD Configuration sub-TLV" MUST include the following sub-TLVs The "BFD Configuration sub-TLV" MUST include the following sub-TLVs
in the Path message: in the Path message:
- "Local Discriminator sub-TLV"; - "Local Discriminator sub-TLV";
- "Negotiation Timer Parameters sub-TLV" if the N flag is cleared. - "Negotiation Timer Parameters sub-TLV" if the N flag is cleared.
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:
- "Local Discriminator sub-TLV;" - "Local Discriminator sub-TLV;"
- "Negotiation Timer Parameters sub-TLV" if: - "Negotiation Timer Parameters sub-TLV" if:
- the N and S flags are cleared - the N and S flags are cleared, or if:
- the N flag is cleared and the S flag is set and a timing
interval larger than the one received needs to be used
Reserved: Reserved for future specification and set to 0. - the N flag is cleared and the S flag is set, and the
Negotiation Timer Parameters sub-TLV received by the egress
contains unsupported values. In this case an updated
Negotiation Timer Parameters sub-TLV, containing values
supported by the egress node, is returned to the ingress.
3.3.1. Local Discriminator sub-TLV 3.3.1. Local Discriminator sub-TLV
The "Local Discriminator sub-TLV" is carried as a sub-TLV of the "BFD The "Local Discriminator 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (1) (IANA) | Length = 8 | | Lcl. Discr. Type (1) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Discriminator | | Local Discriminator
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: indicates a new type, the Local Discriminator sub-TLV (1) (IANA Type: indicates a new type, the Local Discriminator sub-TLV (1) (IANA
to define). to define).
Length: indicates the TLV total length in octets. 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.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timer Neg. Type (2) (IANA) | Length = 20 | | Timer Neg. Type (2) (IANA) | 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: indicates a new type, the "Negotiation Timer Parameters sub-
TLV" (IANA to define). TLV" (IANA to define).
Length: indicates the TLV total length in octets. (20) Length: indicates the TLV total length in octets. (16)
Acceptable Min. Asynchronous TX interval: in case of S (symmetric) Acceptable Min. Asynchronous TX interval: in case of S (symmetric)
flag set in the "BFD Configuration sub-TLV", it expresses the desired flag 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 can reply with an receiving edge LSR can not support such value, it can reply with an
interval greater than the one proposed. interval greater than the one proposed.
In case of S (symmetric) flag cleared in the "BFD Configuration sub- In case of S (symmetric) flag cleared in the "BFD Configuration sub-
TLV", this field expresses the desired time interval (in TLV", this field expresses the desired time interval (in
skipping to change at page 12, line 40 skipping to change at page 12, line 46
rate interval". rate interval".
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 = 8 | | BFD Auth. Type (3) (IANA) | 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: indicates a new type, the "BFD Authentication sub-TLV" (IANA to
define). 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.
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
skipping to change at page 13, line 10 skipping to change at page 13, line 16
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.
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.
Reserved: Reserved for future specification and set to 0. Reserved: Reserved for future specification and set to 0 on
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 functions TLV" has either the L (Loss), D (Delay) or T
(Throughput) flag set, the "Performance Monitoring sub-TLV" MUST be (Throughput) flag set, the "Performance Monitoring sub-TLV" MUST be
present. present.
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", "MPLS OAM PM Loss sub-TLV" MAY
include the following sub-TLVs: include the following sub-TLVs:
skipping to change at page 13, line 33 skipping to change at page 13, line 40
functions TLV"; functions TLV";
- "MPLS OAM PM Delay sub-TLV" if the D flag is set in the "OAM - "MPLS OAM PM Delay sub-TLV" if the D flag is set in the "OAM
functions TLV"; functions 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 "OAM Functions 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 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 (IANA)| Length | | Perf Monitoring Type(4) (IANA)| 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 ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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)
- L: Loss inferred/direct (0=INFERRED, 1=DIRECT) - L: Loss inferred/direct (0=INFERRED, 1=DIRECT)
- J: Delay variation/jitter (1=ACTIVE, 0=NOT ACTIVE) - J: Delay variation/jitter (1=ACTIVE, 0=NOT ACTIVE)
- Y: Dyadic (1=ACTIVE, 0=NOT ACTIVE) - Y: Dyadic (1=ACTIVE, 0=NOT ACTIVE)
- K: Loopback (1=ACTIVE, 0=NOT ACTIVE) - K: Loopback (1=ACTIVE, 0=NOT ACTIVE)
- C: Combined (1=ACTIVE, 0=NOT ACTIVE) - C: Combined (1=ACTIVE, 0=NOT ACTIVE)
Reserved: Reserved for future specification and set to 0 on
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 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) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OTF |T|B| RESERVED | | 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: indicates a new type, the "MPLS OAM PM Loss sub-TLV" (IANA to
define, suggested value 1). define, suggested value 1).
Length: indicates the length of the parameters in octets (12). 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.
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
transmission and ignored when received.
Measurement Interval: the time interval (in microseconds) at which Measurement Interval: the time interval (in microseconds) 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 edge LSR receiving the Path message can not support such value,
it can reply back with a higher interval. By default it is set to it can reply back with a higher interval. By default it is set to
(TBD). (TBD).
Test Interval: test messages interval as described in [RFC6374]. By Test Interval: test messages interval as described in [RFC6374]. By
default it is set to (TBD). default it is set to (TBD).
Loss Threshold: the threshold value of lost packets over which Loss Threshold: the threshold value of lost packets over which
skipping to change at page 15, line 26 skipping to change at page 15, line 40
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 "OAM Functions TLV". TLV of the "OAM Functions 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 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) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OTF |T|B| RESERVED | | 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: indicates a new type, the "MPLS OAM PM Loss sub-TLV" (IANA to
define, suggested value 1). define, suggested value 1).
Length: indicates the length of the parameters in octets (12). 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.
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
transmission and ignored when received.
Measurement Interval: the time interval (in microseconds) at which Measurement Interval: the time interval (in microseconds) 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 edge LSR receiving the Path message can not support such value,
it can reply back with a higher interval. By default it is set to it can reply back with a higher interval. By default it is set to
(TBD). (TBD).
Test Interval: test messages interval as described in [RFC6374]. By Test Interval: test messages interval as described in [RFC6374]. By
default it is set to (TBD). default it is set to (TBD).
Delay Threshold: the threshold value of measured delay (in Delay Threshold: the threshold value of measured delay (in
skipping to change at page 16, line 31 skipping to change at page 16, line 47
it is set to (TBD). it is set to (TBD).
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". the "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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (5) (IANA) | Length = 12 | | MPLS OAM FMS Type (5) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|D|L|C| Reserved (set all to 0s) | PHB | |A|D|L|C| Reserved (set to all 0s) | PHB |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Refresh Timer | | Refresh Timer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: indicates a new type, the "MPLS OAM FMS sub-TLV" (IANA to Type: indicates a new type, the "MPLS OAM FMS sub-TLV" (IANA to
define). define).
Length: indicates the TLV total length in octets. Length: indicates the TLV total length in octets. (12)
Signal Flags should not be processed at intermediate nodes as they Signal Flags should not be processed at intermediate nodes as they
only have an end-point significance. They are used to enable the only have an end-point significance. They are used to enable the
following signals at end points: following signals at end points:
- A: Alarm Indication Signal (AIS) as described in [MPLS-FMS] - A: Alarm Indication Signal (AIS) as described in [MPLS-FMS]
- D: Link Down Indication (LDI) as described in [MPLS-FMS] - D: Link Down Indication (LDI) as described in [MPLS-FMS]
- L: Locked Report (LKR) as described in [MPLS-FMS] - L: Locked Report (LKR) as described in [MPLS-FMS]
- C: Client Signal Failure (CSF) as described in [MPLS-CSF] - C: Client Signal Failure (CSF) as described in [MPLS-CSF]
- Remaining bits: Reserved for future specification and set to 0. - Remaining bits: Reserved for future specification and set to 0.
Reserved: Reserved for future specification and set to 0 on
transmission and ignored when received.
Configuration Flags: Configuration Flags:
- PHB: identifies the per-hop behavior of packets with fault - PHB: identifies the per-hop behavior of packets with fault
management information. It is significant only when C flag is management information. It is significant only when C flag is
set. set.
Refresh Timer: indicates the refresh timer (in microseconds) of fault Refresh Timer: indicates the refresh timer (in microseconds) of fault
indication messages. If the edge LSR receiving the Path message can indication messages. If the edge LSR receiving the Path message can
not support such value, it can reply back with a higher interval. not support such value, it can reply back with a higher interval.
4. IANA Considerations 4. IANA Considerations
This document specifies the following new TLV types: This document specifies the following new TLV types:
- "BFD Configuration" type: 2; - "BFD Configuration" type: 3;
- "MPLS OAM PM Loss" type: 3;
- "MPLS OAM PM Delay" type: 4; - "Performance Monitoring" type: 4;
- "MPLS OAM FMS" type: 5. - "MPLS OAM FMS" type: 5.
sub-TLV types to be carried in the "BFD Configuration sub-TLV": sub-TLV types to be carried in the "BFD Configuration sub-TLV":
- "Local Discriminator" sub-TLV type: 1; - "Local Discriminator" sub-TLV type: 1;
- "Negotiation Timer Parameters" sub-TLV type: 2. - "Negotiation Timer Parameters" sub-TLV type: 2.
- "BFD Authentication" sub-TLV type: 3. - "BFD Authentication" sub-TLV type: 3.
sub-TLV types to be carried in the "BFD Configuration sub-TLV":
- "MPLS OAM PM Loss" type: 1;
- "MPLS OAM PM Delay" type: 2;
5. BFD OAM configuration errors 5. BFD OAM configuration errors
In addition to error values specified in [OAM-CONF-FWK] and [ETH-OAM] In addition to error values specified in [OAM-CONF-FWK] and [ETH-OAM]
this document defines the following values for the "OAM Problem" this document defines the following values for the "OAM Problem"
Error Code: Error Code:
- "MPLS OAM Unsupported Functionality"; - "MPLS OAM Unsupported Functionality";
- "OAM Problem/Unsupported TX rate interval". - "OAM Problem/Unsupported TX rate interval";
- "OAM Problem/Unsupported RX rate interval";
- "OAM Problem/Unsupported unsupported Authentication Type";
- "OAM Problem, mismatch of Authentication Key ID ".
6. 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 7. Security Considerations
The signaling of OAM related parameters and the automatic The signaling of OAM related parameters and the automatic
skipping to change at page 19, line 34 skipping to change at page 20, line 14
"Bidirectional Forwarding Detection (BFD) for MPLS Label "Bidirectional Forwarding Detection (BFD) for MPLS Label
Switched Paths (LSPs)", RFC 5884, June 2010. Switched Paths (LSPs)", RFC 5884, June 2010.
[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.
[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.
[RFC6428] Allan, D., Swallow Ed. , G., and J. Drake Ed. , "Proactive
Connectivity Verification, Continuity Check, and Remote
Defect Indication for the MPLS Transport Profile",
RFC 6428, November 2011.
8.2. Informative References 8.2. Informative References
[BFD-CCCV] [BFD-CCCV]
Allan, D., Swallow, G., and J. Drake, "Proactive Allan, D., Swallow, G., and J. Drake, "Proactive
Connectivity Verification, Continuity Check and Remote Connectivity Verification, Continuity Check and Remote
Defect indication for MPLS Transport Profile", 2010, Defect indication for MPLS Transport Profile", 2010,
<draft-ietf-mpls-tp-bfd-cc-cv-rdi>. <draft-ietf-mpls-tp-bfd-cc-cv-rdi>.
[BFD-Ping] [BFD-Ping]
Bahadur, N., Aggarwal, R., Ward, D., Nadeau, T., Sprecher, Bahadur, N., Aggarwal, R., Ward, D., Nadeau, T., Sprecher,
 End of changes. 47 change blocks. 
61 lines changed or deleted 100 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/