RFC 8510: OSPF Link-Local Signaling (LLS) Extensions for Local Interface ID Advertisement
In plain English — editorial summary, not part of the RFC
Every OSPF interface is assigned an Interface ID that uniquely identifies the interface on the router. In some cases, it is useful to know the assigned Interface ID on the remote side of the adjacency (Remote Interface ID). This document describes the extensions to OSPF link-local signaling (LLS) to advertise the Local Interface ID.
Document record
- Document ID
- RFC8510
- Published
- January 2019
- Authors
- P. Psenak; K. Talaulikar; W. Henderickx; P. Pillay-Esnault
- 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 8379OSPF Graceful Link ShutdownCurrent
May 2018
- RFC 8665OSPF Extensions for Segment RoutingCurrent
December 2019
- RFC 8666OSPFv3 Extensions for Segment RoutingCurrent
December 2019
- RFC 8099OSPF Topology-Transparent ZoneCurrent
February 2017
- RFC 9339OSPF Reverse MetricCurrent
December 2022
- RFC 9355OSPF Bidirectional Forwarding Detection (BFD) Strict-ModeCurrent
February 2023
- RFC 4972Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh MembershipCurrent
July 2007
- RFC 8518Selection of Loop-Free Alternates for Multi-Homed PrefixesCurrent
March 2019
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?