HTTP/2 302 date: Mon, 14 Jul 2025 00:53:43 GMT content-type: text/html content-length: 143 location: https://get.ietf.org/implementation-report/report-isis-ipv6.txt cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0 expires: Thu, 01 Jan 1970 00:00:01 GMT vary: Accept-Encoding server: cloudflare cf-ray: 95ed0b70de86c1b3-BLR alt-svc: h3=":443"; ma=86400 HTTP/2 200 date: Mon, 14 Jul 2025 00:53:43 GMT content-type: text/plain etag: W/"c305c8c9b28ff43522204fb83d9949b5" vary: Accept-Encoding server: cloudflare cf-ray: 95ed0b710a588839-BLR content-encoding: gzip alt-svc: h3=":443"; ma=86400 Internet Engineering Task Force Christian E. Hopps Cisco Systems 24 January 2006 Routing IPv6 with IS-IS Implementation Report Abstract Routing IPv6 with IS-IS as specified in RFC XXXX extends the IS-IS routing protocol to allow for the exchange of IPv6 routing information. This document provides an implementation report for this extension. 1. Introduction IS-IS [ISO] is an extendible intra-domain routing protocol. Each router in the routing domain issues an LSP (link-state-pdu) that contains information pertaining to that router. An LSP contains typed variable length data often referred to as TLVs (type-length- values). The IS-IS [ISO] protocol has been extended through the use of 2 new TLVs as specified in [ISIS-IPV6] to carry IPv6 routing information. This document satisfies the implementation report requirement from RFC 1264 [REQD]. 2. Implementation Experience Four vendors responded to the survey. The respondents were: Cisco Systems, Juniper Networks, NextHop Technologies and IP Infusion. All four implementations were original. All four vendors tested interoperability with Cisco. All four vendors have shipped the code to customers. IP Infusion and NextHop indicated that they tested leaking of prefixes. The largest known deployments of the protocol extension included 40 and 40-50 routers. No one reported any difficulty in comprehending the standard while implementing or in needing any clarifications. 3. MIB Reference The IS-IS MIB [ISIS-MIB] has been generalized to support both IPv4 and IPv6 addresses through the use of the standard [ADDR-MIB] InetAddressType and InetAddress objects throughout the MIB. In addition the protocols supported type IsisSupportedProtocol includes an new value to indicate support within the router for IPv6. 4. Authentication Requirement Since [ISIS-IPV6] utilizes the TLV mechanism to extend [ISO] it inherits the base protocols authentication methods as described in [ISO] as well as the extended authentication method as documented in [ISIS-HMAC]. 5. Security Considerations This document does not introduce any security concerns. It does make reference to the security mechanisms as provided by the base protocol and documented in [ISO] [ISIS] and the extension documented in [ISIS- HMAC]. 6. Acknowledgments The author wishes to thank the following people who responded to the survey. Donald Adams (IP Infusion). Patrick Grossetete and Scott Sturgess (Cisco Systems). Daniel Gryniewicz (NextHop Technologies). Nischal Sheth (Juniper Networks). 7. Normative References [ISO] "Intermediate System to Intermediate System Intra-Domain Routeing Exchange Protocol for use in Conjunction with the Protocol for Providing the Connectionless-mode Network Service (ISO 8473)", ISO 10589, 1992. [ISIS] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and dual environments", RFC 1195, December 1990. [ISIS-IPV6] Hopps, C., "Routing IPv6 with IS-IS", RFC XXXX, XXXXXXX XXXX. [ADDR-MIB] Daniele, et. al., "Textual Conventions for Internet Network Addresses" RFC 3291, May 2002. [ISIS-MIB] Parker, J., "Management Information Base for IS-IS", draft-ietf- isis-wg-mib-26.txt 8. Informative References [REQD] Hinden, R., "Internet Engineering Task Force Internet Routing Protocol Standardization Criteria", RFC 1264, October 1991. [ISIS-HMAC] Li, T., Atkinson, R., "Intermediate System to Intermediate System (IS-IS) Cryptographic Authentication", RFC 3567, July 2003. 9. Author's Address Christian E. Hopps Cisco Systems 3750 Cisco Way San Jose, CA 95134 U.S.A. Phone: +1 408 525 1684 Email: chopps@cisco.com