Encryption of Header Extensions in the Secure Real-time Transport Protocol
RFC 6904, “Encryption of Header Extensions in the Secure Real-time Transport Protocol”, is a Proposed Standard document published in April 2013 by J. Lennox. It updates RFC 3711. The canonical text is published by the RFC Editor.
Abstract
The Secure Real-time Transport Protocol (SRTP) provides authentication, but not encryption, of the headers of Real-time Transport Protocol (RTP) packets. However, RTP header extensions may carry sensitive information for which participants in multimedia sessions want confidentiality. This document provides a mechanism, extending the mechanisms of SRTP, to selectively encrypt RTP header extensions in SRTP.
This document updates RFC 3711, the Secure Real-time Transport Protocol specification, to require that all future SRTP encryption transforms specify how RTP header extensions are to be encrypted.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6904 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6903 Additional Link Relation Types
- RFC 6905 Requirements for Operations, Administration, and Maintenance in Transparent Interconnection of Lots of Links
- RFC 6902 JavaScript Object Notation Patch
- RFC 6906 The 'profile' Link Relation Type
- RFC 6901 JavaScript Object Notation Pointer
- RFC 6907 Use Cases and Interpretations of Resource Public Key Infrastructure Objects for Issuers and Relying Parties
- RFC 6908 Deployment Considerations for Dual-Stack Lite
- RFC 6909 IPv4 Traffic Offload Selector Option for Proxy Mobile IPv6