draft-ietf-isis-link-attr-00.txt   draft-ietf-isis-link-attr-01.txt 
ISIS WG ISIS WG
Internet Draft JP Vasseur Internet Draft Jean-Philippe Vasseur
Stefano Previdi Stefano Previdi
Cisco Systems Cisco Systems
Document: draft-ietf-isis-link-attr-00.txt Proposed Status : Standard
Expires: July 2005 January 2004 Expires: November 2005 May 2005
Definition of an IS-IS Link Attribute sub-TLV Definition of an IS-IS Link Attribute sub-TLV
draft-ietf-isis-link-attr-00.txt draft-ietf-isis-link-attr-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or IPR claims of which I am aware have been disclosed, and any applicable patent or other IPR claims of which he or she is aware
of which I become aware will be disclosed, in accordance with RFC have been or will be disclosed, and any of which he or she becomes
3668. aware will be disclosed, in accordance with Section 6 of BCP 79.
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [i].
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
other groups may also distribute working documents as Internet- groups may also distribute working documents as Internet-Drafts.
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This document defines a sub-TLV called ˘Link-attributes÷ carried This document defines a sub-TLV called "Link-attributes" carried
within the TLV 22 and used to flood some link characteristics. within the TLV 22 and used to flood some link characteristics.
Conventions used in this document Conventions used in this document
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 [ii]. document are to be interpreted as described in RFC-2119 [i].
Table of contents Table of contents
1. Introduction................................................. 2 1. Introduction...................................................2
2. Link-attributes sub-TLV format............................... 2 2. Link-attributes sub-TLV format.................................2
3. Interoperability with routers non supporting this capability. 3 3. Interoperability with routers non supporting this capability...3
4. Security considerations...................................... 3 4. Security considerations........................................3
5. Intellectual Property Considerations......................... 3 5. IANA considerations............................................3
6. Acknowledgments.............................................. 4 6. Intellectual Property Considerations...........................3
7. Intellectual property considerations......................... 4 7. Acknowledgments................................................4
8. References................................................... 5 8. References.....................................................4
Normative references............................................ 5 8.1 Normative references.......................................4
Informative references.......................................... 5 8.2 Informative references.....................................4
9. Author's Addresses........................................... 5 9. Authors' Addresses.............................................5
Full Copyright Statement........................................ 5 Full Copyright Statement..........................................5
1. Introduction 1. Introduction
[IS-IS] specifies the IS-IS protocol (ISO 10589) with extensions to [IS-IS] specifies the IS-IS protocol (ISO 10589) with extensions to
support IPv4 in [IS-IS-IP]. A router advertises one or several Link support IPv4 in [IS-IS-IP]. A router advertises one or several Link
State Protocol data units which are composed of variable length State Protocol data units which are composed of variable length
tuples called TLVs (Type-Length-Value). tuples called TLVs (Type-Length-Value).
[IS-IS-TE] defines a set of new TLVs whose aims are to add more [IS-IS-TE] defines a set of new TLVs whose aims are to add more
information about links characteristics, increase the range of IS-IS information about links characteristics, increase the range of IS-IS
metrics and optimize the encoding of IS-IS prefixes. metrics and optimize the encoding of IS-IS prefixes.
This document defines a new sub-TLV named ˘Link-attributes÷ carried This document defines a new sub-TLV named "Link-attributes" carried
within the extended IS reachability TLV (type 22) specified in [IS- within the extended IS reachability TLV (type 22) specified in [IS-
IS-TE]. IS-TE].
2. Link-attributes sub-TLV format 2. Link-attributes sub-TLV format
The link-attribute sub-TLV is carried within the TLV 22 and has a The link-attribute sub-TLV is carried within the TLV 22 and has a
format identical to the sub-TLV format used by the Traffic format identical to the sub-TLV format used by the Traffic
Engineering Extensions for IS-IS [IS-IS-TE]: 1 octet of sub-type, 1 Engineering Extensions for IS-IS [IS-IS-TE]: 1 octet of sub-type, 1
octet of length of the value field of the sub-TLV followed by the octet of length of the value field of the sub-TLV followed by the
value field ű in this case, a 16 bit flags field. value field in this case, a 16 bit flags field.
The Link-attribute sub-type is 19 (to be assigned by IANA) and has a The Link-attribute sub-type is 19 (to be assigned by IANA) and has a
length of 2 octets. length of 2 octets.
This sub-TLV is OPTIONAL and MAY appear at most once for a single IS This sub-TLV is OPTIONAL and MAY appear at most once for a single IS
neighbor. neighbor.
The following bits are defined (values to be confirmed by IANA): The following bits are defined:
Local Protection Available (0x01). When set, this indicates that the Local Protection Available (0x01). When set, this indicates that the
link is protected by means of some local protection mechanism (e.g link is protected by means of some local protection mechanism (e.g
[FRR]). [FRR]).
Link excluded from local protection path (0x02). When set, this link Link excluded from local protection path (0x02). When set, this link
SHOULD not be included in any computation of a repair path by any SHOULD not be included in any computation of a repair path by any
other router in the routing area. The triggers for setting up this other router in the routing area. The triggers for setting up this
bit are out of the scope of this document. bit are out of the scope of this document.
skipping to change at page 3, line 42 skipping to change at page 3, line 40
Where the information in the link attributes sub-TLV is used to Where the information in the link attributes sub-TLV is used to
affect the IS-IS SPF calculation, additional information indicating affect the IS-IS SPF calculation, additional information indicating
which routers are using this information is required to insure such which routers are using this information is required to insure such
usage does not result in loops or black holes. How this additional usage does not result in loops or black holes. How this additional
information is conveyed is outside the scope of this document. information is conveyed is outside the scope of this document.
4. Security considerations 4. Security considerations
No new security issues are raised in this document. No new security issues are raised in this document.
5. Intellectual Property Considerations 5. IANA considerations
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
The IETF has been notified of intellectual property rights claimed in
regard to some or all of the specification contained in this
document. For more information consult the online list of claimed
rights.
6. Acknowledgments
The authors would like to thank Mike Shand and Les Ginsberg for their IANA will assign a new codepoint for the link-attribute sub-TLV
useful comments. defined in this document and carried within TLV 22. Suggested value
is 19 (to be assigned by IANA).
7. Intellectual property considerations 6. Intellectual Property Considerations
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 5, line 5 skipping to change at page 4, line 20
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
7. Acknowledgments
The authors would like to thank Mike Shand and Les Ginsberg for their
useful comments.
8. References 8. References
Normative references 8.1 Normative references
[RFC] Bradner, S., "Key words for use in RFCs to Indicate Requirement [RFC] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels," RFC 2119. Levels," RFC 2119.
[IS-IS] "Intermediate System to Intermediate System Intra-Domain [IS-IS] "Intermediate System to Intermediate System Intra-Domain
Routeing Exchange Protocol for use in Conjunction with the Protocol Routeing Exchange Protocol for use in Conjunction with the Protocol
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., RFC 1195, "Use of OSI IS-IS for routing in [IS-IS-IP] Callon, R., RFC 1195, "Use of OSI IS-IS for routing in
TCP/IP and dual environments", RFC 1195, December 1990. TCP/IP and dual environments", RFC 1195, December 1990.
[IS-IS-TE] H. Smit, T. Li, ˘IS-IS extensions for traffic [IS-IS-TE] H. Smit, T. Li, "IS-IS extensions for traffic
engineering÷, RFC 3784. engineering", RFC 3784.
Informative references 8.2 Informative references
[FRR] Ping Pan, et al, "Fast Reroute Extensions to RSVP-TE for LSP [FRR] Ping Pan, et al, "Fast Reroute Extensions to RSVP-TE for LSP
Tunnels", draft-ietf-mpls-rsvp-lsp-fastreroute-07.txt. Work in Tunnels", draft-ietf-mpls-rsvp-lsp-fastreroute-07.txt. Work in
progress. progress.
[GR-SHUT], Z. Ali et al, ˘Graceful Shutdown in MPLS Traffic [GR-SHUT], Z. Ali et al, "Graceful Shutdown in MPLS Traffic
Engineering Networks÷, draft-ali-ccamp-mpls-graceful-shutdown-00.txt. Engineering Networks", draft-ali-ccamp-mpls-graceful-shutdown-01.txt.
Work in progress. Work in progress.
9. Author's Addresses 9. Authors' Addresses
Jean-Philippe Vasseur Jean-Philippe Vasseur
CISCO Systems, Inc. CISCO Systems, Inc.
300 Beaver Brook 300 Beaver Brook
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.
 End of changes. 

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