IETF Logo Mail Archive

Re: [Dcrup] draft-ietf-dcrup-dkim-usage and document shepherds

Scott Kitterman <sklist@kitterman.com> Sat, 10 June 2017 02:14 UTC

Return-Path: <sklist@kitterman.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 5A476126CD6 for <dcrup@ietfa.amsl.com>; Fri, 9 Jun 2017 19:14:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=kitterman.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 ejadxdZWwcUy for <dcrup@ietfa.amsl.com>; Fri, 9 Jun 2017 19:14:35 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8788D126C7A for <dcrup@ietf.org>; Fri, 9 Jun 2017 19:14:35 -0700 (PDT)
Received: from [10.240.183.25] (mobile-166-171-59-202.mycingular.net [166.171.59.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 99915C402C5; Fri, 9 Jun 2017 21:14:31 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=201409; t=1497060871; bh=pVMAaMmcCVTGYzo2E7inD16hwVSveTRMaV/fNCa/hqM=; h=Date:In-Reply-To:References:Subject:To:From:From; b=Y3PpUEL6Q22Z8mx++k6h5uFhYyXxQZOUa2rgruv60d+uvXu8CKIHeGm8n67B9RPca 58vwi3WzAhIj7HFEO7SfWenktE7Ds03E6uownzGuZjf+Mxh9Rt+//D0USkar8+XVPN HBiGmV8pJsiDn9TDQiIoCF+wq76vuU/M0bc3cpkU=
Date: Sat, 10 Jun 2017 02:14:29 +0000
In-Reply-To: <20170610002538.10992.qmail@ary.lan>
References: <20170610002538.10992.qmail@ary.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: dcrup@ietf.org
From: Scott Kitterman <sklist@kitterman.com>
Message-ID: <CBFF8363-08F6-419E-AB24-D26137627C76@kitterman.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/U_XKPW0WsqU9sdHXTt46R061AnI>
Subject: Re: [Dcrup] draft-ietf-dcrup-dkim-usage and document shepherds
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: Sat, 10 Jun 2017 02:14:37 -0000


On June 9, 2017 8:25:38 PM EDT, John Levine <johnl@taugh.com> wrote:
>In article
><CAL0qLwaGzfw_s8wqGTNEyVc+B1u7b4ayM2NgYfuTuksLE9x_nw@mail.gmail.com>
>you write:
>>It's been suggested that draft-ietf-dcrup-dkim-usage is ready for
>Working
>>Group Last Call, ...
>
>Given that we are nowhere close to deciding what elliptic algorithm(s)
>to add, it seems kind of premature to me.

Why would that matter?  This draft just gets rid of the obsolete cruft.  It clears the deck for adding a new algorithm, but in no way requires we have that sorted out.

Scott K

v2.27.8 | Report a Bug | By Email | System Status