draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-06.txt   draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-07.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: January 12, 2012 P. Skoldstrom, Ed. Expires: May 3, 2012 P. Skoldstrom, Ed.
Acreo AB Acreo AB
D. Ward D. Ward
Juniper Juniper
A. Takacs A. Takacs
Ericsson Ericsson
July 11, 2011 October 31, 2011
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-06 draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-07
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 January 12, 2012. This Internet-Draft will expire on May 3, 2012.
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
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 Measurements and FMS . . . . . . . . 6 3.1.3. Configuration of Fault Management Signals . . . . . . 6
3.2. OAM Configuration TLV . . . . . . . . . . . . . . . . . . 6 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 . . . . . . . . . . . . . 10
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 . . . . . . . . . . . . . . 12 3.4. Performance Monitoring sub-TLV . . . . . . . . . . . . . . 13
3.4.1. MPLS OAM PM Loss sub-TLV . . . . . . . . . . . . . . . 13 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 . . . . . . . . . . . . . . . . . 17
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18
7. Security Considerations . . . . . . . . . . . . . . . . . . . 17 7. Security Considerations . . . . . . . . . . . . . . . . . . . 18
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.1. Normative References . . . . . . . . . . . . . . . . . . . 18 8.1. Normative References . . . . . . . . . . . . . . . . . . . 18
8.2. Informative References . . . . . . . . . . . . . . . . . . 19 8.2. Informative References . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20
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
for monitoring and performing measurements on an LSP, as well as at and points for monitoring and performing measurements on an LSP,
defining information elements and procedures to configure pro-active as well as defining information elements and procedures to configure
MPLS OAM functions. Initialization and control of on-demand MPLS OAM pro-active MPLS OAM functions runnineg between LERs. Initialization
functions are expected to be carried out by directly accessing and control of on-demand MPLS OAM functions are expected to be
network nodes via a management interface; hence configuration and carried out by directly accessing network nodes via a management
control of on-demand OAM functions are out-of-scope for this interface; hence configuration and control of on-demand OAM functions
document. 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 three options for configuring MPLS-TP OAM, without a control plane by
either using an NMS or LSP Ping, or with a control plane using GMPLS either using an NMS or LSP Ping, or with a control plane using GMPLS
(specifically RSVP-TE) . (specifically RSVP-TE) .
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) [RFC5880] for Continuity
Check/Connectivity Verification, the delay measurement protocol (DM) Check/Connectivity Verification, the delay measurement protocol (DM)
[MPLS-PM] for delay and delay variation (jitter) measurements, and [RFC6374] for delay and delay variation (jitter) measurements, and
the loss measurement protocol (LM) [MPLS-PM] for packet loss and the loss measurement protocol (LM) [RFC6374] for packet loss and
throughput measurements. Additionally there is a number of Fault throughput measurements. Additionally there is a number of Fault
Management Signals that can be configured. Management Signals that can be configured.
BFD is a protocol that provides low-overhead, fast detection of BFD is a protocol that provides low-overhead, fast detection of
failures in the path between two forwarding engines, including the failures in the path between two forwarding engines, including the
interfaces, data link(s), and to the extent possible the forwarding interfaces, data link(s), and to the extent possible the forwarding
engines themselves. BFD can be used to track the liveliness and engines themselves. BFD can be used to track the liveliness and
detect data plane failures of MPLS-TP point-to-point and might also detect data plane failures of MPLS-TP point-to-point and might also
be extended to support point-to-multipoint connections. be extended to support point-to-multipoint connections.
The delay and loss measurements protocols [MPLS-PM] use a simple The delay and loss measurements protocols [RFC6374] use a simple
query/response model for performing bidirectional measurements that query/response model for performing bidirectional measurements that
allows the originating node to measure packet loss and delay in both allows the originating node to measure packet loss and delay in both
directions. By timestamping and/or writing current packet counters directions. By timestamping and/or writing current packet counters
to the measurement packets at four times (Tx and Rx in both to the measurement packets at four times (Tx and Rx in both
directions) current delays and packet losses can be calculated. By directions) current delays and packet losses can be calculated. By
performing successive delay measurements the delay variation (jitter) performing successive delay measurements the delay variation (jitter)
can be calculated. Current throughput can be calculated from the can be calculated. Current throughput can be calculated from the
packet loss measurements by dividing the number of packets sent/ packet loss measurements by dividing the number of packets sent/
received with the time it took to perform the measurement, given by received with the time it took to perform the measurement, given by
the timestamp in LM header. Combined with a packet generator the the timestamp in LM header. Combined with a packet generator the
skipping to change at page 4, line 43 skipping to change at page 4, line 43
[MPLS-TP-OAM-FWK] describes how MPLS OAM mechanisms are operated to [MPLS-TP-OAM-FWK] describes how MPLS OAM mechanisms are operated to
meet transport requirements outlined in [RFC5860]. meet transport requirements outlined in [RFC5860].
[BFD-CCCV] specifies two BFD operation modes: 1) "CC mode", which [BFD-CCCV] specifies two BFD operation modes: 1) "CC mode", which
uses periodic BFD message exchanges with symmetric timer settings, uses periodic BFD message exchanges with symmetric timer settings,
supporting Continuity Check, 2) "CV/CC mode" which sends unique supporting Continuity Check, 2) "CV/CC mode" which sends unique
maintenance entity identifiers in the periodic BFD messages maintenance entity identifiers in the periodic BFD messages
supporting Connectivity Verification as well as Continuity Check. supporting Connectivity Verification as well as Continuity Check.
[MPLS-PM] specifies mechanisms for performance monitoring of LSPs, in [RFC6374] specifies mechanisms for performance monitoring of LSPs, in
particular it specifies loss and delay measurement OAM functions. particular it specifies loss and delay measurement OAM functions.
[MPLS-FMS] specifies fault management signals with which a server LSP [MPLS-FMS] specifies fault management signals with which a server LSP
can notify client LSPs about various fault conditions to suppress can notify client LSPs about various fault conditions to suppress
alarms or to be used as triggers for actions in the client LSPs. The alarms or to be used as triggers for actions in the client LSPs. The
following signals are defined: Alarm Indication Signal (AIS), Link following signals are defined: Alarm Indication Signal (AIS), Link
Down Indication (LDI) and Locked Report (LKR). To indicate client Down Indication (LDI) and Locked Report (LKR). To indicate client
faults associated with the attachment circuits Client Signal Failure faults associated with the attachment circuits Client Signal Failure
Indication (CSF) can be used. CSF is described in [MPLS-TP-OAM-FWK] Indication (CSF) can be used. CSF is described in [MPLS-TP-OAM-FWK]
and in the context of this document is for further study. and in the context of this document is for further study.
skipping to change at page 5, line 27 skipping to change at page 5, line 27
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". Additionally one may
include sub-TLVs for the different OAM functions in order to specify include sub-TLVs for the different OAM functions in order to specify
different parameters in detail. different parameters in detail.
The presence of OAM configuration TLVs at intermediate nodes is
justified because the mid-points need to forward the RSVP-TE message
to the end point. No TLV processing or modification or following OAM
actions need to be taken at the intermediate points.
3.1.1. Configuration of BFD sessions 3.1.1. Configuration of BFD sessions
For this specification, BFD MUST be run in either one of the two For this specification, BFD MUST be run in either one of the two
modes: modes:
- Asynchronous mode, where both sides should be in active mode. - Asynchronous mode, where both sides should be in active mode
- Unidirectional mode - Unidirectional mode
In the simplest scenario LSP Ping, or alternatively RSVP-TE [RSVP-TE In the simplest scenario LSP Ping, or alternatively RSVP-TE [RSVP-TE
CONF], is used only to bootstrap a BFD session for an LSP, without CONF], is used only to bootstrap a BFD session for an LSP, without
any timer negotiation. any timer negotiation.
Timer negotiation can be performed either in subsequent BFD control Timer negotiation can be performed either in subsequent BFD control
messages (in this case the operation is similar to LSP Ping based messages (in this case the operation is similar to LSP Ping based
bootstrapping described in [RFC5884]) or directly in the LSP ping bootstrapping described in [RFC5884]) or directly in the LSP ping
skipping to change at page 6, line 20 skipping to change at page 6, line 25
(i.e. authentication and not only error detection) the "BFD (i.e. authentication and not only error detection) the "BFD
Authentication sub-TLV" MUST be included in the "BFD Configuration Authentication sub-TLV" MUST be included in the "BFD Configuration
sub-TLV". The "BFD Authentication sub-TLV" is used to specify which sub-TLV". The "BFD Authentication sub-TLV" is used to specify which
authentication method that should be used and which pre-shared key / authentication method 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 Throuhput as described in [MPLS-PM]. such as Loss, Delay and Throughput as described in [RFC6374].
When configuring Performance monitoring functionalities it can be When configuring Performance monitoring functionalities it can be
choosen either the default configuration (by only setting the chosen either the default configuration (by only setting the
respective flags in the "OAM functions TLV") or a customized respective flags in the "OAM functions TLV") or a customized
configuration (by including the respective Loss and/or Delay sub- configuration (by including the respective Loss and/or Delay sub-
TLVs). TLVs).
3.1.3. Configuration of Measurements and FMS 3.1.3. Configuration of Fault Management Signals
Additional OAM functions may be configured by setting the appropriate Additional OAM functions may be configured by setting the appropriate
flags in the "OAM Functions TLV", these include Performance flags in the "OAM Functions TLV", these include Performance
Measurements (packet loss, throughput, delay, and delay variation) Measurements (packet loss, throughput, delay, and delay variation)
and Fault Management Signal handling. 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.
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. sub-TLV" included. If an intermediate point is meant to originate
fault management signal messages this mean that such intermediate
point is associated to a server MEP through a co-located MPLS-TP
client/server adaptation function and such server MEP needs to be
configured by its own RSVP-TE session (or, in alternative, NMS or LSP
ping).
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 8, line 49 skipping to change at page 9, line 12
"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.
[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. This need to be agreed required for Performance monitoring purposes. This need to be agreed
with [MPLS-PM] authors.] with [RFC6374] authors.]
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.
skipping to change at page 13, line 5 skipping to change at page 13, line 18
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.
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 vlues needs 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
skipping to change at page 13, line 30 skipping to change at page 13, line 43
| Perf Monitoring Type (IANA)| Length | | Perf Monitoring Type (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 ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Configuration Flags, for the specific function description please Configuration Flags, for the specific function description please
refer to [MPLS-PM]: 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)
3.4.1. MPLS OAM PM Loss sub-TLV 3.4.1. MPLS OAM PM Loss sub-TLV
skipping to change at page 14, line 24 skipping to change at page 14, line 36
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 (12).
OTF: Origin Timestamp Format of the Origin Timestamp field described OTF: Origin Timestamp Format of the Origin Timestamp field described
in [MPLS-PM]. 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 [MPLS-PM] 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.
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 [MPLS-PM]. 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
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".
skipping to change at page 15, line 29 skipping to change at page 15, line 41
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 (12).
OTF: Origin Timestamp Format of the Origin Timestamp field described OTF: Origin Timestamp Format of the Origin Timestamp field described
in [MPLS-PM]. 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 [MPLS-PM] 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.
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 [MPLS-PM]. 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".
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 (set all to 0s) |E| PHB | |A|D|L|C| Reserved (set all to 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.
Signal Flags: are used to enable the following signals: Signal Flags should not be processed at intermediate nodes as they
only have an end-point significance. They are used to enable the
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.
Configuration Flags: Configuration Flags:
- 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. It is significant only when C flag is
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: 2;
skipping to change at page 18, line 19 skipping to change at page 18, line 32
8. References 8. References
8.1. Normative References 8.1. Normative References
[MPLS-FMS] [MPLS-FMS]
Swallow, G., Fulignoli, A., Vigoureux, M., Boutros, S., Swallow, G., Fulignoli, A., Vigoureux, M., Boutros, S.,
and D. Ward, "MPLS Fault Management OAM", 2009, and D. Ward, "MPLS Fault Management OAM", 2009,
<draft-ietf-mpls-tp-fault>. <draft-ietf-mpls-tp-fault>.
[MPLS-PM] Bryant, S. and D. Frost, "Packet Loss and Delay
Measurement for the MPLS Transport Profile", 2010,
<draft-ietf-mpls-loss-delay>.
[MPLS-PM-Profile]
Bryant, S. and D. Frost, "A Packet Loss and Delay
Measurement Profile for MPLS-based Transport Networks",
2010, <draft-ietf-mpls-tp-loss-delay-profile>.
[MPLS-TP-IDENTIF] [MPLS-TP-IDENTIF]
Bocci, M., Swallow, G., and E. Gray, "MPLS-TP Bocci, M., Swallow, G., and E. Gray, "MPLS-TP
Identifiers", 2010, <draft-ietf-mpls-tp-identifiers>. Identifiers", 2010, <draft-ietf-mpls-tp-identifiers>.
[OAM-CONF-FWK] [OAM-CONF-FWK]
Takacs, A., Fedyk, D., and J. van He, "OAM Configuration Takacs, A., Fedyk, D., and J. van He, "OAM Configuration
Framework for GMPLS RSVP-TE", 2009, Framework for GMPLS RSVP-TE", 2009,
<draft-ietf-ccamp-oam-configuration-fwk>. <draft-ietf-ccamp-oam-configuration-fwk>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
skipping to change at page 19, line 23 skipping to change at page 19, line 27
Operations, Administration, and Maintenance (OAM) in MPLS Operations, Administration, and Maintenance (OAM) in MPLS
Transport Networks", RFC 5860, May 2010. Transport Networks", RFC 5860, May 2010.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, June 2010. (BFD)", RFC 5880, June 2010.
[RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, [RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow,
"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
Measurement for MPLS Networks", RFC 6374, September 2011.
[RFC6375] Frost, D. and S. Bryant, "A Packet Loss and Delay
Measurement Profile for MPLS-Based Transport Networks",
RFC 6375, September 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. 34 change blocks. 
51 lines changed or deleted 58 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/