@techreport{ietf-msec-ipsec-multicast-issues-01,
    number =    {draft-ietf-msec-ipsec-multicast-issues-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-msec-ipsec-multicast-issues/01/},
    author =    {Mark Baugher and Ran Canetti and Thomas Hardjono and Brian Weis},
    title =     {{IP Multicast issues with IPsec}},
    pagetotal = 10,
    year =      2002,
    month =     dec,
    day =       23,
    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.},
}