RFC 5796: Authentication and Confidentiality in Protocol Independent Multicast Sparse Mode (PIM-SM) Link-Local Messages
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5796
- Published
- March 2010
- Authors
- W. Atwood; S. Islam; M. Siami
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 21
- Also known as
- —
- Updates:
- RFC 4601
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5060Protocol Independent Multicast MIBCurrent
January 2008
- RFC 4611Multicast Source Discovery Protocol (MSDP) Deployment ScenariosCurrent
August 2006
- RFC 6178Label Edge Router Forwarding of IPv4 Option PacketsCurrent
March 2011
- RFC 5384The Protocol Independent Multicast (PIM) Join Attribute FormatUpdated
November 2008
- RFC 6233IS-IS Registry Extension for PurgesCurrent
May 2011
- RFC 5310IS-IS Generic Cryptographic AuthenticationUpdated
February 2009
- RFC 5304IS-IS Cryptographic AuthenticationUpdated
October 2008
- RFC 6506Supporting Authentication Trailer for OSPFv3Obsoleted
February 2012
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?