[29524] in North American Network Operators' Group
Re: PGP kerserver infrastructure
daemon@ATHENA.MIT.EDU (L. Sassaman)
Tue Jun 27 15:45:41 2000
Date: Tue, 27 Jun 2000 12:43:14 -0700 (PDT)
From: "L. Sassaman" <rabbi@quickie.net>
To: Shawn McMahon <smcmahon@eiv.com>
Cc: nanog@merit.edu
In-Reply-To: <20000627145856.A2713@eiv.com>
Message-ID: <Pine.LNX.4.21.QNWS_2.0006271238390.14157-100000@thetis.deor.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Keyservers are officially out of the scope of the OpenPGP working group's
charter, last I heard. Jon Callas (author/editor of RFC 2440) suggested
that if there was interest, we start a working group on keyserver
behaviors.
There are many issues too detailed to go into here that should be
formally addressed in regards to keyservers. If the keyserver
infrastructure does ramp up, I think that an RFC will be in order. Anyone
with the IETF here? Who would I talk to about forming such a WG? Is a
keyserver standard within the scope of the IETF?
On Tue, 27 Jun 2000, Shawn McMahon wrote:
>
> If you guys are serious about being the latest cast and crew to pursue this,
> here's a resource you might want to be aware of:
>
> http://www.imc.org/ietf-openpgp/
>
>
> You also might want to look at this message from their mailing list archive:
>
> http://www.imc.org/ietf-openpgp/mail-archive/msg02132.html
>
> They have a pgp-directory mailing list, and all of this has been discussed
> before, so perhaps it can save you some research.
>
>
__
L. Sassaman
System Administrator | "Everything looks bad
Technology Consultant | if you remember it."
icq.. 10735603 |
pgp.. finger://ns.quickie.net/rabbi | --Homer Simpson
-----BEGIN PGP SIGNATURE-----
Comment: OpenPGP Encrypted Email Preferred.
iD8DBQE5WQPfPYrxsgmsCmoRAhp1AJ48hfG4xci33ztbyxdKtj4KFAiK1wCgvasC
nATU/P0GELbazSEhdZetw4Y=
=2RVA
-----END PGP SIGNATURE-----
