[rfc-dist] RFC 4572 on Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)

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

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

        
        RFC 4572

        Title:      Connection-Oriented Media Transport over the 
                    Transport Layer Security (TLS) Protocol in 
                    the Session Description Protocol (SDP) 
        Author:     J. Lennox
        Status:     Standards Track
        Date:       July 2006
        Mailbox:    lennox at cs.columbia.edu
        Pages:      17
        Characters: 38658
        Updates:    RFC4145
        See-Also:   

        I-D Tag:    draft-ietf-mmusic-comedia-tls-06.txt

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

This document specifies how to establish secure connection-oriented
media transport sessions over the Transport Layer Security (TLS)
protocol using the Session Description Protocol (SDP).  It defines a
new SDP protocol identifier, 'TCP/TLS'.  It also defines the syntax
and semantics for an SDP 'fingerprint' attribute that identifies the
certificate that will be presented for the TLS session.  This
mechanism allows media transport over TLS connections to be
established securely, so long as the integrity of session
descriptions is assured.

This document extends and updates RFC 4145.  [STANDARDS TRACK]

This document is a product of the Multiparty Multimedia Session Control
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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...