| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 13:14:02 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=QnB_rx1y4rMKcZe4kGoH85QqqTwKOJQCaZcnWGRCcnc-1760188442-1.0.1.1-3Zp625hLl0V7Wxg9_XKPrLkLfBoTvMVFvrcqqrSuNfhPBX_TgH23PIsSKkpmjJJ_x00bOy7ShyeGSC9StrytnZujcsrZPQuEbK5j3FuJPD0; path=/; expires=Sat, 11-Oct-25 13:44:02 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98ce9e3e19cd5ace-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 8968 » RFC Editor
Search RFCs
RFC 8968
Babel Routing Protocol over Datagram Transport Layer Security, January 2021
- File formats:
- Also available: XML file for editing
- Status:
- PROPOSED STANDARD
- Authors:
- A. Décimo
D. Schinazi
J. Chroboczek - Stream:
- IETF
- Source:
- babel (rtg)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8968
Discuss this RFC: Send questions or comments to the mailing list babel@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8968
Abstract
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).
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us