[dd] Charter issue: synchronization between parents and children

[Paul Hoffman <[e-mail]>]

On Mar 21, 2024, at 18:16, Geoff Huston <[e-mail]> wrote:
>> On 21 Mar 2024, at 5:57 PM, Paul Hoffman <[e-mail]> wrote:
>> 
>> Greetings again. Based on the comments during the DELEG BoF this week, Wes made many changes to the proposed charter that was shown in the BoF. The current version is here:
>>  https://github.com/paulehoffman/dns-delegation/blob/main/charter.md
>> 
>> Please see if the new wording works for you. If so, please say so. If not, please start a new thread with a descriptive subject of what you would like to see changed.
> 
> no it does not.
> 
> 1. Background and problems includes: ." A significant issue in today's deployed DNS that derives from these issues is data often being out of synchronization between parents and children. Said another way, children often have more up-to-date information about the nameservers and DNSSEC keying information than their parents due to slowness, or complete lack, of automated child-to-parent updates."
> 
> But there is no mention of any objective or deliverable that specifically addresses this "significant issue".
> 
> Is this topic in or out of scope? If its in scope then should there be a deliverable that references this? If its out of scope then why mention synchronisation at all, let alone as a "significant issue"?

My no-hats interpretation is that it is definitely in-scope and would need to be dealt with in the requirements document. It is, after all, listed as a significant issue in the charter.

My no-hats preference is not to have the charter itemize every item that would appear in the requirements document.

--Paul Hoffman