Ballot for charter-ietf-dispatch
Yes
No Objection
Note: This ballot was opened for revision 03-00 and is now closed.
Ballot question: "Is this charter ready for external review?"
Clearly, I'm in favor of this charter. And that includes the name that the community has insisted on using.
Thanks for putting this together and I support the idea of introducing some flexibility for alternate work flows besides dispatching only during the IETF plenary meeting week sessions. Now I know that DISPATCH did process some documents, but I wonder if that is something that should be done away with going forward so the WG focus is purely on guiding and dispatching new work. "The DISPATCH working group may, with the agreement of the relevant ART, SEC, or WIT ADs, process and have as work items simple administrative documents for media-type specifications and other IANA actions. Otherwise, the DISPATCH working group does not process documents." Why not remove this? Can't it be done elsewhere?
The changes [1] address key points raised in my previous ballot. Many thanks. [1] https://author-tools.ietf.org/iddiff?url1=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-dispatch%2Fwithmilestones-03-00.txt&url2=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-dispatch%2Fwithmilestones-03-01.txt&difftype=--hwdiff [2] https://mailarchive.ietf.org/arch/msg/dispatch/OUQH4nzif48Rte26j7UHZ-KxY_4/
** Per “New work relating to the way the IETF transport protocols interact with network elements should be directed to TSVWG if a relevant working group cannot be found.” Is this text needed? This means that if another WG gets this scope or some other process is defined, this charter must be updated. ** Per “Participants requesting to present a topic at a DISPATCH working group meeting must have: …” Keying in on the “must” in this text and that charters typically are not so prescriptive about agenda slot requests, would it be a charter violation (appealable?) if a time slot is given to a topic which does not meet all 6 requirements? Would it be better to afford some flexibility? Other topics are already delegated to the WG wiki, why not some of these requirements? It also would allow future refinement. ** Per “ 3. People with interest and expertise to work on this problem. 4. People interested in an interoperable solution and capable of implementing and deploying it.” How does a participant requesting a slot demonstrate #3 and #4? Is there some roster to share? Is it literally people’s names? ** Per “The chairs are empowered to create operational procedures within the bounds of established IETF processes to meet the goals of this working group, including but not limited to, mandating presentation templates, instituting mailing list workflows, etc…” Is this text really needed? This is true for EVERY WG chair in the IETF.