Jim Reid <[email protected]> wrote:
    > Here's the draft charter for the proposed WG which will focus on DNS
    > protocol maintenance and update, leaving dnsop to do DNS
    > Operations. If/when there's consensus on the proposed charter, the
    > dnsop charter will need to be updated. Which should be a no-brainer:
    > just delete the 2 paragraphs that mention DNS protocol maintenance.

I think the re-org itself is busy work.
I'll sit on my hands on that topic.

    > The name-to-be-decided WG is responsible for maintenance, updates and
    > extensions to the DNS protocol. This includes defining, updating and
    > deprecating DNS protocol elements, their wire formats and their
    > processing rules.

Fair enough charter.  I support it.
The details will matter, and will get sorted out as we go.

====

    > The WG is also responsible for documenting and
    > updating the DNS architecture.

What document is the _DNS architecture_?  RFC1034/35?
(I wish document titles were consistent about whether they have "(DNS)" in
their name).  If it's in scope, it would be good to know what it is that is in 
scope.

I think that a discussion about architecture would include a discussion
about, for instance, getting rid of the root name servers and have everyone
do 8806.  Never mind if that's a good idea or not: it would be in scope, right?

    > DNS operations are out of scope for the name-to-be-decided WG.

So I'm finding it hard to think about having the above discussion without
being informed by DNS operations.  Is RFC8806 an operational document?
Or an architectural one?  I don't know.

    > The IESG will decide whenever some aspects of DNS protocol activities
    > are best carried out in other WGs. When this happens, those topics will
    > be out of scope for the name-to-be-decided WG.

    > The name-to-be-decided WG will engage with relevant WGs and other
    > appropriate organisations  especially for WG adoption and Last
    > Calls. It will instruct IANA whenever changes are needed to its
    > DNS-related registries.



    > Milestones

    > * March 2027: Submit “Signalling a Zone Cut to Nowhere in the DNS” to the 
IESG.

At least, that document seems clearly in scope to me :-)

--
Michael Richardson <[email protected]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

**       My working hours and your working hours may be different.         **
** Please do not feel obligated to reply outside your normal working hours **




Attachment: signature.asc
Description: PGP signature

_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to