Thanks Med, these are noted and will be fixed.

On Thu, 21 May 2026, at 11:53, [email protected] wrote:
> Hi Gavin, 
>
> Thank you for implementing the changes.
>
> -11 has these nits:
>
> (1)
>
> OLD:
>    The Registration Data Access Protocol (RDAP, [STD95]) provides access
>                                                          ^^^^^^^^^^^^^^ 
>    to provides access to information about Internet resources (domain^
>    ^^^^^^^^^^^^^^^^^^^^^
>    names, autonomous system numbers, and IP addresses).
>
> NEW:
>    The Registration Data Access Protocol (RDAP, [STD95]) provides access
>    to information about Internet resources (domain
>    names, autonomous system numbers, and IP addresses).
>
> (2) 
>
> RFC9083 and RFC7481 should be cited per the guidance at 
> https://authors.ietf.org/en/reference-style-guidance. That is, "RFC 
> 9083 [STD95]" and "RFC 7481 [STD95]", not [RFC9083] or RFC9083.
>
> Up to you to fix these now or leave that to AUTH48.
>
> Cheers,
> Med
>
>> -----Message d'origine-----
>> De : Gavin Brown <[email protected]>
>> Envoyé : jeudi 21 mai 2026 12:36
>> À : [email protected]
>> Objet : [regext] Re: I-D Action: draft-ietf-regext-rdap-ttl-
>> extension-11.txt
>> 
>> 
>> This version incorporates all the IESG evaluation feedback
>> received to date.
>> 
>> G.
>> 
>> On Thu, 21 May 2026, at 10:47, [email protected] wrote:
>> > Internet-Draft draft-ietf-regext-rdap-ttl-extension-11.txt is
>> now available.
>> > It is a work item of the Registration Protocols Extensions
>> (REGEXT) WG
>> > of the IETF.
>> >
>> >    Title:   RDAP Extension for DNS Time-To-Live (TTL Values)
>> >    Author:  Gavin Brown
>> >    Name:    draft-ietf-regext-rdap-ttl-extension-11.txt
>> >    Pages:   12
>> >    Dates:   2026-05-21
>> >
>> > Abstract:
>> >
>> >    This document specifies an extension to the Registration Data
>> Access
>> >    Protocol which allows the Time-To-Live (TTL) values for
>> relevant DNS
>> >    record types to be included in RDAP responses.
>> >
>> > About this draft
>> >
>> >    This note is to be removed before publishing as an RFC.
>> >
> ____________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez 
> recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les 
> messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme 
> ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and 
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have 
> been modified, changed or falsified.
> Thank you.
>
> _______________________________________________
> 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]

Reply via email to