Re: [Dcrup] draft-ietf-dcrup-dkim-usage and document shepherds

Scott Kitterman <sklist@kitterman.com> Mon, 12 June 2017 04: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 04B95129BB2 for <dcrup@ietfa.amsl.com>; Sun, 11 Jun 2017 21:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) 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 8taA6rBzMO8s for <dcrup@ietfa.amsl.com>; Sun, 11 Jun 2017 21:38:32 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AD54129BAE for <dcrup@ietf.org>; Sun, 11 Jun 2017 21:38:32 -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 ESMTPSA id DC229C40236 for <dcrup@ietf.org>; Sun, 11 Jun 2017 23:38:28 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=201409; t=1497242309; bh=/eqkKGTWOQwwFK36Pr1hdVEzqBHh/MnKyRJ58BOyZXU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=LpX4+BeEY1RmNP++ljuZoBouF1pxGZmYWttkmzJVu/dE+9icb0EOZwZnYgCLStiRr z50mAeKL4bowvCVqmQi20W+rbdiO+3Bj+XewyOTvJR0q6x5SNr8l630P2iBVQ0C4Tn HAEPubBJIuVNYuVaY4iPch69Po0zlKHluK1qACz4=
From: Scott Kitterman <sklist@kitterman.com>
To: dcrup@ietf.org
Date: Mon, 12 Jun 2017 00:38:28 -0400
Message-ID: <2034638.szbv6KSWyz@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-119-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <CAL0qLwYx9=_vqsD9=WVLqyXGoOpbTvBwDBHcZMpzdPo8LSv7UQ@mail.gmail.com>
References: <20170610002538.10992.qmail@ary.lan> <CABuGu1o21f-4r4RzSdCLQAJG3ySDajc=BMFsVC9t_CNEz4ut+Q@mail.gmail.com> <CAL0qLwYx9=_vqsD9=WVLqyXGoOpbTvBwDBHcZMpzdPo8LSv7UQ@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/fSrj19yHE1fo5e3bxUZfMxl4aBA>
Subject: Re: [Dcrup] draft-ietf-dcrup-dkim-usage and document shepherds
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: Mon, 12 Jun 2017 04:38:34 -0000

On Sunday, June 11, 2017 08:37:23 PM Murray S. Kucherawy wrote:
> On Sun, Jun 11, 2017 at 11:17 AM, Kurt Andersen <kurta@drkurt.com> wrote:
> > On June 9, 2017 8:25:38 PM EDT, John Levine <johnl@taugh.com> wrote:
> >> . . .it seems kind of premature to me.
> >> 
> >> Why would that matter?  This draft just gets rid of the obsolete cruft.
> >> It clears the deck for adding a new algorithm, but in no way requires we
> >> have that sorted out.
> > 
> > While RFCs do have a cost, can the ADs weigh in on the relative benefits
> > of doing this "sweep the decks clean" first update to be followed by "add
> > more algorithms" vs. bundling it all together?
> 
> Regardless of the answer to that, I don't think we should be in some sort
> of hurry here.
> 
> From where I'm sitting, ARC has other questions it needs to work out before
> this will be a pressing issue for them, and for the most part they just say
> "do what DKIM does" in terms of key management anyway, so when we change
> DKIM, ARC will just follow.

The IETF is five years late with action on this front.  At least.  Whatever is 
happening in this working group, hurrying isn't on the list.

I have no idea what should be in this draft or if it should even exist 
anymore.

I also really don't understand why we have a discussion about if a draft 
should be adopted before a WG adopts it if we just get to re-have the same 
discussion periodically.

Scott K