draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-05.txt   draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-06.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: September 11, 2011 P. Skoldstrom, Ed. Expires: January 12, 2012 P. Skoldstrom, Ed.
Acreo AB Acreo AB
D. Ward D. Ward
Juniper Juniper
A. Takacs A. Takacs
Ericsson Ericsson
March 10, 2011 July 11, 2011
Configuration of pro-active MPLS-TP Operations, Administration, and Configuration of Pro-Active Operations, Administration, and Maintenance
Maintenance (OAM) Functions Using RSVP-TE (OAM) Functions for MPLS-based Transport Networks using RSVP-TE
draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-05 draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-06
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 can be carried in 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
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 11, 2011. This Internet-Draft will expire on January 12, 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
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
skipping to change at page 2, line 14 skipping to change at page 2, line 20
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Contributing Authors . . . . . . . . . . . . . . . . . . . 3 1.1. Contributing Authors . . . . . . . . . . . . . . . . . . . 4
1.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.2. Requirements Language . . . . . . . . . . . . . . . . . . 4
1.3. Overview of BFD OAM operation . . . . . . . . . . . . . . 4
2. Overview of MPLS OAM for Transport Applications . . . . . . . 4 2. Overview of MPLS OAM for Transport Applications . . . . . . . 4
3. Theory of Operations . . . . . . . . . . . . . . . . . . . . . 5 3. Theory of Operations . . . . . . . . . . . . . . . . . . . . . 5
3.1. MPLS OAM Configuration Operation Overview . . . . . . . . 5 3.1. MPLS OAM Configuration Operation Overview . . . . . . . . 5
3.2. OAM Configuration TLV . . . . . . . . . . . . . . . . . . 7 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.2. OAM Configuration TLV . . . . . . . . . . . . . . . . . . 6
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. MPLS OAM PM Loss sub-TLV . . . . . . . . . . . . . . . . . 13 3.4. Performance Monitoring sub-TLV . . . . . . . . . . . . . . 12
3.5. MPLS OAM PM Delay sub-TLV . . . . . . . . . . . . . . . . 14 3.4.1. MPLS OAM PM Loss sub-TLV . . . . . . . . . . . . . . . 13
3.6. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . . . 15 3.4.2. MPLS OAM PM Delay sub-TLV . . . . . . . . . . . . . . 15
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 3.5. MPLS OAM FMS sub-TLV . . . . . . . . . . . . . . . . . . . 16
5. BFD OAM configuration errors . . . . . . . . . . . . . . . . . 16 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 5. BFD OAM configuration errors . . . . . . . . . . . . . . . . . 17
7. Security Considerations . . . . . . . . . . . . . . . . . . . 16 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 7. Security Considerations . . . . . . . . . . . . . . . . . . . 17
8.1. Normative References . . . . . . . . . . . . . . . . . . . 17 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.2. Informative References . . . . . . . . . . . . . . . . . . 18 8.1. Normative References . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 8.2. Informative References . . . . . . . . . . . . . . . . . . 19
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 a common set of TLVs carried on RSVP-TE [RFC3209]. given LSP using TLVs carried by RSVP-TE [RFC3209]. In particular it
In particular it specifies the mechanisms necessary to establish specifies the mechanisms necessary to establish MPLS-TP OAM entities
MPLS-TP OAM entities monitoring an LSP and defines information for monitoring and performing measurements on an LSP, as well as
elements and procedures to configure pro-active MPLS OAM functions. defining information elements and procedures to configure pro-active
Initialization and control of on-demand MPLS OAM functions are MPLS OAM functions. Initialization and control of on-demand MPLS OAM
expected to be carried out by directly accessing network nodes via a functions are expected to be carried out by directly accessing
management interface; hence configuration and control of on-demand network nodes via a management interface; hence configuration and
OAM functions are out-of-scope for this document. control of on-demand OAM functions are out-of-scope for this
document.
Pro-active MPLS OAM is based on the Bidirectional Forwarding The Transport Profile of MPLS must, by definition [RFC5654], be
Detection (BFD) protocol [RFC5880]. Bidirectional Forwarding capable of operating without a control plane. Therefore there are
Detection (BFD), as described in [RFC5880], defines a protocol that three options for configuring MPLS-TP OAM, without a control plane by
provides low- overhead, short-duration detection of failures in the either using an NMS or LSP Ping, or with a control plane using GMPLS
path between two forwarding engines, including the interfaces, data (specifically RSVP-TE) .
link(s), and to the extent possible the forwarding engines
themselves. BFD can be used to track the liveliness and detect data Pro-active MPLS OAM is performed by three different protocols,
plane failures of MPLS-TP point-to-point and might also be extended Bidirectional Forwarding Detection (BFD) [RFC5880] for Continuity
to p2mp connections. 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
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
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
throughput measurement can be used to measure the maximum capacity of
a particular LSP.
MPLS Transport Profile (MPLS-TP) describes a profile of MPLS that MPLS Transport Profile (MPLS-TP) describes a profile of MPLS that
enables operational models typical in transport networks, while enables operational models typical in transport networks, while
providing additional OAM, survivability and other maintenance providing additional OAM, survivability and other maintenance
functions not currently supported by MPLS. [RFC5860] defines the functions not currently supported by MPLS. [RFC5860] defines the
requirements for the OAM functionality of MPLS-TP. requirements for the OAM functionality of MPLS-TP.
BFD has been chosen to be the basis of pro-active MPLS-TP OAM This document is a product of a joint Internet Engineering Task Force
functions. MPLS-TP OAM extensions for transport applications, for (IETF) / International Telecommunication Union Telecommunication
which this document specifies the configuration, are specified in Standardization Sector (ITU-T) effort to include an MPLS Transport
[BFD-CCCV], [MPLS-PM], and [MPLS-FMS]. Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network.
1.1. Contributing Authors 1.1. Contributing Authors
This document is the result of a large team of authors and This document is the result of a large team of authors and
contributors. The following is a list of the co-authors: contributors. The following is a list of the co-authors:
John Drake John Drake
Benoit Tremblay Benoit Tremblay
1.2. Requirements Language 1.2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
1.3. Overview of BFD OAM operation
BFD is a simple hello protocol that in many respects is similar to
the detection components of well-known routing protocols. A pair of
systems transmits BFD packets periodically over each path between the
two systems, and if a system stops receiving BFD packets for long
enough, some component in that particular bidirectional path to the
neighboring system is assumed to have failed. Systems may also
negotiate to not send periodic BFD packets in order to reduce
overhead.
A path is only declared to be operational when two-way communication
has been established between systems, though this does not preclude
the use of unidirectional links to support bidirectional paths (co-
routed or bidirectional or associated bidirectional).
Each system estimates how quickly it can send and receive BFD packets
in order to come to an agreement with its neighbor about how rapidly
detection of failure will take place. These estimates can be
modified in real time in order to adapt to unusual situations. This
design also allows for fast systems on a shared medium with a slow
system to be able to more rapidly detect failures between the fast
systems while allowing the slow system to participate to the best of
its ability. However, in some cases one may want to configure these
timers manually, in those cases the TLVs defined in this document can
be used.
The ability of each system to control the BFD packet transmission
rate in both directions provides a mechanism for congestion control,
particularly when BFD is used across multiple network hops.
As recommended in [BFD-CCCV], the BFD tool needs to be extended for
the proactive CV functionality by the addition of an unique
identifier in order to meet the requirements. The document in [BFD-
CCCV] specifies the BFD extension and behavior to meet the
requirements for MPLS-TP proactive Continuity Check and Connectivity
Verification functionality and the RDI functionality as defined in
[RFC5860].
2. Overview of MPLS OAM for Transport Applications 2. Overview of MPLS OAM for Transport Applications
[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.
skipping to change at page 5, line 27 skipping to change at page 5, line 15
and in the context of this document is for further study. and in the context of this document is for further study.
[MPLS-TP-OAM-FWK] describes the mapping of fault conditions to [MPLS-TP-OAM-FWK] describes the mapping of fault conditions to
consequent actions. Some of these mappings may be configured by the consequent actions. Some of these mappings may be configured by the
operator, depending on the application of the LSP. The following operator, depending on the application of the LSP. The following
defects are identified: Loss Of Continuity (LOC), Misconnectivity, defects are identified: Loss Of Continuity (LOC), Misconnectivity,
MEP Misconfiguration and Period Misconfiguration. Out of these MEP Misconfiguration and Period Misconfiguration. Out of these
defect conditions, the following consequent actions may be defect conditions, the following consequent actions may be
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 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 in alternative LSP Ping [LSP-PING CONF], can be used to RSVP-TE, or alternatively LSP Ping [LSP-PING CONF], can be used to
simply establish (i.e., bootstrap) a BFD session or it can simply enable the different OAM functions, by setting the
selectively enable and configure all pro-active MPLS OAM functions. corresponding flags in the "OAM Functions TLV". Additionally one may
For this specification, BFD MUST be run in asynchronous mode and both include sub-TLVs for the different OAM functions in order to specify
sides should be in active mode. different parameters in detail.
In the simplest scenario RSVP-TE, or in alternative LSP Ping [LSP- 3.1.1. Configuration of BFD sessions
PING CONF], is used only to bootstrap the BFD session. In this case
the initiating node includes an "OAM Configuration TLV" in the
message it sends to the receiving node at the other end of the LSP.
The OAM Type in the "OAM Configuration TLV" is set to "MPLS OAM", the
CC OAM Function flag is set, and a "BFD Configuration sub-TLV" is
included. The sub-TLV carries a "Local Discriminator sub-TLV" with
the discriminator value selected by the initiating node for the BFD
session associated with the LSP. The N flag in the "BFD
Configuration sub-TLV" MUST be set to enable timer negotiation/
re-negotiation via BFD Control Messages.
The receiving node MUST use the Local Discriminator value it receives For this specification, BFD MUST be run in either one of the two
to identify the remote end of the BFD session. The receiving node modes:
must send a message to the initiating node that includes an "OAM
Configuration TLV" containing the same values as it received, except
for the "Local Discriminator sub-TLV", which contains the local
discriminator value selected by the receiving node for the BFD
session.
Timer negotiation is performed in subsequent BFD control messages. - Asynchronous mode, where both sides should be in active mode.
This operation is similar to LSP Ping based bootstrapping described
in [RFC5884].
If timer negotiation is to be done using the TLVs defined in this - Unidirectional mode
document rather than with BFD Control packets, the N flag MUST be
cleared and a "Timer Negotiation Parameters sub-TLV" MUST be present
in the "BFD Configuration sub-TLV". In this case, there are two
configuration options, symmetric and asymmetric. If symmetric
configuration is used, the S flag in "BFD Configuration sub-TLV" MUST
be set. If the flag is cleared, the configuration is completed
asymmetrically in the two directions. Section 3.3.2 includes a
detailed explanation of such configuration.
In the case of the "CV/CC mode" OAM [BFD-CCCV], the "CV" flag MUST be In the simplest scenario LSP Ping, or alternatively RSVP-TE [RSVP-TE
set in addition to the CC flag in the "OAM Configuration TLV". The CONF], is used only to bootstrap a BFD session for an LSP, without
information required to support this functionality is defined in any timer negotiation.
[MPLS-TP-IDENTIF]. If RSVP-TE is used, this information is found
respectively in the SESSION and SENDER_TEMPLATE object with no need Timer negotiation can be performed either in subsequent BFD control
of additional sub-TLVs as described in section 3.2. messages (in this case the operation is similar to LSP Ping based
bootstrapping described in [RFC5884]) or directly in the LSP ping
configuration messages.
When BFD Control packets are transported in the G-ACh they are not When BFD Control packets are transported in the G-ACh they are not
protected by any end-to-end checksum, only lower-layers are providing protected by any end-to-end checksum, only lower-layers are providing
error detection/correction. A single bit error, e.g. a flipped bit error detection/correction. A single bit error, e.g. a flipped bit
in the BFD State field could cause the receiving end to wrongly in the BFD State field could cause the receiving end to wrongly
conclude that the link is down and thus trigger protection switching. conclude that the link is down and in turn trigger protection
To prevent this from happening the "BFD Configuration sub-TLV" has an switching. To prevent this from happening the "BFD Configuration
Integrity flag that when set enables BFD Authentication using Keyed sub-TLV" has an Integrity flag that when set enables BFD
SHA1 with an empty key (all 0s) [RFC5880]. This would make every BFD Authentication using Keyed SHA1 with an empty key (all 0s) [RFC5880].
Control packet carry an SHA1 hash of itself that can be used to This would make every BFD Control packet carry an SHA1 hash of itself
detect errors. that can be used to detect errors.
If BFD Authentication using a shared key / password is desired (i.e. If BFD Authentication using a pre-shared key / password is desired
actual authentication 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 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
It is possible to configure Performance Monitoring functionalities
such as Loss, Delay and Throuhput as described in [MPLS-PM].
When configuring Performance monitoring functionalities it can be
choosen 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
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 and packet delay) and Fault Management Measurements (packet loss, throughput, delay, and delay variation)
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.
3.2. OAM Configuration TLV 3.2. OAM Configuration TLV
The "OAM Configuration TLV" is depicted in the following figure. It The "OAM Configuration TLV" is depicted in the following figure. It
specifies the OAM functions that are to be used for the subject LSP specifies the OAM functions that are to be used for the LSP and it is
and it is defined in [OAM-CONF-FWK]. The "OAM Configuration TLV" is defined in [OAM-CONF-FWK]. The "OAM Configuration TLV" is carried in
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (2) (IANA) | Length | | Type (2) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OAM Type | Reserved | | OAM Type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ sub-TLVs ~ ~ sub-TLVs ~
skipping to change at page 8, line 10 skipping to change at page 7, line 33
generated: "OAM Problem/Unsupported OAM Type". generated: "OAM Problem/Unsupported OAM Type".
This document defines a new OAM Type: "MPLS OAM" (suggested value 2, This document defines a new OAM Type: "MPLS OAM" (suggested value 2,
IANA to assign) from the "RSVP-TE OAM Configuration Registry". The IANA to assign) from the "RSVP-TE OAM Configuration Registry". The
"MPLS OAM" type is set to request the establishment of OAM functions "MPLS OAM" type is set to request the establishment of OAM functions
for MPLS-TP LSPs. The specific OAM functions are specified in the for MPLS-TP LSPs. The specific OAM functions are specified in the
"Function Flags" sub-TLV as depicted in [OAM-CONF-FWK]. "Function Flags" sub-TLV as depicted in [OAM-CONF-FWK].
The receiving edge LSR when the MPLS-TP OAM Type is requested should The receiving edge LSR when the MPLS-TP OAM Type is requested should
check which OAM Function Flags are set in the "Function Flags TLV" check which OAM Function Flags are set in the "Function Flags TLV"
and look for the corresponding technology specific configuration TLV. (also defined in [OAM-CONF-FWK]) and look for the corresponding
technology specific configuration TLVs.
Additional corresponding sub-TLVs are as follows: Additional corresponding sub-TLVs are as follows:
- "BFD Configuration sub-TLV", which MUST be included if the CC - "BFD Configuration sub-TLV", which MUST be included if the CC
OAM Function flag is set. This sub-TLV MUST carry a "BFD Local and/or the CV OAM Function flag is set. This sub-TLV MUST carry a
Discriminator sub-TLV" and a "Timer Negotiation Parameters sub- "BFD Local Discriminator sub-TLV" and a "Timer Negotiation
TLV" if the N flag is cleared. It MAY carry a "BFD Authentication Parameters sub-TLV" if the N flag is cleared. If the I flag is
sub-TLV" if the I flag is set. If the I flag is set but no "BFD set, the "BFD Authentication sub-TLV" may be included.
Authentication sub-TLV" is included Keyed SHA1 with an empty key
is used.
- "MPLS OAM PM Loss sub-TLV", which MAY be included if the PM/Loss - "MPLS OAM PM Loss sub-TLV" within the "Performance Monitoring
OAM Function flag is set. If the "MPLS OAM PM Loss sub-TLV" is sub-TLV", which MAY be included if the PM/Loss OAM Function flag
not included, default configuration values are used. is set. If the "MPLS OAM PM Loss sub-TLV" is not included,
default configuration values are used. Such sub-TLV MAY also be
included in case the Throughput function flag is set and there is
the need to specify measurement interval different from the
default ones. In fact the throughput measurement make use of the
same tool as the loss measurement, hence the same TLV is used.
- "MPLS OAM PM Delay sub-TLV", which MAY be included if the PM/ - "MPLS OAM PM Delay sub-TLV" within the "Performance Monitoring
Delay OAM Function flag is set. If the "MPLS OAM PM Delay sub- sub-TLV", which MAY be included if the PM/Delay OAM Function flag
TLV" is not included, default configuration values are used. is set. If the "MPLS OAM PM Delay sub-TLV" is not included,
default configuration values are used.
- "MPLS OAM FMS sub-TLV", which MAY be included if the FMS OAM - "MPLS OAM FMS sub-TLV", which MAY be included if the FMS OAM
Function flag is set. If the "MPLS OAM FMS sub-TLV" is not Function flag is set. If the "MPLS OAM FMS sub-TLV" is not
included, default configuration values are used. included, default configuration values are used.
Moreover, if the CV flag is set, the CC flag MUST be set at the same Moreover, if the CV or CC flag is set, the CC flag MUST be set at the
time. The format of an MPLS-TP CV/CC message is shown in [BFD-CCCV] same time. The format of an MPLS-TP CV/CC message is shown in [BFD-
and it requires, together with the BFD control packet information, CCCV] and it requires, together with the BFD control packet
the "Unique MEP-ID of source of BFD packet". [MPLS-TP-IDENTIF] information, the "Unique MEP-ID of source of BFD packet". [MPLS-TP-
defines the composition of such identifier as: IDENTIF] defines the composition of such identifier as:
<"Unique MEP-ID of source of BFD packet"> ::= <"Unique MEP-ID of source of BFD packet"> ::=
<src_node_id><src_tunnel_num><lsp_num> <src_node_id><src_tunnel_num><lsp_num>
GMPLS signaling [RFC3473] uses a 5-tuple to uniquely identify an LSP GMPLS signaling [RFC3473] uses a 5-tuple to uniquely identify an LSP
within an operator's network. This tuple is composed of a Tunnel within an operator's network. This tuple is composed of a Tunnel
Endpoint Address, Tunnel_ID, Extended Tunnel ID, and Tunnel Sender Endpoint Address, Tunnel_ID, Extended Tunnel ID, and Tunnel Sender
Address and (GMPLS) LSP_ID. Address and (GMPLS) LSP_ID.
Hence, the following mapping is used without the need of redefining a Hence, the following mapping is used without the need of redefining a
skipping to change at page 9, line 19 skipping to change at page 8, line 48
- LSP ID = LSP_Num - LSP ID = LSP_Num
"Tunnel ID" and "Tunnel Sender Address" are included in the "SESSION" "Tunnel ID" and "Tunnel Sender Address" are included in the "SESSION"
object [RFC3209], which is mandatory in both Path and Resv messages. object [RFC3209], which is mandatory in both Path and Resv messages.
"LSP ID" will be the same on both directions and it is included in "LSP ID" will be the same on both directions and it is included in
the "SENDER_TEMPLATE" object [RFC3209] which is mandatory in Path the "SENDER_TEMPLATE" object [RFC3209] which is mandatory in Path
messages. messages.
[Author's note: the same "Unique MEP-ID of source" will be likely [Author's note: the same "Unique MEP-ID of source" will be likely
required for Performance monitoring purposes. However for the moment required for Performance monitoring purposes. This need to be agreed
in [MPLS-PM] it is stated: "The question of ACH TLV usage and the with [MPLS-PM] authors.]
manner of supporting metadata such as authentication keys and node
identifiers is deliberately omitted. These issues will be addressed
in a future version of the document."]
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 10, line 21 skipping to change at page 9, line 49
Control Messages is enabled, when cleared it is disabled. Control Messages is enabled, when cleared it is disabled.
Symmetric session (S): If set the BFD session MUST use symmetric Symmetric session (S): If set the BFD session MUST use symmetric
timing values. timing values.
Integrity (I): If set BFD Authentication MUST be enabled. If the Integrity (I): If set BFD Authentication MUST be enabled. If the
"BFD Configuration sub-TLV" does not include a "BFD Authentication "BFD Configuration sub-TLV" does not include a "BFD Authentication
sub-TLV" the authentication MUST use Keyed SHA1 with an empty pre- sub-TLV" the authentication MUST use Keyed SHA1 with an empty pre-
shared key (all 0s). shared key (all 0s).
Encapsulation Capability (G): if set, it shows the capability of
encapsulating BFD messages into G-Ach channel. If both the G bit and
U bit are set, configuration gives precedence to the G bit.
Encapsulation Capability (U): if set, it shows the capability of
encapsulating BFD messages into UDP packets. If both the G bit and U
bit are set, configuration gives precedence to the G bit.
Bidirectional (B): if set, it configures BFD in the Bidirectional
mode. If it is not set it configures BFD in unidirectional mode. In
the second case, the source node does not expect any Discriminator
values back from the destination node.
The "BFD Configuration sub-TLV" MUST include the following sub-TLVs The "BFD Configuration sub-TLV" MUST include the following sub-TLVs
in the Path message: in the Path message:
- "Local Discriminator sub-TLV"; - "Local Discriminator sub-TLV";
- "Negotiation Timer Parameters sub-TLV" if N flag is cleared. - "Negotiation Timer Parameters sub-TLV" if the N flag is cleared.
The "BFD Configuration sub-TLV" MUST include the following sub-TLVs The "BFD Configuration sub-TLV" MUST include the following sub-TLVs
in the Resv message: in the Resv message:
- "Local Discriminator sub-TLV;" - "Local Discriminator sub-TLV;"
- "Negotiation Timer Parameters sub-TLV" if: - "Negotiation Timer Parameters sub-TLV" if:
- N flag and S are cleared - the N and S flags are cleared
- N flag is cleared and S flag is set and a timing value higher - the N flag is cleared and the S flag is set and a timing
than the one received needs to be used interval larger than the one received needs to be used
Reserved: Reserved for future specification and set to 0. Reserved: Reserved for future specification and set to 0.
3.3.1. Local Discriminator sub-TLV 3.3.1. Local Discriminator sub-TLV
The "Local Discriminator sub-TLV" is carried as a sub-TLV of the "BFD The "Local Discriminator sub-TLV" is carried as a sub-TLV of the "BFD
Configuration sub-TLV" 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
skipping to change at page 11, line 38 skipping to change at page 11, line 25
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timer Neg. Type (2) (IANA) | Length = 20 | | Timer Neg. Type (2) (IANA) | Length = 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Acceptable Min. Asynchronous TX interval | | Acceptable Min. Asynchronous TX interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Acceptable Min. Asynchronous RX interval | | Acceptable Min. Asynchronous RX interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Required Echo TX Interval | | Required Echo TX Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Detect. Mult.| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: indicates a new type, the "Negotiation Timer Parameters sub- Type: indicates a new type, the "Negotiation Timer Parameters sub-
TLV" (IANA to define). TLV" (IANA to define).
Length: indicates the TLV total length in octets. (20) Length: indicates the TLV total length in octets. (20)
Acceptable Min. Asynchronous TX interval: in case of S (symmetric) Acceptable Min. Asynchronous TX interval: in case of S (symmetric)
flag set in the "BFD Configuration 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 LER initiating the time interval (in microseconds) at which the ingress LER intends to
signaling intends to both transmit and receive BFD periodic control both transmit and receive BFD periodic control packets. If the
packets. If the receiving edge LSR can not support such value, it is receiving edge LSR can not support such value, it can reply with an
allowed to reply back with an interval greater than the one proposed. interval greater than the one proposed.
In case of S (symmetric) flag cleared in the "BFD Configuration sub- In case of S (symmetric) flag cleared in the "BFD Configuration sub-
TLV", this field expresses the desired time interval (in TLV", this field expresses the desired time interval (in
microseconds) at which a edge LSR intends to transmit BFD periodic microseconds) at which a edge LSR intends to transmit BFD periodic
control packets in its transmitting direction. control packets in its transmitting direction.
Acceptable Min. Asynchronous RX interval: in case of S (symmetric) Acceptable Min. Asynchronous RX interval: in case of S (symmetric)
flag set in the "BFD Configuration sub-TLV", this field MUST be equal flag set in the "BFD Configuration sub-TLV", this field MUST be equal
to "Acceptable Min. Asynchronous TX interval" and has no additional to "Acceptable Min. Asynchronous TX interval" and has no additional
meaning respect to the one described for "Acceptable Min. meaning respect to the one described for "Acceptable Min.
skipping to change at page 12, line 34 skipping to change at page 12, line 19
Required Echo TX Interval: the minimum interval (in microseconds) Required Echo TX Interval: the minimum interval (in microseconds)
between received BFD Echo packets that this system is capable of between received BFD Echo packets that this system is capable of
supporting, less any jitter applied by the sender as described in supporting, less any jitter applied by the sender as described in
[RFC5880] sect. 6.8.9. This value is also an indication for the [RFC5880] sect. 6.8.9. This value is also an indication for the
receiving system of the minimum interval between transmitted BFD Echo receiving system of the minimum interval between transmitted BFD Echo
packets. If this value is zero, the transmitting system does not packets. If this value is zero, the transmitting system does not
support the receipt of BFD Echo packets. If the receiving system can support the receipt of BFD Echo packets. If the receiving system can
not support this value an error MUST be generated "Unsupported BFD TX not support this value an error MUST be generated "Unsupported BFD TX
rate interval". rate interval".
Detection time multiplier: The negotiated transmit interval,
multiplied by this value, provides the Detection Time for the
receiving system in Asynchronous mode.
Reserved: Reserved for future specification and set to 0.
3.3.3. BFD Authentication sub-TLV 3.3.3. BFD Authentication sub-TLV
The "BFD Authentication sub-TLV" is carried as a sub-TLV of the "BFD The "BFD Authentication sub-TLV" is carried as a sub-TLV of the "BFD
Configuration sub-TLV" and is depicted below. Configuration sub-TLV" and is depicted below.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BFD Auth. Type (3) (IANA) | Length = 8 | | BFD Auth. Type (3) (IANA) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 13, line 18 skipping to change at page 12, line 46
Auth Type: indicates which type of authentication to use. The same Auth Type: indicates which type of authentication to use. The same
values as are defined in section 4.1 of [RFC5880] are used. values as are defined in section 4.1 of [RFC5880] are used.
Auth Key ID: indicates which authentication key or password Auth Key ID: indicates which authentication key or password
(depending on Auth Type) should be used. How the key exchange is (depending on Auth Type) should be used. How the key exchange is
performed is out of scope of this document. performed is out of scope of this document.
Reserved: Reserved for future specification and set to 0. Reserved: Reserved for future specification and set to 0.
3.4. MPLS OAM PM Loss sub-TLV 3.4. Performance Monitoring sub-TLV
The "MPLS OAM PM Loss sub-TLV" depicted below is carried as a sub-TLV If the "OAM functions TLV" has either the L (Loss), D (Delay) or T
of the "OAM Configuration sub-TLV". (Throughput) flag set, the "Performance Monitoring sub-TLV" MUST be
present.
0 1 2 3 In case the vlues needs to be different than the default ones the
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 "Performance Monitoring sub-TLV", "MPLS OAM PM Loss sub-TLV" MAY
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ include the following sub-TLVs:
| PM Loss Type (3) (IANA) | Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Vers.|E|C| | Reserved (set to all 0s) | PHB |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Loss Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: indicates a new type, the "MPLS OAM PM Loss" (IANA to define). - "MPLS OAM PM Loss sub-TLV" if the L flag is set in the "OAM
functions TLV";
Length: indicates the TLV total length in octets. - "MPLS OAM PM Delay sub-TLV" if the D flag is set in the "OAM
functions TLV";
Version: indicates the Loss measurement protocol version. The "Performance Monitoring sub-TLV" depicted below is carried as a
sub-TLV of the "OAM Functions TLV".
Configuration Flags: 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Perf Monitoring Type (IANA)| Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|D|L|J|Y|K|C| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ sub-TLVs ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- E: exclude from the Loss Measurement all G-ACh messages Configuration Flags, for the specific function description please
refer to [MPLS-PM]:
- C: require the use of a counter in the "Querier Context" field - D: Delay inferred/direct (0=INFERRED, 1=DIRECT)
described in [MPLS-PM]
- Remaining bits: Reserved for future specification and set to 0. - L: Loss inferred/direct (0=INFERRED, 1=DIRECT)
PHB: identifies the per-hop behavior of packets with loss - J: Delay variation/jitter (1=ACTIVE, 0=NOT ACTIVE)
information.
- Y: Dyadic (1=ACTIVE, 0=NOT ACTIVE)
- K: Loopback (1=ACTIVE, 0=NOT ACTIVE)
- C: Combined (1=ACTIVE, 0=NOT ACTIVE)
3.4.1. MPLS OAM PM Loss sub-TLV
The "MPLS OAM PM Loss sub-TLV" depicted below is carried as a 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PM Loss Type (1) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OTF |T|B| RESERVED |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Test Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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.
Configuration Flags, please refer to [MPLS-PM] 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 Measurement Interval: the time interval (in microseconds) at which
Loss Measurement query messages MUST be sent on both directions. If Loss Measurement query messages MUST be sent on both directions. If
the edge LSR receiving the Path message can not support such value, the edge LSR receiving the Path message can not support such value,
it can reply back with a higher interval. it can reply back with a higher interval. By default it is set to
(TBD).
Test Interval: test messages interval as described in [MPLS-PM]. By
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. protections MUST be triggered. By default it is set to (TBD).
3.5. 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 Configuration sub-TLV". 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PM Delay Type (4) (IANA) | Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Vers.| Flags | Reserved (set to all 0s) | PHB |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delay Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: indicates a new type, the "MPLS OAM PM Delay" (IANA to define).
Length: indicates the TLV total length in octets. 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OTF |T|B| RESERVED |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Test Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delay Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Version: indicates the Delay measurement protocol version. Type: indicates a new type, the "MPLS OAM PM Loss sub-TLV" (IANA to
define, suggested value 1).
Configuration Flags: Length: indicates the length of the parameters in octets (12).
- E: exclude from the Loss Measurement all G-ACh messages OTF: Origin Timestamp Format of the Origin Timestamp field described
in [MPLS-PM]. By default it is set to IEEE 1588 version 1.
- C: require the use of a counter in the "Querier Context" field Configuration Flags, please refer to [MPLS-PM] for further details:
described in [MPLS-PM]
- Remaining bits: Reserved for future specification and set to 0. - 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.
PHB: - identifies the per-hop behavior of packets with delay - B: Octet (byte) count. When set to 1, indicates that the
information. 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 Measurement Interval: the time interval (in microseconds) at which
Delay Measurement query messages MUST be sent on both directions. If Delay Measurement query messages MUST be sent on both directions. If
the edge LSR receiving the Path message can not support such value, the edge LSR receiving the Path message can not support such value,
it can reply back with a higher interval. it can reply back with a higher interval. By default it is set to
(TBD).
Delay Threshold: the threshold value of measured delay (in Test Interval: test messages interval as described in [MPLS-PM]. By
microseconds) over which protections MUST be triggered. default it is set to (TBD).
[Author's note: TBD if we want to include the timestamp format Delay Threshold: the threshold value of measured delay (in
negotiation as in [MPLS-PM] 4.2.5.] microseconds) over which protections MUST be triggered. By default
it is set to (TBD).
3.6. 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) |E| PHB |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Refresh Timer | | Refresh Timer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: indicates a new type, the "MPLS OAM FMS" (IANA to define). Type: indicates a new type, the "MPLS OAM FMS sub-TLV" (IANA to
define).
Length: indicates the TLV total length in octets. Length: indicates the TLV total length in octets.
Signal Flags: are used to enable the following signals: Signal Flags: are used to enable the following signals:
- A: Alarm Indication Signal (AIS) as described in [MPLS-FMS] - A: Alarm Indication Signal (AIS) as described in [MPLS-FMS]
- D: Link Down Indication (LDI) as described in [MPLS-FMS] - D: Link Down Indication (LDI) as described in [MPLS-FMS]
- L: Locked Report (LKR) as described in [MPLS-FMS] - L: Locked Report (LKR) as described in [MPLS-FMS]
skipping to change at page 17, line 5 skipping to change at page 17, line 47
The authors would like to thank David Allan, Lou Berger, Annamaria The authors would like to thank David Allan, Lou Berger, Annamaria
Fulignoli, Eric Gray, Andras Kern, David Jocha and David Sinicrope Fulignoli, Eric Gray, Andras Kern, David Jocha and David Sinicrope
for their useful comments. for their useful comments.
7. Security Considerations 7. Security Considerations
The signaling of OAM related parameters and the automatic The signaling of OAM related parameters and the automatic
establishment of OAM entities introduces additional security establishment of OAM entities introduces additional security
considerations to those discussed in [RFC3473]. In particular, a considerations to those discussed in [RFC3473]. In particular, a
network element could be overloaded, if an attacker would request network element could be overloaded if an attacker were to request
liveliness monitoring, with frequent periodic messages, for a high high frequency liveliness monitoring of a large number of LSPs,
number of LSPs, targeting a single network element. targeting a single network element.
Security aspects will be covered in more detailed in subsequent Security aspects will be covered in more detailed in subsequent
versions of this document. versions of this document.
8. References 8. References
8.1. Normative References 8.1. Normative References
[MPLS-CSF]
He, J., Li, H., and E. Bellagamba, "Indication of Client
Failure in MPLS-TP", 2010, <draft-he-mpls-tp-csf>.
[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 [MPLS-PM] Bryant, S. and D. Frost, "Packet Loss and Delay
Measurement for the MPLS Transport Profile", 2010, Measurement for the MPLS Transport Profile", 2010,
<draft-ietf-mpls-tp-loss-delay>. <draft-ietf-mpls-loss-delay>.
[MPLS-PM-Profile] [MPLS-PM-Profile]
Bryant, S. and D. Frost, "A Packet Loss and Delay Bryant, S. and D. Frost, "A Packet Loss and Delay
Measurement Profile for MPLS-based Transport Networks", Measurement Profile for MPLS-based Transport Networks",
2010, <draft-ietf-mpls-tp-loss-delay-profile>. 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>.
skipping to change at page 19, line 33 skipping to change at page 20, line 26
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
Elisa Bellagamba (editor) Elisa Bellagamba (editor)
Ericsson Ericsson
Farogatan 6 Torshamnsgatan 48
Kista, 164 40 Kista, 164 40
Sweden Sweden
Phone: +46 761440785
Email: elisa.bellagamba@ericsson.com Email: elisa.bellagamba@ericsson.com
Loa Andersson (editor) Loa Andersson (editor)
Ericsson Ericsson
Farogatan 6 Torshamnsgatan 48
Kista, 164 40 Kista, 164 40
Sweden Sweden
Phone: Phone:
Email: loa.andersson@ericsson.com Email: loa.andersson@ericsson.com
Pontus Skoldstrom (editor) Pontus Skoldstrom (editor)
Acreo AB Acreo AB
Electrum 236 Electrum 236
Kista, 164 40 Kista, 164 40
Sweden Sweden
Phone: +46 8 6327731 Phone: +46 8 6327731
Email: pontus.skoldstrom@acreo.se Email: pontus.skoldstrom@acreo.se
Dave Ward Dave Ward
Juniper Juniper
Phone: Phone:
Email: dward@juniper.net Email: dward@juniper.net
Attila Takacs Attila Takacs
Ericsson Ericsson
1. Laborc u. 1. Laborc u.
Budapest, Budapest,
 End of changes. 75 change blocks. 
248 lines changed or deleted 296 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/