[Mimi] Design Team progress update

[Richard Barnes <[e-mail]>]

Hi all,

I wanted to provide a quick update on the status of the design team.  You
may have noticed that we did not do an adoption call as expected after the
last IETF meeting.  That's because we got some early, private feedback that
indicated the call would not succeed.  Over the winter break and into the
new year, we've been working on addressing that feedback.

We've recently merged some PRs on draft-ralston-mimi-protocol that are
intended to have the document do fewer things more clearly.  I would draw
your attention to a few things:

1. The new document is pretty aggressively consolidated and down-scoped.
What was once split between draft-kohbrok-mimi-ds and
draft-ralston-mimi-protocol is getting consolidated in the latter.  We have
removed any mechanism not required to make a basic scenario work, with the
idea that this document should show the overall framework for MIMI, and
then the full functionality can be elaborated by the WG within that
framework.  The new "Example Protocol Flow" should give a good sense of
both the overall framework and concretely how some important scenarios are
realized:
https://bifurcation.github.io/ietf-mimi-protocol/draft-ralston-mimi-protocol.html#name-example-protocol-flow

2. "MLS Application State Sync" - One bit of feedback we got was that our
initial proposal was too deeply intertwined with MLS, and should be using
MLS as more of a black box.  Our feeling was that that is possible, but
requires adding some new functionality to MLS to synchronize application
state.  This mechanism should ultimately be a draft in the MLS working
group, but we've included it here in the spirit of making things readable.
https://bifurcation.github.io/ietf-mimi-protocol/draft-ralston-mimi-protocol.html#name-mls-application-state-synch

The Design Team is still working on aligning the detailed technical content
of the draft with these bigger-picture changes.  We expect to have a more
complete draft out in time for the I-D deadline for March IETF meeting.

Best,
--Richard