
From nobody Thu Apr 30 12:38:00 2020
Return-Path: <cabo@tzi.org>
X-Original-To: loops@ietfa.amsl.com
Delivered-To: loops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D2E33A1212 for <loops@ietfa.amsl.com>; Thu, 30 Apr 2020 12:37:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iJupDkS8qc9O for <loops@ietfa.amsl.com>; Thu, 30 Apr 2020 12:37:16 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1F953A11C2 for <loops@ietf.org>; Thu, 30 Apr 2020 12:37:15 -0700 (PDT)
Received: from [192.168.217.119] (p548DCD70.dip0.t-ipconnect.de [84.141.205.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 49ClyL02V8zydX; Thu, 30 Apr 2020 21:37:13 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mao-Original-Outgoing-Id: 609968233.544153-81c8bbf7fc87ba97ece18043adb4ac33
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Thu, 30 Apr 2020 21:37:13 +0200
Message-Id: <04EBF640-8E6C-41EB-A704-ECCE6FC0BA48@tzi.org>
To: loops@ietf.org
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/loops/3y0B5ShW_BKk4SSbOsmWRMGWU3Y>
Subject: [LOOPS] LOOPS meetings in May 2020, replacing IETF 107 side meetings
X-BeenThere: loops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Local Optimizations on Path Segments <loops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/loops>, <mailto:loops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/loops/>
List-Post: <mailto:loops@ietf.org>
List-Help: <mailto:loops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/loops>, <mailto:loops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Apr 2020 19:37:27 -0000

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=20

(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=E2=80=9310:00 -0700 PDT
11:00=E2=80=9313:00 -0400 EDT
15:00-17:00 +0000 Z (world time, a.k.a. UTC)
17:00=E2=80=9319:00 +0200 CEST
23:00=E2=80=9301: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=C3=BC=C3=9Fe, Carsten

[1]: https://tools.ietf.org/html/draft-welzl-loops-gen-info
[2]: =
https://www.timeanddate.com/worldclock/fixedtime.html?p1=3D1440&iso=3D2020=
0507T15&msg=3DLOOPS%20design%20team%20meeting&ah=3D2&sort=3D2
[3]: =
https://www.timeanddate.com/worldclock/fixedtime.html?p1=3D1440&iso=3D2020=
0526T15&msg=3DLOOPS%20side%20meeting&ah=3D2&sort=3D2=

