[rfc-dist] RFC 5764 on Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)

[rfc-editor at rfc-editor.org (rfc-editor at rfc-editor.org)]

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

        
        RFC 5764

        Title:      Datagram Transport Layer Security (DTLS) 
                    Extension to Establish Keys for the 
                    Secure Real-time Transport Protocol (SRTP) 
        Author:     D. McGrew, E. Rescorla
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2010
        Mailbox:    mcgrew at cisco.com, 
                    ekr at rtfm.com
        Pages:      26
        Characters: 60590
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avt-dtls-srtp-07.txt

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

This document describes a Datagram Transport Layer Security (DTLS)
extension to establish keys for Secure RTP (SRTP) and Secure RTP
Control Protocol (SRTCP) flows.  DTLS keying happens on the media
path, independent of any out-of-band signalling channel present.
[STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  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/rfcsearch.html.
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