Ballot for charter-ietf-sidrops
Yes
No Objection
No Record
Note: This ballot was opened for revision 00-04 and is now closed.
Ballot question: "Do we approve of this charter?"
I'm a Yes (this is the right thing to do), but I don't need to be the only Yes :-)
Given that the sponsoring AD hasn't balloted and none of the suggestions made during internal review were adopted or responded to, I was expecting this ballot to get deferred. I'm ok with the charter going forward but I wonder what is the point of spending time to review this twice if there is zero response to our original round of comments before we get asked to approve it.
I agree with the various comments about a final version
There were comments on the charter v3: https://datatracker.ietf.org/doc/charter-ietf-sidrops/ballot/480576/ Looking at the diffs, it seems that none of them (even the editorial ones) have been considered. While there are certainly not BLOCKS, I guess this is an oversight. Note that I haven't seen any discussions on the IESG mailing list. Regards, B.
Typo in #3 3. Operational olutions for identified issues should be developed in sidr-ops and documented in informational or BCP documents. s/olutions/solutions/
As Alissa said, I think there would be value in addressing our previous comments. At least the typos should be removed...
I agree with the comments that it'd be better to have a final charter now but am fine if that's fixed up before sending out to the community.
Comments should be applied and the charter updated. Then I'll be happily in favor. Another typo: "(for example protocol maintenance clearly does not fit elsewhere in the IETF. " is missing a )