On Thu, 31 Oct 2024, Ben Schwartz wrote:
This is why I wanted to raise this topic. I don't believe we have thought very
carefully about when DCV is actually safe
or appropriate, and I don't think we should be recommending a mechanism without
consensus and guidance for what this
mechanism achi
This is why I wanted to raise this topic. I don't believe we have thought very
carefully about when DCV is actually safe or appropriate, and I don't think we
should be recommending a mechanism without consensus and guidance for what this
mechanism achieves and when this mechanism is safe to use
On Thu, 31 Oct 2024, Tim Wicinski wrote:
draft-ietf-dnsop-domain-verification-techniques-06.txt
I'll review it today and I now understand your reasoning a lot better.
I reviewd the text.
It makes assumptions on knowing what are valid and invalid use cases of
domain ownership verificatio
On 2024-10-24 09:28 +11, Jen Linkova wrote:
> On Tue, Oct 22, 2024 at 1:42 AM Florian Obser wrote:
>> It occurred to me that a validating stub resolver still needs to know if
>> its upstream is messing with DNS. With RFC9606 we can just ask the
>> resolver what it's doing, so I put up
>> https://
All
I know many of you are busy at RIPE, or preparing for travel, but we wanted
to bring this back up. This WGLC will carry on through the week of IETF.
There was a strong consensus to adopt this work at the time. We need to
hear both positive support and constructive feedback.
Failure to reach
Thanks Ben
I'll review it today and I now understand your reasoning a lot better.
tim
On Wed, Oct 30, 2024 at 10:07 PM Ben Schwartz wrote:
> OK, I've written up some text that tries to get at this question:
> https://github.com/ietf-wg-dnsop/draft-ietf-dnsop-domain-verification-techniques/pul
