--- 1/draft-ietf-ccamp-gmpls-dcsc-channel-ext-02.txt 2010-01-20 20:11:02.000000000 +0100 +++ 2/draft-ietf-ccamp-gmpls-dcsc-channel-ext-03.txt 2010-01-20 20:11:02.000000000 +0100 @@ -1,60 +1,59 @@ Internet Draft Lou Berger (LabN) -Updates: 3471, 3473, 3945, 4202 Don Fedyk (Alcatel-Lucent) +Updates: 3471, 3473, 3945, 4202, 4203, 5307 Don Fedyk (Alcatel-Lucent) Category: Standards Track -Expiration Date: April 14, 2010 +Expiration Date: July 19, 2010 - October 14, 2009 + January 19, 2010 Generalized MPLS (GMPLS) Data Channel Switching Capable (DCSC) and Channel Set Label Extensions - draft-ietf-ccamp-gmpls-dcsc-channel-ext-02.txt + draft-ietf-ccamp-gmpls-dcsc-channel-ext-03.txt Status of this Memo - This Internet-Draft is submitted to IETF in full conformance with the + This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. - By submitting this Internet-Draft, each author represents that any - applicable patent or other IPR claims of which he or she is aware - have been or will be disclosed, and any of which he or she becomes - aware will be disclosed, in accordance with BCP 78 and BCP 79. - Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html - This Internet-Draft will expire on April 14, 2010. + This Internet-Draft will expire on July 19, 2010. Copyright and License Notice - Copyright (c) 2009 IETF Trust and the persons identified as the + Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal - Provisions Relating to IETF Documents in effect on the date of - publication of this document (http://trustee.ietf.org/license-info). - Please review these documents carefully, as they describe your rights - and restrictions with respect to this document. + Provisions Relating to IETF Documents + (http://trustee.ietf.org/license-info) in effect on the date of + publication of this document. Please review these documents + carefully, as they describe your rights and restrictions with respect + to this document. Code Components extracted from this document must + include Simplified BSD License text as described in Section 4.e of + the Trust Legal Provisions and are provided without warranty as + 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 @@ -80,73 +79,81 @@ 6 References ............................................. 9 6.1 Normative References ................................... 9 6.2 Informative References ................................. 10 7 Acknowledgments ........................................ 11 8 Author's Addresses ..................................... 11 1. Introduction This document describes two technology independent extensions to Generalized Multi-Protocol Label Switching (GMPLS). Both of these - extensions were initially defined to 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 nature and may be useful to any switching technology controlled via GMPLS. The first extension defines a new switching type, which is called Data Channel Switching Capable (DCSC). DCSC 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. + data plane label to be controlled as part of a GMPLS label-switched + path (LSP). 1.1. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 2. Data Channel Switching Current GMPLS switching types are defined in [RFC3945] and [RFC3471] and support switching at the packet (PSC), frame (L2SC), time-slot - (TDM), frequency (LSC) and fiber (FSC) granularities. One type of - switching that is not well represented in this current set is - switching that occurs when all data received on an ingress port is - switched through a network to an egress port. While there are - similarities between this level of switching and the "opaque single - wavelength" case described in Section 3.5 of [RFC4202], such port-to- - port switching is not limited to the optical switching technology - implied by the LSC type. FSC is also similar, but it is restricted to - fiber ports and also supports multiple data channels with-in the - fiber port. + (TDM), frequency (LSC) and fiber (FSC) granularities. Parallel + definitions for these switching types are also made in [RFC4202], + [RFC4203] and [RFC5307]. - This document defines the new switching type called Data Channel + One type of switching that is not well represented in this current + set is switching that occurs when all data received on an ingress + port is switched through a network to an egress port. While there + are similarities between this level of switching and the "opaque + single wavelength" case described in Section 3.5 of [RFC4202], such + port-to-port switching is not limited to the optical switching + technology implied by the LSC type. FSC is also similar, but it is + restricted to fiber ports and also supports multiple data channels + within a fiber port. + + This document defines a new switching type called Data Channel Switching Capable (DCSC). Port switching seems a more intuitive name, - but this naming collides with PSC so it isn't 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 on single channel interfaces. Interfaces that inherently support multiple channels, e.g., WDM and channelized TDM interfaces, are specifically excluded from this type. Any interface that can be represented as a single digital channel are included. Examples include concatenated TDM and line encoded interfaces. Framed interfaces may also be included when they support switching on an interface granularity. DCSC is represented in GMPLS, see [RFC3471] and [RFC4202], using the - value TBA (by IANA). + value TBA (by IANA). The DCSC value is carried in routing protocols + in the Interface Switching Capability Descriptor defined in + [RFC4202], and used in OSPF [RFC4203] and IS-IS [RFC5307]. These + documents are not otherwise modified by this document. - Port labels, as defined in [RFC3471], SHOULD be used for LSPs - signaled using the DCSC Switching Type. The DCSC Switching Type may - be used with the Generalized Label Request object, [RFC3473], or the - Generalized Channel_Set LABEL_REQUEST Object defined below. + The DCSC Switching Type may be used with the Generalized Label + Request object, [RFC3473], or the Generalized Channel_Set + LABEL_REQUEST Object defined below. Port labels, as defined in + [RFC3471], SHOULD be used for LSPs signaled using the DCSC Switching + Type. 2.1. Compatibility Transit and egress nodes that do not support the DCSC Switching Type when receiving a Path message with a Label Request containing the DCSC Switching Type will behave in the same way nodes generally handle the case of an unsupported Switching Type. Specifically, per [RFC3473], such nodes are required to generate a PathErr message, with a "Routing problem/Unsupported Encoding" indication. @@ -246,21 +253,27 @@ 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) is used in a LABEL or UPSTREAM_LABEL object to indicate that the subchannel(s) used in the corresponding (downstream or upstream) direction MUST match the subchannel(s) carried in the reverse directions label object. When value of zero (0) is used, no Subchannels are included in the Channel_Set Sub-Object 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 - object of the same LSP. + objects of the same LSP. Note that unacceptable label values + continue to be handled according to [RFC3209] and [RFC3473], + i.e., they result in PathErr or ResvErr messages with a + "Routing problem/Unacceptable label value" indication. For + example, in the case where a Resv message containing a zero (0) + in both the LABEL and UPSTREAM_LABEL objects is received, the + node would generate a ResvErr message. Label Type: 14 bits See [RFC3473] for a description of this field. Subchannel: Variable See [RFC3471] for a description of this field. Note that this field might not be 32 bit aligned. @@ -392,20 +405,28 @@ RFC 3473, January 2003. [RFC3945] Mannie, E., Editor, "Generalized Multi-Protocol Label Switching (GMPLS) Architecture", RFC 3945, October 2004. [RFC4202] Kompella, K., Ed., and Y. Rekhter, Ed., "Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)", RFC 4202, October 2005. + [RFC4203] Kompella, K. and Y. Rekhter, "OSPF Extensions in + Support of Generalized Multi-Protocol Label Switching + (GMPLS)", RFC 4203, October 2005. + + [RFC5307] Kompella, K. and Rekhter, Y., "IS-IS Extensions in + Support of Generalized Multi-Protocol Label Switching + (GMPLS)", RFC 5307, October 2008. + 6.2. Informative References [GMPLS-ESVCS] Berger, L., Fedyk, D., "Generalized MPLS (GMPLS) Support For Metro Ethernet Forum and G.8011 Ethernet Service Switching", Work in Progress, draft-ietf-ccamp-gmpls-ether-svcs. [GMPLS-MEF-UNI] Berger, L., Fedyk, D., "Generalized MPLS (GMPLS) Support For Metro Ethernet Forum and G.8011 User-Network Interface (UNI)", Work in Progress, @@ -434,11 +455,11 @@ LabN Consulting, L.L.C. Phone: +1-301-468-9228 Email: lberger@labn.net Don Fedyk Alcatel-Lucent Groton, MA, 01450 Phone: +1-978-467-5645 Email: donald.fedyk@alcatel-lucent.com -Generated on: Wed Oct 14 14:46:36 EDT 2009 +Generated on: Wed Jan 20 13:22:05 EST 2010