Re: [LOOPS] BOF co-chairs thinking on LOOPS next steps

Mirja Kuehlewind <ietf@kuehlewind.net> Tue, 30 July 2019 10:34 UTC

Return-Path: <ietf@kuehlewind.net>
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 6B8121203E2 for <loops@ietfa.amsl.com>; Tue, 30 Jul 2019 03:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 irHPmGyBSO5N for <loops@ietfa.amsl.com>; Tue, 30 Jul 2019 03:34:41 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDFA112012B for <loops@ietf.org>; Tue, 30 Jul 2019 03:34:40 -0700 (PDT)
Received: from 200116b82cf82f00096e5b7dce73fffb.dip.versatel-1u1.de ([2001:16b8:2cf8:2f00:96e:5b7d:ce73:fffb]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1hsPSo-0004FV-9X; Tue, 30 Jul 2019 12:34:38 +0200
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <CAKKJt-c24RdPyZRoK-B6fXuN0xABUsU=p7Y6UFwAcENfjE3oOQ@mail.gmail.com>
Date: Tue, 30 Jul 2019 12:34:37 +0200
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, loops@ietf.org, Suresh Krishnan <suresh@kaloom.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A4576796-AACA-4BE1-9EF8-9422E1BAB9F3@kuehlewind.net>
References: <CAKKJt-eRGJe+9PtEC7xgFz+HA0zsr_sR0NUgKRmJ-P5Q3XBg-A@mail.gmail.com> <CAPjWiCSbPioTHkYBpX73qxzO=H1sJDZpCMCKzBKoU4rZLLhwMQ@mail.gmail.com> <E6659E42-D6D7-4033-B4D6-9305823063D2@tzi.org> <CAKKJt-c24RdPyZRoK-B6fXuN0xABUsU=p7Y6UFwAcENfjE3oOQ@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3445.104.11)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1564482880;5ae631dd;
X-HE-SMSGID: 1hsPSo-0004FV-9X
Archived-At: <https://mailarchive.ietf.org/arch/msg/loops/dNehIpiannYEBvhlRZ2MWy8XGcM>
Subject: Re: [LOOPS] BOF co-chairs thinking on LOOPS next steps
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: Tue, 30 Jul 2019 10:34:42 -0000

Hi Carsten, hi Spencer,

> On 25. Jul 2019, at 20:59, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
> 
> My impression, and Magnus might say I'm insane, was that Magnus is right on the edge of whether this work can be chartered without a second, working group-forming BOF. If the LOOPS community can't live without host-to-node, the community should add it. If the community can make use of LOOPS without host-to-node and add it later, the community might consider whether that reduces the scope of the initial proposed charter enough to help Magnus approve it :-) 

Yes, it would be possible to charter without another BoF a small and well-scoped group, however, it also would be possible to work on small and well-defined pieces of work without a new working group. This was one of the reasons why this was not a non-wg-forming BoF because it is not clear yet if a new group is needed or the resulting pieces of standardization work are small enough to fit into an existing group. 

Therefore, I really recommend focus on defining the standardising work items that you think are needed rather than trying to do any word-smithing of a potential charter (that eventually is not needed).

Mirja