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

"Su, Chi-Jiun" <Chi-Jiun.Su@hughes.com> Wed, 11 December 2019 14:49 UTC

Return-Path: <prvs=02484527b9=chi-jiun.su@hughes.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 7C41F120119 for <etosat@ietfa.amsl.com>; Wed, 11 Dec 2019 06:49:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hughes.com header.b=i3qN4T6W; dkim=pass (1024-bit key) header.d=hughes.com header.b=GCNeyNkl
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 hC6_BZ_MD509 for <etosat@ietfa.amsl.com>; Wed, 11 Dec 2019 06:49:40 -0800 (PST)
Received: from mx0a-00115402.pphosted.com (mx0a-00115402.pphosted.com [148.163.150.3]) (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 7B9A6120137 for <etosat@ietf.org>; Wed, 11 Dec 2019 06:49:40 -0800 (PST)
Received: from pps.filterd (m0118426.ppops.net [127.0.0.1]) by mx0a-00115402.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id xBBEhqXH031944; Wed, 11 Dec 2019 14:49:40 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hughes.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=3152018; bh=ntYP1NW27+w+ofbftZrTBK9Ay81ehxEqgiIgfrE5IhY=; b=i3qN4T6Wy2Sz/jOg3sqYMFu3Arzg9QViEliaoAEYLnfbNtHu1FyFxht1u79974RUHxCJ sxXxUW4mt36xuq0YbSxD6Rjo2HOGJxsiXrBvqB2CWRSiU1oGH6lfF7NX9m7za56msqCT o2uKfeKHKYDKgqniIirvLVHL5ImVG0+Em5E2uMpLbbkmcxIhJGc2x3btPqzm0LXUTtnV U6Zt3NZRixXgXScsw8qH73RQ5CuTVE14lRBQVKsJrQvYNhgzNGIRwv8NkQdqe0fL9VAG fPPVYgt07lL+IyjZ0PGkwxfKH/GcvpugSWzPZ4xvJd+EYheEectuNlAp4w6Pfi3nbjD5 TA==
Received: from nam02-bl2-obe.outbound.protection.outlook.com (mail-bl2nam02lp2059.outbound.protection.outlook.com [104.47.38.59]) by mx0a-00115402.pphosted.com with ESMTP id 2wtehxws8t-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 11 Dec 2019 14:49:39 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FBjjQbUYbFexBWuozRXk+9TqUKJYdD4Cq1jJXrhQZ/qK6tfP7gSFGJNwup0uRC9I55o8Z7v/0Fdwo1Gx0D9GGfp0mtpNcjt9GR2tUOddsloB69lniopq5TADP71su1ZHxFtMja6lOPtqI2enafFMLpNWD0IMtTQPaslIHmZXRnBDzIwe1opud8DEbFM7Y2ZhY5EYj855wq4t+AaNnmi8kmf9axMuZjvXqsi6UN+8LlH2TYCXur6eJTx1swzxicrLZ1R6t5Nh8FVWjgr1tY2CqFQiIzO2QSMi7YsDcWu4W6hrrG+QqeUoMJOGg0wMNPzxRhVNP1of/EAuN/jw+7usLQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ntYP1NW27+w+ofbftZrTBK9Ay81ehxEqgiIgfrE5IhY=; b=GLUP3P3HfQmPBz1RwRZt+Kq/dGWiPy5J3136dUrDOAAzAvh33O2rfkNODlWP0P7Ifyhc5filrpBGlmbYtt5uZoaOJ7XCZOWQIcdj1MS73gOa6+rSTMaavTleMxlSzQZrMAzhke/ude4ric7FPJRLK8mrzHqfCjNiFc/JuoD0CsrMqOVuwxgqipxeLt2vWSYJFB9D5JvxvSo2t/DIrnlm4rn+nw2cw9Vqy5UkcrQldIXGg1zudaQLOQRxCIt6mq8bk0ZaopskVaoFO/JfGdzjk0zZSyKtYzDIv8sprMUPv9rfgTjmKbjujKBGfg0AtwBOrb7ZHHUDvjupcHKatnI6NQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=hughes.com; dmarc=pass action=none header.from=hughes.com; dkim=pass header.d=hughes.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hughes.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ntYP1NW27+w+ofbftZrTBK9Ay81ehxEqgiIgfrE5IhY=; b=GCNeyNkljmkEOtffoPqLnkAPDlE7QguefHc5SdLhYQ4frkkYCEUv41+m+MdThhNXoU1bdPjQpMl0hyCPWBhtKDasQxYlCtKr7+jp8QlEZHf0aTS7E/52Def6KR0Ae/B0pu4vy5Jbvkn/7p1Kqj2DXABdGrdkc0PRh9ceWqUIvHk=
Received: from BYAPR11MB3078.namprd11.prod.outlook.com (20.177.225.85) by BYAPR11MB3736.namprd11.prod.outlook.com (20.178.237.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2516.12; Wed, 11 Dec 2019 14:49:36 +0000
Received: from BYAPR11MB3078.namprd11.prod.outlook.com ([fe80::dc3f:3a8d:5316:f9a3]) by BYAPR11MB3078.namprd11.prod.outlook.com ([fe80::dc3f:3a8d:5316:f9a3%5]) with mapi id 15.20.2516.017; Wed, 11 Dec 2019 14:49:36 +0000
From: "Su, Chi-Jiun" <Chi-Jiun.Su@hughes.com>
To: "Morten V. Pedersen" <morten@steinwurf.com>, "etosat@ietf.org" <etosat@ietf.org>
Thread-Topic: [EToSat] What we are looking for from QUIC
Thread-Index: AdWqBvqSpD0dZHfeQqedFPfMiHoxPwEe5tAAAARH8DAACdnqgAA1zDegAAJm3IAAJWjm4A==
Date: Wed, 11 Dec 2019 14:49:36 +0000
Message-ID: <BYAPR11MB3078177B24AB04D3282EB805CE5A0@BYAPR11MB3078.namprd11.prod.outlook.com>
References: <SN6PR11MB308798A993C4C67CF898A4E5CE580@SN6PR11MB3087.namprd11.prod.outlook.com> <5D6C8912-FF49-4C03-886B-C4509DA7EA16@huitema.net> <BYAPR11MB30789EC9EF9F6F9725845F4DCE5B0@BYAPR11MB3078.namprd11.prod.outlook.com> <01cee9b3-7cc9-d051-1afc-b669d32cec29@steinwurf.com>
In-Reply-To: <01cee9b3-7cc9-d051-1afc-b669d32cec29@steinwurf.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [139.85.223.11]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 89fe3491-0547-42c7-db50-08d77e4957db
x-ms-traffictypediagnostic: BYAPR11MB3736:
x-microsoft-antispam-prvs: <BYAPR11MB373688FE960A0D18387AE43FCE5A0@BYAPR11MB3736.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 024847EE92
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6029001)(136003)(366004)(346002)(39860400002)(376002)(396003)(51444003)(189003)(199004)(51914003)(13464003)(52536014)(86362001)(478600001)(8936002)(966005)(66476007)(2906002)(110136005)(66446008)(66556008)(316002)(64756008)(8676002)(9686003)(5660300002)(6506007)(186003)(55016002)(26005)(7696005)(76116006)(66946007)(81166006)(81156014)(33656002)(53546011)(71200400001)(562404015); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR11MB3736; H:BYAPR11MB3078.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: hughes.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: YAiCz1LmrGVsjZa5bpai54cz0KQfUiSuCRHo02FRrG0QPS1dxzDj0UatFTTpUBqFXipOwyvyenzw23xS5odFsuKpz9t4kg3+F2+Qtzq8ixuBFSFfokygCJqHG4dn9grRXUJGsVkcolhC9ddw9WT0z18ws4l1rptG5bf7EPFQaBrOYetn0hI7yhSzyfiIEiAKKIm+fGEUUSQB7wbtk646FGGvbYJSyHeBrnf9l6Cim8/GXNrOsQ7kAP+w47MZd2yOD8suxfVp6kcqqVULiG7jKaSLKSOv6E0KSci3+cUTjDRaaUVVdsCZaG3eCuPG8n1FvRbZhRuzGGWymXpikAiY4nJ5U3tOlu8yHIYxXnXhB+NRdfdFMwwiMWNb94sgsqomXi8qpvO1AmM/scQaWpYyPpcH2BGfUCZNrRtCw2HX84XVg9RHq1aU3TBe2uVnvba8fV8EOleaHwBI3H0GClLT16upRIN5oyBYmF3WIvdHfS4Stl7PfTG3zpqGn5PoLQG4prga20dQe7Wo0LJQ5AC00duzE7nQL2/aWmxxjanxKlJDDP1HImz6YZqASmaPoxdfiUQtGzNLjp9U6jFadsUr8WU7JIWcb+K/3bd5+JlC9T0=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB3078177B24AB04D3282EB805CE5A0BYAPR11MB3078namp_"
MIME-Version: 1.0
X-OriginatorOrg: hughes.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 89fe3491-0547-42c7-db50-08d77e4957db
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Dec 2019 14:49:36.6893 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0e1f3187-4610-4ce2-bad1-b92f4ba36ab3
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: bC1JLA8Tlq4m5wuv334J2ylByBaiUhsrczIoU9NxQ4zJT8ikBiCzMN9Qrluw8L69mUq7nSW5miAmOWm/Q5lziA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3736
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-12-11_03:2019-12-11,2019-12-11 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 clxscore=1015 phishscore=0 priorityscore=1501 suspectscore=0 bulkscore=0 mlxlogscore=999 mlxscore=0 lowpriorityscore=0 impostorscore=0 spamscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1912110126
Archived-At: <https://mailarchive.ietf.org/arch/msg/etosat/RUCzSvpX-TpoFByxGZJ9XtERRiw>
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, 11 Dec 2019 14:49:44 -0000

Here are links to packet level FEC, XOR and beyond.

RFC 5109
https://tools.ietf.org/html/rfc5109

Francois Michel’s MS thesis
https://dial.uclouvain.be/memoire/ucl/fr/object/thesis%3A14650/datastream/PDF_01/view
page 29 describe XOR.


From: EToSat <etosat-bounces@ietf.org> On Behalf Of Morten V. Pedersen
Sent: Tuesday, December 10, 2019 3:54 PM
To: 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.

Dear all,
Thanks for your input.

@Christian Thanks for the paper - I will carefully go though it. It looks like a really nice motivation why coding is useful in multicast / broadcast scenarios.

For multicast I would say that the gain of coding should also be present even if the receivers have no packet loss, but simply are blocked from time to time (this creates a discrepancy between the N receivers) which would be costly to fix with a retransmission based system.

I have one question on the encoding you describe, you write that it can be done with with XOR and shifts alone. Could you provide some more details on that?

@John & CJ: In general I think that makes a lot of sense for point-to-point links. You would typically use packet level FEC to avoid retransmissions in which case you add redundancy on the link and if you don't needed it - well then it is essentially wasted bandwidth.

All the best,
Morten
On 12/10/19 8:50 PM, Su, Chi-Jiun wrote:
From Christian’s paper, the first two cases where use of packet level FEC provides benefits are in satellite communication.


“There are in fact at least three environment where the reduced error rate proves very valuable. When multicasting data toward large groups, even a small individual error rate per recipient may result in large retransmission rates for the whole group and the use of redundancy will result in dramatic efficiency gains. In the case of long transmission delays, the use of redundancy helps maintaining the delivery delays within acceptable limits, even in presence of errors. When the receivers do not have enough memory resources to implement sophisticated retransmission techniques, forward error correction can compensate the relative inefficiency of cheap algorithms of the go-back N family.”


From: EToSat <etosat-bounces@ietf.org><mailto:etosat-bounces@ietf.org> On Behalf Of Christian Huitema
Sent: Monday, December 9, 2019 1:05 PM
To: Su, Chi-Jiun <Chi-Jiun.Su@hughes.com><mailto:Chi-Jiun.Su@hughes.com>
Cc: Morten V. Pedersen <morten@steinwurf.com><mailto:morten@steinwurf.com>; etosat@ietf.org<mailto: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.
This reminds me of the "case for FEC" paper that I wrote a long time ago. The abstract is here: https://link.springer.com/chapter/10.1007%2F978-0-387-34986-2_8<https://urldefense.com/v3/__https:/link.springer.com/chapter/10.1007*2F978-0-387-34986-2_8__;JQ!!Emaut56SYw!ghR40lR1fPlxTxd2FAQ-A_MS23aqVeE3QWHRTwu4oXqBld0WqeiQZEFO8RA2UrI3xw$>

My copy of the text, in Postscript, is here: http://huitema.net/papers/case4fec.ps<https://urldefense.com/v3/__http:/huitema.net/papers/case4fec.ps__;!!Emaut56SYw!ghR40lR1fPlxTxd2FAQ-A_MS23aqVeE3QWHRTwu4oXqBld0WqeiQZEFO8RClCMWs_Q$>
-- Christian Huitema



On Dec 9, 2019, at 3:31 AM, Su, Chi-Jiun <Chi-Jiun.Su@hughes.com<mailto:Chi-Jiun.Su@hughes.com>> wrote:
Hi Morten,

John may respond to you when he is available.
I work in the same company as John.
Yes. You're right more or less.

- large window requires allocation of memory.  The number may be significantly huge for a server serving tens/hundreds of thousands of connections.
- FEC adds overhead in transmitted bytes and delay in encoding and decoding of FEC in addition to computational resource requirements.

Hope it answers your questions.
Thanks.
cj

-----Original Message-----
From: EToSat <etosat-bounces@ietf.org<mailto:etosat-bounces@ietf.org>> On Behalf Of Morten V. Pedersen
Sent: Monday, December 9, 2019 6:20 AM
To: etosat@ietf.org<mailto: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.

Hi John,
Could you elaborate on the point below:

--------------------------

On 12/3/19 7:43 PM, Border, John wrote:


We are looking at FEC to help with the packet loss problem and large
windows to address the throughput problem.  Since enabling FEC and
very large windows (especially initial windows) will not be good
defaults for general use, we need some sort of learning capability to
know when they should be used.

--------------------------

Is it because of computational complexity or similar?

All the best,
Morten

_______________________________________________
EToSat mailing list
EToSat@ietf.org<mailto:EToSat@ietf.org>
https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/etosat__;!!Emaut56SYw!jbhJ11p7YT7--EvCJ88bLI55OqJl1kcHQ46EEnS7wGZdk3cJCgFk3JMytIjk4Fi9Cw$<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/etosat__;!!Emaut56SYw!jbhJ11p7YT7--EvCJ88bLI55OqJl1kcHQ46EEnS7wGZdk3cJCgFk3JMytIjk4Fi9Cw$>

_______________________________________________
EToSat mailing list
EToSat@ietf.org<mailto:EToSat@ietf.org>
https://www.ietf.org/mailman/listinfo/etosat<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/etosat__;!!Emaut56SYw!ivs3VnRUz1xYDvhqkbCsC-TQv5gp0ltfQMJ9xMReizTkKC0ZhDQN4lsHG9IdRCTWEg$>



_______________________________________________



EToSat mailing list



EToSat@ietf.org<mailto:EToSat@ietf.org>



https://www.ietf.org/mailman/listinfo/etosat<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/etosat__;!!Emaut56SYw!ivs3VnRUz1xYDvhqkbCsC-TQv5gp0ltfQMJ9xMReizTkKC0ZhDQN4lsHG9IdRCTWEg$>