RE: spin bit in QUIC

JESUS MARIA MARTIN GARCIA <jesusmaria.martingarcia@telefonica.com> Wed, 15 November 2017 01:24 UTC

Return-Path: <jesusmaria.martingarcia@telefonica.com>
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 9735412940B for <quic@ietfa.amsl.com>; Tue, 14 Nov 2017 17:24:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, 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 gtKacWubSscC for <quic@ietfa.amsl.com>; Tue, 14 Nov 2017 17:24:30 -0800 (PST)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0099.outbound.protection.outlook.com [104.47.1.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 464E8126CD6 for <quic@ietf.org>; Tue, 14 Nov 2017 17:24:30 -0800 (PST)
Received: from VI1PR0601MB2431.eurprd06.prod.outlook.com (10.173.84.135) by VI1PR0601MB2430.eurprd06.prod.outlook.com (10.173.83.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.218.12; Wed, 15 Nov 2017 01:24:27 +0000
Received: from VI1PR0601MB2431.eurprd06.prod.outlook.com ([fe80::c062:bf8:cc99:33eb]) by VI1PR0601MB2431.eurprd06.prod.outlook.com ([fe80::c062:bf8:cc99:33eb%17]) with mapi id 15.20.0218.015; Wed, 15 Nov 2017 01:24:27 +0000
From: JESUS MARIA MARTIN GARCIA <jesusmaria.martingarcia@telefonica.com>
To: "sanjay.mishra@verizon.com" <sanjay.mishra@verizon.com>, QUIC WG <quic@ietf.org>
Subject: RE: spin bit in QUIC
Thread-Topic: spin bit in QUIC
Thread-Index: AdNdInWu9OoodX6pTBa2nSIjjM2p0wABTQNQACIWFrA=
Date: Wed, 15 Nov 2017 01:24:27 +0000
Message-ID: <VI1PR0601MB24316996BD50FEF4FBDF53D591290@VI1PR0601MB2431.eurprd06.prod.outlook.com>
References: <6E58094ECC8D8344914996DAD28F1CCD836BC1@DGGEMM506-MBX.china.huawei.com> <b2e177651f94481b899362904c16b84d@OMZP1LUMXCA08.uswin.ad.vzwcorp.com>
In-Reply-To: <b2e177651f94481b899362904c16b84d@OMZP1LUMXCA08.uswin.ad.vzwcorp.com>
Accept-Language: es-ES, en-US
Content-Language: es-ES
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=jesusmaria.martingarcia@telefonica.com;
x-originating-ip: [2001:67c:370:128:85d9:8d79:7054:cf26]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR0601MB2430; 6:frtDfRhg6LApJxQf79M8sioKNPLClZEDcy9IzDDN/topSNQyHryHG8/bEGJ8zw7K/3Q678ri5F1iXi/bFuGXyV8dy1B6E4f9AYu+lYJXwZ+lC9KsU3Y65cEN056yYKh+FflysBKmTB6yUcG0gC5PGnCR+ImUSvV6ORUqNhNvWZxu8OFs2n7idiySnhVAkaye7rNqXQHXUK3o/hkwoinLNulZCWRe71V0sICwK5WqYUtnAOklF08H+fT2zpmqdyj91qfGYBVtdRLOYYcBdYNW5CiMBYZGt2eTuNE2EL/vi0qjrgiDurdeZZLIUkEc5a+QPTyIx+IZrvGRJ7ncC24rlH9WxYCtrkdxOS1OarAcL0k=; 5:3yg5N9mk8oZcr/N4RO1UWj8pEl1/04JWAuHRCXda4VMA5mG95uuj8xlnudWTDpY3NRmDwOK/q9vbjI/VXVnXjj696aPT/HozecXzrH2AouJJ5ha+OXFgq0hoAowVX0MCnsPmrdET77NyrUbIueoYceh5U7o3YXM8YtJlFe56obg=; 24:+vrImQw0Aq898wTw0WOoxEkcCTTm1m+azZfMDst5uixztMS/76GvpbMSPTXU26tfekqozCjwSv3MkbJ6BYfttifBGobp0jtuoDiR+kuonZI=; 7:y8HcJ5U2DCLiGqY3hob6v9aQs4x7/VrykZn8EYjvBZ2zKw9/3ftZJ4qeWvxcIucazF2SvvFFKaZEhORuO2M/PzbE+voRDHj8Gp7YOm+zvc7Rx7McAs1JkfyJXNEwGawT9oIyDXhsXaqyENpgdaoPo+SW736bFWOG0dGar7GNqvBalDurlO8OiWwL/GnpQRS0fzF2opvnghVNulHG9clCeDGdCCgeFIFaFQM8od8EPJ6oe/alc4SD+FOrk6wPbXqF
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 2a36ecf2-f335-4c34-4f03-08d52bc79d16
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603258); SRVR:VI1PR0601MB2430;
x-ms-traffictypediagnostic: VI1PR0601MB2430:
x-microsoft-antispam-prvs: <VI1PR0601MB2430AC1554E4F2952A11425191290@VI1PR0601MB2430.eurprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(192374486261705)(50582790962513)(227612066756510)(21748063052155)(154440410675630);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(93006095)(93001095)(10201501046)(3002001)(3231022)(6055026)(6041248)(20161123560025)(20161123564025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123558100)(20161123562025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:VI1PR0601MB2430; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:VI1PR0601MB2430;
x-forefront-prvs: 0492FD61DD
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(376002)(39860400002)(189002)(40134004)(25724002)(199003)(8676002)(2950100002)(81166006)(81156014)(86362001)(99286004)(5660300001)(7696004)(6306002)(54896002)(5250100002)(55016002)(53936002)(97736004)(3280700002)(2900100001)(110136005)(14454004)(68736007)(8936002)(316002)(2501003)(6506006)(2906002)(229853002)(6436002)(786003)(7736002)(74316002)(76176999)(54356999)(25786009)(50986999)(101416001)(3480700004)(53346004)(3660700001)(53546010)(105586002)(6116002)(102836003)(6246003)(478600001)(790700001)(33656002)(189998001)(236005)(106356001)(9686003)(9010500006)(19627235001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR0601MB2430; H:VI1PR0601MB2431.eurprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: telefonica.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_VI1PR0601MB24316996BD50FEF4FBDF53D591290VI1PR0601MB2431_"
MIME-Version: 1.0
X-OriginatorOrg: telefonica.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 2a36ecf2-f335-4c34-4f03-08d52bc79d16
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Nov 2017 01:24:27.5983 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9744600e-3e04-492e-baa1-25ec245c6f10
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0601MB2430
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/_mvduq_bmMI6F12hIY_1_pLtgqA>
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: Wed, 15 Nov 2017 01:24:35 -0000

+1

Even with the limitations known, the spin bit will allow service providers to measure latency in the network for troubleshooting.

That's why I want to add my support for the inclusion of the spin bit into V1

BR
Jesus
Make a small change everyday

Jesús Martín | Telefónica S.A.

De: QUIC [mailto:quic-bounces@ietf.org] En nombre de sanjay.mishra@verizon.com
Enviado el: martes, 14 de noviembre de 2017 10:38
Para: QUIC WG <quic@ietf.org>
CC: Roni Even <roni.even@huawei.com>
Asunto: RE: spin bit in QUIC

Adding to what Roni has below, first, I applaud to the spin bit design for their time since the Prague meeting and many thanks to Ted for presenting those findings.

>From Ted's presentation, it appears that the design team accomplished what they were asked to do, that is, look at geolocation threat and Min RTT. Slide 7 from Ted's presentation lays out negligible threat and at least not any additional adversarial information.  Given this, I would have thought design team to be less tentative and come to a clear consensus.

Also, agree with Marcus on his enumeration on the need for spin bit and as Roni pointed out inclusion of spin but in v1 gives us some real -world deployment experience on performance and bottlenecks.

I ask the chairs to add spin bit for v1.

-Sanjay


From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Roni Even
Sent: Tuesday, November 14, 2017 4:41 PM
To: QUIC WG <quic@ietf.org<mailto:quic@ietf.org>>
Subject: [E] spin bit in QUIC

Hi,
It is good that the conclusion about the geo location security issue is that the spin bit does not add privacy risk on top of what can be done without it.

As for the spin bit. RTT calculation are used for trouble shooting in TCP see in draft-even-quic-troubleshooting-video-delivery-00.
The spin bit will provide similar functionality even though it is less reliable as was mentioned since it is not part of the QUIC state machine.
We envision that we will see a lot of QUIC traffic in the network and having the spin bit can help with identifying bottle necks in the network and reducing QUIC latency.  It will be important to have the spin bit in V1 and the main text is already in the github

Thanks
Roni Even




________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição