Return-Path: <scott.rose@nist.gov>
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 D894712EBD2
 for <dcrup@ietfa.amsl.com>; Fri,  2 Jun 2017 07:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001,
 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 gyhLo4xjf8GL for <dcrup@ietfa.amsl.com>;
 Fri,  2 Jun 2017 07:47:08 -0700 (PDT)
Received: from wsget1.nist.gov (wsget1.nist.gov [IPv6:2610:20:6005:13::150])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 46CA312EBD5
 for <dcrup@ietf.org>; Fri,  2 Jun 2017 07:47:08 -0700 (PDT)
Received: from WSGHUB1.xchange.nist.gov (129.6.42.34) by wsget1.nist.gov
 (129.6.13.150) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 2 Jun
 2017 10:46:52 -0400
Received: from postmark.nist.gov (129.6.16.94) by mail-g.nist.gov
 (129.6.42.33) with Microsoft SMTP Server id 14.3.319.2; Fri, 2 Jun 2017
 10:47:06 -0400
Received: from [129.6.140.7] ([129.6.140.7])	by postmark.nist.gov
 (8.13.8/8.13.1) with ESMTP id v52EkxfX009809	for <dcrup@ietf.org>; Fri, 2 Jun
 2017 10:46:59 -0400
From: "Rose, Scott" <scott.rose@nist.gov>
To: <dcrup@ietf.org>
Date: Fri, 2 Jun 2017 10:46:59 -0400
Message-ID: <2D2E54E1-23A0-4470-85AD-F861770B10B1@nist.gov>
In-Reply-To: <149641449629.31859.14544571541039601302@ietfa.amsl.com>
References: <149641449629.31859.14544571541039601302@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5347)
X-NIST-MailScanner-Information: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/Kw9FnbaXlXLsikKOajefR6mh-No>
Subject: Re: [Dcrup] I-D Action: draft-ietf-dcrup-dkim-ecc-00.txt
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: Fri, 02 Jun 2017 14:47:11 -0000

Updated to reflect WG status.  Also made the following changes:

1. Reduced new algorithms list to just one (ECDSA P=256).

2. Included revised definition of key:value pairs for DKIM keys and 
signatures.  One thing I thought about: should the “k=“ in keys to 
be mandatory now that RSA isn’t the only algorithm?  Or leave the 
default as is, so that anyone using ECDSA must use the “k=“ tag to 
signal its use?

3. Just noticed that the format is mess up for the ABNF notation - dang. 
  Will fix that.

Scott

On 2 Jun 2017, at 10:41, internet-drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the DKIM Crypto Update of the IETF.
>
>         Title           : Defining Elliptic Curve Cryptography 
> Algorithms for use with DKIM
>         Author          : Scott Rose
> 	Filename        : draft-ietf-dcrup-dkim-ecc-00.txt
> 	Pages           : 7
> 	Date            : 2017-06-02
>
> Abstract:
>    DomainKeys Identified Mail (DKIM) uses digital signature to 
> associate
>    a message with a given sending domain.  Currently, there is only 
> one
>    cryptography algorithm defined for use with DKIM (RSA).  This
>    document defines four new elliptic curve cryptography algorithms 
> for
>    use with DKIM.  This will allow for algorithm agility if a weakness
>    is found in RSA, and allows for smaller key length to provide the
>    same digital signature strength.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dcrup-dkim-ecc/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dcrup-dkim-ecc-00
> https://datatracker.ietf.org/doc/html/draft-ietf-dcrup-dkim-ecc-00
>
>
> Please note that it may take a couple of minutes from the time of 
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> Dcrup mailing list
> Dcrup@ietf.org
> https://www.ietf.org/mailman/listinfo/dcrup


===================================
Scott Rose
NIST ITL
scott.rose@nist.gov
+1-301-975-8439
GV: +1-571-249-3671
===================================

