Re: [Dcrup] last call updated draft-ietf-dcrup-dkim-crypto-13

Russ Housley <housley@vigilsec.com> Mon, 18 June 2018 21:39 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: dcrup@ietfa.amsl.com
Delivered-To: dcrup@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B561129C6B for <dcrup@ietfa.amsl.com>; Mon, 18 Jun 2018 14:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
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 nM-zp0wmCJlp for <dcrup@ietfa.amsl.com>; Mon, 18 Jun 2018 14:38:57 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AACD8130EA0 for <dcrup@ietf.org>; Mon, 18 Jun 2018 14:38:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 8F1BA300681 for <dcrup@ietf.org>; Mon, 18 Jun 2018 17:38:55 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Hr-Nvk7qWnKv for <dcrup@ietf.org>; Mon, 18 Jun 2018 17:38:54 -0400 (EDT)
Received: from a860b60074bd.home (pool-71-127-50-4.washdc.fios.verizon.net [71.127.50.4]) by mail.smeinc.net (Postfix) with ESMTPSA id 18F5E30025C; Mon, 18 Jun 2018 17:38:54 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <33998159.vzdTK0rSvT@kitterma-e6430>
Date: Mon, 18 Jun 2018 17:38:55 -0400
Cc: dcrup@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <1363D217-5AD7-4034-A3E0-AFE3B632795E@vigilsec.com>
References: <152873414342.2872.16681801090252484956@ietfa.amsl.com> <alpine.OSX.2.21.1806152019090.6903@ary.qy> <D4F597BC-2652-47DC-A71A-85545D0C1254@vigilsec.com> <33998159.vzdTK0rSvT@kitterma-e6430>
To: Scott Kitterman <sklist@kitterman.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/OzzdJdtYWiu2KJgAXN5HU5D1O3s>
Subject: Re: [Dcrup] last call updated draft-ietf-dcrup-dkim-crypto-13
X-BeenThere: dcrup@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: DKIM Crypto Update <dcrup.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dcrup>, <mailto:dcrup-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dcrup/>
List-Post: <mailto:dcrup@ietf.org>
List-Help: <mailto:dcrup-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dcrup>, <mailto:dcrup-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2018 21:39:11 -0000

Frankly, I missed it.  The intro text to A.3 provides no hint that the example is showing two signatures using different algorithms.

The text is repeated below so that other readers do not need to look it up.

Russ

= = = = = = = =

A.3.  Signed Message

   The text in each line of the message starts at the first position
   except for the continuation lines on the DKIM-Signature headers which
   start with a single space.  A blank line follows the "Joe." line.

   DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed;
    d=football.example.com; i=@football.example.com;
    q=dns/txt; s=brisbane; t=1528637909; h=from : to :
    subject : date : message-id : from : subject : date;
    bh=2jUSOH9NhtVGCQWNr9BrIAPreKQjO6Sn7XIkfJVOzv8=;
    b=/gCrinpcQOoIfuHNQIbq4pgh9kyIK3AQUdt9OdqQehSwhEIug4D11Bus
    Fa3bT3FY5OsU7ZbnKELq+eXdp1Q1Dw==
   DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
    d=football.example.com; i=@football.example.com;
    q=dns/txt; s=test; t=1528637909; h=from : to : subject :
    date : message-id : from : subject : date;
    bh=2jUSOH9NhtVGCQWNr9BrIAPreKQjO6Sn7XIkfJVOzv8=;
    b=F45dVWDfMbQDGHJFlXUNB2HKfbCeLRyhDXgFpEL8GwpsRe0IeIixNTe3
    DhCVlUrSjV4BwcVcOF6+FF3Zo9Rpo1tFOeS9mPYQTnGdaSGsgeefOsk2Jz
    dA+L10TeYt9BgDfQNZtKdN1WO//KgIqXP7OdEFE4LjFYNcUxZQ4FADY+8=
   From: Joe SixPack <joe@football.example.com>
   To: Suzie Q <suzie@shopping.example.net>
   Subject: Is dinner ready?
   Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)
   Message-ID: <20030712040037.46341.5F8J@football.example.com>

   Hi.

   We lost the game.  Are you hungry yet?

   Joe.



> On Jun 18, 2018, at 4:37 PM, Scott Kitterman <sklist@kitterman.com> wrote:
> 
> I think we have that in the current revision in Appendix A.3.  Do we need to 
> specifically refer to that in Section 6?
> 
> Scott K
> 
> On Monday, June 18, 2018 04:23:09 PM Russ Housley wrote:
>> John:
>> 
>> How hard would it be to expand section 6 to include an example of two
>> selectors being used, one with RSA and one with ed25519?  If it is pretty
>> easy, I think it would help the reader.
>> 
>> Russ
>> 
>>> On Jun 15, 2018, at 8:19 PM, John R. Levine <johnl@iecc.com> wrote:
>>> 
>>> I think the -13 addresses the last call comments.
>>> 
>>> Regards,
>>> John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for
>>> Dummies", Please consider the environment before reading this e-mail.
>>> https://jl.ly
>>> 
>>> _______________________________________________
>>> Dcrup mailing list
>>> Dcrup@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dcrup
>> 
>> _______________________________________________
>> Dcrup mailing list
>> Dcrup@ietf.org
>> https://www.ietf.org/mailman/listinfo/dcrup
> 
> _______________________________________________
> Dcrup mailing list
> Dcrup@ietf.org
> https://www.ietf.org/mailman/listinfo/dcrup