RFC 8967: MAC Authentication for the Babel Routing Protocol
In plain English — editorial summary, not part of the RFC
This document describes a cryptographic authentication mechanism for the Babel routing protocol that has provisions for replay avoidance. This document obsoletes RFC 7298.
Document record
- Document ID
- RFC8967
- Published
- January 2021
- Authors
- C. Dô; W. Kolodziejak; J. Chroboczek
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 17
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8965Applicability of the Babel Routing ProtocolCurrent
January 2021
- RFC 8253PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)Updated
October 2017
- RFC 9692RIFT: Routing in Fat TreesCurrent
April 2025
- RFC 9985Optimizing Bidirectional Forwarding Detection (BFD) AuthenticationCurrent
June 2026
- RFC 7185Link Metrics for the Mobile Ad Hoc Network (MANET) Routing Protocol OLSRv2 - RationaleCurrent
April 2014
- RFC 6952Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design GuideCurrent
May 2013
- RFC 6552Objective Function Zero for the Routing Protocol for Low-Power and Lossy Networks (RPL)Current
March 2012
- RFC 6550RPL: IPv6 Routing Protocol for Low-Power and Lossy NetworksUpdated
March 2012
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?