draft-ietf-isis-gmpls-extensions-01.txt   draft-ietf-isis-gmpls-extensions-02.txt 
Network Working Group K. Kompella (Juniper Networks) Network Working Group K. Kompella (Juniper Networks)
Internet Draft Y. Rekhter (Cisco Systems) Internet Draft Y. Rekhter (Juniper Networks)
Expiration Date: May 2001 A. Banerjee (Calient Networks) Expiration Date: August 2001 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 (Tellabs) V. Sharma (Tellabs)
IS-IS Extensions in Support of Generalized MPLS IS-IS Extensions in Support of Generalized MPLS
draft-ietf-isis-gmpls-extensions-01.txt draft-ietf-isis-gmpls-extensions-02.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 5, line 48 skipping to change at page 5, line 48
compatibility, one MAY set the Maximum Link Bandwidth to the Maximum compatibility, one MAY set the Maximum Link Bandwidth to the Maximum
LSP Bandwidth at priority 7 of the link. LSP Bandwidth at priority 7 of the link.
5.4. Link Protection Type sub-TLV 5.4. Link Protection Type sub-TLV
The Link Protection Type sub-TLV represents the protection capability The Link Protection Type sub-TLV represents the protection capability
that exists on a link. It is desirable to carry this information so that exists on a link. It is desirable to carry this information so
that it may be used by the path computation algorithm to set up LSPs that it may be used by the path computation algorithm to set up LSPs
with appropriate protection characteristics. This is a sub-TLV (of with appropriate protection characteristics. This is a sub-TLV (of
type 20) of the extended IS reachability TLV, with length two octets, type 20) of the extended IS reachability TLV, with length two octets,
the first of which can take one of the following values: the first of which is a bit vector describing the protection
capabilities of the link. They are:
Value Link Protection Type 0x01 Extra Traffic
0 Unprotected If the link is Extra Traffic, it indicates that these links are
1 Shared protecting other (primary) links. The LSPs on a link of this
2 Dedicated 1:1 type will be lost if the primary links being protected fail.
3 Dedicated 1+1
4 Enhanced
If the link is Unprotected, it means that there is no backup link for 0x02 Unprotected
traffic being carried on the link. If the link is Unprotected, it means that there is no backup link
for traffic being carried on the link.
0x04 Shared
If the link has Shared protection, it means that for the N > 1 If the link has Shared protection, it means that for the N > 1
primary data-bearing channels, there are M disjoint backup data- primary data-bearing channels, there are M disjoint backup data-
bearing channels reserved to carry the traffic. Additionally, the bearing channels reserved to carry the traffic. Additionally, the
protection data-bearing channel MAY carry low-priority preemptable protection data-bearing channel MAY carry low-priority preemptable
traffic. The bandwidth of backup data-bearing channels will be traffic. The bandwidth of backup data-bearing channels will be
announced in the unreserved bandwidth sub-TLV at the appropriate announced in the unreserved bandwidth sub-TLV at the appropriate
priority. priority.
0x08 Dedicated 1:1
If the link has Dedicated 1:1 protection, it means that for each If the link has Dedicated 1:1 protection, it means that for each
primary data-bearing channel, there is one disjoint backup data- primary data-bearing channel, there is one disjoint backup data-
bearing channel reserved to carry the traffic. Additionally, the bearing channel reserved to carry the traffic. Additionally, the
protection data-bearing channel MAY carry low-priority preemptable protection data-bearing channel MAY carry low-priority preemptable
traffic. The bandwidth of backup data-bearing channels will be traffic. The bandwidth of backup data-bearing channels will be
announced in the unreserved bandwidth sub-TLV at the appropriate announced in the unreserved bandwidth sub-TLV at the appropriate
priority. priority.
0x10 Dedicated 1+1
If the link has Dedicated 1+1 protection, it means that a disjoint If the link has Dedicated 1+1 protection, it means that a disjoint
backup data-bearing channel is reserved and dedicated for protecting backup data-bearing channel is reserved and dedicated for
the primary data-bearing channel. This backup data-bearing channel protecting the primary data-bearing channel. This backup data-
is not shared by any other connection, and traffic is duplicated and bearing channel is not shared by any other connection, and traffic
carried simultaneously over both channels. is duplicated and carried simultaneously over both channels.
If the link has Enhanced protection, it indicates that the protection 0x20 Enhanced
scheme for the link is more reliable than the Dedicated 1+1, e.g., 4 If the link has Enhanced protection, it indicates that a protection
fiber BLSR/MS-SPRING. scheme that is more reliable than Dedicated 1+1 is being used,
e.g., 4 fiber BLSR/MS-SPRING to protect this link.
0x40 Reserved
0x80 Reserved
The second octet gives a priority value such that a new connection The second octet gives a priority value such that a new connection
with a higher priority (i.e., numerically lower than this value) is with a higher priority (i.e., numerically lower than this value) is
guaranteed to be setup on a primary (or working) channel, and not on guaranteed to be setup on a primary (or working) channel, and not on
a secondary (or protect) channel. a secondary (or protect) channel.
The Link Protection Type sub-TLV is optional and if an LSA does not The Link Protection Type sub-TLV is optional and if an LSA does not
carry the TLV, then the Link Protection Type is unknown. The carry the TLV, then the Link Protection Type is unknown. The
protection capability of a link is typically pre-configured and does protection capability of a link is typically pre-configured and does
not change dynamically over time. The working priority value is pre- not change dynamically over time. The working priority value is pre-
skipping to change at page 10, line 38 skipping to change at page 10, line 45
[2] Basak, D., Awduche, D., Drake, J., Rekhter, Y., "Multi- [2] Basak, D., Awduche, D., Drake, J., Rekhter, Y., "Multi-
protocol Lambda Switching: Issues in Combining MPLS Traffic protocol Lambda Switching: Issues in Combining MPLS Traffic
Engineering Control With Optical Crossconnects", Engineering Control With Optical Crossconnects",
draft-basak-mpls-oxc-issues-01.txt (work in progress) draft-basak-mpls-oxc-issues-01.txt (work in progress)
[3] Smit, H., Li, T., "IS-IS Extensions for Traffic Engineering", [3] Smit, H., Li, T., "IS-IS Extensions for Traffic Engineering",
draft-ietf-isis-traffic-02.txt (work in progress) draft-ietf-isis-traffic-02.txt (work in progress)
[4] Kompella, K., Rekhter, Y., Berger, L., "Link Bundling in MPLS [4] Kompella, K., Rekhter, Y., Berger, L., "Link Bundling in MPLS
Traffic Engineering", draft-kompella-mpls-bundle-04.txt (work Traffic Engineering", draft-kompella-mpls-bundle-05.txt (work
in progress) in progress)
[5] Kompella, K., Rekhter, Y., "LSP Hierarchy with MPLS TE", [5] Kompella, K., Rekhter, Y., "LSP Hierarchy with MPLS TE",
draft-ietf-mpls-lsp-hierarchy-00.txt (work in progress) draft-ietf-mpls-lsp-hierarchy-01.txt (work in progress)
[6] Generalized MPLS Group, "Generalized MPLS - Signaling Functional [6] Generalized MPLS Group, "Generalized MPLS - Signaling Functional
Description", draft-ietf-mpls-generalized-signaling-01.txt (work Description", draft-ietf-mpls-generalized-signaling-02.txt (work
in progress) in progress)
[7] Lang J., Mitra K., Drake J., Kompella K., Rekhter Y., Berger L., [7] Lang J., Mitra K., Drake J., Kompella K., Rekhter Y., Berger L.,
Saha, D., Sandick, H., and Basak D., "Link Management Protocol", Saha, D., Sandick, H., and Basak D., "Link Management Protocol",
draft-ietf-mpls-lmp-01.txt (work in progress) draft-ietf-mpls-lmp-02.txt (work in progress)
9. Authors' Information 9. 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
Cisco Systems, Inc. Juniper Networks, Inc.
170 West Tasman Drive 1194 N. Mathilda Ave
San Jose, CA 95134 Sunnyvale, CA 94089
Email: yakov@cisco.com Email: yakov@juniper.net
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
John Drake John Drake
Calient Networks Calient Networks
skipping to change at page 12, line 36 skipping to change at page 12, line 36
Debanjan Saha Debanjan Saha
Tellium Optical Systems Tellium Optical Systems
2 Crescent Place 2 Crescent Place
P.O. Box 901 P.O. Box 901
Ocean Port, NJ 07757 Ocean Port, NJ 07757
Phone: (732) 923-4264 Phone: (732) 923-4264
Email: dsaha@tellium.com Email: dsaha@tellium.com
Vishal Sharma Vishal Sharma
Tellabs Research Center Jasmine Networks, Inc.
One Kendall Square 3061 Zanker Rd, Suite B
Bldg. 100, Ste. 121 San Jose, CA 95134
Cambridge, MA 02139-1562 Phone: (408) 895-5000
Phone: (617) 577-8760
Email: Vishal.Sharma@tellabs.com
 End of changes. 

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