FW: RFC 3830 on MIKEY: Multimedia Internet KEYing

simao.campos at ITU.INT simao.campos at ITU.INT
Sun Aug 29 17:36:45 EDT 2004


Dear colleagues,

FYI as it may be of interest (in particular Q.G/16)

Cheers,
Simão

-----Original Message-----
From: rfc-editor at rfc-editor.org [mailto:rfc-editor at rfc-editor.org] 
Sent: Saturday, August 28, 2004 01:55
To: ietf-announce at ietf.org
Cc: msec at securemulticast.org; rfc-editor at rfc-editor.org
Subject: RFC 3830 on MIKEY: Multimedia Internet KEYing



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


        RFC 3830

        Title:      MIKEY: Multimedia Internet KEYing
        Author(s):  J. Arkko, E. Carrara, F. Lindholm, M. Naslund,
                    K. Norrman
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    jari.arkko at ericsson.com,
                    elisabetta.carrara at ericsson.com,
                    fredrik.lindholm at ericsson.com,
                    mats.naslund at ericsson.com,
                    karl.norrman at ericsson.com
        Pages:      66
        Characters: 145238
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-msec-mikey-08.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3830.txt


This document describes a key management scheme that can be used for
real-time applications (both for peer-to-peer communication and group
communication).  In particular, its use to support the Secure Real-time
Transport Protocol is described in detail.

Security protocols for real-time multimedia applications have started to
appear.  This has brought forward the need for a key management solution to
support these protocols.

This document is a product of the Multicast Security Working Group of the
IETF.

This is now a Proposed Standard Protocol.

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

..

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.



More information about the sg16-avd mailing list