Let me repeat this. The discovery is not in RFC6147, but RFC7050. This involved some security issues fixed by RFC8880.
In my experience this discovery mechanism is not being actually used (if anyone has a different experience I will be very happy to hear). So I will actually advocate for deprecating RFC7050, or at least not recommend its use anymore in favor of PREF64 (RFC8181) and PCP (RFC7225). Regards, Jordi @jordipalet > El 10 abr 2026, a las 9:43, Philip Homburg <[email protected]> > escribió: > >> I'm very torn on that, because like it or not DNS64 is stable, >> well-defined, and widely implemented. (I'd also prefer to abolish >> the problem by abolishing the distinction between Proposed Standard >> and Internet Standard, but that's another story.) >> >> But we still do need co-existence for very practical reasons. That's >> why v6ops is developing the IPv6-mostly approach in draft-ietf-v6ops-6mops, >> which explicitly says: "Those concerns make DNS64 a suboptimal >> and undesirable solution long-term. To eliminate the needs for >> DNS64..." etc. > > What do we gain by advancing DNS64? It seems that draft-ietf-v6ops-6mops > uses DNS64 mainly for discovery of the translation prefix. If DNS64 would be > scoped such that it only works for ipv4only.arpa. then there is not a lot > of harm in having that as part of a DNS resolver. > > Having a full DNS64 component only for the purpose of discovering the > translation prefix is likely to do more harm than good. > > _______________________________________________ > DNSOP mailing list -- [email protected] > To unsubscribe send an email to [email protected] ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
