RFC 4535: GSAKMP: Group Secure Association Key Management Protocol
In plain English — editorial summary, not part of the RFC
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 keys. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4535
- Published
- June 2006
- Authors
- H. Harney; U. Meth; A. Colegrove; G. Gross
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 106
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4534Group Security Policy Token v1Current
June 2006
- RFC 4537Kerberos Cryptosystem Negotiation ExtensionCurrent
June 2006
- RFC 4555IKEv2 Mobility and Multihoming Protocol (MOBIKE)Current
June 2006
- RFC 4556Public Key Cryptography for Initial Authentication in Kerberos (PKINIT)Updated
June 2006
- RFC 4557Online Certificate Status Protocol (OCSP) Support for Public Key Cryptography for Initial Authentication in Kerberos (PKINIT)Current
June 2006
- RFC 4563The Key ID Information Type for the General Extension Payload in Multimedia Internet KEYing (MIKEY)Updated
June 2006
- RFC 4505Anonymous Simple Authentication and Security Layer (SASL) MechanismCurrent
June 2006
- RFC 4492Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS)Obsoleted
May 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?