Dynamic Hostname Exchange Mechanism for IS-IS
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 5
- Abstract
- 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.
- Publication Date
- 2000-02-01
- Status Note
- Informational
- DOI
10.17487/RFC2763- Link
- https://doi.org/10.17487/RFC2763
- Author(s)
- Naiming ShenHenk Smit
- Keyword(s)
- Routers, TLV
Latest version of IETF RFC 2763
Document Versions — IETF RFC 2763
-
▶ IETF RFC 2763 (2000-02-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Bibliographic Reference(s)
- ISO.10589.1992 — 1 EXTERNAL
- Li, T., "IS-IS HMAC-MD5 Authentication" , Work in Progress. EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC2763.json
Superseded by:
IETF RFC 5301 [Active*]
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 2763, Dynamic Hostname Exchange Mechanism for IS-IS. Available at https://doi.org/10.17487/RFC2763
Snippet:
IETF RFC 2763, Dynamic Hostname Exchange Mechanism for IS-IS. Available at https://doi.org/10.17487/RFC2763
HTML (ISO 690 compliant)
Preview:
IETF RFC 2763, Dynamic Hostname Exchange Mechanism for IS-IS. Available at https://doi.org/10.17487/RFC2763
Snippet:
<span class="citation"><cite>IETF RFC 2763</cite>, Dynamic Hostname Exchange Mechanism for IS-IS. Available at <a href="https://doi.org/10.17487/RFC2763" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2763</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 2763, Dynamic Hostname Exchange Mechanism for IS-IS
doi: 10.17487/RFC2763
url: https://doi.org/10.17487/RFC2763
doi: 10.17487/RFC2763
url: https://doi.org/10.17487/RFC2763
Snippet:
<li> <cite id="bib-rfc2763">IETF RFC 2763</cite>, Dynamic Hostname Exchange Mechanism for IS-IS <span class="doi">10.17487/RFC2763</span> </li>
Referenced By
- IETF RFC 5301 [Active*]
- IETF RFC 5642 [Active*]