cryptoanarchy.wiki

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

1995-08-10 - IPSEC goes to RFC

Header Data

From: “Perry E. Metzger” <perry@panix.com>
To: cypherpunks@toad.com
Message Hash: bf2dd30ab0bc9df218650890c031628239ad8f0dcbeb7ee7e43fb3009cf874b2
Message ID: <199508100214.WAA28860@panix2.panix.com>
Reply To: N/A
UTC Datetime: 1995-08-10 02:14:34 UTC
Raw Date: Wed, 9 Aug 95 19:14:34 PDT

Raw message

From: "Perry E. Metzger" <perry@panix.com>
Date: Wed, 9 Aug 95 19:14:34 PDT
To: cypherpunks@toad.com
Subject: IPSEC goes to RFC
Message-ID: <199508100214.WAA28860@panix2.panix.com>
MIME-Version: 1.0
Content-Type: text/plain



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.

Please read them and help us in the effort to universally deploy this
protocol.

Still to come will be a key management system. The current notion is
to store RSA keys in the DNS -- a proposal to do this made by Eastlake
and Kaufman has been accepted by the IETF. Eastlake is now working on
a certificate format that will be an alternative to X.509. The keys
will be used by a modified version of the STS protocol (a signed
Diffie-Hellman exchange) that is being worked on by Phil Karn -- the
key management system is to be called "Photuris" and is currently an
internet draft.

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

Perry

Thread