I-D ACTION:draft-atkinson-ipng-auth-00.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IPv6 Authentication Header Author(s) : R. Atkinson Filename : draft-atkinson-ipng-auth-00.txt Pages : 10 Date : 11/16/1994 The Internet community is working on a transition from version 4 of the Internet Protocol (IPv4) to version 6 of the Internet Protocol (IPv6). This memo describes the IPv6 Authentication Header. This optional header provides strong integrity and authentication for IPv6 datagrams. Non-repudiation might be provided by an authentication algorithm used with the Authentication Header, but it is not provided with all authentication algorithms that might be used. Confidentiality, and protection from traffic analysis are not provided by the Authentication Header. Users desiring confidentiality should consider using the IPv6 Encapsulating Security Protocol (ESP) either in lieu of or in conjunction with the Authentication Header. [NB: All references to "IPv6 Encapsulating Security Protocol" will be replaced with references to the "IPv6 Security Protocol (IPSP)" if/when such a document appears as an online Internet Draft]. This document assumes the reader has previously read and understood the related "IPv6 Security Overview" document which defines the overall security architecture for IPv6 and provides important background information for this specification. Internet-Drafts are 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-atkinson-ipng-auth-00.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-atkinson-ipng-auth-00.txt Internet-Drafts directories are located at: o Africa Address: ftp.is.co.za (196.4.160.2) o Europe Address: nic.nordu.net (192.36.148.17) o Pacific Rim Address: munnari.oz.au (128.250.1.21) o US East Coast Address: ds.internic.net (198.49.45.10) o US West Coast Address: ftp.isi.edu (128.9.0.32) Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-atkinson-ipng-auth-00.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.
Some of us are participants in the IETF, are even on the IPSEC working group, and are well aware of the pending work on IPng and IPv4 security, and don't want Yet Another Copy of these things. If you insist, why not just note that there are drafts pending and not forward each of the announcement messages? Perry Eric Blossom says:
--NextPart
A New Internet-Draft is available from the on-line Internet-Drafts directories.
Title : IPv6 Authentication Header
THUS SPAKE "Perry E. Metzger" <perry@imsi.com>: # # Some of us are participants in the IETF, are even on the IPSEC working # group, and are well aware of the pending work on IPng and IPv4 # security, and don't want Yet Another Copy of these things. If you # insist, why not just note that there are drafts pending and not # forward each of the announcement messages? If he were to do that, people would ask (or at least wonder) 1. just what is this? and 2. where can I get it? It turns out the announcment is only two or three pages long, and about 1/3 of it answers question 1, and the other 2/3 answers (for various clients) question 2. I thought it was a very appropriate way of using the list -- a good comprimise between spamming and being silent. I was able to quickly determine if I was interested (I was), and use my favorite way to fetch it (since I'm not in metamail, I grabbed the URLs and LYNXed them.) strick
The standard thing in these cases is to say "There are some neat RFC drafts on security in ftp://hostname/names; you might be interested." I have already gotten three other copies of each of the three messages associated with Ran's new IPng drafts because every security mailing list on earth seems to operate on the "just forward everything" premise. More aren't needed. strick -- henry strickland says:
THUS SPAKE "Perry E. Metzger" <perry@imsi.com>: # # Some of us are participants in the IETF, are even on the IPSEC working # group, and are well aware of the pending work on IPng and IPv4 # security, and don't want Yet Another Copy of these things. If you # insist, why not just note that there are drafts pending and not # forward each of the announcement messages?
If he were to do that, people would ask (or at least wonder) 1. just what is this? and 2. where can I get it?
It turns out the announcment is only two or three pages long, and about 1/3 of it answers question 1, and the other 2/3 answers (for various clients) question 2.
I thought it was a very appropriate way of using the list -- a good comprimise between spamming and being silent. I was able to quickly determine if I was interested (I was), and use my favorite way to fetch it (since I'm not in metamail, I grabbed the URLs and LYNXed them.)
strick
THUS SPAKE "Perry E. Metzger" <perry@imsi.com>: # # The standard thing in these cases is to say "There are some neat RFC # drafts on security in ftp://hostname/names; you might be interested." Yeah, there's always neat RFC drafts on security out there; that hardly needs announceing. Which ones are new & interesting & why? # I have already gotten three other copies of each of the three messages # associated with Ran's new IPng drafts because every security mailing # list on earth seems to operate on the "just forward everything" # premise. More aren't needed. So the perfect solution, from your point of view, is that there be no announcement on cyperpunks. And the perfect solution, from my point of view, is that you unsubscribe from all those other lists, so that you only see one announcement. :) And the perfect solution, from everyone's point of view, is to have a real solution to the document-repost problem. Like a cypherpunk registry web page where you post small announcements and pointers to things, with the ability to scan first and see if anyone else has done that. Then a periodic summary of new stuff gets mailed out on a regular basis, if there is new stuff to announce. Sounds like a good web project for someone ... strick
In article <199411182159.NAA10356@gwarn.versant.com>, strick -- henry strickland <strick@versant.com> wrote:
So the perfect solution, from your point of view, is that there be no announcement on cyperpunks.
Oh, please. You can announce them without sending them out verbatim to the entire world: established net procedure is to just post a pointer to anything really huge instead of spamming every mailing list where people might be interested. If you want to note why they're interesting, you can explain that with the pointer and provide a real service: people are unlikely to read huge volumes unless you have a reputation for sending Really Interesting Stuff (IE, if Bruce Schneir posted something huge, it'd get read more than if I posted something huge). -- Todd Masco | "I'd rather have my country die for me." - P Kantner cactus@hks.net | "But for now, only our T-shirts cry 'freedom!'." - Fish
Perry E. Metzger scribbles:
Some of us are participants in the IETF, are even on the IPSEC working group, and are well aware of the pending work on IPng and IPv4 security, and don't want Yet Another Copy of these things. If you insist, why not just note that there are drafts pending and not forward each of the announcement messages?
Because many, probably most of us aren't participants, and these items are of greater cryptological relavence than much, if not most, of the material on the list. How would a note about the drafts being pending and the posting of the announcement be significantly different? I appreciate the MIME encoding of the mail, since my MIME mail reader can go out and pull them for me. Bob
-----BEGIN PGP SIGNED MESSAGE----- Bob Snyder writes:
How would a note about the drafts being pending and the posting of the announcement be significantly different? I appreciate the MIME encoding of the mail, since my MIME mail reader can go out and pull them for me.
Speaking of which, can anyone explain why my usually-MIME-compliant mail reader (ELM 2.4 PL22) pukes on the fancy parts of all these draft announcements ? Personally, I find MIMEd messages very annoying because I'm forced to hit RETURN (not just "any key") several extra times for each message. {Luckily, it's clear that I'd never have time to read any of these, so they get tossed in the bit bucket almost immediately.} - -L. McCarthy -----BEGIN PGP SIGNATURE----- Version: 2.6.1 iQCVAwUBLs05aWf7YYibNzjpAQGFKgP7BoFckFIIQ7GzoPiqExUWesbVHi0r4zjp yD/d2ipLQA6ii8VDMviJ6Y2j3wyxk5gNDYBgkHG56D57gD0SwJL8tlCUgvQDkprM AsCiu4ojNDVAdt+jppITPimMIUM5gRRh7uuMcjzunI6PDl3056H+ZGQXJAJV9g21 34UaRN4mSfQ= =jH2A -----END PGP SIGNATURE-----
L. McCarthy wrote:
Speaking of which, can anyone explain why my usually-MIME-compliant mail reader (ELM 2.4 PL22) pukes on the fancy parts of all these draft announcements ? Personally, I find MIMEd messages very annoying because I'm forced to hit RETURN (not just "any key") several extra times for each message. {Luckily, it's clear that I'd never have time to read any of these, so they get tossed in the bit bucket almost immediately.}
Hear, hear! An increasing fraction of my e-mail is non-ASCII, and has this MIME (or whatever) stuff in it. (The Smalltalk list I'm on is about 50% like this.) I suppose some messages make use of it, as Eric Blossom's just did (in allowing retrieval of more stuff, somehow), but a lot of the "offending" messages just seem to be non-ASCII for the hell of it. Like Lewis, I find myself to easily delete the message and move on. (I'm debating just deleting the messsages, which are marked "M" for Mime, before even starting to read them.) Personally, I like simple ASCII. No fancy fonts, no embedded graphics, no Quicktime movies I have to watch, etc. Just my views. --Tim May -- .......................................................................... Timothy C. May | Crypto Anarchy: encryption, digital money, tcmay@netcom.com | anonymous networks, digital pseudonyms, zero 408-688-5409 | knowledge, reputations, information markets, W.A.S.T.E.: Aptos, CA | black markets, collapse of governments. Higher Power: 2^859433 | Public Key: PGP and MailSafe available. Cypherpunks list: majordomo@toad.com with body message of only: subscribe cypherpunks. FAQ available at ftp.netcom.com in pub/tcmay
participants (7)
-
Bob Snyder -
cactus＠bb.hks.net -
Eric Blossom -
L. McCarthy -
Perry E. Metzger -
strick -- henry strickland -
tcmay＠netcom.com