draft-ietf-ccamp-gmpls-vcat-lcas-12.txt   draft-ietf-ccamp-gmpls-vcat-lcas-13.txt 
CCAMP Working Group G. Bernstein (ed.) CCAMP Working Group G. Bernstein (ed.)
Internet Draft Grotto Networking Internet Draft Grotto Networking
Updates: 4606 (if approved) D. Caviglia Updates: 4606 (if approved) D. Caviglia
Category: Standards Track Ericsson Category: Standards Track Ericsson
Expires: November 2011 R. Rabbat Expires: November 2011 R. Rabbat
Google Google
H. van Helvoort H. van Helvoort
Huawei Huawei
May 2, 2011 May 4, 2011
Operating Virtual Concatenation (VCAT) and the Link Capacity Operating Virtual Concatenation (VCAT) and the Link Capacity
Adjustment Scheme (LCAS) with Generalized Multi-Protocol Label Adjustment Scheme (LCAS) with Generalized Multi-Protocol Label
Switching (GMPLS) Switching (GMPLS)
draft-ietf-ccamp-gmpls-vcat-lcas-12.txt draft-ietf-ccamp-gmpls-vcat-lcas-13.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. the 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 39 skipping to change at page 1, line 39
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference 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 September 2, 2011. This Internet-Draft will expire on November 4, 2011.
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
skipping to change at page 2, line 45 skipping to change at page 2, line 45
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
2. VCAT/LCAS Scenarios and Specific Requirements..................4 2. VCAT/LCAS Scenarios and Specific Requirements..................4
2.1. VCAT/LCAS Interface Capabilities..........................4 2.1. VCAT/LCAS Interface Capabilities..........................4
2.2. Member Signal Configuration Scenarios.....................4 2.2. Member Signal Configuration Scenarios.....................4
2.3. VCAT Operation With or Without LCAS.......................5 2.3. VCAT Operation With or Without LCAS.......................5
2.4. VCGs and VCG Members......................................6 2.4. VCGs and VCG Members......................................6
3. VCAT Data and Control Plane Concepts...........................6 3. VCAT Data and Control Plane Concepts...........................6
4. VCGs Composed of a Single Member Set (One LSP).................7 4. VCGs Composed of a Single Member Set (One LSP).................7
4.1. One-shot VCG Setup........................................7 4.1. One-shot VCG Setup........................................8
4.2. Incremental VCG Setup.....................................8 4.2. Incremental VCG Setup.....................................8
4.3. Procedure for VCG Reduction by Removing a Member..........9 4.3. Procedure for VCG Reduction by Removing a Member..........9
4.4. Removing Multiple VCG Members in One Shot.................9 4.4. Removing Multiple VCG Members in One Shot.................9
4.5. Teardown of Whole VCG.....................................9 4.5. Teardown of Whole VCG.....................................9
5. VCGs Composed of Multiple Member Sets (Multiple LSPs)..........9 5. VCGs Composed of Multiple Member Sets (Multiple LSPs).........10
5.1. Signaled VCG Service Layer Information...................11 5.1. Signaled VCG Service Layer Information...................11
5.2. CALL ATTRIBUTES Object VCAT TLV..........................11 5.2. CALL ATTRIBUTES Object VCAT TLV..........................11
5.3. Procedures for Multiple Member Sets......................13 5.3. Procedures for Multiple Member Sets......................13
5.3.1. Setting up a new VCAT call and VCG Simultaneously...14 5.3.1. Setting up a new VCAT call and VCG Simultaneously...14
5.3.2. Setting up a VCAT call + LSPs without a VCG.........14 5.3.2. Setting up a VCAT call + LSPs without a VCG.........14
5.3.3. Associating an existing VCAT call with a new VCG....14 5.3.3. Associating an existing VCAT call with a new VCG....14
5.3.4. Removing the association between a call and VCG.....14 5.3.4. Removing the association between a call and VCG.....15
5.3.5. VCG Bandwidth modification..........................15 5.3.5. VCG Bandwidth modification..........................15
6. Error Conditions and Codes....................................16 6. Error Conditions and Codes....................................16
7. IANA Considerations...........................................16 7. IANA Considerations...........................................16
7.1. RSVP CALL_ATTRIBUTE TLV..................................16 7.1. RSVP CALL_ATTRIBUTE TLV..................................16
7.2. RSVP Error Codes and Error Values........................17 7.2. RSVP Error Codes and Error Values........................17
8. Security Considerations.......................................17 8. Security Considerations.......................................18
9. Contributors..................................................18 9. Contributors..................................................19
10. Acknowledgments..............................................18 10. Acknowledgments..............................................19
11. References...................................................19 11. References...................................................20
11.1. Normative References....................................19 11.1. Normative References....................................20
11.2. Informative References..................................19 11.2. Informative References..................................20
Authors' Addresses...............................................20 Authors' Addresses...............................................21
Intellectual Property Statement..................................21 Intellectual Property Statement..................................22
Disclaimer of Validity...........................................21 Disclaimer of Validity...........................................22
Acknowledgment.........................Error! Bookmark not defined. Acknowledgment.........................Error! Bookmark not defined.
1. Introduction 1. Introduction
The Generalized Multi-Protocol Label Switching (GMPLS) suite of The Generalized Multi-Protocol Label Switching (GMPLS) suite of
protocols allows for the automated control of different switching protocols allows for the automated control of different switching
technologies including Synchronous Optical Network (SONET)[ANSI- technologies including Synchronous Optical Network (SONET)[ANSI-
T1.105], Synchronous Digital Hierarchy (SDH)[ITU-T-G.707], Optical T1.105], Synchronous Digital Hierarchy (SDH)[ITU-T-G.707], Optical
Transport Network (OTN)[ITU-T-G.709] and Plesiochronous Digital Transport Network (OTN)[ITU-T-G.709] and Plesiochronous Digital
Hierarchy (PDH)[ITU-T-G.704]. This document updates the procedures Hierarchy (PDH)[ITU-T-G.704]. This document updates the procedures
skipping to change at page 4, line 37 skipping to change at page 4, line 37
2.2. Member Signal Configuration Scenarios 2.2. Member Signal Configuration Scenarios
We list in this section the different scenarios. Here we use the We list in this section the different scenarios. Here we use the
[ITU-T-G.707] term "VCG" to refer to the VCAT group and the [ITU-T-G.707] term "VCG" to refer to the VCAT group and the
terminology "set" and "subset" to refer to the subdivision of the terminology "set" and "subset" to refer to the subdivision of the
group and the individual VCAT group member signals. As noted above, group and the individual VCAT group member signals. As noted above,
the scope of these scenarios is limited to scenarios where all the scope of these scenarios is limited to scenarios where all
member signals are controlled using mechanisms defined in this member signals are controlled using mechanisms defined in this
document. document.
The scenarios listed here are dependent on the terms "co-routed" and
"diversely routed". In the context of this document, "co-routed"
refers to a set of VCAT signals that all traverse the same sequence
of switching nodes. Furthermore, a co-routed set of signals between
any pair of adjacent nodes utilize a set of links that have similar
delay characteristics. Thus, "diversely routed" means a set of
signals that are not classed as "co-routed".
Fixed, co-routed: A fixed bandwidth VCG, transported over a co- Fixed, co-routed: A fixed bandwidth VCG, transported over a co-
routed set of member signals. This is the case where the routed set of member signals. This is the case where the
intended bandwidth of the VCG does not change and all member intended bandwidth of the VCG does not change and all member
signals follow the same route to minimize differential delay. signals follow the same route to minimize differential delay.
The application here is the capability to allocate an amount of The application here is the capability to allocate an amount of
bandwidth close to that required at the client layer. bandwidth close to that required at the client layer.
Fixed, diversely routed: A fixed bandwidth VCG, transported over at Fixed, diversely routed: A fixed bandwidth VCG, transported over at
least two diversely routed subsets of member signals. In this least two diversely routed subsets of member signals. In this
case, the subsets are link-disjoint over at least one link of the case, the subsets are link-disjoint over at least one link of the
skipping to change at page 10, line 45 skipping to change at page 11, line 10
support by moving call(s) and their associated LSPs from one VCG to support by moving call(s) and their associated LSPs from one VCG to
another. Figure 1 below illustrates these relationships, however, another. Figure 1 below illustrates these relationships, however,
note, VCAT calls can exist independently of a VCG (for connection note, VCAT calls can exist independently of a VCG (for connection
pre-establishment) as will be described later in this document. pre-establishment) as will be described later in this document.
+-------+ +-------------+ +-------+ +------------+ +-------+ +-------------+ +-------+ +------------+
| |1 n| |1 n| |1 n| Data Plane | | |1 n| |1 n| |1 n| Data Plane |
| VCG |<>----| VCAT Call |<>----| LSP |<>----| Connection | | VCG |<>----| VCAT Call |<>----| LSP |<>----| Connection |
| | | | | | |(co-routed) | | | | | | | |(co-routed) |
+-------+ +-------------+ +-------+ +------------+ +-------+ +-------------+ +-------+ +------------+
Figure 1 . Conceptual containment relationship between VCG, VCAT . Conceptual containment relationship between VCG, VCAT
calls, control plane LSPs, and data plane connections. calls, control plane LSPs, and data plane connections.
5.1. Signaled VCG Service Layer Information 5.1. Signaled VCG Service Layer Information
In this section, we provide a list of information that will be In this section, we provide a list of information that will be
communicated at the VCG level, i.e., between the VCG signaling communicated at the VCG level, i.e., between the VCG signaling
endpoints using the call procedures of [RFC4974]. To accommodate endpoints using the call procedures of [RFC4974]. To accommodate
the VCG information, a new TLV is defined in this document for the the VCG information, a new TLV is defined in this document for the
CALL ATTRIBUTES Object [RFC6001] for use in the Notify message CALL ATTRIBUTES Object [RFC6001] for use in the Notify message
[RFC4974]. The Notify message is a targeted message and does not [RFC4974]. The Notify message is a targeted message and does not
skipping to change at page 17, line 31 skipping to change at page 17, line 37
Meaning Value Meaning Value
------------------------------------ -------- ------------------------------------ --------
VCG signal type not Supported 1 VCG signal type not Supported 1
LCAS option not supported 2 LCAS option not supported 2
Max number of VCGs exceeded 3 Max number of VCGs exceeded 3
Max number of VCG members exceeded 4 Max number of VCG members exceeded 4
LSP Type incompatible with VCAT call 5 LSP Type incompatible with VCAT call 5
Unknown LCR (LCAS required) value 6 Unknown LCR (LCAS required) value 6
Unknown or unsupported ACTION 7 Unknown or unsupported ACTION 7
7.3. VCAT Elementary Signal Registry
IANA is requested to create a registry to track elementary signal
types as defined in Section 5.2. New allocations are by "IETF
Review" [RFC5226].
IANA is requested to track:
- Value
- Type (Elementary Signal)
- RFC
The available range is 0 - 65535
The registry should be initially populated with the values shown in
Section 5.2 of this document. Value 0 should be marked as Reserved.
Other values should be marked Unassigned.
7.4. VCAT VCG Operation Actions
IANA is requested to create a registry to track VCAT VCG operation
actions as defined in Section 5.2. New allocations are by "IETF
Review" [RFC5226].
IANA is requested to track:
- Value
- Meaning
- RFC
The available range is 0 - 255
The registry should be initially populated with the values shown in
Section 5.2 of this document. Other values should be marked
Unassigned.
8. Security Considerations 8. Security Considerations
This document introduces a specific use of the Notify message and This document introduces a specific use of the Notify message and
admin status object for GMPLS signaling as originally specified in admin status object for GMPLS signaling as originally specified in
[RFC4974]. It does not introduce any new signaling messages, nor [RFC4974]. It does not introduce any new signaling messages, nor
change the relationship between LSRs that are adjacent in the change the relationship between LSRs that are adjacent in the
control plane. The call information associated with diversely control plane. The call information associated with diversely
routed control plane LSPs, in the event of an interception, may routed control plane LSPs, in the event of an interception, may
indicate that these are members of the same VCAT group that take a indicate that these are members of the same VCAT group that take a
different route, and may indicate to an interceptor that the VCG different route, and may indicate to an interceptor that the VCG
skipping to change at page 20, line 21 skipping to change at page 21, line 21
Interface for the Synchronous Digital Hierarchy Interface for the Synchronous Digital Hierarchy
(SDH)", ITU-T Recommendation G.707, December 2003. (SDH)", ITU-T Recommendation G.707, December 2003.
[ITU-T-G.709] International Telecommunications Union, "Interfaces [ITU-T-G.709] International Telecommunications Union, "Interfaces
for the Optical Transport Network (OTN)", ITU-T for the Optical Transport Network (OTN)", ITU-T
Recommendation G.709, March 2003. Recommendation G.709, March 2003.
[RFC5920] L. Fang, Ed., "Security Framework for MPLS and GMPLS [RFC5920] L. Fang, Ed., "Security Framework for MPLS and GMPLS
Networks", July 2010. Networks", July 2010.
[RFC5226] T. Narten, H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", May 2008.
Authors' Addresses Authors' Addresses
Greg M. Bernstein (ed.) Greg M. Bernstein (ed.)
Grotto Networking Grotto Networking
Fremont California, USA Fremont California, USA
Phone: (510) 573-2237 Phone: (510) 573-2237
Email: gregb@grotto-networking.com Email: gregb@grotto-networking.com
Diego Caviglia Diego Caviglia
 End of changes. 11 change blocks. 
16 lines changed or deleted 62 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/