[rfc-dist] RFC 7202 on Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Mon Apr 14 21:58:54 PDT 2014


A new Request for Comments is now available in online RFC libraries.

        
        RFC 7202

        Title:      Securing the RTP Framework: Why 
                    RTP Does Not Mandate a Single 
                    Media Security Solution 
        Author:     C. Perkins, M. Westerlund
        Status:     Informational
        Stream:     IETF
        Date:       April 2014
        Mailbox:    csp at csperkins.org, 
                    magnus.westerlund at ericsson.com
        Pages:      10
        Characters: 23428
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avt-srtp-not-mandatory-16.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7202.txt

This memo discusses the problem of securing real-time multimedia
sessions.  It also explains why the Real-time Transport Protocol
(RTP) and the associated RTP Control Protocol (RTCP) do not mandate a
single media security mechanism.  This is relevant for designers and
reviewers of future RTP extensions to ensure that appropriate
security mechanisms are mandated and that any such mechanisms are
specified in a manner that conforms with the RTP architecture.

This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC




More information about the rfc-dist mailing list