On Wed, Nov 11, 2020 at 05:17:54PM -0500, John R Levine wrote: > > if you guys are going to automate and secure the public suffix list > > functionality, ... > > Not a chance.
seems like we're passing like ships in the night here. > > icann will likely never require it, but hopefully ietf can specify > > it, after which the invisible hand of the market can decide it. > > Doubly not a chance. Having been hanging around the "expedited" process at > ICANN I can assure you that the registries will voluntarily provide no WHOIS > data at all. The business plan, you know. i know about the business plans. so icann will never require it. but if there's an ietf specified way for a registrar to signal their role in all their domains, it'll be seen by at least one of them as a market differentiator. (i know the ones i'll be proposing this to.) that's all we need. so instead of debating whether icann is or is not a regulator and whether they have or have not been captured by their industry and whether they can or cannot require anything controversial, can we debate instead whether the ietf, being above the fray, can possibly specify a scalable ("not in whois") method of automatic identification of a domain's registrar? i brought this up because this marker's presence would also help with the kinds of tree walking and public-suffix-list functionalities we use today. so, there's technical merit here, it's not strictly a defense budget play. -- Paul Vixie _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop