On 2013-03-13, at 13:17, Doug Barton <[email protected]> wrote: > In order to really make this work a non-trivial number of TLD registries > (which have a variety of different rules and policies) AND registrars would > have to be on board.
No. Where there are registrars involved, you just need a registrar that can handle your domain name to support it. The registry-registrar interactions can remain unchanged. > Has anyone communicated with them about this topic? The ICANN forums for both > groups would be a good place to start. No doubt some of them have people here. But this is not an topic that deals with issues of registries and registrars; it's a DNS protocol issue. Changing the context to a policy one seems unlikely to result in additional light. > You're defining "need" differently than I am. You're saying, "We need an > automated mechanism to deal with DS records." I'm saying that unless the > registries and registrars are on board with the mechanism we create, it > doesn't matter how good it is, it isn't going to solve the real-world need. I understand. I think you're wrong. >> Also, I don't know how realistic "near real time" is, if you consider >> the problem of a parent operator having to poll 5,000,000 children >> for changes. "Some time today" would satisfy the need I see. > > ... which is why I agreed with the others that raised the idea of a special > packet for the child to send to the parent to signal the need to scrape. I think that's a non-starter. Joe _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
