IPv6 Traffic Engineering in IS-IS
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 10
- Abstract
- This document specifies a method for exchanging IPv6 traffic engineering information using the IS-IS routing protocol. This information enables routers in an IS-IS network to calculate traffic-engineered routes using IPv6 addresses. [STANDARDS-TRACK]
- Publication Date
- 2011-02-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC6119- Link
- https://doi.org/10.17487/RFC6119
- Author(s)
- Jon HarrisonJon BergerMike Bartlett
Latest version of IETF RFC 6119
Document Versions — IETF RFC 6119
-
▶ IETF RFC 6119 (2011-02-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- ISO.10589.2002 — 1 EXTERNAL
- IETF RFC 2119 [Active*]
- IETF RFC 4202 [Active*]
- IETF RFC 5304 [Active*]
- IETF RFC 5305 [Active*]
- IETF RFC 5307 [Active*]
- IETF RFC 5308 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC6119.json
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 6119, IPv6 Traffic Engineering in IS-IS. Available at https://doi.org/10.17487/RFC6119
Snippet:
IETF RFC 6119, IPv6 Traffic Engineering in IS-IS. Available at https://doi.org/10.17487/RFC6119
HTML (ISO 690 compliant)
Preview:
IETF RFC 6119, IPv6 Traffic Engineering in IS-IS. Available at https://doi.org/10.17487/RFC6119
Snippet:
<span class="citation"><cite>IETF RFC 6119</cite>, IPv6 Traffic Engineering in IS-IS. Available at <a href="https://doi.org/10.17487/RFC6119" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6119</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 6119, IPv6 Traffic Engineering in IS-IS
doi: 10.17487/RFC6119
url: https://doi.org/10.17487/RFC6119
doi: 10.17487/RFC6119
url: https://doi.org/10.17487/RFC6119
Snippet:
<li> <cite id="bib-rfc6119">IETF RFC 6119</cite>, IPv6 Traffic Engineering in IS-IS <span class="doi">10.17487/RFC6119</span> </li>
Referenced By
- IETF RFC 7439 [Active*]
- IETF RFC 7752 [Superseded*]
- IETF RFC 9522 [Active*]
- IETF RFC 9552 [Active*]