Routing IPv6 with IS-IS
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 7
- Abstract
- This document specifies a method for exchanging IPv6 routing information using the IS-IS routing protocol. The described method utilizes two new TLVs: a reachability TLV and an interface address TLV to distribute the necessary IPv6 information throughout a routing domain. Using this method, one can route IPv6 along with IPv4 and OSI using a single intra-domain routing protocol. [STANDARDS-TRACK]
- Publication Date
- 2008-10-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC5308- Link
- https://doi.org/10.17487/RFC5308
- Author(s)
- Christian Hopps
- Keyword(s)
- IS-IS, TLV, OSI
Latest version of IETF RFC 5308
Document Versions — IETF RFC 5308
-
▶ IETF RFC 5308 (2008-10-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- ISO.10589.2002 — 1 EXTERNAL
- IETF RFC 1195 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 5226 [Superseded*]
- IETF RFC 5304 [Active*]
- IETF RFC 5305 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5308.json
Amended by:
RFC7775 NOT IN REGISTRY
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5308, Routing IPv6 with IS-IS. Available at https://doi.org/10.17487/RFC5308
Snippet:
IETF RFC 5308, Routing IPv6 with IS-IS. Available at https://doi.org/10.17487/RFC5308
HTML (ISO 690 compliant)
Preview:
IETF RFC 5308, Routing IPv6 with IS-IS. Available at https://doi.org/10.17487/RFC5308
Snippet:
<span class="citation"><cite>IETF RFC 5308</cite>, Routing IPv6 with IS-IS. Available at <a href="https://doi.org/10.17487/RFC5308" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5308</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc5308">IETF RFC 5308</cite>, Routing IPv6 with IS-IS <span class="doi">10.17487/RFC5308</span> </li>
Referenced By
- IETF RFC 5309 [Active*]
- IETF RFC 6107 [Active*]
- IETF RFC 6119 [Active*]
- IETF RFC 6272 [Active*]