On Thu, 10 Oct 2013, Ondřej Surý wrote:
I think that publish-in-the-child-zone and UPDATE mechanisms complement each
other and it's up to parent policy if they accept UPDATE and what to do when
they receive the UPDATE. One option would be to drop the contents of UPDATE
and check the child zone and pull the correct data from there.
It also requires no new firewall rules at the TLDs to let in new kind of
messages like UPDATE.
Don't tell me that "oh, no, I need to add new firewall rule" argument should be
a showstopper when designing new protocol.
TLDs were very adament themselves about this. Don't shoot the messenger :)
If TLDs agree on UPDATE as the trigger mechanism as opposed to EPP, I
have no problem with it. As long as signaling by using zone content is
not blocked for another 2 years while we discuss triggers. That is, I
think it is out of scope for the timers discussion and whether to use
CDS/CDNSKEY and/or DNSKEY flag.
Paul
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
