Best Practices for Securing RTP Media Signaled with SIP
draft-peterson-dispatch-rtpsec-00

Document Type Replaced Internet-Draft (individual)
Last updated 2016-09-22 (latest revision 2016-03-21)
Replaced by draft-peterson-sipbrandy-rtpsec
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-peterson-sipbrandy-rtpsec
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-peterson-dispatch-rtpsec-00.txt

Abstract

Although the Session Initital Protocol (SIP) includes a suite of security services that has been expanded by numerous specifications over the years, there is no single place that explains how to use SIP to establish confidential media sessions. Additionally, existing mechanisms have some feature gaps that need to be identified and resolved in order for them to address the pervasive monitoring threat model. This specification describes practices for negotiating confidential media with SIP, including both comprehensive security solutions which bind the media to SIP-layer identities as well as opportunistic security solutions.

Authors

Jon Peterson (jon.peterson@neustar.biz)
Eric Rescorla (ekr@rtfm.com)
Richard Barnes (rbarnes@mozilla.com)
Russ Housley (rhousley@vigilsec.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)