GSAKMP: Group Secure Association Key Management Protocol

Harney, Hugh; Meth, Uri; Colegrove, Andrea; Gross, George

doi:10.17487/rfc4535

Cited by 48 publications

(39 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Several existing protocols, including Group DOI (GDOI) [RFC3547], Group Secure Association Key Management Protocol (GSAKMP) [RFC4535], and Multimedia Internet KEYing (MIKEY) [RFC3830], satisfy the group key management requirements defined in this document. Both the architecture and the components for Multicast Group Security differ from IPsec.…”

Section: Rfc 4869 Suite B Cryptographic Suites For Ipsec (I May 2007)mentioning

confidence: 99%

IP Security (IPsec) and Internet Key Exchange (IKE) Document Roadmap

Krishnan¹,

Frankel²

2011

110

View full text Add to dashboard Cite

Over the past few years, the number of RFCs that define and use IPsec and Internet Key Exchange (IKE) has greatly proliferated. This is complicated by the fact that these RFCs originate from numerous IETF working groups: the original IPsec WG, its various spin-offs, and other WGs that use IPsec and/or IKE to protect their protocols' traffic.This document is a snapshot of IPsec-and IKE-related RFCs. It includes a brief description of each RFC, along with background information explaining the motivation and context of IPsec's outgrowths and extensions. It obsoletes RFC 2411, the previous "IP Security Document Roadmap."

show abstract

Section: Rfc 4869 Suite B Cryptographic Suites For Ipsec (I May 2007)mentioning

confidence: 99%

IP Security (IPsec) and Internet Key Exchange (IKE) Document Roadmap

Krishnan¹,

Frankel²

2011

110

View full text Add to dashboard Cite

show abstract

“…This does not preclude the use of a negotiation protocol such as the Group Domain Of Interpretation (GDOI) [RFC3547] or Group Secure Association Key Management Protocol (GSAKMP) [RFC4535] to establish these SAs.…”

Section: Key Managementmentioning

confidence: 99%

Authentication and Confidentiality in Protocol Independent Multicast Sparse Mode (PIM-SM) Link-Local Messages

Islam¹,

Siami²

2010

View full text Add to dashboard Cite

RFC 4601 mandates the use of IPsec to ensure authentication of the link-local messages in the Protocol Independent Multicast -Sparse Mode (PIM-SM) routing protocol. This document specifies mechanisms to authenticate the PIM-SM link-local messages using the IP security (IPsec) Encapsulating Security Payload (ESP) or (optionally) the Authentication Header (AH). It specifies optional mechanisms to provide confidentiality using the ESP. Manual keying is specified as the mandatory and default group key management solution. To deal with issues of scalability and security that exist with manual keying, optional support for an automated group key management mechanism is provided. However, the procedures for implementing automated group key management are left to other documents. This document updates RFC 4601.

show abstract

“…However, the establishment of multicast security associations (phase 2b) typically does not involve EAP and needs to be handled by a group key management protocol such as Group Domain of Interpretation (GDOI) [RFC3547], Group Secure Association Key Management Protocol (GSAKMP) [RFC4535], Multimedia Internet KEYing (MIKEY) [RFC3830], or Group Key Distribution Protocol (GKDP) [GKDP]. Several mechanisms have been proposed for the discovery of IPsec security gateways.…”

Section: Ikev2mentioning

confidence: 99%