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

Carsten Bormann <cabo@tzi.org> Mon, 08 June 2020 16:41 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 CDCBB3A0CFB for <loops@ietfa.amsl.com>; Mon, 8 Jun 2020 09:41:58 -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 C6gGW4cs4YQQ for <loops@ietfa.amsl.com>; Mon, 8 Jun 2020 09:41:57 -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 46F343A0CF8 for <loops@ietf.org>; Mon, 8 Jun 2020 09:41:57 -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 49gfD36FjNzyTv; Mon, 8 Jun 2020 18:41:55 +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>
In-Reply-To: <b5674ad0ed6e4974a5c2b7c51125cdab@huawei.com>
Date: Mon, 08 Jun 2020 18:41:55 +0200
Cc: "loops@ietf.org" <loops@ietf.org>
X-Mao-Original-Outgoing-Id: 613327315.393358-28c41bf02ba46ae8584b6e23ff3e697b
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC740304-204A-4A1B-9FD0-A42E43A8232F@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> <b5674ad0ed6e4974a5c2b7c51125cdab@huawei.com>
To: Liyizhou <liyizhou@huawei.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/loops/PU7VAH35EKTbSgDgfGvCPkpKL3Y>
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:41:59 -0000

(And it probably is worth pointing out that there is a draft already:

https://tools.ietf.org/html/draft-bormann-loops-geneve-binding

I apologize for having let that draft expire; I need to update it with the decision to focus on Geneve first.)

Grüße, Carsten


> On 2020-06-04, at 10:50, Liyizhou <liyizhou@huawei.com> wrote:
> 
> Hi,
> 
> From last discussion, I think LOOPS would provide the flexibility to allow the negotiation of what FEC to be used.
> 
> So in the charter proposal, 
> "at least one FEC scheme will be included in order to exercise the protocol mechanisms. "
> 
> We can add text like,
> Channel to allow FEC scheme negotiation is also to be defined?
> 
> Thanks,
> Yizhou  
> "
> 
> -----Original Message-----
> From: LOOPS [mailto:loops-bounces@ietf.org] On Behalf Of Carsten Bormann
> Sent: Thursday, June 4, 2020 8:16 AM
> To: loops@ietf.org
> Subject: [LOOPS] Results of the LOOPS side meeting May 2020
> 
> Thank you all for participating in the May 26 side meeting.
> I have updated the charter proposal with the results of the discussion:
> 
> https://github.com/loops-wg/charter
> 
> This reflects embracing ECN both for the end-to-end flows and for the path segment, as well as cleaning up the milestones to a single deliverable (which might or might not be multiple documents; I don’t think the charter needs to nail this down).  Goals for FEC support are scaled down, but FEC stays in as part of the first deliverable.
> 
> I have also moved the “discussion” section to a separate file.
> 
> Please have a timely look as the charter will be one of the inputs to the BOF process — we need to have a solid BOF proposal by June 12.
> 
> Grüße, Carsten
> 
> -- 
> LOOPS mailing list
> LOOPS@ietf.org
> https://www.ietf.org/mailman/listinfo/loops