Network Working Group X. Xu Internet-Draft Huawei Intended status: Standards Track U. Chunduri Expires: November 30, 2014 Ericsson May 29, 2014 Carrying Routable IP Addresses in IS-IS Router Capability TLV draft-xu-isis-routable-ip-address-00 Abstract This document proposes two new sub-TLVs of the IS-IS Router CAPABILITY TLV, called Routable IPv4 Address sub-TLV and Routable IPv6 Address sub-TLV respectively. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on November 30, 2014. Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Xu & Chunduri Expires November 30, 2014 [Page 1] Internet-Draft May 2014 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 3. Routable IPv4 Address Sub-TLV . . . . . . . . . . . . . . . . 2 4. Routable IPv6 Address Sub-TLV . . . . . . . . . . . . . . . . 3 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 7. Security Considerations . . . . . . . . . . . . . . . . . . . 3 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 8.1. Normative References . . . . . . . . . . . . . . . . . . 4 8.2. Informative References . . . . . . . . . . . . . . . . . 4 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction There are several situations where it is required for IS-IS routers within one area to find correlations between routable IP addresses and capabilities of IS-IS routers within another area. However, in the IS-IS Router CAPABILITY TLV [RFC4971] which is used by IS-IS routers to announce their capabilities, there is no field for containing routable IP addresses of the originating router. Although TE Router ID sub-TLVs as defined in [RFC5316] are used to carry routable IP addresses, these sub-TLVs are specifically designed for Traffic-Engineering (TE) purpose. Therefore, this document propose two new sub-TLVs of this CAPABILITY TLV for carrying routable IPv4 and IPv6 addresses of the router originating the CAPABILITY TLV respectively. These two sub-TLVs could be used for non-TE purpose. These routable addresses are typically implemented as "loopback addresses". 1.1. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 2. Terminology This memo makes use of the terms defined in [RFC4971]. 3. Routable IPv4 Address Sub-TLV A new sub-TLV of the IS-IS Router Capability TLV, called Routable IPv4 Address sub-TLV is defined to carry one or more routable IPv4 addresses of the router originating the CAPABILITY TLV. The Type of this sub-TLV is TBD, the Length is variable (multiple of 4), and the Xu & Chunduri Expires November 30, 2014 [Page 2] Internet-Draft May 2014 Value field contains one or more routable IPv4 addresses of the router originating the CAPABILITY TLV. This sub-TLV SHOULD NOT be included more than once in an CAPABILITY TLV. The scope of the advertisement depends on the application but it is recommended that it SHOULD be domain-wide. An implementation receiving a Routable IPv4 Address sub-TLV defined in this document MUST NOT consider the routable IPv4 address(es) contained in such sub-TLV in the standard SPF calculation because this can lead to forwarding loops when interacting with systems that do not support this sub-TLV. 4. Routable IPv6 Address Sub-TLV A new sub-TLV of the IS-IS Router Capability TLV, called Routable IPv6 Address sub-TLV is defined to carry one or more routable IPv6 global addresses of the router originating the CAPABILITY TLV. The Type of this sub-TLV is TBD, the Length is variable (multiple of 16), and the Value field contains one or more routable IPv6 global address of the router originating the CAPABILITY TLV. This sub-TLV SHOULD NOT be included more than once in an CAPABILITY TLV. The scope of the advertisement depends on the application but it is recommended that it SHOULD be domain-wide. An implementation receiving a Routable IPv6 Address sub-TLV defined in this document MUST NOT consider the routable IPv6 address(es) contained in such sub-TLV in the standard SPF calculation because this can lead to forwarding loops when interacting with systems that do not support this sub-TLV. 5. Acknowledgements Thanks Karsten Thomann, Anton Smirnov, Joel Jaeggli, Joel Halpern, Les Ginsberg, Wes George and Acee Lindem for their valuable comments on the initial idea of this draft. 6. IANA Considerations This memo includes a request to IANA to allocate two sub-TLV type codes within the IS-IS Router Capability TLV for the Routable IPv4 Address Sub-TLV and the Routable IPv6 Address Sub-TLV respectively. 7. Security Considerations This document does not introduce any new security risk. 8. References Xu & Chunduri Expires November 30, 2014 [Page 3] Internet-Draft May 2014 8.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC4971] Vasseur, JP., Shen, N., and R. Aggarwal, "Intermediate System to Intermediate System (IS-IS) Extensions for Advertising Router Information", RFC 4971, July 2007. 8.2. Informative References [RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and dual environments", RFC 1195, December 1990. [RFC5316] Chen, M., Zhang, R., and X. Duan, "ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering", RFC 5316, December 2008. Authors' Addresses Xiaohu Xu Huawei Email: xuxiaohu@huawei.com Uma Chunduri Ericsson Email: uma.chunduri@ericsson.com Xu & Chunduri Expires November 30, 2014 [Page 4]