How would having an SRV record and an entirely different (currently undeveloped) service help the situation?
If its a question of query logs, the consequence of putting any service (smtp, web, slack) in the hands of a third-party is they need to provide that (if you pay them) or you don’t get it. Why should this service be special in that regard? — John Bambenek On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license which means commercial use will require a license. Contact sa...@bambenekconsulting.com for details On Jul 9, 2019, at 09:46, Paul Vixie <p...@redbarn.org> wrote: >> On Tuesday, 9 July 2019 14:36:50 UTC John Bambenek wrote: >> Below >> >> ... > > john, (all,) my own prior review of this proposal was effectively neutral but > actually negative. dns does not permit the kind of rate limiting and logging > needed by individual domain holders around their whois details unless they > operate their own authority servers, which is rare these days. > > i would prefer to see a SRV RR at _whois._tcp.$apex, and a separate service > running on the designated server(s) to actually provide the whois > information. > i believe there's a JSON or similar encoding now, to make it machine readable. > > i'd like to know who fetches my registration information, and how often. some > friend with whom i exchange secondary name services will likely not thank me > for asking to see their dnstap output, or to run my preferred DNS RRL config. > > -- > Paul > > _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
