draft-ietf-isis-gmpls-extensions-04.txt   draft-ietf-isis-gmpls-extensions-05.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: March 2002 A. Banerjee (Calient Networks) Expiration Date: May 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-04.txt draft-ietf-isis-gmpls-extensions-05.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, we add sub-TLVs for: Outgoing/Incoming Interface Identifier, Link
Interface MTU, Link Protection Type, and Interface Switching Protection Type, and Interface Switching Capability Descriptor. This
Capability Descriptor. This brings the list of sub-TLVs of the brings the list of sub-TLVs of the extended IS reachability TLV to:
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 Outgoing Interface Identifier 4 4 Link Local Identifier
5 4 Incoming Interface Identifier 5 4 Link Remote Identifier
6 4 IPv4 interface address 6 4 IPv4 interface address
7 2 Interface MTU
8 4 IPv4 neighbor address 8 4 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.
TLV Type Length Name TLV Type Length Name
138 (TBD) variable Shared Risk Link Group 138 (TBD) variable Shared Risk Link Group
Finally, we add one more TLV to the Hello PDUs. Finally, we add one more TLV to the Hello PDUs.
TLV Type Length Name TLV Type Length Name
(TBD) 4 Interface Identifier (TBD) 4 Link Identifier
5.1. Outgoing Interface Identifier
An Outgoing Interface Identifier is a sub-TLV of the extended IS
reachability TLV with type 4, length 4 and value equal to the
assigned identifier.
5.2. Incoming Interface Identifier 5.1. Link Local Identifier
An Incoming Interface Identifier is a sub-TLV of the extended IS A Link Local Interface Identifier is a sub-TLV of the extended IS
reachability TLV with type 5, length 4 and value equal to L's reachability TLV with type 4, and length 4.
incoming interface identifier.
5.3. Interface MTU 5.2. Link Remote Identifier
The Interface MTU is a sub-TLV of the extended IS reachability TLV A Link Remote Identifier is a sub-TLV of the extended IS reachability
with type 10, length 2, and value equal to the maximum size of an IP TLV with type 5, and length 4.
packet that can be transmitted on this interface without being
fragmented.
5.4. Link Protection Type 5.3. Link Protection Type
The Link Protection Type is is a sub-TLV (of type 20) of the The Link Protection Type is is a sub-TLV (of type 20) of the
extended IS reachability TLV, with length two octets, the first of extended IS reachability TLV, with length two octets, the first of
which is a bit vector describing the protection capabilities of the which is a bit vector describing the protection capabilities of the
link. They are: link. They are:
0x01 Extra Traffic 0x01 Extra Traffic
0x02 Unprotected 0x02 Unprotected
skipping to change at page 5, line 5 skipping to change at page 4, line 38
0x08 Dedicated 1:1 0x08 Dedicated 1:1
0x10 Dedicated 1+1 0x10 Dedicated 1+1
0x20 Enhanced 0x20 Enhanced
0x40 Reserved 0x40 Reserved
0x80 Reserved 0x80 Reserved
5.5. Interface Switching Capability Descriptor 5.4. Interface Switching Capability Descriptor
The Interface Switching Capability Descriptor is a sub-TLV (of type The Interface Switching Capability Descriptor is a sub-TLV (of type
21) of the extended IS reachability TLV. The length is the length of 21) of the extended IS reachability TLV. The length is the length of
value field in octets. The format of the value field is as shown value field in octets. The format of the value field is as shown
below: below:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Switching Cap | Encoding | Reserved | | Switching Cap | Encoding | Reserved |
skipping to change at page 6, line 19 skipping to change at page 5, line 47
51 Layer-2 Switch Capable (L2SC) 51 Layer-2 Switch Capable (L2SC)
100 Time-Division-Multiplex Capable (TDM) 100 Time-Division-Multiplex Capable (TDM)
150 Lambda-Switch Capable (LSC) 150 Lambda-Switch Capable (LSC)
200 Fiber-Switch Capable (FSC) 200 Fiber-Switch Capable (FSC)
The Encoding field contains one of the values specified in Section The Encoding field contains one of the values specified in Section
3.1.1 of [GMPLS-SIG]. 3.1.1 of [GMPLS-SIG].
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. 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, PSC-4, or When the Switching Capability field is PSC-1, PSC-2, PSC-3, or PSC-4,
L2SC, there is no specific information. the specific information includes Interface MTU and Minimum LSP
Bandwidth. The Interface MTU is encoded as a two octets integer. The
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.
When the Switching Capability field is L2SC, there is no specific
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, which is is encoded in a 4 octets includes Minimum LSP Bandwidth, which is is encoded in a 4 octets
field in the IEEE floating point format. field in the IEEE floating point format. The units are bytes (not
bits!) per second.
When the Switching Capability field is LSC, there is no specific When the Switching Capability field is LSC, there is no specific
information. information.
5.6. 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 an Outgoing
Interface Identifier Interface Identifier
4 octets of IPv4 neighbor address or 4 octets of an Incoming 4 octets of IPv4 neighbor address or 4 octets of an Incoming
Interface Identifier Interface 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.7. Interface Identifier for Unnumbered Interfaces 5.6. Link Identifier for Unnumbered Interfaces
The Interface Identifier TLV is carried as part of the Point-to-point The Link Identifier TLV is carried as part of the Point-to-point ISIS
ISIS Hello PDUs. The Type field of this TLV is TBD. The Length field Hello PDUs. The Type field of this TLV is TBD. The Length field of
of this TLV is set to 4. The Value field of this TLV contains 4 this TLV is set to 4. The Value field of this TLV contains 4 octets
octets that encode the Interface Identifier corresponding to the that encode the Identifier assigned to the link over which this PDU
interface over which this PDU is to be transmitted. is to be transmitted by the LSR that transmits the PDU.
6. Security Considerations 6. 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 7. 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.
 End of changes. 

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