Hi Mike, thanks for your review! The next version will fix these issues. On Mon, 18 May 2026, at 19:22, Mike Bishop via Datatracker wrote: > Mike Bishop has entered the following ballot position for > draft-ietf-regext-rdap-ttl-extension-10: 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://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ > for more information about how to handle DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-ttl-extension/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > # IESG review of draft-ietf-regext-rdap-ttl-extension-10 > > CC @MikeBishop > > ## Comments > > ### Section 1, paragraph 1 > > A sentence expanding RDAP (Registration Data Access Protocol) and > giving a brief definition/description would be helpful context. > > ### Section 3, paragraph 3 > > This implies that all records of a given type have the same TTL across > a given domain. Is that necessarily the case? > > ## Nits > > All comments below are about very minor potential issues that you may choose > to > address in some way - or ignore - as you see fit. Some were flagged by > automated tools (via https://github.com/larseggert/ietf-reviewtool), so there > will likely be some false positives. There is no need to let me know what you > did with these suggestions. > > ### Typos > > #### Section 8.1, paragraph 3 > ``` > - 2. Made [RFC9499] a normative reference (thanks Ketan Talaulika) > + 2. Made [RFC9499] a normative reference (thanks Ketan Talaulikar) > + + > ``` > > #### Section 9, paragraph 2 > ``` > - K. Gurbani, Di Ma, Nabeel Cocker, Ketan Talaulika. > + K. Gurbani, Di Ma, Nabeel Cocker, Ketan Talaulikar. > + + > ``` > > ### Grammar/style > > #### Section 3, paragraph 3 > ``` > ection 8 of [RFC2181], a TTL value is a "an unsigned number, with a minimum v > ^ > ``` > Use "an" instead of "a" if the following word starts with a vowel sound, e.g. > "an article", "an hour". > > You don't need an article both inside and outside the quotes. > > #### Section 3, paragraph 4 > ``` > 483647. That is, a maximum of 2^31 - 1.". TTL values are represented as JSON > ^^^^ > ``` > Unless punctuating an abbreviation or acronym, periods should not appear both > inside and outside of a quote. > > > > _______________________________________________ > regext mailing list -- [email protected] > To unsubscribe send an email to [email protected]
_______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
