Re: [EToSat] Transport in 0-RTT connections for high BDP
Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com> Thu, 07 March 2019 14:03 UTC
Return-Path: <mikkelfj@gmail.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 5F406127961; Thu, 7 Mar 2019 06:03:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 LoyEFabY9SZB; Thu, 7 Mar 2019 06:03:13 -0800 (PST)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 0076E124184; Thu, 7 Mar 2019 06:03:12 -0800 (PST)
Received: by mail-io1-xd2f.google.com with SMTP id r136so13546397iod.3; Thu, 07 Mar 2019 06:03:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=0npKgFarQ1XOlASCtnpZvc0I0D/q+Rza63Zimdm/YYs=; b=lTs5wOdMJG4+O3/O37vI+0R/Ox8+hCKtJQNa9hU4pmYKdgL1foANuks7LsnLfvMNPx SuLAFT6Qsbl3h7hVw7QRvxfA6BhWGGmyr3qtm7yROe1ha9g9tmhl9bP0rt9OCBT4iWWe enlUR+td8h1CSu/DU/13vN/FBCuKd06gOU3G1NYPMwbb5hyl/Lpyjm1A4LZvhAuXO/py i4oZIm0ZAgX+l4UiYg14J9f59xaSd+T8lM/jpQo9eznGOJ2QL366fTpqbtBp9yQY+uzQ DspW0wcUOolmC1gtIjpB6WLGYxiYZNBkg1btFTM0gg6d2IkALYVw1sn1NJ8nam6OXs67 +Qtw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=0npKgFarQ1XOlASCtnpZvc0I0D/q+Rza63Zimdm/YYs=; b=hKyBtBt78BtP2k1HDIIk3GGi5ZknP4WMl1eoUzat5qncIqmf81XrhKOP8be0qzO4FR EHN0hGgx3kXeHWbXg89YH1gkL1Kw3YvFBrep4vlC0ZrHckLDvPSdqRsYgp5+vpA+COKl 9mT3QmUhG9Oq0n3kYObHYkUJ7B0BeGwAoQjRf//XoEagKqTrHXn+ihznzHHZGMzFSP5+ PL7I4bRQrQQdiSB+I7ZJ2fKJPUmxexJNwVCX0pjG+bQ0djYeNUeD0fFAjwRvk5iMzV9Y TRqcQ7reTRgQORxGgDmAMEQCmcBe7UvtHZ/ceL4082G81c59w0V+WgN0FX0Cwr82Rivd /jEg==
X-Gm-Message-State: APjAAAXlgmFjfGHM0RA3CF50rbQwuIpkz0dS8v2gThr1hMXypfs1RK9E NttS6iG2hhOOA/T1NOAnKNhaCorhKGc+paGROdw=
X-Google-Smtp-Source: APXvYqziaSzAJwKySoFwFgpAq0jL+g/VAwf6oH4AKjQAjktSvKxde0PqOj31MwLLFf+LPhdHlxoMCShTlcp1H3xO7VA=
X-Received: by 2002:a6b:5b01:: with SMTP id v1mr6076823ioh.12.1551967392370; Thu, 07 Mar 2019 06:03:12 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 7 Mar 2019 15:03:12 +0100
From: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
In-Reply-To: <CAN1APdfHWaHnP9Dh3uurrPoh8GxDBUjSaa1G75XoWDgPirtmmQ@mail.gmail.com>
References: <F3B0A07CFD358240926B78A680E166FF1EBABEF8@TW-MBX-P03.cnesnet.ad.cnes.fr> <CAN1APde09k5rw678dSjvCofr_syeBNGdGpLm7AfBsHtk6ag=Ww@mail.gmail.com> <20190307133159.GA20802@ubuntu-dmitri> <CAN1APdfHWaHnP9Dh3uurrPoh8GxDBUjSaa1G75XoWDgPirtmmQ@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Thu, 07 Mar 2019 15:03:12 +0100
Message-ID: <CAN1APdfkf0PafCP_Xqsw_QRV29NM83kLKK2_0nG91NMP+xM_ww@mail.gmail.com>
To: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
Cc: "etosat@ietf.org" <etosat@ietf.org>, "quic@ietf.org" <quic@ietf.org>, Kuhn Nicolas <nicolas.kuhn@cnes.fr>
Content-Type: multipart/alternative; boundary="00000000000020153705838191b2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/etosat/VXHvlzTyAshH9wQj81uiEPhV7wg>
X-Mailman-Approved-At: Thu, 07 Mar 2019 07:21:02 -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 14:03:15 -0000
On 7 March 2019 at 15.00.47, Mikkel Fahnøe Jørgensen (mikkelfj@gmail.com) wrote: 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. Yes of course In the context of recent replay attack discussion, this should be interesting.
- [EToSat] Transport in 0-RTT connections for high … Kuhn Nicolas
- Re: [EToSat] Transport in 0-RTT connections for h… Dmitri Tikhonov
- Re: [EToSat] Transport in 0-RTT connections for h… Mikkel Fahnøe Jørgensen
- Re: [EToSat] Transport in 0-RTT connections for h… Mikkel Fahnøe Jørgensen
- Re: [EToSat] Transport in 0-RTT connections for h… Mikkel Fahnøe Jørgensen
- Re: [EToSat] Transport in 0-RTT connections for h… Kazuho Oku