RFC 5374: Multicast Extensions to the Security Architecture for the Internet Protocol
In plain English — editorial summary, not part of the RFC
The Security Architecture for the Internet Protocol describes security services for traffic at the IP layer. That architecture primarily defines services for Internet Protocol (IP) unicast packets. This document describes how the IPsec security services are applied to IP multicast packets. These extensions are relevant only for an IPsec implementation that supports multicast. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5374
- Published
- November 2008
- Authors
- B. Weis; G. Gross; D. Ignjatic
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 38
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 2401Security Architecture for the Internet ProtocolObsoleted
November 1998
- RFC 1829The ESP DES-CBC TransformCurrent
August 1995
- RFC 5387Problem and Applicability Statement for Better-Than-Nothing Security (BTNS)Current
November 2008
- RFC 5660IPsec Channels: Connection LatchingCurrent
October 2009
- RFC 5755An Internet Attribute Certificate Profile for AuthorizationCurrent
January 2010
- RFC 4945The Internet IP Security PKI Profile of IKEv1/ISAKMP, IKEv2, and PKIXCurrent
August 2007
- RFC 5879Heuristics for Detecting ESP-NULL PacketsCurrent
May 2010
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?