Re: [dispatch] Proposed charter for DCRUP v0.3

Eric Rescorla <ekr@rtfm.com> Fri, 07 April 2017 16:41 UTC

Return-Path: <ekr@rtfm.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 4D6C7129543 for <dispatch@ietfa.amsl.com>; Fri, 7 Apr 2017 09:41:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 9UnMmdadtirn for <dispatch@ietfa.amsl.com>; Fri, 7 Apr 2017 09:41:57 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (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 0C9051294E0 for <dispatch@ietf.org>; Fri, 7 Apr 2017 09:41:57 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id j9so13636216ywj.3 for <dispatch@ietf.org>; Fri, 07 Apr 2017 09:41:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=XdLe9z+EM+5ju2FoFvVfBWGSK9XqeO3b/lQlGwkLK8Y=; b=Gqh/ZULygxNARzbbTTFQAgAVOFVu1nUKvfkotydQOpQ9uQ2fQY4T85bwcbRlNMTSlt Z6yYnRA7uM7Dw3IAEn6F31Oun9BatFP3QhZJn70WbSC2DbqwCf65LDttbyCYBSMCMEFE SCLOTQBTusT9uhRzzNiq20hCYsszXs4TLMigoBafHAyDvLrozUWNpVGvQomQMUiErXGt BW1fomGm78GBQQzq1LFP8sjRpseRfTo4fZknihUCoG48QxWGgDCJXVZCRS6qmEw/fTT8 TojUD/8GoHDzMjQYK559RMfawyjliHOKTZgIYoSc4lk3DeD/zeQ3RtoXQieHKCQODXaP GOQw==
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=XdLe9z+EM+5ju2FoFvVfBWGSK9XqeO3b/lQlGwkLK8Y=; b=X+fzAIIV0WtbUM5QeuNhJJId5Ni3+bSIrdVQyBTsvztqV3X4GB20TGtA0gMfpYCMiq o7AlCLFAI3c5VaAvh1nLeCDqKfSmmNGzVCTZRMhBIYBnyQ/XANEUflFelcpx3OjtjcWH o5vOfdN63sGePnqQg7p3o1fRLFzrV6ZdS9jfIV+0td08Mn6TB/dzftqTJ8SRSLjfJKLl /wESWwPqTfv2EjEr1IBN+kQf7w4U1ULqnIGOzSYs3Ef7fnnNwNz/HBC/fLxuqhVLf+ZM HwqG32lXjjSV8mLmTCU43UYphdVS7SzRiBnCZNogQJVQqQp2Q7/gMHGunStnMxjERlDS w9mg==
X-Gm-Message-State: AN3rC/7vWs5ZWqsI23K7TQ5JkwzirY5SRvwQk5EKVv6N1ME1l6t4s88LSkusmmZpk15CuywEPvFOIkeGvqguJg==
X-Received: by 10.13.250.129 with SMTP id k123mr3174699ywf.276.1491583316133; Fri, 07 Apr 2017 09:41:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.154.210 with HTTP; Fri, 7 Apr 2017 09:41:15 -0700 (PDT)
In-Reply-To: <alpine.OSX.2.20.1704071233050.55219@ary.qy>
References: <alpine.OSX.2.20.1703271129060.7578@dhcp-80f1.meeting.ietf.org> <CAL0qLwZ9pDcOsooOgrpN9feDywc-+=twNtN4BpvOQ6ny68yLfA@mail.gmail.com> <alpine.OSX.2.20.1703301431530.8232@dhcp-80f1.meeting.ietf.org> <alpine.OSX.2.20.1704071233050.55219@ary.qy>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 07 Apr 2017 09:41:15 -0700
Message-ID: <CABcZeBMw+S-O-gX4Yhse+WRQNeV3rR-W4nLCb8KdNf+oBiyMaA@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Cc: DISPATCH list <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c080a1cb61fbe054c964d3f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/zDhot0Zp16x8CFPLH_g2Ne_kGVE>
Subject: Re: [dispatch] Proposed charter for DCRUP v0.3
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: Fri, 07 Apr 2017 16:41:59 -0000

On Fri, Apr 7, 2017 at 9:36 AM, John R Levine <johnl@taugh.com> wrote:

> One last twiddle, make it clear we can deprecate obsolete signing
> algorithms.  I have in mind SHA-1 and RSA-512.
>
> Assuming people are happy with this, what's the next step?
>
> R's,
> John
>
> -----------
>
> The DKIM Crypto Update (DCRUP) working groupkin is chartered to update
> 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 three types of changes to DKIM: additional signing
> algorithms such as those based on elliptic curves, changes to key strength
> advice and requirements including deprecating obsolete algorithms, 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.


Can you clarify "implemented" here? Do you just mean "in wide use by IETF
or otherwise"?

-Ekr



Other changes to DKIM, such as new message canonicalization schemes, are
> out of scope.  The WG will as far as possible avoid changes incompatible
> with deployed DKIM signers and verifiers.
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>