draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-04.txt   draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-05.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: July 13, 2011 P. Skoldstrom, Ed. Expires: September 11, 2011 P. Skoldstrom, Ed.
Acreo AB Acreo AB
D. Ward D. Ward
Juniper Juniper
A. Takacs A. Takacs
Ericsson Ericsson
January 9, 2011 March 10, 2011
Configuration of pro-active MPLS-TP Operations, Administration, and Configuration of pro-active MPLS-TP Operations, Administration, and
Maintenance (OAM) Functions Using RSVP-TE Maintenance (OAM) Functions Using RSVP-TE
draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-04 draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-05
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 common set of TLVs that can be carried on RSVP-TE given LSP using a set of TLVs that can be carried in the RSVP-TE
protocol. protocol.
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 July 13, 2011. This Internet-Draft will expire on September 11, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Contributing Authors . . . . . . . . . . . . . . . . . . . 3 1.1. Contributing Authors . . . . . . . . . . . . . . . . . . . 3
1.2. Requirements Language . . . . . . . . . . . . . . . . . . 4 1.2. Requirements Language . . . . . . . . . . . . . . . . . . 3
1.3. Overview of BFD OAM operation . . . . . . . . . . . . . . 4 1.3. Overview of BFD OAM operation . . . . . . . . . . . . . . 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.2. OAM Configuration TLV . . . . . . . . . . . . . . . . . . 6 3.2. OAM Configuration TLV . . . . . . . . . . . . . . . . . . 7
3.3. BFD Configuration TLV . . . . . . . . . . . . . . . . . . 9 3.3. BFD Configuration sub-TLV . . . . . . . . . . . . . . . . 9
3.3.1. Local Discriminator sub-TLV . . . . . . . . . . . . . 10 3.3.1. Local Discriminator sub-TLV . . . . . . . . . . . . . 10
3.3.2. Negotiation Timer Parameters . . . . . . . . . . . . . 10 3.3.2. Negotiation Timer Parameters sub-TLV . . . . . . . . . 11
3.4. MPLS OAM PM Loss TLV . . . . . . . . . . . . . . . . . . . 12 3.3.3. BFD Authentication sub-TLV . . . . . . . . . . . . . . 12
3.5. MPLS OAM PM Delay TLV . . . . . . . . . . . . . . . . . . 13 3.4. MPLS OAM PM Loss sub-TLV . . . . . . . . . . . . . . . . . 13
3.6. MPLS OAM FMS TLV . . . . . . . . . . . . . . . . . . . . . 14 3.5. MPLS OAM PM Delay sub-TLV . . . . . . . . . . . . . . . . 14
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 3.6. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . . . 15
5. BFD OAM configuration errors . . . . . . . . . . . . . . . . . 15 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 5. BFD OAM configuration errors . . . . . . . . . . . . . . . . . 16
7. Security Considerations . . . . . . . . . . . . . . . . . . . 15 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 7. Security Considerations . . . . . . . . . . . . . . . . . . . 16
8.1. Normative References . . . . . . . . . . . . . . . . . . . 16 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.2. Informative References . . . . . . . . . . . . . . . . . . 17 8.1. Normative References . . . . . . . . . . . . . . . . . . . 17
Appendix A. Additional Stuff . . . . . . . . . . . . . . . . . . 18 8.2. Informative References . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
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 a common set of TLVs carried on RSVP-TE [RFC3209] but given LSP using a common set of TLVs carried on RSVP-TE [RFC3209].
reusable also for LSP Ping [BFD-Ping] as defined in [LSP-PING CONF].
In particular it specifies the mechanisms necessary to establish In particular it specifies the mechanisms necessary to establish
MPLS-TP OAM entities monitoring an LSP and defines information MPLS-TP OAM entities monitoring an LSP and defines information
elements and procedures to configure pro-active MPLS OAM functions. elements and procedures to configure pro-active MPLS OAM functions.
Initialization and control of on-demand MPLS OAM functions are Initialization and control of on-demand MPLS OAM functions are
expected to be carried out by directly accessing network nodes via a expected to be carried out by directly accessing network nodes via a
management interface; hence configuration and control of on-demand management interface; hence configuration and control of on-demand
OAM functions are out-of-scope for this document. OAM functions are out-of-scope for this document.
Pro-active MPLS OAM is based on the Bidirectional Forwarding Pro-active MPLS OAM is based on the Bidirectional Forwarding
Detection (BFD) protocol [RFC5880]. Bidirectional Forwarding Detection (BFD) protocol [RFC5880]. Bidirectional Forwarding
skipping to change at page 4, line 34 skipping to change at page 4, line 28
the use of unidirectional links to support bidirectional paths (co- the use of unidirectional links to support bidirectional paths (co-
routed or bidirectional or associated bidirectional). routed or bidirectional or associated bidirectional).
Each system estimates how quickly it can send and receive BFD packets Each system estimates how quickly it can send and receive BFD packets
in order to come to an agreement with its neighbor about how rapidly in order to come to an agreement with its neighbor about how rapidly
detection of failure will take place. These estimates can be detection of failure will take place. These estimates can be
modified in real time in order to adapt to unusual situations. This modified in real time in order to adapt to unusual situations. This
design also allows for fast systems on a shared medium with a slow design also allows for fast systems on a shared medium with a slow
system to be able to more rapidly detect failures between the fast system to be able to more rapidly detect failures between the fast
systems while allowing the slow system to participate to the best of systems while allowing the slow system to participate to the best of
its ability. its ability. However, in some cases one may want to configure these
timers manually, in those cases the TLVs defined in this document can
be used.
The ability of each system to control the BFD packet transmission The ability of each system to control the BFD packet transmission
rate in both directions provides a mechanism for congestion control, rate in both directions provides a mechanism for congestion control,
particularly when BFD is used across multiple network hops. particularly when BFD is used across multiple network hops.
As recommended in [BFD-CCCV], the BFD tool needs to be extended for As recommended in [BFD-CCCV], the BFD tool needs to be extended for
the proactive CV functionality by the addition of an unique the proactive CV functionality by the addition of an unique
identifier in order to meet the requirements. The document in [BFD- identifier in order to meet the requirements. The document in [BFD-
CCCV] specifies the BFD extension and behavior to meet the CCCV] specifies the BFD extension and behavior to meet the
requirements for MPLS-TP proactive Continuity Check and Connectivity requirements for MPLS-TP proactive Continuity Check and Connectivity
skipping to change at page 5, line 45 skipping to change at page 5, line 41
3.1. MPLS OAM Configuration Operation Overview 3.1. MPLS OAM Configuration Operation Overview
RSVP-TE, or in alternative LSP Ping [LSP-PING CONF], can be used to RSVP-TE, or in alternative LSP Ping [LSP-PING CONF], can be used to
simply establish (i.e., bootstrap) a BFD session or it can simply establish (i.e., bootstrap) a BFD session or it can
selectively enable and configure all pro-active MPLS OAM functions. selectively enable and configure all pro-active MPLS OAM functions.
For this specification, BFD MUST be run in asynchronous mode and both For this specification, BFD MUST be run in asynchronous mode and both
sides should be in active mode. sides should be in active mode.
In the simplest scenario RSVP-TE, or in alternative LSP Ping [LSP- In the simplest scenario RSVP-TE, or in alternative LSP Ping [LSP-
PING CONF], is used only to bootstrap the BFD session. In this case PING CONF], is used only to bootstrap the BFD session. In this case
the initiating node includes an 'OAM Configuration TLV' in the the initiating node includes an "OAM Configuration TLV" in the
message it sends to the receiving node at the other end of the LSP. message it sends to the receiving node at the other end of the LSP.
The OAM Type in the 'OAM Configuration TLV' is set to 'MPLS OAM', the The OAM Type in the "OAM Configuration TLV" is set to "MPLS OAM", the
CC OAM Function flag is set, and a 'BFD Configuration sub-TLV' is CC OAM Function flag is set, and a "BFD Configuration sub-TLV" is
included. The sub-TLV carries a 'Local Discriminator sub-TLV' with included. The sub-TLV carries a "Local Discriminator sub-TLV" with
the discriminator value selected by the initiating node for the BFD the discriminator value selected by the initiating node for the BFD
session associated with the LSP. The N flag in the 'BFD session associated with the LSP. The N flag in the "BFD
Configuration sub-TLV' MUST be set to enable timer negotiation/ Configuration sub-TLV" MUST be set to enable timer negotiation/
re-negotiation via BFD Control Messages. re-negotiation via BFD Control Messages.
The receiving node MUST use the Local Discriminator value it receives The receiving node MUST use the Local Discriminator value it receives
to identify the remote end of the BFD session. The receiving node to identify the remote end of the BFD session. The receiving node
must send a message to the initiating node that includes an 'OAM must send a message to the initiating node that includes an "OAM
Configuration TLV' containing the same values as it received, except Configuration TLV" containing the same values as it received, except
for the 'Local Discriminator sub-TLV', which contains the local for the "Local Discriminator sub-TLV", which contains the local
discriminator value selected by the receiving node for the BFD discriminator value selected by the receiving node for the BFD
session. session.
Timer negotiation is performed in subsequent BFD control messages. Timer negotiation is performed in subsequent BFD control messages.
This operation is similar to LSP Ping based bootstrapping described This operation is similar to LSP Ping based bootstrapping described
in [RFC5884]. in [RFC5884].
If timer negotiation is to be done using the TLVs defined in this If timer negotiation is to be done using the TLVs defined in this
document rather than with BFD Control Messages, the N flag MUST be document rather than with BFD Control packets, the N flag MUST be
cleared and a 'Timer Negotiation Parameters sub-TLV' MUST be present cleared and a "Timer Negotiation Parameters sub-TLV" MUST be present
in the 'BFD Configuration sub-TLV'. In this case, there are two in the "BFD Configuration sub-TLV". In this case, there are two
configuration options, symmetric and asymmetric. If symmetric configuration options, symmetric and asymmetric. If symmetric
configuration is used, the S flag in 'BFD Configuration sub-TLV' MUST configuration is used, the S flag in "BFD Configuration sub-TLV" MUST
be set. If the flag is cleared, the configuration is completed be set. If the flag is cleared, the configuration is completed
asymmetrically in the two directions. Section 3.3.2 includes a asymmetrically in the two directions. Section 3.3.2 includes a
detailed explanation of such configuration. detailed explanation of such configuration.
In the case of the "CV/CC mode" OAM [BFD-CCCV], the "CV" flag MUST be In the case of the "CV/CC mode" OAM [BFD-CCCV], the "CV" flag MUST be
set in addition to the CC flag in the "OAM Configuration TLV". The set in addition to the CC flag in the "OAM Configuration TLV". The
information required to support this functionality is defined in information required to support this functionality is defined in
[MPLS-TP-IDENTIF]. If RSVP-TE is used, this information is found [MPLS-TP-IDENTIF]. If RSVP-TE is used, this information is found
respectively in the SESSION and SENDER_TEMPLATE object with no need respectively in the SESSION and SENDER_TEMPLATE object with no need
of further sub-TLV as described in section 3.2. In case of LSP Ping of additional sub-TLVs as described in section 3.2.
configuration this information is supplied by an additional sub-TLV,
but this is defined in [LSP-PING CONF] and it is outside the scope of When BFD Control packets are transported in the G-ACh they are not
this document. protected by any end-to-end checksum, only lower-layers are providing
error detection/correction. A single bit error, e.g. a flipped bit
in the BFD State field could cause the receiving end to wrongly
conclude that the link is down and thus trigger protection switching.
To prevent this from happening the "BFD Configuration sub-TLV" has an
Integrity flag that when set enables BFD Authentication using Keyed
SHA1 with an empty key (all 0s) [RFC5880]. This would make every BFD
Control packet carry an SHA1 hash of itself that can be used to
detect errors.
If BFD Authentication using a shared key / password is desired (i.e.
actual authentication not only error detection) the "BFD
Authentication sub-TLV" MUST be included in the "BFD Configuration
sub-TLV". The "BFD Authentication sub-TLV" is used to specify which
authentication method that should be used and which shared key /
password that should be used for this particular session. How the
key exchange is performed is out of scope of this document.
Additional OAM functions may be configured by setting the appropriate
flags in the "OAM Functions TLV", these include Performance
Measurements (packet loss and packet delay) and Fault Management
Signal handling.
By setting the PM Loss flag in the "OAM Functions TLV" and including
the "MPLS OAM PM Loss sub-TLV" one can configure the measurement
interval and loss threshold values for triggering protection.
Delay measurements are configured by setting PM Delay flag in the
"OAM Functions TLV" and including the "MPLS OAM PM Loss sub-TLV" one
can configure the measurement interval and the delay threshold values
for triggering protection.
To configure Fault Monitoring Signals and their refresh time the FMS
flag in the "OAM Functions TLV" MUST be set and the "MPLS OAM FMS
sub-TLV" included.
3.2. OAM Configuration TLV 3.2. OAM Configuration TLV
The "OAM Configuration TLV" is depicted in the following figure. It The "OAM Configuration TLV" is depicted in the following figure. It
specifies the OAM functions that are to be used for the subject LSP specifies the OAM functions that are to be used for the subject LSP
and it is defined in [OAM-CONF-FWK]. For RSVP-TE, the "OAM and it is defined in [OAM-CONF-FWK]. The "OAM Configuration TLV" is
Configuration TLV" is carried in the LSP_ATTRIBUTES object in Path carried in the LSP_ATTRIBUTES object in Path and Resv messages.
and Resv messages.
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 (2) (IANA) | Length | | Type (2) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OAM Type | Reserved | | OAM Type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ sub-TLVs ~ ~ sub-TLVs ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: indicates the "OAM Configuration TLV" (2) (IANA to assign). Type: indicates the "OAM Configuration TLV" (2) (IANA to assign).
OAM Type: one octet that specifies the technology specific OAM Type. OAM Type: one octet that specifies the technology specific OAM Type.
If the requested OAM Type is not supported, an error must be If the requested OAM Type is not supported, an error must be
generated: "OAM Problem/Unsupported OAM Type". generated: "OAM Problem/Unsupported OAM Type".
This document defines a new OAM Type: "MPLS OAM" (suggested value 2, This document defines a new OAM Type: "MPLS OAM" (suggested value 2,
IANA to assign) from the "RSVP-TE OAM Configuration Registry". The IANA to assign) from the "RSVP-TE OAM Configuration Registry". The
"MPLS OAM" type is set to request the establishment of OAM functions "MPLS OAM" type is set to request the establishment of OAM functions
skipping to change at page 7, line 38 skipping to change at page 8, line 17
The receiving edge LSR when the MPLS-TP OAM Type is requested should The receiving edge LSR when the MPLS-TP OAM Type is requested should
check which OAM Function Flags are set in the "Function Flags TLV" check which OAM Function Flags are set in the "Function Flags TLV"
and look for the corresponding technology specific configuration TLV. and look for the corresponding technology specific configuration TLV.
Additional corresponding sub-TLVs are as follows: Additional corresponding sub-TLVs are as follows:
- "BFD Configuration sub-TLV", which MUST be included if the CC - "BFD Configuration sub-TLV", which MUST be included if the CC
OAM Function flag is set. This sub-TLV MUST carry a "BFD Local OAM Function flag is set. This sub-TLV MUST carry a "BFD Local
Discriminator sub-TLV" and a "Timer Negotiation Parameters sub- Discriminator sub-TLV" and a "Timer Negotiation Parameters sub-
TLV" if the N flag is cleared. TLV" if the N flag is cleared. It MAY carry a "BFD Authentication
sub-TLV" if the I flag is set. If the I flag is set but no "BFD
Authentication sub-TLV" is included Keyed SHA1 with an empty key
is used.
- "MPLS OAM PM Loss sub-TLV", which MAY be included if the PM/Loss - "MPLS OAM PM Loss sub-TLV", which MAY be included if the PM/Loss
OAM Function flag is set. If the "MPLS OAM PM Loss sub-TLV" is OAM Function flag is set. If the "MPLS OAM PM Loss sub-TLV" is
not included, default configuration values are used. not included, default configuration values are used.
- "MPLS OAM PM Delay sub-TLV", which MAY be included if the PM/ - "MPLS OAM PM Delay sub-TLV", which MAY be included if the PM/
Delay OAM Function flag is set. If the "MPLS OAM PM Delay sub- Delay OAM Function flag is set. If the "MPLS OAM PM Delay sub-
TLV" is not included, default configuration values are used. TLV" is not included, 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, 'Unique MEP-ID of Source', MUST be included in case
the configuration is done with LSP Ping and CV flag is set as
defined in [LSP-PING CONF]. But this is outside the scope of this
document.
Moreover, if the CV flag is set, the CC flag MUST be set at the same Moreover, if the CV flag is set, the CC flag MUST be set at the same
time. The format of an MPLS-TP CV/CC message is shown in [BFD-CCCV] time. The format of an MPLS-TP CV/CC message is shown in [BFD-CCCV]
and it requires, together with the BFD control packet information, and it requires, together with the BFD control packet information,
the "Unique MEP-ID of source of BFD packet". [MPLS-TP-IDENTIF] the "Unique MEP-ID of source of BFD packet". [MPLS-TP-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>
GMPLS signaling [RFC3473] uses a 5-tuple to uniquely identify an LSP GMPLS signaling [RFC3473] uses a 5-tuple to uniquely identify an LSP
skipping to change at page 8, line 40 skipping to change at page 9, line 18
- 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.
In case the configuration is done via LSP Ping [LSP-PING CONF] the
'Unique MEP-ID of Source' is needed to supply this information but
this is defined in [LSP-PING CONF] and it is outside the scope of
this document.
[Author's note: the same "Unique MEP-ID of source" will be likely [Author's note: the same "Unique MEP-ID of source" will be likely
required for Performance monitoring purposes. However for the moment required for Performance monitoring purposes. However for the moment
in [MPLS-PM] it is stated: "The question of ACH TLV usage and the in [MPLS-PM] it is stated: "The question of ACH TLV usage and the
manner of supporting metadata such as authentication keys and node manner of supporting metadata such as authentication keys and node
identifiers is deliberately omitted. These issues will be addressed identifiers is deliberately omitted. These issues will be addressed
in a future version of the document."] in a future version of the document."]
3.3. BFD Configuration TLV 3.3. BFD Configuration sub-TLV
The "BFD Configuration TLV" (depicted below) is defined for BFD OAM The "BFD Configuration sub-TLV" (depicted below) is defined for BFD
specific configuration parameters. The "BFD Configuration TLV" is OAM specific configuration parameters. The "BFD Configuration sub-
carried as a sub-TLV of the "OAM Configuration TLV". TLV" is carried as a sub-TLV of the "OAM Configuration TLV".
This new TLV accommodates generic BFD OAM information and carries This TLV accommodates generic BFD OAM information and carries sub-
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 | | Type (3) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Vers.| PHB |N|S| Reserved (set to all 0s) | |Vers.| PHB |N|S|I| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ sub TLVs ~ ~ sub-TLVs ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: indicates a new type, the "BFD Configuration 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.
Version: identifies the BFD protocol version. If a node does not Version: identifies the BFD protocol version. If a node does not
support a specific BFD version an error must be generated: "OAM support a specific BFD version an error must be generated: "OAM
Problem/Unsupported OAM Version &rdquo". Problem/Unsupported OAM 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.
The "BFD Configuration TLV" MUST include the following sub-TLVs in Symmetric session (S): If set the BFD session MUST use symmetric
the Path message: timing values.
Integrity (I): If set BFD Authentication MUST be enabled. If the
"BFD Configuration sub-TLV" does not include a "BFD Authentication
sub-TLV" the authentication MUST use Keyed SHA1 with an empty pre-
shared key (all 0s).
The "BFD Configuration sub-TLV" MUST include the following sub-TLVs
in the Path message:
- "Local Discriminator sub-TLV"; - "Local Discriminator sub-TLV";
- "Negotiation Timer Parameters sub-TLV" if N flag is cleared. - "Negotiation Timer Parameters sub-TLV" if N flag is cleared.
The "BFD Configuration TLV" MUST include the following sub-TLVs in The "BFD Configuration sub-TLV" MUST include the following sub-TLVs
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:
- N flag and S are cleared - N flag and S are cleared
- N flag is cleared and S flag is set and a timing value higher - N flag is cleared and S flag is set and a timing value higher
than the one received needs to be used than the one received needs to be used
Reserved: Reserved for future specification and set to 0.
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. It 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 | | Type (1) (IANA) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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.
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 3.3.2. Negotiation Timer Parameters sub-TLV
The "Negotiation Timer Parameters sub-TLV" is depicted below. The "Negotiation Timer Parameters sub-TLV" is carried as a sub-TLV of
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Req. TX int. Type (2) (IANA) | Length = 20 | | Timer Neg. Type (2) (IANA) | Length = 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Detect. Mult.| Reserved | | Detect. Mult.| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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. Length: indicates the TLV total length in octets. (20)
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" TLV, it expresses the desired flag set in the "BFD Configuration sub-TLV", it expresses the desired
time interval (in microseconds) at which the LER initiating the time interval (in microseconds) at which the LER initiating the
signaling intends to both transmit and receive BFD periodic control signaling intends to both transmit and receive BFD periodic control
packets. If the receiving edge LSR can not support such value, it is packets. If the receiving edge LSR can not support such value, it is
allowed to reply back with an interval greater than the one proposed. allowed to reply back with an interval greater than the one proposed.
In case of S (symmetric) flag cleared in the "BFD Configuration TLV", In case of S (symmetric) flag cleared in the "BFD Configuration sub-
this field expresses the desired time interval (in microseconds) at TLV", this field expresses the desired time interval (in
which a edge LSR intends to transmit BFD periodic control packets in microseconds) at which a edge LSR intends to transmit BFD periodic
its transmitting direction. control packets in its transmitting direction.
Acceptable Min. Asynchronous RX interval: in case of S (symmetric) Acceptable Min. Asynchronous RX interval: in case of S (symmetric)
flag set in the "BFD Configuration TLV", this field MUST be equal to flag set in the "BFD Configuration sub-TLV", this field MUST be equal
"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 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 TLV", In case of S (symmetric) flag cleared in the "BFD Configuration sub-
it expresses the minimum time interval (in microseconds) at which TLV", it expresses the minimum time interval (in microseconds) at
edge LSRs can receive BFD periodic control packets. In case this which edge LSRs can receive BFD periodic control packets. In case
value is greater than the "Acceptable Min. Asynchronous TX interval" this value is greater than the "Acceptable Min. Asynchronous TX
received from the other edge LSR, such edge LSR MUST adopt the interval" received from the other edge LSR, such edge LSR MUST adopt
interval expressed in this "Acceptable Min. Asynchronous RX the interval expressed in this "Acceptable Min. Asynchronous RX
interval". 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 receiving system can
not support this value an error MUST be generated "Unsupported BFD TX not support this value an error MUST be generated "Unsupported BFD TX
rate interval". rate interval".
Detection time multiplier: The negotiated transmit interval, Detection time multiplier: The negotiated transmit interval,
multiplied by this value, provides the Detection Time for the multiplied by this value, provides the Detection Time for the
receiving system in Asynchronous mode. receiving system in Asynchronous mode.
skipping to change at page 12, line 16 skipping to change at page 12, line 38
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 receiving system can
not support this value an error MUST be generated "Unsupported BFD TX not support this value an error MUST be generated "Unsupported BFD TX
rate interval". rate interval".
Detection time multiplier: The negotiated transmit interval, Detection time multiplier: The negotiated transmit interval,
multiplied by this value, provides the Detection Time for the multiplied by this value, provides the Detection Time for the
receiving system in Asynchronous mode. receiving system in Asynchronous mode.
3.4. MPLS OAM PM Loss TLV Reserved: Reserved for future specification and set to 0.
The "MPLS OAM PM Loss TLV" depicted below is carried as a sub-TLV of 3.3.3. BFD Authentication sub-TLV
the "OAM Configuration TLV".
The "BFD Authentication sub-TLV" is carried as a sub-TLV of the "BFD
Configuration sub-TLV" and is depicted below.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BFD Auth. Type (3) (IANA) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Auth Type | Auth Key ID | Reserved (0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: indicates a new type, the "BFD Authentication sub-TLV" (IANA to
define).
Length: indicates the TLV total length in octets. (8)
Auth Type: indicates which type of authentication to use. The same
values as are defined in section 4.1 of [RFC5880] are used.
Auth Key ID: indicates which authentication key or password
(depending on Auth Type) should be used. How the key exchange is
performed is out of scope of this document.
Reserved: Reserved for future specification and set to 0.
3.4. MPLS OAM PM Loss sub-TLV
The "MPLS OAM PM Loss sub-TLV" depicted below is carried as a sub-TLV
of 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PM Loss Type (3) (IANA) | Length = 16 | | PM Loss Type (3) (IANA) | Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Vers.|E|C| | Reserved | PHB | |Vers.|E|C| | Reserved (set to all 0s) | PHB |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Interval | | Measurement Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Loss Threshold | | Loss Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: indicates a new type, the "PM Loss" (IANA to define). Type: indicates a new type, the "MPLS OAM PM Loss" (IANA to define).
Length: indicates the TLV total length in octets. Length: indicates the TLV total length in octets.
Version: indicates the Loss measurement protocol version. Version: indicates the Loss measurement protocol version.
Configuration Flags: Configuration Flags:
- E: exclude from the Loss Measurement all G-ACh messages - E: exclude from the Loss Measurement all G-ACh messages
- C: require the use of a counter in the "Querier Context" field - C: require the use of a counter in the "Querier Context" field
skipping to change at page 13, line 11 skipping to change at page 14, line 14
information. information.
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. it can reply back with a higher interval.
Loss Threshold: the threshold value of lost packets over which Loss Threshold: the threshold value of lost packets over which
protections MUST be triggered. protections MUST be triggered.
3.5. MPLS OAM PM Delay TLV 3.5. MPLS OAM PM Delay sub-TLV
The "MPLS OAM PM Delay TLV" depicted below is carried as a sub-TLV of The "MPLS OAM PM Delay sub-TLV" depicted below is carried as a sub-
the "OAM Configuration TLV". TLV of 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PM Delay Type (4) (IANA) | Length = 16 | | PM Delay Type (4) (IANA) | Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Vers.| Flags | Reserved | PHB | |Vers.| Flags | Reserved (set to all 0s) | PHB |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Interval | | Measurement Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delay Threshold | | Delay Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: indicates a new type, the "PM Delay" (IANA to define). Type: indicates a new type, the "MPLS OAM PM Delay" (IANA to define).
Length: indicates the TLV total length in octets. Length: indicates the TLV total length in octets.
Version: indicates the Delay measurement protocol version. Version: indicates the Delay measurement protocol version.
Configuration Flags: Configuration Flags:
- E: exclude from the Loss Measurement all G-ACh messages - E: exclude from the Loss Measurement all G-ACh messages
- C: require the use of a counter in the "Querier Context" field - C: require the use of a counter in the "Querier Context" field
skipping to change at page 14, line 5 skipping to change at page 15, line 7
- Remaining bits: Reserved for future specification and set to 0. - Remaining bits: Reserved for future specification and set to 0.
PHB: - identifies the per-hop behavior of packets with delay PHB: - identifies the per-hop behavior of packets with delay
information. information.
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. it can reply back with a higher interval.
Delay Threshold: the threshold value of lost packets over which Delay Threshold: the threshold value of measured delay (in
protections MUST be triggered. microseconds) over which protections MUST be triggered.
[Author's note: TBD if we want to include the timestamp format [Author's note: TBD if we want to include the timestamp format
negotiation as in [MPLS-PM] 4.2.5.] negotiation as in [MPLS-PM] 4.2.5.]
3.6. MPLS OAM FMS TLV 3.6. MPLS OAM FMS sub-TLV
The "MPLS OAM FMS TLV" depicted below is carried as a sub-TLV of the The "MPLS OAM FMS sub-TLV" depicted below is carried as a sub-TLV of
"OAM Configuration 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) | | Type (5) (IANA) | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|D|L|C| Reserved | |E| PHB | |A|D|L|C| Reserved (set all to 0s) |E| PHB |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Refresh Timer | | Refresh Timer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: indicates a new type, the "PM Delay" (IANA to define). Type: indicates a new type, the "MPLS OAM FMS" (IANA to define).
Length: indicates the TLV total length in octets. Length: indicates the TLV total length in octets.
Signal Flags: are used to enable the following signals: Signal Flags: are used to enable the following signals:
- 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.
Configuration Flags: Configuration Flags:
- E: used to enable/disable explicitly clearing faults - E: used to enable/disable explicitly clearing faults
- PHB: identifies the per-hop behavior of packets with fault - PHB: identifies the per-hop behavior of packets with fault
management information management information
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.
skipping to change at page 15, line 15 skipping to change at page 16, line 19
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: 2;
- "MPLS OAM PM Loss" type: 3; - "MPLS OAM PM Loss" type: 3;
- "MPLS OAM PM Delay" type: 4; - "MPLS OAM PM Delay" type: 4;
- "MPLS OAM PM 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.
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".
skipping to change at page 17, line 30 skipping to change at page 18, line 39
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,
N., and Y. Weingarten, "LSP-Ping and BFD encapsulation N., and Y. Weingarten, "LSP Ping and BFD encapsulation
over ACH", 2010, over ACH", 2010,
<draft-ietf-mpls-tp-lsp-ping-bfd-procedures-02>. <draft-ietf-mpls-tp-lsp-ping-bfd-procedures-02>.
[ETH-OAM] Takacs, A., Gero, B., Fedyk, D., Mohan, D., and D. Long, [ETH-OAM] Takacs, A., Gero, B., Fedyk, D., Mohan, D., and D. Long,
"GMPLS RSVP-TE Extensions for Ethernet OAM", 2009, "GMPLS RSVP-TE Extensions for Ethernet OAM", 2009,
<draft-ietf-ccamp-rsvp-te-eth-oam-ext>. <draft-ietf-ccamp-rsvp-te-eth-oam-ext>.
[LSP Ping] [LSP Ping]
Kompella, K. and G. Swallow, "Detecting Multi-Protocol Kompella, K. and G. Swallow, "Detecting Multi-Protocol
Label Switched (MPLS) Data Plane Failures", 2006, <RFC Label Switched (MPLS) Data Plane Failures", 2006, <RFC
3479>. 3479>.
[LSP-PING CONF] [LSP-PING CONF]
Bellagamba, E., Andersson, L., Ward, D., and P. Bellagamba, E., Andersson, L., Ward, D., and P.
Skoelstroem, "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", 2010, Functions Using LSP Ping", 2010,
<draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf>. <draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf>.
[MPLS-TP OAM Analysis] [MPLS-TP OAM Analysis]
Sprecher, N., Weingarten, Y., and E. Bellagamba, "MPLS-TP Sprecher, N., Weingarten, Y., and E. Bellagamba, "MPLS-TP
OAM Analysis", 2011, <draft-ietf-mpls-tp-oam-analysis>. OAM Analysis", 2011, <draft-ietf-mpls-tp-oam-analysis>.
[MPLS-TP-OAM-FWK] [MPLS-TP-OAM-FWK]
Bocci, M. and D. Allan, "Operations, Administration and Bocci, M. and D. Allan, "Operations, Administration and
skipping to change at page 18, line 18 skipping to change at page 19, line 29
2010, <draft-ietf-mpls-tp-oam-framework>. 2010, <draft-ietf-mpls-tp-oam-framework>.
[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 5921, July 2010. RFC 5921, July 2010.
Appendix A. Additional Stuff
This becomes an Appendix.
Authors' Addresses Authors' Addresses
Elisa Bellagamba (editor) Elisa Bellagamba (editor)
Ericsson Ericsson
Farogatan 6 Farogatan 6
Kista, 164 40 Kista, 164 40
Sweden Sweden
Phone: +46 761440785 Phone: +46 761440785
Email: elisa.bellagamba@ericsson.com Email: elisa.bellagamba@ericsson.com
 End of changes. 66 change blocks. 
129 lines changed or deleted 194 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/