draft-ietf-ccamp-gmpls-sonet-sdh-08.txt   rfc3946.txt 
CCAMP Working Group Eric Mannie (Consulting) - Editor Network Working Group E. Mannie
Internet Draft D. Papadimitriou (Alcatel) - Editor Request for Comments: 3946 Consultant
Category: Standards Track D. Papadimitriou
Expiration Date: August 2003 February 2003 Alcatel
October 2004
Generalized Multi-Protocol Label Switching Extensions for
SONET and SDH Control
draft-ietf-ccamp-gmpls-sonet-sdh-08.txt Generalized Multi-Protocol Label Switching (GMPLS) Extensions for
Synchronous Optical Network (SONET) and
Synchronous Digital Hierarchy (SDH) Control
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document specifies an Internet standards track protocol for the
all provisions of Section 10 of RFC2026. Internet-Drafts are Internet community, and requests discussion and suggestions for
working documents of the Internet Engineering Task Force (IETF), improvements. Please refer to the current edition of the "Internet
its areas, and its working groups. Note that other groups may Official Protocol Standards" (STD 1) for the standardization state
also distribute working documents as Internet-Drafts. and status of this protocol. Distribution of this memo is unlimited.
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 Copyright Notice
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at Copyright (C) The Internet Society (2004).
http://www.ietf.org/shadow.html
Abstract Abstract
This document is a companion to the Generalized Multi-Protocol This document is a companion to the Generalized Multi-Protocol Label
Label Switching (GMPLS) signaling. It defines the Synchronous Switching (GMPLS) signaling. It defines the Synchronous Optical
Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) Network (SONET)/Synchronous Digital Hierarchy (SDH) technology
technology specific information needed when using GMPLS signaling. specific information needed when using GMPLS signaling.
E.Mannie & D.Papadimitriou (Editors) 1 Table of Contents
1. Introduction
As described in [GMPLS-ARCH], Generalized MPLS (GMPLS) extends 1. Introduction ................................................. 2
MPLS from supporting packet (Packet Switching Capable - PSC) 2. SONET and SDH Traffic Parameters ............................. 2
interfaces and switching to include support of four new classes of 2.1. SONET/SDH Traffic Parameters ........................... 3
interfaces and switching: Layer-2 Switch Capable (L2SC), Time- 2.2. RSVP-TE Details ........................................ 9
Division Multiplex (TDM), Lambda Switch Capable (LSC) and Fiber- 2.3. CR-LDP Details ......................................... 9
Switch Capable (FSC). A functional description of the extensions 3. SONET and SDH Labels ......................................... 10
to MPLS signaling needed to support the new classes of interfaces 4. Acknowledgments .............................................. 15
and switching is provided in [RFC3471]. [RFC3473] describes RSVP- 5. Security Considerations ...................................... 16
TE specific formats and mechanisms needed to support all five 6. IANA Considerations .......................................... 16
classes of interfaces, and CR-LDP extensions can be found in 7. References ................................................... 16
[RFC3472]. This document presents details that are specific to 7.1. Normative References ................................... 16
Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy Appendix 1 - Signal Type Values Extension for VC-3 ............... 18
(SDH). Per [RFC3471], SONET/SDH specific parameters are carried in Annex 1 - Examples ............................................... 18
the signaling protocol in traffic parameter specific objects. Contributors ..................................................... 21
Authors' Addresses ............................................... 25
Full Copyright Statement ......................................... 26
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 1. Introduction
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
in this document are to be interpreted as described in [RFC2119]. As described in [RFC3945], Generalized MPLS (GMPLS) extends MPLS from
supporting packet (Packet Switching Capable - PSC) interfaces and
switching to include support of four new classes of interfaces and
switching: Layer-2 Switch Capable (L2SC), Time-Division Multiplex
(TDM), Lambda Switch Capable (LSC) and Fiber-Switch Capable (FSC). A
functional description of the extensions to MPLS signaling needed to
support the new classes of interfaces and switching is provided in
[RFC3471]. [RFC3473] describes RSVP-TE specific formats and
mechanisms needed to support all five classes of interfaces, and CR-
LDP extensions can be found in [RFC3472]. This document presents
details that are specific to Synchronous Optical Network
(SONET)/Synchronous Digital Hierarchy (SDH). Per [RFC3471],
SONET/SDH specific parameters are carried in the signaling protocol
in traffic parameter specific objects.
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].
Moreover, the reader is assumed to be familiar with the terminology Moreover, the reader is assumed to be familiar with the terminology
in ANSI [T1.105], ITU-T [G.707] as well as [RFC3471], [RFC3472] and in ANSI [T1.105], ITU-T [G.707] as well as [RFC3471], [RFC3472], and
[RFC3473]. The following abbreviations are used in this document: [RFC3473]. The following abbreviations are used in this document:
DCC: Data Communications Channel. DCC: Data Communications Channel.
LOVC: Lower Order Virtual Container LOVC: Lower Order Virtual Container
HOVC: Higher Order Virtual Container HOVC: Higher Order Virtual Container
MS: Multiplex Section. MS: Multiplex Section.
MSOH: Multiplex Section overhead. MSOH: Multiplex Section overhead.
POH: Path overhead. POH: Path overhead.
RS: Regenerator Section. RS: Regenerator Section.
RSOH: Regenerator section overhead. RSOH: Regenerator section overhead.
SDH: Synchronous digital hierarchy. SDH: Synchronous digital hierarchy.
SOH: Section overhead. SOH: Section overhead.
SONET: Synchronous Optical Network. SONET: Synchronous Optical Network.
SPE: Synchronous Payload Envelope. SPE: Synchronous Payload Envelope.
STM(-N): Synchronous Transport Module (-N) (SDH). STM(-N): Synchronous Transport Module (-N) (SDH).
STS(-N): Synchronous Transport Signal-Level N (SONET). STS(-N): Synchronous Transport Signal-Level N (SONET).
VC-n: Virtual Container-n (SDH). VC-n: Virtual Container-n (SDH).
VTn: Virtual Tributary-n (SONET). 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
The protocol specific formats, for the SONET/SDH-specific RSVP-TE protocol specific formats, for the SONET/SDH-specific RSVP-TE objects
objects and CR-LDP TLVs are described in sections 2.2 and 2.3 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
concatenation and transparency. Other documents may further and transparency. Other documents may further enhance this set of
enhance this set of capabilities in the future. For instance, capabilities in the future. For instance, signaling for SDH over PDH
ITU-T G.832 or sub-STM-0 ITU-T G.708 interfaces could be defined.
E.Mannie & D.Papadimitriou (Editors) 2
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 (see Section 2.1) MUST be The traffic parameters defined hereafter (see Section 2.1) MUST be
used when the label is encoded as SUKLM as defined in this memo used when the label is encoded as SUKLM as defined in this memo (see
(see Section 3). They MUST also be used when requesting one of Section 3). They MUST also be used when requesting one of Section/RS
Section/RS or Line/MS overhead transparent STS-1/STM-0/STS- or Line/MS overhead transparent STS-1/STM-0, STS-3*N/STM-N (N=1, 4,
3*N/STM-N (N=1, 4, 16, 64, 256) signals. 16, 64, 256) signals.
The traffic parameters and label encoding defined in [RFC3471] The traffic parameters and label encoding defined in [RFC3471],
Section 3.2 MUST be used for fully transparent STS-1/STM-0/STS- Section 3.2, MUST be used for fully transparent STS-1/STM-0,
3*N/STM-N (N=1, 4, 16, 64, 256) signal requests. A fully STS-3*N/STM-N (N=1, 4, 16, 64, 256) signal requests. A fully
transparent signal is one for which all overhead is left transparent signal is one for which all overhead is left unmodified
unmodified by intermediate nodes, i.e., when all defined by intermediate nodes, i.e., when all defined Transparency (T) bits
Transparency (T) bits would be set if the traffic parameters would be set if the traffic parameters defined in section 2.1 were
defined in section 2.1 were used. used.
2.1. SONET/SDH Traffic Parameters 2.1. SONET/SDH Traffic Parameters
The traffic parameters for SONET/SDH are 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 lists 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
comprises the requested LSP. Several transforms can be applied requested LSP. Several transforms can be applied successively on the
successively on the Elementary Signal to build the Final Signal Elementary Signal to build the Final Signal being actually requested
being actually requested for the LSP. for the LSP.
Each transform application is optional and must be ignored if
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: Each transform application is optional and must be ignored if zero,
except the Multiplier (MT) that cannot be zero and is ignored if
equal to one.
- First, contiguous concatenation (by using the RCC and NCC Transforms must be applied strictly in the following order:
fields) can be optionally applied on the Elementary Signal,
resulting in a contiguously concatenated signal.
- Second, virtual concatenation (by using the NVC field) can
be optionally applied on the Elementary Signal resulting in
a virtually concatenated signal.
E.Mannie & D.Papadimitriou (Editors) 3 - First, contiguous concatenation (by using the RCC and NCC fields)
- Third, some transparency (by using the Transparency field) can be optionally applied on the Elementary Signal, resulting in a
can be optionally specified when requesting a frame as contiguously concatenated signal.
signal rather than an SPE or VC based signal.
- Fourth, a multiplication (by using the Multiplier field) can be
optionally applied either directly on the Elementary Signal, or
on the contiguously concatenated signal obtained from the first
phase, or on the virtually concatenated signal obtained from
the second phase, or on these signals combined with some
transparency.
Permitted Signal Type values for SONET/SDH are: - Second, virtual concatenation (by using the NVC field) can be
optionally applied on the Elementary Signal resulting in a
virtually concatenated signal.
Value Type (Elementary Signal) - Third, some transparency (by using the Transparency field) can be
----- ------------------------ optionally specified when requesting a frame as signal rather than
1 VT1.5 SPE / VC-11 an SPE or VC based signal.
2 VT2 SPE / VC-12
3 VT3 SPE
4 VT6 SPE / VC-2
5 STS-1 SPE / VC-3
6 STS-3c SPE / VC-4
7 STS-1 / STM-0 (only when requesting transparency)
8 STS-3 / STM-1 (only when requesting transparency)
9 STS-12 / STM-4 (only when requesting transparency)
10 STS-48 / STM-16 (only when requesting transparency)
11 STS-192 / STM-64 (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 - Fourth, a multiplication (by using the Multiplier field) can be
of coding it as a contiguous concatenation of three STS-1 SPEs. optionally applied either directly on the Elementary Signal, or on
This is done in order to provide easy interworking between SONET the contiguously concatenated signal obtained from the first
and SDH signaling. phase, or on the virtually concatenated signal obtained from the
second phase, or on these signals combined with some transparency.
Appendix 1 adds one signal type (optional) to the above values. Permitted Signal Type values for SONET/SDH are:
Requested Contiguous Concatenation (RCC): 8 bits Value Type (Elementary Signal)
----- ------------------------
1 VT1.5 SPE / VC-11
2 VT2 SPE / VC-12
3 VT3 SPE
4 VT6 SPE / VC-2
5 STS-1 SPE / VC-3
6 STS-3c SPE / VC-4
7 STS-1 / STM-0 (only when requesting transparency)
8 STS-3 / STM-1 (only when requesting transparency)
9 STS-12 / STM-4 (only when requesting transparency)
10 STS-48 / STM-16 (only when requesting transparency)
11 STS-192 / STM-64 (only when requesting transparency)
12 STS-768 / STM-256 (only when requesting transparency)
This field is used to request the optional SONET/SDH contiguous A dedicated signal type is assigned to a SONET STS-3c SPE instead of
concatenation of the Elementary Signal. coding it as a contiguous concatenation of three STS-1 SPEs. This is
done in order to provide easy interworking between SONET and SDH
signaling.
This field is a vector of flags. Each flag indicates the Appendix 1 adds one signal type (optional) to the above values.
support of a particular type of contiguous concatenation.
Several flags can be set at the same time to indicate a choice.
These flags allow an upstream node to indicate to a downstream Requested Contiguous Concatenation (RCC): 8 bits
node the different types of contiguous concatenation that it
supports. However, the downstream node decides which one to use
according to its own rules.
A downstream node receiving simultaneously more than one flag This field is used to request the optional SONET/SDH contiguous
chooses a particular type of contiguous concatenation, if any concatenation of the Elementary Signal.
supported, and based on criteria that are out of this document
scope. A downstream node that doesnt support any of the
concatenation types indicated by the field must refuse the LSP
E.Mannie & D.Papadimitriou (Editors) 4 This field is a vector of flags. Each flag indicates the support of
request. In particular, it must refuse the LSP request if it a particular type of contiguous concatenation. Several flags can be
doesnt support contiguous concatenation at all. set at the same time to indicate a choice.
When several flags have been set, the upstream node retrieves These flags allow an upstream node to indicate to a downstream node
the (single) type of contiguous concatenation the downstream the different types of contiguous concatenation that it supports.
node has selected by looking at the position indicated by the However, the downstream node decides which one to use according to
first label and the number of label(s) as returned by the its own rules.
downstream node (see also Section 3).
The entire field is set to zero to indicate that no contiguous A downstream node receiving simultaneously more than one flag chooses
concatenation is requested at all (default value). A non-zero a particular type of contiguous concatenation, if any supported, and
field indicates that some contiguous concatenation is based on criteria that are out of this document scope. A downstream
requested. node that doesn't support any of the concatenation types indicated by
the field must refuse the LSP request. In particular, it must refuse
the LSP request if it doesn't support contiguous concatenation at
all.
The following flag is defined: When several flags have been set, the upstream node retrieves the
(single) type of contiguous concatenation the downstream node has
selected by looking at the position indicated by the first label and
the number of label(s) as returned by the downstream node (see also
Section 3).
Flag 1 (bit 1): Standard contiguous concatenation. The entire field is set to zero to indicate that no contiguous
concatenation is requested at all (default value). A non-zero field
indicates that some contiguous concatenation is requested.
Flag 1 indicates that the standard SONET/SDH contiguous The following flag is defined:
concatenation as defined in [T1.105]/[G.707] is supported. Note
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
should be ignored when received.
See note 1 hereafter in the section on the NCC about the SONET Flag 1 (bit 1): Standard contiguous concatenation.
contiguous concatenation of STS-1 SPEs when the number of
components is a multiple of three.
Number of Contiguous Components (NCC): 16 bits Flag 1 indicates that the standard SONET/SDH contiguous concatenation
as defined in [T1.105]/[G.707] is supported. Note 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 should be ignored when
received.
This field indicates the number of identical SONET SPEs/SDH VCs See note 1 hereafter in the section on the NCC about the SONET
(i.e. Elementary Signal) that are requested to be concatenated, contiguous concatenation of STS-1 SPEs when the number of components
as specified in the RCC field. is a multiple of three.
Note 1: when requesting a SONET STS-Nc SPE with N=3*X, the Number of Contiguous Components (NCC): 16 bits
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
allows also facilitating the interworking between SONET and
SDH. In particular, it means that the contiguous concatenation
of three STS-1 SPEs can not be requested because according to
this specification, this type of signal must be coded using the
STS-3c SPE signal type.
Note 2: when requesting a transparent STS-N/STM-N signal This field indicates the number of identical SONET SPEs/SDH VCs
limited to a single contiguously concatenated STS-Nc_SPE/VC-4- (i.e., Elementary Signal) that are requested to be concatenated, as
Nc, the signal type must be STS-N/STM-N, RCC with flag 1 and specified in the RCC field.
NCC set to 1.
The NCC value must be consistent with the type of contiguous Note 1: when requesting a SONET STS-Nc SPE with N=3*X, the
concatenation being requested in the RCC field. In particular, Elementary Signal to use must always be an STS-3c_SPE signal type
this field is irrelevant if no contiguous concatenation is and the value of NCC must always be equal to X. This allows also
requested (RCC = 0), in that case it must be set to zero when facilitating the interworking between SONET and SDH. In
sent, and should be ignored when received. A RCC value particular, it means that the contiguous concatenation of three
STS-1 SPEs can not be requested because according to this
specification, this type of signal must be coded using the STS-3c
SPE signal type.
E.Mannie & D.Papadimitriou (Editors) 5 Note 2: when requesting a transparent STS-N/STM-N signal
different from 0 must imply a number of contiguous components limited to a single contiguously concatenated STS-Nc_SPE/VC-4-Nc,
greater than 1. the signal type must be STS-N/STM-N, RCC with flag 1 and NCC set
to 1.
Number of Virtual Components (NVC): 16 bits 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 sent, and should be
ignored when received. A RCC value different from 0 must imply a
number of contiguous components greater than 1.
This field indicates the number of signals that are requested Number of Virtual Components (NVC): 16 bits
to be virtually concatenated. These signals are all of the same
type by definition. They are Elementary Signal SPEs/VCs for
which signal types are defined in this document, i.e.
VT1.5_SPE/VC-11, VT2_SPE/VC-12, VT3_SPE, VT6_SPE/VC-2, STS-
1_SPE/VC-3 or STS-3c_SPE/VC-4.
This field is set to 0 (default value) to indicate that no This field indicates the number of signals that are requested to be
virtual concatenation is requested. virtually concatenated. These signals are all of the same type by
definition. They are Elementary Signal SPEs/VCs for which signal
types are defined in this document, i.e., VT1.5_SPE/VC-11,
VT2_SPE/VC-12, VT3_SPE, VT6_SPE/VC-2, STS-1_SPE/VC-3 or
STS-3c_SPE/VC-4.
Multiplier (MT): 16 bits This field is set to 0 (default value) to indicate that no virtual
concatenation is requested.
This field indicates the number of identical signals that are Multiplier (MT): 16 bits
requested for the LSP, i.e. that form the Final Signal. These
signals can be either identical Elementary Signals, or
identical contiguously concatenated signals, or identical
virtually concatenated signals. Note that all these signals
belong thus to the same LSP.
The distinction between the components of multiple virtually This field indicates the number of identical signals that are
concatenated signals is done via the order of the labels that requested for the LSP, i.e., that form the Final Signal. These
are specified in the signaling. The first set of labels must signals can be either identical Elementary Signals, or identical
describe the first component (set of individual signals contiguously concatenated signals, or identical virtually
belonging to the first virtual concatenated signal), the second concatenated signals. Note that all these signals belong thus to the
set must describe the second component (set of individual same LSP.
signals belonging to the second virtual concatenated signal)
and so on.
This field is set to one (default value) to indicate that exactly The distinction between the components of multiple virtually
one instance of a signal is being requested. Intermediate and concatenated signals is done via the order of the labels that are
egress nodes MUST verify that the node itself and the interfaces specified in the signaling. The first set of labels must describe
on which the LSP will be established can support the requested the first component (set of individual signals belonging to the first
multiplier value. If the requested values can not be supported, virtual concatenated signal), the second set must describe the second
the receiver node MUST generate a PathErr/NOTIFICATION message component (set of individual signals belonging to the second virtual
(see Section 2.2/2.3, respectively). concatenated signal) and so on.
Zero is an invalid value. If received, the node MUST generate a This field is set to one (default value) to indicate that exactly one
PathErr/NOTIFICATION message (see Section 2.2/2.3, respectively). instance of a signal is being 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 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).
Note 1: when requesting a transparent STS-N/STM-N signal limited Zero is an invalid value. If received, the node MUST generate a
to a single contiguously concatenated STS-Nc-SPE/VC-4-Nc, the PathErr/NOTIFICATION message (see Section 2.2/2.3, respectively).
multiplier field MUST be equal to 1 (only valid value).
Transparency (T): 32 bits 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).
This field is a vector of flags that indicates the type of Transparency (T): 32 bits
transparency being requested. Several flags can be combined to
provide different types of transparency. Not all combinations
E.Mannie & D.Papadimitriou (Editors) 6 This field is a vector of flags that indicates the type of
are necessarily valid. The default value for this field is transparency being requested. Several flags can be combined to
zero, i.e. no transparency requested. provide different types of transparency. Not all combinations are
necessarily valid. The default value for this field is 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
signaling specification, is only applicable to the fields in specification, is only applicable to the fields in the SONET/SDH
the SONET/SDH frame overheads. In the SONET case, these are the frame overheads. In the SONET case, these are the fields in the
fields in the Section Overhead (SOH), and the Line Overhead Section Overhead (SOH), and the Line Overhead (LOH). In the SDH
(LOH). In the SDH case, these are the fields in the Regenerator case, these are the fields in the Regenerator Section Overhead
Section Overhead (RSOH), the Multiplex Section overhead (MSOH), (RSOH), the Multiplex Section overhead (MSOH), and the pointer fields
and the pointer fields between the two. With SONET, the pointer between the two. With SONET, the pointer fields are part of the LOH.
fields are part of the LOH.
Note as well that transparency is only applicable when using Note as well that transparency is only applicable when using the
the following Signal Types: STS-1/STM-0, STS-3/STM-1, STS-12/ following Signal Types: STS-1/STM-0, STS-3/STM-1, STS-12/STM-4,
STM-4, STS-48/STM-16, STS-192/STM-64 and STS-768/STM-256. At STS-48/STM-16, STS-192/STM-64 and STS-768/STM-256. At least one
least one transparency type must be specified when requesting transparency type must be specified when requesting such a signal
such a signal type. type.
Transparency indicates precisely which fields in these Transparency indicates precisely which fields in these overheads must
overheads must be delivered unmodified at the other end of the be delivered unmodified at the other end of the LSP. An ingress LSR
LSP. An ingress LSR requesting transparency will pass these requesting transparency will pass these overhead fields that must be
overhead fields that must be delivered to the egress LSR delivered to the egress LSR without any change. From the ingress and
without any change. From the ingress and egress LSRs point of 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
initiating and terminating LSRs, but is only applied between 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
the requested transparency type; it may also be used to setup requested transparency type; it may also be used to setup the
the transparency process to be applied at each intermediate 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. Other flags are reserved, they Where bit 1 is the low order bit. Other flags are reserved, they
should be set to zero when sent, and should be ignored when should be set to zero when sent, and should be ignored when received.
received. A flag is set to one to indicate that the corresponding A flag is set to one to indicate that the corresponding transparency
transparency is requested. is requested.
Intermediate and egress nodes MUST verify that the node itself and Intermediate and egress nodes MUST verify that the node itself and
the interfaces on which the LSP will be established can support the interfaces on which the LSP will be established can support the
the requested transparency. If the requested flags can not be requested transparency. If the requested flags can not be supported,
supported, the receiver node MUST generate a PathErr/NOTIFICATION the receiver node MUST generate a PathErr/NOTIFICATION message (see
message (see Section 2.2/2.3, respectively). Section 2.2/2.3, respectively).
Section/Regenerator Section layer transparency means that the Section/Regenerator Section layer transparency means that the entire
entire frames must be delivered unmodified. This implies that frames must be delivered unmodified. This implies that pointers
pointers cannot be adjusted. When using Section/Regenerator cannot be adjusted. When using Section/Regenerator Section layer
Section layer transparency all other flags MUST be ignored. transparency all other flags MUST be ignored.
E.Mannie & D.Papadimitriou (Editors) 7 Line/Multiplex Section layer transparency means that the LOH/MSOH
Line/Multiplex Section layer transparency means that the must be delivered unmodified. This implies that pointers cannot be
LOH/MSOH must be delivered unmodified. This implies that adjusted.
pointers cannot be adjusted.
Profile (P): 32 bits Profile (P): 32 bits
This field is intended to indicate particular capabilities that This field is intended to indicate particular capabilities that must
must be supported for the LSP, for example monitoring be supported for the LSP, for example monitoring capabilities.
capabilities.
No standard profile is currently defined and this field SHOULD No standard profile is currently defined and this field SHOULD be set
be set to zero when transmitted and SHOULD be ignored when to zero when transmitted and SHOULD be ignored when received.
received.
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
used both for SENDER_TSPEC object and FLOWSPEC objects. The both for SENDER_TSPEC object and FLOWSPEC objects. The content of
content of the objects is defined above in Section 2.1. The the objects is defined above in Section 2.1. The objects have the
objects have the following class and type: following class and type:
For SONET ANSI T1.105 and SDH ITU-T G.707: For SONET ANSI T1.105 and SDH ITU-T G.707:
SONET/SDH SENDER_TSPEC object: Class = 12, C-Type = TBA (by IANA) SONET/SDH SENDER_TSPEC object: Class = 12, C-Type = 4
SONET/SDH FLOWSPEC object: Class = 9, C-Type = TBA (by IANA) SONET/SDH FLOWSPEC object: Class = 9, C-Type = 4
There is no Adspec associated with the SONET/SDH SENDER_TSPEC. There is no Adspec associated with the SONET/SDH SENDER_TSPEC.
Either the Adspec is omitted or an int-serv Adspec with the Either the Adspec is omitted or an int-serv Adspec with the Default
Default General Characterization Parameters and Guaranteed Service General Characterization Parameters and Guaranteed Service fragment
fragment is used, see [RFC2210]. 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
contents of the SENDER_TSPEC object received in the corresponding of the SENDER_TSPEC object received in the corresponding Path
Path message. If the objects do not match, a ResvErr message with message. If the objects do not match, a ResvErr message with a
a "Traffic Control Error/Bad Flowspec value" error SHOULD be "Traffic Control Error/Bad Flowspec value" error SHOULD be generated.
generated.
Intermediate and egress nodes MUST verify that the node itself and Intermediate and egress nodes MUST verify that the node itself and
the interfaces on which the LSP will be established can support the interfaces on which the LSP will be established can support the
the requested Signal Type, RCC, NCC, NVC and Multiplier (as requested Signal Type, RCC, NCC, NVC and Multiplier (as defined in
defined in Section 2.1). If the requested value(s) can not be Section 2.1). If the requested value(s) can not be supported, the
supported, the receiver node MUST generate a PathErr message with receiver node MUST generate a PathErr message with a "Traffic Control
a "Traffic Control Error/ Service unsupported" indication (see Error/ Service unsupported" indication (see [RFC2205]).
[RFC2205]).
In addition, if the MT field is received with a zero value, the In addition, if the MT field is received with a zero value, the node
node MUST generate a PathErr message with a "Traffic Control MUST generate a PathErr message with a "Traffic Control Error/Bad
Error/Bad Tspec value" indication (see [RFC2205]). Tspec value" indication (see [RFC2205]).
E.Mannie & D.Papadimitriou (Editors) 8
Intermediate nodes MUST also verify that the node itself and the Intermediate nodes MUST also verify that the node itself and the
interfaces on which the LSP will be established can support the interfaces on which the LSP will be established can support the
requested Transparency (as defined in Section 2.1). If the requested Transparency (as defined in Section 2.1). If the requested
requested value(s) can not be supported, the receiver node MUST value(s) can not be supported, the receiver node MUST generate a
generate a PathErr message with a "Traffic Control Error/Service PathErr message with a "Traffic Control Error/Service unsupported"
unsupported" indication (see [RFC2205]). 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 defined
defined above in Section 2.1. The header of the TLV has the above in Section 2.1. The header of the TLV has the following
following format: 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: 0x0838.
(by IANA).
Intermediate and egress nodes MUST verify that the node itself and Intermediate and egress nodes MUST verify that the node itself and
the interfaces on which the LSP will be established can support the interfaces on which the LSP will be established can support the
the requested Signal Type, RCC, NCC, NVC and Multiplier (as requested Signal Type, RCC, NCC, NVC and Multiplier (as defined in
defined in Section 2.1). If the requested value(s) can not be Section 2.1). If the requested value(s) can not be supported, the
supported, the receiver node MUST generate a NOTIFICATION message receiver node MUST generate a NOTIFICATION message with a "Resource
with a "Resource Unavailable" status code (see [RFC3212]).
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]). Unavailable" status code (see [RFC3212]).
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]).
Intermediate nodes MUST also verify that the node itself and the Intermediate nodes MUST also verify that the node itself and the
interfaces on which the LSP will be established can support the interfaces on which the LSP will be established can support the
requested Transparency (as defined in Section 2.1). If the requested Transparency (as defined in Section 2.1). If the requested
requested value(s) can not be supported, the receiver node MUST value(s) can not be supported, the receiver node MUST generate a
generate a NOTIFICATION message with a "Resource Unavailable" NOTIFICATION message with a "Resource Unavailable" status code (see
status code (see [RFC3212]). [RFC3212]).
3. SONET and SDH Labels 3. SONET and SDH Labels
SONET and SDH each define a multiplexing structure. Both SONET and SDH each define a multiplexing structure. Both structures
structures are trees whose roots are respectively an STS-N or an are trees whose roots are respectively an STS-N or an STM-N; and
STM-N; and whose leaves are the signals that can be transported whose leaves are the signals that can be transported via the time-
via the time-slots and switched between time-slots within an slots and switched between time-slots within an ingress port and
ingress port and time-slots within an egress port, i.e. a VTx SPE, time-slots within an egress port, i.e., a VTx SPE, an STS-x SPE or a
an STS-x SPE or a VC-x. A SONET/SDH label will identify the exact VC-x. A SONET/SDH label will identify the exact position (i.e.,
position (i.e. first time-slot) of a particular VTx SPE, STS-x SPE first time-slot) of a particular VTx SPE, STS-x SPE or VC-x signal in
or VC-x signal in a multiplexing structure. SONET and SDH labels a multiplexing structure. SONET and SDH labels are carried in the
are carried in the Generalized Label per [RFC3473] and [RFC3472]. Generalized Label per [RFC3473] and [RFC3472].
E.Mannie & D.Papadimitriou (Editors) 9
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
after any possible interleaving. any possible interleaving.
These multiplexing structures will be used as naming trees to These multiplexing structures will be used as naming trees to create
create unique multiplex entry names or labels. The same format of unique multiplex entry names or labels. The same format of label is
label is used for SONET and SDH. As explained in [RFC3471], a used for SONET and SDH. As explained in [RFC3471], a label does not
label does not identify the "class" to which the label belongs. identify the "class" to which the label belongs. This is implicitly
This is implicitly determined by the link on which the label is determined by the link on which the label is used.
used.
In case of signal concatenation or multiplication, a list of In case of signal concatenation or multiplication, a list of labels
labels can appear in the Label field of a Generalized Label. 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
by the contiguously concatenated signal. By lowest time-slot we the contiguously concatenated signal. By lowest time-slot we mean
mean the one having the lowest label (value) when compared as the one having the lowest label (value) when compared as integer
integer values, i.e. the time-slot occupied by the first component values, i.e., the time-slot occupied by the first component signal of
signal of the concatenated signal encountered when descending the the concatenated signal encountered when descending the tree.
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
first time-slot occupied by a component of the virtually time-slot occupied by a component of the virtually concatenated
concatenated signal. The order of the labels must reflect the signal. The order of the labels must reflect the order of the
order of the payloads to concatenate (not the physical order of payloads to concatenate (not the physical order of time-slots). The
time-slots). The above representation limits virtual concatenation above representation limits virtual concatenation to remain within a
to remain within a single (component) link; it imposes as such a single (component) link; it imposes as such a restriction compared to
restriction compared to the ANSI [T1.105]/ITU-T [G.707] the ANSI [T1.105]/ITU-T [G.707] recommendations.
recommendations.
The standard definition for virtual concatenation allows each The standard definition for virtual concatenation allows each virtual
virtual concatenation components to travel over diverse paths. concatenation components to travel over diverse paths. Within GMPLS,
Within GMPLS, virtual concatenation components must travel over virtual concatenation components must travel over the same
the same (component) link if they are part of the same LSP. This (component) link if they are part of the same LSP. This is due to
is due to the way that labels are bound to a (component) link. the way that labels are bound to a (component) link. Note however,
Note however, that the routing of components on different paths is that the routing of components on different paths is indeed
indeed equivalent to establishing different LSPs, each one having equivalent to establishing different LSPs, each one having its own
its own route. Several LSPs can be initiated and terminated route. Several LSPs can be initiated and terminated between the same
between the same nodes and their corresponding components can then nodes and their corresponding components can then be associated
be associated together (i.e. virtually concatenated). 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
the explicit ordered list of all labels that take part in the explicit ordered list of all labels that take part in the Final
Final Signal is given. In case of multiplication of virtually Signal is given. In case of multiplication of virtually concatenated
concatenated signals, the first set of labels indicates the time- signals, the first set of labels indicates the time-slots occupied by
slots occupied by the first virtually concatenated signal, the the first virtually concatenated signal, the second set of labels
second set of labels indicates the time-slots occupied by the indicates the time-slots occupied by the second virtually
second virtually concatenated signal, and so on. The above concatenated signal, and so on. The above representation limits
representation limits multiplication to remain within a single multiplication to remain within a single (component) link.
(component) link.
The format of the label for SONET and/or SDH TDM-LSR link is: The format of the label for SONET and/or SDH TDM-LSR link is:
E.Mannie & D.Papadimitriou (Editors) 10
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 the higher order numbering scheme defined in [G.707] sections 7.3.1
7.3.1 to 7.3.6 is not used here. to 7.3.6 is not used here.
Each letter indicates a possible branch number starting at the Each letter indicates a possible branch number starting at the parent
parent node in the multiplex structure. Branches are considered as node in the multiplex structure. Branches are considered as numbered
numbered in increasing order, starting from the top of the in increasing order, starting from the top of the multiplexing
multiplexing structure. The numbering starts at 1, zero is used to structure. The numbering starts at 1, zero is used to indicate a
indicate a non-significant or ignored field. 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
it MUST be set to zero when transmitted, and MUST be ignored when MUST be set to zero when transmitted, and MUST be ignored when
received. received.
When a hierarchy of SONET/SDH LSPs is used, a higher order LSP When a hierarchy of SONET/SDH LSPs is used, a higher order LSP with a
with a given bandwidth can be used to carry lower order LSPs. given bandwidth can be used to carry lower order LSPs. Remember here
Remember here that a higher order LSP is established through a that a higher order LSP is established through a SONET/SDH higher
SONET/SDH higher order path layer network and a lower order LSP, order path layer network and a lower order LSP, through a SONET/SDH
through a SONET/SDH lower order path layer network (see also ITU-T lower order path layer network (see also ITU-T G.803, Section 3 for
G.803, Section 3 for the corresponding definitions). In this the corresponding definitions). In this context, the higher order
context, the higher order SONET/SDH LSP behaves as a "virtual SONET/SDH LSP behaves as a "virtual link" with a given bandwidth
link" with a given bandwidth (e.g. VC-3), it may also be used as a (e.g., VC-3), it may also be used as a Forwarding Adjacency. A lower
Forwarding Adjacency. A lower order SONET/SDH LSP can be order SONET/SDH LSP can be established through that higher order LSP.
established through that higher order LSP. Since a label is local Since a label is local to a (virtual) link, the highest part of that
to a (virtual) link, the highest part of that label (i.e. the S, U label (i.e., the S, U and K fields) is non-significant and is set to
and K fields) is non-significant and is set to zero, i.e. the zero, i.e., the label is "0,0,0,L,M". Similarly, if the structure of
label is "0,0,0,L,M". Similarly, if the structure of the lower the lower order LSP is unknown or not relevant, the lowest part of
order LSP is unknown or not relevant, the lowest part of that that label (i.e., the L and M fields) is non-significant and is set
label (i.e. the L and M fields) is non-significant and is set to to zero, i.e., the label is "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
LSP for the lower order LSPs will have S, U and K set to zero, for the lower order LSPs will have S, U and K set to zero, i.e.,
i.e., non-significant, while L and M will be used to indicate the non-significant, while L and M will be used to indicate the signal
signal allocated in that VC-3. allocated in that VC-3.
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
12/VC-11 where the SUKLM structure is not adequate to represent VC-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 STS-3/AUG-1 inside an 1. S=1->N is the index of a particular STS-3/AUG-1 inside an
STS-N/STM-N multiplex. S is only significant for SONET STS-N STS-N/STM-N multiplex. S is only significant for SONET STS-N
(N>1) and SDH STM-N (N>0). S must be 0 and ignored for STS-1 and
E.Mannie & D.Papadimitriou (Editors) 11 STM-0.
(N>1) and SDH STM-N (N>0). S must be 0 and ignored for STS-1 and
STM-0.
2. U=1->3 is the index of a particular STS-1_SPE/VC-3 within an 2. U=1->3 is the index of a particular STS-1_SPE/VC-3 within an
STS-3/AUG-1. U is only significant for SONET STS-N (N>1) and SDH STS-3/AUG-1. U is only significant for SONET STS-N (N>1) and SDH
STM-N (N>0). U must be 0 and ignored for STS-1 and STM-0. 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. K must be only significant for an SDH VC-4 structured in TUG-3s. K must 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 VT_Group/TUG-2 within an 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 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 VT1.5_SPE/VC-11, VT2_SPE/VC-12 5. M is the index of a particular VT1.5_SPE/VC-11, VT2_SPE/VC-12 or
or VT3_SPE within a VT_Group/TUG-2. M=1->2 indicates a specific VT3_SPE within a VT_Group/TUG-2. M=1->2 indicates a specific VT3
VT3 SPE inside the corresponding VT Group, these values MUST NOT SPE inside the corresponding VT Group, these values MUST NOT be
be used for SDH since there is no equivalent of VT3 with SDH. used for SDH since there is no equivalent of VT3 with SDH. M=3->5
M=3->5 indicates a specific VT2_SPE/VC-12 inside the indicates a specific VT2_SPE/VC-12 inside the corresponding
corresponding VT_Group/TUG-2. M=6->9 indicates a specific VT_Group/TUG-2. M=6->9 indicates a specific VT1.5_SPE/VC-11
VT1.5_SPE/VC-11 inside the corresponding VT_Group/TUG-2. 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
SONET/SDH traffic parameters, i.e. a label by itself does not SONET/SDH traffic parameters, i.e., a label by itself does not allow
allow knowing which signal is being requested (a label is context knowing which signal is being requested (a label is context
sensitive). sensitive).
The label format defined in this section, referred to as SUKLM, The label format defined in this section, referred to as SUKLM, MUST
MUST be used for any SONET/SDH signal requests that are not be used for any SONET/SDH signal requests that are not transparent
transparent i.e. when all Transparency (T) bits defined in section i.e., when all Transparency (T) bits defined in section 2.1 are set
2.1 are set to zero. Any transparent STS-1/STM-0/STS-3*N/STM-N to zero. Any transparent STS-1/STM-0/STS-3*N/STM-N (N=1, 4, 16, 64,
(N=1, 4, 16, 64, 256) signal request MUST use a label format as 256) signal request MUST use a label format as defined in [RFC3471].
defined in [RFC3471].
The S encoding is summarized in the following table:
S SDH SONET The S encoding is summarized in the following table:
------------------------------------------------
0 other other
1 1st AUG-1 1st STS-3
2 2nd AUG-1 2nd STS-3
3 3rd AUG-1 3rd STS-3
4 4rd AUG-1 4rd STS-3
: : :
N Nth AUG-1 Nth STS-3
The U encoding is summarized in the following table: S SDH SONET
------------------------------------------------
0 other other
1 1st AUG-1 1st STS-3
2 2nd AUG-1 2nd STS-3
3 3rd AUG-1 3rd STS-3
4 4rd AUG-1 4rd STS-3
: : :
N Nth AUG-1 Nth STS-3
U SDH AUG-1 SONET STS-3 The U encoding is summarized in the following table:
-------------------------------------------------
0 other other
1 1st VC-3 1st STS-1 SPE
2 2nd VC-3 2nd STS-1 SPE
E.Mannie & D.Papadimitriou (Editors) 12 U SDH AUG-1 SONET STS-3
3 3rd VC-3 3rd STS-1 SPE -------------------------------------------------
0 other other
1 1st VC-3 1st STS-1 SPE
2 2nd VC-3 2nd 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:
K SDH VC-4 K SDH VC-4
--------------- ---------------
0 other 0 other
1 1st TUG-3 1 1st TUG-3
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
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 VT3 SPE 1 - 1st VT3 SPE
2 - 2nd VT3 SPE 2 - 2nd VT3 SPE
3 1st VC-12 1st VT2 SPE 3 1st VC-12 1st VT2 SPE
4 2nd VC-12 2nd VT2 SPE 4 2nd VC-12 2nd VT2 SPE
5 3rd VC-12 3rd VT2 SPE 5 3rd VC-12 3rd VT2 SPE
6 1st VC-11 1st VT1.5 SPE 6 1st VC-11 1st VT1.5 SPE
7 2nd VC-11 2nd VT1.5 SPE 7 2nd VC-11 2nd VT1.5 SPE
8 3rd VC-11 3rd VT1.5 SPE 8 3rd VC-11 3rd VT1.5 SPE
9 4th VC-11 4th VT1.5 SPE 9 4th VC-11 4th VT1.5 SPE
Examples of labels: Examples of labels:
Example 1: the label for the STS-3c_SPE/VC-4 in the Sth STS-3/AUG- Example 1: the label for the STS-3c_SPE/VC-4 in the Sth STS-3/AUG-1
1 is: S>0, U=0, K=0, L=0, M=0. 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.
Example 3: the label for the Uth-1 STS-1_SPE/VC-3 within the Sth Example 3: the label for 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. STS-3/AUG-1 is: S>0, U>0, K=0, L=0, M=0.
Example 4: the label for the VT6/VC-2 in the Lth-1 VT Group/TUG-2 Example 4: the label for the VT6/VC-2 in the Lth-1 VT Group/TUG-2
in the Uth-1 STS-1_SPE/VC-3 within the Sth STS-3/AUG-1 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.
E.Mannie & D.Papadimitriou (Editors) 13
Example 5: the label for the 3rd VT1.5_SPE/VC-11 in the Lth-1 VT Example 5: the label for the 3rd VT1.5_SPE/VC-11 in the Lth-1 VT
Group/TUG-2 within the Uth-1 STS-1_SPE/VC-3 within the Sth STS- Group/TUG-2 within 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=8. 3/AUG-1 is: S>0, U>0, K=0, L>0, M=8.
Example 6: the label for the STS-12c/VC-4-4c which uses the 9th Example 6: the label for the STS-12c/VC-4-4c which uses the 9th
STS-3/AUG-1 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 (value) of the contiguously concatenated signal as lowest label (value) of the contiguously concatenated signal as
explained before. The higher part of the label indicates where the explained before. The higher part of the label indicates where the
signal 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.
M=0. When requesting a VC-11 in a VC-3 in an STM-0 the label is When requesting a VC-11 in a VC-3 in an STM-0 the label is S=0, U=0,
S=0, U=0, K=0, L>0, M=6..9. K=0, L>0, M=6..9.
Note: when a Section/RS or Line/MS transparent STS-1/STM-0/STS- Note: when a Section/RS or Line/MS transparent STS-1/STM-0/STS-
3*N/STM-N (N=1, 4, 16, 64, 256) signal is requested, the SUKLM 3*N/STM-N (N=1, 4, 16, 64, 256) signal is requested, the SUKLM label
label format and encoding is not applicable and the label encoding format and encoding is not applicable and the label encoding MUST
MUST follow the rules defined in [RFC3471] Section 3.2. follow the rules defined in [RFC3471] Section 3.2.
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
list where outstanding discussions took place. where outstanding discussions took place.
5. Security Considerations 5. Security Considerations
This draft introduces no new security considerations to either This document introduces no new security considerations to either
[RFC3473] or [RFC3472]. GMPLS security is described in section 11 [RFC3473] or [RFC3472]. GMPLS security is described in section 11 of
of [RFC3471] and refers to [RFC3209] for RSVP-TE and to [RFC3212] [RFC3471] and refers to [RFC3209] for RSVP-TE and to [RFC3212] for
for CR-LDP. CR-LDP.
6. IANA Considerations 6. IANA Considerations
Three values have to be defined by IANA for this document: Three values have been defined by IANA for this document:
Two RSVP C-Types in registry: Two RSVP C-Types in registry:
http://www.iana.org/assignments/rsvp-parameters http://www.iana.org/assignments/rsvp-parameters
- A SONET/SDH SENDER_TSPEC object: Class = 12, C-Type = TBA - A SONET/SDH SENDER_TSPEC object: Class = 12, C-Type = 4 (see
(see section 2.2). section 2.2).
- A SONET/SDH FLOWSPEC object: Class = 9, C-Type = TBA (see - A SONET/SDH FLOWSPEC object: Class = 9, C-Type = 4 (see section
section 2.2). 2.2).
One LDP TLV Type in registry: One LDP TLV Type in registry:
http://www.iana.org/assignments/ldp-namespaces http://www.iana.org/assignments/ldp-namespaces
- A type field for the SONET/SDH Traffic Parameters TLV
(see section 2.3).
E.Mannie & D.Papadimitriou (Editors) 14
7. Intellectual Property Notice
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances
of licenses to be made available, or the result of an attempt made
to obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification
can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
8. References - A type field for the SONET/SDH Traffic Parameters TLV (see section
2.3).
8.1 Normative References 7. References
[G.707] ITU-T Recommendation G.707, "Network Node Interface 7.1. Normative References
for the Synchronous Digital Hierarchy", October 2000.
[GMPLS-ARCH] Mannie, E., Papadimitriou D., et al., "Generalized [G.707] ITU-T Recommendation G.707, "Network Node Interface for
Multiprotocol Label Switching Architecture", Internet the Synchronous Digital Hierarchy", October 2000.
Draft, Work in progress, draft-ietf-ccamp-gmpls-
architecture-03.txt, August 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", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2205] Braden, R., et al., "Resource ReSerVation Protocol [RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S.
(RSVP) -- Version 1 Functional Specification", RFC Jamin, "Resource ReSerVation Protocol (RSVP) -- Version
2205, September 1997. 1 Functional Specification", RFC 2205, September 1997.
[RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated [RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated
Services," RFC 2210, September 1997. Services", RFC 2210, September 1997.
[RFC3209] Awduche, D., et al., "RSVP-TE: Extensions to RSVP for
LSP Tunnels", RFC 3209, December 2001.
[RFC3212] Jamoussi, B., et al., "Constraint-Based LSP Setup using [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan,
LDP", RFC 3212, January 2002. V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, December 2001.
[RFC3471] Berger, L. (Editor), et al., "Generalized MPLS [RFC3212] Jamoussi, B., Andersson, L., Callon, R., Dantu, R., Wu,
Signaling Functional Description", RFC 3471, January L., Doolan, P., Worster, T., Feldman, N., Fredette, A.,
2003. Girish, M., Gray, E., Heinanen, J., Kilty, T., and A.
Malis, "Constraint-Based LSP Setup using LDP", RFC 3212,
January 2002.
E.Mannie & D.Papadimitriou (Editors) 15 [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(MPLS) Signaling Functional Description", RFC 3471,
January 2003.
[RFC3472] Berger, L. (Editor), et al., "Generalized MPLS [RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized
Signaling - CR-LDP Extensions", RFC 3472, January Multi-Protocol Label Switching (MPLS) Signaling
2003. - Constraint-based Routed Label Distribution Protocol
(CR-LDP) Extensions", RFC 3472, January 2003.
[RFC3473] Berger, L. (Editor), et al., "Generalized MPLS [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching
Signaling - RSVP-TE Extensions", RFC 3473, January (MPLS) Signaling - Resource ReserVation Protocol Traffic
Engineering (RSVP-TE) Extensions", RFC 3473, January
2003. 2003.
[T1.105] "Synchronous Optical Network (SONET): Basic [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label
Description Including Multiplex Structure, Rates, and Switching (GMPLS) Architecture", RFC 3945, October 2004.
Formats", ANSI T1.105, October 2000.
9. Authors Addresses
Eric Mannie (Consulting)
Phone: +32 2 648-5023
Mobile: +32 (0)495-221775
Email: eric_mannie@hotmail.com
Dimitri Papadimitriou (Alcatel)
Francis Wellesplein 1,
B-2018 Antwerpen, Belgium
Phone: +32 3 240-8491
Email: dimitri.papadimitriou@alcatel.be
10. Contributors
Contributors are listed by alphabetical order:
Stefan Ansorge (Alcatel) Peter Ashwood-Smith (Nortel)
Lorenzstrasse 10 PO. Box 3511 Station C,
70435 Stuttgart, Germany Ottawa, ON K1Y 4H7, Canada
Email: stefan.ansorge@alcatel.de Email:petera@nortelnetworks.com
Ayan Banerjee (Calient) Lou Berger (Movaz)
5853 Rue Ferrari 7926 Jones Branch Drive
San Jose, CA 95138, USA McLean, VA 22102, USA
Email: abanerjee@calient.net Email: lberger@movaz.com
Greg Bernstein (Ciena) Angela Chiu (Celion)
10480 Ridgeview Court One Sheila Drive, Suite 2
Cupertino, CA 94014, USA Tinton Falls, NJ 07724-2658
Email: greg@ciena.com Email: angela.chiu@celion.com
John Drake (Calient) Yanhe Fan (Axiowave)
5853 Rue Ferrari 100 Nickerson Road
San Jose, CA 95138, USA Marlborough, MA 01752, USA
Email: jdrake@calient.net Email: yfan@axiowave.com
Michele Fontana (Alcatel) Gert Grammel (Alcatel)
Via Trento 30, Lorenzstrasse, 10
I-20059 Vimercate, Italy 70435 Stuttgart, Germany
Email: michele.fontana@alcatel.it Email: gert.grammel@alcatel.de
E.Mannie & D.Papadimitriou (Editors) 16
Juergen Heiles (Siemens) Suresh Katukam (Cisco)
Hofmannstr. 51 1450 N. McDowell Blvd,
D-81379 Munich, Germany Petaluma, CA 94954-6515, USA
Email: juergen.heiles@siemens.com Email: suresh.katukam@cisco.com
Kireeti Kompella (Juniper) Jonathan P. Lang (Calient)
1194 N. Mathilda Ave. 25 Castilian
Sunnyvale, CA 94089, USA Goleta, CA 93117, USA
Email: kireeti@juniper.net Email: jplang@calient.net
Fong Liaw (Solas Research) Zhi-Wei Lin (Lucent)
Email: fongliaw@yahoo.com 101 Crawfords Corner Rd
Holmdel, NJ 07733-3030, USA
Email: zwlin@lucent.com
Ben Mack-Crane (Tellabs) Dimitrios Pendarakis (Tellium)
Email: ben.mack-crane@tellabs.com 2 Crescent Place, P.O. Box 901
Oceanport, NJ 07757-0901, USA
Email: dpendarakis@tellium.com
Mike Raftelis (White Rock) Bala Rajagopalan (Tellium)
18111 Preston Road 2 Crescent Place, P.O. Box 901
Dallas, TX 75252, USA Oceanport, NJ 07757-0901, USA
Email: braja@tellium.com
Yakov Rekhter (Juniper) Debanjan Saha (Tellium)
1194 N. Mathilda Ave. 2 Crescent Place, P.O. Box 901
Sunnyvale, CA 94089, USA Oceanport, NJ 07757-0901, USA
Email: yakov@juniper.net Email: dsaha@tellium.com
Vishal Sharma (Metanoia) George Swallow (Cisco)
335 Elan Village Lane 250 Apollo Drive
San Jose, CA 95134, USA Chelmsford, MA 01824, USA
Email: vsharma87@yahoo.com Email: swallow@cisco.com
Z. Bo Tang (Tellium) Eve Varma (Lucent)
2 Crescent Place, P.O. Box 901 101 Crawfords Corner Rd
Oceanport, NJ 07757-0901, USA Holmdel, NJ 07733-3030, USA
Email: btang@tellium.com 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) 17
11. Full Copyright Statement
"Copyright (C) The Internet Society (date). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an [T1.105] "Synchronous Optical Network (SONET): Basic Description
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING Including Multiplex Structure, Rates, and Formats", ANSI
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING T1.105, October 2000.
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."
E.Mannie & D.Papadimitriou (Editors) 18
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
Type value for the Signal Type field of section 2.1: 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 ITU-T [G.707] recommendation a VC-3 in the TU- According to the ITU-T [G.707] recommendation a VC-3 in the TU-
3/TUG-3/VC-4/AU-4 branch of the SDH multiplex cannot be structured 3/TUG-3/VC-4/AU-4 branch of the SDH multiplex cannot be structured in
in TUG-2s, however a VC-3 in the AU-3 branch can be. In addition, TUG-2s, however a VC-3 in the AU-3 branch can be. In addition, a VC-3
a VC-3 could be switched between the two branches if required. 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
LSR (e.g. forming a VC-3 forwarding adjacency). This LSR could (e.g., forming a VC-3 forwarding adjacency). This LSR could then want
then want to demultiplex this VC-3 and switch internal low order to demultiplex this VC-3 and switch internal low order LSPs. For
LSPs. For implementation reasons, this could be only possible if implementation reasons, this could be only possible if the LSR
the LSR receives the VC-3 in the AU-3 branch. E.g. for an LSR not receives the VC-3 in the AU-3 branch. E.g., for an LSR not able to
able to switch internally from a TU-3 branch to an AU-3 branch on switch internally from a TU-3 branch to an AU-3 branch on its
its incoming interface before demultiplexing and then switching incoming interface before demultiplexing and then switching the
the content with its switch fabric. content with its switch fabric.
In that case it is useful to indicate that the VC-3 LSP must be In that case it is useful to indicate that the VC-3 LSP must be
terminated at the end in the AU-3 branch instead of the TU-3 terminated at the end in the AU-3 branch instead of the TU-3 branch.
branch.
This is achieved by using the "VC-3 via AU-3 at the end" signal This is achieved by using the "VC-3 via AU-3 at the end" signal type.
type. This information can be used, for instance, by the This information can be used, for instance, by the penultimate LSR to
penultimate LSR to switch an incoming VC-3 received in any branch switch an incoming VC-3 received in any branch to the AU-3 branch on
to the AU-3 branch on the outgoing interface to the destination 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
the network. The VC-3 signal type just indicates that a VC-3 in network. The VC-3 signal type just indicates that a VC-3 in any
any branch is suitable. branch is suitable.
E.Mannie & D.Papadimitriou (Editors) 19
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
transforms can be applied to obtain Final Signals. 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
components), MT with value 1 and T with value 0 to a VC-4 7 components), MT with value 1 and T with value 0 to a VC-4
Elementary Signal. Elementary Signal.
3. A VC-4-16c signal is formed by the application of RCC with flag 3. A VC-4-16c signal is formed by the application of RCC with flag
1 (standard contiguous concatenation), NCC with value 16, NVC with 1 (standard contiguous concatenation), NCC with value 16, NVC
value 0, MT with value 1 and T with value 0 to a VC-4 Elementary with value 0, MT with value 1 and T with value 0 to a VC-4
Signal. Elementary Signal.
4. An STM-16 signal with Multiplex Section layer transparency is 4. An STM-16 signal with Multiplex Section layer transparency is
formed by the application of RCC with value 0, NCC with value 0, formed by the application of RCC with value 0, NCC with value 0,
NVC with value 0, MT with value 1 and T with flag 2 to an STM-16 NVC with value 0, MT with value 1 and T with flag 2 to an STM-16
Elementary Signal. Elementary Signal.
5. An STM-4 signal with Multiplex Section layer transparency is 5. An STM-4 signal with Multiplex Section layer transparency is
formed by the application of RCC with flag 0, NCC with value 0, formed by the application of RCC with flag 0, NCC with value 0,
NVC with value 0, MT with value 1 and T with flag 2 applied to an NVC with value 0, MT with value 1 and T with flag 2 applied to
STM-4 Elementary Signal. an STM-4 Elementary Signal.
6. An STM-256 signal with Multiplex Section layer transparency is 6. An STM-256 signal with Multiplex Section layer transparency is
formed by the application of RCC with flag 0, NCC with value 0, formed by the application of RCC with flag 0, NCC with value 0,
NVC with value 0, MT with value 1 and T with flag 2 applied to an NVC with value 0, MT with value 1 and T with flag 2 applied to
STM-256 Elementary Signal. an STM-256 Elementary Signal.
7. An STS-1 SPE signal is formed by the application of RCC with 7. An STS-1 SPE 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 value 0, NCC with value 0, NVC with value 0, MT with value 1 and
with value 0 to an STS-1 SPE Elementary Signal. T with value 0 to an STS-1 SPE Elementary Signal.
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 1 (standard contiguous concatenation), NCC with value 1, NVC value 1 (standard contiguous concatenation), NCC with value 1,
with value 0, MT with value 1 and T with value 0 to an STS-3c SPE NVC with value 0, MT with value 1 and T with value 0 to an STS-
Elementary Signal. 3c SPE 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,
with value 0, MT with value 1 and T with value 0 to an STS-3c SPE NVC with value 0, MT with value 1 and T with value 0 to an STS-
Elementary Signal. 3c SPE Elementary Signal.
E.Mannie & D.Papadimitriou (Editors) 20 10. An STS-1-3v SPE signal is formed by the application of RCC with
10. An STS-1-3v SPE signal is formed by the application of RCC 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
with value 1, NCC with value 1, NVC with value 9 (virtual value 1, NCC with value 1, 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
an STS-3c SPE Elementary Signal. to an STS-3c SPE Elementary Signal.
12. An STS-12 signal with Section layer (full) transparency is 12. An STS-12 signal with Section layer (full) transparency is
formed by the application of RCC with value 0, NVC with value 0, formed by the application of RCC with value 0, NVC with value 0,
MT with value 1 and T with flag 1 to an STS-12 Elementary Signal. MT with value 1 and T with flag 1 to an STS-12 Elementary
Signal.
13. 3 x STS-768c SPE signal is formed by the application of RCC 13. 3 x STS-768c SPE signal is formed by the application of RCC with
with flag 1, NCC with value 256, NVC with value 0, MT with value flag 1, NCC with value 256, NVC with value 0, MT with value 3,
3, and T with value 0 to an STS-3c SPE Elementary Signal. and T with value 0 to an STS-3c SPE Elementary Signal.
14. 5 x VC-4-13v composed signal is formed by the application of 14. 5 x VC-4-13v composed signal is formed by the application of RCC
RCC with value 0, NVC with value 13, MT with value 5 and T with with value 0, NVC with value 13, MT with value 5 and T with
value 0 to a VC-4 Elementary Signal. value 0 to a VC-4 Elementary Signal.
The encoding of these examples is summarized in the following The encoding of these examples is summarized in the following table:
table:
Signal ST RCC NCC NVC MT T Signal ST RCC NCC NVC MT T
-------------------------------------------------------- --------------------------------------------------------
VC-4 6 0 0 0 1 0 VC-4 6 0 0 0 1 0
VC-4-7v 6 0 0 7 1 0 VC-4-7v 6 0 0 7 1 0
VC-4-16c 6 1 16 0 1 0 VC-4-16c 6 1 16 0 1 0
STM-16 MS transparent 10 0 0 0 1 2 STM-16 MS transparent 10 0 0 0 1 2
STM-4 MS transparent 9 0 0 0 1 2 STM-4 MS transparent 9 0 0 0 1 2
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 1 1 0 1 0 STS-3c SPE 6 1 1 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 1 1 9 1 0 STS-3c-9v SPE 6 1 1 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
E.Mannie & D.Papadimitriou (Editors) 21 Contributors
Contributors are listed by alphabetical order:
Stefan Ansorge (Alcatel)
Lorenzstrasse 10
70435 Stuttgart, Germany
EMail: stefan.ansorge@alcatel.de
Peter Ashwood-Smith (Nortel)
PO. Box 3511 Station C,
Ottawa, ON K1Y 4H7, Canada
EMail:petera@nortelnetworks.com
Ayan Banerjee (Calient)
5853 Rue Ferrari
San Jose, CA 95138, USA
EMail: abanerjee@calient.net
Lou Berger (Movaz)
7926 Jones Branch Drive
McLean, VA 22102, USA
EMail: lberger@movaz.com
Greg Bernstein (Ciena)
10480 Ridgeview Court
Cupertino, CA 94014, USA
EMail: greg@ciena.com
Angela Chiu (Celion)
One Sheila Drive, Suite 2
Tinton Falls, NJ 07724-2658
EMail: angela.chiu@celion.com
John Drake (Calient)
5853 Rue Ferrari
San Jose, CA 95138, USA
EMail: jdrake@calient.net
Yanhe Fan (Axiowave)
100 Nickerson Road
Marlborough, MA 01752, USA
EMail: yfan@axiowave.com
Michele Fontana (Alcatel)
Via Trento 30,
I-20059 Vimercate, Italy
EMail: michele.fontana@alcatel.it
Gert Grammel (Alcatel)
Lorenzstrasse, 10
70435 Stuttgart, Germany
EMail: gert.grammel@alcatel.de
Juergen Heiles (Siemens)
Hofmannstr. 51
D-81379 Munich, Germany
EMail: juergen.heiles@siemens.com
Suresh Katukam (Cisco)
1450 N. McDowell Blvd,
Petaluma, CA 94954-6515, USA
EMail: suresh.katukam@cisco.com
Kireeti Kompella (Juniper)
1194 N. Mathilda Ave.
Sunnyvale, CA 94089, USA
EMail: kireeti@juniper.net
Jonathan P. Lang (Calient)
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
EMail: zwlin@lucent.com
Ben Mack-Crane (Tellabs)
EMail: ben.mack-crane@tellabs.com
Dimitrios Pendarakis (Tellium)
2 Crescent Place, P.O. Box 901
Oceanport, NJ 07757-0901, USA
EMail: dpendarakis@tellium.com
Mike Raftelis (White Rock)
18111 Preston Road
Dallas, TX 75252, USA
Bala Rajagopalan (Tellium)
2 Crescent Place, P.O. Box 901
Oceanport, NJ 07757-0901, USA
EMail: braja@tellium.com
Yakov Rekhter (Juniper)
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
EMail: dsaha@tellium.com
Vishal Sharma (Metanoia)
335 Elan Village Lane
San Jose, CA 95134, USA
EMail: vsharma87@yahoo.com
George Swallow (Cisco)
250 Apollo Drive
Chelmsford, MA 01824, USA
EMail: swallow@cisco.com
Z. Bo Tang (Tellium)
2 Crescent Place, P.O. Box 901
Oceanport, NJ 07757-0901, USA
EMail: btang@tellium.com
Eve Varma (Lucent)
101 Crawfords Corner Rd
Holmdel, NJ 07733-3030, USA
EMail: evarma@lucent.com
Yangguang Xu (Lucent)
21-2A41, 1600 Osgood Street
North Andover, MA 01845, USA
EMail: xuyg@lucent.com
Authors' Addresses
Eric Mannie (Consultant)
Avenue de la Folle Chanson, 2
B-1050 Brussels, Belgium
Phone: +32 2 648-5023
Mobile: +32 (0)495-221775
EMail: eric_mannie@hotmail.com
Dimitri Papadimitriou (Alcatel)
Francis Wellesplein 1,
B-2018 Antwerpen, Belgium
Phone: +32 3 240-8491
EMail: dimitri.papadimitriou@alcatel.be
Full Copyright Statement
Copyright (C) The Internet Society (2004).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the IETF's procedures with respect to rights in IETF Documents can
be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 180 change blocks. 
797 lines changed or deleted 626 lines changed or added

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