IETF Logo Mail Archive

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

Martin Thomson <martin.thomson@gmail.com> Tue, 08 August 2017 04:46 UTC

Return-Path: <martin.thomson@gmail.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 92A9C126C23 for <dcrup@ietfa.amsl.com>; Mon, 7 Aug 2017 21:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ym6piAeYfJJt for <dcrup@ietfa.amsl.com>; Mon, 7 Aug 2017 21:46:23 -0700 (PDT)
Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBBE51243F3 for <dcrup@ietf.org>; Mon, 7 Aug 2017 21:46:23 -0700 (PDT)
Received: by mail-io0-x22a.google.com with SMTP id g71so9525766ioe.5 for <dcrup@ietf.org>; Mon, 07 Aug 2017 21:46:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5pXB7IAc1Ys8qLtrH0qpW9UtU6nDGqRGg338Fzh7SI0=; b=K7snR/2pmySkhorJyzG696Wh166H3ExHSDRFro2fdEpOzIOW1vTn7+cplcXJ08FVs+ jmaPtlyrX4vvrlOgzn+8AvsiDeK4hAurA+5rgpkKlFSXbRdRFeeIKmGIpEys/U059v5n 26ZQvyFYbChDrNGPDGOSDjlArbQVoDAVJfjnFOiwVmmMYVxCimkIePQNxqXRy7WWFnP/ 7x0Ogj9WBtqRb+Oc1XgLc/I81C28FsfTEXYJy7x+0lEPPUkVpxmg2Jrom5cm1/CySJiN 7geImWNKIGu5DfoEfzUw1J53zeetw0qYNhTGkz8ClEChAvnH/QEVWt16cL21uoA3kvAb UbxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5pXB7IAc1Ys8qLtrH0qpW9UtU6nDGqRGg338Fzh7SI0=; b=LOVoIxIkHprHzicwrkcUjt/PWhnB8Hxnzq4/xpu28e5swVHb9ACOMG1iTw6zGBqSAe /bQbiisSM/aWMN71B2/Y6QXUe/8v66+lqUYzVLuOEV3ctKi6L3lsi1r8kB2R6ouEJR8l DkIligK8S4qrDczAkq6hYDC3YrnKe1z9DwRqakwjCrzJogTyfxXgDjHRnm6oM2h3EI5m cHmLlbTcdSNBtINuwcIkETDB0Cuy1gIGJtUNKkTYs2XxgiRDgc8ePLtamC5YrfNNMgBP hwyRNtWNlBP7UDEP2ECo6D+7Ix7r6SAACRFJKGbAk8/nptbljrPv4tjLxOJpv+TVzIB5 8yvA==
X-Gm-Message-State: AHYfb5gA4FCAzDiz1rr894pmYrqgkyY0LfTXy2DuFlG3FEjHXYkadtZ0 BZlO/FCErFE4MgRc5pUSmPCvwnpz3w==
X-Received: by 10.107.16.196 with SMTP id 65mr2855650ioq.297.1502167582922; Mon, 07 Aug 2017 21:46:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.164.42 with HTTP; Mon, 7 Aug 2017 21:46:22 -0700 (PDT)
In-Reply-To: <alpine.OSX.2.21.1708071143450.29177@ary.qy>
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> <alpine.OSX.2.21.1708071143450.29177@ary.qy>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 08 Aug 2017 14:46:22 +1000
Message-ID: <CABkgnnU3=yyFQ1R_8JW=pN1YYcf-Wq9J4SKhQ5tSDSb3d6vR9Q@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Cc: dcrup@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/MAmWGOHyZY-Nt3ir8OZBh6eAz8k>
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: Tue, 08 Aug 2017 04:46:25 -0000

On 8 August 2017 at 01:51, John R Levine <johnl@taugh.com> wrote:
> 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?

In your draft?

It's not like you can't define new values, but it's also the case that
you don't have to.  The already-defined extension point covers all
valid values.

> 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,

Yes, that's possible without updating 6376.  One problem I've
encountered is that 6376 plus its updates and 6376 plus some other RFC
are materially different to some people.  "Updates" is taken to mean
corrections, and we're not really correcting it - it's perfectly fine.

> but in any event, this is a decision for the WG
> or the chairs, not for us.

I don't think that it's the chairs who decide these things, though I
would certainly respect their views on this.  Ultimately, it's a
community-consensus thing.

v2.23.0 | Report a Bug | By Email