draft-ietf-ccamp-rfc3946bis-01.txt   rfc4606.txt 
Network Working Group E. Mannie Network Working Group E. Mannie
Internet Draft Consultant Request for Comments: 4606 Perceval
Replaces RFC 3946 D. Papadimitriou Obsoletes: 3946 D. Papadimitriou
Category: Standard Track Alcatel Category: Standards Track Alcatel
December 2005 August 2006
Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for Synchronous Optical Network (SONET)
and Synchronous Digital Hierarchy (SDH) Control
draft-ietf-ccamp-rfc3946bis-01.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six Generalized Multi-Protocol Label Switching (GMPLS) Extensions for
months and may be updated, replaced, or obsoleted by other documents Synchronous Optical Network (SONET) and
at any time. It is inappropriate to use Internet-Drafts as reference Synchronous Digital Hierarchy (SDH) Control
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Status of This Memo
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at This document specifies an Internet standards track protocol for the
http://www.ietf.org/shadow.html. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution cof this memo is
unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2006).
Abstract Abstract
This document provides minor clarification to RFC 3946. This document provides minor clarification to RFC 3946.
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 GMPLS signaling is used.
E.Mannie & D.Papadimitriou (Editors) 1
Table of Contents Table of Contents
1. Introduction .............................................. 2 1. Introduction ....................................................2
2. SONET and SDH Traffic Parameters .......................... 2 2. SONET and SDH Traffic Parameters ................................3
2.1. SONET/SDH Traffic Parameters ........................ 3 2.1. SONET/SDH Traffic Parameters ...............................3
2.2. RSVP-TE Details ..................................... 9 2.2. RSVP-TE Details ............................................9
2.3. CR-LDP Details ...................................... 9 2.3. CR-LDP Details ............................................10
3. SONET and SDH Labels ...................................... 10 3. SONET and SDH Labels ...........................................11
4. Acknowledgments ........................................... 15 4. Acknowledgements ...............................................16
5. Security Considerations ................................... 16 5. Security Considerations ........................................16
6. IANA Considerations ....................................... 16 6. IANA Considerations ............................................16
7. References ................................................ 16 Contributors ......................................................17
7.1. Normative References ................................ 16 Appendix 1. Signal Type Values Extension for VC-3 .................20
Appendix 1 - Signal Type Values Extension for VC-3 ............ 18 Annex 1. Examples .................................................20
Annex 1 - Examples ............................................ 18 Normative References ..............................................23
Contributors .................................................. 21
Authors' Addresses ............................................ 25
Full Copyright Statement ...................................... 26
1. Introduction 1. Introduction
As described in [RFC3945], Generalized MPLS (GMPLS) extends MPLS As described in [RFC3945], Generalized MPLS (GMPLS) extends MPLS from
from supporting packet (Packet Switching Capable - PSC) interfaces supporting packet (Packet Switching Capable, or PSC) interfaces and
and switching to include support of four new classes of interfaces switching to include support of four new classes of interfaces and
and switching: Layer-2 Switch Capable (L2SC), Time-Division switching: Layer-2 Switch Capable (L2SC), Time-Division Multiplex
Multiplex (TDM), Lambda Switch Capable (LSC) and Fiber-Switch (TDM), Lambda Switch Capable (LSC) and Fiber-Switch Capable (FSC). A
Capable (FSC). A functional description of the extensions to MPLS functional description of the extensions to MPLS signaling needed to
signaling needed to support the new classes of interfaces and support the new classes of interfaces and switching is provided in
switching is provided in [RFC3471]. [RFC3473] describes RSVP-TE [RFC3471]. [RFC3473] describes RSVP-TE-specific formats and
specific formats and mechanisms needed to support all five classes mechanisms needed to support all five classes of interfaces, and CR-
of interfaces, and CR-LDP extensions can be found in [RFC3472]. LDP extensions can be found in [RFC3472].
This document presents details that are specific to Synchronous This document presents details that are specific to Synchronous
Optical Network (SONET)/Synchronous Digital Hierarchy (SDH). Per Optical Network (SONET)/Synchronous Digital Hierarchy (SDH). Per
[RFC3471], SONET/SDH specific parameters are carried in the [RFC3471], SONET/SDH-specific parameters are carried in the signaling
signaling protocol in traffic parameter specific objects. 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",
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
in this document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
Moreover, the reader is assumed to be familiar with the Moreover, the reader is assumed to be familiar with the terminology
terminology in ANSI [T1.105], ITU-T [G.707] as well as [RFC3471], in American National Standards Institute (ANSI) [T1.105] and ITU-T
[RFC3472], and [RFC3473]. The following abbreviations are used in [G.707], as well as with that in [RFC3471], [RFC3472], and [RFC3473].
this document: 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.
E.Mannie & D.Papadimitriou (Editors) 2
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 a base set of capabilities for SONET
for SONET ANSI [T1.105] and SDH ITU-T [G.707] such as ANSI [T1.105] and SDH ITU-T [G.707], such as concatenation and
concatenation and transparency. Other documents may further 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
signaling for SDH over PDH ITU-T G.832 or sub-STM-0 ITU-T G.708 ITU-T G.832 or sub-STM-0 ITU-T G.708 interfaces could be defined.
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.
E.Mannie & D.Papadimitriou (Editors) 3
o) Signal Type (ST): 8 bits o) Signal Type (ST): 8 bits
This field indicates the type of Elementary Signal that comprises This field indicates the type of Elementary Signal that constitutes
the requested LSP. Several transforms can be applied successively the requested Label Switched Path (LSP). Several transforms can be
on the Elementary Signal to build the Final Signal being actually applied successively on the Elementary Signal to build the Final
requested for the LSP. Signal actually being requested for the LSP.
Each transform application is optional and must be ignored if Each transform application is optional and must be ignored if zero,
zero, except the Multiplier (MT) that cannot be zero and is except the Multiplier (MT), which cannot be zero and is ignored if
ignored if equal to one. 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)
fields) can be optionally applied on the Elementary Signal, can be optionally applied on the Elementary Signal, resulting in a
resulting in a contiguously concatenated signal. contiguously concatenated signal.
- Second, virtual concatenation (by using the NVC field) can be - Second, virtual concatenation (by using the NVC field) can be
optionally applied on the Elementary Signal resulting in a optionally applied on the Elementary Signal, resulting in a
virtually concatenated signal. virtually concatenated signal.
- Third, some transparency (by using the Transparency field) can
be optionally specified when requesting a frame as signal rather - Third, some transparency (by using the Transparency field) can be
than an SPE or VC based signal. optionally specified when a frame is requested as signal rather
than an SPE- or VC-based signal.
- 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 on optionally applied directly on the Elementary Signal, on the
the contiguously concatenated signal obtained from the first contiguously concatenated signal obtained from the first phase, on
phase, or on the virtually concatenated signal obtained from the the virtually concatenated signal obtained from the second phase,
second phase, or on these signals combined with some transparency. or on these signals combined with some transparency.
Permitted Signal Type values for SONET/SDH are: Permitted Signal Type values for SONET/SDH are
Value Type (Elementary Signal) Value Type (Elementary Signal)
----- ------------------------ ----- ------------------------
1 VT1.5 SPE / VC-11 1 VT1.5 SPE / VC-11
2 VT2 SPE / VC-12 2 VT2 SPE / VC-12
3 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 transparency is requested)
8 STS-3 / STM-1 (only when requesting transparency) 8 STS-3 / STM-1 (only when transparency is requested)
9 STS-12 / STM-4 (only when requesting transparency) 9 STS-12 / STM-4 (only when transparency is requested)
10 STS-48 / STM-16 (only when requesting transparency) 10 STS-48 / STM-16 (only when transparency is requested)
11 STS-192 / STM-64 (only when requesting transparency) 11 STS-192 / STM-64 (only when transparency is requested)
12 STS-768 / STM-256 (only when requesting transparency) 12 STS-768 / STM-256 (only when transparency is requested)
A dedicated signal type is assigned to a SONET STS-3c SPE instead of 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. This is being coded as a contiguous concatenation of three STS-1 SPEs. This
done in order to provide easy interworking between SONET and SDH is done in order to provide easy interworking between SONET and SDH
signaling. signaling.
Appendix 1 adds one signal type (optional) to the above values. Appendix 1 adds one signal type (optional) to the above values.
E.Mannie & D.Papadimitriou (Editors) 4
o) Requested Contiguous Concatenation (RCC): 8 bits o) Requested Contiguous Concatenation (RCC): 8 bits
This field is used to request the optional SONET/SDH contiguous This field is used to request 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 support This field is a vector of flags. Each flag indicates the support of
of a particular type of contiguous concatenation. Several flags a particular type of contiguous concatenation. Several flags can be
can be set at the same time to indicate a choice. 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
node the different types of contiguous concatenation that it the different types of contiguous concatenation that it supports.
supports. However, the downstream node decides which one to use However, the downstream node decides which one to use according to
according to its own rules. its own rules.
A downstream node receiving simultaneously more than one flag A downstream node receiving simultaneously more than one flag chooses
chooses a particular type of contiguous concatenation, if any a particular type of contiguous concatenation, if any is supported,
supported, and based on criteria that are out of this document and according to criteria that are out of this document's scope. A
scope. A downstream node that doesn't support any of the downstream node that doesn't support any of the concatenation types
concatenation types indicated by the field must refuse the LSP indicated by the field must refuse the LSP request. In particular,
request. In particular, it must refuse the LSP request if it it must refuse the LSP request if it doesn't support contiguous
doesn't support contiguous concatenation at all. concatenation at all.
When several flags have been set, the upstream node retrieves the When several flags have been set, the upstream node retrieves the
(single) type of contiguous concatenation the downstream node has (single) type of contiguous concatenation the downstream node has
selected by looking at the position indicated by the first label selected by looking at the position indicated by the first label and
and the number of label(s) as returned by the downstream node (see the number of labels as returned by the downstream node (see also
also Section 3). Section 3).
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 field
field indicates that some contiguous concatenation is requested. indicates that some contiguous concatenation is 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 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 in the section on the NCC about the SONET contiguous
contiguous concatenation of STS-1 SPEs when the number of concatenation of STS-1 SPEs when the number of components is a
components is a multiple of three. multiple of three.
o) Number of Contiguous Components (NCC): 16 bits o) Number of Contiguous Components (NCC): 16 bits
This field indicates the number of identical SONET SPEs/SDH VCs This field indicates the number of identical SONET SPEs/SDH VCs
(i.e., Elementary Signal) that are requested to be concatenated, (i.e., Elementary Signal) that are requested to be concatenated, as
as specified in the RCC field. specified in the RCC field.
Note 1: when requesting a SONET STS-Nc SPE with N=3*X, the
E.Mannie & D.Papadimitriou (Editors) 5 Note 1: When a SONET STS-Nc SPE with N=3*X is requested, the
Elementary Signal to use must always be an STS-3c_SPE signal type Elementary Signal to be used must always be an STS-3c_SPE signal
and the value of NCC must always be equal to X. This allows also type, and the value of NCC must always be equal to X. This allows
facilitating the interworking between SONET and SDH. In facilitating the interworking between SONET and SDH. In particular,
particular, it means that the contiguous concatenation of three it means that the contiguous concatenation of three STS-1 SPEs cannot
STS-1 SPEs can not be requested because according to this be requested, as according to this specification this type of signal
specification, this type of signal must be coded using the STS-3c must be coded using the STS-3c SPE signal type.
SPE signal type.
Note 2: when requesting a transparent STS-N/STM-N signal limited Note 2: When a transparent STS-N/STM-N signal is requested that is
to a single contiguously concatenated STS-Nc_SPE/VC-4-Nc, the limited to a single contiguously concatenated STS-Nc_SPE/VC-4-Nc, the
signal type must be STS-N/STM-N, RCC with flag 1 and NCC set to 1. signal type must be STS-N/STM-N, RCC with flag 1, NCC set to 1.
The NCC value must be consistent with the type of contiguous The NCC value must be consistent with the type of contiguous
concatenation being requested in the RCC field. In particular, concatenation being requested in the RCC field. In particular, this
this field is irrelevant if no contiguous concatenation is field is irrelevant if no contiguous concatenation is requested (RCC
requested (RCC = 0), in that case it must be set to zero when = 0). In that case, it must be set to zero when sent and should be
sent, and should be ignored when received. A RCC value different ignored when received. A RCC value different from 0 implies a number
from 0 implies a number of contiguous components greater than or of contiguous components greater than or equal to 1.
equal to 1.
Note 3: Following these rules, when requesting a VC-4 signal, the Note 3: Following these rules, when a VC-4 signal is requested, the
RCC and the NCC values SHOULD be set to 0 whereas for an STS-3c RCC and the NCC values SHOULD be set to 0, whereas for an STS-3c SPE
SPE signal, the RCC and the NCC values SHOULD be set 1. However, signal, the RCC and the NCC values SHOULD be set 1. However, if
if local conditions allow and since the setting of the RCC and NCC local conditions allow, since the setting of the RCC and NCC values
values is locally driven, the requesting upstream node MAY set the is locally driven, the requesting upstream node MAY set the RCC and
RCC and NCC values to either SDH or SONET settings without NCC values to either SDH or SONET settings without impacting the
impacting the function. Moreover, the downstream node SHOULD function. Moreover, the downstream node SHOULD accept the requested
accept the requested values if local conditions allow. If these values if local conditions allow. If these values cannot be
values cannot be supported, the receiver downstream node SHOULD supported, the receiver downstream node SHOULD generate a
generate a PathErr/NOTIFICATION message (see Section 2.2/2.3, PathErr/NOTIFICATION message (see Sections 2.2 and 2.3,
respectively). respectively).
o) Number of Virtual Components (NVC): 16 bits o) Number of Virtual Components (NVC): 16 bits
This field indicates the number of signals that are requested to This field indicates the number of signals that are requested to be
be virtually concatenated. These signals are all of the same type virtually concatenated. These signals are all of the same type by
by definition. They are Elementary Signal SPEs/VCs for which definition. They are Elementary Signal SPEs/VCs for which signal
signal types are defined in this document, i.e., VT1.5_SPE/VC-11, 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- VT2_SPE/VC-12, VT3_SPE, VT6_SPE/VC-2, STS-1_SPE/VC-3, or
3c_SPE/VC-4. STS-3c_SPE/VC-4.
This field is set to 0 (default value) to indicate that no virtual This field is set to 0 (default value) to indicate that no virtual
concatenation is requested. concatenation is requested.
o) Multiplier (MT): 16 bits o) 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 identical signals can be identical Elementary Signals, identical contiguously
contiguously concatenated signals, or identical virtually concatenated signals, or identical virtually concatenated signals.
concatenated signals. Note that all these signals belong thus to Note that all of these signals thus belong to the same LSP.
the same LSP.
E.Mannie & D.Papadimitriou (Editors) 6
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 are concatenated signals is done via the order of the labels that are
specified in the signaling. The first set of labels must describe specified in the signaling. The first set of labels must describe
the first component (set of individual signals belonging to the the first component (set of individual signals belonging to the first
first virtual concatenated signal), the second set must describe virtual concatenated signal), the second set must describe the second
the second component (set of individual signals belonging to the component (set of individual signals belonging to the second virtual
second virtual concatenated signal) and so on. concatenated signal), and so on.
This field is set to one (default value) to indicate that exactly This field is set to one (default value) to indicate that exactly one
one instance of a signal is being requested. Intermediate and instance of a signal is being requested. Intermediate and egress
egress nodes MUST verify that the node itself and the interfaces nodes MUST verify that the node itself and the interfaces on which
on which the LSP will be established can support the requested the LSP will be established can support the requested multiplier
multiplier value. If the requested values can not be supported, value. If the requested values cannot be supported, the receiver
the receiver node MUST generate a PathErr/NOTIFICATION message node MUST generate a PathErr/NOTIFICATION message (see Sections 2.2
(see Section 2.2/2.3, respectively). and 2.3, respectively).
Zero is an invalid value. If received, the node MUST generate a Zero is an invalid value. If a zero is received, the node MUST
PathErr/NOTIFICATION message (see Section 2.2/2.3, respectively). generate a PathErr/NOTIFICATION message (see Sections 2.2 and 2.3,
respectively).
Note 1: when requesting a transparent STS-N/STM-N signal limited Note 1: When a transparent STS-N/STM-N signal is requested that is
to a single contiguously concatenated STS-Nc-SPE/VC-4-Nc, the limited to a single contiguously concatenated STS-Nc-SPE/VC-4-Nc, the
multiplier field MUST be equal to 1 (only valid value). multiplier field MUST be equal to 1 (only valid value).
o) Transparency (T): 32 bits o) 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 are provide different types of transparency. Not all combinations are
necessarily valid. The default value for this field is zero, i.e., necessarily valid. The default value for this field is zero, i.e.,
no transparency requested. no transparency is requested.
Transparency, as defined from the point of view of this signaling Transparency, as defined from the point of view of this signaling
specification, is only applicable to the fields in the SONET/SDH specification, is only applicable to the fields in the SONET/SDH
frame overheads. In the SONET case, these are the fields in the frame overheads. In the SONET case, these are the fields in the
Section Overhead (SOH), and the Line Overhead (LOH). In the SDH Section Overhead (SOH) and the Line Overhead (LOH). In the SDH case,
case, these are the fields in the Regenerator Section Overhead these are the fields in the Regenerator Section Overhead (RSOH), the
(RSOH), the Multiplex Section overhead (MSOH), and the pointer Multiplex Section overhead (MSOH), and the pointer fields between the
fields between the two. With SONET, the pointer fields are part of two. With SONET, the pointer fields are part of the LOH.
the LOH.
Note as well that transparency is only applicable when using the Note also that transparency is only applicable when the following
following Signal Types: STS-1/STM-0, STS-3/STM-1, STS-12/STM-4, signal types are used: STS-1/STM-0, STS-3/STM-1, STS-12/STM-4,
STS-48/STM-16, STS-192/STM-64 and STS-768/STM-256. At least one STS-48/STM-16, STS-192/STM-64, and STS-768/STM-256. At least one
transparency type must be specified when requesting such a signal transparency type must be specified when such a signal type is
type. requested.
Transparency indicates precisely which fields in these overheads Transparency indicates precisely which fields in these overheads must
must be delivered unmodified at the other end of the LSP. An be delivered unmodified at the other end of the LSP. An ingress
ingress LSR requesting transparency will pass these overhead Label Switching Router (LSR) requesting transparency will pass these
fields that must be delivered to the egress LSR without any overhead fields that must be delivered to the egress LSR without any
change. From the ingress and egress LSRs point of views, these change. From the ingress and egress LSRs point of views, these
fields must be seen as unmodified. fields must be seen as being unmodified.
E.Mannie & D.Papadimitriou (Editors) 7 Transparency is applied not at the interfaces with the initiating and
Transparency is not applied at the interfaces with the initiating terminating LSRs but only between intermediate LSRs. The
and terminating LSRs, but is only applied between intermediate transparency field is used to request an LSP that supports the
LSRs. The transparency field is used to request an LSP that requested transparency type; it may also be used to set up the
supports the requested transparency type; it may also be used to transparency process to be applied at each intermediate LSR.
setup the transparency process to be applied at each intermediate
LSR.
The different transparency flags are the following: The different transparency flags are as follows:
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 ignored when received. A flag is
received. A flag is set to one to indicate that the corresponding set to one to indicate that the corresponding transparency is
transparency is requested. 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 cannot 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). Sections 2.2 and 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 Section/Regenerator Section layer
Section layer transparency all other flags MUST be ignored. transparency is used all other flags MUST be ignored.
Line/Multiplex Section layer transparency means that the LOH/MSOH Line/Multiplex Section layer transparency means that the LOH/MSOH
must be delivered unmodified. This implies that pointers cannot be must be delivered unmodified. This implies that pointers cannot be
adjusted. adjusted.
o) Profile (P): 32 bits o) 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 be No standard profile is currently defined, and this field SHOULD be
set to zero when transmitted and SHOULD be ignored when received. set to zero when transmitted and ignored when 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 the SENDER_TSPEC object and for 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
objects have the following class and type for SONET ANSI T1.105 have the following class and type for SONET ANSI T1.105 and SDH ITU-T
and SDH ITU-T G.707: G.707:
SONET/SDH SENDER_TSPEC object: Class = 12, C-Type = 4 SONET/SDH SENDER_TSPEC object: Class = 12, C-Type = 4
SONET/SDH FLOWSPEC object: Class = 9, C-Type = 4 SONET/SDH FLOWSPEC object: Class = 9, C-Type = 4
E.Mannie & D.Papadimitriou (Editors) 8
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]).
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) cannot 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: The type field for the SONET/SDH Traffic Parameters TLV is 0x0838.
0x0838.
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) cannot 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]).
E.Mannie & D.Papadimitriou (Editors) 9
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) cannot 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 time-slots within an egress port; i.e., a VTx SPE, an STS-x SPE, or a
SPE, an STS-x SPE or a VC-x. A SONET/SDH label will identify the VC-x. A SONET/SDH label will identify the exact position (i.e.,
exact position (i.e., first time-slot) of a particular VTx SPE, first time-slot) of a particular VTx SPE, STS-x SPE, or VC-x signal
STS-x SPE or VC-x signal in a multiplexing structure. SONET and in a multiplexing structure. SONET and SDH labels are carried in the
SDH labels are carried in the Generalized Label per [RFC3473] and Generalized Label per [RFC3473] and [RFC3472].
[RFC3472].
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 unique label is encoded as a single 32 bit label Label field. This unique label is encoded as a single 32-bit label
value (as defined in this Section) of the Generalized Label object value (as defined in this section) of the Generalized Label object
(Class-Num = 16, C-Type = 2)/TLV (0x0825). This label identifies (Class-Num = 16, C-Type = 2)/TLV (0x0825). This label identifies the
the lowest time-slot occupied by the contiguously concatenated lowest time-slot occupied by the contiguously concatenated signal.
signal. By lowest time-slot we mean the one having the lowest By lowest time-slot, we mean the one having the lowest label (value)
label (value) when compared as integer values, i.e., the time-slot when compared as an integer value; i.e., the time-slot occupied by
occupied by the first component signal of the concatenated signal the first component signal of the concatenated signal encountered
encountered when descending the tree. 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. This ordered list of labels labels in the concatenation is given. This ordered list of labels is
is encoded as a sequence of 32 bit label values (as defined in encoded as a sequence of 32-bit label values (as defined in this
this Section) of the Generalized Label object (Class-Num = 16, C- section) of the Generalized Label object (Class-Num = 16, C-Type =
Type = 2)/TLV (0x0825). Each label indicates the first time-slot 2)/TLV (0x0825). Each label indicates the first time-slot occupied
by a component of the virtually concatenated signal. The order of
E.Mannie & D.Papadimitriou (Editors) 10 the labels must reflect the order of the payloads to concatenate (not
occupied by a component of the virtually concatenated signal. The the physical order of time-slots). The above representation limits
order of the labels must reflect the order of the payloads to virtual concatenation to remain within a single (component) link; it
concatenate (not the physical order of time-slots). The above imposes, as such, a restriction compared to the ANSI [T1.105]/ ITU-T
representation limits virtual concatenation to remain within a [G.707] recommendations. The standard definition for virtual
single (component) link; it imposes as such a restriction compared concatenation allows each virtual concatenation components to travel
to the ANSI [T1.105]/ ITU-T [G.707] recommendations. The standard over diverse paths. Within GMPLS, virtual concatenation components
definition for virtual concatenation allows each virtual must travel over the same (component) link if they are part of the
concatenation components to travel over diverse paths. Within same LSP. This is due to the way that labels are bound to a
GMPLS, virtual concatenation components must travel over the same (component) link. Note, however, that the routing of components on
(component) link if they are part of the same LSP. This is due to different paths is indeed equivalent to establishing different LSPs,
the way that labels are bound to a (component) link. Note however, each one having its own route. Several LSPs can be initiated and
that the routing of components on different paths is indeed terminated between the same nodes, and their corresponding components
equivalent to establishing different LSPs, each one having its own can then be associated together (i.e., virtually concatenated).
route. Several LSPs can be initiated and terminated between the
same nodes and their corresponding components can then 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
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. This ordered list of labels is encoded as a Signal is given. This ordered list of labels is encoded as a
sequence of 32 bit label values (as defined in this Section) of sequence of 32-bit label values (as defined in this section) of the
the Generalized Label object (Class-Num = 16, C-Type = 2)/TLV Generalized Label object (Class-Num = 16, C-Type = 2)/TLV (0x0825).
(0x0825). In case of multiplication of virtually concatenated In case of multiplication of virtually concatenated signals, the
signals, the explicit ordered list of set of labels that take part explicit ordered list of the set of labels that take part in the
in the Final Signal is given. The first set of labels indicates Final Signal is given. The first set of labels indicates the time-
the time-slots occupied by the first virtually concatenated slots occupied by the first virtually concatenated signal, the second
signal, the second set of labels indicates the time-slots occupied set of labels indicates the time-slots occupied by the second
by the second virtually concatenated signal, and so on. The above virtually concatenated signal, and so on. The above representation
representation limits multiplication to remain within a single limits 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
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 Sections 7.3.7 through 7.3.13; i.e., the (K, L, M) numbering. Note
that the higher order numbering scheme defined in [G.707] sections that the higher order numbering scheme defined in [G.707], Sections
7.3.1 to 7.3.6 is not used here. 7.3.1 through 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 being
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 ignored when received.
received.
E.Mannie & D.Papadimitriou (Editors) 11 When a hierarchy of SONET/SDH LSPs is used, a higher-order LSP with a
When a hierarchy of SONET/SDH LSPs is used, a higher order LSP given bandwidth can be used to carry lower-order LSPs. Remember that
with a given bandwidth can be used to carry lower order LSPs. a higher-order LSP is established through a SONET/SDH higher-order
Remember here that a higher order LSP is established through a path layer network, and a lower-order LSP through a SONET/SDH lower-
SONET/SDH higher order path layer network and a lower order LSP, order path layer network (see also ITU-T G.803, Section 3, for the
through a SONET/SDH lower order path layer network (see also ITU-T corresponding definitions). In this context, the higher-order
G.803, Section 3 for the corresponding definitions). In this SONET/SDH LSP behaves as a "virtual link" with a given bandwidth
context, the higher order SONET/SDH LSP behaves as a "virtual (e.g., VC-3); it may also be used as a Forwarding Adjacency. A
link" with a given bandwidth (e.g., VC-3), it may also be used as lower-order SONET/SDH LSP can be established through that higher-
a Forwarding Adjacency. A lower order SONET/SDH LSP can be order LSP. Since a label is local to a (virtual) link, the highest
established through that higher order LSP. Since a label is local part of that label (i.e., the S, U, and K fields) is non-significant
to a (virtual) link, the highest part of that label (i.e., the S, and is set to zero; i.e., the label is "0,0,0,L,M". Similarly, if
U and K fields) is non-significant and is set to zero, i.e., the the structure of the lower-order LSP is unknown or not relevant, the
label is "0,0,0,L,M". Similarly, if the structure of the lower lowest part of that label (i.e., the L and M fields) is non-
order LSP is unknown or not relevant, the lowest part of that significant and is set to zero; i.e., the label is "S,U,K,0,0".
label (i.e., the L and M fields) is non-significant and is set to
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. For instance, a VC-3 LSP can be used to carry lower-order LSPs. In
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 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 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 (N>1) and SDH STM-N (N>0). S must be 0 and ignored for STS-1 and
and STM-0. 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 STS-3/AUG-1. U is only significant for SONET STS-N (N>1) and SDH
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 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 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 SPE inside the corresponding VT Group; these values MUST NOT be
NOT be used for SDH since there is no equivalent of VT3 with used for SDH, since there is no equivalent of VT3 with SDH.
SDH. M=3->5 indicates a specific VT2_SPE/VC-12 inside the M=3->5 indicates a specific VT2_SPE/VC-12 inside the
corresponding VT_Group/TUG-2. M=6->9 indicates a specific corresponding VT_Group/TUG-2. M=6->9 indicates a specific
VT1.5_SPE/VC-11 inside the corresponding VT_Group/TUG-2. VT1.5_SPE/VC-11 inside the corresponding VT_Group/TUG-2.
E.Mannie & D.Papadimitriou (Editors) 12
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 i.e., when all Transparency (T) bits defined in Section 2.1 are set
section 2.1 are set to zero. Any transparent STS-1/STM-0/STS- to zero. Any transparent STS-1/STM-0/STS-3*N/STM-N (N=1, 4, 16, 64,
3*N/STM-N (N=1, 4, 16, 64, 256) signal request MUST use a label 256) signal request MUST use a label format as defined in [RFC3471].
format as defined in [RFC3471].
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
skipping to change at line 710 skipping to change at page 15, line 15
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
E.Mannie & D.Papadimitriou (Editors) 13
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
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 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 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. is: S>0, U>0, K=0, L>0, M=0.
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 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. Sth STS-3/AUG-1 is: S>0, U>0, K=0, L>0, M=8.
Example 6: the label for the STS-12c SPE/VC-4-4c which uses the Example 6: the label for the STS-12c SPE/VC-4-4c which uses the
9th STS-3/AUG-1 as its first timeslot is: S=9, U=0, 9th STS-3/AUG-1 as its first timeslot is: S=9, U=0,
K=0, L=0, M=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
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,
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.
Note: when a Section/RS or Line/MS transparent STS-1/STM-0/STS- In case of STM-0/STS-1, the values of S, U, and K must be equal to
3*N/STM-N (N=1, 4, 16, 64, 256) signal is requested, the SUKLM zero, according to the field coding rules. For instance, when a VC-3
in an STM-0 is requested, the label is S=0, U=0, K=0, L=0, M=0. When
a VC-11 in a VC-3 in an STM-0 is requested, the label is S=0, U=0,
K=0, L>0, M=6..9.
E.Mannie & D.Papadimitriou (Editors) 14 Note: when a Section/RS or Line/MS transparent STS-1/STM-0/
label format and encoding is not applicable and the label encoding STS-3*N/STM-N (N=1, 4, 16, 64, 256) signal is requested, the SUKLM
MUST follow the rules defined in [RFC3471] Section 3.2. label format and encoding is not applicable, and the label encoding
MUST follow the rules defined in [RFC3471], Section 3.2.
4. Acknowledgments 4. Acknowledgements
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.
The authors would like to thank Richard Rabbat for its valuable The authors would like to thank Richard Rabbat for his valuable
input that lead to this revision. input, which lead to this revision.
5. Security Considerations 5. Security Considerations
This document 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 been defined by IANA for this document. Three values defined by IANA for RFC 3946 now apply to 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 = 4 (see - A SONET/SDH SENDER_TSPEC object: Class = 12, C-Type = 4 (see
Section 2.2). Section 2.2).
- A SONET/SDH FLOWSPEC object: Class = 9, C-Type = 4 (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 - A type field for the SONET/SDH Traffic Parameters TLV (see Section
Section 2.3). 2.3).
7. References
7.1 Normative References
[G.707] ITU-T Recommendation G.707, "Network Node Interface for
the Synchronous Digital Hierarchy", October 2000.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S.
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version
1 Functional Specification", RFC 2205, September 1997.
[RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated
Services", RFC 2210, September 1997.
E.Mannie & D.Papadimitriou (Editors) 15
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan,
V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, December 2001.
[RFC3212] Jamoussi, B., Andersson, L., Callon, R., Dantu, R.,
Wu, L., Doolan, P., Worster, T., Feldman, N.,
Fredette, A., Girish, M., Gray, E., Heinanen, J.,
Kilty, T., and A. Malis, "Constraint-Based LSP Setup
using LDP", RFC 3212, January 2002.
[RFC3471] Berger, L., "Generalized Multi-Protocol Label
Switching (MPLS) Signaling Functional Description",
RFC 3471, January 2003.
[RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized Multi-
Protocol Label Switching (MPLS) Signaling -
Constraint-based Routed Label Distribution Protocol
(CR-LDP) Extensions", RFC 3472, January 2003.
[RFC3473] Berger, L., "Generalized Multi-Protocol Label
Switching (MPLS) Signaling - Resource ReserVation
Protocol Traffic Engineering (RSVP-TE) Extensions",
RFC 3473, January 2003.
[RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label
Switching (GMPLS) Architecture", RFC 3945, October
2004.
[T1.105] "Synchronous Optical Network (SONET): Basic
Description Including Multiplex Structure, Rates, and
Formats", ANSI T1.105, October 2000.
E.Mannie & D.Papadimitriou (Editors) 16
Appendix 1 - Signal Type Values Extension for VC-3
This appendix defines the following optional additional Signal
Type value for the Signal Type field of section 2.1:
Value Type
----- ---------------------
20 "VC-3 via AU-3 at the end"
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
in TUG-2s, however a VC-3 in the AU-3 branch can be. In addition,
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
LSR (e.g. forming a VC-3 forwarding adjacency). This LSR could
then want to demultiplex this VC-3 and switch internal low order
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
able to switch internally from a TU-3 branch to an AU-3 branch on
its incoming interface before demultiplexing and then switching
the content with its switch fabric.
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
branch.
This is achieved by using the "VC-3 via AU-3 at the end" signal
type. This information can be used, for instance, by the
penultimate LSR to switch an incoming VC-3 received in any branch
to the AU-3 branch on the outgoing interface to the destination
LSR.
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
the network. The VC-3 signal type just indicates that a VC-3 in
any branch is suitable.
E.Mannie & D.Papadimitriou (Editors) 17
Annex 1 - Examples
This annex defines examples of SONET and SDH signal coding. Their
objective is to help the reader to understand how works the traffic
parameter coding and not to give examples of typical SONET or SDH
signals.
As stated above, signal types are Elementary Signals to which
successive concatenation, multiplication and transparency
transforms can be applied to obtain Final Signals.
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 value 0 to a VC-4 Elementary Signal.
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 components), MT with value 1 and T with value 0 to a VC-4
Elementary Signal.
3. A VC-4-16c signal is formed by the application of RCC with
value 1 (standard contiguous concatenation), NCC with value 16,
NVC with value 0, MT with value 1 and T with value 0 to a VC-4
Elementary Signal.
4. An STM-16 signal with Multiplex Section layer transparency 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 flag 2 to an
STM-16 Elementary Signal.
5. An STM-4 signal with Multiplex Section layer transparency 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 flag 2 applied
to an STM-4 Elementary Signal.
6. An STM-256 signal with Multiplex Section layer transparency 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 flag 2 applied
to an STM-256 Elementary Signal.
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 with value 0 to an STS-1 SPE Elementary Signal.
8. An STS-3c SPE signal is formed by the application of RCC with
value 1 (standard contiguous concatenation), NCC with value 1,
NVC with value 0, MT with value 1 and T with value 0 to an STS-
3c SPE Elementary Signal.
9. An STS-48c SPE signal is formed by the application of RCC with
value 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 Elementary Signal.
E.Mannie & D.Papadimitriou (Editors) 18
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
components), MT with value 1 and T with value 0 to an STS-1 SPE
Elementary Signal.
11.An STS-3c-9v SPE signal is formed by the application of RCC
with 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 an STS-3c SPE Elementary Signal.
12.An STS-12 signal with Section layer (full) transparency 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 flag 1 to an
STS-12 Elementary Signal.
13.A 3 x STS-768c SPE signal is formed by the application of RCC
with value 1, NCC with value 256, NVC with value 0, MT with
value 3, and T with value 0 to an STS-3c SPE Elementary Signal.
14.
A 5 x VC-4-13v composed signal is formed by the application of
RCC with value 0, NVC with value 13, MT with value 5 and T with
value 0 to a VC-4 Elementary Signal.
The encoding of these examples is summarized in the following
table:
Signal ST RCC NCC NVC MT T
--------------------------------------------------------
VC-4 6 0 0 0 1 0
VC-4-7v 6 0 0 7 1 0
VC-4-16c 6 1 16 0 1 0
STM-16 MS transparent 10 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
STS-1 SPE 5 0 0 0 1 0
STS-3c SPE 6 1 1 0 1 0
STS-48c SPE 6 1 16 0 1 0
STS-1-3v SPE 5 0 0 3 1 0
STS-3c-9v SPE 6 1 1 9 1 0
STS-12 Section transparent 9 0 0 0 1 1
3 x STS-768c SPE 6 1 256 0 3 0
5 x VC-4-13v 6 0 0 13 5 0
Contributors Contributors
Contributors are listed by alphabetical order: Contributors are listed in alphabetical order:
Stefan Ansorge (Alcatel) Stefan Ansorge (Alcatel)
Lorenzstrasse 10 Lorenzstrasse 10
70435 Stuttgart, Germany 70435 Stuttgart, Germany
EMail: stefan.ansorge@alcatel.de EMail: stefan.ansorge@alcatel.de
Peter Ashwood-Smith (Nortel) Peter Ashwood-Smith (Nortel)
PO. Box 3511 Station C, PO. Box 3511 Station C,
E.Mannie & D.Papadimitriou (Editors) 19
Ottawa, ON K1Y 4H7, Canada Ottawa, ON K1Y 4H7, Canada
EMail:petera@nortelnetworks.com EMail:petera@nortelnetworks.com
Ayan Banerjee (Calient) Ayan Banerjee (Calient)
5853 Rue Ferrari 5853 Rue Ferrari
San Jose, CA 95138, USA San Jose, CA 95138, USA
EMail: abanerjee@calient.net EMail: abanerjee@calient.net
Lou Berger (Movaz) Lou Berger (Movaz)
7926 Jones Branch Drive 7926 Jones Branch Drive
skipping to change at line 1062 skipping to change at page 18, line 30
Hofmannstr. 51 Hofmannstr. 51
D-81379 Munich, Germany D-81379 Munich, Germany
EMail: juergen.heiles@siemens.com EMail: juergen.heiles@siemens.com
Suresh Katukam (Cisco) Suresh Katukam (Cisco)
1450 N. McDowell Blvd, 1450 N. McDowell Blvd,
Petaluma, CA 94954-6515, USA Petaluma, CA 94954-6515, USA
EMail: suresh.katukam@cisco.com EMail: suresh.katukam@cisco.com
Kireeti Kompella (Juniper) Kireeti Kompella (Juniper)
E.Mannie & D.Papadimitriou (Editors) 20
1194 N. Mathilda Ave. 1194 N. Mathilda Ave.
Sunnyvale, CA 94089, USA Sunnyvale, CA 94089, USA
EMail: kireeti@juniper.net EMail: kireeti@juniper.net
Jonathan P. Lang (Calient) Jonathan P. Lang (Calient)
25 Castilian 25 Castilian
Goleta, CA 93117, USA Goleta, CA 93117, USA
EMail: jplang@calient.net EMail: jplang@calient.net
Fong Liaw (Solas Research) Fong Liaw (Solas Research)
skipping to change at line 1118 skipping to change at page 19, line 38
Vishal Sharma (Metanoia) Vishal Sharma (Metanoia)
335 Elan Village Lane 335 Elan Village Lane
San Jose, CA 95134, USA San Jose, CA 95134, USA
EMail: vsharma87@yahoo.com EMail: vsharma87@yahoo.com
George Swallow (Cisco) George Swallow (Cisco)
250 Apollo Drive 250 Apollo Drive
Chelmsford, MA 01824, USA Chelmsford, MA 01824, USA
EMail: swallow@cisco.com EMail: swallow@cisco.com
E.Mannie & D.Papadimitriou (Editors) 21
Z. Bo Tang (Tellium) Z. Bo Tang (Tellium)
2 Crescent Place, P.O. Box 901 2 Crescent Place, P.O. Box 901
Oceanport, NJ 07757-0901, USA Oceanport, NJ 07757-0901, USA
EMail: btang@tellium.com EMail: btang@tellium.com
Eve Varma (Lucent) Eve Varma (Lucent)
101 Crawfords Corner Rd 101 Crawfords Corner Rd
Holmdel, NJ 07733-3030, USA Holmdel, NJ 07733-3030, USA
EMail: evarma@lucent.com EMail: evarma@lucent.com
Yangguang Xu (Lucent) Yangguang Xu (Lucent)
21-2A41, 1600 Osgood Street 21-2A41, 1600 Osgood Street
North Andover, MA 01845, USA North Andover, MA 01845, USA
EMail: xuyg@lucent.com EMail: xuyg@lucent.com
Appendix 1. Signal Type Values Extension for VC-3
This appendix defines the following optional additional Signal
Type value for the Signal Type field of Section 2.1:
Value Type
----- ---------------------
20 "VC-3 via AU-3 at the end"
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 in
TUG-2s; however, a VC-3 in the AU-3 branch can be. In addition, 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 LSR
(e.g., forming a VC-3 forwarding adjacency). This LSR could then
want to demultiplex this VC-3 and switch internal low-order LSPs.
For implementation reasons, this could be only possible if the LSR
receives the VC-3 in the AU-3 branch. For example, for an LSR not
able to switch internally from a TU-3 branch to an AU-3 branch on its
incoming interface before demultiplexing and then switching the
content with its switch fabric.
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 branch.
This is achieved by using the "VC-3 via AU-3 at the end" signal type.
This information can be used, for instance, by the penultimate LSR to
switch an incoming VC-3 received in any branch to the AU-3 branch on
the outgoing interface to the destination LSR.
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 the
network. The VC-3 signal type just indicates that a VC-3 in any
branch is suitable.
Annex 1. Examples
This annex defines examples of SONET and SDH signal coding. The
objective is to help the reader to understand how the traffic
parameter coding works and not to give examples of typical SONET or
SDH signals.
As stated above, signal types are Elementary Signals to which
successive concatenation, multiplication, and transparency transforms
can be applied to obtain Final Signals.
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
value 0 to a VC-4 Elementary Signal.
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 components), MT with value 1, and T with value 0 to a VC-4
Elementary Signal.
3. A VC-4-16c signal is formed by the application of RCC with value
1 (standard contiguous concatenation), NCC with value 16, NVC
with value 0, MT with value 1, and T with value 0 to a VC-4
Elementary Signal.
4. An STM-16 signal with Multiplex Section layer transparency 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 flag 2 to an
STM-16 Elementary Signal.
5. An STM-4 signal with Multiplex Section layer transparency 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 flag 2 applied to
an STM-4 Elementary Signal.
6. An STM-256 signal with Multiplex Section layer transparency 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 flag 2 applied to
an STM-256 Elementary Signal.
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 with value 0 to an STS-1 SPE Elementary Signal.
8. An STS-3c SPE signal is formed by the application of RCC with
value 1 (standard contiguous concatenation), NCC with value 1,
NVC with value 0, MT with value 1, and T with value 0 to an
STS-3c SPE Elementary Signal.
9. An STS-48c SPE signal is formed by the application of RCC with
value 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 Elementary Signal.
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
components), MT with value 1, and T with value 0 to an STS-1 SPE
Elementary Signal.
11. An STS-3c-9v SPE signal is formed by the application of RCC with
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 an STS-3c SPE Elementary Signal.
12. An STS-12 signal with Section layer (full) transparency 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 flag 1 to an
STS-12 Elementary Signal.
13. A 3 x STS-768c SPE signal is formed by the application of RCC
with value 1, NCC with value 256, NVC with value 0, MT with
value 3, and T with value 0 to an STS-3c SPE Elementary Signal.
14. A 5 x VC-4-13v composed signal is formed by the application of
RCC with value 0, NVC with value 13, MT with value 5, and T with
value 0 to a VC-4 Elementary Signal.
The encoding of these examples is summarized in the following table:
Signal ST RCC NCC NVC MT T
--------------------------------------------------------
VC-4 6 0 0 0 1 0
VC-4-7v 6 0 0 7 1 0
VC-4-16c 6 1 16 0 1 0
STM-16 MS transparent 10 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
STS-1 SPE 5 0 0 0 1 0
STS-3c SPE 6 1 1 0 1 0
STS-48c SPE 6 1 16 0 1 0
STS-1-3v SPE 5 0 0 3 1 0
STS-3c-9v SPE 6 1 1 9 1 0
STS-12 Section transparent 9 0 0 0 1 1
3 x STS-768c SPE 6 1 256 0 3 0
5 x VC-4-13v 6 0 0 13 5 0
Normative References
[G.707] ITU-T Recommendation G.707, "Network Node Interface for
the Synchronous Digital Hierarchy", October 2000.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S.
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
Functional Specification", RFC 2205, September 1997.
[RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated
Services", RFC 2210, September 1997.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, December 2001.
[RFC3212] Jamoussi, B., Andersson, L., Callon, R., Dantu, R., Wu,
L., Doolan, P., Worster, T., Feldman, N., Fredette, A.,
Girish, M., Gray, E., Heinanen, J., Kilty, T., and A.
Malis, "Constraint-Based LSP Setup using LDP", RFC 3212,
January 2002.
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Functional Description", RFC 3471,
January 2003.
[RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized Multi-
Protocol Label Switching (GMPLS) Signaling Constraint-
based Routed Label Distribution Protocol (CR-LDP)
Extensions", RFC 3472, January 2003.
[RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Resource ReserVation Protocol-Traffic
Engineering (RSVP-TE) Extensions", RFC 3473, January
2003.
[RFC3945] Mannie, E., "Generalized Multi-Protocol Label Switching
(GMPLS) Architecture", RFC 3945, October 2004.
[T1.105] "Synchronous Optical Network (SONET): Basic Description
Including Multiplex Structure, Rates, and Formats", ANSI
T1.105, October 2000.
Authors' Addresses Authors' Addresses
Eric Mannie (Consultant) Eric Mannie
Avenue de la Folle Chanson, 2 Perceval
B-1050 Brussels, Belgium Rue Tenbosch, 9
Phone: +32 2 648-5023 1000 Brussels
Mobile: +32 (0)495-221775 Belgium
EMail: eric_mannie@hotmail.com Phone: +32-2-6409194
EMail: eric.mannie@perceval.net
Dimitri Papadimitriou (Alcatel) Dimitri Papadimitriou
Francis Wellesplein 1, Alcatel
Copernicuslaan 50
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
E.Mannie & D.Papadimitriou (Editors) 22
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on This document and the information contained herein are provided on an
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
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 Rights or other rights that might be claimed Intellectual Property Rights or other rights that might be claimed to
to pertain to the implementation or use of the technology pertain to the implementation or use of the technology described in
described in this document or the extent to which any license this document or the extent to which any license under such rights
under such rights might or might not be available; nor does it might or might not be available; nor does it represent that it has
represent that it has made any independent effort to identify any made any independent effort to identify any such rights. Information
such rights. Information on the IETF's procedures with respect to on the procedures with respect to rights in RFC documents can be
rights in IETF Documents can be found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use attempt made to obtain a general license or permission for the use of
of such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository specification can be obtained from the IETF on-line IPR repository at
at http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention The IETF invites any interested party to bring to its attention any
any copyrights, patents or patent applications, or other copyrights, patents or patent applications, or other proprietary
proprietary rights that may cover technology that may be required rights that may cover technology that may be required to implement
to implement this standard. Please address the information to the this standard. Please address the information to the IETF at
IETF at ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
E.Mannie & D.Papadimitriou (Editors) 23
 End of changes. 127 change blocks. 
683 lines changed or deleted 610 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/