draft-ietf-isis-caps-04.txt   draft-ietf-isis-caps-05.txt 
Network Working Group Network Working Group
Internet Draft Jean-Philippe Vasseur(Ed) Internet Draft Jean-Philippe Vasseur(Ed)
Naiming Shen (Ed) Naiming Shen (Ed)
Cisco Systems, Inc. Cisco Systems, Inc.
Rahul Aggarwal(Ed) Rahul Aggarwal(Ed)
Juniper Networks Juniper Networks
Proposed status: Standard Proposed status: Standard
Expires: May 2006 November 2005 Expires: June 2006 December 2005
IS-IS extensions for advertising router information IS-IS Extensions for Advertising Router Information
draft-ietf-isis-caps-04.txt draft-ietf-isis-caps-05.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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 other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 2, line ? skipping to change at page 2, line 35
1. Mesh-group: the setting up of a mesh of TE LSPs requires some 1. Mesh-group: the setting up of a mesh of TE LSPs requires some
significant configuration effort. [AUTOMESH] proposes an auto- significant configuration effort. [AUTOMESH] proposes an auto-
discovery mechanism whereby every LSR of a mesh advertises its discovery mechanism whereby every LSR of a mesh advertises its
mesh-group membership by means of IS-IS extensions. mesh-group membership by means of IS-IS extensions.
2. Point to Multi-point TE LSP (P2MP LSP). A specific sub-TLV ([TE- 2. Point to Multi-point TE LSP (P2MP LSP). A specific sub-TLV ([TE-
NODE-CAP]) allows an LSR to advertise its Point To Multipoint NODE-CAP]) allows an LSR to advertise its Point To Multipoint
capabilities ([P2MP] and [P2MP-REQS]). capabilities ([P2MP] and [P2MP-REQS]).
3. Inter-area traffic engineering: Advertisement of the IPv4
and/or the IPv6 Traffic Engineering Router IDs.
The use of IS-IS for Path Computation Element (PCE) discovery may The use of IS-IS for Path Computation Element (PCE) discovery may
also be considered and will be discussed in the PCE WG. also be considered and will be discussed in the PCE WG.
The capabilities mentioned above require the specification of new The capabilities mentioned above require the specification of new
sub-TLVs carried within the CAPABILITY TLV defined in this document. sub-TLVs carried within the CAPABILITY TLV defined in this document.
Note that the examples above are provided for the sake of Note that the examples above are provided for the sake of
illustration. This document proposes a generic capability advertising illustration. This document proposes a generic capability advertising
mechanism not limited to MPLS Traffic Engineering. mechanism not limited to MPLS Traffic Engineering.
skipping to change at page 3, line 50 skipping to change at page 3, line 50
The Router CAPABILITY TLV is OPTIONAL. As specified in section 3, The Router CAPABILITY TLV is OPTIONAL. As specified in section 3,
more than one Router CAPABILITY TLVs from the same source MAY be more than one Router CAPABILITY TLVs from the same source MAY be
present. present.
This document does not specify how an application may use the Router This document does not specify how an application may use the Router
Capability TLV and such specification is outside the scope of this Capability TLV and such specification is outside the scope of this
document. document.
3. Elements of procedure 3. Elements of procedure
A router which generates a capability TLV MUST also generate a A router which generates a CAPABILITY TLV MUST have a Router ID
Traffic Engineering Router ID TLV (134) at each level for which it which is a 32 bit number. The ID MUST be unique within the IS-IS
generates a router capability TLV. area. If the router generates any capability TLVs with domain
flooding scope then the ID MUST also be unique within the IS-IS
routing domain.
When advertising capabilities with different flooding scopes, a When advertising capabilities with different flooding scopes, a
router MUST originate a minimum of two Router CAPABILITY TLVs, each router MUST originate a minimum of two Router CAPABILITY TLVs, each
TLV carrying the set of sub-TLVs with the same flooding scope. For TLV carrying the set of sub-TLVs with the same flooding scope. For
instance, if a router advertises two sets of capabilities C1 and C2 instance, if a router advertises two sets of capabilities C1 and C2
with an area/level scope and routing domain scope respectively, C1 with an area/level scope and routing domain scope respectively, C1
and C2 being specified by their respective sub-TLV(s), the router and C2 being specified by their respective sub-TLV(s), the router
will originate two Router CAPABILITY TLVs: will originate two Router CAPABILITY TLVs:
- One Router CAPABILITY TLV with the S flag cleared, carrying the - One Router CAPABILITY TLV with the S flag cleared, carrying the
 End of changes. 5 change blocks. 
6 lines changed or deleted 11 lines changed or added

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