[DNSOP] dnsop - Update to a Meeting Session Request for IETF 117

An update to a meeting session request has just been submitted by Tim Wicinski, a Chair of the DNSOP Working Group. - Working Group Name: Domain Name System Operations Area Name: Operations and Management Area Session Requester: Tim Wicin

Re: [DNSOP] Domain Verification Techniques using DNS

Thank you for your reply Shivan, Your comment cleared some things up for me: > The draft surveyed several widely deployed techniques and synthesized best > current practices. The technique you're proposing is a new technique, and > worth considering in its own separate document by the DNSOP wor

Re: [DNSOP] Domain Verification Techniques using DNS

Hi Elliott, On Wed, 24 May 2023 at 14:52, wrote: > --- Original Message --- > On Tuesday, May 23rd, 2023 at 21:22, Paul Wouters 40aiven...@dmarc.ietf.org> wrote: > > > On Mon, May 22, 2023 at 5:49 PM wrote: > >> Dear DNSOP WG, >> >> My company has developed a domain verification techni

Re: [DNSOP] Domain Verification Techniques using DNS

--- Original Message --- On Tuesday, May 23rd, 2023 at 21:22, Paul Wouters wrote: > On Mon, May 22, 2023 at 5:49 PM wrote: > >> Dear DNSOP WG, >> >> My company has developed a domain verification technique using DNS, it fits >> the abstract of draft-ietf-dnsop-domain-verification-techn

Re: [DNSOP] [Ext] Call for Adoption: draft-klh-dnsop-rfc8109bis

On May 24, 2023, at 7:01 AM, Tim Wicinski wrote: > > > All > > The authors for RFC8109 have made some updates to their document > "Initializing a DNS Resolver with Priming Queries", and are looking to have > the > work adopted by DNSOP. > > You can see the changes made since RFC8109 here: >

[DNSOP] DNSOP WG Interim June 2023 planning: draft-ietf-dnsop rfc8499bis and lame delegation

Dear WG, As mentioned earlier on the mailing list, the chairs are planning an interim meeting in June to discuss the three options on how to proceed with draft-ietf-dnsop-rfc8499bis wrt. lame delegation: 1) Stick with the current text in the document – the original definition from RFC8499 pl

[DNSOP] Call for Adoption: draft-klh-dnsop-rfc8109bis

All The authors for RFC8109 have made some updates to their document "Initializing a DNS Resolver with Priming Queries", and are looking to have the work adopted by DNSOP. You can see the changes made since RFC8109 here: https://author-tools.ietf.org/iddiff?url1=rfc8109&url2=draft-klh-dnsop-rfc8

[DNSOP] The DNSOP WG has placed draft-klh-dnsop-rfc8109bis in state "Call For Adoption By WG Issued"

The DNSOP WG has placed draft-klh-dnsop-rfc8109bis in state Call For Adoption By WG Issued (entered by Tim Wicinski) The document is available at https://datatracker.ietf.org/doc/draft-klh-dnsop-rfc8109bis/ ___ DNSOP mailing list DNSOP@ietf.org https

Re: [DNSOP] Incompatibility with indicating client support for EDE (draft-ietf-dnsop-structured-dns-error)

> On May 24, 2023, at 12:00 AM, tirumal reddy wrote: > > On Wed, 24 May 2023 at 01:48, Tommy Pauly > wrote: >> Using length=2 and INFO-CODE=0 sounds fine to me. >> >> For the dependency on draft-ietf-add-resolver-info, I don't think we need to >> impose tha

Re: [DNSOP] Incompatibility with indicating client support for EDE (draft-ietf-dnsop-structured-dns-error)

On Wed, 24 May 2023 at 01:48, Tommy Pauly wrote: > Using length=2 and INFO-CODE=0 sounds fine to me. > > For the dependency on draft-ietf-add-resolver-info, I don't think we need > to impose that dependency. I'd much prefer to allow clients to look at that > optionally, but still be able to inclu