-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sorry you found my posting off-topic. Since the charter process has
not been completed yet (I believe it's going through due process, I
am not worried) and since I was discussing a critical and
undocumented aspect of the current and future technology I thought it
was relevant.
I think we have to allow some level of discussion of the state of the
art in this forum or else we won't have a baseline as to where the
next generation of PGP should go.
The fact there is no public established developer list is exactly the
point -- there are clusters of informal communities, and what we want
to do is to get those pulled together in an IETF framework to move
forward.
Also, you seem to have waited an AWFULLY long time before speaking
up.
Date: Tue, 9 Sep 1997 19:45:12 -0700
To: ietf-open-pgp(_at_)imc(_dot_)org
From: Paul Hoffman / IMC <phoffman(_at_)imc(_dot_)org>
Subject: The purpose of this mailing list
Sender: owner-ietf-open-pgp(_at_)imc(_dot_)org
This mailing list is for discussion of the next-generation of
PGP/MIME. We
should be creating and discussing descriptions of that protocol.
The discussions of the last few days (key server lookup protocol,
API) are
not really relevant to the OpenPGP spec. Disucssions about how a
particular
implementation of PGP work should be on the PGP developer's mailing
list,
not here. (I don't remember where that mailing list is, and it
doesn't seem
to be mentioned on the PGP, Inc. Web site, so if someone wants to
pipe in
with the address of that list, it would be very helpful.)
--Paul E. Hoffman, Director
--Internet Mail Consortium
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv
iQA/AwUBNBaXS4wpVk/gvJfqEQJCYACZAfhKtSfOrmmLaJbE3eZf6VfK7TMAn3Zj
dvCls2TxkQ7+Y3H+NuK9czyY
=UqBL
-----END PGP SIGNATURE-----