Re: [dispatch] Draft and Proposed charter for DCRUP
"John R Levine" <johnl@taugh.com> Wed, 29 March 2017 20:55 UTC
Return-Path: <johnl@taugh.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 57B16129982 for <dispatch@ietfa.amsl.com>; Wed, 29 Mar 2017 13:55:22 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=oW8Pkrq8; dkim=pass (1536-bit key) header.d=taugh.com header.b=o5LxCW1a
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 G_azxHg4mpO3 for <dispatch@ietfa.amsl.com>; Wed, 29 Mar 2017 13:55:14 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA6C912997C for <dispatch@ietf.org>; Wed, 29 Mar 2017 13:55:13 -0700 (PDT)
Received: (qmail 76948 invoked from network); 29 Mar 2017 20:55:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type:user-agent; s=12c91.58dc1f30.k1703; bh=NyGm3x5lqu0UpRZpCQhC7SWmzAfBE/3kCFjVIvy8Clw=; b=oW8Pkrq8rCNXRGBuVGBwxeUOpB/5Qnr07arz+5PO/0KL5ILGOjDv8B9qZpFU2e30H1n0jBPZgwNVbcB8EKySQdhVrPbpZXz+6bv9VirrM3qFItaak2me+yfnconXICFuO3RdN55lQrDqlcA+LrL8KilRaN3woPTkDpsuYVtBGnCWCUhfqbERB7cnWz081EbQvLu8/mLcZkKE/HW8QcCkvQl8ov7EDdyfiFa9dnV+tNrtfR0O9nIW50rOnBCWOzYL
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type:user-agent; s=12c91.58dc1f30.k1703; bh=NyGm3x5lqu0UpRZpCQhC7SWmzAfBE/3kCFjVIvy8Clw=; b=o5LxCW1axcIRVTtDVAXFVywSrLAOabkbAJ9CyKQ0HMgB5D5KC4YN6/knC6BYXWicX7XVW5raotioiUrcnhlIyXzYNaYLH8sTnKNWzERqksFbgsEsTB5TRk4s9anzXVOwzkPzeCMrPtaoeDBnyhC8rzAYQLdrMPBK3hEodQ3oLsqpNkHNyNltbj8uKfQijyGkV5dh6sBywkVTvtjF6ta0Z/Mx64Tdhi1iBj7b6eG+gu1Ue/soKtZZdatQ4Rxhlgrs
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 29 Mar 2017 20:55:12 -0000
Date: Wed, 29 Mar 2017 15:55:11 -0500
Message-ID: <alpine.OSX.2.20.1703291554100.6401@dhcp-80f1.meeting.ietf.org>
From: John R Levine <johnl@taugh.com>
To: DISPATCH list <dispatch@ietf.org>
In-Reply-To: <alpine.OSX.2.20.1703271129060.7578@dhcp-80f1.meeting.ietf.org>
References: <alpine.OSX.2.20.1703271129060.7578@dhcp-80f1.meeting.ietf.org>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/3x2MHW40y54O0UJAiv0NbRWbFIg>
Subject: Re: [dispatch] Draft and Proposed charter for DCRUP
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, 29 Mar 2017 20:55:22 -0000
Here's a draft. It needs a lot of work but it at least mentions all the things I think DCRUP would do. Name: draft-levine-dcrup-dkim-crypto Revision: 00 Title: Cryptographic Update to DKIM Document date: 2017-03-29 Group: Individual Submission Pages: 5 URL: https://www.ietf.org/internet-drafts/draft-levine-dcrup-dkim-crypto-00.txt Status: https://datatracker.ietf.org/doc/draft-levine-dcrup-dkim-crypto/ Htmlized: https://tools.ietf.org/html/draft-levine-dcrup-dkim-crypto-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-levine-dcrup-dkim-crypto-00 ---------- On Mon, 27 Mar 2017, John R Levine wrote: > The DKIM Crypto Update (DCRUP) working groupkin is chartered to modify DKIM > to handle more modern cryptographic algorithms and key sizes. DKIM (RFC 6376) > signatures include a tag that identifies the hash algorithm and signing > algorithm used in the signature. The only current algorithm is RSA, with > advice that signing keys should be between 1024 and 2048 bits. While 1024 bit > signatures are common, longer signatures are not because bugs in DNS > provisioning software prevent publishing longer keys as DNS TXT records. > > DCRUP will consider two types of changes to DKIM: additional signing > algorithms such as those based on elliptic curves, and new public key forms, > such as putting the public key in the signature and a hash of the key in the > DNS. It will limit itself to existing implemented algorithms and key forms. > Other changes to DKIM, such as new message canonicalization schemes, are out > of scope. > > The WG's output will be an update to DKIM describing the changes to DKIM > signatures to represent new algorithms or key representations, and to DNS TXT > records containing public key information. > > Milestones: > > * Adopt draft for new algorithms and key forms > > * WG last call > > * Ship it > > Regards, > John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY > Please consider the environment before reading this e-mail. https://jl.ly > > Regards, John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. https://jl.ly
- [dispatch] Proposed charter for DCRUP John R Levine
- Re: [dispatch] Proposed charter for DCRUP Martin Thomson
- Re: [dispatch] Proposed charter for DCRUP Eric Rescorla
- Re: [dispatch] Proposed charter for DCRUP Barry Leiba
- Re: [dispatch] Proposed charter for DCRUP Martin J. Dürst
- Re: [dispatch] Draft and Proposed charter for DCR… John R Levine
- Re: [dispatch] Proposed charter for DCRUP Jim Fenton
- Re: [dispatch] Proposed charter for DCRUP Murray S. Kucherawy
- [dispatch] Proposed charter for DCRUP v0.2 John R Levine
- Re: [dispatch] Proposed charter for DCRUP v0.2 Jim Fenton
- Re: [dispatch] Proposed charter for DCRUP v0.2 Federico Santandrea
- Re: [dispatch] Proposed charter for DCRUP v0.2 John Levine
- Re: [dispatch] Proposed charter for DCRUP v0.2 John Levine
- [dispatch] Proposed charter for DCRUP v0.3 John R Levine
- Re: [dispatch] Proposed charter for DCRUP v0.3 Eric Rescorla
- Re: [dispatch] Proposed charter for DCRUP v0.3 John R Levine
- Re: [dispatch] Proposed charter for DCRUP v0.3 Eric Rescorla
- Re: [dispatch] Proposed charter for DCRUP v0.3 John R Levine