draft-ietf-ccamp-gmpls-vcat-lcas-07.txt   draft-ietf-ccamp-gmpls-vcat-lcas-08.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: June 2009 R. Rabbat Expires: January 2010 R. Rabbat
Google Google
H. van Helvoort H. van Helvoort
Huawei Huawei
December 18, 2008 July 29, 2009
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-07.txt draft-ietf-ccamp-gmpls-vcat-lcas-08.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 39 skipping to change at page 1, line 39
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 June 18, 2009. This Internet-Draft will expire on January 29, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2008 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of
(http://trustee.ietf.org/license-info) in effect on the date of publication of this document (http://trustee.ietf.org/license-info).
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document.
to this document.
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 30 skipping to change at page 2, line 29
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...............................................4 2. Revision History...............................................4
2.1. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-05 and -06..4 2.1. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-07..........4
2.2. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-04..........4 2.2. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-05 and -06..4
2.3. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-03..........4 2.3. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-04..........4
2.4. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-02..........4 2.4. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-03..........4
2.5. Changes from draft-ieft-ccamp-gmpls-vcat-lcas-01..........4 2.5. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-02..........4
2.6. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-00..........5 2.6. Changes from draft-ieft-ccamp-gmpls-vcat-lcas-01..........4
2.7. 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.....................6
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..........9
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....10
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. Use of the CALL_ATTRIBUTES Object........................12 4.3. Use of the CALL_ATTRIBUTES Object........................12
4.4. VCAT CALL_ATTRIBUTES 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..................................................18
9. Acknowledgments...............................................17 9. Acknowledgments...............................................18
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..................................21 Intellectual Property Statement..................................21
Disclaimer of Validity...........................................21 Disclaimer of Validity...........................................21
Acknowledgment...................................................21 Acknowledgment...................................................21
1. Introduction 1. Introduction
skipping to change at page 4, line 7 skipping to change at page 4, line 7
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-05 and -06 2.1. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-07
None. Needed to refresh the expired draft.
2.2. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-05 and -06
Used the CALL_ATTRIBUTES Object from [MLN-Ext] rather than defining a Used the CALL_ATTRIBUTES Object from [MLN-Ext] rather than defining a
new CALL_DATA object. new CALL_DATA object.
2.2. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-04 2.3. 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.3. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-03 2.4. 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.4. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-02 2.5. 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.5. Changes from draft-ieft-ccamp-gmpls-vcat-lcas-01 2.6. 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 19 skipping to change at page 5, line 25
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.6. Changes from draft-ietf-ccamp-gmpls-vcat-lcas-00 2.7. 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 21, line 40 skipping to change at line 900
All IETF Documents and the information contained therein are provided All IETF Documents and the information contained therein are provided
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. FOR A PARTICULAR PURPOSE.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 18 change blocks. 
27 lines changed or deleted 31 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/