Hi Gavin, Éric, Please see inline.
Cheers, Med > -----Message d'origine----- > De : Gavin Brown <[email protected]> > Envoyé : mercredi 20 mai 2026 14:50 > À : Éric Vyncke <[email protected]>; The IESG <[email protected]> > Cc : Ralf Weber <[email protected]>; draft-ietf-regext-rdap-ttl- > [email protected]; [email protected]; regext- > [email protected]; [email protected]; BOUCADAIR Mohamed INNOV/NET > <[email protected]> > Objet : Re: [regext] Éric Vyncke's No Objection on draft-ietf- > regext-rdap-ttl-extension-10: (with COMMENT) > > > Hi Éric, thanks for your review! > > On Tue, 19 May 2026, at 15:07, Éric Vyncke via Datatracker wrote: > > > > [snip] > > > > One MAJOR comment and I am trusting the responsible AD to ensure > that > > this point is acted upon. There are many "SHOULD" in this > document > > without the required guidance per > > Please consider using a "MUST" (especially for > > interoperation), or the plain English "should" (which is still > > normative). > > IMHO these can all be lowercased. [Med] Not all, there is a SHOULD inherited from the base spec: https://mailarchive.ietf.org/arch/msg/regext/TOACgQUYoaKH98V7HmzyvyJXvno/ > > Med, they were actually introduced following your review, so I > would like to check whether you agree? [Med] There are two other SHOULDs. (1) CURRENT: RDAP clients which use these frameworks SHOULD explicitly This one was added to address DNSDIR review: https://datatracker.ietf.org/doc/review-ietf-regext-rdap-ttl-extension-08-dnsdir-early-ma-2026-05-10/. I'm fine to use lowercase here. (2) CURRENT: SHOULD periodically update the list of valid DNS record types to I suggest to keep this one as this is important for the maintenance of the client. Otherwise, there is a risk that the client will discard a RRType. > > Thanks, > > G. ____________________________________________________________________________________________________________ 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]
