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

Scott Kitterman <sklist@kitterman.com> Sat, 19 August 2017 19:46 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 E406C1329DE for <dcrup@ietfa.amsl.com>; Sat, 19 Aug 2017 12:46:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01, 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 PnnYGlsLXOcY for <dcrup@ietfa.amsl.com>; Sat, 19 Aug 2017 12:46:37 -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 7DE771329DD for <dcrup@ietf.org>; Sat, 19 Aug 2017 12:46:37 -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 E5AA7C40166 for <dcrup@ietf.org>; Sat, 19 Aug 2017 14:46:35 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=201409; t=1503171996; bh=DwgBAY73lVL5XwitRLupNTEiwJfOTOVZzeNpZJnVkt0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=kZlz0S8HzuhElSbXezgbA1b2+J/WoPmNxOnZzjrUu1ErwDwbclhEwIwrxWXKqepgN 4lrc9WthcD7kAXXp4kLusMnPD+UykGTXy8FZ/mN6BCGad6oNagD4z5VecY27Vda/rw dpXVH834oXYGAZ6/UcSivheW7zJaClb75mAO2nF0=
From: Scott Kitterman <sklist@kitterman.com>
To: dcrup@ietf.org
Date: Sat, 19 Aug 2017 15:46:39 -0400
Message-ID: <1577948.qipkle3Fep@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-125-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <DA3AF00B-7084-454D-A1D2-5BB417EE96C8@akamai.com>
References: <150257492983.26466.3488799276681870364.idtracker@ietfa.amsl.com> <DA3AF00B-7084-454D-A1D2-5BB417EE96C8@akamai.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="nextPart2413950.EA2yxVcUPJ"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/bN2cC7zoHpduq0e0wZu99P3PQ_I>
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: Sat, 19 Aug 2017 19:46:41 -0000

On Saturday, August 12, 2017 09:58:30 PM Salz, Rich wrote:
> At the IETF meeting last month there was strong consensus to have MUST NOT
> for both generate and verify using SHA-1.  The discussion on the list had
> one major participant opposed, who removed their objection once they
> understood there were two separate documents.
> 
> Therefore, we are entering a one-week WG last call.
> 
> (Seth, please start preparing your shepherd writeup :)
> 
> 
> On 8/12/17, 5:55 PM, "IETF Secretariat" <ietf-secretariat-reply@ietf.org>
> wrote:
> 
> 
>     The IETF WG state of draft-ietf-dcrup-dkim-usage has been changed to "In
> WG Last Call" from "WG Document" by Rich Salz:
> 
>     https://datatracker.ietf.org/doc/draft-ietf-dcrup-dkim-usage/

We're within a few hours of the week being up and the rate of additional 
commentary has fallen to nil, so I took a crack at updating based on the last 
call comments.  I'm attaching an rfcdiff of what I would propose as a post-LC 
-04, but won't upload it until I get some direction.

Scott K