On Nov 6, 2013, at 20:15, Joe Abley wrote: > On 2013-11-06, at 17:08, Mark Andrews <[email protected]> wrote: > >> Guess what >> every time the Registrant does a DNS lookup in the Registry zone >> it is talking directly with the Registry. > > You're conflating registry services with DNS services. This is a common > mistake.
And registrant with DNS service provider ... the world's a bit more complicated than RRR or not. I'm confused by Mark's sentence beyond that comment. A registrant per se has no reason to do a DNS lookup so I don't get why "Registrant does a DNS lookup" is meaningful. The registrant's relying parties that do lookups. Using different terminology - customers of enterprises do the lookups, not the enterprises. Where the enterprise (registrant) has employed a DNS service provider and separately a registrar, the enterprise may be completely hands-off the DNS. And then there's the place the name is registered... One gap in such a scenario is bridging between the DNS service operator and the domain name registrar. Today there is absolutely no standard protocol (I mean "rules of engagement" not "XML/JSON-based language") there. ...I'm mindful of the wide range of use cases. I'm just focusing on one here that is still not addressed in any of the proposals I've seen to date. (FWIW, this is a necessary piece of work but I'm doubtful the answer lies within the port 53 protocol.) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Edward Lewis NeuStar You can leave a voice message at +1-571-434-5468 Why is it that people who fear government monitoring of social media are surprised to learn that I avoid contributing to social media?
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
