Re: Explicit measurability in the QUIC wire image (was Re: Packet number encryption)

Christian Huitema <huitema@huitema.net> Thu, 08 February 2018 00:37 UTC

Return-Path: <huitema@huitema.net>
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 A4B25126DED for <quic@ietfa.amsl.com>; Wed, 7 Feb 2018 16:37:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 JkyHbcTt7yYw for <quic@ietfa.amsl.com>; Wed, 7 Feb 2018 16:37:33 -0800 (PST)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 E7BED120721 for <quic@ietf.org>; Wed, 7 Feb 2018 16:37:32 -0800 (PST)
Received: from xsmtp03.mail2web.com ([168.144.250.223]) by mx35.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1ejaDN-0003lU-Le for quic@ietf.org; Thu, 08 Feb 2018 01:37:26 +0100
Received: from [10.5.2.52] (helo=xmail12.myhosting.com) by xsmtp03.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1ejaDG-0005Bf-Q6 for quic@ietf.org; Wed, 07 Feb 2018 19:37:19 -0500
Received: (qmail 1205 invoked from network); 8 Feb 2018 00:37:18 -0000
Received: from unknown (HELO [192.168.200.68]) (Authenticated-user:_huitema@huitema.net@[72.235.171.77]) (envelope-sender <huitema@huitema.net>) by xmail12.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 8 Feb 2018 00:37:18 -0000
To: quic@ietf.org
References: <CABkgnnVyo3MmWtVULiV=FJTnR528qfY8-OmKGWAs0bCvri-a_g@mail.gmail.com> <2CD9DC43-D69B-43F0-8474-DFE798850A52@akamai.com> <CAGD1bZaUuNxqpDkn62B0wWcFD8=mCUWrAwWGG-rAOxH7Mf1=cQ@mail.gmail.com> <CY4PR21MB01334E30C7AF6AE75F58EEFDB6FE0@CY4PR21MB0133.namprd21.prod.outlook.com> <CAGD1bZaxrqzdkk0wxRaULwOTgg6wnrSrXNBK31s4uxdozaACBA@mail.gmail.com> <CAGD1bZbOAaSBcQw4nVtGuwRunaAW8MYHq9yPxNN6DdKHzt5HtQ@mail.gmail.com> <CANatvzx+uDHMV5XS=OuVYBqe_RYX=EmVWAmjuONS8BpNYCPweA@mail.gmail.com> <5233815B-00F3-4961-ABB8-505906258B89@trammell.ch> <CAN1APdcuKSLYw4Odyc4g=+4_+ojsNekeqmM9eYqxykkfxRx3Cg@mail.gmail.com> <CANatvzz3rmGPRgu1Z5+bAHhgjiN3L5OVTDhb4fmpPX+M8o4z3w@mail.gmail.com> <DB6PR10MB17661B9957DF90733FA28EC5ACFD0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <DB6PR10MB176682C63A91007574BBEAECACFC0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <CAN1APddkFxLFREQQe+0Kqqi+zJeU20ALjzN4R0Muf9FD1BzZUg@mail.gmail.com> <CANatvzw3RFekoHx_MJWkDY0Q+G2gUNshpocozwkQWpH8sqnnTA@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <0828f8d4-e8cc-c4be-6062-6e9fe843f849@huitema.net>
Date: Wed, 07 Feb 2018 14:37:17 -1000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CANatvzw3RFekoHx_MJWkDY0Q+G2gUNshpocozwkQWpH8sqnnTA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Subject: Re: Explicit measurability in the QUIC wire image (was Re: Packet number encryption)
X-Originating-IP: 168.144.250.223
X-AntiSpamCloud-Domain: xsmtpout.mail2web.com
X-AntiSpamCloud-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-AntiSpamCloud-Outgoing-Class: unsure
X-AntiSpamCloud-Outgoing-Evidence: Combined (0.37)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5rtF0XixPV2jHdgxufwKyZ4Xv9krsgRhBn0ayn6qsUc7A2kcKDr1fzRm ksYYe0sWHrgNzB/4Jkrw1eDLcif59fvgZfXHVShMJl4RfsV9JAzrB98yDTitFWvbHwz9vKZpm/D1 Ad4OAlzgsEH8ABk9OXtTPSw+CekCTYoDa8nAx3W5ZsQEbaxxISMHgJxrdMdSS4B6hVJPXxgisa+g wkHvC+PVG1YjIrFRKhESMT/tU1Dx+IHaAZrg1ulFniksjLYqZxdG5bOwa1rOgT+89+/XFrGt2tce crpXRY6fm8RXptyzavERpop5LF7RavHozgbn9XzprFRbpFQTOcEGeQOY3IcDlgJpEbxunV7tCPNi PQvHQpVRoYcix47lJTuKsG8TgnDHFRDF834rtLc6Wv9Yj+vBPX9bzGJi0ycLbiOUDEySIK/1NH5T HMtlYvyHAYGOGheVSH7cGoIH3Vd41lbD31WoCGUWNgo50bBZN3FfqI2VItAPyqRyV95ZNrHd7vkN RnCZrsXthqMpjY8hecAMutnh9PobrbwB1Jj4vRnvuFdQKx3Zprq3ZEpafGy+zLjUntilh9dvYvV/ 5Pg3UZt3l4cobM5+AwD0A5qDgSPsXJ3Goyp65o39wd3xyIqswrw4YJnHEeB4hpRrmo/duzUUp/L9 UD9MCYFan2eRHD4U+beDmq4NFZuQJnJJRLxixstHPXLYM3A6BXfvel8OEFDbU529jj6VuEkkQiOd 2CLFCAI+0EF5F4XJDGest21JnLKg8Ij2lB9TLiDMfXuvSrucRXpoVg5fOhUS7LnGpWowDQkTpsib JQz6bCR19sO/++nnSqCDBedeB75TJ0VuxRY+unEnaeycva4NRXu2m3j3Y8zB9xGo0bndvIE+SDBs cm+vLiZuZ5OAUoGBziSYFLZuu6wTRhJez+ibxiREoUwadL3g
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/laUgeD2KwNCcwNYztCHQM9fzZnw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 08 Feb 2018 00:37:40 -0000


On 2/7/2018 1:10 AM, Kazuho Oku wrote:
> The pros of using a sequence that randomly distributes 0 and ones
> (i.e. PI or xorshift+) is that you can extract good loss / reordering
> information if the error rate is low.
>
> OTOH, it is fragile to high error rate or certain patterns of error.
> Let me explain two examples.
>
> Consider the case where the packet loss rate is 50%. I doubt if you
> could use pattern matching against those sequences to figure out the
> loss rate. This is because the power among the sequence is mostly high
> frequencies. If you use a sequence that distributes power among lower
> frequencies (like square wave or sin wave that I discussed), you can
> calculate the loss rate in such cases as well.

Actually, it should be possible to build a maximum likelihood decoder
for an xorshift sending pattern. You are mostly concerned with erasure
and permutations, and you roughly know the range of probability, so you
can see likelihood of 1, 2, 3, etc. erasures, or permutations in some
range. Obviously, the range that you can manage depends on the length of
the code. If you can keep the decoder synchronized, you will be able to
measure the erasure rate. If it looses synchronization, you know that
the error rate is truly horrendous, and that's information too. And
xorshift codes are self synchronizing, so you will regain
synchronization quickly.

-- Christian Huitema