draft-ietf-isis-gmpls-extensions-15.txt   draft-ietf-isis-gmpls-extensions-16.txt 
Network Working Group K. Kompella (Editor) Network Working Group K. Kompella (Editor)
Internet Draft Y. Rekhter (Editor) Internet Draft Y. Rekhter (Editor)
Category: Informational Juniper Networks Category: Informational Juniper Networks
Expires: June 2003 December 2002 Expires: June 2003 December 2002
IS-IS Extensions in Support of Generalized MPLS IS-IS Extensions in Support of Generalized MPLS
draft-ietf-isis-gmpls-extensions-15.txt draft-ietf-isis-gmpls-extensions-16.txt
Status of this Memo 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 9 skipping to change at page 3, line 9
1. Specification of Requirements 1. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. Introduction 2. Introduction
This document specifies extensions to the IS-IS routing protocol in This document specifies extensions to the IS-IS routing protocol in
support of carrying link state information for Generalized Multi- support of carrying link state information for Generalized Multi-
Protocol Label Switching (GMPLS). The set of required enhancements Protocol Label Switching (GMPLS). The set of required enhancements to
to IS-IS are outlined in [GMPLS-ROUTING]. IS-IS are outlined in [GMPLS-ROUTING]. Support for unnumbered
interfaces assumes support for the "Point-to-Point Three-Way
Adjacency" IS-IS Option type [ISIS-3way].
3. IS-IS Routing Enhancements 3. 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 Link State Protocol
Data Units.
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 the following sub-TLVs: we add the following sub-TLVs:
Sub-TLV Type Length Name Sub-TLV Type Length Name
4 8 Link Local/Remote Identifiers 4 8 Link Local/Remote Identifiers
20 2 Link Protection Type 20 2 Link Protection Type
21 variable Interface Switching Capability Descriptor 21 variable Interface Switching Capability Descriptor
We further add one new TLV to the TE LSAs. We further add one new TLV to the TE TLVs:
TLV Type Length Name TLV Type Length Name
138 variable Shared Risk Link Group 138 variable Shared Risk Link Group
3.1. Link Local/Remote Identifiers 3.1. Link Local/Remote Identifiers
A Link Local Interface Identifiers is a sub-TLV of the extended IS A Link Local Interface Identifiers is a sub-TLV of the extended IS
reachability TLV. The type of this sub-TLV is 4, and length is eight reachability TLV. The type of this sub-TLV is 4, and length is eight
octets. The value field of this sub-TLV contains four octets of Link octets. The value field of this sub-TLV contains four octets of Link
Local Identifier followed by four octets of Link Remote Idenfier (see Local Identifier followed by four octets of Link Remote Idenfier (see
Section "Support for unnumbered links" of [GMPLS-ROUTING]). If the Section "Support for unnumbered links" of [GMPLS-ROUTING]). If the
Link Remote Identifier is unknown, it is set to 0. Link Remote Identifier is unknown, it is set to 0.
The following illustrates encoding of the Value field of the Link
Local/Remote Identifiers sub-TLV.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Local Identifier | | Link Local Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Remote Identifier | | Link Remote Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Link Local/Remote Identifiers sub-TLV MUST NOT occur more than
once within the extended IS reachability TLV. If the Link
Local/Remote Idenfitiers sub-TLV occurs more than once within the
extended IS reachability TLV, the receiver SHOULD ignore all these
sub-TLVs.
3.2. Link Protection Type 3.2. 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. extended IS reachability TLV, with length two octets.
The following illustrates encoding of the Value field of the Link
Protection Type sub-TLV.
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Protection Cap | Reserved | |Protection Cap | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The first octet is a bit vector describing the protection The first octet is a bit vector describing the protection
capabilities of the link (see Section "Link Protection Type" of capabilities of the link (see Section "Link Protection Type" of
[GMPLS-ROUTING]). They are: [GMPLS-ROUTING]). They are:
skipping to change at page 4, line 35 skipping to change at page 5, line 4
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
The second octet SHOULD be set to zero by the sender, and SHOULD be The second octet SHOULD be set to zero by the sender, and SHOULD be
ignored by the receiver. ignored by the receiver.
The Link Protection Type sub-TLV may occur at most once within the The Link Protection Type sub-TLV MUST NOT occur more than once within
extended IS reachability TLV. the extended IS reachability TLV. If the Link Protection Type sub-TLV
occurs more than once within the extended IS reachability TLV, the
receiver SHOULD ignore all these sub-TLVs.
3.3. Interface Switching Capability Descriptor 3.3. 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 following illustrates encoding of the
below: Value field of the Interface Switching Capability Descriptor sub-TLV.
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max LSP Bandwidth at priority 0 | | Max LSP Bandwidth at priority 0 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max LSP Bandwidth at priority 1 | | Max LSP Bandwidth at priority 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 6, line 15 skipping to change at page 6, line 33
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Minimum LSP Bandwidth | | Minimum LSP Bandwidth |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface MTU | | Interface MTU |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Minimum LSP Bandwidth is is encoded in a 4 octets field in the 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 IEEE floating point format. The units are bytes (not bits!) per
second. The Interface MTU is encoded as a 2 octets integer. second. The Interface MTU is encoded as a 2 octets integer, and
carries the MTU value in the units of bytes.
When the Switching Capability field is L2SC, there is no Switching When the Switching Capability field is L2SC, there is no Switching
Capability specific information field present. Capability specific information field present.
When the Switching Capability field is TDM, the Switching Capability When the Switching Capability field is TDM, the Switching Capability
specific information field includes Minimum LSP Bandwidth and an specific information field includes Minimum LSP Bandwidth and an
indication whether the interface supports Standard or Arbitrary indication whether the interface supports Standard or Arbitrary
SONET/SDH. SONET/SDH.
0 1 2 3 0 1 2 3
skipping to change at page 6, line 46 skipping to change at page 7, line 17
SONET/SDH is encoded as 1 octet. The value of this octet is 0 if the SONET/SDH is encoded as 1 octet. The value of this octet is 0 if the
interface supports Standard SONET/SDH, and 1 if the interface interface supports Standard SONET/SDH, and 1 if the interface
supports Arbitrary SONET/SDH. supports Arbitrary SONET/SDH.
When the Switching Capability field is LSC, there is no Switching When the Switching Capability field is LSC, there is no Switching
Capability specific information field present. Capability specific information field present.
To support interfaces that have more than one Interface Switching To support interfaces that have more than one Interface Switching
Capability Descriptor (see Section "Interface Switching Capability Capability Descriptor (see Section "Interface Switching Capability
Descriptor" of [GMPLS-ROUTING]) the Interface Switching Capability Descriptor" of [GMPLS-ROUTING]) the Interface Switching Capability
Descriptor sub-TLV may occur more than once within the extended IS Descriptor sub-TLV MAY occur more than once within the extended IS
reachability TLV. reachability TLV.
3.4. Shared Risk Link Group TLV 3.4. Shared Risk Link Group TLV
The SRLG TLV (of type 138 TBD) contains a data structure consisting The SRLG TLV (of type 138 TBD) contains a data structure consisting
of: of:
6 octets of System ID 6 octets of System ID
1 octet of Pseudonode Number 1 octet of Pseudonode Number
1 octet Flag 1 octet Flag
4 octets of IPv4 interface address or 4 octets of a Link Local 4 octets of IPv4 interface address or 4 octets of a Link Local
Identifier Identifier
4 octets of IPv4 neighbor address or 4 octets of a Link Remote 4 octets of IPv4 neighbor address or 4 octets of a Link Remote
Identifier Identifier
(variable) list of SRLG values, where each element in the list has 4
octets.
and a list of SRLG values, where each element in the list has 4 The following illustrates encoding of the Value field of the SRLG
octets. The length of this TLV is 16 + 4 * (number of SRLG values). TLV.
The Least Significant Bit of the Flag octet indicates whether the
interface is numbered (set to 1), or unnumbered (set to 0). All
other bits are reserved and should be set to 0.
The neighbor is identified by its System Id (6-octets), plus one
octet to indicate the pseudonode number if the neighbor is on a LAN
interface.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| System ID | | System ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| System ID (cont.) | Pseudonode num| Flags | | System ID (cont.) | Pseudonode num| Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 interface address/Link Local Identifier | | IPv4 interface address/Link Local Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 neighbors address/Link Remote Identifier | | IPv4 neighbors address/Link Remote Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Shared Risk Link Group Value | | Shared Risk Link Group Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ............ | | ............ |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Shared Risk Link Group Value | | Shared Risk Link Group Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The neighbor is identified by its System Id (6-octets), plus one
octet to indicate the pseudonode number if the neighbor is on a LAN
interface.
The Least Significant Bit of the Flag octet indicates whether the
interface is numbered (set to 1), or unnumbered (set to 0). All
other bits are reserved and should be set to 0.
The length of this TLV is 16 + 4 * (number of SRLG values).
This TLV carries the Shared Risk Link Group information (see Section This TLV carries the Shared Risk Link Group information (see Section
"Shared Risk Link Group Information" of [GMPLS-ROUTING]). "Shared Risk Link Group Information" of [GMPLS-ROUTING]).
The SRLG TLV MAY occur more than once within the IS-IS Link State
Protocol Data Units.
3.5. Link Identifier for Unnumbered Interfaces 3.5. Link Identifier for Unnumbered Interfaces
Link Identifiers are exchanged in the Extended Local Circuit ID field Link Identifiers are exchanged in the Extended Local Circuit ID field
of the "Point-to-Point Three-Way Adjacency" IS-IS Option type of the "Point-to-Point Three-Way Adjacency" IS-IS Option type
[ISIS-3way]. [ISIS-3way].
4. Implications on Graceful Restart 4. Implications on Graceful Restart
The restarting node should follow the ISIS restart procedures [ISIS- The restarting node SHOULD follow the ISIS restart procedures [ISIS-
RESTART], and the RSVP-TE restart procedures [GMPLS-RSVP]. RESTART], and the RSVP-TE restart procedures [GMPLS-RSVP].
When the restarting node is going to originate its TE LSAs, these When the restarting node is going to originate its IS-IS Link State
LSAs should be originated with 0 unreserved bandwidth, Traffic Protocol data units for TE links, these Link State Protocol data
Engineering Default metric set to 0xffffff, and if the Link has LSC units SHOULD be originated with 0 unreserved bandwidth, Traffic
Engineering Default metric set to 0xffffff, and if the link has LSC
or FSC as its Switching Capability then also with 0 as Max LSP or FSC as its Switching Capability then also with 0 as Max LSP
Bandwidth, until the node is able to determine the amount of Bandwidth, until the node is able to determine the amount of
unreserved resources taking into account the resources reserved by unreserved resources taking into account the resources reserved by
the already established LSPs that have been preserved across the the already established LSPs that have been preserved across the
restart. Once the restarting node determines the amount of restart. Once the restarting node determines the amount of unreserved
unreserved resources, taking into account the resources reserved by resources, taking into account the resources reserved by the already
the already established LSPs that have been preserved across the established LSPs that have been preserved across the restart, the
restart, the node should advertise these resources in its TE LSAs. node SHOULD advertise these resources in its Link State Protocol data
units.
In addition in the case of a planned restart prior to restarting, the In addition in the case of a planned restart prior to restarting, the
restarting node SHOULD originate the TE LSAs with 0 as unreserved restarting node SHOULD originate the IS-IS Link State Protocol data
bandwidth, and if the Link has LSC or FSC as its Switching Capability units for TE links with 0 as unreserved bandwidth, and if the link
then also with 0 as Max LSP Bandwidth. This would discourage new LSP has LSC or FSC as its Switching Capability then also with 0 as Max
establishment through the restarting router. LSP Bandwidth. This would discourage new LSP establishment through
the restarting router.
Neighbors of the restarting node should continue advertise the actual Neighbors of the restarting node SHOULD continue advertise the actual
unreserved bandwidth on the TE links from the neighbors to that node. 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.
5. Normative References 5. Normative References
[GMPLS-ROUTING] Kompella, K., and Rekhter, Y. (Editors), "Routing [GMPLS-ROUTING] Kompella, K., and Rekhter, Y. (Editors), "Routing
Extensions in Support of Generalized MPLS", (work in progress) Extensions in Support of Generalized MPLS", (work in progress)
[GMPLS-RSVP] Berger, L. (Editors), "Generalized MPLS Signaling - [GMPLS-RSVP] Berger, L. (Editors), "Generalized MPLS Signaling -
RSVP-TE Extensions", (work in progress) RSVP-TE Extensions", (work in progress)
[GMPLS-SIG] Berger, L. (Editor), "Generalized MPLS - Signaling [GMPLS-SIG] Berger, L. (Editor), "Generalized MPLS - Signaling
 End of changes. 

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