Best Practices for Securing RTP Media Signaled with SIP
RFC 8862
also known as BCP 228
Revision differences
Document history
Date | By | Action |
---|---|---|
2023-12-12
|
(System) | Imported membership of rfc8862 in bcp228 via sync to the rfc-index |
2023-12-12
|
(System) | No history of BCP228 is currently available in the datatracker before this point |
2021-01-18
|
(System) | Received changes through RFC Editor sync (created alias RFC 8862, changed abstract to 'Although the Session Initiation Protocol (SIP) includes a suite of security … Received changes through RFC Editor sync (created alias RFC 8862, changed abstract to 'Although the Session Initiation 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 best practices for negotiating confidential media with SIP, including a comprehensive protection solution that binds the media layer to SIP layer identities.', changed pages to 12, changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2021-01-18, changed IESG state to RFC Published, created alias BCP 228) |
2021-01-18
|
(System) | RFC published |