Re: [EToSat] What we are looking for from QUIC

Junho Choi <junho.choi@gmail.com> Wed, 04 December 2019 04:53 UTC

Return-Path: <junho.choi@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 B8F4112008F for <etosat@ietfa.amsl.com>; Tue, 3 Dec 2019 20:53:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.497
X-Spam-Level:
X-Spam-Status: No, score=-1.497 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_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_NOVOWEL=0.5] 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 1Ylt5zQKG0Q8 for <etosat@ietfa.amsl.com>; Tue, 3 Dec 2019 20:53:52 -0800 (PST)
Received: from mail-vk1-xa2f.google.com (mail-vk1-xa2f.google.com [IPv6:2607:f8b0:4864:20::a2f]) (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 3C8D01200C3 for <etosat@ietf.org>; Tue, 3 Dec 2019 20:53:52 -0800 (PST)
Received: by mail-vk1-xa2f.google.com with SMTP id m128so1774440vkb.5 for <etosat@ietf.org>; Tue, 03 Dec 2019 20:53:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=glFnC6MX37BIXLdzCc0NHryind4unML8jZ0JyRZw84I=; b=ovNBIiboAIxU0F1TT9HD3lURrXaSXS2oQrQh+KwYdebZECU0fUxVdrkLpZnp4F54Aa sTJRW9ErXApBPJ15JpLjsy2Zv7a9+0KXPWQkxoaZf2ui/bW3COJlEDABfVEY75D55wxK M3uj9YGrMlrJi00L3ivfRiCqtnr7XibtyU/jH4iPH+ddRJqTVpQUWlbq5D6Gt9hORLf7 0dk5ljDxAcN04H1iKqzRIacrePxgheTzjNL3XhbcXuSu/QbWgsgyvULrXYrV+D1mKt5o ASSPwO7E7HH7xbKbGHZMTTIKuQ87SUXI1MfX3O9bcPBq1fXsWmuPc2KxoeltxlkbKd6J yJyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=glFnC6MX37BIXLdzCc0NHryind4unML8jZ0JyRZw84I=; b=tj3OEV/h4urh9ykAtiljRAugy7UpdWCp1Ukgiyf1SLpqmLOY8CFDXmd0A3XkvLm9yZ gHTWTN+8FbYXPu+iy8m3uOc2zYaGvU/OLoUdDlpQGx6dZZlDPDK58RZrFGtz4FHihL9N QiGtkfoynLUvAL1BLb+QV1OtqTm+ylwGZ/+dWa5AvXGDrOuW5cEs7N2lVOt/+zJ7tn3W UTYz21R9x0oE5w+rHhg9KXIX/b8IhyCfD7bO7D0bmpXKZ+qicSs4kC+1pWnKI0/2DYfM PIsa+ngpm7zp4EIM9TMn7vvCf7yedNW0iYFJ4ch/zJGw5d4SuITJ7ibBDsK57GrlPA5g +Ylw==
X-Gm-Message-State: APjAAAU2w+Gmh0udgeUTgupWaG/yBhz8TJ8truISHgxM3l60B6tbOmjK yV6HhfnZPsBzQTYepoF6rNDuvctnW+ZvKbqCEU8=
X-Google-Smtp-Source: APXvYqytwr0ceuVeUNN/XmMMIXGD1RPSISzfmQEoGcgvFzK1U9GHC64JzDll3DKbqowWkaG+oIRvOBlV/niJRg9y4HY=
X-Received: by 2002:a05:6122:319:: with SMTP id c25mr871618vko.26.1575435230952; Tue, 03 Dec 2019 20:53:50 -0800 (PST)
MIME-Version: 1.0
References: <BL0PR11MB3394354FD21C86492999FB8590420@BL0PR11MB3394.namprd11.prod.outlook.com> <CAJ5e+HCjai4Z+Cqddo3FDNDnKO_Lpow=T_JfB0+LJ_6JXEuPwQ@mail.gmail.com> <SN6PR11MB3087D0B3421F93B42A2B6C49CE5D0@SN6PR11MB3087.namprd11.prod.outlook.com>
In-Reply-To: <SN6PR11MB3087D0B3421F93B42A2B6C49CE5D0@SN6PR11MB3087.namprd11.prod.outlook.com>
From: Junho Choi <junho.choi@gmail.com>
Date: Tue, 03 Dec 2019 20:53:14 -0800
Message-ID: <CAJ5e+HC9aH0s20Mbeo63Ei7h5cgmEn_1s4FuWNeL_4CDy98jjg@mail.gmail.com>
To: "Su, Chi-Jiun" <Chi-Jiun.Su@hughes.com>
Cc: "Border, John" <John.Border@hughes.com>, "etosat@ietf.org" <etosat@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004ec2ab0598d99969"
Archived-At: <https://mailarchive.ietf.org/arch/msg/etosat/9Sleh6_auJGxQlcZ5z4sHvCV-Ag>
Subject: Re: [EToSat] What we are looking for from QUIC
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: Wed, 04 Dec 2019 04:53:56 -0000

Thank you guys, it's very helpful! I will take a look.

Best,

On Tue, Dec 3, 2019 at 5:39 PM Su, Chi-Jiun <Chi-Jiun.Su@hughes.com> wrote:

> This thesis and the references therein should provide basic idea of tcp
> spoofing (tcp proxies).
>
> https://drum.lib.umd.edu/handle/1903/6106
>
>
> https://drum.lib.umd.edu/bitstream/handle/1903/6106/MS_99-10.pdf?sequence=1&isAllowed=y
>
> some more math
> http://web.eecs.umich.edu/~mingyan/pub/JCC04.pdf
>
> cj
> Navid Ehsan*, Mingyan Liu
> <http://web.eecs.umich.edu/~mingyan/pub/JCC04.pdf>
> server–client RTT. Our analysis, therefore only applies to situations
> where there is a cache miss. 2.2. Assumptions and parameters We assume that
> a file contains exactly M segments of the
> web.eecs.umich.edu
>
> drum.lib.umd.edu
> <https://drum.lib.umd.edu/bitstream/handle/1903/6106/MS_99-10.pdf?sequence=1&isAllowed=y>
> M P IJ^KI NM ME IKT P IO5fPUxK LNJ hs r U O HNM O%m J^ { Ux nUz n ot ^W'<
> AO I ^KIJ fD ` P AO I ^ rHNMLNM O otmE r ot MP L P r NM N B s K{ 5Lpm J^ V
> yUxL M O O Iop NM n J^L opLNJ ] IO%mD IJ^ h NJ opLNMEKI
> drum.lib.umd.edu
>
>
>
> ------------------------------
> *From:* EToSat <etosat-bounces@ietf.org> on behalf of Junho Choi <
> junho.choi@gmail.com>
> *Sent:* Tuesday, December 3, 2019 7:08 PM
> *To:* Border, John <John.Border@hughes.com>
> *Cc:* etosat@ietf.org <etosat@ietf.org>
> *Subject:* Re: [EToSat] What we are looking for from QUIC
>
> *CAUTION:* This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
> On Tue, Dec 3, 2019 at 10:43 AM Border, John <John.Border@hughes.com>
> wrote:
>
>
>
>      With TCP spoofing, we can currently achieve very high speeds (e.g. >
> 200 Mbps).
>
>
> Sorry for newbie question but where can I find more information on TCP
> spoofing and how it can improve long-haul network performance?
>
> Thanks,
>
> --
> Junho Choi <junho dot choi at gmail.com
> <https://urldefense.com/v3/__http://gmail.com__;!!Emaut56SYw!gFqcg39rPXq4EDxtSDfvwc6kmTTdXBZ-kFJ_SvE8j1rdhCfaVQiLXom0rV1JmH-9jA$>
> >
>


-- 
Junho Choi <junho dot choi at gmail.com>