IETF Logo Mail Archive

Re: [EToSat] Transport in 0-RTT connections for high BDP

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Thu, 07 March 2019 13:32 UTC

Return-Path: <dtikhonov@litespeedtech.com>
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 772AB1286D8 for <etosat@ietfa.amsl.com>; Thu, 7 Mar 2019 05:32:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 ikOL3n41XwnX for <etosat@ietfa.amsl.com>; Thu, 7 Mar 2019 05:32:09 -0800 (PST)
Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (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 537E71240D3 for <etosat@ietf.org>; Thu, 7 Mar 2019 05:32:09 -0800 (PST)
Received: by mail-qk1-x72d.google.com with SMTP id a15so8991590qkc.1 for <etosat@ietf.org>; Thu, 07 Mar 2019 05:32:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=1yG85yUG9n3ncxIkXZzDXOYqtF64D9+0RcfpC45BtoY=; b=j3xzmcDAamX/fIir5VbETjAtYfVQIFmjJU8oVy2x00psAi3w6zGRIprtMqGwP2u5aY bsugdhH9xNGrtJwUNZ1OzLyGpZh34zf/9BgnApdQk8kvfxUQ9MfEQS8JB5gw+kY68K0o Kf7Pne9ZsPyxSVoXqEOrJVSJILtMy8W0uZHTc/cg86YLTVT/vsm582WcjORrW/MsuIr6 WyMePfp4bTwd8EV1c/52VMJYTsCsmk64zPUPAY+GGHVBfwIzgTthJW9MUX5lTGb7r1gO RgRhDt1U1qvXWcnKQVyIgYn/ZkwLFXUfwg9PmhFbPOEyM54VeQ1H1cMHBSxoF3aT/Ct8 QnMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=1yG85yUG9n3ncxIkXZzDXOYqtF64D9+0RcfpC45BtoY=; b=OywZc5Kdf36wjR9AK7W9VY/h7x76H9LmMK5DjPxf9bp9FXKIX6ZCj5REUenQK8OrsK LOSdzsOeBRE4CC+IBH4LFkTvNpe+PS+zwZ0MbTDzUeX1On4hBDdfjn6cclosMqAG5sbY OrIaK54YJowmkMu6i+c6OaWBMvKr9cIK1nXyljhurlx4ctXov+C3+2z6AFjHzG2Orawj F/7JHWKNmeRbDYazvW7OMgffrvK179bA9RAM7fV3JV1Bv9dNjGkhj5Dgf2lDfsmtBn4p mcvV7UU9qr8pRSeR0ojJdQn6uyik0PtEicYDI7L8Pc5G7UzVcK95vmfZYNdQaQruf8AC bSCA==
X-Gm-Message-State: APjAAAU5WrjNr/W+nxfwzBTFlmYvhmfyCdR5zBsapVcgsT6oB7LSoJRu 7i5T4SPv5tPmRrHgGoBPU7J3WQ==
X-Google-Smtp-Source: APXvYqzLS+L3DhK7AFLKGRqcW6QQ1cHN+y66sImyn0BSIrkU3otUl9KBxGr5sjA2q5dbT0nz1H2xBw==
X-Received: by 2002:a37:4e97:: with SMTP id c145mr9697925qkb.85.1551965528424; Thu, 07 Mar 2019 05:32:08 -0800 (PST)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id h18sm1450041qkj.50.2019.03.07.05.32.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Mar 2019 05:32:07 -0800 (PST)
Date: Thu, 07 Mar 2019 08:32:00 -0500
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
Cc: "quic@ietf.org" <quic@ietf.org>, Kuhn Nicolas <nicolas.kuhn@cnes.fr>, "etosat@ietf.org" <etosat@ietf.org>
Message-ID: <20190307133159.GA20802@ubuntu-dmitri>
Mail-Followup-To: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>, "quic@ietf.org" <quic@ietf.org>, Kuhn Nicolas <nicolas.kuhn@cnes.fr>, "etosat@ietf.org" <etosat@ietf.org>
References: <F3B0A07CFD358240926B78A680E166FF1EBABEF8@TW-MBX-P03.cnesnet.ad.cnes.fr> <CAN1APde09k5rw678dSjvCofr_syeBNGdGpLm7AfBsHtk6ag=Ww@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAN1APde09k5rw678dSjvCofr_syeBNGdGpLm7AfBsHtk6ag=Ww@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/etosat/WcJLeKu27fNfZoHQEPjDgfGQXVg>
X-Mailman-Approved-At: Thu, 07 Mar 2019 07:20:42 -0800
Subject: Re: [EToSat] Transport in 0-RTT connections for high BDP
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, 07 Mar 2019 13:32:12 -0000

On Thu, Mar 07, 2019 at 01:03:47PM +0100, Mikkel Fahnøe Jørgensen wrote:
> That said, I think the bandwidth, the connection RTT, the ticket timestamp,
> and perhaps the PMTU are all good things to have available to an 0-RTT
> session

For example, in GQUIC, the client can send an IRTT tag to specify the
initial value to set the RTT to.

> On the other hand, a client could be caching these data along with a
> session ticket based on knowledge gained from a previous connection, so
> perhaps it it is not really an issue other than explaining best practices?

I think the idea is to allow the server to start blasting away if it
learns from the ticket that the connection has a large BDP.

  - Dmitri.

v2.23.0 | Report a Bug | By Email