Carsten Bormann <cabo@xxxxxxx> wrote:
> As usual, there are tons of subtle conflicts; e.g., having TIGRESS,
> MADINAS, and SECDISPATCH in one slot will be hard for security and
> privacy minded people even if they seem to be all different areas; it
> will also make sure that CBOR is completely sucked dry of this crowd.
Like Carsten I also am discouraged by this conflict.
While it feels like conflicts are down a bit compared to pandemic online
meetings, that could also be because we started less new work. In general,
unless you are a core author of a document, it's less of a problem to keep up
with ongoing work (vs new work) via ML, youtube, etc.
I wind up with listening to many (a dozen) recordings of plenary week
sessions on youtube. At 1.5x speed at least. While the total number of
hours is not that great, the attension span required can be. I have not
finished 114 yet, and I guess I probably won't.
MADINAS had a virtual interim ten days ago, I missed it because I was
physically boarding an aircraft at the time. I don't think the WG is going
well. The work has potential for far reaching impacts on many things were
IETF protocols are applied, even if the protocols as we define them do not
seem to depend upon stable layer-2 identifiers.
The *DISPATCH groups have become an important *new* process for the IETF.
They are most useful when there is a wide diversity of people reviewing the
work.
To that end, I wonder if we should do one or more of:
a) move *DISPATCH into its own slot. We have M/T/W/T, 9-10 maybe.
(although I see we starting at 9:30 for 115)
b) never schedule *DISPATCH against any other groups in that area?
c) always schedule *DISPATCH as virtual interim meetings, perhaps with
enough gap between the and the plenary that a BOF could be scheduled.
d) Assume people have read the drafts, and watched the HotRFC-style (4min?)
video presentation, and just do questions, and be able to combine
multiple *DISPATCH sessions?
e) combine them into the I* Plenary somehow.
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
Attachment:
signature.asc
Description: PGP signature
