draft-ietf-ccamp-gmpls-routing-03.txt   draft-ietf-ccamp-gmpls-routing-04.txt 
skipping to change at page 1, line 17 skipping to change at page 1, line 17
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) L. Berger (Movaz Networks)
Routing Extensions in Support of Generalized MPLS Routing Extensions in Support of Generalized MPLS
draft-ietf-ccamp-gmpls-routing-03.txt draft-ietf-ccamp-gmpls-routing-04.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 11, line 6 skipping to change at page 11, line 6
hierarchy, with the leaf and the root of the branch being defined by hierarchy, with the leaf and the root of the branch being defined by
the Minimum LSP Bandwidth and the Maximum LSP Bandwidth at priority the Minimum LSP Bandwidth and the Maximum LSP Bandwidth at priority
p. p.
On an interface having Arbitrary SDH multiplexing, an LSP at priority On an interface having Arbitrary SDH multiplexing, an LSP at priority
p could reserve any bandwidth between the Minimum LSP Bandwidth and p could reserve any bandwidth between the Minimum LSP Bandwidth and
the Maximum LSP Bandwidth at priority p, provided that the bandwidth the Maximum LSP Bandwidth at priority p, provided that the bandwidth
reserved by the LSP is a multiple of the Minimum LSP Bandwidth. reserved by the LSP is a multiple of the Minimum LSP Bandwidth.
Interface Switching Capability Descriptor for the interfaces that Interface Switching Capability Descriptor for the interfaces that
support sub-STS1 may include additional information. The nature and support sub VC-3 may include additional information. The nature and
the encoding of such information is outside the scope of this the encoding of such information is outside the scope of this
document. 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 SDH multiplexing hierarchy, multiple Interface branches of the SDH multiplexing hierarchy, multiple Interface
Switching Capability Descriptors would be advertised, one per branch. Switching Capability Descriptors would be advertised, one per branch.
For example, if an interface supports VT-1.5 and VT-2 (which are not For example, if an interface supports VC-11 and VC-12 (which are not
part of same branch of SDH multiplexing tree), Then it could part of same branch of SDH multiplexing tree), then 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
supported by the interface at a given priority number. supported by the interface at a given priority number.
A way to handle the case of multiple data rates or multiple encodings A way to handle the case of multiple data rates or multiple encodings
within a single TE Link, multiple Interface Switching Capability within a single TE Link, multiple Interface Switching Capability
Descriptors would be advertised, one per supported data rate and Descriptors would be advertised, one per supported data rate and
encoding combination. For example, an LSC interface could support encoding combination. For example, an LSC interface could support
the establishment of LSC LSPs at both OC-48c and OC-192c data rates. the establishment of LSC LSPs at both STM-16 and STM-64 data rates.
6.4.5. Fiber-Switch Capable 6.4.5. Fiber-Switch Capable
If an interface is of type FSC, it means that the node receiving data If an interface is of type FSC, it means that the node receiving data
over this interface can switch the entire contents to another over this interface can switch the entire contents to another
interface (without distinguishing lambdas, channels or packets). interface (without distinguishing lambdas, channels or packets).
I.e., an interface of type FSC switches at the granularity of an I.e., an interface of type FSC switches at the granularity of an
entire interface, and can not extract individual lambdas within the entire interface, and can not extract individual lambdas within the
interface. An interface of type FSC can not restrict itself to just interface. An interface of type FSC can not restrict itself to just
one lambda. one lambda.
skipping to change at page 12, line 42 skipping to change at page 12, line 42
[PSC, LSC] - label represents a lambda [PSC, LSC] - label represents a lambda
[PSC, FSC] - label represents a port [PSC, FSC] - label represents a port
[TDM, LSC] - label represents a lambda [TDM, LSC] - label represents a lambda
[TDM, FSC] - label represents a port [TDM, FSC] - label represents a port
[LSC, 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 VC-3, VC-4, VC-4-4c, VC-4-16c and VC-4-64c
LSPs can be established on a OC-192 interface whose Encoding Type is LSPs can be established on a STM-64 interface whose Encoding Type is
SDH. Thus, initially in the Interface Switching Capability Descriptor SDH. Thus, initially in the Interface Switching Capability Descriptor
the Minimum LSP Bandwidth is set to STS-1, and Maximum LSP Bandwidth the Minimum LSP Bandwidth is set to VC-3, and Maximum LSP Bandwidth
is set to STS-192 for all priorities. As soon as an LSP of STS-1 is set to STM-64 for all priorities. As soon as an LSP of VC-3 size
size at priority 1 is established on the interface, it is no longer at priority 1 is established on the interface, it is no longer
capable of STS-192c for all but LSPs at priority 0. Therefore, the capable of VC-4-64c for all but LSPs at priority 0. Therefore, the
node advertises a modified Interface Switching Capability Descriptor node 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 STM-64, but
STS-48 for all but priority 0 (at priority 0 the Maximum LSP STM-16 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 STM-64). If subsequently there is another VC-3
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 VC-4-16c 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.5. Bandwidth Encoding
Encoding in IEEE floating point format of the discrete values that
could be used to identify Unreserved bandwidth, Maximum LSP bandwidth
and Minimum LSP bandwidth is described in Section 3.1.2 of [GMPLS-
SIG].
7. Examples of Interface Switching Capability Descriptor 7. Examples of Interface Switching Capability Descriptor
7.1. STS-48 POS Interface on a LSR 7.1. STM-16 POS Interface on a LSR
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = PSC-1 Interface Switching Capability = PSC-1
Encoding = SDH 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.
7.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.
7.3. OC-192 SDH Interface on a Digital Cross Connect with Standard SDH 7.3. STM-64 SDH Interface on a Digital Cross Connect with Standard SDH
Consider a branch of SDH multiplexing tree : VT-1.5, STS-1, STS-3c, Consider a branch of SDH multiplexing tree : VC-3, VC-4, VC-4-4c,
STS-12c, STS-48c, STS-192c. If it is possible to establish all these VC-4-16c, VC-4-64c. If it is possible to establish all these
connections on a OC-192 interface, the Interface Switching Capability connections on a STM-64 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 SDH] Interface Switching Capability = TDM [Standard SDH]
Encoding = SDH Encoding = SDH
Min LSP Bandwidth = VT1.5 Min LSP Bandwidth = VC-3
Max LSP Bandwidth[p] = STS192, for all p Max LSP Bandwidth[p] = STM-64, 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.
7.4. OC-192 SDH Interface on a Digital Cross Connect with two types of 7.4. STM-64 SDH Interface on a Digital Cross Connect with two types of
SDH multiplexing hierarchy supported SDH multiplexing hierarchy supported
Interface Switching Capability Descriptor 1: Interface Switching Capability Descriptor 1:
Interface Switching Capability = TDM [Standard SDH] Interface Switching Capability = TDM [Standard SDH]
Encoding = SDH Encoding = SDH
Min LSP Bandwidth = VT1.5 Min LSP Bandwidth = VC-3
Max LSP Bandwidth[p] = STS192, for all p Max LSP Bandwidth[p] = STM-64, for all p
Interface Switching Capability Descriptor 2: Interface Switching Capability Descriptor 2:
Interface Switching Capability = TDM [Arbitrary SDH] Interface Switching Capability = TDM [Arbitrary SDH]
Encoding = SDH Encoding = SDH
Min LSP Bandwidth = VT2 Min LSP Bandwidth = VC-4
Max LSP Bandwidth[p] = STS192, for all p Max LSP Bandwidth[p] = STM-64, 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.
7.5. Interface on an opaque OXC (SDH framed) with support for one lambda 7.5. Interface on an opaque OXC (SDH framed) with support for one lambda
per port/interface 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 SDH line) is switched transparently without lambda (carrying the SDH line) is switched transparently without
further multiplexing/demultiplexing, and either none of the SDH further multiplexing/demultiplexing, and either none of the SDH
skipping to change at page 15, line 11 skipping to change at page 15, line 20
interfaces on a given OXC are required to have identifiers unique to interfaces on a given OXC are required to have identifiers unique to
that OXC, and these identifiers are used as labels (see 3.2.1.1 of that OXC, and these identifiers are used as labels (see 3.2.1.1 of
[GMPLS-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 an SDH 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 = SDH Encoding = SDH
Reservable Bandwidth = Determined by SDH Framer (say OC192) Reservable Bandwidth = Determined by SDH Framer (say STM-64)
7.6. Interface on a transparent OXC (PXC) with external DWDM that 7.6. Interface on a transparent OXC (PXC) with external DWDM that
understands SDH 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.
skipping to change at page 15, line 44 skipping to change at page 16, line 8
that PXC, and these identifiers are used as labels (see 3.2.1.1 of that PXC, and these identifiers are used as labels (see 3.2.1.1 of
[GMPLS-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 SDH framing: understands SDH framing:
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = LSC Interface Switching Capability = LSC
Encoding = SDH (comes from DWDM) Encoding = SDH (comes from DWDM)
Reservable Bandwidth = Determined by DWDM (say OC192) Reservable Bandwidth = Determined by DWDM (say STM-64)
7.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.
skipping to change at page 17, line 38 skipping to change at page 17, line 44
have identifiers unique to that interface, and these identifiers are have identifiers unique to that interface, and these identifiers are
used as labels (see 3.2.1.1 of [GMPLS-SIG]). used as labels (see 3.2.1.1 of [GMPLS-SIG]).
The following is an example of an interface switching capability The following is an example of an interface switching capability
descriptor on an OXC with internal DWDM that understands SDH framing descriptor on an OXC with internal DWDM that understands SDH framing
and supports discrete bandwidths: and supports discrete bandwidths:
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = LSC Interface Switching Capability = LSC
Encoding = SDH (comes from DWDM) Encoding = SDH (comes from DWDM)
Max LSP Bandwidth = Determined by DWDM (say OC192) Max LSP Bandwidth = Determined by DWDM (say STM-16)
Interface Switching Capability = LSC Interface Switching Capability = LSC
Encoding = SDH (comes from DWDM) Encoding = SDH (comes from DWDM)
Max LSP Bandwidth = Determined by DWDM (say OC48) Max LSP Bandwidth = Determined by DWDM (say STM-64)
7.10. Interface on a OXC with internal DWDM that is transparent to bit- 7.10. Interface on a OXC with internal DWDM that is transparent to bit-
rate and framing rate and framing
This example assumes that DWDM and OXC are connected in such a way This example assumes that DWDM and OXC are connected in such a way
that each interface on the OXC handles multiple wavelengths that each interface on the OXC handles multiple wavelengths
individually. In this case an interface on the OXC is considered LSC, individually. In this case an interface on the OXC is considered LSC,
and not FSC. and not FSC.
_______ _______
skipping to change at page 19, line 11 skipping to change at page 19, line 11
SDH 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 = SDH (comes from WDM) Encoding = SDH (comes from WDM)
Reservable Bandwidth = OC192 Reservable Bandwidth = STM-64
and and
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = TDM [Standard SDH] Interface Switching Capability = TDM [Standard SDH]
Encoding = SDH Encoding = SDH
Min LSP Bandwidth = VT1.5 Min LSP Bandwidth = VC-3
Max LSP Bandwidth[p] = STS192, for all p Max LSP Bandwidth[p] = STM-64, for all p
8.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.
8.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
skipping to change at page 19, line 43 skipping to change at page 19, line 43
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 = SDH (comes from WDM) Encoding = SDH (comes from WDM)
Reservable Bandwidth = OC192 Reservable Bandwidth = STM-64
and and
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = PSC-1 Interface Switching Capability = PSC-1
Encoding = SDH Encoding = SDH
Max LSP Bandwidth[p] = 10 Gbps, for all p Max LSP Bandwidth[p] = 10 Gbps, for all p
8.4. Interface on a TDM+LSR device 8.4. Interface on a TDM+LSR device
skipping to change at page 20, line 31 skipping to change at page 20, line 31
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 SDH] Interface Switching Capability = TDM [Standard SDH]
Encoding = SDH Encoding = SDH
Min LSP Bandwidth = VT1.5 Min LSP Bandwidth = VC-3
Max LSP Bandwidth[p] = STS192, for all p Max LSP Bandwidth[p] = STM-64, for all p
and and
Interface Switching Capability Descriptor: Interface Switching Capability Descriptor:
Interface Switching Capability = PSC-1 Interface Switching Capability = PSC-1
Encoding = SDH Encoding = SDH
Max LSP Bandwidth[p] = 10 Gbps, for all p Max LSP Bandwidth[p] = 10 Gbps, for all p
9. 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.
10. Acknowledgements 10. Acknowledgements
The authors would like to thank Suresh Katukam, Jonathan Lang and The authors would like to thank Suresh Katukam, Jonathan Lang, Zhi-
Quaizar Vohra for their comments on the draft. Wei Lin, and Quaizar Vohra for their comments and contributions to
the draft.
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 11. 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-04.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-04.txt (work in progress)
[GMPLS-SIG] Ashwood-Smith, P., et al., "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-07.txt
(work in progress) (work in progress)
[GMPLS-SONET-SDH] Mannie, E., "GMPLS Extensions for SONET and SDH [GMPLS-SONET-SDH] Mannie, E., "GMPLS Extensions for SONET and SDH
Control", work in progress Control", draft-ietf-ccamp-gmpls-sonet-sdh-03.txt (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-06.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-10.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-06.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] Lang, J., et al., "Link Management Protocol (LMP)", work in [LMP] Lang, J., et al., "Link Management Protocol (LMP)", work in
progress progress
13. Authors' Information 12. 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
 End of changes. 

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