[rfc-dist] RFC 4738 on MIKEY-RSA-R: An Additional Mode of Key Distribution in Multimedia Internet KEYing (MIKEY)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Thu Nov 16 17:42:16 PST 2006


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

        
        RFC 4738

        Title:      MIKEY-RSA-R: An Additional Mode of 
                    Key Distribution in Multimedia Internet KEYing 
                    (MIKEY) 
        Author:     D. Ignjatic, L. Dondeti,
                    F. Audet, P. Lin
        Status:     Standards Track
        Date:       November 2006
        Mailbox:    dignjatic at polycom.com, 
                    ldondeti at qualcomm.com, 
                    audet at nortel.com,  linping at nortel.com
        Pages:      19
        Characters: 43015
        Updates:    RFC3830
        See-Also:   

        I-D Tag:    draft-ietf-msec-mikey-rsa-r-07.txt

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

The Multimedia Internet Keying (MIKEY) specification describes
several modes of key distribution solution that address multimedia
scenarios (e.g., SIP calls and Real Time Streaming Protocol (RTSP)
sessions) using pre-shared keys, public keys, and optionally a
Diffie-Hellman key exchange.  In the public-key mode, the Initiator
encrypts a random key with the Responder's public key and sends it to
the Responder.  In many communication scenarios, the Initiator may
not know the Responder's public key, or in some cases the Responder's
ID (e.g., call forwarding) in advance.  We propose a new MIKEY mode
that works well in such scenarios.  This mode also enhances the group
key management support in MIKEY; it supports member-initiated group
key download (in contrast to group manager pushing the group keys to
all members).  This document updates RFC 3830 with the RSA-R mode.  
[STANDARDS TRACK]

This document is a product of the Multicast Security
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

...




More information about the rfc-dist mailing list