[rfc-dist] RFC 4909 on Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST LTKM/STKM Transport

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Wed Jun 27 17:25:59 PDT 2007


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



        

        RFC 4909



        Title:      Multimedia Internet KEYing (MIKEY) General 

                    Extension Payload for Open Mobile Alliance 

                    BCAST LTKM/STKM Transport 

        Author:     L. Dondeti, Ed.,

                    D. Castleford, F. Hartung

        Status:     Informational

        Date:       June 2007

        Mailbox:    ldondeti at qualcomm.com, 

                    david.castleford at orange-ftgroup.com, 

                    frank.hartung at ericsson.com

        Pages:      7

        Characters: 12228

        Updates/Obsoletes/SeeAlso:   None



        I-D Tag:    draft-dondeti-msec-mikey-genext-oma-04.txt



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



This document specifies a new Multimedia Internet KEYing (MIKEY)

General Extension payload (RFC 3830) to transport the short-term key 

message (STKM) and long-term key message (LTKM) payloads defined in the 

Open Mobile Alliance's (OMA) Browser and Content (BAC) Broadcast (BCAST)

group's Service and Content protection specification.  This memo provides information for the Internet community.





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 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.





The RFC Editor Team

USC/Information Sciences Institute



..





_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________


More information about the rfc-dist mailing list