I will reiterate some of my concerns with the draft: I find the format of section 3.2 to be very strange. As a paragraph it jumbles some items together. It should be a list format like the ones in RFCs 6761 and 7686.
Section 3.2 does not say how applications that do not use .alt should behave. Section 3.2 does not say how APIs and libraries should behave (only that .alt-aware applications will probably use specialized APIs and libraries). Section 3.2 uses “will” several times instead of BCP 14 requirements keywords. I still think the requirements for library (stub) and caching resolver behavior should be stronger. i.e. MUST NOT put .alt queries on the wire. But this is probably a minority opinion. “Caching Resolvers performing aggressive use of DNSSEC-validated caches ... will not send any queries for names under .alt to the root zone.” This statement is too strong. RFC 8198 says SHOULD, not MUST. Not to mention cache misses. DW From: DNSOP <dnsop-boun...@ietf.org> on behalf of Suzanne Woolf <swo...@pir.org> Date: Tuesday, December 13, 2022 at 12:26 PM To: "dnsop@ietf.org" <dnsop@ietf.org> Cc: "dnsop-cha...@ietf.org" <dnsop-cha...@ietf.org>, "Rob Wilton (rwilton)" <rwil...@cisco.com> Subject: [EXTERNAL] [DNSOP] WGLC for draft-ietf-dnsop-alt-tld Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Dear colleagues, This message will serve to start a Working Group Last Call on “The ALT Special Use Top Level Domain” (https://datatracker.ietf.org/doc/draft-ietf-dnsop-alt-tld/<https://secure-web.cisco.com/1KEyaIDN65K4VF1WFK4R1Riwh0dr0IiS4Ohj1QmijQQpkv69IFpuMx3py1dW1OEny5arBiZsIjc-LaAAFUtXJprF7f4QYr6deDXKb9-SL8SM6JFELHTwLqsFyrLHTJ6ZlKfxmaGpJivEQses0R6tIvCFQssNZ4ta0NLHQuYLnaiFmAsM369LBMpTdxOD4YfuITtUNmVnP3q-tdo5aj_xY77W6GN7Faw7R--nLoUx2U5-jltF2q9nkzGg_nW1VguvBtP4zN4A7oBDorjHjJTb_vfbhb_tkIEK9wRIv_wm6FkE/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-dnsop-alt-tld%2F>). Due to the end-of-year holidays, we’re starting it now and will give it four weeks. As you’ve seen from Paul Hoffman’s email, the authors have updated to version 19 based on the feedback they heard at IETF 115. Thanks Paul and Warren! The WG is very familiar with this document by now, and the WGLC is to determine whether the document has rough consensus to progress. The chairs need to know whether you support it (which, for this purpose, includes “I can live with it”), or actively oppose publishing it. Please also assume that any necessary liaison communications with ICANN will be undertaken if this document has WG consensus to move forward. Managing the potential for misunderstanding or differences of opinion among relevant organizations is the primary reason why the IETF has liaison relationships. The IETF liaison to the ICANN Board is Harald Alvestrand, who has been monitoring the conversations about alt-tld on the mailing list and has discussed the draft with the chairs and with Rob Wilton as the responsible AD. Start date: 13 December 2022 End date: 10 January 2023 Many thanks, Suzanne, Tim, and Benno
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
