Re: editorial on Photuris

Derek Atkins <warlord@MIT.EDU> Tue, 14 November 1995 22:13 UTC

Received: from interlock.ans.net by ftp.ans.net with SMTP id AA15403 (5.65c/IDA-1.4.4 for <archive-ipsec@ftp.ans.net>); Tue, 14 Nov 1995 17:13:32 -0500
Received: by interlock.ans.net id AA07356 (InterLock SMTP Gateway 3.0 for ipsec-out@ans.net); Tue, 14 Nov 1995 17:12:00 -0500
Message-Id: <199511142212.AA07356@interlock.ans.net>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-2); Tue, 14 Nov 1995 17:12:00 -0500
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-1); Tue, 14 Nov 1995 17:12:00 -0500
To: rja@cs.nrl.navy.mil
Cc: Charles Watt <watt@sware.com>, ipsec@ans.net
Subject: Re: editorial on Photuris
In-Reply-To: Your message of "Tue, 14 Nov 1995 15:35:53 EST." <199511142037.AA03346@interlock.ans.net>
Date: Tue, 14 Nov 1995 17:10:31 -0500
From: Derek Atkins <warlord@MIT.EDU>

> There is no process problem with the IETF referencing PGP certificates.
> The IETF is not restricted to only referencing IETF specs.

FYI: There is currently an I-D specifying the format of PGP version 2
(and version 3) packet formats.  This specification includes the
definition of public key certificates.

Hopefully this draft will be lifted to an RFC in the near future.
Please feel free to comment on it.  It is currently called:
	draft-atkins-pgpformat-01.txt

-derek