draft-ietf-ccamp-gmpls-dcsc-channel-ext-03.txt   draft-ietf-ccamp-gmpls-dcsc-channel-ext-04.txt 
Internet Draft Lou Berger (LabN) Internet Draft Lou Berger (LabN)
Updates: 3471, 3473, 3945, 4202, 4203, 5307 Don Fedyk (Alcatel-Lucent) Updates: 3471, 3473, 3945, 4202, 4203, 5307 Don Fedyk (Alcatel-Lucent)
Category: Standards Track Category: Standards Track
Expiration Date: July 19, 2010 Expiration Date: August 18, 2010
January 19, 2010 February 18, 2010
Generalized MPLS (GMPLS) Data Channel Switching Capable (DCSC) and Generalized MPLS (GMPLS) Data Channel Switching Capable (DCSC) and
Channel Set Label Extensions Channel Set Label Extensions
draft-ietf-ccamp-gmpls-dcsc-channel-ext-03.txt draft-ietf-ccamp-gmpls-dcsc-channel-ext-04.txt
Abstract
This document describes two technology-independent extensions to
Generalized Multi-Protocol Label Switching. The first extension
defines the new switching type Data Channel Switching Capable.
Data Channel Switching Capable interfaces are able to support
switching of the whole digital channel presented on single channel
interfaces. The second extension defines a new type of
generalized label and updates related objects. The new label is
called the Generalized Channel_Set Label and allows more than one
data plane label to be controlled as part of an LSP.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted 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 35 skipping to change at page 1, line 47
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/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
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 July 19, 2010. This Internet-Draft will expire on August 18, 2010
Copyright and License Notice Copyright and License Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Abstract
This document describes two technology-independent extensions to
Generalized Multi-Protocol Label Switching. The first extension
defines the new switching type Data Channel Switching Capable. Data
Channel Switching Capable interfaces are able to support switching of
the whole digital channel presented on single channel interfaces.
The second extension defines a new type of generalized label and
updates related objects. The new label is called the Generalized
Channel_Set Label and allows more than one data plane label to be
controlled as part of an LSP.
Table of Contents Table of Contents
1 Introduction ........................................... 3 1 Introduction ........................................... 3
1.1 Conventions used in this document ...................... 3 1.1 Conventions used in this document ...................... 3
2 Data Channel Switching ................................. 3 2 Data Channel Switching ................................. 3
2.1 Compatibility .......................................... 4 2.1 Compatibility .......................................... 4
3 Generalized Channel_Set Label Related Formats .......... 4 3 Generalized Channel_Set Label Related Formats .......... 4
3.1 Generalized Channel_Set LABEL_REQUEST Object ........... 5 3.1 Generalized Channel_Set LABEL_REQUEST Object ........... 5
3.2 Generalized Channel_Set LABEL Object ................... 5 3.2 Generalized Channel_Set LABEL Object ................... 5
3.3 Other Label related Objects ............................ 7 3.3 Other Label Related Objects ............................ 8
3.4 Compatibility .......................................... 8 3.4 Compatibility .......................................... 8
4 IANA Considerations .................................... 8 4 IANA Considerations .................................... 8
4.1 Data Channel Switching Type ............................ 8 4.1 Data Channel Switching Type ............................ 8
4.2 Generalized Channel_Set LABEL_REQUEST Object ........... 8 4.2 Generalized Channel_Set LABEL_REQUEST Object ........... 9
4.3 Generalized Channel_Set LABEL Object ................... 9 4.3 Generalized Channel_Set LABEL Object ................... 9
5 Security Considerations ................................ 9 5 Security Considerations ................................ 10
6 References ............................................. 9 6 References ............................................. 10
6.1 Normative References ................................... 9 6.1 Normative References ................................... 10
6.2 Informative References ................................. 10 6.2 Informative References ................................. 11
7 Acknowledgments ........................................ 11 7 Acknowledgments ........................................ 11
8 Author's Addresses ..................................... 11 8 Author's Addresses ..................................... 11
1. Introduction 1. Introduction
This document describes two technology independent extensions to This document describes two technology independent extensions to
Generalized Multi-Protocol Label Switching (GMPLS). Both of these Generalized Multi-Protocol Label Switching (GMPLS). Both of these
extensions were initially defined in the context of Ethernet extensions were initially defined in the context of Ethernet
services, see [GMPLS-ESVCS] and [GMPLS-MEF-UNI], but are generic in services, see [GMPLS-ESVCS] and [GMPLS-MEF-UNI], but are generic in
nature and may be useful to any switching technology controlled via nature and may be useful to any switching technology controlled via
skipping to change at page 4, line 7 skipping to change at page 4, line 7
This document defines a new switching type called Data Channel This document defines a new switching type called Data Channel
Switching Capable (DCSC). Port switching seems a more intuitive name, Switching Capable (DCSC). Port switching seems a more intuitive name,
but this naming collides with PSC so is not used. DCSC interfaces but this naming collides with PSC so is not used. DCSC interfaces
are able to support switching of the whole digital channel presented are able to support switching of the whole digital channel presented
on single channel interfaces. Interfaces that inherently support on single channel interfaces. Interfaces that inherently support
multiple channels, e.g., WDM and channelized TDM interfaces, are multiple channels, e.g., WDM and channelized TDM interfaces, are
specifically excluded from this type. Any interface that can be specifically excluded from this type. Any interface that can be
represented as a single digital channel are included. Examples represented as a single digital channel are included. Examples
include concatenated TDM and line encoded interfaces. Framed include concatenated TDM and line encoded interfaces. Framed
interfaces may also be included when they support switching on an interfaces may also be included when they support switching on an
interface granularity. interface granularity, for example Ethernet terminated at the
physical (port) level and all traffic received on a port is switched
to a physical port at the LSP egress.
DCSC is represented in GMPLS, see [RFC3471] and [RFC4202], using the DCSC is represented in GMPLS, see [RFC3471] and [RFC4202], using the
value TBA (by IANA). The DCSC value is carried in routing protocols value TBA (by IANA). The DCSC value is carried in routing protocols
in the Interface Switching Capability Descriptor defined in in the Interface Switching Capability Descriptor defined in
[RFC4202], and used in OSPF [RFC4203] and IS-IS [RFC5307]. These [RFC4202], and used in OSPF [RFC4203] and IS-IS [RFC5307]. These
documents are not otherwise modified by this document. documents are not otherwise modified by this document.
The DCSC Switching Type may be used with the Generalized Label The DCSC Switching Type may be used with the Generalized Label
Request object, [RFC3473], or the Generalized Channel_Set Request object, [RFC3473], or the Generalized Channel_Set
LABEL_REQUEST Object defined below. Port labels, as defined in LABEL_REQUEST Object defined below. Port labels, as defined in
skipping to change at page 6, line 40 skipping to change at page 6, line 40
be used when possible to minimize the size of the Channel_Set be used when possible to minimize the size of the Channel_Set
LABEL Object. LABEL Object.
Number of Subchannels: 10 bits Number of Subchannels: 10 bits
Indicates the number of subchannels carried in the sub-object. Indicates the number of subchannels carried in the sub-object.
When the number of subchannels required exceeds the limit of When the number of subchannels required exceeds the limit of
the field, i.e., 1024, multiple Channel_Set Sub-Objects MUST be the field, i.e., 1024, multiple Channel_Set Sub-Objects MUST be
used. Note that the size of the sub-object may result in a used. Note that the size of the sub-object may result in a
Path message being larger than a single unfragmented IP packet. Path message being larger than a single unfragmented IP packet.
See section 4.4 for an example of how this case may be handled. See Section 4.4 of [GMPLS-ESVCS] for an example of how this
case may be handled.
A value of zero (0) has special meaning and MAY be used in A value of zero (0) has special meaning and MAY be used in
either the LABEL or UPSTREAM_LABEL object. A value of zero (0) either the LABEL or UPSTREAM_LABEL object. A value of zero (0)
is used in a LABEL or UPSTREAM_LABEL object to indicate that is used in a LABEL or UPSTREAM_LABEL object to indicate that
the subchannel(s) used in the corresponding (downstream or the subchannel(s) used in the corresponding (downstream or
upstream) direction MUST match the subchannel(s) carried in the upstream) direction MUST match the subchannel(s) carried in the
reverse directions label object. When value of zero (0) is reverse directions label object. When value of zero (0) is
used, no Subchannels are included in the Channel_Set Sub-Object used, no Subchannels are included in the Channel_Set Sub-Object
and only one Channel_Set Sub-Object may be present. The zero and only one Channel_Set Sub-Object may be present. The zero
(0) value MUST NOT be used in both the LABEL and UPSTREAM_LABEL (0) value MUST NOT be used in both the LABEL and UPSTREAM_LABEL
skipping to change at page 7, line 34 skipping to change at page 7, line 35
The Padding field MUST be included when the number of bits The Padding field MUST be included when the number of bits
represented in all the Subchannel fields included in a represented in all the Subchannel fields included in a
Generalized Channel_Set Sub-Object result in the Sub-Object not Generalized Channel_Set Sub-Object result in the Sub-Object not
being 32 bit aligned. When present, the Padding field MUST being 32 bit aligned. When present, the Padding field MUST
have a length that results in the Sub-Object being 32 bit have a length that results in the Sub-Object being 32 bit
aligned. When present, the Padding field MUST be set to a zero aligned. When present, the Padding field MUST be set to a zero
(0) value on transmission and MUST be ignored on receipt. (0) value on transmission and MUST be ignored on receipt.
These bits SHOULD be passed through unmodified by transit These bits SHOULD be passed through unmodified by transit
nodes. nodes.
3.3. Other Label related Objects Note that the overall length of a Channel_Set Sub-Object is
determined based on the value of the Num Subchannels field together
with the size of each Subchannel field as well as any required
padding. The size of the Subchannel field is uniquely identified by
the Label Type field.
3.3. Other Label Related Objects
The previous section introduced a new LABEL object. As such the The previous section introduced a new LABEL object. As such the
formats of the other label related objects are also impacted. formats of the other label related objects and subobjects are also
Processing of these objects is not modified and remains per their impacted. Processing of these objects and subobjects is not modified
respective specifications. The other label related objects are and remains per their respective specifications. The other label
defined in [RFC3473] and include: related objects and subobjects are defined in [RFC3473] and include:
- SUGGESTED_LABEL object - SUGGESTED_LABEL object
- LABEL_SET object - LABEL_SET object
- ACCEPTABLE_LABEL_SET object - ACCEPTABLE_LABEL_SET object
- UPSTREAM_LABEL object - UPSTREAM_LABEL object
- RECOVERY_LABEL object - RECOVERY_LABEL object
- Label ERO subobject
- Label RRO subobject
The label related objects and subobjects each contain a Label field,
all of which may carry any label type. As any label type may be
carried, the introduction of a new label type means that the new
label type may be carried in the Label field of each of the label
related objects and subobjects. No new definition needs to specified
as their original specification is label type agnostic.
3.4. Compatibility 3.4. Compatibility
Transit and egress nodes that do not support the Generalized Transit and egress nodes that do not support the Generalized
Channel_Set Label related formats will first receive a Path message Channel_Set Label related formats will first receive a Path message
containing Generalized Channel_Set LABEL_REQUEST object. When such a containing Generalized Channel_Set LABEL_REQUEST object. When such a
node receives the Path message, per [RFC3209], it will send a PathErr node receives the Path message, per [RFC3209], it will send a PathErr
with the error code "Unknown object C_Type". with the error code "Unknown object C_Type".
Ingress nodes initiating a Path message containing a Generalized Ingress nodes initiating a Path message containing a Generalized
skipping to change at line 465 skipping to change at line 483
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
Phone: +1-301-468-9228 Phone: +1-301-468-9228
Email: lberger@labn.net Email: lberger@labn.net
Don Fedyk Don Fedyk
Alcatel-Lucent Alcatel-Lucent
Groton, MA, 01450 Groton, MA, 01450
Phone: +1-978-467-5645 Phone: +1-978-467-5645
Email: donald.fedyk@alcatel-lucent.com Email: donald.fedyk@alcatel-lucent.com
Generated on: Wed Jan 20 13:22:05 EST 2010 Generated on: Thu Feb 18 19:47:04 EST 2010
 End of changes. 14 change blocks. 
29 lines changed or deleted 47 lines changed or added

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