Re: [LOOPS] Results of the LOOPS side meeting May 2020

Carsten Bormann <cabo@tzi.org> Mon, 08 June 2020 16:24 UTC

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 400333A0CE1 for <loops@ietfa.amsl.com>; Mon, 8 Jun 2020 09:24:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 3oiwCMSKpGBh for <loops@ietfa.amsl.com>; Mon, 8 Jun 2020 09:24:04 -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 82E5C3A0884 for <loops@ietf.org>; Mon, 8 Jun 2020 09:24:04 -0700 (PDT)
Received: from [192.168.217.117] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (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 49gdqR0rbKzyQp; Mon, 8 Jun 2020 18:24:03 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Carsten Bormann <cabo@tzi.org>
X-Priority: 3
In-Reply-To: <2020060419473524988034@chinatelecom.cn>
Date: Mon, 08 Jun 2020 18:24:02 +0200
Cc: loops <loops@ietf.org>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
X-Mao-Original-Outgoing-Id: 613326242.671582-362f87b63f4f9b9ce14ed9806848fd06
Content-Transfer-Encoding: quoted-printable
Message-Id: <D6BE0989-2610-4921-BEB5-3C2DFE0D1A37@tzi.org>
References: <614826114.20890951590412654399.JavaMail.nobody@rln2rmd101.webex.com> <D59C1BF0-443D-4068-ADCF-D501C24F0AA6@tzi.org> <6967F8C0-6A4E-4C6B-AA49-B2652DB616A3@tzi.org> <1F57EAE7-DA4F-4E09-9991-01DAD588851C@tzi.org> <787AE7BB302AE849A7480A190F8B9330314D7D40@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <2020060419473524988034@chinatelecom.cn>
To: wangjl50 <wangjl50@chinatelecom.cn>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/loops/tSMUxGcrMM-mUBwoXuhPfStGBBU>
Subject: Re: [LOOPS] Results of the LOOPS side meeting May 2020
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: Mon, 08 Jun 2020 16:24:07 -0000


> On 2020-06-04, at 13:47, wangjl50 <wangjl50@chinatelecom.cn> wrote:
> 
> Hi Carsten,
>      Thank you for updating the charter proposal. It looks good for me. I'd also suggest to set up a milestone for adopting problems and opportunities, which is also mentioned by Med. It need not be published as an RFC eventually, but an adopted problem and opportunity draft can help the community to better design the specification during its development process. 

Hi Jianglong,

That is indeed a good idea.  I changed the proposed wording as follows below.

Grüße, Carsten


 ## Milestones
 
+The main deliverable will be a LOOPS specification.
+Also, the working group will adopt a "problems and opportunities"
+document as the basis of this work; this document then does not
+necessarily need to be published by itself as an output of the WG.
+
+* LOOPS problems and opportunities, WG document adopted, September 2020
 * LOOPS specification, WG document adopted, October 2020
 * LOOPS specification, PS to IESG, October 2021