[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Adding in BZ2 compression?

To: Len Sassaman <rabbi@xxxxxxxxxxx>
Subject: Re: Adding in BZ2 compression?
From: David Shaw <dshaw@xxxxxxxxxxxxxxx>
Date: Thu, 17 Jul 2003 20:58:46 -0400
Cc: Jon Callas <jon@xxxxxxxxxx>, OpenPGP <ietf-openpgp@xxxxxxx>
Delivery-date: Fri, 18 Jul 2003 03:01:43 +0200
Envelope-to: ietf-openpgp@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.30.QNWS.0307171509430.4445-100000@xxxxxxxxxxxxxxx>
List-archive: <http://www.imc.org/ietf-openpgp/mail-archive/>
List-id: <ietf-openpgp.imc.org>
List-unsubscribe: <mailto:ietf-openpgp-request@imc.org?body=unsubscribe>
Mail-followup-to: Len Sassaman <rabbi@xxxxxxxxxxx>, Jon Callas <jon@xxxxxxxxxx>, OpenPGP <ietf-openpgp@xxxxxxx>
References: <BB2F668E.80013EBA%jon@xxxxxxxxxx> <Pine.LNX.4.30.QNWS.0307171509430.4445-100000@xxxxxxxxxxxxxxx>
Sender: owner-ietf-openpgp@xxxxxxxxxxxx
User-agent: Mutt/1.5.4i

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Jul 17, 2003 at 03:13:32PM -0700, Len Sassaman wrote:

> > Yes, I know that there are potential interoperability issues when keys get
> > migrated around, but I also of the opinion that when an implementation
> > imports a key, it should make sure that the preferences reflect what it
> > supports.
> 
> Amen. Can that be explicitly stated in the next draft?

Yes, please.

David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3rc1 (GNU/Linux)
Comment: Key available at http://www.jabberwocky.com/david/keys.asc

iD8DBQE/F0ZG4mZch0nhy8kRAgXiAKCglNsielY5l+GddZZVfD5+JGF0pACfZSyq
Zx7ePyEobFstdZIEw2D2dZ8=
=VeVu
-----END PGP SIGNATURE-----

References:
- Re: Adding in BZ2 compression?
  - From: Jon Callas
- Re: Adding in BZ2 compression?
  - From: Len Sassaman

Prev by Date: Re: Requiring self-signed uids? (was Re: PoP & Signer's User ID subpacket?)
Next by Date: Re: key flag for authentication
Previous by thread: Re: Adding in BZ2 compression?
Next by thread: Re: Adding in BZ2 compression?
Index(es):
- Date
- Thread