Re: [dispatch] Updating DKIM for stronger crypto

Wei Chuang <weihaw@google.com> Thu, 23 March 2017 15:57 UTC

Return-Path: <weihaw@google.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 6FD50126E3A for <dispatch@ietfa.amsl.com>; Thu, 23 Mar 2017 08:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, 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=google.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 KeUzkolJ8JBy for <dispatch@ietfa.amsl.com>; Thu, 23 Mar 2017 08:57:26 -0700 (PDT)
Received: from mail-ot0-x22d.google.com (mail-ot0-x22d.google.com [IPv6:2607:f8b0:4003:c0f::22d]) (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 87BE4126579 for <dispatch@ietf.org>; Thu, 23 Mar 2017 08:57:26 -0700 (PDT)
Received: by mail-ot0-x22d.google.com with SMTP id o24so190027161otb.1 for <dispatch@ietf.org>; Thu, 23 Mar 2017 08:57:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cHqOhK7M9CFZJNeA+KBWtC1E2b8hrIjS/fX+xlyfYt8=; b=pDKaeqxdVnzOBaq1GAy24EsEJ2IkToL6MuMHq3aDq4PI/6LjkH1iq5bUZ+wFO7Q3cn JdWl1iTfF8DZYSxsqKHayPjm0O/7N5S/FPmY8WmQJ4dovB45o7nIpLLIsQ2uoic/9TDr AYTc2yJFkWLBT84R7mDHLfN751tayccj5do+7GfjQQkzjEBsBvBH9+ZHf+xxpBWU08bA BxlsMEqiysi+vgcHIk0kvriUaATii1wZ+NNu+DErmc3P5e9YhtlSODJJgjYcIj/2kISk oV6MxbtHJmM+p781sKR1JsBGW9ynmdXcWPNoAeiaBwxu9iggS/0YJv1VKvaxvgUvtYei DpRw==
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=cHqOhK7M9CFZJNeA+KBWtC1E2b8hrIjS/fX+xlyfYt8=; b=nvy0jgtKkygZB2xrIkh5RhB4ukC+iQGvHE/IjMcnDSw07bY70wDxcjeJO2usnBAd84 p6UnMQf4iwEoZXWNMhK8FeLMgUXVC9rkPbHJ13SnxcVTsmUzuRIB7reh6j4IYK3e+Y77 oa2F946dEgWkfofxOq1fOj7JQVCt1/WbhHzQ99nzx/ZqjF0tmyBQGLg+BFwnyUfQ3hpH 9qy2Rq7vFGoWBH/+9gD+yt5DU1O/I+++AYFGoRJw37LDXpqvWrAE6k8HKMOQ4EzHF77C MYrsI8BaZqcZtIhYtxhQNLeUjEZ43esZc8TEFwnXLe6MrbGWe6xedisS/1OKh+fpF9wN vVYw==
X-Gm-Message-State: AFeK/H1uZWsB/F/JnrFoFcDZt5PLjhYkqiTehI2yZwP8RYYNDu3OW0caIV2Nz5FmhNVdpB/pyYPWM2Xkpz1BWLcE
X-Received: by 10.157.57.228 with SMTP id y91mr1891636otb.33.1490284645816; Thu, 23 Mar 2017 08:57:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.89.206 with HTTP; Thu, 23 Mar 2017 08:57:25 -0700 (PDT)
In-Reply-To: <02a5c817-4b7a-0da8-6ad3-e8a5ac1c441e@cs.tcd.ie>
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> <02a5c817-4b7a-0da8-6ad3-e8a5ac1c441e@cs.tcd.ie>
From: Wei Chuang <weihaw@google.com>
Date: Thu, 23 Mar 2017 08:57:25 -0700
Message-ID: <CAAFsWK3ZTXqj7xhatzyZuotOPdEfkbVWPoB1dpKgFkR4C0q_0A@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: John R Levine <johnl@taugh.com>, DISPATCH list <dispatch@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="001a11406d5af21bfe054b67eefe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/dKpImFcZzzKps2v6IZb7WtgfI6o>
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: Thu, 23 Mar 2017 15:57:28 -0000

I think we (Gmail) would be interested in having this update get published.


-Wei

On Tue, Mar 21, 2017 at 7:32 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
>
> On 21/03/17 14:05, John R Levine wrote:
> >
> > If someone wanted to write something about key lifetimes with a way to
> > poison keys by publishing them, that would be OK with me but I wouldn't
> > want to put it into the DKIM spec.  Currently it offers no advice on key
> > rotation beyond noting that it's possible, and no useful advice on key
> > sizes.
>
> Fully agree - were this to be done it ought be in it's
> own document. Personally, I'd be willing to help with it,
> but only if someone was likely to use it. (And so far,
> nobody is afaik.)
>
> S.
>
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>
>