[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
I-D ACTION:draft-ietf-sipp-ap-04.txt
With the posting of Ran's most recent Authentication Header draft,
I formally request that this WG adopt it as a Proposed Standard for
IPv4. This would require the removal of very little IPv6 language.
I believe this action to be the consensus at the Toronto IETF.
> Mime-Version: 1.0
> Content-Type: Multipart/Mixed; Boundary="NextPart"
> To: IETF-Announce:@CNRI.Reston.VA.US@Eng.Sun.COM@Sun.COM;
> Cc: sipp@sunroof.eng.sun.com
> From: Internet-Drafts@CNRI.Reston.VA.US
> Subject: (sipp) I-D ACTION:draft-ietf-sipp-ap-04.txt
> Date: Tue, 16 Aug 94 10:47:35 -0400
> Message-Id: <9408161047.aa05277@IETF.CNRI.Reston.VA.US>
> Sender: owner-sipp@sunroof.eng.sun.com
> Precedence: bulk
> Reply-To: sipp@sunroof.eng.sun.com
>
> --NextPart
>
> A Revised Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the Simple Internet Protocol Plus
> Working Group of the IETF.
>
> Title : IPv6 Authentication Header
> Author(s) : R. Atkinson
> Filename : draft-ietf-sipp-ap-04.txt
> Pages : 9
> Date : 08/15/1994
>
> This draft specifies the Authentication Header to be used to provide
> authentication and integrity without confidentiality to IPv6 datagrams.
> It is one of two security mechanisms proposed for IPv6.
>
> Internet-Drafts are available by anonymous FTP. Login with the
> username "anonymous" and password "guest". After logging in,
> Type "cd internet-drafts".
> "get draft-ietf-sipp-ap-04.txt".
>
> Internet-Drafts directories are located at:
>
> o US East Coast
> Address: ds.internic.net (198.49.45.10)
>
> o US West Coast
> Address: ftp.isi.edu (128.9.0.32)
>
> o Pacific Rim
> Address: munnari.oz.au (128.250.1.21)
>
> o Europe
> Address: nic.nordu.net (192.36.148.17)
>
> Internet-Drafts are also available by mail.
>
> Send a message to: mailserv@ds.internic.net. In the body type:
> "FILE /internet-drafts/draft-ietf-sipp-ap-04.txt".
>
> NOTE: The mail server at ds.internic.net 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.
>
> For questions, please mail to Internet-Drafts@cnri.reston.va.us.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version
> of the Internet-Draft.
>
> --NextPart
> Content-Type: Multipart/Alternative; Boundary="OtherAccess"
>
> --OtherAccess
> Content-Type: Message/External-body;
> access-type="mail-server";
> server="mailserv@ds.internic.net"
>
> Content-Type: text/plain
> Content-ID: <19940815131545.I-D@CNRI.Reston.VA.US>
>
> ENCODING mime
> FILE /internet-drafts/draft-ietf-sipp-ap-04.txt
>
> --OtherAccess
> Content-Type: Message/External-body;
> name="draft-ietf-sipp-ap-04.txt";
> site="ds.internic.net";
> access-type="anon-ftp";
> directory="internet-drafts"
>
> Content-Type: text/plain
> Content-ID: <19940815131545.I-D@CNRI.Reston.VA.US>
>
> --OtherAccess--
>
> --NextPart--
Bill.Simpson@um.cc.umich.edu
Follow-Ups: