ietf-wg-deleg / draft-ietf-deleg-requirements

Other
0 stars 2 forks source link

Address issue with client-side update #2

Open moonshiner opened 2 months ago

moonshiner commented 2 months ago

Does seem to be addressed independently

per WG discussion

vttale commented 2 months ago

It's in the doc because someone had brought it up as a wish list item, though I can't remember who. Unlike Ben's comment to the list that it is "largely irrelevant", I do see it as relevant because it is talking about the relationship across the boundary of a delegation and is pretty closely related to existing issues like DS updates.

I brought the issue up during my presentation on the draft, where I called out that this could be solved with the proposal for DNS Notify. As a soft requirement it is only aspirational so it doesn't fully matter if it isn't achieved, but it can also be explicitly addressed in any protocol design with a simple call out to DNS Notify and keeping the issue on the radar seems worthwhile to me.

I'm mostly in favor of keeping it in, but won't fight for it if the wind blows against it.

paulehoffman commented 1 month ago

I have just opened a thread on the mailing list related to this, giving specific examples of what has been proposed in the past few weeks.

moonshiner commented 1 month ago

https://mailarchive.ietf.org/arch/msg/dd/jJ62JgxGGNPYhz6IR2ZfEJINGlI/

Mail thread for reference