Re: [Dcrup] [taugh.com-standards] Benjamin Kaduk's No Objection on draft-ietf-dcrup-dkim-crypto-13: (with COMMENT)

Jim Fenton <fenton@bluepopcorn.net> Sat, 16 June 2018 19:17 UTC

Return-Path: <fenton@bluepopcorn.net>
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 8F86A130E3D; Sat, 16 Jun 2018 12:17:40 -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, 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=bluepopcorn.net
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 TFC3e7lKnMeD; Sat, 16 Jun 2018 12:17:39 -0700 (PDT)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24FD2129C6B; Sat, 16 Jun 2018 12:17:39 -0700 (PDT)
Received: from [IPv6:2601:647:5500:1330:62a4:4cff:fe65:83dd] ([IPv6:2601:647:5500:1330:62a4:4cff:fe65:83dd]) (authenticated bits=0) by v2.bluepopcorn.net (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id w5GJHUPJ021470 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 16 Jun 2018 12:17:34 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bluepopcorn.net; s=supersize; t=1529176655; bh=USeenKIN4zfDs+Vi5QP07HQ5Rs42Y4G2quk16fMd95A=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=Si6uxovdUOpi9cS+QJATQa1KaCQ7IJ19XMCgMawc2YlpdSiSYLLMQGZ31M1nBw1Ax qXyVMtPv1A+iIRF28LQU+4/sXYmIrDQYfsYYyPucOZJyIwbcEsgJpjsQRi3O1qB89b 0kh8GlgbEpsm2n4mKgzU5OAzS0chW7xu5DhwcWOA=
To: "John R. Levine" <johnl@iecc.com>, Benjamin Kaduk <kaduk@mit.edu>
Cc: dcrup@ietf.org, dcrup-chairs@ietf.org, The IESG <iesg@ietf.org>
References: <152916023988.6185.8096866196786504366.idtracker@ietfa.amsl.com> <alpine.OSX.2.21.1806161055500.9832@ary.qy> <20180616182747.GX64971@kduck.kaduk.org> <alpine.OSX.2.21.1806161448290.10727@ary.qy>
From: Jim Fenton <fenton@bluepopcorn.net>
Message-ID: <c6d38f5c-358e-1060-7f19-7889f06122cc@bluepopcorn.net>
Date: Sat, 16 Jun 2018 12:17:25 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.21.1806161448290.10727@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/JSsJvxgINWgA85nW1bZacXSxK0Y>
Subject: Re: [Dcrup] [taugh.com-standards] Benjamin Kaduk's No Objection on draft-ietf-dcrup-dkim-crypto-13: (with COMMENT)
X-BeenThere: dcrup@ietf.org
X-Mailman-Version: 2.1.26
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, 16 Jun 2018 19:17:41 -0000

On 06/16/2018 12:01 PM, John R. Levine wrote:
> % Remove or indicate the RFC Editor should remove the following text:
>> %
>> %       Discussion Venue:    Discussion about this draft is directed 
>> to the
>> %       dcrup@ietf.org [1] mailing list.
>>
>> Still relevant.
>
> Sorry, relevant to what?  Surely you're not saying that the staff in 
> the RPC don't know to remove this kind of stuff as they turn drafts 
> into RFCs.

If there's any reason to spin another revision, I would suggest cleaning 
this up. I had initially thought that it was something the RFC Editor 
could fix as well, but it's not a good use of reviewers' time to make 
each of them point it out.

-Jim (as document shepherd)