R: Spin bit - semantics - rtt and loss

Fioccola Giuseppe <giuseppe.fioccola@telecomitalia.it> Fri, 23 March 2018 09:51 UTC

Return-Path: <giuseppe.fioccola@telecomitalia.it>
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 06DB112D7E8 for <quic@ietfa.amsl.com>; Fri, 23 Mar 2018 02:51:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 hbUkv8GbPg6U for <quic@ietfa.amsl.com>; Fri, 23 Mar 2018 02:51:31 -0700 (PDT)
Received: from mx04.telecomitalia.it (mx04.telecomitalia.it [217.169.121.24]) (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 26B4F12D96C for <quic@ietf.org>; Fri, 23 Mar 2018 02:51:30 -0700 (PDT)
X-AuditID: d9a97918-c47ff70000000252-62-5ab4ce211d0e
Received: from TELMBXB06RM001.telecomitalia.local ( [10.14.252.35]) (using TLS with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx04.telecomitalia.it () with SMTP id C1.F1.00594.12EC4BA5; Fri, 23 Mar 2018 10:51:29 +0100 (CET)
From: Fioccola Giuseppe <giuseppe.fioccola@telecomitalia.it>
To: "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, "Lubashev, Igor" <ilubashe@akamai.com>
CC: "Lubashev, Igor" <ilubashe@akamai.com>, "quic@ietf.org" <quic@ietf.org>
Subject: R: Spin bit - semantics - rtt and loss
Thread-Topic: Spin bit - semantics - rtt and loss
Thread-Index: AQHTwjus7aoj5pwVoECWxZMvp9O9NaPdUocAgAAFugCAABdSAIAAISrQ
Date: Fri, 23 Mar 2018 09:51:28 +0000
Message-ID: <53d89af084d14bb5bfa6ffb348628164@TELMBXB02RM001.telecomitalia.local>
References: <9168a7b6700d49d6b7454f8c91eebce2@ustx2ex-dag1mb5.msg.corp.akamai.com> <8654_1521788108_5AB4A4CC_8654_341_3_5AB4A4CC.6070306@orange.com> <6f4adb4fa23e42cf9f07ecfe9afacf39@ustx2ex-dag1mb5.msg.corp.akamai.com> <24169_1521794346_5AB4BD2A_24169_70_3_5AB4BD2A.5070406@orange.com>
In-Reply-To: <24169_1521794346_5AB4BD2A_24169_70_3_5AB4BD2A.5070406@orange.com>
Accept-Language: it-IT, en-US
Content-Language: it-IT
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.14.252.251]
x-ti-disclaimer: Disclaimer1
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOKsWRmVeSWpSXmKPExsXCxfdHWVfx3JYog8aF/BbLfshbNDWsYLbo WcDtwOwx+cgCZo8lS34yebQ8O8kWwBzVwGiTmJeXX5JYkqqQklqcbKvkklmcnJOYmZtapBCS mpOanJ+rpJCZYqtkrKRQkJOYnJqbmldiq5RYUJCal6Jkx6WAAWyAyjLzFFLzkvNTMvPSbZU8 g/11LSxMLXUNlewCS1OLS/IVclOLixPT0zPzFVIT1gtmrL96l61gkXbFm3dL2BoYe5S7GDk5 JARMJNatvM8KYgsJTGGSWLW9AMRmE7CROPjqBBuILSKQK7F0fTc7iM0s4C3xf/NjMFtYQF9i 1qt1UDWGEpsWngGawwFku0ncnhIIYrIIqEpcbrYBqeAVCJQ4N7+LqYuRC2jTEiaJTze+M4Ek OAX8JSb/fAY2klFAVmLC7kWMEKvEJV5MP8EOcaaAxJI955khbFGJl4//sULYBhJbl+5jgbAV JY62nmaCsGUkFh6ZzAoxR0/ixtQpbBC2tsSyha+ZIQ4SlDg58wnLBEaxWUjWzULSMgtJyywk LQsYWVYxiuZWGJjolUBiL7MkMSczUS+zZBMjMHXcXFkpsYOxe63zIUYBDkYlHt4rh7dECbEm lhVX5h5ilOBgVhLh/T4XKMSbklhZlVqUH19UmpNafIjRBxhiE5mlRJPzgWktryTe0MTC0tDY wsLI0MLMFIewkjjvy5Wbo4QE0oHJKzs1tSC1CGYcEwenVAPjA1+lCMP725TvTlp6/ifrwpwJ Mgx7snUcup9PXvVS+4oY5w2pt8FlCstXvygqePzpssad3gSFNsEH7kyXFK7vZ2ifKpbG2680 Yf+kKx8DREJ8Lm6rbcwVeno4fW/wi7eLC0Tnej45lD31bPDjtbP+hYsemMjx5nfEO5t+zhUb nibVJHtocpX/UWIpzkg01GIuKk4EAKFOF1hKAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/EoKj3RxXpec1wFPScq0xWSV7PpA>
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: Fri, 23 Mar 2018 09:51:35 -0000

Agree and, in general, spin square wave and spin counters can also allow intra-domain loss and delay measurements with the application of RFC8321.

Giuseppe

-----Messaggio originale-----
Da: QUIC [mailto:quic-bounces@ietf.org] Per conto di alexandre.ferrieux@orange.com
Inviato: venerdì 23 marzo 2018 09:39
A: Lubashev, Igor
Cc: Lubashev, Igor; quic@ietf.org
Oggetto: Re: Spin bit - semantics - rtt and loss

Note that the spin counters don't just use more bits ; they also add bidirectional feedback and allow to see loss both downstream and upstream in either direction. And their transmission is robust to any level of reordering and loss.


On 23/03/2018 08:15, Lubashev, Igor wrote:
> Thanks, Alexandre!
>
> Yes, 7 bits would work 64 times better, but it is 7 times more bits.  That's a difference between adding a byte to short packets vs adding no extra bytes.  I could live with both.
>
> The 10-packet square wave was just an initial suggestion (the exact size is minor details, and I actually expect that to be an endpoint configuration option).  It also seems that having an rtt spin bit alongside the square wave should help in detecting losses that exceed a "wavelength" (20 packets in this case), though someone more analytically talented than me would likely be able to tell exactly what benefits an rtt wave adds to the loss estimation.
>
> - Igor
>
> -----Original Message-----
> From: alexandre.ferrieux@orange.com 
> [mailto:alexandre.ferrieux@orange.com]
> Sent: Friday, March 23, 2018 6:55 AM
> To: Lubashev, Igor<ilubashe=40akamai.com@dmarc.ietf.org>
> Cc: quic@ietf.org
> Subject: Re: Spin bit - semantics - rtt and loss
>
> Hi Igor,
>
> Indeed packet loss is important to track.
>
> Your proposal is an instance of the "square sequence" proposed earlier by Kazuho. He suggested a much longer period (hundreds); you're exploring lower values. Each range has issues: too long turns into a large temporal imprecision for sparse flows (like ACKs); too short blurs the signal in case of tail drops (many contiguous losses).
>
> Also, these methods only give upstream losses (between the sender and 
> the midpoint). For this reason we propose a more ambitious 7-bit 
> solution here: Spin Counters
>
>    http://snaggletooth.akam.ai/IETF-101-HotRFC/10-Ferrieux.pdf
>
> Would that help ?
>
> On 23/03/2018 01:12, Lubashev, Igor wrote:
>>  Since we decided to put some work into spin bit, albeit in a 
>> separate  document from V1, here are some thoughts.
>>
>>  It is nice that spin bit can be used to estimate rtt. I am sure that  
>> it is useful to many well-meaning people. It is not very useful to me, though.
>>
>>  When I debug network problems, they are much more likely to be about  
>> lost packets. And I like to be able to know packet loss frequency and  
>> pattern very accurately. (I am assuming an encrypted packet number, 
>> or  the problem would be trivial.)
>>
>>  I would prefer, if we have a spin bit, for it to spin not every rtt  
>> but every, say, 10 packets that an endpoint sends. Client sends 10  
>> packets with 0 and then
>>  10 packets with 1, repeat. Sever does the same.
>>
>>  So maybe two spin bits -- one for rtt and one for loss? I would 
>> assume  that loss bit would assist in rtt estimation in case of loss.
>>
>>  Thoughts?
>>
>>  - Igor
>
>
> ______________________________________________________________________
> ___________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
>


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. 

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. 

Rispetta l'ambiente. Non stampare questa mail se non è necessario.