> Il 22/02/2025 01:40 WET Mark Nottingham <mnot=40mnot....@dmarc.ietf.org> ha > scritto: > > > Hi DNS folk, > > See draft below for an update based upon feedback received. Note that the > short name of the draft isn't really accurate any more, since some of the > feedback was that this could/should be potentially applicable to other > resolvers too. > Was there any consideration of the potential workload that this model would put on IANA? If each resolver of the planet (or even just each resolver run by an entity that provides Internet connectivity services to end-users) had to register and get a resolver ID, the registry could become quite sizeable - but perhaps this would not be an issue. In general, I am not too convinced by this proposal. Authenticating these error messages a little better through the registry + URI (domain name) control mechanism could be a positive thing, but only if it does not contribute to the gatekeeping of user communication by the browsers. In fact, at the end of section 1 the draft states clearly that the mechanism will allow web browsers to decide which resolver operators (ISPs etc) will be allowed to show explanatory messages to end-users when enacting filters, and this is yet another centralization of control into the browser oligopoly. I see the potential risk in enabling any resolver to show arbitrary messages to users, but possibly the browsers should focus on controlling what kind of message is presented to the users, rather than who is sending it. Also, if in the end the deciding element for the trust is the domain name in the URI, then the registry does not add much to it, unless IANA is expected to do some trustability checks on applicants before adding their entry. --
Vittorio Bertola | Head of Policy & Innovation, Open-Xchange vittorio.bert...@open-xchange.com mailto:vittorio.bert...@open-xchange.com Office @ Via Treviso 12, 10144 Torino, Italy
_______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
