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

Jacob Hoffman-Andrews <jsha@eff.org> Tue, 27 November 2018 01:38 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 90C4012F1A5 for <spasm@ietfa.amsl.com>; Mon, 26 Nov 2018 17:38:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.461
X-Spam-Level:
X-Spam-Status: No, score=-8.461 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 eCOQEnMRsrJN for <spasm@ietfa.amsl.com>; Mon, 26 Nov 2018 17:38:55 -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 E8477129A87 for <spasm@ietf.org>; Mon, 26 Nov 2018 17:38:54 -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=cC6fzoUjYfEw+eH5QPxeXHY5rA9APjXE/BzvylqVvHI=; b=DtO5zAOBRW/Yn9EEhQDTcIuUMb 55fEJvVZLDa4Lw8RgIzVPwfti+h5CoLqyqFRhA6U9SbTQvmw8yRyGgbuo/7G79STxpOFGCI5yK9Yz czq5TtDl+CXPMBH9PRFsozeGgbd0q4fcxujA5GhdOZcZUxxta+bBoTdxVBmhxXAfo2lI=;
Received: ; Mon, 26 Nov 2018 17:38:51 -0800
To: fujiwara@jprs.co.jp, housley@vigilsec.com
Cc: rob.stradling@comodo.com, jsha@letsencrypt.org, phill@hallambaker.com, spasm@ietf.org
References: <7FC03EEB-0D87-4454-805C-62DBCBA845C3@vigilsec.com> <20181126.140929.1660685088175275606.fujiwara@jprs.co.jp>
From: Jacob Hoffman-Andrews <jsha@eff.org>
Message-ID: <11295b14-5424-ba55-630e-6f22fa44b45d@eff.org>
Date: Mon, 26 Nov 2018 17:38:50 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <20181126.140929.1660685088175275606.fujiwara@jprs.co.jp>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/y4XB5Mg_FktLYE_NrpUzwR91s74>
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: Tue, 27 Nov 2018 01:38:58 -0000

On 11/25/18 9:09 PM, fujiwara@jprs.co.jp wrote:
 > 2. At section 9 IANA considerations, Reference should be changed as 
this draft
 >     because this draft obsoletes RFC 6844.

This and Sean Turner's comment both relate to the IANA Considerations 
section. I have to admit I'm not familiar with best practice for an IANA 
Considerations section when writing an "Obsoletes" RFC. Should 
RFC6844bis have an empty section, since the relevant registries were 
already established by RFC6844bis? That's what I tried to do in this 
doc, though I accidentally left in one of the sub-sections 
("Certification Authority Restriction Flags").

> 1. Before proceeding, please fix errata of RFC 6844.
>     Most of them still remain.
> 
>     See https://www.rfc-editor.org/errata/rfc6844

Related to IANA Considerations section:

https://www.rfc-editor.org/errata/eid3547
https://www.rfc-editor.org/errata/eid3528
https://www.rfc-editor.org/errata/eid3532

Addressed:
https://www.rfc-editor.org/errata/eid3532
  - We no longer treat DNAME specially.

https://www.rfc-editor.org/errata/eid5200
  - Parameters are now split by semicolons.

https://www.rfc-editor.org/errata/eid5244
  - We added explicit wording about non-empty CAA RRsets.

https://www.rfc-editor.org/errata/eid5452
  - We fixed the ABNF.

https://www.rfc-editor.org/errata/eid5065
  - This was the discovery algorithm change.

https://www.rfc-editor.org/errata/eid5091
  - This was obsoleted by the revised language we used for the discovery 
algorithm.


Needs addressing:
https://www.rfc-editor.org/errata/eid4062
https://www.rfc-editor.org/errata/eid4070

I'll work on those last two.