draft-ietf-isis-gmpls-extensions-07.txt   draft-ietf-isis-gmpls-extensions-08.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: July 2002 A. Banerjee (Calient Networks) Expiration Date: August 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.)
IS-IS Extensions in Support of Generalized MPLS IS-IS Extensions in Support of Generalized MPLS
draft-ietf-isis-gmpls-extensions-07.txt draft-ietf-isis-gmpls-extensions-08.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 3, line 19 skipping to change at page 3, line 19
Protocol Label Switching (GMPLS). The set of required enhancements to Protocol Label Switching (GMPLS). The set of required enhancements to
IS-IS are outlined in [GMPLS-ROUTING]. IS-IS are outlined in [GMPLS-ROUTING].
5. IS-IS Routing Enhancements 5. IS-IS 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 that can be announced in IS-IS TE LSAs. GMPLS TE links that can be announced in IS-IS TE LSAs.
In this document, we enhance the sub-TLVs for the extended IS In this document, we enhance the sub-TLVs for the extended IS
reachability TLV (see [ISIS-TE]) in support of GMPLS. Specifically, reachability TLV (see [ISIS-TE]) in support of GMPLS. Specifically,
we add sub-TLVs for: Outgoing/Incoming Interface Identifier, Link we add the following sub-TLVs:
Protection Type, and Interface Switching Capability Descriptor. This
brings the list of sub-TLVs of the extended IS reachability TLV to: 1. Link Local Identifier
2. Remote Interface Identifier
3. Link Protection Type
4. Interface Switching Capability Descriptor
This brings the list of sub-TLVs of the extended IS reachability TLV
to:
Sub-TLV Type Length Name Sub-TLV Type Length Name
3 4 Administrative group (color) 3 4 Administrative group (color)
4 4 Link Local Identifier 4 4 Link Local Identifier
5 4 Link Remote Identifier 5 4 Link Remote Identifier
6 4 IPv4 interface address 6 variable IPv4 interface address
8 4 IPv4 neighbor address 8 variable IPv4 neighbor address
9 4 Maximum link bandwidth 9 4 Maximum link bandwidth
10 4 Reservable link bandwidth 10 4 Reservable link bandwidth
11 32 Unreserved bandwidth 11 32 Unreserved bandwidth
18 3 TE Default metric 18 3 TE Default metric
20 2 Link Protection Type 20 2 Link Protection Type
21 variable Interface Switching Capability Descriptor 21 variable Interface Switching Capability Descriptor
250-254 - Reserved for cisco specific extensions 250-254 - Reserved for cisco specific extensions
255 - Reserved for future expansion 255 - Reserved for future expansion
We further add one new TLV to the TE LSAs. We further add one new TLV to the TE LSAs.
skipping to change at page 6, line 8 skipping to change at page 6, line 8
Maximum LSP Bandwidth is encoded as a list of eight 4 octet fields in Maximum LSP Bandwidth is encoded as a list of eight 4 octet fields in
the IEEE floating point format, with priority 0 first and priority 7 the IEEE floating point format, with priority 0 first and priority 7
last. The units are bytes (not bits!) per second. last. The units are bytes (not bits!) per second.
The content of the Switching Capability specific information field The content of the Switching Capability specific information field
depends on the value of the Switching Capability field. depends on the value of the Switching Capability field.
When the Switching Capability field is PSC-1, PSC-2, PSC-3, or PSC-4, When the Switching Capability field is PSC-1, PSC-2, PSC-3, or PSC-4,
the specific information includes Interface MTU and Minimum LSP the specific information includes Interface MTU and Minimum LSP
Bandwidth. The Interface MTU is encoded as a two octets integer. The Bandwidth. The Interface MTU is encoded as a 2 octets integer. The
Minimum LSP Bandwidth is is encoded in a 4 octets field in the IEEE Minimum LSP Bandwidth is is encoded in a 4 octets field in the IEEE
floating point format. The units are bytes (not bits!) per second. floating point format. The units are bytes (not bits!) per second.
When the Switching Capability field is L2SC, there is no specific When the Switching Capability field is L2SC, there is no specific
information. information.
When the Switching Capability field is TDM, the specific information When the Switching Capability field is TDM, the specific information
includes Minimum LSP Bandwidth, and an indication whether the includes Minimum LSP Bandwidth, and an indication whether the
interface supports Standard or Arbitrary SONET/SDH. The Minimum LSP interface supports Standard or Arbitrary SONET/SDH. The Minimum LSP
Bandwidth is encoded in a 4 octets field in the IEEE floating point Bandwidth is encoded in a 4 octets field in the IEEE floating point
skipping to change at page 6, line 39 skipping to change at page 6, line 39
than once within the extended IS reachability TLV (this is needed to than once within the extended IS reachability TLV (this is needed to
handle interfaces that support multiple switching capabilities). handle interfaces that support multiple switching capabilities).
5.5. Shared Risk Link Group TLV 5.5. Shared Risk Link Group TLV
The proposed SRLG (of type 138 TBD) contains a new data structure The proposed SRLG (of type 138 TBD) contains a new data structure
consisting of: consisting of:
7 octets of System ID and Pseudonode Number 7 octets of System ID and Pseudonode Number
1 octet Flag 1 octet Flag
4 octets of IPv4 interface address or 4 octets of an Outgoing 4 octets of IPv4 interface address or 4 octets of a Link Local
Interface Identifier Identifier
4 octets of IPv4 neighbor address or 4 octets of an Incoming 4 octets of IPv4 neighbor address or 4 octets of a Link Remote
Interface Identifier Identifier
and a list of SRLG values, where each element in the list has 4 and a list of SRLG values, where each element in the list has 4
octets. The length of this TLV is 16 + 4 * (number of SRLG values). octets. The length of this TLV is 16 + 4 * (number of SRLG values).
The Least Significant Bit of the Flag octet indicates whether the The Least Significant Bit of the Flag octet indicates whether the
interface is numbered (set to 1), or unnumbered (set to 0). All other interface is numbered (set to 1), or unnumbered (set to 0). All other
bits are reserved and should be set to 0. bits are reserved and should be set to 0.
5.6. Link Identifier for Unnumbered Interfaces 5.6. Link Identifier for Unnumbered Interfaces
The Link Identifier TLV is carried as part of the Point-to-point ISIS The Link Identifier TLV is carried as part of the Point-to-point ISIS
Hello PDUs. The Type field of this TLV is TBD. The Length field of Hello PDUs. The Type field of this TLV is TBD. The Length field of
this TLV is set to 4. The Value field of this TLV contains 4 octets this TLV is set to 4. The Value field of this TLV contains 4 octets
that encode the Identifier assigned to the link over which this PDU that encode the Identifier assigned to the link over which this PDU
is to be transmitted by the LSR that transmits the PDU. is to be transmitted by the LSR that transmits the PDU.
6. Security Considerations 6. Implications on Graceful Restart
The restarting node should follow the ISIS restart procedures [ISIS-
RESTART], and the RSVP-TE restart procedures [GMPLS-RSVP].
Once the restarting node re-establishes at least one ISIS adjacency,
the node should originate its TE LSAs. These LSAs should be
originated with 0 unreserved bandwidth until the node is able to
determine the amount of unreserved resources taking into account the
resources reserved by the already established LSPs that have been
preserved across the restart. Once the restarting node determines the
amount of unreserved resources, taking into account the resources
reserved by the already established LSPs that have been preserved
across the restart, the node should advertise these resources in its
TE LSAs.
Neighbors of the restarting node should continue advertise the actual
unreserved bandwidth on the TE links from the neighbors to that node.
Regular graceful restart should not be aborted if a TE LSA or TE
topology changes. TE graceful restart need not be aborted if a TE LSA
or TE topology changes.
7. Security Considerations
The extensions proposed in this document does not raise any new The extensions proposed in this document does not raise any new
security concerns. security concerns.
7. Acknowledgements 8. 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.
8. References 9. References
[ISIS-TE] Smit, H., Li, T., "IS-IS Extensions for Traffic [ISIS-TE] Smit, H., Li, T., "IS-IS Extensions for Traffic
Engineering", Engineering",
draft-ietf-isis-traffic-03.txt (work in progress) draft-ietf-isis-traffic-03.txt (work in progress)
[GMPLS-SIG] Generalized MPLS Group, "Generalized MPLS - Signaling [GMPLS-SIG] Generalized MPLS Group, "Generalized MPLS - Signaling
Functional Functional
Description", draft-ietf-mpls-generalized-signaling-04.txt (work Description", draft-ietf-mpls-generalized-signaling-04.txt (work
in progress) in progress)
[GMPLS-ROUTING] "Routing Extensions in Support of Generalized MPLS", [GMPLS-ROUTING] "Routing Extensions in Support of Generalized MPLS",
draft-many-ccamp-gmpls-routing-00.txt draft-many-ccamp-gmpls-routing-01.txt (work in progress)
9. Authors' Information [ISIS-RESTART] "Restart signaling for ISIS", draft-ietf-isis-
restart-00.txt
(work in progress)
[GMPLS-RSVP] "Generalized MPLS Signaling - RSVP-TE Extensions",
draft-ietf-mpls-generalized-rsvp-te-06.txt (work in progress)
10. 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/