[LOOPS] LOOPS meetings in May 2020, replacing IETF 107 side meetings

[Carsten Bormann <[e-mail]>]

We plan to have two LOOPS-related online side meetings during May:

* May 07, "design team meeting"
* May 26, "LOOPS side meeting"

The objectives of the "design team meeting" are 

(1) to look at the design space and make a few decisions that reduce the design space to a more manageable size (or at least focus us on parts of that space for now).  These decisions of course could be unraveled by a later WG, but it probably helps the effort to have something more specific to work on.  The document most impacted is likely to be "gen-info" [1].  I don't think we will discuss encapsulation a lot in this meeting, except maybe for consequences of the design decisions.

(2) to look at about a dozen other WGs and RGs and agree what our technical relationship with them is going to be, e.g. "watch" (shared interests, but no specific exchange or mutual dependency envisioned now; could develop, though), "import" (specs that the other WG works on will be used by ours), and "export" (we could do some work that would benefit that other WG).  This will then be useful as input for a charter discussion.

The objectives of the "LOOPS side meeting" are to

(3) look at the results of the "design team meeting" and validate that this is the way to go; with any technical discussion that follows from that;

(4) work on the charter proposal to make it more useful for chartering or as input to a second (this time WG-forming) BOF at IETF108.

Specific agenda and input documents will follow.

The timing of global online meetings is difficult.  We are spanning participants from the US (including California PDT), Europe (e.g., CEST), and Asia (e.g., China time).  There is no good timing, only less bad.  For the May meetings, we are going for this timing:

08:00–10:00 -0700 PDT
11:00–13:00 -0400 EDT
15:00-17:00 +0000 Z (world time, a.k.a. UTC)
17:00–19:00 +0200 CEST
23:00–01:00 +0800 (next day) China time, sorry about that
(Dates for other locations below in [2], [3].)

We might roll this timing around for later months, but the continents are not entirely rotationally symmetrical.

On May 7th, we are conflicting with an IESG meeting in the first hour; we will structure this meeting in such a way that it will be productive to join only for the second hour.

Both meetings are public; the word "design team" is not meant to exclude anyone.
Details to join the meeting (probably Webex) will be provided closer to the dates.
It seems we might not have the means to make recordings, which might be a bug or a feature; we do need good minute takers anyway.

If there is any unforeseen difficulty with the timing, please do speak up now.

Grüße, Carsten

[1]: https://tools.ietf.org/html/draft-welzl-loops-gen-info
[2]: https://www.timeanddate.com/worldclock/fixedtime.html?p1=1440&iso=20200507T15&msg=LOOPS%20design%20team%20meeting&ah=2&sort=2
[3]: https://www.timeanddate.com/worldclock/fixedtime.html?p1=1440&iso=20200526T15&msg=LOOPS%20side%20meeting&ah=2&sort=2