Ballot for charter-ietf-curdle
Yes
No Objection
Note: This ballot was opened for revision 00-02 and is now closed.
Ballot question: "Is this charter ready for external review?"
I don't get what it means for Kerberos and JSON to be "potentially" in scope. It seems to me that they are in scope. If the WG chooses not to pursue the work related to them that's ok, but they're still in the scope of the charter.
I concur with Alissa's and Joel's comments.
seems like: The relevant IETF protocols are primarily those protocols that are standardized through the IETF and that do not have an active working group, or where the working group decides to not take on the work. To be concrete, the protocols in scope are Secure Shell (SSH), DNSSEC, PKIX, CMS, XML Digital Signatures and potentially Kerberos and JSON. can be simplified to The protocols in scope are Secure Shell (SSH), DNSSEC, PKIX, CMS, XML Digital Signatures and potentially Kerberos and JSON. also As the CURDLE working group will be handling changes to protocols and registries some of which include what are now considered outdated algorithm options, the working group can also choose to propose deprecation of such algorithms. The CURDLE working group will be handling changes to protocols and registries some of which include what are now considered outdated algorithm options, and may propose deprecation of such algorithms.