IETF Logo Mail Archive

Re: [Dcrup] sequence of drafts, draft-ietf-dcrup-dkim-usage and document shepherds

"John R. Levine" <johnl@iecc.com> Sat, 10 June 2017 13:42 UTC

Return-Path: <johnl@iecc.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 00C8F126BF3 for <dcrup@ietfa.amsl.com>; Sat, 10 Jun 2017 06:42:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.792
X-Spam-Level:
X-Spam-Status: No, score=-1.792 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=iecc.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 Tl9Bajd8gIgl for <dcrup@ietfa.amsl.com>; Sat, 10 Jun 2017 06:42:27 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C94A7120227 for <dcrup@ietf.org>; Sat, 10 Jun 2017 06:42:26 -0700 (PDT)
Received: (qmail 66252 invoked from network); 10 Jun 2017 13:42:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=102ca.593bf741.k1705; bh=j6y6/qFFkWJxXA/ziN0rxC2kguYgJVUz6MjtIZFNbfU=; b=q73coLWiw2pfe22DY3CtoRplQ4NyCujz9J4s+tmJi49ZWHvrWOJdFWqHfVgtpNAWVvb58H++ubZY+wGASDD0+NZUb6kkfCdczP971Es3TFwxDGcmRtISkvP953V+kf7A2EsMb7CvP5jtvcOxT4KcqyXFA8VeQ67fiONopnnwwW9+JYo4QoOzwZyc9whxNA0mcDVWm7vHRAeppMoZb+aO+ZY76xzHyfrXoWIy26mF0D1CdUj8wJXHRITR3J+StwOG
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; 10 Jun 2017 13:42:25 -0000
Date: Sat, 10 Jun 2017 09:42:25 -0400
Message-ID: <alpine.OSX.2.21.1706100940170.16076@ary.qy>
From: "John R. Levine" <johnl@iecc.com>
To: Scott Kitterman <sklist@kitterman.com>
Cc: dcrup@ietf.org
In-Reply-To: <DE201939-EA16-4957-B160-2B45B3BA60C1@kitterman.com>
References: <20170610030400.12835.qmail@ary.lan> <DE201939-EA16-4957-B160-2B45B3BA60C1@kitterman.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/iyhY25apnoc-hBZyyjSXFEIoC-s>
Subject: Re: [Dcrup] sequence of drafts, 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 13:42:28 -0000

> If we don't get something that rips out the obsolete crypto soon, then 
> ARC is either going to have to wait or have a separate crypto 
> specification from DKIM.  I don't see a new protocol with rsa-sha1 512 
> bits getting approved.  Neither of those options is good.

I'm not clear on what sequence you're expecting here.  Is this it?

* Update DKIM to take out old crypto

* Publish ARC with only sha256 and RSA1024.

* Update DKIM to add new algorithm and maybe key hashes

* What about ARC?

I'm seeing at least four documents where we should only need two, one to 
update DKIM, one to publish ARC with the same crypto.

R's,
John

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