On Jul 3, 2023, at 3:10 AM, Paul Wouters <p...@nohats.ca> wrote: > > I think this message bounced back to me. Resending. > > Begin forwarded message: > >> From: Paul Wouters <p...@nohats.ca> >> Date: June 27, 2023 at 21:15:43 EDT >> To: Brian Haberman <br...@innovationslab.net> >> Cc: "dns-privacy@ietf.org" <dns-privacy@ietf.org> >> Subject: Re: [dns-privacy] Next steps : draft-ietf-dprive-unilateral-probing >> >> On Mon, 26 Jun 2023, Brian Haberman wrote: >> >>> 1. The authors verify that the implementations listed in Appendix A is >>> up-to-date. The chairs will request that this list be retained in the >>> published RFC. >> >> What is the reasoning to override RFC 7942 and leaving this in? >> There is good reason not to leave this in, which is why 7942 instructs >> to remove it. It prevents advertising, namedropping, immortalizing >> information that is quickly going to be outdated, and punishes >> implementations that wait on the RFC to implement the specification. >> >> Note also that Appendix A is not in the format specified in Section 2 >> of 7942. Without any versioning, license info and contact info, I wonder >> how useful it is right now, and even more important, years down the >> line. >> >> It also only lists two unspecified versions of known DNS software, >> 2 tools I as a DNS opensource packager have never heard of, an auth >> nameserver that doesn't mention probing at all, and the root zone that >> does no probing. >> >> I think this section should be removed before publication.
I'd like to follow RFC 7942 (which is also BCP 202) so we don't get in trouble during the IESG review. --Paul Hoffman _______________________________________________ dns-privacy mailing list dns-privacy@ietf.org https://www.ietf.org/mailman/listinfo/dns-privacy
