[rfc-dist] RFC 4567 on Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)
rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Wed, 19 July 2006 18:01 UTC
From: "rfc-editor at rfc-editor.org"
Date: Wed, 19 Jul 2006 11:01:52 -0700
Subject: [rfc-dist] RFC 4567 on Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)
Message-ID: <200607191801.k6JI1qH0029310@nit.isi.edu>
A new Request for Comments is now available in online RFC libraries. RFC 4567 Title: Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP) Author: J. Arkko, F. Lindholm, M. Naslund, K. Norrman, E. Carrara Status: Standards Track Date: July 2006 Mailbox: jari.arkko at ericsson.com, fredrik.lindholm at ericsson.com, mats.naslund at ericsson.com, karl.norrman at ericsson.com, carrara at kth.se Pages: 30 Characters: 67693 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mmusic-kmgmt-ext-15.txt URL: http://www.rfc-editor.org/rfc/rfc4567.txt This document defines general extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP) to carry messages, as specified by a key management protocol, in order to secure the media. These extensions are presented as a framework, to be used by one or more key management protocols. As such, their use is meaningful only when complemented by an appropriate key management protocol. General guidelines are also given on how the framework should be used together with SIP and RTSP. The usage with the Multimedia Internet KEYing (MIKEY) key management protocol is also defined. [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 ...
- [rfc-dist] RFC 4567 on Key Management Extensions … rfc-editor@rfc-editor.org