Hi Megan, all, OK for Q#7. I would "s/it/The Parental Agent", though.
Cheers, Med > -----Message d'origine----- > De : [email protected] <[email protected]> > Envoyé : mercredi 6 mai 2026 16:15 > À : [email protected] > Cc : [email protected]; [email protected]; dnsop- > [email protected]; [email protected]; BOUCADAIR Mohamed INNOV/NET > <[email protected]>; [email protected] > Objet : Re: [AD] AUTH48: RFC-to-be 9975 <draft-ietf-dnsop-cds- > consistency-11> for your review > > > Peter and *AD, > > *AD - please review question 7 below (related to BCP 14 keywords). > > While reviewing this document during AUTH48, please resolve (as > necessary) the following questions, which are also in the source > file. > > 1) <!--[rfced] Please note that we have updated the abbreviated > title for > this document from "cds-consistency" to instead read as "CDS > Consistency". Please let us know any objections. --> > > > 2) <!-- [rfced] Please insert any keywords (beyond those that > appear in the title) for use on > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc- > editor.org%2Fsearch&data=05%7C02%7Cmohamed.boucadair%40orange.com% > 7C72a77f8064fd4956c48008deab79d0ee%7C90c7a20af34b40bfbc48b9253b6f5 > d20%7C0%7C0%7C639136737184496706%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0e > U1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCI > sIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=esRtsmG4jpkd%2FFA8sQBh%2BF4TF > 5X3zwm%2BmHMkxxmTy8Q%3D&reserved=0. --> > > > 3) <!--[rfced] We had a few questions regarding the following > text: > > Original: > The corresponding Section 6.1 of [RFC7344] (CDS/CDNSKEY) contains > no provision for how specifically queries for these records should > be done. > > a) "The corresponding Section 6.1" sounds a bit strange (as it is > being compared to Section 3.1 of RFC 7477). May we update as > follows? > > Perhaps: > [RFC7344] has a corresponding section (Section 6.1) (CDS/CDNSKEY) > that contains no provision for how specifically queries for these > records should be done. > > b) How does the parenthetical (CDS/CDNSKEY) relate to the > sentence? > It is not the title of Section 6.1. Please review. > --> > > > 4) <!--[rfced] Please review this use of the plural possessive (as > previous text in the same paragraph used singular possessive). > > Original: > In any case, a single provider should not be in the position to > remove the other providers' records from the delegation. > > Perhaps: > In any case, a single provider should not be in the position to > remove the other provider's records from the delegation. > --> > > > 5) <!--[rfced] Would it make sense to add a pointer to RFC 2308 or > RFC > 9499 on first use of NODATA for the ease of the reader? > > Original: > (A NODATA response is a received response.) > > Perhaps: > (A NODATA response [RFC9499] is a received response.) > --> > > > 6) <!--[rfced] Would it make sense to make the following update > for a > parallel between implicitly and explicitly? > > Original: > Any pending queries can immediately be dequeued when encountering > a response that confirms the status quo, either implicitly > (NODATA) or explicitly. > > Perhaps: > Any pending queries can immediately be dequeued when encountering > a response that confirms the status quo, either implicitly > (NODATA) or explicitly (via a response that matches the current > delegation state). > --> > > > 7) <!--[rfced] [AD] May we break up this sentence as follows? As > it would require repetition of a BCP 14 keyword, please advise: > > Original: > To retrieve a Child's CDS/CDNSKEY RRset for DNSSEC delegation > trust > maintenance, the Parental Agent, knowing both the Child zone > name and > its NS hostnames, MUST ascertain that queries are made against > all > nameservers listed in the Child's delegation from the Parent, > and > ensure that each key referenced in any of the received answers > is > also referenced in all other received responses, or that > responses > consistently indicate a request for removal of the entire DS > RRset > ([RFC8078], Section 6). > > Perhaps: > To retrieve a Child's CDS/CDNSKEY RRset for DNSSEC delegation > trust > maintenance, the Parental Agent, knowing both the Child zone > name > and its NS hostnames, MUST ascertain that queries are made > against > all nameservers listed in the Child's delegation from the > Parent. > It MUST also ensure that each key referenced in any of the > received > answers is also referenced in all other received responses or > that > responses consistently indicate a request for removal of the > entire > DS RRset ([RFC8078], Section 6). > > --> > > > 8) <!-- [rfced] Would you like the references to be alphabetized > or left in their current order? > --> > > > 9) <!--[rfced] Is this a shared copy? > > Original: > First, the providers include each other's signing keys as DNSKEY > and > CDS/CDNSKEY records in their copy of the zone. > > Perhaps: > First, the providers include each other's signing keys as DNSKEY > and > CDS/CDNSKEY records in their copies of the zone. > > --> > > > 10) <!--[rfced] We had the following questions about abbreviations > used throughout the document: > > a) How may we expand DS? Delegation Signer as used in RFC 4034? > > b) How may we expand EPP? Extensible Provisioning Protocol as > used in RFC 5730? > > --> > > > 11) <!--[rfced] The following similar forms are used throughout > the document. Please let us know if/how the y may be made > uniform: > > child vs. Child > parent vs. Parent > --> > > > 13) <!-- [rfced] Please review the "Inclusive Language" portion of > the online Style Guide > <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fwww.rfc- > editor.org%2Fstyleguide%2Fpart2%2F%23inclusive_language&data=05%7C > 02%7Cmohamed.boucadair%40orange.com%7C72a77f8064fd4956c48008deab79 > d0ee%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6391367371845176 > 12%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDA > wMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C > &sdata=PtOYXkRZR2otU8MxLp%2FruL3%2Bq5w6XPhym2F1G4w52xA%3D&reserved > =0> and let us know if any changes are needed. Updates of this > nature typically result in more precise language, which is helpful > for readers. > > Note that our script did not flag any words in particular, but > this should still be reviewed as a best practice. > > --> > > > Thank you. > > Megan Ferguson > RFC Production Center > > *****IMPORTANT***** > > Updated 2026/05/06 > > RFC Author(s): > -------------- > > Instructions for Completing AUTH48 > > Your document has now entered AUTH48. Once it has been reviewed > and approved by you and all coauthors, it will be published as an > RFC. > If an author is no longer available, there are several remedies > available as listed in the FAQ > (https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fwww.rfc- > editor.org%2Ffaq%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com% > 7C72a77f8064fd4956c48008deab79d0ee%7C90c7a20af34b40bfbc48b9253b6f5 > d20%7C0%7C0%7C639136737184531073%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0e > U1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCI > sIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=GbH%2FeYSrtrXpbSVdubOmuj9sqZz > bHBo3a%2FOXwK3oeaA%3D&reserved=0). > > You and you coauthors are responsible for engaging other parties > (e.g., Contributors or Working Group) as necessary before > providing your approval. > > Planning your review > --------------------- > > Please review the following aspects of your document: > > * RFC Editor questions > > Please review and resolve any questions raised by the RFC > Editor > that have been included in the XML file as comments marked as > follows: > > <!-- [rfced] ... --> > > These questions will also be sent in a subsequent email. > > * Changes submitted by coauthors > > Please ensure that you review any changes submitted by your > coauthors. We assume that if you do not speak up that you > agree to changes submitted by your coauthors. > > * Content > > Please review the full content of the document, as this cannot > change once the RFC is published. Please pay particular > attention to: > - IANA considerations updates (if applicable) > - contact information > - references > > * Copyright notices and legends > > Please review the copyright notice and legends as defined in > RFC 5378 and the Trust Legal Provisions > (TLP - > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > trustee.ietf.org%2Flicense- > info&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C72a77f8064fd4 > 956c48008deab79d0ee%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6 > 39136737184544110%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUs > IlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D% > 3D%7C0%7C%7C%7C&sdata=xd9M5zC2aPh3tC9RNxeNkPKrTolSQWMTVKPmFFDJ4LE% > 3D&reserved=0). > > * Semantic markup > > Please review the markup in the XML file to ensure that > elements of > content are correctly tagged. For example, ensure that > <sourcecode> > and <artwork> are set correctly. See details at > > <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fauthors.ietf.org%2Frfcxml- > vocabulary&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C72a77f8 > 064fd4956c48008deab79d0ee%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7 > C0%7C639136737184558159%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn > RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoy > fQ%3D%3D%7C0%7C%7C%7C&sdata=YNXewH3HlTpD7d41cFjPASOWCY%2BaV%2BpD%2 > B79FLaUhhoM%3D&reserved=0>. > > * Formatted output > > Please review the PDF, HTML, and TXT files to ensure that the > formatted output, as generated from the markup in the XML file, > is > reasonable. Please note that the TXT will have formatting > limitations compared to the PDF and HTML. > > > Submitting changes > ------------------ > > To submit changes, please reply to this email using 'REPLY ALL' as > all the parties CCed on this message need to see your changes. The > parties > include: > > * your coauthors > > * [email protected] (the RPC team) > > * other document participants, depending on the stream (e.g., > IETF Stream participants are your working group chairs, the > responsible ADs, and the document shepherd). > > * [email protected], which is a new archival > mailing list > to preserve AUTH48 conversations; it is not an active > discussion > list: > > * More info: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > mailarchive.ietf.org%2Farch%2Fmsg%2Fietf-announce%2Fyb6lpIGh- > 4Q9l2USxIAe6P8O4Zc&data=05%7C02%7Cmohamed.boucadair%40orange.com%7 > C72a77f8064fd4956c48008deab79d0ee%7C90c7a20af34b40bfbc48b9253b6f5d > 20%7C0%7C0%7C639136737184578352%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU > 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs > IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=DVVLzZ1ODQfla2DirHi4xxQhDRACDA > %2F%2BmiEx0xF0klU%3D&reserved=0 > > * The archive itself: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > mailarchive.ietf.org%2Farch%2Fbrowse%2Fauth48archive%2F&data=05%7C > 02%7Cmohamed.boucadair%40orange.com%7C72a77f8064fd4956c48008deab79 > d0ee%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6391367371845967 > 32%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDA > wMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C > &sdata=dAVhxUx7X1lf6kdFingzkRlz9vAdzbwHn6VocJ75hB0%3D&reserved=0 > > * Note: If only absolutely necessary, you may temporarily > opt out > of the archiving of messages (e.g., to discuss a sensitive > matter). > If needed, please add a note at the top of the message > that you > have dropped the address. When the discussion is > concluded, > [email protected] will be re-added to the CC > list and > its addition will be noted at the top of the message. > > You may submit your changes in one of two ways: > > An update to the provided XML file > - OR - > An explicit list of changes in this format > > Section # (or indicate Global) > > OLD: > old text > > NEW: > new text > > You do not need to reply with both an updated XML file and an > explicit list of changes, as either form is sufficient. > > We will ask a stream manager to review and approve any changes > that seem beyond editorial in nature, e.g., addition of new text, > deletion of text, and technical changes. Information about stream > managers can be found in the FAQ. Editorial changes do not > require approval from a stream manager. > > > Approving for publication > -------------------------- > > To approve your RFC for publication, please reply to this email > stating that you approve this RFC for publication. Please use > 'REPLY ALL', as all the parties CCed on this message need to see > your approval. > > > Files > ----- > > The files are available here: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc- > editor.org%2Fauthors%2Frfc9975.xml&data=05%7C02%7Cmohamed.boucadai > r%40orange.com%7C72a77f8064fd4956c48008deab79d0ee%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639136737184614475%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=WSjvOruhPiXKnv > Y%2FSHuLAfvIZhsqNGUnGVX0pR4CI4k%3D&reserved=0 > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc- > editor.org%2Fauthors%2Frfc9975.html&data=05%7C02%7Cmohamed.boucada > ir%40orange.com%7C72a77f8064fd4956c48008deab79d0ee%7C90c7a20af34b4 > 0bfbc48b9253b6f5d20%7C0%7C0%7C639136737184631513%7CUnknown%7CTWFpb > GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI > sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=TjZ926K2DbgM4 > bZg7c0WUxAeUt5%2FZZXlZhZiteLEfuA%3D&reserved=0 > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc- > editor.org%2Fauthors%2Frfc9975.pdf&data=05%7C02%7Cmohamed.boucadai > r%40orange.com%7C72a77f8064fd4956c48008deab79d0ee%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639136737184647176%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=CVpcaZ29d8y%2F > qG5LtPBbU%2FiVhMF8x2Oo94lAJMNt6ic%3D&reserved=0 > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc- > editor.org%2Fauthors%2Frfc9975.txt&data=05%7C02%7Cmohamed.boucadai > r%40orange.com%7C72a77f8064fd4956c48008deab79d0ee%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639136737184663019%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=V1eh0wuv4ag9yX > rVWoyosF6TsNUemJEL%2Bmsc3iby%2Bsc%3D&reserved=0 > > Diff file of the text: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc-editor.org%2Fauthors%2Frfc9975- > diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C72a77f80 > 64fd4956c48008deab79d0ee%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C > 0%7C639136737184678167%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR > ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf > Q%3D%3D%7C0%7C%7C%7C&sdata=atYJlyKNFmeXE7SWqkYuujqq8Be9n7sL6zBfQOh > F%2Bek%3D&reserved=0 > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc-editor.org%2Fauthors%2Frfc9975- > rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C72a77 > f8064fd4956c48008deab79d0ee%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0 > %7C0%7C639136737184692911%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki > OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIj > oyfQ%3D%3D%7C0%7C%7C%7C&sdata=qkyHow59E5hvh6FalbVJRsCelZlXU7LHRUFq > KnR2PXE%3D&reserved=0 (side by side) > > Diff of the XML: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc-editor.org%2Fauthors%2Frfc9975- > xmldiff1.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C72a7 > 7f8064fd4956c48008deab79d0ee%7C90c7a20af34b40bfbc48b9253b6f5d20%7C > 0%7C0%7C639136737184708954%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk > iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI > joyfQ%3D%3D%7C0%7C%7C%7C&sdata=nOlOsxPrgQsbuahDUpkW1ioePk5rXExBAhm > PxBFH5MY%3D&reserved=0 > > > Tracking progress > ----------------- > > The details of the AUTH48 status of your document are here: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc- > editor.org%2Fauth48%2Frfc9975&data=05%7C02%7Cmohamed.boucadair%40o > range.com%7C72a77f8064fd4956c48008deab79d0ee%7C90c7a20af34b40bfbc4 > 8b9253b6f5d20%7C0%7C0%7C639136737184732259%7CUnknown%7CTWFpbGZsb3d > 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI > joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=t%2FF061zQYhJ8lsRQI > gN23kzvaA8i4My6WUmVYG7RpqI%3D&reserved=0 > > Please let us know if you have any questions. > > Thank you for your cooperation, > > RFC Editor > > -------------------------------------- > RFC9975 (draft-ietf-dnsop-cds-consistency-11) > > Title : Clarifications on CDS/CDNSKEY and CSYNC > Consistency > Author(s) : P. Thomassen > WG Chair(s) : Benno Overeinder, Ond?ej Surý > > Area Director(s) : Mohamed Boucadair, Mahesh Jethanandani > ____________________________________________________________________________________________________________ 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. -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
