Re: [lamps] Preparing the shepherd write-up for rfc6844bis

Jacob Hoffman-Andrews <jsha@eff.org> Sun, 04 November 2018 19:26 UTC

Return-Path: <jsha@eff.org>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DE8412D7F8 for <spasm@ietfa.amsl.com>; Sun, 4 Nov 2018 11:26:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.47
X-Spam-Level:
X-Spam-Status: No, score=-7.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, 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=eff.org
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 N96VkNr6W9sQ for <spasm@ietfa.amsl.com>; Sun, 4 Nov 2018 11:26:50 -0800 (PST)
Received: from mail2.eff.org (mail2.eff.org [173.239.79.204]) (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 96195126CB6 for <spasm@ietf.org>; Sun, 4 Nov 2018 11:26:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=eff.org; s=mail2; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version: Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=eu/fKAubuqh7UBsbLcgWTLaD29Dm6nGk4Myq7D24Tkg=; b=t+Pp91I2p0IrD9x7CsmYaIsH21 +l9/dDwESK5YoCbVA7EpylpiiXijAuqnOiY6hWwowoFqHE/uI5j9l3NaHct/pp/HEJYIQ26WHb7gu DnyKZgHHnpqFc5ocTG2zxVaD/fj8E0So4MKewzvjwHA5YpavdcexOJAgUTkhDkyr3R4c=;
Received: ; Sun, 04 Nov 2018 11:26:47 -0800
To: Russ Housley <housley@vigilsec.com>
Cc: SPASM <spasm@ietf.org>, jsha@letsencrypt.org, Rob Stradling <rob.stradling@comodo.com>, Phillip Hallam-Baker <phill@hallambaker.com>
References: <7FC03EEB-0D87-4454-805C-62DBCBA845C3@vigilsec.com> <87bde21f-f685-9d2b-78e3-ef459554c724@eff.org> <323CEDEA-1693-4137-A7D1-4815E05B1612@vigilsec.com>
From: Jacob Hoffman-Andrews <jsha@eff.org>
Message-ID: <09ac2d7b-8d5b-95ea-1a0f-b640e1e4b617@eff.org>
Date: Sun, 4 Nov 2018 11:26:46 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <323CEDEA-1693-4137-A7D1-4815E05B1612@vigilsec.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/EulFZpuQp0I_TpnXFUE1MBw36p8>
Subject: Re: [lamps] Preparing the shepherd write-up for rfc6844bis
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2018 19:26:52 -0000

I've now uploaded draft-02 with these fixes. 
https://tools.ietf.org/html/draft-ietf-lamps-rfc6844bis-02

On 10/31/2018 12:49 PM, Russ Housley wrote:
> The document is missing a revision number.  I am assuming that will get filled in properly when you do the post.
>
> Otherwise, it looks good to me.
>
> Russ
>
>
>> On Oct 30, 2018, at 6:45 PM, Jacob Hoffman-Andrews <jsha@eff.org> wrote:
>>
>> I've now made these fixes in the latest working copy at https://github.com/jsha/caa-simplification/blob/master/draft-ietf-lamps-rfc6844bis.md. The uploading tool is closed until 2018-11-03 23:59 +07, so I can't upload a fresh draft. I can provide rendered .txt or .xml format of the current working copy to anyone who would prefer to read in those formats.
>>
>> On 10/30/18 10:04 AM, Russ Housley wrote:
>>> IDnits reports the following problems:
>>>
>>> idnits 2.16.0
>>>
>>>    Checking nits according to https://www.ietf.org/id-info/checklist :
>>>    ----------------------------------------------------------------------------
>>>
>>>    == The 'Obsoletes: ' line in the draft header should list only the
>>>       _numbers_ of the RFCs which will be obsoleted by this document (if
>>>       approved); it should not include the word 'RFC' in the list.
>>>
>>> {{{ Easy to fix, and I would not say anything if this was the only issue. }}}
>>>
>>>
>>>    -- The draft header indicates that this document obsoletes RFC6844, but the
>>>       abstract doesn't seem to mention this, which it should.
>>>
>>> {{{ Please add a sentence to the Abstract. }}}
>>>
>>>
>>>    Checking references for intended status: Proposed Standard
>>>    ----------------------------------------------------------------------------
>>>
>>>       (See RFCs 3967 and 4897 for information about using normative references
>>>       to lower-maturity documents in RFCs)
>>>
>>>    == Missing Reference: 'STD13' is mentioned on line 194, but not defined
>>>
>>> {{{ Perhaps you meant to reference RFC 1035 here. }}}
>>>
>>>
>>>    ** Downref: Normative reference to an Informational RFC: RFC 3647
>>>
>>> {{{ Can this be moved to an Informational reference? }}}
>>>
>>>
>>>    ** Obsolete normative reference: RFC 5070 (Obsoleted by RFC 7970)
>>>
>>> {{{ Is there a reason to not reference RFC 7970? }}}
>>>
>>>
>>>    ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126)
>>>
>>> {{{ Is there a reason to not reference RFC 8126? }}}
>>>
>>> Russ
>>>
>>>
>>>
>> _______________________________________________
>> Spasm mailing list
>> Spasm@ietf.org
>> https://www.ietf.org/mailman/listinfo/spasm
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm
>