Re: [Trans] Policy for adding to IANA registries requested in 6962-bis

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 14 December 2016 00:55 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 685F51295FA for <trans@ietfa.amsl.com>; Tue, 13 Dec 2016 16:55:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.197
X-Spam-Level:
X-Spam-Status: No, score=-7.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ams1l5gRSNID for <trans@ietfa.amsl.com>; Tue, 13 Dec 2016 16:55:53 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 107AF129489 for <trans@ietf.org>; Tue, 13 Dec 2016 16:48:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id AFF6FBE47; Wed, 14 Dec 2016 00:48:27 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RdSvepKGaQ3Z; Wed, 14 Dec 2016 00:48:26 +0000 (GMT)
Received: from [10.87.48.210] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id E5137BE39; Wed, 14 Dec 2016 00:48:25 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1481676506; bh=sUaVVnrPjq//vcDkbuvo8mpvlYu+oJGrh5vQSgK+Lb4=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=lE+nMmQ8Z3WaS7eyPn3V+HrEjFIjj41tEVA2GDIHmFNePPXOVKSnJRYp1fckv6DD2 70vpBrs1LS0/ix559v87HuPWMHkpTIAI5DIPdFF1cLrkJZwirxebdOjdUr+v++r6Qa 1l6ygXYKZMyFH9FAyHURChL3U8+ECjkQA5Xxt2vE=
To: Bill Frantz <frantz@pwpconsult.com>, Andrew Ayer <agwa@andrewayer.name>
References: <r470Ps-10121i-019CF7E50A5744F38D78ABB70C8C48F5@Williams-MacBook-Pro.local>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <5e6de6cc-4d3a-d380-d923-8933f51d9a0d@cs.tcd.ie>
Date: Wed, 14 Dec 2016 00:48:26 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <r470Ps-10121i-019CF7E50A5744F38D78ABB70C8C48F5@Williams-MacBook-Pro.local>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms020007050008020300030901"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/7Udc4P4XxEztAtRbyarRgjzSs2E>
Cc: Eran Messeri <eranm@google.com>, trans@ietf.org
Subject: Re: [Trans] Policy for adding to IANA registries requested in 6962-bis
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Dec 2016 00:55:56 -0000

Hiya,

Just a comment from the sidelines...

On 14/12/16 00:20, Bill Frantz wrote:
> 
> "Suitable for use as a cryptographic hash with no known preimage or
> collision attacks. These attacks can damage the integrity of the log."

If taking this approach it might be useful to consider the
duration for which any such properties are desired, e.g. to
consider how that duration maps to hashes used in certificate
signing would seem like a natural enough thing to do. And it
might even be the case that such consideration provides a way
to avoid a separate registry maybe, not sure.

S.