RE: [Hash] Charter discussion, round 1

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 22 June 2005 00:15 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dksu4-0003D2-Cw; Tue, 21 Jun 2005 20:15:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dksu2-0003A6-13 for hash@megatron.ietf.org; Tue, 21 Jun 2005 20:15:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29866 for <hash@ietf.org>; Tue, 21 Jun 2005 20:15:36 -0400 (EDT)
Received: from above.proper.com ([208.184.76.39]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DktI3-0003pL-7O for hash@ietf.org; Tue, 21 Jun 2005 20:40:27 -0400
Received: from [165.227.249.220] (dsl2-63-249-92-231.cruzio.com [63.249.92.231]) (authenticated bits=0) by above.proper.com (8.12.11/8.12.9) with ESMTP id j5M0FRKT010505; Tue, 21 Jun 2005 17:15:30 -0700 (PDT) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0623093bbede5b98c918@[165.227.249.220]>
In-Reply-To: <6.2.1.2.2.20050620094732.05d64ba0@mail.binhost.com> <20050617191830.6B39C32735@smtp2.pacifier.net>
References: <6.2.1.2.2.20050616093927.0660b700@mail.binhost.com> <20050617191830.6B39C32735@smtp2.pacifier.net> <6.2.1.2.2.20050620094732.05d64ba0@mail.binhost.com> <20050617191830.6B39C32735@smtp2.pacifier.net>
Date: Tue, 21 Jun 2005 17:15:33 -0700
To: "Jim Schaad" <ietf@augustcellars.com>, "'Russ Housley'" <housley@vigilsec.com>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: RE: [Hash] Charter discussion, round 1
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: hash@ietf.org
X-BeenThere: hash@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: hash.lists.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hash>, <mailto:hash-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/hash>
List-Post: <mailto:hash@lists.ietf.org>
List-Help: <mailto:hash-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hash>, <mailto:hash-request@lists.ietf.org?subject=subscribe>
Sender: hash-bounces@lists.ietf.org
Errors-To: hash-bounces@lists.ietf.org

At 12:20 PM -0700 6/17/05, Jim Schaad wrote:
>  > >3.  I think that adding explicit deliverables for phase 2
>>  could wait, I
>>  >think it must wait until a re-charter for phase 3.
>>
>>  Are you saying that we can do a good job on Phase 2 even if
>>  the participation from the international crypto community is low?
>
>Yes I think so, we are identifying the locations where hash functions are
>being used or are likely to be used in IETF protocols.  We are then
>specifying what prosperities are needed in these situations.  This does not
>seem to be highly reliant on big research issues.

At 10:04 AM -0400 6/20/05, Russ Housley wrote:
>I would like to see more discussion of this point on this mail list 
>and ant the BoF.  You might be able to convince me that we should 
>include Phase 1 and Phase 2 in the first version if the charter.

Remember that this effort is intended to be done in an IETF Working 
Group, and WGs are inherently open to all participants. If we begin 
the work or deciding the criteria that make a good hash without the 
experts from the international crypto community who understand those 
criteria being on-board, the WG will probably tend towards 
non-experts quoting (and misquoting) what they read in the trade 
press.

There is the additional factor that we are just finding out some 
important things about hashes, and have heard very few analyses of 
that new information. Do the discoveries by Wang et. al. only apply 
to collisions? If we wait a year or two, will the crypto community be 
able to extend those into measurable preimage attacks? If so, what 
will we know then?

I'm not saying we need to wait on chartering phase 2, but we should 
certainly not try to rush this based on our limited information.

--Paul Hoffman, Director
--VPN Consortium

_______________________________________________
Hash mailing list
Hash@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/hash