Re: [dispatch] Updating DKIM for stronger crypto

Martin Thomson <martin.thomson@gmail.com> Wed, 22 March 2017 02:12 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7706C131101 for <dispatch@ietfa.amsl.com>; Tue, 21 Mar 2017 19:12:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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] 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 OWRXE7Pyxwla for <dispatch@ietfa.amsl.com>; Tue, 21 Mar 2017 19:12:32 -0700 (PDT)
Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::231]) (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 5EB8F129659 for <dispatch@ietf.org>; Tue, 21 Mar 2017 19:12:28 -0700 (PDT)
Received: by mail-qt0-x231.google.com with SMTP id n21so144871650qta.1 for <dispatch@ietf.org>; Tue, 21 Mar 2017 19:12:28 -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=+MigjAlgmkFWZb7TZig249aefZYcDhgA7x0ouV3jk8A=; b=qQSpsQO9FIS+YhMKnU9BbZBFPwhdRuWnys65eg2MAfYjBUBN9UCPUjcQIWptfPlLkS iCZT5puWdlBg+WwpTeaXr27LUHyLDNVeXk5laXTxOFgR9Pg6n3wSn15edntPtf/0hQqw oG8PbZbpqSBY4dm+Jvt9boECLzMzg//+HcO1R87yCU0vyLKZntQRd2R0Li+SyXyNxBTB JW35VY9u6PSKbWmf1YMI/jIiJuYDV3rcAgqYEZT07qbpTiy7fNIh/Lp+ooiVtLVnQzKn gTArvteTRIeEiz9BocUuwTEweKOw+O0dQ7e5kViav5VagY8yQ2DC1JvKh7vT7/yVqzIp Y/kw==
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=+MigjAlgmkFWZb7TZig249aefZYcDhgA7x0ouV3jk8A=; b=W6ks9XnH+T/KS6dGFFqJK3twz83rCgilDsysylK2QLUCwQa+NAPePDkPuS5KMUdAwR vEiCXeVpq/MNQv9jxUkvjvQHanfKDlI28aVZ1PlNJoCE9202QJSKFN3KfJEqK25S7r5I jwYpW6+IDls7/Q/lD8VdUihD7TurgrCY5P+TzvS8HJqOyyoygO/4P7tblfuFHNFiGB/9 ktVktEN4+8NgeGpexnXeGR+2bP0BrmejzBNuf9DTZlO6chpDADZHl/X6tUdOPMGzWNCQ eK2qqRhQUFiN2dcMsLRiCHddkQ9JVyZvApeCbZHK7LTLkNwm9tPdq4dU7yU9sfHLgqoy rp8w==
X-Gm-Message-State: AFeK/H3OLsn87cwr6dSKh49wucWIqeizsFXY/+1jYmFfUV8jcGTnirX1ZkQaDoUPvj2seNrSSSKAOxytMeWWKg==
X-Received: by 10.237.41.100 with SMTP id s91mr38465082qtd.143.1490148747603; Tue, 21 Mar 2017 19:12:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.27.194 with HTTP; Tue, 21 Mar 2017 19:12:27 -0700 (PDT)
In-Reply-To: <alpine.OSX.2.20.1703210930150.22945@ary.qy>
References: <20170206020826.1108.qmail@ary.lan> <29F6F66C-F14F-402A-83D4-CAC70841667E@iii.ca> <CABkgnnVX3rgMY0ZGmf_xcQ+zgGtCMaZcsymyW2BCWBeAKm_CqQ@mail.gmail.com> <b7f8064f-d91d-6c16-b984-fd20014c7975@cs.tcd.ie> <CABcZeBObvXkFd2G7st1iywMjVr-JWvzMrV46zCXZ251LHiddGA@mail.gmail.com> <alpine.OSX.2.20.1703210930150.22945@ary.qy>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 22 Mar 2017 13:12:27 +1100
Message-ID: <CABkgnnVB3ztkaN3YuQbaVG4znh_3XNu_SWN+9KNmZ66zVF-R+g@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Cc: DISPATCH list <dispatch@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/ea1kpFLWuJJxprNz8_6PoAPIvO4>
Subject: Re: [dispatch] Updating DKIM for stronger crypto
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Mar 2017 02:12:33 -0000

On 22 March 2017 at 01:05, John R Levine <johnl@taugh.com> wrote:
> Given the difficulty of opening up specs, if we're going to do anything I'd
> like to both add the new algorithm and the option to publish key hashes.


This sounds fine, though I'd disagree with the premise.  I'm sure that
you can write an extension specification that doesn't even have to
update DKIM.  It just says, you can implement this in addition to DKIM
and it makes the keys bigger and better.