draft-ietf-ccamp-gmpls-routing-02.txt   draft-ietf-ccamp-gmpls-routing-03.txt 
Network Working Group K. Kompella (Juniper Networks) Network Working Group K. Kompella (Juniper Networks)
Internet Draft Y. Rekhter (Juniper Networks) Internet Draft Y. Rekhter (Juniper Networks)
Expiration Date: August 2002 A. Banerjee (Calient Networks) Expiration Date: October 2002 A. Banerjee (Calient Networks)
J. Drake (Calient Networks) J. Drake (Calient Networks)
G. Bernstein (Ciena) G. Bernstein (Ciena)
D. Fedyk (Nortel Networks) D. Fedyk (Nortel Networks)
E. Mannie (GTS Network) E. Mannie (GTS Network)
D. Saha (Tellium) D. Saha (Tellium)
V. Sharma (Metanoia, Inc.) V. Sharma (Metanoia, Inc.)
D. Basak (AcceLight Networks) D. Basak (AcceLight Networks)
L. Berger (Movaz Networks)
Routing Extensions in Support of Generalized MPLS Routing Extensions in Support of Generalized MPLS
draft-ietf-ccamp-gmpls-routing-02.txt draft-ietf-ccamp-gmpls-routing-03.txt
1. Status of this Memo 1. 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. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 4, line 24 skipping to change at page 4, line 24
[ISIS-TE] and [OSFP-TE] define the canonical TE properties, and say [ISIS-TE] and [OSFP-TE] define the canonical TE properties, and say
how to associate TE properties to regular (packet-switched) links. how to associate TE properties to regular (packet-switched) links.
This document extends the set of TE properties, and also says how to This document extends the set of TE properties, and also says how to
associate TE properties with non-packet-switched links such as links associate TE properties with non-packet-switched links such as links
between Optical Cross-Connects (OXCs). [LSP-HIER] says how to between Optical Cross-Connects (OXCs). [LSP-HIER] says how to
associate TE properties with links formed by Label Switched Paths. associate TE properties with links formed by Label Switched Paths.
5.1. Excluding data traffic from control channels 5.1. Excluding data traffic from control channels
The control channels between nodes in a GMPLS network, such as OXCs, The control channels between nodes in a GMPLS network, such as OXCs,
SONET cross-connects and/or routers, are generally meant for control SDH cross-connects and/or routers, are generally meant for control
and administrative traffic. These control channels are advertised and administrative traffic. These control channels are advertised
into routing as normal links as mentioned in the previous section; into routing as normal links as mentioned in the previous section;
this allows the routing of (for example) RSVP messages and telnet this allows the routing of (for example) RSVP messages and telnet
sessions. However, if routers on the edge of the optical domain sessions. However, if routers on the edge of the optical domain
attempt to forward data traffic over these channels, the channel attempt to forward data traffic over these channels, the channel
capacity will quickly be exhausted. capacity will quickly be exhausted.
In order to keep these control channels from being advertised into In order to keep these control channels from being advertised into
the user data plane a variety of techniques can be used. the user data plane a variety of techniques can be used.
skipping to change at page 5, line 9 skipping to change at page 5, line 9
switch incapable links; if all of its links are packet-switch switch incapable links; if all of its links are packet-switch
capable, then clearly this check is redundant. capable, then clearly this check is redundant.
In other instances it may be desirable to keep the whole address In other instances it may be desirable to keep the whole address
space of a GMPLS routing plane disjoint from the endpoint addresses space of a GMPLS routing plane disjoint from the endpoint addresses
in another portion of the GMPLS network. For example, the addresses in another portion of the GMPLS network. For example, the addresses
of a carrier network where the carrier uses GMPLS but does not wish of a carrier network where the carrier uses GMPLS but does not wish
to expose the internals of the addressing or topology. In such a to expose the internals of the addressing or topology. In such a
network the control channels are never advertised into the end data network the control channels are never advertised into the end data
network. In this instance, independent mechanisms are used to network. In this instance, independent mechanisms are used to
advertise the data addresses over the carrier network. The Optical advertise the data addresses over the carrier network.
VPNs architecture [OVPN] discusses a mechanism for automating the
distribution of independent addresses.
Other techniques for excluding data traffic from control channels may Other techniques for excluding data traffic from control channels may
also be needed. also be needed.
6. GMPLS Routing Enhancements 6. GMPLS Routing Enhancements
In this section we define the enhancements to the TE properties of In this section we define the enhancements to the TE properties of
GMPLS TE links. Encoding of this information in IS-IS is specified in GMPLS TE links. Encoding of this information in IS-IS is specified in
[GMPLS-ISIS]. Encoding of this information in OSPF is specified in [GMPLS-ISIS]. Encoding of this information in OSPF is specified in
[GMPLS-OSPF]. [GMPLS-OSPF].
skipping to change at page 7, line 39 skipping to change at page 7, line 39
The SRLG Information is optional and if a Link State Advertisement The SRLG Information is optional and if a Link State Advertisement
doesn't carry the SRLG Information, then it means that SRLG of that doesn't carry the SRLG Information, then it means that SRLG of that
link is unknown. link is unknown.
6.4. Interface Switching Capability Descriptor 6.4. Interface Switching Capability Descriptor
In the context of this document we say that a link is connected to a In the context of this document we say that a link is connected to a
node by an interface. In the context of GMPLS interfaces may have node by an interface. In the context of GMPLS interfaces may have
different switching capabilities. For example an interface that different switching capabilities. For example an interface that
connects a given link to a node may not be able to switch individual connects a given link to a node may not be able to switch individual
packets, but it may be able to switch channels within a SONET packets, but it may be able to switch channels within an SDH payload.
payload. Interfaces at each end of a link need not have the same Interfaces at each end of a link need not have the same switching
switching capabilities. Interfaces on the same node need not have capabilities. Interfaces on the same node need not have the same
the same switching capabilities. switching capabilities.
The Interface Switching Capability Descriptor describes switching The Interface Switching Capability Descriptor describes switching
capability of an interface. For bi-directional links, the switching capability of an interface. For bi-directional links, the switching
capabilities of an interface are defined to be the same in either capabilities of an interface are defined to be the same in either
direction. I.e., for data entering the node through that interface direction. I.e., for data entering the node through that interface
and for data leaving the node through that interface. and for data leaving the node through that interface.
A Link State Advertisement of a link carries the Interface Switching A Link State Advertisement of a link carries the Interface Switching
Capability Descriptor(s) only of the near end (the end incumbent on Capability Descriptor(s) only of the near end (the end incumbent on
the LSR originating the advertisement). the LSR originating the advertisement).
skipping to change at page 8, line 48 skipping to change at page 8, line 48
(PSC-1). (PSC-1).
Interface Switching Capability Descriptors present a new constraint Interface Switching Capability Descriptors present a new constraint
for LSP path computation. for LSP path computation.
Irrespective of a particular Interface Switching Capability, the Irrespective of a particular Interface Switching Capability, the
Interface Switching Capability Descriptor always includes information Interface Switching Capability Descriptor always includes information
about the encoding supported by an interface. The defined encodings about the encoding supported by an interface. The defined encodings
are the same as LSP Encoding as defined in [GMPLS-SIG]. are the same as LSP Encoding as defined in [GMPLS-SIG].
An interface may have more than one Interface Switching Capability
Descriptor. This is used to handle interfaces that support multiple
switching capabilities, for interfaces that have Max LSP Bandwidth
values that differ by priority level, and for interfaces that support
discrete bandwidths.
Depending on a particular Interface Switching Capability, the Depending on a particular Interface Switching Capability, the
Interface Switching Capability Descriptor may include additional Interface Switching Capability Descriptor may include additional
information, as specified below. information, as specified below.
6.4.1. Layer-2 Switch Capable 6.4.1. Layer-2 Switch Capable
If an interface is of type L2SC, it means that the node receiving If an interface is of type L2SC, it means that the node receiving
data over this interface can switch the received frames based on the data over this interface can switch the received frames based on the
layer 2 address. For example, an interface associated with a link layer 2 address. For example, an interface associated with a link
terminating on an ATM switch would be considered L2SC. terminating on an ATM switch would be considered L2SC.
skipping to change at page 9, line 45 skipping to change at page 10, line 5
Although Maximum Bandwidth is to be deprecated, for backward Although Maximum Bandwidth is to be deprecated, for backward
compatibility, one MAY set the Maximum Bandwidth to the Maximum LSP compatibility, one MAY set the Maximum Bandwidth to the Maximum LSP
Bandwidth at priority 7. Bandwidth at priority 7.
The Minimum LSP Bandwidth specifies the minimum bandwidth an LSP The Minimum LSP Bandwidth specifies the minimum bandwidth an LSP
could reserve. could reserve.
Typical values for the Minimum LSP Bandwidth and for the Maximum LSP Typical values for the Minimum LSP Bandwidth and for the Maximum LSP
Bandwidth are enumerated in [GMPLS-SIG]. Bandwidth are enumerated in [GMPLS-SIG].
On a PSC interface that supports Standard SONET (or Standard SDH) On a PSC interface that supports Standard SDH encoding, an LSP at
encoding, an LSP at priority p could reserve any bandwidth allowed by priority p could reserve any bandwidth allowed by the branch of the
the branch of the SONET/SDH hierarchy, with the leaf and the root of SDH hierarchy, with the leaf and the root of the branch being defined
the branch being defined by the Minimum LSP Bandwidth and the Maximum by the Minimum LSP Bandwidth and the Maximum LSP Bandwidth at
LSP Bandwidth at priority p. priority p.
On a PSC interface that supports Arbitrary SONET (or Arbitrary SDH) On a PSC interface that supports Arbitrary SDH encoding, an LSP at
encoding, an LSP at priority p could reserve any bandwidth between priority p could reserve any bandwidth between the Minimum LSP
the Minimum LSP Bandwidth and the Maximum LSP Bandwidth at priority Bandwidth and the Maximum LSP Bandwidth at priority p, provided that
p, provided that the bandwidth reserved by the LSP is a multiple of the bandwidth reserved by the LSP is a multiple of the Minimum LSP
the Minimum LSP Bandwidth. Bandwidth.
The Interface MTU is the maximum size of a packet that can be The Interface MTU is the maximum size of a packet that can be
transmitted on this interface without being fragmented. transmitted on this interface without being fragmented.
6.4.3. Time-Division Multiplex Capable 6.4.3. Time-Division Multiplex Capable
If an interface is of type TDM, it means that the node receiving data If an interface is of type TDM, it means that the node receiving data
over this interface can multiplex or demultiplex channels within a over this interface can multiplex or demultiplex channels within an
SONET/SDH payload. SDH payload.
For Time-Division Multiplex Capable interfaces the additional For Time-Division Multiplex Capable interfaces the additional
information includes Maximum LSP Bandwidth, the information on information includes Maximum LSP Bandwidth, the information on
whether the interface supports Standard or Arbitrary SONET/SDH, and whether the interface supports Standard or Arbitrary SDH, and Minimum
Minimum LSP Bandwidth. LSP Bandwidth.
For a simple (unbundled) link the Maximum LSP Bandwidth at priority p For a simple (unbundled) link the Maximum LSP Bandwidth at priority p
is defined as the maximum bandwidth an LSP at priority p could is defined as the maximum bandwidth an LSP at priority p could
reserve. Maximum LSP Bandwidth for a bundled link is defined in reserve. Maximum LSP Bandwidth for a bundled link is defined in
[LINK-BUNDLE]. [LINK-BUNDLE].
The Minimum LSP Bandwidth specifies the minimum bandwidth an LSP The Minimum LSP Bandwidth specifies the minimum bandwidth an LSP
could reserve. could reserve.
Typical values for the Minimum LSP Bandwidth and for the Maximum LSP Typical values for the Minimum LSP Bandwidth and for the Maximum LSP
Bandwidth are enumerated in [GMPLS-SIG]. Bandwidth are enumerated in [GMPLS-SIG].
On an interface having Standard SONET (or Standard SDH) multiplexing, On an interface having Standard SDH multiplexing, an LSP at priority
an LSP at priority p could reserve any bandwidth allowed by the p could reserve any bandwidth allowed by the branch of the SDH
branch of the SONET/SDH hierarchy, with the leaf and the root of the hierarchy, with the leaf and the root of the branch being defined by
branch being defined by the Minimum LSP Bandwidth and the Maximum LSP the Minimum LSP Bandwidth and the Maximum LSP Bandwidth at priority
Bandwidth at priority p. p.
On an interface having Arbitrary SONET (or Arbitrary SDH) On an interface having Arbitrary SDH multiplexing, an LSP at priority
multiplexing, an LSP at priority p could reserve any bandwidth p could reserve any bandwidth between the Minimum LSP Bandwidth and
between the Minimum LSP Bandwidth and the Maximum LSP Bandwidth at the Maximum LSP Bandwidth at priority p, provided that the bandwidth
priority p, provided that the bandwidth reserved by the LSP is a reserved by the LSP is a multiple of the Minimum LSP Bandwidth.
multiple of the Minimum LSP Bandwidth.
Interface Switching Capability Descriptor for the interfaces that
support sub-STS1 may include additional information. The nature and
the encoding of such information is outside the scope of this
document.
A way to handle the case where an interface supports multiple A way to handle the case where an interface supports multiple
branches of the SONET (or SDH) multiplexing hierarchy, multiple branches of the SDH multiplexing hierarchy, multiple Interface
Interface Switching Capability Descriptors would be advertised, one Switching Capability Descriptors would be advertised, one per branch.
per branch. For example, if an interface supports VT-1.5 and VT-2 For example, if an interface supports VT-1.5 and VT-2 (which are not
(which are not part of same branch of SONET multiplexing tree), Then part of same branch of SDH multiplexing tree), Then it could
it could advertise two descriptors, one for each one. advertise two descriptors, one for each one.
6.4.4. Lambda-Switch Capable 6.4.4. Lambda-Switch Capable
If an interface is of type LSC, it means that the node receiving data If an interface is of type LSC, it means that the node receiving data
over this interface can recognize and switch individual lambdas over this interface can recognize and switch individual lambdas
within the interface. An interface that allows only one lambda per within the interface. An interface that allows only one lambda per
interface, and switches just that lambda is of type LSC. interface, and switches just that lambda is of type LSC.
The additional information includes Reservable Bandwidth per The additional information includes Reservable Bandwidth per
priority, which specifies the bandwidth of an LSP that could be priority, which specifies the bandwidth of an LSP that could be
skipping to change at page 12, line 24 skipping to change at page 12, line 29
[PSC, LSC] - a link between a packet LSR and an OXC [PSC, LSC] - a link between a packet LSR and an OXC
[TDM, LSC] - a link between a Digital Cross Connect and an OXC [TDM, LSC] - a link between a Digital Cross Connect and an OXC
Both ends of a given TE link has to use the same way of carrying Both ends of a given TE link has to use the same way of carrying
label information over that link. Carrying label information on a label information over that link. Carrying label information on a
given TE link depends on the Interface Switching Capability at both given TE link depends on the Interface Switching Capability at both
ends of the link, and is determined as follows: ends of the link, and is determined as follows:
[PSC, PSC] - label is carried in the "shim" header [RFC3032] [PSC, PSC] - label is carried in the "shim" header [RFC3032]
[TDM, TDM] - label represents a TDM time slot [GMPLS-SONET-SDH] [TDM, TDM] - label represents a TDM time slot [GMPLS-SONET-SDH]
[LSC, LSC] - label represents a port on an OXC [LSC, LSC] - label represents a lambda
[FSC, FSC] - label represents a port on an OXC
[PSC, TDM] - label represents a TDM time slot [GMPLS-SONET-SDH] [PSC, TDM] - label represents a TDM time slot [GMPLS-SONET-SDH]
[PSC, LSC] - label represents a port [PSC, LSC] - label represents a lambda
[TDM, LSC] - label represents a port [PSC, FSC] - label represents a port
[TDM, LSC] - label represents a lambda
[TDM, FSC] - label represents a port
[LSC, FSC] - label represents a port
6.4.8. Other issues 6.4.8. Other issues
It is possible that Interface Switching Capability Descriptor will It is possible that Interface Switching Capability Descriptor will
change over time, reflecting the allocation/deallocation of LSPs. change over time, reflecting the allocation/deallocation of LSPs.
For example, assume that STS-1, STS-3c, STS-12c, STS-48c and STS-192c For example, assume that STS-1, STS-3c, STS-12c, STS-48c and STS-192c
LSPs can be established on a OC-192 interface whose Encoding Type is LSPs can be established on a OC-192 interface whose Encoding Type is
SONET (or to be more precise, SONET ANSI T1.105). Thus, initially in SDH. Thus, initially in the Interface Switching Capability Descriptor
the Interface Switching Capability Descriptor the Minimum LSP the Minimum LSP Bandwidth is set to STS-1, and Maximum LSP Bandwidth
Bandwidth is set to STS-1, and Maximum LSP Bandwidth is set to is set to STS-192 for all priorities. As soon as an LSP of STS-1
STS-192 for all priorities. As soon as an LSP of STS-1 size at size at priority 1 is established on the interface, it is no longer
priority 1 is established on the interface, it is no longer capable capable of STS-192c for all but LSPs at priority 0. Therefore, the
of STS-192c for all but LSPs at priority 0. Therefore, the node node advertises a modified Interface Switching Capability Descriptor
advertises a modified Interface Switching Capability Descriptor
indicating that the Maximum LSP Bandwidth is no longer STS-192, but indicating that the Maximum LSP Bandwidth is no longer STS-192, but
STS-48 for all but priority 0 (at priority 0 the Maximum LSP STS-48 for all but priority 0 (at priority 0 the Maximum LSP
Bandwidth is still STS-192). If subsequently there is another STS-1 Bandwidth is still STS-192). If subsequently there is another STS-1
LSP, there is no change in the Interface Switching Capability LSP, there is no change in the Interface Switching Capability
Descriptor. The Descriptor remains the same until the node can no Descriptor. The Descriptor remains the same until the node can no
longer establish a STS-48c LSP over the interface (which means that longer establish a STS-48c LSP over the interface (which means that
at this point more than 144 time slots are taken by LSPs on the at this point more than 144 time slots are taken by LSPs on the
interface). Once this happened, the Descriptor is modified again, interface). Once this happened, the Descriptor is modified again,
and the modified Descriptor is advertised to other nodes. and the modified Descriptor is advertised to other nodes.
6.4.9. Examples of Interface Switching Capability Descriptor 7. Examples of Interface Switching Capability Descriptor
6.4.9.1. STS-48 POS Interface on a LSR 7.1. STS-48 POS Interface on a LSR
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = PSC-1 Interface Switching Capability = PSC-1
Encoding = SONET ANSI T1.105 Encoding = SDH
Max LSP Bandwidth[p] = 2.5 Gbps, for all p Max LSP Bandwidth[p] = 2.5 Gbps, for all p
If multiple links with such interfaces at both ends were to be If multiple links with such interfaces at both ends were to be
advertised as one TE link, link bundling techniques should be used. advertised as one TE link, link bundling techniques should be used.
6.4.9.2. GigE Packet Interface on a LSR 7.2. GigE Packet Interface on a LSR
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = PSC-1 Interface Switching Capability = PSC-1
Encoding = Ethernet 802.3 Encoding = Ethernet 802.3
Max LSP Bandwidth[p] = 1.0 Gbps, for all p Max LSP Bandwidth[p] = 1.0 Gbps, for all p
If multiple links with such interfaces at both ends were to be If multiple links with such interfaces at both ends were to be
advertised as one TE link, link bundling techniques should be used. advertised as one TE link, link bundling techniques should be used.
6.4.9.3. OC-192 SONET Interface on a Digital Cross Connect with Standard 7.3. OC-192 SDH Interface on a Digital Cross Connect with Standard SDH
SONET
Consider a branch of SONET multiplexing tree : VT-1.5, STS-1, STS-3c, Consider a branch of SDH multiplexing tree : VT-1.5, STS-1, STS-3c,
STS-12c, STS-48c, STS-192c. If it is possible to establish all these STS-12c, STS-48c, STS-192c. If it is possible to establish all these
connections on a OC-192 interface, the Interface Switching Capability connections on a OC-192 interface, the Interface Switching Capability
Descriptor of that interface can be advertised as follows: Descriptor of that interface can be advertised as follows:
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = TDM [Standard SONET] Interface Switching Capability = TDM [Standard SDH]
Encoding = SONET ANSI T1.105 Encoding = SDH
Min LSP Bandwidth = VT1.5 Min LSP Bandwidth = VT1.5
Max LSP Bandwidth[p] = STS192, for all p Max LSP Bandwidth[p] = STS192, for all p
If multiple links with such interfaces at both ends were to be If multiple links with such interfaces at both ends were to be
advertised as one TE link, link bundling techniques should be used. advertised as one TE link, link bundling techniques should be used.
6.4.9.4. OC-192 SONET Interface on a Digital Cross Connect with two 7.4. OC-192 SDH Interface on a Digital Cross Connect with two types of
types of SONET multiplexing hierarchy supported SDH multiplexing hierarchy supported
Interface Switching Capability Descriptor 1: Interface Switching Capability Descriptor 1:
Interface Switching Capability = TDM [Standard SONET] Interface Switching Capability = TDM [Standard SDH]
Encoding = SONET ANSI T1.105 Encoding = SDH
Min LSP Bandwidth = VT1.5 Min LSP Bandwidth = VT1.5
Max LSP Bandwidth[p] = STS192, for all p Max LSP Bandwidth[p] = STS192, for all p
Interface Switching Capability Descriptor 2: Interface Switching Capability Descriptor 2:
Interface Switching Capability = TDM [Arbitrary SONET] Interface Switching Capability = TDM [Arbitrary SDH]
Encoding = SONET ANSI T1.105 Encoding = SDH
Min LSP Bandwidth = VT2 Min LSP Bandwidth = VT2
Max LSP Bandwidth[p] = STS192, for all p Max LSP Bandwidth[p] = STS192, for all p
If multiple links with such interfaces at both ends were to be If multiple links with such interfaces at both ends were to be
advertised as one TE link, link bundling techniques should be used. advertised as one TE link, link bundling techniques should be used.
6.4.9.5. Interface on an opaque OXC (SONET framed) 7.5. Interface on an opaque OXC (SDH framed) with support for one lambda
per port/interface
An "opaque OXC" is considered operationally an OXC, as the whole An "opaque OXC" is considered operationally an OXC, as the whole
lambda (carrying the SONET line) is switched transparently without lambda (carrying the SDH line) is switched transparently without
further multiplexing/demultiplexing, and either none of the SONET further multiplexing/demultiplexing, and either none of the SDH
overhead bytes, or at least the important ones are not changed. overhead bytes, or at least the important ones are not changed.
An interface on an opaque OXC handles a single wavelength, and An interface on an opaque OXC handles a single wavelength, and
cannot switch multiple wavelengths as a whole. Thus, an interface on cannot switch multiple wavelengths as a whole. Thus, an interface on
an opaque OXC is always LSC, and not FSC, irrespective of whether an opaque OXC is always LSC, and not FSC, irrespective of whether
there is DWDM external to it. there is DWDM external to it.
Note that if there is external DWDM, then the framing understood by Note that if there is external DWDM, then the framing understood by
the DWDM must be same as that understood by the OXC. the DWDM must be same as that understood by the OXC.
A TE link is a group of interfaces on an OXC. All interfaces on a A TE link is a group of one or more interfaces on an OXC. All
given OXC are required to have identifiers unique to that OXC, and interfaces on a given OXC are required to have identifiers unique to
these identifiers are used as port labels (see 3.2.1.1 of [GMPLS- that OXC, and these identifiers are used as labels (see 3.2.1.1 of
SIG]). [GMPLS-SIG]).
The following is an example of an interface switching capability The following is an example of an interface switching capability
descriptor on a SONET framed opaque OXC: descriptor on an SDH framed opaque OXC:
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = LSC Interface Switching Capability = LSC
Encoding = SONET ANSI T1.105 Encoding = SDH
Reservable Bandwidth = Determined by SONET Framer (say OC192) Reservable Bandwidth = Determined by SDH Framer (say OC192)
6.4.9.6. Interface on a transparent OXC (PXC) with external DWDM that 7.6. Interface on a transparent OXC (PXC) with external DWDM that
understands SONET framing understands SDH framing
This example assumes that DWDM and PXC are connected in such a way This example assumes that DWDM and PXC are connected in such a way
that each interface (port) on the PXC handles just a single that each interface (port) on the PXC handles just a single
wavelength. Thus, even if in principle an interface on the PXC could wavelength. Thus, even if in principle an interface on the PXC could
switch multiple wavelengths as a whole, in this particular case an switch multiple wavelengths as a whole, in this particular case an
interface on the PXC is considered LSC, and not FSC. interface on the PXC is considered LSC, and not FSC.
_______ _______
| | | |
/|___| | /|___| |
| |___| PXC | | |___| PXC |
========| |___| | ========| |___| |
| |___| | | |___| |
\| |_______| \| |_______|
DWDM DWDM
(SONET framed) (SDH framed)
A TE link is a group of interfaces on the PXC. All interfaces on a A TE link is a group of one or more interfaces on the PXC. All
given PXC are required to have identifiers unique to that PXC, and interfaces on a given PXC are required to have identifiers unique to
these identifiers are used as port labels (see 3.2.1.1 of [GMPLS- that PXC, and these identifiers are used as labels (see 3.2.1.1 of
SIG]). [GMPLS-SIG]).
The following is an example of an interface switching capability The following is an example of an interface switching capability
descriptor on a transparent OXC (PXC) with external DWDM that descriptor on a transparent OXC (PXC) with external DWDM that
understands SONET framing: understands SDH framing:
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = LSC Interface Switching Capability = LSC
Encoding = SONET ANSI T1.105 (comes from DWDM) Encoding = SDH (comes from DWDM)
Reservable Bandwidth = Determined by DWDM (say OC192) Reservable Bandwidth = Determined by DWDM (say OC192)
6.4.9.7. Interface on a transparent OXC (PXC) with external DWDM that is 7.7. Interface on a transparent OXC (PXC) with external DWDM that is
transparent to bit-rate and framing transparent to bit-rate and framing
This example assumes that DWDM and PXC are connected in such a way This example assumes that DWDM and PXC are connected in such a way
that each interface (port) on the PXC handles just a single that each interface (port) on the PXC handles just a single
wavelength. Thus, even if in principle an interface on the PXC could wavelength. Thus, even if in principle an interface on the PXC could
switch multiple wavelengths as a whole, in this particular case an switch multiple wavelengths as a whole, in this particular case an
interface on the PXC is considered LSC, and not FSC. interface on the PXC is considered LSC, and not FSC.
_______ _______
| | | |
/|___| | /|___| |
| |___| PXC | | |___| PXC |
========| |___| | ========| |___| |
| |___| | | |___| |
\| |_______| \| |_______|
DWDM DWDM
(transparent to bit-rate and framing) (transparent to bit-rate and framing)
A TE link is a group of interfaces on the PXC. All interfaces on a A TE link is a group of one or more interfaces on the PXC. All
given PXC are required to have identifiers unique to that PXC, and interfaces on a given PXC are required to have identifiers unique to
these identifiers are used as port labels (see 3.2.1.1 of [GMPLS- that PXC, and these identifiers are used as labels (see 3.2.1.1 of
SIG]). [GMPLS-SIG]).
The following is an example of an interface switching capability The following is an example of an interface switching capability
descriptor on a transparent OXC (PXC) with external DWDM that is descriptor on a transparent OXC (PXC) with external DWDM that is
transparent to bit-rate and framing: transparent to bit-rate and framing:
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = LSC Interface Switching Capability = LSC
Encoding = Lambda (photonic) Encoding = Lambda (photonic)
Reservable Bandwidth = Determined by optical technology limits Reservable Bandwidth = Determined by optical technology limits
6.4.9.8. Interface on a PXC with no external DWDM 7.8. Interface on a PXC with no external DWDM
The absence of DWDM in between two PXCs, implies that an interface is The absence of DWDM in between two PXCs, implies that an interface is
not limited to one wavelength. Thus, the interface is advertised as not limited to one wavelength. Thus, the interface is advertised as
FSC. FSC.
A TE link is a group of interfaces on the PXC. All interfaces on a A TE link is a group of one or more interfaces on the PXC. All
given PXC are required to have identifiers unique to that PXC, and interfaces on a given PXC are required to have identifiers unique to
these identifiers are used as port labels (see 3.2.1.1 of [GMPLS- that PXC, and these identifiers are used as port labels (see 3.2.1.1
SIG]). of [GMPLS-SIG]).
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = FSC Interface Switching Capability = FSC
Encoding = Lambda (photonic) Encoding = Lambda (photonic)
Reservable Bandwidth = Determined by optical technology limits Reservable Bandwidth = Determined by optical technology limits
Note that this example assumes that the PXC does not restrict each Note that this example assumes that the PXC does not restrict each
port to carry only one wavelength. port to carry only one wavelength.
6.4.10. Example of interfaces that support multiple switching 7.9. Interface on a OXC with internal DWDM that understands SDH framing
capabilities
This example assumes that DWDM and OXC are connected in such a way
that each interface on the OXC handles multiple wavelengths
individually. In this case an interface on the OXC is considered LSC,
and not FSC.
_______
| |
/|| ||\
| || OXC || |
========| || || |====
| || || |
\||_______||/
DWDM
(SDH framed)
A TE link is a group of one or more of the interfaces on the OXC.
All lambdas associated with a particular interface are required to
have identifiers unique to that interface, and these identifiers are
used as labels (see 3.2.1.1 of [GMPLS-SIG]).
The following is an example of an interface switching capability
descriptor on an OXC with internal DWDM that understands SDH framing
and supports discrete bandwidths:
Interface Switching Capability Descriptor:
Interface Switching Capability = LSC
Encoding = SDH (comes from DWDM)
Max LSP Bandwidth = Determined by DWDM (say OC192)
Interface Switching Capability = LSC
Encoding = SDH (comes from DWDM)
Max LSP Bandwidth = Determined by DWDM (say OC48)
7.10. Interface on a OXC with internal DWDM that is transparent to bit-
rate and framing
This example assumes that DWDM and OXC are connected in such a way
that each interface on the OXC handles multiple wavelengths
individually. In this case an interface on the OXC is considered LSC,
and not FSC.
_______
| |
/|| ||\
| || OXC || |
========| || || |====
| || || |
\||_______||/
DWDM
(transparent to bit-rate and framing)
A TE link is a group of one or more of the interfaces on the OXC.
All lambdas associated with a particular interface are required to
have identifiers unique to that interface, and these identifiers are
used as labels (see 3.2.1.1 of [GMPLS-SIG]).
The following is an example of an interface switching capability
descriptor on an OXC with internal DWDM that is transparent to bit-
rate and framing:
Interface Switching Capability Descriptor:
Interface Switching Capability = LSC
Encoding = Lambda (photonic)
Max LSP Bandwidth = Determined by optical technology limits
8. Example of interfaces that support multiple switching capabilities
There can be many combinations possible, some are described below. There can be many combinations possible, some are described below.
6.4.10.1. Interface on a PXC+TDM device with external DWDM 8.1. Interface on a PXC+TDM device with external DWDM
As discussed earlier, the presence of the external DWDM limits that As discussed earlier, the presence of the external DWDM limits that
only one wavelength be on a port of the PXC. On such a port, the only one wavelength be on a port of the PXC. On such a port, the
attached PXC+TDM device can do one of the following. The wavelength attached PXC+TDM device can do one of the following. The wavelength
may be cross-connected by the PXC element to other out-bound optical may be cross-connected by the PXC element to other out-bound optical
channel, or the wavelength may be terminated as a SONET interface and channel, or the wavelength may be terminated as an SDH interface and
SONET channels switched. SDH channels switched.
From a GMPLS perspective the PXC+TDM functionality is treated as a From a GMPLS perspective the PXC+TDM functionality is treated as a
single interface. The interface is described using two Interface single interface. The interface is described using two Interface
descriptors, one for the LSC and another for the TDM, with descriptors, one for the LSC and another for the TDM, with
appropriate parameters. For example, appropriate parameters. For example,
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = LSC Interface Switching Capability = LSC
Encoding = SONET ANSI T1.105 (comes from WDM) Encoding = SDH (comes from WDM)
Reservable Bandwidth = OC192 Reservable Bandwidth = OC192
and and
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = TDM [Standard SONET] Interface Switching Capability = TDM [Standard SDH]
Encoding = SONET ANSI T1.105 Encoding = SDH
Min LSP Bandwidth = VT1.5 Min LSP Bandwidth = VT1.5
Max LSP Bandwidth[p] = STS192, for all p Max LSP Bandwidth[p] = STS192, for all p
6.4.10.2. Interface on an opaque OXC+TDM device with external DWDM 8.2. Interface on an opaque OXC+TDM device with external DWDM
An interface on an "opaque OXC+TDM" device would also be advertised An interface on an "opaque OXC+TDM" device would also be advertised
as LSC+TDM much the same way as the previous case. as LSC+TDM much the same way as the previous case.
6.4.10.3. Interface on a PXC+LSR device with external DWDM 8.3. Interface on a PXC+LSR device with external DWDM
As discussed earlier, the presence of the external DWDM limits that As discussed earlier, the presence of the external DWDM limits that
only one wavelength be on a port of the PXC. On such a port, the only one wavelength be on a port of the PXC. On such a port, the
attached PXC+LSR device can do one of the following. The wavelength attached PXC+LSR device can do one of the following. The wavelength
may be cross-connected by the PXC element to other out-bound optical may be cross-connected by the PXC element to other out-bound optical
channel, or the wavelength may be terminated as a Packet interface channel, or the wavelength may be terminated as a Packet interface
and packets switched. and packets switched.
From a GMPLS perspective the PXC+LSR functionality is treated as a From a GMPLS perspective the PXC+LSR functionality is treated as a
single interface. The interface is described using two Interface single interface. The interface is described using two Interface
skipping to change at page 18, line 4 skipping to change at page 19, line 39
only one wavelength be on a port of the PXC. On such a port, the only one wavelength be on a port of the PXC. On such a port, the
attached PXC+LSR device can do one of the following. The wavelength attached PXC+LSR device can do one of the following. The wavelength
may be cross-connected by the PXC element to other out-bound optical may be cross-connected by the PXC element to other out-bound optical
channel, or the wavelength may be terminated as a Packet interface channel, or the wavelength may be terminated as a Packet interface
and packets switched. and packets switched.
From a GMPLS perspective the PXC+LSR functionality is treated as a From a GMPLS perspective the PXC+LSR functionality is treated as a
single interface. The interface is described using two Interface single interface. The interface is described using two Interface
descriptors, one for the LSC and another for the PSC, with descriptors, one for the LSC and another for the PSC, with
appropriate parameters. For example, appropriate parameters. For example,
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = LSC Interface Switching Capability = LSC
Encoding = SONET ANSI T1.105 (comes from WDM) Encoding = SDH (comes from WDM)
Reservable Bandwidth = OC192 Reservable Bandwidth = OC192
and and
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = PSC-1 Interface Switching Capability = PSC-1
Encoding = SONET ANSI T1.105 Encoding = SDH
Max LSP Bandwidth[p] = 10 Gbps, for all p Max LSP Bandwidth[p] = 10 Gbps, for all p
6.4.10.4. Interface on a TDM+LSR device 8.4. Interface on a TDM+LSR device
On a TDM+LSR device that offers a channelized SONET/SDH interface the On a TDM+LSR device that offers a channelized SDH interface the
following may be possible: following may be possible:
- A subset of the SONET/SDH channels may be uncommitted. That is, - A subset of the SDH channels may be uncommitted. That is, they
they are not currently in use and hence are available for are not currently in use and hence are available for allocation.
allocation.
- A second subset of channels may already be committed for transit - A second subset of channels may already be committed for transit
purposes. That is, they are already cross-connected by the purposes. That is, they are already cross-connected by the SDH
SONET/SDH cross connect function to other out-bound channels and cross connect function to other out-bound channels and thus are
thus are not immediately available for allocation. not immediately available for allocation.
- Another subset of channels could be in use as terminal channels. - Another subset of channels could be in use as terminal channels.
That is, they are already allocated by terminate on a packet That is, they are already allocated by terminate on a packet
interface and packets switched. interface and packets switched.
From a GMPLS perspective the TDM+PSC functionality is treated as a From a GMPLS perspective the TDM+PSC functionality is treated as a
single interface. The interface is described using two Interface single interface. The interface is described using two Interface
descriptors, one for the TDM and another for the PSC, with descriptors, one for the TDM and another for the PSC, with
appropriate parameters. For example, appropriate parameters. For example,
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = TDM [Standard SONET] Interface Switching Capability = TDM [Standard SDH]
Encoding = SONET ANSI T1.105 Encoding = SDH
Min LSP Bandwidth = VT1.5 Min LSP Bandwidth = VT1.5
Max LSP Bandwidth[p] = STS192, for all p Max LSP Bandwidth[p] = STS192, for all p
and and
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = PSC-1 Interface Switching Capability = PSC-1
Encoding = SONET ANSI T1.105 Encoding = SDH
Max LSP Bandwidth[p] = 10 Gbps, for all p Max LSP Bandwidth[p] = 10 Gbps, for all p
7. Security Considerations 9. Security Considerations
The routing extensions proposed in this document do not raise any new The routing extensions proposed in this document do not raise any new
security concerns. security concerns.
8. Acknowledgements 10. Acknowledgements
The authors would like to thank Suresh Katukam, Jonathan Lang and The authors would like to thank Suresh Katukam, Jonathan Lang and
Quaizar Vohra for their comments on the draft. Quaizar Vohra for their comments on the draft.
9. References 11. Appendix: Bandwidth Encoding
The following table enumerates encoding in IEEE floating point format
some of the discrete values that could be used to identify the
bandwidth.
Signal Type (Bit-rate) Value (Bytes/Sec)
(IEEE Floating point)
-------------- --------------- ---------------------
DS0 (0.064 Mbps) 0x45FA0000
DS1 (1.544 Mbps) 0x483C7A00
E1 (2.048 Mbps) 0x487A0000
DS2 (6.312 Mbps) 0x4940A080
E2 (8.448 Mbps) 0x4980E800
Ethernet (10.00 Mbps) 0x49989680
E3 (34.368 Mbps) 0x4A831A80
DS3 (44.736 Mbps) 0x4AAAA780
STS-1 (51.84 Mbps) 0x4AC5C100
Fast Ethernet (100.00 Mbps) 0x4B3EBC20
E4 (139.264 Mbps) 0x4B84D000
FC-0 133M 0x4B7DAD68
OC-3/STM-1 (155.52 Mbps) 0x4B9450C0
FC-0 266M 0x4BFDAD68
FC-0 531M 0x4C7D3356
OC-12/STM-4 (622.08 Mbps) 0x4C9450C0
GigE (1000.00 Mbps) 0x4CEE6B28
FC-0 1062M 0x4CFD3356
OC-48/STM-16 (2488.32 Mbps) 0x4D9450C0
OC-192/STM-64 (9953.28 Mbps) 0x4E9450C0
10GigE-LAN (10000.00 Mbps) 0x4E9502F9
OC-768/STM-256 (39813.12 Mbps) 0x4F9450C0
12. References
[ISIS-TE] Smit, H., Li, T., "IS-IS Extensions for Traffic [ISIS-TE] Smit, H., Li, T., "IS-IS Extensions for Traffic
Engineering", draft-ietf-isis-traffic-02.txt (work in progress) Engineering", draft-ietf-isis-traffic-02.txt (work in progress)
[LSP-HIER] Kompella, K., Rekhter, Y., "LSP Hierarchy with MPLS TE", [LSP-HIER] Kompella, K., Rekhter, Y., "LSP Hierarchy with MPLS TE",
draft-ietf-mpls-lsp-hierarchy-01.txt (work in progress) draft-ietf-mpls-lsp-hierarchy-01.txt (work in progress)
[GMPLS-SIG] Generalized MPLS Group, "Generalized MPLS - Signaling [GMPLS-SIG] Ashwood-Smith, P., et al., "Generalized MPLS - Signaling
Functional Description", draft-ietf-mpls-generalized-signaling-05.txt Functional Description", draft-ietf-mpls-generalized-signaling-05.txt
(work in progress) (work in progress)
[GMPLS-SONET-SDH] Mannie, E., "GMPLS Extensions for SONET and SDH
Control", work in progress
[OSPF-TE] Katz, D., Yeung, D., Kompella, K., "Traffic Engineering [OSPF-TE] Katz, D., Yeung, D., Kompella, K., "Traffic Engineering
Extensions to OSPF", draft-katz-yeung-ospf-traffic-05.txt Extensions to OSPF", draft-katz-yeung-ospf-traffic-05.txt
[GMPLS-ISIS] Kompella, K., Rekhter, Y., Banerjee, A. et al, "IS-IS [GMPLS-ISIS] Kompella, K., Rekhter, Y., Banerjee, A. et al, "IS-IS
Extensions in Support of Generalized MPLS", draft-ietf-isis-gmpls- Extensions in Support of Generalized MPLS", draft-ietf-isis-gmpls-
extensions-02.txt (work in progress) extensions-02.txt (work in progress)
[GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF [GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF
Extensions in Support of Generalized MPLS", draft-ietf-ccamp-ospf- Extensions in Support of Generalized MPLS", draft-ietf-ccamp-ospf-
gmpls-extensions-00.txt (work in progress) gmpls-extensions-00.txt (work in progress)
[LINK-BUNDLE] Kompella, K., Rekhter, Y., Berger, L., "Link Bundling [LINK-BUNDLE] Kompella, K., Rekhter, Y., Berger, L., "Link Bundling
in MPLS Traffic Engineering", draft-ietf-mpls-bundle-00.txt (work in in MPLS Traffic Engineering", draft-ietf-mpls-bundle-00.txt (work in
progress) progress)
[LMP] [LMP] Lang, J., et al., "Link Management Protocol (LMP)", work in
progress
[OVPN] Ould-Brahim, H., Rekhter, Y., Fedyk, D., Ashwood-Smith, P.,
Rosen, E., Mannie, E., Fang, L., Drake, J., "BGP/GMPLS Optical VPNs",
draft-ouldbrahim-bgpgmpls-ovpn-01.txt (work in progress)
10. Authors' Information 13. Authors' Information
Kireeti Kompella Kireeti Kompella
Juniper Networks, Inc. Juniper Networks, Inc.
1194 N. Mathilda Ave 1194 N. Mathilda Ave
Sunnyvale, CA 94089 Sunnyvale, CA 94089
Email: kireeti@juniper.net Email: kireeti@juniper.net
Yakov Rekhter Yakov Rekhter
Juniper Networks, Inc. Juniper Networks, Inc.
1194 N. Mathilda Ave 1194 N. Mathilda Ave
skipping to change at line 914 skipping to change at page 24, line 33
335 Elan Village Lane, Unit 203 335 Elan Village Lane, Unit 203
San Jose, CA 95134-2539 San Jose, CA 95134-2539
Phone: +1 408-943-1794 Phone: +1 408-943-1794
Email: v.sharma@ieee.org Email: v.sharma@ieee.org
Debashis Basak Debashis Basak
AcceLight Networks, AcceLight Networks,
70 Abele Rd, Bldg 1200 70 Abele Rd, Bldg 1200
Bridgeville PA 15017 Bridgeville PA 15017
Email: dbasak@accelight.com Email: dbasak@accelight.com
Lou Berger
Movaz Networks, Inc.
7926 Jones Branch Drive
Suite 615
McLean VA, 22102
Email: lberger@movaz.com
 End of changes. 

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