[DNSOP] Re: Murray Kucherawy's Discuss on draft-ietf-dnsop-compact-denial-of-existence-06: (with DISCUSS and COMMENT)

On Sun, Feb 23, 2025 at 4:25 PM Murray S. Kucherawy wrote: > On Sun, Feb 23, 2025 at 3:35 AM Shumon Huque wrote: > >> (2) Section 3.1 Paragraph 2: >>> >>> The Next Domain Name field SHOULD be set to the immediate lexicographic >>> successor of the QNAME. The Type Bit Maps field MUST only hav

[DNSOP] Re: Murray Kucherawy's Discuss on draft-ietf-dnsop-compact-denial-of-existence-06: (with DISCUSS and COMMENT)

On Mon, Feb 24, 2025 at 2:14 PM Shumon Huque wrote: > > On Sun, Feb 23, 2025 at 4:25 PM Murray S. Kucherawy > wrote: >> >> On Sun, Feb 23, 2025 at 3:35 AM Shumon Huque wrote: (2) Section 3.1 Paragraph 2: The Next Domain Name field SHOULD be set to the immediate lexicograph

[DNSOP] Re: Fwd: New Version Notification for draft-nottingham-public-resolver-errors-01.txt

I continue to view this proposal as interesting and potentially valuable. However, I think the integration with draft-ietf-dnsop-structured-dns-error creates an apparent conflict. Both drafts seem to present the same information, but by very different mechanisms. This conflict could result in

[DNSOP] REMINDER: draft cutoff and meeting planning for IETF 122

Hi, Just a quick reminder that the internet-draft cutoff for IETF 122 is a week from today, Monday 3 March, at midnight UTC. The Internet-draft Submission Tool is here. Also as a reminder from Benno’s message to the list on 13 February, we’re taking reques