RFC 5303: Three-Way Handshake for IS-IS Point-to-Point Adjacencies
In plain English — editorial summary, not part of the RFC
The IS-IS routing protocol (Intermediate System to Intermediate System, ISO 10589) requires reliable protocols at the link layer for point-to-point links. As a result, it does not use a three-way handshake when establishing adjacencies on point-to-point media. This paper defines a backward-compatible extension to the protocol that provides for a three-way handshake. It is fully interoperable with systems that do not support the extension. Additionally, the extension allows the robust operation of more than 256 point-to-point links on a single router. This extension has been implemented by multiple router vendors; this paper is provided to the Internet community in order to allow interoperable implementations to be built by other vendors. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5303
- Published
- October 2008
- Authors
- D. Katz; R. Saluja; D. Eastlake 3rd
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
- Obsoletes:
- RFC 3373
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5304IS-IS Cryptographic AuthenticationUpdated
October 2008
- RFC 5302Domain-Wide Prefix Distribution with Two-Level IS-ISCurrent
October 2008
- RFC 5301Dynamic Hostname Exchange Mechanism for IS-ISUpdated
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 5308Routing IPv6 with IS-ISUpdated
October 2008
- RFC 5089IS-IS Protocol Extensions for Path Computation Element (PCE) DiscoveryUpdated
January 2008
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?