draft-ietf-ccamp-gmpls-vcat-lcas-05.txt   draft-ietf-ccamp-gmpls-vcat-lcas-06.txt 
CCAMP Working Group G. Bernstein (ed.) CCAMP Working Group G. Bernstein (ed.)
Internet Draft Grotto Networking Internet Draft Grotto Networking
Updates: RFC 3946 D. Caviglia Updates: RFC 3946 D. Caviglia
Category: Standards Track Ericsson Category: Standards Track Ericsson
Expires: December 2008 R. Rabbat Expires: May 2009 R. Rabbat
Google Google
H. van Helvoort H. van Helvoort
Huawei Huawei
July 8, 2008 November 17, 2008
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-05.txt draft-ietf-ccamp-gmpls-vcat-lcas-06.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is any applicable patent or other IPR claims of which he or she is
aware have been or will be disclosed, and any of which he or she aware have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of becomes aware will be disclosed, in accordance with Section 6 of
BCP 79. BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 December 8, 2008. This Internet-Draft will expire on January 17, 2009.
Abstract Abstract
This document describes requirements for, and use of, the Generalized This document describes requirements for, and use of, the Generalized
Multi-Protocol Label Switching (GMPLS) control plane in conjunction Multi-Protocol Label Switching (GMPLS) control plane in conjunction
with the Virtual Concatenation (VCAT) layer 1 inverse multiplexing with the Virtual Concatenation (VCAT) layer 1 inverse multiplexing
mechanism and its companion Link Capacity Adjustment Scheme (LCAS) mechanism and its companion Link Capacity Adjustment Scheme (LCAS)
which can be used for hitless dynamic resizing of the inverse which can be used for hitless dynamic resizing of the inverse
multiplex group. These techniques apply to Optical Transport Network multiplex group. These techniques apply to Optical Transport Network
(OTN), Synchronous Optical Network (SONET), Synchronous Digital (OTN), Synchronous Optical Network (SONET), Synchronous Digital
skipping to change at page 2, line 21 skipping to change at page 2, line 26
Conventions used in this document Conventions used in this document
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].
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
2. Revision History...............................................3 2. Revision History...............................................3
2.1. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-04..........3 2.1. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-05..........3
2.2. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-03..........4 2.2. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-04..........4
2.3. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-02..........4 2.3. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-03..........4
2.4. Changes from draft-ieft-ccamp-gmpls-vcat-lcas-01..........4 2.4. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-02..........4
2.5. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-00..........5 2.5. Changes from draft-ieft-ccamp-gmpls-vcat-lcas-01..........4
2.6. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-00..........5
3. VCAT/LCAS Scenarios and Specific Requirements..................5 3. VCAT/LCAS Scenarios and Specific Requirements..................5
3.1. VCAT/LCAS Interface Capabilities..........................5 3.1. VCAT/LCAS Interface Capabilities..........................5
3.2. Member Signal Configuration Scenarios.....................5 3.2. Member Signal Configuration Scenarios.....................5
3.3. VCAT Operation With or Without LCAS.......................6 3.3. VCAT Operation With or Without LCAS.......................6
3.4. VCGs and VCG Members......................................7 3.4. VCGs and VCG Members......................................7
4. GMPLS Mechanisms in Support of VCGs............................7 4. GMPLS Mechanisms in Support of VCGs............................7
4.1. VCGs Composed of a Single Co-Signaled Member Set..........8 4.1. VCGs Composed of a Single Co-Signaled Member Set..........8
4.1.1. One-shot VCG Setup with Co-Signaled Members..........8 4.1.1. One-shot VCG Setup with Co-Signaled Members..........8
4.1.2. Incremental VCG Setup with Co-Signaled Members.......9 4.1.2. Incremental VCG Setup with Co-Signaled Members.......9
4.1.3. Procedure for VCG Reduction by Removing a Member.....9 4.1.3. Procedure for VCG Reduction by Removing a Member.....9
4.1.4. Removing Multiple VCG Members in One Shot...........10 4.1.4. Removing Multiple VCG Members in One Shot...........10
4.1.5. Teardown of Whole VCG...............................10 4.1.5. Teardown of Whole VCG...............................10
4.2. VCGs Composed of Multiple Co-Signaled Member Sets........10 4.2. VCGs Composed of Multiple Co-Signaled Member Sets........10
4.2.1. Signaled VCG Layer Information......................11 4.2.1. Signaled VCG Layer Information......................11
4.3. Call Data Object.........................................11 4.3. Use of the CALL_ATTRIBUTES Object........................11
4.4. VCAT TLV Object..........................................12 4.4. VCAT CALL_ATTRIBUTES TLV Object..........................12
4.5. Procedures for Multiple Co-signaled Member Sets..........13 4.5. Procedures for Multiple Co-signaled Member Sets..........13
4.5.1. Setting up a VCAT call and VCG......................15 4.5.1. Setting up a VCAT call and VCG......................15
4.5.2. Setting up a VCAT call + LSPs with no VCG...........15 4.5.2. Setting up a VCAT call + LSPs with no VCG...........15
4.5.3. Associating an existing VCAT call with a VCG........15 4.5.3. Associating an existing VCAT call with a VCG........15
4.5.4. Removing the association between a call and VCG.....16 4.5.4. Removing the association between a call and VCG.....16
5. Error Conditions and Codes....................................16 5. Error Conditions and Codes....................................16
6. IANA Considerations...........................................16 6. IANA Considerations...........................................16
7. Security Considerations.......................................17 7. Security Considerations.......................................17
8. Contributors..................................................17 8. Contributors..................................................17
9. Acknowledgments...............................................17 9. Acknowledgments...............................................17
10. References...................................................19 10. References...................................................19
10.1. Normative References....................................19 10.1. Normative References....................................19
10.2. Informative References..................................19 10.2. Informative References..................................19
Author's Addresses...............................................20 Author's Addresses...............................................20
Intellectual Property Statement..................................20 Intellectual Property Statement..................................21
Disclaimer of Validity...........................................21 Disclaimer of Validity...........................................21
Copyright Statement..............................................21 Copyright Statement..............................................21
Acknowledgment...................................................21 Acknowledgment...................................................21
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), technologies including Synchronous Optical Network (SONET),
Synchronous Digital Hierarchy (SDH), Optical Transport Network (OTN) Synchronous Digital Hierarchy (SDH), Optical Transport Network (OTN)
skipping to change at page 3, line 42 skipping to change at page 3, line 47
selection of an optimal signal bandwidth (size), extraction of selection of an optimal signal bandwidth (size), extraction of
bandwidth from a mesh network, and, when combined with LCAS, hitless bandwidth from a mesh network, and, when combined with LCAS, hitless
dynamic resizing of bandwidth and fast graceful degradation in the dynamic resizing of bandwidth and fast graceful degradation in the
presence of network faults. To take full advantage of VCAT/LCAS presence of network faults. To take full advantage of VCAT/LCAS
functionality extensions to GMPLS signaling are given that enable the functionality extensions to GMPLS signaling are given that enable the
setup of diversely routed circuits that are members of the same VCAT setup of diversely routed circuits that are members of the same VCAT
group. group.
2. Revision History 2. Revision History
2.1. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-04 2.1. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-05
Used the CALL_ATTRIBUTES Object from [MLN-Ext] rather than defining a
new CALL_DATA object.
2.2. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-04
Fixed text in section 4.1.3 on VCG Reduction to more accurately Fixed text in section 4.1.3 on VCG Reduction to more accurately
describe LCAS and non-LCAS cases. describe LCAS and non-LCAS cases.
2.2. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-03 2.3. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-03
Added requirements on pre-existing members. Added requirements on pre-existing members.
Slightly modified solution for member sharing to constrain calls to a Slightly modified solution for member sharing to constrain calls to a
maximum of one VCG. maximum of one VCG.
Introduced the CALL_DATA object. Introduced the CALL_DATA object.
Detailed coding of new TLV for VCAT to be included in the CALL_DATA Detailed coding of new TLV for VCAT to be included in the CALL_DATA
object. object.
Modified and expanded procedures to deal with new requirements and Modified and expanded procedures to deal with new requirements and
modified solution methodology. modified solution methodology.
Added a list of error conditions. Added a list of error conditions.
2.3. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-02 2.4. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-02
Grammar and punctuation fixes. Updated references with newly Grammar and punctuation fixes. Updated references with newly
published RFCs. published RFCs.
2.4. Changes from draft-ieft-ccamp-gmpls-vcat-lcas-01 2.5. Changes from draft-ieft-ccamp-gmpls-vcat-lcas-01
Changed section 3.1 from "Multiple VCAT Groups per GMPLS endpoint" to Changed section 3.1 from "Multiple VCAT Groups per GMPLS endpoint" to
"VCAT/LCAS Interface Capability" to improve clarity. "VCAT/LCAS Interface Capability" to improve clarity.
Changed terminology from "component" signal to "member" signal where Changed terminology from "component" signal to "member" signal where
possible (not quoted text) to avoid confusion with link bundle possible (not quoted text) to avoid confusion with link bundle
components. components.
Added "Dynamic, member sharing" scenario. Added "Dynamic, member sharing" scenario.
skipping to change at page 5, line 5 skipping to change at page 5, line 13
endpoints to support required scenarios. endpoints to support required scenarios.
Added text to describe: co-signaled, co-routed, data plane LSP, Added text to describe: co-signaled, co-routed, data plane LSP,
control plane LSP and their relationship to the VCAT/LCAS control plane LSP and their relationship to the VCAT/LCAS
application. application.
Change implementation mechanism from one based on the Association Change implementation mechanism from one based on the Association
object to one based on "Call concepts" utilizing the Notify object to one based on "Call concepts" utilizing the Notify
message. message.
2.5. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-00 2.6. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-00
Updated reference from RFC3946bis to issued RFC4606 Updated reference from RFC3946bis to issued RFC4606
Updated section 3.2 based on discussions on the mailing list Updated section 3.2 based on discussions on the mailing list
3. VCAT/LCAS Scenarios and Specific Requirements 3. VCAT/LCAS Scenarios and Specific Requirements
There are a number of specific requirements for the support of There are a number of specific requirements for the support of
VCAT/LCAS in GMPLS that can be derived from the carriers' VCAT/LCAS in GMPLS that can be derived from the carriers'
application-specific demands for the use of VCAT/LCAS and from the application-specific demands for the use of VCAT/LCAS and from the
skipping to change at page 11, line 39 skipping to change at page 11, line 41
b. LCAS desired b. LCAS desired
c. LCAS not desired (but acceptable) c. LCAS not desired (but acceptable)
4. VCG Identifier - Used to identify a particular VCG separately 4. VCG Identifier - Used to identify a particular VCG separately
from the call ID so that call members can be reused with from the call ID so that call members can be reused with
different VCGs per the requirements for member sharing and the different VCGs per the requirements for member sharing and the
requirements of section 3.4. requirements of section 3.4.
4.3. Call Data Object 4.3. Use of the CALL_ATTRIBUTES Object
In RFC4974 the general mechanism for communicating call information In RFC4974 the general mechanism for communicating call information
via Notify messages is given. In general different types of calls via Notify messages is given. In [MLN-Ext] the CALL_ATTRIBUTES object
will need to convey call related information during call is introduce for the conveyance of call related information during
establishment and updates. We define a general CALL_DATA object for call establishment and updates. We define a new
inclusion in call related notify messages and define a specific class
type (C-Type) for VCAT calls.
4.4. VCAT TLV Object 4.4. VCAT CALL_ATTRIBUTES TLV Object
For use in the CALL_DATA object (of VCAT-Call C-Type) in Notify For use in the CALL_ATTRIBUTES object in Notify messages we define
messages we define the following VCAT TLV: the following VCAT related 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 = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signal Type | Number of Members | | Signal Type | Number of Members |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LCAS Req | Action | VCG ID | | LCAS Req | Action | VCG ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where Type is TBD, and the Length = 12 bytes.
Signal Type can take the following values and MUST never change over Signal Type can take the following values and MUST never change over
the lifetime of a VCG: the lifetime of a VCG:
Value Type (Elementary Signal) Value Type (Elementary Signal)
----- ------------------------ ----- ------------------------
1 VT1.5 SPE / VC-11 1 VT1.5 SPE / VC-11
2 VT2 SPE / VC-12 2 VT2 SPE / VC-12
3 STS-1 SPE / VC-3 3 STS-1 SPE / VC-3
4 STS-3c SPE / VC-4 4 STS-3c SPE / VC-4
11 OPU1 (i.e., 2.5 Gbit/s 11 OPU1 (i.e., 2.5 Gbit/s
skipping to change at page 16, line 39 skipping to change at page 16, line 39
Error Subcode Error Subcode
------------------------------------ -------- ------------------------------------ --------
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
6. IANA Considerations 6. IANA Considerations
This document requests from IANA the assignment of a new RSVP-TE This document requests from IANA the assignment of a new TLV for the
Object for CALL_DATA and a C-Type within that class for a VCAT call. CALL_ATTRIBUTES Object from [MLN-Ext]. Within this VCAT TLV are a set
Within this VCAT C-Type are a set of code points for permissible of code points for permissible signal types. In addition, we request
signal types. In addition, we request a new RSVP error code for use a new RSVP error code for use with VCAT call and define a number of
with VCAT call and define a number of corresponding error sub-codes. corresponding error sub-codes.
7. Security Considerations 7. 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 control change the relationship between LSRs that are adjacent in the control
plane. The call information associated with diversely routed control plane. The call information associated with diversely routed control
plane LSPs, in the event of an interception may indicate that there plane LSPs, in the event of an interception may indicate that there
are members of the same VCAT group that take a different route and are members of the same VCAT group that take a different route and
skipping to change at page 19, line 9 skipping to change at page 19, line 9
The authors would like to thank Adrian Farrel, Maarten Vissers, The authors would like to thank Adrian Farrel, Maarten Vissers,
Trevor Wilson, Evelyne Roch, Vijay Pandian, Fred Gruman, Dan Li, Trevor Wilson, Evelyne Roch, Vijay Pandian, Fred Gruman, Dan Li,
Stephen Shew, Jonathan Saddler and Dieter Beller for extensive Stephen Shew, Jonathan Saddler and Dieter Beller for extensive
reviews and contributions to this draft. reviews and contributions to this draft.
10. References 10. References
10.1. Normative References 10.1. Normative References
[MLN-Ext] Papadimitriou, D., Vigoureux M., Shiomoto, K.
Brungard, D., Le Roux, JL., "Generalized Multi-
Protocol Label Switching (GMPLS) Protocol Extensions
for Multi-Layer and Multi-Region Networks (MLN/MRN)",
work in progress: draft-ietf-ccamp-gmpls-mln-
extensions-03.txt, October, 2008.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3473] Berger, L., "Generalized Multi-Protocol Label [RFC3473] Berger, L., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Resource ReserVation Switching (GMPLS) Signaling Resource ReserVation
Protocol-Traffic Engineering (RSVP-TE) Extensions", Protocol-Traffic Engineering (RSVP-TE) Extensions",
RFC 3473, January 2003. RFC 3473, January 2003.
[RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol [RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol
Label Switching (GMPLS) Signaling Extensions for G.709 Label Switching (GMPLS) Signaling Extensions for G.709
skipping to change at page 20, line 11 skipping to change at page 20, line 20
[ITU-T-G.707] International Telecommunications Union, "Network Node [ITU-T-G.707] International Telecommunications Union, "Network Node
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.
Author's Addresses Author's Addresses
Greg Bernstein Greg M. Bernstein (ed.)
Grotto Networking Grotto Networking
Fremont California, USA
Phone: +1-510-573-2237 Phone: (510) 573-2237
Email: gregb@grotto-networking.com Email: gregb@grotto-networking.com
Diego Caviglia Diego Caviglia
Ericsson Ericsson
Via A. Negrone 1/A 16153 Via A. Negrone 1/A 16153
Genoa Italy Genoa Italy
Phone: +39 010 600 3736 Phone: +39 010 600 3736
Email: diego.caviglia@(marconi.com, ericsson.com) Email: diego.caviglia@(marconi.com, ericsson.com)
 End of changes. 23 change blocks. 
33 lines changed or deleted 49 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/