RFC 8175: Dynamic Link Exchange Protocol (DLEP)
In plain English — editorial summary, not part of the RFC
When routing devices rely on modems to effect communications over wireless links, they need timely and accurate knowledge of the characteristics of the link (speed, state, etc.) in order to make routing decisions. In mobile or other environments where these characteristics change frequently, manual configurations or the inference of state through routing or transport protocols does not allow the router to make the best decisions. This document introduces a new protocol called the Dynamic Link Exchange Protocol (DLEP), which provides a bidirectional, event-driven communication channel between the router and the modem to facilitate communication of changing link characteristics.
Document record
- Document ID
- RFC8175
- Published
- June 2017
- Authors
- S. Ratliff; S. Jury; D. Satterwhite; R. Taylor; B. Berry
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 82
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8177YANG Data Model for Key ChainsCurrent
June 2017
- RFC 8171Transparent Interconnection of Lots of Links (TRILL): Edge Directory Assistance MechanismsCurrent
June 2017
- RFC 8169Residence Time Measurement in MPLS NetworksCurrent
May 2017
- RFC 8181A Publication Protocol for the Resource Public Key Infrastructure (RPKI)Current
July 2017
- RFC 8182The RPKI Repository Delta Protocol (RRDP)Updated
July 2017
- RFC 8183An Out-of-Band Setup Protocol for Resource Public Key Infrastructure (RPKI) Production ServicesCurrent
July 2017
- RFC 8184Dual-Homing Protection for MPLS and the MPLS Transport Profile (MPLS-TP) PseudowiresCurrent
June 2017
- RFC 8185Dual-Homing Coordination for MPLS Transport Profile (MPLS-TP) Pseudowires ProtectionCurrent
June 2017
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?