[no-hats] So, this all raises an interesting question -- both dnscrypt.org and dnscrypt.info resolve, and work for me.... but: 1: "Errata are meant to fix "bugs" in the specification and should not be used to change what the community meant when it approved the RFC." - https://www.ietf.org/about/groups/iesg/statements/processing-rfc-errata/ . Clearly, the community "meant" https://www.dnscrypt.org/ when this was published --- or did they? I'd posit that they actually meant "the webpage which talks about DNScrypt". 2: The same "how to verify" page says: "Common sense and good judgment should be used by the IESG to decide what is the right thing to do."
but, more importantly, for the general case, how should the IETF / IESG verify that example.com and example.net are the "same"? I did the obvious "let me go look at the whois, and make an educated guess from that" - but, the scourge of whois proxy registrations makes that impossible. As a general rule, it seems like having the site owner publish a (provided) token on both would work, assuming both sites still "exist". Luckily, in this case it's not my errata, so I'll run away, leaving the problem to Eric :-P W p.s: if it were mine, I'd probably mark it hold for update with a note of "someone should validate this..." On Fri, Dec 20, 2019 at 5:10 AM Vladimír Čunát <[email protected]> wrote: > > On 12/19/19 2:08 PM, RFC Errata System wrote: > > [...] www.dnscrypt.org leads to a parking page. The official website is now > > at www.dnscrypt.info. > > The site *does* work for me ATM and looks reasonable at a quick glance, > but I haven't checked who controls it etc. > > > _______________________________________________ > dns-privacy mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dns-privacy -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf _______________________________________________ dns-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/dns-privacy
