Re: [IETF106] Proposed workshop on QUIC performance over high BDP

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Tue, 05 November 2019 10:12 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FB5B12088C; Tue, 5 Nov 2019 02:12:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 MS0qiq0hE-KT; Tue, 5 Nov 2019 02:12:03 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 524BE12088B; Tue, 5 Nov 2019 02:12:03 -0800 (PST)
Received: from gorry-mac.erg.abdn.ac.uk (unknown [IPv6:2001:630:42:110:e55f:a14f:6fbb:b4cc]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 97E291B001D2; Tue, 5 Nov 2019 10:11:55 +0000 (GMT)
Subject: Re: [IETF106] Proposed workshop on QUIC performance over high BDP
To: Joerg Ott <ott@in.tum.de>, "etosat@ietf.org" <etosat@ietf.org>, IETF QUIC WG <quic@ietf.org>, "iccrg@irtf.org" <iccrg@irtf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Cc: STEPHAN Emile RD-CORE-LAN <emile.stephan@orange.com>
References: <F3B0A07CFD358240926B78A680E166FF1ECE4F1F@TW-MBX-P03.cnesnet.ad.cnes.fr> <314f4a3c-9e56-26b6-fda3-bc2694f75d3e@in.tum.de>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <05fcdc09-4d86-980c-ced7-30fbc544569e@erg.abdn.ac.uk>
Date: Tue, 5 Nov 2019 10:11:53 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <314f4a3c-9e56-26b6-fda3-bc2694f75d3e@in.tum.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/PgMRpashTgLO_oelre2zjHB_P5c>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2019 10:12:05 -0000

Yes, that sounds fun! - which QUIC implementation were you using, just 
so we can make sure we compare like-with-like, and did you use an 
operational satellite system or an emulation, or something in-between?

Gorry

On 05/11/2019 09:38, Joerg Ott wrote:
> Hi guys,
>
> great activity -- we also did extensive emulation studies for QUIC
> over satellites in a controlled environment.  Would be happy to
> share those findings if room.
>
> Cheers,
> Jörg
>
> On 05.11.19 09:57, Kuhn Nicolas wrote:
>> Hi,
>>
>> There are multiple drafts related to the performance of QUIC over 
>> large BDP networks (draft-kuhn-quic-4-sat, draft-kuhn-quic-0rtt-bdp, 
>> draft-ietf-quic-recovery) or related to the performance of encrypted 
>> protocols in general (draft-fairhurst-tsvwg-cc).
>>
>> The objective of this workshop is to gather people interested in such 
>> activity and discuss the best way towards better end user experience 
>> in this use case.
>>
>> Details : https://trac.ietf.org/trac/ietf/meeting/wiki/106sidemeetings
>>
>> Time : 3pm30 – 4pm30 on Wednesday
>>
>> Where : Bras Basah 
>> https://datatracker.ietf.org/meeting/106/floor-plan?room=bras-basah#raffles-city-convention-center 
>>
>>
>> Proposed agenda:
>>
>> Introduction : contributions that showed performance issues with QUIC 
>> over satellite links
>>
>> draft-kuhn-quic-0rtt-bdp : solution to let both client and server 
>> know the path characteristics
>>
>> draft-kuhn-quic-4-sat : what can be done once both client and server 
>> have this information
>>
>> draft-fairhurst-tsvwg-cc : generalization to any transport and best 
>> current practice on internet congestion control at end points
>>
>> If time permits: sharing experimental results (interaction between 
>> transport and high BDP systems)
>>
>> If there is anything you would like to present please let us know.
>>
>>
>> Kind regards,
>>
>> Nico, Gorry and Emile
>>