Hi, In reviewing the draft-ietf-regext-org-ext changes in draft-ietf-regext-org-ext-03, I found the following issues:
1. In section 3. “Object Attributes”, I would revise the sentence “This extension adds additional elements to the EPP domain name mapping [RFC5731].” to “This extension adds additional elements to EPP object mappings like the EPP domain name mapping [RFC5731].” 2. In section 4.2.1. “EPP <create> Command”, I would revise “One or more <orgext:id> element that…” to “One or more <orgext:id> elements that…”. 3. In section 4.2.5. “EPP <update> Command”, I would remove the “Example <update> command, domain with no organization” example, since I don’t believe that the <orgext:add/> can be empty. 4. In section 5. “Formal Syntax”, minOccurs=”0” needs to be added to the “add”, “rem”, and “chg” elements of the “updateType”type, since they are optional. 5. I found the following error via idnits: a. ** Obsolete normative reference: RFC 6982 (Obsoleted by RFC 7942) b. ** Downref: Normative reference to an Informational RFC: RFC 7451 — JG [cid:[email protected]] James Gould Distinguished Engineer [email protected] 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com<http://verisigninc.com/> From: James Gould <[email protected]> Date: Friday, April 20, 2018 at 5:54 PM To: James Galvin <[email protected]>, Registration Protocols Extensions <[email protected]> Subject: Re: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-org-ext-02 I'm am a co-author on this draft, but I did a re-read and I have the following items that need to be addressed: 1. In section 4.1.2 “EPP <info> Command” a. I recommend changing “based on its server policy” to “based on server policy”. b. I recommend changing the sentence ‘An attribute “role” associated with <orgext:id> is used…’ to ‘The “role” attribute is used to represent the relationship that the organization has to the object’. c. Change “One or more <orgext:id> elements…” to “Zero or more <orgext:id> element…”, since the XML schema supports zero organizations and there is an example without zero organizations. d. The info command example can be removed since it is not applicable. 2. In section 4.2.1 “EPP <create> Command” a. The <orgext:create> element supports a list of <orgext:id> elements and not just one. My recommendation is to modify the description of the <orgext:id> element to be: i. “One or more <orgext:id> elements that contain the identifier of the organization.” b. I recommend changing the sentence ‘An attribute “role” associated with <orgext:id> is used…’ to ‘The “role” attribute is used to represent the relationship that the organization has to the object’. c. I recommend removing the roid attribute from the <domain:pw> element of the <create> examples. 3. In section 4.2.5 “EPP <update> Command” a. Modify “…modify the attributes of a domain object” to “…modify the attribute of an object”, “In addition to the EPP command elements described in the EPP domain object,...” to “In addition to the EPP <update> command elements, …”, and “wants to update the domain object” to “wants to update the object” to be object agnostic. b. Modify “The <orgext:add>, <orgext:rem>, and <orgext:rem> elements…” to ““The <orgext:add>, <orgext:rem>, and <orgext:chg> elements…”. c. The <orgext:add>, <orgext:rem>, and <orgext:chg> elements support a list of <orgext:id> elements and not just one. My recommendation is to modify the description of the <orgext:id> element to be: i. “One or more <orgext:id> elements that contain the identifier of the organization.” d. Shouldn’t the “addRemChgType” in the XML schema remove the minOccurs=”0”, since I believe that if the <orgext:add>, <orgext:rem>, or <orgext:chg> element is provided that it should contain at least one organization? e. I recommend changing the sentence ‘An attribute “role” associated with <orgext:id> is used…’ to ‘The “role” attribute is used to represent the relationship that the organization has to the object’. f. I would remove the “domain with no organization” example since it looks like a duplicate of the “adding multiple organizations” example, and I don’t believe it is applicable. — JG James Gould Distinguished Engineer [email protected] 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 4/20/18, 9:36 AM, "regext on behalf of James Galvin" <[email protected] on behalf of [email protected]> wrote: This is a reminder that this document is in working group last call. Please indicate your support for the publication of this document. If any working group member objects to the publication of this document please respond on the list by close of business everywhere, Friday, 27 April 2018. If there are no objections the document will be submitted to the IESG. During the last call the chairs are looking for a document shepherd for this document. If you are interested in being the document shepherd please let the chairs know. The document editors cannot be the document shepherd. Thanks, Jim On 13 Apr 2018, at 9:21, James Galvin wrote: > The document editors have indicated that the following document is > ready for submission to the IESG to be considered for publication as a > Proposed Standard: > > Organization Extension for the Extensible Provisioning Protocol (EPP) > https://datatracker.ietf.org/doc/draft-ietf-regext-org-ext/ > > Please indicate your support for the publication of this document. > > If any working group member objects to the publication of this > document please respond on the list by close of business everywhere, > Friday, 27 April 2018. If there are no objections the document will > be submitted to the IESG. > > During the last call the chairs are looking for a document shepherd > for this document. If you are interested in being the document > shepherd please let the chairs know. The document editors cannot be > the document shepherd. > > If you’ve never been a document shepherd before don’t worry. > It’s a great way to understand the IETF process and your chairs > would be delighted to help you through it. > > Thanks, > > Antoin and Jim > WG Co-Chairs _______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
_______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
