RFC 8968: Babel Routing Protocol over Datagram Transport Layer Security
In plain English — editorial summary, not part of the RFC
The Babel Routing Protocol does not contain any means to authenticate neighbours or provide integrity or confidentiality for messages sent between them. This document specifies a mechanism to ensure these properties using Datagram Transport Layer Security (DTLS).
Document record
- Document ID
- RFC8968
- Published
- January 2021
- Authors
- A. Décimo; D. Schinazi; J. Chroboczek
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8967MAC Authentication for the Babel Routing ProtocolUpdated
January 2021
- RFC 8966The Babel Routing ProtocolCurrent
January 2021
- RFC 8971Bidirectional Forwarding Detection (BFD) for Virtual eXtensible Local Area Network (VXLAN)Current
December 2020
- RFC 8965Applicability of the Babel Routing ProtocolCurrent
January 2021
- RFC 8964Deterministic Networking (DetNet) Data Plane: MPLSCurrent
January 2021
- RFC 8960A YANG Data Model for MPLS BaseCurrent
December 2020
- RFC 8957Synonymous Flow Label FrameworkCurrent
January 2021
- RFC 8979Subscriber and Performance Policy Identifier Context Headers in the Network Service Header (NSH)Current
February 2021
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?