On 11/7/13 5:32 AM, Edward Lewis wrote:
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.
I believe that all these examples went out of their way to specifically
not address the DNS Service operator <-> domain name registrar bridge,
lest they be accused of trying to enforce a process upon those folks,
which would not take kindly to such things.
(FWIW, this is a necessary piece of work but I'm doubtful the answer
lies within the port 53 protocol.)
This may be the bigger discussion, and it may be the ultimate answer.
But (my opinion) is that we should do our due diligence.
tim
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
