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

Liyizhou <liyizhou@huawei.com> Thu, 04 June 2020 08:50 UTC

Return-Path: <liyizhou@huawei.com>
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 2813D3A084F for <loops@ietfa.amsl.com>; Thu, 4 Jun 2020 01:50:33 -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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 UQ79TSIxjz_u for <loops@ietfa.amsl.com>; Thu, 4 Jun 2020 01:50:31 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73F703A0827 for <loops@ietf.org>; Thu, 4 Jun 2020 01:50:31 -0700 (PDT)
Received: from lhreml717-chm.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id E5DB145FA961160C8FA4 for <loops@ietf.org>; Thu, 4 Jun 2020 09:50:27 +0100 (IST)
Received: from nkgeml706-chm.china.huawei.com (10.98.57.153) by lhreml717-chm.china.huawei.com (10.201.108.68) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 4 Jun 2020 09:50:27 +0100
Received: from nkgeml707-chm.china.huawei.com (10.98.57.157) by nkgeml706-chm.china.huawei.com (10.98.57.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 4 Jun 2020 16:50:24 +0800
Received: from nkgeml707-chm.china.huawei.com ([10.98.57.157]) by nkgeml707-chm.china.huawei.com ([10.98.57.157]) with mapi id 15.01.1913.007; Thu, 4 Jun 2020 16:50:24 +0800
From: Liyizhou <liyizhou@huawei.com>
To: Carsten Bormann <cabo@tzi.org>, "loops@ietf.org" <loops@ietf.org>
Thread-Topic: [LOOPS] Results of the LOOPS side meeting May 2020
Thread-Index: AQHWOgVxQq/LO9mduU2EPnpoRG0/ZKjIH8Vw
Date: Thu, 04 Jun 2020 08:50:24 +0000
Message-ID: <b5674ad0ed6e4974a5c2b7c51125cdab@huawei.com>
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>
In-Reply-To: <1F57EAE7-DA4F-4E09-9991-01DAD588851C@tzi.org>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.13.7]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/loops/KY8JnIt45sK6_zc1bni-MsJtoe4>
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: Thu, 04 Jun 2020 08:50:33 -0000

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