Re: [Dcrup] FW: IETF WG state changed for draft-ietf-dcrup-dkim-usage

"John Levine" <johnl@taugh.com> Sun, 13 August 2017 22:35 UTC

Return-Path: <johnl@taugh.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 D8F6913351B for <dcrup@ietfa.amsl.com>; Sun, 13 Aug 2017 15:35:55 -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 IkpZWdjom4qe for <dcrup@ietfa.amsl.com>; Sun, 13 Aug 2017 15:35:54 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 476B3133519 for <dcrup@ietf.org>; Sun, 13 Aug 2017 15:35:54 -0700 (PDT)
Received: (qmail 40031 invoked from network); 13 Aug 2017 22:35:52 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 13 Aug 2017 22:35:52 -0000
Date: Sun, 13 Aug 2017 22:35:30 -0000
Message-ID: <20170813223530.39855.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dcrup@ietf.org
Cc: sklist@kitterman.com
In-Reply-To: <36659107.dMb7D4c16s@kitterma-e6430>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/YGXYX__fsQmUZ9eGi44rP-LdI8w>
Subject: Re: [Dcrup] FW: IETF WG state changed for draft-ietf-dcrup-dkim-usage
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: Sun, 13 Aug 2017 22:35:56 -0000

In article <36659107.dMb7D4c16s@kitterma-e6430> you write:
>I updated the ABNF in the draft because I think if we are going to kill it, we 
>should kill it absolutely dead.  What is the benefit of retaining obsolete 
>features that are MUST NOT use in the ABNF?

Recognize them and ridicule people who are still using them?

On a slightly more pragmatic note, leaving them in the ABNF makes it
less likely that someone later will add something that conflicts.  I
realize that the chances of adding something else named sha1 are
pretty low, but who knows what strangeness may happen a decade from
now.


R's,
John