Re: [DNSOP] Working Group Last Call for "Domain Verification Techniques using DNS"

2023-02-17 Thread Brian Dickson
On Fri, Feb 17, 2023 at 4:06 PM tjw ietf wrote: > John > > Paul is right. As an operator one thing I always obsess on in is the data > in my zones. Why is it there , should it be, etc. Another example you may > understand is “who created this incorrect DMARC record?” > > I’ve given them much

Re: [DNSOP] Working Group Last Call for "Domain Verification Techniques using DNS"

2023-02-17 Thread John Levine
It appears that Paul Wouters said: >But also, the pain is not felt at the people who dictate how to use >their DNS validation scheme. It is with the DNS administrators finding >a bunch of unrecognisable DNS records and not knowing what the hell >they are for and whether they can or should be

Re: [DNSOP] Working Group Last Call for "Domain Verification Techniques using DNS"

2023-02-17 Thread tjw ietf
John Paul is right. As an operator one thing I always obsess on in is the data in my zones. Why is it there , should it be, etc. Another example you may understand is “who created this incorrect DMARC record?” I’ve given them much much feedback. I am eager for others to sound off. And

Re: [DNSOP] Working Group Last Call for "Domain Verification Techniques using DNS"

2023-02-17 Thread Paul Wouters
On Fri, 17 Feb 2023, John R Levine wrote: Surely we know people who run services that use DNS validation. How about talking to some of them and finding out what kind of user errors they run into? The insinuation here is that we didn't talk to them. One of the authors is at salesforce, who

Re: [DNSOP] Working Group Last Call for "Domain Verification Techniques using DNS"

2023-02-17 Thread Paul Wouters
On Fri, 17 Feb 2023, John Levine wrote: That makes no sense. Why is it harder to copy a string to the name field in a cruddy web GUI than to the data field? It's copy and paste either way. For one, if the zone data presented to you is like a sorted zone file. Second, because LHS entries

Re: [DNSOP] I-D Action: draft-ietf-dnsop-dnssec-bootstrapping-02.txt

2023-02-17 Thread tjw ietf
Peter There is no undesirable consequences in pushing new versions before they expire without changes. Actually i have an action item to review some of the discussion on this draft which is now on my short list as we push several of these other documents forward. Tim Sent from my iPhone

Re: [DNSOP] I-D Action: draft-ietf-dnsop-dnssec-bootstrapping-02.txt

2023-02-17 Thread Peter Thomassen
Hi Joe, all, On 2/17/23 21:48, Joe Abley wrote: On Fri, Feb 17, 2023 at 15:03, Peter Thomassen mailto:pe...@desec.io>> wrote: I am not sure whether draft expiry impacts the WG document handling process in any way. I would not worry. You can always reset the timer by bumping the version and

[DNSOP] I-D Action: draft-ietf-dnsop-dnssec-bootstrapping-03.txt

2023-02-17 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Domain Name System Operations WG of the IETF. Title : Automatic DNSSEC Bootstrapping using Authenticated Signals from the Zone's Operator Authors

Re: [DNSOP] QDCOUNT > 1 (a modest proposal)

2023-02-17 Thread Ted Lemon
OpenThread. It’s on GitHub. On Fri, 17 Feb 2023 at 15:38, John Kristoff wrote: > On Wed, 15 Feb 2023 13:52:03 -0500 > Ted Lemon wrote: > > > It clearly is, in the sense that someone is using it and it keeps > > coming up. :) > > Hi Ted, > > I'm just catching up on this conversation and maybe

Re: [DNSOP] I-D Action: draft-ietf-dnsop-dnssec-bootstrapping-02.txt

2023-02-17 Thread Joe Abley
On Fri, Feb 17, 2023 at 15:03, Peter Thomassen wrote: > I am not sure whether draft expiry impacts the WG document handling process > in any way. I would not worry. You can always reset the timer by bumping the version and the date and resubmitting, if it bothers you. The particular lifetime

Re: [DNSOP] QDCOUNT > 1 (a modest proposal)

2023-02-17 Thread John Kristoff
On Wed, 15 Feb 2023 13:52:03 -0500 Ted Lemon wrote: > It clearly is, in the sense that someone is using it and it keeps > coming up. :) Hi Ted, I'm just catching up on this conversation and maybe I've missed it, but can you point me at the implementation(s) that are setting QDCOUNT > 1?

Re: [DNSOP] I-D Action: draft-ietf-dnsop-dnssec-bootstrapping-02.txt

2023-02-17 Thread Peter Thomassen
Hi Michael, Chairs, On 2/17/23 14:10, Michael Bauland wrote: we've recently implemented the DNSSEC bootstrapping as defined in this draft in our registry system TANGO as well as in the CORE registry system. I just realised that the draft is going to expire tomorrow. What are the next steps?

[DNSOP] I-D Action: draft-ietf-dnsop-glue-is-not-optional-08.txt

2023-02-17 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Domain Name System Operations WG of the IETF. Title : DNS Glue Requirements in Referral Responses Authors : M. Andrews

Re: [DNSOP] Working Group Last Call for "Domain Verification Techniques using DNS"

2023-02-17 Thread John Levine
It appears that Paul Wouters said: >> _a1b2c3.example.com IN ... "whatever" >> _crudco.example.com IN ... "a1b2c3" > >Adding cryptogrpahically strong/long strings in the prefix seems >unwieldly and prone to problems - especially if the user has to put >these in via a webgui of mediocre quality.

Re: [DNSOP] Working Group Last Call for "Domain Verification Techniques using DNS"

2023-02-17 Thread Paul Wouters
John Levine wrote: While I think it would be good to publish some best practices in this area, this draft still seems scattered and makes some assertions that seem to me to be somewhere between unsupported and mistaken. I think we agree that the goal is there are two parties, call them owner

[DNSOP] Fwd: New Version Notification for draft-bellis-dnsop-qdcount-is-one-00.txt

2023-02-17 Thread Ray Bellis
Forwarded Message Subject: New Version Notification for draft-bellis-dnsop-qdcount-is-one-00.txt Date: Fri, 17 Feb 2023 08:12:18 -0800 From: internet-dra...@ietf.org To: Joe Abley , Ray Bellis A new version of I-D, draft-bellis-dnsop-qdcount-is-one-00.txt has been

Re: [DNSOP] Working Group Last Call for "DNS Terminology" (draft-ietf-dnsop-rfc8499bis)

2023-02-17 Thread Tim Wicinski
(speaking without a hat) I think this includes some good updates around the definition of Glue, and not because we've spent many hours wordsmithing this. I would like to see some folks who have commented about the definitions in the past, review these changes. Thanks the authors for their

[DNSOP] Working Group Last Call for "DNS Terminology" (draft-ietf-dnsop-rfc8499bis)

2023-02-17 Thread Benno Overeinder
Dear DNSOP WG, Following the latest consultation with the Working Group on bailiwick and in-domain/sibling name servers terminology, the authors and chairs believe this document has reached the stage of being ready for Working Group Last Call. Due to normative reference to

Re: [DNSOP] I-D Action: draft-ietf-dnsop-dnssec-bootstrapping-02.txt

2023-02-17 Thread Michael Bauland
Hi, we've recently implemented the DNSSEC bootstrapping as defined in this draft in our registry system TANGO as well as in the CORE registry system. I just realised that the draft is going to expire tomorrow. What are the next steps? Will the draft be advanced? Will there be an extension?