draft-ietf-ccamp-gmpls-sonet-sdh-00.txt   draft-ietf-ccamp-gmpls-sonet-sdh-01.txt 
CCAMP Working Group Stefan Ansorge (Alcatel) CCAMP Working Group Eric Mannie (Ebone) - Editor
Internet Draft Peter Ashwood-Smith (Nortel) Internet Draft
Expiration Date: November 2001 Ayan Banerjee (Calient) Expiration Date: December 2001 Stefan Ansorge (Alcatel)
Peter Ashwood-Smith (Nortel)
Ayan Banerjee (Calient)
Lou Berger (Movaz) Lou Berger (Movaz)
Greg Bernstein (Ciena) Greg Bernstein (Ciena)
Angela Chiu (Celion) Angela Chiu (Celion)
John Drake (Calient) John Drake (Calient)
Yanhe Fan (Axiowave) Yanhe Fan (Axiowave)
Michele Fontana (Alcatel) Michele Fontana (Alcatel)
Gert Grammel (Alcatel) Gert Grammel (Alcatel)
Juergen Heiles(Siemens) Juergen Heiles(Siemens)
Suresh Katukam (Cisco) Suresh Katukam (Cisco)
Kireeti Kompella (Juniper) Kireeti Kompella (Juniper)
Jonathan P. Lang (Calient) Jonathan P. Lang (Calient)
Fong Liaw (Zaffire) Fong Liaw (Zaffire)
Zhi-Wei Lin (Lucent) Zhi-Wei Lin (Lucent)
Ben Mack-Crane (Tellabs) Ben Mack-Crane (Tellabs)
Dimitri Papadimitriou (Alcatel) Dimitri Papadimitriou (Alcatel)
Dimitrios Pendarakis (Tellium) Dimitrios Pendarakis (Tellium)
Mike Raftelis (White Rock) Mike Raftelis (White Rock)
Bala Rajagopalan (Tellium) Bala Rajagopalan (Tellium)
Yakov Rekhter (Juniper) Yakov Rekhter (Juniper)
Debanjan Saha (Tellium) Debanjan Saha (Tellium)
Vishal Sharma (Jasmine) Vishal Sharma (Metanoia)
George Swallow (Cisco) George Swallow (Cisco)
Z. Bo Tang (Tellium) Z. Bo Tang (Tellium)
Eve Varma (Lucent) Eve Varma (Lucent)
Maarten Vissers (Lucent) Maarten Vissers (Lucent)
Yangguang Xu (Lucent) Yangguang Xu (Lucent)
Eric Mannie (Ebone) - Editor June 2001
May 2001
GMPLS Extensions for SONET and SDH Control GMPLS Extensions for SONET and SDH Control
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt draft-ietf-ccamp-gmpls-sonet-sdh-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are all provisions of Section 10 of RFC2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), working documents of the Internet Engineering Task Force (IETF),
its areas, and its working groups. Note that other groups may its areas, and its working groups. Note that other groups may
also distribute working documents as Internet-Drafts. also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." progress."
E. Mannie Editor 1 E. Mannie Editor 1
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001 draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
To view the current status of any Internet-Draft, please check the To view the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in an Internet-Drafts Shadow "1id-abstracts.txt" listing contained in an Internet-Drafts Shadow
Directory, see http://www.ietf.org/shadow.html. Directory, see http://www.ietf.org/shadow.html.
Abstract Abstract
This document is a companion to the Generalized MPLS signaling This document is a companion to the Generalized MPLS signaling
documents, [GMPLS-SIG], [GMPLS-RSVP] and [GMPLS-LDP]. It defines documents, [GMPLS-SIG], [GMPLS-RSVP] and [GMPLS-LDP]. It defines
the SONET/SDH technology specific information needed when using the SONET/SDH technology specific information needed when using
GMPLS signaling. GMPLS signaling.
1. Introduction 1. Introduction
Generalized MPLS extends MPLS from supporting packet (Packet Generalized MPLS (GMPLS) extends MPLS from supporting packet
Switching Capable - PSC) interfaces and switching to include (Packet Switching Capable - PSC) interfaces and switching to
support of three new classes of interfaces and switching: Time- include support of three new classes of interfaces and switching:
Division Multiplex (TDM), Lambda Switch (LSC) and Fiber-Switch Time-Division Multiplex (TDM), Lambda Switch (LSC) and Fiber-
(FSC). A functional description of the extensions to MPLS Switch (FSC). A functional description of the extensions to MPLS
signaling needed to support the new classes of interfaces and signaling needed to support the new classes of interfaces and
switching is provided in [GMPLS-SIG]. [GMPLS-RSVP] describes RSVP- switching is provided in [GMPLS-SIG]. [GMPLS-RSVP] describes RSVP-
TE specific formats and mechanisms needed to support all four TE specific formats and mechanisms needed to support all four
classes of interfaces, and CR-LDP extensions can be found in classes of interfaces, and CR-LDP extensions can be found in
[GMPLS-LDP]. This document presents details that are specific to [GMPLS-LDP]. This document presents details that are specific to
SONET/SDH. Per [GMPLS-SIG], SONET/SDH specific parameters are SONET/SDH. Per [GMPLS-SIG], SONET/SDH specific parameters are
carried in the signaling protocol in traffic parameter specific carried in the signaling protocol in traffic parameter specific
objects. objects.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
skipping to change at line 96 skipping to change at line 96
in this document are to be interpreted as described in [RFC2119]. in this document are to be interpreted as described in [RFC2119].
2. SDH and SONET Traffic Parameters 2. SDH and SONET Traffic Parameters
This section defines the GMPLS traffic parameters for SONET/SDH. This section defines the GMPLS traffic parameters for SONET/SDH.
The protocol specific formats, for the SDH/SONET-specific RSVP-TE The protocol specific formats, for the SDH/SONET-specific RSVP-TE
objects and CR-LDP TLVs are described in sections 2.2 and 2.3 objects and CR-LDP TLVs are described in sections 2.2 and 2.3
respectively. respectively.
These traffic parameters specify indeed a base set of capabilities These traffic parameters specify indeed a base set of capabilities
for SONET (ANSI T1.105) and SDH (G.707) such as concatenation and for SONET (ANSI T1.105) and SDH (ITU-T G.707) such as
transparency. Other documents could enhance this set of concatenation and transparency. Other documents could enhance this
capabilities in the future. For instance, extensions to G.707 such set of capabilities in the future. For instance, signaling for SDH
as SDH over PDH, or sub-STM-0 interfaces could be defined. over PDH (ITU-T G.832), or sub-STM-0 (ITU-T G.708) interfaces
could be defined.
The traffic parameters defined hereafter MUST be used when The traffic parameters defined hereafter MUST be used when
SONET/SDH is specified in the LSP Encoding Type field of a SONET/SDH is specified in the LSP Encoding Type field of a
Generalized Label Request [GMPLS-SIG]. Generalized Label Request [GMPLS-SIG].
E. Mannie Editor Internet-Draft November 2001 2 E. Mannie Editor Internet-Draft December 2001 2
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001 draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
2.1. SONET/SDH Traffic Parameters 2.1. SONET/SDH Traffic Parameters
The traffic parameters for SONET/SDH is organized as follows: The traffic parameters for SONET/SDH is 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 | Resv | CCT | NCC | | Signal Type | RCC | NCC |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NVC | Multiplier (MT) | | NVC | Multiplier (MT) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transparency (T) | | Transparency (T) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Signal Type (ST): 8 bits Signal Type (ST): 8 bits
This field indicates the type of Elementary Signal that This field indicates the type of Elementary Signal that
comprises the requested LSP. Several transforms can be applied comprises the requested LSP. Several transforms can be applied
successively on the Elementary Signal to build the Final Signal successively on the Elementary Signal to build the Final Signal
being actually requested for the LSP. Each transform is being actually requested for the LSP.
optional and must be ignored if zero. Transforms must be
applied strictly in the following order:
-First, contiguous concatenation (by using the CCT and NCC Each transform is optional and must be ignored if zero, except
MT that cannot be zero and is ignored if equal to one.
Transforms must be applied strictly in the following order:
- First, contiguous concatenation (by using the RCC and NCC
fields) can be optionally applied on the Elementary Signal, fields) can be optionally applied on the Elementary Signal,
resulting in a contiguously concatenated signal. resulting in a contiguously concatenated signal.
-Second, virtual concatenation (by using the NVC field) can -Second, virtual concatenation (by using the NVC field) can
be optionally applied either directly on the Elementary be optionally applied either directly on the Elementary
Signal, or on the contiguously concatenated signal obtained Signal, or on the contiguously concatenated signal obtained
from the previous phase. This allows requesting the virtual from the previous phase (see Appendix 4).
concatenation of a contiguously concatenated signal, for
instance the virtual concatenation of STS-3c's, or any STS-
Xc's.
-Third, some transparency can be optionally specified when -Third, some transparency can be optionally specified when
requesting a frame as signal rather than an SPE or VC based requesting a frame as signal rather than an SPE or VC based
signal (by using the Transparency field). signal (by using the Transparency field).
-Fourth, a multiplication (by using the Multiplier field) can be -Fourth, a multiplication (by using the Multiplier field) can be
optionally applied either directly on the Elementary Signal, or optionally applied either directly on the Elementary Signal, or
on the contiguously concatenated signal obtained from the first on the contiguously concatenated signal obtained from the first
phase, or on the virtually concatenated signal obtained from phase, or on the virtually concatenated signal obtained from
the second phase, or on these signals combined with some the second phase, or on these signals combined with some
transparency. transparency.
E. Mannie Editor Internet-Draft November 2001 3 E. Mannie Editor Internet-Draft December 2001 3
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001 draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
Permitted Signal Type values for SDH are: Permitted Signal Type values for SONET/SDH are:
Value Type Value Type
----- ---- ----- -----------------
1 VC-11 1 VT1.5 SPE / VC-11
2 VC-12 2 VT2 SPE / VC-12
3 VC-2 3 VT3 SPE
4 TUG-2 4 VT6 SPE / VC-2
5 VC-3 5 STS-1 SPE / VC-3
6 "VC-3 via AU-3 at the end" (see comment hereafter) 6 STS-3c SPE / VC-4
7 TUG-3 7 STS-1 / STM-0 (only when requesting transparency)
8 VC-4 8 STS-3 / STM-1 (only when requesting transparency)
9 AUG-1 9 STS-12 / STM-4 (only when requesting transparency)
10 AUG-4 10 STS-48 / STM-16 (only when requesting transparency)
11 AUG-16 11 STS-192 / STM-64 (only when requesting transparency)
12 AUG-64 12 STS-768 / STM-256 (only when requesting transparency)
13 AUG-256
14 STM-1 (only when requesting transparency)
15 STM-4 (only when requesting transparency)
16 STM-16 (only when requesting transparency)
17 STM-64 (only when requesting transparency)
18 STM-256 (only when requesting transparency)
According to the G.707 standard a VC-3 in the TU-3/TUG-3/VC- A dedicated signal type is assigned to a SONET STS-3c SPE instead
4/AU-4 branch of the SDH multiplex cannot be structured in TUG- of coding it as a contiguous concatenation of three STS-1 SPEs.
2's, however a VC-3 in the AU-3 branch can be. In addition, a This was done in order to provide easy interworking between SONET
VC-3 could be switched between the two branches if required. In and SDH signaling.
some cases, it could be useful to indicate that the destination
LSR needs to receive a VC-3 via the AU-3 branch in order to be
able to demultiplex it into TUG-2's. 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 the
incoming VC-3 into 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 in the AU-3 at
some other places. The VC-3 signal type indicates that a VC-3
in any branch is suitable.
Administrative Unit Group-N's (AUG-N's) are either a homogeneous Refer to Appendix 1 and Appendix 2 for an extended set of signal
collection of AU-3s or AU-4s. When used as a signal type this type values beyond the signal types as defined in T1.105/G.707.
means that all the VC-3s or VC-4s in the AU-3s or AU-4s that
comprise the AUG-N are switched together as one unique signal. In
addition any contiguous concatenation relationships between the
VC-3s or VC-4s in the AUG-N are preserved and are allowed to
change over the life of an AUG-N. It is this flexibility in the
concatenation relationships between the component virtual
containers that differentiates this signal from a set of VC-3s or
VC-4s. In addition whether the AUG-N is structured with AU-3s or
AU-4s does not need to be specified and is allowed to change over
time. The same reasoning applies to TUG-2 and TUG-3 signal types.
E. Mannie Editor Internet-Draft November 2001 4 Requested Contiguous Concatenation (RCC): 8 bits
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001
Permitted Signal Type values for SONET are: This field is used to request and negotiate the optional
SONET/SDH contiguous concatenation of the Elementary Signal.
Value Type This field is a vector of flags. Each flag indicates the
----- ---- support of a particular type of contiguous concatenation.
1 VT1.5 Several flags can be set at the same time to indicate a choice.
2 VT2
3 VT3
4 VT6
5 VTG
6 STS-1 SPE
7 STS Group-3
8 STS Group-12
9 STS Group-48
10 STS Group-192
11 STS Group-768
12 STS-1 (only when requesting transparency)
13 STS-3 (only when requesting transparency)
14 STS-12 (only when requesting transparency)
15 STS-48 (only when requesting transparency)
16 STS-192 (only when requesting transparency)
17 STS-768 (only when requesting transparency)
STS Group-N is a collection of STS-1 SPE signals whose contiguous These flags allow an upstream node to indicate to a downstream
concatenation relationship within the group need not be defined node the different types of contiguous concatenation that it
and is permitted to change during the life of the STS-Group-N. It supports. However, the downstream node decides which one to use
is this flexibility in the concatenation relationships between the according to its own rules.
component STS-1 SPE's that differentiates this signal from a set
of STS-1 SPE's. For example an STS Group-48 could at one time
consist of four STS-12c signals and at another point in times of
three STS-12c signals and four STS-3c signals. The same reasoning
applies to the VTG signal type.
Reserved: 5 bits A downstream node receiving such flags chooses, as it likes, a
particular type of contiguous concatenation, if any supported.
A downstream 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.
Reserved bits should be set to zero when sent and must be ignored The upstream node can know which type of contiguous
when received. concatenation the downstream node chosen by looking at the
position indicated by the first label and the number of
label(s) as returned by the downstream node.
Contiguous Concatenation Type (CCT): 3 bits E. Mannie Editor Internet-Draft December 2001 4
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
This field indicates the type of SONET/SDH contiguous The entire field is set to zero to indicate that no contiguous
concatenation to apply on the Elementary Signal. It is set to concatenation is requested at all (default value). A non-zero
zero to indicate that no contiguous concatenation is requested field indicates that some contiguous concatenation is being
(default value). The values are defined in the following table: requested.
Bits Contiguous Concatenation Type The following flag is defined:
----- ----------------------------------
000 No contiguous concatenation requested
001 Standard contiguous concatenation
010 Arbitrary contiguous concatenation
others Vendor specific concatenation types
E. Mannie Editor Internet-Draft November 2001 5 Flag 1 (bit 1): Standard contiguous concatenation.
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001
Flag 1 indicates that only 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 should 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
contiguous concatenation of STS-1 SPEs when the number of
components is a multiple of three.
Refer to Appendix 3 for an extended set of contiguous
concatenation types beyond the contiguous concatenation types as
defined in T1.105/G.707.
Number of Contiguous Components (NCC): 16 bits Number of Contiguous Components (NCC): 16 bits
This field indicates the number of identical SONET/SDH This field indicates the number of identical SONET/SDH SPEs/VCs
SPE's/VC's that are requested to be contiguously concatenated, that are requested to be concatenated, as specified in the RCC
as specified in the CCT field. field.
Note 1: when requesting a SONET STS-Nc SPE with N=3*X, the
elementary signal to use must always be an STS-3c SPE signal
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 cannot 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 STM-N/STS-N signal
limited to a single contiguously concatenated VC-4-Nc/STS-Nc-
SPE, the signal type must be STM-N/STS-N, RCC with flag 1 and
NCC set to 1.
This field is irrelevant if no contiguous concatenation is This field is irrelevant if no contiguous concatenation is
requested (CCT = 0), in that case it must be set to zero when requested (RCC = 0), in that case it must be set to zero when
generated. A CCT value different from 0 must imply a number of send, and should be ignored when received. A RCC value
components greater than 1. different from 0 must imply a number of components greater than
1.
E. Mannie Editor Internet-Draft December 2001 5
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
Number of Virtual Components (NVC): 16 bits Number of Virtual Components (NVC): 16 bits
This field indicates the number of identical signals that are This field indicates the number of signals that are requested
requested to be virtually concatenated. These signals can be to be virtually concatenated. These signals are all of the same
either identical Elementary Signal's SPE's/VC's, or identical type by definition. They are Elementary Signal SPEs/VCs for
contiguously concatenated signals. In this last case, it allows which signal types are defined.
to request the virtual concatenation of contiguously
concatenated signals, for instance the virtual concatenation of
several STS-3c SPE's, or any STS-Xc SPE's (to obtain an STS-Xc-
Yv SPE).
This field is set to 0 (default value) to indicate that no This field is set to 0 (default value) to indicate that no
virtual concatenation is requested. virtual concatenation is requested.
Refer to Appendix 4 for an extended set of signals that can be
virtually concatenated beyond the virtual concatenation as defined
in T1.105/G.707.
Multiplier (MT): 16 bits Multiplier (MT): 16 bits
This field indicates the number of identical signals that are This field indicates the number of identical signals that are
requested for the LSP, i.e. that form the Final Signal. These requested for the LSP, i.e. that form the Final Signal. These
signals can be either identical Elementary Signal's, or signals can be either identical Elementary Signals, or
identical contiguously concatenated signals, or identical identical contiguously concatenated signals, or identical
virtually concatenated signals. Note that all these signals virtually concatenated signals. Note that all these signals
belongs thus to the same LSP. belongs thus to the same LSP.
The distinction between the components of multiple virtually The distinction between the components of multiple virtually
concatenated signals is done via the order of the labels that concatenated signals is done via the order of the labels that
are specified in the signaling. The first set of labels must are specified in the signaling. The first set of labels must
describe the first component (set of individual signals describe the first component (set of individual signals
belonging to the first virtual concatenated signal), the second belonging to the first virtual concatenated signal), the second
set must describe the second component (set of individual set must describe the second component (set of individual
signals belonging to the second virtual concatenated signal) signals belonging to the second virtual concatenated signal)
and so on. and so on.
This field is set to one (default value) to indicate that This field is set to one (default value) to indicate that
exactly one instance of a signal is being requested. Zero is an exactly one instance of a signal is being requested. Zero is an
invalid value. invalid value.
Transparency (T): 32 bits Transparency (T): 32 bits
This field is a vector of flags that indicates the type of This field is a vector of flags that indicates the type of
transparency being requested. Several flags can be combined transparency being requested. Several flags can be combined to
to provide different types of transparency. Not all provide different types of transparency. Not all combinations
combinations are necessarily valid. are necessarily valid. The default value for this field is
zero, i.e. no transparency requested.
E. Mannie Editor Internet-Draft November 2001 6 Transparency as defined from the point of view of this
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001 signaling specification is only applicable to the fields in the
SONET/SDH frame overheads. In the SONET case, these are the
fields in the Section Overhead (SOH), and the Line Overhead
(LOH). In the SDH case, these are the fields in the Regenerator
Section Overhead (RSOH), the Multiplex Section overhead (MSOH),
and the pointer fields between the two. With SONET, the pointer
fields are part of the LOH.
Transparency is only applicable to the fields in the SONET/SDH E. Mannie Editor Internet-Draft December 2001 6
frame overheads. In the SONET case, these are the fields in the draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
Section Overhead (SOH), and the Line Overhead (LOH). In the SDH
case, these are the fields in the Regenerator Section Overhead
(RSOH), the Multiplex Section overhead (MSOH), and the pointer
fields between the two. With SONET, the pointer fields are
defined as being 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 following Signal Types (ST's): STM-1, STM-4, STM-16, STM- the following Signal Types: STM-0, STM-1, STM-4, STM-16, STM-
64, STM-256, STS-1, STS-3, STS-12, STS-48, STS-192, and STS- 64, STM-256, STS-1, STS-3, STS-12, STS-48, STS-192, and STS-
768. At least one transparency type must be specified when 768. At least one transparency type must be specified when
requesting such a signal type. requesting such a signal type.
Transparency indicates precisely which fields in these Transparency indicates precisely which fields in these
overheads must be delivered unmodified at the other end of the overheads must be delivered unmodified at the other end of the
LSP. An ingress LSR requesting transparency will pass these LSP. An ingress LSR requesting transparency will pass these
overhead fields that must be delivered to the egress LSR overhead fields that must be delivered to the egress LSR
without any change. From the ingress and egress LSR's point of without any change. From the ingress and egress LSRs point of
views, these fields must be seen as unmodified. views, these fields must be seen as unmodified.
Note that B1 in the SOH/RSOH is computed over the complete Transparency is not applied at the interfaces with the
previous frame, if one bit changes, B1 must be re-computed. initiating and terminating LSRs, but is only applied between
Note that B2 in the LOH/MSOH is also computed over the complete intermediate LSRs.
previous frame, except the SOH/RSOH.
This specification neither addresses how this process is
achieved nor network deployment scenarios. The signaling is
independent of these consideration (For example, fields could
be simply unmofified or could be tunneled into unused overhead
bytes).
Several transparency types are defined below. Other
transparency types are for further study.
The transparency field is used to request an LSP that supports The transparency field is used to request an LSP that supports
the requested transparency, it may also be used to setup the the requested transparency type; it may also be used to setup
transparency process to be applied in each intermediate LSR. the transparency process to be applied in each intermediate
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.
flag 3 (bit 3) : J0.
flag 4 (bit 4) : SOH/RSOH DCC (D1-D3).
flag 5 (bit 5) : LOH/MSOH DCC (D4-D12).
flag 6 (bit 6) : LOH/MSOH Extended DCC (D13-D156).
flag 7 (bit 7) : K1/K2.
flag 8 (bit 8) : E1.
flag 9 (bit 9) : F1.
flag 10 (bit 10): E2.
Where bit 1 is the low order bit. Others flags are reserved, Where bit 1 is the low order bit. Others flags are reserved,
they should be set to zero when sent, and should be ignored they should be set to zero when sent, and should be ignored
E. Mannie Editor Internet-Draft November 2001 7
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001
when received. A flag is set to one to indicate that the when received. A flag is set to one to indicate that the
corresponding transparency is requested. corresponding transparency is requested.
Section/Regenerator Section layer transparency means that the Section/Regenerator Section layer transparency means that the
entire frames must be delivered unmodified. This implies that entire frames must be delivered unmodified. This implies that
pointers cannot be adjusted. When using Section/Regenerator pointers cannot be adjusted. When using Section/Regenerator
Section layer transparency all other flags must be ignored. Section layer transparency all other flags must be ignored.
Line/Multiplex Section layer transparency means that the Line/Multiplex Section layer transparency means that the
LOH/MSOH must be delivered unmodified. This implies that LOH/MSOH must be delivered unmodified. This implies that
pointers cannot be adjusted. Line/Multiplex Section layer pointers cannot be adjusted.
transparency can be combined only with any of the following
transparency types: J0, SOH/RSOH DCC (D1-D3), E1, F1; and all
other transparency flags must be ignored.
Note that the extended LOH/MSOH DCC (D13-D156) is only Refer to Appendix 5 for an extended set of transparency types
applicable to (defined for) STS-768/STM-256. beyond the transparency types as defined in T1.105/G.707.
2.2. RSVP-TE Details 2.2. RSVP-TE Details
For RSVP-TE, the SONET/SDH traffic parameters are carried in the For RSVP-TE, the SONET/SDH traffic parameters are carried in the
SONET/SDH SENDER_TSPEC and FLOWSPEC objects. The same format is SONET/SDH SENDER_TSPEC and FLOWSPEC objects. The same format is
used both for SENDER_TSPEC object and FLOWSPEC objects. The used both for SENDER_TSPEC object and FLOWSPEC objects. The
contents of the objects is defined above in Section 2.1. The contents of the objects is defined above in Section 2.1. The
objects have the following class and type: objects have the following class and type:
E. Mannie Editor Internet-Draft December 2001 7
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
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 = 4 (TBA) SONET/SDH SENDER_TSPEC object: Class = 12, C-Type = 4 (TBA)
SONET/SDH FLOWSPEC object: Class = 9, C-Type = 4 (TBA) SONET/SDH FLOWSPEC object: Class = 9, C-Type = 4 (TBA)
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 General Characterization Parameters and Guaranteed Service Default General Characterization Parameters and Guaranteed Service
fragment is used, see [RFC2210]. fragment is used, see [RFC2210].
For a particular sender in a session the contents of the FLOWSPEC For a particular sender in a session the contents of the FLOWSPEC
object received in a Resv message SHOULD be identical to the object received in a Resv message SHOULD be identical to the
contents of the SENDER_TSPEC object received in the corresponding contents of the SENDER_TSPEC object received in the corresponding
Path message. If the objects do not match, a ResvErr message with Path message. If the objects do not match, a ResvErr message with
a "Traffic Control Error/Bad Flowspec value" error SHOULD be a "Traffic Control Error/Bad Flowspec value" error SHOULD be
generated. generated.
E. Mannie Editor Internet-Draft November 2001 8
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001
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 contents of the TLV is SONET/SDH Traffic Parameters TLV. The contents of the TLV is
defined above in Section 2.1. The header of the TLV has the defined above in Section 2.1. The header of the TLV has the
following format: following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F| Type | Length | |U|F| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The type field indicates either SONET or SDH: The type field indicates either SONET or SDH:
For SONET ANSI T1.105 : 0xTBA. For SONET ANSI T1.105 : 0xTBA.
For SDH ITU-T G.707 : 0xTBA. For SDH ITU-T G.707 : 0xTBA.
3. SDH and SONET Labels 3. SDH and SONET Labels
SDH and SONET each define a multiplexing structure. These two SDH and SONET each define a multiplexing structure, with the SONET
structures are trees whose roots are respectively an STM-N or an multiplex structure being a subset of the SDH multiplex structure.
STS-N; and whose leaves are the signals (time-slots) that can be These two structures are trees whose roots are respectively an
transported and switched, i.e. a VC-x or a VT-x. An SDH/SONET STM-N or an STS-N; and whose leaves are the signals that can be
label will identify the exact position of a particular signal in a transported via the time-slots and switched between time-slots,
multiplexing structure. SDH and SONET labels are carried in the i.e. a VC-x or a VT-x. An SDH/SONET label will identify the exact
Generalized Label per [GMPLS-RSVP] and [GMPLS-LDP]. position of a particular signal in a multiplexing structure. SDH
and SONET labels are carried in the Generalized Label per [GMPLS-
RSVP] and [GMPLS-LDP].
These multiplexing structures will be used as naming trees to These multiplexing structures will be used as naming trees to
create unique multiplex entry names or labels. Since the SONET create unique multiplex entry names or labels. Since the SONET
multiplexing structure may be seen as a subset of the SDH multiplexing structure may be seen as a subset of the SDH
multiplexing structure, the same format of label is used for SDH multiplexing structure, the same format of label is used for SDH
and SONET. As explained in [GMPLS-SIG], a label does not identify and SONET. As explained in [GMPLS-SIG], a label does not identify
E. Mannie Editor Internet-Draft December 2001 8
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
the "class" to which the label belongs. This is implicitly the "class" to which the label belongs. This is implicitly
determined by the link on which the label is used. However, in determined by the link on which the label is used. However, in
some cases the encoding specified hereafter can make the direct some cases the encoding specified hereafter can make the direct
distinction between SDH and SONET. distinction between SDH and SONET.
In case of signal concatenation or multiplication, a list of In case of signal concatenation or multiplication, a list of
labels can appear in the Label field of a Generalized Label. labels can appear in the Label field of a Generalized Label.
In case of any type of contiguous concatenation (e.g. standard or In case of any type of contiguous concatenation, only one label
arbitrary concatenation), only one label appears in the Label appears in the Label field. That label is the lowest signal of the
field. That label is the lowest signal of the contiguously contiguously concatenated signal. By lowest signal we mean the one
concatenated signal. By lowest signal we mean the one having the having the lowest label when compared as integer values, i.e. the
lowest label when compared as integer values, i.e. the first first component signal of the concatenated signal encountered when
component signal of the concatenated signal 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. Each label indicates a labels in the concatenation is given. Each label indicates a
component of the virtually concatenated signal. The order of the component of the virtually concatenated signal. The order of the
E. Mannie Editor Internet-Draft November 2001 9
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001
labels must reflect the order of the payloads to concatenate (not labels must reflect the order of the payloads to concatenate (not
the physical order of time-slots). The above representation limits the physical order of time-slots). The above representation limits
virtual concatenation to remain within a single (component) link. virtual concatenation to remain within a single (component) link;
it imposes as such a restriction compared to the specification in
G.707/T1.105.
In case of multiplication (i.e. using the multiplier transform), In case of multiplication (i.e. using the multiplier transform),
the explicit ordered list of all labels that take part in the the explicit ordered list of all labels that take part in the
Final Signal is given. In case of multiplication of virtually Final Signal is given. In case of multiplication of virtually
concatenated signals, the first set of labels indicates the first concatenated signals, the first set of labels indicates the first
virtually concatenated signal, the second set of labels indicates virtually concatenated signal, the second set of labels indicates
the second virtually concatenated signal, and so on. The above the second virtually concatenated signal, and so on. The above
representation limits multiplication to remain within a single representation limits multiplication to remain within a single
(component) link. (component) link.
skipping to change at line 512 skipping to change at line 481
and K fields are not significant and must be set to zero. Only the and K fields are not significant and must be set to zero. Only the
S, L and M fields are significant for SONET and have a similar S, L and M fields are significant for SONET and have a similar
meaning as for SDH. meaning as for SDH.
Each letter indicates a possible branch number starting at the Each letter indicates a possible branch number starting at the
parent node in the multiplex structure. Branches are considered as parent node in the multiplex structure. Branches are considered as
numbered in increasing order, starting from the top of the numbered in increasing order, starting from the top of the
multiplexing structure. The numbering starts at 1, zero is used to multiplexing structure. The numbering starts at 1, zero is used to
indicate a non-significant field. indicate a non-significant field.
E. Mannie Editor Internet-Draft December 2001 9
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
When a field is not significant in a particular context it MUST be When a field is not significant in a particular context it MUST be
set to zero when transmitted, and MUST be ignored when received. set to zero when transmitted, and MUST be ignored when received.
When hierarchical SDH/SONET LSPs are used, an LSP with a given When hierarchical SDH/SONET LSPs are used, an LSP with a given
bandwidth can be used to tunnel lower order LSPs. The higher bandwidth can be used to tunnel lower order LSPs. The higher
order SDH/SONET LSP behaves as a virtual link with a given order SDH/SONET LSP behaves as a virtual link with a given
bandwidth (e.g. VC-3), it may also be used as a Forwarding bandwidth (e.g. VC-3), it may also be used as a Forwarding
Adjacency. A lower order SDH/SONET LSP can be established through Adjacency. A lower order SDH/SONET LSP can be established through
that higher order LSP. Since a label is local to a (virtual) link, that higher order LSP. Since a label is local to a (virtual) link,
the highest part of that label is non-significant and is set to the highest part of that label is non-significant and is set to
zero. zero.
For instance, a VC-3 LSP can be advertised as a forwarding For instance, a VC-3 LSP can be advertised as a forwarding
adjacency. In that case all labels allocated between the two ends adjacency. In that case all labels allocated between the two ends
of that LSP will have S, U and K set to zero, i.e., non- of that LSP will have S, U and K set to zero, i.e., non-
significant, while L and M will be used to indicate the signal significant, while L and M will be used to indicate the signal
allocated in that VC-3. allocated in that VC-3.
1. S is the index of a particular STM-1/STS-1 signal. S=1->N 1. S is the index of a particular AUG-1/STS-1. S=1->N indicates
indicates a specific STM-1/STS-1 inside an STM-N/STS-N a specific AUG-1/STS-1 inside an STM-N/STS-N multiplex. For
example, S=1 indicates the first AUG-1/STS-1, and S=N indicates
E. Mannie Editor Internet-Draft November 2001 10 the last AUG-1/STS-1 of this multiplex.
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001
multiplex. For example, S=1 indicates the first STM-1/STS-1, and
S=N indicates the last STM-1/STS-1 of this multiplex.
2. U is only significant for SDH and must be ignored for SONET. 2. U is only significant for SDH and must be ignored for SONET.
It indicates a specific VC inside a given STM-1. U=1 indicates a It indicates a specific VC inside a given AUG-1. U=1 indicates a
single VC-4, while U=2->4 indicates a specific VC-3 inside the single VC-4, while U=2->4 indicates a specific VC-3 inside the
given STM-1. given AUG-1.
3. K is only significant for SDH and must be ignored for SONET. 3. K is only significant for SDH VC-4 and must be ignored for
It indicates a specific branch of a VC-4. K=1 indicates that the SONET and SDH HOVC-3. It indicates a specific branch of a VC-4.
VC-4 is not further subdivided and contains a C-4. K=2->4 K=1 indicates that the VC-4 is not further subdivided and
indicates a specific TUG-3 inside the VC-4. K is not significant contains a C-4. K=2->4 indicates a specific TUG-3 inside the VC-
when the STM-1 is divided into VC-3s (easy to read and test). 4. K is not significant when the AUG-1 is divided into AU-3s
(easy to read and test).
4. L indicates a specific branch of a TUG-3, VC-3 or STS-1 SPE. 4. L indicates a specific branch of a TUG-3, VC-3 or STS-1 SPE.
It is not significant for an unstructured VC-4. L=1 indicates It is not significant for an unstructured VC-4 or STS-1 SPE. L=1
that the TUG-3/VC-3/STS-1 SPE is not further subdivided and indicates that the TUG-3/VC-3/STS-1 SPE is not further
contains a VC-3/C-3 in SDH or the equivalent in SONET. L=2->8 subdivided and contains a VC-3/C-3 in SDH or the equivalent in
indicates a specific TUG-2/VT Group inside the corresponding SONET. L=2->8 indicates a specific TUG-2/VT Group inside the
higher order signal. corresponding higher order signal.
5. M indicates a specific branch of a TUG-2/VT Group. It is not 5. M indicates a specific branch of a TUG-2/VT Group. It is not
significant for an unstructured VC-4, TUG-3, VC-3 or STS-1 SPE. significant for an unstructured VC-4, TUG-3, VC-3 or STS-1 SPE.
M=1 indicates that the TUG-2/VT Group is not further subdivided M=1 indicates that the TUG-2/VT Group is not further subdivided
and contains a VC-2/VT-6. M=2->3 indicates a specific VT-3 and contains a VC-2/VT-6 SPE. M=2->3 indicates a specific VT-3
inside the corresponding VT Group, these values MUST NOT be used inside the corresponding VT Group, these values MUST NOT be used
for SDH since there is no equivalent of VT-3 with SDH. M=4->6 for SDH since there is no equivalent of VT-3 with SDH. M=4->6
indicates a specific VC-12/VT-2 inside the corresponding TUG- indicates a specific VC-12/VT-2 SPE inside the corresponding
2/VT Group. M=7->10 indicates a specific VC-11/VT-1.5 inside the TUG-2/VT Group. M=7->10 indicates a specific VC-11/VT-1.5 SPE
corresponding TUG-2/VT Group. Note that M=0 denotes an inside the corresponding TUG-2/VT Group. Note that M=0 denotes
unstructured VC-4, VC-3 or STS-1 SPE (easy for debugging). an unstructured VC-4, VC-3 or STS-1 SPE (easy for debugging).
E. Mannie Editor Internet-Draft December 2001 10
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
The M encoding is summarized in the following table: The M encoding is summarized in the following table:
M SDH SONET M SDH SONET
---------------------------------------------------------- ----------------------------------------------------------
0 unstructured VC-4/VC-3 unstructured STS-1 SPE 0 unstructured VC-4/VC-3 unstructured STS-1 SPE
1 VC-2 VT-6 1 VC-2 VT-6
2 - 1st VT-3 2 - 1st VT-3
3 - 2nd VT-3 3 - 2nd VT-3
4 1st VC-12 1st VT-2 4 1st VC-12 1st VT-2
skipping to change at line 590 skipping to change at line 562
8 2nd VC-11 2nd VT-1.5 8 2nd VC-11 2nd VT-1.5
9 3rd VC-11 3rd VT-1.5 9 3rd VC-11 3rd VT-1.5
10 4th VC-11 4th VT-1.5 10 4th VC-11 4th VT-1.5
In case of contiguous concatenation, the label that is used is the In case of contiguous concatenation, the label that is used is the
lowest label of the contiguously concatenated signal as explained lowest label of the contiguously concatenated signal as explained
before. The higher part of the label indicates where the signal before. The higher part of the label indicates where the signal
starts and the lowest part is not significant. For instance, when starts and the lowest part is not significant. For instance, when
requesting an STS-48c the label is S>0, U=0, K=0, L=0, M=0. requesting an STS-48c the label is S>0, U=0, K=0, L=0, M=0.
E. Mannie Editor Internet-Draft November 2001 11
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001
Examples of labels: Examples of labels:
Example 1: S>0, U=1, K=1, L=0, M=0 Example 1: S>0, U=1, K=1, L=0, M=0
Denotes the unstructured VC-4 of the Sth STM-1. Denotes the unstructured VC-4 of the Sth AUG-1.
Example 2: S>0, U=1, K>1, L=1, M=0 Example 2: S>0, U=1, K>1, L=1, M=0
Denotes the unstructured VC-3 of the Kth-1 TUG-3 of the Sth STM-1. Denotes the unstructured VC-3 of the Kth-1 TUG-3 of the Sth AUG-1.
Example 3: S>0, U=0, K=0, L=0, M=0 Example 3: S>0, U=0, K=0, L=0, M=0
Denotes the unstructured STM-1/STS-1 SPE of the Sth STM-1/STS-1. Denotes the unstructured SPE of the Sth STS-1.
Example 4: S>0, U=0, K=0, L>1, M=1 Example 4: S>0, U=0, K=0, L>1, M=1
Denotes the VT-6 in the Lth-1 VT Group in the Sth STS-1. Denotes the VT-6 in the Lth-1 VT Group in the Sth STS-1.
Example 5: S>0, U=0, K=0, L>1, M=9 Example 5: S>0, U=0, K=0, L>1, M=9
Denotes the 3rd VT-1.5 in the Lth-1 VT Group in the Sth STS-1. Denotes the 3rd VT-1.5 in the Lth-1 VT Group in the Sth STS-1.
4. Examples of SONET and SDH signals 4. Acknowledgments
As stated above, signal types are Elementary Signals to which
successive concatenation, multiplication and transparency
transforms can be applied.
1. A VC-4 signal is formed by the application of CCT with value 0,
NVC with value 0 (no concatenation), 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 CCT 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 CCT 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.
5. An STM-16 signal with Multiplex Section layer transparency is
formed by the application of CCT with value 0, NVC with value 0,
MT with value 1 and T with flag 2 to an STM-16 Elementary Signal.
6. An STM-64 signal with RSOH and MSOH DCC's transparency is
formed by the application of CCT with value 0, NVC with value 0,
MT with value 1 and T with flag 4 and 5 to an STM-64 Elementary
Signal.
7. An STM-4c signal (i.e. VC-4-4C with the transport overhead)
with Multiplex Section layer transparency is formed by the
application of CCT with value 1, NCC with value 4, NVC with value
0, MT with value 1 and T with flag 2 applied to an STM-4
Elementary Signal.
8. An STM-256c signal with Multiplex Section layer transparency is
formed by the application of CCT with value 1, NCC with value 256,
E. Mannie Editor Internet-Draft November 2001 12
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001
NVC with value 0, MT with value 1 and T with flag 2 applied to an
STM-256 Elementary Signal.
9. An STS-1 SPE signal is formed by the application of CCT with
value 0, NVC with value 0, MT with value 1 and T with value 0 to
an STS-1 SPE Elementary Signal.
10. An STS-3c SPE signal is formed by the application of CCT with
value 1 (standard contiguous concatenation), NCC with value 3, NVC
with value 0, MT with value 1 and T with value 0 to an STS-1 SPE
Elementary Signal.
11. An STS-48c SPE signal is formed by the application of CCT with
value 1 (standard contiguous concatenation), NCC with value 48,
NVC with value 0, MT with value 1 and T with value 0 to an STS-1
SPE Elementary Signal.
12. An STS-1-3v SPE signal is formed by the application of CCT
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.
13. An STS-3c-9v SPE signal is formed by the application of CCT
with value 1 (standard contiguous concatenation), NCC with value
3, NVC with value 9 (virtual concatenation of 9 STS-3c), MT with
value 1 and T with value 0 to an STS-1 SPE Elementary Signal.
14. An STS-12 signal with Section layer (full) transparency is
formed by the application of CCT with value 0, NVC with value 0,
MT with value 1 and T with flag 1 to an STS-12 Elementary Signal.
15. An STS-192 signal with K1/K2 and LOH DCC transparency is
formed by the application of CCT with value 0, NVC with value 0,
MT with value 1 and T with flags 5 and 7 to an STS-192 Elementary
Signal.
16. An STS-48c signal with LOH DCC and E2 transparency is formed
by the application of CCT with Type 1, NCC with value 48, NVC with
value 0, MT with value 1 and T with flag 5 and 10 to an STS-48
Elementary Signal.
17. An STS-768c signal with K1/K2 and LOH DCC transparency is
formed by the application of CCT with Type 1, NCC with value 768,
NVC with value 0, MT with value 1 and T with flag 5 and 7 to an
STS-768 Elementary Signal.
18. 4 x STS-12 signals with K1/K2 and LOH DCC transparency is
formed by the application of CCT with value 0, NVC with value 0,
MT with value 4 and T with flags 5 and 7 to an STS-12 Elementary
Signal.
19. 3 x STS-768c SPE signal is formed by the application of CCT
with value 1, NCC with value 768, NVC with value 0, MT with value
3, and T with value 0 to an STS-1 SPE Elementary Signal.
E. Mannie Editor Internet-Draft November 2001 13
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001
20. 5 x VC-4-13v composed signal is formed by the application of
CCT with value 0, NVC with value 13, MT with value 5 and T with
value 0 to a VC-4 Elementary Signal.
21. 2 x STS-4a-5v SPE signal is formed by the application of CCT
with value 2 (for arbitrary concatenation), NCC with value 4, NVC
with value 5, MT with value 2 and T with value 0 to an STS-1 SPE
Elementary Signal.
5. Acknowledgments
Valuable comments and input were received from many people. Valuable comments and input were received from many people.
6. Security Considerations 5. Security Considerations
This draft introduce no new security considerations to either This draft introduce no new security considerations to either
[GMPLS-RSVP] or [GMPLS-LDP]. [GMPLS-RSVP] or [GMPLS-LDP].
7. References E. Mannie Editor Internet-Draft December 2001 11
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
[GMPLS-LDP] Ashwood-Smith, P. et al, "Generalized MPLS Signaling - 6. References
CR-LDP Extensions", Internet Draft,
draft-ietf-mpls-generalized-cr-ldp-02.txt,
April, 2001.
[GMPLS-SIG] Ashwood-Smith, P. et al, "Generalized MPLS - [GMPLS-SIG] Ashwood-Smith, P. et al, "Generalized MPLS -
Signaling Functional Description", Internet Draft, Signaling Functional Description", Internet Draft,
draft-ietf-mpls-generalized-signaling-02.txt, draft-ietf-mpls-generalized-signaling-04.txt,
February 2001. May 2001.
[GMPLS-LDP] Ashwood-Smith, P. et al, "Generalized MPLS Signaling -
CR-LDP Extensions", Internet Draft,
draft-ietf-mpls-generalized-cr-ldp-03.txt,
May 2001.
[GMPLS-RSVP] Ashwood-Smith, P. et al, "Generalized MPLS [GMPLS-RSVP] Ashwood-Smith, P. et al, "Generalized MPLS
Signaling - RSVP-TE Extensions", Internet Draft, Signaling - RSVP-TE Extensions", Internet Draft,
draft-ietf-mpls-generalized-rsvp-te-02.txt, draft-ietf-mpls-generalized-rsvp-te-03.txt,
April, 2001. May 2001.
[GMPLS-ARCH] E. Mannie Editor, "GMPLS Architecture", Internet [GMPLS-ARCH] E. Mannie Editor, "GMPLS Architecture", Internet
Draft, draft-many-gmpls-architecture-00.txt, March, Draft, draft-many-gmpls-architecture-00.txt, March
2001. 2001.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels," RFC 2119. Requirement Levels," RFC 2119.
[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.
E. Mannie Editor Internet-Draft November 2001 14 7. Authors Addresses
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001
8. Authors' Addresses Stefan Ansorge
Alcatel SEL AG
Lorenzstrasse 10
70435 Stuttgart
Germany
Phone: +49 7 11 821 337 44
Email: Stefan.ansorge@alcatel.de
Peter Ashwood-Smith Peter Ashwood-Smith
Nortel Networks Corp. Nortel Networks Corp.
P.O. Box 3511 Station C, P.O. Box 3511 Station C,
Ottawa, ON K1Y 4H7 Ottawa, ON K1Y 4H7
Canada Canada
Phone: +1 613 763 4534 Phone: +1 613 763 4534
Email: petera@nortelnetworks.com Email: petera@nortelnetworks.com
Ayan Banerjee Ayan Banerjee
Calient Networks Calient Networks
5853 Rue Ferrari 5853 Rue Ferrari
San Jose, CA 95138 San Jose, CA 95138
Phone: +1 408 972-3645 Phone: +1 408 972-3645
Email: abanerjee@calient.net Email: abanerjee@calient.net
E. Mannie Editor Internet-Draft December 2001 12
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
Lou Berger Lou Berger
Movaz Networks, Inc. Movaz Networks, Inc.
7926 Jones Branch Drive 7926 Jones Branch Drive
Suite 615 Suite 615
McLean VA, 22102 McLean VA, 22102
Phone: +1 703 847-1801 Phone: +1 703 847-1801
Email: lberger@movaz.com Email: lberger@movaz.com
Greg Bernstein Greg Bernstein
Ciena Corporation Ciena Corporation
skipping to change at line 809 skipping to change at line 682
Phone: +1 408 972 3720 Phone: +1 408 972 3720
Email: jdrake@calient.net Email: jdrake@calient.net
Yanhe Fan Yanhe Fan
Axiowave Networks, Inc. Axiowave Networks, Inc.
100 Nickerson Road 100 Nickerson Road
Marlborough, MA 01752 Marlborough, MA 01752
Phone: +1 508 460 6969 Ext. 627 Phone: +1 508 460 6969 Ext. 627
Email: yfan@axiowave.com Email: yfan@axiowave.com
E. Mannie Editor Internet-Draft November 2001 15
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001
Michele Fontana Michele Fontana
Alcatel TND-Vimercate Alcatel TND-Vimercate
Via Trento 30, Via Trento 30,
I-20059 Vimercate, Italy I-20059 Vimercate, Italy
Phone: +39 039 686-7053 Phone: +39 039 686-7053
Email: michele.fontana@netit.alcatel.it Email: michele.fontana@netit.alcatel.it
Gert Grammel Gert Grammel
Alcatel TND-Vimercate Alcatel TND-Vimercate
Via Trento 30, Via Trento 30,
I-20059 Vimercate, Italy I-20059 Vimercate, Italy
Phone: +39 039 686-7060 Phone: +39 039 686-7060
Email: gert.grammel@netit.alcatel.it Email: gert.grammel@netit.alcatel.it
E. Mannie Editor Internet-Draft December 2001 13
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
Juergen Heiles Juergen Heiles
Siemens AG Siemens AG
Hofmannstr. 51 Hofmannstr. 51
D-81379 Munich, Germany D-81379 Munich, Germany
Phone: +49 89 7 22 - 4 86 64 Phone: +49 89 7 22 - 4 86 64
Email: Juergen.Heiles@icn.siemens.de Email: Juergen.Heiles@icn.siemens.de
Suresh Katukam Suresh Katukam
Cisco Systems Cisco Systems
1450 N. McDowell Blvd, 1450 N. McDowell Blvd,
skipping to change at line 861 skipping to change at line 734
Zhi-Wei Lin Zhi-Wei Lin
101 Crawfords Corner Rd 101 Crawfords Corner Rd
Holmdel, NJ 07733-3030 Holmdel, NJ 07733-3030
Phone: +1 732 949 5141 Phone: +1 732 949 5141
Email: zwlin@lucent.com Email: zwlin@lucent.com
Ben Mack-Crane Ben Mack-Crane
Tellabs Tellabs
Email: Ben.Mack-Crane@tellabs.com Email: Ben.Mack-Crane@tellabs.com
E. Mannie Editor Internet-Draft November 2001 16
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001
Eric Mannie Eric Mannie
EBONE EBONE
Terhulpsesteenweg 6A Terhulpsesteenweg 6A
1560 Hoeilaart - Belgium 1560 Hoeilaart - Belgium
Phone: +32 2 658 56 52 Phone: +32 2 658 56 52
Mobile: +32 496 58 56 52 Mobile: +32 496 58 56 52
Fax: +32 2 658 51 18 Fax: +32 2 658 51 18
Email: eric.mannie@ebone.com Email: eric.mannie@ebone.com
Dimitri Papadimitriou Dimitri Papadimitriou
Senior R&D Engineer - Optical Networking Senior R&D Engineer - Optical Networking
Alcatel IPO-NSG Alcatel IPO-NSG
Francis Wellesplein 1, Francis Wellesplein 1,
B-2018 Antwerpen, Belgium B-2018 Antwerpen, Belgium
Phone: +32 3 240-8491 Phone: +32 3 240-8491
Email: Dimitri.Papadimitriou@alcatel.be Email: Dimitri.Papadimitriou@alcatel.be
E. Mannie Editor Internet-Draft December 2001 14
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
Mike Raftelis Mike Raftelis
White Rock Networks White Rock Networks
18111 Preston Road Suite 900 18111 Preston Road Suite 900
Dallas, TX 75252 Dallas, TX 75252
Phone: +1 (972)588-3728 Phone: +1 (972)588-3728
Fax: +1 (972)588-3701 Fax: +1 (972)588-3701
Email: Mraftelis@WhiteRockNetworks.com Email: Mraftelis@WhiteRockNetworks.com
Bala Rajagopalan Bala Rajagopalan
Tellium, Inc. Tellium, Inc.
skipping to change at line 911 skipping to change at line 784
Debanjan Saha Debanjan Saha
Tellium Optical Systems Tellium Optical Systems
2 Crescent Place 2 Crescent Place
Oceanport, NJ 07757-0901 Oceanport, NJ 07757-0901
Phone: +1 732 923 4264 Phone: +1 732 923 4264
Fax: +1 732 923 9804 Fax: +1 732 923 9804
Email: dsaha@tellium.com Email: dsaha@tellium.com
Vishal Sharma Vishal Sharma
Jasmine Networks, Inc. Metanoia, Inc.
3061 Zanker Road, Suite B 335 Elan Village Lane
San Jose, CA 95134 San Jose, CA 95134
Phone: +1 408 895 5030 Phone: +1 408 943 1794
Fax: +1 408 895 5050 Email: vsharma87@yahoo.com
Email: vsharma@jasminenetworks.com
E. Mannie Editor Internet-Draft November 2001 17
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt May, 2001
George Swallow George Swallow
Cisco Systems, Inc. Cisco Systems, Inc.
250 Apollo Drive 250 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Voice: +1 978 244 8143 Voice: +1 978 244 8143
Email: swallow@cisco.com Email: swallow@cisco.com
Z. Bo Tang Z. Bo Tang
Tellium, Inc. Tellium, Inc.
2 Crescent Place 2 Crescent Place
P.O. Box 901 P.O. Box 901
Oceanport, NJ 07757-0901 Oceanport, NJ 07757-0901
Phone: +1 732 923 4231 Phone: +1 732 923 4231
Fax: +1 732 923 9804 Fax: +1 732 923 9804
Email: btang@tellium.com Email: btang@tellium.com
E. Mannie Editor Internet-Draft December 2001 15
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
Eve Varma Eve Varma
101 Crawfords Corner Rd 101 Crawfords Corner Rd
Holmdel, NJ 07733-3030 Holmdel, NJ 07733-3030
Phone: +1 732 949 8559 Phone: +1 732 949 8559
Email: evarma@lucent.com Email: evarma@lucent.com
Maarten Vissers Maarten Vissers
Botterstraat 45 Botterstraat 45
Postbus 18 Postbus 18
1270 AA Huizen, Netherlands 1270 AA Huizen, Netherlands
Email: mvissers@lucent.com Email: mvissers@lucent.com
Yangguang Xu Yangguang Xu
21-2A41, 1600 Osgood Street 21-2A41, 1600 Osgood Street
North Andover, MA 01845 North Andover, MA 01845
Email: xuyg@lucent.com Email: xuyg@lucent.com
E. Mannie Editor Internet-Draft November 2001 18 E. Mannie Editor Internet-Draft December 2001 16
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
Appendix 1 - Signal Type Values Extension For Group Signals
This appendix defines the following optional additional Signal
Type values for the Signal Type field of section 2.1:
Value Type
----- ---------------------
13 VTG / TUG-2
14 TUG-3
15 STSG-3 / AUG-1
16 STSG-12 / AUG-4
17 STSG-48 / AUG-16
18 STSG-192 / AUG-64
19 STSG-768 / AUG-256
Administrative Unit Group-Ns (AUG-Ns) and STS Groups-3*Ns (STSG-Ms),
are logical objects that are a collection of AU-3s/STS-1 SPEs, AU-
4s/STS-3c SPEs and/or AU-4-Xcs/STS-3*Xc SPEs (X = 4,16,64,256).
When used as a signal type this means that all the VC-3s/STS-1_SPEs,
VC-4s/STS-3c_SPEs or VC-4-Xcs/STS-3*Xc SPEs in the AU-3s/STS-1 SPEs,
AU-4s/STS-3c SPEs or AU-4-Xcs/STS-3*Xc SPEs that comprise the AUG-
N/STSG-3*N are switched together as one unique signal.
In addition the structure of the VC-3s/STS-1_SPEs, VC-4s/STS-3c_SPEs
or VC-4-Xcs/STS-3*Xc_SPEs in the AUG-N/STSG-3*N are preserved and are
allowed to change over the life of an AUG-N/STSG-3*N.
It is this flexibility in the relationships between the component VCs
or SPEs that differentiates this signal from a set of VC-3s/STS-
1_SPEs, VC-4s/STS-3c_SPEs or VC-4-Xcs/STS-3*Xc_SPEs. Whether the AUG-
N/STSG-3*N is structured with AU-3s/STS-1 SPEs, AU-4s/STS-3c SPEs
and/or AU-4-Xcs/STS-3*Xc SPEs does not need to be specified and is
allowed to change over time. The same reasoning applies to TUG-2/VTG
and TUG-3 signal types.
For example an STSG-48 could at one time consist of four STS-12c
signals and at another point in time of three STS-12c signals and
four STS-3c signals.
Note that the use of TUG-X, AUG-N and STSG-M as circuit types is not
described in ANSI and ITU-T standards. The use of these signal types
in the signaling plane is conceptual.
These signal types are conceptual objects that intend to designate
a group of physical objects in the standardized data plane.
E. Mannie Editor Internet-Draft December 2001 17
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
Appendix 2 - 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 G.707 standard 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 path instead of the TU-3 path.
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 TU-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.
The VC-3 signal type indicates that a VC-3 in any branch is
suitable.
E. Mannie Editor Internet-Draft December 2001 18
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
Appendix 3 - Contiguous Concatenation Extension
This appendix defines the following optional extension flag for
the Requested Contiguous Concatenation (RCC) field of section 2.1:
Flag 2 (bit 2): Arbitrary contiguous concatenation.
This flag allows an upstream node to signal to a downstream node
that it supports arbitrary contiguous concatenation. This type of
concatenation is not defined by ANSI or ITU-T.
Arbitrary contiguous concatenation allows for any value of X (X
less or equal N) in VC-4-Xc/STS-Xc. In addition, it allows the
arbitrary contiguous concatenated signal to start at any location
(AU-4/STS-1 timeslot) in the STM-N/STS-N signal.
This flag can be setup together with Flag 1 (Standard Contiguous
Concatenation) to give a choice to the downstream node. The
resulting type of contiguous concatenation can be different at
each hop according to the result of the negotiation.
E. Mannie Editor Internet-Draft December 2001 19
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
Appendix 4 - Virtual Concatenation Extension
This appendix defines the following optional extension for the
signals that can be virtually concatenated.
In addition to the elementary signal types, which can be virtual
concatenated as indicated in section 2.1, identical contiguously
concatenated signals may be virtual concatenated. In this last
case, it allows to request the virtual concatenation of, for
instance, several VC-4-4c/STS-12c SPEs, or any VC-4-Xc/STS-Xc SPEs
to obtain a VC-4-Xc-Yv/STS-Xc-Yv SPE.
Note that the standard definition for virtual concatenation allows
each virtual concatenation components to travel over diverse
paths. Within GMPLS, virtual concatenation components must travel
over the same (component) link if they are part of the same LSP.
This is due to the way that labels are bound to a (component)
link. Note however, that the routing of components on different
paths is indeed equivalent to establishing different LSPs, each
one having its own route. Several LSPs can be initiated and
terminated between the same nodes and their corresponding
components can then be associated together.
In case of virtual concatenation of a contiguously concatenated
signal, the same rule as described in section 3 for virtual
concatenation applies, except that a component of the virtually
concatenated signal is now itself represented by a list of labels
because it is concatenated. The first set of labels indicates the
first contiguously concatenated signal; the second set of labels
indicates the second contiguously concatenated signal, and so on.
E. Mannie Editor Internet-Draft December 2001 20
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
Appendix 5 - Transparency Extension
This appendix defines the following optional extension for the
Transparency field of section 2.1.
Transparency can be requested for a particular SOH/RSOH or
MSOH/LOH field in the STM-N/STS-N signal.
Transparency is not applied at the interfaces of the initiating
and terminating LSRs, but is only applied between intermediate
LSRs. Moreover, the transparency extensions can be implemented
effectively in very different ways, e.g. by forwarding the
corresponding overhead bytes untouched, or by tunneling the bytes.
This specification specifies neither how transparency is achieved;
nor the behavior of the signal at the egress of the transparent
network during fault conditions at the ingress of the transparent
network or within the transparent network; nor network deployment
scenarios. The signaling is independent of these considerations.
When the signaling is used between intermediate nodes it is up to
a data plane profile or specification to indicate how transparency
is effectively achieved in the data plane. When the signaling is
used at the interfaces with the initiating and terminating LSRs it
is up to the data plane specification to guarantee compliant
behavior to G.707/T1.105 under fault free and fault conditions.
Note that B1 in the SOH/RSOH is computed over the complete
previous frame, if one bit changes, B1 must be re-computed. Note
that B2 in the LOH/MSOH is also computed over the complete
previous frame, except the SOH/RSOH.
The different transparency extension flags are the following:
Flag 3 (bit 3) : J0.
Flag 4 (bit 4) : SOH/RSOH DCC (D1-D3).
Flag 5 (bit 5) : LOH/MSOH DCC (D4-D12).
Flag 6 (bit 6) : LOH/MSOH Extended DCC (D13-D156).
Flag 7 (bit 7) : K1/K2.
Flag 8 (bit 8) : E1.
Flag 9 (bit 9) : F1.
Flag 10 (bit 10): E2.
Flag 11 (bit 11): B1.
Flag 12 (bit 12): B2.
Line/Multiplex Section layer transparency (refer to section 2.1)
can be combined only with any of the following transparency types:
J0, SOH/RSOH DCC (D1-D3), E1, F1; and all other transparency flags
must be ignored.
Note that the extended LOH/MSOH DCC (D13-D156) is only applicable
to (defined for) STS-768/STM-256.
E. Mannie Editor Internet-Draft December 2001 21
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
If B1 transparency is requested, this means transparency for the bit
error supervision functionality provided by the B1. The B1 contains
the BIP8 calculated over the previous RS/Section frame of the STM-
N/STS-N signal at the RS/Section termination source. At the
RS/Section termination sink the B1 BIP is compared with the local
BIP also calculated over the previous RS/Section frame of the STM-
N/STS-N. Any difference between the two BIP values is an indication
for a bit error that occurred between the termination source and
sink. In case of B1 transparency this functionality shall be
preserved. This means that a B1 bit error detection as described
above performed after the transparent transport (at a RS/Section
termination sink) indicates exactly the bit errors that occur
between the B1 insertion point (RS/Section termination source) and
this point. Any intended changes to the previous RS/Section frame
content due to the implementation of the transparency feature (e.g.
modifications of the RS/Section overhead, modifications of the
payload due to pointer justifications) have to be reflected in the
B1 BIP value, it has to be adjusted accordingly.
If B2 transparency is requested, this means transparency for the bit
error supervision functionality provided by the B2. The B2 contains
the BIP24*N/BIP8*N calculated over the previous MS/Line frame of the
STM-N/STS-N signal at the MS/Line termination source. At the MS/Line
termination sink the B2 BIP is compared with the local BIP also
calculated over the previous MS/Line frame of the STM-N/STS-N. Any
difference between the two BIP values is an indication for a bit
error that occurred between the termination source and sink. In case
of B2 transparency this functionality shall be preserved. This means
that a B2 bit error detection as described above performed after the
transparent transport (at a MS/Line termination sink) indicates
exactly the bit errors that occur between the B2 insertion point
(MS/Line termination source) and this point. Any intended changes to
the previous MS/Line frame content due to the implementation of the
transparency feature (e.g. modifications of the MS/Line overhead,
modifications of the payload due to pointer justifications) have to
be reflected in the B2 BIP value, it has to be adjusted accordingly.
E. Mannie Editor Internet-Draft December 2001 22
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
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.
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 flag
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.
5. 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.
6. An STM-64 signal with RSOH and MSOH DCCs 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 4 and 5 to an STM-64
Elementary Signal.
7. An STM-4c signal (i.e. VC-4-4C with the transport overhead)
with Multiplex Section layer transparency is formed by the
application of RCC with flag 1, NCC with value 1, NVC with value
0, MT with value 1 and T with flag 2 applied to an STM-4
Elementary Signal.
8. An STM-256c signal with Multiplex Section layer transparency is
formed by the application of RCC with flag 1, NCC with value 1,
NVC with value 0, MT with value 1 and T with flag 2 applied to an
STM-256 Elementary Signal.
9. 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.
10. An STS-3c SPE signal is formed by the application of RCC with
value 0 (no contiguous concatenation), NCC with value 0, NVC with
value 0, MT with value 1 and T with value 0 to an STS-3c SPE
Elementary Signal.
E. Mannie Editor Internet-Draft December 2001 23
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
11. An STS-48c SPE signal is formed by the application of RCC with
flag 1 (standard contiguous concatenation), NCC with value 16, NVC
with value 0, MT with value 1 and T with value 0 to an STS-3c SPE
Elementary Signal.
12. 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.
13. An STS-3c-9v SPE signal is formed by the application of RCC
with value 0, NCC with value 0, NVC with value 9 (virtual
concatenation of 9 STS-3c), MT with value 1 and T with value 0 to
an STS-3c SPE Elementary Signal.
14. An STS-12 signal with Section layer (full) transparency is
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.
15. An STS-192 signal with K1/K2 and LOH DCC transparency is
formed by the application of RCC with value 0, NVC with value 0,
MT with value 1 and T with flags 5 and 7 to an STS-192 Elementary
Signal.
16. An STS-48c signal with LOH DCC and E2 transparency is formed
by the application of RCC with flag 1, NCC with value 1, NVC with
value 0, MT with value 1 and T with flag 5 and 10 to an STS-48
Elementary Signal.
17. An STS-768c signal with K1/K2 and LOH DCC transparency is
formed by the application of RCC with flag 1, NCC with value 1,
NVC with value 0, MT with value 1 and T with flag 5 and 7 to an
STS-768 Elementary Signal.
18. 4 x STS-12 signals with K1/K2 and LOH DCC transparency is
formed by the application of RCC with value 0, NVC with value 0,
MT with value 4 and T with flags 5 and 7 to an STS-12 Elementary
Signal.
19. 3 x STS-768c SPE signal is formed by the application of RCC
with flag 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.
20. 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.
21. 2 x STS-4a-5v SPE signal is formed by the application of RCC
with flag 2 (for arbitrary contiguous concatenation), NCC with
value 4, NVC with value 5, MT with value 2 and T with value 0 to
an STS-1 SPE Elementary Signal.
E. Mannie Editor Internet-Draft December 2001 24
draft-ietf-ccamp-gmpls-sonet-sdh-01.txt June, 2001
22. A VC-4-3a signal is formed by the application of RCC with flag
2 (arbitrary contiguous concatenation), NCC with value 3, NVC with
value 0, MT with value 1 and T with value 0 to a VC-4 Elementary
Signal.
23. An STS-34a SPE signal is formed by the application of RCC with
flag 2 (arbitrary contiguous concatenation), NCC with value 34,
NVC with value 0, MT with value 1 and T with value 0 to an STS-1
SPE Elementary Signal.
E. Mannie Editor Internet-Draft December 2001 25
 End of changes. 

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