Re: [Dcrup] Adam Roach's No Objection on draft-ietf-dcrup-dkim-usage-04: (with COMMENT)

Scott Kitterman <sklist@kitterman.com> Wed, 25 October 2017 04:32 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 A2B0513B10F for <dcrup@ietfa.amsl.com>; Tue, 24 Oct 2017 21:32:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level:
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=kitterman.com
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 Xtpq5tOpDpuk for <dcrup@ietfa.amsl.com>; Tue, 24 Oct 2017 21:32:11 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6620213B0EA for <dcrup@ietf.org>; Tue, 24 Oct 2017 21:32:11 -0700 (PDT)
Received: from kitterma-e6430.localnet (unknown [209.65.111.194]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 2B249C4025F for <dcrup@ietf.org>; Tue, 24 Oct 2017 23:32:07 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2001409; t=1508905927; bh=oVOTgb9sUPmQ24pldFcz8t46P7GCUR0FysNJlCtL7K4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=k3sZoWOpxC2et0ADXCwY6qgiM9oqGOFgmfE8b2qYmvmBuBnAKGN2kKm3QWYiz8D1v f/zgENAzk16GXCiiSUW9zqwJ3T/NrCDHD3MSPE875uNztIKg8s57bgq7EH8VrHnxTL LbZJqcR5Tg35wF0d3y+St2Y9/srjPbqN8uM50IPQ=
From: Scott Kitterman <sklist@kitterman.com>
To: dcrup@ietf.org
Date: Wed, 25 Oct 2017 00:32:05 -0400
Message-ID: <1827464.gt1Kil1zhX@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-133-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <CAL0qLwbKYuffPwyz=zQLQatKpb6d07gsGCJ4wFJLpfSfJavTjA@mail.gmail.com>
References: <150649085207.24995.1867894975380491185.idtracker@ietfa.amsl.com> <CABuGu1pVBARKZBxVR=Sgkb_kB-CuPrHEPqUxZs57HpmABOpi9A@mail.gmail.com> <CAL0qLwbKYuffPwyz=zQLQatKpb6d07gsGCJ4wFJLpfSfJavTjA@mail.gmail.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/2XM42XWiQnha-uw17r1jevmCdvg>
Subject: Re: [Dcrup] Adam Roach's No Objection on draft-ietf-dcrup-dkim-usage-04: (with COMMENT)
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: Wed, 25 Oct 2017 04:32:13 -0000

On Tuesday, October 24, 2017 09:15:05 PM Murray S. Kucherawy wrote:
> On Tue, Oct 24, 2017 at 4:35 PM, Kurt Andersen <kurta@drkurt.com> wrote:
> > In fact I would claim that by the definitions in Section 2.7.1 of RFC7601,
> > 
> >> "policy" is the only option.
> > 
> > Are we talking about before or after this group consigns sha1 to the ash
> > heap?
> 
> Concurrent with.
> 
> Perhaps I'm confused about the sequencing of events that we are discussing.
> 
> > If the original DKIM spec had allowed rsa-md5 and a previous
> > (hypothetical)
> > instance of DCRUP had similarly deprecated MD5, what sort of designation
> > would we expect to be recorded today for such usage?
> 
> The question's never been asked before, so I don't know how to answer
> that.  But I don't think "none" is right unless we also want to contend
> that a DKIM-Signature field with a syntax error in it also warrants a
> "none", which I don't believe is the case.
> 
> -MSK

You've convinced me "none" is not what we want.  I think that your 
hypothetical DKIM signature warrants a "permerror" and that's what we should 
use here.

Scott K