Harald,
I think the consensus you have asserted is indeed the rough consensus of those who have spoken up.
I would make three observations:
1. We are attempting to change part of the IETF's "social contract" here. I'm glad to see the IAB and IESG showing leadership, but it is unusually important to involve the whole community.
2. I would like to see us stick as closely as possible to the letter and spirit of RFC 2026, even if we don't have process rules that cover exactly what we are doing. Specifically, I'd like to see normal usage of the I-D mechanism for developing successive versions of the necessary documents. I don't consider a web site that I have to remember to look at to be a satisfactory alternative.
3. Some issues were raised in the recent "Shuffle those deck chairs" and "Sunshine law" threads that are outside the scope of administrative restructuring, but they deserve attention in the reasonably near future. But let's keep them separate.
Brian
Harald Alvestrand wrote:
The IAB and IESG have considered the input and feedback of the IETF community to date, including discussions on the IETF mailing and the results of the straw poll conducted in mid-October. Based on this input, the IAB and IESG have written a specific recommendation about how to go forward with this work, and have published it as an Internet-Draft:
- IAB and IESG Recommendation for IETF Administrative Restructuring <draft-iab-iesg-adminrest-rec-00.txt>
We believe that the IETF community opinion has converged on a rough consensus to restructure our administrative support activity as described in this recommendation ("Scenario O"), and we are sending out this Call for Consensus in order to verify that such a consensus exists. Verifying this consensus will allow the IAB and IESG to focus our efforts on executing the AdminRest transition plan and on refining and completing the IASA BCP.
Once we have a verified consensus, we will publish the recommendation document as an Informational RFC for the historical record.
If you disagree with our determination of IETF consensus, or if you have any other comments on this consensus call or on the document describing the recommendation, please send them to the IETF mailing list (ietf@xxxxxxxx) by Monday, November 8, 2004.
NEXT STEPS:
The document that is our working document for the IASA BCP is published as an internet-draft:
- Structure of the IETF Administrative Support Activity (IASA) <draft-wasserman-iasa-bcp-01.txt>
This document is not ready for Last Call, and we expect it to be substantially revised based on community feedback and discussion.
Our plan for carrying out the restructuring is made public on the AdminRest web page at <http://www.alvestrand.no/ietf/adminrest/>. One snapshot of it (current as of this writing) is also a current internet-draft:
- Proposed Transition Plan for IETF Administrative Restructuring <draft-wasserman-adminrest-plan-01.txt>
This document will not be published as an RFC.
Harald & Leslie (for the IESG & IAB)
_______________________________________________ IETF-Announce mailing list IETF-Announce@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf