Re: [nwcrg] NWCRG meeting@ietf109 follow-up…

whyeung <whyeung@ie.cuhk.edu.hk> Wed, 18 November 2020 14:34 UTC

Return-Path: <whyeung@ie.cuhk.edu.hk>
X-Original-To: nwcrg@ietfa.amsl.com
Delivered-To: nwcrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B7653A09D5 for <nwcrg@ietfa.amsl.com>; Wed, 18 Nov 2020 06:34:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ie.cuhk.edu.hk
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 qnWvkq3IludC for <nwcrg@ietfa.amsl.com>; Wed, 18 Nov 2020 06:34:25 -0800 (PST)
Received: from outmailgw.ie.cuhk.edu.hk (outmailgw.ie.cuhk.edu.hk [137.189.96.60]) (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 E6A963A09D6 for <nwcrg@irtf.org>; Wed, 18 Nov 2020 06:34:24 -0800 (PST)
Received: from eng.ie.cuhk.edu.hk (eng.ie.cuhk.edu.hk [137.189.96.20]) by outmailgw.ie.cuhk.edu.hk (8.14.7/8.14.7) with ESMTP id 0AIEYBjw023653; Wed, 18 Nov 2020 22:34:12 +0800
DKIM-Filter: OpenDKIM Filter v2.10.3 outmailgw.ie.cuhk.edu.hk 0AIEYBjw023653
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ie.cuhk.edu.hk; s=default; t=1605710052; bh=PQ1KMRtTyk4cVSZ8WPXLcOcpq4tzNp72YlrY+JA1Ruw=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=mrDXExQgiS2dav0sb9tvZN+7lU+z9bc01mvU+b77cR7AlE5L6mnuK3t4DCvKlfmoB t0GtzC3gMv134gAWXv+PolOwaxIXAi3a+uyUM0RC99lOACeBCV/z4eMRXApP+RApW4 TEQU96DOylTj5AaNxCzIHiQj6TB8Qrvs8AYp40C2Mn/7+6OaFWd5RcNbKN0U0XLa0A eJUbof937Dep8kno9hMCvld+cvshT+vNxSwqZzt1aGGKCvkwncsKi6lfDenPjuH6xx /S2KQL1uyoeTeKZFTAoRL2iqEHn6U1NKo3kHBOK7Cs1W6/TpuaKk0dFIP1Ps8s2NKh 8qJ77BbL3gnxQ==
Received: from imailgw2.ie.cuhk.edu.hk (imailgw2.ie.cuhk.edu.hk [137.189.99.106]) by eng.ie.cuhk.edu.hk (8.15.2/8.15.2) with ESMTP id 0AIEYBrr026400; Wed, 18 Nov 2020 22:34:11 +0800
Received: from smtp-tls.ie.cuhk.edu.hk (smtp-tls.ie.cuhk.edu.hk [137.189.99.109]) by imailgw2.ie.cuhk.edu.hk (8.14.4/8.14.4) with ESMTP id 0AIEY9eg003248; Wed, 18 Nov 2020 22:34:09 +0800
Received: from [10.10.55.48] ([10.10.55.48]) (authenticated bits=0) by smtp-tls.ie.cuhk.edu.hk (8.14.4/8.14.4) with ESMTP id 0AIEYwZ9024909 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 18 Nov 2020 22:34:59 +0800
From: whyeung <whyeung@ie.cuhk.edu.hk>
Message-Id: <256BBDA0-46A8-4E35-8FFD-64197D78C18A@ie.cuhk.edu.hk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_38D36836-65F3-479C-ACF2-4C3EE002D6E1"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Date: Wed, 18 Nov 2020 22:34:03 +0800
In-Reply-To: <1A9D18D6-8C4E-4FC9-B797-3164C9FCABA2@orandom.net>
Cc: Vincent Roca <vincent.roca@inria.fr>, nwcrg@irtf.org, Marie-Jose Montpetit <marie@mjmontpetit.com>, icnrg-chairs@ietf.org
To: "David R. Oran" <daveoran@orandom.net>
References: <048B9020-DF60-4FB7-A36F-88F7613DBC10@inria.fr> <1A9D18D6-8C4E-4FC9-B797-3164C9FCABA2@orandom.net>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
X-Scanned-By: MIMEDefang 2.73 on 137.189.99.106
Archived-At: <https://mailarchive.ietf.org/arch/msg/nwcrg/P9h5SOyujwO3KMFpDCknmxkw37E>
Subject: Re: [nwcrg] =?utf-8?q?NWCRG_meeting=40ietf109_follow-up=E2=80=A6?=
X-BeenThere: nwcrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF Network Coding Research Group discussion list <nwcrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nwcrg>, <mailto:nwcrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nwcrg/>
List-Post: <mailto:nwcrg@irtf.org>
List-Help: <mailto:nwcrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nwcrg>, <mailto:nwcrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Nov 2020 14:34:27 -0000

Many thanks, Dave.

Raymond

> On 18 Nov 2020, at 10:29 PM, David R. Oran <daveoran@orandom.net> wrote:
> 
> Few comments embedded:
> 
> On 18 Nov 2020, at 2:36, Vincent Roca wrote:
> 
>> Dear all,
>> 
>> Since we run short of time during our meeting yesterday (sorry for that), here are a few additional items to discuss on the list:
>> 
>> 
>> ##1  BATS I-D adoption as RG Item
>> 
>> Main comment during adoption call (in September) was about the lack of research perspective, the ID being more a specification IETF document than an IRTF document.
>> Authors updated their ID in the -04 version, adding in particular section 6. « Data Delivery Protocol Considerations ».
>> NWCRG chairs think it’s a good initiative, but it still lacks the required depth. Chairs also think It should not be very difficult to add a more detailed discussion, given the
>> major academic background and reputation of the team, given the practical experience gained by the team during field experiments.
>> Adding this discussion would highlight the way BATS codes can answer some of these challenges.
>> 
>> Chairs believe we have a small but sufficient set of reviewers (although small, 2-3 people) for adoption, and since the ID is already in good shape, finishing the NWCRG
>> work mid-2021 seems feasible.
>> 
>> ————
>> Suggestion: adopt it as RG Item document.
>> 
>> @all: raise your hand if you object by next week.
>> ————
> No objection but a potentially good research connection is the recent work by Mike Luby and John Byers published at this year’s UCN conference, which might connect well with using BATS in an experimental setting to validate their coding-centric ICN architecture. Coding folks should definitely read the paper: https://dl.acm.org/doi/10.1145/3405656.3418710
> 
>> 
>> 
>> ##2  NC for CCN/NDN: Requirements and Challenges
>> 
>> The NWCRG chairs think the ID is almost ready for IRSG, it’s just a matter of revising the ID to reflect yesterday’s comments (no serious issue was found).
>> 
>> ————
>> @ICNRG chairs: Do you agree?
>> ————
> Yes for my part. Please also check with Dirk.
> 
>> 
>> 
>> ##3   About « Coding for QUIC » and « RLC Forward Erasure Correction (FEC) Schemes for QUIC »  I-Ds
>> 
>> No decision has been taken by authors regarding the strategy: keep it as NWCRG informational document, or move them to QUIC IETF WG.
>> The work on multipath QUIC could justify moving IDs there.
>> 
> I suspect it’s likely to be a better home since for me the only researchy aspects (as opposed to engineering questions) are related to congestion control, which we are going to continue to noodle on in NWCRG
> 
>> Authors will determine a strategy by IETF110.
>> 
>> 
>> ##4  « Tetrys, an On-the-Fly Network Coding protocol »
>> 
>> @Authors: what do you want/intend to do?
>> 
>> 
>> Cheers,
>> 
>>   Marie-Jose and Vincent
> 
>> _______________________________________________
>> nwcrg mailing list
>> nwcrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/nwcrg
> 
> DaveO
> 
> _______________________________________________
> nwcrg mailing list
> nwcrg@irtf.org
> https://www.irtf.org/mailman/listinfo/nwcrg