draft-ietf-ccamp-gmpls-sonet-sdh-05.txt   draft-ietf-ccamp-gmpls-sonet-sdh-06.txt 
CCAMP Working Group Eric Mannie (KPNQwest) - Editor CCAMP Working Group Eric Mannie (KPNQwest) - Editor
Internet Draft Dimitri Papadimitriou (Alcatel) - Editor Internet Draft Dimitri Papadimitriou (Alcatel) - Editor
Expiration Date: December 2002
Stefan Ansorge (Alcatel)
Peter Ashwood-Smith (Nortel)
Ayan Banerjee (Calient)
Lou Berger (Movaz)
Greg Bernstein (Ciena)
Angela Chiu (Celion)
John Drake (Calient)
Yanhe Fan (Axiowave)
Michele Fontana (Alcatel)
Gert Grammel (Alcatel)
Juergen Heiles (Siemens)
Suresh Katukam (Cisco)
Kireeti Kompella (Juniper)
Jonathan P. Lang (Calient)
Fong Liaw (Solas)
Zhi-Wei Lin (Lucent)
Ben Mack-Crane (Tellabs)
Dimitrios Pendarakis (Tellium)
Mike Raftelis (White Rock)
Bala Rajagopalan (Tellium)
Yakov Rekhter (Juniper)
Debanjan Saha (Tellium)
Vishal Sharma (Metanoia)
George Swallow (Cisco)
Z. Bo Tang (Tellium)
Eve Varma (Lucent)
Maarten Vissers (Lucent)
Yangguang Xu (Lucent)
June 2002 Expiration Date: February 2003 August 2002
Generalized Multiprotocol Label Switching Extensions for Generalized Multiprotocol Label Switching Extensions for
SONET and SDH Control SONET and SDH Control
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt draft-ietf-ccamp-gmpls-sonet-sdh-06.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are all provisions of Section 10 of RFC2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), working documents of the Internet Engineering Task Force (IETF),
its areas, and its working groups. Note that other groups may its areas, and its working groups. Note that other groups may
also distribute working documents as Internet-Drafts. also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." progress."
Mannie & Papadimitriou Editors 1
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002
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
Abstract Abstract
This document is a companion to the Generalized Multiprotocol This document is a companion to the Generalized Multiprotocol
Label Switching (GMPLS) signaling. It defines the SONET/SDH Label Switching (GMPLS) signaling. It defines the Synchronous
Optical Network (SONET)/Synchronous Digital Hierarchy (SDH)
technology specific information needed when using GMPLS signaling. technology specific information needed when using GMPLS signaling.
E.Mannie & D.Papadimitriou Editors 1
draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
Contributors
Contributors are listed by alphabetical order.
Stefan Ansorge (Alcatel)
Lorenzstrasse 10
70435 Stuttgart, Germany
Phone: +49 711 821-33744
Email: stefan.ansorge@alcatel.de
Peter Ashwood-Smith (Nortel Networks Corp.)
P.O. Box 3511 Station C,
Ottawa, ON K1Y 4H7, Canada
Phone: +1 613 763-4534
Email: petera@nortelnetworks.com
Ayan Banerjee (Calient Networks)
5853 Rue Ferrari
San Jose, CA 95138, USA
Phone: +1 408 972-3645
Email: abanerjee@calient.net
Lou Berger (Movaz Networks, Inc.)
7926 Jones Branch Drive
Suite 615
McLean VA, 22102, USA
Phone: +1 703 847-1801
Email: lberger@movaz.com
Greg Bernstein (Ciena Corporation)
10480 Ridgeview Court
Cupertino, CA 94014, USA
Phone: +1 408 366-4713
Email: greg@ciena.com
Angela Chiu (Celion Networks)
One Sheila Drive, Suite 2
Tinton Falls, NJ 07724-2658, USA
Phone: +1 732 747 9987
Email: angela.chiu@celion.com
John Drake (Calient Networks)
5853 Rue Ferrari
San Jose, CA 95138, USA
Phone: +1 408 972-3720
Email: jdrake@calient.net
Yanhe Fan (Axiowave Networks, Inc.)
100 Nickerson Road
Marlborough, MA 01752, USA
Phone: +1 508 460-6969 Ext. 627
Email: yfan@axiowave.com
Michele Fontana (Alcatel)
E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 2
draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
Via Trento 30,
I-20059 Vimercate, Italy
Phone: +39 039 686-7053
Email: michele.fontana@netit.alcatel.it
Gert Grammel (Alcatel)
Via Trento 30,
I-20059 Vimercate, Italy
Phone: +39 039 686-7060
Email: gert.grammel@netit.alcatel.it
Juergen Heiles (Siemens AG)
Hofmannstr. 51
D-81379 Munich, Germany
Phone: +49 89 722-48664
Email: Juergen.Heiles@icn.siemens.de
Suresh Katukam (Cisco Systems)
1450 N. McDowell Blvd,
Petaluma, CA 94954-6515, USA
Email: skatukam@cisco.com
Kireeti Kompella (Juniper Networks, Inc.)
1194 N. Mathilda Ave.
Sunnyvale, CA 94089, USA
Email: kireeti@juniper.net
Jonathan P. Lang (Calient Networks)
25 Castilian
Goleta, CA 93117, USA
Email: jplang@calient.net
Fong Liaw (Solas Research)
Email: fongliaw@yahoo.com
Zhi-Wei Lin (Lucent)
101 Crawfords Corner Rd
Holmdel, NJ 07733-3030, USA
Phone: +1 732 949-5141
Email: zwlin@lucent.com
Ben Mack-Crane (Tellabs)
Email: ben.mack-crane@tellabs.com
Dimitrios Pendarakis (Tellium, Inc.)
2 Crescent Place
P.O. Box 901
Oceanport, NJ 07757-0901, USA
Phone: +1 732 923-4254
Email: dpendarakis@tellium.com
Mike Raftelis (White Rock Networks)
18111 Preston Road Suite 900
Dallas, TX 75252, USA
E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 3
draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
Phone: +1 972 588-3728
Email: mraftelis@WhiteRockNetworks.com
Bala Rajagopalan (Tellium, Inc.)
2 Crescent Place
P.O. Box 901
Oceanport, NJ 07757-0901, USA
Phone: +1 732 923 4237
Email: braja@tellium.com
Yakov Rekhter (Juniper Networks, Inc.)
1194 N. Mathilda Ave.
Sunnyvale, CA 94089, USA
Email: yakov@juniper.net
Debanjan Saha (Tellium)
2 Crescent Place
P.O. Box 901
Oceanport, NJ 07757-0901, USA
Phone: +1 732 923 4264
Email: dsaha@tellium.com
Vishal Sharma (Metanoia, Inc.)
335 Elan Village Lane
San Jose, CA 95134, USA
Phone: +1 408 943-1794
Email: vsharma87@yahoo.com
George Swallow (Cisco Systems, Inc.)
250 Apollo Drive
Chelmsford, MA 01824, USA
Voice: +1 978 244-8143
Email: swallow@cisco.com
Z. Bo Tang (Tellium, Inc.)
2 Crescent Place
P.O. Box 901
Oceanport, NJ 07757-0901, USA
Phone: +1 732 923-4231
Email: btang@tellium.com
Eve Varma (Lucent)
101 Crawfords Corner Rd
Holmdel, NJ 07733-3030, USA
Phone: +1 732 949-8559
Email: evarma@lucent.com
Yangguang Xu (Lucent)
21-2A41, 1600 Osgood Street
North Andover, MA 01845, USA
Email: xuyg@lucent.com
E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 4
draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
1. Introduction 1. Introduction
Generalized MPLS (GMPLS) extends MPLS from supporting packet As described in [GMPLS-ARCH], Generalized MPLS (GMPLS) extends
(Packet Switching Capable - PSC) interfaces and switching to MPLS from supporting packet (Packet Switching Capable - PSC)
include support of four new classes of interfaces and switching: interfaces and switching to include support of four new classes of
Layer-2 Switch Capable (L2SC), Time-Division Multiplex (TDM), interfaces and switching: Layer-2 Switch Capable (L2SC), Time-
Lambda Switch Capable (LSC) and Fiber-Switch Capable (FSC). A Division Multiplex (TDM), Lambda Switch Capable (LSC) and Fiber-
functional description of the extensions to MPLS signaling needed Switch Capable (FSC). A functional description of the extensions
to support the new classes of interfaces and switching is provided to MPLS signaling needed to support the new classes of interfaces
in [GMPLS-SIG]. [GMPLS-RSVP] describes RSVP-TE specific formats and switching is provided in [GMPLS-SIG]. [GMPLS-RSVP] describes
and mechanisms needed to support all five classes of interfaces, RSVP-TE specific formats and mechanisms needed to support all five
and CR-LDP extensions can be found in [GMPLS-LDP]. This document classes of interfaces, and CR-LDP extensions can be found in
presents details that are specific to SONET/SDH. Per [GMPLS-SIG], [GMPLS-LDP]. This document presents details that are specific to
SONET/SDH specific parameters are carried in the signaling Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy
protocol in traffic parameter specific objects. (SDH). Per [GMPLS-SIG], SONET/SDH specific parameters are carried
in the signaling protocol in traffic parameter specific objects.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
in this document are to be interpreted as described in [RFC2119]. in this document are to be interpreted as described in [RFC2119].
The reader is assumed to be familiar with the terminology in ANSI
[T1.105], ITU-T [G.707] as well as [GMPLS-SIG], [GMPLS-RSVP] and
[GMPLS-LDP]. The following abbreviations are used in this document:
DCC: Data Communications Channel.
LOVC: Lower Order Virtual Container
HOVC: Higher Order Virtual Container
MS: Multiplex Section.
MSOH: Multiplex Section overhead.
POH: Path overhead.
RS: Regenerator Section.
RSOH: Regenerator section overhead.
SDH: Synchronous digital hierarchy.
SOH: Section overhead.
SONET: Synchronous Optical Network.
SPE: Synchronous Payload Envelope.
STM(-N): Synchronous Transport Module (-N) (SDH).
STS(-N): Synchronous Transport Signal-Level N (SONET).
VC-n: Virtual Container-n (SDH).
VTn: Virtual Tributary-n (SONET).
2. SONET and SDH Traffic Parameters 2. SONET and SDH Traffic Parameters
This section defines the GMPLS traffic parameters for SONET/SDH. This section defines the GMPLS traffic parameters for SONET/SDH.
The protocol specific formats, for the SDH/SONET-specific RSVP-TE The protocol specific formats, for the SONET/SDH-specific RSVP-TE
objects and CR-LDP TLVs are described in sections 2.2 and 2.3 objects and CR-LDP TLVs are described in sections 2.2 and 2.3
respectively. respectively.
These traffic parameters specify indeed a base set of capabilities These traffic parameters specify indeed a base set of capabilities
for SONET (ANSI T1.105) and SDH (ITU-T G.707) such as for SONET ANSI [T1.105] and SDH ITU-T [G.707] such as
concatenation and transparency. Some extra non-standard concatenation and transparency. Other documents may further
capabilities are defined in [GMPLS-SONET-SDH-EXT]. Other documents enhance this set of capabilities in the future. For instance,
could further enhance this set of capabilities in the future. For
instance, signaling for SDH over PDH (ITU-T G.832), or sub-STM-0 E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 5
(ITU-T G.708) interfaces could be defined. draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
signaling for SDH over PDH ITU-T G.832 or sub-STM-0 ITU-T G.708
interfaces could be defined.
The traffic parameters defined hereafter MUST be used when The traffic parameters defined hereafter MUST be used when
SONET/SDH is specified in the LSP Encoding Type field of a SONET/SDH is specified in the LSP Encoding Type field of a
Generalized Label Request [GMPLS-SIG]. Generalized Label Request [GMPLS-SIG].
Mannie & Papadimitriou Editors Internet-Draft December 2002 2
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002
2.1. SONET/SDH Traffic Parameters 2.1. SONET/SDH Traffic Parameters
The traffic parameters for SONET/SDH is organized as follows: The traffic parameters for SONET/SDH are organized 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signal Type | RCC | NCC | | Signal Type | RCC | NCC |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NVC | Multiplier (MT) | | NVC | Multiplier (MT) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transparency (T) | | Transparency (T) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Profile (P) | | Profile (P) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Annex 1 defines examples of SONET and SDH signal coding. Annex 1 lists examples of SONET and SDH signal coding.
Signal Type (ST): 8 bits Signal Type (ST): 8 bits
This field indicates the type of Elementary Signal that This field indicates the type of Elementary Signal that
comprises the requested LSP. Several transforms can be applied comprises the requested LSP. Several transforms can be applied
successively on the Elementary Signal to build the Final Signal successively on the Elementary Signal to build the Final Signal
being actually requested for the LSP. being actually requested for the LSP.
Each transform is optional and must be ignored if zero, except Each transform application is optional and must be ignored if
MT that cannot be zero and is ignored if equal to one. zero, except the Multiplier (MT) that cannot be zero and is
ignored if equal to one.
Transforms must be applied strictly in the following order: Transforms must be applied strictly in the following order:
- First, contiguous concatenation (by using the RCC and NCC - First, contiguous concatenation (by using the RCC and NCC
fields) can be optionally applied on the Elementary Signal, fields) can be optionally applied on the Elementary Signal,
resulting in a contiguously concatenated signal. resulting in a contiguously concatenated signal.
- Second, virtual concatenation (by using the NVC field) can - Second, virtual concatenation (by using the NVC field) can
be optionally applied either directly on the Elementary be optionally applied on the Elementary Signal resulting in
Signal, or on the contiguously concatenated signal obtained a virtually concatenated signal.
from the previous phase (see [GMPLS-SONET-SDH-EXT]). - Third, some transparency (by using the Transparency field)
- Third, some transparency can be optionally specified when can be optionally specified when requesting a frame as
requesting a frame as signal rather than an SPE or VC based signal rather than an SPE or VC based signal.
signal (by using the Transparency field).
- Fourth, a multiplication (by using the Multiplier field) can be - Fourth, a multiplication (by using the Multiplier field) can be
optionally applied either directly on the Elementary Signal, or optionally applied either directly on the Elementary Signal, or
on the contiguously concatenated signal obtained from the first on the contiguously concatenated signal obtained from the first
phase, or on the virtually concatenated signal obtained from phase, or on the virtually concatenated signal obtained from
the second phase, or on these signals combined with some the second phase, or on these signals combined with some
transparency. transparency.
Mannie & Papadimitriou Editors Internet-Draft December 2002 3 E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 6
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002 draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
Permitted Signal Type values for SONET/SDH are: Permitted Signal Type values for SONET/SDH are:
Value Type 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 VT3 SPE 3 VT3 SPE
4 VT6 SPE / VC-2 4 VT6 SPE / VC-2
5 STS-1 SPE / VC-3 5 STS-1 SPE / VC-3
6 STS-3c SPE / VC-4 6 STS-3c SPE / VC-4
7 STS-1 / STM-0 (only when requesting transparency) 7 STS-1 / STM-0 (only when requesting transparency)
8 STS-3 / STM-1 (only when requesting transparency) 8 STS-3 / STM-1 (only when requesting transparency)
9 STS-12 / STM-4 (only when requesting transparency) 9 STS-12 / STM-4 (only when requesting transparency)
10 STS-48 / STM-16 (only when requesting transparency) 10 STS-48 / STM-16 (only when requesting transparency)
11 STS-192 / STM-64 (only when requesting transparency) 11 STS-192 / STM-64 (only when requesting transparency)
12 STS-768 / STM-256 (only when requesting transparency) 12 STS-768 / STM-256 (only when requesting transparency)
A dedicated signal type is assigned to a SONET STS-3c SPE instead A dedicated signal type is assigned to a SONET STS-3c SPE instead
of coding it as a contiguous concatenation of three STS-1 SPEs. of coding it as a contiguous concatenation of three STS-1 SPEs.
This is done in order to provide easy interworking between SONET This is done in order to provide easy interworking between SONET
and SDH signaling. and SDH signaling.
Appendix 1 adds one more signal type (optional). Refer to [GMPLS- Appendix 1 adds one signal type (optional) to the above values.
SDH-SONET-EXT] for an extended set of signal type values beyond
the signal types as defined in T1.105/G.707.
Requested Contiguous Concatenation (RCC): 8 bits Requested Contiguous Concatenation (RCC): 8 bits
This field is used to request and sometimes negotiate (see This field is used to request the optional SONET/SDH contiguous
[GMPLS-SDH-SONET-EXT]) the optional SONET/SDH contiguous
concatenation of the Elementary Signal. concatenation of the Elementary Signal.
This field is a vector of flags. Each flag indicates the This field is a vector of flags. Each flag indicates the
support of a particular type of contiguous concatenation. support of a particular type of contiguous concatenation.
Several flags can be set at the same time to indicate a choice. Several flags can be set at the same time to indicate a choice.
These flags allow an upstream node to indicate to a downstream These flags allow an upstream node to indicate to a downstream
node the different types of contiguous concatenation that it node the different types of contiguous concatenation that it
supports. However, the downstream node decides which one to use supports. However, the downstream node decides which one to use
according to its own rules. according to its own rules.
A downstream node receiving simultaneously more than one flag A downstream node receiving simultaneously more than one flag
chooses a particular type of contiguous concatenation, if any chooses a particular type of contiguous concatenation, if any
supported, and based on criteria that are out of this document supported, and based on criteria that are out of this document
scope. A downstream node that doesnt support any of the scope. A downstream node that doesnt support any of the
concatenation types indicated by the field must refuse the LSP concatenation types indicated by the field must refuse the LSP
request. In particular, it must refuse the LSP request if it request. In particular, it must refuse the LSP request if it
doesnt support contiguous concatenation at all. doesnt support contiguous concatenation at all.
The upstream node knows which type of contiguous concatenation When several flags have been set, the upstream node retrieves
the downstream node chosen by looking at the position indicated the (single) type of contiguous concatenation the downstream
by the first label and the number of label(s) as returned by node has selected by looking at the position indicated by the
the downstream node. first label and the number of label(s) as returned by the
downstream node (see also Section 3).
Mannie & Papadimitriou Editors Internet-Draft December 2002 4
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002
The entire field is set to zero to indicate that no contiguous The entire field is set to zero to indicate that no contiguous
concatenation is requested at all (default value). A non-zero concatenation is requested at all (default value). A non-zero
E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 7
draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
field indicates that some contiguous concatenation is field indicates that some contiguous concatenation is
requested. requested.
The following flag is defined: The following flag is defined:
Flag 1 (bit 1): Standard contiguous concatenation. Flag 1 (bit 1): Standard contiguous concatenation.
Flag 1 indicates that only the standard SONET/SDH contiguous Flag 1 indicates that the standard SONET/SDH contiguous
concatenation as defined in T1.105/G.707 is supported. Note concatenation as defined in [T1.105]/[G.707] is supported. Note
that bit 1 is the low order bit. Other flags are reserved for that bit 1 is the low order bit. Other flags are reserved for
extensions, if not used they must be set to zero when sent, and extensions, if not used they must be set to zero when sent, and
should be ignored when received. should be ignored when received.
See note 1 hereafter in the section on the NCC about the SONET See note 1 hereafter in the section on the NCC about the SONET
contiguous concatenation of STS-1 SPEs when the number of contiguous concatenation of STS-1 SPEs when the number of
components is a multiple of three. components is a multiple of three.
Refer to [GMPLS-SONET-SDH-EXT] for an extended set of contiguous
concatenation types beyond the contiguous concatenation types as
defined in T1.105/G.707.
Number of Contiguous Components (NCC): 16 bits Number of Contiguous Components (NCC): 16 bits
This field indicates the number of identical SONET/SDH SPEs/VCs This field indicates the number of identical SONET SPEs/SDH VCs
that are requested to be concatenated, as specified in the RCC (i.e. Elementary Signal) that are requested to be concatenated,
field. as specified in the RCC field.
Note 1: when requesting a SONET STS-Nc SPE with N=3*X, the Note 1: when requesting a SONET STS-Nc SPE with N=3*X, the
elementary signal to use must always be an STS-3c SPE signal Elementary Signal to use must always be an STS-3c SPE signal
type and the value of NCC must always be equal to X. This type and the value of NCC must always be equal to X. This
allows also facilitating the interworking between SONET and allows also facilitating the interworking between SONET and
SDH. In particular, it means that the contiguous concatenation SDH. In particular, it means that the contiguous concatenation
of three STS-1 SPEs cannot not be requested because according of three STS-1 SPEs can not be requested because according to
to this specification, this type of signal must be coded using this specification, this type of signal must be coded using the
the STS-3c SPE signal type. STS-3c SPE signal type.
Note 2: when requesting a transparent STM-N/STS-N signal Note 2: when requesting a transparent STS-N/STM-N signal
limited to a single contiguously concatenated VC-4-Nc/STS-Nc- limited to a single contiguously concatenated STS-Nc_SPE/VC-4-
SPE, the signal type must be STM-N/STS-N, RCC with flag 1 and Nc, the signal type must be STS-N/STM-N, RCC with flag 1 and
NCC set to 1. NCC set to 1.
This field is irrelevant if no contiguous concatenation is The NCC value must be consistent with the type of contiguous
concatenation being requested in the RCC field. In particular,
this field is irrelevant if no contiguous concatenation is
requested (RCC = 0), in that case it must be set to zero when requested (RCC = 0), in that case it must be set to zero when
send, and should be ignored when received. A RCC value sent, and should be ignored when received. A RCC value
different from 0 must imply a number of components greater than different from 0 must imply a number of contiguous components
1. The NCC value must be consistent with the type of contiguous greater than 1.
concatenation being requested in the RCC field.
Mannie & Papadimitriou Editors Internet-Draft December 2002 5
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002
Number of Virtual Components (NVC): 16 bits Number of Virtual Components (NVC): 16 bits
This field indicates the number of signals that are requested This field indicates the number of signals that are requested
to be virtually concatenated. These signals are all of the same to be virtually concatenated. These signals are all of the same
type by definition. They are Elementary Signal SPEs/VCs for type by definition. They are Elementary Signal SPEs/VCs for
which signal types are defined in this document, i.e. VT1.5 which signal types are defined in this document, i.e.
SPE, VT2 SPE, VT3 SPE, VT6 SPE, STS-1 SPE, STS-3c SPE, VC-11, VT1.5_SPE/VC-11, VT2_SPE/VC-12, VT3_SPE, VT6_SPE/VC-2, STS-
VC-12, VC-2, VC-3 or VC-4. 1_SPE/VC-3 or STS-3c_SPE/VC-4.
E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 8
draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
This field is set to 0 (default value) to indicate that no This field is set to 0 (default value) to indicate that no
virtual concatenation is requested. virtual concatenation is requested.
Refer to [GMPLS-SONET-SDH-EXT] for an extended set of signals that
can be virtually concatenated beyond the virtual concatenation as
defined in T1.105/G.707.
Multiplier (MT): 16 bits Multiplier (MT): 16 bits
This field indicates the number of identical signals that are This field indicates the number of identical signals that are
requested for the LSP, i.e. that form the Final Signal. These requested for the LSP, i.e. that form the Final Signal. These
signals can be either identical Elementary Signals, or signals can be either identical Elementary Signals, or
identical contiguously concatenated signals, or identical identical contiguously concatenated signals, or identical
virtually concatenated signals. Note that all these signals virtually concatenated signals. Note that all these signals
belong thus to the same LSP. belong thus to the same LSP.
The distinction between the components of multiple virtually The distinction between the components of multiple virtually
concatenated signals is done via the order of the labels that concatenated signals is done via the order of the labels that
are specified in the signaling. The first set of labels must are specified in the signaling. The first set of labels must
describe the first component (set of individual signals describe the first component (set of individual signals
belonging to the first virtual concatenated signal), the second belonging to the first virtual concatenated signal), the second
set must describe the second component (set of individual set must describe the second component (set of individual
signals belonging to the second virtual concatenated signal) signals belonging to the second virtual concatenated signal)
and so on. and so on.
This field is set to one (default value) to indicate that This field is set to one (default value) to indicate that exactly
exactly one instance of a signal is being requested. Zero is an one instance of a signal is being requested. Intermediate and
invalid value. egress nodes MUST verify that the node itself and the interfaces
on which the LSP will be established can support the requested
multiplier value. If the requested values can not be supported,
the receiver node MUST generate a PathErr/NOTIFICATION message
(see Section 2.2/2.3, respectively).
Zero is an invalid value. If received, the node MUST generate a
PathErr/NOTIFICATION message (see Section 2.2/2.3, respectively).
Note 1: when requesting a transparent STS-N/STM-N signal limited
to a single contiguously concatenated STS-Nc-SPE/VC-4-Nc, the
multiplier field must be equal to 1 (only valid value).
Transparency (T): 32 bits Transparency (T): 32 bits
This field is a vector of flags that indicates the type of This field is a vector of flags that indicates the type of
transparency being requested. Several flags can be combined to transparency being requested. Several flags can be combined to
provide different types of transparency. Not all combinations provide different types of transparency. Not all combinations
are necessarily valid. The default value for this field is are necessarily valid. The default value for this field is
zero, i.e. no transparency requested. zero, i.e. no transparency requested.
Transparency, as defined from the point of view of this Transparency, as defined from the point of view of this
signaling specification, is only applicable to the fields in signaling specification, is only applicable to the fields in
the SONET/SDH frame overheads. In the SONET case, these are the the SONET/SDH frame overheads. In the SONET case, these are the
fields in the Section Overhead (SOH), and the Line Overhead fields in the Section Overhead (SOH), and the Line Overhead
(LOH). In the SDH case, these are the fields in the Regenerator (LOH). In the SDH case, these are the fields in the Regenerator
Section Overhead (RSOH), the Multiplex Section overhead (MSOH), Section Overhead (RSOH), the Multiplex Section overhead (MSOH),
and the pointer fields between the two. With SONET, the pointer and the pointer fields between the two. With SONET, the pointer
fields are part of the LOH. fields are part of the LOH.
Mannie & Papadimitriou Editors Internet-Draft December 2002 6 E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 9
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002 draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
Note as well that transparency is only applicable when using Note as well that transparency is only applicable when using
the following Signal Types: STM-0, STM-1, STM-4, STM-16, STM- the following Signal Types: STS-1/STM-0, STS-3/STM-1, STS-12/
64, STM-256, STS-1, STS-3, STS-12, STS-48, STS-192, and STS- STM-4, STS-48/STM-16, STS-192/STM-64 and STS-768/STM-256. At
768. At least one transparency type must be specified when least one transparency type must be specified when requesting
requesting such a signal type. such a signal type.
Transparency indicates precisely which fields in these Transparency indicates precisely which fields in these
overheads must be delivered unmodified at the other end of the overheads must be delivered unmodified at the other end of the
LSP. An ingress LSR requesting transparency will pass these LSP. An ingress LSR requesting transparency will pass these
overhead fields that must be delivered to the egress LSR overhead fields that must be delivered to the egress LSR
without any change. From the ingress and egress LSRs point of without any change. From the ingress and egress LSRs point of
views, these fields must be seen as unmodified. views, these fields must be seen as unmodified.
Transparency is not applied at the interfaces with the Transparency is not applied at the interfaces with the
initiating and terminating LSRs, but is only applied between initiating and terminating LSRs, but is only applied between
intermediate LSRs. intermediate LSRs.
The transparency field is used to request an LSP that supports The transparency field is used to request an LSP that supports
the requested transparency type; it may also be used to setup the requested transparency type; it may also be used to setup
the transparency process to be applied in each intermediate the transparency process to be applied at each intermediate
LSR. LSR.
The different transparency flags are the following: The different transparency flags are the following:
Flag 1 (bit 1): Section/Regenerator Section layer. Flag 1 (bit 1): Section/Regenerator Section layer.
Flag 2 (bit 2): Line/Multiplex Section layer. Flag 2 (bit 2): Line/Multiplex Section layer.
Where bit 1 is the low order bit. Others flags are reserved, Where bit 1 is the low order bit. Others flags are reserved, they
they should be set to zero when sent, and should be ignored should be set to zero when sent, and should be ignored when
when received. A flag is set to one to indicate that the received. A flag is set to one to indicate that the corresponding
corresponding transparency is requested. transparency is requested.
Intermediate and egress nodes MUST verify that the node itself and
the interfaces on which the LSP will be established can support
the requested transparency. If the requested flags can not be
supported, the receiver node MUST generate a PathErr/ NOTIFICATION
message (see Section 2.2/2.3, respectively).
Section/Regenerator Section layer transparency means that the Section/Regenerator Section layer transparency means that the
entire frames must be delivered unmodified. This implies that entire frames must be delivered unmodified. This implies that
pointers cannot be adjusted. When using Section/Regenerator pointers cannot be adjusted. When using Section/Regenerator
Section layer transparency all other flags must be ignored. Section layer transparency all other flags must be ignored.
Line/Multiplex Section layer transparency means that the Line/Multiplex Section layer transparency means that the
LOH/MSOH must be delivered unmodified. This implies that LOH/MSOH must be delivered unmodified. This implies that
pointers cannot be adjusted. pointers cannot be adjusted.
Refer to [GMPLS-SONET-SDH-EXT] for an extended set of transparency Profile (P): 32 bits
types beyond the transparency types as defined in T1.105/G.707.
Profile (P)
This field is intended to indicate particular capabilities that This field is intended to indicate particular capabilities that
must be supported for the LSP, for example monitoring must be supported for the LSP, for example monitoring
capabilities. capabilities.
E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 10
draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
No standard profile is currently defined and this field SHOULD No standard profile is currently defined and this field SHOULD
be set to zero when transmitted and SHOULD be ignored when be set to zero when transmitted and SHOULD be ignored when
received. received.
Mannie & Papadimitriou Editors Internet-Draft December 2002 7
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002
In the future TLV based extensions may be created. In the future TLV based extensions may be created.
2.2. RSVP-TE Details 2.2. RSVP-TE Details
For RSVP-TE, the SONET/SDH traffic parameters are carried in the For RSVP-TE, the SONET/SDH traffic parameters are carried in the
SONET/SDH SENDER_TSPEC and FLOWSPEC objects. The same format is SONET/SDH SENDER_TSPEC and FLOWSPEC objects. The same format is
used both for SENDER_TSPEC object and FLOWSPEC objects. The used both for SENDER_TSPEC object and FLOWSPEC objects. The
content of the objects is defined above in Section 2.1. The content of the objects is defined above in Section 2.1. The
objects have the following class and type: objects have the following class and type:
skipping to change at line 414 skipping to change at line 585
Default General Characterization Parameters and Guaranteed Service Default General Characterization Parameters and Guaranteed Service
fragment is used, see [RFC2210]. fragment is used, see [RFC2210].
For a particular sender in a session the contents of the FLOWSPEC For a particular sender in a session the contents of the FLOWSPEC
object received in a Resv message SHOULD be identical to the object received in a Resv message SHOULD be identical to the
contents of the SENDER_TSPEC object received in the corresponding contents of the SENDER_TSPEC object received in the corresponding
Path message. If the objects do not match, a ResvErr message with Path message. If the objects do not match, a ResvErr message with
a "Traffic Control Error/Bad Flowspec value" error SHOULD be a "Traffic Control Error/Bad Flowspec value" error SHOULD be
generated. generated.
Intermediate and egress nodes MUST verify that the node itself and
the interfaces on which the LSP will be established can support
the requested Signal Type, RCC, NCC, NVC and Multiplier (as
defined in Section 2.1). If the requested value(s) can not be
supported, the receiver node MUST generate a PathErr message with
a "Traffic Control Error/ Service unsupported" indication (see
[RFC2205]).
In addition, if the MT field is received with a zero value, the
node MUST generate a PathErr message with a "Traffic Control
Error/Bad Tspec value" indication (see [RFC2205]).
Intermediate nodes MUST also verify that the node itself and the
interfaces on which the LSP will be established can support the
requested Transparency (as defined in Section 2.1). If the
requested value(s) can not be supported, the receiver node MUST
generate a PathErr message with a "Traffic Control Error/Service
unsupported" indication (see [RFC2205]).
2.3. CR-LDP Details 2.3. CR-LDP Details
For CR-LDP, the SONET/SDH traffic parameters are carried in the For CR-LDP, the SONET/SDH traffic parameters are carried in the
SONET/SDH Traffic Parameters TLV. The content of the TLV is SONET/SDH Traffic Parameters TLV. The content of the TLV is
E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 11
draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
defined above in Section 2.1. The header of the TLV has the defined above in Section 2.1. The header of the TLV has the
following format: following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F| Type | Length | |U|F| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The type field for the SONET/SDH Traffic Parameters TLV is: TBA The type field for the SONET/SDH Traffic Parameters TLV is: TBA
(by IANA). (by IANA).
Mannie & Papadimitriou Editors Internet-Draft December 2002 8 Intermediate and egress nodes MUST verify that the node itself and
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002 the interfaces on which the LSP will be established can support
the requested Signal Type, RCC, NCC, NVC and Multiplier (as
defined in Section 2.1). If the requested value(s) can not be
supported, the receiver node MUST generate a NOTIFICATION message
with a "Resource Unavailable" status code (see [RFC3212]).
3. SDH and SONET Labels In addition, if the MT field is received with a zero value, the
node MUST generate a NOTIFICATION message with a "Resource
Unavailable" status code (see [RFC3212]).
SDH and SONET each define a multiplexing structure, with the SONET Intermediate nodes MUST also verify that the node itself and the
multiplex structure being a subset of the SDH multiplex structure. interfaces on which the LSP will be established can support the
These two structures are trees whose roots are respectively an requested Transparency (as defined in Section 2.1). If the
STM-N or an STS-N; and whose leaves are the signals that can be requested value(s) can not be supported, the receiver node MUST
transported via the time-slots and switched between time-slots generate a NOTIFICATION message with a "Resource Unavailable"
within an ingress port and time-slots within an egress port, i.e. status code (see [RFC3212]).
a VC-x, a VT-x SPE or an STS-x SPE. An SDH/SONET label will
identify the exact position (i.e. first time-slot) of a particular 3. SONET and SDH Labels
VC-x, VT-x SPE or STS-x SPE signal in a multiplexing structure.
SDH and SONET labels are carried in the Generalized Label per SONET and SDH each define a multiplexing structure. Both
[GMPLS-RSVP] and [GMPLS-LDP]. structures are trees whose roots are respectively an STS-N or an
STM-N; and whose leaves are the signals that can be transported
via the time-slots and switched between time-slots within an
ingress port and time-slots within an egress port, i.e. a VTx SPE,
an STS-x SPE or a VC-x. A SONET/SDH label will identify the exact
position (i.e. first time-slot) of a particular VTx SPE, STS-x SPE
or VC-x signal in a multiplexing structure. SONET and SDH labels
are carried in the Generalized Label per [GMPLS-RSVP] and [GMPLS-
LDP].
Note that by time-slots we mean the time-slots as they appear Note that by time-slots we mean the time-slots as they appear
logically and sequentially in the multiplex, not as they appear logically and sequentially in the multiplex, not as they appear
after any possible interleaving. after any possible interleaving.
These multiplexing structures will be used as naming trees to These multiplexing structures will be used as naming trees to
create unique multiplex entry names or labels. Since the SONET create unique multiplex entry names or labels. The same format of
multiplexing structure may be seen as a subset of the SDH label is used for SONET and SDH. As explained in [GMPLS-SIG], a
multiplexing structure, the same format of label is used for SDH label does not identify the "class" to which the label belongs.
and SONET. As explained in [GMPLS-SIG], a label does not identify This is implicitly determined by the link on which the label is
the "class" to which the label belongs. This is implicitly used.
determined by the link on which the label is used.
E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 12
draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
In case of signal concatenation or multiplication, a list of In case of signal concatenation or multiplication, a list of
labels can appear in the Label field of a Generalized Label. labels can appear in the Label field of a Generalized Label.
In case of contiguous concatenation, only one label appears in the In case of contiguous concatenation, only one label appears in the
Label field. This label identifies the lowest time-slot occupied Label field. This label identifies the lowest time-slot occupied
by the contiguously concatenated signal. By lowest time-slot we by the contiguously concatenated signal. By lowest time-slot we
mean the one having the lowest label when compared as integer mean the one having the lowest label (value) when compared as
values, i.e. the time-slot occupied by the first component signal integer values, i.e. the time-slot occupied by the first component
of the concatenated signal encountered when descending the tree. signal of the concatenated signal encountered when descending the
tree.
In case of virtual concatenation, the explicit ordered list of all In case of virtual concatenation, the explicit ordered list of all
labels in the concatenation is given. Each label indicates the labels in the concatenation is given. Each label indicates the
first time-slot occupied by a component of the virtually first time-slot occupied by a component of the virtually
concatenated signal. The order of the labels must reflect the concatenated signal. The order of the labels must reflect the
order of the payloads to concatenate (not the physical order of order of the payloads to concatenate (not the physical order of
time-slots). The above representation limits virtual concatenation time-slots). The above representation limits virtual concatenation
to remain within a single (component) link; it imposes as such a to remain within a single (component) link; it imposes as such a
restriction compared to the G.707/T1.105 recommendations. restriction compared to the ANSI [T1.105]/ITU-T [G.707]
recommendations.
The standard definition for virtual concatenation allows each The standard definition for virtual concatenation allows each
virtual concatenation components to travel over diverse paths. virtual concatenation components to travel over diverse paths.
Within GMPLS, virtual concatenation components must travel over Within GMPLS, virtual concatenation components must travel over
the same (component) link if they are part of the same LSP. This the same (component) link if they are part of the same LSP. This
is due to the way that labels are bound to a (component) link. is due to the way that labels are bound to a (component) link.
Note however, that the routing of components on different paths is Note however, that the routing of components on different paths is
indeed equivalent to establishing different LSPs, each one having indeed equivalent to establishing different LSPs, each one having
its own route. Several LSPs can be initiated and terminated its own route. Several LSPs can be initiated and terminated
Mannie & Papadimitriou Editors Internet-Draft December 2002 9
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002
between the same nodes and their corresponding components can then between the same nodes and their corresponding components can then
be associated together (i.e. virtually concatenated). be associated together (i.e. virtually concatenated).
In case of multiplication (i.e. using the multiplier transform), In case of multiplication (i.e. using the multiplier transform),
the explicit ordered list of all labels that take part in the the explicit ordered list of all labels that take part in the
Final Signal is given. In case of multiplication of virtually Final Signal is given. In case of multiplication of virtually
concatenated signals, the first set of labels indicates the time- concatenated signals, the first set of labels indicates the time-
slots occupied by the first virtually concatenated signal, the slots occupied by the first virtually concatenated signal, the
second set of labels indicates the time-slots occupied by the second set of labels indicates the time-slots occupied by the
second virtually concatenated signal, and so on. The above second virtually concatenated signal, and so on. The above
representation limits multiplication to remain within a single representation limits multiplication to remain within a single
(component) link. (component) link.
The format of the label for SDH and/or SONET TDM-LSR link is: The format of the label for SONET and/or SDH TDM-LSR link is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S | U | K | L | M | | S | U | K | L | M |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This is an extension of the numbering scheme defined in G.707 This is an extension of the numbering scheme defined in [G.707]
sections 7.3.7 to 7.3.13, i.e. the (K, L, M) numbering. Note that sections 7.3.7 to 7.3.13, i.e. the (K, L, M) numbering. Note that
the higher order numbering scheme defined in G.707 sections 7.3.1 the higher order numbering scheme defined in [G.707] sections
to 7.3.6 is not used here. 7.3.1 to 7.3.6 is not used here.
E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 13
draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
Each letter indicates a possible branch number starting at the Each letter indicates a possible branch number starting at the
parent node in the multiplex structure. Branches are considered as parent node in the multiplex structure. Branches are considered as
numbered in increasing order, starting from the top of the numbered in increasing order, starting from the top of the
multiplexing structure. The numbering starts at 1, zero is used to multiplexing structure. The numbering starts at 1, zero is used to
indicate a non-significant or ignored field. indicate a non-significant or ignored field.
When a field is not significant or ignored in a particular context When a field is not significant or ignored in a particular context
it MUST be set to zero when transmitted, and MUST be ignored when it MUST be set to zero when transmitted, and MUST be ignored when
received. received.
When a hierarchy of SDH/SONET LSPs is used, an LSP with a given When a hierarchy of SONET/SDH LSPs is used, a higher order LSP
bandwidth can be used to carry lower order LSPs. The higher order with a given bandwidth can be used to carry lower order LSPs.
SDH/SONET LSP behaves as a "virtual link" with a given bandwidth Remember here that a higher order LSP is established through a
(e.g. VC-3), it may also be used as a Forwarding Adjacency. A SONET/SDH higher order path layer network and a lower order LSP,
lower order SDH/SONET LSP can be established through that higher through a SONET/SDH lower order path layer network (see also ITU-T
order LSP. Since a label is local to a (virtual) link, the highest G.803, Section 3 for the corresponding definitions). In this
part of that label is non-significant and is set to zero, i.e. the context, the higher order SONET/SDH LSP behaves as a "virtual
label is "0,0,0,L,M". Similarly, if the structure of the higher link" with a given bandwidth (e.g. VC-3), it may also be used as a
Forwarding Adjacency. A lower order SONET/SDH LSP can be
established through that higher order LSP. Since a label is local
to a (virtual) link, the highest part of that label (i.e. the S, U
and K fields) is non-significant and is set to zero, i.e. the
label is "0,0,0,L,M". Similarly, if the structure of the lower
order LSP is unknown or not relevant, the lowest part of that order LSP is unknown or not relevant, the lowest part of that
label is non-significant and is set to zero, i.e. the label is label (i.e. the L and M fields) is non-significant and is set to
"S,U,K,0,0". zero, i.e. the label is "S,U,K,0,0".
For instance, a VC-3 LSP can be used to carry lower order LSPs. In For instance, a VC-3 LSP can be used to carry lower order LSPs. In
that case the labels allocated between the two ends of the VC-3 that case the labels allocated between the two ends of the VC-3
LSP for the lower order LSPs will have S, U and K set to zero, LSP for the lower order LSPs will have S, U and K set to zero,
i.e., non-significant, while L and M will be used to indicate the i.e., non-significant, while L and M will be used to indicate the
signal allocated in that VC-3. signal allocated in that VC-3.
Mannie & Papadimitriou Editors Internet-Draft December 2002 10
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002
In case of tunneling such as VC-4 containing VC-3 containing VC- In case of tunneling such as VC-4 containing VC-3 containing VC-
12/VC-11 where the SUKLM structure is not adequate to represent 12/VC-11 where the SUKLM structure is not adequate to represent
the full signal structure, a hierarchical approach must be used, the full signal structure, a hierarchical approach must be used,
i.e. per layer network signaling. i.e. per layer network signaling.
The possible values of S, U, K, L and M are defined as follows: The possible values of S, U, K, L and M are defined as follows:
1. S=1->N is the index of a particular AUG-1/STS-3 inside an 1. S=1->N is the index of a particular STS-3/AUG-1 inside an
STM-N/STS-N multiplex. S is only significant for SDH STM-N (N>0) STS-N/STM-N multiplex. S is only significant for SONET STS-N
and SONET STS-N (N>1) and must be 0 and ignored for STM-0 and (N>1) and SDH STM-N (N>0). S must be 0 and ignored for STS-1 and
STS-1. STM-0.
2. U=1->3 is the index of a particular VC-3/STS-1 SPE within an 2. U=1->3 is the index of a particular STS-1_SPE/VC-3 within an
AUG-1/STS-3. U is only significant for SDH STM-N (N>0) and SONET STS-3/AUG-1. U is only significant for SONET STS-N (N>1) and SDH
STS-N (N>1) and must be 0 and ignored for STM-0 and STS-1. STM-N (N>0). U must be 0 and ignored for STS-1 and STM-0.
3. K=1->3 is the index of a particular TUG-3 within a VC-4. K is 3. K=1->3 is the index of a particular TUG-3 within a VC-4. K is
only significant for an SDH VC-4 structured in TUG-3s and must only significant for an SDH VC-4 structured in TUG-3s. K must be
be 0 and ignored in all other cases. 0 and ignored in all other cases.
4. L=1->7 is the index of a particular TUG-2/VT Group within a E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 14
TUG-3, VC-3 or STS-1 SPE. L must be 0 and ignored in all other draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
4. L=1->7 is the index of a particular VT_Group/TUG-2 within an
STS-1_SPE/TUG-3 or VC-3. L must be 0 and ignored in all other
cases. cases.
5. M is the index of a particular VC-1/VT-1.5, VT-2 or VT-3 SPE 5. M is the index of a particular VT1.5_SPE/VC-11, VT2_SPE/VC-12
within a TUG-2/VT Group. M=1->2 indicates a specific VT-3 SPE or VT3_SPE within a VT_Group/TUG-2. M=1->2 indicates a specific
inside the corresponding VT Group, these values MUST NOT be used VT3 SPE inside the corresponding VT Group, these values MUST NOT
for SDH since there is no equivalent of VT-3 with SDH. M=3->5 be used for SDH since there is no equivalent of VT3 with SDH.
indicates a specific VC-12/VT-2 SPE inside the corresponding M=3->5 indicates a specific VT2_SPE/VC-12 inside the
TUG-2/VT Group. M=6->9 indicates a specific VC-11/VT-1.5 SPE corresponding VT_Group/TUG-2. M=6->9 indicates a specific
inside the corresponding TUG-2/VT Group. VT1.5_SPE/VC-11 inside the corresponding VT_Group/TUG-2.
Note that a label always has to be interpreted according the Note that a label always has to be interpreted according the
SDH/SONET traffic parameters, i.e. a label by itself does not SONET/SDH traffic parameters, i.e. a label by itself does not
allow knowing which signal is being requested (a label is allow knowing which signal is being requested (a label is
context sensitive). context sensitive).
The S encoding is summarized in the following table: The S encoding is summarized in the following table:
S SDH SONET S SDH SONET
------------------------------------------------ ------------------------------------------------
0 other other 0 other other
1 1st AUG-1 1st STS-3 1 1st AUG-1 1st STS-3
2 2nd AUG-1 2nd STS-3 2 2nd AUG-1 2nd STS-3
3 3rd AUG-1 3rd STS-3 3 3rd AUG-1 3rd STS-3
4 4rd AUG-1 4rd STS-3 4 4rd AUG-1 4rd STS-3
: : : : : :
N Nth AUG-1 Nth STS-3 N Nth AUG-1 Nth STS-3
Mannie & Papadimitriou Editors Internet-Draft December 2002 11
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002
The U encoding is summarized in the following table: The U encoding is summarized in the following table:
U SDH AUG-1 SONET STS-3 U SDH AUG-1 SONET STS-3
------------------------------------------------- -------------------------------------------------
0 other other 0 other other
1 1st VC-3 1st STS-1 SPE 1 1st VC-3 1st STS-1 SPE
2 2nd VC-3 2nd STS-1 SPE 2 2nd VC-3 2nd STS-1 SPE
3 3rd VC-3 3rd STS-1 SPE 3 3rd VC-3 3rd STS-1 SPE
The K encoding is summarized in the following table: The K encoding is summarized in the following table:
skipping to change at line 624 skipping to change at line 837
2 2nd TUG-3 2 2nd TUG-3
3 3rd TUG-3 3 3rd TUG-3
The L encoding is summarized in the following table: The L encoding is summarized in the following table:
L SDH TUG-3 SDH VC-3 SONET STS-1 SPE L SDH TUG-3 SDH VC-3 SONET STS-1 SPE
------------------------------------------------- -------------------------------------------------
0 other other other 0 other other other
1 1st TUG-2 1st TUG-2 1st VTG 1 1st TUG-2 1st TUG-2 1st VTG
2 2nd TUG-2 2nd TUG-2 2nd VTG 2 2nd TUG-2 2nd TUG-2 2nd VTG
E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 15
draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
3 3rd TUG-2 3rd TUG-2 3rd VTG 3 3rd TUG-2 3rd TUG-2 3rd VTG
4 4th TUG-2 4th TUG-2 4th VTG 4 4th TUG-2 4th TUG-2 4th VTG
5 5th TUG-2 5th TUG-2 5th VTG 5 5th TUG-2 5th TUG-2 5th VTG
6 6th TUG-2 6th TUG-2 6th VTG 6 6th TUG-2 6th TUG-2 6th VTG
7 7th TUG-2 7th TUG-2 7th VTG 7 7th TUG-2 7th TUG-2 7th VTG
The M encoding is summarized in the following table: The M encoding is summarized in the following table:
M SDH TUG-2 SONET VTG M SDH TUG-2 SONET VTG
------------------------------------------------- -------------------------------------------------
0 other other 0 other other
1 - 1st VT-3 SPE 1 - 1st VT3 SPE
2 - 2nd VT-3 SPE 2 - 2nd VT3 SPE
3 1st VC-12 1st VT-2 SPE 3 1st VC-12 1st VT2 SPE
4 2nd VC-12 2nd VT-2 SPE 4 2nd VC-12 2nd VT2 SPE
5 3rd VC-12 3rd VT-2 SPE 5 3rd VC-12 3rd VT2 SPE
6 1st VC-11 1st VT-1.5 SPE 6 1st VC-11 1st VT1.5 SPE
7 2nd VC-11 2nd VT-1.5 SPE 7 2nd VC-11 2nd VT1.5 SPE
8 3rd VC-11 3rd VT-1.5 SPE 8 3rd VC-11 3rd VT1.5 SPE
9 4th VC-11 4th VT-1.5 SPE 9 4th VC-11 4th VT1.5 SPE
Examples of labels: Examples of labels:
Example 1: the label for the VC-4/STS-3c in the Sth AUG-1/STS-3 Example 1: the label for the STS-3c_SPE/VC-4 in the Sth STS-3/AUG-
is: S>0, U=0, K=0, L=0, M=0. 1 is: S>0, U=0, K=0, L=0, M=0.
Example 2: the label for the VC-3 within the Kth-1 TUG-3 within Example 2: the label for the VC-3 within the Kth-1 TUG-3 within
the VC-4 in the Sth AUG-1 is: S>0, U=0, K>0, L=0, M=0. the VC-4 in the Sth AUG-1 is: S>0, U=0, K>0, L=0, M=0.
Mannie & Papadimitriou Editors Internet-Draft December 2002 12 Example 3: the label for the Uth-1 STS-1_SPE/VC-3 within the Sth
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002 STS-3/AUG-1 is: S>0, U>0, K=0, L=0, M=0.
Example 3: the label for the Uth-1 VC-3/STS-1 SPE within the Sth
AUG-1/STS-3 is: S>0, U>0, K=0, L=0, M=0.
Example 4: the label for the VC-2/VT-6 in the Lth-1 TUG-2/VT Group Example 4: the label for the VT6/VC-2 in the Lth-1 VT Group/TUG-2
in the Uth-1 VC-3/STS-1 SPE within the Sth AUG-1/STS-3 is: S>0, in the Uth-1 STS-1_SPE/VC-3 within the Sth STS-3/AUG-1 is: S>0,
U>0, K=0, L>0, M=0. U>0, K=0, L>0, M=0.
Example 5: the label for the 3rd VC-11/VT-1.5 in the Lth-1 TUG- Example 5: the label for the 3rd VT1.5_SPE/VC-11 in the Lth-1 VT
2/VT Group within the Uth-1 VC-3/STS-1 SPE within the Sth AUG- Group/TUG-2 within the Uth-1 STS-1_SPE/VC-3 within the Sth STS-
1/STS-3 is: S>0, U>0, K=0, L>0, M=8. 3/AUG-1 is: S>0, U>0, K=0, L>0, M=8.
Example 6: the label for the VC-4-4c/STS-12c which uses the 9th Example 6: the label for the STS-12c/VC-4-4c which uses the 9th
AUG-1/STS-3 as its first timeslot is: S=9, U=0, K=0, L=0, M=0. STS-3/AUG-1 as its first timeslot is: S=9, U=0, K=0, L=0, M=0.
In case of contiguous concatenation, the label that is used is the In case of contiguous concatenation, the label that is used is the
lowest label of the contiguously concatenated signal as explained lowest label (value) of the contiguously concatenated signal as
before. The higher part of the label indicates where the signal explained before. The higher part of the label indicates where the
starts and the lowest part is not significant. signal starts and the lowest part is not significant.
In case of STM-0/STS-1, the values of S, U and K must be equal to In case of STM-0/STS-1, the values of S, U and K must be equal to
zero according to the field coding rules. For instance, when zero according to the field coding rules. For instance, when
requesting a VC-3 in an STM-0 the label is S=0, U=0, K=0, L=0, requesting a VC-3 in an STM-0 the label is S=0, U=0, K=0, L=0,
M=0. When requesting a VC-11 in a VC-3 in an STM-0 the label is M=0. When requesting a VC-11 in a VC-3 in an STM-0 the label is
S=0, U=0, K=0, L>0, M=6..9. S=0, U=0, K=0, L>0, M=6..9.
When a transparent STM-N/STS-3*N (N=1, 4, 16, 64, 256) is E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 16
requested, the label is not applicable and is set to zero. draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
Refer to [GMPLS-SONET-SDH-EXT] for the label for the extended set When a transparent STS-3*N/STM-N (N=1, 4, 16, 64, 256) is
of transparency types beyond the transparency types as defined in requested, the label is not applicable and is set to zero.
T1.105/G.707.
4. Acknowledgments 4. Acknowledgments
Valuable comments and input were received from the CCAMP mailing Valuable comments and input were received from the CCAMP mailing
list where outstanding discussions took place. list where outstanding discussions took place.
5. Security Considerations 5. Security Considerations
This draft introduces no new security considerations to either This draft introduces no new security considerations to either
[GMPLS-RSVP] or [GMPLS-LDP]. GMPLS security is described in [GMPLS-RSVP] or [GMPLS-LDP]. GMPLS security is described in
section 11 of [GMPLS-SIG], in [CR-LDP] and in [RSVP-TE]. section 11 of [GMPLS-SIG], in [RFC3209] and in [RFC3212].
6. IANA Considerations 6. IANA Considerations
Three values have to be defined by IANA for this document (two Three values have to be defined by IANA for this document:
RSVP C-Types and one LDP TLV Type): two RSVP C-Types in registry:
http://www.iana.org/assignments/rsvp-parameters
and one LDP TLV Type in registry:
http://www.iana.org/assignments/ldp-namespaces
- A SONET/SDH SENDER_TSPEC object: Class = 12, C-Type = TBA (see - A SONET/SDH SENDER_TSPEC object: Class = 12, C-Type = TBA (see
section 2.2). section 2.2).
Mannie & Papadimitriou Editors Internet-Draft December 2002 13
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002
- A SONET/SDH FLOWSPEC object: Class = 9, C-Type = TBA (see - A SONET/SDH FLOWSPEC object: Class = 9, C-Type = TBA (see
section 2.2). section 2.2).
- A type field for the SONET/SDH Traffic Parameters TLV (see - A type field for the SONET/SDH Traffic Parameters TLV (see
section 2.3). section 2.3).
7. Intellectual Property Notice 7. Intellectual Property Notice
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
skipping to change at line 737 skipping to change at line 949
to obtain a general license or permission for the use of such to obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification proprietary rights by implementors or users of this specification
can be obtained from the IETF Secretariat. can be obtained from the IETF Secretariat.
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 which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
8. Normative References E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 17
draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
[GMPLS-SIG] Berger, L. et al., "Generalized MPLS - 8. References
Signaling Functional Description", Internet Draft,
draft-ietf-mpls-generalized-signaling-08.txt,
April 2002.
[GMPLS-LDP] Ashwood-Smith, P., Berger, L. et al., "Generalized 8.1 Normative References
MPLS Signaling - CR-LDP Extensions", Internet Draft,
[G.707] ITU-T Recommendation G.707, Network Node Interface
for the Synchronous Digital Hierarchy, October 2000.
[GMPLS-ARCH] Mannie, E., Papadimitriou D., et al., "Generalized
Multiprotocol Label Switching Architecture",
Internet Draft, Work in progress,
draft-ietf-ccamp-gmpls-architecture-03.txt,
August 2002.
[GMPLS-LDP] Berger, L. et al., "Generalized MPLS Signaling - CR-
LDP Extensions",
Internet Draft, Work in progress,
draft-ietf-mpls-generalized-cr-ldp-06.txt, draft-ietf-mpls-generalized-cr-ldp-06.txt,
April 2002. April 2002.
[GMPLS-RSVP] Berger, L. et al, "Generalized MPLS [GMPLS-RSVP] Berger, L. et al., "Generalized MPLS Signaling
Signaling - RSVP-TE Extensions", Internet Draft, RSVP-TE Extensions",
Internet Draft, Work in progress,
draft-ietf-mpls-generalized-rsvp-te-07.txt, draft-ietf-mpls-generalized-rsvp-te-07.txt,
April 2002. April 2002.
[CR-LDP] Jamoussi et al., "Constraint-Based LSP Setup using LDP", [GMPLS-SIG] Berger, L. et al., "Generalized MPLS - Signaling
RFC3212, January, 2002. Functional Description",
Internet Draft, Work in progress,
[RSVP-TE] Awduche, et al., "RSVP-TE: Extensions to RSVP for LSP draft-ietf-mpls-generalized-signaling-08.txt,
Tunnels", RFC 3209, December 2001. April 2002.
[RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated
Services," RFC 2210, September 1997.
Mannie & Papadimitriou Editors Internet-Draft December 2002 14
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002
9. Informative References
[GMPLS-SONET-SDH-EXT] Mannie, E., Papadimitriou D. et al.,
"Generalized Multiprotocol Label Switching extensions
to control non-standard SONET and SDH features",
Internet Draft,
draft-ietf-ccamp-gmpls-sonet-sdh-extensions-03.txt,
June 2002.
[GMPLS-ARCH] Mannie, E., Papadimitriou D. et al., " Generalized
Multiprotocol Label Switching Architecture",
Internet Draft,
draft-ietf-ccamp-gmpls-architecture-02.txt,
March 2002.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels," RFC 2119. Requirement Levels", BCP 14, RFC 2119, March 1997.
10. Contributors
Contributors are listed by alphabetical order.
Stefan Ansorge
Alcatel
Lorenzstrasse 10
70435 Stuttgart
Germany
Phone: +49 7 11 821 337 44
Email: Stefan.ansorge@alcatel.de
Peter Ashwood-Smith
Nortel Networks Corp.
P.O. Box 3511 Station C,
Ottawa, ON K1Y 4H7
Canada
Phone: +1 613 763 4534
Email: petera@nortelnetworks.com
Ayan Banerjee
Calient Networks
5853 Rue Ferrari
San Jose, CA 95138
Phone: +1 408 972-3645
Email: abanerjee@calient.net
Lou Berger
Movaz Networks, Inc.
7926 Jones Branch Drive
Suite 615
McLean VA, 22102
Phone: +1 703 847-1801
Mannie & Papadimitriou Editors Internet-Draft December 2002 15
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002
Email: lberger@movaz.com
Greg Bernstein
Ciena Corporation
10480 Ridgeview Court
Cupertino, CA 94014
Phone: +1 408 366 4713
Email: greg@ciena.com
Angela Chiu
Celion Networks
One Sheila Drive, Suite 2
Tinton Falls, NJ 07724-2658
Phone: +1 732 747 9987
Email: angela.chiu@celion.com
John Drake
Calient Networks
5853 Rue Ferrari
San Jose, CA 95138
Phone: +1 408 972 3720
Email: jdrake@calient.net
Yanhe Fan
Axiowave Networks, Inc.
100 Nickerson Road
Marlborough, MA 01752
Phone: +1 508 460 6969 Ext. 627
Email: yfan@axiowave.com
Michele Fontana
Alcatel
Via Trento 30,
I-20059 Vimercate, Italy
Phone: +39 039 686-7053
Email: michele.fontana@netit.alcatel.it
Gert Grammel
Alcatel
Via Trento 30,
I-20059 Vimercate, Italy
Phone: +39 039 686-7060
Email: gert.grammel@netit.alcatel.it
Juergen Heiles
Siemens AG
Hofmannstr. 51
D-81379 Munich, Germany
Phone: +49 89 7 22 - 4 86 64
Email: Juergen.Heiles@icn.siemens.de
Suresh Katukam
Cisco Systems
1450 N. McDowell Blvd,
Mannie & Papadimitriou Editors Internet-Draft December 2002 16
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002
Petaluma, CA 94954-6515 USA
e-mail: skatukam@cisco.com
Kireeti Kompella
Juniper Networks, Inc.
1194 N. Mathilda Ave.
Sunnyvale, CA 94089
Email: kireeti@juniper.net
Jonathan P. Lang
Calient Networks
25 Castilian
Goleta, CA 93117
Email: jplang@calient.net
Fong Liaw
Solas Research
Email: fongliaw@yahoo.com
Zhi-Wei Lin
Lucent
101 Crawfords Corner Rd
Holmdel, NJ 07733-3030
Phone: +1 732 949 5141
Email: zwlin@lucent.com
Ben Mack-Crane
Tellabs
Email: Ben.Mack-Crane@tellabs.com
Dimitrios Pendarakis
Tellium
Phone: +1 (732) 923-4254
Email: dpendarakis@tellium.com
Mike Raftelis
White Rock Networks
18111 Preston Road Suite 900
Dallas, TX 75252
Phone: +1 (972)588-3728
Fax: +1 (972)588-3701
Email: Mraftelis@WhiteRockNetworks.com
Bala Rajagopalan
Tellium, Inc.
2 Crescent Place
P.O. Box 901
Oceanport, NJ 07757-0901
Phone: +1 732 923 4237
Fax: +1 732 923 9804
Email: braja@tellium.com
Yakov Rekhter
Juniper Networks, Inc.
Mannie & Papadimitriou Editors Internet-Draft December 2002 17
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002
Email: yakov@juniper.net
Debanjan Saha
Tellium Optical Systems
2 Crescent Place
Oceanport, NJ 07757-0901
Phone: +1 732 923 4264
Fax: +1 732 923 9804
Email: dsaha@tellium.com
Vishal Sharma
Metanoia, Inc.
335 Elan Village Lane
San Jose, CA 95134
Phone: +1 408 943 1794
Email: vsharma87@yahoo.com
George Swallow [RFC2205] Braden, R., et al., "Resource ReSerVation Protocol
Cisco Systems, Inc. (RSVP) -- Version 1 Functional Specification", RFC
250 Apollo Drive 2205, September 1997.
Chelmsford, MA 01824
Voice: +1 978 244 8143
Email: swallow@cisco.com
Z. Bo Tang [RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated
Tellium, Inc. Services," RFC 2210, September 1997.
2 Crescent Place
P.O. Box 901
Oceanport, NJ 07757-0901
Phone: +1 732 923 4231
Fax: +1 732 923 9804
Email: btang@tellium.com
Eve Varma [RFC3209] Awduche, D., et al., "RSVP-TE: Extensions to RSVP for
Lucent LSP Tunnels", RFC 3209, December 2001.
101 Crawfords Corner Rd
Holmdel, NJ 07733-3030
Phone: +1 732 949 8559
Email: evarma@lucent.com
Maarten Vissers [RFC3212] Jamoussi, B., et al., "Constraint-Based LSP Setup using
Lucent LDP", RFC 3212, January 2002.
Botterstraat 45
Postbus 18
1270 AA Huizen, Netherlands
Email: mvissers@lucent.com
Yangguang Xu [T1.105] "Synchronous Optical Network (SONET): Basic
Lucent Description Including Multiplex Structure, Rates, and
21-2A41, 1600 Osgood Street Formats", ANSI T1.105, October 2000.
North Andover, MA 01845
Email: xuyg@lucent.com
Mannie & Papadimitriou Editors Internet-Draft December 2002 18 E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 18
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002 draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
11. Editors 9. Authors Addresses
Eric Mannie Eric Mannie (KPNQwest)
KPNQwest
Terhulpsesteenweg 6A Terhulpsesteenweg 6A
1560 Hoeilaart - Belgium 1560 Hoeilaart - Belgium
Phone: +32 2 658 56 52 Phone: +32 2 658-5652
Mobile: +32 496 58 56 52 Mobile: +32 496 58 56 52
Fax: +32 2 658 51 18 Fax: +32 2 658-5118
Email: eric.mannie@kpnqwest.com Email: eric.mannie@kpnqwest.com
Dimitri Papadimitriou Dimitri Papadimitriou (Alcatel)
Alcatel
Francis Wellesplein 1, Francis Wellesplein 1,
B-2018 Antwerpen, Belgium B-2018 Antwerpen, Belgium
Phone: +32 3 240-8491 Phone: +32 3 240-8491
Email: Dimitri.Papadimitriou@alcatel.be Email: dimitri.papadimitriou@alcatel.be
12. Full Copyright Statement 10. Full Copyright Statement
"Copyright (C) The Internet Society (date). All Rights Reserved. "Copyright (C) The Internet Society (date). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
skipping to change at line 1039 skipping to change at line 1050
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."
Mannie & Papadimitriou Editors Internet-Draft December 2002 19 E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 19
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002 draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
Appendix 1 - Signal Type Values Extension For VC-3 Appendix 1 - Signal Type Values Extension for VC-3
This appendix defines the following optional additional Signal This appendix defines the following optional additional Signal
Type value for the Signal Type field of section 2.1: Type value for the Signal Type field of section 2.1:
Value Type Value Type
----- --------------------- ----- ---------------------
20 "VC-3 via AU-3 at the end" 20 "VC-3 via AU-3 at the end"
According to the G.707 standard a VC-3 in the TU-3/TUG-3/VC-4/AU-4 According to the ITU-T [G.707] recommendation a VC-3 in the TU-
branch of the SDH multiplex cannot be structured in TUG-2s, 3/TUG-3/VC-4/AU-4 branch of the SDH multiplex cannot be structured
however a VC-3 in the AU-3 branch can be. In addition, a VC-3 in TUG-2s, however a VC-3 in the AU-3 branch can be. In addition,
could be switched between the two branches if required. a VC-3 could be switched between the two branches if required.
A VC-3 circuit could be terminated on an ingress interface of an A VC-3 circuit could be terminated on an ingress interface of an
LSR (e.g. forming a VC-3 forwarding adjacency). This LSR could LSR (e.g. forming a VC-3 forwarding adjacency). This LSR could
then want to demultiplex this VC-3 and switch internal low order then want to demultiplex this VC-3 and switch internal low order
LSPs. For implementation reasons, this could be only possible if LSPs. For implementation reasons, this could be only possible if
the LSR receives the VC-3 in the AU-3 branch. E.g. for an LSR not the LSR receives the VC-3 in the AU-3 branch. E.g. for an LSR not
able to switch internally from a TU-3 branch to an AU-3 branch on able to switch internally from a TU-3 branch to an AU-3 branch on
its incoming interface before demultiplexing and then switching its incoming interface before demultiplexing and then switching
the content with its switch fabric. the content with its switch fabric.
skipping to change at line 1080 skipping to change at line 1091
type. This information can be used, for instance, by the type. This information can be used, for instance, by the
penultimate LSR to switch an incoming VC-3 received in any branch penultimate LSR to switch an incoming VC-3 received in any branch
to the AU-3 branch on the outgoing interface to the destination to the AU-3 branch on the outgoing interface to the destination
LSR. LSR.
The "VC-3 via AU-3 at the end" signal type does not imply that the The "VC-3 via AU-3 at the end" signal type does not imply that the
VC-3 must be switched via the AU-3 branch at some other places in VC-3 must be switched via the AU-3 branch at some other places in
the network. The VC-3 signal type just indicates that a VC-3 in the network. The VC-3 signal type just indicates that a VC-3 in
any branch is suitable. any branch is suitable.
Mannie & Papadimitriou Editors Internet-Draft December 2002 20 E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 20
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002 draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
Annex 1 - Examples Annex 1 - Examples
This annex defines examples of SONET and SDH signal coding. Their This annex defines examples of SONET and SDH signal coding. Their
objective is to help the reader to understand how works the traffic objective is to help the reader to understand how works the traffic
parameter coding and not to give examples of typical SONET or SDH parameter coding and not to give examples of typical SONET or SDH
signals. signals.
As stated above, signal types are Elementary Signals to which As stated above, signal types are Elementary Signals to which
successive concatenation, multiplication and transparency successive concatenation, multiplication and transparency
transforms can be applied. transforms can be applied to obtain Final Signals.
1. A VC-4 signal is formed by the application of RCC with value 0, 1. A VC-4 signal is formed by the application of RCC with value 0,
NCC with value 0, NVC with value 0, MT with value 1 and T with NCC with value 0, NVC with value 0, MT with value 1 and T with
value 0 to a VC-4 Elementary Signal. value 0 to a VC-4 Elementary Signal.
2. A VC-4-7v signal is formed by the application of RCC with value 2. A VC-4-7v signal is formed by the application of RCC with value
0, NCC with value 0, NVC with value 7 (virtual concatenation of 7 0, NCC with value 0, NVC with value 7 (virtual concatenation of 7
components), MT with value 1 and T with value 0 to a VC-4 components), MT with value 1 and T with value 0 to a VC-4
Elementary Signal. Elementary Signal.
skipping to change at line 1137 skipping to change at line 1148
8. An STS-3c SPE signal is formed by the application of RCC with 8. An STS-3c SPE signal is formed by the application of RCC with
value 0 (no contiguous concatenation), NCC with value 0, NVC with value 0 (no contiguous concatenation), NCC with value 0, NVC with
value 0, MT with value 1 and T with value 0 to an STS-3c SPE value 0, MT with value 1 and T with value 0 to an STS-3c SPE
Elementary Signal. Elementary Signal.
9. An STS-48c SPE signal is formed by the application of RCC with 9. An STS-48c SPE signal is formed by the application of RCC with
flag 1 (standard contiguous concatenation), NCC with value 16, NVC flag 1 (standard contiguous concatenation), NCC with value 16, NVC
with value 0, MT with value 1 and T with value 0 to an STS-3c SPE with value 0, MT with value 1 and T with value 0 to an STS-3c SPE
Elementary Signal. Elementary Signal.
Mannie & Papadimitriou Editors Internet-Draft December 2002 21 E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 21
draft-ietf-ccamp-gmpls-sonet-sdh-05.txt June, 2002 draft-ietf-ccamp-gmpls-sonet-sdh-06.txt August 2002
10. An STS-1-3v SPE signal is formed by the application of RCC 10. An STS-1-3v SPE signal is formed by the application of RCC
with value 0, NVC with value 3 (virtual concatenation of 3 with value 0, NVC with value 3 (virtual concatenation of 3
components), MT with value 1 and T with value 0 to an STS-1 SPE components), MT with value 1 and T with value 0 to an STS-1 SPE
Elementary Signal. Elementary Signal.
11. An STS-3c-9v SPE signal is formed by the application of RCC 11. An STS-3c-9v SPE signal is formed by the application of RCC
with value 0, NCC with value 0, NVC with value 9 (virtual with value 0, NCC with value 0, NVC with value 9 (virtual
concatenation of 9 STS-3c), MT with value 1 and T with value 0 to concatenation of 9 STS-3c), MT with value 1 and T with value 0 to
an STS-3c SPE Elementary Signal. an STS-3c SPE Elementary Signal.
skipping to change at line 1182 skipping to change at line 1193
STM-256 MS transparent 12 0 0 0 1 2 STM-256 MS transparent 12 0 0 0 1 2
STS-1 SPE 5 0 0 0 1 0 STS-1 SPE 5 0 0 0 1 0
STS-3c SPE 6 0 0 0 1 0 STS-3c SPE 6 0 0 0 1 0
STS-48c SPE 6 1 16 0 1 0 STS-48c SPE 6 1 16 0 1 0
STS-1-3v SPE 5 0 0 3 1 0 STS-1-3v SPE 5 0 0 3 1 0
STS-3c-9v SPE 6 0 0 9 1 0 STS-3c-9v SPE 6 0 0 9 1 0
STS-12 Section transparent 9 0 0 0 1 1 STS-12 Section transparent 9 0 0 0 1 1
3 x STS-768c SPE 6 1 256 0 3 0 3 x STS-768c SPE 6 1 256 0 3 0
5 x VC-4-13v 6 0 0 13 5 0 5 x VC-4-13v 6 0 0 13 5 0
Mannie & Papadimitriou Editors Internet-Draft December 2002 22 E.Mannie & D.Papadimitriou Editors - Internet-Draft Feb. 2003 22
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/