Re: [Dcrup] AD review of draft-ietf-dcrup-dkim-usage-04.txt

Scott Kitterman <sklist@kitterman.com> Thu, 02 November 2017 18:38 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 3AE8E13F59F for <dcrup@ietfa.amsl.com>; Thu, 2 Nov 2017 11:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 gOEBV9-Q19Da for <dcrup@ietfa.amsl.com>; Thu, 2 Nov 2017 11:38:51 -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 7886E137832 for <dcrup@ietf.org>; Thu, 2 Nov 2017 11:38:51 -0700 (PDT)
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 ESMTPS id 86F9DC400B7 for <dcrup@ietf.org>; Thu, 2 Nov 2017 13:38:49 -0500 (CDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dcrup@ietf.org
Date: Thu, 02 Nov 2017 14:01:08 -0400
Message-ID: <7977231.PulXPLHMLE@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-133-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <1509635295.3915594.1159426944.0FC7FF67@webmail.messagingengine.com>
References: <1504117534.496823.1090155768.0E7DA2E2@webmail.messagingengine.com> <CAL0qLwY-UcZdmR4=kWP8g2pJagskQLfoPJX9ajpSKE48J8-r-w@mail.gmail.com> <1509635295.3915594.1159426944.0FC7FF67@webmail.messagingengine.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/Z-BXaEBddraiLcz1DgLXu3OPMNs>
Subject: Re: [Dcrup] AD review of draft-ietf-dcrup-dkim-usage-04.txt
X-BeenThere: dcrup@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 02 Nov 2017 18:38:53 -0000

On Thursday, November 02, 2017 03:08:15 PM Alexey Melnikov wrote:
> On Thu, Nov 2, 2017, at 01:29 AM, Murray S. Kucherawy wrote:
> > On Wed, Nov 1, 2017 at 6:12 PM, Scott Kitterman
> > <sklist@kitterman.com> wrote:>> That would leave the new language about
> > permanently failing tied only> 
> >> to rsa-sha1 and not also in key size. I would either split the second
> >> paragraph of 4.1 to put with insufficient key size in 4.2 (DKIM
> >> signatures signed with insufficient key sizes (currently rsa-sha256
> >> with less than 1024 bits) have permanently failed evaluation as
> >> discussed in [RFC6376] Section 3.9
> >> <https://tools.ietf.org/html/rfc6376#section-3.9>) or move the whole
> >> paragraph up into section 4.>
> > 
> > I think I like the first option.  Anyone else (and Alexey in
> > particular)?
> 
> Either is fine with me.

OK.  I'll have an update shortly.  There's also a word missing in Appendix A 
that I'll fix at the same time (this was reported off-list after I uploaded 
-05):

Appendix A, Line 194:

READS:
Thanks to John Levine his DCRUP work that was the source for much of

SHOULD READ:
Thanks to John Levine for his DCRUP work that was the source for much of

Scott K