RFC 8703: Dynamic Link Exchange Protocol (DLEP) Link Identifier Extension
In plain English — editorial summary, not part of the RFC
The Dynamic Link Exchange Protocol (DLEP) is a protocol for modems to advertise the status of wireless links between reachable destinations to attached routers. The core specification of the protocol (RFC 8175) assumes that every modem in the radio network has an attached DLEP router and requires that the Media Access Control (MAC) address of the DLEP interface on the attached router be used to identify the destination in the network, for purposes of reporting the state and quality of the link to that destination. This document describes a DLEP extension that allows modems that do not meet the strict requirement above to use DLEP to describe link availability and quality to one or more destinations reachable beyond a device on the Layer 2 domain.
Document record
- Document ID
- RFC8703
- Published
- February 2020
- Authors
- R. Taylor; S. Ratliff
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8651Dynamic Link Exchange Protocol (DLEP) Control-Plane-Based Pause ExtensionCurrent
October 2019
- RFC 8757Dynamic Link Exchange Protocol (DLEP) Latency Range ExtensionCurrent
March 2020
- RFC 8245Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444Current
October 2017
- RFC 8218Multipath Extension for the Optimized Link State Routing Protocol Version 2 (OLSRv2)Current
August 2017
- RFC 8116Security Threats to the Optimized Link State Routing Protocol Version 2 (OLSRv2)Current
May 2017
- RFC 7985Security Threats to Simplified Multicast Forwarding (SMF)Current
November 2016
- RFC 7939Definition of Managed Objects for the Neighborhood Discovery ProtocolCurrent
August 2016
- RFC 7859Identity-Based Signatures for Mobile Ad Hoc Network (MANET) Routing ProtocolsCurrent
May 2016
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?