draft-ietf-isis-caps-03.txt   draft-ietf-isis-caps-04.txt 
ISIS WG 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: November 2005 May 2005 Expires: May 2006 November 2005
IS-IS extensions for advertising router information IS-IS extensions for advertising router information
draft-ietf-isis-caps-03.txt draft-ietf-isis-caps-04.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 ?
1. Introduction...................................................2 1. Introduction...................................................2
2. IS-IS Router CAPABILITY TLV....................................3 2. IS-IS Router CAPABILITY TLV....................................3
3. Element of procedure...........................................3 3. Element of procedure...........................................3
4. Interoperability with routers not supporting the capability TLV.5 4. Interoperability with routers not supporting the capability TLV.5
5. Security considerations........................................5 5. Security considerations........................................5
6. Acknowledgment.................................................6 6. Acknowledgment.................................................6
7. Intellectual Property Considerations...........................6 7. Intellectual Property Considerations...........................6
8. References.....................................................6 8. References.....................................................6
Normative references..............................................6 Normative references..............................................6
Informative references............................................7 Informative references............................................6
9. Author's Addresses.............................................7 9. Author's Addresses.............................................7
1. Introduction 1. Introduction
There are several situations where it is useful for the IS-IS There are several situations where it is useful for the IS-IS
routers to learn the capabilities of the other routers of their IS- routers to learn the capabilities of the other routers of their IS-
IS level, area or routing domain. For the sake of illustration, two IS level, area or routing domain. For the sake of illustration, two
examples related to MPLS Traffic Engineering are described here: examples related to MPLS Traffic Engineering are described here:
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
skipping to change at page 4, line 11 skipping to change at page 4, line 11
A router which generates a capability TLV MUST also generate a A router which generates a capability TLV MUST also generate a
Traffic Engineering Router ID TLV (134) at each level for which it Traffic Engineering Router ID TLV (134) at each level for which it
generates a router capability TLV. generates a router capability TLV.
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
MUST 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
sub-TLV(s) relative to C1. This Router CAPABILITY TLV MUST NOT be sub-TLV(s) relative to C1. This Router CAPABILITY TLV will not be
leaked into another level. leaked into another level.
- One Router CAPABILITY TLV with the S flag set, carrying the sub- - One Router CAPABILITY TLV with the S flag set, carrying the sub-
TLV(s) relative to C2. This Router CAPABILITY TLV MUST be leaked TLV(s) relative to C2. This Router CAPABILITY TLV will be leaked
into other IS-IS levels. When the TLV is leaked from level-2 to into other IS-IS levels. When the TLV is leaked from level-2 to
level-1, the D bit MUST be set in the level-1 LSP advertisement. level-1, the D bit will be set in the level-1 LSP advertisement.
When leaking Capability TLVs downward from Level-2 into Level-1, if
the originator of the TLV is a Level-1 router in another area, it is
possible that multiple copies of the same TLV may be received from
multiple L2 routers in the originating area. To prevent a router from
leaking multiple copies of the same TLV, the router performing the
downward leaking MUST check for such duplication by comparing the
contents of the TLVs.
In order to prevent the use of stale capabilities information A In order to prevent the use of stale capabilities information A
system MUST NOT use a Capability TLV present in an LSP of a system system MUST NOT use a Capability TLV present in an LSP of a system
which is not currently reachable via Level-x paths, where "x" is the which is not currently reachable via Level-x paths, where "x" is the
level (1 or 2) in which the sending system advertised the TLV. This level (1 or 2) in which the sending system advertised the TLV. This
requirement applies regardless of whether the sending system is the requirement applies regardless of whether the sending system is the
originator of the Capabilities TLV or not. Note that leaking a originator of the Capabilities TLV or not. Note that leaking a
Capabilities TLV is one of the uses which is prohibited under these Capabilities TLV is one of the uses which is prohibited under these
conditions. conditions.
skipping to change at page 7, line 12 skipping to change at page 7, line 4
for Providing the Connectionless-mode Network Service (ISO 8473)", for Providing the Connectionless-mode Network Service (ISO 8473)",
ISO 10589. ISO 10589.
[IS-IS-IP] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and [IS-IS-IP] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and
dual environments", RFC 1195, December 1990. dual environments", RFC 1195, December 1990.
[ISIS-TE] Li, T., Smit, H., "IS-IS extensions for Traffic [ISIS-TE] Li, T., Smit, H., "IS-IS extensions for Traffic
Engineering", RFC 3784, June 2004. Engineering", RFC 3784, June 2004.
9.2 Informative references 9.2 Informative references
[AUTOMESH] JP Vasseur, JL. Le Roux et al, "Routing extensions for [AUTOMESH] JP Vasseur, JL. Le Roux et al, "Routing extensions for
discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic
Engineering (TE) mesh membership", draft-vasseur-ccamp-automesh- Engineering (TE) mesh membership", draft-ietf-ccamp-automesh, work in
00.txt, Work in progress. progress.
[TE-NODE-CAP] JP Vasseur, JL. Le Roux et al, "Routing extensions for [TE-NODE-CAP] JP Vasseur, JL. Le Roux et al, "Routing extensions for
discovery of Traffic Engineering Node Capabilities", draft-vasseur- discovery of Traffic Engineering Node Capabilities", draft-ietf-
ccamp-te-node-cap-00.txt, Work in progress. ccamp-te-node-cap, work in progress.
[P2MP] R. Aggarwal,D. Papadimitriou,S. Yasukawa, et. al. "Extensions [P2MP] R. Aggarwal,D. Papadimitriou,S. Yasukawa, et. al. "Extensions
to RSVP-TE for Point To Multipoint TE LSPs", draft-ietf-mpls-rsvp-te- to RSVP-TE for Point To Multipoint TE LSPs", draft-ietf-mpls-rsvp-te-
p2mp-01.txt, work in progress. p2mp, work in progress.
[P2MP-REQS] S. Yasukawa et al. "Requirements for point to multipoint [P2MP-REQS] S. Yasukawa et al. "Requirements for point to multipoint
extension to RSVP", draft-ietf-mpls-p2mp-sig-requirement-01.txt, work extension to RSVP", draft-ietf-mpls-p2mp-sig-requirement, work in
in progress. progress.
10. Authors' Addresses 10. Authors' Addresses
Jean-Philippe Vasseur Jean-Philippe Vasseur
CISCO Systems, Inc. CISCO Systems, Inc.
300 Beaver Brook 1414 Massachusetts Avenue
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
Email: jpv@cisco.com Email: jpv@cisco.com
Stefano Previdi Stefano Previdi
CISCO Systems, Inc. CISCO Systems, Inc.
Via Del Serafico 200 Via Del Serafico 200
00142 - Roma 00142 - Roma
ITALY ITALY
Email: sprevidi@cisco.com Email: sprevidi@cisco.com
 End of changes. 14 change blocks. 
25 lines changed or deleted 16 lines changed or added

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