RFC 2763: Dynamic Hostname Exchange Mechanism for IS-IS
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5301.
Current version: RFC 5301 — Dynamic Hostname Exchange Mechanism for IS-IS
In plain English — editorial summary, not part of the RFC
This document defines a new TLV which allows the IS-IS routers to flood their name to system ID mapping information across the IS-IS network. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2763
- Published
- February 2000
- Authors
- N. Shen; H. Smit
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 5
- Also known as
- —
- Obsoleted by:
- RFC 5301
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 2966Domain-wide Prefix Distribution with Two-Level IS-ISObsoleted
October 2000
- RFC 2973IS-IS Mesh GroupsCurrent
October 2000
- RFC 2270Using a Dedicated AS for Sites Homed to a Single ProviderCurrent
January 1998
- RFC 2178OSPF Version 2Obsoleted
July 1997
- RFC 1966BGP Route Reflection An alternative to full mesh IBGPObsoleted
June 1996
- RFC 1665Definitions of Managed Objects for SNA NAUs using SMIv2Obsoleted
July 1994
- RFC 1364BGP OSPF InteractionObsoleted
September 1992
- RFC 4456BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)Updated
April 2006
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?