draft-ietf-ccamp-gmpls-vcat-lcas-11.txt   draft-ietf-ccamp-gmpls-vcat-lcas-12.txt 
CCAMP Working Group G. Bernstein (ed.) CCAMP Working Group G. Bernstein (ed.)
Internet Draft Grotto Networking Internet Draft Grotto Networking
Updates: 4606 D. Caviglia Updates: 4606 (if approved) D. Caviglia
Category: Standards Track Ericsson Category: Standards Track Ericsson
Expires: September 2011 R. Rabbat Expires: November 2011 R. Rabbat
Google Google
H. van Helvoort H. van Helvoort
Huawei Huawei
March 9, 2011 May 2, 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-11.txt draft-ietf-ccamp-gmpls-vcat-lcas-12.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
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.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six
and may be updated, replaced, or obsoleted by other documents at any months and may be updated, replaced, or obsoleted by other documents
time. It is inappropriate to use Internet-Drafts as reference at any time. It is inappropriate to use Internet-Drafts as
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 9, 2011. This Internet-Draft will expire on September 2, 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with
to this document. Code Components extracted from this document must respect to this document. Code Components extracted from this
include Simplified BSD License text as described in Section 4.e of document must include Simplified BSD License text as described in
the Trust Legal Provisions and are provided without warranty as Section 4.e of the Trust Legal Provisions and are provided without
described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Abstract Abstract
This document describes requirements for, and use of, the Generalized This document describes requirements for, and use of, the
Multi-Protocol Label Switching (GMPLS) control plane in support of Generalized Multi-Protocol Label Switching (GMPLS) control plane in
the Virtual Concatenation (VCAT) layer 1 inverse multiplexing data support of the Virtual Concatenation (VCAT) layer 1 inverse
plane mechanism and its companion Link Capacity Adjustment Scheme multiplexing data plane mechanism and its companion Link Capacity
(LCAS) which can be used for hitless dynamic resizing of the inverse Adjustment Scheme (LCAS) which can be used for hitless dynamic
multiplex group. These techniques apply to Optical Transport Network resizing of the inverse multiplex group. These techniques apply to
(OTN), Synchronous Optical Network (SONET), Synchronous Digital Optical Transport Network (OTN), Synchronous Optical Network
Hierarchy (SDH), and Plesiochronous Digital Hierarchy (PDH) signals. (SONET), Synchronous Digital Hierarchy (SDH), and Plesiochronous
This document updates the procedures for supporting virtual Digital Hierarchy (PDH) signals. This document updates RFC 4606 by
concatenation in [RFC4606]. making modifications to the procedures for supporting virtual
concatenation.
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. 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........................................7
4.2. Incremental VCG Setup.....................................8 4.2. Incremental VCG Setup.....................................8
4.3. Procedure for VCG Reduction by Removing a Member..........8 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)..........9
5.1. Signaled VCG Service Layer Information...................10 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...13 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.........13 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.....14
5.3.5. VCG Bandwidth modification..........................14 5.3.5. VCG Bandwidth modification..........................15
6. Error Conditions and Codes....................................15 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........................16 7.2. RSVP Error Codes and Error Values........................17
8. Security Considerations.......................................17 8. Security Considerations.......................................17
9. Contributors..................................................18 9. Contributors..................................................18
10. Acknowledgments..............................................18 10. Acknowledgments..............................................18
11. References...................................................19 11. References...................................................19
11.1. Normative References....................................19 11.1. Normative References....................................19
11.2. Informative References..................................19 11.2. Informative References..................................19
Author's Addresses...............................................20 Authors' Addresses...............................................20
Intellectual Property Statement..................................21 Intellectual Property Statement..................................21
Disclaimer of Validity...........................................21 Disclaimer of Validity...........................................21
Acknowledgment...................................................21 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 of Hierarchy (PDH)[ITU-T-G.704]. This document updates the procedures
[RFC4606] to allow supporting additional applications of the Virtual of [RFC4606] to allow supporting additional applications of the
Concatenation (VCAT) layer 1 inverse multiplexing mechanism that has Virtual Concatenation (VCAT) layer 1 inverse multiplexing mechanism
been standardized for SONET, SDH, OTN and PDH [ITU-T-G.707, ITU-T- that has been standardized for SONET, SDH, OTN and PDH [ITU-T-G.707,
G.709, and ITU-T-G.7043] technologies along with its companion Link ITU-T-G.709, and ITU-T-G.7043] technologies along with its companion
Capacity Adjustment Scheme (LCAS) [ITU-T-G.7042]. Link Capacity Adjustment Scheme (LCAS) [ITU-T-G.7042].
VCAT is a TDM oriented byte striping inverse multiplexing method that VCAT is a time division multiplexing (TDM) oriented byte striping
works with a wide range of existing and emerging TDM framed signals, inverse multiplexing method that works with a wide range of existing
including very high bit rate OTN and SDH/SONET signals. VCAT enables and emerging TDM framed signals, including very high bit rate OTN
the selection of an optimal signal server bandwidth (size) utilizing and SDH/SONET signals. VCAT enables the selection of an optimal
a group of server signals and provides for efficient use of bandwidth signal server bandwidth (size) utilizing a group of server signals
in a mesh network. When combined with LCAS, hitless dynamic resizing and provides for efficient use of bandwidth in a mesh network. When
of bandwidth and fast graceful degradation in the presence of network combined with LCAS, hitless dynamic resizing of bandwidth and fast
faults can be supported. To take full advantage of VCAT/LCAS graceful degradation in the presence of network faults can be
functionality, additional extensions to GMPLS signaling are needed supported. To take full advantage of VCAT/LCAS functionality,
that enable the setup of diversely routed signals that are members of additional extensions to GMPLS signaling are needed that enable the
the same VCAT group. Note that the scope of this document is limited setup of diversely routed signals that are members of the same VCAT
to scenarios where all member signals of a VCAT group are controlled group. Note that the scope of this document is limited to scenarios
using mechanisms defined in this document and related RFCs. Scenarios where all member signals of a VCAT group are controlled using
where a subset of member signals are controlled by a management plane mechanisms defined in this document and related RFCs. Scenarios
or a proprietary control plane are outside the scope of this where a subset of member signals are controlled by a management
plane or a proprietary control plane are outside the scope of this
document. document.
2. VCAT/LCAS Scenarios and Specific Requirements 2. 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'
applications for the use of VCAT/LCAS. These are set out in the applications for the use of VCAT/LCAS. These are set out in the
following section. following section.
2.1. VCAT/LCAS Interface Capabilities 2.1. VCAT/LCAS Interface Capabilities
In general, an LSR can be ingress/egress of one or more VCAT groups. In general, an label switched router (LSR) can be ingress/egress of
VCAT and LCAS are data plane interface capabilities. An LSR may one or more VCAT groups. VCAT and LCAS are data plane interface
have, for example, VCAT-capable interfaces that are not LCAS-capable. capabilities. An LSR may have, for example, VCAT-capable interfaces
It may at the same time have interfaces that are neither VCAT nor that are not LCAS-capable. It may at the same time have interfaces
LCAS-capable. that are neither VCAT nor LCAS-capable.
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 member the scope of these scenarios is limited to scenarios where all
signals are controlled using mechanisms defined in this document. member signals are controlled using mechanisms defined in this
document.
Fixed, co-routed: A fixed bandwidth VCG, transported over a co-routed Fixed, co-routed: A fixed bandwidth VCG, transported over a co-
set of member signals. This is the case where the intended routed set of member signals. This is the case where the
bandwidth of the VCG does not change and all member signals follow intended bandwidth of the VCG does not change and all member
the same route to minimize differential delay. The application signals follow the same route to minimize differential delay.
here is the capability to allocate an amount of bandwidth close to The application here is the capability to allocate an amount of
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
route. The application here is more efficient use of network route. The application here is more efficient use of network
resources, e.g., no unique route has the required bandwidth. resources, e.g., no unique route has the required bandwidth.
Fixed, member sharing: A fixed bandwidth VCG, transported over a set Fixed, member sharing: A fixed bandwidth VCG, transported over a set
of member signals that are allocated from a common pool of of member signals that are allocated from a common pool of
available member signals without requiring member connection available member signals without requiring member connection
teardown and setup. This document only covers the case where this teardown and setup. This document only covers the case where this
pool of "potential" member signals has been established via pool of "potential" member signals has been established via
mechanisms defined in this document. Note that by the nature of mechanisms defined in this document. Member signals need not be
VCAT, a member signal can only belong to one VCG at a time. To be co-routed or be guaranteed to be diversely routed. Note that by
used in a different VCG, a signal must first be removed from any the nature of VCAT, a member signal can only belong to one VCG at
VCG to which it may belong. a time. To be used in a different VCG, a signal must first be
removed from any VCG to which it may belong.
Dynamic, co-routed: A dynamic VCG (bandwidth can be increased or Dynamic, co-routed: A dynamic VCG (bandwidth can be increased or
decreased via the addition or removal of member signals), decreased via the addition or removal of member signals),
transported over a co-routed set of members. The application here transported over a co-routed set of members. The application
is dynamic resizing and resilience of bandwidth. here is dynamic resizing and resilience of bandwidth.
Dynamic, diversely routed: A dynamic VCG (bandwidth can be increased Dynamic, diversely routed: A dynamic VCG (bandwidth can be increased
or decreased via the addition or removal of member signals), or decreased via the addition or removal of member signals),
transported over at least two diversely routed subsets of member transported over at least two diversely routed subsets of member
signals. The application here is efficient use of network signals. The application here is efficient use of network
resources, dynamic resizing and resilience of bandwidth. resources, dynamic resizing and resilience of bandwidth.
Dynamic, member sharing: A dynamic bandwidth VCG, transported over a Dynamic, member sharing: A dynamic bandwidth VCG, transported over a
set of member signals that are allocated from a common pool of set of member signals that are allocated from a common pool of
available member signals without requiring member connection available member signals without requiring member connection
teardown and setup. teardown and setup.
2.3. VCAT Operation With or Without LCAS 2.3. VCAT Operation With or Without LCAS
VCAT capabilities may be present with or without the presence of VCAT capabilities may be present with or without the presence of
LCAS. The use of LCAS is beneficial in the provisioning of flexible LCAS. The use of LCAS is beneficial in the provisioning of flexible
bandwidth services, but in the absence of LCAS, VCAT is still a valid bandwidth services, but in the absence of LCAS, VCAT is still a
technique. Therefore GMPLS mechanisms for the operation of VCAT are valid technique. Therefore GMPLS mechanisms for the operation of
REQUIRED for both the case where LCAS is available and the case where VCAT are REQUIRED for both the case where LCAS is available and the
it is not available. The GMPLS procedures for the two cases SHOULD case where it is not available. The GMPLS procedures for the two
be identical. cases SHOULD be identical.
. GMPLS signaling for LCAS-capable interfaces MUST support all . GMPLS signaling for LCAS-capable interfaces MUST support all
scenarios of section 2.2. with no loss of traffic. scenarios of section 2.2. with no loss of traffic.
. GMPLS signaling for non-LCAS-capable interfaces MUST support . GMPLS signaling for non-LCAS-capable interfaces MUST support
only the "fixed" scenarios of section 2.2. the "fixed" scenarios of section 2.2.
To provide for these requirements, GMPLS signaling MUST carry the To provide for these requirements, GMPLS signaling MUST carry the
following information on behalf of the VCAT endpoints: following information on behalf of the VCAT endpoints:
. The type of the member signal that the VCG will contain, e.g., . The type of the member signal that the VCG will contain, e.g.,
VC-3, VC-4, etc. VC-3, VC-4, etc.
. The total number of members to be in the VCG. This provides the . The total number of members to be in the VCG. This provides the
endpoints in both the LCAS and non-LCAS case with information on endpoints in both the LCAS and non-LCAS case with information on
which to accept or reject the request, and in the non-LCAS case which to accept or reject the request, and in the non-LCAS case
will let the receiving endpoint know when all members of the VCG will let the receiving endpoint know when all members of the VCG
have been established. have been established.
. Identification of the VCG and its associated members. This . Identification of the VCG and its associated members. This
provides information that allows the endpoints to differentiate provides information that allows the endpoints to differentiate
multiple VCGs and to tell what members (LSPs) to associate with multiple VCGs and to tell what members - label switched paths
a particular VCG. (LSPs)- to associate with a particular VCG.
2.4. VCGs and VCG Members 2.4. VCGs and VCG Members
The signaling solution SHOULD provide a mechanism to support these The signaling solution SHOULD provide a mechanism to support these
scenarios: scenarios:
. VCG members (server layer connections) may be set up prior to . VCG members (server layer connections) may be set up prior to
their use in a VCG. their use in a VCG.
. VCG members (server layer connections) may exist after their . VCG members (server layer connections) may exist after their
corresponding VCG has been removed. corresponding VCG has been removed.
However, it is not required that any arbitrarily created server layer However, it is not required that any arbitrarily created server
connection be supported in the above scenarios, i.e., connections layer connection be supported in the above scenarios, i.e.,
established without following the procedures of this document. connections established without following the procedures of this
document.
3. VCAT Data and Control Plane Concepts 3. VCAT Data and Control Plane Concepts
When utilizing GMPLS with VCAT/LCAS, we use a number of control and When utilizing GMPLS with VCAT/LCAS, we use a number of control and
data plane concepts described below. data plane concepts described below.
VCG -- This is the group of data plane server layer signals used to VCG -- This is the group of data plane server layer signals used to
provide the bandwidth for the virtual concatenation link connection provide the bandwidth for the virtual concatenation link
through a network ([G7042]). connection through a network ([G7042]).
VCG member -- This is an individual data plane server layer signal VCG member -- This is an individual data plane server layer signal
that belongs to a VCG ([G7042]). that belongs to a VCG ([G7042]).
Member set -- One or more VCG members (or potential members) set up Member set -- One or more VCG members (or potential members) set up
via the same control plane signaling exchange. Note that all via the same control plane signaling exchange. Note that all
members in a member set follow the same route. members in a member set follow the same route.
Data plane LSP -- This is an individual VCG member. Data plane LSP -- This is an individual VCG member.
Control plane LSP -- A control plane entity that can control multiple Control plane LSP -- A control plane entity that can control multiple
data plane LSPs. For our purposes here, this is equivalent to the data plane LSPs. For our purposes here, this is equivalent to the
member set. member set.
Call - A control plane mechanism for providing association between Call - A control plane mechanism for providing association between
endpoints and possibly key transit points. endpoints and possibly key transit points.
4. VCGs Composed of a Single Member Set (One LSP) 4. VCGs Composed of a Single Member Set (One LSP)
In this section and the next section, we will describe the procedures In this section and the next section, we will describe the
for supporting the applications described in Section 2. procedures for supporting the applications described in Section 2.
This section describes the support of a single VCG composed of a This section describes the support of a single VCG composed of a
single member set (in support of the fixed, co-routed application and single member set (in support of the fixed, co-routed application
the dynamic, co-routed application) using existing GMPLS procedures and the dynamic, co-routed application) using existing GMPLS
[RFC4606]. Note that this section is included for informational procedures [RFC4606]. Note that this section is included for
purposes only. informational purposes only and does not modify [RFC4606]. It is
provided to show how the existing GMPLS procedures may be used.
[RFC4606] provides the normative definition for GMPLS processing of
VCGs composed of a single member set, and in the event of any
conflict between this section and that document, [RFC4606] takes
precedence.
The existing GMPLS signaling protocols support a VCG composed of a The existing GMPLS signaling protocols support a VCG composed of a
single member set. Setup using the NVC field is explained in section single member set. Setup using the number of virtual components
2.1 of [RFC4606]. In this case, one (single) control plane LSP is (NVC) field is explained in section 2.1 of [RFC4606]. In this case,
used in support of the VCG. one (single) control plane LSP is used in support of the VCG.
There are two options for setting up the VCG, depending on policy There are two options for setting up the VCG, depending on policy
preferences: one-shot setup and incremental setup. preferences: one-shot setup and incremental setup.
The following sections explain the procedure based on an example of The following sections explain the procedure based on an example of
setting up a VC-4-7v SDH VCAT group (corresponding to an STS-3c-7v setting up a VC-4-7v SDH VCAT group (corresponding to an STS-3c-7v
SONET VCAT group) which is composed of 7 virtually concatenated VC-4s SONET VCAT group) which is composed of 7 virtually concatenated VC-
(or STS-3c). 4s (or STS-3c).
4.1. One-shot VCG Setup 4.1. One-shot VCG Setup
This section describes establishment of an LSP that supports all VCG This section describes establishment of an LSP that supports all VCG
members as part of the initial LSP establishment. To establish such members as part of the initial LSP establishment. To establish such
an LSP, an RSVP-TE Path message is sent containing the SONET/SDH an LSP, an RSVP-TE Path message is sent containing the SONET/SDH
Traffic Parameters defined in [RFC4606]. In the case of this example: Traffic Parameters defined in [RFC4606]. In the case of this
example:
. Elementary signal is set to 6 (for VC-4/STS-3c_SPE). . Elementary signal is set to 6 (for VC-4/STS-3c_SPE).
. NVC is set to 7 (number of members). . NVC is set to 7 (number of members).
. Per [RFC4606] a Multiplier Transform greater than 1 (say N>1) . Per [RFC4606] a Multiplier Transform greater than 1 (say N>1)
may be used if the operator wants to set up N identical VCAT may be used if the operator wants to set up N identical VCAT
groups (for the same LSP). groups (for the same LSP).
. SDH or SONET labels have to be assigned for each member of the . SDH or SONET labels have to be assigned for each member of the
VCG and concatenated to form a single Generalized Label VCG and concatenated to form a single Generalized Label
constructed as an ordered list of 32-bit timeslot identifiers of constructed as an ordered list of 32-bit timeslot identifiers
the same format as TDM labels. [RFC4606] requires that the of the same format as TDM labels. [RFC4606] requires that the
order of the labels reflect the order of the payloads to order of the labels reflect the order of the payloads to
concatenate, and not the physical order of time-slots. concatenate, and not the physical order of time-slots.
. Refer to [RFC4606] for other traffic parameter settings. . Refer to [RFC4606] for other traffic parameter settings.
4.2. Incremental VCG Setup 4.2. Incremental VCG Setup
In some cases, it may be necessary or desirable to set up the VCG In some cases, it may be necessary or desirable to set up the VCG
members individually, or to add group members to an existing group. members individually, or to add group members to an existing group.
One example of this need is when the local policy requires that VCAT One example of this need is when the local policy requires that VCAT
can only add VCAT members one at a time or cannot automatically match can only add VCAT members one at a time or cannot automatically
the members at the ingress and egress for the purposes of inverse match the members at the ingress and egress for the purposes of
multiplexing. Serial or incremental setup solves this problem. inverse multiplexing. Serial or incremental setup solves this
problem.
In order to accomplish incremental setup, an iterative process is In order to accomplish incremental setup, an iterative process is
used to add group members. For each iteration, NVC is incremented up used to add group members. For each iteration, NVC is incremented
to the final value required. A successful iteration consists of the up to the final value required. A successful iteration consists of
successful completion of Path and Resv signaling. At first, NVC = 1 the successful completion of Path and Resv signaling. At first, NVC
and the label includes just one timeslot identifier = 1 and the label includes just one timeslot identifier
At each of the next iterations, NVC is set to (NVC +1), one more At each of the next iterations, NVC is set to (NVC +1), one more
timeslot identifier is added to the ordered list in the Generalized timeslot identifier is added to the ordered list in the Generalized
Label (in the Path or Resv message). A node that receives a Path Label (in the Path or Resv message). A node that receives a Path
message that contains changed fields will process the full Path message that contains changed fields will process the full Path
message and, based on the new value of NVC, it will add a component message and, based on the new value of NVC, it will add a component
signal to the VCAT group, and switch the new timeslot based on the signal to the VCAT group, and switch the new timeslot based on the
new label information. new label information.
Following the addition of the new label (identifying the new member) Following the addition of the new label (identifying the new member)
to the LSP, in the data plane, LCAS may be used to add the new member to the LSP, in the data plane, LCAS may be used to add the new
at the end points into the existing VCAT group. LCAS (data plane) member at the end points into the existing VCAT group. LCAS (data
signaling is described in [ITU-T-G.7042]. plane) signaling is described in [ITU-T-G.7042].
4.3. Procedure for VCG Reduction by Removing a Member 4.3. Procedure for VCG Reduction by Removing a Member
The procedure to remove a component signal is similar to that used to The procedure to remove a component signal is similar to that used
add components as described in Section 4. 2. In the data plane, LCAS to add components as described in Section 4. 2. In the data plane,
signaling is used first to take the component out of service from the LCAS signaling is used first to take the component out of service
group. LCAS signaling is described in [ITU-T-G.7042]. from the group. LCAS signaling is described in [ITU-T-G.7042].
In this case, the NVC value is decremented by 1 and the timeslot In this case, the NVC value is decremented by 1 and the timeslot
identifier for the dropped component is removed from the ordered identifier for the dropped component is removed from the ordered
list in the Generalized Label. list in the Generalized Label.
Note that for interfaces that are not LCAS-capable, removing one Note that for interfaces that are not LCAS-capable, removing one
component of the VCG will result in failure detection of the member component of the VCG will result in failure detection of the member
at the end point and failure of the whole group (per ITU-T at the end point and failure of the whole group (per ITU-T
definition). So, this is a feature that only LCAS-capable VCAT definition). So, this is a feature that only LCAS-capable VCAT
interfaces can support without management intervention at the end interfaces can support without management intervention at the end
points. points.
Note if using LCAS, a VCG member can be temporary removed from the Note if using LCAS, a VCG member can be temporarily removed from the
VCG due to a failure of the component signal. The LCAS data plane VCG due to a failure of the component signal. The LCAS data plane
signaling will take appropriate actions to adjust the VCG as signaling will take appropriate actions to adjust the VCG as
described in [ITU-T-G.7042]. described in [ITU-T-G.7042].
4.4. Removing Multiple VCG Members in One Shot 4.4. Removing Multiple VCG Members in One Shot
The procedure is similar to 4.3. In this case, the NVC value is The procedure is similar to 4.3. In this case, the NVC value is
changed to the new value and all relevant timeslot identifiers for changed to the new value and all relevant timeslot identifiers for
the components to be torn down are removed from the ordered list in the components to be torn down are removed from the ordered list in
the Generalized Label. This procedure is also not supported for the Generalized Label. This procedure is also not supported for
skipping to change at page 9, line 44 skipping to change at page 10, line 6
The motivation for VCGs composed of multiple member sets comes from The motivation for VCGs composed of multiple member sets comes from
the requirement to support VCGs with diversely routed members. The the requirement to support VCGs with diversely routed members. The
initial GMPLS specification did not support diversely routed signals initial GMPLS specification did not support diversely routed signals
using the NVC construct. [RFC4606] says: using the NVC construct. [RFC4606] says:
[...] The standard definition for virtual concatenation allows [...] The standard definition for virtual concatenation allows
each virtual concatenation components to travel over diverse each virtual concatenation components to travel over diverse
paths. Within GMPLS, virtual concatenation components must paths. Within GMPLS, virtual concatenation components must
travel over the same (component) link if they are part of the travel over the same (component) link if they are part of the
same LSP. This is due to the way that labels are bound to a same LSP. This is due to the way that labels are bound to a
(component) link. Note however, that the routing of components (component) link. Note however, that the routing of
on different paths is indeed equivalent to establishing components on different paths is indeed equivalent to
different LSPs, each one having its own route. Several LSPs establishing different LSPs, each one having its own route.
can be initiated and terminated between the same nodes and Several LSPs can be initiated and terminated between the same
their corresponding components can then be associated together nodes and their corresponding components can then be
(i.e., virtually concatenated). associated together (i.e., virtually concatenated).
The setup of diversely routed VCG members requires multiple VCG The setup of diversely routed VCG members requires multiple VCG
member sets, i.e., multiple control plane LSPs. member sets, i.e., multiple control plane LSPs.
The support of a VCG with multiple VCG members sets requires being The support of a VCG with multiple VCG members sets requires being
able to identify separate sets of control plane LSPs with a single able to identify separate sets of control plane LSPs with a single
VCG and exchange information pertaining to the VCG as a whole between VCG and exchange information pertaining to the VCG as a whole
the endpoints. This document updates the procedures of [RFC4606] to between the endpoints. This document updates the procedures of
provide this capability by using the call procedures and extensions [RFC4606] to provide this capability by using the call procedures
described in [RFC4974]. The VCG makes use of one or more calls (VCAT and extensions described in [RFC4974]. The VCG makes use of one or
calls) to associate control plane LSPs in support of VCG server layer more calls (VCAT calls) to associate control plane LSPs in support
connections (VCG members) in the data plane. Note, the trigger for of VCG server layer connections (VCG members) in the data plane.
the VCG (by management plane or client layer) is outside the scope of Note, the trigger for the VCG (by management plane or client layer)
this document. These procedures provide for autonomy of the client is outside the scope of this document. These procedures provide for
layer and server layer with respect to their management. autonomy of the client layer and server layer with respect to their
management.
In addition, by supporting the identification of a VCG (VCG ID) and In addition, by supporting the identification of a VCG (VCG ID) and
VCAT call identification (VCAT Call ID), support can be provided for VCAT call identification (VCAT Call ID), support can be provided for
the member sharing scenarios, i.e. by explicitly separating the VCG the member sharing scenarios, i.e. by explicitly separating the VCG
ID from the VCAT call ID. Note that per [RFC4974], LSPs (connections) ID from the VCAT call ID. Note that per [RFC4974], LSPs
cannot be moved from one call to another, hence to support member (connections) cannot be moved from one call to another, hence to
sharing, the procedures in this document provide support by moving support member sharing, the procedures in this document provide
call(s) and their associated LSPs from one VCG to another. Figure 1 support by moving call(s) and their associated LSPs from one VCG to
below illustrates these relationships, however, note, VCAT calls can another. Figure 1 below illustrates these relationships, however,
exist independently of a VCG (for connection pre-establishment) as note, VCAT calls can exist independently of a VCG (for connection
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 Figure 1. Conceptual containment relationship between VCG, Figure 1 . Conceptual containment relationship between VCG, VCAT
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 the endpoints using the call procedures of [RFC4974]. To accommodate
VCG information, a new TLV is defined in this document for the CALL the VCG information, a new TLV is defined in this document for the
ATTRIBUTES Object [RFC6001] for use in the Notify message [RFC4974]. CALL ATTRIBUTES Object [RFC6001] for use in the Notify message
The Notify message is a targeted message and does not need to follow [RFC4974]. The Notify message is a targeted message and does not
the path of LSPs through the network i.e. there is no dependency on need to follow the path of LSPs through the network i.e. there is no
the member signaling for establishing the VCAT call and does not dependency on the member signaling for establishing the VCAT call
preclude the use of external call managers as described in [RFC4974]. and does not preclude the use of external call managers as described
in [RFC4974].
The following information is needed: The following information is needed:
1. Signal Type 1. Signal Type
2. Number of VCG Members 2. Number of VCG Members
3. LCAS requirements: 3. LCAS requirements:
a. LCAS required a. LCAS required
skipping to change at page 11, line 34 skipping to change at page 11, line 49
This document defines a CALL_ATTRIBUTES object VCAT TLV for use in This document defines a CALL_ATTRIBUTES object VCAT TLV for use in
the CALL_ATTRIBUTES object [RFC6001] as follows: the CALL_ATTRIBUTES object [RFC6001] as follows:
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 = TBA | Length = 12 | | Type = TBA | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signal Type | Number of Members | | Signal Type | Number of Members |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LCAS Req | Action | VCG ID | |LCR| Reserved | Action | VCG ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type, as defined in [RFC6001]. This field MUST be set to TBA (by Type, as defined in [RFC6001]. This field MUST be set to TBA (by
IANA). IANA).
Length, as defined in [RFC6001]. This field MUST be set to 12. Length, as defined in [RFC6001]. This field MUST be set to 12.
Signal Type: 16 bits Signal Type: 16 bits
The signal types can never be mixed in a VCG (per ITU-T definition) The signal types can never be mixed in a VCG (per ITU-T
and hence a VCAT call contains only one signal type. This field can definition) and hence a VCAT call contains only one signal type.
take the following values and MUST never change over the lifetime This field can take the following values and MUST never change
of a VCG [ANSI-T1-105, ITU-T-G.707, ITU-T-G.709, ITU-T-G.7043]: over the lifetime of a VCG [ANSI-T1-105, ITU-T-G.707, ITU-T-G.709,
ITU-T-G.7043]:
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 ODU1 (i.e., 2.5 Gbit/s 11 ODU1 (i.e., 2.5 Gbit/s
12 ODU2 (i.e., 10 Gbit/s) 12 ODU2 (i.e., 10 Gbit/s)
13 ODU3 (i.e., 40 Gbit/s) 13 ODU3 (i.e., 40 Gbit/s)
skipping to change at page 12, line 26 skipping to change at page 12, line 39
23 E3 (i.e., 34.368 Mbps) 23 E3 (i.e., 34.368 Mbps)
24 T3 (i.e., 44.736 Mbps) 24 T3 (i.e., 44.736 Mbps)
Number of Members: 16 bits Number of Members: 16 bits
This field is an unsigned integer that MUST indicate the total This field is an unsigned integer that MUST indicate the total
number of members in the VCG (not just the call). This field MUST number of members in the VCG (not just the call). This field MUST
be changed (over the life of the VCG) to indicate the current be changed (over the life of the VCG) to indicate the current
number of members. number of members.
LCAS Required: 8 bits LCR (LCAS Required): 2 bits
This field can take the following values and MUST NOT change over This field can take the following values and MUST NOT change over
the life of a VCG: the life of a VCG:
Value Meaning Value Meaning
----- --------------------------------- ----- ---------------------------------
0 LCAS required 0 LCAS required
1 LCAS desired 1 LCAS desired
2 LCAS not supported 2 LCAS not supported
skipping to change at page 13, line 25 skipping to change at page 13, line 36
particular VCG within a session. The value of the field MUST NOT particular VCG within a session. The value of the field MUST NOT
change over the lifetime of a VCG but MAY change over the lifetime change over the lifetime of a VCG but MAY change over the lifetime
of a call. of a call.
5.3. Procedures for Multiple Member Sets 5.3. Procedures for Multiple Member Sets
The creation of a VCG based on multiple member sets requires the The creation of a VCG based on multiple member sets requires the
establishment of at least one VCAT layer call. VCAT layer calls and establishment of at least one VCAT layer call. VCAT layer calls and
related LSPs (connections) MUST follow the procedures as defined in related LSPs (connections) MUST follow the procedures as defined in
[RFC4974] with the addition of the inclusion of a CALL_ATTRIBUTES [RFC4974] with the addition of the inclusion of a CALL_ATTRIBUTES
object containing the VCAT TLV. Multiple VCAT layer calls per VCG are object containing the VCAT TLV. Multiple VCAT layer calls per VCG
not required to support member sets, but are needed to support are not required to support member sets, but are needed to support
certain member sharing scenario. certain member sharing scenario.
The remainder of this section provides specific procedures related to The remainder of this section provides specific procedures related
VCG signaling. The procedures of [RFC4974] are only modified as to VCG signaling. The procedures of [RFC4974] are only modified as
discussed in this section. discussed in this section.
When LCAS is supported, the data plane will add or decrease the When LCAS is supported, the data plane will add or decrease the
members per [G7042]. When LCAS is not supported across LSPs, the data members per [G7042]. When LCAS is not supported across LSPs, the
plane coordination across member sets, is outside the scope of this data plane coordination across member sets, is outside the scope of
document. this document.
5.3.1. Setting up a new VCAT call and VCG Simultaneously 5.3.1. Setting up a new VCAT call and VCG Simultaneously
To simultaneously set up a VCAT call and identify it with an To simultaneously set up a VCAT call and identify it with an
associated VCG, a CALL_ATTRIBUTES object containing the VCAT TLV associated VCG, a CALL_ATTRIBUTES object containing the VCAT TLV
MUSTbe included in the Notify message at the time of call setup. The MUSTbe included in the Notify message at the time of call setup.
VCAT TLV Action field MUST be set to 1, which indicates that this is The VCAT TLV Action field MUST be set to 1, which indicates that
a new VCG for this call. LSPs MUST then be added to the call until this is a new VCG for this call. LSPs MUST then be added to the
the number of members reaches the number specified in the VCAT TLV. call until the number of members reaches the number specified in the
VCAT TLV.
5.3.2. Setting up a VCAT call + LSPs without a VCG 5.3.2. Setting up a VCAT call + LSPs without a VCG
To provide for pre-establishment of the server layer connections for To provide for pre-establishment of the server layer connections for
a VCG a VCAT call MAY be established without an associated VCG a VCG a VCAT call MAY be established without an associated VCG
identifier. In fact, to provide for the member sharing scenario, a identifier. In fact, to provide for the member sharing scenario, a
pool of VCAT calls with associated connections (LSPs) can be pool of VCAT calls with associated connections (LSPs) can be
established, and then one or more of these calls (with accompanying established, and then one or more of these calls (with accompanying
connections) can be associated with a particular VCG (via the VCG connections) can be associated with a particular VCG (via the VCG
ID). Note that multiple calls can be associated with a single VCG but ID). Note that multiple calls can be associated with a single VCG
that a call MUST NOT contain members used in more than one VCG. but that a call MUST NOT contain members used in more than one VCG.
To establish a VCAT call with no VCG association, a CALL_ATTRIBUTES To establish a VCAT call with no VCG association, a CALL_ATTRIBUTES
object containing the VCAT TLV MUST be included at the time of call object containing the VCAT TLV MUST be included at the time of call
setup in the Notify message. The VCAT TLV Action field MUST be set setup in the Notify message. The VCAT TLV Action field MUST be set
to 0, which indicates that this is a VCAT call without an associated to 0, which indicates that this is a VCAT call without an associated
VCG. LSPs can then be added to the call. The number of members VCG. LSPs can then be added to the call. The number of members
parameter in the VCAT TLV has no meaning at this point since it parameter in the VCAT TLV has no meaning at this point since it
reflects the intended number of members in a VCG and not in a call. reflects the intended number of members in a VCG and not in a call.
5.3.3. Associating an existing VCAT call with a new VCG 5.3.3. Associating an existing VCAT call with a new VCG
skipping to change at page 14, line 36 skipping to change at page 14, line 51
field MUST equal the sum of all LSPs associated with the VCG. Note field MUST equal the sum of all LSPs associated with the VCG. Note
that the total number of VCGs supported by a node may be limited and that the total number of VCGs supported by a node may be limited and
hence on reception of any message with a change of VCG ID this limit hence on reception of any message with a change of VCG ID this limit
should be checked. Likewise the sender of a message with a change in should be checked. Likewise the sender of a message with a change in
VCG ID MUST be prepared to receive an error response. Again, any VCG ID MUST be prepared to receive an error response. Again, any
error in a VCG may result in the failure of the complete VCG. error in a VCG may result in the failure of the complete VCG.
5.3.4. Removing the association between a call and VCG 5.3.4. Removing the association between a call and VCG
To reuse the server layer connections in a call in another VCG, the To reuse the server layer connections in a call in another VCG, the
current association between the call and a VCG MUST first be removed. current association between the call and a VCG MUST first be
To do this, a Notify message MUST be sent with a CALL_ATTRIBUTES removed. To do this, a Notify message MUST be sent with a
object containing a VCAT TLV. The Action field of the TLV MUST be CALL_ATTRIBUTES object containing a VCAT TLV. The Action field of
set to 3 (Remove VCG from Call). The VCG ID field is ignored and MAY the TLV MUST be set to 3 (Remove VCG from Call). The VCG ID field is
be set to any value. The number of members field is also ignored and ignored and MAY be set to any value. The number of members field is
MAY be set to any value. When the association between a VCG and all also ignored and MAY be set to any value. When the association
existing calls has been removed then the VCG is considered torn down. between a VCG and all existing calls has been removed then the VCG
is considered torn down.
5.3.5. VCG Bandwidth modification 5.3.5. VCG Bandwidth modification
The following cases may occur when increasing or decreasing the The following cases may occur when increasing or decreasing the
bandwidth of a VCG: bandwidth of a VCG:
1. LSPs are added to or, in the case of a decrease, removed from a 1. LSPs are added to or, in the case of a decrease, removed from a
VCAT Call already associated with a VCG. VCAT Call already associated with a VCG.
2. An existing VCAT call, and corresponding LSPs, is associated 2. An existing VCAT call, and corresponding LSPs, is associated
with a VCG or, in the case of a decrease, has its association with a VCG or, in the case of a decrease, has its association
removed. Note that in the increase case, the call MUST NOT have removed. Note that in the increase case, the call MUST NOT have
any existing association with a VCG. any existing association with a VCG.
The following sequence SHOULD be used when modifying the bandwidth of The following sequence SHOULD be used when modifying the bandwidth
a VCG: of a VCG:
1. In both cases, prior to any other change, a Notify message MUST 1. In both cases, prior to any other change, a Notify message MUST
be sent with a CALL_ATTRIBUTES object containing a VCAT TLV for each be sent with a CALL_ATTRIBUTES object containing a VCAT TLV for each
of the existing VCAT calls associated with the VCG. The Action field of the existing VCAT calls associated with the VCG. The Action field
of the TLV MUST be set to 2. The VCG ID field MUST be set to match of the TLV MUST be set to 2. The VCG ID field MUST be set to match
the VCG. The number of members field MUST equal the sum of all LSPs the VCG. The number of members field MUST equal the sum of all LSPs
that are anticipated to be associated with the VCG after the that are anticipated to be associated with the VCG after the
bandwidth change. The Notify message is otherwise formatted and bandwidth change. The Notify message is otherwise formatted and
processed as defined under Call Establishment in [RFC4974]. If an processed as defined under Call Establishment in [RFC4974]. If an
error is encountered while processing any of the Notify messages, the error is encountered while processing any of the Notify messages, the
number of members is reverted to the pre-change value and the number of members is reverted to the pre-change value and the
increase is aborted. The reverted number of members MUST be signaled increase is aborted. The reverted number of members MUST be signaled
in a Notify message as described above. Failures encountered in in a Notify message as described above. Failures encountered in
processing these Notify messages are handled per [RFC4974]. processing these Notify messages are handled per [RFC4974].
2. Once the existing calls have successfully been notified of the 2. Once the existing calls have successfully been notified of the
new number of members in the VCG, the bandwidth change can be made. new number of members in the VCG, the bandwidth change can be made.
The next step is dependent on the two cases defined above. In the The next step is dependent on the two cases defined above. In the
first case defined above, the bandwidth change is made by adding (in first case defined above, the bandwidth change is made by adding (in
the case of increase) or removing (in the case of a decrease) LSPs to the case of increase) or removing (in the case of a decrease) LSPs
the VCAT call per the procedures defined in [RFC4974]. In the second to the VCAT call per the procedures defined in [RFC4974]. In the
case, the same procedure defined in Section 5.3.3. is followed for an second case, the same procedure defined in Section 5.3.3. is
increase, and the procedure defined in Section 5.3.4. is followed for followed for an increase, and the procedure defined in Section
a decrease. 5.3.4. is followed for a decrease.
6. Error Conditions and Codes 6. Error Conditions and Codes
VCAT Call and member LSP setup can be denied for various reasons. In VCAT Call and member LSP setup can be denied for various reasons. In
addition to the call procedures and related error codes described in addition to the call procedures and related error codes described in
[RFC4974], below is a list of error conditions that can be [RFC4974], below is a list of error conditions that can be
encountered during the procedures as defined in this document. These encountered during the procedures as defined in this document. These
fall under RSVP error code TBA. fall under RSVP error code TBA.
These can occur when setting up a VCAT call or associating a VCG with These can occur when setting up a VCAT call or associating a VCG
a VCAT call. with a VCAT call.
Error Value Error 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 or unsupported ACTION 7
Any failure in call or LSP establishment MUST be treated as a failure Any failure in call or LSP establishment MUST be treated as a
of the VCG as a whole and MAY trigger the calls and LSPs associated failure of the VCG as a whole and MAY trigger the calls and LSPs
with the VCG being deleted. associated with the VCG being deleted.
7. IANA Considerations 7. IANA Considerations
7.1. RSVP CALL_ATTRIBUTE TLV 7.1. RSVP CALL_ATTRIBUTE TLV
IANA has made the following assignments in the "Class Names, Class IANA has made the following assignments in the "Class Names, Class
Numbers, and Class Types" section of the "RSVP PARAMETERS" registry Numbers, and Class Types" section of the "RSVP PARAMETERS" registry
located at http://www.iana.org/assignments/rsvp-parameters. located at http://www.iana.org/assignments/rsvp-parameters.
We request that IANA make assignments from the CALL_ATTRIBUTES TLV We request that IANA make assignments from the CALL_ATTRIBUTES TLV
[RFC6001] portions of this registry. [RFC6001] portions of this registry.
skipping to change at page 16, line 28 skipping to change at page 17, line 4
7.1. RSVP CALL_ATTRIBUTE TLV 7.1. RSVP CALL_ATTRIBUTE TLV
IANA has made the following assignments in the "Class Names, Class IANA has made the following assignments in the "Class Names, Class
Numbers, and Class Types" section of the "RSVP PARAMETERS" registry Numbers, and Class Types" section of the "RSVP PARAMETERS" registry
located at http://www.iana.org/assignments/rsvp-parameters. located at http://www.iana.org/assignments/rsvp-parameters.
We request that IANA make assignments from the CALL_ATTRIBUTES TLV We request that IANA make assignments from the CALL_ATTRIBUTES TLV
[RFC6001] portions of this registry. [RFC6001] portions of this registry.
This document introduces a new CALL_ATTRIBUTES TLV This document introduces a new CALL_ATTRIBUTES TLV
TLV Value Name Reference TLV Value Name Reference
--------- ---------------------- --------- --------- ---------------------- ---------
TBD (2) VCAT_TLV This I-D TBD VCAT_TLV This I-D
7.2. RSVP Error Codes and Error Values 7.2. RSVP Error Codes and Error Values
A new RSVP Error Code and new Error Values are introduced. We A new RSVP Error Code and new Error Values are introduced. We
request IANA make assignments from the "RSVP Parameters" registry request IANA make assignments from the "RSVP Parameters" registry
using the sub-registry "Error Codes and Globally-Defined Error Value using the sub-registry "Error Codes and Globally-Defined Error Value
Sub-Codes". Sub-Codes".
o Error Codes: o Error Codes:
- VCAT Call Management (value TBD) - VCAT Call Management (value TBD)
o Error Values: o Error Values:
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 or unsupported ACTION 7
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 control change the relationship between LSRs that are adjacent in the
plane. The call information associated with diversely routed control control plane. The call information associated with diversely
plane LSPs, in the event of an interception, may indicate that these routed control plane LSPs, in the event of an interception, may
are members of the same VCAT group that take a different route, and indicate that these are members of the same VCAT group that take a
may indicate to an interceptor that the VCG call desires increased different route, and may indicate to an interceptor that the VCG
reliability. call desires increased reliability.
See [RFC5920] for additional information on GMPLS security.
9. Contributors 9. Contributors
Wataru Imajuku (NTT) Wataru Imajuku (NTT)
1-1 Hikari-no-oka Yokosuka Kanagawa 239-0847 1-1 Hikari-no-oka Yokosuka Kanagawa 239-0847
Japan Japan
Phone +81-46-859-4315 Phone +81-46-859-4315
Email: imajuku.wataru@lab.ntt.co.jp Email: imajuku.wataru@lab.ntt.co.jp
skipping to change at page 19, line 37 skipping to change at page 19, line 37
2005. 2005.
[RFC4974] Papadimitriou, D. and A. Farrel, "Generalized MPLS [RFC4974] Papadimitriou, D. and A. Farrel, "Generalized MPLS
(GMPLS) RSVP-TE Signaling Extensions in Support of (GMPLS) RSVP-TE Signaling Extensions in Support of
Calls", RFC 4974, August 2007. Calls", RFC 4974, August 2007.
11.2. Informative References 11.2. Informative References
[ANSI-T1.105] American National Standards Institute, "Synchronous [ANSI-T1.105] American National Standards Institute, "Synchronous
Optical Network (SONET) - Basic Description including Optical Network (SONET) - Basic Description including
Multiplex Structure, Rates, and Formats", ANSI T1.105- Multiplex Structure, Rates, and Formats", ANSI
2001, May 2001. T1.105-2001, May 2001.
[G7042] International Telecommunications Union, "Link Capacity [G7042] International Telecommunications Union, "Link
Adjustment Scheme (LCAS) for Virtual Concatenated Capacity Adjustment Scheme (LCAS) for Virtual
Signals", ITU-T Recommendation G.7042, March 2006. Concatenated Signals", ITU-T Recommendation G.7042,
March 2006.
[ITU-T-G.7043] International Telecommunications Union, "Virtual [ITU-T-G.7043] International Telecommunications Union, "Virtual
Concatenation of Plesiochronous Digital Hierarchy Concatenation of Plesiochronous Digital Hierarchy
(PDH) Signals", ITU-T Recommendation G.7043, July (PDH) Signals", ITU-T Recommendation G.7043, July
2004. 2004.
[ITU-T-G.704] International Telecommunications Union, " Synchronous [ITU-T-G.704] International Telecommunications Union, " Synchronous
frame structures used at 1544, 6312, 2048, 8448 and 44 frame structures used at 1544, 6312, 2048, 8448 and
736 kbit/s hierarchical levels", ITU-T Recommendation 44 736 kbit/s hierarchical levels", ITU-T
G.704, October 1998. Recommendation G.704, October 1998.
[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 [RFC5920] L. Fang, Ed., "Security Framework for MPLS and GMPLS
Networks", July 2010.
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
Ericsson Ericsson
skipping to change at page 21, line 19 skipping to change at page 21, line 26
claimed to pertain to the implementation or use of the technology claimed to pertain to the implementation or use of the technology
described in any IETF Document or the extent to which any license described in any IETF Document or the extent to which any license
under such rights might or might not be available; nor does it under such rights might or might not be available; nor does it
represent that it has made any independent effort to identify any represent that it has made any independent effort to identify any
such rights. such rights.
Copies of Intellectual Property disclosures made to the IETF Copies of Intellectual Property disclosures made to the IETF
Secretariat and any assurances of licenses to be made available, or Secretariat and any assurances of licenses to be made available, or
the result of an attempt made to obtain a general license or the result of an attempt made to obtain a general license or
permission for the use of such proprietary rights by implementers or permission for the use of such proprietary rights by implementers or
users of this specification can be obtained from the IETF on-line IPR users of this specification can be obtained from the IETF on-line
repository at http://www.ietf.org/ipr IPR repository at http://www.ietf.org/ipr
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
any standard or specification contained in an IETF Document. Please any standard or specification contained in an IETF Document. Please
address the information to the IETF at ietf-ipr@ietf.org. address the information to the IETF at ietf-ipr@ietf.org.
Disclaimer of Validity Disclaimer of Validity
All IETF Documents and the information contained therein are provided All IETF Documents and the information contained therein are
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY,
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL THE 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
 End of changes. 75 change blocks. 
229 lines changed or deleted 255 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/