Re: [Dcrup] Is there anything this WG wants to do not yet in draft-ietf-dcrup-dkim-crypto-01 ?
Scott Kitterman <sklist@kitterman.com> Tue, 20 June 2017 19:28 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 1F9EF131613 for <dcrup@ietfa.amsl.com>; Tue, 20 Jun 2017 12:28:23 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 gQF6scRUHy6m for <dcrup@ietfa.amsl.com>; Tue, 20 Jun 2017 12:28:21 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB8A813160B for <dcrup@ietf.org>; Tue, 20 Jun 2017 12:28:21 -0700 (PDT)
Received: from kitterma-e6430.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id B61A7C400E6 for <dcrup@ietf.org>; Tue, 20 Jun 2017 14:28:20 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=201409; t=1497986900; bh=RyuvnOmN0iKFD30wWMy76K5EDeKEHQA+FsspJ26mbyE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Hb/xGz3PJa98A9C0JpHlT+pw0//KlRdi39vLMDAullB3oc3a0x8cJ5t/AQj181rvl aK2P94/Edpsqx4wb6EKxr5AR6sGNcqssUN0ltmM/XF7rpHy5nZpmsyGZsGT0fa0N10 i1RvHF64BZnCtQQWN0balawkFUTdrJ5TgRgRgRAc=
From: Scott Kitterman <sklist@kitterman.com>
To: dcrup@ietf.org
Date: Tue, 20 Jun 2017 15:28:19 -0400
Message-ID: <10345013.0xW9ERPpmE@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-119-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <20170619205309.10839.qmail@ary.lan>
References: <20170619205309.10839.qmail@ary.lan>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/mY_KS_gjJv4JtDB_GqJeCuQZN1c>
Subject: Re: [Dcrup] Is there anything this WG wants to do not yet in draft-ietf-dcrup-dkim-crypto-01 ?
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: Tue, 20 Jun 2017 19:28:23 -0000
On Monday, June 19, 2017 08:53:09 PM John Levine wrote: > Not to nag or anything, but I think this draft addresses everything in the > WG's charter, assuming the charter is adjusted to deprecate SHA-1. > > Could people take a look and see if you agree? If so we could move it to > last call and be within hailing distance of wrapping things up. > > >* new algorithm is now EdDSA, tags updated appropriately > > > >* sha1 hash is moved to historic > > > >* place marker to splice in deprecation text from Scott's draft if we want > >to. > > > >My draft has always provided updated text for section 3.3 of RFC 6376. > >It says which algorithms signers and verifiers are supposed to use. As another non-crypto expert, it's not clear to me what the DNS record for the new algorithm are supposed to look like? If it's reasonably clear from what's in the exisitng RFCs, perhaps an example? Scott K
- [Dcrup] combo update draft-ietf-dcrup-dkim-crypto… John R Levine
- Re: [Dcrup] combo update draft-ietf-dcrup-dkim-cr… Martin Thomson
- Re: [Dcrup] combo update draft-ietf-dcrup-dkim-cr… John R Levine
- Re: [Dcrup] combo update draft-ietf-dcrup-dkim-cr… Martin Thomson
- Re: [Dcrup] Is there anything this WG wants to do… John Levine
- Re: [Dcrup] Is there anything this WG wants to do… Salz, Rich
- Re: [Dcrup] Is there anything this WG wants to do… Eric Rescorla
- Re: [Dcrup] Is there anything this WG wants to do… John R Levine
- Re: [Dcrup] Is there anything this WG wants to do… Eric Rescorla
- Re: [Dcrup] Is there anything this WG wants to do… Jon Callas
- Re: [Dcrup] key rotation, was Is there anything t… John R Levine
- Re: [Dcrup] Is there anything this WG wants to do… Scott Kitterman
- Re: [Dcrup] Is there anything this WG wants to do… Scott Kitterman
- Re: [Dcrup] Is there anything this WG wants to do… John R. Levine
- Re: [Dcrup] Is there anything this WG wants to do… John R. Levine
- Re: [Dcrup] Is there anything this WG wants to do… Scott Kitterman
- Re: [Dcrup] Is there anything this WG wants to do… Peter Goldstein