RFC 5642: Dynamic Hostname Exchange Mechanism for OSPF
In plain English — editorial summary, not part of the RFC
This document defines a new OSPF Router Information (RI) TLV that allows OSPF routers to flood their hostname-to-Router-ID mapping information across an OSPF network to provide a simple and dynamic mechanism for routers running OSPF to learn about symbolic hostnames, just like for routers running IS-IS. This mechanism is applicable to both OSPFv2 and OSPFv3. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5642
- Published
- August 2009
- Authors
- S. Venkata; S. Harwani; C. Pignataro; D. McPherson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4970Extensions to OSPF for Advertising Optional Router CapabilitiesObsoleted
July 2007
- RFC 7770Extensions to OSPF for Advertising Optional Router CapabilitiesCurrent
February 2016
- RFC 5643Management Information Base for OSPFv3Current
August 2009
- RFC 5613OSPF Link-Local SignalingCurrent
August 2009
- RFC 5709OSPFv2 HMAC-SHA Cryptographic AuthenticationUpdated
October 2009
- RFC 5523OSPFv3-Based Layer 1 VPN Auto-DiscoveryCurrent
April 2009
- RFC 5820Extensions to OSPF to Support Mobile Ad Hoc NetworkingUpdated
March 2010
- RFC 5449OSPF Multipoint Relay (MPR) Extension for Ad Hoc NetworksCurrent
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?