[rfc-dist] RFC 4650 on HMAC-Authenticated Diffie-Hellman for Multimedia Internet KEYing (MIKEY)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Sat Sep 30 14:25:53 PDT 2006

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

        RFC 4650

        Title:      HMAC-Authenticated Diffie-Hellman for Multimedia 
                    Internet KEYing (MIKEY) 
        Author:     M. Euchner
        Status:     Standards Track
        Date:       September 2006
        Mailbox:    martin_euchner at hotmail.com
        Pages:      27
        Characters: 63016
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-msec-mikey-dhhmac-11.txt

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

This document describes a lightweight point-to-point key management
protocol variant for the multimedia Internet keying (MIKEY) protocol
MIKEY, as defined in RFC 3830.  In particular, this variant deploys
the classic Diffie-Hellman key agreement protocol for key
establishment featuring perfect forward secrecy in conjunction with
a keyed hash message authentication code for achieving mutual
authentication and message integrity of the key management messages
exchanged.  This protocol addresses the security and performance
constraints of multimedia key management in MIKEY.  [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 

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

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