--- 1/draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf-02.txt 2011-10-31 17:14:07.458671641 +0100 +++ 2/draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf-03.txt 2011-10-31 17:14:07.498671145 +0100 @@ -1,24 +1,24 @@ MPLS Working Group E. Bellagamba, Ed. Internet-Draft L. Andersson Intended status: Standards Track Ericsson -Expires: January 12, 2012 P. Skoldstrom, Ed. +Expires: May 3, 2012 P. Skoldstrom, Ed. Acreo AB D. Ward J. Drake Juniper - July 11, 2011 + October 31, 2011 Configuration of Pro-Active Operations, Administration, and Maintenance (OAM) Functions for MPLS-based Transport Networks using LSP Ping - draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf-02 + draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf-03 Abstract This specification describes the configuration of pro-active MPLS-TP Operations, Administration, and Maintenance (OAM) Functions for a given LSP using a set of TLVs that are carried by the LSP Ping protocol This document is a product of a joint Internet Engineering Task Force (IETF) / International Telecommunication Union Telecommunication @@ -34,21 +34,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference 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 (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -60,21 +60,21 @@ Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 2. Overview of MPLS OAM for Transport Applications . . . . . . . 4 3. Theory of Operations . . . . . . . . . . . . . . . . . . . . . 5 3.1. MPLS OAM Configuration Operation Overview . . . . . . . . 5 3.1.1. Configuration of BFD sessions . . . . . . . . . . . . 5 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 Functions TLV . . . . . . . . . . . . . . . . . . . . 6 3.2.1. BFD Configuration sub-TLV . . . . . . . . . . . . . . 8 3.2.1.1. Local Discriminator sub-TLV . . . . . . . . . . . 10 3.2.1.2. Negotiation Timer Parameters sub-TLV . . . . . . . 10 3.2.1.3. BFD Authentication sub-TLV . . . . . . . . . . . . 11 3.2.2. MPLS OAM Source MEP-ID sub-TLV . . . . . . . . . . . . 12 3.2.3. Performance Monitoring sub-TLV . . . . . . . . . . . . 13 3.2.3.1. MPLS OAM PM Loss sub-TLV . . . . . . . . . . . . . 14 3.2.3.2. MPLS OAM PM Delay sub-TLV . . . . . . . . . . . . 15 3.2.4. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . 16 @@ -85,50 +85,50 @@ 6.1. Normative References . . . . . . . . . . . . . . . . . . . 18 6.2. Informative References . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 1. Introduction This document describes the configuration of pro-active MPLS-TP Operations, Administration, and Maintenance (OAM) Functions for a given LSP using TLVs carried in LSP Ping [BFD-Ping]. In particular it specifies the mechanisms necessary to establish MPLS-TP OAM - entities for monitoring and performing measurements on an LSP, as - well as defining information elements and procedures to configure - pro-active MPLS OAM functions. Initialization and control of on- - demand MPLS OAM functions are expected to be carried out by directly - accessing network nodes via a management interface; hence - configuration and control of on-demand OAM functions are out-of-scope - for this document. + entities at the end points for monitoring and performing measurements + on an LSP, as well as defining information elements and procedures to + configure pro-active MPLS OAM functions running between LERs. + Initialization and control of on-demand MPLS OAM functions are + expected to be carried out by directly accessing network nodes via a + management interface; hence configuration and control of on-demand + OAM functions are out-of-scope for this document. The Transport Profile of MPLS must, by definition [RFC5654], be capable of operating without a control plane. Therefore there are 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 (specifically RSVP-TE) . Pro-active MPLS OAM is performed by three different protocols, Bidirectional Forwarding Detection (BFD) [RFC5880] for Continuity Check/Connectivity Verification, the delay measurement protocol (DM) - [MPLS-PM] for delay and delay variation (jitter) measurements, and - the loss measurement protocol (LM) [MPLS-PM] for packet loss and + [RFC6374] for delay and delay variation (jitter) measurements, and + the loss measurement protocol (LM) [RFC6374] for packet loss and throughput measurements. Additionally there is a number of Fault Management Signals that can be configured. BFD is a protocol that provides low-overhead, fast detection of failures in the path between two forwarding engines, including the interfaces, data link(s), and to the extent possible the forwarding engines themselves. BFD can be used to track the liveliness and detect data plane failures of MPLS-TP point-to-point and might also 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 allows the originating node to measure packet loss and delay in both directions. By timestamping and/or writing current packet counters to the measurement packets at four times (Tx and Rx in both directions) current delays and packet losses can be calculated. By performing successive delay measurements the delay variation (jitter) can be calculated. Current throughput can be calculated from the packet loss measurements by dividing the number of packets sent/ received with the time it took to perform the measurement, given by the timestamp in LM header. Combined with a packet generator the @@ -157,21 +157,21 @@ [MPLS-TP-OAM-FWK] describes how MPLS OAM mechanisms are operated to meet transport requirements outlined in [RFC5860]. [BFD-CCCV] specifies two BFD operation modes: 1) "CC mode", which uses periodic BFD message exchanges with symmetric timer settings, supporting Continuity Check, 2) "CV/CC mode" which sends unique maintenance entity identifiers in the periodic BFD messages 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. [MPLS-FMS] specifies fault management signals with which a server LSP can notify client LSPs about various fault conditions to suppress alarms or to be used as triggers for actions in the client LSPs. The following signals are defined: Alarm Indication Signal (AIS), Link Down Indication (LDI) and Locked Report (LKR). To indicate client faults associated with the attachment circuits Client Signal Failure Indication (CSF) can be used. CSF is described in [MPLS-TP-OAM-FWK] and in the context of this document is for further study. @@ -189,26 +189,31 @@ 3. Theory of Operations 3.1. MPLS OAM Configuration Operation Overview LSP Ping, or alternatively RSVP-TE [RSVP-TE CONF], can be used to simply enable the different OAM functions, by setting the corresponding flags in the "OAM Functions TLV". Additionally one may include sub-TLVs for the different OAM functions in order to specify different parameters in detail. + The presence of OAM configuration TLVs at intermediate nodes is + justified because the intermediate nodes need to forward the LSP-ping + 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 For this specification, BFD MUST be run in either one of the two modes: - - Asynchronous mode, where both sides should be in active mode. + - Asynchronous mode, where both sides should be in active mode - Unidirectional mode 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 any timer negotiation. Timer negotiation can be performed either in subsequent BFD control messages (in this case the operation is similar to LSP Ping based bootstrapping described in [RFC5884]) or directly in the LSP ping @@ -229,47 +234,52 @@ (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 pre-shared key / password that should be used for this particular session. How the key exchange is performed is out of scope of this document. 3.1.2. Configuration of Performance Monitoring 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 - 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 configuration (by including the respective Loss and/or Delay sub- 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 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 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. + 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 LSP-ping session (or, in alternative, NMS or + RSVP-TE). 3.2. OAM Functions TLV The "OAM Functions TLV" depicted below is carried as a TLV of the LSP Echo request/response messages. 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | OAM Func. Type (16) (IANA) | Length | @@ -550,21 +560,21 @@ LSP ID: a 16-bit unsigned integer unique within the Tunnel_ID as defined in [MPLS-TP-IDENTIF]. 3.2.3. Performance Monitoring sub-TLV If the "OAM functions TLV" has either the L (Loss), D (Delay) or T (Throughput) flag set, the "Performance Monitoring sub-TLV" MUST be 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 include the following sub-TLVs: - "MPLS OAM PM Loss sub-TLV" if the L flag is set in the "OAM functions TLV"; - "MPLS OAM PM Delay sub-TLV" if the D flag is set in the "OAM functions TLV"; The "Performance Monitoring sub-TLV" depicted below is carried as a @@ -575,21 +585,21 @@ | Perf Monitoring Type (IANA)| Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |D|L|J|Y|K|C| Reserved (set to all 0s) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ sub-TLVs ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Configuration Flags, for the specific function description please - refer to [MPLS-PM]: + refer to [RFC6374]: - D: Delay inferred/direct (0=INFERRED, 1=DIRECT) - L: Loss inferred/direct (0=INFERRED, 1=DIRECT) - J: Delay variation/jitter (1=ACTIVE, 0=NOT ACTIVE) - Y: Dyadic (1=ACTIVE, 0=NOT ACTIVE) - K: Loopback (1=ACTIVE, 0=NOT ACTIVE) @@ -612,42 +622,42 @@ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Loss Threshold | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type: indicates a new type, the "MPLS OAM PM Loss sub-TLV" (IANA to define, suggested value 1). Length: indicates the length of the parameters in octets (12). 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 the measurement operation is scoped to packets of a particular traffic class (DSCP value), and 0 otherwise. When set to 1, the DS field of the message indicates the measured traffic class. By default it is set to 1. - B: Octet (byte) count. When set to 1, indicates that the Counter 1-4 fields represent octet counts. When set to 0, indicates that the Counter 1-4 fields represent packet counts. By default it is set to 0. Measurement Interval: the time interval (in microseconds) at which Loss Measurement query messages MUST be sent on both directions. If 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 (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). Loss Threshold: the threshold value of lost packets over which protections MUST be triggered. By default it is set to (TBD). 3.2.3.2. MPLS OAM PM Delay sub-TLV The "MPLS OAM PM Delay sub-TLV" depicted below is carried as a sub- TLV of the "OAM Functions TLV". @@ -663,86 +673,87 @@ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Delay Threshold | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type: indicates a new type, the "MPLS OAM PM Loss sub-TLV" (IANA to define, suggested value 1). Length: indicates the length of the parameters in octets (12). 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 the measurement operation is scoped to packets of a particular traffic class (DSCP value), and 0 otherwise. When set to 1, the DS field of the message indicates the measured traffic class. By default it is set to 1. - B: Octet (byte) count. When set to 1, indicates that the Counter 1-4 fields represent octet counts. When set to 0, indicates that the Counter 1-4 fields represent packet counts. By default it is set to 0. Measurement Interval: the time interval (in microseconds) at which Delay Measurement query messages MUST be sent on both directions. If 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 (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). Delay Threshold: the threshold value of measured delay (in microseconds) over which protections MUST be triggered. By default it is set to (TBD). 3.2.4. MPLS OAM FMS sub-TLV The "MPLS OAM FMS sub-TLV" depicted below is carried as a sub-TLV of the "OAM Functions TLV". 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Fault mgmt Type (4) (IANA) | Length (8) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - |A|D|L|C| Reserved (set to all 0s) |E| PHB | + |A|D|L|C| Reserved (set to all 0s) | PHB | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Refresh Timer | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type: indicates a new type, the "MPLS OAM FMS sub-TLV" (IANA to define, suggested value 4). Length: indicates the length of the parameters in octets (8). - 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] - D: Link Down Indication (LDI) as described in [MPLS-FMS] - L: Locked Report (LKR) as described in [MPLS-FMS] - C: Client Signal Failure (CSF) as described in [MPLS-CSF] - Remaining bits: Reserved for future specification and set to 0. Configuration Flags: - - E: used to enable/disable explicitly clearing faults - - 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 indication messages. If the edge LSR receiving the Path message can not support such value, it can reply back with a higher interval. 3.3. IANA Considerations This document specifies the following new TLV types: - "OAM Functions" type: 16; @@ -791,29 +802,20 @@ 6. References 6.1. Normative References [MPLS-FMS] Swallow, G., Fulignoli, A., Vigoureux, M., Boutros, S., and D. Ward, "MPLS Fault Management OAM", 2009, . - [MPLS-PM] Bryant, S. and D. Frost, "Packet Loss and Delay - Measurement for the MPLS Transport Profile", 2010, - . - - [MPLS-PM-Profile] - Bryant, S. and D. Frost, "A Packet Loss and Delay - Measurement Profile for MPLS-based Transport Networks", - 2010, . - [MPLS-TP-IDENTIF] Bocci, M., Swallow, G., and E. Gray, "MPLS-TP Identifiers", 2010, . [OAM-CONF-FWK] Takacs, A., Fedyk, D., and J. van He, "OAM Configuration Framework for GMPLS RSVP-TE", 2009, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate @@ -830,20 +832,27 @@ and S. Ueno, "Requirements of an MPLS Transport Profile", RFC 5654, September 2009. [RFC5860] Vigoureux, M., Ward, D., and M. Betts, "Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport Networks", RFC 5860, May 2010. [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD)", RFC 5880, 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. + [RSVP-TE CONF] Bellagamba, E., Ward, D., Andersson, L., and P. Skoldstrom, "Configuration of pro-active MPLS-TP Operations, Administration, and Maintenance (OAM) Functions Using RSVP-TE", 2010, . 6.2. Informative References [BFD-CCCV]