Re: [dd] starting charter text for the DELEG BOF discussion

[Ralf Weber <[e-mail]>]

Moin!

On 2 Mar 2024, at 21:39, Wes Hardaker wrote:

[..]
> # Objective and Scope
>
> To address these challenges, the working group will first develop the requirements for adding a new signaling mechanism that allows parents to return DNS delegation information to resolvers.

Given that there is current work on actual protocol ideas that would stall that. I’m ok with a requirements document and changing the spec, but I don’t want to stall that work, so maybe delete “first” from that sentence.


> The working group will also list the other types of information not available today that might be be provided over a designed signaling mechanism.
>
> The working group will then define the semantics of a new signaling mechanism, taking future extensibility into account.
>
> The first use case for this DNS delegation signalling mechanism is expected to be delegation aliasing, where the parent returns a pointer to service provider that will then return the needed delegation information.
> This use case has been discussed for many years in the DNSOP and other Working Groups.

While this is one use case it might no be the first that finishes, so IMHO we should maybe use that as an example and having a generic additional use cases for the delegation mechanism in the charter.


> The working group will only specify extensions to the DNS protocol that relate to delegation.
>
> # Deliverables
>
> - A document listing the consensus-derived requirements for a new signaling mechanism between a parent and a resolver about communication parameters available for communicating with a delegated child.
> This need not be published as an RFC and may remain as an Internet-draft.
>
> - A document listing, and ideally prioritizing, new delegation attributes to be distributed from parents that would benefit resolver and child communications.
> This need not be published as an RFC and may remain as an Internet-draft.
>
> - A specification defining the new delegation attribute signaling mechanism.
> This is expected to become a standards-track RFC.
>
> - A specification for how to use the new delegation attribute signaling mechanism to perform aliasing for delegation.
> This is expected to become a standards-track RFC.

Same here note it as an example.

So long
-Ralf
——-
Ralf Weber