Re: [Dcrup] FW: IETF WG state changed for draft-ietf-dcrup-dkim-usage

Scott Kitterman <sklist@kitterman.com> Tue, 15 August 2017 03:26 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 927351323CA for <dcrup@ietfa.amsl.com>; Mon, 14 Aug 2017 20:26:42 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 KpurBcrEiwg5 for <dcrup@ietfa.amsl.com>; Mon, 14 Aug 2017 20:26:40 -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 9922C13202D for <dcrup@ietf.org>; Mon, 14 Aug 2017 20:26:40 -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 AB500C4031D for <dcrup@ietf.org>; Mon, 14 Aug 2017 22:26:39 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=201409; t=1502767599; bh=kNWWbcIbsw6Bzxrty6zsruuVVJ58pXd9olFLsdib2VM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Uz50mXCxWAJueFZxYm1WwaqoUMk9Kh3qLo6QHbUq4ddLZTldGrgRd933Xwl8oHutV t/JQMaiK0gUyTr4rGkmTu8AJFYkhUMQddAfpj4YcZu8oCTqSWswTEK1CkZ/tnLw6Ne koh7AG/i5bQivzJVuXlNK1yJ4MyNjgWl3yKOWZ98=
From: Scott Kitterman <sklist@kitterman.com>
To: dcrup@ietf.org
Date: Mon, 14 Aug 2017 23:26:38 -0400
Message-ID: <1619558.erSAfqAhe6@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-125-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <20170815013333.1308.qmail@ary.lan>
References: <20170815013333.1308.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/va6ZNa-ZZ3T6oqslKuZ3R8QQzk8>
Subject: Re: [Dcrup] FW: IETF WG state changed for draft-ietf-dcrup-dkim-usage
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, 15 Aug 2017 03:26:43 -0000

On Tuesday, August 15, 2017 01:33:33 AM John Levine wrote:
> In article <8695284.qrNCWkNy01@kitterma-e6430> you write:
> >> Another way to look at this: I think it's more appropriate to render
> >> rsa-sha1 obsolete, but this approach seems as if we want to act like it
> >> never existed.
> >
> >Fast forward a few years:  Is the fact that it ever existed relevant to
> >anything?  I think it's highly unlikely.
> 
> The Internet being the Internet, sha-1 hashes will trickle in forever.
> I'd rather have the diagnostic say "obsolete hash" than "syntax
> error."
> 
> If you look at this curdle draft that deprecates RC4, it goes through
> and makes changes to turn OPTIONAL to MUST NOT and the like, but it
> doesn't try to undefine the obsolete rc4 crypto modes.  I think you'll
> find that typical in crypto updates.
> 
> 
> https://datatracker.ietf.org/doc/draft-ietf-curdle-rc4-die-die-die/

OK.  It seems odd to me, but if that's the IETF norm, no problem.

Scott K