draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-08.txt   draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-09.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: October 15, 2012 P. Skoldstrom, Ed. Expires: April 10, 2013 P. Skoldstrom, Ed.
Acreo AB Acreo AB
D. Ward D. Ward
Juniper Juniper
A. Takacs A. Takacs
Ericsson Ericsson
April 13, 2012 October 7, 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-08 draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-09
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 October 15, 2012. This Internet-Draft will expire on April 10, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 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
skipping to change at page 2, line 27 skipping to change at page 2, line 27
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
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 . . . . . . 7
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 . . . . . . . . . . . . . 11 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 . . . . . . . . . . . . . . 13
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 . . . . . . . . . . . . . . 16
3.5. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . . . 16 3.5. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . . . 17
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
5. BFD OAM configuration errors . . . . . . . . . . . . . . . . . 18 5. BFD OAM configuration errors . . . . . . . . . . . . . . . . . 18
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19
7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 7. Security Considerations . . . . . . . . . . . . . . . . . . . 19
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.1. Normative References . . . . . . . . . . . . . . . . . . . 19 8.1. Normative References . . . . . . . . . . . . . . . . . . . 19
8.2. Informative References . . . . . . . . . . . . . . . . . . 20 8.2. Informative References . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 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
skipping to change at page 5, line 27 skipping to change at page 5, line 27
configurable: 1) whether or not the LOC defect should result in configurable: 1) whether or not the LOC defect should result in
blocking the outgoing data traffic; 2) whether or not the "Period blocking the outgoing data traffic; 2) whether or not the "Period
Misconfiguration defect" should result in a signal fail condition. Misconfiguration defect" should result in a signal fail condition.
3. Theory of Operations 3. Theory of Operations
3.1. MPLS OAM Configuration Operation Overview 3.1. MPLS OAM Configuration Operation Overview
RSVP-TE, or alternatively LSP Ping [LSP-PING CONF], can be used to RSVP-TE, or alternatively LSP Ping [LSP-PING CONF], can be used to
simply enable the different OAM functions, by setting the simply enable the different OAM functions, by setting the
corresponding flags in the "OAM Functions TLV". Additionally one may corresponding flags in the "OAM Functions TLV". For a more detailed
include sub-TLVs for the different OAM functions in order to specify configuration one may include sub-TLVs for the different OAM
different parameters in detail. functions in order to specify various parameters in detail.
The presence of OAM configuration TLVs at intermediate nodes is Typically intermediate nodes should not process or modify any of the
justified because the mid-points need to forward the RSVP-TE message OAM configuration TLVs but simply forward them to the end-node.
to the end point. No TLV processing or modification or following OAM There is one exception to this and that is if the "MPLS OAM FMS sub-
actions need to be taken at the intermediate points. TLV" is present. This sub-TLV has to be examined even by
intermediate nodes. The sub-TLV MAY be present if a flag is set in
the "Function Flags sub-TLV", see section [3.2. OAM Configuration
TLV].
3.1.1. Configuration of BFD sessions 3.1.1. Configuration of BFD sessions
For this specification, BFD MUST be run in either one of the two For this specification, BFD MUST be run in either one of the two
modes: modes:
- Asynchronous mode, where both sides should be in active mode - Asynchronous mode, where both sides should be in active mode
- Unidirectional mode - Unidirectional mode
skipping to change at page 6, line 31 skipping to change at page 6, line 34
sub-TLV". The "BFD Authentication sub-TLV" is used to specify which sub-TLV". The "BFD Authentication sub-TLV" is used to specify which
authentication method that should be used and which pre-shared key / authentication method that should be used and which pre-shared key /
password that should be used for this particular session. How the password that should be used for this particular session. How the
key exchange is performed is out of scope of this document. key exchange is performed is out of scope of this document.
3.1.2. Configuration of Performance Monitoring 3.1.2. Configuration of Performance Monitoring
It is possible to configure Performance Monitoring functionalities It is possible to configure Performance Monitoring functionalities
such as Loss, Delay and Throughput as described in [RFC6374]. such as Loss, Delay and Throughput as described in [RFC6374].
When configuring Performance monitoring functionalities it can be When configuring Performance monitoring functionalities it is
chosen either the default configuration (by only setting the possible to choose either the default configuration, by only setting
respective flags in the "OAM functions TLV") or a customized the respective flags in the "OAM functions TLV", or a customized
configuration (by including the respective Loss and/or Delay sub- configuration. To customize the configuration one would set the
TLVs). respective flags in the including the respective Loss and/or Delay
sub-TLVs).
3.1.3. Configuration of Fault Management Signals
Additional OAM functions may be configured by setting the appropriate
flags in the "OAM Functions TLV", these include Performance
Measurements (packet loss, throughput, delay, and delay variation)
and Fault Management Signal handling.
By setting the PM Loss flag in the "OAM Functions TLV" and including 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 the "MPLS OAM PM Loss sub-TLV" one can configure the measurement
interval and loss threshold values for triggering protection. interval and loss threshold values for triggering protection.
Delay measurements are configured by setting PM Delay flag in the Delay measurements are configured by setting PM Delay flag in the
"OAM Functions TLV" and including the "MPLS OAM PM Loss sub-TLV" one "OAM Functions TLV" and including the "MPLS OAM PM Loss sub-TLV" one
can configure the measurement interval and the delay threshold values can configure the measurement interval and the delay threshold values
for triggering protection. for triggering protection.
3.1.3. Configuration of Fault Management Signals
To configure Fault Monitoring Signals and their refresh time the FMS 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 flag in the "OAM Functions TLV" MUST be set and the "MPLS OAM FMS
sub-TLV" included. If an intermediate point is meant to originate sub-TLV" included. When configuring Fault Monitoring Signals it can
fault management signal messages this mean that such intermediate be chosen either the default configuration (by only setting the
point is associated to a server MEP through a co-located MPLS-TP respective flags in the "OAM functions TLV") or a customized
client/server adaptation function and such server MEP needs to be configuration (by including the "MPLS OAM FMS sub-TLV").
configured by its own RSVP-TE session (or, in alternative, NMS or LSP
ping). If an intermediate point is meant to originate fault management
signal messages this means that such an intermediate point is
associated to a server MEP through a co-located MPLS-TP client/server
adaptation function. Such a server MEP needs to be configured by its
own RSVP-TE session (or, alternatively, via an NMS or LSP-ping).
However, by setting the "Fault Management subscription" flag in the
"MPLS OAM FMS sub-TLV" a client LSP can indicate that it would like
an association to be created to the server MEP(s) on any intermediate
nodes.
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 LSP and it is specifies the OAM functions that are to be used for the LSP and it is
defined in [OAM-CONF-FWK]. The "OAM Configuration TLV" is carried in defined in [OAM-CONF-FWK]. The "OAM Configuration TLV" is carried in
the LSP_ATTRIBUTES object in Path and Resv messages. the LSP_ATTRIBUTES object in Path 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
skipping to change at page 9, line 28 skipping to change at page 9, line 37
3.3. BFD Configuration sub-TLV 3.3. BFD Configuration sub-TLV
The "BFD Configuration sub-TLV" (depicted below) is defined for BFD The "BFD Configuration sub-TLV" (depicted below) is defined for BFD
OAM specific configuration parameters. The "BFD Configuration sub- OAM specific configuration parameters. The "BFD Configuration sub-
TLV" is carried as a sub-TLV of the "OAM Configuration TLV". TLV" is carried as a sub-TLV of the "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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BFD Conf. Type (3) (IANA) | Length | | BFD Conf. Type (3) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Vers.| PHB |N|S|I|G|U|B| Reserved (set to all 0s) | |Vers.| PHB |N|S|I|G|U|B| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ sub-TLVs ~ ~ sub-TLVs ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: indicates a new type, the "BFD Configuration sub-TLV" (IANA to Type: 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". Problem/Unsupported OAM Version".
skipping to change at page 11, line 15 skipping to change at page 11, line 27
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Lcl. Discr. Type (1) (IANA) | Length | | 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. (8) Length: indicates the TLV total length in octets. (8)
Local Discriminator: A unique, nonzero discriminator value generated Local Discriminator: A unique, nonzero discriminator value generated
by the transmitting system and referring to itself, used to by the transmitting system and referring to itself, used to
demultiplex multiple BFD sessions between the same pair of systems. demultiplex multiple BFD sessions between the same pair of systems.
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 | | 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. (16) Length: indicates the TLV total length in octets. (16)
Acceptable Min. Asynchronous TX interval: in case of S (symmetric) Acceptable Min. Asynchronous TX interval: 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
skipping to change at page 13, line 31 skipping to change at page 14, line 4
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:
- "MPLS OAM PM Loss sub-TLV" if the L flag is set in the "OAM - "MPLS OAM PM Loss sub-TLV" if the L flag is set in the "OAM
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
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Perf Monitoring Type(4) (IANA)| Length | | Perf Monitoring Type(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 ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 14, line 28 skipping to change at page 15, line 5
- C: Combined (1=ACTIVE, 0=NOT ACTIVE) - C: Combined (1=ACTIVE, 0=NOT ACTIVE)
Reserved: Reserved for future specification and set to 0 on Reserved: Reserved for future specification and set to 0 on
transmission and ignored when received. transmission and ignored when received.
3.4.1. MPLS OAM PM Loss sub-TLV 3.4.1. MPLS OAM PM Loss sub-TLV
The "MPLS OAM PM Loss sub-TLV" depicted below is carried as a sub-TLV The "MPLS OAM PM Loss sub-TLV" depicted below is carried as a sub-TLV
of the "Performance Monitoring sub-TLV". of the "Performance Monitoring sub-TLV".
0 1 2 3 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
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 (set to all 0s) | | OTF |T|B| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Interval | | Measurement Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Test Interval | | Test Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Loss Threshold | | Loss Threshold |
skipping to change at page 15, line 36 skipping to change at page 16, line 11
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
protections MUST be triggered. By default it is set to (TBD). protections MUST be triggered. By default it is set to (TBD).
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
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 (set to all 0s) | | OTF |T|B| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Interval | | Measurement Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Test Interval | | Test Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delay Threshold | | Delay Threshold |
skipping to change at page 16, line 42 skipping to change at page 17, line 18
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
microseconds) over which protections MUST be triggered. By default microseconds) over which protections MUST be triggered. By default
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". When both working and protection
paths are signaled, both LSPs SHOULD be signaled with identical
settings of the E flag, T flag, and the refresh timer.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MPLS OAM FMS Type (5) (IANA) | Length | | MPLS OAM FMS Type (5) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|D|L|C| Reserved (set to all 0s) | PHB | |E|S|T| Reserved (set to all 0s)| Refresh Timer | PHB |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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. (12) Length: indicates the TLV total length in octets. (8)
Signal Flags should not be processed at intermediate nodes as they FMS Signal Flags are used to enable the FMS signals at end point MEPs
only have an end-point significance. They are used to enable the and the Server MEPs of the links over which the LSP is forwarded. In
following signals at end points: this document only the S flag pertains to Server MEPs.
- A: Alarm Indication Signal (AIS) as described in [MPLS-FMS] The following flags are defined:
- D: Link Down Indication (LDI) as described in [MPLS-FMS] - E: Enable Alarm Indication Signal (AIS) and Locked Report (LKR)
signalling as described in [MPLS-FMS]. Default value is 1
(enabled).
- L: Locked Report (LKR) as described in [MPLS-FMS] - S: Indicate to a server MEP that its should transmit AIS and LKR
signals on the client LSP. Default value is 0 (disabled).
- C: Client Signal Failure (CSF) as described in [MPLS-CSF] - T: Set timer value, enabled the configuration of a specific
timer value. Default value is 0 (disabled).
- Remaining bits: Reserved for future specification and set to 0. - Remaining bits: Reserved for future specification and set to 0.
Reserved: Reserved for future specification and set to 0 on Refresh Timer: indicates the refresh timer of fault indication
transmission and ignored when received. messages. If the edge LSR receiving the Path message can not support
such value, it can reply back with a higher interval.
Configuration Flags:
- PHB: identifies the per-hop behavior of packets with fault
management information. It is significant only when C flag is
set.
Refresh Timer: indicates the refresh timer (in microseconds) of fault - PHB: identifies the per-hop behavior of packets with fault
indication messages. If the edge LSR receiving the Path message can management information.
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: 3; - "BFD Configuration" type: 3;
- "Performance Monitoring" type: 4; - "Performance Monitoring" type: 4;
- "MPLS OAM FMS" type: 5. - "MPLS OAM FMS" type: 5.
skipping to change at page 20, line 37 skipping to change at page 21, line 15
[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-CONF]
Kompella, K. and G. Swallow, "Detecting Multi-Protocol
Label Switched (MPLS) Data Plane Failures", 2006, <RFC
3479>.
[LSP-PING CONF]
Bellagamba, E., Andersson, L., Ward, D., and P. Bellagamba, E., Andersson, L., Ward, D., and P.
Skoldstrom, "Configuration of pro-active MPLS-TP Skoldstrom, "Configuration of pro-active MPLS-TP
Operations, Administration, and Maintenance (OAM) Operations, Administration, and Maintenance (OAM)
Functions Using LSP Ping", 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
Maintenance Framework for MPLS-based Transport Networks", Maintenance Framework for MPLS-based Transport Networks",
2010, <draft-ietf-mpls-tp-oam-framework>. 2010, <draft-ietf-mpls-tp-oam-framework>.
[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
Label Switched (MPLS) Data Plane Failures", RFC 4379,
February 2006.
[RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G. [RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G.
Heron, "Pseudowire Setup and Maintenance Using the Label Heron, "Pseudowire Setup and Maintenance Using the Label
Distribution Protocol (LDP)", RFC 4447, April 2006. Distribution Protocol (LDP)", RFC 4447, April 2006.
[RFC5921] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. [RFC5921] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L.
Berger, "A Framework for MPLS in Transport Networks", Berger, "A Framework for MPLS in Transport Networks",
RFC 5921, July 2010. RFC 5921, July 2010.
Authors' Addresses Authors' Addresses
 End of changes. 33 change blocks. 
99 lines changed or deleted 105 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/