From: "Perry E. Metzger" <perry@panix.com>
Date: Thu, 10 Aug 95 07:52:58 PDT
To: Adam Shostack <adam@bwh.harvard.edu>
Subject: Re: IPSEC goes to RFC
In-Reply-To: <199508100310.XAA11723@bwh.harvard.edu>
Message-ID: <199508101452.KAA24637@panix4.panix.com>
MIME-Version: 1.0
Content-Type: text/plain



Adam Shostack writes:
> | 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?

The IETF was challenged by Steve Crocker to be ready for use of IPSEC
for the Dallas meeting in December so that no IETFer who wanted to
communicate securely with his home site need be insecure.

To accomplish that, we need to produce versions of the security stack
for many architectures. Right now, we have AIX and 4.4BSD fairly
solidly covered. Less well covered is HPUX. People familiar with code
like the Trumpet Winsock stack, Linux, or who have access to the
innards of SunOS, Solaris, Windows 95, Mac stacks, and others, and can
legitimately release implementations for those platforms, are probably
needed. We need serious commitments from people but of course everyone
is trying to help everyone else along.

Basically, if you know how to hack kernels and networking code and you
have a platform you can work on, we need you.

We also lack work on the key management end of things -- people who
can start playing around with implementing Photuris, even on a "toy"
basis, would probably be of help.

Perry