CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 02:53:22 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=eeoETnQAvZyOGxPnG3ReZOM06lPo4o77AutsMYO2Rvw-1759978402-1.0.1.1-7fUUjXaSl8F5VINqoA7ZW77TrmGuac8q1oFxzHqbuBZjP7oukLYHsu5ehpRPY0nfdpRswrFvi48K8f6._2McrW07yA5pOiHPGheNFXDX61g; path=/; expires=Thu, 09-Oct-25 03:23:22 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98ba96432d4958e1-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 6119 » RFC Editor
Search RFCs
RFC 6119
IPv6 Traffic Engineering in IS-IS, February 2011
- File formats:
- Status:
- PROPOSED STANDARD
- Authors:
- J. Harrison
J. Berger
M. Bartlett - Stream:
- IETF
- Source:
- isis (rtg)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6119
Discuss this RFC: Send questions or comments to the mailing list lsr@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6119
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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us