Thanks for the feed back Erik. Apologies for missing this on v17. We have updated the document to v18 and included the updated suggested.
https://github.com/seitsu/registry-epp-maintenance/blob/master/draft-ietf-regext-epp-registry-maintenance.txt Thanks! Jody Kolker. -----Original Message----- From: Eric Vyncke (evyncke) <evyn...@cisco.com> Sent: Thursday, October 7, 2021 6:24 AM To: Jody Kolker <jkol...@godaddy.com>; The IESG <i...@ietf.org> Cc: draft-ietf-regext-epp-registry-maintena...@ietf.org; regext-cha...@ietf.org; regext@ietf.org; James Galvin <gal...@elistx.com> Subject: Re: Éric Vyncke's No Objection on draft-ietf-regext-epp-registry-maintenance-17: (with COMMENT) [You don't often get email from evyn...@cisco.com. Learn why this is important at http://aka.ms/LearnAboutSenderIdentification.] Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Jody, Thanks for your reply but in section 3.3 I only see the attribute "lang" for the element "<maint:id>" and not on "<maint:type>" per: <maint:id> The server unique identifier for the maintenance event with the OPTIONAL "name" attribute that includes a human-readable name of the event. The server unique identifier SHALL NOT be changed if the event is updated or deleted. When the "name" attribute is set, the OPTIONAL "lang" attribute MAY be present to identify the language if the negotiated value is something other than the default value of "en" (English). <maint:type> Zero or more OPTIONAL types of the maintenance event that has the possible set of values defined by server policy, such as "Routine Maintenance", "Software Update", "Software Upgrade", or "Extended Outage". -éric On 06/10/2021, 18:33, "Jody Kolker" <jkol...@godaddy.com> wrote: Eric, Thank you for review and comments. We've added our replies in line below. Please let us know if you have any questions. Thanks, Jody. -----Original Message----- From: Éric Vyncke via Datatracker <nore...@ietf.org> Sent: Wednesday, October 6, 2021 10:46 AM To: The IESG <i...@ietf.org> Cc: draft-ietf-regext-epp-registry-maintena...@ietf.org; regext-cha...@ietf.org; regext@ietf.org; James Galvin <gal...@elistx.com>; gal...@elistx.com Subject: Éric Vyncke's No Objection on draft-ietf-regext-epp-registry-maintenance-17: (with COMMENT) Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Éric Vyncke has entered the following ballot position for draft-ietf-regext-epp-registry-maintenance-17: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fblog%2Fhandling-iesg-ballot-positions%2F&data=04%7C01%7Cjkolker%40godaddy.com%7C99f471a3e3de4281efd908d989850cc3%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637692026809761671%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=G5IdUKXIAF3WoFJ2KZUIRfWdkIKABoosG7pWogliHCo%3D&reserved=0 for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-epp-registry-maintenance%2F&data=04%7C01%7Cjkolker%40godaddy.com%7C99f471a3e3de4281efd908d989850cc3%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637692026809761671%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=O0oQ%2FI0uEVJYzn1khPUrrNt3rcRX2PbZGitFNtzw3lA%3D&reserved=0 ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for the work put into this document. Please find below some non-blocking COMMENT points (but replies would be appreciated even if only for my own education). I hope that this helps to improve the document, Regards, -éric -- Section 3.3 -- In "mantid", should the reference for the encoding of the language be mentioned ? << We believe that the encoding for the language of "maintid" should default to the encoding included in the "encoding" attribute of the main "xml" element of the response and should not be needed to be included here. >> The use of "maint:tlds" seems to indicate a limitation to top-level domains only (even if the text mentions later "registry zone") but EPP is used not only for TLD. Suggest to make it even clearer (as I am afraid that it is too late in the process to change the element name). << The description of <maint:tld> element includes that the element can include top-level domain or registry zone and we felt that adding the description to <maint:tlds> may add duplication that may not be needed. However if others agree we would be happy to add in the <maint:tlds> description also. >> -- Section 4.1.3.1 -- In the example, there is "<maint:type lang="en">" but lang is not specified as an attribute of "maint:type" in section 3.3. << In section 3.3, the description of "<maint:type>" does already appear to have the following language - "The OPTIONAL "lang" attribute MAY be present to identify the language if the negotiated value is something other than the default value of "en" (English)." We might have missed it, but it seems it is already there. Could you verify? >> _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
