IP Multicast issues with IPsec
draft-ietf-msec-ipsec-multicast-issues-01

Document Type Expired Internet-Draft (msec WG)
Last updated 2002-12-23
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-msec-ipsec-multicast-issues-01.txt

Abstract

The IPsec Architecture [RFC2401] and IPsec transform RFCs [RFC2402, RFC2406] define certain mechanisms for IP multicast traffic. The recent revisions to each of the protocol documents [ESPbis, AHbis] propose changes to those semantics. However, neither the existing nor proposed semantics are sufficiently general such that IPsec can be used to protect the wide variety of IPv4 and IPv6 multicast applications that are expected by the IP multicast community. In particular, they are not compatible with the needs of the protocols developed in the MSEC WG and for Source Specific Multicast [RFC3376, SSM-ARCH]. This document reviews these semantics and proposes some minor changes, which would enable IPsec to be suitable for these uses.

Authors

Mark Baugher (mbaugher@cisco.com)
Ran Canetti (canetti@watson.ibm.com)
Thomas Hardjono (thardjono@verisign.com)
Brian Weis (bew@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)