Re: [Dcrup] new version draft-ietf-dcrup-dkim-crypto-04

"John R Levine" <johnl@taugh.com> Mon, 07 August 2017 15:51 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 E8C9712ECB7 for <dcrup@ietfa.amsl.com>; Mon, 7 Aug 2017 08:51:04 -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=pass (1536-bit key) header.d=iecc.com header.b=nQy7oNN2; dkim=pass (1536-bit key) header.d=taugh.com header.b=S4nFC9zg
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 tEYxEsNsp87A for <dcrup@ietfa.amsl.com>; Mon, 7 Aug 2017 08:51:03 -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 2DECC12EC11 for <dcrup@ietf.org>; Mon, 7 Aug 2017 08:51:03 -0700 (PDT)
Received: (qmail 70902 invoked from network); 7 Aug 2017 15:51:01 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=114f4.59888c65.k1707; bh=FrGc0ZdVdlyy8uFOT4A8UtEH+IVeq7rPelrHsTloTpo=; b=nQy7oNN2xtG9BIa6e1xE7VSD28QVxSg2/SsRe6cB3THK+S/iosOSL2evHib3mnthra9pewtGPyLQ2qGLP9paQWgU9QdmezHgeHMZBHD6BZ1GKy6f9XMpc4VZMM04HyaU7NKbLxrXmVliwr/2jQed5/PH4ow2YHFD6XdCyrNJugDFOWRvkyFeDKhUaUFtfvNIs0Q6zfV9rye//95usNTTz+EJmcDbKQjlmxD8C+pbqYkwNdAMSXYUr3etrqGbKBLV
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=114f4.59888c65.k1707; bh=FrGc0ZdVdlyy8uFOT4A8UtEH+IVeq7rPelrHsTloTpo=; b=S4nFC9zgky8hoP+4OWo2eVoaWU9yZ6I9MA3l4dEjW/hsdOnkXlyLax6iFZA68t59nojeC5lUpiA+EEqk+c1V3+/iC+2qgnSDNPioPjkB/HAP/jJphnnvyZWy+23iT+PScc8Hn0/0kWkkoAITDdks4OfYeDBN12T88O5yVHru+LdepWXVy0zmmw07nqB+QYRRyXmofJwGwG1mjtkwYYbM1B0gjGNyNwx61xP1VNW41FA+Wi7rTQs2qUY+mG9zCAgV
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 07 Aug 2017 15:51:01 -0000
Date: Mon, 07 Aug 2017 11:51:00 -0400
Message-ID: <alpine.OSX.2.21.1708071143450.29177@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: dcrup@ietf.org
In-Reply-To: <CABkgnnV9E3ASo9PpH8M90tzWX-mp2Kdm6kEpejfeeBY3_X=EEg@mail.gmail.com>
References: <alpine.OSX.2.21.1707281410000.7564@ary.qy> <CABkgnnWi6qS6L7mBHfFObMZhP=2C9mpX8sCuM8sx5efD=dX=kQ@mail.gmail.com> <alpine.OSX.2.21.1708062218580.28227@ary.qy> <CABkgnnV9E3ASo9PpH8M90tzWX-mp2Kdm6kEpejfeeBY3_X=EEg@mail.gmail.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/a3Ej_95Qt5KXdTGcG0xMeLtGhcE>
Subject: Re: [Dcrup] new version draft-ietf-dcrup-dkim-crypto-04
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, 07 Aug 2017 15:51:05 -0000

On Mon, 7 Aug 2017, Martin Thomson wrote:
> I don't believe that adding a signature algorithm means that you need
> to update 6376.

Well, OK, but where does all the new ABNF go?

Our plan here is that once this is published, people implement 6376 plus 
this draft plus (or perhaps minus) Scott's anti-SHA1, which tells me that 
these have to update 6376, but in any event, this is a decision for the 
WG or the chairs, not for us.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly