Re: [nwcrg] RG Last Call for "Coding and congestion control in transport"
roca <firstname.lastname@example.org> Tue, 29 June 2021 13:53 UTC
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBB9D3A350C for <email@example.com>; Tue, 29 Jun 2021 06:53:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Status: No, score=-4.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=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 ([22.214.171.124]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lrJBbUzZDR5L for <firstname.lastname@example.org>; Tue, 29 Jun 2021 06:53:38 -0700 (PDT)
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [126.96.36.199]) (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 8F3843A30AE for <email@example.com>; Tue, 29 Jun 2021 06:53:37 -0700 (PDT)
IronPort-HdrOrdr: =?us-ascii?q?A9a23=3ADTbi8K9xK+dxGL9wABhuk+ABI+orL9Y04lQ7?= =?us-ascii?q?vn2ZKCY4TiX8rauTdZsguiMc9wx+ZJhNo7G90YO7IU80jKQFgrX5ZI3SPjUO21?= =?us-ascii?q?HYSb2Kk7GSpwEIQBeOkdK1vJ0IG5SWbueAa2SS5vyW3ODXKbwdKC3sytHQuQ6n?= =?us-ascii?q?9QYUcengAJsQlDuQgG2gYzdLrLAsP+tFKKah?=
X-IronPort-AV: E=Sophos;i="5.83,309,1616454000"; d="scan'208,217";a="386518437"
Received: from xbn44-4_migr-88-165-27-50.fbx.proxad.net (HELO smtpclient.apple) ([188.8.131.52]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jun 2021 15:53:33 +0200
From: roca <firstname.lastname@example.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8F071E4A-D404-42F7-9A56-75E59B0B4C86"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(36184.108.40.206.22\))
Date: Tue, 29 Jun 2021 15:53:32 +0200
Cc: roca <email@example.com>, "firstname.lastname@example.org" <email@example.com>, Marie-Jose Montpetit <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>
To: Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>
References: <DEF1E3BB-27C8-4F38-8BEA-BB2E12477063@inria.fr> <FF3C4150-056A-49A4-A5E6-A8C7B0829BEE@inria.fr> <F3B0A07CFD358240926B78A680E166FF29F1A861@TW-MBX-P03.cnesnet.ad.cnes.fr>
X-Mailer: Apple Mail (2.36220.127.116.11.22)
Subject: Re: [nwcrg] RG Last Call for "Coding and congestion control in transport"
List-Id: IRTF Network Coding Research Group discussion list <nwcrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nwcrg>, <mailto:email@example.com?subject=unsubscribe>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nwcrg>, <mailto:firstname.lastname@example.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jun 2021 13:53:44 -0000
Dear Nicolas and Authors, Thank you for this update, I’m happy with your modifications. With Marie-Jose we think the new version of this document is now available for next step and we’ll submit it to IRSG soon. Cheers, Marie-Jose and Vincent > Le 25 juin 2021 à 13:45, Kuhn Nicolas <Nicolas.Kuhn@cnes.fr> a écrit : > > Dear Vincent, > > Thank you for your comments. > We have uploaded an updated version of the draft : https://datatracker.ietf.org/doc/draft-irtf-nwcrg-coding-and-congestion/ <https://datatracker.ietf.org/doc/draft-irtf-nwcrg-coding-and-congestion/> > > Please see inline for how your comments have been (we hope!) addressed in this update. > > Cheers, > > Nico > > De : roca <email@example.com <mailto:firstname.lastname@example.org>> > Envoyé : vendredi 11 juin 2021 16:46 > À : email@example.com <mailto:firstname.lastname@example.org> > Cc : roca <email@example.com <mailto:firstname.lastname@example.org>>; Marie-Jose Montpetit <email@example.com <mailto:firstname.lastname@example.org>>; email@example.com <mailto:firstname.lastname@example.org> > Objet : Re: RG Last Call for "Coding and congestion control in transport" > > Dear authors, > > I’ve read your updated I-D which I find in pretty good shape. > I only have a few minor comments below. > > For me, the I-D is ready for IRSG review, once these comments are fixed. > However I’d like to have another opinion on the topic. > > Sorry for the delay in reading it (RGLC finished 11 days ago). > > Cheers, Vincent > > > Clarification: > > ** Section 2.3: > - 1st paragraph: > The use of multipath can indeed be associated to the case where there are multiple application streams, to split different streams to different paths, but not necessarily. The way it's written suggests me multipath is useless unless there are several application streams. > I'm pretty sure this is not what you mean. > [NK] The text has been updated as follows : > <- > The application layer may be composed of several streams above FEC > and transport layers instances. The transport layer may exploit a > multipath mechanism. The different streams could exploit different > paths between the sender and the receiver or not. This section > describes what is in the scope of this document in regards with > multi-streams applications and multipath transport protocols. > -> > The application layer can be composed of several streams above FEC > and transport layers instances. The transport layer can exploit a > multipath mechanism. The different streams could exploit different > paths between the sender and the receiver. Moreover, a single-stream > application could also exploit a multipath transport mechanism. This > section describes what is in the scope of this document in regards > with multi-streams applications and multipath transport protocols. > > - fig 4 and 5: could you write in the figures what is in scope and what is not. It's hard to follow from the text. > - What are the motivations for considering or not each possibility? It's not clear to me after reading this section. > > [NK] This section has been updated with new figures and cases number to clarify what is discussed and what is not. > “ Cases > IV, V and VI of Figure 5 are related to how multiple streams are > managed by a single transport or FEC layer: this does not directly > concerns the interaction between FEC and the transport and is out of > the scope of this document.” > > ** Section 9, security considerations: > What about manipulating feedback signals in order to compromize FEC rate adaptation? These feedback packets could be dropped or modified by an attacker. This is a way to trigger a DoS that specifically uses the technics described in this document that should be discussed briefly IMHO. > > [NK] We have added the following in the security section > “ FEC and CC schemes can contribute to DoS attacks. Moreover, the > transmission of signaling messages from the client to the server > should be protected and reliable otherwise an attacker may compromise > FEC rate adaptation. Indeed, an attacker could either modify the > values indicated by the client or drop signaling messages.” > > Minor comments: > > ** suggestion: "recovered" instead of "repaired" in 2.1. (repaired suggests there could be an error I think). > > [NK] We have made an editorial check on the usage of recovered/repaired. > > ** fig 1: I'm a bit surprised by the arrows: > | | source and/or ---->| | > | | ----- repair symbols ---->| | > > Why not the following: > | | source and/or | | > | | ----- repair symbols ---->| | > or even: > | | ----- source and/or ---->| | > | | ----- repair symbols ---->| | > > [NK] Thanks. > > > > Le 10 mai 2021 à 10:48, Vincent Roca <email@example.com <mailto:firstname.lastname@example.org>> a écrit : > > Dear all, > > Following the recent update of the I-D (thank you!), we would like to officially start a RG Last Call for: > "Coding and congestion control in transport" > https://datatracker.ietf.org/doc/draft-irtf-nwcrg-coding-and-congestion/ <https://datatracker.ietf.org/doc/draft-irtf-nwcrg-coding-and-congestion/> > > The call will end on Monday May 31st (3 weeks). > > Please read it and provide feedback on the mailing list. Thanks in advance. > > Regards, > > Marie-Jose and Vincent