IETF Logo Mail Archive

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

Andrew Ayer <agwa@andrewayer.name> Wed, 14 December 2016 00:01 UTC

Return-Path: <agwa@andrewayer.name>
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 BD85F129C95 for <trans@ietfa.amsl.com>; Tue, 13 Dec 2016 16:01:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=andrewayer.name
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 3iUCuf3ny7qv for <trans@ietfa.amsl.com>; Tue, 13 Dec 2016 16:01:30 -0800 (PST)
Received: from alcazar.beanwood.com (alcazar.beanwood.com [IPv6:2600:3c00:e000:6c::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63947129C9A for <trans@ietf.org>; Tue, 13 Dec 2016 15:59:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=andrewayer.name; s=beanwood20160511; t=1481673558; bh=123AOJBauCQakmYpuOidaeKXxXqJL516l19MKZpypFo=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=CE4yM2FNA0rSe11tJ4viw/OeQqgnDpo5HJRGvPmklIygC8OuSRiert4OGbn8kMAoe Ol0zNNls3kXW1nScdYQU9i2wKF4cPKl2JbpmrZFYi/J0BsgVLcIAc6BpOQp+7Y/72o cwpg5zVMzeWy+1aZrjHsuoq9qwfBTYnxQIi2Ax9hcZqqzPixuliiktM6azX/Cg+AvM Hvt+lBa9SSSN6PClf/6p3MEHeSB1OqB5LiomfbRbRfKJxAGa4jjd8Ot4J0sdp2Qnk8 0L4EzXpFmIuB4b0W98SH5abNH9xWTjpquOg9q3O3/ytsnOpwkInkbRXdzRR9S8eT3R Y2YfPxeP/dGYg==
Date: Tue, 13 Dec 2016 15:59:17 -0800
From: Andrew Ayer <agwa@andrewayer.name>
To: Eran Messeri <eranm@google.com>
Message-Id: <20161213155917.195a6b88a726c74cc320d7df@andrewayer.name>
In-Reply-To: <CALzYgEdBHz5XaqXzPH5rThoJYkrfmViGOCG8soechR1HE9SJfA@mail.gmail.com>
References: <CALzYgEce25Z7tSz6T+kmFQCA+xbgO0ECknV6nE1m55-pey3vrQ@mail.gmail.com> <CALzYgEf74uLn00GWDt0ccHVuPRdJOpBNfGBKGcB2BWML23s3YQ@mail.gmail.com> <06cb8a34-7067-95af-708d-b2c2be261a1d@comodo.com> <alpine.LRH.2.20.1612122034310.31017@bofh.nohats.ca> <CALzYgEdBHz5XaqXzPH5rThoJYkrfmViGOCG8soechR1HE9SJfA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/fNpLnbB18hQX4IRxSnhTnDX4_K4>
Cc: Paul Wouters <paul@nohats.ca>, "trans@ietf.org" <trans@ietf.org>, Rob Stradling <rob.stradling@comodo.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
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:01:32 -0000

On Tue, 13 Dec 2016 14:32:04 +0000
Eran Messeri <eranm@google.com> wrote:

> * For Hash Algorithm repository, specify "Expert Review" guiding the
> Expert to make sure the proposed hash algorithm has public
> specification and does not suffer from known preimage attacks.

The hash algorithm also needs collision resistance.

How precise does the guidance need to be?  "Not suffer from known
preimage attacks" wouldn't be construed as forbidding SHA-2 because
there are some very expensive preimage attacks on some rounds, would it?

Arguably, "suitable for use as a cryptographic hash function" covers
both preimage and collision resistance, and leaves it to the expert's
discretion what attacks are worth worrying about.  Would leaving it at
this provide sufficient guidance?

Regards,
Andrew

v2.23.0 | Report a Bug | By Email