IETF Logo Mail Archive

Re: [dispatch] Updating DKIM for stronger crypto

Cullen Jennings <fluffy@iii.ca> Fri, 10 February 2017 20:50 UTC

Return-Path: <fluffy@iii.ca>
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 D096F129BDF for <dispatch@ietfa.amsl.com>; Fri, 10 Feb 2017 12:50:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level:
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 4uQlBf0MeH2g for <dispatch@ietfa.amsl.com>; Fri, 10 Feb 2017 12:50:51 -0800 (PST)
Received: from smtp144.dfw.emailsrvr.com (smtp144.dfw.emailsrvr.com [67.192.241.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9C27129BDB for <dispatch@ietf.org>; Fri, 10 Feb 2017 12:50:50 -0800 (PST)
Received: from smtp23.relay.dfw1a.emailsrvr.com (localhost [127.0.0.1]) by smtp23.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 3C988E0358; Fri, 10 Feb 2017 15:50:50 -0500 (EST)
X-Auth-ID: fluffy@iii.ca
Received: by smtp23.relay.dfw1a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id B373CE033A; Fri, 10 Feb 2017 15:50:49 -0500 (EST)
X-Sender-Id: fluffy@iii.ca
Received: from [192.168.4.119] ([UNAVAILABLE]. [128.107.241.188]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Fri, 10 Feb 2017 15:50:50 -0500
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <20170206020826.1108.qmail@ary.lan>
Date: Fri, 10 Feb 2017 13:50:48 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <29F6F66C-F14F-402A-83D4-CAC70841667E@iii.ca>
References: <20170206020826.1108.qmail@ary.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/i8O2D__7tZQVUMa6pPKC4pV6LEg>
Cc: DISPATCH list <dispatch@ietf.org>
Subject: Re: [dispatch] Updating DKIM for stronger crypto
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 10 Feb 2017 20:50:52 -0000

The Chairs and ADs discussed this today and we plan to allocate some agenda time for it at IETF 98. At the meeting we can try and figure out best way to dispatch this. 

It seems like a mini WG or possibly AD sponsor by ART or SEC AD are within the range of possibilities we should consider for how to move the work forward.

v2.23.0 | Report a Bug | By Email