On Apr 18, 2014, at 8:06 AM, Antoin Verschuren <antoin.verschu...@sidn.nl> wrote:
> On of the things I haven't reviewed thoroughly enough is the > detection/polling/pushing methods in the draft. > The way it is described now in the draft feels like "we're in a hurry > so we don't care, you might as well just push a freaky proprietary > button somewhere but we're not going to tell you which one" > I think we can do better than that. Maybe, but I don't. If we have a standardized version of that button, it will probably over HTTP. For that, we would need to have a discovery mechanism for "where is my parent's web site with the button", which is very hard. It is possible, and could even be signaled in the DNS with a URL RR (thank you Patrik!), but that will take a lot more discussion. I propose that if people want to do that, it be done as a update to this document. > I would have expected somebody to mention "notify" as a detection > method that I think would be of great help for the detection of > CDNSKEY/CDS changes. The question is the same as above: notify whom? > I just haven't gotten around to phrasing the correct words on how > notify could be used to have a parental agent detect CNDSKEY/CDS > changes to be pulled. > > But we do use examples in the draft that I think are freakier than > notify, and I feel they give too much bad advise on methods that could > be used. It's not described well enough that a detection mechanism for > CDNSKEY/CDS changes is just as important for adoption of this idea to > be automated. I think we should either mention a standardized method > in the draft, or write a separate draft on how to notify a parental > agent for CDNSKEY/CDS changes and mention that in this draft, or this > will not be widely implemented. > This based on feedback I got from registrars. To me, the polling option is well-described and the most likely one to be used because it takes so much less new stuff. --Paul Hoffman _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
