RFC 4563 on The Key ID Information Type for the General Extension Payload in Multimedia Internet KEYing (MIKEY)

[rfc-editor at rfc-editor.org]

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

        
        RFC 4563

        Title:      The Key ID Information Type 
                    for the General Extension Payload in 
                    Multimedia Internet KEYing (MIKEY) 
        Author:     E. Carrara, V. Lehtovirta,
                    K. Norrman
        Status:     Standards Track
        Date:       June 2006
        Mailbox:    carrara at kth.se, 
                    vesa.lehtovirta at ericsson.com, 
                    karl.norrman at ericsson.com
        Pages:      10
        Characters: 20464
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-msec-newtype-keyid-05.txt

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

This memo specifies a new Type (the Key ID Information Type) for the
General Extension Payload in the Multimedia Internet KEYing (MIKEY)
Protocol.  This is used in, for example, the Multimedia 
Broadcast/Multicast Service specified in the Third Generation Partnership 
Project.  [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

...



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