On Thu, 12 Dec 2024 06:53:06 -0500 Tim Wicinski <tjw.i...@gmail.com> wrote:
> This starts a *four week* Working Group Last Call for > draft-ietf-dnsop-generalized-notify > "Generalized DNS Notifications" > > Current versions of the draft is available here: > https://datatracker.ietf.org/doc/draft-ietf-dnsop-generalized-notify/ > > The Current Intended Status of this document is: Proposed Standard > > Please review the draft and offer relevant comments. After reading the document I have a few questions and remarks In section 3.2 (Child-specific Method) it says: "It is also possible to publish child-specific records, where the wildcard label is replaced by the child's FQDN with the parent zone's labels stripped." I think it would be better to have a text like: "It is also possible to publish child-specific records, where instead of the wildcard label, a child's FQDN with the parent zone's labels stripped, in used." Because the word replaced triggered a way of thinking that they could not co-exist, but that is possible as mentioned in the last paragraph of section 3 "... separate zone, and/or synthesize records under it." In section 4 the text contains "parent registry", where most of the rest of the text uses "parent operator". Is this intentional? I would think using "parent operator" everywhere in the document would make it better. I find the example in section 4.1 (Endpoint Discovery) very useful, thank you for that. In section 4.2.1 I wonder why MUST the agent domain be a subordinate or equal to one of the NS hostnames? Maybe I am missing a good reason why it cannot be just a hostname listing for reports. Section 4.3 (Processing of NOTIFY Messages): Would it be useful to add "The report query will be out of bound of the NOTIFY query and response sequence" or similar to the section that talks about the EDNS0 Report-Channel? > For WGLC, we need positive support and constructive comments; lack of > objection is not enough. > So if you think this draft should be published as an RFC, please say > so. Overall I support the document, but some things might need some clarification (at least to me). -- Stefan Ubbink DNS & Systems Engineer Present: Mon, Tue, Wed, Fri SIDN | Meander 501 | 6825 MD | ARNHEM | The Netherlands T +31 (0)26 352 55 00 https://www.sidn.nl
pgp2dwY7ePKsa.pgp
Description: OpenPGP digital signature
_______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
