On 03/13/2013 10:05 AM, Paul Wouters wrote:
On Wed, 13 Mar 2013, Doug Barton wrote:
So how likely are those parents to utilize CDS records to
auto-publish DS? Or, put more simply, Do we have any indication
that registry operators will actually use this? I know that
registries are not the only zone parents, but without some
significant buy-in from them I think that regardless of the merits
of this idea it may be of low utility.
I am not a lawyer, but I understand that some interpretations of
public gTLD contracts would prohibit registries from exchanging
registry data directly with registrants (registrants should deal with
registrars).
The language tends to be focused around registries not contacting
registrants directly. This sort of thing would likely be an exception
to the rule, but I'm not a lawyer either. :)
It would be worth getting some clarity on this before moving forward
though.
No it is not. That already killed the use-cases document. Let's not go
there again. Whatever we specify either can or cannot be used by certain
TLDs as dictated by their local policy. There is nothing for us to take
into consideration.
Errr ... your past bad experiences aside, let's take 2 possible
theoretical scenarios.
1. There is nothing the TLD operators will accept in this space.
2. There is something that the TLD operators would gladly implement, but
because we don't talk to them and find out what that is, the thing which
we do end up creating gets ignored.
In both scenarios we've wasted our time. Of course there is some small
utility for non-TLD parents, but that's in the margins.
I don't like wasting time, and I like even less giving the critics who
say the IETF is out of touch and anachronistic more ammunition.
The question of how likely it is that anybody will implement this is
difficult to answer without time travel capability. However, if
there's no standardised mechansm, I think chances are good that
nobody will implement anything.
Um ... aren't you looking at it bass-ackwards? It doesn't matter if we
develop a standard if it doesn't meet a real-world need. Communicating
with the primary target audience for the thing we are developing would
seem to be a good step in the process.
If a TLD contract does not allow registrant-registry contact directly,
then that prevents child-parent interaction, and so nothing we specify
here can be used. So this issue is fully out of scope for this document.
I didn't say raise the issue in the document. What I said was that we
should understand the landscape before we try to build on it.
Doug
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
