RFC 5301: Dynamic Hostname Exchange Mechanism for IS-IS
In plain English — editorial summary, not part of the RFC
RFC 2763 defined a simple and dynamic mechanism for routers running IS-IS to learn about symbolic hostnames. RFC 2763 defined a new TLV that allows the IS-IS routers to flood their name-to-systemID mapping information across the IS-IS network. This document obsoletes RFC 2763. This document moves the capability provided by RFC 2763 to the Standards Track. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5301
- Published
- October 2008
- Authors
- D. McPherson; N. Shen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5302Domain-Wide Prefix Distribution with Two-Level IS-ISCurrent
October 2008
- RFC 5308Routing IPv6 with IS-ISUpdated
October 2008
- RFC 5303Three-Way Handshake for IS-IS Point-to-Point AdjacenciesCurrent
October 2008
- RFC 5304IS-IS Cryptographic AuthenticationUpdated
October 2008
- RFC 5305IS-IS Extensions for Traffic EngineeringUpdated
October 2008
- RFC 5306Restart Signaling for IS-ISObsoleted
October 2008
- RFC 5307IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)Updated
October 2008
- RFC 5444Generalized Mobile Ad Hoc Network (MANET) Packet/Message FormatUpdated
February 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?