Re: [MLS] recharter text

Commenting specifically on the taxonomy proposed by Richard in the PR:

"Support for Verifiable Credentials" -- I think this is too narrow, and
should instead say "Support for new credential types." Credentials are
similar to ciphersuites in that the wg should generally be open for
business to standardize new ones (when there's support / belief that they
would be valuable).

"Support for common operational patterns in messaging applications" -- On
the other hand this seems too broad, in that arbitrary endless work could
fit under this umbrella. The two drafts listed under this category are
"Last resort KPs" and "KP context". I've been concerned about the utility
of these drafts. They specify that new information be put inside of the
KeyPackage and signed. But I don't believe there's much security value in
having this information signed. The drafts also require application logic
outside of the extension to work correctly, so using the extension is not
any operationally simpler than a solution that's entirely application-level.

I'd also like to see a call-out to work on support for the "user trees"
idea that was mentioned during the meeting.

On Sat, Nov 11, 2023 at 4:17 AM Paul Wouters <paul@nohats.ca> wrote:

> On Fri, 10 Nov 2023, Watson Ladd wrote:
>
> > Does a saving clause of "such other extensions as the working group
> > consensus deems advisable" sound good?
>
> No - Recursive chartering loops are not allowed :-)
>
> The charter shows the important things the WG want to work on first.
>
> Having statements along the lines of "anything goes" won't help keep
> the WG stay focussed and won't help us evaluate how the WG is doing
> on its goals. I would not like to see 20 draft documents that are all
> in flight and not getting proper attention because everyone is working
> on their own draft only and no one is reviewing all the other drafts.
>
> However, you get a beverage of choice for your pentest of the chartering
> system :)
>
> Paul
>
> _______________________________________________
> MLS mailing list
> MLS@ietf.org
> https://www.ietf.org/mailman/listinfo/mls
>