After reading the thread, I'm confused as to why there's any question as
to adoption. This is an independent submission replacing an independent
submission, and is directive only on ICANN and explanatory for everyone
else.
Section 5 has "This document describes how DNSSEC trust anchors for the
root zone of the DNS are published." That's incomplete: "This document
describes ... are published _by ICANN_." is more correct. So the IETF
will have no real change control over this document.
There's no reason to make this a WG draft - and lots of (we're too busy
already) reasons not to. Instead, make sure the ISE knows that we'd
(DNSOP) like a chance to comment before publication, but that DNSOPs
comments should not be show stoppers. To address Geoff's note below -
the mere desire to have external/peer review does not translate into a
need to make this a WG draft.
So no.
Later, Mike
On 12/19/2023 9:55 AM, Paul Hoffman wrote:
On Dec 18, 2023, at 18:33, Paul Wouters<p...@nohats.ca> wrote:
On Mon, 18 Dec 2023, Geoff Huston wrote:
I am in support of adoption by the Working Group. The process of peer review
has proved to be highly valuable over the years and the result is generally a
more robust framework for critical elements of the DNS infrastructure.
I agree, but also understand the situation could be strange. What if the
WG would want some text but the authors representing the Root Zone
operator cannot or do not want to do this?
This is a very weird question. The authors of a WG document serve at the behest
of the WG via the chairs. The authors never get to override WG consensus or,
later, IETF consensus.
I guess at that point the
document would have to move to the ISE ?
If a group of authors want to write an RFC that doesn't need to have IETF
consensus, they should go straight to the ISE. This group of authors very
intentionally didn't do that.
--Paul Hoffman
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
