Fwd: [MSEC] I-D ACTION:draft-ietf-msec-ipsec-multicast-issues-00.txt

[Thomas Hardjono <thardjono@yahoo.com>]

>Delivered-To: msec@pairlist.net
>Delivered-To: ietfsmug-securemulticast:org-msec@securemulticast.org
>To: IETF-Announce: ;IETF-Announce:;@securemulticast.org
>Cc: msec@securemulticast.org
>From: Internet-Drafts@ietf.org
>Reply-To: Internet-Drafts@ietf.org
>Subject: [MSEC] I-D ACTION:draft-ietf-msec-ipsec-multicast-issues-00.txt
>Sender: msec-admin@securemulticast.org
>X-BeenThere: msec@securemulticast.org
>X-Mailman-Version: 2.0
>List-Help: <mailto:msec-request@securemulticast.org?subject=help>
>List-Post: <mailto:msec@securemulticast.org>
>List-Subscribe: <http://www.pairlist.net/mailman/listinfo/msec>,
>         <mailto:msec-request@securemulticast.org?subject=subscribe>
>List-Id: IETF Multicast Security (MSEC) WG list <msec.securemulticast.org>
>List-Unsubscribe: <http://www.pairlist.net/mailman/listinfo/msec>,
>         <mailto:msec-request@securemulticast.org?subject=unsubscribe>
>List-Archive: <http://www.pairlist.net/pipermail/msec/>
>Date: Mon, 09 Dec 2002 08:03:19 -0500
>
>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>This draft is a work item of the Multicast Security Working Group of the IETF.
>
>         Title           : IP Multicast issues with IPsec
>         Author(s)       : M. Baugher, T. Hardjono, B. Weis
>         Filename        : draft-ietf-msec-ipsec-multicast-issues-00.txt
>         Pages           : 8
>         Date            : 2002-12-6
>
>The IPsec Architecture [RFC2401] and IPsec transform RFCs [RFC2402,
>RFC2406] define certain semantics for use of IPsec with 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. This document reviews these semantics and proposes
>changes which would enable IPsec to be generally useful for a wider
>variety of IPv4 and IPv6 multicast traffic.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-msec-ipsec-multicast-issues-00.txt
>
>To remove yourself from the IETF Announcement list, send a message to
>ietf-announce-request with the word unsubscribe in the body of the message.
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>         "get draft-ietf-msec-ipsec-multicast-issues-00.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>         mailserv@ietf.org.
>In the body type:
>         "FILE 
> /internet-drafts/draft-ietf-msec-ipsec-multicast-issues-00.txt".
>
>NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
>
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>
>Content-Type: text/plain
>Content-ID:     <2002-12-6141134.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-ietf-msec-ipsec-multicast-issues-00.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-ietf-msec-ipsec-multicast-issues-00.txt>