cryptoanarchy.wiki

Arise, you have nothing to lose but your barbed wire fences!

1995-08-10 - Re: IPSEC goes to RFC

Header Data

From: Adam Shostack <adam@bwh.harvard.edu>
To: perry@piermont.com
Message Hash: eeb6bf651907da63461da9c9e34d97de9775cddfaa2a65a6330e544040b594c3
Message ID: <199508100310.XAA11723@bwh.harvard.edu>
Reply To: <199508100214.WAA28860@panix2.panix.com>
UTC Datetime: 1995-08-10 03:10:19 UTC
Raw Date: Wed, 9 Aug 95 20:10:19 PDT

Raw message

From: Adam Shostack <adam@bwh.harvard.edu>
Date: Wed, 9 Aug 95 20:10:19 PDT
To: perry@piermont.com
Subject: Re: IPSEC goes to RFC
In-Reply-To: <199508100214.WAA28860@panix2.panix.com>
Message-ID: <199508100310.XAA11723@bwh.harvard.edu>
MIME-Version: 1.0
Content-Type: text/plain


Perry wrote:

| RFCs 1825, 1826, 1827, 1828, and 1829 came out today.
| 
| These RFCs describe in detail the IPSEC protocol, which is designed to
| secure the internet from the ground up. IPSEC permits the
| cryptographic encapsulation of all your IP traffic, which means all
| your internet communications.
| 
| IPSEC is now a Proposed Standard.

| Again, *we need your help*. Cypherpunks write code. Help us make the
| internet safe for personal privacy by contributing to this effort.

	How about posting a list of 'things that need doing?'  I
assume one is floating around, possibly even with time estimates?

Adam


-- 
"It is seldom that liberty of any kind is lost all at once."
					               -Hume

Thread