draft-ietf-teas-rsvp-te-li-lb-00.txt   draft-ietf-teas-rsvp-te-li-lb-01.txt 
Network Working Group J. Dong Network Working Group J. Dong
Internet-Draft M. Chen Internet-Draft M. Chen
Intended status: Standards Track Huawei Technologies Intended status: Standards Track Huawei Technologies
Expires: June 13, 2015 Z. Li Expires: July 3, 2015 Z. Li
China Mobile China Mobile
D. Ceccarelli D. Ceccarelli
Ericsson Ericsson
December 10, 2014 December 30, 2014
GMPLS RSVP-TE Extensions for Lock Instruct and Loopback GMPLS RSVP-TE Extensions for Lock Instruct and Loopback
draft-ietf-teas-rsvp-te-li-lb-00 draft-ietf-teas-rsvp-te-li-lb-01
Abstract Abstract
This document specifies extensions to Resource Reservation Protocol- This document specifies extensions to Resource Reservation Protocol-
Traffic Engineering (RSVP-TE) to support Lock Instruct (LI) and Traffic Engineering (RSVP-TE) to support Lock Instruct (LI) and
Loopback (LB) mechanisms for Label Switched Paths (LSPs). These Loopback (LB) mechanisms for Label Switched Paths (LSPs). These
mechanisms are applicable to technologies which use Generalized mechanisms are applicable to technologies which use Generalized
Multi-Protocol Label Switching (GMPLS) as control plane. Multi-Protocol Label Switching (GMPLS) as control plane.
Requirements Language Requirements Language
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 June 13, 2015. This Internet-Draft will expire on July 3, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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
skipping to change at page 2, line 26 skipping to change at page 2, line 26
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 . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Flag Definitions for LI and LB . . . . . . . . . . . . . . . 3 2. Flag Definitions for LI and LB . . . . . . . . . . . . . . . 3
2.1. Lock Instruct Indication . . . . . . . . . . . . . . . . 3 2.1. Lock Instruct Indication . . . . . . . . . . . . . . . . 3
2.2. Extensions for Loopback . . . . . . . . . . . . . . . . . 3 2.2. Extensions for Loopback . . . . . . . . . . . . . . . . . 3
3. Operational Procedures . . . . . . . . . . . . . . . . . . . 4 3. Operational Procedures . . . . . . . . . . . . . . . . . . . 3
3.1. Lock Instruct . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Lock Instruct . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Loopback . . . . . . . . . . . . . . . . . . . . . . . . 5 3.2. Loopback . . . . . . . . . . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
4.1. Attribute Flags . . . . . . . . . . . . . . . . . . . . . 6 4.1. Attribute Flags . . . . . . . . . . . . . . . . . . . . . 5
4.2. RSVP Error Value Sub-codes . . . . . . . . . . . . . . . 6 4.2. RSVP Error Value Sub-codes . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 7 7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . 7 7.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
The requirements for Lock Instruct (LI) and Loopback (LB) in The requirements for Lock Instruct (LI) and Loopback (LB) in
Multiprotocol Label Switching Transport Profile (MPLS-TP) are Multiprotocol Label Switching Transport Profile (MPLS-TP) are
specified in [RFC5860], and the framework of LI and LB is specified specified in [RFC5860], and the framework of LI and LB is specified
in [RFC6371]. in [RFC6371].
skipping to change at page 3, line 25 skipping to change at page 3, line 25
applicable to technologies which use GMPLS as control plane. For applicable to technologies which use GMPLS as control plane. For
MPLS-TP network, the mechanisms defined in this document are MPLS-TP network, the mechanisms defined in this document are
complementary to [RFC6435]. complementary to [RFC6435].
2. Flag Definitions for LI and LB 2. Flag Definitions for LI and LB
2.1. Lock Instruct Indication 2.1. Lock Instruct Indication
In order to indicate the lock/unlock of the LSP, the A In order to indicate the lock/unlock of the LSP, the A
(Administratively down) bit in ADMIN_STATUS object [RFC3471] (Administratively down) bit in ADMIN_STATUS object [RFC3471]
[RFC3473] is used. The format of ADMIN_STATUS Object is as below: [RFC3473] is used.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | Class-Num(196)| C-Type (1) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|R| Reserved |M|O|H|L|I|C|T|A|D|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1. Admin_Status Object
Reflect (R): 1 bit - see [RFC3471]
OAM Flows Enabled (M): 1 bit - see [RFC7260]
OAM Alarms Enabled (O): 1 bit - see [RFC7260]
Handover (H): 1 bit - see [RFC5852]
Lockout (L): 1 bit - see [RFC4872]
Inhibit Alarm Indication (I): 1 bit - see [RFC4783]
Call Control (C): 1 bit - see [RFC4974]
Testing (T): 1 bit - see [RFC3471]
Administratively down (A): 1 bit - see [RFC3471], reused for Lock
Deletion in progress (D): 1 bit - see [RFC3471]
2.2. Extensions for Loopback 2.2. Extensions for Loopback
In order to indicate the loopback mode of LSP, a new bit flag is In order to indicate the loopback mode of LSP, a new bit flag is
defined in the Attribute Flags TLV [RFC5420]. defined in the Attribute Flags TLV [RFC5420].
Loopback flag: Loopback flag:
This flag indicates a particular node on the LSP is required to This flag indicates a particular node on the LSP is required to
enter loopback mode. This can also be used for specifying the enter loopback mode. This can also be used for specifying the
skipping to change at page 4, line 35 skipping to change at page 4, line 16
On receipt of this Path message, the egress LSR SHOULD try to take On receipt of this Path message, the egress LSR SHOULD try to take
the LSP out of service. If the egress LSR locks the LSP the LSP out of service. If the egress LSR locks the LSP
successfully, it MUST send a Resv message with the A bit in successfully, it MUST send a Resv message with the A bit in
ADMIN_STATUS object set. Otherwise, it MUST send a PathErr message ADMIN_STATUS object set. Otherwise, it MUST send a PathErr message
with the Error Code "OAM Problem" [RFC7260] and the new Error Value with the Error Code "OAM Problem" [RFC7260] and the new Error Value
"Lock Failure", and the following Resv messages MUST be sent with the "Lock Failure", and the following Resv messages MUST be sent with the
A bit cleared. A bit cleared.
When an LSP is put in lock mode, the subsequent Path and Resv When an LSP is put in lock mode, the subsequent Path and Resv
messages SHOULD keep the A bit in ADMIN_STATUS Object set. messages MUST keep the A bit in ADMIN_STATUS Object set.
When the ingress LSR intends to take the LSP out of the lock mode, it When the ingress LSR intends to take the LSP out of the lock mode, it
MUST send a Path message with the A bit in ADMIN_STATUS Object MUST send a Path message with the A bit in ADMIN_STATUS Object
cleared. cleared.
On receipt of this Path message, the egress LSR SHOULD try to bring On receipt of this Path message, the egress LSR SHOULD try to bring
the LSP back to service. If the egress LSR unlocks the LSP the LSP back to service. If the egress LSR unlocks the LSP
successfully, it MUST send a Resv message with the A bit in successfully, it MUST send a Resv message with the A bit in
ADMIN_STATUS Object cleared. Otherwise, it MUST send a PathErr ADMIN_STATUS Object cleared. Otherwise, it MUST send a PathErr
message with the Error Code "OAM Problem" [RFC7260] and the new Error message with the Error Code "OAM Problem" [RFC7260] and the new Error
Value "Unlock Failure", and the following Resv messages MUST be sent Value "Unlock Failure", and the following Resv messages MUST be sent
with the A bit set. with the A bit set.
When an LSP is taken out of lock mode, the subsequent Path and Resv When an LSP is taken out of lock mode, the subsequent Path and Resv
messages SHOULD keep the A bit in ADMIN_STATUS Object cleared. messages MUST keep the A bit in ADMIN_STATUS Object cleared.
3.2. Loopback 3.2. Loopback
The loopback request can be sent either to the egress LSR or to a The loopback request can be sent either to the egress LSR or to a
particular intermediate node. The mechanism defined in particular intermediate node. The mechanism defined in
[I-D.ietf-ccamp-lsp-attribute-ro] is used for addressing the loopback [I-D.ietf-ccamp-lsp-attribute-ro] is used for addressing the loopback
request to a particular node on the LSP. The ingress LSR MUST ensure request to a particular node on the LSP. The ingress LSR MUST ensure
that the LSP is in lock mode before it requests setting a particular that the LSP is in lock mode before it requests setting a particular
node on the LSP into loopback mode. node on the LSP into loopback mode.
When a ingress LSR intends to put a particular node on the LSP into When a ingress LSR intends to put a particular node on the LSP into
loopback mode, it MUST send a Path message with the Loopback bit loopback mode, it MUST send a Path message with the Loopback
defined above in the Attribute Flags TLV set. The mechanism defined Attribute Flag defined above in the Attribute Flags TLV set. The
in [I-D.ietf-ccamp-lsp-attribute-ro] is used to address the loopback mechanism defined in [I-D.ietf-ccamp-lsp-attribute-ro] is used to
request to the particular LSR. The Administratively down (A) bit in address the loopback request to the particular LSR. The
ADMIN_STATUS object MUST be kept set to indicate that the LSP is Administratively down (A) bit in ADMIN_STATUS object MUST be kept set
still in lock mode. to indicate that the LSP is still in lock mode.
On receipt of this Path message, the target LSR of the loopback On receipt of this Path message, the target LSR of the loopback
request SHOULD try to put the LSP into loopback mode. If the node request SHOULD try to put the LSP into loopback mode. If the node
puts the LSP into loopback mode successfully, it MUST set the puts the LSP into loopback mode successfully, it MUST set the
Loopback (B) bit in the Record Route Object (RRO) Attribute subobject Loopback Attribute Flag in the Record Route Object (RRO) Attribute
[RFC5420] and push this subobject onto the RRO object in the subobject [RFC5420] and push this subobject onto the RRO object in
corresponding Resv message. The Administratively down (A) bit in the corresponding Resv message. The Administratively down (A) bit in
ADMIN_STATUS object MUST be kept set in the Resv message. If the ADMIN_STATUS object MUST be kept set in the Resv message. If the
node cannot put the LSP into loopback mode, it MUST send a PathErr node cannot put the LSP into loopback mode, it MUST send a PathErr
message with the Error Code "OAM Problem" [RFC7260] and the new Error message with the Error Code "OAM Problem" [RFC7260] and the new Error
Value "Loopback Failure". Value "Loopback Failure".
When the ingress LSR intends to take the particular node out of When the ingress LSR intends to take the particular node out of
loopback mode, it MUST send a Path message with the Loopback (B) bit loopback mode, it MUST send a Path message with the Loopback
in the Attribute Flags TLV cleared. The mechanism defined in Attribute Flag in the Attribute Flags TLV cleared. The mechanism
[I-D.ietf-ccamp-lsp-attribute-ro] is used to indicate that the defined in [I-D.ietf-ccamp-lsp-attribute-ro] is used to indicate that
particular LSR SHOULD exit loopback mode for this LSP. The the particular LSR SHOULD exit loopback mode for this LSP. The
Administratively down (A) bit in ADMIN_STATUS object MUST be kept set Administratively down (A) bit in ADMIN_STATUS object MUST be kept set
to indicate the LSP is still in lock mode. to indicate the LSP is still in lock mode.
On receipt of this Path message, the target LSR SHOULD try to take On receipt of this Path message, the target LSR SHOULD try to take
the LSP out of loopback mode. If the node takes the LSP out of the LSP out of loopback mode. If the node takes the LSP out of
loopback mode successfully, it MUST clear the Loopback (B) Bit in the loopback mode successfully, it MUST clear the Loopback Attribute Flag
RRO Attribute subobject and push this subobject onto the RRO object in the RRO Attribute subobject and push this subobject onto the RRO
in the corresponding Resv message. The Administratively down (A) Bit object in the corresponding Resv message. The Administratively down
in ADMIN_STATUS Object MUST be kept set in the Resv message. (A) Bit in ADMIN_STATUS Object MUST be kept set in the Resv message.
Otherwise, the node MUST send a PathErr message with the Error Code Otherwise, the node MUST send a PathErr message with the Error Code
"OAM Problem" [RFC7260] and the new Error Value "Exit Loopback "OAM Problem" [RFC7260] and the new Error Value "Exit Loopback
Failure". Failure".
After the loopback mode is cleared successfully, the ingress LSR MAY After the loopback mode is cleared successfully, the ingress LSR MAY
remove the Lock Instruct using the mechanism defined in section 3.1. remove the Lock Instruct using the mechanism defined in section 3.1.
4. IANA Considerations 4. IANA Considerations
IANA is requested to administer the assignment of new values defined IANA is requested to administer the assignment of new values defined
skipping to change at page 7, line 49 skipping to change at page 7, line 29
Extensions for Operations, Administration, and Maintenance Extensions for Operations, Administration, and Maintenance
(OAM) Configuration", RFC 7260, June 2014. (OAM) Configuration", RFC 7260, June 2014.
7.2. Informative References 7.2. Informative References
[I-D.ietf-ccamp-rsvp-te-mpls-tp-oam-ext] [I-D.ietf-ccamp-rsvp-te-mpls-tp-oam-ext]
Bellagamba, E., Mirsky, G., Andersson, L., Skoldstrom, P., Bellagamba, E., Mirsky, G., Andersson, L., Skoldstrom, P.,
Ward, D., and A. Takacs, "Configuration of Pro-Active Ward, D., and A. Takacs, "Configuration of Pro-Active
Operations, Administration, and Maintenance (OAM) Operations, Administration, and Maintenance (OAM)
Functions for MPLS-based Transport Networks using RSVP- Functions for MPLS-based Transport Networks using RSVP-
TE", draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-13 (work in TE", draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-14 (work in
progress), November 2014. progress), December 2014.
[RFC4783] Berger, L., "GMPLS - Communication of Alarm Information", [RFC4783] Berger, L., "GMPLS - Communication of Alarm Information",
RFC 4783, December 2006. RFC 4783, December 2006.
[RFC4872] Lang, J., Rekhter, Y., and D. Papadimitriou, "RSVP-TE [RFC4872] Lang, J., Rekhter, Y., and D. Papadimitriou, "RSVP-TE
Extensions in Support of End-to-End Generalized Multi- Extensions in Support of End-to-End Generalized Multi-
Protocol Label Switching (GMPLS) Recovery", RFC 4872, May Protocol Label Switching (GMPLS) Recovery", RFC 4872, May
2007. 2007.
[RFC4974] Papadimitriou, D. and A. Farrel, "Generalized MPLS (GMPLS) [RFC4974] Papadimitriou, D. and A. Farrel, "Generalized MPLS (GMPLS)
 End of changes. 14 change blocks. 
53 lines changed or deleted 33 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/