draft-ietf-mpls-tp-li-lb-00.txt   draft-ietf-mpls-tp-li-lb-01.txt 
Network Working Group Sami Boutros (Ed.) Network Working Group Sami Boutros (Ed.)
Internet Draft Siva Sivabalan (Ed.) Internet Draft Siva Sivabalan (Ed.)
Intended status: Standards Track Cisco Systems, Inc. Intended status: Standards Track Cisco Systems, Inc.
Expires: March 29, 2011 Expires: September 1, 2011
Rahul Aggarwal (Ed.) Rahul Aggarwal (Ed.)
Juniper Networks, Inc. Juniper Networks, Inc.
Martin Vigoureux (Ed.) Martin Vigoureux (Ed.)
Alcatel-Lucent Alcatel-Lucent
Xuehui Dai (Ed.) Xuehui Dai (Ed.)
ZTE Corporation ZTE Corporation
September 29, 2010 March 1, 2011
MPLS Transport Profile Lock Instruct and Loopback Functions MPLS Transport Profile Lock Instruct and Loopback Functions
draft-ietf-mpls-tp-li-lb-00.txt draft-ietf-mpls-tp-li-lb-01.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on March 29, 2007. This Internet-Draft will expire on September 1, 2011.
Abstract Abstract
This document specifies an extension to MPLS Operation, This document specifies an extension to MPLS Operation,
administration, and Maintenance (OAM) to operate an MPLS Transport administration, and Maintenance (OAM) to operate an Label Switched
Profile (MPLS-TP) Label Switched Path (LSP), bi-directional RSVP-TE Path (LSP), bi-directional RSVP-TE tunnels, Pseudowires (PW), or
tunnels, pseudowires (PW), or Multi-segment PWs in loopback mode for Multi-segment PWs in loopback mode for management purpose in an MPLS
management purpose. This extension includes mechanism to lock and based Transport. This extension includes mechanism to lock and
unlock MPLS-TP Tunnels (i.e. data and control traffic) and can be unlock MPLS-TP Tunnels (i.e. data and control traffic) and can be
used to loop all traffic (i.e, data and control traffic) at a used to loop all traffic (i.e, data and control traffic) at a
specified LSR on the path of the MPLS-TP LSP back to the source. specified LSR on the path of the LSP in an MPLS based Transport
Network back to the source. However, the mechanisms are intended to
be applicable to other aspects of MPLS as well.
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
2. Terminology....................................................4 2. Terminology....................................................5
3. MPLS-TP Loopback/Lock Mechanism................................5 3. Loopback/Lock Mechanism........................................5
3.1. In-band Message Identification............................5 3.1. In-band Message Identification............................5
3.2. MPLS LI-LB Message Format.................................5 3.2. LI-LB Message Format......................................6
3.3. LSP Ping Extensions.......................................8 3.3. LSP Ping Extensions.......................................8
3.3.1. Lock Request TLV.....................................8 3.3.1. Lock Request TLV.....................................8
3.3.2. Unlock Request TLV...................................8 3.3.2. Unlock Request TLV...................................8
3.3.3. Loopback Request TLV.................................8 3.3.3. Loopback Request TLV.................................8
3.3.4. Loopback Removal TLV.................................9 3.3.4. Loopback Removal TLV.................................9
3.3.5. Response TLV.........................................9 3.3.5. Response TLV.........................................9
3.3.6. Authentication TLV..................................10 3.3.6. Authentication TLV..................................10
4. Loopback/Lock Operations......................................10 4. Loopback/Lock Operations......................................10
4.1. Lock Request.............................................10 4.1. Lock Request.............................................10
4.2. Unlock Request...........................................10 4.2. Unlock Request...........................................10
4.3. Loopback Request.........................................11 4.3. Loopback Request.........................................11
4.4. Loopback Removal.........................................11 4.4. Loopback Removal.........................................11
5. Data packets..................................................11 5. Data packets..................................................11
6. Operation.....................................................12 6. Operation.....................................................11
6.1. General Procedures.......................................12 6.1. General Procedures.......................................11
6.2. Example Topology.........................................12 6.2. Example Topology.........................................12
6.3. Locking an LSP...........................................13 6.3. Locking an LSP...........................................12
6.4. Unlocking an LSP.........................................13 6.4. Unlocking an LSP.........................................13
6.5. Setting an LSP into Loopback mode........................14 6.5. Interoperability with Lock Instruct OAM function.........14
6.6. Removing an LSP from Loopback mode.......................15 6.6. Setting an LSP into Loopback mode........................14
6.7. Removing an LSP from Loopback mode.......................15
7. Security Considerations.......................................16 7. Security Considerations.......................................16
8. IANA Considerations...........................................16 8. IANA Considerations...........................................16
TBD..............................................................16 8.1. Pseudowire Associated Channel Type.......................16
9. References....................................................16 8.2. New LSP Ping TLV types...................................16
9.1. Normative References.....................................16 9. Acknowledgements..............................................17
9.2. Informative References...................................17 10. References...................................................17
Author's Addresses...............................................17 10.1. Normative References....................................17
10.2. Informative References..................................17
Author's Addresses...............................................18
Full Copyright Statement.........................................19 Full Copyright Statement.........................................19
Intellectual Property Statement..................................19 Intellectual Property Statement..................................20
1. Introduction 1. Introduction
In traditional transport networks, circuits are provisioned across In traditional transport networks, circuits are provisioned across
multiple nodes and service providers have the ability to operate the multiple nodes and service providers have the ability to operate the
transport circuit such as T1 line in loopback mode for management transport circuit such as T1 line in loopback mode for management
purposes, e.g., to test or verify connectivity of the circuit up to a purposes, e.g., to test or verify connectivity of the circuit up to a
specific node on the path of the circuit, to test the circuit specific node on the path of the circuit, to test the circuit
performance with respect to delay/jitter, etc. MPLS-TP bidirectional performance with respect to delay/jitter, etc. We need to provide the
LSP emulating traditional transport circuits need to provide the same same loopback capability for the bi-directional LSPs in MPLS based
loopback capability. The mechanisms in this document apply to Transport Networks emulating traditional transport circuits. The
associated bidirectional paths as defined in [7], which include MPLS- mechanisms in this document apply to co-routed bidirectional paths as
TP LSPs, bi-directional RSVP-TE tunnels, pseudowires (PW), and Multi- defined in [7], which include LSPs, bi-directional RSVP-TE tunnels,
segment PWs. Pseudowires (PW), and Multi-segment PWs in MPLS based Transport
Networks. However, the mechanisms are intended to be applicable to
other aspects of MPLS as well.
This document specifies how to operate the Lock and Loopback
functions over the Generic Associated Channel (GACh) and over LSP-
Ping. LSP-Ping is possible to run over the GACh or when IP-addressing
is available it is possible to run it natively. The first two cases
will work for MPLS based Transport Networks without IP-addressing.
To describe the loopback functionality, let us assume a bi- To describe the loopback functionality, let us assume a bi-
directional MPLS-TP LSP A <---> B <---> C <---> D where A, B, C, and directional LSP in a MPLS based Transport Network A <---> B <---> C
D are MPLS capable nodes. Also, let us assume that the network <---> D where A, B, C, and D are MPLS capable nodes. Also, let us
operator requires C to loop, back to A, the packets sent from A. In assume that the network operator requires C to loop, back to A, so
this example, A and D acts as Maintenance End Points (MEPs) and C that all the test data packets sent from A over that LSP. In this
acts as a Maintenance Intermediate Point (MIP). The operator can example, A and D acts as Maintenance End Points (MEPs) and C acts as
setup the MPLS-TP LSP into loopback mode such that C loops all the a Maintenance Intermediate Point (MIP). The operator can setup the
packets (regardless of whether they are data or control packets) LSP into loopback mode such that C loops all MPLS encapsulated
generated by node A back to A. The packets are not also forwarded packets (regardless of whether they are data or control packets) that
towards D. Similarly, any traffic received by C from the reverse A as an ingress LSR puts on the LSP back to A. The packets MUST NOT
direction will be dropped. be forwarded towards D. Similarly, any traffic received by C from the
reverse direction MUST be dropped.
The operator must take the MPLS-TP LSP out of service before setting For any LSP in a MPLS based Transport Network the operator must take
up the MPLS-TP LSP in loopback mode. This is accomplished by the MEP the LSP out of service before setting up the LSP in loopback mode.
establishing the loopback first sending a Lock command to the remote This is accomplished by the MEP establishing the loopback first
MEP(s). In the case above, A sends a Lock request message along the sending a Lock command to the remote MEP(s). In the case above, A
MPLS-TP LSP and destined to D to lock the MPLS-TP LSP. The message sends a Lock request message along the LSP and destined to D to lock
will be intercepted by D since it is at the end of the LSP. D the LSP. The message will be intercepted by D since it is at the end
responds to the lock request with a reply message specifying whether of the LSP. D responds to the lock request with a reply message
it can take the LSP out of service or not. specifying whether it can take the LSP out of service or not.
In order to set the MPLS-TP LSP in loopback mode, A sends a Loopback In order to set the LSP in loopback mode, A sends a Loopback request
request message to the MIP or MEP where the loopback is to be message to the MIP or MEP where the loopback is to be enabled. In the
enabled. In the above example, the MPLS TTL value is set so that the above example, the MPLS TTL value is set so that the message will be
message will be intercepted by C. intercepted by C.
This message contains a request to instruct C to operate the The request message contains a Loopback request to instruct C to
corresponding MPLS-TP LSP in Loopback mode. C responds to the operate an indicated LSP in Loopback mode. C responds to the Loopback
Loopback request with a reply message back to A to indicate whether request with a reply message back to A to indicate whether or not it
or not it has successfully set the MPLS-TP LSP into the loopback has successfully set the LSP into the loopback mode.
mode. If the loopback cannot be set, the reply message would contain
an error code. Upon receiving such a reply to the loopback request, A If the loopback cannot be set, the reply message would contain an
logs the event and takes further reporting actions as necessary. If error code. Upon receiving a reply with an error code to the loopback
the MPLS-TP LSP was previously locked, A sends another request request, A logs the event and takes further reporting actions as
necessary. If the LSP was previously locked, A sends another request
message to D to unlock it. message to D to unlock it.
If the loopback request can be performed, the input LSP from the If the loopback request can be performed, the input LSP from the
direction of A is directly cross-connected to the output LSP towards direction of A is directly cross-connected to the output LSP towards
A. All the packets generated by node A (data and control) are looped A. All the packets generated by node A (data and control) are looped
back at C, excepting the case of TTL expiration. back at C, excepting the case of TTL expiration.
When the loopback operation is no longer required, A sends a request When the loopback operation is no longer required, A sends a request
message to remove the loopback and thus restore the LSP to its message to remove the loopback and thus restore the LSP to its
original forwarding state. In this example the MPLS TTL is set such original forwarding state. In this example the MPLS TTL is set such
that this message is intercepted by C. It is expected that C sends a that this message is intercepted by C. It is expected that C sends a
reply back to A to with a return code either ACKing or NAK the reply back to A to with a return code either ACKing or NAK the
loopback removal request. Upon getting an ACK response to loopback loopback removal request. Upon getting an ACK response to loopback
mode removal request, A sends another request message to unlock the mode removal request, A sends another request message to unlock the
MPLS-TP LSP. The packet is intercepted by D as it is at the end of LSP. The packet is intercepted by D as it is at the end of the LSP.
the MPLS-TP LSP.
The proposed mechanism is based on a new set of messages and TLVs The proposed mechanism is based on a new set of messages and TLVs
which can be transported using one of the following methods: which can be transported using one of the following methods:
(1) An in-band MPLS message transported using a new ACH code point, (1) An in-band MPLS message transported using a new ACH code point,
the message will have different types to perform the loopback the message will have different types to perform the loopback
request/remove and Lock/unlock functions, and may carry new set of request/remove and Lock/unlock functions, and may carry new set of
TLVs. TLVs.
(2) A new set of TLVs which can be transported using LSP-Ping (2) A new set of TLVs which can be transported using LSP-Ping
skipping to change at page 5, line 16 skipping to change at page 5, line 38
MPLS-TP LSP: Bidirectional Label Switch Path representing a circuit MPLS-TP LSP: Bidirectional Label Switch Path representing a circuit
NMS: Network Management System NMS: Network Management System
TLV: Type Length Value TLV: Type Length Value
TTL: Time To Live TTL: Time To Live
LI-LB: Lock instruct-Loopback LI-LB: Lock instruct-Loopback
3. MPLS-TP Loopback/Lock Mechanism 3. Loopback/Lock Mechanism
For the in-band option, the proposed mechanism uses a new code point For the in-band option, the proposed mechanism uses a new code point
in the Associated Channel Header (ACH) described in [6]. in the Associated Channel Header (ACH) described in [6].
3.1. In-band Message Identification 3.1. In-band Message Identification
In the in-band option, the MPLS-TP LI-LB channel is identified by the In the in-band option, the LI-LB channel is identified by the ACH as
ACH as defined in RFC 5586 [6] with the Channel Type set to the MPLS- defined in RFC 5586 [6] with the Channel Type set to the LI-LB code
TP LI-LB code point = 0xHH. [HH to be assigned by IANA from the PW point = 0xHH. [HH to be assigned by IANA from the PW Associated
Associated Channel Type registry] The LI-LB Channel does not use ACH Channel Type registry] The LI-LB Channel does not use ACH TLVs and
TLVs and MUST not include the ACH TLV header. The LI-LB ACH MUST not include the ACH TLV header. The LI-LB ACH
Channel is shown below. Channel is shown 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 1|Version|Reserved | 0xHH (MPLS-TP LI-LB) | |0 0 0 1|Version|Reserved | 0xHH ( LI-LB) | +-+-
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: ACH Indication of MPLS-TP LI-LB Figure 1: ACH Indication of LI-LB
The LI-LB Channel is 0xHH (to be assigned by IANA) The LI-LB Channel is 0xHH (to be assigned by IANA)
3.2. MPLS LI-LB Message Format 3.2. LI-LB Message Format
The format of an MPLS-TP LI-LB Message is shown below. The format of an LI-LB Message is shown 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Operation | Reserved | | Version | Message Type | Operation | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Return Code | Cause Code | Message Length | | Return Code | Cause Code | Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender's Handle | | Sender's Handle |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 6, line 49 skipping to change at page 7, line 20
0x2 Unlock 0x2 Unlock
0x3 Set_Loopback 0x3 Set_Loopback
0x4 Unset_Loopback 0x4 Unset_Loopback
Message Length Message Length
The total length of any included TLVs. The total length of any included TLVs.
Sender's Handle Sender's Handle
The Sender's Handle is filled in by the sender, and returned The Sender's Handle is filled in by the sender, and MUST be copied
unchanged by the receiver in the MPLS response message (if any). unchanged by the receiver in the MPLS response message (if any).
There are no semantics associated with this handle, although a sender There are no semantics associated with this handle, although a sender
may find this useful for matching up requests with replies. may find this useful for matching up requests with replies.
Message ID Message ID
The Message ID is set by the sender of an MPLS request message. It The Message ID is set by the sender of an MPLS request message. It
MUST be copied unchanged by the receiver in the MPLS response message MUST be copied unchanged by the receiver in the MPLS response message
(if any). A sender SHOULD increment this value on each new message. (if any). A sender SHOULD increment this value on each new message.
A retransmitted message SHOULD leave the value unchanged. A retransmitted message SHOULD leave the value unchanged.
skipping to change at page 7, line 32 skipping to change at page 7, line 49
Cause code Cause code
Value Meaning Value Meaning
----- ------- ----- -------
0 No cause code 0 No cause code
1 Fail to match target MIP/MEP ID 1 Fail to match target MIP/MEP ID
2 Malformed request received 2 Malformed request received
3 One or more of the TLVs is/are unknown 3 One or more of the TLVs is/are unknown
4 Authentication failed 4 Authentication failed
5 MPLS-TP LSP/PW already locked 5 LSP/PW already locked
6 MPLS-TP LSP/PW already unlocked 6 LSP/PW already unlocked
7 Fail to lock MPLS-TP LSP/PW 7 Fail to lock LSP/PW
8 Fail to unlock MPLS-TP LSP/PW 8 Fail to unlock LSP/PW
9 MPLS-TP LSP/PW already in loopback mode 9 LSP/PW already in loopback mode
10 MPLS-TP LSP/PW is not in loopback mode 10 LSP/PW is not in loopback mode
11 Fail to set MPLS-TP LSP/PW in loopback mode 11 Fail to set LSP/PW in loopback mode
12 Fail to remove MPLS-TP/PW from loopback mode 12 Fail to remove LSP/PW from loopback mode
13 No label binding for received message 13 No label binding for received message
The Return code and Cause code only have meaning in a Response The Return code and Cause code only have meaning in a Response
message. In a request message the Return code and Cause code must be message. In a request message the Return code and Cause code must be
set to zero and ignored on receipt. set to zero and ignored on receipt.
3.3. LSP Ping Extensions 3.3. LSP Ping Extensions
3.3.1. Lock Request TLV 3.3.1. Lock Request 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 = TBD | length = 0 | | type = TBD | length = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
A MEP includes a Lock Request TLV in the MPLS LSP Ping echo request A MEP includes a Lock Request TLV in the MPLS LSP Ping echo request
message to request the MEP on the other side of the MPLS-TP LSP to message to request the MEP on the other side of the LSP to take the
take the LSP out of service. LSP out of service.
3.3.2. Unlock Request TLV 3.3.2. Unlock Request 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 = TBD | length = 0 | | type = TBD | length = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Unlock Request TLV is sent from the MEP which has previously sent The Unlock Request TLV is sent from the MEP which has previously sent
lock request. Upon receiving the LSP Ping Echo request message with lock request. Upon receiving the LSP Ping Echo request message with
the unlock request TLV, the receiver MEP brings the MPLS-TP LSP back the unlock request TLV, the receiver MEP brings the LSP back in
in service. service.
3.3.3. Loopback Request TLV 3.3.3. Loopback Request 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 = TBD | length = 0 | | type = TBD | length = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
When a MEP wants to put an MPLS-TP LSP in loopback mode, it sends a When a MEP wants to put an LSP in loopback mode, it sends a MPLS LSP
MPLS LSP Ping echo request message with Loopback Request TLV. The Ping echo request message with Loopback Request TLV. The message can
message can be intercepted by either a MIP or a MEP depending on the be intercepted by either a MIP or a MEP depending on the MPLS TTL
MPLS TTL value. The receiver puts in corresponding MPLS-TP LSP in value. The receiver puts in corresponding LSP in loopback mode.
loopback mode.
3.3.4. Loopback Removal TLV 3.3.4. Loopback Removal 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 = TBD | length = 0 | | type = TBD | length = 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
When loopback mode operation of an MPLS-TP LSP is no longer required, When loopback mode operation of an LSP is no longer required, the MEP
the MEP that previously sent the MPLS LSP Ping echo request message that previously sent the MPLS LSP Ping echo request message with a
with a loopback TLV, sends another MPLS LSP Ping echo request message loopback TLV, sends another MPLS LSP Ping echo request message with a
with a Loopback Removal TLV. The receiver MEP changes the MPLS-TP LSP Loopback Removal TLV. The receiver MEP changes the LSP from loopback
from loopback mode to normal mode of operation. mode to normal mode of operation.
3.3.5. Response TLV 3.3.5. Response 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 = TBD | Length = 0x1 | | type = TBD | Length = 0x1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|ReturnCode | |ReturnCode |
+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+
Return code Return code
Value Meaning Value Meaning
----- ------- ----- -------
0 Success 0 Success
1 Fail to match target MIP/MEP ID 1 Fail to match target MIP/MEP ID
2 Malformed loopback request received 2 Malformed loopback request received
3 One or more of the TLVs is/are unknown 3 One or more of the TLVs is/are unknown
4 Authentication failed 4 Authentication failed
5 MPLS-TP LSP/PW already locked 5 LSP/PW already locked
6 MPLS-TP LSP/PW already unlocked 6 LSP/PW already unlocked
7 Fail to lock MPLS-TP LSP/PW 7 Fail to lock LSP/PW
8 Fail to unlock MPLS-TP LSP/PW 8 Fail to unlock LSP/PW
9 MPLS-TP LSP/PW already in loopback mode 9 LSP/PW already in loopback mode
10 MPLS-TP LSP/PW is not in loopback mode 10 LSP/PW is not in loopback mode
11 Fail to set MPLS-TP LSP/PW in loopback mode 11 Fail to set LSP/PW in loopback mode
12 Fail to remove MPLS-TP LSP/PW from loopback mode 12 Fail to remove LSP/PW from loopback mode
13 No label binding for received message 13 No label binding for received message
Note that in the case of error code 3, the unknown TLV can also be Note that in the case of error code 3, the unknown TLV can also be
optionally included in the response TLV. optionally included in the response TLV.
3.3.6. Authentication TLV 3.3.6. Authentication 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 10, line 26 skipping to change at page 10, line 26
Loopback request. A variable length key can be carried in an optional Loopback request. A variable length key can be carried in an optional
authentication TLV which can be included in the MPLS OAM LSP Ping authentication TLV which can be included in the MPLS OAM LSP Ping
echo request message containing a loopback request TLV or the LI-LB echo request message containing a loopback request TLV or the LI-LB
Message. The use of authentication key is outside the scope of the Message. The use of authentication key is outside the scope of the
document. document.
4. Loopback/Lock Operations 4. Loopback/Lock Operations
4.1. Lock Request 4.1. Lock Request
Lock Request is used to request a MEP to take an MPLS-TP LSP out of Lock Request is used to request a MEP to take an LSP out of service
service so that some form of maintenance can be done. so that some form of maintenance can be done.
The receiver MEP MUST send either an ACK or a NAK response to the The receiver MEP MUST send either an ACK or a NAK response to the
sender MEP. Until the sender MEP receives an ACK, it MUST NOT assume sender MEP. Until the sender MEP receives an ACK, it MUST NOT assume
that the receiver MEP has taken the MPLS-TP LSP out of service. A that the receiver MEP has taken the LSP out of service. A receiver
receiver MEP sends an ACK only if it can successfully lock the MPLS- MEP sends an ACK only if it can successfully lock the LSP. Otherwise,
TP LSP. Otherwise, it sends a NAK. it sends a NAK.
4.2. Unlock Request 4.2. Unlock Request
The Unlock Request is sent from the MEP which has previously sent The Unlock Request is sent from the MEP which has previously sent
lock request. Upon receiving the unlock request message, the receiver lock request. Upon receiving the unlock request message, the receiver
MEP brings the MPLS-TP LSP back in service. MEP brings the LSP back in service.
The receiver MEP MUST send either an ACK or a NAK response to the The receiver MEP MUST send either an ACK or a NAK response to the
sender MEP. Until the sender MEP receives an ACK, it MUST NOT assume sender MEP. Until the sender MEP receives an ACK, it MUST NOT assume
that the MPLS-TP LSP has been put back in service. A receiver MEP that the LSP has been put back in service. A receiver MEP sends an
sends an ACK only if the MPLS-TP LSP has been unlocked, and unlock ACK only if the LSP has been unlocked, and unlock operation is
operation is successful. Otherwise, it sends a NAK. successful. Otherwise, it sends a NAK.
4.3. Loopback Request 4.3. Loopback Request
When a MEP wants to put an MPLS-TP LSP in loopback mode, it sends a When a MEP wants to put an LSP in loopback mode, it sends a Loopback
Loopback request message. The message can be intercepted by either a request message. The message can be intercepted by either a MIP or a
MIP or a MEP depending on the MPLS TTL value. The receiver puts in MEP depending on the MPLS TTL value. The receiver puts in
corresponding MPLS-TP LSP in loopback mode. corresponding LSP in loopback mode.
The receiver MEP or MIP MUST send either an ACK or NAK response to The receiver MEP or MIP MUST send either an ACK or NAK response to
the sender MEP. An ACK response is sent if the MPLS-TP LSP is the sender MEP. An ACK response is sent if the LSP is successfully
successfully put in loopback mode. Otherwise, a NAK response is sent. put in loopback mode. Otherwise, a NAK response is sent. Until an ACK
Until an ACK response is received, the sender MEP MUST NOT assume response is received, the sender MEP MUST NOT assume that the LSP can
that the MPLS-TP LSP can operate in loopback mode. operate in loopback mode.
4.4. Loopback Removal 4.4. Loopback Removal
When loopback mode operation of an MPLS-TP LSP is no longer required, When loopback mode operation of an LSP is no longer required, the MEP
the MEP that previously sent the Loopback request message sends that previously sent the Loopback request message sends another
another Loopback Removal message. The receiver MEP changes the MPLS- Loopback Removal message. The receiver MEP changes the LSP from
TP LSP from loopback mode to normal mode of operation. loopback mode to normal mode of operation.
The receiver MEP or MIP MUST send either an ACK or NAK response to The receiver MEP or MIP MUST send either an ACK or NAK response to
the sender MEP. An ACK response is sent if the MPLS-TP LSP is already the sender MEP. An ACK response is sent if the LSP is already in
in loopback mode, and if the MPLS-TP LSP is successfully put back in loopback mode, and if the LSP is successfully put back in normal
normal operation mode. Otherwise, a NAK response is sent. Until an operation mode. Otherwise, a NAK response is sent. Until an ACK
ACK response is received, the sender MEP MUST NOT assume that the response is received, the sender MEP MUST NOT assume that the LSP is
MPLS-TP LSP is put back in normal operation mode. put back in normal operation mode.
5. Data packets 5. Data packets
Data packets sent from the sender MEP will be looped back to that Data packets sent from the sender MEP will be looped back to that
sender MEP. In order for the sender MEP node to make sure that no sender MEP. The use of data packets to measure packet loss, delay and
data packets are dropped, each data MPLS packets may contain a delay variation is outside the scope of this document.
sequence-id right after the label stack. A time-stamp fields in the
data packets can help calculate the Round trip delay of datapackets.
The Local Time-Stamp is set by the sender, and can be used to
calculate the round trip delay after the message is looped back.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Label with EOS bit set |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence-Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Time-Stamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Time-Stamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Arbitrary Padding |
: :
| Arbitrary Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
6. Operation 6. Operation
6.1. General Procedures 6.1. General Procedures
When placing an LSP into Loopback mode, the operation MUST first be When placing an LSP into Loopback mode, the operation MUST first be
preceded by a Lock operation. preceded by a Lock operation.
Sending LSP Ping Echo Request message with Loopback Request/Removal Sending LSP Ping Echo Request message with Loopback Request/Removal
or in-Band Loopback Request/Removal Message or in-Band Loopback Request/Removal Message
skipping to change at page 12, line 40 skipping to change at page 12, line 19
However, to remove a MEP from Loopback mode, the sending MEP MUST set However, to remove a MEP from Loopback mode, the sending MEP MUST set
the TTL to the exact number of hops required to reach the MEP (if the the TTL to the exact number of hops required to reach the MEP (if the
TTL were set higher, the Loopback removal message would be looped TTL were set higher, the Loopback removal message would be looped
back toward the sender). It is RECOMMENDED that the TTL be set to the back toward the sender). It is RECOMMENDED that the TTL be set to the
exact number of hops required to reach the MEP. exact number of hops required to reach the MEP.
6.2. Example Topology 6.2. Example Topology
The next four sections discuss the procedures for Locking, Unlocking, The next four sections discuss the procedures for Locking, Unlocking,
setting an LSP into loopback, and removing the loopback. The setting an LSP into loopback, and removing the loopback. The
description is worded using an example. Assume an MPLS-TP LSP description is worded using an example. Assume an LSP traverses nodes
traverses nodes A <--> B <--> C <--> D. We will refer to the A <--> B <--> C <--> D. We will refer to the Maintenance Entities
Maintenance Entities involved as MEP-A, MIP-B, MIP-C, and MEP-D involved as MEP-A, MIP-B, MIP-C, and MEP-D respectively. Suppose a
respectively. Suppose a maintenance operation invoked at node A maintenance operation invoked at node A requires a loopback be set at
requires a loopback be set at node C. To invoke Loopack mode at node node C. To invoke Loopack mode at node C, A would first need to lock
C, A would first need to lock the LSP. Then it may proceed to set the the LSP. Then it may proceed to set the loopback at C. Following the
loopback at C. Following the loopback operation, A would need to loopback operation, A would need to remove the loopback at C and
remove the loopback at C and finally unlock the LSP. finally unlock the LSP.
The following sections describe MEP-A setting and unsetting a lock at The following sections describe MEP-A setting and unsetting a lock at
MEP-D and then setting and removing a loopback at MIP-C. MEP-D and then setting and removing a loopback at MIP-C.
6.3. Locking an LSP 6.3. Locking an LSP
1. MEP-A sends an MPLS LSP Ping Echo request message with the Lock 1. MEP-A sends an MPLS LSP Ping Echo request message with the Lock
TLV or an in-Band Lock request Message. Optionally, an authentication TLV or an in-Band Lock request Message. Optionally, an authentication
TLV MAY be included. TLV MAY be included.
skipping to change at page 13, line 34 skipping to change at page 13, line 11
c. if the message is malformed, it sends a response with error code 2 c. if the message is malformed, it sends a response with error code 2
back to MEP-A. back to MEP-A.
d. if message authentication fails, it MAY send a response with error d. if message authentication fails, it MAY send a response with error
code 4 back to MEP-A. code 4 back to MEP-A.
e. if any of the TLVs is not known, it sends a response with error e. if any of the TLVs is not known, it sends a response with error
code 3 back to MEP-A. It may also include the unknown TLVs. code 3 back to MEP-A. It may also include the unknown TLVs.
f. if the MPLS-TP LSP is already locked, it sends a response with f. if the LSP is already locked, it sends a response with
error code 5 back to MEP-A. error code 5 back to MEP-A.
g. if the MPLS-TP LSP is not already locked and cannot be locked, it g. if the LSP is not already locked and cannot be locked, it sends a
sends a response with error code 7 back to A. response with error code 7 back to A.
h. if the MPLS-TP LSP is successfully locked, it sends a response h. if the LSP is successfully locked, it sends a response with error
with error code 0 (Success) back to MEP-A. code 0 (Success) back to MEP-A.
The response is sent using an MPLS LSP Ping echo reply with a The response is sent using an MPLS LSP Ping echo reply with a
response TLV or an in-Band Lock response message. An authentication response TLV or an in-Band Lock response message. An authentication
TLV MAY be included. TLV MAY be included.
6.4. Unlocking an LSP 6.4. Unlocking an LSP
1. MEP-A sends an MPLS Echo request message with the unLock TLV or an 1. MEP-A sends an MPLS Echo request message with the unLock TLV or an
in-Band unLock request Message. Optionally, an authentication TLV MAY in-Band unLock request Message. Optionally, an authentication TLV MAY
be included. be included.
skipping to change at page 14, line 25 skipping to change at page 13, line 53
c. if the message is malformed, it sends a response with error code 2 c. if the message is malformed, it sends a response with error code 2
back to MEP-A. back to MEP-A.
d. if message authentication fails, it MAY send a response with error d. if message authentication fails, it MAY send a response with error
code 4 back to MEP-A. code 4 back to MEP-A.
e. if any of the TLVs is not known, it sends a response with error e. if any of the TLVs is not known, it sends a response with error
code 3 back to MEP-A. It may also include the unknown TLVs. code 3 back to MEP-A. It may also include the unknown TLVs.
f. if the MPLS-TP LSP is already unlocked, it sends a response with f. if the LSP is already unlocked, it sends a response with
error code 6 back to MEP-A. error code 6 back to MEP-A.
g. if the LSP is locked and cannot be unlocked, it sends a response g. if the LSP is locked and cannot be unlocked, it sends a response
with error code 8 back to MEP-A. with error code 8 back to MEP-A.
h. if the LSP is successfully unlocked, it sends a response with h. if the LSP is successfully unlocked, it sends a response with
error code 0 (Success) back to MEP-A. error code 0 (Success) back to MEP-A.
The response is sent using an MPLS LSP Ping echo reply with a The response is sent using an MPLS LSP Ping echo reply with a
response TLV or an in-Band unlock response message. An authentication response TLV or an in-Band unlock response message. An authentication
TLV MAY be included. TLV MAY be included.
6.5. Setting an LSP into Loopback mode 6.5. Interoperability with Lock Instruct OAM function
a. Upon receiving a lock instruct MEP-D will lock the LSP,
resulting in that all traffic from D to A, including OAM, stops.
b. MEP-A will detect a discontinuation in the OAM traffic, e.g. cv
and cc, but since it has been informed that the LSP will be
locked it will take no action(s).
c. MEP-D will send an LI Ack, and be prepared that all traffic,
including OAM will stop
d. When MEP-A receives the LI ACK, MEP-A discontinues sending OAM
traffic.
e. MEP-D will detect this, but since it is in Locked state it will
take no action.
6.6. Setting an LSP into Loopback mode
1. MEP-A sends an MPLS LSP Ping Echo request message with the 1. MEP-A sends an MPLS LSP Ping Echo request message with the
loopback TLV or an in-Band Loopback request message. Optionally, an loopback TLV or an in-Band Loopback request message. Optionally, an
authentication TLV MAY be included. authentication TLV MAY be included.
2. Upon intercepting the MPLS Loopback message via TTL expiration, C 2. Upon intercepting the MPLS Loopback message via TTL expiration, C
uses the received label stack and target FEC/source MEP-ID to uses the received label stack and target FEC/source MEP-ID to
identify the LSP. identify the LSP.
If no label binding exists or there is no associated LSP back to the If no label binding exists or there is no associated LSP back to the
skipping to change at page 15, line 22 skipping to change at page 15, line 16
c. if the message is malformed, it sends a response with error code 2 c. if the message is malformed, it sends a response with error code 2
back to MEP-A. back to MEP-A.
d. if the message authentication fails, it sends a response with d. if the message authentication fails, it sends a response with
error code 4 back to MEP-A. error code 4 back to MEP-A.
e. if any of the TLV is not known, C sends a response with error code e. if any of the TLV is not known, C sends a response with error code
3 back to MEP-A. It may also include the unknown TLVs. 3 back to MEP-A. It may also include the unknown TLVs.
f. if the MPLS-TP LSP is already in the requested loopback mode, it f. if the LSP is already in the requested loopback mode, it sends a
sends a response with error code 9 back to MEP-A. response with error code 9 back to MEP-A.
g. if the MPLS-TP LSP is not already in the requested loopback mode g. if the LSP is not already in the requested loopback mode and that
and that loopback mode cannot be set, it sends a response with error loopback mode cannot be set, it sends a response with error code 11
code 11 back to MEP-A. back to MEP-A.
h. if the MPLS-TP LSP is successfully programmed into the requested h. if the LSP is successfully programmed into the requested loopback
loopback mode, it sends a response with error code 0 (Success) back mode, it sends a response with error code 0 (Success) back to MEP-A.
to MEP-A.
The response is sent using an MPLS LSP Ping echo reply with a The response is sent using an MPLS LSP Ping echo reply with a
response TLV or an in-Band Loopback response message. An response TLV or an in-Band Loopback response message. An
authentication TLV MAY be included. authentication TLV MAY be included.
6.6. Removing an LSP from Loopback mode 6.7. Removing an LSP from Loopback mode
1. MEP-A sends a MPLS LSP Ping Echo request message with the Loopback 1. MEP-A sends a MPLS LSP Ping Echo request message with the Loopback
removal TLV or an in-Band Loopback removal request message. removal TLV or an in-Band Loopback removal request message.
Optionally, an authentication TLV MAY be included. Optionally, an authentication TLV MAY be included.
2. Upon intercepting the MPLS Loopback removal message via TTL 2. Upon intercepting the MPLS Loopback removal message via TTL
expiration, C uses the received label stack and the target FEC/source expiration, C uses the received label stack and the target FEC/source
MEP-ID to identify the LSP. MEP-ID to identify the LSP.
If no label binding exists or there is no associated LSP back to If no label binding exists or there is no associated LSP back to
skipping to change at page 16, line 19 skipping to change at page 16, line 14
c. if the message is malformed, it sends a response with error code 2 c. if the message is malformed, it sends a response with error code 2
back to MEP-A. back to MEP-A.
d. if the message authentication fails, it sends a response with d. if the message authentication fails, it sends a response with
error code 4 back to MEP-A. error code 4 back to MEP-A.
e. if any of the TLV is not known, C sends a response with error code e. if any of the TLV is not known, C sends a response with error code
3 back to MEP-A. It may also include the unknown TLVs. 3 back to MEP-A. It may also include the unknown TLVs.
f. if the MPLS-TP is not in loopback mode, it sends a response with f. if the LSP is not in loopback mode, it sends a response with error
error code 10 back to MEP-A. code 10 back to MEP-A.
g. if the MPLS-TP LSP loopback cannot be removed, it sends a response g. if the LSP loopback cannot be removed, it sends a response with
with error code 12 back to MEP-A. error code 12 back to MEP-A.
h. if the MPLS-TP is successfully changed from loopback mode to h. if the LSP is successfully changed from loopback mode to normal
normal mode of operation, it sends a reply with error code 0 (Success mode of operation, it sends a reply with error code 0 (Success ) back
) back to MEP-A. to MEP-A.
The response is sent using an MPLS LSP Ping echo reply with a The response is sent using an MPLS LSP Ping echo reply with a
response TLV or an in-Band Loopback removal response message. An response TLV or an in-Band Loopback removal response message. An
authentication TLV MAY be included. authentication TLV MAY be included.
7. Security Considerations 7. Security Considerations
The security considerations for the authentication TLV need further The security considerations for the authentication TLV need further
study. study.
8. IANA Considerations 8. IANA Considerations
TBD 8.1. Pseudowire Associated Channel Type
9. References LI-LB OAM requires a unique Associated Channel Type which is assigned
by IANA from the Pseudowire Associated Channel Types Registry.
9.1. Normative References Registry:
Value Description TLV Follows Reference
----------- ----------------------- ----------- ---------
0xHHHH LI-LB No (Section 3.1)
8.2. New LSP Ping TLV types
IANA is requested to assign TLV type values to the following TLVs
from the "Multiprotocol Label Switching Architecture (MPLS) Label
Switched Paths (LSPs) Parameters - TLVs" registry, "TLVs and sub-
TLVs" sub-registry.
1. Lock Request TLV (See section 3.3.1)
2. Unlock Request TLV (See section 3.3.2)
3. Loopback Request TLV (See section 3.3.3)
4. Loopback Removal TLV (See section 3.3.4)
5. Response TLV (See section 3.3.5)
6. Authentication TLV (See section 3.3.6)
9. Acknowledgements
The authors would like to thank Loa Andersson for his valuable
comments.
10. References
10.1. Normative References
[1] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., and [1] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., and
S. Ueno, "Requirements of an MPLS Transport Profile", RFC 5654, S. Ueno, "Requirements of an MPLS Transport Profile", RFC 5654,
September 2009. September 2009.
[2] Vigoureux, M., Ward, D., and M. Betts, "Requirements for [2] Vigoureux, M., Ward, D., and M. Betts, "Requirements for
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.
[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement
skipping to change at page 17, line 25 skipping to change at page 17, line 48
[6] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic [6] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic
Associated Channel", RFC 5586, June 2009. Associated Channel", RFC 5586, June 2009.
[7] Bocci, M. and G. Swallow, "MPLS-TP Identifiers", draft-ietf- [7] Bocci, M. and G. Swallow, "MPLS-TP Identifiers", draft-ietf-
mpls-tp-identifiers-01 (work in progress), June 2010. mpls-tp-identifiers-01 (work in progress), June 2010.
[8] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., and [8] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., and
S.Ueno, "Requirements of an MPLS Transport Profile", RFC 5654, S.Ueno, "Requirements of an MPLS Transport Profile", RFC 5654,
September 2009. September 2009.
9.2. Informative References 10.2. Informative References
[9] Nabil Bitar, et. al, "Requirements for Multi-Segment Pseudowire [9] Nabil Bitar, et. al, "Requirements for Multi-Segment Pseudowire
Emulation Edge-to-Edge (PWE3) ", RFC5254, October 2008. Emulation Edge-to-Edge (PWE3) ", RFC5254, October 2008.
Author's Addresses Author's Addresses
Sami Boutros Sami Boutros
Cisco Systems, Inc. Cisco Systems, Inc.
Email: sboutros@cisco.com Email: sboutros@cisco.com
 End of changes. 60 change blocks. 
189 lines changed or deleted 223 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/