IETF Logo Mail Archive

Re: [regext] doc shepherd comments for draft-ietf-regext-epp-registry-maintenance-14

Tobias Sattler <sattler@united-domains.de> Mon, 21 June 2021 11:40 UTC

Return-Path: <sattler@united-domains.de>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EF353A08FF for <regext@ietfa.amsl.com>; Mon, 21 Jun 2021 04:40:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=united-domains.de
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 bYvbjHiWjoka for <regext@ietfa.amsl.com>; Mon, 21 Jun 2021 04:39:57 -0700 (PDT)
Received: from falbalka.udag.de (intmail.udag.de [89.31.137.125]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3ECBF3A08FD for <regext@ietf.org>; Mon, 21 Jun 2021 04:39:57 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=united-domains.de; s=ud20150520; t=1624275590; bh=1qw+wfX2Hu+JpAbp+OL4e6ph+11K+M1juF6jGvZYJwQ=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=MAzvHIBply6PLla3n7DFryuEm4m4k6Nr0mSMXEdeJ9zocN2EtWZpWiMYhVjAEGuMI UCGaacG/CliNqrtvF21ysup9SPSugPDqpwzRYgycDGkjpgfSFFZ5C91phTWW/pAkef mhVZTEo661IMdYOdXLmkRaCnnB4yaMfN464GupUgSknZN0oAwIgBzZHa5FXN74koYY UC9MIxuXZdHbHbjf9In6FbUTIKK4JSTbW1UQQCMOHgRNsn6WtBh5PrfkgKb827DYMj ZTsi+wX+ZXWIIDyzbcsSgX7stcVb4OlTDprR7fWqCmunGPh80L/KzuJWE99vwhHFxO 4086KL3Kz057Q==
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
From: Tobias Sattler <sattler@united-domains.de>
In-Reply-To: <542C203E-C90C-4E7A-A517-7E14407272B4@elistx.com>
Date: Mon, 21 Jun 2021 13:39:49 +0200
Cc: Registration Protocols Extensions <regext@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <ED367F1A-1F9F-4FC3-A946-964DB27E989B@united-domains.de>
References: <F1D48C2D-7E64-4820-9A8B-3D47E56A2AF7@elistx.com> <CA662C3D-9542-4048-9A58-68C421556027@me.com> <542C203E-C90C-4E7A-A517-7E14407272B4@elistx.com>
To: James Galvin <galvin@elistx.com>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
Authentication-Results: falbalka.udag.de; auth=pass smtp.auth=sattler smtp.mailfrom=sattler@united-domains.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/NPORUSEN1oWfW2WxTkRNzC6y8Ts>
Subject: Re: [regext] doc shepherd comments for draft-ietf-regext-epp-registry-maintenance-14
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jun 2021 11:40:02 -0000

Thanks, Jim.

We published a new version to address your feedback.

Tobias

> On 19. Jun 2021, at 02:49, James Galvin <galvin@elistx.com> wrote:
> 
> Thanks for the quick response.
> 
> One comment inline.
> 
> 
> 
> On 18 Jun 2021, at 16:52, Tobias Sattler wrote:
> 
>> Thank you, Jim.
>> 
>> I have prepared a new version already and ready to do another update to address your points. If that doesn’t break the process.
>> 
>> Please see my comments inline.
>> 
>>> On 18. Jun 2021, at 22:14, James Galvin <galvin@elistx.com> wrote:
>>> 
>>> As document shepherd I have reviewed:
>>> 
>>> https://datatracker.ietf.org/doc/draft-ietf-regext-epp-registry-maintenance-14
>>> 
>>> and provided a shepherd writeup so it can be submitted to the IESG for publication.
>>> 
>>> However, I note the following three editorial nits that the authors should correct before submission to the IESG.
>>> 
>>> 
>>> 1. The document has a normative reference to an internet-draft that has been recently published as an RFC:
>>> 
>>> 	draft-ietf-regext-unhandled-namespaces -> RFC9038
>>> 
>> 
>> TS: Changed.
>> 
>>> 
>>> 2. In this paragraph, Section 1.1:
>>> 
>>>  XML is case sensitive. Unless stated otherwise, XML specifications
>>>  moreover, examples provided in this document MUST be interpreted in
>>>  the character case presented to develop a conforming implementation.
>>> 
>>> Change “specifications” to “specification”.  Drop “moreover,”.
>>> 
>> 
>> TS: According to other RFCs, such as RFC9038, it says “Unless stated otherwise, XML specifications and examples provided …” Would you be fine with changing it like that?
> 
> Works for me.  Thanks!
> 
> Jim
> 
> 
>> 
>>> 
>>> 3. In this paragraph, Section 1.1:
>>> 
>>>  In examples, "C:" represents lines sent by a protocol client and
>>>  "S:" represents lines returned by a protocol server. Indentation and
>>>  white space in examples are provided only to illustrate element
>>>  relationships and are not a REQUIRED feature of this protocol.
>>> 
>>> Downcase the use of “REQUIRED”.
>> 
>> TS: Changed.
>> 
>>> 
>>> 
>>> With those changes I would recommend to Antoin Verschuren as the responsible Chair for this document to submit the next version to the IESG for publication.
>>> 
>>> Jim
> 
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext

v2.23.0 | Report a Bug | By Email