Re: [TLS] Review of draft-ietf-tls-openpgp-keys-08
Nikos Mavrogiannopoulos <nmav@gnutls.org> Tue, 16 May 2006 17:33 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg3Q2-0000tL-IW; Tue, 16 May 2006 13:33:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg3Q1-0000tG-Dt for tls@ietf.org; Tue, 16 May 2006 13:33:13 -0400
Received: from ug-out-1314.google.com ([66.249.92.175]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fg3Q0-00032l-49 for tls@ietf.org; Tue, 16 May 2006 13:33:13 -0400
Received: by ug-out-1314.google.com with SMTP id k3so28312ugf for <tls@ietf.org>; Tue, 16 May 2006 10:33:11 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender; b=k9pIiVdi5pW2JWt4Y0sS7XOaePGb3QuK9cyKcMPB5ABnOkcDx6v9D3Lfki1h5IPRCtxsKz0Khk69pWUnu5rTFDpln1mNznGAEjiNoPdASi2N2JElZpod9WnkCxMUryz0l8QfSBvV2/+EE4g6LBVWR5npJEDJCsADjqRc1pj0Brc=
Received: by 10.67.87.4 with SMTP id p4mr3492894ugl; Tue, 16 May 2006 10:33:11 -0700 (PDT)
Received: from ?172.16.1.206? ( [81.175.93.238]) by mx.gmail.com with ESMTP id m1sm1303544uge.2006.05.16.10.33.10; Tue, 16 May 2006 10:33:10 -0700 (PDT)
From: Nikos Mavrogiannopoulos <nmav@gnutls.org>
To: tls@ietf.org
Subject: Re: [TLS] Review of draft-ietf-tls-openpgp-keys-08
Date: Tue, 16 May 2006 19:32:41 +0200
User-Agent: KMail/1.9.1
References: <B356D8F434D20B40A8CEDAEC305A1F2402A799DB@esebe105.NOE.Nokia.com>
In-Reply-To: <B356D8F434D20B40A8CEDAEC305A1F2402A799DB@esebe105.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200605161932.41460.nmav@gnutls.org>
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc:
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
Errors-To: tls-bounces@lists.ietf.org
On Tue 16 May 2006 13:59, Pasi.Eronen@nokia.com wrote: > Thus, I would not hard-code this limitation in the specification, > especially when it's very easy to avoid (just allow a list just > as in normal TLS), and there's just 3 bytes of overhead for > implementations that send only one PGP key... (and in fact > even this overhead could be avoided if we remove the redundant > length field by stating that the "key descriptor type" is the > first byte of the key data) It is not about the byte overhead. It is about defining what a key chain is how is it going to be used, what is an implementor going to put there etc. Otherwise it would be a pandoras box, waiting to be opened. Given the feedback I've got all the years this draft exists, it seems that nobody so far had a need for it. If in the future this proves to be a limitation, it is easy to add an extra key descriptor type with a key list, that follows some rules, or none. > > That approach follows the way openpgp keys are used in electronic > > mail and I see no good reason to change it by introducing an > > openpgp key chain in this draft. > It does not follow the email way of using PGP: most email messages > don't contain the public key at all (only the signature), and when + the fingerprint of the signer, because that's what is needed for authentication. The receipient is responsible for retrieving the keys based on the fingerprint. regards, Nikos ps. I hope I didn't get rude or personal in this or previous mails, but my point is that since we have no use of this functionality today, I see no point in adding it. If needed it might be better to be added from people who would use it because they will define it the way the really need it. _______________________________________________ TLS mailing list TLS@lists.ietf.org https://www1.ietf.org/mailman/listinfo/tls
- [TLS] Review of draft-ietf-tls-openpgp-keys-08 Pasi.Eronen
- Re: [TLS] Review of draft-ietf-tls-openpgp-keys-08 Nikos Mavrogiannopoulos
- RE: [TLS] Review of draft-ietf-tls-openpgp-keys-08 Pasi.Eronen
- Re: [TLS] Review of draft-ietf-tls-openpgp-keys-08 Nikos Mavrogiannopoulos
- RE: [TLS] Review of draft-ietf-tls-openpgp-keys-08 Pasi.Eronen
- Re: [TLS] Review of draft-ietf-tls-openpgp-keys-08 Nikos Mavrogiannopoulos
- RE: [TLS] Review of draft-ietf-tls-openpgp-keys-08 Pasi.Eronen
- [TLS] Re: Review of draft-ietf-tls-openpgp-keys-08 Simon Josefsson
- Re: [TLS] Re: Review of draft-ietf-tls-openpgp-ke… Eric Rescorla
- Re: [TLS] Re: Review of draft-ietf-tls-openpgp-ke… Nikos Mavrogiannopoulos
- Re: [TLS] Review of draft-ietf-tls-openpgp-keys-08 Nikos Mavrogiannopoulos
- Re: [TLS] Re: Review of draft-ietf-tls-openpgp-ke… Steven M. Bellovin
- Re: [TLS] Re: Review of draft-ietf-tls-openpgp-ke… Eric Rescorla
- [TLS] Re: Review of draft-ietf-tls-openpgp-keys-08 Simon Josefsson
- [TLS] Re: Review of draft-ietf-tls-openpgp-keys-08 Eric Rescorla
- [TLS] Re: Review of draft-ietf-tls-openpgp-keys-08 Simon Josefsson
- [TLS] Re: Review of draft-ietf-tls-openpgp-keys-08 Eric Rescorla
- [TLS] Re: Review of draft-ietf-tls-openpgp-keys-08 Simon Josefsson
- RE: [TLS] Re: Review of draft-ietf-tls-openpgp-ke… Pasi.Eronen
- RE: [TLS] Review of draft-ietf-tls-openpgp-keys-08 Pasi.Eronen
- Re: [TLS] Review of draft-ietf-tls-openpgp-keys-08 Nikos Mavrogiannopoulos