Ballot for charter-ietf-calext
Yes
No Objection
Note: This ballot was opened for revision 01-00 and is now closed.
Ballot question: "Is this charter ready for external review?"
Only one comment: fix the Markdown of the charter ;-)
As Éric notes, the markdown formatter seems to have mangled some (but not all?) of the lists. How is "use cases where there is demand" to be evaluated? In a certain sense, if a single user asks for a feature, that is "demand", but I do not think that scenario should prompt us to take on the work in question.
Should the charter explicitly state that defining any new Calendaring or Contact formats is out of scope?