Re: [EToSat] TR: New Version Notification for draft-kuhn-quic-4-sat-04.txt

Christian Huitema <huitema@huitema.net> Thu, 23 April 2020 05:34 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: etosat@ietfa.amsl.com
Delivered-To: etosat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ED253A1459 for <etosat@ietfa.amsl.com>; Wed, 22 Apr 2020 22:34:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 hltcAQBdOnve for <etosat@ietfa.amsl.com>; Wed, 22 Apr 2020 22:34:26 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 85FE63A1456 for <etosat@ietf.org>; Wed, 22 Apr 2020 22:34:26 -0700 (PDT)
Received: from xse22.mail2web.com ([66.113.196.22] helo=xse.mail2web.com) by mx168.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1jRUVA-0013ZD-2M for etosat@ietf.org; Thu, 23 Apr 2020 07:34:23 +0200
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 4975Zx6d1zz2fv7 for <etosat@ietf.org>; Wed, 22 Apr 2020 22:34:17 -0700 (PDT)
Received: from [10.5.2.17] (helo=xmail07.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1jRUV7-0003up-QQ for etosat@ietf.org; Wed, 22 Apr 2020 22:34:17 -0700
Received: (qmail 11750 invoked from network); 23 Apr 2020 05:34:17 -0000
Received: from unknown (HELO [192.168.1.104]) (Authenticated-user:_huitema@huitema.net@[172.58.43.126]) (envelope-sender <huitema@huitema.net>) by xmail07.myhosting.com (qmail-ldap-1.03) with ESMTPA for <gorry@erg.abdn.ac.uk>; 23 Apr 2020 05:34:17 -0000
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Christian Huitema <huitema@huitema.net>
Mime-Version: 1.0 (1.0)
Date: Wed, 22 Apr 2020 22:34:16 -0700
Message-Id: <EFFE2C3A-7D18-4559-B221-579E6737675E@huitema.net>
References: <BAE60451-8D3A-4C36-A924-B12DC67070C5@eggert.org>
Cc: Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>, "etosat@ietf.org" <etosat@ietf.org>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, "Border, John" <John.Border@hughes.com>, "emile.stephan@orange.com" <emile.stephan@orange.com>
In-Reply-To: <BAE60451-8D3A-4C36-A924-B12DC67070C5@eggert.org>
To: Lars Eggert <lars@eggert.org>
X-Mailer: iPhone Mail (17D50)
X-Originating-IP: 66.113.196.22
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.22/32
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.22/32@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: ham
X-Spampanel-Outgoing-Evidence: Combined (0.06)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0c6d8zDasFm/nDPEg7mmhmypSDasLI4SayDByyq9LIhVOOiy1Ozghezi jm5/fqQ39UTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDYbC1vFNC/qFxauDStI0QV8RX qYbtEQV1z/L435ZRxFR/3K7zyCBPVdQIgS4MPmMC+rYZvu7UEJiU3s27VgKHO7lwS3dBJTnTxDoD vBGGxph9w6EwXICYy0ePXtGEMhqrAl7yqJ0XTcW1wfUEo6fP12U6UgOqKJ9sMwhVoOBGSAIZmL0k TGIVN3DthM1B8FVxuy8lNDS0QWWkADhl7glCR9PbrhSmW22tW1yBxgRT8bmxZJSIFVPkVVALPRKr lHlM3kWCH4Q79vaQ+COHDJAgLHQOD0r6/AaHZiEtdTMtMlgTBUa5LSawQcdT80HH17nNg8oiq9mz mwrbQbTulSg7juWBOXp8nHKe0R+FkIqN7hkFZqA6TBkpoO/ktnXt0JlLIRFsicyJMEhQFtD8PLoi nuxTyssp4L0plUGigax8zy4LpVxP5YFZg5fgueXLf6LKHDJ71JSXKkUqfqsTqwEEUOidX4Ts4xdG +C13IyWeZaLav7A+Uka4T0EWpWGeiDY04nuZrRf7bMi0WRR6pZ+nWYkz0vK0J/mUarIW+DdCdS8z 7Vu2PZFHkJEE/wqpNG6eC79opvvAYzM67TQJHmLZ4WkvZ+pWP1s35neRYWMQUWZErSs0X3oyoTc8 j/o7qulxPZFIoGhcS2mzqvB/oEoIQFACVO3tx78u0bG7If2TCVRB6X2gm+eQYyypkOMd6JONRlWO mx7s8sXU09SCA8pFpFffncYFDRVcOLM39ai6q8tr4Weped4Vi7unz95FFRsgJOYIJd4MvQ0Nf4Ec bvHO1diDanHV9KirFAIIecsyj+YNTo81GR+jDXFsz/ZQnbbTizvwlZsrbltGiZoUh+c+5pFVgpT1 b21uZVckGp0ccOa2XhkGbmsUNPNkere1WheNsVXmhO8BzADiszcWR9bz/SDtF09JpSbuuCeiIDK0 C/0=
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/etosat/Iu-sagsp5mNRU9ogQ0f1Yl5PT6I>
Subject: Re: [EToSat] TR: New Version Notification for draft-kuhn-quic-4-sat-04.txt
X-BeenThere: etosat@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "The EToSat list is a non-WG mailing list used to discuss performance implications of running encrypted transports such as QUIC over satellite." <etosat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/etosat>, <mailto:etosat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/etosat/>
List-Post: <mailto:etosat@ietf.org>
List-Help: <mailto:etosat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/etosat>, <mailto:etosat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Apr 2020 05:34:34 -0000

I don't. I could probably do a parallel flow test, but I don't have the TCP simulation ready. Basically, I have been starting with the test cases in the quic4sat draft.

In theory, parallel flows are easier, not harder, because each flow has a smaller BDP than if it were alone. But fairness is much harder to achieve with long delay links. In TCP fairness is a statistical property, measured over some time. But in our cases the whole transfer is over in a half dozen RTT, and that does not leave much time for the statistics to play out. If we do desire fairness, my suggestion would be appropriate AQM in front of the satellite link.

-- Christian Huitema 

> On Apr 22, 2020, at 10:09 PM, Lars Eggert <lars@eggert.org> wrote:
> 
> Hi,
> 
> do you have measurements with multiple parallel flows and/or competing TCP traffic?
> 
> Thanks,
> Lars
> 
> -- 
> Sent from a mobile device; please excuse typos.
> 
>> On Apr 23, 2020, at 06:05, Christian Huitema <huitema@huitema.net> wrote:
>> 
>> Something related: I have been working for some time on how to
>> accelerate the "startup" phase of a QUIC connection over satellite. The
>> main changes in Picoquic are:
>> 
>> 1) If the measured RTT is large, scale up the initial Window. We
>> discussed this in Singapore.
>> 
>> 2) Tweak the pacing algorithm so Picoquic can send data bursts
>> (moderately sized)
>> 
>> 3) Implement a peak bandwidth measurement by looking at acknowledgements
>> over time, and noticing peaks when data bursts are acknowledged
>> 
>> 4) During start-up, increase the congestion window if it is smaller than
>> 1/2 peak-bandwidth times RTT.
>> 
>> With that, the test of sending 100MB on a 250/3 Mbps link completes in
>> 5.2 second, of which 1.2 seconds are the connection set up RTT and one
>> RTT to request and ack the file. That means the actual transfer lasts 4
>> seconds, average rate of 200 Mbps, 80% of the capacity.
>> 
>> Details on how the experiment progressed at
>> https://huitema.wordpress.com/2020/04/21/faster-slow-start-for-satellite-links/.
>> 
>> -- Christian Huitema
>> 
>>>> On 3/6/2020 7:53 AM, Kuhn Nicolas wrote:
>>> Hi,
>>> 
>>> We have just pushed an updated version of the "QUIC 4 SAT" document. 
>>> The main difference with the previous version is that we have proposed baseline values for the regression test for the performance of QUIC on SATCOM systems. 
>>> 
>>> We plan a side-meeting during IETF107 where we will present the rationale behind these numbers and recent experiments on QUIC over SATCOM systems.
>>>   Monday 23rd 
>>>   8:30 am 
>>>   Room: Regency E
>>> 
>>> If you are interested by remote participation, please join the ETOSAT mailing list where we will share conf call details. 
>>> In the meantime, do not hesitate if you have comments on this version of the document. 
>>> 
>>> Cheers, 
>>> 
>>> Nico - on the behalf of the authors 
>>> 
>>> -----Message d'origine-----
>>> De : internet-drafts@ietf.org <internet-drafts@ietf.org> 
>>> Envoyé : vendredi 6 mars 2020 16:43
>>> À : Gorry Fairhurst <gorry@erg.abdn.ac.uk>; Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>; John Border <border@hns.com>; Godred Fairhurst <gorry@erg.abdn.ac.uk>; Stephan Emile <emile.stephan@orange.com>; Emile Stephan <emile.stephan@orange.com>
>>> Objet : New Version Notification for draft-kuhn-quic-4-sat-04.txt
>>> 
>>> 
>>> A new version of I-D, draft-kuhn-quic-4-sat-04.txt has been successfully submitted by Nicolas Kuhn and posted to the IETF repository.
>>> 
>>> Name:        draft-kuhn-quic-4-sat
>>> Revision:    04
>>> Title:        QUIC for SATCOM
>>> Document date:    2020-03-06
>>> Group:        Individual Submission
>>> Pages:        13
>>> URL:            https://www.ietf.org/internet-drafts/draft-kuhn-quic-4-sat-04.txt
>>> Status:         https://datatracker.ietf.org/doc/draft-kuhn-quic-4-sat/
>>> Htmlized:       https://tools.ietf.org/html/draft-kuhn-quic-4-sat-04
>>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-kuhn-quic-4-sat
>>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-kuhn-quic-4-sat-04
>>> 
>>> Abstract:
>>>  QUIC has been designed for use across Internet paths.  Initial
>>>  designs of QUIC have focussed on common deployment scenarios for web
>>>  traffic and have not focussed on the performance when using a path
>>>  with a large Bandwidth-Delay Product (BDP).  A path can combine
>>>  satellites network segment together with a wide variety of other
>>>  network technologies (Ethernet, cable modems, WiFi, cellular, radio
>>>  links, etc): this complicates the characteristics of the end-to-end
>>>  path.  One example of such a scenario occurs when a satellite
>>>  communication (SATCOM) system is used to provide all or a part of the
>>>  end-to-end path.  If this is not addressed, the end-to-end quality of
>>>  experience can be degraded.
>>> 
>>>  This memo identifies the characteristics of a SATCOM link that impact
>>>  the operation of the QUIC transport protocol.  It proposes regression
>>>  tests to evaluate QUIC over SATCOM links.  It discusses how to ensure
>>>  acceptable protocol performance.
>>> 
>>> 
>>> 
>>> 
>>> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
>>> 
>>> The IETF Secretariat
>>> 
>>> 
>>> _______________________________________________
>>> EToSat mailing list
>>> EToSat@ietf.org
>>> https://www.ietf.org/mailman/listinfo/etosat
>> 
>> _______________________________________________
>> EToSat mailing list
>> EToSat@ietf.org
>> https://www.ietf.org/mailman/listinfo/etosat
>