From nobody Sat Oct  3 02:53:26 2020
Return-Path: <shenghao.yang@gmail.com>
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 2831C3A097D
 for <nwcrg@ietfa.amsl.com>; Sat,  3 Oct 2020 02:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
 header.d=gmail.com
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 fMqteMRxxpQH for <nwcrg@ietfa.amsl.com>;
 Sat,  3 Oct 2020 02:53:22 -0700 (PDT)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com
 [IPv6:2607:f8b0:4864:20::d35])
 (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 5F6C93A0898
 for <nwcrg@irtf.org>; Sat,  3 Oct 2020 02:53:22 -0700 (PDT)
Received: by mail-io1-xd35.google.com with SMTP id l8so4119189ioh.11
 for <nwcrg@irtf.org>; Sat, 03 Oct 2020 02:53:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; 
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc; bh=8ywTlNlQCVgCO0IGaFOu8oPLvtzznQ1rnVItKQpiOMs=;
 b=uUJpK7a8M9OJKi/MLI8Ql/Gc+bkMGFGGILODgXwZT6lhw3YNnoGeOZ1jl06ewqQN2x
 iZZnXviZKdtIr/xGj1SQ1kEjFvflx4TOtYrWcrPzyQw8A98O1x2qua10sTUufWiXP5HB
 Zb2F6TcsYD+++53vfVLbXmiM6e+l5gD8jcBc23w0Lm8P2tGICOd1i7/HEULABVsFeSSW
 Irr2Ceg9VOmqEkcbHrSQoWsq6HmawT/3BumsHR8ANwwemWUJmQTaLo0zzN7GSH9VItDz
 Q/S+PtzOgLVc3k8GBstnY+UAq0mqH6Qgp7eLe6YeJ6zoOaukbHA/8CS/vLahTuOueMUo
 C/Zg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=8ywTlNlQCVgCO0IGaFOu8oPLvtzznQ1rnVItKQpiOMs=;
 b=CZ/3Mz+o4UTPzR0cqID8oVheEQePVgxMIZjQR19e8Zg8DbTzNpasVhBqSh5zCTvCT0
 CEE0sI1bl6cATsqihEgRP9gPWFB0/oYsDkKzyTXC51B8K/510TFdLRZ2P7fmBLCzPq9W
 Jsp+jorI6K02EioiAKM7GHmopE54cvaKQZbuehWTaZQJi1HCRg8e7oXTo77tZsZAAdBv
 wzusWRx2UjdqWBj2O1EAqSLjY58MPZ+H0n/h3a085KIO21e4cVPdZ4RQxKu42g5jMcLb
 miH1WrCK9lkxi4Z7zqvwoxmBRUME+vEi4d2J4EWBPV3nehxf+qwR8sc3BQ80pZAyPYd2
 GXEA==
X-Gm-Message-State: AOAM532vNAK7n7Ob3WqbCnRlk3lmrE5Q6Dn63eJSX/N/FRKHTgLjG03d
 Ymev6GDwq2Em0SEyYJlHybR+dUoAwnMjPM+jLgg=
X-Google-Smtp-Source: ABdhPJxxPRJHH26Ylc+dnM0NwHiz+KYVlHQdmWVxwy/clkyxQ7zioEwqjUgHtz/81KHt8uMzXGiA8E1KxRCIgJeA6jM=
X-Received: by 2002:a05:6638:14c8:: with SMTP id
 l8mr5877954jak.136.1601718801598; 
 Sat, 03 Oct 2020 02:53:21 -0700 (PDT)
MIME-Version: 1.0
References: <AD5376B8-94DC-4FC5-B324-4CEC5C48746E@inria.fr>
 <72B1EC11-E0CB-4BA6-8D9B-4C1D2099C502@csperkins.org>
In-Reply-To: <72B1EC11-E0CB-4BA6-8D9B-4C1D2099C502@csperkins.org>
From: Shenghao Yang <shenghao.yang@gmail.com>
Date: Sat, 3 Oct 2020 17:53:10 +0800
Message-ID: <CAMGveSXduKHN2RDTNrxTWfOQMGeMuay9uPDuMaDj+=zHs8CL2w@mail.gmail.com>
To: Colin Perkins <csp@csperkins.org>
Cc: Vincent Roca <vincent.roca@inria.fr>, nwcrg@irtf.org, 
 Marie-Jose Montpetit <marie@mjmontpetit.com>
Content-Type: multipart/alternative; boundary="00000000000033106c05b0c13897"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nwcrg/Q_DhejjNuAycPqLPdxSzqvkiZq8>
Subject: Re: [nwcrg] RG Item Call for Adoption for "BATS Coding Scheme for
 Multi-hop Data Transport"
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: Sat, 03 Oct 2020 09:53:24 -0000

--00000000000033106c05b0c13897
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Dear Colin,

Thanks for your suggestion about research related aspects. In our next
version, we will add a paragraph in the Introduction section, and a new
section to elaborate the research issues.

The purpose of this document is a preliminary BATS coding scheme for
researchers and engineers so that they can further develop network
communication applications/protocols based on BATS codes. Towards a
sophisticated BATS code based network protocol/application, several
important research directions should be considered. In addition to the
security issues, another important research is to design the corresponding
congestion control and routing algorithms for BATS codes.

Best,

Shenghao

On Wed, Sep 9, 2020 at 2:56 AM Colin Perkins <csp@csperkins.org> wrote:

> The draft clearly describes the approach =E2=80=93 as a protocol specific=
ation, it
> seems pretty good. The draft also clearly describes where the approach
> might be useful.
>
> The draft doesn=E2=80=99t, however, seem to include much discussion of wh=
at is the
> research contribution. The references show that there has been research i=
n
> this space, but the draft doesn=E2=80=99t explain why it should be publis=
hed on the
> IRTF stream rather than by the IETF. What=E2=80=99s the current research?
>
> Colin
>
>
>
>
> On 7 Sep 2020, at 15:00, Vincent Roca <vincent.roca@inria.fr> wrote:
>
> Dear all,
>
> We would like to start a RG-Item call for adoption for the following I-D:
> "BATS Coding Scheme for Multi-hop Data Transport"
> https://datatracker.ietf.org/doc/draft-yang-nwcrg-bats/
>
> This document has been around and discussed in our RG for 2 years, it=E2=
=80=99s
> time to decide.
>
> The call will *end on Monday Sept. 28th (3 weeks)*.
>
> Please read it, provide feedback, and tell us whether you are in favour o=
f
> adopting it and if
> you would agree to review if accepted. Thanks in advance.
>
> Regards,
>
>   Marie-Jose and Vincent
> _______________________________________________
> nwcrg mailing list
> nwcrg@irtf.org
> https://www.irtf.org/mailman/listinfo/nwcrg
>
>
> _______________________________________________
> nwcrg mailing list
> nwcrg@irtf.org
> https://www.irtf.org/mailman/listinfo/nwcrg
>

--00000000000033106c05b0c13897
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><font f=
ace=3D"arial, sans-serif">Dear Colin,=C2=A0</font><div><font face=3D"arial,=
 sans-serif"><br></font></div><div><font face=3D"arial, sans-serif">Thanks =
for your suggestion about research related aspects.=C2=A0<span style=3D"col=
or:rgb(0,0,0)">In our next version, we will add a paragraph in the Introduc=
tion section, and a new section to elaborate the research issues.=C2=A0</sp=
an></font></div><div><font face=3D"arial, sans-serif"><br></font></div><div=
><font face=3D"arial, sans-serif">The purpose of this document is a prelimi=
nary BATS coding scheme for researchers and engineers so that they can furt=
her develop network communication applications/protocols based on BATS code=
s.=C2=A0Towards a sophisticated BATS code based network protocol/applicatio=
n, several important research directions should be considered. In addition =
to the security issues, another important research is to design the corresp=
onding congestion control and routing algorithms for BATS codes.=C2=A0</fon=
t></div><div><font face=3D"arial, sans-serif"><br></font></div><div><font f=
ace=3D"arial, sans-serif">Best,=C2=A0</font></div><div><font face=3D"arial,=
 sans-serif"><br></font></div><div><font face=3D"arial, sans-serif">Shengha=
o</font></div></div></div></div><br><div class=3D"gmail_quote"><div dir=3D"=
ltr" class=3D"gmail_attr">On Wed, Sep 9, 2020 at 2:56 AM Colin Perkins &lt;=
<a href=3D"mailto:csp@csperkins.org" target=3D"_blank">csp@csperkins.org</a=
>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-co=
lor:rgb(204,204,204);padding-left:1ex"><div style=3D"word-wrap:break-word;l=
ine-break:after-white-space"><div>The draft clearly describes the approach =
=E2=80=93 as a protocol specification, it seems pretty good. The draft also=
 clearly describes where the approach might be useful.=C2=A0</div><div><br>=
</div><div>The draft doesn=E2=80=99t, however, seem to include much discuss=
ion of what is the research contribution. The references show that there ha=
s been research in this space, but the draft doesn=E2=80=99t explain why it=
 should be published on the IRTF stream rather than by the IETF. What=E2=80=
=99s the current research?</div><div><br></div><div>Colin</div><div><br></d=
iv><div><br></div><div><br><div><br><blockquote type=3D"cite"><div>On 7 Sep=
 2020, at 15:00, Vincent Roca &lt;<a href=3D"mailto:vincent.roca@inria.fr" =
target=3D"_blank">vincent.roca@inria.fr</a>&gt; wrote:</div><br><div><div s=
tyle=3D"word-wrap:break-word;line-break:after-white-space">Dear all,<div><b=
r></div><div>We would like to start a RG-Item call for adoption for the fol=
lowing I-D:</div><div><span style=3D"white-space:pre-wrap">	</span>&quot;BA=
TS Coding Scheme for Multi-hop Data Transport&quot;</div><div><span style=
=3D"white-space:pre-wrap">	</span><a href=3D"https://datatracker.ietf.org/d=
oc/draft-yang-nwcrg-bats/" target=3D"_blank">https://datatracker.ietf.org/d=
oc/draft-yang-nwcrg-bats/</a></div><div><br></div><div>This document has be=
en around and discussed in our RG for 2 years, it=E2=80=99s time to decide.=
</div><div><br></div><div>The call will <b>end on Monday Sept. 28th (3 week=
s)</b>.</div><div><br></div><div>Please read it, provide feedback, and tell=
 us whether you are in favour of adopting it and if</div><div>you would agr=
ee to review if accepted. Thanks in advance.</div><div><br></div><div>Regar=
ds,</div><div><br></div><div>=C2=A0 Marie-Jose and Vincent</div></div>_____=
__________________________________________<br>nwcrg mailing list<br><a href=
=3D"mailto:nwcrg@irtf.org" target=3D"_blank">nwcrg@irtf.org</a><br><a href=
=3D"https://www.irtf.org/mailman/listinfo/nwcrg" target=3D"_blank">https://=
www.irtf.org/mailman/listinfo/nwcrg</a><br></div></blockquote></div><br></d=
iv></div>_______________________________________________<br>
nwcrg mailing list<br>
<a href=3D"mailto:nwcrg@irtf.org" target=3D"_blank">nwcrg@irtf.org</a><br>
<a href=3D"https://www.irtf.org/mailman/listinfo/nwcrg" rel=3D"noreferrer" =
target=3D"_blank">https://www.irtf.org/mailman/listinfo/nwcrg</a><br>
</blockquote></div>
</div>

--00000000000033106c05b0c13897--

