| CARVIEW |
Select Language
HTTP/2 200
date: Tue, 05 Aug 2025 18:33:33 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=ZqwBaSxKcZHbOTKKLL94DaT5FfvdC6uDhiVXZUb8zWo-1754418813-1.0.1.1-nbPoGk3B35C1Hjj4Os0x_82RHU9XkmJAB.JLJOCsGnfx7VTcSP8ia4KeoX3okLTnZoHZkjdpeyya9OL3aB1F4fmAa6ZuE2k_NgpPvzwq2Ic; path=/; expires=Tue, 05-Aug-25 19:03:33 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 96a8622bbd4a755c-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 9172 » RFC Editor
Search RFCs
RFC 9172
Bundle Protocol Security (BPSec), January 2022
- File formats:
- Also available: XML file for editing
- Status:
- PROPOSED STANDARD
- Authors:
- E. Birrane, III
K. McKeever - Stream:
- IETF
- Source:
- dtn (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC9172
Discuss this RFC: Send questions or comments to the mailing list dtn@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9172
Abstract
This document defines a security protocol providing data integrity and confidentiality services for the Bundle Protocol (BP).
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