[rfc-dist] RFC 4535 on GSAKMP: Group Secure Association Key Management Protocol

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Mon Jun 26 12:15:04 PDT 2006

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

        RFC 4535

        Title:      GSAKMP: Group Secure Association Key 
                    Management Protocol 
        Author:     H. Harney, U. Meth,
                    A. Colegrove, G. Gross
        Status:     Standards Track
        Date:       June 2006
        Mailbox:    hh at sparta.com, 
                    umeth at sparta.com, 
                    acc at sparta.com,  gmgross at identaware.com
        Pages:      106
        Characters: 240863
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-msec-gsakmp-sec-10.txt

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

This document specifies the Group Secure Association
Key Management Protocol (GSAKMP).  The GSAKMP provides a
security framework for creating and managing cryptographic
groups on a network.  It provides mechanisms to disseminate
group policy and authenticate users, rules to perform
access control decisions during group establishment and
recovery, capabilities to recover from the compromise of
group members, delegation of group security functions, and
capabilities to destroy the group.  It also generates group

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