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

Scott Kitterman <sklist@kitterman.com> Mon, 18 June 2018 21:45 UTC

Return-Path: <sklist@kitterman.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 C9087130EA0 for <dcrup@ietfa.amsl.com>; Mon, 18 Jun 2018 14:45:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=Y7L26+Pb; dkim=pass (2048-bit key) header.d=kitterman.com header.b=S0HLL1MM
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 ugEiFL1Bq0Tg for <dcrup@ietfa.amsl.com>; Mon, 18 Jun 2018 14:45:50 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0C6A129C6B for <dcrup@ietf.org>; Mon, 18 Jun 2018 14:45:50 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201803e; t=1529358348; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from : subject : date; bh=ami++1W/J6apTaRFrarePpWbjaOyciI6yU04VyuIECg=; b=Y7L26+PbFYoTuWzPNPXvyzE06Ahw/0EZdxh+fCk5DHDNzklDXjMqUca2 wciDX1KfMk19x+NR5lqMFlSgCenFDA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201803r; t=1529358348; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from : subject : date; bh=ami++1W/J6apTaRFrarePpWbjaOyciI6yU04VyuIECg=; b=S0HLL1MMjcMETMNrN4AstRYfPVcsg/DifAzKYj7/gY92BrvwJn5n5FjW JER+evlDRTyeXEIEULLXbK6rgkhWUCvASJod4F48nbAKvVjSd4Zs0/sQ4i XiEKd/a6b7nOZ2+7Gevsvl0LSYYO1cf+mVEsEpshfn99MSer+6M+lBOcuh qiJgtHLuHF0n3NLfpc9LK4+4QG7eIYKem7IqKftSQTs7oPmXQvwmMWkDxv TUxAGtg9us7DELQ56NkniUZfqugwKRgAT3OL+X13tUZUSImzFNv9PQcC0c pGQzKKxIBcTOPfHkPe1c1w2igICoBOLZnlwJfwGdXQWEwOT7ldx42w==
Received: from kitterma-e6430.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 9FD3FC40079 for <dcrup@ietf.org>; Mon, 18 Jun 2018 16:45:48 -0500 (CDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dcrup@ietf.org
Date: Mon, 18 Jun 2018 17:45:48 -0400
Message-ID: <3034956.vqE5bSIrEz@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-147-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <1363D217-5AD7-4034-A3E0-AFE3B632795E@vigilsec.com>
References: <152873414342.2872.16681801090252484956@ietfa.amsl.com> <33998159.vzdTK0rSvT@kitterma-e6430> <1363D217-5AD7-4034-A3E0-AFE3B632795E@vigilsec.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/3aPgr0oYyjCA9wmLVyeU4Msa6L8>
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:45:54 -0000

OK.  Maybe added to the end of the paragraph in section 6:

Current:

6.  Transition Considerations

   For backward compatibility, signers can add multiple signatures that
   use old and new signing algorithms.  Since there can only be a single
   key record in the DNS for each selector, the signatures have to use
   different selectors, although they can use the same d= and i=
   identifiers.

Proposed:

6.  Transition Considerations

   For backward compatibility, signers can add multiple signatures that
   use old and new signing algorithms.  Since there can only be a single
   key record in the DNS for each selector, the signatures have to use
   different selectors, although they can use the same d= and i=
   identifiers.  Appendix A.3 shows an example message signed with both
   ed25519-sha256 and rsa-sha256 with the same d= and i=, but unique
   selectors (s=brisbane and s=test respectively).

Scott K

On Monday, June 18, 2018 05:38:55 PM Russ Housley wrote:
> 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
> 
> _______________________________________________
> Dcrup mailing list
> Dcrup@ietf.org
> https://www.ietf.org/mailman/listinfo/dcrup