Network Working Group X. Xu Internet-Draft Huawei Intended status: Standards Track April 24, 2014 Expires: October 26, 2014 Carrying IPv6 Router ID in IS-IS Router Capability TLV draft-xu-isis-ipv6-router-id-00 Abstract This document proposes a new sub-TLV of the IS-IS Router CAPABILITY TLV, called IPv6 Router ID sub-TLV. 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 October 26, 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 Expires October 26, 2014 [Page 1] Internet-Draft April 2014 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 3. IPv6 Router ID Sub-TLV . . . . . . . . . . . . . . . . . . . 2 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 6. Security Considerations . . . . . . . . . . . . . . . . . . . 3 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 7.1. Normative References . . . . . . . . . . . . . . . . . . 3 7.2. Informative References . . . . . . . . . . . . . . . . . 3 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction There are several situations where it is useful for the IS-IS routers in one area to establish the correlations between the IPv6 addresses and the capabilities of the other routers in another area. However, in the IS-IS Router CAPABILITY TLV as defined in [RFC4971], which is appliable for both IPv4 IS-IS [RFC1195] [RFC5305] and IPv6 IS-IS [RFC5308], only a 4-octet router ID is contained. Therefore, this document propose a new sub-TLV of this CAPABILITY TLV to carry an 16-octect router ID. This 16-octect router ID MUST be a routable IPv6 global address of the router originating the CAPABILITY TLV. 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. IPv6 Router ID Sub-TLV A new sub-TLV of the IS-IS Router Capability TLV, called IPv6 Router ID sub-TLV is defined to carry a routable IPv6 global address of the router originating the CAPABILITY TLV. The Type of this sub-TLV is TBD, the Length is set to 16, and the Value field contains an routable IPv6 global address of the router originating the CAPABILITY TLV. The scope of the advertisement depends on the application but it is recommended that it SHOULD be domain-wide. Xu Expires October 26, 2014 [Page 2] Internet-Draft April 2014 4. Acknowledgements TBD. 5. IANA Considerations This memo includes a request to IANA to allocate a sub-TLV type within the IS-IS Router Capability TLV. 6. Security Considerations This document does not introduce any new security risk. 7. References 7.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. 7.2. Informative References [RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and dual environments", RFC 1195, December 1990. [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic Engineering", RFC 5305, October 2008. [RFC5308] Hopps, C., "Routing IPv6 with IS-IS", RFC 5308, October 2008. Author's Address Xiaohu Xu Huawei Email: xuxiaohu@huawei.com Xu Expires October 26, 2014 [Page 3]