IETF Logo Mail Archive

Re: [Trans] Further comments on RFC 6962

Phillip Hallam-Baker <hallam@gmail.com> Tue, 11 March 2014 15:52 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 598CD1A076C for <trans@ietfa.amsl.com>; Tue, 11 Mar 2014 08:52:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 9IYrSdxEquD3 for <trans@ietfa.amsl.com>; Tue, 11 Mar 2014 08:52:10 -0700 (PDT)
Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id DD07B1A074D for <trans@ietf.org>; Tue, 11 Mar 2014 08:52:09 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id hr13so5872322lab.3 for <trans@ietf.org>; Tue, 11 Mar 2014 08:52:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=b1ai5/bW7ZBcjhZBa8bYn/JPYWLKrpUtbxpBEuKKyrM=; b=wCsueA5DEGmcDZdGfVHuO55K8dTf10mU0X9ebzAU2Ro85Liq+xWPUyaT6t+ZlQ0rgy 3Sd0XQ/2DujUKFJDSTB11TCcjpF3t5t3qkYglVYXEdbM5mr6w4AziLHMb8OSTClxMgqw EECsy4TnI+o1rgcGXYgKWFnmcLmnQvpbao4bdfmqJlmypd929ox5WcKIMpRrPH4e7ofw ZV5jSMozwTeC3ongnZQYnkPozEI1jhY4sVpMlPTV0Lo8qlBowqp5tSLDEYPhVyJuASGP WM4uHz0noIIUDoxmgTXdXDW9JF1OgxTWhNQUzNa+NLzBNng+zeR7VE4ygaLuZ1gdwlyn KINg==
MIME-Version: 1.0
X-Received: by 10.112.170.234 with SMTP id ap10mr26418749lbc.23.1394553123589; Tue, 11 Mar 2014 08:52:03 -0700 (PDT)
Received: by 10.112.37.168 with HTTP; Tue, 11 Mar 2014 08:52:03 -0700 (PDT)
In-Reply-To: <CABrd9SQim3ev=2rsCDXSF5fWqv3+cKf9j-88pQ+4NAaBV9w2PA@mail.gmail.com>
References: <CAMm+LwhpCD9gf_XJUTsKBo3739jOeiHdedqWwi3b0jkeZkSo8w@mail.gmail.com> <CABrd9SQim3ev=2rsCDXSF5fWqv3+cKf9j-88pQ+4NAaBV9w2PA@mail.gmail.com>
Date: Tue, 11 Mar 2014 11:52:03 -0400
Message-ID: <CAMm+LwjGdit7smWasFB5FVAnkjZ_ejnGPKiSPwMNMVQ8fMRT-w@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ben Laurie <benl@google.com>
Content-Type: multipart/alternative; boundary="001a11c373ec8d539d04f456b371"
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/eSlkymxzDYdeZk1tGEnIdmYbzHM
Cc: "trans@ietf.org" <trans@ietf.org>
Subject: Re: [Trans] Further comments on RFC 6962
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 11 Mar 2014 15:52:12 -0000

On Tue, Mar 11, 2014 at 11:46 AM, Ben Laurie <benl@google.com> wrote:

> Since a 6962-bis already exists
> (https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/) it
> would be better to comment on that. But I think all these comments
> apply anyway.
>
> On 10 March 2014 20:58, Phillip Hallam-Baker <hallam@gmail.com> wrote:
>
> > 4) sha256_root_hash.
> >
> > Really? This should be an object that has an algorithm/data pair.
> Encoding
> > the algorithm into the tag is going to make algorithm agility hard.
>
> I agree about the name. Not sure I agree about agility. We don't think
> a log can change algorithm partway through - at least, we don't think
> we want to specify how.
>
> If you want a new algorithm, you start a new log.


But the digest algorithm has to be specified somewhere. Or how does the
client discover what it is?




-- 
Website: http://hallambaker.com/

v2.23.0 | Report a Bug | By Email