
From nobody Mon Oct  1 08:43:06 2018
Return-Path: <dtikhonov@litespeedtech.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 8F076130EA5 for <quic@ietfa.amsl.com>; Mon,  1 Oct 2018 08:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=litespeedtech-com.20150623.gappssmtp.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 9_yRBQaSorJA for <quic@ietfa.amsl.com>; Mon,  1 Oct 2018 08:42:48 -0700 (PDT)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 74818130EAF for <quic@ietf.org>; Mon,  1 Oct 2018 08:42:47 -0700 (PDT)
Received: by mail-qt1-x82c.google.com with SMTP id q40-v6so1553357qte.0 for <quic@ietf.org>; Mon, 01 Oct 2018 08:42:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mail-followup-to:mime-version :content-disposition:user-agent; bh=HoIjcpH0KWCM1kGT9zdLz8MVj9QwZgvfvI+OsWXWfiA=; b=fSkZItT7Do7PE6va7f5gGkU7Hoo3/UmQpghxNhWXQ5K5KfgXXAq7WGYA761oaPbAfN wEGHtrhLYnBrv64qLla68gZUlQJrizglIMru9aBynEkXnWt3xseFGgo8nXvlDFx1ndYW nCZXRWpJyEsN6pSbUdMOY+Fz9fBkClMv+lLWhYnHK5vHg0F6dqKtTwWYl8cfMTsWVIEg REWhl1zM921kyDBvcnF6cwoO9ehd3Ej2gY+6EB5JNWmh3lG/WUDvSmrkq5t1Qi1wGQIg MzcSxM86Ygf422fTWZDzHjVt5iUc/QV0HPkkwb5wX6581UJgG8QEx3qI9XWsiP8IywLY tudw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :mime-version:content-disposition:user-agent; bh=HoIjcpH0KWCM1kGT9zdLz8MVj9QwZgvfvI+OsWXWfiA=; b=j9zBG66Nwy8N2aS3tikn3JPgzg3ZdUeINdNUt+qdCjM0S/Attf+ApbNXjubcbAs2RI tCjoQA+ZSvkuBcfPuOrBcBCUmWBKxvPLDBtgwpgBLbgjGGN7da5y2dt5JWE06vclZLBx tTCfTDbpi4qPBF9BWyopRtB0g//sTFqNg61L7wHtVxkRZn0aIzZtn9fk2SfBRxoeFcVv qsYMY3hDpzhw7n/tyuLP8CguNfi2xp2FV6N0cwNjMRkwi5MqYu0HWMpQZuDgX/sJeQVc qTEGGOCVXRb0vgkPed16I7w5DfhMVgYfTt664DyBgB3ZJ2lSSGN8i5u7ZIZjFIljXm3m E0Ag==
X-Gm-Message-State: ABuFfogRhL9ONhij6A29sORE5kjJ56uj6sjG+Nh0nn8egc/kt2s/o/8X C5SSZG+GPXikPcbWGd4Lk/wyTJuWs48=
X-Google-Smtp-Source: ACcGV61orrTxv3dWfPS1rbX4yoHTGRne3E+xZXvgJphFAXquH4MSlfKOBN0HKfVAedQidyzWqKz2rg==
X-Received: by 2002:ac8:5508:: with SMTP id j8-v6mr8958802qtq.139.1538408566382;  Mon, 01 Oct 2018 08:42:46 -0700 (PDT)
Received: from ubuntu-dmitri (ool-44c1d219.dyn.optonline.net. [68.193.210.25]) by smtp.gmail.com with ESMTPSA id f90-v6sm9970089qkf.49.2018.10.01.08.42.45 for <quic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 01 Oct 2018 08:42:45 -0700 (PDT)
Date: Mon, 1 Oct 2018 11:42:43 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: IETF QUIC WG <quic@ietf.org>
Subject: Purpose of HTTP settings' maxima
Message-ID: <20181001154242.GB20456@ubuntu-dmitri>
Mail-Followup-To: IETF QUIC WG <quic@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/wXttU3H7M9TAxYJzDVHtzQy_-oQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 01 Oct 2018 15:43:05 -0000

Hello,

draft-ietf-quic-http-14 [1] states:

   The following settings are defined in HTTP/QUIC:

   SETTINGS_NUM_PLACEHOLDERS (0x3):  An integer with a maximum value of
      2^16 - 1.  The value SHOULD be non-zero.  The default value is 16.

   SETTINGS_MAX_HEADER_LIST_SIZE (0x6):  An integer with a maximum value
      of 2^30 - 1.  The default value is unlimited.

These maximum values seem arbitrary.  Assuming that they are, I wonder:
why specify them at all?

Both of these are integers, which means that they must be expressed
using the QUIC integer encoding [2].  That is to say, both have an
implicit limit of 2^62 - 1.

Since both of these specify what the sender is willing to support,
an arbitrary maximum like this is unnecessary.  The peer will select a
minimum of its own and the sender's specified maximum.  If that happens
to be 2^62 - 1, well, then so be it!

  - Dmitri.

1. https://tools.ietf.org/html/draft-ietf-quic-http-14
2. https://tools.ietf.org/html/draft-ietf-quic-transport-14#section-7.1


From nobody Mon Oct  1 09:30:25 2018
Return-Path: <Lucas.Pardue@bbc.co.uk>
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 0C377130E5B for <quic@ietfa.amsl.com>; Mon,  1 Oct 2018 09:30:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 uicxO2Ajnu1w for <quic@ietfa.amsl.com>; Mon,  1 Oct 2018 09:30:22 -0700 (PDT)
Received: from mailout0.cwwtf.bbc.co.uk (mailout0.cwwtf.bbc.co.uk [132.185.160.179]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CE27130E11 for <quic@ietf.org>; Mon,  1 Oct 2018 09:30:21 -0700 (PDT)
Received: from BGB01XI1011.national.core.bbc.co.uk (bgb01xi1011.national.core.bbc.co.uk [10.161.14.15]) by mailout0.cwwtf.bbc.co.uk (8.15.2/8.15.2) with ESMTP id w91GUKkp006187; Mon, 1 Oct 2018 17:30:20 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1011.national.core.bbc.co.uk ([10.161.14.15]) with mapi id 14.03.0408.000; Mon, 1 Oct 2018 17:30:19 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Purpose of HTTP settings' maxima
Thread-Topic: Purpose of HTTP settings' maxima
Thread-Index: AQHUWZ2DCUwPjr8j3Uqo/B+qJnS4ZKUKj+AQ
Date: Mon, 1 Oct 2018 16:30:19 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BBAFE0B@bgb01xud1012>
References: <20181001154242.GB20456@ubuntu-dmitri>
In-Reply-To: <20181001154242.GB20456@ubuntu-dmitri>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.19.161.212]
x-exclaimer-md-config: 1cd3ac1c-62e5-43f2-8404-6b688271c769
x-tm-as-product-ver: SMEX-12.5.0.1300-8.2.1013-24054.007
x-tm-as-result: No-16.279300-8.000000-10
x-tmase-matchedrid: 6otD/cJAac27lpQUW6Uvz7iMC5wdwKqdwZLXS0hN8p0NcckEPxfz2IP+ YDa/Dhu9ujQMTOaH2U5uk1SYLV+ldvJMF6pylZNWsTcWkxuDrdIZKp0SZ4P+dWM+uU0H6AyrrUP UnGU6bCmx7sLYPyWWYof3FqTyUbJVRUqOXUf3BH1fwzQfOH01PBSRa9qpSosfyj+mMsG+WjYjhm sSV51KnCWSzsPREMfEQ3uyYiQUJdcnX6qFKKAH9JWOaq+3+nxyBXJ6j2Ez1IcLBdHVMDTSl7aKL ra4faAg6OOHNsEXHdasXAiB6VK48Ka9gJYeYbzMma6DzXaohvPP60q/FX5hsFG8vLCRjD2po8WM kQWv6iXBcIE78YqRWsR4CqSjYlsD
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
x-tmase-result: 10--16.279300-8.000000
x-tmase-version: SMEX-12.5.0.1300-8.2.1013-24054.007
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/jvoQx4UK8KfXGbD7gDd3SRoTUb4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 01 Oct 2018 16:30:24 -0000

Dmitri Tikhonov wrote:

>   SETTINGS_NUM_PLACEHOLDERS (0x3):  An integer with a maximum value of
>      2^16 - 1.  The value SHOULD be non-zero.  The default value is 16.

I must admit to not following too closely the work on PRIORITY that introdu=
ced this [1] (Sorry Mike!). I'd be interested in knowing where the limit (a=
nd suggest default) for placeholders comes from.

I initially jumped to conclusion that this could lead to some weird logic f=
or PRIORITY frame but actually think it would be consistent. A client gener=
ates a PRIORITY frame with an element ID that must fit within the limit of =
varint AND the maximum permitted for that ID type (request stream - MAX_STR=
EAM_ID, push stream - MAX_PUSH_ID, placeholder - SETTINGS_NUM_PLACEHOLDERS)=
.

Finally, on a tangent (sorry), is a server supposed to ignore SETTINGS_NUM_=
PLACEHOLDERS? Or does the connection use the "negotiated" highest/lowest va=
lue advertised by peers?

https://github.com/quicwg/base-drafts/pull/1422



-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specif=
ically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------


From nobody Mon Oct  1 23:07:04 2018
Return-Path: <alexandre.ferrieux@orange.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 63147130E04 for <quic@ietfa.amsl.com>; Mon,  1 Oct 2018 23:07:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.291
X-Spam-Level: 
X-Spam-Status: No, score=-0.291 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 ftTjn2vedCy6 for <quic@ietfa.amsl.com>; Mon,  1 Oct 2018 23:07:02 -0700 (PDT)
Received: from orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D34212F295 for <quic@ietf.org>; Mon,  1 Oct 2018 23:07:02 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar20.francetelecom.fr (ESMTP service) with ESMTP id 42PTFJ4S2Bz8sxh for <quic@ietf.org>; Tue,  2 Oct 2018 08:07:00 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 42PTFJ3Tn6zCqlF for <quic@ietf.org>; Tue,  2 Oct 2018 08:07:00 +0200 (CEST)
Received: from [10.193.4.89] (10.168.234.2) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 2 Oct 2018 08:07:00 +0200
To: IETF QUIC WG <quic@ietf.org>
From: <alexandre.ferrieux@orange.com>
Subject: Spin bit decision
Message-ID: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com>
Date: Tue, 2 Oct 2018 08:05:19 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: fr-xx-moderne
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.168.234.2]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/v3jwPlR7gyprjqmBwDj-dr_SwB8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 06:07:03 -0000

Hello,

After NYC, what are the remaining questions the WG is asking regarding the spin 
bit to educate the upcoming decision (Bangkok):

   (a) why is midpoint half-RTT measurement useful (in current practices) ?
   (b) is the spin bit up to the job?
   (c) isn't there any other way ?
   (d) other

?

_________________________________________________________________________________________________________________________

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.


From nobody Mon Oct  1 23:51:58 2018
Return-Path: <lars@eggert.org>
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 C1668130DC0 for <quic@ietfa.amsl.com>; Mon,  1 Oct 2018 23:51:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 6tqBo2sPyhIy for <quic@ietfa.amsl.com>; Mon,  1 Oct 2018 23:51:55 -0700 (PDT)
Received: from emh01.mail.saunalahti.fi (emh01.mail.saunalahti.fi [62.142.5.107]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED63B128B14 for <quic@ietf.org>; Mon,  1 Oct 2018 23:51:54 -0700 (PDT)
Received: from eggert.org (unknown [62.248.255.56]) by emh01.mail.saunalahti.fi (Postfix) with ESMTP id 9D0CA20322; Tue,  2 Oct 2018 09:51:52 +0300 (EEST)
Received: from slate.eggert.org (pf.eggert.org [172.16.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by eggert.org (Postfix) with ESMTPSA id ED41561C7EB; Tue,  2 Oct 2018 09:51:36 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: Re: Spin bit decision
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com>
Date: Tue, 2 Oct 2018 09:51:33 +0300
Cc: IETF QUIC WG <quic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com>
To: alexandre.ferrieux@orange.com
X-Mailer: Apple Mail (2.3445.100.39)
X-MailScanner-ID: ED41561C7EB.A4F50
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/RGi9IcOwYUkdmICV4-nge4XdIBA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 06:51:57 -0000

Hi,

On 2018-10-2, at 9:05, alexandre.ferrieux@orange.com wrote:
> After NYC, what are the remaining questions the WG is asking regarding =
the spin bit to educate the upcoming decision (Bangkok):
>=20
>  (a) why is midpoint half-RTT measurement useful (in current =
practices) ?
>  (b) is the spin bit up to the job?
>  (c) isn't there any other way ?
>  (d) other
>=20
> ?

the following is my personal feedback on this matter, i.e., I'm not =
speaking as chair:

I have little doubt that the single-bit spin bit variant is fit for =
purpose. I also think the DT has analyzed the privacy implications of =
the single-bit variant sufficiently for me to have no serious privacy =
concerns about the variant.

The key open question in my mind is this: on what fraction of the =
traffic would an operator need to see spinning and echoed bits in order =
to obtain useful network-wide or at least path specific latency =
information? In other words, how many browsers and servers-side =
deployments would need to opt in and spin or echo the bits? Would it be =
sufficient if one hyperscalar with a bowser and a server deployment =
opted in? Even if most of their traffic concentrated towards their =
peering links?

Regards,
Lars=


From nobody Tue Oct  2 01:30:33 2018
Return-Path: <alexandre.ferrieux@orange.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 AF3C2130DF5 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 01:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.291
X-Spam-Level: 
X-Spam-Status: No, score=-0.291 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 2QiOa9gy4U_s for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 01:30:30 -0700 (PDT)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D510A130DD7 for <quic@ietf.org>; Tue,  2 Oct 2018 01:30:29 -0700 (PDT)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr26.francetelecom.fr (ESMTP service) with ESMTP id 42PXQr1SV0z10Rw; Tue,  2 Oct 2018 10:30:28 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id 42PXQr0VBlzDq78; Tue,  2 Oct 2018 10:30:28 +0200 (CEST)
Received: from [10.193.4.89] (10.168.234.6) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 2 Oct 2018 10:30:27 +0200
Subject: Re: Spin bit decision
To: Lars Eggert <lars@eggert.org>
CC: IETF QUIC WG <quic@ietf.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org>
From: <alexandre.ferrieux@orange.com>
Message-ID: <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com>
Date: Tue, 2 Oct 2018 10:28:41 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.168.234.6]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fvaKEg77prH_njeCjMLzBeKy1KE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 08:30:32 -0000

On 10/02/18 08:51, Lars Eggert wrote:
> Hi,
> 
> On 2018-10-2, at 9:05, alexandre.ferrieux@orange.com wrote:
>> After NYC, what are the remaining questions the WG is asking regarding the
>> spin bit to educate the upcoming decision (Bangkok):
>> 
>> (a) why is midpoint half-RTT measurement useful (in current practices) ? 
>> (b) is the spin bit up to the job ? >> (c) isn't there any other way ?
>> (d) other >> ?
> 
> the following is my personal feedback on this matter, i.e., I'm not speaking
> as chair:
> 
> I have little doubt that the single-bit spin bit variant is fit for purpose.
> I also think the DT has analyzed the privacy implications of the single-bit
> variant sufficiently for me to have no serious privacy concerns about the
> variant.
> 
> The key open question in my mind is this: on what fraction of the traffic
> would an operator need to see spinning and echoed bits in order to obtain
> useful network-wide or at least path specific latency information? In other
> words, how many browsers and servers-side deployments would need to opt in
> and spin or echo the bits? Would it be sufficient if one hyperscalar with a
> bowser and a server deployment opted in? Even if most of their traffic
> concentrated towards their peering links?

Experience with debugging our networks in several countries shows that (1) all
segments may misbehave, and (2) sample size is very often an issue, in that some
problems are triggered by a non-obvious conjunction of parameters that is
extremely sensitive to sampling bias. So, the more support for measurement, the
better. TCP shines because clear headers are ubiquitous, not an opt-in debug
mode, nor a randomly enabled feature in X% of flows.

May I ask why this question is key ? Are you envisioning a situation where v1
would allow for the spin bit as a negotiated option instead of just requiring it
? Added complexity and inferior outcome: what is the motivation ?


_________________________________________________________________________________________________________________________

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.


From nobody Tue Oct  2 04:00:31 2018
Return-Path: <lars@eggert.org>
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 9E7B0126BED for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 04:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 qym7f9yxynQf for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 04:00:27 -0700 (PDT)
Received: from emh04.mail.saunalahti.fi (emh04.mail.saunalahti.fi [62.142.5.110]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F56F130DDB for <quic@ietf.org>; Tue,  2 Oct 2018 04:00:27 -0700 (PDT)
Received: from eggert.org (unknown [62.248.255.56]) by emh04.mail.saunalahti.fi (Postfix) with ESMTP id D7DF030268; Tue,  2 Oct 2018 14:00:25 +0300 (EEST)
Received: from slate.eggert.org (pf.eggert.org [172.16.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by eggert.org (Postfix) with ESMTPSA id 5067B61FA15; Tue,  2 Oct 2018 13:59:44 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: Re: Spin bit decision
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com>
Date: Tue, 2 Oct 2018 13:59:43 +0300
Cc: IETF QUIC WG <quic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com>
To: alexandre.ferrieux@orange.com
X-Mailer: Apple Mail (2.3445.100.39)
X-MailScanner-ID: 5067B61FA15.A350C
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Z4kNp9VHK2LvpEMuAQ7WmPT6L78>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 11:00:31 -0000

Hi,

again, as an individual:

On 2018-10-2, at 11:28, alexandre.ferrieux@orange.com wrote:
> Experience with debugging our networks in several countries shows that =
(1) all
> segments may misbehave, and (2) sample size is very often an issue, in =
that some
> problems are triggered by a non-obvious conjunction of parameters that =
is
> extremely sensitive to sampling bias. So, the more support for =
measurement, the
> better. TCP shines because clear headers are ubiquitous, not an opt-in =
debug
> mode, nor a randomly enabled feature in X% of flows.

so what fraction of spin-enabled QUIC traffic would be sufficient? Maybe =
just a ballpark number; 1%, 10%, 100%?

> May I ask why this question is key ? Are you envisioning a situation =
where v1
> would allow for the spin bit as a negotiated option instead of just =
requiring it
> ? Added complexity and inferior outcome: what is the motivation ?

The WG hasn't really discussed yet what requirements level any inclusion =
of the spin bit into the main spec would have, and there could obviously =
be different levels of requirement for clients and servers.

But irrespective of what - if anything - the spec chooses to say, =
deployed implementations can obviously choose to do whatever they wish, =
since the spin bit is not affecting interoperability at all.

So for the spin bit to fulfill its intended purpose, at least some =
client deployments and at least some server deployments that spin and =
echo the bit are required. Enough on both sides so that a sufficient =
fraction of the traffic is spinning (which is what my first question was =
about.)=20

Lars=


From nobody Tue Oct  2 04:45:25 2018
Return-Path: <marcus.ihlar@ericsson.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 CA5E3130DEE for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 04:45:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=T4jfDped; dkim=pass (1024-bit key) header.d=ericsson.com header.b=N1ChRldS
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 HQjoL2Y3e6w3 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 04:45:21 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 E99B8126BED for <quic@ietf.org>; Tue,  2 Oct 2018 04:45:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1538480719; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=L53KbBv2M4RnHOwI95eL9CkbG/FjtoydC/6NYFUcMZ0=; b=T4jfDpedFnf+MzApTGQ7JcBSm6XhMAgWSs4P9+jxnyzq5V45ftXWbbpj+/XRqVPd rSu0sp1Dx5IaVX2Szg3UNQ1hJbm/R+KuMU2z3JVrZmqX/J8LNzqKjJjkJ2Dimy7y MzKFzb6Sc9rpTUUflNE/7AZs0pjm7SkQ/K5ExVXy3iQ=;
X-AuditID: c1b4fb30-3cd869c0000055da-98-5bb35a4f416e
Received: from ESESSMB501.ericsson.se (Unknown_Domain [153.88.183.119]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 2D.36.21978.F4A53BB5; Tue,  2 Oct 2018 13:45:19 +0200 (CEST)
Received: from ESESSMB503.ericsson.se (153.88.183.164) by ESESSMB501.ericsson.se (153.88.183.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Tue, 2 Oct 2018 13:44:21 +0200
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB503.ericsson.se (153.88.183.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Tue, 2 Oct 2018 13:44:21 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=la2akNRC6kbqiWHIscRIBHPV7QKHW6fKEXT0eGM5zTk=; b=N1ChRldSlv5ygzfdutLSdwJ4D9q3KvpcN5BZ2kYJaSxuBg5VLBa+nZ4V5wxqpbiWRvfRRnpJiP7yeqwhDjFaC2Sa8DhHJSBp5UfouoFTxGLdwNFV8I+qCIN5XKs+sSdUW3yAGqE3fipRgRxznYbpDluqWTMdI/BN98WNN8Dz63w=
Received: from HE1PR0701MB2393.eurprd07.prod.outlook.com (10.168.128.12) by HE1PR0701MB1820.eurprd07.prod.outlook.com (10.167.247.8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1207.16; Tue, 2 Oct 2018 11:44:19 +0000
Received: from HE1PR0701MB2393.eurprd07.prod.outlook.com ([fe80::400d:3614:de33:b3a8]) by HE1PR0701MB2393.eurprd07.prod.outlook.com ([fe80::400d:3614:de33:b3a8%4]) with mapi id 15.20.1207.018; Tue, 2 Oct 2018 11:44:19 +0000
From: Marcus Ihlar <marcus.ihlar@ericsson.com>
To: "lars@eggert.org" <lars@eggert.org>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>
CC: "quic@ietf.org" <quic@ietf.org>
Subject: RE: Spin bit decision
Thread-Topic: Spin bit decision
Thread-Index: AQHUWhY0QgtwVDCa9kyLuQ+XAu9Y8qULhImAgAAbI4CAACozgIAABuvA
Date: Tue, 2 Oct 2018 11:44:19 +0000
Message-ID: <HE1PR0701MB2393CDB16819A54B33D22417E2E80@HE1PR0701MB2393.eurprd07.prod.outlook.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org>
In-Reply-To: <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.176.1.88]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR0701MB1820; 6:iS3bW6F8Vy7Agvn2fm265GrOBl/F9Cs08PRwU2E2ui8PoiB0R2yhO3q/Zlw2//1nWjyYI1sCGYxY78tFT7AJszbrsYOlgaBkrM+hpsuMB9es+bRsRWmDnOSKymY9Dr7OGyjCjPJsGPmyFSFM3RSlTZaMqrZMBaIiuyizl2RdGoMtLOuUh89zy/bJssyl7uDO/LLygla7Ads0JMxzYGOe3SAX5+KD+gBNE1cR8hi+DMi9q3YMZw9BFj0JmelOeAfOa0YF5AljUjrkaDZ1aifjJN1+Jkx747oEMzF0jDzSnZPrbsoTzGTM9JWzXDus21GC9pRJfJl/ZoX5X6rsLoWnU9cc861Zct9IGE/2dxYVI2SjkapuxrRYw9M8jcOXoirBbor5aYVjRsA77ZrpK4kVFIEFXhyPlcc8RgCrWYXehURFkAr3XKe1DktlqyCt6IQ9qTLLrazHsEMm0s3sgiOh7A==; 5:J3kmBZYF1yoZlmcCtZgUAVdXH/a42+Bc8dqjFtml6T8kG6UxCHpGN1GC0VQ0X6y4lZFPyUyD7swksf0S1y2uSMDDhGX33A49Atd3PMpDNBaAnppdy46Ilzsf5VVC1pkMOB7ZWtPOfDmOxc2FGFk5yoSc7zCdLr7DJiYrISoMUAM=; 7:XvN7rWmLWNA0otuBrkTnfE/Ecck99F7bWNYwRyOAaG2uqb0DJT8d+V/f8mvHHHnCijQf9QrWgWutEfKOD85dly8/l1E6dG5sAgy+4MA13UgnrZP9RNIystCStLH78i5abQk1EfJl/DXSxugs2vOZ6wwhn5iLTsyINPnJEN+Z5kmjnVtFH21NPl13Y2BVPAKTnuRfu3fR2DUXg8WjKPu5LoMA1JIUga0GjQOjebWF3VdNBfeq8+EtZGjiaRQHZd2U
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 33fb651f-e96f-4cb3-2484-08d6285c63be
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534165)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:HE1PR0701MB1820; 
x-ms-traffictypediagnostic: HE1PR0701MB1820:
x-microsoft-antispam-prvs: <HE1PR0701MB182062A20EFE3C264A3FC5D8E2E80@HE1PR0701MB1820.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(161740460382875)(18271650672692)(72170088055959)(158342451672863); 
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3231355)(944501410)(52105095)(93006095)(93001095)(3002001)(10201501046)(149066)(150057)(6041310)(20161123564045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123562045)(201708071742011)(7699051)(76991041); SRVR:HE1PR0701MB1820; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0701MB1820; 
x-forefront-prvs: 0813C68E65
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(39860400002)(366004)(396003)(136003)(189003)(13464003)(199004)(26005)(186003)(316002)(6246003)(106356001)(5660300001)(7116003)(33656002)(6346003)(102836004)(99286004)(2906002)(256004)(3480700004)(8676002)(81166006)(81156014)(53546011)(105586002)(2900100001)(7696005)(68736007)(66066001)(110136005)(71200400001)(476003)(14454004)(478600001)(4001150100001)(25786009)(4326008)(8936002)(7736002)(305945005)(44832011)(6506007)(76176011)(486006)(6116002)(3846002)(71190400001)(74316002)(5250100002)(2501003)(11346002)(446003)(6436002)(53936002)(9686003)(97736004)(229853002)(55016002)(93886005)(86362001); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0701MB1820; H:HE1PR0701MB2393.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=marcus.ihlar@ericsson.com; 
x-microsoft-antispam-message-info: MjMiHDgIsrGC7vCV9Rnt+Ib3LTJudXGvYot/jo/OVYdMLGUO3gvsUZi2AAg4DlEa1w6tvy5HoJ50rrjVU8Q18QYl83KDsBdQlBmt8gotQv3qjuKD36rynGCYns/mQMwGCuYBqKnT1WCgncPCR0wjhZnENWnsrX0EPulCKNLHx103Yd76h8/qpAcj9jbefglmNZcSxrxnB84wgCYplMbLHpgW9jdBXqqxDL2VcvlSC3pB36PKOlhUGyGvpGZd/5uMHea/5h1q+7rz30UHRTY+x5OL2smPbkd/eYdoZq6g7pkcBeITE9+RVdbtK96Qpom9CdKR2I3midSq0Jmluy1XSVWOXYBtrT0b5D/EXAZQyCI=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 33fb651f-e96f-4cb3-2484-08d6285c63be
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Oct 2018 11:44:19.3380 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB1820
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Sa0iTURjHOe9tr9PR0WY+eY0ZUZmmsmJUmCLE7GJSFqFGznzT5Zyyecmo 2AdvaIqkoxRsVioxCEHFpCx0JmTmJd0Hi7RMTdQoy6SlJLmdBX37Pef//J//eQ6Hpz0qWW9e rc0RdFqVRsaJmdpzj/ODTya0JYZ2FWFFsy1AsfiiXKS42eAaSSuriwdYZWPjb0pZ+Lmfi6MT xIdSBY06T9DtjUgWpw8Ou2ffkl55+vI5ZUD3cRly4QHLYdVciuzsgfsQVJtTypB4g1cQGKp7 GFI8oKDhzw9kLxhcRcPQrIUlipGCQVuxiPhnETxrltiZwyHweqKcs7MUX4bW9XYH0zgQagYM rJ03Y3+Y+zSJSE8ATHQ3MoSPwFqPlbYzg7fD1PR7x3wJTobalU6OBDdR0LQw7xjqgiPAulJF 2RlhP/jwa5IhYV7wbsZEkUUxNHYN04Q9YX56nSW8Db7WD3CE/WDUVO5YE3C3CHpHDSIiBMOS 0eg0n4DZljs0aepH0PJoGhFhD5gm3zrTsmCs6KeTNWBZHnOa/cFcMcUQcy8NtpE5ugqF1f13 W8IhMG6s4QgHQfO9RbrO8QTu0F87wzQgxow89YI+JTMtPDxE0Kkv6vVZ2hCtkNOKNn5JT/ta aCean4uyIMwjmZvkum9bogerytMXZFoQ8LRMKmEPbhxJUlUFVwVd1gVdrkbQW5APz8i8JIrY tgQPnKbKETIEIVvQ/VMp3sXbgJTBX9S2b2+WlKdd+RjfeB//qbvaG1vrdxSq5NyuZh8UuX+1 soU+c3bJojgv6ogMZb9/PHV0hIukA0sDM22XHlpN1zLMboNJtxXCbEVuzJB1ebV7i/zAzuqS 1mN9bU0dyU9iF4KmX8mj3brHD8cdj16qMmrm4/e1SEvyk4KjqE0yRp+uCttN6/Sqvwblumoh AwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/iBalTfo0hN2rgU1oKvTkWYKXqx0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 11:45:24 -0000

Hi,

-----Original Message-----
From: QUIC <quic-bounces@ietf.org> On Behalf Of Lars Eggert
Sent: den 2 oktober 2018 13:00
To: alexandre.ferrieux@orange.com
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Spin bit decision

Hi,

again, as an individual:

On 2018-10-2, at 11:28, alexandre.ferrieux@orange.com wrote:
> Experience with debugging our networks in several countries shows that
> (1) all segments may misbehave, and (2) sample size is very often an
> issue, in that some problems are triggered by a non-obvious
> conjunction of parameters that is extremely sensitive to sampling
> bias. So, the more support for measurement, the better. TCP shines
> because clear headers are ubiquitous, not an opt-in debug mode, nor a ran=
domly enabled feature in X% of flows.

so what fraction of spin-enabled QUIC traffic would be sufficient? Maybe ju=
st a ballpark number; 1%, 10%, 100%?

MI: It=B4s a difficult question to answer as there are different uses of th=
e spin information ranging from active troubleshooting sessions for a small=
 set of subscribers to passive monitoring on a large scale e.g for KPI dash=
boards.
>From a spin consumer perspective the bigger the fraction the better of cour=
se, but the pain thresholds would be different from usecase to usecase.
The active troubleshooting case would require either that a very large port=
ion of traffic is spin-enabled or that it would be possible for a user to s=
electively enable the functionality.
The large scale monitoring case would likely be useful even if  only a few =
% of flows are spin-enabled.

> May I ask why this question is key ? Are you envisioning a situation
> where v1 would allow for the spin bit as a negotiated option instead
> of just requiring it ? Added complexity and inferior outcome: what is the=
 motivation ?

The WG hasn't really discussed yet what requirements level any inclusion of=
 the spin bit into the main spec would have, and there could obviously be d=
ifferent levels of requirement for clients and servers.

But irrespective of what - if anything - the spec chooses to say, deployed =
implementations can obviously choose to do whatever they wish, since the sp=
in bit is not affecting interoperability at all.

So for the spin bit to fulfill its intended purpose, at least some client d=
eployments and at least some server deployments that spin and echo the bit =
are required. Enough on both sides so that a sufficient fraction of the tra=
ffic is spinning (which is what my first question was about.)

Lars


From nobody Tue Oct  2 04:52:34 2018
Return-Path: <lars@eggert.org>
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 B7DA6130DF2 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 04:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 mmqdrPENOIQk for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 04:52:31 -0700 (PDT)
Received: from emh02.mail.saunalahti.fi (emh02.mail.saunalahti.fi [62.142.5.108]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAB7D126BED for <quic@ietf.org>; Tue,  2 Oct 2018 04:52:30 -0700 (PDT)
Received: from eggert.org (unknown [62.248.255.56]) by emh02.mail.saunalahti.fi (Postfix) with ESMTP id AB18E2019A; Tue,  2 Oct 2018 14:52:28 +0300 (EEST)
Received: from slate.eggert.org (pf.eggert.org [172.16.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by eggert.org (Postfix) with ESMTPSA id 4231061C764; Tue,  2 Oct 2018 14:51:47 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: Re: Spin bit decision
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <HE1PR0701MB2393CDB16819A54B33D22417E2E80@HE1PR0701MB2393.eurprd07.prod.outlook.com>
Date: Tue, 2 Oct 2018 14:51:46 +0300
Cc: "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, "quic@ietf.org" <quic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E76B081-E78F-4C81-96A7-9DF71D7DA733@eggert.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <HE1PR0701MB2393CDB16819A54B33D22417E2E80@HE1PR0701MB2393.eurprd07.prod.outlook.com>
To: Marcus Ihlar <marcus.ihlar@ericsson.com>
X-Mailer: Apple Mail (2.3445.100.39)
X-MailScanner-ID: 4231061C764.AFBEB
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/sDOisNwsHyxYvXS23K0k-Pvd6hY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 11:52:33 -0000

Hi,

On 2018-10-2, at 14:44, Marcus Ihlar <marcus.ihlar@ericsson.com> wrote:
> The active troubleshooting case would require either that a very large =
portion of traffic is spin-enabled or that it would be possible for a =
user to selectively enable the functionality.
> The large scale monitoring case would likely be useful even if  only a =
few % of flows are spin-enabled.

thanks, Marcus! That was what I was wondering about.

Lars=


From nobody Tue Oct  2 05:43:41 2018
Return-Path: <alexandre.ferrieux@orange.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 79662124D68 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 05:43:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.291
X-Spam-Level: 
X-Spam-Status: No, score=-0.291 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 WRkbMjdvlmtn for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 05:43:38 -0700 (PDT)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 944131277D2 for <quic@ietf.org>; Tue,  2 Oct 2018 05:43:38 -0700 (PDT)
Received: from opfednr03.francetelecom.fr (unknown [xx.xx.xx.67]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id 42Pf2w6Pnnz1yvh; Tue,  2 Oct 2018 14:43:36 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfednr03.francetelecom.fr (ESMTP service) with ESMTP id 42Pf2w5FsDzDq7J; Tue,  2 Oct 2018 14:43:36 +0200 (CEST)
Received: from [10.193.4.89] (10.168.234.4) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 2 Oct 2018 14:43:36 +0200
Subject: Re: Spin bit decision
To: Lars Eggert <lars@eggert.org>
CC: IETF QUIC WG <quic@ietf.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org>
From: <alexandre.ferrieux@orange.com>
Message-ID: <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com>
Date: Tue, 2 Oct 2018 14:41:55 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: fr-xx-moderne
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.168.234.4]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/wAFR5GiB_DuBRiKalC5G235AJhw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 12:43:40 -0000

On 10/02/18 12:59, Lars Eggert wrote:
>  >> May I ask why this question is key ? Are you envisioning a situation where
>> v1 would allow for the spin bit as a negotiated option instead of just
>> requiring it ? Added complexity and inferior outcome: what is the
>> motivation ?
> 
> The WG hasn't really discussed yet what requirements level any inclusion of
> the spin bit into the main spec would have, and there could obviously be
> different levels of requirement for clients and servers.
> 
> But irrespective of what - if anything - the spec chooses to say, deployed
> implementations can obviously choose to do whatever they wish, since the spin
> bit is not affecting interoperability at all.

Well, if the spec says that en endpoint MUST copy of flip a bit, an implementor 
would be fairly ill-advised not do comply. And nothing prevents from adding a 
"does it spin ?" criterion to the interop test suite.

Clearly you now have this degree of freedom: weaken that MUST into a MAY or a 
SHOULD, separately for each role. But for what purpose ?


_________________________________________________________________________________________________________________________

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.


From nobody Tue Oct  2 05:56:02 2018
Return-Path: <lars@eggert.org>
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 17AA91277BB for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 05:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 oMJIfSdmcW3z for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 05:55:58 -0700 (PDT)
Received: from emh03.mail.saunalahti.fi (emh03.mail.saunalahti.fi [62.142.5.109]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D41F130E5C for <quic@ietf.org>; Tue,  2 Oct 2018 05:55:58 -0700 (PDT)
Received: from eggert.org (unknown [62.248.255.56]) by emh03.mail.saunalahti.fi (Postfix) with ESMTP id A7AAB40208; Tue,  2 Oct 2018 15:55:56 +0300 (EEST)
Received: from slate.eggert.org (pf.eggert.org [172.16.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by eggert.org (Postfix) with ESMTPSA id B587361DC23; Tue,  2 Oct 2018 15:55:51 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: Re: Spin bit decision
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com>
Date: Tue, 2 Oct 2018 15:55:50 +0300
Cc: IETF QUIC WG <quic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com>
To: "<alexandre.ferrieux@orange.com>" <alexandre.ferrieux@orange.com>
X-Mailer: Apple Mail (2.3445.100.39)
X-MailScanner-ID: B587361DC23.A3499
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/t-GYUFYML8OtC_gDnAiczuknGeE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 12:56:01 -0000

Hi,

again, as an individual:

On 2018-10-2, at 15:41, <alexandre.ferrieux@orange.com> =
<alexandre.ferrieux@orange.com> wrote:
> Well, if the spec says that en endpoint MUST copy of flip a bit, an =
implementor would be fairly ill-advised not do comply.

sure, it may be "ill-advised", but in practice, it won't affect interop =
at all.

> And nothing prevents from adding a "does it spin ?" criterion to the =
interop test suite.

We can certainly consider this - it may give us some data about the =
current capabilities and configurations of the participating stacks.

> Clearly you now have this degree of freedom: weaken that MUST into a =
MAY or a SHOULD, separately for each role. But for what purpose ?

The point I'm trying to make is that it in practice doesn't matter if =
the spec says "MUST", "SHOULD" or "MAY", since it doesn't affect =
interop, and doesn't affect performance. Essentially, each stack can =
decide in isolation whether to spin, echo, do nothing, grease the bits, =
etc., no matter what language we put in the spec.

Lars=


From nobody Tue Oct  2 05:59:43 2018
Return-Path: <mikkelfj@gmail.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 63080127598 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 05:59:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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_PASS=-0.001, UNPARSEABLE_RELAY=0.001] 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 pLCNY2KM1pI3 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 05:59:40 -0700 (PDT)
Received: from mail-ot1-x333.google.com (mail-ot1-x333.google.com [IPv6:2607:f8b0:4864:20::333]) (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 5AC3F124D68 for <quic@ietf.org>; Tue,  2 Oct 2018 05:59:40 -0700 (PDT)
Received: by mail-ot1-x333.google.com with SMTP id c18-v6so1760047otm.3 for <quic@ietf.org>; Tue, 02 Oct 2018 05:59:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=w7TWozWdoZV412F0h66SXvxq7iy0XLoFf7Y41FWdlAM=; b=Y50gpFkgpBzee1NArGRkObIdYb4KPRvX2kiFxo0xxK38omgh/H5oAvxeAKqQR/w70w jUXjgc/7p5A9PhEr2QBZLCnu1ftNCLi6rQhey0CsNAiCsYTtEVfp5UrYkZV5hsAXWKcb gyDYlAJyUb10o5WJNyP1PTHtFq9OBvvvrBjxjjc3MRq4K8VDgKNT7P2eWyXJ3tkLaO1S X6Em0ewMIvDyxlWrdb+hbwnPpOSBPnce9zDvfROdzEoT+K44EbjMpKAdB8/VpdWH6IiP DxV/EeuwqJb95lIOH6r9D7Q5eQUPvfmMDQg3M0sXmbdIRbMSKThvRqs+O37YzYGlGenm oCbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=w7TWozWdoZV412F0h66SXvxq7iy0XLoFf7Y41FWdlAM=; b=FTOzO7Rhzx/jwq2qC8PgZj6WQYr5At1ayCuFrMKZGF5atSovS8Cb2cMvF8f7S2jA/q 92ErQG34KgHdhrU6/svHrmt9tEV7gK2q6vRgwgPhLnaZDxmhosxWgG+EyeBfKr+Do8lN yaRoMY62fNAAA7gmnQgew7Rlp3VzNDsgHaK/5Dkg4zoejzsn750muWe6UeGDRSlpxm2W ChodD4Dqiv0xGcWYbfH1pxT/tEx0hYNYP5nycCfjmgZPtzUS35cFQA7xT5G5wt3SUXgJ FdQ8p8AhwY6QqSl8axXB92YgyDxybanjyg/2BMhmnKwsYqnSH6xCO4Ubs2izWw9cYmMN TE3g==
X-Gm-Message-State: ABuFfoiRkiq2IxmgA2AAnGNtaD8r3Wx29nw9UMpbvQLmQbEcBxaxrmo/ BtxuqBfWsUcB+ocnr11F7f5GcsawlG0sDn8Jmhc=
X-Google-Smtp-Source: ACcGV60wZMa+lKEy+rV0rsPH7xCE31uOH4BqPJEqQV7gGC7PKNop7KR3iCCkV8nomLnEKezG2074CIlkpT88FqiJok0=
X-Received: by 2002:a9d:429a:: with SMTP id r26mr3527035ote.337.1538485179703;  Tue, 02 Oct 2018 05:59:39 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 2 Oct 2018 05:59:39 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Tue, 2 Oct 2018 05:59:38 -0700
Message-ID: <CAN1APdcn8Fjbz7XGT4mkCaS503fFCPXaz0X6Qem6eFY4LtD4rg@mail.gmail.com>
Subject: Re: Spin bit decision
To: Lars Eggert <lars@eggert.org>,  "<alexandre.ferrieux@orange.com>" <alexandre.ferrieux@orange.com>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a0e55905773e7e51"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/SxFnmuqbQUKo5G5acebNrSBLTzw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 12:59:43 -0000

--000000000000a0e55905773e7e51
Content-Type: text/plain; charset="UTF-8"

Are there any concerns about impact and how to handle or ignore malicious
manipulation of the spin either by endpoint or a middlebox?



On 2 October 2018 at 14.56.16, Lars Eggert (lars@eggert.org) wrote:

Hi,

again, as an individual:

On 2018-10-2, at 15:41, <alexandre.ferrieux@orange.com> <
alexandre.ferrieux@orange.com> wrote:
> Well, if the spec says that en endpoint MUST copy of flip a bit, an
implementor would be fairly ill-advised not do comply.

sure, it may be "ill-advised", but in practice, it won't affect interop at
all.

> And nothing prevents from adding a "does it spin ?" criterion to the
interop test suite.

We can certainly consider this - it may give us some data about the current
capabilities and configurations of the participating stacks.

> Clearly you now have this degree of freedom: weaken that MUST into a MAY
or a SHOULD, separately for each role. But for what purpose ?

The point I'm trying to make is that it in practice doesn't matter if the
spec says "MUST", "SHOULD" or "MAY", since it doesn't affect interop, and
doesn't affect performance. Essentially, each stack can decide in isolation
whether to spin, echo, do nothing, grease the bits, etc., no matter what
language we put in the spec.

Lars

--000000000000a0e55905773e7e51
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Are there any concer=
ns about impact and how to handle or ignore malicious manipulation of the s=
pin either by endpoint or a middlebox?</div><div id=3D"bloop_customfont" st=
yle=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);mar=
gin:0px;line-height:auto"><br></div><div id=3D"bloop_sign_15384850658859811=
84" class=3D"bloop_sign"><div style=3D"font-family:helvetica,arial;font-siz=
e:13px"><br></div></div> <br><p class=3D"airmail_on">On 2 October 2018 at 1=
4.56.16, Lars Eggert (<a href=3D"mailto:lars@eggert.org">lars@eggert.org</a=
>) wrote:</p> <blockquote type=3D"cite" class=3D"clean_bq"><span><div><div>=
</div><div>Hi,
<br>
<br>again, as an individual:
<br>
<br>On 2018-10-2, at 15:41, &lt;<a href=3D"mailto:alexandre.ferrieux@orange=
.com">alexandre.ferrieux@orange.com</a>&gt; &lt;<a href=3D"mailto:alexandre=
.ferrieux@orange.com">alexandre.ferrieux@orange.com</a>&gt; wrote:
<br>&gt; Well, if the spec says that en endpoint MUST copy of flip a bit, a=
n implementor would be fairly ill-advised not do comply.
<br>
<br>sure, it may be &quot;ill-advised&quot;, but in practice, it won&#39;t =
affect interop at all.
<br>
<br>&gt; And nothing prevents from adding a &quot;does it spin ?&quot; crit=
erion to the interop test suite.
<br>
<br>We can certainly consider this - it may give us some data about the cur=
rent capabilities and configurations of the participating stacks.
<br>
<br>&gt; Clearly you now have this degree of freedom: weaken that MUST into=
 a MAY or a SHOULD, separately for each role. But for what purpose ?
<br>
<br>The point I&#39;m trying to make is that it in practice doesn&#39;t mat=
ter if the spec says &quot;MUST&quot;, &quot;SHOULD&quot; or &quot;MAY&quot=
;, since it doesn&#39;t affect interop, and doesn&#39;t affect performance.=
 Essentially, each stack can decide in isolation whether to spin, echo, do =
nothing, grease the bits, etc., no matter what language we put in the spec.
<br>
<br>Lars
<br></div></div></span></blockquote></body></html>

--000000000000a0e55905773e7e51--


From nobody Tue Oct  2 06:01:49 2018
Return-Path: <ietf@trammell.ch>
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 54AC81292F1 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 06:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 vNivBNY6m8KK for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 06:01:44 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [IPv6:2001:8e0:40:325::36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71217127598 for <quic@ietf.org>; Tue,  2 Oct 2018 06:01:44 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 59115341AF6; Tue,  2 Oct 2018 15:01:42 +0200 (CEST)
X-Iway-Path: 0
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/14501.14531); Tue,  2 Oct 2018 15:01:41 +0200 (CEST)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Tue,  2 Oct 2018 15:01:41 +0200 (CEST)
Received: from [195.176.110.228] (account ietf@trammell.ch HELO public-docking-etx-1035.ethz.ch) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 69089750; Tue, 02 Oct 2018 15:01:41 +0200
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <69FB07C4-8DCD-448F-A4B9-9C68E70E9907@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_F0695ED7-41F3-4726-B263-DC544361A7ED"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: Spin bit decision
Date: Tue, 2 Oct 2018 15:01:40 +0200
In-Reply-To: <CAN1APdcn8Fjbz7XGT4mkCaS503fFCPXaz0X6Qem6eFY4LtD4rg@mail.gmail.com>
Cc: Lars Eggert <lars@eggert.org>, "<alexandre.ferrieux@orange.com>" <alexandre.ferrieux@orange.com>, IETF QUIC WG <quic@ietf.org>
To: =?utf-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <CAN1APdcn8Fjbz7XGT4mkCaS503fFCPXaz0X6Qem6eFY4LtD4rg@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/lDJAV5MrCPHUUfmdFbzMGK1Dm3o>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 13:01:47 -0000

--Apple-Mail=_F0695ED7-41F3-4726-B263-DC544361A7ED
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Yes. See the last two paragraphs of section 6 of the current (TSVWG) =
full spin bit draft: =
https://tools.ietf.org/html/draft-trammell-tsvwg-spin-00.

> On 2 Oct 2018, at 14:59, Mikkel Fahn=C3=B8e J=C3=B8rgensen =
<mikkelfj@gmail.com> wrote:
>=20
> Are there any concerns about impact and how to handle or ignore =
malicious manipulation of the spin either by endpoint or a middlebox?
>=20
>=20
>=20
> On 2 October 2018 at 14.56.16, Lars Eggert (lars@eggert.org) wrote:
>=20
>> Hi,
>>=20
>> again, as an individual:
>>=20
>> On 2018-10-2, at 15:41, <alexandre.ferrieux@orange.com> =
<alexandre.ferrieux@orange.com> wrote:
>> > Well, if the spec says that en endpoint MUST copy of flip a bit, an =
implementor would be fairly ill-advised not do comply.
>>=20
>> sure, it may be "ill-advised", but in practice, it won't affect =
interop at all.
>>=20
>> > And nothing prevents from adding a "does it spin ?" criterion to =
the interop test suite.
>>=20
>> We can certainly consider this - it may give us some data about the =
current capabilities and configurations of the participating stacks.
>>=20
>> > Clearly you now have this degree of freedom: weaken that MUST into =
a MAY or a SHOULD, separately for each role. But for what purpose ?
>>=20
>> The point I'm trying to make is that it in practice doesn't matter if =
the spec says "MUST", "SHOULD" or "MAY", since it doesn't affect =
interop, and doesn't affect performance. Essentially, each stack can =
decide in isolation whether to spin, echo, do nothing, grease the bits, =
etc., no matter what language we put in the spec.
>>=20
>> Lars


--Apple-Mail=_F0695ED7-41F3-4726-B263-DC544361A7ED
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAluzbDQACgkQihK3vwvq
RqM+4RAAk3ajkD2x+RenNundwAP6dSzxxY8bdSGW4zXvUyTkxyxbLZ3MO7eBX073
3Ifhox0mgaibLc5W6+fGN3bNsLbcsjUYwqq7Ztjd4gBGWkGBp0aUsSu1O/KyZwJ4
zdDCZtsBAFIqWuv64V1cCN2Cy3xpqIc/p6CSiKvrdD5LGqHzbHf8eoi9NJSJkygP
MfQPDi9aYWq22lNzytRF5SO5zZgiRP9VeZBZeMHQ2KSybDWCjU3fEniHVXynU008
9K+QV76NwD54HVWY3VZJhtQiOU/QFmN8P1GcJkSouOu1j/tNpS4Vz8nF2nYT7On+
hSmuiNi3W+22ug5g2tSpTvLKliW1zTAbA/mkWe2f4GpQzFBwg3F+is3YZuI8p34v
9dHFG0gnZSOS8nHiGYmtL9fWgb6jM4PqSAQO3mFgxJdzo/fq6Xyy/CWnHqfdoTLi
g1yMYiBVzFKzj1vYTT+PDBu9biafauFS9V6+QCPXacqpW1OazfoKmsyg39wvsTk7
ypXpM3NY9hmQgptJP2r16creKn+SUuU0/06CaF3/i1GEvhw0g3YakweDWrN+bEKA
Z62FUhRFxHCMtJFaSK1/TwaBWl8auDv4z2Jst85126g+QDwOWUjdvxqigJlkZ/gC
CkOKC6clLIu9TMwOHd6The04KPIr8sOgpfF+iRaP/6J/ls/yIvc=
=fvmK
-----END PGP SIGNATURE-----

--Apple-Mail=_F0695ED7-41F3-4726-B263-DC544361A7ED--


From nobody Tue Oct  2 06:08:47 2018
Return-Path: <alexandre.ferrieux@orange.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 3CE961277BB for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 06:08:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.291
X-Spam-Level: 
X-Spam-Status: No, score=-0.291 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 7Rv6_Zqa2UBZ for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 06:08:45 -0700 (PDT)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C48B127598 for <quic@ietf.org>; Tue,  2 Oct 2018 06:08:45 -0700 (PDT)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) by opfednr27.francetelecom.fr (ESMTP service) with ESMTP id 42Pfbv3XGFz4x84; Tue,  2 Oct 2018 15:08:43 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfednr02.francetelecom.fr (ESMTP service) with ESMTP id 42Pfbv2ZZrz8sY7; Tue,  2 Oct 2018 15:08:43 +0200 (CEST)
Received: from [10.193.4.89] (10.168.234.6) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 2 Oct 2018 15:08:43 +0200
Subject: Re: Spin bit decision
To: Lars Eggert <lars@eggert.org>
CC: IETF QUIC WG <quic@ietf.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org>
From: <alexandre.ferrieux@orange.com>
Message-ID: <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com>
Date: Tue, 2 Oct 2018 15:07:02 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.168.234.6]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/CV9X_qo73Ju3-d1ljgoXn34ezCg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 13:08:46 -0000

On 10/02/18 14:55, Lars Eggert wrote:
> Hi,
> 
> again, as an individual:
> 
> On 2018-10-2, at 15:41, <alexandre.ferrieux@orange.com> <alexandre.ferrieux@orange.com> wrote:
>> Well, if the spec says that en endpoint MUST copy of flip a bit, an implementor would be fairly ill-advised not do comply.
> 
> sure, it may be "ill-advised", but in practice, it won't affect interop at all.
> 
>> And nothing prevents from adding a "does it spin ?" criterion to the interop test suite.
> 
> We can certainly consider this - it may give us some data about the current capabilities and configurations of the participating stacks.

More than that: you seem to be implying that automated interop testing outweighs 
textual specification. No problem with that; let's focus on test definition then.

>> Clearly you now have this degree of freedom: weaken that MUST into a MAY or a SHOULD, separately for each role. But for what purpose ?
> 
> The point I'm trying to make is that it in practice doesn't matter if the spec says "MUST", "SHOULD" or "MAY", since it doesn't affect interop, and doesn't affect performance. Essentially, each stack can decide in isolation whether to spin, echo, do nothing, grease the bits, etc., no matter what language we put in the spec.

Sure. So, what is there to lose by saying "MUST" anyway ?


_________________________________________________________________________________________________________________________

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.


From nobody Tue Oct  2 07:01:00 2018
Return-Path: <lars@eggert.org>
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 68E06130E6C for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 07:00:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 wjoOyn-ajtJE for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 07:00:51 -0700 (PDT)
Received: from emh03.mail.saunalahti.fi (emh03.mail.saunalahti.fi [62.142.5.109]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AB54130E48 for <quic@ietf.org>; Tue,  2 Oct 2018 07:00:51 -0700 (PDT)
Received: from eggert.org (unknown [62.248.255.56]) by emh03.mail.saunalahti.fi (Postfix) with ESMTP id E4CA140138; Tue,  2 Oct 2018 17:00:49 +0300 (EEST)
Received: from slate.eggert.org (pf.eggert.org [172.16.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by eggert.org (Postfix) with ESMTPSA id C041961097C; Tue,  2 Oct 2018 17:00:17 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: Re: Spin bit decision
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com>
Date: Tue, 2 Oct 2018 17:00:17 +0300
Cc: IETF QUIC WG <quic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7479831-9594-444E-9545-A162E8D9B154@eggert.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com>
To: "<alexandre.ferrieux@orange.com>" <alexandre.ferrieux@orange.com>
X-Mailer: Apple Mail (2.3445.100.39)
X-MailScanner-ID: C041961097C.A3D80
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2zOHcTFM3ogw6p5e1iJPyBmpPLg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 14:00:59 -0000

Hi,

yet again as an individual.

On 2018-10-2, at 16:07, alexandre.ferrieux@orange.com wrote:
> On 10/02/18 14:55, Lars Eggert wrote:
>> We can certainly consider this - it may give us some data about the =
current capabilities and configurations of the participating stacks.
>=20
> More than that: you seem to be implying that automated interop testing =
outweighs textual specification. No problem with that; let's focus on =
test definition then.

I'm not implying that at all, and I'm confused as to why you'd think so?

>>> Clearly you now have this degree of freedom: weaken that MUST into a =
MAY or a SHOULD, separately for each role. But for what purpose ?
>> The point I'm trying to make is that it in practice doesn't matter if =
the spec says "MUST", "SHOULD" or "MAY", since it doesn't affect =
interop, and doesn't affect performance. Essentially, each stack can =
decide in isolation whether to spin, echo, do nothing, grease the bits, =
etc., no matter what language we put in the spec.
>=20
> Sure. So, what is there to lose by saying "MUST" anyway ?

This is a discussion the WG needs to have after there is consensus to =
merge the spin bit proposal.

The point I can't seem to be getting across is that irrespective of what =
the WG decides to require, there is no penalty for individual stacks at =
deployment time (or after) to do whatever they wish, since the spin bit =
by design has no impact on protocol operation and interop.

Lars=


From nobody Tue Oct  2 07:26:20 2018
Return-Path: <nibanks@microsoft.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 0F8E7130EB0 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 07:26:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.457
X-Spam-Level: 
X-Spam-Status: No, score=-2.457 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 IWHpVe5NGGSg for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 07:26:10 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0119.outbound.protection.outlook.com [104.47.36.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B9A7130E83 for <quic@ietf.org>; Tue,  2 Oct 2018 07:26:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jX4A0bGZLVMLTA24N3M4gvwR/Vc22pTJ8McBjTYjWbk=; b=EaUzPvnzhMNBVjh8Sz7cCWiotCA/keOahRTtblbQohiaZItgqTK/GLxus4pTR36mNc66q9l2zSMq54TZSVgkiF1WKhMuH0rVgD52erqXxVY+An0wNptH/rmYKq8ezWUB+jfubGmf7eKiOKntNfQd+mqKSL9qph/Sa3REhZwsnCM=
Received: from DM5PR2101MB0901.namprd21.prod.outlook.com (52.132.132.158) by DM5PR2101MB0968.namprd21.prod.outlook.com (52.132.133.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1228.4; Tue, 2 Oct 2018 14:26:06 +0000
Received: from DM5PR2101MB0901.namprd21.prod.outlook.com ([fe80::f586:795d:7d52:8f36]) by DM5PR2101MB0901.namprd21.prod.outlook.com ([fe80::f586:795d:7d52:8f36%2]) with mapi id 15.20.1228.007; Tue, 2 Oct 2018 14:26:06 +0000
From: Nick Banks <nibanks@microsoft.com>
To: Lars Eggert <lars@eggert.org>, "<alexandre.ferrieux@orange.com>" <alexandre.ferrieux@orange.com>
CC: IETF QUIC WG <quic@ietf.org>
Subject: RE: Spin bit decision
Thread-Topic: Spin bit decision
Thread-Index: AQHUWhYtSdEA9yvRQkC4HtiqCaoEeaULhImAgAAbI4CAACozgIAAHI6AgAAD4wCAAAMhAIAADuGAgAAGIZA=
Date: Tue, 2 Oct 2018 14:26:06 +0000
Message-ID: <DM5PR2101MB09014906B258D1F96179D085B3E80@DM5PR2101MB0901.namprd21.prod.outlook.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org>
In-Reply-To: <E7479831-9594-444E-9545-A162E8D9B154@eggert.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=nibanks@microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2018-10-02T14:26:04.1748017Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic; Sensitivity=General
x-originating-ip: [2001:4898:80e8:1:d143:977d:dfba:37c6]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR2101MB0968; 6:yZPHKIQ3Ye4puJPZXiFMHp23T623cuS0j1qmXMyzY1LPUDDlBlJJnId5e+fUShZpT+fV6lrNX3S5xzZUbn+vGuPEEwabNERYQLv6Guj0tLpbon/mlYbDdIXj5R54+hMRdXpkGiwp/mbKD1itss9Z6csdXcLsHm3IWaH4avzxlCDMK5M6Q5nrQoFdvUz3gNrpcvFxzdXw4+SKr3KOYRkBRMD06ZV62dVDgLu8J5WHo4L5Qd5KlWqfzjwSdOh688ufGDki9PgWuk+sPJPm8QVdBkJ5xZ/2lo7qY2QbJzh6uRi/nKWDYcekQl1Wr/4MudjhgPjJBu1YtJXUiImMwKVCVhBr6csxhGrtP8q5OgvVnqvI/MHP8hgeoUiplNtzGC3718gvc+cOj5aGvggM7VqEe3dWqpmqCiyRAuRS9Pm5p5sZleR/9cfFxA9p1E4umpKT2DOyWUwQWe6nZQ+po2+XSg==; 5:l0Z9x2xhmNgJAiLUPNJL4+DgN+xDqnIxmxZRQBMJ6B58HduNMG7c1GouR8NAb+PKmt2R+DqTctrHnHJrV9PTfXSDgLNFXprvUao9xBAkElCG2nYtlDfLz90y1Eoau7i4+piaHaiLD69zCkr6oXJXo9d35DOJv7YyTn74LpCI2NY=; 7:e4eLIhrnFTzWUSIgwUYYZH8QpEkTHyL4RaCnvqBo/aQetgpkbrMV17aEa8R2UsPjmmsClJI7IJ8MbQYf52XYvVhgF9xmnDDw80u/yF3C0CKOtMkMjwv2zWIAvqIlzs7Xgo/ZGejz//siOQjLHJxAs6FrFmwoKD2GK2mYgZo3NecmtLp+fnA+PP5QpRrK3v6PGSI8+bndwzgjpSRIZjrccnZ5wcGoynOLPCZI86ysSawjkPaSSbqlopvxEgkjy+5p
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 4fe6f430-7ba6-4343-5527-08d62872fd7e
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534165)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7193020); SRVR:DM5PR2101MB0968; 
x-ms-traffictypediagnostic: DM5PR2101MB0968:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=nibanks@microsoft.com; 
x-microsoft-antispam-prvs: <DM5PR2101MB09686A89B3551D8278A1ED97B3E80@DM5PR2101MB0968.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(18271650672692)(161740460382875)(100405760836317); 
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(10201501046)(3002001)(93006095)(93001095)(3231355)(944501410)(52105095)(2018427008)(6055026)(149066)(150057)(6041310)(20161123564045)(20161123562045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(20161123558120)(201708071742011)(7699051)(76991041); SRVR:DM5PR2101MB0968; BCL:0; PCL:0; RULEID:; SRVR:DM5PR2101MB0968; 
x-forefront-prvs: 0813C68E65
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(39860400002)(366004)(376002)(346002)(396003)(199004)(189003)(13464003)(7736002)(305945005)(99286004)(5660300001)(6246003)(229853002)(186003)(5250100002)(2900100001)(10290500003)(4326008)(46003)(508600001)(106356001)(7696005)(71200400001)(71190400001)(7116003)(74316002)(102836004)(6116002)(76176011)(53546011)(6506007)(110136005)(53936002)(86612001)(81156014)(81166006)(9686003)(3480700004)(316002)(68736007)(22452003)(55016002)(8676002)(25786009)(33656002)(86362001)(561944003)(14444005)(256004)(486006)(97736004)(4001150100001)(10090500001)(11346002)(476003)(2906002)(105586002)(8936002)(93886005)(446003)(6436002)(14454004)(8990500004)(491001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR2101MB0968; H:DM5PR2101MB0901.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: K+ww0HwbwpCPUcL2YX95xO0YGLBCeHzGNDwaInBzttuLkGf81oK4tGOvslc8GdMY5vGWOLgxwm8FnLIi2UyHV8D7ZDbpiouZsLPcefjpKUwYo5Hx9BgmZvQCfE2Y288PfjXMHv1FQcr2XPXkHgWK5kRWu67BblED2V61NNBN05pNlderLGTA914m00Nb27CSBKGYkjIfKj25To7IREeXBUH8LapnD1fkHs2iRKqnTh7Zs2M0cfHzlakKQz1bYZ7JG3OUQ93boL+luFZT3hJi7J9sAO3/1Z8e+mol3yFIvBnu1NZPHaqmrGodn70uDvfl0/4gmOhfcr9ccbTgpfsbfEVe4B+G/7uu/hAKYznD5js=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4fe6f430-7ba6-4343-5527-08d62872fd7e
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Oct 2018 14:26:06.1920 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR2101MB0968
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/3liuvFKPltXAbTMtoOF9YkC36QM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 14:26:15 -0000

If we decide to make it a MUST, it seems to me that it would be pretty easy=
 to add some logic to check that your peer is 'spinning' the bit. If they a=
re not, after a couple of RTTs just to make sure, you could close the conne=
ction (add a new PEER_NOT_SPINNING error code). If just one or two major im=
plementations implement the validation logic, then we could ensure interop =
and compliance for the most part.

- Nick

-----Original Message-----
From: QUIC <quic-bounces@ietf.org> On Behalf Of Lars Eggert
Sent: Tuesday, October 2, 2018 7:00 AM
To: <alexandre.ferrieux@orange.com> <alexandre.ferrieux@orange.com>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Spin bit decision

Hi,

yet again as an individual.

On 2018-10-2, at 16:07, alexandre.ferrieux@orange.com wrote:
> On 10/02/18 14:55, Lars Eggert wrote:
>> We can certainly consider this - it may give us some data about the curr=
ent capabilities and configurations of the participating stacks.
>=20
> More than that: you seem to be implying that automated interop testing ou=
tweighs textual specification. No problem with that; let's focus on test de=
finition then.

I'm not implying that at all, and I'm confused as to why you'd think so?

>>> Clearly you now have this degree of freedom: weaken that MUST into a MA=
Y or a SHOULD, separately for each role. But for what purpose ?
>> The point I'm trying to make is that it in practice doesn't matter if th=
e spec says "MUST", "SHOULD" or "MAY", since it doesn't affect interop, and=
 doesn't affect performance. Essentially, each stack can decide in isolatio=
n whether to spin, echo, do nothing, grease the bits, etc., no matter what =
language we put in the spec.
>=20
> Sure. So, what is there to lose by saying "MUST" anyway ?

This is a discussion the WG needs to have after there is consensus to merge=
 the spin bit proposal.

The point I can't seem to be getting across is that irrespective of what th=
e WG decides to require, there is no penalty for individual stacks at deplo=
yment time (or after) to do whatever they wish, since the spin bit by desig=
n has no impact on protocol operation and interop.

Lars


From nobody Tue Oct  2 07:44:37 2018
Return-Path: <alexandre.ferrieux@orange.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 300D2130E9A for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 07:44:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.291
X-Spam-Level: 
X-Spam-Status: No, score=-0.291 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 W0CeWA-VOn9Y for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 07:44:34 -0700 (PDT)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74E68130E78 for <quic@ietf.org>; Tue,  2 Oct 2018 07:44:34 -0700 (PDT)
Received: from opfednr03.francetelecom.fr (unknown [xx.xx.xx.67]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id 42PhkS69pnz5wTy; Tue,  2 Oct 2018 16:44:32 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfednr03.francetelecom.fr (ESMTP service) with ESMTP id 42PhkS4WlDzDq7T; Tue,  2 Oct 2018 16:44:32 +0200 (CEST)
Received: from [10.193.4.89] (10.168.234.4) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 2 Oct 2018 16:44:32 +0200
Subject: Re: Spin bit decision
To: Nick Banks <nibanks@microsoft.com>, Lars Eggert <lars@eggert.org>
CC: IETF QUIC WG <quic@ietf.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <DM5PR2101MB09014906B258D1F96179D085B3E80@DM5PR2101MB0901.namprd21.prod.outlook.com>
From: <alexandre.ferrieux@orange.com>
Message-ID: <13400_1538491472_5BB38450_13400_128_3_495d8ee9-3875-e72b-1a6a-8a44e58cd4b4@orange.com>
Date: Tue, 2 Oct 2018 16:42:50 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <DM5PR2101MB09014906B258D1F96179D085B3E80@DM5PR2101MB0901.namprd21.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: fr-xx-moderne
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.168.234.4]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/kV7EFkN-rVh777AZDKrQ-J2iaqg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 14:44:36 -0000

Exactly. It is only a question of deciding we want it.


On 10/02/18 16:26, Nick Banks wrote:
> If we decide to make it a MUST, it seems to me that it would be pretty easy to add some logic to check that your peer is 'spinning' the bit. If they are not, after a couple of RTTs just to make sure, you could close the connection (add a new PEER_NOT_SPINNING error code). If just one or two major implementations implement the validation logic, then we could ensure interop and compliance for the most part.
> 
> - Nick
> 
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of Lars Eggert
> Sent: Tuesday, October 2, 2018 7:00 AM
> To: <alexandre.ferrieux@orange.com> <alexandre.ferrieux@orange.com>
> Cc: IETF QUIC WG <quic@ietf.org>
> Subject: Re: Spin bit decision
> 
> Hi,
> 
> yet again as an individual.
> 
> On 2018-10-2, at 16:07, alexandre.ferrieux@orange.com wrote:
>> On 10/02/18 14:55, Lars Eggert wrote:
>>> We can certainly consider this - it may give us some data about the current capabilities and configurations of the participating stacks.
>> 
>> More than that: you seem to be implying that automated interop testing outweighs textual specification. No problem with that; let's focus on test definition then.
> 
> I'm not implying that at all, and I'm confused as to why you'd think so?
> 
>>>> Clearly you now have this degree of freedom: weaken that MUST into a MAY or a SHOULD, separately for each role. But for what purpose ?
>>> The point I'm trying to make is that it in practice doesn't matter if the spec says "MUST", "SHOULD" or "MAY", since it doesn't affect interop, and doesn't affect performance. Essentially, each stack can decide in isolation whether to spin, echo, do nothing, grease the bits, etc., no matter what language we put in the spec.
>> 
>> Sure. So, what is there to lose by saying "MUST" anyway ?
> 
> This is a discussion the WG needs to have after there is consensus to merge the spin bit proposal.
> 
> The point I can't seem to be getting across is that irrespective of what the WG decides to require, there is no penalty for individual stacks at deployment time (or after) to do whatever they wish, since the spin bit by design has no impact on protocol operation and interop.
> 
> Lars
> 


_________________________________________________________________________________________________________________________

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.


From nobody Tue Oct  2 07:45:20 2018
Return-Path: <ietf@trammell.ch>
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 BE27D130EB1 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 07:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 LrNX8tBqn9_P for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 07:45:15 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [IPv6:2001:8e0:40:325::36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5430130E78 for <quic@ietf.org>; Tue,  2 Oct 2018 07:45:14 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id EC589341AD5; Tue,  2 Oct 2018 16:45:12 +0200 (CEST)
X-Iway-Path: 0
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/14501.21808); Tue,  2 Oct 2018 16:45:12 +0200 (CEST)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Tue,  2 Oct 2018 16:45:12 +0200 (CEST)
Received: from [195.176.110.228] (account ietf@trammell.ch HELO public-docking-etx-1035.ethz.ch) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 69104365; Tue, 02 Oct 2018 16:45:12 +0200
From: Brian Trammell (IETF) <ietf@trammell.ch>
Message-Id: <BB87D8D0-DA01-4C0F-B557-2A728BF19A64@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_CCA9482D-B9C4-4C39-B94C-278DA1AD019A"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: Spin bit decision
Date: Tue, 2 Oct 2018 16:45:11 +0200
In-Reply-To: <HE1PR0701MB2393CDB16819A54B33D22417E2E80@HE1PR0701MB2393.eurprd07.prod.outlook.com>
Cc: Lars Eggert <lars@eggert.org>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, "quic@ietf.org" <quic@ietf.org>
To: Marcus Ihlar <marcus.ihlar@ericsson.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <HE1PR0701MB2393CDB16819A54B33D22417E2E80@HE1PR0701MB2393.eurprd07.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ZMN0P6D3HrO7Ps2spv_Y1evYeXg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 14:45:19 -0000

--Apple-Mail=_CCA9482D-B9C4-4C39-B94C-278DA1AD019A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Marcus, Lars, all,

> On 2 Oct 2018, at 13:44, Marcus Ihlar <marcus.ihlar@ericsson.com> =
wrote:
>=20

(=E2=80=A6note: not sure about any of the quoting below=E2=80=A6)

> so what fraction of spin-enabled QUIC traffic would be sufficient? =
Maybe just a ballpark number; 1%, 10%, 100%?
>=20
> MI: It=C2=B4s a difficult question to answer as there are different =
uses of the spin information ranging from active troubleshooting =
sessions for a small set of subscribers to passive monitoring on a large =
scale e.g for KPI dashboards.
>> =46rom a spin consumer perspective the bigger the fraction the better =
of course, but the pain thresholds would be different from usecase to =
usecase.
> The active troubleshooting case would require either that a very large =
portion of traffic is spin-enabled or that it would be possible for a =
user to selectively enable the functionality.
> The large scale monitoring case would likely be useful even if  only a =
few % of flows are spin-enabled.

In any situation other than 100% participation, I think it will be =
necessary to have client opt-in be exposed up to the user for intraflow =
diagnostics using the spin bit.

(yes, once you=E2=80=99re opting in, quictrace gives you all that the =
spin bit does and more, but I don=E2=80=99t see it as a reasonable =
replacement for the spin bit: first, =E2=80=9Csend me a trace=E2=80=9D =
scales way less well than automated =E2=80=9Clocking on=E2=80=9D to an =
available one-bit signal; second, just exposing RTT is somewhat less =
risky than exposing the full operation of the transport to a =
partially-trusted operator. quictrace seems more like a debugging tool =
than an operational diagnostics tool to me. It=E2=80=99s a very cool =
one, and one we really need to standardize, hopefully after stripping =
the protobuf cruft off of it, but these questions are IMO completely =
separate=E2=80=A6)

I=E2=80=99m more optimistic than Marcus is with respect to the utility =
of the spin bit for aggregate (link / path-level) measurements even with =
small amounts of deployment. It is relatively easy for a midpoint to =
recognize whether the bit spins or not, and to make those RTT samples =
available to the aggregate sample (or aggregate baseline / residual) on =
demand. So for a given aggregate, as long as there's one available =
active flow, the spin bit provides good RTT samples. This points to even =
one part in a thousand being useful in the Internet core.

IMO (and this is an opinion; I don't think anyone will have enough data =
to answer this question for real before Bangkok), as you say one =
"hyperscalar" turning the spin bit on -- even probabalistically, e.g. as =
Apple did (still does?) during transition to ECN-by-default on the =
client side -- would provide more than enough signal on the paths =
between the access networks of its users (most of them) and the =
network(s) through which it provides its services.

This would also be the case if one of the top-N CDNs and one major =
browser vendor did so (again, probabilistic activation suffices). The =
larger the set of the server networks implementing, the more coverage =
one would have for access and core network paths.

Cheers,

Brian



--Apple-Mail=_CCA9482D-B9C4-4C39-B94C-278DA1AD019A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAluzhHcACgkQihK3vwvq
RqPRTxAAyWCJQJ58sA+qTDskTpedP5XkZyqtevJKBhCSgXVKKOOw51akH3NhBFcg
z0gRSxbRHin4EcIWlghDaL7ee3gyVNxrKhIuJ5lFEC6Y3tITUgwhl8z3ORk38ymf
4FpGfxMiMLHPyS0ljd9s2sBeW2c7JpuJ4IGkFQGuKaZZhzuB4+mWdXpcPIVrYoBO
5zFOl5pu9baDqjVbSMN3Yj24xRtO6EoK2sxAlMd0Rs4mHWUoS+mc8tvA8B6AXXIs
nio9o6n75+mozhUhlQB0EjUv/e1N1sV7Lj1TSMP2JiREtSsiQYuKNSzZR2cMqkgm
6DXgP/BsYLAXcNNDYmx8X5fUT7J+6jzj/lB1bj7frfGn9zdJ5FZSH103c/kftvg9
sZrLmira3RkVKBm7X8s6RCzR5aYNCRBfsBYr4d3ulLbZKNxsJgsxZLlzEFo6iM1u
qVnZxQpTuW/V9jSgNxfe1dvvTKCkyJfwYce10MmnwbTkRyuglPyV8WSBJSdNZfXB
GZaYctcBZQkCYH3pXNuksAJbi6NQCrwoQQey1vulgruTGLwlhC6L7NvO1UMm04/A
6Q2CpjAIiK3vto2lhjcjUWytNprBm9V/0cCaVP1WNFFHq7d1U7sgEWYpyxvAfkUS
H79GNfbsN0UvVZH4CVbr0lEvXkis7GUqw1UbyJUrNp5ZhutpZ70=
=2oPo
-----END PGP SIGNATURE-----

--Apple-Mail=_CCA9482D-B9C4-4C39-B94C-278DA1AD019A--


From nobody Tue Oct  2 07:48:17 2018
Return-Path: <Lucas.Pardue@bbc.co.uk>
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 5FFA1130E78 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 07:48:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable 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 hzX-h8KgfaSM for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 07:48:14 -0700 (PDT)
Received: from mailout0.cwwtf.bbc.co.uk (mailout0.cwwtf.bbc.co.uk [132.185.160.179]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A79A9128766 for <quic@ietf.org>; Tue,  2 Oct 2018 07:48:13 -0700 (PDT)
Received: from BGB01XI1009.national.core.bbc.co.uk (bgb01xi1009.national.core.bbc.co.uk [10.161.14.23]) by mailout0.cwwtf.bbc.co.uk (8.15.2/8.15.2) with ESMTP id w92Em5lM017265; Tue, 2 Oct 2018 15:48:05 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1009.national.core.bbc.co.uk ([10.161.14.23]) with mapi id 14.03.0408.000; Tue, 2 Oct 2018 15:48:05 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: Nick Banks <nibanks=40microsoft.com@dmarc.ietf.org>, Lars Eggert <lars@eggert.org>, "<alexandre.ferrieux@orange.com>" <alexandre.ferrieux@orange.com>
CC: IETF QUIC WG <quic@ietf.org>
Subject: RE: Spin bit decision
Thread-Topic: Spin bit decision
Thread-Index: AQHUWhYuY5uphqKTlk+gydAimQZJXKULc8WAgAAbJICAACozgIAAHI2AgAAD5ACAAAMhAIAADuGAgAAHNgCAABRogA==
Date: Tue, 2 Oct 2018 14:48:04 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BBAFFA3@bgb01xud1012>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <DM5PR2101MB09014906B258D1F96179D085B3E80@DM5PR2101MB0901.namprd21.prod.outlook.com>
In-Reply-To: <DM5PR2101MB09014906B258D1F96179D085B3E80@DM5PR2101MB0901.namprd21.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.19.161.211]
x-exclaimer-md-config: 1cd3ac1c-62e5-43f2-8404-6b688271c769
x-tm-as-product-ver: SMEX-12.5.0.1300-8.2.1013-24054.007
x-tm-as-result: No-12.612500-8.000000-10
x-tmase-matchedrid: 6otD/cJAac27lpQUW6Uvz7iMC5wdwKqdwZLXS0hN8p1CannV/b7f2eSt JsQxPDW9wQTqbLJ40jt6pJLn1hitZHrSP9RtGZYoma6DzXaohvOUctRw0zzl2nN4oJrDvdmBzEV DGnc+EfLYK6UiVCRRQY/I8ZCpajgJp4OKIC9Rc5UlqaDT/7H7l7MiWJGbehIJE84BOf/GC8xBpT Dv/pIBigVLdw2DpYln3GYRbGEerQSziThmwPb+1cK1Ib9JAALx+0Sg1I/+5cHMEmMJ+LiV/cINy MXk5L+I6DAgvE9hypaotEtc6aBglLvuuksuYzsCEmjTpXaUdN4PQyhEi9yXBZsoi2XrUn/J8m+h zBStansfRoCwBzgRYj3zSp73HMHc
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
x-tmase-result: 10--12.612500-8.000000
x-tmase-version: SMEX-12.5.0.1300-8.2.1013-24054.007
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/niHSZoKfmutlkINF1CrOXq20Pns>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 14:48:16 -0000

>If we decide to make it a MUST, it seems to me that it would be pretty eas=
y to
>add some logic to check that your peer is 'spinning' the bit. If they are =
not,
>after a couple of RTTs just to make sure, you could close the connection (=
add a
>new PEER_NOT_SPINNING error code). If just one or two major
>implementations implement the validation logic, then we could ensure
>interop and compliance for the most part.
>
>- Nick

A hypothetical spin stick.

With a cyncial endpoint operator hat on, I think the realisation spin bit b=
enefits could be minimal. Leading to little incentive to implement spin bit=
. Using a stick, like causing connection termination, sounds like it will i=
ntroduce fun and games for interop testing, and deployment on heterogenous =
real-world networks.

What's the carrot to offer a non-hyperscaler?


-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specif=
ically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------


From nobody Tue Oct  2 08:06:58 2018
Return-Path: <alexandre.ferrieux@orange.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 9ED06130E7D for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 08:06:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.291
X-Spam-Level: 
X-Spam-Status: No, score=-0.291 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 gobfdpnsEN45 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 08:06:55 -0700 (PDT)
Received: from orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 772B8130DDC for <quic@ietf.org>; Tue,  2 Oct 2018 08:06:55 -0700 (PDT)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) by opfednr22.francetelecom.fr (ESMTP service) with ESMTP id 42PjDF4kKFz10J2; Tue,  2 Oct 2018 17:06:53 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfednr00.francetelecom.fr (ESMTP service) with ESMTP id 42PjDF40hgzDq7s; Tue,  2 Oct 2018 17:06:53 +0200 (CEST)
Received: from [10.193.4.89] (10.168.234.2) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 2 Oct 2018 17:06:53 +0200
Subject: Re: Spin bit decision
To: Lars Eggert <lars@eggert.org>
CC: IETF QUIC WG <quic@ietf.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org>
From: <alexandre.ferrieux@orange.com>
Message-ID: <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com>
Date: Tue, 2 Oct 2018 17:05:12 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <E7479831-9594-444E-9545-A162E8D9B154@eggert.org>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.168.234.2]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/L18zcPZfnmpxJcK52ftzgn1owcE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 15:06:57 -0000

On 10/02/18 16:00, Lars Eggert wrote:
> 
> The point I can't seem to be getting across is that irrespective of what the
> WG decides to require, there is no penalty for individual stacks at
> deployment time (or after) to do whatever they wish, since the spin bit by
> design has no impact on protocol operation and interop.

It is getting across, but it is a very grim view of the standardization process 
itself. Are there many examples of MUST in RFCs that turned out to be ignored by 
implementations just because they were not part of the core semantics and hence 
not enforced by other peers ?


_________________________________________________________________________________________________________________________

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.


From nobody Tue Oct  2 08:13:30 2018
Return-Path: <Lucas.Pardue@bbc.co.uk>
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 93009130E9F for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 08:13:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 8Q2VXaHSdmLb for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 08:13:28 -0700 (PDT)
Received: from mailout1.telhc.bbc.co.uk (mailout1.telhc.bbc.co.uk [132.185.161.180]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9CEC130E8F for <quic@ietf.org>; Tue,  2 Oct 2018 08:13:27 -0700 (PDT)
Received: from BGB01XI1011.national.core.bbc.co.uk (bgb01xi1011.national.core.bbc.co.uk [10.161.14.15]) by mailout1.telhc.bbc.co.uk (8.15.2/8.15.2) with ESMTP id w92FDPIP021624; Tue, 2 Oct 2018 16:13:25 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1011.national.core.bbc.co.uk ([10.161.14.15]) with mapi id 14.03.0408.000; Tue, 2 Oct 2018 16:13:25 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, "Lars Eggert" <lars@eggert.org>
CC: IETF QUIC WG <quic@ietf.org>
Subject: RE: Spin bit decision
Thread-Topic: Spin bit decision
Thread-Index: AQHUWhYuY5uphqKTlk+gydAimQZJXKULc8WAgAAbJICAACozgIAAHI2AgAAD5ACAAAMhAIAADuGAgAASIwCAABHx0A==
Date: Tue, 2 Oct 2018 15:13:25 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BBAFFCB@bgb01xud1012>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com>
In-Reply-To: <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.19.161.211]
x-exclaimer-md-config: 1cd3ac1c-62e5-43f2-8404-6b688271c769
x-tm-as-product-ver: SMEX-12.5.0.1300-8.2.1013-24054.007
x-tm-as-result: No-11.450700-8.000000-10
x-tmase-matchedrid: L8tZF6zWW2q7lpQUW6Uvz7iMC5wdwKqdwZLXS0hN8p0NcckEPxfz2MWl hj9iHeVpxqHJpNCgnQ7WgZRcXldbCXxpK/HViL+DFqNNeSB7ZZCC7C2rJeUToWuFHUq0bxxndhe NPERaTABSFLa4rvhU1DhKz81n5lYsNLRiJDKMJurCtSG/SQAC8ftEoNSP/uXBzBJjCfi4lf3CDc jF5OS/iOgwILxPYcqWqLRLXOmgYJSf1aLEK0xXO7MjW/sniEQKz+tKvxV+YbBRvLywkYw9qaPFj JEFr+olKE0Je8DR/D6No+PRbWqfRGTjfUfrkn0A
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
x-tmase-result: 10--11.450700-8.000000
x-tmase-version: SMEX-12.5.0.1300-8.2.1013-24054.007
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/GK8cqeFEYfS9ClxgdcBROdCJz7s>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 15:13:29 -0000

QWxleGFuZHJlIEZlcnJpZXV4IHdyb3RlOg0KPk9uIDEwLzAyLzE4IDE2OjAwLCBMYXJzIEVnZ2Vy
dCB3cm90ZToNCj4+DQo+PiBUaGUgcG9pbnQgSSBjYW4ndCBzZWVtIHRvIGJlIGdldHRpbmcgYWNy
b3NzIGlzIHRoYXQgaXJyZXNwZWN0aXZlIG9mDQo+PiB3aGF0IHRoZSBXRyBkZWNpZGVzIHRvIHJl
cXVpcmUsIHRoZXJlIGlzIG5vIHBlbmFsdHkgZm9yIGluZGl2aWR1YWwNCj4+IHN0YWNrcyBhdCBk
ZXBsb3ltZW50IHRpbWUgKG9yIGFmdGVyKSB0byBkbyB3aGF0ZXZlciB0aGV5IHdpc2gsIHNpbmNl
DQo+PiB0aGUgc3BpbiBiaXQgYnkgZGVzaWduIGhhcyBubyBpbXBhY3Qgb24gcHJvdG9jb2wgb3Bl
cmF0aW9uIGFuZCBpbnRlcm9wLg0KPg0KPkl0IGlzIGdldHRpbmcgYWNyb3NzLCBidXQgaXQgaXMg
YSB2ZXJ5IGdyaW0gdmlldyBvZiB0aGUgc3RhbmRhcmRpemF0aW9uIHByb2Nlc3MNCj5pdHNlbGYu
IEFyZSB0aGVyZSBtYW55IGV4YW1wbGVzIG9mIE1VU1QgaW4gUkZDcyB0aGF0IHR1cm5lZCBvdXQg
dG8gYmUNCj5pZ25vcmVkIGJ5IGltcGxlbWVudGF0aW9ucyBqdXN0IGJlY2F1c2UgdGhleSB3ZXJl
IG5vdCBwYXJ0IG9mIHRoZSBjb3JlDQo+c2VtYW50aWNzIGFuZCBoZW5jZSBub3QgZW5mb3JjZWQg
Ynkgb3RoZXIgcGVlcnMgPw0KPg0KDQpPbmUgZXhhbXBsZSBpcyBwcm92aWRlZCBpbiBSRkMgNjkx
OSBTZWN0aW9uIDEgWzFdLg0KDQpbMV0gaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzY5
MTkjc2VjdGlvbi0xDQoNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCmh0dHA6Ly93
d3cuYmJjLmNvLnVrDQpUaGlzIGUtbWFpbCAoYW5kIGFueSBhdHRhY2htZW50cykgaXMgY29uZmlk
ZW50aWFsIGFuZA0KbWF5IGNvbnRhaW4gcGVyc29uYWwgdmlld3Mgd2hpY2ggYXJlIG5vdCB0aGUg
dmlld3Mgb2YgdGhlIEJCQyB1bmxlc3Mgc3BlY2lmaWNhbGx5IHN0YXRlZC4NCklmIHlvdSBoYXZl
IHJlY2VpdmVkIGl0IGluDQplcnJvciwgcGxlYXNlIGRlbGV0ZSBpdCBmcm9tIHlvdXIgc3lzdGVt
Lg0KRG8gbm90IHVzZSwgY29weSBvciBkaXNjbG9zZSB0aGUNCmluZm9ybWF0aW9uIGluIGFueSB3
YXkgbm9yIGFjdCBpbiByZWxpYW5jZSBvbiBpdCBhbmQgbm90aWZ5IHRoZSBzZW5kZXINCmltbWVk
aWF0ZWx5Lg0KUGxlYXNlIG5vdGUgdGhhdCB0aGUgQkJDIG1vbml0b3JzIGUtbWFpbHMNCnNlbnQg
b3IgcmVjZWl2ZWQuDQpGdXJ0aGVyIGNvbW11bmljYXRpb24gd2lsbCBzaWduaWZ5IHlvdXIgY29u
c2VudCB0bw0KdGhpcy4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo=


From nobody Tue Oct  2 08:24:34 2018
Return-Path: <bkaduk@akamai.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 517F41310DA for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 08:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 43DKMNfXv0YL for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 08:24:19 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 8A38C130FCD for <quic@ietf.org>; Tue,  2 Oct 2018 08:24:14 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.22/8.16.0.22) with SMTP id w92FM4ii019561; Tue, 2 Oct 2018 16:24:06 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : in-reply-to; s=jan2016.eng; bh=ae7l5/e926Qy2kkDdDT8W8RWt29qjTLIq3U0I7gSBrY=; b=Py4iJaNbbTw4v9cIXv1PdaSxXu3tzWzDadYXstyF/VPs3h+wk0Pc1Cbz19z3uy8P4bBj DGwEBM2SKKBYdYbM7rEU5oWrAVIvIXzWNUMGoanQnOPpymRR353OoqTiwwghh3UFrQUO A+3i/PwUmWu4L+cBh6QLHaMwVzl/QA4G4mkYPrBUOsgjGMseyontTBfmhwP67cJraMU7 k0mBF+Fb761w2FT+ChFHnuGns7Lnwwsea8mOezBc14KxCEjbpM377KIt/Z2b3i86MEvZ g8i4X0rcBgCAoFgomVPZMsnOAHL6Y6PoNP+9KvU9bRFnbF7Z2i+26PKn/eV+qXNRlLMm mw== 
Received: from prod-mail-ppoint3 (a96-6-114-86.deploy.static.akamaitechnologies.com [96.6.114.86] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 2msxfday21-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 02 Oct 2018 16:24:06 +0100
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w92FKClR027998; Tue, 2 Oct 2018 11:24:05 -0400
Received: from prod-mail-relay14.akamai.com ([172.27.17.39]) by prod-mail-ppoint3.akamai.com with ESMTP id 2mt4rcvwu2-1; Tue, 02 Oct 2018 11:24:05 -0400
Received: from bos-lpczi.kendall.corp.akamai.com (bos-lpczi.kendall.corp.akamai.com [172.19.17.86]) by prod-mail-relay14.akamai.com (Postfix) with ESMTP id 1E83781760; Tue,  2 Oct 2018 15:24:05 +0000 (GMT)
Received: from bkaduk by bos-lpczi.kendall.corp.akamai.com with local (Exim 4.86_2) (envelope-from <bkaduk@akamai.com>) id 1g7MWq-0007JP-9x; Tue, 02 Oct 2018 10:24:04 -0500
Date: Tue, 2 Oct 2018 10:24:04 -0500
From: Benjamin Kaduk <bkaduk@akamai.com>
To: alexandre.ferrieux@orange.com
Cc: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
Subject: Re: Spin bit decision
Message-ID: <20181002152404.GP19845@akamai.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-02_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=695 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810020148
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-02_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=787 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810020149
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YJCnDadtGH9qn6U2zmaLHSJe2M4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 15:24:30 -0000

On Tue, Oct 02, 2018 at 05:05:12PM +0200, alexandre.ferrieux@orange.com wrote:
> On 10/02/18 16:00, Lars Eggert wrote:
> >
> >The point I can't seem to be getting across is that irrespective of what the
> >WG decides to require, there is no penalty for individual stacks at
> >deployment time (or after) to do whatever they wish, since the spin bit by
> >design has no impact on protocol operation and interop.
> 
> It is getting across, but it is a very grim view of the standardization
> process itself. Are there many examples of MUST in RFCs that turned out to
> be ignored by implementations just because they were not part of the core
> semantics and hence not enforced by other peers ?

I guess that this bit of https://tools.ietf.org/html/rfc4120 qualifies:

   Implementations of Kerberos and protocols based on Kerberos MUST NOT
   use insecure DNS queries to canonicalize the hostname components of
   the service principal names (i.e., they MUST NOT use insecure DNS
   queries to map one name to another to determine the host part of the
   principal name with which one is to communicate).

It's a local matter that the remote peer can't enforce, and "everybody"
is doing it, still.

-Ben


From nobody Tue Oct  2 09:42:04 2018
Return-Path: <lars@eggert.org>
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 C82A7130E52 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 09:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 mtM4FL2vMJ2Q for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 09:42:01 -0700 (PDT)
Received: from emh03.mail.saunalahti.fi (emh03.mail.saunalahti.fi [62.142.5.109]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0495B130DC8 for <quic@ietf.org>; Tue,  2 Oct 2018 09:42:01 -0700 (PDT)
Received: from eggert.org (unknown [62.248.255.56]) by emh03.mail.saunalahti.fi (Postfix) with ESMTP id 712BD40158; Tue,  2 Oct 2018 19:41:59 +0300 (EEST)
Received: from slate.eggert.org (pf.eggert.org [172.16.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by eggert.org (Postfix) with ESMTPSA id 2BE7761C5EA; Tue,  2 Oct 2018 19:41:55 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: Re: Spin bit decision
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <BB87D8D0-DA01-4C0F-B557-2A728BF19A64@trammell.ch>
Date: Tue, 2 Oct 2018 19:41:54 +0300
Cc: Marcus Ihlar <marcus.ihlar@ericsson.com>, "quic@ietf.org" <quic@ietf.org>,  "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C9FE8E50-0214-41E0-B0FF-52EA4DF2B0DF@eggert.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <HE1PR0701MB2393CDB16819A54B33D22417E2E80@HE1PR0701MB2393.eurprd07.prod.outlook.com> <BB87D8D0-DA01-4C0F-B557-2A728BF19A64@trammell.ch>
To: Brian Trammell <ietf@trammell.ch>
X-Mailer: Apple Mail (2.3445.100.39)
X-MailScanner-ID: 2BE7761C5EA.A5C59
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-1djTfmpiGacc0VOIc95Sv4-nLA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 16:42:03 -0000

Hi,

On 2018-10-2, at 17:45, Brian Trammell (IETF) <ietf@trammell.ch> wrote:
>=20
> IMO (and this is an opinion; I don't think anyone will have enough =
data to answer this question for real before Bangkok), as you say one =
"hyperscalar" turning the spin bit on -- even probabalistically, e.g. as =
Apple did (still does?) during transition to ECN-by-default on the =
client side -- would provide more than enough signal on the paths =
between the access networks of its users (most of them) and the =
network(s) through which it provides its services.
>=20
> This would also be the case if one of the top-N CDNs and one major =
browser vendor did so (again, probabilistic activation suffices). The =
larger the set of the server networks implementing, the more coverage =
one would have for access and core network paths.

thanks, this is helpful!

Lars=


From nobody Tue Oct  2 09:51:14 2018
Return-Path: <mbishop@evequefou.be>
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 98B45130E35 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 09:51:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 wxtP5Bv0_BTX for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 09:51:09 -0700 (PDT)
Received: from NAM05-CO1-obe.outbound.protection.outlook.com (mail-eopbgr720094.outbound.protection.outlook.com [40.107.72.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A63C130DD8 for <quic@ietf.org>; Tue,  2 Oct 2018 09:50:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=k/ZeA0q6iqxCACk9UWRjWOsNlxjPJ8qTZgevfNwAeYQ=; b=dzqYNDRbX6ZobJJmBh3FszO/6qLDJ73nly0SdDKW1GLC/wabEyAtriXeQKdVTHNmzz7ME+hTFZmSGKFn0cBQJ+PrxtuM76Iw/IE2cEyR9NZj9cdh2rQg5LmMvExPk2PRSohy7GdEJX8w96+Qgb8H9HmNS9E8KesaS+PBYbmLzBQ=
Received: from MWHPR22MB0991.namprd22.prod.outlook.com (10.171.145.21) by MWHPR22MB0957.namprd22.prod.outlook.com (10.171.145.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1185.22; Tue, 2 Oct 2018 16:50:32 +0000
Received: from MWHPR22MB0991.namprd22.prod.outlook.com ([fe80::582e:a300:785c:8592]) by MWHPR22MB0991.namprd22.prod.outlook.com ([fe80::582e:a300:785c:8592%9]) with mapi id 15.20.1185.024; Tue, 2 Oct 2018 16:50:32 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, Lars Eggert <lars@eggert.org>
CC: IETF QUIC WG <quic@ietf.org>
Subject: RE: Spin bit decision
Thread-Topic: Spin bit decision
Thread-Index: AQHUWhYukd5OdbmHyk+wNZHVyKYYO6ULhImAgAAbI4CAACozgIAAHI6AgAAD4wCAAAMhAIAADuGAgAASIwCAABt7EA==
Date: Tue, 2 Oct 2018 16:50:32 +0000
Message-ID: <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com>
In-Reply-To: <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [38.134.241.6]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR22MB0957; 6:1Bc4/Rxn7rc9MeXVX+ACiU9ax5eqnm6ZLhDtcIH3JF684Y3XkyyiTCp9VppMTwgAaPaRIacxBh0BUNj9DpWNdHD20T6J8Jfpox9HMVKeY6j2LgXEHRV3deNeu3v3cGBmYKrYljnN9UmzvPH49QXkMIbdj5iNiYA8qBHR27KgszpO8AP4pjAaq83q6J++dDyeSYcD3Qz+gxFJ5Qw84rmKGWWFgPau0gDpwQHD/ivhKAK2Y5RRMdrWNuMnoa00p8/VYXhCkZ4xuebRyRyVSeSj+EByN9jF+zv6USKhhUxGgOFoD0njLudARz7Ugq2A5sdLpAKaqJtQr7hd+qh3xGY1YG6NUsokef+XPJb+wVEbHHOiRAfO7GQF11guKEe4jIes203wdfNq4OVuAgZksHqa+FZXZMJJLL96ZmEYshN2IHUDev301VEU3eR1EOlMBWx2JWwdH63U/yVotTzSoj509A==; 5:WQnl3C3HK14DXul1ji+jiP6SqQU/pBWR5xtA4YkZjQepJ03zjkV3cdiXg0NuNL7iPhgieaE+Nbj31a3ZGTPp3Ts6y3uFJY1arSZUgeFydY4uz9hAhqCUKUnfgQIvp/CunRHB7GtkBlIX7S4/V22mAoq7DxHmqWSqTVPazqHM++Q=; 7:ED3xehABuwst3PHAb05hpibSC+ni3TPQ5/a3AWgD0St0wNBUyx6JQkrg/C0A80F7jbouQVLbFt9bP6QJv7Q6WY2Vypd+oEKrSfuRJFGYn/O+KIg2Z+KEdOQqxrnj3pArTpDNJOQZtpj0Nikp/cKhxuGz9iUswa9+JfiC5AX0TyzY8fkQhy7z1oJA/efL/j3gCUoct0OSGqTNyjPprTLevj3jE+/GevdyYCTtB+ZYazHAdBny1rYmxijdpZW1xIXM
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 59233285-e3ca-4485-e291-08d628872b18
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(7021145)(8989299)(4534165)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:MWHPR22MB0957; 
x-ms-traffictypediagnostic: MWHPR22MB0957:
x-microsoft-antispam-prvs: <MWHPR22MB0957DCEEB9199CE79920C17BDAE80@MWHPR22MB0957.namprd22.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(18271650672692)(161740460382875)(21748063052155)(28532068793085)(190501279198761)(227612066756510);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(10201501046)(93006095)(93001095)(3231355)(944501410)(52105095)(3002001)(149066)(150057)(6041310)(20161123562045)(20161123558120)(20161123560045)(2016111802025)(20161123564045)(6043046)(201708071742011)(7699051); SRVR:MWHPR22MB0957; BCL:0; PCL:0; RULEID:; SRVR:MWHPR22MB0957; 
x-forefront-prvs: 0813C68E65
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(396003)(39830400003)(366004)(346002)(376002)(13464003)(189003)(199004)(5660300001)(102836004)(6506007)(53936002)(53546011)(105586002)(106356001)(7116003)(74316002)(71190400001)(2900100001)(4326008)(7736002)(97736004)(26005)(66066001)(25786009)(486006)(2501003)(476003)(11346002)(5250100002)(446003)(71200400001)(508600001)(81166006)(74482002)(316002)(790700001)(33656002)(68736007)(6116002)(256004)(8936002)(8676002)(93886005)(14444005)(5024004)(81156014)(186003)(3846002)(99286004)(2906002)(3480700004)(110136005)(14454004)(229853002)(6436002)(86362001)(55016002)(9686003)(54896002)(76176011)(6246003)(7696005)(6306002); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR22MB0957; H:MWHPR22MB0991.namprd22.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: YjXRczzanj6nl90NII3GirMghDWyYvERajs4SVC+p4YBAvUwMSzlTCfuBmesGGPbANOnTi45QIFhCRJaxYHPkslojfnfeCSDxNvxutB1X7RVRLMfCgu0FApe5fq4wQE0neCVA8Z/V1D4ll3MIqDDfruscc3xQYEVSrvNEK99n8iKUIKZzHAZCz90EOCZt8xeNh296BRr+plnu4PfUUZuOaf38Oc7gDLbVBSSd3mHCXNHkoOOfmT4HGYJJeSwmKEbsLAQcwYgx+RDQzYMdNFLEkdswhQzMoRQtwTO4Tn1VoYfu5OCUQE2MeNaGtX0Mf/aQzF5xl3w5/UzPZFAxbU5rUtML8dIROgP4U8Pg1sLz1U=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_MWHPR22MB0991D93D706031603B077BFCDAE80MWHPR22MB0991namp_"
MIME-Version: 1.0
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 59233285-e3ca-4485-e291-08d628872b18
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Oct 2018 16:50:32.3477 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR22MB0957
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/cARhsZn7YGUa285Nzmw_s5hfByg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 16:51:13 -0000

--_000_MWHPR22MB0991D93D706031603B077BFCDAE80MWHPR22MB0991namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SSBkb27igJl0IHRoaW5rIGl04oCZcyBhIGdyaW0gdmlldywgSSB0aGluayBpdOKAmXMgYSBwcmFn
bWF0aWMgdmlldy4gIE91ciByb2xlIGlzIHRvIHNwZWNpZnkgdGhlIHRoaW5ncyB3aGljaCBhcmUg
ZnVuZGFtZW50YWwgdG8gdGhlIHByb3RvY29sIGFuZCBoYXZlIHRvIGhhcHBlbiBmb3IgcGVlcnMg
dG8gaW50ZXJvcGVyYXRlLiAgTWlzLXVzaW5nIG5vcm1hdGl2ZSBsYW5ndWFnZSBmb3Igb3RoZXIg
dGhpbmdzIGlzIGFuIGFidXNlIG9mIHRoZSBwcm9jZXNzIC0tIHRoYXQncyBraW5kIG9mIHRoZSBw
b2ludCBvZiBSRkMgNjkxOS4NCg0KDQoNClJGQyAyMTE5IHNheXM6DQpJbiBwYXJ0aWN1bGFyLCBb
bm9ybWF0aXZlIGxhbmd1YWdlXSBNVVNUIG9ubHkgYmUgdXNlZCB3aGVyZSBpdCBpcyBhY3R1YWxs
eSByZXF1aXJlZCBmb3IgaW50ZXJvcGVyYXRpb24gb3IgdG8gbGltaXQgYmVoYXZpb3Igd2hpY2gg
aGFzIHBvdGVudGlhbCBmb3IgY2F1c2luZyBoYXJtIChlLmcuLCBsaW1pdGluZyByZXRyYW5zbWlz
c3Npb25zKSAgRm9yIGV4YW1wbGUsIHRoZXkgbXVzdCBub3QgYmUgdXNlZCB0byB0cnkgdG8gaW1w
b3NlIGEgcGFydGljdWxhciBtZXRob2Qgb24gaW1wbGVtZW50b3JzIHdoZXJlIHRoZSBtZXRob2Qg
aXMgbm90IHJlcXVpcmVkIGZvciBpbnRlcm9wZXJhYmlsaXR5Lg0KDQoNCg0KR2l2ZW4gdGhhdCB0
aGUgc3BpbiBiaXQgaXMgbm90IOKAnGFjdHVhbGx5IHJlcXVpcmVkIGZvciBpbnRlcm9wZXJhdGlv
bizigJ0gYnV0IGlzIHRoZSB2ZXJ5IGRlZmluaXRpb24gb2Yg4oCcdHJ5IHRvIGltcG9zZSBhIHBh
cnRpY3VsYXIgbWV0aG9kIG9uIGltcGxlbWVudG9ycyzigJ0gSeKAmWQgc2F5IHRoYXQgUkZDIDIx
MTkgaW1wZXJhdGl2ZXMgYXJlIHVud2FycmFudGVkLg0KDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCkZyb206IFFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxmIE9m
IGFsZXhhbmRyZS5mZXJyaWV1eEBvcmFuZ2UuY29tDQpTZW50OiBUdWVzZGF5LCBPY3RvYmVyIDIs
IDIwMTggODowNSBBTQ0KVG86IExhcnMgRWdnZXJ0IDxsYXJzQGVnZ2VydC5vcmc+DQpDYzogSUVU
RiBRVUlDIFdHIDxxdWljQGlldGYub3JnPg0KU3ViamVjdDogUmU6IFNwaW4gYml0IGRlY2lzaW9u
DQoNCg0KDQpPbiAxMC8wMi8xOCAxNjowMCwgTGFycyBFZ2dlcnQgd3JvdGU6DQoNCj4NCg0KPiBU
aGUgcG9pbnQgSSBjYW4ndCBzZWVtIHRvIGJlIGdldHRpbmcgYWNyb3NzIGlzIHRoYXQgaXJyZXNw
ZWN0aXZlIG9mDQoNCj4gd2hhdCB0aGUgV0cgZGVjaWRlcyB0byByZXF1aXJlLCB0aGVyZSBpcyBu
byBwZW5hbHR5IGZvciBpbmRpdmlkdWFsDQoNCj4gc3RhY2tzIGF0IGRlcGxveW1lbnQgdGltZSAo
b3IgYWZ0ZXIpIHRvIGRvIHdoYXRldmVyIHRoZXkgd2lzaCwgc2luY2UNCg0KPiB0aGUgc3BpbiBi
aXQgYnkgZGVzaWduIGhhcyBubyBpbXBhY3Qgb24gcHJvdG9jb2wgb3BlcmF0aW9uIGFuZCBpbnRl
cm9wLg0KDQoNCg0KSXQgaXMgZ2V0dGluZyBhY3Jvc3MsIGJ1dCBpdCBpcyBhIHZlcnkgZ3JpbSB2
aWV3IG9mIHRoZSBzdGFuZGFyZGl6YXRpb24gcHJvY2VzcyBpdHNlbGYuIEFyZSB0aGVyZSBtYW55
IGV4YW1wbGVzIG9mIE1VU1QgaW4gUkZDcyB0aGF0IHR1cm5lZCBvdXQgdG8gYmUgaWdub3JlZCBi
eSBpbXBsZW1lbnRhdGlvbnMganVzdCBiZWNhdXNlIHRoZXkgd2VyZSBub3QgcGFydCBvZiB0aGUg
Y29yZSBzZW1hbnRpY3MgYW5kIGhlbmNlIG5vdCBlbmZvcmNlZCBieSBvdGhlciBwZWVycyA/DQoN
Cg0KDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KDQoNCg0KQ2UgbWVzc2FnZSBldCBzZXMgcGllY2VzIGpvaW50ZXMg
cGV1dmVudCBjb250ZW5pciBkZXMgaW5mb3JtYXRpb25zIGNvbmZpZGVudGllbGxlcyBvdSBwcml2
aWxlZ2llZXMgZXQgbmUgZG9pdmVudCBkb25jIHBhcyBldHJlIGRpZmZ1c2VzLCBleHBsb2l0ZXMg
b3UgY29waWVzIHNhbnMgYXV0b3Jpc2F0aW9uLiBTaSB2b3VzIGF2ZXogcmVjdSBjZSBtZXNzYWdl
IHBhciBlcnJldXIsIHZldWlsbGV6IGxlIHNpZ25hbGVyIGEgbCdleHBlZGl0ZXVyIGV0IGxlIGRl
dHJ1aXJlIGFpbnNpIHF1ZSBsZXMgcGllY2VzIGpvaW50ZXMuIExlcyBtZXNzYWdlcyBlbGVjdHJv
bmlxdWVzIGV0YW50IHN1c2NlcHRpYmxlcyBkJ2FsdGVyYXRpb24sIE9yYW5nZSBkZWNsaW5lIHRv
dXRlIHJlc3BvbnNhYmlsaXRlIHNpIGNlIG1lc3NhZ2UgYSBldGUgYWx0ZXJlLCBkZWZvcm1lIG91
IGZhbHNpZmllLiBNZXJjaS4NCg0KDQoNClRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRz
IG1heSBjb250YWluIGNvbmZpZGVudGlhbCBvciBwcml2aWxlZ2VkIGluZm9ybWF0aW9uIHRoYXQg
bWF5IGJlIHByb3RlY3RlZCBieSBsYXc7IHRoZXkgc2hvdWxkIG5vdCBiZSBkaXN0cmlidXRlZCwg
dXNlZCBvciBjb3BpZWQgd2l0aG91dCBhdXRob3Jpc2F0aW9uLg0KDQpJZiB5b3UgaGF2ZSByZWNl
aXZlZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgYW5kIGRl
bGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cy4NCg0KQXMgZW1haWxzIG1heSBi
ZSBhbHRlcmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhhdCBoYXZlIGJl
ZW4gbW9kaWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVkLg0KDQpUaGFuayB5b3UuDQoNCg0K

--_000_MWHPR22MB0991D93D706031603B077BFCDAE80MWHPR22MB0991namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQph
OmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv
cjojMDU2M0MxOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjoj
OTU0RjcyOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29QbGFpblRleHQsIGxp
Lk1zb1BsYWluVGV4dCwgZGl2Lk1zb1BsYWluVGV4dA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJbXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJn
aW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2Fs
aWJyaSIsc2Fucy1zZXJpZjt9DQpwcmUNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1z
dHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdp
bi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3Vy
aWVyIE5ldyI7fQ0Kc3Bhbi5QbGFpblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJQbGFpbiBU
ZXh0IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUGxh
aW4gVGV4dCI7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5IVE1M
UHJlZm9ybWF0dGVkQ2hhcg0KCXttc28tc3R5bGUtbmFtZToiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hh
ciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZv
cm1hdHRlZCI7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQouTXNvQ2hwRGVmYXVsdA0K
CXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fu
cy1zZXJpZjt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFy
Z2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpX
b3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNo
YXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRp
Zl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0
Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0Pjwv
eG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYz
QzEiIHZsaW5rPSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij5JIGRvbuKAmXQgdGhpbmsgaXTigJlzIGEgZ3JpbSB2aWV3LCBJIHRo
aW5rIGl04oCZcyBhIHByYWdtYXRpYyB2aWV3LiZuYnNwOyBPdXIgcm9sZSBpcyB0byBzcGVjaWZ5
IHRoZSB0aGluZ3Mgd2hpY2ggYXJlIGZ1bmRhbWVudGFsIHRvIHRoZSBwcm90b2NvbCBhbmQgaGF2
ZSB0byBoYXBwZW4gZm9yIHBlZXJzIHRvIGludGVyb3BlcmF0ZS4mbmJzcDsgTWlzLXVzaW5nIG5v
cm1hdGl2ZSBsYW5ndWFnZSBmb3Igb3RoZXIgdGhpbmdzIGlzIGFuDQogYWJ1c2Ugb2YgdGhlIHBy
b2Nlc3MgLS0gdGhhdCdzIGtpbmQgb2YgdGhlIHBvaW50IG9mIFJGQyA2OTE5LjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij5SRkMgMjExOSBzYXlzOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJs
YWNrIj5JbiBwYXJ0aWN1bGFyLCBbbm9ybWF0aXZlIGxhbmd1YWdlXSBNVVNUIG9ubHkgYmUgdXNl
ZCB3aGVyZSBpdCBpcyBhY3R1YWxseSByZXF1aXJlZCBmb3IgaW50ZXJvcGVyYXRpb24gb3IgdG8g
bGltaXQgYmVoYXZpb3Igd2hpY2ggaGFzIHBvdGVudGlhbA0KIGZvciBjYXVzaW5nIGhhcm0gKGUu
Zy4sIGxpbWl0aW5nIHJldHJhbnNtaXNzc2lvbnMpJm5ic3A7IEZvciBleGFtcGxlLCB0aGV5IG11
c3Qgbm90IGJlIHVzZWQgdG8gdHJ5IHRvIGltcG9zZSBhIHBhcnRpY3VsYXIgbWV0aG9kIG9uIGlt
cGxlbWVudG9ycyB3aGVyZSB0aGUgbWV0aG9kIGlzIG5vdCByZXF1aXJlZCBmb3IgaW50ZXJvcGVy
YWJpbGl0eS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkdpdmVuIHRoYXQg
dGhlIHNwaW4gYml0IGlzIG5vdCDigJxhY3R1YWxseSByZXF1aXJlZCBmb3IgaW50ZXJvcGVyYXRp
b24s4oCdIGJ1dCBpcyB0aGUgdmVyeSBkZWZpbml0aW9uIG9mIOKAnHRyeSB0byBpbXBvc2UgYSBw
YXJ0aWN1bGFyIG1ldGhvZCBvbiBpbXBsZW1lbnRvcnMs4oCdIEnigJlkIHNheSB0aGF0IFJGQyAy
MTE5IGltcGVyYXRpdmVzIGFyZSB1bndhcnJhbnRlZC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08YnI+DQpGcm9tOiBRVUlDICZsdDtxdWlj
LWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7IE9uIEJlaGFsZiBPZiBhbGV4YW5kcmUuZmVycmlldXhAb3Jh
bmdlLmNvbTxicj4NClNlbnQ6IFR1ZXNkYXksIE9jdG9iZXIgMiwgMjAxOCA4OjA1IEFNPGJyPg0K
VG86IExhcnMgRWdnZXJ0ICZsdDtsYXJzQGVnZ2VydC5vcmcmZ3Q7PGJyPg0KQ2M6IElFVEYgUVVJ
QyBXRyAmbHQ7cXVpY0BpZXRmLm9yZyZndDs8YnI+DQpTdWJqZWN0OiBSZTogU3BpbiBiaXQgZGVj
aXNpb248L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPk9uIDEwLzAyLzE4IDE2OjAwLCBMYXJzIEVnZ2VydCB3
cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgPG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IFRoZSBwb2ludCBJIGNhbid0
IHNlZW0gdG8gYmUgZ2V0dGluZyBhY3Jvc3MgaXMgdGhhdCBpcnJlc3BlY3RpdmUgb2YNCjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jmd0OyB3aGF0IHRoZSBXRyBkZWNp
ZGVzIHRvIHJlcXVpcmUsIHRoZXJlIGlzIG5vIHBlbmFsdHkgZm9yIGluZGl2aWR1YWwNCjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jmd0OyBzdGFja3MgYXQgZGVwbG95
bWVudCB0aW1lIChvciBhZnRlcikgdG8gZG8gd2hhdGV2ZXIgdGhleSB3aXNoLCBzaW5jZQ0KPG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IHRoZSBzcGluIGJpdCBi
eSBkZXNpZ24gaGFzIG5vIGltcGFjdCBvbiBwcm90b2NvbCBvcGVyYXRpb24gYW5kIGludGVyb3Au
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkl0IGlzIGdldHRpbmcgYWNyb3NzLCBidXQg
aXQgaXMgYSB2ZXJ5IGdyaW0gdmlldyBvZiB0aGUgc3RhbmRhcmRpemF0aW9uIHByb2Nlc3MgaXRz
ZWxmLiBBcmUgdGhlcmUgbWFueSBleGFtcGxlcyBvZiBNVVNUIGluIFJGQ3MgdGhhdCB0dXJuZWQg
b3V0IHRvIGJlIGlnbm9yZWQgYnkgaW1wbGVtZW50YXRpb25zIGp1c3QgYmVjYXVzZSB0aGV5IHdl
cmUgbm90IHBhcnQgb2YgdGhlIGNvcmUgc2VtYW50aWNzIGFuZA0KIGhlbmNlIG5vdCBlbmZvcmNl
ZCBieSBvdGhlciBwZWVycyA/PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+X19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij5DZSBtZXNzYWdlIGV0IHNlcyBwaWVjZXMgam9pbnRlcyBwZXV2
ZW50IGNvbnRlbmlyIGRlcyBpbmZvcm1hdGlvbnMgY29uZmlkZW50aWVsbGVzIG91IHByaXZpbGVn
aWVlcyBldCBuZSBkb2l2ZW50IGRvbmMgcGFzIGV0cmUgZGlmZnVzZXMsIGV4cGxvaXRlcyBvdSBj
b3BpZXMgc2FucyBhdXRvcmlzYXRpb24uIFNpIHZvdXMgYXZleiByZWN1IGNlIG1lc3NhZ2UgcGFy
IGVycmV1ciwgdmV1aWxsZXogbGUgc2lnbmFsZXINCiBhIGwnZXhwZWRpdGV1ciBldCBsZSBkZXRy
dWlyZSBhaW5zaSBxdWUgbGVzIHBpZWNlcyBqb2ludGVzLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25p
cXVlcyBldGFudCBzdXNjZXB0aWJsZXMgZCdhbHRlcmF0aW9uLCBPcmFuZ2UgZGVjbGluZSB0b3V0
ZSByZXNwb25zYWJpbGl0ZSBzaSBjZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBm
YWxzaWZpZS4gTWVyY2kuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPlRoaXMgbWVzc2Fn
ZSBhbmQgaXRzIGF0dGFjaG1lbnRzIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBvciBwcml2aWxl
Z2VkIGluZm9ybWF0aW9uIHRoYXQgbWF5IGJlIHByb3RlY3RlZCBieSBsYXc7IHRoZXkgc2hvdWxk
IG5vdCBiZSBkaXN0cmlidXRlZCwgdXNlZCBvciBjb3BpZWQgd2l0aG91dCBhdXRob3Jpc2F0aW9u
LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+SWYgeW91IGhhdmUgcmVj
ZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGFuZCBk
ZWxldGUgdGhpcyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVudHMuPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5BcyBlbWFpbHMgbWF5IGJlIGFsdGVyZWQsIE9yYW5nZSBp
cyBub3QgbGlhYmxlIGZvciBtZXNzYWdlcyB0aGF0IGhhdmUgYmVlbiBtb2RpZmllZCwgY2hhbmdl
ZCBvciBmYWxzaWZpZWQuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5U
aGFuayB5b3UuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_MWHPR22MB0991D93D706031603B077BFCDAE80MWHPR22MB0991namp_--


From nobody Tue Oct  2 10:11:31 2018
Return-Path: <ted.ietf@gmail.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 CE9B0131356 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 10:11:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-0.001] 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 n1I6hjlejXlX for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 10:11:26 -0700 (PDT)
Received: from mail-ot1-x331.google.com (mail-ot1-x331.google.com [IPv6:2607:f8b0:4864:20::331]) (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 3E1AF1311B9 for <quic@ietf.org>; Tue,  2 Oct 2018 10:06:53 -0700 (PDT)
Received: by mail-ot1-x331.google.com with SMTP id h26-v6so2626244otl.9 for <quic@ietf.org>; Tue, 02 Oct 2018 10:06:53 -0700 (PDT)
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=ShnDr+OI5dJ7M0BuRlyJ3IoIMQlLdhG4AyWK3hObgdU=; b=e7hXXN8XRb/fkehZjJHHD3Y73Gx2qLtpwD3V4mtraYEsZLr+Laane7kMg+jheZx9/D MdgxlxCy84Xo0gTByw/SrDQAkpDWJzwM4ReUHM3MGp9lxBxbmadyJ2X+K7X/ez/JJ87K nnk7SL2FH/9ozG3fq3zJPPoD2Y4teYqjIjewG8aORzt8N4ZwwW3V3RaT4oju0ftYniTh mu9x5y3jkt2zpikNEXRBs4LpOU29uGZc2kHmqRm4KbUNE3xJBkeMguWTPLWvHp8osXFK w1RFxAQFP2FWbtwmrbny8I8YtWHPfSRo5q+u0OijzdOL9Uzkng4rmyX6aeH8u1Vn8cQV 9axA==
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=ShnDr+OI5dJ7M0BuRlyJ3IoIMQlLdhG4AyWK3hObgdU=; b=l8M6XoWZBg2KzrdNgoY+BLODdDLGPLd8WqZo9g78UTYZj8YUulf62YuVleNZ/gzleb q9rExsOjII86pNpgLK2v3n+9PiulAya61gNbsz7+RH5tQy+somlsWgylcfFNPdDmGsmt gpXdO6R59v63JuHkZRw1F/9gTO6/WDDtGJJPNPhRJ0xNxiUj1AaVDOBIfqN2fJ95khaO 5qMWi6AjAoDpGAM3M4I5vHQg2al7eWiNvSy7DdPMyE6jPuOo0RiNnma4cM/RQb0QC2C7 GQEBKUmTmwQyUOwQjR5Ndu7bZrWNwnTldQodnnIsAjQKO5Vph4uvKfxnyi6OgE9ILk7i lRHA==
X-Gm-Message-State: ABuFfoh5LDxRj88kMqHKtPLkabIpVvhIOI3bwWPJZ7EBLWSwjNR/DYuH zl9zxdaoY6BPVw6ibQ4QUf7dI6LxZWr4ArBS0a4=
X-Google-Smtp-Source: ACcGV633wEEn6gQOvQZ3YkfF110H5SWi3khM4zR3Ls/0aHia4h0Fl937uKItrjHQ/ucg4TtZIWvtcYKqX3K1zn6xLK0=
X-Received: by 2002:a9d:9a1:: with SMTP id q30-v6mr9668248otd.351.1538500012287;  Tue, 02 Oct 2018 10:06:52 -0700 (PDT)
MIME-Version: 1.0
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com>
In-Reply-To: <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 2 Oct 2018 10:06:25 -0700
Message-ID: <CA+9kkMCRmgS_6ZgDnv3-+V8aUhh3-As2SG2ZR0MWTC48JWQ78A@mail.gmail.com>
Subject: Re: Spin bit decision
To: Mike Bishop <mbishop@evequefou.be>
Cc: alexandre.ferrieux@orange.com, Lars Eggert <lars@eggert.org>,  IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b82b3b057741f225"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/I6crDezYG_Wv1ET-2srbkrzB3pk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 17:11:29 -0000

--000000000000b82b3b057741f225
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 2, 2018 at 9:51 AM Mike Bishop <mbishop@evequefou.be> wrote:

> I don=E2=80=99t think it=E2=80=99s a grim view, I think it=E2=80=99s a pr=
agmatic view.  Our role
> is to specify the things which are fundamental to the protocol and have t=
o
> happen for peers to interoperate.  Mis-using normative language for other
> things is an abuse of the process -- that's kind of the point of RFC 6919=
.
>
>
>
> RFC 2119 says:
>
> In particular, [normative language] MUST only be used where it is actuall=
y
> required for interoperation or to limit behavior which has potential for
> causing harm (e.g., limiting retransmisssions)  For example, they must no=
t
> be used to try to impose a particular method on implementors where the
> method is not required for interoperability.
>
>
>
> Given that the spin bit is not =E2=80=9Cactually required for interoperat=
ion,=E2=80=9D but
> is the very definition of =E2=80=9Ctry to impose a particular method on
> implementors,=E2=80=9D I=E2=80=99d say that RFC 2119 imperatives are unwa=
rranted.
>

That's not quite what we generally mean by "interoperation" here.  It's
quite common to have something say, in effect, "If you use X, you MUST do
Y.".  So, we could have a MUST in Section 2.3 of the draft, instead of the
current language:

   Each client and server MUST reset its spin value to zero when sending th=
e
   first packet of a given connection with a new connection ID.  This
   reduces the risk that transient spin bit state can be used to link
   flows across connection migration or ID change.

That MUST doesn't say anything about when you use the spin bit, it simply
says that *if*  you use it, other implementations will expect this
behavior; if they get a new connection ID with a non-zero spin value, it
will be a protocol error.  That pattern of use is very common.

Ted

--000000000000b82b3b057741f225
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Oct 2, 2018 at 9:51 AM Mike Bishop &lt;<a href=3D"=
mailto:mbishop@evequefou.be">mbishop@evequefou.be</a>&gt; wrote:<br><div cl=
ass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div link=3D"#0563C1" vlink=3D"#954F72" lang=3D"EN-US">
<div class=3D"m_-9071695150965445483WordSection1">
<p class=3D"m_-9071695150965445483MsoPlainText">I don=E2=80=99t think it=E2=
=80=99s a grim view, I think it=E2=80=99s a pragmatic view.=C2=A0 Our role =
is to specify the things which are fundamental to the protocol and have to =
happen for peers to interoperate.=C2=A0 Mis-using normative language for ot=
her things is an
 abuse of the process -- that&#39;s kind of the point of RFC 6919.<u></u><u=
></u></p>
<p class=3D"m_-9071695150965445483MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_-9071695150965445483MsoPlainText">RFC 2119 says:<u></u><u></u=
></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt;font-family:&quot;Courier New&quot;;color:black">In particular, [nor=
mative language] MUST only be used where it is actually required for intero=
peration or to limit behavior which has potential
 for causing harm (e.g., limiting retransmisssions)=C2=A0 For example, they=
 must not be used to try to impose a particular method on implementors wher=
e the method is not required for interoperability.<u></u><u></u></span></p>
<p class=3D"m_-9071695150965445483MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_-9071695150965445483MsoPlainText">Given that the spin bit is =
not =E2=80=9Cactually required for interoperation,=E2=80=9D but is the very=
 definition of =E2=80=9Ctry to impose a particular method on implementors,=
=E2=80=9D I=E2=80=99d say that RFC 2119 imperatives are unwarranted.<u></u>=
<u></u></p>
</div></div></blockquote><div><br></div><div>That&#39;s not quite what we g=
enerally mean by &quot;interoperation&quot; here.=C2=A0 It&#39;s quite comm=
on to have something say, in effect, &quot;If you use X, you MUST do Y.&quo=
t;.=C2=A0 So, we could have a MUST in Section 2.3 of the draft, instead of =
the current language:<br></div><div><br></div><div><pre>   Each client and =
server MUST reset its spin value to zero when sending the
   first packet of a given connection with a new connection ID.  This
   reduces the risk that transient spin bit state can be used to link
   flows across connection migration or ID change.<br><br></pre>That MUST d=
oesn&#39;t say anything about when you use the spin bit, it simply says tha=
t *if*=C2=A0 you use it, other implementations will expect this behavior; i=
f they get a new connection ID with a non-zero spin value, it will be a pro=
tocol error.=C2=A0 That pattern of use is very common.</div><div><br></div>=
<div>Ted<br></div></div></div>

--000000000000b82b3b057741f225--


From nobody Tue Oct  2 10:17:20 2018
Return-Path: <ianswett@google.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 55D3413131A for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 10:17:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.5
X-Spam-Level: 
X-Spam-Status: No, score=-17.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 9ErYbAjtce4M for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 10:17:15 -0700 (PDT)
Received: from mail-yb1-xb32.google.com (mail-yb1-xb32.google.com [IPv6:2607:f8b0:4864:20::b32]) (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 DE5B5131210 for <quic@ietf.org>; Tue,  2 Oct 2018 10:13:56 -0700 (PDT)
Received: by mail-yb1-xb32.google.com with SMTP id w7-v6so1104290ybm.7 for <quic@ietf.org>; Tue, 02 Oct 2018 10:13:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DULqzf1ad0Os/5viCZUIBU1FIhM3+fxlJQGDTf3bVHg=; b=HpP9dlHdZUprP4zAM5xEhyxJroa88V4HGoPikioNGYLpOdg6t6oJRFBRVypFPt2BwD SLWrUK66DiFyr1zaqQp1PFWB5ADdrSTHPEnuHopM6NT3t4hoyBPoiHrSMHXR2g4iSMwY vE5MbG+bV8/vp++MnJtHpdFIxJaHPrqIAsRq3IlQWXyPty1+8esK8+r5hrI5VjXFBkai EvQUsig/VvqmWJwHXsZY3c/t3s7gf2OCNatjqaOpZY05o3mkAEmsK4v64VMdgd52CLKV IQ/YkbrT+olVBmUof1AjTcQTJcZmz6yc7f8wCfG62UnQjaa8TRFy3zNOGmb4e2Kv//n6 3/GA==
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=DULqzf1ad0Os/5viCZUIBU1FIhM3+fxlJQGDTf3bVHg=; b=XFGW8cAveFvUZUZzoKRH29vA9HjSMrPOKaLbUbrwp/bt2T0CRbsl5HYN/k4FZqm7wl TKiV4YVNk4l8lYQAByoYVnEvAat4XhxH02cKvarvcHHIDWLVzni2vAEZLTD8ZYt+IA9Z l5eTxYkOzTW9wu9ye2JypMDrdGud2+F7UUKb+FXMID/XmbWYbt1OfhcHzWEue9teKI7R TvdTBCCeNPsDHvj+3T800OJN5FXea/5NutF87HIcpHSa0bch1J5k5QqXSQdIVdBlXfub TI6Ex7e4zQ8+kKUqp2e/YL5/z+qAg/tVqf2WIfikXqQudc1ZzEPMvDHVau/1GQRCgiAU ReQA==
X-Gm-Message-State: ABuFfojBsKLeRWs2pAh7JGfz4DoRAZ8LGApoR2Zfn8op6K9d92Tl35qZ rPntr5M+wvdsy4+T4Nxo1/hfIJZgq5hiCMwdr6FJww==
X-Google-Smtp-Source: ACcGV6094XFUXewAj1s/0H/4kj2T7BMth3HshQQDBqqnEzGGXulpQQ/tRl0fx6gOkoiZ/IYqc8sqxIm/4CoFjrIqD6g=
X-Received: by 2002:a25:dccf:: with SMTP id y198-v6mr8919629ybe.389.1538500435876;  Tue, 02 Oct 2018 10:13:55 -0700 (PDT)
MIME-Version: 1.0
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com>
In-Reply-To: <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com>
From: Ian Swett <ianswett@google.com>
Date: Tue, 2 Oct 2018 13:13:43 -0400
Message-ID: <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com>
Subject: Re: Spin bit decision
To: Mike Bishop <mbishop@evequefou.be>
Cc: alexandre.ferrieux@orange.com, Lars Eggert <lars@eggert.org>,  IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f80eac0577420bdf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Lrfckq4BiSfIlY2L0cPPGzcUgGw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 17:17:19 -0000

--000000000000f80eac0577420bdf
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

One piece of information related to the above discussion is whether
detecting who is and is not spinning is easy and reliable.

One of my concerns is unintentional mis-use of the signal, and if it can't
be detected reliably in a mixed environment, that means SHOULD is unwise
and argues for either not including it or making it a MUST.

On Tue, Oct 2, 2018 at 12:51 PM Mike Bishop <mbishop@evequefou.be> wrote:

> I don=E2=80=99t think it=E2=80=99s a grim view, I think it=E2=80=99s a pr=
agmatic view.  Our role
> is to specify the things which are fundamental to the protocol and have t=
o
> happen for peers to interoperate.  Mis-using normative language for other
> things is an abuse of the process -- that's kind of the point of RFC 6919=
.
>
>
>
> RFC 2119 says:
>
> In particular, [normative language] MUST only be used where it is actuall=
y
> required for interoperation or to limit behavior which has potential for
> causing harm (e.g., limiting retransmisssions)  For example, they must no=
t
> be used to try to impose a particular method on implementors where the
> method is not required for interoperability.
>
>
>
> Given that the spin bit is not =E2=80=9Cactually required for interoperat=
ion,=E2=80=9D but
> is the very definition of =E2=80=9Ctry to impose a particular method on
> implementors,=E2=80=9D I=E2=80=99d say that RFC 2119 imperatives are unwa=
rranted.
>
>
>
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of
> alexandre.ferrieux@orange.com
> Sent: Tuesday, October 2, 2018 8:05 AM
> To: Lars Eggert <lars@eggert.org>
> Cc: IETF QUIC WG <quic@ietf.org>
> Subject: Re: Spin bit decision
>
>
>
> On 10/02/18 16:00, Lars Eggert wrote:
>
> >
>
> > The point I can't seem to be getting across is that irrespective of
>
> > what the WG decides to require, there is no penalty for individual
>
> > stacks at deployment time (or after) to do whatever they wish, since
>
> > the spin bit by design has no impact on protocol operation and interop.
>
>
>
> It is getting across, but it is a very grim view of the standardization
> process itself. Are there many examples of MUST in RFCs that turned out t=
o
> be ignored by implementations just because they were not part of the core
> semantics and hence not enforced by other peers ?
>
>
>
>
>
>
> _________________________________________________________________________=
________________________________________________
>
>
>
> 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'alteratio=
n,
> Orange decline toute responsabilite si ce message a ete altere, deforme o=
u
> 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 bee=
n
> modified, changed or falsified.
>
> Thank you.
>
>
>

--000000000000f80eac0577420bdf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">One piece of information related to the above discussion i=
s whether detecting who is and is not spinning is easy and reliable.<div><b=
r></div><div>One of my concerns is unintentional mis-use of the signal, and=
 if it can&#39;t be detected reliably in a mixed environment, that means SH=
OULD is unwise and argues for either not including it or making it a MUST.<=
/div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Oct 2, 2=
018 at 12:51 PM Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be">mbi=
shop@evequefou.be</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"m_-7784818331224156811WordSection1">
<p class=3D"m_-7784818331224156811MsoPlainText">I don=E2=80=99t think it=E2=
=80=99s a grim view, I think it=E2=80=99s a pragmatic view.=C2=A0 Our role =
is to specify the things which are fundamental to the protocol and have to =
happen for peers to interoperate.=C2=A0 Mis-using normative language for ot=
her things is an
 abuse of the process -- that&#39;s kind of the point of RFC 6919.<u></u><u=
></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText">RFC 2119 says:<u></u><u></u=
></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt;font-family:&quot;Courier New&quot;;color:black">In particular, [nor=
mative language] MUST only be used where it is actually required for intero=
peration or to limit behavior which has potential
 for causing harm (e.g., limiting retransmisssions)=C2=A0 For example, they=
 must not be used to try to impose a particular method on implementors wher=
e the method is not required for interoperability.<u></u><u></u></span></p>
<p class=3D"m_-7784818331224156811MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText">Given that the spin bit is =
not =E2=80=9Cactually required for interoperation,=E2=80=9D but is the very=
 definition of =E2=80=9Ctry to impose a particular method on implementors,=
=E2=80=9D I=E2=80=99d say that RFC 2119 imperatives are unwarranted.<u></u>=
<u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText">-----Original Message-----<=
br>
From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_blank">q=
uic-bounces@ietf.org</a>&gt; On Behalf Of <a href=3D"mailto:alexandre.ferri=
eux@orange.com" target=3D"_blank">alexandre.ferrieux@orange.com</a><br>
Sent: Tuesday, October 2, 2018 8:05 AM<br>
To: Lars Eggert &lt;<a href=3D"mailto:lars@eggert.org" target=3D"_blank">la=
rs@eggert.org</a>&gt;<br>
Cc: IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">qui=
c@ietf.org</a>&gt;<br>
Subject: Re: Spin bit decision</p>
<p class=3D"m_-7784818331224156811MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText">On 10/02/18 16:00, Lars Egg=
ert wrote:<u></u><u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText">&gt; <u></u><u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText">&gt; The point I can&#39;t =
seem to be getting across is that irrespective of
<u></u><u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText">&gt; what the WG decides to=
 require, there is no penalty for individual
<u></u><u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText">&gt; stacks at deployment t=
ime (or after) to do whatever they wish, since
<u></u><u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText">&gt; the spin bit by design=
 has no impact on protocol operation and interop.<u></u><u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText">It is getting across, but i=
t is a very grim view of the standardization process itself. Are there many=
 examples of MUST in RFCs that turned out to be ignored by implementations =
just because they were not part of the core semantics and
 hence not enforced by other peers ?<u></u><u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText">___________________________=
___________________________________________________________________________=
___________________<u></u><u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText">Ce message et ses pieces jo=
intes peuvent contenir des informations confidentielles ou privilegiees et =
ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. S=
i vous avez recu ce message par erreur, veuillez le signaler
 a l&#39;expediteur et le detruire ainsi que les pieces jointes. Les messag=
es electroniques etant susceptibles d&#39;alteration, Orange decline toute =
responsabilite si ce message a ete altere, deforme ou falsifie. Merci.<u></=
u><u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText">This message and its attach=
ments may contain confidential or privileged information that may be protec=
ted by law; they should not be distributed, used or copied without authoris=
ation.<u></u><u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText">If you have received this e=
mail in error, please notify the sender and delete this message and its att=
achments.<u></u><u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText">As emails may be altered, O=
range is not liable for messages that have been modified, changed or falsif=
ied.<u></u><u></u></p>
<p class=3D"m_-7784818331224156811MsoPlainText">Thank you.<u></u><u></u></p=
>
<p class=3D"m_-7784818331224156811MsoPlainText"><u></u>=C2=A0<u></u></p>
</div>
</div>

</blockquote></div>

--000000000000f80eac0577420bdf--


From nobody Tue Oct  2 10:50:54 2018
Return-Path: <mbishop@evequefou.be>
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 AD7EB131029 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 10:50:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 ECkxVAg2pl7E for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 10:50:49 -0700 (PDT)
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (mail-dm3nam05on0716.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe51::716]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BC4C130EAA for <quic@ietf.org>; Tue,  2 Oct 2018 10:50:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Bfw0FYKEiLXTTwKxRDhbJSO2dTQcuyO5ktWkeUwyucY=; b=f+YDYJzikDZVByxpTKWesQOjiClLBbGRHd7OkZ7WFB9Rq3cqlpepJgQxCv7MF64abhGM848Q23pmOxIm5c2NO3UMD0e8Q9yzjyWAczi3O6/ni0aRhf6bOQc5AFEcoF2i7l+s0JMZgV5N7f3gID9jolZ2IiNiPxE46GEhVdQK5NI=
Received: from MWHPR22MB0991.namprd22.prod.outlook.com (10.171.145.21) by MWHPR22MB0573.namprd22.prod.outlook.com (10.172.171.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1185.25; Tue, 2 Oct 2018 17:50:44 +0000
Received: from MWHPR22MB0991.namprd22.prod.outlook.com ([fe80::582e:a300:785c:8592]) by MWHPR22MB0991.namprd22.prod.outlook.com ([fe80::582e:a300:785c:8592%9]) with mapi id 15.20.1185.024; Tue, 2 Oct 2018 17:50:44 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Ted Hardie <ted.ietf@gmail.com>
CC: "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Spin bit decision
Thread-Topic: Spin bit decision
Thread-Index: AQHUWhYukd5OdbmHyk+wNZHVyKYYO6ULhImAgAAbI4CAACozgIAAHI6AgAAD4wCAAAMhAIAADuGAgAASIwCAABt7EIAABmOAgAAMAWA=
Date: Tue, 2 Oct 2018 17:50:44 +0000
Message-ID: <MWHPR22MB09917883912D880756E7DD2FDAE80@MWHPR22MB0991.namprd22.prod.outlook.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CA+9kkMCRmgS_6ZgDnv3-+V8aUhh3-As2SG2ZR0MWTC48JWQ78A@mail.gmail.com>
In-Reply-To: <CA+9kkMCRmgS_6ZgDnv3-+V8aUhh3-As2SG2ZR0MWTC48JWQ78A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [38.134.241.6]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR22MB0573; 6:TiZrqbma1fu+IfC1ZU0CCnJzar1i9ncw5nXME/Q9KFDQd91/Zsr0UyZ5bqwE2T3psl4GAp1FB3zoTLT8oGK6bMDUexHBLhV6ICWdD14+Q9C3qV4VG/vjvhxhrvrc0M0J8tlWhJ4EmLshHTHOI/n4ZknJL5cvvHJoaDuicD9/peJXExYD8Dm0PEwcR5+16M14WN83X4ddEZ1dnHDlkaeXutEY0ulUyeQKrrL1UDRF4uJ5luTAaQEELI71RSTJsJVaEeCqPLg36//Q7gCO22BEdT81djOdC57Bma1+D3SaERTt0eGt10NoogeJA7sfEoRzfM0Ds9l8Gh6pRxt7XgWvCGb5H666sIIlUV+HQEo2ZJs006HfqA8WWzScM2UqblsCJuEIyk14KGaAlZSvnWpMyef0DLG+jX+z7fkcxskMHnYAOyxFFxn3VzRWqEc8lMS3ZUvtj1A52376xrByMLnvjg==; 5:nu56aP0rXk2vupSanXG0+dxOCLk/iwpHnfQDx+Q18LLASCEakNSmmgomD4qky5qoqPQFiDbXlu1sqCHw6V/TkV3E/DTt1ql8reiLRxQvfPCBTQTNj9oVbg8/MCmF0eF3pi8n0efrfOQFCrIXJ1KOHrrII1Qi7wOQ9o81m4I27yo=; 7:6wN20+DEE0oJ+zjN+D694+rI2iPoQvb0A/YSrgf6qq3uO3Ugy7bm3/GgstYirBs20EeJtNyA+ACalWvCDzdGLhzybnhBq23SyonpLkuOvBCIEuCreR6GxuOaZh1r/6QHxcvLiFvCjRDXtAgO6bUtVXl0oH0viqK11Tb2EKG4OkVc9OeBHDsEOuO9uot1vD86l4/MjYibLw9q7dLxEPr7jF0+YaO6wzvj0tRpOxWBM7SnxETElRBOTA/+wZHbyLsS
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 5e37e1c8-8c2a-4de7-cc01-08d6288f93c3
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:MWHPR22MB0573; 
x-ms-traffictypediagnostic: MWHPR22MB0573:
x-microsoft-antispam-prvs: <MWHPR22MB057335623FC0D926BCEA0AE2DAE80@MWHPR22MB0573.namprd22.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(192374486261705)(85827821059158)(161740460382875)(18271650672692)(158342451672863)(21748063052155)(28532068793085)(190501279198761)(227612066756510);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3002001)(3231355)(944501410)(52105095)(10201501046)(93006095)(93001095)(149066)(150057)(6041310)(20161123560045)(2016111802025)(20161123562045)(20161123558120)(20161123564045)(6043046)(201708071742011)(7699051); SRVR:MWHPR22MB0573; BCL:0; PCL:0; RULEID:; SRVR:MWHPR22MB0573; 
x-forefront-prvs: 0813C68E65
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39830400003)(366004)(396003)(376002)(136003)(346002)(199004)(189003)(26005)(66066001)(5250100002)(14454004)(186003)(6246003)(102836004)(2906002)(6506007)(229853002)(5660300001)(446003)(11346002)(7116003)(19609705001)(6436002)(7696005)(53546011)(7736002)(54906003)(6916009)(74316002)(256004)(14444005)(99286004)(476003)(97736004)(76176011)(6306002)(81156014)(93886005)(81166006)(8936002)(86362001)(236005)(33656002)(316002)(74482002)(54896002)(8676002)(9686003)(3846002)(6116002)(790700001)(4326008)(71200400001)(71190400001)(68736007)(53936002)(508600001)(105586002)(25786009)(3480700004)(55016002)(486006)(39060400002)(106356001)(2900100001); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR22MB0573; H:MWHPR22MB0991.namprd22.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: dfBnQteZoWJ10MJnNdmgVCYiXmmlmbjceGjDNbZR3hjkIzjfQubDAUpmLT2EwN77vrTjpkRaQGuyUNQPWMl7mairyXF11JrD6DpHv/tG3O9O1ERcH16qO6m9O6zWcfwhTHhO03XCWMBEZGGFR6WUino0JWABbJjh+gQFxM+P9hhFsciHSZEzDMUwqoOSMu2EkNfSsVwQ7xMAv8zzoA9OZG+6Z7+B9Ey9y0+JL9HGKu0LLLbWFiUCZuQPQ9IwcCj4ezDlIb11887MX3LRNZ2sj1ZIi/Vxm66vr+/YJ3wg6YqEk//pu/AhnTgYpbM+tuGv3xRZGn+bBqL5bu6XOJuQdTFJvYs5FrWrFZCTcONozAo=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_MWHPR22MB09917883912D880756E7DD2FDAE80MWHPR22MB0991namp_"
MIME-Version: 1.0
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 5e37e1c8-8c2a-4de7-cc01-08d6288f93c3
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Oct 2018 17:50:44.1969 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR22MB0573
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/5McJlxqyLcGTTwfFd5aNcg3NYqs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 17:50:53 -0000

--_000_MWHPR22MB09917883912D880756E7DD2FDAE80MWHPR22MB0991namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SeKAmWQgY29uc2lkZXIgdGhhdCB0byBiZSDigJxwb3RlbnRpYWwgZm9yIGNhdXNpbmcgaGFybS7i
gJ0gIFdl4oCZdmUgZGVjaWRlZCB0aGF0IGNvcnJlbGF0aW9uIGlzIGEgcG90ZW50aWFsIHNlY3Vy
aXR5IHJpc2ssIGFuZCBmYWlsdXJlIHRvIGRvIHRoYXQgZXhwb3NlcyB5b3UgdG8gdGhlIHJpc2su
DQoNCkZyb206IFRlZCBIYXJkaWUgPHRlZC5pZXRmQGdtYWlsLmNvbT4NClNlbnQ6IFR1ZXNkYXks
IE9jdG9iZXIgMiwgMjAxOCAxMDowNiBBTQ0KVG86IE1pa2UgQmlzaG9wIDxtYmlzaG9wQGV2ZXF1
ZWZvdS5iZT4NCkNjOiBhbGV4YW5kcmUuZmVycmlldXhAb3JhbmdlLmNvbTsgTGFycyBFZ2dlcnQg
PGxhcnNAZWdnZXJ0Lm9yZz47IElFVEYgUVVJQyBXRyA8cXVpY0BpZXRmLm9yZz4NClN1YmplY3Q6
IFJlOiBTcGluIGJpdCBkZWNpc2lvbg0KDQpPbiBUdWUsIE9jdCAyLCAyMDE4IGF0IDk6NTEgQU0g
TWlrZSBCaXNob3AgPG1iaXNob3BAZXZlcXVlZm91LmJlPG1haWx0bzptYmlzaG9wQGV2ZXF1ZWZv
dS5iZT4+IHdyb3RlOg0KDQpJIGRvbuKAmXQgdGhpbmsgaXTigJlzIGEgZ3JpbSB2aWV3LCBJIHRo
aW5rIGl04oCZcyBhIHByYWdtYXRpYyB2aWV3LiAgT3VyIHJvbGUgaXMgdG8gc3BlY2lmeSB0aGUg
dGhpbmdzIHdoaWNoIGFyZSBmdW5kYW1lbnRhbCB0byB0aGUgcHJvdG9jb2wgYW5kIGhhdmUgdG8g
aGFwcGVuIGZvciBwZWVycyB0byBpbnRlcm9wZXJhdGUuICBNaXMtdXNpbmcgbm9ybWF0aXZlIGxh
bmd1YWdlIGZvciBvdGhlciB0aGluZ3MgaXMgYW4gYWJ1c2Ugb2YgdGhlIHByb2Nlc3MgLS0gdGhh
dCdzIGtpbmQgb2YgdGhlIHBvaW50IG9mIFJGQyA2OTE5Lg0KDQoNCg0KUkZDIDIxMTkgc2F5czoN
CkluIHBhcnRpY3VsYXIsIFtub3JtYXRpdmUgbGFuZ3VhZ2VdIE1VU1Qgb25seSBiZSB1c2VkIHdo
ZXJlIGl0IGlzIGFjdHVhbGx5IHJlcXVpcmVkIGZvciBpbnRlcm9wZXJhdGlvbiBvciB0byBsaW1p
dCBiZWhhdmlvciB3aGljaCBoYXMgcG90ZW50aWFsIGZvciBjYXVzaW5nIGhhcm0gKGUuZy4sIGxp
bWl0aW5nIHJldHJhbnNtaXNzc2lvbnMpICBGb3IgZXhhbXBsZSwgdGhleSBtdXN0IG5vdCBiZSB1
c2VkIHRvIHRyeSB0byBpbXBvc2UgYSBwYXJ0aWN1bGFyIG1ldGhvZCBvbiBpbXBsZW1lbnRvcnMg
d2hlcmUgdGhlIG1ldGhvZCBpcyBub3QgcmVxdWlyZWQgZm9yIGludGVyb3BlcmFiaWxpdHkuDQoN
Cg0KDQpHaXZlbiB0aGF0IHRoZSBzcGluIGJpdCBpcyBub3Qg4oCcYWN0dWFsbHkgcmVxdWlyZWQg
Zm9yIGludGVyb3BlcmF0aW9uLOKAnSBidXQgaXMgdGhlIHZlcnkgZGVmaW5pdGlvbiBvZiDigJx0
cnkgdG8gaW1wb3NlIGEgcGFydGljdWxhciBtZXRob2Qgb24gaW1wbGVtZW50b3JzLOKAnSBJ4oCZ
ZCBzYXkgdGhhdCBSRkMgMjExOSBpbXBlcmF0aXZlcyBhcmUgdW53YXJyYW50ZWQuDQoNClRoYXQn
cyBub3QgcXVpdGUgd2hhdCB3ZSBnZW5lcmFsbHkgbWVhbiBieSAiaW50ZXJvcGVyYXRpb24iIGhl
cmUuICBJdCdzIHF1aXRlIGNvbW1vbiB0byBoYXZlIHNvbWV0aGluZyBzYXksIGluIGVmZmVjdCwg
IklmIHlvdSB1c2UgWCwgeW91IE1VU1QgZG8gWS4iLiAgU28sIHdlIGNvdWxkIGhhdmUgYSBNVVNU
IGluIFNlY3Rpb24gMi4zIG9mIHRoZSBkcmFmdCwgaW5zdGVhZCBvZiB0aGUgY3VycmVudCBsYW5n
dWFnZToNCg0KDQogICBFYWNoIGNsaWVudCBhbmQgc2VydmVyIE1VU1QgcmVzZXQgaXRzIHNwaW4g
dmFsdWUgdG8gemVybyB3aGVuIHNlbmRpbmcgdGhlDQoNCiAgIGZpcnN0IHBhY2tldCBvZiBhIGdp
dmVuIGNvbm5lY3Rpb24gd2l0aCBhIG5ldyBjb25uZWN0aW9uIElELiAgVGhpcw0KDQogICByZWR1
Y2VzIHRoZSByaXNrIHRoYXQgdHJhbnNpZW50IHNwaW4gYml0IHN0YXRlIGNhbiBiZSB1c2VkIHRv
IGxpbmsNCg0KICAgZmxvd3MgYWNyb3NzIGNvbm5lY3Rpb24gbWlncmF0aW9uIG9yIElEIGNoYW5n
ZS4NClRoYXQgTVVTVCBkb2Vzbid0IHNheSBhbnl0aGluZyBhYm91dCB3aGVuIHlvdSB1c2UgdGhl
IHNwaW4gYml0LCBpdCBzaW1wbHkgc2F5cyB0aGF0ICppZiogIHlvdSB1c2UgaXQsIG90aGVyIGlt
cGxlbWVudGF0aW9ucyB3aWxsIGV4cGVjdCB0aGlzIGJlaGF2aW9yOyBpZiB0aGV5IGdldCBhIG5l
dyBjb25uZWN0aW9uIElEIHdpdGggYSBub24temVybyBzcGluIHZhbHVlLCBpdCB3aWxsIGJlIGEg
cHJvdG9jb2wgZXJyb3IuICBUaGF0IHBhdHRlcm4gb2YgdXNlIGlzIHZlcnkgY29tbW9uLg0KDQpU
ZWQNCg==

--_000_MWHPR22MB09917883912D880756E7DD2FDAE80MWHPR22MB0991namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZp
c2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5
Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnByZQ0KCXtt
c28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVk
IENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6
ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpwLm1zb25vcm1hbDAsIGxp
Lm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsN
Cgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTEuMHB0
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnAubS05MDcxNjk1MTUwOTY1
NDQ1NDgzbXNvcGxhaW50ZXh0LCBsaS5tLTkwNzE2OTUxNTA5NjU0NDU0ODNtc29wbGFpbnRleHQs
IGRpdi5tLTkwNzE2OTUxNTA5NjU0NDU0ODNtc29wbGFpbnRleHQNCgl7bXNvLXN0eWxlLW5hbWU6
bV8tOTA3MTY5NTE1MDk2NTQ0NTQ4M21zb3BsYWludGV4dDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0K
CW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxp
YnJpIixzYW5zLXNlcmlmO30NCnNwYW4uSFRNTFByZWZvcm1hdHRlZENoYXINCgl7bXNvLXN0eWxl
LW5hbWU6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsN
Cgltc28tc3R5bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0ZWQiOw0KCWZvbnQtZmFtaWx5OkNvbnNv
bGFzO30NCnNwYW4uRW1haWxTdHlsZTIxDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7
fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6
OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29y
ZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUg
bXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2
IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFw
ZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4N
CjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9
IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0
aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5J4oCZZCBjb25zaWRlciB0aGF0IHRvIGJlIOKA
nHBvdGVudGlhbCBmb3IgY2F1c2luZyBoYXJtLuKAnSZuYnNwOyBXZeKAmXZlIGRlY2lkZWQgdGhh
dCBjb3JyZWxhdGlvbiBpcyBhIHBvdGVudGlhbCBzZWN1cml0eSByaXNrLCBhbmQgZmFpbHVyZSB0
byBkbyB0aGF0IGV4cG9zZXMgeW91IHRvIHRoZSByaXNrLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48Yj5Gcm9tOjwvYj4gVGVkIEhhcmRpZSAmbHQ7dGVkLmlldGZAZ21haWwuY29tJmd0OyA8YnI+
DQo8Yj5TZW50OjwvYj4gVHVlc2RheSwgT2N0b2JlciAyLCAyMDE4IDEwOjA2IEFNPGJyPg0KPGI+
VG86PC9iPiBNaWtlIEJpc2hvcCAmbHQ7bWJpc2hvcEBldmVxdWVmb3UuYmUmZ3Q7PGJyPg0KPGI+
Q2M6PC9iPiBhbGV4YW5kcmUuZmVycmlldXhAb3JhbmdlLmNvbTsgTGFycyBFZ2dlcnQgJmx0O2xh
cnNAZWdnZXJ0Lm9yZyZndDs7IElFVEYgUVVJQyBXRyAmbHQ7cXVpY0BpZXRmLm9yZyZndDs8YnI+
DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFNwaW4gYml0IGRlY2lzaW9uPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5PbiBUdWUsIE9jdCAyLCAyMDE4IGF0IDk6NTEgQU0gTWlrZSBCaXNob3Ag
Jmx0OzxhIGhyZWY9Im1haWx0bzptYmlzaG9wQGV2ZXF1ZWZvdS5iZSI+bWJpc2hvcEBldmVxdWVm
b3UuYmU8L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8YmxvY2txdW90ZSBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5n
OjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0K
PGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0ibS05MDcxNjk1MTUwOTY1NDQ1NDgzbXNvcGxhaW50ZXh0
Ij5JIGRvbuKAmXQgdGhpbmsgaXTigJlzIGEgZ3JpbSB2aWV3LCBJIHRoaW5rIGl04oCZcyBhIHBy
YWdtYXRpYyB2aWV3LiZuYnNwOyBPdXIgcm9sZSBpcyB0byBzcGVjaWZ5IHRoZSB0aGluZ3Mgd2hp
Y2ggYXJlIGZ1bmRhbWVudGFsIHRvIHRoZSBwcm90b2NvbCBhbmQgaGF2ZSB0byBoYXBwZW4gZm9y
IHBlZXJzIHRvIGludGVyb3BlcmF0ZS4mbmJzcDsgTWlzLXVzaW5nIG5vcm1hdGl2ZSBsYW5ndWFn
ZQ0KIGZvciBvdGhlciB0aGluZ3MgaXMgYW4gYWJ1c2Ugb2YgdGhlIHByb2Nlc3MgLS0gdGhhdCdz
IGtpbmQgb2YgdGhlIHBvaW50IG9mIFJGQyA2OTE5LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Im0tOTA3MTY5NTE1MDk2NTQ0NTQ4M21zb3BsYWludGV4dCI+Jm5ic3A7PG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0ibS05MDcxNjk1MTUwOTY1NDQ1NDgzbXNvcGxhaW50ZXh0Ij5SRkMgMjExOSBz
YXlzOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0Oi41
aW4iPg0KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291
cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPkluIHBhcnRpY3VsYXIsIFtub3JtYXRpdmUgbGFu
Z3VhZ2VdIE1VU1Qgb25seSBiZSB1c2VkIHdoZXJlIGl0IGlzIGFjdHVhbGx5IHJlcXVpcmVkIGZv
ciBpbnRlcm9wZXJhdGlvbiBvciB0byBsaW1pdCBiZWhhdmlvciB3aGljaCBoYXMgcG90ZW50aWFs
IGZvciBjYXVzaW5nIGhhcm0gKGUuZy4sIGxpbWl0aW5nIHJldHJhbnNtaXNzc2lvbnMpJm5ic3A7
DQogRm9yIGV4YW1wbGUsIHRoZXkgbXVzdCBub3QgYmUgdXNlZCB0byB0cnkgdG8gaW1wb3NlIGEg
cGFydGljdWxhciBtZXRob2Qgb24gaW1wbGVtZW50b3JzIHdoZXJlIHRoZSBtZXRob2QgaXMgbm90
IHJlcXVpcmVkIGZvciBpbnRlcm9wZXJhYmlsaXR5Ljwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJtLTkwNzE2OTUxNTA5NjU0NDU0ODNtc29wbGFpbnRleHQiPiZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Im0tOTA3MTY5NTE1MDk2NTQ0NTQ4M21zb3BsYWludGV4dCI+R2l2
ZW4gdGhhdCB0aGUgc3BpbiBiaXQgaXMgbm90IOKAnGFjdHVhbGx5IHJlcXVpcmVkIGZvciBpbnRl
cm9wZXJhdGlvbizigJ0gYnV0IGlzIHRoZSB2ZXJ5IGRlZmluaXRpb24gb2Yg4oCcdHJ5IHRvIGlt
cG9zZSBhIHBhcnRpY3VsYXIgbWV0aG9kIG9uIGltcGxlbWVudG9ycyzigJ0gSeKAmWQgc2F5IHRo
YXQgUkZDIDIxMTkgaW1wZXJhdGl2ZXMgYXJlIHVud2FycmFudGVkLjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPlRoYXQncyBub3QgcXVpdGUgd2hhdCB3ZSBnZW5lcmFsbHkgbWVhbiBieSAmcXVvdDtpbnRl
cm9wZXJhdGlvbiZxdW90OyBoZXJlLiZuYnNwOyBJdCdzIHF1aXRlIGNvbW1vbiB0byBoYXZlIHNv
bWV0aGluZyBzYXksIGluIGVmZmVjdCwgJnF1b3Q7SWYgeW91IHVzZSBYLCB5b3UgTVVTVCBkbyBZ
LiZxdW90Oy4mbmJzcDsgU28sIHdlIGNvdWxkIGhhdmUgYSBNVVNUIGluIFNlY3Rpb24gMi4zIG9m
IHRoZSBkcmFmdCwgaW5zdGVhZCBvZiB0aGUgY3VycmVudCBsYW5ndWFnZTo8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHByZT4mbmJzcDsmbmJzcDsgRWFjaCBjbGllbnQgYW5kIHNl
cnZlciBNVVNUIHJlc2V0IGl0cyBzcGluIHZhbHVlIHRvIHplcm8gd2hlbiBzZW5kaW5nIHRoZTxv
OnA+PC9vOnA+PC9wcmU+DQo8cHJlPiZuYnNwOyZuYnNwOyBmaXJzdCBwYWNrZXQgb2YgYSBnaXZl
biBjb25uZWN0aW9uIHdpdGggYSBuZXcgY29ubmVjdGlvbiBJRC4mbmJzcDsgVGhpczxvOnA+PC9v
OnA+PC9wcmU+DQo8cHJlPiZuYnNwOyZuYnNwOyByZWR1Y2VzIHRoZSByaXNrIHRoYXQgdHJhbnNp
ZW50IHNwaW4gYml0IHN0YXRlIGNhbiBiZSB1c2VkIHRvIGxpbms8bzpwPjwvbzpwPjwvcHJlPg0K
PHByZSBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPiZuYnNwOyZuYnNwOyBmbG93cyBhY3Jv
c3MgY29ubmVjdGlvbiBtaWdyYXRpb24gb3IgSUQgY2hhbmdlLjxvOnA+PC9vOnA+PC9wcmU+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGF0IE1VU1QgZG9lc24ndCBzYXkgYW55dGhpbmcgYWJvdXQg
d2hlbiB5b3UgdXNlIHRoZSBzcGluIGJpdCwgaXQgc2ltcGx5IHNheXMgdGhhdCAqaWYqJm5ic3A7
IHlvdSB1c2UgaXQsIG90aGVyIGltcGxlbWVudGF0aW9ucyB3aWxsIGV4cGVjdCB0aGlzIGJlaGF2
aW9yOyBpZiB0aGV5IGdldCBhIG5ldyBjb25uZWN0aW9uIElEIHdpdGggYSBub24temVybyBzcGlu
IHZhbHVlLCBpdCB3aWxsIGJlIGEgcHJvdG9jb2wgZXJyb3IuJm5ic3A7DQogVGhhdCBwYXR0ZXJu
IG9mIHVzZSBpcyB2ZXJ5IGNvbW1vbi48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+VGVkPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_MWHPR22MB09917883912D880756E7DD2FDAE80MWHPR22MB0991namp_--


From nobody Tue Oct  2 11:07:49 2018
Return-Path: <martenseemann@gmail.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 66126130FF8 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 11:07:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-0.001] autolearn=unavailable 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 XaaDJI2GRwYK for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 11:07:43 -0700 (PDT)
Received: from mail-it1-x135.google.com (mail-it1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (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 21B7E130FD9 for <quic@ietf.org>; Tue,  2 Oct 2018 11:07:43 -0700 (PDT)
Received: by mail-it1-x135.google.com with SMTP id w200-v6so4983969itc.4 for <quic@ietf.org>; Tue, 02 Oct 2018 11:07:43 -0700 (PDT)
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=pKLpnYy30QjkCSu/aiB7x8Ql2/uHW8e0UhfhOMDG588=; b=q9nk8LiN8m4ZR7HPwb1qwmVH+i//nA8kI5ot7EsKzZOTI/dom7lq3lSsWPOcrg4EYm eFK95D1dQSMP2jl5w2dgTulyVdOQRn+CnRgSyXnqx3RlD3LiGoUmQ1d1aYBMrF29fLfN sv7lvN/BE9IQquVSI0ExLun3A8MenSLTNBsJLwmENPSCSosJRKo9eXRPOg4C8tdKRVA1 R9JM6nwChnFHssVnJ5PJcFCy90e28z3vt6Grl/27LVzRlyy/xRym1vXW3FopIYq+jA8K XBAutKmozoDqLPNy8FW9z66XLC9bOisxr2QtM8/Ixbd8SoRIZFVRVNqiH/ZxAj3Da87k UaGg==
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=pKLpnYy30QjkCSu/aiB7x8Ql2/uHW8e0UhfhOMDG588=; b=SV0iQODATK2sDwhNCEuQ41cvOvFtSgqrUZmHt1Ymn3C4V82ds8hXFkT42Itn3t5fCz 15a0QNRuKO4FvVl5Ux6PybnuJX1GJ8lTs6stTAaBO4S5Mfn+oPQHuZTeyjJ8KuEPlu6p j+54/hsv2e5AJIYAwps4rBMbgfNTcBpkdwjjhYINl+QNxBWBVXHMA2wxQtB7CFn7C9qo mJriKHRBo4n5ilhX4W1hlCYpTWy6uqOVrY3OXttWNHgg5yt//z48C0fLiR7wxt37W/IC t2StsaQwMU6HVUUMceBS5oivrzmIK4yRIQSyqNye5IPRW8OjTwZ62uq9uRqzu1GRDsxI ebNQ==
X-Gm-Message-State: ABuFfogkH1RTUtiukkMUWQzRmz/ArTCfLLrgjqGrCFr6gs0Wn1cDcEJ/ c7txNlYL0O0er0P7PNuCHZZsxElZnolQERlwU6M=
X-Google-Smtp-Source: ACcGV60BGTLCPcD5Ys6itbyBiPHRJYHOBOrL7T99/F45nuGNRmtn3kpEUDfaggp25OZqVXy7z03RE1QIBA6yiEzOUrM=
X-Received: by 2002:a02:91c9:: with SMTP id s9-v6mr9222443jag.104.1538503662290;  Tue, 02 Oct 2018 11:07:42 -0700 (PDT)
MIME-Version: 1.0
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com>
In-Reply-To: <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com>
From: Marten Seemann <martenseemann@gmail.com>
Date: Tue, 2 Oct 2018 11:07:30 -0700
Message-ID: <CAOYVs2o2AUN7-SV=8EcW31juLo4wZUXWrkfNMGj7+8LSH4recA@mail.gmail.com>
Subject: Re: Spin bit decision
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: Mike Bishop <mbishop@evequefou.be>, Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>, alexandre.ferrieux@orange.com
Content-Type: multipart/alternative; boundary="00000000000046ce63057742cc7b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/GWuZ8BsPAT7qO1PXEzAZTwoZRjE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 18:07:47 -0000

--00000000000046ce63057742cc7b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

> One of my concerns is unintentional mis-use of the signal, and if it
can't be detected reliably in a mixed environment, that means SHOULD is
unwise and argues for either not including it or making it a MUST.

The problem is, even if we decide to make it a MUST, a middlebox still
needs to distinguish between QUIC traffic and other UDP traffic. We're not
exposing any unambiguous signal to the path that a particular flow actually
is QUIC traffic, so middlebox vendors will have to come up with some kind
of heuristic to identify QUIC.
My fear is that if all implementations actually implement the spin bit, and
middleboxes learn to rely on that signal (and enforce compliance), we might
do great harm to other UDP based protocols (current and future) which
happen to use the same code points that middleboxes came to rely on.

Coming back to Alexandre's question, I think here is little an experiment
could do to assuage that fear. This is just another symptom of exposing
this signal in the wrong OSI layer.


On Tue, Oct 2, 2018 at 10:18 AM Ian Swett <ianswett=3D
40google.com@dmarc.ietf.org> wrote:

> One piece of information related to the above discussion is whether
> detecting who is and is not spinning is easy and reliable.
>
> One of my concerns is unintentional mis-use of the signal, and if it can'=
t
> be detected reliably in a mixed environment, that means SHOULD is unwise
> and argues for either not including it or making it a MUST.
>
> On Tue, Oct 2, 2018 at 12:51 PM Mike Bishop <mbishop@evequefou.be> wrote:
>
>> I don=E2=80=99t think it=E2=80=99s a grim view, I think it=E2=80=99s a p=
ragmatic view.  Our role
>> is to specify the things which are fundamental to the protocol and have =
to
>> happen for peers to interoperate.  Mis-using normative language for othe=
r
>> things is an abuse of the process -- that's kind of the point of RFC 691=
9.
>>
>>
>>
>> RFC 2119 says:
>>
>> In particular, [normative language] MUST only be used where it is
>> actually required for interoperation or to limit behavior which has
>> potential for causing harm (e.g., limiting retransmisssions)  For exampl=
e,
>> they must not be used to try to impose a particular method on implemento=
rs
>> where the method is not required for interoperability.
>>
>>
>>
>> Given that the spin bit is not =E2=80=9Cactually required for interopera=
tion,=E2=80=9D
>> but is the very definition of =E2=80=9Ctry to impose a particular method=
 on
>> implementors,=E2=80=9D I=E2=80=99d say that RFC 2119 imperatives are unw=
arranted.
>>
>>
>>
>> -----Original Message-----
>> From: QUIC <quic-bounces@ietf.org> On Behalf Of
>> alexandre.ferrieux@orange.com
>> Sent: Tuesday, October 2, 2018 8:05 AM
>> To: Lars Eggert <lars@eggert.org>
>> Cc: IETF QUIC WG <quic@ietf.org>
>> Subject: Re: Spin bit decision
>>
>>
>>
>> On 10/02/18 16:00, Lars Eggert wrote:
>>
>> >
>>
>> > The point I can't seem to be getting across is that irrespective of
>>
>> > what the WG decides to require, there is no penalty for individual
>>
>> > stacks at deployment time (or after) to do whatever they wish, since
>>
>> > the spin bit by design has no impact on protocol operation and interop=
.
>>
>>
>>
>> It is getting across, but it is a very grim view of the standardization
>> process itself. Are there many examples of MUST in RFCs that turned out =
to
>> be ignored by implementations just because they were not part of the cor=
e
>> semantics and hence not enforced by other peers ?
>>
>>
>>
>>
>>
>>
>> ________________________________________________________________________=
_________________________________________________
>>
>>
>>
>> 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'alterati=
on,
>> 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.
>>
>>
>>
>

--00000000000046ce63057742cc7b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">&gt;=C2=A0<span style=3D"color:rgb(33,33,33);font-size:13p=
x">One of my concerns is unintentional mis-use of the signal, and if it can=
&#39;t be detected reliably in a mixed environment, that means SHOULD is un=
wise and argues for either not including it or making it a MUST.</span><div=
 class=3D"inbox-inbox-uyb8Gf" style=3D"color:rgb(33,33,33);font-size:13px">=
<br class=3D"inbox-inbox-Apple-interchange-newline"></div><div class=3D"inb=
ox-inbox-uyb8Gf" style=3D"color:rgb(33,33,33)"><span style=3D"font-size:13p=
x">The problem is, even if we decide to make it a MUST, a middlebox still n=
eeds to distinguish between QUIC traffic and other UDP traffic. We&#39;re n=
ot exposing any </span>unambiguous signal to the path that a particular flo=
w actually is QUIC traffic, so middlebox vendors will have to come up with =
some kind of heuristic to identify QUIC.</div><div class=3D"inbox-inbox-uyb=
8Gf" style=3D"color:rgb(33,33,33)">My fear is that if all implementations a=
ctually implement the spin bit, and middleboxes learn to rely on that signa=
l (and enforce compliance), we might do great harm to other UDP based proto=
cols (current and future) which happen to use the same code points that mid=
dleboxes came to rely on.</div><div class=3D"inbox-inbox-uyb8Gf" style=3D"c=
olor:rgb(33,33,33)"><br></div><div class=3D"inbox-inbox-uyb8Gf" style=3D"co=
lor:rgb(33,33,33)">Coming back to Alexandre&#39;s question, I think here is=
 little an experiment could do to assuage that fear. This is just another s=
ymptom of exposing this signal in the wrong OSI layer.</div><div class=3D"i=
nbox-inbox-uyb8Gf" style=3D"color:rgb(33,33,33)"><br></div><div class=3D"in=
box-inbox-uyb8Gf" style=3D"color:rgb(33,33,33)"><br></div><div class=3D"gma=
il_quote"><div dir=3D"ltr">On Tue, Oct 2, 2018 at 10:18 AM Ian Swett &lt;ia=
nswett=3D<a href=3D"mailto:40google.com@dmarc.ietf.org">40google.com@dmarc.=
ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D=
"ltr">One piece of information related to the above discussion is whether d=
etecting who is and is not spinning is easy and reliable.<div><br></div><di=
v>One of my concerns is unintentional mis-use of the signal, and if it can&=
#39;t be detected reliably in a mixed environment, that means SHOULD is unw=
ise and argues for either not including it or making it a MUST.</div></div>=
<br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Oct 2, 2018 at 12:5=
1 PM Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be" target=3D"_bla=
nk">mbishop@evequefou.be</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">





<div lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"m_3148899256555212731m_-7784818331224156811WordSection1">
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">I don=
=E2=80=99t think it=E2=80=99s a grim view, I think it=E2=80=99s a pragmatic=
 view.=C2=A0 Our role is to specify the things which are fundamental to the=
 protocol and have to happen for peers to interoperate.=C2=A0 Mis-using nor=
mative language for other things is an
 abuse of the process -- that&#39;s kind of the point of RFC 6919.<u></u><u=
></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText"><u></u=
>=C2=A0<u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">RFC 21=
19 says:<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt;font-family:&quot;Courier New&quot;;color:black">In particular, [nor=
mative language] MUST only be used where it is actually required for intero=
peration or to limit behavior which has potential
 for causing harm (e.g., limiting retransmisssions)=C2=A0 For example, they=
 must not be used to try to impose a particular method on implementors wher=
e the method is not required for interoperability.<u></u><u></u></span></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText"><u></u=
>=C2=A0<u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">Given =
that the spin bit is not =E2=80=9Cactually required for interoperation,=E2=
=80=9D but is the very definition of =E2=80=9Ctry to impose a particular me=
thod on implementors,=E2=80=9D I=E2=80=99d say that RFC 2119 imperatives ar=
e unwarranted.<u></u><u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText"><u></u=
>=C2=A0<u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">-----O=
riginal Message-----<br>
From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_blank">q=
uic-bounces@ietf.org</a>&gt; On Behalf Of <a href=3D"mailto:alexandre.ferri=
eux@orange.com" target=3D"_blank">alexandre.ferrieux@orange.com</a><br>
Sent: Tuesday, October 2, 2018 8:05 AM<br>
To: Lars Eggert &lt;<a href=3D"mailto:lars@eggert.org" target=3D"_blank">la=
rs@eggert.org</a>&gt;<br>
Cc: IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">qui=
c@ietf.org</a>&gt;<br>
Subject: Re: Spin bit decision</p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText"><u></u=
>=C2=A0<u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">On 10/=
02/18 16:00, Lars Eggert wrote:<u></u><u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">&gt; <=
u></u><u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">&gt; T=
he point I can&#39;t seem to be getting across is that irrespective of
<u></u><u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">&gt; w=
hat the WG decides to require, there is no penalty for individual
<u></u><u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">&gt; s=
tacks at deployment time (or after) to do whatever they wish, since
<u></u><u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">&gt; t=
he spin bit by design has no impact on protocol operation and interop.<u></=
u><u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText"><u></u=
>=C2=A0<u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">It is =
getting across, but it is a very grim view of the standardization process i=
tself. Are there many examples of MUST in RFCs that turned out to be ignore=
d by implementations just because they were not part of the core semantics =
and
 hence not enforced by other peers ?<u></u><u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText"><u></u=
>=C2=A0<u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText"><u></u=
>=C2=A0<u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">______=
___________________________________________________________________________=
________________________________________<u></u><u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText"><u></u=
>=C2=A0<u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">Ce mes=
sage et ses pieces jointes peuvent contenir des informations confidentielle=
s ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies=
 sans autorisation. Si vous avez recu ce message par erreur, veuillez le si=
gnaler
 a l&#39;expediteur et le detruire ainsi que les pieces jointes. Les messag=
es electroniques etant susceptibles d&#39;alteration, Orange decline toute =
responsabilite si ce message a ete altere, deforme ou falsifie. Merci.<u></=
u><u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText"><u></u=
>=C2=A0<u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">This m=
essage and its attachments may contain confidential or privileged informati=
on that may be protected by law; they should not be distributed, used or co=
pied without authorisation.<u></u><u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">If you=
 have received this email in error, please notify the sender and delete thi=
s message and its attachments.<u></u><u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">As ema=
ils may be altered, Orange is not liable for messages that have been modifi=
ed, changed or falsified.<u></u><u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText">Thank =
you.<u></u><u></u></p>
<p class=3D"m_3148899256555212731m_-7784818331224156811MsoPlainText"><u></u=
>=C2=A0<u></u></p>
</div>
</div>

</blockquote></div>
</blockquote></div></div>

--00000000000046ce63057742cc7b--


From nobody Tue Oct  2 13:17:33 2018
Return-Path: <ietf@trammell.ch>
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 B33C113112E for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 13:17:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable 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 THsqORQxMCkE for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 13:17:28 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [IPv6:2001:8e0:40:325::36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4170A131110 for <quic@ietf.org>; Tue,  2 Oct 2018 13:17:28 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 3693D34118B; Tue,  2 Oct 2018 22:17:26 +0200 (CEST)
X-Iway-Path: 0
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/14501.9690);  Tue,  2 Oct 2018 22:17:23 +0200 (CEST)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Tue,  2 Oct 2018 22:17:23 +0200 (CEST)
Received: from [145.14.214.39] (account ietf@trammell.ch HELO [10.11.33.83]) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 69131424; Tue, 02 Oct 2018 22:17:23 +0200
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <475EF632-6078-443F-876C-BA25C17E152B@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_AD1918B1-588A-47E6-8FA7-F6F7F76688EF"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: signaling that QUIC is QUIC was Re: Spin bit decision
Date: Tue, 2 Oct 2018 22:17:22 +0200
In-Reply-To: <CAOYVs2o2AUN7-SV=8EcW31juLo4wZUXWrkfNMGj7+8LSH4recA@mail.gmail.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>, Mike Bishop <mbishop@evequefou.be>, alexandre.ferrieux@orange.com
To: Marten Seemann <martenseemann@gmail.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <CAOYVs2o2AUN7-SV=8EcW31juLo4wZUXWrkfNMGj7+8LSH4recA@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/hp1mztO-rTzdcskHe7RslIvgb1o>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 20:17:32 -0000

--Apple-Mail=_AD1918B1-588A-47E6-8FA7-F6F7F76688EF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

hi Marten,

> On 2 Oct 2018, at 20:07, Marten Seemann <martenseemann@gmail.com> =
wrote:
>=20
> > One of my concerns is unintentional mis-use of the signal, and if it =
can't be detected reliably in a mixed environment, that means SHOULD is =
unwise and argues for either not including it or making it a MUST.
>=20
> The problem is, even if we decide to make it a MUST, a middlebox still =
needs to distinguish between QUIC traffic and other UDP traffic. We're =
not exposing any unambiguous signal to the path that a particular flow =
actually is QUIC traffic, so middlebox vendors will have to come up with =
some kind of heuristic to identify QUIC.

Will have to, have already, will continue to. Neither wishful thinking =
nor stern lectures in RFCs nor the suitable application of strong =
cryptography will make the *perceived* requirement to distinguish QUIC =
from not-QUIC go away (without comment on whether this perception is =
accurate).

> My fear is that if all implementations actually implement the spin =
bit, and middleboxes learn to rely on that signal (and enforce =
compliance), we might do great harm to other UDP based protocols =
(current and future) which happen to use the same code points that =
middleboxes came to rely on.

Notwithstanding that tracking spin edges to determine whether something =
is QUIC or not would be a heuristic so heavyweight that widespread =
deployment of spin-classification would be unlikely, IMO the correct =
design in the face of this fear has nothing to do with the spin bit at =
all -- if we care about keeping middleboxes from breaking things =
accidentally, then we should give these middleboxes something to grab on =
to that *won't* cause collateral damage: QUIC's invariants should be =
designed in such a way that a flow as defined by 5-tuple, if not a =
packet without the context of such a 5-tuple, can be unambiguously and =
obviously classified as QUIC. We kind of got close to this during the =
New York interim during the first octet discussion with the "QUIC bit"; =
maybe we should make that explicit.

> Coming back to Alexandre's question, I think here is little an =
experiment could do to assuage that fear. This is just another symptom =
of exposing this signal in the wrong OSI layer.

(as an aside, as to whether transport-experienced end-to-end RTT =
measurability is a transport or network layer function, see also section =
5.1 of draft-trammell-tsvwg-spin.)

Cheers,

Brian

>=20
> On Tue, Oct 2, 2018 at 10:18 AM Ian Swett =
<ianswett=3D40google.com@dmarc.ietf.org> wrote:
> One piece of information related to the above discussion is whether =
detecting who is and is not spinning is easy and reliable.
>=20
> One of my concerns is unintentional mis-use of the signal, and if it =
can't be detected reliably in a mixed environment, that means SHOULD is =
unwise and argues for either not including it or making it a MUST.
>=20
> On Tue, Oct 2, 2018 at 12:51 PM Mike Bishop <mbishop@evequefou.be> =
wrote:
> I don=E2=80=99t think it=E2=80=99s a grim view, I think it=E2=80=99s a =
pragmatic view.  Our role is to specify the things which are fundamental =
to the protocol and have to happen for peers to interoperate.  Mis-using =
normative language for other things is an abuse of the process -- that's =
kind of the point of RFC 6919.
>=20
>=20
>=20
> RFC 2119 says:
>=20
> In particular, [normative language] MUST only be used where it is =
actually required for interoperation or to limit behavior which has =
potential for causing harm (e.g., limiting retransmisssions)  For =
example, they must not be used to try to impose a particular method on =
implementors where the method is not required for interoperability.
>=20
>=20
>=20
> Given that the spin bit is not =E2=80=9Cactually required for =
interoperation,=E2=80=9D but is the very definition of =E2=80=9Ctry to =
impose a particular method on implementors,=E2=80=9D I=E2=80=99d say =
that RFC 2119 imperatives are unwarranted.
>=20
>=20
>=20
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of =
alexandre.ferrieux@orange.com
> Sent: Tuesday, October 2, 2018 8:05 AM
> To: Lars Eggert <lars@eggert.org>
> Cc: IETF QUIC WG <quic@ietf.org>
> Subject: Re: Spin bit decision
>=20
>=20
>=20
> On 10/02/18 16:00, Lars Eggert wrote:
>=20
> >
>=20
> > The point I can't seem to be getting across is that irrespective of
>=20
> > what the WG decides to require, there is no penalty for individual
>=20
> > stacks at deployment time (or after) to do whatever they wish, since
>=20
> > the spin bit by design has no impact on protocol operation and =
interop.
>=20
>=20
>=20
> It is getting across, but it is a very grim view of the =
standardization process itself. Are there many examples of MUST in RFCs =
that turned out to be ignored by implementations just because they were =
not part of the core semantics and hence not enforced by other peers ?
>=20
>=20
>=20
>=20
>=20
> =
__________________________________________________________________________=
_______________________________________________
>=20
>=20
>=20
> 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.
>=20
>=20
>=20
> 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.
>=20
> If you have received this email in error, please notify the sender and =
delete this message and its attachments.
>=20
> As emails may be altered, Orange is not liable for messages that have =
been modified, changed or falsified.
>=20
> Thank you.
>=20
>=20
>=20


--Apple-Mail=_AD1918B1-588A-47E6-8FA7-F6F7F76688EF
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAluz0lIACgkQihK3vwvq
RqOM1w/9FdN+2HCucCm/irpB/DnOa1qNlUXkck/gr4J9s/BsHO6P2J0KGbnxMYr2
BG13Ejjhh2Pl1wn/weJnuG585bnw4GCt7ShUGgntYlL0dcnnmHuUIkf45NTJw4kx
n5KtDsY00Rr68Z2VWla4vJtzQRKy6OAK/tiZxMSQZZ2HGI4qwueyA3v7+4kHR2Hi
lMK5KP0zcg4wJb61z7o9qKzaCX4D/g+9TCQbUTc9GWgBprzVe4iCUN2CduwTK3qQ
PHN+vcsiEhwWK1nivngNIdnSMyZ8vNr6SjSevxeYiQNgBb+TNWSGKUdzVnQu/xHp
iiwBr2YizgZDb/rwza4BhI8Xz+cbsNftJ07hhx/FI9SYEYGtdBaNAOmlG0E/QpTp
7gs05ykaEO/xYY5f+0LigRZk+2bHOaG7jUCGLGq6MAbW/1zOzV9FF1mnu8s/nYTV
wpEOYrAUpHdIrESiEm5uV3aVKqdydnE0I8bH3hqLP1P7cF37131I82CV6fiBvWBw
WTMLUFSC4io/sg9sGRDGCLms1SguI1LggAYFaJYb4ae2nqA6jtuGP6QG2YTCfKH6
qtRRVe9L5JrjV7SjsRmlaRO3Eh6PU5sF8+9OEMXChkJnMGESXkoOojiUd590Tew+
mx3WGK9BgASi2gUoLozelGaexjca1zcXxoMrIIiJKdTXfjwWxB4=
=jSFF
-----END PGP SIGNATURE-----

--Apple-Mail=_AD1918B1-588A-47E6-8FA7-F6F7F76688EF--


From nobody Tue Oct  2 14:10:51 2018
Return-Path: <ietf@trammell.ch>
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 3596A131182 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 14:10:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 MLaBPnBQCEBE for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 14:10:47 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [IPv6:2001:8e0:40:325::36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12FC913117F for <quic@ietf.org>; Tue,  2 Oct 2018 14:10:47 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 7D028341721; Tue,  2 Oct 2018 23:10:45 +0200 (CEST)
X-Iway-Path: 0
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/14501.13199); Tue,  2 Oct 2018 23:10:44 +0200 (CEST)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Tue,  2 Oct 2018 23:10:44 +0200 (CEST)
Received: from [145.14.214.39] (account ietf@trammell.ch HELO [10.11.33.83]) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 69133598; Tue, 02 Oct 2018 23:10:44 +0200
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_120035F5-7CC1-4213-ACC2-5BA08A0CF00F"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: a proposed way forward was Re: Spin bit decision
Date: Tue, 2 Oct 2018 23:10:43 +0200
In-Reply-To: <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com>
Cc: Mike Bishop <mbishop@evequefou.be>, Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>, alexandre.ferrieux@orange.com
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/FF9oIcq3jdrfgqf0ZdVH1uHmsiI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 21:10:49 -0000

--Apple-Mail=_120035F5-7CC1-4213-ACC2-5BA08A0CF00F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

hi Ian, all,

Perhaps we can exploit the asymmetry inherent in QUIC (there are servers =
and clients), the spin bit (the server reflects, the client inverts), =
and the desire to participate or not (ISTM that most of the discussion =
we've had about opting out have focused on client opt-out, based either =
on the principle of the thing and/or a suspicion that the signal is =
useless) to resolve this discussion.


A proposal:

1. Servers MUST reflect the spin value. Clients MAY treat an =
unambiguously detected non-reflected bit as a protocol error.

2a. Clients SHOULD invert the spin value, unless [EDNOTE: someone other =
than me should write convincing reasons for non-implementation here], or =
the client has been configured not to spin, or to use some other client =
behavior.

-OR-

2b. Clients set the spin bit value as they see fit, provided that this =
behavior is consistent per connection ID. In order to provide RTT =
information to the path, clients MAY invert the spin value (per =
reference to a separate RFC that looks a lot like draft-tsvwg-quic=3Dspin,=
 to be published by QUIC, TSVWG, or IPPM).

3. Servers and clients MUST NOT expose spin state from one Connection ID =
to another Connection ID.


1 is intended to drive deployment through server defaults. Yes, one can =
argue that the protocol error here is artificial (and the proposal =
explicitly acknowledges that through the client MAY error out), but the =
client can always opt out by clamping to a random value per CID.

The 2a variant is essentially a 2119-compliant way of saying "we'd =
really like it if you implemented the spin bit", leaving the question of =
client defaults (opt in versus opt out) up to the client implementors.

The 2b variant is designed to allow for future or parallel client-side =
behaviors other than spinning to support different measurement goals. =
For example, using the adaptive square wave proposed for on-path loss =
measurement (by either Mikkel or Kazuho, I believe) at the client with =
server reflection would allow accumulation of loss on the upstream as =
well as the downstream path, as well as upstream (toward the server) RTT =
measurement. Obviously, the set of these deployed in the wild would have =
to be kept small in order to allow a measurement device to heuristically =
determine which signal was in use given a spinbit stream.

3 prevents spin state from leaking across CIDs, reducing the (already =
tiny but nonzero) linkability surface.

(Obviously, the above needs wordsmithing, but these are the broad =
lines.)

Cheers,

Brian

> On 2 Oct 2018, at 19:13, Ian Swett =
<ianswett=3D40google.com@dmarc.ietf.org> wrote:
>=20
> One piece of information related to the above discussion is whether =
detecting who is and is not spinning is easy and reliable.
>=20
> One of my concerns is unintentional mis-use of the signal, and if it =
can't be detected reliably in a mixed environment, that means SHOULD is =
unwise and argues for either not including it or making it a MUST.
>=20
> On Tue, Oct 2, 2018 at 12:51 PM Mike Bishop <mbishop@evequefou.be> =
wrote:
> I don=E2=80=99t think it=E2=80=99s a grim view, I think it=E2=80=99s a =
pragmatic view.  Our role is to specify the things which are fundamental =
to the protocol and have to happen for peers to interoperate.  Mis-using =
normative language for other things is an abuse of the process -- that's =
kind of the point of RFC 6919.
>=20
>=20
>=20
> RFC 2119 says:
>=20
> In particular, [normative language] MUST only be used where it is =
actually required for interoperation or to limit behavior which has =
potential for causing harm (e.g., limiting retransmisssions)  For =
example, they must not be used to try to impose a particular method on =
implementors where the method is not required for interoperability.
>=20
>=20
>=20
> Given that the spin bit is not =E2=80=9Cactually required for =
interoperation,=E2=80=9D but is the very definition of =E2=80=9Ctry to =
impose a particular method on implementors,=E2=80=9D I=E2=80=99d say =
that RFC 2119 imperatives are unwarranted.
>=20
>=20
>=20
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of =
alexandre.ferrieux@orange.com
> Sent: Tuesday, October 2, 2018 8:05 AM
> To: Lars Eggert <lars@eggert.org>
> Cc: IETF QUIC WG <quic@ietf.org>
> Subject: Re: Spin bit decision
>=20
>=20
>=20
> On 10/02/18 16:00, Lars Eggert wrote:
>=20
> >
>=20
> > The point I can't seem to be getting across is that irrespective of
>=20
> > what the WG decides to require, there is no penalty for individual
>=20
> > stacks at deployment time (or after) to do whatever they wish, since
>=20
> > the spin bit by design has no impact on protocol operation and =
interop.
>=20
>=20
>=20
> It is getting across, but it is a very grim view of the =
standardization process itself. Are there many examples of MUST in RFCs =
that turned out to be ignored by implementations just because they were =
not part of the core semantics and hence not enforced by other peers ?
>=20
>=20
>=20
>=20
>=20
> =
__________________________________________________________________________=
_______________________________________________
>=20
>=20
>=20
> 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.
>=20
>=20
>=20
> 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.
>=20
> If you have received this email in error, please notify the sender and =
delete this message and its attachments.
>=20
> As emails may be altered, Orange is not liable for messages that have =
been modified, changed or falsified.
>=20
> Thank you.
>=20
>=20
>=20


--Apple-Mail=_120035F5-7CC1-4213-ACC2-5BA08A0CF00F
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAluz3tMACgkQihK3vwvq
RqNGaA/+KdOTv+QljnH9+l6gSIU/NE5pLuNwt7gVKVJtISHFNB1RIXP4ulrvYYkF
s6OBt1IfDtV1KZAsIcviXRM30wmYR8ymI90CpWprH00X+ktR46t0lV6rjp9y+kep
87Tt01dVFJ4sWwUI67N1mZv/au7i0+DegwvK0hW/CQbbJKeAx0AM/1ozADL1dw5z
/cI402TE+v1DvefwrukIwbyG4g7WzMQzzo7pgRapt35VwSb1dOjelkK2mFAi/Fqa
gMYaffdX4nSFvGLS5pkfUUbrgTl6MegTbsDBhYSXTTUKF+eN/lKylLipwkpT5fLp
jQVFct+nRakPT0mRllQ6F0s8MkIYvpWUCScNfHGGWWaN6rrU/pdWKrLoJVL4/luO
yE5286Dp719kiWk+ZgH9Xfwxh+LRv5JMQvnjw6oNfEmiFKO8BrlLaV/CR0z4yL1j
tDFzLNWE9SK9wQmKvG74+fk2YB842o5UUqIBW4ClDU9zcHBS15QaDRnGf+B4ZXO0
bCY9REKV+m7UkvejcMKbysiNSiolPQVt9N2HSZp/WxGEn9qvFQlc2+n4aZzSxJOF
WOgj8yGSvhamuIxCN+MR47tklVoNIw1BwqWtRgc9ke4l3dvm54YzmNYcGX+0HW6L
XvxDNZqB5a+qf/lVSPbA11NxSVgu//fWdb8PfXo+y6xw3bHputQ=
=f0dj
-----END PGP SIGNATURE-----

--Apple-Mail=_120035F5-7CC1-4213-ACC2-5BA08A0CF00F--


From nobody Tue Oct  2 14:23:27 2018
Return-Path: <martenseemann@gmail.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 E298A131199 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 14:23:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-0.001] 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 zxK3wwDTd8G5 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 14:23:23 -0700 (PDT)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (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 57B951310E3 for <quic@ietf.org>; Tue,  2 Oct 2018 14:23:23 -0700 (PDT)
Received: by mail-io1-xd35.google.com with SMTP id e2-v6so1642308ioh.5 for <quic@ietf.org>; Tue, 02 Oct 2018 14:23:23 -0700 (PDT)
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=sQMcxZpQmdAfgBWiwPaxS6ZjTVtxmW/P1TgR0xvaiNM=; b=MCjFtNqobuOO0V3Fn7gaiVlBGsCd6OnwTPqoQaCCQimre2oxAiTP56iYvayfz4Etp2 w45p49SDJnDWyDhY3gYjmkZyKIoKGXPc/RtmBPLRanZsWExed0g4I8jMM0R6OAJ77lVK ZB4gnQbLo1t0H9WJubR2dzf3DrhXzxRMIqKPituTR0HipcJmmauRKO66hll4qtDsCMUC QBXYLDLKJiN8ygh/rVcySxDdGOE0Vxf/DNxK5bNHu3Pyj9y//g1WTIH3FaGxJw6lZnYI MunM8s/XgphijyXKGD4tXjXay4rkBTs7/c8S6HUgOnOhRWfNmkEnukKAVXahoRP/FHPa QhEw==
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=sQMcxZpQmdAfgBWiwPaxS6ZjTVtxmW/P1TgR0xvaiNM=; b=AzJE8TUwHh53e2YhgmXtTNxdEQh1TWqP1Q/KDuJWhHzku0YEfwCWDXaf1XtpNyHqYq 09m83/DijRqgqtzF8qZ67par5pGtaexSOs/QavHuNne62RGKgSRxjqSFBkD1x/aNgiBH g28frWYUJPbWeTaaF9eP+aXyTe3Er9Y4IrKr/CJCak34XiuQKODJzf9+V8sUZ7C6gXqs X+9R6DLQ7YsTPvK19XxCRQO3QqQLOmiBTJKsujbFqtTWLg7dW9p2Y++ZRV3Um/nWaE36 r02NyqEyADZz+RA9S3/TK2PvgW6lFzLwBv9Og4Ml0FRSPO34kaKbPOXrzv+LJw7OQC7d l5bg==
X-Gm-Message-State: ABuFfogZv2tM2I6FTBxi/5ua/zf4AQB9N3Ni70GnbRXWHS8Iy++p2Dw9 +Ue7Gr8dPW4HqHGjFcblHse/j6FltSRdbusgMA4=
X-Google-Smtp-Source: ACcGV63b+kxUoccD//Yf8KutonlhwcH5gc2Z3YMhVeNSf2aINGY145Ozs5Tp54A9fizR0SI1DFS1ddta94XW5cfBuek=
X-Received: by 2002:a5e:8b48:: with SMTP id z8-v6mr11607481iom.100.1538515402451;  Tue, 02 Oct 2018 14:23:22 -0700 (PDT)
MIME-Version: 1.0
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch>
In-Reply-To: <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch>
From: Marten Seemann <martenseemann@gmail.com>
Date: Tue, 2 Oct 2018 14:23:10 -0700
Message-ID: <CAOYVs2pg1jRmAZ=i_C2YLb9g-pVgtvh_d_xpeP_8MjXV_ytVdw@mail.gmail.com>
Subject: Re: a proposed way forward was Re: Spin bit decision
To: "Brian Trammell (IETF)" <ietf@trammell.ch>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Lars Eggert <lars@eggert.org>,  IETF QUIC WG <quic@ietf.org>, Mike Bishop <mbishop@evequefou.be>, alexandre.ferrieux@orange.com
Content-Type: multipart/alternative; boundary="0000000000000b71750577458820"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7fpNTvFjXV3EOw-TAgEBKJlyoik>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 21:23:26 -0000

--0000000000000b71750577458820
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

> 1. Servers MUST reflect the spin value. Clients MAY treat an
unambiguously detected non-reflected bit as a protocol error.

This might works for classical client-server deployment, but in the p2p use
case, the terms "client" and "server" are a bit misleading, and we're just
using them for simplicity in the draft. Both "client" and "server" are
really just peers on the network, one of which happened to initiate the
connection and the other one accepted the connection.
If we acknowledge that there are convincing reasons to opt-out of exposing
the spin bit, both sides need to have the ability to do so.

On Tue, Oct 2, 2018 at 2:11 PM Brian Trammell (IETF) <ietf@trammell.ch>
wrote:

> hi Ian, all,
>
> Perhaps we can exploit the asymmetry inherent in QUIC (there are servers
> and clients), the spin bit (the server reflects, the client inverts), and
> the desire to participate or not (ISTM that most of the discussion we've
> had about opting out have focused on client opt-out, based either on the
> principle of the thing and/or a suspicion that the signal is useless) to
> resolve this discussion.
>
>
> A proposal:
>
> 1. Servers MUST reflect the spin value. Clients MAY treat an unambiguousl=
y
> detected non-reflected bit as a protocol error.
>
> 2a. Clients SHOULD invert the spin value, unless [EDNOTE: someone other
> than me should write convincing reasons for non-implementation here], or
> the client has been configured not to spin, or to use some other client
> behavior.
>
> -OR-
>
> 2b. Clients set the spin bit value as they see fit, provided that this
> behavior is consistent per connection ID. In order to provide RTT
> information to the path, clients MAY invert the spin value (per reference
> to a separate RFC that looks a lot like draft-tsvwg-quic=3Dspin, to be
> published by QUIC, TSVWG, or IPPM).
>
> 3. Servers and clients MUST NOT expose spin state from one Connection ID
> to another Connection ID.
>
>
> 1 is intended to drive deployment through server defaults. Yes, one can
> argue that the protocol error here is artificial (and the proposal
> explicitly acknowledges that through the client MAY error out), but the
> client can always opt out by clamping to a random value per CID.
>
> The 2a variant is essentially a 2119-compliant way of saying "we'd really
> like it if you implemented the spin bit", leaving the question of client
> defaults (opt in versus opt out) up to the client implementors.
>
> The 2b variant is designed to allow for future or parallel client-side
> behaviors other than spinning to support different measurement goals. For
> example, using the adaptive square wave proposed for on-path loss
> measurement (by either Mikkel or Kazuho, I believe) at the client with
> server reflection would allow accumulation of loss on the upstream as wel=
l
> as the downstream path, as well as upstream (toward the server) RTT
> measurement. Obviously, the set of these deployed in the wild would have =
to
> be kept small in order to allow a measurement device to heuristically
> determine which signal was in use given a spinbit stream.
>
> 3 prevents spin state from leaking across CIDs, reducing the (already tin=
y
> but nonzero) linkability surface.
>
> (Obviously, the above needs wordsmithing, but these are the broad lines.)
>
> Cheers,
>
> Brian
>
> > On 2 Oct 2018, at 19:13, Ian Swett <ianswett=3D40google.com@dmarc.ietf.=
org>
> wrote:
> >
> > One piece of information related to the above discussion is whether
> detecting who is and is not spinning is easy and reliable.
> >
> > One of my concerns is unintentional mis-use of the signal, and if it
> can't be detected reliably in a mixed environment, that means SHOULD is
> unwise and argues for either not including it or making it a MUST.
> >
> > On Tue, Oct 2, 2018 at 12:51 PM Mike Bishop <mbishop@evequefou.be>
> wrote:
> > I don=E2=80=99t think it=E2=80=99s a grim view, I think it=E2=80=99s a =
pragmatic view.  Our role
> is to specify the things which are fundamental to the protocol and have t=
o
> happen for peers to interoperate.  Mis-using normative language for other
> things is an abuse of the process -- that's kind of the point of RFC 6919=
.
> >
> >
> >
> > RFC 2119 says:
> >
> > In particular, [normative language] MUST only be used where it is
> actually required for interoperation or to limit behavior which has
> potential for causing harm (e.g., limiting retransmisssions)  For example=
,
> they must not be used to try to impose a particular method on implementor=
s
> where the method is not required for interoperability.
> >
> >
> >
> > Given that the spin bit is not =E2=80=9Cactually required for interoper=
ation,=E2=80=9D
> but is the very definition of =E2=80=9Ctry to impose a particular method =
on
> implementors,=E2=80=9D I=E2=80=99d say that RFC 2119 imperatives are unwa=
rranted.
> >
> >
> >
> > -----Original Message-----
> > From: QUIC <quic-bounces@ietf.org> On Behalf Of
> alexandre.ferrieux@orange.com
> > Sent: Tuesday, October 2, 2018 8:05 AM
> > To: Lars Eggert <lars@eggert.org>
> > Cc: IETF QUIC WG <quic@ietf.org>
> > Subject: Re: Spin bit decision
> >
> >
> >
> > On 10/02/18 16:00, Lars Eggert wrote:
> >
> > >
> >
> > > The point I can't seem to be getting across is that irrespective of
> >
> > > what the WG decides to require, there is no penalty for individual
> >
> > > stacks at deployment time (or after) to do whatever they wish, since
> >
> > > the spin bit by design has no impact on protocol operation and intero=
p.
> >
> >
> >
> > It is getting across, but it is a very grim view of the standardization
> process itself. Are there many examples of MUST in RFCs that turned out t=
o
> be ignored by implementations just because they were not part of the core
> semantics and hence not enforced by other peers ?
> >
> >
> >
> >
> >
> >
> _________________________________________________________________________=
________________________________________________
> >
> >
> >
> > 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'alteratio=
n,
> Orange decline toute responsabilite si ce message a ete altere, deforme o=
u
> 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.
> >
> >
> >
>
>

--0000000000000b71750577458820
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">&gt;=C2=A0<span style=3D"color:rgb(33,33,33)">1. Servers M=
UST reflect the spin value. Clients MAY treat an unambiguously detected non=
-reflected bit as a protocol error.</span><br style=3D"color:rgb(33,33,33)"=
><div><span style=3D"color:rgb(33,33,33)"><br></span></div><div><span style=
=3D"color:rgb(33,33,33)">This might works for classical client-server deplo=
yment, but in the p2p use case, the terms &quot;client&quot; and &quot;serv=
er&quot; are a bit misleading, and we&#39;re just using them for simplicity=
 in the draft. Both &quot;client&quot; and &quot;server&quot; are really ju=
st peers on the network, one of which happened to initiate the connection a=
nd the other one accepted the connection.</span></div><div><span style=3D"c=
olor:rgb(33,33,33)">If we acknowledge that there are convincing reasons to =
opt-out of exposing the spin bit, both sides need to have the ability to do=
 so.</span></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On T=
ue, Oct 2, 2018 at 2:11 PM Brian Trammell (IETF) &lt;<a href=3D"mailto:ietf=
@trammell.ch">ietf@trammell.ch</a>&gt; wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">hi Ian, all,<br>
<br>
Perhaps we can exploit the asymmetry inherent in QUIC (there are servers an=
d clients), the spin bit (the server reflects, the client inverts), and the=
 desire to participate or not (ISTM that most of the discussion we&#39;ve h=
ad about opting out have focused on client opt-out, based either on the pri=
nciple of the thing and/or a suspicion that the signal is useless) to resol=
ve this discussion.<br>
<br>
<br>
A proposal:<br>
<br>
1. Servers MUST reflect the spin value. Clients MAY treat an unambiguously =
detected non-reflected bit as a protocol error.<br>
<br>
2a. Clients SHOULD invert the spin value, unless [EDNOTE: someone other tha=
n me should write convincing reasons for non-implementation here], or the c=
lient has been configured not to spin, or to use some other client behavior=
.<br>
<br>
-OR-<br>
<br>
2b. Clients set the spin bit value as they see fit, provided that this beha=
vior is consistent per connection ID. In order to provide RTT information t=
o the path, clients MAY invert the spin value (per reference to a separate =
RFC that looks a lot like draft-tsvwg-quic=3Dspin, to be published by QUIC,=
 TSVWG, or IPPM).<br>
<br>
3. Servers and clients MUST NOT expose spin state from one Connection ID to=
 another Connection ID.<br>
<br>
<br>
1 is intended to drive deployment through server defaults. Yes, one can arg=
ue that the protocol error here is artificial (and the proposal explicitly =
acknowledges that through the client MAY error out), but the client can alw=
ays opt out by clamping to a random value per CID.<br>
<br>
The 2a variant is essentially a 2119-compliant way of saying &quot;we&#39;d=
 really like it if you implemented the spin bit&quot;, leaving the question=
 of client defaults (opt in versus opt out) up to the client implementors.<=
br>
<br>
The 2b variant is designed to allow for future or parallel client-side beha=
viors other than spinning to support different measurement goals. For examp=
le, using the adaptive square wave proposed for on-path loss measurement (b=
y either Mikkel or Kazuho, I believe) at the client with server reflection =
would allow accumulation of loss on the upstream as well as the downstream =
path, as well as upstream (toward the server) RTT measurement. Obviously, t=
he set of these deployed in the wild would have to be kept small in order t=
o allow a measurement device to heuristically determine which signal was in=
 use given a spinbit stream.<br>
<br>
3 prevents spin state from leaking across CIDs, reducing the (already tiny =
but nonzero) linkability surface.<br>
<br>
(Obviously, the above needs wordsmithing, but these are the broad lines.)<b=
r>
<br>
Cheers,<br>
<br>
Brian<br>
<br>
&gt; On 2 Oct 2018, at 19:13, Ian Swett &lt;ianswett=3D<a href=3D"mailto:40=
google.com@dmarc.ietf.org" target=3D"_blank">40google.com@dmarc.ietf.org</a=
>&gt; wrote:<br>
&gt; <br>
&gt; One piece of information related to the above discussion is whether de=
tecting who is and is not spinning is easy and reliable.<br>
&gt; <br>
&gt; One of my concerns is unintentional mis-use of the signal, and if it c=
an&#39;t be detected reliably in a mixed environment, that means SHOULD is =
unwise and argues for either not including it or making it a MUST.<br>
&gt; <br>
&gt; On Tue, Oct 2, 2018 at 12:51 PM Mike Bishop &lt;<a href=3D"mailto:mbis=
hop@evequefou.be" target=3D"_blank">mbishop@evequefou.be</a>&gt; wrote:<br>
&gt; I don=E2=80=99t think it=E2=80=99s a grim view, I think it=E2=80=99s a=
 pragmatic view.=C2=A0 Our role is to specify the things which are fundamen=
tal to the protocol and have to happen for peers to interoperate.=C2=A0 Mis=
-using normative language for other things is an abuse of the process -- th=
at&#39;s kind of the point of RFC 6919.<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; RFC 2119 says:<br>
&gt; <br>
&gt; In particular, [normative language] MUST only be used where it is actu=
ally required for interoperation or to limit behavior which has potential f=
or causing harm (e.g., limiting retransmisssions)=C2=A0 For example, they m=
ust not be used to try to impose a particular method on implementors where =
the method is not required for interoperability.<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; Given that the spin bit is not =E2=80=9Cactually required for interope=
ration,=E2=80=9D but is the very definition of =E2=80=9Ctry to impose a par=
ticular method on implementors,=E2=80=9D I=E2=80=99d say that RFC 2119 impe=
ratives are unwarranted.<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; -----Original Message-----<br>
&gt; From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_bla=
nk">quic-bounces@ietf.org</a>&gt; On Behalf Of <a href=3D"mailto:alexandre.=
ferrieux@orange.com" target=3D"_blank">alexandre.ferrieux@orange.com</a><br=
>
&gt; Sent: Tuesday, October 2, 2018 8:05 AM<br>
&gt; To: Lars Eggert &lt;<a href=3D"mailto:lars@eggert.org" target=3D"_blan=
k">lars@eggert.org</a>&gt;<br>
&gt; Cc: IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank=
">quic@ietf.org</a>&gt;<br>
&gt; Subject: Re: Spin bit decision<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; On 10/02/18 16:00, Lars Eggert wrote:<br>
&gt; <br>
&gt; &gt;<br>
&gt; <br>
&gt; &gt; The point I can&#39;t seem to be getting across is that irrespect=
ive of<br>
&gt; <br>
&gt; &gt; what the WG decides to require, there is no penalty for individua=
l<br>
&gt; <br>
&gt; &gt; stacks at deployment time (or after) to do whatever they wish, si=
nce<br>
&gt; <br>
&gt; &gt; the spin bit by design has no impact on protocol operation and in=
terop.<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; It is getting across, but it is a very grim view of the standardizatio=
n process itself. Are there many examples of MUST in RFCs that turned out t=
o be ignored by implementations just because they were not part of the core=
 semantics and hence not enforced by other peers ?<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; ______________________________________________________________________=
___________________________________________________<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; Ce message et ses pieces jointes peuvent contenir des informations con=
fidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploite=
s ou copies sans autorisation. Si vous avez recu ce message par erreur, veu=
illez le signaler a l&#39;expediteur et le detruire ainsi que les pieces jo=
intes. Les messages electroniques etant susceptibles d&#39;alteration, Oran=
ge decline toute responsabilite si ce message a ete altere, deforme ou fals=
ifie. Merci.<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; This message and its attachments may contain confidential or privilege=
d information that may be protected by law; they should not be distributed,=
 used or copied without authorisation.<br>
&gt; <br>
&gt; If you have received this email in error, please notify the sender and=
 delete this message and its attachments.<br>
&gt; <br>
&gt; As emails may be altered, Orange is not liable for messages that have =
been modified, changed or falsified.<br>
&gt; <br>
&gt; Thank you.<br>
&gt; <br>
&gt; <br>
&gt; <br>
<br>
</blockquote></div>

--0000000000000b71750577458820--


From nobody Tue Oct  2 15:14:35 2018
Return-Path: <alexandre.ferrieux@orange.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 4BC1413119F for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 15:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.291
X-Spam-Level: 
X-Spam-Status: No, score=-0.291 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 E_7EndtNJgro for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 15:14:32 -0700 (PDT)
Received: from orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E4FF131182 for <quic@ietf.org>; Tue,  2 Oct 2018 15:14:32 -0700 (PDT)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id 42Ptjf1Phpz1yyX; Wed,  3 Oct 2018 00:14:30 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id 42Ptjf0NdCzDq7C; Wed,  3 Oct 2018 00:14:30 +0200 (CEST)
Received: from [10.193.4.89] (10.168.234.4) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 3 Oct 2018 00:14:29 +0200
Subject: Re: Spin bit decision
To: Mike Bishop <mbishop@evequefou.be>, Lars Eggert <lars@eggert.org>
CC: IETF QUIC WG <quic@ietf.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com>
From: <alexandre.ferrieux@orange.com>
Message-ID: <4629_1538518470_5BB3EDC6_4629_90_1_071dda88-6bd8-fdf6-2321-d59c928ce904@orange.com>
Date: Wed, 3 Oct 2018 00:12:48 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: fr-xx-moderne
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: [10.168.234.4]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YcVTemTcZLSEtwL-F5sJ-UYi7AE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 22:14:33 -0000

On 10/02/18 18:50, Mike Bishop wrote:
> Given that the spin bit is not =E2=80=9Cactually required for interoperat=
ion,=E2=80=9D but is=20
> the very definition of =E2=80=9Ctry to impose a particular method on impl=
ementors,=E2=80=9D I=E2=80=99d=20
> say that RFC 2119 imperatives are unwarranted.

My naive belief was that we were in the process of (1) deciding whether we'=
d=20
like the spin bit to be widespread; and later, (2) how to get there given t=
he=20
fact that implementors are moderately only constrained by  RFCs.

But your statements above seem to indicate that (1)=3DNO.
Is this consensual already ? If yes, why are we discussing at all ?




___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Tue Oct  2 16:31:47 2018
Return-Path: <kazuhooku@gmail.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 3D926130FBD for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 16:31:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 FYcvNK2mgESg for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 16:31:42 -0700 (PDT)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 BAA7C1310B7 for <quic@ietf.org>; Tue,  2 Oct 2018 16:31:41 -0700 (PDT)
Received: by mail-lf1-x12e.google.com with SMTP id w21-v6so2743124lff.6 for <quic@ietf.org>; Tue, 02 Oct 2018 16:31:41 -0700 (PDT)
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:content-transfer-encoding; bh=PYqxxkP47khONn8d8b78wnnJvRwQYS6h/OmW0e960QQ=; b=SZ8V3+H1iZvhqMJK02XaHPntnl8JC5zJLJTpnDwscqWlG8I5tq2dYyKURVSwqEPrwK kold/MEQWeSBwc5oWWjNLZoKdH3D8buoSt5ez4UBoRztkrVSWNbErnbdrwPH7g6Encu/ wnBTIqOYtzaAaFj0ipnEfWHaltA7lIwABmqjkqsJVjertu5pb/cQkHcteOkmYJji4Bkf VMEsiLAGBs4xQnIl+8Sxirw+bKdanSlYIR8a+XYKCrROUQPsLL9kfP39yA4tgb1s7tEg GA7VRukliGXeJB1bb6FMERVxT3VtwD/9ogucDSJD7f6ohdC0D4fS2SNhQL8B8EdhNLLp tCJw==
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:content-transfer-encoding; bh=PYqxxkP47khONn8d8b78wnnJvRwQYS6h/OmW0e960QQ=; b=pHXGQvw0z2R6Ou9Pd6B2AGWUV5TcXv3nqyr3tDar33XziOKj3hr3qGONMJEzHOt5+G y+YLOEBLq70m2vbtrEyC6y3z4XhdpsXiUOXpLO0M0j2aVlQ7vzCChMIezOzNrjDFO/y3 UvDvkPLVO6oAslHO8BXiLMyebhdFmLX/A6Gt2ybwnN6FOkXe1R3obl2CYUV8IyReptdu gQx15tFEkwrO6EBLgOpvfpnxGdH2+CkdYKk5zRvfvssko3MW7b5lNdUsHzTOSknHUlan 18wON5uK6ap30j0/LABArVs6G7e8ycbGs+X4mX+Gf8YZ+bsiv95eRFfXwPf20pHylezi Y1vw==
X-Gm-Message-State: ABuFfojq4kgw9bvyt92nQhj4XwzzyRPBAzFxr3ClWrLD9sguDHrk5Iqb GHGdVPHojN8HN9APYgIeXNEGwkC6ynva6pqIcq0=
X-Google-Smtp-Source: ACcGV61QQhQH7UYY6zB0RyxzmI2AgVqw9QxyGT82auhdf9NwQxBB2vJx85BpwVkiG7GJPYh8MGOi6ZKGdoerrlKOoLM=
X-Received: by 2002:a19:2288:: with SMTP id i130-v6mr9356040lfi.50.1538523099835;  Tue, 02 Oct 2018 16:31:39 -0700 (PDT)
MIME-Version: 1.0
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch>
In-Reply-To: <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Wed, 3 Oct 2018 08:31:28 +0900
Message-ID: <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com>
Subject: Re: a proposed way forward was Re: Spin bit decision
To: Brian Trammell <ietf@trammell.ch>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Lars Eggert <lars@eggert.org>,  IETF QUIC WG <quic@ietf.org>, Mike Bishop <mbishop@evequefou.be>,  Lili Peaudchien <alexandre.ferrieux@orange.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/5dmT_-1pnB4kDOJ-5D4wdvC2IJ0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Oct 2018 23:31:45 -0000

2018=E5=B9=B410=E6=9C=883=E6=97=A5(=E6=B0=B4) 6:11 Brian Trammell (IETF) <i=
etf@trammell.ch>:
>
> hi Ian, all,
>
> Perhaps we can exploit the asymmetry inherent in QUIC (there are servers =
and clients), the spin bit (the server reflects, the client inverts), and t=
he desire to participate or not (ISTM that most of the discussion we've had=
 about opting out have focused on client opt-out, based either on the princ=
iple of the thing and/or a suspicion that the signal is useless) to resolve=
 this discussion.
>
>
> A proposal:
>
> 1. Servers MUST reflect the spin value. Clients MAY treat an unambiguousl=
y detected non-reflected bit as a protocol error.

I oppose to using MUST for the server, because some *servers* might
not be willing to expose the path RTT, for example when it is running
hidden behind a UDP proxy.

I also do not think that maintaining the spin-bit for each
"connection" works. My understanding is that it should be per-5-tuple
because multiple QUIC connections can be coalesced onto single UDP
port on both sides, and because it is impossible for an observer to
track the pair of CIDs identifying the same connection across CID
changes.

I have opened https://github.com/quicwg/base-drafts/issues/1828 to
track the issue.

> 2a. Clients SHOULD invert the spin value, unless [EDNOTE: someone other t=
han me should write convincing reasons for non-implementation here], or the=
 client has been configured not to spin, or to use some other client behavi=
or.
>
> -OR-
>
> 2b. Clients set the spin bit value as they see fit, provided that this be=
havior is consistent per connection ID. In order to provide RTT information=
 to the path, clients MAY invert the spin value (per reference to a separat=
e RFC that looks a lot like draft-tsvwg-quic=3Dspin, to be published by QUI=
C, TSVWG, or IPPM).
>
> 3. Servers and clients MUST NOT expose spin state from one Connection ID =
to another Connection ID.
>
>
> 1 is intended to drive deployment through server defaults. Yes, one can a=
rgue that the protocol error here is artificial (and the proposal explicitl=
y acknowledges that through the client MAY error out), but the client can a=
lways opt out by clamping to a random value per CID.
>
> The 2a variant is essentially a 2119-compliant way of saying "we'd really=
 like it if you implemented the spin bit", leaving the question of client d=
efaults (opt in versus opt out) up to the client implementors.
>
> The 2b variant is designed to allow for future or parallel client-side be=
haviors other than spinning to support different measurement goals. For exa=
mple, using the adaptive square wave proposed for on-path loss measurement =
(by either Mikkel or Kazuho, I believe) at the client with server reflectio=
n would allow accumulation of loss on the upstream as well as the downstrea=
m path, as well as upstream (toward the server) RTT measurement. Obviously,=
 the set of these deployed in the wild would have to be kept small in order=
 to allow a measurement device to heuristically determine which signal was =
in use given a spinbit stream.
>
> 3 prevents spin state from leaking across CIDs, reducing the (already tin=
y but nonzero) linkability surface.
>
> (Obviously, the above needs wordsmithing, but these are the broad lines.)
>
> Cheers,
>
> Brian
>
> > On 2 Oct 2018, at 19:13, Ian Swett <ianswett=3D40google.com@dmarc.ietf.=
org> wrote:
> >
> > One piece of information related to the above discussion is whether det=
ecting who is and is not spinning is easy and reliable.
> >
> > One of my concerns is unintentional mis-use of the signal, and if it ca=
n't be detected reliably in a mixed environment, that means SHOULD is unwis=
e and argues for either not including it or making it a MUST.
> >
> > On Tue, Oct 2, 2018 at 12:51 PM Mike Bishop <mbishop@evequefou.be> wrot=
e:
> > I don=E2=80=99t think it=E2=80=99s a grim view, I think it=E2=80=99s a =
pragmatic view.  Our role is to specify the things which are fundamental to=
 the protocol and have to happen for peers to interoperate.  Mis-using norm=
ative language for other things is an abuse of the process -- that's kind o=
f the point of RFC 6919.
> >
> >
> >
> > RFC 2119 says:
> >
> > In particular, [normative language] MUST only be used where it is actua=
lly required for interoperation or to limit behavior which has potential fo=
r causing harm (e.g., limiting retransmisssions)  For example, they must no=
t be used to try to impose a particular method on implementors where the me=
thod is not required for interoperability.
> >
> >
> >
> > Given that the spin bit is not =E2=80=9Cactually required for interoper=
ation,=E2=80=9D but is the very definition of =E2=80=9Ctry to impose a part=
icular method on implementors,=E2=80=9D I=E2=80=99d say that RFC 2119 imper=
atives are unwarranted.
> >
> >
> >
> > -----Original Message-----
> > From: QUIC <quic-bounces@ietf.org> On Behalf Of alexandre.ferrieux@oran=
ge.com
> > Sent: Tuesday, October 2, 2018 8:05 AM
> > To: Lars Eggert <lars@eggert.org>
> > Cc: IETF QUIC WG <quic@ietf.org>
> > Subject: Re: Spin bit decision
> >
> >
> >
> > On 10/02/18 16:00, Lars Eggert wrote:
> >
> > >
> >
> > > The point I can't seem to be getting across is that irrespective of
> >
> > > what the WG decides to require, there is no penalty for individual
> >
> > > stacks at deployment time (or after) to do whatever they wish, since
> >
> > > the spin bit by design has no impact on protocol operation and intero=
p.
> >
> >
> >
> > It is getting across, but it is a very grim view of the standardization=
 process itself. Are there many examples of MUST in RFCs that turned out to=
 be ignored by implementations just because they were not part of the core =
semantics and hence not enforced by other peers ?
> >
> >
> >
> >
> >
> > _______________________________________________________________________=
__________________________________________________
> >
> >
> >
> > Ce message et ses pieces jointes peuvent contenir des informations conf=
identielles ou privilegiees et ne doivent donc pas etre diffuses, exploites=
 ou copies sans autorisation. Si vous avez recu ce message par erreur, veui=
llez le signaler a l'expediteur et le detruire ainsi que les pieces jointes=
. Les messages electroniques etant susceptibles d'alteration, Orange declin=
e toute responsabilite si ce message a ete altere, deforme ou falsifie. Mer=
ci.
> >
> >
> >
> > 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 b=
een modified, changed or falsified.
> >
> > Thank you.
> >
> >
> >
>


--=20
Kazuho Oku


From nobody Tue Oct  2 18:47:04 2018
Return-Path: <kazuhooku@gmail.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 E7D0E131181 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 18:47:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 7owmfDh8TnG4 for <quic@ietfa.amsl.com>; Tue,  2 Oct 2018 18:47:00 -0700 (PDT)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 59FD9131038 for <quic@ietf.org>; Tue,  2 Oct 2018 18:47:00 -0700 (PDT)
Received: by mail-lf1-x12a.google.com with SMTP id m18-v6so2891733lfl.11 for <quic@ietf.org>; Tue, 02 Oct 2018 18:47:00 -0700 (PDT)
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:content-transfer-encoding; bh=5mhjrRcoOKsfO9hzi6lqXxScVroerNt/1pZrg/1LKx4=; b=YNsj0rWHY0mJWFpHveBOlOhfnoqE+Oa3aTPqhciBn06utTFklU7NiaV7qizsacJcSp QzZrRrJVLcKxyvdyYa4sN/WIgg8kpLLW9YUpI7G4V/H8V3DAjb0js+uq0VxnfjWehhKI qnMRLCY2hdIkNvn0Oq9RFYECdRsZ4pjoU+lIa4p6aaT0lj5Z7cCNJUBRHv7Yj519DLXN 15xLSSSwCpHjPdy0nzVNFMD+Qw7w8sMbUGlWZkatsBf9BsFP+UB3h6F3OkqSC1uTNo9/ /7V28ko/T8CnVHjp7WNtLZKoag+cVHzQFR2jHt1tpY5+rZOw+tlVtJ9JCNXJRO3oAqHZ 5cRg==
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:content-transfer-encoding; bh=5mhjrRcoOKsfO9hzi6lqXxScVroerNt/1pZrg/1LKx4=; b=R1HjcB+hU3/1dzE/tKJslyTVzEZogjGe8mMv+FwtLz9KvvaJ4APNhj5oh76OX60c0d ZIudK7CZS2YCjdssJYZXGONOhXKN6Pic4VpENThwj3L1c347uDxPJzUT0ZBnhHNUG8fN qCuuxEln1sFPw9jj2dZyMX/dmAeLxQz71jCeYGILnTbxEycbQ5FXK6qFc7Y37HLQYSww ZXsOloU7sKTeXsPWDou+9yXDlEfRhAtQP6c2BsJu9QPa5wwD+9/0JKFJ6aAUDnUjnsBc YzMkL1ugFhTxPrTePoFMjfsuNuPv0lEz/vOoOniWa+7CAaDUjwJYcoFM/mSHIzRc0Ats fHgw==
X-Gm-Message-State: ABuFfohUGBmS3nLBksEDVjfH4aULJaASsR4c9e0pAtmyHXhMLcjyGhoy 2kh3EAzTWoT0PYDJRcua5lkaagkTSehf0rYSDiY=
X-Google-Smtp-Source: ACcGV62F4A94GF21iGfjspxVrPZCg6JwO65CKebNi/w4Ya1QghTxB3LvhdZ3BlA+QaU/cSAY1Rln7UEYfg9RXrJvXPU=
X-Received: by 2002:a19:6d0e:: with SMTP id i14-v6mr10126388lfc.57.1538531218340;  Tue, 02 Oct 2018 18:46:58 -0700 (PDT)
MIME-Version: 1.0
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com>
In-Reply-To: <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Wed, 3 Oct 2018 10:46:47 +0900
Message-ID: <CANatvzwmsAfey3SJqsP+fa8JrXe97zexXuCEjUOnOM3ntPoHrg@mail.gmail.com>
Subject: Re: Spin bit decision
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: Mike Bishop <mbishop@evequefou.be>, Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>,  Lili Peaudchien <alexandre.ferrieux@orange.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-H9J7cE32A17kGyB7KYr1LrTEgg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 01:47:03 -0000

2018=E5=B9=B410=E6=9C=883=E6=97=A5(=E6=B0=B4) 2:18 Ian Swett <ianswett=3D40=
google.com@dmarc.ietf.org>:
>
> One piece of information related to the above discussion is whether detec=
ting who is and is not spinning is easy and reliable.

+1.

>From practical standpoint, it is very difficult to design a mechanism
that detects if the peer is not sending false information using the
spin bit. We need to make sure that a middlebox cannot disrupt a
connection by reordering packets, leading an endpoint to believe that
the peer is faking the spin bits. The design needs take care of
multithreaded (or clustered) endpoints sending packets.

I am not against adopting the spin bit proposal, but I strongly prefer
having the possibility to *not* use the spin bits for the endpoints
that want to hide the latency. For example for the endpoints could for
example be behind a NAT or a UDP proxy.

OTOH, I think it is fine to expose a signal that indicates if the spin
bit is turned on. We have an unused bit in the short header :-)

> One of my concerns is unintentional mis-use of the signal, and if it can'=
t be detected reliably in a mixed environment, that means SHOULD is unwise =
and argues for either not including it or making it a MUST.
>
> On Tue, Oct 2, 2018 at 12:51 PM Mike Bishop <mbishop@evequefou.be> wrote:
>>
>> I don=E2=80=99t think it=E2=80=99s a grim view, I think it=E2=80=99s a p=
ragmatic view.  Our role is to specify the things which are fundamental to =
the protocol and have to happen for peers to interoperate.  Mis-using norma=
tive language for other things is an abuse of the process -- that's kind of=
 the point of RFC 6919.
>>
>>
>>
>> RFC 2119 says:
>>
>> In particular, [normative language] MUST only be used where it is actual=
ly required for interoperation or to limit behavior which has potential for=
 causing harm (e.g., limiting retransmisssions)  For example, they must not=
 be used to try to impose a particular method on implementors where the met=
hod is not required for interoperability.
>>
>>
>>
>> Given that the spin bit is not =E2=80=9Cactually required for interopera=
tion,=E2=80=9D but is the very definition of =E2=80=9Ctry to impose a parti=
cular method on implementors,=E2=80=9D I=E2=80=99d say that RFC 2119 impera=
tives are unwarranted.
>>
>>
>>
>> -----Original Message-----
>> From: QUIC <quic-bounces@ietf.org> On Behalf Of alexandre.ferrieux@orang=
e.com
>> Sent: Tuesday, October 2, 2018 8:05 AM
>> To: Lars Eggert <lars@eggert.org>
>> Cc: IETF QUIC WG <quic@ietf.org>
>> Subject: Re: Spin bit decision
>>
>>
>>
>> On 10/02/18 16:00, Lars Eggert wrote:
>>
>> >
>>
>> > The point I can't seem to be getting across is that irrespective of
>>
>> > what the WG decides to require, there is no penalty for individual
>>
>> > stacks at deployment time (or after) to do whatever they wish, since
>>
>> > the spin bit by design has no impact on protocol operation and interop=
.
>>
>>
>>
>> It is getting across, but it is a very grim view of the standardization =
process itself. Are there many examples of MUST in RFCs that turned out to =
be ignored by implementations just because they were not part of the core s=
emantics and hence not enforced by other peers ?
>>
>>
>>
>>
>>
>> ________________________________________________________________________=
_________________________________________________
>>
>>
>>
>> Ce message et ses pieces jointes peuvent contenir des informations confi=
dentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites =
ou copies sans autorisation. Si vous avez recu ce message par erreur, veuil=
lez 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. Merc=
i.
>>
>>
>>
>> This message and its attachments may contain confidential or privileged =
information that may be protected by law; they should not be distributed, u=
sed or copied without authorisation.
>>
>> If you have received this email in error, please notify the sender and d=
elete this message and its attachments.
>>
>> As emails may be altered, Orange is not liable for messages that have be=
en modified, changed or falsified.
>>
>> Thank you.
>>
>>



--=20
Kazuho Oku


From nobody Wed Oct  3 00:32:58 2018
Return-Path: <alexandre.ferrieux@orange.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 C0BCC1310F1 for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 00:32:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.291
X-Spam-Level: 
X-Spam-Status: No, score=-0.291 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 G3z3bJE1dlOA for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 00:32:54 -0700 (PDT)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFB6A1310F8 for <quic@ietf.org>; Wed,  3 Oct 2018 00:32:53 -0700 (PDT)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) by opfednr26.francetelecom.fr (ESMTP service) with ESMTP id 42Q75w16QHz10cT; Wed,  3 Oct 2018 09:32:52 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfednr02.francetelecom.fr (ESMTP service) with ESMTP id 42Q75w0GT6z8sbM; Wed,  3 Oct 2018 09:32:52 +0200 (CEST)
Received: from [10.193.4.89] (10.168.234.4) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 3 Oct 2018 09:32:51 +0200
Subject: Re: a proposed way forward was Re: Spin bit decision
To: Kazuho Oku <kazuhooku@gmail.com>, Brian Trammell <ietf@trammell.ch>
CC: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>, Mike Bishop <mbishop@evequefou.be>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com>
From: <alexandre.ferrieux@orange.com>
Message-ID: <7221_1538551972_5BB470A4_7221_106_1_4a70bd20-3b2e-d4a6-4832-23024e1119f0@orange.com>
Date: Wed, 3 Oct 2018 09:31:10 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: fr-xx-moderne
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.168.234.4]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/tOWDApFsSOtelxQgxJxIKEb8Sks>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 07:32:56 -0000

On 10/03/18 01:31, Kazuho Oku wrote>
> I oppose to using MUST for the server, because some *servers* might not be
> willing to expose the path RTT, for example when it is running hidden behind
> a UDP proxy.

At last a concrete argument, thanks ;)
But why would exposing the RTT be harmful in a NAT/UDP-proxy scenario ?


_________________________________________________________________________________________________________________________

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.


From nobody Wed Oct  3 00:45:22 2018
Return-Path: <mikkelfj@gmail.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 29848131090 for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 00:45:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=unavailable 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 ErIyK-yOff1d for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 00:45:07 -0700 (PDT)
Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (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 802FF1310F8 for <quic@ietf.org>; Wed,  3 Oct 2018 00:45:07 -0700 (PDT)
Received: by mail-ot1-x32d.google.com with SMTP id 36-v6so4595948oth.11 for <quic@ietf.org>; Wed, 03 Oct 2018 00:45:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=ZuhOVtzQNOWTrwfS6xAJpbI8qHx8aEKGUiNuk2Ew8Xg=; b=UeZunMR6ilnziTJ8B48ZFuMYmW5f+KXhsn24Zukwy11dizjsVaWEOnk6QsD/tji5Wy elgA8rN+6gMhji+vJRmX6mLmW2iAASHV6YOnx/6UrAmYZqbnLxfuQQzy4cRuRekC725W Z3KQ1p5c1BPKYtjgkoz8Kw6pxEncqmAIT6ib1uKpjNQVJRcJGYHXK3vBiUhurTAvBUGz kdi/iYa3IkOgKRzpRjyOVmHSW+EGcxYH8enemc+Y9jfUYJoGE2ucgYPG9GEYPxRw9Mek cbeHTVhi8JoQhtXdpPd2DV1pvveB1iUVSGoTwTcmGLfA5XecnHR81PBIjF9XLcuo65jG pimQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=ZuhOVtzQNOWTrwfS6xAJpbI8qHx8aEKGUiNuk2Ew8Xg=; b=rWeT/gJyAk4wsh2E7eq6fP+LimKCnoLcD0TewMET6d2dleG+VGTRYv1uGOLjmNcDte KN8WWcKs0c8dwZQ2DQVvy8hyUV+HHkQOs0sTRXoyMLqZ2RIvApQP4iQmK/u1qrDLaRLg plHs24YjMMQmSp4ML4iy9ul2DjHo5ww5NHwmm9CH7qm+v5X/+X1Zv1DI/hY7H3KIn0UT vCwg0CLlmTeux6BecvfA8PPLyQyuqijKpeeisLP35bl7HV593kVE8GI/xAsTTx8AcKkT cx6Ml2udsHCp6mHHDnpRm3Y7bahJ/c+mbfRrJMk0If+RXObptBiU4RrxKK+V6pW/kVyE FaHg==
X-Gm-Message-State: ABuFfogCs+iY4C6qANOHO2bxQMnlfvoaB0If36M8E0/vx4jmvjI+yitE GAxiZlxUzMpBrEykPEgGA4Di+xf8WT9eUHNEwxA=
X-Google-Smtp-Source: ACcGV63+kWH+V+SwRrter1QyMbOiwBQZS0kLueO468w12GiTNYE5QKfEghhGJzKmTv0DvV7QisBh4wTmiPi9ridoS1s=
X-Received: by 2002:a9d:5809:: with SMTP id r9mr142696oth.36.1538552706862; Wed, 03 Oct 2018 00:45:06 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 3 Oct 2018 00:45:06 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <7221_1538551972_5BB470A4_7221_106_1_4a70bd20-3b2e-d4a6-4832-23024e1119f0@orange.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <7221_1538551972_5BB470A4_7221_106_1_4a70bd20-3b2e-d4a6-4832-23024e1119f0@orange.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Wed, 3 Oct 2018 00:45:06 -0700
Message-ID: <CAN1APddaqCxYr5rZVfd5K_LWMDigcRdhj4CihdCVo3F=NH0idg@mail.gmail.com>
Subject: Re: a proposed way forward was Re: Spin bit decision
To: alexandre.ferrieux@orange.com, Brian Trammell <ietf@trammell.ch>,  Kazuho Oku <kazuhooku@gmail.com>
Cc: Lars Eggert <lars@eggert.org>, Mike Bishop <mbishop@evequefou.be>, IETF QUIC WG <quic@ietf.org>,  Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008f962505774e37e5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-n4848iFbmCeolyI4i62kGK8VaU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 07:45:11 -0000

--0000000000008f962505774e37e5
Content-Type: text/plain; charset="UTF-8"

At last a concrete argument, thanks ;)
But why would exposing the RTT be harmful in a NAT/UDP-proxy scenario ?

Great firewall censorship. VPN proxy to bypass streaming restrictions by
country. Hackers that proxy traffic via a legitimate cooperation. Internet
access providers prioritising local traffic. High latency onion routing
traffic.





_________________________________________________________________________________________________________________________


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.

--0000000000008f962505774e37e5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div> <div><blo=
ckquote type=3D"cite" class=3D"clean_bq" style=3D"font-family:Helvetica,Ari=
al;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:no=
rmal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:=
none;white-space:normal;word-spacing:0px;text-decoration:none"><span><div><=
div>At last a concrete argument, thanks ;)<span class=3D"Apple-converted-sp=
ace">=C2=A0</span><br>But why would exposing the RTT be harmful in a NAT/UD=
P-proxy scenario ?<span class=3D"Apple-converted-space">=C2=A0</span></div>=
</div></span></blockquote></div><p>Great firewall censorship. VPN proxy to =
bypass streaming restrictions by country. Hackers that proxy traffic via a =
legitimate cooperation. Internet access providers prioritising local traffi=
c. High latency onion routing traffic.</p><p><br></p><div><blockquote type=
=3D"cite" class=3D"clean_bq" style=3D"font-family:Helvetica,Arial;font-size=
:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-=
spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-s=
pace:normal;word-spacing:0px;text-decoration:none"><span><div><div><br><br>=
<br>_______________________________________________________________________=
__________________________________________________<span class=3D"Apple-conv=
erted-space">=C2=A0</span><br><br>Ce message et ses pieces jointes peuvent =
contenir des informations confidentielles ou privilegiees et ne doivent don=
c<span class=3D"Apple-converted-space">=C2=A0</span><br>pas etre diffuses, =
exploites ou copies sans autorisation. Si vous avez recu ce message par err=
eur, veuillez le signaler<span class=3D"Apple-converted-space">=C2=A0</span=
><br>a l&#39;expediteur et le detruire ainsi que les pieces jointes. Les me=
ssages electroniques etant susceptibles d&#39;alteration,<span class=3D"App=
le-converted-space">=C2=A0</span><br>Orange decline toute responsabilite si=
 ce message a ete altere, deforme ou falsifie. Merci.<span class=3D"Apple-c=
onverted-space">=C2=A0</span><br><br>This message and its attachments may c=
ontain confidential or privileged information that may be protected by law;=
<span class=3D"Apple-converted-space">=C2=A0</span><br>they should not be d=
istributed, used or copied without authorisation.<span class=3D"Apple-conve=
rted-space">=C2=A0</span><br>If you have received this email in error, plea=
se notify the sender and delete this message and its attachments.<span clas=
s=3D"Apple-converted-space">=C2=A0</span><br>As emails may be altered, Oran=
ge is not liable for messages that have been modified, changed or falsified=
.<span class=3D"Apple-converted-space">=C2=A0</span><br>Thank you.<span cla=
ss=3D"Apple-converted-space">=C2=A0</span><br><br></div></div></span></bloc=
kquote></div></body></html>

--0000000000008f962505774e37e5--


From nobody Wed Oct  3 00:58:12 2018
Return-Path: <ietf@trammell.ch>
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 72A901311EA for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 00:58:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 okUi8e5dG-KV for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 00:58:05 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [212.25.24.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73B89131090 for <quic@ietf.org>; Wed,  3 Oct 2018 00:58:05 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id A5D31341C50; Wed,  3 Oct 2018 09:58:03 +0200 (CEST)
X-Iway-Path: 0
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/14501.21294); Wed,  3 Oct 2018 09:58:02 +0200 (CEST)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Wed,  3 Oct 2018 09:58:02 +0200 (CEST)
Received: from [145.14.214.39] (account ietf@trammell.ch HELO [10.11.33.5]) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 69170760; Wed, 03 Oct 2018 09:58:02 +0200
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_33B68A7D-2258-4E63-A5C8-14CF8FCB5EAC"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: a proposed way forward was Re: Spin bit decision
Date: Wed, 3 Oct 2018 09:58:01 +0200
In-Reply-To: <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>, Mike Bishop <mbishop@evequefou.be>, Lili Peaudchien <alexandre.ferrieux@orange.com>
To: Kazuho Oku <kazuhooku@gmail.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/_zcNTqjEk4Db_Q7hTfnSEF7ZsY4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 07:58:10 -0000

--Apple-Mail=_33B68A7D-2258-4E63-A5C8-14CF8FCB5EAC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

hi Kazuho,

> On 3 Oct 2018, at 01:31, Kazuho Oku <kazuhooku@gmail.com> wrote:
>=20
> 2018=E5=B9=B410=E6=9C=883=E6=97=A5(=E6=B0=B4) 6:11 Brian Trammell =
(IETF) <ietf@trammell.ch>:
>>=20
>> hi Ian, all,
>>=20
>> Perhaps we can exploit the asymmetry inherent in QUIC (there are =
servers and clients), the spin bit (the server reflects, the client =
inverts), and the desire to participate or not (ISTM that most of the =
discussion we've had about opting out have focused on client opt-out, =
based either on the principle of the thing and/or a suspicion that the =
signal is useless) to resolve this discussion.
>>=20
>>=20
>> A proposal:
>>=20
>> 1. Servers MUST reflect the spin value. Clients MAY treat an =
unambiguously detected non-reflected bit as a protocol error.
>=20
> I oppose to using MUST for the server, because some *servers* might
> not be willing to expose the path RTT, for example when it is running
> hidden behind a UDP proxy.

s/MUST/SHOULD, unless.../ is an acceptable change, as long as we have a =
nice tight box around the unless. The tradeoff is that every caveat we =
put on the server-side reduces server-side deployment, which reduces the =
chances that a cooperating server and a cooperating client meet up.

I'm also quite sympathetic to Marten's argument that "server" and =
"client" are more arbitrary in P2P situations. However, the asymmetry of =
the spinbit is pretty far down the list of asymmetries (stream handling, =
handshake, TLS certs, etc) that I'd want to see optionally addressed in =
a QUIC version i2 (is this the terminology we're using now?)

Backing off the MUST for now for such situations is IMO a good tradeoff, =
though, especially since we only need fractions of a percent of =
deployment to start seeing useful signal for baseline/anomaly =
measurement of large aggregates.

> I also do not think that maintaining the spin-bit for each
> "connection" works. My understanding is that it should be per-5-tuple
> because multiple QUIC connections can be coalesced onto single UDP
> port on both sides, and because it is impossible for an observer to
> track the pair of CIDs identifying the same connection across CID
> changes.

Well, it should be per 5-tuple, but it should also change when CIDs =
change. Dumping state on any CID change is the easiest way I know to =
break linkability, and the most obvious way to do this when you have CID =
concurrency is to keep state per CID.

That might be too far into the implementation weeds for the spec =
though... the language needs to be clear (and clearer than in my initial =
proposal, which is one reason that's a list message and not a PR ;) )

> I have opened https://github.com/quicwg/base-drafts/issues/1828 to
> track the issue.

Thanks, will follow discussion there as well.

Cheers,

Brian


>=20
>> 2a. Clients SHOULD invert the spin value, unless [EDNOTE: someone =
other than me should write convincing reasons for non-implementation =
here], or the client has been configured not to spin, or to use some =
other client behavior.
>>=20
>> -OR-
>>=20
>> 2b. Clients set the spin bit value as they see fit, provided that =
this behavior is consistent per connection ID. In order to provide RTT =
information to the path, clients MAY invert the spin value (per =
reference to a separate RFC that looks a lot like draft-tsvwg-quic=3Dspin,=
 to be published by QUIC, TSVWG, or IPPM).
>>=20
>> 3. Servers and clients MUST NOT expose spin state from one Connection =
ID to another Connection ID.
>>=20
>>=20
>> 1 is intended to drive deployment through server defaults. Yes, one =
can argue that the protocol error here is artificial (and the proposal =
explicitly acknowledges that through the client MAY error out), but the =
client can always opt out by clamping to a random value per CID.
>>=20
>> The 2a variant is essentially a 2119-compliant way of saying "we'd =
really like it if you implemented the spin bit", leaving the question of =
client defaults (opt in versus opt out) up to the client implementors.
>>=20
>> The 2b variant is designed to allow for future or parallel =
client-side behaviors other than spinning to support different =
measurement goals. For example, using the adaptive square wave proposed =
for on-path loss measurement (by either Mikkel or Kazuho, I believe) at =
the client with server reflection would allow accumulation of loss on =
the upstream as well as the downstream path, as well as upstream (toward =
the server) RTT measurement. Obviously, the set of these deployed in the =
wild would have to be kept small in order to allow a measurement device =
to heuristically determine which signal was in use given a spinbit =
stream.
>>=20
>> 3 prevents spin state from leaking across CIDs, reducing the (already =
tiny but nonzero) linkability surface.
>>=20
>> (Obviously, the above needs wordsmithing, but these are the broad =
lines.)
>>=20
>> Cheers,
>>=20
>> Brian
>>=20
>>> On 2 Oct 2018, at 19:13, Ian Swett =
<ianswett=3D40google.com@dmarc.ietf.org> wrote:
>>>=20
>>> One piece of information related to the above discussion is whether =
detecting who is and is not spinning is easy and reliable.
>>>=20
>>> One of my concerns is unintentional mis-use of the signal, and if it =
can't be detected reliably in a mixed environment, that means SHOULD is =
unwise and argues for either not including it or making it a MUST.
>>>=20
>>> On Tue, Oct 2, 2018 at 12:51 PM Mike Bishop <mbishop@evequefou.be> =
wrote:
>>> I don=E2=80=99t think it=E2=80=99s a grim view, I think it=E2=80=99s =
a pragmatic view.  Our role is to specify the things which are =
fundamental to the protocol and have to happen for peers to =
interoperate.  Mis-using normative language for other things is an abuse =
of the process -- that's kind of the point of RFC 6919.
>>>=20
>>>=20
>>>=20
>>> RFC 2119 says:
>>>=20
>>> In particular, [normative language] MUST only be used where it is =
actually required for interoperation or to limit behavior which has =
potential for causing harm (e.g., limiting retransmisssions)  For =
example, they must not be used to try to impose a particular method on =
implementors where the method is not required for interoperability.
>>>=20
>>>=20
>>>=20
>>> Given that the spin bit is not =E2=80=9Cactually required for =
interoperation,=E2=80=9D but is the very definition of =E2=80=9Ctry to =
impose a particular method on implementors,=E2=80=9D I=E2=80=99d say =
that RFC 2119 imperatives are unwarranted.
>>>=20
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: QUIC <quic-bounces@ietf.org> On Behalf Of =
alexandre.ferrieux@orange.com
>>> Sent: Tuesday, October 2, 2018 8:05 AM
>>> To: Lars Eggert <lars@eggert.org>
>>> Cc: IETF QUIC WG <quic@ietf.org>
>>> Subject: Re: Spin bit decision
>>>=20
>>>=20
>>>=20
>>> On 10/02/18 16:00, Lars Eggert wrote:
>>>=20
>>>>=20
>>>=20
>>>> The point I can't seem to be getting across is that irrespective of
>>>=20
>>>> what the WG decides to require, there is no penalty for individual
>>>=20
>>>> stacks at deployment time (or after) to do whatever they wish, =
since
>>>=20
>>>> the spin bit by design has no impact on protocol operation and =
interop.
>>>=20
>>>=20
>>>=20
>>> It is getting across, but it is a very grim view of the =
standardization process itself. Are there many examples of MUST in RFCs =
that turned out to be ignored by implementations just because they were =
not part of the core semantics and hence not enforced by other peers ?
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>> =
__________________________________________________________________________=
_______________________________________________
>>>=20
>>>=20
>>>=20
>>> 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.
>>>=20
>>>=20
>>>=20
>>> 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.
>>>=20
>>> If you have received this email in error, please notify the sender =
and delete this message and its attachments.
>>>=20
>>> As emails may be altered, Orange is not liable for messages that =
have been modified, changed or falsified.
>>>=20
>>> Thank you.
>>>=20
>>>=20
>>>=20
>>=20
>=20
>=20
> --
> Kazuho Oku


--Apple-Mail=_33B68A7D-2258-4E63-A5C8-14CF8FCB5EAC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAlu0dokACgkQihK3vwvq
RqO8Aw//aiWxBs/O6yfElQlThnKxdM3y8225yIP4UnEQV6SKQbSCn7hX390V28yv
punzqKlYSAJ/dZ4KVTLVwNuKRA9qUEDjRyj60aOIpZSMss6RIVOlSCSH/zFcl/vy
BsCAoHs0bVPQyF/MAm8DLyXW6oNmdqHOae4Z7YQXglkqIk5wwVAGNHsTYbelOZHN
534vqaYbgf2WwUl5FhwoOyFPbE5Ih16LmLsY5LFzf4E9xAm1kXALT8BmjBSSkXWF
pYyJ4SBU+w3WT3S0BFlEQKTqU/sBjTiJSa3LvrZ9/EOYJJo36XN/HycRmdH4ux6q
jIVlNXbgItDVmelGDy0L7FZU3p/fZadk7R/IOpRJKgsITD6zc1R7SFDzhr35qHPe
VqUMT3tyapuZj717ViCemanyhn1GmkP5kOwDvGpunPHrntAoN6o5O1ft4I5KyX0K
TR8EyDyIZOargIUvPucQ2x/Cs6hmW7W2b66MlTE0D4G8N8jgl0G9mpDROVQ3dQ45
fTbZGgB059JzWckngKxRN5J/hCJdkQOJIAMKQyO7OI5yU+jG6xq01Wz0TgvTwlDI
ZNRPx781R2fKiveq4Wq0mdRmvXF7p/UqYpuxMUK9qaa6Siu7x0OtO6eAolDzyV2S
SkqJJW4UJVRrAGi1EJUgeDkP41cHwp44U9EL/zRgaoyPnrWvznI=
=s/GB
-----END PGP SIGNATURE-----

--Apple-Mail=_33B68A7D-2258-4E63-A5C8-14CF8FCB5EAC--


From nobody Wed Oct  3 00:58:29 2018
Return-Path: <ietf@trammell.ch>
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 814BD13123E for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 00:58:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 bILDMQvFXctV for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 00:58:13 -0700 (PDT)
Received: from grape.iway.ch (grape.iway.ch [83.150.31.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F36D131232 for <quic@ietf.org>; Wed,  3 Oct 2018 00:58:13 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [212.25.24.36]) by grape.iway.ch (Postfix) with ESMTP id BA889341C54; Wed,  3 Oct 2018 09:58:11 +0200 (CEST)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id AFB3A341C52; Wed,  3 Oct 2018 09:58:11 +0200 (CEST)
X-iWay-Transport: alternative
X-Iway-Path: 1
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/14501.21294); Wed,  3 Oct 2018 09:58:11 +0200 (CEST)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Wed,  3 Oct 2018 09:58:11 +0200 (CEST)
Received: from [145.14.214.39] (account ietf@trammell.ch HELO [10.11.33.5]) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 69170782; Wed, 03 Oct 2018 09:58:11 +0200
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <055E2627-9D6C-45E8-8130-069B4891D24C@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_5F79E5D2-99ED-4A16-90D6-E339A6651DC0"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: a proposed way forward was Re: Spin bit decision
Date: Wed, 3 Oct 2018 09:58:11 +0200
In-Reply-To: <CAN1APddaqCxYr5rZVfd5K_LWMDigcRdhj4CihdCVo3F=NH0idg@mail.gmail.com>
Cc: alexandre.ferrieux@orange.com, Kazuho Oku <kazuhooku@gmail.com>, Lars Eggert <lars@eggert.org>, Mike Bishop <mbishop@evequefou.be>, IETF QUIC WG <quic@ietf.org>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
To: =?utf-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <7221_1538551972_5BB470A4_7221_106_1_4a70bd20-3b2e-d4a6-4832-23024e1119f0@orange.com> <CAN1APddaqCxYr5rZVfd5K_LWMDigcRdhj4CihdCVo3F=NH0idg@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/vhwjeFErQZteCujbgatMzLXYvf8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 07:58:28 -0000

--Apple-Mail=_5F79E5D2-99ED-4A16-90D6-E339A6651DC0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

hi Mikkel,

I think we're having trouble with the many meanings of the word "proxy" =
here. It can mean at least three things in this context, each of which =
has different implications for RTT measurement:

(1) Web proxying. The web proxy terminates transport connections, and as =
such the spin bit would only expose the RTT on the segment between the =
proxy and its Internet-side peer. Since the whole point of the proxy =
from a privacy standpoint is to make traffic look like it's coming from =
the proxy, exposing this RTT is not an issue.

(2) Transport-terminating proxying. Here the proxying happens at the =
stream, as opposed to the request level. For spin bit measurement, this =
is equivalent to (1) above. (Note that this is widely deployed for TCP =
in the form of transparent back-to-back proxies, which won't work in =
QUIC since the security association protecting the transport is =
end-to-end.)

(3) Proxy-via-NAT. Here the proxy simply rewrites UDP addresses; in this =
case, since the transport association is not terminated, the spin bit =
will expose full end-to-end RTT. Indeed, in this case, endpoints may =
want to disable RTT measurement.

> On 3 Oct 2018, at 09:45, Mikkel Fahn=C3=B8e J=C3=B8rgensen =
<mikkelfj@gmail.com> wrote:
>=20
>>=20
>> At last a concrete argument, thanks ;)
>> But why would exposing the RTT be harmful in a NAT/UDP-proxy scenario =
?
> Great firewall censorship.

Say more here? I don't see the relevance.

> VPN proxy to bypass streaming restrictions by country.

AFAIK most/all of these are of type (1) and (2), so not relevant to the =
discussion.

> Hackers that proxy traffic via a legitimate cooperation.

For web traffic, at least, this would probably be of type (1).

> Internet access providers prioritising local traffic.

This can and always will be done via other identifiers, so even if RTT =
is exposed here, it is of limited utility/threat (depending on which =
team you're rooting for).

> High latency onion routing traffic.

Necessarily always terminates transport. However, the fundamental design =
properties of circuit-based anonymity systems do mean that if you're =
doing something like running a VPN tunnel over ToR (for.. some reason?), =
then you should turn off the spin bit for traffic within that tunnel. =
Client opt-outs seem to be mostly sufficient for this, though.

Cheers,

Brian


>=20
>>=20
>>=20
>>=20
>> =
__________________________________________________________________________=
_______________________________________________
>>=20
>> 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.
>>=20
>> 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.


--Apple-Mail=_5F79E5D2-99ED-4A16-90D6-E339A6651DC0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAlu0dpMACgkQihK3vwvq
RqN7TA/7Bg0bLBTyhhcuxYWk4nC472wZLdVzjAl5AxSuhzRSpVEiml7ZWQR60Q8w
GSTw1wrmcSD1dIOA/BiWAfwLQHHUlD1exMP4VeJRvU1Zc7/qMtGC4M5kY0a4pa8B
Ke771d8hWyr6jEDIlMJsh49+OLD2SwR4W6UI+Yad4wUy/zCeec/XydM5r3wN+4KO
vUupGktNq1djA2CEamSX4xqkbjiO1wRruXhkcADQv05mESmzOq/DK4UHP1tSSKUO
Y+PYQUKAVx6a0cxUT8iQfBRMmuvM1AC+BmUG8UugHUNv6qnepOf71uuUg20TDVoR
QHLpAjASFbWofAJda3CvIAoaPYfv3jlVxE01j1eJss53E1YuS0NUcPwSOrgG+MRg
M72eDtsUM9/MSqR0ed+J2qHM/Rk0EjJGPpz4qyxwbv5uF8o6ai9AyFabIX7afB1X
0JaxsD9r3BQTwOwprcyvVg9SarB5tg2QqLH+uifc67RLxAdnR7QAPBTPi+pj15aa
h9eaojKQD9c2CQCiUpqy/uEKZA3/vrn/jj4PVMF9vRfUW4tPj7/ain5A6pmk0jNO
Zdiq1pp76BO5UbPb6Gd1pwvKaI0FGbZi9pwUbGCy0BHLgHzdFJ/5cX4Uh5X+YxOq
xX2upszR1GCgLmj/JmSF7sAykyMp0uuJv625AEtU6DPFT5PeUhg=
=14mt
-----END PGP SIGNATURE-----

--Apple-Mail=_5F79E5D2-99ED-4A16-90D6-E339A6651DC0--


From nobody Wed Oct  3 01:18:38 2018
Return-Path: <mikkelfj@gmail.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 02E5E1311FF for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 01:18:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 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_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 izDpY1mTE7V2 for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 01:18:33 -0700 (PDT)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (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 AF5D0131090 for <quic@ietf.org>; Wed,  3 Oct 2018 01:18:33 -0700 (PDT)
Received: by mail-ot1-x32a.google.com with SMTP id h26-v6so4688281otl.9 for <quic@ietf.org>; Wed, 03 Oct 2018 01:18:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=VK58pB6+/qWOkL9DRsIM72+ZMSdTbcFljWPOY9ELVMc=; b=pSZiqn1btfhR/rMni2nhN7WV+aUIUjYJZ480IEsWzAZzgqBkZHj3DWHYhnvcKSf/CU wFXFuum3AQSoOrJ0O19e3cLc+Nb6E0bb6Pw2BsXjIgjlG8nvZNfm8shsOstsllan8cgk 2gLTXPv1J5jkrSo9MUZszSbqdWvCjT8OtLBzgUrdczFY8rHpEDFP8bic4pLLolGG4X/L Ph0dwMUnI59fmGx7rmiR7gE/HuGc1oo+NOc3/Gbpjyjo67d3NfX7niqJdN2gWMetUAlR /OErjQBvkTPQClueJk4F2Bu46kTHBxMC9zjEaYHjMtMEr1F+7dlwpf5O5JsyzHMalXRp Fq3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=VK58pB6+/qWOkL9DRsIM72+ZMSdTbcFljWPOY9ELVMc=; b=L25oY1ZHWsXqJAFcDyxo6KYEkEutCmWbqZwYZe0sxuDgruZduQSpD3ILPcjYId3fVS ighSI1aLrnWJUs3G9CFG83RmWysYUSVOobr2Xx+znbYfFTZU7XfYPWwirxbkQH4uyGcn PGJxKvSBIHlZw2LdVYh65okB6qJvQDGJwiKKsZJ6+GZ8OJ5O2kcUm599dwzVLAJroud4 GdUmj+k6ffa8+ogH2lZt8ZBpi8QqIVw1fPljquV9iWboTvfI4PuX03iMhMGkVOy+oLQ3 FSOYIX3vo3WaSSJx/cpSIMLq4egwykuAPWNyDMIgGsRILa7U3Xkyvws/6TFFpPkFuIDe r6TQ==
X-Gm-Message-State: ABuFfojJM8QPl6gjhMPzOo3r7PY/KV96ooV+xh5DsujPN2jO4osMYulL Mi5w0ccVp//Uv8zwUX+xOZZXmDcGU5JWBZsP40g=
X-Google-Smtp-Source: ACcGV63cxYIB0XOls18Rkbe/2rPH2bc6R/6ol20k7csCZXAV0rFWU+fR9gxgejx7hWeyPOSZhwVdrFMSColmITAo5O0=
X-Received: by 2002:a9d:429a:: with SMTP id r26mr188961ote.337.1538554713094;  Wed, 03 Oct 2018 01:18:33 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 3 Oct 2018 01:18:32 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <055E2627-9D6C-45E8-8130-069B4891D24C@trammell.ch>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <7221_1538551972_5BB470A4_7221_106_1_4a70bd20-3b2e-d4a6-4832-23024e1119f0@orange.com> <CAN1APddaqCxYr5rZVfd5K_LWMDigcRdhj4CihdCVo3F=NH0idg@mail.gmail.com> <055E2627-9D6C-45E8-8130-069B4891D24C@trammell.ch>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Wed, 3 Oct 2018 01:18:32 -0700
Message-ID: <CAN1APdfY_7gxYmMnG-RX4TMeCMeepxJwJGfu-9xVt1drjQzHSA@mail.gmail.com>
Subject: Re: a proposed way forward was Re: Spin bit decision
To: "Brian Trammell (IETF)" <ietf@trammell.ch>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Lars Eggert <lars@eggert.org>,  Mike Bishop <mbishop@evequefou.be>, IETF QUIC WG <quic@ietf.org>, alexandre.ferrieux@orange.com, Kazuho Oku <kazuhooku@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000243d7105774eafe0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/oqoM7QueKtMKLCkVxmRENIcAeic>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 08:18:37 -0000

--000000000000243d7105774eafe0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

You are right that there are other obstacles to prevent detection that just
RTT.

You can imagine an alternative DNS service and router system that send
traffic in one direction and then forwards traffic into the general
backbone. So you have a person in Asia connect to a US university that has
router that forwards packets out into the general internet without
terminating anything as a sort of extended NAT box. I might be missing
something here, but that is my train of thoughts. The latency is not hiding
the distance between the two continents but it can reveal detectable
anomalies in traffic. More generally, you could apply machine learning to
RTT - or to any other observable parameter.

I=E2=80=99m not really against the spin bit and I agree that there are ofte=
n better
ways to achieve such attacks, but dropping the spin bit is a really easy
first line of defence. Hence, for the cases I listed you cannot expect
cooperation on the spin bit even if the attack is unlikely.


On 3 October 2018 at 09.58.12, Brian Trammell (IETF) (ietf@trammell.ch)
wrote:

hi Mikkel,

I think we're having trouble with the many meanings of the word "proxy"
here. It can mean at least three things in this context, each of which has
different implications for RTT measurement:

(1) Web proxying. The web proxy terminates transport connections, and as
such the spin bit would only expose the RTT on the segment between the
proxy and its Internet-side peer. Since the whole point of the proxy from a
privacy standpoint is to make traffic look like it's coming from the proxy,
exposing this RTT is not an issue.

(2) Transport-terminating proxying. Here the proxying happens at the
stream, as opposed to the request level. For spin bit measurement, this is
equivalent to (1) above. (Note that this is widely deployed for TCP in the
form of transparent back-to-back proxies, which won't work in QUIC since
the security association protecting the transport is end-to-end.)

(3) Proxy-via-NAT. Here the proxy simply rewrites UDP addresses; in this
case, since the transport association is not terminated, the spin bit will
expose full end-to-end RTT. Indeed, in this case, endpoints may want to
disable RTT measurement.

> On 3 Oct 2018, at 09:45, Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@gmai=
l.com>
wrote:
>
>>
>> At last a concrete argument, thanks ;)
>> But why would exposing the RTT be harmful in a NAT/UDP-proxy scenario ?
> Great firewall censorship.

Say more here? I don't see the relevance.

> VPN proxy to bypass streaming restrictions by country.

AFAIK most/all of these are of type (1) and (2), so not relevant to the
discussion.

> Hackers that proxy traffic via a legitimate cooperation.

For web traffic, at least, this would probably be of type (1).

> Internet access providers prioritising local traffic.

This can and always will be done via other identifiers, so even if RTT is
exposed here, it is of limited utility/threat (depending on which team
you're rooting for).

> High latency onion routing traffic.

Necessarily always terminates transport. However, the fundamental design
properties of circuit-based anonymity systems do mean that if you're doing
something like running a VPN tunnel over ToR (for.. some reason?), then you
should turn off the spin bit for traffic within that tunnel. Client
opt-outs seem to be mostly sufficient for this, though.

Cheers,

Brian


>
>>
>>
>>
>>
___________________________________________________________________________=
______________________________________________

>>
>> 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.

--000000000000243d7105774eafe0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">You are right that t=
here are other obstacles to prevent detection that just RTT.</div><div id=
=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;c=
olor:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id=3D"bloo=
p_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;color:rgb=
a(0,0,0,1.0);margin:0px;line-height:auto">You can imagine an alternative DN=
S service and router system that send traffic in one direction and then for=
wards traffic into the general backbone. So you have a person in Asia conne=
ct to a US university that has router that forwards packets out into the ge=
neral internet without terminating anything as a sort of extended NAT box. =
I might be missing something here, but that is my train of thoughts. The la=
tency is not hiding the distance between the two continents but it can reve=
al detectable anomalies in traffic. More generally, you could apply machine=
 learning to RTT - or to any other observable parameter.</div><div id=3D"bl=
oop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;color:r=
gba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id=3D"bloop_cust=
omfont" style=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,=
0,1.0);margin:0px;line-height:auto">I=E2=80=99m not really against the spin=
 bit and I agree that there are often better ways to achieve such attacks, =
but dropping the spin bit is a really easy first line of defence. Hence, fo=
r the cases I listed you cannot expect cooperation on the spin bit even if =
the attack is unlikely.</div><div id=3D"bloop_customfont" style=3D"font-fam=
ily:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-he=
ight:auto"><br></div> <br><p class=3D"airmail_on">On 3 October 2018 at 09.5=
8.12, Brian Trammell (IETF) (<a href=3D"mailto:ietf@trammell.ch">ietf@tramm=
ell.ch</a>) wrote:</p> <blockquote type=3D"cite" class=3D"clean_bq"><span><=
div><div></div><div>hi Mikkel,
<br>
<br>I think we&#39;re having trouble with the many meanings of the word &qu=
ot;proxy&quot; here. It can mean at least three things in this context, eac=
h of which has different implications for RTT measurement:
<br>
<br>(1) Web proxying. The web proxy terminates transport connections, and a=
s such the spin bit would only expose the RTT on the segment between the pr=
oxy and its Internet-side peer. Since the whole point of the proxy from a p=
rivacy standpoint is to make traffic look like it&#39;s coming from the pro=
xy, exposing this RTT is not an issue.
<br>
<br>(2) Transport-terminating proxying. Here the proxying happens at the st=
ream, as opposed to the request level. For spin bit measurement, this is eq=
uivalent to (1) above. (Note that this is widely deployed for TCP in the fo=
rm of transparent back-to-back proxies, which won&#39;t work in QUIC since =
the security association protecting the transport is end-to-end.)
<br>
<br>(3) Proxy-via-NAT. Here the proxy simply rewrites UDP addresses; in thi=
s case, since the transport association is not terminated, the spin bit wil=
l expose full end-to-end RTT. Indeed, in this case, endpoints may want to d=
isable RTT measurement.
<br>
<br>&gt; On 3 Oct 2018, at 09:45, Mikkel Fahn=C3=B8e J=C3=B8rgensen &lt;<a =
href=3D"mailto:mikkelfj@gmail.com">mikkelfj@gmail.com</a>&gt; wrote:
<br>&gt; =20
<br>&gt;&gt; =20
<br>&gt;&gt; At last a concrete argument, thanks ;)
<br>&gt;&gt; But why would exposing the RTT be harmful in a NAT/UDP-proxy s=
cenario ?
<br>&gt; Great firewall censorship.
<br>
<br>Say more here? I don&#39;t see the relevance.
<br>
<br>&gt; VPN proxy to bypass streaming restrictions by country.
<br>
<br>AFAIK most/all of these are of type (1) and (2), so not relevant to the=
 discussion.
<br>
<br>&gt; Hackers that proxy traffic via a legitimate cooperation.
<br>
<br>For web traffic, at least, this would probably be of type (1).
<br>
<br>&gt; Internet access providers prioritising local traffic.
<br>
<br>This can and always will be done via other identifiers, so even if RTT =
is exposed here, it is of limited utility/threat (depending on which team y=
ou&#39;re rooting for).
<br>
<br>&gt; High latency onion routing traffic.
<br>
<br>Necessarily always terminates transport. However, the fundamental desig=
n properties of circuit-based anonymity systems do mean that if you&#39;re =
doing something like running a VPN tunnel over ToR (for.. some reason?), th=
en you should turn off the spin bit for traffic within that tunnel. Client =
opt-outs seem to be mostly sufficient for this, though.
<br>
<br>Cheers,
<br>
<br>Brian
<br>
<br>
<br>&gt; =20
<br>&gt;&gt; =20
<br>&gt;&gt; =20
<br>&gt;&gt; =20
<br>&gt;&gt; ______________________________________________________________=
___________________________________________________________
<br>&gt;&gt; =20
<br>&gt;&gt; Ce message et ses pieces jointes peuvent contenir des informat=
ions confidentielles ou privilegiees et ne doivent donc
<br>&gt;&gt; pas etre diffuses, exploites ou copies sans autorisation. Si v=
ous avez recu ce message par erreur, veuillez le signaler
<br>&gt;&gt; a l&#39;expediteur et le detruire ainsi que les pieces jointes=
. Les messages electroniques etant susceptibles d&#39;alteration,
<br>&gt;&gt; Orange decline toute responsabilite si ce message a ete altere=
, deforme ou falsifie. Merci.
<br>&gt;&gt; =20
<br>&gt;&gt; This message and its attachments may contain confidential or p=
rivileged information that may be protected by law;
<br>&gt;&gt; they should not be distributed, used or copied without authori=
sation.
<br>&gt;&gt; If you have received this email in error, please notify the se=
nder and delete this message and its attachments.
<br>&gt;&gt; As emails may be altered, Orange is not liable for messages th=
at have been modified, changed or falsified.
<br>&gt;&gt; Thank you.
<br>
<br></div></div></span></blockquote></body></html>

--000000000000243d7105774eafe0--


From nobody Wed Oct  3 01:38:36 2018
Return-Path: <Lucas.Pardue@bbc.co.uk>
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 427AE131215 for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 01:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 3sSCYRnvEFs6 for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 01:38:32 -0700 (PDT)
Received: from mailout0.cwwtf.bbc.co.uk (mailout0.cwwtf.bbc.co.uk [132.185.160.179]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8821813117E for <quic@ietf.org>; Wed,  3 Oct 2018 01:38:32 -0700 (PDT)
Received: from BGB01XI1009.national.core.bbc.co.uk (bgb01xi1009.national.core.bbc.co.uk [10.161.14.23]) by mailout0.cwwtf.bbc.co.uk (8.15.2/8.15.2) with ESMTP id w938cPDe003575; Wed, 3 Oct 2018 09:38:25 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1009.national.core.bbc.co.uk ([10.161.14.23]) with mapi id 14.03.0408.000; Wed, 3 Oct 2018 09:38:24 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: "Brian Trammell (IETF)" <ietf@trammell.ch>, =?iso-8859-1?Q?Mikkel_Fahn=F8e_J=F8rgensen?= <mikkelfj@gmail.com>
CC: "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, "Mike Bishop" <mbishop@evequefou.be>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Lars Eggert <lars@eggert.org>, "IETF QUIC WG" <quic@ietf.org>, Kazuho Oku <kazuhooku@gmail.com>
Subject: RE: a proposed way forward was Re: Spin bit decision
Thread-Topic: a proposed way forward was Re: Spin bit decision
Thread-Index: AQHUWhYuY5uphqKTlk+gydAimQZJXKULc8WAgAAbJICAACozgIAAHI2AgAAD5ACAAAMhAIAADuGAgAASIwCAAB1uAIAABnqAgABCOICAACdTAIAAhgcAgAAD5ACAAAOogIAAGLUI
Date: Wed, 3 Oct 2018 08:38:24 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BBB00DA@bgb01xud1012>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <7221_1538551972_5BB470A4_7221_106_1_4a70bd20-3b2e-d4a6-4832-23024e1119f0@orange.com> <CAN1APddaqCxYr5rZVfd5K_LWMDigcRdhj4CihdCVo3F=NH0idg@mail.gmail.com>, <055E2627-9D6C-45E8-8130-069B4891D24C@trammell.ch>
In-Reply-To: <055E2627-9D6C-45E8-8130-069B4891D24C@trammell.ch>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.19.161.212]
x-exclaimer-md-config: 1cd3ac1c-62e5-43f2-8404-6b688271c769
x-tm-as-product-ver: SMEX-12.5.0.1300-8.2.1013-24054.007
x-tm-as-result: No-37.705300-8.000000-10
x-tmase-matchedrid: pS5owHKhBO27lpQUW6Uvz7iMC5wdwKqdwZLXS0hN8p20Vg+MnSE2GCSO mrPBOTFp8ty+F4TiZDZxvvgR6yC2EzF3DQuo8wbaphvn2pPa92rw32IpICSC57V5fSMRD1zqUd7 jq59x7R1VxL1PhbSI96negxRs49FT8ZTibkDR5X0tR8fVMTBo3dFqG4/BpDVaqpNaTZ0S3Fr4hi RIXPhrIbIzlaBf+4h7QkYx1vO7N4uOmViJfjdvoDCIlN/eSPB9HnCRYlUUdYIUWf/cATIRrF+hl YnBh/slkYT5USYazQMtnXPD6pweTgi0GZadNB0efzgVmnL/olUL8TGleseLPO8ds1VIBbmgqTxX CvCnW1mV5BPzQPU1D1nYhNgsPx56Wf0IJ7aY2tA1yhbbA7We02bjce3pJ48ePDzeo+c968ijzdl 62tnv9RIN0bzkIrLmurvXFtEEMOfXldNKzKPlvYhaKK0I26FpHmXF/OYOjDnacTb0VZn3bkOqvs HryI595Y53zV811G5cPefnTdDkpYExDBN5M0kC6Zzj+kMRBrZ3J6MxnbtBOKNBX6Jm6gSkFnLAl umzG5Zgdvv/pcQeKKavVzHi4JqLkJPIJbdUhLk9HwZ07hqhxxI8HTM/0D2xS3CKR8YF+uvwGkWa 09Fp5hOEo1hWJY3zoIScwzfdV/lqMvDA3P0M/e/cmJXNCoS0CaO15406QjPD5oLmhs2KluiWfa2 dX3m6bKwqjQte6IRftubUGcJZ4fTNQ78PQBz0Q0+ZYxb89wir3d1rmRdCgFcZNuxCoduSkjRM0G spi6egO9Fz0SRSPqi0S1zpoGCUbXK/7rgzL96eAiCmPx4NwJuJ+Pb8n/Vx+gD2vYtOFhj8338/l jjrYg==
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
x-tmase-result: 10--37.705300-8.000000
x-tmase-version: SMEX-12.5.0.1300-8.2.1013-24054.007
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/VJyvnpZ30U9INbK0R8NNBDLMVEg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 08:38:34 -0000

Nice summary Brian.

Thinking about tunneling QUIC in QUIC and proxy chains, we might end up wit=
h multiple layered QUIC security contexts, with the innermost layer being t=
he end-to-end QUIC connection that is used for an actual application layer.=
 Do you think this would benefit from multiple spin bits? Is that covered b=
y the cases you already set out?

Lucas
________________________________________
From: QUIC [quic-bounces@ietf.org] on behalf of Brian Trammell (IETF) [ietf=
@trammell.ch]
Sent: 03 October 2018 08:58
To: Mikkel Fahn=F8e J=F8rgensen
Cc: alexandre.ferrieux@orange.com; Mike Bishop; Ian Swett; Lars Eggert; IET=
F QUIC WG; Kazuho Oku
Subject: Re: a proposed way forward was Re: Spin bit decision

hi Mikkel,

I think we're having trouble with the many meanings of the word "proxy" her=
e. It can mean at least three things in this context, each of which has dif=
ferent implications for RTT measurement:

(1) Web proxying. The web proxy terminates transport connections, and as su=
ch the spin bit would only expose the RTT on the segment between the proxy =
and its Internet-side peer. Since the whole point of the proxy from a priva=
cy standpoint is to make traffic look like it's coming from the proxy, expo=
sing this RTT is not an issue.

(2) Transport-terminating proxying. Here the proxying happens at the stream=
, as opposed to the request level. For spin bit measurement, this is equiva=
lent to (1) above. (Note that this is widely deployed for TCP in the form o=
f transparent back-to-back proxies, which won't work in QUIC since the secu=
rity association protecting the transport is end-to-end.)

(3) Proxy-via-NAT. Here the proxy simply rewrites UDP addresses; in this ca=
se, since the transport association is not terminated, the spin bit will ex=
pose full end-to-end RTT. Indeed, in this case, endpoints may want to disab=
le RTT measurement.

> On 3 Oct 2018, at 09:45, Mikkel Fahn=F8e J=F8rgensen <mikkelfj@gmail.com>=
 wrote:
>
>>
>> At last a concrete argument, thanks ;)
>> But why would exposing the RTT be harmful in a NAT/UDP-proxy scenario ?
> Great firewall censorship.

Say more here? I don't see the relevance.

> VPN proxy to bypass streaming restrictions by country.

AFAIK most/all of these are of type (1) and (2), so not relevant to the dis=
cussion.

> Hackers that proxy traffic via a legitimate cooperation.

For web traffic, at least, this would probably be of type (1).

> Internet access providers prioritising local traffic.

This can and always will be done via other identifiers, so even if RTT is e=
xposed here, it is of limited utility/threat (depending on which team you'r=
e rooting for).

> High latency onion routing traffic.

Necessarily always terminates transport. However, the fundamental design pr=
operties of circuit-based anonymity systems do mean that if you're doing so=
mething like running a VPN tunnel over ToR (for.. some reason?), then you s=
hould turn off the spin bit for traffic within that tunnel. Client opt-outs=
 seem to be mostly sufficient for this, though.

Cheers,

Brian


>
>>
>>
>>
>> ________________________________________________________________________=
_________________________________________________
>>
>> Ce message et ses pieces jointes peuvent contenir des informations confi=
dentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez r=
ecu 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 d=
elete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have be=
en modified, changed or falsified.
>> Thank you.



-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specif=
ically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------


From nobody Wed Oct  3 03:06:30 2018
Return-Path: <alexandre.ferrieux@orange.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 806B3130F89 for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 03:06:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.291
X-Spam-Level: 
X-Spam-Status: No, score=-0.291 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 JDadyriJhKs8 for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 03:06:28 -0700 (PDT)
Received: from orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E1FE131084 for <quic@ietf.org>; Wed,  3 Oct 2018 03:06:28 -0700 (PDT)
Received: from opfednr03.francetelecom.fr (unknown [xx.xx.xx.67]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id 42QBW65qzMzCrVZ; Wed,  3 Oct 2018 12:06:26 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfednr03.francetelecom.fr (ESMTP service) with ESMTP id 42QBW64rL3zDq7V; Wed,  3 Oct 2018 12:06:26 +0200 (CEST)
Received: from [10.193.4.89] (10.168.234.2) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 3 Oct 2018 12:06:26 +0200
Subject: Spin bit as a negotiated option
To: IETF QUIC WG <quic@ietf.org>, Brian Trammell <ietf@trammell.ch>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch>
From: <alexandre.ferrieux@orange.com>
CC: Christian Huitema <huitema@huitema.net>
Message-ID: <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com>
Date: Wed, 3 Oct 2018 12:04:45 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: fr-xx-moderne
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.168.234.2]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/aGad69N5fdLnw2T1p3TtRZPOUbY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 10:06:29 -0000

On 10/03/18 09:58, Brian Trammell (IETF) wrote:
> Backing off the MUST for now for such situations is IMO a good tradeoff,
> though, especially since we only need fractions of a percent of deployment to
> start seeing useful signal for baseline/anomaly measurement of large
> aggregates.

If the consensus is that we must allow for such situations, then there are two 
possibilities:

  (a) weak spec language (MAY WISH TO or similar) => many implementations will 
simply drop it

  (b) negotiated option where the negotiation mechanism is mandatory

In the vein of (b), Christian suggested offline to introduce negotiation to 
allow for experimentation of the remaining two reserved bits. Then may be we can 
synthesize both ideas by the following proposal:

  - in the first few exchanges of the 5-tuple, use the three bits for option 
negotiation

  - then use them as defined by the selected option

Example encodings:

  000 : nothing
  001 : spin bit alone : S00
  010 : spin bit + VEC : SVV
  ... : other extensions

The negotiation mechanism allows both endpoints to force 000.
And since it is in the clear first byte, it allows on-path observers to identify 
the option without resorting to heuristics; this helps in the case of a small 
support ratio.




_________________________________________________________________________________________________________________________

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.


From nobody Wed Oct  3 06:32:26 2018
Return-Path: <kazuhooku@gmail.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 E1A1A131270 for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 06:32:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 oT12fsMTPEFk for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 06:32:21 -0700 (PDT)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 21CD9131288 for <quic@ietf.org>; Wed,  3 Oct 2018 06:32:21 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id 203-v6so5082212ljj.13 for <quic@ietf.org>; Wed, 03 Oct 2018 06:32:21 -0700 (PDT)
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:content-transfer-encoding; bh=7c7zO6JAGDZaNLWq24+c/Jt3sM0VoiBm9JmhK3vf5nU=; b=am9J3kiEIEzC/tcynzdsZq3ghqndE0N2tEjbPAGcnbXcwlC856dc5SmGJUR2Gq4rkS q2zLUxFCMS32tHZLIDaMBW9vc3McLa4TVG53oRluBK2eigkYuJTDQPOwz430VRcFbzCl H8CBtGdvTwvQbuTXmjHWRIogmkWGaeCgn9bfYHxGWK4rSpKjs0fby7Hp9m7Rvo8LYz3N OEqERixdyGcbp9kg38cM8GlA2XMmrHYt+D26kpzhcjJLQQD3soBvXWEoStkgmL+CX57S vAi8NLRs0PbMe/T0nJCvtZXPi3b5NEZS7O7rlQ/O4IPXhBzi3Ph1+Rr4BAOKK9jPKle4 k9vw==
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:content-transfer-encoding; bh=7c7zO6JAGDZaNLWq24+c/Jt3sM0VoiBm9JmhK3vf5nU=; b=fCC+aSP3jzKKYHGvFZ4sRSkV72M9XouiFxfPFOqrhJBup4cBCOJ9uZEL5/1DkkYYZY L6tsCfpkrG9JnSA5OBfQoAqT3OQxVE2O3BxSu1i+CRkXxXHZ9thEJ3uPFNDXJJjFziz0 YhovWB8vj0jGNLZ5kVV/U32nojmiIctP5p98WotGT0mYHjHwrNyYl+Z1f4HMDXCb9ic/ dqdGd1CDQdb/qDOYPCsIjk2Qv3t5n75p5MrtA4Yux3XL1hL/gBI/cSyx3ubQyD4IERTn laELyRbPdx/M+VEeFYGByNFHg8BeF6bOl1+deXhBUqW7s9J2P4JPfpVSPN2ltu66ZesO 4uTg==
X-Gm-Message-State: ABuFfohKRLb3p9gvmagwT+iAZTuXyY9IjZk5ajxcBCPCkc26w4p0LmAS VU8Jk/QWX4KIqLWM6IA1MI6x3ooC7teG5qN70XI=
X-Google-Smtp-Source: ACcGV63/Lrj8rJiO6ajDhm8E+gX9r6qdlD4XZ+rotsAXH8wGFwn9z0X8bv7Bx+1NA1dwRWnodOXMf4pls9Tuk42G6CI=
X-Received: by 2002:a2e:350e:: with SMTP id z14-v6mr1155099ljz.49.1538573539107;  Wed, 03 Oct 2018 06:32:19 -0700 (PDT)
MIME-Version: 1.0
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch>
In-Reply-To: <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Wed, 3 Oct 2018 22:32:06 +0900
Message-ID: <CANatvzwrqcH6JZjaG=gtD3CCoPphkhx8RgRzkAKb2oKBJ9QU-w@mail.gmail.com>
Subject: Re: a proposed way forward was Re: Spin bit decision
To: Brian Trammell <ietf@trammell.ch>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Lars Eggert <lars@eggert.org>,  IETF QUIC WG <quic@ietf.org>, Mike Bishop <mbishop@evequefou.be>,  Lili Peaudchien <alexandre.ferrieux@orange.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/F3W9r-kZqcJFgSCYyeBk5c8ySac>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 13:32:25 -0000

2018=E5=B9=B410=E6=9C=883=E6=97=A5(=E6=B0=B4) 16:58 Brian Trammell (IETF) <=
ietf@trammell.ch>:
>
> hi Kazuho,
>
> > On 3 Oct 2018, at 01:31, Kazuho Oku <kazuhooku@gmail.com> wrote:
> >
> > 2018=E5=B9=B410=E6=9C=883=E6=97=A5(=E6=B0=B4) 6:11 Brian Trammell (IETF=
) <ietf@trammell.ch>:
> >>
> >> hi Ian, all,
> >>
> >> Perhaps we can exploit the asymmetry inherent in QUIC (there are serve=
rs and clients), the spin bit (the server reflects, the client inverts), an=
d the desire to participate or not (ISTM that most of the discussion we've =
had about opting out have focused on client opt-out, based either on the pr=
inciple of the thing and/or a suspicion that the signal is useless) to reso=
lve this discussion.
> >>
> >>
> >> A proposal:
> >>
> >> 1. Servers MUST reflect the spin value. Clients MAY treat an unambiguo=
usly detected non-reflected bit as a protocol error.
> >
> > I oppose to using MUST for the server, because some *servers* might
> > not be willing to expose the path RTT, for example when it is running
> > hidden behind a UDP proxy.
>
> s/MUST/SHOULD, unless.../ is an acceptable change, as long as we have a n=
ice tight box around the unless.

My current thinking is that I would not oppose to having a simple
"SHOULD", which is IMO stronger than SHOULD with exceptions.

Regarding the "unless..." clause, I think all we can state is the
general rule; i.e. that an endpoint not willing to expose RTT needs to
opt-out from using spin bit. We could provide some examples of cases
where opting-out is desirable, but I do not think we could come up
with an exhaustive list of the cases.

> The tradeoff is that every caveat we put on the server-side reduces serve=
r-side deployment, which reduces the chances that a cooperating server and =
a cooperating client meet up.

I agree. Generally speaking, I think it is a good idea to specify a
tool that network operators can use for troubleshooting. And spin bit
looks simple enough to implement. Even for a person like me who does
not place Spin bit a high priority in his/her ToDo list, it is good to
have a mechanism that the person can run for help when facing trouble.

>
> I'm also quite sympathetic to Marten's argument that "server" and "client=
" are more arbitrary in P2P situations. However, the asymmetry of the spinb=
it is pretty far down the list of asymmetries (stream handling, handshake, =
TLS certs, etc) that I'd want to see optionally addressed in a QUIC version=
 i2 (is this the terminology we're using now?)
>
> Backing off the MUST for now for such situations is IMO a good tradeoff, =
though, especially since we only need fractions of a percent of deployment =
to start seeing useful signal for baseline/anomaly measurement of large agg=
regates.
>
> > I also do not think that maintaining the spin-bit for each
> > "connection" works. My understanding is that it should be per-5-tuple
> > because multiple QUIC connections can be coalesced onto single UDP
> > port on both sides, and because it is impossible for an observer to
> > track the pair of CIDs identifying the same connection across CID
> > changes.
>
> Well, it should be per 5-tuple, but it should also change when CIDs chang=
e. Dumping state on any CID change is the easiest way I know to break linka=
bility, and the most obvious way to do this when you have CID concurrency i=
s to keep state per CID.

I am not sure if you need to dump the spin bit state when changing
CID, because it would be obvious to the observer that a flow (that
consists of multiple connections) continue running on the same
5-tuple.

As I have stated in my previous mail and on the GH issue, it is
practical for an observer to assume that QUIC connections sharing one
5-tuple are between two machines, even in case NAT or UDP proxy is
involved. That means that RTT does not change across CID changes, and
therefore to me it seems that resetting the spin bit state is
unnecessary.

Regarding breaking linkability when coalescing multiple QUIC
connections, my understanding is that the practical method is to
change CID for all the connections at once. Doing so would hide each
connection behind the anonymity set of N connections where N is the
number of connections being coalesced. I think that is the most we can
achieve.

>
> That might be too far into the implementation weeds for the spec though..=
. the language needs to be clear (and clearer than in my initial proposal, =
which is one reason that's a list message and not a PR ;) )
>
> > I have opened https://github.com/quicwg/base-drafts/issues/1828 to
> > track the issue.
>
> Thanks, will follow discussion there as well.
>
> Cheers,
>
> Brian
>
>
> >
> >> 2a. Clients SHOULD invert the spin value, unless [EDNOTE: someone othe=
r than me should write convincing reasons for non-implementation here], or =
the client has been configured not to spin, or to use some other client beh=
avior.
> >>
> >> -OR-
> >>
> >> 2b. Clients set the spin bit value as they see fit, provided that this=
 behavior is consistent per connection ID. In order to provide RTT informat=
ion to the path, clients MAY invert the spin value (per reference to a sepa=
rate RFC that looks a lot like draft-tsvwg-quic=3Dspin, to be published by =
QUIC, TSVWG, or IPPM).
> >>
> >> 3. Servers and clients MUST NOT expose spin state from one Connection =
ID to another Connection ID.
> >>
> >>
> >> 1 is intended to drive deployment through server defaults. Yes, one ca=
n argue that the protocol error here is artificial (and the proposal explic=
itly acknowledges that through the client MAY error out), but the client ca=
n always opt out by clamping to a random value per CID.
> >>
> >> The 2a variant is essentially a 2119-compliant way of saying "we'd rea=
lly like it if you implemented the spin bit", leaving the question of clien=
t defaults (opt in versus opt out) up to the client implementors.
> >>
> >> The 2b variant is designed to allow for future or parallel client-side=
 behaviors other than spinning to support different measurement goals. For =
example, using the adaptive square wave proposed for on-path loss measureme=
nt (by either Mikkel or Kazuho, I believe) at the client with server reflec=
tion would allow accumulation of loss on the upstream as well as the downst=
ream path, as well as upstream (toward the server) RTT measurement. Obvious=
ly, the set of these deployed in the wild would have to be kept small in or=
der to allow a measurement device to heuristically determine which signal w=
as in use given a spinbit stream.
> >>
> >> 3 prevents spin state from leaking across CIDs, reducing the (already =
tiny but nonzero) linkability surface.
> >>
> >> (Obviously, the above needs wordsmithing, but these are the broad line=
s.)
> >>
> >> Cheers,
> >>
> >> Brian
> >>
> >>> On 2 Oct 2018, at 19:13, Ian Swett <ianswett=3D40google.com@dmarc.iet=
f.org> wrote:
> >>>
> >>> One piece of information related to the above discussion is whether d=
etecting who is and is not spinning is easy and reliable.
> >>>
> >>> One of my concerns is unintentional mis-use of the signal, and if it =
can't be detected reliably in a mixed environment, that means SHOULD is unw=
ise and argues for either not including it or making it a MUST.
> >>>
> >>> On Tue, Oct 2, 2018 at 12:51 PM Mike Bishop <mbishop@evequefou.be> wr=
ote:
> >>> I don=E2=80=99t think it=E2=80=99s a grim view, I think it=E2=80=99s =
a pragmatic view.  Our role is to specify the things which are fundamental =
to the protocol and have to happen for peers to interoperate.  Mis-using no=
rmative language for other things is an abuse of the process -- that's kind=
 of the point of RFC 6919.
> >>>
> >>>
> >>>
> >>> RFC 2119 says:
> >>>
> >>> In particular, [normative language] MUST only be used where it is act=
ually required for interoperation or to limit behavior which has potential =
for causing harm (e.g., limiting retransmisssions)  For example, they must =
not be used to try to impose a particular method on implementors where the =
method is not required for interoperability.
> >>>
> >>>
> >>>
> >>> Given that the spin bit is not =E2=80=9Cactually required for interop=
eration,=E2=80=9D but is the very definition of =E2=80=9Ctry to impose a pa=
rticular method on implementors,=E2=80=9D I=E2=80=99d say that RFC 2119 imp=
eratives are unwarranted.
> >>>
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: QUIC <quic-bounces@ietf.org> On Behalf Of alexandre.ferrieux@or=
ange.com
> >>> Sent: Tuesday, October 2, 2018 8:05 AM
> >>> To: Lars Eggert <lars@eggert.org>
> >>> Cc: IETF QUIC WG <quic@ietf.org>
> >>> Subject: Re: Spin bit decision
> >>>
> >>>
> >>>
> >>> On 10/02/18 16:00, Lars Eggert wrote:
> >>>
> >>>>
> >>>
> >>>> The point I can't seem to be getting across is that irrespective of
> >>>
> >>>> what the WG decides to require, there is no penalty for individual
> >>>
> >>>> stacks at deployment time (or after) to do whatever they wish, since
> >>>
> >>>> the spin bit by design has no impact on protocol operation and inter=
op.
> >>>
> >>>
> >>>
> >>> It is getting across, but it is a very grim view of the standardizati=
on process itself. Are there many examples of MUST in RFCs that turned out =
to be ignored by implementations just because they were not part of the cor=
e semantics and hence not enforced by other peers ?
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> _____________________________________________________________________=
____________________________________________________
> >>>
> >>>
> >>>
> >>> Ce message et ses pieces jointes peuvent contenir des informations co=
nfidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploit=
es ou copies sans autorisation. Si vous avez recu ce message par erreur, ve=
uillez le signaler a l'expediteur et le detruire ainsi que les pieces joint=
es. Les messages electroniques etant susceptibles d'alteration, Orange decl=
ine toute responsabilite si ce message a ete altere, deforme ou falsifie. M=
erci.
> >>>
> >>>
> >>>
> >>> This message and its attachments may contain confidential or privileg=
ed 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 an=
d 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.
> >>>
> >>>
> >>>
> >>
> >
> >
> > --
> > Kazuho Oku
>


--=20
Kazuho Oku


From nobody Wed Oct  3 06:55:35 2018
Return-Path: <kazuhooku@gmail.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 177EE13129A for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 06:55:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 dU3zXRe_HByR for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 06:55:31 -0700 (PDT)
Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (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 C018F131029 for <quic@ietf.org>; Wed,  3 Oct 2018 06:55:30 -0700 (PDT)
Received: by mail-lf1-x132.google.com with SMTP id d4-v6so4225503lfa.3 for <quic@ietf.org>; Wed, 03 Oct 2018 06:55:30 -0700 (PDT)
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:content-transfer-encoding; bh=uPPQ54QY2UF/I8Cz0x148A1j45VPOjKB3Sy10JOYNjk=; b=AIdg2N0Bin0ubvn9CGT8ev2G9wYPObmKy8qd1+8S21GfawpwIopzUwYoehGPN5DxD5 YizcBvfCjr1AP0YpYk/aVYwluP8Kmt35+JPog10e9qBBHF5S1r2OVfndrkWV1ueoXIRp qlVBOcMP03ujA7KGZnD042xwrqEc43Gm0vOggoHObl7G15nMDWro3saxTvOefY4OS4Kw BlbpOeWcH4kREYIEIaPIuWadwqx9yBy86CHK4rm4nu5OoM99NgOz8ZuNJ36dUE9t9zwT aC8Rrm1IUPLYXotWfWhFDAZyjtY4Z850UFB6c1d+aOs/rX6GTWv5/l2qJfgs7Mq13foT MK2w==
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:content-transfer-encoding; bh=uPPQ54QY2UF/I8Cz0x148A1j45VPOjKB3Sy10JOYNjk=; b=DGI1QMLcbyKDo07B2zZlowA70Q7YRg1NxqeRf5g1pxOWrrRWK/bAXvXICKpo7g4LEg acj1IGd6P4eDkveELPVr9apnz4hCCT5/DWY6enRssMGoLWabJFlm4IeIe/Rg2Y52lKuj Oyyk28tlFGirRCZxFfhQ7/XAT6KsU+7PN9uWuydrSDaQVw3kOkD/k+6zqMPvKjDbaF4Q T5+7ZpZzA7QCh4cgAVdFOD1AtU5supE5VKfMwEm/k0953uAY4iXMuYmACnNHdPHOu8fW a2172CSUFXGW/BjtMQpOk53Rgbl8Bkj6OpwpKX7rhKhoku7nZqye92EY/GNU3voJV8PI 0bQQ==
X-Gm-Message-State: ABuFfohapmuTuLvcX/861hSxtNepFUxIjbfb1p6UR9UfLoaWT/X375GX os5YAMTvfeqPvKzuit3FikVYtXFQoMReUCcXtP0f8H7sH2o=
X-Google-Smtp-Source: ACcGV60lX2P6gJiaxS6dBxgW6fPFtnZqBNhxmhI3hLE23s65t2uuzY5bqMWC6EpjPBk23pbImL8E+As4Z4wgRb6To3I=
X-Received: by 2002:a19:8d11:: with SMTP id p17-v6mr1080371lfd.116.1538574928812;  Wed, 03 Oct 2018 06:55:28 -0700 (PDT)
MIME-Version: 1.0
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <7221_1538551972_5BB470A4_7221_106_1_4a70bd20-3b2e-d4a6-4832-23024e1119f0@orange.com> <CAN1APddaqCxYr5rZVfd5K_LWMDigcRdhj4CihdCVo3F=NH0idg@mail.gmail.com> <055E2627-9D6C-45E8-8130-069B4891D24C@trammell.ch>
In-Reply-To: <055E2627-9D6C-45E8-8130-069B4891D24C@trammell.ch>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Wed, 3 Oct 2018 22:55:16 +0900
Message-ID: <CANatvzwJ_aeRTcmvyrYfc=NAhPQMtO2BQ9DOKJ6ztseJz024xA@mail.gmail.com>
Subject: Re: a proposed way forward was Re: Spin bit decision
To: Brian Trammell <ietf@trammell.ch>
Cc: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>,  Lili Peaudchien <alexandre.ferrieux@orange.com>, Lars Eggert <lars@eggert.org>, Mike Bishop <mbishop@evequefou.be>, IETF QUIC WG <quic@ietf.org>,  Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YhPDqxlugtlZF0KAGjLEv2uiuBQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 13:55:33 -0000

2018=E5=B9=B410=E6=9C=883=E6=97=A5(=E6=B0=B4) 16:58 Brian Trammell (IETF) <=
ietf@trammell.ch>:
>
> hi Mikkel,
>
> I think we're having trouble with the many meanings of the word "proxy" h=
ere. It can mean at least three things in this context, each of which has d=
ifferent implications for RTT measurement:
>
> (1) Web proxying. The web proxy terminates transport connections, and as =
such the spin bit would only expose the RTT on the segment between the prox=
y and its Internet-side peer. Since the whole point of the proxy from a pri=
vacy standpoint is to make traffic look like it's coming from the proxy, ex=
posing this RTT is not an issue.
>
> (2) Transport-terminating proxying. Here the proxying happens at the stre=
am, as opposed to the request level. For spin bit measurement, this is equi=
valent to (1) above. (Note that this is widely deployed for TCP in the form=
 of transparent back-to-back proxies, which won't work in QUIC since the se=
curity association protecting the transport is end-to-end.)

FWIW, IIUC TCP proxies that forward HTTPS traffic exist in the market.
At the very least, we care of such proxies in the ESNI draft [1]. The
practical merit of using such proxy is to mitigate DDoS attacks in an
application-protocol-agnostic way, but I would not be surprised if
some of the users are also interested in hiding the true location of
the server.

As you correctly note, such proxy services do not leak the end-to-end
RTT, because TCP is terminated by the proxy, but for QUIC the
transport becomes end-to-end, and it would essentially leak the RTT
between the proxy and the hidden server.

In my view, this should be considered as a degradation in terms of
privacy preservation from TCP to QUIC. I am opposed to having such
degradation, even though it could be considered as a niche. Hence my
argument for SHOULD rather than MUST.

[1] https://tools.ietf.org/html/draft-ietf-tls-esni-01#section-3.1

> (3) Proxy-via-NAT. Here the proxy simply rewrites UDP addresses; in this =
case, since the transport association is not terminated, the spin bit will =
expose full end-to-end RTT. Indeed, in this case, endpoints may want to dis=
able RTT measurement.
>
> > On 3 Oct 2018, at 09:45, Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@gm=
ail.com> wrote:
> >
> >>
> >> At last a concrete argument, thanks ;)
> >> But why would exposing the RTT be harmful in a NAT/UDP-proxy scenario =
?
> > Great firewall censorship.
>
> Say more here? I don't see the relevance.
>
> > VPN proxy to bypass streaming restrictions by country.
>
> AFAIK most/all of these are of type (1) and (2), so not relevant to the d=
iscussion.
>
> > Hackers that proxy traffic via a legitimate cooperation.
>
> For web traffic, at least, this would probably be of type (1).
>
> > Internet access providers prioritising local traffic.
>
> This can and always will be done via other identifiers, so even if RTT is=
 exposed here, it is of limited utility/threat (depending on which team you=
're rooting for).
>
> > High latency onion routing traffic.
>
> Necessarily always terminates transport. However, the fundamental design =
properties of circuit-based anonymity systems do mean that if you're doing =
something like running a VPN tunnel over ToR (for.. some reason?), then you=
 should turn off the spin bit for traffic within that tunnel. Client opt-ou=
ts seem to be mostly sufficient for this, though.
>
> Cheers,
>
> Brian
>
>
> >
> >>
> >>
> >>
> >> ______________________________________________________________________=
___________________________________________________
> >>
> >> Ce message et ses pieces jointes peuvent contenir des informations con=
fidentielles 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 messag=
es electroniques etant susceptibles d'alteration,
> >> Orange decline toute responsabilite si ce message a ete altere, deform=
e ou falsifie. Merci.
> >>
> >> This message and its attachments may contain confidential or privilege=
d 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.
>


--=20
Kazuho Oku


From nobody Wed Oct  3 11:41:52 2018
Return-Path: <mbishop@evequefou.be>
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 9935F130DDF for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 11:41:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 TqKjQHIVw1Po for <quic@ietfa.amsl.com>; Wed,  3 Oct 2018 11:41:40 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0098.outbound.protection.outlook.com [104.47.38.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D65412D7EA for <quic@ietf.org>; Wed,  3 Oct 2018 11:41:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pC7d1HR0fdV6jesv7wJLXYd00w+3OHNfNzESKaUCvwU=; b=FUsWWowJjkc3P8K0jGz0Gh5CeSQHVKnUkydcjGz60yJjm4lK1m4ateZ13PkSglbCwkkEcMD4oMlMDZeVVg6t856Qwjwy+x1nGa/aMRvy7rudJNM9CbDur7BihLRZDjczPhjcPd/sHjYHpj4BuRP8y1TnLw/cTmcJY80ZdD+1WOA=
Received: from CY4PR22MB0983.namprd22.prod.outlook.com (10.171.171.20) by CY4PR22MB0885.namprd22.prod.outlook.com (10.171.164.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1185.23; Wed, 3 Oct 2018 18:41:35 +0000
Received: from CY4PR22MB0983.namprd22.prod.outlook.com ([fe80::f4f6:67f1:e04e:7f6a]) by CY4PR22MB0983.namprd22.prod.outlook.com ([fe80::f4f6:67f1:e04e:7f6a%5]) with mapi id 15.20.1207.018; Wed, 3 Oct 2018 18:41:35 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, Lars Eggert <lars@eggert.org>
CC: IETF QUIC WG <quic@ietf.org>
Subject: RE: Spin bit decision
Thread-Topic: Spin bit decision
Thread-Index: AQHUWhYukd5OdbmHyk+wNZHVyKYYO6ULhImAgAAbI4CAACozgIAAHI6AgAAD4wCAAAMhAIAADuGAgAASIwCAABt7EIAAW/4AgAFWcbA=
Date: Wed, 3 Oct 2018 18:41:34 +0000
Message-ID: <CY4PR22MB098308F84A8FABCD2DB99B99DAE90@CY4PR22MB0983.namprd22.prod.outlook.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <4629_1538518470_5BB3EDC6_4629_90_1_071dda88-6bd8-fdf6-2321-d59c928ce904@orange.com>
In-Reply-To: <4629_1538518470_5BB3EDC6_4629_90_1_071dda88-6bd8-fdf6-2321-d59c928ce904@orange.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [38.134.241.6]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR22MB0885; 6:vE84nxET7qO7cm5fgAl0HkZiJU8G25GGE9ZNmbApcoDgVa9pwfLUO/HPsCOn2mBpr1qZ0reRthycf9nf1zXxAsLu1CaRIei7+VbvNJc/xFgERo7gz9z3ESVV3/tnuwGqsC7ryOQ8IhWqGyDNuXfJYQt13QpPjojpgZlVUPYIgZOTOAokmkvdBZQIQteXwwIbQQ3BvJeJPEHWJFyBHKr/7glBCqWDDAl1FJ1oKXL5WVHwMzuavD5g1GcFgusaLxAdNynBleUpvPSV1KwGoLCNJhDUEwilvPdjj5hXqm+HnToLjQhu9LU2UQB/j7VEg4HK4BfEUSnEFdXDzda6eltQP90CBYWAEB70VDUmj1xKYWT6XQryKRGyeEziOTJY9tUyFw++8cQgBmJZET1XTvP2z874K/6T582Wj6cUhnKMXmzlrKnUfgIbRFZb/QpfZNCd2hL7lVxkgwgGD9aSceqGMg==; 5:Y91vEQEuQsAyBsKnAZEQatGEkgFts7OBNsQCrjc460w5EBbofnhkgxqsMz2BBAoMn6M3lYyKqBMOhmKsDppnf/oMurObo9WnawUynxCCc6JpsV1QMAAOa1eY19o3z3RlGAhqGjL3mRnFM1pSo6SVKmCmUyzqEYDjD+0oHPIhoD4=; 7:IwWJR/y2vGIQpFhtP2RmjnSUjmNM39g69va0XghZNbGaxkzRNzlbJ3kyWYHrzN+v6Z6YHO+C3h32U7sVFIgzBG0rgubZiLYFsmsgcihOoSfE4by6gGsiFcGPzDEhPx842utju2w2mT7+wFRnz1p0EJfp0OVootm9cxSsOojaksQXSdbv+RcD6NROR32MJ9i2d/r+aRMQny7U7olHxiGSiSsf79Md2eespBT7Sq9qIyBWLQplFdhlZyPaPXUfPDoD
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 4c6eba96-39af-4217-fd9d-08d6295fd886
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:CY4PR22MB0885; 
x-ms-traffictypediagnostic: CY4PR22MB0885:
x-microsoft-antispam-prvs: <CY4PR22MB08858CDB04E91782B3786A24DAE90@CY4PR22MB0885.namprd22.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(161740460382875)(18271650672692);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(10201501046)(3231355)(944501410)(52105095)(149066)(150057)(6041310)(20161123558120)(20161123564045)(20161123560045)(20161123562045)(2016111802025)(6043046)(201708071742011)(7699051); SRVR:CY4PR22MB0885; BCL:0; PCL:0; RULEID:; SRVR:CY4PR22MB0885; 
x-forefront-prvs: 0814A2C7A3
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(366004)(136003)(39830400003)(396003)(346002)(189003)(199004)(13464003)(8936002)(316002)(2900100001)(99286004)(5024004)(3846002)(55016002)(6116002)(14454004)(14444005)(71190400001)(76176011)(305945005)(66066001)(9686003)(86362001)(6436002)(26005)(186003)(97736004)(71200400001)(2906002)(256004)(476003)(110136005)(102836004)(508600001)(6506007)(53546011)(7116003)(74316002)(33656002)(229853002)(74482002)(11346002)(486006)(5660300001)(5250100002)(53936002)(106356001)(7736002)(25786009)(4326008)(2501003)(7696005)(105586002)(3480700004)(6246003)(68736007)(8676002)(93886005)(81156014)(81166006)(446003); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR22MB0885; H:CY4PR22MB0983.namprd22.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: luNY7i0h/diF/7k6hbtSkZGVp7rcNikkd4Q481ftMs7YPJgmuVPRa5eZwgOPFPNTsLEmeEGLB4eoRHtAbZCDgpNX1jbG4g3C5spa+7qQi9tzW+NHE681I2CpOC4uR+GmSDbJtzMyLdroH80Ge7D88zQKE6RSoMhLFQq/jZACTsR08OZXCIynHVfLDRAl0BW1A1BSekfrn6byefEKynQ/e25QzGc14MTHrKlZa3+RtaUUFNaV5qIJn/21HV9Ezy3GjultLJ3lLxwLvOKjcXPepwuElEkap5PoPikW3tirOWMa9mTQ/6KCMVibq2xi3wRkPq27FIo7bbYHEjvv8Am9+oT6UxmlJAoFf67Odihg/K0=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 4c6eba96-39af-4217-fd9d-08d6295fd886
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Oct 2018 18:41:34.8204 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR22MB0885
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/TwWqkFM0DjEtznsaEjUXBb1xNqc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 18:41:50 -0000

Tm90IGF0IGFsbCAtLSB3aGV0aGVyIHdlJ2QgbGlrZSBpdCB0byBiZSB3aWRlc3ByZWFkIGJlaGF2
aW9yIGlzIGEgc2VwYXJhdGUgcXVlc3Rpb24gZnJvbSB3aGV0aGVyIGl0J3MgYSByZXF1aXJlbWVu
dCB0byBzdWNjZXNzZnVsbHkgaW50ZXJvcGVyYXRlLg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KRnJvbTogYWxleGFuZHJlLmZlcnJpZXV4QG9yYW5nZS5jb20gPGFsZXhhbmRyZS5mZXJy
aWV1eEBvcmFuZ2UuY29tPiANClNlbnQ6IFR1ZXNkYXksIE9jdG9iZXIgMiwgMjAxOCAzOjEzIFBN
DQpUbzogTWlrZSBCaXNob3AgPG1iaXNob3BAZXZlcXVlZm91LmJlPjsgTGFycyBFZ2dlcnQgPGxh
cnNAZWdnZXJ0Lm9yZz4NCkNjOiBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc+DQpTdWJqZWN0
OiBSZTogU3BpbiBiaXQgZGVjaXNpb24NCg0KT24gMTAvMDIvMTggMTg6NTAsIE1pa2UgQmlzaG9w
IHdyb3RlOg0KPiBHaXZlbiB0aGF0IHRoZSBzcGluIGJpdCBpcyBub3Qg4oCcYWN0dWFsbHkgcmVx
dWlyZWQgZm9yIGludGVyb3BlcmF0aW9uLOKAnSANCj4gYnV0IGlzIHRoZSB2ZXJ5IGRlZmluaXRp
b24gb2Yg4oCcdHJ5IHRvIGltcG9zZSBhIHBhcnRpY3VsYXIgbWV0aG9kIG9uIA0KPiBpbXBsZW1l
bnRvcnMs4oCdIEnigJlkIHNheSB0aGF0IFJGQyAyMTE5IGltcGVyYXRpdmVzIGFyZSB1bndhcnJh
bnRlZC4NCg0KTXkgbmFpdmUgYmVsaWVmIHdhcyB0aGF0IHdlIHdlcmUgaW4gdGhlIHByb2Nlc3Mg
b2YgKDEpIGRlY2lkaW5nIHdoZXRoZXIgd2UnZCBsaWtlIHRoZSBzcGluIGJpdCB0byBiZSB3aWRl
c3ByZWFkOyBhbmQgbGF0ZXIsICgyKSBob3cgdG8gZ2V0IHRoZXJlIGdpdmVuIHRoZSBmYWN0IHRo
YXQgaW1wbGVtZW50b3JzIGFyZSBtb2RlcmF0ZWx5IG9ubHkgY29uc3RyYWluZWQgYnkgIFJGQ3Mu
DQoNCkJ1dCB5b3VyIHN0YXRlbWVudHMgYWJvdmUgc2VlbSB0byBpbmRpY2F0ZSB0aGF0ICgxKT1O
Ty4NCklzIHRoaXMgY29uc2Vuc3VhbCBhbHJlYWR5ID8gSWYgeWVzLCB3aHkgYXJlIHdlIGRpc2N1
c3NpbmcgYXQgYWxsID8NCg0KDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KDQpDZSBtZXNzYWdlIGV0IHNlcyBwaWVj
ZXMgam9pbnRlcyBwZXV2ZW50IGNvbnRlbmlyIGRlcyBpbmZvcm1hdGlvbnMgY29uZmlkZW50aWVs
bGVzIG91IHByaXZpbGVnaWVlcyBldCBuZSBkb2l2ZW50IGRvbmMgcGFzIGV0cmUgZGlmZnVzZXMs
IGV4cGxvaXRlcyBvdSBjb3BpZXMgc2FucyBhdXRvcmlzYXRpb24uIFNpIHZvdXMgYXZleiByZWN1
IGNlIG1lc3NhZ2UgcGFyIGVycmV1ciwgdmV1aWxsZXogbGUgc2lnbmFsZXIgYSBsJ2V4cGVkaXRl
dXIgZXQgbGUgZGV0cnVpcmUgYWluc2kgcXVlIGxlcyBwaWVjZXMgam9pbnRlcy4gTGVzIG1lc3Nh
Z2VzIGVsZWN0cm9uaXF1ZXMgZXRhbnQgc3VzY2VwdGlibGVzIGQnYWx0ZXJhdGlvbiwgT3Jhbmdl
IGRlY2xpbmUgdG91dGUgcmVzcG9uc2FiaWxpdGUgc2kgY2UgbWVzc2FnZSBhIGV0ZSBhbHRlcmUs
IGRlZm9ybWUgb3UgZmFsc2lmaWUuIE1lcmNpLg0KDQpUaGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRh
Y2htZW50cyBtYXkgY29udGFpbiBjb25maWRlbnRpYWwgb3IgcHJpdmlsZWdlZCBpbmZvcm1hdGlv
biB0aGF0IG1heSBiZSBwcm90ZWN0ZWQgYnkgbGF3OyB0aGV5IHNob3VsZCBub3QgYmUgZGlzdHJp
YnV0ZWQsIHVzZWQgb3IgY29waWVkIHdpdGhvdXQgYXV0aG9yaXNhdGlvbi4NCklmIHlvdSBoYXZl
IHJlY2VpdmVkIHRoaXMgZW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBh
bmQgZGVsZXRlIHRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRzLg0KQXMgZW1haWxzIG1h
eSBiZSBhbHRlcmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhhdCBoYXZl
IGJlZW4gbW9kaWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVkLg0KVGhhbmsgeW91Lg0KDQo=


From nobody Wed Oct  3 15:40:47 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 17BE3130DCB; Wed,  3 Oct 2018 15:40:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-qpack-03.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.85.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <153860643702.9128.18142464629204085867@ietfa.amsl.com>
Date: Wed, 03 Oct 2018 15:40:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/KiI9cBpADC8wiKUCYY2wxD7T6bk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 22:40:37 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : QPACK: Header Compression for HTTP over QUIC
        Authors         : Charles 'Buck' Krasic
                          Mike Bishop
                          Alan Frindell
	Filename        : draft-ietf-quic-qpack-03.txt
	Pages           : 35
	Date            : 2018-10-03

Abstract:
   This specification defines QPACK, a compression format for
   efficiently representing HTTP header fields, to be used in HTTP/QUIC.
   This is a variation of HPACK header compression that seeks to reduce
   head-of-line blocking.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-qpack/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-qpack-03
https://datatracker.ietf.org/doc/html/draft-ietf-quic-qpack-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-qpack-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Oct  3 15:41:13 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D8553130DFB; Wed,  3 Oct 2018 15:40:50 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-http-15.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.85.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <153860645083.9124.2956485723206917113@ietfa.amsl.com>
Date: Wed, 03 Oct 2018 15:40:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/t57OOr2_Z9tvp_ytVFUOXCqz-mY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 22:41:05 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : Hypertext Transfer Protocol (HTTP) over QUIC
        Author          : Mike Bishop
	Filename        : draft-ietf-quic-http-15.txt
	Pages           : 47
	Date            : 2018-10-03

Abstract:
   The QUIC transport protocol has several features that are desirable
   in a transport for HTTP, such as stream multiplexing, per-stream flow
   control, and low-latency connection establishment.  This document
   describes a mapping of HTTP semantics over QUIC.  This document also
   identifies HTTP/2 features that are subsumed by QUIC, and describes
   how HTTP/2 extensions can be ported to QUIC.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-http/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-http-15
https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-15

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-http-15


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Oct  3 16:01:51 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 91148130DBE; Wed,  3 Oct 2018 16:01:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-transport-15.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.85.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <153860770355.9128.11178239595373153590@ietfa.amsl.com>
Date: Wed, 03 Oct 2018 16:01:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/E2Srfp5OqmDsCBv1hE0CSbgYmZ4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 23:01:44 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : QUIC: A UDP-Based Multiplexed and Secure Transport
        Authors         : Jana Iyengar
                          Martin Thomson
	Filename        : draft-ietf-quic-transport-15.txt
	Pages           : 134
	Date            : 2018-10-03

Abstract:
   This document defines the core of the QUIC transport protocol.  This
   document describes connection establishment, packet format,
   multiplexing, and reliability.  Accompanying documents describe the
   cryptographic handshake and loss detection.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-transport/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-transport-15
https://datatracker.ietf.org/doc/html/draft-ietf-quic-transport-15

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-transport-15


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Oct  3 16:02:23 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EC238130DF5; Wed,  3 Oct 2018 16:02:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-recovery-15.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.85.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <153860772791.8954.16588533947198670244@ietfa.amsl.com>
Date: Wed, 03 Oct 2018 16:02:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/nNsI0jIBBigl4tnay3NF5Fj6gmc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 23:02:22 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : QUIC Loss Detection and Congestion Control
        Authors         : Jana Iyengar
                          Ian Swett
	Filename        : draft-ietf-quic-recovery-15.txt
	Pages           : 34
	Date            : 2018-10-03

Abstract:
   This document describes loss detection and congestion control
   mechanisms for QUIC.

Note to Readers

   Discussion of this draft takes place on the QUIC working group
   mailing list (quic@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/search/?email_list=quic [1].

   Working Group information can be found at https://github.com/quicwg
   [2]; source code and issues list for this draft can be found at
   https://github.com/quicwg/base-drafts/labels/-recovery [3].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-recovery/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-recovery-15
https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-15

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-recovery-15


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Oct  4 02:50:38 2018
Return-Path: <kazuhooku@gmail.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 B407E130E11 for <quic@ietfa.amsl.com>; Thu,  4 Oct 2018 02:50:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 EogYQgrHi6Rt for <quic@ietfa.amsl.com>; Thu,  4 Oct 2018 02:50:34 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 E777B130DFB for <quic@ietf.org>; Thu,  4 Oct 2018 02:50:33 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id j4-v6so3992578ljc.12 for <quic@ietf.org>; Thu, 04 Oct 2018 02:50:33 -0700 (PDT)
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:content-transfer-encoding; bh=Zcmf3uVr/PAerLaZFiH8dlGvZ45zEofMwjg+3/RQmMA=; b=YYo5dPEwZR3B3MgtDyOGWqNRVUW5iaKIcP0aGHvA4zJ27T4PHqt7Qv1QWdNDGq2NoC eTYjWcIxzIlMt/tW2nP+Vop+UBXfL4Pai01Ef1qsHIgf2p1ZdULCiYTTy7PxVfxnwrvJ IzIzbxDYQQ1rcAadmgLdYlnzjyL7da7ApSn0qoudgP5n7RN9dyxQIXMBhkYbew8gdF2Z c9n0cmIzGpXfaE12fukZvWaQ8fAvf9s07S70U/A3Pz1ivGTIkkDNX2aQeiyF+2qjByN5 J7H1r8FIQOmKuVvwi4GQ1QBEa9WMmbJFokxyrFq6939x2xPZYCf0EnWUS2eJ/ZRPy1qj PHvA==
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:content-transfer-encoding; bh=Zcmf3uVr/PAerLaZFiH8dlGvZ45zEofMwjg+3/RQmMA=; b=h8DT5XRndQ0w3EP1vnyYKePGJYNZXl5qCsXYvYvLlDCw+mIb31LB9qn8bohij3bOp/ fIspL45knZTadP1S7Eloj+gis1E41H7ppfC8S9dqT5x/TasIjYC9ToMWk7Y5B3Y22Agn VWJf6nem9N3FAuQnCdfwe10O78ukXTLek8UW4v30gQUhQoTNZtGqVF/UScgB4v1EJRqG BzBoYFYNnrl9VEiU4faunnmhjVhxNfJmf1fF/UwHHYU4zGBIfp/steFCTEhcFtbtr1Kd /WdpoRocjkDY2SWaJIycSIFkBcqRkxM7ntGaWfwPhvBvJrGuk8OnPHq849NbrB9MenfT yR/A==
X-Gm-Message-State: ABuFfohd+stzVXH2TFvRpkjNeKd9r4BuJLBcj3DaO+91a16jahJYbOSK d65lyhH03sT3QAr9hK9Qi8s1538S4vVAKMD3aTxLLu1J
X-Google-Smtp-Source: ACcGV61cbJH8yGTgFXuYzZOS6KLPVKUJw0B5r7ZvkNV458NLargoDlalH0EeQ6VwOyOViuMQiKszydSubyU2o1u1S8Y=
X-Received: by 2002:a2e:570b:: with SMTP id l11-v6mr3944881ljb.14.1538646632060;  Thu, 04 Oct 2018 02:50:32 -0700 (PDT)
MIME-Version: 1.0
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com>
In-Reply-To: <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Thu, 4 Oct 2018 18:50:20 +0900
Message-ID: <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com>
Subject: Re: Spin bit as a negotiated option
To: Lili Peaudchien <alexandre.ferrieux@orange.com>
Cc: IETF QUIC WG <quic@ietf.org>, Brian Trammell <ietf@trammell.ch>,  Christian Huitema <huitema@huitema.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/cyg3kKgJsfwbgPwD15gFy0lxclg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Oct 2018 09:50:37 -0000

Hi,

Thank you for starting the discussion specific to how we could
possibly negotiate the use of spin bits.

Regarding the topic, my preference goes to using the version number
field of the long header for negotiating the presence of spin bits, or
any additional signal being exposed to the network.

For example, QUICv1 without spin bit could use version 0x101, and v1
with spin bit could use 0x102. In the future, we can assign a
different version number for QUICv1 with multiple spin + VEC (or
people interested in testing the feature can designate a private
version number even before that).

I see the following benefits to using the version field as a method to
negotiate the use of spin bits.

1. One of the concern regarding spin bits has been that they could
lead to ossification. Spin bits are not part of the Invariants, but if
the observation tools start looking at those bits without checking the
version number field, we will have the pressure to not change how the
bits are used. Using the version number to indicate the presence of
spin bits is the best approach to resolve such concern.

2. We have hoped to roll out multiple versions of QUIC in a small
interval so that the version number field does not get ossified. The
best solution is obviously to roll out two flavors of the protocol
that uses different version numbers at the same time. We will have a
real-world use of version negotiation from day one, because we are in
a condition where implementors have different opinions on if they
should support spin bit :-)

The blocker to this approach has been version negotiation requiring an
additional round-trip, but that is going to be resolved by #1755.

2018=E5=B9=B410=E6=9C=883=E6=97=A5(=E6=B0=B4) 19:06 <alexandre.ferrieux@ora=
nge.com>:
>
> On 10/03/18 09:58, Brian Trammell (IETF) wrote:
> > Backing off the MUST for now for such situations is IMO a good tradeoff=
,
> > though, especially since we only need fractions of a percent of deploym=
ent to
> > start seeing useful signal for baseline/anomaly measurement of large
> > aggregates.
>
> If the consensus is that we must allow for such situations, then there ar=
e two
> possibilities:
>
>   (a) weak spec language (MAY WISH TO or similar) =3D> many implementatio=
ns will
> simply drop it
>
>   (b) negotiated option where the negotiation mechanism is mandatory
>
> In the vein of (b), Christian suggested offline to introduce negotiation =
to
> allow for experimentation of the remaining two reserved bits. Then may be=
 we can
> synthesize both ideas by the following proposal:
>
>   - in the first few exchanges of the 5-tuple, use the three bits for opt=
ion
> negotiation
>
>   - then use them as defined by the selected option
>
> Example encodings:
>
>   000 : nothing
>   001 : spin bit alone : S00
>   010 : spin bit + VEC : SVV
>   ... : other extensions
>
> The negotiation mechanism allows both endpoints to force 000.
> And since it is in the clear first byte, it allows on-path observers to i=
dentify
> the option without resorting to heuristics; this helps in the case of a s=
mall
> support ratio.
>
>
>
>
> _________________________________________________________________________=
________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confid=
entielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez re=
cu 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 o=
u falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged i=
nformation 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 de=
lete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have bee=
n modified, changed or falsified.
> Thank you.
>


--=20
Kazuho Oku


From nobody Thu Oct  4 02:57:54 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 67DF7130E18; Thu,  4 Oct 2018 02:57:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-tls-15.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.85.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <153864706538.4399.13871471868376617480@ietfa.amsl.com>
Date: Thu, 04 Oct 2018 02:57:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/plg-fJJzbe2QDi54JwuiEqCXmPk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Oct 2018 09:57:45 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : Using Transport Layer Security (TLS) to Secure QUIC
        Authors         : Martin Thomson
                          Sean Turner
	Filename        : draft-ietf-quic-tls-15.txt
	Pages           : 32
	Date            : 2018-10-03

Abstract:
   This document describes how Transport Layer Security (TLS) is used to
   secure QUIC.

Note to Readers

   Discussion of this draft takes place on the QUIC working group
   mailing list (quic@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/search/?email_list=quic [1].

   Working Group information can be found at https://github.com/quicwg
   [2]; source code and issues list for this draft can be found at
   https://github.com/quicwg/base-drafts/labels/-tls [3].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-tls/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-tls-15
https://datatracker.ietf.org/doc/html/draft-ietf-quic-tls-15

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-tls-15


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Oct  4 03:46:38 2018
Return-Path: <alexandre.ferrieux@orange.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 F092B130E09 for <quic@ietfa.amsl.com>; Thu,  4 Oct 2018 03:46:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.291
X-Spam-Level: 
X-Spam-Status: No, score=-0.291 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 eIkcCz4I9h8X for <quic@ietfa.amsl.com>; Thu,  4 Oct 2018 03:46:35 -0700 (PDT)
Received: from orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38CB2130DFB for <quic@ietf.org>; Thu,  4 Oct 2018 03:46:35 -0700 (PDT)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr24.francetelecom.fr (ESMTP service) with ESMTP id 42QqLx6yPCz1ysv; Thu,  4 Oct 2018 12:46:33 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id 42QqLx644kzDq7Q; Thu,  4 Oct 2018 12:46:33 +0200 (CEST)
Received: from [10.193.4.89] (10.168.234.2) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 4 Oct 2018 12:46:33 +0200
Subject: Re: Spin bit as a negotiated option
To: Kazuho Oku <kazuhooku@gmail.com>
CC: IETF QUIC WG <quic@ietf.org>, Brian Trammell <ietf@trammell.ch>, Christian Huitema <huitema@huitema.net>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com>
From: <alexandre.ferrieux@orange.com>
Organization: Orange
Message-ID: <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com>
Date: Thu, 4 Oct 2018 12:46:32 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: [10.168.234.2]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/jc0GV27RYk3Ic34qAm7UaPoSdsk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Oct 2018 10:46:37 -0000

Thanks Kazuho. Using version numbers directly was an obvious choice, but so=
 far=20
I was discouraged by strong language in the spec, saying 0x00000001 was the=
=20
unavoidable point of convergence after all 0xFF0000XX experiments. So in es=
sence=20
you're proposing to weaken that a bit, right ?

If so, how do you envision segmenting the version number space ?

  - direct enumeration:

	0x00000001 =3D v1dry
	0x00000002 =3D v1 + spinbit
	0x00000003 =3D v1 + spinbit + VEC
=09
  - low order bits for options:

	0x000001XX =3D v1 + option XX
	0x000002YY =3D v2 + option YY

Also, are we sure that this explosion won't weigh on the new VN scheme, ind=
ucing=20
slower convergence due to longer lists on either side ?

On 10/04/18 11:50, Kazuho Oku wrote:
> Hi,
>=20
> Thank you for starting the discussion specific to how we could
> possibly negotiate the use of spin bits.
>=20
> Regarding the topic, my preference goes to using the version number
> field of the long header for negotiating the presence of spin bits, or
> any additional signal being exposed to the network.
>=20
> For example, QUICv1 without spin bit could use version 0x101, and v1
> with spin bit could use 0x102. In the future, we can assign a
> different version number for QUICv1 with multiple spin + VEC (or
> people interested in testing the feature can designate a private
> version number even before that).
>=20
> I see the following benefits to using the version field as a method to
> negotiate the use of spin bits.
>=20
> 1. One of the concern regarding spin bits has been that they could
> lead to ossification. Spin bits are not part of the Invariants, but if
> the observation tools start looking at those bits without checking the
> version number field, we will have the pressure to not change how the
> bits are used. Using the version number to indicate the presence of
> spin bits is the best approach to resolve such concern.
>=20
> 2. We have hoped to roll out multiple versions of QUIC in a small
> interval so that the version number field does not get ossified. The
> best solution is obviously to roll out two flavors of the protocol
> that uses different version numbers at the same time. We will have a
> real-world use of version negotiation from day one, because we are in
> a condition where implementors have different opinions on if they
> should support spin bit :-)
>=20
> The blocker to this approach has been version negotiation requiring an
> additional round-trip, but that is going to be resolved by #1755.
>=20
> 2018=E5=B9=B410=E6=9C=883=E6=97=A5(=E6=B0=B4) 19:06 <alexandre.ferrieux@o=
range.com>:
>>
>> On 10/03/18 09:58, Brian Trammell (IETF) wrote:
>> > Backing off the MUST for now for such situations is IMO a good tradeof=
f,
>> > though, especially since we only need fractions of a percent of deploy=
ment to
>> > start seeing useful signal for baseline/anomaly measurement of large
>> > aggregates.
>>
>> If the consensus is that we must allow for such situations, then there a=
re two
>> possibilities:
>>
>>   (a) weak spec language (MAY WISH TO or similar) =3D> many implementati=
ons will
>> simply drop it
>>
>>   (b) negotiated option where the negotiation mechanism is mandatory
>>
>> In the vein of (b), Christian suggested offline to introduce negotiation=
 to
>> allow for experimentation of the remaining two reserved bits. Then may b=
e we can
>> synthesize both ideas by the following proposal:
>>
>>   - in the first few exchanges of the 5-tuple, use the three bits for op=
tion
>> negotiation
>>
>>   - then use them as defined by the selected option
>>
>> Example encodings:
>>
>>   000 : nothing
>>   001 : spin bit alone : S00
>>   010 : spin bit + VEC : SVV
>>   ... : other extensions
>>
>> The negotiation mechanism allows both endpoints to force 000.
>> And since it is in the clear first byte, it allows on-path observers to =
identify
>> the option without resorting to heuristics; this helps in the case of a =
small
>> support ratio.
>>
>>
>>
>>
>> ________________________________________________________________________=
_________________________________________________
>>
>> Ce message et ses pieces jointes peuvent contenir des informations confi=
dentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez r=
ecu 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 d=
elete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have be=
en modified, changed or falsified.
>> Thank you.
>>
>=20
>=20



___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Thu Oct  4 14:40:41 2018
Return-Path: <kazuhooku@gmail.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 40E07130DE5 for <quic@ietfa.amsl.com>; Thu,  4 Oct 2018 14:40:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 cLj6MElB6_SD for <quic@ietfa.amsl.com>; Thu,  4 Oct 2018 14:40:37 -0700 (PDT)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (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 8A662130934 for <quic@ietf.org>; Thu,  4 Oct 2018 14:40:36 -0700 (PDT)
Received: by mail-lj1-x234.google.com with SMTP id 63-v6so9768620ljs.4 for <quic@ietf.org>; Thu, 04 Oct 2018 14:40:36 -0700 (PDT)
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:content-transfer-encoding; bh=Gn9mVDhilfb16MlL1ayeNoyZZXUiTg3RiGOB2W4EcK4=; b=dCRhDHn2cy+WpxDPcrQV0Gh/ANuohUW6qIeqhoxEziRwjAouhU3XknPRSYhP8zM9/n 8EloO8TtVB5HCwl3RN2F0umn8pYhtZ0IClq9ROVonXKddkT7DUjwU33re7l2uLspQDFA o7wDZuDheUuk749HuPJInEQniogkBSIW1TaIm5BC52SAaiRQjypXAvYwXdIlTklUUNP+ 3aJw2KVgzVmNyerpDD+jKgdsvTPeeFO9rUdQG91biopcu3Yqt7lc3lGVnRnVTvJCRNyp UnckxiHuGtfIrO15D1J8oNZX2Xrn3VVM93fw2rDcfDuaXNG/+EM/nX/dX/qCi+GwtIph AwlQ==
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:content-transfer-encoding; bh=Gn9mVDhilfb16MlL1ayeNoyZZXUiTg3RiGOB2W4EcK4=; b=nOeQhNGCBbx/iR1+6LmOu2Lp1Tap9WdsbCNYbaTyzS2rTbpzKGsMSebpoSEXTWH7DP iDqAja/DrLLqOVDXpYAFm1i4UVjUv7wY269FV2vp2xZ2vdic7rEWlpWILDYYd2EEwiCj PSW8ZjGzeZHe0+T6mWvT3hI9jHurTddUOKoEq6NVJXRDnJwIGIMpZE4rjWhif+h9Q3zy IvvhsQfWtq+xNI3fOdk5Ik+6E3xUjpxZPX8mx4+viy//2aMLAiHHimEpY5OJKBwD7FxF 87qBAkSlt3UDcFquseSNyKdBc5j/kiZpmACR1vCNzp8XcKWkDEf7PAPtgM4E3ct3lWmN SSOw==
X-Gm-Message-State: ABuFfohk6ik0B2+lxyYx9Y4keFvul4vr+VP0aE0IH7vqOAoz6q2THi/n iLebvzNv5a3hAWenh9KEsM6rGXVGcIRIw2Qk8z0vsdwn
X-Google-Smtp-Source: ACcGV60J9+noTCkgk/KSE1dbF0//koOnpbuI5HPHkBa66Uf0Ihkba2yf0vnbVyKUIrwD0mgxPRhp4cB9/nPDyO5Z3Vk=
X-Received: by 2002:a2e:9d50:: with SMTP id y16-v6mr5687031ljj.136.1538689234613;  Thu, 04 Oct 2018 14:40:34 -0700 (PDT)
MIME-Version: 1.0
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com>
In-Reply-To: <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Fri, 5 Oct 2018 06:40:24 +0900
Message-ID: <CANatvzwzw7snBV4bXfhvWJk4znOmv0Er6kwidRR+dPQsfFczkw@mail.gmail.com>
Subject: Re: Spin bit as a negotiated option
To: Lili Peaudchien <alexandre.ferrieux@orange.com>
Cc: IETF QUIC WG <quic@ietf.org>, Brian Trammell <ietf@trammell.ch>,  Christian Huitema <huitema@huitema.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ctm3SFiECrnbr6FJV2Vn4RWmUa8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Oct 2018 21:40:39 -0000

2018=E5=B9=B410=E6=9C=884=E6=97=A5(=E6=9C=A8) 19:46 <alexandre.ferrieux@ora=
nge.com>:
>
> Thanks Kazuho. Using version numbers directly was an obvious choice, but =
so far
> I was discouraged by strong language in the spec, saying 0x00000001 was t=
he
> unavoidable point of convergence after all 0xFF0000XX experiments. So in =
essence
> you're proposing to weaken that a bit, right ?

I am not sure if we have reached consensus that QUICv1 should use
0x00000001 as the one and only number for the version number field.

My understanding is that it is simply written as such because I-D is a
draft of a RFC. A RFC needs to clarify the value of version number
field it uses, and I-D needs to have a paragraph that amends on how
the draft-versions uses the field.

>
> If so, how do you envision segmenting the version number space ?
>
>   - direct enumeration:
>
>         0x00000001 =3D v1dry
>         0x00000002 =3D v1 + spinbit
>         0x00000003 =3D v1 + spinbit + VEC
>
>   - low order bits for options:
>
>         0x000001XX =3D v1 + option XX
>         0x000002YY =3D v2 + option YY

I do not think we can segment the version number space, because IMO it
essentially means making spin bits an invariant. My understanding is
that spin bits is something specific to v1.

QUICv1 might use different values on the version number field to
represent if spin bits is (or other signals are) available, but that
does not mean that v2 will expose the same signals or they would use
the version number field for indicating that.

If it is the case that the use of 0x1xx for V1 might give people the
impression that the lower bits are used to indicate the availability
of unencrypted signals across multiple versions, I think starting from
0x00000001 (i.e. the one you describe as "direct enumeration") would
be preferable.

>
> Also, are we sure that this explosion won't weigh on the new VN scheme, i=
nducing
> slower convergence due to longer lists on either side ?

I do not think that is an issue for v1, because what currently at
stake is if we should assign one or two extra version numbers (i.e.
one for spin bit, and possibly another for spin+vec as a separate
draft).

If folks agree to expose other signals that requires a "configuration"
to be exposed as well, then they can define a new version number that
introduces a new field to the long header format for exposing the
"configuration."

>
> On 10/04/18 11:50, Kazuho Oku wrote:
> > Hi,
> >
> > Thank you for starting the discussion specific to how we could
> > possibly negotiate the use of spin bits.
> >
> > Regarding the topic, my preference goes to using the version number
> > field of the long header for negotiating the presence of spin bits, or
> > any additional signal being exposed to the network.
> >
> > For example, QUICv1 without spin bit could use version 0x101, and v1
> > with spin bit could use 0x102. In the future, we can assign a
> > different version number for QUICv1 with multiple spin + VEC (or
> > people interested in testing the feature can designate a private
> > version number even before that).
> >
> > I see the following benefits to using the version field as a method to
> > negotiate the use of spin bits.
> >
> > 1. One of the concern regarding spin bits has been that they could
> > lead to ossification. Spin bits are not part of the Invariants, but if
> > the observation tools start looking at those bits without checking the
> > version number field, we will have the pressure to not change how the
> > bits are used. Using the version number to indicate the presence of
> > spin bits is the best approach to resolve such concern.
> >
> > 2. We have hoped to roll out multiple versions of QUIC in a small
> > interval so that the version number field does not get ossified. The
> > best solution is obviously to roll out two flavors of the protocol
> > that uses different version numbers at the same time. We will have a
> > real-world use of version negotiation from day one, because we are in
> > a condition where implementors have different opinions on if they
> > should support spin bit :-)
> >
> > The blocker to this approach has been version negotiation requiring an
> > additional round-trip, but that is going to be resolved by #1755.
> >
> > 2018=E5=B9=B410=E6=9C=883=E6=97=A5(=E6=B0=B4) 19:06 <alexandre.ferrieux=
@orange.com>:
> >>
> >> On 10/03/18 09:58, Brian Trammell (IETF) wrote:
> >> > Backing off the MUST for now for such situations is IMO a good trade=
off,
> >> > though, especially since we only need fractions of a percent of depl=
oyment to
> >> > start seeing useful signal for baseline/anomaly measurement of large
> >> > aggregates.
> >>
> >> If the consensus is that we must allow for such situations, then there=
 are two
> >> possibilities:
> >>
> >>   (a) weak spec language (MAY WISH TO or similar) =3D> many implementa=
tions will
> >> simply drop it
> >>
> >>   (b) negotiated option where the negotiation mechanism is mandatory
> >>
> >> In the vein of (b), Christian suggested offline to introduce negotiati=
on to
> >> allow for experimentation of the remaining two reserved bits. Then may=
 be we can
> >> synthesize both ideas by the following proposal:
> >>
> >>   - in the first few exchanges of the 5-tuple, use the three bits for =
option
> >> negotiation
> >>
> >>   - then use them as defined by the selected option
> >>
> >> Example encodings:
> >>
> >>   000 : nothing
> >>   001 : spin bit alone : S00
> >>   010 : spin bit + VEC : SVV
> >>   ... : other extensions
> >>
> >> The negotiation mechanism allows both endpoints to force 000.
> >> And since it is in the clear first byte, it allows on-path observers t=
o identify
> >> the option without resorting to heuristics; this helps in the case of =
a small
> >> support ratio.
> >>
> >>
> >>
> >>
> >> ______________________________________________________________________=
___________________________________________________
> >>
> >> Ce message et ses pieces jointes peuvent contenir des informations con=
fidentielles 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 messag=
es electroniques etant susceptibles d'alteration,
> >> Orange decline toute responsabilite si ce message a ete altere, deform=
e ou falsifie. Merci.
> >>
> >> This message and its attachments may contain confidential or privilege=
d 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 confid=
entielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez re=
cu 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 o=
u falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged i=
nformation 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 de=
lete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have bee=
n modified, changed or falsified.
> Thank you.
>


--=20
Kazuho Oku


From nobody Thu Oct  4 14:53:22 2018
Return-Path: <Gabriel.Montenegro@microsoft.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 23237130DE5 for <quic@ietfa.amsl.com>; Thu,  4 Oct 2018 14:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.457
X-Spam-Level: 
X-Spam-Status: No, score=-2.457 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 jjvyYzR8BTGe for <quic@ietfa.amsl.com>; Thu,  4 Oct 2018 14:53:16 -0700 (PDT)
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (mail-eopbgr730137.outbound.protection.outlook.com [40.107.73.137]) (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 89A1612D7EA for <quic@ietf.org>; Thu,  4 Oct 2018 14:53:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=QCBMX8Qbe4gBK6m/Vc+J1qZ7CxuZ+YVholcN6ET3eWQ=; b=IQNCCT8Za3zJnjRAIm4IKnE9npGXMde4rehwfuZ95SI1QZDEdS0j0KSk12BwgNjCFuOkS3jY+D8qWORYXitAra18piNr0JVVnpc99xV3g6pmH+bCHdcQjcrXKJvuWPWQXFxs/2cyNkBx76EBZvCulVxsimnVQAvN74InYB++De8=
Received: from MWHPR21MB0141.namprd21.prod.outlook.com (10.173.52.11) by MWHPR21MB0192.namprd21.prod.outlook.com (10.173.52.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1228.7; Thu, 4 Oct 2018 21:53:14 +0000
Received: from MWHPR21MB0141.namprd21.prod.outlook.com ([fe80::2cb2:4f75:71d1:7d93]) by MWHPR21MB0141.namprd21.prod.outlook.com ([fe80::2cb2:4f75:71d1:7d93%6]) with mapi id 15.20.1228.007; Thu, 4 Oct 2018 21:53:14 +0000
From: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
To: Lars Eggert <lars@eggert.org>
CC: IETF QUIC WG <quic@ietf.org>
Subject: RE: Spin bit decision
Thread-Topic: Spin bit decision
Thread-Index: AQHUWhYtwD17YLpD6kW5JiybEBbIRKULhImAgAAbI4CAACozgIAAHI6AgAAD4wCAAAMhAIAADuGAgAASIwCAAB1uAIAAWgsAgAFXUACAAceUgA==
Date: Thu, 4 Oct 2018 21:53:14 +0000
Message-ID: <MWHPR21MB01411212FF00421BD0C1EB3895EA0@MWHPR21MB0141.namprd21.prod.outlook.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9A63F295-5DC5-4992-9A9C-A98F72C8430D@eggert.org> <22440_1538469028_5BB32CA4_22440_292_2_8e00a462-2bbf-acf0-1195-74269a0c2fbd@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <4629_1538518470_5BB3EDC6_4629_90_1_071dda88-6bd8-fdf6-2321-d59c928ce904@orange.com> <CY4PR22MB098308F84A8FABCD2DB99B99DAE90@CY4PR22MB0983.namprd22.prod.outlook.com>
In-Reply-To: <CY4PR22MB098308F84A8FABCD2DB99B99DAE90@CY4PR22MB0983.namprd22.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e8:8:9528:bd8c:2e6c:8b2]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR21MB0192; 6:97vKcFuJCLkt2RONbl8OOvGU9IRXT51e64ltGgANierxKZ9I6xyLnWSLCpU79SMWfiFAEbyW8js+wRvHCtM7v7lCs8SxZg0ufWkFnP7o2Oqu9YgEAIEuRFzGqk1BBYB72REa1LzQKQEld8FrT7SGMbXSMkA2b6sE9ea3hG136hV5BAsElCjq5PRZ2L7xzF/KMbFWegliRvGSSZzrjxyEIelP+96sabY7CpOsrcuFAwF5H25UFchXgt4wdZO7e0oREQPGfPAdQc1Jp90ynzxDWhT8AZvmxgVYMo9x/h0mKTZX4wAOvAyOjZprCLNx469HUMCSw8jyP38mPF4HLBmF7jqO/4Nhv8WAHHAnMX2RzLg9Ztn8tnNRZxuKjffmcmXuw8777OJoH3K7zwJfrZeaq+dBuGBKK2DM/mLkzzvcXRdP0m9KSD9tWo9rmfwZSCJ2RiGZ+3WroYfXprg9EDm5SQ==; 5:3cBTA6s2XFSIuFsW/hqKVhGkS4mHnLp6LCPOVhNLLPK+5nL7wQtGxcUfPB5miRttnkl7gVuFnDG9loPJIeGbVmtHAjInUh9CSmHOx8p991p410RFJL+HG2aTexAtRxFmybH0IYzjFi1hpcGx5RPktFP3f23hgtIhk3AkmA98qjk=; 7:OLkmMrliLvYbp8S1bkZzCiXf2IWEn5wRZFBDN4HaLL7LDW72rNCKQ+pf6d65eqxa/asx9RbxBgwA5tcIs+dt+xM2Py0b9Y24CJCB21AAeD2TrE3d9DpjzLkbutd2l+W802y3t1Pxu1A01krcvxw85oASju95xKPuRXDYnPTZP33JEXYRmVDlhLpEdyvS6tapDkAU47E+4mRQKuukXPL7yqp43uLgrLTS+xLA/1KjUN8/mbXaoGsj3oSyMup0qZq/
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: aa34d5fc-1941-448e-724e-08d62a43c94e
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7193020); SRVR:MWHPR21MB0192; 
x-ms-traffictypediagnostic: MWHPR21MB0192:
x-microsoft-antispam-prvs: <MWHPR21MB01929E1F1CFA912CCF485DDD95EA0@MWHPR21MB0192.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3002001)(10201501046)(3231355)(944501410)(52105095)(2018427008)(93006095)(93001095)(6055026)(149066)(150057)(6041310)(20161123564045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(20161123560045)(20161123562045)(201708071742011)(7699051)(76991048); SRVR:MWHPR21MB0192; BCL:0; PCL:0; RULEID:; SRVR:MWHPR21MB0192; 
x-forefront-prvs: 0815F8251E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(366004)(396003)(39860400002)(376002)(346002)(199004)(189003)(86612001)(6246003)(81166006)(81156014)(86362001)(6346003)(4326008)(105586002)(7116003)(3480700004)(8936002)(8990500004)(106356001)(68736007)(71190400001)(5660300001)(10090500001)(7736002)(74316002)(305945005)(8676002)(71200400001)(5250100002)(256004)(25786009)(486006)(6116002)(14454004)(2900100001)(508600001)(53936002)(55016002)(476003)(186003)(7696005)(33656002)(97736004)(22452003)(99286004)(9686003)(316002)(446003)(76176011)(102836004)(11346002)(6436002)(93886005)(10290500003)(2906002)(6506007)(46003)(229853002)(6916009)(72206003); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR21MB0192; H:MWHPR21MB0141.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Gabriel.Montenegro@microsoft.com; 
x-microsoft-antispam-message-info: kFy4rZ1unJNQFereMU0cuHDMSEY615b9wfQVJ8XD5PGjUuWl6WJwljyACxqwuHc5lHr/geCF87KvzL6zANvKGKkbhgxMxAaTPEcVzH1bzCA18AxFxCQJHqFTRk+HaEvnPQdGoGbQXHYnk+CKETbPZqAyETmATK/EoOTUw/y9tgXoP3j9qxuuB4mMcL8upkeq/v5fIxbmzYIuUBSvNs8ZjbZVMqNnLfxyedeXrfwP4OUM2cBDkZGSRjNcYX/GZaK81lDTWny2x3STIVCUoUh0k4uXdBpK5YCqrZaCsRYHZCvibcH7zwnPY8QA4g0mkECN1M42F5LpAAc4d6fn0aEXicjjlpgvEsQIMp9FC5AmxQY=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: aa34d5fc-1941-448e-724e-08d62a43c94e
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Oct 2018 21:53:14.5618 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR21MB0192
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/QHN5Mpr3yhhT6ANHkNlV7CI1w7A>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Oct 2018 21:53:19 -0000

V2Ugc3VwcG9ydCBleHBsaWNpdCBzaWduYWxzIHByb3ZpZGVkIHRoZXJlIGFyZSBubyBhZGRpdGlv
bmFsIHByaXZhY3kgaW1wbGljYXRpb25zIGFuZCB0aGUgcGVyZm9ybWFuY2UgY29zdCBpcyBuZWds
aWdpYmxlLiBXZSBrbm93IHRoaXMgaXMgdHJ1ZSB0b2RheSBmb3IgdGhlIHNwaW4gYml0LiBXaGVy
ZWFzIHdlIGNhbm5vdCBtYWtlIGFueSBmdXR1cmUgcHJvZHVjdCBjb21taXRtZW50cywgd2UgYXJl
IGxpa2VseSB0byBpbmNsdWRlIGRlZmF1bHQgc3VwcG9ydCBmb3IgdGhlIHNwaW4gYml0IGluIG91
ciBjbGllbnQgYW5kIHNlcnZlciBRVUlDIGltcGxlbWVudGF0aW9uIGlmIGl0IGlzIHBhcnQgb2Yg
dGhlIFFVSUMgc3BlY2lmaWNhdGlvbi4NCg0KDQo=


From nobody Thu Oct  4 14:55:34 2018
Return-Path: <alexandre.ferrieux@orange.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 C632512D7EA for <quic@ietfa.amsl.com>; Thu,  4 Oct 2018 14:55:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.291
X-Spam-Level: 
X-Spam-Status: No, score=-0.291 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 zaevOX-NvC6m for <quic@ietfa.amsl.com>; Thu,  4 Oct 2018 14:55:31 -0700 (PDT)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41B12130934 for <quic@ietf.org>; Thu,  4 Oct 2018 14:55:31 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id 42R6Bn2RQnz5vp0; Thu,  4 Oct 2018 23:55:29 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 42R6Bn1hQNz1xnr; Thu,  4 Oct 2018 23:55:29 +0200 (CEST)
Received: from [10.193.4.89] (10.168.234.2) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 4 Oct 2018 23:55:28 +0200
Subject: Re: Spin bit as a negotiated option
To: Kazuho Oku <kazuhooku@gmail.com>
CC: IETF QUIC WG <quic@ietf.org>, Brian Trammell <ietf@trammell.ch>, Christian Huitema <huitema@huitema.net>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com> <CANatvzwzw7snBV4bXfhvWJk4znOmv0Er6kwidRR+dPQsfFczkw@mail.gmail.com>
From: <alexandre.ferrieux@orange.com>
Organization: Orange
Message-ID: <5571_1538690129_5BB68C51_5571_214_1_77c6c0d0-d40c-d44c-e763-bb955eef69ae@orange.com>
Date: Thu, 4 Oct 2018 23:55:28 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CANatvzwzw7snBV4bXfhvWJk4znOmv0Er6kwidRR+dPQsfFczkw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: [10.168.234.2]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7MpZ9gql9TfLnMeZaFXVB43kEYc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Oct 2018 21:55:33 -0000

On 10/04/18 23:40, Kazuho Oku wrote:
> 2018=E5=B9=B410=E6=9C=884=E6=97=A5(=E6=9C=A8) 19:46 <alexandre.ferrieux@o=
range.com>:
>>
>> Thanks Kazuho. Using version numbers directly was an obvious choice, but=
 so far
>> I was discouraged by strong language in the spec, saying 0x00000001 was =
the
>> unavoidable point of convergence after all 0xFF0000XX experiments. So in=
 essence
>> you're proposing to weaken that a bit, right ?
>=20
> I am not sure if we have reached consensus that QUICv1 should use
> 0x00000001 as the one and only number for the version number field.
>=20
> My understanding is that it is simply written as such because I-D is a
> draft of a RFC. A RFC needs to clarify the value of version number
> field it uses, and I-D needs to have a paragraph that amends on how
> the draft-versions uses the field.

OK, thanks for the clarification.

> I do not think we can segment the version number space, because IMO it
> essentially means making spin bits an invariant. My understanding is
> that spin bits is something specific to v1.
>=20
> QUICv1 might use different values on the version number field to
> represent if spin bits is (or other signals are) available, but that
> does not mean that v2 will expose the same signals or they would use
> the version number field for indicating that.
>=20
> If it is the case that the use of 0x1xx for V1 might give people the
> impression that the lower bits are used to indicate the availability
> of unencrypted signals across multiple versions, I think starting from
> 0x00000001 (i.e. the one you describe as "direct enumeration") would
> be preferable.

Crystal clear, and agreed:)

>> Also, are we sure that this explosion won't weigh on the new VN scheme, =
inducing
>> slower convergence due to longer lists on either side ?
>=20
> I do not think that is an issue for v1, because what currently at
> stake is if we should assign one or two extra version numbers (i.e.
> one for spin bit, and possibly another for spin+vec as a separate
> draft).
>=20
> If folks agree to expose other signals that requires a "configuration"
> to be exposed as well, then they can define a new version number that
> introduces a new field to the long header format for exposing the
> "configuration."

OK. So, wrapping up, and abstracting away for now the bit layout of the ver=
sion=20
number by using symbolic names, we'd start (right after Bangkok) with somet=
hing=20
like:

	- "v1"     =3D v1 without extensions
	- "v1s"    =3D v1 with spin bit only
	- "v1svv"  =3D v1 with spin bit and VEC
	- "v1sqr"  =3D v1 with spin bit and loss bits Q and R
	- etc (?)

One question though: what part of the version negotiation exchange is in cl=
ear ?
IOW, would the selected version always be exposed to the path, or should=20
spin-consumers rely on heuristics to guess the variant in use ?




___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Thu Oct  4 15:16:11 2018
Return-Path: <kazuhooku@gmail.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 3B894130DE3 for <quic@ietfa.amsl.com>; Thu,  4 Oct 2018 15:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 U_7KoxkWwp9D for <quic@ietfa.amsl.com>; Thu,  4 Oct 2018 15:16:06 -0700 (PDT)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 695DF130934 for <quic@ietf.org>; Thu,  4 Oct 2018 15:16:06 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id p1-v6so5954034ljg.6 for <quic@ietf.org>; Thu, 04 Oct 2018 15:16:06 -0700 (PDT)
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:content-transfer-encoding; bh=SQv0Xe+aP96jOqem/sHAjjgn3D5nHt0bIYZTgGBuUKQ=; b=Qk9Hv+58DfTAqEJndE7j1/Otk4LSToeL51JvYdu/57ak9x3iCXuaEriXbDEpo0Z7lf M8DGYol9QD4PGB8HslcV6oEXZOFiVAAkSi3k6sU9UunJEJcfgyTR+b4gdEL8RrXSngeu 7p08jIo4WdHJMDcy8G2cLVJbNMKbjOkKSL9De10sYtlt89V9cCret91JFgsH4FU0jSHW iC++6iqhG8p/LLPLispK614lMcaj1yYelpdeYzrhLPCmdBqwaMJQP2x0x8ju00d9mScN QPVyuKoMa9lm3yRoI1o1uI+1xvDDLgGvmy5l6EhZ0CWJZLVjSGeNB863VrTGWOTW7cA1 F18A==
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:content-transfer-encoding; bh=SQv0Xe+aP96jOqem/sHAjjgn3D5nHt0bIYZTgGBuUKQ=; b=JO9GmMNXMZkR/kWG0B/tG0xNC+jRbJNUS9iYCmOIB8uFq2fnW3ym0rUyOdw2i7h7ZD eQc7As1bgbDgFEDU5RIWpgQ6TVsVF5xdQ/EpQ2bXzg2dOMMauUthzze8vz6qyQjNMIWp +E0JngXoGV4wW9Y0tUDA0X6awyyyropGGPGgVa5f+Zh9imILJ8OzntIyx9xvpqoNrHmf o/1fYUaM2iag9A+eD5bT3CzGfbOvMs4bcf+YwP4DWGP+nqPp6fDE6/tlzadvF6TcL4cz rlQ3AvI+ejavtDXLcddsoTdLmB5yOTjcI4UUxSUC5P/8foBWrWhg7brBgkUjTqiTu1vF O1KQ==
X-Gm-Message-State: ABuFfohAWV2lSAb0+dpfw+c1kVULqYUADIG2DYDDvY/vV2LdS/ZlCM8T 4Bpg4B0zFhn/LSCB23iHOlXGXXrZ7w2StZf1oqA=
X-Google-Smtp-Source: ACcGV61imvEnK8AfiSW0PgziheeyTrmJ9JhRtRXToPW7lHqnXmzJf5nlKuXmIKuDWiNummcDX+j6kw1GP6ZiFr5bNYw=
X-Received: by 2002:a2e:350e:: with SMTP id z14-v6mr5221420ljz.49.1538691364554;  Thu, 04 Oct 2018 15:16:04 -0700 (PDT)
MIME-Version: 1.0
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com> <CANatvzwzw7snBV4bXfhvWJk4znOmv0Er6kwidRR+dPQsfFczkw@mail.gmail.com> <5571_1538690129_5BB68C51_5571_214_1_77c6c0d0-d40c-d44c-e763-bb955eef69ae@orange.com>
In-Reply-To: <5571_1538690129_5BB68C51_5571_214_1_77c6c0d0-d40c-d44c-e763-bb955eef69ae@orange.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Fri, 5 Oct 2018 07:15:54 +0900
Message-ID: <CANatvzyHUXSPsW84GE=-A4JNJTQ1rFtRgr1kvoxfOF9qGtws_A@mail.gmail.com>
Subject: Re: Spin bit as a negotiated option
To: Lili Peaudchien <alexandre.ferrieux@orange.com>
Cc: IETF QUIC WG <quic@ietf.org>, Brian Trammell <ietf@trammell.ch>,  Christian Huitema <huitema@huitema.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/5CGdr4Hgrq9GNPMdTZlnA80mrTw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Oct 2018 22:16:09 -0000

2018=E5=B9=B410=E6=9C=885=E6=97=A5(=E9=87=91) 6:55 <alexandre.ferrieux@oran=
ge.com>:
>
> On 10/04/18 23:40, Kazuho Oku wrote:
> > 2018=E5=B9=B410=E6=9C=884=E6=97=A5(=E6=9C=A8) 19:46 <alexandre.ferrieux=
@orange.com>:
> >>
> >> Thanks Kazuho. Using version numbers directly was an obvious choice, b=
ut so far
> >> I was discouraged by strong language in the spec, saying 0x00000001 wa=
s the
> >> unavoidable point of convergence after all 0xFF0000XX experiments. So =
in essence
> >> you're proposing to weaken that a bit, right ?
> >
> > I am not sure if we have reached consensus that QUICv1 should use
> > 0x00000001 as the one and only number for the version number field.
> >
> > My understanding is that it is simply written as such because I-D is a
> > draft of a RFC. A RFC needs to clarify the value of version number
> > field it uses, and I-D needs to have a paragraph that amends on how
> > the draft-versions uses the field.
>
> OK, thanks for the clarification.
>
> > I do not think we can segment the version number space, because IMO it
> > essentially means making spin bits an invariant. My understanding is
> > that spin bits is something specific to v1.
> >
> > QUICv1 might use different values on the version number field to
> > represent if spin bits is (or other signals are) available, but that
> > does not mean that v2 will expose the same signals or they would use
> > the version number field for indicating that.
> >
> > If it is the case that the use of 0x1xx for V1 might give people the
> > impression that the lower bits are used to indicate the availability
> > of unencrypted signals across multiple versions, I think starting from
> > 0x00000001 (i.e. the one you describe as "direct enumeration") would
> > be preferable.
>
> Crystal clear, and agreed:)
>
> >> Also, are we sure that this explosion won't weigh on the new VN scheme=
, inducing
> >> slower convergence due to longer lists on either side ?
> >
> > I do not think that is an issue for v1, because what currently at
> > stake is if we should assign one or two extra version numbers (i.e.
> > one for spin bit, and possibly another for spin+vec as a separate
> > draft).
> >
> > If folks agree to expose other signals that requires a "configuration"
> > to be exposed as well, then they can define a new version number that
> > introduces a new field to the long header format for exposing the
> > "configuration."
>
> OK. So, wrapping up, and abstracting away for now the bit layout of the v=
ersion
> number by using symbolic names, we'd start (right after Bangkok) with som=
ething
> like:
>
>         - "v1"     =3D v1 without extensions
>         - "v1s"    =3D v1 with spin bit only
>         - "v1svv"  =3D v1 with spin bit and VEC
>         - "v1sqr"  =3D v1 with spin bit and loss bits Q and R
>         - etc (?)

Yes.

We will have "v1" and "v1s", assuming that we would agree to ship the
one-bit "spin bit" approach as part of QUICv1. People will also have
the freedom for using more bits for the flavors (e.g. "v1svvv",
"v1sqr").

>
> One question though: what part of the version negotiation exchange is in =
clear ?
> IOW, would the selected version always be exposed to the path, or should
> spin-consumers rely on heuristics to guess the variant in use ?

My understanding is (assuming #1755 gets merged):
* the version number field of a long header would always be "v1" for
the first Initial sent from the client
* the value would be the negotiated version for exchanges that follows that
* there is no version number field in the short header

Therefore, for each path identified the 5-tuple, an observer would
remember the version number of the last long header packet that it has
seen (or it could remember the version number of any Handshake
packet), and use that to determine what is being exposed on the wire.
No heuristics is required.

OTOH, because version number field does not exist in the short header,
an observer cannot determine if any signal is exposed for a connection
after it migrates to a 5-tuple, or for a connection that has been
alive before starting the observation. Use of heuristics would be the
only way for such cases.

>
>
>
>
> _________________________________________________________________________=
________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confid=
entielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez re=
cu 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 o=
u falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged i=
nformation 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 de=
lete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have bee=
n modified, changed or falsified.
> Thank you.
>


--=20
Kazuho Oku


From nobody Thu Oct  4 15:40:12 2018
Return-Path: <mbishop@evequefou.be>
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 2E456128CB7 for <quic@ietfa.amsl.com>; Thu,  4 Oct 2018 15:40:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 dyC8Qoi7n67S for <quic@ietfa.amsl.com>; Thu,  4 Oct 2018 15:40:06 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0728.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe45::728]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17CF4126DBF for <quic@ietf.org>; Thu,  4 Oct 2018 15:40:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=hWJbTyXxVvaT4IhuzaXBe7Y5x0AlRZY8zPE10HRah7o=; b=eYDX9u0czzMTa256E0HbgGzWL+i07hJIz+Pcgg2B1MHBl7AWgEDLqkTmkgeLRq89laxSSVK4gH6jOAves0RIyjBlWbwv9iS23Sr3sSzM+v73ROjkOxo9rBfhUgdg5uP2JyAdEaZkTNhf6EXYLgrfcd72zMkzYGvo8aTuMSp+7Ak=
Received: from CY4PR22MB0983.namprd22.prod.outlook.com (10.171.171.20) by CY4PR22MB0343.namprd22.prod.outlook.com (10.173.194.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1185.25; Thu, 4 Oct 2018 22:40:02 +0000
Received: from CY4PR22MB0983.namprd22.prod.outlook.com ([fe80::f4f6:67f1:e04e:7f6a]) by CY4PR22MB0983.namprd22.prod.outlook.com ([fe80::f4f6:67f1:e04e:7f6a%5]) with mapi id 15.20.1207.018; Thu, 4 Oct 2018 22:40:02 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, Kazuho Oku <kazuhooku@gmail.com>
CC: Brian Trammell <ietf@trammell.ch>, IETF QUIC WG <quic@ietf.org>, Christian Huitema <huitema@huitema.net>
Subject: RE: Spin bit as a negotiated option
Thread-Topic: Spin bit as a negotiated option
Thread-Index: AQHUWwDL3eYd6OM/2EiT5VFIc0lTpKUO2VEAgAAPtACAALED4A==
Date: Thu, 4 Oct 2018 22:40:02 +0000
Message-ID: <CY4PR22MB0983849F01312CBE18A4F69CDAEA0@CY4PR22MB0983.namprd22.prod.outlook.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com>
In-Reply-To: <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [2601:600:8080:701:e970:c0e5:e9fa:7bb2]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR22MB0343; 6:0GS3COOdAFeIfjm5+aQF1X5Ue9fLwfaGZMYYHbfGfiE5zCeSG7k/oVmQL0C5+p0nhUp/uQb8ndU0CtJNoapDhEdtFVsB66IzPwF+GzXUBg4m4adLevWD/b7QclVcQUENx9g2L93dleFROlii9XNScJd/EU1jjauEwJ3lq/xH1ksbBwC9+NVjs3anBOfYTgLn+R+3cchehxq7Q+xrJUyAmNBeXMj4eahMiPoEBj67YItxUyR/umhh705WpSaUAYybXFX7IcWLHlInaag2M5D1OaCBTohpq1sJ/x8LK6t9SVzZyCCcYLseIx8u+JERoIAmVkMVHWgx7r5VXwy5Eqdkry0BhIoPhoOqo+7HA1JNgSjc/CKMTUWE0WfyxgJWgRHStX5k1Vtb1/MucgRUzi4aWzWtOE8GhjKAxVH7X+0CGvUNu3Ce6xhEXiNkYOI1GTDP13InNydO67gxx6+gviGiUA==; 5:By5UWM+DPgq4Fcv56tYjU/WzxkTeDu0yQK7R/xFk7BtkM2GGGsKxRDI3OO/6aS/RlEKLt/66dwMllaaUgTeVeecyuPFwx4wulLK5M5OGTKzOWbq+9XjxYcLJj36f2OaslUdQq9vOOZ8lww0+e47dUAZI9xF0wS3Osi5znZd+THk=; 7:fXw2G4t1rcgImXPryjXJzZjc4ea/US9t7v6pOK85m9Gm1PGQU6dgT4MBV0ExFbuEkDzndMYYGt8LvL0+6KLVO4Q3nVgnFl5WJQuTBuPqKnR3Tvcqd8jNfIqJyfpZXywWVGAfoQ3xn5Y1ymHCyuc7eodmzfcqXzvge1OY4oRitT4MWIt1SbEqXSfeciapc3asml9ExXUrdecnbOeCsYNCL2ciyRWXGNL5BaAyHU0idC18ot3QyRE0DmN20D2q6CYH
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 6e5aa264-bb17-42c9-ae64-08d62a4a530b
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:CY4PR22MB0343; 
x-ms-traffictypediagnostic: CY4PR22MB0343:
x-microsoft-antispam-prvs: <CY4PR22MB03431AF7B8E7F36E388CA53EDAEA0@CY4PR22MB0343.namprd22.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(18271650672692)(161740460382875)(100405760836317)(85827821059158); 
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231355)(944501410)(52105095)(149066)(150057)(6041310)(20161123562045)(20161123558120)(20161123564045)(2016111802025)(20161123560045)(6043046)(201708071742011)(7699051); SRVR:CY4PR22MB0343; BCL:0; PCL:0; RULEID:; SRVR:CY4PR22MB0343; 
x-forefront-prvs: 0815F8251E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(366004)(346002)(376002)(396003)(39830400003)(199004)(189003)(13464003)(102836004)(14454004)(6436002)(14444005)(9686003)(8936002)(106356001)(8676002)(93886005)(6116002)(54906003)(81166006)(86362001)(256004)(105586002)(99286004)(74482002)(2501003)(110136005)(81156014)(53936002)(114624004)(55016002)(6246003)(5024004)(5250100002)(53546011)(39060400002)(6506007)(446003)(76176011)(476003)(71190400001)(2900100001)(345774005)(305945005)(33656002)(561944003)(7736002)(508600001)(11346002)(71200400001)(229853002)(7696005)(2906002)(46003)(551934003)(186003)(74316002)(5660300001)(4326008)(25786009)(68736007)(97736004)(316002)(486006)(414714003)(473944003); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR22MB0343; H:CY4PR22MB0983.namprd22.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: D2joHQmSjWuZyIz/mj96SGwCcQAeoAMbwdH264UOp9TI1fIodtRFmAvH/ahxMMQL+QkmjqJ3Sk0DC1pDJKXM4FwXET8i3aY+MZ5Dvr5AaBJvuS2Cu/ouhprgn+HoEqssPmhpQFRyHl79yMXEPyx2s8i8Ky5S1mbD1gKtm/bKzehP3T0ZSOf17piYBzeC2N2/fvaMZHAg6IzDV7oQyKZlDLbzHonOH8E42dzoXZo7oeSvkCo25cDG5Z5ocSRmbCUzwoPxRUBDuE0KFHgv/tLex6ukcqW7ntS67+fFRsjMEXJHpfrBdg614VUS3C3/iKk/Y51UPSEa7aNJO/fyufmd3HCDMshxHA6+x38VJ3USX44=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 6e5aa264-bb17-42c9-ae64-08d62a4a530b
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Oct 2018 22:40:02.7943 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR22MB0343
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/19kpLUe9xhIQJ5PCFl-8qadGU9E>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Oct 2018 22:40:10 -0000

U28gbG9uZyBhcyB0aGlzIGlzIHRoZSBvbmx5IHRoaW5nIGJlaW5nIG5lZ290aWF0ZWQsIGl0J3Mg
bm90IHRvbyBiYWQuICBJZiB3ZSB3YW50IHRvIG5lZ290aWF0ZSBvdGhlciB0aGluZ3MsIGl0IHF1
aWNrbHkgZ2V0cyBvdXQgb2YgaGFuZC4gIE9uZSBjb3VsZCBwbGF1c2libHkgYXJndWUgdGhhdCB0
aGUgc3BpbiBiaXQgaXMgc3BlY2lhbCBpbiB0aGF0IHdlIGFjdHVhbGx5IHdhbnQgcGFydGllcyBv
YnNlcnZpbmcgdGhlIHRyYW5zYWN0aW9uIHRvIHVuZGVyc3RhbmQgd2hpY2ggb3B0aW9uIGhhcyBi
ZWVuIHNlbGVjdGVkLg0KDQpJdCdzIGltcG9ydGFudCB0byByZW1lbWJlciwgdGhvdWdoLCB0aGF0
IHRoaXMgaXMgaW5mb3JtYXRpb24geW91IGdldCBvbmx5IGF0IHRoZSBiZWdpbm5pbmcgb2YgYSBu
ZXcgY29ubmVjdGlvbi4gIElmIHRoZXJlJ3MgbWlncmF0aW9uIG9yIE5BVCByZWJpbmRpbmcsIGl0
J3Mgbm90IGd1YXJhbnRlZWQgKGFuZCBpbiBmYWN0LCBub3QgaW50ZW5kZWQpIHRoYW4geW91IGNh
biBjb3JyZWxhdGUgaXQgYmFjayB0byBhIHBhcnRpY3VsYXIgcHJldmlvdXMgaGFuZHNoYWtlLiAg
WW91J2xsIHN0aWxsIGVpdGhlciBuZWVkIGhldXJpc3RpY3MgdG8gaWRlbnRpZnkgd2hldGhlciB0
aGUgc3BpbiBiaXQgaXMgYWN0dWFsbHkgaW4gdXNlLCBvciB5b3UnbGwgbmVlZCB0byBpZ25vcmUg
YW55IHRyYWZmaWMgZm9yIHdoaWNoIHlvdSBkaWRuJ3Qgc2VlIHRoZSBoYW5kc2hha2UuDQoNCi0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBRVUlDIDxxdWljLWJvdW5jZXNAaWV0Zi5v
cmc+IE9uIEJlaGFsZiBPZiBhbGV4YW5kcmUuZmVycmlldXhAb3JhbmdlLmNvbQ0KU2VudDogVGh1
cnNkYXksIE9jdG9iZXIgNCwgMjAxOCAzOjQ3IEFNDQpUbzogS2F6dWhvIE9rdSA8a2F6dWhvb2t1
QGdtYWlsLmNvbT4NCkNjOiBCcmlhbiBUcmFtbWVsbCA8aWV0ZkB0cmFtbWVsbC5jaD47IElFVEYg
UVVJQyBXRyA8cXVpY0BpZXRmLm9yZz47IENocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRl
bWEubmV0Pg0KU3ViamVjdDogUmU6IFNwaW4gYml0IGFzIGEgbmVnb3RpYXRlZCBvcHRpb24NCg0K
VGhhbmtzIEthenVoby4gVXNpbmcgdmVyc2lvbiBudW1iZXJzIGRpcmVjdGx5IHdhcyBhbiBvYnZp
b3VzIGNob2ljZSwgYnV0IHNvIGZhciBJIHdhcyBkaXNjb3VyYWdlZCBieSBzdHJvbmcgbGFuZ3Vh
Z2UgaW4gdGhlIHNwZWMsIHNheWluZyAweDAwMDAwMDAxIHdhcyB0aGUgdW5hdm9pZGFibGUgcG9p
bnQgb2YgY29udmVyZ2VuY2UgYWZ0ZXIgYWxsIDB4RkYwMDAwWFggZXhwZXJpbWVudHMuIFNvIGlu
IGVzc2VuY2UgeW91J3JlIHByb3Bvc2luZyB0byB3ZWFrZW4gdGhhdCBhIGJpdCwgcmlnaHQgPw0K
DQpJZiBzbywgaG93IGRvIHlvdSBlbnZpc2lvbiBzZWdtZW50aW5nIHRoZSB2ZXJzaW9uIG51bWJl
ciBzcGFjZSA/DQoNCiAgLSBkaXJlY3QgZW51bWVyYXRpb246DQoNCgkweDAwMDAwMDAxID0gdjFk
cnkNCgkweDAwMDAwMDAyID0gdjEgKyBzcGluYml0DQoJMHgwMDAwMDAwMyA9IHYxICsgc3BpbmJp
dCArIFZFQw0KCQ0KICAtIGxvdyBvcmRlciBiaXRzIGZvciBvcHRpb25zOg0KDQoJMHgwMDAwMDFY
WCA9IHYxICsgb3B0aW9uIFhYDQoJMHgwMDAwMDJZWSA9IHYyICsgb3B0aW9uIFlZDQoNCkFsc28s
IGFyZSB3ZSBzdXJlIHRoYXQgdGhpcyBleHBsb3Npb24gd29uJ3Qgd2VpZ2ggb24gdGhlIG5ldyBW
TiBzY2hlbWUsIGluZHVjaW5nIHNsb3dlciBjb252ZXJnZW5jZSBkdWUgdG8gbG9uZ2VyIGxpc3Rz
IG9uIGVpdGhlciBzaWRlID8NCg0KT24gMTAvMDQvMTggMTE6NTAsIEthenVobyBPa3Ugd3JvdGU6
DQo+IEhpLA0KPiANCj4gVGhhbmsgeW91IGZvciBzdGFydGluZyB0aGUgZGlzY3Vzc2lvbiBzcGVj
aWZpYyB0byBob3cgd2UgY291bGQgDQo+IHBvc3NpYmx5IG5lZ290aWF0ZSB0aGUgdXNlIG9mIHNw
aW4gYml0cy4NCj4gDQo+IFJlZ2FyZGluZyB0aGUgdG9waWMsIG15IHByZWZlcmVuY2UgZ29lcyB0
byB1c2luZyB0aGUgdmVyc2lvbiBudW1iZXIgDQo+IGZpZWxkIG9mIHRoZSBsb25nIGhlYWRlciBm
b3IgbmVnb3RpYXRpbmcgdGhlIHByZXNlbmNlIG9mIHNwaW4gYml0cywgb3IgDQo+IGFueSBhZGRp
dGlvbmFsIHNpZ25hbCBiZWluZyBleHBvc2VkIHRvIHRoZSBuZXR3b3JrLg0KPiANCj4gRm9yIGV4
YW1wbGUsIFFVSUN2MSB3aXRob3V0IHNwaW4gYml0IGNvdWxkIHVzZSB2ZXJzaW9uIDB4MTAxLCBh
bmQgdjEgDQo+IHdpdGggc3BpbiBiaXQgY291bGQgdXNlIDB4MTAyLiBJbiB0aGUgZnV0dXJlLCB3
ZSBjYW4gYXNzaWduIGEgDQo+IGRpZmZlcmVudCB2ZXJzaW9uIG51bWJlciBmb3IgUVVJQ3YxIHdp
dGggbXVsdGlwbGUgc3BpbiArIFZFQyAob3IgDQo+IHBlb3BsZSBpbnRlcmVzdGVkIGluIHRlc3Rp
bmcgdGhlIGZlYXR1cmUgY2FuIGRlc2lnbmF0ZSBhIHByaXZhdGUgDQo+IHZlcnNpb24gbnVtYmVy
IGV2ZW4gYmVmb3JlIHRoYXQpLg0KPiANCj4gSSBzZWUgdGhlIGZvbGxvd2luZyBiZW5lZml0cyB0
byB1c2luZyB0aGUgdmVyc2lvbiBmaWVsZCBhcyBhIG1ldGhvZCB0byANCj4gbmVnb3RpYXRlIHRo
ZSB1c2Ugb2Ygc3BpbiBiaXRzLg0KPiANCj4gMS4gT25lIG9mIHRoZSBjb25jZXJuIHJlZ2FyZGlu
ZyBzcGluIGJpdHMgaGFzIGJlZW4gdGhhdCB0aGV5IGNvdWxkIA0KPiBsZWFkIHRvIG9zc2lmaWNh
dGlvbi4gU3BpbiBiaXRzIGFyZSBub3QgcGFydCBvZiB0aGUgSW52YXJpYW50cywgYnV0IGlmIA0K
PiB0aGUgb2JzZXJ2YXRpb24gdG9vbHMgc3RhcnQgbG9va2luZyBhdCB0aG9zZSBiaXRzIHdpdGhv
dXQgY2hlY2tpbmcgdGhlIA0KPiB2ZXJzaW9uIG51bWJlciBmaWVsZCwgd2Ugd2lsbCBoYXZlIHRo
ZSBwcmVzc3VyZSB0byBub3QgY2hhbmdlIGhvdyB0aGUgDQo+IGJpdHMgYXJlIHVzZWQuIFVzaW5n
IHRoZSB2ZXJzaW9uIG51bWJlciB0byBpbmRpY2F0ZSB0aGUgcHJlc2VuY2Ugb2YgDQo+IHNwaW4g
Yml0cyBpcyB0aGUgYmVzdCBhcHByb2FjaCB0byByZXNvbHZlIHN1Y2ggY29uY2Vybi4NCj4gDQo+
IDIuIFdlIGhhdmUgaG9wZWQgdG8gcm9sbCBvdXQgbXVsdGlwbGUgdmVyc2lvbnMgb2YgUVVJQyBp
biBhIHNtYWxsIA0KPiBpbnRlcnZhbCBzbyB0aGF0IHRoZSB2ZXJzaW9uIG51bWJlciBmaWVsZCBk
b2VzIG5vdCBnZXQgb3NzaWZpZWQuIFRoZSANCj4gYmVzdCBzb2x1dGlvbiBpcyBvYnZpb3VzbHkg
dG8gcm9sbCBvdXQgdHdvIGZsYXZvcnMgb2YgdGhlIHByb3RvY29sIA0KPiB0aGF0IHVzZXMgZGlm
ZmVyZW50IHZlcnNpb24gbnVtYmVycyBhdCB0aGUgc2FtZSB0aW1lLiBXZSB3aWxsIGhhdmUgYSAN
Cj4gcmVhbC13b3JsZCB1c2Ugb2YgdmVyc2lvbiBuZWdvdGlhdGlvbiBmcm9tIGRheSBvbmUsIGJl
Y2F1c2Ugd2UgYXJlIGluIA0KPiBhIGNvbmRpdGlvbiB3aGVyZSBpbXBsZW1lbnRvcnMgaGF2ZSBk
aWZmZXJlbnQgb3BpbmlvbnMgb24gaWYgdGhleSANCj4gc2hvdWxkIHN1cHBvcnQgc3BpbiBiaXQg
Oi0pDQo+IA0KPiBUaGUgYmxvY2tlciB0byB0aGlzIGFwcHJvYWNoIGhhcyBiZWVuIHZlcnNpb24g
bmVnb3RpYXRpb24gcmVxdWlyaW5nIGFuIA0KPiBhZGRpdGlvbmFsIHJvdW5kLXRyaXAsIGJ1dCB0
aGF0IGlzIGdvaW5nIHRvIGJlIHJlc29sdmVkIGJ5ICMxNzU1Lg0KPiANCj4gMjAxOOW5tDEw5pyI
M+aXpSjmsLQpIDE5OjA2IDxhbGV4YW5kcmUuZmVycmlldXhAb3JhbmdlLmNvbT46DQo+Pg0KPj4g
T24gMTAvMDMvMTggMDk6NTgsIEJyaWFuIFRyYW1tZWxsIChJRVRGKSB3cm90ZToNCj4+ID4gQmFj
a2luZyBvZmYgdGhlIE1VU1QgZm9yIG5vdyBmb3Igc3VjaCBzaXR1YXRpb25zIGlzIElNTyBhIGdv
b2QgDQo+PiA+IHRyYWRlb2ZmLCB0aG91Z2gsIGVzcGVjaWFsbHkgc2luY2Ugd2Ugb25seSBuZWVk
IGZyYWN0aW9ucyBvZiBhIA0KPj4gPiBwZXJjZW50IG9mIGRlcGxveW1lbnQgdG8gc3RhcnQgc2Vl
aW5nIHVzZWZ1bCBzaWduYWwgZm9yIA0KPj4gPiBiYXNlbGluZS9hbm9tYWx5IG1lYXN1cmVtZW50
IG9mIGxhcmdlIGFnZ3JlZ2F0ZXMuDQo+Pg0KPj4gSWYgdGhlIGNvbnNlbnN1cyBpcyB0aGF0IHdl
IG11c3QgYWxsb3cgZm9yIHN1Y2ggc2l0dWF0aW9ucywgdGhlbiANCj4+IHRoZXJlIGFyZSB0d28N
Cj4+IHBvc3NpYmlsaXRpZXM6DQo+Pg0KPj4gICAoYSkgd2VhayBzcGVjIGxhbmd1YWdlIChNQVkg
V0lTSCBUTyBvciBzaW1pbGFyKSA9PiBtYW55IA0KPj4gaW1wbGVtZW50YXRpb25zIHdpbGwgc2lt
cGx5IGRyb3AgaXQNCj4+DQo+PiAgIChiKSBuZWdvdGlhdGVkIG9wdGlvbiB3aGVyZSB0aGUgbmVn
b3RpYXRpb24gbWVjaGFuaXNtIGlzIG1hbmRhdG9yeQ0KPj4NCj4+IEluIHRoZSB2ZWluIG9mIChi
KSwgQ2hyaXN0aWFuIHN1Z2dlc3RlZCBvZmZsaW5lIHRvIGludHJvZHVjZSANCj4+IG5lZ290aWF0
aW9uIHRvIGFsbG93IGZvciBleHBlcmltZW50YXRpb24gb2YgdGhlIHJlbWFpbmluZyB0d28gDQo+
PiByZXNlcnZlZCBiaXRzLiBUaGVuIG1heSBiZSB3ZSBjYW4gc3ludGhlc2l6ZSBib3RoIGlkZWFz
IGJ5IHRoZSBmb2xsb3dpbmcgcHJvcG9zYWw6DQo+Pg0KPj4gICAtIGluIHRoZSBmaXJzdCBmZXcg
ZXhjaGFuZ2VzIG9mIHRoZSA1LXR1cGxlLCB1c2UgdGhlIHRocmVlIGJpdHMgZm9yIA0KPj4gb3B0
aW9uIG5lZ290aWF0aW9uDQo+Pg0KPj4gICAtIHRoZW4gdXNlIHRoZW0gYXMgZGVmaW5lZCBieSB0
aGUgc2VsZWN0ZWQgb3B0aW9uDQo+Pg0KPj4gRXhhbXBsZSBlbmNvZGluZ3M6DQo+Pg0KPj4gICAw
MDAgOiBub3RoaW5nDQo+PiAgIDAwMSA6IHNwaW4gYml0IGFsb25lIDogUzAwDQo+PiAgIDAxMCA6
IHNwaW4gYml0ICsgVkVDIDogU1ZWDQo+PiAgIC4uLiA6IG90aGVyIGV4dGVuc2lvbnMNCj4+DQo+
PiBUaGUgbmVnb3RpYXRpb24gbWVjaGFuaXNtIGFsbG93cyBib3RoIGVuZHBvaW50cyB0byBmb3Jj
ZSAwMDAuDQo+PiBBbmQgc2luY2UgaXQgaXMgaW4gdGhlIGNsZWFyIGZpcnN0IGJ5dGUsIGl0IGFs
bG93cyBvbi1wYXRoIG9ic2VydmVycyANCj4+IHRvIGlkZW50aWZ5IHRoZSBvcHRpb24gd2l0aG91
dCByZXNvcnRpbmcgdG8gaGV1cmlzdGljczsgdGhpcyBoZWxwcyBpbiANCj4+IHRoZSBjYXNlIG9m
IGEgc21hbGwgc3VwcG9ydCByYXRpby4NCj4+DQo+Pg0KPj4NCj4+DQo+PiBfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
Cj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
Cj4+DQo+PiBDZSBtZXNzYWdlIGV0IHNlcyBwaWVjZXMgam9pbnRlcyBwZXV2ZW50IGNvbnRlbmly
IGRlcyBpbmZvcm1hdGlvbnMgDQo+PiBjb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVzIGV0
IG5lIGRvaXZlbnQgZG9uYyBwYXMgZXRyZSBkaWZmdXNlcywgDQo+PiBleHBsb2l0ZXMgb3UgY29w
aWVzIHNhbnMgYXV0b3Jpc2F0aW9uLiBTaSB2b3VzIGF2ZXogcmVjdSBjZSBtZXNzYWdlIA0KPj4g
cGFyIGVycmV1ciwgdmV1aWxsZXogbGUgc2lnbmFsZXIgYSBsJ2V4cGVkaXRldXIgZXQgbGUgZGV0
cnVpcmUgYWluc2kgcXVlIGxlcyBwaWVjZXMgam9pbnRlcy4gTGVzIG1lc3NhZ2VzIGVsZWN0cm9u
aXF1ZXMgZXRhbnQgc3VzY2VwdGlibGVzIGQnYWx0ZXJhdGlvbiwgT3JhbmdlIGRlY2xpbmUgdG91
dGUgcmVzcG9uc2FiaWxpdGUgc2kgY2UgbWVzc2FnZSBhIGV0ZSBhbHRlcmUsIGRlZm9ybWUgb3Ug
ZmFsc2lmaWUuIE1lcmNpLg0KPj4NCj4+IFRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRz
IG1heSBjb250YWluIGNvbmZpZGVudGlhbCBvciANCj4+IHByaXZpbGVnZWQgaW5mb3JtYXRpb24g
dGhhdCBtYXkgYmUgcHJvdGVjdGVkIGJ5IGxhdzsgdGhleSBzaG91bGQgbm90IGJlIGRpc3RyaWJ1
dGVkLCB1c2VkIG9yIGNvcGllZCB3aXRob3V0IGF1dGhvcmlzYXRpb24uDQo+PiBJZiB5b3UgaGF2
ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIg
YW5kIGRlbGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cy4NCj4+IEFzIGVtYWls
cyBtYXkgYmUgYWx0ZXJlZCwgT3JhbmdlIGlzIG5vdCBsaWFibGUgZm9yIG1lc3NhZ2VzIHRoYXQg
aGF2ZSBiZWVuIG1vZGlmaWVkLCBjaGFuZ2VkIG9yIGZhbHNpZmllZC4NCj4+IFRoYW5rIHlvdS4N
Cj4+DQo+IA0KPiANCg0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18NCg0KQ2UgbWVzc2FnZSBldCBzZXMgcGllY2VzIGpv
aW50ZXMgcGV1dmVudCBjb250ZW5pciBkZXMgaW5mb3JtYXRpb25zIGNvbmZpZGVudGllbGxlcyBv
dSBwcml2aWxlZ2llZXMgZXQgbmUgZG9pdmVudCBkb25jIHBhcyBldHJlIGRpZmZ1c2VzLCBleHBs
b2l0ZXMgb3UgY29waWVzIHNhbnMgYXV0b3Jpc2F0aW9uLiBTaSB2b3VzIGF2ZXogcmVjdSBjZSBt
ZXNzYWdlIHBhciBlcnJldXIsIHZldWlsbGV6IGxlIHNpZ25hbGVyIGEgbCdleHBlZGl0ZXVyIGV0
IGxlIGRldHJ1aXJlIGFpbnNpIHF1ZSBsZXMgcGllY2VzIGpvaW50ZXMuIExlcyBtZXNzYWdlcyBl
bGVjdHJvbmlxdWVzIGV0YW50IHN1c2NlcHRpYmxlcyBkJ2FsdGVyYXRpb24sIE9yYW5nZSBkZWNs
aW5lIHRvdXRlIHJlc3BvbnNhYmlsaXRlIHNpIGNlIG1lc3NhZ2UgYSBldGUgYWx0ZXJlLCBkZWZv
cm1lIG91IGZhbHNpZmllLiBNZXJjaS4NCg0KVGhpcyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVu
dHMgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIG9yIHByaXZpbGVnZWQgaW5mb3JtYXRpb24gdGhh
dCBtYXkgYmUgcHJvdGVjdGVkIGJ5IGxhdzsgdGhleSBzaG91bGQgbm90IGJlIGRpc3RyaWJ1dGVk
LCB1c2VkIG9yIGNvcGllZCB3aXRob3V0IGF1dGhvcmlzYXRpb24uDQpJZiB5b3UgaGF2ZSByZWNl
aXZlZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgYW5kIGRl
bGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cy4NCkFzIGVtYWlscyBtYXkgYmUg
YWx0ZXJlZCwgT3JhbmdlIGlzIG5vdCBsaWFibGUgZm9yIG1lc3NhZ2VzIHRoYXQgaGF2ZSBiZWVu
IG1vZGlmaWVkLCBjaGFuZ2VkIG9yIGZhbHNpZmllZC4NClRoYW5rIHlvdS4NCg0K


From nobody Fri Oct  5 03:15:23 2018
Return-Path: <marcus.ihlar@ericsson.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 A7771130E02 for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 03:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.756
X-Spam-Level: 
X-Spam-Status: No, score=-4.756 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=cVzirlUP; dkim=pass (1024-bit key) header.d=ericsson.com header.b=hItKr6bC
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 3A-teOt7-4SX for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 03:15:18 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 BB9E0130E0A for <quic@ietf.org>; Fri,  5 Oct 2018 03:15:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1538734515; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=jrHD7Q3Lhjr9E+sMjI+UZwcXpvp/FXP5kzM+MgZV4Zs=; b=cVzirlUP3seNJNgQff/Nfwl1tHkIRHXMzeYAQwNVokoleCr3lV8LPidQdOFaKoO3 oVgV9LHGgtN3PViRukzKLwqO9L1kPgX73+ZkWFx1jv1jG2QK3HXFKOPV4nxtp9Cb lw6xJKTNiwRVf5K6p0+1ZbO2GOXnjBtFYT0A1qRurQw=;
X-AuditID: c1b4fb3a-99fff70000002fc1-be-5bb739b30360
Received: from ESESSMB503.ericsson.se (Unknown_Domain [153.88.183.121]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 36.08.12225.3B937BB5; Fri,  5 Oct 2018 12:15:15 +0200 (CEST)
Received: from ESESBMR506.ericsson.se (153.88.183.202) by ESESSMB503.ericsson.se (153.88.183.121) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 5 Oct 2018 12:15:15 +0200
Received: from ESESBMB501.ericsson.se (153.88.183.168) by ESESBMR506.ericsson.se (153.88.183.202) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 5 Oct 2018 12:15:15 +0200
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (153.88.183.157) by ESESBMB501.ericsson.se (153.88.183.168) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Fri, 5 Oct 2018 12:15:15 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jrHD7Q3Lhjr9E+sMjI+UZwcXpvp/FXP5kzM+MgZV4Zs=; b=hItKr6bCrRKUpLpIj0YLyEPNT3vE+vb0dPQ3yGoe1sGo6wGd2uf3+PoezlBXkYE1mZKcCHUVCABm8H3GOgK1atC4gRIs6Y67q9442Da30jtxbH7CL8ckZT7Wa1oGb8+mjAFC3ly9AIzV61nbp0OlD19DIvh9M5O12Bqzyqlt+MA=
Received: from HE1PR0701MB2393.eurprd07.prod.outlook.com (10.168.128.12) by HE1PR0701MB2922.eurprd07.prod.outlook.com (10.168.92.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1207.15; Fri, 5 Oct 2018 10:15:13 +0000
Received: from HE1PR0701MB2393.eurprd07.prod.outlook.com ([fe80::400d:3614:de33:b3a8]) by HE1PR0701MB2393.eurprd07.prod.outlook.com ([fe80::400d:3614:de33:b3a8%4]) with mapi id 15.20.1228.011; Fri, 5 Oct 2018 10:15:13 +0000
From: Marcus Ihlar <marcus.ihlar@ericsson.com>
To: "mbishop@evequefou.be" <mbishop@evequefou.be>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, "kazuhooku@gmail.com" <kazuhooku@gmail.com>
CC: "ietf@trammell.ch" <ietf@trammell.ch>, "quic@ietf.org" <quic@ietf.org>, "huitema@huitema.net" <huitema@huitema.net>
Subject: RE: Spin bit as a negotiated option
Thread-Topic: Spin bit as a negotiated option
Thread-Index: AQHUWwDJ8lpz5mbOFU6DOhcb6dfH26UO2VEAgAAPtACAAMdZAIAAuUuA
Date: Fri, 5 Oct 2018 10:15:13 +0000
Message-ID: <HE1PR0701MB2393C0B9756449E5CC060723E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com> <CY4PR22MB0983849F01312CBE18A4F69CDAEA0@CY4PR22MB0983.namprd22.prod.outlook.com>
In-Reply-To: <CY4PR22MB0983849F01312CBE18A4F69CDAEA0@CY4PR22MB0983.namprd22.prod.outlook.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=marcus.ihlar@ericsson.com; 
x-originating-ip: [192.176.1.95]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR0701MB2922; 6:9mDUnEQ/V/B9ywe/9XAdlsHhDEWqZN7hXjKit+58cs8xt8UpIRK9+FumtRmmcQfdflGHf17RVpGF3PF9mzIDMO5h1JEspojlrHvlG358XRUFn9STXpMrx51JGA6BeAeyhRPMs/47TOZAUt6m7gtPNpq2bKLGMv6mvAVgNGiJq7lgrQNET8+CvKKZqSXzx5Phd3LskasaEpxMnBhAyRsmQdQmcERVIzQUoxfstb8PDdPP+dV8V03mYLYwKlSWaf9mSDD5rV4gEIngehgLOwjblvhr5UacH2CYp3MveHaOFapAteaPGj6LRrG6dVTlzk886+TY5fLhfB6DQWfqO9jugaNY9vTW+ud09uU7ZXjfehQEYL6cm9QpXThgLK4DDv01J8/77a5Bt6f7R0SWTW/iMayIyYKq9EF5WGlgAKvRZKQGTXzKje/fLtJTR/rlF6ffzP35rBrF+RMBIfgS3vP5qg==; 5:/isIwvhwe8a31uGYi73PWQVhjDRdaKXTkfy/Nk4289AOdiVKOKUq+geJ6tmZ29IykomDESdTdTG/KrilkSAxGHlVL0A1JhTIRwmOzI6iXVn56vzVSr3Bbwm9O5DZMg00pHlZP6WzLzPO5E+cbcUg6UsgmNNrIHXjs/hMn5KVNKY=; 7:kIuOM3dr5N7t0Gfqb2bVXIM4Dq3xE9BIoL8Mu/P9GRROwg85bj0pD3zkMQz/uzIprJZbGlILpzNlXFDxYDj1MjrCU1GpDqZavXCo+uTIGcmioV/ej4bO938dsgUy5driBMfenpin5eGyBCiCydXbmm5XZpAb9dgqvAIzZSuUjyKs4aoBt3CCy3E2PuWusJ800zJN402HsCoJqkibyMwdBNUqPbsfA824ziKY8BdSreWjKGK4V1nqJP6xAd4sKqe7
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: f55676d6-433c-4067-9674-08d62aab70a9
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:HE1PR0701MB2922; 
x-ms-traffictypediagnostic: HE1PR0701MB2922:
x-microsoft-antispam-prvs: <HE1PR0701MB2922E8136D08B120370A46F2E2EB0@HE1PR0701MB2922.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(18271650672692)(161740460382875)(100405760836317)(85827821059158); 
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(3231355)(944501410)(52105095)(10201501046)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123564045)(20161123558120)(20161123560045)(201708071742011)(7699051); SRVR:HE1PR0701MB2922; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0701MB2922; 
x-forefront-prvs: 0816F1D86E
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(346002)(376002)(396003)(366004)(136003)(13464003)(189003)(199004)(2501003)(102836004)(8936002)(81156014)(55016002)(81166006)(53936002)(478600001)(114624004)(256004)(5660300001)(345774005)(66066001)(106356001)(5024004)(105586002)(14454004)(5250100002)(229853002)(14444005)(9686003)(6436002)(68736007)(8676002)(186003)(25786009)(316002)(11346002)(7736002)(74316002)(86362001)(99286004)(39060400002)(53546011)(486006)(446003)(2201001)(2900100001)(54906003)(476003)(2906002)(4326008)(76176011)(305945005)(7696005)(3846002)(97736004)(71200400001)(93886005)(26005)(110136005)(551934003)(71190400001)(6116002)(561944003)(44832011)(33656002)(6506007)(6246003)(473944003)(414714003); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0701MB2922; H:HE1PR0701MB2393.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: KdkJRjxlh0QEpB03/uc9mpokRhYH4wMZcO8Zs7e+rdUhXZWpcxtfqIiZSZ0rKNA9BNinpGujmYmV+n+zOyIb+BHosbDucU+VOUlyuMXxesGzkNwPbeI2J4hdmg8rUTKKioiFdymD9C0d7BRXT+H1edQ3FBlRZvpRALB1RC3w9nf/yLOj4Afkkgoxje9ISZ0UvcSUirYgzM7yBkiidv75COlTNLCD2rLjI0cLHdI1LfbrOqewCm2T0nxISj1/9n3T7HJakKcLtT60z+dnMka4nw3zdcjlRZzX9KzikvoKAI2NORszDz9DDN/52EdmWeLeseMN4REG6I8CErzjfu2S01GTtUgfOv0iqKBit4frRoE=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: f55676d6-433c-4067-9674-08d62aab70a9
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Oct 2018 10:15:13.5618 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2922
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Sa0hTYRjHeXfO2c6mo9ep+WBINiRIvFMyy0r7oEOJktJCM116vOCctjPN CYGKGs0Co2lOP3jNQGPmpbygqMOwiSGEoih2oakUFkqYt7I8OwZ9+z3P//8+l5eHJmTPKHc6 U6NjtBqVWi6UkKbrvXrf7pDehICZmRBF69ZRxePiOpGis/S7UPFt/R6l2FkxiBQPGhzChMqp 8ReUsr92UaScr5kglS0t2wJl6bJVqLQNm8jLwnhJaCqjzsxntP7nkiUZ7WsVRO6v2ILJ4SGq CH28YkA0DfgkGEdiDUhMy/BrBP09LjxvIDCVFBqQhOfduT3EB80CKCt7QnIBiSsJ2OpcEPFK tQBmR14K+WAJwfybAZIrJsR+MLlYYRdccDOCP60GghMIrAfzVK+QY2fsA+sdXBPxvskXitva BTxHQNNYNeKGJbEX2JoOcyjFyWAznOd7NYqh/mG7/akYJ4LRumRnhD3gw+Z7km/lBvO2entJ wBhaBqcInl3hy+c9iquJ8A3YWcjl055wf2T1wO4B7+or7OsDHhHB+uBXxAu+sFZVRfD/eBFG bZG8x4pgqX/jwOMDz/sHKJ5z4OnGKsX71fCz9U4lCqr9b7rafYXAJ6BjwJ9PHwNjxScRx1Ls BFaTjWxAZBtyZRmWzU4PCvJjtJkpLJuj8dMwui60fz6jPbun+9DoSrgFYRrJHaWB+6cko1T5 rD7bgoAm5C7Sa7pXCTJpqkpfyGhzkrR5aoa1oCM0KXeTXkhTxMtwukrHZDFMLqP9pwposXsR kng3hjiEju8ZQ50eUVHoeJw+OHJvc+JuUpTzzWmUd3vyUlPB2alTK3o6I2gw2jxLdlSm3IrR bGfNdXqnjx2yxMx7LoTL62Z3f6jczerEjohac/JwrtdA19Xu8oQhTVe5T1peyZnt1rDYnmlH x76E4JqA6JpK82+TcdkY1+70Vk6yGapAb0LLqv4Co0D3hjoDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/6VbkdFVxltPISW7Ku0xbntej9pM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Oct 2018 10:15:22 -0000

SGksDQpJIGxpa2UgdGhpcyBhcHByb2FjaCBzaW5jZSBpdCBhbGxvd3MgdXMgdG8gZGlzcmVnYXJk
IG5vbi1zcGlubmluZyBmbG93cyBieSBzaW1wbHkgb2JzZXJ2aW5nIHRoZSBpbml0aWFsIGhhbmRz
aGFrZS4gVGhpcyBzYXZlcyB1cyBxdWl0ZSBzb21lIHdvcmsuIA0KT24gdGhlIGhldXJpc3RpY3Mg
cGFydCwgd2UgY2Fubm90IGdldCBhd2F5IGZyb20gaXQsIGV2ZW4gaWYgd2Ugc2VlIHRoZSBzcGlu
IHZlcnNpb24gaW4gdGhlIGluaXRpYWwgaGFuZHNoYWtlIGFzIHRoZXJlwrRzIG5vIGd1YXJhbnRl
ZSB0aGF0IGFuIGVuZHBvaW50IHdpbGwgc2V0IHRoZSBiaXQgcHJvcGVybHkgYW55d2F5Lg0KSG93
ZXZlciwgZm9yIHRoZSB2ZXJzaW9uIHdoZXJlIHRoZSBpbnRlbnQgdG8gdXNlIHNwaW5iaXQgaXMg
ZXhwbGljaXQgaXQgYWN0dWFsbHkgbWFrZXMgc2Vuc2UgZm9yIGFuIGVuZHBvaW50IHRvIHRyZWF0
IG5vbi1wYXJ0aWNpcGF0aW5nIGJlaGF2aW9yIGFzIGEgcHJvdG9jb2wgZXJyb3IuDQoNCk1hcmN1
cw0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogUVVJQyA8cXVpYy1ib3VuY2Vz
QGlldGYub3JnPiBPbiBCZWhhbGYgT2YgTWlrZSBCaXNob3ANClNlbnQ6IGRlbiA1IG9rdG9iZXIg
MjAxOCAwMDo0MA0KVG86IGFsZXhhbmRyZS5mZXJyaWV1eEBvcmFuZ2UuY29tOyBLYXp1aG8gT2t1
IDxrYXp1aG9va3VAZ21haWwuY29tPg0KQ2M6IEJyaWFuIFRyYW1tZWxsIDxpZXRmQHRyYW1tZWxs
LmNoPjsgSUVURiBRVUlDIFdHIDxxdWljQGlldGYub3JnPjsgQ2hyaXN0aWFuIEh1aXRlbWEgPGh1
aXRlbWFAaHVpdGVtYS5uZXQ+DQpTdWJqZWN0OiBSRTogU3BpbiBiaXQgYXMgYSBuZWdvdGlhdGVk
IG9wdGlvbg0KDQpTbyBsb25nIGFzIHRoaXMgaXMgdGhlIG9ubHkgdGhpbmcgYmVpbmcgbmVnb3Rp
YXRlZCwgaXQncyBub3QgdG9vIGJhZC4gIElmIHdlIHdhbnQgdG8gbmVnb3RpYXRlIG90aGVyIHRo
aW5ncywgaXQgcXVpY2tseSBnZXRzIG91dCBvZiBoYW5kLiAgT25lIGNvdWxkIHBsYXVzaWJseSBh
cmd1ZSB0aGF0IHRoZSBzcGluIGJpdCBpcyBzcGVjaWFsIGluIHRoYXQgd2UgYWN0dWFsbHkgd2Fu
dCBwYXJ0aWVzIG9ic2VydmluZyB0aGUgdHJhbnNhY3Rpb24gdG8gdW5kZXJzdGFuZCB3aGljaCBv
cHRpb24gaGFzIGJlZW4gc2VsZWN0ZWQuDQoNCkl0J3MgaW1wb3J0YW50IHRvIHJlbWVtYmVyLCB0
aG91Z2gsIHRoYXQgdGhpcyBpcyBpbmZvcm1hdGlvbiB5b3UgZ2V0IG9ubHkgYXQgdGhlIGJlZ2lu
bmluZyBvZiBhIG5ldyBjb25uZWN0aW9uLiAgSWYgdGhlcmUncyBtaWdyYXRpb24gb3IgTkFUIHJl
YmluZGluZywgaXQncyBub3QgZ3VhcmFudGVlZCAoYW5kIGluIGZhY3QsIG5vdCBpbnRlbmRlZCkg
dGhhbiB5b3UgY2FuIGNvcnJlbGF0ZSBpdCBiYWNrIHRvIGEgcGFydGljdWxhciBwcmV2aW91cyBo
YW5kc2hha2UuICBZb3UnbGwgc3RpbGwgZWl0aGVyIG5lZWQgaGV1cmlzdGljcyB0byBpZGVudGlm
eSB3aGV0aGVyIHRoZSBzcGluIGJpdCBpcyBhY3R1YWxseSBpbiB1c2UsIG9yIHlvdSdsbCBuZWVk
IHRvIGlnbm9yZSBhbnkgdHJhZmZpYyBmb3Igd2hpY2ggeW91IGRpZG4ndCBzZWUgdGhlIGhhbmRz
aGFrZS4NCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFFVSUMgPHF1aWMtYm91
bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxmIE9mIGFsZXhhbmRyZS5mZXJyaWV1eEBvcmFuZ2UuY29t
DQpTZW50OiBUaHVyc2RheSwgT2N0b2JlciA0LCAyMDE4IDM6NDcgQU0NClRvOiBLYXp1aG8gT2t1
IDxrYXp1aG9va3VAZ21haWwuY29tPg0KQ2M6IEJyaWFuIFRyYW1tZWxsIDxpZXRmQHRyYW1tZWxs
LmNoPjsgSUVURiBRVUlDIFdHIDxxdWljQGlldGYub3JnPjsgQ2hyaXN0aWFuIEh1aXRlbWEgPGh1
aXRlbWFAaHVpdGVtYS5uZXQ+DQpTdWJqZWN0OiBSZTogU3BpbiBiaXQgYXMgYSBuZWdvdGlhdGVk
IG9wdGlvbg0KDQpUaGFua3MgS2F6dWhvLiBVc2luZyB2ZXJzaW9uIG51bWJlcnMgZGlyZWN0bHkg
d2FzIGFuIG9idmlvdXMgY2hvaWNlLCBidXQgc28gZmFyIEkgd2FzIGRpc2NvdXJhZ2VkIGJ5IHN0
cm9uZyBsYW5ndWFnZSBpbiB0aGUgc3BlYywgc2F5aW5nIDB4MDAwMDAwMDEgd2FzIHRoZSB1bmF2
b2lkYWJsZSBwb2ludCBvZiBjb252ZXJnZW5jZSBhZnRlciBhbGwgMHhGRjAwMDBYWCBleHBlcmlt
ZW50cy4gU28gaW4gZXNzZW5jZSB5b3UncmUgcHJvcG9zaW5nIHRvIHdlYWtlbiB0aGF0IGEgYml0
LCByaWdodCA/DQoNCklmIHNvLCBob3cgZG8geW91IGVudmlzaW9uIHNlZ21lbnRpbmcgdGhlIHZl
cnNpb24gbnVtYmVyIHNwYWNlID8NCg0KICAtIGRpcmVjdCBlbnVtZXJhdGlvbjoNCg0KCTB4MDAw
MDAwMDEgPSB2MWRyeQ0KCTB4MDAwMDAwMDIgPSB2MSArIHNwaW5iaXQNCgkweDAwMDAwMDAzID0g
djEgKyBzcGluYml0ICsgVkVDDQoJDQogIC0gbG93IG9yZGVyIGJpdHMgZm9yIG9wdGlvbnM6DQoN
CgkweDAwMDAwMVhYID0gdjEgKyBvcHRpb24gWFgNCgkweDAwMDAwMllZID0gdjIgKyBvcHRpb24g
WVkNCg0KQWxzbywgYXJlIHdlIHN1cmUgdGhhdCB0aGlzIGV4cGxvc2lvbiB3b24ndCB3ZWlnaCBv
biB0aGUgbmV3IFZOIHNjaGVtZSwgaW5kdWNpbmcgc2xvd2VyIGNvbnZlcmdlbmNlIGR1ZSB0byBs
b25nZXIgbGlzdHMgb24gZWl0aGVyIHNpZGUgPw0KDQpPbiAxMC8wNC8xOCAxMTo1MCwgS2F6dWhv
IE9rdSB3cm90ZToNCj4gSGksDQo+IA0KPiBUaGFuayB5b3UgZm9yIHN0YXJ0aW5nIHRoZSBkaXNj
dXNzaW9uIHNwZWNpZmljIHRvIGhvdyB3ZSBjb3VsZCANCj4gcG9zc2libHkgbmVnb3RpYXRlIHRo
ZSB1c2Ugb2Ygc3BpbiBiaXRzLg0KPiANCj4gUmVnYXJkaW5nIHRoZSB0b3BpYywgbXkgcHJlZmVy
ZW5jZSBnb2VzIHRvIHVzaW5nIHRoZSB2ZXJzaW9uIG51bWJlciANCj4gZmllbGQgb2YgdGhlIGxv
bmcgaGVhZGVyIGZvciBuZWdvdGlhdGluZyB0aGUgcHJlc2VuY2Ugb2Ygc3BpbiBiaXRzLCBvciAN
Cj4gYW55IGFkZGl0aW9uYWwgc2lnbmFsIGJlaW5nIGV4cG9zZWQgdG8gdGhlIG5ldHdvcmsuDQo+
IA0KPiBGb3IgZXhhbXBsZSwgUVVJQ3YxIHdpdGhvdXQgc3BpbiBiaXQgY291bGQgdXNlIHZlcnNp
b24gMHgxMDEsIGFuZCB2MSANCj4gd2l0aCBzcGluIGJpdCBjb3VsZCB1c2UgMHgxMDIuIEluIHRo
ZSBmdXR1cmUsIHdlIGNhbiBhc3NpZ24gYSANCj4gZGlmZmVyZW50IHZlcnNpb24gbnVtYmVyIGZv
ciBRVUlDdjEgd2l0aCBtdWx0aXBsZSBzcGluICsgVkVDIChvciANCj4gcGVvcGxlIGludGVyZXN0
ZWQgaW4gdGVzdGluZyB0aGUgZmVhdHVyZSBjYW4gZGVzaWduYXRlIGEgcHJpdmF0ZSANCj4gdmVy
c2lvbiBudW1iZXIgZXZlbiBiZWZvcmUgdGhhdCkuDQo+IA0KPiBJIHNlZSB0aGUgZm9sbG93aW5n
IGJlbmVmaXRzIHRvIHVzaW5nIHRoZSB2ZXJzaW9uIGZpZWxkIGFzIGEgbWV0aG9kIHRvIA0KPiBu
ZWdvdGlhdGUgdGhlIHVzZSBvZiBzcGluIGJpdHMuDQo+IA0KPiAxLiBPbmUgb2YgdGhlIGNvbmNl
cm4gcmVnYXJkaW5nIHNwaW4gYml0cyBoYXMgYmVlbiB0aGF0IHRoZXkgY291bGQgDQo+IGxlYWQg
dG8gb3NzaWZpY2F0aW9uLiBTcGluIGJpdHMgYXJlIG5vdCBwYXJ0IG9mIHRoZSBJbnZhcmlhbnRz
LCBidXQgaWYgDQo+IHRoZSBvYnNlcnZhdGlvbiB0b29scyBzdGFydCBsb29raW5nIGF0IHRob3Nl
IGJpdHMgd2l0aG91dCBjaGVja2luZyB0aGUgDQo+IHZlcnNpb24gbnVtYmVyIGZpZWxkLCB3ZSB3
aWxsIGhhdmUgdGhlIHByZXNzdXJlIHRvIG5vdCBjaGFuZ2UgaG93IHRoZSANCj4gYml0cyBhcmUg
dXNlZC4gVXNpbmcgdGhlIHZlcnNpb24gbnVtYmVyIHRvIGluZGljYXRlIHRoZSBwcmVzZW5jZSBv
ZiANCj4gc3BpbiBiaXRzIGlzIHRoZSBiZXN0IGFwcHJvYWNoIHRvIHJlc29sdmUgc3VjaCBjb25j
ZXJuLg0KPiANCj4gMi4gV2UgaGF2ZSBob3BlZCB0byByb2xsIG91dCBtdWx0aXBsZSB2ZXJzaW9u
cyBvZiBRVUlDIGluIGEgc21hbGwgDQo+IGludGVydmFsIHNvIHRoYXQgdGhlIHZlcnNpb24gbnVt
YmVyIGZpZWxkIGRvZXMgbm90IGdldCBvc3NpZmllZC4gVGhlIA0KPiBiZXN0IHNvbHV0aW9uIGlz
IG9idmlvdXNseSB0byByb2xsIG91dCB0d28gZmxhdm9ycyBvZiB0aGUgcHJvdG9jb2wgDQo+IHRo
YXQgdXNlcyBkaWZmZXJlbnQgdmVyc2lvbiBudW1iZXJzIGF0IHRoZSBzYW1lIHRpbWUuIFdlIHdp
bGwgaGF2ZSBhIA0KPiByZWFsLXdvcmxkIHVzZSBvZiB2ZXJzaW9uIG5lZ290aWF0aW9uIGZyb20g
ZGF5IG9uZSwgYmVjYXVzZSB3ZSBhcmUgaW4gDQo+IGEgY29uZGl0aW9uIHdoZXJlIGltcGxlbWVu
dG9ycyBoYXZlIGRpZmZlcmVudCBvcGluaW9ucyBvbiBpZiB0aGV5IA0KPiBzaG91bGQgc3VwcG9y
dCBzcGluIGJpdCA6LSkNCj4gDQo+IFRoZSBibG9ja2VyIHRvIHRoaXMgYXBwcm9hY2ggaGFzIGJl
ZW4gdmVyc2lvbiBuZWdvdGlhdGlvbiByZXF1aXJpbmcgYW4gDQo+IGFkZGl0aW9uYWwgcm91bmQt
dHJpcCwgYnV0IHRoYXQgaXMgZ29pbmcgdG8gYmUgcmVzb2x2ZWQgYnkgIzE3NTUuDQo+IA0KPiAy
MDE45bm0MTDmnIgz5pelKOawtCkgMTk6MDYgPGFsZXhhbmRyZS5mZXJyaWV1eEBvcmFuZ2UuY29t
PjoNCj4+DQo+PiBPbiAxMC8wMy8xOCAwOTo1OCwgQnJpYW4gVHJhbW1lbGwgKElFVEYpIHdyb3Rl
Og0KPj4gPiBCYWNraW5nIG9mZiB0aGUgTVVTVCBmb3Igbm93IGZvciBzdWNoIHNpdHVhdGlvbnMg
aXMgSU1PIGEgZ29vZCANCj4+ID4gdHJhZGVvZmYsIHRob3VnaCwgZXNwZWNpYWxseSBzaW5jZSB3
ZSBvbmx5IG5lZWQgZnJhY3Rpb25zIG9mIGEgDQo+PiA+IHBlcmNlbnQgb2YgZGVwbG95bWVudCB0
byBzdGFydCBzZWVpbmcgdXNlZnVsIHNpZ25hbCBmb3IgDQo+PiA+IGJhc2VsaW5lL2Fub21hbHkg
bWVhc3VyZW1lbnQgb2YgbGFyZ2UgYWdncmVnYXRlcy4NCj4+DQo+PiBJZiB0aGUgY29uc2Vuc3Vz
IGlzIHRoYXQgd2UgbXVzdCBhbGxvdyBmb3Igc3VjaCBzaXR1YXRpb25zLCB0aGVuIA0KPj4gdGhl
cmUgYXJlIHR3bw0KPj4gcG9zc2liaWxpdGllczoNCj4+DQo+PiAgIChhKSB3ZWFrIHNwZWMgbGFu
Z3VhZ2UgKE1BWSBXSVNIIFRPIG9yIHNpbWlsYXIpID0+IG1hbnkgDQo+PiBpbXBsZW1lbnRhdGlv
bnMgd2lsbCBzaW1wbHkgZHJvcCBpdA0KPj4NCj4+ICAgKGIpIG5lZ290aWF0ZWQgb3B0aW9uIHdo
ZXJlIHRoZSBuZWdvdGlhdGlvbiBtZWNoYW5pc20gaXMgbWFuZGF0b3J5DQo+Pg0KPj4gSW4gdGhl
IHZlaW4gb2YgKGIpLCBDaHJpc3RpYW4gc3VnZ2VzdGVkIG9mZmxpbmUgdG8gaW50cm9kdWNlIA0K
Pj4gbmVnb3RpYXRpb24gdG8gYWxsb3cgZm9yIGV4cGVyaW1lbnRhdGlvbiBvZiB0aGUgcmVtYWlu
aW5nIHR3byANCj4+IHJlc2VydmVkIGJpdHMuIFRoZW4gbWF5IGJlIHdlIGNhbiBzeW50aGVzaXpl
IGJvdGggaWRlYXMgYnkgdGhlIGZvbGxvd2luZyBwcm9wb3NhbDoNCj4+DQo+PiAgIC0gaW4gdGhl
IGZpcnN0IGZldyBleGNoYW5nZXMgb2YgdGhlIDUtdHVwbGUsIHVzZSB0aGUgdGhyZWUgYml0cyBm
b3IgDQo+PiBvcHRpb24gbmVnb3RpYXRpb24NCj4+DQo+PiAgIC0gdGhlbiB1c2UgdGhlbSBhcyBk
ZWZpbmVkIGJ5IHRoZSBzZWxlY3RlZCBvcHRpb24NCj4+DQo+PiBFeGFtcGxlIGVuY29kaW5nczoN
Cj4+DQo+PiAgIDAwMCA6IG5vdGhpbmcNCj4+ICAgMDAxIDogc3BpbiBiaXQgYWxvbmUgOiBTMDAN
Cj4+ICAgMDEwIDogc3BpbiBiaXQgKyBWRUMgOiBTVlYNCj4+ICAgLi4uIDogb3RoZXIgZXh0ZW5z
aW9ucw0KPj4NCj4+IFRoZSBuZWdvdGlhdGlvbiBtZWNoYW5pc20gYWxsb3dzIGJvdGggZW5kcG9p
bnRzIHRvIGZvcmNlIDAwMC4NCj4+IEFuZCBzaW5jZSBpdCBpcyBpbiB0aGUgY2xlYXIgZmlyc3Qg
Ynl0ZSwgaXQgYWxsb3dzIG9uLXBhdGggb2JzZXJ2ZXJzIA0KPj4gdG8gaWRlbnRpZnkgdGhlIG9w
dGlvbiB3aXRob3V0IHJlc29ydGluZyB0byBoZXVyaXN0aWNzOyB0aGlzIGhlbHBzIGluIA0KPj4g
dGhlIGNhc2Ugb2YgYSBzbWFsbCBzdXBwb3J0IHJhdGlvLg0KPj4NCj4+DQo+Pg0KPj4NCj4+IF9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KPj4NCj4+IENlIG1lc3NhZ2UgZXQgc2VzIHBpZWNlcyBqb2ludGVzIHBldXZl
bnQgY29udGVuaXIgZGVzIGluZm9ybWF0aW9ucyANCj4+IGNvbmZpZGVudGllbGxlcyBvdSBwcml2
aWxlZ2llZXMgZXQgbmUgZG9pdmVudCBkb25jIHBhcyBldHJlIGRpZmZ1c2VzLCANCj4+IGV4cGxv
aXRlcyBvdSBjb3BpZXMgc2FucyBhdXRvcmlzYXRpb24uIFNpIHZvdXMgYXZleiByZWN1IGNlIG1l
c3NhZ2UgDQo+PiBwYXIgZXJyZXVyLCB2ZXVpbGxleiBsZSBzaWduYWxlciBhIGwnZXhwZWRpdGV1
ciBldCBsZSBkZXRydWlyZSBhaW5zaSBxdWUgbGVzIHBpZWNlcyBqb2ludGVzLiBMZXMgbWVzc2Fn
ZXMgZWxlY3Ryb25pcXVlcyBldGFudCBzdXNjZXB0aWJsZXMgZCdhbHRlcmF0aW9uLCBPcmFuZ2Ug
ZGVjbGluZSB0b3V0ZSByZXNwb25zYWJpbGl0ZSBzaSBjZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwg
ZGVmb3JtZSBvdSBmYWxzaWZpZS4gTWVyY2kuDQo+Pg0KPj4gVGhpcyBtZXNzYWdlIGFuZCBpdHMg
YXR0YWNobWVudHMgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIG9yIA0KPj4gcHJpdmlsZWdlZCBp
bmZvcm1hdGlvbiB0aGF0IG1heSBiZSBwcm90ZWN0ZWQgYnkgbGF3OyB0aGV5IHNob3VsZCBub3Qg
YmUgZGlzdHJpYnV0ZWQsIHVzZWQgb3IgY29waWVkIHdpdGhvdXQgYXV0aG9yaXNhdGlvbi4NCj4+
IElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgZW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkg
dGhlIHNlbmRlciBhbmQgZGVsZXRlIHRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRzLg0K
Pj4gQXMgZW1haWxzIG1heSBiZSBhbHRlcmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBmb3IgbWVz
c2FnZXMgdGhhdCBoYXZlIGJlZW4gbW9kaWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVkLg0KPj4g
VGhhbmsgeW91Lg0KPj4NCj4gDQo+IA0KDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KDQpDZSBtZXNzYWdlIGV0IHNl
cyBwaWVjZXMgam9pbnRlcyBwZXV2ZW50IGNvbnRlbmlyIGRlcyBpbmZvcm1hdGlvbnMgY29uZmlk
ZW50aWVsbGVzIG91IHByaXZpbGVnaWVlcyBldCBuZSBkb2l2ZW50IGRvbmMgcGFzIGV0cmUgZGlm
ZnVzZXMsIGV4cGxvaXRlcyBvdSBjb3BpZXMgc2FucyBhdXRvcmlzYXRpb24uIFNpIHZvdXMgYXZl
eiByZWN1IGNlIG1lc3NhZ2UgcGFyIGVycmV1ciwgdmV1aWxsZXogbGUgc2lnbmFsZXIgYSBsJ2V4
cGVkaXRldXIgZXQgbGUgZGV0cnVpcmUgYWluc2kgcXVlIGxlcyBwaWVjZXMgam9pbnRlcy4gTGVz
IG1lc3NhZ2VzIGVsZWN0cm9uaXF1ZXMgZXRhbnQgc3VzY2VwdGlibGVzIGQnYWx0ZXJhdGlvbiwg
T3JhbmdlIGRlY2xpbmUgdG91dGUgcmVzcG9uc2FiaWxpdGUgc2kgY2UgbWVzc2FnZSBhIGV0ZSBh
bHRlcmUsIGRlZm9ybWUgb3UgZmFsc2lmaWUuIE1lcmNpLg0KDQpUaGlzIG1lc3NhZ2UgYW5kIGl0
cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBjb25maWRlbnRpYWwgb3IgcHJpdmlsZWdlZCBpbmZv
cm1hdGlvbiB0aGF0IG1heSBiZSBwcm90ZWN0ZWQgYnkgbGF3OyB0aGV5IHNob3VsZCBub3QgYmUg
ZGlzdHJpYnV0ZWQsIHVzZWQgb3IgY29waWVkIHdpdGhvdXQgYXV0aG9yaXNhdGlvbi4NCklmIHlv
dSBoYXZlIHJlY2VpdmVkIHRoaXMgZW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNl
bmRlciBhbmQgZGVsZXRlIHRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRzLg0KQXMgZW1h
aWxzIG1heSBiZSBhbHRlcmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhh
dCBoYXZlIGJlZW4gbW9kaWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVkLg0KVGhhbmsgeW91Lg0K
DQo=


From nobody Fri Oct  5 03:33:31 2018
Return-Path: <martenseemann@gmail.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 581EA130E69 for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 03:33:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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_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=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 BqBTr-0QP0zX for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 03:33:25 -0700 (PDT)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (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 27889130E51 for <quic@ietf.org>; Fri,  5 Oct 2018 03:33:25 -0700 (PDT)
Received: by mail-io1-xd31.google.com with SMTP id w11-v6so10287978iob.2 for <quic@ietf.org>; Fri, 05 Oct 2018 03:33:25 -0700 (PDT)
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=k8JUFU355rIsfUju/1vxXO5bsK0pdUbzDBZU0ZjLxNA=; b=WVm66i89O7mgeY0BjZ2FGVJ8C8b7/QEEpUJoD3DCoMRbfbBcyCeKi46mrKAgsYmQOB 6YzX0L9LSS19FPIVtuuEag8M76QWzrP/9QXsxkHrow3qBcXaWvh7zYgzJI7CD6qS+ElI s/sCmyClWXamjBdcPLumqfM2xWMXdJOtML8CRztfUlU3Zd5nReY0rlKrNXdzo7Z1Z+oM masGOd+YqsgPZEtu2E9woPqw6PwQDv6tM4Be62rWmxzt+e+Cz2Pf0XYlDwKGyvUOg5Ap A+AIpulH44tsRtCQ60EM20zZQpVMDP657iJJsBuqEdgbPwP0sjihhiPdAIyaYbB5Zh7Q j1iw==
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=k8JUFU355rIsfUju/1vxXO5bsK0pdUbzDBZU0ZjLxNA=; b=JikoYG/fVA5u5O/QvvDJE5tlMZNtqsxqwNnmFh43y1xddhJgHdPyr9dKyk8muQP3gT flPI2a0tqzt81jLtROyqJpej/f1RJvmTXJPLrgwQYW7rafHsdjIFpfY1LTy0+B2hMJOL jIyASGC81irp7rvTdJD/2c+6WEWQeTJD+kkznhyL4Kbh/7naPPe5JlvuaewzaC01rEPQ WPrPcFAB2OqenKHXqfdQuQG0DUCYUYedtk2unOxJsuHL4yoHTbdxsJz5kiI9ULkEW6fG fXP9ONFDxvcgkd4Eg78xQqBVmf+Czyh+9jFe/siECAf1jW3kD8PzGTsh/TX/5GY4oQYj S6hw==
X-Gm-Message-State: ABuFfohyCfJuKCy+gc49cccppPd5vD9UYeDVdCpX3NjWaT1Ha+F3Rog4 uCk7V09vIwDFDlY5upw68C3lLqbC76SfdS1pFCw=
X-Google-Smtp-Source: ACcGV621RDqdOcaLqBUDgWVfuJfVk1wO0TtozsY7bra1tLOrTdG5g5S7stfAAEuMSa8zojDm4Kk8SsXAQCtMvAU8i3o=
X-Received: by 2002:a6b:8c48:: with SMTP id o69-v6mr7632737iod.195.1538735604161;  Fri, 05 Oct 2018 03:33:24 -0700 (PDT)
MIME-Version: 1.0
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com> <CY4PR22MB0983849F01312CBE18A4F69CDAEA0@CY4PR22MB0983.namprd22.prod.outlook.com> <HE1PR0701MB2393C0B9756449E5CC060723E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR0701MB2393C0B9756449E5CC060723E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
From: Marten Seemann <martenseemann@gmail.com>
Date: Fri, 5 Oct 2018 12:33:11 +0200
Message-ID: <CAOYVs2oyQO6kC3tMA3Cw7zzzDjiJca4yWRXqaK1ZH3_sbxWWtQ@mail.gmail.com>
Subject: Re: Spin bit as a negotiated option
To: Marcus Ihlar <marcus.ihlar@ericsson.com>
Cc: "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>,  "huitema@huitema.net" <huitema@huitema.net>, "ietf@trammell.ch" <ietf@trammell.ch>,  "kazuhooku@gmail.com" <kazuhooku@gmail.com>, "mbishop@evequefou.be" <mbishop@evequefou.be>,  "quic@ietf.org" <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000016e223057778cd16"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/XtroO3lEDjb28wQjoShb0qXc4V8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Oct 2018 10:33:29 -0000

--00000000000016e223057778cd16
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

The problem with using a specific version for implementations that use and
don=E2=80=99t use the spin bit is that middleboxes can effectively enforce =
usage of
the spin bit version by blackholing every packet advertising a version that
doesn=E2=80=99t use the spin bit. If only a few middleboxes do that, this w=
ould
force *all* implementations to avoid these versions.
Implementations that don=E2=80=99t want to expose their RTT would then have=
 to
negotiate a version that is supposed to use the spin bit, but then grease
the corresponding bits in order to preserve their privacy. Of course, this
would only work if the peer doesn=E2=80=99t enforce compliance. Otherwise, =
we=E2=80=99ll
end up in a world where it=E2=80=99s basically impossible to opt-out of the
spin-bit.

On Fri, Oct 5, 2018 at 12:15 Marcus Ihlar <marcus.ihlar@ericsson.com> wrote=
:

> Hi,
> I like this approach since it allows us to disregard non-spinning flows b=
y
> simply observing the initial handshake. This saves us quite some work.
> On the heuristics part, we cannot get away from it, even if we see the
> spin version in the initial handshake as there=C2=B4s no guarantee that a=
n
> endpoint will set the bit properly anyway.
> However, for the version where the intent to use spinbit is explicit it
> actually makes sense for an endpoint to treat non-participating behavior =
as
> a protocol error.
>
> Marcus
>
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of Mike Bishop
> Sent: den 5 oktober 2018 00:40
> To: alexandre.ferrieux@orange.com; Kazuho Oku <kazuhooku@gmail.com>
> Cc: Brian Trammell <ietf@trammell.ch>; IETF QUIC WG <quic@ietf.org>;
> Christian Huitema <huitema@huitema.net>
> Subject: RE: Spin bit as a negotiated option
>
> So long as this is the only thing being negotiated, it's not too bad.  If
> we want to negotiate other things, it quickly gets out of hand.  One coul=
d
> plausibly argue that the spin bit is special in that we actually want
> parties observing the transaction to understand which option has been
> selected.
>
> It's important to remember, though, that this is information you get only
> at the beginning of a new connection.  If there's migration or NAT
> rebinding, it's not guaranteed (and in fact, not intended) than you can
> correlate it back to a particular previous handshake.  You'll still eithe=
r
> need heuristics to identify whether the spin bit is actually in use, or
> you'll need to ignore any traffic for which you didn't see the handshake.
>
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of
> alexandre.ferrieux@orange.com
> Sent: Thursday, October 4, 2018 3:47 AM
> To: Kazuho Oku <kazuhooku@gmail.com>
> Cc: Brian Trammell <ietf@trammell.ch>; IETF QUIC WG <quic@ietf.org>;
> Christian Huitema <huitema@huitema.net>
> Subject: Re: Spin bit as a negotiated option
>
> Thanks Kazuho. Using version numbers directly was an obvious choice, but
> so far I was discouraged by strong language in the spec, saying 0x0000000=
1
> was the unavoidable point of convergence after all 0xFF0000XX experiments=
.
> So in essence you're proposing to weaken that a bit, right ?
>
> If so, how do you envision segmenting the version number space ?
>
>   - direct enumeration:
>
>         0x00000001 =3D v1dry
>         0x00000002 =3D v1 + spinbit
>         0x00000003 =3D v1 + spinbit + VEC
>
>   - low order bits for options:
>
>         0x000001XX =3D v1 + option XX
>         0x000002YY =3D v2 + option YY
>
> Also, are we sure that this explosion won't weigh on the new VN scheme,
> inducing slower convergence due to longer lists on either side ?
>
> On 10/04/18 11:50, Kazuho Oku wrote:
> > Hi,
> >
> > Thank you for starting the discussion specific to how we could
> > possibly negotiate the use of spin bits.
> >
> > Regarding the topic, my preference goes to using the version number
> > field of the long header for negotiating the presence of spin bits, or
> > any additional signal being exposed to the network.
> >
> > For example, QUICv1 without spin bit could use version 0x101, and v1
> > with spin bit could use 0x102. In the future, we can assign a
> > different version number for QUICv1 with multiple spin + VEC (or
> > people interested in testing the feature can designate a private
> > version number even before that).
> >
> > I see the following benefits to using the version field as a method to
> > negotiate the use of spin bits.
> >
> > 1. One of the concern regarding spin bits has been that they could
> > lead to ossification. Spin bits are not part of the Invariants, but if
> > the observation tools start looking at those bits without checking the
> > version number field, we will have the pressure to not change how the
> > bits are used. Using the version number to indicate the presence of
> > spin bits is the best approach to resolve such concern.
> >
> > 2. We have hoped to roll out multiple versions of QUIC in a small
> > interval so that the version number field does not get ossified. The
> > best solution is obviously to roll out two flavors of the protocol
> > that uses different version numbers at the same time. We will have a
> > real-world use of version negotiation from day one, because we are in
> > a condition where implementors have different opinions on if they
> > should support spin bit :-)
> >
> > The blocker to this approach has been version negotiation requiring an
> > additional round-trip, but that is going to be resolved by #1755.
> >
> > 2018=E5=B9=B410=E6=9C=883=E6=97=A5(=E6=B0=B4) 19:06 <alexandre.ferrieux=
@orange.com>:
> >>
> >> On 10/03/18 09:58, Brian Trammell (IETF) wrote:
> >> > Backing off the MUST for now for such situations is IMO a good
> >> > tradeoff, though, especially since we only need fractions of a
> >> > percent of deployment to start seeing useful signal for
> >> > baseline/anomaly measurement of large aggregates.
> >>
> >> If the consensus is that we must allow for such situations, then
> >> there are two
> >> possibilities:
> >>
> >>   (a) weak spec language (MAY WISH TO or similar) =3D> many
> >> implementations will simply drop it
> >>
> >>   (b) negotiated option where the negotiation mechanism is mandatory
> >>
> >> In the vein of (b), Christian suggested offline to introduce
> >> negotiation to allow for experimentation of the remaining two
> >> reserved bits. Then may be we can synthesize both ideas by the
> following proposal:
> >>
> >>   - in the first few exchanges of the 5-tuple, use the three bits for
> >> option negotiation
> >>
> >>   - then use them as defined by the selected option
> >>
> >> Example encodings:
> >>
> >>   000 : nothing
> >>   001 : spin bit alone : S00
> >>   010 : spin bit + VEC : SVV
> >>   ... : other extensions
> >>
> >> The negotiation mechanism allows both endpoints to force 000.
> >> And since it is in the clear first byte, it allows on-path observers
> >> to identify the option without resorting to heuristics; this helps in
> >> the case of a small support ratio.
> >>
> >>
> >>
> >>
> >> _____________________________________________________________________
> >> ____________________________________________________
> >>
> >> 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 b=
e
> 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'alteratio=
n,
> Orange decline toute responsabilite si ce message a ete altere, deforme o=
u
> 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 bee=
n
> modified, changed or falsified.
> Thank you.
>
>

--00000000000016e223057778cd16
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><div dir=3D"auto">The problem with using a specific version for implem=
entations that use and don=E2=80=99t use the spin bit is that middleboxes c=
an effectively enforce usage of the spin bit version by blackholing every p=
acket advertising a version that doesn=E2=80=99t use the spin bit. If only =
a few middleboxes do that, this would force *all* implementations to avoid =
these versions.</div></div><div dir=3D"auto">Implementations that don=E2=80=
=99t want to expose their RTT would then have to negotiate a version that i=
s supposed to use the spin bit, but then grease the corresponding bits in o=
rder to preserve their privacy. Of course, this would only work if the peer=
 doesn=E2=80=99t enforce compliance. Otherwise, we=E2=80=99ll end up in a w=
orld where it=E2=80=99s basically impossible to opt-out of the spin-bit.</d=
iv><div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Fri, Oct 5, 2018=
 at 12:15 Marcus Ihlar &lt;<a href=3D"mailto:marcus.ihlar@ericsson.com">mar=
cus.ihlar@ericsson.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">Hi,<br>
I like this approach since it allows us to disregard non-spinning flows by =
simply observing the initial handshake. This saves us quite some work. <br>
On the heuristics part, we cannot get away from it, even if we see the spin=
 version in the initial handshake as there=C2=B4s no guarantee that an endp=
oint will set the bit properly anyway.<br>
However, for the version where the intent to use spinbit is explicit it act=
ually makes sense for an endpoint to treat non-participating behavior as a =
protocol error.<br>
<br>
Marcus<br>
<br>
-----Original Message-----<br>
From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_blank">q=
uic-bounces@ietf.org</a>&gt; On Behalf Of Mike Bishop<br>
Sent: den 5 oktober 2018 00:40<br>
To: <a href=3D"mailto:alexandre.ferrieux@orange.com" target=3D"_blank">alex=
andre.ferrieux@orange.com</a>; Kazuho Oku &lt;<a href=3D"mailto:kazuhooku@g=
mail.com" target=3D"_blank">kazuhooku@gmail.com</a>&gt;<br>
Cc: Brian Trammell &lt;<a href=3D"mailto:ietf@trammell.ch" target=3D"_blank=
">ietf@trammell.ch</a>&gt;; IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.or=
g" target=3D"_blank">quic@ietf.org</a>&gt;; Christian Huitema &lt;<a href=
=3D"mailto:huitema@huitema.net" target=3D"_blank">huitema@huitema.net</a>&g=
t;<br>
Subject: RE: Spin bit as a negotiated option<br>
<br>
So long as this is the only thing being negotiated, it&#39;s not too bad.=
=C2=A0 If we want to negotiate other things, it quickly gets out of hand.=
=C2=A0 One could plausibly argue that the spin bit is special in that we ac=
tually want parties observing the transaction to understand which option ha=
s been selected.<br>
<br>
It&#39;s important to remember, though, that this is information you get on=
ly at the beginning of a new connection.=C2=A0 If there&#39;s migration or =
NAT rebinding, it&#39;s not guaranteed (and in fact, not intended) than you=
 can correlate it back to a particular previous handshake.=C2=A0 You&#39;ll=
 still either need heuristics to identify whether the spin bit is actually =
in use, or you&#39;ll need to ignore any traffic for which you didn&#39;t s=
ee the handshake.<br>
<br>
-----Original Message-----<br>
From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_blank">q=
uic-bounces@ietf.org</a>&gt; On Behalf Of <a href=3D"mailto:alexandre.ferri=
eux@orange.com" target=3D"_blank">alexandre.ferrieux@orange.com</a><br>
Sent: Thursday, October 4, 2018 3:47 AM<br>
To: Kazuho Oku &lt;<a href=3D"mailto:kazuhooku@gmail.com" target=3D"_blank"=
>kazuhooku@gmail.com</a>&gt;<br>
Cc: Brian Trammell &lt;<a href=3D"mailto:ietf@trammell.ch" target=3D"_blank=
">ietf@trammell.ch</a>&gt;; IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.or=
g" target=3D"_blank">quic@ietf.org</a>&gt;; Christian Huitema &lt;<a href=
=3D"mailto:huitema@huitema.net" target=3D"_blank">huitema@huitema.net</a>&g=
t;<br>
Subject: Re: Spin bit as a negotiated option<br>
<br>
Thanks Kazuho. Using version numbers directly was an obvious choice, but so=
 far I was discouraged by strong language in the spec, saying 0x00000001 wa=
s the unavoidable point of convergence after all 0xFF0000XX experiments. So=
 in essence you&#39;re proposing to weaken that a bit, right ?<br>
<br>
If so, how do you envision segmenting the version number space ?<br>
<br>
=C2=A0 - direct enumeration:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 0x00000001 =3D v1dry<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 0x00000002 =3D v1 + spinbit<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 0x00000003 =3D v1 + spinbit + VEC<br>
<br>
=C2=A0 - low order bits for options:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 0x000001XX =3D v1 + option XX<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 0x000002YY =3D v2 + option YY<br>
<br>
Also, are we sure that this explosion won&#39;t weigh on the new VN scheme,=
 inducing slower convergence due to longer lists on either side ?<br>
<br>
On 10/04/18 11:50, Kazuho Oku wrote:<br>
&gt; Hi,<br>
&gt; <br>
&gt; Thank you for starting the discussion specific to how we could <br>
&gt; possibly negotiate the use of spin bits.<br>
&gt; <br>
&gt; Regarding the topic, my preference goes to using the version number <b=
r>
&gt; field of the long header for negotiating the presence of spin bits, or=
 <br>
&gt; any additional signal being exposed to the network.<br>
&gt; <br>
&gt; For example, QUICv1 without spin bit could use version 0x101, and v1 <=
br>
&gt; with spin bit could use 0x102. In the future, we can assign a <br>
&gt; different version number for QUICv1 with multiple spin + VEC (or <br>
&gt; people interested in testing the feature can designate a private <br>
&gt; version number even before that).<br>
&gt; <br>
&gt; I see the following benefits to using the version field as a method to=
 <br>
&gt; negotiate the use of spin bits.<br>
&gt; <br>
&gt; 1. One of the concern regarding spin bits has been that they could <br=
>
&gt; lead to ossification. Spin bits are not part of the Invariants, but if=
 <br>
&gt; the observation tools start looking at those bits without checking the=
 <br>
&gt; version number field, we will have the pressure to not change how the =
<br>
&gt; bits are used. Using the version number to indicate the presence of <b=
r>
&gt; spin bits is the best approach to resolve such concern.<br>
&gt; <br>
&gt; 2. We have hoped to roll out multiple versions of QUIC in a small <br>
&gt; interval so that the version number field does not get ossified. The <=
br>
&gt; best solution is obviously to roll out two flavors of the protocol <br=
>
&gt; that uses different version numbers at the same time. We will have a <=
br>
&gt; real-world use of version negotiation from day one, because we are in =
<br>
&gt; a condition where implementors have different opinions on if they <br>
&gt; should support spin bit :-)<br>
&gt; <br>
&gt; The blocker to this approach has been version negotiation requiring an=
 <br>
&gt; additional round-trip, but that is going to be resolved by #1755.<br>
&gt; <br>
&gt; 2018=E5=B9=B410=E6=9C=883=E6=97=A5(=E6=B0=B4) 19:06 &lt;<a href=3D"mai=
lto:alexandre.ferrieux@orange.com" target=3D"_blank">alexandre.ferrieux@ora=
nge.com</a>&gt;:<br>
&gt;&gt;<br>
&gt;&gt; On 10/03/18 09:58, Brian Trammell (IETF) wrote:<br>
&gt;&gt; &gt; Backing off the MUST for now for such situations is IMO a goo=
d <br>
&gt;&gt; &gt; tradeoff, though, especially since we only need fractions of =
a <br>
&gt;&gt; &gt; percent of deployment to start seeing useful signal for <br>
&gt;&gt; &gt; baseline/anomaly measurement of large aggregates.<br>
&gt;&gt;<br>
&gt;&gt; If the consensus is that we must allow for such situations, then <=
br>
&gt;&gt; there are two<br>
&gt;&gt; possibilities:<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0(a) weak spec language (MAY WISH TO or similar) =3D&gt=
; many <br>
&gt;&gt; implementations will simply drop it<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0(b) negotiated option where the negotiation mechanism =
is mandatory<br>
&gt;&gt;<br>
&gt;&gt; In the vein of (b), Christian suggested offline to introduce <br>
&gt;&gt; negotiation to allow for experimentation of the remaining two <br>
&gt;&gt; reserved bits. Then may be we can synthesize both ideas by the fol=
lowing proposal:<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0- in the first few exchanges of the 5-tuple, use the t=
hree bits for <br>
&gt;&gt; option negotiation<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0- then use them as defined by the selected option<br>
&gt;&gt;<br>
&gt;&gt; Example encodings:<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0000 : nothing<br>
&gt;&gt;=C2=A0 =C2=A0001 : spin bit alone : S00<br>
&gt;&gt;=C2=A0 =C2=A0010 : spin bit + VEC : SVV<br>
&gt;&gt;=C2=A0 =C2=A0... : other extensions<br>
&gt;&gt;<br>
&gt;&gt; The negotiation mechanism allows both endpoints to force 000.<br>
&gt;&gt; And since it is in the clear first byte, it allows on-path observe=
rs <br>
&gt;&gt; to identify the option without resorting to heuristics; this helps=
 in <br>
&gt;&gt; the case of a small support ratio.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; __________________________________________________________________=
___<br>
&gt;&gt; ____________________________________________________<br>
&gt;&gt;<br>
&gt;&gt; Ce message et ses pieces jointes peuvent contenir des informations=
 <br>
&gt;&gt; confidentielles ou privilegiees et ne doivent donc pas etre diffus=
es, <br>
&gt;&gt; exploites ou copies sans autorisation. Si vous avez recu ce messag=
e <br>
&gt;&gt; par erreur, veuillez le signaler a l&#39;expediteur et le detruire=
 ainsi que les pieces jointes. Les messages electroniques etant susceptible=
s d&#39;alteration, Orange decline toute responsabilite si ce message a ete=
 altere, deforme ou falsifie. Merci.<br>
&gt;&gt;<br>
&gt;&gt; This message and its attachments may contain confidential or <br>
&gt;&gt; privileged information that may be protected by law; they should n=
ot be distributed, used or copied without authorisation.<br>
&gt;&gt; If you have received this email in error, please notify the sender=
 and delete this message and its attachments.<br>
&gt;&gt; As emails may be altered, Orange is not liable for messages that h=
ave been modified, changed or falsified.<br>
&gt;&gt; Thank you.<br>
&gt;&gt;<br>
&gt; <br>
&gt; <br>
<br>
<br>
<br>
___________________________________________________________________________=
______________________________________________<br>
<br>
Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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&#39;expediteur et le detruire ainsi que les pieces jointes=
. Les messages electroniques etant susceptibles d&#39;alteration, Orange de=
cline toute responsabilite si ce message a ete altere, deforme ou falsifie.=
 Merci.<br>
<br>
This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law; they should not be distributed, used=
 or copied without authorisation.<br>
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.<br>
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.<br>
Thank you.<br>
<br>
</blockquote></div></div>

--00000000000016e223057778cd16--


From nobody Fri Oct  5 03:52:38 2018
Return-Path: <alexandre.ferrieux@orange.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 C7002130ECA for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 03:52:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.289
X-Spam-Level: 
X-Spam-Status: No, score=-0.289 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 twIb6Bl_H1uQ for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 03:52:34 -0700 (PDT)
Received: from orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94FA7130E9E for <quic@ietf.org>; Fri,  5 Oct 2018 03:52:33 -0700 (PDT)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) by opfedar22.francetelecom.fr (ESMTP service) with ESMTP id 42RRRN00gbz2xdx; Fri,  5 Oct 2018 12:52:32 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfedar06.francetelecom.fr (ESMTP service) with ESMTP id 42RRRM66fMz3wbX; Fri,  5 Oct 2018 12:52:31 +0200 (CEST)
Received: from [10.193.4.89] (10.168.234.2) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 5 Oct 2018 12:52:31 +0200
Subject: Re: Spin bit as a negotiated option
To: Marten Seemann <martenseemann@gmail.com>, Marcus Ihlar <marcus.ihlar@ericsson.com>
CC: "huitema@huitema.net" <huitema@huitema.net>, "ietf@trammell.ch" <ietf@trammell.ch>, "kazuhooku@gmail.com" <kazuhooku@gmail.com>, "mbishop@evequefou.be" <mbishop@evequefou.be>, "quic@ietf.org" <quic@ietf.org>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com> <CY4PR22MB0983849F01312CBE18A4F69CDAEA0@CY4PR22MB0983.namprd22.prod.outlook.com> <HE1PR0701MB2393C0B9756449E5CC060723E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <CAOYVs2oyQO6kC3tMA3Cw7zzzDjiJca4yWRXqaK1ZH3_sbxWWtQ@mail.gmail.com>
From: <alexandre.ferrieux@orange.com>
Message-ID: <23413_1538736751_5BB7426F_23413_53_1_0e2abf8d-e652-271e-099c-a32812b2ce46@orange.com>
Date: Fri, 5 Oct 2018 12:52:30 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CAOYVs2oyQO6kC3tMA3Cw7zzzDjiJca4yWRXqaK1ZH3_sbxWWtQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------8A11536F30A95651FDECD257"
Content-Language: en-US
X-Originating-IP: [10.168.234.2]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YIPkwXkx0u-OLBoK2JH6ZA1VQR8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Oct 2018 10:52:37 -0000

--------------8A11536F30A95651FDECD257
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: quoted-printable

As Kazuho reminded, the aim is to fight ossification by having a wealth of=
=20
different versions around from the beginning. Typically, each major server =
would=20
choose its QUIC implementation and supported versions. So, an active middle=
box=20
that would block traffic on these grounds would instantly break access to a=
=20
major application or content provider. No sane operator would tolerate that=
 for=20
more than an hour.

On 10/05/18 12:33, Marten Seemann wrote:
> The problem with using a specific version for implementations that use an=
d=20
> don=E2=80=99t use the spin bit is that middleboxes can effectively enforc=
e usage of=20
> the spin bit version by blackholing every packet advertising a version th=
at=20
> doesn=E2=80=99t use the spin bit. If only a few middleboxes do that, this=
 would force=20
> *all* implementations to avoid these versions.
> Implementations that don=E2=80=99t want to expose their RTT would then ha=
ve to=20
> negotiate a version that is supposed to use the spin bit, but then grease=
 the=20
> corresponding bits in order to preserve their privacy. Of course, this wo=
uld=20
> only work if the peer doesn=E2=80=99t enforce compliance. Otherwise, we=
=E2=80=99ll end up in a=20
> world where it=E2=80=99s basically impossible to opt-out of the spin-bit.
>
> On Fri, Oct 5, 2018 at 12:15 Marcus Ihlar <marcus.ihlar@ericsson.com=20
> <mailto:marcus.ihlar@ericsson.com>> wrote:
>
>     Hi,
>     I like this approach since it allows us to disregard non-spinning flo=
ws by
>     simply observing the initial handshake. This saves us quite some work.
>     On the heuristics part, we cannot get away from it, even if we see the
>     spin version in the initial handshake as there=C2=B4s no guarantee th=
at an
>     endpoint will set the bit properly anyway.
>     However, for the version where the intent to use spinbit is explicit =
it
>     actually makes sense for an endpoint to treat non-participating behav=
ior
>     as a protocol error.
>
>     Marcus
>
>     -----Original Message-----
>     From: QUIC <quic-bounces@ietf.org <mailto:quic-bounces@ietf.org>> On
>     Behalf Of Mike Bishop
>     Sent: den 5 oktober 2018 00:40
>     To: alexandre.ferrieux@orange.com <mailto:alexandre.ferrieux@orange.c=
om>;
>     Kazuho Oku <kazuhooku@gmail.com <mailto:kazuhooku@gmail.com>>
>     Cc: Brian Trammell <ietf@trammell.ch <mailto:ietf@trammell.ch>>; IETF=
 QUIC
>     WG <quic@ietf.org <mailto:quic@ietf.org>>; Christian Huitema
>     <huitema@huitema.net <mailto:huitema@huitema.net>>
>     Subject: RE: Spin bit as a negotiated option
>
>     So long as this is the only thing being negotiated, it's not too bad.=
=C2=A0 If
>     we want to negotiate other things, it quickly gets out of hand.=C2=A0=
 One could
>     plausibly argue that the spin bit is special in that we actually want
>     parties observing the transaction to understand which option has been
>     selected.
>
>     It's important to remember, though, that this is information you get =
only
>     at the beginning of a new connection.=C2=A0 If there's migration or N=
AT
>     rebinding, it's not guaranteed (and in fact, not intended) than you c=
an
>     correlate it back to a particular previous handshake.=C2=A0 You'll st=
ill either
>     need heuristics to identify whether the spin bit is actually in use, =
or
>     you'll need to ignore any traffic for which you didn't see the handsh=
ake.
>
>     -----Original Message-----
>     From: QUIC <quic-bounces@ietf.org <mailto:quic-bounces@ietf.org>> On
>     Behalf Of alexandre.ferrieux@orange.com <mailto:alexandre.ferrieux@or=
ange.com>
>     Sent: Thursday, October 4, 2018 3:47 AM
>     To: Kazuho Oku <kazuhooku@gmail.com <mailto:kazuhooku@gmail.com>>
>     Cc: Brian Trammell <ietf@trammell.ch <mailto:ietf@trammell.ch>>; IETF=
 QUIC
>     WG <quic@ietf.org <mailto:quic@ietf.org>>; Christian Huitema
>     <huitema@huitema.net <mailto:huitema@huitema.net>>
>     Subject: Re: Spin bit as a negotiated option
>
>     Thanks Kazuho. Using version numbers directly was an obvious choice, =
but
>     so far I was discouraged by strong language in the spec, saying 0x000=
00001
>     was the unavoidable point of convergence after all 0xFF0000XX experim=
ents.
>     So in essence you're proposing to weaken that a bit, right ?
>
>     If so, how do you envision segmenting the version number space ?
>
>     =C2=A0 - direct enumeration:
>
>     =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x00000001 =3D v1dry
>     =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x00000002 =3D v1 + spinbit
>     =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x00000003 =3D v1 + spinbit + VEC
>
>     =C2=A0 - low order bits for options:
>
>     =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x000001XX =3D v1 + option XX
>     =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x000002YY =3D v2 + option YY
>
>     Also, are we sure that this explosion won't weigh on the new VN schem=
e,
>     inducing slower convergence due to longer lists on either side ?
>
>     On 10/04/18 11:50, Kazuho Oku wrote:
>     > Hi,
>     >
>     > Thank you for starting the discussion specific to how we could
>     > possibly negotiate the use of spin bits.
>     >
>     > Regarding the topic, my preference goes to using the version number
>     > field of the long header for negotiating the presence of spin bits,=
 or
>     > any additional signal being exposed to the network.
>     >
>     > For example, QUICv1 without spin bit could use version 0x101, and v1
>     > with spin bit could use 0x102. In the future, we can assign a
>     > different version number for QUICv1 with multiple spin + VEC (or
>     > people interested in testing the feature can designate a private
>     > version number even before that).
>     >
>     > I see the following benefits to using the version field as a method=
 to
>     > negotiate the use of spin bits.
>     >
>     > 1. One of the concern regarding spin bits has been that they could
>     > lead to ossification. Spin bits are not part of the Invariants, but=
 if
>     > the observation tools start looking at those bits without checking =
the
>     > version number field, we will have the pressure to not change how t=
he
>     > bits are used. Using the version number to indicate the presence of
>     > spin bits is the best approach to resolve such concern.
>     >
>     > 2. We have hoped to roll out multiple versions of QUIC in a small
>     > interval so that the version number field does not get ossified. The
>     > best solution is obviously to roll out two flavors of the protocol
>     > that uses different version numbers at the same time. We will have a
>     > real-world use of version negotiation from day one, because we are =
in
>     > a condition where implementors have different opinions on if they
>     > should support spin bit :-)
>     >
>     > The blocker to this approach has been version negotiation requiring=
 an
>     > additional round-trip, but that is going to be resolved by #1755.
>     >
>     > 2018=E5=B9=B410=E6=9C=883=E6=97=A5(=E6=B0=B4) 19:06 <alexandre.ferr=
ieux@orange.com
>     <mailto:alexandre.ferrieux@orange.com>>:
>     >>
>     >> On 10/03/18 09:58, Brian Trammell (IETF) wrote:
>     >> > Backing off the MUST for now for such situations is IMO a good
>     >> > tradeoff, though, especially since we only need fractions of a
>     >> > percent of deployment to start seeing useful signal for
>     >> > baseline/anomaly measurement of large aggregates.
>     >>
>     >> If the consensus is that we must allow for such situations, then
>     >> there are two
>     >> possibilities:
>     >>
>     >>=C2=A0 =C2=A0(a) weak spec language (MAY WISH TO or similar) =3D> m=
any
>     >> implementations will simply drop it
>     >>
>     >>=C2=A0 =C2=A0(b) negotiated option where the negotiation mechanism =
is mandatory
>     >>
>     >> In the vein of (b), Christian suggested offline to introduce
>     >> negotiation to allow for experimentation of the remaining two
>     >> reserved bits. Then may be we can synthesize both ideas by the
>     following proposal:
>     >>
>     >>=C2=A0 =C2=A0- in the first few exchanges of the 5-tuple, use the t=
hree bits for
>     >> option negotiation
>     >>
>     >>=C2=A0 =C2=A0- then use them as defined by the selected option
>     >>
>     >> Example encodings:
>     >>
>     >>=C2=A0 =C2=A0000 : nothing
>     >>=C2=A0 =C2=A0001 : spin bit alone : S00
>     >>=C2=A0 =C2=A0010 : spin bit + VEC : SVV
>     >>=C2=A0 =C2=A0... : other extensions
>     >>
>     >> The negotiation mechanism allows both endpoints to force 000.
>     >> And since it is in the clear first byte, it allows on-path observe=
rs
>     >> to identify the option without resorting to heuristics; this helps=
 in
>     >> the case of a small support ratio.
>     >>
>     >>
>     >>
>     >>
>     >> __________________________________________________________________=
___
>     >> ____________________________________________________
>     >>
>     >> Ce message et ses pieces jointes peuvent contenir des informations
>     >> confidentielles ou privilegiees et ne doivent donc pas etre diffus=
es,
>     >> exploites ou copies sans autorisation. Si vous avez recu ce message
>     >> par erreur, veuillez le signaler a l'expediteur et le detruire ain=
si
>     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 n=
ot 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 h=
ave
>     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 p=
ar
>     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 privileg=
ed
>     information that may be protected by law; they should not be distribu=
ted,
>     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 confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


--------------8A11536F30A95651FDECD257
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8=
">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div class=3D"moz-cite-prefix">As Kazuho reminded, the aim is to fight
      ossification by having a wealth of different versions around from
      the beginning. Typically, each major server would choose its QUIC
      implementation and supported versions. So, an active middlebox
      that would block traffic on these grounds would instantly break
      access to a major application or content provider. No sane
      operator would tolerate that for more than an hour. <br>
      <br>
      On 10/05/18 12:33, Marten Seemann wrote:<br>
    </div>
    <blockquote type=3D"cite"
cite=3D"mid:CAOYVs2oyQO6kC3tMA3Cw7zzzDjiJca4yWRXqaK1ZH3_sbxWWtQ@mail.gmail.=
com">
      <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf=
-8">
      <div>
        <div dir=3D"auto">The problem with using a specific version for
          implementations that use and don=E2=80=99t use the spin bit is th=
at
          middleboxes can effectively enforce usage of the spin bit
          version by blackholing every packet advertising a version that
          doesn=E2=80=99t use the spin bit. If only a few middleboxes do th=
at,
          this would force *all* implementations to avoid these
          versions.</div>
      </div>
      <div dir=3D"auto">Implementations that don=E2=80=99t want to expose t=
heir
        RTT would then have to negotiate a version that is supposed to
        use the spin bit, but then grease the corresponding bits in
        order to preserve their privacy. Of course, this would only work
        if the peer doesn=E2=80=99t enforce compliance. Otherwise, we=E2=80=
=99ll end up
        in a world where it=E2=80=99s basically impossible to opt-out of the
        spin-bit.</div>
      <div><br>
        <div class=3D"gmail_quote">
          <div dir=3D"ltr">On Fri, Oct 5, 2018 at 12:15 Marcus Ihlar &lt;<a
              href=3D"mailto:marcus.ihlar@ericsson.com"
              moz-do-not-send=3D"true">marcus.ihlar@ericsson.com</a>&gt;
            wrote:<br>
          </div>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
            I like this approach since it allows us to disregard
            non-spinning flows by simply observing the initial
            handshake. This saves us quite some work. <br>
            On the heuristics part, we cannot get away from it, even if
            we see the spin version in the initial handshake as there=C2=B4s
            no guarantee that an endpoint will set the bit properly
            anyway.<br>
            However, for the version where the intent to use spinbit is
            explicit it actually makes sense for an endpoint to treat
            non-participating behavior as a protocol error.<br>
            <br>
            Marcus<br>
            <br>
            -----Original Message-----<br>
            From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org"
              target=3D"_blank" moz-do-not-send=3D"true">quic-bounces@ietf.=
org</a>&gt;
            On Behalf Of Mike Bishop<br>
            Sent: den 5 oktober 2018 00:40<br>
            To: <a href=3D"mailto:alexandre.ferrieux@orange.com"
              target=3D"_blank" moz-do-not-send=3D"true">alexandre.ferrieux=
@orange.com</a>;
            Kazuho Oku &lt;<a href=3D"mailto:kazuhooku@gmail.com"
              target=3D"_blank" moz-do-not-send=3D"true">kazuhooku@gmail.co=
m</a>&gt;<br>
            Cc: Brian Trammell &lt;<a href=3D"mailto:ietf@trammell.ch"
              target=3D"_blank" moz-do-not-send=3D"true">ietf@trammell.ch</=
a>&gt;;
            IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org"
              target=3D"_blank" moz-do-not-send=3D"true">quic@ietf.org</a>&=
gt;;
            Christian Huitema &lt;<a href=3D"mailto:huitema@huitema.net"
              target=3D"_blank" moz-do-not-send=3D"true">huitema@huitema.ne=
t</a>&gt;<br>
            Subject: RE: Spin bit as a negotiated option<br>
            <br>
            So long as this is the only thing being negotiated, it's not
            too bad.=C2=A0 If we want to negotiate other things, it quickly
            gets out of hand.=C2=A0 One could plausibly argue that the spin
            bit is special in that we actually want parties observing
            the transaction to understand which option has been
            selected.<br>
            <br>
            It's important to remember, though, that this is information
            you get only at the beginning of a new connection.=C2=A0 If
            there's migration or NAT rebinding, it's not guaranteed (and
            in fact, not intended) than you can correlate it back to a
            particular previous handshake.=C2=A0 You'll still either need
            heuristics to identify whether the spin bit is actually in
            use, or you'll need to ignore any traffic for which you
            didn't see the handshake.<br>
            <br>
            -----Original Message-----<br>
            From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org"
              target=3D"_blank" moz-do-not-send=3D"true">quic-bounces@ietf.=
org</a>&gt;
            On Behalf Of <a href=3D"mailto:alexandre.ferrieux@orange.com"
              target=3D"_blank" moz-do-not-send=3D"true">alexandre.ferrieux=
@orange.com</a><br>
            Sent: Thursday, October 4, 2018 3:47 AM<br>
            To: Kazuho Oku &lt;<a href=3D"mailto:kazuhooku@gmail.com"
              target=3D"_blank" moz-do-not-send=3D"true">kazuhooku@gmail.co=
m</a>&gt;<br>
            Cc: Brian Trammell &lt;<a href=3D"mailto:ietf@trammell.ch"
              target=3D"_blank" moz-do-not-send=3D"true">ietf@trammell.ch</=
a>&gt;;
            IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org"
              target=3D"_blank" moz-do-not-send=3D"true">quic@ietf.org</a>&=
gt;;
            Christian Huitema &lt;<a href=3D"mailto:huitema@huitema.net"
              target=3D"_blank" moz-do-not-send=3D"true">huitema@huitema.ne=
t</a>&gt;<br>
            Subject: Re: Spin bit as a negotiated option<br>
            <br>
            Thanks Kazuho. Using version numbers directly was an obvious
            choice, but so far I was discouraged by strong language in
            the spec, saying 0x00000001 was the unavoidable point of
            convergence after all 0xFF0000XX experiments. So in essence
            you're proposing to weaken that a bit, right ?<br>
            <br>
            If so, how do you envision segmenting the version number
            space ?<br>
            <br>
            =C2=A0 - direct enumeration:<br>
            <br>
            =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x00000001 =3D v1dry<br>
            =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x00000002 =3D v1 + spinbit<br>
            =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x00000003 =3D v1 + spinbit + VEC<b=
r>
            <br>
            =C2=A0 - low order bits for options:<br>
            <br>
            =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x000001XX =3D v1 + option XX<br>
            =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x000002YY =3D v2 + option YY<br>
            <br>
            Also, are we sure that this explosion won't weigh on the new
            VN scheme, inducing slower convergence due to longer lists
            on either side ?<br>
            <br>
            On 10/04/18 11:50, Kazuho Oku wrote:<br>
            &gt; Hi,<br>
            &gt; <br>
            &gt; Thank you for starting the discussion specific to how
            we could <br>
            &gt; possibly negotiate the use of spin bits.<br>
            &gt; <br>
            &gt; Regarding the topic, my preference goes to using the
            version number <br>
            &gt; field of the long header for negotiating the presence
            of spin bits, or <br>
            &gt; any additional signal being exposed to the network.<br>
            &gt; <br>
            &gt; For example, QUICv1 without spin bit could use version
            0x101, and v1 <br>
            &gt; with spin bit could use 0x102. In the future, we can
            assign a <br>
            &gt; different version number for QUICv1 with multiple spin
            + VEC (or <br>
            &gt; people interested in testing the feature can designate
            a private <br>
            &gt; version number even before that).<br>
            &gt; <br>
            &gt; I see the following benefits to using the version field
            as a method to <br>
            &gt; negotiate the use of spin bits.<br>
            &gt; <br>
            &gt; 1. One of the concern regarding spin bits has been that
            they could <br>
            &gt; lead to ossification. Spin bits are not part of the
            Invariants, but if <br>
            &gt; the observation tools start looking at those bits
            without checking the <br>
            &gt; version number field, we will have the pressure to not
            change how the <br>
            &gt; bits are used. Using the version number to indicate the
            presence of <br>
            &gt; spin bits is the best approach to resolve such concern.<br>
            &gt; <br>
            &gt; 2. We have hoped to roll out multiple versions of QUIC
            in a small <br>
            &gt; interval so that the version number field does not get
            ossified. The <br>
            &gt; best solution is obviously to roll out two flavors of
            the protocol <br>
            &gt; that uses different version numbers at the same time.
            We will have a <br>
            &gt; real-world use of version negotiation from day one,
            because we are in <br>
            &gt; a condition where implementors have different opinions
            on if they <br>
            &gt; should support spin bit :-)<br>
            &gt; <br>
            &gt; The blocker to this approach has been version
            negotiation requiring an <br>
            &gt; additional round-trip, but that is going to be resolved
            by #1755.<br>
            &gt; <br>
            &gt; 2018=E5=B9=B410=E6=9C=883=E6=97=A5(=E6=B0=B4) 19:06 &lt;<a
              href=3D"mailto:alexandre.ferrieux@orange.com"
              target=3D"_blank" moz-do-not-send=3D"true">alexandre.ferrieux=
@orange.com</a>&gt;:<br>
            &gt;&gt;<br>
            &gt;&gt; On 10/03/18 09:58, Brian Trammell (IETF) wrote:<br>
            &gt;&gt; &gt; Backing off the MUST for now for such
            situations is IMO a good <br>
            &gt;&gt; &gt; tradeoff, though, especially since we only
            need fractions of a <br>
            &gt;&gt; &gt; percent of deployment to start seeing useful
            signal for <br>
            &gt;&gt; &gt; baseline/anomaly measurement of large
            aggregates.<br>
            &gt;&gt;<br>
            &gt;&gt; If the consensus is that we must allow for such
            situations, then <br>
            &gt;&gt; there are two<br>
            &gt;&gt; possibilities:<br>
            &gt;&gt;<br>
            &gt;&gt;=C2=A0 =C2=A0(a) weak spec language (MAY WISH TO or sim=
ilar)
            =3D&gt; many <br>
            &gt;&gt; implementations will simply drop it<br>
            &gt;&gt;<br>
            &gt;&gt;=C2=A0 =C2=A0(b) negotiated option where the negotiation
            mechanism is mandatory<br>
            &gt;&gt;<br>
            &gt;&gt; In the vein of (b), Christian suggested offline to
            introduce <br>
            &gt;&gt; negotiation to allow for experimentation of the
            remaining two <br>
            &gt;&gt; reserved bits. Then may be we can synthesize both
            ideas by the following proposal:<br>
            &gt;&gt;<br>
            &gt;&gt;=C2=A0 =C2=A0- in the first few exchanges of the 5-tupl=
e, use
            the three bits for <br>
            &gt;&gt; option negotiation<br>
            &gt;&gt;<br>
            &gt;&gt;=C2=A0 =C2=A0- then use them as defined by the selected=
 option<br>
            &gt;&gt;<br>
            &gt;&gt; Example encodings:<br>
            &gt;&gt;<br>
            &gt;&gt;=C2=A0 =C2=A0000 : nothing<br>
            &gt;&gt;=C2=A0 =C2=A0001 : spin bit alone : S00<br>
            &gt;&gt;=C2=A0 =C2=A0010 : spin bit + VEC : SVV<br>
            &gt;&gt;=C2=A0 =C2=A0... : other extensions<br>
            &gt;&gt;<br>
            &gt;&gt; The negotiation mechanism allows both endpoints to
            force 000.<br>
            &gt;&gt; And since it is in the clear first byte, it allows
            on-path observers <br>
            &gt;&gt; to identify the option without resorting to
            heuristics; this helps in <br>
            &gt;&gt; the case of a small support ratio.<br>
            &gt;&gt;<br>
            &gt;&gt;<br>
            &gt;&gt;<br>
            &gt;&gt;<br>
            &gt;&gt;
            _______________________________________________________________=
______<br>
            &gt;&gt;
            ____________________________________________________<br>
            &gt;&gt;<br>
            &gt;&gt; Ce message et ses pieces jointes peuvent contenir
            des informations <br>
            &gt;&gt; confidentielles ou privilegiees et ne doivent donc
            pas etre diffuses, <br>
            &gt;&gt; exploites ou copies sans autorisation. Si vous avez
            recu ce message <br>
            &gt;&gt; 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.<br>
            &gt;&gt;<br>
            &gt;&gt; This message and its attachments may contain
            confidential or <br>
            &gt;&gt; privileged information that may be protected by
            law; they should not be distributed, used or copied without
            authorisation.<br>
            &gt;&gt; If you have received this email in error, please
            notify the sender and delete this message and its
            attachments.<br>
            &gt;&gt; As emails may be altered, Orange is not liable for
            messages that have been modified, changed or falsified.<br>
            &gt;&gt; Thank you.<br>
            &gt;&gt;<br>
            &gt; <br>
            &gt; <br>
            <br>
            <br>
            <br>
___________________________________________________________________________=
______________________________________________<br>
            <br>
            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.<br>
            <br>
            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.<br>
            If you have received this email in error, please notify the
            sender and delete this message and its attachments.<br>
            As emails may be altered, Orange is not liable for messages
            that have been modified, changed or falsified.<br>
            Thank you.<br>
            <br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
  <PRE>____________________________________________________________________=
_____________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.
</PRE></body>
</html>

--------------8A11536F30A95651FDECD257--


From nobody Fri Oct  5 03:56:16 2018
Return-Path: <marcus.ihlar@ericsson.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 983A2130E3A for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 03:56:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.755
X-Spam-Level: 
X-Spam-Status: No, score=-4.755 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=hR53NDcB; dkim=pass (1024-bit key) header.d=ericsson.com header.b=gB6UR+fo
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 mdMKqh6WH-TB for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 03:56:10 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 EFC62130E05 for <quic@ietf.org>; Fri,  5 Oct 2018 03:56:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1538736968; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=bIa/dvwHZQm+1/pGpORCdwcvMULpViFcsqo2+TbAX/g=; b=hR53NDcBFWVRwBWtsCaAaCUzmNYRMeZYlNgnTDcSDLsKD+vMbWpVQF65ifx6zemT QYhHcD68no4hU5RD6rZdRDVXYuVbvbWW12d3Wl+WF3y7ApnXIA2eZnujp8V1HbN1 1MpuzOgzkygoGRF2hA1kf7NndNn1MdY9OZyLelzvcQg=;
X-AuditID: c1b4fb25-cd2929c0000013ad-9c-5bb74348ab33
Received: from ESESSMB501.ericsson.se (Unknown_Domain [153.88.183.119]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 84.9F.05037.84347BB5; Fri,  5 Oct 2018 12:56:08 +0200 (CEST)
Received: from ESESSMB503.ericsson.se (153.88.183.164) by ESESSMB501.ericsson.se (153.88.183.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 5 Oct 2018 12:56:07 +0200
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB503.ericsson.se (153.88.183.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Fri, 5 Oct 2018 12:56:07 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bIa/dvwHZQm+1/pGpORCdwcvMULpViFcsqo2+TbAX/g=; b=gB6UR+fo0k4o4bi9P8kGVMrvEvwLzmhgfpBUlw6jgKHZKSwb4uCW/CwaXm6D7i1ShdLokR9QsIDjsEmvb9J6oh1jpJhTC14jo6OOoEAGyhXGZikS4y09eti0pPu3DamvlX3JGEUDDXbNBcArTu8sAFl8Th6if7JsfR7ctFJGVtk=
Received: from HE1PR0701MB2393.eurprd07.prod.outlook.com (10.168.128.12) by HE1PR0701MB2764.eurprd07.prod.outlook.com (10.168.188.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1228.8; Fri, 5 Oct 2018 10:56:05 +0000
Received: from HE1PR0701MB2393.eurprd07.prod.outlook.com ([fe80::400d:3614:de33:b3a8]) by HE1PR0701MB2393.eurprd07.prod.outlook.com ([fe80::400d:3614:de33:b3a8%4]) with mapi id 15.20.1228.011; Fri, 5 Oct 2018 10:56:05 +0000
From: Marcus Ihlar <marcus.ihlar@ericsson.com>
To: "martenseemann@gmail.com" <martenseemann@gmail.com>
CC: "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, "huitema@huitema.net" <huitema@huitema.net>, "ietf@trammell.ch" <ietf@trammell.ch>, "kazuhooku@gmail.com" <kazuhooku@gmail.com>, "mbishop@evequefou.be" <mbishop@evequefou.be>, "quic@ietf.org" <quic@ietf.org>
Subject: RE: Spin bit as a negotiated option
Thread-Topic: Spin bit as a negotiated option
Thread-Index: AQHUWwDJ8lpz5mbOFU6DOhcb6dfH26UO2VEAgAAPtACAAMdZAIAAuUuAgAAN9oCAAAGHcA==
Date: Fri, 5 Oct 2018 10:56:05 +0000
Message-ID: <HE1PR0701MB23938FB7C6C13902AC04B637E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com> <CY4PR22MB0983849F01312CBE18A4F69CDAEA0@CY4PR22MB0983.namprd22.prod.outlook.com> <HE1PR0701MB2393C0B9756449E5CC060723E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <CAOYVs2oyQO6kC3tMA3Cw7zzzDjiJca4yWRXqaK1ZH3_sbxWWtQ@mail.gmail.com>
In-Reply-To: <CAOYVs2oyQO6kC3tMA3Cw7zzzDjiJca4yWRXqaK1ZH3_sbxWWtQ@mail.gmail.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=marcus.ihlar@ericsson.com; 
x-originating-ip: [192.176.1.95]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR0701MB2764; 6:FnxpjlQ74rQt7EysBPnaZKXupmxYmhmHoa0LYYHdoMe0lEOxrtOHsflI97KRt0oEURw5hVcUnYapsDLGCx1mmA7EPx3nbsecVmNSLQ6J1CtzFMRDuFvQE521rFttzni0biVaATQN/DpQQymGHn4+fiTkF+XP3Y6hQIwnbgn5joHyI9oQSoQOQ3Q/OCfYM/eXBxc0WUrgNeyJVwmz3INxgTRCiklIeyrSoTZfoFymrDrGYu5j+XGKDbs3nldG3DRwAZkWdnRr5NBP7kgWlZQGCdKc72S6m4o/YG/WQt82QaN/ZU81ryNAww6lSC9Sv/zJmWjG8Y6fOnKdFyuwFRYBs/nZLMfY3N5jbegeMYVkHGSB31jiFKQKxIrvSKwLqpxlgQyz0/kuYxdH0LHlQ7aayD0xLgyS5W/QBzFK830mU4bdfg1+O0bOEKf5s4A/kRio6F/vSeb9hBMD9v9IUdZQHA==; 5:wFydjv7mS0YmNRHytwCfHfuzqvQAfCoJp9RXWZqSB9yV5DB+tWNMHrXUVzJnAlHXSaaN08e9aN4KiHnkLlCC//NSzEmoRGZvcesv3qLlTvhjZc5d5gEQrHmkMtNyaxe0NVJYIMxRd9d98mMn09Sez6DvxF5Ea7oIxrz4vs8DZGI=; 7:YiqMvosW4jJyjkWWdVwFaX+GfneRMON4dxvTsFZElZ49kwMzQY4YQHEB0i+4eeAsqBTc7xyjzONBayQ+BU/89XKFM5Qw6rmLKphm4XdUE9sGGxcrE8Y3Rn2NAaiK+bX7sufRvPtg0KHhALjV7MetEO2+zFBiahIi1Y4cF2cYtRCZDdNEs9xOlYKvZE7PFmds0CVz7M1xSP/LQgMHjYEeDUpXbrm02vDTOFssZ65+LwmxOSI9Bs7WR/OJtTZXY2ZP
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 1d1a33cf-a0df-4c16-b015-08d62ab125ff
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:HE1PR0701MB2764; 
x-ms-traffictypediagnostic: HE1PR0701MB2764:
x-microsoft-antispam-prvs: <HE1PR0701MB2764309BFEDAA1E877255033E2EB0@HE1PR0701MB2764.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(72170088055959)(85827821059158)(248295561703944)(37575265505322)(161740460382875)(18271650672692)(100405760836317)(21748063052155)(28532068793085)(190501279198761);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231355)(944501410)(52105095)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(201708071742011)(7699051); SRVR:HE1PR0701MB2764; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0701MB2764; 
x-forefront-prvs: 0816F1D86E
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(376002)(136003)(396003)(366004)(346002)(199004)(189003)(13464003)(7736002)(446003)(6506007)(93886005)(5660300001)(25786009)(53546011)(186003)(1411001)(11346002)(102836004)(76176011)(2351001)(7696005)(81156014)(54906003)(39060400002)(6116002)(345774005)(790700001)(3846002)(8936002)(71190400001)(71200400001)(5630700001)(97736004)(26005)(86362001)(81166006)(14454004)(5250100002)(8676002)(1730700003)(2906002)(256004)(478600001)(2501003)(14444005)(5024004)(74316002)(68736007)(551934003)(114624004)(561944003)(6916009)(316002)(4326008)(106356001)(99286004)(1361003)(105586002)(5640700003)(6306002)(54896002)(486006)(55016002)(6436002)(53936002)(236005)(229853002)(44832011)(2900100001)(476003)(66066001)(9686003)(6246003)(33656002)(473944003)(414714003); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0701MB2764; H:HE1PR0701MB2393.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: bf/XM/R0loyXjrGn2Exgwkj4QuWwfgfp4hAKWB6V2WpJ7fUhLegcDiNZ0HAdqmn4s58MkrREkMyR/pi/REnIEQXvZJgcOhrfQOmj7eD+OWoNdGtpRcLw7F3tRr8HOIjYc2P38Z6g0naVRokbvapJxcHx1BRN4UkWWTf1+1JPqyam58feGXWhvW0LnWdEduYC1BVIq+RRbJxDeb+QJw3UsiZ3RMQgmVgrjSegGxst7C60duxeXN9/t+BvA7e3rWPkUWn6UgkepvCj0eCDg9VbEoOXifW3y8njMzbTxXjdOus1L3UCDae/AKn4vXmo3KxfUv/ng4586W8b5ALPV4QLzdUvGDAEZ8YiPneBMF9avSk=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HE1PR0701MB23938FB7C6C13902AC04B637E2EB0HE1PR0701MB2393_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 1d1a33cf-a0df-4c16-b015-08d62ab125ff
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Oct 2018 10:56:05.3144 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2764
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Sa0hTYRjHec9l57iavK7Eh6LUdaGLLq2gdaES+3C+FNUHr1FbejBRp+ws SyHSqMxpNE1Tp5Lp0DBs1bR1g9SKWkiGkeFsmmY1aZV2T8PyeBb07f9//r/3ed7n5WVJZS89 j03VG3mDXpeuksmpqjjHoXAu2pEYYX3Fahp/BmvO5lczmqvHP8o0H8YLaM2x+lpGM/HOxGiK 62ZtZbjuh1do7qbFzXCuyscUZ7X+Irjjb50ybuRuFbVTliDflMynp2bzhlWbtfID7zr66Kzi SuLw0KlJKg+9MhMm5McCXgtfn11AJiRnlfgBgl+jYzLJfEPQ0uWiJNNAQK+tlRQNhc0kXLzQ 5UvOEeAd9JCSeYOgrKKRFDvLsBq63EUyUc/F6+B23zAhQiSuIeBP7X1GDObgMBi3TSEJCof8 5kuEpGPgi/cTLWoKLwbvo9IZXoG18Ltvkpam3ZXD9WL79DSW9cO74EyhXmQQXgCDPwYoUZM4 CFwj532rYrDe6SYlHQijr6do8SjCe2CiP0sqh0Bhu9eHL4Ce80UzLwO4nQGzp4mRgnAYKy+f GQt4OwyepCTGiaCgz0RL9TDoeBkg4ZlQ2NTmY54gsNhLfAMWQvPpIcqMIiz/XVXSmeAc6CIt MysHgLNqhLJMtyXxcrDdWiUhoVBWNMRIehmcqKll/q/XIaYZBQq8sD8jZfUaNW9ITRKETL1a zxuvoenf1tE6ueQGeuaN6kSYRarZCv/1jkQlrcsWcjI6EbCkaq4i1ng9UalI1uXk8obMfYaD 6bzQieazlCpIMbTOnqDEKTojn8bzWbzhX0qwfvPy0MEVe4vsatXojpI760M2x28bXFm9KO55 3SNjPT1e7ozqd0fGGgVuZ299+NGKsVtPlyo8m1Lu5VjTSk0NlfaBJpqPScota2PSvqvf6Bq0 ga4HEwUbcv1tkbOHTxmmQh+3vAhxm177R70fLm46smXW5bie4Ozd49EbPY60l9r4z4WNKko4 oItcQRoE3V9zokMmaQMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/vLSS31mkvvdkA-qQuwFvFEYeuJU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Oct 2018 10:56:15 -0000

--_000_HE1PR0701MB23938FB7C6C13902AC04B637E2EB0HE1PR0701MB2393_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SSBzZWUgeW91ciBwb2ludCwgYnV0IEkgZG9uwrR0IGJlbGlldmUgaXQgaXMgYSBwYXJ0aWN1bGFy
bHkgcmVhbGlzdGljIHNjZW5hcmlvLg0KDQpJdCBpcyBpbiB0aGUgaW50ZXJlc3Qgb2YgdGhlIG5l
dHdvcmsgb3BlcmF0b3JzIHRvIGVuc3VyZSB0aGF0IHRoZWlyIHN1YnNjcmliZXJzIGhhcyBhcyBn
b29kIGFuZCBjb25zaXN0ZW50IGV4cGVyaWVuY2UuDQoNCkJsYWNraG9saW5nIHZlcnNpb25zIG9m
IFFVSUMgaGFzIHRoZSBwb3RlbnRpYWwgb2YgY29tcGxldGVseSBkaXNydXB0aW5nIHNlcnZpY2Vz
IGFuZCBpbnRyb2R1Y2UgaW5jb25zaXN0ZW50IGJlaGF2aW9yLg0KDQpUaGUgc3BpbmJpdCBpcyBp
bnRlbmRlZCBhcyBhIHRvb2wgdG8gYXNzaXN0IHRyb3VibGVzaG9vdGluZyBhbmQgcXVhbGl0eSBt
b25pdG9yaW5nLiBFeHBsaWNpdGx5IGludHJvZHVjaW5nIHBvdGVudGlhbGx5IHBvb3IgbmV0d29y
ayBleHBlcmllbmNlIHdpdGggdGhlIGhvcGVzIHRoYXQgeW91ciB0cm91Ymxlc2hvb3RpbmcgLyBt
b25pdG9yaW5nIGNhcGFiaWxpdGllcyBpbXByb3ZlcyBpcyBhIHJlYWxseSBiYWQgaWRlYSwgZXZl
biBmb3IgdGhlIG1vc3QgY3luaWNhbCBuZXR3b3JrIG9wZXJhdG9yLg0KDQoNCg0KRnJvbTogTWFy
dGVuIFNlZW1hbm4gPG1hcnRlbnNlZW1hbm5AZ21haWwuY29tPg0KU2VudDogZGVuIDUgb2t0b2Jl
ciAyMDE4IDEyOjMzDQpUbzogTWFyY3VzIElobGFyIDxtYXJjdXMuaWhsYXJAZXJpY3Nzb24uY29t
Pg0KQ2M6IGFsZXhhbmRyZS5mZXJyaWV1eEBvcmFuZ2UuY29tOyBodWl0ZW1hQGh1aXRlbWEubmV0
OyBpZXRmQHRyYW1tZWxsLmNoOyBrYXp1aG9va3VAZ21haWwuY29tOyBtYmlzaG9wQGV2ZXF1ZWZv
dS5iZTsgcXVpY0BpZXRmLm9yZw0KU3ViamVjdDogUmU6IFNwaW4gYml0IGFzIGEgbmVnb3RpYXRl
ZCBvcHRpb24NCg0KDQoNClRoZSBwcm9ibGVtIHdpdGggdXNpbmcgYSBzcGVjaWZpYyB2ZXJzaW9u
IGZvciBpbXBsZW1lbnRhdGlvbnMgdGhhdCB1c2UgYW5kIGRvbuKAmXQgdXNlIHRoZSBzcGluIGJp
dCBpcyB0aGF0IG1pZGRsZWJveGVzIGNhbiBlZmZlY3RpdmVseSBlbmZvcmNlIHVzYWdlIG9mIHRo
ZSBzcGluIGJpdCB2ZXJzaW9uIGJ5IGJsYWNraG9saW5nIGV2ZXJ5IHBhY2tldCBhZHZlcnRpc2lu
ZyBhIHZlcnNpb24gdGhhdCBkb2VzbuKAmXQgdXNlIHRoZSBzcGluIGJpdC4gSWYgb25seSBhIGZl
dyBtaWRkbGVib3hlcyBkbyB0aGF0LCB0aGlzIHdvdWxkIGZvcmNlICphbGwqIGltcGxlbWVudGF0
aW9ucyB0byBhdm9pZCB0aGVzZSB2ZXJzaW9ucy4NCg0KSW1wbGVtZW50YXRpb25zIHRoYXQgZG9u
4oCZdCB3YW50IHRvIGV4cG9zZSB0aGVpciBSVFQgd291bGQgdGhlbiBoYXZlIHRvIG5lZ290aWF0
ZSBhIHZlcnNpb24gdGhhdCBpcyBzdXBwb3NlZCB0byB1c2UgdGhlIHNwaW4gYml0LCBidXQgdGhl
biBncmVhc2UgdGhlIGNvcnJlc3BvbmRpbmcgYml0cyBpbiBvcmRlciB0byBwcmVzZXJ2ZSB0aGVp
ciBwcml2YWN5LiBPZiBjb3Vyc2UsIHRoaXMgd291bGQgb25seSB3b3JrIGlmIHRoZSBwZWVyIGRv
ZXNu4oCZdCBlbmZvcmNlIGNvbXBsaWFuY2UuIE90aGVyd2lzZSwgd2XigJlsbCBlbmQgdXAgaW4g
YSB3b3JsZCB3aGVyZSBpdOKAmXMgYmFzaWNhbGx5IGltcG9zc2libGUgdG8gb3B0LW91dCBvZiB0
aGUgc3Bpbi1iaXQuDQoNCg0KDQpPbiBGcmksIE9jdCA1LCAyMDE4IGF0IDEyOjE1IE1hcmN1cyBJ
aGxhciA8bWFyY3VzLmlobGFyQGVyaWNzc29uLmNvbTxtYWlsdG86bWFyY3VzLmlobGFyQGVyaWNz
c29uLmNvbT4+IHdyb3RlOg0KDQogICBIaSwNCiAgIEkgbGlrZSB0aGlzIGFwcHJvYWNoIHNpbmNl
IGl0IGFsbG93cyB1cyB0byBkaXNyZWdhcmQgbm9uLXNwaW5uaW5nIGZsb3dzIGJ5IHNpbXBseSBv
YnNlcnZpbmcgdGhlIGluaXRpYWwgaGFuZHNoYWtlLiBUaGlzIHNhdmVzIHVzIHF1aXRlIHNvbWUg
d29yay4NCiAgIE9uIHRoZSBoZXVyaXN0aWNzIHBhcnQsIHdlIGNhbm5vdCBnZXQgYXdheSBmcm9t
IGl0LCBldmVuIGlmIHdlIHNlZSB0aGUgc3BpbiB2ZXJzaW9uIGluIHRoZSBpbml0aWFsIGhhbmRz
aGFrZSBhcyB0aGVyZcK0cyBubyBndWFyYW50ZWUgdGhhdCBhbiBlbmRwb2ludCB3aWxsIHNldCB0
aGUgYml0IHByb3Blcmx5IGFueXdheS4NCiAgIEhvd2V2ZXIsIGZvciB0aGUgdmVyc2lvbiB3aGVy
ZSB0aGUgaW50ZW50IHRvIHVzZSBzcGluYml0IGlzIGV4cGxpY2l0IGl0IGFjdHVhbGx5IG1ha2Vz
IHNlbnNlIGZvciBhbiBlbmRwb2ludCB0byB0cmVhdCBub24tcGFydGljaXBhdGluZyBiZWhhdmlv
ciBhcyBhIHByb3RvY29sIGVycm9yLg0KDQogICBNYXJjdXMNCg0KICAgLS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCiAgIEZyb206IFFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86
cXVpYy1ib3VuY2VzQGlldGYub3JnPj4gT24gQmVoYWxmIE9mIE1pa2UgQmlzaG9wDQogICBTZW50
OiBkZW4gNSBva3RvYmVyIDIwMTggMDA6NDANCiAgIFRvOiBhbGV4YW5kcmUuZmVycmlldXhAb3Jh
bmdlLmNvbTxtYWlsdG86YWxleGFuZHJlLmZlcnJpZXV4QG9yYW5nZS5jb20+OyBLYXp1aG8gT2t1
IDxrYXp1aG9va3VAZ21haWwuY29tPG1haWx0bzprYXp1aG9va3VAZ21haWwuY29tPj4NCiAgIENj
OiBCcmlhbiBUcmFtbWVsbCA8aWV0ZkB0cmFtbWVsbC5jaDxtYWlsdG86aWV0ZkB0cmFtbWVsbC5j
aD4+OyBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc8bWFpbHRvOnF1aWNAaWV0Zi5vcmc+Pjsg
Q2hyaXN0aWFuIEh1aXRlbWEgPGh1aXRlbWFAaHVpdGVtYS5uZXQ8bWFpbHRvOmh1aXRlbWFAaHVp
dGVtYS5uZXQ+Pg0KICAgU3ViamVjdDogUkU6IFNwaW4gYml0IGFzIGEgbmVnb3RpYXRlZCBvcHRp
b24NCg0KICAgU28gbG9uZyBhcyB0aGlzIGlzIHRoZSBvbmx5IHRoaW5nIGJlaW5nIG5lZ290aWF0
ZWQsIGl0J3Mgbm90IHRvbyBiYWQuICBJZiB3ZSB3YW50IHRvIG5lZ290aWF0ZSBvdGhlciB0aGlu
Z3MsIGl0IHF1aWNrbHkgZ2V0cyBvdXQgb2YgaGFuZC4gIE9uZSBjb3VsZCBwbGF1c2libHkgYXJn
dWUgdGhhdCB0aGUgc3BpbiBiaXQgaXMgc3BlY2lhbCBpbiB0aGF0IHdlIGFjdHVhbGx5IHdhbnQg
cGFydGllcyBvYnNlcnZpbmcgdGhlIHRyYW5zYWN0aW9uIHRvIHVuZGVyc3RhbmQgd2hpY2ggb3B0
aW9uIGhhcyBiZWVuIHNlbGVjdGVkLg0KDQogICBJdCdzIGltcG9ydGFudCB0byByZW1lbWJlciwg
dGhvdWdoLCB0aGF0IHRoaXMgaXMgaW5mb3JtYXRpb24geW91IGdldCBvbmx5IGF0IHRoZSBiZWdp
bm5pbmcgb2YgYSBuZXcgY29ubmVjdGlvbi4gIElmIHRoZXJlJ3MgbWlncmF0aW9uIG9yIE5BVCBy
ZWJpbmRpbmcsIGl0J3Mgbm90IGd1YXJhbnRlZWQgKGFuZCBpbiBmYWN0LCBub3QgaW50ZW5kZWQp
IHRoYW4geW91IGNhbiBjb3JyZWxhdGUgaXQgYmFjayB0byBhIHBhcnRpY3VsYXIgcHJldmlvdXMg
aGFuZHNoYWtlLiAgWW91J2xsIHN0aWxsIGVpdGhlciBuZWVkIGhldXJpc3RpY3MgdG8gaWRlbnRp
Znkgd2hldGhlciB0aGUgc3BpbiBiaXQgaXMgYWN0dWFsbHkgaW4gdXNlLCBvciB5b3UnbGwgbmVl
ZCB0byBpZ25vcmUgYW55IHRyYWZmaWMgZm9yIHdoaWNoIHlvdSBkaWRuJ3Qgc2VlIHRoZSBoYW5k
c2hha2UuDQoNCiAgIC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQogICBGcm9tOiBRVUlDIDxx
dWljLWJvdW5jZXNAaWV0Zi5vcmc8bWFpbHRvOnF1aWMtYm91bmNlc0BpZXRmLm9yZz4+IE9uIEJl
aGFsZiBPZiBhbGV4YW5kcmUuZmVycmlldXhAb3JhbmdlLmNvbTxtYWlsdG86YWxleGFuZHJlLmZl
cnJpZXV4QG9yYW5nZS5jb20+DQogICBTZW50OiBUaHVyc2RheSwgT2N0b2JlciA0LCAyMDE4IDM6
NDcgQU0NCiAgIFRvOiBLYXp1aG8gT2t1IDxrYXp1aG9va3VAZ21haWwuY29tPG1haWx0bzprYXp1
aG9va3VAZ21haWwuY29tPj4NCiAgIENjOiBCcmlhbiBUcmFtbWVsbCA8aWV0ZkB0cmFtbWVsbC5j
aDxtYWlsdG86aWV0ZkB0cmFtbWVsbC5jaD4+OyBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc8
bWFpbHRvOnF1aWNAaWV0Zi5vcmc+PjsgQ2hyaXN0aWFuIEh1aXRlbWEgPGh1aXRlbWFAaHVpdGVt
YS5uZXQ8bWFpbHRvOmh1aXRlbWFAaHVpdGVtYS5uZXQ+Pg0KICAgU3ViamVjdDogUmU6IFNwaW4g
Yml0IGFzIGEgbmVnb3RpYXRlZCBvcHRpb24NCg0KICAgVGhhbmtzIEthenVoby4gVXNpbmcgdmVy
c2lvbiBudW1iZXJzIGRpcmVjdGx5IHdhcyBhbiBvYnZpb3VzIGNob2ljZSwgYnV0IHNvIGZhciBJ
IHdhcyBkaXNjb3VyYWdlZCBieSBzdHJvbmcgbGFuZ3VhZ2UgaW4gdGhlIHNwZWMsIHNheWluZyAw
eDAwMDAwMDAxIHdhcyB0aGUgdW5hdm9pZGFibGUgcG9pbnQgb2YgY29udmVyZ2VuY2UgYWZ0ZXIg
YWxsIDB4RkYwMDAwWFggZXhwZXJpbWVudHMuIFNvIGluIGVzc2VuY2UgeW91J3JlIHByb3Bvc2lu
ZyB0byB3ZWFrZW4gdGhhdCBhIGJpdCwgcmlnaHQgPw0KDQogICBJZiBzbywgaG93IGRvIHlvdSBl
bnZpc2lvbiBzZWdtZW50aW5nIHRoZSB2ZXJzaW9uIG51bWJlciBzcGFjZSA/DQoNCiAgICAgLSBk
aXJlY3QgZW51bWVyYXRpb246DQoNCiAgICAgICAgICAgMHgwMDAwMDAwMSA9IHYxZHJ5DQogICAg
ICAgICAgIDB4MDAwMDAwMDIgPSB2MSArIHNwaW5iaXQNCiAgICAgICAgICAgMHgwMDAwMDAwMyA9
IHYxICsgc3BpbmJpdCArIFZFQw0KDQogICAgIC0gbG93IG9yZGVyIGJpdHMgZm9yIG9wdGlvbnM6
DQoNCiAgICAgICAgICAgMHgwMDAwMDFYWCA9IHYxICsgb3B0aW9uIFhYDQogICAgICAgICAgIDB4
MDAwMDAyWVkgPSB2MiArIG9wdGlvbiBZWQ0KDQogICBBbHNvLCBhcmUgd2Ugc3VyZSB0aGF0IHRo
aXMgZXhwbG9zaW9uIHdvbid0IHdlaWdoIG9uIHRoZSBuZXcgVk4gc2NoZW1lLCBpbmR1Y2luZyBz
bG93ZXIgY29udmVyZ2VuY2UgZHVlIHRvIGxvbmdlciBsaXN0cyBvbiBlaXRoZXIgc2lkZSA/DQoN
CiAgIE9uIDEwLzA0LzE4IDExOjUwLCBLYXp1aG8gT2t1IHdyb3RlOg0KICAgPiBIaSwNCiAgID4N
CiAgID4gVGhhbmsgeW91IGZvciBzdGFydGluZyB0aGUgZGlzY3Vzc2lvbiBzcGVjaWZpYyB0byBo
b3cgd2UgY291bGQNCiAgID4gcG9zc2libHkgbmVnb3RpYXRlIHRoZSB1c2Ugb2Ygc3BpbiBiaXRz
Lg0KICAgPg0KICAgPiBSZWdhcmRpbmcgdGhlIHRvcGljLCBteSBwcmVmZXJlbmNlIGdvZXMgdG8g
dXNpbmcgdGhlIHZlcnNpb24gbnVtYmVyDQogICA+IGZpZWxkIG9mIHRoZSBsb25nIGhlYWRlciBm
b3IgbmVnb3RpYXRpbmcgdGhlIHByZXNlbmNlIG9mIHNwaW4gYml0cywgb3INCiAgID4gYW55IGFk
ZGl0aW9uYWwgc2lnbmFsIGJlaW5nIGV4cG9zZWQgdG8gdGhlIG5ldHdvcmsuDQogICA+DQogICA+
IEZvciBleGFtcGxlLCBRVUlDdjEgd2l0aG91dCBzcGluIGJpdCBjb3VsZCB1c2UgdmVyc2lvbiAw
eDEwMSwgYW5kIHYxDQogICA+IHdpdGggc3BpbiBiaXQgY291bGQgdXNlIDB4MTAyLiBJbiB0aGUg
ZnV0dXJlLCB3ZSBjYW4gYXNzaWduIGENCiAgID4gZGlmZmVyZW50IHZlcnNpb24gbnVtYmVyIGZv
ciBRVUlDdjEgd2l0aCBtdWx0aXBsZSBzcGluICsgVkVDIChvcg0KICAgPiBwZW9wbGUgaW50ZXJl
c3RlZCBpbiB0ZXN0aW5nIHRoZSBmZWF0dXJlIGNhbiBkZXNpZ25hdGUgYSBwcml2YXRlDQogICA+
IHZlcnNpb24gbnVtYmVyIGV2ZW4gYmVmb3JlIHRoYXQpLg0KICAgPg0KICAgPiBJIHNlZSB0aGUg
Zm9sbG93aW5nIGJlbmVmaXRzIHRvIHVzaW5nIHRoZSB2ZXJzaW9uIGZpZWxkIGFzIGEgbWV0aG9k
IHRvDQogICA+IG5lZ290aWF0ZSB0aGUgdXNlIG9mIHNwaW4gYml0cy4NCiAgID4NCiAgID4gMS4g
T25lIG9mIHRoZSBjb25jZXJuIHJlZ2FyZGluZyBzcGluIGJpdHMgaGFzIGJlZW4gdGhhdCB0aGV5
IGNvdWxkDQogICA+IGxlYWQgdG8gb3NzaWZpY2F0aW9uLiBTcGluIGJpdHMgYXJlIG5vdCBwYXJ0
IG9mIHRoZSBJbnZhcmlhbnRzLCBidXQgaWYNCiAgID4gdGhlIG9ic2VydmF0aW9uIHRvb2xzIHN0
YXJ0IGxvb2tpbmcgYXQgdGhvc2UgYml0cyB3aXRob3V0IGNoZWNraW5nIHRoZQ0KICAgPiB2ZXJz
aW9uIG51bWJlciBmaWVsZCwgd2Ugd2lsbCBoYXZlIHRoZSBwcmVzc3VyZSB0byBub3QgY2hhbmdl
IGhvdyB0aGUNCiAgID4gYml0cyBhcmUgdXNlZC4gVXNpbmcgdGhlIHZlcnNpb24gbnVtYmVyIHRv
IGluZGljYXRlIHRoZSBwcmVzZW5jZSBvZg0KICAgPiBzcGluIGJpdHMgaXMgdGhlIGJlc3QgYXBw
cm9hY2ggdG8gcmVzb2x2ZSBzdWNoIGNvbmNlcm4uDQogICA+DQogICA+IDIuIFdlIGhhdmUgaG9w
ZWQgdG8gcm9sbCBvdXQgbXVsdGlwbGUgdmVyc2lvbnMgb2YgUVVJQyBpbiBhIHNtYWxsDQogICA+
IGludGVydmFsIHNvIHRoYXQgdGhlIHZlcnNpb24gbnVtYmVyIGZpZWxkIGRvZXMgbm90IGdldCBv
c3NpZmllZC4gVGhlDQogICA+IGJlc3Qgc29sdXRpb24gaXMgb2J2aW91c2x5IHRvIHJvbGwgb3V0
IHR3byBmbGF2b3JzIG9mIHRoZSBwcm90b2NvbA0KICAgPiB0aGF0IHVzZXMgZGlmZmVyZW50IHZl
cnNpb24gbnVtYmVycyBhdCB0aGUgc2FtZSB0aW1lLiBXZSB3aWxsIGhhdmUgYQ0KICAgPiByZWFs
LXdvcmxkIHVzZSBvZiB2ZXJzaW9uIG5lZ290aWF0aW9uIGZyb20gZGF5IG9uZSwgYmVjYXVzZSB3
ZSBhcmUgaW4NCiAgID4gYSBjb25kaXRpb24gd2hlcmUgaW1wbGVtZW50b3JzIGhhdmUgZGlmZmVy
ZW50IG9waW5pb25zIG9uIGlmIHRoZXkNCiAgID4gc2hvdWxkIHN1cHBvcnQgc3BpbiBiaXQgOi0p
DQogICA+DQogICA+IFRoZSBibG9ja2VyIHRvIHRoaXMgYXBwcm9hY2ggaGFzIGJlZW4gdmVyc2lv
biBuZWdvdGlhdGlvbiByZXF1aXJpbmcgYW4NCiAgID4gYWRkaXRpb25hbCByb3VuZC10cmlwLCBi
dXQgdGhhdCBpcyBnb2luZyB0byBiZSByZXNvbHZlZCBieSAjMTc1NS4NCiAgID4NCiAgID4gMjAx
OOW5tDEw5pyIM+aXpSjmsLQpIDE5OjA2IDxhbGV4YW5kcmUuZmVycmlldXhAb3JhbmdlLmNvbTxt
YWlsdG86YWxleGFuZHJlLmZlcnJpZXV4QG9yYW5nZS5jb20+PjoNCiAgID4+DQogICA+PiBPbiAx
MC8wMy8xOCAwOTo1OCwgQnJpYW4gVHJhbW1lbGwgKElFVEYpIHdyb3RlOg0KICAgPj4gPiBCYWNr
aW5nIG9mZiB0aGUgTVVTVCBmb3Igbm93IGZvciBzdWNoIHNpdHVhdGlvbnMgaXMgSU1PIGEgZ29v
ZA0KICAgPj4gPiB0cmFkZW9mZiwgdGhvdWdoLCBlc3BlY2lhbGx5IHNpbmNlIHdlIG9ubHkgbmVl
ZCBmcmFjdGlvbnMgb2YgYQ0KICAgPj4gPiBwZXJjZW50IG9mIGRlcGxveW1lbnQgdG8gc3RhcnQg
c2VlaW5nIHVzZWZ1bCBzaWduYWwgZm9yDQogICA+PiA+IGJhc2VsaW5lL2Fub21hbHkgbWVhc3Vy
ZW1lbnQgb2YgbGFyZ2UgYWdncmVnYXRlcy4NCiAgID4+DQogICA+PiBJZiB0aGUgY29uc2Vuc3Vz
IGlzIHRoYXQgd2UgbXVzdCBhbGxvdyBmb3Igc3VjaCBzaXR1YXRpb25zLCB0aGVuDQogICA+PiB0
aGVyZSBhcmUgdHdvDQogICA+PiBwb3NzaWJpbGl0aWVzOg0KICAgPj4NCiAgID4+ICAgKGEpIHdl
YWsgc3BlYyBsYW5ndWFnZSAoTUFZIFdJU0ggVE8gb3Igc2ltaWxhcikgPT4gbWFueQ0KICAgPj4g
aW1wbGVtZW50YXRpb25zIHdpbGwgc2ltcGx5IGRyb3AgaXQNCiAgID4+DQogICA+PiAgIChiKSBu
ZWdvdGlhdGVkIG9wdGlvbiB3aGVyZSB0aGUgbmVnb3RpYXRpb24gbWVjaGFuaXNtIGlzIG1hbmRh
dG9yeQ0KICAgPj4NCiAgID4+IEluIHRoZSB2ZWluIG9mIChiKSwgQ2hyaXN0aWFuIHN1Z2dlc3Rl
ZCBvZmZsaW5lIHRvIGludHJvZHVjZQ0KICAgPj4gbmVnb3RpYXRpb24gdG8gYWxsb3cgZm9yIGV4
cGVyaW1lbnRhdGlvbiBvZiB0aGUgcmVtYWluaW5nIHR3bw0KICAgPj4gcmVzZXJ2ZWQgYml0cy4g
VGhlbiBtYXkgYmUgd2UgY2FuIHN5bnRoZXNpemUgYm90aCBpZGVhcyBieSB0aGUgZm9sbG93aW5n
IHByb3Bvc2FsOg0KICAgPj4NCiAgID4+ICAgLSBpbiB0aGUgZmlyc3QgZmV3IGV4Y2hhbmdlcyBv
ZiB0aGUgNS10dXBsZSwgdXNlIHRoZSB0aHJlZSBiaXRzIGZvcg0KICAgPj4gb3B0aW9uIG5lZ290
aWF0aW9uDQogICA+Pg0KICAgPj4gICAtIHRoZW4gdXNlIHRoZW0gYXMgZGVmaW5lZCBieSB0aGUg
c2VsZWN0ZWQgb3B0aW9uDQogICA+Pg0KICAgPj4gRXhhbXBsZSBlbmNvZGluZ3M6DQogICA+Pg0K
ICAgPj4gICAwMDAgOiBub3RoaW5nDQogICA+PiAgIDAwMSA6IHNwaW4gYml0IGFsb25lIDogUzAw
DQogICA+PiAgIDAxMCA6IHNwaW4gYml0ICsgVkVDIDogU1ZWDQogICA+PiAgIC4uLiA6IG90aGVy
IGV4dGVuc2lvbnMNCiAgID4+DQogICA+PiBUaGUgbmVnb3RpYXRpb24gbWVjaGFuaXNtIGFsbG93
cyBib3RoIGVuZHBvaW50cyB0byBmb3JjZSAwMDAuDQogICA+PiBBbmQgc2luY2UgaXQgaXMgaW4g
dGhlIGNsZWFyIGZpcnN0IGJ5dGUsIGl0IGFsbG93cyBvbi1wYXRoIG9ic2VydmVycw0KICAgPj4g
dG8gaWRlbnRpZnkgdGhlIG9wdGlvbiB3aXRob3V0IHJlc29ydGluZyB0byBoZXVyaXN0aWNzOyB0
aGlzIGhlbHBzIGluDQogICA+PiB0aGUgY2FzZSBvZiBhIHNtYWxsIHN1cHBvcnQgcmF0aW8uDQog
ICA+Pg0KICAgPj4NCiAgID4+DQogICA+Pg0KICAgPj4gX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQogICA+PiBfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQogICA+Pg0K
ICAgPj4gQ2UgbWVzc2FnZSBldCBzZXMgcGllY2VzIGpvaW50ZXMgcGV1dmVudCBjb250ZW5pciBk
ZXMgaW5mb3JtYXRpb25zDQogICA+PiBjb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVzIGV0
IG5lIGRvaXZlbnQgZG9uYyBwYXMgZXRyZSBkaWZmdXNlcywNCiAgID4+IGV4cGxvaXRlcyBvdSBj
b3BpZXMgc2FucyBhdXRvcmlzYXRpb24uIFNpIHZvdXMgYXZleiByZWN1IGNlIG1lc3NhZ2UNCiAg
ID4+IHBhciBlcnJldXIsIHZldWlsbGV6IGxlIHNpZ25hbGVyIGEgbCdleHBlZGl0ZXVyIGV0IGxl
IGRldHJ1aXJlIGFpbnNpIHF1ZSBsZXMgcGllY2VzIGpvaW50ZXMuIExlcyBtZXNzYWdlcyBlbGVj
dHJvbmlxdWVzIGV0YW50IHN1c2NlcHRpYmxlcyBkJ2FsdGVyYXRpb24sIE9yYW5nZSBkZWNsaW5l
IHRvdXRlIHJlc3BvbnNhYmlsaXRlIHNpIGNlIG1lc3NhZ2UgYSBldGUgYWx0ZXJlLCBkZWZvcm1l
IG91IGZhbHNpZmllLiBNZXJjaS4NCiAgID4+DQogICA+PiBUaGlzIG1lc3NhZ2UgYW5kIGl0cyBh
dHRhY2htZW50cyBtYXkgY29udGFpbiBjb25maWRlbnRpYWwgb3INCiAgID4+IHByaXZpbGVnZWQg
aW5mb3JtYXRpb24gdGhhdCBtYXkgYmUgcHJvdGVjdGVkIGJ5IGxhdzsgdGhleSBzaG91bGQgbm90
IGJlIGRpc3RyaWJ1dGVkLCB1c2VkIG9yIGNvcGllZCB3aXRob3V0IGF1dGhvcmlzYXRpb24uDQog
ICA+PiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVhc2Ugbm90
aWZ5IHRoZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50
cy4NCiAgID4+IEFzIGVtYWlscyBtYXkgYmUgYWx0ZXJlZCwgT3JhbmdlIGlzIG5vdCBsaWFibGUg
Zm9yIG1lc3NhZ2VzIHRoYXQgaGF2ZSBiZWVuIG1vZGlmaWVkLCBjaGFuZ2VkIG9yIGZhbHNpZmll
ZC4NCiAgID4+IFRoYW5rIHlvdS4NCiAgID4+DQogICA+DQogICA+DQoNCg0KDQogICBfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQoNCiAgIENlIG1lc3NhZ2UgZXQgc2VzIHBpZWNlcyBqb2ludGVzIHBldXZlbnQgY29udGVuaXIg
ZGVzIGluZm9ybWF0aW9ucyBjb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVzIGV0IG5lIGRv
aXZlbnQgZG9uYyBwYXMgZXRyZSBkaWZmdXNlcywgZXhwbG9pdGVzIG91IGNvcGllcyBzYW5zIGF1
dG9yaXNhdGlvbi4gU2kgdm91cyBhdmV6IHJlY3UgY2UgbWVzc2FnZSBwYXIgZXJyZXVyLCB2ZXVp
bGxleiBsZSBzaWduYWxlciBhIGwnZXhwZWRpdGV1ciBldCBsZSBkZXRydWlyZSBhaW5zaSBxdWUg
bGVzIHBpZWNlcyBqb2ludGVzLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25pcXVlcyBldGFudCBzdXNj
ZXB0aWJsZXMgZCdhbHRlcmF0aW9uLCBPcmFuZ2UgZGVjbGluZSB0b3V0ZSByZXNwb25zYWJpbGl0
ZSBzaSBjZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBmYWxzaWZpZS4gTWVyY2ku
DQoNCiAgIFRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRzIG1heSBjb250YWluIGNvbmZp
ZGVudGlhbCBvciBwcml2aWxlZ2VkIGluZm9ybWF0aW9uIHRoYXQgbWF5IGJlIHByb3RlY3RlZCBi
eSBsYXc7IHRoZXkgc2hvdWxkIG5vdCBiZSBkaXN0cmlidXRlZCwgdXNlZCBvciBjb3BpZWQgd2l0
aG91dCBhdXRob3Jpc2F0aW9uLg0KICAgSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBp
biBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBtZXNzYWdl
IGFuZCBpdHMgYXR0YWNobWVudHMuDQogICBBcyBlbWFpbHMgbWF5IGJlIGFsdGVyZWQsIE9yYW5n
ZSBpcyBub3QgbGlhYmxlIGZvciBtZXNzYWdlcyB0aGF0IGhhdmUgYmVlbiBtb2RpZmllZCwgY2hh
bmdlZCBvciBmYWxzaWZpZWQuDQogICBUaGFuayB5b3UuDQoNCg==

--_000_HE1PR0701MB23938FB7C6C13902AC04B637E2EB0HE1PR0701MB2393_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Ik1TIEdvdGhpYyI7DQoJcGFub3NlLTE6MiAxMSA2IDkgNyAyIDUgOCAyIDQ7fQ0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQE1TIEdv
dGhpYyI7DQoJcGFub3NlLTE6MiAxMSA2IDkgNyAyIDUgOCAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5p
dGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFy
Z2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJs
aW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3Jh
dGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJ
e21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9u
OnVuZGVybGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWww
DQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsN
CgltYXJnaW4tcmlnaHQ6MGNtOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdp
bi1sZWZ0OjBjbTsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFs
LXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRv
d3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6
RU4tVVM7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1h
cmdpbjo3MC44NXB0IDcwLjg1cHQgNzAuODVwdCA3MC44NXB0O30NCmRpdi5Xb3JkU2VjdGlvbjEN
Cgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHht
bD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3ht
bD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6
ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBl
bGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iU1YiIGxpbms9
ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6RU4tVVMiPkkgc2VlIHlvdXIgcG9pbnQsIGJ1dCBJIGRvbsK0dCBiZWxpZXZlIGl0IGlz
IGEgcGFydGljdWxhcmx5IHJlYWxpc3RpYyBzY2VuYXJpby4NCjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0ibXNvLWZh
cmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkl0IGlzIGluIHRoZSBpbnRlcmVzdCBvZiB0aGUgbmV0d29y
ayBvcGVyYXRvcnMgdG8gZW5zdXJlIHRoYXQgdGhlaXIgc3Vic2NyaWJlcnMgaGFzIGFzIGdvb2Qg
YW5kIGNvbnNpc3RlbnQgZXhwZXJpZW5jZS4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6RU4tVVMiPkJsYWNraG9saW5nIHZlcnNpb25zIG9mIFFVSUMgaGFzIHRoZSBwb3RlbnRp
YWwgb2YgY29tcGxldGVseSBkaXNydXB0aW5nIHNlcnZpY2VzIGFuZCBpbnRyb2R1Y2UgaW5jb25z
aXN0ZW50IGJlaGF2aW9yLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1V
UyI+VGhlIHNwaW5iaXQgaXMgaW50ZW5kZWQgYXMgYSB0b29sIHRvIGFzc2lzdCB0cm91Ymxlc2hv
b3RpbmcgYW5kIHF1YWxpdHkgbW9uaXRvcmluZy4gRXhwbGljaXRseSBpbnRyb2R1Y2luZyBwb3Rl
bnRpYWxseSBwb29yIG5ldHdvcmsgZXhwZXJpZW5jZSB3aXRoIHRoZSBob3BlcyB0aGF0IHlvdXIg
dHJvdWJsZXNob290aW5nDQogLyBtb25pdG9yaW5nIGNhcGFiaWxpdGllcyBpbXByb3ZlcyBpcyBh
IHJlYWxseSBiYWQgaWRlYSwgZXZlbiBmb3IgdGhlIG1vc3QgY3luaWNhbCBuZXR3b3JrIG9wZXJh
dG9yLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0i
RU4tVVMiPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyI+IE1hcnRlbiBTZWVtYW5u
ICZsdDttYXJ0ZW5zZWVtYW5uQGdtYWlsLmNvbSZndDsNCjxicj4NCjxiPlNlbnQ6PC9iPiBkZW4g
NSBva3RvYmVyIDIwMTggMTI6MzM8YnI+DQo8Yj5Ubzo8L2I+IE1hcmN1cyBJaGxhciAmbHQ7bWFy
Y3VzLmlobGFyQGVyaWNzc29uLmNvbSZndDs8YnI+DQo8Yj5DYzo8L2I+IGFsZXhhbmRyZS5mZXJy
aWV1eEBvcmFuZ2UuY29tOyBodWl0ZW1hQGh1aXRlbWEubmV0OyBpZXRmQHRyYW1tZWxsLmNoOyBr
YXp1aG9va3VAZ21haWwuY29tOyBtYmlzaG9wQGV2ZXF1ZWZvdS5iZTsgcXVpY0BpZXRmLm9yZzxi
cj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogU3BpbiBiaXQgYXMgYSBuZWdvdGlhdGVkIG9wdGlvbjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGUgcHJvYmxlbSB3
aXRoIHVzaW5nIGEgc3BlY2lmaWMgdmVyc2lvbiBmb3IgaW1wbGVtZW50YXRpb25zIHRoYXQgdXNl
IGFuZCBkb27igJl0IHVzZSB0aGUgc3BpbiBiaXQgaXMgdGhhdCBtaWRkbGVib3hlcyBjYW4gZWZm
ZWN0aXZlbHkgZW5mb3JjZSB1c2FnZSBvZiB0aGUgc3BpbiBiaXQgdmVyc2lvbiBieSBibGFja2hv
bGluZyBldmVyeSBwYWNrZXQgYWR2ZXJ0aXNpbmcgYSB2ZXJzaW9uIHRoYXQgZG9lc27igJl0IHVz
ZQ0KIHRoZSBzcGluIGJpdC4gSWYgb25seSBhIGZldyBtaWRkbGVib3hlcyBkbyB0aGF0LCB0aGlz
IHdvdWxkIGZvcmNlICphbGwqIGltcGxlbWVudGF0aW9ucyB0byBhdm9pZCB0aGVzZSB2ZXJzaW9u
cy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+SW1wbGVtZW50YXRpb25zIHRoYXQgZG9u4oCZdCB3YW50IHRvIGV4cG9zZSB0aGVpciBS
VFQgd291bGQgdGhlbiBoYXZlIHRvIG5lZ290aWF0ZSBhIHZlcnNpb24gdGhhdCBpcyBzdXBwb3Nl
ZCB0byB1c2UgdGhlIHNwaW4gYml0LCBidXQgdGhlbiBncmVhc2UgdGhlIGNvcnJlc3BvbmRpbmcg
Yml0cyBpbiBvcmRlciB0byBwcmVzZXJ2ZSB0aGVpciBwcml2YWN5LiBPZiBjb3Vyc2UsIHRoaXMg
d291bGQgb25seSB3b3JrDQogaWYgdGhlIHBlZXIgZG9lc27igJl0IGVuZm9yY2UgY29tcGxpYW5j
ZS4gT3RoZXJ3aXNlLCB3ZeKAmWxsIGVuZCB1cCBpbiBhIHdvcmxkIHdoZXJlIGl04oCZcyBiYXNp
Y2FsbHkgaW1wb3NzaWJsZSB0byBvcHQtb3V0IG9mIHRoZSBzcGluLWJpdC48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBGcmksIE9jdCA1LCAy
MDE4IGF0IDEyOjE1IE1hcmN1cyBJaGxhciAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1hcmN1cy5paGxh
ckBlcmljc3Nvbi5jb20iPm1hcmN1cy5paGxhckBlcmljc3Nvbi5jb208L2E+Jmd0OyB3cm90ZTo8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDtt
YXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+SGksPGJyPg0KSSBsaWtlIHRoaXMgYXBwcm9h
Y2ggc2luY2UgaXQgYWxsb3dzIHVzIHRvIGRpc3JlZ2FyZCBub24tc3Bpbm5pbmcgZmxvd3MgYnkg
c2ltcGx5IG9ic2VydmluZyB0aGUgaW5pdGlhbCBoYW5kc2hha2UuIFRoaXMgc2F2ZXMgdXMgcXVp
dGUgc29tZSB3b3JrLg0KPGJyPg0KT24gdGhlIGhldXJpc3RpY3MgcGFydCwgd2UgY2Fubm90IGdl
dCBhd2F5IGZyb20gaXQsIGV2ZW4gaWYgd2Ugc2VlIHRoZSBzcGluIHZlcnNpb24gaW4gdGhlIGlu
aXRpYWwgaGFuZHNoYWtlIGFzIHRoZXJlwrRzIG5vIGd1YXJhbnRlZSB0aGF0IGFuIGVuZHBvaW50
IHdpbGwgc2V0IHRoZSBiaXQgcHJvcGVybHkgYW55d2F5Ljxicj4NCkhvd2V2ZXIsIGZvciB0aGUg
dmVyc2lvbiB3aGVyZSB0aGUgaW50ZW50IHRvIHVzZSBzcGluYml0IGlzIGV4cGxpY2l0IGl0IGFj
dHVhbGx5IG1ha2VzIHNlbnNlIGZvciBhbiBlbmRwb2ludCB0byB0cmVhdCBub24tcGFydGljaXBh
dGluZyBiZWhhdmlvciBhcyBhIHByb3RvY29sIGVycm9yLjxicj4NCjxicj4NCk1hcmN1czxicj4N
Cjxicj4NCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJyPg0KRnJvbTogUVVJQyAmbHQ7PGEg
aHJlZj0ibWFpbHRvOnF1aWMtYm91bmNlc0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnF1aWMt
Ym91bmNlc0BpZXRmLm9yZzwvYT4mZ3Q7IE9uIEJlaGFsZiBPZiBNaWtlIEJpc2hvcDxicj4NClNl
bnQ6IGRlbiA1IG9rdG9iZXIgMjAxOCAwMDo0MDxicj4NClRvOiA8YSBocmVmPSJtYWlsdG86YWxl
eGFuZHJlLmZlcnJpZXV4QG9yYW5nZS5jb20iIHRhcmdldD0iX2JsYW5rIj5hbGV4YW5kcmUuZmVy
cmlldXhAb3JhbmdlLmNvbTwvYT47IEthenVobyBPa3UgJmx0OzxhIGhyZWY9Im1haWx0bzprYXp1
aG9va3VAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+a2F6dWhvb2t1QGdtYWlsLmNvbTwvYT4m
Z3Q7PGJyPg0KQ2M6IEJyaWFuIFRyYW1tZWxsICZsdDs8YSBocmVmPSJtYWlsdG86aWV0ZkB0cmFt
bWVsbC5jaCIgdGFyZ2V0PSJfYmxhbmsiPmlldGZAdHJhbW1lbGwuY2g8L2E+Jmd0OzsgSUVURiBR
VUlDIFdHICZsdDs8YSBocmVmPSJtYWlsdG86cXVpY0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsi
PnF1aWNAaWV0Zi5vcmc8L2E+Jmd0OzsgQ2hyaXN0aWFuIEh1aXRlbWEgJmx0OzxhIGhyZWY9Im1h
aWx0bzpodWl0ZW1hQGh1aXRlbWEubmV0IiB0YXJnZXQ9Il9ibGFuayI+aHVpdGVtYUBodWl0ZW1h
Lm5ldDwvYT4mZ3Q7PGJyPg0KU3ViamVjdDogUkU6IFNwaW4gYml0IGFzIGEgbmVnb3RpYXRlZCBv
cHRpb248YnI+DQo8YnI+DQpTbyBsb25nIGFzIHRoaXMgaXMgdGhlIG9ubHkgdGhpbmcgYmVpbmcg
bmVnb3RpYXRlZCwgaXQncyBub3QgdG9vIGJhZC4mbmJzcDsgSWYgd2Ugd2FudCB0byBuZWdvdGlh
dGUgb3RoZXIgdGhpbmdzLCBpdCBxdWlja2x5IGdldHMgb3V0IG9mIGhhbmQuJm5ic3A7IE9uZSBj
b3VsZCBwbGF1c2libHkgYXJndWUgdGhhdCB0aGUgc3BpbiBiaXQgaXMgc3BlY2lhbCBpbiB0aGF0
IHdlIGFjdHVhbGx5IHdhbnQgcGFydGllcyBvYnNlcnZpbmcgdGhlIHRyYW5zYWN0aW9uIHRvIHVu
ZGVyc3RhbmQNCiB3aGljaCBvcHRpb24gaGFzIGJlZW4gc2VsZWN0ZWQuPGJyPg0KPGJyPg0KSXQn
cyBpbXBvcnRhbnQgdG8gcmVtZW1iZXIsIHRob3VnaCwgdGhhdCB0aGlzIGlzIGluZm9ybWF0aW9u
IHlvdSBnZXQgb25seSBhdCB0aGUgYmVnaW5uaW5nIG9mIGEgbmV3IGNvbm5lY3Rpb24uJm5ic3A7
IElmIHRoZXJlJ3MgbWlncmF0aW9uIG9yIE5BVCByZWJpbmRpbmcsIGl0J3Mgbm90IGd1YXJhbnRl
ZWQgKGFuZCBpbiBmYWN0LCBub3QgaW50ZW5kZWQpIHRoYW4geW91IGNhbiBjb3JyZWxhdGUgaXQg
YmFjayB0byBhIHBhcnRpY3VsYXIgcHJldmlvdXMgaGFuZHNoYWtlLiZuYnNwOw0KIFlvdSdsbCBz
dGlsbCBlaXRoZXIgbmVlZCBoZXVyaXN0aWNzIHRvIGlkZW50aWZ5IHdoZXRoZXIgdGhlIHNwaW4g
Yml0IGlzIGFjdHVhbGx5IGluIHVzZSwgb3IgeW91J2xsIG5lZWQgdG8gaWdub3JlIGFueSB0cmFm
ZmljIGZvciB3aGljaCB5b3UgZGlkbid0IHNlZSB0aGUgaGFuZHNoYWtlLjxicj4NCjxicj4NCi0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJyPg0KRnJvbTogUVVJQyAmbHQ7PGEgaHJlZj0ibWFp
bHRvOnF1aWMtYm91bmNlc0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnF1aWMtYm91bmNlc0Bp
ZXRmLm9yZzwvYT4mZ3Q7IE9uIEJlaGFsZiBPZg0KPGEgaHJlZj0ibWFpbHRvOmFsZXhhbmRyZS5m
ZXJyaWV1eEBvcmFuZ2UuY29tIiB0YXJnZXQ9Il9ibGFuayI+YWxleGFuZHJlLmZlcnJpZXV4QG9y
YW5nZS5jb208L2E+PGJyPg0KU2VudDogVGh1cnNkYXksIE9jdG9iZXIgNCwgMjAxOCAzOjQ3IEFN
PGJyPg0KVG86IEthenVobyBPa3UgJmx0OzxhIGhyZWY9Im1haWx0bzprYXp1aG9va3VAZ21haWwu
Y29tIiB0YXJnZXQ9Il9ibGFuayI+a2F6dWhvb2t1QGdtYWlsLmNvbTwvYT4mZ3Q7PGJyPg0KQ2M6
IEJyaWFuIFRyYW1tZWxsICZsdDs8YSBocmVmPSJtYWlsdG86aWV0ZkB0cmFtbWVsbC5jaCIgdGFy
Z2V0PSJfYmxhbmsiPmlldGZAdHJhbW1lbGwuY2g8L2E+Jmd0OzsgSUVURiBRVUlDIFdHICZsdDs8
YSBocmVmPSJtYWlsdG86cXVpY0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnF1aWNAaWV0Zi5v
cmc8L2E+Jmd0OzsgQ2hyaXN0aWFuIEh1aXRlbWEgJmx0OzxhIGhyZWY9Im1haWx0bzpodWl0ZW1h
QGh1aXRlbWEubmV0IiB0YXJnZXQ9Il9ibGFuayI+aHVpdGVtYUBodWl0ZW1hLm5ldDwvYT4mZ3Q7
PGJyPg0KU3ViamVjdDogUmU6IFNwaW4gYml0IGFzIGEgbmVnb3RpYXRlZCBvcHRpb248YnI+DQo8
YnI+DQpUaGFua3MgS2F6dWhvLiBVc2luZyB2ZXJzaW9uIG51bWJlcnMgZGlyZWN0bHkgd2FzIGFu
IG9idmlvdXMgY2hvaWNlLCBidXQgc28gZmFyIEkgd2FzIGRpc2NvdXJhZ2VkIGJ5IHN0cm9uZyBs
YW5ndWFnZSBpbiB0aGUgc3BlYywgc2F5aW5nIDB4MDAwMDAwMDEgd2FzIHRoZSB1bmF2b2lkYWJs
ZSBwb2ludCBvZiBjb252ZXJnZW5jZSBhZnRlciBhbGwgMHhGRjAwMDBYWCBleHBlcmltZW50cy4g
U28gaW4gZXNzZW5jZSB5b3UncmUgcHJvcG9zaW5nIHRvDQogd2Vha2VuIHRoYXQgYSBiaXQsIHJp
Z2h0ID88YnI+DQo8YnI+DQpJZiBzbywgaG93IGRvIHlvdSBlbnZpc2lvbiBzZWdtZW50aW5nIHRo
ZSB2ZXJzaW9uIG51bWJlciBzcGFjZSA/PGJyPg0KPGJyPg0KJm5ic3A7IC0gZGlyZWN0IGVudW1l
cmF0aW9uOjxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAweDAwMDAwMDAx
ID0gdjFkcnk8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgMHgwMDAwMDAwMiA9IHYx
ICYjNDM7IHNwaW5iaXQ8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgMHgwMDAwMDAw
MyA9IHYxICYjNDM7IHNwaW5iaXQgJiM0MzsgVkVDPGJyPg0KPGJyPg0KJm5ic3A7IC0gbG93IG9y
ZGVyIGJpdHMgZm9yIG9wdGlvbnM6PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7IDB4MDAwMDAxWFggPSB2MSAmIzQzOyBvcHRpb24gWFg8YnI+DQombmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgMHgwMDAwMDJZWSA9IHYyICYjNDM7IG9wdGlvbiBZWTxicj4NCjxicj4NCkFs
c28sIGFyZSB3ZSBzdXJlIHRoYXQgdGhpcyBleHBsb3Npb24gd29uJ3Qgd2VpZ2ggb24gdGhlIG5l
dyBWTiBzY2hlbWUsIGluZHVjaW5nIHNsb3dlciBjb252ZXJnZW5jZSBkdWUgdG8gbG9uZ2VyIGxp
c3RzIG9uIGVpdGhlciBzaWRlID88YnI+DQo8YnI+DQpPbiAxMC8wNC8xOCAxMTo1MCwgS2F6dWhv
IE9rdSB3cm90ZTo8YnI+DQomZ3Q7IEhpLDxicj4NCiZndDsgPGJyPg0KJmd0OyBUaGFuayB5b3Ug
Zm9yIHN0YXJ0aW5nIHRoZSBkaXNjdXNzaW9uIHNwZWNpZmljIHRvIGhvdyB3ZSBjb3VsZCA8YnI+
DQomZ3Q7IHBvc3NpYmx5IG5lZ290aWF0ZSB0aGUgdXNlIG9mIHNwaW4gYml0cy48YnI+DQomZ3Q7
IDxicj4NCiZndDsgUmVnYXJkaW5nIHRoZSB0b3BpYywgbXkgcHJlZmVyZW5jZSBnb2VzIHRvIHVz
aW5nIHRoZSB2ZXJzaW9uIG51bWJlciA8YnI+DQomZ3Q7IGZpZWxkIG9mIHRoZSBsb25nIGhlYWRl
ciBmb3IgbmVnb3RpYXRpbmcgdGhlIHByZXNlbmNlIG9mIHNwaW4gYml0cywgb3IgPGJyPg0KJmd0
OyBhbnkgYWRkaXRpb25hbCBzaWduYWwgYmVpbmcgZXhwb3NlZCB0byB0aGUgbmV0d29yay48YnI+
DQomZ3Q7IDxicj4NCiZndDsgRm9yIGV4YW1wbGUsIFFVSUN2MSB3aXRob3V0IHNwaW4gYml0IGNv
dWxkIHVzZSB2ZXJzaW9uIDB4MTAxLCBhbmQgdjEgPGJyPg0KJmd0OyB3aXRoIHNwaW4gYml0IGNv
dWxkIHVzZSAweDEwMi4gSW4gdGhlIGZ1dHVyZSwgd2UgY2FuIGFzc2lnbiBhIDxicj4NCiZndDsg
ZGlmZmVyZW50IHZlcnNpb24gbnVtYmVyIGZvciBRVUlDdjEgd2l0aCBtdWx0aXBsZSBzcGluICYj
NDM7IFZFQyAob3IgPGJyPg0KJmd0OyBwZW9wbGUgaW50ZXJlc3RlZCBpbiB0ZXN0aW5nIHRoZSBm
ZWF0dXJlIGNhbiBkZXNpZ25hdGUgYSBwcml2YXRlIDxicj4NCiZndDsgdmVyc2lvbiBudW1iZXIg
ZXZlbiBiZWZvcmUgdGhhdCkuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IEkgc2VlIHRoZSBmb2xsb3dp
bmcgYmVuZWZpdHMgdG8gdXNpbmcgdGhlIHZlcnNpb24gZmllbGQgYXMgYSBtZXRob2QgdG8gPGJy
Pg0KJmd0OyBuZWdvdGlhdGUgdGhlIHVzZSBvZiBzcGluIGJpdHMuPGJyPg0KJmd0OyA8YnI+DQom
Z3Q7IDEuIE9uZSBvZiB0aGUgY29uY2VybiByZWdhcmRpbmcgc3BpbiBiaXRzIGhhcyBiZWVuIHRo
YXQgdGhleSBjb3VsZCA8YnI+DQomZ3Q7IGxlYWQgdG8gb3NzaWZpY2F0aW9uLiBTcGluIGJpdHMg
YXJlIG5vdCBwYXJ0IG9mIHRoZSBJbnZhcmlhbnRzLCBidXQgaWYgPGJyPg0KJmd0OyB0aGUgb2Jz
ZXJ2YXRpb24gdG9vbHMgc3RhcnQgbG9va2luZyBhdCB0aG9zZSBiaXRzIHdpdGhvdXQgY2hlY2tp
bmcgdGhlIDxicj4NCiZndDsgdmVyc2lvbiBudW1iZXIgZmllbGQsIHdlIHdpbGwgaGF2ZSB0aGUg
cHJlc3N1cmUgdG8gbm90IGNoYW5nZSBob3cgdGhlIDxicj4NCiZndDsgYml0cyBhcmUgdXNlZC4g
VXNpbmcgdGhlIHZlcnNpb24gbnVtYmVyIHRvIGluZGljYXRlIHRoZSBwcmVzZW5jZSBvZiA8YnI+
DQomZ3Q7IHNwaW4gYml0cyBpcyB0aGUgYmVzdCBhcHByb2FjaCB0byByZXNvbHZlIHN1Y2ggY29u
Y2Vybi48YnI+DQomZ3Q7IDxicj4NCiZndDsgMi4gV2UgaGF2ZSBob3BlZCB0byByb2xsIG91dCBt
dWx0aXBsZSB2ZXJzaW9ucyBvZiBRVUlDIGluIGEgc21hbGwgPGJyPg0KJmd0OyBpbnRlcnZhbCBz
byB0aGF0IHRoZSB2ZXJzaW9uIG51bWJlciBmaWVsZCBkb2VzIG5vdCBnZXQgb3NzaWZpZWQuIFRo
ZSA8YnI+DQomZ3Q7IGJlc3Qgc29sdXRpb24gaXMgb2J2aW91c2x5IHRvIHJvbGwgb3V0IHR3byBm
bGF2b3JzIG9mIHRoZSBwcm90b2NvbCA8YnI+DQomZ3Q7IHRoYXQgdXNlcyBkaWZmZXJlbnQgdmVy
c2lvbiBudW1iZXJzIGF0IHRoZSBzYW1lIHRpbWUuIFdlIHdpbGwgaGF2ZSBhIDxicj4NCiZndDsg
cmVhbC13b3JsZCB1c2Ugb2YgdmVyc2lvbiBuZWdvdGlhdGlvbiBmcm9tIGRheSBvbmUsIGJlY2F1
c2Ugd2UgYXJlIGluIDxicj4NCiZndDsgYSBjb25kaXRpb24gd2hlcmUgaW1wbGVtZW50b3JzIGhh
dmUgZGlmZmVyZW50IG9waW5pb25zIG9uIGlmIHRoZXkgPGJyPg0KJmd0OyBzaG91bGQgc3VwcG9y
dCBzcGluIGJpdCA6LSk8YnI+DQomZ3Q7IDxicj4NCiZndDsgVGhlIGJsb2NrZXIgdG8gdGhpcyBh
cHByb2FjaCBoYXMgYmVlbiB2ZXJzaW9uIG5lZ290aWF0aW9uIHJlcXVpcmluZyBhbiA8YnI+DQom
Z3Q7IGFkZGl0aW9uYWwgcm91bmQtdHJpcCwgYnV0IHRoYXQgaXMgZ29pbmcgdG8gYmUgcmVzb2x2
ZWQgYnkgIzE3NTUuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDIwMTg8c3BhbiBzdHlsZT0iZm9udC1m
YW1pbHk6JnF1b3Q7TVMgR290aGljJnF1b3Q7Ij7lubQ8L3NwYW4+MTA8c3BhbiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7TVMgR290aGljJnF1b3Q7Ij7mnIg8L3NwYW4+MzxzcGFuIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtNUyBHb3RoaWMmcXVvdDsiPuaXpTwvc3Bhbj4oPHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O01TIEdvdGhpYyZxdW90OyI+5rC0PC9zcGFuPikgMTk6MDYgJmx0
OzxhIGhyZWY9Im1haWx0bzphbGV4YW5kcmUuZmVycmlldXhAb3JhbmdlLmNvbSIgdGFyZ2V0PSJf
YmxhbmsiPmFsZXhhbmRyZS5mZXJyaWV1eEBvcmFuZ2UuY29tPC9hPiZndDs6PGJyPg0KJmd0OyZn
dDs8YnI+DQomZ3Q7Jmd0OyBPbiAxMC8wMy8xOCAwOTo1OCwgQnJpYW4gVHJhbW1lbGwgKElFVEYp
IHdyb3RlOjxicj4NCiZndDsmZ3Q7ICZndDsgQmFja2luZyBvZmYgdGhlIE1VU1QgZm9yIG5vdyBm
b3Igc3VjaCBzaXR1YXRpb25zIGlzIElNTyBhIGdvb2QgPGJyPg0KJmd0OyZndDsgJmd0OyB0cmFk
ZW9mZiwgdGhvdWdoLCBlc3BlY2lhbGx5IHNpbmNlIHdlIG9ubHkgbmVlZCBmcmFjdGlvbnMgb2Yg
YSA8YnI+DQomZ3Q7Jmd0OyAmZ3Q7IHBlcmNlbnQgb2YgZGVwbG95bWVudCB0byBzdGFydCBzZWVp
bmcgdXNlZnVsIHNpZ25hbCBmb3IgPGJyPg0KJmd0OyZndDsgJmd0OyBiYXNlbGluZS9hbm9tYWx5
IG1lYXN1cmVtZW50IG9mIGxhcmdlIGFnZ3JlZ2F0ZXMuPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7
Jmd0OyBJZiB0aGUgY29uc2Vuc3VzIGlzIHRoYXQgd2UgbXVzdCBhbGxvdyBmb3Igc3VjaCBzaXR1
YXRpb25zLCB0aGVuIDxicj4NCiZndDsmZ3Q7IHRoZXJlIGFyZSB0d288YnI+DQomZ3Q7Jmd0OyBw
b3NzaWJpbGl0aWVzOjxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmbmJzcDsgJm5ic3A7KGEp
IHdlYWsgc3BlYyBsYW5ndWFnZSAoTUFZIFdJU0ggVE8gb3Igc2ltaWxhcikgPSZndDsgbWFueSA8
YnI+DQomZ3Q7Jmd0OyBpbXBsZW1lbnRhdGlvbnMgd2lsbCBzaW1wbHkgZHJvcCBpdDxicj4NCiZn
dDsmZ3Q7PGJyPg0KJmd0OyZndDsmbmJzcDsgJm5ic3A7KGIpIG5lZ290aWF0ZWQgb3B0aW9uIHdo
ZXJlIHRoZSBuZWdvdGlhdGlvbiBtZWNoYW5pc20gaXMgbWFuZGF0b3J5PGJyPg0KJmd0OyZndDs8
YnI+DQomZ3Q7Jmd0OyBJbiB0aGUgdmVpbiBvZiAoYiksIENocmlzdGlhbiBzdWdnZXN0ZWQgb2Zm
bGluZSB0byBpbnRyb2R1Y2UgPGJyPg0KJmd0OyZndDsgbmVnb3RpYXRpb24gdG8gYWxsb3cgZm9y
IGV4cGVyaW1lbnRhdGlvbiBvZiB0aGUgcmVtYWluaW5nIHR3byA8YnI+DQomZ3Q7Jmd0OyByZXNl
cnZlZCBiaXRzLiBUaGVuIG1heSBiZSB3ZSBjYW4gc3ludGhlc2l6ZSBib3RoIGlkZWFzIGJ5IHRo
ZSBmb2xsb3dpbmcgcHJvcG9zYWw6PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZuYnNwOyAm
bmJzcDstIGluIHRoZSBmaXJzdCBmZXcgZXhjaGFuZ2VzIG9mIHRoZSA1LXR1cGxlLCB1c2UgdGhl
IHRocmVlIGJpdHMgZm9yIDxicj4NCiZndDsmZ3Q7IG9wdGlvbiBuZWdvdGlhdGlvbjxicj4NCiZn
dDsmZ3Q7PGJyPg0KJmd0OyZndDsmbmJzcDsgJm5ic3A7LSB0aGVuIHVzZSB0aGVtIGFzIGRlZmlu
ZWQgYnkgdGhlIHNlbGVjdGVkIG9wdGlvbjxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDsgRXhh
bXBsZSBlbmNvZGluZ3M6PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZuYnNwOyAmbmJzcDsw
MDAgOiBub3RoaW5nPGJyPg0KJmd0OyZndDsmbmJzcDsgJm5ic3A7MDAxIDogc3BpbiBiaXQgYWxv
bmUgOiBTMDA8YnI+DQomZ3Q7Jmd0OyZuYnNwOyAmbmJzcDswMTAgOiBzcGluIGJpdCAmIzQzOyBW
RUMgOiBTVlY8YnI+DQomZ3Q7Jmd0OyZuYnNwOyAmbmJzcDsuLi4gOiBvdGhlciBleHRlbnNpb25z
PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyBUaGUgbmVnb3RpYXRpb24gbWVjaGFuaXNtIGFs
bG93cyBib3RoIGVuZHBvaW50cyB0byBmb3JjZSAwMDAuPGJyPg0KJmd0OyZndDsgQW5kIHNpbmNl
IGl0IGlzIGluIHRoZSBjbGVhciBmaXJzdCBieXRlLCBpdCBhbGxvd3Mgb24tcGF0aCBvYnNlcnZl
cnMgPGJyPg0KJmd0OyZndDsgdG8gaWRlbnRpZnkgdGhlIG9wdGlvbiB3aXRob3V0IHJlc29ydGlu
ZyB0byBoZXVyaXN0aWNzOyB0aGlzIGhlbHBzIGluIDxicj4NCiZndDsmZ3Q7IHRoZSBjYXNlIG9m
IGEgc21hbGwgc3VwcG9ydCByYXRpby48YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7PGJyPg0K
Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7IF9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCiZn
dDsmZ3Q7IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X188YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7IENlIG1lc3NhZ2UgZXQgc2VzIHBpZWNlcyBq
b2ludGVzIHBldXZlbnQgY29udGVuaXIgZGVzIGluZm9ybWF0aW9ucyA8YnI+DQomZ3Q7Jmd0OyBj
b25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVzIGV0IG5lIGRvaXZlbnQgZG9uYyBwYXMgZXRy
ZSBkaWZmdXNlcywgPGJyPg0KJmd0OyZndDsgZXhwbG9pdGVzIG91IGNvcGllcyBzYW5zIGF1dG9y
aXNhdGlvbi4gU2kgdm91cyBhdmV6IHJlY3UgY2UgbWVzc2FnZSA8YnI+DQomZ3Q7Jmd0OyBwYXIg
ZXJyZXVyLCB2ZXVpbGxleiBsZSBzaWduYWxlciBhIGwnZXhwZWRpdGV1ciBldCBsZSBkZXRydWly
ZSBhaW5zaSBxdWUgbGVzIHBpZWNlcyBqb2ludGVzLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25pcXVl
cyBldGFudCBzdXNjZXB0aWJsZXMgZCdhbHRlcmF0aW9uLCBPcmFuZ2UgZGVjbGluZSB0b3V0ZSBy
ZXNwb25zYWJpbGl0ZSBzaSBjZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBmYWxz
aWZpZS4gTWVyY2kuPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyBUaGlzIG1lc3NhZ2UgYW5k
IGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBjb25maWRlbnRpYWwgb3IgPGJyPg0KJmd0OyZn
dDsgcHJpdmlsZWdlZCBpbmZvcm1hdGlvbiB0aGF0IG1heSBiZSBwcm90ZWN0ZWQgYnkgbGF3OyB0
aGV5IHNob3VsZCBub3QgYmUgZGlzdHJpYnV0ZWQsIHVzZWQgb3IgY29waWVkIHdpdGhvdXQgYXV0
aG9yaXNhdGlvbi48YnI+DQomZ3Q7Jmd0OyBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWls
IGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIG1lc3Nh
Z2UgYW5kIGl0cyBhdHRhY2htZW50cy48YnI+DQomZ3Q7Jmd0OyBBcyBlbWFpbHMgbWF5IGJlIGFs
dGVyZWQsIE9yYW5nZSBpcyBub3QgbGlhYmxlIGZvciBtZXNzYWdlcyB0aGF0IGhhdmUgYmVlbiBt
b2RpZmllZCwgY2hhbmdlZCBvciBmYWxzaWZpZWQuPGJyPg0KJmd0OyZndDsgVGhhbmsgeW91Ljxi
cj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxicj4NCjxicj4NCjxicj4NCjxicj4N
Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX188YnI+DQo8YnI+DQpDZSBtZXNzYWdlIGV0IHNlcyBwaWVjZXMgam9pbnRlcyBwZXV2
ZW50IGNvbnRlbmlyIGRlcyBpbmZvcm1hdGlvbnMgY29uZmlkZW50aWVsbGVzIG91IHByaXZpbGVn
aWVlcyBldCBuZSBkb2l2ZW50IGRvbmMgcGFzIGV0cmUgZGlmZnVzZXMsIGV4cGxvaXRlcyBvdSBj
b3BpZXMgc2FucyBhdXRvcmlzYXRpb24uIFNpIHZvdXMgYXZleiByZWN1IGNlIG1lc3NhZ2UgcGFy
IGVycmV1ciwgdmV1aWxsZXogbGUgc2lnbmFsZXIgYSBsJ2V4cGVkaXRldXIgZXQgbGUNCiBkZXRy
dWlyZSBhaW5zaSBxdWUgbGVzIHBpZWNlcyBqb2ludGVzLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25p
cXVlcyBldGFudCBzdXNjZXB0aWJsZXMgZCdhbHRlcmF0aW9uLCBPcmFuZ2UgZGVjbGluZSB0b3V0
ZSByZXNwb25zYWJpbGl0ZSBzaSBjZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBm
YWxzaWZpZS4gTWVyY2kuPGJyPg0KPGJyPg0KVGhpcyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVu
dHMgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIG9yIHByaXZpbGVnZWQgaW5mb3JtYXRpb24gdGhh
dCBtYXkgYmUgcHJvdGVjdGVkIGJ5IGxhdzsgdGhleSBzaG91bGQgbm90IGJlIGRpc3RyaWJ1dGVk
LCB1c2VkIG9yIGNvcGllZCB3aXRob3V0IGF1dGhvcmlzYXRpb24uPGJyPg0KSWYgeW91IGhhdmUg
cmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGFu
ZCBkZWxldGUgdGhpcyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVudHMuPGJyPg0KQXMgZW1haWxz
IG1heSBiZSBhbHRlcmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhhdCBo
YXZlIGJlZW4gbW9kaWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVkLjxicj4NClRoYW5rIHlvdS48
bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
Ym9keT4NCjwvaHRtbD4NCg==

--_000_HE1PR0701MB23938FB7C6C13902AC04B637E2EB0HE1PR0701MB2393_--


From nobody Fri Oct  5 05:23:02 2018
Return-Path: <ietf@trammell.ch>
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 08164130EF4 for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 05:22:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 o2SQOnAjoppG for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 05:22:49 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [212.25.24.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D535F130EB9 for <quic@ietf.org>; Fri,  5 Oct 2018 05:22:48 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 366D5341C21; Fri,  5 Oct 2018 14:22:47 +0200 (CEST)
X-Iway-Path: 0
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/14501.17478); Fri,  5 Oct 2018 14:22:46 +0200 (CEST)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Fri,  5 Oct 2018 14:22:46 +0200 (CEST)
Received: from [195.176.110.242] (account ietf@trammell.ch HELO public-docking-etx-1035.ethz.ch) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 69468058; Fri, 05 Oct 2018 14:22:46 +0200
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <EEF07499-6E93-46E5-A50A-D2690D670D3C@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_D3A572D7-1B88-4460-822F-701F0647E782"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: Spin bit as a negotiated option
Date: Fri, 5 Oct 2018 14:22:45 +0200
In-Reply-To: <HE1PR0701MB2393C0B9756449E5CC060723E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
Cc: "mbishop@evequefou.be" <mbishop@evequefou.be>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, "kazuhooku@gmail.com" <kazuhooku@gmail.com>, "quic@ietf.org" <quic@ietf.org>, "huitema@huitema.net" <huitema@huitema.net>
To: Marcus Ihlar <marcus.ihlar@ericsson.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com> <CY4PR22MB0983849F01312CBE18A4F69CDAEA0@CY4PR22MB0983.namprd22.prod.outlook.com> <HE1PR0701MB2393C0B9756449E5CC060723E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/im4MiB36_rOtlUZONxnnSNjEEiM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Oct 2018 12:23:01 -0000

--Apple-Mail=_D3A572D7-1B88-4460-822F-701F0647E782
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Kazuho, Marcus, all,

I am of two minds about this proposal.

I like it, because:

- it exercises the version negotiation machinery in a way beyond =
greasing, i.e. such that the negotiated information actually has an =
impact on the operation of the protocol. That is worth it for itself, =
spin bit or no.

-  it makes deploying and debugging the spin bit easier -- when =
negotiating the spin bit then not using it is a protocol error, then =
subtle errors in spin bit implementation don't require fully deployed =
heuristic measurement devices to detect.

- it is an explicit signal (both to the path and the other endpoint) =
about intent with respect to measurability. As Marcus notes, this makes =
it easier to reject flow state for non-spinning flows early, which eases =
measurement in the (likely) case that some smallish (1-10%) of flows in =
the Internet actually spin.


I'm less happy about the complexity implied:

- in any (non-VEC) implementation of a negotiated spin bit, the =
negotiation code will dwarf the code for the signal it's negotiating, =
which seems wrong.

- if we decide to support other client behaviors for other measurement =
goals in the future, it pushes the complexity of deciding what to =
measure to the endpoints, as opposed to placing that complexity at the =
midpoint.


I get that this seems like a good compromise for those who are queasy =
about the spin bit for whatever reason. But personally, I see this more =
as a good way to meaningfully exercise version control (IMO a hard =
requirement for V1) than as a good way to control the use of the spin =
bit.


Cheers,

Brian


> On 5 Oct 2018, at 12:15, Marcus Ihlar <marcus.ihlar@ericsson.com> =
wrote:
>=20
> Hi,
> I like this approach since it allows us to disregard non-spinning =
flows by simply observing the initial handshake. This saves us quite =
some work.
> On the heuristics part, we cannot get away from it, even if we see the =
spin version in the initial handshake as there=C2=B4s no guarantee that =
an endpoint will set the bit properly anyway.
> However, for the version where the intent to use spinbit is explicit =
it actually makes sense for an endpoint to treat non-participating =
behavior as a protocol error.
>=20
> Marcus
>=20
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of Mike Bishop
> Sent: den 5 oktober 2018 00:40
> To: alexandre.ferrieux@orange.com; Kazuho Oku <kazuhooku@gmail.com>
> Cc: Brian Trammell <ietf@trammell.ch>; IETF QUIC WG <quic@ietf.org>; =
Christian Huitema <huitema@huitema.net>
> Subject: RE: Spin bit as a negotiated option
>=20
> So long as this is the only thing being negotiated, it's not too bad.  =
If we want to negotiate other things, it quickly gets out of hand.  One =
could plausibly argue that the spin bit is special in that we actually =
want parties observing the transaction to understand which option has =
been selected.
>=20
> It's important to remember, though, that this is information you get =
only at the beginning of a new connection.  If there's migration or NAT =
rebinding, it's not guaranteed (and in fact, not intended) than you can =
correlate it back to a particular previous handshake.  You'll still =
either need heuristics to identify whether the spin bit is actually in =
use, or you'll need to ignore any traffic for which you didn't see the =
handshake.
>=20
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of =
alexandre.ferrieux@orange.com
> Sent: Thursday, October 4, 2018 3:47 AM
> To: Kazuho Oku <kazuhooku@gmail.com>
> Cc: Brian Trammell <ietf@trammell.ch>; IETF QUIC WG <quic@ietf.org>; =
Christian Huitema <huitema@huitema.net>
> Subject: Re: Spin bit as a negotiated option
>=20
> Thanks Kazuho. Using version numbers directly was an obvious choice, =
but so far I was discouraged by strong language in the spec, saying =
0x00000001 was the unavoidable point of convergence after all 0xFF0000XX =
experiments. So in essence you're proposing to weaken that a bit, right =
?
>=20
> If so, how do you envision segmenting the version number space ?
>=20
>  - direct enumeration:
>=20
> 	0x00000001 =3D v1dry
> 	0x00000002 =3D v1 + spinbit
> 	0x00000003 =3D v1 + spinbit + VEC
>=20
>  - low order bits for options:
>=20
> 	0x000001XX =3D v1 + option XX
> 	0x000002YY =3D v2 + option YY
>=20
> Also, are we sure that this explosion won't weigh on the new VN =
scheme, inducing slower convergence due to longer lists on either side ?
>=20
> On 10/04/18 11:50, Kazuho Oku wrote:
>> Hi,
>>=20
>> Thank you for starting the discussion specific to how we could
>> possibly negotiate the use of spin bits.
>>=20
>> Regarding the topic, my preference goes to using the version number
>> field of the long header for negotiating the presence of spin bits, =
or
>> any additional signal being exposed to the network.
>>=20
>> For example, QUICv1 without spin bit could use version 0x101, and v1
>> with spin bit could use 0x102. In the future, we can assign a
>> different version number for QUICv1 with multiple spin + VEC (or
>> people interested in testing the feature can designate a private
>> version number even before that).
>>=20
>> I see the following benefits to using the version field as a method =
to
>> negotiate the use of spin bits.
>>=20
>> 1. One of the concern regarding spin bits has been that they could
>> lead to ossification. Spin bits are not part of the Invariants, but =
if
>> the observation tools start looking at those bits without checking =
the
>> version number field, we will have the pressure to not change how the
>> bits are used. Using the version number to indicate the presence of
>> spin bits is the best approach to resolve such concern.
>>=20
>> 2. We have hoped to roll out multiple versions of QUIC in a small
>> interval so that the version number field does not get ossified. The
>> best solution is obviously to roll out two flavors of the protocol
>> that uses different version numbers at the same time. We will have a
>> real-world use of version negotiation from day one, because we are in
>> a condition where implementors have different opinions on if they
>> should support spin bit :-)
>>=20
>> The blocker to this approach has been version negotiation requiring =
an
>> additional round-trip, but that is going to be resolved by #1755.
>>=20
>> 2018=E5=B9=B410=E6=9C=883=E6=97=A5(=E6=B0=B4) 19:06 =
<alexandre.ferrieux@orange.com>:
>>>=20
>>> On 10/03/18 09:58, Brian Trammell (IETF) wrote:
>>>> Backing off the MUST for now for such situations is IMO a good
>>>> tradeoff, though, especially since we only need fractions of a
>>>> percent of deployment to start seeing useful signal for
>>>> baseline/anomaly measurement of large aggregates.
>>>=20
>>> If the consensus is that we must allow for such situations, then
>>> there are two
>>> possibilities:
>>>=20
>>>  (a) weak spec language (MAY WISH TO or similar) =3D> many
>>> implementations will simply drop it
>>>=20
>>>  (b) negotiated option where the negotiation mechanism is mandatory
>>>=20
>>> In the vein of (b), Christian suggested offline to introduce
>>> negotiation to allow for experimentation of the remaining two
>>> reserved bits. Then may be we can synthesize both ideas by the =
following proposal:
>>>=20
>>>  - in the first few exchanges of the 5-tuple, use the three bits for
>>> option negotiation
>>>=20
>>>  - then use them as defined by the selected option
>>>=20
>>> Example encodings:
>>>=20
>>>  000 : nothing
>>>  001 : spin bit alone : S00
>>>  010 : spin bit + VEC : SVV
>>>  ... : other extensions
>>>=20
>>> The negotiation mechanism allows both endpoints to force 000.
>>> And since it is in the clear first byte, it allows on-path observers
>>> to identify the option without resorting to heuristics; this helps =
in
>>> the case of a small support ratio.
>>>=20
>>>=20
>>>=20
>>>=20
>>> =
_____________________________________________________________________
>>> ____________________________________________________
>>>=20
>>> 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.
>>>=20
>>> 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.
>>>=20
>>=20
>>=20
>=20
>=20
>=20
> =
__________________________________________________________________________=
_______________________________________________
>=20
> 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.
>=20
> 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.
>=20


--Apple-Mail=_D3A572D7-1B88-4460-822F-701F0647E782
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAlu3V5UACgkQihK3vwvq
RqNmgxAApSDTPZne+fBh5KEUGatQsxa5I5d9VSEoIc7T78FLRUn5piQr/HR4hzYu
47/LqXTb/B64LThxH4Bobbdzc9tQiJUnybQKC+fKzMVR5RQpEm+aWZ/YKlsJXlBC
FZU5XVWB9h3LEUCMhe6QYkqjEBBPxyQ9k5iXDF9mZyR2qsVKOSil9Fj2VCn4jHY8
PvTDVcEHS0Ffy/dB0FDCd6nHUSTrsCuNrZjbWK5l9OYlAlbomrpjToNW9IJQMWDs
Us96+K4H7AZNYSxWcrE8aEYel6ZWVBwOuOonaSgP2IfzWurXVJcUtCacJv//IU2x
a6CfrQd0PcjPyXyr/Cfa+QcbHEWKzpcMTGsb031sn99k1bYaSZemexZlGJzOS1j5
k1r6HElPZQOeYBwVHhRyzvQ+ULnZBzDAublJdVRd+zjpV+L0DGPpF8ASSQafxkJ3
znI0TFzLrpjfMeZ+Pwz/7YnpOqHddtxg/vGAys2wd0IefMOAqtSx+Sp6UIIxLn2n
BqzrnnVUJFTmpQNvInUmSx1t+Bgiw6mpFjXVPWm25aRoKBkTkA8aWAYUjY9sQVUg
eCKdy6yCzdcM27Mmc/m2Z0cWP2ij9SzbRg3rGsFvpk+qjpObtXjJzZGiEMm/ITfx
wY5PBe0vxIC7mP96U5rhGk1r4oMcUnPLxnrLwJWG0SeBFOlf+Vw=
=mRHG
-----END PGP SIGNATURE-----

--Apple-Mail=_D3A572D7-1B88-4460-822F-701F0647E782--


From nobody Fri Oct  5 05:27:20 2018
Return-Path: <ietf@trammell.ch>
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 64020130E42 for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 05:27:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 1Sx28IhMnfTV for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 05:27:15 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [212.25.24.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CB33130E10 for <quic@ietf.org>; Fri,  5 Oct 2018 05:27:15 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id C7A1B341F41; Fri,  5 Oct 2018 14:27:13 +0200 (CEST)
X-Iway-Path: 0
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/14501.17746); Fri,  5 Oct 2018 14:27:13 +0200 (CEST)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Fri,  5 Oct 2018 14:27:13 +0200 (CEST)
Received: from [195.176.110.242] (account ietf@trammell.ch HELO public-docking-etx-1035.ethz.ch) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 69468556; Fri, 05 Oct 2018 14:27:13 +0200
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <E764EA78-B1B1-472F-A5CC-F3507873D6EE@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_D53C6164-6EC4-4D45-B303-0DCEA910A178"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: Spin bit as a negotiated option
Date: Fri, 5 Oct 2018 14:27:12 +0200
In-Reply-To: <HE1PR0701MB23938FB7C6C13902AC04B637E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
Cc: "martenseemann@gmail.com" <martenseemann@gmail.com>, "huitema@huitema.net" <huitema@huitema.net>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, "mbishop@evequefou.be" <mbishop@evequefou.be>, "quic@ietf.org" <quic@ietf.org>, "kazuhooku@gmail.com" <kazuhooku@gmail.com>
To: Marcus Ihlar <marcus.ihlar@ericsson.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com> <CY4PR22MB0983849F01312CBE18A4F69CDAEA0@CY4PR22MB0983.namprd22.prod.outlook.com> <HE1PR0701MB2393C0B9756449E5CC060723E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <CAOYVs2oyQO6kC3tMA3Cw7zzzDjiJca4yWRXqaK1ZH3_sbxWWtQ@mail.gmail.com> <HE1PR0701MB23938FB7C6C13902AC04B637E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/d3PPQNsRRbwyP-TsQPwQrxjvTek>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Oct 2018 12:27:18 -0000

--Apple-Mail=_D53C6164-6EC4-4D45-B303-0DCEA910A178
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 5 Oct 2018, at 12:56, Marcus Ihlar <marcus.ihlar@ericsson.com> =
wrote:
>=20
> I see your point, but I don=C2=B4t believe it is a particularly =
realistic scenario.
> It is in the interest of the network operators to ensure that their =
subscribers has as good and consistent experience.
> Blackholing versions of QUIC has the potential of completely =
disrupting services and introduce inconsistent behavior.
> The spinbit is intended as a tool to assist troubleshooting and =
quality monitoring. Explicitly introducing potentially poor network =
experience with the hopes that your troubleshooting / monitoring =
capabilities improves is a really bad idea, even for the most cynical =
network operator.

+ a whole lot to this. Treating middleboxes as a byzantine adversary is =
a useful thought experiment to determine the corner cases in a protocol, =
but I do not think we are well served by treating all arbitrary aims and =
capabilities on path as equally likely.

At the end of the day, every one of the middleboxes that we curse for =
their ossification was bought and sold because the operator deploying it =
believed it solved a problem they had, so analyzing the space of likely =
*intentional* behaviors reduces to an analysis of the business case for =
each of those behaviors.

I frankly don't see the business case for a spin-bit-blocking middlebox =
that wouldn't just block QUIC wholesale. But I'm not a middlebox vendor, =
so maybe I'm just missing something.

Now, there may be some *unintentional* breakage because some middlebox =
vendor only happens to analyze traffic that spins when trying to =
reverse-engineer QUIC, and decides that the non-spinning version is just =
grease and blocks it. But that seems to me to be more an argument to =
robustly exercise version negotiation from day one than anything else.

Cheers,

Brian

> From: Marten Seemann <martenseemann@gmail.com>
> Sent: den 5 oktober 2018 12:33
> To: Marcus Ihlar <marcus.ihlar@ericsson.com>
> Cc: alexandre.ferrieux@orange.com; huitema@huitema.net; =
ietf@trammell.ch; kazuhooku@gmail.com; mbishop@evequefou.be; =
quic@ietf.org
> Subject: Re: Spin bit as a negotiated option
>=20
> The problem with using a specific version for implementations that use =
and don=E2=80=99t use the spin bit is that middleboxes can effectively =
enforce usage of the spin bit version by blackholing every packet =
advertising a version that doesn=E2=80=99t use the spin bit. If only a =
few middleboxes do that, this would force *all* implementations to avoid =
these versions.
> Implementations that don=E2=80=99t want to expose their RTT would then =
have to negotiate a version that is supposed to use the spin bit, but =
then grease the corresponding bits in order to preserve their privacy. =
Of course, this would only work if the peer doesn=E2=80=99t enforce =
compliance. Otherwise, we=E2=80=99ll end up in a world where it=E2=80=99s =
basically impossible to opt-out of the spin-bit.
>=20
> On Fri, Oct 5, 2018 at 12:15 Marcus Ihlar <marcus.ihlar@ericsson.com> =
wrote:
> Hi,
> I like this approach since it allows us to disregard non-spinning =
flows by simply observing the initial handshake. This saves us quite =
some work.
> On the heuristics part, we cannot get away from it, even if we see the =
spin version in the initial handshake as there=C2=B4s no guarantee that =
an endpoint will set the bit properly anyway.
> However, for the version where the intent to use spinbit is explicit =
it actually makes sense for an endpoint to treat non-participating =
behavior as a protocol error.
>=20
> Marcus
>=20
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of Mike Bishop
> Sent: den 5 oktober 2018 00:40
> To: alexandre.ferrieux@orange.com; Kazuho Oku <kazuhooku@gmail.com>
> Cc: Brian Trammell <ietf@trammell.ch>; IETF QUIC WG <quic@ietf.org>; =
Christian Huitema <huitema@huitema.net>
> Subject: RE: Spin bit as a negotiated option
>=20
> So long as this is the only thing being negotiated, it's not too bad.  =
If we want to negotiate other things, it quickly gets out of hand.  One =
could plausibly argue that the spin bit is special in that we actually =
want parties observing the transaction to understand which option has =
been selected.
>=20
> It's important to remember, though, that this is information you get =
only at the beginning of a new connection.  If there's migration or NAT =
rebinding, it's not guaranteed (and in fact, not intended) than you can =
correlate it back to a particular previous handshake.  You'll still =
either need heuristics to identify whether the spin bit is actually in =
use, or you'll need to ignore any traffic for which you didn't see the =
handshake.
>=20
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of =
alexandre.ferrieux@orange.com
> Sent: Thursday, October 4, 2018 3:47 AM
> To: Kazuho Oku <kazuhooku@gmail.com>
> Cc: Brian Trammell <ietf@trammell.ch>; IETF QUIC WG <quic@ietf.org>; =
Christian Huitema <huitema@huitema.net>
> Subject: Re: Spin bit as a negotiated option
>=20
> Thanks Kazuho. Using version numbers directly was an obvious choice, =
but so far I was discouraged by strong language in the spec, saying =
0x00000001 was the unavoidable point of convergence after all 0xFF0000XX =
experiments. So in essence you're proposing to weaken that a bit, right =
?
>=20
> If so, how do you envision segmenting the version number space ?
>=20
>   - direct enumeration:
>=20
>         0x00000001 =3D v1dry
>         0x00000002 =3D v1 + spinbit
>         0x00000003 =3D v1 + spinbit + VEC
>=20
>   - low order bits for options:
>=20
>         0x000001XX =3D v1 + option XX
>         0x000002YY =3D v2 + option YY
>=20
> Also, are we sure that this explosion won't weigh on the new VN =
scheme, inducing slower convergence due to longer lists on either side ?
>=20
> On 10/04/18 11:50, Kazuho Oku wrote:
> > Hi,
> >
> > Thank you for starting the discussion specific to how we could
> > possibly negotiate the use of spin bits.
> >
> > Regarding the topic, my preference goes to using the version number
> > field of the long header for negotiating the presence of spin bits, =
or
> > any additional signal being exposed to the network.
> >
> > For example, QUICv1 without spin bit could use version 0x101, and v1
> > with spin bit could use 0x102. In the future, we can assign a
> > different version number for QUICv1 with multiple spin + VEC (or
> > people interested in testing the feature can designate a private
> > version number even before that).
> >
> > I see the following benefits to using the version field as a method =
to
> > negotiate the use of spin bits.
> >
> > 1. One of the concern regarding spin bits has been that they could
> > lead to ossification. Spin bits are not part of the Invariants, but =
if
> > the observation tools start looking at those bits without checking =
the
> > version number field, we will have the pressure to not change how =
the
> > bits are used. Using the version number to indicate the presence of
> > spin bits is the best approach to resolve such concern.
> >
> > 2. We have hoped to roll out multiple versions of QUIC in a small
> > interval so that the version number field does not get ossified. The
> > best solution is obviously to roll out two flavors of the protocol
> > that uses different version numbers at the same time. We will have a
> > real-world use of version negotiation from day one, because we are =
in
> > a condition where implementors have different opinions on if they
> > should support spin bit :-)
> >
> > The blocker to this approach has been version negotiation requiring =
an
> > additional round-trip, but that is going to be resolved by #1755.
> >
> > 2018=E5=B9=B410=E6=9C=883=E6=97=A5(=E6=B0=B4) 19:06 =
<alexandre.ferrieux@orange.com>:
> >>
> >> On 10/03/18 09:58, Brian Trammell (IETF) wrote:
> >> > Backing off the MUST for now for such situations is IMO a good
> >> > tradeoff, though, especially since we only need fractions of a
> >> > percent of deployment to start seeing useful signal for
> >> > baseline/anomaly measurement of large aggregates.
> >>
> >> If the consensus is that we must allow for such situations, then
> >> there are two
> >> possibilities:
> >>
> >>   (a) weak spec language (MAY WISH TO or similar) =3D> many
> >> implementations will simply drop it
> >>
> >>   (b) negotiated option where the negotiation mechanism is =
mandatory
> >>
> >> In the vein of (b), Christian suggested offline to introduce
> >> negotiation to allow for experimentation of the remaining two
> >> reserved bits. Then may be we can synthesize both ideas by the =
following proposal:
> >>
> >>   - in the first few exchanges of the 5-tuple, use the three bits =
for
> >> option negotiation
> >>
> >>   - then use them as defined by the selected option
> >>
> >> Example encodings:
> >>
> >>   000 : nothing
> >>   001 : spin bit alone : S00
> >>   010 : spin bit + VEC : SVV
> >>   ... : other extensions
> >>
> >> The negotiation mechanism allows both endpoints to force 000.
> >> And since it is in the clear first byte, it allows on-path =
observers
> >> to identify the option without resorting to heuristics; this helps =
in
> >> the case of a small support ratio.
> >>
> >>
> >>
> >>
> >> =
_____________________________________________________________________
> >> ____________________________________________________
> >>
> >> 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.
> >>
> >
> >
>=20
>=20
>=20
> =
__________________________________________________________________________=
_______________________________________________
>=20
> 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.
>=20
> 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.
>=20


--Apple-Mail=_D53C6164-6EC4-4D45-B303-0DCEA910A178
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAlu3WKAACgkQihK3vwvq
RqOs7hAAonsMSMiCSh2AB4d9+WalfbLgolt0rxMS7wMc++yVzVOahl5IKcLHrdn9
r26X7u8h7vT3f0dkNDQ51ZSEp7dT3O1ye+66cmUyfnI38s3s+aVL3N3yJ5yzErry
jhAEX7FmrRb4b+3KnemWPc9P6op5/ywZTpUBg7nXhTvIgmHr7G2L33ZcxxO6ZLe5
3NS1fNfhkWBMwo46kIEaTem03LCho7Y7U7CUxdPRYhPXGLqhcFggKfJ3+UP/MrCd
ZDNW9qrOmgj+7zPTYUIn9iAIYIxxgXloSp/RTOoU4VaTrVDd5QnK9brYq/1RJUUA
ycELGA8LccrF5T4vMoo/Q/kwsQqIfRAfGlFgUZiApmHQJJVG7K28LRLKmdakOEuG
zGOQaxPAyQsYUTHMJ3vhl1D4SRU6/4U5LzUdFAP1O2PC72vR1GiiqZuN69xpARB2
7Xwk6+s4pbqb7UfOkH/yZsFc/K0PeGrdAQCHsYy8bOZJG02E7+iwpN6wnMoDNgkx
lrAjugjB7aTaehw0j8q6xg050lKaq0aMvlIhQDJR8qAwz2VmVxP/vLlgRxSDUGS+
YvkC94UbCAIdOcs/iUyz5qAMR1nYoH3SIcJbj2epWKyWJaBaOLHRykYJYn5T+HQc
n1qvR9Kbzp6n8RuCeApLW3Y/99yUpxVYtnEovEr1qJaLNTmE4nk=
=9UAg
-----END PGP SIGNATURE-----

--Apple-Mail=_D53C6164-6EC4-4D45-B303-0DCEA910A178--


From nobody Fri Oct  5 05:32:21 2018
Return-Path: <alexandre.ferrieux@orange.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 DDB30130E43 for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 05:32:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.291
X-Spam-Level: 
X-Spam-Status: No, score=-0.291 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 lAREAcCjBC0G for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 05:32:17 -0700 (PDT)
Received: from orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74461130E10 for <quic@ietf.org>; Fri,  5 Oct 2018 05:32:17 -0700 (PDT)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) by opfednr27.francetelecom.fr (ESMTP service) with ESMTP id 42RTfS00FXz4wfT; Fri,  5 Oct 2018 14:32:16 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfednr02.francetelecom.fr (ESMTP service) with ESMTP id 42RTfR6M8Yz8sYR; Fri,  5 Oct 2018 14:32:15 +0200 (CEST)
Received: from [10.193.4.89] (10.168.234.4) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 5 Oct 2018 14:32:15 +0200
Subject: Re: Spin bit as a negotiated option
To: "Brian Trammell (IETF)" <ietf@trammell.ch>, Marcus Ihlar <marcus.ihlar@ericsson.com>
CC: "huitema@huitema.net" <huitema@huitema.net>, "quic@ietf.org" <quic@ietf.org>, "mbishop@evequefou.be" <mbishop@evequefou.be>, "kazuhooku@gmail.com" <kazuhooku@gmail.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com> <CY4PR22MB0983849F01312CBE18A4F69CDAEA0@CY4PR22MB0983.namprd22.prod.outlook.com> <HE1PR0701MB2393C0B9756449E5CC060723E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <EEF07499-6E93-46E5-A50A-D2690D670D3C@trammell.ch>
From: <alexandre.ferrieux@orange.com>
Organization: Orange
Message-ID: <15185_1538742735_5BB759CF_15185_399_1_d9cdb295-d68e-ee43-938e-e3a79003d731@orange.com>
Date: Fri, 5 Oct 2018 14:32:15 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <EEF07499-6E93-46E5-A50A-D2690D670D3C@trammell.ch>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.168.234.4]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7CWwdWIlokYVieAMgRtCk1wRXvo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Oct 2018 12:32:19 -0000

On 10/05/18 14:22, Brian Trammell (IETF) wrote:
> 
> I'm less happy about the complexity implied:
> 
> - in any (non-VEC) implementation of a negotiated spin bit, the negotiation
> code will dwarf the code for the signal it's negotiating, which seems wrong.

The version negotiation code is a one-shot investment for all extensions. Not a 
single extra line when the set moves from {v1,v1s} to {v1,v1s,v1svv,v1sqr?...}.

> - if we decide to support other client behaviors for other measurement goals
> in the future, it pushes the complexity of deciding what to measure to the
> endpoints, as opposed to placing that complexity at the midpoint.
The one thing that pushes the burden onto the endpoints is not negotiation but 
enforcement. I don't think enforcement is a good idea, for this very reason. 
Since these extensions are only for observers and may easily be opted out by 
either endpoint, it makes sense to honor them in a best-effort way, no more.

_________________________________________________________________________________________________________________________

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.


From nobody Fri Oct  5 06:43:38 2018
Return-Path: <kazuhooku@gmail.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 B88ED130DEB for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 06:43:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 f2eFPHNgBXgp for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 06:43:33 -0700 (PDT)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 5E978130DC6 for <quic@ietf.org>; Fri,  5 Oct 2018 06:43:33 -0700 (PDT)
Received: by mail-lj1-x22c.google.com with SMTP id j17-v6so2381718lja.1 for <quic@ietf.org>; Fri, 05 Oct 2018 06:43:33 -0700 (PDT)
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:content-transfer-encoding; bh=6o2TDENMe1Y9FzVL6VyWC4/oXZ+PP0VZf+kL20l9p8c=; b=edJdKlgwgQk62Lk3K1IAcpJvAez+YuEEZGZ2l0PfFDRFpiRku4zbvUKOxYM6XwdWI1 1VcqWGJEk7K7eDMTcblXivTkLdmRsB6HYhOFwnQGlCBif9TcWB9Qp9ukCwOuBYozm1VM 2u6aTB0BaiouYRfGQLGt5KHm0xDJkwxGadnw5RMFRPjxnzLp2auA6YEGLeHPZ05msMYy IlFEIiOzLGwf4XGfL1Ldq/UdGM8dqWse+z3PSanqORKEDSL0bFIvjxt60JwHResRDkWn felWmXRdM0KhDEG76fC0+2stwhDZeLXbPvPN1kcdlgaX4gFDwvv2eiQWs+g0uowINahj Fxnw==
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:content-transfer-encoding; bh=6o2TDENMe1Y9FzVL6VyWC4/oXZ+PP0VZf+kL20l9p8c=; b=jenKSyGq2nCSMgWTYzfDQV058c6WxmczRutfuwVbqd4RQilTnuCOUNcWcFgpftw7dx OIEc8WFNi/DHbFjlh+wnv+TiDu4TYHpZrlPIocsQdmnvPu/2cRfOjLJ/s966a6eZXZ+V G6xWE5dAt/ggEKSa3VhLtRLD8n6AMEjqbOamr8XodGgsj7JfZYQ5GpGoNX1GM67hR+Qj YKOJZJpcBtEmOYaDhnucS3Yq8yKbd4IR3LgcbbomJ+g0/jpKsGyIyGlrG/g5ELKjJerG r5FdSn7mfqSOuYHC/fB33sw2ZoT7zMbFHhl90PV0sE/dJ2PfX5V9L7+sLVH/GMHyQGwp tggQ==
X-Gm-Message-State: ABuFfojF3qMzgP296u69mOKECGqv4m/cdydQnfEYOKeZZgPJrpel2Mut QoZ9jzpYq1i/FcnPTMfn3gOKXc920HHSCu2ZMgA=
X-Google-Smtp-Source: ACcGV61aYWVft5/xYMKFM9bGGI3LTtFf+uk/N3hQbk2pgnqCHIdrkHNez7IIhMVRn7MLCjgP7ofvIA+TiZMt0kYIfh4=
X-Received: by 2002:a2e:3918:: with SMTP id g24-v6mr7235274lja.113.1538747011517;  Fri, 05 Oct 2018 06:43:31 -0700 (PDT)
MIME-Version: 1.0
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com> <CY4PR22MB0983849F01312CBE18A4F69CDAEA0@CY4PR22MB0983.namprd22.prod.outlook.com> <HE1PR0701MB2393C0B9756449E5CC060723E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <EEF07499-6E93-46E5-A50A-D2690D670D3C@trammell.ch> <15185_1538742735_5BB759CF_15185_399_1_d9cdb295-d68e-ee43-938e-e3a79003d731@orange.com>
In-Reply-To: <15185_1538742735_5BB759CF_15185_399_1_d9cdb295-d68e-ee43-938e-e3a79003d731@orange.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Fri, 5 Oct 2018 22:43:19 +0900
Message-ID: <CANatvzztOx72qACw9VWFW1S89Kgn6a+bMTH+qERd57aPXfbaLQ@mail.gmail.com>
Subject: Re: Spin bit as a negotiated option
To: Lili Peaudchien <alexandre.ferrieux@orange.com>
Cc: Brian Trammell <ietf@trammell.ch>, marcus.ihlar@ericsson.com,  Christian Huitema <huitema@huitema.net>, IETF QUIC WG <quic@ietf.org>, Mike Bishop <mbishop@evequefou.be>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/VVZfqpCSIjuYkkYVL-OHUbzpGo4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Oct 2018 13:43:36 -0000

2018=E5=B9=B410=E6=9C=885=E6=97=A5(=E9=87=91) 21:32 <alexandre.ferrieux@ora=
nge.com>:
>
> On 10/05/18 14:22, Brian Trammell (IETF) wrote:
> >
> > I'm less happy about the complexity implied:
> >
> > - in any (non-VEC) implementation of a negotiated spin bit, the negotia=
tion
> > code will dwarf the code for the signal it's negotiating, which seems w=
rong.
>
> The version negotiation code is a one-shot investment for all extensions.=
 Not a
> single extra line when the set moves from {v1,v1s} to {v1,v1s,v1svv,v1sqr=
?...}.

+1.

I would also argue that having explicit negotiation using the version
number field helps both the endpoints and the middleboxes, because it
ensures us of having the freedom to evolve.

Having one bit (or several bits) tied forever to the behavior we
define in v1 would be a loss for everybody.

> > - if we decide to support other client behaviors for other measurement =
goals
> > in the future, it pushes the complexity of deciding what to measure to =
the
> > endpoints, as opposed to placing that complexity at the midpoint.
> The one thing that pushes the burden onto the endpoints is not negotiatio=
n but
> enforcement. I don't think enforcement is a good idea, for this very reas=
on.
> Since these extensions are only for observers and may easily be opted out=
 by
> either endpoint, it makes sense to honor them in a best-effort way, no mo=
re.

I would also argue that the endpoints must be given the freedom to
choose the signals they would expose, because there could be privacy
implications based on how the endpoints are deployed.

FWIW, I am not opposed to the idea of middlebox suggesting a signal it
wants to see, possibly by injecting a long header packet into the
flow.

>
> _________________________________________________________________________=
________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confid=
entielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez re=
cu 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 o=
u falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged i=
nformation 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 de=
lete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have bee=
n modified, changed or falsified.
> Thank you.
>


--=20
Kazuho Oku


From nobody Fri Oct  5 07:00:53 2018
Return-Path: <kazuhooku@gmail.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 E5E86127B92 for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 07:00:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 TkpbW5dcvXjA for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 07:00:51 -0700 (PDT)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 5ABB112426A for <quic@ietf.org>; Fri,  5 Oct 2018 07:00:50 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id r83-v6so11714405ljr.7 for <quic@ietf.org>; Fri, 05 Oct 2018 07:00:50 -0700 (PDT)
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:content-transfer-encoding; bh=nVjGE41PnhlirKZaXDuFkPnJdYpoiNwTHqJzWkid/aE=; b=WVK4kjKr8vd0kDHIGcN6vc5IUR5FNf9wEw/4ukhmjXWyXCUhSElZ3LPp+Id8+SUyQI MWfyoJrUOShvqsFoHH8Ywmyg1y4cfuoDXFXOYp5p72os83I13XE5M4j093UZwcuxloLJ yRqXMYkoU2gEHFNElxyR/hTTJelWwNBEyE8uk4H7Rh7tF2Fr8LTlEMwCwKndA16AlKm7 1JBpRCyQ//jtn284oQazEiAQx7gPmrqoPtqAkncKHJL3rKEcoHsIhO1t1N+ZEDMY3mT/ T7IxgpDBIsrq+mPRz0L0F7NakQj+PwiEPyf4rfNJkkAotswkuQqo0PCWsZD42VbwY9bf iTgg==
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:content-transfer-encoding; bh=nVjGE41PnhlirKZaXDuFkPnJdYpoiNwTHqJzWkid/aE=; b=TANtK8TCnV1k1o3aRMUKz45F2GTUCaFfGmzZRHFDn3cuSLkN6oIfj5uHPsGC8DJ+pl 2/TgmqTqHtA+SQpTRmsZe5vvCj3R6pcXwnCUNjvNiUTJUpMkbkl2Yb35rWrR2i7i2bKU DukgLx9NzqGDWnwb0xvmAan+Joq5xJ/+PaPWFzpnr4k7vwqsr+F1z0gDf+YZ4YQyrpP5 5DQBuV3cZbVm9y4I3PA6B3HOlZQhT8KJfzHcDibjfasoAcXSJBDKe5HQX+9ARZ/G2/3j /TXK+4Kzz2JxNi/HYHP3XCThCThJXJxswWH+N9WHNiPcDQYIIO6fFXKghVqPQxyFPasI XjTg==
X-Gm-Message-State: ABuFfojyqDSGXOpPv80/RavPvMglXPt57UbVOno4YkLtohRtlEaxQjbj VfEB8l6S1wpTDT6PDvP3VxqqKvMeaJiPeFOud0A=
X-Google-Smtp-Source: ACcGV61XoTbcMjzUwXS41ZCPIMUIFQtz1gdhdgr5TdTThWeUzefoD1J3evKL5+yUqf8Y2SpTIHvkq7ue25+A/Z2mRoM=
X-Received: by 2002:a2e:9d50:: with SMTP id y16-v6mr7914948ljj.136.1538748048403;  Fri, 05 Oct 2018 07:00:48 -0700 (PDT)
MIME-Version: 1.0
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com> <CY4PR22MB0983849F01312CBE18A4F69CDAEA0@CY4PR22MB0983.namprd22.prod.outlook.com> <HE1PR0701MB2393C0B9756449E5CC060723E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <CAOYVs2oyQO6kC3tMA3Cw7zzzDjiJca4yWRXqaK1ZH3_sbxWWtQ@mail.gmail.com> <HE1PR0701MB23938FB7C6C13902AC04B637E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <E764EA78-B1B1-472F-A5CC-F3507873D6EE@trammell.ch>
In-Reply-To: <E764EA78-B1B1-472F-A5CC-F3507873D6EE@trammell.ch>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Fri, 5 Oct 2018 23:00:36 +0900
Message-ID: <CANatvzz4hiWZ+JkdgzzDT12R87MZ=vzfN=qoQcUGbU24dRCtTQ@mail.gmail.com>
Subject: Re: Spin bit as a negotiated option
To: Brian Trammell <ietf@trammell.ch>
Cc: marcus.ihlar@ericsson.com, Marten Seemann <martenseemann@gmail.com>,  Christian Huitema <huitema@huitema.net>, Lili Peaudchien <alexandre.ferrieux@orange.com>,  Mike Bishop <mbishop@evequefou.be>, IETF QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/xEIAuuASldo4ycoGrMYbfFtr3R4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Oct 2018 14:00:53 -0000

2018=E5=B9=B410=E6=9C=885=E6=97=A5(=E9=87=91) 21:27 Brian Trammell (IETF) <=
ietf@trammell.ch>:
>
>
>
> > On 5 Oct 2018, at 12:56, Marcus Ihlar <marcus.ihlar@ericsson.com> wrote=
:
> >
> > I see your point, but I don=C2=B4t believe it is a particularly realist=
ic scenario.
> > It is in the interest of the network operators to ensure that their sub=
scribers has as good and consistent experience.
> > Blackholing versions of QUIC has the potential of completely disrupting=
 services and introduce inconsistent behavior.
> > The spinbit is intended as a tool to assist troubleshooting and quality=
 monitoring. Explicitly introducing potentially poor network experience wit=
h the hopes that your troubleshooting / monitoring capabilities improves is=
 a really bad idea, even for the most cynical network operator.
>
> + a whole lot to this. Treating middleboxes as a byzantine adversary is a=
 useful thought experiment to determine the corner cases in a protocol, but=
 I do not think we are well served by treating all arbitrary aims and capab=
ilities on path as equally likely.
>
> At the end of the day, every one of the middleboxes that we curse for the=
ir ossification was bought and sold because the operator deploying it belie=
ved it solved a problem they had, so analyzing the space of likely *intenti=
onal* behaviors reduces to an analysis of the business case for each of tho=
se behaviors.
>
> I frankly don't see the business case for a spin-bit-blocking middlebox t=
hat wouldn't just block QUIC wholesale.

In addition to what Alexandre and Marcus have pointed out, I would
like to second what Brian has stated here.

There are business-related reasons to prefer TCP over QUIC. There are
middlebox vendors selling TCP traffic-shaping middleboxes that claim
to reduce the consumed bandwidth (by reducing the number of
retransmits, utilizing the information about the condition of the
mobile network). There are (still!) networks that give preferential
treatment to non-TLS HTTP because they can deploy transparent,
compressing proxies.

Compared to those cases, spin bit has very weak reason for
preferential treatment (i.e. troubleshooting and quality monitoring).

Besides, the endpoints would also have the choice to expose fake
signal once we start seeing networks blocking QUIC without the spin
bit. Actually, that is the status-quo, in which we do not have any
negotiation. To put it the other way, the endpoints lose nothing by
using the version number field for exposing the availability of the
signal.

> But I'm not a middlebox vendor, so maybe I'm just missing something.
>
> Now, there may be some *unintentional* breakage because some middlebox ve=
ndor only happens to analyze traffic that spins when trying to reverse-engi=
neer QUIC, and decides that the non-spinning version is just grease and blo=
cks it. But that seems to me to be more an argument to robustly exercise ve=
rsion negotiation from day one than anything else.
>
> Cheers,
>
> Brian
>
> > From: Marten Seemann <martenseemann@gmail.com>
> > Sent: den 5 oktober 2018 12:33
> > To: Marcus Ihlar <marcus.ihlar@ericsson.com>
> > Cc: alexandre.ferrieux@orange.com; huitema@huitema.net; ietf@trammell.c=
h; kazuhooku@gmail.com; mbishop@evequefou.be; quic@ietf.org
> > Subject: Re: Spin bit as a negotiated option
> >
> > The problem with using a specific version for implementations that use =
and don=E2=80=99t use the spin bit is that middleboxes can effectively enfo=
rce usage of the spin bit version by blackholing every packet advertising a=
 version that doesn=E2=80=99t use the spin bit. If only a few middleboxes d=
o that, this would force *all* implementations to avoid these versions.
> > Implementations that don=E2=80=99t want to expose their RTT would then =
have to negotiate a version that is supposed to use the spin bit, but then =
grease the corresponding bits in order to preserve their privacy. Of course=
, this would only work if the peer doesn=E2=80=99t enforce compliance. Othe=
rwise, we=E2=80=99ll end up in a world where it=E2=80=99s basically impossi=
ble to opt-out of the spin-bit.
> >
> > On Fri, Oct 5, 2018 at 12:15 Marcus Ihlar <marcus.ihlar@ericsson.com> w=
rote:
> > Hi,
> > I like this approach since it allows us to disregard non-spinning flows=
 by simply observing the initial handshake. This saves us quite some work.
> > On the heuristics part, we cannot get away from it, even if we see the =
spin version in the initial handshake as there=C2=B4s no guarantee that an =
endpoint will set the bit properly anyway.
> > However, for the version where the intent to use spinbit is explicit it=
 actually makes sense for an endpoint to treat non-participating behavior a=
s a protocol error.
> >
> > Marcus
> >
> > -----Original Message-----
> > From: QUIC <quic-bounces@ietf.org> On Behalf Of Mike Bishop
> > Sent: den 5 oktober 2018 00:40
> > To: alexandre.ferrieux@orange.com; Kazuho Oku <kazuhooku@gmail.com>
> > Cc: Brian Trammell <ietf@trammell.ch>; IETF QUIC WG <quic@ietf.org>; Ch=
ristian Huitema <huitema@huitema.net>
> > Subject: RE: Spin bit as a negotiated option
> >
> > So long as this is the only thing being negotiated, it's not too bad.  =
If we want to negotiate other things, it quickly gets out of hand.  One cou=
ld plausibly argue that the spin bit is special in that we actually want pa=
rties observing the transaction to understand which option has been selecte=
d.
> >
> > It's important to remember, though, that this is information you get on=
ly at the beginning of a new connection.  If there's migration or NAT rebin=
ding, it's not guaranteed (and in fact, not intended) than you can correlat=
e it back to a particular previous handshake.  You'll still either need heu=
ristics to identify whether the spin bit is actually in use, or you'll need=
 to ignore any traffic for which you didn't see the handshake.
> >
> > -----Original Message-----
> > From: QUIC <quic-bounces@ietf.org> On Behalf Of alexandre.ferrieux@oran=
ge.com
> > Sent: Thursday, October 4, 2018 3:47 AM
> > To: Kazuho Oku <kazuhooku@gmail.com>
> > Cc: Brian Trammell <ietf@trammell.ch>; IETF QUIC WG <quic@ietf.org>; Ch=
ristian Huitema <huitema@huitema.net>
> > Subject: Re: Spin bit as a negotiated option
> >
> > Thanks Kazuho. Using version numbers directly was an obvious choice, bu=
t so far I was discouraged by strong language in the spec, saying 0x0000000=
1 was the unavoidable point of convergence after all 0xFF0000XX experiments=
. So in essence you're proposing to weaken that a bit, right ?
> >
> > If so, how do you envision segmenting the version number space ?
> >
> >   - direct enumeration:
> >
> >         0x00000001 =3D v1dry
> >         0x00000002 =3D v1 + spinbit
> >         0x00000003 =3D v1 + spinbit + VEC
> >
> >   - low order bits for options:
> >
> >         0x000001XX =3D v1 + option XX
> >         0x000002YY =3D v2 + option YY
> >
> > Also, are we sure that this explosion won't weigh on the new VN scheme,=
 inducing slower convergence due to longer lists on either side ?
> >
> > On 10/04/18 11:50, Kazuho Oku wrote:
> > > Hi,
> > >
> > > Thank you for starting the discussion specific to how we could
> > > possibly negotiate the use of spin bits.
> > >
> > > Regarding the topic, my preference goes to using the version number
> > > field of the long header for negotiating the presence of spin bits, o=
r
> > > any additional signal being exposed to the network.
> > >
> > > For example, QUICv1 without spin bit could use version 0x101, and v1
> > > with spin bit could use 0x102. In the future, we can assign a
> > > different version number for QUICv1 with multiple spin + VEC (or
> > > people interested in testing the feature can designate a private
> > > version number even before that).
> > >
> > > I see the following benefits to using the version field as a method t=
o
> > > negotiate the use of spin bits.
> > >
> > > 1. One of the concern regarding spin bits has been that they could
> > > lead to ossification. Spin bits are not part of the Invariants, but i=
f
> > > the observation tools start looking at those bits without checking th=
e
> > > version number field, we will have the pressure to not change how the
> > > bits are used. Using the version number to indicate the presence of
> > > spin bits is the best approach to resolve such concern.
> > >
> > > 2. We have hoped to roll out multiple versions of QUIC in a small
> > > interval so that the version number field does not get ossified. The
> > > best solution is obviously to roll out two flavors of the protocol
> > > that uses different version numbers at the same time. We will have a
> > > real-world use of version negotiation from day one, because we are in
> > > a condition where implementors have different opinions on if they
> > > should support spin bit :-)
> > >
> > > The blocker to this approach has been version negotiation requiring a=
n
> > > additional round-trip, but that is going to be resolved by #1755.
> > >
> > > 2018=E5=B9=B410=E6=9C=883=E6=97=A5(=E6=B0=B4) 19:06 <alexandre.ferrie=
ux@orange.com>:
> > >>
> > >> On 10/03/18 09:58, Brian Trammell (IETF) wrote:
> > >> > Backing off the MUST for now for such situations is IMO a good
> > >> > tradeoff, though, especially since we only need fractions of a
> > >> > percent of deployment to start seeing useful signal for
> > >> > baseline/anomaly measurement of large aggregates.
> > >>
> > >> If the consensus is that we must allow for such situations, then
> > >> there are two
> > >> possibilities:
> > >>
> > >>   (a) weak spec language (MAY WISH TO or similar) =3D> many
> > >> implementations will simply drop it
> > >>
> > >>   (b) negotiated option where the negotiation mechanism is mandatory
> > >>
> > >> In the vein of (b), Christian suggested offline to introduce
> > >> negotiation to allow for experimentation of the remaining two
> > >> reserved bits. Then may be we can synthesize both ideas by the follo=
wing proposal:
> > >>
> > >>   - in the first few exchanges of the 5-tuple, use the three bits fo=
r
> > >> option negotiation
> > >>
> > >>   - then use them as defined by the selected option
> > >>
> > >> Example encodings:
> > >>
> > >>   000 : nothing
> > >>   001 : spin bit alone : S00
> > >>   010 : spin bit + VEC : SVV
> > >>   ... : other extensions
> > >>
> > >> The negotiation mechanism allows both endpoints to force 000.
> > >> And since it is in the clear first byte, it allows on-path observers
> > >> to identify the option without resorting to heuristics; this helps i=
n
> > >> the case of a small support ratio.
> > >>
> > >>
> > >>
> > >>
> > >> ____________________________________________________________________=
_
> > >> ____________________________________________________
> > >>
> > >> 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'al=
teration, Orange decline toute responsabilite si ce message a ete altere, d=
eforme 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 a=
nd delete this message and its attachments.
> > >> As emails may be altered, Orange is not liable for messages that hav=
e been modified, changed or falsified.
> > >> Thank you.
> > >>
> > >
> > >
> >
> >
> >
> > _______________________________________________________________________=
__________________________________________________
> >
> > Ce message et ses pieces jointes peuvent contenir des informations conf=
identielles ou privilegiees et ne doivent donc pas etre diffuses, exploites=
 ou copies sans autorisation. Si vous avez recu ce message par erreur, veui=
llez le signaler a l'expediteur et le detruire ainsi que les pieces jointes=
. Les messages electroniques etant susceptibles d'alteration, Orange declin=
e toute responsabilite si ce message a ete altere, deforme ou falsifie. Mer=
ci.
> >
> > 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 b=
een modified, changed or falsified.
> > Thank you.
> >
>


--=20
Kazuho Oku


From nobody Fri Oct  5 07:01:12 2018
Return-Path: <ietf@trammell.ch>
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 7B712127B92 for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 07:01:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 dkqkQx8V-27n for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 07:01:00 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [212.25.24.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3D56130E6C for <quic@ietf.org>; Fri,  5 Oct 2018 07:00:59 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 39F16341EDF; Fri,  5 Oct 2018 16:00:58 +0200 (CEST)
X-Iway-Path: 0
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/14501.24034); Fri,  5 Oct 2018 16:00:58 +0200 (CEST)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Fri,  5 Oct 2018 16:00:57 +0200 (CEST)
Received: from [195.176.111.3] (account ietf@trammell.ch HELO public-docking-cx-2490.ethz.ch) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 69480895; Fri, 05 Oct 2018 16:00:55 +0200
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <AF2ED1E9-B72C-4526-ADC7-77BD4C12D300@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_199E1994-D970-42CC-B871-61E8E7C24EA4"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: Spin bit as a negotiated option
Date: Fri, 5 Oct 2018 16:00:55 +0200
In-Reply-To: <CANatvzztOx72qACw9VWFW1S89Kgn6a+bMTH+qERd57aPXfbaLQ@mail.gmail.com>
Cc: Lili Peaudchien <alexandre.ferrieux@orange.com>, marcus.ihlar@ericsson.com, Christian Huitema <huitema@huitema.net>, IETF QUIC WG <quic@ietf.org>, Mike Bishop <mbishop@evequefou.be>
To: Kazuho Oku <kazuhooku@gmail.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com> <CY4PR22MB0983849F01312CBE18A4F69CDAEA0@CY4PR22MB0983.namprd22.prod.outlook.com> <HE1PR0701MB2393C0B9756449E5CC060723E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <EEF07499-6E93-46E5-A50A-D2690D670D3C@trammell.ch> <15185_1538742735_5BB759CF_15185_399_1_d9cdb295-d68e-ee43-938e-e3a79003d731@orange.com> <CANatvzztOx72qACw9VWFW1S89Kgn6a+bMTH+qERd57aPXfbaLQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/RTuMaRLy1kJXE72cErJwq1Y0wm0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Oct 2018 14:01:10 -0000

--Apple-Mail=_199E1994-D970-42CC-B871-61E8E7C24EA4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 5 Oct 2018, at 15:43, Kazuho Oku <kazuhooku@gmail.com> wrote:
>=20
> 2018=E5=B9=B410=E6=9C=885=E6=97=A5(=E9=87=91) 21:32 =
<alexandre.ferrieux@orange.com>:
>>=20
>> On 10/05/18 14:22, Brian Trammell (IETF) wrote:
>>>=20
>>> I'm less happy about the complexity implied:
>>>=20
>>> - in any (non-VEC) implementation of a negotiated spin bit, the =
negotiation
>>> code will dwarf the code for the signal it's negotiating, which =
seems wrong.
>>=20
>> The version negotiation code is a one-shot investment for all =
extensions. Not a
>> single extra line when the set moves from {v1,v1s} to =
{v1,v1s,v1svv,v1sqr?...}.
>=20
> +1.
>=20
> I would also argue that having explicit negotiation using the version
> number field helps both the endpoints and the middleboxes, because it
> ensures us of having the freedom to evolve.
>=20
> Having one bit (or several bits) tied forever to the behavior we
> define in v1 would be a loss for everybody.

Okay, I buy that argument. That probably tips me into the "let's do this =
with VN" camp.

Cheers,

Brian

>=20
>>> - if we decide to support other client behaviors for other =
measurement goals
>>> in the future, it pushes the complexity of deciding what to measure =
to the
>>> endpoints, as opposed to placing that complexity at the midpoint.
>> The one thing that pushes the burden onto the endpoints is not =
negotiation but
>> enforcement. I don't think enforcement is a good idea, for this very =
reason.
>> Since these extensions are only for observers and may easily be opted =
out by
>> either endpoint, it makes sense to honor them in a best-effort way, =
no more.
>=20
> I would also argue that the endpoints must be given the freedom to
> choose the signals they would expose, because there could be privacy
> implications based on how the endpoints are deployed.
>=20
> FWIW, I am not opposed to the idea of middlebox suggesting a signal it
> wants to see, possibly by injecting a long header packet into the
> flow.
>=20
>>=20
>> =
__________________________________________________________________________=
_______________________________________________
>>=20
>> 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.
>>=20
>> 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.
>>=20
>=20
>=20
> --
> Kazuho Oku


--Apple-Mail=_199E1994-D970-42CC-B871-61E8E7C24EA4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAlu3bpcACgkQihK3vwvq
RqMQuA//VSJmNC1JWV10hWocBQ2XCE2ea1XU12YCRC0TDK709JeU0hbqJas2h+BD
zC8Wr4QO/FIALtekerVeOoxlkc2FyI7EpcM5pIBSOPtj80T0adHgxpnzXuh7mPDu
4FyIeKStV3AOcwLMmx2YsNosZ9sBZAWrb3b6+fAIQZu4674YJ1i+Mco/AsroKmRK
wmUtEG29p+LlhvBdMTgoo8gKhhkxALVdLumDUJ7zZxXZZgsOq5QSODvcSMrDfxjv
+k7L64fKrlhhaP+Wkb0bCxz4SkHqJblsJ27GxYE/YoYQ4ANiCKe1+1qGqKEcW9Sr
iL8/98ezyZD1J6vow0642Rn+ryuQsCuxagzQLkKyeSyvmJ/UgwsF9UuK+N75Opp9
u6mV3X0PKOYRejJl+uwAv3Ujy29iO3pDc5qZ6LlxOrboCl4yU2JmvXpBFT6DbzQw
ec25IBBssm+o1ZpPcpO/tEewXHCo3hMvQ92XOdh7n3eyYw9LfL57FwME+3725Ap0
h1cimdlTHgYJ/L4yKBG4xYyH9veRGVgfXUh4IyM0C/pwHe3e/GNFZJZ6k4kyAfKt
PQdw4ktAayUCJekG8hpkl57ydeJzvUFjQj4YKlfi0Rlhu1nCa/7meQEQMMhJ/3Rg
kIoV8/VorkSDSMD3O2HrTfv0SHDfMLXFveO+Z/Cba1A9paSJuTw=
=XjvV
-----END PGP SIGNATURE-----

--Apple-Mail=_199E1994-D970-42CC-B871-61E8E7C24EA4--


From nobody Fri Oct  5 08:13:46 2018
Return-Path: <marcus.ihlar@ericsson.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 D76FF130E02 for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 08:13:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.755
X-Spam-Level: 
X-Spam-Status: No, score=-4.755 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=HEYZG8ah; dkim=pass (1024-bit key) header.d=ericsson.com header.b=Lnu8Tbcq
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 qJRuRsFlLwpR for <quic@ietfa.amsl.com>; Fri,  5 Oct 2018 08:13:41 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 D8D5F124BE5 for <quic@ietf.org>; Fri,  5 Oct 2018 08:13:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1538752419; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=T9+V/JpQrJDZfHmtou5A/gEdSfVKcCP1D7vgOk+R6Ag=; b=HEYZG8ahA+yB1AdXzeCscVB2KYNPaVIB3jCuS3Dx/THj+LirXZ5QodLly4nFWOLO 18a9cRiGnenMXqzBz6uQZrsIWmXuKb32EL57mCvZ3iE9+qGuBc5z1DA5Xn9U9Viq jllktMky+eP9gui3n9kaHiFQ60/cfmffHEZc/quRBLw=;
X-AuditID: c1b4fb30-3cd869c0000055da-8a-5bb77fa280f3
Received: from ESESSMB501.ericsson.se (Unknown_Domain [153.88.183.119]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id FE.EE.21978.2AF77BB5; Fri,  5 Oct 2018 17:13:38 +0200 (CEST)
Received: from ESESSMB502.ericsson.se (153.88.183.163) by ESESSMB501.ericsson.se (153.88.183.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 5 Oct 2018 17:12:21 +0200
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB502.ericsson.se (153.88.183.163) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Fri, 5 Oct 2018 17:12:21 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=T9+V/JpQrJDZfHmtou5A/gEdSfVKcCP1D7vgOk+R6Ag=; b=Lnu8TbcqbrHxLsN0NXVQrsdavEogyqEJQBwI/wgDen14bdea9zkp67Va90L+LvBKF64XYR6t+9wsiiG8hDd/9IvC9gCoqaBbubGCucnCzzuzvpsJkRvcjDZ4MDh/CsRoLeq1zXOywHQs1qQiWs/ZDscKcwLypkUfqGwCg2e7zBY=
Received: from HE1PR0701MB2393.eurprd07.prod.outlook.com (10.168.128.12) by HE1PR0701MB2124.eurprd07.prod.outlook.com (10.168.36.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1207.13; Fri, 5 Oct 2018 15:12:19 +0000
Received: from HE1PR0701MB2393.eurprd07.prod.outlook.com ([fe80::400d:3614:de33:b3a8]) by HE1PR0701MB2393.eurprd07.prod.outlook.com ([fe80::400d:3614:de33:b3a8%4]) with mapi id 15.20.1228.011; Fri, 5 Oct 2018 15:12:19 +0000
From: Marcus Ihlar <marcus.ihlar@ericsson.com>
To: Kazuho Oku <kazuhooku@gmail.com>, Brian Trammell <ietf@trammell.ch>
CC: IETF QUIC WG <quic@ietf.org>, Lili Peaudchien <alexandre.ferrieux@orange.com>, Mike Bishop <mbishop@evequefou.be>, "Marten Seemann" <martenseemann@gmail.com>, Christian Huitema <huitema@huitema.net>
Subject: SV: Spin bit as a negotiated option
Thread-Topic: Spin bit as a negotiated option
Thread-Index: AQHUWwDJ8lpz5mbOFU6DOhcb6dfH26UO2VEAgAAPtACAAMdZAIAAuUuAgAAN9oCAAAGHcIAAHlQAgAAaGACAAA0OPA==
Date: Fri, 5 Oct 2018 15:12:19 +0000
Message-ID: <HE1PR0701MB23937DEBD284002B65CAA3EEE2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <3E3DBC15-FE42-47CF-AF7A-1F2597ED2390@eggert.org> <24019_1538484216_5BB367F8_24019_26_1_8e6b0d8e-78f0-56c7-e731-da2ff22cb194@orange.com> <08A9C80F-59E6-46EE-A4D4-1F78F5085CF7@eggert.org> <9737_1538485723_5BB36DDB_9737_147_1_82e0e028-b0e8-5e09-7bd5-e66db97c556a@orange.com> <E7479831-9594-444E-9545-A162E8D9B154@eggert.org> <32072_1538492813_5BB3898D_32072_266_1_8380ff40-29fe-269b-8ed7-4331c9e53f4d@orange.com> <MWHPR22MB0991D93D706031603B077BFCDAE80@MWHPR22MB0991.namprd22.prod.outlook.com> <CAKcm_gM+zAEwfimHsorsWprJgS7O++85EOjpQoNY0LviaQ+KNQ@mail.gmail.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com> <CY4PR22MB0983849F01312CBE18A4F69CDAEA0@CY4PR22MB0983.namprd22.prod.outlook.com> <HE1PR0701MB2393C0B9756449E5CC060723E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <CAOYVs2oyQO6kC3tMA3Cw7zzzDjiJca4yWRXqaK1ZH3_sbxWWtQ@mail.gmail.com> <HE1PR0701MB23938FB7C6C13902AC04B637E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <E764EA78-B1B1-472F-A5CC-F3507873D6EE@trammell.ch>, <CANatvzz4hiWZ+JkdgzzDT12R87MZ=vzfN=qoQcUGbU24dRCtTQ@mail.gmail.com>
In-Reply-To: <CANatvzz4hiWZ+JkdgzzDT12R87MZ=vzfN=qoQcUGbU24dRCtTQ@mail.gmail.com>
Accept-Language: sv-SE, en-US
Content-Language: sv-SE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.176.1.88]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR0701MB2124; 6:il5l+4WvMKH9WqqIXktJk6211ElD4itHR6GXAuZCMpkUKroGk++m+gshKIQKJ/OJ1UKZ5uwN1xclgNbZJ9IAwwvb1Neq5Fyj+Tj/YykA//bDzLc5PdVAXu3tmihe5pqQuUjZnl2+Mvc7FFsXOKXLWZyMk0IeMOpbH23FZA9WOysuk9lowvteFpOneO42K8+wiqmDxB1zgBdQPxlY9msQTzLT+kgM6T0W2Nwsr3CKrxwAG14cl6Pl2/5ofMf8/ImYgCoKEnowjy6QZBH0rlaqzFsG+QmKcgRxYb17gjBx2OJ8o229DMDWBMXsP1GmmhRJMSagdcJVkGHaZrga4aT/WCr/DgtsERT1N+9sqXkJ8gOmYDWYSrbByKhGkZ/a1KgNaNVjVtRcqQJIvj7+RUDY3XzH9tgKyUWYxanF7qRharKtYBVrOtStREGfqcajnnPkQGgezVRYTC6FStf1ugb68g==; 5:gPo6qjfjKLaR2uw9GSYFNYQAn5ETiAch+1rs5iYXzeenK5uQp8+Px05JAARColldr7c5L+YVLE7kwPJisPd0iM05WtVfuvrGroSvGMgZbs+n+V7sdY4dCjo8jfsAPujU4aBZLdy7dkXl1usJHg/5ndVYDdpyI9Jz0W77wnaH03k=; 7:RzlSFr53w/qUlm17JAoe+iZTExmAlOGplzN+cuSgzSByHap7ZoC3dIrnp1EQrz3Ldcx/5otouT/pZdCKaBgIpitLpClLfAV1twbbuM8cSK2ottVPQW5fht/GnZNAEjPlEXYDDPTXP3j7wJXx0hPyEZNbIN7f6TyG6vvh7bqnyepXm9gB/eNP0s04CTuABoC70bJjfT3J5i1zN74VZgYJ34LWbAuHqWQSQvmJxtiKQodF/IP2vuiJy5gbkcJbI6S0
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 8647b279-0d52-4bbb-3874-08d62ad4f18b
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:HE1PR0701MB2124; 
x-ms-traffictypediagnostic: HE1PR0701MB2124:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=marcus.ihlar@ericsson.com; 
x-microsoft-antispam-prvs: <HE1PR0701MB21242594D4C270EE7F97FCE3E2EB0@HE1PR0701MB2124.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(85827821059158)(248295561703944)(37575265505322)(72170088055959)(161740460382875)(18271650672692)(100405760836317);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3231355)(944501410)(4982022)(52105095)(10201501046)(3002001)(93006095)(93001095)(149066)(150057)(6041310)(20161123562045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(201708071742011)(7699051)(76991048); SRVR:HE1PR0701MB2124; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0701MB2124; 
x-forefront-prvs: 0816F1D86E
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(136003)(376002)(346002)(366004)(39860400002)(13464003)(189003)(199004)(256004)(14444005)(6606003)(2906002)(53936002)(4326008)(5250100002)(110136005)(19627405001)(54896002)(5024004)(6116002)(3846002)(55016002)(8936002)(14454004)(93886005)(66066001)(6436002)(54906003)(476003)(44832011)(53546011)(4744004)(8676002)(81166006)(76176011)(6506007)(446003)(11346002)(66574009)(81156014)(486006)(345774005)(71200400001)(71190400001)(105586002)(26005)(5660300001)(106356001)(86362001)(74316002)(316002)(33656002)(99286004)(9686003)(97736004)(102836004)(7696005)(186003)(39060400002)(551934003)(7736002)(68736007)(25786009)(561944003)(478600001)(2900100001)(473944003)(414714003); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0701MB2124; H:HE1PR0701MB2393.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: +KS7qh+RWuU3eGu5IuImRTSBlvflTYI9ZY5F1Ji9Z0vgA5yTK3/J5xmao+P7Tn0kRPZykz15fkVxwaVLobpOhMA6VOWTmOp2/tFVQG8X4CKUe/1y/RYNWDuqarFDJzyy9AXCVN7UDcGbaU7TVXSxW+weLEo3Z3iM2eCuA8FC6Mmi9Xj68WezJ9iDxLC1ZdS9+osM/Lo84dNQW07Zvmlv4VKEDJpYlIasxjDHfNydpfq6KRQ9gRGD9UkN7vYNcCLQngZDNeqTHl4JBSOMSFh/tbcZGV+zYDJvW3AoY/EJQ52aqaaCvHCGG3/LmwaBMk3F5wBqIZdrXftGVMk9+8B0KdIdvYjcXeFMYxOX1JhCXkg=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HE1PR0701MB23937DEBD284002B65CAA3EEE2EB0HE1PR0701MB2393_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 8647b279-0d52-4bbb-3874-08d62ad4f18b
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Oct 2018 15:12:19.1538 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2124
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SWUwTURSGuZ3pzIA0XiuEE1DExgc1UhZ9KMaVGGmMLL4RNbEFJoAsJS2C LImgiISKFmWxQLUBBC0ERVEsiliiEJCAokEFWapF0geVRaOoQdtOTXj7zvn/s91chhCO8L2Z xNR0VpkqTxZRbqQ2uj3Tv/ZU+5HAwhshkoaf6ySX86tpSWvBF0ryee4cX3K6VkdLfs0U05Lz +hV7aOlQ722+1Fg1TktHr/ST0vr6RZ604FMfJbV0acko6rDbjjg2OTGDVQbskrklDL8yo7SK ft5JjbWZn4eemnjFyJUBvA3UZwZQMXJjhPgZgsWCNoILviO4f2mJ4oI6Hrwe+eBQSKwhoGa+ wWkr48GL5iFkbybE0whavrJ2prAYBsbVtnKG8cBhUPl9p91P4EEEeUWllN2zGm+BeWu1YxEP 7A/5hiYnH4cL4+MOD4k3wGxDkYMFWAazxk4+N1jjDsaJe7RdcMWHQF1iIu2M8FqY/DHhYAJ7 wYJuynkphvpHQwTHnmD9uMTn2A++6J5THK+F4Wtqx2sAfkJDY6EecYI/zJaXO4vDQVtsJjhT H4LZl018+5lgO0ebL7cjwkfh11gaZ1fA+7/9JGfXISi6WuAc7AuGEjOpQYFVy3blWAFd5imq ynH0KujTWsgqW1sCb4JbHQGcZT2Uqc00xxvhbI2OXp7XI9qAPFWsKiYlPjhYzCoTY1UqRao4 lU2/g2y/zdT2O/ABss7s7UaYQSJ3gUtu+xEhX56hykrpRsAQIg/BXI4tJYiTZ2WzSsUx5Ylk VtWNfBhS5CWQRNw9LMTx8nQ2iWXTWOV/lce4euch3qQsZ2tZhKupuqtlMDtzYaxiIPpm1p+l feF1oROxM4/nUnp8VhxYSgpK+vZuxnDwOpZ1GfZPm0Kp3WMuuQ9j9gx6KN6GLEam74sI13tZ Q6NqPq4vbbT8NP6QSTtkuae2a8zNGtGNTvriSl/1m9ae0d5KsaXQXR7pZ1RHnVkTtl9EqhLk QZsJpUr+D246owtpAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fqU-fiuAGkC0JjaqbGQ-l7_LELE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Oct 2018 15:13:45 -0000

--_000_HE1PR0701MB23937DEBD284002B65CAA3EEE2EB0HE1PR0701MB2393_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SSdtIGhhcHB5IHdpdGggZW5kcG9pbnRzIGhhdmluZyB0aGUgcG9zc2liaWxpdHkgdG8gZ3JlYXNl
IHRoZSBiaXQgZXZlbiBmb3IgdGhlIG5lZ290aWF0ZWQgdmVyc2lvbi4NCg0KVGhlIGZld2VyIGFz
c3VtcHRpb25zIG1pZGRsZWJveGVzIG1ha2UgYWJvdXQgZXhwZWN0ZWQgYmVoYXZpb3VyIHRoZSBi
ZXR0ZXIuDQoNCkZvciBhIHNwaW5ib3ggdGhlcmUncyBiYXNpY2FsbHkgb25seSB0aHJlZSBhc3N1
bXB0aW9ucyB0aGF0IGNhbiBiZSBtYWRlIHRoZW46IG5vbi1zcGluIHZlcnNpb25zIGFyZSB1bmlu
dGVyZXN0aW5nLCBzcGluLXZlcnNpb24ocykgbWlnaHQgYmUgaW50ZXJlc3RpbmcsIGZsb3dzIHdp
dGggdW5rbm93biB2ZXJzaW9uIG1pZ2h0IGJlIGludGVyZXN0aW5nLg0KDQpfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KRnLDpW46IFFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZz4g
ZsO2ciBLYXp1aG8gT2t1IDxrYXp1aG9va3VAZ21haWwuY29tPg0KU2tpY2thdDogZGVuIDUgb2t0
b2JlciAyMDE4IDE2OjAwDQpUaWxsOiBCcmlhbiBUcmFtbWVsbA0KS29waWE6IElFVEYgUVVJQyBX
RzsgTGlsaSBQZWF1ZGNoaWVuOyBNaWtlIEJpc2hvcDsgTWFydGVuIFNlZW1hbm47IENocmlzdGlh
biBIdWl0ZW1hOyBNYXJjdXMgSWhsYXINCsOEbW5lOiBSZTogU3BpbiBiaXQgYXMgYSBuZWdvdGlh
dGVkIG9wdGlvbg0KDQoyMDE45bm0MTDmnIg15pelKOmHkSkgMjE6MjcgQnJpYW4gVHJhbW1lbGwg
KElFVEYpIDxpZXRmQHRyYW1tZWxsLmNoPjoNCj4NCj4NCj4NCj4gPiBPbiA1IE9jdCAyMDE4LCBh
dCAxMjo1NiwgTWFyY3VzIElobGFyIDxtYXJjdXMuaWhsYXJAZXJpY3Nzb24uY29tPiB3cm90ZToN
Cj4gPg0KPiA+IEkgc2VlIHlvdXIgcG9pbnQsIGJ1dCBJIGRvbsK0dCBiZWxpZXZlIGl0IGlzIGEg
cGFydGljdWxhcmx5IHJlYWxpc3RpYyBzY2VuYXJpby4NCj4gPiBJdCBpcyBpbiB0aGUgaW50ZXJl
c3Qgb2YgdGhlIG5ldHdvcmsgb3BlcmF0b3JzIHRvIGVuc3VyZSB0aGF0IHRoZWlyIHN1YnNjcmli
ZXJzIGhhcyBhcyBnb29kIGFuZCBjb25zaXN0ZW50IGV4cGVyaWVuY2UuDQo+ID4gQmxhY2tob2xp
bmcgdmVyc2lvbnMgb2YgUVVJQyBoYXMgdGhlIHBvdGVudGlhbCBvZiBjb21wbGV0ZWx5IGRpc3J1
cHRpbmcgc2VydmljZXMgYW5kIGludHJvZHVjZSBpbmNvbnNpc3RlbnQgYmVoYXZpb3IuDQo+ID4g
VGhlIHNwaW5iaXQgaXMgaW50ZW5kZWQgYXMgYSB0b29sIHRvIGFzc2lzdCB0cm91Ymxlc2hvb3Rp
bmcgYW5kIHF1YWxpdHkgbW9uaXRvcmluZy4gRXhwbGljaXRseSBpbnRyb2R1Y2luZyBwb3RlbnRp
YWxseSBwb29yIG5ldHdvcmsgZXhwZXJpZW5jZSB3aXRoIHRoZSBob3BlcyB0aGF0IHlvdXIgdHJv
dWJsZXNob290aW5nIC8gbW9uaXRvcmluZyBjYXBhYmlsaXRpZXMgaW1wcm92ZXMgaXMgYSByZWFs
bHkgYmFkIGlkZWEsIGV2ZW4gZm9yIHRoZSBtb3N0IGN5bmljYWwgbmV0d29yayBvcGVyYXRvci4N
Cj4NCj4gKyBhIHdob2xlIGxvdCB0byB0aGlzLiBUcmVhdGluZyBtaWRkbGVib3hlcyBhcyBhIGJ5
emFudGluZSBhZHZlcnNhcnkgaXMgYSB1c2VmdWwgdGhvdWdodCBleHBlcmltZW50IHRvIGRldGVy
bWluZSB0aGUgY29ybmVyIGNhc2VzIGluIGEgcHJvdG9jb2wsIGJ1dCBJIGRvIG5vdCB0aGluayB3
ZSBhcmUgd2VsbCBzZXJ2ZWQgYnkgdHJlYXRpbmcgYWxsIGFyYml0cmFyeSBhaW1zIGFuZCBjYXBh
YmlsaXRpZXMgb24gcGF0aCBhcyBlcXVhbGx5IGxpa2VseS4NCj4NCj4gQXQgdGhlIGVuZCBvZiB0
aGUgZGF5LCBldmVyeSBvbmUgb2YgdGhlIG1pZGRsZWJveGVzIHRoYXQgd2UgY3Vyc2UgZm9yIHRo
ZWlyIG9zc2lmaWNhdGlvbiB3YXMgYm91Z2h0IGFuZCBzb2xkIGJlY2F1c2UgdGhlIG9wZXJhdG9y
IGRlcGxveWluZyBpdCBiZWxpZXZlZCBpdCBzb2x2ZWQgYSBwcm9ibGVtIHRoZXkgaGFkLCBzbyBh
bmFseXppbmcgdGhlIHNwYWNlIG9mIGxpa2VseSAqaW50ZW50aW9uYWwqIGJlaGF2aW9ycyByZWR1
Y2VzIHRvIGFuIGFuYWx5c2lzIG9mIHRoZSBidXNpbmVzcyBjYXNlIGZvciBlYWNoIG9mIHRob3Nl
IGJlaGF2aW9ycy4NCj4NCj4gSSBmcmFua2x5IGRvbid0IHNlZSB0aGUgYnVzaW5lc3MgY2FzZSBm
b3IgYSBzcGluLWJpdC1ibG9ja2luZyBtaWRkbGVib3ggdGhhdCB3b3VsZG4ndCBqdXN0IGJsb2Nr
IFFVSUMgd2hvbGVzYWxlLg0KDQpJbiBhZGRpdGlvbiB0byB3aGF0IEFsZXhhbmRyZSBhbmQgTWFy
Y3VzIGhhdmUgcG9pbnRlZCBvdXQsIEkgd291bGQNCmxpa2UgdG8gc2Vjb25kIHdoYXQgQnJpYW4g
aGFzIHN0YXRlZCBoZXJlLg0KDQpUaGVyZSBhcmUgYnVzaW5lc3MtcmVsYXRlZCByZWFzb25zIHRv
IHByZWZlciBUQ1Agb3ZlciBRVUlDLiBUaGVyZSBhcmUNCm1pZGRsZWJveCB2ZW5kb3JzIHNlbGxp
bmcgVENQIHRyYWZmaWMtc2hhcGluZyBtaWRkbGVib3hlcyB0aGF0IGNsYWltDQp0byByZWR1Y2Ug
dGhlIGNvbnN1bWVkIGJhbmR3aWR0aCAoYnkgcmVkdWNpbmcgdGhlIG51bWJlciBvZg0KcmV0cmFu
c21pdHMsIHV0aWxpemluZyB0aGUgaW5mb3JtYXRpb24gYWJvdXQgdGhlIGNvbmRpdGlvbiBvZiB0
aGUNCm1vYmlsZSBuZXR3b3JrKS4gVGhlcmUgYXJlIChzdGlsbCEpIG5ldHdvcmtzIHRoYXQgZ2l2
ZSBwcmVmZXJlbnRpYWwNCnRyZWF0bWVudCB0byBub24tVExTIEhUVFAgYmVjYXVzZSB0aGV5IGNh
biBkZXBsb3kgdHJhbnNwYXJlbnQsDQpjb21wcmVzc2luZyBwcm94aWVzLg0KDQpDb21wYXJlZCB0
byB0aG9zZSBjYXNlcywgc3BpbiBiaXQgaGFzIHZlcnkgd2VhayByZWFzb24gZm9yDQpwcmVmZXJl
bnRpYWwgdHJlYXRtZW50IChpLmUuIHRyb3VibGVzaG9vdGluZyBhbmQgcXVhbGl0eSBtb25pdG9y
aW5nKS4NCg0KQmVzaWRlcywgdGhlIGVuZHBvaW50cyB3b3VsZCBhbHNvIGhhdmUgdGhlIGNob2lj
ZSB0byBleHBvc2UgZmFrZQ0Kc2lnbmFsIG9uY2Ugd2Ugc3RhcnQgc2VlaW5nIG5ldHdvcmtzIGJs
b2NraW5nIFFVSUMgd2l0aG91dCB0aGUgc3Bpbg0KYml0LiBBY3R1YWxseSwgdGhhdCBpcyB0aGUg
c3RhdHVzLXF1bywgaW4gd2hpY2ggd2UgZG8gbm90IGhhdmUgYW55DQpuZWdvdGlhdGlvbi4gVG8g
cHV0IGl0IHRoZSBvdGhlciB3YXksIHRoZSBlbmRwb2ludHMgbG9zZSBub3RoaW5nIGJ5DQp1c2lu
ZyB0aGUgdmVyc2lvbiBudW1iZXIgZmllbGQgZm9yIGV4cG9zaW5nIHRoZSBhdmFpbGFiaWxpdHkg
b2YgdGhlDQpzaWduYWwuDQoNCj4gQnV0IEknbSBub3QgYSBtaWRkbGVib3ggdmVuZG9yLCBzbyBt
YXliZSBJJ20ganVzdCBtaXNzaW5nIHNvbWV0aGluZy4NCj4NCj4gTm93LCB0aGVyZSBtYXkgYmUg
c29tZSAqdW5pbnRlbnRpb25hbCogYnJlYWthZ2UgYmVjYXVzZSBzb21lIG1pZGRsZWJveCB2ZW5k
b3Igb25seSBoYXBwZW5zIHRvIGFuYWx5emUgdHJhZmZpYyB0aGF0IHNwaW5zIHdoZW4gdHJ5aW5n
IHRvIHJldmVyc2UtZW5naW5lZXIgUVVJQywgYW5kIGRlY2lkZXMgdGhhdCB0aGUgbm9uLXNwaW5u
aW5nIHZlcnNpb24gaXMganVzdCBncmVhc2UgYW5kIGJsb2NrcyBpdC4gQnV0IHRoYXQgc2VlbXMg
dG8gbWUgdG8gYmUgbW9yZSBhbiBhcmd1bWVudCB0byByb2J1c3RseSBleGVyY2lzZSB2ZXJzaW9u
IG5lZ290aWF0aW9uIGZyb20gZGF5IG9uZSB0aGFuIGFueXRoaW5nIGVsc2UuDQo+DQo+IENoZWVy
cywNCj4NCj4gQnJpYW4NCj4NCj4gPiBGcm9tOiBNYXJ0ZW4gU2VlbWFubiA8bWFydGVuc2VlbWFu
bkBnbWFpbC5jb20+DQo+ID4gU2VudDogZGVuIDUgb2t0b2JlciAyMDE4IDEyOjMzDQo+ID4gVG86
IE1hcmN1cyBJaGxhciA8bWFyY3VzLmlobGFyQGVyaWNzc29uLmNvbT4NCj4gPiBDYzogYWxleGFu
ZHJlLmZlcnJpZXV4QG9yYW5nZS5jb207IGh1aXRlbWFAaHVpdGVtYS5uZXQ7IGlldGZAdHJhbW1l
bGwuY2g7IGthenVob29rdUBnbWFpbC5jb207IG1iaXNob3BAZXZlcXVlZm91LmJlOyBxdWljQGll
dGYub3JnDQo+ID4gU3ViamVjdDogUmU6IFNwaW4gYml0IGFzIGEgbmVnb3RpYXRlZCBvcHRpb24N
Cj4gPg0KPiA+IFRoZSBwcm9ibGVtIHdpdGggdXNpbmcgYSBzcGVjaWZpYyB2ZXJzaW9uIGZvciBp
bXBsZW1lbnRhdGlvbnMgdGhhdCB1c2UgYW5kIGRvbuKAmXQgdXNlIHRoZSBzcGluIGJpdCBpcyB0
aGF0IG1pZGRsZWJveGVzIGNhbiBlZmZlY3RpdmVseSBlbmZvcmNlIHVzYWdlIG9mIHRoZSBzcGlu
IGJpdCB2ZXJzaW9uIGJ5IGJsYWNraG9saW5nIGV2ZXJ5IHBhY2tldCBhZHZlcnRpc2luZyBhIHZl
cnNpb24gdGhhdCBkb2VzbuKAmXQgdXNlIHRoZSBzcGluIGJpdC4gSWYgb25seSBhIGZldyBtaWRk
bGVib3hlcyBkbyB0aGF0LCB0aGlzIHdvdWxkIGZvcmNlICphbGwqIGltcGxlbWVudGF0aW9ucyB0
byBhdm9pZCB0aGVzZSB2ZXJzaW9ucy4NCj4gPiBJbXBsZW1lbnRhdGlvbnMgdGhhdCBkb27igJl0
IHdhbnQgdG8gZXhwb3NlIHRoZWlyIFJUVCB3b3VsZCB0aGVuIGhhdmUgdG8gbmVnb3RpYXRlIGEg
dmVyc2lvbiB0aGF0IGlzIHN1cHBvc2VkIHRvIHVzZSB0aGUgc3BpbiBiaXQsIGJ1dCB0aGVuIGdy
ZWFzZSB0aGUgY29ycmVzcG9uZGluZyBiaXRzIGluIG9yZGVyIHRvIHByZXNlcnZlIHRoZWlyIHBy
aXZhY3kuIE9mIGNvdXJzZSwgdGhpcyB3b3VsZCBvbmx5IHdvcmsgaWYgdGhlIHBlZXIgZG9lc27i
gJl0IGVuZm9yY2UgY29tcGxpYW5jZS4gT3RoZXJ3aXNlLCB3ZeKAmWxsIGVuZCB1cCBpbiBhIHdv
cmxkIHdoZXJlIGl04oCZcyBiYXNpY2FsbHkgaW1wb3NzaWJsZSB0byBvcHQtb3V0IG9mIHRoZSBz
cGluLWJpdC4NCj4gPg0KPiA+IE9uIEZyaSwgT2N0IDUsIDIwMTggYXQgMTI6MTUgTWFyY3VzIElo
bGFyIDxtYXJjdXMuaWhsYXJAZXJpY3Nzb24uY29tPiB3cm90ZToNCj4gPiBIaSwNCj4gPiBJIGxp
a2UgdGhpcyBhcHByb2FjaCBzaW5jZSBpdCBhbGxvd3MgdXMgdG8gZGlzcmVnYXJkIG5vbi1zcGlu
bmluZyBmbG93cyBieSBzaW1wbHkgb2JzZXJ2aW5nIHRoZSBpbml0aWFsIGhhbmRzaGFrZS4gVGhp
cyBzYXZlcyB1cyBxdWl0ZSBzb21lIHdvcmsuDQo+ID4gT24gdGhlIGhldXJpc3RpY3MgcGFydCwg
d2UgY2Fubm90IGdldCBhd2F5IGZyb20gaXQsIGV2ZW4gaWYgd2Ugc2VlIHRoZSBzcGluIHZlcnNp
b24gaW4gdGhlIGluaXRpYWwgaGFuZHNoYWtlIGFzIHRoZXJlwrRzIG5vIGd1YXJhbnRlZSB0aGF0
IGFuIGVuZHBvaW50IHdpbGwgc2V0IHRoZSBiaXQgcHJvcGVybHkgYW55d2F5Lg0KPiA+IEhvd2V2
ZXIsIGZvciB0aGUgdmVyc2lvbiB3aGVyZSB0aGUgaW50ZW50IHRvIHVzZSBzcGluYml0IGlzIGV4
cGxpY2l0IGl0IGFjdHVhbGx5IG1ha2VzIHNlbnNlIGZvciBhbiBlbmRwb2ludCB0byB0cmVhdCBu
b24tcGFydGljaXBhdGluZyBiZWhhdmlvciBhcyBhIHByb3RvY29sIGVycm9yLg0KPiA+DQo+ID4g
TWFyY3VzDQo+ID4NCj4gPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+IEZyb206IFFV
SUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxmIE9mIE1pa2UgQmlzaG9wDQo+ID4g
U2VudDogZGVuIDUgb2t0b2JlciAyMDE4IDAwOjQwDQo+ID4gVG86IGFsZXhhbmRyZS5mZXJyaWV1
eEBvcmFuZ2UuY29tOyBLYXp1aG8gT2t1IDxrYXp1aG9va3VAZ21haWwuY29tPg0KPiA+IENjOiBC
cmlhbiBUcmFtbWVsbCA8aWV0ZkB0cmFtbWVsbC5jaD47IElFVEYgUVVJQyBXRyA8cXVpY0BpZXRm
Lm9yZz47IENocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0Pg0KPiA+IFN1Ympl
Y3Q6IFJFOiBTcGluIGJpdCBhcyBhIG5lZ290aWF0ZWQgb3B0aW9uDQo+ID4NCj4gPiBTbyBsb25n
IGFzIHRoaXMgaXMgdGhlIG9ubHkgdGhpbmcgYmVpbmcgbmVnb3RpYXRlZCwgaXQncyBub3QgdG9v
IGJhZC4gIElmIHdlIHdhbnQgdG8gbmVnb3RpYXRlIG90aGVyIHRoaW5ncywgaXQgcXVpY2tseSBn
ZXRzIG91dCBvZiBoYW5kLiAgT25lIGNvdWxkIHBsYXVzaWJseSBhcmd1ZSB0aGF0IHRoZSBzcGlu
IGJpdCBpcyBzcGVjaWFsIGluIHRoYXQgd2UgYWN0dWFsbHkgd2FudCBwYXJ0aWVzIG9ic2Vydmlu
ZyB0aGUgdHJhbnNhY3Rpb24gdG8gdW5kZXJzdGFuZCB3aGljaCBvcHRpb24gaGFzIGJlZW4gc2Vs
ZWN0ZWQuDQo+ID4NCj4gPiBJdCdzIGltcG9ydGFudCB0byByZW1lbWJlciwgdGhvdWdoLCB0aGF0
IHRoaXMgaXMgaW5mb3JtYXRpb24geW91IGdldCBvbmx5IGF0IHRoZSBiZWdpbm5pbmcgb2YgYSBu
ZXcgY29ubmVjdGlvbi4gIElmIHRoZXJlJ3MgbWlncmF0aW9uIG9yIE5BVCByZWJpbmRpbmcsIGl0
J3Mgbm90IGd1YXJhbnRlZWQgKGFuZCBpbiBmYWN0LCBub3QgaW50ZW5kZWQpIHRoYW4geW91IGNh
biBjb3JyZWxhdGUgaXQgYmFjayB0byBhIHBhcnRpY3VsYXIgcHJldmlvdXMgaGFuZHNoYWtlLiAg
WW91J2xsIHN0aWxsIGVpdGhlciBuZWVkIGhldXJpc3RpY3MgdG8gaWRlbnRpZnkgd2hldGhlciB0
aGUgc3BpbiBiaXQgaXMgYWN0dWFsbHkgaW4gdXNlLCBvciB5b3UnbGwgbmVlZCB0byBpZ25vcmUg
YW55IHRyYWZmaWMgZm9yIHdoaWNoIHlvdSBkaWRuJ3Qgc2VlIHRoZSBoYW5kc2hha2UuDQo+ID4N
Cj4gPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+IEZyb206IFFVSUMgPHF1aWMtYm91
bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxmIE9mIGFsZXhhbmRyZS5mZXJyaWV1eEBvcmFuZ2UuY29t
DQo+ID4gU2VudDogVGh1cnNkYXksIE9jdG9iZXIgNCwgMjAxOCAzOjQ3IEFNDQo+ID4gVG86IEth
enVobyBPa3UgPGthenVob29rdUBnbWFpbC5jb20+DQo+ID4gQ2M6IEJyaWFuIFRyYW1tZWxsIDxp
ZXRmQHRyYW1tZWxsLmNoPjsgSUVURiBRVUlDIFdHIDxxdWljQGlldGYub3JnPjsgQ2hyaXN0aWFu
IEh1aXRlbWEgPGh1aXRlbWFAaHVpdGVtYS5uZXQ+DQo+ID4gU3ViamVjdDogUmU6IFNwaW4gYml0
IGFzIGEgbmVnb3RpYXRlZCBvcHRpb24NCj4gPg0KPiA+IFRoYW5rcyBLYXp1aG8uIFVzaW5nIHZl
cnNpb24gbnVtYmVycyBkaXJlY3RseSB3YXMgYW4gb2J2aW91cyBjaG9pY2UsIGJ1dCBzbyBmYXIg
SSB3YXMgZGlzY291cmFnZWQgYnkgc3Ryb25nIGxhbmd1YWdlIGluIHRoZSBzcGVjLCBzYXlpbmcg
MHgwMDAwMDAwMSB3YXMgdGhlIHVuYXZvaWRhYmxlIHBvaW50IG9mIGNvbnZlcmdlbmNlIGFmdGVy
IGFsbCAweEZGMDAwMFhYIGV4cGVyaW1lbnRzLi4gU28gaW4gZXNzZW5jZSB5b3UncmUgcHJvcG9z
aW5nIHRvIHdlYWtlbiB0aGF0IGEgYml0LCByaWdodCA/DQo+ID4NCj4gPiBJZiBzbywgaG93IGRv
IHlvdSBlbnZpc2lvbiBzZWdtZW50aW5nIHRoZSB2ZXJzaW9uIG51bWJlciBzcGFjZSA/DQo+ID4N
Cj4gPiAgIC0gZGlyZWN0IGVudW1lcmF0aW9uOg0KPiA+DQo+ID4gICAgICAgICAweDAwMDAwMDAx
ID0gdjFkcnkNCj4gPiAgICAgICAgIDB4MDAwMDAwMDIgPSB2MSArIHNwaW5iaXQNCj4gPiAgICAg
ICAgIDB4MDAwMDAwMDMgPSB2MSArIHNwaW5iaXQgKyBWRUMNCj4gPg0KPiA+ICAgLSBsb3cgb3Jk
ZXIgYml0cyBmb3Igb3B0aW9uczoNCj4gPg0KPiA+ICAgICAgICAgMHgwMDAwMDFYWCA9IHYxICsg
b3B0aW9uIFhYDQo+ID4gICAgICAgICAweDAwMDAwMllZID0gdjIgKyBvcHRpb24gWVkNCj4gPg0K
PiA+IEFsc28sIGFyZSB3ZSBzdXJlIHRoYXQgdGhpcyBleHBsb3Npb24gd29uJ3Qgd2VpZ2ggb24g
dGhlIG5ldyBWTiBzY2hlbWUsIGluZHVjaW5nIHNsb3dlciBjb252ZXJnZW5jZSBkdWUgdG8gbG9u
Z2VyIGxpc3RzIG9uIGVpdGhlciBzaWRlID8NCj4gPg0KPiA+IE9uIDEwLzA0LzE4IDExOjUwLCBL
YXp1aG8gT2t1IHdyb3RlOg0KPiA+ID4gSGksDQo+ID4gPg0KPiA+ID4gVGhhbmsgeW91IGZvciBz
dGFydGluZyB0aGUgZGlzY3Vzc2lvbiBzcGVjaWZpYyB0byBob3cgd2UgY291bGQNCj4gPiA+IHBv
c3NpYmx5IG5lZ290aWF0ZSB0aGUgdXNlIG9mIHNwaW4gYml0cy4NCj4gPiA+DQo+ID4gPiBSZWdh
cmRpbmcgdGhlIHRvcGljLCBteSBwcmVmZXJlbmNlIGdvZXMgdG8gdXNpbmcgdGhlIHZlcnNpb24g
bnVtYmVyDQo+ID4gPiBmaWVsZCBvZiB0aGUgbG9uZyBoZWFkZXIgZm9yIG5lZ290aWF0aW5nIHRo
ZSBwcmVzZW5jZSBvZiBzcGluIGJpdHMsIG9yDQo+ID4gPiBhbnkgYWRkaXRpb25hbCBzaWduYWwg
YmVpbmcgZXhwb3NlZCB0byB0aGUgbmV0d29yay4NCj4gPiA+DQo+ID4gPiBGb3IgZXhhbXBsZSwg
UVVJQ3YxIHdpdGhvdXQgc3BpbiBiaXQgY291bGQgdXNlIHZlcnNpb24gMHgxMDEsIGFuZCB2MQ0K
PiA+ID4gd2l0aCBzcGluIGJpdCBjb3VsZCB1c2UgMHgxMDIuIEluIHRoZSBmdXR1cmUsIHdlIGNh
biBhc3NpZ24gYQ0KPiA+ID4gZGlmZmVyZW50IHZlcnNpb24gbnVtYmVyIGZvciBRVUlDdjEgd2l0
aCBtdWx0aXBsZSBzcGluICsgVkVDIChvcg0KPiA+ID4gcGVvcGxlIGludGVyZXN0ZWQgaW4gdGVz
dGluZyB0aGUgZmVhdHVyZSBjYW4gZGVzaWduYXRlIGEgcHJpdmF0ZQ0KPiA+ID4gdmVyc2lvbiBu
dW1iZXIgZXZlbiBiZWZvcmUgdGhhdCkuDQo+ID4gPg0KPiA+ID4gSSBzZWUgdGhlIGZvbGxvd2lu
ZyBiZW5lZml0cyB0byB1c2luZyB0aGUgdmVyc2lvbiBmaWVsZCBhcyBhIG1ldGhvZCB0bw0KPiA+
ID4gbmVnb3RpYXRlIHRoZSB1c2Ugb2Ygc3BpbiBiaXRzLg0KPiA+ID4NCj4gPiA+IDEuIE9uZSBv
ZiB0aGUgY29uY2VybiByZWdhcmRpbmcgc3BpbiBiaXRzIGhhcyBiZWVuIHRoYXQgdGhleSBjb3Vs
ZA0KPiA+ID4gbGVhZCB0byBvc3NpZmljYXRpb24uIFNwaW4gYml0cyBhcmUgbm90IHBhcnQgb2Yg
dGhlIEludmFyaWFudHMsIGJ1dCBpZg0KPiA+ID4gdGhlIG9ic2VydmF0aW9uIHRvb2xzIHN0YXJ0
IGxvb2tpbmcgYXQgdGhvc2UgYml0cyB3aXRob3V0IGNoZWNraW5nIHRoZQ0KPiA+ID4gdmVyc2lv
biBudW1iZXIgZmllbGQsIHdlIHdpbGwgaGF2ZSB0aGUgcHJlc3N1cmUgdG8gbm90IGNoYW5nZSBo
b3cgdGhlDQo+ID4gPiBiaXRzIGFyZSB1c2VkLiBVc2luZyB0aGUgdmVyc2lvbiBudW1iZXIgdG8g
aW5kaWNhdGUgdGhlIHByZXNlbmNlIG9mDQo+ID4gPiBzcGluIGJpdHMgaXMgdGhlIGJlc3QgYXBw
cm9hY2ggdG8gcmVzb2x2ZSBzdWNoIGNvbmNlcm4uDQo+ID4gPg0KPiA+ID4gMi4gV2UgaGF2ZSBo
b3BlZCB0byByb2xsIG91dCBtdWx0aXBsZSB2ZXJzaW9ucyBvZiBRVUlDIGluIGEgc21hbGwNCj4g
PiA+IGludGVydmFsIHNvIHRoYXQgdGhlIHZlcnNpb24gbnVtYmVyIGZpZWxkIGRvZXMgbm90IGdl
dCBvc3NpZmllZC4gVGhlDQo+ID4gPiBiZXN0IHNvbHV0aW9uIGlzIG9idmlvdXNseSB0byByb2xs
IG91dCB0d28gZmxhdm9ycyBvZiB0aGUgcHJvdG9jb2wNCj4gPiA+IHRoYXQgdXNlcyBkaWZmZXJl
bnQgdmVyc2lvbiBudW1iZXJzIGF0IHRoZSBzYW1lIHRpbWUuIFdlIHdpbGwgaGF2ZSBhDQo+ID4g
PiByZWFsLXdvcmxkIHVzZSBvZiB2ZXJzaW9uIG5lZ290aWF0aW9uIGZyb20gZGF5IG9uZSwgYmVj
YXVzZSB3ZSBhcmUgaW4NCj4gPiA+IGEgY29uZGl0aW9uIHdoZXJlIGltcGxlbWVudG9ycyBoYXZl
IGRpZmZlcmVudCBvcGluaW9ucyBvbiBpZiB0aGV5DQo+ID4gPiBzaG91bGQgc3VwcG9ydCBzcGlu
IGJpdCA6LSkNCj4gPiA+DQo+ID4gPiBUaGUgYmxvY2tlciB0byB0aGlzIGFwcHJvYWNoIGhhcyBi
ZWVuIHZlcnNpb24gbmVnb3RpYXRpb24gcmVxdWlyaW5nIGFuDQo+ID4gPiBhZGRpdGlvbmFsIHJv
dW5kLXRyaXAsIGJ1dCB0aGF0IGlzIGdvaW5nIHRvIGJlIHJlc29sdmVkIGJ5ICMxNzU1Lg0KPiA+
ID4NCj4gPiA+IDIwMTjlubQxMOaciDPml6Uo5rC0KSAxOTowNiA8YWxleGFuZHJlLmZlcnJpZXV4
QG9yYW5nZS5jb20+Og0KPiA+ID4+DQo+ID4gPj4gT24gMTAvMDMvMTggMDk6NTgsIEJyaWFuIFRy
YW1tZWxsIChJRVRGKSB3cm90ZToNCj4gPiA+PiA+IEJhY2tpbmcgb2ZmIHRoZSBNVVNUIGZvciBu
b3cgZm9yIHN1Y2ggc2l0dWF0aW9ucyBpcyBJTU8gYSBnb29kDQo+ID4gPj4gPiB0cmFkZW9mZiwg
dGhvdWdoLCBlc3BlY2lhbGx5IHNpbmNlIHdlIG9ubHkgbmVlZCBmcmFjdGlvbnMgb2YgYQ0KPiA+
ID4+ID4gcGVyY2VudCBvZiBkZXBsb3ltZW50IHRvIHN0YXJ0IHNlZWluZyB1c2VmdWwgc2lnbmFs
IGZvcg0KPiA+ID4+ID4gYmFzZWxpbmUvYW5vbWFseSBtZWFzdXJlbWVudCBvZiBsYXJnZSBhZ2dy
ZWdhdGVzLg0KPiA+ID4+DQo+ID4gPj4gSWYgdGhlIGNvbnNlbnN1cyBpcyB0aGF0IHdlIG11c3Qg
YWxsb3cgZm9yIHN1Y2ggc2l0dWF0aW9ucywgdGhlbg0KPiA+ID4+IHRoZXJlIGFyZSB0d28NCj4g
PiA+PiBwb3NzaWJpbGl0aWVzOg0KPiA+ID4+DQo+ID4gPj4gICAoYSkgd2VhayBzcGVjIGxhbmd1
YWdlIChNQVkgV0lTSCBUTyBvciBzaW1pbGFyKSA9PiBtYW55DQo+ID4gPj4gaW1wbGVtZW50YXRp
b25zIHdpbGwgc2ltcGx5IGRyb3AgaXQNCj4gPiA+Pg0KPiA+ID4+ICAgKGIpIG5lZ290aWF0ZWQg
b3B0aW9uIHdoZXJlIHRoZSBuZWdvdGlhdGlvbiBtZWNoYW5pc20gaXMgbWFuZGF0b3J5DQo+ID4g
Pj4NCj4gPiA+PiBJbiB0aGUgdmVpbiBvZiAoYiksIENocmlzdGlhbiBzdWdnZXN0ZWQgb2ZmbGlu
ZSB0byBpbnRyb2R1Y2UNCj4gPiA+PiBuZWdvdGlhdGlvbiB0byBhbGxvdyBmb3IgZXhwZXJpbWVu
dGF0aW9uIG9mIHRoZSByZW1haW5pbmcgdHdvDQo+ID4gPj4gcmVzZXJ2ZWQgYml0cy4gVGhlbiBt
YXkgYmUgd2UgY2FuIHN5bnRoZXNpemUgYm90aCBpZGVhcyBieSB0aGUgZm9sbG93aW5nIHByb3Bv
c2FsOg0KPiA+ID4+DQo+ID4gPj4gICAtIGluIHRoZSBmaXJzdCBmZXcgZXhjaGFuZ2VzIG9mIHRo
ZSA1LXR1cGxlLCB1c2UgdGhlIHRocmVlIGJpdHMgZm9yDQo+ID4gPj4gb3B0aW9uIG5lZ290aWF0
aW9uDQo+ID4gPj4NCj4gPiA+PiAgIC0gdGhlbiB1c2UgdGhlbSBhcyBkZWZpbmVkIGJ5IHRoZSBz
ZWxlY3RlZCBvcHRpb24NCj4gPiA+Pg0KPiA+ID4+IEV4YW1wbGUgZW5jb2RpbmdzOg0KPiA+ID4+
DQo+ID4gPj4gICAwMDAgOiBub3RoaW5nDQo+ID4gPj4gICAwMDEgOiBzcGluIGJpdCBhbG9uZSA6
IFMwMA0KPiA+ID4+ICAgMDEwIDogc3BpbiBiaXQgKyBWRUMgOiBTVlYNCj4gPiA+PiAgIC4uLiA6
IG90aGVyIGV4dGVuc2lvbnMNCj4gPiA+Pg0KPiA+ID4+IFRoZSBuZWdvdGlhdGlvbiBtZWNoYW5p
c20gYWxsb3dzIGJvdGggZW5kcG9pbnRzIHRvIGZvcmNlIDAwMC4NCj4gPiA+PiBBbmQgc2luY2Ug
aXQgaXMgaW4gdGhlIGNsZWFyIGZpcnN0IGJ5dGUsIGl0IGFsbG93cyBvbi1wYXRoIG9ic2VydmVy
cw0KPiA+ID4+IHRvIGlkZW50aWZ5IHRoZSBvcHRpb24gd2l0aG91dCByZXNvcnRpbmcgdG8gaGV1
cmlzdGljczsgdGhpcyBoZWxwcyBpbg0KPiA+ID4+IHRoZSBjYXNlIG9mIGEgc21hbGwgc3VwcG9y
dCByYXRpby4NCj4gPiA+Pg0KPiA+ID4+DQo+ID4gPj4NCj4gPiA+Pg0KPiA+ID4+IF9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KPiA+ID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCj4gPiA+Pg0KPiA+ID4+IENlIG1lc3NhZ2UgZXQgc2VzIHBpZWNlcyBqb2ludGVz
IHBldXZlbnQgY29udGVuaXIgZGVzIGluZm9ybWF0aW9ucw0KPiA+ID4+IGNvbmZpZGVudGllbGxl
cyBvdSBwcml2aWxlZ2llZXMgZXQgbmUgZG9pdmVudCBkb25jIHBhcyBldHJlIGRpZmZ1c2VzLA0K
PiA+ID4+IGV4cGxvaXRlcyBvdSBjb3BpZXMgc2FucyBhdXRvcmlzYXRpb24uIFNpIHZvdXMgYXZl
eiByZWN1IGNlIG1lc3NhZ2UNCj4gPiA+PiBwYXIgZXJyZXVyLCB2ZXVpbGxleiBsZSBzaWduYWxl
ciBhIGwnZXhwZWRpdGV1ciBldCBsZSBkZXRydWlyZSBhaW5zaSBxdWUgbGVzIHBpZWNlcyBqb2lu
dGVzLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25pcXVlcyBldGFudCBzdXNjZXB0aWJsZXMgZCdhbHRl
cmF0aW9uLCBPcmFuZ2UgZGVjbGluZSB0b3V0ZSByZXNwb25zYWJpbGl0ZSBzaSBjZSBtZXNzYWdl
IGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBmYWxzaWZpZS4gTWVyY2kuDQo+ID4gPj4NCj4gPiA+
PiBUaGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBjb25maWRlbnRp
YWwgb3INCj4gPiA+PiBwcml2aWxlZ2VkIGluZm9ybWF0aW9uIHRoYXQgbWF5IGJlIHByb3RlY3Rl
ZCBieSBsYXc7IHRoZXkgc2hvdWxkIG5vdCBiZSBkaXN0cmlidXRlZCwgdXNlZCBvciBjb3BpZWQg
d2l0aG91dCBhdXRob3Jpc2F0aW9uLg0KPiA+ID4+IElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMg
ZW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBhbmQgZGVsZXRlIHRoaXMg
bWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRzLg0KPiA+ID4+IEFzIGVtYWlscyBtYXkgYmUgYWx0
ZXJlZCwgT3JhbmdlIGlzIG5vdCBsaWFibGUgZm9yIG1lc3NhZ2VzIHRoYXQgaGF2ZSBiZWVuIG1v
ZGlmaWVkLCBjaGFuZ2VkIG9yIGZhbHNpZmllZC4NCj4gPiA+PiBUaGFuayB5b3UuDQo+ID4gPj4N
Cj4gPiA+DQo+ID4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPg0KPiA+IENlIG1l
c3NhZ2UgZXQgc2VzIHBpZWNlcyBqb2ludGVzIHBldXZlbnQgY29udGVuaXIgZGVzIGluZm9ybWF0
aW9ucyBjb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVzIGV0IG5lIGRvaXZlbnQgZG9uYyBw
YXMgZXRyZSBkaWZmdXNlcywgZXhwbG9pdGVzIG91IGNvcGllcyBzYW5zIGF1dG9yaXNhdGlvbi4g
U2kgdm91cyBhdmV6IHJlY3UgY2UgbWVzc2FnZSBwYXIgZXJyZXVyLCB2ZXVpbGxleiBsZSBzaWdu
YWxlciBhIGwnZXhwZWRpdGV1ciBldCBsZSBkZXRydWlyZSBhaW5zaSBxdWUgbGVzIHBpZWNlcyBq
b2ludGVzLi4gTGVzIG1lc3NhZ2VzIGVsZWN0cm9uaXF1ZXMgZXRhbnQgc3VzY2VwdGlibGVzIGQn
YWx0ZXJhdGlvbiwgT3JhbmdlIGRlY2xpbmUgdG91dGUgcmVzcG9uc2FiaWxpdGUgc2kgY2UgbWVz
c2FnZSBhIGV0ZSBhbHRlcmUsIGRlZm9ybWUgb3UgZmFsc2lmaWUuIE1lcmNpLg0KPiA+DQo+ID4g
VGhpcyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVudHMgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFs
IG9yIHByaXZpbGVnZWQgaW5mb3JtYXRpb24gdGhhdCBtYXkgYmUgcHJvdGVjdGVkIGJ5IGxhdzsg
dGhleSBzaG91bGQgbm90IGJlIGRpc3RyaWJ1dGVkLCB1c2VkIG9yIGNvcGllZCB3aXRob3V0IGF1
dGhvcmlzYXRpb24uDQo+ID4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJv
ciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBtZXNzYWdlIGFuZCBp
dHMgYXR0YWNobWVudHMuDQo+ID4gQXMgZW1haWxzIG1heSBiZSBhbHRlcmVkLCBPcmFuZ2UgaXMg
bm90IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhhdCBoYXZlIGJlZW4gbW9kaWZpZWQsIGNoYW5nZWQg
b3IgZmFsc2lmaWVkLg0KPiA+IFRoYW5rIHlvdS4NCj4gPg0KPg0KDQoNCi0tDQpLYXp1aG8gT2t1
DQoNCg==

--_000_HE1PR0701MB23937DEBD284002B65CAA3EEE2EB0HE1PR0701MB2393_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxzdHlsZSB0eXBlPSJ0ZXh0L2NzcyIgc3R5bGU9
ImRpc3BsYXk6bm9uZTsiPjwhLS0gUCB7bWFyZ2luLXRvcDowO21hcmdpbi1ib3R0b206MDt9IC0t
Pjwvc3R5bGU+DQo8L2hlYWQ+DQo8Ym9keSBkaXI9Imx0ciI+DQo8ZGl2IGlkPSJkaXZ0YWdkZWZh
dWx0d3JhcHBlciIgc3R5bGU9ImZvbnQtc2l6ZToxMnB0O2NvbG9yOiMwMDAwMDA7Zm9udC1mYW1p
bHk6Q2FsaWJyaSxIZWx2ZXRpY2Esc2Fucy1zZXJpZjsiIGRpcj0ibHRyIj4NCjxwIHN0eWxlPSJt
YXJnaW4tdG9wOjA7bWFyZ2luLWJvdHRvbTowIj5JJ20gaGFwcHkgd2l0aCBlbmRwb2ludHMgaGF2
aW5nIHRoZSBwb3NzaWJpbGl0eSB0byBncmVhc2UgdGhlIGJpdCBldmVuIGZvciB0aGUgbmVnb3Rp
YXRlZCB2ZXJzaW9uLg0KPGJyPg0KPC9wPg0KPHAgc3R5bGU9Im1hcmdpbi10b3A6MDttYXJnaW4t
Ym90dG9tOjAiPlRoZSBmZXdlciBhc3N1bXB0aW9ucyBtaWRkbGVib3hlcyBtYWtlIGFib3V0IGV4
cGVjdGVkIGJlaGF2aW91ciB0aGUgYmV0dGVyLg0KPGJyPg0KPC9wPg0KPHAgc3R5bGU9Im1hcmdp
bi10b3A6MDttYXJnaW4tYm90dG9tOjAiPkZvciBhIHNwaW5ib3ggdGhlcmUncyBiYXNpY2FsbHkg
b25seSB0aHJlZSBhc3N1bXB0aW9ucyB0aGF0IGNhbiBiZSBtYWRlIHRoZW46IG5vbi1zcGluIHZl
cnNpb25zIGFyZSB1bmludGVyZXN0aW5nLCBzcGluLXZlcnNpb24ocykgbWlnaHQgYmUgaW50ZXJl
c3RpbmcsIGZsb3dzIHdpdGggdW5rbm93biB2ZXJzaW9uIG1pZ2h0IGJlIGludGVyZXN0aW5nLg0K
PGJyPg0KPC9wPg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsiPg0KPGhyIHN0eWxl
PSJkaXNwbGF5OmlubGluZS1ibG9jazt3aWR0aDo5OCUiIHRhYmluZGV4PSItMSI+DQo8ZGl2IGlk
PSJkaXZScGx5RndkTXNnIiBkaXI9Imx0ciI+PGZvbnQgc3R5bGU9ImZvbnQtc2l6ZToxMXB0IiBm
YWNlPSJDYWxpYnJpLCBzYW5zLXNlcmlmIiBjb2xvcj0iIzAwMDAwMCI+PGI+RnLDpW46PC9iPiBR
VUlDICZsdDtxdWljLWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7IGbDtnIgS2F6dWhvIE9rdSAmbHQ7a2F6
dWhvb2t1QGdtYWlsLmNvbSZndDs8YnI+DQo8Yj5Ta2lja2F0OjwvYj4gZGVuIDUgb2t0b2JlciAy
MDE4IDE2OjAwPGJyPg0KPGI+VGlsbDo8L2I+IEJyaWFuIFRyYW1tZWxsPGJyPg0KPGI+S29waWE6
PC9iPiBJRVRGIFFVSUMgV0c7IExpbGkgUGVhdWRjaGllbjsgTWlrZSBCaXNob3A7IE1hcnRlbiBT
ZWVtYW5uOyBDaHJpc3RpYW4gSHVpdGVtYTsgTWFyY3VzIElobGFyPGJyPg0KPGI+w4RtbmU6PC9i
PiBSZTogU3BpbiBiaXQgYXMgYSBuZWdvdGlhdGVkIG9wdGlvbjwvZm9udD4NCjxkaXY+Jm5ic3A7
PC9kaXY+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IkJvZHlGcmFnbWVudCI+PGZvbnQgc2l6ZT0iMiI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMXB0OyI+DQo8ZGl2IGNsYXNzPSJQbGFpblRleHQiPjIw
MTjlubQxMOaciDXml6Uo6YeRKSAyMToyNyBCcmlhbiBUcmFtbWVsbCAoSUVURikgJmx0O2lldGZA
dHJhbW1lbGwuY2gmZ3Q7Ojxicj4NCiZndDs8YnI+DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDsg
Jmd0OyBPbiA1IE9jdCAyMDE4LCBhdCAxMjo1NiwgTWFyY3VzIElobGFyICZsdDttYXJjdXMuaWhs
YXJAZXJpY3Nzb24uY29tJmd0OyB3cm90ZTo8YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsg
SSBzZWUgeW91ciBwb2ludCwgYnV0IEkgZG9uwrR0IGJlbGlldmUgaXQgaXMgYSBwYXJ0aWN1bGFy
bHkgcmVhbGlzdGljIHNjZW5hcmlvLjxicj4NCiZndDsgJmd0OyBJdCBpcyBpbiB0aGUgaW50ZXJl
c3Qgb2YgdGhlIG5ldHdvcmsgb3BlcmF0b3JzIHRvIGVuc3VyZSB0aGF0IHRoZWlyIHN1YnNjcmli
ZXJzIGhhcyBhcyBnb29kIGFuZCBjb25zaXN0ZW50IGV4cGVyaWVuY2UuPGJyPg0KJmd0OyAmZ3Q7
IEJsYWNraG9saW5nIHZlcnNpb25zIG9mIFFVSUMgaGFzIHRoZSBwb3RlbnRpYWwgb2YgY29tcGxl
dGVseSBkaXNydXB0aW5nIHNlcnZpY2VzIGFuZCBpbnRyb2R1Y2UgaW5jb25zaXN0ZW50IGJlaGF2
aW9yLjxicj4NCiZndDsgJmd0OyBUaGUgc3BpbmJpdCBpcyBpbnRlbmRlZCBhcyBhIHRvb2wgdG8g
YXNzaXN0IHRyb3VibGVzaG9vdGluZyBhbmQgcXVhbGl0eSBtb25pdG9yaW5nLiBFeHBsaWNpdGx5
IGludHJvZHVjaW5nIHBvdGVudGlhbGx5IHBvb3IgbmV0d29yayBleHBlcmllbmNlIHdpdGggdGhl
IGhvcGVzIHRoYXQgeW91ciB0cm91Ymxlc2hvb3RpbmcgLyBtb25pdG9yaW5nIGNhcGFiaWxpdGll
cyBpbXByb3ZlcyBpcyBhIHJlYWxseSBiYWQgaWRlYSwgZXZlbiBmb3IgdGhlDQogbW9zdCBjeW5p
Y2FsIG5ldHdvcmsgb3BlcmF0b3IuPGJyPg0KJmd0Ozxicj4NCiZndDsgJiM0MzsgYSB3aG9sZSBs
b3QgdG8gdGhpcy4gVHJlYXRpbmcgbWlkZGxlYm94ZXMgYXMgYSBieXphbnRpbmUgYWR2ZXJzYXJ5
IGlzIGEgdXNlZnVsIHRob3VnaHQgZXhwZXJpbWVudCB0byBkZXRlcm1pbmUgdGhlIGNvcm5lciBj
YXNlcyBpbiBhIHByb3RvY29sLCBidXQgSSBkbyBub3QgdGhpbmsgd2UgYXJlIHdlbGwgc2VydmVk
IGJ5IHRyZWF0aW5nIGFsbCBhcmJpdHJhcnkgYWltcyBhbmQgY2FwYWJpbGl0aWVzIG9uIHBhdGgg
YXMgZXF1YWxseSBsaWtlbHkuPGJyPg0KJmd0Ozxicj4NCiZndDsgQXQgdGhlIGVuZCBvZiB0aGUg
ZGF5LCBldmVyeSBvbmUgb2YgdGhlIG1pZGRsZWJveGVzIHRoYXQgd2UgY3Vyc2UgZm9yIHRoZWly
IG9zc2lmaWNhdGlvbiB3YXMgYm91Z2h0IGFuZCBzb2xkIGJlY2F1c2UgdGhlIG9wZXJhdG9yIGRl
cGxveWluZyBpdCBiZWxpZXZlZCBpdCBzb2x2ZWQgYSBwcm9ibGVtIHRoZXkgaGFkLCBzbyBhbmFs
eXppbmcgdGhlIHNwYWNlIG9mIGxpa2VseSAqaW50ZW50aW9uYWwqIGJlaGF2aW9ycyByZWR1Y2Vz
IHRvIGFuIGFuYWx5c2lzDQogb2YgdGhlIGJ1c2luZXNzIGNhc2UgZm9yIGVhY2ggb2YgdGhvc2Ug
YmVoYXZpb3JzLjxicj4NCiZndDs8YnI+DQomZ3Q7IEkgZnJhbmtseSBkb24ndCBzZWUgdGhlIGJ1
c2luZXNzIGNhc2UgZm9yIGEgc3Bpbi1iaXQtYmxvY2tpbmcgbWlkZGxlYm94IHRoYXQgd291bGRu
J3QganVzdCBibG9jayBRVUlDIHdob2xlc2FsZS48YnI+DQo8YnI+DQpJbiBhZGRpdGlvbiB0byB3
aGF0IEFsZXhhbmRyZSBhbmQgTWFyY3VzIGhhdmUgcG9pbnRlZCBvdXQsIEkgd291bGQ8YnI+DQps
aWtlIHRvIHNlY29uZCB3aGF0IEJyaWFuIGhhcyBzdGF0ZWQgaGVyZS48YnI+DQo8YnI+DQpUaGVy
ZSBhcmUgYnVzaW5lc3MtcmVsYXRlZCByZWFzb25zIHRvIHByZWZlciBUQ1Agb3ZlciBRVUlDLiBU
aGVyZSBhcmU8YnI+DQptaWRkbGVib3ggdmVuZG9ycyBzZWxsaW5nIFRDUCB0cmFmZmljLXNoYXBp
bmcgbWlkZGxlYm94ZXMgdGhhdCBjbGFpbTxicj4NCnRvIHJlZHVjZSB0aGUgY29uc3VtZWQgYmFu
ZHdpZHRoIChieSByZWR1Y2luZyB0aGUgbnVtYmVyIG9mPGJyPg0KcmV0cmFuc21pdHMsIHV0aWxp
emluZyB0aGUgaW5mb3JtYXRpb24gYWJvdXQgdGhlIGNvbmRpdGlvbiBvZiB0aGU8YnI+DQptb2Jp
bGUgbmV0d29yaykuIFRoZXJlIGFyZSAoc3RpbGwhKSBuZXR3b3JrcyB0aGF0IGdpdmUgcHJlZmVy
ZW50aWFsPGJyPg0KdHJlYXRtZW50IHRvIG5vbi1UTFMgSFRUUCBiZWNhdXNlIHRoZXkgY2FuIGRl
cGxveSB0cmFuc3BhcmVudCw8YnI+DQpjb21wcmVzc2luZyBwcm94aWVzLjxicj4NCjxicj4NCkNv
bXBhcmVkIHRvIHRob3NlIGNhc2VzLCBzcGluIGJpdCBoYXMgdmVyeSB3ZWFrIHJlYXNvbiBmb3I8
YnI+DQpwcmVmZXJlbnRpYWwgdHJlYXRtZW50IChpLmUuIHRyb3VibGVzaG9vdGluZyBhbmQgcXVh
bGl0eSBtb25pdG9yaW5nKS48YnI+DQo8YnI+DQpCZXNpZGVzLCB0aGUgZW5kcG9pbnRzIHdvdWxk
IGFsc28gaGF2ZSB0aGUgY2hvaWNlIHRvIGV4cG9zZSBmYWtlPGJyPg0Kc2lnbmFsIG9uY2Ugd2Ug
c3RhcnQgc2VlaW5nIG5ldHdvcmtzIGJsb2NraW5nIFFVSUMgd2l0aG91dCB0aGUgc3Bpbjxicj4N
CmJpdC4gQWN0dWFsbHksIHRoYXQgaXMgdGhlIHN0YXR1cy1xdW8sIGluIHdoaWNoIHdlIGRvIG5v
dCBoYXZlIGFueTxicj4NCm5lZ290aWF0aW9uLiBUbyBwdXQgaXQgdGhlIG90aGVyIHdheSwgdGhl
IGVuZHBvaW50cyBsb3NlIG5vdGhpbmcgYnk8YnI+DQp1c2luZyB0aGUgdmVyc2lvbiBudW1iZXIg
ZmllbGQgZm9yIGV4cG9zaW5nIHRoZSBhdmFpbGFiaWxpdHkgb2YgdGhlPGJyPg0Kc2lnbmFsLjxi
cj4NCjxicj4NCiZndDsgQnV0IEknbSBub3QgYSBtaWRkbGVib3ggdmVuZG9yLCBzbyBtYXliZSBJ
J20ganVzdCBtaXNzaW5nIHNvbWV0aGluZy48YnI+DQomZ3Q7PGJyPg0KJmd0OyBOb3csIHRoZXJl
IG1heSBiZSBzb21lICp1bmludGVudGlvbmFsKiBicmVha2FnZSBiZWNhdXNlIHNvbWUgbWlkZGxl
Ym94IHZlbmRvciBvbmx5IGhhcHBlbnMgdG8gYW5hbHl6ZSB0cmFmZmljIHRoYXQgc3BpbnMgd2hl
biB0cnlpbmcgdG8gcmV2ZXJzZS1lbmdpbmVlciBRVUlDLCBhbmQgZGVjaWRlcyB0aGF0IHRoZSBu
b24tc3Bpbm5pbmcgdmVyc2lvbiBpcyBqdXN0IGdyZWFzZSBhbmQgYmxvY2tzIGl0LiBCdXQgdGhh
dCBzZWVtcyB0byBtZSB0bw0KIGJlIG1vcmUgYW4gYXJndW1lbnQgdG8gcm9idXN0bHkgZXhlcmNp
c2UgdmVyc2lvbiBuZWdvdGlhdGlvbiBmcm9tIGRheSBvbmUgdGhhbiBhbnl0aGluZyBlbHNlLjxi
cj4NCiZndDs8YnI+DQomZ3Q7IENoZWVycyw8YnI+DQomZ3Q7PGJyPg0KJmd0OyBCcmlhbjxicj4N
CiZndDs8YnI+DQomZ3Q7ICZndDsgRnJvbTogTWFydGVuIFNlZW1hbm4gJmx0O21hcnRlbnNlZW1h
bm5AZ21haWwuY29tJmd0Ozxicj4NCiZndDsgJmd0OyBTZW50OiBkZW4gNSBva3RvYmVyIDIwMTgg
MTI6MzM8YnI+DQomZ3Q7ICZndDsgVG86IE1hcmN1cyBJaGxhciAmbHQ7bWFyY3VzLmlobGFyQGVy
aWNzc29uLmNvbSZndDs8YnI+DQomZ3Q7ICZndDsgQ2M6IGFsZXhhbmRyZS5mZXJyaWV1eEBvcmFu
Z2UuY29tOyBodWl0ZW1hQGh1aXRlbWEubmV0OyBpZXRmQHRyYW1tZWxsLmNoOyBrYXp1aG9va3VA
Z21haWwuY29tOyBtYmlzaG9wQGV2ZXF1ZWZvdS5iZTsgcXVpY0BpZXRmLm9yZzxicj4NCiZndDsg
Jmd0OyBTdWJqZWN0OiBSZTogU3BpbiBiaXQgYXMgYSBuZWdvdGlhdGVkIG9wdGlvbjxicj4NCiZn
dDsgJmd0Ozxicj4NCiZndDsgJmd0OyBUaGUgcHJvYmxlbSB3aXRoIHVzaW5nIGEgc3BlY2lmaWMg
dmVyc2lvbiBmb3IgaW1wbGVtZW50YXRpb25zIHRoYXQgdXNlIGFuZCBkb27igJl0IHVzZSB0aGUg
c3BpbiBiaXQgaXMgdGhhdCBtaWRkbGVib3hlcyBjYW4gZWZmZWN0aXZlbHkgZW5mb3JjZSB1c2Fn
ZSBvZiB0aGUgc3BpbiBiaXQgdmVyc2lvbiBieSBibGFja2hvbGluZyBldmVyeSBwYWNrZXQgYWR2
ZXJ0aXNpbmcgYSB2ZXJzaW9uIHRoYXQgZG9lc27igJl0IHVzZSB0aGUgc3BpbiBiaXQuDQogSWYg
b25seSBhIGZldyBtaWRkbGVib3hlcyBkbyB0aGF0LCB0aGlzIHdvdWxkIGZvcmNlICphbGwqIGlt
cGxlbWVudGF0aW9ucyB0byBhdm9pZCB0aGVzZSB2ZXJzaW9ucy48YnI+DQomZ3Q7ICZndDsgSW1w
bGVtZW50YXRpb25zIHRoYXQgZG9u4oCZdCB3YW50IHRvIGV4cG9zZSB0aGVpciBSVFQgd291bGQg
dGhlbiBoYXZlIHRvIG5lZ290aWF0ZSBhIHZlcnNpb24gdGhhdCBpcyBzdXBwb3NlZCB0byB1c2Ug
dGhlIHNwaW4gYml0LCBidXQgdGhlbiBncmVhc2UgdGhlIGNvcnJlc3BvbmRpbmcgYml0cyBpbiBv
cmRlciB0byBwcmVzZXJ2ZSB0aGVpciBwcml2YWN5LiBPZiBjb3Vyc2UsIHRoaXMgd291bGQgb25s
eSB3b3JrIGlmIHRoZSBwZWVyIGRvZXNu4oCZdA0KIGVuZm9yY2UgY29tcGxpYW5jZS4gT3RoZXJ3
aXNlLCB3ZeKAmWxsIGVuZCB1cCBpbiBhIHdvcmxkIHdoZXJlIGl04oCZcyBiYXNpY2FsbHkgaW1w
b3NzaWJsZSB0byBvcHQtb3V0IG9mIHRoZSBzcGluLWJpdC48YnI+DQomZ3Q7ICZndDs8YnI+DQom
Z3Q7ICZndDsgT24gRnJpLCBPY3QgNSwgMjAxOCBhdCAxMjoxNSBNYXJjdXMgSWhsYXIgJmx0O21h
cmN1cy5paGxhckBlcmljc3Nvbi5jb20mZ3Q7IHdyb3RlOjxicj4NCiZndDsgJmd0OyBIaSw8YnI+
DQomZ3Q7ICZndDsgSSBsaWtlIHRoaXMgYXBwcm9hY2ggc2luY2UgaXQgYWxsb3dzIHVzIHRvIGRp
c3JlZ2FyZCBub24tc3Bpbm5pbmcgZmxvd3MgYnkgc2ltcGx5IG9ic2VydmluZyB0aGUgaW5pdGlh
bCBoYW5kc2hha2UuIFRoaXMgc2F2ZXMgdXMgcXVpdGUgc29tZSB3b3JrLjxicj4NCiZndDsgJmd0
OyBPbiB0aGUgaGV1cmlzdGljcyBwYXJ0LCB3ZSBjYW5ub3QgZ2V0IGF3YXkgZnJvbSBpdCwgZXZl
biBpZiB3ZSBzZWUgdGhlIHNwaW4gdmVyc2lvbiBpbiB0aGUgaW5pdGlhbCBoYW5kc2hha2UgYXMg
dGhlcmXCtHMgbm8gZ3VhcmFudGVlIHRoYXQgYW4gZW5kcG9pbnQgd2lsbCBzZXQgdGhlIGJpdCBw
cm9wZXJseSBhbnl3YXkuPGJyPg0KJmd0OyAmZ3Q7IEhvd2V2ZXIsIGZvciB0aGUgdmVyc2lvbiB3
aGVyZSB0aGUgaW50ZW50IHRvIHVzZSBzcGluYml0IGlzIGV4cGxpY2l0IGl0IGFjdHVhbGx5IG1h
a2VzIHNlbnNlIGZvciBhbiBlbmRwb2ludCB0byB0cmVhdCBub24tcGFydGljaXBhdGluZyBiZWhh
dmlvciBhcyBhIHByb3RvY29sIGVycm9yLjxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyBN
YXJjdXM8YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgLS0tLS1PcmlnaW5hbCBNZXNzYWdl
LS0tLS08YnI+DQomZ3Q7ICZndDsgRnJvbTogUVVJQyAmbHQ7cXVpYy1ib3VuY2VzQGlldGYub3Jn
Jmd0OyBPbiBCZWhhbGYgT2YgTWlrZSBCaXNob3A8YnI+DQomZ3Q7ICZndDsgU2VudDogZGVuIDUg
b2t0b2JlciAyMDE4IDAwOjQwPGJyPg0KJmd0OyAmZ3Q7IFRvOiBhbGV4YW5kcmUuZmVycmlldXhA
b3JhbmdlLmNvbTsgS2F6dWhvIE9rdSAmbHQ7a2F6dWhvb2t1QGdtYWlsLmNvbSZndDs8YnI+DQom
Z3Q7ICZndDsgQ2M6IEJyaWFuIFRyYW1tZWxsICZsdDtpZXRmQHRyYW1tZWxsLmNoJmd0OzsgSUVU
RiBRVUlDIFdHICZsdDtxdWljQGlldGYub3JnJmd0OzsgQ2hyaXN0aWFuIEh1aXRlbWEgJmx0O2h1
aXRlbWFAaHVpdGVtYS5uZXQmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IFN1YmplY3Q6IFJFOiBTcGluIGJp
dCBhcyBhIG5lZ290aWF0ZWQgb3B0aW9uPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IFNv
IGxvbmcgYXMgdGhpcyBpcyB0aGUgb25seSB0aGluZyBiZWluZyBuZWdvdGlhdGVkLCBpdCdzIG5v
dCB0b28gYmFkLiZuYnNwOyBJZiB3ZSB3YW50IHRvIG5lZ290aWF0ZSBvdGhlciB0aGluZ3MsIGl0
IHF1aWNrbHkgZ2V0cyBvdXQgb2YgaGFuZC4mbmJzcDsgT25lIGNvdWxkIHBsYXVzaWJseSBhcmd1
ZSB0aGF0IHRoZSBzcGluIGJpdCBpcyBzcGVjaWFsIGluIHRoYXQgd2UgYWN0dWFsbHkgd2FudCBw
YXJ0aWVzIG9ic2VydmluZyB0aGUgdHJhbnNhY3Rpb24NCiB0byB1bmRlcnN0YW5kIHdoaWNoIG9w
dGlvbiBoYXMgYmVlbiBzZWxlY3RlZC48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgSXQn
cyBpbXBvcnRhbnQgdG8gcmVtZW1iZXIsIHRob3VnaCwgdGhhdCB0aGlzIGlzIGluZm9ybWF0aW9u
IHlvdSBnZXQgb25seSBhdCB0aGUgYmVnaW5uaW5nIG9mIGEgbmV3IGNvbm5lY3Rpb24uJm5ic3A7
IElmIHRoZXJlJ3MgbWlncmF0aW9uIG9yIE5BVCByZWJpbmRpbmcsIGl0J3Mgbm90IGd1YXJhbnRl
ZWQgKGFuZCBpbiBmYWN0LCBub3QgaW50ZW5kZWQpIHRoYW4geW91IGNhbiBjb3JyZWxhdGUgaXQg
YmFjayB0byBhIHBhcnRpY3VsYXIgcHJldmlvdXMNCiBoYW5kc2hha2UuJm5ic3A7IFlvdSdsbCBz
dGlsbCBlaXRoZXIgbmVlZCBoZXVyaXN0aWNzIHRvIGlkZW50aWZ5IHdoZXRoZXIgdGhlIHNwaW4g
Yml0IGlzIGFjdHVhbGx5IGluIHVzZSwgb3IgeW91J2xsIG5lZWQgdG8gaWdub3JlIGFueSB0cmFm
ZmljIGZvciB3aGljaCB5b3UgZGlkbid0IHNlZSB0aGUgaGFuZHNoYWtlLjxicj4NCiZndDsgJmd0
Ozxicj4NCiZndDsgJmd0OyAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCiZndDsgJmd0
OyBGcm9tOiBRVUlDICZsdDtxdWljLWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7IE9uIEJlaGFsZiBPZiBh
bGV4YW5kcmUuZmVycmlldXhAb3JhbmdlLmNvbTxicj4NCiZndDsgJmd0OyBTZW50OiBUaHVyc2Rh
eSwgT2N0b2JlciA0LCAyMDE4IDM6NDcgQU08YnI+DQomZ3Q7ICZndDsgVG86IEthenVobyBPa3Ug
Jmx0O2thenVob29rdUBnbWFpbC5jb20mZ3Q7PGJyPg0KJmd0OyAmZ3Q7IENjOiBCcmlhbiBUcmFt
bWVsbCAmbHQ7aWV0ZkB0cmFtbWVsbC5jaCZndDs7IElFVEYgUVVJQyBXRyAmbHQ7cXVpY0BpZXRm
Lm9yZyZndDs7IENocmlzdGlhbiBIdWl0ZW1hICZsdDtodWl0ZW1hQGh1aXRlbWEubmV0Jmd0Ozxi
cj4NCiZndDsgJmd0OyBTdWJqZWN0OiBSZTogU3BpbiBiaXQgYXMgYSBuZWdvdGlhdGVkIG9wdGlv
bjxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyBUaGFua3MgS2F6dWhvLiBVc2luZyB2ZXJz
aW9uIG51bWJlcnMgZGlyZWN0bHkgd2FzIGFuIG9idmlvdXMgY2hvaWNlLCBidXQgc28gZmFyIEkg
d2FzIGRpc2NvdXJhZ2VkIGJ5IHN0cm9uZyBsYW5ndWFnZSBpbiB0aGUgc3BlYywgc2F5aW5nIDB4
MDAwMDAwMDEgd2FzIHRoZSB1bmF2b2lkYWJsZSBwb2ludCBvZiBjb252ZXJnZW5jZSBhZnRlciBh
bGwgMHhGRjAwMDBYWCBleHBlcmltZW50cy4uIFNvIGluIGVzc2VuY2UgeW91J3JlIHByb3Bvc2lu
Zw0KIHRvIHdlYWtlbiB0aGF0IGEgYml0LCByaWdodCA/PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0
OyAmZ3Q7IElmIHNvLCBob3cgZG8geW91IGVudmlzaW9uIHNlZ21lbnRpbmcgdGhlIHZlcnNpb24g
bnVtYmVyIHNwYWNlID88YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsmbmJzcDsmbmJzcDsg
LSBkaXJlY3QgZW51bWVyYXRpb246PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDB4MDAwMDAwMDEgPSB2
MWRyeTxicj4NCiZndDsgJmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyAweDAwMDAwMDAyID0gdjEgJiM0Mzsgc3BpbmJpdDxicj4NCiZndDsgJmd0OyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAweDAwMDAwMDAz
ID0gdjEgJiM0Mzsgc3BpbmJpdCAmIzQzOyBWRUM8YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZn
dDsmbmJzcDsmbmJzcDsgLSBsb3cgb3JkZXIgYml0cyBmb3Igb3B0aW9uczo8YnI+DQomZ3Q7ICZn
dDs8YnI+DQomZ3Q7ICZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgMHgwMDAwMDFYWCA9IHYxICYjNDM7IG9wdGlvbiBYWDxicj4NCiZndDsgJmd0OyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAweDAwMDAwMllZ
ID0gdjIgJiM0Mzsgb3B0aW9uIFlZPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IEFsc28s
IGFyZSB3ZSBzdXJlIHRoYXQgdGhpcyBleHBsb3Npb24gd29uJ3Qgd2VpZ2ggb24gdGhlIG5ldyBW
TiBzY2hlbWUsIGluZHVjaW5nIHNsb3dlciBjb252ZXJnZW5jZSBkdWUgdG8gbG9uZ2VyIGxpc3Rz
IG9uIGVpdGhlciBzaWRlID88YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgT24gMTAvMDQv
MTggMTE6NTAsIEthenVobyBPa3Ugd3JvdGU6PGJyPg0KJmd0OyAmZ3Q7ICZndDsgSGksPGJyPg0K
Jmd0OyAmZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgJmd0OyBUaGFuayB5b3UgZm9yIHN0YXJ0aW5n
IHRoZSBkaXNjdXNzaW9uIHNwZWNpZmljIHRvIGhvdyB3ZSBjb3VsZDxicj4NCiZndDsgJmd0OyAm
Z3Q7IHBvc3NpYmx5IG5lZ290aWF0ZSB0aGUgdXNlIG9mIHNwaW4gYml0cy48YnI+DQomZ3Q7ICZn
dDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7IFJlZ2FyZGluZyB0aGUgdG9waWMsIG15IHByZWZl
cmVuY2UgZ29lcyB0byB1c2luZyB0aGUgdmVyc2lvbiBudW1iZXI8YnI+DQomZ3Q7ICZndDsgJmd0
OyBmaWVsZCBvZiB0aGUgbG9uZyBoZWFkZXIgZm9yIG5lZ290aWF0aW5nIHRoZSBwcmVzZW5jZSBv
ZiBzcGluIGJpdHMsIG9yPGJyPg0KJmd0OyAmZ3Q7ICZndDsgYW55IGFkZGl0aW9uYWwgc2lnbmFs
IGJlaW5nIGV4cG9zZWQgdG8gdGhlIG5ldHdvcmsuPGJyPg0KJmd0OyAmZ3Q7ICZndDs8YnI+DQom
Z3Q7ICZndDsgJmd0OyBGb3IgZXhhbXBsZSwgUVVJQ3YxIHdpdGhvdXQgc3BpbiBiaXQgY291bGQg
dXNlIHZlcnNpb24gMHgxMDEsIGFuZCB2MTxicj4NCiZndDsgJmd0OyAmZ3Q7IHdpdGggc3BpbiBi
aXQgY291bGQgdXNlIDB4MTAyLiBJbiB0aGUgZnV0dXJlLCB3ZSBjYW4gYXNzaWduIGE8YnI+DQom
Z3Q7ICZndDsgJmd0OyBkaWZmZXJlbnQgdmVyc2lvbiBudW1iZXIgZm9yIFFVSUN2MSB3aXRoIG11
bHRpcGxlIHNwaW4gJiM0MzsgVkVDIChvcjxicj4NCiZndDsgJmd0OyAmZ3Q7IHBlb3BsZSBpbnRl
cmVzdGVkIGluIHRlc3RpbmcgdGhlIGZlYXR1cmUgY2FuIGRlc2lnbmF0ZSBhIHByaXZhdGU8YnI+
DQomZ3Q7ICZndDsgJmd0OyB2ZXJzaW9uIG51bWJlciBldmVuIGJlZm9yZSB0aGF0KS48YnI+DQom
Z3Q7ICZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7IEkgc2VlIHRoZSBmb2xsb3dpbmcgYmVu
ZWZpdHMgdG8gdXNpbmcgdGhlIHZlcnNpb24gZmllbGQgYXMgYSBtZXRob2QgdG88YnI+DQomZ3Q7
ICZndDsgJmd0OyBuZWdvdGlhdGUgdGhlIHVzZSBvZiBzcGluIGJpdHMuPGJyPg0KJmd0OyAmZ3Q7
ICZndDs8YnI+DQomZ3Q7ICZndDsgJmd0OyAxLiBPbmUgb2YgdGhlIGNvbmNlcm4gcmVnYXJkaW5n
IHNwaW4gYml0cyBoYXMgYmVlbiB0aGF0IHRoZXkgY291bGQ8YnI+DQomZ3Q7ICZndDsgJmd0OyBs
ZWFkIHRvIG9zc2lmaWNhdGlvbi4gU3BpbiBiaXRzIGFyZSBub3QgcGFydCBvZiB0aGUgSW52YXJp
YW50cywgYnV0IGlmPGJyPg0KJmd0OyAmZ3Q7ICZndDsgdGhlIG9ic2VydmF0aW9uIHRvb2xzIHN0
YXJ0IGxvb2tpbmcgYXQgdGhvc2UgYml0cyB3aXRob3V0IGNoZWNraW5nIHRoZTxicj4NCiZndDsg
Jmd0OyAmZ3Q7IHZlcnNpb24gbnVtYmVyIGZpZWxkLCB3ZSB3aWxsIGhhdmUgdGhlIHByZXNzdXJl
IHRvIG5vdCBjaGFuZ2UgaG93IHRoZTxicj4NCiZndDsgJmd0OyAmZ3Q7IGJpdHMgYXJlIHVzZWQu
IFVzaW5nIHRoZSB2ZXJzaW9uIG51bWJlciB0byBpbmRpY2F0ZSB0aGUgcHJlc2VuY2Ugb2Y8YnI+
DQomZ3Q7ICZndDsgJmd0OyBzcGluIGJpdHMgaXMgdGhlIGJlc3QgYXBwcm9hY2ggdG8gcmVzb2x2
ZSBzdWNoIGNvbmNlcm4uPGJyPg0KJmd0OyAmZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgJmd0OyAy
LiBXZSBoYXZlIGhvcGVkIHRvIHJvbGwgb3V0IG11bHRpcGxlIHZlcnNpb25zIG9mIFFVSUMgaW4g
YSBzbWFsbDxicj4NCiZndDsgJmd0OyAmZ3Q7IGludGVydmFsIHNvIHRoYXQgdGhlIHZlcnNpb24g
bnVtYmVyIGZpZWxkIGRvZXMgbm90IGdldCBvc3NpZmllZC4gVGhlPGJyPg0KJmd0OyAmZ3Q7ICZn
dDsgYmVzdCBzb2x1dGlvbiBpcyBvYnZpb3VzbHkgdG8gcm9sbCBvdXQgdHdvIGZsYXZvcnMgb2Yg
dGhlIHByb3RvY29sPGJyPg0KJmd0OyAmZ3Q7ICZndDsgdGhhdCB1c2VzIGRpZmZlcmVudCB2ZXJz
aW9uIG51bWJlcnMgYXQgdGhlIHNhbWUgdGltZS4gV2Ugd2lsbCBoYXZlIGE8YnI+DQomZ3Q7ICZn
dDsgJmd0OyByZWFsLXdvcmxkIHVzZSBvZiB2ZXJzaW9uIG5lZ290aWF0aW9uIGZyb20gZGF5IG9u
ZSwgYmVjYXVzZSB3ZSBhcmUgaW48YnI+DQomZ3Q7ICZndDsgJmd0OyBhIGNvbmRpdGlvbiB3aGVy
ZSBpbXBsZW1lbnRvcnMgaGF2ZSBkaWZmZXJlbnQgb3BpbmlvbnMgb24gaWYgdGhleTxicj4NCiZn
dDsgJmd0OyAmZ3Q7IHNob3VsZCBzdXBwb3J0IHNwaW4gYml0IDotKTxicj4NCiZndDsgJmd0OyAm
Z3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsgVGhlIGJsb2NrZXIgdG8gdGhpcyBhcHByb2FjaCBoYXMg
YmVlbiB2ZXJzaW9uIG5lZ290aWF0aW9uIHJlcXVpcmluZyBhbjxicj4NCiZndDsgJmd0OyAmZ3Q7
IGFkZGl0aW9uYWwgcm91bmQtdHJpcCwgYnV0IHRoYXQgaXMgZ29pbmcgdG8gYmUgcmVzb2x2ZWQg
YnkgIzE3NTUuPGJyPg0KJmd0OyAmZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgJmd0OyAyMDE45bm0
MTDmnIgz5pelKOawtCkgMTk6MDYgJmx0O2FsZXhhbmRyZS5mZXJyaWV1eEBvcmFuZ2UuY29tJmd0
Ozo8YnI+DQomZ3Q7ICZndDsgJmd0OyZndDs8YnI+DQomZ3Q7ICZndDsgJmd0OyZndDsgT24gMTAv
MDMvMTggMDk6NTgsIEJyaWFuIFRyYW1tZWxsIChJRVRGKSB3cm90ZTo8YnI+DQomZ3Q7ICZndDsg
Jmd0OyZndDsgJmd0OyBCYWNraW5nIG9mZiB0aGUgTVVTVCBmb3Igbm93IGZvciBzdWNoIHNpdHVh
dGlvbnMgaXMgSU1PIGEgZ29vZDxicj4NCiZndDsgJmd0OyAmZ3Q7Jmd0OyAmZ3Q7IHRyYWRlb2Zm
LCB0aG91Z2gsIGVzcGVjaWFsbHkgc2luY2Ugd2Ugb25seSBuZWVkIGZyYWN0aW9ucyBvZiBhPGJy
Pg0KJmd0OyAmZ3Q7ICZndDsmZ3Q7ICZndDsgcGVyY2VudCBvZiBkZXBsb3ltZW50IHRvIHN0YXJ0
IHNlZWluZyB1c2VmdWwgc2lnbmFsIGZvcjxicj4NCiZndDsgJmd0OyAmZ3Q7Jmd0OyAmZ3Q7IGJh
c2VsaW5lL2Fub21hbHkgbWVhc3VyZW1lbnQgb2YgbGFyZ2UgYWdncmVnYXRlcy48YnI+DQomZ3Q7
ICZndDsgJmd0OyZndDs8YnI+DQomZ3Q7ICZndDsgJmd0OyZndDsgSWYgdGhlIGNvbnNlbnN1cyBp
cyB0aGF0IHdlIG11c3QgYWxsb3cgZm9yIHN1Y2ggc2l0dWF0aW9ucywgdGhlbjxicj4NCiZndDsg
Jmd0OyAmZ3Q7Jmd0OyB0aGVyZSBhcmUgdHdvPGJyPg0KJmd0OyAmZ3Q7ICZndDsmZ3Q7IHBvc3Np
YmlsaXRpZXM6PGJyPg0KJmd0OyAmZ3Q7ICZndDsmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsmZ3Q7
Jm5ic3A7Jm5ic3A7IChhKSB3ZWFrIHNwZWMgbGFuZ3VhZ2UgKE1BWSBXSVNIIFRPIG9yIHNpbWls
YXIpID0mZ3Q7IG1hbnk8YnI+DQomZ3Q7ICZndDsgJmd0OyZndDsgaW1wbGVtZW50YXRpb25zIHdp
bGwgc2ltcGx5IGRyb3AgaXQ8YnI+DQomZ3Q7ICZndDsgJmd0OyZndDs8YnI+DQomZ3Q7ICZndDsg
Jmd0OyZndDsmbmJzcDsmbmJzcDsgKGIpIG5lZ290aWF0ZWQgb3B0aW9uIHdoZXJlIHRoZSBuZWdv
dGlhdGlvbiBtZWNoYW5pc20gaXMgbWFuZGF0b3J5PGJyPg0KJmd0OyAmZ3Q7ICZndDsmZ3Q7PGJy
Pg0KJmd0OyAmZ3Q7ICZndDsmZ3Q7IEluIHRoZSB2ZWluIG9mIChiKSwgQ2hyaXN0aWFuIHN1Z2dl
c3RlZCBvZmZsaW5lIHRvIGludHJvZHVjZTxicj4NCiZndDsgJmd0OyAmZ3Q7Jmd0OyBuZWdvdGlh
dGlvbiB0byBhbGxvdyBmb3IgZXhwZXJpbWVudGF0aW9uIG9mIHRoZSByZW1haW5pbmcgdHdvPGJy
Pg0KJmd0OyAmZ3Q7ICZndDsmZ3Q7IHJlc2VydmVkIGJpdHMuIFRoZW4gbWF5IGJlIHdlIGNhbiBz
eW50aGVzaXplIGJvdGggaWRlYXMgYnkgdGhlIGZvbGxvd2luZyBwcm9wb3NhbDo8YnI+DQomZ3Q7
ICZndDsgJmd0OyZndDs8YnI+DQomZ3Q7ICZndDsgJmd0OyZndDsmbmJzcDsmbmJzcDsgLSBpbiB0
aGUgZmlyc3QgZmV3IGV4Y2hhbmdlcyBvZiB0aGUgNS10dXBsZSwgdXNlIHRoZSB0aHJlZSBiaXRz
IGZvcjxicj4NCiZndDsgJmd0OyAmZ3Q7Jmd0OyBvcHRpb24gbmVnb3RpYXRpb248YnI+DQomZ3Q7
ICZndDsgJmd0OyZndDs8YnI+DQomZ3Q7ICZndDsgJmd0OyZndDsmbmJzcDsmbmJzcDsgLSB0aGVu
IHVzZSB0aGVtIGFzIGRlZmluZWQgYnkgdGhlIHNlbGVjdGVkIG9wdGlvbjxicj4NCiZndDsgJmd0
OyAmZ3Q7Jmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7Jmd0OyBFeGFtcGxlIGVuY29kaW5nczo8YnI+
DQomZ3Q7ICZndDsgJmd0OyZndDs8YnI+DQomZ3Q7ICZndDsgJmd0OyZndDsmbmJzcDsmbmJzcDsg
MDAwIDogbm90aGluZzxicj4NCiZndDsgJmd0OyAmZ3Q7Jmd0OyZuYnNwOyZuYnNwOyAwMDEgOiBz
cGluIGJpdCBhbG9uZSA6IFMwMDxicj4NCiZndDsgJmd0OyAmZ3Q7Jmd0OyZuYnNwOyZuYnNwOyAw
MTAgOiBzcGluIGJpdCAmIzQzOyBWRUMgOiBTVlY8YnI+DQomZ3Q7ICZndDsgJmd0OyZndDsmbmJz
cDsmbmJzcDsgLi4uIDogb3RoZXIgZXh0ZW5zaW9uczxicj4NCiZndDsgJmd0OyAmZ3Q7Jmd0Ozxi
cj4NCiZndDsgJmd0OyAmZ3Q7Jmd0OyBUaGUgbmVnb3RpYXRpb24gbWVjaGFuaXNtIGFsbG93cyBi
b3RoIGVuZHBvaW50cyB0byBmb3JjZSAwMDAuPGJyPg0KJmd0OyAmZ3Q7ICZndDsmZ3Q7IEFuZCBz
aW5jZSBpdCBpcyBpbiB0aGUgY2xlYXIgZmlyc3QgYnl0ZSwgaXQgYWxsb3dzIG9uLXBhdGggb2Jz
ZXJ2ZXJzPGJyPg0KJmd0OyAmZ3Q7ICZndDsmZ3Q7IHRvIGlkZW50aWZ5IHRoZSBvcHRpb24gd2l0
aG91dCByZXNvcnRpbmcgdG8gaGV1cmlzdGljczsgdGhpcyBoZWxwcyBpbjxicj4NCiZndDsgJmd0
OyAmZ3Q7Jmd0OyB0aGUgY2FzZSBvZiBhIHNtYWxsIHN1cHBvcnQgcmF0aW8uPGJyPg0KJmd0OyAm
Z3Q7ICZndDsmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsm
Z3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsmZ3Q7IF9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXzxicj4NCiZndDsgJmd0OyAmZ3Q7Jmd0OyBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KJmd0OyAmZ3Q7ICZndDsmZ3Q7PGJyPg0K
Jmd0OyAmZ3Q7ICZndDsmZ3Q7IENlIG1lc3NhZ2UgZXQgc2VzIHBpZWNlcyBqb2ludGVzIHBldXZl
bnQgY29udGVuaXIgZGVzIGluZm9ybWF0aW9uczxicj4NCiZndDsgJmd0OyAmZ3Q7Jmd0OyBjb25m
aWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVzIGV0IG5lIGRvaXZlbnQgZG9uYyBwYXMgZXRyZSBk
aWZmdXNlcyw8YnI+DQomZ3Q7ICZndDsgJmd0OyZndDsgZXhwbG9pdGVzIG91IGNvcGllcyBzYW5z
IGF1dG9yaXNhdGlvbi4gU2kgdm91cyBhdmV6IHJlY3UgY2UgbWVzc2FnZTxicj4NCiZndDsgJmd0
OyAmZ3Q7Jmd0OyBwYXIgZXJyZXVyLCB2ZXVpbGxleiBsZSBzaWduYWxlciBhIGwnZXhwZWRpdGV1
ciBldCBsZSBkZXRydWlyZSBhaW5zaSBxdWUgbGVzIHBpZWNlcyBqb2ludGVzLiBMZXMgbWVzc2Fn
ZXMgZWxlY3Ryb25pcXVlcyBldGFudCBzdXNjZXB0aWJsZXMgZCdhbHRlcmF0aW9uLCBPcmFuZ2Ug
ZGVjbGluZSB0b3V0ZSByZXNwb25zYWJpbGl0ZSBzaSBjZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwg
ZGVmb3JtZSBvdSBmYWxzaWZpZS4gTWVyY2kuPGJyPg0KJmd0OyAmZ3Q7ICZndDsmZ3Q7PGJyPg0K
Jmd0OyAmZ3Q7ICZndDsmZ3Q7IFRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRzIG1heSBj
b250YWluIGNvbmZpZGVudGlhbCBvcjxicj4NCiZndDsgJmd0OyAmZ3Q7Jmd0OyBwcml2aWxlZ2Vk
IGluZm9ybWF0aW9uIHRoYXQgbWF5IGJlIHByb3RlY3RlZCBieSBsYXc7IHRoZXkgc2hvdWxkIG5v
dCBiZSBkaXN0cmlidXRlZCwgdXNlZCBvciBjb3BpZWQgd2l0aG91dCBhdXRob3Jpc2F0aW9uLjxi
cj4NCiZndDsgJmd0OyAmZ3Q7Jmd0OyBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGlu
IGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIG1lc3NhZ2Ug
YW5kIGl0cyBhdHRhY2htZW50cy48YnI+DQomZ3Q7ICZndDsgJmd0OyZndDsgQXMgZW1haWxzIG1h
eSBiZSBhbHRlcmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhhdCBoYXZl
IGJlZW4gbW9kaWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVkLjxicj4NCiZndDsgJmd0OyAmZ3Q7
Jmd0OyBUaGFuayB5b3UuPGJyPg0KJmd0OyAmZ3Q7ICZndDsmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZn
dDs8YnI+DQomZ3Q7ICZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4N
CiZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0
OyAmZ3Q7IENlIG1lc3NhZ2UgZXQgc2VzIHBpZWNlcyBqb2ludGVzIHBldXZlbnQgY29udGVuaXIg
ZGVzIGluZm9ybWF0aW9ucyBjb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVzIGV0IG5lIGRv
aXZlbnQgZG9uYyBwYXMgZXRyZSBkaWZmdXNlcywgZXhwbG9pdGVzIG91IGNvcGllcyBzYW5zIGF1
dG9yaXNhdGlvbi4gU2kgdm91cyBhdmV6IHJlY3UgY2UgbWVzc2FnZSBwYXIgZXJyZXVyLCB2ZXVp
bGxleiBsZSBzaWduYWxlciBhIGwnZXhwZWRpdGV1cg0KIGV0IGxlIGRldHJ1aXJlIGFpbnNpIHF1
ZSBsZXMgcGllY2VzIGpvaW50ZXMuLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25pcXVlcyBldGFudCBz
dXNjZXB0aWJsZXMgZCdhbHRlcmF0aW9uLCBPcmFuZ2UgZGVjbGluZSB0b3V0ZSByZXNwb25zYWJp
bGl0ZSBzaSBjZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBmYWxzaWZpZS4gTWVy
Y2kuPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IFRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0
dGFjaG1lbnRzIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBvciBwcml2aWxlZ2VkIGluZm9ybWF0
aW9uIHRoYXQgbWF5IGJlIHByb3RlY3RlZCBieSBsYXc7IHRoZXkgc2hvdWxkIG5vdCBiZSBkaXN0
cmlidXRlZCwgdXNlZCBvciBjb3BpZWQgd2l0aG91dCBhdXRob3Jpc2F0aW9uLjxicj4NCiZndDsg
Jmd0OyBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVhc2Ugbm90
aWZ5IHRoZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50
cy48YnI+DQomZ3Q7ICZndDsgQXMgZW1haWxzIG1heSBiZSBhbHRlcmVkLCBPcmFuZ2UgaXMgbm90
IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhhdCBoYXZlIGJlZW4gbW9kaWZpZWQsIGNoYW5nZWQgb3Ig
ZmFsc2lmaWVkLjxicj4NCiZndDsgJmd0OyBUaGFuayB5b3UuPGJyPg0KJmd0OyAmZ3Q7PGJyPg0K
Jmd0Ozxicj4NCjxicj4NCjxicj4NCi0tIDxicj4NCkthenVobyBPa3U8YnI+DQo8YnI+DQo8L2Rp
dj4NCjwvc3Bhbj48L2ZvbnQ+PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1s
Pg0K

--_000_HE1PR0701MB23937DEBD284002B65CAA3EEE2EB0HE1PR0701MB2393_--


From nobody Sat Oct  6 17:45:31 2018
Return-Path: <do_not_reply@mnot.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 0C07112785F for <quic@ietfa.amsl.com>; Sat,  6 Oct 2018 17:45:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, 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=mnot.net header.b=DRwbOx7h; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ExnRt7yH
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 bTAyj4up9DtN for <quic@ietfa.amsl.com>; Sat,  6 Oct 2018 17:45:26 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F225E1277D2 for <quic@ietf.org>; Sat,  6 Oct 2018 17:45:25 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id C337032B4 for <quic@ietf.org>; Sat,  6 Oct 2018 20:45:23 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sat, 06 Oct 2018 20:45:23 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject:message-id:date; s= fm3; bh=OI3LDkD0+QcYSYNw1CC0Z/RPqGrJ3zsjmnAKsi4JAm8=; b=DRwbOx7h mXktZb4eSoPorVrfdOw7I699bu3lYZMYkPV+6vWNaHeIxJbV8Et0MWGeDq6k2KO7 TOpTBwUSeX42E6H6acCmZkTxFeEtAnGR/3Y7zbpi2wNZVY4tH11vzQFIPdjzImJW pewK6sOH4r8RDIsdjsJZEjoh0upWrHT5VxSkMmH8MzfT4xWja78l6theRroUH+Qb qsz6twCDbN3hVSg/2Sp9i9L3NJv7m3wB6ZN67Rh7mM+RQ7IhnGS7YtF3E4F7GPpT Nc5Zsx4BXexdRGt+VsUbjtzKy2GEib7Xl3ZWHpP19aIYuXFXYTDX6AL12t9gmHun vRd/B0BvFWIVvQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=OI3LDkD0+QcYSYNw1CC0Z/RPqGrJ3 zsjmnAKsi4JAm8=; b=ExnRt7yHM05nhW+/MebEdxzV7NO1vUTJOk/Q6tUCRmsDL yZXuhLp0k9vvYJpjbPfaPQgIMa2Vg+QILXoSJLVXKlGH7zr61FqBjD6QHIy0hJxW 0ibVwcFkgzA91vMV6WXv0l55xQRaCV+uIYjJu3Z0q7sxJdIQqXer9u7xX6BUDcyX JxyCFQeq79LBNIq9zp2GlPvIkkO1r4qvRmTyP+MmlTQ7zr6+Lyy/6eNuxasDjxDZ o8G/Ct/PMpr0H19141z0YCFqfH6Dg5Uf4H2nAifLsgPbUqVn+LqAlkSSsIE9an3u MWUj9iG7aaRQjJ+ILR1KknFjKckZp673n+N+HSCNg==
X-ME-Sender: <xms:Ile5WyqY2DyK5C6AHcUoysLxv4RFXuaQIxmnKI9nIm8ekNoRI90MlA>
X-ME-Proxy: <xmx:Ile5WxbxfxR2C2HadcJ7LzkzICyA3A5MsAYJyuaLGXK36_fv4Zivrw> <xmx:Ile5W_cvACHgC9nDltBR8TkzCE7k37fokV_rqG5DP-HIMMJO3YR36w> <xmx:Ile5W4MHFzHtsQkFg_L6QAkxxUMNQWrC4WRpEF8h_4COCalWCZNdYQ> <xmx:Ile5WybB1q6D_nEAgtQeAeoV6czL6GodOKdJAcgG3LkFDC74pw4lmA> <xmx:Ile5W8B6m7EQksuVLofMCCuKVeWlkzl3oHJo4Ucbc7Le78AQ6KtMHg> <xmx:I1e5Ww4e9j-MJ-vvxHagBskrFvPAmCPcfRIOnNP6CSLMloW3Ciqejg>
Received: from cloud.mnot.net (cloud.mnot.net [119.9.43.241]) by mail.messagingengine.com (Postfix) with ESMTPA id 934DAE49D9 for <quic@ietf.org>; Sat,  6 Oct 2018 20:45:21 -0400 (EDT)
Received: from cloud.mnot.net (localhost [127.0.0.1]) by cloud.mnot.net (Postfix) with ESMTP id 478CAC041B for <quic@ietf.org>; Sun,  7 Oct 2018 00:45:18 +0000 (UTC)
Content-Type: multipart/alternative; boundary="===============7862733640891669342=="
MIME-Version: 1.0
From: =?utf-8?q?Github_Notifications?= <do_not_reply@mnot.net>
To: quic@ietf.org
Subject: Weekly github digest (QUIC Working Group Specifications)
Message-Id: <20181007004518.478CAC041B@cloud.mnot.net>
Date: Sun,  7 Oct 2018 00:45:18 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/aNF8YUjM_CKkN513T9JG6M0ZVT0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 07 Oct 2018 00:45:30 -0000

--===============7862733640891669342==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Events without label "editorial"

Issues
------
* quicwg/base-drafts (+10/-12/=F0=9F=92=AC68)
  10 issues created:
  - "Handshake Packet" is Overloaded (by martinduke)
    https://github.com/quicwg/base-drafts/issues/1836 =

  - Recommended response for empty packets (by huitema)
    https://github.com/quicwg/base-drafts/issues/1835 =

  - Flow control for post-handshake CRYPTO messages (by vasilvv)
    https://github.com/quicwg/base-drafts/issues/1834 =

  - Forbid TLS-level KeyUpdate in draft-ietf-quic-tls (by davidben)
    https://github.com/quicwg/base-drafts/issues/1833 =

  - HTTP: State that an empty SETTINGS frame is legal (by dtikhonov)
    https://github.com/quicwg/base-drafts/issues/1832 =

  - Optional packet length field in the short header? (by larseggert)
    https://github.com/quicwg/base-drafts/issues/1831 =

  - Contradicting statement about when CID can be changed during the handsh=
ake (by kazuho)
    https://github.com/quicwg/base-drafts/issues/1830 =

  - Spin bit should be applied per each 5-tuple rather than per connection =
(by kazuho)
    https://github.com/quicwg/base-drafts/issues/1828 =

  - PLPMTUD section claims that PADDING frames generate ACKs (by ajmacedoni=
a)
    https://github.com/quicwg/base-drafts/issues/1827 =

  - Use a "stream" for transmitting CIDs (by kazuho)
    https://github.com/quicwg/base-drafts/issues/1826 =


  17 issues received 68 new comments:
  - #1826 Use a "stream" for transmitting CIDs (24 by kazuho, marten-seeman=
n, mikkelfj, MikeBishop, nibanks, dtikhonov)
    https://github.com/quicwg/base-drafts/issues/1826 =

  - #1828 Spin bit should be applied per each 5-tuple rather than per conne=
ction (10 by kazuho, ianswett, larseggert, mikkelfj)
    https://github.com/quicwg/base-drafts/issues/1828 =

  - #1835 Recommended response for empty packets (7 by kazuho, nibanks, hui=
tema, mikkelfj)
    https://github.com/quicwg/base-drafts/issues/1835 =

  - #1834 Flow control for post-handshake CRYPTO messages (6 by kazuho, dav=
idben)
    https://github.com/quicwg/base-drafts/issues/1834 =

  - #1831 Optional packet length field in the short header? (4 by britram, =
nibanks, mikkelfj)
    https://github.com/quicwg/base-drafts/issues/1831 [-transport] =

  - #1575 Consider simplifying Packet Number Encryption (3 by DavidSchinazi=
, kazuho)
    https://github.com/quicwg/base-drafts/issues/1575 [-tls] [design] [need=
s-discussion] =

  - #1833 Forbid TLS-level KeyUpdate in draft-ietf-quic-tls (3 by mikkelfj,=
 davidben, MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1833 [-tls] [design] =

  - #941 Resume HTTP/2 TLS from QUIC ? (2 by martinduke, LPardue)
    https://github.com/quicwg/base-drafts/issues/941 [-tls] [design] [has-p=
roposal] [quicv2] =

  - #1827 PLPMTUD section claims that PADDING frames generate ACKs (1 by mi=
kkelfj)
    https://github.com/quicwg/base-drafts/issues/1827 =

  - #1464 Confusion about number of outstanding CIDs (1 by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1464 [-transport] [design] =

  - #1468 Prevent connection ID exhaustion (1 by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1468 [-transport] [design] =

  - #1729 Connection ID Garbage Collection (1 by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1729 [-transport] [design] =

  - #1483 Connection ID Sequence Number and Server's Preferred Address (1 b=
y MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1483 [-transport] [design] =

  - #1484 Negative Connection ID Sequence Number (1 by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1484 [-transport] [design] =

  - #1486 Client's initial destination CID is unauthenticated (1 by MikeBis=
hop)
    https://github.com/quicwg/base-drafts/issues/1486 [-transport] [design] =

  - #1495 Disagreement about CID Liveness (1 by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1495 [-transport] [design] =

  - #1655 Change packet types (1 by mjoras)
    https://github.com/quicwg/base-drafts/issues/1655 [-transport] [design] =


  12 issues closed:
  - Confusion about number of outstanding CIDs https://github.com/quicwg/ba=
se-drafts/issues/1464 [-transport] [design] =

  - Prevent connection ID exhaustion https://github.com/quicwg/base-drafts/=
issues/1468 [-transport] [design] =

  - Connection ID Sequence Number and Server's Preferred Address https://gi=
thub.com/quicwg/base-drafts/issues/1483 [-transport] [design] =

  - Negative Connection ID Sequence Number https://github.com/quicwg/base-d=
rafts/issues/1484 [-transport] [design] =

  - Client's initial destination CID is unauthenticated https://github.com/=
quicwg/base-drafts/issues/1486 [-transport] [design] =

  - Disagreement about CID Liveness https://github.com/quicwg/base-drafts/i=
ssues/1495 [-transport] [design] =

  - Connection ID Garbage Collection https://github.com/quicwg/base-drafts/=
issues/1729 [-transport] [design] =

  - Avoid renewing retired connection IDs https://github.com/quicwg/base-dr=
afts/issues/1799 [-transport] =

  - Subsequent Initial Packets with Token Field https://github.com/quicwg/b=
ase-drafts/issues/1649 [-transport] [design] [editor-ready] =

  - Handshake loss recovery interacts poorly with amplification attack defe=
nse https://github.com/quicwg/base-drafts/issues/1764 [-transport] [design]=
 [editor-ready] =

  - QPACK improvement: wrap absolute index values https://github.com/quicwg=
/base-drafts/issues/1644 [-qpack] [design] =

  - HTTP header compression: static table fit for QUIC https://github.com/q=
uicwg/base-drafts/issues/904 [-qpack] [design] =




Pull requests
-------------
* quicwg/base-drafts (+3/-9/=F0=9F=92=AC10)
  3 pull requests submitted:
  - Sequence for Connection IDs, RETIRE (by MikeBishop)
    https://github.com/quicwg/base-drafts/pull/1829 [-transport] [design] =

  - Handshake deadlock (by ianswett)
    https://github.com/quicwg/base-drafts/pull/1824 =

  - Remove QUIC_FLOW_CONTROL_RECEIVED_TOO_MUCH_DATA (by ianswett)
    https://github.com/quicwg/base-drafts/pull/1823 =


  6 pull requests received 10 new comments:
  - #1818 Clarify crypto context for Connection Close (3 by kazuho, martind=
uke, mikkelfj)
    https://github.com/quicwg/base-drafts/pull/1818 =

  - #1815 transport: Initialize a changelog for draft-15 (2 by MikeBishop)
    https://github.com/quicwg/base-drafts/pull/1815 =

  - #1822 Track smallest_newly_acked to prevent spurious RTO (2 by ianswett)
    https://github.com/quicwg/base-drafts/pull/1822 =

  - #1820 Drop HTTP settings' maxima -- they serve no purpose (1 by MikeBis=
hop)
    https://github.com/quicwg/base-drafts/pull/1820 =

  - #1821 Add sequence number to NCID frame (1 by MikeBishop)
    https://github.com/quicwg/base-drafts/pull/1821 =

  - #1824 Handshake deadlock (1 by ianswett)
    https://github.com/quicwg/base-drafts/pull/1824 =


  9 pull requests merged:
  - Add sequence number to CID frames
    https://github.com/quicwg/base-drafts/pull/1821 =

  - Sequence for Connection IDs, RETIRE
    https://github.com/quicwg/base-drafts/pull/1829 [-transport] [design] =

  - Track smallest_newly_acked to prevent spurious RTO
    https://github.com/quicwg/base-drafts/pull/1822 =

  - transport: add missing 2 new TP on IANA table
    https://github.com/quicwg/base-drafts/pull/1814 =

  - Include a token on all Initial packets
    https://github.com/quicwg/base-drafts/pull/1794 [-transport] =

  - Handshake deadlock
    https://github.com/quicwg/base-drafts/pull/1824 =

  - QPACK: Encode Largest Reference modulo MaxEntries
    https://github.com/quicwg/base-drafts/pull/1763 [-qpack] =

  - QPACK:  Updated Static Table
    https://github.com/quicwg/base-drafts/pull/1355 [-qpack] [design] =

  - Drop HTTP settings' maxima -- they serve no purpose
    https://github.com/quicwg/base-drafts/pull/1820 =



Repositories tracked by this digest:
-----------------------------------
* https://github.com/quicwg/base-drafts

--===============7862733640891669342==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (QUIC Working Group Specifications)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
</style>
</head>

<body>
<h1>Sunday October 07, 2018</h1>

<p>Events without label "editorial"</p>

<h2>Issues</h2>

<h3>quicwg/base-drafts (+10/-12/=F0=9F=92=AC68)</h3>
  <p class=3D"new">10 issues created:</p>
  <ul>
  <li>#1836 <a href=3D"https://github.com/quicwg/base-drafts/issues/1836">&=
quot;Handshake Packet&quot; is Overloaded</a> (by martinduke) </li>
  =

  <li>#1835 <a href=3D"https://github.com/quicwg/base-drafts/issues/1835">R=
ecommended response for empty packets</a> (by huitema) </li>
  =

  <li>#1834 <a href=3D"https://github.com/quicwg/base-drafts/issues/1834">F=
low control for post-handshake CRYPTO messages</a> (by vasilvv) </li>
  =

  <li>#1833 <a href=3D"https://github.com/quicwg/base-drafts/issues/1833">F=
orbid TLS-level KeyUpdate in draft-ietf-quic-tls</a> (by davidben) </li>
  =

  <li>#1832 <a href=3D"https://github.com/quicwg/base-drafts/issues/1832">H=
TTP: State that an empty SETTINGS frame is legal</a> (by dtikhonov) </li>
  =

  <li>#1831 <a href=3D"https://github.com/quicwg/base-drafts/issues/1831">O=
ptional packet length field in the short header?</a> (by larseggert) </li>
  =

  <li>#1830 <a href=3D"https://github.com/quicwg/base-drafts/issues/1830">C=
ontradicting statement about when CID can be changed during the handshake</=
a> (by kazuho) </li>
  =

  <li>#1828 <a href=3D"https://github.com/quicwg/base-drafts/issues/1828">S=
pin bit should be applied per each 5-tuple rather than per connection</a> (=
by kazuho) </li>
  =

  <li>#1827 <a href=3D"https://github.com/quicwg/base-drafts/issues/1827">P=
LPMTUD section claims that PADDING frames generate ACKs</a> (by ajmacedonia=
) </li>
  =

  <li>#1826 <a href=3D"https://github.com/quicwg/base-drafts/issues/1826">U=
se a &quot;stream&quot; for transmitting CIDs</a> (by kazuho) </li>
  </ul>

  <p>17 issues received 68 new comments:</p>
  <ul>
  <li>#1826 <a href=3D"https://github.com/quicwg/base-drafts/issues/1826">U=
se a &quot;stream&quot; for transmitting CIDs</a> (24 by kazuho, marten-see=
mann, mikkelfj, MikeBishop, nibanks, dtikhonov) </li>
  =

  <li>#1828 <a href=3D"https://github.com/quicwg/base-drafts/issues/1828">S=
pin bit should be applied per each 5-tuple rather than per connection</a> (=
10 by kazuho, ianswett, larseggert, mikkelfj) </li>
  =

  <li>#1835 <a href=3D"https://github.com/quicwg/base-drafts/issues/1835">R=
ecommended response for empty packets</a> (7 by kazuho, nibanks, huitema, m=
ikkelfj) </li>
  =

  <li>#1834 <a href=3D"https://github.com/quicwg/base-drafts/issues/1834">F=
low control for post-handshake CRYPTO messages</a> (6 by kazuho, davidben) =
</li>
  =

  <li>#1831 <a href=3D"https://github.com/quicwg/base-drafts/issues/1831">O=
ptional packet length field in the short header?</a> (4 by britram, nibanks=
, mikkelfj) <span class=3D"label" style=3D"background-color: #fbca04; color=
: #000000">-transport</span> </li>
  =

  <li>#1575 <a href=3D"https://github.com/quicwg/base-drafts/issues/1575">C=
onsider simplifying Packet Number Encryption</a> (3 by DavidSchinazi, kazuh=
o) <span class=3D"label" style=3D"background-color: #fbca04; color: #000000=
">-tls</span> <span class=3D"label" style=3D"background-color: #1d76db; col=
or: #ffffff">design</span> <span class=3D"label" style=3D"background-color:=
 #006b75; color: #ffffff">needs-discussion</span> </li>
  =

  <li>#1833 <a href=3D"https://github.com/quicwg/base-drafts/issues/1833">F=
orbid TLS-level KeyUpdate in draft-ietf-quic-tls</a> (3 by mikkelfj, davidb=
en, MikeBishop) <span class=3D"label" style=3D"background-color: #fbca04; c=
olor: #000000">-tls</span> <span class=3D"label" style=3D"background-color:=
 #1d76db; color: #ffffff">design</span> </li>
  =

  <li>#941 <a href=3D"https://github.com/quicwg/base-drafts/issues/941">Res=
ume HTTP/2 TLS from QUIC ?</a> (2 by martinduke, LPardue) <span class=3D"la=
bel" style=3D"background-color: #fbca04; color: #000000">-tls</span> <span =
class=3D"label" style=3D"background-color: #1d76db; color: #ffffff">design<=
/span> <span class=3D"label" style=3D"background-color: #c5def5; color: #00=
0000">has-proposal</span> <span class=3D"label" style=3D"background-color: =
#8e64e0; color: #ffffff">quicv2</span> </li>
  =

  <li>#1827 <a href=3D"https://github.com/quicwg/base-drafts/issues/1827">P=
LPMTUD section claims that PADDING frames generate ACKs</a> (1 by mikkelfj)=
 </li>
  =

  <li>#1464 <a href=3D"https://github.com/quicwg/base-drafts/issues/1464">C=
onfusion about number of outstanding CIDs</a> (1 by MikeBishop) <span class=
=3D"label" style=3D"background-color: #fbca04; color: #000000">-transport</=
span> <span class=3D"label" style=3D"background-color: #1d76db; color: #fff=
fff">design</span> </li>
  =

  <li>#1468 <a href=3D"https://github.com/quicwg/base-drafts/issues/1468">P=
revent connection ID exhaustion</a> (1 by MikeBishop) <span class=3D"label"=
 style=3D"background-color: #fbca04; color: #000000">-transport</span> <spa=
n class=3D"label" style=3D"background-color: #1d76db; color: #ffffff">desig=
n</span> </li>
  =

  <li>#1729 <a href=3D"https://github.com/quicwg/base-drafts/issues/1729">C=
onnection ID Garbage Collection</a> (1 by MikeBishop) <span class=3D"label"=
 style=3D"background-color: #fbca04; color: #000000">-transport</span> <spa=
n class=3D"label" style=3D"background-color: #1d76db; color: #ffffff">desig=
n</span> </li>
  =

  <li>#1483 <a href=3D"https://github.com/quicwg/base-drafts/issues/1483">C=
onnection ID Sequence Number and Server&#x27;s Preferred Address</a> (1 by =
MikeBishop) <span class=3D"label" style=3D"background-color: #fbca04; color=
: #000000">-transport</span> <span class=3D"label" style=3D"background-colo=
r: #1d76db; color: #ffffff">design</span> </li>
  =

  <li>#1484 <a href=3D"https://github.com/quicwg/base-drafts/issues/1484">N=
egative Connection ID Sequence Number</a> (1 by MikeBishop) <span class=3D"=
label" style=3D"background-color: #fbca04; color: #000000">-transport</span=
> <span class=3D"label" style=3D"background-color: #1d76db; color: #ffffff"=
>design</span> </li>
  =

  <li>#1486 <a href=3D"https://github.com/quicwg/base-drafts/issues/1486">C=
lient&#x27;s initial destination CID is unauthenticated</a> (1 by MikeBisho=
p) <span class=3D"label" style=3D"background-color: #fbca04; color: #000000=
">-transport</span> <span class=3D"label" style=3D"background-color: #1d76d=
b; color: #ffffff">design</span> </li>
  =

  <li>#1495 <a href=3D"https://github.com/quicwg/base-drafts/issues/1495">D=
isagreement about CID Liveness</a> (1 by MikeBishop) <span class=3D"label" =
style=3D"background-color: #fbca04; color: #000000">-transport</span> <span=
 class=3D"label" style=3D"background-color: #1d76db; color: #ffffff">design=
</span> </li>
  =

  <li>#1655 <a href=3D"https://github.com/quicwg/base-drafts/issues/1655">C=
hange packet types</a> (1 by mjoras) <span class=3D"label" style=3D"backgro=
und-color: #fbca04; color: #000000">-transport</span> <span class=3D"label"=
 style=3D"background-color: #1d76db; color: #ffffff">design</span> </li>
  </ul>

  <p>12 issues closed:</p>
  <ul>
  <li>#1464 <a href=3D"https://github.com/quicwg/base-drafts/issues/1464">C=
onfusion about number of outstanding CIDs</a> <span class=3D"label" style=
=3D"background-color: #fbca04; color: #000000">-transport</span> <span clas=
s=3D"label" style=3D"background-color: #1d76db; color: #ffffff">design</spa=
n> </li>
  =

  <li>#1468 <a href=3D"https://github.com/quicwg/base-drafts/issues/1468">P=
revent connection ID exhaustion</a> <span class=3D"label" style=3D"backgrou=
nd-color: #fbca04; color: #000000">-transport</span> <span class=3D"label" =
style=3D"background-color: #1d76db; color: #ffffff">design</span> </li>
  =

  <li>#1483 <a href=3D"https://github.com/quicwg/base-drafts/issues/1483">C=
onnection ID Sequence Number and Server&#x27;s Preferred Address</a> <span =
class=3D"label" style=3D"background-color: #fbca04; color: #000000">-transp=
ort</span> <span class=3D"label" style=3D"background-color: #1d76db; color:=
 #ffffff">design</span> </li>
  =

  <li>#1484 <a href=3D"https://github.com/quicwg/base-drafts/issues/1484">N=
egative Connection ID Sequence Number</a> <span class=3D"label" style=3D"ba=
ckground-color: #fbca04; color: #000000">-transport</span> <span class=3D"l=
abel" style=3D"background-color: #1d76db; color: #ffffff">design</span> </l=
i>
  =

  <li>#1486 <a href=3D"https://github.com/quicwg/base-drafts/issues/1486">C=
lient&#x27;s initial destination CID is unauthenticated</a> <span class=3D"=
label" style=3D"background-color: #fbca04; color: #000000">-transport</span=
> <span class=3D"label" style=3D"background-color: #1d76db; color: #ffffff"=
>design</span> </li>
  =

  <li>#1495 <a href=3D"https://github.com/quicwg/base-drafts/issues/1495">D=
isagreement about CID Liveness</a> <span class=3D"label" style=3D"backgroun=
d-color: #fbca04; color: #000000">-transport</span> <span class=3D"label" s=
tyle=3D"background-color: #1d76db; color: #ffffff">design</span> </li>
  =

  <li>#1729 <a href=3D"https://github.com/quicwg/base-drafts/issues/1729">C=
onnection ID Garbage Collection</a> <span class=3D"label" style=3D"backgrou=
nd-color: #fbca04; color: #000000">-transport</span> <span class=3D"label" =
style=3D"background-color: #1d76db; color: #ffffff">design</span> </li>
  =

  <li>#1799 <a href=3D"https://github.com/quicwg/base-drafts/issues/1799">A=
void renewing retired connection IDs</a> <span class=3D"label" style=3D"bac=
kground-color: #fbca04; color: #000000">-transport</span> </li>
  =

  <li>#1649 <a href=3D"https://github.com/quicwg/base-drafts/issues/1649">S=
ubsequent Initial Packets with Token Field</a> <span class=3D"label" style=
=3D"background-color: #fbca04; color: #000000">-transport</span> <span clas=
s=3D"label" style=3D"background-color: #1d76db; color: #ffffff">design</spa=
n> <span class=3D"label" style=3D"background-color: #0e8a16; color: #ffffff=
">editor-ready</span> </li>
  =

  <li>#1764 <a href=3D"https://github.com/quicwg/base-drafts/issues/1764">H=
andshake loss recovery interacts poorly with amplification attack defense</=
a> <span class=3D"label" style=3D"background-color: #fbca04; color: #000000=
">-transport</span> <span class=3D"label" style=3D"background-color: #1d76d=
b; color: #ffffff">design</span> <span class=3D"label" style=3D"background-=
color: #0e8a16; color: #ffffff">editor-ready</span> </li>
  =

  <li>#1644 <a href=3D"https://github.com/quicwg/base-drafts/issues/1644">Q=
PACK improvement: wrap absolute index values</a> <span class=3D"label" styl=
e=3D"background-color: #fbca04; color: #000000">-qpack</span> <span class=
=3D"label" style=3D"background-color: #1d76db; color: #ffffff">design</span=
> </li>
  =

  <li>#904 <a href=3D"https://github.com/quicwg/base-drafts/issues/904">HTT=
P header compression: static table fit for QUIC</a> <span class=3D"label" s=
tyle=3D"background-color: #fbca04; color: #000000">-qpack</span> <span clas=
s=3D"label" style=3D"background-color: #1d76db; color: #ffffff">design</spa=
n> </li>
  </ul>



<h2>Pull requests</h2>
<h3>quicwg/base-drafts (+3/-9/=F0=9F=92=AC10)</h3>
  <p class=3D"new">3 pull requests submitted:</p>
  <ul>
  <li>#1829 <a href=3D"https://github.com/quicwg/base-drafts/pull/1829">Seq=
uence for Connection IDs, RETIRE</a> (by MikeBishop) <span class=3D"label" =
style=3D"background-color: #fbca04; color: #">-transport</span> <span class=
=3D"label" style=3D"background-color: #1d76db; color: #">design</span> </li>
  =

  <li>#1824 <a href=3D"https://github.com/quicwg/base-drafts/pull/1824">Han=
dshake deadlock</a> (by ianswett) </li>
  =

  <li>#1823 <a href=3D"https://github.com/quicwg/base-drafts/pull/1823">Rem=
ove QUIC_FLOW_CONTROL_RECEIVED_TOO_MUCH_DATA</a> (by ianswett) </li>
  </ul>

  <p>6 pull requests received 10 new comments:</p>
  <ul>
  <li>#1818 <a href=3D"https://github.com/quicwg/base-drafts/pull/1818">Cla=
rify crypto context for Connection Close</a> (3 by kazuho, martinduke, mikk=
elfj) </li>
  =

  <li>#1815 <a href=3D"https://github.com/quicwg/base-drafts/pull/1815">tra=
nsport: Initialize a changelog for draft-15</a> (2 by MikeBishop) </li>
  =

  <li>#1822 <a href=3D"https://github.com/quicwg/base-drafts/pull/1822">Tra=
ck smallest_newly_acked to prevent spurious RTO</a> (2 by ianswett) </li>
  =

  <li>#1820 <a href=3D"https://github.com/quicwg/base-drafts/pull/1820">Dro=
p HTTP settings&#x27; maxima -- they serve no purpose</a> (1 by MikeBishop)=
 </li>
  =

  <li>#1821 <a href=3D"https://github.com/quicwg/base-drafts/pull/1821">Add=
 sequence number to NCID frame</a> (1 by MikeBishop) </li>
  =

  <li>#1824 <a href=3D"https://github.com/quicwg/base-drafts/pull/1824">Han=
dshake deadlock</a> (1 by ianswett) </li>
  </ul>

  <p>9 pull requests merged:</p>
  <ul>
  <li>#1821 <a href=3D"https://github.com/quicwg/base-drafts/pull/1821">Add=
 sequence number to CID frames</a> </li>
  =

  <li>#1829 <a href=3D"https://github.com/quicwg/base-drafts/pull/1829">Seq=
uence for Connection IDs, RETIRE</a> <span class=3D"label" style=3D"backgro=
und-color: #fbca04; color: #">-transport</span> <span class=3D"label" style=
=3D"background-color: #1d76db; color: #">design</span> </li>
  =

  <li>#1822 <a href=3D"https://github.com/quicwg/base-drafts/pull/1822">Tra=
ck smallest_newly_acked to prevent spurious RTO</a> </li>
  =

  <li>#1814 <a href=3D"https://github.com/quicwg/base-drafts/pull/1814">tra=
nsport: add missing 2 new TP on IANA table</a> </li>
  =

  <li>#1794 <a href=3D"https://github.com/quicwg/base-drafts/pull/1794">Inc=
lude a token on all Initial packets</a> <span class=3D"label" style=3D"back=
ground-color: #fbca04; color: #">-transport</span> </li>
  =

  <li>#1824 <a href=3D"https://github.com/quicwg/base-drafts/pull/1824">Han=
dshake deadlock</a> </li>
  =

  <li>#1763 <a href=3D"https://github.com/quicwg/base-drafts/pull/1763">QPA=
CK: Encode Largest Reference modulo MaxEntries</a> <span class=3D"label" st=
yle=3D"background-color: #fbca04; color: #">-qpack</span> </li>
  =

  <li>#1355 <a href=3D"https://github.com/quicwg/base-drafts/pull/1355">QPA=
CK:  Updated Static Table</a> <span class=3D"label" style=3D"background-col=
or: #fbca04; color: #">-qpack</span> <span class=3D"label" style=3D"backgro=
und-color: #1d76db; color: #">design</span> </li>
  =

  <li>#1820 <a href=3D"https://github.com/quicwg/base-drafts/pull/1820">Dro=
p HTTP settings&#x27; maxima -- they serve no purpose</a> </li>
  </ul>


<h2>Repositories tracked by this digest:</h2>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/quicwg/base-drafts">https://github.com/=
quicwg/base-drafts</a></li>
  </ul>
</body>
</html>

--===============7862733640891669342==--


From nobody Sun Oct  7 20:47:17 2018
Return-Path: <theja2.reddy@gmail.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 86D4B130E4C for <quic@ietfa.amsl.com>; Sun,  7 Oct 2018 20:47:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-0.001] 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 epeekaUsDsCT for <quic@ietfa.amsl.com>; Sun,  7 Oct 2018 20:47:13 -0700 (PDT)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (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 19AD0128CB7 for <quic@ietf.org>; Sun,  7 Oct 2018 20:47:13 -0700 (PDT)
Received: by mail-lj1-x234.google.com with SMTP id o14-v6so16521244ljj.2 for <quic@ietf.org>; Sun, 07 Oct 2018 20:47:12 -0700 (PDT)
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;  bh=MuUoXr92xgJ7+lR/EUC3mGuNXHIpiHNmuVX4s/x5ebI=; b=G12VNhcPcJ0lGe+HdoxvaWzrPmGmWOD3Punm0pVjwdwesc2EVOWgHyWixLaG4TczK6 5lPyGP0FQ0S/sBImZ6A5gy7QZ7fYJFR4BnSWhRxKjfPt92o7ZUoK/rA1XxjFvcJrPsXp wkZAjb/LUmH1f0E/EldO5BD9ab6ZsXEiykZ8cEeTpbI8Gb4DHUPvLiq79rWEs78Q13Wr F+zhf3EG9PAW1i2LrctQw2iKAYLt8qQehmBqBmrXqZhq0q2JvLgt1mdDrITPo99rb73P e08ApsH8qrGzJ/cC37jFMCCPCarbQnbXGJIPY0sw5+1oUtnIFlCDLS9tyYSgowaWTKxL jRXw==
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; bh=MuUoXr92xgJ7+lR/EUC3mGuNXHIpiHNmuVX4s/x5ebI=; b=TSLgZIflQSqWIDzZEpNfgkwk2HXffIK3wxPUdgCqNUTQFq2989cy0LVW6jHXTWJZnZ tU4zqGld1QhtnVaQCeM4JxiSeGLcPhZc1di+tjvjPOmWND9XAFDr5Wg/WiMfI/5sivm6 6L8RZKbtTjZaMonWxtfHiV4iNsc/l5D2ehK8xB0QhRoTHI5EOUHSveFJGoAEaswkq4Ox 7PP/NdsE3Rfv6ecXDUUSWb71VPPOEKotbe/yp7f9g3tOZ2QGL19m6Vc4CL4cChqQBvWv 4WsZnftf4LUb/vuxVgFiv5jZvxvHiZ0U1q+uDkH1OHaH8pRLYPMeA/wkWQhYSja2bIsU ns0w==
X-Gm-Message-State: ABuFfojtEBIxvajm/HgLwORmVRKpExARnm07zzfTO+UKQrwuIpArpEz/ /kJSvhSDb6AEj/hQScOC4i5BEoNct7ab2UxTgVSNQQ==
X-Google-Smtp-Source: ACcGV63ySCiWjIxgThyLnKL6AJr99aPsoP1dm7HvSmqe9PuTrKMV34WnaAeU/MEzFNAkqStkqZB8FaFS+BNueUMc0K0=
X-Received: by 2002:a2e:6353:: with SMTP id x80-v6mr12755554ljb.11.1538970430928;  Sun, 07 Oct 2018 20:47:10 -0700 (PDT)
MIME-Version: 1.0
References: <153860645083.9124.2956485723206917113@ietfa.amsl.com>
In-Reply-To: <153860645083.9124.2956485723206917113@ietfa.amsl.com>
From: Theja Reddy <theja2.reddy@gmail.com>
Date: Mon, 8 Oct 2018 09:16:58 +0530
Message-ID: <CABYA432TqfsgEdt2CGvAcb73Yzvjw1KFZSc5z6M7pmUT-Xwquw@mail.gmail.com>
Subject: Re: I-D Action: draft-ietf-quic-http-15.txt
To: quic@ietf.org
Content-Type: multipart/alternative; boundary="000000000000dafb240577af7928"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/UMdWZ98Oy1O_wIIFF1tuXjDrfTo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 08 Oct 2018 03:47:16 -0000

--000000000000dafb240577af7928
Content-Type: text/plain; charset="UTF-8"

On Thu, 4 Oct 2018, 04:14 , <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the QUIC WG of the IETF.
>
>         Title           : Hypertext Transfer Protocol (HTTP) over QUIC
>         Author          : Mike Bishop
>         Filename        : draft-ietf-quic-http-15.txt
>         Pages           : 47
>         Date            : 2018-10-03
>
> Abstract:
>    The QUIC transport protocol has several features that are desirable
>    in a transport for HTTP, such as stream multiplexing, per-stream flow
>    control, and low-latency connection establishment.  This document
>    describes a mapping of HTTP semantics over QUIC.  This document also
>    identifies HTTP/2 features that are subsumed by QUIC, and describes
>    how HTTP/2 extensions can be ported to QUIC.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-quic-http/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-quic-http-15
> https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-15
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-http-15
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>

--000000000000dafb240577af7928
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On =
Thu, 4 Oct 2018, 04:14 , &lt;<a href=3D"mailto:internet-drafts@ietf.org">in=
ternet-drafts@ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the QUIC WG of the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Hypertext Transfer Protocol (HTTP) over QUIC<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Mike=
 Bishop<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-quic-http-15.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 47<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2018-10-03<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0The QUIC transport protocol has several features that are desi=
rable<br>
=C2=A0 =C2=A0in a transport for HTTP, such as stream multiplexing, per-stre=
am flow<br>
=C2=A0 =C2=A0control, and low-latency connection establishment.=C2=A0 This =
document<br>
=C2=A0 =C2=A0describes a mapping of HTTP semantics over QUIC.=C2=A0 This do=
cument also<br>
=C2=A0 =C2=A0identifies HTTP/2 features that are subsumed by QUIC, and desc=
ribes<br>
=C2=A0 =C2=A0how HTTP/2 extensions can be ported to QUIC.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-quic-http/" rel=3D"n=
oreferrer noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/dr=
aft-ietf-quic-http/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-quic-http-15" rel=3D"nore=
ferrer noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-ietf=
-quic-http-15</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-15" r=
el=3D"noreferrer noreferrer" target=3D"_blank">https://datatracker.ietf.org=
/doc/html/draft-ietf-quic-http-15</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-quic-http-15" rel=
=3D"noreferrer noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?u=
rl2=3Ddraft-ietf-quic-http-15</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer noreferrer" target=3D"_blank">tools.ietf.org<=
/a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer noreferre=
r" target=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
<br>
</blockquote></div>

--000000000000dafb240577af7928--


From nobody Sun Oct  7 20:50:34 2018
Return-Path: <theja2.reddy@gmail.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 EDFAF128CB7 for <quic@ietfa.amsl.com>; Sun,  7 Oct 2018 20:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-0.001] 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 3B0sXadr0v7R for <quic@ietfa.amsl.com>; Sun,  7 Oct 2018 20:50:30 -0700 (PDT)
Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (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 6BF9D130E4C for <quic@ietf.org>; Sun,  7 Oct 2018 20:50:30 -0700 (PDT)
Received: by mail-lj1-x232.google.com with SMTP id j17-v6so7214745lja.1 for <quic@ietf.org>; Sun, 07 Oct 2018 20:50:30 -0700 (PDT)
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;  bh=/HDCPLJD8HbohOMq1ljjMFOCMzXx1/fugMineSY29Z0=; b=W678niHaJsjM0wU4w0MkowpGKNsp6+ilx9rBI0S/rfz1ya7VB445R8aKDGf4PM8N2I MtA6PWGLH2f713H4orDD6T4OqqgyLLqJIT5+wF08WDh0JEPatG1gyfeAWFSLlEOiPOlP nofh72WoNXaRfjbzrX6ThG6I3LAzJ10ONl+t9dlQ9uFujSkdUloWPsve+vHKmKuqYAr/ 0U+ES9fQXbgPD6HBj07iLkm+d6KonEN5LL3VF2G5iq+9ntQ0Yt12ishIdkhUA/aB3Bdc eyDF4oSPlI3Xn0rcWYqceYUBOCYbYquhB3XjSw7kNMJBkGJ/EqaBw+o49rsxlHU5WtA/ MiSg==
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; bh=/HDCPLJD8HbohOMq1ljjMFOCMzXx1/fugMineSY29Z0=; b=O7cSOSbQzTEZ0FukJLDxWdf9wTfcKei+BqI9cY0l0cuuq/r6G2VZ/yQtA2/j5EoFj2 tn1H6HA3JcZWZSHchSmS4PIFlKLByRWUe82CKGRYBjg5O6WDWGIDGgrvxsk6RhpS+oMO 4DbuE6v1abgxipmUVnaNijqsRwEneIR6SEvRsQhneaVAIBu9jZm6SAnbyhuexfMnsQU1 FD46+eK89Oo64lIj3xE3v6OkL8jtyiBalNujAMwwYS6uWme098Z099c1d9aFeBnn8BMs TIJwfJJzXSigQR2xALVYcxyyHp0MovyMrsgFcRKThU5uycOG08IMecdRXoubv8qRL+fE yHag==
X-Gm-Message-State: ABuFfogfxBKsTyqJtnXT2+lQ0FSZ52lu++KoHSTLH6BFOawsa72IaBWv Zi33wnn6ax1W8RqZj7axs5Mv2wfDJWeYi0zLb7nqZQ==
X-Google-Smtp-Source: ACcGV62s4dyNKXT9iSeO27QkAl+Qfwp/ROIeRZqaGybdZdrv0R1AezwgvBT2789/bxSn6PLIUgsF0NPN8Y2F/aGGE18=
X-Received: by 2002:a2e:9a93:: with SMTP id p19-v6mr8316912lji.87.1538970628337;  Sun, 07 Oct 2018 20:50:28 -0700 (PDT)
MIME-Version: 1.0
References: <153860645083.9124.2956485723206917113@ietfa.amsl.com> <CABYA432TqfsgEdt2CGvAcb73Yzvjw1KFZSc5z6M7pmUT-Xwquw@mail.gmail.com>
In-Reply-To: <CABYA432TqfsgEdt2CGvAcb73Yzvjw1KFZSc5z6M7pmUT-Xwquw@mail.gmail.com>
From: Theja Reddy <theja2.reddy@gmail.com>
Date: Mon, 8 Oct 2018 09:20:16 +0530
Message-ID: <CABYA433ZuzRmnoD4VO3Fxc+iE4f6Jpg0euTGY-pYs682RA-Jsg@mail.gmail.com>
Subject: Re: I-D Action: draft-ietf-quic-http-15.txt
To: quic@ietf.org
Content-Type: multipart/alternative; boundary="0000000000009f341d0577af850c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/XLl-dHjbHd1m-oEgPYGRk9ivLDA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 08 Oct 2018 03:50:33 -0000

--0000000000009f341d0577af850c
Content-Type: text/plain; charset="UTF-8"

On Mon, 8 Oct 2018, 09:16 Theja Reddy, <theja2.reddy@gmail.com> wrote:

>
> On Thu, 4 Oct 2018, 04:14 , <internet-drafts@ietf.org> wrote:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the QUIC WG of the IETF.
>>
>>         Title           : Hypertext Transfer Protocol (HTTP) over QUIC
>>         Author          : Mike Bishop
>>         Filename        : draft-ietf-quic-http-15.txt
>>         Pages           : 47
>>         Date            : 2018-10-03
>>
>> Abstract:
>>    The QUIC transport protocol has several features that are desirable
>>    in a transport for HTTP, such as stream multiplexing, per-stream flow
>>    control, and low-latency connection establishment.  This document
>>    describes a mapping of HTTP semantics over QUIC.  This document also
>>    identifies HTTP/2 features that are subsumed by QUIC, and describes
>>    how HTTP/2 extensions can be ported to QUIC.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-quic-http/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-quic-http-15
>> https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-15
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-http-15
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>>

--0000000000009f341d0577af850c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On =
Mon, 8 Oct 2018, 09:16 Theja Reddy, &lt;<a href=3D"mailto:theja2.reddy@gmai=
l.com">theja2.reddy@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex"><div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr">On Thu, 4 Oct 2018, 04:14 , &lt;<a href=3D"mailto:internet-drafts@=
ietf.org" target=3D"_blank" rel=3D"noreferrer">internet-drafts@ietf.org</a>=
&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the QUIC WG of the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Hypertext Transfer Protocol (HTTP) over QUIC<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Mike=
 Bishop<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-quic-http-15.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 47<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2018-10-03<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0The QUIC transport protocol has several features that are desi=
rable<br>
=C2=A0 =C2=A0in a transport for HTTP, such as stream multiplexing, per-stre=
am flow<br>
=C2=A0 =C2=A0control, and low-latency connection establishment.=C2=A0 This =
document<br>
=C2=A0 =C2=A0describes a mapping of HTTP semantics over QUIC.=C2=A0 This do=
cument also<br>
=C2=A0 =C2=A0identifies HTTP/2 features that are subsumed by QUIC, and desc=
ribes<br>
=C2=A0 =C2=A0how HTTP/2 extensions can be ported to QUIC.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-quic-http/" rel=3D"n=
oreferrer noreferrer noreferrer" target=3D"_blank">https://datatracker.ietf=
.org/doc/draft-ietf-quic-http/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-quic-http-15" rel=3D"nore=
ferrer noreferrer noreferrer" target=3D"_blank">https://tools.ietf.org/html=
/draft-ietf-quic-http-15</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-15" r=
el=3D"noreferrer noreferrer noreferrer" target=3D"_blank">https://datatrack=
er.ietf.org/doc/html/draft-ietf-quic-http-15</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-quic-http-15" rel=
=3D"noreferrer noreferrer noreferrer" target=3D"_blank">https://www.ietf.or=
g/rfcdiff?url2=3Ddraft-ietf-quic-http-15</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">tool=
s.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer noreferre=
r noreferrer" target=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
<br>
</blockquote></div>
</blockquote></div>

--0000000000009f341d0577af850c--


From nobody Sun Oct  7 20:52:10 2018
Return-Path: <theja2.reddy@gmail.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 56D16130E4E for <quic@ietfa.amsl.com>; Sun,  7 Oct 2018 20:52:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-0.001] 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 iBaykSbH-y1o for <quic@ietfa.amsl.com>; Sun,  7 Oct 2018 20:52:06 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 EF96B128CB7 for <quic@ietf.org>; Sun,  7 Oct 2018 20:52:05 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id 63-v6so16498634ljs.4 for <quic@ietf.org>; Sun, 07 Oct 2018 20:52:05 -0700 (PDT)
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;  bh=nd0dp9EObuZ8+/CmaXQB5Y+IXW/uGFZzfxo/8Bz2Vrc=; b=qHfLKZd2E4RuPstk921k6uR/bAe9aIIIeXMSd+T+EHWAuC/V9+welr0uiw9K8bgH0i LBuEHELXbJoFYiPrTy2YAh2BOqBQ9cvVPWddolIJUussX9HhhfFyWk6kgWFbPicCovrM T5R5invlmD5GTNg6GFvhmgaVfZYVEeDVwZY3S/Ob8W2BXesPmANNWFYyjasV8KipbJFz AHCckn7TmvXm8iLI7hi3jc7VWRdYsEUlEmrbpeQ3x1RVZNfSQV0dkQD3xD5NBFxtZ56f 9nD3ObW7eM6dUpnRjxQ8F1WU9B0T+skqlfEoNF4MDIxhiZVTJsNU2f7Za4QQENP46jCo r6Vg==
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; bh=nd0dp9EObuZ8+/CmaXQB5Y+IXW/uGFZzfxo/8Bz2Vrc=; b=h+Qo9dMWiRopPlUTYbVuhU0fK9LYCu5eDMFD/ey4gpLYPYVQaS7zQeuKVWEtrbh21X p2s3CbUf3SUF1eR34TJHZIQwoNJr+0PdeJclTykLHkFfAv1Dt+TdvDphYlvghxvnp2Qn /YqsG8lCoUqSp9XG6iHuol4HhoBJkTD7IiRGzhAsWazQtWkSsNTQUkss+hs6X/r1MWFN yOuQsdiZEXoXh+CedHOmItIVWi1gt60VOT4AKkYGw3NhDJ9xF83rbbr1mXyUpJb3SYAS /cMTyfSjvHvKWkNaHctf2LzfQhJLRmP1MGfPHmSNCH36U1u6f74fkzrlBzI1lvOoD4UI sWgA==
X-Gm-Message-State: ABuFfojxcCNTDEVPB6DaTWGS0I2X7GT03bJ476raNlTIrIKyvemTgUQ0 VA2YHMANUvj4TyqzntPB5UsuUWG5edJBsdQYvMjlbg==
X-Google-Smtp-Source: ACcGV63jOPiAStBzREK4HfVfRBF/hSjmMhBqnLVhgEXFcE+2YEGjR5qahPqiRhiyQV/UDnv5kWTFYsxCooif9eo34fE=
X-Received: by 2002:a2e:91d3:: with SMTP id u19-v6mr12857620ljg.64.1538970723892;  Sun, 07 Oct 2018 20:52:03 -0700 (PDT)
MIME-Version: 1.0
References: <153860645083.9124.2956485723206917113@ietfa.amsl.com> <CABYA432TqfsgEdt2CGvAcb73Yzvjw1KFZSc5z6M7pmUT-Xwquw@mail.gmail.com> <CABYA433ZuzRmnoD4VO3Fxc+iE4f6Jpg0euTGY-pYs682RA-Jsg@mail.gmail.com>
In-Reply-To: <CABYA433ZuzRmnoD4VO3Fxc+iE4f6Jpg0euTGY-pYs682RA-Jsg@mail.gmail.com>
From: Theja Reddy <theja2.reddy@gmail.com>
Date: Mon, 8 Oct 2018 09:21:50 +0530
Message-ID: <CABYA433XroKhOuOve6Ca1GWnJzh9bq6hjMUxM48N1VjoVf0x_w@mail.gmail.com>
Subject: Re: I-D Action: draft-ietf-quic-http-15.txt
To: quic@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005142be0577af8b90"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YmlSRUHX7bpVN0D9zojMkoKgrHs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 08 Oct 2018 03:52:08 -0000

--0000000000005142be0577af8b90
Content-Type: text/plain; charset="UTF-8"

On Mon, 8 Oct 2018, 09:20 Theja Reddy, <theja2.reddy@gmail.com> wrote:

>
> On Mon, 8 Oct 2018, 09:16 Theja Reddy, <theja2.reddy@gmail.com> wrote:
>
>>
>> On Thu, 4 Oct 2018, 04:14 , <internet-drafts@ietf.org> wrote:
>>
>>>
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories.
>>> This draft is a work item of the QUIC WG of the IETF.
>>>
>>>         Title           : Hypertext Transfer Protocol (HTTP) over QUIC
>>>         Author          : Mike Bishop
>>>         Filename        : draft-ietf-quic-http-15.txt
>>>         Pages           : 47
>>>         Date            : 2018-10-03
>>>
>>> Abstract:
>>>    The QUIC transport protocol has several features that are desirable
>>>    in a transport for HTTP, such as stream multiplexing, per-stream flow
>>>    control, and low-latency connection establishment.  This document
>>>    describes a mapping of HTTP semantics over QUIC.  This document also
>>>    identifies HTTP/2 features that are subsumed by QUIC, and describes
>>>    how HTTP/2 extensions can be ported to QUIC.
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-quic-http/
>>>
>>> There are also htmlized versions available at:
>>> https://tools.ietf.org/html/draft-ietf-quic-http-15
>>> https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-15
>>>
>>> A diff from the previous version is available at:
>>> https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-http-15
>>>
>>>
>>> Please note that it may take a couple of minutes from the time of
>>> submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>>

--0000000000005142be0577af8b90
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On =
Mon, 8 Oct 2018, 09:20 Theja Reddy, &lt;<a href=3D"mailto:theja2.reddy@gmai=
l.com">theja2.reddy@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex"><div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr">On Mon, 8 Oct 2018, 09:16 Theja Reddy, &lt;<a href=3D"mailto:theja=
2.reddy@gmail.com" target=3D"_blank" rel=3D"noreferrer">theja2.reddy@gmail.=
com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto=
"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Thu, 4 Oct 2018,=
 04:14 , &lt;<a href=3D"mailto:internet-drafts@ietf.org" rel=3D"noreferrer =
noreferrer" target=3D"_blank">internet-drafts@ietf.org</a>&gt; wrote:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the QUIC WG of the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Hypertext Transfer Protocol (HTTP) over QUIC<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Mike=
 Bishop<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-quic-http-15.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 47<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2018-10-03<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0The QUIC transport protocol has several features that are desi=
rable<br>
=C2=A0 =C2=A0in a transport for HTTP, such as stream multiplexing, per-stre=
am flow<br>
=C2=A0 =C2=A0control, and low-latency connection establishment.=C2=A0 This =
document<br>
=C2=A0 =C2=A0describes a mapping of HTTP semantics over QUIC.=C2=A0 This do=
cument also<br>
=C2=A0 =C2=A0identifies HTTP/2 features that are subsumed by QUIC, and desc=
ribes<br>
=C2=A0 =C2=A0how HTTP/2 extensions can be ported to QUIC.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-quic-http/" rel=3D"n=
oreferrer noreferrer noreferrer noreferrer" target=3D"_blank">https://datat=
racker.ietf.org/doc/draft-ietf-quic-http/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-quic-http-15" rel=3D"nore=
ferrer noreferrer noreferrer noreferrer" target=3D"_blank">https://tools.ie=
tf.org/html/draft-ietf-quic-http-15</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-15" r=
el=3D"noreferrer noreferrer noreferrer noreferrer" target=3D"_blank">https:=
//datatracker.ietf.org/doc/html/draft-ietf-quic-http-15</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-quic-http-15" rel=
=3D"noreferrer noreferrer noreferrer noreferrer" target=3D"_blank">https://=
www.ietf.org/rfcdiff?url2=3Ddraft-ietf-quic-http-15</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer noreferrer noreferrer noreferrer" target=3D"_=
blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer noreferre=
r noreferrer noreferrer" target=3D"_blank">ftp://ftp.ietf.org/internet-draf=
ts/</a><br>
<br>
</blockquote></div>
</blockquote></div>
</blockquote></div>

--0000000000005142be0577af8b90--


From nobody Sun Oct  7 20:53:21 2018
Return-Path: <theja2.reddy@gmail.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 8B436130E4C for <quic@ietfa.amsl.com>; Sun,  7 Oct 2018 20:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-0.001] 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 Zg4MsoI87IE5 for <quic@ietfa.amsl.com>; Sun,  7 Oct 2018 20:53:17 -0700 (PDT)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 E6886128CB7 for <quic@ietf.org>; Sun,  7 Oct 2018 20:53:16 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id u21-v6so16472766lja.8 for <quic@ietf.org>; Sun, 07 Oct 2018 20:53:16 -0700 (PDT)
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;  bh=om774zgq9QfHewFkcn7yBUNxieFu051D+XOkgGbsqO8=; b=MvAp0OdH128O3SHyT8Y4ymY9kvyIqNB6/CkMGixQSr4mRYVfZf/hBCSdoi9/svxxd8 e67pCy4ICZlo62F4RLnA+XvlyJYWeVkYmzm90vYWz8+J1TV4iLgicLWW4o62d0czAXPJ G11PWkpS3+JukOPt2IY/dB1Q+NZ3P/wYeT3sv3th7jbtl7ylgzmgldInCbjkrNgFm2Mu NGf45BvUaKLcwMfIh8OPOSvHov+qS30+hRHa28aOF0+r+h7Mprrj8KhogVjc/9Qk/xxh rKtZ84FQU9KjXnM6qv0fhaF5L5TfM8iOTiDwVYfiZnT/Z0USq6zOjLrYZb/6TeD9SFcz GbMw==
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; bh=om774zgq9QfHewFkcn7yBUNxieFu051D+XOkgGbsqO8=; b=N5O3Tj9iqItwh8XQJx0gs3yI6IVL5KCmN0FgqaKZkRfkdGFrNsenXZCXovXK08HI5R 8b6th41TXMN5diLP4Z9ds5fkvrTepREja49WbE9LGUV7hiNsx/fs2r+QqXNATfNYw8Jn /TsabdIKf91S6fHSdrXioUGnxVQ+40dx1p99groztjgMlVFmT0g9hXj5sqxX8yF3sVL3 BGFnXv/ZPUPw6jJWtg8VxX2BOxEXa+RO4aJ0jLu+A1wiukSocZpt7OXzEaNHx6LEYWn7 iXux7OtQLvvSElx679yzDDOqypm+xcu/Ysf0517FuqvDQNI6doeyDObGbrjh5tQSq+Ib Ps+w==
X-Gm-Message-State: ABuFfoiFkW22G4fjg9wgRqqoUOmIngTM10Pmnchpr+ueVYnFSXSNNCNN jXZ5rxRXf/tgcj1jSsNntTBQdk+SEzRQ1BrDXXDNIw==
X-Google-Smtp-Source: ACcGV62Tg7ExwNeEtlCjeHh5LLBi52F84Dr/f4VKhGXEbflx9itMv6mdk3S5ALcW7rYqV9uTKhVr9JugLxW+n4T3m44=
X-Received: by 2002:a2e:99d3:: with SMTP id l19-v6mr5139811ljj.132.1538970794859;  Sun, 07 Oct 2018 20:53:14 -0700 (PDT)
MIME-Version: 1.0
References: <153860643702.9128.18142464629204085867@ietfa.amsl.com>
In-Reply-To: <153860643702.9128.18142464629204085867@ietfa.amsl.com>
From: Theja Reddy <theja2.reddy@gmail.com>
Date: Mon, 8 Oct 2018 09:23:02 +0530
Message-ID: <CABYA432jbL-r=sotZrvBxqstJrKfNj8VXs2cjToPuvWLrYp=Gg@mail.gmail.com>
Subject: Re: I-D Action: draft-ietf-quic-qpack-03.txt
To: quic@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008c1f880577af8f1e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Eq4GGDlPibhBlIowIJSTYpjrnUk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 08 Oct 2018 03:53:19 -0000

--0000000000008c1f880577af8f1e
Content-Type: text/plain; charset="UTF-8"

On Thu, 4 Oct 2018, 04:12 , <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the QUIC WG of the IETF.
>
>         Title           : QPACK: Header Compression for HTTP over QUIC
>         Authors         : Charles 'Buck' Krasic
>                           Mike Bishop
>                           Alan Frindell
>         Filename        : draft-ietf-quic-qpack-03.txt
>         Pages           : 35
>         Date            : 2018-10-03
>
> Abstract:
>    This specification defines QPACK, a compression format for
>    efficiently representing HTTP header fields, to be used in HTTP/QUIC.
>    This is a variation of HPACK header compression that seeks to reduce
>    head-of-line blocking.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-quic-qpack/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-quic-qpack-03
> https://datatracker.ietf.org/doc/html/draft-ietf-quic-qpack-03
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-qpack-03
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>

--0000000000008c1f880577af8f1e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On =
Thu, 4 Oct 2018, 04:12 , &lt;<a href=3D"mailto:internet-drafts@ietf.org">in=
ternet-drafts@ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the QUIC WG of the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 QPACK: Header Compression for HTTP over QUIC<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Char=
les &#39;Buck&#39; Krasic<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Mike Bishop<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Alan Frindell<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-quic-qpack-03.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 35<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2018-10-03<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This specification defines QPACK, a compression format for<br>
=C2=A0 =C2=A0efficiently representing HTTP header fields, to be used in HTT=
P/QUIC.<br>
=C2=A0 =C2=A0This is a variation of HPACK header compression that seeks to =
reduce<br>
=C2=A0 =C2=A0head-of-line blocking.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-quic-qpack/" rel=3D"=
noreferrer noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/d=
raft-ietf-quic-qpack/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-quic-qpack-03" rel=3D"nor=
eferrer noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-iet=
f-quic-qpack-03</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-quic-qpack-03" =
rel=3D"noreferrer noreferrer" target=3D"_blank">https://datatracker.ietf.or=
g/doc/html/draft-ietf-quic-qpack-03</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-quic-qpack-03" re=
l=3D"noreferrer noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?=
url2=3Ddraft-ietf-quic-qpack-03</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer noreferrer" target=3D"_blank">tools.ietf.org<=
/a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer noreferre=
r" target=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
<br>
</blockquote></div>

--0000000000008c1f880577af8f1e--


From nobody Tue Oct  9 23:49:50 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F5D0130E91; Tue,  9 Oct 2018 23:49:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-invariants-03.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.86.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <153915418105.10700.689314192030281701@ietfa.amsl.com>
Date: Tue, 09 Oct 2018 23:49:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Qhf_Awjhu68-WrK7rm0c3-sc5nM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 10 Oct 2018 06:49:42 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : Version-Independent Properties of QUIC
        Author          : Martin Thomson
	Filename        : draft-ietf-quic-invariants-03.txt
	Pages           : 9
	Date            : 2018-10-03

Abstract:
   This document defines the properties of the QUIC transport protocol
   that are expected to remain unchanged over time as new versions of
   the protocol are developed.

Note to Readers

   Discussion of this draft takes place on the QUIC working group
   mailing list (quic@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/search/?email_list=quic [1].

   Working Group information can be found at https://github.com/quicwg
   [2]; source code and issues list for this draft can be found at
   https://github.com/quicwg/base-drafts/labels/-invariants [3].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-invariants/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-invariants-03
https://datatracker.ietf.org/doc/html/draft-ietf-quic-invariants-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-invariants-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sat Oct 13 17:45:27 2018
Return-Path: <do_not_reply@mnot.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 AA9EB127598 for <quic@ietfa.amsl.com>; Sat, 13 Oct 2018 17:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=Wa2G/VJ2; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=rN8eY7fl
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 2WMX8DUWQTMU for <quic@ietfa.amsl.com>; Sat, 13 Oct 2018 17:45:22 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BAB912785F for <quic@ietf.org>; Sat, 13 Oct 2018 17:45:21 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 0D81921BD8 for <quic@ietf.org>; Sat, 13 Oct 2018 20:45:21 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sat, 13 Oct 2018 20:45:21 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject:message-id:date; s= fm3; bh=pVw+PSo68HsqG7ZbebCILErAkuC3b+02/fMX1A/UTaU=; b=Wa2G/VJ2 pYwVpPJx9tVsygoylTcRjdHz/xIUZiIm80b3SwCaefaImNFgej2pOFrMzD7ON0VS I+/se6WDjAQ2zeoEyIGz4575p7uTux06DQysu87l7bMXqx40PwKKSBX/VAy23CMH /1JqqjKskQK53oktiMOwYJu86799+9N+FhfiAq+8gSnpRsFyLDL6qUv/MwkXOwGW uk0ir9Ij1ygpfHWqz3E0hVoO4FVHpuAKBvKduMLS3CMp1B8aUpfi2TSx56BycheL bNo9hxkK8FwNAp7N3p/uqza5zP583CGET8lXe3HanklKE/7YJ5u4dNlYJ4oN0k2l serOdjHioRem8Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=pVw+PSo68HsqG7ZbebCILErAkuC3b +02/fMX1A/UTaU=; b=rN8eY7flA732csKejg/j5q9NKaNelHbBwX4UJa6rF841f wtMir17hvlXv9D31eGzplVFdYEnAVFh1FD6T8KegIx05nG34syyzsWZHYM9bx6Ig BdBmao3JD07t9il5pP9iCcI3odXyQm8diyCdl2FoHnwc+VvtaVDxQjg55I+8MIZv Bc+zV07czbQzwS2fbuhWxeM71CsIC4EUoyv8g/uQ35Qe8OVrRpEstMyOpR5qCcnx mDcVO6UPS5+NWZnxGR/0vrmTv9vNEhbKJnPRBxd5eVCYNKC0Y4V9wCjpMFfX1lDW jKdt3Y7Y9JEL0bjVWYDvwq/IMWC6K8PS2Fb8z+v6A==
X-ME-Sender: <xms:npHCW1rKdekvBdGLPLStJcWOeqsiJhS3pOP8Efc1AuCbE3Gwsf25kA>
X-ME-Proxy: <xmx:n5HCW_kfvRO-6guR4FCEHCGNjLI2yezKdPgv9gHyihTwIzGlRrrz5A> <xmx:n5HCW0Pq5husy7DA_zFXMrlCg_4W9cGJtuPiVu7d9hXzqsYa0wuNOQ> <xmx:n5HCW-6vRAMDeG1zb-S8uqPoxBSinHVtEPc8hIkAXa3wnFxuRrynxg> <xmx:n5HCW_1yrbGDkF0_bnmEBWQ28Za9VaVq2QmPHfOvEgy5TUmcfUrqVQ> <xmx:n5HCW0pNC_m8K938TrRqw1YCu_PlPgBhzHOjJ7jfM9BW0naj2_GTvA> <xmx:oJHCW_IU3Vs-_TPv20c5kpcU7WRj4lsy4Ys5dNozVzE4curQS9i2cw>
Received: from cloud.mnot.net (cloud.mnot.net [119.9.43.241]) by mail.messagingengine.com (Postfix) with ESMTPA id 57F93E4623 for <quic@ietf.org>; Sat, 13 Oct 2018 20:45:18 -0400 (EDT)
Received: from cloud.mnot.net (localhost [127.0.0.1]) by cloud.mnot.net (Postfix) with ESMTP id C4207C4FD3 for <quic@ietf.org>; Sun, 14 Oct 2018 00:45:14 +0000 (UTC)
Content-Type: multipart/alternative; boundary="===============4472943487960647431=="
MIME-Version: 1.0
From: =?utf-8?q?Github_Notifications?= <do_not_reply@mnot.net>
To: quic@ietf.org
Subject: Weekly github digest (QUIC Working Group Specifications)
Message-Id: <20181014004514.C4207C4FD3@cloud.mnot.net>
Date: Sun, 14 Oct 2018 00:45:14 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/jMRPSAM1fCZv0LZTFiYMxWZtsvI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 14 Oct 2018 00:45:26 -0000

--===============4472943487960647431==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Events without label "editorial"

Issues
------
* quicwg/base-drafts (+9/-3/=F0=9F=92=AC57)
  9 issues created:
  - Transport parameter "original connection ID" if no retry (by huitema)
    https://github.com/quicwg/base-drafts/issues/1855 =

  - Does GOAWAY really need a stream number? (by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1853 [-http] [design] =

  - STREAM_ID_BLOCKED frame can't encode being blocked on stream 0 (by mart=
en-seemann)
    https://github.com/quicwg/base-drafts/issues/1850 =

  - PRIORITY frame illustration is unclear (by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1848 =

  - HTTP SETTINGS: why reuse codepoint 0x3? (by dtikhonov)
    https://github.com/quicwg/base-drafts/issues/1847 =

  - Asymmetry in the handling of SETTINGS frame (by kazuho)
    https://github.com/quicwg/base-drafts/issues/1846 =

  - Should the key update expansion use "quic " or "tls13 "? (by huitema)
    https://github.com/quicwg/base-drafts/issues/1845 =

  - When to ignore coalesced packets and when to terminate the connection (=
by igorlord)
    https://github.com/quicwg/base-drafts/issues/1840 =

  - ECN counters and Coalescing of QUIC packets (by gloinul)
    https://github.com/quicwg/base-drafts/issues/1838 =


  9 issues received 57 new comments:
  - #1846 Asymmetry in the handling of SETTINGS frame (28 by kazuho, afrind=
, MikeBishop, RyanAtGoogle, lnicco, dtikhonov, LPardue)
    https://github.com/quicwg/base-drafts/issues/1846 [-http] [design] =

  - #1850 STREAM_ID_BLOCKED frame can't encode being blocked on stream 0 (1=
2 by kazuho, marten-seemann, janaiyengar, mikkelfj, nibanks, ianswett, dtik=
honov)
    https://github.com/quicwg/base-drafts/issues/1850 =

  - #1853 Does GOAWAY really need a stream number? (6 by kazuho, afrind, Mi=
keBishop)
    https://github.com/quicwg/base-drafts/issues/1853 [-http] [design] =

  - #1831 Optional packet length field in the short header? (2 by larsegger=
t, ianswett)
    https://github.com/quicwg/base-drafts/issues/1831 [-transport] =

  - #1835 Recommended response for empty packets (2 by igorlord, ianswett)
    https://github.com/quicwg/base-drafts/issues/1835 =

  - #1836 "Handshake Packet" is Overloaded (2 by martinduke, ianswett)
    https://github.com/quicwg/base-drafts/issues/1836 =

  - #941 Resume HTTP/2 TLS from QUIC ? (2 by martinthomson)
    https://github.com/quicwg/base-drafts/issues/941 [-tls] [design] [has-p=
roposal] [quicv2] =

  - #1855 Transport parameter "original connection ID" if no retry (2 by ja=
naiyengar, hardie)
    https://github.com/quicwg/base-drafts/issues/1855 =

  - #1840 When to ignore coalesced packets and when to terminate the connec=
tion (1 by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1840 =


  3 issues closed:
  - Optional packet length field in the short header? https://github.com/qu=
icwg/base-drafts/issues/1831 [-transport] =

  - Resume HTTP/2 TLS from QUIC ? https://github.com/quicwg/base-drafts/iss=
ues/941 [-tls] [design] [has-proposal] [quicv2] =

  - Recommended response for empty packets https://github.com/quicwg/base-d=
rafts/issues/1835 =




Pull requests
-------------
* quicwg/base-drafts (+9/-2/=F0=9F=92=AC6)
  9 pull requests submitted:
  - First iteration over transport draft (by janaiyengar)
    https://github.com/quicwg/base-drafts/pull/1857 =

  - Parenthesize 2 * MaxEntries to prevent naive errors (by dtikhonov)
    https://github.com/quicwg/base-drafts/pull/1856 =

  - WIP: Reorganize QPACK (by afrind)
    https://github.com/quicwg/base-drafts/pull/1852 =

  - change the STREAM_ID_BLOCKED frame to encode stream 0 (by marten-seeman=
n)
    https://github.com/quicwg/base-drafts/pull/1851 =

  - Clarify coalesced packet processing (by igorlord)
    https://github.com/quicwg/base-drafts/pull/1844 =

  - Move server send limitations (by martinduke)
    https://github.com/quicwg/base-drafts/pull/1843 =

  - Rename is_handshake_packets in quic-recovery (by martinduke)
    https://github.com/quicwg/base-drafts/pull/1842 =

  - Fix Frame # for RETIRE_CONNECTION_ID (by martinduke)
    https://github.com/quicwg/base-drafts/pull/1841 =

  - Terminate the connection if there are no frames (by ianswett)
    https://github.com/quicwg/base-drafts/pull/1839 =


  3 pull requests received 6 new comments:
  - #1851 change the STREAM_ID_BLOCKED frame to encode stream 0 (4 by marti=
nthomson, marten-seemann, MikeBishop)
    https://github.com/quicwg/base-drafts/pull/1851 =

  - #1841 Fix Frame # for RETIRE_CONNECTION_ID (1 by martinthomson)
    https://github.com/quicwg/base-drafts/pull/1841 =

  - #1844 Clarify coalesced packet processing (1 by igorlord)
    https://github.com/quicwg/base-drafts/pull/1844 =


  2 pull requests merged:
  - Fix Frame # for RETIRE_CONNECTION_ID
    https://github.com/quicwg/base-drafts/pull/1841 =

  - Terminate the connection if there are no frames
    https://github.com/quicwg/base-drafts/pull/1839 =



Repositories tracked by this digest:
-----------------------------------
* https://github.com/quicwg/base-drafts

--===============4472943487960647431==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (QUIC Working Group Specifications)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
</style>
</head>

<body>
<h1>Sunday October 14, 2018</h1>

<p>Events without label "editorial"</p>

<h2>Issues</h2>

<h3>quicwg/base-drafts (+9/-3/=F0=9F=92=AC57)</h3>
  <p class=3D"new">9 issues created:</p>
  <ul>
  <li>#1855 <a href=3D"https://github.com/quicwg/base-drafts/issues/1855">T=
ransport parameter &quot;original connection ID&quot; if no retry</a> (by h=
uitema) </li>
  =

  <li>#1853 <a href=3D"https://github.com/quicwg/base-drafts/issues/1853">D=
oes GOAWAY really need a stream number?</a> (by MikeBishop) <span class=3D"=
label" style=3D"background-color: #fbca04; color: #000000">-http</span> <sp=
an class=3D"label" style=3D"background-color: #1d76db; color: #ffffff">desi=
gn</span> </li>
  =

  <li>#1850 <a href=3D"https://github.com/quicwg/base-drafts/issues/1850">S=
TREAM_ID_BLOCKED frame can&#x27;t encode being blocked on stream 0</a> (by =
marten-seemann) </li>
  =

  <li>#1848 <a href=3D"https://github.com/quicwg/base-drafts/issues/1848">P=
RIORITY frame illustration is unclear</a> (by MikeBishop) </li>
  =

  <li>#1847 <a href=3D"https://github.com/quicwg/base-drafts/issues/1847">H=
TTP SETTINGS: why reuse codepoint 0x3?</a> (by dtikhonov) </li>
  =

  <li>#1846 <a href=3D"https://github.com/quicwg/base-drafts/issues/1846">A=
symmetry in the handling of SETTINGS frame</a> (by kazuho) </li>
  =

  <li>#1845 <a href=3D"https://github.com/quicwg/base-drafts/issues/1845">S=
hould the key update expansion use &quot;quic &quot; or &quot;tls13 &quot;?=
</a> (by huitema) </li>
  =

  <li>#1840 <a href=3D"https://github.com/quicwg/base-drafts/issues/1840">W=
hen to ignore coalesced packets and when to terminate the connection</a> (b=
y igorlord) </li>
  =

  <li>#1838 <a href=3D"https://github.com/quicwg/base-drafts/issues/1838">E=
CN counters and Coalescing of QUIC packets</a> (by gloinul) </li>
  </ul>

  <p>9 issues received 57 new comments:</p>
  <ul>
  <li>#1846 <a href=3D"https://github.com/quicwg/base-drafts/issues/1846">A=
symmetry in the handling of SETTINGS frame</a> (28 by kazuho, afrind, MikeB=
ishop, RyanAtGoogle, lnicco, dtikhonov, LPardue) <span class=3D"label" styl=
e=3D"background-color: #fbca04; color: #000000">-http</span> <span class=3D=
"label" style=3D"background-color: #1d76db; color: #ffffff">design</span> <=
/li>
  =

  <li>#1850 <a href=3D"https://github.com/quicwg/base-drafts/issues/1850">S=
TREAM_ID_BLOCKED frame can&#x27;t encode being blocked on stream 0</a> (12 =
by kazuho, marten-seemann, janaiyengar, mikkelfj, nibanks, ianswett, dtikho=
nov) </li>
  =

  <li>#1853 <a href=3D"https://github.com/quicwg/base-drafts/issues/1853">D=
oes GOAWAY really need a stream number?</a> (6 by kazuho, afrind, MikeBisho=
p) <span class=3D"label" style=3D"background-color: #fbca04; color: #000000=
">-http</span> <span class=3D"label" style=3D"background-color: #1d76db; co=
lor: #ffffff">design</span> </li>
  =

  <li>#1831 <a href=3D"https://github.com/quicwg/base-drafts/issues/1831">O=
ptional packet length field in the short header?</a> (2 by larseggert, ians=
wett) <span class=3D"label" style=3D"background-color: #fbca04; color: #000=
000">-transport</span> </li>
  =

  <li>#1835 <a href=3D"https://github.com/quicwg/base-drafts/issues/1835">R=
ecommended response for empty packets</a> (2 by igorlord, ianswett) </li>
  =

  <li>#1836 <a href=3D"https://github.com/quicwg/base-drafts/issues/1836">&=
quot;Handshake Packet&quot; is Overloaded</a> (2 by martinduke, ianswett) <=
/li>
  =

  <li>#941 <a href=3D"https://github.com/quicwg/base-drafts/issues/941">Res=
ume HTTP/2 TLS from QUIC ?</a> (2 by martinthomson) <span class=3D"label" s=
tyle=3D"background-color: #fbca04; color: #000000">-tls</span> <span class=
=3D"label" style=3D"background-color: #1d76db; color: #ffffff">design</span=
> <span class=3D"label" style=3D"background-color: #c5def5; color: #000000"=
>has-proposal</span> <span class=3D"label" style=3D"background-color: #8e64=
e0; color: #ffffff">quicv2</span> </li>
  =

  <li>#1855 <a href=3D"https://github.com/quicwg/base-drafts/issues/1855">T=
ransport parameter &quot;original connection ID&quot; if no retry</a> (2 by=
 janaiyengar, hardie) </li>
  =

  <li>#1840 <a href=3D"https://github.com/quicwg/base-drafts/issues/1840">W=
hen to ignore coalesced packets and when to terminate the connection</a> (1=
 by MikeBishop) </li>
  </ul>

  <p>3 issues closed:</p>
  <ul>
  <li>#1831 <a href=3D"https://github.com/quicwg/base-drafts/issues/1831">O=
ptional packet length field in the short header?</a> <span class=3D"label" =
style=3D"background-color: #fbca04; color: #000000">-transport</span> </li>
  =

  <li>#941 <a href=3D"https://github.com/quicwg/base-drafts/issues/941">Res=
ume HTTP/2 TLS from QUIC ?</a> <span class=3D"label" style=3D"background-co=
lor: #fbca04; color: #000000">-tls</span> <span class=3D"label" style=3D"ba=
ckground-color: #1d76db; color: #ffffff">design</span> <span class=3D"label=
" style=3D"background-color: #c5def5; color: #000000">has-proposal</span> <=
span class=3D"label" style=3D"background-color: #8e64e0; color: #ffffff">qu=
icv2</span> </li>
  =

  <li>#1835 <a href=3D"https://github.com/quicwg/base-drafts/issues/1835">R=
ecommended response for empty packets</a> </li>
  </ul>



<h2>Pull requests</h2>
<h3>quicwg/base-drafts (+9/-2/=F0=9F=92=AC6)</h3>
  <p class=3D"new">9 pull requests submitted:</p>
  <ul>
  <li>#1857 <a href=3D"https://github.com/quicwg/base-drafts/pull/1857">Fir=
st iteration over transport draft</a> (by janaiyengar) </li>
  =

  <li>#1856 <a href=3D"https://github.com/quicwg/base-drafts/pull/1856">Par=
enthesize 2 * MaxEntries to prevent naive errors</a> (by dtikhonov) </li>
  =

  <li>#1852 <a href=3D"https://github.com/quicwg/base-drafts/pull/1852">WIP=
: Reorganize QPACK</a> (by afrind) </li>
  =

  <li>#1851 <a href=3D"https://github.com/quicwg/base-drafts/pull/1851">cha=
nge the STREAM_ID_BLOCKED frame to encode stream 0</a> (by marten-seemann) =
</li>
  =

  <li>#1844 <a href=3D"https://github.com/quicwg/base-drafts/pull/1844">Cla=
rify coalesced packet processing</a> (by igorlord) </li>
  =

  <li>#1843 <a href=3D"https://github.com/quicwg/base-drafts/pull/1843">Mov=
e server send limitations</a> (by martinduke) </li>
  =

  <li>#1842 <a href=3D"https://github.com/quicwg/base-drafts/pull/1842">Ren=
ame is_handshake_packets in quic-recovery</a> (by martinduke) </li>
  =

  <li>#1841 <a href=3D"https://github.com/quicwg/base-drafts/pull/1841">Fix=
 Frame # for RETIRE_CONNECTION_ID</a> (by martinduke) </li>
  =

  <li>#1839 <a href=3D"https://github.com/quicwg/base-drafts/pull/1839">Ter=
minate the connection if there are no frames</a> (by ianswett) </li>
  </ul>

  <p>3 pull requests received 6 new comments:</p>
  <ul>
  <li>#1851 <a href=3D"https://github.com/quicwg/base-drafts/pull/1851">cha=
nge the STREAM_ID_BLOCKED frame to encode stream 0</a> (4 by martinthomson,=
 marten-seemann, MikeBishop) </li>
  =

  <li>#1841 <a href=3D"https://github.com/quicwg/base-drafts/pull/1841">Fix=
 Frame # for RETIRE_CONNECTION_ID</a> (1 by martinthomson) </li>
  =

  <li>#1844 <a href=3D"https://github.com/quicwg/base-drafts/pull/1844">Cla=
rify coalesced packet processing</a> (1 by igorlord) </li>
  </ul>

  <p>2 pull requests merged:</p>
  <ul>
  <li>#1841 <a href=3D"https://github.com/quicwg/base-drafts/pull/1841">Fix=
 Frame # for RETIRE_CONNECTION_ID</a> </li>
  =

  <li>#1839 <a href=3D"https://github.com/quicwg/base-drafts/pull/1839">Ter=
minate the connection if there are no frames</a> </li>
  </ul>


<h2>Repositories tracked by this digest:</h2>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/quicwg/base-drafts">https://github.com/=
quicwg/base-drafts</a></li>
  </ul>
</body>
</html>

--===============4472943487960647431==--


From nobody Sun Oct 14 10:05:20 2018
Return-Path: <alexandre.ferrieux@orange.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 2D14B127B92 for <quic@ietfa.amsl.com>; Sun, 14 Oct 2018 10:05:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.109
X-Spam-Level: *
X-Spam-Status: No, score=1.109 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 5k5_TXf8HIOA for <quic@ietfa.amsl.com>; Sun, 14 Oct 2018 10:05:17 -0700 (PDT)
Received: from orange.com (mta239.mail.business.static.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6344E130DCA for <quic@ietf.org>; Sun, 14 Oct 2018 10:05:15 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar25.francetelecom.fr (ESMTP service) with ESMTP id 42Y7HF4bbTz8tBY; Sun, 14 Oct 2018 19:05:13 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 42Y7HF3sh1zCqkM; Sun, 14 Oct 2018 19:05:13 +0200 (CEST)
Received: from [10.193.4.89] (10.168.234.4) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sun, 14 Oct 2018 19:05:13 +0200
Subject: Re: Spin bit as a negotiated option
To: IETF QUIC WG <quic@ietf.org>
CC: Kazuho Oku <kazuhooku@gmail.com>
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com> <CY4PR22MB0983849F01312CBE18A4F69CDAEA0@CY4PR22MB0983.namprd22.prod.outlook.com> <HE1PR0701MB2393C0B9756449E5CC060723E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <EEF07499-6E93-46E5-A50A-D2690D670D3C@trammell.ch> <15185_1538742735_5BB759CF_15185_399_1_d9cdb295-d68e-ee43-938e-e3a79003d731@orange.com> <CANatvzztOx72qACw9VWFW1S89Kgn6a+bMTH+qERd57aPXfbaLQ@mail.gmail.com> <AF2ED1E9-B72C-4526-ADC7-77BD4C12D300@trammell.ch>
From: <alexandre.ferrieux@orange.com>
Message-ID: <2158_1539536713_5BC37749_2158_236_1_8bd88e52-0816-279f-d5fb-314be3d16f47@orange.com>
Date: Sun, 14 Oct 2018 19:05:13 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <AF2ED1E9-B72C-4526-ADC7-77BD4C12D300@trammell.ch>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.168.234.4]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/8AH4-107pGyF1GYncmz3ZGiccn0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 14 Oct 2018 17:05:18 -0000

Hello,

FWIW, PicoQuic now implements several "spin bit" variants, to be selected by 
version number as discussed here. Endpoints can thus decide to allow for on-path 
RTT measurement, loss location, both, or none.

_________________________________________________________________________________________________________________________

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.


From nobody Sun Oct 14 20:17:30 2018
Return-Path: <mnot@mnot.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 E1DC5128766 for <quic@ietfa.amsl.com>; Sun, 14 Oct 2018 20:17:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=mnot.net header.b=pdLXn/Yr; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=XvXALyyF
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 NbvsBE-wVdaq for <quic@ietfa.amsl.com>; Sun, 14 Oct 2018 20:17:26 -0700 (PDT)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 803D71286E3 for <quic@ietf.org>; Sun, 14 Oct 2018 20:17:26 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id C3F52449; Sun, 14 Oct 2018 23:17:23 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Sun, 14 Oct 2018 23:17:23 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=from :content-type:content-transfer-encoding:mime-version:subject :message-id:date:cc:to; s=fm3; bh=C+jDtXsvEPfQb0uKtdiOo3nL9rkxpj JBSIsUifCA/uo=; b=pdLXn/Yr6VKda8aw5GnIs4w/fHhnGxpsEMeAGLb10RN8Ds Bl20tl8RGc8sPCAESuXviiS1Hmp5+8gifdPufr7g4jFuwo/789x2AOMy5BVoEaX0 COqBUkAb2wLS2NaDH5NhrsrCMe76R4GaUbDFxDE3P7YfwAM0xRAk5hl8Y79sTwil XUxnuj1Kqq9kepEqi6kBF1RJQYMCg051miCefLM0jH5C1t/9zXmhqgWVUUPflazg /iAc750MjrC9JHSVw5bM2BVuNSzpqStLq07DIX8ttTty04WtqByOEHOPsyTzuaz0 EbTQSNjoMG4ll/jnvIneV8aqDIdQ1wO2lw1Y9Qdw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=C+jDtX svEPfQb0uKtdiOo3nL9rkxpjJBSIsUifCA/uo=; b=XvXALyyFxXwqwLv81IGI+p RlxOflY+3/CRl6R+EtVK5EBKR1Ha9dVeh9DtvZeFJt7fJbOwAt+/q3K5mnxKthCc T1UPaGxJjPni0VacupSsL+Q4qrr4fhP4hJqGVRr8U/MUBHwU9prXSj+o9nqcGsUd RSjCwGgNLloNUtllHQgouo4gJKiVG0jf8/puTQKOBo91r9W/DXnpGsBoxMcxMXx0 Qr6gq8X/uX2fPxcwr/ICpt/XDa/soxITR6ZXRGX0yihZ1ntmGAEeoTvxIBQIwXzN vYIYR4ifeLZdO2Vkbw7ELFUCv4n6WCgsbURBUNg5xQ7ySC5M3UtplFfoVsT/1IOg ==
X-ME-Sender: <xms:wgbEW6GPGr4MGgSP8D6gUb1-qvYakgFttFyaeGWiSyvr5zZEyfQs0A>
X-ME-Proxy: <xmx:wgbEW9zsaJQBPJEp58cxUiSkFdmOaepGP0DSbOZnVWpB0Ps9TIoytQ> <xmx:wgbEW3SfMw3tCrSSyXMpZDU_vf3YMeSNrw1CnLbD3KGdSKQGeDfgxg> <xmx:wgbEW9-qa7-2JRpoFN8twOXN32dSx7O7xzK0uJSdJfvTWanFmf6pig> <xmx:wgbEW9sYqASmXhmXKqiBTsflcw_rVHeD6w9DelI6XHSY8xtCoR-0lA> <xmx:wgbEW9OnjljYdQnoKxxkUeYNoHm4kg-YyF3_EMdx8mN3AqBPo6mp9A> <xmx:wwbEW7_Qdi3gkJFCCSY0k-XWC8oJs9Mxh_C5LqS-ZX4loxrgYF50Cw>
Received: from attitudadjuster.mnot.net (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 098E6E4532; Sun, 14 Oct 2018 23:17:20 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: DRAFT agenda for IETF 103 Bangkok
Message-Id: <B3DBC85D-EF22-45A0-8708-6E00DED10D2B@mnot.net>
Date: Mon, 15 Oct 2018 14:17:17 +1100
Cc: Lars Eggert <lars@eggert.org>
To: IETF QUIC WG <quic@ietf.org>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/SsrAoFRhMXXYqrcBqzZX3eJ-lww>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 15 Oct 2018 03:17:29 -0000

... is at:
  https://github.com/quicwg/wg-materials/blob/master/ietf103/agenda.md

This is just an outline; we'll fill in details about the discussed items =
over the next week or two.

As always, suggestions and additions welcome, either as a response to =
this e-mail or Pull Request.

Cheers,

--
Mark Nottingham   https://www.mnot.net/


From nobody Wed Oct 17 00:59:28 2018
Return-Path: <kazuhooku@gmail.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 C3F6F129AB8 for <quic@ietfa.amsl.com>; Wed, 17 Oct 2018 00:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 QYDAzJc1KVeB for <quic@ietfa.amsl.com>; Wed, 17 Oct 2018 00:59:24 -0700 (PDT)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (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 84A9712D4E9 for <quic@ietf.org>; Wed, 17 Oct 2018 00:59:24 -0700 (PDT)
Received: by mail-lj1-x231.google.com with SMTP id r8-v6so23412336ljc.10 for <quic@ietf.org>; Wed, 17 Oct 2018 00:59:24 -0700 (PDT)
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:content-transfer-encoding; bh=jlOXkLM5fk4k7NLlqcXnh2wuscluST+Fxe83ezWaKCY=; b=N/BBQLbpPVSzBKdZ3e9Rnt1LjS/mOadDlkGW5SlRgvyNJnTmkTpVE50Pp+o4L8vZoi wlHYtvszHJsLbfxeyHWXR2/zu+reF0aW1yq2uV729uYKNrcl5lGWs3TEKORHIfm/u9xj qZO2LeeepqZTN2CnxGqB6CUbrh1KH4w+8I0zCLKQw8hct+bbaFbi2LY3hE+FCeeyhXCM 6FikfCCOob/aLKmVotoSxA63N5B16d1FaPqGFEkegcKghtTDXYJoAR/OxBL4bPtWEqBe QBFYcf2RVkIt5a/Xg1K8ey0HNkUJeN0vFsrdJX8AEKjDpjhjKNeJmr9bBj/HG+TJmVZ6 Nb6A==
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:content-transfer-encoding; bh=jlOXkLM5fk4k7NLlqcXnh2wuscluST+Fxe83ezWaKCY=; b=CPktdnSapRbBt8Tq6aoW7O4QBjEpqfmmmOXth55CPbIWQrR9FY7exj3Pguc12AGnxB vYRAOQzM+iXFCsrMnA7k+0al+ShyCpecmaQoHzZBsyWHjM0p2nkShJNpqinOrUG1wV3U HO9GCa6vqdWhCSy2/216o2Y+3Rch1ke7qK9gMMLCDA9233bdtxKxcZiLdhNJqj/RH24a o9Y8cCreyLJs0Ef1d4PUKc2NPjTbCu4IBql7iHI0L4y8vlhpMUe+AJsepF6KuvcLmUl6 CTOwUjJd+LIGWR3a8jWW9Q0pA1VK2pQPisnqMDtwyjNRoIpAmdq0oob2QH0olgpWgyNd TMIA==
X-Gm-Message-State: ABuFfogdpvyyHMVSgn/9gyLs2AoZM/zGiOwVjE5bqHchmqjPw6PYn6Uc u2lqjSkDZTaqxyHNVvwEGErBW1sgWRy/M9x+yLZ1dVcP
X-Google-Smtp-Source: ACcGV6061bf+WUgbB5hM7chlvrtgZIogXEP8G7oLpu1QBur7uAoaW3bFb2+by8miH2k2/WLs1hWapUUgKpZdyFCE+s4=
X-Received: by 2002:a2e:3918:: with SMTP id g24-v6mr15548305lja.113.1539763162644;  Wed, 17 Oct 2018 00:59:22 -0700 (PDT)
MIME-Version: 1.0
References: <14531_1538460420_5BB30B04_14531_237_4_c0f3a391-9897-80b0-575b-aa73edad0d52@orange.com> <45751C2A-9F6C-4447-8D70-11ABE8C07F8D@trammell.ch> <CANatvzzCvmbu=bN1C-UCzNaT6EUPVCMPwY53wyFNkKa4HQT00g@mail.gmail.com> <E32A1E8D-0FD7-47F3-B026-10D46E201D54@trammell.ch> <21082_1538561186_5BB494A2_21082_335_1_26ed0978-a314-37d1-3c97-5924d62ef539@orange.com> <CANatvzy87Lc-kyzQUcZZS7unvaBQF+DUoEHsd1G0UoPncr4AEQ@mail.gmail.com> <4582_1538649993_5BB5EF89_4582_187_1_98109893-8492-6a58-0534-3fc4eaa09dd9@orange.com> <CY4PR22MB0983849F01312CBE18A4F69CDAEA0@CY4PR22MB0983.namprd22.prod.outlook.com> <HE1PR0701MB2393C0B9756449E5CC060723E2EB0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <EEF07499-6E93-46E5-A50A-D2690D670D3C@trammell.ch> <15185_1538742735_5BB759CF_15185_399_1_d9cdb295-d68e-ee43-938e-e3a79003d731@orange.com> <CANatvzztOx72qACw9VWFW1S89Kgn6a+bMTH+qERd57aPXfbaLQ@mail.gmail.com> <AF2ED1E9-B72C-4526-ADC7-77BD4C12D300@trammell.ch> <2158_1539536713_5BC37749_2158_236_1_8bd88e52-0816-279f-d5fb-314be3d16f47@orange.com>
In-Reply-To: <2158_1539536713_5BC37749_2158_236_1_8bd88e52-0816-279f-d5fb-314be3d16f47@orange.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Wed, 17 Oct 2018 16:59:11 +0900
Message-ID: <CANatvzxXU-xkT2N8EHj4Krgxt4kucKsL7xUveb1hPtAU+xt71w@mail.gmail.com>
Subject: Re: Spin bit as a negotiated option
To: Lili Peaudchien <alexandre.ferrieux@orange.com>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/1ex1IrFmO1EvrV5P2hcF6LkY3zU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 17 Oct 2018 07:59:27 -0000

2018=E5=B9=B410=E6=9C=8815=E6=97=A5(=E6=9C=88) 2:05 <alexandre.ferrieux@ora=
nge.com>:
>
> Hello,
>
> FWIW, PicoQuic now implements several "spin bit" variants, to be selected=
 by
> version number as discussed here. Endpoints can thus decide to allow for =
on-path
> RTT measurement, loss location, both, or none.

Fantastic. It's reassuring to know that it works, and that you are
running multiple variants.

>
> _________________________________________________________________________=
________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confid=
entielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez re=
cu 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 o=
u falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged i=
nformation 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 de=
lete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have bee=
n modified, changed or falsified.
> Thank you.
>


--=20
Kazuho Oku


From nobody Wed Oct 17 09:23:42 2018
Return-Path: <samuelh@rd.bbc.co.uk>
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 35543130DEF for <quic@ietfa.amsl.com>; Wed, 17 Oct 2018 09:23:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 LUyYoUUrneV5 for <quic@ietfa.amsl.com>; Wed, 17 Oct 2018 09:23:39 -0700 (PDT)
Received: from gateh.kw.bbc.co.uk (gateh.kw.bbc.co.uk [132.185.132.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17EA9130DEC for <quic@ietf.org>; Wed, 17 Oct 2018 09:23:38 -0700 (PDT)
Received: from mailhub1.rd.bbc.co.uk ([172.29.120.129]) by gateh.kw.bbc.co.uk (8.14.5+Sun/8.13.6) with ESMTP id w9HGNaLD010373 for <quic@ietf.org>; Wed, 17 Oct 2018 17:23:36 +0100 (BST)
Received: from rd015072.rd.bbc.co.uk ([172.29.91.136]:35036) by mailhub1.rd.bbc.co.uk with esmtp (Exim 4.84_2) (envelope-from <samuelh@rd.bbc.co.uk>) id 1gCobg-00089i-DK for quic@ietf.org; Wed, 17 Oct 2018 17:23:36 +0100
From: Samuel Hurst <samuelh@rd.bbc.co.uk>
Subject: Clarification on HTTP/QUIC Unidirectional Streams
To: IETF QUIC WG <quic@ietf.org>
Message-ID: <272107b2-8136-48cc-f429-efcea1231d78@rd.bbc.co.uk>
Date: Wed, 17 Oct 2018 17:23:36 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/assCVGvT2Cl7wPk_zFeOrVI9UP4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 17 Oct 2018 16:23:41 -0000

Hi All,


Apologies if this question has been asked before, but I'd just like to 
check that my understanding of something is correct and searching back 
through the list has not answered my question.

Given that HTTP/QUIC requires each peer in a connection to open a 
unidirectional control stream when a connection begins, I think it's 
safe to assume that streams 2 and 3 will be the control streams.

Now, a client will make a request on Stream 0, which will include some 
QPACK HEADERS, and the odds are that some of those headers will be poked 
into the dynamic table (I'm thinking of the User-Agent as a prime 
candidate for this).

However, as I understand it, QPACK requires two unidirectional control 
streams for the encode (type 'H') and decode (type 'h'). And this is per 
encode-decode pair, so there will be another pair of unidirectional 
control streams for the encode and decode of the server's response headers.

So in my head, the current state of streams in use is thus:

Stream 0 - Client Request
Stream 2 - Client Control Stream
Stream 3 - Server Control Stream
Stream 6 - Client Headers QPACK Encoder Stream
Stream 7 - Client Headers QPACK Decoder Stream
Stream 10 - Server Headers QPACK Decoder Stream
Stream 11 - Server Headers QPACK Encoder Stream

So, if as part of the request made in stream 0, the server decides to 
send a PUSH_PROMISE frame, and then once acknowledged by the client the 
server begins the server push immediately, is is a safe assumption to 
make that the first server push stream will be on stream 15?

I also don't think there's anything to stop a server from sending a 
PUSH_PROMISE frame before it's even sent a HEADERS frame back for the 
initial request, so in that case would the server push end up on stream 
11, the server headers encoder stream ends up on stream 15 and the 
decoder stream stays on stream 10?

I'm just trying to get it into my head exactly what the expected lay of 
the land will be during a running HTTP/QUIC session. It's been a while 
since I last looked at the QUIC drafts and I'm jumping ahead through 
several revisions so it's possible that I've missed something.


Best Regards,
Sam


From nobody Wed Oct 17 10:42:30 2018
Return-Path: <mikkelfj@gmail.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 9D860130E19 for <quic@ietfa.amsl.com>; Wed, 17 Oct 2018 10:42:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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_PASS=-0.001, UNPARSEABLE_RELAY=0.001] 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 m4a8vvXlHOc7 for <quic@ietfa.amsl.com>; Wed, 17 Oct 2018 10:42:26 -0700 (PDT)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (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 2CB4C130E02 for <quic@ietf.org>; Wed, 17 Oct 2018 10:42:26 -0700 (PDT)
Received: by mail-ot1-x32a.google.com with SMTP id c23so25260337otl.9 for <quic@ietf.org>; Wed, 17 Oct 2018 10:42:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to;  bh=Oun8scUL55sifzB9xK0d7AskPDWCnkOBnTA5Rnl7kpE=; b=i/gwbHzXRjkwx1sumPcT8YIyspUD8orFU9UoSDxBe7toItIys/c2TLlDpSPD67C6LV keo9zCEV64nxG1nbBnsv3doDieAkHMnM7QXhyD94rOFQ/+mjcbEC+oZ02wKUeScHz2Vr 6vGZZrbmQ6IFJrtAiX5auqzlWfCme0eszNx4LjSg0GaLKzYPzYrki+HrJpT410w4saHX VMkuRomMjzHgcbG4ixFjhhVK3rLDS4MjN3SglD/GZg+HygR7JIEIC4d5zJji5z8nSj2H mr2WdoBsX9/pQ4LBjp2sFYU3Js47dns4OOWHAiUOelARhOC7b2c7jOshQh+2J74mfb6x qbSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to; bh=Oun8scUL55sifzB9xK0d7AskPDWCnkOBnTA5Rnl7kpE=; b=SzLybmmviewhl6HAnnaYGwiBHKTlvgsNl2ZhS6Y4bmQ5rJOMqle+iaGVO4aAIODaZe OhWue/v/5ojiS77ydKb9bGvo0rOLdqUleBkACRnv38OkdkZBoqRRvqgBgQLdaREVEdRm d6iBKSpRTJ0D9u58GIqRybRosszze4f7GYbmG7roNu+Cwtnm32QphA+Jx3DrsLw2I8xv KWCVybNuUiSpk2RqLeElXHQKWvJ3XK3WmkYyEVSV6UmMoWa83Kos2zyYM+ejlodMRSNq J+PdxHUvfFhVrrW4f9VBQE5QI9y+PsqItBDW2jIbVVbtuVxY//dPcbdkuUOU/4rx8N3P LKRw==
X-Gm-Message-State: ABuFfoj210SwG/UX6nlkT9YW45qSivDGEh8o0c1BkfOpDHjamrbMiH5x szpEK3JyvASgqVuWSDHCdu6Ra6wHQfnDTWMxqIEhmg==
X-Google-Smtp-Source: ACcGV62fbFiKOXvJeDY5nPfooarlcjzvTO3bNI11hNlv0YS7AW4HG+CbWQmmlJbtVQp0flLtHiSYhWO+KO6PflA9z5w=
X-Received: by 2002:a9d:52a4:: with SMTP id f36mr18162738oth.186.1539798145231;  Wed, 17 Oct 2018 10:42:25 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 17 Oct 2018 10:42:24 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <272107b2-8136-48cc-f429-efcea1231d78@rd.bbc.co.uk>
References: <272107b2-8136-48cc-f429-efcea1231d78@rd.bbc.co.uk>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Wed, 17 Oct 2018 10:42:24 -0700
Message-ID: <CAN1APddZzF-Cr77r5rvrsnwAwY_tnBRhkzviC=190sDuWr1Xtw@mail.gmail.com>
Subject: Re: Clarification on HTTP/QUIC Unidirectional Streams
To: IETF QUIC WG <quic@ietf.org>, Samuel Hurst <samuelh@rd.bbc.co.uk>
Content-Type: multipart/alternative; boundary="00000000000078f2ab057870318f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/O6T7xE7hJ050h-i0ppdwA0sSTkQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 17 Oct 2018 17:42:29 -0000

--00000000000078f2ab057870318f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I=E2=80=99m not at all into all the details of HQ/QPACK

but you cannot assume anything about stream identifiers before you see them=
.

If stream 2 is an obvious control streams, some implementation will make
stream 8 the initial control stream because it will have some idea idea
about forcing the earlier streams open so the peer can do something evil to
them before it even begins sending data. Or they might just do it for the
heck of it to break applications making such assumptions (like ping of
death).

Some implementation could have fewer streams because they are
micro-controllers that do not want to use QPACK compression at all, so
assuming server push on stream 15 would possibly work most of the time at
best.

On 17 October 2018 at 18.23.57, Samuel Hurst (samuelh@rd.bbc.co.uk) wrote:

Hi All,


Apologies if this question has been asked before, but I'd just like to
check that my understanding of something is correct and searching back
through the list has not answered my question.

Given that HTTP/QUIC requires each peer in a connection to open a
unidirectional control stream when a connection begins, I think it's
safe to assume that streams 2 and 3 will be the control streams.

Now, a client will make a request on Stream 0, which will include some
QPACK HEADERS, and the odds are that some of those headers will be poked
into the dynamic table (I'm thinking of the User-Agent as a prime
candidate for this).

However, as I understand it, QPACK requires two unidirectional control
streams for the encode (type 'H') and decode (type 'h'). And this is per
encode-decode pair, so there will be another pair of unidirectional
control streams for the encode and decode of the server's response headers.

So in my head, the current state of streams in use is thus:

Stream 0 - Client Request
Stream 2 - Client Control Stream
Stream 3 - Server Control Stream
Stream 6 - Client Headers QPACK Encoder Stream
Stream 7 - Client Headers QPACK Decoder Stream
Stream 10 - Server Headers QPACK Decoder Stream
Stream 11 - Server Headers QPACK Encoder Stream

So, if as part of the request made in stream 0, the server decides to
send a PUSH_PROMISE frame, and then once acknowledged by the client the
server begins the server push immediately, is is a safe assumption to
make that the first server push stream will be on stream 15?

I also don't think there's anything to stop a server from sending a
PUSH_PROMISE frame before it's even sent a HEADERS frame back for the
initial request, so in that case would the server push end up on stream
11, the server headers encoder stream ends up on stream 15 and the
decoder stream stays on stream 10?

I'm just trying to get it into my head exactly what the expected lay of
the land will be during a running HTTP/QUIC session. It's been a while
since I last looked at the QUIC drafts and I'm jumping ahead through
several revisions so it's possible that I've missed something.


Best Regards,
Sam

--00000000000078f2ab057870318f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">I=E2=80=99m not at a=
ll into all the details of HQ/QPACK</div><div id=3D"bloop_customfont" style=
=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin=
:0px;line-height:auto"><br></div><div id=3D"bloop_customfont" style=3D"font=
-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;lin=
e-height:auto">but you cannot assume anything about stream identifiers befo=
re you see them.</div><div id=3D"bloop_customfont" style=3D"font-family:Hel=
vetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:au=
to"><br></div><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,A=
rial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">If s=
tream 2 is an obvious control streams, some implementation will make stream=
 8 the initial control stream because it will have some idea idea about for=
cing the earlier streams open so the peer can do something evil to them bef=
ore it even begins sending data. Or they might just do it for the heck of i=
t to break applications making such assumptions (like ping of death).</div>=
<div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size=
:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id=
=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;c=
olor:rgba(0,0,0,1.0);margin:0px;line-height:auto">Some implementation could=
 have fewer streams because they are micro-controllers that do not want to =
use QPACK compression at all, so assuming server push on stream 15 would po=
ssibly work most of the time at best.</div> <br><p class=3D"airmail_on">On =
17 October 2018 at 18.23.57, Samuel Hurst (<a href=3D"mailto:samuelh@rd.bbc=
.co.uk">samuelh@rd.bbc.co.uk</a>) wrote:</p> <blockquote type=3D"cite" clas=
s=3D"clean_bq"><span><div><div></div><div>Hi All,
<br>
<br>
<br>Apologies if this question has been asked before, but I&#39;d just like=
 to =20
<br>check that my understanding of something is correct and searching back =
=20
<br>through the list has not answered my question.
<br>
<br>Given that HTTP/QUIC requires each peer in a connection to open a =20
<br>unidirectional control stream when a connection begins, I think it&#39;=
s =20
<br>safe to assume that streams 2 and 3 will be the control streams.
<br>
<br>Now, a client will make a request on Stream 0, which will include some =
=20
<br>QPACK HEADERS, and the odds are that some of those headers will be poke=
d =20
<br>into the dynamic table (I&#39;m thinking of the User-Agent as a prime =
=20
<br>candidate for this).
<br>
<br>However, as I understand it, QPACK requires two unidirectional control =
=20
<br>streams for the encode (type &#39;H&#39;) and decode (type &#39;h&#39;)=
. And this is per =20
<br>encode-decode pair, so there will be another pair of unidirectional =20
<br>control streams for the encode and decode of the server&#39;s response =
headers.
<br>
<br>So in my head, the current state of streams in use is thus:
<br>
<br>Stream 0 - Client Request
<br>Stream 2 - Client Control Stream
<br>Stream 3 - Server Control Stream
<br>Stream 6 - Client Headers QPACK Encoder Stream
<br>Stream 7 - Client Headers QPACK Decoder Stream
<br>Stream 10 - Server Headers QPACK Decoder Stream
<br>Stream 11 - Server Headers QPACK Encoder Stream
<br>
<br>So, if as part of the request made in stream 0, the server decides to =
=20
<br>send a PUSH_PROMISE frame, and then once acknowledged by the client the=
 =20
<br>server begins the server push immediately, is is a safe assumption to =
=20
<br>make that the first server push stream will be on stream 15?
<br>
<br>I also don&#39;t think there&#39;s anything to stop a server from sendi=
ng a =20
<br>PUSH_PROMISE frame before it&#39;s even sent a HEADERS frame back for t=
he =20
<br>initial request, so in that case would the server push end up on stream=
 =20
<br>11, the server headers encoder stream ends up on stream 15 and the =20
<br>decoder stream stays on stream 10?
<br>
<br>I&#39;m just trying to get it into my head exactly what the expected la=
y of =20
<br>the land will be during a running HTTP/QUIC session. It&#39;s been a wh=
ile =20
<br>since I last looked at the QUIC drafts and I&#39;m jumping ahead throug=
h =20
<br>several revisions so it&#39;s possible that I&#39;ve missed something.
<br>
<br>
<br>Best Regards,
<br>Sam
<br>
<br></div></div></span></blockquote></body></html>

--00000000000078f2ab057870318f--


From nobody Wed Oct 17 10:52:14 2018
Return-Path: <dtikhonov@litespeedtech.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 31165130E19 for <quic@ietfa.amsl.com>; Wed, 17 Oct 2018 10:52:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 k6F-RfC_U3mz for <quic@ietfa.amsl.com>; Wed, 17 Oct 2018 10:52:10 -0700 (PDT)
Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (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 11764130E02 for <quic@ietf.org>; Wed, 17 Oct 2018 10:52:10 -0700 (PDT)
Received: by mail-qt1-x82d.google.com with SMTP id o17-v6so31130821qtr.1 for <quic@ietf.org>; Wed, 17 Oct 2018 10:52:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=dS8biGifFXESIO/SwWeX5nzzHD5mz7QgQJLTqyG+PSU=; b=epIuP2bNvPtKvaSB2XKh3qi1VS4wZR7BxmbLTJa2aMHnfCNv+sxQWiCyPzfqtolNWg JiKAtc8o57r+ZhKPWM3zslQu4e+ycxDfwikk1JSF26+5hwTJden0xbjrc9ut0AHFfNBs 6pxWbTrp4PnoyJue8KTe1y4rg/9bA5wREkBDfvri7XRqFgS+x42oxr6SmqZVG+5IFo+8 OvHNtJD4pqKqW87g1J5QtcxCIt2rSiBF2pW6Tssv89eSrxM5OafSGPOvgN7bAyFpjWH4 5QlVlVP/8ErhzQuh0YBErccuXOJPIoReX6DYqGIgMrL1gZrsNJsjRzzT+Vmp6TJkzOzF xCVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=dS8biGifFXESIO/SwWeX5nzzHD5mz7QgQJLTqyG+PSU=; b=kaXbo3kOJAiyGDt40ZLJGnaJuNbAKTEAy/lKplDtARiSmnB9zO9HtLbv7Rxl1ZCVL8 fj9mi7no09VfrKCdkCJHUh/xB9Yi3pltP5uA9CnXSjjqVY5rEpRA6+tiZyzK4RGUcXpJ bVbpJu/a60awG8+UrvSdT+0VKUjUoL4ehwGWnjUxXjqoLmx28oPHvzUyCTeDyNTySplg GNWdHKwLDvgDh7VIUThYcZuWtpbGGsI9HkwulHadujZmY4fV/cBicZ/np2dBMjmxPBWd aZHZtx917K/vdNWISlrRD+NHMEI4Op++UzXE2/sSPirrNulcegL4Lm2WDTe5SNvF1PHI FyIQ==
X-Gm-Message-State: ABuFfoixvle83wwDXrV7TzQb9Q+yzcLgy+a22rTM8pqQKCxsSThWJ6Tr 17yw2TrnIPrBEifFvJl2j0R1vg==
X-Google-Smtp-Source: ACcGV60BGBba9XKvOjheIT4xs1hvPjb0XoqQ6jFp/sNr7TC9mLeHKRjeuFojLP+tFaHgL2MuWISqgQ==
X-Received: by 2002:aed:206e:: with SMTP id 101-v6mr25681248qta.11.1539798729204;  Wed, 17 Oct 2018 10:52:09 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id l97-v6sm9222140qte.21.2018.10.17.10.52.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 17 Oct 2018 10:52:08 -0700 (PDT)
Date: Wed, 17 Oct 2018 13:52:04 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Mikkel =?iso-8859-1?Q?Fahn=F8e_J=F8rgensen?= <mikkelfj@gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>, Samuel Hurst <samuelh@rd.bbc.co.uk>
Subject: Re: Clarification on HTTP/QUIC Unidirectional Streams
Message-ID: <20181017175203.GA18782@ubuntu-dmitri>
Mail-Followup-To: Mikkel =?iso-8859-1?Q?Fahn=F8e_J=F8rgensen?= <mikkelfj@gmail.com>,  IETF QUIC WG <quic@ietf.org>, Samuel Hurst <samuelh@rd.bbc.co.uk>
References: <272107b2-8136-48cc-f429-efcea1231d78@rd.bbc.co.uk> <CAN1APddZzF-Cr77r5rvrsnwAwY_tnBRhkzviC=190sDuWr1Xtw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAN1APddZzF-Cr77r5rvrsnwAwY_tnBRhkzviC=190sDuWr1Xtw@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/uUYgWMonk2dN-dK5skxrmEMKgw0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 17 Oct 2018 17:52:12 -0000

On Wed, Oct 17, 2018 at 10:42:24AM -0700, Mikkel Fahnøe Jørgensen wrote:
> I’m not at all into all the details of HQ/QPACK
> 
> but you cannot assume anything about stream identifiers before you see them..

Amen.  This is the WG consensus: do not rely on stream IDs being
assigned to particular streams in HTTP/QUIC.

  - Dmitri.


From nobody Thu Oct 18 01:46:20 2018
Return-Path: <samuelh@rd.bbc.co.uk>
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 225891292F1 for <quic@ietfa.amsl.com>; Thu, 18 Oct 2018 01:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 h5eymkZ9QMyL for <quic@ietfa.amsl.com>; Thu, 18 Oct 2018 01:46:18 -0700 (PDT)
Received: from gateh.kw.bbc.co.uk (gateh.kw.bbc.co.uk [132.185.132.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A57C3128CF3 for <quic@ietf.org>; Thu, 18 Oct 2018 01:46:18 -0700 (PDT)
Received: from mailhub1.rd.bbc.co.uk ([172.29.120.129]) by gateh.kw.bbc.co.uk (8.14.5+Sun/8.13.6) with ESMTP id w9I8kGZ4003649 for <quic@ietf.org>; Thu, 18 Oct 2018 09:46:16 +0100 (BST)
Received: from rd015072.rd.bbc.co.uk ([172.29.91.136]:54102) by mailhub1.rd.bbc.co.uk with esmtp (Exim 4.84_2) (envelope-from <samuelh@rd.bbc.co.uk>) id 1gD3wd-0000Lg-Uy for quic@ietf.org; Thu, 18 Oct 2018 09:46:16 +0100
Subject: Re: Clarification on HTTP/QUIC Unidirectional Streams
To: quic@ietf.org
References: <272107b2-8136-48cc-f429-efcea1231d78@rd.bbc.co.uk> <CAN1APddZzF-Cr77r5rvrsnwAwY_tnBRhkzviC=190sDuWr1Xtw@mail.gmail.com>
From: Samuel Hurst <samuelh@rd.bbc.co.uk>
Message-ID: <1990abd4-7112-0620-061a-3f88950eb2e1@rd.bbc.co.uk>
Date: Thu, 18 Oct 2018 09:46:15 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <CAN1APddZzF-Cr77r5rvrsnwAwY_tnBRhkzviC=190sDuWr1Xtw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/BEZ5pdtfXXbEDD8Mqumfw4OMWV4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 18 Oct 2018 08:46:20 -0000

On 17/10/2018 18:42, Mikkel Fahnøe Jørgensen wrote:
> I’m not at all into all the details of HQ/QPACK
> 
> but you cannot assume anything about stream identifiers before you see them.
> 
> If stream 2 is an obvious control streams, some implementation will make 
> stream 8 the initial control stream because it will have some idea idea 
> about forcing the earlier streams open so the peer can do something evil 
> to them before it even begins sending data. Or they might just do it for 
> the heck of it to break applications making such assumptions (like ping 
> of death).

Oh absolutely, but I was more thinking of an example flow with a client 
behaving in an at least somewhat predictable and not malicious manner. 
I'm mostly trying to sort out in my head how the QPACK encoder/decoder 
streams work together, apologies if that wasn't as clear as it could've 
been.

I'm fully aware that a client could open as many unidirectional streams 
as it likes and as long as it doesn't do anything else on those streams 
before starting a control stream somewhere.

And if something opens a control stream on Stream 8, shouldn't that be a 
protocol error, as stream 8 is not a unidirectional stream?

> Some implementation could have fewer streams because they are 
> micro-controllers that do not want to use QPACK compression at all, so 
> assuming server push on stream 15 would possibly work most of the time 
> at best.

There's nothing in the specs that specifies when the QPACK 
encoder/decoder streams are opened, so I was going on the assumption 
that they are only opened when a client wants to use the dynamic table. 
If a client only wants to send literal headers or reference in the 
static table, or if the table size is set to zero in the SETTINGS frame, 
I'd assume the QPACK streams will not be opened. In which case, the 
first server push could be stream 7.

-Sam


From nobody Thu Oct 18 01:49:36 2018
Return-Path: <mikkelfj@gmail.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 C6B591292F1 for <quic@ietfa.amsl.com>; Thu, 18 Oct 2018 01:49:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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_PASS=-0.001, UNPARSEABLE_RELAY=0.001] 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 a9EWnVryF4KG for <quic@ietfa.amsl.com>; Thu, 18 Oct 2018 01:49:33 -0700 (PDT)
Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (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 195FA128CF3 for <quic@ietf.org>; Thu, 18 Oct 2018 01:49:33 -0700 (PDT)
Received: by mail-oi1-x22f.google.com with SMTP id 22-v6so23395509oiz.2 for <quic@ietf.org>; Thu, 18 Oct 2018 01:49:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to;  bh=Y6E2+r02TKwrpMZmhzpLS+DlkYd0eccgw0Y531BYjBo=; b=EhOoCldcHmX6XfoQfysmaOTmHgQwrQx7tE5alMW3Bi6IXB4g3MLCUQtOaswhn909Np RR7Vio2rMoHyu5l8MxjZQ1SSUQ3nUfxDvNyKtfHwRiad9MetS6uKh2Aw8H9sXS+sk1mt 6iY9LkPTf1wvmny0/vtBjISd2Hpo67RS+NOufJUgcOQRbEVe45YCUEY4Qgu6eYkHkR/n l6PJZW1dxQp+Ghaer6XnK85mycZaAyiB1dqTtd+r4ZnqxrOHLsfNGJYSN28c/EMjQ3uA lVME11B2E8YmhmkxEAcDQk1HegyIuGv26GkSQAL5Gdq+5qzcb1ZySRsv0KTy4yPsAfqn YYTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to; bh=Y6E2+r02TKwrpMZmhzpLS+DlkYd0eccgw0Y531BYjBo=; b=cVO4DSMil2ieUQyU95H04YjVDj6gaU3V1llA9nUt/0KoBFzCbXsEygEkO9+Baf+eYK 7tWFnBvq7XNExWkcg8XlgcKBGitwVFCwGpM3sE7SJbGJ8OKBk0Jimxe3pBtoZsjCtN4g dDC3arsBKFMdzARgd+GPchriimp5YEKTEXT2xsHGbKBhxUK+LJ9jCWzOnnwfTEUjKbTR yyLjRKWzcTr6VA6ilfB8zMuqwhvrG2ZE+ll7XFdPHPoOZQwNOd6e5v6l18OW4twB+xVL GM1swKfXIGfONqDGWLnGAsxiQt4chXayhQc1WoENsOoWeKcxqNdYZmgcqqJa2IA2zOIV JEhA==
X-Gm-Message-State: ABuFfohWr+Zsb+YA1hwWHtVyPErRncQ21bhu5wLJNPpE9ItOzGAZmp0e 6I56/4xLtwrAcnNu66zB4tYvIvyAjj+QJ3TJtjOAAg==
X-Google-Smtp-Source: ACcGV61sgYjxAKqiny9UXC+RJHxji/G54FP0aEfwEpJqLQXnWefoewjx4OL+sA2HDdKuKtx0iEXwUXy9l6bCCNa5ljU=
X-Received: by 2002:aca:5bc5:: with SMTP id p188-v6mr16422303oib.339.1539852572259;  Thu, 18 Oct 2018 01:49:32 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 18 Oct 2018 10:49:31 +0200
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <1990abd4-7112-0620-061a-3f88950eb2e1@rd.bbc.co.uk>
References: <272107b2-8136-48cc-f429-efcea1231d78@rd.bbc.co.uk> <CAN1APddZzF-Cr77r5rvrsnwAwY_tnBRhkzviC=190sDuWr1Xtw@mail.gmail.com> <1990abd4-7112-0620-061a-3f88950eb2e1@rd.bbc.co.uk>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Thu, 18 Oct 2018 10:49:31 +0200
Message-ID: <CAN1APdf9-6MJ-1fZfrNzJ9KJ8Kw=ccaaOfGmruOjTbjJ2E4b_A@mail.gmail.com>
Subject: Re: Clarification on HTTP/QUIC Unidirectional Streams
To: quic@ietf.org, Samuel Hurst <samuelh@rd.bbc.co.uk>
Content-Type: multipart/alternative; boundary="00000000000093791105787cdd3f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/FN1sME3SIDLtCQBu3icLlNCGPMY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 18 Oct 2018 08:49:35 -0000

--00000000000093791105787cdd3f
Content-Type: text/plain; charset="UTF-8"

On 18 October 2018 at 10.46.34, Samuel Hurst (samuelh@rd.bbc.co.uk) wrote:

And if something opens a control stream on Stream 8, shouldn't that be a
protocol error, as stream 8 is not a unidirectional stream?

That was a typo, I meant 10.

--00000000000093791105787cdd3f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">On 18 October 2018 a=
t 10.46.34, Samuel Hurst (<a href=3D"mailto:samuelh@rd.bbc.co.uk">samuelh@r=
d.bbc.co.uk</a>) wrote:</div> <div><blockquote type=3D"cite" class=3D"clean=
_bq" style=3D"font-family:Helvetica,Arial;font-size:13px;font-style:normal;=
font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-alig=
n:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing=
:0px;text-decoration:none"><span><div><span style=3D"color:rgb(0,0,0);font-=
family:&quot;helvetica Neue&quot;,helvetica;font-size:14px;font-style:norma=
l;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-al=
ign:start;text-indent:0px;text-transform:none;white-space:normal;word-spaci=
ng:0px;background-color:rgb(255,255,255);text-decoration:none;float:none;di=
splay:inline!important">And if something opens a control stream on Stream 8=
, shouldn&#39;t that be a<span class=3D"Apple-converted-space">=C2=A0</span=
></span><br style=3D"color:rgb(0,0,0);font-family:&quot;helvetica Neue&quot=
;,helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-=
weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-t=
ransform:none;white-space:normal;word-spacing:0px;text-decoration:none"><sp=
an style=3D"color:rgb(0,0,0);font-family:&quot;helvetica Neue&quot;,helveti=
ca;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:no=
rmal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:=
none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);=
text-decoration:none;float:none;display:inline!important">protocol error, a=
s stream 8 is not a unidirectional stream?<span class=3D"Apple-converted-sp=
ace">=C2=A0</span></span></div></span></blockquote></div><p>That was a typo=
, I meant 10.</p><div></div></body></html>

--00000000000093791105787cdd3f--


From nobody Thu Oct 18 01:54:46 2018
Return-Path: <mikkelfj@gmail.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 642471292F1 for <quic@ietfa.amsl.com>; Thu, 18 Oct 2018 01:54:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.738
X-Spam-Level: 
X-Spam-Status: No, score=-1.738 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, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] 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 pKJYeZBxY99k for <quic@ietfa.amsl.com>; Thu, 18 Oct 2018 01:54:43 -0700 (PDT)
Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (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 EC9BC128CF3 for <quic@ietf.org>; Thu, 18 Oct 2018 01:54:42 -0700 (PDT)
Received: by mail-oi1-x22f.google.com with SMTP id l197-v6so23368689oib.8 for <quic@ietf.org>; Thu, 18 Oct 2018 01:54:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to;  bh=9OEsA1MMqjeCqYeiD7dkkNuLeXi1ZY+3o4aP3ysG0tc=; b=t8tnMNPS5XeXe8oINlwVxO5IysG1Dd28n+2PQfsytIkpYPp/KLd4mExkfq0OcBxGI/ 9M5Q5T2WagtlApm5O2P1pXfsxfsDtXucf24jRS8+gG6QdeKeQZPZXPKtXkbfbFGcf3Q6 2Blj5O+4OXNLgRL5I08UNQ+M/7W4Did4t7FG5DUgyVwwIdIgm1SozwSZYcAVeqlkH2QX 1/8153VPUIG8LMYY5420GnvoOKuWBgNx05M4ju0HXxsPR/jnmEMQ88jH2s6C0rznQdN3 MamuCVvxjV3ga+Nv1ZX5dv4VNtaNKy+epSHQbN1CgGpuV4u933dqjs1O59ILFHzItg7F ++4A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to; bh=9OEsA1MMqjeCqYeiD7dkkNuLeXi1ZY+3o4aP3ysG0tc=; b=qrTys1E1i40Jpyadje0zS5/3JJvWED3GkIuT1EuBumAZWrmXIYV317tHM3v0zXH17K 90pbl/7Z36COxKaCxy1tin7KUiz2BPoqCRfr7lN0tEQ7MdKiik/7mi9DGHPdbvXXCtpP RTrhTxPFUs1OhnbtG5l0FNE/z+Li2S2O0phtd1CDM11O5UMyF9xnYbJL21egGNfGhclN LR5ebxEl5HvBviIx4Vdj7q+sIyfppsR+Bb6rAynewtbbnm6DD3QOLxsKE43EPwGJbA+Y MtM0klwS1IbxhcFrQchRBjmiHwBk80LdwdBSR/LaJdbm04DREPqMdXx9Gbu8xNc2rFzI E6Mw==
X-Gm-Message-State: ABuFfoi4tmSbWcsA6OFhuOByKScSZRpoxzhEJ/4LMfcnbzU7WVdc1O+J TRFaPOKF7UCzWWan21MnKm7lXZxWcvleTajDj5t/cg==
X-Google-Smtp-Source: ACcGV63Ww+oenSkHviUC8nC96NDbKWvLsiuWRVM1uNBVf6tS8tjIE9esBSP5OQrxd3i2x+Ct7me4L9axgK7Ode5rg1w=
X-Received: by 2002:aca:49c8:: with SMTP id w191-v6mr15016514oia.114.1539852882252;  Thu, 18 Oct 2018 01:54:42 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 18 Oct 2018 10:54:41 +0200
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <1990abd4-7112-0620-061a-3f88950eb2e1@rd.bbc.co.uk>
References: <272107b2-8136-48cc-f429-efcea1231d78@rd.bbc.co.uk> <CAN1APddZzF-Cr77r5rvrsnwAwY_tnBRhkzviC=190sDuWr1Xtw@mail.gmail.com> <1990abd4-7112-0620-061a-3f88950eb2e1@rd.bbc.co.uk> <1990abd4-7112-0620-061a-3f88950eb2e1@rd.bbc.co.uk>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Thu, 18 Oct 2018 10:54:41 +0200
Message-ID: <CAN1APdebfcjMkTLqo57kzsckenJAa+P3Zw-Up=Jq3TPa2fAcwA@mail.gmail.com>
Subject: Re: Clarification on HTTP/QUIC Unidirectional Streams
To: quic@ietf.org, Samuel Hurst <samuelh@rd.bbc.co.uk>
Content-Type: multipart/alternative; boundary="0000000000000d9ac005787cf00c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/18856Wjm-rko8GAYvU52l2hWjGQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 18 Oct 2018 08:54:45 -0000

--0000000000000d9ac005787cf00c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On 18 October 2018 at 10.46.34, Samuel Hurst (samuelh@rd.bbc.co.uk) wrote:

> Some implementation could have fewer streams because they are
> micro-controllers that do not want to use QPACK compression at all, so
> assuming server push on stream 15 would possibly work most of the time
> at best.

There's nothing in the specs that specifies when the QPACK
encoder/decoder streams are opened, so I was going on the assumption
that they are only opened when a client wants to use the dynamic table.


I=E2=80=99m not really sure where this landed, but there was some discussio=
n here:
https://github.com/quicwg/base-drafts/issues/1747

--0000000000000d9ac005787cf00c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">On 18 October 2018 a=
t 10.46.34, Samuel Hurst (<a href=3D"mailto:samuelh@rd.bbc.co.uk">samuelh@r=
d.bbc.co.uk</a>) wrote:</div> <div><blockquote type=3D"cite" class=3D"clean=
_bq" style=3D"font-family:Helvetica,Arial;font-size:13px;font-style:normal;=
font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-alig=
n:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing=
:0px;text-decoration:none"><span><div><span style=3D"color:rgb(0,0,0);font-=
family:&quot;helvetica Neue&quot;,helvetica;font-size:14px;font-style:norma=
l;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-al=
ign:start;text-indent:0px;text-transform:none;white-space:normal;word-spaci=
ng:0px;background-color:rgb(255,255,255);text-decoration:none;float:none;di=
splay:inline!important">&gt; Some implementation could have fewer streams b=
ecause they are<span class=3D"Apple-converted-space">=C2=A0</span></span><b=
r style=3D"color:rgb(0,0,0);font-family:&quot;helvetica Neue&quot;,helvetic=
a;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:nor=
mal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:n=
one;white-space:normal;word-spacing:0px;text-decoration:none"><span style=
=3D"color:rgb(0,0,0);font-family:&quot;helvetica Neue&quot;,helvetica;font-=
size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;let=
ter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;whi=
te-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-dec=
oration:none;float:none;display:inline!important">&gt; micro-controllers th=
at do not want to use QPACK compression at all, so<span class=3D"Apple-conv=
erted-space">=C2=A0</span></span><br style=3D"color:rgb(0,0,0);font-family:=
&quot;helvetica Neue&quot;,helvetica;font-size:14px;font-style:normal;font-=
variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:sta=
rt;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;=
text-decoration:none"><span style=3D"color:rgb(0,0,0);font-family:&quot;hel=
vetica Neue&quot;,helvetica;font-size:14px;font-style:normal;font-variant-c=
aps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-i=
ndent:0px;text-transform:none;white-space:normal;word-spacing:0px;backgroun=
d-color:rgb(255,255,255);text-decoration:none;float:none;display:inline!imp=
ortant">&gt; assuming server push on stream 15 would possibly work most of =
the time<span class=3D"Apple-converted-space">=C2=A0</span></span><br style=
=3D"color:rgb(0,0,0);font-family:&quot;helvetica Neue&quot;,helvetica;font-=
size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;let=
ter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;whi=
te-space:normal;word-spacing:0px;text-decoration:none"><span style=3D"color=
:rgb(0,0,0);font-family:&quot;helvetica Neue&quot;,helvetica;font-size:14px=
;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spaci=
ng:normal;text-align:start;text-indent:0px;text-transform:none;white-space:=
normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration:n=
one;float:none;display:inline!important">&gt; at best.<span class=3D"Apple-=
converted-space">=C2=A0</span></span><br style=3D"color:rgb(0,0,0);font-fam=
ily:&quot;helvetica Neue&quot;,helvetica;font-size:14px;font-style:normal;f=
ont-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align=
:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:=
0px;text-decoration:none"><br style=3D"color:rgb(0,0,0);font-family:&quot;h=
elvetica Neue&quot;,helvetica;font-size:14px;font-style:normal;font-variant=
-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text=
-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-de=
coration:none"><span style=3D"color:rgb(0,0,0);font-family:&quot;helvetica =
Neue&quot;,helvetica;font-size:14px;font-style:normal;font-variant-caps:nor=
mal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0=
px;text-transform:none;white-space:normal;word-spacing:0px;background-color=
:rgb(255,255,255);text-decoration:none;float:none;display:inline!important"=
>There&#39;s nothing in the specs that specifies when the QPACK<span class=
=3D"Apple-converted-space">=C2=A0</span></span><br style=3D"color:rgb(0,0,0=
);font-family:&quot;helvetica Neue&quot;,helvetica;font-size:14px;font-styl=
e:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;=
text-align:start;text-indent:0px;text-transform:none;white-space:normal;wor=
d-spacing:0px;text-decoration:none"><span style=3D"color:rgb(0,0,0);font-fa=
mily:&quot;helvetica Neue&quot;,helvetica;font-size:14px;font-style:normal;=
font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-alig=
n:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing=
:0px;background-color:rgb(255,255,255);text-decoration:none;float:none;disp=
lay:inline!important">encoder/decoder streams are opened, so I was going on=
 the assumption<span class=3D"Apple-converted-space">=C2=A0</span></span><b=
r style=3D"color:rgb(0,0,0);font-family:&quot;helvetica Neue&quot;,helvetic=
a;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:nor=
mal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:n=
one;white-space:normal;word-spacing:0px;text-decoration:none"><span style=
=3D"color:rgb(0,0,0);font-family:&quot;helvetica Neue&quot;,helvetica;font-=
size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;let=
ter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;whi=
te-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-dec=
oration:none;float:none;display:inline!important">that they are only opened=
 when a client wants to use the dynamic table.<span class=3D"Apple-converte=
d-space">=C2=A0</span></span></div></span></blockquote></div><p><br></p><p>=
I=E2=80=99m not really sure where this landed, but there was some discussio=
n here:=C2=A0<a href=3D"https://github.com/quicwg/base-drafts/issues/1747">=
https://github.com/quicwg/base-drafts/issues/1747</a></p><p><br></p><div></=
div></body></html>

--0000000000000d9ac005787cf00c--


From nobody Thu Oct 18 08:18:53 2018
Return-Path: <Lucas.Pardue@bbc.co.uk>
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 EF03612D4EB for <quic@ietfa.amsl.com>; Thu, 18 Oct 2018 08:18:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 uRl36HCkFBZz for <quic@ietfa.amsl.com>; Thu, 18 Oct 2018 08:18:48 -0700 (PDT)
Received: from mailout1.telhc.bbc.co.uk (mailout1.telhc.bbc.co.uk [132.185.161.180]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C65012426A for <quic@ietf.org>; Thu, 18 Oct 2018 08:18:48 -0700 (PDT)
Received: from BGB01XI1003.national.core.bbc.co.uk ([10.184.50.53]) by mailout1.telhc.bbc.co.uk (8.15.2/8.15.2) with ESMTP id w9IFIkf3023822 for <quic@ietf.org>; Thu, 18 Oct 2018 16:18:46 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1003.national.core.bbc.co.uk ([10.184.50.53]) with mapi id 14.03.0408.000; Thu, 18 Oct 2018 16:18:44 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: IETF QUIC WG <quic@ietf.org>
Subject: unsubscribe
Thread-Topic: unsubscribe
Thread-Index: AdRm9dtE78HJi6MYQeCOLxcnCqj2Mw==
Date: Thu, 18 Oct 2018 15:18:44 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BBCB397@bgb01xud1012>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.19.161.211]
x-exclaimer-md-config: 1cd3ac1c-62e5-43f2-8404-6b688271c769
x-tm-as-product-ver: SMEX-12.5.0.1300-8.2.1013-24052.007
x-tm-as-result: No-15.442700-8.000000-10
x-tmase-matchedrid: vk/IrZbtW3/fVqwz+CynaRgO7sCGTR0NXF/PXQ6xePkINo8Qmyzu3Jug 7EeB7h9A2qOAkQrDumN6a7qHolmGufwGVtfL479a4pinC0b7AdXZZ3tkYPr8pJ7/UtsgxGs/a+5 MR1psyWg5pKkTkkVdkQwfhKwa9GwDcbVmJQ7kUKXnlNKhb+fAfjnuQWM5Mjkl77q9ZAKNG0okw1 9B3BcLFoIiDu0n/+6xNNHZMWDTEbf8Xh935PYSDsO/l0Ny5PZ5PQlKJ9DUxnmdvEbju2boo2Nre vvM6dySUtX1sDqa6EjC+o4YGuB7e5FJWAPVTWFNEVcJzjkdE3AMef7y/r+VNBjAKcQNzqp2Yy6J 2dt5kpHuHXE92Wk6HBJo06V2lHTeD0MoRIvclwXNsmTIwLSke90pRIFbsjfbb7mJ6HbhlhFftuJ wrFEhTW+wxxJRnl451uSuyrpf5R6A6k6KAPdvJwufUGZx9fyesfqUj4vUtp/kp5fOzKaGvI4YtS KM5tsvbtFM8A/sqTs=
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
x-tmase-result: 10--15.442700-8.000000
x-tmase-version: SMEX-12.5.0.1300-8.2.1013-24052.007
Content-Type: multipart/alternative; boundary="_000_7CF7F94CB496BF4FAB1676F375F9666A3BBCB397bgb01xud1012_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Sh6vVjwMpYA-ygHWO566m70vmcs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 18 Oct 2018 15:18:51 -0000

--_000_7CF7F94CB496BF4FAB1676F375F9666A3BBCB397bgb01xud1012_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQoNCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCmh0dHA6Ly93d3cuYmJjLmNv
LnVrDQpUaGlzIGUtbWFpbCAoYW5kIGFueSBhdHRhY2htZW50cykgaXMgY29uZmlkZW50aWFsIGFu
ZCBtYXkgY29udGFpbiBwZXJzb25hbCB2aWV3cyB3aGljaCBhcmUgbm90IHRoZSB2aWV3cyBvZiB0
aGUgQkJDIHVubGVzcyBzcGVjaWZpY2FsbHkgc3RhdGVkLg0KSWYgeW91IGhhdmUgcmVjZWl2ZWQg
aXQgaW4gZXJyb3IsIHBsZWFzZSBkZWxldGUgaXQgZnJvbSB5b3VyIHN5c3RlbS4NCkRvIG5vdCB1
c2UsIGNvcHkgb3IgZGlzY2xvc2UgdGhlIGluZm9ybWF0aW9uIGluIGFueSB3YXkgbm9yIGFjdCBp
biByZWxpYW5jZSBvbiBpdCBhbmQgbm90aWZ5IHRoZSBzZW5kZXIgaW1tZWRpYXRlbHkuDQpQbGVh
c2Ugbm90ZSB0aGF0IHRoZSBCQkMgbW9uaXRvcnMgZS1tYWlscyBzZW50IG9yIHJlY2VpdmVkLg0K
RnVydGhlciBjb21tdW5pY2F0aW9uIHdpbGwgc2lnbmlmeSB5b3VyIGNvbnNlbnQgdG8gdGhpcy4N
Cg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo=

--_000_7CF7F94CB496BF4FAB1676F375F9666A3BBCB397bgb01xud1012_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjwhLS0gVGVtcGxhdGUgZ2VuZXJhdGVkIGJ5IEV4Y2xh
aW1lciBNYWlsIERpc2NsYWltZXJzIG9uIDA0OjE4OjQ0IFRodXJzZGF5LCAxOCBPY3RvYmVyIDIw
MTggLS0+DQo8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9InRleHQvaHRt
bDsgY2hhcnNldD11dGYtOCI+DQo8c3R5bGUgdHlwZT0idGV4dC9jc3MiPlAuNTNjNzA0MWItODJm
ZS00M2E3LTk0ODAtYTE2MDk5ZTc1ODkzIHsNCglNQVJHSU46IDBjbSAwY20gMHB0DQp9DQpMSS41
M2M3MDQxYi04MmZlLTQzYTctOTQ4MC1hMTYwOTllNzU4OTMgew0KCU1BUkdJTjogMGNtIDBjbSAw
cHQNCn0NCkRJVi41M2M3MDQxYi04MmZlLTQzYTctOTQ4MC1hMTYwOTllNzU4OTMgew0KCU1BUkdJ
TjogMGNtIDBjbSAwcHQNCn0NClRBQkxFLjUzYzcwNDFiLTgyZmUtNDNhNy05NDgwLWExNjA5OWU3
NTg5M1RhYmxlIHsNCglNQVJHSU46IDBjbSAwY20gMHB0DQp9DQpESVYuU2VjdGlvbjEgew0KCXBh
Z2U6IFNlY3Rpb24xDQp9DQo8L3N0eWxlPg0KPG1ldGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50
PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQgbWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyog
Rm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBN
YXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9u
dC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBT
dHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05v
cm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6
MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCW1zby1mYXJlYXN0
LWxhbmd1YWdlOkVOLVVTO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxl
LXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGlu
ZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9
DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1jb21wb3NlOw0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0K
Lk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVM7fQ0K
QHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4w
cHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRT
ZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVk
ZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0t
PjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0K
PG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+
PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1HQiIgbGluaz0iIzA1NjNDMSIg
dmxpbms9IiM5NTRGNzIiPg0KPHAgY2xhc3M9IjUzYzcwNDFiLTgyZmUtNDNhNy05NDgwLWExNjA5
OWU3NTg5MyI+PC9wPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8cD48L3A+DQo8cCBjbGFzcz0i
NTNjNzA0MWItODJmZS00M2E3LTk0ODAtYTE2MDk5ZTc1ODkzIj4mbmJzcDs8L3A+DQo8cCBjbGFz
cz0iNTNjNzA0MWItODJmZS00M2E3LTk0ODAtYTE2MDk5ZTc1ODkzIj4tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tPGJyPg0KPGZvbnQgc2l6ZT0iMyIgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48
Zm9udCBzaXplPSIzIiBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjxmb250IHNpemU9IjMiIGZhY2U9
IlRpbWVzIE5ldyBSb21hbiI+PGJyPg0KPGZvbnQgc2l6ZT0iMyIgZmFjZT0iVGltZXMgTmV3IFJv
bWFuIj48YSBocmVmPSJodHRwOi8vd3d3LmJiYy5jby51ayIgdGFyZ2V0PSJfYmxhbmsiPmh0dHA6
Ly93d3cuPHNwYW4gY2xhc3M9ImlsIj5iYmM8L3NwYW4+LjxzcGFuIGNsYXNzPSJpbCI+Y288L3Nw
YW4+LjxzcGFuIGNsYXNzPSJpbCI+dWs8L3NwYW4+PC9hPjxicj4NClRoaXMgZS1tYWlsIChhbmQg
YW55IGF0dGFjaG1lbnRzKSBpcyBjb25maWRlbnRpYWwgYW5kIG1heSBjb250YWluIHBlcnNvbmFs
IHZpZXdzIHdoaWNoIGFyZSBub3QgdGhlIHZpZXdzIG9mIHRoZQ0KPHNwYW4gY2xhc3M9ImlsIj5C
QkM8L3NwYW4+IHVubGVzcyBzcGVjaWZpY2FsbHkgc3RhdGVkLjxicj4NCklmIHlvdSBoYXZlIHJl
Y2VpdmVkIGl0IGluIGVycm9yLCBwbGVhc2UgZGVsZXRlIGl0IGZyb20geW91ciBzeXN0ZW0uPGJy
Pg0KRG8gbm90IHVzZSwgY29weSBvciBkaXNjbG9zZSB0aGUgaW5mb3JtYXRpb24gaW4gYW55IHdh
eSBub3IgYWN0IGluIHJlbGlhbmNlIG9uIGl0IGFuZCBub3RpZnkgdGhlIHNlbmRlciBpbW1lZGlh
dGVseS48YnI+DQpQbGVhc2Ugbm90ZSB0aGF0IHRoZSA8c3BhbiBjbGFzcz0iaWwiPkJCQzwvc3Bh
bj4gbW9uaXRvcnMgZS1tYWlscyBzZW50IG9yIHJlY2VpdmVkLjxicj4NCkZ1cnRoZXIgY29tbXVu
aWNhdGlvbiB3aWxsIHNpZ25pZnkgeW91ciBjb25zZW50IHRvIHRoaXMuPC9mb250PjwvZm9udD48
L2ZvbnQ+PC9mb250PjwvcD4NCjxwIGNsYXNzPSI1M2M3MDQxYi04MmZlLTQzYTctOTQ4MC1hMTYw
OTllNzU4OTMiPi0tLS0tLS0tLS0tLS0tLS0tLS0tLTwvcD4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_7CF7F94CB496BF4FAB1676F375F9666A3BBCB397bgb01xud1012_--


From nobody Fri Oct 19 02:45:09 2018
Return-Path: <session-request@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D318B130E8E; Fri, 19 Oct 2018 02:45:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: lars@eggert.org, quic@ietf.org, spencerdawkins.ietf@gmail.com, quic-chairs@ietf.org
Subject: quic - New Interim Meeting Request
X-Test-IDTracker: no
X-IETF-IDTracker: 6.87.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153994230578.31869.2269372753947570889.idtracker@ietfa.amsl.com>
Date: Fri, 19 Oct 2018 02:45:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2_VJxXjfxbdHrtbhUchjY2xUCaY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Oct 2018 09:45:06 -0000

A new interim meeting request has just been submitted by Lars Eggert.

This request requires approval by the Area Director of the Transport Area

The meeting can be approved here: 
https://datatracker.ietf.org/meeting/interim/request/interim-2019-quic-01



---------------------------------------------------------
Working Group Name: QUIC
Area Name: Transport Area
Session Requester: Lars Eggert

City: Tokyo
Country: JP


Session 1:

Date: 2019-01-30
Start Time: 09:00 Asia/Tokyo
Duration: 08:00
Remote Participation Information: yes, after registration, see https://github.com/quicwg/wg-materials/blob/master/interim-19-01/arrangements.md
Agenda Note: https://github.com/quicwg/wg-materials/blob/master/interim-19-01/arrangements.md
Session 2:

Date: 2019-01-31
Start Time: 09:00 Asia/Tokyo
Duration: 08:00
Remote Participation Information: yes, after registration, see https://github.com/quicwg/wg-materials/blob/master/interim-19-01/arrangements.md
Agenda Note: https://github.com/quicwg/wg-materials/blob/master/interim-19-01/arrangements.md

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


From nobody Fri Oct 19 11:58:23 2018
Return-Path: <agenda@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C62C3130FFF; Fri, 19 Oct 2018 11:56:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <lars@eggert.org>, <quic-chairs@ietf.org>
Cc: quic@ietf.org, spencerdawkins.ietf@gmail.com
Subject: quic - Requested sessions have been scheduled for IETF 103
X-Test-IDTracker: no
X-IETF-IDTracker: 6.87.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153997538780.6592.17671395266105585750.idtracker@ietfa.amsl.com>
Date: Fri, 19 Oct 2018 11:56:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/z42H4DfvEwt21qs51xwsEr-bjB4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Oct 2018 18:56:35 -0000

Dear Lars Eggert,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 


    quic Session 1 (2:00 requested)
    Tuesday, 6 November 2018, Afternoon Session I 1350-1550
    Room Name: Chitlada 1 size: 300
    ---------------------------------------------
    quic Session 2 (2:00 requested)
    Wednesday, 7 November 2018, Morning Session I 0900-1100
    Room Name: Chitlada 1 size: 300
    ---------------------------------------------


iCalendar: https://datatracker.ietf.org/meeting/103/sessions/quic.ics

Request Information:


---------------------------------------------------------
Working Group Name: QUIC
Area Name: Transport Area
Session Requester: Lars Eggert

Number of Sessions: 2
Length of Session(s):  2 Hours, 2 Hours
Number of Attendees: 200
Conflicts to Avoid: 
 First Priority: tsvarea tsvwg tcpm iccrg httpbis tls dispatch
 Second Priority: mptcp saag rtcweb
 Third Priority: irtfopen maprg


People who must be present:
  Sean Turner
  Mark Nottingham
  Patrick R. McManus
  Jana Iyengar
  Martin Thomson
  Spencer Dawkins
  Brian Trammell
  Mirja Kuehlewind
  Lars Eggert
  Mike Bishop
  Ian Swett
  Alan Frindell

Resources Requested:
  Experimental Room Setup (U-Shape and classroom, subject to availability)

Special Requests:
  Two consecutive days early in the week, if possible.
---------------------------------------------------------


From nobody Sat Oct 20 17:45:31 2018
Return-Path: <do_not_reply@mnot.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 C835D130E34 for <quic@ietfa.amsl.com>; Sat, 20 Oct 2018 17:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=GRga2twd; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Gki01xC/
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 Ab8on7pjbB8r for <quic@ietfa.amsl.com>; Sat, 20 Oct 2018 17:45:26 -0700 (PDT)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3231F130E17 for <quic@ietf.org>; Sat, 20 Oct 2018 17:45:26 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 2D9734A0 for <quic@ietf.org>; Sat, 20 Oct 2018 20:45:25 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sat, 20 Oct 2018 20:45:25 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject:message-id:date; s= fm1; bh=SlKxmrZvswnGxfEcv77zSwGbq/cH3HkHFRNXUOQaoz0=; b=GRga2twd Bbcjqsh2z3OKsoceFegsnjxoZtAOCNrTs31X0n2XlhhSm4CJCTkC5jYgTapzEBfh v4czscZN2RYnitSJ/tTiAzhw24n1sxM4U9dBHVnpuRlspsUQBgVqDZ6zLJ5nS1/f DujVU6Y2bgAC2QV8UHBuHj3ZmGRWUFbhM8AIxlMEwEBewbg4+9RMU+sHJ60ZXBZy Pdi9EgEo8bIHoPxHz/AfUMgp2ZLBEewi/oWVS9D2Bx15d6q2FbHS0DhmFMXnQkr6 AtRkQ4FreKwThT8XYlXXDnxomjxTanHqHAh8DsfbGKneZgcmXfYqn3atYVLEPjNX qWmh0G/DUG8Tvg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=SlKxmrZvswnGxfEcv77zSwGbq/cH3 HkHFRNXUOQaoz0=; b=Gki01xC/xv4I6nhNuhoBfV9X1H7dLEiGCVepnqH71cWy3 PujMKd7fBURriBWGGrIbE0PasFk4Idvfxi1URbRohqq3r/X39mYblpQvMFisNnpt z3jIDqb2W6FnuAqw7GFiGjgCO+myV5ZWMspwWWSAWQ0j9YJSuj6enDXvyQGaF3mK EbxVV4JBfCnhILRjQIgdyBNshhWoAnOEh2vVrxfWkyTUDAd1oReoV5i5vpPpZKr4 1hleBI1aQKlAOCNbQJf9gih2YliZwKMXzftq2xqcwQJzQVGG/9Yp1pFGGatFCGgU KMOx+zzBuWHmPGUCx6Lbih6/ECTrjc6UZ3sfBSchg==
X-ME-Sender: <xms:I8zLW8Gw1n-cZ15dbvxTT3M3eQ4GDWjyrV6ScCygLpCDgU17BKxFJg>
X-ME-Proxy: <xmx:JMzLW-NJPfzuv1xQMCC72gq5TXlddLLHecrDTQBVHIBb8kIEQs17Yw> <xmx:JMzLW18tNcUPY3ZZTTp57Jn3qK3bRt72qGxemnu-kpItuKQcUwz0sQ> <xmx:JMzLW---2KpI_l37vcDIQD8xePEUVSDShSkckGm3TodkoQz5HewuGA> <xmx:JMzLW1pVdOQ7JHigcnGg_YTF4Ax6Hvn6cDsPlyXZ4x-I8qF3pB_Kwg> <xmx:JMzLW5JP9kbxsEuNubuYE5RkxjvRtA2xBLV7fTyZpV3dssNSnIuPrQ> <xmx:JMzLW4ymVcCjiIqhtr3uHWnosvjtl18SHcn9FP_LRA5sCQcGf1cHhQ>
Received: from cloud.mnot.net (cloud.mnot.net [119.9.43.241]) by mail.messagingengine.com (Postfix) with ESMTPA id 5C467102E9 for <quic@ietf.org>; Sat, 20 Oct 2018 20:45:23 -0400 (EDT)
Received: from cloud.mnot.net (localhost [127.0.0.1]) by cloud.mnot.net (Postfix) with ESMTP id A7202D01C1 for <quic@ietf.org>; Sun, 21 Oct 2018 00:45:20 +0000 (UTC)
Content-Type: multipart/alternative; boundary="===============7003219247566504559=="
MIME-Version: 1.0
From: =?utf-8?q?Github_Notifications?= <do_not_reply@mnot.net>
To: quic@ietf.org
Subject: Weekly github digest (QUIC Working Group Specifications)
Message-Id: <20181021004520.A7202D01C1@cloud.mnot.net>
Date: Sun, 21 Oct 2018 00:45:20 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/o0etwcaWoh7_Hdn9LNhDXxTPEBg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 21 Oct 2018 00:45:30 -0000

--===============7003219247566504559==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Events without label "editorial"

Issues
------
* quicwg/base-drafts (+11/-6/=F0=9F=92=AC60)
  11 issues created:
  - Make Client TP Optional (by nibanks)
    https://github.com/quicwg/base-drafts/issues/1892 =

  - DATA frame encoding is inefficient for long dynamically generated bodie=
s (by RyanAtGoogle)
    https://github.com/quicwg/base-drafts/issues/1885 =

  - Need to clarify QUIC stream usage in HTTP/2 mapping (by gloinul)
    https://github.com/quicwg/base-drafts/issues/1882 =

  - Should we collapse APPLICATION_CLOSE and CONNECTION_CLOSE (by martintho=
mson)
    https://github.com/quicwg/base-drafts/issues/1881 =

  - Permitted frame types (by rpaulo)
    https://github.com/quicwg/base-drafts/issues/1880 =

  - RST_STREAM can (still) cause flow control problems (by martinduke)
    https://github.com/quicwg/base-drafts/issues/1878 =

  - Channel binding (by DemiMarie)
    https://github.com/quicwg/base-drafts/issues/1877 =

  - Heartbeats (by DemiMarie)
    https://github.com/quicwg/base-drafts/issues/1876 =

  - Post-quantum cryptography integration (by DemiMarie)
    https://github.com/quicwg/base-drafts/issues/1875 =

  - Formal analysis of the protocol (by DemiMarie)
    https://github.com/quicwg/base-drafts/issues/1874 =

  - FTP integration (by DemiMarie)
    https://github.com/quicwg/base-drafts/issues/1873 =


  14 issues received 60 new comments:
  - #1885 DATA frame encoding is inefficient for long dynamically generated=
 bodies (31 by kazuho, mikkelfj, MikeBishop, martinthomson, ianswett, RyanA=
tGoogle, dtikhonov, LPardue)
    https://github.com/quicwg/base-drafts/issues/1885 [-http] [design] =

  - #1878 RST_STREAM can (still) cause flow control problems (10 by mikkelf=
j, ianswett, martinthomson, MikeBishop, RyanAtGoogle, martinduke)
    https://github.com/quicwg/base-drafts/issues/1878 =

  - #1871 Multihoming support (3 by mikkelfj, DemiMarie, MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1871 =

  - #1874 Formal analysis of the protocol (3 by ianswett, MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1874 [-tls] [parked] =

  - #1892 Make Client TP Optional (2 by kazuho, ianswett)
    https://github.com/quicwg/base-drafts/issues/1892 =

  - #1880 Permitted frame types (2 by kazuho, MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1880 =

  - #1853 Does GOAWAY really need a stream number? (2 by ddragana, MikeBish=
op)
    https://github.com/quicwg/base-drafts/issues/1853 [-http] [design] =

  - #1865 In-order priority changes in HQ does not hold (1 by dtikhonov)
    https://github.com/quicwg/base-drafts/issues/1865 =

  - #1875 Post-quantum cryptography integration (1 by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1875 =

  - #1872 Kerberos integration (1 by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1872 =

  - #1873 FTP integration (1 by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1873 =

  - #1877 Channel binding (1 by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1877 =

  - #1876 Heartbeats (1 by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1876 =

  - #1882 Need to clarify QUIC stream usage in HTTP/2 mapping (1 by MikeBis=
hop)
    https://github.com/quicwg/base-drafts/issues/1882 =


  6 issues closed:
  - Permitted frame types https://github.com/quicwg/base-drafts/issues/1880 =

  - Channel binding https://github.com/quicwg/base-drafts/issues/1877 =

  - Heartbeats https://github.com/quicwg/base-drafts/issues/1876 =

  - Post-quantum cryptography integration https://github.com/quicwg/base-dr=
afts/issues/1875 =

  - Multihoming support https://github.com/quicwg/base-drafts/issues/1871 =

  - Kerberos integration https://github.com/quicwg/base-drafts/issues/1872 =




Pull requests
-------------
* quicwg/base-drafts (+5/-2/=F0=9F=92=AC10)
  5 pull requests submitted:
  - Minor edits to amplification attack text (by martinduke)
    https://github.com/quicwg/base-drafts/pull/1895 =

  - Explicitly suggest FIN or RST_STREAM (by martinduke)
    https://github.com/quicwg/base-drafts/pull/1893 =

  - Crisp definition of BLOCKING and friends (by martinthomson)
    https://github.com/quicwg/base-drafts/pull/1889 [-transport] =

  - Remove some excessive nesting from reorg (by martinthomson)
    https://github.com/quicwg/base-drafts/pull/1887 =

  - Reorganizes drafts (by janaiyengar)
    https://github.com/quicwg/base-drafts/pull/1884 =


  7 pull requests received 10 new comments:
  - #1893 Explicitly suggest FIN or RST_STREAM (3 by RyanAtGoogle, kazuho, =
marten-seemann)
    https://github.com/quicwg/base-drafts/pull/1893 =

  - #1819 Let Endpoints Ignore invalid Initial Packets (2 by martinthomson,=
 martinduke)
    https://github.com/quicwg/base-drafts/pull/1819 =

  - #1665 Full (mostly) editorial pass (1 by martinthomson)
    https://github.com/quicwg/base-drafts/pull/1665 =

  - #1862 Amplification limit in recovery (1 by mikkelfj)
    https://github.com/quicwg/base-drafts/pull/1862 [-recovery] [design] =

  - #1869 Improve description of max_ack_delay transport parameter (1 by ma=
rtinthomson)
    https://github.com/quicwg/base-drafts/pull/1869 =

  - #1843 Move server send limitations (1 by martinthomson)
    https://github.com/quicwg/base-drafts/pull/1843 =

  - #1844 Clarify coalesced packet processing (1 by martinthomson)
    https://github.com/quicwg/base-drafts/pull/1844 =


  2 pull requests merged:
  - Reorganizes drafts
    https://github.com/quicwg/base-drafts/pull/1884 =

  - WIP: High-level restructure of transport draft
    https://github.com/quicwg/base-drafts/pull/1857 [unicorns!!!] =



Repositories tracked by this digest:
-----------------------------------
* https://github.com/quicwg/base-drafts

--===============7003219247566504559==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (QUIC Working Group Specifications)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
</style>
</head>

<body>
<h1>Sunday October 21, 2018</h1>

<p>Events without label "editorial"</p>

<h2>Issues</h2>

<h3>quicwg/base-drafts (+11/-6/=F0=9F=92=AC60)</h3>
  <p class=3D"new">11 issues created:</p>
  <ul>
  <li>#1892 <a href=3D"https://github.com/quicwg/base-drafts/issues/1892">M=
ake Client TP Optional</a> (by nibanks) </li>
  =

  <li>#1885 <a href=3D"https://github.com/quicwg/base-drafts/issues/1885">D=
ATA frame encoding is inefficient for long dynamically generated bodies</a>=
 (by RyanAtGoogle) </li>
  =

  <li>#1882 <a href=3D"https://github.com/quicwg/base-drafts/issues/1882">N=
eed to clarify QUIC stream usage in HTTP/2 mapping</a> (by gloinul) </li>
  =

  <li>#1881 <a href=3D"https://github.com/quicwg/base-drafts/issues/1881">S=
hould we collapse APPLICATION_CLOSE and CONNECTION_CLOSE</a> (by martinthom=
son) </li>
  =

  <li>#1880 <a href=3D"https://github.com/quicwg/base-drafts/issues/1880">P=
ermitted frame types</a> (by rpaulo) </li>
  =

  <li>#1878 <a href=3D"https://github.com/quicwg/base-drafts/issues/1878">R=
ST_STREAM can (still) cause flow control problems</a> (by martinduke) </li>
  =

  <li>#1877 <a href=3D"https://github.com/quicwg/base-drafts/issues/1877">C=
hannel binding</a> (by DemiMarie) </li>
  =

  <li>#1876 <a href=3D"https://github.com/quicwg/base-drafts/issues/1876">H=
eartbeats</a> (by DemiMarie) </li>
  =

  <li>#1875 <a href=3D"https://github.com/quicwg/base-drafts/issues/1875">P=
ost-quantum cryptography integration</a> (by DemiMarie) </li>
  =

  <li>#1874 <a href=3D"https://github.com/quicwg/base-drafts/issues/1874">F=
ormal analysis of the protocol</a> (by DemiMarie) </li>
  =

  <li>#1873 <a href=3D"https://github.com/quicwg/base-drafts/issues/1873">F=
TP integration</a> (by DemiMarie) </li>
  </ul>

  <p>14 issues received 60 new comments:</p>
  <ul>
  <li>#1885 <a href=3D"https://github.com/quicwg/base-drafts/issues/1885">D=
ATA frame encoding is inefficient for long dynamically generated bodies</a>=
 (31 by kazuho, mikkelfj, MikeBishop, martinthomson, ianswett, RyanAtGoogle=
, dtikhonov, LPardue) <span class=3D"label" style=3D"background-color: #fbc=
a04; color: #000000">-http</span> <span class=3D"label" style=3D"background=
-color: #1d76db; color: #ffffff">design</span> </li>
  =

  <li>#1878 <a href=3D"https://github.com/quicwg/base-drafts/issues/1878">R=
ST_STREAM can (still) cause flow control problems</a> (10 by mikkelfj, ians=
wett, martinthomson, MikeBishop, RyanAtGoogle, martinduke) </li>
  =

  <li>#1871 <a href=3D"https://github.com/quicwg/base-drafts/issues/1871">M=
ultihoming support</a> (3 by mikkelfj, DemiMarie, MikeBishop) </li>
  =

  <li>#1874 <a href=3D"https://github.com/quicwg/base-drafts/issues/1874">F=
ormal analysis of the protocol</a> (3 by ianswett, MikeBishop) <span class=
=3D"label" style=3D"background-color: #fbca04; color: #000000">-tls</span> =
<span class=3D"label" style=3D"background-color: #f9d0c4; color: #000000">p=
arked</span> </li>
  =

  <li>#1892 <a href=3D"https://github.com/quicwg/base-drafts/issues/1892">M=
ake Client TP Optional</a> (2 by kazuho, ianswett) </li>
  =

  <li>#1880 <a href=3D"https://github.com/quicwg/base-drafts/issues/1880">P=
ermitted frame types</a> (2 by kazuho, MikeBishop) </li>
  =

  <li>#1853 <a href=3D"https://github.com/quicwg/base-drafts/issues/1853">D=
oes GOAWAY really need a stream number?</a> (2 by ddragana, MikeBishop) <sp=
an class=3D"label" style=3D"background-color: #fbca04; color: #000000">-htt=
p</span> <span class=3D"label" style=3D"background-color: #1d76db; color: #=
ffffff">design</span> </li>
  =

  <li>#1865 <a href=3D"https://github.com/quicwg/base-drafts/issues/1865">I=
n-order priority changes in HQ does not hold</a> (1 by dtikhonov) </li>
  =

  <li>#1875 <a href=3D"https://github.com/quicwg/base-drafts/issues/1875">P=
ost-quantum cryptography integration</a> (1 by MikeBishop) </li>
  =

  <li>#1872 <a href=3D"https://github.com/quicwg/base-drafts/issues/1872">K=
erberos integration</a> (1 by MikeBishop) </li>
  =

  <li>#1873 <a href=3D"https://github.com/quicwg/base-drafts/issues/1873">F=
TP integration</a> (1 by MikeBishop) </li>
  =

  <li>#1877 <a href=3D"https://github.com/quicwg/base-drafts/issues/1877">C=
hannel binding</a> (1 by MikeBishop) </li>
  =

  <li>#1876 <a href=3D"https://github.com/quicwg/base-drafts/issues/1876">H=
eartbeats</a> (1 by MikeBishop) </li>
  =

  <li>#1882 <a href=3D"https://github.com/quicwg/base-drafts/issues/1882">N=
eed to clarify QUIC stream usage in HTTP/2 mapping</a> (1 by MikeBishop) </=
li>
  </ul>

  <p>6 issues closed:</p>
  <ul>
  <li>#1880 <a href=3D"https://github.com/quicwg/base-drafts/issues/1880">P=
ermitted frame types</a> </li>
  =

  <li>#1877 <a href=3D"https://github.com/quicwg/base-drafts/issues/1877">C=
hannel binding</a> </li>
  =

  <li>#1876 <a href=3D"https://github.com/quicwg/base-drafts/issues/1876">H=
eartbeats</a> </li>
  =

  <li>#1875 <a href=3D"https://github.com/quicwg/base-drafts/issues/1875">P=
ost-quantum cryptography integration</a> </li>
  =

  <li>#1871 <a href=3D"https://github.com/quicwg/base-drafts/issues/1871">M=
ultihoming support</a> </li>
  =

  <li>#1872 <a href=3D"https://github.com/quicwg/base-drafts/issues/1872">K=
erberos integration</a> </li>
  </ul>



<h2>Pull requests</h2>
<h3>quicwg/base-drafts (+5/-2/=F0=9F=92=AC10)</h3>
  <p class=3D"new">5 pull requests submitted:</p>
  <ul>
  <li>#1895 <a href=3D"https://github.com/quicwg/base-drafts/pull/1895">Min=
or edits to amplification attack text</a> (by martinduke) </li>
  =

  <li>#1893 <a href=3D"https://github.com/quicwg/base-drafts/pull/1893">Exp=
licitly suggest FIN or RST_STREAM</a> (by martinduke) </li>
  =

  <li>#1889 <a href=3D"https://github.com/quicwg/base-drafts/pull/1889">Cri=
sp definition of BLOCKING and friends</a> (by martinthomson) <span class=3D=
"label" style=3D"background-color: #fbca04; color: #">-transport</span> </l=
i>
  =

  <li>#1887 <a href=3D"https://github.com/quicwg/base-drafts/pull/1887">Rem=
ove some excessive nesting from reorg</a> (by martinthomson) </li>
  =

  <li>#1884 <a href=3D"https://github.com/quicwg/base-drafts/pull/1884">Reo=
rganizes drafts</a> (by janaiyengar) </li>
  </ul>

  <p>7 pull requests received 10 new comments:</p>
  <ul>
  <li>#1893 <a href=3D"https://github.com/quicwg/base-drafts/pull/1893">Exp=
licitly suggest FIN or RST_STREAM</a> (3 by RyanAtGoogle, kazuho, marten-se=
emann) </li>
  =

  <li>#1819 <a href=3D"https://github.com/quicwg/base-drafts/pull/1819">Let=
 Endpoints Ignore invalid Initial Packets</a> (2 by martinthomson, martindu=
ke) </li>
  =

  <li>#1665 <a href=3D"https://github.com/quicwg/base-drafts/pull/1665">Ful=
l (mostly) editorial pass</a> (1 by martinthomson) </li>
  =

  <li>#1862 <a href=3D"https://github.com/quicwg/base-drafts/pull/1862">Amp=
lification limit in recovery</a> (1 by mikkelfj) <span class=3D"label" styl=
e=3D"background-color: #fbca04; color: #000000">-recovery</span> <span clas=
s=3D"label" style=3D"background-color: #1d76db; color: #ffffff">design</spa=
n> </li>
  =

  <li>#1869 <a href=3D"https://github.com/quicwg/base-drafts/pull/1869">Imp=
rove description of max_ack_delay transport parameter</a> (1 by martinthoms=
on) </li>
  =

  <li>#1843 <a href=3D"https://github.com/quicwg/base-drafts/pull/1843">Mov=
e server send limitations</a> (1 by martinthomson) </li>
  =

  <li>#1844 <a href=3D"https://github.com/quicwg/base-drafts/pull/1844">Cla=
rify coalesced packet processing</a> (1 by martinthomson) </li>
  </ul>

  <p>2 pull requests merged:</p>
  <ul>
  <li>#1884 <a href=3D"https://github.com/quicwg/base-drafts/pull/1884">Reo=
rganizes drafts</a> </li>
  =

  <li>#1857 <a href=3D"https://github.com/quicwg/base-drafts/pull/1857">WIP=
: High-level restructure of transport draft</a> <span class=3D"label" style=
=3D"background-color: #fc1196; color: #">unicorns!!!</span> </li>
  </ul>


<h2>Repositories tracked by this digest:</h2>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/quicwg/base-drafts">https://github.com/=
quicwg/base-drafts</a></li>
  </ul>
</body>
</html>

--===============7003219247566504559==--


From nobody Mon Oct 22 07:49:36 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0578D1276D0; Mon, 22 Oct 2018 07:49:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-manageability-03.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.87.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <154021975791.6590.4931731246777478690@ietfa.amsl.com>
Date: Mon, 22 Oct 2018 07:49:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/_aMdgWiMBqxY0p4K0Fa_1segkG4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 22 Oct 2018 14:49:18 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : Manageability of the QUIC Transport Protocol
        Authors         : Mirja Kuehlewind
                          Brian Trammell
	Filename        : draft-ietf-quic-manageability-03.txt
	Pages           : 19
	Date            : 2018-10-22

Abstract:
   This document discusses manageability of the QUIC transport protocol,
   focusing on caveats impacting network operations involving QUIC
   traffic.  Its intended audience is network operators, as well as
   content providers that rely on the use of QUIC-aware middleboxes,
   e.g. for load balancing.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-manageability/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-manageability-03
https://datatracker.ietf.org/doc/html/draft-ietf-quic-manageability-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-manageability-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Oct 22 07:49:42 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 04B79130EE7; Mon, 22 Oct 2018 07:49:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-applicability-03.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.87.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <154021976197.5529.6435672303176765169@ietfa.amsl.com>
Date: Mon, 22 Oct 2018 07:49:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/sAoR6ebfOI3Z8cFThCfgbFw-Klo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 22 Oct 2018 14:49:24 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : Applicability of the QUIC Transport Protocol
        Authors         : Mirja Kuehlewind
                          Brian Trammell
	Filename        : draft-ietf-quic-applicability-03.txt
	Pages           : 13
	Date            : 2018-10-22

Abstract:
   This document discusses the applicability of the QUIC transport
   protocol, focusing on caveats impacting application protocol
   development and deployment over QUIC.  Its intended audience is
   designers of application protocol mappings to QUIC, and implementors
   of these application protocols.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-applicability/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-applicability-03
https://datatracker.ietf.org/doc/html/draft-ietf-quic-applicability-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-applicability-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Oct 22 07:55:27 2018
Return-Path: <ietf@trammell.ch>
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 4320512870E for <quic@ietfa.amsl.com>; Mon, 22 Oct 2018 07:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.699
X-Spam-Level: 
X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 0YHem-148Q0h for <quic@ietfa.amsl.com>; Mon, 22 Oct 2018 07:55:23 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [IPv6:2001:8e0:40:325::36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D29A912D4EF for <quic@ietf.org>; Mon, 22 Oct 2018 07:55:22 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 157DE34120E for <quic@ietf.org>; Mon, 22 Oct 2018 16:55:21 +0200 (CEST)
X-Iway-Path: 0
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/20439.28100); Mon, 22 Oct 2018 16:55:21 +0200 (CEST)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS for <quic@ietf.org>; Mon, 22 Oct 2018 16:55:20 +0200 (CEST)
Received: from [195.176.111.22] (account ietf@trammell.ch HELO public-docking-cx-2490.ethz.ch) by switchplus-mail.ch (CommuniGate Pro SMTP 6.2.8) with ESMTPSA id 71190143 for quic@ietf.org; Mon, 22 Oct 2018 16:55:20 +0200
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_CC0E80A4-5D5C-44E5-B537-259C9FDE5E32"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Fwd: I-D Action: draft-ietf-quic-applicability-03.txt
Message-Id: <4757BE87-478C-4D67-A05C-AF6367695E7A@trammell.ch>
References: <154021976197.5529.6435672303176765169@ietfa.amsl.com>
To: IETF QUIC WG <quic@ietf.org>
Date: Mon, 22 Oct 2018 16:55:20 +0200
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/TRXPL-GcHhM2h5PTVKZupUMmBVE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 22 Oct 2018 14:55:25 -0000

--Apple-Mail=_CC0E80A4-5D5C-44E5-B537-259C9FDE5E32
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_1030ED6E-78BB-4F79-9381-5AC33A336F6B"


--Apple-Mail=_1030ED6E-78BB-4F79-9381-5AC33A336F6B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Greetings, all,

We've posted -03 of the applicability and manageability drafts, which =
cover various incremental improvements since Montreal. Issues still open =
can be seen at https://github.com/quicwg/ops-drafts/issues =
<https://github.com/quicwg/ops-drafts/issues> (when github's consistency =
becomes less eventual :) )

Cheers,

Brian and Mirja

> Begin forwarded message:
>=20
> From: internet-drafts@ietf.org
> Subject: I-D Action: draft-ietf-quic-applicability-03.txt
> Date: 22 October 2018 at 16:49:22 CEST
> To: <i-d-announce@ietf.org>
> Cc: quic@ietf.org
> Reply-To: quic@ietf.org
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the QUIC WG of the IETF.
>=20
>        Title           : Applicability of the QUIC Transport Protocol
>        Authors         : Mirja Kuehlewind
>                          Brian Trammell
> 	Filename        : draft-ietf-quic-applicability-03.txt
> 	Pages           : 13
> 	Date            : 2018-10-22
>=20
> Abstract:
>   This document discusses the applicability of the QUIC transport
>   protocol, focusing on caveats impacting application protocol
>   development and deployment over QUIC.  Its intended audience is
>   designers of application protocol mappings to QUIC, and implementors
>   of these application protocols.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-quic-applicability/
>=20
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-quic-applicability-03
> https://datatracker.ietf.org/doc/html/draft-ietf-quic-applicability-03
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-quic-applicability-03
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20


--Apple-Mail=_1030ED6E-78BB-4F79-9381-5AC33A336F6B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Greetings, all,&nbsp;<div class=3D""><br class=3D""></div><div =
class=3D"">We've posted -03 of the applicability and manageability =
drafts, which cover various incremental improvements since Montreal. =
Issues still open can be seen at&nbsp;<a =
href=3D"https://github.com/quicwg/ops-drafts/issues" =
class=3D"">https://github.com/quicwg/ops-drafts/issues</a>&nbsp;(when =
github's consistency becomes less eventual :) )</div><div class=3D""><br =
class=3D""></div><div class=3D"">Cheers,</div><div class=3D""><br =
class=3D""></div><div class=3D"">Brian and Mirja<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">Begin =
forwarded message:</div><br class=3D"Apple-interchange-newline"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">From: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><a =
href=3D"mailto:internet-drafts@ietf.org" =
class=3D"">internet-drafts@ietf.org</a><br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Subject: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><b class=3D"">I-D Action: =
draft-ietf-quic-applicability-03.txt</b><br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Date: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">22 October 2018 at 16:49:22 =
CEST<br class=3D""></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">To: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">&lt;<a =
href=3D"mailto:i-d-announce@ietf.org" =
class=3D"">i-d-announce@ietf.org</a>&gt;<br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Cc: </b></span><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif;" class=3D""><a href=3D"mailto:quic@ietf.org" =
class=3D"">quic@ietf.org</a><br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Reply-To: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><a href=3D"mailto:quic@ietf.org" =
class=3D"">quic@ietf.org</a><br class=3D""></span></div><br =
class=3D""><div class=3D""><div class=3D""><br class=3D"">A New =
Internet-Draft is available from the on-line Internet-Drafts =
directories.<br class=3D"">This draft is a work item of the QUIC WG of =
the IETF.<br class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Title =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
Applicability of the QUIC Transport Protocol<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Authors =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Mirja Kuehlewind<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;Brian Trammell<br class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Filename =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
draft-ietf-quic-applicability-03.txt<br class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Pages =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 13<br =
class=3D""><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Date =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
2018-10-22<br class=3D""><br class=3D"">Abstract:<br class=3D""> =
&nbsp;&nbsp;This document discusses the applicability of the QUIC =
transport<br class=3D""> &nbsp;&nbsp;protocol, focusing on caveats =
impacting application protocol<br class=3D""> &nbsp;&nbsp;development =
and deployment over QUIC. &nbsp;Its intended audience is<br class=3D""> =
&nbsp;&nbsp;designers of application protocol mappings to QUIC, and =
implementors<br class=3D""> &nbsp;&nbsp;of these application =
protocols.<br class=3D""><br class=3D""><br class=3D"">The IETF =
datatracker status page for this draft is:<br class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-quic-applicability/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-quic-applicability/=
</a><br class=3D""><br class=3D"">There are also htmlized versions =
available at:<br =
class=3D"">https://tools.ietf.org/html/draft-ietf-quic-applicability-03<br=
 =
class=3D"">https://datatracker.ietf.org/doc/html/draft-ietf-quic-applicabi=
lity-03<br class=3D""><br class=3D"">A diff from the previous version is =
available at:<br =
class=3D"">https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-quic-applicabili=
ty-03<br class=3D""><br class=3D""><br class=3D"">Please note that it =
may take a couple of minutes from the time of submission<br =
class=3D"">until the htmlized version and diff are available at =
tools.ietf.org.<br class=3D""><br class=3D"">Internet-Drafts are also =
available by anonymous FTP at:<br =
class=3D"">ftp://ftp.ietf.org/internet-drafts/<br class=3D""><br =
class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_1030ED6E-78BB-4F79-9381-5AC33A336F6B--

--Apple-Mail=_CC0E80A4-5D5C-44E5-B537-259C9FDE5E32
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAlvN5NgACgkQihK3vwvq
RqPdiBAAkdmUOCGGEYFj46YtveWGd70XGl4R7Ni9LGyUECap6OmyU8dgC1gCO9Q2
1TgM+idbbdQM0g7/WTqm4a815PPQWJVonMaZC1Z+GBmIbkPJLGjkyYgkzCrGcfwP
VLnzKZZM5NBSzynroKR4Jmf7CqP6npRJkEv2TWrwfkErKF62okeH8PHmqydHJB3z
B0dxPqoDeqRGN6BYBbdZVgCrXw8lKzbWxqeFmK7AhiLgMGGKrQvOy0mH04kf9k8g
UUW4paPEYe+HEVz0nvWYBtlN3d8B/mJtkmjgrKIjS7A5KHzfQPUJJq96DJwTpI+i
oWzeeaZQRCdsZH/fjKjqAAVNiLM+WpO90rMCqQir9yMB9zyudEWYJNcyB4/onlKe
PRlyjEWbTsQhdO1dahWN+tQE8FCj/1w66yGRgRLlhG6ua99YWzxfaVL62UHwms+m
qgx21K3QfSZvDftBocPcDdqntXQjarAygPH19MTftCunGc/KKdYJPEDsi2VyfoSZ
vlZmLpbUaGvcEvjgaAb3cvUnkPqrQT3Ph9a4+xemtFpAbeqvb14nhEq26lOeIxmV
JcHyXRmHIklcND9yIW1VFWxnxHO2pe2Uh+Rj2MtNML1PhvF/a+RMRjo5KlFTxkcd
NVLCr2HoQGajclf8BF5gI+jqh3oJzujvx7WvNlFsH7nCzrDuSik=
=RUup
-----END PGP SIGNATURE-----

--Apple-Mail=_CC0E80A4-5D5C-44E5-B537-259C9FDE5E32--


From nobody Mon Oct 22 08:12:41 2018
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 50D2F124BE5; Mon, 22 Oct 2018 08:12:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IESG Secretary <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: quic@ietf.org
Subject: QUIC (quic) WG Interim Meeting: 2019-01-30
X-Test-IDTracker: no
X-IETF-IDTracker: 6.87.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154022115922.5895.12548864351533491613@ietfa.amsl.com>
Date: Mon, 22 Oct 2018 08:12:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/KyqOfRVz7u7F8zI13b856NaE3Fc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 22 Oct 2018 15:12:39 -0000

The QUIC (quic) Working Group will hold
a multi-day interim meeting.

Session 1:
2019-01-30     09:00 to 17:00  Asia/Tokyo
Session 2:
2019-01-31     09:00 to 17:00  Asia/Tokyo

Meeting Location:
Tokyo, JP

Agenda:
https://github.com/quicwg/wg-materials/blob/master/interim-19-01/agenda.md

Information about remote participation:
yes, after registration, see https://github.com/quicwg/wg-materials/blob/master/interim-19-01/arrangements.md

https://github.com/quicwg/wg-materials/blob/master/interim-19-01/arrangements.md


From nobody Mon Oct 22 10:03:17 2018
Return-Path: <mail@beatricemartini.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 34384130E98 for <quic@ietfa.amsl.com>; Mon, 22 Oct 2018 10:03:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=beatricemartini-it.20150623.gappssmtp.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 udX8qK5tubOo for <quic@ietfa.amsl.com>; Mon, 22 Oct 2018 10:02:59 -0700 (PDT)
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (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 BCBB7130EA0 for <quic@ietf.org>; Mon, 22 Oct 2018 10:02:59 -0700 (PDT)
Received: by mail-io1-xd36.google.com with SMTP id k17-v6so1894532ioc.4 for <quic@ietf.org>; Mon, 22 Oct 2018 10:02:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=beatricemartini-it.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=k/085ktDt/aMUHmtQGP6S7EVLfZhfVuw/bFaCnoV2xU=; b=roGw5+z3BCED/QEu2yBGtmZ6H5H14v6DfQwusiEGZB5XlDKjqwctirXhkdb5+lDDEx IKZHxJAG8Wxi4/IDa/yKiqFgtHldLgIQ+jtmJ6Rl7iXWSPwqp9L1jqE1Db8hGOxY81gu uGA1V0Ms+gh89aBGWejIPqUd48lUR5CkiJpR/5UODoAKUAvhbSmNIpReD/o2kVL8Xkx4 3WtM3eezlRx1OYBp4g2sehQuvUiIZEeLLFyuCjDgP1kZmDTV4m4ZKMC8LN6w+LyM/uoG 67IRL6+yvew54HDOzI4G9tYnYQcgBfT+/wX6RfdZElVbkrOjYsauvkbLW8LONyNIhVYE qCaw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=k/085ktDt/aMUHmtQGP6S7EVLfZhfVuw/bFaCnoV2xU=; b=Kj3ICyTf4HBeRiF+8SOOCDGrnyd4U3DkwOoKCHbKFXV1/CWBABzo9ZTggLKUQUr3Eg /kb1ZzUgEx1PlqH2uyDYtfag3o6mlQxWCCNCep9HLdCWxriNbNIpRBMTkQi6T6M2dZWi Qr3LjnNTfh94qS+RVmRY/pIHIQFfL8HXAYjXAL/ptN6m0yqcA09P1LbhgAie+QL8xnQA EyHxWKpcSRcPuRCJPWP247PJLUX9WIsjm44KB+/TD53YF+ENynSFAwFg552vyp+Fs2Cp HDoKASwRbAzlJUXKmDW1Cav9x7ew5e1K7s8IaO+AcJ9jmk0O1qxYrA7O4QfiFj/Rgrxh TDfQ==
X-Gm-Message-State: AGRZ1gI3rPR8Ae3jh9sTejEgsHZrljuBTivKEBQ8iWAQEOHYjCuKOdU2 Kotys/UQoNtIGnDGL0756FmQXcl157RYWJNJP9QP0dYHb30=
X-Google-Smtp-Source: AJdET5daREnbV+qdoJ1T05uO6f6csMWZ5GEAJRiFWs9ApQ52K0ypeasTkQE7jO0tSH3q6yvmdt4mAvAB0X4DVghnYV4=
X-Received: by 2002:a6b:f10f:: with SMTP id e15-v6mr8673792iog.271.1540227778654;  Mon, 22 Oct 2018 10:02:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a02:5d84:0:0:0:0:0 with HTTP; Mon, 22 Oct 2018 10:02:58 -0700 (PDT)
From: Beatrice Martini <mail@beatricemartini.it>
Date: Mon, 22 Oct 2018 19:02:58 +0200
Message-ID: <CA+0Hr7uPXE4gng6+SvQ+=hE_n2tC2Zb-yxN9S8NiicgR_jGg_w@mail.gmail.com>
Subject: Human Rights Review of QUIC
To: quic@ietf.org
Cc: Niels ten Oever <mail@nielstenoever.net>
Content-Type: multipart/alternative; boundary="0000000000009ecce20578d43975"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7vkCBAAmhJGZb_e5JO4ErNU3iAw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 22 Oct 2018 17:03:07 -0000

--0000000000009ecce20578d43975
Content-Type: text/plain; charset="UTF-8"

Hello,

I am Beatrice Martini, participant in the IRTF Human Rights Protocol
Considerations Research Group and Human Rights Review Team.

Nice to connect!

Together with co-author and fellow HRPC and HR-rt participant Niels ten
Oever, we worked on a Human Rights Review of QUIC.

Our aim was to contribute to the QUIC WG efforts by providing relevant and
applicable feedback. For this reason, as you can also read in the
"Methodology and Process" section of the document, we conducted our review
analyzing drafts through the perspective of the Guidelines for Human Rights
Protocol Considerations outlined in RFC8280, as well as by doing a series
of interviews with QUIC WG chairs, document authors and participants.

We just published the review as an Internet Draft, as a way to make it more
easy to read and share. You can find the review at:

https://tools.ietf.org/html/draft-martini-hrpc-quichr-00

Thanks to all the WG participants and document authors and editors who
contributed to our work and have been so gracious with their time.

We hope you will find the review of interest, and we very much welcome your
input, questions and suggestions.

Thank you!

Best,
Beatrice & Niels

--0000000000009ecce20578d43975
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div id=3D"gmail-magicdomid593" class=3D"gmail-ace-line"><=
span class=3D"gmail-author-a-fjz87zz87zz79zz85z8z82zz84zlz73zjsbz71zu">Hell=
o,</span></div><div id=3D"gmail-magicdomid595" class=3D"gmail-ace-line"><br=
></div><div id=3D"gmail-magicdomid2721" class=3D"gmail-ace-line"><span clas=
s=3D"gmail-author-a-fjz87zz87zz79zz85z8z82zz84zlz73zjsbz71zu">I am Beatrice=
 Martini, </span><span class=3D"gmail-author-a-s09z83zz66zh7ez88zvhz80zz83z=
82u">participant in the</span><span class=3D"gmail-author-a-fjz87zz87zz79zz=
85z8z82zz84zlz73zjsbz71zu"> IRTF Human Rights Protocol Considerations Resea=
rch Group and Human Rights Review Team.</span></div><div class=3D"gmail-ace=
-line"><span class=3D"gmail-author-a-fjz87zz87zz79zz85z8z82zz84zlz73zjsbz71=
zu"><br></span></div><div class=3D"gmail-ace-line"><span class=3D"gmail-aut=
hor-a-fjz87zz87zz79zz85z8z82zz84zlz73zjsbz71zu">Nice to connect!</span></di=
v><div id=3D"gmail-magicdomid678" class=3D"gmail-ace-line"><br></div><div i=
d=3D"gmail-magicdomid2725" class=3D"gmail-ace-line"><span class=3D"gmail-au=
thor-a-fjz87zz87zz79zz85z8z82zz84zlz73zjsbz71zu">Together with co-author an=
d fellow HRPC and HR-rt </span><span class=3D"gmail-author-a-s09z83zz66zh7e=
z88zvhz80zz83z82u">participant</span><span class=3D"gmail-author-a-fjz87zz8=
7zz79zz85z8z82zz84zlz73zjsbz71zu"> Niels ten Oever, we worked on a Human Ri=
ghts Review of QUIC.</span></div><div id=3D"gmail-magicdomid2274" class=3D"=
gmail-ace-line"><br></div><div id=3D"gmail-magicdomid2732" class=3D"gmail-a=
ce-line"><span class=3D"gmail-author-a-fjz87zz87zz79zz85z8z82zz84zlz73zjsbz=
71zu">Our aim was to contribute to the QUIC WG efforts by providing relevan=
t and applicable feedback. For this reason, as you can also read in the &qu=
ot;Methodology and Process&quot; section of the document, we conducted our =
review analyzing drafts through the perspective of the Guidelines for Human=
 Rights Protocol Considerations outlined in RFC8280, as well as </span><spa=
n class=3D"gmail-author-a-s09z83zz66zh7ez88zvhz80zz83z82u">by doing</span><=
span class=3D"gmail-author-a-fjz87zz87zz79zz85z8z82zz84zlz73zjsbz71zu"> a s=
eries of interviews with QUIC WG chairs, document authors and <span class=
=3D"gmail-author-a-s09z83zz66zh7ez88zvhz80zz83z82u">participants</span>.<br=
></span></div><div id=3D"gmail-magicdomid1412" class=3D"gmail-ace-line"><br=
></div><div id=3D"gmail-magicdomid2908" class=3D"gmail-ace-line"><span clas=
s=3D"gmail-author-a-fjz87zz87zz79zz85z8z82zz84zlz73zjsbz71zu">We just publi=
shed t</span><span class=3D"gmail-author-a-s09z83zz66zh7ez88zvhz80zz83z82u"=
>he review</span><span class=3D"gmail-author-a-fjz87zz87zz79zz85z8z82zz84zl=
z73zjsbz71zu"> as an Internet Draft, as a way to make it more easy to read =
and share. </span><span class=3D"gmail-author-a-s09z83zz66zh7ez88zvhz80zz83=
z82u">You can find the review at</span><span class=3D"gmail-author-a-fjz87z=
z87zz79zz85z8z82zz84zlz73zjsbz71zu">:</span></div><div id=3D"gmail-magicdom=
id1455" class=3D"gmail-ace-line"><br></div><div id=3D"gmail-magicdomid2781"=
 class=3D"gmail-ace-line"><span class=3D"gmail-author-a-s09z83zz66zh7ez88zv=
hz80zz83z82u gmail-url"><a href=3D"https://tools.ietf.org/html/draft-martin=
i-hrpc-quichr-00">https://tools.ietf.org/html/draft-martini-hrpc-quichr-00<=
/a></span></div><div id=3D"gmail-magicdomid1468" class=3D"gmail-ace-line"><=
br></div><div id=3D"gmail-magicdomid2905" class=3D"gmail-ace-line"><span cl=
ass=3D"gmail-author-a-s09z83zz66zh7ez88zvhz80zz83z82u">Thanks to all the WG=
 participants and document authors and editors who</span><span class=3D"gma=
il-author-a-fjz87zz87zz79zz85z8z82zz84zlz73zjsbz71zu"> contributed to our w=
ork and</span><span class=3D"gmail-author-a-s09z83zz66zh7ez88zvhz80zz83z82u=
"> have been so gracious with their time.=C2=A0</span></div><div id=3D"gmai=
l-magicdomid2909" class=3D"gmail-ace-line"><br></div><div id=3D"gmail-magic=
domid2958" class=3D"gmail-ace-line"><span class=3D"gmail-author-a-fjz87zz87=
zz79zz85z8z82zz84zlz73zjsbz71zu">W</span><span class=3D"gmail-author-a-s09z=
83zz66zh7ez88zvhz80zz83z82u">e</span><span class=3D"gmail-author-a-fjz87zz8=
7zz79zz85z8z82zz84zlz73zjsbz71zu"> hope you will find the review of interes=
t, and </span><span class=3D"gmail-author-a-s09z83zz66zh7ez88zvhz80zz83z82u=
">we very much welcome</span><span class=3D"gmail-author-a-fjz87zz87zz79zz8=
5z8z82zz84zlz73zjsbz71zu"> your input</span><span class=3D"gmail-author-a-s=
09z83zz66zh7ez88zvhz80zz83z82u">, </span><span class=3D"gmail-author-a-fjz8=
7zz87zz79zz85z8z82zz84zlz73zjsbz71zu">questions and </span><span class=3D"g=
mail-author-a-s09z83zz66zh7ez88zvhz80zz83z82u">suggestions</span><span clas=
s=3D"gmail-author-a-fjz87zz87zz79zz85z8z82zz84zlz73zjsbz71zu">.</span></div=
><div id=3D"gmail-magicdomid2916" class=3D"gmail-ace-line"><br></div><div i=
d=3D"gmail-magicdomid2922" class=3D"gmail-ace-line"><span class=3D"gmail-au=
thor-a-fjz87zz87zz79zz85z8z82zz84zlz73zjsbz71zu">Thank you!<br></span></div=
><div id=3D"gmail-magicdomid2912" class=3D"gmail-ace-line"><br></div><div i=
d=3D"gmail-magicdomid2214" class=3D"gmail-ace-line"><span class=3D"gmail-au=
thor-a-fjz87zz87zz79zz85z8z82zz84zlz73zjsbz71zu">Best,</span></div><div id=
=3D"gmail-magicdomid2335" class=3D"gmail-ace-line"><span class=3D"gmail-aut=
hor-a-fjz87zz87zz79zz85z8z82zz84zlz73zjsbz71zu">Beatrice &amp; Niels</span>=
</div><br></div>

--0000000000009ecce20578d43975--


From nobody Mon Oct 22 14:59:03 2018
Return-Path: <mnot@mnot.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 6735212D4F1 for <quic@ietfa.amsl.com>; Mon, 22 Oct 2018 14:58:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=2y2ZmF19; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=wJ45dz2M
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 f44DyieUVukl for <quic@ietfa.amsl.com>; Mon, 22 Oct 2018 14:58:50 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0AC41130E95 for <quic@ietf.org>; Mon, 22 Oct 2018 14:58:44 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id EB08221D12 for <quic@ietf.org>; Mon, 22 Oct 2018 17:58:42 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 22 Oct 2018 17:58:42 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=from :content-type:content-transfer-encoding:mime-version:subject :date:references:to:in-reply-to:message-id; s=fm1; bh=F2R0kJdCsV caGjkWNH0h/t7Y4sBUPxVMbgz2Ye14Mzk=; b=2y2ZmF19uN1vgrDpGjtHdqnOnA 9+Kg5RVT4cVFID78levl0kk9gMP863cMwahr3gcuS61CBy9q5SsuE6JbPFdP+Bjf yX2LS+5PsLHPPL3YvP+xM19WxfPjclH2NanT5SBcvDiB8/kOgwYQpn2GXQqeftqp nlUhQz4SPtmjnqutx1gUTFneWiU4sECBzh/c9oAg1WHqCfzOHXmGTf+BF7VMIm8z 50r2fj9Da4Qe06NJuxqEe5kCfbi3RzCixE+6JM8EECJPA/xKK2vJm3aHTpTDnxc3 Uc59ObQQ/rsoRdZ3gkHzkd7c7vKs7Qko5zOMmyicKpKCy5uET41IJvnFAoiA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=F2R0kJdCsVcaGjkWNH0h/t7Y4sBUPxVMbgz2Ye14M zk=; b=wJ45dz2Mv1mXKgDiN3VjPZtkIwmnW00/tkB4OLlo4w5Ebwh9TKAZfjl0J nlmShbGWbIX+vYWw4HmA4+alnlIepSw6LbD052WiQbN42TrPp05SFzruVgjDieFn r6u48qzPsO9Q7ZUSdt1kN0FdUofZ/O+b6VUeNtdzFCIOdj3zcOpk0MZ8JkelYG1+ Zlc+PyjIbBa+ZUNjkQSZBGHHv2sLqrZtuUnjYN9OqZA2WRDv7uHnqllvJkN3/Bg8 5Pu0P8UhfxluNVA/qa4CEM2NdCW93MMnteeOagTUH9lmaPXrLSRlQjdIUw9kqW5U VWhKDzW67QaEXpaPsipGAV2VNZWDA==
X-ME-Sender: <xms:EkjOWx68DAMDv839pHaJpLPvyfcnuKKl7TxVjg0JUCC0RJNTGqJLyQ>
X-ME-Proxy: <xmx:EkjOW81m-_rJl4ZfILOwda77OPfErm3alJwUHeY68VwvQXfhzpVK_A> <xmx:EkjOW38HpqVIvw-rzo7O9sxGite2kgYpUrCiievnF1vbkTW8uq5ldQ> <xmx:EkjOW5H2CbAOQJIYun5N5prerKweO1jtlflekl1SHd2BVcYvC92sWg> <xmx:EkjOW4q8xWyTWEKr9Sv0JizZr41PONk6TSb6EF0AeP2_l_TlhGqgKQ> <xmx:EkjOWzW8rbvPOYuzdC8DptwEgCMM7nwi7548reMAD9hsMgeat2SKfw> <xmx:EkjOW3WnmRYjb_XeKY3806Zi2aS3jx1LZa1RgbWTsAdLa-SfRtP64g>
Received: from attitudadjuster.mnot.net (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 84DF7102E0 for <quic@ietf.org>; Mon, 22 Oct 2018 17:58:41 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: Re: QUIC (quic) WG Interim Meeting: 2019-01-30
Date: Tue, 23 Oct 2018 08:58:38 +1100
References: <154022115922.5895.12548864351533491613@ietfa.amsl.com>
To: IETF QUIC WG <quic@ietf.org>
In-Reply-To: <154022115922.5895.12548864351533491613@ietfa.amsl.com>
Message-Id: <9E04DD9B-9CA8-4C7E-A6C4-20FC001F3193@mnot.net>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/lQ6UU3PMiX_CtNMonJXV1FhjzDU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 22 Oct 2018 21:59:03 -0000

... and registration is now open at:
  https://goo.gl/forms/H5NA9n0eLTtsm5IU2

Registration closes on 18 December.

Cheers,


> On 23 Oct 2018, at 2:12 am, IESG Secretary <iesg-secretary@ietf.org> =
wrote:
>=20
> The QUIC (quic) Working Group will hold
> a multi-day interim meeting.
>=20
> Session 1:
> 2019-01-30     09:00 to 17:00  Asia/Tokyo
> Session 2:
> 2019-01-31     09:00 to 17:00  Asia/Tokyo
>=20
> Meeting Location:
> Tokyo, JP
>=20
> Agenda:
> =
https://github.com/quicwg/wg-materials/blob/master/interim-19-01/agenda.md=

>=20
> Information about remote participation:
> yes, after registration, see =
https://github.com/quicwg/wg-materials/blob/master/interim-19-01/arrangeme=
nts.md
>=20
> =
https://github.com/quicwg/wg-materials/blob/master/interim-19-01/arrangeme=
nts.md
>=20

--
Mark Nottingham   https://www.mnot.net/


From nobody Mon Oct 22 23:38:28 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E7D79130E94; Mon, 22 Oct 2018 23:38:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-spin-exp-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.87.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <154027669890.13766.10576203850224302194@ietfa.amsl.com>
Date: Mon, 22 Oct 2018 23:38:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/XuTpv16PEyIpRzCwXQ7k0dltQcc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 23 Oct 2018 06:38:19 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : The QUIC Latency Spin Bit
        Authors         : Brian Trammell
                          Mirja Kuehlewind
	Filename        : draft-ietf-quic-spin-exp-01.txt
	Pages           : 8
	Date            : 2018-10-22

Abstract:
   This document specifies the addition of a latency spin bit to the
   QUIC transport protocol and describes how to use it to measure end-
   to-end latency.

Note to Readers

   This document specifies an experimental delta to the QUIC transport
   protocol.  Specifically, this experimentation is intended to
   determine:

   o  the impact of the addition of the latency spin bit on
      implementation and specification complexity; and

   o  the accuracy and value of the information derived from spin bit
      measurement on live network traffic.

   The information generated by this experiment will be used by the QUIC
   working group as input to a decision about the standardization of the
   latency spin bit.  Although this is a Working Group document, it is
   currently NOT a Working Group deliverable.

   Discussion of this draft takes place on the QUIC working group
   mailing list (quic@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/search/?email_list=quic [1].

   Working Group information can be found at https://github.com/quicwg
   [2]; source code and issues list for this draft can be found at
   https://github.com/quicwg/base-drafts/labels/-spin [3].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-spin-exp/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-spin-exp-01
https://datatracker.ietf.org/doc/html/draft-ietf-quic-spin-exp-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-spin-exp-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Oct 23 16:55:38 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 58D4B130DC6; Tue, 23 Oct 2018 16:55:36 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-recovery-16.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.87.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <154033893631.31232.9554289030536571198@ietfa.amsl.com>
Date: Tue, 23 Oct 2018 16:55:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/PUzKh7R3KsD2sJohMbbM2s3CaVY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 23 Oct 2018 23:55:37 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : QUIC Loss Detection and Congestion Control
        Authors         : Jana Iyengar
                          Ian Swett
	Filename        : draft-ietf-quic-recovery-16.txt
	Pages           : 33
	Date            : 2018-10-23

Abstract:
   This document describes loss detection and congestion control
   mechanisms for QUIC.

Note to Readers

   Discussion of this draft takes place on the QUIC working group
   mailing list (quic@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/search/?email_list=quic [1].

   Working Group information can be found at https://github.com/quicwg
   [2]; source code and issues list for this draft can be found at
   https://github.com/quicwg/base-drafts/labels/-recovery [3].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-recovery/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-recovery-16
https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-16

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-recovery-16


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Oct 23 16:57:03 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 59AD7130E9B; Tue, 23 Oct 2018 16:56:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-transport-16.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.87.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <154033900532.31361.12068796633730113327@ietfa.amsl.com>
Date: Tue, 23 Oct 2018 16:56:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/75Xo7o4e_hZYfj-h3msH6Maj5mY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 23 Oct 2018 23:56:56 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : QUIC: A UDP-Based Multiplexed and Secure Transport
        Authors         : Jana Iyengar
                          Martin Thomson
	Filename        : draft-ietf-quic-transport-16.txt
	Pages           : 135
	Date            : 2018-10-23

Abstract:
   This document defines the core of the QUIC transport protocol.  This
   document describes connection establishment, packet format,
   multiplexing, and reliability.  Accompanying documents describe the
   cryptographic handshake and loss detection.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-transport/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-transport-16
https://datatracker.ietf.org/doc/html/draft-ietf-quic-transport-16

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-transport-16


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Oct 23 16:57:10 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C8D68130ED0; Tue, 23 Oct 2018 16:56:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-tls-16.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.87.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <154033901277.31305.1644356425473989844@ietfa.amsl.com>
Date: Tue, 23 Oct 2018 16:56:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/N8IbTvJrh-KTJHxEacpzPqNfghQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 23 Oct 2018 23:57:01 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : Using Transport Layer Security (TLS) to Secure QUIC
        Authors         : Martin Thomson
                          Sean Turner
	Filename        : draft-ietf-quic-tls-16.txt
	Pages           : 32
	Date            : 2018-10-23

Abstract:
   This document describes how Transport Layer Security (TLS) is used to
   secure QUIC.

Note to Readers

   Discussion of this draft takes place on the QUIC working group
   mailing list (quic@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/search/?email_list=quic [1].

   Working Group information can be found at https://github.com/quicwg
   [2]; source code and issues list for this draft can be found at
   https://github.com/quicwg/base-drafts/labels/-tls [3].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-tls/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-tls-16
https://datatracker.ietf.org/doc/html/draft-ietf-quic-tls-16

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-tls-16


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Oct 23 16:58:52 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E6F1130E92; Tue, 23 Oct 2018 16:58:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-http-16.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.87.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <154033910908.31236.15085086520560447274@ietfa.amsl.com>
Date: Tue, 23 Oct 2018 16:58:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/TKqS4ZjdcORBGO5iYpMk6Jmgb7E>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 23 Oct 2018 23:58:42 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : Hypertext Transfer Protocol (HTTP) over QUIC
        Author          : Mike Bishop
	Filename        : draft-ietf-quic-http-16.txt
	Pages           : 48
	Date            : 2018-10-23

Abstract:
   The QUIC transport protocol has several features that are desirable
   in a transport for HTTP, such as stream multiplexing, per-stream flow
   control, and low-latency connection establishment.  This document
   describes a mapping of HTTP semantics over QUIC.  This document also
   identifies HTTP/2 features that are subsumed by QUIC, and describes
   how HTTP/2 extensions can be ported to QUIC.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-http/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-http-16
https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-16

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-http-16


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Oct 23 17:26:33 2018
Return-Path: <martin.thomson@gmail.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 A15BB130DE8 for <quic@ietfa.amsl.com>; Tue, 23 Oct 2018 17:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 j8RObHF4oK9W for <quic@ietfa.amsl.com>; Tue, 23 Oct 2018 17:26:30 -0700 (PDT)
Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (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 EED3712D4EA for <quic@ietf.org>; Tue, 23 Oct 2018 17:26:29 -0700 (PDT)
Received: by mail-ot1-x32d.google.com with SMTP id z15so3253608otm.12 for <quic@ietf.org>; Tue, 23 Oct 2018 17:26:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=7Cf8Jn5Nmj8zgBGVOy98MVTSUwsoAADdYWkJxHzxgtw=; b=A9h/VznQzKQRENjaJQglDydlixki0RBOVSh8FgFNvgugOJe0mJnT9PD2pccIWFhSAF fzrev7eNObhVxHV/zNlnpOTuf1MUHK6WZ31JIQdptO7lU0K101Lhi78q/z3Ecwh7P0ya XnQ2U37p9TwYGURv46vRt8WLkzzdGjRuNNFNZ6k2nUYhpMQcp3NbJ18SSySNm6RZ6Z2c 7HxWSlYnTRY2AtwN4ahfJ7bs3FylKdKzbcTojtCfs0vjKKfud3twxs+MFIykhibN6xvC LxCWRRH7HWWAk7cc3CORxbL9njsYtxRma0wGrwiWcaUn2TFZPOMQ9GTCvfH43F8i6J1P vo0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=7Cf8Jn5Nmj8zgBGVOy98MVTSUwsoAADdYWkJxHzxgtw=; b=LuvxBI4MHm7fkqzYvT6xRksQ7vjejrzS3p8bHNnRpDELPAx4jK4AWWguMrekpItqLV xm5DJ1SBJNCryBK5ZBhoahtt0RrCcLL4qh0KgT9/N68pLia+AiJEsZXAbR4Y59GDeeKp voKD0A+c3D9j9J27PeM90PWQDZgsw1HbGsmylKxLCS2AajLIEB2nhfGJ7Cgu/2FVWVLy 6erXautEo+AFT05+RajI4pkCCna0gcmVYfsAllwnlLd3VvbYfoN+46vtb29sNLknh9xb hxaF15YAQpTF07W1o7naU94aFWmXVcmOxR4kfF5WrQQjIZOubyRlFtjv+b6gtm53Z/s3 KTIA==
X-Gm-Message-State: AGRZ1gLzduAgm8V5HmY6n6NFrTTSWmTqGhItyCLdLg4dBZYIKQOLtntm f4edWsjGqFHtoqBSX2nhjuxPDpjmg0umeHR+EJCeorTn
X-Google-Smtp-Source: AJdET5dgddh7oOteQv6iF8QUcHAQ6gN5jYrKtxNIVKMIRwbLEDwmyQhL/khaL5ept3Y5zOfc8RwSBz0Ht542o9vQtQs=
X-Received: by 2002:a9d:7602:: with SMTP id k2mr282033otl.299.1540340789018; Tue, 23 Oct 2018 17:26:29 -0700 (PDT)
MIME-Version: 1.0
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 24 Oct 2018 11:26:20 +1100
Message-ID: <CABkgnnXBM-TXyfddDKEEqis3d+rsdjYRAWsaJtPNWjaN8jJbxQ@mail.gmail.com>
Subject: -16 drafts
To: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/MkNME5jTFRcXsUamJkY3IrRRn1Q>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Oct 2018 00:26:32 -0000

As you can see, there are new drafts.  There wasn't going to be, but
we took advantage of the deadline extension.

These drafts look a lot different to the -15 drafts, but there should
be no substantive technical changes.  But there has been a ton of
editorial work done.  The editors are of the view that the structure
is now more stable.  There is still a good amount of cleanup to do to
make things stitch together more coherently, but it shouldn't be
structural.

If you had been holding back on editorial comments in your reviews of
the docs, hold back no longer.  As always, pull requests are the
preferred form of currency (short of actual currency, that is).


From nobody Tue Oct 23 17:29:01 2018
Return-Path: <lucaspardue.24.7@gmail.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 5B5EA130DE8 for <quic@ietfa.amsl.com>; Tue, 23 Oct 2018 17:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 e7D8YDglTFcp for <quic@ietfa.amsl.com>; Tue, 23 Oct 2018 17:28:59 -0700 (PDT)
Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (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 3B2DB128CB7 for <quic@ietf.org>; Tue, 23 Oct 2018 17:28:59 -0700 (PDT)
Received: by mail-vs1-xe2a.google.com with SMTP id e206so2087833vsd.0 for <quic@ietf.org>; Tue, 23 Oct 2018 17:28:59 -0700 (PDT)
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=8QDYz+PDcl7jduswizAd4oRKDkEMjgd+D0YmWxWuW9A=; b=WtHEMEzy1nAGj1xGsjqMFZ5YMQfNgIKsBvFB+WBUqvllVRatPAre27s7JtZ2y8YJhV ZohpEynQaj297qmFug9mGeyzxesEg4C7PQ+RaI8Vjqc3cf/nVAcaF9WBoRr2uA8WvlJy 0ZP4YqdEeRDDxX3vNJdYwGHP6ncGkJfAJr4kxFZe3YoKgoCA6Wv5gNGqo2yvCgM9bkGe J9toGgkAJEvpQaFGDnY57RakSaA28hyxYJydh2qbzdBdLkPgsFcHq5cSOSeVE0O5WxZU a3dv0lhGDkXlM9/DMog1rUzA5XIG/uIRobMnATDIG+dDY5Ebmmhwt4Cy34MXFM69N8+j aGig==
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=8QDYz+PDcl7jduswizAd4oRKDkEMjgd+D0YmWxWuW9A=; b=BGcToWvm8L+yxDPfUT8st8wEwWDYeLSAsZwU3tPlAChCQ5DG+Qjf/45SZ97nMgzWOZ GIjLrjXosTbuu2ZG7/JnkOkAkpbV02VCU+K3SWoRdYEDDYCUrM0CWgMnnelgbnj4NDZQ fc90+DxFqjMmaueNdsDuQHphqGi8kMAW3L94EuvpyVW807QNsdFuXv0j4oLgrjVYgorE 2TltcqCP9kn1GWJORWM455jD2gYeTER99FlWMsWK9bI3s4/sG+nVcB/bxbK226v4GN6p +M+70q4x4xG+ymp4aIvXER96jMzXsyp2vymxiGHjhstpWNpWCGPRq4xW/O+Cz7sB9JxC aZqw==
X-Gm-Message-State: AGRZ1gKCdAoK2GMx6S12vMh/mmtancpmxjwg3uXsQGgRPzd+SYDeJTGG eSjpbp90KHjpIaMJ+2wmaHscWykC1cmy6JHOUH4=
X-Google-Smtp-Source: AJdET5czKl5AUSLLtmIKU8DMAt4Cmro31YDh9KgPpiOUMq1NDxKzKujDOVol9XFWHMmvfzy8RGo8rMtj7lyxj3xCzVE=
X-Received: by 2002:a67:4719:: with SMTP id u25mr197737vsa.27.1540340938340; Tue, 23 Oct 2018 17:28:58 -0700 (PDT)
MIME-Version: 1.0
References: <CABkgnnXBM-TXyfddDKEEqis3d+rsdjYRAWsaJtPNWjaN8jJbxQ@mail.gmail.com>
In-Reply-To: <CABkgnnXBM-TXyfddDKEEqis3d+rsdjYRAWsaJtPNWjaN8jJbxQ@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Wed, 24 Oct 2018 01:28:46 +0100
Message-ID: <CALGR9obh3PKCDKBcLYmEmw+A5T-hL-K0UbxhuwBx4FPknip0VQ@mail.gmail.com>
Subject: Re: -16 drafts
To: Martin Thomson <martin.thomson@gmail.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000767cbe0578ee927c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/DC56B3VZJJaxm8DODNFeQacnK-k>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Oct 2018 00:29:00 -0000

--000000000000767cbe0578ee927c
Content-Type: text/plain; charset="UTF-8"

Great stuff, thanks editors and contributors!

On Wed, 24 Oct 2018, 01:26 Martin Thomson, <martin.thomson@gmail.com> wrote:

> As you can see, there are new drafts.  There wasn't going to be, but
> we took advantage of the deadline extension.
>
> These drafts look a lot different to the -15 drafts, but there should
> be no substantive technical changes.  But there has been a ton of
> editorial work done.  The editors are of the view that the structure
> is now more stable.  There is still a good amount of cleanup to do to
> make things stitch together more coherently, but it shouldn't be
> structural.
>
> If you had been holding back on editorial comments in your reviews of
> the docs, hold back no longer.  As always, pull requests are the
> preferred form of currency (short of actual currency, that is).
>
>

--000000000000767cbe0578ee927c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Great stuff, thanks editors and contributors!</div><br><d=
iv class=3D"gmail_quote"><div dir=3D"ltr">On Wed, 24 Oct 2018, 01:26 Martin=
 Thomson, &lt;<a href=3D"mailto:martin.thomson@gmail.com">martin.thomson@gm=
ail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">As you can s=
ee, there are new drafts.=C2=A0 There wasn&#39;t going to be, but<br>
we took advantage of the deadline extension.<br>
<br>
These drafts look a lot different to the -15 drafts, but there should<br>
be no substantive technical changes.=C2=A0 But there has been a ton of<br>
editorial work done.=C2=A0 The editors are of the view that the structure<b=
r>
is now more stable.=C2=A0 There is still a good amount of cleanup to do to<=
br>
make things stitch together more coherently, but it shouldn&#39;t be<br>
structural.<br>
<br>
If you had been holding back on editorial comments in your reviews of<br>
the docs, hold back no longer.=C2=A0 As always, pull requests are the<br>
preferred form of currency (short of actual currency, that is).<br>
<br>
</blockquote></div>

--000000000000767cbe0578ee927c--


From nobody Thu Oct 25 16:20:57 2018
Return-Path: <martin.thomson@gmail.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 6D065130FA6 for <quic@ietfa.amsl.com>; Thu, 25 Oct 2018 16:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 iaILVx84KURG for <quic@ietfa.amsl.com>; Thu, 25 Oct 2018 16:20:51 -0700 (PDT)
Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (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 29C8E130E08 for <quic@ietf.org>; Thu, 25 Oct 2018 16:20:17 -0700 (PDT)
Received: by mail-ot1-x32d.google.com with SMTP id k9so10811891otl.10 for <quic@ietf.org>; Thu, 25 Oct 2018 16:20:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=lGBDYFIsHqIxjGrX4NklHThxmOQI9wNX6kas3TcxSDU=; b=PCKP0FrXP2xyIthno9jIKKsM547SNsaQp8lVLNbI60pu7f3Io4lEneGTMZHq9uA/Fp 7dn431j0yvAzOMBx1wle8TmesE3zsaumxc4BpXZ+R9DlkA4NbLRa5LyRiV0fr87z7Mwx 7/r2UvtlvXWoXhplgTu6lF76QzTMtM3X5Lmxc8KXLSGnrXa4JRxJcWtbbjwRdtqo0JTK wCZtaJXu0G2FPeL87vwqI0DVcQNbGl9Ko4optRHbJctC8rtpsYOyQq4Xxnu+ws84nE0o B6hK7mrncw3t3lWkc1L7/NEMGpU7T/wwD1Svx8fhuKvPWYk4+viVrgTFosbvocyypQsw jxng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=lGBDYFIsHqIxjGrX4NklHThxmOQI9wNX6kas3TcxSDU=; b=Tn856/1YDzybOtVNLgL3dzXxiPXhBvP+u31UTAZzOvlkDnVbaTiEzGx0tJqzluvpWV QpLEpRBvImGTVUQNp2KXeCwpA47/f2SbmV+sb+DGkJ+5ov8J50XHTHeaHPLvR4g718en J6tAsYuEOPRH+xnrEGT6aj15LTuqroP/+JzpYIBVBzszCDA+sh+L9QDwNhzHra7Z/By+ Ol9vYqVI/69KbwGRXSary0YQc8JNqlrAXj8kw6b4QJ6nUDORcDufTrmnq17tcXX4MvVZ UdeJPqJvIjnVFOzdOC6etcK9bl6rLbBT1LNHcojawaB3UY9tcb2hElYpPQKc4jcUQnUc 7CRA==
X-Gm-Message-State: AGRZ1gLSGokD1MX1a5gJPkr32ES2QXDrynomdc0yEZiQ400LDo5eFkPU QndwUXEZZO7gDXU3x0kwmZYHHqGNh8UpJPRENRwYBMBqyrw=
X-Google-Smtp-Source: AJdET5dP3r8eyImwY3SFtSKsr9v21IQjSPEsPsVLKfXOJDS/1i7v2UplLWBdMRX5LNO9bN9Beoph/bwkU1G6wcV9/iE=
X-Received: by 2002:a9d:6101:: with SMTP id i1mr796756otj.310.1540509616065; Thu, 25 Oct 2018 16:20:16 -0700 (PDT)
MIME-Version: 1.0
From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 26 Oct 2018 10:20:04 +1100
Message-ID: <CABkgnnVFqdx4VYbqT7SztPf8Q+vWMV86VkOHY-4aGSpauNPapg@mail.gmail.com>
Subject: Big changes in -17
To: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/WBslQf07Frg9t09qQfZYndxww3k>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Oct 2018 23:20:55 -0000

No, that doesn't mean that we're going to be making major changes, but
I did want to draw attention to a few things that seem likely to
happen in -17 in the transport.

I hope that nothing here is a surprise to anyone.

1. Version negotiation.  This was discussed in NY and people seemed to
like the proposed direction.  There is a PR in progress here:
https://github.com/quicwg/base-drafts/pull/1901

2. MAX_STREAMS.  We realized that the accounting for stream limits,
particularly STREAM_ID_BLOCKED, was slightly broken.  Making the frame
consistent with the transport parameter - that is, having a count
rather than a maximum - solves this problem nicely.  PR:
https://github.com/quicwg/base-drafts/pull/1900

3. Renumbering.  With all the changes we've had, we've tried to keep
identifiers stable.  That means we have a fragmented mess.  The
editors plan to renumber frame types and transport parameters to try
to restore some semblance of sanity.

4. The first octet.  We discussed this in NY:
https://github.com/quicwg/wg-materials/blob/master/interim-18-09/minutes.md#first-octet---martin-thomson
and we will have a decision about the spin bit within 2 weeks.  After
that, one of the designs discussed will be implemented.

5. Your last minute changes.  Maybe.  Get them in soon, please.

After that, the list of remaining design issues gets very lean (at
least for the transport draft).  Once we ship -17, the intent is to
raise the bar considerably for changes that aren't clearly bug fixes
or editorial improvements.  The idea is that people can start
deploying -17, so we can all start to learn the hard lessons.
Avoiding gratuitous changes from that point is going to be necessary.


From nobody Sat Oct 27 17:31:07 2018
Return-Path: <mnot@mnot.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 38367130E05 for <quic@ietfa.amsl.com>; Sat, 27 Oct 2018 17:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=Womn+NUE; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=CtrUB8c/
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 yn0qI51qJJZX for <quic@ietfa.amsl.com>; Sat, 27 Oct 2018 17:31:02 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBEC2130E02 for <quic@ietf.org>; Sat, 27 Oct 2018 17:31:01 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 5397D21D03 for <quic@ietf.org>; Sat, 27 Oct 2018 20:30:59 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Sat, 27 Oct 2018 20:30:59 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=from :content-type:content-transfer-encoding:mime-version:subject :message-id:date:to; s=fm1; bh=F5ZsHIOU4bmy4skM4L4c/gIb0qwgM0WBz PYF9RDOtu4=; b=Womn+NUE6OonsEbhxshMEUE1bZI+NSdrsJ6J52yMBvmDwrvUD ReCVOsqBLZnjxU1Rj00v3ko3gX8ODJHhj+SAMsExTRh+CjMpfxVSMVdLKwE4pgc1 bEuaFUQWJn6qYYwswgDFg27BGvxS5Y3SzUMBSQaw94NIQ9+uqZar8lNQMdAldDRW o1gQcd39Ijv+c4WzjQOhzHAvGrTuFmuAqTc0vRbhnqpzwAPal66GXk99dhU+cg3x yxlm2bSSkDrZifK8Fs6Z/AO9xwq3Ne+6b282GnkTd9OFVfYkEUFf25rr5gT9/prk oKcdpIovrHyfOxpCQngSc+9cwYukZBXV91+XQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=F5ZsHI OU4bmy4skM4L4c/gIb0qwgM0WBzPYF9RDOtu4=; b=CtrUB8c/OjIPoBB11ca5vR HHv2MwwQHdPf1QrViObMhZddNhzymTAFokjGtw6OtqJLVtlYtANoQ4jHP3Ye8Nuf Nvai+PehXNv8URyDJgq02rsAqctTcdGNW/FeyJkOlEAwXsvKOnhTRTUdOq5HUe2t o6Rx7/Gidx013HUk2bxeK3ws+TpNTtuJoa8pmUu0qnkS1t7B4rxUJjC5npom9ST/ 0iunlXofjOmVa7sOkTdQArB445FotgYrYx2yAJuNXAsZVTukLlfmXguEISNTop5Y PIKG6P3dtiSMb9mrXS5eU5zFNPCrMrrm3sZQvj8OY4oMrBCgwyz0pt9CqM/2OXdw ==
X-ME-Sender: <xms:QgPVW1FhsKYpcGfnc84WxBHjEwBqxf4Exvgei8Cu4oLyVmWMDbF6Vw>
X-ME-Proxy: <xmx:QgPVWwVpvY_kFr7AoK98IfaznDWw8MkKa_SM80ZAKQmrLIcg-hlQNA> <xmx:QgPVW-o_hh8d5MPN9spiM5wojL2rLJPsYEAR73GrBvY8BcUTdFrfTw> <xmx:QgPVW5W-9-5ta7jEJ-6McZWHL2Ae6FhRNSL397UON1rGQ_wfA5Cvhw> <xmx:QgPVW3Hm_7U_jKfX1ovKhyFm-dHqj4V0DBAP9pWVlhfRkJ94uWC2ig> <xmx:QgPVW4CX8HJP7YtiYdHnHKLwukkQ2Dt49mRlDqXcYFoocCJpoWBD9Q> <xmx:QwPVW8meY2wA225CUrkFUwZU6n8SF2j9MN_1A1FMVChfgdFwfnRAQQ>
Received: from attitudadjuster.mnot.net (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 10485E4A41 for <quic@ietf.org>; Sat, 27 Oct 2018 20:30:57 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: Identifying our deliverables
Message-Id: <578BB4EC-421E-4B21-AA14-B545A41754C8@mnot.net>
Date: Sun, 28 Oct 2018 11:30:55 +1100
To: IETF QUIC WG <quic@ietf.org>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/RLRs4nB1lwFCZ_7k0iuz0ZBa35s>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 28 Oct 2018 00:31:05 -0000

You might recall that we've previously talked about renaming our =
deliverables to clarify their relationship to the input documents =
(sometimes referred to as "gQUIC vs iQUIC").

After a fair amount of discussion with various folks, it seems like =
there's confidence that calling our core deliverable just "QUIC" will =
work, since Google's variant will fade out of use if we succeed, and =
there aren't any good alternatives; our best candidate was "QUIC/2", but =
it was pointed out that this additional level of versioning (since we =
already have a wire version) will cause yet more confusion.

However, in those discussions, a related concern was identified; =
confusion between QUIC-the-transport-protocol, and =
QUIC-the-HTTP-binding. I and others have seen a number of folks not =
closely involved in this work conflating the two, even though they're =
now separate things.

To address this, I'd like to suggest that -- after coordination with the =
HTTP WG -- we rename our the HTTP document to "HTTP/3", and using the =
final ALPN token "h3". Doing so clearly identifies it as another binding =
of HTTP semantics to the wire protocol -- just as HTTP/2 did -- so =
people understand its separation from QUIC.

As part of that discussion, I'd suggest that we formalise that its =
maintenance (as well as that of QPACK) pass off to the HTTP WG once =
we've published it.

I've talked about this with a number of folks. The only concerns I've =
heard so far are:

a) That QUIC isn't yet proven. That's true, but the name won't be =
formalised or used on the wire until the RFC is published, so we have a =
good amount of time to back away. Even then, if it fails in the market, =
we can always skip to HTTP/4 one day, if we need to.=20

b) That discussing naming is a distraction from our technical work. I =
agree with the concern overall, but we have a responsibility to =
communicate clearly with external developers and users, so I'd like to =
have a *limited* discussion about this. Please, don't bike shed.

*Chair hat*=20

We plan on reserving a very small period of time to discuss this in =
Bangkok; barring serious objections (of which "what about this name that =
I like instead?" is not one), we'll bring it up with the HTTP WG in =
Bangkok as well.

Cheers,


--
Mark Nottingham   https://www.mnot.net/


From nobody Sat Oct 27 17:45:29 2018
Return-Path: <do_not_reply@mnot.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 1DA6112008A for <quic@ietfa.amsl.com>; Sat, 27 Oct 2018 17:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=012BJiqE; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=o+zjcZU4
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 zpvvAXnKH6LZ for <quic@ietfa.amsl.com>; Sat, 27 Oct 2018 17:45:26 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB00F130E02 for <quic@ietf.org>; Sat, 27 Oct 2018 17:45:25 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 02F7121E1C for <quic@ietf.org>; Sat, 27 Oct 2018 20:45:24 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sat, 27 Oct 2018 20:45:24 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject:message-id:date; s= fm1; bh=F6zipBMXDq/VH3+ZonjRm/hacUeiQiP8st6yMysP7UY=; b=012BJiqE Vsag71FgzVcNg6guyYLHc5Yc41vkfqyYIKOieOEeEI4YgrpLMrzZz8dUFUdfhZhN BBy5eSM1IvszCYqnQCMk8D6oYk+7rG2ww8sc66iyHm0GYrjRk3o/Z5sp8rOdBoIq IQowJG5nsURFlSqIKTMSpJlIs4RY4WwPlRdZ6bceKL/Zeafghi5uZm/wqdJuVp1S 3ygo/ft/blkhQnijLHC8Y9WZnK1fyfhcp54Kgtb/TKifsIhO3Aq5N8PwaFbpZV6m U0hY5vXCt/cEQcrkuB+jg0vQ/T33yiZpZATHOjtftmATmuZCYP/V2+K5Bhu5a287 HKA3NNWWAlwvww==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=F6zipBMXDq/VH3+ZonjRm/hacUeiQ iP8st6yMysP7UY=; b=o+zjcZU4nB7rztfEb1kka4EkFN5lgmwDmU+aA5IxDukLX gVVGN55Zamp31qTLNXaFfVVk8zkabkap5Eha8/o4B672IupBjK7PZqJYOxfyEanD spoCz7zzVzTEn/plUzK80FR6TFtJAdirhUN+UQQx6pdkebtQMk4KD7/fRsYKqBJB +5690wIIcjNyQemEgzBUPgsf+UGvt97v8zD/oauTem2VyiFBfEbFUnr3Lk+FSlBr P2q8u+4QDQwCKYYeHlkxbo4yTgUiG0PvsGebYvqloAu6KqkDQBNu43N3Qlgm3XM4 3+jaK32M3V1gDSHMyuIyyOYHduCFHpmagG86YTrMw==
X-ME-Sender: <xms:owbVWyl8p_dVgCv3Y74H5_4d4pTIkW51NL5TlWIoFal97RufA3SIIA>
X-ME-Proxy: <xmx:owbVW1_eUzxlFPYSKfcP8KQvtPrBEnos6NXZ7TZcPf_1lsVIIEsJ7Q> <xmx:owbVW0bhuI3CEjgH0Gdxm6fjEBn_G-x_5QLmbPL_TTXL1CX3DYr08Q> <xmx:owbVW5qBZN8LJq4lM-RlxXDjIioCLageBUOQdu4cXGWiabJh2GA62w> <xmx:owbVW0YmXA1N_aIWM1Zf9IsPoQRIzUuFYu13yMewyWNiaK951qpBvA> <xmx:owbVW05PxsH5Cz7kOBgsdK_oNED-2uWpcnNwigKTRvFrNpLNj_MIBw> <xmx:owbVW9nw_KcsJ5Fg3ohUk9pKYWrrcbB-oxoPlyxzluHIEX-wNenU6A>
Received: from cloud.mnot.net (cloud.mnot.net [119.9.43.241]) by mail.messagingengine.com (Postfix) with ESMTPA id 687B6E484F for <quic@ietf.org>; Sat, 27 Oct 2018 20:45:22 -0400 (EDT)
Received: from cloud.mnot.net (localhost [127.0.0.1]) by cloud.mnot.net (Postfix) with ESMTP id 710B8C5CC5 for <quic@ietf.org>; Sun, 28 Oct 2018 00:45:19 +0000 (UTC)
Content-Type: multipart/alternative; boundary="===============6405665489797413784=="
MIME-Version: 1.0
From: =?utf-8?q?Github_Notifications?= <do_not_reply@mnot.net>
To: quic@ietf.org
Subject: Weekly github digest (QUIC Working Group Specifications)
Message-Id: <20181028004519.710B8C5CC5@cloud.mnot.net>
Date: Sun, 28 Oct 2018 00:45:19 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/68wbx4UxzaUSz7VmMSD94wbbbZs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 28 Oct 2018 00:45:28 -0000

--===============6405665489797413784==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Events without label "editorial"

Issues
------
* quicwg/base-drafts (+4/-1/=F0=9F=92=AC6)
  4 issues created:
  - Limiting the number of active connection ids (by plakhera)
    https://github.com/quicwg/base-drafts/issues/1924 =

  - Section 4.2.6 PUSH_PROMISE does not indicate on which stream type this =
frame is allowed (by macoxms)
    https://github.com/quicwg/base-drafts/issues/1920 =

  - Version negotiation might never terminate (by mikkelfj)
    https://github.com/quicwg/base-drafts/issues/1919 =

  - Section 4.2.17 references HTTP_UNEXPECTED_GOAWAY which doesn't exist (b=
y macoxms)
    https://github.com/quicwg/base-drafts/issues/1918 =


  3 issues received 6 new comments:
  - #1834 Flow control for post-handshake CRYPTO messages (3 by kazuho, dav=
idben, martinthomson)
    https://github.com/quicwg/base-drafts/issues/1834 [-tls] [design] =

  - #1918 Section 4.2.17 references HTTP_UNEXPECTED_GOAWAY which doesn't ex=
ist (2 by martinthomson, mikkelfj)
    https://github.com/quicwg/base-drafts/issues/1918 =

  - #1919 Version negotiation might never terminate (1 by mikkelfj)
    https://github.com/quicwg/base-drafts/issues/1919 =


  1 issues closed:
  - Version negotiation might never terminate https://github.com/quicwg/bas=
e-drafts/issues/1919 =




Pull requests
-------------
* quicwg/base-drafts (+8/-0/=F0=9F=92=AC30)
  8 pull requests submitted:
  - define HTTP_UNEXPECTED_GOAWAY (by lnicco)
    https://github.com/quicwg/base-drafts/pull/1925 =

  - Stop reserving application error codes (by martinthomson)
    https://github.com/quicwg/base-drafts/pull/1922 [-http] [-transport] [d=
esign] =

  - No octets (by martinthomson)
    https://github.com/quicwg/base-drafts/pull/1921 =

  - Relax 1200B requirement for Initial ACKs/Retx (by martinduke)
    https://github.com/quicwg/base-drafts/pull/1916 =

  - There are *Two* control streams (by LPardue)
    https://github.com/quicwg/base-drafts/pull/1915 =

  - Stream description moved to section 2 of transport (by LPardue)
    https://github.com/quicwg/base-drafts/pull/1914 =

  - Use octets rather than bytes throughout (by martinthomson)
    https://github.com/quicwg/base-drafts/pull/1912 =

  - Don't amplify accidentally when closing (by martinthomson)
    https://github.com/quicwg/base-drafts/pull/1911 [-transport] =


  7 pull requests received 30 new comments:
  - #1901 Compatible version upgrade (21 by kazuho, marten-seemann, mikkelf=
j, martinthomson, ianswett, RyanAtGoogle, dtikhonov)
    https://github.com/quicwg/base-drafts/pull/1901 [-transport] [design] =

  - #1916 Relax 1200B requirement for Initial ACKs/Retx (3 by martinthomson=
, mikkelfj)
    https://github.com/quicwg/base-drafts/pull/1916 =

  - #1922 Stop reserving application error codes (2 by martinthomson, mikke=
lfj)
    https://github.com/quicwg/base-drafts/pull/1922 [-http] [-transport] [d=
esign] =

  - #1895 Minor edits to amplification attack text (1 by martinduke)
    https://github.com/quicwg/base-drafts/pull/1895 =

  - #1900 One close frames (1 by LPardue)
    https://github.com/quicwg/base-drafts/pull/1900 [-http] [-tls] [-transp=
ort] =

  - #1903 Fix type value for RETIRE_CONNECTION_ID frame (1 by udippant)
    https://github.com/quicwg/base-drafts/pull/1903 =

  - #1819 Let Endpoints Ignore invalid Initial Packets (1 by martinthomson)
    https://github.com/quicwg/base-drafts/pull/1819 =



Repositories tracked by this digest:
-----------------------------------
* https://github.com/quicwg/base-drafts

--===============6405665489797413784==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (QUIC Working Group Specifications)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
</style>
</head>

<body>
<h1>Sunday October 28, 2018</h1>

<p>Events without label "editorial"</p>

<h2>Issues</h2>

<h3>quicwg/base-drafts (+4/-1/=F0=9F=92=AC6)</h3>
  <p class=3D"new">4 issues created:</p>
  <ul>
  <li>#1924 <a href=3D"https://github.com/quicwg/base-drafts/issues/1924">L=
imiting the number of active connection ids</a> (by plakhera) </li>
  =

  <li>#1920 <a href=3D"https://github.com/quicwg/base-drafts/issues/1920">S=
ection 4.2.6 PUSH_PROMISE does not indicate on which stream type this frame=
 is allowed</a> (by macoxms) </li>
  =

  <li>#1919 <a href=3D"https://github.com/quicwg/base-drafts/issues/1919">V=
ersion negotiation might never terminate</a> (by mikkelfj) </li>
  =

  <li>#1918 <a href=3D"https://github.com/quicwg/base-drafts/issues/1918">S=
ection 4.2.17 references HTTP_UNEXPECTED_GOAWAY which doesn&#x27;t exist</a=
> (by macoxms) </li>
  </ul>

  <p>3 issues received 6 new comments:</p>
  <ul>
  <li>#1834 <a href=3D"https://github.com/quicwg/base-drafts/issues/1834">F=
low control for post-handshake CRYPTO messages</a> (3 by kazuho, davidben, =
martinthomson) <span class=3D"label" style=3D"background-color: #fbca04; co=
lor: #000000">-tls</span> <span class=3D"label" style=3D"background-color: =
#1d76db; color: #ffffff">design</span> </li>
  =

  <li>#1918 <a href=3D"https://github.com/quicwg/base-drafts/issues/1918">S=
ection 4.2.17 references HTTP_UNEXPECTED_GOAWAY which doesn&#x27;t exist</a=
> (2 by martinthomson, mikkelfj) </li>
  =

  <li>#1919 <a href=3D"https://github.com/quicwg/base-drafts/issues/1919">V=
ersion negotiation might never terminate</a> (1 by mikkelfj) </li>
  </ul>

  <p>1 issues closed:</p>
  <ul>
  <li>#1919 <a href=3D"https://github.com/quicwg/base-drafts/issues/1919">V=
ersion negotiation might never terminate</a> </li>
  </ul>



<h2>Pull requests</h2>
<h3>quicwg/base-drafts (+8/-0/=F0=9F=92=AC30)</h3>
  <p class=3D"new">8 pull requests submitted:</p>
  <ul>
  <li>#1925 <a href=3D"https://github.com/quicwg/base-drafts/pull/1925">def=
ine HTTP_UNEXPECTED_GOAWAY</a> (by lnicco) </li>
  =

  <li>#1922 <a href=3D"https://github.com/quicwg/base-drafts/pull/1922">Sto=
p reserving application error codes</a> (by martinthomson) <span class=3D"l=
abel" style=3D"background-color: #fbca04; color: #">-http</span> <span clas=
s=3D"label" style=3D"background-color: #fbca04; color: #">-transport</span>=
 <span class=3D"label" style=3D"background-color: #1d76db; color: #">design=
</span> </li>
  =

  <li>#1921 <a href=3D"https://github.com/quicwg/base-drafts/pull/1921">No =
octets</a> (by martinthomson) </li>
  =

  <li>#1916 <a href=3D"https://github.com/quicwg/base-drafts/pull/1916">Rel=
ax 1200B requirement for Initial ACKs/Retx</a> (by martinduke) </li>
  =

  <li>#1915 <a href=3D"https://github.com/quicwg/base-drafts/pull/1915">The=
re are *Two* control streams</a> (by LPardue) </li>
  =

  <li>#1914 <a href=3D"https://github.com/quicwg/base-drafts/pull/1914">Str=
eam description moved to section 2 of transport</a> (by LPardue) </li>
  =

  <li>#1912 <a href=3D"https://github.com/quicwg/base-drafts/pull/1912">Use=
 octets rather than bytes throughout</a> (by martinthomson) </li>
  =

  <li>#1911 <a href=3D"https://github.com/quicwg/base-drafts/pull/1911">Don=
&#x27;t amplify accidentally when closing</a> (by martinthomson) <span clas=
s=3D"label" style=3D"background-color: #fbca04; color: #">-transport</span>=
 </li>
  </ul>

  <p>7 pull requests received 30 new comments:</p>
  <ul>
  <li>#1901 <a href=3D"https://github.com/quicwg/base-drafts/pull/1901">Com=
patible version upgrade</a> (21 by kazuho, marten-seemann, mikkelfj, martin=
thomson, ianswett, RyanAtGoogle, dtikhonov) <span class=3D"label" style=3D"=
background-color: #fbca04; color: #000000">-transport</span> <span class=3D=
"label" style=3D"background-color: #1d76db; color: #ffffff">design</span> <=
/li>
  =

  <li>#1916 <a href=3D"https://github.com/quicwg/base-drafts/pull/1916">Rel=
ax 1200B requirement for Initial ACKs/Retx</a> (3 by martinthomson, mikkelf=
j) </li>
  =

  <li>#1922 <a href=3D"https://github.com/quicwg/base-drafts/pull/1922">Sto=
p reserving application error codes</a> (2 by martinthomson, mikkelfj) <spa=
n class=3D"label" style=3D"background-color: #fbca04; color: #000000">-http=
</span> <span class=3D"label" style=3D"background-color: #fbca04; color: #0=
00000">-transport</span> <span class=3D"label" style=3D"background-color: #=
1d76db; color: #ffffff">design</span> </li>
  =

  <li>#1895 <a href=3D"https://github.com/quicwg/base-drafts/pull/1895">Min=
or edits to amplification attack text</a> (1 by martinduke) </li>
  =

  <li>#1900 <a href=3D"https://github.com/quicwg/base-drafts/pull/1900">One=
 close frames</a> (1 by LPardue) <span class=3D"label" style=3D"background-=
color: #fbca04; color: #000000">-http</span> <span class=3D"label" style=3D=
"background-color: #fbca04; color: #000000">-tls</span> <span class=3D"labe=
l" style=3D"background-color: #fbca04; color: #000000">-transport</span> </=
li>
  =

  <li>#1903 <a href=3D"https://github.com/quicwg/base-drafts/pull/1903">Fix=
 type value for RETIRE_CONNECTION_ID frame</a> (1 by udippant) </li>
  =

  <li>#1819 <a href=3D"https://github.com/quicwg/base-drafts/pull/1819">Let=
 Endpoints Ignore invalid Initial Packets</a> (1 by martinthomson) </li>
  </ul>



<h2>Repositories tracked by this digest:</h2>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/quicwg/base-drafts">https://github.com/=
quicwg/base-drafts</a></li>
  </ul>
</body>
</html>

--===============6405665489797413784==--


From nobody Sun Oct 28 22:16:21 2018
Return-Path: <martin.thomson@gmail.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 10EA412F1A6 for <quic@ietfa.amsl.com>; Sun, 28 Oct 2018 22:16:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 ImEW1C0oe-Ud for <quic@ietfa.amsl.com>; Sun, 28 Oct 2018 22:16:18 -0700 (PDT)
Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) (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 2F55D128D0C for <quic@ietf.org>; Sun, 28 Oct 2018 22:16:18 -0700 (PDT)
Received: by mail-ot1-x335.google.com with SMTP id q25so6365351otn.12 for <quic@ietf.org>; Sun, 28 Oct 2018 22:16:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=wCB1B1FaNuW9K8XcGHICipdaJL7iV0nBXI0ryft2Vyo=; b=PjL6xfA/xaoelwbLcTJhdIbODM5s9xsxb0v27I/mxogP/MQCko1HBrR8wPYZsjskUO j5VmBn7Z1X1MlvNvyHZ1J4t8yJtcjtw3gsW8taQQp3JAtbI5nAlIxwISqUapP2Hy2pmh fmFnKNv7cUet6/OgCZjVGZrwXhV36u0ORqh17Mk1T22okFqePxpXb1fNQLmsTU0OZm1z opOpiBWgOD1R9Xrch6QQF6p7LZPe94N6HjwN2YuqEeXQqz9yUYayVFCbxn17aEFFN2Bg 1Tua6weFWIToznmTOftXh9QaCXq9NCn9RMvJ5SFU9o+hqFBJt+JGpiCOGzSfDQacUiiU l2VA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=wCB1B1FaNuW9K8XcGHICipdaJL7iV0nBXI0ryft2Vyo=; b=YRSlWsu5AAw8yqPJWPk2sDG9eHFpWpuCZmh9kmxwlggRcCIMfiOf0s8U0t0OFbDOuu 0wmfHuEHNxREbVJVxLDFwPsZFRHivdesPJ1katmAc9MaTej0PYJibFwsX1l8emhODQvm EbEa9vy2OPvkkWgUnZAAodfjSC/HgGXwSfbFeHfONBCiOymo97akt1u9fvBc5LS8WE4C en4NzpM2nf5tL8KJ3ouXhhpVQlhzgQqh8ADQBkFo+QiMQh2To1rLjy+vBB/rUZnE6092 Glhph5T4sc0mqscGGVogpoyizoEUCuLdi4ZsX9fEPR3aO3Qc/M0Bjl7awASeFdkiUgZW 6esA==
X-Gm-Message-State: AGRZ1gLGAQzcOipiLJrqJ4PfESP+tkdCO8Mxo/cnzHHq+QbLU8HKBsva 4W5ncVHthhQMah5bHy7tTA5yEt5nh/jD2sDeIcA=
X-Google-Smtp-Source: AJdET5fSNQXwmlgaUKBY4NyzKulFPh7rn2qUaqnpJ2Xh4BMUvTA188kHUzID5q+fP+AMIp0ga+x2FhuUqu6SryWXhXI=
X-Received: by 2002:a9d:7a48:: with SMTP id z8mr8573855otm.257.1540790177242;  Sun, 28 Oct 2018 22:16:17 -0700 (PDT)
MIME-Version: 1.0
From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 29 Oct 2018 16:16:07 +1100
Message-ID: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com>
Subject: flow control and DATAGRAM
To: Tommy Pauly <tpauly@apple.com>, QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/T8pnq8DVSlf6dyO3C4aPAO4zBKA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 05:16:20 -0000

Hi Tommy,

Your slides - <https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF103-QUIC-Datagram.pdf>
- say that DATAGRAM frames respect connection-level flow control.  I
missed that in the draft, and I don't know how they can do that in the
face of packet loss, especially when you don't necessarily retransmit
lost DATAGRAM frames.

For that to work, you would need a bunch more machinery to make the
connection-level flow control sync between endpoints in the case that
packets are lost.  A disagreement about how much flow control is used
causes things to break down badly.  Ian and I discussed this point at
the last meeting and quickly agreed that while it might be nice to
have flow control for this stuff, the increase in complexity is
considerable and (at the time) we thought it wouldn't be worth it.

The problem that introduces is that you could end up having too many
DATAGRAM frames arrive.  The receiver has to drop something at the
point that it can't handle them.  And we say that when you acknowledge
something, you processed it.  That's tricky.

It might be easier to say that a QUIC acknowledgment for a DATAGRAM
frame doesn't mean that it was received and processed by an
application.  An endpoint might discard these frames before passing
them on to applications if it doesn't have space.  In other words,
acknowledgment of DATAGRAM means that QUIC got it, not that the
application got it.  Sadly, that means that the QUIC acknowledgment
machinery doesn't help the application that uses DATAGRAM all that
much.  Also, the lower bound on reliability is 0, which isn't the best
thing ever.

Hard choices, I know.  I don't have a good design for maintaining
connection-level flow control (or any back pressure mechanism with
equivalent properties) that doesn't add both complexity and overhead.

Cheers,
Martin


From nobody Mon Oct 29 03:15:49 2018
Return-Path: <lists@digitaldissidents.org>
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 73815130DF4 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 03:15:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 NP1BQ-G5vRtA for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 03:15:42 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.89]) (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 553E8124BAA for <quic@ietf.org>; Mon, 29 Oct 2018 03:15:42 -0700 (PDT)
Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <lists@digitaldissidents.org>) id 1gH4aA-0002hT-O4; Mon, 29 Oct 2018 11:15:40 +0100
From: Niels ten Oever <lists@digitaldissidents.org>
Openpgp: preference=signencrypt
Autocrypt: addr=lists@digitaldissidents.org; prefer-encrypt=mutual; keydata= xsFNBFgpcR0BEACnfvNwTMlN+pyZT0AFYhWqxG3N4AoPIeNfbxLQH7dk8ZL7Ls05xtORfnu9 ovoaRrZpDufkMviUFidNYePbQNdgf63vWVgwpQR7utluwWraetcmZOu6tayJuyBK2b6d2Z23 MJAQxfa2/GMlN3QkvobaoyKtgbc8rOCgNla7WwkgtiVJ89xbAUHXPFpKWZluVRjaFh4p5C5r 7E5OvUiEGLQ5Cn2ir2PGIyIVqjB+hLTyaI6dIGCz2jtL0RATjmsmYUX7UkU/pz8MPPC2BJ5P KU9pdXMRBhAStxcph8vCo2ze9xSi3+1/5A2ULVtvO4s0hZ+exbTfMxMg3H5CCRFEEJXlQEXa Cd0ZHvqcv5xq8n9w/Ccd0CqYWATIwyP8Jlzd+BY3QGTWnWlgoAbs3Guh/pFYhEFNuuAF5Jk1 k5OlNGsRE/LQJmbT5SE7AtLJLbWewcHlEyIH+K6J8uVa4ExLXmRy+eRkFaxjGy3fLlUpy1Ee 1kU7VsQ/TZ8g8ujsMzxqsdB6y0TD/kVlWaDqPL6F+b+pm3lAuCBGWM1YZROTG58R6pD7sNVm i0ift4dIttAsg+2KoShm9A8kQ3tACXZDgNPC0l7VOqnVayjnF0RmjGeiX7PjOcLQCZ9a5wAH 5mrXMaKvfszqAVkP9HSrk1QVZOipF6vEimL43Czy7Rp1aUaUwwARAQABzShOaWVscyB0ZW4g T2V2ZXIgPG1haWxAbmllbHN0ZW5vZXZlci5uZXQ+wsGZBBMBCABDAhsjBQkJZgGABwsJCAcD AgEGFQgCCQoLBBYCAwECHgECF4AWIQQkWAtwXEr9ipSIZDoO2D86RorIswUCWyJaFgIZAQAK CRAO2D86RorIs8I2D/wNc4kT+dRC3Y9lSygeVWuxNj21z/QlbNvfXx9NicgBx4uCjsCm0ZhS 6qnp0uHYZYr8rdIzrL3GazyEuG9uvNzZBvIHm92UY1x0NH0TOVbGwJCWKULStvg9S+DjmNgp x8XM9amCtuXZyCiESeoOVRUanzD1JIidJtKgDfxvC63kqYoXl3azP0ra2nZbpktMm2fW5YdN D6kp6otjBH/jtpLay1CpVDS2Ehl3rLXJVUu96hlBnQB8q+64qyhTZ23HnbU+ib5Zb3OFgYoB KHjukJ4tV4x9rQprCQeirKX627vcNniDPnMp/nr9Qww6iVidX2vsG/22cx8MqLfs4B9tOVCJ Ft9D7MOwxOWgKnaYvrPZBOEmnuGq7btQe1tQZukL1Z83jKkV/e43k1gJaRt4Nl3/6YYCAlnn aQwRmySxznojsEl+X41UaJ6QFcoCphucOHoO9MeVzuNzgOgodXXEvlA8OJAqxRbE5AqB0leJ z1PfyrF1lsy8ETPRGKUKPBVed1vpZCQBfd/5RksOYBGhyfQ8p0w0hGs8SG6Xl6UtorJ+baLZ ZtnYbakfroxQBsF4bD/0P4fZ8wvTUDNLT8WN/9KFoTXrKn2pTLD+V9iw6nQAH4LSPw0G8XsL ce3Ihkf/2bvorGCUO7YXG4u6FPzEHsa/ZNfWHA5kbpGfwe2OVYNeI87BTQRYKXEdARAAxYOE 3/AFmEfQ0SVVFujYFhZKX+BGXolYytC2a1soZogVYTIIlypxkRtN+ljteFAY3xX/El7cx5Fx j+uXvLKAm9xQRI/DCug7/NGULMk9bDK5bzSGw817cyiL5Kb+0RkWj2Y5ArOAK6XPGBZWZTHw yIawsSCN9AhDXZQWVRqkR1QXcq3IYKl+OHWMO7+1VfixCSakNf7T/Kiq46rQEPW8Eghk6CVO BR8xUCBbyk5aRW4VSGO6pUD3H21ur+5fTLsVyan1NHhxNNiXfnEJKr+JI5dXSkj7WqA5n8IT aNdFSAttkdT56wAQpxE2h8zaOmBaFUWQ4D8SdXDVymP5QMtLG+ItMMiNV6kXgsRFugAKM5yZ tPP9gIX+ic8QO5iuct37bRXJU/rmrH54Ab0kyAeeRE7oSsfTZPKvgtUh7VLAUEw/wy6TORJH E8JMaX0yYT6h4PGRS3mNM4bka8hjdfcrexI0zSqFOl2I22zQlG3YqSzIvVh98W67hxfAIaCV aTfJLFPEru3drxNwi6ogdkRmcLGKqqTgeYItrvITyFvzqbrcO2exp0KKEK3cDIZypqHHUf4+ uPlDtuExehLsNOMpjP8qhZpFtyLeDS07qunbvstcyvR30wOJ3DyAbHGzq739UyDcO9Jt5jwO DyVwk3MK5Em4pJ0+IAJx+F6gta0Bk2MAEQEAAcLBZQQYAQgADwUCWClxHQIbDAUJCWYBgAAK CRAO2D86RorIs0ykD/4t151SZG9MbeKRVKbs9Ecjady9bO0L3oBos4rhqY12ha8smFlsUzvb gB4CtkBuXQlq+plOBWv+rFEThOzy3bezgEDjlxycoO1W2wJD6E7Fo9fkHT6UOm9fQBkuKRqK 83OGnfM02qP1Ky8d7EoZz+nTSMf/DJgWw1YRKrXkMHBwKD83lCENsmePWE5AjMqk8cojPv9O y1wWy6fHjwx3r+wQSokBNfxgQyAFonmgBbhlic/pZUYRSIcldyUlaomrjFfr4egzmNE7aWDv LwOUYKevBIeJJcqTyfAn3TtJbPCEHOC2+lP6EcmPFyhQdiia+RqOClumqbWOPeQ2VM8j7NWv KKmBNBB5OJ/rmHogbNU+wWPJ723qMBoOp1jIwFNkQhx01W6v55VMwLr+IuBKY1ggJ2BhwQiG pWv4tMc5oB/qVh3my1VO65ErcJ3S9blpwJdDj5/YDOU7BKEmpRUP+xkaryNzH2x7FzrOOHzJ BX6jeYZabGvnTicQlBAzfGpblFqV3YN6EhCF2AHmGLTZ/DrjGYToIsW8cXlEMqN4u8ODEUY0 OhbnytnopKJKk99bwMoCqDkfQvT3LKDWtZj9NzFndfuoKXsVpwAitrG0mau0/16DKDyVWdtJ 9DYmtE40zO6g70VVxUj+dKt2hbJTy/KQTb7Ijhw7wZrGp/P7nhbVyA==
To: quic@ietf.org
Cc: Beatrice Martini <mail@beatricemartini.it>
Subject: re: Human Rights Review of QUIC
Message-ID: <6de33b8c-840b-ed15-1c7b-e7f434c9bbc9@digitaldissidents.org>
Date: Mon, 29 Oct 2018 11:15:37 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Authenticated-As-Hash: 29cc722430e8f1f6ed904119444c0d49b0f3ee91
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Scan-Signature: 9aee46e6cd82d1321941e51280566951
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/NAfnOQefW3SnPoCHLHZKVtHROhg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 10:15:47 -0000

Hi all,

Thanks _a lot_ for the comments we received off-list! Several of you
asked for clarification on why the review was published as an I-D. So I
just wanted to state again that we are not seeking to make this an RFC,
but rather to have an easy way to share it. To also have it in the list
archives I pasted the markdown of the text below, with the references
underneath.

If you have specific comments, for instance on:
    - issues that are resolved in newer version of the drafts;
    - things that we should add to the issue tracker;
    - things that do not make sense;
please feel welcome to share them.

Happy to discuss on the list or in person in Bangkok.

Best,

Beatrice and Niels

Abstract
========

QUIC is a new transport protocol that provides low-latency communication
and security. QUIC’s key features include faster connection
establishment, stream-based multiplexing, improved loss recovery, and no
head-of-line blocking. This document assesses the potential human rights
implications emerging from the deployment of QUIC. The assessment is
done based on the methodology articulated in {{RFC8280}}.

Introduction
============

This is a review done within the framework of the Human Rights Review
Team, and it was conducted by Beatrice Martini and Niels ten Oever. The
Human Rights Review Team aims to implement and improve the guidelines
for human rights considerations provided in {{RFC8280}}, and seeks to
mitigate potentially adverse human rights impacts that IETF and IRTF
documents might have.

Human Rights Reviews are developed by a group of individuals in the IRTF
and IETF. They work collaboratively and provide their knowledge and
input to the assessments, in an effort to contribute to the IETF open
review process. Human Rights Reviews are individual contributions. The
authors hope that the comments will be taken into consideration by the
draft authors, Working Groups and the IESG.

This review concerns the QUIC protocol in general, and the following
drafts in particular:
draft-ietf-quic-transport-12, draft-ietf-quic-tls-12,
draft-ietf-quic-invariants-01.

Vocabulary Used
===============

Anonymity
: The condition of an identity being unknown or concealed {{RFC4949}}.

Censorship
: Technical mechanisms, including both blocking and filtering, that
state or private actors can use to block or degrade Internet traffic.
For further details on the various elements of Internet censorship, see
{{Halletal}}.

Censorship resistance
: Methods and measures to mitigate Internet censorship.

Confidentiality
: The property that data is not disclosed to system entities unless they
have been authorized to know the data {{RFC4949}}.

Connectivity
: The extent to which a device or network is able to reach other devices
or networks to exchange data. The Internet is the tool for providing
global connectivity {{RFC1958}}. Different types of connectivity are
further specified in {{RFC4084}}.

Content agnosticism
: Treating network traffic identically regardless of content.

Heterogeneity
: "The Internet is characterized by heterogeneity on many levels:
devices and nodes, router scheduling algorithms and queue management
mechanisms, routing protocols, levels of multiplexing, protocol versions
and implementations, underlying link layers (e.g., point-to-point,
multi-access links, wireless, FDDI, etc.), in the traffic mix and in the
levels of congestion at different times and places. Moreover, as the
Internet is composed of autonomous organizations and Internet service
providers, each with their own separate policy concerns, there is a
large heterogeneity of administrative domains and pricing structures."
{{FIArch}}

: As a result, per {{FIArch}}, the heterogeneity principle proposed in
{{RFC1958}} needs to be supported by design.

Human rights
: Principles and norms that are indivisible, interrelated, inalienable,
universal, and mutually reinforcing. Human rights have been codified in
national and international bodies of law. The Universal Declaration of
Human Rights {{UDHR}} is the most well-known document in the history of
human rights. The aspirations from {{UDHR}} were later codified into
treaties such as the International Covenant on Civil and Political
Rights {{ICCPR}} and the International Covenant on Economic, Social and
Cultural Rights {{ICESCR}}, after which signatory countries were
required to reflect them in their national bodies of law. It is also
broadly recognized that not only states, but also non-state actors must
respect human rights.

Integrity
: The property that data has not been changed, destroyed, or lost in an
unauthorized or accidental manner {{RFC4949}}.

Linkability
: Establishing the identity of a host across several IP addresses.

Open standards
: As stated in {{RFC2026}}: "Various national and international
standards bodies, such as ANSI, ISO, IEEE, and ITU-T, develop a variety
of protocol and service specifications that are similar to Technical
Specifications defined here. National and international groups also
publish "implementors' agreements" that are analogous to Applicability
Statements, capturing a body of implementation-specific detail concerned
with the practical application of their standards. All of these are
considered to be 'open external standards' for the purposes of the
Internet Standards Process."

Openness
: Absence of centralized points of control -- "a feature that is assumed
to make it easy for new users to join and new uses to unfold"
{{Ziewitzetal}}.

Ossification
: The increasing inflexibility of the network which results in the
inability to deploy a new protocol or protocol extensions due to the
unchangeable nature of infrastructure components that have come to rely
on particular features of current protocols.

Permissionless innovation
: The freedom and ability to freely create and deploy new protocols on
top of the communications constructs that currently exist.

Privacy
: The right of an entity (usually an individual), acting on its own
behalf, to determine the degree to which it will interact with its
environment, including the degree to which the entity is willing to
share its personal information with others {{RFC4949}}.

: The right of individuals to control or influence what information
related to them may be collected and stored, and by whom and to whom
that information may be disclosed.

: Privacy is a broad concept regarding the protection of individual or
group autonomy and the relation between an individual or group and
society, including government, companies, and private individuals. It
encompasses a wide range of rights, including protections from
intrusions into family and home life, control of sexual and reproductive
rights, and communications secrecy. It is commonly recognized as a core
right that underpins human dignity and other values such as freedom of
association and freedom of speech. The right to privacy is also
recognized in nearly every national constitution and in most
international human rights treaties. The right to privacy is also
legally protected at the national level through provisions in civil
and/or criminal codes.

Pseudonymity
: The ability to use a persistent identifier that is not immediately
linked to an individual's offline identity. Pseudonymity is an critical
feature for many end users, as it allows them different degrees of
disguised identity and privacy online. "Pseudonymity is strengthened
when less personal data can be linked to the pseudonym; when the same
pseudonym is used less often and across fewer contexts; and when
independently chosen pseudonyms are more frequently used for new actions
(making them, from an observer's or attacker's perspective,
unlinkable)." {{RFC6973}}

Review Methodology and Process
==============================

This section describes how the review was undertaken.

We started our review by examining the Internet Drafts which were active
on June 7, 2018 on the QUIC Working Group Datatracker
(https://datatracker.ietf.org/wg/quic/documents).

Inferential reading of the documents resulted in the decision to focus
our efforts on three specific drafts: draft-ietf-quic-transport-12,
draft-ietf-quic-tls-12, draft-ietf-quic-invariants-01.

>From the study of these documents through the perspective of the
Guidelines for Human Rights Protocol Considerations outlined in
{{RFC8280}}, we formulated a questionnaire, to be used as a tool to
guide semi-structured interviews with QUIC Working Group chairs and
document authors.

We engaged in a total of seven interviews, which took place during
IETF102 (July 14-20, 2018). These were then transcribed and analyzed.
The analysis focused on the identification of potential positive or
negative impacts on human rights, and on the categorization of our
findings according to the Guidelines for Human Rights Protocol
Considerations outlined in {{RFC8280}}.

One particular aspect that is critical to consider is the pace at which
the QUIC Working Group operates, which is regarded across the IETF
community as notably faster than usual. This means that while the
general design that is outlined in the QUIC Internet Drafts is fairly
stable, numerous details are in constant change. When it comes to
conducting an interview-based research, this also means that some of the
expressed points of view might be overtaken by intervening changes. To
address this specific characteristic of the work on the QUIC protocol,
we decided to set a time point to examine active Internet Drafts and
current Working Group discussions. The time point is June 7, 2018. In
addition to that, we also kept discussing with the interviewees,
reviewing notes from the following New York interim meeting (September
19-20), and following selected mailing list threads, until our final
review of this very document, on October 17, 2018.

The content examined until the set time point (June 7, 2018) is what
should be considered the core subject of our examination. However, as we
aim to helpfully contribute to the efforts of the QUIC Working Group, we
also decided to monitor potential updates and emerging discussions which
took place in the following months, with the aim to provide relevant and
applicable feedback.

Human Rights Considerations
===========================

The Human Rights Protocols Considerations Research Group (HRPC) welcomes
the drafts draft-ietf-quic-transport, draft-ietf-quic-tls,
draft-ietf-quic-invariants.

In particular, we welcome the efforts to improve connectivity on high
latency, low bandwidth and high loss connections, and the application of
encryption by default. Conclusions and recommendations can be found at
the end of this document.

No implications for Accessibility ({{RFC8280}}, sec. 6.2.11),
Localization ({{RFC8280}}, sec. 6.2.12), Decentralization ({{RFC8280}},
sec. 6.2.13), and Reliability ({{RFC8280}}, sec 6.2.14) have been found.

## Connectivity

Overall, QUIC is expected to result in a greatly improved Internet
service for users worldwide, and in particular for those who currently
do not have high bandwidth or lossless connections. Regions that
currently do not benefit from reliable connectivity, would be provided
with a significantly improved service. These advancements have positive
implications in regards to human rights such as freedom of expression,
freedom of association, right to political participation.

### Latency

QUIC was designed as a new transport protocol to provide connections
with lower latency than previous protocols.

One of the most important differences between TCP and QUIC connections
is that QUIC connection establishment takes 0 RTTs when a server is
known by a client and up to a few RTTs for the first connection to an
unknown server.

By allowing for Zero-Round Trip Time (0-RTT) resumption of connections,
QUIC performs better than TCP on high latency and high loss connections.
When a web client uses TCP and TLS, it requires two to three round trips
with a server to establish a secure connection before the browser can
send a request. With QUIC, if a client has communicated with a server
before (within a specific time period), it can start sending data
without any round trips, so that web pages will load faster.

An example of QUIC’s performance can be observed on a well-optimized
site like Google Search, where connections are often pre-established,
and QUIC’s faster connections can only speed up some requests. Still,
QUIC improves mean page load time by 8% globally, and up to 13% in
regions where latency is higher. {{Behretal}}

### Congestion Control and Loss Recovery

QUIC’s congestion control is based on TCP NewReno {{RFC6582}}, a
congestion window based congestion control. The signals QUIC provides
for congestion control are generic and are designed to support different
algorithms. In this way, QUIC can be configured to fit best in different
contexts.

Compared to TCP, QUIC offers more detailed feedback information for loss
detection.
For example, it uses a monotonically increasing packet number and does
not retransmit on the packet-level but on the content-level. This allows
QUIC to distinguish retransmissions from the originally sent packets,
avoiding retransmission ambiguities.

Overall, comparing it to previously existing protocols, QUIC implements
better estimation of connection RTTs and detects and recovers from loss
more efficiently.

### Reduced Head-Of-Line Blocking

HTTP/2 allows multiple objects to be fetched over the same connection,
using multiple streams within a single flow.

In TCP, if a loss occurs in one stream, all streams stall while waiting
for packet recovery. Differently, QUIC allows other streams to continue
to exchange packets even if one stream is blocked due to a missing
packet {{MolaviKakhkietal}}.

### Resources

QUIC is relatively expensive to implement, both in terms of code (size
and complexity) and processing (including memory overheads). This can
represent a barrier to adoption and the benefits that come with that.

## Privacy

### Encryption

QUIC incorporates the key negotiation features of TLS 1.3, requiring all
connections to be encrypted.

Encryption improves the security and privacy of user data. It is built
into QUIC, using AEAD algorithms such as AES-GCM and ChaCha20 for both
privacy and integrity. QUIC authenticates the parts of its headers that
it does not encrypt, so attackers cannot modify any part of a message
{{Behretal}}.

Furthermore, in addition to improving privacy, encryption helps to
address the ossification of network protocols caused by middleboxes that
assume certain information to be present in the clear {{Kuehlewindetal}}.

### Transparent Proxying

Many cellular and high-latency networks use transparent TCP proxies to
reduce end-to-end delays and improve loss recovery. However, by
encrypting the transport headers, QUIC prevents transparent proxying,
thus protecting their integrity {{MolaviKakhkietal}}.

### Multiple Streams

By establishing connection with multiple streams, QUIC creates higher
opacity for the observer.

Comparing QUIC to TLS over TCP, QUIC significantly reduces the amount of
information that an observer can acquire about communications they are
looking at.

In TCP, all of the information regarding the protocol flow at a
transport layer is exposed, and can be used to identify active
communications.

In QUIC, it is possible to have an established connection with an end
point and to run multiple streams over that connection. Consequently, an
observer who is looking at someone's connection, would not be able to
tell the difference between the streams.

### Packet Number Encryption

In QUIC packet numbers are encrypted.

>From a general standpoint, the number assigned to each packet carries
very little information. For example, it is possible to observe that a
packet sent a certain time and the packet that was sent immediately
after probably have increasing packet numbers.

But when traffic is carried over multiple paths, it becomes observable
at many points, and this has privacy implications. For example, as
stated in {{draft-huitema-quic-mpath-req-01}}: "[...] if packets
belonging to a given connection carry some unique identifiers, observers
could use these identifiers to track client migrations through several
paths, and thus potentially expose the successive locations of a
particular user."

### Padding

Bit padding is the addition of one or more extra bits to a transmission
or storage unit to make it conform to a standard size.

QUIC (like HTTP/2 and TLS) offers a padding mechanism that can be used
as a defense against traffic analysis for protected packets. It is
important to note that its use is discretionary by implementations.

### Lawful Intercept

The lawful intercept of content in QUIC works similarly to TLS over TCP.
An intercept can: force the acceptance of an alternate certificate;
cooperate with or coerce the non-monitored endpoints to obtain session
keys for decryption of traffic; exploit endpoint vulnerabilities to
place monitoring devices directly on the endpoint on the other side of
the crypto boundary.

Forcing TLS 1.3 avoids some common exploit vectors in TLS 1.2 and
strengthens the ciphersuites.

### Spin Bit

When Google offered the IETF the opportunity to take the work on QUIC
and produce an open standard that could be used by all {{Wilketal}}, it
sparked off a debate within the IETF as to how much transport
information should be deliberately kept unknown to the network.

As an explicit design goal, QUIC provides far less information about its
operation to devices on path than TCP does. In TCP, the sequence and
acknowledgement numbers and timestamps (if the respective option is in
use) can be seen by on-path observers, and used to estimate end-to-end
latency.

Differently from previous transport protocols, QUIC splits the
information it uses for its own operation from its wire image. As a
consequence, QUIC's wire image currently does not expose any information
that can be used for passive latency measurement techniques
{{draft-ietf-quic-spin-exp-00}}.

At the June 2017 interim meeting of the QUIC Working Group, a proposal
was made to add a latency spin bit to QUIC's wire image, in order to
allow for passive measurability of RTT equivalent to TCP {{Trammell01}}.

The spin bit is an explicit signal for passive measurability of
round-trip time. It causes one bit in the header to ‘spin’, generating
one edge (a transition from 0 to 1 or from 1 to 0) once per end-to-end RTT.

During the following months, the proposal to add this facility to the
QUIC protocol has been further discussed and researched. At IETF101 the
Working Group agreed upon the reservation of three bits for
experimentation with passive RTT measurement, with the result of this
experimentation to inform an eventual working group decision whether to
include the bit in the shipping version 1 of the protocol, scheduled to
be complete by November 2018. {{Trammell02}}

>From its designers' perspective, the spin bit was formulated to be a
minimal-risk, maximum-utility signal fit for a single purpose: on-path
measurement of end-to-end RTT, to generate RTT samples for a variety of
passive latency measurement tasks.

The key argument in favor of the spin bit originates from the notion
that measurement is fundamental to the operation of networks and
at-scale services, whether for management, security, optimization, and
that if it is at all possible to safely design passive measurability of
any metric explicitly into a protocol, this signal represents how to do
it. {{Trammell01}}

The argument made by those who are not in favor of the addition of the
spin bit to the protocol, is that the exposure of any information beyond
the IP header and the base essentials of a UDP header is not necessary
and not safe. They point out that how this bit may be used, were it to
be added to the protocol, is unknown.

This could represent an infringement of the user privacy. Furthermore,
an exposed bit might cause for ossification of the bit itself, which
would, to some extent, defeat QUIC’s efforts to elude the intrusive and
ossifying grip of network middleware. {{Huston}}

### Packet Injection

It is viable for network operators to add data to packets in order to do
traffic monitoring and/or management.
It is not uncommon for network operators to routinely tag packets as
they enter the network for their own purposes, and simply erase the tag
when they leave the network. Packet modification or injection cannot be
prevented in QUIC. However, the protocol takes steps to ensure that its
own state is not affected by this kind of activity.

## Content Agnosticism

The QUIC protocol itself is content agnostic. While it is currently
being optimized for HTTP traffic, it can also be used with other
application layer protocols (e.g. see {{draft-huitema-quic-dnsoquic-05}}).

## Security

QUIC improves security by making encryption an inherent part of the
transport protocol, instead of adding it as a optional layer on top of
it. This protects the integrity of the data by preventing tampering on
the path, and ensures end-to-end confidentiality between the two
communicating hosts. Furthermore, it ensure that no on-path party can
emulate an endpoint.

By encrypting all Internet traffic by default it is harder for
researchers and network operators to analyze network traffic. This is a
specific design goal, but it also makes research into the promulgation
of malware, cookies and other artefacts much harder, since in this case
access to the stream needs to be provided by the end point.

## Internationalization

{{draft-ietf-quic-transport-12}} does not define human readable strings,
except for where it states that the Reason Phrase in the
CONNECTION_CLOSE and APPLICATION_CLOSE frames "SHOULD be a UTF-8 encoded
string {{RFC3629}}". The QUIC protocol demands that this SHOULD be an
UTF-8 string, while UTF-8 is actually not required. Also, there is
currently no space to declare the charset used. So it is recommended
that this SHOULD becomes a MUST.

{{draft-ietf-quic-transport-12}} does not allow for the use of language
tags. If it would request these tags, it would allow implementations to
signal in which language Reason Phrases are rendered.

## Censorship Resistance

Encryption makes monitoring and filtering of the traffic more complex,
thus hindering fine-grained censorship.

Furthermore, in QUIC it is also harder to terminate connections, since
in the protocol the only parties that can terminate the connection are
those actually involved in the connection once it exists. This means
that a middlebox cannot reset a connection, but needs to continue to
block it, keeping state. Considering this, it can be stated that QUIC
makes censorship harder because it requires the censor to invest more
resources and efforts.

QUIC is also improving the protection against DDoS through observation
of the handshake for connection confirmation, and through the need to
validate new connections in case of a connection migration.

It is worth noting that it is almost impossible to make the handshake
resilient to injection attacks, and the general consensus has been not
to spend cycles trying. This means that handshakes can easily be
disrupted by a censor. Post-handshake, QUIC is very resilient to
attempts to reset the connection by a third party.

## Open Standards

QUIC is published as open standard.

## Heterogeneity Support

The design of the QUIC transport protocol is currently specifically
tailored to be used with TLS1.3 and HTTP2. It is explicitly constructed
in a modular manner and is designed to support other application layer
protocols in the future as well.

## Anonymity

Persistent static identifiers, consistently linking to a particular
person or small, well-defined group of people, are one of the main
threats to anonymity. This is especially concerning when the identifier
is used in repeatedly used in multiple contexts, thus raising an issue
of linkability.

In QUIC, linkability would occur in case a connection ID was used on
multiple network paths. In order to provide some protection against
linkability in case of connection migration, QUIC uses different
connection IDs when different local addresses are used. Furthermore,
packet numbers are encrypted to ensure they are not used to establish a
link between different connection IDs.

However, it is important to note that traffic analysis might still allow
to correlate different streams.

## Pseudonymity

Keeping different identities isolated from each other is critical to
protect and preserve pseudonymity. QUIC contributes to this by using
different connections IDs for different local addresses.

## Confidentiality

Through the use of cryptography, QUIC integrates security,
confidentiality, authenticity, and integrity directly into the transport
protocol rather than having them layered on top of it. Any server that
offers QUIC to benefit from its latency improvements will automatically
provide all the aforementioned attributes to their user.

## Integrity

The use of TLS1.3 in QUIC makes on-path attacks either visible or nearly
impossible to carry out. So, if an actor forces the traffic to go
through one middlebox and decrypt the traffic itself, their action is
made detectable.
This also protects the integrity of the datastream, prevents tampering,
and averts the injection of extra data in the stream.

## Authenticity

Except for the initial handshake, the encryption in QUIC is provided by
TLS1.3, which uses asymmetric cryptography to authenticate the hosts.
This enables verification of authenticity.

## Adaptability

QUIC has a modular approach, and is designed for adaptation. The only
commitments in the protocol are the requirement to run on UDP, the
packet header, and the version negotiation phase. The remainder of the
protocol is quite flexible and can be further adapted.

By preventing the ossification of the protocol by middleboxes through
the encryption of transport headers, QUIC enhances the adaptability of
the architecture.

As a transport protocol, QUIC tries to be agnostic for application layer
protocols, even though it is currently tailored to work with HTTP/2.

## Outcome Transparency

Outcome transparency concerns the intelligibility of the effects of a
protocol in relation to its users, protocol developers, and
implementers, and its potential consequences (e.g. lack of authenticity
may lead to lack of integrity and negative externalities){{RFC8280}}.

QUIC represents a remarkable evolution of the transport layer with
significant impact on the Internet architecture and, most importantly,
the service provided to users.

### Encryption

The IETF has reached consensus on the fact that pervasive monitoring is
an attack (see {{RFC7258}}), and that a response to mitigate this is
represented by ubiquitous encryption, which would also reinforce the
end-to-end nature of the network {{RFC2775}} {{RFC3724}} {{RFC7754}}.

With the advent of QUIC, encryption becomes the default on the transport
level. This has a critical impact on the protection of user privacy.

Furthermore, it has implications concerning network operators that had
previously used visible parts of protocols to, among other things,
manage, operate, and secure their networks {{RFC8404}}.

Encryption also improves the integrity of the datastream, as QUIC allows
to protect users against injections of ads by network operators.

### Permissionless Innovation and Its Challenges

As suggested by interviewees during the research phase of this review,
and to acquire a more contextualized understanding of protocol
development efforts over time, it is relevant to pay attention to the
history of SCTP (Stream Control Transmission Protocol). SCTP is a
protocol for transmitting multiple streams of data at the same time
between two end points that have established a connection in a network,
standardized in {{RFC4960}}.

As outlined in the comparison between SCTP and QUIC presented in
{{draft-joseph-quic-comparison-quic-sctp-00}}, the deployment of SCTP is
not particularly widespread. In-network devices, like NAT gateways for
example, do not support SCTP well. NAT gateways need to be upgraded to
be SCTP-aware, the modification of middleboxes is very expensive, and
Internet service providers, focusing on the sustainability of their
business, update the devices in accordance with the benefit that this
can represent for their revenues.

Furthermore, an early version of QUIC (now popularly called gQUIC) was
initially designed and deployed by a large content provider, Google. It
was implemented in 2012, and the company invested significant resources
to develop it, for example conducting thorough A/B-testing in order to
assess how the protocol would interact with the network, and how the
middleboxes would respond. QUIC is now widely used in Chrome clients
accessing Google services.

In 2015, an Internet Draft of a specification for QUIC was submitted to
the IETF for standardization, and the following year the QUIC Working
Group was established. A growing number of contributors from the
corporate, academic, nonprofit sector have joined the protocol
development work since, and what has been achieved to date is the result
of a notable and labor-intensive collaborative effort.

So, on one hand, the history of QUIC shows that permissionless
innovation is still possible. On the other hand, it also shows what
remarkable efforts and resources are needed to carry out such an
ambitious project.
While permissionless innovation still exists, the threshold and costs
for innovation seem to rise significantly and increasingly.

Also, a look at the actors and dynamics involved in QUIC’s history
should not underestimate the power of Google’s authority. A different
developing actor might have been able to invest a similar amount of
resources into the development of a protocol. Still, without an
impressive user base and traffic stream as Google's, they might have
received a less supportive response from network operators.

Having said that, it is expected that QUIC will improve the current
situation by providing a more capable transport which aims to overcome
ossification and allow for changes in the protocol due to its modularity.

### Privacy, Power and Consolidation

The most relevant privacy advantage provided by QUIC is gained by users
who have different kinds of traffic relations with one end point. In
fact, QUIC does not allow network providers to easily differentiate
between, for instance, HTTP requests, DNS requests and real time voice
packets, thus strengthening user privacy, and also improving
performance. It is important to note, though, that QUIC does not
actually hide or attempt to hide the application protocol being used on
a connection. The ALPN offered by the client is protected only by a key
which can be calculated by any party who can work with the QUIC version
in use.

On the other hand, this creates a concentration of different kinds of
traffic with one end point, thus giving the service provider access to
more categories of privacy sensitive information.

In the current reality of the Internet, the biggest hosts are controlled
by large, consolidated, transnational corporations. This creates an
extreme power differential between end users on the one hand, and
service providers and content operators on the other hand.

In order to protect privacy and secure information, it is important that
the user makes a careful and informed decision about the hosting
provider and plan they choose.

While ubiquitous encryption changes the relation between service
providers and content operators, placing them at the same end of the
spectrum, it remains to be seen whether if it can help users take and
retain control within the overall power structures of Internet
governance and economics.

One of the problems with deploying fully encrypted protocols like QUIC
is that deployment is far easier for organizations that already have
integrated observability, traceability, and tooling in their back-ends,
which not surprisingly happen to be the big players.

If there was any chance to make running a QUIC server relatively easy,
thus enabling a greater diversification of end points, QUIC could
contribute to a power shift in favor of the end user.

However, running a QUIC infrastructure is currently expected to be more
demanding than running a HTTP/2 or HTTP/1 infrastructure. It would be
truly compelling if this consideration could be discussed further, and
ideally addressed by the development and release of openly available
tooling allowing for more accessible ways to run a QUIC server.

### Transparency and IoT

End-to-end encryption on the transport layer makes monitoring and
filtering of the traffic more complex, and can lead to the adoption of
other network management practices to obtain this information.

This has implications on the management of Internet of Things (IoT)
devices. If an IoT device adopts QUIC, it will be harder for the user
who owns the device to monitor what data is communicated with third
parties. It would also be more difficult to conduct research into the
promulgation of malware, cookies and other artefacts.

Adequate tooling to protect the right to privacy of IoT users has not
yet been developed.


Conclusions and Recommendations
===============================

The QUIC protocol provides significant human rights improvements for end
users.

It dramatically improves connectivity for users on high-loss,
high-latency connections. Users will benefit from lower latencies and
will not need to restart sessions as often. And in those cases in which
they will need to restart a session, they will able to do so without
having to re-do the initial handshake.

Another key improvement is represented by the use of encryption by
default, which provides authentication, stream integrity, adaptability
of the protocol by overcoming ossification, and improved protection from
third party monitoring and metadata analysis.

The following is a list of potential improvements that we invite the
QUIC Working group to take into consideration, wishing for the protocol
to have even greater positive implications for human rights.

* As the QUIC Working Group is expected to deliberate on the potential
inclusion of the spin bit in the main specification of the protocol at
the upcoming IETF103 (November 3-9, 2018), we suggest to consider not to
include it. Our recommendation is motivated by the concerns raised in
regards to its implications on user privacy, as reported in this very
document, and also shared by some of the interviewees.

* Consider deploying IP header encryption as an optional extension.

* Evaluate the addition of language tagging and charset identification
in the case of Reason Phrase in the CONNECTION_CLOSE and APPLICATION_CLOSE.

* Examine the opportunity to translate the QUIC specification into other
languages.

* Discuss the viability to make tooling for running QUIC servers openly
available.

* Observe and iteratively assess the implications of QUIC on the power
relations between end user on one end of the spectrum, and network
operators and service providers on the other one.

Acknowledgements
================

The authors thank (in alphabetical order) Mike Bishop, Janardhan
Iyengar, Daniel Kahn Gillmor, Mirja Kuehlewind, Mark Nottingham, Martin
Thomson, and Brian Trammell for their generous contribution to our
research and review. This document does not necessarily reflect their
opinion, but solely that of the authors.

References
==========

   Ziewitzetal:
     title: "A Prehistory of Internet Governance"
     author:
        - ins: M. Ziewitz
        - ins: I. Brown
     seriesinfo: "Research Handbook on Governance of the Internet, ed I.
Brown, 3-26. Cheltenham: Edward Elgar"
     date: 2013

   UDHR:
     title: The Universal Declaration of Human Rights
     author:
        - org: United Nations General Assembly
     date: 1948 December 10
     target: http://www.un.org/en/documents/udhr/

   ICESCR:
     title: International Covenant on Economic, Social and Cultural Rights
     author:
        - org: United Nations General Assembly
     date: 1966 December 16
     target: http://www.ohchr.org/EN/ProfessionalInterest/Pages/CESCR.aspx

   ICCPR:
     title: International Covenant on Civil and Political Rights
     author:
        org: United Nations General Assembly
     date: 1966 December 16
     target: http://www.ohchr.org/EN/ProfessionalInterest/Pages/CCPR.aspx

   draft-huitema-quic-dnsoquic-05:
     title: Specification of DNS over Dedicated QUIC Connections (work
in progress)
     author:
        - ins: C. Huitema
        - ins: M. Shore
        - ins: A. Mankin
        - ins: S. Dickinson
        - ins: J. Iyengar
     date: 2018, June 29
     target: https://tools.ietf.org/html/draft-huitema-quic-dnsoquic-05

   draft-ietf-quic-transport-12:
     title: "QUIC: A UDP-Based Multiplexed and Secure Transport (work in
progress)"
     author:
        - ins: J. Iyengar
        - ins: M. Thomson
     date: 2018, May 22
     target: https://tools.ietf.org/html/draft-ietf-quic-transport-12

   draft-ietf-quic-tls-12:
     title: "Using Transport Layer Security (TLS) to Secure QUIC (work
in progress)"
     author:
        - ins: M. Thomson
        - ins: S. Turner
     date: 2018, May 22
     target: https://tools.ietf.org/html/draft-ietf-quic-tls-12

   draft-ietf-quic-invariants-01:
     title: "Version-Independent Properties of QUIC (work in progress)"
     author:
        - ins: M. Thomson
     date: 2018, March 20
     target: https://tools.ietf.org/html/draft-ietf-quic-invariants-01

   draft-huitema-quic-mpath-req-01:
     title: QUIC Multipath Requirements (work in progress)
     author:
        - ins: C. Huitema
     date: 2018, January 7
     target: https://tools.ietf.org/html/draft-huitema-quic-mpath-req-01

   draft-joseph-quic-comparison-quic-sctp-00:
     title: A Comparison Between SCTP and QUIC (work in progress)
     author:
        - ins: A. Joseph
        - ins: T. Li
        - ins: Z. He
        - ins: Y. Cui
        - ins: L. Zhang
     date: 2018, March 5
     target:
https://tools.ietf.org/html/draft-joseph-quic-comparison-quic-sctp-00

   FIArch:
     title: Future Internet Design Principles
     date: 2012, January
     author:
        - org: Future Internet Architecture (FIArch) Group
     target:
https://pdfs.semanticscholar.org/0f33/5e6df68193367b0d0ea5430c043919477508.pdf

   draft-ietf-quic-spin-exp-00:
     title: The QUIC Latency Spin Bit (work in progress)
     author:
        - ins: B. Trammell
        - ins: M. Kuehlewind
     date: 2018, April 26
     target: https://tools.ietf.org/html/draft-ietf-quic-spin-exp-00

   Halletal:
     title: A Survey of Worldwide Censorship Techniques (work in progress)
     author:
        - ins: J. Hall
        - ins: M. Aaron
        - ins: B. Jones
     date: 2015, April 28
     target: https://tools.ietf.org/html/draft-hall-censorship-tech-01

   Behretal:
      title: Introducing QUIC Support for HTTPS Load Balancing
      author:
         - ins: M. Behr
         - ins: I. Swett
      date: 2018, June 13
      target:
https://cloudplatform.googleblog.com/2018/06/Introducing-QUIC-support-for-HTTPS-load-balancing.html

   Kuehlewindetal:
      title: "A Path Layer for the Internet: Enabling Network Operations
on Encrypted Protocols"
      author:
         - ins: M. Kuehlewind
         - ins: T. Buehler
         - ins: B.Trammell
         - ins: S. Neuhaus
         - ins: R. Muentener
         - ins: G. Fairhurst
      seriesinfo:  IEEE International Conference on Network and Service
Management (CNSM)
      date: 2017, November
      target: https://nsg.ee.ethz.ch/fileadmin/user_upload/CNSM_2017.pdf

   MolaviKakhkietal:
      title: Taking a Long Look at QUIC
      author:
         - ins: A. Molavi Kakhki
         - ins: S. Jero
         - ins: D. Choffnes
         - ins: C. Nita-Rotaru
         - ins: A. Mislove
      seriesinfo: Proceedings of IMC ’17, London, United Kingdom
      date: 2017, November
      target: https://david.choffnes.com/pubs/long-look-at-quic-imc17.pdf

   Wilketal:
      title: A QUIC Update on Google’s Experimental Transport
      author:
         - ins: A. Wilk
         - ins: R.Hamilton
         - ins: I. Swett
      date: 2015, April 17
      target:
https://blog.chromium.org/2015/04/a-quic-update-on-googles-experimental.html

   Trammell01:
      title: Explicit Passive Measurability and the QUIC Spin Bit
      author:
         - ins: B. Trammell
      date: 2018, May 11
      seriesinfo: APNIC
      target:
https://blog.apnic.net/2018/05/11/explicit-passive-measurability-and-the-quic-spin-bit/

   Trammell02:
      title: And Yet, It Spins
      author:
         - ins: B. Trammell
      date: 2018, March 29
      target: https://trammell.ch/post/2018-03-29-and-yet-it-spins

   Huston:
      title: Just One QUIC Bit
      author:
         - ins: G. Huston
      seriesinfo: APNIC
      date: 2018, March 28
      target: https://blog.apnic.net/2018/03/28/just-one-quic-bit/

   Cuietal:
      title: "Innovating Transport with QUIC: Design Approaches and
Research Challenges"
      author:
         - ins: Y. Cui
         - ins: T. Li
         - ins: C. Liu
         - ins: X. Wang
         - ins: M. Kuehlewind
      seriesinfo: IEEE Internet Computing, Vol 21(2), pp. 72-76
      date: 2017, March-April
      target: https://mami-project.eu/wp-content/uploads/2017/03/QUIC.pdf

   Gratzer:
      title: “QUIC - Quick UDP Internet Connections”
      author:
         - ins: F. Gratzer
      seriesinfo: Seminar Innovative Internet-Technologien und
Mobilkommunikation SS2016
      date: 2016
      target:
https://www.net.in.tum.de/fileadmin/TUM/NET/NET-2016-09-1/NET-2016-09-1_06.pdf



    From: Beatrice Martini <mail at beatricemartini.it>
    To: quic at ietf.org
    Cc: Niels ten Oever <mail at nielstenoever.net>
    Date: Mon, 22 Oct 2018 19:02:58 +0200
    List-id: Main mailing list of the IETF QUIC working group
<quic.ietf.org>

-- 
Niels ten Oever
Researcher and PhD Candidate
Datactive Research Group
University of Amsterdam

PGP fingerprint	   2458 0B70 5C4A FD8A 9488
                   643A 0ED8 3F3A 468A C8B3


From nobody Mon Oct 29 04:14:06 2018
Return-Path: <martenseemann@gmail.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 B86FB130E91 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 04:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-0.001] 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 zIShRZvl5rWD for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 04:14:03 -0700 (PDT)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 DA22E130E90 for <quic@ietf.org>; Mon, 29 Oct 2018 04:14:02 -0700 (PDT)
Received: by mail-io1-xd2b.google.com with SMTP id f12-v6so1414710iog.0 for <quic@ietf.org>; Mon, 29 Oct 2018 04:14:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=equF8Qf/AYwL3Q8ORL7TYqDvaqOdloj+QdAPqX3IFec=; b=l+1y3rjtyi54AOVyNGuN1S7CWoWCGYdNZtUJpH60urW15djnrqBL0cCkV3zpayX8hT GgguNec2K3Pd/Ri/kJftw52aBXS8IiYtgsHZDt7LVymZHEtF8oiSdOS7TBwN0YbYCnP+ +twv6oE9zzhZZWWsft53i2L07HBIVOOi99oojRXNlgdbnUBEKFXA/kOZaRDNLdjBn1hg Aa0EDrtRciAFSQVnHgFaPDSAWYEbN+Kd1jZMuM8CfWH16jCanrDmyqaHx85CWr9Kn4cV C0X8fjYYMAszchsxTaqeIsrh3wILPaSApkzzhmm0aW9rrafdBFGNNscF7M6H2MJGMUk7 TreA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=equF8Qf/AYwL3Q8ORL7TYqDvaqOdloj+QdAPqX3IFec=; b=aoeLp4aQgHyJs0CwBlTYEO+3InoC6YoyfpmwpUgSXIx9vwU+bZVeS+8O1KkX1y1zeG mJRc6ZOq73SsFX/mJfm3asXJJ3co4rt0pjRyBz/xDvKfFZl/K/TSAdVOmJ2HENwsJRgW uM06AUbJ2Rn3ctxIdtEK4thiPZjcC8NwNdi5ldDt92/KulqJy4eZ3H055+d53GyAET78 7hOVrBeltFeP/krlLi+S+u9e7r4MpJXyowXhc+moIkZ5uUWp6CLkxuEKhAWa9C3EEAlC 9FeAcoTPOM5DdOKKr+BtSYqzv6mCWZSYixp/+UeXzLvEkK3jEaS2liOl9u297g3pUzni czPQ==
X-Gm-Message-State: AGRZ1gKYzBvVuH1VpCrAuJcD9TWVm36PmMTAT5Kh2SmaKPi5mXC+tGG7 uHJomfoF/r2JFeS0ZccBUWivps4x55Wq1JP+ngnNPA==
X-Google-Smtp-Source: AJdET5frR94TiD8hoVk5RiwM2tp6cLxPa1gK7AT947hKtlRKgrURyohjJdDrNEiexu+KFPCohRcE2ScG+XyJLLuAG/c=
X-Received: by 2002:a5e:8e44:: with SMTP id r4-v6mr8343163ioo.100.1540811641652;  Mon, 29 Oct 2018 04:14:01 -0700 (PDT)
MIME-Version: 1.0
From: Marten Seemann <martenseemann@gmail.com>
Date: Mon, 29 Oct 2018 18:13:50 +0700
Message-ID: <CAOYVs2rKJMXO806Jp5CpCkH8T80zUHUAauUqdmwEQuTJUhPxnA@mail.gmail.com>
Subject: Using varints to encode the Transport Parameters
To: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000910b3d05795c2a32"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/KMSoDdUGs-R7P_GfcBJTxvJARiw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 11:14:05 -0000

--000000000000910b3d05795c2a32
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

This is based on issue https://github.com/quicwg/base-drafts/issues/1608.

The proposal is to change the encoding of the QUIC Transport Parameters
exchanged during the handshake, in order to achieve greater consistency
with how QUIC encodes values, and also to save a few bytes.

We have a few things that are called transport parameters. This proposal
only applies to the TransportParameter struct as defined in section 18 as:
*struct {*
*      TransportParameterId parameter;*
*      opaque value<0..2^16-1>;*
*} TransportParameter;*
According to the encoding defined by the TLS spec, every key-value pair
will be serialized as:
TransportParameterID (2 byte), length (2 byte), value (length byte)
where the length of the value is specified for each TransportParameterID.

We could switch to varint encoding, as follows:

1. for the TransportParameterID: Since we=E2=80=99re only using the code po=
ints 0
to 13, we could save one byte per ID by using a varint.
2. for the length: We would save one more byte, as long as the length of
the value is less than 16 byte (which will be the case for all values
except the preferred_address).
3. For numeric values: This would apply to the flow control offsets, the
maximum stream IDs, the ack delay exponent , the maximum packet size and
the max_ack_delay.

In addition to the byte-savings of 1. and 2., 3. has some more desirable
properties:
    1. It would allow us to encode the whole range of permitted values. For
example, initial_max_data is a 62-bit value, but the current encoding just
allows to send 4 bytes.
    2. Depending on the value sent, this might or might not save a byte
here and there.
    3. We=E2=80=99d be consistent with the encoding we use everywhere else.

--000000000000910b3d05795c2a32
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>This is based on issue <a href=3D"https://github.com/=
quicwg/base-drafts/issues/1608" target=3D"_blank">https://github.com/quicwg=
/base-drafts/issues/1608</a>.</div><div><br></div><div>The proposal is to c=
hange the encoding of the QUIC Transport Parameters exchanged during the ha=
ndshake, in order to achieve greater consistency with how QUIC encodes valu=
es, and also to save a few bytes.</div><div><br></div><div>We have a few th=
ings that are called transport parameters. This proposal only applies to th=
e TransportParameter struct as defined in section 18 as:</div><div><i>struc=
t {</i></div><div><i>=C2=A0 =C2=A0 =C2=A0 TransportParameterId parameter;</=
i></div><div><i>=C2=A0 =C2=A0 =C2=A0 opaque value&lt;0..2^16-1&gt;;</i></di=
v><div><i>} TransportParameter;</i></div><div>According to the encoding def=
ined by the TLS spec, every key-value pair will be serialized as:</div><div=
>TransportParameterID (2 byte), length (2 byte), value (length byte)</div><=
div>where the length of the value is specified for each TransportParameterI=
D.</div><div><br></div><div>We could switch to varint encoding, as follows:=
</div><div><br></div><div>1. for the TransportParameterID: Since we=E2=80=
=99re only using the code points 0 to 13, we could save one byte per ID by =
using a varint.</div><div>2. for the length: We would save one more byte, a=
s long as the length of the value is less than 16 byte (which will be the c=
ase for all values except the preferred_address).</div><div>3. For numeric =
values: This would apply to the flow control offsets, the maximum stream ID=
s, the ack delay exponent , the maximum packet size and the max_ack_delay.=
=C2=A0</div><div><br></div><div>In addition to the byte-savings of 1. and 2=
., 3. has some more desirable properties:</div><div>=C2=A0 =C2=A0 1. It wou=
ld allow us to encode the whole range of permitted values. For example, ini=
tial_max_data is a 62-bit value, but the current encoding just allows to se=
nd 4 bytes.</div><div>=C2=A0 =C2=A0 2. Depending on the value sent, this mi=
ght or might not save a byte here and there.</div><div>=C2=A0 =C2=A0 3. We=
=E2=80=99d be consistent with the encoding we use everywhere else.</div></d=
iv>

--000000000000910b3d05795c2a32--


From nobody Mon Oct 29 05:32:41 2018
Return-Path: <ianswett@google.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 92A7112D4EA for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 05:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.501
X-Spam-Level: 
X-Spam-Status: No, score=-17.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 v2b_yknswDMl for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 05:32:37 -0700 (PDT)
Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (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 89666128CF2 for <quic@ietf.org>; Mon, 29 Oct 2018 05:32:37 -0700 (PDT)
Received: by mail-wr1-x429.google.com with SMTP id r10-v6so8482926wrv.6 for <quic@ietf.org>; Mon, 29 Oct 2018 05:32:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cwrm96QXm00xA09bgoDJgkVf8lY8/xr4fVMtTSEs3Bs=; b=gA5n6HHX7MLCXy4qXoclu/ltefeGumf+9qnuSB/+H8zPLNRCyIHuSAXqki1PBKRYwE UTH3PFb9Uer3XwfaUL4IXPfPmeigZwZQaahpVbsv9naSMem3O4TIBbVoXp5JMptd9QVj /M1nLWkG7MbNbCOlJS3svE9lC/tFzRzbxiDFDcToadV5DJIYYX5d2MZSDFnbbNuho0Md zh83EpkledZpilXmB89VlM2MfDcpiudSg+abU7goh4V5uT7ANdrOl7wtvZkf6a8f7v1e K2WpbKIrxiMmCooIfBYAFg485av1iKcJxLsRi7acxdcH60ItoFrX9tLjacVY3jav6vId ZDSg==
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=cwrm96QXm00xA09bgoDJgkVf8lY8/xr4fVMtTSEs3Bs=; b=JA3+nh9zioJpB24DS77YaoQBrjQiOiEJxz0B5J7ahdxhfwnhka4GKHtWIY6otPEIJJ mWNfmsvMp1fHHpBeMPoL5hCuLo1SspdgVqg5xKRuwpGscjTZXFm8xpy9MmvtbcH6uYX2 v7xYC67OyC9Jl+DJ50aHZmQRt+evDEzn2rVDej1B4k7wzre5oVOqCw0y433iJ9rI3s0b to1ae1Qsk02xN+8gvpZnlBuCtci6Kp60AvvN/tpgm2Y5AlOzBolCeFhm4ouG3fZIfK9C a6ijkm3TA40QRm9eez2/NNWqeH6G2JdHaOI6QRe29XQsWqK/IepxJZYh+GVMUxLbQbb0 BqqQ==
X-Gm-Message-State: AGRZ1gI7ygcXetdtqmgxGz8h5M/Omz/Gm9kxmr5/Af37RsjNWkkyTgdY ZdSU+NJL5PCtX1lanBDiGuilK8pe7yga+6KZ8Xo4Wg==
X-Google-Smtp-Source: AJdET5dAkOPZclYWafwDsRKCjcmodzXwen951m+uJpHuc+0vLxPo17RmOeQ6o98Ix6q1M1HkYJ27MtQP4//GcWyfr0c=
X-Received: by 2002:a05:6000:1008:: with SMTP id a8mr14494159wrx.271.1540816355760;  Mon, 29 Oct 2018 05:32:35 -0700 (PDT)
MIME-Version: 1.0
References: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com>
In-Reply-To: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Mon, 29 Oct 2018 08:32:24 -0400
Message-ID: <CAKcm_gMDOyJC0AwOo2knN6AMxVbySjGsrLvjcC9A8UA9xcvcWw@mail.gmail.com>
Subject: Re: flow control and DATAGRAM
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Tommy Pauly <tpauly@apple.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008d27be05795d43d8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/xp1RHNEFkz8EWD0wcvPRLJwzvdA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 12:32:39 -0000

--0000000000008d27be05795d43d8
Content-Type: text/plain; charset="UTF-8"

Good catch Martin, I missed that in the draft as well, and I also think
it's impossibly with the proposed design.

And yes, I think Martin's proposed solution is likely the only practical
one.  In my implementation, the frame is passed up to the application
immediately, so technically QUIC processed it, and it's the application's
job to decide what to do with it.

On Mon, Oct 29, 2018 at 1:16 AM Martin Thomson <martin.thomson@gmail.com>
wrote:

> Hi Tommy,
>
> Your slides - <
> https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF103-QUIC-Datagram.pdf
> >
> - say that DATAGRAM frames respect connection-level flow control.  I
> missed that in the draft, and I don't know how they can do that in the
> face of packet loss, especially when you don't necessarily retransmit
> lost DATAGRAM frames.
>
> For that to work, you would need a bunch more machinery to make the
> connection-level flow control sync between endpoints in the case that
> packets are lost.  A disagreement about how much flow control is used
> causes things to break down badly.  Ian and I discussed this point at
> the last meeting and quickly agreed that while it might be nice to
> have flow control for this stuff, the increase in complexity is
> considerable and (at the time) we thought it wouldn't be worth it.
>
> The problem that introduces is that you could end up having too many
> DATAGRAM frames arrive.  The receiver has to drop something at the
> point that it can't handle them.  And we say that when you acknowledge
> something, you processed it.  That's tricky.
>
> It might be easier to say that a QUIC acknowledgment for a DATAGRAM
> frame doesn't mean that it was received and processed by an
> application.  An endpoint might discard these frames before passing
> them on to applications if it doesn't have space.  In other words,
> acknowledgment of DATAGRAM means that QUIC got it, not that the
> application got it.  Sadly, that means that the QUIC acknowledgment
> machinery doesn't help the application that uses DATAGRAM all that
> much.  Also, the lower bound on reliability is 0, which isn't the best
> thing ever.
>
> Hard choices, I know.  I don't have a good design for maintaining
> connection-level flow control (or any back pressure mechanism with
> equivalent properties) that doesn't add both complexity and overhead.
>
> Cheers,
> Martin
>
>

--0000000000008d27be05795d43d8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Good catch Martin, I missed that in the draft as well, and=
 I also think it&#39;s impossibly with the proposed design.<div><br></div><=
div>And yes, I think Martin&#39;s proposed solution is likely the only prac=
tical one.=C2=A0 In my implementation, the frame is passed up to the applic=
ation immediately, so technically QUIC processed it, and it&#39;s the appli=
cation&#39;s job to decide what to do with it.</div></div><br><div class=3D=
"gmail_quote"><div dir=3D"ltr">On Mon, Oct 29, 2018 at 1:16 AM Martin Thoms=
on &lt;<a href=3D"mailto:martin.thomson@gmail.com">martin.thomson@gmail.com=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Tommy,<br>
<br>
Your slides - &lt;<a href=3D"https://github.com/quicwg/wg-materials/blob/ma=
ster/ietf103/IETF103-QUIC-Datagram.pdf" rel=3D"noreferrer" target=3D"_blank=
">https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF103-QUIC-D=
atagram.pdf</a>&gt;<br>
- say that DATAGRAM frames respect connection-level flow control.=C2=A0 I<b=
r>
missed that in the draft, and I don&#39;t know how they can do that in the<=
br>
face of packet loss, especially when you don&#39;t necessarily retransmit<b=
r>
lost DATAGRAM frames.<br>
<br>
For that to work, you would need a bunch more machinery to make the<br>
connection-level flow control sync between endpoints in the case that<br>
packets are lost.=C2=A0 A disagreement about how much flow control is used<=
br>
causes things to break down badly.=C2=A0 Ian and I discussed this point at<=
br>
the last meeting and quickly agreed that while it might be nice to<br>
have flow control for this stuff, the increase in complexity is<br>
considerable and (at the time) we thought it wouldn&#39;t be worth it.<br>
<br>
The problem that introduces is that you could end up having too many<br>
DATAGRAM frames arrive.=C2=A0 The receiver has to drop something at the<br>
point that it can&#39;t handle them.=C2=A0 And we say that when you acknowl=
edge<br>
something, you processed it.=C2=A0 That&#39;s tricky.<br>
<br>
It might be easier to say that a QUIC acknowledgment for a DATAGRAM<br>
frame doesn&#39;t mean that it was received and processed by an<br>
application.=C2=A0 An endpoint might discard these frames before passing<br=
>
them on to applications if it doesn&#39;t have space.=C2=A0 In other words,=
<br>
acknowledgment of DATAGRAM means that QUIC got it, not that the<br>
application got it.=C2=A0 Sadly, that means that the QUIC acknowledgment<br=
>
machinery doesn&#39;t help the application that uses DATAGRAM all that<br>
much.=C2=A0 Also, the lower bound on reliability is 0, which isn&#39;t the =
best<br>
thing ever.<br>
<br>
Hard choices, I know.=C2=A0 I don&#39;t have a good design for maintaining<=
br>
connection-level flow control (or any back pressure mechanism with<br>
equivalent properties) that doesn&#39;t add both complexity and overhead.<b=
r>
<br>
Cheers,<br>
Martin<br>
<br>
</blockquote></div>

--0000000000008d27be05795d43d8--


From nobody Mon Oct 29 05:48:48 2018
Return-Path: <dtikhonov@litespeedtech.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 65A07130F12 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 05:48:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 LF1MCmh5HcCo for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 05:48:44 -0700 (PDT)
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (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 B80E212D4F2 for <quic@ietf.org>; Mon, 29 Oct 2018 05:48:44 -0700 (PDT)
Received: by mail-io1-xd36.google.com with SMTP id n18-v6so4832740ioa.9 for <quic@ietf.org>; Mon, 29 Oct 2018 05:48:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=LNtc3yWnRLAbAZ9NRYKFlNE3yFDkjm0etSVqppfH0MY=; b=0K3OpPIgxFq7Zf/zOxzC9kyXXKGsPF21AxvC2/JFuGyIL5056CUrX3vDqgYp+pQpR8 VnoDki6sG3oMHHkTa76RWiamL5nvDhDeagyoXv5keyx5b12FftAnLly10jADlltlzB06 +GVKqemhGKtOsqN1co98aPRzeTRse5UH5WRrRjaMrQ8sQ/D0SVxzuWEwJPJ1UJmJuGL1 Nsg6YoIEgBlVuefrg1sSayXZ40JzSC4G8cYfYF/kd4MHro+hcDDzYCFQl5AtyoE+8T1v G4xBFMln8mgQQRv5RaoIZ4gpeJaS7V8cux40fhv1rdixK+pI/NRKarr+MHnN+saKVx2U erWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=LNtc3yWnRLAbAZ9NRYKFlNE3yFDkjm0etSVqppfH0MY=; b=iku3BxKgVkr0d/8lP5nYsDVQ/ETYQ3W/NpkKKv1qm4fF2cCO+1GhMIYcU4M9hP6jL+ b15GIVhf/wRtCokn3KyDlO6Uv4hY93Lw7oms+BVIh7ga368hiKqbY14VB2AWqaxQFCci TmwcGfPS7ziqdlpWTTiNZm+iqXGXE4TOrmM3Fd5JGuCmBJ4ekvkbEeqOzKa1QLgzTkAA TjAUugHu/BI9WSw8Oau3+63MS4+H5nYFMehSzTCmtSwYwbZRBuc6iYurOiVc/Mff0mfF UjUJMrDILNrtyPe/s+1RPzKUfTphn+1W9sZU6ncZfLdccuhCXU7hvq238Zxi6puXVMxf qj8g==
X-Gm-Message-State: AGRZ1gKjKDwF7XvAABcmlrwDb8No6C5GdldSMCR1Ujcwx3Kz3G+q0Z3Z XgvP1OTJyDzBLzIHJmVQ0Ofglw==
X-Google-Smtp-Source: AJdET5eBwqTZplc9JPo3nvZgsqTtYJj8exMYUUtoRNe5NgdFmrLDHgJDp73zMc+7GWzSu5b491kvwQ==
X-Received: by 2002:a6b:1406:: with SMTP id 6-v6mr8042719iou.218.1540817323959;  Mon, 29 Oct 2018 05:48:43 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id i71-v6sm6079297iti.15.2018.10.29.05.48.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Oct 2018 05:48:43 -0700 (PDT)
Date: Mon, 29 Oct 2018 08:48:36 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Marten Seemann <martenseemann@gmail.com>
Cc: QUIC WG <quic@ietf.org>
Subject: Re: Using varints to encode the Transport Parameters
Message-ID: <20181029124835.GA7258@ubuntu-dmitri>
Mail-Followup-To: Marten Seemann <martenseemann@gmail.com>, QUIC WG <quic@ietf.org>
References: <CAOYVs2rKJMXO806Jp5CpCkH8T80zUHUAauUqdmwEQuTJUhPxnA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAOYVs2rKJMXO806Jp5CpCkH8T80zUHUAauUqdmwEQuTJUhPxnA@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/xcSROUSGogWlj_ScTME4buh5XLw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 12:48:46 -0000

I see two problems with this proposal: timing and size.

This is rather late in the game.  If the Working Group is to follow
the plan Martin Thomson outlined in a recent email, this change would
have to be included into -17.

A hybrid of the TLS Presentation language and QUIC varints has to be
specified somewhere itself, thereby increasing the size of the already
hefty transport document.  This new specification, in turn, is likely
to engender some debate and further optimization proposals.  Allowed
to go unchecked, this work would slip our schedule further.

One way to approach this proposal is to have a ready-to-merge PR and
hum it at the upcoming meeting.

  - Dmitri.

On Mon, Oct 29, 2018 at 06:13:50PM +0700, Marten Seemann wrote:
> This is based on issue https://github.com/quicwg/base-drafts/issues/1608.
> 
> The proposal is to change the encoding of the QUIC Transport Parameters
> exchanged during the handshake, in order to achieve greater consistency
> with how QUIC encodes values, and also to save a few bytes.
> 
> We have a few things that are called transport parameters. This proposal
> only applies to the TransportParameter struct as defined in section 18 as:
> *struct {*
> *      TransportParameterId parameter;*
> *      opaque value<0..2^16-1>;*
> *} TransportParameter;*
> According to the encoding defined by the TLS spec, every key-value pair
> will be serialized as:
> TransportParameterID (2 byte), length (2 byte), value (length byte)
> where the length of the value is specified for each TransportParameterID.
> 
> We could switch to varint encoding, as follows:
> 
> 1. for the TransportParameterID: Since we’re only using the code points 0
> to 13, we could save one byte per ID by using a varint.
> 2. for the length: We would save one more byte, as long as the length of
> the value is less than 16 byte (which will be the case for all values
> except the preferred_address).
> 3. For numeric values: This would apply to the flow control offsets, the
> maximum stream IDs, the ack delay exponent , the maximum packet size and
> the max_ack_delay.
> 
> In addition to the byte-savings of 1. and 2., 3. has some more desirable
> properties:
>     1. It would allow us to encode the whole range of permitted values. For
> example, initial_max_data is a 62-bit value, but the current encoding just
> allows to send 4 bytes.
>     2. Depending on the value sent, this might or might not save a byte
> here and there.
>     3. We’d be consistent with the encoding we use everywhere else.


From nobody Mon Oct 29 06:26:22 2018
Return-Path: <alexandre.ferrieux@orange.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 7BAF7130E1D for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 06:26:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.291
X-Spam-Level: 
X-Spam-Status: No, score=-0.291 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 uwYhLMNvFb_C for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 06:26:20 -0700 (PDT)
Received: from orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CDB71293FB for <quic@ietf.org>; Mon, 29 Oct 2018 06:26:20 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id 42kFjk3lCcz5vsC; Mon, 29 Oct 2018 14:26:18 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 42kFjk50csz1xpG; Mon, 29 Oct 2018 14:26:18 +0100 (CET)
Received: from [10.193.4.89] (10.168.234.6) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 29 Oct 2018 14:26:18 +0100
Subject: Re: Big changes in -17
To: Martin Thomson <martin.thomson@gmail.com>, QUIC WG <quic@ietf.org>
References: <CABkgnnVFqdx4VYbqT7SztPf8Q+vWMV86VkOHY-4aGSpauNPapg@mail.gmail.com>
From: <alexandre.ferrieux@orange.com>
Message-ID: <851_1540819578_5BD70A7A_851_343_1_0ada4f1d-e8c5-25b5-0e8b-8111ee726ae7@orange.com>
Date: Mon, 29 Oct 2018 14:26:18 +0100
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnVFqdx4VYbqT7SztPf8Q+vWMV86VkOHY-4aGSpauNPapg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: fr-xx-moderne
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.168.234.6]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/aw10Br8N2O2WrugHTI4ED9WxN38>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 13:26:21 -0000

Hello Martin,

On 10/26/2018 01:20 AM, Martin Thomson wrote:
> 4. The first octet.  We discussed this in NY:
> https://github.com/quicwg/wg-materials/blob/master/interim-18-09/minutes.md#first-octet---martin-thomson
> and we will have a decision about the spin bit within 2 weeks.  After
> that, one of the designs discussed will be implemented.

Do I assume correctly that "the designs discussed" are the following three:

  - nothing (no spin bit)
  - spin bit alone
  - spin bit + VEC

Or is there room for other (written) proposals ?

_________________________________________________________________________________________________________________________

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.


From nobody Mon Oct 29 08:21:51 2018
Return-Path: <tpauly@apple.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 EA97C130FDE for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 08:21:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.47
X-Spam-Level: 
X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 CgSyUtebUtTl for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 08:21:47 -0700 (PDT)
Received: from nwk-aaemail-lapp01.apple.com (nwk-aaemail-lapp01.apple.com [17.151.62.66]) (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 8819E130FF0 for <quic@ietf.org>; Mon, 29 Oct 2018 08:21:47 -0700 (PDT)
Received: from pps.filterd (nwk-aaemail-lapp01.apple.com [127.0.0.1]) by nwk-aaemail-lapp01.apple.com (8.16.0.22/8.16.0.22) with SMTP id w9TFLg5l064953; Mon, 29 Oct 2018 08:21:42 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : from : message-id : subject : date : in-reply-to : cc : to : references; s=20180706; bh=JIy9OVUr8FO+NAGFgzAAn/b3CJXxpz6NS/rMFYg23T4=; b=C44moYFPQaO2uLeGnrWLfAuiBkKVbD3knSWpiMbLMISr4DSxfSRg2B0iDOwLdH4N3i9F DovX2K/dHScFQzLGKZf8QLbqGcPZepgHlVCUO221oFmXAEor4FA/NA2hY4g/0/mOJor3 9Hu+DZ1ENFQy6kE/TjHMcDs9guUg9iB/mDcdU+UzNANcHknkAmCT54CANiniC0QTR6nd N5tiHoCZLfUaQxJ1Ztla2O3NUGqGVZ/CPkAIA+wYdNT9It43f0e1Y8V0acZwsa2XW9UW YOQOPLC+0A2rSmpHhXMrriawBKZGNhCEBs5B/RWCowt08MIBwDqm+Dj9Rr9zZdkb/QW1 YQ== 
Received: from ma1-mtap-s02.corp.apple.com (ma1-mtap-s02.corp.apple.com [17.40.76.6]) by nwk-aaemail-lapp01.apple.com with ESMTP id 2ncpy5rbev-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 29 Oct 2018 08:21:42 -0700
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_vYp3Wjs6KJBd5xKQoiEXWQ)"
Received: from nwk-mmpp-sz10.apple.com (nwk-mmpp-sz10.apple.com [17.128.115.122]) by ma1-mtap-s02.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPS id <0PHD00A7I9C24W70@ma1-mtap-s02.corp.apple.com>; Mon, 29 Oct 2018 08:21:39 -0700 (PDT)
Received: from process_viserion-daemon.nwk-mmpp-sz10.apple.com by nwk-mmpp-sz10.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) id <0PHD00B008CZD900@nwk-mmpp-sz10.apple.com>; Mon, 29 Oct 2018 08:21:38 -0700 (PDT)
X-Va-A: 
X-Va-T-CD: 1fbd3678d9e2d523e4297dddc27688bd
X-Va-E-CD: c49bf73f2750f6e382c68706c9cc0d07
X-Va-R-CD: 22b8f453b4f47490ba2e2176fe96324e
X-Va-CD: 0
X-Va-ID: 2d1b6828-93dd-4059-b941-32d74e9c085f
X-V-A: 
X-V-T-CD: 8d71b7585ae9b1e749a466ceb4b88582
X-V-E-CD: c49bf73f2750f6e382c68706c9cc0d07
X-V-R-CD: 22b8f453b4f47490ba2e2176fe96324e
X-V-CD: 0
X-V-ID: 1a93c611-a911-455d-9b7c-b1d597d0a615
Received: from process_milters-daemon.nwk-mmpp-sz10.apple.com by nwk-mmpp-sz10.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) id <0PHD00M00953MX00@nwk-mmpp-sz10.apple.com>; Mon, 29 Oct 2018 08:21:38 -0700 (PDT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-10-29_11:,, signatures=0
Received: from [17.234.42.146] (unknown [17.234.42.146]) by nwk-mmpp-sz10.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPSA id <0PHD00IK19C14S70@nwk-mmpp-sz10.apple.com>; Mon, 29 Oct 2018 08:21:38 -0700 (PDT)
Sender: tpauly@apple.com
From: Tommy Pauly <tpauly@apple.com>
Message-id: <19D3595B-8845-45B6-A60D-9E934DD49FAC@apple.com>
Subject: Re: flow control and DATAGRAM
Date: Mon, 29 Oct 2018 08:21:33 -0700
In-reply-to: <CAKcm_gMDOyJC0AwOo2knN6AMxVbySjGsrLvjcC9A8UA9xcvcWw@mail.gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>
To: Ian Swett <ianswett@google.com>, Martin Thomson <martin.thomson@gmail.com>
References: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com> <CAKcm_gMDOyJC0AwOo2knN6AMxVbySjGsrLvjcC9A8UA9xcvcWw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.100.36)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-29_11:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ARudWu6xkuq9CZZtumztvvaj-z0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 15:21:50 -0000

--Boundary_(ID_vYp3Wjs6KJBd5xKQoiEXWQ)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

Hi Martin, Ian,

Yes, very good points!

My tendency would be to prefer what Ian's implementation does of passing these DATAGRAM frames up immediately to the application. I don't think that the acknowledgment needs to indicate that the frame was processed by the application, but merely that it has been delivered to the application (that is, the application doesn't get to do anything with the frame that can influence the acknowledgment).

The current draft indicates that the content of the DATAGRAM frames contributes to the limit used for MAX_DATA, and that if that amount is reached, the frames are blocked along with STREAM data. I think this works fine for the sender, while the receiver gets into the discussion you present. On the sender side, reaching MAX_DATA could mean dropping the DATAGRAM frames when unable to send more (and sending BLOCKED instead). Since the frames are unreliable, they can be dropped in this situation without violating the API contract. 

On the receiver side, I agree that queuing the DATAGRAM frames to let the application drive flow control in the way it does for STREAM frames adds complexity and diminishes the utility of the frame and ACKs. However, I can imagine taking a fairly simplistic approach in which the data limit is automatically increased upon reception of the frame (and the frame is immediately passed to the application). This allows the initial_max_data to put a cap on the amount of data in a given flight of DATAGRAMS, and allow the size of a flight of DATAGRAM frames to be limited by the amount of room left over from STREAM data that may be consuming the connection-wide flow control. 

Perhaps this approach needs a clearer name other than "flow control", since it has a somewhat different meaning in effect.

As for ACKs, if we never discard on the receiver side, the ACK is pretty useful for detecting if there was network-based packet loss.

Thanks,
Tommy 

> On Oct 29, 2018, at 5:32 AM, Ian Swett <ianswett@google.com> wrote:
> 
> Good catch Martin, I missed that in the draft as well, and I also think it's impossibly with the proposed design.
> 
> And yes, I think Martin's proposed solution is likely the only practical one.  In my implementation, the frame is passed up to the application immediately, so technically QUIC processed it, and it's the application's job to decide what to do with it.
> 
> On Mon, Oct 29, 2018 at 1:16 AM Martin Thomson <martin.thomson@gmail.com <mailto:martin.thomson@gmail.com>> wrote:
> Hi Tommy,
> 
> Your slides - <https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF103-QUIC-Datagram.pdf <https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF103-QUIC-Datagram.pdf>>
> - say that DATAGRAM frames respect connection-level flow control.  I
> missed that in the draft, and I don't know how they can do that in the
> face of packet loss, especially when you don't necessarily retransmit
> lost DATAGRAM frames.
> 
> For that to work, you would need a bunch more machinery to make the
> connection-level flow control sync between endpoints in the case that
> packets are lost.  A disagreement about how much flow control is used
> causes things to break down badly.  Ian and I discussed this point at
> the last meeting and quickly agreed that while it might be nice to
> have flow control for this stuff, the increase in complexity is
> considerable and (at the time) we thought it wouldn't be worth it.
> 
> The problem that introduces is that you could end up having too many
> DATAGRAM frames arrive.  The receiver has to drop something at the
> point that it can't handle them.  And we say that when you acknowledge
> something, you processed it.  That's tricky.
> 
> It might be easier to say that a QUIC acknowledgment for a DATAGRAM
> frame doesn't mean that it was received and processed by an
> application.  An endpoint might discard these frames before passing
> them on to applications if it doesn't have space.  In other words,
> acknowledgment of DATAGRAM means that QUIC got it, not that the
> application got it.  Sadly, that means that the QUIC acknowledgment
> machinery doesn't help the application that uses DATAGRAM all that
> much.  Also, the lower bound on reliability is 0, which isn't the best
> thing ever.
> 
> Hard choices, I know.  I don't have a good design for maintaining
> connection-level flow control (or any back pressure mechanism with
> equivalent properties) that doesn't add both complexity and overhead.
> 
> Cheers,
> Martin
> 


--Boundary_(ID_vYp3Wjs6KJBd5xKQoiEXWQ)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Martin, Ian,<div class=3D""><br class=3D""></div><div class=3D"">Yes, =
very good points!</div><div class=3D""><br class=3D""></div><div =
class=3D"">My tendency would be to prefer what Ian's implementation does =
of passing these DATAGRAM frames up immediately to the application. I =
don't think that the acknowledgment needs to indicate that the frame was =
processed by the application, but merely that it has been delivered to =
the application (that is, the application doesn't get to do anything =
with the frame that can influence the acknowledgment).</div><div =
class=3D""><br class=3D""></div><div class=3D"">The current draft =
indicates that the content of the DATAGRAM frames contributes to the =
limit used for&nbsp;MAX_DATA, and that if that amount is reached, the =
frames are blocked along with STREAM data. I think this works fine for =
the sender, while the receiver gets into the discussion you present. On =
the sender side, reaching MAX_DATA could mean dropping the DATAGRAM =
frames when unable to send more (and sending BLOCKED instead). Since the =
frames are unreliable, they can be dropped in this situation without =
violating the API contract.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">On the receiver side, I agree that =
queuing the DATAGRAM frames to let the application drive flow control in =
the way it does for STREAM frames adds complexity and diminishes the =
utility of the frame and ACKs. However, I can imagine taking a fairly =
simplistic approach in which the data limit is automatically increased =
upon reception of the frame (and the frame is immediately passed to the =
application). This allows the initial_max_data to put a cap on the =
amount of data in a given flight of DATAGRAMS, and allow the size of a =
flight of DATAGRAM frames to be limited by the amount of room left over =
from STREAM data that may be consuming the connection-wide flow =
control.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">Perhaps this approach needs a clearer name other than "flow =
control", since it has a somewhat different meaning in effect.</div><div =
class=3D""><br class=3D""></div><div class=3D"">As for ACKs, if we never =
discard on the receiver side, the ACK is pretty useful for detecting if =
there was network-based packet loss.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Thanks,</div><div =
class=3D"">Tommy&nbsp;</div><div class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Oct =
29, 2018, at 5:32 AM, Ian Swett &lt;<a href=3D"mailto:ianswett@google.com"=
 class=3D"">ianswett@google.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D"">Good catch Martin, I missed that in the draft as well, and I =
also think it's impossibly with the proposed design.<div class=3D""><br =
class=3D""></div><div class=3D"">And yes, I think Martin's proposed =
solution is likely the only practical one.&nbsp; In my implementation, =
the frame is passed up to the application immediately, so technically =
QUIC processed it, and it's the application's job to decide what to do =
with it.</div></div><br class=3D""><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"">On Mon, Oct 29, 2018 at 1:16 AM Martin Thomson =
&lt;<a href=3D"mailto:martin.thomson@gmail.com" =
class=3D"">martin.thomson@gmail.com</a>&gt; wrote:<br =
class=3D""></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Tommy,<br class=3D"">=

<br class=3D"">
Your slides - &lt;<a =
href=3D"https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF103=
-QUIC-Datagram.pdf" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF=
103-QUIC-Datagram.pdf</a>&gt;<br class=3D"">
- say that DATAGRAM frames respect connection-level flow control.&nbsp; =
I<br class=3D"">
missed that in the draft, and I don't know how they can do that in =
the<br class=3D"">
face of packet loss, especially when you don't necessarily retransmit<br =
class=3D"">
lost DATAGRAM frames.<br class=3D"">
<br class=3D"">
For that to work, you would need a bunch more machinery to make the<br =
class=3D"">
connection-level flow control sync between endpoints in the case that<br =
class=3D"">
packets are lost.&nbsp; A disagreement about how much flow control is =
used<br class=3D"">
causes things to break down badly.&nbsp; Ian and I discussed this point =
at<br class=3D"">
the last meeting and quickly agreed that while it might be nice to<br =
class=3D"">
have flow control for this stuff, the increase in complexity is<br =
class=3D"">
considerable and (at the time) we thought it wouldn't be worth it.<br =
class=3D"">
<br class=3D"">
The problem that introduces is that you could end up having too many<br =
class=3D"">
DATAGRAM frames arrive.&nbsp; The receiver has to drop something at =
the<br class=3D"">
point that it can't handle them.&nbsp; And we say that when you =
acknowledge<br class=3D"">
something, you processed it.&nbsp; That's tricky.<br class=3D"">
<br class=3D"">
It might be easier to say that a QUIC acknowledgment for a DATAGRAM<br =
class=3D"">
frame doesn't mean that it was received and processed by an<br class=3D"">=

application.&nbsp; An endpoint might discard these frames before =
passing<br class=3D"">
them on to applications if it doesn't have space.&nbsp; In other =
words,<br class=3D"">
acknowledgment of DATAGRAM means that QUIC got it, not that the<br =
class=3D"">
application got it.&nbsp; Sadly, that means that the QUIC =
acknowledgment<br class=3D"">
machinery doesn't help the application that uses DATAGRAM all that<br =
class=3D"">
much.&nbsp; Also, the lower bound on reliability is 0, which isn't the =
best<br class=3D"">
thing ever.<br class=3D"">
<br class=3D"">
Hard choices, I know.&nbsp; I don't have a good design for =
maintaining<br class=3D"">
connection-level flow control (or any back pressure mechanism with<br =
class=3D"">
equivalent properties) that doesn't add both complexity and overhead.<br =
class=3D"">
<br class=3D"">
Cheers,<br class=3D"">
Martin<br class=3D"">
<br class=3D"">
</blockquote></div>
</div></blockquote></div><br class=3D""></div></body></html>=

--Boundary_(ID_vYp3Wjs6KJBd5xKQoiEXWQ)--


From nobody Mon Oct 29 08:26:54 2018
Return-Path: <lars@eggert.org>
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 B335A130FF1 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 08:26:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 ODvI2Kub_vU5 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 08:26:52 -0700 (PDT)
Received: from emh01.mail.saunalahti.fi (emh01.mail.saunalahti.fi [62.142.5.107]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D631D130DF9 for <quic@ietf.org>; Mon, 29 Oct 2018 08:26:51 -0700 (PDT)
Received: from eggert.org (unknown [62.248.255.56]) by emh01.mail.saunalahti.fi (Postfix) with ESMTP id E27D92041F for <quic@ietf.org>; Mon, 29 Oct 2018 17:26:48 +0200 (EET)
Received: from slate.eggert.org (pf.eggert.org [172.16.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by eggert.org (Postfix) with ESMTPSA id 0525B1D072E for <quic@ietf.org>; Mon, 29 Oct 2018 17:26:34 +0200 (EET)
From: Lars Eggert <lars@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_6566EC29-2637-4CEF-A9F0-6B7BE0850158"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: Structuring the BKK spin bit discussion
Message-Id: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org>
Date: Mon, 29 Oct 2018 17:26:34 +0200
To: IETF QUIC WG <quic@ietf.org>
X-MailScanner-ID: 0525B1D072E.A31F6
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/5a2AE7MKXonzjWfUWn-T7NZOHcE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 15:26:54 -0000

--Apple-Mail=_6566EC29-2637-4CEF-A9F0-6B7BE0850158
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

you'll have seen that we've set aside a lengthy slot on the agenda in =
order to finish the discussion on whether the spin bit (described in =
draft-ietf-quic-spin-exp) should be included in the first version of =
QUIC the IETF publishes, and if yes, what shape that inclusion would =
take.

Note that draft-ietf-quic-spin-exp describes what we commonly call the =
single-bit spin bit variant. We'd like to confirm that the discussion =
will be limited to that variant.

Next, we'd like to confirm that the WG believes that it is fit-for =
purpose, i.e., that if a sufficient number of bits were spinning, =
operators could obtain the information they need. This also includes =
confirmation that the privacy aspects of the spin bit proposal are =
understood and acceptable to the WG.

We'd specifically like to ask client and server implementors with =
projected sizable deployments to indicate whether they intent to =
implement and deploy, if the WG decided to include the spin-bit in the =
spec. We have seen one such statement on the list from Microsoft (thank =
you!) and would be interested to hear from others, either on the list or =
during the session in Bangkok.

Finally, if the WG has agreement to include the spin bit in the spec =
based on the information from and the discussion on the points above, we =
need to come to consensus on what shape such an inclusion of the spin =
bit would take, e.g., negotiated extension, conformance requirements =
(MAY/SHOULD/MUST) for clients and servers, etc.

Please let us know if you have any questions or comments about this =
approach for structuring the discussion in Bangkok.

Lars and Mark

--Apple-Mail=_6566EC29-2637-4CEF-A9F0-6B7BE0850158
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAlvXJqoACgkQVLXDCb9w
wVcOqw/+K80PAeLl6f1KZTalF1/gXNWKoSQ/oSxOjUjW6H+EIrf83GdfVUuWCsh7
XiQv7RGUNNJMH74Ex9UmhwSpm4J6uyzS5IRRyBh+taYbthlc8mS0hxjek/wQWUOV
eYr3ezA+X7FsUmTHVyTr2r6GBVq+/nGVcRnwuDnlMdAJGDERyBX4IYnXN5nmw2QP
JFLMIAGuxbrLBGKTY8H+8KFVn1FhpSOG2TRJgt3pcWye6w5627wbCB40ejiMq6ZY
GvrkGPUQGhi0CHA+lyspmNX9pH+PBBLIeAJSq1oiQ3TcQtJcbO5GYgxyNqDAnzfx
Qv/rUhItIqT4UFS1uoxhFfZgy6opstym2oZhSSQRUyuBjiVqCKc7zotjrwpMxkHp
guS8/cqbF+UyPUYkWxHL90iL6pjwUozbyVBRfin2T3FzZbdccFOw/ztdrVir29jj
3A6ym/wa7zZKYWbi6WCyc0IWqkPp/9wm8PN2rCFJ360Qu3lwhpyUOYsbmb8DUw/y
x0ICakkuXAo5bNBKlNy+7Wem7K1eX+Xps13YOHpuqPHLxtwTMcS9z84pnkiRxlle
67P3kl/zgsRqgNgJKAH7o39G6Dni3wiTmZdjLc055KzsUbNol7d2bEnprMVBEWUq
83qAbWEmZcyQ+sTv6aHWSYJuy6oa4KiBXDP1kcDD9bSIbcXKO8g=
=4ge7
-----END PGP SIGNATURE-----

--Apple-Mail=_6566EC29-2637-4CEF-A9F0-6B7BE0850158--


From nobody Mon Oct 29 09:08:10 2018
Return-Path: <dtikhonov@litespeedtech.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 1AD5C130FF9 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 09:08:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 8LbsGLKMTCPu for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 09:08:06 -0700 (PDT)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 9C8331292F1 for <quic@ietf.org>; Mon, 29 Oct 2018 09:08:06 -0700 (PDT)
Received: by mail-qt1-x82c.google.com with SMTP id z2-v6so9877915qts.1 for <quic@ietf.org>; Mon, 29 Oct 2018 09:08:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=0cDrHLPf8LYDlsTn/hX+qEGgTuYkEFNiaX68XqC2UVA=; b=JFxcXm82uf2yAbN3vtvR30uqxlPpBtD8x6T/vfx0ZvSgVDuIVAOQ411apqJnQJ4fmX c2tROimSDSBkKaUo99X/IwhdkoDBjJ+TcJT1Jwja3eXkMeQxbdzO9jT9XSGxirnuDQZF yYy2I83NqF0QIXI3mfHHn4zBiu/hOWY3LhVMZgJZNCs54WG9E7L+FppAQIttmId+g2n0 I8L0pQzCiLbVJitTTyqnAwubcie2wuKOootz2HOfkz0cQZDxAR85qJB0yNBmmARzYCzD GNPhfgaEBfLwR4s2T6epEoV1Ehi8aFKwk2OqRzVK90jG2loSs5oT3ZrRGDlzP+PF/1XY xVeA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=0cDrHLPf8LYDlsTn/hX+qEGgTuYkEFNiaX68XqC2UVA=; b=sI0NR0bq6nul+KDnDOa5E+EaCSTsmurz6DSGck+ytntu84yFY3G7TlOtj1YDm8gJDY 2DQi5Af+G+SW+tud3rgb13RLT2iwQHfm9GWYtsOCPq5Kg71jQp5CRHx7iKz8bMR4EGhV B9jSgxQOod0M9igca1+sATBZneanCxzf2tgYAaMfnqUOSz0NqzzmJpBBfqFp0Ji/QwNg zCxCQ/E8f6jCUhRTJ7mMkSGMEGabNDzwHFp14QCRFVrri0iQJeN1yCY7406pMSWHHRx4 ehWJo+b/k+drZITXkrwjF9BZmGndm7rF1T5PA6TGNZP7hujGn8h2sCEnSmbvRyxBA6Y5 zGbw==
X-Gm-Message-State: AGRZ1gJSA0QxxuuisK4QJX4xM+oYtqRC0G5JPdgSC3kIG5SeVDwXTFhS zc/Ve41jppngnjANeLEHToTYXg==
X-Google-Smtp-Source: AJdET5c0TmZLTuAkNxFf6lRarCqHB7ehgHLnIRH6mnsUg3/JN4M+km9Y2U4ChRLQvnSqL7aygnx9NQ==
X-Received: by 2002:a0c:d94f:: with SMTP id t15mr11739201qvj.189.1540829285668;  Mon, 29 Oct 2018 09:08:05 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id t41-v6sm13038278qte.95.2018.10.29.09.08.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Oct 2018 09:08:05 -0700 (PDT)
Date: Mon, 29 Oct 2018 12:08:03 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Lars Eggert <lars@eggert.org>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Structuring the BKK spin bit discussion
Message-ID: <20181029160802.GD7258@ubuntu-dmitri>
Mail-Followup-To: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fDuLqguR7hKXiJNB89K8DJ3EgB8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 16:08:09 -0000

On Mon, Oct 29, 2018 at 05:26:34PM +0200, Lars Eggert wrote:
> We'd specifically like to ask client and server implementors with
> projected sizable deployments to indicate whether they intent to
> implement and deploy, if the WG decided to include the spin-bit in
> the spec.

LiteSpeed Technologies will support the spin bit -- both in our
server and client QUIC implementations -- if it make it into the
draft.

  - Dmitri.


From nobody Mon Oct 29 09:54:46 2018
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 6DA25131007 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 09:54:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 3gQJeqx97ASu for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 09:54:43 -0700 (PDT)
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 01817127333 for <quic@ietf.org>; Mon, 29 Oct 2018 09:54:42 -0700 (PDT)
Received: from xsmtp02.mail2web.com ([168.144.250.215]) by mx105.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1gHAoI-00050t-UG for quic@ietf.org; Mon, 29 Oct 2018 17:54:40 +0100
Received: from [10.5.2.13] (helo=xmail03.myhosting.com) by xsmtp02.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1gHAoB-0004fR-AM for quic@ietf.org; Mon, 29 Oct 2018 12:54:35 -0400
Received: (qmail 21957 invoked from network); 29 Oct 2018 16:54:28 -0000
Received: from unknown (HELO [192.168.1.104]) (Authenticated-user:_huitema@huitema.net@[172.56.42.225]) (envelope-sender <huitema@huitema.net>) by xmail03.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 29 Oct 2018 16:54:28 -0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Christian Huitema <huitema@huitema.net>
X-Mailer: iPhone Mail (16A404)
In-Reply-To: <20181029160802.GD7258@ubuntu-dmitri>
Date: Mon, 29 Oct 2018 09:53:22 -0700
Cc: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri>
To: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
Subject: Re: Structuring the BKK spin bit discussion
X-Originating-IP: 168.144.250.215
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.30)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5ut4lLhpkcDzlxRJGCRtKWN602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO37pNwwF1lRXh5rzvPzo9Jts1ujulqUFmMITHM77eiViUdM2cv0uLcJB++IXjL6ofM7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pB1VzUjpi3KNxdQZ39cmOPHk5EpHPznVavQp4h 1cyzxbQFXqQgkkYk8mNUb0+uxPxhiSGt4Ko2sv7hY6P0Yu3OA+AIcPc2JG++Fh0y/kogNkMJ0464 etNXHOU+5Kb0QuG3bATPP9eeLWC5kDweN7crsXBXvrLBlKCVRjjdPbjQ4HmidG0pg2HLuLsP3mPp isElTs5Ex5aNZlcgVQFtAhrEij3dKxLhoxcmaInYbR5vlqETd+klAX+KFYkIxu6zxdn+X2XX9bIs GDSYq5OAASmskVIcMSgqtcKbU9La+AHiCFB9vuYMeDoXsMJDD9CZFW2DHXeua4usuyudZl7ZJWmg 5a0jiD6XqsJZtjQxlyCdseygOIcx4SICe6nNcjjd/M50Y6QGVSvC9ATxEYI3bPwB8UgAvmhWj0Kt 6GdNtnBBpzNqJvBXd7I82n0qpCzrPWiSwKPXNKNk2RVY2K5nyLgw1Z+7sPmjIM3bM0ihYRE0YjPM ySEj7fwLz33nMnt8v2VACW4JJLnVejFxn/py1lO++mCP6KnOBvL4JpDTCrFGRy0l6PreDq/GwcsQ Fh1Do775kEu0bIDGx6Hc2akp+kPAbSHqAeeZGuerhbgzLuS7t5uWwhEJBPk7WpO8jVZh2VH4zM60 voqUUzJmvILAkkfgILwrzxcMEL7SnkJgQ5VKYC9Xgjmuntq3xZgBxhdNFJUcZu3d9ZNXJQW8HUxK X5uYJmvDK3PKrieG7T6bf9hS7hR0q7xASYaBUaOtmtSkj3iuxJhh7EHDojb6D9Mx+gs1+GHf4ys4 4rg2B8/9FmK9a1O9x7lsssuZ/53sObhu0YJN
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ITVdhUOHkmM3UiAvhnC8QeYfdM8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 16:54:46 -0000

=20

> On Oct 29, 2018, at 9:08 AM, Dmitri Tikhonov <dtikhonov@litespeedtech.com>=
 wrote:
>=20
>> On Mon, Oct 29, 2018 at 05:26:34PM +0200, Lars Eggert wrote:
>> We'd specifically like to ask client and server implementors with
>> projected sizable deployments to indicate whether they intent to
>> implement and deploy, if the WG decided to include the spin-bit in
>> the spec.
>=20
> LiteSpeed Technologies will support the spin bit -- both in our
> server and client QUIC implementations -- if it make it into the
> draft.

My implementation is not used in any large scale deployment, but it does sup=
port the spin bit. In fact, it has configuration options to support spin bit=
 variants: node, just spin, spin + vec, spin + QR.=20

I think the strongest objection to the spin bit was put up by Marten during t=
he last interim: measuring the RTT with the spin bit discloses the use of hi=
dden path segments like VPN. This issue was not discussed during the privacy=
 analysis.

The privacy issue could be mitigated by turning off the spin bit at privacy s=
ensitive clients, but this would make these clients "stick out".=20

One solution would be to remove the spin bit from the spec, trading off bett=
er privacy for worse management. I am considering another solution in which p=
rivacy sensitive clients hide the RTT by controlling the spin, for example s=
pinning at fixed intervals. I plan testing that option in Picoquic.

-- Christian Huitema=20

=20=


From nobody Mon Oct 29 10:02:44 2018
Return-Path: <nishida@sfc.wide.ad.jp>
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 6421813101F; Mon, 29 Oct 2018 10:02:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 t734ml4oYQrr; Mon, 29 Oct 2018 10:02:32 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [203.178.142.146]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 725B5131011; Mon, 29 Oct 2018 10:02:32 -0700 (PDT)
Received: from mail-ot1-f41.google.com (mail-ot1-f41.google.com [209.85.210.41]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 265D7278576; Tue, 30 Oct 2018 02:02:30 +0900 (JST)
Received: by mail-ot1-f41.google.com with SMTP id q5so2814594otl.13; Mon, 29 Oct 2018 10:02:30 -0700 (PDT)
X-Gm-Message-State: AGRZ1gJ5cQ73fX2Qk/cEfSiAiTA26YDwwUI+o15oUmxoFB0TlopWX3rj udA77W2kO8H3vCNk4Le70T8eQAnKYpi8ORZH1kg=
X-Google-Smtp-Source: AJdET5cfPzSHL2LhxraGNxr+KRuTeK0Y8B1qSV1PEP3yhprcQY1XGr8k7Fn/gAEMb2PmtDtq7LTtmpA4W+Y2V4oNmNY=
X-Received: by 2002:a9d:2084:: with SMTP id x4mr8497711ota.111.1540832547884;  Mon, 29 Oct 2018 10:02:27 -0700 (PDT)
MIME-Version: 1.0
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Mon, 29 Oct 2018 10:02:15 -0700
X-Gmail-Original-Message-ID: <CAO249yeMcawY6zZE-64QFO+L6NZhFLnvjXw9dnjn0qsqtKW9kw@mail.gmail.com>
Message-ID: <CAO249yeMcawY6zZE-64QFO+L6NZhFLnvjXw9dnjn0qsqtKW9kw@mail.gmail.com>
Subject: questions on draft-ietf-quic-recovery
To: quic@ietf.org, "tcpm@ietf.org" <tcpm@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/4_t2UAdkxRpeyVW1KU19XbL7mB0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 17:02:35 -0000

Hello,

At Bangkok, TCPM WG will have a session to discuss loss recovery and
congestion control mechanism in QUIC and TCP. (11/6 Tuesday
11:20-12:20)
I really appreciate Ian and Jana for the efforts.

I might overlook something as I couldn't follow up all discussion in
QUIC, but I am thinking that it might be good if we could get some
comments on the following questions.
I have listed several questions on the value of some parameters, but
it doesn't mean I disagree with these values. I just would like to
check where these values came from.
Hope this will be useful in some ways.


Section 4:
   QUIC supports both ack and timer for loss detection.
   But, it's not very clear whether an implementation can choose one
of them or it should implement both and can use both at the same time.
Can it be clarified?

Section 4.1.1:
   For RTT sampling, implementations will need to maintain the
transmission time for each sending packets even if they support only
ack-based method.
   But, this requirement might be hard for tiny devices. Wouldn't it
limit the applicability of QUIC?

   "the largest newly acked packet" might be confusing. packet that
acks the largest packet number?

Section 4.2.1:
   TCP RACK's reo_wnd is aiming to be 1/4 RTT. Why QUIC uses 1/8 RTT?

Section 4.2.2:
   The early retransmit logic in QUIC seems to be different from TCP's one.
   It doesn't look ack-based as it relies on timer. (I don't say this
is bad, but it's a bit strange to categorize it as an ack-based
method)
   TCP's early retransmit will be triggered only when the amount of
outstanding data is less than 4*SMSS, but this draft doesn't mention
about the condition. Is there any reason for it?
   when timer-based loss detection is used, it this logic still
available? or it won't be used with timer-based loss detection? We
might need clarifications here.

Section 4.3.2:
   TCP RACK's PTO is aiming to be 2 * SRTT. Why QUIC uses 1.5 * SRTT?

Section 4.3.3:
   RFC5681 uses 1 SMSS as the size of loss window, while QUIC uses 2.
I understand the motivation to reduce the possibility of consecutive
RTO events. But, this may means when TCP and QUIC connections are
under heavy congestion, QUIC connections will recover more quickly
than TCP connections. We might want to think how much QUIC and TCP
should be fair.

   BTW, it might not be necessarily, but QUIC does not need the upper
bound for RTO?

Section 4.4:
   why the default value of max_ack_delay is 25ms?

Section 4.5.7.3:
   Sorry.. what is 1/4 RTT timer for early retransmit?

Section 5.8.1:
   Why the recommended value is 1200 bytes?


From nobody Mon Oct 29 10:45:55 2018
Return-Path: <ianswett@google.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 376CA131048 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 10:45:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.5
X-Spam-Level: 
X-Spam-Status: No, score=-17.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 Ik_hlh0jUfrb for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 10:45:52 -0700 (PDT)
Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (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 B3062131023 for <quic@ietf.org>; Mon, 29 Oct 2018 10:45:51 -0700 (PDT)
Received: by mail-wm1-x330.google.com with SMTP id s10-v6so9141049wmc.5 for <quic@ietf.org>; Mon, 29 Oct 2018 10:45:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Ec2NxKH+4jIBgvhOoCeIXkWYJzqqNjvmxyVGzFnlCRQ=; b=TMvNlAiNlqHuA6Ac9zR1n8Qz9IRYQo22abuRCEO5N57Sq2TP9i95C8T6wR1yvewmi6 Qhdzz7gzh5s7u0isYoSuoilQ4NAUz9SRb+2pUqCdUA8+GE7LOxieDQZEAcSaubFZrkez d3hp1eILZZ0ee9IqbLlRtsPalkloHkGhpc4jivqy1Iae54hVUTk5XuwP+viUbyfP+mw7 eyVOGmDfXqauzESFOoNMO7txBvjQHiyXEtf4Sh6B1bvH7Lh0zl4s/OLdHw3j/MFNEOtN TOW3bP+bVBikYwkyaE5zW51TlsLDtQTqwfu1b+UiTeu+ZPkfruLju0ZBoAfmds7bFmNt KQmA==
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; bh=Ec2NxKH+4jIBgvhOoCeIXkWYJzqqNjvmxyVGzFnlCRQ=; b=OUGM/iEz3yzj+HWHy/G1hS9qEXwEtA+cg6K/ld1uiUkxHRrE91wB1YUmtnKYBsXicT 8Z38c/YHOZ3HuKJMzyCLcEUYmEEchqne4bsbXeOra1nzztGvN3QWw9WCDHmGWutgb85M 24U3VrCrJTbaM/JA1JSgFJ2qeV0aNSHd9ChW9NAvdY2Fjq0u55p5w5XJ8h9WY23mND05 aGSG7I8ZHDvnAYi6qBvA9uxDNC9shbM/xpWt7Bc3tAX8E5tVSjgwN5+a9cB0gHQmOZn8 7UZCht8LtoGEcduQX5Qp2xmbARKdGxqKZdRAkFSjHWqb6803/qJnvpVgAq3broNtnZqi KNOA==
X-Gm-Message-State: AGRZ1gIOj7lLbevPOh1Q16eC4oV1j7pL5EhOMJ3xkgDAXlqYiKuRFkFI 94BJafp96xfc0ZoIVUJBc24hxOg+H2ZtIDw2lGshEA==
X-Google-Smtp-Source: AJdET5fgqcdFxHEBgsmPQiy032aKzjSGTOKEGz2hjBILd9s/DE9ZEc1ClT8pTPYyEmo8ZWbzRBUPfh+mUAFYSUdtzKE=
X-Received: by 2002:a1c:cc8:: with SMTP id 191-v6mr14116132wmm.55.1540835150048;  Mon, 29 Oct 2018 10:45:50 -0700 (PDT)
MIME-Version: 1.0
References: <CAOYVs2rKJMXO806Jp5CpCkH8T80zUHUAauUqdmwEQuTJUhPxnA@mail.gmail.com> <20181029124835.GA7258@ubuntu-dmitri>
In-Reply-To: <20181029124835.GA7258@ubuntu-dmitri>
From: Ian Swett <ianswett@google.com>
Date: Mon, 29 Oct 2018 13:45:38 -0400
Message-ID: <CAKcm_gNkVFOverE9GxhGDwf8xH4tb0rDBt6LqKSXj-z6o4r6aw@mail.gmail.com>
Subject: Re: Using varints to encode the Transport Parameters
To: Marten Seemann <martenseemann@gmail.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c71fb0057961a339"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/y_wNH_NjwKFI_03WRg7RaSVTi6w>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 17:45:54 -0000

--000000000000c71fb0057961a339
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I agree on both of Dmitri's points and if we're going to discuss this in
London, a PR is necessary.

If we were discussing this 6 months ago, I'd be in favor.  If it doesn't
make -17 drafts, I'd say it's QUIC v2.

On Mon, Oct 29, 2018 at 8:48 AM Dmitri Tikhonov <dtikhonov@litespeedtech.co=
m>
wrote:

> I see two problems with this proposal: timing and size.
>
> This is rather late in the game.  If the Working Group is to follow
> the plan Martin Thomson outlined in a recent email, this change would
> have to be included into -17.
>
> A hybrid of the TLS Presentation language and QUIC varints has to be
> specified somewhere itself, thereby increasing the size of the already
> hefty transport document.  This new specification, in turn, is likely
> to engender some debate and further optimization proposals.  Allowed
> to go unchecked, this work would slip our schedule further.
>
> One way to approach this proposal is to have a ready-to-merge PR and
> hum it at the upcoming meeting.
>
>   - Dmitri.
>
> On Mon, Oct 29, 2018 at 06:13:50PM +0700, Marten Seemann wrote:
> > This is based on issue https://github.com/quicwg/base-drafts/issues/160=
8
> .
> >
> > The proposal is to change the encoding of the QUIC Transport Parameters
> > exchanged during the handshake, in order to achieve greater consistency
> > with how QUIC encodes values, and also to save a few bytes.
> >
> > We have a few things that are called transport parameters. This proposa=
l
> > only applies to the TransportParameter struct as defined in section 18
> as:
> > *struct {*
> > *      TransportParameterId parameter;*
> > *      opaque value<0..2^16-1>;*
> > *} TransportParameter;*
> > According to the encoding defined by the TLS spec, every key-value pair
> > will be serialized as:
> > TransportParameterID (2 byte), length (2 byte), value (length byte)
> > where the length of the value is specified for each TransportParameterI=
D.
> >
> > We could switch to varint encoding, as follows:
> >
> > 1. for the TransportParameterID: Since we=E2=80=99re only using the cod=
e points 0
> > to 13, we could save one byte per ID by using a varint.
> > 2. for the length: We would save one more byte, as long as the length o=
f
> > the value is less than 16 byte (which will be the case for all values
> > except the preferred_address).
> > 3. For numeric values: This would apply to the flow control offsets, th=
e
> > maximum stream IDs, the ack delay exponent , the maximum packet size an=
d
> > the max_ack_delay.
> >
> > In addition to the byte-savings of 1. and 2., 3. has some more desirabl=
e
> > properties:
> >     1. It would allow us to encode the whole range of permitted values.
> For
> > example, initial_max_data is a 62-bit value, but the current encoding
> just
> > allows to send 4 bytes.
> >     2. Depending on the value sent, this might or might not save a byte
> > here and there.
> >     3. We=E2=80=99d be consistent with the encoding we use everywhere e=
lse.
>
>

--000000000000c71fb0057961a339
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I agree on both of Dmitri&#39;s points and if we&#39;re go=
ing to discuss this in London, a PR is necessary.<div><br></div><div>If we =
were discussing this 6 months ago, I&#39;d be in favor.=C2=A0 If it doesn&#=
39;t make -17 drafts, I&#39;d say it&#39;s QUIC v2.</div></div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr">On Mon, Oct 29, 2018 at 8:48 AM Dmitri =
Tikhonov &lt;<a href=3D"mailto:dtikhonov@litespeedtech.com" target=3D"_blan=
k">dtikhonov@litespeedtech.com</a>&gt; wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">I see two problems with this proposal: timing and size.<br>
<br>
This is rather late in the game.=C2=A0 If the Working Group is to follow<br=
>
the plan Martin Thomson outlined in a recent email, this change would<br>
have to be included into -17.<br>
<br>
A hybrid of the TLS Presentation language and QUIC varints has to be<br>
specified somewhere itself, thereby increasing the size of the already<br>
hefty transport document.=C2=A0 This new specification, in turn, is likely<=
br>
to engender some debate and further optimization proposals.=C2=A0 Allowed<b=
r>
to go unchecked, this work would slip our schedule further.<br>
<br>
One way to approach this proposal is to have a ready-to-merge PR and<br>
hum it at the upcoming meeting.<br>
<br>
=C2=A0 - Dmitri.<br>
<br>
On Mon, Oct 29, 2018 at 06:13:50PM +0700, Marten Seemann wrote:<br>
&gt; This is based on issue <a href=3D"https://github.com/quicwg/base-draft=
s/issues/1608" rel=3D"noreferrer" target=3D"_blank">https://github.com/quic=
wg/base-drafts/issues/1608</a>.<br>
&gt; <br>
&gt; The proposal is to change the encoding of the QUIC Transport Parameter=
s<br>
&gt; exchanged during the handshake, in order to achieve greater consistenc=
y<br>
&gt; with how QUIC encodes values, and also to save a few bytes.<br>
&gt; <br>
&gt; We have a few things that are called transport parameters. This propos=
al<br>
&gt; only applies to the TransportParameter struct as defined in section 18=
 as:<br>
&gt; *struct {*<br>
&gt; *=C2=A0 =C2=A0 =C2=A0 TransportParameterId parameter;*<br>
&gt; *=C2=A0 =C2=A0 =C2=A0 opaque value&lt;0..2^16-1&gt;;*<br>
&gt; *} TransportParameter;*<br>
&gt; According to the encoding defined by the TLS spec, every key-value pai=
r<br>
&gt; will be serialized as:<br>
&gt; TransportParameterID (2 byte), length (2 byte), value (length byte)<br=
>
&gt; where the length of the value is specified for each TransportParameter=
ID.<br>
&gt; <br>
&gt; We could switch to varint encoding, as follows:<br>
&gt; <br>
&gt; 1. for the TransportParameterID: Since we=E2=80=99re only using the co=
de points 0<br>
&gt; to 13, we could save one byte per ID by using a varint.<br>
&gt; 2. for the length: We would save one more byte, as long as the length =
of<br>
&gt; the value is less than 16 byte (which will be the case for all values<=
br>
&gt; except the preferred_address).<br>
&gt; 3. For numeric values: This would apply to the flow control offsets, t=
he<br>
&gt; maximum stream IDs, the ack delay exponent , the maximum packet size a=
nd<br>
&gt; the max_ack_delay.<br>
&gt; <br>
&gt; In addition to the byte-savings of 1. and 2., 3. has some more desirab=
le<br>
&gt; properties:<br>
&gt;=C2=A0 =C2=A0 =C2=A01. It would allow us to encode the whole range of p=
ermitted values. For<br>
&gt; example, initial_max_data is a 62-bit value, but the current encoding =
just<br>
&gt; allows to send 4 bytes.<br>
&gt;=C2=A0 =C2=A0 =C2=A02. Depending on the value sent, this might or might=
 not save a byte<br>
&gt; here and there.<br>
&gt;=C2=A0 =C2=A0 =C2=A03. We=E2=80=99d be consistent with the encoding we =
use everywhere else.<br>
<br>
</blockquote></div>

--000000000000c71fb0057961a339--


From nobody Mon Oct 29 12:07:17 2018
Return-Path: <jri.ietf@gmail.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 66B1213106E for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 12:07:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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_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=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 MLioOuX3ht7L for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 12:07:14 -0700 (PDT)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 C39171252B7 for <quic@ietf.org>; Mon, 29 Oct 2018 12:07:13 -0700 (PDT)
Received: by mail-lj1-x22f.google.com with SMTP id g8-v6so6036737ljk.1 for <quic@ietf.org>; Mon, 29 Oct 2018 12:07:13 -0700 (PDT)
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=KkcMKQkTO/TMEeIMhLW+3JczhNSEtJlIj4AlYAB5MEA=; b=QL5dL2Ld3TRyDu9nNPqlhkHlRkhblHhmEqZfopSe0nzTXffnJ+dHqqhkoUIbPequ+s yxznM/Fr8jmpV2VahaXt4jQdRgzbL6Zy7MAFs01eEU3XjHvhx1n1IrPhwsWykx0DFDSM 7tAAZ2WxE02BZTiMcPkPPR/m9YkNR9iZfIcnSVXhok9xcQ6RiN9Hv3YUdugJfVwyvy6f ug1QStyva/2m10AsyjEh9qcteaZb3wiKBANDMXufrivWLST72zqEbtyBSLNAvfHta/Vk SIYYdQUqLdMbDDR2SNkfWzyLv7I5pwCeaNF+Lg5fj3RAALASaUqwreVVxH7vaMa1gjOl JEiA==
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=KkcMKQkTO/TMEeIMhLW+3JczhNSEtJlIj4AlYAB5MEA=; b=ESieIbmAonROMC/lrbBAolhWkgQlPqf7oLUOrQEKf4msRxtGCM5AfITc1gj/nM1H7F BRcQERZdkKTpQBMDodBBFt35TVN/T3ierrGez3ehtRs4FXVSRtsBrTrLqarXp5ltoJ6a rxwoNYmsRn58Brkko8plB4T+HZYRYD0nXMgtRA8sft2wQ9PGVJXIFzuujTLU7uUwVNSm I/7Wt9+tpissSgt8vwekEL2F2x1GZhedRWcouV7gVXjv948TDsjmk1N8ytUbRQ4l6v8b CSPVACzKVxL5N7pOB5HLG3YcInhBzKfwdH/WeYOTwMg4dhhwcFApPYP8UG1am2DLhn85 1c8w==
X-Gm-Message-State: AGRZ1gLdCHEyFfh6dT5w34Ekl7SZcH4Di1UAZB6Di9XDMwwUR1Nk6V5B VqDD+k7LfsnE5TcXZ6L8NkV+cAkD+HA+3wvUPEk=
X-Google-Smtp-Source: AJdET5eYDcrBxche6PajNQxLFmwAIxcnWmhbZMmgpsFdWl0efFoYeF12jZ8+PK/9/gsbfVn79yTCkLKzBXKMItRABsw=
X-Received: by 2002:a2e:1456:: with SMTP id 22-v6mr10014389lju.116.1540840031936;  Mon, 29 Oct 2018 12:07:11 -0700 (PDT)
MIME-Version: 1.0
References: <CABkgnnVFqdx4VYbqT7SztPf8Q+vWMV86VkOHY-4aGSpauNPapg@mail.gmail.com> <851_1540819578_5BD70A7A_851_343_1_0ada4f1d-e8c5-25b5-0e8b-8111ee726ae7@orange.com>
In-Reply-To: <851_1540819578_5BD70A7A_851_343_1_0ada4f1d-e8c5-25b5-0e8b-8111ee726ae7@orange.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Mon, 29 Oct 2018 12:07:00 -0700
Message-ID: <CACpbDccoy3GS6sc9OxTcrnswKGA8Tvhvvg_aT6ZqnG4aQ1KSjg@mail.gmail.com>
Subject: Re: Big changes in -17
To: alexandre.ferrieux@orange.com
Cc: Martin Thomson <martin.thomson@gmail.com>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c267ab057962c614"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/eIt1NTQ7-7aN2K3vge5HsasfdoA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 19:07:16 -0000

--000000000000c267ab057962c614
Content-Type: text/plain; charset="UTF-8"

Alexandre,

Are you really asking if an alternative design for the spin-bit(s) can be
proposed now, or am I mis-reading your question?

- jana

On Mon, Oct 29, 2018 at 6:26 AM <alexandre.ferrieux@orange.com> wrote:

> Hello Martin,
>
> On 10/26/2018 01:20 AM, Martin Thomson wrote:
> > 4. The first octet.  We discussed this in NY:
> >
> https://github.com/quicwg/wg-materials/blob/master/interim-18-09/minutes.md#first-octet---martin-thomson
> > and we will have a decision about the spin bit within 2 weeks.  After
> > that, one of the designs discussed will be implemented.
>
> Do I assume correctly that "the designs discussed" are the following three:
>
>   - nothing (no spin bit)
>   - spin bit alone
>   - spin bit + VEC
>
> Or is there room for other (written) proposals ?
>
>
> _________________________________________________________________________________________________________________________
>
> 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.
>
>

--000000000000c267ab057962c614
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Alexandre,<div><br></div><div>Are you really asking if an =
alternative design for the spin-bit(s) can be proposed now, or am I mis-rea=
ding your question?</div><div><br></div><div>- jana</div></div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr">On Mon, Oct 29, 2018 at 6:26 AM &lt;<a =
href=3D"mailto:alexandre.ferrieux@orange.com">alexandre.ferrieux@orange.com=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Martin,<br>
<br>
On 10/26/2018 01:20 AM, Martin Thomson wrote:<br>
&gt; 4. The first octet.=C2=A0 We discussed this in NY:<br>
&gt; <a href=3D"https://github.com/quicwg/wg-materials/blob/master/interim-=
18-09/minutes.md#first-octet---martin-thomson" rel=3D"noreferrer" target=3D=
"_blank">https://github.com/quicwg/wg-materials/blob/master/interim-18-09/m=
inutes.md#first-octet---martin-thomson</a><br>
&gt; and we will have a decision about the spin bit within 2 weeks.=C2=A0 A=
fter<br>
&gt; that, one of the designs discussed will be implemented.<br>
<br>
Do I assume correctly that &quot;the designs discussed&quot; are the follow=
ing three:<br>
<br>
=C2=A0 - nothing (no spin bit)<br>
=C2=A0 - spin bit alone<br>
=C2=A0 - spin bit + VEC<br>
<br>
Or is there room for other (written) proposals ?<br>
<br>
___________________________________________________________________________=
______________________________________________<br>
<br>
Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc<br>
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler<br>
a l&#39;expediteur et le detruire ainsi que les pieces jointes. Les message=
s electroniques etant susceptibles d&#39;alteration,<br>
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.<br>
<br>
This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;<br>
they should not be distributed, used or copied without authorisation.<br>
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.<br>
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.<br>
Thank you.<br>
<br>
</blockquote></div>

--000000000000c267ab057962c614--


From nobody Mon Oct 29 12:37:54 2018
Return-Path: <jri.ietf@gmail.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 AB935131055 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 12:37:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-0.001] 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 6L3oFT8ugDFR for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 12:37:49 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 6F1F41276D0 for <quic@ietf.org>; Mon, 29 Oct 2018 12:37:49 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id z80-v6so2947962ljb.8 for <quic@ietf.org>; Mon, 29 Oct 2018 12:37:49 -0700 (PDT)
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=oWnv9ziz78hANCR6tNxm6N0Eczpj9SPSzQSD/gBvKv0=; b=PuRrtKuEXvyxMhMbPl1DaE+dJUeQwFieNeRLduGmJOgjoS3YT2MWNyBGAcpCweCmd+ EwkipfsvFCvJx2kOwtJ0H03GhT4H/mEtU/mvBqpAwzvcReAsMhugjbt7ULoVE4BCfMoE KPnQt2otrxVYtZoBq9w38pDViswHkemloxBbP46aPjko6nyKruckzEzFN0Q5m7JdL/sR OJoDD92WGZHu0zr+L4o7zlJcdXUjlb24nyKsBS+G1gt9eqlymPi4uPqGN8Piw3OtKaMO UtRn2oSDwLWkP3yMiSysAyz/m9yJxShA7F98HawkRaQ0Jifl1VmKDwmHepxE/skLM6RP gfJg==
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=oWnv9ziz78hANCR6tNxm6N0Eczpj9SPSzQSD/gBvKv0=; b=sF663SBQxusXS/hokLpxtoux3gjtKcLTixdz3ChXt3dYBffLA1twAzzEq7cxZ7L0IF lmxXaMYfxkfxlE07yLf1wEyri9jokesEJQj1VlphHD1ulXpB38myxdNBPHEAaEd5bqe6 Ih8Mu1zRdMSGXWEICNfj1WuQe97/ZHhaFLGJRDxDSvb9m4t3ZnI9lzcrzg8ZtjkCgtkW ATJcpvyaMVjh8UumL/ZB+/lq2u7C/T+KQm4dF3ICUqVB7BurGDr35cdI10s8QC5ZqaVV HZWJwr2XBJSwReoTIqj6fnzkOFrZdrgp58zcYm90AsmMq+112N74yrzHlklNkqEBgICr X0kA==
X-Gm-Message-State: AGRZ1gJBJcGkYG+3TutZyvcTbGH4Y7QE7mWe4HjaZNOrMXz/De1GvcAh LcdbMooJ09LUJ1D01g/EkYETi5dZnsCYWEldw1M=
X-Google-Smtp-Source: AJdET5fGTn7Nv7DkwSKnrQGre8Fo6Tnun97f+sF8+dGkB4v5qizZnQdzaUXIBjTg8PyjilzAuR8Y+F+iHuf8jB56ZE8=
X-Received: by 2002:a2e:5555:: with SMTP id j82-v6mr11468498ljb.69.1540841867384;  Mon, 29 Oct 2018 12:37:47 -0700 (PDT)
MIME-Version: 1.0
References: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com> <CAKcm_gMDOyJC0AwOo2knN6AMxVbySjGsrLvjcC9A8UA9xcvcWw@mail.gmail.com> <19D3595B-8845-45B6-A60D-9E934DD49FAC@apple.com>
In-Reply-To: <19D3595B-8845-45B6-A60D-9E934DD49FAC@apple.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Mon, 29 Oct 2018 12:37:36 -0700
Message-ID: <CACpbDcfk+GXb3aL5LG0wQM87thRGO5Y4Q+9cbXf5YuW1=jWCig@mail.gmail.com>
Subject: Re: flow control and DATAGRAM
To: tpauly@apple.com
Cc: Ian Swett <ianswett@google.com>, Martin Thomson <martin.thomson@gmail.com>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000029209d0579633459"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/WJC41F46I_Oa2Z4aWE1qBG3xX3I>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 19:37:53 -0000

--00000000000029209d0579633459
Content-Type: text/plain; charset="UTF-8"

Tommy,

Changing the semantics of an acknowledgment to include delivery up to the
application is a fundamental change to the QUIC machinery, and it doesn't
work. First, an ACK frame acknowledges packets, and you can't have
different semantics of an acknowledgment for different frames that are
carried in the same packet. Second, it interferes with RTT measurement, and
it conflates flow control with congestion control, which gets messy. (This
conflation is an interesting problem to consider theoretically, but not one
for us at this time IMO.)

I am wondering if applying a stream-level flow control for DATAGRAMs makes
sense instead. Meaning that you treat DATAGRAMs as a separate stream for
flow control purposes. You might benefit from having an offset in the
DATAGRAM frame for this purpose.

- jana

On Mon, Oct 29, 2018 at 8:21 AM Tommy Pauly <tpauly@apple.com> wrote:

> Hi Martin, Ian,
>
> Yes, very good points!
>
> My tendency would be to prefer what Ian's implementation does of passing
> these DATAGRAM frames up immediately to the application. I don't think that
> the acknowledgment needs to indicate that the frame was processed by the
> application, but merely that it has been delivered to the application (that
> is, the application doesn't get to do anything with the frame that can
> influence the acknowledgment).
>
> The current draft indicates that the content of the DATAGRAM frames
> contributes to the limit used for MAX_DATA, and that if that amount is
> reached, the frames are blocked along with STREAM data. I think this works
> fine for the sender, while the receiver gets into the discussion you
> present. On the sender side, reaching MAX_DATA could mean dropping the
> DATAGRAM frames when unable to send more (and sending BLOCKED instead).
> Since the frames are unreliable, they can be dropped in this situation
> without violating the API contract.
>
> On the receiver side, I agree that queuing the DATAGRAM frames to let the
> application drive flow control in the way it does for STREAM frames adds
> complexity and diminishes the utility of the frame and ACKs. However, I can
> imagine taking a fairly simplistic approach in which the data limit is
> automatically increased upon reception of the frame (and the frame is
> immediately passed to the application). This allows the initial_max_data to
> put a cap on the amount of data in a given flight of DATAGRAMS, and allow
> the size of a flight of DATAGRAM frames to be limited by the amount of room
> left over from STREAM data that may be consuming the connection-wide flow
> control.
>
> Perhaps this approach needs a clearer name other than "flow control",
> since it has a somewhat different meaning in effect.
>
> As for ACKs, if we never discard on the receiver side, the ACK is pretty
> useful for detecting if there was network-based packet loss.
>
> Thanks,
> Tommy
>
> On Oct 29, 2018, at 5:32 AM, Ian Swett <ianswett@google.com> wrote:
>
> Good catch Martin, I missed that in the draft as well, and I also think
> it's impossibly with the proposed design.
>
> And yes, I think Martin's proposed solution is likely the only practical
> one.  In my implementation, the frame is passed up to the application
> immediately, so technically QUIC processed it, and it's the application's
> job to decide what to do with it.
>
> On Mon, Oct 29, 2018 at 1:16 AM Martin Thomson <martin.thomson@gmail.com>
> wrote:
>
>> Hi Tommy,
>>
>> Your slides - <
>> https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF103-QUIC-Datagram.pdf
>> >
>> - say that DATAGRAM frames respect connection-level flow control.  I
>> missed that in the draft, and I don't know how they can do that in the
>> face of packet loss, especially when you don't necessarily retransmit
>> lost DATAGRAM frames.
>>
>> For that to work, you would need a bunch more machinery to make the
>> connection-level flow control sync between endpoints in the case that
>> packets are lost.  A disagreement about how much flow control is used
>> causes things to break down badly.  Ian and I discussed this point at
>> the last meeting and quickly agreed that while it might be nice to
>> have flow control for this stuff, the increase in complexity is
>> considerable and (at the time) we thought it wouldn't be worth it.
>>
>> The problem that introduces is that you could end up having too many
>> DATAGRAM frames arrive.  The receiver has to drop something at the
>> point that it can't handle them.  And we say that when you acknowledge
>> something, you processed it.  That's tricky.
>>
>> It might be easier to say that a QUIC acknowledgment for a DATAGRAM
>> frame doesn't mean that it was received and processed by an
>> application.  An endpoint might discard these frames before passing
>> them on to applications if it doesn't have space.  In other words,
>> acknowledgment of DATAGRAM means that QUIC got it, not that the
>> application got it.  Sadly, that means that the QUIC acknowledgment
>> machinery doesn't help the application that uses DATAGRAM all that
>> much.  Also, the lower bound on reliability is 0, which isn't the best
>> thing ever.
>>
>> Hard choices, I know.  I don't have a good design for maintaining
>> connection-level flow control (or any back pressure mechanism with
>> equivalent properties) that doesn't add both complexity and overhead.
>>
>> Cheers,
>> Martin
>>
>>
>

--00000000000029209d0579633459
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Tommy,<div><br></div><div>Changing the semantics of an ack=
nowledgment to include delivery up to the application is a fundamental chan=
ge to the QUIC machinery, and it doesn&#39;t work. First, an ACK frame ackn=
owledges packets, and you can&#39;t have different semantics of an acknowle=
dgment for different frames that are carried in the same packet. Second, it=
 interferes with RTT measurement, and it conflates flow control with conges=
tion control, which gets messy. (This conflation is an interesting problem =
to consider theoretically, but not one for us at this time IMO.)</div><div>=
<br></div><div>I am wondering if applying a stream-level flow control for D=
ATAGRAMs makes sense instead. Meaning that you treat DATAGRAMs as a separat=
e stream for flow control purposes. You might benefit from having an offset=
 in the DATAGRAM frame for this purpose.</div><div><br></div><div>- jana</d=
iv></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Mon, Oct 29, 20=
18 at 8:21 AM Tommy Pauly &lt;<a href=3D"mailto:tpauly@apple.com">tpauly@ap=
ple.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=
=3D"word-wrap:break-word;line-break:after-white-space">Hi Martin, Ian,<div>=
<br></div><div>Yes, very good points!</div><div><br></div><div>My tendency =
would be to prefer what Ian&#39;s implementation does of passing these DATA=
GRAM frames up immediately to the application. I don&#39;t think that the a=
cknowledgment needs to indicate that the frame was processed by the applica=
tion, but merely that it has been delivered to the application (that is, th=
e application doesn&#39;t get to do anything with the frame that can influe=
nce the acknowledgment).</div><div><br></div><div>The current draft indicat=
es that the content of the DATAGRAM frames contributes to the limit used fo=
r=C2=A0MAX_DATA, and that if that amount is reached, the frames are blocked=
 along with STREAM data. I think this works fine for the sender, while the =
receiver gets into the discussion you present. On the sender side, reaching=
 MAX_DATA could mean dropping the DATAGRAM frames when unable to send more =
(and sending BLOCKED instead). Since the frames are unreliable, they can be=
 dropped in this situation without violating the API contract.=C2=A0</div><=
div><br></div><div>On the receiver side, I agree that queuing the DATAGRAM =
frames to let the application drive flow control in the way it does for STR=
EAM frames adds complexity and diminishes the utility of the frame and ACKs=
. However, I can imagine taking a fairly simplistic approach in which the d=
ata limit is automatically increased upon reception of the frame (and the f=
rame is immediately passed to the application). This allows the initial_max=
_data to put a cap on the amount of data in a given flight of DATAGRAMS, an=
d allow the size of a flight of DATAGRAM frames to be limited by the amount=
 of room left over from STREAM data that may be consuming the connection-wi=
de flow control.=C2=A0</div><div><br></div><div>Perhaps this approach needs=
 a clearer name other than &quot;flow control&quot;, since it has a somewha=
t different meaning in effect.</div><div><br></div><div>As for ACKs, if we =
never discard on the receiver side, the ACK is pretty useful for detecting =
if there was network-based packet loss.</div><div><br></div><div>Thanks,</d=
iv><div>Tommy=C2=A0</div><div><div><br><blockquote type=3D"cite"><div>On Oc=
t 29, 2018, at 5:32 AM, Ian Swett &lt;<a href=3D"mailto:ianswett@google.com=
" target=3D"_blank">ianswett@google.com</a>&gt; wrote:</div><br class=3D"m_=
-1061371301160893898Apple-interchange-newline"><div><div dir=3D"ltr">Good c=
atch Martin, I missed that in the draft as well, and I also think it&#39;s =
impossibly with the proposed design.<div><br></div><div>And yes, I think Ma=
rtin&#39;s proposed solution is likely the only practical one.=C2=A0 In my =
implementation, the frame is passed up to the application immediately, so t=
echnically QUIC processed it, and it&#39;s the application&#39;s job to dec=
ide what to do with it.</div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr">On Mon, Oct 29, 2018 at 1:16 AM Martin Thomson &lt;<a href=3D"mail=
to:martin.thomson@gmail.com" target=3D"_blank">martin.thomson@gmail.com</a>=
&gt; wrote:<br></div><blockquote class=3D"gmail_quote">Hi Tommy,<br>
<br>
Your slides - &lt;<a href=3D"https://github.com/quicwg/wg-materials/blob/ma=
ster/ietf103/IETF103-QUIC-Datagram.pdf" rel=3D"noreferrer" target=3D"_blank=
">https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF103-QUIC-D=
atagram.pdf</a>&gt;<br>
- say that DATAGRAM frames respect connection-level flow control.=C2=A0 I<b=
r>
missed that in the draft, and I don&#39;t know how they can do that in the<=
br>
face of packet loss, especially when you don&#39;t necessarily retransmit<b=
r>
lost DATAGRAM frames.<br>
<br>
For that to work, you would need a bunch more machinery to make the<br>
connection-level flow control sync between endpoints in the case that<br>
packets are lost.=C2=A0 A disagreement about how much flow control is used<=
br>
causes things to break down badly.=C2=A0 Ian and I discussed this point at<=
br>
the last meeting and quickly agreed that while it might be nice to<br>
have flow control for this stuff, the increase in complexity is<br>
considerable and (at the time) we thought it wouldn&#39;t be worth it.<br>
<br>
The problem that introduces is that you could end up having too many<br>
DATAGRAM frames arrive.=C2=A0 The receiver has to drop something at the<br>
point that it can&#39;t handle them.=C2=A0 And we say that when you acknowl=
edge<br>
something, you processed it.=C2=A0 That&#39;s tricky.<br>
<br>
It might be easier to say that a QUIC acknowledgment for a DATAGRAM<br>
frame doesn&#39;t mean that it was received and processed by an<br>
application.=C2=A0 An endpoint might discard these frames before passing<br=
>
them on to applications if it doesn&#39;t have space.=C2=A0 In other words,=
<br>
acknowledgment of DATAGRAM means that QUIC got it, not that the<br>
application got it.=C2=A0 Sadly, that means that the QUIC acknowledgment<br=
>
machinery doesn&#39;t help the application that uses DATAGRAM all that<br>
much.=C2=A0 Also, the lower bound on reliability is 0, which isn&#39;t the =
best<br>
thing ever.<br>
<br>
Hard choices, I know.=C2=A0 I don&#39;t have a good design for maintaining<=
br>
connection-level flow control (or any back pressure mechanism with<br>
equivalent properties) that doesn&#39;t add both complexity and overhead.<b=
r>
<br>
Cheers,<br>
Martin<br>
<br>
</blockquote></div>
</div></blockquote></div><br></div></div></blockquote></div>

--00000000000029209d0579633459--


From nobody Mon Oct 29 13:01:36 2018
Return-Path: <tpauly@apple.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 846B1130ECD for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 13:01:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.47
X-Spam-Level: 
X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 vhiDHxEa_mTs for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 13:01:32 -0700 (PDT)
Received: from ma1-aaemail-dr-lapp03.apple.com (ma1-aaemail-dr-lapp03.apple.com [17.171.2.72]) (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 D30C9130F6F for <quic@ietf.org>; Mon, 29 Oct 2018 13:01:31 -0700 (PDT)
Received: from pps.filterd (ma1-aaemail-dr-lapp03.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp03.apple.com (8.16.0.22/8.16.0.22) with SMTP id w9TJvHC5021352; Mon, 29 Oct 2018 13:01:29 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : from : message-id : subject : date : in-reply-to : cc : to : references; s=20180706; bh=LpNJR5Mo3VkoqdBshg9ljI0uofOwrc4v+5Jh0jgzVCg=; b=PO6q5XsjPorjfZ4L+SRD6/8mge2q7KoLK8/RDNAqDo/E5g1Z7q4I3fWc45Jj7oZLQ36R PKRGQYMlSHYHm5E3K5w+lQC50YRSUr2I1oVf0xgGH8BTQXZs6w2tuA+9vubdPLqXrQ4o bmdXfm+hOLMZdJD4MfaZJJ0EExt68j31skR8K79H6IqErcZBjS7yWaIobwNmnhTnsumS gUQjWp6ZKU8cuTRtMBoXGIouOhkMxDBujDetP3UmDzSS6Mn8tRbFhOzT72q3qJMd+/fU GtEnH9NIroeHE5H7c0t9xzRnhqhoYcfrhc87jXVWKHqsRr7LuHH1WHqzPbS1FH5FV7P2 Ng== 
Received: from mr2-mtap-s01.rno.apple.com (mr2-mtap-s01.rno.apple.com [17.179.226.133]) by ma1-aaemail-dr-lapp03.apple.com with ESMTP id 2ncq0y37cy-6 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 29 Oct 2018 13:01:29 -0700
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_gJkFUPO11qiwrXD9uJJ2CA)"
Received: from nwk-mmpp-sz13.apple.com (nwk-mmpp-sz13.apple.com [17.128.115.216]) by mr2-mtap-s01.rno.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPS id <0PHD00FWOMAFP510@mr2-mtap-s01.rno.apple.com>; Mon, 29 Oct 2018 13:01:27 -0700 (PDT)
Received: from process_viserion-daemon.nwk-mmpp-sz13.apple.com by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) id <0PHD00M00MA6XX00@nwk-mmpp-sz13.apple.com>; Mon, 29 Oct 2018 13:01:27 -0700 (PDT)
X-Va-A: 
X-Va-T-CD: a5deab3aa8128cfa8ffecae1f592b6eb
X-Va-E-CD: c49bf73f2750f6e382c68706c9cc0d07
X-Va-R-CD: 22b8f453b4f47490ba2e2176fe96324e
X-Va-CD: 0
X-Va-ID: df0a9287-15bc-4cae-b3d8-b9cf85bc0816
X-V-A: 
X-V-T-CD: aefb07da2fd6938664ce892a3812191f
X-V-E-CD: c49bf73f2750f6e382c68706c9cc0d07
X-V-R-CD: 22b8f453b4f47490ba2e2176fe96324e
X-V-CD: 0
X-V-ID: 58d8199d-69b8-44f1-92a6-540fe23f90fe
Received: from process_milters-daemon.nwk-mmpp-sz13.apple.com by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) id <0PHD00J00M4NVR00@nwk-mmpp-sz13.apple.com>; Mon, 29 Oct 2018 13:01:15 -0700 (PDT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-10-29_12:,, signatures=0
Received: from [17.234.42.146] (unknown [17.234.42.146]) by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPSA id <0PHD006C5MA2LH90@nwk-mmpp-sz13.apple.com>; Mon, 29 Oct 2018 13:01:15 -0700 (PDT)
Sender: tpauly@apple.com
From: Tommy Pauly <tpauly@apple.com>
Message-id: <B7BE2454-2A4D-4323-B0A5-0D73BD4B819F@apple.com>
Subject: Re: flow control and DATAGRAM
Date: Mon, 29 Oct 2018 13:01:11 -0700
In-reply-to: <CACpbDcfk+GXb3aL5LG0wQM87thRGO5Y4Q+9cbXf5YuW1=jWCig@mail.gmail.com>
Cc: Ian Swett <ianswett@google.com>, QUIC WG <quic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>
To: Jana Iyengar <jri.ietf@gmail.com>
References: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com> <CAKcm_gMDOyJC0AwOo2knN6AMxVbySjGsrLvjcC9A8UA9xcvcWw@mail.gmail.com> <19D3595B-8845-45B6-A60D-9E934DD49FAC@apple.com> <CACpbDcfk+GXb3aL5LG0wQM87thRGO5Y4Q+9cbXf5YuW1=jWCig@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.100.36)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-29_12:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/cZTYu6pOphTaA2m1DPczZXOV8c0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 20:01:35 -0000

--Boundary_(ID_gJkFUPO11qiwrXD9uJJ2CA)
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: quoted-printable

Hi Jana,

I'm not suggesting any changes to when the packet gets =
ack'ed=E2=80=94specifically, I was responding to Martin's hypothetical =
of having an ACK to a DATAGRAM frame meaning that the application had =
processed the frame. My impression is that the ACK to a packet =
containing a DATAGRAM frame means:
- The packet made it across the network to the QUIC endpoint on the =
other side
- The QUIC implementation will deliver the DATAGRAM frame to application =
(it won't drop it locally)

Does that make sense?

Having a separate outstanding data limit for the DATAGRAM "stream" is an =
interesting solution to the space. It would then have the nice property =
of not looking like traditional flow control. It could even be measured =
in number of frames, rather than bytes (depending on what the limiting =
factors are).

Thanks,
Tommy

> On Oct 29, 2018, at 12:37 PM, Jana Iyengar <jri.ietf@gmail.com> wrote:
>=20
> Tommy,
>=20
> Changing the semantics of an acknowledgment to include delivery up to =
the application is a fundamental change to the QUIC machinery, and it =
doesn't work. First, an ACK frame acknowledges packets, and you can't =
have different semantics of an acknowledgment for different frames that =
are carried in the same packet. Second, it interferes with RTT =
measurement, and it conflates flow control with congestion control, =
which gets messy. (This conflation is an interesting problem to consider =
theoretically, but not one for us at this time IMO.)
>=20
> I am wondering if applying a stream-level flow control for DATAGRAMs =
makes sense instead. Meaning that you treat DATAGRAMs as a separate =
stream for flow control purposes. You might benefit from having an =
offset in the DATAGRAM frame for this purpose.
>=20
> - jana
>=20
> On Mon, Oct 29, 2018 at 8:21 AM Tommy Pauly <tpauly@apple.com =
<mailto:tpauly@apple.com>> wrote:
> Hi Martin, Ian,
>=20
> Yes, very good points!
>=20
> My tendency would be to prefer what Ian's implementation does of =
passing these DATAGRAM frames up immediately to the application. I don't =
think that the acknowledgment needs to indicate that the frame was =
processed by the application, but merely that it has been delivered to =
the application (that is, the application doesn't get to do anything =
with the frame that can influence the acknowledgment).
>=20
> The current draft indicates that the content of the DATAGRAM frames =
contributes to the limit used for MAX_DATA, and that if that amount is =
reached, the frames are blocked along with STREAM data. I think this =
works fine for the sender, while the receiver gets into the discussion =
you present. On the sender side, reaching MAX_DATA could mean dropping =
the DATAGRAM frames when unable to send more (and sending BLOCKED =
instead). Since the frames are unreliable, they can be dropped in this =
situation without violating the API contract.=20
>=20
> On the receiver side, I agree that queuing the DATAGRAM frames to let =
the application drive flow control in the way it does for STREAM frames =
adds complexity and diminishes the utility of the frame and ACKs.. =
However, I can imagine taking a fairly simplistic approach in which the =
data limit is automatically increased upon reception of the frame (and =
the frame is immediately passed to the application). This allows the =
initial_max_data to put a cap on the amount of data in a given flight of =
DATAGRAMS, and allow the size of a flight of DATAGRAM frames to be =
limited by the amount of room left over from STREAM data that may be =
consuming the connection-wide flow control.=20
>=20
> Perhaps this approach needs a clearer name other than "flow control", =
since it has a somewhat different meaning in effect.
>=20
> As for ACKs, if we never discard on the receiver side, the ACK is =
pretty useful for detecting if there was network-based packet loss.
>=20
> Thanks,
> Tommy=20
>=20
>> On Oct 29, 2018, at 5:32 AM, Ian Swett <ianswett@google.com =
<mailto:ianswett@google.com>> wrote:
>>=20
>> Good catch Martin, I missed that in the draft as well, and I also =
think it's impossibly with the proposed design.
>>=20
>> And yes, I think Martin's proposed solution is likely the only =
practical one.  In my implementation, the frame is passed up to the =
application immediately, so technically QUIC processed it, and it's the =
application's job to decide what to do with it.
>>=20
>> On Mon, Oct 29, 2018 at 1:16 AM Martin Thomson =
<martin.thomson@gmail.com <mailto:martin.thomson@gmail.com>> wrote:
>> Hi Tommy,
>>=20
>> Your slides - =
<https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF103-QUIC-D=
atagram.pdf =
<https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF103-QUIC-D=
atagram.pdf>>
>> - say that DATAGRAM frames respect connection-level flow control.  I
>> missed that in the draft, and I don't know how they can do that in =
the
>> face of packet loss, especially when you don't necessarily retransmit
>> lost DATAGRAM frames.
>>=20
>> For that to work, you would need a bunch more machinery to make the
>> connection-level flow control sync between endpoints in the case that
>> packets are lost.  A disagreement about how much flow control is used
>> causes things to break down badly.  Ian and I discussed this point at
>> the last meeting and quickly agreed that while it might be nice to
>> have flow control for this stuff, the increase in complexity is
>> considerable and (at the time) we thought it wouldn't be worth it.
>>=20
>> The problem that introduces is that you could end up having too many
>> DATAGRAM frames arrive.  The receiver has to drop something at the
>> point that it can't handle them.  And we say that when you =
acknowledge
>> something, you processed it.  That's tricky.
>>=20
>> It might be easier to say that a QUIC acknowledgment for a DATAGRAM
>> frame doesn't mean that it was received and processed by an
>> application.  An endpoint might discard these frames before passing
>> them on to applications if it doesn't have space.  In other words,
>> acknowledgment of DATAGRAM means that QUIC got it, not that the
>> application got it.  Sadly, that means that the QUIC acknowledgment
>> machinery doesn't help the application that uses DATAGRAM all that
>> much.  Also, the lower bound on reliability is 0, which isn't the =
best
>> thing ever.
>>=20
>> Hard choices, I know.  I don't have a good design for maintaining
>> connection-level flow control (or any back pressure mechanism with
>> equivalent properties) that doesn't add both complexity and overhead.
>>=20
>> Cheers,
>> Martin
>>=20
>=20


--Boundary_(ID_gJkFUPO11qiwrXD9uJJ2CA)
Content-type: text/html; charset=utf-8
Content-transfer-encoding: quoted-printable

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Jana,<div class=3D""><br class=3D""></div><div class=3D"">I'm not =
suggesting any changes to when the packet gets ack'ed=E2=80=94specifically=
, I was responding to Martin's hypothetical of having an ACK to a =
DATAGRAM frame meaning that the application had processed the frame. My =
impression is that the ACK to a packet containing a DATAGRAM frame =
means:</div><div class=3D"">- The packet made it across the network to =
the QUIC endpoint on the other side</div><div class=3D"">- The QUIC =
implementation will deliver the DATAGRAM frame to application (it won't =
drop it locally)</div><div class=3D""><br class=3D""></div><div =
class=3D"">Does that make sense?</div><div class=3D""><br =
class=3D""></div><div class=3D"">Having a separate outstanding data =
limit for the DATAGRAM "stream" is an interesting solution to the space. =
It would then have the nice property of not looking like traditional =
flow control. It could even be measured in number of frames, rather than =
bytes (depending on what the limiting factors are).</div><div =
class=3D""><br class=3D""></div><div class=3D"">Thanks,</div><div =
class=3D"">Tommy<br class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Oct 29, 2018, at 12:37 PM, =
Jana Iyengar &lt;<a href=3D"mailto:jri.ietf@gmail.com" =
class=3D"">jri.ietf@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D"">Tommy,<div class=3D""><br class=3D""></div><div =
class=3D"">Changing the semantics of an acknowledgment to include =
delivery up to the application is a fundamental change to the QUIC =
machinery, and it doesn't work. First, an ACK frame acknowledges =
packets, and you can't have different semantics of an acknowledgment for =
different frames that are carried in the same packet. Second, it =
interferes with RTT measurement, and it conflates flow control with =
congestion control, which gets messy. (This conflation is an interesting =
problem to consider theoretically, but not one for us at this time =
IMO.)</div><div class=3D""><br class=3D""></div><div class=3D"">I am =
wondering if applying a stream-level flow control for DATAGRAMs makes =
sense instead. Meaning that you treat DATAGRAMs as a separate stream for =
flow control purposes. You might benefit from having an offset in the =
DATAGRAM frame for this purpose.</div><div class=3D""><br =
class=3D""></div><div class=3D"">- jana</div></div><br class=3D""><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"">On Mon, Oct 29, 2018 =
at 8:21 AM Tommy Pauly &lt;<a href=3D"mailto:tpauly@apple.com" =
class=3D"">tpauly@apple.com</a>&gt; wrote:<br class=3D""></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"><div =
style=3D"word-wrap:break-word;line-break:after-white-space" class=3D"">Hi =
Martin, Ian,<div class=3D""><br class=3D""></div><div class=3D"">Yes, =
very good points!</div><div class=3D""><br class=3D""></div><div =
class=3D"">My tendency would be to prefer what Ian's implementation does =
of passing these DATAGRAM frames up immediately to the application. I =
don't think that the acknowledgment needs to indicate that the frame was =
processed by the application, but merely that it has been delivered to =
the application (that is, the application doesn't get to do anything =
with the frame that can influence the acknowledgment).</div><div =
class=3D""><br class=3D""></div><div class=3D"">The current draft =
indicates that the content of the DATAGRAM frames contributes to the =
limit used for&nbsp;MAX_DATA, and that if that amount is reached, the =
frames are blocked along with STREAM data. I think this works fine for =
the sender, while the receiver gets into the discussion you present. On =
the sender side, reaching MAX_DATA could mean dropping the DATAGRAM =
frames when unable to send more (and sending BLOCKED instead). Since the =
frames are unreliable, they can be dropped in this situation without =
violating the API contract.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">On the receiver side, I agree that =
queuing the DATAGRAM frames to let the application drive flow control in =
the way it does for STREAM frames adds complexity and diminishes the =
utility of the frame and ACKs.. However, I can imagine taking a fairly =
simplistic approach in which the data limit is automatically increased =
upon reception of the frame (and the frame is immediately passed to the =
application). This allows the initial_max_data to put a cap on the =
amount of data in a given flight of DATAGRAMS, and allow the size of a =
flight of DATAGRAM frames to be limited by the amount of room left over =
from STREAM data that may be consuming the connection-wide flow =
control.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">Perhaps this approach needs a clearer name other than "flow =
control", since it has a somewhat different meaning in effect.</div><div =
class=3D""><br class=3D""></div><div class=3D"">As for ACKs, if we never =
discard on the receiver side, the ACK is pretty useful for detecting if =
there was network-based packet loss.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Thanks,</div><div =
class=3D"">Tommy&nbsp;</div><div class=3D""><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Oct =
29, 2018, at 5:32 AM, Ian Swett &lt;<a href=3D"mailto:ianswett@google.com"=
 target=3D"_blank" class=3D"">ianswett@google.com</a>&gt; =
wrote:</div><br =
class=3D"m_-1061371301160893898Apple-interchange-newline"><div =
class=3D""><div dir=3D"ltr" class=3D"">Good catch Martin, I missed that =
in the draft as well, and I also think it's impossibly with the proposed =
design.<div class=3D""><br class=3D""></div><div class=3D"">And yes, I =
think Martin's proposed solution is likely the only practical one.&nbsp; =
In my implementation, the frame is passed up to the application =
immediately, so technically QUIC processed it, and it's the =
application's job to decide what to do with it.</div></div><br =
class=3D""><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"">On =
Mon, Oct 29, 2018 at 1:16 AM Martin Thomson &lt;<a =
href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank" =
class=3D"">martin.thomson@gmail.com</a>&gt; wrote:<br =
class=3D""></div><blockquote class=3D"gmail_quote">Hi Tommy,<br =
class=3D"">
<br class=3D"">
Your slides - &lt;<a =
href=3D"https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF103=
-QUIC-Datagram.pdf" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF=
103-QUIC-Datagram.pdf</a>&gt;<br class=3D"">
- say that DATAGRAM frames respect connection-level flow control.&nbsp; =
I<br class=3D"">
missed that in the draft, and I don't know how they can do that in =
the<br class=3D"">
face of packet loss, especially when you don't necessarily retransmit<br =
class=3D"">
lost DATAGRAM frames.<br class=3D"">
<br class=3D"">
For that to work, you would need a bunch more machinery to make the<br =
class=3D"">
connection-level flow control sync between endpoints in the case that<br =
class=3D"">
packets are lost.&nbsp; A disagreement about how much flow control is =
used<br class=3D"">
causes things to break down badly.&nbsp; Ian and I discussed this point =
at<br class=3D"">
the last meeting and quickly agreed that while it might be nice to<br =
class=3D"">
have flow control for this stuff, the increase in complexity is<br =
class=3D"">
considerable and (at the time) we thought it wouldn't be worth it.<br =
class=3D"">
<br class=3D"">
The problem that introduces is that you could end up having too many<br =
class=3D"">
DATAGRAM frames arrive.&nbsp; The receiver has to drop something at =
the<br class=3D"">
point that it can't handle them.&nbsp; And we say that when you =
acknowledge<br class=3D"">
something, you processed it.&nbsp; That's tricky.<br class=3D"">
<br class=3D"">
It might be easier to say that a QUIC acknowledgment for a DATAGRAM<br =
class=3D"">
frame doesn't mean that it was received and processed by an<br class=3D"">=

application.&nbsp; An endpoint might discard these frames before =
passing<br class=3D"">
them on to applications if it doesn't have space.&nbsp; In other =
words,<br class=3D"">
acknowledgment of DATAGRAM means that QUIC got it, not that the<br =
class=3D"">
application got it.&nbsp; Sadly, that means that the QUIC =
acknowledgment<br class=3D"">
machinery doesn't help the application that uses DATAGRAM all that<br =
class=3D"">
much.&nbsp; Also, the lower bound on reliability is 0, which isn't the =
best<br class=3D"">
thing ever.<br class=3D"">
<br class=3D"">
Hard choices, I know.&nbsp; I don't have a good design for =
maintaining<br class=3D"">
connection-level flow control (or any back pressure mechanism with<br =
class=3D"">
equivalent properties) that doesn't add both complexity and overhead.<br =
class=3D"">
<br class=3D"">
Cheers,<br class=3D"">
Martin<br class=3D"">
<br class=3D"">
</blockquote></div>
</div></blockquote></div><br class=3D""></div></div></blockquote></div>
</div></blockquote></div><br class=3D""></div></body></html>=

--Boundary_(ID_gJkFUPO11qiwrXD9uJJ2CA)--


From nobody Mon Oct 29 13:06:51 2018
Return-Path: <alexandre.ferrieux@orange.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 0729F130F6F for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 13:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.289
X-Spam-Level: 
X-Spam-Status: No, score=-0.289 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 it_-dOmydlTE for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 13:06:48 -0700 (PDT)
Received: from orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C978130ECD for <quic@ietf.org>; Mon, 29 Oct 2018 13:06:48 -0700 (PDT)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 42kQbp40VXz5wN6; Mon, 29 Oct 2018 21:06:46 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 42kQbp35xQzFpWV; Mon, 29 Oct 2018 21:06:46 +0100 (CET)
Received: from [10.193.4.89] (10.168.234.4) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 29 Oct 2018 21:06:45 +0100
Subject: Re: Big changes in -17
To: Jana Iyengar <jri.ietf@gmail.com>
CC: QUIC WG <quic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>
References: <CABkgnnVFqdx4VYbqT7SztPf8Q+vWMV86VkOHY-4aGSpauNPapg@mail.gmail.com> <851_1540819578_5BD70A7A_851_343_1_0ada4f1d-e8c5-25b5-0e8b-8111ee726ae7@orange.com> <CACpbDccoy3GS6sc9OxTcrnswKGA8Tvhvvg_aT6ZqnG4aQ1KSjg@mail.gmail.com>
From: <alexandre.ferrieux@orange.com>
Message-ID: <3676_1540843606_5BD76856_3676_474_1_a7961fe6-2444-a899-0729-1cbc310061dc@orange.com>
Date: Mon, 29 Oct 2018 21:06:46 +0100
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CACpbDccoy3GS6sc9OxTcrnswKGA8Tvhvvg_aT6ZqnG4aQ1KSjg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------BDCF3EDA81579175188F9222"
Content-Language: fr-xx-moderne
X-Originating-IP: [10.168.234.4]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/nO21JHp5Oqs3feUiU0ClYh1Xu48>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 20:06:50 -0000

--------------BDCF3EDA81579175188F9222
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: quoted-printable

I was merely trying to clarify what the plural ("designs") meant, given tha=
t in=20
NYC it was made clear that nothing but the single spin bit had undergone en=
ough=20
privacy analysis (not even the VEC).

On 10/29/2018 08:07 PM, Jana Iyengar wrote:
> Alexandre,
>
> Are you really asking if an alternative design for the spin-bit(s) can be=
=20
> proposed now, or am I mis-reading your question?
>
> - jana
>
> On Mon, Oct 29, 2018 at 6:26 AM <alexandre.ferrieux@orange.com=20
> <mailto:alexandre.ferrieux@orange.com>> wrote:
>
>     Hello Martin,
>
>     On 10/26/2018 01:20 AM, Martin Thomson wrote:
>     > 4. The first octet.=C2=A0 We discussed this in NY:
>     >
>     https://github.com/quicwg/wg-materials/blob/master/interim-18-09/minu=
tes.md#first-octet---martin-thomson
>     > and we will have a decision about the spin bit within 2 weeks.=C2=
=A0 After
>     > that, one of the designs discussed will be implemented.
>
>     Do I assume correctly that "the designs discussed" are the following =
three:
>
>     =C2=A0 - nothing (no spin bit)
>     =C2=A0 - spin bit alone
>     =C2=A0 - spin bit + VEC
>
>     Or is there room for other (written) proposals ?
>
>     _____________________________________________________________________=
____________________________________________________
>
>     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 messa=
ges
>     electroniques etant susceptibles d'alteration,
>     Orange decline toute responsabilite si ce message a ete altere, defor=
me ou
>     falsifie. Merci.
>
>     This message and its attachments may contain confidential or privileg=
ed
>     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 confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


--------------BDCF3EDA81579175188F9222
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8=
">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div class=3D"moz-cite-prefix">I was merely trying to clarify what the
      plural ("designs") meant, given that in NYC it was made clear that
      nothing but the single spin bit had undergone enough privacy
      analysis (not even the VEC).<br>
      <br>
      On 10/29/2018 08:07 PM, Jana Iyengar wrote:<br>
    </div>
    <blockquote type=3D"cite"
cite=3D"mid:CACpbDccoy3GS6sc9OxTcrnswKGA8Tvhvvg_aT6ZqnG4aQ1KSjg@mail.gmail.=
com">
      <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf=
-8">
      <div dir=3D"ltr">Alexandre,
        <div><br>
        </div>
        <div>Are you really asking if an alternative design for the
          spin-bit(s) can be proposed now, or am I mis-reading your
          question?</div>
        <div><br>
        </div>
        <div>- jana</div>
      </div>
      <br>
      <div class=3D"gmail_quote">
        <div dir=3D"ltr">On Mon, Oct 29, 2018 at 6:26 AM &lt;<a
            href=3D"mailto:alexandre.ferrieux@orange.com"
            moz-do-not-send=3D"true">alexandre.ferrieux@orange.com</a>&gt;
          wrote:<br>
        </div>
        <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello
          Martin,<br>
          <br>
          On 10/26/2018 01:20 AM, Martin Thomson wrote:<br>
          &gt; 4. The first octet.=C2=A0 We discussed this in NY:<br>
          &gt; <a
href=3D"https://github.com/quicwg/wg-materials/blob/master/interim-18-09/mi=
nutes.md#first-octet---martin-thomson"
            rel=3D"noreferrer" target=3D"_blank" moz-do-not-send=3D"true">h=
ttps://github.com/quicwg/wg-materials/blob/master/interim-18-09/minutes.md#=
first-octet---martin-thomson</a><br>
          &gt; and we will have a decision about the spin bit within 2
          weeks.=C2=A0 After<br>
          &gt; that, one of the designs discussed will be implemented.<br>
          <br>
          Do I assume correctly that "the designs discussed" are the
          following three:<br>
          <br>
          =C2=A0 - nothing (no spin bit)<br>
          =C2=A0 - spin bit alone<br>
          =C2=A0 - spin bit + VEC<br>
          <br>
          Or is there room for other (written) proposals ?<br>
          <br>
___________________________________________________________________________=
______________________________________________<br>
          <br>
          Ce message et ses pieces jointes peuvent contenir des
          informations confidentielles ou privilegiees et ne doivent
          donc<br>
          pas etre diffuses, exploites ou copies sans autorisation. Si
          vous avez recu ce message par erreur, veuillez le signaler<br>
          a l'expediteur et le detruire ainsi que les pieces jointes.
          Les messages electroniques etant susceptibles d'alteration,<br>
          Orange decline toute responsabilite si ce message a ete
          altere, deforme ou falsifie. Merci.<br>
          <br>
          This message and its attachments may contain confidential or
          privileged information that may be protected by law;<br>
          they should not be distributed, used or copied without
          authorisation.<br>
          If you have received this email in error, please notify the
          sender and delete this message and its attachments.<br>
          As emails may be altered, Orange is not liable for messages
          that have been modified, changed or falsified.<br>
          Thank you.<br>
          <br>
        </blockquote>
      </div>
    </blockquote>
    <p><br>
    </p>
  <PRE>____________________________________________________________________=
_____________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.
</PRE></body>
</html>

--------------BDCF3EDA81579175188F9222--


From nobody Mon Oct 29 14:28:58 2018
Return-Path: <ilubashe@akamai.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 AFC17131052 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 14:28:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.819
X-Spam-Level: 
X-Spam-Status: No, score=0.819 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, KHOP_DYNAMIC=1.999, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 HrUJ4IG6Vkiv for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 14:28:54 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 E7C84131028 for <quic@ietf.org>; Mon, 29 Oct 2018 14:28:53 -0700 (PDT)
Received: from pps.filterd (m0050093.ppops.net [127.0.0.1]) by m0050093.ppops.net-00190b01. (8.16.0.23/8.16.0.23) with SMTP id w9TLMuq3012531; Mon, 29 Oct 2018 21:28:48 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=NhibOhV54fYx9t969cgU1WvacBUKUNgTa5bqBedxjyo=; b=Iw6apNtiYuCBrXSqMPTricsR7ZW37MU1+ZbwFcQa2DAiCndbReqB8ht+B5zK6d4V57rK OzD8ZGRRuKiQmbiuqZI4l6ct0VV/Wua4jjZnDXLw+YXb+GfGucBJSeJR14omEk8vqGFp Zdb0KF99kW2lqnWS/FThgp/TXAwNcQo22As+fnTbjE9eM7iaNiHDwLf2aQ6X/z2KjRJG j5ipFhfTD0s3uXsifbDgGHsjFMXB/sy2pFZH1QEiVz1MkA6r6ps8IIiyZsaC9+TKaY8/ FEgSGGKN8H0iFHfg9Kk0vEGj5XYvr0Sim2IAuwxOZdkfiISFLuh6Z0AQsIObALqfHAA0 uA== 
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19]) by m0050093.ppops.net-00190b01. with ESMTP id 2ncf9mbm1c-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 29 Oct 2018 21:28:48 +0000
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w9TLJbvv014673; Mon, 29 Oct 2018 17:28:44 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.30]) by prod-mail-ppoint2.akamai.com with ESMTP id 2nckcaj58k-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 29 Oct 2018 17:28:43 -0400
Received: from usma1ex-dag1mb6.msg.corp.akamai.com (172.27.123.65) by usma1ex-dag1mb1.msg.corp.akamai.com (172.27.123.101) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Mon, 29 Oct 2018 17:28:45 -0400
Received: from usma1ex-dag1mb6.msg.corp.akamai.com ([172.27.123.65]) by usma1ex-dag1mb6.msg.corp.akamai.com ([172.27.123.65]) with mapi id 15.00.1365.000; Mon, 29 Oct 2018 17:28:45 -0400
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Tommy Pauly <tpauly@apple.com>, Jana Iyengar <jri.ietf@gmail.com>
CC: Ian Swett <ianswett@google.com>, QUIC WG <quic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>
Subject: RE: flow control and DATAGRAM
Thread-Topic: flow control and DATAGRAM
Thread-Index: AQHUb0aOcr0oK2RjxUS//IweRKrnD6U2a2QAgAAvQ4CAAEeKAIAABpaA///KoZA=
Date: Mon, 29 Oct 2018 21:28:45 +0000
Message-ID: <344a8a30b95441af988b675c2f887965@usma1ex-dag1mb6.msg.corp.akamai.com>
References: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com> <CAKcm_gMDOyJC0AwOo2knN6AMxVbySjGsrLvjcC9A8UA9xcvcWw@mail.gmail.com> <19D3595B-8845-45B6-A60D-9E934DD49FAC@apple.com> <CACpbDcfk+GXb3aL5LG0wQM87thRGO5Y4Q+9cbXf5YuW1=jWCig@mail.gmail.com> <B7BE2454-2A4D-4323-B0A5-0D73BD4B819F@apple.com>
In-Reply-To: <B7BE2454-2A4D-4323-B0A5-0D73BD4B819F@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.38.233]
Content-Type: multipart/alternative; boundary="_000_344a8a30b95441af988b675c2f887965usma1exdag1mb6msgcorpak_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-29_12:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810290191
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-29_12:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810290191
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/L0hWOo2V5t5gJAiWRK-jDw7vCzo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 21:28:57 -0000

--_000_344a8a30b95441af988b675c2f887965usma1exdag1mb6msgcorpak_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

PiBBQ0sgdG8gYSBwYWNrZXQgY29udGFpbmluZyBhIERBVEFHUkFNIGZyYW1lIG1lYW5zOg0KPiAt
IFRoZSBwYWNrZXQgbWFkZSBpdCBhY3Jvc3MgdGhlIG5ldHdvcmsgdG8gdGhlIFFVSUMgZW5kcG9p
bnQgb24gdGhlIG90aGVyIHNpZGUNCj4gLSBUaGUgUVVJQyBpbXBsZW1lbnRhdGlvbiB3aWxsIGRl
bGl2ZXIgdGhlIERBVEFHUkFNIGZyYW1lIHRvIGFwcGxpY2F0aW9uIChpdCB3b24ndCBkcm9wIGl0
IGxvY2FsbHkpDQo+DQo+IERvZXMgdGhhdCBtYWtlIHNlbnNlPw0KDQpUaGlzIG9ubHkgbWFrZXMg
c2Vuc2UsIGlmIHRoZXJlIGlzIGFuIGVmZmVjdGl2ZSBmbG93IGNvbnRyb2wgZm9yIERBVEFHUkFN
cy4gIFRoZSBzcGVjIHNob3VsZCBiZSBpbXBsZW1lbnRhYmxlIGJ5IHBvbGwvcmVhZCBRVUlDIGlt
cGxlbWVudGF0aW9ucyBhcyB3ZWxsIGFzIGJ5IGNhbGxiYWNrLW9uLW5ldHdvcmstcmVjZWl2ZS10
aHJlYWQgaW1wbGVtZW50YXRpb25zLiAgVW5sZXNzIHRoZXJlIGlzIGFuIGVmZmVjdGl2ZSBmbG93
IGNvbnRyb2wsIGEgYnVmZmVyaW5nIFFVSUMgaW1wbGVtZW50YXRpb24gbXVzdCBiZSBhYmxlIHRv
IGRpc2NhcmQgREFUQUdSQU1zLCBpZiB0aGUgcmVjZWl2ZXIgYXBwIGlzIG5vdCBjYXRjaGluZyB1
cC4gIFRoZSByZWNlaXZlciB3b3VsZCB0aGVuIGhhdmUgdG8gaWdub3JlIGFsbCBub24tREFUQUdS
QU0gZnJhbWVzIGluIHRoYXQgcGFja2V0LCBzaW5jZSBpdCB3b3VsZCBiZSB1bmFibGUgdG8gQUNL
IHRoZSBwYWNrZXQuICBJZiB0aGUgcmVjZWl2ZXIgaXMgcHJvY2Vzc2luZyBEQVRBR1JBTXMgYW5k
IFNUUkVBTXMgYXQgZGlmZmVyZW50IHNwZWVkcywgZGVsaWJlcmF0ZSBkaXNjYXJkcyBvZiBwYWNr
ZXRzIGNvbnRhaW5pbmcgREFUQUdSQU1zIHdvdWxkIGludGVyZmVyZSB3aXRoIHRoZSBjb25nZXN0
aW9uIGNvbnRyb2wsIGVmZmVjdGl2ZWx5IEhPTCBibG9ja2luZyBTVFJFQU1zLg0KDQpBbiBlZmZl
Y3RpdmUgZmxvdyBjb250cm9sIHJlcXVpcmVzIHNlbmRlciBhbmQgcmVjZWl2ZXIgdG8gc3luY2hy
b25pemUgdGhlaXIgdmlldyBvZiB0aGUgZmxvdyBjb250cm9sIGNvdW50ZXIgKE1BWF9EQVRBIGZv
ciBjb25uZWN0aW9uIGZsb3cgY29udHJvbCkuICBSZWx5aW5nIG9uIEFDS3MgaXMgdmVyeSBoYXJk
LCBzaW5jZSB0aGUgcmVjZWl2ZXIgY2Fubm90IGtub3cgaG93IG11Y2ggZGF0YSB0aGUgc2VuZGVy
IGhhcyBzZW50ICh1bmxlc3MgdGhlIHNlbmRlciBpcyBleHBsaWNpdCBhYm91dCBpdCkuDQoNCklm
IGZsb3cgY29udHJvbCBmb3IgREFUQUdSQU1zIGlzIGRlc2lyZWQsIHlvdSBjYW4gdXNlIG1lY2hh
bmljcyBzdWNoIGFzIGluIGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1sdWJhc2hl
di1xdWljLXBhcnRpYWwtcmVsaWFiaWxpdHktMDIgb3IgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9o
dG1sL2RyYWZ0LWx1YmFzaGV2LXF1aWMtcGFydGlhbC1yZWxpYWJpbGl0eS0wMyAoaHR0cHM6Ly9n
aXRodWIuY29tL2lnb3Jsb3JkL2RyYWZ0LWx1YmFzaGV2LXF1aWMtcGFydGlhbC1yZWxpYWJpbGl0
eSkuICAoVGhpcyB3b3VsZCBiZSB0cmVhdGluZyBEQVRBR1JBTXMgYXMgYmVsb25naW5nIHRvIGEg
cGFydGlhbGx5IHJlbGlhYmxlIHN0cmVhbSwgb3Igc3RyZWFtcy4gIEV4Y2VwdCB5b3Ugd291bGQg
bm90IG5lZWQgdG8gZW5zdXJlIG9yZGVyaW5nIG9mIERBVEFHUkFNcyBpbiB0aGF0IHN0cmVhbS4p
DQoNCg0KICAqICAgSWdvcg0KDQoNCkZyb206IFRvbW15IFBhdWx5IDx0cGF1bHlAYXBwbGUuY29t
Pg0KU2VudDogTW9uZGF5LCBPY3RvYmVyIDI5LCAyMDE4IDQ6MDEgUE0NClRvOiBKYW5hIEl5ZW5n
YXIgPGpyaS5pZXRmQGdtYWlsLmNvbT4NCkNjOiBJYW4gU3dldHQgPGlhbnN3ZXR0QGdvb2dsZS5j
b20+OyBRVUlDIFdHIDxxdWljQGlldGYub3JnPjsgTWFydGluIFRob21zb24gPG1hcnRpbi50aG9t
c29uQGdtYWlsLmNvbT4NClN1YmplY3Q6IFJlOiBmbG93IGNvbnRyb2wgYW5kIERBVEFHUkFNDQoN
CkhpIEphbmEsDQoNCkknbSBub3Qgc3VnZ2VzdGluZyBhbnkgY2hhbmdlcyB0byB3aGVuIHRoZSBw
YWNrZXQgZ2V0cyBhY2snZWTigJRzcGVjaWZpY2FsbHksIEkgd2FzIHJlc3BvbmRpbmcgdG8gTWFy
dGluJ3MgaHlwb3RoZXRpY2FsIG9mIGhhdmluZyBhbiBBQ0sgdG8gYSBEQVRBR1JBTSBmcmFtZSBt
ZWFuaW5nIHRoYXQgdGhlIGFwcGxpY2F0aW9uIGhhZCBwcm9jZXNzZWQgdGhlIGZyYW1lLiBNeSBp
bXByZXNzaW9uIGlzIHRoYXQgdGhlIEFDSyB0byBhIHBhY2tldCBjb250YWluaW5nIGEgREFUQUdS
QU0gZnJhbWUgbWVhbnM6DQotIFRoZSBwYWNrZXQgbWFkZSBpdCBhY3Jvc3MgdGhlIG5ldHdvcmsg
dG8gdGhlIFFVSUMgZW5kcG9pbnQgb24gdGhlIG90aGVyIHNpZGUNCi0gVGhlIFFVSUMgaW1wbGVt
ZW50YXRpb24gd2lsbCBkZWxpdmVyIHRoZSBEQVRBR1JBTSBmcmFtZSB0byBhcHBsaWNhdGlvbiAo
aXQgd29uJ3QgZHJvcCBpdCBsb2NhbGx5KQ0KDQpEb2VzIHRoYXQgbWFrZSBzZW5zZT8NCg0KSGF2
aW5nIGEgc2VwYXJhdGUgb3V0c3RhbmRpbmcgZGF0YSBsaW1pdCBmb3IgdGhlIERBVEFHUkFNICJz
dHJlYW0iIGlzIGFuIGludGVyZXN0aW5nIHNvbHV0aW9uIHRvIHRoZSBzcGFjZS4gSXQgd291bGQg
dGhlbiBoYXZlIHRoZSBuaWNlIHByb3BlcnR5IG9mIG5vdCBsb29raW5nIGxpa2UgdHJhZGl0aW9u
YWwgZmxvdyBjb250cm9sLiBJdCBjb3VsZCBldmVuIGJlIG1lYXN1cmVkIGluIG51bWJlciBvZiBm
cmFtZXMsIHJhdGhlciB0aGFuIGJ5dGVzIChkZXBlbmRpbmcgb24gd2hhdCB0aGUgbGltaXRpbmcg
ZmFjdG9ycyBhcmUpLg0KDQpUaGFua3MsDQpUb21teQ0KDQoNCk9uIE9jdCAyOSwgMjAxOCwgYXQg
MTI6MzcgUE0sIEphbmEgSXllbmdhciA8anJpLmlldGZAZ21haWwuY29tPG1haWx0bzpqcmkuaWV0
ZkBnbWFpbC5jb20+PiB3cm90ZToNCg0KVG9tbXksDQoNCkNoYW5naW5nIHRoZSBzZW1hbnRpY3Mg
b2YgYW4gYWNrbm93bGVkZ21lbnQgdG8gaW5jbHVkZSBkZWxpdmVyeSB1cCB0byB0aGUgYXBwbGlj
YXRpb24gaXMgYSBmdW5kYW1lbnRhbCBjaGFuZ2UgdG8gdGhlIFFVSUMgbWFjaGluZXJ5LCBhbmQg
aXQgZG9lc24ndCB3b3JrLiBGaXJzdCwgYW4gQUNLIGZyYW1lIGFja25vd2xlZGdlcyBwYWNrZXRz
LCBhbmQgeW91IGNhbid0IGhhdmUgZGlmZmVyZW50IHNlbWFudGljcyBvZiBhbiBhY2tub3dsZWRn
bWVudCBmb3IgZGlmZmVyZW50IGZyYW1lcyB0aGF0IGFyZSBjYXJyaWVkIGluIHRoZSBzYW1lIHBh
Y2tldC4gU2Vjb25kLCBpdCBpbnRlcmZlcmVzIHdpdGggUlRUIG1lYXN1cmVtZW50LCBhbmQgaXQg
Y29uZmxhdGVzIGZsb3cgY29udHJvbCB3aXRoIGNvbmdlc3Rpb24gY29udHJvbCwgd2hpY2ggZ2V0
cyBtZXNzeS4gKFRoaXMgY29uZmxhdGlvbiBpcyBhbiBpbnRlcmVzdGluZyBwcm9ibGVtIHRvIGNv
bnNpZGVyIHRoZW9yZXRpY2FsbHksIGJ1dCBub3Qgb25lIGZvciB1cyBhdCB0aGlzIHRpbWUgSU1P
LikNCg0KSSBhbSB3b25kZXJpbmcgaWYgYXBwbHlpbmcgYSBzdHJlYW0tbGV2ZWwgZmxvdyBjb250
cm9sIGZvciBEQVRBR1JBTXMgbWFrZXMgc2Vuc2UgaW5zdGVhZC4gTWVhbmluZyB0aGF0IHlvdSB0
cmVhdCBEQVRBR1JBTXMgYXMgYSBzZXBhcmF0ZSBzdHJlYW0gZm9yIGZsb3cgY29udHJvbCBwdXJw
b3Nlcy4gWW91IG1pZ2h0IGJlbmVmaXQgZnJvbSBoYXZpbmcgYW4gb2Zmc2V0IGluIHRoZSBEQVRB
R1JBTSBmcmFtZSBmb3IgdGhpcyBwdXJwb3NlLg0KDQotIGphbmENCg0KT24gTW9uLCBPY3QgMjks
IDIwMTggYXQgODoyMSBBTSBUb21teSBQYXVseSA8dHBhdWx5QGFwcGxlLmNvbTxtYWlsdG86dHBh
dWx5QGFwcGxlLmNvbT4+IHdyb3RlOg0KSGkgTWFydGluLCBJYW4sDQoNClllcywgdmVyeSBnb29k
IHBvaW50cyENCg0KTXkgdGVuZGVuY3kgd291bGQgYmUgdG8gcHJlZmVyIHdoYXQgSWFuJ3MgaW1w
bGVtZW50YXRpb24gZG9lcyBvZiBwYXNzaW5nIHRoZXNlIERBVEFHUkFNIGZyYW1lcyB1cCBpbW1l
ZGlhdGVseSB0byB0aGUgYXBwbGljYXRpb24uIEkgZG9uJ3QgdGhpbmsgdGhhdCB0aGUgYWNrbm93
bGVkZ21lbnQgbmVlZHMgdG8gaW5kaWNhdGUgdGhhdCB0aGUgZnJhbWUgd2FzIHByb2Nlc3NlZCBi
eSB0aGUgYXBwbGljYXRpb24sIGJ1dCBtZXJlbHkgdGhhdCBpdCBoYXMgYmVlbiBkZWxpdmVyZWQg
dG8gdGhlIGFwcGxpY2F0aW9uICh0aGF0IGlzLCB0aGUgYXBwbGljYXRpb24gZG9lc24ndCBnZXQg
dG8gZG8gYW55dGhpbmcgd2l0aCB0aGUgZnJhbWUgdGhhdCBjYW4gaW5mbHVlbmNlIHRoZSBhY2tu
b3dsZWRnbWVudCkuDQoNClRoZSBjdXJyZW50IGRyYWZ0IGluZGljYXRlcyB0aGF0IHRoZSBjb250
ZW50IG9mIHRoZSBEQVRBR1JBTSBmcmFtZXMgY29udHJpYnV0ZXMgdG8gdGhlIGxpbWl0IHVzZWQg
Zm9yIE1BWF9EQVRBLCBhbmQgdGhhdCBpZiB0aGF0IGFtb3VudCBpcyByZWFjaGVkLCB0aGUgZnJh
bWVzIGFyZSBibG9ja2VkIGFsb25nIHdpdGggU1RSRUFNIGRhdGEuIEkgdGhpbmsgdGhpcyB3b3Jr
cyBmaW5lIGZvciB0aGUgc2VuZGVyLCB3aGlsZSB0aGUgcmVjZWl2ZXIgZ2V0cyBpbnRvIHRoZSBk
aXNjdXNzaW9uIHlvdSBwcmVzZW50LiBPbiB0aGUgc2VuZGVyIHNpZGUsIHJlYWNoaW5nIE1BWF9E
QVRBIGNvdWxkIG1lYW4gZHJvcHBpbmcgdGhlIERBVEFHUkFNIGZyYW1lcyB3aGVuIHVuYWJsZSB0
byBzZW5kIG1vcmUgKGFuZCBzZW5kaW5nIEJMT0NLRUQgaW5zdGVhZCkuIFNpbmNlIHRoZSBmcmFt
ZXMgYXJlIHVucmVsaWFibGUsIHRoZXkgY2FuIGJlIGRyb3BwZWQgaW4gdGhpcyBzaXR1YXRpb24g
d2l0aG91dCB2aW9sYXRpbmcgdGhlIEFQSSBjb250cmFjdC4NCg0KT24gdGhlIHJlY2VpdmVyIHNp
ZGUsIEkgYWdyZWUgdGhhdCBxdWV1aW5nIHRoZSBEQVRBR1JBTSBmcmFtZXMgdG8gbGV0IHRoZSBh
cHBsaWNhdGlvbiBkcml2ZSBmbG93IGNvbnRyb2wgaW4gdGhlIHdheSBpdCBkb2VzIGZvciBTVFJF
QU0gZnJhbWVzIGFkZHMgY29tcGxleGl0eSBhbmQgZGltaW5pc2hlcyB0aGUgdXRpbGl0eSBvZiB0
aGUgZnJhbWUgYW5kIEFDS3MuLiBIb3dldmVyLCBJIGNhbiBpbWFnaW5lIHRha2luZyBhIGZhaXJs
eSBzaW1wbGlzdGljIGFwcHJvYWNoIGluIHdoaWNoIHRoZSBkYXRhIGxpbWl0IGlzIGF1dG9tYXRp
Y2FsbHkgaW5jcmVhc2VkIHVwb24gcmVjZXB0aW9uIG9mIHRoZSBmcmFtZSAoYW5kIHRoZSBmcmFt
ZSBpcyBpbW1lZGlhdGVseSBwYXNzZWQgdG8gdGhlIGFwcGxpY2F0aW9uKS4gVGhpcyBhbGxvd3Mg
dGhlIGluaXRpYWxfbWF4X2RhdGEgdG8gcHV0IGEgY2FwIG9uIHRoZSBhbW91bnQgb2YgZGF0YSBp
biBhIGdpdmVuIGZsaWdodCBvZiBEQVRBR1JBTVMsIGFuZCBhbGxvdyB0aGUgc2l6ZSBvZiBhIGZs
aWdodCBvZiBEQVRBR1JBTSBmcmFtZXMgdG8gYmUgbGltaXRlZCBieSB0aGUgYW1vdW50IG9mIHJv
b20gbGVmdCBvdmVyIGZyb20gU1RSRUFNIGRhdGEgdGhhdCBtYXkgYmUgY29uc3VtaW5nIHRoZSBj
b25uZWN0aW9uLXdpZGUgZmxvdyBjb250cm9sLg0KDQpQZXJoYXBzIHRoaXMgYXBwcm9hY2ggbmVl
ZHMgYSBjbGVhcmVyIG5hbWUgb3RoZXIgdGhhbiAiZmxvdyBjb250cm9sIiwgc2luY2UgaXQgaGFz
IGEgc29tZXdoYXQgZGlmZmVyZW50IG1lYW5pbmcgaW4gZWZmZWN0Lg0KDQpBcyBmb3IgQUNLcywg
aWYgd2UgbmV2ZXIgZGlzY2FyZCBvbiB0aGUgcmVjZWl2ZXIgc2lkZSwgdGhlIEFDSyBpcyBwcmV0
dHkgdXNlZnVsIGZvciBkZXRlY3RpbmcgaWYgdGhlcmUgd2FzIG5ldHdvcmstYmFzZWQgcGFja2V0
IGxvc3MuDQoNClRoYW5rcywNClRvbW15DQoNCg0KT24gT2N0IDI5LCAyMDE4LCBhdCA1OjMyIEFN
LCBJYW4gU3dldHQgPGlhbnN3ZXR0QGdvb2dsZS5jb208bWFpbHRvOmlhbnN3ZXR0QGdvb2dsZS5j
b20+PiB3cm90ZToNCg0KR29vZCBjYXRjaCBNYXJ0aW4sIEkgbWlzc2VkIHRoYXQgaW4gdGhlIGRy
YWZ0IGFzIHdlbGwsIGFuZCBJIGFsc28gdGhpbmsgaXQncyBpbXBvc3NpYmx5IHdpdGggdGhlIHBy
b3Bvc2VkIGRlc2lnbi4NCg0KQW5kIHllcywgSSB0aGluayBNYXJ0aW4ncyBwcm9wb3NlZCBzb2x1
dGlvbiBpcyBsaWtlbHkgdGhlIG9ubHkgcHJhY3RpY2FsIG9uZS4gIEluIG15IGltcGxlbWVudGF0
aW9uLCB0aGUgZnJhbWUgaXMgcGFzc2VkIHVwIHRvIHRoZSBhcHBsaWNhdGlvbiBpbW1lZGlhdGVs
eSwgc28gdGVjaG5pY2FsbHkgUVVJQyBwcm9jZXNzZWQgaXQsIGFuZCBpdCdzIHRoZSBhcHBsaWNh
dGlvbidzIGpvYiB0byBkZWNpZGUgd2hhdCB0byBkbyB3aXRoIGl0Lg0KDQpPbiBNb24sIE9jdCAy
OSwgMjAxOCBhdCAxOjE2IEFNIE1hcnRpbiBUaG9tc29uIDxtYXJ0aW4udGhvbXNvbkBnbWFpbC5j
b208bWFpbHRvOm1hcnRpbi50aG9tc29uQGdtYWlsLmNvbT4+IHdyb3RlOg0KSGkgVG9tbXksDQoN
CllvdXIgc2xpZGVzIC0gPGh0dHBzOi8vZ2l0aHViLmNvbS9xdWljd2cvd2ctbWF0ZXJpYWxzL2Js
b2IvbWFzdGVyL2lldGYxMDMvSUVURjEwMy1RVUlDLURhdGFncmFtLnBkZjxodHRwczovL3VybGRl
ZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cHMtM0FfX2dpdGh1Yi5jb21fcXVpY3dn
X3dnLTJEbWF0ZXJpYWxzX2Jsb2JfbWFzdGVyX2lldGYxMDNfSUVURjEwMy0yRFFVSUMtMkREYXRh
Z3JhbS5wZGYmZD1Ed01GYVEmYz05NlpiWlpjYU1GNHcwRjRqcE42TFpnJnI9RGpuM2JRNXVOSkRQ
TV8yc2tmTDNyVzF0emNJeHlqVVpkbl9tNTVLUG1sbyZtPS1KQVZ5S0s0THJERlVuLVR6STk2WkZs
ckZaWW96ZzRHRlZ0dG5qSWpHZGcmcz10cVVRWlctaFAwR3daN3gxb3RQa1NZcEEzYXhHVml6WXUw
YTRKbExvdTZRJmU9Pj4NCi0gc2F5IHRoYXQgREFUQUdSQU0gZnJhbWVzIHJlc3BlY3QgY29ubmVj
dGlvbi1sZXZlbCBmbG93IGNvbnRyb2wuICBJDQptaXNzZWQgdGhhdCBpbiB0aGUgZHJhZnQsIGFu
ZCBJIGRvbid0IGtub3cgaG93IHRoZXkgY2FuIGRvIHRoYXQgaW4gdGhlDQpmYWNlIG9mIHBhY2tl
dCBsb3NzLCBlc3BlY2lhbGx5IHdoZW4geW91IGRvbid0IG5lY2Vzc2FyaWx5IHJldHJhbnNtaXQN
Cmxvc3QgREFUQUdSQU0gZnJhbWVzLg0KDQpGb3IgdGhhdCB0byB3b3JrLCB5b3Ugd291bGQgbmVl
ZCBhIGJ1bmNoIG1vcmUgbWFjaGluZXJ5IHRvIG1ha2UgdGhlDQpjb25uZWN0aW9uLWxldmVsIGZs
b3cgY29udHJvbCBzeW5jIGJldHdlZW4gZW5kcG9pbnRzIGluIHRoZSBjYXNlIHRoYXQNCnBhY2tl
dHMgYXJlIGxvc3QuICBBIGRpc2FncmVlbWVudCBhYm91dCBob3cgbXVjaCBmbG93IGNvbnRyb2wg
aXMgdXNlZA0KY2F1c2VzIHRoaW5ncyB0byBicmVhayBkb3duIGJhZGx5LiAgSWFuIGFuZCBJIGRp
c2N1c3NlZCB0aGlzIHBvaW50IGF0DQp0aGUgbGFzdCBtZWV0aW5nIGFuZCBxdWlja2x5IGFncmVl
ZCB0aGF0IHdoaWxlIGl0IG1pZ2h0IGJlIG5pY2UgdG8NCmhhdmUgZmxvdyBjb250cm9sIGZvciB0
aGlzIHN0dWZmLCB0aGUgaW5jcmVhc2UgaW4gY29tcGxleGl0eSBpcw0KY29uc2lkZXJhYmxlIGFu
ZCAoYXQgdGhlIHRpbWUpIHdlIHRob3VnaHQgaXQgd291bGRuJ3QgYmUgd29ydGggaXQuDQoNClRo
ZSBwcm9ibGVtIHRoYXQgaW50cm9kdWNlcyBpcyB0aGF0IHlvdSBjb3VsZCBlbmQgdXAgaGF2aW5n
IHRvbyBtYW55DQpEQVRBR1JBTSBmcmFtZXMgYXJyaXZlLiAgVGhlIHJlY2VpdmVyIGhhcyB0byBk
cm9wIHNvbWV0aGluZyBhdCB0aGUNCnBvaW50IHRoYXQgaXQgY2FuJ3QgaGFuZGxlIHRoZW0uICBB
bmQgd2Ugc2F5IHRoYXQgd2hlbiB5b3UgYWNrbm93bGVkZ2UNCnNvbWV0aGluZywgeW91IHByb2Nl
c3NlZCBpdC4gIFRoYXQncyB0cmlja3kuDQoNCkl0IG1pZ2h0IGJlIGVhc2llciB0byBzYXkgdGhh
dCBhIFFVSUMgYWNrbm93bGVkZ21lbnQgZm9yIGEgREFUQUdSQU0NCmZyYW1lIGRvZXNuJ3QgbWVh
biB0aGF0IGl0IHdhcyByZWNlaXZlZCBhbmQgcHJvY2Vzc2VkIGJ5IGFuDQphcHBsaWNhdGlvbi4g
IEFuIGVuZHBvaW50IG1pZ2h0IGRpc2NhcmQgdGhlc2UgZnJhbWVzIGJlZm9yZSBwYXNzaW5nDQp0
aGVtIG9uIHRvIGFwcGxpY2F0aW9ucyBpZiBpdCBkb2Vzbid0IGhhdmUgc3BhY2UuICBJbiBvdGhl
ciB3b3JkcywNCmFja25vd2xlZGdtZW50IG9mIERBVEFHUkFNIG1lYW5zIHRoYXQgUVVJQyBnb3Qg
aXQsIG5vdCB0aGF0IHRoZQ0KYXBwbGljYXRpb24gZ290IGl0LiAgU2FkbHksIHRoYXQgbWVhbnMg
dGhhdCB0aGUgUVVJQyBhY2tub3dsZWRnbWVudA0KbWFjaGluZXJ5IGRvZXNuJ3QgaGVscCB0aGUg
YXBwbGljYXRpb24gdGhhdCB1c2VzIERBVEFHUkFNIGFsbCB0aGF0DQptdWNoLiAgQWxzbywgdGhl
IGxvd2VyIGJvdW5kIG9uIHJlbGlhYmlsaXR5IGlzIDAsIHdoaWNoIGlzbid0IHRoZSBiZXN0DQp0
aGluZyBldmVyLg0KDQpIYXJkIGNob2ljZXMsIEkga25vdy4gIEkgZG9uJ3QgaGF2ZSBhIGdvb2Qg
ZGVzaWduIGZvciBtYWludGFpbmluZw0KY29ubmVjdGlvbi1sZXZlbCBmbG93IGNvbnRyb2wgKG9y
IGFueSBiYWNrIHByZXNzdXJlIG1lY2hhbmlzbSB3aXRoDQplcXVpdmFsZW50IHByb3BlcnRpZXMp
IHRoYXQgZG9lc24ndCBhZGQgYm90aCBjb21wbGV4aXR5IGFuZCBvdmVyaGVhZC4NCg0KQ2hlZXJz
LA0KTWFydGluDQoNCg0K

--_000_344a8a30b95441af988b675c2f887965usma1exdag1mb6msgcorpak_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1
IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZp
c2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5
Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvTGlz
dFBhcmFncmFwaCwgbGkuTXNvTGlzdFBhcmFncmFwaCwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGgNCgl7
bXNvLXN0eWxlLXByaW9yaXR5OjM0Ow0KCW1hcmdpbi10b3A6MGluOw0KCW1hcmdpbi1yaWdodDow
aW47DQoJbWFyZ2luLWJvdHRvbTowaW47DQoJbWFyZ2luLWxlZnQ6LjVpbjsNCgltYXJnaW4tYm90
dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
c2Fucy1zZXJpZjt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWww
DQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsN
CgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdp
bi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFs
LXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRv
d3RleHQ7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQou
TXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6
MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJn
aW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldv
cmRTZWN0aW9uMTt9DQovKiBMaXN0IERlZmluaXRpb25zICovDQpAbGlzdCBsMA0KCXttc28tbGlz
dC1pZDoxMTMwMTcyNjc1Ow0KCW1zby1saXN0LXR5cGU6aHlicmlkOw0KCW1zby1saXN0LXRlbXBs
YXRlLWlkczoxMDgzMzU2MjY2IC00MTczMDU2NDQgNjc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkg
Njc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTM7fQ0KQGxpc3QgbDA6
bGV2ZWwxDQoJe21zby1sZXZlbC1zdGFydC1hdDowOw0KCW1zby1sZXZlbC1udW1iZXItZm9ybWF0
OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDotOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0K
CW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJbXNvLWZhcmVhc3QtZm9udC1mYW1p
bHk6Q2FsaWJyaTsNCgltc28tYmlkaS1mb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIjt9DQpA
bGlzdCBsMDpsZXZlbDINCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1s
ZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJl
ci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseToiQ291
cmllciBOZXciO30NCkBsaXN0IGwwOmxldmVsMw0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpi
dWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0K
CW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJ
Zm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwwOmxldmVsNA0KCXttc28tbGV2ZWwtbnVt
YmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWIt
c3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVu
dDotLjI1aW47DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwwOmxldmVsNQ0KCXttc28t
bGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2
ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4
dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6
bGV2ZWw2DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4
dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3Np
dGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7
fQ0KQGxpc3QgbDA6bGV2ZWw3DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCglt
c28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVs
LW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWls
eTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1
bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1z
by1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9u
dC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDkNCgl7bXNvLWxldmVsLW51
bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFi
LXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRl
bnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpvbA0KCXttYXJnaW4tYm90dG9t
OjBpbjt9DQp1bA0KCXttYXJnaW4tYm90dG9tOjBpbjt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3Rl
IG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAy
NiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hh
cGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+
DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5n
PSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2Vj
dGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jmd0OyBBQ0sgdG8gYSBwYWNrZXQgY29udGFp
bmluZyBhIERBVEFHUkFNIGZyYW1lIG1lYW5zOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+Jmd0OyAtIFRoZSBwYWNrZXQgbWFkZSBpdCBhY3Jvc3MgdGhlIG5ldHdvcmsgdG8g
dGhlIFFVSUMgZW5kcG9pbnQgb24gdGhlIG90aGVyIHNpZGU8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPiZndDsgLSBUaGUgUVVJQyBpbXBsZW1lbnRhdGlvbiB3aWxsIGRlbGl2
ZXIgdGhlIERBVEFHUkFNIGZyYW1lIHRvIGFwcGxpY2F0aW9uIChpdCB3b24ndCBkcm9wIGl0IGxv
Y2FsbHkpPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mZ3Q7PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mZ3Q7IERvZXMgdGhhdCBtYWtlIHNl
bnNlPzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGlzIG9ubHkgbWFrZXMgc2Vuc2UsIGlmIHRo
ZXJlIGlzIGFuIGVmZmVjdGl2ZSBmbG93IGNvbnRyb2wgZm9yIERBVEFHUkFNcy4mbmJzcDsgVGhl
IHNwZWMgc2hvdWxkIGJlIGltcGxlbWVudGFibGUgYnkgcG9sbC9yZWFkIFFVSUMgaW1wbGVtZW50
YXRpb25zIGFzIHdlbGwgYXMgYnkgY2FsbGJhY2stb24tbmV0d29yay1yZWNlaXZlLXRocmVhZCBp
bXBsZW1lbnRhdGlvbnMuJm5ic3A7IFVubGVzcyB0aGVyZSBpcyBhbiBlZmZlY3RpdmUNCiBmbG93
IGNvbnRyb2wsIGEgYnVmZmVyaW5nIFFVSUMgaW1wbGVtZW50YXRpb24gbXVzdCBiZSBhYmxlIHRv
IGRpc2NhcmQgREFUQUdSQU1zLCBpZiB0aGUgcmVjZWl2ZXIgYXBwIGlzIG5vdCBjYXRjaGluZyB1
cC4mbmJzcDsgVGhlIHJlY2VpdmVyIHdvdWxkIHRoZW4gaGF2ZSB0byBpZ25vcmUgYWxsIG5vbi1E
QVRBR1JBTSBmcmFtZXMgaW4gdGhhdCBwYWNrZXQsIHNpbmNlIGl0IHdvdWxkIGJlIHVuYWJsZSB0
byBBQ0sgdGhlIHBhY2tldC4mbmJzcDsgSWYgdGhlIHJlY2VpdmVyDQogaXMgcHJvY2Vzc2luZyBE
QVRBR1JBTXMgYW5kIFNUUkVBTXMgYXQgZGlmZmVyZW50IHNwZWVkcywgZGVsaWJlcmF0ZSBkaXNj
YXJkcyBvZiBwYWNrZXRzIGNvbnRhaW5pbmcgREFUQUdSQU1zIHdvdWxkIGludGVyZmVyZSB3aXRo
IHRoZSBjb25nZXN0aW9uIGNvbnRyb2wsIGVmZmVjdGl2ZWx5IEhPTCBibG9ja2luZyBTVFJFQU1z
LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BbiBlZmZlY3RpdmUgZmxvdyBjb250cm9sIHJlcXVp
cmVzIHNlbmRlciBhbmQgcmVjZWl2ZXIgdG8gc3luY2hyb25pemUgdGhlaXIgdmlldyBvZiB0aGUg
ZmxvdyBjb250cm9sIGNvdW50ZXIgKE1BWF9EQVRBIGZvciBjb25uZWN0aW9uIGZsb3cgY29udHJv
bCkuJm5ic3A7IFJlbHlpbmcgb24gQUNLcyBpcyB2ZXJ5IGhhcmQsIHNpbmNlIHRoZSByZWNlaXZl
ciBjYW5ub3Qga25vdyBob3cgbXVjaCBkYXRhIHRoZSBzZW5kZXINCiBoYXMgc2VudCAodW5sZXNz
IHRoZSBzZW5kZXIgaXMgZXhwbGljaXQgYWJvdXQgaXQpLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5JZiBmbG93IGNvbnRyb2wgZm9yIERBVEFHUkFNcyBpcyBkZXNpcmVkLCB5b3UgY2FuIHVzZSBt
ZWNoYW5pY3Mgc3VjaCBhcyBpbg0KPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1s
L2RyYWZ0LWx1YmFzaGV2LXF1aWMtcGFydGlhbC1yZWxpYWJpbGl0eS0wMiI+DQpodHRwczovL3Rv
b2xzLmlldGYub3JnL2h0bWwvZHJhZnQtbHViYXNoZXYtcXVpYy1wYXJ0aWFsLXJlbGlhYmlsaXR5
LTAyPC9hPiBvciA8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtbHVi
YXNoZXYtcXVpYy1wYXJ0aWFsLXJlbGlhYmlsaXR5LTAzIj4NCmh0dHBzOi8vdG9vbHMuaWV0Zi5v
cmcvaHRtbC9kcmFmdC1sdWJhc2hldi1xdWljLXBhcnRpYWwtcmVsaWFiaWxpdHktMDM8L2E+ICg8
YSBocmVmPSJodHRwczovL2dpdGh1Yi5jb20vaWdvcmxvcmQvZHJhZnQtbHViYXNoZXYtcXVpYy1w
YXJ0aWFsLXJlbGlhYmlsaXR5Ij5odHRwczovL2dpdGh1Yi5jb20vaWdvcmxvcmQvZHJhZnQtbHVi
YXNoZXYtcXVpYy1wYXJ0aWFsLXJlbGlhYmlsaXR5PC9hPikuJm5ic3A7IChUaGlzIHdvdWxkIGJl
IHRyZWF0aW5nIERBVEFHUkFNcw0KIGFzIGJlbG9uZ2luZyB0byBhIHBhcnRpYWxseSByZWxpYWJs
ZSBzdHJlYW0sIG9yIHN0cmVhbXMuJm5ic3A7IEV4Y2VwdCB5b3Ugd291bGQgbm90IG5lZWQgdG8g
ZW5zdXJlIG9yZGVyaW5nIG9mIERBVEFHUkFNcyBpbiB0aGF0IHN0cmVhbS4pPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjx1bCBzdHls
ZT0ibWFyZ2luLXRvcDowaW4iIHR5cGU9ImRpc2MiPg0KPGxpIGNsYXNzPSJNc29MaXN0UGFyYWdy
YXBoIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MGluO21zby1saXN0OmwwIGxldmVsMSBsZm8xIj5JZ29y
PG86cD48L286cD48L2xpPjwvdWw+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRp
diBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5n
OjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5Gcm9tOjwvYj4gVG9tbXkgUGF1bHkgJmx0O3RwYXVseUBh
cHBsZS5jb20mZ3Q7IDxicj4NCjxiPlNlbnQ6PC9iPiBNb25kYXksIE9jdG9iZXIgMjksIDIwMTgg
NDowMSBQTTxicj4NCjxiPlRvOjwvYj4gSmFuYSBJeWVuZ2FyICZsdDtqcmkuaWV0ZkBnbWFpbC5j
b20mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBJYW4gU3dldHQgJmx0O2lhbnN3ZXR0QGdvb2dsZS5jb20m
Z3Q7OyBRVUlDIFdHICZsdDtxdWljQGlldGYub3JnJmd0OzsgTWFydGluIFRob21zb24gJmx0O21h
cnRpbi50aG9tc29uQGdtYWlsLmNvbSZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IGZsb3cg
Y29udHJvbCBhbmQgREFUQUdSQU08bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPkhpIEphbmEsPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5JJ20gbm90IHN1Z2dlc3RpbmcgYW55IGNoYW5nZXMgdG8gd2hlbiB0aGUgcGFja2V0IGdldHMg
YWNrJ2Vk4oCUc3BlY2lmaWNhbGx5LCBJIHdhcyByZXNwb25kaW5nIHRvIE1hcnRpbidzIGh5cG90
aGV0aWNhbCBvZiBoYXZpbmcgYW4gQUNLIHRvIGEgREFUQUdSQU0gZnJhbWUgbWVhbmluZyB0aGF0
IHRoZSBhcHBsaWNhdGlvbiBoYWQgcHJvY2Vzc2VkIHRoZSBmcmFtZS4gTXkgaW1wcmVzc2lvbiBp
cyB0aGF0IHRoZSBBQ0sNCiB0byBhIHBhY2tldCBjb250YWluaW5nIGEgREFUQUdSQU0gZnJhbWUg
bWVhbnM6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij4tIFRoZSBwYWNrZXQgbWFkZSBpdCBhY3Jvc3MgdGhlIG5ldHdvcmsgdG8gdGhlIFFVSUMgZW5k
cG9pbnQgb24gdGhlIG90aGVyIHNpZGU8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPi0gVGhlIFFVSUMgaW1wbGVtZW50YXRpb24gd2lsbCBkZWxpdmVy
IHRoZSBEQVRBR1JBTSBmcmFtZSB0byBhcHBsaWNhdGlvbiAoaXQgd29uJ3QgZHJvcCBpdCBsb2Nh
bGx5KTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5Eb2VzIHRoYXQgbWFrZSBzZW5zZT88bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+SGF2aW5nIGEgc2VwYXJhdGUgb3V0c3RhbmRpbmcgZGF0YSBs
aW1pdCBmb3IgdGhlIERBVEFHUkFNICZxdW90O3N0cmVhbSZxdW90OyBpcyBhbiBpbnRlcmVzdGlu
ZyBzb2x1dGlvbiB0byB0aGUgc3BhY2UuIEl0IHdvdWxkIHRoZW4gaGF2ZSB0aGUgbmljZSBwcm9w
ZXJ0eSBvZiBub3QgbG9va2luZyBsaWtlIHRyYWRpdGlvbmFsIGZsb3cgY29udHJvbC4gSXQgY291
bGQgZXZlbiBiZSBtZWFzdXJlZCBpbiBudW1iZXIgb2YgZnJhbWVzLA0KIHJhdGhlciB0aGFuIGJ5
dGVzIChkZXBlbmRpbmcgb24gd2hhdCB0aGUgbGltaXRpbmcgZmFjdG9ycyBhcmUpLjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFua3MsPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Ub21teTxv
OnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxicj4NCjxicj4NCjxv
OnA+PC9vOnA+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2lu
LWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gT2N0IDI5LCAy
MDE4LCBhdCAxMjozNyBQTSwgSmFuYSBJeWVuZ2FyICZsdDs8YSBocmVmPSJtYWlsdG86anJpLmll
dGZAZ21haWwuY29tIj5qcmkuaWV0ZkBnbWFpbC5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRvbW15LDxvOnA+PC9vOnA+PC9w
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Q2hhbmdpbmcgdGhlIHNlbWFudGljcyBv
ZiBhbiBhY2tub3dsZWRnbWVudCB0byBpbmNsdWRlIGRlbGl2ZXJ5IHVwIHRvIHRoZSBhcHBsaWNh
dGlvbiBpcyBhIGZ1bmRhbWVudGFsIGNoYW5nZSB0byB0aGUgUVVJQyBtYWNoaW5lcnksIGFuZCBp
dCBkb2Vzbid0IHdvcmsuIEZpcnN0LCBhbiBBQ0sgZnJhbWUgYWNrbm93bGVkZ2VzIHBhY2tldHMs
IGFuZCB5b3UgY2FuJ3QgaGF2ZSBkaWZmZXJlbnQgc2VtYW50aWNzIG9mDQogYW4gYWNrbm93bGVk
Z21lbnQgZm9yIGRpZmZlcmVudCBmcmFtZXMgdGhhdCBhcmUgY2FycmllZCBpbiB0aGUgc2FtZSBw
YWNrZXQuIFNlY29uZCwgaXQgaW50ZXJmZXJlcyB3aXRoIFJUVCBtZWFzdXJlbWVudCwgYW5kIGl0
IGNvbmZsYXRlcyBmbG93IGNvbnRyb2wgd2l0aCBjb25nZXN0aW9uIGNvbnRyb2wsIHdoaWNoIGdl
dHMgbWVzc3kuIChUaGlzIGNvbmZsYXRpb24gaXMgYW4gaW50ZXJlc3RpbmcgcHJvYmxlbSB0byBj
b25zaWRlciB0aGVvcmV0aWNhbGx5LA0KIGJ1dCBub3Qgb25lIGZvciB1cyBhdCB0aGlzIHRpbWUg
SU1PLik8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+SSBhbSB3b25kZXJpbmcgaWYgYXBwbHlpbmcgYSBzdHJlYW0tbGV2ZWwgZmxvdyBjb250cm9s
IGZvciBEQVRBR1JBTXMgbWFrZXMgc2Vuc2UgaW5zdGVhZC4gTWVhbmluZyB0aGF0IHlvdSB0cmVh
dCBEQVRBR1JBTXMgYXMgYSBzZXBhcmF0ZSBzdHJlYW0gZm9yIGZsb3cgY29udHJvbCBwdXJwb3Nl
cy4gWW91IG1pZ2h0IGJlbmVmaXQgZnJvbSBoYXZpbmcgYW4gb2Zmc2V0IGluIHRoZSBEQVRBR1JB
TSBmcmFtZSBmb3INCiB0aGlzIHB1cnBvc2UuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi0gamFuYTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBNb24sIE9jdCAyOSwgMjAxOCBhdCA4OjIx
IEFNIFRvbW15IFBhdWx5ICZsdDs8YSBocmVmPSJtYWlsdG86dHBhdWx5QGFwcGxlLmNvbSI+dHBh
dWx5QGFwcGxlLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8Ymxv
Y2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBw
dDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdo
dDowaW4iPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhpIE1hcnRpbiwgSWFuLDxvOnA+
PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+WWVzLCB2ZXJ5IGdvb2Qg
cG9pbnRzITxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5NeSB0ZW5kZW5jeSB3b3VsZCBiZSB0byBwcmVmZXIgd2hhdCBJYW4ncyBpbXBsZW1lbnRh
dGlvbiBkb2VzIG9mIHBhc3NpbmcgdGhlc2UgREFUQUdSQU0gZnJhbWVzIHVwIGltbWVkaWF0ZWx5
IHRvIHRoZSBhcHBsaWNhdGlvbi4gSSBkb24ndCB0aGluayB0aGF0IHRoZSBhY2tub3dsZWRnbWVu
dCBuZWVkcyB0byBpbmRpY2F0ZSB0aGF0IHRoZSBmcmFtZSB3YXMgcHJvY2Vzc2VkIGJ5IHRoZSBh
cHBsaWNhdGlvbiwgYnV0DQogbWVyZWx5IHRoYXQgaXQgaGFzIGJlZW4gZGVsaXZlcmVkIHRvIHRo
ZSBhcHBsaWNhdGlvbiAodGhhdCBpcywgdGhlIGFwcGxpY2F0aW9uIGRvZXNuJ3QgZ2V0IHRvIGRv
IGFueXRoaW5nIHdpdGggdGhlIGZyYW1lIHRoYXQgY2FuIGluZmx1ZW5jZSB0aGUgYWNrbm93bGVk
Z21lbnQpLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5UaGUgY3VycmVudCBkcmFmdCBpbmRpY2F0ZXMgdGhhdCB0aGUgY29udGVudCBvZiB0aGUg
REFUQUdSQU0gZnJhbWVzIGNvbnRyaWJ1dGVzIHRvIHRoZSBsaW1pdCB1c2VkIGZvciZuYnNwO01B
WF9EQVRBLCBhbmQgdGhhdCBpZiB0aGF0IGFtb3VudCBpcyByZWFjaGVkLCB0aGUgZnJhbWVzIGFy
ZSBibG9ja2VkIGFsb25nIHdpdGggU1RSRUFNIGRhdGEuIEkgdGhpbmsgdGhpcyB3b3JrcyBmaW5l
IGZvciB0aGUgc2VuZGVyLCB3aGlsZQ0KIHRoZSByZWNlaXZlciBnZXRzIGludG8gdGhlIGRpc2N1
c3Npb24geW91IHByZXNlbnQuIE9uIHRoZSBzZW5kZXIgc2lkZSwgcmVhY2hpbmcgTUFYX0RBVEEg
Y291bGQgbWVhbiBkcm9wcGluZyB0aGUgREFUQUdSQU0gZnJhbWVzIHdoZW4gdW5hYmxlIHRvIHNl
bmQgbW9yZSAoYW5kIHNlbmRpbmcgQkxPQ0tFRCBpbnN0ZWFkKS4gU2luY2UgdGhlIGZyYW1lcyBh
cmUgdW5yZWxpYWJsZSwgdGhleSBjYW4gYmUgZHJvcHBlZCBpbiB0aGlzIHNpdHVhdGlvbg0KIHdp
dGhvdXQgdmlvbGF0aW5nIHRoZSBBUEkgY29udHJhY3QuJm5ic3A7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIHRoZSByZWNlaXZlciBzaWRl
LCBJIGFncmVlIHRoYXQgcXVldWluZyB0aGUgREFUQUdSQU0gZnJhbWVzIHRvIGxldCB0aGUgYXBw
bGljYXRpb24gZHJpdmUgZmxvdyBjb250cm9sIGluIHRoZSB3YXkgaXQgZG9lcyBmb3IgU1RSRUFN
IGZyYW1lcyBhZGRzIGNvbXBsZXhpdHkgYW5kIGRpbWluaXNoZXMgdGhlIHV0aWxpdHkgb2YgdGhl
IGZyYW1lIGFuZCBBQ0tzLi4gSG93ZXZlciwgSSBjYW4gaW1hZ2luZSB0YWtpbmcNCiBhIGZhaXJs
eSBzaW1wbGlzdGljIGFwcHJvYWNoIGluIHdoaWNoIHRoZSBkYXRhIGxpbWl0IGlzIGF1dG9tYXRp
Y2FsbHkgaW5jcmVhc2VkIHVwb24gcmVjZXB0aW9uIG9mIHRoZSBmcmFtZSAoYW5kIHRoZSBmcmFt
ZSBpcyBpbW1lZGlhdGVseSBwYXNzZWQgdG8gdGhlIGFwcGxpY2F0aW9uKS4gVGhpcyBhbGxvd3Mg
dGhlIGluaXRpYWxfbWF4X2RhdGEgdG8gcHV0IGEgY2FwIG9uIHRoZSBhbW91bnQgb2YgZGF0YSBp
biBhIGdpdmVuIGZsaWdodCBvZiBEQVRBR1JBTVMsDQogYW5kIGFsbG93IHRoZSBzaXplIG9mIGEg
ZmxpZ2h0IG9mIERBVEFHUkFNIGZyYW1lcyB0byBiZSBsaW1pdGVkIGJ5IHRoZSBhbW91bnQgb2Yg
cm9vbSBsZWZ0IG92ZXIgZnJvbSBTVFJFQU0gZGF0YSB0aGF0IG1heSBiZSBjb25zdW1pbmcgdGhl
IGNvbm5lY3Rpb24td2lkZSBmbG93IGNvbnRyb2wuJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlBlcmhhcHMgdGhpcyBhcHByb2FjaCBu
ZWVkcyBhIGNsZWFyZXIgbmFtZSBvdGhlciB0aGFuICZxdW90O2Zsb3cgY29udHJvbCZxdW90Oywg
c2luY2UgaXQgaGFzIGEgc29tZXdoYXQgZGlmZmVyZW50IG1lYW5pbmcgaW4gZWZmZWN0LjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BcyBmb3Ig
QUNLcywgaWYgd2UgbmV2ZXIgZGlzY2FyZCBvbiB0aGUgcmVjZWl2ZXIgc2lkZSwgdGhlIEFDSyBp
cyBwcmV0dHkgdXNlZnVsIGZvciBkZXRlY3RpbmcgaWYgdGhlcmUgd2FzIG5ldHdvcmstYmFzZWQg
cGFja2V0IGxvc3MuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPlRoYW5rcyw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPlRvbW15Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGJyPg0KPGJyPg0KPG86cD48L286cD48L3A+DQo8
YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBPY3QgMjksIDIwMTgsIGF0IDU6MzIgQU0s
IElhbiBTd2V0dCAmbHQ7PGEgaHJlZj0ibWFpbHRvOmlhbnN3ZXR0QGdvb2dsZS5jb20iIHRhcmdl
dD0iX2JsYW5rIj5pYW5zd2V0dEBnb29nbGUuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Hb29kIGNhdGNoIE1hcnRpbiwgSSBt
aXNzZWQgdGhhdCBpbiB0aGUgZHJhZnQgYXMgd2VsbCwgYW5kIEkgYWxzbyB0aGluayBpdCdzIGlt
cG9zc2libHkgd2l0aCB0aGUgcHJvcG9zZWQgZGVzaWduLjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QW5kIHllcywgSSB0aGluayBNYXJ0aW4ncyBwcm9wb3Nl
ZCBzb2x1dGlvbiBpcyBsaWtlbHkgdGhlIG9ubHkgcHJhY3RpY2FsIG9uZS4mbmJzcDsgSW4gbXkg
aW1wbGVtZW50YXRpb24sIHRoZSBmcmFtZSBpcyBwYXNzZWQgdXAgdG8gdGhlIGFwcGxpY2F0aW9u
IGltbWVkaWF0ZWx5LCBzbyB0ZWNobmljYWxseSBRVUlDIHByb2Nlc3NlZCBpdCwgYW5kIGl0J3Mg
dGhlIGFwcGxpY2F0aW9uJ3Mgam9iIHRvIGRlY2lkZSB3aGF0DQogdG8gZG8gd2l0aCBpdC48bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gTW9u
LCBPY3QgMjksIDIwMTggYXQgMToxNiBBTSBNYXJ0aW4gVGhvbXNvbiAmbHQ7PGEgaHJlZj0ibWFp
bHRvOm1hcnRpbi50aG9tc29uQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPm1hcnRpbi50aG9t
c29uQGdtYWlsLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8Ymxv
Y2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+SGkgVG9tbXks
PGJyPg0KPGJyPg0KWW91ciBzbGlkZXMgLSAmbHQ7PGEgaHJlZj0iaHR0cHM6Ly91cmxkZWZlbnNl
LnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0dHBzLTNBX19naXRodWIuY29tX3F1aWN3Z193Zy0y
RG1hdGVyaWFsc19ibG9iX21hc3Rlcl9pZXRmMTAzX0lFVEYxMDMtMkRRVUlDLTJERGF0YWdyYW0u
cGRmJmFtcDtkPUR3TUZhUSZhbXA7Yz05NlpiWlpjYU1GNHcwRjRqcE42TFpnJmFtcDtyPURqbjNi
UTV1TkpEUE1fMnNrZkwzclcxdHpjSXh5alVaZG5fbTU1S1BtbG8mYW1wO209LUpBVnlLSzRMckRG
VW4tVHpJOTZaRmxyRlpZb3pnNEdGVnR0bmpJakdkZyZhbXA7cz10cVVRWlctaFAwR3daN3gxb3RQ
a1NZcEEzYXhHVml6WXUwYTRKbExvdTZRJmFtcDtlPSIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8v
Z2l0aHViLmNvbS9xdWljd2cvd2ctbWF0ZXJpYWxzL2Jsb2IvbWFzdGVyL2lldGYxMDMvSUVURjEw
My1RVUlDLURhdGFncmFtLnBkZjwvYT4mZ3Q7PGJyPg0KLSBzYXkgdGhhdCBEQVRBR1JBTSBmcmFt
ZXMgcmVzcGVjdCBjb25uZWN0aW9uLWxldmVsIGZsb3cgY29udHJvbC4mbmJzcDsgSTxicj4NCm1p
c3NlZCB0aGF0IGluIHRoZSBkcmFmdCwgYW5kIEkgZG9uJ3Qga25vdyBob3cgdGhleSBjYW4gZG8g
dGhhdCBpbiB0aGU8YnI+DQpmYWNlIG9mIHBhY2tldCBsb3NzLCBlc3BlY2lhbGx5IHdoZW4geW91
IGRvbid0IG5lY2Vzc2FyaWx5IHJldHJhbnNtaXQ8YnI+DQpsb3N0IERBVEFHUkFNIGZyYW1lcy48
YnI+DQo8YnI+DQpGb3IgdGhhdCB0byB3b3JrLCB5b3Ugd291bGQgbmVlZCBhIGJ1bmNoIG1vcmUg
bWFjaGluZXJ5IHRvIG1ha2UgdGhlPGJyPg0KY29ubmVjdGlvbi1sZXZlbCBmbG93IGNvbnRyb2wg
c3luYyBiZXR3ZWVuIGVuZHBvaW50cyBpbiB0aGUgY2FzZSB0aGF0PGJyPg0KcGFja2V0cyBhcmUg
bG9zdC4mbmJzcDsgQSBkaXNhZ3JlZW1lbnQgYWJvdXQgaG93IG11Y2ggZmxvdyBjb250cm9sIGlz
IHVzZWQ8YnI+DQpjYXVzZXMgdGhpbmdzIHRvIGJyZWFrIGRvd24gYmFkbHkuJm5ic3A7IElhbiBh
bmQgSSBkaXNjdXNzZWQgdGhpcyBwb2ludCBhdDxicj4NCnRoZSBsYXN0IG1lZXRpbmcgYW5kIHF1
aWNrbHkgYWdyZWVkIHRoYXQgd2hpbGUgaXQgbWlnaHQgYmUgbmljZSB0bzxicj4NCmhhdmUgZmxv
dyBjb250cm9sIGZvciB0aGlzIHN0dWZmLCB0aGUgaW5jcmVhc2UgaW4gY29tcGxleGl0eSBpczxi
cj4NCmNvbnNpZGVyYWJsZSBhbmQgKGF0IHRoZSB0aW1lKSB3ZSB0aG91Z2h0IGl0IHdvdWxkbid0
IGJlIHdvcnRoIGl0Ljxicj4NCjxicj4NClRoZSBwcm9ibGVtIHRoYXQgaW50cm9kdWNlcyBpcyB0
aGF0IHlvdSBjb3VsZCBlbmQgdXAgaGF2aW5nIHRvbyBtYW55PGJyPg0KREFUQUdSQU0gZnJhbWVz
IGFycml2ZS4mbmJzcDsgVGhlIHJlY2VpdmVyIGhhcyB0byBkcm9wIHNvbWV0aGluZyBhdCB0aGU8
YnI+DQpwb2ludCB0aGF0IGl0IGNhbid0IGhhbmRsZSB0aGVtLiZuYnNwOyBBbmQgd2Ugc2F5IHRo
YXQgd2hlbiB5b3UgYWNrbm93bGVkZ2U8YnI+DQpzb21ldGhpbmcsIHlvdSBwcm9jZXNzZWQgaXQu
Jm5ic3A7IFRoYXQncyB0cmlja3kuPGJyPg0KPGJyPg0KSXQgbWlnaHQgYmUgZWFzaWVyIHRvIHNh
eSB0aGF0IGEgUVVJQyBhY2tub3dsZWRnbWVudCBmb3IgYSBEQVRBR1JBTTxicj4NCmZyYW1lIGRv
ZXNuJ3QgbWVhbiB0aGF0IGl0IHdhcyByZWNlaXZlZCBhbmQgcHJvY2Vzc2VkIGJ5IGFuPGJyPg0K
YXBwbGljYXRpb24uJm5ic3A7IEFuIGVuZHBvaW50IG1pZ2h0IGRpc2NhcmQgdGhlc2UgZnJhbWVz
IGJlZm9yZSBwYXNzaW5nPGJyPg0KdGhlbSBvbiB0byBhcHBsaWNhdGlvbnMgaWYgaXQgZG9lc24n
dCBoYXZlIHNwYWNlLiZuYnNwOyBJbiBvdGhlciB3b3Jkcyw8YnI+DQphY2tub3dsZWRnbWVudCBv
ZiBEQVRBR1JBTSBtZWFucyB0aGF0IFFVSUMgZ290IGl0LCBub3QgdGhhdCB0aGU8YnI+DQphcHBs
aWNhdGlvbiBnb3QgaXQuJm5ic3A7IFNhZGx5LCB0aGF0IG1lYW5zIHRoYXQgdGhlIFFVSUMgYWNr
bm93bGVkZ21lbnQ8YnI+DQptYWNoaW5lcnkgZG9lc24ndCBoZWxwIHRoZSBhcHBsaWNhdGlvbiB0
aGF0IHVzZXMgREFUQUdSQU0gYWxsIHRoYXQ8YnI+DQptdWNoLiZuYnNwOyBBbHNvLCB0aGUgbG93
ZXIgYm91bmQgb24gcmVsaWFiaWxpdHkgaXMgMCwgd2hpY2ggaXNuJ3QgdGhlIGJlc3Q8YnI+DQp0
aGluZyBldmVyLjxicj4NCjxicj4NCkhhcmQgY2hvaWNlcywgSSBrbm93LiZuYnNwOyBJIGRvbid0
IGhhdmUgYSBnb29kIGRlc2lnbiBmb3IgbWFpbnRhaW5pbmc8YnI+DQpjb25uZWN0aW9uLWxldmVs
IGZsb3cgY29udHJvbCAob3IgYW55IGJhY2sgcHJlc3N1cmUgbWVjaGFuaXNtIHdpdGg8YnI+DQpl
cXVpdmFsZW50IHByb3BlcnRpZXMpIHRoYXQgZG9lc24ndCBhZGQgYm90aCBjb21wbGV4aXR5IGFu
ZCBvdmVyaGVhZC48YnI+DQo8YnI+DQpDaGVlcnMsPGJyPg0KTWFydGluPG86cD48L286cD48L3A+
DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_344a8a30b95441af988b675c2f887965usma1exdag1mb6msgcorpak_--


From nobody Mon Oct 29 15:29:06 2018
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 2E069131030 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 15:29:05 -0700 (PDT)
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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 SMOI8aaGLhyc for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 15:29:03 -0700 (PDT)
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 E4D29127133 for <quic@ietf.org>; Mon, 29 Oct 2018 15:29:02 -0700 (PDT)
Received: from xsmtp06.mail2web.com ([168.144.250.232]) by mx35.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1gHG1r-0001db-Np for quic@ietf.org; Mon, 29 Oct 2018 23:29:00 +0100
Received: from [10.5.2.15] (helo=xmail05.myhosting.com) by xsmtp06.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1gHG1l-0003Zb-CK for quic@ietf.org; Mon, 29 Oct 2018 18:28:57 -0400
Received: (qmail 20901 invoked from network); 29 Oct 2018 22:28:51 -0000
Received: from unknown (HELO [192.168.1.104]) (Authenticated-user:_huitema@huitema.net@[172.56.42.225]) (envelope-sender <huitema@huitema.net>) by xmail05.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ianswett@google.com>; 29 Oct 2018 22:28:50 -0000
Content-Type: multipart/alternative; boundary=Apple-Mail-116CD75E-F367-49B3-B076-0B94A107B7D9
Mime-Version: 1.0 (1.0)
From: Christian Huitema <huitema@huitema.net>
X-Mailer: iPhone Mail (16A404)
In-Reply-To: <344a8a30b95441af988b675c2f887965@usma1ex-dag1mb6.msg.corp.akamai.com>
Date: Mon, 29 Oct 2018 15:28:49 -0700
Cc: Tommy Pauly <tpauly@apple.com>, Jana Iyengar <jri.ietf@gmail.com>, Ian Swett <ianswett@google.com>, QUIC WG <quic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>
Content-Transfer-Encoding: 7bit
Message-Id: <A8DFD881-924E-4838-8056-9FDBC9D3791D@huitema.net>
References: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com> <CAKcm_gMDOyJC0AwOo2knN6AMxVbySjGsrLvjcC9A8UA9xcvcWw@mail.gmail.com> <19D3595B-8845-45B6-A60D-9E934DD49FAC@apple.com> <CACpbDcfk+GXb3aL5LG0wQM87thRGO5Y4Q+9cbXf5YuW1=jWCig@mail.gmail.com> <B7BE2454-2A4D-4323-B0A5-0D73BD4B819F@apple.com> <344a8a30b95441af988b675c2f887965@usma1ex-dag1mb6.msg.corp.akamai.com>
To: "Lubashev, Igor" <ilubashe@akamai.com>
Subject: Re: flow control and DATAGRAM
X-Originating-IP: 168.144.250.232
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.23)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5hjWGYCzUh7YG8fkBxPHR8h602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO37pNwwF1lRXh5rzvPzo9Jts1ujulqUFmMITHM77eiVi+vRj6yzEgvVZTGazwRo55s7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pB6nkU4uouGtaIPSwAALHVjh/TBCf6oYXAWGet lavcAjD9ytQxIHf9lN5jjLJaPK8lRJSPf/SXbEnDSsal/zZzc4n9VZdr7RAFD5mRwooUYhwMPaBP aKeQW+/QlaOdv8isl/qMm08Zpim2AHUKEWvQ6G/bWfgucjnNmABpGhD9TTttrFCuZ0NkwnSz2Luu o1u9uevuNfM1HjkNEFwape+IgNezYqxGMqsKjARq8PBC4qjpVMhqNcdjhoIlgrKzBvjTmdySlZou 9qHIGOZDEEo7Oyc1nq0gsY582CWqKjiRB3ukywmZtiDkyd4mEBjJGGEJE2d52fY0d/1mkgffWkdO 4QEiRQv+PVjjwa+Z5RFCOMTc/0DL0kGticgfK7BXdIl5xnsMi381k+gKZDYa33nZ/Q2hElfCmYHd K/F6jFUrRk5k354Leo8WHhg9Xcph2esmZk4AVtnYApSiFQp1w3dnUoiPn/2xNqt6sQVacVXeY6AU 1zqm/evfkH8cHl25+qKdJvWZ9M/O6eVqbri1Q0O8/x2vWOKTBJk2Pbgs7SLYxsDtOMdZHeKLxpi2 To9NNZ6PS0eJxHqSOPlqEdtb5t20uHG5BnVj6tDKYf18xfK0O5gaJ/Nk40anfxYE/e+AHCqTw6nI oDr0sXUZ7YZoZ/GZ+u+WjISfXGa/P6JeP9Rx/xr6vvsamCqhsCKWQTQWW5aiOYN2LGYOY+RZZ70I EJvMPP9qwM7RXpJS8RjTdyh2j5BSM6Vge5/tyLofFHTUZzjpzRBCCyVCnQKBwcrUTMoPTDRj9D8H LKHAKpPGP8EPnuBvlPE9yn4+7R7hw716lUpV
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/BvZ5pDlBCd98pNT3lv-6e6azQmY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 22:29:05 -0000

--Apple-Mail-116CD75E-F367-49B3-B076-0B94A107B7D9
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable



> On Oct 29, 2018, at 2:28 PM, Lubashev, Igor <ilubashe@akamai.com> wrote:
>=20
> > ACK to a packet containing a DATAGRAM frame means:
> > - The packet made it across the network to the QUIC endpoint on the othe=
r side
> > - The QUIC implementation will deliver the DATAGRAM frame to application=
 (it won't drop it locally)
> >=20
> > Does that make sense?
> =20
> This only makes sense, if there is an effective flow control for DATAGRAMs=
.  The spec should be implementable by poll/read QUIC implementations as wel=
l as by callback-on-network-receive-thread implementations.  Unless there is=
 an effective flow control, a buffering QUIC implementation must be able to d=
iscard DATAGRAMs, if the receiver app is not catching up.  The receiver woul=
d then have to ignore all non-DATAGRAM frames in that packet, since it would=
 be unable to ACK the packet.  If the receiver is processing DATAGRAMs and S=
TREAMs at different speeds, deliberate discards of packets containing DATAGR=
AMs would interfere with the congestion control, effectively HOL blocking ST=
REAMs.

On the other hand, Datagram will be used to carry the media flows currently c=
arried over RTP, and RTP does not include any kind of flow control.=20

The known weakness of RTP is the lack of integrated congestion control betwe=
en data and media, do that a parallel data download can jeopardize  the qual=
ity of the real time media. But that's an argument for counting the datagram=
s in the congestion control window, not an argument for flow control.

There is an argument for controlling the rate at which media is sent. But th=
at's typically done at the app layer, by negotiating codecs and compression p=
arameters.

-- Christian Huitema=20

--Apple-Mail-116CD75E-F367-49B3-B076-0B94A107B7D9
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><br><br><div dir=3D"ltr">On Oct 29, 2018, a=
t 2:28 PM, Lubashev, Igor &lt;<a href=3D"mailto:ilubashe@akamai.com">ilubash=
e@akamai.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div dir=3D=
"ltr">

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1130172675;
	mso-list-type:hybrid;
	mso-list-template-ids:1083356266 -417305644 67698691 67698693 67698=
689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->


<div class=3D"WordSection1">
<p class=3D"MsoNormal">&gt; ACK to a packet containing a DATAGRAM frame mean=
s:<o:p></o:p></p>
<p class=3D"MsoNormal">&gt; - The packet made it across the network to the Q=
UIC endpoint on the other side<o:p></o:p></p>
<p class=3D"MsoNormal">&gt; - The QUIC implementation will deliver the DATAG=
RAM frame to application (it won't drop it locally)<o:p></o:p></p>
<p class=3D"MsoNormal">&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&gt; Does that make sense?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This only makes sense, if there is an effective flow c=
ontrol for DATAGRAMs.&nbsp; The spec should be implementable by poll/read QU=
IC implementations as well as by callback-on-network-receive-thread implemen=
tations.&nbsp; Unless there is an effective
 flow control, a buffering QUIC implementation must be able to discard DATAG=
RAMs, if the receiver app is not catching up.&nbsp; The receiver would then h=
ave to ignore all non-DATAGRAM frames in that packet, since it would be unab=
le to ACK the packet.&nbsp; If the receiver
 is processing DATAGRAMs and STREAMs at different speeds, deliberate discard=
s of packets containing DATAGRAMs would interfere with the congestion contro=
l, effectively HOL blocking STREAMs.</p></div></div></blockquote><div><br></=
div><div>On the other hand, Datagram will be used to carry the media flows c=
urrently carried over RTP, and RTP does not include any kind of flow control=
.&nbsp;</div><div><br></div><div>The known weakness of RTP is the lack of in=
tegrated congestion control between data and media, do that a parallel data d=
ownload can jeopardize &nbsp;the quality of the real time media. But that's a=
n argument for counting the datagrams in the congestion control window, not a=
n argument for flow control.</div><div><br></div><div>There is an argument f=
or controlling the rate at which media is sent. But that's typically done at=
 the app layer, by negotiating codecs and compression parameters.</div><div>=
<br></div><div>-- Christian Huitema&nbsp;</div><blockquote type=3D"cite"><di=
v dir=3D"ltr"><div class=3D"WordSection1"><p class=3D"MsoNormal"><o:p></o:p>=
</p>
</div></div></blockquote><blockquote type=3D"cite"><div dir=3D"ltr"><div cla=
ss=3D"WordSection1"><div style=3D"border:none;border-left:solid blue 1.5pt;p=
adding:0in 0in 0in 4.0pt"><div>
</div>
</div>
</div>


</div></blockquote></body></html>=

--Apple-Mail-116CD75E-F367-49B3-B076-0B94A107B7D9--


From nobody Mon Oct 29 15:30:08 2018
Return-Path: <martin.thomson@gmail.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 486A11277CC for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 15:30:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 PCZTI1efw9wq for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 15:30:04 -0700 (PDT)
Received: from mail-oi1-x22d.google.com (mail-oi1-x22d.google.com [IPv6:2607:f8b0:4864:20::22d]) (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 ABA79127133 for <quic@ietf.org>; Mon, 29 Oct 2018 15:30:04 -0700 (PDT)
Received: by mail-oi1-x22d.google.com with SMTP id p144-v6so4753824oic.12 for <quic@ietf.org>; Mon, 29 Oct 2018 15:30:04 -0700 (PDT)
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:content-transfer-encoding; bh=bJjMUBlUIW2WAWtSimEyfto2OQLfEBedBdXxYyuXsp0=; b=D+LojLLQsj5j0BuhG4kyQvsM7B/jUiz3p7XIAF0GCCYPmlY+5Yed0FUyddOq5kY2ZD 3zmT2itC/KghtxtSTznrN8zLFN5n4mwCZy24qjasDvv2GVH6s1aRvZM2zH3PmRj/STPi li8VxzncL1wJzCl6tygmC/arIJPcNfE02ky+zUa3c4XeRg6FqOY8OG5H+yZZQIHKX79L JINmzo9pxCfNxQPBYkiEAWE3k4ojIUUihNT8WuL5CSJOv+sLMjh8GQ9UOkrFvFlQfT2p ej6txZ0qaLBy29/0x9XwzlFE9DBxBgGJv+ghh8Df/oyZqqpNDSUKyslj7icPZlUDYjqJ FnNA==
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:content-transfer-encoding; bh=bJjMUBlUIW2WAWtSimEyfto2OQLfEBedBdXxYyuXsp0=; b=bHNq7OI/3/6cWCvxWZ7E3EKhwXeVO+1kuFUEVe19SZC8uBdGGPnVTnyv8aS8BgYLIQ ZXDZh82cPE+ba8Ad0vPgS0HG68Ta2n7xKUmQmahhF6gS253LWaWkNhSEzNv753R1Ot/e ahIFBelpoZ5C6ib2w8/HbhLcuVamhNzZ7uVWnNjYu1wDYsuoDMzUXGKEWpzGiyH+VodO RLt8Dv7zYdzBZx3KxIdFiLyxya8IXQrwMbEdGYahxRjuQSquxF1Y+37uiLNmrwFLXDum y0bUoCyYo8wZGDq7aRmkFIRPGMZq7xWx0ZnqawUQ8OPJIQSYTQ8RCTdk6gJWkdIxr0RG 8HmQ==
X-Gm-Message-State: AGRZ1gLjfel0lTWJdLMfYpOqOT4LnWyi6gBGwRtVPucttw7H3VPqZmm6 6N6bcF0+jnPaFBY/8Y2HbntUV9YeAlq1O87fgA2Bo4s4
X-Google-Smtp-Source: AJdET5dMZe4SNIuET3mAw8d/l2oN01jOc8v8UkW0OZN8zHykikHCQ9FfdZ7cHXqy3kYLjfvC+i1Elngw/iTs2b9P2Js=
X-Received: by 2002:aca:c792:: with SMTP id x140-v6mr8962326oif.129.1540852203875;  Mon, 29 Oct 2018 15:30:03 -0700 (PDT)
MIME-Version: 1.0
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net>
In-Reply-To: <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 30 Oct 2018 09:29:53 +1100
Message-ID: <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com>
Subject: Re: Structuring the BKK spin bit discussion
To: Christian Huitema <huitema@huitema.net>
Cc: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Lars Eggert <lars@eggert.org>, QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/snXGKN_ukw5HMEbAyYfb147KvIQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 22:30:06 -0000

On Tue, Oct 30, 2018 at 3:54 AM Christian Huitema <huitema@huitema.net> wro=
te:
> I think the strongest objection to the spin bit was put up by Marten duri=
ng the last interim: measuring the RTT with the spin bit discloses the use =
of hidden path segments like VPN. This issue was not discussed during the p=
rivacy analysis.

I had assumed that was part of the analysis and it was covered by the
assumption that spinning could be disabled

> One solution would be to remove the spin bit from the spec, trading off b=
etter privacy for worse management. I am considering another solution in wh=
ich privacy sensitive clients hide the RTT by controlling the spin, for exa=
mple spinning at fixed intervals. I plan testing that option in Picoquic.

I've done a little thinking about this one, and it might conflict with
the natural signals the transport emits, along the lines of what
Andrew McGregor has mentioned on a couple of occasions.  If the spin
bit is enabled, then privacy-sensitive endpoints will need to make a
hard call regarding standing out.

Note also that you probably can't hide the fact that you aren't at the
same network location as the address you are using.  Spoofing a
shorter RTT is impossible in general because you have to assume edges
that haven't arrived yet.  If there are no edges you expose the
charade.


From nobody Mon Oct 29 15:33:56 2018
Return-Path: <martin.thomson@gmail.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 04FF3131002 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 15:33:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 7RmiRXbQonXa for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 15:33:51 -0700 (PDT)
Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) (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 C6C82127133 for <quic@ietf.org>; Mon, 29 Oct 2018 15:33:51 -0700 (PDT)
Received: by mail-oi1-x231.google.com with SMTP id v198-v6so5889905oif.2 for <quic@ietf.org>; Mon, 29 Oct 2018 15:33:51 -0700 (PDT)
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:content-transfer-encoding; bh=MizFxxtbOIwofN+HRCA4aALpZtwYL8iw8Iq9WhWs4sc=; b=DU0zuNeufdRELTTmqjxzfa8Y3jkqUyM8r6WgADSpTUxbSPI92GS2wvI/XIdYwTE4hZ zC+gY2Brqhnpcpw4l5FDihUO5Lm40CZSvd0IptL/EmsE42TLwZk/fHsdAB3/I6TVNtXw cjOjLXTJ5CFfyk9IOrYqsnS2aLsstzU/4etytk+paFE2kKUkTXoDH2AdeU4I/i1ZOsCB 9+8dlTh5Xrm7OvYu/UmtZj7zzfrPfsMvNHVoaG8tO38kuO6Jy7lE+mqHq2uo7QjQcrf+ MVXA1NdIxg3dgeFm6ua/WfqSlgmLGIklf7h/hRXkoVUgzSpYqy8b+c4nHhzC1V0Ff+rZ xNuw==
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:content-transfer-encoding; bh=MizFxxtbOIwofN+HRCA4aALpZtwYL8iw8Iq9WhWs4sc=; b=j8abQmIB7gaWc8erWojVWQGZh35wwCDKz0Lo2q/hhhys+R5xXz/uDsaNezTS13KhAv lyaan1IrDCO9GV9LQCUScY6XfKgXc/PYm61JkPCMIHrx7sn9vcPJscq6QAU6BarxhLzp tCXFU4ev5oKxr6CGjvsO2yuFW6lUc+0+CJ2CXHnyzkx2k3HR+2cfjnkaV7itgjwv3UQ9 L2GT984TKIQ8QtOgZnZ8qZ5sl6nEgvfh48h+1vgAtSHuQ5ZYaV9P1yiwzoKQAQSsTKDx EXwdQHBRegBL+xkPnoHIEbuoiYr+Dr1/nhfBEimeQJp0Vh8FsLASqdUNaiGprWd/cig+ i1xw==
X-Gm-Message-State: AGRZ1gK2LRfMhgrUEoA3e2wlvhI61/KnlwvMABFzx8g2aTG9B08+M7rZ LSJkbWNtRmiFBvPPDNnbsuDQOHqUrzGDI/o2qBI9XD/8
X-Google-Smtp-Source: AJdET5c6KLS5ky2XLIP8he3IDS7dLByxsr9dsl75ZuoijiYGM27btByNs8QdFVWrEpEPUh8AUJ6XcGEri0T5V1trDDU=
X-Received: by 2002:aca:3554:: with SMTP id c81-v6mr9107428oia.308.1540852430968;  Mon, 29 Oct 2018 15:33:50 -0700 (PDT)
MIME-Version: 1.0
References: <CAOYVs2rKJMXO806Jp5CpCkH8T80zUHUAauUqdmwEQuTJUhPxnA@mail.gmail.com> <20181029124835.GA7258@ubuntu-dmitri> <CAKcm_gNkVFOverE9GxhGDwf8xH4tb0rDBt6LqKSXj-z6o4r6aw@mail.gmail.com>
In-Reply-To: <CAKcm_gNkVFOverE9GxhGDwf8xH4tb0rDBt6LqKSXj-z6o4r6aw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 30 Oct 2018 09:33:41 +1100
Message-ID: <CABkgnnWm8TgRX_Oq2+CvjQq6sGK5b1g_BAwnkPxGkanDSBSNFw@mail.gmail.com>
Subject: Re: Using varints to encode the Transport Parameters
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: Marten Seemann <martenseemann@gmail.com>, QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/bTanCVDs_QZVaozgmyBmaZr3puA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 22:33:54 -0000

Marten has a week.  That's enough time.

FWIW, here's my grade regarding difficulty:

numeric values to varint - trivial
ID to varint - small change to the grammar
length to varint - major change to the grammar (I'm thinking that you
would signal it by dropping the top of the range like `opaque
x<0..>;`)

You might want to consider not touching the grammar.
On Tue, Oct 30, 2018 at 4:46 AM Ian Swett
<ianswett=3D40google.com@dmarc.ietf.org> wrote:
>
> I agree on both of Dmitri's points and if we're going to discuss this in =
London, a PR is necessary.
>
> If we were discussing this 6 months ago, I'd be in favor.  If it doesn't =
make -17 drafts, I'd say it's QUIC v2.
>
> On Mon, Oct 29, 2018 at 8:48 AM Dmitri Tikhonov <dtikhonov@litespeedtech.=
com> wrote:
>>
>> I see two problems with this proposal: timing and size.
>>
>> This is rather late in the game.  If the Working Group is to follow
>> the plan Martin Thomson outlined in a recent email, this change would
>> have to be included into -17.
>>
>> A hybrid of the TLS Presentation language and QUIC varints has to be
>> specified somewhere itself, thereby increasing the size of the already
>> hefty transport document.  This new specification, in turn, is likely
>> to engender some debate and further optimization proposals.  Allowed
>> to go unchecked, this work would slip our schedule further.
>>
>> One way to approach this proposal is to have a ready-to-merge PR and
>> hum it at the upcoming meeting.
>>
>>   - Dmitri.
>>
>> On Mon, Oct 29, 2018 at 06:13:50PM +0700, Marten Seemann wrote:
>> > This is based on issue https://github.com/quicwg/base-drafts/issues/16=
08.
>> >
>> > The proposal is to change the encoding of the QUIC Transport Parameter=
s
>> > exchanged during the handshake, in order to achieve greater consistenc=
y
>> > with how QUIC encodes values, and also to save a few bytes.
>> >
>> > We have a few things that are called transport parameters. This propos=
al
>> > only applies to the TransportParameter struct as defined in section 18=
 as:
>> > *struct {*
>> > *      TransportParameterId parameter;*
>> > *      opaque value<0..2^16-1>;*
>> > *} TransportParameter;*
>> > According to the encoding defined by the TLS spec, every key-value pai=
r
>> > will be serialized as:
>> > TransportParameterID (2 byte), length (2 byte), value (length byte)
>> > where the length of the value is specified for each TransportParameter=
ID.
>> >
>> > We could switch to varint encoding, as follows:
>> >
>> > 1. for the TransportParameterID: Since we=E2=80=99re only using the co=
de points 0
>> > to 13, we could save one byte per ID by using a varint.
>> > 2. for the length: We would save one more byte, as long as the length =
of
>> > the value is less than 16 byte (which will be the case for all values
>> > except the preferred_address).
>> > 3. For numeric values: This would apply to the flow control offsets, t=
he
>> > maximum stream IDs, the ack delay exponent , the maximum packet size a=
nd
>> > the max_ack_delay.
>> >
>> > In addition to the byte-savings of 1. and 2., 3. has some more desirab=
le
>> > properties:
>> >     1. It would allow us to encode the whole range of permitted values=
. For
>> > example, initial_max_data is a 62-bit value, but the current encoding =
just
>> > allows to send 4 bytes.
>> >     2. Depending on the value sent, this might or might not save a byt=
e
>> > here and there.
>> >     3. We=E2=80=99d be consistent with the encoding we use everywhere =
else.
>>


From nobody Mon Oct 29 15:35:36 2018
Return-Path: <martin.thomson@gmail.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 664CE131002 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 15:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 cteVAuWmM9cq for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 15:35:32 -0700 (PDT)
Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) (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 CAA5F1277CC for <quic@ietf.org>; Mon, 29 Oct 2018 15:35:32 -0700 (PDT)
Received: by mail-ot1-x32c.google.com with SMTP id 14so9271186oth.2 for <quic@ietf.org>; Mon, 29 Oct 2018 15:35:32 -0700 (PDT)
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=wxYoEEe3NeZVgPAQygR2dBgXDKpIuIQTDV2oLBW70HA=; b=DXeSBRPv96OSk2tqn3ILFS8Dt8Sc5TmSlP2L9L/wXbcvzzvUnVW8Gi85Tj+l9A7swx bjH3YUiv36bcwp/zV7T3qVb1cLCpohPuDS2Q1a/NWfOTnCE0iomgKSNUYa1PUhrbTqmR P3Il3fu8/bHpSRNQUwsIe5u5ipLrR4DJTwui/J60/jVGb7/SRoQLrKdCdX2/eDmL4h4T C/u4w+qnfvZ5n046eLjrJJ94BUHK5kXN1BkX4cSyWQHTQrAf41J5RCiHUC939Uv6JFdM 7YK4+sLX9rBdfZG2SM9bYr1ByIijWZf3TZVWRDuarPrnH7wgJMN/vpcAT3K/DPoLLxbD 6H9A==
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=wxYoEEe3NeZVgPAQygR2dBgXDKpIuIQTDV2oLBW70HA=; b=ujlQL8kjBUhcPUt+eqEjvO3Js4ZLsIwTxbJ9Uczof8TAcpMdC2aaJ86HYeOucaVEFE 2itp6W+460+yFZHWFPj4tszjIKqd3FhQoLcElD7GuuJpZ1Sj7C3OWRdNUDFC+2Kd2HkC GiOzvfaqrnBoN47/JD362HM1llruw19YYRiIVInVldUYXR86lXVwUfvC2PHhA5cqABGB kZLVAIaAH08ai9uY8CFjx5w5uwY03CsCycabJP3iHVdOFwTIa5Jrz+doF2UAGVkguYK3 kCjGP9p09utR5+oT5Amo1GD4vre7G1r47Y0/bxCbGrX4TuKxgtsv7Jz/I/rjjTpV/Y5B PMqQ==
X-Gm-Message-State: AGRZ1gI4o1ZgiEF9NhT+03t6N/rhqHLAnZv7NkDdooAdszvktVkZWsAy SLP5k9LBgCfEbvH7/nIo0MmaU2j35VNuJrUnmC8=
X-Google-Smtp-Source: AJdET5ews1dy0lG8vW8yAuqtYinBjJDuOru+pFFymzlrN96hFFIV02cocwLD0Nf1RAsHMruEDyjpIRAY99SuMtU/MkU=
X-Received: by 2002:a9d:6101:: with SMTP id i1mr10328440otj.310.1540852532126;  Mon, 29 Oct 2018 15:35:32 -0700 (PDT)
MIME-Version: 1.0
References: <CABkgnnVFqdx4VYbqT7SztPf8Q+vWMV86VkOHY-4aGSpauNPapg@mail.gmail.com> <851_1540819578_5BD70A7A_851_343_1_0ada4f1d-e8c5-25b5-0e8b-8111ee726ae7@orange.com>
In-Reply-To: <851_1540819578_5BD70A7A_851_343_1_0ada4f1d-e8c5-25b5-0e8b-8111ee726ae7@orange.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 30 Oct 2018 09:35:22 +1100
Message-ID: <CABkgnnVG6tT_h9AyoOSBd6qy5eRn0EZ4LO_Z+h-cTgj+MkECmA@mail.gmail.com>
Subject: Re: Big changes in -17
To: alexandre.ferrieux@orange.com
Cc: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/hafnRahlFVPKONsqP4bFJZngkKE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 22:35:34 -0000

On Tue, Oct 30, 2018 at 12:26 AM <alexandre.ferrieux@orange.com> wrote:
> Do I assume correctly that "the designs discussed" are the following three:
>
>   - nothing (no spin bit)
>   - spin bit alone
>   - spin bit + VEC
>
> Or is there room for other (written) proposals ?

You should refer to the email from Lars.  I believe that the approach
they propose only considers "no spin bit" vs. "spin bit alone".


From nobody Mon Oct 29 15:50:25 2018
Return-Path: <ilubashe@akamai.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 7E1CD131021 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 15:50:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.17
X-Spam-Level: 
X-Spam-Status: No, score=-1.17 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, KHOP_DYNAMIC=1.999, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 HSCZ3RnKCvrz for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 15:50:20 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 605D61277CC for <quic@ietf.org>; Mon, 29 Oct 2018 15:50:20 -0700 (PDT)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.23/8.16.0.23) with SMTP id w9TMklEW018559; Mon, 29 Oct 2018 22:50:08 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=CFb0dUov7XwlgtsPR2xJge8rQEqBsH4uV5MKwbEm3+c=; b=jZQfc4lFHDjDli1JDTHMj5wnuMDs807Y05fJsqk+IYU/wQ6XS7eqPctqjpWXQnSby8t7 yH0xjWVxbgAvZHnrbPTfldp8isWkIwcj8NCgdW6S1bQGgpnnyGq/pyVrLVS9xuBPgXdG x730BVD8Db5pPy021/IfY9vsQfHb3B+x9uU12resWtew10N/to5kjamiSy/bCaigDxGK KZRI/OnxJRNp+JfBcC++txQjvzAJoisCWQH6FYXVze7RxQuPKEjM/B/AEfYWdtDRldxT 42D3o5XfFfTTu9fPwZjMZXxJCSUr1cENCLTuTel/aMZ89r8SGuzPr5pmR4kzUpo2vLx7 Og== 
Received: from prod-mail-ppoint4 (a96-6-114-87.deploy.static.akamaitechnologies.com [96.6.114.87] (may be forged)) by mx0b-00190b01.pphosted.com with ESMTP id 2ndgbebtva-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 29 Oct 2018 22:50:08 +0000
Received: from pps.filterd (prod-mail-ppoint4.akamai.com [127.0.0.1]) by prod-mail-ppoint4.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w9TMZAaw020419; Mon, 29 Oct 2018 18:50:08 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.30]) by prod-mail-ppoint4.akamai.com with ESMTP id 2nckbw99np-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 29 Oct 2018 18:50:07 -0400
Received: from usma1ex-dag1mb6.msg.corp.akamai.com (172.27.123.65) by usma1ex-dag1mb6.msg.corp.akamai.com (172.27.123.65) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Mon, 29 Oct 2018 18:50:06 -0400
Received: from usma1ex-dag1mb6.msg.corp.akamai.com ([172.27.123.65]) by usma1ex-dag1mb6.msg.corp.akamai.com ([172.27.123.65]) with mapi id 15.00.1365.000; Mon, 29 Oct 2018 18:50:06 -0400
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Christian Huitema <huitema@huitema.net>
CC: Tommy Pauly <tpauly@apple.com>, Jana Iyengar <jri.ietf@gmail.com>, "Ian Swett" <ianswett@google.com>, QUIC WG <quic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>
Subject: RE: flow control and DATAGRAM
Thread-Topic: flow control and DATAGRAM
Thread-Index: AQHUb0aOcr0oK2RjxUS//IweRKrnD6U2a2QAgAAvQ4CAAEeKAIAABpaA///KoZCAAF6fgP//wVTQ
Date: Mon, 29 Oct 2018 22:50:06 +0000
Message-ID: <a32685f0c2644b74a37e9598700a734c@usma1ex-dag1mb6.msg.corp.akamai.com>
References: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com> <CAKcm_gMDOyJC0AwOo2knN6AMxVbySjGsrLvjcC9A8UA9xcvcWw@mail.gmail.com> <19D3595B-8845-45B6-A60D-9E934DD49FAC@apple.com> <CACpbDcfk+GXb3aL5LG0wQM87thRGO5Y4Q+9cbXf5YuW1=jWCig@mail.gmail.com> <B7BE2454-2A4D-4323-B0A5-0D73BD4B819F@apple.com> <344a8a30b95441af988b675c2f887965@usma1ex-dag1mb6.msg.corp.akamai.com> <A8DFD881-924E-4838-8056-9FDBC9D3791D@huitema.net>
In-Reply-To: <A8DFD881-924E-4838-8056-9FDBC9D3791D@huitema.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.38.233]
Content-Type: multipart/alternative; boundary="_000_a32685f0c2644b74a37e9598700a734cusma1exdag1mb6msgcorpak_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-29_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810290199
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-29_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810290201
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7CBQiuk8l3_OhB9UBu5aKH70mb4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 22:50:23 -0000

--_000_a32685f0c2644b74a37e9598700a734cusma1exdag1mb6msgcorpak_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SSB0aGluayB3ZSBhcmUgaW4gYW4gYWdyZWVtZW50IGhlcmUuICBPbmUgZGVzaWduIGFsdGVybmF0
aXZlIGlzIG5vIGZsb3cgY29udHJvbCAob25seSBjb25nZXN0aW9uIGNvbnRyb2wpIGZvciBkYXRh
Z3JhbXMuICBCdXQgaW4gdGhhdCBjYXNlLCB0aGUgYXNzZXJ0aW9uIGJlbG93IGRvZXMgbm90IGhv
bGQsIHNpbmNlIHRoZSBzZWNvbmQgYnVsbGV0IGlzIGZhbHNlIGZvciDigJxwb2xsL3JlYWTigJ0t
YmFzZWQgaW1wbGVtZW50YXRpb25zIChvciBhbnkgb3RoZXIgaW1wbGVtZW50YXRpb24gdGhhdCBp
cyBub3QgYmFzZWQgb24g4oCcY2FsbGJhY2stb24tbmV0d29yay1yZWNlaXZlLXRocmVhZOKAnSBt
b2RlbCkuDQoNCj4gQUNLIHRvIGEgcGFja2V0IGNvbnRhaW5pbmcgYSBEQVRBR1JBTSBmcmFtZSBt
ZWFuczoNCj4gLSBUaGUgcGFja2V0IG1hZGUgaXQgYWNyb3NzIHRoZSBuZXR3b3JrIHRvIHRoZSBR
VUlDIGVuZHBvaW50IG9uIHRoZSBvdGhlciBzaWRlDQo+IC0gVGhlIFFVSUMgaW1wbGVtZW50YXRp
b24gd2lsbCBkZWxpdmVyIHRoZSBEQVRBR1JBTSBmcmFtZSB0byBhcHBsaWNhdGlvbiAoaXQgd29u
J3QgZHJvcCBpdCBsb2NhbGx5KQ0KDQoNCiAgKiAgIElnb3INCg0KRnJvbTogQ2hyaXN0aWFuIEh1
aXRlbWEgPGh1aXRlbWFAaHVpdGVtYS5uZXQ+DQpTZW50OiBNb25kYXksIE9jdG9iZXIgMjksIDIw
MTggNjoyOSBQTQ0KVG86IEx1YmFzaGV2LCBJZ29yIDxpbHViYXNoZUBha2FtYWkuY29tPg0KQ2M6
IFRvbW15IFBhdWx5IDx0cGF1bHlAYXBwbGUuY29tPjsgSmFuYSBJeWVuZ2FyIDxqcmkuaWV0ZkBn
bWFpbC5jb20+OyBJYW4gU3dldHQgPGlhbnN3ZXR0QGdvb2dsZS5jb20+OyBRVUlDIFdHIDxxdWlj
QGlldGYub3JnPjsgTWFydGluIFRob21zb24gPG1hcnRpbi50aG9tc29uQGdtYWlsLmNvbT4NClN1
YmplY3Q6IFJlOiBmbG93IGNvbnRyb2wgYW5kIERBVEFHUkFNDQoNCg0KT24gT2N0IDI5LCAyMDE4
LCBhdCAyOjI4IFBNLCBMdWJhc2hldiwgSWdvciA8aWx1YmFzaGVAYWthbWFpLmNvbTxtYWlsdG86
aWx1YmFzaGVAYWthbWFpLmNvbT4+IHdyb3RlOg0KPiBBQ0sgdG8gYSBwYWNrZXQgY29udGFpbmlu
ZyBhIERBVEFHUkFNIGZyYW1lIG1lYW5zOg0KPiAtIFRoZSBwYWNrZXQgbWFkZSBpdCBhY3Jvc3Mg
dGhlIG5ldHdvcmsgdG8gdGhlIFFVSUMgZW5kcG9pbnQgb24gdGhlIG90aGVyIHNpZGUNCj4gLSBU
aGUgUVVJQyBpbXBsZW1lbnRhdGlvbiB3aWxsIGRlbGl2ZXIgdGhlIERBVEFHUkFNIGZyYW1lIHRv
IGFwcGxpY2F0aW9uIChpdCB3b24ndCBkcm9wIGl0IGxvY2FsbHkpDQo+DQo+IERvZXMgdGhhdCBt
YWtlIHNlbnNlPw0KDQpUaGlzIG9ubHkgbWFrZXMgc2Vuc2UsIGlmIHRoZXJlIGlzIGFuIGVmZmVj
dGl2ZSBmbG93IGNvbnRyb2wgZm9yIERBVEFHUkFNcy4gIFRoZSBzcGVjIHNob3VsZCBiZSBpbXBs
ZW1lbnRhYmxlIGJ5IHBvbGwvcmVhZCBRVUlDIGltcGxlbWVudGF0aW9ucyBhcyB3ZWxsIGFzIGJ5
IGNhbGxiYWNrLW9uLW5ldHdvcmstcmVjZWl2ZS10aHJlYWQgaW1wbGVtZW50YXRpb25zLiAgVW5s
ZXNzIHRoZXJlIGlzIGFuIGVmZmVjdGl2ZSBmbG93IGNvbnRyb2wsIGEgYnVmZmVyaW5nIFFVSUMg
aW1wbGVtZW50YXRpb24gbXVzdCBiZSBhYmxlIHRvIGRpc2NhcmQgREFUQUdSQU1zLCBpZiB0aGUg
cmVjZWl2ZXIgYXBwIGlzIG5vdCBjYXRjaGluZyB1cC4gIFRoZSByZWNlaXZlciB3b3VsZCB0aGVu
IGhhdmUgdG8gaWdub3JlIGFsbCBub24tREFUQUdSQU0gZnJhbWVzIGluIHRoYXQgcGFja2V0LCBz
aW5jZSBpdCB3b3VsZCBiZSB1bmFibGUgdG8gQUNLIHRoZSBwYWNrZXQuICBJZiB0aGUgcmVjZWl2
ZXIgaXMgcHJvY2Vzc2luZyBEQVRBR1JBTXMgYW5kIFNUUkVBTXMgYXQgZGlmZmVyZW50IHNwZWVk
cywgZGVsaWJlcmF0ZSBkaXNjYXJkcyBvZiBwYWNrZXRzIGNvbnRhaW5pbmcgREFUQUdSQU1zIHdv
dWxkIGludGVyZmVyZSB3aXRoIHRoZSBjb25nZXN0aW9uIGNvbnRyb2wsIGVmZmVjdGl2ZWx5IEhP
TCBibG9ja2luZyBTVFJFQU1zLg0KDQpPbiB0aGUgb3RoZXIgaGFuZCwgRGF0YWdyYW0gd2lsbCBi
ZSB1c2VkIHRvIGNhcnJ5IHRoZSBtZWRpYSBmbG93cyBjdXJyZW50bHkgY2FycmllZCBvdmVyIFJU
UCwgYW5kIFJUUCBkb2VzIG5vdCBpbmNsdWRlIGFueSBraW5kIG9mIGZsb3cgY29udHJvbC4NCg0K
VGhlIGtub3duIHdlYWtuZXNzIG9mIFJUUCBpcyB0aGUgbGFjayBvZiBpbnRlZ3JhdGVkIGNvbmdl
c3Rpb24gY29udHJvbCBiZXR3ZWVuIGRhdGEgYW5kIG1lZGlhLCBkbyB0aGF0IGEgcGFyYWxsZWwg
ZGF0YSBkb3dubG9hZCBjYW4gamVvcGFyZGl6ZSAgdGhlIHF1YWxpdHkgb2YgdGhlIHJlYWwgdGlt
ZSBtZWRpYS4gQnV0IHRoYXQncyBhbiBhcmd1bWVudCBmb3IgY291bnRpbmcgdGhlIGRhdGFncmFt
cyBpbiB0aGUgY29uZ2VzdGlvbiBjb250cm9sIHdpbmRvdywgbm90IGFuIGFyZ3VtZW50IGZvciBm
bG93IGNvbnRyb2wuDQoNClRoZXJlIGlzIGFuIGFyZ3VtZW50IGZvciBjb250cm9sbGluZyB0aGUg
cmF0ZSBhdCB3aGljaCBtZWRpYSBpcyBzZW50LiBCdXQgdGhhdCdzIHR5cGljYWxseSBkb25lIGF0
IHRoZSBhcHAgbGF5ZXIsIGJ5IG5lZ290aWF0aW5nIGNvZGVjcyBhbmQgY29tcHJlc3Npb24gcGFy
YW1ldGVycy4NCg0KLS0gQ2hyaXN0aWFuIEh1aXRlbWENCg==

--_000_a32685f0c2644b74a37e9598700a734cusma1exdag1mb6msgcorpak_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1
IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZp
c2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5
Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvTGlz
dFBhcmFncmFwaCwgbGkuTXNvTGlzdFBhcmFncmFwaCwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGgNCgl7
bXNvLXN0eWxlLXByaW9yaXR5OjM0Ow0KCW1hcmdpbi10b3A6MGluOw0KCW1hcmdpbi1yaWdodDow
aW47DQoJbWFyZ2luLWJvdHRvbTowaW47DQoJbWFyZ2luLWxlZnQ6LjVpbjsNCgltYXJnaW4tYm90
dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
c2Fucy1zZXJpZjt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWww
DQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsN
CgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdp
bi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE5DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFs
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7
fQ0Kc3Bhbi5FbWFpbFN0eWxlMjANCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQpzcGFuLkVt
YWlsU3R5bGUyMQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWls
eToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCi5Nc29DaHBEZWZh
dWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0K
QHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAx
LjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24x
O30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0IGwwDQoJe21zby1saXN0LWlkOjU1MjU0
MDExMDsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsNCgltc28tbGlzdC10ZW1wbGF0ZS1pZHM6LTY3
NjcwMjgzNCAtMTY3NjAxNTAxMiA2NzY5ODY5MSA2NzY5ODY5MyA2NzY5ODY4OSA2NzY5ODY5MSA2
NzY5ODY5MyA2NzY5ODY4OSA2NzY5ODY5MSA2NzY5ODY5Mzt9DQpAbGlzdCBsMDpsZXZlbDENCgl7
bXNvLWxldmVsLXN0YXJ0LWF0OjA7DQoJbXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0K
CW1zby1sZXZlbC10ZXh0Oi07DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVs
LW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWls
eToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgltc28tZmFyZWFzdC1mb250LWZhbWlseTpDYWxpYnJp
Ow0KCW1zby1iaWRpLWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO30NCkBsaXN0IGwwOmxl
dmVsMg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6
bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9u
OmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7
fQ0KQGxpc3QgbDA6bGV2ZWwzDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCglt
c28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVs
LW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWls
eTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw0DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0
OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7
DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsN
Cglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw1DQoJe21zby1sZXZlbC1udW1i
ZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3Rv
cDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDot
LjI1aW47DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDYNCgl7
bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCglt
c28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7
DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBs
MDpsZXZlbDcNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10
ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBv
c2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9
DQpAbGlzdCBsMDpsZXZlbDgNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1z
by1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51
bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseToi
Q291cmllciBOZXciO30NCkBsaXN0IGwwOmxldmVsOQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1h
dDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25l
Ow0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47
DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwxDQoJe21zby1saXN0LWlkOjEyODg5
NzAyMzY7DQoJbXNvLWxpc3QtdHlwZTpoeWJyaWQ7DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOi0y
MDk2NDQ5NjQ4IC00NTIxNTEyMzYgNjc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEg
Njc2OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTM7fQ0KQGxpc3QgbDE6bGV2ZWwxDQoJ
e21zby1sZXZlbC1zdGFydC1hdDowOw0KCW1zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsN
Cgltc28tbGV2ZWwtdGV4dDotOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZl
bC1udW1iZXItcG9zaXRpb246bGVmdDsNCgltYXJnaW4tbGVmdDoyMy4yNXB0Ow0KCXRleHQtaW5k
ZW50Oi0uMjVpbjsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgltc28tZmFy
ZWFzdC1mb250LWZhbWlseTpDYWxpYnJpOw0KCW1zby1iaWRpLWZvbnQtZmFtaWx5OiJUaW1lcyBO
ZXcgUm9tYW4iO30NCkBsaXN0IGwxOmxldmVsMg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpi
dWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCglt
c28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJbWFyZ2luLWxlZnQ6NTkuMjVwdDsNCgl0
ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBs
MTpsZXZlbDMNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10
ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBv
c2l0aW9uOmxlZnQ7DQoJbWFyZ2luLWxlZnQ6OTUuMjVwdDsNCgl0ZXh0LWluZGVudDotLjI1aW47
DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwxOmxldmVsNA0KCXttc28tbGV2ZWwt
bnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10
YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgltYXJnaW4t
bGVmdDoxMzEuMjVwdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6U3ltYm9s
O30NCkBsaXN0IGwxOmxldmVsNQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJ
bXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwt
bnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJbWFyZ2luLWxlZnQ6MTY3LjI1cHQ7DQoJdGV4dC1pbmRl
bnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDE6bGV2ZWw2
DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7
DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjps
ZWZ0Ow0KCW1hcmdpbi1sZWZ0OjIwMy4yNXB0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250
LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDE6bGV2ZWw3DQoJe21zby1sZXZlbC1udW1iZXIt
Zm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9w
Om5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCW1hcmdpbi1sZWZ0OjIz
OS4yNXB0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxp
c3QgbDE6bGV2ZWw4DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2
ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXIt
cG9zaXRpb246bGVmdDsNCgltYXJnaW4tbGVmdDoyNzUuMjVwdDsNCgl0ZXh0LWluZGVudDotLjI1
aW47DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMTpsZXZlbDkNCgl7bXNv
LWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28t
bGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJ
bWFyZ2luLWxlZnQ6MzExLjI1cHQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5
OldpbmdkaW5nczt9DQpvbA0KCXttYXJnaW4tYm90dG9tOjBpbjt9DQp1bA0KCXttYXJnaW4tYm90
dG9tOjBpbjt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVk
ZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0t
PjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0K
PG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+
PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxp
bms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+SSB0aGluayB3ZSBhcmUgaW4gYW4gYWdyZWVtZW50IGhlcmUuJm5ic3A7IE9uZSBkZXNp
Z24gYWx0ZXJuYXRpdmUgaXMgbm8gZmxvdyBjb250cm9sIChvbmx5IGNvbmdlc3Rpb24gY29udHJv
bCkgZm9yIGRhdGFncmFtcy4mbmJzcDsgQnV0IGluIHRoYXQgY2FzZSwgdGhlIGFzc2VydGlvbiBi
ZWxvdyBkb2VzIG5vdCBob2xkLCBzaW5jZSB0aGUgc2Vjb25kIGJ1bGxldCBpcyBmYWxzZSBmb3Ig
4oCccG9sbC9yZWFk4oCdLWJhc2VkIGltcGxlbWVudGF0aW9ucw0KIChvciBhbnkgb3RoZXIgaW1w
bGVtZW50YXRpb24gdGhhdCBpcyBub3QgYmFzZWQgb24g4oCcY2FsbGJhY2stb24tbmV0d29yay1y
ZWNlaXZlLXRocmVhZOKAnSBtb2RlbCkuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZndDsgQUNL
IHRvIGEgcGFja2V0IGNvbnRhaW5pbmcgYSBEQVRBR1JBTSBmcmFtZSBtZWFuczo8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZndDsgLSBUaGUgcGFja2V0IG1hZGUgaXQgYWNy
b3NzIHRoZSBuZXR3b3JrIHRvIHRoZSBRVUlDIGVuZHBvaW50IG9uIHRoZSBvdGhlciBzaWRlPG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mZ3Q7IC0gVGhlIFFVSUMgaW1wbGVt
ZW50YXRpb24gd2lsbCBkZWxpdmVyIHRoZSBEQVRBR1JBTSBmcmFtZSB0byBhcHBsaWNhdGlvbiAo
aXQgd29uJ3QgZHJvcCBpdCBsb2NhbGx5KTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8dWwgc3R5bGU9Im1hcmdpbi10b3A6MGluIiB0
eXBlPSJkaXNjIj4NCjxsaSBjbGFzcz0iTXNvTGlzdFBhcmFncmFwaCIgc3R5bGU9Im1hcmdpbi1s
ZWZ0Oi0xMi43NXB0O21zby1saXN0OmwxIGxldmVsMSBsZm8yIj4NCklnb3I8bzpwPjwvbzpwPjwv
bGk+PC91bD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRp
diBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5n
OjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5Gcm9tOjwvYj4gQ2hyaXN0aWFuIEh1aXRlbWEgJmx0O2h1
aXRlbWFAaHVpdGVtYS5uZXQmZ3Q7IDxicj4NCjxiPlNlbnQ6PC9iPiBNb25kYXksIE9jdG9iZXIg
MjksIDIwMTggNjoyOSBQTTxicj4NCjxiPlRvOjwvYj4gTHViYXNoZXYsIElnb3IgJmx0O2lsdWJh
c2hlQGFrYW1haS5jb20mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBUb21teSBQYXVseSAmbHQ7dHBhdWx5
QGFwcGxlLmNvbSZndDs7IEphbmEgSXllbmdhciAmbHQ7anJpLmlldGZAZ21haWwuY29tJmd0Ozsg
SWFuIFN3ZXR0ICZsdDtpYW5zd2V0dEBnb29nbGUuY29tJmd0OzsgUVVJQyBXRyAmbHQ7cXVpY0Bp
ZXRmLm9yZyZndDs7IE1hcnRpbiBUaG9tc29uICZsdDttYXJ0aW4udGhvbXNvbkBnbWFpbC5jb20m
Z3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBmbG93IGNvbnRyb2wgYW5kIERBVEFHUkFNPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRv
bToxMi4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+T24gT2N0IDI5LCAyMDE4LCBhdCAyOjI4
IFBNLCBMdWJhc2hldiwgSWdvciAmbHQ7PGEgaHJlZj0ibWFpbHRvOmlsdWJhc2hlQGFrYW1haS5j
b20iPmlsdWJhc2hlQGFrYW1haS5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1
LjBwdCI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jmd0OyBBQ0sgdG8gYSBwYWNrZXQg
Y29udGFpbmluZyBhIERBVEFHUkFNIGZyYW1lIG1lYW5zOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+Jmd0OyAtIFRoZSBwYWNrZXQgbWFkZSBpdCBhY3Jvc3MgdGhlIG5ldHdv
cmsgdG8gdGhlIFFVSUMgZW5kcG9pbnQgb24gdGhlIG90aGVyIHNpZGU8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZndDsgLSBUaGUgUVVJQyBpbXBsZW1lbnRhdGlvbiB3aWxs
IGRlbGl2ZXIgdGhlIERBVEFHUkFNIGZyYW1lIHRvIGFwcGxpY2F0aW9uIChpdCB3b24ndCBkcm9w
IGl0IGxvY2FsbHkpPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mZ3Q7Jm5i
c3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mZ3Q7IERvZXMgdGhhdCBt
YWtlIHNlbnNlPzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGlzIG9ubHkgbWFrZXMgc2Vuc2Us
IGlmIHRoZXJlIGlzIGFuIGVmZmVjdGl2ZSBmbG93IGNvbnRyb2wgZm9yIERBVEFHUkFNcy4mbmJz
cDsgVGhlIHNwZWMgc2hvdWxkIGJlIGltcGxlbWVudGFibGUgYnkgcG9sbC9yZWFkIFFVSUMgaW1w
bGVtZW50YXRpb25zIGFzIHdlbGwgYXMgYnkgY2FsbGJhY2stb24tbmV0d29yay1yZWNlaXZlLXRo
cmVhZCBpbXBsZW1lbnRhdGlvbnMuJm5ic3A7IFVubGVzcyB0aGVyZSBpcyBhbiBlZmZlY3RpdmUN
CiBmbG93IGNvbnRyb2wsIGEgYnVmZmVyaW5nIFFVSUMgaW1wbGVtZW50YXRpb24gbXVzdCBiZSBh
YmxlIHRvIGRpc2NhcmQgREFUQUdSQU1zLCBpZiB0aGUgcmVjZWl2ZXIgYXBwIGlzIG5vdCBjYXRj
aGluZyB1cC4mbmJzcDsgVGhlIHJlY2VpdmVyIHdvdWxkIHRoZW4gaGF2ZSB0byBpZ25vcmUgYWxs
IG5vbi1EQVRBR1JBTSBmcmFtZXMgaW4gdGhhdCBwYWNrZXQsIHNpbmNlIGl0IHdvdWxkIGJlIHVu
YWJsZSB0byBBQ0sgdGhlIHBhY2tldC4mbmJzcDsgSWYgdGhlIHJlY2VpdmVyDQogaXMgcHJvY2Vz
c2luZyBEQVRBR1JBTXMgYW5kIFNUUkVBTXMgYXQgZGlmZmVyZW50IHNwZWVkcywgZGVsaWJlcmF0
ZSBkaXNjYXJkcyBvZiBwYWNrZXRzIGNvbnRhaW5pbmcgREFUQUdSQU1zIHdvdWxkIGludGVyZmVy
ZSB3aXRoIHRoZSBjb25nZXN0aW9uIGNvbnRyb2wsIGVmZmVjdGl2ZWx5IEhPTCBibG9ja2luZyBT
VFJFQU1zLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiB0aGUgb3RoZXIgaGFuZCwgRGF0YWdyYW0gd2lsbCBiZSB1
c2VkIHRvIGNhcnJ5IHRoZSBtZWRpYSBmbG93cyBjdXJyZW50bHkgY2FycmllZCBvdmVyIFJUUCwg
YW5kIFJUUCBkb2VzIG5vdCBpbmNsdWRlIGFueSBraW5kIG9mIGZsb3cgY29udHJvbC4mbmJzcDs8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhl
IGtub3duIHdlYWtuZXNzIG9mIFJUUCBpcyB0aGUgbGFjayBvZiBpbnRlZ3JhdGVkIGNvbmdlc3Rp
b24gY29udHJvbCBiZXR3ZWVuIGRhdGEgYW5kIG1lZGlhLCBkbyB0aGF0IGEgcGFyYWxsZWwgZGF0
YSBkb3dubG9hZCBjYW4gamVvcGFyZGl6ZSAmbmJzcDt0aGUgcXVhbGl0eSBvZiB0aGUgcmVhbCB0
aW1lIG1lZGlhLiBCdXQgdGhhdCdzIGFuIGFyZ3VtZW50IGZvciBjb3VudGluZyB0aGUgZGF0YWdy
YW1zIGluIHRoZQ0KIGNvbmdlc3Rpb24gY29udHJvbCB3aW5kb3csIG5vdCBhbiBhcmd1bWVudCBm
b3IgZmxvdyBjb250cm9sLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5UaGVyZSBpcyBhbiBhcmd1bWVudCBmb3IgY29udHJvbGxpbmcgdGhlIHJh
dGUgYXQgd2hpY2ggbWVkaWEgaXMgc2VudC4gQnV0IHRoYXQncyB0eXBpY2FsbHkgZG9uZSBhdCB0
aGUgYXBwIGxheWVyLCBieSBuZWdvdGlhdGluZyBjb2RlY3MgYW5kIGNvbXByZXNzaW9uIHBhcmFt
ZXRlcnMuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPi0tIENocmlzdGlhbiBIdWl0ZW1hJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_a32685f0c2644b74a37e9598700a734cusma1exdag1mb6msgcorpak_--


From nobody Mon Oct 29 15:52:19 2018
Return-Path: <martin.thomson@gmail.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 D19E3131028 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 15:52:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3
X-Spam-Level: ***
X-Spam-Status: No, score=3 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, GB_SUMOF=5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 FAabBixdXKtw for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 15:52:15 -0700 (PDT)
Received: from mail-ot1-x342.google.com (mail-ot1-x342.google.com [IPv6:2607:f8b0:4864:20::342]) (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 6AEDC1277CC for <quic@ietf.org>; Mon, 29 Oct 2018 15:52:15 -0700 (PDT)
Received: by mail-ot1-x342.google.com with SMTP id k9so9259725otl.10 for <quic@ietf.org>; Mon, 29 Oct 2018 15:52:15 -0700 (PDT)
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:content-transfer-encoding; bh=uR+k1AphLSWH/7q5Ao7X0MK+D6Aqu/dbjqKhiTd+jXg=; b=edDmmK/L+rzEK4QsYL3auCr73ybsoRlQWDcCG44oQZ5lzvIzO1PZ7tSBokx6Zzsedm 8sbO8QEn4tMcAuRx65Frl14yvbIK88TnY527FmAs4ZN7Vj6fpJDhpaOjTZZy8AgRhXIN xUGSSoiP/FVVI46vzv81QjxDyEPZGYNqjNsfVXHgWoz6cLxZgxZPo8yLtcto2vfftu5C PEcobuPbZFzfOhwuwaVv+G1gND6N9oPInucHvNLMAyhbNC89LXJMyLhJ1/OxziOv7X6e YjgZfRwFsMUyT56uQn862/3/os4QJNE2+3ylB30nJ/QO8WyaWfh397CqCedk7PaHSPzy PLNg==
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:content-transfer-encoding; bh=uR+k1AphLSWH/7q5Ao7X0MK+D6Aqu/dbjqKhiTd+jXg=; b=qlfsDf25gBGgWhWDGQqqcUwf7hIVW1zJ+cD3ntAzsAxlSPT8TN0GtYHky6JT9Lxa+r 4toPLWMICMUC/lN1ajd6HCIVcOZ8lsQAO4v9Qb3kws+Y0RIdUx6wz1CQPQbCXcHUTIL8 DtQ5TyGErhDZDgsjnEicBeYKiaqi4LfQTon9CNNvZE9aFRJBW4BqnBzPEDlw/i2W2exi SxhNH98ABlpsDSO5zhATtmicQ2kQiTz5Zq9msi9hOMAEKAYNDQxyfC6e9Ux3aRJc4tR0 P5BoyGuTZDAnRJ+vJV9CH0wy9mvcwN9ctgaXID3S2R1kl45qW3QoL2WLEvQm03WAQlsq tfzg==
X-Gm-Message-State: AGRZ1gKS3mTe2kItBMgMp6z2a/aDbB/E5c5vCDECSb/2J56NV5eYWxWI 0wLwKEhGklq6lQDUZLwacCkuO6GFXw79yWKjM5A=
X-Google-Smtp-Source: AJdET5e5FOer8EJALNx8Qu+6X8q8Niw9gb/npO9iwER79n8uLjrXboYH2t6PQgqPsYglB93k/qRNJoG5N3UAhb1iEJo=
X-Received: by 2002:a9d:7a48:: with SMTP id z8mr10819126otm.257.1540853534633;  Mon, 29 Oct 2018 15:52:14 -0700 (PDT)
MIME-Version: 1.0
References: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com> <CAKcm_gMDOyJC0AwOo2knN6AMxVbySjGsrLvjcC9A8UA9xcvcWw@mail.gmail.com> <19D3595B-8845-45B6-A60D-9E934DD49FAC@apple.com> <CACpbDcfk+GXb3aL5LG0wQM87thRGO5Y4Q+9cbXf5YuW1=jWCig@mail.gmail.com> <B7BE2454-2A4D-4323-B0A5-0D73BD4B819F@apple.com>
In-Reply-To: <B7BE2454-2A4D-4323-B0A5-0D73BD4B819F@apple.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 30 Oct 2018 09:52:04 +1100
Message-ID: <CABkgnnVsgNU8dm08-UGQZqyMP49KtXyV5bSDrWAto2t3x9VOcw@mail.gmail.com>
Subject: Re: flow control and DATAGRAM
To: Tommy Pauly <tpauly@apple.com>
Cc: Jana Iyengar <jri.ietf@gmail.com>, Ian Swett <ianswett@google.com>, QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/v_Ye1pTpkA_k-Uw_e0ZfO7wCbUU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 22:52:17 -0000

On Tue, Oct 30, 2018 at 7:01 AM Tommy Pauly <tpauly@apple.com> wrote:
> I'm not suggesting any changes to when the packet gets ack'ed=E2=80=94spe=
cifically, I was responding to Martin's hypothetical of having an ACK to a =
DATAGRAM frame meaning that the application had processed the frame. My imp=
ression is that the ACK to a packet containing a DATAGRAM frame means:
> - The packet made it across the network to the QUIC endpoint on the other=
 side
> - The QUIC implementation will deliver the DATAGRAM frame to application =
(it won't drop it locally)

That works.  If you allow for the possibility that an application that
is unable to process the DATAGRAM will be indistinguishable from QUIC
dropping it.  That is, if the application can't take the upcall
because it is too busy, then QUIC might not bother waiting.

> Having a separate outstanding data limit for the DATAGRAM "stream" is an =
interesting solution to the space. It would then have the nice property of =
not looking like traditional flow control. It could even be measured in num=
ber of frames, rather than bytes (depending on what the limiting factors ar=
e).

This is something I alluded to in my email.  I don't think that it
improves things much, other than perhaps insulating streams from the
excesses of DATAGRAM frames and vice versa.

If you have a limit, then you need to ensure that both endpoints agree
on its value eventually.  With DATAGRAM, you might think that it's
possible to add a new frame that expresses how much data was sent
(that is the sum of sizes of DATAGRAM frames).  That would run afoul
of reordering problems, where the limit is exceeded when delayed
DATAGRAM frames that are already counted, arrive after the accounting
frame.

You could limit the count to just lost DATAGRAM frames.  That would
allow a receiver to repair its view of how much was used.  However
that runs afoul of two problems: acknowledgments aren't reliable, and
packets can be declared lost and still delivered.  In both cases, the
sender can believe that frames didn't arrive and so increase their
report of "lost bytes" too much.  The receiver ends up with an
inflated view of what was consumed (as opposed to the value being
short).

If you wanted to solve this problem, you would probably need to have
per-frame tracking, which makes this a lot less lightweight than I
think we want.


From nobody Mon Oct 29 15:58:33 2018
Return-Path: <ietf@trammell.ch>
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 9874513104F for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 15:58:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 2V11ms-HwmTB for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 15:58:29 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [212.25.24.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A521131021 for <quic@ietf.org>; Mon, 29 Oct 2018 15:58:29 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id C71F5341AD2; Mon, 29 Oct 2018 23:58:26 +0100 (CET)
X-Iway-Path: 0
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/20439.13183); Mon, 29 Oct 2018 23:58:26 +0100 (CET)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Mon, 29 Oct 2018 23:58:26 +0100 (CET)
Received: from [145.14.214.39] (account ietf@trammell.ch HELO [10.11.33.83]) by switchplus-mail.ch (CommuniGate Pro SMTP 6.2.8) with ESMTPSA id 72030851; Mon, 29 Oct 2018 23:58:26 +0100
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_3B29313A-2F60-4AA9-8FB6-13605538C7CF"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: Structuring the BKK spin bit discussion
Date: Mon, 29 Oct 2018 23:58:25 +0100
In-Reply-To: <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com>
Cc: Christian Huitema <huitema@huitema.net>, Lars Eggert <lars@eggert.org>, QUIC WG <quic@ietf.org>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Martin Thomson <martin.thomson@gmail.com>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/e_RD7DxkvPeEGTEpDjkeQPs8ziE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 22:58:32 -0000

--Apple-Mail=_3B29313A-2F60-4AA9-8FB6-13605538C7CF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

hi Martin, Christian, all,

> On 29 Oct 2018, at 23:29, Martin Thomson <martin.thomson@gmail.com> =
wrote:
>=20
> On Tue, Oct 30, 2018 at 3:54 AM Christian Huitema =
<huitema@huitema.net> wrote:
>> I think the strongest objection to the spin bit was put up by Marten =
during the last interim: measuring the RTT with the spin bit discloses =
the use of hidden path segments like VPN. This issue was not discussed =
during the privacy analysis.
>=20
> I had assumed that was part of the analysis and it was covered by the
> assumption that spinning could be disabled

+1. Probabilistically disabling spinning, which seems necessary if we =
want some grease to help us reserve the right to change the semantics of =
the bit at the spin bit's location in the wire image, should ensure that =
endpoints that want to disable spinning for their own reasons will have =
a large anonymity set to hide in, even in a future with perfect =
implementation and deployment of the spin bit.

>> One solution would be to remove the spin bit from the spec, trading =
off better privacy for worse management. I am considering another =
solution in which privacy sensitive clients hide the RTT by controlling =
the spin, for example spinning at fixed intervals. I plan testing that =
option in Picoquic.
>=20
> I've done a little thinking about this one, and it might conflict with
> the natural signals the transport emits, along the lines of what
> Andrew McGregor has mentioned on a couple of occasions.  If the spin
> bit is enabled, then privacy-sensitive endpoints will need to make a
> hard call regarding standing out.
>=20
> Note also that you probably can't hide the fact that you aren't at the
> same network location as the address you are using.  Spoofing a
> shorter RTT is impossible in general because you have to assume edges
> that haven't arrived yet.  If there are no edges you expose the
> charade.

You cannot reliably hide the fact that you're not at the same network =
location as the address you're using, spin bit or no. Most of the =
methods I know of for detecting people trying to hide where they're =
coming from don't rely on RTT at all. (Yes, I'm a Netflix customer who =
relies on Hurricane Electric's tunnel broker for IPv6 connectivity, why =
do you ask? ;) )

The recent academic work I'm aware of in this space (Weinberg et al "How =
to Catch When Proxies Lie", to appear at IMC this week) uses minimum RTT =
(with injected active measurement traffic) to conservatively draw =
exclusion circles to show that VPN providers that promise exits in =
certain countries probably don't actually deliver them. Not being =
vulnerable to this kind of exclusion analysis requires that you actually =
inject latency, not just in the spin bit, but over the entire flow =
(including the handshake).

RTT *higher* (even much higher) than an expected range for a given =
address pair isn't reliable enough to derive any sort of verdict from, =
due to the nature of delay and delay variability in the Internet.

So while I guess you can lie with the spin bit (even using rudimentary =
signal processing magic to take an assumed real RTT and make it look =
like a given lower target RTT, as long as you're not too worried about =
getting caught when your assumptions fail to hold), it's probably =
neither necessary nor sufficient to do so to hide a VPN exit. It's =
cheaper and more effective to just turn it off and hope.

Cheers,

Brian


--Apple-Mail=_3B29313A-2F60-4AA9-8FB6-13605538C7CF
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAlvXkJEACgkQihK3vwvq
RqN6Tg//TZLyxLyZLnZj2b34H885ara4Ah0yXS0OVm7Skhxtc3b8VWAnAvPp7SRO
ROXoMbjX2DMCbPRr/Fje1RF6OTLgPgn5725bwzvODFMC5mhwBa032MDxEdXgFUM9
GJv/u0NQ/WLmrLQsvg+A6Z6InEFAZFslC4fpmDaRUZNz64DFWPev3RvueBje212o
0GxqZOcNqTevc5Q6hMKvG9Yud5q10jsNoZ5YxR4+ZGXxUhFktjux0KcvCflOpCd+
1dTJP3oJRA/l8Rmpr9lv4eajbL8fBVnA+hfToMTcWdQUzEFVHqX3kvtEnPjIKZ0s
WKXwcRjtEuR9bYgLb8LWIgU23rmbm9DEjy2UMtf+auJUncMd1E6DfBnQkvhT0Oyx
1vt3NgxxqF7IdzZZ4wLvOfWT1PEpZYbD/30HQtnNY/BzNzfF/8v8i5qoCkvgxYVH
JgDvu28u9SH9osx0hm0LLNoxp+HtoUDjKmFs9mlUUuJjFHBOj8KX30o4OAUx4NJX
slQzKlo71ejuN04Y22vAdoS2WMog8ktqso5UH8BTcAv354SNqcy+vSwiL9HT9sSx
gKCT+GeZ0w1ZBgbBpoPHDyVH3vDXtpjfH3ecSHXnlwUpShktNdxEF/oaXfSAg5YE
TQbwEJb6fYUd60SQMaYKOEqkJLAEW8GpHKusMNKGLrBGcb+3xDM=
=c/zi
-----END PGP SIGNATURE-----

--Apple-Mail=_3B29313A-2F60-4AA9-8FB6-13605538C7CF--


From nobody Mon Oct 29 16:06:53 2018
Return-Path: <prvs=484051c544=fenix@fb.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 EB316131028 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 16:06:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.828
X-Spam-Level: ***
X-Spam-Status: No, score=3.828 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_SUMOF=5, KHOP_DYNAMIC=1.999, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=DyLW0bdW; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=b0QxPXUN
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 D9oiMLtQRwQG for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 16:06:50 -0700 (PDT)
Received: from mx0a-00082601.pphosted.com (mx0b-00082601.pphosted.com [67.231.153.30]) (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 78E68131021 for <quic@ietf.org>; Mon, 29 Oct 2018 16:06:50 -0700 (PDT)
Received: from pps.filterd (m0001255.ppops.net [127.0.0.1]) by mx0b-00082601.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w9TN2LMs027518; Mon, 29 Oct 2018 16:06:46 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=facebook; bh=kFDixJGpPF9KKFTKIm8L6dnA3fEKxa5LxZym/tOeqIw=; b=DyLW0bdWkiSCfhAOLwNRcSSIR0ydKjPFHRtRdtXUzbp9UWIrwXZ//MpFlsTUiD0uFu40 HuJDJlpnoUT0xW+qqvI1tJ1WuM9Bk3COb/xGMp9w8xWktefNvzb/XC+WbjKqmOiZgIY/ xrIGu2XW7Eps88/R0H3pVvJKIaJg539ZRrk= 
Received: from mail.thefacebook.com ([199.201.64.23]) by mx0b-00082601.pphosted.com with ESMTP id 2ne8u7gndq-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 29 Oct 2018 16:06:46 -0700
Received: from prn-hub03.TheFacebook.com (2620:10d:c081:35::127) by prn-hub03.TheFacebook.com (2620:10d:c081:35::127) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1531.3; Mon, 29 Oct 2018 16:06:44 -0700
Received: from PRN-CHUB08.TheFacebook.com (2620:10d:c081:35::17) by prn-hub03.TheFacebook.com (2620:10d:c081:35::127) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA) id 15.1.1531.3 via Frontend Transport; Mon, 29 Oct 2018 16:06:44 -0700
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (192.168.54.28) by o365-in.thefacebook.com (192.168.16.18) with Microsoft SMTP Server (TLS) id 14.3.361.1; Mon, 29 Oct 2018 16:06:44 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kFDixJGpPF9KKFTKIm8L6dnA3fEKxa5LxZym/tOeqIw=; b=b0QxPXUNHwiDBbK1W7UmCXRmUenpOiF0lx4Hax68elZJXwHyOnO4s5VS0uV1Mb5Gf90JlKzPduFvHvfwGkrK8hukV8YQhOoweZlxmtK4UKZezIrrfRaGQsZdyhypxj/JfCC/JpYoK5MlpDHzItnXoTgbj31BgBgk+OFUSm/FIiE=
Received: from BYAPR15MB2312.namprd15.prod.outlook.com (52.135.197.146) by BYAPR15MB2471.namprd15.prod.outlook.com (52.135.200.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1273.26; Mon, 29 Oct 2018 23:06:42 +0000
Received: from BYAPR15MB2312.namprd15.prod.outlook.com ([fe80::11c0:d70e:972b:7d51]) by BYAPR15MB2312.namprd15.prod.outlook.com ([fe80::11c0:d70e:972b:7d51%3]) with mapi id 15.20.1273.027; Mon, 29 Oct 2018 23:06:42 +0000
From: Roberto Peon <fenix@fb.com>
To: Martin Thomson <martin.thomson@gmail.com>, Tommy Pauly <tpauly@apple.com>
CC: Jana Iyengar <jri.ietf@gmail.com>, Ian Swett <ianswett@google.com>, "QUIC WG" <quic@ietf.org>
Subject: Re: flow control and DATAGRAM
Thread-Topic: flow control and DATAGRAM
Thread-Index: AQHUb0aT1DuXDxXj8U2a4gtuRLXs9aU2KFYAgAAvQoCAAEeKAIAABpeAgAAvvwD//469gA==
Date: Mon, 29 Oct 2018 23:06:42 +0000
Message-ID: <71FCFE79-D9FA-4240-B215-E19695C8BA1F@fb.com>
References: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com> <CAKcm_gMDOyJC0AwOo2knN6AMxVbySjGsrLvjcC9A8UA9xcvcWw@mail.gmail.com> <19D3595B-8845-45B6-A60D-9E934DD49FAC@apple.com> <CACpbDcfk+GXb3aL5LG0wQM87thRGO5Y4Q+9cbXf5YuW1=jWCig@mail.gmail.com> <B7BE2454-2A4D-4323-B0A5-0D73BD4B819F@apple.com> <CABkgnnVsgNU8dm08-UGQZqyMP49KtXyV5bSDrWAto2t3x9VOcw@mail.gmail.com>
In-Reply-To: <CABkgnnVsgNU8dm08-UGQZqyMP49KtXyV5bSDrWAto2t3x9VOcw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.12.0.181014
x-originating-ip: [2620:10d:c090:200::6:e9de]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR15MB2471; 20:cmbOahFd2f7rXMPxgVAaXM5MbVQSzR9rX35P7MYvxe9V0YyRYoqFvgHF48ICc400uZutHiZY9NDu07LGRyereux3Xny/nRtrwSEJGSfctvfQmeEdfIOPlUoL7hpddl8nC6GppHVIYRyy0qP8sIeArJJSit1LRibuHo3njCiIUo0=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 51d8e136-703b-43bb-9f68-08d63df330ea
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:BYAPR15MB2471; 
x-ms-traffictypediagnostic: BYAPR15MB2471:
x-microsoft-antispam-prvs: <BYAPR15MB24713E6FA3033460D175C400CDF30@BYAPR15MB2471.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(85827821059158)(31960201722614)(80524489315369); 
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(3231382)(11241501184)(944501410)(52105095)(148016)(149066)(150057)(6041310)(20161123564045)(20161123560045)(20161123562045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051)(76991095); SRVR:BYAPR15MB2471; BCL:0; PCL:0; RULEID:; SRVR:BYAPR15MB2471; 
x-forefront-prvs: 084080FC15
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(366004)(396003)(39860400002)(376002)(346002)(189003)(199004)(7736002)(53936002)(6512007)(81156014)(5250100002)(8676002)(81166006)(6246003)(6116002)(305945005)(54906003)(68736007)(4326008)(229853002)(25786009)(256004)(2906002)(97736004)(110136005)(14444005)(8936002)(551984002)(3480700004)(5660300001)(6436002)(76176011)(33656002)(14454004)(446003)(105586002)(36756003)(86362001)(106356001)(99286004)(6506007)(476003)(53546011)(11346002)(102836004)(316002)(71200400001)(2900100001)(83716004)(39060400002)(46003)(186003)(71190400001)(58126008)(93886005)(478600001)(82746002)(2616005)(6486002)(486006)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR15MB2471; H:BYAPR15MB2312.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: bzhCfsQYhrMzZgKK/bQuxHcJTqr+dYJe+NSDXx+Zb8p6snF55KuQ2hU4zWqSO0aXE6tMDb/KxzqN1iiodto9lb+pxfnjgSUCaohlgh4+1vdyoagQ31KD4YwwUq3qf0IK3WcZXJ/LQjjetz4I7BKB6fbDgQjl1ZLVmEHktsyPpqK5a+NrXP9FX5MMySAFQl0Y6SJ6NgKRNO4mPqCTXc/LJVAOGkF6uy2b/yJAt282z+BI2cIfAvhA+RzcGEbFU9DN8SGn1TSftTr/mU/v6NvyIMX9m9iIi7PnO1FAv9d+PdGStnHOFPn4H612bY1RH2Hh/CvEH15gv75AcK9GiL1LKPjlqyxKlwab5laqfhdURqw=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <97ED8E478A6D184383C34C407BA65C44@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 51d8e136-703b-43bb-9f68-08d63df330ea
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Oct 2018 23:06:42.5283 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR15MB2471
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-29_13:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/vQXEd1apfb5oOTVf7zz19wFxanY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 23:06:53 -0000

U3VjaCBwZXItZnJhbWUgdHJhY2tpbmcgY291bGQgYmUgYSBzaW5nbGUgYml0IGlmIHRoZSBwcm90
b2NvbCB1c2luZyBEQVRBR1JBTSBpcyB3aWxsaW5nIHRvIGRvIHdpbmRvd2VkIHVwZGF0ZXMgKGku
ZS4gMSBpbiBmbGlnaHQgYXQgb25jZSkgb2Ygc3VjaCB0aGluZ3MuDQotPVINCg0K77u/T24gMTAv
MjkvMTgsIDM6NTIgUE0sICJRVUlDIG9uIGJlaGFsZiBvZiBNYXJ0aW4gVGhvbXNvbiIgPHF1aWMt
Ym91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2YgbWFydGluLnRob21zb25AZ21haWwuY29tPiB3
cm90ZToNCg0KICAgIE9uIFR1ZSwgT2N0IDMwLCAyMDE4IGF0IDc6MDEgQU0gVG9tbXkgUGF1bHkg
PHRwYXVseUBhcHBsZS5jb20+IHdyb3RlOg0KICAgID4gSSdtIG5vdCBzdWdnZXN0aW5nIGFueSBj
aGFuZ2VzIHRvIHdoZW4gdGhlIHBhY2tldCBnZXRzIGFjaydlZOKAlHNwZWNpZmljYWxseSwgSSB3
YXMgcmVzcG9uZGluZyB0byBNYXJ0aW4ncyBoeXBvdGhldGljYWwgb2YgaGF2aW5nIGFuIEFDSyB0
byBhIERBVEFHUkFNIGZyYW1lIG1lYW5pbmcgdGhhdCB0aGUgYXBwbGljYXRpb24gaGFkIHByb2Nl
c3NlZCB0aGUgZnJhbWUuIE15IGltcHJlc3Npb24gaXMgdGhhdCB0aGUgQUNLIHRvIGEgcGFja2V0
IGNvbnRhaW5pbmcgYSBEQVRBR1JBTSBmcmFtZSBtZWFuczoNCiAgICA+IC0gVGhlIHBhY2tldCBt
YWRlIGl0IGFjcm9zcyB0aGUgbmV0d29yayB0byB0aGUgUVVJQyBlbmRwb2ludCBvbiB0aGUgb3Ro
ZXIgc2lkZQ0KICAgID4gLSBUaGUgUVVJQyBpbXBsZW1lbnRhdGlvbiB3aWxsIGRlbGl2ZXIgdGhl
IERBVEFHUkFNIGZyYW1lIHRvIGFwcGxpY2F0aW9uIChpdCB3b24ndCBkcm9wIGl0IGxvY2FsbHkp
DQogICAgDQogICAgVGhhdCB3b3Jrcy4gIElmIHlvdSBhbGxvdyBmb3IgdGhlIHBvc3NpYmlsaXR5
IHRoYXQgYW4gYXBwbGljYXRpb24gdGhhdA0KICAgIGlzIHVuYWJsZSB0byBwcm9jZXNzIHRoZSBE
QVRBR1JBTSB3aWxsIGJlIGluZGlzdGluZ3Vpc2hhYmxlIGZyb20gUVVJQw0KICAgIGRyb3BwaW5n
IGl0LiAgVGhhdCBpcywgaWYgdGhlIGFwcGxpY2F0aW9uIGNhbid0IHRha2UgdGhlIHVwY2FsbA0K
ICAgIGJlY2F1c2UgaXQgaXMgdG9vIGJ1c3ksIHRoZW4gUVVJQyBtaWdodCBub3QgYm90aGVyIHdh
aXRpbmcuDQogICAgDQogICAgPiBIYXZpbmcgYSBzZXBhcmF0ZSBvdXRzdGFuZGluZyBkYXRhIGxp
bWl0IGZvciB0aGUgREFUQUdSQU0gInN0cmVhbSIgaXMgYW4gaW50ZXJlc3Rpbmcgc29sdXRpb24g
dG8gdGhlIHNwYWNlLiBJdCB3b3VsZCB0aGVuIGhhdmUgdGhlIG5pY2UgcHJvcGVydHkgb2Ygbm90
IGxvb2tpbmcgbGlrZSB0cmFkaXRpb25hbCBmbG93IGNvbnRyb2wuIEl0IGNvdWxkIGV2ZW4gYmUg
bWVhc3VyZWQgaW4gbnVtYmVyIG9mIGZyYW1lcywgcmF0aGVyIHRoYW4gYnl0ZXMgKGRlcGVuZGlu
ZyBvbiB3aGF0IHRoZSBsaW1pdGluZyBmYWN0b3JzIGFyZSkuDQogICAgDQogICAgVGhpcyBpcyBz
b21ldGhpbmcgSSBhbGx1ZGVkIHRvIGluIG15IGVtYWlsLiAgSSBkb24ndCB0aGluayB0aGF0IGl0
DQogICAgaW1wcm92ZXMgdGhpbmdzIG11Y2gsIG90aGVyIHRoYW4gcGVyaGFwcyBpbnN1bGF0aW5n
IHN0cmVhbXMgZnJvbSB0aGUNCiAgICBleGNlc3NlcyBvZiBEQVRBR1JBTSBmcmFtZXMgYW5kIHZp
Y2UgdmVyc2EuDQogICAgDQogICAgSWYgeW91IGhhdmUgYSBsaW1pdCwgdGhlbiB5b3UgbmVlZCB0
byBlbnN1cmUgdGhhdCBib3RoIGVuZHBvaW50cyBhZ3JlZQ0KICAgIG9uIGl0cyB2YWx1ZSBldmVu
dHVhbGx5LiAgV2l0aCBEQVRBR1JBTSwgeW91IG1pZ2h0IHRoaW5rIHRoYXQgaXQncw0KICAgIHBv
c3NpYmxlIHRvIGFkZCBhIG5ldyBmcmFtZSB0aGF0IGV4cHJlc3NlcyBob3cgbXVjaCBkYXRhIHdh
cyBzZW50DQogICAgKHRoYXQgaXMgdGhlIHN1bSBvZiBzaXplcyBvZiBEQVRBR1JBTSBmcmFtZXMp
LiAgVGhhdCB3b3VsZCBydW4gYWZvdWwNCiAgICBvZiByZW9yZGVyaW5nIHByb2JsZW1zLCB3aGVy
ZSB0aGUgbGltaXQgaXMgZXhjZWVkZWQgd2hlbiBkZWxheWVkDQogICAgREFUQUdSQU0gZnJhbWVz
IHRoYXQgYXJlIGFscmVhZHkgY291bnRlZCwgYXJyaXZlIGFmdGVyIHRoZSBhY2NvdW50aW5nDQog
ICAgZnJhbWUuDQogICAgDQogICAgWW91IGNvdWxkIGxpbWl0IHRoZSBjb3VudCB0byBqdXN0IGxv
c3QgREFUQUdSQU0gZnJhbWVzLiAgVGhhdCB3b3VsZA0KICAgIGFsbG93IGEgcmVjZWl2ZXIgdG8g
cmVwYWlyIGl0cyB2aWV3IG9mIGhvdyBtdWNoIHdhcyB1c2VkLiAgSG93ZXZlcg0KICAgIHRoYXQg
cnVucyBhZm91bCBvZiB0d28gcHJvYmxlbXM6IGFja25vd2xlZGdtZW50cyBhcmVuJ3QgcmVsaWFi
bGUsIGFuZA0KICAgIHBhY2tldHMgY2FuIGJlIGRlY2xhcmVkIGxvc3QgYW5kIHN0aWxsIGRlbGl2
ZXJlZC4gIEluIGJvdGggY2FzZXMsIHRoZQ0KICAgIHNlbmRlciBjYW4gYmVsaWV2ZSB0aGF0IGZy
YW1lcyBkaWRuJ3QgYXJyaXZlIGFuZCBzbyBpbmNyZWFzZSB0aGVpcg0KICAgIHJlcG9ydCBvZiAi
bG9zdCBieXRlcyIgdG9vIG11Y2guICBUaGUgcmVjZWl2ZXIgZW5kcyB1cCB3aXRoIGFuDQogICAg
aW5mbGF0ZWQgdmlldyBvZiB3aGF0IHdhcyBjb25zdW1lZCAoYXMgb3Bwb3NlZCB0byB0aGUgdmFs
dWUgYmVpbmcNCiAgICBzaG9ydCkuDQogICAgDQogICAgSWYgeW91IHdhbnRlZCB0byBzb2x2ZSB0
aGlzIHByb2JsZW0sIHlvdSB3b3VsZCBwcm9iYWJseSBuZWVkIHRvIGhhdmUNCiAgICBwZXItZnJh
bWUgdHJhY2tpbmcsIHdoaWNoIG1ha2VzIHRoaXMgYSBsb3QgbGVzcyBsaWdodHdlaWdodCB0aGFu
IEkNCiAgICB0aGluayB3ZSB3YW50Lg0KICAgIA0KICAgIA0KDQo=


From nobody Mon Oct 29 16:08:41 2018
Return-Path: <ted.ietf@gmail.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 1B39113104F for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 16:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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_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=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 n4-gyvaXlBIe for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 16:08:38 -0700 (PDT)
Received: from mail-oi1-x233.google.com (mail-oi1-x233.google.com [IPv6:2607:f8b0:4864:20::233]) (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 C8721131021 for <quic@ietf.org>; Mon, 29 Oct 2018 16:08:37 -0700 (PDT)
Received: by mail-oi1-x233.google.com with SMTP id u130-v6so3986138oie.7 for <quic@ietf.org>; Mon, 29 Oct 2018 16:08:37 -0700 (PDT)
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=hZ12PioNHhqMRXgSX1CCiw0F85WBGF7Gnl22oWgpkrE=; b=E6c8zFEeTQkomsqoNeubaU0W6px7ObLn7M3jV33CL9Au7bXaypiKcVLHE88SWiriab MgoWa/6UhY03Q1dRqIqfyYiM04O+QWGrkVuM9cu2xBNt2aRjHC0s/7iknsZX7aoSaqOw PO/K0eyU0U9OHb8DpO+x43f1m/WMT4hqV/u4Fj7e6k0mfr5PzyZ/s2VHT1Ji4s3tgCNO gIvhA/bNQf3ZDVNnrqosOvH889peaVYNqEFS3LXSDXRdINoe7QNNqjAUbGsx+1MqBDRI o3Xc8LI6FaOo8ORrRe61X+Q7cvsusbWB7ZPB8qxiaG+IB+7VLS6YEE3r0rBI2ECd17P1 7RVQ==
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=hZ12PioNHhqMRXgSX1CCiw0F85WBGF7Gnl22oWgpkrE=; b=FT43wdpDkCFxcUNxB2Y8Ja99CWQUmvZiqt0Xpynif0oeDymNzUEHzLMjsb8W95rNJH THZ5ZCtOyGA9Uow6sl5exYTcLBEw6PwjvNsIeTIQymKH0x+Lk/A0hFvEsNk76dpakK7e 1EMyDOLfZwzlgmjh96ADBRK3Salp8I4jSVNl/1iicESpCs/X41wrrCBM/CSskqE61G9u g1UZIiGteQ2HvvjdYlCk/xkrHWUhyazcQZWcC4KsHvttCthGhj/30WygsMlmard7qW8g UResj9+oQ0m4ZJFWlu5aU1kTotxbZOtbMZwP9839S3CbcCPVGbPCL/JmiaA4ZkE3H8rz brxg==
X-Gm-Message-State: AGRZ1gI3hao2bYRJMcVJ8J8TfhSLpQCDKC5P1XdZXPlkR3nAZ+zEpWl3 QVsjaeRrVZUadLHiI5tFfC0pnb1djOopmpcYy+E=
X-Google-Smtp-Source: AJdET5c0Hi1xNYzujBTeqINQQHUi/q/Ewic1ZSinIqzLnh3lfNdHNf9J+SYQ2pSJkSnTUbwnQy6V0ImRslm0EDMC2M4=
X-Received: by 2002:aca:3408:: with SMTP id b8-v6mr9040108oia.270.1540854516853;  Mon, 29 Oct 2018 16:08:36 -0700 (PDT)
MIME-Version: 1.0
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com> <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch>
In-Reply-To: <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Mon, 29 Oct 2018 16:08:09 -0700
Message-ID: <CA+9kkMBb+-YYS3vvhvA1HZJuYZ7Q9cEBF=CW2FR08MPK0X=XoA@mail.gmail.com>
Subject: Re: Structuring the BKK spin bit discussion
To: Brian Trammell <ietf@trammell.ch>
Cc: Martin Thomson <martin.thomson@gmail.com>, Lars Eggert <lars@eggert.org>,  IETF QUIC WG <quic@ietf.org>, Christian Huitema <huitema@huitema.net>, dtikhonov@litespeedtech.com
Content-Type: multipart/alternative; boundary="00000000000020b937057966262c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2mnfi2URULqonqt06oOyYtx7jkM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 23:08:40 -0000

--00000000000020b937057966262c
Content-Type: text/plain; charset="UTF-8"

Just to add one additional piece of data here that was the basis of a lot
of discussion in the design team:  consider whether the handshake alone
discloses the data you are trying to protect.  For the case where you are
trying to obscure a hidden path segment like a VPN, a comparison of
handshake time to expected time is almost certainly enough.

regards,

Ted

On Mon, Oct 29, 2018 at 3:58 PM Brian Trammell (IETF) <ietf@trammell.ch>
wrote:

> hi Martin, Christian, all,
>
> > On 29 Oct 2018, at 23:29, Martin Thomson <martin.thomson@gmail.com>
> wrote:
> >
> > On Tue, Oct 30, 2018 at 3:54 AM Christian Huitema <huitema@huitema.net>
> wrote:
> >> I think the strongest objection to the spin bit was put up by Marten
> during the last interim: measuring the RTT with the spin bit discloses the
> use of hidden path segments like VPN. This issue was not discussed during
> the privacy analysis.
> >
> > I had assumed that was part of the analysis and it was covered by the
> > assumption that spinning could be disabled
>
> +1. Probabilistically disabling spinning, which seems necessary if we want
> some grease to help us reserve the right to change the semantics of the bit
> at the spin bit's location in the wire image, should ensure that endpoints
> that want to disable spinning for their own reasons will have a large
> anonymity set to hide in, even in a future with perfect implementation and
> deployment of the spin bit.
>
> >> One solution would be to remove the spin bit from the spec, trading off
> better privacy for worse management. I am considering another solution in
> which privacy sensitive clients hide the RTT by controlling the spin, for
> example spinning at fixed intervals. I plan testing that option in Picoquic.
> >
> > I've done a little thinking about this one, and it might conflict with
> > the natural signals the transport emits, along the lines of what
> > Andrew McGregor has mentioned on a couple of occasions.  If the spin
> > bit is enabled, then privacy-sensitive endpoints will need to make a
> > hard call regarding standing out.
> >
> > Note also that you probably can't hide the fact that you aren't at the
> > same network location as the address you are using.  Spoofing a
> > shorter RTT is impossible in general because you have to assume edges
> > that haven't arrived yet.  If there are no edges you expose the
> > charade.
>
> You cannot reliably hide the fact that you're not at the same network
> location as the address you're using, spin bit or no. Most of the methods I
> know of for detecting people trying to hide where they're coming from don't
> rely on RTT at all. (Yes, I'm a Netflix customer who relies on Hurricane
> Electric's tunnel broker for IPv6 connectivity, why do you ask? ;) )
>
> The recent academic work I'm aware of in this space (Weinberg et al "How
> to Catch When Proxies Lie", to appear at IMC this week) uses minimum RTT
> (with injected active measurement traffic) to conservatively draw exclusion
> circles to show that VPN providers that promise exits in certain countries
> probably don't actually deliver them. Not being vulnerable to this kind of
> exclusion analysis requires that you actually inject latency, not just in
> the spin bit, but over the entire flow (including the handshake).
>
> RTT *higher* (even much higher) than an expected range for a given address
> pair isn't reliable enough to derive any sort of verdict from, due to the
> nature of delay and delay variability in the Internet.
>
> So while I guess you can lie with the spin bit (even using rudimentary
> signal processing magic to take an assumed real RTT and make it look like a
> given lower target RTT, as long as you're not too worried about getting
> caught when your assumptions fail to hold), it's probably neither necessary
> nor sufficient to do so to hide a VPN exit. It's cheaper and more effective
> to just turn it off and hope.
>
> Cheers,
>
> Brian
>
>

--00000000000020b937057966262c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Just to add one additional piece of data here that wa=
s the basis of a lot of discussion in the design team:=C2=A0 consider wheth=
er the handshake alone discloses the data you are trying to protect.=C2=A0 =
For the case where you are trying to obscure a hidden path segment like a V=
PN, a comparison of handshake time to expected time is almost certainly eno=
ugh.=C2=A0 <br></div><div><br></div><div>regards,</div><div><br></div><div>=
Ted<br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Mon, =
Oct 29, 2018 at 3:58 PM Brian Trammell (IETF) &lt;<a href=3D"mailto:ietf@tr=
ammell.ch">ietf@trammell.ch</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">hi Martin, Christian, all,<br>
<br>
&gt; On 29 Oct 2018, at 23:29, Martin Thomson &lt;<a href=3D"mailto:martin.=
thomson@gmail.com" target=3D"_blank">martin.thomson@gmail.com</a>&gt; wrote=
:<br>
&gt; <br>
&gt; On Tue, Oct 30, 2018 at 3:54 AM Christian Huitema &lt;<a href=3D"mailt=
o:huitema@huitema.net" target=3D"_blank">huitema@huitema.net</a>&gt; wrote:=
<br>
&gt;&gt; I think the strongest objection to the spin bit was put up by Mart=
en during the last interim: measuring the RTT with the spin bit discloses t=
he use of hidden path segments like VPN. This issue was not discussed durin=
g the privacy analysis.<br>
&gt; <br>
&gt; I had assumed that was part of the analysis and it was covered by the<=
br>
&gt; assumption that spinning could be disabled<br>
<br>
+1. Probabilistically disabling spinning, which seems necessary if we want =
some grease to help us reserve the right to change the semantics of the bit=
 at the spin bit&#39;s location in the wire image, should ensure that endpo=
ints that want to disable spinning for their own reasons will have a large =
anonymity set to hide in, even in a future with perfect implementation and =
deployment of the spin bit.<br>
<br>
&gt;&gt; One solution would be to remove the spin bit from the spec, tradin=
g off better privacy for worse management. I am considering another solutio=
n in which privacy sensitive clients hide the RTT by controlling the spin, =
for example spinning at fixed intervals. I plan testing that option in Pico=
quic.<br>
&gt; <br>
&gt; I&#39;ve done a little thinking about this one, and it might conflict =
with<br>
&gt; the natural signals the transport emits, along the lines of what<br>
&gt; Andrew McGregor has mentioned on a couple of occasions.=C2=A0 If the s=
pin<br>
&gt; bit is enabled, then privacy-sensitive endpoints will need to make a<b=
r>
&gt; hard call regarding standing out.<br>
&gt; <br>
&gt; Note also that you probably can&#39;t hide the fact that you aren&#39;=
t at the<br>
&gt; same network location as the address you are using.=C2=A0 Spoofing a<b=
r>
&gt; shorter RTT is impossible in general because you have to assume edges<=
br>
&gt; that haven&#39;t arrived yet.=C2=A0 If there are no edges you expose t=
he<br>
&gt; charade.<br>
<br>
You cannot reliably hide the fact that you&#39;re not at the same network l=
ocation as the address you&#39;re using, spin bit or no. Most of the method=
s I know of for detecting people trying to hide where they&#39;re coming fr=
om don&#39;t rely on RTT at all. (Yes, I&#39;m a Netflix customer who relie=
s on Hurricane Electric&#39;s tunnel broker for IPv6 connectivity, why do y=
ou ask? ;) )<br>
<br>
The recent academic work I&#39;m aware of in this space (Weinberg et al &qu=
ot;How to Catch When Proxies Lie&quot;, to appear at IMC this week) uses mi=
nimum RTT (with injected active measurement traffic) to conservatively draw=
 exclusion circles to show that VPN providers that promise exits in certain=
 countries probably don&#39;t actually deliver them. Not being vulnerable t=
o this kind of exclusion analysis requires that you actually inject latency=
, not just in the spin bit, but over the entire flow (including the handsha=
ke).<br>
<br>
RTT *higher* (even much higher) than an expected range for a given address =
pair isn&#39;t reliable enough to derive any sort of verdict from, due to t=
he nature of delay and delay variability in the Internet.<br>
<br>
So while I guess you can lie with the spin bit (even using rudimentary sign=
al processing magic to take an assumed real RTT and make it look like a giv=
en lower target RTT, as long as you&#39;re not too worried about getting ca=
ught when your assumptions fail to hold), it&#39;s probably neither necessa=
ry nor sufficient to do so to hide a VPN exit. It&#39;s cheaper and more ef=
fective to just turn it off and hope.<br>
<br>
Cheers,<br>
<br>
Brian<br>
<br>
</blockquote></div>

--00000000000020b937057966262c--


From nobody Mon Oct 29 18:08:01 2018
Return-Path: <martin.thomson@gmail.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 835831288BD for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 18:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 q7Mf1zqz3ePF for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 18:07:57 -0700 (PDT)
Received: from mail-oi1-x22b.google.com (mail-oi1-x22b.google.com [IPv6:2607:f8b0:4864:20::22b]) (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 B16CB127332 for <quic@ietf.org>; Mon, 29 Oct 2018 18:07:57 -0700 (PDT)
Received: by mail-oi1-x22b.google.com with SMTP id f21-v6so5781433oig.1 for <quic@ietf.org>; Mon, 29 Oct 2018 18:07:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=1+RJCGw92Aftm002JD+AXtKxCsT+3v199DDD055Fwec=; b=QPNXJ1c4dn0yFn84NDrAAfIq4AgQRiDAKlzJJR2TZWj5l8GbHMBYZhsZXiCA0qMxZ8 WKMQID/8e6sSi894L1CAQUWeze1FteGl49wzXZSuUn/TX/npbyq4SDDESq52Z3gHcpQ0 REkGA3RyP/89BCL5wYEh9dQoiSzEXCKSpug6lCknxyHjAlSOFB3546UHbOxT27FCpvtY gCvwT63vg9EXYO8qxSebBA7vTt8Pz3n3+M4uV1nSFCBS85DC4m6Mv95wvUjl9cqqjGl8 g331VlFuA8FDOIDATBib+uikoiN70i2ZKbsfZU4VrBinmo0FXySpItI+7ngFbCxjafB8 PXWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=1+RJCGw92Aftm002JD+AXtKxCsT+3v199DDD055Fwec=; b=SSz58xL2Iy5rfDoXrhLdzM1keSzr/PhsOkqI6sziNy8iD1F5ZIgG0Brr+54oafJ8oM bwZVvv6zIrX+owIiPA7Qr9hfVaV4mST0W5MxBjhTvXBU5o0tosZM33+V1+N+vv+KyLUj 7HHoVWFvYr6YHbLFpJZnhD0SNqxbYpYIPHipUkwr2VvO2MMvlEzFDdk6yg22VGRBxw8S NCYZRvAM7d4rzhP5wh0JFzhM2CT1SyK4oHrNrGAOtt6iRIqH8V5/o8arg15H4m4gFUMj HCvoU6PAlmxw8358fUz7I5kU1Q84o4KPx+g0ArWQl7LHrsx+R1PBHVQQd6SjpCjCR8dX vSgg==
X-Gm-Message-State: AGRZ1gJxgogzQRMd4Y4Ii0LMtGjgLLx9PdZNJ2mXfUHjrD1iOFUNovYP AVi9/MGMs/kHZfCwuansi+sGMhKvrcjmj0p4muA/ADwmSLI=
X-Google-Smtp-Source: AJdET5fZLLsnCBJXxSGdfb2jY3piM6uBJXT+7+1PUJMCv+HVJM+R0OFA2gmKxYPQDb03+NSv+d9stIB6lsOorx9DipQ=
X-Received: by 2002:aca:3554:: with SMTP id c81-v6mr9315955oia.308.1540861675954;  Mon, 29 Oct 2018 18:07:55 -0700 (PDT)
MIME-Version: 1.0
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 30 Oct 2018 12:07:46 +1100
Message-ID: <CABkgnnXwmvCGcukYnQHU4sfAZFR24RT31O+BVqqnkZwB3Cp_Kw@mail.gmail.com>
Subject: Frame changes landing soon
To: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2PEv3DUJ4m3hJdRR-NgifjxLdFk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 01:07:59 -0000

I have some changes outstanding to frames for -17.  I would like to
resolve these so that I can do some cleanup.

https://github.com/quicwg/base-drafts/pull/1906 contains real changes
to the way that stream limits are signaled.

The discussion on https://github.com/quicwg/base-drafts/pull/1900
seems to be coming to a close (no pun intended, but appreciated
nonetheless).  That consolidates the description of APPLICATION_CLOSE
with CONNECTION_CLOSE (no wire format changes).

My current plan is to merge both of these in the next 24 hours.  That
will allow me to renumber frame types so that they start to make more
sense..  If you are interested in what that will look like, see
https://docs.google.com/spreadsheets/d/1G73qp-GBhXGyKEsZBudzWJY85FSa5txT4MxtVC5ajiE/edit?usp=sharing


From nobody Mon Oct 29 19:24:17 2018
Return-Path: <jri.ietf@gmail.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 B937C1288BD for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 19:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-0.001] 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 gjlmt7FX-7L4 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 19:24:13 -0700 (PDT)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 93DC812008A for <quic@ietf.org>; Mon, 29 Oct 2018 19:24:12 -0700 (PDT)
Received: by mail-lf1-x12a.google.com with SMTP id h192so7669264lfg.3 for <quic@ietf.org>; Mon, 29 Oct 2018 19:24:12 -0700 (PDT)
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=P7I5gr2z5y5yS/MLzDnmDstmcwwneD6mE6s56skPHUE=; b=uwmhEoTTRfEXePcruZjdyg2dOseSSFGJ2lIwYTE7bWW2rKCMQFmDk91N5NVG5lIqGD wMMSe8i0m16x3MWEzbOGVbPbQueef2xIveNZki0M+uCA1IvXMEUI7ukZmEpTX8dYtZTb Dd71ebq1FrS7XEhl5Uxi/2Bg+13QdFn7fnbmQwsuZFOJPDbDJRxtDoTDDSS4e9Wqp/SE RVxRX1OBmPqC/5VDqu56zVNQyW2UmHvoDjw2iLE0+drdW79l4B1y9j9AVO9dUIUjuKDE b6DQbwVC6qdyuwolXrS5ul3/Yzt0vZxl2kL6WLymTt4FpFKFSKpjsqBHEBHdBMJKGE6t q/jg==
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=P7I5gr2z5y5yS/MLzDnmDstmcwwneD6mE6s56skPHUE=; b=nFWrE7wFGCdOoJAAEAGqxO08BZAbUivk0G/ZLBcWXHsqpREN+hCgvyZB3OQOfLG33E kN6aZXui/5uO3Z/AzMOX23TsLAJDKfytM+0jjjT84UaBqmbNWnEtFcUKaQV5UjBjqEG+ Kv+B+L97oYyaE7qwBD3G3urFX6cMtsGPPNZwaa3BmjL93W+VWEheGg0A8+DQZ24eBykR DlohPFtOJP7SS1X28w8Gw54LYwhgv1zdX6rWXdU7BpaxO9QxxTroj3Ji3xZAgC0FMqNz KmgfAneXW6uL42RKqzD3P8qkfcVaPFm2CMsS9ngKYkWxSBy3WxomjftrkbB2bvgI9vhd Q9pw==
X-Gm-Message-State: AGRZ1gLz2DKDp9zazZaN4BZXQt596wEgcaJ5jU9uXPnK6yakBYlHKVml IxjDFwVn6IXguxF6DWhQuS1KBubintIYdys4THI=
X-Google-Smtp-Source: AJdET5cM6NoH8OENcgVWALzytfkmO03g3bfw2WnRP7kuuV+CA+oqu8EUOnkGFfSIOdaRYPuBxNLT3JZ9KunqFz81QGw=
X-Received: by 2002:a19:25c2:: with SMTP id l185-v6mr623800lfl.122.1540866250645;  Mon, 29 Oct 2018 19:24:10 -0700 (PDT)
MIME-Version: 1.0
References: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com> <CAKcm_gMDOyJC0AwOo2knN6AMxVbySjGsrLvjcC9A8UA9xcvcWw@mail.gmail.com> <19D3595B-8845-45B6-A60D-9E934DD49FAC@apple.com> <CACpbDcfk+GXb3aL5LG0wQM87thRGO5Y4Q+9cbXf5YuW1=jWCig@mail.gmail.com> <B7BE2454-2A4D-4323-B0A5-0D73BD4B819F@apple.com>
In-Reply-To: <B7BE2454-2A4D-4323-B0A5-0D73BD4B819F@apple.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Mon, 29 Oct 2018 19:23:59 -0700
Message-ID: <CACpbDcd5YWcxyEH3TS1FssgAT13oqeBBQg92+J0uJqhxPz2qkA@mail.gmail.com>
Subject: Re: flow control and DATAGRAM
To: tpauly@apple.com
Cc: Ian Swett <ianswett@google.com>, QUIC WG <quic@ietf.org>,  Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000008425a4057968e112"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/A-WWIRF5zZeH8_8bLRh4Rw7tPWU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 02:24:16 -0000

--0000000000008425a4057968e112
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hey Tommy,


> I'm not suggesting any changes to when the packet gets
> ack'ed=E2=80=94specifically, I was responding to Martin's hypothetical of=
 having an
> ACK to a DATAGRAM frame meaning that the application had processed the
> frame. My impression is that the ACK to a packet containing a DATAGRAM
> frame means:
> - The packet made it across the network to the QUIC endpoint on the other
> side
>

... and was processed by the QUIC receiver (not necessarily by the
application). This is the same semantic as the ack of a regular frame.


> - The QUIC implementation will deliver the DATAGRAM frame to application
> (it won't drop it locally)
>

In which case you will need flow control. If you agree, then we're on the
same page so far.


> Having a separate outstanding data limit for the DATAGRAM "stream" is an
> interesting solution to the space. It would then have the nice property o=
f
> not looking like traditional flow control. It could even be measured in
> number of frames, rather than bytes (depending on what the limiting facto=
rs
> are).
>

In terms of flow control, I don't think DATAGRAM flow control is any
different than sending stream data on any stream and then canceling it --
there are no retransmissions, but the sender still accounts for it in flow
control. My thought here was basically to have exactly the same flow
control as stream-level flow control, and allow for DATAGRAM bytes to fall
within connection-level flow control as normal.

The simplest scheme would be to reserve a stream ID for DATAGRAM data --
this could be 0 or 2^62-1 -- and then MAX_STREAM_DATA uses this stream ID
for flow control of DATAGRAM octets. Alternatively, define a new frame
called MAX_DATAGRAM_DATA that is carries the largest allowed offset that
can be sent as a DATAGRAM, and introduce an offset field in the DATAGRAM
frame.

- jana


> Thanks,
> Tommy
>
> On Oct 29, 2018, at 12:37 PM, Jana Iyengar <jri.ietf@gmail.com> wrote:
>
> Tommy,
>
> Changing the semantics of an acknowledgment to include delivery up to the
> application is a fundamental change to the QUIC machinery, and it doesn't
> work. First, an ACK frame acknowledges packets, and you can't have
> different semantics of an acknowledgment for different frames that are
> carried in the same packet. Second, it interferes with RTT measurement, a=
nd
> it conflates flow control with congestion control, which gets messy. (Thi=
s
> conflation is an interesting problem to consider theoretically, but not o=
ne
> for us at this time IMO.)
>
> I am wondering if applying a stream-level flow control for DATAGRAMs make=
s
> sense instead. Meaning that you treat DATAGRAMs as a separate stream for
> flow control purposes. You might benefit from having an offset in the
> DATAGRAM frame for this purpose.
>
> - jana
>
> On Mon, Oct 29, 2018 at 8:21 AM Tommy Pauly <tpauly@apple.com> wrote:
>
>> Hi Martin, Ian,
>>
>> Yes, very good points!
>>
>> My tendency would be to prefer what Ian's implementation does of passing
>> these DATAGRAM frames up immediately to the application. I don't think t=
hat
>> the acknowledgment needs to indicate that the frame was processed by the
>> application, but merely that it has been delivered to the application (t=
hat
>> is, the application doesn't get to do anything with the frame that can
>> influence the acknowledgment).
>>
>> The current draft indicates that the content of the DATAGRAM frames
>> contributes to the limit used for MAX_DATA, and that if that amount is
>> reached, the frames are blocked along with STREAM data. I think this wor=
ks
>> fine for the sender, while the receiver gets into the discussion you
>> present. On the sender side, reaching MAX_DATA could mean dropping the
>> DATAGRAM frames when unable to send more (and sending BLOCKED instead).
>> Since the frames are unreliable, they can be dropped in this situation
>> without violating the API contract.
>>
>> On the receiver side, I agree that queuing the DATAGRAM frames to let th=
e
>> application drive flow control in the way it does for STREAM frames adds
>> complexity and diminishes the utility of the frame and ACKs.. However, I
>> can imagine taking a fairly simplistic approach in which the data limit =
is
>> automatically increased upon reception of the frame (and the frame is
>> immediately passed to the application). This allows the initial_max_data=
 to
>> put a cap on the amount of data in a given flight of DATAGRAMS, and allo=
w
>> the size of a flight of DATAGRAM frames to be limited by the amount of r=
oom
>> left over from STREAM data that may be consuming the connection-wide flo=
w
>> control.
>>
>> Perhaps this approach needs a clearer name other than "flow control",
>> since it has a somewhat different meaning in effect.
>>
>> As for ACKs, if we never discard on the receiver side, the ACK is pretty
>> useful for detecting if there was network-based packet loss.
>>
>> Thanks,
>> Tommy
>>
>> On Oct 29, 2018, at 5:32 AM, Ian Swett <ianswett@google.com> wrote:
>>
>> Good catch Martin, I missed that in the draft as well, and I also think
>> it's impossibly with the proposed design.
>>
>> And yes, I think Martin's proposed solution is likely the only practical
>> one.  In my implementation, the frame is passed up to the application
>> immediately, so technically QUIC processed it, and it's the application'=
s
>> job to decide what to do with it.
>>
>> On Mon, Oct 29, 2018 at 1:16 AM Martin Thomson <martin.thomson@gmail.com=
>
>> wrote:
>>
>>> Hi Tommy,
>>>
>>> Your slides - <
>>> https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF103-QUIC=
-Datagram.pdf
>>> >
>>> - say that DATAGRAM frames respect connection-level flow control.  I
>>> missed that in the draft, and I don't know how they can do that in the
>>> face of packet loss, especially when you don't necessarily retransmit
>>> lost DATAGRAM frames.
>>>
>>> For that to work, you would need a bunch more machinery to make the
>>> connection-level flow control sync between endpoints in the case that
>>> packets are lost.  A disagreement about how much flow control is used
>>> causes things to break down badly.  Ian and I discussed this point at
>>> the last meeting and quickly agreed that while it might be nice to
>>> have flow control for this stuff, the increase in complexity is
>>> considerable and (at the time) we thought it wouldn't be worth it.
>>>
>>> The problem that introduces is that you could end up having too many
>>> DATAGRAM frames arrive.  The receiver has to drop something at the
>>> point that it can't handle them.  And we say that when you acknowledge
>>> something, you processed it.  That's tricky.
>>>
>>> It might be easier to say that a QUIC acknowledgment for a DATAGRAM
>>> frame doesn't mean that it was received and processed by an
>>> application.  An endpoint might discard these frames before passing
>>> them on to applications if it doesn't have space.  In other words,
>>> acknowledgment of DATAGRAM means that QUIC got it, not that the
>>> application got it.  Sadly, that means that the QUIC acknowledgment
>>> machinery doesn't help the application that uses DATAGRAM all that
>>> much.  Also, the lower bound on reliability is 0, which isn't the best
>>> thing ever.
>>>
>>> Hard choices, I know.  I don't have a good design for maintaining
>>> connection-level flow control (or any back pressure mechanism with
>>> equivalent properties) that doesn't add both complexity and overhead.
>>>
>>> Cheers,
>>> Martin
>>>
>>>
>>
>

--0000000000008425a4057968e112
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hey Tommy,<div class=3D"gmail_quote"><div>=C2=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div style=3D"word-wrap:break-word;line-break:af=
ter-white-space"><div>I&#39;m not suggesting any changes to when the packet=
 gets ack&#39;ed=E2=80=94specifically, I was responding to Martin&#39;s hyp=
othetical of having an ACK to a DATAGRAM frame meaning that the application=
 had processed the frame. My impression is that the ACK to a packet contain=
ing a DATAGRAM frame means:</div><div>- The packet made it across the netwo=
rk to the QUIC endpoint on the other side</div><div></div></div></blockquot=
e><div><br></div><div>... and was processed by the QUIC receiver (not neces=
sarily by the application). This is the same semantic as the ack of a regul=
ar frame.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=
=3D"word-wrap:break-word;line-break:after-white-space"><div>- The QUIC impl=
ementation will deliver the DATAGRAM frame to application (it won&#39;t dro=
p it locally)</div></div></blockquote><div><br></div><div>In which case you=
 will need flow control. If you agree, then we&#39;re on the same page so f=
ar.</div><div>=C2=A0=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=
=3D"word-wrap:break-word;line-break:after-white-space"><div>Having a separa=
te outstanding data limit for the DATAGRAM &quot;stream&quot; is an interes=
ting solution to the space. It would then have the nice property of not loo=
king like traditional flow control. It could even be measured in number of =
frames, rather than bytes (depending on what the limiting factors are).</di=
v></div></blockquote><div><br></div><div>In terms of flow control, I don&#3=
9;t think DATAGRAM flow control is any different than sending stream data o=
n any stream and then canceling it -- there are no retransmissions, but the=
 sender still accounts for it in flow control. My thought here was basicall=
y to have exactly the same flow control as stream-level flow control, and a=
llow for DATAGRAM bytes to fall within connection-level flow control as nor=
mal.</div><div><br></div><div>The simplest scheme would be to reserve a str=
eam ID for DATAGRAM data -- this could be 0 or 2^62-1 -- and then MAX_STREA=
M_DATA uses this stream ID for flow control of DATAGRAM octets. Alternative=
ly, define a new frame called MAX_DATAGRAM_DATA that is carries the largest=
 allowed offset that can be sent as a DATAGRAM, and introduce an offset fie=
ld in the DATAGRAM frame.</div><div><br></div><div>- jana</div><div>=C2=A0<=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word;line=
-break:after-white-space"><div>Thanks,</div><div>Tommy<br><div><br><blockqu=
ote type=3D"cite"><div>On Oct 29, 2018, at 12:37 PM, Jana Iyengar &lt;<a hr=
ef=3D"mailto:jri.ietf@gmail.com" target=3D"_blank">jri.ietf@gmail.com</a>&g=
t; wrote:</div><br class=3D"m_6117190503338714891Apple-interchange-newline"=
><div><div dir=3D"ltr">Tommy,<div><br></div><div>Changing the semantics of =
an acknowledgment to include delivery up to the application is a fundamenta=
l change to the QUIC machinery, and it doesn&#39;t work. First, an ACK fram=
e acknowledges packets, and you can&#39;t have different semantics of an ac=
knowledgment for different frames that are carried in the same packet. Seco=
nd, it interferes with RTT measurement, and it conflates flow control with =
congestion control, which gets messy. (This conflation is an interesting pr=
oblem to consider theoretically, but not one for us at this time IMO.)</div=
><div><br></div><div>I am wondering if applying a stream-level flow control=
 for DATAGRAMs makes sense instead. Meaning that you treat DATAGRAMs as a s=
eparate stream for flow control purposes. You might benefit from having an =
offset in the DATAGRAM frame for this purpose.</div><div><br></div><div>- j=
ana</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Mon, Oct =
29, 2018 at 8:21 AM Tommy Pauly &lt;<a href=3D"mailto:tpauly@apple.com" tar=
get=3D"_blank">tpauly@apple.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div style=3D"word-wrap:break-word;line-break:after-white-spa=
ce">Hi Martin, Ian,<div><br></div><div>Yes, very good points!</div><div><br=
></div><div>My tendency would be to prefer what Ian&#39;s implementation do=
es of passing these DATAGRAM frames up immediately to the application. I do=
n&#39;t think that the acknowledgment needs to indicate that the frame was =
processed by the application, but merely that it has been delivered to the =
application (that is, the application doesn&#39;t get to do anything with t=
he frame that can influence the acknowledgment).</div><div><br></div><div>T=
he current draft indicates that the content of the DATAGRAM frames contribu=
tes to the limit used for=C2=A0MAX_DATA, and that if that amount is reached=
, the frames are blocked along with STREAM data. I think this works fine fo=
r the sender, while the receiver gets into the discussion you present. On t=
he sender side, reaching MAX_DATA could mean dropping the DATAGRAM frames w=
hen unable to send more (and sending BLOCKED instead). Since the frames are=
 unreliable, they can be dropped in this situation without violating the AP=
I contract.=C2=A0</div><div><br></div><div>On the receiver side, I agree th=
at queuing the DATAGRAM frames to let the application drive flow control in=
 the way it does for STREAM frames adds complexity and diminishes the utili=
ty of the frame and ACKs.. However, I can imagine taking a fairly simplisti=
c approach in which the data limit is automatically increased upon receptio=
n of the frame (and the frame is immediately passed to the application). Th=
is allows the initial_max_data to put a cap on the amount of data in a give=
n flight of DATAGRAMS, and allow the size of a flight of DATAGRAM frames to=
 be limited by the amount of room left over from STREAM data that may be co=
nsuming the connection-wide flow control.=C2=A0</div><div><br></div><div>Pe=
rhaps this approach needs a clearer name other than &quot;flow control&quot=
;, since it has a somewhat different meaning in effect.</div><div><br></div=
><div>As for ACKs, if we never discard on the receiver side, the ACK is pre=
tty useful for detecting if there was network-based packet loss.</div><div>=
<br></div><div>Thanks,</div><div>Tommy=C2=A0</div><div><div><br><blockquote=
 type=3D"cite"><div>On Oct 29, 2018, at 5:32 AM, Ian Swett &lt;<a href=3D"m=
ailto:ianswett@google.com" target=3D"_blank">ianswett@google.com</a>&gt; wr=
ote:</div><br class=3D"m_6117190503338714891m_-1061371301160893898Apple-int=
erchange-newline"><div><div dir=3D"ltr">Good catch Martin, I missed that in=
 the draft as well, and I also think it&#39;s impossibly with the proposed =
design.<div><br></div><div>And yes, I think Martin&#39;s proposed solution =
is likely the only practical one.=C2=A0 In my implementation, the frame is =
passed up to the application immediately, so technically QUIC processed it,=
 and it&#39;s the application&#39;s job to decide what to do with it.</div>=
</div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Mon, Oct 29, 2018 =
at 1:16 AM Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gmail.com" t=
arget=3D"_blank">martin.thomson@gmail.com</a>&gt; wrote:<br></div><blockquo=
te class=3D"gmail_quote">Hi Tommy,<br>
<br>
Your slides - &lt;<a href=3D"https://github.com/quicwg/wg-materials/blob/ma=
ster/ietf103/IETF103-QUIC-Datagram.pdf" rel=3D"noreferrer" target=3D"_blank=
">https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF103-QUIC-D=
atagram.pdf</a>&gt;<br>
- say that DATAGRAM frames respect connection-level flow control.=C2=A0 I<b=
r>
missed that in the draft, and I don&#39;t know how they can do that in the<=
br>
face of packet loss, especially when you don&#39;t necessarily retransmit<b=
r>
lost DATAGRAM frames.<br>
<br>
For that to work, you would need a bunch more machinery to make the<br>
connection-level flow control sync between endpoints in the case that<br>
packets are lost.=C2=A0 A disagreement about how much flow control is used<=
br>
causes things to break down badly.=C2=A0 Ian and I discussed this point at<=
br>
the last meeting and quickly agreed that while it might be nice to<br>
have flow control for this stuff, the increase in complexity is<br>
considerable and (at the time) we thought it wouldn&#39;t be worth it.<br>
<br>
The problem that introduces is that you could end up having too many<br>
DATAGRAM frames arrive.=C2=A0 The receiver has to drop something at the<br>
point that it can&#39;t handle them.=C2=A0 And we say that when you acknowl=
edge<br>
something, you processed it.=C2=A0 That&#39;s tricky.<br>
<br>
It might be easier to say that a QUIC acknowledgment for a DATAGRAM<br>
frame doesn&#39;t mean that it was received and processed by an<br>
application.=C2=A0 An endpoint might discard these frames before passing<br=
>
them on to applications if it doesn&#39;t have space.=C2=A0 In other words,=
<br>
acknowledgment of DATAGRAM means that QUIC got it, not that the<br>
application got it.=C2=A0 Sadly, that means that the QUIC acknowledgment<br=
>
machinery doesn&#39;t help the application that uses DATAGRAM all that<br>
much.=C2=A0 Also, the lower bound on reliability is 0, which isn&#39;t the =
best<br>
thing ever.<br>
<br>
Hard choices, I know.=C2=A0 I don&#39;t have a good design for maintaining<=
br>
connection-level flow control (or any back pressure mechanism with<br>
equivalent properties) that doesn&#39;t add both complexity and overhead.<b=
r>
<br>
Cheers,<br>
Martin<br>
<br>
</blockquote></div>
</div></blockquote></div><br></div></div></blockquote></div>
</div></blockquote></div><br></div></div></blockquote></div></div>

--0000000000008425a4057968e112--


From nobody Mon Oct 29 20:55:02 2018
Return-Path: <ilubashe@akamai.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 304C91286D9 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 20:55:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.818
X-Spam-Level: 
X-Spam-Status: No, score=0.818 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, KHOP_DYNAMIC=1.999, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 4K3cH7fKsgpj for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 20:54:57 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 B671B126CB6 for <quic@ietf.org>; Mon, 29 Oct 2018 20:54:57 -0700 (PDT)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.23/8.16.0.23) with SMTP id w9U3poX3005241; Tue, 30 Oct 2018 03:54:53 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=V3pEXaGOaonCMDwTtzJqPdFl7h5F8dc9feZWLbfGlYQ=; b=HQ1xxLdj8m5vDff44bK8PLmzK+P6v7cr/hU5wvJStQ6YAHXTldjY1AuDukgfx5s/Yog/ L36W+Qh3FWOGn9wbEMZQdl6fzeEpsg4ggBAJeYQ3TkRYDTwOeQDiz3ynco7rqq02bbKl BpIlPuHXxWyHBmrO7CbZWTpPFvNPya6lZzQdBWlhmIZQ9YhUU1totweZ1WSI5BD09cdU P2nGXiTsJ8BILURDj+d4NsFLhwIdz9J94pBAcYF8DLDUL8rfcaSQqUCFX9TFkZNB/cbn 4QmC2Je7zaI6phRlejwnmxLS2Q/HMtN5fRzMFi/MTKkMV2M57U0AEkx0/HcDrBGWh9uo 0Q== 
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19]) by mx0b-00190b01.pphosted.com with ESMTP id 2neekh84r9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 30 Oct 2018 03:54:53 +0000
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w9U3o3mU022847; Mon, 29 Oct 2018 23:54:52 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.34]) by prod-mail-ppoint2.akamai.com with ESMTP id 2nckcaka7e-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 29 Oct 2018 23:54:52 -0400
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag1mb1.msg.corp.akamai.com (172.27.123.101) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Mon, 29 Oct 2018 23:54:52 -0400
Received: from usma1ex-dag1mb6.msg.corp.akamai.com (172.27.123.65) by usma1ex-dag1mb5.msg.corp.akamai.com (172.27.123.105) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Mon, 29 Oct 2018 23:54:51 -0400
Received: from usma1ex-dag1mb6.msg.corp.akamai.com ([172.27.123.65]) by usma1ex-dag1mb6.msg.corp.akamai.com ([172.27.123.65]) with mapi id 15.00.1365.000; Mon, 29 Oct 2018 23:54:51 -0400
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: "tpauly@apple.com" <tpauly@apple.com>, "jri.ietf@gmail.com" <jri.ietf@gmail.com>
CC: "quic@ietf.org" <quic@ietf.org>, "martin.thomson@gmail.com" <martin.thomson@gmail.com>, "ianswett@google.com" <ianswett@google.com>
Subject: RE: flow control and DATAGRAM
Thread-Topic: flow control and DATAGRAM
Thread-Index: AQHUb0aOcr0oK2RjxUS//IweRKrnD6U2a2QAgAAvQ4CAAEeKAIAABpaAgABq9ID//9ZW3Q==
Date: Tue, 30 Oct 2018 03:54:51 +0000
Message-ID: <4b7b02d110f74139bacae8e01c54a4af@usma1ex-dag1mb6.msg.corp.akamai.com>
References: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com> <CAKcm_gMDOyJC0AwOo2knN6AMxVbySjGsrLvjcC9A8UA9xcvcWw@mail.gmail.com> <19D3595B-8845-45B6-A60D-9E934DD49FAC@apple.com> <CACpbDcfk+GXb3aL5LG0wQM87thRGO5Y4Q+9cbXf5YuW1=jWCig@mail.gmail.com> <B7BE2454-2A4D-4323-B0A5-0D73BD4B819F@apple.com>, <CACpbDcd5YWcxyEH3TS1FssgAT13oqeBBQg92+J0uJqhxPz2qkA@mail.gmail.com>
In-Reply-To: <CACpbDcd5YWcxyEH3TS1FssgAT13oqeBBQg92+J0uJqhxPz2qkA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_4b7b02d110f74139bacae8e01c54a4afusma1exdag1mb6msgcorpak_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-30_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810300031
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-30_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810300032
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/b6X2R_DMv8TwRnTTc33EXvGN5OE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 03:55:00 -0000

--_000_4b7b02d110f74139bacae8e01c54a4afusma1exdag1mb6msgcorpak_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Jana,

> The simplest scheme would be to reserve a stream ID for DATAGRAM data -- =
[...]
> -- and then MAX_STREAM_DATA uses this
> stream ID for flow control of DATAGRAM octets.

There are many dragons that way. Flow control indicates commitment to buffe=
r data. When sender does not retransmit, when does receiver give up its com=
mitment to wait for (and buffer) earlier data so it can advance MAX_STREAM_=
DATA to allow the sender to send more data? Can the signal from sender tole=
rate loss/reordering vs STREAM frames (assuming the datagram can be split f=
or sending in multiple QUIC packets)? These dragons can be conquered (see m=
y partially reliable streams draft, v2 or v3), but this is not simple. :(

- Igor

-----Original Message-----
From: Jana Iyengar [jri.ietf@gmail.com]
Received: Monday, 29 Oct 2018, 10:24PM
To: tpauly@apple.com [tpauly@apple.com]
CC: Ian Swett [ianswett@google.com]; QUIC WG [quic@ietf.org]; Martin Thomso=
n [martin.thomson@gmail.com]
Subject: Re: flow control and DATAGRAM

Hey Tommy,

I'm not suggesting any changes to when the packet gets ack'ed=97specificall=
y, I was responding to Martin's hypothetical of having an ACK to a DATAGRAM=
 frame meaning that the application had processed the frame. My impression =
is that the ACK to a packet containing a DATAGRAM frame means:
- The packet made it across the network to the QUIC endpoint on the other s=
ide

... and was processed by the QUIC receiver (not necessarily by the applicat=
ion). This is the same semantic as the ack of a regular frame.

- The QUIC implementation will deliver the DATAGRAM frame to application (i=
t won't drop it locally)

In which case you will need flow control. If you agree, then we're on the s=
ame page so far.

Having a separate outstanding data limit for the DATAGRAM "stream" is an in=
teresting solution to the space. It would then have the nice property of no=
t looking like traditional flow control. It could even be measured in numbe=
r of frames, rather than bytes (depending on what the limiting factors are)=
.

In terms of flow control, I don't think DATAGRAM flow control is any differ=
ent than sending stream data on any stream and then canceling it -- there a=
re no retransmissions, but the sender still accounts for it in flow control=
. My thought here was basically to have exactly the same flow control as st=
ream-level flow control, and allow for DATAGRAM bytes to fall within connec=
tion-level flow control as normal.

The simplest scheme would be to reserve a stream ID for DATAGRAM data -- th=
is could be 0 or 2^62-1 -- and then MAX_STREAM_DATA uses this stream ID for=
 flow control of DATAGRAM octets. Alternatively, define a new frame called =
MAX_DATAGRAM_DATA that is carries the largest allowed offset that can be se=
nt as a DATAGRAM, and introduce an offset field in the DATAGRAM frame.

- jana

Thanks,
Tommy

On Oct 29, 2018, at 12:37 PM, Jana Iyengar <jri.ietf@gmail.com<mailto:jri.i=
etf@gmail.com>> wrote:

Tommy,

Changing the semantics of an acknowledgment to include delivery up to the a=
pplication is a fundamental change to the QUIC machinery, and it doesn't wo=
rk. First, an ACK frame acknowledges packets, and you can't have different =
semantics of an acknowledgment for different frames that are carried in the=
 same packet. Second, it interferes with RTT measurement, and it conflates =
flow control with congestion control, which gets messy. (This conflation is=
 an interesting problem to consider theoretically, but not one for us at th=
is time IMO.)

I am wondering if applying a stream-level flow control for DATAGRAMs makes =
sense instead. Meaning that you treat DATAGRAMs as a separate stream for fl=
ow control purposes. You might benefit from having an offset in the DATAGRA=
M frame for this purpose.

- jana

On Mon, Oct 29, 2018 at 8:21 AM Tommy Pauly <tpauly@apple.com<mailto:tpauly=
@apple.com>> wrote:
Hi Martin, Ian,

Yes, very good points!

My tendency would be to prefer what Ian's implementation does of passing th=
ese DATAGRAM frames up immediately to the application. I don't think that t=
he acknowledgment needs to indicate that the frame was processed by the app=
lication, but merely that it has been delivered to the application (that is=
, the application doesn't get to do anything with the frame that can influe=
nce the acknowledgment).

The current draft indicates that the content of the DATAGRAM frames contrib=
utes to the limit used for MAX_DATA, and that if that amount is reached, th=
e frames are blocked along with STREAM data. I think this works fine for th=
e sender, while the receiver gets into the discussion you present. On the s=
ender side, reaching MAX_DATA could mean dropping the DATAGRAM frames when =
unable to send more (and sending BLOCKED instead). Since the frames are unr=
eliable, they can be dropped in this situation without violating the API co=
ntract.

On the receiver side, I agree that queuing the DATAGRAM frames to let the a=
pplication drive flow control in the way it does for STREAM frames adds com=
plexity and diminishes the utility of the frame and ACKs.. However, I can i=
magine taking a fairly simplistic approach in which the data limit is autom=
atically increased upon reception of the frame (and the frame is immediatel=
y passed to the application). This allows the initial_max_data to put a cap=
 on the amount of data in a given flight of DATAGRAMS, and allow the size o=
f a flight of DATAGRAM frames to be limited by the amount of room left over=
 from STREAM data that may be consuming the connection-wide flow control.

Perhaps this approach needs a clearer name other than "flow control", since=
 it has a somewhat different meaning in effect.

As for ACKs, if we never discard on the receiver side, the ACK is pretty us=
eful for detecting if there was network-based packet loss.

Thanks,
Tommy

On Oct 29, 2018, at 5:32 AM, Ian Swett <ianswett@google.com<mailto:ianswett=
@google.com>> wrote:

Good catch Martin, I missed that in the draft as well, and I also think it'=
s impossibly with the proposed design.

And yes, I think Martin's proposed solution is likely the only practical on=
e.  In my implementation, the frame is passed up to the application immedia=
tely, so technically QUIC processed it, and it's the application's job to d=
ecide what to do with it.

On Mon, Oct 29, 2018 at 1:16 AM Martin Thomson <martin.thomson@gmail.com<ma=
ilto:martin.thomson@gmail.com>> wrote:
Hi Tommy,

Your slides - <https://github.com/quicwg/wg-materials/blob/master/ietf103/I=
ETF103-QUIC-Datagram.pdf<https://urldefense.proofpoint.com/v2/url?u=3Dhttps=
-3A__github.com_quicwg_wg-2Dmaterials_blob_master_ietf103_IETF103-2DQUIC-2D=
Datagram.pdf&d=3DDwMFaQ&c=3D96ZbZZcaMF4w0F4jpN6LZg&r=3DDjn3bQ5uNJDPM_2skfL3=
rW1tzcIxyjUZdn_m55KPmlo&m=3DBOGSfZ4hKaubJ6yww-9_8EDX3OccYvdip0g3k4t66hQ&s=
=3Dqiyr1YY1MHWjhIrPfwHXN6FCdsG8wUuhAuqczkosLlI&e=3D>>
- say that DATAGRAM frames respect connection-level flow control.  I
missed that in the draft, and I don't know how they can do that in the
face of packet loss, especially when you don't necessarily retransmit
lost DATAGRAM frames.

For that to work, you would need a bunch more machinery to make the
connection-level flow control sync between endpoints in the case that
packets are lost.  A disagreement about how much flow control is used
causes things to break down badly.  Ian and I discussed this point at
the last meeting and quickly agreed that while it might be nice to
have flow control for this stuff, the increase in complexity is
considerable and (at the time) we thought it wouldn't be worth it.

The problem that introduces is that you could end up having too many
DATAGRAM frames arrive.  The receiver has to drop something at the
point that it can't handle them.  And we say that when you acknowledge
something, you processed it.  That's tricky.

It might be easier to say that a QUIC acknowledgment for a DATAGRAM
frame doesn't mean that it was received and processed by an
application.  An endpoint might discard these frames before passing
them on to applications if it doesn't have space.  In other words,
acknowledgment of DATAGRAM means that QUIC got it, not that the
application got it.  Sadly, that means that the QUIC acknowledgment
machinery doesn't help the application that uses DATAGRAM all that
much.  Also, the lower bound on reliability is 0, which isn't the best
thing ever.

Hard choices, I know.  I don't have a good design for maintaining
connection-level flow control (or any back pressure mechanism with
equivalent properties) that doesn't add both complexity and overhead.

Cheers,
Martin




--_000_4b7b02d110f74139bacae8e01c54a4afusma1exdag1mb6msgcorpak_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta content=3D"text/html; charset=3Dutf-8">
</head>
<body>
<span style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:11=
pt; color:black">Jana,<br>
<br>
&gt; The simplest scheme would be to reserve a stream ID for DATAGRAM data =
-- [...]<br>
&gt; -- and then MAX_STREAM_DATA uses this<br>
&gt; stream ID for flow control of DATAGRAM octets.<br>
<br>
There are many dragons that way. Flow control indicates commitment to buffe=
r data. When sender does not retransmit, when does receiver give up its com=
mitment to wait for (and buffer) earlier data so it can advance MAX_STREAM_=
DATA to allow the sender to send
 more data? Can the signal from sender tolerate loss/reordering vs STREAM f=
rames (assuming the datagram can be split for sending in multiple QUIC pack=
ets)? These dragons can be conquered (see my partially reliable streams dra=
ft, v2 or v3), but this is not simple.
 :(<br>
<br>
- Igor<br>
<br>
<span style=3D"color:black">-----Original Message----- <br>
<b>From:</b> Jana Iyengar [jri.ietf@gmail.com]<br>
<b>Received:</b> Monday, 29 Oct 2018, 10:24PM<br>
<b>To:</b> tpauly@apple.com [tpauly@apple.com]<br>
<b>CC:</b> Ian Swett [ianswett@google.com]; QUIC WG [quic@ietf.org]; Martin=
 Thomson [martin.thomson@gmail.com]<br>
<b>Subject:</b> Re: flow control and DATAGRAM<br>
<br>
</span></span>
<div>
<div dir=3D"ltr">Hey Tommy,
<div class=3D"gmail_quote">
<div>&nbsp;</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1=
px #ccc solid; padding-left:1ex">
<div style=3D"word-wrap:break-word; line-break:after-white-space">
<div>I'm not suggesting any changes to when the packet gets ack'ed=97specif=
ically, I was responding to Martin's hypothetical of having an ACK to a DAT=
AGRAM frame meaning that the application had processed the frame. My impres=
sion is that the ACK to a packet containing
 a DATAGRAM frame means:</div>
<div>- The packet made it across the network to the QUIC endpoint on the ot=
her side</div>
<div></div>
</div>
</blockquote>
<div><br>
</div>
<div>... and was processed by the QUIC receiver (not necessarily by the app=
lication). This is the same semantic as the ack of a regular frame.</div>
<div>&nbsp;</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1=
px #ccc solid; padding-left:1ex">
<div style=3D"word-wrap:break-word; line-break:after-white-space">
<div>- The QUIC implementation will deliver the DATAGRAM frame to applicati=
on (it won't drop it locally)</div>
</div>
</blockquote>
<div><br>
</div>
<div>In which case you will need flow control. If you agree, then we're on =
the same page so far.</div>
<div>&nbsp;&nbsp;</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1=
px #ccc solid; padding-left:1ex">
<div style=3D"word-wrap:break-word; line-break:after-white-space">
<div>Having a separate outstanding data limit for the DATAGRAM &quot;stream=
&quot; is an interesting solution to the space. It would then have the nice=
 property of not looking like traditional flow control. It could even be me=
asured in number of frames, rather than bytes
 (depending on what the limiting factors are).</div>
</div>
</blockquote>
<div><br>
</div>
<div>In terms of flow control, I don't think DATAGRAM flow control is any d=
ifferent than sending stream data on any stream and then canceling it -- th=
ere are no retransmissions, but the sender still accounts for it in flow co=
ntrol. My thought here was basically
 to have exactly the same flow control as stream-level flow control, and al=
low for DATAGRAM bytes to fall within connection-level flow control as norm=
al.</div>
<div><br>
</div>
<div>The simplest scheme would be to reserve a stream ID for DATAGRAM data =
-- this could be 0 or 2^62-1 -- and then MAX_STREAM_DATA uses this stream I=
D for flow control of DATAGRAM octets. Alternatively, define a new frame ca=
lled MAX_DATAGRAM_DATA that is carries
 the largest allowed offset that can be sent as a DATAGRAM, and introduce a=
n offset field in the DATAGRAM frame.</div>
<div><br>
</div>
<div>- jana</div>
<div>&nbsp;</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1=
px #ccc solid; padding-left:1ex">
<div style=3D"word-wrap:break-word; line-break:after-white-space">
<div>Thanks,</div>
<div>Tommy<br>
<div><br>
<blockquote type=3D"cite">
<div>On Oct 29, 2018, at 12:37 PM, Jana Iyengar &lt;<a href=3D"mailto:jri.i=
etf@gmail.com" target=3D"_blank">jri.ietf@gmail.com</a>&gt; wrote:</div>
<br class=3D"m_6117190503338714891Apple-interchange-newline">
<div>
<div dir=3D"ltr">Tommy,
<div><br>
</div>
<div>Changing the semantics of an acknowledgment to include delivery up to =
the application is a fundamental change to the QUIC machinery, and it doesn=
't work. First, an ACK frame acknowledges packets, and you can't have diffe=
rent semantics of an acknowledgment
 for different frames that are carried in the same packet. Second, it inter=
feres with RTT measurement, and it conflates flow control with congestion c=
ontrol, which gets messy. (This conflation is an interesting problem to con=
sider theoretically, but not one
 for us at this time IMO.)</div>
<div><br>
</div>
<div>I am wondering if applying a stream-level flow control for DATAGRAMs m=
akes sense instead. Meaning that you treat DATAGRAMs as a separate stream f=
or flow control purposes. You might benefit from having an offset in the DA=
TAGRAM frame for this purpose.</div>
<div><br>
</div>
<div>- jana</div>
</div>
<br>
<div class=3D"gmail_quote">
<div dir=3D"ltr">On Mon, Oct 29, 2018 at 8:21 AM Tommy Pauly &lt;<a href=3D=
"mailto:tpauly@apple.com" target=3D"_blank">tpauly@apple.com</a>&gt; wrote:=
<br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1=
px #ccc solid; padding-left:1ex">
<div style=3D"word-wrap:break-word; line-break:after-white-space">Hi Martin=
, Ian,
<div><br>
</div>
<div>Yes, very good points!</div>
<div><br>
</div>
<div>My tendency would be to prefer what Ian's implementation does of passi=
ng these DATAGRAM frames up immediately to the application. I don't think t=
hat the acknowledgment needs to indicate that the frame was processed by th=
e application, but merely that it
 has been delivered to the application (that is, the application doesn't ge=
t to do anything with the frame that can influence the acknowledgment).</di=
v>
<div><br>
</div>
<div>The current draft indicates that the content of the DATAGRAM frames co=
ntributes to the limit used for&nbsp;MAX_DATA, and that if that amount is r=
eached, the frames are blocked along with STREAM data. I think this works f=
ine for the sender, while the receiver
 gets into the discussion you present. On the sender side, reaching MAX_DAT=
A could mean dropping the DATAGRAM frames when unable to send more (and sen=
ding BLOCKED instead). Since the frames are unreliable, they can be dropped=
 in this situation without violating
 the API contract.&nbsp;</div>
<div><br>
</div>
<div>On the receiver side, I agree that queuing the DATAGRAM frames to let =
the application drive flow control in the way it does for STREAM frames add=
s complexity and diminishes the utility of the frame and ACKs.. However, I =
can imagine taking a fairly simplistic
 approach in which the data limit is automatically increased upon reception=
 of the frame (and the frame is immediately passed to the application). Thi=
s allows the initial_max_data to put a cap on the amount of data in a given=
 flight of DATAGRAMS, and allow
 the size of a flight of DATAGRAM frames to be limited by the amount of roo=
m left over from STREAM data that may be consuming the connection-wide flow=
 control.&nbsp;</div>
<div><br>
</div>
<div>Perhaps this approach needs a clearer name other than &quot;flow contr=
ol&quot;, since it has a somewhat different meaning in effect.</div>
<div><br>
</div>
<div>As for ACKs, if we never discard on the receiver side, the ACK is pret=
ty useful for detecting if there was network-based packet loss.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Tommy&nbsp;</div>
<div>
<div><br>
<blockquote type=3D"cite">
<div>On Oct 29, 2018, at 5:32 AM, Ian Swett &lt;<a href=3D"mailto:ianswett@=
google.com" target=3D"_blank">ianswett@google.com</a>&gt; wrote:</div>
<br class=3D"m_6117190503338714891m_-1061371301160893898Apple-interchange-n=
ewline">
<div>
<div dir=3D"ltr">Good catch Martin, I missed that in the draft as well, and=
 I also think it's impossibly with the proposed design.
<div><br>
</div>
<div>And yes, I think Martin's proposed solution is likely the only practic=
al one.&nbsp; In my implementation, the frame is passed up to the applicati=
on immediately, so technically QUIC processed it, and it's the application'=
s job to decide what to do with it.</div>
</div>
<br>
<div class=3D"gmail_quote">
<div dir=3D"ltr">On Mon, Oct 29, 2018 at 1:16 AM Martin Thomson &lt;<a href=
=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomson@gmail=
.com</a>&gt; wrote:<br>
</div>
<blockquote class=3D"gmail_quote">Hi Tommy,<br>
<br>
Your slides - &lt;<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dh=
ttps-3A__github.com_quicwg_wg-2Dmaterials_blob_master_ietf103_IETF103-2DQUI=
C-2DDatagram.pdf&amp;d=3DDwMFaQ&amp;c=3D96ZbZZcaMF4w0F4jpN6LZg&amp;r=3DDjn3=
bQ5uNJDPM_2skfL3rW1tzcIxyjUZdn_m55KPmlo&amp;m=3DBOGSfZ4hKaubJ6yww-9_8EDX3Oc=
cYvdip0g3k4t66hQ&amp;s=3Dqiyr1YY1MHWjhIrPfwHXN6FCdsG8wUuhAuqczkosLlI&amp;e=
=3D" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/wg-mate=
rials/blob/master/ietf103/IETF103-QUIC-Datagram.pdf</a>&gt;<br>
- say that DATAGRAM frames respect connection-level flow control.&nbsp; I<b=
r>
missed that in the draft, and I don't know how they can do that in the<br>
face of packet loss, especially when you don't necessarily retransmit<br>
lost DATAGRAM frames.<br>
<br>
For that to work, you would need a bunch more machinery to make the<br>
connection-level flow control sync between endpoints in the case that<br>
packets are lost.&nbsp; A disagreement about how much flow control is used<=
br>
causes things to break down badly.&nbsp; Ian and I discussed this point at<=
br>
the last meeting and quickly agreed that while it might be nice to<br>
have flow control for this stuff, the increase in complexity is<br>
considerable and (at the time) we thought it wouldn't be worth it.<br>
<br>
The problem that introduces is that you could end up having too many<br>
DATAGRAM frames arrive.&nbsp; The receiver has to drop something at the<br>
point that it can't handle them.&nbsp; And we say that when you acknowledge=
<br>
something, you processed it.&nbsp; That's tricky.<br>
<br>
It might be easier to say that a QUIC acknowledgment for a DATAGRAM<br>
frame doesn't mean that it was received and processed by an<br>
application.&nbsp; An endpoint might discard these frames before passing<br=
>
them on to applications if it doesn't have space.&nbsp; In other words,<br>
acknowledgment of DATAGRAM means that QUIC got it, not that the<br>
application got it.&nbsp; Sadly, that means that the QUIC acknowledgment<br=
>
machinery doesn't help the application that uses DATAGRAM all that<br>
much.&nbsp; Also, the lower bound on reliability is 0, which isn't the best=
<br>
thing ever.<br>
<br>
Hard choices, I know.&nbsp; I don't have a good design for maintaining<br>
connection-level flow control (or any back pressure mechanism with<br>
equivalent properties) that doesn't add both complexity and overhead.<br>
<br>
Cheers,<br>
Martin<br>
<br>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</body>
</html>

--_000_4b7b02d110f74139bacae8e01c54a4afusma1exdag1mb6msgcorpak_--


From nobody Mon Oct 29 21:24:05 2018
Return-Path: <jri.ietf@gmail.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 AD7ED1288BD for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 21:24:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.01
X-Spam-Level: 
X-Spam-Status: No, score=-0.01 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, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 1etGGJOipcan for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 21:24:01 -0700 (PDT)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 6EC8E126CB6 for <quic@ietf.org>; Mon, 29 Oct 2018 21:24:00 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id c24-v6so7779250lfi.12 for <quic@ietf.org>; Mon, 29 Oct 2018 21:24:00 -0700 (PDT)
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=67BhmgGmmCSq9OPdFMvDy1leJ9YMTLAlIPVa0645gMA=; b=lJ81AOXRGrHo2fTWO3MgVCK1pycdmxlsUYGNg3iCzCkUXikUNXHIS6++ulBLpsspp/ yJSnUkQHQsKBVMAW7M0galgRDdJW1LFOu8DfdMTZX7n4zDN/1RfGuTdM6HPHpGJqTjRL eX9RhB6htxZci9xgWF53zrvRQC0n5rvx5qqEhB3tld6fy7GA6CiTP+eCDG6Fapsxcqv9 gky5Fp24oWLrOmIFW8idIyrmuqvJTN59vZ69474KVuASv9J8+DliVnWP+1epBrCkUBNq WmNR8hc3AyTheNXTlgJiVVIZQ9Sr01kZtiqDv0LTOq4unXgC1O/E48uW+qNAdtwh+U3k 752g==
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=67BhmgGmmCSq9OPdFMvDy1leJ9YMTLAlIPVa0645gMA=; b=WWDGAMJLx3d4YQAKLB7SasDROQJv3gIY6caRao+4k0u0klvOTvyb2xUfL97AfPhcj/ hO2VxoYd8QZsPQHVRZ2yoKOT+LxhloCst8ZEAIaJefQP3CrUgSh+ZoqqkuDYQ5GWi04e cK+7kzw+0yYEQC0TXS+bR2C9qPh/o1QroEHTX93Hb2PKUKTiXL7v2dEIh4mW8IdK0Qzi I9bHlml+o3kx9N6OGACMx4C5wEw1daaJFo5HwVeU3eWg3aV/M7rS46AEjakJmPGn4zW9 NdVya8EdRFeJeIV1ebKjFFrwLpBiEr/a6cEdj5FHsVPxEs4g0Yam5C1slvGBVLzmv2Nd Nleg==
X-Gm-Message-State: AGRZ1gJpqP1Ium+651SeH5cS6UGd7XfZMGCL/pVHb/WB48CaTe1Gkiax eoN4tl7FQo+KnOy8XNB1bcuscJ8qlXnb2NbeeZo=
X-Google-Smtp-Source: AJdET5cVbUhP3QxICNkGGaN5KbKumFhAORoBzNDPsvcnkVYDxo0ZBKyzUTbPRm8rTj0bRINVhz1Qtl8f5KVPIA7wJVg=
X-Received: by 2002:a19:53d9:: with SMTP id h86-v6mr824956lfl.75.1540873438394;  Mon, 29 Oct 2018 21:23:58 -0700 (PDT)
MIME-Version: 1.0
References: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com> <CAKcm_gMDOyJC0AwOo2knN6AMxVbySjGsrLvjcC9A8UA9xcvcWw@mail.gmail.com> <19D3595B-8845-45B6-A60D-9E934DD49FAC@apple.com> <CACpbDcfk+GXb3aL5LG0wQM87thRGO5Y4Q+9cbXf5YuW1=jWCig@mail.gmail.com> <B7BE2454-2A4D-4323-B0A5-0D73BD4B819F@apple.com> <CACpbDcd5YWcxyEH3TS1FssgAT13oqeBBQg92+J0uJqhxPz2qkA@mail.gmail.com> <4b7b02d110f74139bacae8e01c54a4af@usma1ex-dag1mb6.msg.corp.akamai.com>
In-Reply-To: <4b7b02d110f74139bacae8e01c54a4af@usma1ex-dag1mb6.msg.corp.akamai.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Mon, 29 Oct 2018 21:23:47 -0700
Message-ID: <CACpbDcfDtwLqhR5um5OwzT2d8QAKrwhqmJJ3TRX9j-JhECRB4Q@mail.gmail.com>
Subject: Re: flow control and DATAGRAM
To: "Lubashev, Igor" <ilubashe@akamai.com>
Cc: tpauly@apple.com, QUIC WG <quic@ietf.org>,  Martin Thomson <martin.thomson@gmail.com>, Ian Swett <ianswett@google.com>
Content-Type: multipart/alternative; boundary="000000000000f080a705796a8d5a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/nnPaMoBshJHuY9g3qcg_zDNq8bs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 04:24:04 -0000

--000000000000f080a705796a8d5a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Igor,

I had thought that this was similar to canceling streams, but you're right.
Canceling a stream gets rid of stream flow control state entirely, where in
this case, the receiver cannot discard flow control state.

I don't have any great ideas right now, but I fear that not having flow
control simply punts the problem down the road. FWIW, this may be quite
fine for this extension, and we can surely evolve it to have flow control
when we have a way to do it.

- jana

On Mon, Oct 29, 2018 at 8:54 PM Lubashev, Igor <ilubashe@akamai.com> wrote:

> Jana,
>
> > The simplest scheme would be to reserve a stream ID for DATAGRAM data -=
-
> [...]
> > -- and then MAX_STREAM_DATA uses this
> > stream ID for flow control of DATAGRAM octets.
>
> There are many dragons that way. Flow control indicates commitment to
> buffer data. When sender does not retransmit, when does receiver give up
> its commitment to wait for (and buffer) earlier data so it can advance
> MAX_STREAM_DATA to allow the sender to send more data? Can the signal fro=
m
> sender tolerate loss/reordering vs STREAM frames (assuming the datagram c=
an
> be split for sending in multiple QUIC packets)? These dragons can be
> conquered (see my partially reliable streams draft, v2 or v3), but this i=
s
> not simple. :(
>
> - Igor
>
> -----Original Message-----
> *From:* Jana Iyengar [jri.ietf@gmail.com]
> *Received:* Monday, 29 Oct 2018, 10:24PM
> *To:* tpauly@apple.com [tpauly@apple.com]
> *CC:* Ian Swett [ianswett@google.com]; QUIC WG [quic@ietf.org]; Martin
> Thomson [martin.thomson@gmail.com]
> *Subject:* Re: flow control and DATAGRAM
>
> Hey Tommy,
>
>
>> I'm not suggesting any changes to when the packet gets
>> ack'ed=E2=80=94specifically, I was responding to Martin's hypothetical o=
f having an
>> ACK to a DATAGRAM frame meaning that the application had processed the
>> frame. My impression is that the ACK to a packet containing a DATAGRAM
>> frame means:
>> - The packet made it across the network to the QUIC endpoint on the othe=
r
>> side
>>
>
> ... and was processed by the QUIC receiver (not necessarily by the
> application). This is the same semantic as the ack of a regular frame.
>
>
>> - The QUIC implementation will deliver the DATAGRAM frame to application
>> (it won't drop it locally)
>>
>
> In which case you will need flow control. If you agree, then we're on the
> same page so far.
>
>
>> Having a separate outstanding data limit for the DATAGRAM "stream" is an
>> interesting solution to the space. It would then have the nice property =
of
>> not looking like traditional flow control. It could even be measured in
>> number of frames, rather than bytes (depending on what the limiting fact=
ors
>> are).
>>
>
> In terms of flow control, I don't think DATAGRAM flow control is any
> different than sending stream data on any stream and then canceling it --
> there are no retransmissions, but the sender still accounts for it in flo=
w
> control. My thought here was basically to have exactly the same flow
> control as stream-level flow control, and allow for DATAGRAM bytes to fal=
l
> within connection-level flow control as normal.
>
> The simplest scheme would be to reserve a stream ID for DATAGRAM data --
> this could be 0 or 2^62-1 -- and then MAX_STREAM_DATA uses this stream ID
> for flow control of DATAGRAM octets. Alternatively, define a new frame
> called MAX_DATAGRAM_DATA that is carries the largest allowed offset that
> can be sent as a DATAGRAM, and introduce an offset field in the DATAGRAM
> frame.
>
> - jana
>
>
>> Thanks,
>> Tommy
>>
>> On Oct 29, 2018, at 12:37 PM, Jana Iyengar <jri.ietf@gmail.com> wrote:
>>
>> Tommy,
>>
>> Changing the semantics of an acknowledgment to include delivery up to th=
e
>> application is a fundamental change to the QUIC machinery, and it doesn'=
t
>> work. First, an ACK frame acknowledges packets, and you can't have
>> different semantics of an acknowledgment for different frames that are
>> carried in the same packet. Second, it interferes with RTT measurement, =
and
>> it conflates flow control with congestion control, which gets messy. (Th=
is
>> conflation is an interesting problem to consider theoretically, but not =
one
>> for us at this time IMO.)
>>
>> I am wondering if applying a stream-level flow control for DATAGRAMs
>> makes sense instead. Meaning that you treat DATAGRAMs as a separate stre=
am
>> for flow control purposes. You might benefit from having an offset in th=
e
>> DATAGRAM frame for this purpose.
>>
>> - jana
>>
>> On Mon, Oct 29, 2018 at 8:21 AM Tommy Pauly <tpauly@apple.com> wrote:
>>
>>> Hi Martin, Ian,
>>>
>>> Yes, very good points!
>>>
>>> My tendency would be to prefer what Ian's implementation does of passin=
g
>>> these DATAGRAM frames up immediately to the application. I don't think =
that
>>> the acknowledgment needs to indicate that the frame was processed by th=
e
>>> application, but merely that it has been delivered to the application (=
that
>>> is, the application doesn't get to do anything with the frame that can
>>> influence the acknowledgment).
>>>
>>> The current draft indicates that the content of the DATAGRAM frames
>>> contributes to the limit used for MAX_DATA, and that if that amount is
>>> reached, the frames are blocked along with STREAM data. I think this wo=
rks
>>> fine for the sender, while the receiver gets into the discussion you
>>> present. On the sender side, reaching MAX_DATA could mean dropping the
>>> DATAGRAM frames when unable to send more (and sending BLOCKED instead).
>>> Since the frames are unreliable, they can be dropped in this situation
>>> without violating the API contract.
>>>
>>> On the receiver side, I agree that queuing the DATAGRAM frames to let
>>> the application drive flow control in the way it does for STREAM frames
>>> adds complexity and diminishes the utility of the frame and ACKs.. Howe=
ver,
>>> I can imagine taking a fairly simplistic approach in which the data lim=
it
>>> is automatically increased upon reception of the frame (and the frame i=
s
>>> immediately passed to the application). This allows the initial_max_dat=
a to
>>> put a cap on the amount of data in a given flight of DATAGRAMS, and all=
ow
>>> the size of a flight of DATAGRAM frames to be limited by the amount of =
room
>>> left over from STREAM data that may be consuming the connection-wide fl=
ow
>>> control.
>>>
>>> Perhaps this approach needs a clearer name other than "flow control",
>>> since it has a somewhat different meaning in effect.
>>>
>>> As for ACKs, if we never discard on the receiver side, the ACK is prett=
y
>>> useful for detecting if there was network-based packet loss.
>>>
>>> Thanks,
>>> Tommy
>>>
>>> On Oct 29, 2018, at 5:32 AM, Ian Swett <ianswett@google.com> wrote:
>>>
>>> Good catch Martin, I missed that in the draft as well, and I also think
>>> it's impossibly with the proposed design.
>>>
>>> And yes, I think Martin's proposed solution is likely the only practica=
l
>>> one.  In my implementation, the frame is passed up to the application
>>> immediately, so technically QUIC processed it, and it's the application=
's
>>> job to decide what to do with it.
>>>
>>> On Mon, Oct 29, 2018 at 1:16 AM Martin Thomson <martin.thomson@gmail.co=
m>
>>> wrote:
>>>
>>>> Hi Tommy,
>>>>
>>>> Your slides - <
>>>> https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF103-QUI=
C-Datagram.pdf
>>>> <https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_qui=
cwg_wg-2Dmaterials_blob_master_ietf103_IETF103-2DQUIC-2DDatagram.pdf&d=3DDw=
MFaQ&c=3D96ZbZZcaMF4w0F4jpN6LZg&r=3DDjn3bQ5uNJDPM_2skfL3rW1tzcIxyjUZdn_m55K=
Pmlo&m=3DBOGSfZ4hKaubJ6yww-9_8EDX3OccYvdip0g3k4t66hQ&s=3Dqiyr1YY1MHWjhIrPfw=
HXN6FCdsG8wUuhAuqczkosLlI&e=3D>
>>>> >
>>>> - say that DATAGRAM frames respect connection-level flow control.  I
>>>> missed that in the draft, and I don't know how they can do that in the
>>>> face of packet loss, especially when you don't necessarily retransmit
>>>> lost DATAGRAM frames.
>>>>
>>>> For that to work, you would need a bunch more machinery to make the
>>>> connection-level flow control sync between endpoints in the case that
>>>> packets are lost.  A disagreement about how much flow control is used
>>>> causes things to break down badly.  Ian and I discussed this point at
>>>> the last meeting and quickly agreed that while it might be nice to
>>>> have flow control for this stuff, the increase in complexity is
>>>> considerable and (at the time) we thought it wouldn't be worth it.
>>>>
>>>> The problem that introduces is that you could end up having too many
>>>> DATAGRAM frames arrive.  The receiver has to drop something at the
>>>> point that it can't handle them.  And we say that when you acknowledge
>>>> something, you processed it.  That's tricky.
>>>>
>>>> It might be easier to say that a QUIC acknowledgment for a DATAGRAM
>>>> frame doesn't mean that it was received and processed by an
>>>> application.  An endpoint might discard these frames before passing
>>>> them on to applications if it doesn't have space.  In other words,
>>>> acknowledgment of DATAGRAM means that QUIC got it, not that the
>>>> application got it.  Sadly, that means that the QUIC acknowledgment
>>>> machinery doesn't help the application that uses DATAGRAM all that
>>>> much.  Also, the lower bound on reliability is 0, which isn't the best
>>>> thing ever.
>>>>
>>>> Hard choices, I know.  I don't have a good design for maintaining
>>>> connection-level flow control (or any back pressure mechanism with
>>>> equivalent properties) that doesn't add both complexity and overhead.
>>>>
>>>> Cheers,
>>>> Martin
>>>>
>>>>
>>>
>>

--000000000000f080a705796a8d5a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Igor,<div><br></div><div>I had thought that this was simil=
ar to canceling streams, but you&#39;re right. Canceling a stream gets rid =
of stream flow control state entirely, where in this case, the receiver can=
not discard flow control state.</div><div><br></div><div>I don&#39;t have a=
ny great ideas right now, but I fear that not having flow control simply pu=
nts the problem down the road. FWIW, this may be quite fine for this extens=
ion, and we can surely evolve it to have flow control when we have a way to=
 do it.</div><div><br></div><div>- jana</div></div><br><div class=3D"gmail_=
quote"><div dir=3D"ltr">On Mon, Oct 29, 2018 at 8:54 PM Lubashev, Igor &lt;=
<a href=3D"mailto:ilubashe@akamai.com">ilubashe@akamai.com</a>&gt; wrote:<b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">




<div>
<span style=3D"font-family:Calibri,Arial,Helvetica,sans-serif;font-size:11p=
t;color:black">Jana,<br>
<br>
&gt; The simplest scheme would be to reserve a stream ID for DATAGRAM data =
-- [...]<br>
&gt; -- and then MAX_STREAM_DATA uses this<br>
&gt; stream ID for flow control of DATAGRAM octets.<br>
<br>
There are many dragons that way. Flow control indicates commitment to buffe=
r data. When sender does not retransmit, when does receiver give up its com=
mitment to wait for (and buffer) earlier data so it can advance MAX_STREAM_=
DATA to allow the sender to send
 more data? Can the signal from sender tolerate loss/reordering vs STREAM f=
rames (assuming the datagram can be split for sending in multiple QUIC pack=
ets)? These dragons can be conquered (see my partially reliable streams dra=
ft, v2 or v3), but this is not simple.
 :(<br>
<br>
- Igor<br>
<br>
<span style=3D"color:black">-----Original Message----- <br>
<b>From:</b> Jana Iyengar [<a href=3D"mailto:jri.ietf@gmail.com" target=3D"=
_blank">jri.ietf@gmail.com</a>]<br>
<b>Received:</b> Monday, 29 Oct 2018, 10:24PM<br>
<b>To:</b> <a href=3D"mailto:tpauly@apple.com" target=3D"_blank">tpauly@app=
le.com</a> [<a href=3D"mailto:tpauly@apple.com" target=3D"_blank">tpauly@ap=
ple.com</a>]<br>
<b>CC:</b> Ian Swett [<a href=3D"mailto:ianswett@google.com" target=3D"_bla=
nk">ianswett@google.com</a>]; QUIC WG [<a href=3D"mailto:quic@ietf.org" tar=
get=3D"_blank">quic@ietf.org</a>]; Martin Thomson [<a href=3D"mailto:martin=
.thomson@gmail.com" target=3D"_blank">martin.thomson@gmail.com</a>]<br>
<b>Subject:</b> Re: flow control and DATAGRAM<br>
<br>
</span></span>
<div>
<div dir=3D"ltr">Hey Tommy,
<div class=3D"gmail_quote">
<div>=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;line-break:after-white-space">
<div>I&#39;m not suggesting any changes to when the packet gets ack&#39;ed=
=E2=80=94specifically, I was responding to Martin&#39;s hypothetical of hav=
ing an ACK to a DATAGRAM frame meaning that the application had processed t=
he frame. My impression is that the ACK to a packet containing
 a DATAGRAM frame means:</div>
<div>- The packet made it across the network to the QUIC endpoint on the ot=
her side</div>
<div></div>
</div>
</blockquote>
<div><br>
</div>
<div>... and was processed by the QUIC receiver (not necessarily by the app=
lication). This is the same semantic as the ack of a regular frame.</div>
<div>=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;line-break:after-white-space">
<div>- The QUIC implementation will deliver the DATAGRAM frame to applicati=
on (it won&#39;t drop it locally)</div>
</div>
</blockquote>
<div><br>
</div>
<div>In which case you will need flow control. If you agree, then we&#39;re=
 on the same page so far.</div>
<div>=C2=A0=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;line-break:after-white-space">
<div>Having a separate outstanding data limit for the DATAGRAM &quot;stream=
&quot; is an interesting solution to the space. It would then have the nice=
 property of not looking like traditional flow control. It could even be me=
asured in number of frames, rather than bytes
 (depending on what the limiting factors are).</div>
</div>
</blockquote>
<div><br>
</div>
<div>In terms of flow control, I don&#39;t think DATAGRAM flow control is a=
ny different than sending stream data on any stream and then canceling it -=
- there are no retransmissions, but the sender still accounts for it in flo=
w control. My thought here was basically
 to have exactly the same flow control as stream-level flow control, and al=
low for DATAGRAM bytes to fall within connection-level flow control as norm=
al.</div>
<div><br>
</div>
<div>The simplest scheme would be to reserve a stream ID for DATAGRAM data =
-- this could be 0 or 2^62-1 -- and then MAX_STREAM_DATA uses this stream I=
D for flow control of DATAGRAM octets. Alternatively, define a new frame ca=
lled MAX_DATAGRAM_DATA that is carries
 the largest allowed offset that can be sent as a DATAGRAM, and introduce a=
n offset field in the DATAGRAM frame.</div>
<div><br>
</div>
<div>- jana</div>
<div>=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;line-break:after-white-space">
<div>Thanks,</div>
<div>Tommy<br>
<div><br>
<blockquote type=3D"cite">
<div>On Oct 29, 2018, at 12:37 PM, Jana Iyengar &lt;<a href=3D"mailto:jri.i=
etf@gmail.com" target=3D"_blank">jri.ietf@gmail.com</a>&gt; wrote:</div>
<br class=3D"m_4877462653349879931m_6117190503338714891Apple-interchange-ne=
wline">
<div>
<div dir=3D"ltr">Tommy,
<div><br>
</div>
<div>Changing the semantics of an acknowledgment to include delivery up to =
the application is a fundamental change to the QUIC machinery, and it doesn=
&#39;t work. First, an ACK frame acknowledges packets, and you can&#39;t ha=
ve different semantics of an acknowledgment
 for different frames that are carried in the same packet. Second, it inter=
feres with RTT measurement, and it conflates flow control with congestion c=
ontrol, which gets messy. (This conflation is an interesting problem to con=
sider theoretically, but not one
 for us at this time IMO.)</div>
<div><br>
</div>
<div>I am wondering if applying a stream-level flow control for DATAGRAMs m=
akes sense instead. Meaning that you treat DATAGRAMs as a separate stream f=
or flow control purposes. You might benefit from having an offset in the DA=
TAGRAM frame for this purpose.</div>
<div><br>
</div>
<div>- jana</div>
</div>
<br>
<div class=3D"gmail_quote">
<div dir=3D"ltr">On Mon, Oct 29, 2018 at 8:21 AM Tommy Pauly &lt;<a href=3D=
"mailto:tpauly@apple.com" target=3D"_blank">tpauly@apple.com</a>&gt; wrote:=
<br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;line-break:after-white-space">Hi Martin,=
 Ian,
<div><br>
</div>
<div>Yes, very good points!</div>
<div><br>
</div>
<div>My tendency would be to prefer what Ian&#39;s implementation does of p=
assing these DATAGRAM frames up immediately to the application. I don&#39;t=
 think that the acknowledgment needs to indicate that the frame was process=
ed by the application, but merely that it
 has been delivered to the application (that is, the application doesn&#39;=
t get to do anything with the frame that can influence the acknowledgment).=
</div>
<div><br>
</div>
<div>The current draft indicates that the content of the DATAGRAM frames co=
ntributes to the limit used for=C2=A0MAX_DATA, and that if that amount is r=
eached, the frames are blocked along with STREAM data. I think this works f=
ine for the sender, while the receiver
 gets into the discussion you present. On the sender side, reaching MAX_DAT=
A could mean dropping the DATAGRAM frames when unable to send more (and sen=
ding BLOCKED instead). Since the frames are unreliable, they can be dropped=
 in this situation without violating
 the API contract.=C2=A0</div>
<div><br>
</div>
<div>On the receiver side, I agree that queuing the DATAGRAM frames to let =
the application drive flow control in the way it does for STREAM frames add=
s complexity and diminishes the utility of the frame and ACKs.. However, I =
can imagine taking a fairly simplistic
 approach in which the data limit is automatically increased upon reception=
 of the frame (and the frame is immediately passed to the application). Thi=
s allows the initial_max_data to put a cap on the amount of data in a given=
 flight of DATAGRAMS, and allow
 the size of a flight of DATAGRAM frames to be limited by the amount of roo=
m left over from STREAM data that may be consuming the connection-wide flow=
 control.=C2=A0</div>
<div><br>
</div>
<div>Perhaps this approach needs a clearer name other than &quot;flow contr=
ol&quot;, since it has a somewhat different meaning in effect.</div>
<div><br>
</div>
<div>As for ACKs, if we never discard on the receiver side, the ACK is pret=
ty useful for detecting if there was network-based packet loss.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Tommy=C2=A0</div>
<div>
<div><br>
<blockquote type=3D"cite">
<div>On Oct 29, 2018, at 5:32 AM, Ian Swett &lt;<a href=3D"mailto:ianswett@=
google.com" target=3D"_blank">ianswett@google.com</a>&gt; wrote:</div>
<br class=3D"m_4877462653349879931m_6117190503338714891m_-10613713011608938=
98Apple-interchange-newline">
<div>
<div dir=3D"ltr">Good catch Martin, I missed that in the draft as well, and=
 I also think it&#39;s impossibly with the proposed design.
<div><br>
</div>
<div>And yes, I think Martin&#39;s proposed solution is likely the only pra=
ctical one.=C2=A0 In my implementation, the frame is passed up to the appli=
cation immediately, so technically QUIC processed it, and it&#39;s the appl=
ication&#39;s job to decide what to do with it.</div>
</div>
<br>
<div class=3D"gmail_quote">
<div dir=3D"ltr">On Mon, Oct 29, 2018 at 1:16 AM Martin Thomson &lt;<a href=
=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomson@gmail=
.com</a>&gt; wrote:<br>
</div>
<blockquote class=3D"gmail_quote">Hi Tommy,<br>
<br>
Your slides - &lt;<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dh=
ttps-3A__github.com_quicwg_wg-2Dmaterials_blob_master_ietf103_IETF103-2DQUI=
C-2DDatagram.pdf&amp;d=3DDwMFaQ&amp;c=3D96ZbZZcaMF4w0F4jpN6LZg&amp;r=3DDjn3=
bQ5uNJDPM_2skfL3rW1tzcIxyjUZdn_m55KPmlo&amp;m=3DBOGSfZ4hKaubJ6yww-9_8EDX3Oc=
cYvdip0g3k4t66hQ&amp;s=3Dqiyr1YY1MHWjhIrPfwHXN6FCdsG8wUuhAuqczkosLlI&amp;e=
=3D" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/wg-mate=
rials/blob/master/ietf103/IETF103-QUIC-Datagram.pdf</a>&gt;<br>
- say that DATAGRAM frames respect connection-level flow control.=C2=A0 I<b=
r>
missed that in the draft, and I don&#39;t know how they can do that in the<=
br>
face of packet loss, especially when you don&#39;t necessarily retransmit<b=
r>
lost DATAGRAM frames.<br>
<br>
For that to work, you would need a bunch more machinery to make the<br>
connection-level flow control sync between endpoints in the case that<br>
packets are lost.=C2=A0 A disagreement about how much flow control is used<=
br>
causes things to break down badly.=C2=A0 Ian and I discussed this point at<=
br>
the last meeting and quickly agreed that while it might be nice to<br>
have flow control for this stuff, the increase in complexity is<br>
considerable and (at the time) we thought it wouldn&#39;t be worth it.<br>
<br>
The problem that introduces is that you could end up having too many<br>
DATAGRAM frames arrive.=C2=A0 The receiver has to drop something at the<br>
point that it can&#39;t handle them.=C2=A0 And we say that when you acknowl=
edge<br>
something, you processed it.=C2=A0 That&#39;s tricky.<br>
<br>
It might be easier to say that a QUIC acknowledgment for a DATAGRAM<br>
frame doesn&#39;t mean that it was received and processed by an<br>
application.=C2=A0 An endpoint might discard these frames before passing<br=
>
them on to applications if it doesn&#39;t have space.=C2=A0 In other words,=
<br>
acknowledgment of DATAGRAM means that QUIC got it, not that the<br>
application got it.=C2=A0 Sadly, that means that the QUIC acknowledgment<br=
>
machinery doesn&#39;t help the application that uses DATAGRAM all that<br>
much.=C2=A0 Also, the lower bound on reliability is 0, which isn&#39;t the =
best<br>
thing ever.<br>
<br>
Hard choices, I know.=C2=A0 I don&#39;t have a good design for maintaining<=
br>
connection-level flow control (or any back pressure mechanism with<br>
equivalent properties) that doesn&#39;t add both complexity and overhead.<b=
r>
<br>
Cheers,<br>
Martin<br>
<br>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>

</blockquote></div>

--000000000000f080a705796a8d5a--


From nobody Mon Oct 29 21:28:13 2018
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 27212126CB6 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 21:28:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 9C8c_qAB1-4k for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 21:28:09 -0700 (PDT)
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 A72341277BB for <quic@ietf.org>; Mon, 29 Oct 2018 21:28:09 -0700 (PDT)
Received: from xsmtp04.mail2web.com ([168.144.250.231]) by mx65.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1gHLdP-000801-1g for quic@ietf.org; Tue, 30 Oct 2018 05:28:08 +0100
Received: from [10.5.2.35] (helo=xmail10.myhosting.com) by xsmtp04.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1gHLdH-0004o6-Pg for quic@ietf.org; Tue, 30 Oct 2018 00:28:03 -0400
Received: (qmail 18849 invoked from network); 30 Oct 2018 04:27:57 -0000
Received: from unknown (HELO [192.168.1.100]) (Authenticated-user:_huitema@huitema.net@[172.56.42.225]) (envelope-sender <huitema@huitema.net>) by xmail10.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 30 Oct 2018 04:27:56 -0000
To: quic@ietf.org
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com> <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch>
From: Christian Huitema <huitema@huitema.net>
Openpgp: preference=signencrypt
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= xsBNBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAHNJ0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PsLAeQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1bOwE0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAcLBfgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8=
Message-ID: <a088c411-1acc-8b0f-fc1b-8c79ce6f1cd7@huitema.net>
Date: Mon, 29 Oct 2018 21:27:47 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cGic02NiFcTLmPo8IIOsMVwWGerTxaz7S"
Subject: Re: Structuring the BKK spin bit discussion
X-Originating-IP: 168.144.250.231
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.13)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5ufZrQkf8DVekiuzI2hZ44N602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO37pNwwF1lRXh5rzvPzo9Jts1ujulqUFmMITHM77eiViTU46NVfhLyv5IbGsB1XRPM7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pBuzDn5j2tUhjYPVPi3bwTCB/TBCf6oYXAWGet lavcAjD9ytQxIHf9lN5jjLJaPK8lRJSPf/SXbEnDSsal/zZzc4n9VZdr7RAFD5mRwooUYhwMPaBP aKeQW+/QlaOdv8isl/qMm08Zpim2AHUKEWvQ6G/bWfgucjnNmABpGhD9TTttrFCuZ0NkwnSz2Luu o1u9uevuNfM1HjkNEFwape+IgNezYqxGMqsKjARq8PBC4qjpVMhqNcdjhoIlgrKzBvjTmdySlZou 9qHIGOZDEEo7Oyc1nq0gsY582CWqKjiRB3ukywmZtiDkyd4mEBjJGGEJE2d52fY0d/1mkgffWkdO 4QEiRQv+PVjjwa+Z5RFCOMR0q/8r+vli3P7r8BoPzXffG1JhEiAOdl0Bn/vyebShl87xZV8dCGUi DygA88+m1WJqJvBXd7I82n0qpCzrPWiSwKPXNKNk2RVY2K5nyLgw1Z+7sPmjIM3bM0ihYRE0YjPM ySEj7fwLz33nMnt8v2VA+QogqeKyP7VkdiNECHuevWCP6KnOBvL4JpDTCrFGRy1FNOX+BWyxshxU zpLja30fKWV8hC0uiHDMDwMmXif3DSHqAeeZGuerhbgzLuS7t5s9GPg40iyG6Zatha+1LmeozM60 voqUUzJmvILAkkfgIC7Q9IN0ifxHSlxrnKocSEpXgjmuntq3xZgBxhdNFJUcZu3d9ZNXJQW8HUxK X5uYJmvDK3PKrieG7T6bf9hS7hR0q7xASYaBUaOtmtSkj3iuxJhh7EHDojb6D9Mx+gs1+GHf4ys4 4rg2B8/9FmK9a1O9x7lsssuZ/53sObhu0YJN
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2XPq3DEWpmIg534RZwIa76VLQnk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 04:28:12 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--cGic02NiFcTLmPo8IIOsMVwWGerTxaz7S
Content-Type: multipart/mixed; boundary="NgwkhZfHfzGalKIrntF1JitZgJNamE4lG";
 protected-headers="v1"
From: Christian Huitema <huitema@huitema.net>
To: quic@ietf.org
Message-ID: <a088c411-1acc-8b0f-fc1b-8c79ce6f1cd7@huitema.net>
Subject: Re: Structuring the BKK spin bit discussion
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org>
 <20181029160802.GD7258@ubuntu-dmitri>
 <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net>
 <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com>
 <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch>
In-Reply-To: <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch>

--NgwkhZfHfzGalKIrntF1JitZgJNamE4lG
Content-Type: multipart/alternative;
 boundary="------------46C06C55B9B726F4543280F0"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------46C06C55B9B726F4543280F0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 10/29/2018 3:58 PM, Brian Trammell (IETF) wrote:

> hi Martin, Christian, all,
>
>> On 29 Oct 2018, at 23:29, Martin Thomson <martin.thomson@gmail.com> wr=
ote:
>>
>> On Tue, Oct 30, 2018 at 3:54 AM Christian Huitema <huitema@huitema.net=
> wrote:
>>> I think the strongest objection to the spin bit was put up by Marten =
during the last interim: measuring the RTT with the spin bit discloses th=
e use of hidden path segments like VPN. This issue was not discussed duri=
ng the privacy analysis.
>> I had assumed that was part of the analysis and it was covered by the
>> assumption that spinning could be disabled
> +1. Probabilistically disabling spinning, which seems necessary if we w=
ant some grease to help us reserve the right to change the semantics of t=
he bit at the spin bit's location in the wire image, should ensure that e=
ndpoints that want to disable spinning for their own reasons will have a =
large anonymity set to hide in, even in a future with perfect implementat=
ion and deployment of the spin bit.

I opened PR https://github.com/quicwg/base-drafts/pull/1931 to discuss th=
is.

-- Christian Huitema

--------------46C06C55B9B726F4543280F0
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html;
      charset=3Dwindows-1252">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p>On 10/29/2018 3:58 PM, Brian Trammell (IETF) wrote:<br>
    </p>
    <blockquote type=3D"cite"
      cite=3D"mid:5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch">
      <pre wrap=3D"">hi Martin, Christian, all,

</pre>
      <blockquote type=3D"cite" style=3D"color: #000000;">
        <pre wrap=3D"">On 29 Oct 2018, at 23:29, Martin Thomson <a class=3D=
"moz-txt-link-rfc2396E" href=3D"mailto:martin.thomson@gmail.com" moz-do-n=
ot-send=3D"true">&lt;martin.thomson@gmail.com&gt;</a> wrote:

On Tue, Oct 30, 2018 at 3:54 AM Christian Huitema <a class=3D"moz-txt-lin=
k-rfc2396E" href=3D"mailto:huitema@huitema.net" moz-do-not-send=3D"true">=
&lt;huitema@huitema.net&gt;</a> wrote:
</pre>
        <blockquote type=3D"cite" style=3D"color: #000000;">
          <pre wrap=3D"">I think the strongest objection to the spin bit =
was put up by Marten during the last interim: measuring the RTT with the =
spin bit discloses the use of hidden path segments like VPN. This issue w=
as not discussed during the privacy analysis.
</pre>
        </blockquote>
        <pre wrap=3D"">I had assumed that was part of the analysis and it=
 was covered by the
assumption that spinning could be disabled
</pre>
      </blockquote>
      <pre wrap=3D"">+1. Probabilistically disabling spinning, which seem=
s necessary if we want some grease to help us reserve the right to change=
 the semantics of the bit at the spin bit's location in the wire image, s=
hould ensure that endpoints that want to disable spinning for their own r=
easons will have a large anonymity set to hide in, even in a future with =
perfect implementation and deployment of the spin bit.
</pre>
    </blockquote>
    <br>
    I opened PR <a class=3D"moz-txt-link-freetext" href=3D"https://github=
=2Ecom/quicwg/base-drafts/pull/1931">https://github.com/quicwg/base-draft=
s/pull/1931</a> to
    discuss this.<br>
    <br>
    -- Christian Huitema<br>
  </body>
</html>

--------------46C06C55B9B726F4543280F0--

--NgwkhZfHfzGalKIrntF1JitZgJNamE4lG--

--cGic02NiFcTLmPo8IIOsMVwWGerTxaz7S
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJb193LAAoJELba05IUOHVQWbUH/REZzcbQfOZCGIrU3t9yUM5M
xFvxdHYtVYRa4f3lycDv148wTCEJxz3u89yvATv5yJRCBwflXpS//IcZxLiPL6ev
Ce1rJdHPVEC6P0ztXgDJXuzj3Lnh1KvP0c+1M0k43Qyk8rKJgmd3Q+B9z2jBxRRo
frOSFU6ZInQSj8aVFwJNe678vMUWbkk1ROfuGQpGp38ThTbvS2vpMHjvCQ1wNNnU
scQ2BVKnyGL6TxPfWyfm+Dltvaqs/GLwbGg1n6VNY50dQus0mk6MfYT0mkETQ86f
D+3sbHaGZgXGMNg6x99I2d/gb8fIA2p5MRPtspNiXaRy5JEw52dmBtk9k5PS59s=
=oNOr
-----END PGP SIGNATURE-----

--cGic02NiFcTLmPo8IIOsMVwWGerTxaz7S--


From nobody Mon Oct 29 22:21:40 2018
Return-Path: <w@1wt.eu>
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 295E3129385 for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 22:21:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 N0r5OykV9U9C for <quic@ietfa.amsl.com>; Mon, 29 Oct 2018 22:21:37 -0700 (PDT)
Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 1734E128CF3 for <quic@ietf.org>; Mon, 29 Oct 2018 22:21:36 -0700 (PDT)
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id w9U5LXVA029970; Tue, 30 Oct 2018 06:21:33 +0100
Date: Tue, 30 Oct 2018 06:21:33 +0100
From: Willy Tarreau <w@1wt.eu>
To: Mark Nottingham <mnot@mnot.net>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Identifying our deliverables
Message-ID: <20181030052133.GA29963@1wt.eu>
References: <578BB4EC-421E-4B21-AA14-B545A41754C8@mnot.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <578BB4EC-421E-4B21-AA14-B545A41754C8@mnot.net>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/E3xbENo886xcx7-H1h3s36VaoRI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 05:21:39 -0000

On Sun, Oct 28, 2018 at 11:30:55AM +1100, Mark Nottingham wrote:
> To address this, I'd like to suggest that -- after coordination with the HTTP
> WG -- we rename our the HTTP document to "HTTP/3", and using the final ALPN
> token "h3". Doing so clearly identifies it as another binding of HTTP
> semantics to the wire protocol -- just as HTTP/2 did -- so people understand
> its separation from QUIC.

FWIW I always thought that HTTP/3 should be its final naming -- just like SPDY
became HTTP/2 -- for various reasons, one of them being encouraging adoption
by the protocol being presented as the natural upgrade to the previous ones
and not a competitor that's been there for some time and suddenly comes as
an RFC.

H1 with 723x, then H2 with 754x have shown that it's not a problem to cover
multiple areas with a common name and that the protocol itself is in fact a
family of protocols and mechanisms. So QPACK will naturally fall under H3
just like HPACK naturally belongs to H2.

Just my two cents,
Willy


From nobody Tue Oct 30 00:01:09 2018
Return-Path: <mikkelfj@gmail.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 DF595128C65 for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 00:01:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-0.001] 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 Aj_CackDgwNo for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 00:01:03 -0700 (PDT)
Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (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 DA27A124BE5 for <quic@ietf.org>; Tue, 30 Oct 2018 00:01:02 -0700 (PDT)
Received: by mail-qk1-x72f.google.com with SMTP id u68so2638135qkg.9 for <quic@ietf.org>; Tue, 30 Oct 2018 00:01:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :mime-version; bh=w2veH7Z5NC7cC4io5Th0AA5shcBoGKr61wPZ8jy0mS4=; b=puWXVBQNtJyo0g3KEjcIxdR70PooZ+UYOHD3fpiAfS7IQzYKPIY/EDtlbsZ8p9RLue t9TD7t4awKvgh+lAzTjxUGbuqLA914mdv4LmO97yChHNPqymRFsFFOGPT2yUMR9zheC8 uJdfi5MY6+euKm9/aSFgHNjx56NMNHg4u8oZP9es+z2Aol/Z0/UEOHGX7YXTzuQ+eT7K 4WjOacxe3Sv0nHmgB+c6kXSwJY4XFO+e3Hi5gv8Nu+LDjnIxTY9iP052im/bFZxO9l1m cqBpyOwGWI2nJ/VfA6RYOKBhW3/kkceUCtHNqpMYRCHuglFwmmFBgBMMALsFDXWyZspO y77g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :mime-version; bh=w2veH7Z5NC7cC4io5Th0AA5shcBoGKr61wPZ8jy0mS4=; b=OG0Lulb2Ar7yDKd5pBxcqTnTfQ1TOoVoSlPzT3RG4X5vGD/psTJlynoDxuB2DuPmgn xIssoiDrvgTSwQn5YPhyIWB3aMNXVKa1Ap1NiGkgBfMNEFWWJMdEfksVtDHsM3XjnN59 +qQuesa+fGFfwOHr/x64bW+B8X83sUr6KYKR9uHu24TXcEfQwUFGLIMQ43vBV5xydrmq AIevZJzz8rD9KZv21lb4cyM47Lt8Q83niPlr+Ioy4OG3xam6BUzFi6MZOFeLgLyC7Afw 65Ge9tgrpIXG3poLWvfbMIZEnbuNGk7/5V/wIu0+UUR5DfTMorYg3ymW1BIgYvHSHt/Q A+rw==
X-Gm-Message-State: AGRZ1gJCPMJDt3f7LC/W/mYeLoc8HJuWmjIhbHYb8qzIQzLOtmZUvNlF 4Xe0URGCziq1BR70dsdXhrJ2VyIa
X-Google-Smtp-Source: AJdET5cRBbsx+Ujm9l4V1K1yF3BryWjvFCHDX8/UjyZP09qliKbNubVyMvmqA6JDbA69JMNX+U/+DQ==
X-Received: by 2002:a37:2bcf:: with SMTP id r76mr14347679qkr.218.1540882861993;  Tue, 30 Oct 2018 00:01:01 -0700 (PDT)
Received: from DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM ([40.101.73.61]) by smtp.gmail.com with ESMTPSA id h49-v6sm17289214qth.32.2018.10.30.00.00.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Oct 2018 00:01:00 -0700 (PDT)
From: =?Windows-1252?Q?Mikkel_Fahn=F8e_J=F8rgensen?= <mikkelfj@gmail.com>
To: Christian Huitema <huitema@huitema.net>, "quic@ietf.org" <quic@ietf.org>
Subject: Re: Structuring the BKK spin bit discussion
Thread-Topic: Structuring the BKK spin bit discussion
Thread-Index: ATk3NTQ0ZtY1VqWVb0gqyyB8bFiFRjhEMDExM0ZBNEV3VC12LTQ2MjRDN2MxODGr/hIiyg==
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Tue, 30 Oct 2018 07:00:57 +0000
Message-ID: <DB6PR10MB1766E6B29792BB4401FF38F0ACCC0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com> <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch>, <a088c411-1acc-8b0f-fc1b-8c79ce6f1cd7@huitema.net>
In-Reply-To: <a088c411-1acc-8b0f-fc1b-8c79ce6f1cd7@huitema.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator: 
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: multipart/alternative; boundary="_000_DB6PR10MB1766E6B29792BB4401FF38F0ACCC0DB6PR10MB1766EURP_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qrGq-pJHYNpOKDS4ymJUN3-0Ej8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 07:01:06 -0000

--_000_DB6PR10MB1766E6B29792BB4401FF38F0ACCC0DB6PR10MB1766EURP_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

In the Netflix case it just takes 16 connections by the same user, or less =
when multiple users originate from the sane IP range. Is it really practica=
l (and thus worthwhile) to hide probabilistically as in Huitemas PR?

________________________________
From: QUIC <quic-bounces@ietf.org> on behalf of Christian Huitema <huitema@=
huitema.net>
Sent: Tuesday, October 30, 2018 5:27:47 AM
To: quic@ietf.org
Subject: Re: Structuring the BKK spin bit discussion


On 10/29/2018 3:58 PM, Brian Trammell (IETF) wrote:

hi Martin, Christian, all,



On 29 Oct 2018, at 23:29, Martin Thomson <martin.thomson@gmail.com><mailto:=
martin.thomson@gmail.com> wrote:

On Tue, Oct 30, 2018 at 3:54 AM Christian Huitema <huitema@huitema.net><mai=
lto:huitema@huitema.net> wrote:


I think the strongest objection to the spin bit was put up by Marten during=
 the last interim: measuring the RTT with the spin bit discloses the use of=
 hidden path segments like VPN. This issue was not discussed during the pri=
vacy analysis.


I had assumed that was part of the analysis and it was covered by the
assumption that spinning could be disabled


+1. Probabilistically disabling spinning, which seems necessary if we want =
some grease to help us reserve the right to change the semantics of the bit=
 at the spin bit's location in the wire image, should ensure that endpoints=
 that want to disable spinning for their own reasons will have a large anon=
ymity set to hide in, even in a future with perfect implementation and depl=
oyment of the spin bit.


I opened PR https://github.com/quicwg/base-drafts/pull/1931 to discuss this=
.

-- Christian Huitema

--_000_DB6PR10MB1766E6B29792BB4401FF38F0ACCC0DB6PR10MB1766EURP_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta content=3D"text/html; charset=3DWindows-1252">
</head>
<body bgcolor=3D"#FFFFFF">
<div id=3D"compose-container" itemscope=3D"" itemtype=3D"https://schema.org=
/EmailMessage" style=3D"direction:ltr">
<span itemprop=3D"creator" itemscope=3D"" itemtype=3D"https://schema.org/Or=
ganization"><span itemprop=3D"name"></span></span>
<div>
<div>
<div style=3D"direction:ltr">In the Netflix case it just takes 16 connectio=
ns by the same user, or less when multiple users originate from the sane IP=
 range. Is it really practical (and thus worthwhile) to hide probabilistica=
lly as in Huitemas PR?</div>
</div>
<div><br>
</div>
<div class=3D"acompli_signature"></div>
</div>
</div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" co=
lor=3D"#000000" style=3D"font-size:11pt"><b>From:</b> QUIC &lt;quic-bounces=
@ietf.org&gt; on behalf of Christian Huitema &lt;huitema@huitema.net&gt;<br=
>
<b>Sent:</b> Tuesday, October 30, 2018 5:27:47 AM<br>
<b>To:</b> quic@ietf.org<br>
<b>Subject:</b> Re: Structuring the BKK spin bit discussion</font>
<div>&nbsp;</div>
</div>
<div>
<p>On 10/29/2018 3:58 PM, Brian Trammell (IETF) wrote:<br>
</p>
<blockquote type=3D"cite">
<pre>hi Martin, Christian, all,

</pre>
<blockquote type=3D"cite" style=3D"color:#000000">
<pre>On 29 Oct 2018, at 23:29, Martin Thomson <a class=3D"moz-txt-link-rfc2=
396E" href=3D"mailto:martin.thomson@gmail.com">&lt;martin.thomson@gmail.com=
&gt;</a> wrote:

On Tue, Oct 30, 2018 at 3:54 AM Christian Huitema <a class=3D"moz-txt-link-=
rfc2396E" href=3D"mailto:huitema@huitema.net">&lt;huitema@huitema.net&gt;</=
a> wrote:
</pre>
<blockquote type=3D"cite" style=3D"color:#000000">
<pre>I think the strongest objection to the spin bit was put up by Marten d=
uring the last interim: measuring the RTT with the spin bit discloses the u=
se of hidden path segments like VPN. This issue was not discussed during th=
e privacy analysis.
</pre>
</blockquote>
<pre>I had assumed that was part of the analysis and it was covered by the
assumption that spinning could be disabled
</pre>
</blockquote>
<pre>&#43;1. Probabilistically disabling spinning, which seems necessary if=
 we want some grease to help us reserve the right to change the semantics o=
f the bit at the spin bit's location in the wire image, should ensure that =
endpoints that want to disable spinning for their own reasons will have a l=
arge anonymity set to hide in, even in a future with perfect implementation=
 and deployment of the spin bit.
</pre>
</blockquote>
<br>
I opened PR <a class=3D"moz-txt-link-freetext" href=3D"https://github.com/q=
uicwg/base-drafts/pull/1931">
https://github.com/quicwg/base-drafts/pull/1931</a> to discuss this.<br>
<br>
-- Christian Huitema<br>
</div>
</body>
</html>

--_000_DB6PR10MB1766E6B29792BB4401FF38F0ACCC0DB6PR10MB1766EURP_--


From nobody Tue Oct 30 02:25:30 2018
Return-Path: <emile.stephan@orange.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 9891B12DD85 for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 02:25:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 kflF-xTXTiex for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 02:25:27 -0700 (PDT)
Received: from orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F47312D4E9 for <quic@ietf.org>; Tue, 30 Oct 2018 02:25:27 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar24.francetelecom.fr (ESMTP service) with ESMTP id 42kmKK2C7wz5wZl; Tue, 30 Oct 2018 10:25:25 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.62]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 42kmKK18QLzCql8; Tue, 30 Oct 2018 10:25:25 +0100 (CET)
Received: from OPEXCLILM44.corporate.adroot.infra.ftgroup ([fe80::b08d:5b75:e92c:a45f]) by OPEXCLILM5E.corporate.adroot.infra.ftgroup ([fe80::6958:931c:a396:f51e%19]) with mapi id 14.03.0415.000; Tue, 30 Oct 2018 10:25:24 +0100
From: <emile.stephan@orange.com>
To: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>, "Mark Nottingham (mnot@mnot.net)" <mnot@mnot.net>
Subject: RE: Structuring the BKK spin bit discussion: and manufacturers  ?
Thread-Topic: Structuring the BKK spin bit discussion: and manufacturers  ?
Thread-Index: AdRwMN0q8nufqw+XQKmj2dkifZmc5A==
Date: Tue, 30 Oct 2018 09:25:24 +0000
Message-ID: <20130_1540891525_5BD82385_20130_144_8_5AE9CCAA1B4A2248AB61B4C7F0AD5FB93140A4EE@OPEXCLILM44.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.2]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/nDwxYtcW_jLriFkX-G1fAxbJPH4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 09:25:28 -0000

Hi

IMO manufacturers of any sort of devices (router, box, proxy, mobile equipm=
ent...) should start sharing their intends too.

Regards
Emile

-----Message d'origine-----
De=A0: QUIC [mailto:quic-bounces@ietf.org] De la part de Lars Eggert
Envoy=E9=A0: lundi 29 octobre 2018 16:27
=C0=A0: IETF QUIC WG
Objet=A0: Structuring the BKK spin bit discussion

Hi,

you'll have seen that we've set aside a lengthy slot on the agenda in order=
 to finish the discussion on whether the spin bit (described in draft-ietf-=
quic-spin-exp) should be included in the first version of QUIC the IETF pub=
lishes, and if yes, what shape that inclusion would take.

Note that draft-ietf-quic-spin-exp describes what we commonly call the sing=
le-bit spin bit variant. We'd like to confirm that the discussion will be l=
imited to that variant.

Next, we'd like to confirm that the WG believes that it is fit-for purpose,=
 i.e., that if a sufficient number of bits were spinning, operators could o=
btain the information they need. This also includes confirmation that the p=
rivacy aspects of the spin bit proposal are understood and acceptable to th=
e WG.

We'd specifically like to ask client and server implementors with projected=
 sizable deployments to indicate whether they intent to implement and deplo=
y, if the WG decided to include the spin-bit in the spec. We have seen one =
such statement on the list from Microsoft (thank you!) and would be interes=
ted to hear from others, either on the list or during the session in Bangko=
k.

Finally, if the WG has agreement to include the spin bit in the spec based =
on the information from and the discussion on the points above, we need to =
come to consensus on what shape such an inclusion of the spin bit would tak=
e, e.g., negotiated extension, conformance requirements (MAY/SHOULD/MUST) f=
or clients and servers, etc.

Please let us know if you have any questions or comments about this approac=
h for structuring the discussion in Bangkok.

Lars and Mark

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Tue Oct 30 03:20:14 2018
Return-Path: <alexandre.ferrieux@orange.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 3FDC2130DCA for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 03:20:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.291
X-Spam-Level: 
X-Spam-Status: No, score=-0.291 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 E9GNwrlVCfTi for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 03:20:08 -0700 (PDT)
Received: from orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03685130DCB for <quic@ietf.org>; Tue, 30 Oct 2018 03:20:08 -0700 (PDT)
Received: from opfedar01.francetelecom.fr (unknown [xx.xx.xx.2]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id 42knXQ5lh0z7tfn; Tue, 30 Oct 2018 11:20:06 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfedar01.francetelecom.fr (ESMTP service) with ESMTP id 42knXQ4fK4zBrLg; Tue, 30 Oct 2018 11:20:06 +0100 (CET)
Received: from [10.193.4.89] (10.168.234.6) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 30 Oct 2018 11:20:06 +0100
Subject: Re: Big changes in -17
To: Martin Thomson <martin.thomson@gmail.com>
CC: QUIC WG <quic@ietf.org>
References: <CABkgnnVFqdx4VYbqT7SztPf8Q+vWMV86VkOHY-4aGSpauNPapg@mail.gmail.com> <851_1540819578_5BD70A7A_851_343_1_0ada4f1d-e8c5-25b5-0e8b-8111ee726ae7@orange.com> <CABkgnnVG6tT_h9AyoOSBd6qy5eRn0EZ4LO_Z+h-cTgj+MkECmA@mail.gmail.com>
Reply-To: Alexandre Ferrieux <alexandre.ferrieux@orange.com>
From: <alexandre.ferrieux@orange.com>
Organization: Orange
Message-ID: <22357_1540894806_5BD83056_22357_330_7_c18e3fda-3a7f-bd02-a573-6933ed38e23a@orange.com>
Date: Tue, 30 Oct 2018 11:20:07 +0100
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnVG6tT_h9AyoOSBd6qy5eRn0EZ4LO_Z+h-cTgj+MkECmA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: fr-xx-moderne
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.168.234.6]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/rIVGldHYoTBtBuot8uI44KWf0eo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 10:20:13 -0000

On 10/29/2018 11:35 PM, Martin Thomson wrote:
> On Tue, Oct 30, 2018 at 12:26 AM <alexandre.ferrieux@orange.com> wrote:
>> Do I assume correctly that "the designs discussed" are the following three:
>>
>>   - nothing (no spin bit)
>>   - spin bit alone
>>   - spin bit + VEC
>>
>> Or is there room for other (written) proposals ?
> 
> You should refer to the email from Lars.  I believe that the approach
> they propose only considers "no spin bit" vs. "spin bit alone".

Then, this means that the two reserved bits (0x3 in 1st byte) are out of scope 
for v1, right ?


_________________________________________________________________________________________________________________________

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.


From nobody Tue Oct 30 03:28:02 2018
Return-Path: <lars@eggert.org>
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 7B3D7130DED for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 03:27:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 Zlk1Nx9aaW9K for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 03:27:49 -0700 (PDT)
Received: from emh02.mail.saunalahti.fi (emh02.mail.saunalahti.fi [62.142.5.108]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B29B128DFD for <quic@ietf.org>; Tue, 30 Oct 2018 03:27:49 -0700 (PDT)
Received: from eggert.org (unknown [62.248.255.56]) by emh02.mail.saunalahti.fi (Postfix) with ESMTP id 79EED202D0; Tue, 30 Oct 2018 12:27:47 +0200 (EET)
Received: from slate.eggert.org (pf.eggert.org [172.16.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by eggert.org (Postfix) with ESMTPSA id 89ED361235D; Tue, 30 Oct 2018 12:27:41 +0200 (EET)
From: Lars Eggert <lars@eggert.org>
Message-Id: <3386479D-9FC1-4A2E-A8A3-1F2A4F247232@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_B07A6608-CFA5-4FF2-B053-DB53945400FB"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: Re: Structuring the BKK spin bit discussion: and manufacturers  ?
Date: Tue, 30 Oct 2018 12:27:41 +0200
In-Reply-To: <20130_1540891525_5BD82385_20130_144_8_5AE9CCAA1B4A2248AB61B4C7F0AD5FB93140A4EE@OPEXCLILM44.corporate.adroot.infra.ftgroup>
Cc: IETF QUIC WG <quic@ietf.org>, Mark Nottingham <mnot@mnot.net>
To: "<emile.stephan@orange.com>" <emile.stephan@orange.com>
References: <20130_1540891525_5BD82385_20130_144_8_5AE9CCAA1B4A2248AB61B4C7F0AD5FB93140A4EE@OPEXCLILM44.corporate.adroot.infra.ftgroup>
X-MailScanner-ID: 89ED361235D.A2594
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/675RHdOSmhoqrfrI94R4tuvJQsg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 10:28:02 -0000

--Apple-Mail=_B07A6608-CFA5-4FF2-B053-DB53945400FB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2018-10-30, at 11:25, emile.stephan@orange.com wrote:
> IMO manufacturers of any sort of devices (router, box, proxy, mobile =
equipment...) should start sharing their intends too.

certainly, there's no harm in that.

But since it's the QUIC clients that need to spin and the QUIC servers =
that need to echo, we're specifically interested in the level of =
implementation interest there.

Lars

--Apple-Mail=_B07A6608-CFA5-4FF2-B053-DB53945400FB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAlvYMh0ACgkQVLXDCb9w
wVcZag/7Betfb6h9qrmpBOxAFg+pVegQHhW1Pj1x0dgDctyNiAEyVS2w6FhEVZVO
fljWJSpOrpaXXehe6Wn7j9y/GEDIjlu7cMkVIkvKe+BIqac0Sx4ruRfRucsjTlhe
YBAqV8NoLKBwY5NbR+hDXbnMPxfSpwSa/SumYkN2o9/LebHKwyh2aY8ODWsHgTut
NT6rST9U5HBv0RyM5bYY0/jR/3Y7WpCpU02I175nc7LgNnnJkUL/528NMFRNbToC
pj2bGVTbktJohegiVoPIUCvbx45wCKn3X8bEpqts36bNdnTzIhA8iagutbo1FZeN
Q/K/mNayfCx3aeZkBDtotp2+2+LI8vZ5IBBXHKpfiGrLnlLqxn2ytaeHvUpJ/JNa
n4XiRAXU2obt4hzypf1oZ2iSxXHgxxLWrO9bY5h4DfejWagonWuoWcfWKBiB9akr
wAMAFAHOGR158Nvq6J8bHeuJIQjdXu1GOCwYyml5i2gf6WqUmPBqeXOYt61GLXu9
feH8g9lyQHjhOUJp9zs+ZGQnOco+DB+tY+7KwmbkgK9ayb0lc6uAvZtXdNn0LCqX
TuI5ql+fF6SpNj1/5vHOUp282HuCBNl8srhvctIpxI3zLIvq6jBB5YKIHdIiSeqz
zAKPK+O1+l/G3AnBgr6ux5pxrDvNVbWJqafSd+o7N/BU3KYtYyQ=
=YdJq
-----END PGP SIGNATURE-----

--Apple-Mail=_B07A6608-CFA5-4FF2-B053-DB53945400FB--


From nobody Tue Oct 30 04:05:45 2018
Return-Path: <martin.thomson@gmail.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 B3126128B14 for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 04:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 JQGLLgjaWe-j for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 04:05:42 -0700 (PDT)
Received: from mail-ot1-x329.google.com (mail-ot1-x329.google.com [IPv6:2607:f8b0:4864:20::329]) (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 2A927126CC7 for <quic@ietf.org>; Tue, 30 Oct 2018 04:05:42 -0700 (PDT)
Received: by mail-ot1-x329.google.com with SMTP id d5so10652240oti.6 for <quic@ietf.org>; Tue, 30 Oct 2018 04:05:42 -0700 (PDT)
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=wFme/CzQX2OW3aQRYR2Y/8BEzFM88lnD6k/77uTdXig=; b=TS5RkGXYGpaZcoqNtMRoaZLeQUB2F0Ih0h0an3bsS2LvN7ESJTP10OC8NDWZGhOVyK f2wuoChBzoI5/Hjh4Cl+F6D8gRJSXbnE7dtVd2OZMnWJuqyO1lIZslkdQ/hWp6G+BF6n 2jo8y+kZ62Lik5cBND2ygMcvQZ0fiNIEAcUgoR5a8bzhVzkqLzCBnBatS5jSi+PV+h4i 1U5OXbdDSDBOLasYqF+udlgN29K5rZJQHj221BEYeOxNy1hZYKdQgCdJAkbJJrmfBFHk tasWrL3tgQTtJ5PtpbRPdvz4lZvyFEhQDbSLAYFkzFpncjT9oqfuWozlza4Qz1kaAzXp sS+Q==
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=wFme/CzQX2OW3aQRYR2Y/8BEzFM88lnD6k/77uTdXig=; b=ryNl8UgIES2SsAjTFQYjjxXdpJVFOxrcmekuKoHB9ykJepdwlbP7seUdbUouwNByQv QcjaR1ZFObmtau5uGzUB+dFKGQj4Vh8FRFC9k6QjnQ2NsMBMZwp+4cjcMZ8W/cJQJxAg K2p9NnXKr4tmSbCTTf/hSV9WZQu+3a98CZfbLA76GOWDKnn+/Cu6tT/eP99rq172txiX aYTtJ4CAQjMNT5T7XnoTIXXR2HgJDsQEVxCKyg0RapOL+eFZG9SI6/ptT2eaekKTN2x+ 6Y6YEbExhaWwXvoOaGatFaXwxQex0Oqz9KbV+w8qvFbEacrbqlVu2NaymUQW2ZOtsNTG ZZng==
X-Gm-Message-State: AGRZ1gJOAqL9YjzQIewg4y9vwtDNxhbRbuRiSbQbogVJCFWGjf/lEQ4t 5EhkVG77cTicAFnEH+SwqOiYnI2HnZkxk9osUEs=
X-Google-Smtp-Source: AJdET5eh5ery2Z4a7A0yJ79tOH6c801gzxBLVUy6DfGW21nj65ijEkc3Uf/EZ+zbdDt5B7JTFyri5et+hcJE3IzNuC8=
X-Received: by 2002:a9d:4185:: with SMTP id p5mr3592751ote.9.1540897541270; Tue, 30 Oct 2018 04:05:41 -0700 (PDT)
MIME-Version: 1.0
References: <CABkgnnVFqdx4VYbqT7SztPf8Q+vWMV86VkOHY-4aGSpauNPapg@mail.gmail.com> <851_1540819578_5BD70A7A_851_343_1_0ada4f1d-e8c5-25b5-0e8b-8111ee726ae7@orange.com> <CABkgnnVG6tT_h9AyoOSBd6qy5eRn0EZ4LO_Z+h-cTgj+MkECmA@mail.gmail.com> <22357_1540894806_5BD83056_22357_330_7_c18e3fda-3a7f-bd02-a573-6933ed38e23a@orange.com>
In-Reply-To: <22357_1540894806_5BD83056_22357_330_7_c18e3fda-3a7f-bd02-a573-6933ed38e23a@orange.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 30 Oct 2018 22:05:31 +1100
Message-ID: <CABkgnnVmWuYNp7XL+4_qMNHXncrrMV2NT=nL-k8wE0ASeBRbkQ@mail.gmail.com>
Subject: Re: Big changes in -17
To: alexandre.ferrieux@orange.com
Cc: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/kwiKHGYPzijdQh_WEGdbcFiKS5E>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 11:05:44 -0000

On Tue, Oct 30, 2018 at 9:20 PM <alexandre.ferrieux@orange.com> wrote:
> Then, this means that the two reserved bits (0x3 in 1st byte) are out of scope
> for v1, right ?

As our chairs said:

> Note that draft-ietf-quic-spin-exp describes what we commonly call the single-bit spin bit variant. We'd like to confirm that the discussion will be limited to that variant.

I read that as saying that this needs to be confirmed.


From nobody Tue Oct 30 04:56:38 2018
Return-Path: <marcus.ihlar@ericsson.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 EF812129385 for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 04:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 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, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=cMkWYp5w; dkim=pass (1024-bit key) header.d=ericsson.com header.b=aViS7LVa
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 bT9paD1CkVkn for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 04:56:33 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 DD1C612D4EF for <quic@ietf.org>; Tue, 30 Oct 2018 04:56:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple;  q=dns/txt; i=@ericsson.com; t=1540900588; x=1543492588; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Bd6mYphAI/MDjdmIKBlo7Dnat9G1PQwRx5EyoesMxg8=; b=cMkWYp5wDD4VtpYxGxXU7JRTEe/q4Um/cP0I8bRqFjoOMs6fCUEVJ7PJfLXeykUE S8Wma31ALa46DH1hOd5aP4WfgZxQd/4ioaFSDqj/6F5QA9/derMPPjkI+7hN5BL4 FV2YqyHooI46lCt6Ak2Be/4aLVES08OIkeRp7UH1e0Q=;
X-AuditID: c1b4fb25-f3b359e00000414e-51-5bd846ec5170
Received: from ESESSMB504.ericsson.se (Unknown_Domain [153.88.183.122]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 2D.00.16718.CE648DB5; Tue, 30 Oct 2018 12:56:28 +0100 (CET)
Received: from ESESBMR503.ericsson.se (153.88.183.135) by ESESSMB504.ericsson.se (153.88.183.192) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Tue, 30 Oct 2018 12:55:59 +0100
Received: from ESESSMB504.ericsson.se (153.88.183.165) by ESESBMR503.ericsson.se (153.88.183.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Tue, 30 Oct 2018 12:55:58 +0100
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB504.ericsson.se (153.88.183.165) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Tue, 30 Oct 2018 12:55:58 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=odYsnlxwi9T7fDEYVqXRaw4Pwm2bVmmr3rqz4zPj8S8=; b=aViS7LVaoHHO3kTrUn2NsAx1QuzkC5NOqfwVDO6ELbSVP1sCztIUl2ybtqf/J3+ekQjuJUOpVSbgIpLmD3FoCMIq29EEEYYM5d63gQ2fk/uZ6tjlQboEmPae9UAoD4nzISxK97ASJ/iEn4Akqcd0yjWiJYJqpOT4UwVHawe2jZk=
Received: from HE1PR0701MB2393.eurprd07.prod.outlook.com (10.168.128.12) by HE1PR0701MB2092.eurprd07.prod.outlook.com (10.168.35.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1294.14; Tue, 30 Oct 2018 11:55:57 +0000
Received: from HE1PR0701MB2393.eurprd07.prod.outlook.com ([fe80::1b9:990b:7c9f:1cf5]) by HE1PR0701MB2393.eurprd07.prod.outlook.com ([fe80::1b9:990b:7c9f:1cf5%5]) with mapi id 15.20.1294.018; Tue, 30 Oct 2018 11:55:57 +0000
From: Marcus Ihlar <marcus.ihlar@ericsson.com>
To: "mikkelfj@gmail.com" <mikkelfj@gmail.com>, "huitema@huitema.net" <huitema@huitema.net>, "quic@ietf.org" <quic@ietf.org>
Subject: RE: Structuring the BKK spin bit discussion
Thread-Topic: Structuring the BKK spin bit discussion
Thread-Index: AQHUb5vbxC4W7eXZzE+qDxda0MBukqU2Y+yAgAAMqQCAAF4GgIAAB/iAgABcB4CAACrLgIAATjcg
Date: Tue, 30 Oct 2018 11:55:57 +0000
Message-ID: <HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com> <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch>, <a088c411-1acc-8b0f-fc1b-8c79ce6f1cd7@huitema.net> <DB6PR10MB1766E6B29792BB4401FF38F0ACCC0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM>
In-Reply-To: <DB6PR10MB1766E6B29792BB4401FF38F0ACCC0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.176.1.83]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR0701MB2092; 6:CbTYtLWGKu+VlDkPfhc0j2Fuhx3MmePCNDUp9Rb+/oM5+tgwTtPa+y6wJly8E6G4izLtQRv2MA3qrJh5p4p31lL6UV8KYp0lxW63evM6eoWzUkJQV+Kb1Rp0Udlkp5+VQp4pTc1eVWntJKRQUlbNHHh6AQNgTWo1MYSfXVaWm9+KMs3EugqpYxGO9Ol5JIJKItooIl7EI5dbJC0FBPaWFXG/7Zo0sns7PTTvOZ9X7EyRt1PGjLLAgZKHRp4mXQ1+hx9e8geYaRIhGIwjTKAZYDF50s5Vax1Sy/26JRneTCovPtmDw36Us8LkHo2Vrbxn7lhzl7oL9wufZLPddLCpz2yRiTRixY095tmSja2lrbAVa5DJepDegYDw+hHJ1YwWtiWYijDOquaFxoM7P29zMDiDnJuZj12c4yV0OgJ9FXHGaWbkAKn6HGQGIgRdWb/Q4SxuvR7bOCJQ9fCiA1hBiA==; 5:8uKiwXP87vU/ckWWh/tMY39dwq74Fp7lh9LlhLZc9oflEvaP6CPFssjJMAmmuBQEWAOCQyCGLA52RhvG4liRCdnmbLfiCrHAGFZNlPRLgprPSR8iD5lkDVaR5QIzFjktR/Ja1ampG1GneXxalQnQElY/XGy9KVAvndJE6M0LYAo=; 7:T01ldd3kQewU/ALgUo2d2Ho/1gFkDde6d1l81osML0DjQOOImxIf/tCO0tzP44amVtxeNKiSBY4MZBVfItDv61v3BOECLmZ3VGtRH6hozQHRzTFAc3xbtFTpwpScvbx8Kz3HYUi04t0SFIOeaQK2QQ==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: dfba905a-5a61-47d6-8b54-08d63e5ea766
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:HE1PR0701MB2092; 
x-ms-traffictypediagnostic: HE1PR0701MB2092:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=marcus.ihlar@ericsson.com; 
x-microsoft-antispam-prvs: <HE1PR0701MB20922193E88A68E088D30CC0E2CC0@HE1PR0701MB2092.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(85827821059158)(166708455590820)(21748063052155)(28532068793085)(190501279198761)(227612066756510);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(3231382)(944501410)(52105095)(148016)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123564045)(20161123560045)(20161123558120)(201708071742011)(7699051)(76991095); SRVR:HE1PR0701MB2092; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0701MB2092; 
x-forefront-prvs: 08417837C5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(136003)(39860400002)(346002)(366004)(376002)(189003)(199004)(86362001)(6436002)(7696005)(44832011)(6506007)(8936002)(8676002)(26005)(81166006)(81156014)(102836004)(76176011)(186003)(446003)(68736007)(256004)(14444005)(790700001)(6116002)(486006)(476003)(66574009)(11346002)(478600001)(606006)(71190400001)(316002)(93886005)(71200400001)(14454004)(2201001)(105586002)(106356001)(966005)(2501003)(5250100002)(53546011)(97736004)(3846002)(229853002)(25786009)(66066001)(561944003)(2900100001)(33656002)(99286004)(74316002)(2906002)(9686003)(5660300001)(54896002)(39060400002)(236005)(110136005)(6306002)(55016002)(7736002)(53936002)(6246003); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0701MB2092; H:HE1PR0701MB2393.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: t1YntEGlckaf2e8+q9ajRDocSNpvUOQtI6osxGXaorSzhAQdudabCMqcBuRN8e8Mm96uzz845v3gdXlEovp+sb/n1i4GLR3l7arwYeoqJ5km9505Qatsia+pzue+s1txjeULhwSCBoit3IE7O+P+OeTEutrAZmWxoBcaXRcVwzoLTz/pkNGbykMEGTCM6Q41J8WM0kVpjAlcGSxj6QeN1J1sucHBipCkrAHXo8R3z4oPfcf3przand/8NARcWqxBttIhh5m7Un85W1ShEg9JaUXlr3CeOoN0l64qGY5hT4j971y+PTFzmm6qJgNuMiKvhMTJoY23ZVGXqToekJjJr87LrgD+tOL9Dfl8l195xEs=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0HE1PR0701MB2393_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: dfba905a-5a61-47d6-8b54-08d63e5ea766
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Oct 2018 11:55:57.4365 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2092
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA03SfyyUcRwH8H3vee7ucbnt20U+Uyy3WSJ3VJYta2UNWzT9USsiJ8+wONyD RWuotfnZiCs/VkeO0CpUfkW4qBEl+uOSH5lry7BVW52jWff4avPf6/t5f77f5/PZHoaSNQsd mXh1KqtRqxLkIgldca4903MpwBju1dez17c0p0rsW2t+RfkWVm87RgV1Vk6LgybLh+kgvd4i CKXCJH4xbEJ8OqtRHo2SxFU90AqTF4KvtNT/Fmaje/75yIYBfAjyarupfCRhZHgAwerTXpoP ZPgPgjHdWRJY3f6xC5GDXgC3ll8K+AONiykwViwKSXJXAN+GGyhy34Sgt5PjLcIKGJkuEPG2 w9dgyNIj5L3D+vGpXMNm3QdKWkc3HQZ3Sh4h3jR2hdUvTdZ+hpHiKJh470Ke11Gw8CmQtw2O gI6x+xtPIuwEs+aZjRUo7ACTJp2A7IlB3/2BIraHhfl1IfEemNI+FhM7wbiuYGNLwEYRdNS1 IBJ4wg+tdvNyCEyau0SkaQjBzED9xnCA98Ovh5E8Eb5gnTmZtCfBqH5QRFyEYPBNALEzNBXN 0cXIq3LLqMRJkLM8T/OW4u0wVGGiSV0BRm2ZiNgD6msWKWJPKF830Fvr1UjchOw5lotOjD1w UMFq4i9xXJJaoWZTW5H1P+p/vubagSaWjhsQZpDcVjrkaQyXCVXpXEaiAQFDye2k6f7WkjRG lZHJapIuatISWM6AdjG03EE6d/hZmAzHqlLZyyybzGr+pwLGxjEblSksknhLX0WkneKnW8/A CZ8bs7fPuF+3eAeaDVkn097lLL1Qmv3PO5vZMDovZvp7VsDMerM8xfS6cMm+zdYlRLm97q85 wuPm/ELj6dC00uD1ms/RBZHKFUVjYFu/2ivGbcxv7YhHz6mRr7pc8dsnu9VXW+Up+6jOlbyJ gZ0N40o5zcWpvN0pDaf6B/RP1GVDAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/4wGIAh1L3esU1MHVQxBamSkG6Ok>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 11:56:36 -0000

--_000_HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0HE1PR0701MB2393_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Making it more difficult to differentiate explicit opt-out from random opt-=
out is likely useful even if it doesn't help in the particular Netflix case=
.

Furthermore, just like Brian points out it is necessary to grease the bit i=
f we want to change the bit semantics later on.

I think the proposal has low enough complexity and potential benefits to be=
 worthwhile.



From: QUIC <quic-bounces@ietf.org> On Behalf Of Mikkel Fahn=F8e J=F8rgensen
Sent: den 30 oktober 2018 08:01
To: Christian Huitema <huitema@huitema.net>; quic@ietf.org
Subject: Re: Structuring the BKK spin bit discussion



In the Netflix case it just takes 16 connections by the same user, or less =
when multiple users originate from the sane IP range. Is it really practica=
l (and thus worthwhile) to hide probabilistically as in Huitemas PR?



  _____

From: QUIC <quic-bounces@ietf.org<mailto:quic-bounces@ietf.org>> on behalf =
of Christian Huitema <huitema@huitema.net<mailto:huitema@huitema.net>>
Sent: Tuesday, October 30, 2018 5:27:47 AM
To: quic@ietf.org<mailto:quic@ietf.org>
Subject: Re: Structuring the BKK spin bit discussion



On 10/29/2018 3:58 PM, Brian Trammell (IETF) wrote:

   hi Martin, Christian, all,


      On 29 Oct 2018, at 23:29, Martin Thomson <martin.thomson@gmail.com><m=
ailto:martin.thomson@gmail.com> wrote:

      On Tue, Oct 30, 2018 at 3:54 AM Christian Huitema <huitema@huitema.ne=
t><mailto:huitema@huitema.net> wrote:

         I think the strongest objection to the spin bit was put up by Mart=
en during the last interim: measuring the RTT with the spin bit discloses t=
he use of hidden path segments like VPN. This issue was not discussed durin=
g the privacy analysis.

      I had assumed that was part of the analysis and it was covered by the
      assumption that spinning could be disabled

   +1. Probabilistically disabling spinning, which seems necessary if we wa=
nt some grease to help us reserve the right to change the semantics of the =
bit at the spin bit's location in the wire image, should ensure that endpoi=
nts that want to disable spinning for their own reasons will have a large a=
nonymity set to hide in, even in a future with perfect implementation and d=
eployment of the spin bit.


   I opened PR https://github.com/quicwg/base-drafts/pull/1931 to discuss t=
his.

   -- Christian Huitema


--_000_HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0HE1PR0701MB2393_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" lang=3D"SV" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"mso-fareast-language:E=
N-US">Making it more difficult to differentiate explicit opt-out from rando=
m opt-out is likely useful even if it doesn&#8217;t help in the particular =
Netflix case.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"mso-fareast-language:E=
N-US">Furthermore, just like Brian points out it is necessary to grease the=
 bit if we want to change the bit semantics later on.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"mso-fareast-language:E=
N-US">I think the proposal has low enough complexity and potential benefits=
 to be worthwhile.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"mso-fareast-language:E=
N-US"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> QUIC &lt;quic-bounces@ietf.org&gt;
<b>On Behalf Of </b>Mikkel Fahn=F8e J=F8rgensen<br>
<b>Sent:</b> den 30 oktober 2018 08:01<br>
<b>To:</b> Christian Huitema &lt;huitema@huitema.net&gt;; quic@ietf.org<br>
<b>Subject:</b> Re: Structuring the BKK spin bit discussion<o:p></o:p></spa=
n></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div id=3D"compose-container">
<div>
<div>
<div>
<p class=3D"MsoNormal">In the Netflix case it just takes 16 connections by =
the same user, or less when multiple users originate from the sane IP range=
. Is it really practical (and thus worthwhile) to hide probabilistically as=
 in Huitemas PR?<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"98%" align=3D"center">
</div>
<div id=3D"divRplyFwdMsg">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From:</span></b><span=
 style=3D"color:black"> QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org">q=
uic-bounces@ietf.org</a>&gt; on behalf of Christian Huitema &lt;<a href=3D"=
mailto:huitema@huitema.net">huitema@huitema.net</a>&gt;<br>
<b>Sent:</b> Tuesday, October 30, 2018 5:27:47 AM<br>
<b>To:</b> <a href=3D"mailto:quic@ietf.org">quic@ietf.org</a><br>
<b>Subject:</b> Re: Structuring the BKK spin bit discussion</span> <o:p></o=
:p></p>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
<div>
<p>On 10/29/2018 3:58 PM, Brian Trammell (IETF) wrote:<o:p></o:p></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>hi Martin, Christian, all,<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style=3D"color:black">On 29 Oct 2018, at 23:29, Martin Thomson <=
a href=3D"mailto:martin.thomson@gmail.com">&lt;martin.thomson@gmail.com&gt;=
</a> wrote:<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">On Tue, Oct 30, 2018 at 3:54 AM Christian =
Huitema <a href=3D"mailto:huitema@huitema.net">&lt;huitema@huitema.net&gt;<=
/a> wrote:<o:p></o:p></span></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style=3D"color:black">I think the strongest objection to the spi=
n bit was put up by Marten during the last interim: measuring the RTT with =
the spin bit discloses the use of hidden path segments like VPN. This issue=
 was not discussed during the privacy analysis.<o:p></o:p></span></pre>
</blockquote>
<pre><span style=3D"color:black">I had assumed that was part of the analysi=
s and it was covered by the<o:p></o:p></span></pre>
<pre><span style=3D"color:black">assumption that spinning could be disabled=
<o:p></o:p></span></pre>
</blockquote>
<pre>&#43;1. Probabilistically disabling spinning, which seems necessary if=
 we want some grease to help us reserve the right to change the semantics o=
f the bit at the spin bit's location in the wire image, should ensure that =
endpoints that want to disable spinning for their own reasons will have a l=
arge anonymity set to hide in, even in a future with perfect implementation=
 and deployment of the spin bit.<o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal"><br>
I opened PR <a href=3D"https://github.com/quicwg/base-drafts/pull/1931">htt=
ps://github.com/quicwg/base-drafts/pull/1931</a> to discuss this.<br>
<br>
-- Christian Huitema<o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0HE1PR0701MB2393_--


From nobody Tue Oct 30 06:05:37 2018
Return-Path: <dtikhonov@litespeedtech.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 D1AC7127AC2 for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 06:05:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 F2fB7pEF95tq for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 06:05:33 -0700 (PDT)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (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 2AA3712D4EC for <quic@ietf.org>; Tue, 30 Oct 2018 06:05:33 -0700 (PDT)
Received: by mail-qt1-x82f.google.com with SMTP id z2-v6so13326124qts.1 for <quic@ietf.org>; Tue, 30 Oct 2018 06:05:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=7Pmc46jhxwFFwcGbq0lzrj3UDsVFZXgLeDqDIb9QDfI=; b=uHUtK1hfI1T0DLpvYUN9/AzHsa4bo3fRtZf+qs9QfVwaUbjkCTR84ZRfEg5+lZ/M0A 54CU9YWlVGKuD+D7TFsYtuTXI6gZX34MmFiWSxkRptYuUpGyp0mGxFVtST1vk5/+J//N 8L5eoCHL/FphXu/gRmtJimio7w5gxWBa/FEEETUPFLyooy4Mip632pyUNwOsTIthEnSo 2j8AV7DH10xJ/AJl6/YlQ0jn83aMGFIvy0snWVA1e4L516FmbHgFviNyIGFGQ7dZbus6 zrojO1BrjPCCyWBXPh18n5E6+vz3RVyaJ+wHvpVcjU2c1KVCf7UeiuC6cX9ksw46Zfd/ gcEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=7Pmc46jhxwFFwcGbq0lzrj3UDsVFZXgLeDqDIb9QDfI=; b=XLpl7DM0u+BXoPcNiDiKGLYj5GykBg0mT4yFLH06vFpe0e3+telpsDy6ilX7SxLgYE 1ardm7I2XXAnONC95ErEgBUyfd6zg/834ey+L75iraoDv2u4j43eghNLj7BqFJhm5CZE 7/zyrjCr+khXWedVBirs8i5cAzWcnJvjNdbeIx8kfnTwMcQG8faEaF8Xgq0hJTPebliM vTbtF/lG69I5bOooeEpZhpmw5gGevZ3zY3qaxLle5jXduA0PXFpL64ATYfCM9/oGjRWu 6pn+xLBNiWKsTmwcXWY37Y9sY0ciToDS4XNsiOhkXFySNM6V3T45ySde2r95DIqmvsC5 WJng==
X-Gm-Message-State: AGRZ1gKyalbGOBprqbNI/D11WMHnAQ5fk+2pyb7I67QRk7puG5V+EvyJ mnFzpHdQPTN0LYFL6d6ofYX/KQ==
X-Google-Smtp-Source: AJdET5dCZ3Qn+PwK3nvPi2wx2b2jfBvAF2w2s7UU6DYJ42dP79TsiW+QB3i2AOOVAygve/IMw4A/Bw==
X-Received: by 2002:a0c:b0c3:: with SMTP id p3mr16605456qvc.174.1540904731877;  Tue, 30 Oct 2018 06:05:31 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id n68-v6sm13438084qka.36.2018.10.30.06.05.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Oct 2018 06:05:31 -0700 (PDT)
Date: Tue, 30 Oct 2018 09:05:24 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: QUIC WG <quic@ietf.org>
Subject: Re: Frame changes landing soon
Message-ID: <20181030130524.GA10485@ubuntu-dmitri>
Mail-Followup-To: Martin Thomson <martin.thomson@gmail.com>, QUIC WG <quic@ietf.org>
References: <CABkgnnXwmvCGcukYnQHU4sfAZFR24RT31O+BVqqnkZwB3Cp_Kw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABkgnnXwmvCGcukYnQHU4sfAZFR24RT31O+BVqqnkZwB3Cp_Kw@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/NsmT-AHoa5QnpufrNzxfoCy3K-g>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 13:05:36 -0000

On Tue, Oct 30, 2018 at 12:07:46PM +1100, Martin Thomson wrote:
> My current plan is to merge both of these in the next 24 hours.  That
> will allow me to renumber frame types so that they start to make more
> sense..

What is the reason for renumbering the frames?  (Not that I am
against it -- simply curious.)  Is it to make the types easier to
remember in order to facilitate eyeballing hex dumps?  Or is there
some other goal?

  - Dmitri.

> If you are interested in what that will look like, see
> https://docs.google.com/spreadsheets/d/1G73qp-GBhXGyKEsZBudzWJY85FSa5txT4MxtVC5ajiE/edit?usp=sharing
> 


From nobody Tue Oct 30 06:37:13 2018
Return-Path: <ietf@trammell.ch>
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 34CF112D4F2 for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 06:37:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 KB6d06U6t5h2 for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 06:37:09 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [IPv6:2001:8e0:40:325::36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FE6F12D4EC for <quic@ietf.org>; Tue, 30 Oct 2018 06:37:09 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 2B378341B50; Tue, 30 Oct 2018 14:37:07 +0100 (CET)
X-Iway-Path: 0
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/20439.7701);  Tue, 30 Oct 2018 14:37:06 +0100 (CET)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Tue, 30 Oct 2018 14:37:04 +0100 (CET)
Received: from [195.176.111.10] (account ietf@trammell.ch HELO public-docking-cx-1504.ethz.ch) by switchplus-mail.ch (CommuniGate Pro SMTP 6.2.8) with ESMTPSA id 72111180; Tue, 30 Oct 2018 14:37:04 +0100
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <2F288470-1659-4A8F-92BD-5640998917D8@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_3F577C1D-9F2A-4DA3-90E8-C1515E99B19E"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: Structuring the BKK spin bit discussion
Date: Tue, 30 Oct 2018 14:37:04 +0100
In-Reply-To: <HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
Cc: "mikkelfj@gmail.com" <mikkelfj@gmail.com>, "huitema@huitema.net" <huitema@huitema.net>, Marcus Ihlar <marcus.ihlar@ericsson.com>
To: "quic@ietf.org" <quic@ietf.org>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com> <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch> <a088c411-1acc-8b0f-fc1b-8c79ce6f1cd7@huitema.net> <DB6PR10MB1766E6B29792BB4401FF38F0ACCC0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ExHWFjJcggwv9bcwzzjVEVoOLA0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 13:37:12 -0000

--Apple-Mail=_3F577C1D-9F2A-4DA3-90E8-C1515E99B19E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

hi Marcus, all,

So let me step back a bit and suggest a starting point (borrowing =
heavily from MT in an offlist discussion) for discussing what we want to =
do in BKK. (Or rather, I should say, let me suggest a starting point for =
y'all to discuss, because I doubt I'll be in a position to join remotely =
at 03:00 next Wednesday local time. Have fun! :)

There seem to be three broad options we've discussed to date:


- No spin bit. Grease it if we can't use it for something else.

- "Discretionary" spin: reserve the bit for spinning, implementations =
MAY/SHOULD/whatever spin. MUST doesn't make any sense here, since =
there's no impact on end-to-end interop or the end-to-end properties the =
protocol guarantees.

- "Negotiated" spin: reserve the bit for spinning, define two versions, =
one in which the endpoints MUST NOT spin the bit, one in which the =
endpoints MUST spin the bit. This has the nice property that negotiation =
of the spin bit is an actual exercise of the version negotiation =
mechanism, which will keep it flexible for future use better that =
greasing alone. (This was discussed in a thread after the NYC interim, =
but there's no text for it in spin-exp. I'd be happy to try and bang out =
a PR for it if that'd make it easier for people to understand/discuss in =
BKK.)

Beyond this, there seem to be a few other qualities we want, and the =
details matter for these. The most important quality discussed is the =
maintenance of an anonymity set of non-spinning flows so that an =
endpoint that does not want to spin will not immediately stick out. So =
we can define some parameters that meet those qualities for both of the =
discretionary and negotiated variants. Let me propose the following =
values for these parameters, as a starting point for discussion in BKK:


(1) No spin bit: no parameters. If the bit is reserved, it must be =
greased. (I'd submit that experimental use of the spin bit is a good =
form of greasing, so an implementation can offer discretionary spin if =
it likes, but without large-scale implementation, such experimental use =
is seen on a tiny minority of traffic and becomes a wholly academic =
exercise.)


(2) Discretionary spin bit: here we want to determine compliance levels =
and participation probability. I'd suggest:

- client SHOULD implement and server SHOULD implement (I acknowledge =
this is a personal preference; I suggest it because I think it will =
drive deployment better than MAY/SHOULD or MAY/MAY).

- both client and server SHOULD allow the application and/or user/system =
configuration to force a given connection or set of connections to spin =
(for targeted diagnostic purposes) or not to spin. (This is a REALLY =
SHOULD, only because MUST on the interface doesn't make a lot of sense.)

- in the absence of such configuration, both client and server SHOULD =
independently decide to spin the bit on a given connection with a set =
probability. I'd suggest probabilities at each endpoint of 7/8, so 3/4 =
of flows between implementing endpoints will expose RTT. This is a wild =
guess at a good starting point, though, picked to cause a large =
proportion of flows to spin even if only a small number of large =
implementations decide to implement; it is possible to set the =
recommendation smaller if it looks like the majority of implementations =
will spin. These proportions SHOULD be user/system/application =
configurable.

- when not spinning, each of the client and server should randomly =
select a value for the spin bit for each new CID the duration of the =
connection, and send that value on every packet with that CID.

This will ensure that even in a future with perfect deployment, the set =
of flows that aren't spinning because of deliberate configuration at any =
given time will have a large enough anonymity set to hide in. It also =
makes the job of recognizing non-spinning flows easy. In any case, it is =
important that all non-spinning flows (due to non-implementation, random =
choice, or deliberate configuration) non-spin in the same way.


(3) Negotiated spin bit: same question. I'd suggest that the starting =
points be chosen to result in the same proportion of spinning bits as in =
discretionary case (2) above, so:

- client SHOULD implement and server SHOULD implement (same comment as =
above)

- both client and server SHOULD allow the application and/or user/system =
configuration to force a given connection to offer/accept to spin, or to =
not offer/refuse to spin.

- in the absence of such configuration, the client SHOULD offer to spin =
(request the spin version of the protocol) with a set probability, and =
the server SHOULD accept an offer to spin with a set probability. =
Suggest 7/8 as above, for target probability 3/4, same caveats.

- when negotiated, both endpoints MUST spin the bit (as described in =
quic-spin-exp). If one endpoint detects the other is not spinning, it =
MUST terminate the connection, as this may indicate an error in the =
version negotiation mechanism itself.

- when not negotiated, each of the client and server should randomly =
select a value for the spin bit for each new CID the duration of the =
connection, and send that value on every packet with that CID.

The additional properties negotiated spin has with respect to =
discretionary spin are that it is a real exercise of the version =
negotiation mechanism, and that it provides an explicit signal to =
on-path devices that a given connection will spin.


I suggest we try to start from these three points, separating the =
question of which pattern (none, discretionary, negotiated) we prefer, =
from the questions about the particular parameters applied thereto. Key =
is that we can tweak the parameters for either pattern to arrive at a =
given deployment curve and proportion of spinning bits in the network.

Thanks, cheers,

Brian



P.S.: I'm not ignoring the "hold two other bits out for measurement =
experimentation" question, but I consider it to be an orthogonal =
question to these; I think it's worth discussing, but we can treat it =
separately, so we should. In any case I think the work you (Marcus) have =
done has shown that relatively simple heuristics at the measurement =
point deliver most of the benefit in terms of measurement fidelity in =
the presence of loss and reordering that the VEC can for realistic loss =
and reordering rates, for two fewer bits per packet. So the spin bit is =
worth doing on its own.





> On 30 Oct 2018, at 12:55, Marcus Ihlar <marcus.ihlar@ericsson.com> =
wrote:
>=20
> Making it more difficult to differentiate explicit opt-out from random =
opt-out is likely useful even if it doesn=E2=80=99t help in the =
particular Netflix case.
> Furthermore, just like Brian points out it is necessary to grease the =
bit if we want to change the bit semantics later on.
> I think the proposal has low enough complexity and potential benefits =
to be worthwhile.
>=20
> From: QUIC <quic-bounces@ietf.org> On Behalf Of Mikkel Fahn=C3=B8e =
J=C3=B8rgensen
> Sent: den 30 oktober 2018 08:01
> To: Christian Huitema <huitema@huitema.net>; quic@ietf.org
> Subject: Re: Structuring the BKK spin bit discussion
>=20
> In the Netflix case it just takes 16 connections by the same user, or =
less when multiple users originate from the sane IP range.. Is it really =
practical (and thus worthwhile) to hide probabilistically as in Huitemas =
PR?
>=20
> From: QUIC <quic-bounces@ietf.org> on behalf of Christian Huitema =
<huitema@huitema.net>
> Sent: Tuesday, October 30, 2018 5:27:47 AM
> To: quic@ietf.org
> Subject: Re: Structuring the BKK spin bit discussion
>=20
> On 10/29/2018 3:58 PM, Brian Trammell (IETF) wrote:
>=20
> hi Martin, Christian, all,
>=20
> On 29 Oct 2018, at 23:29, Martin Thomson <martin.thomson@gmail.com> =
wrote:
>=20
> On Tue, Oct 30, 2018 at 3:54 AM Christian Huitema =
<huitema@huitema.net> wrote:
> I think the strongest objection to the spin bit was put up by Marten =
during the last interim: measuring the RTT with the spin bit discloses =
the use of hidden path segments like VPN. This issue was not discussed =
during the privacy analysis.
> I had assumed that was part of the analysis and it was covered by the
> assumption that spinning could be disabled
> +1. Probabilistically disabling spinning, which seems necessary if we =
want some grease to help us reserve the right to change the semantics of =
the bit at the spin bit's location in the wire image, should ensure that =
endpoints that want to disable spinning for their own reasons will have =
a large anonymity set to hide in, even in a future with perfect =
implementation and deployment of the spin bit.
>=20
> I opened PR https://github.com/quicwg/base-drafts/pull/1931 to discuss =
this.
>=20
> -- Christian Huitema


--Apple-Mail=_3F577C1D-9F2A-4DA3-90E8-C1515E99B19E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAlvYXoAACgkQihK3vwvq
RqOlUw/+NU4tYYawYbKMA9pey5rgyLRQBphYwHYoBJ0EkHyYt11i55J10N9EyL5M
NxQqEaoiZwxyRupSqAS+J7H9C/+wTk00XL3tCVtsGiWTFzYoHJRLoq6Mlw0l8SnP
uuLescNj5cHFMGvBMJ0TbM414cJKvSZa3w4CJAEYstFgXr/C2H7bviLeFSJPUns7
LaAPkkFanGG0d99DwM2K6aM7HHOye9xHgjwnGx9vVAI5Kpl9KucnfkrCebCc3+hV
Tk/N6CTj5g/DF6tWBEIaeVCmKrBXwfhCQ8BBIuOEKm12tgiDC8Tqja1youU89P2u
B1PxyfajX5z+jpIWOE6SUezFWrgE8CcW/SnyKU8/y3EZEO7jMZDEsJ64ukDu81Ru
cJikA/Iyg0tfAnKm7vlaJeTiA1V8e4fZn6BuNZ+SOfxca/oYTB8jjduKDkVW0u1e
+1GfM8BIciF3KaKOTVVWGkWrgl0A+wsZIjunJiQPoHaHQY/HB+bkDcMzPjvlpswA
754jqLB0VuG0aSf/oQNShEddejfAYWLEbeg7Y8aKtvMzGjfb4+ux2gSXSkcbgcP9
TkTL1ZENEPJMISL2K5A47fRxGD2q3VUCbmAAbXmKL6YGBEzc+a8OdIH5SwlnhSVi
f2rqrFnaTNr7s2LLjuu8Yww7rRJBsTlMLnmaHnU6dc2iwSPxxgg=
=fESP
-----END PGP SIGNATURE-----

--Apple-Mail=_3F577C1D-9F2A-4DA3-90E8-C1515E99B19E--


From nobody Tue Oct 30 06:56:17 2018
Return-Path: <ianswett@google.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 EB42A128CF2 for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 06:56:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.501
X-Spam-Level: 
X-Spam-Status: No, score=-17.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 yhDG1XIeGQHk for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 06:56:14 -0700 (PDT)
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (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 F1283127AC2 for <quic@ietf.org>; Tue, 30 Oct 2018 06:56:13 -0700 (PDT)
Received: by mail-wr1-x42f.google.com with SMTP id g9-v6so12702704wrq.4 for <quic@ietf.org>; Tue, 30 Oct 2018 06:56:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0HdkZ7F8yxj+e7URcXVRs89VuuKtcJUnr7QGWzP/e0A=; b=ctFCJyZlYEc43C/upGCfvW1JqFI7fl+e/4bclflbwy1u4lbqo0YNnw0qTuhVg4N+rV CS3IWeKwYUT+HrV4IwtqjGR2MgyS4xHRpg0szB2tzgwRG998InY3wGWqjzgtLQ4/7lPi 8ckyM40+2i/bPSOFl8i6HgWraWcuYUs7pLNbEa2q4x/tAoJ47dNlafe5ODKNF3ocT6Dd Dl1AMmHLGv/BRVQ2eDg0RAL7FzpfawcU7BVfPWljf+ljCOia/WIHWtjGqTA1cZ1hTFMG 6aJwbFVRRCZDrkvgxat9RdvOs39QZvs9FlRbtHgso4t5+ZO7yiSs9Bms7Q2gOjs7Hifj aBNQ==
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=0HdkZ7F8yxj+e7URcXVRs89VuuKtcJUnr7QGWzP/e0A=; b=mIbbwjg7pVZrY1jsfSgMH11YdOBiutnNPThh6t1n0tTo0KWh3s9deAljkM0tqqlaV9 D720GA8lZW7TmciOcxEDJ9CfQW5BjwlIeGeO7Ji/Zj80kiSNo/OKG7B2Vp5RZpimfpfg mPubuCWfP4zAyiUJ1skSZQ9YvnRI3SK8Y7mazbkVV1KPPscE9eQM6lfBI5AOgypxX4A2 g4Gygu1MR0MM4QvB2hHCTVN8cGTBpyyL2S8u0Xej/TtcJNb6F3xJARwB/lz6P5mw1vhp FSIhdv+V06Tu/e4B94JWmOoEpTlUEylII+wfemvBXfjlPxu1l6+ysrdIil/6sQLFhUcR DAeA==
X-Gm-Message-State: AGRZ1gKevFMviQEehctGKvNo+VGEWee4YWU6LeJrHXOh9fq/a4f70sgr 8FTdFLrCihn0ITj2p2yvZDi9oGnKESfPBjEqFY7C0A==
X-Google-Smtp-Source: AJdET5daf+VieHU98UzyvbR7uDOkaRYxuWRVxFmkr13jhyhVZ5teOSrN5nr3F0rlfg5lEvpx1g977hNhsMKtg8cGDOw=
X-Received: by 2002:a05:6000:1009:: with SMTP id a9mr3571012wrx.271.1540907772304;  Tue, 30 Oct 2018 06:56:12 -0700 (PDT)
MIME-Version: 1.0
References: <578BB4EC-421E-4B21-AA14-B545A41754C8@mnot.net> <20181030052133.GA29963@1wt.eu>
In-Reply-To: <20181030052133.GA29963@1wt.eu>
From: Ian Swett <ianswett@google.com>
Date: Tue, 30 Oct 2018 09:56:00 -0400
Message-ID: <CAKcm_gNbQyvAOVsg7wCj+M83Thsj+=KJD0QGLcq42-RAwhTf=g@mail.gmail.com>
Subject: Re: Identifying our deliverables
To: Willy Tarreau <w@1wt.eu>
Cc: Mark Nottingham <mnot@mnot.net>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000066c0950579728c61"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/rtIoBkMO-FGpqEJMrMt0T7E9Rog>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 13:56:16 -0000

--00000000000066c0950579728c61
Content-Type: text/plain; charset="UTF-8"

>From a completely practical perspective, I support this because I can't
tell you how many times I've had to explain the difference between the HTTP
over QUIC mapping and QUIC the transport.

And moving the HTTP over QUIC and QPACK documents to the HTTP working group
seems like the right thing to do.

On Tue, Oct 30, 2018 at 1:21 AM Willy Tarreau <w@1wt.eu> wrote:

> On Sun, Oct 28, 2018 at 11:30:55AM +1100, Mark Nottingham wrote:
> > To address this, I'd like to suggest that -- after coordination with the
> HTTP
> > WG -- we rename our the HTTP document to "HTTP/3", and using the final
> ALPN
> > token "h3". Doing so clearly identifies it as another binding of HTTP
> > semantics to the wire protocol -- just as HTTP/2 did -- so people
> understand
> > its separation from QUIC.
>
> FWIW I always thought that HTTP/3 should be its final naming -- just like
> SPDY
> became HTTP/2 -- for various reasons, one of them being encouraging
> adoption
> by the protocol being presented as the natural upgrade to the previous ones
> and not a competitor that's been there for some time and suddenly comes as
> an RFC.
>
> H1 with 723x, then H2 with 754x have shown that it's not a problem to cover
> multiple areas with a common name and that the protocol itself is in fact a
> family of protocols and mechanisms. So QPACK will naturally fall under H3
> just like HPACK naturally belongs to H2.
>
> Just my two cents,
> Willy
>
>

--00000000000066c0950579728c61
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">From a completely practical perspective, I support this be=
cause I can&#39;t tell you how many times I&#39;ve had to explain the diffe=
rence between the HTTP over QUIC mapping and QUIC the transport.<div><br></=
div><div>And moving the HTTP over QUIC and QPACK documents to the HTTP work=
ing group seems like the right thing to do.</div></div><br><div class=3D"gm=
ail_quote"><div dir=3D"ltr">On Tue, Oct 30, 2018 at 1:21 AM Willy Tarreau &=
lt;<a href=3D"mailto:w@1wt.eu">w@1wt.eu</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">On Sun, Oct 28, 2018 at 11:30:55AM +1100, Mark Nottingh=
am wrote:<br>
&gt; To address this, I&#39;d like to suggest that -- after coordination wi=
th the HTTP<br>
&gt; WG -- we rename our the HTTP document to &quot;HTTP/3&quot;, and using=
 the final ALPN<br>
&gt; token &quot;h3&quot;. Doing so clearly identifies it as another bindin=
g of HTTP<br>
&gt; semantics to the wire protocol -- just as HTTP/2 did -- so people unde=
rstand<br>
&gt; its separation from QUIC.<br>
<br>
FWIW I always thought that HTTP/3 should be its final naming -- just like S=
PDY<br>
became HTTP/2 -- for various reasons, one of them being encouraging adoptio=
n<br>
by the protocol being presented as the natural upgrade to the previous ones=
<br>
and not a competitor that&#39;s been there for some time and suddenly comes=
 as<br>
an RFC.<br>
<br>
H1 with 723x, then H2 with 754x have shown that it&#39;s not a problem to c=
over<br>
multiple areas with a common name and that the protocol itself is in fact a=
<br>
family of protocols and mechanisms. So QPACK will naturally fall under H3<b=
r>
just like HPACK naturally belongs to H2.<br>
<br>
Just my two cents,<br>
Willy<br>
<br>
</blockquote></div>

--00000000000066c0950579728c61--


From nobody Tue Oct 30 07:25:49 2018
Return-Path: <lucaspardue.24.7@gmail.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 D6EBC12D4EC for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 07:25:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 xLQnUToIjXBz for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 07:25:46 -0700 (PDT)
Received: from mail-ua1-x92f.google.com (mail-ua1-x92f.google.com [IPv6:2607:f8b0:4864:20::92f]) (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 7D2271293FB for <quic@ietf.org>; Tue, 30 Oct 2018 07:25:46 -0700 (PDT)
Received: by mail-ua1-x92f.google.com with SMTP id d8so3541912ual.2 for <quic@ietf.org>; Tue, 30 Oct 2018 07:25:46 -0700 (PDT)
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=ZuorgphoJjkU2+BYPMuw2pqqMaUU3GnBqPVTh3kkf0g=; b=tHIRJbr/14Mx9tq0V4zsKdBgbqxvIh6LA4mxDvCcr8NN5ylQhIIvvxVgCCrIDleXrb CMHWcyVsNVof5LWpJMju1NZTFI0CUhNOoz+FAsedHhWLjTfTDUI58yLP4NTBXjvdISU7 qVKqe3PuWiTWHFebuAitvk9Gjn+GbY3FzM3u8V2GkVpQIpvQWkBoKdMilVOK7sOl+xQF hDntgnOLlvDZb2C46k4BSj2Eqsnp/T5kgGSzIv6+AduotoYAzgVdfyHjzcKqqTz8iqNX anbqiRw/8Gq/v91EO8ynMitGB4PPxHW8oXR2+ZelDNOdn8Cq5qG4BicRPq8txmgoMqYI /6rA==
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=ZuorgphoJjkU2+BYPMuw2pqqMaUU3GnBqPVTh3kkf0g=; b=hPuY40kxHoPO52hp9myaapoxKg2YJBXs6IC5ixN2tBv3XiYfSabNGJkx7Sfy+DtLHH wFAmf+Q3PnlUyt24TUldyShailFFMqw3Rrp7pK92Ka9p+URr7yyapzHrIDVPgbP4MXLj kIQtL62dqNCf/GZU+bWvj5FazcShnzPSq7H8ktZmlQSCP5Js5ChX2rdqcqZaxPQs1fQJ wl1ON8ytixPUiVC5f2ha37VfLKNuN8w0ojDlJy1lYG4wRsA4psrQygFCBq1au9TiFmIp s/U1GkosR85YKMF5w6miy9SCbajxE8CepDYxJzqbmoJpgpePEOV8FD3AaU8ahJHtmBVQ 8anw==
X-Gm-Message-State: AGRZ1gLxodif9Hq6mPDNkymmVhpVsnwWcNuVj7h9aqJ+DtXQCyV4OqeH xHxzy7LJG3l/b16mFa0Pl2axNjT0wgI3kYgXutg=
X-Google-Smtp-Source: AJdET5cYoyTFhVx+A+THyciA/PqaiqtOJ6ClI6MoJss1OLQii76bEV7TyG3bR/NTFBLAUwy49mhHtmWBoQlWmxGPsl0=
X-Received: by 2002:ab0:4327:: with SMTP id k36mr8639941uak.46.1540909545215;  Tue, 30 Oct 2018 07:25:45 -0700 (PDT)
MIME-Version: 1.0
References: <578BB4EC-421E-4B21-AA14-B545A41754C8@mnot.net> <20181030052133.GA29963@1wt.eu> <CAKcm_gNbQyvAOVsg7wCj+M83Thsj+=KJD0QGLcq42-RAwhTf=g@mail.gmail.com>
In-Reply-To: <CAKcm_gNbQyvAOVsg7wCj+M83Thsj+=KJD0QGLcq42-RAwhTf=g@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Tue, 30 Oct 2018 14:25:32 +0000
Message-ID: <CALGR9oZSj0GSa=3EVFt27=DLahqJj+qS0nUSfqFNf+NWnEbsLg@mail.gmail.com>
Subject: Re: Identifying our deliverables
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: Willy Tarreau <w@1wt.eu>, Mark Nottingham <mnot@mnot.net>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000012db31057972f68f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/tsEMTMNVIlKcLGvrXOP5gpLoxNU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 14:25:48 -0000

--00000000000012db31057972f68f
Content-Type: text/plain; charset="UTF-8"

I echo Ian's thoughts, "HTTP over QUIC" doesn't work well as a term in
practice.

I support this change, using an incremental number is logical, and is
compatible with the ecosystem that expects an HTTP version number.



On Tue, 30 Oct 2018, 13:56 Ian Swett, <ianswett=40google.com@dmarc.ietf.org>
wrote:

> From a completely practical perspective, I support this because I can't
> tell you how many times I've had to explain the difference between the HTTP
> over QUIC mapping and QUIC the transport.
>
> And moving the HTTP over QUIC and QPACK documents to the HTTP working
> group seems like the right thing to do.
>
> On Tue, Oct 30, 2018 at 1:21 AM Willy Tarreau <w@1wt.eu> wrote:
>
>> On Sun, Oct 28, 2018 at 11:30:55AM +1100, Mark Nottingham wrote:
>> > To address this, I'd like to suggest that -- after coordination with
>> the HTTP
>> > WG -- we rename our the HTTP document to "HTTP/3", and using the final
>> ALPN
>> > token "h3". Doing so clearly identifies it as another binding of HTTP
>> > semantics to the wire protocol -- just as HTTP/2 did -- so people
>> understand
>> > its separation from QUIC.
>>
>> FWIW I always thought that HTTP/3 should be its final naming -- just like
>> SPDY
>> became HTTP/2 -- for various reasons, one of them being encouraging
>> adoption
>> by the protocol being presented as the natural upgrade to the previous
>> ones
>> and not a competitor that's been there for some time and suddenly comes as
>> an RFC.
>>
>> H1 with 723x, then H2 with 754x have shown that it's not a problem to
>> cover
>> multiple areas with a common name and that the protocol itself is in fact
>> a
>> family of protocols and mechanisms. So QPACK will naturally fall under H3
>> just like HPACK naturally belongs to H2.
>>
>> Just my two cents,
>> Willy
>>
>>

--00000000000012db31057972f68f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div dir=3D"auto">I echo Ian&#39;s thoughts,=C2=A0<span s=
tyle=3D"font-family:sans-serif">&quot;HTTP over QUIC&quot; doesn&#39;t work=
 well as a term in practice.=C2=A0</span></div><div dir=3D"auto"><br></div>=
I support this change, using an incremental number is logical, and is compa=
tible with the ecosystem that expects an HTTP version number.=C2=A0<div dir=
=3D"auto"><br></div><div dir=3D"auto"><br></div></div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr">On Tue, 30 Oct 2018, 13:56 Ian Swett, &lt;ianswe=
tt=3D<a href=3D"mailto:40google.com@dmarc.ietf.org">40google.com@dmarc.ietf=
.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr=
">From a completely practical perspective, I support this because I can&#39=
;t tell you how many times I&#39;ve had to explain the difference between t=
he HTTP over QUIC mapping and QUIC the transport.<div><br></div><div>And mo=
ving the HTTP over QUIC and QPACK documents to the HTTP working group seems=
 like the right thing to do.</div></div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr">On Tue, Oct 30, 2018 at 1:21 AM Willy Tarreau &lt;<a href=3D"m=
ailto:w@1wt.eu" target=3D"_blank" rel=3D"noreferrer">w@1wt.eu</a>&gt; wrote=
:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">On Sun, Oct 28, 2018 at 11:30:55A=
M +1100, Mark Nottingham wrote:<br>
&gt; To address this, I&#39;d like to suggest that -- after coordination wi=
th the HTTP<br>
&gt; WG -- we rename our the HTTP document to &quot;HTTP/3&quot;, and using=
 the final ALPN<br>
&gt; token &quot;h3&quot;. Doing so clearly identifies it as another bindin=
g of HTTP<br>
&gt; semantics to the wire protocol -- just as HTTP/2 did -- so people unde=
rstand<br>
&gt; its separation from QUIC.<br>
<br>
FWIW I always thought that HTTP/3 should be its final naming -- just like S=
PDY<br>
became HTTP/2 -- for various reasons, one of them being encouraging adoptio=
n<br>
by the protocol being presented as the natural upgrade to the previous ones=
<br>
and not a competitor that&#39;s been there for some time and suddenly comes=
 as<br>
an RFC.<br>
<br>
H1 with 723x, then H2 with 754x have shown that it&#39;s not a problem to c=
over<br>
multiple areas with a common name and that the protocol itself is in fact a=
<br>
family of protocols and mechanisms. So QPACK will naturally fall under H3<b=
r>
just like HPACK naturally belongs to H2.<br>
<br>
Just my two cents,<br>
Willy<br>
<br>
</blockquote></div>
</blockquote></div>

--00000000000012db31057972f68f--


From nobody Tue Oct 30 07:29:00 2018
Return-Path: <mikkelfj@gmail.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 23287130DD1 for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 07:28:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level: 
X-Spam-Status: No, score=-0.998 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 Uf6RUySOz4pq for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 07:28:45 -0700 (PDT)
Received: from mail-it1-x130.google.com (mail-it1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (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 D6730129C6A for <quic@ietf.org>; Tue, 30 Oct 2018 07:28:44 -0700 (PDT)
Received: by mail-it1-x130.google.com with SMTP id e74-v6so13893184ita.2 for <quic@ietf.org>; Tue, 30 Oct 2018 07:28:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=JKO8SVpcZc65vm8Bx+yA+an6VD9WPoKzlToc+adja0Q=; b=fYJvj59JxnTrhGKVUId2vQ2YnHnKJjb/iJRmcgL2JNh7pGbft9QfnPmFJdrxncH7cm yOS1FpFiWP1xakrh1ezgxhF+6DFpAySGwRd9t7PwbeXmUe6GJOEkL8jd3gkyPdRhpzIH ZY7jKrEg33GMqo8duejrwhMEcD2qGFLPgeUow9O+b0i/X+d3rQ3iVPRbOYB5te3MkjbX mpxhCF+dDuP9azZs8bxB1/KxoofqglX6d3hhUeHOngReexlB99dZ3rfuf9ptsDOBQXdN bZopUCBez/JNtxCOkypn4LWlFDsLdAR/wvVLlQLHm6jmq+JVL/79GJnXWoYy2c/4ozXM 077A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=JKO8SVpcZc65vm8Bx+yA+an6VD9WPoKzlToc+adja0Q=; b=fdOfHs9SjEmgpPrkf8HeS5KCo8jGOr7/omHoej7o5QgkBkFWsKVaotV5b4DhUgFRo9 rQZXUt3QOqKc3CpnuTihVfDWu9XdjnzAZI0fYjJF4DbbA+JwTwCVkyLQhNWTbQnmA+wd WzbQBLrm0QaF2toRHXr8Ge/SymslzvZX++JrJE80ufGvWR2k60Gu+VJfsOEvqbJPHtHw eU/QvuBwz3+/Oa8H7vFeakHjpyTxWcPdBHy7B6dBWmhYn2Wm7idNZuIFlcJrkpzwbjNJ 1ULE/SRbQgv4yjHMIjJPagV5ZmCrEklJusNm0hpwgpegVnJ0b8BX+2cFoNORdGoz+gQZ 6FGg==
X-Gm-Message-State: AGRZ1gI8pnnBgkPy6JyW2SkAMl2CsUnMCOINH2/kGSzvmkU6F8j6Vh0K Y2ymBm8+fcjenZHG0luqCrshPaLIhK/rtmsFss0=
X-Google-Smtp-Source: AJdET5eYM8S6FAQXeeU6vnwU/gsnOJHNLo6mZbcKkC3zBQZ0ZsV0Qe/v0bWhK1+clNtD0XnfcU1Cx+5ceSjn3NiEJno=
X-Received: by 2002:a24:cd02:: with SMTP id l2-v6mr1482668itg.70.1540909724051;  Tue, 30 Oct 2018 07:28:44 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 30 Oct 2018 07:28:43 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CALGR9oZSj0GSa=3EVFt27=DLahqJj+qS0nUSfqFNf+NWnEbsLg@mail.gmail.com>
References: <578BB4EC-421E-4B21-AA14-B545A41754C8@mnot.net> <20181030052133.GA29963@1wt.eu> <CAKcm_gNbQyvAOVsg7wCj+M83Thsj+=KJD0QGLcq42-RAwhTf=g@mail.gmail.com> <CALGR9oZSj0GSa=3EVFt27=DLahqJj+qS0nUSfqFNf+NWnEbsLg@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Tue, 30 Oct 2018 07:28:43 -0700
Message-ID: <CAN1APdeKSWYFgtiKT-=eQ0=o+Mm6pyFeY00trd+SMLKNdVofxw@mail.gmail.com>
Subject: Re: Identifying our deliverables
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>,  Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>, Willy Tarreau <w@1wt.eu>, Mark Nottingham <mnot@mnot.net>
Content-Type: multipart/alternative; boundary="000000000000bbaf3505797300e7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/8dCbiwS5l__exjD0fj_vtt9G_m4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 14:28:49 -0000

--000000000000bbaf3505797300e7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Recent edits in transport also use terms such as =E2=80=9CThis frame is onl=
y used
in the QUIC layer=E2=80=9D which is slightly confusing when QUIC/HTTP is al=
so a
(higher) level QUIC layer while =E2=80=9CQUIC layer=E2=80=9D refers to the =
transport layer
only, implicitly.

Mikkel


On 30 October 2018 at 15.26.19, Lucas Pardue (lucaspardue.24.7@gmail.com)
wrote:

I echo Ian's thoughts, "HTTP over QUIC" doesn't work well as a term in
practice.

I support this change, using an incremental number is logical, and is
compatible with the ecosystem that expects an HTTP version number.



On Tue, 30 Oct 2018, 13:56 Ian Swett, <ianswett=3D40google.com@dmarc.ietf..=
org
<40google.com@dmarc.ietf.org>> wrote:

> From a completely practical perspective, I support this because I can't
> tell you how many times I've had to explain the difference between the HT=
TP
> over QUIC mapping and QUIC the transport.
>
> And moving the HTTP over QUIC and QPACK documents to the HTTP working
> group seems like the right thing to do.
>
> On Tue, Oct 30, 2018 at 1:21 AM Willy Tarreau <w@1wt.eu> wrote:
>
>> On Sun, Oct 28, 2018 at 11:30:55AM +1100, Mark Nottingham wrote:
>> > To address this, I'd like to suggest that -- after coordination with
>> the HTTP
>> > WG -- we rename our the HTTP document to "HTTP/3", and using the final
>> ALPN
>> > token "h3". Doing so clearly identifies it as another binding of HTTP
>> > semantics to the wire protocol -- just as HTTP/2 did -- so people
>> understand
>> > its separation from QUIC.
>>
>> FWIW I always thought that HTTP/3 should be its final naming -- just lik=
e
>> SPDY
>> became HTTP/2 -- for various reasons, one of them being encouraging
>> adoption
>> by the protocol being presented as the natural upgrade to the previous
>> ones
>> and not a competitor that's been there for some time and suddenly comes =
as
>> an RFC.
>>
>> H1 with 723x, then H2 with 754x have shown that it's not a problem to
>> cover
>> multiple areas with a common name and that the protocol itself is in fac=
t
>> a
>> family of protocols and mechanisms. So QPACK will naturally fall under H=
3
>> just like HPACK naturally belongs to H2.
>>
>> Just my two cents,
>> Willy
>>
>>

--000000000000bbaf3505797300e7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Recent edits in tran=
sport also use terms such as =E2=80=9CThis frame is only used in the QUIC l=
ayer=E2=80=9D which is slightly confusing when QUIC/HTTP is also a (higher)=
 level QUIC layer while =E2=80=9CQUIC layer=E2=80=9D refers to the transpor=
t layer only, implicitly.</div><div id=3D"bloop_customfont" style=3D"font-f=
amily:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-=
height:auto"><br></div><div id=3D"bloop_customfont" style=3D"font-family:He=
lvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:a=
uto">Mikkel</div><div id=3D"bloop_customfont" style=3D"font-family:Helvetic=
a,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><=
br></div> <br><p class=3D"airmail_on">On 30 October 2018 at 15.26.19, Lucas=
 Pardue (<a href=3D"mailto:lucaspardue.24.7@gmail.com">lucaspardue.24.7@gma=
il.com</a>) wrote:</p> <blockquote type=3D"cite" class=3D"clean_bq"><span><=
div><div></div><div>


<title></title>


<div dir=3D"auto">
<div dir=3D"auto">I echo Ian&#39;s thoughts,=C2=A0<span style=3D"font-famil=
y:sans-serif">&quot;HTTP over QUIC&quot; doesn&#39;t work well as a
term in practice.=C2=A0</span></div>
<div dir=3D"auto"><br></div>
I support this change, using an incremental number is logical, and
is compatible with the ecosystem that expects an HTTP version
number.=C2=A0
<div dir=3D"auto"><br></div>
<div dir=3D"auto"><br></div>
</div>
<br>
<div class=3D"gmail_quote">
<div dir=3D"ltr">On Tue, 30 Oct 2018, 13:56 Ian Swett,
&lt;ianswett=3D<a href=3D"mailto:40google.com@dmarc.ietf.org">40google.com@=
dmarc.ietf..org</a>&gt;
wrote:<br></div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div dir=3D"ltr">From a completely practical perspective, I support
this because I can&#39;t tell you how many times I&#39;ve had to explain
the difference between the HTTP over QUIC mapping and QUIC the
transport.
<div><br></div>
<div>And moving the HTTP over QUIC and QPACK documents to the HTTP
working group seems like the right thing to do.</div>
</div>
<br>
<div class=3D"gmail_quote">
<div dir=3D"ltr">On Tue, Oct 30, 2018 at 1:21 AM Willy Tarreau
&lt;<a href=3D"mailto:w@1wt.eu" target=3D"_blank" rel=3D"noreferrer">w@1wt.=
eu</a>&gt; wrote:<br></div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On
Sun, Oct 28, 2018 at 11:30:55AM +1100, Mark Nottingham wrote:<br>
&gt; To address this, I&#39;d like to suggest that -- after
coordination with the HTTP<br>
&gt; WG -- we rename our the HTTP document to &quot;HTTP/3&quot;, and using
the final ALPN<br>
&gt; token &quot;h3&quot;. Doing so clearly identifies it as another bindin=
g
of HTTP<br>
&gt; semantics to the wire protocol -- just as HTTP/2 did -- so
people understand<br>
&gt; its separation from QUIC.<br>
<br>
FWIW I always thought that HTTP/3 should be its final naming --
just like SPDY<br>
became HTTP/2 -- for various reasons, one of them being encouraging
adoption<br>
by the protocol being presented as the natural upgrade to the
previous ones<br>
and not a competitor that&#39;s been there for some time and suddenly
comes as<br>
an RFC.<br>
<br>
H1 with 723x, then H2 with 754x have shown that it&#39;s not a problem
to cover<br>
multiple areas with a common name and that the protocol itself is
in fact a<br>
family of protocols and mechanisms. So QPACK will naturally fall
under H3<br>
just like HPACK naturally belongs to H2.<br>
<br>
Just my two cents,<br>
Willy<br>
<br></blockquote>
</div>
</blockquote>
</div>


</div></div></span></blockquote></body></html>

--000000000000bbaf3505797300e7--


From nobody Tue Oct 30 09:36:36 2018
Return-Path: <prvs=48412b72f3=fenix@fb.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 2523E12D4EA for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 09:36:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.172
X-Spam-Level: 
X-Spam-Status: No, score=-1.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, KHOP_DYNAMIC=1.999, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=nSsPfFx0; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=eeFoKJak
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 eqOR3EtzGfnf for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 09:36:33 -0700 (PDT)
Received: from mx0a-00082601.pphosted.com (mx0a-00082601.pphosted.com [67.231.145.42]) (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 3B0EC130D7A for <quic@ietf.org>; Tue, 30 Oct 2018 09:36:33 -0700 (PDT)
Received: from pps.filterd (m0044012.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w9UGZhgj016003; Tue, 30 Oct 2018 09:36:06 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=0DiqcSZs55e8xcnyYYeCuuOo3lyA6f8BFumIVBgMwXA=; b=nSsPfFx0GcZLKmvu4nGIJ2N3agfsCQeUeib9A9E5KQGcdRonUZbbxt+oM+NYgry8Ehu2 LHyTDj1dfi9ybjzGcWWaoABObY8bIygpvyXCZ4fAEc4fmHtueqGmKlQFWYkH5n5w0lYL qlmNp9YXTehjGNz4FAqttucba070mv1v9H4= 
Received: from mail.thefacebook.com ([199.201.64.23]) by mx0a-00082601.pphosted.com with ESMTP id 2nereeghwj-3 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 30 Oct 2018 09:36:06 -0700
Received: from prn-hub01.TheFacebook.com (2620:10d:c081:35::125) by prn-hub01.TheFacebook.com (2620:10d:c081:35::125) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1531.3; Tue, 30 Oct 2018 09:34:06 -0700
Received: from PRN-CHUB02.TheFacebook.com (2620:10d:c081:35::11) by prn-hub01.TheFacebook.com (2620:10d:c081:35::125) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA) id 15.1.1531.3 via Frontend Transport; Tue, 30 Oct 2018 09:34:06 -0700
Received: from NAM05-CO1-obe.outbound.protection.outlook.com (192.168.54.28) by o365-in.thefacebook.com (192.168.16.12) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 30 Oct 2018 09:34:06 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0DiqcSZs55e8xcnyYYeCuuOo3lyA6f8BFumIVBgMwXA=; b=eeFoKJakRrGIm+hepWhuByVzD+l87PkjYwOj8fnqLYwBAOi5kAlq0FKroww44D8m7ygf+Rwp2jVsiVWwmMMY4YWyPvEP6Z6sfpgjF28u9djuBCMNk4XOlbc4VWNZtx4S8EWBQfxYJfTBbG+YKngUWqVwU6jI3homTW54vQD1fEg=
Received: from BYAPR15MB2312.namprd15.prod.outlook.com (52.135.197.146) by BYAPR15MB2278.namprd15.prod.outlook.com (52.135.197.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1273.26; Tue, 30 Oct 2018 16:34:05 +0000
Received: from BYAPR15MB2312.namprd15.prod.outlook.com ([fe80::11c0:d70e:972b:7d51]) by BYAPR15MB2312.namprd15.prod.outlook.com ([fe80::11c0:d70e:972b:7d51%3]) with mapi id 15.20.1273.027; Tue, 30 Oct 2018 16:34:05 +0000
From: Roberto Peon <fenix@fb.com>
To: =?utf-8?B?TWlra2VsIEZhaG7DuGUgSsO4cmdlbnNlbg==?= <mikkelfj@gmail.com>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Lucas Pardue <lucaspardue.24.7@gmail.com>
CC: Mark Nottingham <mnot@mnot.net>, IETF QUIC WG <quic@ietf.org>, "Willy Tarreau" <w@1wt.eu>
Subject: Re: Identifying our deliverables
Thread-Topic: Identifying our deliverables
Thread-Index: AQHUblWOohbKAxrEIUqtTkvPIZCgaKU3RCyAgACPvACAAAhBAIAAAOOA//+trQA=
Date: Tue, 30 Oct 2018 16:34:04 +0000
Message-ID: <B1357972-7731-4B9E-AA80-A36D4F31306C@fb.com>
References: <578BB4EC-421E-4B21-AA14-B545A41754C8@mnot.net> <20181030052133.GA29963@1wt.eu> <CAKcm_gNbQyvAOVsg7wCj+M83Thsj+=KJD0QGLcq42-RAwhTf=g@mail.gmail.com> <CALGR9oZSj0GSa=3EVFt27=DLahqJj+qS0nUSfqFNf+NWnEbsLg@mail.gmail.com> <CAN1APdeKSWYFgtiKT-=eQ0=o+Mm6pyFeY00trd+SMLKNdVofxw@mail.gmail.com>
In-Reply-To: <CAN1APdeKSWYFgtiKT-=eQ0=o+Mm6pyFeY00trd+SMLKNdVofxw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.12.0.181014
x-originating-ip: [2620:10d:c090:200::6:e9de]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR15MB2278; 20:HMpqBhdo742xJtEVdRs2rO0BPRru/CWlHf/phUBRU0eY/kWbshv3WeAPv4zQ3IbDE1PaiVBH+qzASC1F1wwq0lNBEaq2suFyRPJirxqdHodKu2Stz73zlDk3sdnvdstMGE2nxZbg6wBwON/gTwo0wTxzPj4oEZmUtRiKIHBr82U=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 298fe936-048e-4427-7981-08d63e8581e5
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:BYAPR15MB2278; 
x-ms-traffictypediagnostic: BYAPR15MB2278:
x-microsoft-antispam-prvs: <BYAPR15MB22788BC6AD1B9669E04A5017CDCC0@BYAPR15MB2278.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(85827821059158)(21748063052155)(28532068793085)(190501279198761)(227612066756510);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(3231382)(11241501184)(944501410)(4982022)(52105095)(148016)(149066)(150057)(6041310)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051)(76991095); SRVR:BYAPR15MB2278; BCL:0; PCL:0; RULEID:; SRVR:BYAPR15MB2278; 
x-forefront-prvs: 08417837C5
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(136003)(39860400002)(396003)(366004)(376002)(189003)(199004)(3480700004)(53546011)(54906003)(58126008)(102836004)(8936002)(2900100001)(82746002)(14454004)(110136005)(6436002)(4326008)(2906002)(76176011)(25786009)(36756003)(33656002)(6506007)(53936002)(54896002)(99286004)(39060400002)(6116002)(6486002)(6306002)(6512007)(68736007)(83716004)(236005)(6246003)(71200400001)(71190400001)(316002)(97736004)(478600001)(81156014)(106356001)(66574009)(186003)(105586002)(8676002)(86362001)(5250100002)(476003)(14444005)(486006)(93886005)(7736002)(5660300001)(256004)(446003)(46003)(7116003)(11346002)(81166006)(229853002)(2616005)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR15MB2278; H:BYAPR15MB2312.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: S5x7sHc/h4OPER+C/2uCkxaRs7gPDPsajmK/0UsL3ONieVxkyge0qiUzC0QaGnPzxfGRrZc+SMMlemN4lkdG9je76v7BV99ZW3AQ24fS2U84vvKW9XilbYMROsAeiwMYrw2PfG0qFnBFRF+oDl5Tfp4UQjnkPuYDgGzio1OmX1MxwNIgp8iKtlUvVHY4gow5AxzxRMx03t9B/w5pUI5UKKZz7xQPEE1t0dOTAENpVJYpKRnlr6E/Jc7hkAqLXK7aWSik7GATIqKhCdWWagu73uw4udM8MvpF89K3pN2IKxZyHQOrOUr8FtF5SNlhPK2vVJCAlOJei03tt4tLvGSDytKQS5eAMjbH6d6EgWGdvFU=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_B135797277314B9EAA80A36D4F31306Cfbcom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 298fe936-048e-4427-7981-08d63e8581e5
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Oct 2018 16:34:04.9126 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR15MB2278
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-30_10:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/0o3XjOoSMi26owgZpHTnvBhhZvY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 16:36:35 -0000

--_000_B135797277314B9EAA80A36D4F31306Cfbcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

U2luY2UgdGhlcmUgaXNu4oCZdCBhbnkgcGFydGljdWxhciBuZWVkIHRvIGlkZW50aWZ5IFFVSUMg
dGhlIHRyYW5zcG9ydCAod2l0aG91dCBtZWNoYW5pc21zIHRvIGV4cGxpY2l0bHkgbXVsdGlwbGV4
IG11bHRpcGxlIHByb3RvY29scyksIEkgdGhpbmsgY2FsbGluZyBIVFRQLW9uLVFVSUMgSDMgaXMg
dGhlIHJpZ2h0IG1vdmUuDQpRVUlDIHdpdGhvdXQgYW55dGhpbmcgZWxzZSBpcyBhcyBtZWFuaW5n
bGVzcyBhcyBUQ1Agd2l0aG91dCBhbnl0aGluZyBlbHNlIGZyb20gYSB3aGF0LXRoZS1zZXJ2ZXIt
d2lsbC1zcGVhayBwZXJzcGVjdGl2ZS4NCi09Ug0KDQpGcm9tOiBRVUlDIDxxdWljLWJvdW5jZXNA
aWV0Zi5vcmc+IG9uIGJlaGFsZiBvZiBNaWtrZWwgRmFobsO4ZSBKw7hyZ2Vuc2VuIDxtaWtrZWxm
akBnbWFpbC5jb20+DQpEYXRlOiBUdWVzZGF5LCBPY3RvYmVyIDMwLCAyMDE4IGF0IDc6MjkgQU0N
ClRvOiBJYW4gU3dldHQgPGlhbnN3ZXR0PTQwZ29vZ2xlLmNvbUBkbWFyYy5pZXRmLm9yZz4sIEx1
Y2FzIFBhcmR1ZSA8bHVjYXNwYXJkdWUuMjQuN0BnbWFpbC5jb20+DQpDYzogTWFyayBOb3R0aW5n
aGFtIDxtbm90QG1ub3QubmV0PiwgSUVURiBRVUlDIFdHIDxxdWljQGlldGYub3JnPiwgV2lsbHkg
VGFycmVhdSA8d0Axd3QuZXU+DQpTdWJqZWN0OiBSZTogSWRlbnRpZnlpbmcgb3VyIGRlbGl2ZXJh
Ymxlcw0KDQpSZWNlbnQgZWRpdHMgaW4gdHJhbnNwb3J0IGFsc28gdXNlIHRlcm1zIHN1Y2ggYXMg
4oCcVGhpcyBmcmFtZSBpcyBvbmx5IHVzZWQgaW4gdGhlIFFVSUMgbGF5ZXLigJ0gd2hpY2ggaXMg
c2xpZ2h0bHkgY29uZnVzaW5nIHdoZW4gUVVJQy9IVFRQIGlzIGFsc28gYSAoaGlnaGVyKSBsZXZl
bCBRVUlDIGxheWVyIHdoaWxlIOKAnFFVSUMgbGF5ZXLigJ0gcmVmZXJzIHRvIHRoZSB0cmFuc3Bv
cnQgbGF5ZXIgb25seSwgaW1wbGljaXRseS4NCg0KTWlra2VsDQoNCg0KDQpPbiAzMCBPY3RvYmVy
IDIwMTggYXQgMTUuMjYuMTksIEx1Y2FzIFBhcmR1ZSAobHVjYXNwYXJkdWUuMjQuN0BnbWFpbC5j
b208bWFpbHRvOmx1Y2FzcGFyZHVlLjI0LjdAZ21haWwuY29tPikgd3JvdGU6DQpJIGVjaG8gSWFu
J3MgdGhvdWdodHMsICJIVFRQIG92ZXIgUVVJQyIgZG9lc24ndCB3b3JrIHdlbGwgYXMgYSB0ZXJt
IGluIHByYWN0aWNlLg0KDQpJIHN1cHBvcnQgdGhpcyBjaGFuZ2UsIHVzaW5nIGFuIGluY3JlbWVu
dGFsIG51bWJlciBpcyBsb2dpY2FsLCBhbmQgaXMgY29tcGF0aWJsZSB3aXRoIHRoZSBlY29zeXN0
ZW0gdGhhdCBleHBlY3RzIGFuIEhUVFAgdmVyc2lvbiBudW1iZXIuDQoNCg0KDQpPbiBUdWUsIDMw
IE9jdCAyMDE4LCAxMzo1NiBJYW4gU3dldHQsIDxpYW5zd2V0dD00MGdvb2dsZS5jb21AZG1hcmMu
aWV0Zi4ub3JnPG1haWx0bzo0MGdvb2dsZS5jb21AZG1hcmMuaWV0Zi5vcmc+PiB3cm90ZToNCkZy
b20gYSBjb21wbGV0ZWx5IHByYWN0aWNhbCBwZXJzcGVjdGl2ZSwgSSBzdXBwb3J0IHRoaXMgYmVj
YXVzZSBJIGNhbid0IHRlbGwgeW91IGhvdyBtYW55IHRpbWVzIEkndmUgaGFkIHRvIGV4cGxhaW4g
dGhlIGRpZmZlcmVuY2UgYmV0d2VlbiB0aGUgSFRUUCBvdmVyIFFVSUMgbWFwcGluZyBhbmQgUVVJ
QyB0aGUgdHJhbnNwb3J0Lg0KDQpBbmQgbW92aW5nIHRoZSBIVFRQIG92ZXIgUVVJQyBhbmQgUVBB
Q0sgZG9jdW1lbnRzIHRvIHRoZSBIVFRQIHdvcmtpbmcgZ3JvdXAgc2VlbXMgbGlrZSB0aGUgcmln
aHQgdGhpbmcgdG8gZG8uDQoNCk9uIFR1ZSwgT2N0IDMwLCAyMDE4IGF0IDE6MjEgQU0gV2lsbHkg
VGFycmVhdSA8d0Axd3QuZXU8bWFpbHRvOndAMXd0LmV1Pj4gd3JvdGU6DQpPbiBTdW4sIE9jdCAy
OCwgMjAxOCBhdCAxMTozMDo1NUFNICsxMTAwLCBNYXJrIE5vdHRpbmdoYW0gd3JvdGU6DQo+IFRv
IGFkZHJlc3MgdGhpcywgSSdkIGxpa2UgdG8gc3VnZ2VzdCB0aGF0IC0tIGFmdGVyIGNvb3JkaW5h
dGlvbiB3aXRoIHRoZSBIVFRQDQo+IFdHIC0tIHdlIHJlbmFtZSBvdXIgdGhlIEhUVFAgZG9jdW1l
bnQgdG8gIkhUVFAvMyIsIGFuZCB1c2luZyB0aGUgZmluYWwgQUxQTg0KPiB0b2tlbiAiaDMiLiBE
b2luZyBzbyBjbGVhcmx5IGlkZW50aWZpZXMgaXQgYXMgYW5vdGhlciBiaW5kaW5nIG9mIEhUVFAN
Cj4gc2VtYW50aWNzIHRvIHRoZSB3aXJlIHByb3RvY29sIC0tIGp1c3QgYXMgSFRUUC8yIGRpZCAt
LSBzbyBwZW9wbGUgdW5kZXJzdGFuZA0KPiBpdHMgc2VwYXJhdGlvbiBmcm9tIFFVSUMuDQoNCkZX
SVcgSSBhbHdheXMgdGhvdWdodCB0aGF0IEhUVFAvMyBzaG91bGQgYmUgaXRzIGZpbmFsIG5hbWlu
ZyAtLSBqdXN0IGxpa2UgU1BEWQ0KYmVjYW1lIEhUVFAvMiAtLSBmb3IgdmFyaW91cyByZWFzb25z
LCBvbmUgb2YgdGhlbSBiZWluZyBlbmNvdXJhZ2luZyBhZG9wdGlvbg0KYnkgdGhlIHByb3RvY29s
IGJlaW5nIHByZXNlbnRlZCBhcyB0aGUgbmF0dXJhbCB1cGdyYWRlIHRvIHRoZSBwcmV2aW91cyBv
bmVzDQphbmQgbm90IGEgY29tcGV0aXRvciB0aGF0J3MgYmVlbiB0aGVyZSBmb3Igc29tZSB0aW1l
IGFuZCBzdWRkZW5seSBjb21lcyBhcw0KYW4gUkZDLg0KDQpIMSB3aXRoIDcyM3gsIHRoZW4gSDIg
d2l0aCA3NTR4IGhhdmUgc2hvd24gdGhhdCBpdCdzIG5vdCBhIHByb2JsZW0gdG8gY292ZXINCm11
bHRpcGxlIGFyZWFzIHdpdGggYSBjb21tb24gbmFtZSBhbmQgdGhhdCB0aGUgcHJvdG9jb2wgaXRz
ZWxmIGlzIGluIGZhY3QgYQ0KZmFtaWx5IG9mIHByb3RvY29scyBhbmQgbWVjaGFuaXNtcy4gU28g
UVBBQ0sgd2lsbCBuYXR1cmFsbHkgZmFsbCB1bmRlciBIMw0KanVzdCBsaWtlIEhQQUNLIG5hdHVy
YWxseSBiZWxvbmdzIHRvIEgyLg0KDQpKdXN0IG15IHR3byBjZW50cywNCldpbGx5DQo=

--_000_B135797277314B9EAA80A36D4F31306Cfbcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <1DED87831CD7F044B95836702111BFAE@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseTpIZWx2ZXRpY2E7DQoJcGFub3NlLTE6MCAwIDAgMCAwIDAgMCAwIDAg
MDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0x
OjIgNCA1IDMgNSA0IDYgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJp
Ow0KCXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25z
ICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjow
aW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0K
CXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246
dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28t
c3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRl
cmxpbmU7fQ0KcC5tc29ub3JtYWwwLCBsaS5tc29ub3JtYWwwLCBkaXYubXNvbm9ybWFsMA0KCXtt
c28tc3R5bGUtbmFtZTptc29ub3JtYWw7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFy
Z2luLXJpZ2h0OjBpbjsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVm
dDowaW47DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1z
ZXJpZjt9DQpwLmFpcm1haWxvbiwgbGkuYWlybWFpbG9uLCBkaXYuYWlybWFpbG9uDQoJe21zby1z
dHlsZS1uYW1lOmFpcm1haWxfb247DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2lu
LXJpZ2h0OjBpbjsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDow
aW47DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJp
Zjt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsN
Cglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQouTXNvQ2hwRGVmYXVsdA0KCXtt
c28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdv
cmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4w
aW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48
L3N0eWxlPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJw
dXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PlNpbmNlIHRoZXJlIGlzbuKAmXQgYW55IHBhcnRpY3VsYXIgbmVlZCB0byBpZGVudGlmeSBRVUlD
IHRoZSB0cmFuc3BvcnQgKHdpdGhvdXQgbWVjaGFuaXNtcyB0byBleHBsaWNpdGx5IG11bHRpcGxl
eCBtdWx0aXBsZSBwcm90b2NvbHMpLCBJIHRoaW5rIGNhbGxpbmcgSFRUUC1vbi1RVUlDIEgzIGlz
IHRoZSByaWdodCBtb3ZlLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+UVVJ
QyB3aXRob3V0IGFueXRoaW5nIGVsc2UgaXMgYXMgbWVhbmluZ2xlc3MgYXMgVENQIHdpdGhvdXQg
YW55dGhpbmcgZWxzZSBmcm9tIGEgd2hhdC10aGUtc2VydmVyLXdpbGwtc3BlYWsgcGVyc3BlY3Rp
dmUuPGJyPg0KLT1SPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQg
I0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2NvbG9yOmJsYWNrIj5Gcm9t
OiA8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2NvbG9yOmJsYWNrIj5R
VUlDICZsdDtxdWljLWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7IG9uIGJlaGFsZiBvZiBNaWtrZWwgRmFo
bsO4ZSBKw7hyZ2Vuc2VuICZsdDttaWtrZWxmakBnbWFpbC5jb20mZ3Q7PGJyPg0KPGI+RGF0ZTog
PC9iPlR1ZXNkYXksIE9jdG9iZXIgMzAsIDIwMTggYXQgNzoyOSBBTTxicj4NCjxiPlRvOiA8L2I+
SWFuIFN3ZXR0ICZsdDtpYW5zd2V0dD00MGdvb2dsZS5jb21AZG1hcmMuaWV0Zi5vcmcmZ3Q7LCBM
dWNhcyBQYXJkdWUgJmx0O2x1Y2FzcGFyZHVlLjI0LjdAZ21haWwuY29tJmd0Ozxicj4NCjxiPkNj
OiA8L2I+TWFyayBOb3R0aW5naGFtICZsdDttbm90QG1ub3QubmV0Jmd0OywgSUVURiBRVUlDIFdH
ICZsdDtxdWljQGlldGYub3JnJmd0OywgV2lsbHkgVGFycmVhdSAmbHQ7d0Axd3QuZXUmZ3Q7PGJy
Pg0KPGI+U3ViamVjdDogPC9iPlJlOiBJZGVudGlmeWluZyBvdXIgZGVsaXZlcmFibGVzPG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXYgaWQ9ImJsb29wX2N1c3RvbWZvbnQiPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6SGVsdmV0aWNhIj5SZWNlbnQgZWRpdHMgaW4gdHJhbnNwb3J0IGFsc28gdXNlIHRlcm1z
IHN1Y2ggYXMg4oCcVGhpcyBmcmFtZSBpcyBvbmx5IHVzZWQgaW4gdGhlIFFVSUMgbGF5ZXLigJ0g
d2hpY2ggaXMgc2xpZ2h0bHkgY29uZnVzaW5nIHdoZW4gUVVJQy9IVFRQIGlzIGFsc28gYSAoaGln
aGVyKSBsZXZlbCBRVUlDIGxheWVyIHdoaWxlIOKAnFFVSUMNCiBsYXllcuKAnSByZWZlcnMgdG8g
dGhlIHRyYW5zcG9ydCBsYXllciBvbmx5LCBpbXBsaWNpdGx5LjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdiBpZD0iYmxvb3BfY3VzdG9tZm9udCI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpIZWx2ZXRpY2Ei
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBpZD0iYmxvb3BfY3Vz
dG9tZm9udCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTpIZWx2ZXRpY2EiPk1pa2tlbDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdiBpZD0iYmxvb3BfY3VzdG9tZm9udCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpIZWx2ZXRpY2EiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iYWlybWFpbG9uIj5PbiAzMCBPY3RvYmVy
IDIwMTggYXQgMTUuMjYuMTksIEx1Y2FzIFBhcmR1ZSAoPGEgaHJlZj0ibWFpbHRvOmx1Y2FzcGFy
ZHVlLjI0LjdAZ21haWwuY29tIj5sdWNhc3BhcmR1ZS4yNC43QGdtYWlsLmNvbTwvYT4pIHdyb3Rl
OjxvOnA+PC9vOnA+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFy
Z2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+SSBlY2hvIElhbidzIHRob3VnaHRzLCZuYnNwOzxzcGFuIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj4mcXVvdDtIVFRQIG92ZXIgUVVJ
QyZxdW90OyBkb2Vzbid0IHdvcmsgd2VsbCBhcyBhIHRlcm0gaW4gcHJhY3RpY2UuJm5ic3A7PC9z
cGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgc3Vw
cG9ydCB0aGlzIGNoYW5nZSwgdXNpbmcgYW4gaW5jcmVtZW50YWwgbnVtYmVyIGlzIGxvZ2ljYWws
IGFuZCBpcyBjb21wYXRpYmxlIHdpdGggdGhlIGVjb3N5c3RlbSB0aGF0IGV4cGVjdHMgYW4gSFRU
UCB2ZXJzaW9uIG51bWJlci4mbmJzcDsNCjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPk9uIFR1ZSwgMzAgT2N0IDIwMTgsIDEzOjU2IElhbiBTd2V0dCwg
Jmx0O2lhbnN3ZXR0PTxhIGhyZWY9Im1haWx0bzo0MGdvb2dsZS5jb21AZG1hcmMuaWV0Zi5vcmci
PjQwZ29vZ2xlLmNvbUBkbWFyYy5pZXRmLi5vcmc8L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNv
bGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0
LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Gcm9t
IGEgY29tcGxldGVseSBwcmFjdGljYWwgcGVyc3BlY3RpdmUsIEkgc3VwcG9ydCB0aGlzIGJlY2F1
c2UgSSBjYW4ndCB0ZWxsIHlvdSBob3cgbWFueSB0aW1lcyBJJ3ZlIGhhZCB0byBleHBsYWluIHRo
ZSBkaWZmZXJlbmNlIGJldHdlZW4gdGhlIEhUVFAgb3ZlciBRVUlDIG1hcHBpbmcgYW5kIFFVSUMg
dGhlIHRyYW5zcG9ydC4NCjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+QW5kIG1vdmluZyB0aGUgSFRUUCBvdmVyIFFVSUMgYW5kIFFQQUNLIGRvY3VtZW50cyB0
byB0aGUgSFRUUCB3b3JraW5nIGdyb3VwIHNlZW1zIGxpa2UgdGhlIHJpZ2h0IHRoaW5nIHRvIGRv
LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5P
biBUdWUsIE9jdCAzMCwgMjAxOCBhdCAxOjIxIEFNIFdpbGx5IFRhcnJlYXUgJmx0OzxhIGhyZWY9
Im1haWx0bzp3QDF3dC5ldSIgdGFyZ2V0PSJfYmxhbmsiPndAMXd0LmV1PC9hPiZndDsgd3JvdGU6
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTti
b3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7
bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPk9uIFN1biwgT2N0IDI4LCAyMDE4IGF0IDEx
OjMwOjU1QU0gJiM0MzsxMTAwLCBNYXJrIE5vdHRpbmdoYW0gd3JvdGU6PGJyPg0KJmd0OyBUbyBh
ZGRyZXNzIHRoaXMsIEknZCBsaWtlIHRvIHN1Z2dlc3QgdGhhdCAtLSBhZnRlciBjb29yZGluYXRp
b24gd2l0aCB0aGUgSFRUUDxicj4NCiZndDsgV0cgLS0gd2UgcmVuYW1lIG91ciB0aGUgSFRUUCBk
b2N1bWVudCB0byAmcXVvdDtIVFRQLzMmcXVvdDssIGFuZCB1c2luZyB0aGUgZmluYWwgQUxQTjxi
cj4NCiZndDsgdG9rZW4gJnF1b3Q7aDMmcXVvdDsuIERvaW5nIHNvIGNsZWFybHkgaWRlbnRpZmll
cyBpdCBhcyBhbm90aGVyIGJpbmRpbmcgb2YgSFRUUDxicj4NCiZndDsgc2VtYW50aWNzIHRvIHRo
ZSB3aXJlIHByb3RvY29sIC0tIGp1c3QgYXMgSFRUUC8yIGRpZCAtLSBzbyBwZW9wbGUgdW5kZXJz
dGFuZDxicj4NCiZndDsgaXRzIHNlcGFyYXRpb24gZnJvbSBRVUlDLjxicj4NCjxicj4NCkZXSVcg
SSBhbHdheXMgdGhvdWdodCB0aGF0IEhUVFAvMyBzaG91bGQgYmUgaXRzIGZpbmFsIG5hbWluZyAt
LSBqdXN0IGxpa2UgU1BEWTxicj4NCmJlY2FtZSBIVFRQLzIgLS0gZm9yIHZhcmlvdXMgcmVhc29u
cywgb25lIG9mIHRoZW0gYmVpbmcgZW5jb3VyYWdpbmcgYWRvcHRpb248YnI+DQpieSB0aGUgcHJv
dG9jb2wgYmVpbmcgcHJlc2VudGVkIGFzIHRoZSBuYXR1cmFsIHVwZ3JhZGUgdG8gdGhlIHByZXZp
b3VzIG9uZXM8YnI+DQphbmQgbm90IGEgY29tcGV0aXRvciB0aGF0J3MgYmVlbiB0aGVyZSBmb3Ig
c29tZSB0aW1lIGFuZCBzdWRkZW5seSBjb21lcyBhczxicj4NCmFuIFJGQy48YnI+DQo8YnI+DQpI
MSB3aXRoIDcyM3gsIHRoZW4gSDIgd2l0aCA3NTR4IGhhdmUgc2hvd24gdGhhdCBpdCdzIG5vdCBh
IHByb2JsZW0gdG8gY292ZXI8YnI+DQptdWx0aXBsZSBhcmVhcyB3aXRoIGEgY29tbW9uIG5hbWUg
YW5kIHRoYXQgdGhlIHByb3RvY29sIGl0c2VsZiBpcyBpbiBmYWN0IGE8YnI+DQpmYW1pbHkgb2Yg
cHJvdG9jb2xzIGFuZCBtZWNoYW5pc21zLiBTbyBRUEFDSyB3aWxsIG5hdHVyYWxseSBmYWxsIHVu
ZGVyIEgzPGJyPg0KanVzdCBsaWtlIEhQQUNLIG5hdHVyYWxseSBiZWxvbmdzIHRvIEgyLjxicj4N
Cjxicj4NCkp1c3QgbXkgdHdvIGNlbnRzLDxicj4NCldpbGx5PG86cD48L286cD48L3A+DQo8L2Js
b2NrcXVvdGU+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_B135797277314B9EAA80A36D4F31306Cfbcom_--


From nobody Tue Oct 30 10:55:38 2018
Return-Path: <jri.ietf@gmail.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 6CFFC128BCC for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 10:55:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-0.001] 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 3AEX0KA9YT5m for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 10:55:32 -0700 (PDT)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 58F02127333 for <quic@ietf.org>; Tue, 30 Oct 2018 10:55:31 -0700 (PDT)
Received: by mail-lf1-x12a.google.com with SMTP id p17so3141178lfh.4 for <quic@ietf.org>; Tue, 30 Oct 2018 10:55:31 -0700 (PDT)
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=8av/ek6NCT2D6EwKbWq13k9j0GkZW64J9cvS1YaBi5U=; b=okBerbXcbTA0WjQ9iRJX1nfbKAbbiCZwX3cH/ZPb/39Xco5VKq7l6AhYo+RScsmvaW kpA8/kPe6AKcMShlp5LaG2X67+nQp34hXVk7EdQRaE3aSCGBihgmfJpAIDjR/EQbeXqv xvOQcDZvoq+6Wr+1DPzeyfjIFIWaXsXfyjS8TPMPnCWlX+akwpQ4sdwuovlz4G6NSwRl R1HebRdw4DZA5UI/RnqNBaJoCY8kCQc02YIt+SfHT3XMEhrVdshpMxGNRExmmyWVgUfk hWxRKlQhXleKp/Fmm24r/AEMoiRpxedk5C/iVVgRRu+fFgDLrUdP/xgWHacYTQvllGYY tAZw==
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=8av/ek6NCT2D6EwKbWq13k9j0GkZW64J9cvS1YaBi5U=; b=TQNLmnk9oQs44hCmJfALAmfy3biY2MViR/VSZjHv75l9cazpJ2rtQBujjYwTWc6XAH TytnHJwBOYMlw3EVT68A7ejUes+t7hwGFB6VRbaRhZhA2APFEN2c+XAWIWtDtTnX7vAh zg9rCT43IeIrvtvnWUMREhqFAbQAKjN6UyEvzgeJ+DL7dE02NQ/fEXtaRGeUynVd/E06 HhCW58dznbH3eouRXSZpQNilgEyRTu40sDkXmsR7jvtz6J/SD3RJ17kL2Zoewq0t7aS2 D+Ynr5IMgvVWpLgf5TtD1PpuiEQFafjwR55vas9DzUm1RUhvszGAtoTBNcOWxX5+Khv1 Ng6Q==
X-Gm-Message-State: AGRZ1gIUI2ktpJbYY428tAX8vkyLR+efKl8fXjYpQKbUAm4sGxiFml3y jjmw0oFyRKOwKWo6qF4oNALTbrxlfQxWF7qWu4Q=
X-Google-Smtp-Source: AJdET5dolp75uq3bm0YdIO6oblCWQ3xXC7nqKilEJQTZndnJxc9oSaZUts34/MauCBjwjnsHBNzfUcE1uoxFyNxJMyw=
X-Received: by 2002:a19:1a41:: with SMTP id a62-v6mr2571613lfa.40.1540922129218;  Tue, 30 Oct 2018 10:55:29 -0700 (PDT)
MIME-Version: 1.0
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com> <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch> <a088c411-1acc-8b0f-fc1b-8c79ce6f1cd7@huitema.net> <DB6PR10MB1766E6B29792BB4401FF38F0ACCC0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <2F288470-1659-4A8F-92BD-5640998917D8@trammell.ch>
In-Reply-To: <2F288470-1659-4A8F-92BD-5640998917D8@trammell.ch>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Tue, 30 Oct 2018 10:55:17 -0700
Message-ID: <CACpbDccPEkpdU0KW8iaUk=MKJwd2ptGRr09Z0ofKi+rOv9Ee0A@mail.gmail.com>
Subject: Re: Structuring the BKK spin bit discussion
To: "Brian Trammell (IETF)" <ietf@trammell.ch>
Cc: QUIC WG <quic@ietf.org>, =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>,  Marcus Ihlar <marcus.ihlar@ericsson.com>, Christian Huitema <huitema@huitema.net>
Content-Type: multipart/alternative; boundary="000000000000238240057975e42c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/_rBq3Cjv1G_Uh0XW0-UlPc3PRs8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 17:55:36 -0000

--000000000000238240057975e42c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Brian, (and Martin),

I like this structuring of the discussion, and I think it'll be good to use
this structure for the discussion in BKK.

- jana

On Tue, Oct 30, 2018 at 6:37 AM Brian Trammell (IETF) <ietf@trammell.ch>
wrote:

> hi Marcus, all,
>
> So let me step back a bit and suggest a starting point (borrowing heavily
> from MT in an offlist discussion) for discussing what we want to do in BK=
K.
> (Or rather, I should say, let me suggest a starting point for y'all to
> discuss, because I doubt I'll be in a position to join remotely at 03:00
> next Wednesday local time. Have fun! :)
>
> There seem to be three broad options we've discussed to date:
>
>
> - No spin bit. Grease it if we can't use it for something else.
>
> - "Discretionary" spin: reserve the bit for spinning, implementations
> MAY/SHOULD/whatever spin. MUST doesn't make any sense here, since there's
> no impact on end-to-end interop or the end-to-end properties the protocol
> guarantees.
>
> - "Negotiated" spin: reserve the bit for spinning, define two versions,
> one in which the endpoints MUST NOT spin the bit, one in which the
> endpoints MUST spin the bit. This has the nice property that negotiation =
of
> the spin bit is an actual exercise of the version negotiation mechanism,
> which will keep it flexible for future use better that greasing alone.
> (This was discussed in a thread after the NYC interim, but there's no tex=
t
> for it in spin-exp. I'd be happy to try and bang out a PR for it if that'=
d
> make it easier for people to understand/discuss in BKK.)
>
> Beyond this, there seem to be a few other qualities we want, and the
> details matter for these. The most important quality discussed is the
> maintenance of an anonymity set of non-spinning flows so that an endpoint
> that does not want to spin will not immediately stick out. So we can defi=
ne
> some parameters that meet those qualities for both of the discretionary a=
nd
> negotiated variants. Let me propose the following values for these
> parameters, as a starting point for discussion in BKK:
>
>
> (1) No spin bit: no parameters. If the bit is reserved, it must be
> greased. (I'd submit that experimental use of the spin bit is a good form
> of greasing, so an implementation can offer discretionary spin if it like=
s,
> but without large-scale implementation, such experimental use is seen on =
a
> tiny minority of traffic and becomes a wholly academic exercise.)
>
>
> (2) Discretionary spin bit: here we want to determine compliance levels
> and participation probability. I'd suggest:
>
> - client SHOULD implement and server SHOULD implement (I acknowledge this
> is a personal preference; I suggest it because I think it will drive
> deployment better than MAY/SHOULD or MAY/MAY).
>
> - both client and server SHOULD allow the application and/or user/system
> configuration to force a given connection or set of connections to spin
> (for targeted diagnostic purposes) or not to spin. (This is a REALLY
> SHOULD, only because MUST on the interface doesn't make a lot of sense.)
>
> - in the absence of such configuration, both client and server SHOULD
> independently decide to spin the bit on a given connection with a set
> probability. I'd suggest probabilities at each endpoint of 7/8, so 3/4 of
> flows between implementing endpoints will expose RTT. This is a wild gues=
s
> at a good starting point, though, picked to cause a large proportion of
> flows to spin even if only a small number of large implementations decide
> to implement; it is possible to set the recommendation smaller if it look=
s
> like the majority of implementations will spin. These proportions SHOULD =
be
> user/system/application configurable.
>
> - when not spinning, each of the client and server should randomly select
> a value for the spin bit for each new CID the duration of the connection,
> and send that value on every packet with that CID.
>
> This will ensure that even in a future with perfect deployment, the set o=
f
> flows that aren't spinning because of deliberate configuration at any giv=
en
> time will have a large enough anonymity set to hide in. It also makes the
> job of recognizing non-spinning flows easy. In any case, it is important
> that all non-spinning flows (due to non-implementation, random choice, or
> deliberate configuration) non-spin in the same way.
>
>
> (3) Negotiated spin bit: same question. I'd suggest that the starting
> points be chosen to result in the same proportion of spinning bits as in
> discretionary case (2) above, so:
>
> - client SHOULD implement and server SHOULD implement (same comment as
> above)
>
> - both client and server SHOULD allow the application and/or user/system
> configuration to force a given connection to offer/accept to spin, or to
> not offer/refuse to spin.
>
> - in the absence of such configuration, the client SHOULD offer to spin
> (request the spin version of the protocol) with a set probability, and th=
e
> server SHOULD accept an offer to spin with a set probability. Suggest 7/8
> as above, for target probability 3/4, same caveats.
>
> - when negotiated, both endpoints MUST spin the bit (as described in
> quic-spin-exp). If one endpoint detects the other is not spinning, it MUS=
T
> terminate the connection, as this may indicate an error in the version
> negotiation mechanism itself.
>
> - when not negotiated, each of the client and server should randomly
> select a value for the spin bit for each new CID the duration of the
> connection, and send that value on every packet with that CID.
>
> The additional properties negotiated spin has with respect to
> discretionary spin are that it is a real exercise of the version
> negotiation mechanism, and that it provides an explicit signal to on-path
> devices that a given connection will spin.
>
>
> I suggest we try to start from these three points, separating the questio=
n
> of which pattern (none, discretionary, negotiated) we prefer, from the
> questions about the particular parameters applied thereto. Key is that we
> can tweak the parameters for either pattern to arrive at a given deployme=
nt
> curve and proportion of spinning bits in the network.
>
> Thanks, cheers,
>
> Brian
>
>
>
> P.S.: I'm not ignoring the "hold two other bits out for measurement
> experimentation" question, but I consider it to be an orthogonal question
> to these; I think it's worth discussing, but we can treat it separately, =
so
> we should. In any case I think the work you (Marcus) have done has shown
> that relatively simple heuristics at the measurement point deliver most o=
f
> the benefit in terms of measurement fidelity in the presence of loss and
> reordering that the VEC can for realistic loss and reordering rates, for
> two fewer bits per packet. So the spin bit is worth doing on its own.
>
>
>
>
>
> > On 30 Oct 2018, at 12:55, Marcus Ihlar <marcus.ihlar@ericsson.com>
> wrote:
> >
> > Making it more difficult to differentiate explicit opt-out from random
> opt-out is likely useful even if it doesn=E2=80=99t help in the particula=
r Netflix
> case.
> > Furthermore, just like Brian points out it is necessary to grease the
> bit if we want to change the bit semantics later on.
> > I think the proposal has low enough complexity and potential benefits t=
o
> be worthwhile.
> >
> > From: QUIC <quic-bounces@ietf.org> On Behalf Of Mikkel Fahn=C3=B8e J=C3=
=B8rgensen
> > Sent: den 30 oktober 2018 08:01
> > To: Christian Huitema <huitema@huitema.net>; quic@ietf.org
> > Subject: Re: Structuring the BKK spin bit discussion
> >
> > In the Netflix case it just takes 16 connections by the same user, or
> less when multiple users originate from the sane IP range.. Is it really
> practical (and thus worthwhile) to hide probabilistically as in Huitemas =
PR?
> >
> > From: QUIC <quic-bounces@ietf.org> on behalf of Christian Huitema <
> huitema@huitema.net>
> > Sent: Tuesday, October 30, 2018 5:27:47 AM
> > To: quic@ietf.org
> > Subject: Re: Structuring the BKK spin bit discussion
> >
> > On 10/29/2018 3:58 PM, Brian Trammell (IETF) wrote:
> >
> > hi Martin, Christian, all,
> >
> > On 29 Oct 2018, at 23:29, Martin Thomson <martin.thomson@gmail.com>
> wrote:
> >
> > On Tue, Oct 30, 2018 at 3:54 AM Christian Huitema <huitema@huitema.net>
> wrote:
> > I think the strongest objection to the spin bit was put up by Marten
> during the last interim: measuring the RTT with the spin bit discloses th=
e
> use of hidden path segments like VPN. This issue was not discussed during
> the privacy analysis.
> > I had assumed that was part of the analysis and it was covered by the
> > assumption that spinning could be disabled
> > +1. Probabilistically disabling spinning, which seems necessary if we
> want some grease to help us reserve the right to change the semantics of
> the bit at the spin bit's location in the wire image, should ensure that
> endpoints that want to disable spinning for their own reasons will have a
> large anonymity set to hide in, even in a future with perfect
> implementation and deployment of the spin bit.
> >
> > I opened PR https://github.com/quicwg/base-drafts/pull/1931 to discuss
> this.
> >
> > -- Christian Huitema
>
>

--000000000000238240057975e42c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Brian, (and Martin),<div><br></div><div>I like this struct=
uring of the discussion, and I think it&#39;ll be good to use this structur=
e for the discussion in BKK.</div><div><br></div><div>- jana</div></div><br=
><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Oct 30, 2018 at 6:37 A=
M Brian Trammell (IETF) &lt;<a href=3D"mailto:ietf@trammell.ch">ietf@tramme=
ll.ch</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hi Marcus, all=
,<br>
<br>
So let me step back a bit and suggest a starting point (borrowing heavily f=
rom MT in an offlist discussion) for discussing what we want to do in BKK. =
(Or rather, I should say, let me suggest a starting point for y&#39;all to =
discuss, because I doubt I&#39;ll be in a position to join remotely at 03:0=
0 next Wednesday local time. Have fun! :)<br>
<br>
There seem to be three broad options we&#39;ve discussed to date:<br>
<br>
<br>
- No spin bit. Grease it if we can&#39;t use it for something else.<br>
<br>
- &quot;Discretionary&quot; spin: reserve the bit for spinning, implementat=
ions MAY/SHOULD/whatever spin. MUST doesn&#39;t make any sense here, since =
there&#39;s no impact on end-to-end interop or the end-to-end properties th=
e protocol guarantees.<br>
<br>
- &quot;Negotiated&quot; spin: reserve the bit for spinning, define two ver=
sions, one in which the endpoints MUST NOT spin the bit, one in which the e=
ndpoints MUST spin the bit. This has the nice property that negotiation of =
the spin bit is an actual exercise of the version negotiation mechanism, wh=
ich will keep it flexible for future use better that greasing alone. (This =
was discussed in a thread after the NYC interim, but there&#39;s no text fo=
r it in spin-exp. I&#39;d be happy to try and bang out a PR for it if that&=
#39;d make it easier for people to understand/discuss in BKK.)<br>
<br>
Beyond this, there seem to be a few other qualities we want, and the detail=
s matter for these. The most important quality discussed is the maintenance=
 of an anonymity set of non-spinning flows so that an endpoint that does no=
t want to spin will not immediately stick out. So we can define some parame=
ters that meet those qualities for both of the discretionary and negotiated=
 variants. Let me propose the following values for these parameters, as a s=
tarting point for discussion in BKK:<br>
<br>
<br>
(1) No spin bit: no parameters. If the bit is reserved, it must be greased.=
 (I&#39;d submit that experimental use of the spin bit is a good form of gr=
easing, so an implementation can offer discretionary spin if it likes, but =
without large-scale implementation, such experimental use is seen on a tiny=
 minority of traffic and becomes a wholly academic exercise.)<br>
<br>
<br>
(2) Discretionary spin bit: here we want to determine compliance levels and=
 participation probability. I&#39;d suggest:<br>
<br>
- client SHOULD implement and server SHOULD implement (I acknowledge this i=
s a personal preference; I suggest it because I think it will drive deploym=
ent better than MAY/SHOULD or MAY/MAY).<br>
<br>
- both client and server SHOULD allow the application and/or user/system co=
nfiguration to force a given connection or set of connections to spin (for =
targeted diagnostic purposes) or not to spin. (This is a REALLY SHOULD, onl=
y because MUST on the interface doesn&#39;t make a lot of sense.)<br>
<br>
- in the absence of such configuration, both client and server SHOULD indep=
endently decide to spin the bit on a given connection with a set probabilit=
y. I&#39;d suggest probabilities at each endpoint of 7/8, so 3/4 of flows b=
etween implementing endpoints will expose RTT. This is a wild guess at a go=
od starting point, though, picked to cause a large proportion of flows to s=
pin even if only a small number of large implementations decide to implemen=
t; it is possible to set the recommendation smaller if it looks like the ma=
jority of implementations will spin. These proportions SHOULD be user/syste=
m/application configurable.<br>
<br>
- when not spinning, each of the client and server should randomly select a=
 value for the spin bit for each new CID the duration of the connection, an=
d send that value on every packet with that CID.<br>
<br>
This will ensure that even in a future with perfect deployment, the set of =
flows that aren&#39;t spinning because of deliberate configuration at any g=
iven time will have a large enough anonymity set to hide in. It also makes =
the job of recognizing non-spinning flows easy. In any case, it is importan=
t that all non-spinning flows (due to non-implementation, random choice, or=
 deliberate configuration) non-spin in the same way.<br>
<br>
<br>
(3) Negotiated spin bit: same question. I&#39;d suggest that the starting p=
oints be chosen to result in the same proportion of spinning bits as in dis=
cretionary case (2) above, so:<br>
<br>
- client SHOULD implement and server SHOULD implement (same comment as abov=
e)<br>
<br>
- both client and server SHOULD allow the application and/or user/system co=
nfiguration to force a given connection to offer/accept to spin, or to not =
offer/refuse to spin.<br>
<br>
- in the absence of such configuration, the client SHOULD offer to spin (re=
quest the spin version of the protocol) with a set probability, and the ser=
ver SHOULD accept an offer to spin with a set probability. Suggest 7/8 as a=
bove, for target probability 3/4, same caveats.<br>
<br>
- when negotiated, both endpoints MUST spin the bit (as described in quic-s=
pin-exp). If one endpoint detects the other is not spinning, it MUST termin=
ate the connection, as this may indicate an error in the version negotiatio=
n mechanism itself.<br>
<br>
- when not negotiated, each of the client and server should randomly select=
 a value for the spin bit for each new CID the duration of the connection, =
and send that value on every packet with that CID.<br>
<br>
The additional properties negotiated spin has with respect to discretionary=
 spin are that it is a real exercise of the version negotiation mechanism, =
and that it provides an explicit signal to on-path devices that a given con=
nection will spin.<br>
<br>
<br>
I suggest we try to start from these three points, separating the question =
of which pattern (none, discretionary, negotiated) we prefer, from the ques=
tions about the particular parameters applied thereto. Key is that we can t=
weak the parameters for either pattern to arrive at a given deployment curv=
e and proportion of spinning bits in the network.<br>
<br>
Thanks, cheers,<br>
<br>
Brian<br>
<br>
<br>
<br>
P.S.: I&#39;m not ignoring the &quot;hold two other bits out for measuremen=
t experimentation&quot; question, but I consider it to be an orthogonal que=
stion to these; I think it&#39;s worth discussing, but we can treat it sepa=
rately, so we should. In any case I think the work you (Marcus) have done h=
as shown that relatively simple heuristics at the measurement point deliver=
 most of the benefit in terms of measurement fidelity in the presence of lo=
ss and reordering that the VEC can for realistic loss and reordering rates,=
 for two fewer bits per packet. So the spin bit is worth doing on its own.<=
br>
<br>
<br>
<br>
<br>
<br>
&gt; On 30 Oct 2018, at 12:55, Marcus Ihlar &lt;<a href=3D"mailto:marcus.ih=
lar@ericsson.com" target=3D"_blank">marcus.ihlar@ericsson.com</a>&gt; wrote=
:<br>
&gt; <br>
&gt; Making it more difficult to differentiate explicit opt-out from random=
 opt-out is likely useful even if it doesn=E2=80=99t help in the particular=
 Netflix case.<br>
&gt; Furthermore, just like Brian points out it is necessary to grease the =
bit if we want to change the bit semantics later on.<br>
&gt; I think the proposal has low enough complexity and potential benefits =
to be worthwhile.<br>
&gt; <br>
&gt; From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_bla=
nk">quic-bounces@ietf.org</a>&gt; On Behalf Of Mikkel Fahn=C3=B8e J=C3=B8rg=
ensen<br>
&gt; Sent: den 30 oktober 2018 08:01<br>
&gt; To: Christian Huitema &lt;<a href=3D"mailto:huitema@huitema.net" targe=
t=3D"_blank">huitema@huitema.net</a>&gt;; <a href=3D"mailto:quic@ietf.org" =
target=3D"_blank">quic@ietf.org</a><br>
&gt; Subject: Re: Structuring the BKK spin bit discussion<br>
&gt; <br>
&gt; In the Netflix case it just takes 16 connections by the same user, or =
less when multiple users originate from the sane IP range.. Is it really pr=
actical (and thus worthwhile) to hide probabilistically as in Huitemas PR?<=
br>
&gt; <br>
&gt; From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_bla=
nk">quic-bounces@ietf.org</a>&gt; on behalf of Christian Huitema &lt;<a hre=
f=3D"mailto:huitema@huitema.net" target=3D"_blank">huitema@huitema.net</a>&=
gt;<br>
&gt; Sent: Tuesday, October 30, 2018 5:27:47 AM<br>
&gt; To: <a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf.org</=
a><br>
&gt; Subject: Re: Structuring the BKK spin bit discussion<br>
&gt; <br>
&gt; On 10/29/2018 3:58 PM, Brian Trammell (IETF) wrote:<br>
&gt; <br>
&gt; hi Martin, Christian, all,<br>
&gt; <br>
&gt; On 29 Oct 2018, at 23:29, Martin Thomson &lt;<a href=3D"mailto:martin.=
thomson@gmail.com" target=3D"_blank">martin.thomson@gmail.com</a>&gt; wrote=
:<br>
&gt; <br>
&gt; On Tue, Oct 30, 2018 at 3:54 AM Christian Huitema &lt;<a href=3D"mailt=
o:huitema@huitema.net" target=3D"_blank">huitema@huitema.net</a>&gt; wrote:=
<br>
&gt; I think the strongest objection to the spin bit was put up by Marten d=
uring the last interim: measuring the RTT with the spin bit discloses the u=
se of hidden path segments like VPN. This issue was not discussed during th=
e privacy analysis.<br>
&gt; I had assumed that was part of the analysis and it was covered by the<=
br>
&gt; assumption that spinning could be disabled<br>
&gt; +1. Probabilistically disabling spinning, which seems necessary if we =
want some grease to help us reserve the right to change the semantics of th=
e bit at the spin bit&#39;s location in the wire image, should ensure that =
endpoints that want to disable spinning for their own reasons will have a l=
arge anonymity set to hide in, even in a future with perfect implementation=
 and deployment of the spin bit.<br>
&gt; <br>
&gt; I opened PR <a href=3D"https://github.com/quicwg/base-drafts/pull/1931=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/1931</a> to discuss this.<br>
&gt; <br>
&gt; -- Christian Huitema<br>
<br>
</blockquote></div>

--000000000000238240057975e42c--


From nobody Tue Oct 30 10:59:06 2018
Return-Path: <jri.ietf@gmail.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 42895130D7A for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 10:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 uNOAqIOj8BUM for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 10:59:03 -0700 (PDT)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 1CCC7127333 for <quic@ietf.org>; Tue, 30 Oct 2018 10:59:03 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id o2-v6so9577651lfl.13 for <quic@ietf.org>; Tue, 30 Oct 2018 10:59:03 -0700 (PDT)
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=koDj3CZsF6b4XAzOjhiM7gjsIy4OWsKDbtg/d1BYsJI=; b=rZ0V0qym93UaYMdnWTSY744uQDUQA3LC0Daew93iX7NuexHtLxlDScgssXfnDXIn5O 86wgrw72n6HC9u8AXENTGQM4boQYk4mXKwUDYOrqrPp9mrqA0V/inz+kpB+I5GTDNqj4 WdTCCFrNPcn4XIcsQxQ2gcDTttze9w03Ouo1beTRaDnHpIRKgYjzmOBOFPeRveYnLlrR ov6U3OFn1sHPaAtWcj1FjrdxS6OWaJZt7Bnpw8HpZpXonPOJylJCGvHvr6KUhj+XoVz7 bT0Z0ukk1TbRFov0yWfd8Y/PbDqK4B/EFfZV2QLMtg2YQrAW0hdhauNaxWdzADERD2Uw oGxw==
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=koDj3CZsF6b4XAzOjhiM7gjsIy4OWsKDbtg/d1BYsJI=; b=RFQPq0Q4aUS76uva6NLvweCFNF/AsRCgkuKVfg/02bD6gt9mXxQh9yIhqsJB5W6KCA 3GRBeTo5V49Y2Bn2FhiLM9a5z4W/Dzs0hDwT78Cskg/2IwTHJOmQCXXuV4ZkQpiVsm9H eX5CoSU1bD1KqHZKHaE4NWPwlUcUcC+frAJSKqqESyWbt+f6m1ERq1B7vOYmz2JvV5GT Ol7P7+oh1MFa+8hL+g7QZZESQKKZSql9cXD3OpbX2oKnIwlJohLFSIxBIWjRmnMvRhmn bM/MAPgQcHLmPBNvM/JC02lnATx+sg2v0M/XiuqBB+e2YXHi8WBq5nFag3pC8RHikzgc kVFQ==
X-Gm-Message-State: AGRZ1gIwYvqGqj849jZ6Mn2FX6qlvvwr8mBX44JH09TgHsUbPESLhAy1 KHnva3+RJJnVSBCku0Znf4jG2h/arUfG24poXUI=
X-Google-Smtp-Source: AJdET5ctIr+VHpDftWbQG2cagr5yXc22CUFBcyr6tZTtbWXojDXWsoYMjCtGtb28CljTBgzQ936No1TN9M5/SFANnQw=
X-Received: by 2002:a19:1a41:: with SMTP id a62-v6mr2579045lfa.40.1540922341223;  Tue, 30 Oct 2018 10:59:01 -0700 (PDT)
MIME-Version: 1.0
References: <578BB4EC-421E-4B21-AA14-B545A41754C8@mnot.net> <20181030052133.GA29963@1wt.eu> <CAKcm_gNbQyvAOVsg7wCj+M83Thsj+=KJD0QGLcq42-RAwhTf=g@mail.gmail.com> <CALGR9oZSj0GSa=3EVFt27=DLahqJj+qS0nUSfqFNf+NWnEbsLg@mail.gmail.com> <CAN1APdeKSWYFgtiKT-=eQ0=o+Mm6pyFeY00trd+SMLKNdVofxw@mail.gmail.com> <B1357972-7731-4B9E-AA80-A36D4F31306C@fb.com>
In-Reply-To: <B1357972-7731-4B9E-AA80-A36D4F31306C@fb.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Tue, 30 Oct 2018 10:58:49 -0700
Message-ID: <CACpbDcfHNxUnXXNF6Tarapaw+=0SkHVGT9Wj7a967BKAibsDqQ@mail.gmail.com>
Subject: Re: Identifying our deliverables
To: Roberto Peon <fenix@fb.com>
Cc: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>,  Ian Swett <ianswett=40google.com@dmarc.ietf.org>, lucaspardue.24.7@gmail.com,  Mark Nottingham <mnot@mnot.net>, QUIC WG <quic@ietf.org>, w@1wt.eu
Content-Type: multipart/alternative; boundary="000000000000c67289057975f01f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/LKMqlT0PeBpKAnOadq4VZ2jbu-E>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 17:59:05 -0000

--000000000000c67289057975f01f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I'll add to the chorus: I'm in favor of this change.

On Tue, Oct 30, 2018 at 9:36 AM Roberto Peon <fenix@fb.com> wrote:

> Since there isn=E2=80=99t any particular need to identify QUIC the transp=
ort
> (without mechanisms to explicitly multiplex multiple protocols), I think
> calling HTTP-on-QUIC H3 is the right move.
>
> QUIC without anything else is as meaningless as TCP without anything else
> from a what-the-server-will-speak perspective.
> -=3DR
>
>
>
> *From: *QUIC <quic-bounces@ietf.org> on behalf of Mikkel Fahn=C3=B8e J=C3=
=B8rgensen
> <mikkelfj@gmail.com>
> *Date: *Tuesday, October 30, 2018 at 7:29 AM
> *To: *Ian Swett <ianswett=3D40google.com@dmarc.ietf.org>, Lucas Pardue <
> lucaspardue.24.7@gmail.com>
> *Cc: *Mark Nottingham <mnot@mnot.net>, IETF QUIC WG <quic@ietf.org>,
> Willy Tarreau <w@1wt.eu>
> *Subject: *Re: Identifying our deliverables
>
>
>
> Recent edits in transport also use terms such as =E2=80=9CThis frame is o=
nly used
> in the QUIC layer=E2=80=9D which is slightly confusing when QUIC/HTTP is =
also a
> (higher) level QUIC layer while =E2=80=9CQUIC layer=E2=80=9D refers to th=
e transport layer
> only, implicitly.
>
>
>
> Mikkel
>
>
>
>
>
> On 30 October 2018 at 15.26.19, Lucas Pardue (lucaspardue.24.7@gmail.com)
> wrote:
>
> I echo Ian's thoughts, "HTTP over QUIC" doesn't work well as a term in
> practice.
>
>
>
> I support this change, using an incremental number is logical, and is
> compatible with the ecosystem that expects an HTTP version number.
>
>
>
>
>
>
>
> On Tue, 30 Oct 2018, 13:56 Ian Swett, <ianswett=3D
> 40google.com@dmarc.ietf..org <40google.com@dmarc.ietf.org>> wrote:
>
> From a completely practical perspective, I support this because I can't
> tell you how many times I've had to explain the difference between the HT=
TP
> over QUIC mapping and QUIC the transport.
>
>
>
> And moving the HTTP over QUIC and QPACK documents to the HTTP working
> group seems like the right thing to do.
>
>
>
> On Tue, Oct 30, 2018 at 1:21 AM Willy Tarreau <w@1wt.eu> wrote:
>
> On Sun, Oct 28, 2018 at 11:30:55AM +1100, Mark Nottingham wrote:
> > To address this, I'd like to suggest that -- after coordination with th=
e
> HTTP
> > WG -- we rename our the HTTP document to "HTTP/3", and using the final
> ALPN
> > token "h3". Doing so clearly identifies it as another binding of HTTP
> > semantics to the wire protocol -- just as HTTP/2 did -- so people
> understand
> > its separation from QUIC.
>
> FWIW I always thought that HTTP/3 should be its final naming -- just like
> SPDY
> became HTTP/2 -- for various reasons, one of them being encouraging
> adoption
> by the protocol being presented as the natural upgrade to the previous on=
es
> and not a competitor that's been there for some time and suddenly comes a=
s
> an RFC.
>
> H1 with 723x, then H2 with 754x have shown that it's not a problem to cov=
er
> multiple areas with a common name and that the protocol itself is in fact=
 a
> family of protocols and mechanisms. So QPACK will naturally fall under H3
> just like HPACK naturally belongs to H2.
>
> Just my two cents,
> Willy
>
>

--000000000000c67289057975f01f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;ll add to the chorus: I&#39;m in favor of this chang=
e.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Oct 30, 201=
8 at 9:36 AM Roberto Peon &lt;<a href=3D"mailto:fenix@fb.com">fenix@fb.com<=
/a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-5275553445103497062WordSection1">
<p class=3D"MsoNormal">Since there isn=E2=80=99t any particular need to ide=
ntify QUIC the transport (without mechanisms to explicitly multiplex multip=
le protocols), I think calling HTTP-on-QUIC H3 is the right move.<u></u><u>=
</u></p>
<p class=3D"MsoNormal">QUIC without anything else is as meaningless as TCP =
without anything else from a what-the-server-will-speak perspective.<br>
-=3DR<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:12.0pt;color:black">From=
: </span></b><span style=3D"font-size:12.0pt;color:black">QUIC &lt;<a href=
=3D"mailto:quic-bounces@ietf.org" target=3D"_blank">quic-bounces@ietf.org</=
a>&gt; on behalf of Mikkel Fahn=C3=B8e J=C3=B8rgensen &lt;<a href=3D"mailto=
:mikkelfj@gmail.com" target=3D"_blank">mikkelfj@gmail.com</a>&gt;<br>
<b>Date: </b>Tuesday, October 30, 2018 at 7:29 AM<br>
<b>To: </b>Ian Swett &lt;ianswett=3D<a href=3D"mailto:40google.com@dmarc.ie=
tf.org" target=3D"_blank">40google.com@dmarc.ietf.org</a>&gt;, Lucas Pardue=
 &lt;<a href=3D"mailto:lucaspardue.24.7@gmail.com" target=3D"_blank">lucasp=
ardue.24.7@gmail.com</a>&gt;<br>
<b>Cc: </b>Mark Nottingham &lt;<a href=3D"mailto:mnot@mnot.net" target=3D"_=
blank">mnot@mnot.net</a>&gt;, IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.=
org" target=3D"_blank">quic@ietf.org</a>&gt;, Willy Tarreau &lt;<a href=3D"=
mailto:w@1wt.eu" target=3D"_blank">w@1wt.eu</a>&gt;<br>
<b>Subject: </b>Re: Identifying our deliverables<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div id=3D"m_-5275553445103497062bloop_customfont">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:Helvetic=
a">Recent edits in transport also use terms such as =E2=80=9CThis frame is =
only used in the QUIC layer=E2=80=9D which is slightly confusing when QUIC/=
HTTP is also a (higher) level QUIC layer while =E2=80=9CQUIC
 layer=E2=80=9D refers to the transport layer only, implicitly.<u></u><u></=
u></span></p>
</div>
<div id=3D"m_-5275553445103497062bloop_customfont">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:Helvetic=
a"><u></u>=C2=A0<u></u></span></p>
</div>
<div id=3D"m_-5275553445103497062bloop_customfont">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:Helvetic=
a">Mikkel<u></u><u></u></span></p>
</div>
<div id=3D"m_-5275553445103497062bloop_customfont">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:Helvetic=
a"><u></u>=C2=A0<u></u></span></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"m_-5275553445103497062airmailon">On 30 October 2018 at 15.26.19=
, Lucas Pardue (<a href=3D"mailto:lucaspardue.24.7@gmail.com" target=3D"_bl=
ank">lucaspardue.24.7@gmail.com</a>) wrote:<u></u><u></u></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal">I echo Ian&#39;s thoughts,=C2=A0<span style=3D"font-=
family:&quot;Arial&quot;,sans-serif">&quot;HTTP over QUIC&quot; doesn&#39;t=
 work well as a term in practice.=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">I support this change, using an incremental number i=
s logical, and is compatible with the ecosystem that expects an HTTP versio=
n number.=C2=A0
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Tue, 30 Oct 2018, 13:56 Ian Swett, &lt;ianswett=
=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_blank">40googl=
e.com@dmarc.ietf..org</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class=3D"MsoNormal">From a completely practical perspective, I support t=
his because I can&#39;t tell you how many times I&#39;ve had to explain the=
 difference between the HTTP over QUIC mapping and QUIC the transport.
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">And moving the HTTP over QUIC and QPACK documents to=
 the HTTP working group seems like the right thing to do.<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Tue, Oct 30, 2018 at 1:21 AM Willy Tarreau &lt;<a=
 href=3D"mailto:w@1wt.eu" target=3D"_blank">w@1wt.eu</a>&gt; wrote:<u></u><=
u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">On Sun, Oct 28, 2018 =
at 11:30:55AM +1100, Mark Nottingham wrote:<br>
&gt; To address this, I&#39;d like to suggest that -- after coordination wi=
th the HTTP<br>
&gt; WG -- we rename our the HTTP document to &quot;HTTP/3&quot;, and using=
 the final ALPN<br>
&gt; token &quot;h3&quot;. Doing so clearly identifies it as another bindin=
g of HTTP<br>
&gt; semantics to the wire protocol -- just as HTTP/2 did -- so people unde=
rstand<br>
&gt; its separation from QUIC.<br>
<br>
FWIW I always thought that HTTP/3 should be its final naming -- just like S=
PDY<br>
became HTTP/2 -- for various reasons, one of them being encouraging adoptio=
n<br>
by the protocol being presented as the natural upgrade to the previous ones=
<br>
and not a competitor that&#39;s been there for some time and suddenly comes=
 as<br>
an RFC.<br>
<br>
H1 with 723x, then H2 with 754x have shown that it&#39;s not a problem to c=
over<br>
multiple areas with a common name and that the protocol itself is in fact a=
<br>
family of protocols and mechanisms. So QPACK will naturally fall under H3<b=
r>
just like HPACK naturally belongs to H2.<br>
<br>
Just my two cents,<br>
Willy<u></u><u></u></p>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>

</blockquote></div>

--000000000000c67289057975f01f--


From nobody Tue Oct 30 11:40:54 2018
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 24310130E1B for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 11:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 QkaV85T5rpWm for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 11:40:40 -0700 (PDT)
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 9AC76130DFD for <quic@ietf.org>; Tue, 30 Oct 2018 11:40:40 -0700 (PDT)
Received: from xsmtp12.mail2web.com ([168.144.250.177]) by mx37.antispamcloud.com with esmtps (TLSv1.2:AES128-SHA:128) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1gHYwO-0006uv-4H for quic@ietf.org; Tue, 30 Oct 2018 19:40:37 +0100
Received: from [10.5.2.15] (helo=xmail05.myhosting.com) by xsmtp12.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from <huitema@huitema.net>) id 1gHYvm-0006hH-VL for quic@ietf.org; Tue, 30 Oct 2018 14:40:34 -0400
Received: (qmail 4766 invoked from network); 30 Oct 2018 18:39:56 -0000
Received: from unknown (HELO [192.168.1.100]) (Authenticated-user:_huitema@huitema.net@[172.56.42.225]) (envelope-sender <huitema@huitema.net>) by xmail05.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 30 Oct 2018 18:39:54 -0000
To: Marcus Ihlar <marcus.ihlar@ericsson.com>, "mikkelfj@gmail.com" <mikkelfj@gmail.com>, "quic@ietf.org" <quic@ietf.org>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com> <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch> <a088c411-1acc-8b0f-fc1b-8c79ce6f1cd7@huitema.net> <DB6PR10MB1766E6B29792BB4401FF38F0ACCC0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
From: Christian Huitema <huitema@huitema.net>
Openpgp: preference=signencrypt
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= xsBNBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAHNJ0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PsLAeQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1bOwE0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAcLBfgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8=
Message-ID: <65907d96-a525-dcd0-39cd-678c52d26ab6@huitema.net>
Date: Tue, 30 Oct 2018 11:39:52 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------0B1BAC0CAFEE5A487D58DE70"
Content-Language: en-US
Subject: Re: Structuring the BKK spin bit discussion
X-Originating-IP: 168.144.250.177
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.23)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5kBpJk8GlPra1v1msIriLoB602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO37pNwwF1lRXh5rzvPzo9Jts1ujulqUFmMITHM77eiViOr6TL2aTYnruHLS172gRQc7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pB1c1FPznmLv13i1NL5aXaHx/TBCf6oYXAWGet lavcAjD9ytQxIHf9lN5jjLJaPK8ld75Mkfa0TXuGgWrtZAThGwCXzXVH0VhevtbmuedAriM5y6Jm AIAY8S7twiW4L/r9ejBqyWvcZBiXaJZVJq4phGrxEaaKeSxe0Wrx6M4G5/V80gh9dcdo+eZNL0Fs iIzVTmUGeySSmF3iws3y1vQUjhgfpCul9mJMxGTjFfDR8Fy86PGjtK99ZvAN7RDQPAib1gsC8oLX MeV2P9P0vPDCmSCv9TR+UxzLZWL8hwGBjhpX1GxcrmFtrLoYg/qdZgT+F3skC2Xm0bnSHV49vy45 +off17ZK94fMsXNf9icpky+FiB3uMCt7k721kuE0szZgdQDKTJVLRKBoxwiWStFyQEJX12/0qGkU ppSf8KeokHprb+EVdww6XCcBiPtcXsBGWe4P8aUJ+LQRE1MkIL8E1/E+tYwN4qebTyj8dmVwpn/X afo0bG1ffaPnDAnoTKJfe34TY+s3lj/RgDQoaICKQ3CGH75AEzzXKcS8MGkqOEI2WSdZEs8pgSzd lhsywaPkHHASJNUmoOHSoqgqxfHmWf5Y5QBZjkGm+ftxh+1gKnz0ZjEYT1k5oGj+q8taxT49k80x dgCFHeK5ajw1RkNe48OlaqhSmisOylbyX9cD1dzUjq68vZr+JJ1bJDCUHbEf5OULFjqmmjT2Lzr1 GjHkRCERbInMiTBIUBbQ/Dy6Ip4ZoX5yXuaBZHopk5YnJpgZXnghBRqZ+JqkkJtSSxnHbb2yh0VC hVH6RkcwhKi7Pjg=
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/DVe6mbh35ceCx2gXVPbZi9IiveY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 18:40:54 -0000

This is a multi-part message in MIME format.
--------------0B1BAC0CAFEE5A487D58DE70
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable


On 10/30/2018 4:55 AM, Marcus Ihlar wrote:
>
> Making it more difficult to differentiate explicit opt-out from random
> opt-out is likely useful even if it doesn=92t help in the particular
> Netflix case.
>
> Furthermore, just like Brian points out it is necessary to grease the
> bit if we want to change the bit semantics later on.
>
> I think the proposal has low enough complexity and potential benefits
> to be worthwhile.
>
> =A0
>
> *From:*QUIC <quic-bounces@ietf.org> *On Behalf Of *Mikkel Fahn=F8e J=F8=
rgensen
> *Sent:* den 30 oktober 2018 08:01
> *To:* Christian Huitema <huitema@huitema.net>; quic@ietf.org
> *Subject:* Re: Structuring the BKK spin bit discussion
>
> =A0
>
> In the Netflix case it just takes 16 connections by the same user, or
> less when multiple users originate from the sane IP range.. Is it
> really practical (and thus worthwhile) to hide probabilistically as in
> Huitemas PR?
>

Mikkel is correct, we may not want a purely random per connection
behavior, but rather something "random per destination". This would
better mimic the opt-out behavior of a privacy-sensitive endpoint, which
would always opt out when contacting a specific destination. If I had to
implement it, I would not use a PRNG, but rather something compute the
hash of a local secret and either the peer address or the peer name.
That way, the client would opt out for all 16 Netflix connections, or
for none of them.

-- Christian Huitema

--------------0B1BAC0CAFEE5A487D58DE70
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><br>
    </p>
    On 10/30/2018 4:55 AM, Marcus Ihlar wrote:<br>
    <blockquote type="cite"
cite="mid:HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0@HE1PR0701MB2393.eurprd07.prod.outlook.com">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
..shape {behavior:url(#default#VML);}
</style><![endif]-->
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;}
..MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US"
            lang="EN-US">Making it more difficult to differentiate
            explicit opt-out from random opt-out is likely useful even
            if it doesn’t help in the particular Netflix case.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US"
            lang="EN-US">Furthermore, just like Brian points out it is
            necessary to grease the bit if we want to change the bit
            semantics later on.
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US"
            lang="EN-US">I think the proposal has low enough complexity
            and potential benefits to be worthwhile.
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US"
            lang="EN-US"><o:p> </o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #E1E1E1
            1.0pt;padding:3.0pt 0cm 0cm 0cm">
            <p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span
                lang="EN-US"> QUIC <a class="moz-txt-link-rfc2396E" href="mailto:quic-bounces@ietf.org">&lt;quic-bounces@ietf.org&gt;</a>
                <b>On Behalf Of </b>Mikkel Fahnøe Jørgensen<br>
                <b>Sent:</b> den 30 oktober 2018 08:01<br>
                <b>To:</b> Christian Huitema
                <a class="moz-txt-link-rfc2396E" href="mailto:huitema@huitema.net">&lt;huitema@huitema.net&gt;</a>; <a class="moz-txt-link-abbreviated" href="mailto:quic@ietf.org">quic@ietf.org</a><br>
                <b>Subject:</b> Re: Structuring the BKK spin bit
                discussion<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
        <div id="compose-container">
          <div>
            <div>
              <div>
                <p class="MsoNormal">In the Netflix case it just takes
                  16 connections by the same user, or less when multiple
                  users originate from the sane IP range.. Is it really
                  practical (and thus worthwhile) to hide
                  probabilistically as in Huitemas PR?<br>
                </p>
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Mikkel is correct, we may not want a purely random per connection
    behavior, but rather something "random per destination". This would
    better mimic the opt-out behavior of a privacy-sensitive endpoint,
    which would always opt out when contacting a specific destination.
    If I had to implement it, I would not use a PRNG, but rather
    something compute the hash of a local secret and either the peer
    address or the peer name. That way, the client would opt out for all
    16 Netflix connections, or for none of them.<br>
    <br>
    -- Christian Huitema<br>
  </body>
</html>

--------------0B1BAC0CAFEE5A487D58DE70--


From nobody Tue Oct 30 12:19:05 2018
Return-Path: <fielding@gbiv.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 BDDF2130DCF for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 12:19:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gbiv.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 wlFu-XWpFxmo for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 12:19:01 -0700 (PDT)
Received: from bonobo.maple.relay.mailchannels.net (bonobo.maple.relay.mailchannels.net [23.83.214.22]) (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 885EA130DC0 for <quic@ietf.org>; Tue, 30 Oct 2018 12:19:01 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|fielding@gbiv.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 983D05E3065; Tue, 30 Oct 2018 19:19:00 +0000 (UTC)
Received: from pdx1-sub0-mail-a14.g.dreamhost.com (unknown [100.96.19.78]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 4CA9F5E0D22; Tue, 30 Oct 2018 19:19:00 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|fielding@gbiv.com
Received: from pdx1-sub0-mail-a14.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.16.2); Tue, 30 Oct 2018 19:19:00 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|fielding@gbiv.com
X-MailChannels-Auth-Id: dreamhost
X-Society-Invention: 1134f49d4f030edf_1540927140452_2864324956
X-MC-Loop-Signature: 1540927140452:1571239916
X-MC-Ingress-Time: 1540927140452
Received: from pdx1-sub0-mail-a14.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a14.g.dreamhost.com (Postfix) with ESMTP id 01EDF7F1F2; Tue, 30 Oct 2018 12:19:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=wzfI4YIkH2upIcbCepU286UWRsk=; b=raw33y1QeFRdGVhswW0i1kwc9S/F 99PGRiicnhO/tcKbfoJY+cC0hJD/wkXFx8+3G2AFjkx+MjgT7lObSJqka3/mwDx3 E+Q/86CkmzZDCxCXs0owIcGK8sYC2vpCi39YN7S6XcJUupFIYf9dSUPScJyGJ8vV 5VmGamC2wikrGwk=
Received: from [192.168.1.5] (ip68-228-64-138.oc.oc.cox.net [68.228.64.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by pdx1-sub0-mail-a14.g.dreamhost.com (Postfix) with ESMTPSA id D9D407F962; Tue, 30 Oct 2018 12:18:58 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: Identifying our deliverables
X-DH-BACKEND: pdx1-sub0-mail-a14
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <578BB4EC-421E-4B21-AA14-B545A41754C8@mnot.net>
Date: Tue, 30 Oct 2018 12:18:57 -0700
Cc: IETF QUIC WG <quic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <873C0B44-EE49-4CCF-97A2-E71DB43298E2@gbiv.com>
References: <578BB4EC-421E-4B21-AA14-B545A41754C8@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3445.9.1)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedtkedriedtgdduvdduucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepfdftohihucfvrdcuhfhivghlughinhhgfdcuoehfihgvlhguihhnghesghgsihhvrdgtohhmqeenucffohhmrghinhephhhtthhpqdhovhgvrhdqqhhuihgtsghinhguihhnghhqphgrtghkvghttgdrihhtpdhhthhtphdvughiugdqqdhsohhpvghophhlvghunhguvghrshhtrghnughithhsshgvphgrrhgrthhiohhnfhhrohhmqhhuihgtrdgrshenucfkphepieekrddvvdekrdeigedrudefkeenucfrrghrrghmpehmohguvgepshhmthhppdhhvghloheplgduledvrdduieekrddurdehngdpihhnvghtpeeikedrvddvkedrieegrddufeekpdhrvghtuhhrnhdqphgrthhhpedftfhohicuvfdrucfhihgvlhguihhnghdfuceofhhivghlughinhhgsehgsghivhdrtghomheqpdhmrghilhhfrhhomhepfhhivghlughinhhgsehgsghivhdrtghomhdpnhhrtghpthhtohepqhhuihgtsehivghtfhdrohhrghenucevlhhushhtvghrufhiiigvpedt
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Ha_aWHy3JTqjjqJu3sFJpqO7ZEE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 19:19:04 -0000

> On Oct 27, 2018, at 5:30 PM, Mark Nottingham <mnot@mnot.net> wrote:
>=20
> You might recall that we've previously talked about renaming our =
deliverables to clarify their relationship to the input documents =
(sometimes referred to as "gQUIC vs iQUIC").
>=20
> After a fair amount of discussion with various folks, it seems like =
there's confidence that calling our core deliverable just "QUIC" will =
work, since Google's variant will fade out of use if we succeed, and =
there aren't any good alternatives; our best candidate was "QUIC/2", but =
it was pointed out that this additional level of versioning (since we =
already have a wire version) will cause yet more confusion.
>=20
> However, in those discussions, a related concern was identified; =
confusion between QUIC-the-transport-protocol, and =
QUIC-the-HTTP-binding. I and others have seen a number of folks not =
closely involved in this work conflating the two, even though they're =
now separate things.
>=20
> To address this, I'd like to suggest that -- after coordination with =
the HTTP WG -- we rename our the HTTP document to "HTTP/3", and using =
the final ALPN token "h3". Doing so clearly identifies it as another =
binding of HTTP semantics to the wire protocol -- just as HTTP/2 did -- =
so people understand its separation from QUIC.
>=20
> As part of that discussion, I'd suggest that we formalise that its =
maintenance (as well as that of QPACK) pass off to the HTTP WG once =
we've published it.
>=20
> I've talked about this with a number of folks. The only concerns I've =
heard so far are:
>=20
> a) That QUIC isn't yet proven. That's true, but the name won't be =
formalised or used on the wire until the RFC is published, so we have a =
good amount of time to back away. Even then, if it fails in the market, =
we can always skip to HTTP/4 one day, if we need to.=20
>=20
> b) That discussing naming is a distraction from our technical work. I =
agree with the concern overall, but we have a responsibility to =
communicate clearly with external developers and users, so I'd like to =
have a *limited* discussion about this. Please, don't bike shed.
>=20
> *Chair hat*=20
>=20
> We plan on reserving a very small period of time to discuss this in =
Bangkok; barring serious objections (of which "what about this name that =
I like instead?" is not one), we'll bring it up with the HTTP WG in =
Bangkok as well.

FWIW, I don't have a problem with calling a product of the HTTP WG some =
form of h3,
with the implication that we are working on the next version of HTTP and =
that it will
work on top of QUIC.  I have a bit of a problem with assuming that h3 =
product will be
the current HTTP-over-QUIC binding, QPACK, etc.  It's a reasonable =
option to work upon.

....Roy


From nobody Tue Oct 30 12:22:48 2018
Return-Path: <mikkelfj@gmail.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 25B9B130DCF for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 12:22:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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_PASS=-0.001, UNPARSEABLE_RELAY=0.001] 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 QvWer0VyoYs0 for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 12:22:44 -0700 (PDT)
Received: from mail-it1-x131.google.com (mail-it1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (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 A9F96130DCB for <quic@ietf.org>; Tue, 30 Oct 2018 12:22:44 -0700 (PDT)
Received: by mail-it1-x131.google.com with SMTP id d6so9535937itl.4 for <quic@ietf.org>; Tue, 30 Oct 2018 12:22:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=SUs7cTOptSDWeoZgG0xgZPU68wch0M0QbmcRfYnkulg=; b=p8FhCyOCnK2Zs3koxDh6DuIBz+qB8BABm7/QLYV8L/Cp4wJIRG2VcXElkiI9NwoS19 jZfXupSiT1hMbF5nmADKCVCw2e4OejvW3taRcd1893r+WY+WcRVSGU97gAXKX8vpQMjx 7sBh3cKZYT/s00utxlJKJR+dK7bWPDT22Vsi280bTEu6AqxmwezLE5u1M6nVOrQ60L7N hoWfDafE2AAUqw1oUOPj7etFZOg9+t0ZnocNeY2cUShuVDOIvRsZHbW/AEGF/8yWxkgX GlEq7hmU9HEoZkOfYLQLg4AxUPyd5MQpodVkalMsPNQuvX8RqfR9Rd9ACNM2yuP7icrV aX0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=SUs7cTOptSDWeoZgG0xgZPU68wch0M0QbmcRfYnkulg=; b=SQdLeafAqbXLxZtg9UxNRn8wMCrUkTf6RWVjozb4kdYUA/OTnH7eVIqICiIQNQ9Tci j0+zxhufuGp69s2xqdMPP4tpIWSHoagG/9pBPkljw4aPNyFm2jyZNUVYYEaD7PiF5wXg mQ0NOl935EdNxHwu0+0wXwwVeFaTqopjpFTV26PIKmlauFCOdvHCyKxEruvBWT4cc+4q bhh3sp7vDBTENvaeYqT7efcBKkfdAu3888Xmnm5ycZ70i/PPcf0dLI6IBKM/O0UL9h3X LTlA7tC42SxKZ2UK9XehnkzRJ28b4CfrdHB/CNHVLyRkjF8xBQwJgDkSzVAfhNu82CvC o6Sw==
X-Gm-Message-State: AGRZ1gJm0Hb5XJLhvtf51AbLRNzJTy/Q18t9kTl0ltrLMhnCf3yky9mt 0kt1UQpKOpYYC+QrQAi4Vqd9cAXrQgmqjHqJMM0=
X-Google-Smtp-Source: AJdET5duyTuc4+clvg0kHK8ouAB/5J1tmwqZSmjafmhGuXGgMewGJrOLaH23W62LQrkns1DYkY+sA4YfxfmL3uOI4YY=
X-Received: by 2002:a05:660c:342:: with SMTP id b2mr58806itl.167.1540927363964;  Tue, 30 Oct 2018 12:22:43 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 30 Oct 2018 12:22:43 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <873C0B44-EE49-4CCF-97A2-E71DB43298E2@gbiv.com>
References: <578BB4EC-421E-4B21-AA14-B545A41754C8@mnot.net> <873C0B44-EE49-4CCF-97A2-E71DB43298E2@gbiv.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Tue, 30 Oct 2018 12:22:43 -0700
Message-ID: <CAN1APddyyjPcUOoOE5AzyH1xzJzbS2HQ=PWHn-NuO6Xj3rX6KA@mail.gmail.com>
Subject: Re: Identifying our deliverables
To: "Roy T. Fielding" <fielding@gbiv.com>, Mark Nottingham <mnot@mnot.net>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002764f20579771ce9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/uCYVC3Srj0-StmRtoWs7bkyxOI4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 19:22:46 -0000

--0000000000002764f20579771ce9
Content-Type: text/plain; charset="UTF-8"

On 30 October 2018 at 20.19.26, Roy T. Fielding (fielding@gbiv.com) wrote:

 I have a bit of a problem with assuming that h3 product will be
the current HTTP-over-QUIC binding, QPACK, etc. It's a reasonable option to
work upon.


It could be h3.alpha

--0000000000002764f20579771ce9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">On 30 October 2018 a=
t 20.19.26, Roy T. Fielding (<a href=3D"mailto:fielding@gbiv.com">fielding@=
gbiv.com</a>) wrote:</div><div id=3D"bloop_customfont" style=3D"font-family=
:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-heigh=
t:auto"><br></div> <div><blockquote type=3D"cite" class=3D"clean_bq" style=
=3D"font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-varia=
nt-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;te=
xt-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-=
decoration:none"><span><div><span style=3D"color:rgb(0,0,0);font-family:&qu=
ot;helvetica Neue&quot;,helvetica;font-size:14px;font-style:normal;font-var=
iant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;=
text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;bac=
kground-color:rgb(255,255,255);text-decoration:none;float:none;display:inli=
ne!important"><span class=3D"Apple-converted-space">=C2=A0</span>I have a b=
it of a problem with assuming that h3 product will be<span class=3D"Apple-c=
onverted-space">=C2=A0</span></span><br style=3D"color:rgb(0,0,0);font-fami=
ly:&quot;helvetica Neue&quot;,helvetica;font-size:14px;font-style:normal;fo=
nt-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:=
start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0=
px;text-decoration:none"><span style=3D"color:rgb(0,0,0);font-family:&quot;=
helvetica Neue&quot;,helvetica;font-size:14px;font-style:normal;font-varian=
t-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;tex=
t-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;backgr=
ound-color:rgb(255,255,255);text-decoration:none;float:none;display:inline!=
important">the current HTTP-over-QUIC binding, QPACK, etc. It&#39;s a reaso=
nable option to work upon.<span class=3D"Apple-converted-space">=C2=A0</spa=
n></span></div></span></blockquote></div><p><br></p><p>It could be h3.alpha=
</p><div></div></body></html>

--0000000000002764f20579771ce9--


From nobody Tue Oct 30 13:37:29 2018
Return-Path: <jri.ietf@gmail.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 1F14C130DDD for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 13:37:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-0.001] 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 nWnvbuQtBwQl for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 13:37:09 -0700 (PDT)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 DB77C130DEA for <quic@ietf.org>; Tue, 30 Oct 2018 13:37:08 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id d7-v6so9972756lfi.2 for <quic@ietf.org>; Tue, 30 Oct 2018 13:37:08 -0700 (PDT)
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=fJIvwADPf+gyh2to0g3Zyi/Kap6v5X83j9DUI9YyQ/Y=; b=bMakm5q/TrJw6Q1hlob8kvUxW12rcH12pBi0QuzNItGRTT0px89glgg8mJrYOMvbNL rhGe55r30G0LeFRwhfjdVVn+0fgddff0D4FmqJc9k9grCG1aYNiZrAYtWLCWAOnpgyga 6mdIHL9chJymyeE+0vdFOzkkwNRXZ25sAhR8CJKkJYHkKOHH6uDluGnV2joXyWEgvXqj KE9FlcA5SVe37z2OC8cX/898jsM69+M4I3ktK0B2dCXhKowh30twySrTpji34s+z9Ttc mU5ZCs/fqXWY7yuXHxYK7GPmaeXIudafXwuI7Mm3+O/4YSydX96asDxI8InlnAUUdJZQ IWpQ==
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=fJIvwADPf+gyh2to0g3Zyi/Kap6v5X83j9DUI9YyQ/Y=; b=fqYCYsZwBrGp2t32iBIjosv6mw+ulYHHA7REwz3Ix05L2LF5z3ynG/OrUfr09pZwzN Jlv+H4T6az8ZRY6OaYfEYjrcCmJgTht7kPvVyTCooYTi5LpH16JRryWnBZ1vfLuSKAx4 vzj9ROpjnKewtx1UoZB3Ka+zXSo3BJnHgiGbI/e7s2PK6035/jUhv/hpb+V92LtaILKO V4K2Qw5WzeLX60UUbSw4Ve2rkrMRRuwjW92tKo3nXd72sQJZ3sMrYXBceAyAnDSMv/uf W5l/AO7dxKzBmA6SVzFZpASflDAovyQmMUAxUf7WzEpUePOiba1ziBIa4L7q0C08h0Qw ZGvw==
X-Gm-Message-State: AGRZ1gITGxPsY9Cd3JV9J2Yq5hVZii9WlsbfHNuGPZyPZXRtjV2KiBc7 KpddkNto5TiG/UNE/S7+73kircJUh3EfQQaEg6GUVw==
X-Google-Smtp-Source: AJdET5clTURRV6oN/p+vHb7Q+DUJzR3h1L1rSI3Woqn3VFF0hxnxnoLXKb+/PFHt9scKWIP/PNtSKTOEgrD/JRg8ZOo=
X-Received: by 2002:a19:2395:: with SMTP id j143mr115502lfj.107.1540931826940;  Tue, 30 Oct 2018 13:37:06 -0700 (PDT)
MIME-Version: 1.0
References: <578BB4EC-421E-4B21-AA14-B545A41754C8@mnot.net> <873C0B44-EE49-4CCF-97A2-E71DB43298E2@gbiv.com>
In-Reply-To: <873C0B44-EE49-4CCF-97A2-E71DB43298E2@gbiv.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Tue, 30 Oct 2018 13:36:55 -0700
Message-ID: <CACpbDcfJ=+ZCvmpF1zjXbPx36vnvfq6YHKu5_9supf9iZx26Zg@mail.gmail.com>
Subject: Re: Identifying our deliverables
To: fielding@gbiv.com
Cc: Mark Nottingham <mnot@mnot.net>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002b00cf05797826a5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/8MIA-sDPRUNA9uJk2Vk7hVpHslI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 20:37:22 -0000

--0000000000002b00cf05797826a5
Content-Type: text/plain; charset="UTF-8"

>
> FWIW, I don't have a problem with calling a product of the HTTP WG some
> form of h3,
> with the implication that we are working on the next version of HTTP and
> that it will

work on top of QUIC.


That sounds like HTTP/4 to me :-)

--0000000000002b00cf05797826a5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
FWIW, I don&#39;t have a problem with calling a product of the HTTP WG some=
 form of h3,<br>
with the implication that we are working on the next version of HTTP and th=
at it will=C2=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">work on top of =
QUIC.=C2=A0 </blockquote><div><br></div><div>That sounds like HTTP/4 to me =
:-)</div><div><br></div></div></div>

--0000000000002b00cf05797826a5--


From nobody Tue Oct 30 15:55:46 2018
Return-Path: <martin.thomson@gmail.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 C4DBD127133 for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 15:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 K4P6PD1-kgaS for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 15:55:43 -0700 (PDT)
Received: from mail-ot1-x336.google.com (mail-ot1-x336.google.com [IPv6:2607:f8b0:4864:20::336]) (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 E78AB124BE5 for <quic@ietf.org>; Tue, 30 Oct 2018 15:55:42 -0700 (PDT)
Received: by mail-ot1-x336.google.com with SMTP id p23so12785641otf.11 for <quic@ietf.org>; Tue, 30 Oct 2018 15:55:42 -0700 (PDT)
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:content-transfer-encoding; bh=OolWPUeB3OyXVME6fj3XOAkoB+SmIiTxaKvRoyE4whI=; b=R9AgJ5LF9bUyy73a6m3mFlhZLbsER1PRCaZQf8/U47mEQmvA6PkR+TzwufLumP+n7J 6hpX8VwM84UFXViBM6hLmE+Wuze3JTD2vzwBf156Hb8IPsa5HT2huSgSp7d2a70k3Y4j p6RS5zLeIdbVZE7jlD9zxhQyayp7OFRo1K+XI3YGllo6T0/qpTI1QrSKVPwvK1svvvim JuLfIVB+D4GEBmpltW9FhmG/qfWp8LalVszVXSzdEfv7iL4KzhLfoK3X+LxlLal7OXUo Pm4Ae3Yu5dfybgW67TsozIz0XFDYqPmFKVxaQFLS2EouPBYJjXNYlKMVhvayMuxKuSFE gO9A==
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:content-transfer-encoding; bh=OolWPUeB3OyXVME6fj3XOAkoB+SmIiTxaKvRoyE4whI=; b=qvqrQIFwKilphPQ9sqnxw7C0ybKPpd1WHJZYXf+qXDSMoHqSmlcdvEa97Xc7i52rg/ kgCAzSnWc7OEKUG85LJ51zihkotRKJnWkCEP4x8QgNO3MXBSLYpR+eQi77kOSq0/mDxA 0m0upXEguJT6lUfTP4k6+z//lYFdzJEtj0xsZYYiWYtRtt815p8mtSEscgRlfRr3K5vg YqiUV/+kqyycaqxmtYrNHYgaVetyK93ZlApyaA83LfksUAIMH8I+kjQKqG+DZ1DjQw9+ 8hInOQUYLDs37ipWi5VOn4Bpwqtht6dUr5aMFSA3mCixlIh5ZWYO8IZ3/n5FHvZoNYZ3 PHHg==
X-Gm-Message-State: AGRZ1gKngtoP1/5Mdyqj7eCvUIS8meiKFT/B/U50d2BxXXT8tOz7MMFJ am/3aFDmLKjWUOKw55jZDsPoQNLuCwJcTT8DlD6+e+ss
X-Google-Smtp-Source: AJdET5cXEKA5LfCyhZIyrzj8KRNWJ+ssyYslQL4Gdm+OoMS5c8+LPTOsU5KkOZ+IIaTEorH/oyrMzD8k/SWh5IbjoVo=
X-Received: by 2002:a9d:6101:: with SMTP id i1mr439102otj.310.1540940142225; Tue, 30 Oct 2018 15:55:42 -0700 (PDT)
MIME-Version: 1.0
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com> <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch> <a088c411-1acc-8b0f-fc1b-8c79ce6f1cd7@huitema.net> <DB6PR10MB1766E6B29792BB4401FF38F0ACCC0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <65907d96-a525-dcd0-39cd-678c52d26ab6@huitema.net>
In-Reply-To: <65907d96-a525-dcd0-39cd-678c52d26ab6@huitema.net>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 31 Oct 2018 09:55:33 +1100
Message-ID: <CABkgnnVCveXr2GUsx2ZyKNf08VaCh+Ts-T=5wD3_-8Pqk2xRTQ@mail.gmail.com>
Subject: Re: Structuring the BKK spin bit discussion
To: Christian Huitema <huitema@huitema.net>
Cc: Marcus Ihlar <marcus.ihlar@ericsson.com>,  =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>,  QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Ss7PDIKC4p8_kcEaiWKxR6Dwr6g>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 22:55:45 -0000

On Wed, Oct 31, 2018 at 5:42 AM Christian Huitema <huitema@huitema.net> wro=
te:
> Mikkel is correct, we may not want a purely random per connection behavio=
r, but rather something "random per destination". This would better mimic t=
he opt-out behavior of a privacy-sensitive endpoint, which would always opt=
 out when contacting a specific destination. If I had to implement it, I wo=
uld not use a PRNG, but rather something compute the hash of a local secret=
 and either the peer address or the peer name. That way, the client would o=
pt out for all 16 Netflix connections, or for none of them.

Or are we looking for random per-path?

That notion would seem to tilt the balance more in favour of the
"discretionary" option over the "negotiated" one on the basis that
spinning/not doesn't become a linkability consideration.


From nobody Tue Oct 30 16:02:25 2018
Return-Path: <martin.thomson@gmail.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 298EE130E6E for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 16:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 2wJYtbgTT5Y9 for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 16:02:14 -0700 (PDT)
Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) (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 400A5130E11 for <quic@ietf.org>; Tue, 30 Oct 2018 16:02:12 -0700 (PDT)
Received: by mail-oi1-x231.google.com with SMTP id i10-v6so12005435oik.8 for <quic@ietf.org>; Tue, 30 Oct 2018 16:02:12 -0700 (PDT)
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;  bh=TwHbIF4CDvWIon6NrXRkb7Emt8gvC1U/QWRSDqjoi9Y=; b=TK1ieq9/F+LX92zuIShoEKok3OAzEKpW44Db0+DMeiDaTTU6cyU+CpCuMwMWtTNjwL inGkZNAb5c5UtuQblS3Zh5B9ynLfSbrLtyxWWPNmOxo9xbAO99fSgsK4C0o9ivIRqm0b SCgEnc14luCOwBczfcyKaAzU0Q5Vkfs7Ocelv0PWfG0Lm3MkR+fnnLJbiGHXg9u+SAXf ViJB//dlKOEuSOxg1gOadrv6haQc5+6b8tHwLNv3SuPeNzqjoyqZK/vZcfCFGBgeRZqH p0PEf6o7lWcmK2ulAKKKkeJJtzhRmSoxKICYVBVUKHE7mM36Ti1k1csHzBjoI9OXX66D tasA==
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; bh=TwHbIF4CDvWIon6NrXRkb7Emt8gvC1U/QWRSDqjoi9Y=; b=E56OACgQYEXDXxS8r14xF77nuSP2dDTxkel741Rjyu5NoO2sbtQQfSP/kxeroq4mGi XMuEwyYPKgH4T/LeexAU7Lo7M6JP0bM/66gLdlHMycZE6UOMPK10WoOqlmA8EQ81bOIA 5R/SLR8e37txSnr0KYjk5vuqh1KCGDzEt554NU4mXAhb3PZyZgX4/Bb4rFgs08XR7s83 MtPv+rRBkxekpBrAfAcHk1gfbNxpxynMk/zMI86kejj9yex7HWGnSQPiPHXfEtLL4Ha0 nE1j2+jDpXFcTvs5yN5ywjSTKzJLkhboQz7LvOWZkVU8eNA1SiVywe09s9DomUq7esTP irUw==
X-Gm-Message-State: AGRZ1gJwUjIgG5GiH9Pppu9Ln29CN/V1SB/itF5Au4P8OHMh0YJHZK9r PaQhl3twl9PtLjNw2A+N9MctYFmSCc42HD4T/cNJw85U
X-Google-Smtp-Source: AJdET5eSkEBGXUB8cx5S+a7xxwm5c0cmObd0usd5pnTNIDUgKSWGcl4wzzMEN0znHtEZ4c8EN2Jdi0Hf3Yfb1GBB5RU=
X-Received: by 2002:aca:5407:: with SMTP id i7-v6mr415845oib.344.1540940531344;  Tue, 30 Oct 2018 16:02:11 -0700 (PDT)
MIME-Version: 1.0
References: <CABkgnnXwmvCGcukYnQHU4sfAZFR24RT31O+BVqqnkZwB3Cp_Kw@mail.gmail.com> <20181030130524.GA10485@ubuntu-dmitri>
In-Reply-To: <20181030130524.GA10485@ubuntu-dmitri>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 31 Oct 2018 10:02:02 +1100
Message-ID: <CABkgnnV3S6DJ=mdCiAasrFz_FaJnfRyy6BEqBpRJuvbDk8O3kg@mail.gmail.com>
Subject: Re: Frame changes landing soon
To: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ybRypjHMpZiPZklNwXer9p3uKZw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 23:02:24 -0000

On Wed, Oct 31, 2018 at 12:05 AM Dmitri Tikhonov
<dtikhonov@litespeedtech.com> wrote:
> On Tue, Oct 30, 2018 at 12:07:46PM +1100, Martin Thomson wrote:
> > My current plan is to merge both of these in the next 24 hours.  That
> > will allow me to renumber frame types so that they start to make more
> > sense..
>
> What is the reason for renumbering the frames?  (Not that I am
> against it -- simply curious.)  Is it to make the types easier to
> remember in order to facilitate eyeballing hex dumps?  Or is there
> some other goal?

Just tidiness.  It would be good to have the document ordered in a
sensible fashion, and to be consistent with the frame numbers.  Over
time, as we've added and removed frames, we didn't renumber, and so we
have them all over.  And, as you say, changing the numbers isn't
particularly difficult.


From nobody Tue Oct 30 16:03:01 2018
Return-Path: <daniel@haxx.se>
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 A0BBF130E72 for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 16:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 nbm-1q9WFf9A for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 16:02:50 -0700 (PDT)
Received: from giant.haxx.se (www.haxx.se [IPv6:2a00:1a28:1200:9::2]) (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 DB499130E52 for <quic@ietf.org>; Tue, 30 Oct 2018 16:02:48 -0700 (PDT)
Received: from giant.haxx.se (mail [127.0.0.1]) by giant.haxx.se (8.15.2/8.15.2/Debian-4) with ESMTPS id w9UN2iMe020924 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 31 Oct 2018 00:02:44 +0100
Received: from localhost (dast@localhost) by giant.haxx.se (8.15.2/8.15.2/Submit) with ESMTP id w9UN2hwC020920; Wed, 31 Oct 2018 00:02:43 +0100
X-Authentication-Warning: giant.haxx.se: dast owned process doing -bs
Date: Wed, 31 Oct 2018 00:02:43 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Mark Nottingham <mnot@mnot.net>
cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Identifying our deliverables
In-Reply-To: <578BB4EC-421E-4B21-AA14-B545A41754C8@mnot.net>
Message-ID: <alpine.DEB.2.20.1810310001540.21030@tvnag.unkk.fr>
References: <578BB4EC-421E-4B21-AA14-B545A41754C8@mnot.net>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/zAKc8fsVsiBQ0wB_A6SOltOGwdk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 23:03:00 -0000

On Sun, 28 Oct 2018, Mark Nottingham wrote:

> To address this, I'd like to suggest that -- after coordination with the 
> HTTP WG -- we rename our the HTTP document to "HTTP/3", and using the final 
> ALPN token "h3". Doing so clearly identifies it as another binding of HTTP 
> semantics to the wire protocol -- just as HTTP/2 did -- so people understand 
> its separation from QUIC.

I like it!

-- 

  / daniel.haxx.se


From nobody Tue Oct 30 16:52:33 2018
Return-Path: <jri.ietf@gmail.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 00A87130DC7 for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 16:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-0.001] 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 nts72xjPDQvv for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 16:52:30 -0700 (PDT)
Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (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 51C3F1277CC for <quic@ietf.org>; Tue, 30 Oct 2018 16:52:30 -0700 (PDT)
Received: by mail-lf1-x133.google.com with SMTP id p17so3833034lfh.4 for <quic@ietf.org>; Tue, 30 Oct 2018 16:52:30 -0700 (PDT)
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=uJRylu7yfNIH1qajDRBOa8OlbQWsBacCcbkjqJsDIrI=; b=ZsQlLY+Tc9JTLK+8Q22e7CYaNCcDYRyjvdarbdSXDvoTnQchXJuc70jWoWA17E/AnF ULUdAzN3q+gb9s6lhg1NgFNKTmEJFSbe7ZBsSl0O/lGUZP/0ART5qcaNX14pg/pajf4y rITqSbz2s35erpDiEseTxkKEA3QLaR4Gk0cHy64RH5CpNILTRG9Fci4zt222pCtNC52H xO5jHhmVz0HTl+t1E1NcPAkQ9sxRuvh0mmOM/dOJV7l0ZN0lG1109JAUlP8WoeQ6o8gh PpeeT2X8vHakSM0MUwN2E2zszXljgLP7ztkZdnfXkqHSgY4zRvnLjYLUnWPZQgWzN9FG mpXQ==
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=uJRylu7yfNIH1qajDRBOa8OlbQWsBacCcbkjqJsDIrI=; b=nVJW9i1ZSINq995f6lTFafRcCtJBDmePf908dcVcPaNc+Kh070N5qMkBEG/lhTFveV 7HkcDXh72HJSEXn9cKI5SctfTey7JEvirQfHvf+y1PqCE+fjeV9bbh5YPvu5/kJRKy0D WvkB7rOb0+td+OW6G+6VwlfFElXIWuHgk+/GXvHoOpiztZpC+ymAhUF2i1ucINGDUuIi CoVg13cgzYkN2rDJDVf7pU9VB7PkeiDtqacbtTHHiWBzc26bBcG9rdLM/xXxvyLmBn9A U2ntivacWc55xLHiXF+TkvJvbi3qVpYdBILDhWSqFU5Cnu5/qbJE55eJlkw3caLLU2aW MS7w==
X-Gm-Message-State: AGRZ1gLi0+kKZKGe52j4NNEa4SkKYB3LMpXBuEpvqVTQcDhkZZp3kssI bP3eot8Hu9TaonkDuieeiiR0idn2KNCz5P/YxEyeig==
X-Google-Smtp-Source: AJdET5eZK7IlX88Pt+mPvwrij+7+EixS8soOu6zVuop93jk2rAWxkHDf/66zUfBMLyQlLkGD33orzCMGdVckoQas1is=
X-Received: by 2002:a19:2395:: with SMTP id j143mr390388lfj.107.1540943548322;  Tue, 30 Oct 2018 16:52:28 -0700 (PDT)
MIME-Version: 1.0
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com> <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch> <a088c411-1acc-8b0f-fc1b-8c79ce6f1cd7@huitema.net> <DB6PR10MB1766E6B29792BB4401FF38F0ACCC0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <65907d96-a525-dcd0-39cd-678c52d26ab6@huitema.net> <CABkgnnVCveXr2GUsx2ZyKNf08VaCh+Ts-T=5wD3_-8Pqk2xRTQ@mail.gmail.com>
In-Reply-To: <CABkgnnVCveXr2GUsx2ZyKNf08VaCh+Ts-T=5wD3_-8Pqk2xRTQ@mail.gmail.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Tue, 30 Oct 2018 16:52:17 -0700
Message-ID: <CACpbDccP7zw6yUyMs0iyAzByBDjprsoBbwey3c0t7wXEddvrvA@mail.gmail.com>
Subject: Re: Structuring the BKK spin bit discussion
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Christian Huitema <huitema@huitema.net>, =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>,  Marcus Ihlar <marcus.ihlar@ericsson.com>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d118a205797ae0a9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/hvKJCFpjrA8i4k7J4lSbl8yHdbE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 30 Oct 2018 23:52:32 -0000

--000000000000d118a205797ae0a9
Content-Type: text/plain; charset="UTF-8"

On Tue, Oct 30, 2018 at 3:55 PM Martin Thomson <martin.thomson@gmail.com>
wrote:

> On Wed, Oct 31, 2018 at 5:42 AM Christian Huitema <huitema@huitema.net>
> wrote:
> > Mikkel is correct, we may not want a purely random per connection
> behavior, but rather something "random per destination". This would better
> mimic the opt-out behavior of a privacy-sensitive endpoint, which would
> always opt out when contacting a specific destination. If I had to
> implement it, I would not use a PRNG, but rather something compute the hash
> of a local secret and either the peer address or the peer name. That way,
> the client would opt out for all 16 Netflix connections, or for none of
> them.
>
> Or are we looking for random per-path?
>
> That notion would seem to tilt the balance more in favour of the
> "discretionary" option over the "negotiated" one on the basis that
> spinning/not doesn't become a linkability consideration.
>

Yes, per path makes sense to me. I think the linkability concern here is
weak, but it doesn't hurt any to do this per path.

--000000000000d118a205797ae0a9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Oct 30=
, 2018 at 3:55 PM Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gmail=
.com">martin.thomson@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">On Wed, Oct 31, 2018 at 5:42 AM Christian Huitema &lt;<a href=3D=
"mailto:huitema@huitema.net" target=3D"_blank">huitema@huitema.net</a>&gt; =
wrote:<br>
&gt; Mikkel is correct, we may not want a purely random per connection beha=
vior, but rather something &quot;random per destination&quot;. This would b=
etter mimic the opt-out behavior of a privacy-sensitive endpoint, which wou=
ld always opt out when contacting a specific destination. If I had to imple=
ment it, I would not use a PRNG, but rather something compute the hash of a=
 local secret and either the peer address or the peer name. That way, the c=
lient would opt out for all 16 Netflix connections, or for none of them.<br=
>
<br>
Or are we looking for random per-path?<br>
<br>
That notion would seem to tilt the balance more in favour of the<br>
&quot;discretionary&quot; option over the &quot;negotiated&quot; one on the=
 basis that<br>
spinning/not doesn&#39;t become a linkability consideration.<br></blockquot=
e><div><br></div><div>Yes, per path makes sense=C2=A0to me. I think the lin=
kability concern here is weak, but it doesn&#39;t hurt any to do this per p=
ath.</div></div></div>

--000000000000d118a205797ae0a9--


From nobody Tue Oct 30 17:05:32 2018
Return-Path: <mikkelfj@gmail.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 0A6FB1277CC for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 17:05:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level: 
X-Spam-Status: No, score=-0.998 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 l8mFsS9JrZDn for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 17:05:29 -0700 (PDT)
Received: from mail-it1-x130.google.com (mail-it1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (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 AA0F1130DC7 for <quic@ietf.org>; Tue, 30 Oct 2018 17:05:29 -0700 (PDT)
Received: by mail-it1-x130.google.com with SMTP id e74-v6so16014321ita.2 for <quic@ietf.org>; Tue, 30 Oct 2018 17:05:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=uHbUHM1vMvfBVz6+p6Y5TbQn4ane+bSQxv6gFDb+im0=; b=LBC0B5CvPkj7pUKnUXFzieOntkDMuUzjW2QHAP6EBsNSNo/m05zKpQ7K67ZpjuD/m0 oe5w77sI/jZCoOTlFM/vEH2uXtcD+4Gw9WmzZ4NOw4rWnyvtIjzaZCH4W1842dlKLURz ulJBNu0RnXzY7AqvWMpowRPnA/SNL2ZiN8ZXaPBqb6fKXUL5O7Eqn4PkKqxDgMwbheT8 tfpzeGitLMfJxPFS2LLK0HT2SguzMUWpGGpdP57JUfYbOV8lLJA6vO68aZKTj6PC7trE JClugw7T7jLHBnsxZh0eKrw6CgJNKgxHhuY8yHGhoMQo47/qXw+4JD1mdGQxwlu9Ph/y 8JMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=uHbUHM1vMvfBVz6+p6Y5TbQn4ane+bSQxv6gFDb+im0=; b=cZmMF6wG0Iak/8uENEZbbK7aTi+7WaWrbdia3JbbSbdIQYUf4usSNPYJdd1gSV0txa +DRVLAny69LfxdcUX5sc04nHiiZgUHJ+FnJpcERM7TPYpJq9ta9YNO1tSPhcLOvgsYuB ZVz/YJ45XC3HRjoWgnRlh6lKXLSnF5Lh0SOmu3C1OgrYPXWlqWCNrQXz0dBxc78e2VP6 jU0v60ZvaYzxdP4MqxwJS+LaZXxoJMrIQ7bSRIr82v4jk+ExkEV+NuIQ39RJeZS5eyyw zKhWfjMQKdSZWprlncExmhPRF0KoZ84XN0DWumwXWpDKGETq8oJSQ8LuhaAQjYiB/CJw dZ0A==
X-Gm-Message-State: AGRZ1gJ703PpjtpM7OPQicoj2GTz33K5EcIggG7BTo08gRPLMB5pCUaT hKevjWERDVEa/ZfoPCGuhxVqdb/BZH8tU8cOiT4=
X-Google-Smtp-Source: AJdET5eI5o6CsTVfSCgnXI1KZ/Dm94z8XxQeNYYAR1Mei1Aer01vqwGQtrnYiXCN4Oc9fGFFnx/05L4Yx9MlOFdIXyo=
X-Received: by 2002:a24:3088:: with SMTP id q130-v6mr589627itq.148.1540944329022;  Tue, 30 Oct 2018 17:05:29 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 30 Oct 2018 17:05:28 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CACpbDccP7zw6yUyMs0iyAzByBDjprsoBbwey3c0t7wXEddvrvA@mail.gmail.com>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com> <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch> <a088c411-1acc-8b0f-fc1b-8c79ce6f1cd7@huitema.net> <DB6PR10MB1766E6B29792BB4401FF38F0ACCC0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <65907d96-a525-dcd0-39cd-678c52d26ab6@huitema.net> <CABkgnnVCveXr2GUsx2ZyKNf08VaCh+Ts-T=5wD3_-8Pqk2xRTQ@mail.gmail.com> <CACpbDccP7zw6yUyMs0iyAzByBDjprsoBbwey3c0t7wXEddvrvA@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Tue, 30 Oct 2018 17:05:27 -0700
Message-ID: <CAN1APdcZAK6Kw0b+hB6Z1fZ4xWATmqYXzg--_qFLdKUq7E5zPg@mail.gmail.com>
Subject: Re: Structuring the BKK spin bit discussion
To: Jana Iyengar <jri.ietf@gmail.com>, Martin Thomson <martin.thomson@gmail.com>
Cc: Marcus Ihlar <marcus.ihlar@ericsson.com>, Christian Huitema <huitema@huitema.net>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000059a34a05797b0f3e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2uxft7S1NBnJWXZ5DOWyFMYnOYQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 00:05:31 -0000

--00000000000059a34a05797b0f3e
Content-Type: text/plain; charset="UTF-8"

This might overcomplicate things but a client could perhaps downsample the
spin bit by only changing phase every second time the server does, or other
harmonics. If this is done randomly it could hide some latency.


On 31 October 2018 at 00.52.29, Jana Iyengar (jri.ietf@gmail.com) wrote:

On Tue, Oct 30, 2018 at 3:55 PM Martin Thomson <martin.thomson@gmail.com>
wrote:

> On Wed, Oct 31, 2018 at 5:42 AM Christian Huitema <huitema@huitema.net>
> wrote:
> > Mikkel is correct, we may not want a purely random per connection
> behavior, but rather something "random per destination". This would better
> mimic the opt-out behavior of a privacy-sensitive endpoint, which would
> always opt out when contacting a specific destination. If I had to
> implement it, I would not use a PRNG, but rather something compute the hash
> of a local secret and either the peer address or the peer name. That way,
> the client would opt out for all 16 Netflix connections, or for none of
> them.
>
> Or are we looking for random per-path?
>
> That notion would seem to tilt the balance more in favour of the
> "discretionary" option over the "negotiated" one on the basis that
> spinning/not doesn't become a linkability consideration.
>

Yes, per path makes sense to me. I think the linkability concern here is
weak, but it doesn't hurt any to do this per path.

--00000000000059a34a05797b0f3e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">This might overcompl=
icate things but a client could perhaps downsample the spin bit by only cha=
nging phase every second time the server does, or other harmonics. If this =
is done randomly it could hide some latency.</div> <div id=3D"bloop_sign_15=
40944140993678080" class=3D"bloop_sign"><div style=3D"font-family:helvetica=
,arial;font-size:13px"><br></div></div> <br><p class=3D"airmail_on">On 31 O=
ctober 2018 at 00.52.29, Jana Iyengar (<a href=3D"mailto:jri.ietf@gmail.com=
">jri.ietf@gmail.com</a>) wrote:</p> <blockquote type=3D"cite" class=3D"cle=
an_bq"><span><div><div></div><div>


<title></title>


<div dir=3D"ltr">
<div class=3D"gmail_quote">
<div dir=3D"ltr">On Tue, Oct 30, 2018 at 3:55 PM Martin Thomson
&lt;<a href=3D"mailto:martin.thomson@gmail.com">martin.thomson@gmail.com</a=
>&gt;
wrote:<br></div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On
Wed, Oct 31, 2018 at 5:42 AM Christian Huitema &lt;<a href=3D"mailto:huitem=
a@huitema.net" target=3D"_blank">huitema@huitema.net</a>&gt; wrote:<br>
&gt; Mikkel is correct, we may not want a purely random per
connection behavior, but rather something &quot;random per destination&quot=
;.
This would better mimic the opt-out behavior of a privacy-sensitive
endpoint, which would always opt out when contacting a specific
destination. If I had to implement it, I would not use a PRNG, but
rather something compute the hash of a local secret and either the
peer address or the peer name. That way, the client would opt out
for all 16 Netflix connections, or for none of them.<br>
<br>
Or are we looking for random per-path?<br>
<br>
That notion would seem to tilt the balance more in favour of
the<br>
&quot;discretionary&quot; option over the &quot;negotiated&quot; one on the=
 basis
that<br>
spinning/not doesn&#39;t become a linkability
consideration.<br></blockquote>
<div><br></div>
<div>Yes, per path makes sense=C2=A0to me. I think the linkability
concern here is weak, but it doesn&#39;t hurt any to do this per
path.</div>
</div>
</div>


</div></div></span></blockquote></body></html>

--00000000000059a34a05797b0f3e--


From nobody Tue Oct 30 18:34:59 2018
Return-Path: <ianswett@google.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 239D2130DE9 for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 18:34:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.499
X-Spam-Level: 
X-Spam-Status: No, score=-17.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 iXn1M49BVZ-b for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 18:34:54 -0700 (PDT)
Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (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 61057130DD8 for <quic@ietf.org>; Tue, 30 Oct 2018 18:34:54 -0700 (PDT)
Received: by mail-wr1-x42b.google.com with SMTP id r10-v6so14666204wrv.6 for <quic@ietf.org>; Tue, 30 Oct 2018 18:34:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=o3nP+gVvuUqsAJGx7M278VJx0xJyMk51eHy0bl8JvJA=; b=jxYf3SuAkeaiQ2jbFJKzPrppJ36SYbCwWE57ccEWf/ItiEr3ezLD7pY1OtYAyNThc+ X2dalCF/W/quNyduagIRlwS00hMrtierprwKqb/jX4hDwmLlHit6uPH279KeB+pDFQIJ vHYTJnvy7FBl7FvEJdZ6aVRYJif/Fo4qPeH8PN1/X27C6oj9gc1vm0gn5Tbna9Qoozdq HFApuw96EcaRQaxmSg9dSpxlcvaGvyG6k+dPnlOunlCHCOe5WOJCVcADczAQ+t/Q3WVt DqGDn9yOpJ3RnVkeaBOxoZxJxC+TxXiUOxYisCnK9QLe3olXm646QDXz5EmlbcwVo40S zrEQ==
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=o3nP+gVvuUqsAJGx7M278VJx0xJyMk51eHy0bl8JvJA=; b=Hc105pdhNMeep0/Q9kBv421WcV6Q4HhRK+b2Rzy8Sr4hn92qBSa9FZ9P/VbqgWz28n eZc39wa0xDlx+Dh4nHwP9fRFGdlqh7WrvyLhNP8jnccn+R5PaqKBeiPHz/tg2pIVAiSA 4HhrWgMkq85uIr/c20mTpKqDhdNUqOhP4XygKDPQohnjIg4k5vm3jbailLkMZIpbDFly Ccv5HrNmdbtRG+vqjWvSgFfSLxZFgmr/M/WsaPkudxbtgpWDsfUCCkwyT8urZkNb4sLz tzBfoJvqK3p5YmFG/8bLQOFFtZvMPXRzP5tlH5nv7lbwM+njyMCSsoRJ8opoTldIcPXL ugjQ==
X-Gm-Message-State: AGRZ1gK0jiPI7ROnLanvcu2JmJVhW7f161FF97Oy1JV2YW7hLk1B7ikC XMywim/vohUiY4T2KFCkRT53Xq+cBWN7vEo8kRuS6A==
X-Google-Smtp-Source: AJdET5dN0fjpo2wH1DbqTXzMxHnDWKbH22mas17Wry22rROSSea4ivvB8/4U9o4ezwZBs+N1PyQJBX9ww/EDQu9Qse4=
X-Received: by 2002:adf:812a:: with SMTP id 39-v6mr811915wrm.84.1540949692646;  Tue, 30 Oct 2018 18:34:52 -0700 (PDT)
MIME-Version: 1.0
References: <CAO249yeMcawY6zZE-64QFO+L6NZhFLnvjXw9dnjn0qsqtKW9kw@mail.gmail.com>
In-Reply-To: <CAO249yeMcawY6zZE-64QFO+L6NZhFLnvjXw9dnjn0qsqtKW9kw@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Tue, 30 Oct 2018 21:34:39 -0400
Message-ID: <CAKcm_gP-CrgUYEU4Vjdeo2sjpsZvebE-NLXGAL97ckntVwvhOQ@mail.gmail.com>
Subject: Re: questions on draft-ietf-quic-recovery
To: nishida@sfc.wide.ad.jp
Cc: IETF QUIC WG <quic@ietf.org>, tcpm@ietf.org, Jana Iyengar <jri.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000000c6fe605797c4fcf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/n4i5xMmIxmBvnakWIqmBQHFY5ko>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 01:34:57 -0000

--0000000000000c6fe605797c4fcf
Content-Type: text/plain; charset="UTF-8"

Thanks for your careful reading, answers inline.
On Mon, Oct 29, 2018 at 1:03 PM Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
wrote:

> Hello,
>
> At Bangkok, TCPM WG will have a session to discuss loss recovery and
> congestion control mechanism in QUIC and TCP. (11/6 Tuesday
> 11:20-12:20)
> I really appreciate Ian and Jana for the efforts.
>
> I might overlook something as I couldn't follow up all discussion in
> QUIC, but I am thinking that it might be good if we could get some
> comments on the following questions.
> I have listed several questions on the value of some parameters, but
> it doesn't mean I disagree with these values. I just would like to
> check where these values came from.
> Hope this will be useful in some ways.
>
>
> Section 4:
>    QUIC supports both ack and timer for loss detection.
>    But, it's not very clear whether an implementation can choose one
> of them or it should implement both and can use both at the same time.
> Can it be clarified?
>

Yes, there's an open Issue to clarify this.
https://github.com/quicwg/base-drafts/issues/1212

The outstanding PR is quite old, but has some helpful clarifications in it,
so I'm intending to migrate the best parts to a new PR.  Suggestions(or
PRs) welcome.


> Section 4.1.1:
>    For RTT sampling, implementations will need to maintain the
> transmission time for each sending packets even if they support only
> ack-based method.
>    But, this requirement might be hard for tiny devices. Wouldn't it
> limit the applicability of QUIC?
>

Good question.  Assuming a ~1200 byte packet and a 4 byte timestamp, that's
<0.5% of the total storage overhead, assuming the data being sent is
reliable.  That doesn't seem like too much overhead to me, but one could
certainly store less granular information if they were really constrained.
ie: packet numbers X to X+N all contain a certain sequence of bytes and
were sent at approximately a single time.  I believe such a storage
approach would make it more similar to TCP metadata, but you likely know
better than I do.


>
>    "the largest newly acked packet" might be confusing. packet that
> acks the largest packet number?
>

 That's the largest packet that was acknowledged in the current ack frame
being processed.  I re-read the text and I'm not sure how to improve it, so
feel free to send a PR.

>
> Section 4.2.1:
>    TCP RACK's reo_wnd is aiming to be 1/4 RTT. Why QUIC uses 1/8 RTT?
>

I ran some experiments that indicated 1/4 RTT was a slight latency
regression for web applications and 1/8 RTT still had fewer spurious
retransmits than the dupack threshold loss detection.  I also presented
some reordering data at maprg in Montreal that indicated 1/8 RTT was
typically enough.  Obviously different networks and workloads are
different, and I think the best approach is likely an adaptive one, but I
don't have an adaptive algorithm I'm confident enough in to write it up.
Suggestions definitely welcome.

>
> Section 4.2.2:
>    The early retransmit logic in QUIC seems to be different from TCP's one.
>    It doesn't look ack-based as it relies on timer. (I don't say this
> is bad, but it's a bit strange to categorize it as an ack-based
> method)
>    TCP's early retransmit will be triggered only when the amount of
> outstanding data is less than 4*SMSS, but this draft doesn't mention
> about the condition. Is there any reason for it?
>    when timer-based loss detection is used, it this logic still
> available? or it won't be used with timer-based loss detection? We
> might need clarifications here.
>

The timer is taken from Linux, as mentioned at the end of 4.2.2.  It's
categorized as ACK based because it is only armed when a packet with a
larger packet number than the one being lost has been acknowledged.  One
could argue the same issue for time based loss detection, which also needs
a timer.

Instead of 4*SMSS, we specify kReorderingThreshold, since it seemed like
the core issue being fixed was that there was no other mechanism for
quickly declaring these packets lost, and if one did implement adaptive
reordering tolerance, one threshold wouldn't be out of sync with the other.

The intent is that like RACK, timer based loss detection subsumes early
retransmit.  But yes, this text could use some further clarification,
including and not limited to items pointed out in #1212.


>
> Section 4.3.2:
>    TCP RACK's PTO is aiming to be 2 * SRTT. Why QUIC uses 1.5 * SRTT?
>

This arose because TCP uses 1.5 * SRTT + MaxAckDelay if there is only one
MSS outstanding.  QUIC is still arriving at the optimal algorithm for
sending ACKs and how to indicate that to the peer, so QUIC explicitly
specifies MaxAckDelay in the handshake and always includes the MaxAckDelay
in PTO.  We could go back to the approach of trying to determine whether a
fast ACK is expected and use 2 * SRTT in that case, if we thought it was
better, but this is a bit simpler.


>
> Section 4.3.3:
>    RFC5681 uses 1 SMSS as the size of loss window, while QUIC uses 2.
> I understand the motivation to reduce the possibility of consecutive
> RTO events. But, this may means when TCP and QUIC connections are
> under heavy congestion, QUIC connections will recover more quickly
> than TCP connections. We might want to think how much QUIC and TCP
> should be fair.
>

I have some experimental code to see if 2 packets makes a difference vs 1
packet.  If not, we can change QUIC to 1.  If it does make a difference,
then we should discuss what to recommend for both TCP and QUIC.


>    BTW, it might not be necessarily, but QUIC does not need the upper
> bound for RTO?
>

In practice, I'd expect a QUIC connection to idle timeout before it hit the
upper bound.  We could add one if you think it's useful, but it seemed
safer to continue with exponential backoff.

>
> Section 4.4:
>    why the default value of max_ack_delay is 25ms?
>

It was a chosen as a good general purpose value for modern networks.  25ms
means sending an ACK for every packet only if packets are evenly spaced and
the bandwidth is about 300kbits or lower if my math is correct.  That's
definitely on the lower end of internet speeds.  Additionally, if a client
knows they're on such a slow link(2g) they can use the MaxAckDelay
transport param to specify a larger ack delay.

Or, from 4.6:
"A shorter delayed ack time of 25ms was chosen because longer delayed

   acks can delay loss recovery and for the small number of connections
   where less than packet per 25ms is delivered, acking every packet is
   beneficial to congestion control and loss recovery."


> Section 4.5.7.3:
>    Sorry.. what is 1/4 RTT timer for early retransmit?
>

 Sorry, I can't seem to find the reference to a 1/4 RTT timer for early
retransmit.

>
> Section 5.8.1:
>    Why the recommended value is 1200 bytes?
>
>
That's from QUIC transport, but the intent is to make the minimum MTU
fairly large to avoid amplification attacks as well as provide enough room
for the TLS ClientHello.

--0000000000000c6fe605797c4fcf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Thanks for your careful reading, answers =
inline.<br><div class=3D"gmail_quote"><div dir=3D"ltr">On Mon, Oct 29, 2018=
 at 1:03 PM Yoshifumi Nishida &lt;<a href=3D"mailto:nishida@sfc.wide.ad.jp"=
 target=3D"_blank">nishida@sfc.wide.ad.jp</a>&gt; wrote:<br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
At Bangkok, TCPM WG will have a session to discuss loss recovery and<br>
congestion control mechanism in QUIC and TCP. (11/6 Tuesday<br>
11:20-12:20)<br>
I really appreciate Ian and Jana for the efforts.<br>
<br>
I might overlook something as I couldn&#39;t follow up all discussion in<br=
>
QUIC, but I am thinking that it might be good if we could get some<br>
comments on the following questions.<br>
I have listed several questions on the value of some parameters, but<br>
it doesn&#39;t mean I disagree with these values. I just would like to<br>
check where these values came from.<br>
Hope this will be useful in some ways.<br>
<br>
<br>
Section 4:<br>
=C2=A0 =C2=A0QUIC supports both ack and timer for loss detection.<br>
=C2=A0 =C2=A0But, it&#39;s not very clear whether an implementation can cho=
ose one<br>
of them or it should implement both and can use both at the same time.<br>
Can it be clarified?<br></blockquote><div><br>Yes, there&#39;s an open Issu=
e to clarify this.=C2=A0 <a href=3D"https://github.com/quicwg/base-drafts/i=
ssues/1212" target=3D"_blank">https://github.com/quicwg/base-drafts/issues/=
1212</a></div><div><br></div><div>The outstanding PR is quite old, but has =
some helpful clarifications in it, so I&#39;m intending to migrate the best=
 parts to a new PR.=C2=A0 Suggestions(or PRs) welcome.</div><div><br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Section 4.1.1:<br>
=C2=A0 =C2=A0For RTT sampling, implementations will need to maintain the<br=
>
transmission time for each sending packets even if they support only<br>
ack-based method.<br>
=C2=A0 =C2=A0But, this requirement might be hard for tiny devices. Wouldn&#=
39;t it<br>
limit the applicability of QUIC?<br></blockquote><div><br></div><div>Good q=
uestion.=C2=A0 Assuming a ~1200 byte packet and a 4 byte timestamp, that&#3=
9;s &lt;0.5% of the total storage overhead, assuming the data being sent is=
 reliable.=C2=A0 That doesn&#39;t seem like too much overhead to me, but on=
e could certainly store less granular information if they were really const=
rained.=C2=A0 ie: packet numbers X to X+N all contain a certain sequence of=
 bytes and were sent at approximately a single time.=C2=A0 I believe such a=
 storage approach would make it more similar to TCP metadata, but you likel=
y know better than I do.</div><div>=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex">
<br>
=C2=A0 =C2=A0&quot;the largest newly acked packet&quot; might be confusing.=
 packet that<br>
acks the largest packet number?<br></blockquote><div><br></div><div>=C2=A0T=
hat&#39;s the largest packet that was acknowledged in the current ack frame=
 being processed.=C2=A0 I re-read the text and I&#39;m not sure how to impr=
ove it, so feel free to send a PR.</div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex">
<br>
Section 4.2.1:<br>
=C2=A0 =C2=A0TCP RACK&#39;s reo_wnd is aiming to be 1/4 RTT. Why QUIC uses =
1/8 RTT?<br></blockquote><div><br></div><div>I ran some experiments that in=
dicated 1/4 RTT was a slight latency regression for web applications and 1/=
8 RTT still had fewer spurious retransmits than the dupack threshold loss d=
etection.=C2=A0 I also presented some reordering data at maprg in Montreal =
that indicated 1/8 RTT was typically enough.=C2=A0 Obviously different netw=
orks and workloads are different, and I think the best approach is likely a=
n adaptive one, but I don&#39;t have an adaptive algorithm I&#39;m confiden=
t enough in to write it up.=C2=A0 Suggestions definitely welcome.</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Section 4.2.2:<br>
=C2=A0 =C2=A0The early retransmit logic in QUIC seems to be different from =
TCP&#39;s one.<br>
=C2=A0 =C2=A0It doesn&#39;t look ack-based as it relies on timer. (I don&#3=
9;t say this<br>
is bad, but it&#39;s a bit strange to categorize it as an ack-based<br>
method)<br>
=C2=A0 =C2=A0TCP&#39;s early retransmit will be triggered only when the amo=
unt of<br>
outstanding data is less than 4*SMSS, but this draft doesn&#39;t mention<br=
>
about the condition. Is there any reason for it?<br>
=C2=A0 =C2=A0when timer-based loss detection is used, it this logic still<b=
r>
available? or it won&#39;t be used with timer-based loss detection? We<br>
might need clarifications here.<br></blockquote><div><br></div><div>The tim=
er is taken from Linux, as mentioned at the end of 4.2.2.=C2=A0 It&#39;s ca=
tegorized as ACK based because it is only armed when a packet with a larger=
 packet number than the one being lost has been acknowledged.=C2=A0 One cou=
ld argue the same issue for time based loss detection, which also needs a t=
imer.</div><div><br></div><div>Instead of 4*SMSS, we specify kReorderingThr=
eshold, since it seemed like the core issue being fixed was that there was =
no other mechanism for quickly declaring these packets lost, and if one did=
 implement adaptive reordering tolerance, one threshold wouldn&#39;t be out=
 of sync with the other.</div><div><br></div><div>The intent is that like R=
ACK, timer based loss detection subsumes early retransmit.=C2=A0 But yes, t=
his text could use some further clarification, including and not limited to=
 items pointed out in #1212.</div><div>=C2=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex">
<br>
Section 4.3.2:<br>
=C2=A0 =C2=A0TCP RACK&#39;s PTO is aiming to be 2 * SRTT. Why QUIC uses 1.5=
 * SRTT?<br></blockquote><div><br></div><div>This arose because TCP uses 1.=
5 * SRTT=C2=A0+ MaxAckDelay if there is only one MSS outstanding.=C2=A0 QUI=
C is still arriving at the optimal algorithm for sending ACKs and how to in=
dicate that to the peer, so QUIC explicitly specifies MaxAckDelay in the ha=
ndshake and always includes the MaxAckDelay in PTO.=C2=A0 We could go back =
to the approach of trying to determine whether a fast ACK is expected and u=
se 2 * SRTT in that case, if we thought it was better, but this is a bit si=
mpler.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">
<br>
Section 4.3.3:<br>
=C2=A0 =C2=A0RFC5681 uses 1 SMSS as the size of loss window, while QUIC use=
s 2.<br>
I understand the motivation to reduce the possibility of consecutive<br>
RTO events. But, this may means when TCP and QUIC connections are<br>
under heavy congestion, QUIC connections will recover more quickly<br>
than TCP connections. We might want to think how much QUIC and TCP<br>
should be fair.<br></blockquote><div><br></div><div>I have some experimenta=
l code to see if 2 packets makes a difference vs 1 packet.=C2=A0 If not, we=
 can change QUIC to 1.=C2=A0 If it does make a difference, then we should d=
iscuss what to recommend for both TCP and QUIC.</div><div><br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex">
<br>
=C2=A0 =C2=A0BTW, it might not be necessarily, but QUIC does not need the u=
pper<br>
bound for RTO?<br></blockquote><div><br></div><div>In practice, I&#39;d exp=
ect a QUIC connection to idle timeout before it hit the upper bound.=C2=A0 =
We could add one if you think it&#39;s useful, but it seemed safer to conti=
nue with exponential backoff.=C2=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex">
<br>
Section 4.4:<br>
=C2=A0 =C2=A0why the default value of max_ack_delay is 25ms?<br></blockquot=
e><div><br></div><div>It was a chosen as a good general purpose value for m=
odern networks.=C2=A0 25ms means sending an ACK for every packet only if pa=
ckets are evenly spaced and the bandwidth is about 300kbits or lower if my =
math is correct.=C2=A0 That&#39;s definitely on the lower end of internet s=
peeds.=C2=A0 Additionally, if a client knows they&#39;re on such a slow lin=
k(2g) they can use the MaxAckDelay transport param to specify a larger ack =
delay.</div><div><br></div><div>Or, from 4.6:</div><div><font face=3D"monos=
pace, monospace">&quot;<span style=3D"color:rgb(0,0,0);font-size:13.3333px"=
>A shorter delayed ack time of 25ms was chosen because longer delayed</span=
></font></div><pre class=3D"m_8844379984790899579gmail-newpage" style=3D"fo=
nt-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:=
rgb(0,0,0)">   acks can delay loss recovery and for the small number of con=
nections
   where less than packet per 25ms is delivered, acking every packet is
   beneficial to congestion control and loss recovery.&quot;</pre><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">
<br>
Section <a href=3D"http://4.5.7.3" rel=3D"noreferrer" target=3D"_blank">4.5=
.7.3</a>:<br>
=C2=A0 =C2=A0Sorry.. what is 1/4 RTT timer for early retransmit?<br></block=
quote><div><br></div><div>=C2=A0Sorry, I can&#39;t seem to find the referen=
ce to a 1/4 RTT timer for early retransmit.</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">
<br>
Section 5.8.1:<br>
=C2=A0 =C2=A0Why the recommended value is 1200 bytes?<br>
<br></blockquote><div><br></div><div>That&#39;s from QUIC transport, but th=
e intent is to make the minimum MTU fairly large to avoid amplification att=
acks as well as provide enough room for the TLS ClientHello.<br></div></div=
></div></div>

--0000000000000c6fe605797c4fcf--


From nobody Tue Oct 30 20:22:39 2018
Return-Path: <kazuhooku@gmail.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 633BE127332 for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 20:22:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 yGL23tIswHcO for <quic@ietfa.amsl.com>; Tue, 30 Oct 2018 20:22:36 -0700 (PDT)
Received: from mail-lj1-x244.google.com (mail-lj1-x244.google.com [IPv6:2a00:1450:4864:20::244]) (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 BAED7124C04 for <quic@ietf.org>; Tue, 30 Oct 2018 20:22:35 -0700 (PDT)
Received: by mail-lj1-x244.google.com with SMTP id g26-v6so12170503lja.10 for <quic@ietf.org>; Tue, 30 Oct 2018 20:22:35 -0700 (PDT)
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:content-transfer-encoding; bh=79yD4oHBfcWzISnO1PUGjDZeYuf/DtVtzxY0AgNoyIw=; b=G1WCDbClML2UkCly9HjVmQkX7x5pZZS2fv3JYiX/zKogcGUuRqJ3fz8gfeb1Skmdbk MW1SQ7sJPBtepgW6jZzcUezevPRONzZ68Y+DZfyOcNmbzJTnAIiIRlabpe9EzIb6xNeH SDpDqPPpd7WiY2q+r3pIja70On8A22aIrEF2chtn0qdb+U0K2PE0BPe/m1pZE1c63xdx 133yu4ziK4DxbWpMU3J1GdEey06lAdGqf4lIJPVvLO39M5zrSQBOAU96XMzXhosZTsCa gQZSPdPuXhbFFb+i9YxAlMUSl1oJUvviePrNNjgg3H6NG4v3sU1dLsa+ojpavwRJ9Jz1 JGHg==
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:content-transfer-encoding; bh=79yD4oHBfcWzISnO1PUGjDZeYuf/DtVtzxY0AgNoyIw=; b=EODBtdhf6U7qh80MhstaTGnylhSemJ6zMPp+33ckwJwEIBeQFSc2P8jKSe9pVhe6bs UAACtfqDtXCCoL1PywwkEdELVOsMXB+P+PbYAxXAycQmVlcNTmWDBKCoTyIIrXPUtzW5 O8VqtigU1RkYL99JBq8GcLvUj85YLY6cg5ZK1saF48YIU4PkdHuhz0cfE87xJLnIeFGM gN3wgzqTEn4JIz4ogh1SWMEcictoXuNTxbAWON8pPK0p4A3sVjMkCbQop6ab4PFACAGw AtpcAycuxz2PdUAR4MZYdZIu7lLJpUO0rI7hOYBdTDx0cu0iLJo2dqFospr1sw06R6GW ORNw==
X-Gm-Message-State: AGRZ1gIfJnmWhk1LvTBeGir/zAILykMd80TDNHiGok17z/OxJwoyIHDY u5u6ibsz0lZQUV17MZXBa9yUFJY/iZZ1yI9EUPQ=
X-Google-Smtp-Source: AJdET5clt3stQoP9trzUzw0jx/Rjx37CnpVf6f44YUk5XnYlOu4A/sjE7BPufrFtpFrn+J9F88jJDhfgCyu3kxqMkEc=
X-Received: by 2002:a2e:9d50:: with SMTP id y16-v6mr858033ljj.136.1540956153942;  Tue, 30 Oct 2018 20:22:33 -0700 (PDT)
MIME-Version: 1.0
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com> <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch> <a088c411-1acc-8b0f-fc1b-8c79ce6f1cd7@huitema.net> <DB6PR10MB1766E6B29792BB4401FF38F0ACCC0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <65907d96-a525-dcd0-39cd-678c52d26ab6@huitema.net> <CABkgnnVCveXr2GUsx2ZyKNf08VaCh+Ts-T=5wD3_-8Pqk2xRTQ@mail.gmail.com>
In-Reply-To: <CABkgnnVCveXr2GUsx2ZyKNf08VaCh+Ts-T=5wD3_-8Pqk2xRTQ@mail.gmail.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Wed, 31 Oct 2018 12:22:22 +0900
Message-ID: <CANatvzysY8kh7xGRHnTLFrtRZUfmJAhybN0LCpyZZqVAgX-7xg@mail.gmail.com>
Subject: Re: Structuring the BKK spin bit discussion
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Christian Huitema <huitema@huitema.net>, =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>,  marcus.ihlar@ericsson.com, IETF QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/u2H7OueZwiTABslgnUdHxCoAyCU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 03:22:37 -0000

2018=E5=B9=B410=E6=9C=8831=E6=97=A5(=E6=B0=B4) 7:55 Martin Thomson <martin.=
thomson@gmail.com>:
>
> On Wed, Oct 31, 2018 at 5:42 AM Christian Huitema <huitema@huitema.net> w=
rote:
> > Mikkel is correct, we may not want a purely random per connection behav=
ior, but rather something "random per destination". This would better mimic=
 the opt-out behavior of a privacy-sensitive endpoint, which would always o=
pt out when contacting a specific destination. If I had to implement it, I =
would not use a PRNG, but rather something compute the hash of a local secr=
et and either the peer address or the peer name. That way, the client would=
 opt out for all 16 Netflix connections, or for none of them.
>
> Or are we looking for random per-path?
>
> That notion would seem to tilt the balance more in favour of the
> "discretionary" option over the "negotiated" one on the basis that
> spinning/not doesn't become a linkability consideration.

Even though spin-bit is a per-path thing, I am not sure if the
probabilistic opt-out needs to be per-path. This is because what we
need to ensure is having at least some portion of QUIC packets flows
floating on each path not using the spin bit.

That can be achieved either by having QUIC endpoints turning off the
spin-bit for every path at a fixed probability, or by having them
turning off the spin-bit for every connection at a fixed probability.

--=20
Kazuho Oku


From nobody Wed Oct 31 01:38:51 2018
Return-Path: <ietf@trammell.ch>
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 EDE59130DED for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 01:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 yqgYDIDsnuch for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 01:38:47 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [212.25.24.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A58A0129619 for <quic@ietf.org>; Wed, 31 Oct 2018 01:38:46 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 9A036341C8E; Wed, 31 Oct 2018 09:38:44 +0100 (CET)
X-Iway-Path: 0
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/20439.20981); Wed, 31 Oct 2018 09:38:44 +0100 (CET)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Wed, 31 Oct 2018 09:38:44 +0100 (CET)
Received: from [145.14.214.39] (account ietf@trammell.ch HELO [10.11.33.83]) by switchplus-mail.ch (CommuniGate Pro SMTP 6.2.9) with ESMTPSA id 72209542; Wed, 31 Oct 2018 09:38:44 +0100
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <AC119BF0-FFDE-4B74-B628-D26B53CEC4CE@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_32313F8E-FD9F-450A-9DEB-7301C4936572"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: Structuring the BKK spin bit discussion
Date: Wed, 31 Oct 2018 09:38:43 +0100
In-Reply-To: <CABkgnnVCveXr2GUsx2ZyKNf08VaCh+Ts-T=5wD3_-8Pqk2xRTQ@mail.gmail.com>
Cc: Christian Huitema <huitema@huitema.net>, =?utf-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>, Marcus Ihlar <marcus.ihlar@ericsson.com>, QUIC WG <quic@ietf.org>
To: Martin Thomson <martin.thomson@gmail.com>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com> <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch> <a088c411-1acc-8b0f-fc1b-8c79ce6f1cd7@huitema.net> <DB6PR10MB1766E6B29792BB4401FF38F0ACCC0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <65907d96-a525-dcd0-39cd-678c52d26ab6@huitema.net> <CABkgnnVCveXr2GUsx2ZyKNf08VaCh+Ts-T=5wD3_-8Pqk2xRTQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/OOtgC4M21RtHJ_6GcHdlhvLP0OU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 08:38:49 -0000

--Apple-Mail=_32313F8E-FD9F-450A-9DEB-7301C4936572
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

hi Martin,

> On 30 Oct 2018, at 23:55, Martin Thomson <martin.thomson@gmail.com> =
wrote:
>=20
> On Wed, Oct 31, 2018 at 5:42 AM Christian Huitema =
<huitema@huitema.net> wrote:
>> Mikkel is correct, we may not want a purely random per connection =
behavior, but rather something "random per destination". This would =
better mimic the opt-out behavior of a privacy-sensitive endpoint, which =
would always opt out when contacting a specific destination. If I had to =
implement it, I would not use a PRNG, but rather something compute the =
hash of a local secret and either the peer address or the peer name. =
That way, the client would opt out for all 16 Netflix connections, or =
for none of them.
>=20
> Or are we looking for random per-path?
>=20
> That notion would seem to tilt the balance more in favour of the
> "discretionary" option over the "negotiated" one on the basis that
> spinning/not doesn't become a linkability consideration.

Yeah, I noticed this when writing up =
https://github.com/quicwg/base-drafts/pull/1937 -- if a handshake =
negotiating a spin version commits both endpoints to spin on that =
connection for every subsequent CID, then if endpoints implementing spin =
are relatively rare (which may be the case no matter what early in the =
deployment curve), this sticky state is a potential linkability issue. =
If endpoints willing to negotiate spin are widely deployed, linkability =
becomes negligible.

One can fix this by allowing endpoints that have negotiated spinning to =
transition to discretionary non-spinning on a CID change, since for this =
to be a useful exercise of the version negotiation machinery, the MUST =
spin is only important for the CID directly after the handshake.

But you're right, the additional complexity starts making negotiation =
look less attractive.

Cheers,

Brian

--Apple-Mail=_32313F8E-FD9F-450A-9DEB-7301C4936572
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAlvZahMACgkQihK3vwvq
RqOJPg/9HO2CzwAyLuVZIhg+2RkKQDvtpzT2o2wbPbTqttFThStl9Yp5D87G4ABy
oR6CU6fhWNsln+bk+dmrF+vnUOicz8aVaa0h9YZpd4GOKAz3qaY156CO35JFL00Y
l5bM92MEIwcqw0CK4gtit03cab1p84+FukGx/A8d8udFZVtsDX1uJs+GcCrqWNne
ZbvqeONU16tlpEktdVUr/oLUJkS3DRfnjZbxRdiWJyDnPhPsJwSbKCTdLUUGhJ3A
VjUqj53gI88xuMPnj661GXBHx3xoJMJpq7RQu4VJkBORKXeDhD45W7ewuVh2j3Kc
rqLumH9AQ3c95cGzTlrPvb/323XTRd0/pUzXcyVOldhAddqkJP5EqOIdcRejstVZ
ieNFqTBvnBaPNk3nxdCP625BxPn6OM9gtEYlN/LdJQ/+VfTvPEb2qwKB8yAUqVP3
u+WROEn0inp6uRIimIRwlJzKZ35+T37YHE8LpAKvcTTJ/FvCs0bO/m3S38R8HcmF
UOcx1QqqOz4/Uh8QKOrA+QCLyOZTRwf+DEltbKcq1aPdzOPsie3K0fM5Fyc7U2uY
ERu04uUxpaMM/Fj2kXFJK2KNPVrtbnT3kkTj0YEISP6n7xy1A3BTqCa9FaU5FH0g
mR6kMjlq0Qv+UU0YL9TSUu65jOSc70BDp/MXEMvDKVD/6QLelrU=
=VGFp
-----END PGP SIGNATURE-----

--Apple-Mail=_32313F8E-FD9F-450A-9DEB-7301C4936572--


From nobody Wed Oct 31 01:51:24 2018
Return-Path: <ietf@trammell.ch>
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 6DB18130934 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 01:51:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 lCgubuLU_O_x for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 01:51:21 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [IPv6:2001:8e0:40:325::36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7236B129619 for <quic@ietf.org>; Wed, 31 Oct 2018 01:51:21 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id D4C93341C8D; Wed, 31 Oct 2018 09:51:19 +0100 (CET)
X-Iway-Path: 0
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/20439.21978); Wed, 31 Oct 2018 09:51:19 +0100 (CET)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Wed, 31 Oct 2018 09:51:19 +0100 (CET)
Received: from [145.14.214.39] (account ietf@trammell.ch HELO [10.11.33.83]) by switchplus-mail.ch (CommuniGate Pro SMTP 6.2.9) with ESMTPSA id 72211358; Wed, 31 Oct 2018 09:51:19 +0100
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <C2E19BC3-36D9-4392-845B-B328FFF4198B@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_1A57FB0D-A3DC-4B16-BF4D-E9D01B03B53E"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: Structuring the BKK spin bit discussion
Date: Wed, 31 Oct 2018 09:51:18 +0100
In-Reply-To: <CACpbDccPEkpdU0KW8iaUk=MKJwd2ptGRr09Z0ofKi+rOv9Ee0A@mail.gmail.com>
Cc: Christian Huitema <huitema@huitema.net>, =?utf-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>, Marcus Ihlar <marcus.ihlar@ericsson.com>, Jana Iyengar <jri.ietf@gmail.com>
To: QUIC WG <quic@ietf.org>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com> <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch> <a088c411-1acc-8b0f-fc1b-8c79ce6f1cd7@huitema.net> <DB6PR10MB1766E6B29792BB4401FF38F0ACCC0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <2F288470-1659-4A8F-92BD-5640998917D8@trammell.ch> <CACpbDccPEkpdU0KW8iaUk=MKJwd2ptGRr09Z0ofKi+rOv9Ee0A@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/3Tt6T-FjUSvnsequsrn__qdad1o>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 08:51:23 -0000

--Apple-Mail=_1A57FB0D-A3DC-4B16-BF4D-E9D01B03B53E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Greetings, all,

I've merged Christian's PR #1931 which covers discretionary spin, and my =
PR #1937 which covers negotiated spin, into draft-ietf-quic-spin-exp. =
For those of you who'd like text in a draft to accompany this =
discussion, have a look at the editor's copy:

https://quicwg.org/base-drafts/draft-ietf-quic-spin-exp.html

Note that the document has two different suggestions as to what =
endpoints should do with the spin bit when not spinning it: either pin =
it to 0, or select a random value per CID. Picking one is a detail =
question. IMO, either is fine; the latter has a (probably negligible) =
greasing effect.

Cheers,

Brian



> On 30 Oct 2018, at 18:55, Jana Iyengar <jri.ietf@gmail.com> wrote:
>=20
> Brian, (and Martin),
>=20
> I like this structuring of the discussion, and I think it'll be good =
to use this structure for the discussion in BKK.
>=20
> - jana
>=20
> On Tue, Oct 30, 2018 at 6:37 AM Brian Trammell (IETF) =
<ietf@trammell.ch> wrote:
> hi Marcus, all,
>=20
> So let me step back a bit and suggest a starting point (borrowing =
heavily from MT in an offlist discussion) for discussing what we want to =
do in BKK. (Or rather, I should say, let me suggest a starting point for =
y'all to discuss, because I doubt I'll be in a position to join remotely =
at 03:00 next Wednesday local time. Have fun! :)




--Apple-Mail=_1A57FB0D-A3DC-4B16-BF4D-E9D01B03B53E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAlvZbQYACgkQihK3vwvq
RqMJBg/+MbosOJavjS3Zx8lo2dRxH4JpL9821jV7rj3PWmzE3mdCojRVUr9faqW5
feM9A4NaNWTxgVmDi9f76ATewsh0/E8HctraRjcluCLaX3KEZuc2EeXVuptVNqm9
jS5Sd3q6aj6xQbXiNIRiAJN2d2xP6OGQ1R3g0scsLqVPcg8EGgfsdaFcU+nyVlSc
DoWMnbzbb+bjVQ5zszHFXq5byWvTATWgbJpFQdpPiewYMhBNQz4KQR/hzcOq16Lc
tic0GyXIrLhUWVAoN7Xi8/gVSUM4MgambSLUR+SUK9JAKbrDsqi6SJe4bv6EKkR/
AZsmUA+KbLCKmii3CvpuinUOy9bcibeffV/WL0p9YjpCzGykEi9Mr7f4GgfcI2ck
UVNoAkjZcMSpCYL/Mr3jo2I7iF4RgXhp9SssH0e1pTuu/+97O+AUEg9kuS57/u+W
eYY48f2p4W1V4juMaR/R+xwV7ZJswbbYA5qO92AABvaJ6UxyzbVOnKxO2igF6T+f
RDvBrhVVqaJlVZHedkf4LIafNY8xgSZPHMYg4Lr/+Ugn0sW8sGdLmSbERremJjhh
L4a2/BPbvlILLSser/PwqTF3EYlJExqFN8tgWjBzCWQ7o3lhks+smJUj+b4aTCXk
MiMYunIr5NFo7JpqD9HIdkmMfGtGaFniPirLxPMhYM2DdIFG/Zo=
=JBp4
-----END PGP SIGNATURE-----

--Apple-Mail=_1A57FB0D-A3DC-4B16-BF4D-E9D01B03B53E--


From nobody Wed Oct 31 03:21:08 2018
Return-Path: <kazuhooku@gmail.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 B9C14129619 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 03:21:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 GVW9j030ArEo for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 03:21:05 -0700 (PDT)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (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 BA1E212958B for <quic@ietf.org>; Wed, 31 Oct 2018 03:21:04 -0700 (PDT)
Received: by mail-lj1-x234.google.com with SMTP id z80-v6so8224843ljb.8 for <quic@ietf.org>; Wed, 31 Oct 2018 03:21:04 -0700 (PDT)
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:content-transfer-encoding; bh=lDtpRyKsjJ+r1TFVKzXIToDv8OAtJ0zr9MqtIlvktRc=; b=Ix+qB10sKAe3YAStW4eS4SjWEsRaKTGRmt0vlUcntv2Ri5xW3A6BE99UolgImQ60rV zLFeGcjqPoFLGCkWO4AUVGWkThtyDFNghmdU4unP1bihaDoNBJi9AFnJLF6QB195T3G/ LtHvgbfVmVD+BoOj5kIHAg0dK8mrPeOBcKKB5nEd7tSdqB4El9HP8V/XeHynYOKmxloK WvZaArn7mYrCxsa7MnOSpd++3W6S4TRw9DREOGsTtpYtuzioH5HfU3Ayhx5H61SeE1GB kFeUcdESXhKBL//PUaaJ9EEQ7qGbIBB8wSaMWfDmrFOgPEbYy/VNBkbrIkUQszcLVLkK 0GCA==
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:content-transfer-encoding; bh=lDtpRyKsjJ+r1TFVKzXIToDv8OAtJ0zr9MqtIlvktRc=; b=nymUjEzS88oZUN85hTDqVFMvcMQbtB+kVjh4gZ//BERO71XEd+e8OJaXoUhvUoXFVM +O9LNXITN0Fnx75RWPutF2kk7KzzhMW5k0v7d2/36KMetQ6Zxkl1QPkv7XuR2MxGsyS4 r7Ugw78c9JbflbnujQS7BejEYrRBokqeEHiG40SO4S/18VqU9E8NacvOFiJho95YAMMX uVUyevpb7WkryZlAUMipHJxRpS9RAEfvttXKfWC3wiCbHhg0mpL1GdQFN8LPuypwSN+0 vOrjB14rgjZuUoqhqn/zRZvylUbOKgUGuKbycxuSZraOM04flUzZONy7LcNjvJPBFl0y WA+A==
X-Gm-Message-State: AGRZ1gLni9UmF6bKXj+U5j/43EFsXSIm5i2Ug9QiHrnogv7qKlOXWXk2 L4/s2cZnzgTaBC9K/QhsPrENf5SRb7B9A/J6Lug=
X-Google-Smtp-Source: AJdET5ed1/yLj8EtO9WIWlW8AWKTeJhOwPOEe6fgls2tr2jI1y09idTAsPtcJD2ji8n16Bpq29Mcxxjsz5TF0tRrHFQ=
X-Received: by 2002:a2e:3918:: with SMTP id g24-v6mr1545227lja.113.1540981262816;  Wed, 31 Oct 2018 03:21:02 -0700 (PDT)
MIME-Version: 1.0
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net>
In-Reply-To: <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Wed, 31 Oct 2018 19:20:51 +0900
Message-ID: <CANatvzxt-QBmeJUwp+MjtbpYXstPiEigDzQe0KfWJN+q0XR4Kg@mail.gmail.com>
Subject: Re: Structuring the BKK spin bit discussion
To: Christian Huitema <huitema@huitema.net>
Cc: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/g-3ADJIkFXGbh-3fQ0xzu7lGqXA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 10:21:07 -0000

2018=E5=B9=B410=E6=9C=8830=E6=97=A5(=E7=81=AB) 1:54 Christian Huitema <huit=
ema@huitema.net>:
>
>
>
> > On Oct 29, 2018, at 9:08 AM, Dmitri Tikhonov <dtikhonov@litespeedtech.c=
om> wrote:
> >
> >> On Mon, Oct 29, 2018 at 05:26:34PM +0200, Lars Eggert wrote:
> >> We'd specifically like to ask client and server implementors with
> >> projected sizable deployments to indicate whether they intent to
> >> implement and deploy, if the WG decided to include the spin-bit in
> >> the spec.
> >
> > LiteSpeed Technologies will support the spin bit -- both in our
> > server and client QUIC implementations -- if it make it into the
> > draft.
>
> My implementation is not used in any large scale deployment, but it does =
support the spin bit. In fact, it has configuration options to support spin=
 bit variants: node, just spin, spin + vec, spin + QR.
>
> I think the strongest objection to the spin bit was put up by Marten duri=
ng the last interim: measuring the RTT with the spin bit discloses the use =
of hidden path segments like VPN. This issue was not discussed during the p=
rivacy analysis.

May I ask if the VPN users are the only ones that lose some privacy
with spin bits?

I ask this because I live in a country where IIUC the mobile carriers
place their nation-wide carrier-grade NAT near the capital city (i.e.,
Tokyo). That means that for people living in the country, having spin
bits turned on could reveal their distance from Tokyo.

So the question is: if VPN users need special care, do some NAT users
as well? Or if the answer is no, what is the difference from between
the two groups?

Generally speaking, I am not against giving users the freedom to
expose spin bits, however I am wondering how the endpoints should
provide the freedom of choice (UI question) as well as what the
default should be.

>
> The privacy issue could be mitigated by turning off the spin bit at priva=
cy sensitive clients, but this would make these clients "stick out".
>
> One solution would be to remove the spin bit from the spec, trading off b=
etter privacy for worse management. I am considering another solution in wh=
ich privacy sensitive clients hide the RTT by controlling the spin, for exa=
mple spinning at fixed intervals. I plan testing that option in Picoquic.
>
> -- Christian Huitema
>
>


--=20
Kazuho Oku


From nobody Wed Oct 31 04:12:11 2018
Return-Path: <ianswett@google.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 0274612785F for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 04:12:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.5
X-Spam-Level: 
X-Spam-Status: No, score=-17.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 zyYXav9EzhJP for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 04:12:07 -0700 (PDT)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (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 7C47A130DF7 for <quic@ietf.org>; Wed, 31 Oct 2018 04:12:07 -0700 (PDT)
Received: by mail-wm1-x334.google.com with SMTP id b203-v6so14167425wme.5 for <quic@ietf.org>; Wed, 31 Oct 2018 04:12:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SO4sJ8BUirWBwCZZWSTS32YwvXYrmczAs9Pm3yoYmbo=; b=jMJ2lrSdf8pJqtkAp0f+J4VzdCIKFcl1TfgkXzDCrQybe1CKB9qWHST7TtiaaGetVM sPMrS+bB6k/ArTqYvvN8hZlqbriHyjGVdCld70RgQRAiYaq0zVnNSUi7NAHGK0Hn46I0 I2Thd9690uHBX89IYE84PBiT78k7o2H7iSRcyjypNx1ur335yS/9z6gCGSWC/ULtT9rl 8xWCbebjJPKVNNItL3FFGRa3vxxEopN9U8QdZm45IDAJoDvFy63xsO1pAu1eP33jn47p UIZ9A6M30X3bGs5mSiQNNXbHxO7qBlKCJnCxMweSTn2TLuMq0Z6K/E7uUfr7qRmo9GHA aDPQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SO4sJ8BUirWBwCZZWSTS32YwvXYrmczAs9Pm3yoYmbo=; b=W3NXx8DGxQ8FXni/bLCgiGwiaavX0BZZhc2iMhdtxz4gc5pLFMyc2Y6zRKeWHr5Ug7 BlLIZO5yo8juKZbLHyyldp0u2JgmqREo3s+6hZg30blSPYPMb1q1rL+yn2Hachf8jzgV aVH+dQ2ipZdVNeCZtvJtY5hRUF8n4RwFPthS1ZI/k6bryDdALamKhloeZjS5OCsdhi8S c+i86q1UqYd49w9M4o0qMrHXbfrf5ZG63AjiVlmxRkXpa0Es4y58ymFkRw8wDgj/pAi2 cc01llgUH/Pj0tBS4Z1sCvjdgYDzTpKpo38dsJFwZf/r6rxiqwWGYQDMWBWY45tCRNvd 2n4Q==
X-Gm-Message-State: AGRZ1gIxhh656JID4f7y+Kg4spcyAXAPyNk3JB1/aatrzoCNTU3MePYF /s+4HeVeJFuVc1jPh9ZZ5bQ0yqGlAvIUqWnXUT/lzw==
X-Google-Smtp-Source: AJdET5fXI7pRMg8BaBXST+99uGEjnJOBZPCiF03Wrqu7aPleO6yYinnyzsc8nCTevytxIcXzwcsFfX8BgICcWEM9Rtw=
X-Received: by 2002:a1c:cc07:: with SMTP id h7-v6mr229862wmb.0.1540984325281;  Wed, 31 Oct 2018 04:12:05 -0700 (PDT)
MIME-Version: 1.0
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CABkgnnU7W-_o_EGZWpJvTGRSm0KiL-hS7q_oQ6kT3LBoNKHGhw@mail.gmail.com> <5E1AB9AC-D24F-4E0D-9925-57816C5314A4@trammell.ch> <a088c411-1acc-8b0f-fc1b-8c79ce6f1cd7@huitema.net> <DB6PR10MB1766E6B29792BB4401FF38F0ACCC0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <HE1PR0701MB23939472CAA7CC7C1CD42BB1E2CC0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <2F288470-1659-4A8F-92BD-5640998917D8@trammell.ch> <CACpbDccPEkpdU0KW8iaUk=MKJwd2ptGRr09Z0ofKi+rOv9Ee0A@mail.gmail.com> <C2E19BC3-36D9-4392-845B-B328FFF4198B@trammell.ch>
In-Reply-To: <C2E19BC3-36D9-4392-845B-B328FFF4198B@trammell.ch>
From: Ian Swett <ianswett@google.com>
Date: Wed, 31 Oct 2018 07:11:52 -0400
Message-ID: <CAKcm_gONwjdmuccFRia4YrQfB7cgNnwtFQ=5B3aJBgrV5ZUqFQ@mail.gmail.com>
Subject: Re: Structuring the BKK spin bit discussion
To: Brian Trammell <ietf@trammell.ch>
Cc: IETF QUIC WG <quic@ietf.org>, Jana Iyengar <jri.ietf@gmail.com>,  =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>,  Marcus Ihlar <marcus.ihlar@ericsson.com>, Christian Huitema <huitema@huitema.net>
Content-Type: multipart/alternative; boundary="00000000000053033b0579845fec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/5PC_jAl8aekl9c1SOvClJXP5TRw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 11:12:10 -0000

--00000000000053033b0579845fec
Content-Type: text/plain; charset="UTF-8"

Thanks Brian, please do not pin it to 0.  I have a strong feeling that
could end badly, particularly if early clients and/or servers do not spin.

On Wed, Oct 31, 2018 at 4:51 AM Brian Trammell (IETF) <ietf@trammell.ch>
wrote:

> Greetings, all,
>
> I've merged Christian's PR #1931 which covers discretionary spin, and my
> PR #1937 which covers negotiated spin, into draft-ietf-quic-spin-exp. For
> those of you who'd like text in a draft to accompany this discussion, have
> a look at the editor's copy:
>
> https://quicwg.org/base-drafts/draft-ietf-quic-spin-exp.html
>
> Note that the document has two different suggestions as to what endpoints
> should do with the spin bit when not spinning it: either pin it to 0, or
> select a random value per CID. Picking one is a detail question. IMO,
> either is fine; the latter has a (probably negligible) greasing effect.
>
> Cheers,
>
> Brian
>
>
>
> > On 30 Oct 2018, at 18:55, Jana Iyengar <jri.ietf@gmail.com> wrote:
> >
> > Brian, (and Martin),
> >
> > I like this structuring of the discussion, and I think it'll be good to
> use this structure for the discussion in BKK.
> >
> > - jana
> >
> > On Tue, Oct 30, 2018 at 6:37 AM Brian Trammell (IETF) <ietf@trammell.ch>
> wrote:
> > hi Marcus, all,
> >
> > So let me step back a bit and suggest a starting point (borrowing
> heavily from MT in an offlist discussion) for discussing what we want to do
> in BKK. (Or rather, I should say, let me suggest a starting point for y'all
> to discuss, because I doubt I'll be in a position to join remotely at 03:00
> next Wednesday local time. Have fun! :)
>
>
>
>

--00000000000053033b0579845fec
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks Brian, please do not pin it to 0.=C2=A0 I have a st=
rong feeling that could end badly, particularly if early clients and/or ser=
vers do not spin.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On W=
ed, Oct 31, 2018 at 4:51 AM Brian Trammell (IETF) &lt;<a href=3D"mailto:iet=
f@trammell.ch">ietf@trammell.ch</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Greetings, all,<br>
<br>
I&#39;ve merged Christian&#39;s PR #1931 which covers discretionary spin, a=
nd my PR #1937 which covers negotiated spin, into draft-ietf-quic-spin-exp.=
 For those of you who&#39;d like text in a draft to accompany this discussi=
on, have a look at the editor&#39;s copy:<br>
<br>
<a href=3D"https://quicwg.org/base-drafts/draft-ietf-quic-spin-exp.html" re=
l=3D"noreferrer" target=3D"_blank">https://quicwg.org/base-drafts/draft-iet=
f-quic-spin-exp.html</a><br>
<br>
Note that the document has two different suggestions as to what endpoints s=
hould do with the spin bit when not spinning it: either pin it to 0, or sel=
ect a random value per CID. Picking one is a detail question. IMO, either i=
s fine; the latter has a (probably negligible) greasing effect.<br>
<br>
Cheers,<br>
<br>
Brian<br>
<br>
<br>
<br>
&gt; On 30 Oct 2018, at 18:55, Jana Iyengar &lt;<a href=3D"mailto:jri.ietf@=
gmail.com" target=3D"_blank">jri.ietf@gmail.com</a>&gt; wrote:<br>
&gt; <br>
&gt; Brian, (and Martin),<br>
&gt; <br>
&gt; I like this structuring of the discussion, and I think it&#39;ll be go=
od to use this structure for the discussion in BKK.<br>
&gt; <br>
&gt; - jana<br>
&gt; <br>
&gt; On Tue, Oct 30, 2018 at 6:37 AM Brian Trammell (IETF) &lt;<a href=3D"m=
ailto:ietf@trammell.ch" target=3D"_blank">ietf@trammell.ch</a>&gt; wrote:<b=
r>
&gt; hi Marcus, all,<br>
&gt; <br>
&gt; So let me step back a bit and suggest a starting point (borrowing heav=
ily from MT in an offlist discussion) for discussing what we want to do in =
BKK. (Or rather, I should say, let me suggest a starting point for y&#39;al=
l to discuss, because I doubt I&#39;ll be in a position to join remotely at=
 03:00 next Wednesday local time. Have fun! :)<br>
<br>
<br>
<br>
</blockquote></div>

--00000000000053033b0579845fec--


From nobody Wed Oct 31 05:03:40 2018
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
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 A4657130DED for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 05:03:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 YdN08KyNPWKz for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 05:03:36 -0700 (PDT)
Received: from virgo02.ee.ethz.ch (virgo02.ee.ethz.ch [129.132.72.10]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD64A130DF7 for <quic@ietf.org>; Wed, 31 Oct 2018 05:03:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by virgo02.ee.ethz.ch (Postfix) with ESMTP id 42lRnL1S3dz15LSn; Wed, 31 Oct 2018 13:03:34 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at virgo02.ee.ethz.ch
Received: from virgo02.ee.ethz.ch ([127.0.0.1]) by localhost (virgo02.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id efK9z-wPh5Pf; Wed, 31 Oct 2018 13:03:28 +0100 (CET)
X-MtScore: NO score=0
Received: from [192.168.178.24] (mue-88-130-61-252.dsl.tropolys.de [88.130.61.252]) by virgo02.ee.ethz.ch (Postfix) with ESMTPSA; Wed, 31 Oct 2018 13:03:28 +0100 (CET)
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: maprg session on Tue Nov 6, 1610-1810
Message-Id: <C70C3C49-50DB-43C6-94F9-9C48C350C861@tik.ee.ethz.ch>
Date: Wed, 31 Oct 2018 13:03:27 +0100
Cc: Dave Plonka <dave@plonka.us>
To: quic@ietf.org
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/B07JUnEjtaa4JsuYYsxh5N8jAMI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 12:03:39 -0000

Hi quic floks,

we have a talk on quic over satellite network on the maprg agenda and I =
guess that could be interesting for you:

   QUIC performance over a satellite public Internet access (Nicolas =
Kuhn)

The maprg session will take place on

   Tuesday, 6 November 2018, Afternoon Session II 1610-1810
   Room Name: Chitlada 1

See you there!
Mirja (maprg co-chair)=


From nobody Wed Oct 31 05:40:15 2018
Return-Path: <marcus.ihlar@ericsson.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 18F79130E06 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 05:40:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.769
X-Spam-Level: 
X-Spam-Status: No, score=-4.769 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=W+fKLQys; dkim=pass (1024-bit key) header.d=ericsson.com header.b=TNuGPhRb
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 dvcxTqUQ1MIt for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 05:40:11 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 7B3E5130E01 for <quic@ietf.org>; Wed, 31 Oct 2018 05:40:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple;  q=dns/txt; i=@ericsson.com; t=1540989608; x=1543581608; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=UoLWcJok7vH7LdABqQIS3hER1dBo7hOXsEGE8ToIXdc=; b=W+fKLQysBQ6K/P1TEHe9IN5nWOa31gAwr9FVCAHzr9FCZEZKIVIGMppiOhViAs1T v1N/VWK1g6W8NCE/hId3jWJhZsqlw/UmNQzGBedniY3zTylafpOnNvKWKKzWao08 u//en4E7pdTSJIHkZyGvVMaySPYAARRW/oFJuk4Xqhc=;
X-AuditID: c1b4fb25-f3b359e00000414e-52-5bd9a2a82ec4
Received: from ESESSMB501.ericsson.se (Unknown_Domain [153.88.183.119]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 8D.CD.16718.8A2A9DB5; Wed, 31 Oct 2018 13:40:08 +0100 (CET)
Received: from ESESBMR505.ericsson.se (153.88.183.201) by ESESSMB501.ericsson.se (153.88.183.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Wed, 31 Oct 2018 13:40:07 +0100
Received: from ESESSMB505.ericsson.se (153.88.183.166) by ESESBMR505.ericsson.se (153.88.183.201) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Wed, 31 Oct 2018 13:40:07 +0100
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB505.ericsson.se (153.88.183.166) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Wed, 31 Oct 2018 13:40:07 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UoLWcJok7vH7LdABqQIS3hER1dBo7hOXsEGE8ToIXdc=; b=TNuGPhRboUCumKN3gNH6KDYYvzjzpMBLmn/D1Op1qfbpm9kOlGy/HqmsEiqRhfv9V4Sly7bKfuhcgAdV+gQaK9Zz33TZpA7V4H6IFR6S+32GKdCJYDjASwTNdVynLSxuexf/j5+FrZNVf4ciC1M0criN+RpZrB3g586utFmSou8=
Received: from HE1PR0701MB2393.eurprd07.prod.outlook.com (10.168.128.12) by HE1PR0701MB2396.eurprd07.prod.outlook.com (10.168.128.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1294.10; Wed, 31 Oct 2018 12:40:06 +0000
Received: from HE1PR0701MB2393.eurprd07.prod.outlook.com ([fe80::1b9:990b:7c9f:1cf5]) by HE1PR0701MB2393.eurprd07.prod.outlook.com ([fe80::1b9:990b:7c9f:1cf5%5]) with mapi id 15.20.1294.022; Wed, 31 Oct 2018 12:40:06 +0000
From: Marcus Ihlar <marcus.ihlar@ericsson.com>
To: Kazuho Oku <kazuhooku@gmail.com>, Christian Huitema <huitema@huitema.net>
CC: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>, "Dmitri Tikhonov" <dtikhonov@litespeedtech.com>
Subject: SV: Structuring the BKK spin bit discussion
Thread-Topic: Structuring the BKK spin bit discussion
Thread-Index: AQHUb5vbxC4W7eXZzE+qDxda0MBukqU2Y+yAgAAMqQCAArb/gIAAJKtM
Date: Wed, 31 Oct 2018 12:40:06 +0000
Message-ID: <HE1PR0701MB23938B01BC31888DAC3629B8E2CD0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net>, <CANatvzxt-QBmeJUwp+MjtbpYXstPiEigDzQe0KfWJN+q0XR4Kg@mail.gmail.com>
In-Reply-To: <CANatvzxt-QBmeJUwp+MjtbpYXstPiEigDzQe0KfWJN+q0XR4Kg@mail.gmail.com>
Accept-Language: sv-SE, en-US
Content-Language: sv-SE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=marcus.ihlar@ericsson.com; 
x-originating-ip: [192.176.1.88]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR0701MB2396; 6:8TbLe187TmeYhmaZSSqwnuUWPxu+q/ApwG0mQqeIzVjCGbl16vUdRc86YjdMPNxZJ2whOmvZPDuUoEvGALWpOFTWctUFTH8ToA2nYsnwK5sA0yKvDnPYqA8rqGATSHEfgO3Mmqxlv8PtgzbB5Yq6F0vWAVBfpEGqGK9KSc/riz7GNKfZ0TgtaP7L99fNK9FnEDZfmL8JNNNc25qAooY68D0fQMCg5FX7DFxWtVZ9eoCps+FSL7iqTiHUSsvVwm5EYWv7wfamalrLkmeJ5EbU2eX39Dqe+zn3OCyd0NqaMxRsoYQslO7e68m532/X3vJp2skbE05bRmrM+uD7BA6Mbb6wwv37oaLca2MoT3BowE0Gmtx+1qg2pufUaZFWzW5x85BARyDI6lVSJp0agmEQU6BD3y6oZub8GIr4lHtMSId5GgcKkGJIOCWpYj+W5l0ec1cLt9ytDubagABKttrljQ==; 5:ozLPrK9mjcjt4dA6T8kFR/b6KpefiFMcNLv4sjPMgUUTroqGo729Vv5WfKfnL6R9hXHm1xqIH6n/0mZWlm2AX2o5EsynPDa6wapMJMrxNgTSWX+8DLtkVvQJvWvHh8mrZSlb6twRmWkmvrvjuCu5cRcxSI1VTlNJETp3aBbfK+0=; 7:lz9XfkVxB25dLMl0gr1dG8WKkfc92MQWWHpKQpieOVoORA/vhcI+YnZT6229acoLl5Y9w7L1cyP5ytd3ntb1xfyU+eR8UwZKNg1Rw6a5TdCROxRVVuKkz2TAQxIHQeGbOsSmg7FEUk11OYxa8SIaoQ==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 852d5946-3fe3-448a-a2f6-08d63f2dfca4
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:HE1PR0701MB2396; 
x-ms-traffictypediagnostic: HE1PR0701MB2396:
x-microsoft-antispam-prvs: <HE1PR0701MB23963852ED9F160CE67A3756E2CD0@HE1PR0701MB2396.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(85827821059158)(158342451672863);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(3231382)(944501410)(52105095)(148016)(149066)(150057)(6041310)(20161123564045)(20161123562045)(20161123558120)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051)(76991095); SRVR:HE1PR0701MB2396; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0701MB2396; 
x-forefront-prvs: 084285FC5C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(396003)(346002)(376002)(366004)(136003)(189003)(199004)(6116002)(7736002)(71190400001)(44832011)(486006)(39060400002)(6506007)(71200400001)(66066001)(8676002)(81156014)(81166006)(26005)(6606003)(446003)(476003)(11346002)(97736004)(86362001)(3846002)(53546011)(186003)(5660300001)(7696005)(25786009)(76176011)(2906002)(316002)(9686003)(55016002)(68736007)(53936002)(256004)(93886005)(4326008)(19627405001)(6436002)(74316002)(54896002)(54906003)(99286004)(478600001)(110136005)(8936002)(105586002)(14454004)(33656002)(5250100002)(2900100001)(106356001)(102836004); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0701MB2396; H:HE1PR0701MB2393.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: +XOGVoUcg6iU5ZMstPyvHB2S1KuIe0/HZ8WWKn1I6RYuGqIg4X1yLn5kY84flFijsiDu65bxeuL7Uz0uiS/cAIkeR/zsJDhWsAGOaCFH2MB2yPlx3ykGWta60ynPqnm0RFq0x8mDKnBgz2eHkCAqy4DYQ1iirdXgPyylxCd4VX6TDtQn6EHQ4k+5mP2CdrEpxnqHEHji/JHF6p6hr6DVC1P8V6J0UY5SpFgCKBd684sZkeilwoLzCZuYhzTmkA6xEZDs1zedfuxTzvPIipGhybs/lutNsbJtZqgmlA3AOZCCEPyEi9w/PE2OgfZEMRRv3J32b2vWih5LDN5WrkMyyWUeVa/QTwWscZhLUjuuGN0=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HE1PR0701MB23938B01BC31888DAC3629B8E2CD0HE1PR0701MB2393_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 852d5946-3fe3-448a-a2f6-08d63f2dfca4
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Oct 2018 12:40:06.3189 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2396
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Sa0hUURDHPXufPpaO70kRakEqTc21aIlII5AtkQwjQ4O85UUlX9w1TT/Y RqnkGllq6Zr5JKXEdA3TFEIRxEdZmqb5fhGZZZYVZmpe7wZ++83Mf+Y/czgsYdVCObCRMfG8 EMNFKWgzMv/s80S3ytKhkH1Z3XaqpSxalX2tgFF9WUynVJ/bdIwqs9jch1Jnp3VR6kb9KKP+ kNdJqsvLl2Xqmfp2IoAKNjscxkdFJvCCx5FQs4imkpS4h0FXFhZHaC2aP52BWBbwflgzJGQg M9YKtyGorZunpOAXgqWVdlkGMpWCgiWFVCiXwWRmj0wMSJxFQE9fKilV7ssgM7uKklpmEKTO OotMY3foHtXRIttgf9BWZJMiE1iA0vrpTbbe2KOk57dRcwDuGF4Z2Re0c482Z5LYGYZWBhmR 5TgUFu4aCMl4HMFIZy0tHmSKT4GhJVHUIOwE47/HjF728KNwYvMcwBjKm3sIiW3h0/QaJbYi fA7+DMdJ6R3wtbCLltgJeot0SLQCPEhD+9RNY68bfMvNNbI/rOqXaEnUgeDGmykkPfBeyPzl ImliIa26C0nsB98r7zFZyFO/ZT2JY+FP02tCv3mmJXTkz5D6jUkE3gNPX3hIkp2Qo5tkJN4N qQ8Kma35YsQ8RrYaXnMhOlzp5c4LkRc1mtgY9xg+3oA2PlbLsxXnBtQ3f7QVYRYpLOR1OUMh VhSXoEmKbkXAEgobeXPRRkoexiUl80LseeFyFK9pRY4sqbCXTx6sC7bC4Vw8f4nn43jhf1XG mjpokVd1vSUXeCYo5y23zMx6K5VE1faqkyW3WTetSWNAhoWs5mS34F1hl76g8trVe/V9YXf7 +rz5MccCT936R1ddWMO7/mGTYodDSgfnsr/bOnxOzPUztJ/S3zVgVDtQU7s6kfJz4CX3ZNh6 2TewM+R6cl4cp47gom/lHRprchw7XqYgNRGcpwshaLh/dJjINlQDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/J_g5akbhcLiWRHTNQcKigrhhbNo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 12:40:14 -0000

--_000_HE1PR0701MB23938B01BC31888DAC3629B8E2CD0HE1PR0701MB2393_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgS2F6dWhvLA0KDQpJIGJlbGlldmUgdGhlIGJpZ2dlc3QgZGlmZmVyZW5jZSBpcyB0aGUgc2l6
ZSBvZiB0aGUgaGlkZGVuIG5ldHdvcmsgc2VnbWVudC4NCg0KSW4gdGhlIE5BVCBjYXNlIHRoZSBj
bGllbnQgYW5kIE5BVCBhcmUgc3RpbGwgaW4gdGhlIHNhbWUgY291bnRyeSBvciBjb250aW5lbnQu
DQoNCkEgcXVpY2sgZ2xhY25lIGF0IGRpc3RhbmNlY2FsY3VsYXRvci5uZXQgc2hvd3MgdGhhdCB0
aGUgY2l0eSBmYXJ0aGVzdCBmcm9tIFRva3lvIGluIEphcGFuIGlzIE5haGEtU2hpLCBhdCAxNTU0
IGttLg0KDQpUaGF0IHRyYW5zbGF0ZXMgdG8gcm91Z2hseSA1bXMgYXQgdGhlIHNwZWVkIG9mIGxp
Z2h0LCBzbyB0aGUga2luZHMgb2YgbWVhc3VyZW1lbnRzIHRvIGRldGVybWluZSBkaXN0YW5jZSBm
cm9tIFRva3lvIGJhc2VkIG9uIFJUVCB3aWxsIGJlIGV4dHJlbWVseSBzZW5zaXRpdmUgYW5kIGVy
cm9yIHByb25lLg0KDQpQbGVhc2Ugbm90ZSB0aGF0IHRoZSBkaXN0YW5jZSBhbmFseWlzIGNhbiBi
ZSBwZXJmb3JtZWQgb24gaGFuZHNoYWtlIFJUVCBhcyB3ZWxsLCBmb3IgY29ubmVjdGlvbnMgd2hl
cmUgdGhlIGluaXRpYWwgaGFuZHNoYWtlIGlzIHZpc2libGUgYXQgdGhlIG1lYXN1cmVtZW50IHBv
aW50Lg0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpGcsOlbjogUVVJQyA8
cXVpYy1ib3VuY2VzQGlldGYub3JnPiBmw7ZyIEthenVobyBPa3UgPGthenVob29rdUBnbWFpbC5j
b20+DQpTa2lja2F0OiBkZW4gMzEgb2t0b2JlciAyMDE4IDExOjIwDQpUaWxsOiBDaHJpc3RpYW4g
SHVpdGVtYQ0KS29waWE6IExhcnMgRWdnZXJ0OyBJRVRGIFFVSUMgV0c7IERtaXRyaSBUaWtob25v
dg0Kw4RtbmU6IFJlOiBTdHJ1Y3R1cmluZyB0aGUgQktLIHNwaW4gYml0IGRpc2N1c3Npb24NCg0K
MjAxOOW5tDEw5pyIMzDml6Uo54GrKSAxOjU0IENocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1
aXRlbWEubmV0PjoNCj4NCj4NCj4NCj4gPiBPbiBPY3QgMjksIDIwMTgsIGF0IDk6MDggQU0sIERt
aXRyaSBUaWtob25vdiA8ZHRpa2hvbm92QGxpdGVzcGVlZHRlY2guY29tPiB3cm90ZToNCj4gPg0K
PiA+PiBPbiBNb24sIE9jdCAyOSwgMjAxOCBhdCAwNToyNjozNFBNICswMjAwLCBMYXJzIEVnZ2Vy
dCB3cm90ZToNCj4gPj4gV2UnZCBzcGVjaWZpY2FsbHkgbGlrZSB0byBhc2sgY2xpZW50IGFuZCBz
ZXJ2ZXIgaW1wbGVtZW50b3JzIHdpdGgNCj4gPj4gcHJvamVjdGVkIHNpemFibGUgZGVwbG95bWVu
dHMgdG8gaW5kaWNhdGUgd2hldGhlciB0aGV5IGludGVudCB0bw0KPiA+PiBpbXBsZW1lbnQgYW5k
IGRlcGxveSwgaWYgdGhlIFdHIGRlY2lkZWQgdG8gaW5jbHVkZSB0aGUgc3Bpbi1iaXQgaW4NCj4g
Pj4gdGhlIHNwZWMuDQo+ID4NCj4gPiBMaXRlU3BlZWQgVGVjaG5vbG9naWVzIHdpbGwgc3VwcG9y
dCB0aGUgc3BpbiBiaXQgLS0gYm90aCBpbiBvdXINCj4gPiBzZXJ2ZXIgYW5kIGNsaWVudCBRVUlD
IGltcGxlbWVudGF0aW9ucyAtLSBpZiBpdCBtYWtlIGl0IGludG8gdGhlDQo+ID4gZHJhZnQuDQo+
DQo+IE15IGltcGxlbWVudGF0aW9uIGlzIG5vdCB1c2VkIGluIGFueSBsYXJnZSBzY2FsZSBkZXBs
b3ltZW50LCBidXQgaXQgZG9lcyBzdXBwb3J0IHRoZSBzcGluIGJpdC4gSW4gZmFjdCwgaXQgaGFz
IGNvbmZpZ3VyYXRpb24gb3B0aW9ucyB0byBzdXBwb3J0IHNwaW4gYml0IHZhcmlhbnRzOiBub2Rl
LCBqdXN0IHNwaW4sIHNwaW4gKyB2ZWMsIHNwaW4gKyBRUi4NCj4NCj4gSSB0aGluayB0aGUgc3Ry
b25nZXN0IG9iamVjdGlvbiB0byB0aGUgc3BpbiBiaXQgd2FzIHB1dCB1cCBieSBNYXJ0ZW4gZHVy
aW5nIHRoZSBsYXN0IGludGVyaW06IG1lYXN1cmluZyB0aGUgUlRUIHdpdGggdGhlIHNwaW4gYml0
IGRpc2Nsb3NlcyB0aGUgdXNlIG9mIGhpZGRlbiBwYXRoIHNlZ21lbnRzIGxpa2UgVlBOLiBUaGlz
IGlzc3VlIHdhcyBub3QgZGlzY3Vzc2VkIGR1cmluZyB0aGUgcHJpdmFjeSBhbmFseXNpcy4NCg0K
TWF5IEkgYXNrIGlmIHRoZSBWUE4gdXNlcnMgYXJlIHRoZSBvbmx5IG9uZXMgdGhhdCBsb3NlIHNv
bWUgcHJpdmFjeQ0Kd2l0aCBzcGluIGJpdHM/DQoNCkkgYXNrIHRoaXMgYmVjYXVzZSBJIGxpdmUg
aW4gYSBjb3VudHJ5IHdoZXJlIElJVUMgdGhlIG1vYmlsZSBjYXJyaWVycw0KcGxhY2UgdGhlaXIg
bmF0aW9uLXdpZGUgY2Fycmllci1ncmFkZSBOQVQgbmVhciB0aGUgY2FwaXRhbCBjaXR5IChpLmUu
LA0KVG9reW8pLiBUaGF0IG1lYW5zIHRoYXQgZm9yIHBlb3BsZSBsaXZpbmcgaW4gdGhlIGNvdW50
cnksIGhhdmluZyBzcGluDQpiaXRzIHR1cm5lZCBvbiBjb3VsZCByZXZlYWwgdGhlaXIgZGlzdGFu
Y2UgZnJvbSBUb2t5by4NCg0KU28gdGhlIHF1ZXN0aW9uIGlzOiBpZiBWUE4gdXNlcnMgbmVlZCBz
cGVjaWFsIGNhcmUsIGRvIHNvbWUgTkFUIHVzZXJzDQphcyB3ZWxsPyBPciBpZiB0aGUgYW5zd2Vy
IGlzIG5vLCB3aGF0IGlzIHRoZSBkaWZmZXJlbmNlIGZyb20gYmV0d2Vlbg0KdGhlIHR3byBncm91
cHM/DQoNCkdlbmVyYWxseSBzcGVha2luZywgSSBhbSBub3QgYWdhaW5zdCBnaXZpbmcgdXNlcnMg
dGhlIGZyZWVkb20gdG8NCmV4cG9zZSBzcGluIGJpdHMsIGhvd2V2ZXIgSSBhbSB3b25kZXJpbmcg
aG93IHRoZSBlbmRwb2ludHMgc2hvdWxkDQpwcm92aWRlIHRoZSBmcmVlZG9tIG9mIGNob2ljZSAo
VUkgcXVlc3Rpb24pIGFzIHdlbGwgYXMgd2hhdCB0aGUNCmRlZmF1bHQgc2hvdWxkIGJlLg0KDQo+
DQo+IFRoZSBwcml2YWN5IGlzc3VlIGNvdWxkIGJlIG1pdGlnYXRlZCBieSB0dXJuaW5nIG9mZiB0
aGUgc3BpbiBiaXQgYXQgcHJpdmFjeSBzZW5zaXRpdmUgY2xpZW50cywgYnV0IHRoaXMgd291bGQg
bWFrZSB0aGVzZSBjbGllbnRzICJzdGljayBvdXQiLg0KPg0KPiBPbmUgc29sdXRpb24gd291bGQg
YmUgdG8gcmVtb3ZlIHRoZSBzcGluIGJpdCBmcm9tIHRoZSBzcGVjLCB0cmFkaW5nIG9mZiBiZXR0
ZXIgcHJpdmFjeSBmb3Igd29yc2UgbWFuYWdlbWVudC4gSSBhbSBjb25zaWRlcmluZyBhbm90aGVy
IHNvbHV0aW9uIGluIHdoaWNoIHByaXZhY3kgc2Vuc2l0aXZlIGNsaWVudHMgaGlkZSB0aGUgUlRU
IGJ5IGNvbnRyb2xsaW5nIHRoZSBzcGluLCBmb3IgZXhhbXBsZSBzcGlubmluZyBhdCBmaXhlZCBp
bnRlcnZhbHMuIEkgcGxhbiB0ZXN0aW5nIHRoYXQgb3B0aW9uIGluIFBpY29xdWljLg0KPg0KPiAt
LSBDaHJpc3RpYW4gSHVpdGVtYQ0KPg0KPg0KDQoNCi0tDQpLYXp1aG8gT2t1DQoNCg==

--_000_HE1PR0701MB23938B01BC31888DAC3629B8E2CD0HE1PR0701MB2393_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxzdHlsZSB0eXBlPSJ0ZXh0L2NzcyIgc3R5bGU9
ImRpc3BsYXk6bm9uZTsiPjwhLS0gUCB7bWFyZ2luLXRvcDowO21hcmdpbi1ib3R0b206MDt9IC0t
Pjwvc3R5bGU+DQo8L2hlYWQ+DQo8Ym9keSBkaXI9Imx0ciI+DQo8ZGl2IGlkPSJkaXZ0YWdkZWZh
dWx0d3JhcHBlciIgc3R5bGU9ImZvbnQtc2l6ZToxMnB0O2NvbG9yOiMwMDAwMDA7Zm9udC1mYW1p
bHk6Q2FsaWJyaSxIZWx2ZXRpY2Esc2Fucy1zZXJpZjsiIGRpcj0ibHRyIj4NCjxwIHN0eWxlPSJt
YXJnaW4tdG9wOjA7bWFyZ2luLWJvdHRvbTowIj5IaSBLYXp1aG8sPC9wPg0KPHAgc3R5bGU9Im1h
cmdpbi10b3A6MDttYXJnaW4tYm90dG9tOjAiPkkgYmVsaWV2ZSB0aGUgYmlnZ2VzdCBkaWZmZXJl
bmNlIGlzIHRoZSBzaXplIG9mIHRoZSBoaWRkZW4gbmV0d29yayBzZWdtZW50Lg0KPGJyPg0KPC9w
Pg0KPHAgc3R5bGU9Im1hcmdpbi10b3A6MDttYXJnaW4tYm90dG9tOjAiPkluIHRoZSBOQVQgY2Fz
ZSB0aGUgY2xpZW50IGFuZCBOQVQgYXJlIHN0aWxsIGluIHRoZSBzYW1lIGNvdW50cnkgb3IgY29u
dGluZW50Lg0KPGJyPg0KPC9wPg0KPHAgc3R5bGU9Im1hcmdpbi10b3A6MDttYXJnaW4tYm90dG9t
OjAiPkEgcXVpY2sgZ2xhY25lIGF0IGRpc3RhbmNlY2FsY3VsYXRvci5uZXQgc2hvd3MgdGhhdCB0
aGUgY2l0eSBmYXJ0aGVzdCBmcm9tIFRva3lvIGluIEphcGFuIGlzIE5haGEtU2hpLCBhdCAxNTU0
IGttLg0KPGJyPg0KPC9wPg0KPHAgc3R5bGU9Im1hcmdpbi10b3A6MDttYXJnaW4tYm90dG9tOjAi
PlRoYXQgdHJhbnNsYXRlcyB0byByb3VnaGx5IDVtcyBhdCB0aGUgc3BlZWQgb2YgbGlnaHQsIHNv
IHRoZSBraW5kcyBvZiBtZWFzdXJlbWVudHMgdG8gZGV0ZXJtaW5lIGRpc3RhbmNlIGZyb20gVG9r
eW8gYmFzZWQgb24gUlRUIHdpbGwgYmUgZXh0cmVtZWx5IHNlbnNpdGl2ZSBhbmQgZXJyb3IgcHJv
bmUuPC9wPg0KPHAgc3R5bGU9Im1hcmdpbi10b3A6MDttYXJnaW4tYm90dG9tOjAiPlBsZWFzZSBu
b3RlIHRoYXQgdGhlIGRpc3RhbmNlIGFuYWx5aXMgY2FuIGJlIHBlcmZvcm1lZCBvbiBoYW5kc2hh
a2UgUlRUIGFzIHdlbGwsIGZvciBjb25uZWN0aW9ucyB3aGVyZSB0aGUgaW5pdGlhbCBoYW5kc2hh
a2UgaXMgdmlzaWJsZSBhdCB0aGUgbWVhc3VyZW1lbnQgcG9pbnQuDQo8YnI+DQo8L3A+DQo8YnI+
DQo8YnI+DQo8ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyI+DQo8aHIgc3R5bGU9ImRp
c3BsYXk6aW5saW5lLWJsb2NrO3dpZHRoOjk4JSIgdGFiaW5kZXg9Ii0xIj4NCjxkaXYgaWQ9ImRp
dlJwbHlGd2RNc2ciIGRpcj0ibHRyIj48Zm9udCBzdHlsZT0iZm9udC1zaXplOjExcHQiIGZhY2U9
IkNhbGlicmksIHNhbnMtc2VyaWYiIGNvbG9yPSIjMDAwMDAwIj48Yj5GcsOlbjo8L2I+IFFVSUMg
Jmx0O3F1aWMtYm91bmNlc0BpZXRmLm9yZyZndDsgZsO2ciBLYXp1aG8gT2t1ICZsdDtrYXp1aG9v
a3VAZ21haWwuY29tJmd0Ozxicj4NCjxiPlNraWNrYXQ6PC9iPiBkZW4gMzEgb2t0b2JlciAyMDE4
IDExOjIwPGJyPg0KPGI+VGlsbDo8L2I+IENocmlzdGlhbiBIdWl0ZW1hPGJyPg0KPGI+S29waWE6
PC9iPiBMYXJzIEVnZ2VydDsgSUVURiBRVUlDIFdHOyBEbWl0cmkgVGlraG9ub3Y8YnI+DQo8Yj7D
hG1uZTo8L2I+IFJlOiBTdHJ1Y3R1cmluZyB0aGUgQktLIHNwaW4gYml0IGRpc2N1c3Npb248L2Zv
bnQ+DQo8ZGl2PiZuYnNwOzwvZGl2Pg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJCb2R5RnJhZ21lbnQi
Pjxmb250IHNpemU9IjIiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTFwdDsiPg0KPGRpdiBjbGFz
cz0iUGxhaW5UZXh0Ij4yMDE45bm0MTDmnIgzMOaXpSjngaspIDE6NTQgQ2hyaXN0aWFuIEh1aXRl
bWEgJmx0O2h1aXRlbWFAaHVpdGVtYS5uZXQmZ3Q7Ojxicj4NCiZndDs8YnI+DQomZ3Q7PGJyPg0K
Jmd0Ozxicj4NCiZndDsgJmd0OyBPbiBPY3QgMjksIDIwMTgsIGF0IDk6MDggQU0sIERtaXRyaSBU
aWtob25vdiAmbHQ7ZHRpa2hvbm92QGxpdGVzcGVlZHRlY2guY29tJmd0OyB3cm90ZTo8YnI+DQom
Z3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsmZ3Q7IE9uIE1vbiwgT2N0IDI5LCAyMDE4IGF0IDA1OjI2
OjM0UE0gJiM0MzswMjAwLCBMYXJzIEVnZ2VydCB3cm90ZTo8YnI+DQomZ3Q7ICZndDsmZ3Q7IFdl
J2Qgc3BlY2lmaWNhbGx5IGxpa2UgdG8gYXNrIGNsaWVudCBhbmQgc2VydmVyIGltcGxlbWVudG9y
cyB3aXRoPGJyPg0KJmd0OyAmZ3Q7Jmd0OyBwcm9qZWN0ZWQgc2l6YWJsZSBkZXBsb3ltZW50cyB0
byBpbmRpY2F0ZSB3aGV0aGVyIHRoZXkgaW50ZW50IHRvPGJyPg0KJmd0OyAmZ3Q7Jmd0OyBpbXBs
ZW1lbnQgYW5kIGRlcGxveSwgaWYgdGhlIFdHIGRlY2lkZWQgdG8gaW5jbHVkZSB0aGUgc3Bpbi1i
aXQgaW48YnI+DQomZ3Q7ICZndDsmZ3Q7IHRoZSBzcGVjLjxicj4NCiZndDsgJmd0Ozxicj4NCiZn
dDsgJmd0OyBMaXRlU3BlZWQgVGVjaG5vbG9naWVzIHdpbGwgc3VwcG9ydCB0aGUgc3BpbiBiaXQg
LS0gYm90aCBpbiBvdXI8YnI+DQomZ3Q7ICZndDsgc2VydmVyIGFuZCBjbGllbnQgUVVJQyBpbXBs
ZW1lbnRhdGlvbnMgLS0gaWYgaXQgbWFrZSBpdCBpbnRvIHRoZTxicj4NCiZndDsgJmd0OyBkcmFm
dC48YnI+DQomZ3Q7PGJyPg0KJmd0OyBNeSBpbXBsZW1lbnRhdGlvbiBpcyBub3QgdXNlZCBpbiBh
bnkgbGFyZ2Ugc2NhbGUgZGVwbG95bWVudCwgYnV0IGl0IGRvZXMgc3VwcG9ydCB0aGUgc3BpbiBi
aXQuIEluIGZhY3QsIGl0IGhhcyBjb25maWd1cmF0aW9uIG9wdGlvbnMgdG8gc3VwcG9ydCBzcGlu
IGJpdCB2YXJpYW50czogbm9kZSwganVzdCBzcGluLCBzcGluICYjNDM7IHZlYywgc3BpbiAmIzQz
OyBRUi48YnI+DQomZ3Q7PGJyPg0KJmd0OyBJIHRoaW5rIHRoZSBzdHJvbmdlc3Qgb2JqZWN0aW9u
IHRvIHRoZSBzcGluIGJpdCB3YXMgcHV0IHVwIGJ5IE1hcnRlbiBkdXJpbmcgdGhlIGxhc3QgaW50
ZXJpbTogbWVhc3VyaW5nIHRoZSBSVFQgd2l0aCB0aGUgc3BpbiBiaXQgZGlzY2xvc2VzIHRoZSB1
c2Ugb2YgaGlkZGVuIHBhdGggc2VnbWVudHMgbGlrZSBWUE4uIFRoaXMgaXNzdWUgd2FzIG5vdCBk
aXNjdXNzZWQgZHVyaW5nIHRoZSBwcml2YWN5IGFuYWx5c2lzLjxicj4NCjxicj4NCk1heSBJIGFz
ayBpZiB0aGUgVlBOIHVzZXJzIGFyZSB0aGUgb25seSBvbmVzIHRoYXQgbG9zZSBzb21lIHByaXZh
Y3k8YnI+DQp3aXRoIHNwaW4gYml0cz88YnI+DQo8YnI+DQpJIGFzayB0aGlzIGJlY2F1c2UgSSBs
aXZlIGluIGEgY291bnRyeSB3aGVyZSBJSVVDIHRoZSBtb2JpbGUgY2FycmllcnM8YnI+DQpwbGFj
ZSB0aGVpciBuYXRpb24td2lkZSBjYXJyaWVyLWdyYWRlIE5BVCBuZWFyIHRoZSBjYXBpdGFsIGNp
dHkgKGkuZS4sPGJyPg0KVG9reW8pLiBUaGF0IG1lYW5zIHRoYXQgZm9yIHBlb3BsZSBsaXZpbmcg
aW4gdGhlIGNvdW50cnksIGhhdmluZyBzcGluPGJyPg0KYml0cyB0dXJuZWQgb24gY291bGQgcmV2
ZWFsIHRoZWlyIGRpc3RhbmNlIGZyb20gVG9reW8uPGJyPg0KPGJyPg0KU28gdGhlIHF1ZXN0aW9u
IGlzOiBpZiBWUE4gdXNlcnMgbmVlZCBzcGVjaWFsIGNhcmUsIGRvIHNvbWUgTkFUIHVzZXJzPGJy
Pg0KYXMgd2VsbD8gT3IgaWYgdGhlIGFuc3dlciBpcyBubywgd2hhdCBpcyB0aGUgZGlmZmVyZW5j
ZSBmcm9tIGJldHdlZW48YnI+DQp0aGUgdHdvIGdyb3Vwcz88YnI+DQo8YnI+DQpHZW5lcmFsbHkg
c3BlYWtpbmcsIEkgYW0gbm90IGFnYWluc3QgZ2l2aW5nIHVzZXJzIHRoZSBmcmVlZG9tIHRvPGJy
Pg0KZXhwb3NlIHNwaW4gYml0cywgaG93ZXZlciBJIGFtIHdvbmRlcmluZyBob3cgdGhlIGVuZHBv
aW50cyBzaG91bGQ8YnI+DQpwcm92aWRlIHRoZSBmcmVlZG9tIG9mIGNob2ljZSAoVUkgcXVlc3Rp
b24pIGFzIHdlbGwgYXMgd2hhdCB0aGU8YnI+DQpkZWZhdWx0IHNob3VsZCBiZS48YnI+DQo8YnI+
DQomZ3Q7PGJyPg0KJmd0OyBUaGUgcHJpdmFjeSBpc3N1ZSBjb3VsZCBiZSBtaXRpZ2F0ZWQgYnkg
dHVybmluZyBvZmYgdGhlIHNwaW4gYml0IGF0IHByaXZhY3kgc2Vuc2l0aXZlIGNsaWVudHMsIGJ1
dCB0aGlzIHdvdWxkIG1ha2UgdGhlc2UgY2xpZW50cyAmcXVvdDtzdGljayBvdXQmcXVvdDsuPGJy
Pg0KJmd0Ozxicj4NCiZndDsgT25lIHNvbHV0aW9uIHdvdWxkIGJlIHRvIHJlbW92ZSB0aGUgc3Bp
biBiaXQgZnJvbSB0aGUgc3BlYywgdHJhZGluZyBvZmYgYmV0dGVyIHByaXZhY3kgZm9yIHdvcnNl
IG1hbmFnZW1lbnQuIEkgYW0gY29uc2lkZXJpbmcgYW5vdGhlciBzb2x1dGlvbiBpbiB3aGljaCBw
cml2YWN5IHNlbnNpdGl2ZSBjbGllbnRzIGhpZGUgdGhlIFJUVCBieSBjb250cm9sbGluZyB0aGUg
c3BpbiwgZm9yIGV4YW1wbGUgc3Bpbm5pbmcgYXQgZml4ZWQgaW50ZXJ2YWxzLg0KIEkgcGxhbiB0
ZXN0aW5nIHRoYXQgb3B0aW9uIGluIFBpY29xdWljLjxicj4NCiZndDs8YnI+DQomZ3Q7IC0tIENo
cmlzdGlhbiBIdWl0ZW1hPGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQo8YnI+DQo8YnI+DQotLSA8
YnI+DQpLYXp1aG8gT2t1PGJyPg0KPGJyPg0KPC9kaXY+DQo8L3NwYW4+PC9mb250PjwvZGl2Pg0K
PC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_HE1PR0701MB23938B01BC31888DAC3629B8E2CD0HE1PR0701MB2393_--


From nobody Wed Oct 31 06:05:34 2018
Return-Path: <alexandre.ferrieux@orange.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 46311130E06 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 06:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.291
X-Spam-Level: 
X-Spam-Status: No, score=-0.291 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no 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 wEZv5zD-hbAh for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 06:05:31 -0700 (PDT)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73651130DF0 for <quic@ietf.org>; Wed, 31 Oct 2018 06:05:31 -0700 (PDT)
Received: from opfednr05.francetelecom.fr (unknown [xx.xx.xx.69]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id 42lT8p0zDYzCs7f; Wed, 31 Oct 2018 14:05:30 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfednr05.francetelecom.fr (ESMTP service) with ESMTP id 42lT8p05KgzyPk; Wed, 31 Oct 2018 14:05:30 +0100 (CET)
Received: from [10.193.4.89] (10.168.234.4) by OPEXCLILM5D.corporate.adroot.infra.ftgroup (10.114.31.3) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 31 Oct 2018 14:05:28 +0100
Subject: Re: SV: Structuring the BKK spin bit discussion
To: Marcus Ihlar <marcus.ihlar@ericsson.com>
CC: Kazuho Oku <kazuhooku@gmail.com>, Christian Huitema <huitema@huitema.net>,  Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CANatvzxt-QBmeJUwp+MjtbpYXstPiEigDzQe0KfWJN+q0XR4Kg@mail.gmail.com> <HE1PR0701MB23938B01BC31888DAC3629B8E2CD0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
Reply-To: Alexandre Ferrieux <alexandre.ferrieux@orange.com>
From: <alexandre.ferrieux@orange.com>
Organization: Orange
Message-ID: <25140_1540991130_5BD9A89A_25140_398_1_1968bd4e-7c2b-36fb-47cb-af10a0aa6be9@orange.com>
Date: Wed, 31 Oct 2018 14:05:29 +0100
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <HE1PR0701MB23938B01BC31888DAC3629B8E2CD0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.168.234.4]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/w3Fvq4Ay5hWWxaGDW1xMguzl-Cg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 13:05:32 -0000

On 10/31/2018 01:40 PM, Marcus Ihlar wrote:
> 
> Please note that the distance analyis can be performed on handshake RTT as well, 
> for connections where the initial handshake is visible at the measurement point.

+1.

Moreover, the same applies to an already established connection when a new 
request fitting in a single packet is emitted by the browser after some idle 
time. Simple temporal filtering allows an on-path observer to extract those 
events even though the handshake is long over.


_________________________________________________________________________________________________________________________

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.


From nobody Wed Oct 31 07:18:50 2018
Return-Path: <ietf@trammell.ch>
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 088FF130E27 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 07:18:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 YWDep4rIZXqy for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 07:18:45 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [212.25.24.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 729C0130DCC for <quic@ietf.org>; Wed, 31 Oct 2018 07:18:45 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 137E9341C98; Wed, 31 Oct 2018 15:18:43 +0100 (CET)
X-Iway-Path: 0
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/20439.12204); Wed, 31 Oct 2018 15:18:42 +0100 (CET)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Wed, 31 Oct 2018 15:18:42 +0100 (CET)
Received: from [145.14.214.39] (account ietf@trammell.ch HELO [10.11.33.83]) by switchplus-mail.ch (CommuniGate Pro SMTP 6.2.9) with ESMTPSA id 72262924; Wed, 31 Oct 2018 15:18:42 +0100
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <D8BB0373-FDEB-4312-94E6-BBA304D595BE@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_0E4952A1-AC2D-41CB-8D48-45671CF1DDF9"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: Structuring the BKK spin bit discussion
Date: Wed, 31 Oct 2018 15:18:41 +0100
In-Reply-To: <HE1PR0701MB23938B01BC31888DAC3629B8E2CD0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
Cc: Kazuho Oku <kazuhooku@gmail.com>, Christian Huitema <huitema@huitema.net>,  Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Marcus Ihlar <marcus.ihlar@ericsson.com>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CANatvzxt-QBmeJUwp+MjtbpYXstPiEigDzQe0KfWJN+q0XR4Kg@mail.gmail.com> <HE1PR0701MB23938B01BC31888DAC3629B8E2CD0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/PhtjEpHaKFLdf5ThNprkV_7M02c>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 14:18:49 -0000

--Apple-Mail=_0E4952A1-AC2D-41CB-8D48-45671CF1DDF9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

hi Kazuho, Marcus,

+1 to this; the intra-network latency variation on the mobile segment of =
the mobile networks we looked at via the MONROE in the testbed in our =
PAM paper the followed from the RTT DT work (see =
https://github.com/mami-project/rtt-privacy-paper/blob/master/rtt-privacy.=
pdf, especially section 3.1 and figure 2(b)) makes RTT measurement on a =
mobile network useless for geolocation.

We did notice (not shown in the paper) that different carriers (n =3D 4, =
if I recall correctly) had distinct latency distributions, so with =
traffic from all Japanese mobile users you could probably use RTT data =
in the aggregate to build a "carrier classifier". This is of course a =
useless exercise because you can already tell which carrier a subscriber =
is coming from by looking at the IP address of the CGNAT exit.

IMO there are only a few edge cases where there are actual potential =
geoprivacy issues raised by the spin bit with respect to tunneled VPN =
traffic. All of these involve trans- or intercontinental tunnels (>30ms =
of additional RTT, for 3000km of location uncertainty -- how far is it =
from Okinawa to Hokkaido?). In every case the handshake latency gives =
you away as well, but in every case long RTTs might also have =
non-distance related causes. So while I see disabling the spin bit as a =
necessary feature, especially for clients to have, IMO its utility is =
more useful for peace of mind and information reduction than for actual =
information elimination.

Cheers,

Brian

> On 31 Oct 2018, at 13:40, Marcus Ihlar <marcus.ihlar@ericsson.com> =
wrote:
>=20
> Hi Kazuho,
> I believe the biggest difference is the size of the hidden network =
segment.
> In the NAT case the client and NAT are still in the same country or =
continent.
> A quick glacne at distancecalculator.net shows that the city farthest =
from Tokyo in Japan is Naha-Shi, at 1554 km.
> That translates to roughly 5ms at the speed of light, so the kinds of =
measurements to determine distance from Tokyo based on RTT will be =
extremely sensitive and error prone.
> Please note that the distance analyis can be performed on handshake =
RTT as well, for connections where the initial handshake is visible at =
the measurement point.
>=20
>=20
> Fr=C3=A5n: QUIC <quic-bounces@ietf.org> f=C3=B6r Kazuho Oku =
<kazuhooku@gmail.com>
> Skickat: den 31 oktober 2018 11:20
> Till: Christian Huitema
> Kopia: Lars Eggert; IETF QUIC WG; Dmitri Tikhonov
> =C3=84mne: Re: Structuring the BKK spin bit discussion
>=20
> 2018=E5=B9=B410=E6=9C=8830=E6=97=A5(=E7=81=AB) 1:54 Christian Huitema =
<huitema@huitema.net>:
> >
> >
> >
> > > On Oct 29, 2018, at 9:08 AM, Dmitri Tikhonov =
<dtikhonov@litespeedtech.com> wrote:
> > >
> > >> On Mon, Oct 29, 2018 at 05:26:34PM +0200, Lars Eggert wrote:
> > >> We'd specifically like to ask client and server implementors with
> > >> projected sizable deployments to indicate whether they intent to
> > >> implement and deploy, if the WG decided to include the spin-bit =
in
> > >> the spec.
> > >
> > > LiteSpeed Technologies will support the spin bit -- both in our
> > > server and client QUIC implementations -- if it make it into the
> > > draft.
> >
> > My implementation is not used in any large scale deployment, but it =
does support the spin bit. In fact, it has configuration options to =
support spin bit variants: node, just spin, spin + vec, spin + QR.
> >
> > I think the strongest objection to the spin bit was put up by Marten =
during the last interim: measuring the RTT with the spin bit discloses =
the use of hidden path segments like VPN. This issue was not discussed =
during the privacy analysis.
>=20
> May I ask if the VPN users are the only ones that lose some privacy
> with spin bits?
>=20
> I ask this because I live in a country where IIUC the mobile carriers
> place their nation-wide carrier-grade NAT near the capital city (i.e.,
> Tokyo). That means that for people living in the country, having spin
> bits turned on could reveal their distance from Tokyo.
>=20
> So the question is: if VPN users need special care, do some NAT users
> as well? Or if the answer is no, what is the difference from between
> the two groups?
>=20
> Generally speaking, I am not against giving users the freedom to
> expose spin bits, however I am wondering how the endpoints should
> provide the freedom of choice (UI question) as well as what the
> default should be.
>=20
> >
> > The privacy issue could be mitigated by turning off the spin bit at =
privacy sensitive clients, but this would make these clients "stick =
out".
> >
> > One solution would be to remove the spin bit from the spec, trading =
off better privacy for worse management. I am considering another =
solution in which privacy sensitive clients hide the RTT by controlling =
the spin, for example spinning at fixed intervals. I plan testing that =
option in Picoquic.
> >
> > -- Christian Huitema
> >
> >
>=20
>=20
> --
> Kazuho Oku


--Apple-Mail=_0E4952A1-AC2D-41CB-8D48-45671CF1DDF9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAlvZucEACgkQihK3vwvq
RqO/bRAAiM66SMfZE/Jk1jR+XzK+MRZGHWref4Wdg5FfrnSBI8J8T/J7bKRmRdKS
1rF78BBuBptRESN8lVJzyZdbMg/ysDj7u5bhHamaUxlunTzOk54AOM8/FToYrE0Y
A2EWxxDpVNAEZs92vCfgJBZDJagy8Ts82Y3XoYIf3rJOcDyCadVD5+78FfSdjlme
6RL59rdNC1L3Qgmka0ELz8LDOPeSjOlo6TSd75nzwXjDOfEsw6ZhqXLkSWW3TE5F
XPEOSJeTaFhlOnxii0Iv9nXRWR6lOwAQCOaDXrARB0b7m1OORutRCycVI7uh5ASP
XFzMszPLhFgeqvwcoqNQzbxAKOIntPYpEtqw5GTWvkMBhX0SKFP+/JKxG1Q09ZI6
9mJf4lOaw+D+htAS+HDFgU+uqzmtERI/KH4LV3qC3MrcqhBs9HT3ZvToSqP/FD2c
NK2nIvCwXGu0c5jSK3SEG5PXF3dKwYoJegMsDYRrvmGDG2j1LOe99xL5ZGEZINVD
/simjXzcXhL4DcTNEVEA3QrvQAfag+9qXl7DPMP4F9w76rYjqVdwD+cKGtxeillw
xlrEDF28XLxezIK9sjyHDGe8looFPGPlAZ4hm6e+Yr/d9ErsgV8NeH02Sda7gCqo
BQQIybty0nuUFrKeBQuwMlRf6Ii0OC+dSMVgLEBkbHrJgSQ1+jY=
=Or0j
-----END PGP SIGNATURE-----

--Apple-Mail=_0E4952A1-AC2D-41CB-8D48-45671CF1DDF9--


From nobody Wed Oct 31 08:06:46 2018
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
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 5AA8B128D68 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 08:06:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 QBe611migxRr for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 08:06:42 -0700 (PDT)
Received: from virgo01.ee.ethz.ch (virgo01.ee.ethz.ch [129.132.2.226]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E3931252B7 for <quic@ietf.org>; Wed, 31 Oct 2018 08:06:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by virgo01.ee.ethz.ch (Postfix) with ESMTP id 42lWrc5zxSzMmj9 for <quic@ietf.org>; Wed, 31 Oct 2018 16:06:40 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at virgo01.ee.ethz.ch
Received: from virgo01.ee.ethz.ch ([127.0.0.1]) by localhost (virgo01.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8EpOIrhiizUl for <quic@ietf.org>; Wed, 31 Oct 2018 16:06:35 +0100 (CET)
X-MtScore: NO score=0
Received: from [192.168.178.24] (mue-88-130-61-252.dsl.tropolys.de [88.130.61.252]) by virgo01.ee.ethz.ch (Postfix) with ESMTPSA for <quic@ietf.org>; Wed, 31 Oct 2018 16:06:35 +0100 (CET)
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: [quicwg/base-drafts] Add an appendix describing spin negotiation (#1937)
Date: Wed, 31 Oct 2018 16:06:33 +0100
References: <quicwg/base-drafts/pull/1937@github.com> <quicwg/base-drafts/pull/1937/review/170290167@github.com>
To: quic@ietf.org
In-Reply-To: <quicwg/base-drafts/pull/1937/review/170290167@github.com>
Message-Id: <FBF0F47E-64E0-4E51-B6C0-B277811756C9@tik.ee.ethz.ch>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ICYHHXu77M_aOIdpgBmiD9LoHuc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 15:06:44 -0000

Ah, never mind. Now I got it...

> Am 31.10.2018 um 15:44 schrieb mirjak <notifications@github.com>:
>=20
> @mirjak commented on this pull request.
>=20
> In draft-ietf-quic-spin-exp.md:
>=20
> > +usage of the spin bit described in the main body of this document:
> +
> +- It provides a method to exercise version negotiation beyond the =
version
> +  greasing mechanism described in section 15 of {{QUIC-TRANSPORT}}. =
This
> +  additional exercise has the benefit of actually changing the =
protocol's
> +  behavior in a way each endpoint can detect based on the negotiation =
of the
> +  version, and may defend against ossification of the version =
negotiation
> +  mechanism caused both by on-path interference as well as lazy =
implementations
> +  better than greasing alone.
> +
> +- It provides a method by which on-path devices that observe the =
handshake can
> +  explicitly classify a connection as spinning or not.
> +
> +## The Spin Bit in Spinless QUIC {#nospin}
> +
> +When version Vt is negotiated, both client and server randomly select =
a "pin
>=20
> "pin" or "spin"...?
>=20
> =E2=80=94
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
>=20


From nobody Wed Oct 31 09:01:16 2018
Return-Path: <ianswett@google.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 E8C96130DDF for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 09:01:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.511
X-Spam-Level: 
X-Spam-Status: No, score=-15.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 fx37ltH7nt1L for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 09:01:08 -0700 (PDT)
Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (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 20D05130DDA for <quic@ietf.org>; Wed, 31 Oct 2018 09:01:08 -0700 (PDT)
Received: by mail-wr1-x42d.google.com with SMTP id n5-v6so17053624wrw.12 for <quic@ietf.org>; Wed, 31 Oct 2018 09:01:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ywPspWzVzySLY25CoDX0m+jBQEvj1UCO/fwKfQdw2Bs=; b=BAgDSrfCV2iPNlvZHeqwT5iNr+fwGhvPtScalm+EvkmzhamV8+TDT97ZS9R3vvKjJs nSl2/qCVIUfHZH0uhSz9yKob+xdPbVjFSQ7V8o01qnOZuwgScKoT/aDku0i7Ncm7f1hu ZTcJeT4YV19pxBCEQ0e37WCECfDtvqKdZNVbodyEJHw/nmuVrNUi4XjO8KpAwR1M5DB8 50n80CSMLdhLj7DbG0ljyJabTL/skImF5jGicJTIINVt3+9kSVXRQLtDSQuVo70Clwdg bWUdc3PYPfji9+EX1FocLNRP4W8ERtiiC8UGdd2S8i8NFdA9cdUexVJ3s7Dc3coR2mcQ S46A==
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=ywPspWzVzySLY25CoDX0m+jBQEvj1UCO/fwKfQdw2Bs=; b=BOqzRW5QtjKjoLNTKUz+nY0mBu7aWVN7pwT+vjxgJe3ZbixSTPcL33vRQTmHPFkSqi 8n50JcZ4U5Jf1bYf+0hLkYP07nbRcjt7V0PZwIsCoarLJkRhw26VCLXaBvvOo9HIKSgR BhkxSIhQM+ORWXqVaMKzPuGa8csfEbtt8HaBfv88e4iHfptuDZm5PdxG4LoGNwtiohMF C2Sir2joVIJMdFEV5VS+STzWO4gOrkIHnUXcIhEavlPkT10G+dSVJViAU7quDj1L7Yw3 XqgbDgzZp+RJn58QQE2O4NvjtOUHpu349QwbTCZqOE0wLdZWIfY1IRmdllc2M+jT4RsS NVgw==
X-Gm-Message-State: AGRZ1gL7D/WrdbW+JBXvgpHUCwx+kcY7xSWHw73WHKSFlTp1l8SmE1lb 3foQ7ZnMzpTa5/U9YTKdLonU4kjkvHv4gq++fjVZbRifSQE=
X-Google-Smtp-Source: AJdET5e5X2kPY+LaTD3aNOrLGlQpeQimBKYLa7ZLAKWDJ+JGTRLInPPzLIfcCv/ExJYHXWBtwL/z1DTh77RkK8uNkmc=
X-Received: by 2002:a5d:6489:: with SMTP id r9-v6mr2295249wru.92.1541001666306;  Wed, 31 Oct 2018 09:01:06 -0700 (PDT)
MIME-Version: 1.0
References: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com> <CAKcm_gMDOyJC0AwOo2knN6AMxVbySjGsrLvjcC9A8UA9xcvcWw@mail.gmail.com> <19D3595B-8845-45B6-A60D-9E934DD49FAC@apple.com> <CACpbDcfk+GXb3aL5LG0wQM87thRGO5Y4Q+9cbXf5YuW1=jWCig@mail.gmail.com> <B7BE2454-2A4D-4323-B0A5-0D73BD4B819F@apple.com> <CACpbDcd5YWcxyEH3TS1FssgAT13oqeBBQg92+J0uJqhxPz2qkA@mail.gmail.com> <4b7b02d110f74139bacae8e01c54a4af@usma1ex-dag1mb6.msg.corp.akamai.com> <CACpbDcfDtwLqhR5um5OwzT2d8QAKrwhqmJJ3TRX9j-JhECRB4Q@mail.gmail.com>
In-Reply-To: <CACpbDcfDtwLqhR5um5OwzT2d8QAKrwhqmJJ3TRX9j-JhECRB4Q@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Wed, 31 Oct 2018 12:00:53 -0400
Message-ID: <CAKcm_gMZxRTYRJhTkw7EFxkK-qkNLr-hUd-XXj8HxS7Pho3SyQ@mail.gmail.com>
Subject: Re: flow control and DATAGRAM
To: Jana Iyengar <jri.ietf@gmail.com>
Cc: "Lubashev, Igor" <ilubashe@akamai.com>, Tommy Pauly <tpauly@apple.com>, IETF QUIC WG <quic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000eb8eee057988680f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/FmawoDCPbqPfHRNvyrTHdE5c5ac>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 16:01:14 -0000

--000000000000eb8eee057988680f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

If you add flow control, there's little benefit over a unidirectional
stream, so adding flow control fundamentally breaks this design.

My goal is to use this for cases when I want to use a single QUIC
connection to replace DTLS or RTP + something reliable.  WebRTC is the
obvious use case, but not the only one.  DTLS and RTP don't have flow
control, so adding it just make the application mapping a lot more complex.

On Tue, Oct 30, 2018 at 12:23 AM Jana Iyengar <jri.ietf@gmail.com> wrote:

> Igor,
>
> I had thought that this was similar to canceling streams, but you're
> right. Canceling a stream gets rid of stream flow control state entirely,
> where in this case, the receiver cannot discard flow control state.
>
> I don't have any great ideas right now, but I fear that not having flow
> control simply punts the problem down the road. FWIW, this may be quite
> fine for this extension, and we can surely evolve it to have flow control
> when we have a way to do it.
>
> - jana
>
> On Mon, Oct 29, 2018 at 8:54 PM Lubashev, Igor <ilubashe@akamai.com>
> wrote:
>
>> Jana,
>>
>> > The simplest scheme would be to reserve a stream ID for DATAGRAM data
>> -- [...]
>> > -- and then MAX_STREAM_DATA uses this
>> > stream ID for flow control of DATAGRAM octets.
>>
>> There are many dragons that way. Flow control indicates commitment to
>> buffer data. When sender does not retransmit, when does receiver give up
>> its commitment to wait for (and buffer) earlier data so it can advance
>> MAX_STREAM_DATA to allow the sender to send more data? Can the signal fr=
om
>> sender tolerate loss/reordering vs STREAM frames (assuming the datagram =
can
>> be split for sending in multiple QUIC packets)? These dragons can be
>> conquered (see my partially reliable streams draft, v2 or v3), but this =
is
>> not simple. :(
>>
>> - Igor
>>
>> -----Original Message-----
>> *From:* Jana Iyengar [jri.ietf@gmail.com]
>> *Received:* Monday, 29 Oct 2018, 10:24PM
>> *To:* tpauly@apple.com [tpauly@apple.com]
>> *CC:* Ian Swett [ianswett@google.com]; QUIC WG [quic@ietf.org]; Martin
>> Thomson [martin.thomson@gmail.com]
>> *Subject:* Re: flow control and DATAGRAM
>>
>> Hey Tommy,
>>
>>
>>> I'm not suggesting any changes to when the packet gets
>>> ack'ed=E2=80=94specifically, I was responding to Martin's hypothetical =
of having an
>>> ACK to a DATAGRAM frame meaning that the application had processed the
>>> frame. My impression is that the ACK to a packet containing a DATAGRAM
>>> frame means:
>>> - The packet made it across the network to the QUIC endpoint on the
>>> other side
>>>
>>
>> ... and was processed by the QUIC receiver (not necessarily by the
>> application). This is the same semantic as the ack of a regular frame.
>>
>>
>>> - The QUIC implementation will deliver the DATAGRAM frame to applicatio=
n
>>> (it won't drop it locally)
>>>
>>
>> In which case you will need flow control. If you agree, then we're on th=
e
>> same page so far.
>>
>>
>>> Having a separate outstanding data limit for the DATAGRAM "stream" is a=
n
>>> interesting solution to the space. It would then have the nice property=
 of
>>> not looking like traditional flow control. It could even be measured in
>>> number of frames, rather than bytes (depending on what the limiting fac=
tors
>>> are).
>>>
>>
>> In terms of flow control, I don't think DATAGRAM flow control is any
>> different than sending stream data on any stream and then canceling it -=
-
>> there are no retransmissions, but the sender still accounts for it in fl=
ow
>> control. My thought here was basically to have exactly the same flow
>> control as stream-level flow control, and allow for DATAGRAM bytes to fa=
ll
>> within connection-level flow control as normal.
>>
>> The simplest scheme would be to reserve a stream ID for DATAGRAM data --
>> this could be 0 or 2^62-1 -- and then MAX_STREAM_DATA uses this stream I=
D
>> for flow control of DATAGRAM octets. Alternatively, define a new frame
>> called MAX_DATAGRAM_DATA that is carries the largest allowed offset that
>> can be sent as a DATAGRAM, and introduce an offset field in the DATAGRAM
>> frame.
>>
>> - jana
>>
>>
>>> Thanks,
>>> Tommy
>>>
>>> On Oct 29, 2018, at 12:37 PM, Jana Iyengar <jri.ietf@gmail.com> wrote:
>>>
>>> Tommy,
>>>
>>> Changing the semantics of an acknowledgment to include delivery up to
>>> the application is a fundamental change to the QUIC machinery, and it
>>> doesn't work. First, an ACK frame acknowledges packets, and you can't h=
ave
>>> different semantics of an acknowledgment for different frames that are
>>> carried in the same packet. Second, it interferes with RTT measurement,=
 and
>>> it conflates flow control with congestion control, which gets messy. (T=
his
>>> conflation is an interesting problem to consider theoretically, but not=
 one
>>> for us at this time IMO.)
>>>
>>> I am wondering if applying a stream-level flow control for DATAGRAMs
>>> makes sense instead. Meaning that you treat DATAGRAMs as a separate str=
eam
>>> for flow control purposes. You might benefit from having an offset in t=
he
>>> DATAGRAM frame for this purpose.
>>>
>>> - jana
>>>
>>> On Mon, Oct 29, 2018 at 8:21 AM Tommy Pauly <tpauly@apple.com> wrote:
>>>
>>>> Hi Martin, Ian,
>>>>
>>>> Yes, very good points!
>>>>
>>>> My tendency would be to prefer what Ian's implementation does of
>>>> passing these DATAGRAM frames up immediately to the application. I don=
't
>>>> think that the acknowledgment needs to indicate that the frame was
>>>> processed by the application, but merely that it has been delivered to=
 the
>>>> application (that is, the application doesn't get to do anything with =
the
>>>> frame that can influence the acknowledgment).
>>>>
>>>> The current draft indicates that the content of the DATAGRAM frames
>>>> contributes to the limit used for MAX_DATA, and that if that amount is
>>>> reached, the frames are blocked along with STREAM data. I think this w=
orks
>>>> fine for the sender, while the receiver gets into the discussion you
>>>> present. On the sender side, reaching MAX_DATA could mean dropping the
>>>> DATAGRAM frames when unable to send more (and sending BLOCKED instead)=
.
>>>> Since the frames are unreliable, they can be dropped in this situation
>>>> without violating the API contract.
>>>>
>>>> On the receiver side, I agree that queuing the DATAGRAM frames to let
>>>> the application drive flow control in the way it does for STREAM frame=
s
>>>> adds complexity and diminishes the utility of the frame and ACKs.. How=
ever,
>>>> I can imagine taking a fairly simplistic approach in which the data li=
mit
>>>> is automatically increased upon reception of the frame (and the frame =
is
>>>> immediately passed to the application). This allows the initial_max_da=
ta to
>>>> put a cap on the amount of data in a given flight of DATAGRAMS, and al=
low
>>>> the size of a flight of DATAGRAM frames to be limited by the amount of=
 room
>>>> left over from STREAM data that may be consuming the connection-wide f=
low
>>>> control.
>>>>
>>>> Perhaps this approach needs a clearer name other than "flow control",
>>>> since it has a somewhat different meaning in effect.
>>>>
>>>> As for ACKs, if we never discard on the receiver side, the ACK is
>>>> pretty useful for detecting if there was network-based packet loss.
>>>>
>>>> Thanks,
>>>> Tommy
>>>>
>>>> On Oct 29, 2018, at 5:32 AM, Ian Swett <ianswett@google.com> wrote:
>>>>
>>>> Good catch Martin, I missed that in the draft as well, and I also thin=
k
>>>> it's impossibly with the proposed design.
>>>>
>>>> And yes, I think Martin's proposed solution is likely the only
>>>> practical one.  In my implementation, the frame is passed up to the
>>>> application immediately, so technically QUIC processed it, and it's th=
e
>>>> application's job to decide what to do with it.
>>>>
>>>> On Mon, Oct 29, 2018 at 1:16 AM Martin Thomson <
>>>> martin.thomson@gmail.com> wrote:
>>>>
>>>>> Hi Tommy,
>>>>>
>>>>> Your slides - <
>>>>> https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF103-QU=
IC-Datagram.pdf
>>>>> <https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_qu=
icwg_wg-2Dmaterials_blob_master_ietf103_IETF103-2DQUIC-2DDatagram.pdf&d=3DD=
wMFaQ&c=3D96ZbZZcaMF4w0F4jpN6LZg&r=3DDjn3bQ5uNJDPM_2skfL3rW1tzcIxyjUZdn_m55=
KPmlo&m=3DBOGSfZ4hKaubJ6yww-9_8EDX3OccYvdip0g3k4t66hQ&s=3Dqiyr1YY1MHWjhIrPf=
wHXN6FCdsG8wUuhAuqczkosLlI&e=3D>
>>>>> >
>>>>> - say that DATAGRAM frames respect connection-level flow control.  I
>>>>> missed that in the draft, and I don't know how they can do that in th=
e
>>>>> face of packet loss, especially when you don't necessarily retransmit
>>>>> lost DATAGRAM frames.
>>>>>
>>>>> For that to work, you would need a bunch more machinery to make the
>>>>> connection-level flow control sync between endpoints in the case that
>>>>> packets are lost.  A disagreement about how much flow control is used
>>>>> causes things to break down badly.  Ian and I discussed this point at
>>>>> the last meeting and quickly agreed that while it might be nice to
>>>>> have flow control for this stuff, the increase in complexity is
>>>>> considerable and (at the time) we thought it wouldn't be worth it.
>>>>>
>>>>> The problem that introduces is that you could end up having too many
>>>>> DATAGRAM frames arrive.  The receiver has to drop something at the
>>>>> point that it can't handle them.  And we say that when you acknowledg=
e
>>>>> something, you processed it.  That's tricky.
>>>>>
>>>>> It might be easier to say that a QUIC acknowledgment for a DATAGRAM
>>>>> frame doesn't mean that it was received and processed by an
>>>>> application.  An endpoint might discard these frames before passing
>>>>> them on to applications if it doesn't have space.  In other words,
>>>>> acknowledgment of DATAGRAM means that QUIC got it, not that the
>>>>> application got it.  Sadly, that means that the QUIC acknowledgment
>>>>> machinery doesn't help the application that uses DATAGRAM all that
>>>>> much.  Also, the lower bound on reliability is 0, which isn't the bes=
t
>>>>> thing ever.
>>>>>
>>>>> Hard choices, I know.  I don't have a good design for maintaining
>>>>> connection-level flow control (or any back pressure mechanism with
>>>>> equivalent properties) that doesn't add both complexity and overhead.
>>>>>
>>>>> Cheers,
>>>>> Martin
>>>>>
>>>>>
>>>>
>>>

--000000000000eb8eee057988680f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">If you add flow control, there&#39;s little benefit over a=
 unidirectional stream, so adding flow control fundamentally breaks this de=
sign.<div><br>My goal is to use this for cases when I want to use a single =
QUIC connection to replace DTLS or RTP + something reliable.=C2=A0 WebRTC i=
s the obvious use case, but not the only one.=C2=A0 DTLS and RTP don&#39;t =
have flow control, so adding it just make the application mapping a lot mor=
e complex.</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tu=
e, Oct 30, 2018 at 12:23 AM Jana Iyengar &lt;<a href=3D"mailto:jri.ietf@gma=
il.com">jri.ietf@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex"><div dir=3D"ltr">Igor,<div><br></div><div>I had thought that this wa=
s similar to canceling streams, but you&#39;re right. Canceling a stream ge=
ts rid of stream flow control state entirely, where in this case, the recei=
ver cannot discard flow control state.</div><div><br></div><div>I don&#39;t=
 have any great ideas right now, but I fear that not having flow control si=
mply punts the problem down the road. FWIW, this may be quite fine for this=
 extension, and we can surely evolve it to have flow control when we have a=
 way to do it.</div><div><br></div><div>- jana</div></div><br><div class=3D=
"gmail_quote"><div dir=3D"ltr">On Mon, Oct 29, 2018 at 8:54 PM Lubashev, Ig=
or &lt;<a href=3D"mailto:ilubashe@akamai.com" target=3D"_blank">ilubashe@ak=
amai.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">




<div>
<span style=3D"font-family:Calibri,Arial,Helvetica,sans-serif;font-size:11p=
t;color:black">Jana,<br>
<br>
&gt; The simplest scheme would be to reserve a stream ID for DATAGRAM data =
-- [...]<br>
&gt; -- and then MAX_STREAM_DATA uses this<br>
&gt; stream ID for flow control of DATAGRAM octets.<br>
<br>
There are many dragons that way. Flow control indicates commitment to buffe=
r data. When sender does not retransmit, when does receiver give up its com=
mitment to wait for (and buffer) earlier data so it can advance MAX_STREAM_=
DATA to allow the sender to send
 more data? Can the signal from sender tolerate loss/reordering vs STREAM f=
rames (assuming the datagram can be split for sending in multiple QUIC pack=
ets)? These dragons can be conquered (see my partially reliable streams dra=
ft, v2 or v3), but this is not simple.
 :(<br>
<br>
- Igor<br>
<br>
<span style=3D"color:black">-----Original Message----- <br>
<b>From:</b> Jana Iyengar [<a href=3D"mailto:jri.ietf@gmail.com" target=3D"=
_blank">jri.ietf@gmail.com</a>]<br>
<b>Received:</b> Monday, 29 Oct 2018, 10:24PM<br>
<b>To:</b> <a href=3D"mailto:tpauly@apple.com" target=3D"_blank">tpauly@app=
le.com</a> [<a href=3D"mailto:tpauly@apple.com" target=3D"_blank">tpauly@ap=
ple.com</a>]<br>
<b>CC:</b> Ian Swett [<a href=3D"mailto:ianswett@google.com" target=3D"_bla=
nk">ianswett@google.com</a>]; QUIC WG [<a href=3D"mailto:quic@ietf.org" tar=
get=3D"_blank">quic@ietf.org</a>]; Martin Thomson [<a href=3D"mailto:martin=
.thomson@gmail.com" target=3D"_blank">martin.thomson@gmail.com</a>]<br>
<b>Subject:</b> Re: flow control and DATAGRAM<br>
<br>
</span></span>
<div>
<div dir=3D"ltr">Hey Tommy,
<div class=3D"gmail_quote">
<div>=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;line-break:after-white-space">
<div>I&#39;m not suggesting any changes to when the packet gets ack&#39;ed=
=E2=80=94specifically, I was responding to Martin&#39;s hypothetical of hav=
ing an ACK to a DATAGRAM frame meaning that the application had processed t=
he frame. My impression is that the ACK to a packet containing
 a DATAGRAM frame means:</div>
<div>- The packet made it across the network to the QUIC endpoint on the ot=
her side</div>
<div></div>
</div>
</blockquote>
<div><br>
</div>
<div>... and was processed by the QUIC receiver (not necessarily by the app=
lication). This is the same semantic as the ack of a regular frame.</div>
<div>=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;line-break:after-white-space">
<div>- The QUIC implementation will deliver the DATAGRAM frame to applicati=
on (it won&#39;t drop it locally)</div>
</div>
</blockquote>
<div><br>
</div>
<div>In which case you will need flow control. If you agree, then we&#39;re=
 on the same page so far.</div>
<div>=C2=A0=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;line-break:after-white-space">
<div>Having a separate outstanding data limit for the DATAGRAM &quot;stream=
&quot; is an interesting solution to the space. It would then have the nice=
 property of not looking like traditional flow control. It could even be me=
asured in number of frames, rather than bytes
 (depending on what the limiting factors are).</div>
</div>
</blockquote>
<div><br>
</div>
<div>In terms of flow control, I don&#39;t think DATAGRAM flow control is a=
ny different than sending stream data on any stream and then canceling it -=
- there are no retransmissions, but the sender still accounts for it in flo=
w control. My thought here was basically
 to have exactly the same flow control as stream-level flow control, and al=
low for DATAGRAM bytes to fall within connection-level flow control as norm=
al.</div>
<div><br>
</div>
<div>The simplest scheme would be to reserve a stream ID for DATAGRAM data =
-- this could be 0 or 2^62-1 -- and then MAX_STREAM_DATA uses this stream I=
D for flow control of DATAGRAM octets. Alternatively, define a new frame ca=
lled MAX_DATAGRAM_DATA that is carries
 the largest allowed offset that can be sent as a DATAGRAM, and introduce a=
n offset field in the DATAGRAM frame.</div>
<div><br>
</div>
<div>- jana</div>
<div>=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;line-break:after-white-space">
<div>Thanks,</div>
<div>Tommy<br>
<div><br>
<blockquote type=3D"cite">
<div>On Oct 29, 2018, at 12:37 PM, Jana Iyengar &lt;<a href=3D"mailto:jri.i=
etf@gmail.com" target=3D"_blank">jri.ietf@gmail.com</a>&gt; wrote:</div>
<br class=3D"m_2073751388042974774m_4877462653349879931m_611719050333871489=
1Apple-interchange-newline">
<div>
<div dir=3D"ltr">Tommy,
<div><br>
</div>
<div>Changing the semantics of an acknowledgment to include delivery up to =
the application is a fundamental change to the QUIC machinery, and it doesn=
&#39;t work. First, an ACK frame acknowledges packets, and you can&#39;t ha=
ve different semantics of an acknowledgment
 for different frames that are carried in the same packet. Second, it inter=
feres with RTT measurement, and it conflates flow control with congestion c=
ontrol, which gets messy. (This conflation is an interesting problem to con=
sider theoretically, but not one
 for us at this time IMO.)</div>
<div><br>
</div>
<div>I am wondering if applying a stream-level flow control for DATAGRAMs m=
akes sense instead. Meaning that you treat DATAGRAMs as a separate stream f=
or flow control purposes. You might benefit from having an offset in the DA=
TAGRAM frame for this purpose.</div>
<div><br>
</div>
<div>- jana</div>
</div>
<br>
<div class=3D"gmail_quote">
<div dir=3D"ltr">On Mon, Oct 29, 2018 at 8:21 AM Tommy Pauly &lt;<a href=3D=
"mailto:tpauly@apple.com" target=3D"_blank">tpauly@apple.com</a>&gt; wrote:=
<br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;line-break:after-white-space">Hi Martin,=
 Ian,
<div><br>
</div>
<div>Yes, very good points!</div>
<div><br>
</div>
<div>My tendency would be to prefer what Ian&#39;s implementation does of p=
assing these DATAGRAM frames up immediately to the application. I don&#39;t=
 think that the acknowledgment needs to indicate that the frame was process=
ed by the application, but merely that it
 has been delivered to the application (that is, the application doesn&#39;=
t get to do anything with the frame that can influence the acknowledgment).=
</div>
<div><br>
</div>
<div>The current draft indicates that the content of the DATAGRAM frames co=
ntributes to the limit used for=C2=A0MAX_DATA, and that if that amount is r=
eached, the frames are blocked along with STREAM data. I think this works f=
ine for the sender, while the receiver
 gets into the discussion you present. On the sender side, reaching MAX_DAT=
A could mean dropping the DATAGRAM frames when unable to send more (and sen=
ding BLOCKED instead). Since the frames are unreliable, they can be dropped=
 in this situation without violating
 the API contract.=C2=A0</div>
<div><br>
</div>
<div>On the receiver side, I agree that queuing the DATAGRAM frames to let =
the application drive flow control in the way it does for STREAM frames add=
s complexity and diminishes the utility of the frame and ACKs.. However, I =
can imagine taking a fairly simplistic
 approach in which the data limit is automatically increased upon reception=
 of the frame (and the frame is immediately passed to the application). Thi=
s allows the initial_max_data to put a cap on the amount of data in a given=
 flight of DATAGRAMS, and allow
 the size of a flight of DATAGRAM frames to be limited by the amount of roo=
m left over from STREAM data that may be consuming the connection-wide flow=
 control.=C2=A0</div>
<div><br>
</div>
<div>Perhaps this approach needs a clearer name other than &quot;flow contr=
ol&quot;, since it has a somewhat different meaning in effect.</div>
<div><br>
</div>
<div>As for ACKs, if we never discard on the receiver side, the ACK is pret=
ty useful for detecting if there was network-based packet loss.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Tommy=C2=A0</div>
<div>
<div><br>
<blockquote type=3D"cite">
<div>On Oct 29, 2018, at 5:32 AM, Ian Swett &lt;<a href=3D"mailto:ianswett@=
google.com" target=3D"_blank">ianswett@google.com</a>&gt; wrote:</div>
<br class=3D"m_2073751388042974774m_4877462653349879931m_611719050333871489=
1m_-1061371301160893898Apple-interchange-newline">
<div>
<div dir=3D"ltr">Good catch Martin, I missed that in the draft as well, and=
 I also think it&#39;s impossibly with the proposed design.
<div><br>
</div>
<div>And yes, I think Martin&#39;s proposed solution is likely the only pra=
ctical one.=C2=A0 In my implementation, the frame is passed up to the appli=
cation immediately, so technically QUIC processed it, and it&#39;s the appl=
ication&#39;s job to decide what to do with it.</div>
</div>
<br>
<div class=3D"gmail_quote">
<div dir=3D"ltr">On Mon, Oct 29, 2018 at 1:16 AM Martin Thomson &lt;<a href=
=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomson@gmail=
.com</a>&gt; wrote:<br>
</div>
<blockquote class=3D"gmail_quote">Hi Tommy,<br>
<br>
Your slides - &lt;<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dh=
ttps-3A__github.com_quicwg_wg-2Dmaterials_blob_master_ietf103_IETF103-2DQUI=
C-2DDatagram.pdf&amp;d=3DDwMFaQ&amp;c=3D96ZbZZcaMF4w0F4jpN6LZg&amp;r=3DDjn3=
bQ5uNJDPM_2skfL3rW1tzcIxyjUZdn_m55KPmlo&amp;m=3DBOGSfZ4hKaubJ6yww-9_8EDX3Oc=
cYvdip0g3k4t66hQ&amp;s=3Dqiyr1YY1MHWjhIrPfwHXN6FCdsG8wUuhAuqczkosLlI&amp;e=
=3D" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/wg-mate=
rials/blob/master/ietf103/IETF103-QUIC-Datagram.pdf</a>&gt;<br>
- say that DATAGRAM frames respect connection-level flow control.=C2=A0 I<b=
r>
missed that in the draft, and I don&#39;t know how they can do that in the<=
br>
face of packet loss, especially when you don&#39;t necessarily retransmit<b=
r>
lost DATAGRAM frames.<br>
<br>
For that to work, you would need a bunch more machinery to make the<br>
connection-level flow control sync between endpoints in the case that<br>
packets are lost.=C2=A0 A disagreement about how much flow control is used<=
br>
causes things to break down badly.=C2=A0 Ian and I discussed this point at<=
br>
the last meeting and quickly agreed that while it might be nice to<br>
have flow control for this stuff, the increase in complexity is<br>
considerable and (at the time) we thought it wouldn&#39;t be worth it.<br>
<br>
The problem that introduces is that you could end up having too many<br>
DATAGRAM frames arrive.=C2=A0 The receiver has to drop something at the<br>
point that it can&#39;t handle them.=C2=A0 And we say that when you acknowl=
edge<br>
something, you processed it.=C2=A0 That&#39;s tricky.<br>
<br>
It might be easier to say that a QUIC acknowledgment for a DATAGRAM<br>
frame doesn&#39;t mean that it was received and processed by an<br>
application.=C2=A0 An endpoint might discard these frames before passing<br=
>
them on to applications if it doesn&#39;t have space.=C2=A0 In other words,=
<br>
acknowledgment of DATAGRAM means that QUIC got it, not that the<br>
application got it.=C2=A0 Sadly, that means that the QUIC acknowledgment<br=
>
machinery doesn&#39;t help the application that uses DATAGRAM all that<br>
much.=C2=A0 Also, the lower bound on reliability is 0, which isn&#39;t the =
best<br>
thing ever.<br>
<br>
Hard choices, I know.=C2=A0 I don&#39;t have a good design for maintaining<=
br>
connection-level flow control (or any back pressure mechanism with<br>
equivalent properties) that doesn&#39;t add both complexity and overhead.<b=
r>
<br>
Cheers,<br>
Martin<br>
<br>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>

</blockquote></div>
</blockquote></div>

--000000000000eb8eee057988680f--


From nobody Wed Oct 31 09:32:42 2018
Return-Path: <pravb@microsoft.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 3E78B1293FB for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 09:32:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.47
X-Spam-Level: 
X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 6hXPb37QJA2V for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 09:32:38 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0106.outbound.protection.outlook.com [104.47.36.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 419A4128CE4 for <quic@ietf.org>; Wed, 31 Oct 2018 09:32:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=mDQoPAzTy5IA2P93jWxO63H91APrKgPpdu+iZClpqik=; b=dmWLAhr+qeWnMtz9ABkzez1ptq7mVSdZtw7TD/bk6jyeL+FlCNkY/U0di5qfsNgriuHi05WWVmDnHMe/UKQU796KYKRNBIXQW6sCQQzxKRR1XVMb3/XfhZ8EnVv/+r2Izc8IDupeoQXNfcGzGEabf8l0JskhY0RxCrubpDDjf+Y=
Received: from DM5PR2101MB1046.namprd21.prod.outlook.com (52.132.128.15) by DM5PR2101MB0919.namprd21.prod.outlook.com (52.132.132.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1294.2; Wed, 31 Oct 2018 16:32:36 +0000
Received: from DM5PR2101MB1046.namprd21.prod.outlook.com ([fe80::9c64:a017:8062:939f]) by DM5PR2101MB1046.namprd21.prod.outlook.com ([fe80::9c64:a017:8062:939f%4]) with mapi id 15.20.1294.014; Wed, 31 Oct 2018 16:32:36 +0000
From: Praveen Balasubramanian <pravb@microsoft.com>
To: "Brian Trammell (IETF)" <ietf@trammell.ch>, Marcus Ihlar <marcus.ihlar@ericsson.com>
CC: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>, huitema <huitema@huitema.net>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Kazuho Oku <kazuhooku@gmail.com>
Subject: RE: Structuring the BKK spin bit discussion
Thread-Topic: Structuring the BKK spin bit discussion
Thread-Index: AQHUb5vavgJndpf/BEmVaq54GPMvY6U2Y+yAgAAMqQCAArb/gIAAJugAgAAbi4CAACNjQA==
Date: Wed, 31 Oct 2018 16:32:36 +0000
Message-ID: <DM5PR2101MB10464C5346F73F83CAC25BD1B6CD0@DM5PR2101MB1046.namprd21.prod.outlook.com>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CANatvzxt-QBmeJUwp+MjtbpYXstPiEigDzQe0KfWJN+q0XR4Kg@mail.gmail.com> <HE1PR0701MB23938B01BC31888DAC3629B8E2CD0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <D8BB0373-FDEB-4312-94E6-BBA304D595BE@trammell.ch>
In-Reply-To: <D8BB0373-FDEB-4312-94E6-BBA304D595BE@trammell.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e8:b:2933:a062:eb3b:5529]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR2101MB0919; 6:cIqbD8rxthHyBa+8Ew1ITKwtxIJLtcowlgIroznPr8nsnkdmJwqktFcrSutPkEu+7ppddW/JFz/tNR0VULdAarlzOjH776wCP2AGJoExkZEioUEa5MDsUgvwQBClnjiGP5ddrf1YGCGq6U0dAS3Cs48g8u8LrF2KDqzBWMAIhKFKkmaWEvZ9PDMNb3iojCB6FfTFPg0sU7VZN2hsFQklYyKCXWJE3mxTixzIDCOeRQ5D2wKmMHPZin21N1rs2IKChqNIpPlcpy/PYsIqZOnx9RD5b3yLZDm2F1UPM7CpgKG4ogcWkF1bNX9hMF3oVk+njEEkvY5pFZTjFRcdaSYYRnpSzKqLGuwbNn+9UXcGNZkfu28lAov9c3bfDnlrj+3gZFmRW4inKHf+aZJkRKeNK3eNpFAKmt4n5dvOCAq09SWFx8dM0lq2G4CgFjlfpftb+gjphs0vTB3vmCozX2nx2A==; 5:bYg83oZst4ReddzyjWNsU+5Z5h0/44vIDA3+5GzDbggO9Y5yC3y749rUhSkuQVu1rcgtK8gZhhp31zKfTmkR3Ph1BOkiptkmwEzO9gBBxwQ9SBu8jyilye+Dm1K2doGICnYzxBM0a5/zlSajgi35XPwPtGSkm5/mnMFgfZjzVSM=; 7:Bhb8SOMaCgr1pceTruWjgGf4dr5NMeweDWnPbJbPRb4p4iszs5yGI8DyStfjdKUZlNue294oxr6EEKMeE6hmBG+RH/DVp661lsReOQMTdYqbyi3Ge2DdY0TaHtmqP9fYuKXN4FbZ7ZEhewu0KamuVw==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 59020e94-ae8d-4daa-46dd-08d63f4e77b0
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7193020); SRVR:DM5PR2101MB0919; 
x-ms-traffictypediagnostic: DM5PR2101MB0919:
x-ld-processed: 72f988bf-86f1-41af-91ab-2d7cd011db47,ExtAddr
x-microsoft-antispam-prvs: <DM5PR2101MB0919FEBE49D7985E5A342DEEB6CD0@DM5PR2101MB0919.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(166708455590820)(158342451672863)(248295561703944)(37575265505322)(85827821059158);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(8220035)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(10201501046)(3231382)(944501410)(52105095)(2018427008)(6055026)(148016)(149066)(150057)(6041310)(20161123560045)(20161123562045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(201708071742011)(7699051)(76991095); SRVR:DM5PR2101MB0919; BCL:0; PCL:0; RULEID:; SRVR:DM5PR2101MB0919; 
x-forefront-prvs: 084285FC5C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(136003)(366004)(346002)(39860400002)(376002)(189003)(13464003)(199004)(97736004)(8990500004)(5660300001)(10290500003)(76176011)(229853002)(316002)(305945005)(2900100001)(86612001)(6306002)(105586002)(46003)(14444005)(256004)(99286004)(186003)(9686003)(86362001)(106356001)(66574009)(71190400001)(7736002)(6246003)(71200400001)(22452003)(74316002)(53936002)(7696005)(14454004)(53546011)(33656002)(476003)(93886005)(6506007)(10090500001)(478600001)(5250100002)(8936002)(11346002)(6436002)(68736007)(102836004)(55016002)(8676002)(39060400002)(4326008)(966005)(25786009)(446003)(81166006)(6116002)(81156014)(54906003)(2906002)(6346003)(110136005)(486006); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR2101MB0919; H:DM5PR2101MB1046.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pravb@microsoft.com; 
x-microsoft-antispam-message-info: zaSCWNEOgRdVQo3R4rw3VUo+su4ZFhbUN7PCEWFH6Yv8YHmJHknYUsdR/N9tGI2y5hHkeljFZs+Q+LjC8A94rvbrr8LLmrgebarVzj4g+x+DKBpz89iSUry4HvZaBx5vvrX0cSrAf+TYjXsIyj98cJEIQyuVjIyFvW23FiReRLVEAwF6aiRh4mjRPN/EdJ8EQSlEB15pqyFIqCG+kroI213Amh8zbCFBCNNH3DVokRf2TR/2gBToy/k4SEsWhOI3Ev5ohANLAdxTiCn3myCf51XT8U2XjN7cJseQXfCteijin8W0xbo8cU2/ugHdUBpM2sdpzC3cya3jxXvhSMP6qZ/nuNTUhaJJo3SjhSBJ9So=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 59020e94-ae8d-4daa-46dd-08d63f4e77b0
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Oct 2018 16:32:36.6042 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR2101MB0919
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-HRgkCswUa6LoeGNvHbeP5dccTk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 16:32:41 -0000

U2luY2UgdGhlIGhhbmRzaGFrZSBleHBvc2VzIHRoZSBSVFQgaW5mb3JtYXRpb24sIHdoYXQgaXMg
dGhlIGdlb2xvY2F0aW9uIHByaXZhY3kgaXNzdWUgcmVzdWx0aW5nIGZyb20gdGhlIHNwaW4gYml0
PyBCcmlhbiwgd2hhdCBhcmUgdGhlIGVkZ2UgY2FzZXMgeW91IHJlZmVyIHRvIHdoZXJlIGhhbmRz
aGFrZSBsYXRlbmN5IHdpbGwgYmUgZGlmZmVyZW50IHRoYW4gd2hhdCBpcyBtZWFzdXJlZCBieSBz
cGluIGJpdD8gDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBRVUlDIDxxdWlj
LWJvdW5jZXNAaWV0Zi5vcmc+IE9uIEJlaGFsZiBPZiBCcmlhbiBUcmFtbWVsbCAoSUVURikNClNl
bnQ6IFdlZG5lc2RheSwgT2N0b2JlciAzMSwgMjAxOCA3OjE5IEFNDQpUbzogTWFyY3VzIElobGFy
IDxtYXJjdXMuaWhsYXJAZXJpY3Nzb24uY29tPg0KQ2M6IExhcnMgRWdnZXJ0IDxsYXJzQGVnZ2Vy
dC5vcmc+OyBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc+OyBodWl0ZW1hIDxodWl0ZW1hQGh1
aXRlbWEubmV0PjsgRG1pdHJpIFRpa2hvbm92IDxkdGlraG9ub3ZAbGl0ZXNwZWVkdGVjaC5jb20+
OyBLYXp1aG8gT2t1IDxrYXp1aG9va3VAZ21haWwuY29tPg0KU3ViamVjdDogUmU6IFN0cnVjdHVy
aW5nIHRoZSBCS0sgc3BpbiBiaXQgZGlzY3Vzc2lvbg0KDQpoaSBLYXp1aG8sIE1hcmN1cywNCg0K
KzEgdG8gdGhpczsgdGhlIGludHJhLW5ldHdvcmsgbGF0ZW5jeSB2YXJpYXRpb24gb24gdGhlIG1v
YmlsZSBzZWdtZW50IG9mIHRoZSBtb2JpbGUgbmV0d29ya3Mgd2UgbG9va2VkIGF0IHZpYSB0aGUg
TU9OUk9FIGluIHRoZSB0ZXN0YmVkIGluIG91ciBQQU0gcGFwZXIgdGhlIGZvbGxvd2VkIGZyb20g
dGhlIFJUVCBEVCB3b3JrIChzZWUgaHR0cHM6Ly9naXRodWIuY29tL21hbWktcHJvamVjdC9ydHQt
cHJpdmFjeS1wYXBlci9ibG9iL21hc3Rlci9ydHQtcHJpdmFjeS5wZGYsIGVzcGVjaWFsbHkgc2Vj
dGlvbiAzLjEgYW5kIGZpZ3VyZSAyKGIpKSBtYWtlcyBSVFQgbWVhc3VyZW1lbnQgb24gYSBtb2Jp
bGUgbmV0d29yayB1c2VsZXNzIGZvciBnZW9sb2NhdGlvbi4NCg0KV2UgZGlkIG5vdGljZSAobm90
IHNob3duIGluIHRoZSBwYXBlcikgdGhhdCBkaWZmZXJlbnQgY2FycmllcnMgKG4gPSA0LCBpZiBJ
IHJlY2FsbCBjb3JyZWN0bHkpIGhhZCBkaXN0aW5jdCBsYXRlbmN5IGRpc3RyaWJ1dGlvbnMsIHNv
IHdpdGggdHJhZmZpYyBmcm9tIGFsbCBKYXBhbmVzZSBtb2JpbGUgdXNlcnMgeW91IGNvdWxkIHBy
b2JhYmx5IHVzZSBSVFQgZGF0YSBpbiB0aGUgYWdncmVnYXRlIHRvIGJ1aWxkIGEgImNhcnJpZXIg
Y2xhc3NpZmllciIuIFRoaXMgaXMgb2YgY291cnNlIGEgdXNlbGVzcyBleGVyY2lzZSBiZWNhdXNl
IHlvdSBjYW4gYWxyZWFkeSB0ZWxsIHdoaWNoIGNhcnJpZXIgYSBzdWJzY3JpYmVyIGlzIGNvbWlu
ZyBmcm9tIGJ5IGxvb2tpbmcgYXQgdGhlIElQIGFkZHJlc3Mgb2YgdGhlIENHTkFUIGV4aXQuDQoN
CklNTyB0aGVyZSBhcmUgb25seSBhIGZldyBlZGdlIGNhc2VzIHdoZXJlIHRoZXJlIGFyZSBhY3R1
YWwgcG90ZW50aWFsIGdlb3ByaXZhY3kgaXNzdWVzIHJhaXNlZCBieSB0aGUgc3BpbiBiaXQgd2l0
aCByZXNwZWN0IHRvIHR1bm5lbGVkIFZQTiB0cmFmZmljLiBBbGwgb2YgdGhlc2UgaW52b2x2ZSB0
cmFucy0gb3IgaW50ZXJjb250aW5lbnRhbCB0dW5uZWxzICg+MzBtcyBvZiBhZGRpdGlvbmFsIFJU
VCwgZm9yIDMwMDBrbSBvZiBsb2NhdGlvbiB1bmNlcnRhaW50eSAtLSBob3cgZmFyIGlzIGl0IGZy
b20gT2tpbmF3YSB0byBIb2trYWlkbz8pLiBJbiBldmVyeSBjYXNlIHRoZSBoYW5kc2hha2UgbGF0
ZW5jeSBnaXZlcyB5b3UgYXdheSBhcyB3ZWxsLCBidXQgaW4gZXZlcnkgY2FzZSBsb25nIFJUVHMg
bWlnaHQgYWxzbyBoYXZlIG5vbi1kaXN0YW5jZSByZWxhdGVkIGNhdXNlcy4gU28gd2hpbGUgSSBz
ZWUgZGlzYWJsaW5nIHRoZSBzcGluIGJpdCBhcyBhIG5lY2Vzc2FyeSBmZWF0dXJlLCBlc3BlY2lh
bGx5IGZvciBjbGllbnRzIHRvIGhhdmUsIElNTyBpdHMgdXRpbGl0eSBpcyBtb3JlIHVzZWZ1bCBm
b3IgcGVhY2Ugb2YgbWluZCBhbmQgaW5mb3JtYXRpb24gcmVkdWN0aW9uIHRoYW4gZm9yIGFjdHVh
bCBpbmZvcm1hdGlvbiBlbGltaW5hdGlvbi4NCg0KQ2hlZXJzLA0KDQpCcmlhbg0KDQo+IE9uIDMx
IE9jdCAyMDE4LCBhdCAxMzo0MCwgTWFyY3VzIElobGFyIDxtYXJjdXMuaWhsYXJAZXJpY3Nzb24u
Y29tPiB3cm90ZToNCj4gDQo+IEhpIEthenVobywNCj4gSSBiZWxpZXZlIHRoZSBiaWdnZXN0IGRp
ZmZlcmVuY2UgaXMgdGhlIHNpemUgb2YgdGhlIGhpZGRlbiBuZXR3b3JrIHNlZ21lbnQuDQo+IElu
IHRoZSBOQVQgY2FzZSB0aGUgY2xpZW50IGFuZCBOQVQgYXJlIHN0aWxsIGluIHRoZSBzYW1lIGNv
dW50cnkgb3IgY29udGluZW50Lg0KPiBBIHF1aWNrIGdsYWNuZSBhdCBkaXN0YW5jZWNhbGN1bGF0
b3IubmV0IHNob3dzIHRoYXQgdGhlIGNpdHkgZmFydGhlc3QgZnJvbSBUb2t5byBpbiBKYXBhbiBp
cyBOYWhhLVNoaSwgYXQgMTU1NCBrbS4NCj4gVGhhdCB0cmFuc2xhdGVzIHRvIHJvdWdobHkgNW1z
IGF0IHRoZSBzcGVlZCBvZiBsaWdodCwgc28gdGhlIGtpbmRzIG9mIG1lYXN1cmVtZW50cyB0byBk
ZXRlcm1pbmUgZGlzdGFuY2UgZnJvbSBUb2t5byBiYXNlZCBvbiBSVFQgd2lsbCBiZSBleHRyZW1l
bHkgc2Vuc2l0aXZlIGFuZCBlcnJvciBwcm9uZS4NCj4gUGxlYXNlIG5vdGUgdGhhdCB0aGUgZGlz
dGFuY2UgYW5hbHlpcyBjYW4gYmUgcGVyZm9ybWVkIG9uIGhhbmRzaGFrZSBSVFQgYXMgd2VsbCwg
Zm9yIGNvbm5lY3Rpb25zIHdoZXJlIHRoZSBpbml0aWFsIGhhbmRzaGFrZSBpcyB2aXNpYmxlIGF0
IHRoZSBtZWFzdXJlbWVudCBwb2ludC4NCj4gDQo+IA0KPiBGcsOlbjogUVVJQyA8cXVpYy1ib3Vu
Y2VzQGlldGYub3JnPiBmw7ZyIEthenVobyBPa3UgDQo+IDxrYXp1aG9va3VAZ21haWwuY29tPg0K
PiBTa2lja2F0OiBkZW4gMzEgb2t0b2JlciAyMDE4IDExOjIwDQo+IFRpbGw6IENocmlzdGlhbiBI
dWl0ZW1hDQo+IEtvcGlhOiBMYXJzIEVnZ2VydDsgSUVURiBRVUlDIFdHOyBEbWl0cmkgVGlraG9u
b3YNCj4gw4RtbmU6IFJlOiBTdHJ1Y3R1cmluZyB0aGUgQktLIHNwaW4gYml0IGRpc2N1c3Npb24N
Cj4gDQo+IDIwMTjlubQxMOaciDMw5pelKOeBqykgMTo1NCBDaHJpc3RpYW4gSHVpdGVtYSA8aHVp
dGVtYUBodWl0ZW1hLm5ldD46DQo+ID4NCj4gPg0KPiA+DQo+ID4gPiBPbiBPY3QgMjksIDIwMTgs
IGF0IDk6MDggQU0sIERtaXRyaSBUaWtob25vdiA8ZHRpa2hvbm92QGxpdGVzcGVlZHRlY2guY29t
PiB3cm90ZToNCj4gPiA+DQo+ID4gPj4gT24gTW9uLCBPY3QgMjksIDIwMTggYXQgMDU6MjY6MzRQ
TSArMDIwMCwgTGFycyBFZ2dlcnQgd3JvdGU6DQo+ID4gPj4gV2UnZCBzcGVjaWZpY2FsbHkgbGlr
ZSB0byBhc2sgY2xpZW50IGFuZCBzZXJ2ZXIgaW1wbGVtZW50b3JzIHdpdGggDQo+ID4gPj4gcHJv
amVjdGVkIHNpemFibGUgZGVwbG95bWVudHMgdG8gaW5kaWNhdGUgd2hldGhlciB0aGV5IGludGVu
dCB0byANCj4gPiA+PiBpbXBsZW1lbnQgYW5kIGRlcGxveSwgaWYgdGhlIFdHIGRlY2lkZWQgdG8g
aW5jbHVkZSB0aGUgc3Bpbi1iaXQgDQo+ID4gPj4gaW4gdGhlIHNwZWMuDQo+ID4gPg0KPiA+ID4g
TGl0ZVNwZWVkIFRlY2hub2xvZ2llcyB3aWxsIHN1cHBvcnQgdGhlIHNwaW4gYml0IC0tIGJvdGgg
aW4gb3VyIA0KPiA+ID4gc2VydmVyIGFuZCBjbGllbnQgUVVJQyBpbXBsZW1lbnRhdGlvbnMgLS0g
aWYgaXQgbWFrZSBpdCBpbnRvIHRoZSANCj4gPiA+IGRyYWZ0Lg0KPiA+DQo+ID4gTXkgaW1wbGVt
ZW50YXRpb24gaXMgbm90IHVzZWQgaW4gYW55IGxhcmdlIHNjYWxlIGRlcGxveW1lbnQsIGJ1dCBp
dCBkb2VzIHN1cHBvcnQgdGhlIHNwaW4gYml0LiBJbiBmYWN0LCBpdCBoYXMgY29uZmlndXJhdGlv
biBvcHRpb25zIHRvIHN1cHBvcnQgc3BpbiBiaXQgdmFyaWFudHM6IG5vZGUsIGp1c3Qgc3Bpbiwg
c3BpbiArIHZlYywgc3BpbiArIFFSLg0KPiA+DQo+ID4gSSB0aGluayB0aGUgc3Ryb25nZXN0IG9i
amVjdGlvbiB0byB0aGUgc3BpbiBiaXQgd2FzIHB1dCB1cCBieSBNYXJ0ZW4gZHVyaW5nIHRoZSBs
YXN0IGludGVyaW06IG1lYXN1cmluZyB0aGUgUlRUIHdpdGggdGhlIHNwaW4gYml0IGRpc2Nsb3Nl
cyB0aGUgdXNlIG9mIGhpZGRlbiBwYXRoIHNlZ21lbnRzIGxpa2UgVlBOLiBUaGlzIGlzc3VlIHdh
cyBub3QgZGlzY3Vzc2VkIGR1cmluZyB0aGUgcHJpdmFjeSBhbmFseXNpcy4NCj4gDQo+IE1heSBJ
IGFzayBpZiB0aGUgVlBOIHVzZXJzIGFyZSB0aGUgb25seSBvbmVzIHRoYXQgbG9zZSBzb21lIHBy
aXZhY3kgDQo+IHdpdGggc3BpbiBiaXRzPw0KPiANCj4gSSBhc2sgdGhpcyBiZWNhdXNlIEkgbGl2
ZSBpbiBhIGNvdW50cnkgd2hlcmUgSUlVQyB0aGUgbW9iaWxlIGNhcnJpZXJzIA0KPiBwbGFjZSB0
aGVpciBuYXRpb24td2lkZSBjYXJyaWVyLWdyYWRlIE5BVCBuZWFyIHRoZSBjYXBpdGFsIGNpdHkg
KGkuZS4sIA0KPiBUb2t5bykuIFRoYXQgbWVhbnMgdGhhdCBmb3IgcGVvcGxlIGxpdmluZyBpbiB0
aGUgY291bnRyeSwgaGF2aW5nIHNwaW4gDQo+IGJpdHMgdHVybmVkIG9uIGNvdWxkIHJldmVhbCB0
aGVpciBkaXN0YW5jZSBmcm9tIFRva3lvLg0KPiANCj4gU28gdGhlIHF1ZXN0aW9uIGlzOiBpZiBW
UE4gdXNlcnMgbmVlZCBzcGVjaWFsIGNhcmUsIGRvIHNvbWUgTkFUIHVzZXJzIA0KPiBhcyB3ZWxs
PyBPciBpZiB0aGUgYW5zd2VyIGlzIG5vLCB3aGF0IGlzIHRoZSBkaWZmZXJlbmNlIGZyb20gYmV0
d2VlbiANCj4gdGhlIHR3byBncm91cHM/DQo+IA0KPiBHZW5lcmFsbHkgc3BlYWtpbmcsIEkgYW0g
bm90IGFnYWluc3QgZ2l2aW5nIHVzZXJzIHRoZSBmcmVlZG9tIHRvIA0KPiBleHBvc2Ugc3BpbiBi
aXRzLCBob3dldmVyIEkgYW0gd29uZGVyaW5nIGhvdyB0aGUgZW5kcG9pbnRzIHNob3VsZCANCj4g
cHJvdmlkZSB0aGUgZnJlZWRvbSBvZiBjaG9pY2UgKFVJIHF1ZXN0aW9uKSBhcyB3ZWxsIGFzIHdo
YXQgdGhlIA0KPiBkZWZhdWx0IHNob3VsZCBiZS4NCj4gDQo+ID4NCj4gPiBUaGUgcHJpdmFjeSBp
c3N1ZSBjb3VsZCBiZSBtaXRpZ2F0ZWQgYnkgdHVybmluZyBvZmYgdGhlIHNwaW4gYml0IGF0IHBy
aXZhY3kgc2Vuc2l0aXZlIGNsaWVudHMsIGJ1dCB0aGlzIHdvdWxkIG1ha2UgdGhlc2UgY2xpZW50
cyAic3RpY2sgb3V0Ii4NCj4gPg0KPiA+IE9uZSBzb2x1dGlvbiB3b3VsZCBiZSB0byByZW1vdmUg
dGhlIHNwaW4gYml0IGZyb20gdGhlIHNwZWMsIHRyYWRpbmcgb2ZmIGJldHRlciBwcml2YWN5IGZv
ciB3b3JzZSBtYW5hZ2VtZW50LiBJIGFtIGNvbnNpZGVyaW5nIGFub3RoZXIgc29sdXRpb24gaW4g
d2hpY2ggcHJpdmFjeSBzZW5zaXRpdmUgY2xpZW50cyBoaWRlIHRoZSBSVFQgYnkgY29udHJvbGxp
bmcgdGhlIHNwaW4sIGZvciBleGFtcGxlIHNwaW5uaW5nIGF0IGZpeGVkIGludGVydmFscy4gSSBw
bGFuIHRlc3RpbmcgdGhhdCBvcHRpb24gaW4gUGljb3F1aWMuDQo+ID4NCj4gPiAtLSBDaHJpc3Rp
YW4gSHVpdGVtYQ0KPiA+DQo+ID4NCj4gDQo+IA0KPiAtLQ0KPiBLYXp1aG8gT2t1DQoNCg==


From nobody Wed Oct 31 10:16:38 2018
Return-Path: <ietf@trammell.ch>
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 6C66612F18C for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 10:16:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 ha8u2xMVySvR for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 10:16:33 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [IPv6:2001:8e0:40:325::36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFDC2129C6A for <quic@ietf.org>; Wed, 31 Oct 2018 10:16:32 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 98B1E34174D; Wed, 31 Oct 2018 18:16:30 +0100 (CET)
X-Iway-Path: 0
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/20439.31728); Wed, 31 Oct 2018 18:16:30 +0100 (CET)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Wed, 31 Oct 2018 18:16:29 +0100 (CET)
Received: from [145.14.214.39] (account ietf@trammell.ch HELO [10.11.33.83]) by switchplus-mail.ch (CommuniGate Pro SMTP 6.2.9) with ESMTPSA id 72287488; Wed, 31 Oct 2018 18:16:29 +0100
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <1F53D383-37C1-430B-8CC4-416CD5749A2D@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_FF083EFA-8533-46F9-839F-56AA30252059"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: Structuring the BKK spin bit discussion
Date: Wed, 31 Oct 2018 18:16:28 +0100
In-Reply-To: <DM5PR2101MB10464C5346F73F83CAC25BD1B6CD0@DM5PR2101MB1046.namprd21.prod.outlook.com>
Cc: Marcus Ihlar <marcus.ihlar@ericsson.com>, Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>, huitema <huitema@huitema.net>, Kazuho Oku <kazuhooku@gmail.com>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CANatvzxt-QBmeJUwp+MjtbpYXstPiEigDzQe0KfWJN+q0XR4Kg@mail.gmail.com> <HE1PR0701MB23938B01BC31888DAC3629B8E2CD0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <D8BB0373-FDEB-4312-94E6-BBA304D595BE@trammell.ch> <DM5PR2101MB10464C5346F73F83CAC25BD1B6CD0@DM5PR2101MB1046.namprd21.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qqcIn3FUPYkadkt0BU-Q248GZ4o>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 17:16:36 -0000

--Apple-Mail=_FF083EFA-8533-46F9-839F-56AA30252059
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

hi Praveen,

> On 31 Oct 2018, at 17:32, Praveen Balasubramanian =
<pravb=3D40microsoft.com@dmarc.ietf.org> wrote:
>=20
> Since the handshake exposes the RTT information, what is the =
geolocation privacy issue resulting from the spin bit? Brian, what are =
the edge cases you refer to where handshake latency will be different =
than what is measured by spin bit?

In the case that...

- ...an end-to-end connection actually terminates at a location =
different than the apparent location in the endpoint IP address, because =
the endpoint IP address is a VPN tunnel endpoint
- ...the "hidden" endpoint is very far (> ~3000-5000km) from the =
apparent location
- ...that VPN tunnel exists solely to make the end-to-end association =
appear to originate from at or near the VPN tunnel endpoint (e.g., =
anti-geofencing)

then the handshake RTT gives you one sample per flow, and on a per-flow =
basis, that is not enough evidence to definitively classify that flow as =
having a far hidden endpoint. The spin bit provides more evidence, since =
the upper bound on network RTT is the minimum RTT over all samples, and =
the spin bit gives you more samples per flow.

This is a contrived example, but the additional marginal geoprivacy risk =
in this specific instance is nonzero, if epsilon. I don't think it's a =
practical additional marginal risk, though, because:

- the (non-research) techniques I know of that are deployed to prevent =
breaking of geofences don't rely on latency measurement, rather on =
lookups in IP address geolocation databases *.
- given that one sample per flow in the handshake RTT and the fact that =
an endpoint will often generate multiple flows, it will eventually be =
found out anyway. The answer to the question of using a VPN for robust =
endpoint hiding is "don't do that". a far endpoint actually wants to =
remain hidden, it should be using a transport-terminating proxy or an =
anonymity network like Tor, as opposed to a simple L3.5 VPN.

As I said, turning off the spin bit is about peace of mind and =
information reduction; in my opinion, even in the absence of practical =
threat, that's reason enough to provide the option.

Cheers,

Brian

* one of the cool things hiding in that IMC paper I cited upthread is =
the fact that there's at least one anti-geofencing VPN provider that =
sells the ability to have your traffic appear to come from any country =
on earth. While the authors do not come right out and say it, it appears =
that said provider discovered it was sufficient for their business model =
to have the traffic originate from one of three easy-to-get-to, =
near-an-IXP datacenters, on three different continents, and to do some =
Layer 9 work to have the specific IPs labeled as coming from the desired =
countries in the commercial IP geolocation databases. Hacking the =
database is way easier than hacking the speed of light. :)

>=20
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of Brian Trammell (IETF)
> Sent: Wednesday, October 31, 2018 7:19 AM
> To: Marcus Ihlar <marcus.ihlar@ericsson.com>
> Cc: Lars Eggert <lars@eggert.org>; IETF QUIC WG <quic@ietf.org>; =
huitema <huitema@huitema.net>; Dmitri Tikhonov =
<dtikhonov@litespeedtech.com>; Kazuho Oku <kazuhooku@gmail.com>
> Subject: Re: Structuring the BKK spin bit discussion
>=20
> hi Kazuho, Marcus,
>=20
> +1 to this; the intra-network latency variation on the mobile segment =
of the mobile networks we looked at via the MONROE in the testbed in our =
PAM paper the followed from the RTT DT work (see =
https://github.com/mami-project/rtt-privacy-paper/blob/master/rtt-privacy.=
pdf, especially section 3.1 and figure 2(b)) makes RTT measurement on a =
mobile network useless for geolocation.
>=20
> We did notice (not shown in the paper) that different carriers (n =3D =
4, if I recall correctly) had distinct latency distributions, so with =
traffic from all Japanese mobile users you could probably use RTT data =
in the aggregate to build a "carrier classifier". This is of course a =
useless exercise because you can already tell which carrier a subscriber =
is coming from by looking at the IP address of the CGNAT exit.
>=20
> IMO there are only a few edge cases where there are actual potential =
geoprivacy issues raised by the spin bit with respect to tunneled VPN =
traffic. All of these involve trans- or intercontinental tunnels (>30ms =
of additional RTT, for 3000km of location uncertainty -- how far is it =
from Okinawa to Hokkaido?). In every case the handshake latency gives =
you away as well, but in every case long RTTs might also have =
non-distance related causes. So while I see disabling the spin bit as a =
necessary feature, especially for clients to have, IMO its utility is =
more useful for peace of mind and information reduction than for actual =
information elimination.
>=20
> Cheers,
>=20
> Brian
>=20
>> On 31 Oct 2018, at 13:40, Marcus Ihlar <marcus.ihlar@ericsson.com> =
wrote:
>>=20
>> Hi Kazuho,
>> I believe the biggest difference is the size of the hidden network =
segment.
>> In the NAT case the client and NAT are still in the same country or =
continent.
>> A quick glacne at distancecalculator.net shows that the city farthest =
from Tokyo in Japan is Naha-Shi, at 1554 km.
>> That translates to roughly 5ms at the speed of light, so the kinds of =
measurements to determine distance from Tokyo based on RTT will be =
extremely sensitive and error prone.
>> Please note that the distance analyis can be performed on handshake =
RTT as well, for connections where the initial handshake is visible at =
the measurement point.
>>=20
>>=20
>> Fr=C3=A5n: QUIC <quic-bounces@ietf.org> f=C3=B6r Kazuho Oku
>> <kazuhooku@gmail.com>
>> Skickat: den 31 oktober 2018 11:20
>> Till: Christian Huitema
>> Kopia: Lars Eggert; IETF QUIC WG; Dmitri Tikhonov
>> =C3=84mne: Re: Structuring the BKK spin bit discussion
>>=20
>> 2018=E5=B9=B410=E6=9C=8830=E6=97=A5(=E7=81=AB) 1:54 Christian Huitema =
<huitema@huitema.net>:
>>>=20
>>>=20
>>>=20
>>>> On Oct 29, 2018, at 9:08 AM, Dmitri Tikhonov =
<dtikhonov@litespeedtech.com> wrote:
>>>>=20
>>>>> On Mon, Oct 29, 2018 at 05:26:34PM +0200, Lars Eggert wrote:
>>>>> We'd specifically like to ask client and server implementors with
>>>>> projected sizable deployments to indicate whether they intent to
>>>>> implement and deploy, if the WG decided to include the spin-bit
>>>>> in the spec.
>>>>=20
>>>> LiteSpeed Technologies will support the spin bit -- both in our
>>>> server and client QUIC implementations -- if it make it into the
>>>> draft.
>>>=20
>>> My implementation is not used in any large scale deployment, but it =
does support the spin bit. In fact, it has configuration options to =
support spin bit variants: node, just spin, spin + vec, spin + QR.
>>>=20
>>> I think the strongest objection to the spin bit was put up by Marten =
during the last interim: measuring the RTT with the spin bit discloses =
the use of hidden path segments like VPN. This issue was not discussed =
during the privacy analysis.
>>=20
>> May I ask if the VPN users are the only ones that lose some privacy
>> with spin bits?
>>=20
>> I ask this because I live in a country where IIUC the mobile carriers
>> place their nation-wide carrier-grade NAT near the capital city =
(i.e.,
>> Tokyo). That means that for people living in the country, having spin
>> bits turned on could reveal their distance from Tokyo.
>>=20
>> So the question is: if VPN users need special care, do some NAT users
>> as well? Or if the answer is no, what is the difference from between
>> the two groups?
>>=20
>> Generally speaking, I am not against giving users the freedom to
>> expose spin bits, however I am wondering how the endpoints should
>> provide the freedom of choice (UI question) as well as what the
>> default should be.
>>=20
>>>=20
>>> The privacy issue could be mitigated by turning off the spin bit at =
privacy sensitive clients, but this would make these clients "stick =
out".
>>>=20
>>> One solution would be to remove the spin bit from the spec, trading =
off better privacy for worse management. I am considering another =
solution in which privacy sensitive clients hide the RTT by controlling =
the spin, for example spinning at fixed intervals. I plan testing that =
option in Picoquic.
>>>=20
>>> -- Christian Huitema
>>>=20
>>>=20
>>=20
>>=20
>> --
>> Kazuho Oku
>=20


--Apple-Mail=_FF083EFA-8533-46F9-839F-56AA30252059
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAlvZ42wACgkQihK3vwvq
RqPLVxAAwPkdchwtzc8D/3SPaPPSJ4xpFiNEfN644LlBzuT9rX+OivfUNZGTJyYB
UT8HciblksngQO2OaH68VsG+lScMDc+vXUOX5PCEDv7RRdXet/qwjf6x1IlCehF5
FV7W2V54lJxoLSpLA5ZS2Hhk+8CzTZcMDhDLwzj1a38V3sC2fHPBRe+9fg6F+vtO
FtZRKfzUv7otSLhU2l6yJZtmUcUCzWIL7S89sLihu/NZnwis2WLKLvfIgvkYC8Pt
1HY95ps5DeltXlGFwtXegLHQqXJMsgwCyaMJ1j9arD12eAuaAdLPzB7NAHCRtAkk
MkYQfwTwcawMLZmyH4NXGa0KF9QzZ1LXwulWws7s+5pqi40RAFrc2tLwwcyXfdZo
SqLgXJj94sGqQKXQzbbNKCs1zyP3EM1bTnZe3e1H9WQTaHBGyOKjflVFFKT8aHw/
SBRxbvdmegrUQCiklB/1oNxMPplPpBPguuOlw1gU/7z0R6aRreGJT7Ok6NcCa6tP
qz4EiEY3DAVdwMyRdsXaEK5e6rMRl9hAjw5zhnxxaGxZ9KlIv7rmqiAzXHrxQ8UF
gO8iozVeFpcT7/Yb36mZRh8K5W5uJZlrsEMgI6EDp6YQ9BapAzl2fVMp3HBGgPv+
z2+hjEJACD04B+Y3eOzZCYZT1XgRqpBgsFCCMAxrracc8FfY+HM=
=2Qdt
-----END PGP SIGNATURE-----

--Apple-Mail=_FF083EFA-8533-46F9-839F-56AA30252059--


From nobody Wed Oct 31 11:25:35 2018
Return-Path: <roland@zinks.de>
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 60DA8128BCC for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 11:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=zinks.de
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 dTZP3I4QQBsU for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 11:25:30 -0700 (PDT)
Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::11]) (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 BE38412D4F2 for <quic@ietf.org>; Wed, 31 Oct 2018 11:25:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1541010326; s=strato-dkim-0002; d=zinks.de; h=In-Reply-To:Date:Message-ID:From:References:To:Subject: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=CJCTdG6YQm3gpPlmPzBV+zvAvWhwSE+MKo6z5bgvBzk=; b=inXfZrYBK/czH8TovEvgwOuhJXtAOEO5y9Xw1cx9NTtodnXSczKP2d1ojBUxShefkE y4bOceFZYcS9R/rOjhhR32t3XAiEg/0oCYHmwILSqTrJUOgbprFJtO8DdS6zgfaHINzW Y/I/wWcZ+x0hBeAE8Snsy2NqZgfj1dFKhyF2Afr4Z/7JKK2GCfCld5I91s8dFXLTbOUE WJtNeJuvLAPTw2CuTxKnO6Zd+8+zaBgEfLDFVS6of6X5+/MmgJFzm5gndYwRu7yiiD/c 4KOQOqbtno5j5TUsrD2rZAfAZBnX95CmqfQJyZmlKdUydEgCqHKqhlaNKfwOqlif72as WzNA==
X-RZG-AUTH: ":PmMIdE6sW+WWP9q/oR3Lt+I+9LAZzXrcq8knhvfmBiJzkmKn1YaZ2OgvlDQJHaS2TOg="
X-RZG-CLASS-ID: mo00
Received: from [10.10.10.82] by smtp.strato.de (RZmta 44.3 DYNA|AUTH) with ESMTPSA id R07dc3u9VIPQ49e (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate) for <quic@ietf.org>; Wed, 31 Oct 2018 19:25:26 +0100 (CET)
Subject: Re: Structuring the BKK spin bit discussion
To: quic@ietf.org
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CANatvzxt-QBmeJUwp+MjtbpYXstPiEigDzQe0KfWJN+q0XR4Kg@mail.gmail.com> <HE1PR0701MB23938B01BC31888DAC3629B8E2CD0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <D8BB0373-FDEB-4312-94E6-BBA304D595BE@trammell.ch> <DM5PR2101MB10464C5346F73F83CAC25BD1B6CD0@DM5PR2101MB1046.namprd21.prod.outlook.com> <1F53D383-37C1-430B-8CC4-416CD5749A2D@trammell.ch>
From: Roland Zink <roland@zinks.de>
Message-ID: <eafbabf7-5eb7-cb57-db96-7d1539691f76@zinks.de>
Date: Wed, 31 Oct 2018 19:25:27 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <1F53D383-37C1-430B-8CC4-416CD5749A2D@trammell.ch>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/IEfm3BCwQvh1VMFyS8Z21zkmLoU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 18:25:34 -0000

Am 31.10.2018 um 18:16 schrieb Brian Trammell (IETF):
> hi Praveen,
>
>> On 31 Oct 2018, at 17:32, Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org> wrote:
>>
>> Since the handshake exposes the RTT information, what is the geolocation privacy issue resulting from the spin bit? Brian, what are the edge cases you refer to where handshake latency will be different than what is measured by spin bit?
> In the case that...
>
> - ...an end-to-end connection actually terminates at a location different than the apparent location in the endpoint IP address, because the endpoint IP address is a VPN tunnel endpoint
> - ...the "hidden" endpoint is very far (> ~3000-5000km) from the apparent location
> - ...that VPN tunnel exists solely to make the end-to-end association appear to originate from at or near the VPN tunnel endpoint (e.g., anti-geofencing)
>
> then the handshake RTT gives you one sample per flow, and on a per-flow basis, that is not enough evidence to definitively classify that flow as having a far hidden endpoint. The spin bit provides more evidence, since the upper bound on network RTT is the minimum RTT over all samples, and the spin bit gives you more samples per flow.

Often devices have patterns where the RTT can be determined. Android and 
iOS devices (and the Chrome browser) for example keep connections to 
push servers and may do periodic keep-alives. Similar when a video is 
watched using adaptive bitrate like MPEG DASH then there are 
periodically idle times followed by a new request and response. So when 
it is only about the privacy of the users RTT then the privacy isn't 
very high anyway and detection isn't restricted to the handshake.

Regards,

Roland


> This is a contrived example, but the additional marginal geoprivacy risk in this specific instance is nonzero, if epsilon. I don't think it's a practical additional marginal risk, though, because:
>
> - the (non-research) techniques I know of that are deployed to prevent breaking of geofences don't rely on latency measurement, rather on lookups in IP address geolocation databases *.
> - given that one sample per flow in the handshake RTT and the fact that an endpoint will often generate multiple flows, it will eventually be found out anyway. The answer to the question of using a VPN for robust endpoint hiding is "don't do that". a far endpoint actually wants to remain hidden, it should be using a transport-terminating proxy or an anonymity network like Tor, as opposed to a simple L3.5 VPN.
>
> As I said, turning off the spin bit is about peace of mind and information reduction; in my opinion, even in the absence of practical threat, that's reason enough to provide the option.
>
> Cheers,
>
> Brian
>
> * one of the cool things hiding in that IMC paper I cited upthread is the fact that there's at least one anti-geofencing VPN provider that sells the ability to have your traffic appear to come from any country on earth. While the authors do not come right out and say it, it appears that said provider discovered it was sufficient for their business model to have the traffic originate from one of three easy-to-get-to, near-an-IXP datacenters, on three different continents, and to do some Layer 9 work to have the specific IPs labeled as coming from the desired countries in the commercial IP geolocation databases. Hacking the database is way easier than hacking the speed of light. :)
>
>> -----Original Message-----
>> From: QUIC <quic-bounces@ietf.org> On Behalf Of Brian Trammell (IETF)
>> Sent: Wednesday, October 31, 2018 7:19 AM
>> To: Marcus Ihlar <marcus.ihlar@ericsson.com>
>> Cc: Lars Eggert <lars@eggert.org>; IETF QUIC WG <quic@ietf.org>; huitema <huitema@huitema.net>; Dmitri Tikhonov <dtikhonov@litespeedtech.com>; Kazuho Oku <kazuhooku@gmail.com>
>> Subject: Re: Structuring the BKK spin bit discussion
>>
>> hi Kazuho, Marcus,
>>
>> +1 to this; the intra-network latency variation on the mobile segment of the mobile networks we looked at via the MONROE in the testbed in our PAM paper the followed from the RTT DT work (see https://github.com/mami-project/rtt-privacy-paper/blob/master/rtt-privacy.pdf, especially section 3.1 and figure 2(b)) makes RTT measurement on a mobile network useless for geolocation.
>>
>> We did notice (not shown in the paper) that different carriers (n = 4, if I recall correctly) had distinct latency distributions, so with traffic from all Japanese mobile users you could probably use RTT data in the aggregate to build a "carrier classifier". This is of course a useless exercise because you can already tell which carrier a subscriber is coming from by looking at the IP address of the CGNAT exit.
>>
>> IMO there are only a few edge cases where there are actual potential geoprivacy issues raised by the spin bit with respect to tunneled VPN traffic. All of these involve trans- or intercontinental tunnels (>30ms of additional RTT, for 3000km of location uncertainty -- how far is it from Okinawa to Hokkaido?). In every case the handshake latency gives you away as well, but in every case long RTTs might also have non-distance related causes. So while I see disabling the spin bit as a necessary feature, especially for clients to have, IMO its utility is more useful for peace of mind and information reduction than for actual information elimination.
>>
>> Cheers,
>>
>> Brian
>>
>>> On 31 Oct 2018, at 13:40, Marcus Ihlar <marcus.ihlar@ericsson.com> wrote:
>>>
>>> Hi Kazuho,
>>> I believe the biggest difference is the size of the hidden network segment.
>>> In the NAT case the client and NAT are still in the same country or continent.
>>> A quick glacne at distancecalculator.net shows that the city farthest from Tokyo in Japan is Naha-Shi, at 1554 km.
>>> That translates to roughly 5ms at the speed of light, so the kinds of measurements to determine distance from Tokyo based on RTT will be extremely sensitive and error prone.
>>> Please note that the distance analyis can be performed on handshake RTT as well, for connections where the initial handshake is visible at the measurement point.
>>>
>>>
>>> Från: QUIC <quic-bounces@ietf.org> för Kazuho Oku
>>> <kazuhooku@gmail.com>
>>> Skickat: den 31 oktober 2018 11:20
>>> Till: Christian Huitema
>>> Kopia: Lars Eggert; IETF QUIC WG; Dmitri Tikhonov
>>> Ämne: Re: Structuring the BKK spin bit discussion
>>>
>>> 2018年10月30日(火) 1:54 Christian Huitema <huitema@huitema.net>:
>>>>
>>>>
>>>>> On Oct 29, 2018, at 9:08 AM, Dmitri Tikhonov <dtikhonov@litespeedtech.com> wrote:
>>>>>
>>>>>> On Mon, Oct 29, 2018 at 05:26:34PM +0200, Lars Eggert wrote:
>>>>>> We'd specifically like to ask client and server implementors with
>>>>>> projected sizable deployments to indicate whether they intent to
>>>>>> implement and deploy, if the WG decided to include the spin-bit
>>>>>> in the spec.
>>>>> LiteSpeed Technologies will support the spin bit -- both in our
>>>>> server and client QUIC implementations -- if it make it into the
>>>>> draft.
>>>> My implementation is not used in any large scale deployment, but it does support the spin bit. In fact, it has configuration options to support spin bit variants: node, just spin, spin + vec, spin + QR.
>>>>
>>>> I think the strongest objection to the spin bit was put up by Marten during the last interim: measuring the RTT with the spin bit discloses the use of hidden path segments like VPN. This issue was not discussed during the privacy analysis.
>>> May I ask if the VPN users are the only ones that lose some privacy
>>> with spin bits?
>>>
>>> I ask this because I live in a country where IIUC the mobile carriers
>>> place their nation-wide carrier-grade NAT near the capital city (i.e.,
>>> Tokyo). That means that for people living in the country, having spin
>>> bits turned on could reveal their distance from Tokyo.
>>>
>>> So the question is: if VPN users need special care, do some NAT users
>>> as well? Or if the answer is no, what is the difference from between
>>> the two groups?
>>>
>>> Generally speaking, I am not against giving users the freedom to
>>> expose spin bits, however I am wondering how the endpoints should
>>> provide the freedom of choice (UI question) as well as what the
>>> default should be.
>>>
>>>> The privacy issue could be mitigated by turning off the spin bit at privacy sensitive clients, but this would make these clients "stick out".
>>>>
>>>> One solution would be to remove the spin bit from the spec, trading off better privacy for worse management. I am considering another solution in which privacy sensitive clients hide the RTT by controlling the spin, for example spinning at fixed intervals. I plan testing that option in Picoquic.
>>>>
>>>> -- Christian Huitema
>>>>
>>>>
>>>
>>> --
>>> Kazuho Oku


From nobody Wed Oct 31 11:30:35 2018
Return-Path: <mikkelfj@gmail.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 1BCA312F1A5 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 11:30:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 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_PASS=-0.001, UNPARSEABLE_RELAY=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=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 nzR9i7Ruq53c for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 11:30:30 -0700 (PDT)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (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 02149128BCC for <quic@ietf.org>; Wed, 31 Oct 2018 11:30:30 -0700 (PDT)
Received: by mail-io1-xd2e.google.com with SMTP id h19-v6so1749526iog.9 for <quic@ietf.org>; Wed, 31 Oct 2018 11:30:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to;  bh=Vn7e0H4JNhkrOAsHdPuLc4/ee0HW7j3+Ck/ve0KMimo=; b=iIr9VvTEWarsP5PprhCLLbxPeuMvaLBJzO+fDFOFdP7LsjDh3hVqBumFvzOJ2MEMFu f1Ma+Z1MzwKhahTRYFLzIqG16CjWUqd9WJw/x8o5zvwn4tAmw0SXvnjtNSuC3HqEXPSp H3vb9576iDbOaUPvc+vsRxVQN1wuokaCIS6Ai3cKiRGFNT5BNEcO6oYW4N2woljvJfUN NHlQtrEaqGyUaLpMSizEvqSrAeDtGv4ea1MHkmOMdiODjFiChjRWdCntL4PNc0+HAveG 41MNGn+WEqr0ay2Fev0XiAjuav0Bi1CRl12/1Uap2gir7wbQRo8aQj6K3oBBWYxwaZGU wsVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to; bh=Vn7e0H4JNhkrOAsHdPuLc4/ee0HW7j3+Ck/ve0KMimo=; b=c4xHzNOpG1sLxXythIwrfWm2kh/pKqPNxk5oWlDzAztLymkDDjEKxSBQdur2FXnpuf UacpYM1hDiGedblDvVycSZUxuZd4qDxVnwoAmgxUxTWEPnntOLiHn1aZ1oJEyPylt5cN hutNFyWdb6YGEsfTfKWobWR1DD8vSVFzH6Kj3DzGt2uGQ/X2laE35uMzV09HVZany7py pBw5O7j01FAwMET166ITcdG3qtgV3tJ6eOfrzTI/83K/ihraGff0ZRgezKT1gtUc/KL5 zZKeKM2MrklVp8qc+UmfOPNjxbsvYn3zvXr02PN65UVlL/M6AQ/J8NLsd89MankEEUeW mwNQ==
X-Gm-Message-State: AGRZ1gJN7JlQW5o0d8y5d9vjDVBahEKkIlpsEAI4TKDlfH0yFP4yXksh yOtd0WLnLWFhwA3BtQtib+2tYO+TxK+k0ojjlNC2ig==
X-Google-Smtp-Source: AJdET5ecJ8//6bZicKKU8VtXyRIiQR0tDtS3sV0s1ZqGQgXfWdzuuVCLv6NqcUlX1bMZP17l9dV3olF/3+maz1f8FjQ=
X-Received: by 2002:a6b:ed01:: with SMTP id n1-v6mr2889692iog.106.1541010628713;  Wed, 31 Oct 2018 11:30:28 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 31 Oct 2018 11:30:27 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <eafbabf7-5eb7-cb57-db96-7d1539691f76@zinks.de>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CANatvzxt-QBmeJUwp+MjtbpYXstPiEigDzQe0KfWJN+q0XR4Kg@mail.gmail.com> <HE1PR0701MB23938B01BC31888DAC3629B8E2CD0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <D8BB0373-FDEB-4312-94E6-BBA304D595BE@trammell.ch> <DM5PR2101MB10464C5346F73F83CAC25BD1B6CD0@DM5PR2101MB1046.namprd21.prod.outlook.com> <1F53D383-37C1-430B-8CC4-416CD5749A2D@trammell.ch> <eafbabf7-5eb7-cb57-db96-7d1539691f76@zinks.de>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Wed, 31 Oct 2018 11:30:27 -0700
Message-ID: <CAN1APdcRiJcni_K6_bHSvAsWFnTqcn451qnn7oBozD6z=NumPA@mail.gmail.com>
Subject: Re: Structuring the BKK spin bit discussion
To: quic@ietf.org, Roland Zink <roland@zinks.de>
Content-Type: multipart/alternative; boundary="0000000000001ea3ee05798a7fef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/f4pBtO_5R8qY-52b6o7nvPtSHpo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 18:30:33 -0000

--0000000000001ea3ee05798a7fef
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Obviously some research effort has been put into this, but I find it hard
to believe that you cannot approximately geolocate within 3000km
considering that you derive an AES key based on remote timing attacks.


On 31 October 2018 at 19.25.45, Roland Zink (roland@zinks.de) wrote:


Am 31.10.2018 um 18:16 schrieb Brian Trammell (IETF):
> hi Praveen,
>
>> On 31 Oct 2018, at 17:32, Praveen Balasubramanian <pravb=3D
40microsoft.com@dmarc.ietf.org> wrote:
>>
>> Since the handshake exposes the RTT information, what is the geolocation
privacy issue resulting from the spin bit? Brian, what are the edge cases
you refer to where handshake latency will be different than what is
measured by spin bit?
> In the case that...
>
> - ...an end-to-end connection actually terminates at a location different
than the apparent location in the endpoint IP address, because the endpoint
IP address is a VPN tunnel endpoint
> - ...the "hidden" endpoint is very far (> ~3000-5000km) from the apparent
location
> - ...that VPN tunnel exists solely to make the end-to-end association
appear to originate from at or near the VPN tunnel endpoint (e.g.,
anti-geofencing)
>
> then the handshake RTT gives you one sample per flow, and on a per-flow
basis, that is not enough evidence to definitively classify that flow as
having a far hidden endpoint. The spin bit provides more evidence, since
the upper bound on network RTT is the minimum RTT over all samples, and the
spin bit gives you more samples per flow.

Often devices have patterns where the RTT can be determined. Android and
iOS devices (and the Chrome browser) for example keep connections to
push servers and may do periodic keep-alives. Similar when a video is
watched using adaptive bitrate like MPEG DASH then there are
periodically idle times followed by a new request and response. So when
it is only about the privacy of the users RTT then the privacy isn't
very high anyway and detection isn't restricted to the handshake.

Regards,

Roland


> This is a contrived example, but the additional marginal geoprivacy risk
in this specific instance is nonzero, if epsilon. I don't think it's a
practical additional marginal risk, though, because:
>
> - the (non-research) techniques I know of that are deployed to prevent
breaking of geofences don't rely on latency measurement, rather on lookups
in IP address geolocation databases *.
> - given that one sample per flow in the handshake RTT and the fact that
an endpoint will often generate multiple flows, it will eventually be found
out anyway. The answer to the question of using a VPN for robust endpoint
hiding is "don't do that". a far endpoint actually wants to remain hidden,
it should be using a transport-terminating proxy or an anonymity network
like Tor, as opposed to a simple L3.5 VPN.
>
> As I said, turning off the spin bit is about peace of mind and
information reduction; in my opinion, even in the absence of practical
threat, that's reason enough to provide the option.
>
> Cheers,
>
> Brian
>
> * one of the cool things hiding in that IMC paper I cited upthread is the
fact that there's at least one anti-geofencing VPN provider that sells the
ability to have your traffic appear to come from any country on earth.
While the authors do not come right out and say it, it appears that said
provider discovered it was sufficient for their business model to have the
traffic originate from one of three easy-to-get-to, near-an-IXP
datacenters, on three different continents, and to do some Layer 9 work to
have the specific IPs labeled as coming from the desired countries in the
commercial IP geolocation databases. Hacking the database is way easier
than hacking the speed of light. :)
>
>> -----Original Message-----
>> From: QUIC <quic-bounces@ietf.org> On Behalf Of Brian Trammell (IETF)
>> Sent: Wednesday, October 31, 2018 7:19 AM
>> To: Marcus Ihlar <marcus.ihlar@ericsson.com>
>> Cc: Lars Eggert <lars@eggert.org>; IETF QUIC WG <quic@ietf.org>; huitema
<huitema@huitema.net>; Dmitri Tikhonov <dtikhonov@litespeedtech.com>;
Kazuho Oku <kazuhooku@gmail.com>
>> Subject: Re: Structuring the BKK spin bit discussion
>>
>> hi Kazuho, Marcus,
>>
>> +1 to this; the intra-network latency variation on the mobile segment of
the mobile networks we looked at via the MONROE in the testbed in our PAM
paper the followed from the RTT DT work (see
https://github.com/mami-project/rtt-privacy-paper/blob/master/rtt-privacy.p=
df,
especially section 3.1 and figure 2(b)) makes RTT measurement on a mobile
network useless for geolocation.
>>
>> We did notice (not shown in the paper) that different carriers (n =3D 4,
if I recall correctly) had distinct latency distributions, so with traffic
from all Japanese mobile users you could probably use RTT data in the
aggregate to build a "carrier classifier". This is of course a useless
exercise because you can already tell which carrier a subscriber is coming
from by looking at the IP address of the CGNAT exit.
>>
>> IMO there are only a few edge cases where there are actual potential
geoprivacy issues raised by the spin bit with respect to tunneled VPN
traffic. All of these involve trans- or intercontinental tunnels (>30ms of
additional RTT, for 3000km of location uncertainty -- how far is it from
Okinawa to Hokkaido?). In every case the handshake latency gives you away
as well, but in every case long RTTs might also have non-distance related
causes. So while I see disabling the spin bit as a necessary feature,
especially for clients to have, IMO its utility is more useful for peace of
mind and information reduction than for actual information elimination.
>>
>> Cheers,
>>
>> Brian
>>
>>> On 31 Oct 2018, at 13:40, Marcus Ihlar <marcus.ihlar@ericsson.com>
wrote:
>>>
>>> Hi Kazuho,
>>> I believe the biggest difference is the size of the hidden network
segment.
>>> In the NAT case the client and NAT are still in the same country or
continent.
>>> A quick glacne at distancecalculator.net shows that the city farthest
from Tokyo in Japan is Naha-Shi, at 1554 km.
>>> That translates to roughly 5ms at the speed of light, so the kinds of
measurements to determine distance from Tokyo based on RTT will be
extremely sensitive and error prone.
>>> Please note that the distance analyis can be performed on handshake RTT
as well, for connections where the initial handshake is visible at the
measurement point.
>>>
>>>
>>> Fr=C3=A5n: QUIC <quic-bounces@ietf.org> f=C3=B6r Kazuho Oku
>>> <kazuhooku@gmail.com>
>>> Skickat: den 31 oktober 2018 11:20
>>> Till: Christian Huitema
>>> Kopia: Lars Eggert; IETF QUIC WG; Dmitri Tikhonov
>>> =C3=84mne: Re: Structuring the BKK spin bit discussion
>>>
>>> 2018=E5=B9=B410=E6=9C=8830=E6=97=A5(=E7=81=AB) 1:54 Christian Huitema <=
huitema@huitema.net>:
>>>>
>>>>
>>>>> On Oct 29, 2018, at 9:08 AM, Dmitri Tikhonov <
dtikhonov@litespeedtech.com> wrote:
>>>>>
>>>>>> On Mon, Oct 29, 2018 at 05:26:34PM +0200, Lars Eggert wrote:
>>>>>> We'd specifically like to ask client and server implementors with
>>>>>> projected sizable deployments to indicate whether they intent to
>>>>>> implement and deploy, if the WG decided to include the spin-bit
>>>>>> in the spec.
>>>>> LiteSpeed Technologies will support the spin bit -- both in our
>>>>> server and client QUIC implementations -- if it make it into the
>>>>> draft.
>>>> My implementation is not used in any large scale deployment, but it
does support the spin bit. In fact, it has configuration options to support
spin bit variants: node, just spin, spin + vec, spin + QR.
>>>>
>>>> I think the strongest objection to the spin bit was put up by Marten
during the last interim: measuring the RTT with the spin bit discloses the
use of hidden path segments like VPN. This issue was not discussed during
the privacy analysis.
>>> May I ask if the VPN users are the only ones that lose some privacy
>>> with spin bits?
>>>
>>> I ask this because I live in a country where IIUC the mobile carriers
>>> place their nation-wide carrier-grade NAT near the capital city (i.e.,
>>> Tokyo). That means that for people living in the country, having spin
>>> bits turned on could reveal their distance from Tokyo.
>>>
>>> So the question is: if VPN users need special care, do some NAT users
>>> as well? Or if the answer is no, what is the difference from between
>>> the two groups?
>>>
>>> Generally speaking, I am not against giving users the freedom to
>>> expose spin bits, however I am wondering how the endpoints should
>>> provide the freedom of choice (UI question) as well as what the
>>> default should be.
>>>
>>>> The privacy issue could be mitigated by turning off the spin bit at
privacy sensitive clients, but this would make these clients "stick out".
>>>>
>>>> One solution would be to remove the spin bit from the spec, trading
off better privacy for worse management. I am considering another solution
in which privacy sensitive clients hide the RTT by controlling the spin,
for example spinning at fixed intervals. I plan testing that option in
Picoquic.
>>>>
>>>> -- Christian Huitema
>>>>
>>>>
>>>
>>> --
>>> Kazuho Oku

--0000000000001ea3ee05798a7fef
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Obviously some resea=
rch effort has been put into this, but I find it hard to believe that you c=
annot approximately geolocate within 3000km considering that you derive an =
AES key based on remote timing attacks.</div> <div id=3D"bloop_sign_1541010=
468240030976" class=3D"bloop_sign"><div style=3D"font-family:helvetica,aria=
l;font-size:13px"><br></div></div> <br><p class=3D"airmail_on">On 31 Octobe=
r 2018 at 19.25.45, Roland Zink (<a href=3D"mailto:roland@zinks.de">roland@=
zinks.de</a>) wrote:</p> <blockquote type=3D"cite" class=3D"clean_bq"><span=
><div><div></div><div>
<br>Am 31.10.2018 um 18:16 schrieb Brian Trammell (IETF):
<br>&gt; hi Praveen,
<br>&gt;
<br>&gt;&gt; On 31 Oct 2018, at 17:32, Praveen Balasubramanian &lt;pravb=3D=
<a href=3D"mailto:40microsoft.com@dmarc.ietf.org">40microsoft.com@dmarc.iet=
f.org</a>&gt; wrote:
<br>&gt;&gt;
<br>&gt;&gt; Since the handshake exposes the RTT information, what is the g=
eolocation privacy issue resulting from the spin bit? Brian, what are the e=
dge cases you refer to where handshake latency will be different than what =
is measured by spin bit?
<br>&gt; In the case that...
<br>&gt;
<br>&gt; - ...an end-to-end connection actually terminates at a location di=
fferent than the apparent location in the endpoint IP address, because the =
endpoint IP address is a VPN tunnel endpoint
<br>&gt; - ...the &quot;hidden&quot; endpoint is very far (&gt; ~3000-5000k=
m) from the apparent location
<br>&gt; - ...that VPN tunnel exists solely to make the end-to-end associat=
ion appear to originate from at or near the VPN tunnel endpoint (e.g., anti=
-geofencing)
<br>&gt;
<br>&gt; then the handshake RTT gives you one sample per flow, and on a per=
-flow basis, that is not enough evidence to definitively classify that flow=
 as having a far hidden endpoint. The spin bit provides more evidence, sinc=
e the upper bound on network RTT is the minimum RTT over all samples, and t=
he spin bit gives you more samples per flow.
<br>
<br>Often devices have patterns where the RTT can be determined. Android an=
d =20
<br>iOS devices (and the Chrome browser) for example keep connections to =
=20
<br>push servers and may do periodic keep-alives. Similar when a video is =
=20
<br>watched using adaptive bitrate like MPEG DASH then there are =20
<br>periodically idle times followed by a new request and response. So when=
 =20
<br>it is only about the privacy of the users RTT then the privacy isn&#39;=
t =20
<br>very high anyway and detection isn&#39;t restricted to the handshake.
<br>
<br>Regards,
<br>
<br>Roland
<br>
<br>
<br>&gt; This is a contrived example, but the additional marginal geoprivac=
y risk in this specific instance is nonzero, if epsilon. I don&#39;t think =
it&#39;s a practical additional marginal risk, though, because:
<br>&gt;
<br>&gt; - the (non-research) techniques I know of that are deployed to pre=
vent breaking of geofences don&#39;t rely on latency measurement, rather on=
 lookups in IP address geolocation databases *.
<br>&gt; - given that one sample per flow in the handshake RTT and the fact=
 that an endpoint will often generate multiple flows, it will eventually be=
 found out anyway. The answer to the question of using a VPN for robust end=
point hiding is &quot;don&#39;t do that&quot;. a far endpoint actually want=
s to remain hidden, it should be using a transport-terminating proxy or an =
anonymity network like Tor, as opposed to a simple L3.5 VPN.
<br>&gt;
<br>&gt; As I said, turning off the spin bit is about peace of mind and inf=
ormation reduction; in my opinion, even in the absence of practical threat,=
 that&#39;s reason enough to provide the option.
<br>&gt;
<br>&gt; Cheers,
<br>&gt;
<br>&gt; Brian
<br>&gt;
<br>&gt; * one of the cool things hiding in that IMC paper I cited upthread=
 is the fact that there&#39;s at least one anti-geofencing VPN provider tha=
t sells the ability to have your traffic appear to come from any country on=
 earth. While the authors do not come right out and say it, it appears that=
 said provider discovered it was sufficient for their business model to hav=
e the traffic originate from one of three easy-to-get-to, near-an-IXP datac=
enters, on three different continents, and to do some Layer 9 work to have =
the specific IPs labeled as coming from the desired countries in the commer=
cial IP geolocation databases. Hacking the database is way easier than hack=
ing the speed of light. :)
<br>&gt;
<br>&gt;&gt; -----Original Message-----
<br>&gt;&gt; From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org">quic-b=
ounces@ietf.org</a>&gt; On Behalf Of Brian Trammell (IETF)
<br>&gt;&gt; Sent: Wednesday, October 31, 2018 7:19 AM
<br>&gt;&gt; To: Marcus Ihlar &lt;<a href=3D"mailto:marcus.ihlar@ericsson.c=
om">marcus.ihlar@ericsson.com</a>&gt;
<br>&gt;&gt; Cc: Lars Eggert &lt;<a href=3D"mailto:lars@eggert.org">lars@eg=
gert.org</a>&gt;; IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org">quic@ie=
tf.org</a>&gt;; huitema &lt;<a href=3D"mailto:huitema@huitema.net">huitema@=
huitema.net</a>&gt;; Dmitri Tikhonov &lt;<a href=3D"mailto:dtikhonov@litesp=
eedtech.com">dtikhonov@litespeedtech.com</a>&gt;; Kazuho Oku &lt;<a href=3D=
"mailto:kazuhooku@gmail.com">kazuhooku@gmail.com</a>&gt;
<br>&gt;&gt; Subject: Re: Structuring the BKK spin bit discussion
<br>&gt;&gt;
<br>&gt;&gt; hi Kazuho, Marcus,
<br>&gt;&gt;
<br>&gt;&gt; +1 to this; the intra-network latency variation on the mobile =
segment of the mobile networks we looked at via the MONROE in the testbed i=
n our PAM paper the followed from the RTT DT work (see <a href=3D"https://g=
ithub.com/mami-project/rtt-privacy-paper/blob/master/rtt-privacy.pdf">https=
://github.com/mami-project/rtt-privacy-paper/blob/master/rtt-privacy.pdf</a=
>, especially section 3.1 and figure 2(b)) makes RTT measurement on a mobil=
e network useless for geolocation.
<br>&gt;&gt;
<br>&gt;&gt; We did notice (not shown in the paper) that different carriers=
 (n =3D 4, if I recall correctly) had distinct latency distributions, so wi=
th traffic from all Japanese mobile users you could probably use RTT data i=
n the aggregate to build a &quot;carrier classifier&quot;. This is of cours=
e a useless exercise because you can already tell which carrier a subscribe=
r is coming from by looking at the IP address of the CGNAT exit.
<br>&gt;&gt;
<br>&gt;&gt; IMO there are only a few edge cases where there are actual pot=
ential geoprivacy issues raised by the spin bit with respect to tunneled VP=
N traffic. All of these involve trans- or intercontinental tunnels (&gt;30m=
s of additional RTT, for 3000km of location uncertainty -- how far is it fr=
om Okinawa to Hokkaido?). In every case the handshake latency gives you awa=
y as well, but in every case long RTTs might also have non-distance related=
 causes. So while I see disabling the spin bit as a necessary feature, espe=
cially for clients to have, IMO its utility is more useful for peace of min=
d and information reduction than for actual information elimination.
<br>&gt;&gt;
<br>&gt;&gt; Cheers,
<br>&gt;&gt;
<br>&gt;&gt; Brian
<br>&gt;&gt;
<br>&gt;&gt;&gt; On 31 Oct 2018, at 13:40, Marcus Ihlar &lt;<a href=3D"mail=
to:marcus.ihlar@ericsson.com">marcus.ihlar@ericsson.com</a>&gt; wrote:
<br>&gt;&gt;&gt;
<br>&gt;&gt;&gt; Hi Kazuho,
<br>&gt;&gt;&gt; I believe the biggest difference is the size of the hidden=
 network segment.
<br>&gt;&gt;&gt; In the NAT case the client and NAT are still in the same c=
ountry or continent.
<br>&gt;&gt;&gt; A quick glacne at <a href=3D"http://distancecalculator.net=
">distancecalculator.net</a> shows that the city farthest from Tokyo in Jap=
an is Naha-Shi, at 1554 km.
<br>&gt;&gt;&gt; That translates to roughly 5ms at the speed of light, so t=
he kinds of measurements to determine distance from Tokyo based on RTT will=
 be extremely sensitive and error prone.
<br>&gt;&gt;&gt; Please note that the distance analyis can be performed on =
handshake RTT as well, for connections where the initial handshake is visib=
le at the measurement point.
<br>&gt;&gt;&gt;
<br>&gt;&gt;&gt;
<br>&gt;&gt;&gt; Fr=C3=A5n: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.or=
g">quic-bounces@ietf.org</a>&gt; f=C3=B6r Kazuho Oku
<br>&gt;&gt;&gt; &lt;<a href=3D"mailto:kazuhooku@gmail.com">kazuhooku@gmail=
.com</a>&gt;
<br>&gt;&gt;&gt; Skickat: den 31 oktober 2018 11:20
<br>&gt;&gt;&gt; Till: Christian Huitema
<br>&gt;&gt;&gt; Kopia: Lars Eggert; IETF QUIC WG; Dmitri Tikhonov
<br>&gt;&gt;&gt; =C3=84mne: Re: Structuring the BKK spin bit discussion
<br>&gt;&gt;&gt;
<br>&gt;&gt;&gt; 2018=E5=B9=B410=E6=9C=8830=E6=97=A5(=E7=81=AB) 1:54 Christ=
ian Huitema &lt;<a href=3D"mailto:huitema@huitema.net">huitema@huitema.net<=
/a>&gt;:
<br>&gt;&gt;&gt;&gt;
<br>&gt;&gt;&gt;&gt;
<br>&gt;&gt;&gt;&gt;&gt; On Oct 29, 2018, at 9:08 AM, Dmitri Tikhonov &lt;<=
a href=3D"mailto:dtikhonov@litespeedtech.com">dtikhonov@litespeedtech.com</=
a>&gt; wrote:
<br>&gt;&gt;&gt;&gt;&gt;
<br>&gt;&gt;&gt;&gt;&gt;&gt; On Mon, Oct 29, 2018 at 05:26:34PM +0200, Lars=
 Eggert wrote:
<br>&gt;&gt;&gt;&gt;&gt;&gt; We&#39;d specifically like to ask client and s=
erver implementors with
<br>&gt;&gt;&gt;&gt;&gt;&gt; projected sizable deployments to indicate whet=
her they intent to
<br>&gt;&gt;&gt;&gt;&gt;&gt; implement and deploy, if the WG decided to inc=
lude the spin-bit
<br>&gt;&gt;&gt;&gt;&gt;&gt; in the spec.
<br>&gt;&gt;&gt;&gt;&gt; LiteSpeed Technologies will support the spin bit -=
- both in our
<br>&gt;&gt;&gt;&gt;&gt; server and client QUIC implementations -- if it ma=
ke it into the
<br>&gt;&gt;&gt;&gt;&gt; draft.
<br>&gt;&gt;&gt;&gt; My implementation is not used in any large scale deplo=
yment, but it does support the spin bit. In fact, it has configuration opti=
ons to support spin bit variants: node, just spin, spin + vec, spin + QR.
<br>&gt;&gt;&gt;&gt;
<br>&gt;&gt;&gt;&gt; I think the strongest objection to the spin bit was pu=
t up by Marten during the last interim: measuring the RTT with the spin bit=
 discloses the use of hidden path segments like VPN. This issue was not dis=
cussed during the privacy analysis.
<br>&gt;&gt;&gt; May I ask if the VPN users are the only ones that lose som=
e privacy
<br>&gt;&gt;&gt; with spin bits?
<br>&gt;&gt;&gt;
<br>&gt;&gt;&gt; I ask this because I live in a country where IIUC the mobi=
le carriers
<br>&gt;&gt;&gt; place their nation-wide carrier-grade NAT near the capital=
 city (i.e.,
<br>&gt;&gt;&gt; Tokyo). That means that for people living in the country, =
having spin
<br>&gt;&gt;&gt; bits turned on could reveal their distance from Tokyo.
<br>&gt;&gt;&gt;
<br>&gt;&gt;&gt; So the question is: if VPN users need special care, do som=
e NAT users
<br>&gt;&gt;&gt; as well? Or if the answer is no, what is the difference fr=
om between
<br>&gt;&gt;&gt; the two groups?
<br>&gt;&gt;&gt;
<br>&gt;&gt;&gt; Generally speaking, I am not against giving users the free=
dom to
<br>&gt;&gt;&gt; expose spin bits, however I am wondering how the endpoints=
 should
<br>&gt;&gt;&gt; provide the freedom of choice (UI question) as well as wha=
t the
<br>&gt;&gt;&gt; default should be.
<br>&gt;&gt;&gt;
<br>&gt;&gt;&gt;&gt; The privacy issue could be mitigated by turning off th=
e spin bit at privacy sensitive clients, but this would make these clients =
&quot;stick out&quot;.
<br>&gt;&gt;&gt;&gt;
<br>&gt;&gt;&gt;&gt; One solution would be to remove the spin bit from the =
spec, trading off better privacy for worse management. I am considering ano=
ther solution in which privacy sensitive clients hide the RTT by controllin=
g the spin, for example spinning at fixed intervals. I plan testing that op=
tion in Picoquic.
<br>&gt;&gt;&gt;&gt;
<br>&gt;&gt;&gt;&gt; -- Christian Huitema
<br>&gt;&gt;&gt;&gt;
<br>&gt;&gt;&gt;&gt;
<br>&gt;&gt;&gt;
<br>&gt;&gt;&gt; --
<br>&gt;&gt;&gt; Kazuho Oku
<br>
<br></div></div></span></blockquote></body></html>

--0000000000001ea3ee05798a7fef--


From nobody Wed Oct 31 11:44:39 2018
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 DD6D012F1A5 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 11:44:38 -0700 (PDT)
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 qKJa1PtD88lG for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 11:44:35 -0700 (PDT)
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 000DD128BCC for <quic@ietf.org>; Wed, 31 Oct 2018 11:44:34 -0700 (PDT)
Received: from xsmtp04.mail2web.com ([168.144.250.231]) by mx114.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1gHvTj-0013Jn-Rn for quic@ietf.org; Wed, 31 Oct 2018 19:44:32 +0100
Received: from [10.5.2.15] (helo=xmail05.myhosting.com) by xsmtp04.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1gHvT2-0007CC-7I for quic@ietf.org; Wed, 31 Oct 2018 14:44:28 -0400
Received: (qmail 18282 invoked from network); 31 Oct 2018 18:04:44 -0000
Received: from unknown (HELO [192.168.1.100]) (Authenticated-user:_huitema@huitema.net@[172.56.42.225]) (envelope-sender <huitema@huitema.net>) by xmail05.myhosting.com (qmail-ldap-1.03) with ESMTPA for <kazuhooku@gmail.com>; 31 Oct 2018 18:04:43 -0000
To: "Brian Trammell (IETF)" <ietf@trammell.ch>, Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>
Cc: IETF QUIC WG <quic@ietf.org>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Lars Eggert <lars@eggert.org>, Marcus Ihlar <marcus.ihlar@ericsson.com>, Kazuho Oku <kazuhooku@gmail.com>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CANatvzxt-QBmeJUwp+MjtbpYXstPiEigDzQe0KfWJN+q0XR4Kg@mail.gmail.com> <HE1PR0701MB23938B01BC31888DAC3629B8E2CD0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <D8BB0373-FDEB-4312-94E6-BBA304D595BE@trammell.ch> <DM5PR2101MB10464C5346F73F83CAC25BD1B6CD0@DM5PR2101MB1046.namprd21.prod.outlook.com> <1F53D383-37C1-430B-8CC4-416CD5749A2D@trammell.ch>
From: Christian Huitema <huitema@huitema.net>
Openpgp: preference=signencrypt
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= xsBNBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAHNJ0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PsLAeQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1bOwE0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAcLBfgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8=
Message-ID: <c7c51c5a-8f4a-c802-4c73-339288a3650d@huitema.net>
Date: Wed, 31 Oct 2018 11:04:23 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <1F53D383-37C1-430B-8CC4-416CD5749A2D@trammell.ch>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="O4ZNBWoBt4PoGsdmmviTwFPrUvIUNQYSy"
Subject: Re: Structuring the BKK spin bit discussion
X-Originating-IP: 168.144.250.231
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.19)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5lErpz26ZRHhKCVhrQnLsy5602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO37pNwwF1lRXh5rzvPzo9Jts1ujulqUFmMITHM77eiViMDovPjqp8V2sUC7aqDc1Js7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pB81OoFFeyN79z+gPkYXfWpU5EpHPznVavQp4h 1cyzxbQFXqQgkkYk8mNUb0+uxPxh1SJjtqxg9ToQOYgvpTXfiGuWFHL2CFALT37iujGyMC2K4cpU ualkQCN89mFr4hzV9Toz96geSJlwqLmXoHr6lp7KuHNaaKdg7iBEZefdsNV4YIf5ImMTjwbMKp8Y PS53nf7PGnOpecYaJDTU+UZIqwmLmW5xejNwBYllkh0bdnaT4v31xJIi7Xy4t2KeuFNOkVWClPVv bW5lVyQanRxw5nX9q2g89emBxjk4vbSaEK4mBBZyuzyr5ZxdVdkNxbnSdADg25CDX78caB9Pgj1m GtOITDa6LxNU+V0EKPyMEBN0UMMXiIAmQgAEYQzWQE9OdwZYmnjXBK2n15GHwEE5LdmmSBFbIW9r 526bbdC2BGGAImxrekFydH4DojSCKJXVXfdz0+Q1eHsqtFQKXUaZ+neRXC2QfgHjpfJ8vHpGO1E1 rv1PGgUKl8Fk2bt6QgNFhK7unSGReaJhoESbMmiSIg22jZRl2kt9yYk5WCrzAYDU5KVZAuq7iRMO L0AqK7ggpVX8TjAFljeNKxwQ6q+MLFk8tLLJBl4kzg4sgIGXQirWSvYFRhImdY0rWWgG9tFHfqb5 R4VemuUI6bcEARsm0IytVb/slNDbsfQrrYxivbA+rrlJHnDn0ZA2vL1vx9UKwR4HDdDnpJnsnZ8l 83pkqWSdEOMftBjsWb6BDQzjSsFWaUKZ1JJcGxhwBY5CmZTIj1ZZXNSM8qRmAS6qJ+SgmVRG5T3/ 95tq5YraEsSrXcIxL7hrJSk60SF3F6RYOYr2
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/iIuLUuVxdvZOq4GY2l8o5ZR4VHs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 18:44:39 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--O4ZNBWoBt4PoGsdmmviTwFPrUvIUNQYSy
Content-Type: multipart/mixed; boundary="vs0G6Wft9JYNFRD11x8Ln4Ymz9tWNBAej";
 protected-headers="v1"
From: Christian Huitema <huitema@huitema.net>
To: "Brian Trammell (IETF)" <ietf@trammell.ch>,
 Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>
Cc: IETF QUIC WG <quic@ietf.org>,
 Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Lars Eggert
 <lars@eggert.org>, Marcus Ihlar <marcus.ihlar@ericsson.com>,
 Kazuho Oku <kazuhooku@gmail.com>
Message-ID: <c7c51c5a-8f4a-c802-4c73-339288a3650d@huitema.net>
Subject: Re: Structuring the BKK spin bit discussion
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org>
 <20181029160802.GD7258@ubuntu-dmitri>
 <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net>
 <CANatvzxt-QBmeJUwp+MjtbpYXstPiEigDzQe0KfWJN+q0XR4Kg@mail.gmail.com>
 <HE1PR0701MB23938B01BC31888DAC3629B8E2CD0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
 <D8BB0373-FDEB-4312-94E6-BBA304D595BE@trammell.ch>
 <DM5PR2101MB10464C5346F73F83CAC25BD1B6CD0@DM5PR2101MB1046.namprd21.prod.outlook.com>
 <1F53D383-37C1-430B-8CC4-416CD5749A2D@trammell.ch>
In-Reply-To: <1F53D383-37C1-430B-8CC4-416CD5749A2D@trammell.ch>

--vs0G6Wft9JYNFRD11x8Ln4Ymz9tWNBAej
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US

On 10/31/2018 10:16 AM, Brian Trammell (IETF) wrote:

> In the case that...
>
> - ...an end-to-end connection actually terminates at a location differe=
nt than the apparent location in the endpoint IP address, because the end=
point IP address is a VPN tunnel endpoint
> - ...the "hidden" endpoint is very far (> ~3000-5000km) from the appare=
nt location
> - ...that VPN tunnel exists solely to make the end-to-end association a=
ppear to originate from at or near the VPN tunnel endpoint (e.g., anti-ge=
ofencing)

The actual scenario relates to UDP/QUIC proxies, and how they would
compare to TCP/TLS proxies.

Today, I can build a TCP/TLS proxy that accepts connections at port 443,
examines the (possibly encrypted) SNI in the client Hello, establishes a
TCP connection to the hidden destination, and relays TLS packets between
the 2 connections. TCP is hop by hop, TLS is end to end, examining TCP
sequence numbers and ACKs does not reveal the hidden leg of the service.

Suppose that I build a QUIC proxy that accepts UDP packets at port 4433,
and then does pretty much the same job as load balancer: look for the
(possibly encrypted) SNI inside the client hello for initial packets;
look for the destination connection ID in other packets; forward the UDP
packets to the hidden server based on that, and vice versa in the other
direction. This is sort of equivalent to the TCP/TLS proxy scenario: UDP
is hop by hop; QUIC and TLS is end to end. The QUIC messages are
encrypted and don't reveal much, but the spin bit will reveal the
end-to-end RTT.

Of course, examining the content and timing of packets might in both
cases reveal the end-to-end RTT, but layering makes a difference. The
application may be able to implement end-to-end measures to counter the
analysis of end-to-end traffic, but the application cannot easily
influence the spin bit.

-- Christian Huitema




--vs0G6Wft9JYNFRD11x8Ln4Ymz9tWNBAej--

--O4ZNBWoBt4PoGsdmmviTwFPrUvIUNQYSy
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJb2e65AAoJELba05IUOHVQo1AH/0UOpnH5zX/v+PPCCcQg9ZcK
P6JEL96bcBhmBZqzZtbVu0Ogg542kTN+ue+Vr6AF33RMPpRroK3ezWTedAEiTzAU
ycrmCAqZAbuDFdZCl6J4WAUOtOAhMwhRbOAZVoyCQ9i4hkg0Cc87tYn0C2aUminF
I+PCSsg1UJ5zASJgZOGLWIzW+HQS3Sj63cll4G+0s6kI1J/HVmOtapOkC41AkaZ6
GUDfj+MCjL4xLVtSD9ivZeqYSSJxy69BPIGcDA3wjW80UkUiWw6rJi6hfp5Fg4LL
3TQeTTdS1FHCbJ4yxnn0uJbWqZp4exwpgKD50Ocoa4tVVsPE4B6wZ7JSDyy0ggI=
=lE1G
-----END PGP SIGNATURE-----

--O4ZNBWoBt4PoGsdmmviTwFPrUvIUNQYSy--


From nobody Wed Oct 31 13:36:35 2018
Return-Path: <dschinazi.ietf@gmail.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 812B7130DC8 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 13:36:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.009
X-Spam-Level: 
X-Spam-Status: No, score=-0.009 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, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 7Adt2JGiZpp4 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 13:36:29 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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 42A31130D7A for <quic@ietf.org>; Wed, 31 Oct 2018 13:36:29 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id g59-v6so3824984plb.10 for <quic@ietf.org>; Wed, 31 Oct 2018 13:36:29 -0700 (PDT)
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=0a8yaUoFu4x/q1y1fx1TKUVJe/Kn0ck+5talidqV42Q=; b=sh+td4JuonOs+6iovUNB5M44PdYqCyeYRiIUSgXNc3IhudRTaPJ+vQNIZyzdlDB5kw 71713OoM5xXJg2TmsOb4ubaksEalMqX8FLQPvBIdC7CtN1NQJN32RDs9uy0DC46tKtHw e2CJ5EspIT1OmoXBzgXLIpyCuesGX7f4PtQjZmYYTb/V5N4BHYKOlLzxoro24fSQAynO 8FpnefAS0aOpi3qlCiPDZX7Iags7jgTgaH78x/AAjA6lV/K3w7zzuPcCBLx1+D6Myu72 XlVaGyCWrlIQAIsLWXWxrt8loRkaVL3gQwHmK6IivT4PM4TmekDdEy1ldU3rT9PZSFfj 56UQ==
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=0a8yaUoFu4x/q1y1fx1TKUVJe/Kn0ck+5talidqV42Q=; b=RgSSxsGWnle8gDUUt0jqq9qBGQFd8/VFDId7+ivwCUCvhQ1RLNnyw8Elmg8HwdRy0v UAHp5lIWvHDrsKRNBA9eN/EAaJeIlZ5BP2GMOhih6tEfc2tt+yjFnzBd+MIeZzI/oQze AqWaVO7HZ3W2aJjxIq8gIVhZcnj8Z0chP/kpChtqZC/DNQCIVW2xpciO1Tbu3dX2ASR0 57s9zR+DFVlB23N2voOQsuM48prgq6FV/SqlxDgUt3pWVSvV+7hy/rO6Wj9iQK18eJvn P6Cnr/f3BqevUP5ns1vE4+jccD5hTOKwBax2x6UUpXVhZ4elb7JoXS7xERy25J13377z cvjQ==
X-Gm-Message-State: AGRZ1gJcGFfcSM2b3iXvKxVePz8elbz1K5TJSBVy1YouTfmuIBmEgc4D 2ujgzBzlHiXHEz0B3dM3AFLUjua0/zXCEI9SkjQ=
X-Google-Smtp-Source: AJdET5dRfxRMsixKdHYpD9dAxSMnzoqg4R3UQ860sG4nidC4wPHNSjxX8Ba4qm3Le9cZTaAgH4dsXvZT645zWgGJB40=
X-Received: by 2002:a17:902:6a8b:: with SMTP id n11-v6mr4789976plk.16.1541018188735;  Wed, 31 Oct 2018 13:36:28 -0700 (PDT)
MIME-Version: 1.0
References: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com> <CAKcm_gMDOyJC0AwOo2knN6AMxVbySjGsrLvjcC9A8UA9xcvcWw@mail.gmail.com> <19D3595B-8845-45B6-A60D-9E934DD49FAC@apple.com> <CACpbDcfk+GXb3aL5LG0wQM87thRGO5Y4Q+9cbXf5YuW1=jWCig@mail.gmail.com> <B7BE2454-2A4D-4323-B0A5-0D73BD4B819F@apple.com> <CACpbDcd5YWcxyEH3TS1FssgAT13oqeBBQg92+J0uJqhxPz2qkA@mail.gmail.com> <4b7b02d110f74139bacae8e01c54a4af@usma1ex-dag1mb6.msg.corp.akamai.com> <CACpbDcfDtwLqhR5um5OwzT2d8QAKrwhqmJJ3TRX9j-JhECRB4Q@mail.gmail.com> <CAKcm_gMZxRTYRJhTkw7EFxkK-qkNLr-hUd-XXj8HxS7Pho3SyQ@mail.gmail.com>
In-Reply-To: <CAKcm_gMZxRTYRJhTkw7EFxkK-qkNLr-hUd-XXj8HxS7Pho3SyQ@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Wed, 31 Oct 2018 13:36:17 -0700
Message-ID: <CAPDSy+4Ve93PK6OAGkme-8HAcuhMij3ydtt+eObv-YXHgeJhgg@mail.gmail.com>
Subject: Re: flow control and DATAGRAM
To: Ian Swett <ianswett@google.com>
Cc: jri.ietf@gmail.com, QUIC <quic@ietf.org>, ilubashe@akamai.com,  martin.thomson@gmail.com, Tommy Pauly <tpauly@apple.com>
Content-Type: multipart/alternative; boundary="000000000000bb684905798c417e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/NAE0XUc6HnoIdTXy0MUoiblX490>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 20:36:34 -0000

--000000000000bb684905798c417e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I agree.

Another use case is VPN, where one could want to have the control traffic
(e.g. what IKEv2 does today) be sent reliably with flow control and have
the data path (e.g. what ESP does today) be sent unreliably without flow
control. As with ESP today, flow control is handled by upper layer
protocols (e.g. TCP) inside the encryption/encapsulation.

I think it might be best to remove flow control from this proposal
entirely, and if later someone has a use-case for flow-controlled datagrams
we can define a new different extension then.

David

On Wed, Oct 31, 2018 at 9:01 AM Ian Swett <ianswett=3D
40google.com@dmarc.ietf.org> wrote:

> If you add flow control, there's little benefit over a unidirectional
> stream, so adding flow control fundamentally breaks this design.
>
> My goal is to use this for cases when I want to use a single QUIC
> connection to replace DTLS or RTP + something reliable.  WebRTC is the
> obvious use case, but not the only one.  DTLS and RTP don't have flow
> control, so adding it just make the application mapping a lot more comple=
x.
>
> On Tue, Oct 30, 2018 at 12:23 AM Jana Iyengar <jri.ietf@gmail.com> wrote:
>
>> Igor,
>>
>> I had thought that this was similar to canceling streams, but you're
>> right. Canceling a stream gets rid of stream flow control state entirely=
,
>> where in this case, the receiver cannot discard flow control state.
>>
>> I don't have any great ideas right now, but I fear that not having flow
>> control simply punts the problem down the road. FWIW, this may be quite
>> fine for this extension, and we can surely evolve it to have flow contro=
l
>> when we have a way to do it.
>>
>> - jana
>>
>> On Mon, Oct 29, 2018 at 8:54 PM Lubashev, Igor <ilubashe@akamai.com>
>> wrote:
>>
>>> Jana,
>>>
>>> > The simplest scheme would be to reserve a stream ID for DATAGRAM data
>>> -- [...]
>>> > -- and then MAX_STREAM_DATA uses this
>>> > stream ID for flow control of DATAGRAM octets.
>>>
>>> There are many dragons that way. Flow control indicates commitment to
>>> buffer data. When sender does not retransmit, when does receiver give u=
p
>>> its commitment to wait for (and buffer) earlier data so it can advance
>>> MAX_STREAM_DATA to allow the sender to send more data? Can the signal f=
rom
>>> sender tolerate loss/reordering vs STREAM frames (assuming the datagram=
 can
>>> be split for sending in multiple QUIC packets)? These dragons can be
>>> conquered (see my partially reliable streams draft, v2 or v3), but this=
 is
>>> not simple. :(
>>>
>>> - Igor
>>>
>>> -----Original Message-----
>>> *From:* Jana Iyengar [jri.ietf@gmail.com]
>>> *Received:* Monday, 29 Oct 2018, 10:24PM
>>> *To:* tpauly@apple.com [tpauly@apple.com]
>>> *CC:* Ian Swett [ianswett@google.com]; QUIC WG [quic@ietf.org]; Martin
>>> Thomson [martin.thomson@gmail.com <martin..thomson@gmail.com>]
>>> *Subject:* Re: flow control and DATAGRAM
>>>
>>> Hey Tommy,
>>>
>>>
>>>> I'm not suggesting any changes to when the packet gets
>>>> ack'ed=E2=80=94specifically, I was responding to Martin's hypothetical=
 of having an
>>>> ACK to a DATAGRAM frame meaning that the application had processed the
>>>> frame. My impression is that the ACK to a packet containing a DATAGRAM
>>>> frame means:
>>>> - The packet made it across the network to the QUIC endpoint on the
>>>> other side
>>>>
>>>
>>> ... and was processed by the QUIC receiver (not necessarily by the
>>> application). This is the same semantic as the ack of a regular frame.
>>>
>>>
>>>> - The QUIC implementation will deliver the DATAGRAM frame to
>>>> application (it won't drop it locally)
>>>>
>>>
>>> In which case you will need flow control. If you agree, then we're on
>>> the same page so far.
>>>
>>>
>>>> Having a separate outstanding data limit for the DATAGRAM "stream" is
>>>> an interesting solution to the space. It would then have the nice prop=
erty
>>>> of not looking like traditional flow control. It could even be measure=
d in
>>>> number of frames, rather than bytes (depending on what the limiting fa=
ctors
>>>> are).
>>>>
>>>
>>> In terms of flow control, I don't think DATAGRAM flow control is any
>>> different than sending stream data on any stream and then canceling it =
--
>>> there are no retransmissions, but the sender still accounts for it in f=
low
>>> control. My thought here was basically to have exactly the same flow
>>> control as stream-level flow control, and allow for DATAGRAM bytes to f=
all
>>> within connection-level flow control as normal.
>>>
>>> The simplest scheme would be to reserve a stream ID for DATAGRAM data -=
-
>>> this could be 0 or 2^62-1 -- and then MAX_STREAM_DATA uses this stream =
ID
>>> for flow control of DATAGRAM octets. Alternatively, define a new frame
>>> called MAX_DATAGRAM_DATA that is carries the largest allowed offset tha=
t
>>> can be sent as a DATAGRAM, and introduce an offset field in the DATAGRA=
M
>>> frame.
>>>
>>> - jana
>>>
>>>
>>>> Thanks,
>>>> Tommy
>>>>
>>>> On Oct 29, 2018, at 12:37 PM, Jana Iyengar <jri.ietf@gmail.com> wrote:
>>>>
>>>> Tommy,
>>>>
>>>> Changing the semantics of an acknowledgment to include delivery up to
>>>> the application is a fundamental change to the QUIC machinery, and it
>>>> doesn't work. First, an ACK frame acknowledges packets, and you can't =
have
>>>> different semantics of an acknowledgment for different frames that are
>>>> carried in the same packet. Second, it interferes with RTT measurement=
, and
>>>> it conflates flow control with congestion control, which gets messy. (=
This
>>>> conflation is an interesting problem to consider theoretically, but no=
t one
>>>> for us at this time IMO.)
>>>>
>>>> I am wondering if applying a stream-level flow control for DATAGRAMs
>>>> makes sense instead. Meaning that you treat DATAGRAMs as a separate st=
ream
>>>> for flow control purposes. You might benefit from having an offset in =
the
>>>> DATAGRAM frame for this purpose.
>>>>
>>>> - jana
>>>>
>>>> On Mon, Oct 29, 2018 at 8:21 AM Tommy Pauly <tpauly@apple.com> wrote:
>>>>
>>>>> Hi Martin, Ian,
>>>>>
>>>>> Yes, very good points!
>>>>>
>>>>> My tendency would be to prefer what Ian's implementation does of
>>>>> passing these DATAGRAM frames up immediately to the application. I do=
n't
>>>>> think that the acknowledgment needs to indicate that the frame was
>>>>> processed by the application, but merely that it has been delivered t=
o the
>>>>> application (that is, the application doesn't get to do anything with=
 the
>>>>> frame that can influence the acknowledgment).
>>>>>
>>>>> The current draft indicates that the content of the DATAGRAM frames
>>>>> contributes to the limit used for MAX_DATA, and that if that amount i=
s
>>>>> reached, the frames are blocked along with STREAM data. I think this =
works
>>>>> fine for the sender, while the receiver gets into the discussion you
>>>>> present. On the sender side, reaching MAX_DATA could mean dropping th=
e
>>>>> DATAGRAM frames when unable to send more (and sending BLOCKED instead=
).
>>>>> Since the frames are unreliable, they can be dropped in this situatio=
n
>>>>> without violating the API contract.
>>>>>
>>>>> On the receiver side, I agree that queuing the DATAGRAM frames to let
>>>>> the application drive flow control in the way it does for STREAM fram=
es
>>>>> adds complexity and diminishes the utility of the frame and ACKs.. Ho=
wever,
>>>>> I can imagine taking a fairly simplistic approach in which the data l=
imit
>>>>> is automatically increased upon reception of the frame (and the frame=
 is
>>>>> immediately passed to the application). This allows the initial_max_d=
ata to
>>>>> put a cap on the amount of data in a given flight of DATAGRAMS, and a=
llow
>>>>> the size of a flight of DATAGRAM frames to be limited by the amount o=
f room
>>>>> left over from STREAM data that may be consuming the connection-wide =
flow
>>>>> control.
>>>>>
>>>>> Perhaps this approach needs a clearer name other than "flow control",
>>>>> since it has a somewhat different meaning in effect.
>>>>>
>>>>> As for ACKs, if we never discard on the receiver side, the ACK is
>>>>> pretty useful for detecting if there was network-based packet loss.
>>>>>
>>>>> Thanks,
>>>>> Tommy
>>>>>
>>>>> On Oct 29, 2018, at 5:32 AM, Ian Swett <ianswett@google.com> wrote:
>>>>>
>>>>> Good catch Martin, I missed that in the draft as well, and I also
>>>>> think it's impossibly with the proposed design.
>>>>>
>>>>> And yes, I think Martin's proposed solution is likely the only
>>>>> practical one.  In my implementation, the frame is passed up to the
>>>>> application immediately, so technically QUIC processed it, and it's t=
he
>>>>> application's job to decide what to do with it.
>>>>>
>>>>> On Mon, Oct 29, 2018 at 1:16 AM Martin Thomson <
>>>>> martin.thomson@gmail..com <martin.thomson@gmail.com>> wrote:
>>>>>
>>>>>> Hi Tommy,
>>>>>>
>>>>>> Your slides - <
>>>>>> https://github.com/quicwg/wg-materials/blob/master/ietf103/IETF103-Q=
UIC-Datagram.pdf
>>>>>> <https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_q=
uicwg_wg-2Dmaterials_blob_master_ietf103_IETF103-2DQUIC-2DDatagram.pdf&d=3D=
DwMFaQ&c=3D96ZbZZcaMF4w0F4jpN6LZg&r=3DDjn3bQ5uNJDPM_2skfL3rW1tzcIxyjUZdn_m5=
5KPmlo&m=3DBOGSfZ4hKaubJ6yww-9_8EDX3OccYvdip0g3k4t66hQ&s=3Dqiyr1YY1MHWjhIrP=
fwHXN6FCdsG8wUuhAuqczkosLlI&e=3D>
>>>>>> >
>>>>>> - say that DATAGRAM frames respect connection-level flow control.  I
>>>>>> missed that in the draft, and I don't know how they can do that in t=
he
>>>>>> face of packet loss, especially when you don't necessarily retransmi=
t
>>>>>> lost DATAGRAM frames.
>>>>>>
>>>>>> For that to work, you would need a bunch more machinery to make the
>>>>>> connection-level flow control sync between endpoints in the case tha=
t
>>>>>> packets are lost.  A disagreement about how much flow control is use=
d
>>>>>> causes things to break down badly.  Ian and I discussed this point a=
t
>>>>>> the last meeting and quickly agreed that while it might be nice to
>>>>>> have flow control for this stuff, the increase in complexity is
>>>>>> considerable and (at the time) we thought it wouldn't be worth it.
>>>>>>
>>>>>> The problem that introduces is that you could end up having too many
>>>>>> DATAGRAM frames arrive.  The receiver has to drop something at the
>>>>>> point that it can't handle them.  And we say that when you acknowled=
ge
>>>>>> something, you processed it.  That's tricky.
>>>>>>
>>>>>> It might be easier to say that a QUIC acknowledgment for a DATAGRAM
>>>>>> frame doesn't mean that it was received and processed by an
>>>>>> application.  An endpoint might discard these frames before passing
>>>>>> them on to applications if it doesn't have space.  In other words,
>>>>>> acknowledgment of DATAGRAM means that QUIC got it, not that the
>>>>>> application got it.  Sadly, that means that the QUIC acknowledgment
>>>>>> machinery doesn't help the application that uses DATAGRAM all that
>>>>>> much.  Also, the lower bound on reliability is 0, which isn't the be=
st
>>>>>> thing ever.
>>>>>>
>>>>>> Hard choices, I know.  I don't have a good design for maintaining
>>>>>> connection-level flow control (or any back pressure mechanism with
>>>>>> equivalent properties) that doesn't add both complexity and overhead=
.
>>>>>>
>>>>>> Cheers,
>>>>>> Martin
>>>>>>
>>>>>>
>>>>>
>>>>

--000000000000bb684905798c417e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I agree.</div><div><br></div>Another use case is VPN,=
 where one could want to have the control traffic (e.g. what IKEv2 does tod=
ay) be sent reliably with flow control and have the data path (e.g. what ES=
P does today) be sent unreliably without flow control. As with ESP today, f=
low control is handled by upper layer protocols (e.g. TCP) inside the encry=
ption/encapsulation.<div><br></div><div>I think it might be best to remove =
flow control from this proposal entirely, and if later someone has a use-ca=
se for flow-controlled datagrams we can define a new different extension th=
en.</div><div><br></div><div>David</div></div><br><div class=3D"gmail_quote=
"><div dir=3D"ltr">On Wed, Oct 31, 2018 at 9:01 AM Ian Swett &lt;ianswett=
=3D<a href=3D"mailto:40google.com@dmarc.ietf.org">40google.com@dmarc.ietf.o=
rg</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">=
If you add flow control, there&#39;s little benefit over a unidirectional s=
tream, so adding flow control fundamentally breaks this design.<div><br>My =
goal is to use this for cases when I want to use a single QUIC connection t=
o replace DTLS or RTP + something reliable.=C2=A0 WebRTC is the obvious use=
 case, but not the only one.=C2=A0 DTLS and RTP don&#39;t have flow control=
, so adding it just make the application mapping a lot more complex.</div><=
/div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Oct 30, 2018 a=
t 12:23 AM Jana Iyengar &lt;<a href=3D"mailto:jri.ietf@gmail.com" target=3D=
"_blank">jri.ietf@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><div dir=3D"ltr">Igor,<div><br></div><div>I had thought that this w=
as similar to canceling streams, but you&#39;re right. Canceling a stream g=
ets rid of stream flow control state entirely, where in this case, the rece=
iver cannot discard flow control state.</div><div><br></div><div>I don&#39;=
t have any great ideas right now, but I fear that not having flow control s=
imply punts the problem down the road. FWIW, this may be quite fine for thi=
s extension, and we can surely evolve it to have flow control when we have =
a way to do it.</div><div><br></div><div>- jana</div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr">On Mon, Oct 29, 2018 at 8:54 PM Lubashev,=
 Igor &lt;<a href=3D"mailto:ilubashe@akamai.com" target=3D"_blank">ilubashe=
@akamai.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">




<div>
<span style=3D"font-family:Calibri,Arial,Helvetica,sans-serif;font-size:11p=
t;color:black">Jana,<br>
<br>
&gt; The simplest scheme would be to reserve a stream ID for DATAGRAM data =
-- [...]<br>
&gt; -- and then MAX_STREAM_DATA uses this<br>
&gt; stream ID for flow control of DATAGRAM octets.<br>
<br>
There are many dragons that way. Flow control indicates commitment to buffe=
r data. When sender does not retransmit, when does receiver give up its com=
mitment to wait for (and buffer) earlier data so it can advance MAX_STREAM_=
DATA to allow the sender to send
 more data? Can the signal from sender tolerate loss/reordering vs STREAM f=
rames (assuming the datagram can be split for sending in multiple QUIC pack=
ets)? These dragons can be conquered (see my partially reliable streams dra=
ft, v2 or v3), but this is not simple.
 :(<br>
<br>
- Igor<br>
<br>
<span style=3D"color:black">-----Original Message----- <br>
<b>From:</b> Jana Iyengar [<a href=3D"mailto:jri.ietf@gmail.com" target=3D"=
_blank">jri.ietf@gmail.com</a>]<br>
<b>Received:</b> Monday, 29 Oct 2018, 10:24PM<br>
<b>To:</b> <a href=3D"mailto:tpauly@apple.com" target=3D"_blank">tpauly@app=
le.com</a> [<a href=3D"mailto:tpauly@apple.com" target=3D"_blank">tpauly@ap=
ple.com</a>]<br>
<b>CC:</b> Ian Swett [<a href=3D"mailto:ianswett@google.com" target=3D"_bla=
nk">ianswett@google.com</a>]; QUIC WG [<a href=3D"mailto:quic@ietf.org" tar=
get=3D"_blank">quic@ietf.org</a>]; Martin Thomson [<a href=3D"mailto:martin=
..thomson@gmail.com" target=3D"_blank">martin.thomson@gmail.com</a>]<br>
<b>Subject:</b> Re: flow control and DATAGRAM<br>
<br>
</span></span>
<div>
<div dir=3D"ltr">Hey Tommy,
<div class=3D"gmail_quote">
<div>=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;line-break:after-white-space">
<div>I&#39;m not suggesting any changes to when the packet gets ack&#39;ed=
=E2=80=94specifically, I was responding to Martin&#39;s hypothetical of hav=
ing an ACK to a DATAGRAM frame meaning that the application had processed t=
he frame. My impression is that the ACK to a packet containing
 a DATAGRAM frame means:</div>
<div>- The packet made it across the network to the QUIC endpoint on the ot=
her side</div>
<div></div>
</div>
</blockquote>
<div><br>
</div>
<div>... and was processed by the QUIC receiver (not necessarily by the app=
lication). This is the same semantic as the ack of a regular frame.</div>
<div>=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;line-break:after-white-space">
<div>- The QUIC implementation will deliver the DATAGRAM frame to applicati=
on (it won&#39;t drop it locally)</div>
</div>
</blockquote>
<div><br>
</div>
<div>In which case you will need flow control. If you agree, then we&#39;re=
 on the same page so far.</div>
<div>=C2=A0=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;line-break:after-white-space">
<div>Having a separate outstanding data limit for the DATAGRAM &quot;stream=
&quot; is an interesting solution to the space. It would then have the nice=
 property of not looking like traditional flow control. It could even be me=
asured in number of frames, rather than bytes
 (depending on what the limiting factors are).</div>
</div>
</blockquote>
<div><br>
</div>
<div>In terms of flow control, I don&#39;t think DATAGRAM flow control is a=
ny different than sending stream data on any stream and then canceling it -=
- there are no retransmissions, but the sender still accounts for it in flo=
w control. My thought here was basically
 to have exactly the same flow control as stream-level flow control, and al=
low for DATAGRAM bytes to fall within connection-level flow control as norm=
al.</div>
<div><br>
</div>
<div>The simplest scheme would be to reserve a stream ID for DATAGRAM data =
-- this could be 0 or 2^62-1 -- and then MAX_STREAM_DATA uses this stream I=
D for flow control of DATAGRAM octets. Alternatively, define a new frame ca=
lled MAX_DATAGRAM_DATA that is carries
 the largest allowed offset that can be sent as a DATAGRAM, and introduce a=
n offset field in the DATAGRAM frame.</div>
<div><br>
</div>
<div>- jana</div>
<div>=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;line-break:after-white-space">
<div>Thanks,</div>
<div>Tommy<br>
<div><br>
<blockquote type=3D"cite">
<div>On Oct 29, 2018, at 12:37 PM, Jana Iyengar &lt;<a href=3D"mailto:jri.i=
etf@gmail.com" target=3D"_blank">jri.ietf@gmail.com</a>&gt; wrote:</div>
<br class=3D"m_-1773148686139427117m_2073751388042974774m_48774626533498799=
31m_6117190503338714891Apple-interchange-newline">
<div>
<div dir=3D"ltr">Tommy,
<div><br>
</div>
<div>Changing the semantics of an acknowledgment to include delivery up to =
the application is a fundamental change to the QUIC machinery, and it doesn=
&#39;t work. First, an ACK frame acknowledges packets, and you can&#39;t ha=
ve different semantics of an acknowledgment
 for different frames that are carried in the same packet. Second, it inter=
feres with RTT measurement, and it conflates flow control with congestion c=
ontrol, which gets messy. (This conflation is an interesting problem to con=
sider theoretically, but not one
 for us at this time IMO.)</div>
<div><br>
</div>
<div>I am wondering if applying a stream-level flow control for DATAGRAMs m=
akes sense instead. Meaning that you treat DATAGRAMs as a separate stream f=
or flow control purposes. You might benefit from having an offset in the DA=
TAGRAM frame for this purpose.</div>
<div><br>
</div>
<div>- jana</div>
</div>
<br>
<div class=3D"gmail_quote">
<div dir=3D"ltr">On Mon, Oct 29, 2018 at 8:21 AM Tommy Pauly &lt;<a href=3D=
"mailto:tpauly@apple.com" target=3D"_blank">tpauly@apple.com</a>&gt; wrote:=
<br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;line-break:after-white-space">Hi Martin,=
 Ian,
<div><br>
</div>
<div>Yes, very good points!</div>
<div><br>
</div>
<div>My tendency would be to prefer what Ian&#39;s implementation does of p=
assing these DATAGRAM frames up immediately to the application. I don&#39;t=
 think that the acknowledgment needs to indicate that the frame was process=
ed by the application, but merely that it
 has been delivered to the application (that is, the application doesn&#39;=
t get to do anything with the frame that can influence the acknowledgment).=
</div>
<div><br>
</div>
<div>The current draft indicates that the content of the DATAGRAM frames co=
ntributes to the limit used for=C2=A0MAX_DATA, and that if that amount is r=
eached, the frames are blocked along with STREAM data. I think this works f=
ine for the sender, while the receiver
 gets into the discussion you present. On the sender side, reaching MAX_DAT=
A could mean dropping the DATAGRAM frames when unable to send more (and sen=
ding BLOCKED instead). Since the frames are unreliable, they can be dropped=
 in this situation without violating
 the API contract.=C2=A0</div>
<div><br>
</div>
<div>On the receiver side, I agree that queuing the DATAGRAM frames to let =
the application drive flow control in the way it does for STREAM frames add=
s complexity and diminishes the utility of the frame and ACKs.. However, I =
can imagine taking a fairly simplistic
 approach in which the data limit is automatically increased upon reception=
 of the frame (and the frame is immediately passed to the application). Thi=
s allows the initial_max_data to put a cap on the amount of data in a given=
 flight of DATAGRAMS, and allow
 the size of a flight of DATAGRAM frames to be limited by the amount of roo=
m left over from STREAM data that may be consuming the connection-wide flow=
 control.=C2=A0</div>
<div><br>
</div>
<div>Perhaps this approach needs a clearer name other than &quot;flow contr=
ol&quot;, since it has a somewhat different meaning in effect.</div>
<div><br>
</div>
<div>As for ACKs, if we never discard on the receiver side, the ACK is pret=
ty useful for detecting if there was network-based packet loss.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Tommy=C2=A0</div>
<div>
<div><br>
<blockquote type=3D"cite">
<div>On Oct 29, 2018, at 5:32 AM, Ian Swett &lt;<a href=3D"mailto:ianswett@=
google.com" target=3D"_blank">ianswett@google.com</a>&gt; wrote:</div>
<br class=3D"m_-1773148686139427117m_2073751388042974774m_48774626533498799=
31m_6117190503338714891m_-1061371301160893898Apple-interchange-newline">
<div>
<div dir=3D"ltr">Good catch Martin, I missed that in the draft as well, and=
 I also think it&#39;s impossibly with the proposed design.
<div><br>
</div>
<div>And yes, I think Martin&#39;s proposed solution is likely the only pra=
ctical one.=C2=A0 In my implementation, the frame is passed up to the appli=
cation immediately, so technically QUIC processed it, and it&#39;s the appl=
ication&#39;s job to decide what to do with it.</div>
</div>
<br>
<div class=3D"gmail_quote">
<div dir=3D"ltr">On Mon, Oct 29, 2018 at 1:16 AM Martin Thomson &lt;<a href=
=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomson@gmail=
..com</a>&gt; wrote:<br>
</div>
<blockquote class=3D"gmail_quote">Hi Tommy,<br>
<br>
Your slides - &lt;<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dh=
ttps-3A__github.com_quicwg_wg-2Dmaterials_blob_master_ietf103_IETF103-2DQUI=
C-2DDatagram.pdf&amp;d=3DDwMFaQ&amp;c=3D96ZbZZcaMF4w0F4jpN6LZg&amp;r=3DDjn3=
bQ5uNJDPM_2skfL3rW1tzcIxyjUZdn_m55KPmlo&amp;m=3DBOGSfZ4hKaubJ6yww-9_8EDX3Oc=
cYvdip0g3k4t66hQ&amp;s=3Dqiyr1YY1MHWjhIrPfwHXN6FCdsG8wUuhAuqczkosLlI&amp;e=
=3D" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/wg-mate=
rials/blob/master/ietf103/IETF103-QUIC-Datagram.pdf</a>&gt;<br>
- say that DATAGRAM frames respect connection-level flow control.=C2=A0 I<b=
r>
missed that in the draft, and I don&#39;t know how they can do that in the<=
br>
face of packet loss, especially when you don&#39;t necessarily retransmit<b=
r>
lost DATAGRAM frames.<br>
<br>
For that to work, you would need a bunch more machinery to make the<br>
connection-level flow control sync between endpoints in the case that<br>
packets are lost.=C2=A0 A disagreement about how much flow control is used<=
br>
causes things to break down badly.=C2=A0 Ian and I discussed this point at<=
br>
the last meeting and quickly agreed that while it might be nice to<br>
have flow control for this stuff, the increase in complexity is<br>
considerable and (at the time) we thought it wouldn&#39;t be worth it.<br>
<br>
The problem that introduces is that you could end up having too many<br>
DATAGRAM frames arrive.=C2=A0 The receiver has to drop something at the<br>
point that it can&#39;t handle them.=C2=A0 And we say that when you acknowl=
edge<br>
something, you processed it.=C2=A0 That&#39;s tricky.<br>
<br>
It might be easier to say that a QUIC acknowledgment for a DATAGRAM<br>
frame doesn&#39;t mean that it was received and processed by an<br>
application.=C2=A0 An endpoint might discard these frames before passing<br=
>
them on to applications if it doesn&#39;t have space.=C2=A0 In other words,=
<br>
acknowledgment of DATAGRAM means that QUIC got it, not that the<br>
application got it.=C2=A0 Sadly, that means that the QUIC acknowledgment<br=
>
machinery doesn&#39;t help the application that uses DATAGRAM all that<br>
much.=C2=A0 Also, the lower bound on reliability is 0, which isn&#39;t the =
best<br>
thing ever.<br>
<br>
Hard choices, I know.=C2=A0 I don&#39;t have a good design for maintaining<=
br>
connection-level flow control (or any back pressure mechanism with<br>
equivalent properties) that doesn&#39;t add both complexity and overhead.<b=
r>
<br>
Cheers,<br>
Martin<br>
<br>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>

</blockquote></div>
</blockquote></div>
</blockquote></div>

--000000000000bb684905798c417e--


From nobody Wed Oct 31 13:57:33 2018
Return-Path: <briansw@microsoft.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 B98D9130DC8 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 13:57:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.47
X-Spam-Level: 
X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 zYGpH7ECTlJE for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 13:57:29 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0110.outbound.protection.outlook.com [104.47.38.110]) (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 D1BD0130D7A for <quic@ietf.org>; Wed, 31 Oct 2018 13:57:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=p1v/ajpqIlQs9TubWTJU3tkipCrqGBC7UB0Bqf0Z0fY=; b=EJ7caNqY0QBOIBO1y08zm2jxNzohuj64aRUMLyjpR0mdbqeIqWgCyuIwTLwtnTyl3fYUXA1zuO/C/1JaOFGG5gnSVqIAPsMPPigxkJoMu1M31Ol0D1ggML5pAYgX4l0XsAgvVXXga/kGyDQ9r/KSx85MOqG89FG8XL5cybvjwoA=
Received: from DM5PR21MB0124.namprd21.prod.outlook.com (10.173.173.11) by DM5PR21MB0859.namprd21.prod.outlook.com (10.173.172.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1294.4; Wed, 31 Oct 2018 20:57:27 +0000
Received: from DM5PR21MB0124.namprd21.prod.outlook.com ([fe80::41a:587a:d7ed:d689]) by DM5PR21MB0124.namprd21.prod.outlook.com ([fe80::41a:587a:d7ed:d689%2]) with mapi id 15.20.1294.014; Wed, 31 Oct 2018 20:57:27 +0000
From: Brian Swander <briansw@microsoft.com>
To: "quic@ietf.org" <quic@ietf.org>
Subject: question about QPACK decode framing
Thread-Topic: question about QPACK decode framing
Thread-Index: AdRxXAgQAarsEnv1SKWHpz4SzyG/9Q==
Date: Wed, 31 Oct 2018 20:57:27 +0000
Message-ID: <DM5PR21MB01241538AD5198940C463A13B3CD0@DM5PR21MB0124.namprd21.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=briansw@microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2018-10-31T20:57:25.7207916Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic; Sensitivity=General
x-originating-ip: [2001:4898:80e8:1:95a3:2d80:61c2:85b2]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR21MB0859; 6:h+xwiJWSRTh6+zIzju8gj6zkTBjDfFPG7dVDBSKXQ+ati6rMZ6Ft0B7q8IGoLIsLUvVkteqA1UDZo/jBBf4RfQSlBc4yqTa3SgPKfxglCVjh5bqde+SqXM5YXN2l3uKngCO66W0y7dfaNTNURVp7PFE3IgJlJ5aNLOJ4vhetHahA4rtp1vXe+qJaF99Pl2AMELosUuIESk5E6708akj1sEHFBzGcJKWi/9Abds6coci3pguZe0npVUyAZyc7akLcXkqOQm8KiaPhxIcUDjeRrvV72mufOwAe3L1y8CUXWRQlaDnkIJjBnp4a/TAkQ3NX0da3uLhHS5H446AAbEyPI007MxmRQe65O+bvrFAtSks1B+HqM3l/tUsD5BtZDCFc5jLmOHZMoKhqg3PMmIdF+SVggtIxxkwr9Q5++xrOizOwHDKWkNc/0EHymbl4WMjfrh3345XXG+WvR1oDMNBW9g==; 5:Hc6OslQckOZzR0bu3MUbjqo7GPrM9BZ7d7jL3Pz2xtUC2kZMc3vp10kfMtVJPo5jZvmo45eagNwO/aEDz2ugXNsxdPdT5mSmvWEcIS+8m1V2Uo6ogyKR0mRmzIRcbD+zQCHFgTBv4U32dqr1bIMSIvmxfLL1H6spe/MaXBwQHPc=; 7:05rcArCT30YFh5e3U40nxA/xI3JU5tT/Y7IYQ3kXOJBkNEKFrAJMrbUtL6xRTxg9tyxcxN8O+VWh9VYiJTVUxVIcm9cwQaBPJXXDN1jdkNq2VZlu+8zs+W5M+6a91hC+ztHVwILHNusV6VCpwbXEEg==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: f537ac5c-6a55-4417-2ccb-08d63f737731
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(5600074)(711020)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:DM5PR21MB0859; 
x-ms-traffictypediagnostic: DM5PR21MB0859:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=briansw@microsoft.com; 
x-microsoft-antispam-prvs: <DM5PR21MB0859B436964391FB12282674B3CD0@DM5PR21MB0859.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(21748063052155)(28532068793085)(190501279198761)(227612066756510); 
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(8220035)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3231382)(944501410)(52105095)(2018427008)(3002001)(6055026)(148016)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123562045)(20161123560045)(20161123564045)(201708071742011)(7699051)(76991095); SRVR:DM5PR21MB0859; BCL:0; PCL:0; RULEID:; SRVR:DM5PR21MB0859; 
x-forefront-prvs: 084285FC5C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(366004)(376002)(136003)(39860400002)(346002)(199004)(189003)(9686003)(6306002)(5630700001)(2501003)(14454004)(54896002)(8936002)(81166006)(558084003)(81156014)(256004)(7736002)(68736007)(1730700003)(8676002)(478600001)(33656002)(53936002)(2906002)(10290500003)(102836004)(6436002)(5250100002)(99286004)(55016002)(5640700003)(7696005)(97736004)(8990500004)(106356001)(105586002)(6116002)(2351001)(6916009)(5660300001)(476003)(486006)(46003)(71190400001)(186003)(71200400001)(25786009)(2900100001)(74316002)(86612001)(6506007)(10090500001)(86362001)(22452003)(316002)(790700001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR21MB0859; H:DM5PR21MB0124.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: DPwc2rU9NnsYHxWbIrH8xZRWLI9t/1BE4CVDUDaElAbrQ8NhWLnlNWQOJ5ffEtF429kFIOs7N3KKaVLvIB2Nmb3qGdXclaseWJbDKe4dKq3ViUQGgA6HVKBYtR7LEUYGivULminr35C0wgZjC0Q5/e2tmZ+nUadB1B5XxH1HV94ar/s6aXl2sf+0ZCDmRbDng9tcmbhH85lhOkwP4livJY0sKjeHtuzH8qXqICuSEiAanr994dCCnG90BDqMKufX7fZUephtzgdaFRIdWpkUuHZaKqKWx0WG23ay0Nox9DBDLY1DEZ929TUUneRrP00oTulG0lkO0IUe+WFtK3hQ45qFhCwkFDo0+KXPYcTxIUM=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM5PR21MB01241538AD5198940C463A13B3CD0DM5PR21MB0124namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f537ac5c-6a55-4417-2ccb-08d63f737731
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Oct 2018 20:57:27.1823 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR21MB0859
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/e_WZqkNXTI7vb4aPq5JcuLMp4Yk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 20:57:32 -0000

--_000_DM5PR21MB01241538AD5198940C463A13B3CD0DM5PR21MB0124namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Is there a way to determine that we are decoding a complete set of headers =
a priori?   I.e. is the "headers length" encoded anywhere?   Or does decode=
 (control stream) just have to handle the case where we only have a partial=
 header, and we just pend and wait for more data before continuing?

Thanks
bs

--_000_DM5PR21MB01241538AD5198940C463A13B3CD0DM5PR21MB0124namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Is there a way to determine that we are decoding a c=
omplete set of headers a priori?&nbsp;&nbsp; I.e. is the &#8220;headers len=
gth&#8221; encoded anywhere?&nbsp;&nbsp; Or does decode (control stream) ju=
st have to handle the case where we only have a partial header, and
 we just pend and wait for more data before continuing?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks<o:p></o:p></p>
<p class=3D"MsoNormal">bs<o:p></o:p></p>
</div>
</body>
</html>

--_000_DM5PR21MB01241538AD5198940C463A13B3CD0DM5PR21MB0124namp_--


From nobody Wed Oct 31 14:15:39 2018
Return-Path: <dtikhonov@litespeedtech.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 09962130E3C for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 14:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 xZNsI0t1ouSg for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 14:15:24 -0700 (PDT)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (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 B2A41130E90 for <quic@ietf.org>; Wed, 31 Oct 2018 14:15:24 -0700 (PDT)
Received: by mail-qt1-x830.google.com with SMTP id l41-v6so18861256qtl.8 for <quic@ietf.org>; Wed, 31 Oct 2018 14:15:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=IL2j82afmXxYACbQQVP22rjGAzE6ggYfTF3SUuXjb4c=; b=Fw0GYD0l5pNlBO5IiJBpisGA9X4HMf+PrnyVWKrEe065Ea81HNyZDKZmujiY2fUY8h nNPS+ZtRuSMhfBr5IyOtirna52/6hVwt90XRTv8XCm514tVJ118P4PgsU1NgmNlkewJr v7hzTaeyo9RCMJanHfHy+JJ0FQSDDEDPysb3iXloFA023cf6nhP0L7vmHF2bE7g14f8V JB9WCMpGJnuo811EHhBBcPAOyjlVw1QI9OtUrs8LwXeemrslTh/uLNARpmW37VIvFzU7 s3kmicVhIXq7exCEkhHgzQkAhn2ELj9+iwXu5vtgv52q45WZwONTij9H97+jceBNmKZU R4gA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=IL2j82afmXxYACbQQVP22rjGAzE6ggYfTF3SUuXjb4c=; b=qX/KdT+dWdkQwa3WI+xjDqj+HlLgWciMwuJICVB7HZ8JT12g77u927jJ4nf086q0vE L+wjzlRTBTH5yL5yqHawcoMq3Wjj6MlsNNRf75WIQ7YQUpnJafrO6FlkAneqMty4DzI4 UeeyRO7PGUb0bWO7F9F2i1eu/oqqBxdXn0JSO8/fYlXfej6uEIDq3dHrGS9A4qLG0Gv5 1IJKByfnBZnO7/0IWzsRHiyvfSRRavt1KfzHPtXM6jHonE5vujODqTXHI0L6eF6RrNiY Y80LC/sdHSDSU8LNBuVeb9KghctqSIimp3BI4pl2jkWmP8Xxp28O50HM7R83KzFTC4FE X0/A==
X-Gm-Message-State: AGRZ1gLvtD4Uv5ZYlcrplr9cZ2Y4pOW3yKgOYzMMDYgUD6ffgYK4FG24 NTVxXXboVVBQQcTIzv3fPtYQlQ==
X-Google-Smtp-Source: AJdET5fTG/Zu33+JiG1tWelK9b+V3aMpPvXvjtestz32qxOsF6xbk/xmNThbOznD/JPTIaS4GNGH2Q==
X-Received: by 2002:ac8:7119:: with SMTP id z25-v6mr4287743qto.270.1541020523732;  Wed, 31 Oct 2018 14:15:23 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id u27-v6sm25895700qth.39.2018.10.31.14.15.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Oct 2018 14:15:23 -0700 (PDT)
Date: Wed, 31 Oct 2018 17:15:18 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Brian Swander <briansw=40microsoft.com@dmarc.ietf.org>
Cc: "quic@ietf.org" <quic@ietf.org>
Subject: Re: question about QPACK decode framing
Message-ID: <20181031211518.GA9622@ubuntu-dmitri>
Mail-Followup-To: Brian Swander <briansw=40microsoft.com@dmarc.ietf.org>, "quic@ietf.org" <quic@ietf.org>
References: <DM5PR21MB01241538AD5198940C463A13B3CD0@DM5PR21MB0124.namprd21.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DM5PR21MB01241538AD5198940C463A13B3CD0@DM5PR21MB0124.namprd21.prod.outlook.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fcj58uI7E5zjjG5IurW-_t8PXxw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 21:15:37 -0000

Hi Brian,

(I am assuming you're talking about processing the header block.)

The header block is in the HQ "HEADERS" frame which has a length.
Depending on your implementation, you may be able to tell if you
have the complete header block buffered.

  - Dmitri.

On Wed, Oct 31, 2018 at 08:57:27PM +0000, Brian Swander wrote:
> Is there a way to determine that we are decoding a complete set of headers a priori?   I.e. is the "headers length" encoded anywhere?   Or does decode (control stream) just have to handle the case where we only have a partial header, and we just pend and wait for more data before continuing?
> 
> Thanks
> bs


From nobody Wed Oct 31 15:06:46 2018
Return-Path: <kazuhooku@gmail.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 9E91B130DD6 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 15:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 heM4q-LBmuZf for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 15:06:41 -0700 (PDT)
Received: from mail-lf1-x143.google.com (mail-lf1-x143.google.com [IPv6:2a00:1450:4864:20::143]) (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 A6D09130DD4 for <quic@ietf.org>; Wed, 31 Oct 2018 15:06:40 -0700 (PDT)
Received: by mail-lf1-x143.google.com with SMTP id n18so4503909lfh.6 for <quic@ietf.org>; Wed, 31 Oct 2018 15:06:40 -0700 (PDT)
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:content-transfer-encoding; bh=isHLNyJkXZvM+FiTCS6+Q2XiLitjMQzM4Wei3lKk6no=; b=JZIfwPg6xw8ivqQNEFJD9i076iHg1WIIjN5yZdt+TFz0yBxlWIEpofON3rhV7oRYIm VYwGXhiUUidv9XcLEfLO8xqzCwnEAt8off0Qk9yW8YqSodjoogPjuxFOy7DAnYsB9HUS h0Hy33PH+8V8CurthwB43TtrwRZCre7834s6RXViHRe5LjTZE37Wq+QD3MvmYLA7Myxd bdzyz68b3HjlyNGgZUWdsYM1/hsCUXQvi3W9nxGWLylP0GcRHMnTzvQqzJE4/36AcwBA sYGB4+cQD9vV2I+3Ec2EEk/VhNKjQ2IXSs5yvEPzbCjCVfr9bt8qOLrFlSkz5Gk2rG1E C2gQ==
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:content-transfer-encoding; bh=isHLNyJkXZvM+FiTCS6+Q2XiLitjMQzM4Wei3lKk6no=; b=g8YbLB5udeItjHXkvKQBKeRmDxZNotz97L42Tb9efq0IX2MCiHosUsKpD107zvByTu Z0aRqrJsecIFM/Ab0+eIbJF9CiPCIJhi7nwsku4no1GCPQunW3dPAZs1Ka6wwfv5wuCb 6xTQSz43UDdBaxd1UuRxug55HlF3ysQtkqVkgOglT9eceKJ1PiHP0fDEEmf0ULuNUDqC zaX685hzirkwMD7WjFkvt/RryglmiseCaU2aldBR6PHEFkUJKUmnVt/MThtNujDRRxzA pIp2EPMvH3vYQeP3Imigu71aFEgv+zdqxKFIXo9bUkbZJnDn2qGoNp5jcHGXWVV5vEy+ 9QJQ==
X-Gm-Message-State: AGRZ1gIhNf7bNA//jVlIReLambzWvMa6ocGKaZv2cUd4DC4EKOcLdg71 odW2t6dkLk4ng0sk9muP/0vIJOvEjYYuodYl9QI=
X-Google-Smtp-Source: AJdET5e8mbYv3A16rze+mt76DwcCBEqpNu1KJ7yUgewv7fCpk0RSksli2Wk16zhRQkbOgVm8XmoogITeGe0pKSGXV2s=
X-Received: by 2002:a19:9b50:: with SMTP id d77mr3011000lfe.137.1541023598708;  Wed, 31 Oct 2018 15:06:38 -0700 (PDT)
MIME-Version: 1.0
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net> <CANatvzxt-QBmeJUwp+MjtbpYXstPiEigDzQe0KfWJN+q0XR4Kg@mail.gmail.com> <HE1PR0701MB23938B01BC31888DAC3629B8E2CD0@HE1PR0701MB2393.eurprd07.prod.outlook.com> <D8BB0373-FDEB-4312-94E6-BBA304D595BE@trammell.ch>
In-Reply-To: <D8BB0373-FDEB-4312-94E6-BBA304D595BE@trammell.ch>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Thu, 1 Nov 2018 07:06:27 +0900
Message-ID: <CANatvzwZZXB4d43N6g+jJ=HeTEzgdDK5KQVPKVdKDb=kBZzfpw@mail.gmail.com>
Subject: Re: Structuring the BKK spin bit discussion
To: Brian Trammell <ietf@trammell.ch>
Cc: marcus.ihlar@ericsson.com, Christian Huitema <huitema@huitema.net>,  Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>,  Dmitri Tikhonov <dtikhonov@litespeedtech.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/XvMg0br4wx8ZrwQmCyxEwQVPJx0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 22:06:44 -0000

Hi,

Marcus, Alexandre, Brian, thank you for the responses. My comments below.

2018=E5=B9=B410=E6=9C=8831=E6=97=A5(=E6=B0=B4) 23:18 Brian Trammell (IETF) =
<ietf@trammell.ch>:
>
> hi Kazuho, Marcus,
>
> +1 to this; the intra-network latency variation on the mobile segment of =
the mobile networks we looked at via the MONROE in the testbed in our PAM p=
aper the followed from the RTT DT work (see https://github.com/mami-project=
/rtt-privacy-paper/blob/master/rtt-privacy.pdf, especially section 3.1 and =
figure 2(b)) makes RTT measurement on a mobile network useless for geolocat=
ion.
>
> We did notice (not shown in the paper) that different carriers (n =3D 4, =
if I recall correctly) had distinct latency distributions, so with traffic =
from all Japanese mobile users you could probably use RTT data in the aggre=
gate to build a "carrier classifier". This is of course a useless exercise =
because you can already tell which carrier a subscriber is coming from by l=
ooking at the IP address of the CGNAT exit.
>
> IMO there are only a few edge cases where there are actual potential geop=
rivacy issues raised by the spin bit with respect to tunneled VPN traffic. =
All of these involve trans- or intercontinental tunnels (>30ms of additiona=
l RTT, for 3000km of location uncertainty -- how far is it from Okinawa to =
Hokkaido?). In every case the handshake latency gives you away as well, but=
 in every case long RTTs might also have non-distance related causes. So wh=
ile I see disabling the spin bit as a necessary feature, especially for cli=
ents to have, IMO its utility is more useful for peace of mind and informat=
ion reduction than for actual information elimination.

Thank you for sharing the research.

FWIW, inhabited islands of Japan span across 3,000km, however the
longest hidden path of the carrier-grade NAT will be around 2,000km
because Tokyo is located near the middle. So it's a bit shorter than
your numbers.

I can understand that there are other factors that have impact on the
RTT exposed by the spin bit, and that might overshadow the distance.

OTOH, I think it's important to remember that the spin bit expose many
RTT samples (every once an RTT) compared to handshake which is a one
time thing for each connection, or compared to other behavior like
client issuing HTTP requests.

For cases like large file download (in which the only output from the
receiver would be ACKs), I would assume that the spin bit would be by
far the most accurate piece of information for an observer to
determine the RTT to the connection.

>
> Cheers,
>
> Brian
>
> > On 31 Oct 2018, at 13:40, Marcus Ihlar <marcus.ihlar@ericsson.com> wrot=
e:
> >
> > Hi Kazuho,
> > I believe the biggest difference is the size of the hidden network segm=
ent.
> > In the NAT case the client and NAT are still in the same country or con=
tinent.
> > A quick glacne at distancecalculator.net shows that the city farthest f=
rom Tokyo in Japan is Naha-Shi, at 1554 km.
> > That translates to roughly 5ms at the speed of light, so the kinds of m=
easurements to determine distance from Tokyo based on RTT will be extremely=
 sensitive and error prone.
> > Please note that the distance analyis can be performed on handshake RTT=
 as well, for connections where the initial handshake is visible at the mea=
surement point.
> >
> >
> > Fr=C3=A5n: QUIC <quic-bounces@ietf.org> f=C3=B6r Kazuho Oku <kazuhooku@=
gmail.com>
> > Skickat: den 31 oktober 2018 11:20
> > Till: Christian Huitema
> > Kopia: Lars Eggert; IETF QUIC WG; Dmitri Tikhonov
> > =C3=84mne: Re: Structuring the BKK spin bit discussion
> >
> > 2018=E5=B9=B410=E6=9C=8830=E6=97=A5(=E7=81=AB) 1:54 Christian Huitema <=
huitema@huitema.net>:
> > >
> > >
> > >
> > > > On Oct 29, 2018, at 9:08 AM, Dmitri Tikhonov <dtikhonov@litespeedte=
ch.com> wrote:
> > > >
> > > >> On Mon, Oct 29, 2018 at 05:26:34PM +0200, Lars Eggert wrote:
> > > >> We'd specifically like to ask client and server implementors with
> > > >> projected sizable deployments to indicate whether they intent to
> > > >> implement and deploy, if the WG decided to include the spin-bit in
> > > >> the spec.
> > > >
> > > > LiteSpeed Technologies will support the spin bit -- both in our
> > > > server and client QUIC implementations -- if it make it into the
> > > > draft.
> > >
> > > My implementation is not used in any large scale deployment, but it d=
oes support the spin bit. In fact, it has configuration options to support =
spin bit variants: node, just spin, spin + vec, spin + QR.
> > >
> > > I think the strongest objection to the spin bit was put up by Marten =
during the last interim: measuring the RTT with the spin bit discloses the =
use of hidden path segments like VPN. This issue was not discussed during t=
he privacy analysis.
> >
> > May I ask if the VPN users are the only ones that lose some privacy
> > with spin bits?
> >
> > I ask this because I live in a country where IIUC the mobile carriers
> > place their nation-wide carrier-grade NAT near the capital city (i.e.,
> > Tokyo). That means that for people living in the country, having spin
> > bits turned on could reveal their distance from Tokyo.
> >
> > So the question is: if VPN users need special care, do some NAT users
> > as well? Or if the answer is no, what is the difference from between
> > the two groups?
> >
> > Generally speaking, I am not against giving users the freedom to
> > expose spin bits, however I am wondering how the endpoints should
> > provide the freedom of choice (UI question) as well as what the
> > default should be.
> >
> > >
> > > The privacy issue could be mitigated by turning off the spin bit at p=
rivacy sensitive clients, but this would make these clients "stick out".
> > >
> > > One solution would be to remove the spin bit from the spec, trading o=
ff better privacy for worse management. I am considering another solution i=
n which privacy sensitive clients hide the RTT by controlling the spin, for=
 example spinning at fixed intervals. I plan testing that option in Picoqui=
c.
> > >
> > > -- Christian Huitema
> > >
> > >
> >
> >
> > --
> > Kazuho Oku
>


--=20
Kazuho Oku


From nobody Wed Oct 31 15:48:40 2018
Return-Path: <fdeweerdt@fastly.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 AE831130DF5 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 15:48:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastly.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 yGbWO14mnVjA for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 15:48:37 -0700 (PDT)
Received: from mail-yw1-xc31.google.com (mail-yw1-xc31.google.com [IPv6:2607:f8b0:4864:20::c31]) (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 4E6BF130DF3 for <quic@ietf.org>; Wed, 31 Oct 2018 15:48:37 -0700 (PDT)
Received: by mail-yw1-xc31.google.com with SMTP id z72-v6so2906276ywa.0 for <quic@ietf.org>; Wed, 31 Oct 2018 15:48:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google;  h=mime-version:from:date:message-id:subject:to; bh=PNW/9peAZIIdqkkpe1hEBWl2sJ1m4rHncwb23qeRX34=; b=iP2gXpL20AYUu6/nXyyka59etUJ3CxgL0KSzgXa96gGSPQcfty0Y38AOGu1pbVzxtk MRjb9uIvOhJPiQ79G0HiytwIJFaCqmyJXaXOIqlU+G4idfOWWaN0KQbMYhqv01Vxz2Ao s7mJLON4oBGgm1or9mFFQv5F0JEBFpjxAwkC0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=PNW/9peAZIIdqkkpe1hEBWl2sJ1m4rHncwb23qeRX34=; b=fpXNhcp4Dc0/fUKhlZP2JtW3Tt+tglNmSZzkh88EUMXgfytUPxQE7LCp2tXsOsDMFJ r3gcgzjAlJX2hF0Y+2t4TGfbutDz4CYtVilb4HurjAtzUIRxZEqigIAf7z6lO9k89Zep k9+HdEAFhPKpraHaNPNxMZxO0EHcSmtEEb8XoKIy4aPi3HNuIzLfra6QYuOg8nAHwsNf c+T9Ao1SfJFNY7LZeRfyMslRI+AeQbp8LtpzzpOqa8XT1fArbGDr0fIjaHwA/ta6uxMM izcwARxzYJMY447woiEKf/+OdR3TkZlvkQIeDanRdUBaNIPAKXQCydbrN8iYIsXxDvdu gkcw==
X-Gm-Message-State: AGRZ1gKxlbhkF2GZs5qR7yjgLawZhQkFHfb1hE735Jiw27VtgkMNYiXD 9Iwhnr49s436g9/r3NYW9D8sJEoxHNYFV21RSkmo96pO4JIEnw==
X-Google-Smtp-Source: AJdET5erb1JIRy2OrvyMmuYPr1iioJ9uGHKcaBUvNKe4KsRDgabgoocv+0D82ijONsyao6hcMVHijPpEcAdouVYZsU4=
X-Received: by 2002:a81:a153:: with SMTP id y80-v6mr4983518ywg.323.1541026116162;  Wed, 31 Oct 2018 15:48:36 -0700 (PDT)
MIME-Version: 1.0
From: Frederik Deweerdt <fdeweerdt@fastly.com>
Date: Wed, 31 Oct 2018 15:48:24 -0700
Message-ID: <CAM8YLW=xxHQpLdrOmy_i5gOFRyax8UC7P9cXRSNE=xQ+gHUtDA@mail.gmail.com>
Subject: Connection coalescing in HTTP/QUIC
To: "quic@ietf.org" <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003e767f05798e1aad"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/tZ3xvwQgB1V9E624eTKsomdjKyo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 22:48:39 -0000

--0000000000003e767f05798e1aad
Content-Type: text/plain; charset="UTF-8"

Hello,

In draft-ietf-quic-http-16 "2.4. Connection Reuse" states:

>  Clients MUST NOT assume that an HTTP/QUIC endpoint is authoritative for other origins without an explicit signal.


The explicit signal bit (is it referring to an origin frame?) reads
more restrictive than connection coalescing for HTTP/2. Does that mean
that clients wouldn't
be coalescing connections based on what the certificate is
authoritative for and the DNS resolution results?


Thanks,

Frederik

--0000000000003e767f05798e1aad
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br clear=3D"all"><div>Hello,</div><div><=
br></div>In draft-ietf-quic-http-16 &quot;2.4. Connection Reuse&quot; state=
s:<div><span style=3D"font-size:1em;font-weight:bold;color:rgb(0,0,0);font-=
family:Arial,Helvetica,sans-serif"><br></span></div><div><pre class=3D"gmai=
l-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;br=
eak-before:page;color:rgb(0,0,0)">&gt;  Clients MUST NOT assume that an HTT=
P/QUIC endpoint is authoritative for other origins without an explicit sign=
al.</pre><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-t=
op:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre><pre=
 class=3D"gmail-newpage" style=3D"margin-top:0px;margin-bottom:0px;break-be=
fore:page"><font color=3D"#000000"><span style=3D"font-size:13.3333px">The =
explicit signal bit (is it referring to an origin frame?) reads more restri=
ctive than connection coalescing for HTTP/2. Does that mean that clients wo=
uldn&#39;t
be coalescing connections based on what the certificate is authoritative fo=
r and the DNS resolution results?<br></span></font></pre><pre class=3D"gmai=
l-newpage" style=3D"margin-top:0px;margin-bottom:0px;break-before:page"><fo=
nt color=3D"#000000"><span style=3D"font-size:13.3333px"><br></span></font>=
</pre><pre class=3D"gmail-newpage" style=3D"margin-top:0px;margin-bottom:0p=
x;break-before:page"><font color=3D"#000000"><span style=3D"font-size:13.33=
33px">Thanks,</span></font></pre><pre class=3D"gmail-newpage" style=3D"marg=
in-top:0px;margin-bottom:0px;break-before:page"><font color=3D"#000000"><sp=
an style=3D"font-size:13.3333px">Frederik</span></font></pre></div><div dir=
=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div style=3D"margin:0p=
x;padding:0px;color:rgb(23,43,77);font-family:-apple-system,BlinkMacSystemF=
ont,&quot;Segoe UI&quot;,Roboto,Oxygen,Ubuntu,&quot;Fira Sans&quot;,&quot;D=
roid Sans&quot;,&quot;Helvetica Neue&quot;,sans-serif;font-size:14px"><div =
style=3D"margin:0px;padding:0px"></div></div></div></div></div></div>

--0000000000003e767f05798e1aad--


From nobody Wed Oct 31 16:03:26 2018
Return-Path: <lucaspardue.24.7@gmail.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 A3364130DF5 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 16:03:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 TcTj-TtHf3Ts for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 16:03:23 -0700 (PDT)
Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (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 127FE130DD6 for <quic@ietf.org>; Wed, 31 Oct 2018 16:03:23 -0700 (PDT)
Received: by mail-vs1-xe36.google.com with SMTP id q15so11165605vso.1 for <quic@ietf.org>; Wed, 31 Oct 2018 16:03:23 -0700 (PDT)
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=fJjoy7NXB3H8jBglW8wL1BFGeoRqCikNvixteAQi7qU=; b=klpQ0fDWszw6yuMue+Agp3/jcdAiaXLjddyMc5xVphrMjyr1iOEbU56PIVZi1RpK8d pEINq/YA6/KpIIiRrE3GFOGzRfQcQ9ZCSq1l+Iyvz4+k3gFEeU5EA9nsZrf4dzLPXXdg kkC1v2jvYeLPg2GbetetpRwtgsUVbUmA4x9QygFlcbAClyLO5I8vhQDFwhicpbfGm1Bq XrSbLLGxac6SrbGH7cgiGAIG45uhxfMdw8wtEzWB1bTNo6MNIMdwA1QW3zEAWB4bZH1E EurKAL5IegVMIgspez2idNQ7I8XtME+aFb3opl4DAW5Z6dPBFWWIlW9fkThrp1anJf+K 9AAA==
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=fJjoy7NXB3H8jBglW8wL1BFGeoRqCikNvixteAQi7qU=; b=Cro4YELUNumozQUDkHZrVVjFw/ft6EXwWx6uLr8sCsIiGqxdK8gK70eofVGPoG+M9m VxydpMZXO07tyodSCuc8+E2qlS4g0DDhdKDeE0agg59DjaMYJBsRpkZMRhoHPYU+qfmj 3weqbzPvVS+YfU5ntZV3gyIzb2Jtbckv9iIkxQR5AVdCJU9R7b84vhkhJiyXtF9lwbDZ Ph7BKM/AYpuF1dqEtlPhurRmpLIp9LXd3Vb3bgsjhFUOm62Hk2JReOrrAwhZRYmRaw+B BtYHvBhntZBqZSpZP7iOiJhcWFmLnWjc0Mhm7mqZnbHVfedzb7KPIGlEJEEICZf7ct6p nHcw==
X-Gm-Message-State: AGRZ1gKcZyLnDWwTFGjaPu/O4iTmuPE6lJeoU7sDWSbLfzhct3zuuipW 7bU74ERu9Xd5OgR8qyN/KiDNgHxLwDdHTcJTjEwang==
X-Google-Smtp-Source: AJdET5flRvPgcyh547uI0wfA3lsY1bHH/tirULqFEuJjlmIFkx91L2W71AVyEHLLJcFNhfrUQic+g6LLCSFZjphnzRA=
X-Received: by 2002:a67:4719:: with SMTP id u25mr2241981vsa.27.1541027001951;  Wed, 31 Oct 2018 16:03:21 -0700 (PDT)
MIME-Version: 1.0
References: <CAM8YLW=xxHQpLdrOmy_i5gOFRyax8UC7P9cXRSNE=xQ+gHUtDA@mail.gmail.com>
In-Reply-To: <CAM8YLW=xxHQpLdrOmy_i5gOFRyax8UC7P9cXRSNE=xQ+gHUtDA@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Wed, 31 Oct 2018 23:03:08 +0000
Message-ID: <CALGR9oZvCDdp6c=CNNsFoexmB92VTMsH_b0jjRc1f5X_Bu5-bQ@mail.gmail.com>
Subject: Re: Connection coalescing in HTTP/QUIC
To: Frederik Deweerdt <fdeweerdt=40fastly.com@dmarc.ietf.org>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000a6b6705798e4f31"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YXgS-Vr6jLf2jB-guRbw2Pz3NWo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 31 Oct 2018 23:03:25 -0000

--0000000000000a6b6705798e4f31
Content-Type: text/plain; charset="UTF-8"

On Wed, 31 Oct 2018, 22:48 Frederik Deweerdt, <fdeweerdt=
40fastly.com@dmarc.ietf.org> wrote:

>
> Hello,
>
> In draft-ietf-quic-http-16 "2.4. Connection Reuse" states:
>
> >  Clients MUST NOT assume that an HTTP/QUIC endpoint is authoritative for other origins without an explicit signal.
>
>
> The explicit signal bit (is it referring to an origin frame?) reads more restrictive than connection coalescing for HTTP/2. Does that mean that clients wouldn't
> be coalescing connections based on what the certificate is authoritative for and the DNS resolution results?
>
>
> Thanks,
>
> Frederik
>
>
This PR might be the best explanation
https://github.com/quicwg/base-drafts/issues/940

Another side effect of not having an HTTP/QUIC native URI.

--0000000000000a6b6705798e4f31
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><div class=3D"gmail_quote"><div dir=3D"ltr">On Wed, =
31 Oct 2018, 22:48 Frederik Deweerdt, &lt;fdeweerdt=3D<a href=3D"mailto:40f=
astly.com@dmarc.ietf.org">40fastly.com@dmarc.ietf.org</a>&gt; wrote:<br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br cle=
ar=3D"all"><div>Hello,</div><div><br></div>In draft-ietf-quic-http-16 &quot=
;2.4. Connection Reuse&quot; states:<div><span style=3D"font-size:1em;font-=
weight:bold;color:rgb(0,0,0);font-family:Arial,Helvetica,sans-serif"><br></=
span></div><div><pre class=3D"m_106484133921675978gmail-newpage" style=3D"f=
ont-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color=
:rgb(0,0,0)">&gt;  Clients MUST NOT assume that an HTTP/QUIC endpoint is au=
thoritative for other origins without an explicit signal.</pre><pre class=
=3D"m_106484133921675978gmail-newpage" style=3D"font-size:13.3333px;margin-=
top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre><pr=
e class=3D"m_106484133921675978gmail-newpage" style=3D"margin-top:0px;margi=
n-bottom:0px;break-before:page"><font color=3D"#000000"><span style=3D"font=
-size:13.3333px">The explicit signal bit (is it referring to an origin fram=
e?) reads more restrictive than connection coalescing for HTTP/2. Does that=
 mean that clients wouldn&#39;t
be coalescing connections based on what the certificate is authoritative fo=
r and the DNS resolution results?<br></span></font></pre><pre class=3D"m_10=
6484133921675978gmail-newpage" style=3D"margin-top:0px;margin-bottom:0px;br=
eak-before:page"><font color=3D"#000000"><span style=3D"font-size:13.3333px=
"><br></span></font></pre><pre class=3D"m_106484133921675978gmail-newpage" =
style=3D"margin-top:0px;margin-bottom:0px;break-before:page"><font color=3D=
"#000000"><span style=3D"font-size:13.3333px">Thanks,</span></font></pre><p=
re class=3D"m_106484133921675978gmail-newpage" style=3D"margin-top:0px;marg=
in-bottom:0px;break-before:page"><font color=3D"#000000"><span style=3D"fon=
t-size:13.3333px">Frederik</span></font></pre></div></div></div></blockquot=
e></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">This PR might b=
e the best explanation=C2=A0<a href=3D"https://github.com/quicwg/base-draft=
s/issues/940">https://github.com/quicwg/base-drafts/issues/940</a></div><di=
v dir=3D"auto"><br></div><div dir=3D"auto">Another side effect of not havin=
g an HTTP/QUIC native URI.</div><div dir=3D"auto"><br></div><div dir=3D"aut=
o"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"lt=
r"><div dir=3D"ltr"><div dir=3D"ltr" class=3D"m_106484133921675978gmail_sig=
nature"><div dir=3D"ltr"><div style=3D"margin:0px;padding:0px;color:rgb(23,=
43,77);font-family:-apple-system,BlinkMacSystemFont,&quot;Segoe UI&quot;,Ro=
boto,Oxygen,Ubuntu,&quot;Fira Sans&quot;,&quot;Droid Sans&quot;,&quot;Helve=
tica Neue&quot;,sans-serif;font-size:14px"><div style=3D"margin:0px;padding=
:0px"></div></div></div></div></div></div>
</blockquote></div></div></div>

--0000000000000a6b6705798e4f31--


From nobody Wed Oct 31 20:32:29 2018
Return-Path: <mbishop@evequefou.be>
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 14115130DF5 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 20:32:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 TfHUFZ0ChTMH for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 20:32:25 -0700 (PDT)
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-eopbgr690104.outbound.protection.outlook.com [40.107.69.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16ED2130DE8 for <quic@ietf.org>; Wed, 31 Oct 2018 20:32:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kzI8pMY7iuvZRYlsmYixpqZcIca9ccwVRd8EFiICkHo=; b=Ni+9jitMcbb0upFFEMi5+9Gm15KSbOb+idRzv/xpvH6ZQrCkHJ7k+SrTQkzDV1o2cevnLT6LxM9Ucy3gzppe6Vznf492LNVCfRquhwqr/0x40npPi9P9TBfhEgGRlW/GNqW7LmP3uh7UvvDffOJ/LJ+mwF7ouniY3jlaQwA5fj8=
Received: from CY4PR22MB0983.namprd22.prod.outlook.com (10.171.171.20) by CY4PR22MB0231.namprd22.prod.outlook.com (10.169.187.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1273.26; Thu, 1 Nov 2018 03:32:21 +0000
Received: from CY4PR22MB0983.namprd22.prod.outlook.com ([fe80::706e:6d82:cc25:531f]) by CY4PR22MB0983.namprd22.prod.outlook.com ([fe80::706e:6d82:cc25:531f%10]) with mapi id 15.20.1294.021; Thu, 1 Nov 2018 03:32:21 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: "Roy T. Fielding" <fielding@gbiv.com>, Mark Nottingham <mnot@mnot.net>
CC: IETF QUIC WG <quic@ietf.org>
Subject: RE: Identifying our deliverables
Thread-Topic: Identifying our deliverables
Thread-Index: AQHUblWNqkWku1UrEkCUwcHTex6xJqU4LiOAgAIaLeA=
Date: Thu, 1 Nov 2018 03:32:21 +0000
Message-ID: <CY4PR22MB0983CAC48213F5F748D8920ADACE0@CY4PR22MB0983.namprd22.prod.outlook.com>
References: <578BB4EC-421E-4B21-AA14-B545A41754C8@mnot.net> <873C0B44-EE49-4CCF-97A2-E71DB43298E2@gbiv.com>
In-Reply-To: <873C0B44-EE49-4CCF-97A2-E71DB43298E2@gbiv.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [24.197.53.86]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR22MB0231; 6:XWplbuQNwJdezg5+qQyI54azB5dBdzzI4ip1hl6gw3YAG7ZH3Aw3Vha0uHHFqHk5Z5gdYQPkXMo0D/r7IwKJvFO5V4ndmp14UxtfxcoYw57TOKucHAYb0viwMTCzUSi9DzJkyPYprGZ2vx/elWT76ld6tYFumqfmV1Z4Ha5XZcsLF9q23IM/omnq8LXkGM1i8iKMcxsCHn8dqt4feB9HWACowseOtUwSVvzShtC2KBKcBM0bGeGrEX5W0N7QVjnpKwFL1FKeTvh6S5oi08BvZOajsjoMoMsFRS8IvhdmlswkCKXib5JFlDVkLY0SYRxe1Vzfi6FJy5LNgj/YFQVpFGqseq0eiQn0t7NidvxmMhTOGAuMsi9WD8bNx61KhcB1s6XT8ldCeN4RrIzIP5v17bPUJiUtYLPHJPif7rpw1osPpa2qzvYpZIaHSABaEvyscvjknNUGBl8ZKnfwYInjYg==; 5:5pvRu5j7+FoUSiED+V3+xdTTWPnbZmKNuLLdWZHzsHC0vUAqfM0Ww1RKVfEl0pe5iJrPVNEXWa78IRCmh/rA7aF/dzYP/4815Tslz8EggEHZdZJNeFHttHfXN43aNa7bWXPIZqHpUqMHJuvDrE2mNFLJW8E91IGwZWpcKAR3qqo=; 7:YmYhLANewzOVHi6BChbnXgm/8+eoPWX4jfSH8RJbOPxWXcCgFRvcnZW2ncz7uUGnvq7YFosqI3bTkdw7Lb6Zy645wbRJrhOJpiUeplArcvl2SavnYApfKQillWRs6917SkbBO0Vge95MKok4I3wsgw==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 3a556636-6af8-42ed-42a4-08d63faaa23d
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:CY4PR22MB0231; 
x-ms-traffictypediagnostic: CY4PR22MB0231:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-microsoft-antispam-prvs: <CY4PR22MB02313FBDD014431B5864E4F5DACE0@CY4PR22MB0231.namprd22.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(100405760836317)(60795455431006);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(3231382)(944501410)(4982022)(52105095)(148016)(149066)(150057)(6041310)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(2016111802025)(6043046)(201708071742011)(7699051)(76991095); SRVR:CY4PR22MB0231; BCL:0; PCL:0; RULEID:; SRVR:CY4PR22MB0231; 
x-forefront-prvs: 0843C17679
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(376002)(366004)(396003)(136003)(39830400003)(13464003)(199004)(189003)(66066001)(7116003)(446003)(5660300001)(14454004)(74316002)(6506007)(53546011)(102836004)(305945005)(7736002)(53936002)(4326008)(110136005)(256004)(14444005)(8676002)(26005)(6116002)(55016002)(3846002)(106356001)(186003)(229853002)(6436002)(105586002)(9686003)(86362001)(97736004)(25786009)(76176011)(74482002)(3480700004)(561944003)(8936002)(71190400001)(71200400001)(5250100002)(2906002)(81166006)(2900100001)(81156014)(6246003)(68736007)(486006)(99286004)(508600001)(11346002)(33656002)(7696005)(316002)(476003); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR22MB0231; H:CY4PR22MB0983.namprd22.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: tpSlb1IyT8a+0fFcN8aVZXc/Ej47vMdF76oMpVjhJg2ClwyS2PB03bzMDvX2J116cINHJuxt9ROJGFCfPWuY+5vWZLymac15y9hFUMXZc8ZKck19N7gQbA78f+8q006TitFs7TLIhj/LcRfUUS9wOWWqsqvo1JBqcPb7qeFDtDQuoQEFyroFKr2OS0FnIRB4RFCe+cnBjmeG1cg/TO4OXL81gqYXVs/lV7oB1PSBr0EcaaZIc/jInVPYeFejZLQ4a3uRTIXhdOwkD/HETfHNt+UQVkPHbqtGcbCqsi+9e798XcUFX2wAD/v7MdkV/TCSXLAUIt01ww1mqTiA2VLi+ZXgnEvzEAya6jhC2rNgNS4=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 3a556636-6af8-42ed-42a4-08d63faaa23d
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Nov 2018 03:32:21.6616 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR22MB0231
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/99b0mKWJcrdZrFEnTEfKZf891z0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Nov 2018 03:32:28 -0000

In theory, all Standards-track RFCs reflect IETF consensus, not just the co=
nsensus of a single working group, so I don't see HTTP as having "naming ri=
ghts" per se.  But in general, I think the QUIC WG should have the consensu=
s of the HTTP WG to call its output "HTTP/3."  And Mark's proposal reflects=
 exactly that, with a heads-up to the HTTP list that we'll be discussing in=
 Bangkok.  Along similar lines, I think we'd want to send the HTTP doc to b=
oth working groups for WGLC, either in parallel or in sequence.  If both WG=
s have consensus on the documents, I don't see this as a barrier.

Those process and ownership requirements satisfied, I think this naming is =
entirely appropriate.  In Montreal, the HTTP WG made an explicit decision n=
ot to backport things from HTTP/QUIC to HTTP/2 because HTTP/QUIC is "the fu=
ture," and I think the HTTP/3 name reflects that intent.  Not to say the in=
tent couldn't change as future circumstances do, but it accurately reflects=
 what we plan at this point.

-----Original Message-----
From: QUIC <quic-bounces@ietf.org> On Behalf Of Roy T. Fielding
Sent: Tuesday, October 30, 2018 2:19 PM
To: Mark Nottingham <mnot@mnot.net>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Identifying our deliverables

> On Oct 27, 2018, at 5:30 PM, Mark Nottingham <mnot@mnot.net> wrote:
>=20
> You might recall that we've previously talked about renaming our delivera=
bles to clarify their relationship to the input documents (sometimes referr=
ed to as "gQUIC vs iQUIC").
>=20
> After a fair amount of discussion with various folks, it seems like there=
's confidence that calling our core deliverable just "QUIC" will work, sinc=
e Google's variant will fade out of use if we succeed, and there aren't any=
 good alternatives; our best candidate was "QUIC/2", but it was pointed out=
 that this additional level of versioning (since we already have a wire ver=
sion) will cause yet more confusion.
>=20
> However, in those discussions, a related concern was identified; confusio=
n between QUIC-the-transport-protocol, and QUIC-the-HTTP-binding. I and oth=
ers have seen a number of folks not closely involved in this work conflatin=
g the two, even though they're now separate things.
>=20
> To address this, I'd like to suggest that -- after coordination with the =
HTTP WG -- we rename our the HTTP document to "HTTP/3", and using the final=
 ALPN token "h3". Doing so clearly identifies it as another binding of HTTP=
 semantics to the wire protocol -- just as HTTP/2 did -- so people understa=
nd its separation from QUIC.
>=20
> As part of that discussion, I'd suggest that we formalise that its mainte=
nance (as well as that of QPACK) pass off to the HTTP WG once we've publish=
ed it.
>=20
> I've talked about this with a number of folks. The only concerns I've hea=
rd so far are:
>=20
> a) That QUIC isn't yet proven. That's true, but the name won't be formali=
sed or used on the wire until the RFC is published, so we have a good amoun=
t of time to back away. Even then, if it fails in the market, we can always=
 skip to HTTP/4 one day, if we need to.=20
>=20
> b) That discussing naming is a distraction from our technical work. I agr=
ee with the concern overall, but we have a responsibility to communicate cl=
early with external developers and users, so I'd like to have a *limited* d=
iscussion about this. Please, don't bike shed.
>=20
> *Chair hat*
>=20
> We plan on reserving a very small period of time to discuss this in Bangk=
ok; barring serious objections (of which "what about this name that I like =
instead?" is not one), we'll bring it up with the HTTP WG in Bangkok as wel=
l.

FWIW, I don't have a problem with calling a product of the HTTP WG some for=
m of h3, with the implication that we are working on the next version of HT=
TP and that it will work on top of QUIC.  I have a bit of a problem with as=
suming that h3 product will be the current HTTP-over-QUIC binding, QPACK, e=
tc.  It's a reasonable option to work upon.

.....Roy


From nobody Wed Oct 31 20:47:49 2018
Return-Path: <mbishop@evequefou.be>
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 E8812130DF5 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 20:47:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 O6vNKQbMmICO for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 20:47:44 -0700 (PDT)
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-eopbgr820090.outbound.protection.outlook.com [40.107.82.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D36B0130DFE for <quic@ietf.org>; Wed, 31 Oct 2018 20:47:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=AoYquD8b2WHMK180BCyAk6qm7R/7aRDnEDAg7DHHUDU=; b=lupv/Pd0GW06K1wQMW7JdxwwqDeFMkT6UE4k24PPTaDha/frCr1d0nidlB40UrYRCeUzDoONzvq1Z2rXUb6NAgheRBTk/tFrMsraeOtR85lIUN65gw3qUoKlrJE3TINdOeHCQ2DhboAqxJa/+DxKXFsZ9MG5N955QGiqf/VyW78=
Received: from CY4PR22MB0983.namprd22.prod.outlook.com (10.171.171.20) by CY4PR22MB0150.namprd22.prod.outlook.com (10.169.181.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1294.23; Thu, 1 Nov 2018 03:47:41 +0000
Received: from CY4PR22MB0983.namprd22.prod.outlook.com ([fe80::706e:6d82:cc25:531f]) by CY4PR22MB0983.namprd22.prod.outlook.com ([fe80::706e:6d82:cc25:531f%10]) with mapi id 15.20.1294.021; Thu, 1 Nov 2018 03:47:41 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Marcus Ihlar <marcus.ihlar@ericsson.com>, Kazuho Oku <kazuhooku@gmail.com>, Christian Huitema <huitema@huitema.net>
CC: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>
Subject: RE: Structuring the BKK spin bit discussion
Thread-Topic: Structuring the BKK spin bit discussion
Thread-Index: AQHUb5vbdkM8BiwhukKPBrI6M20NOaU2Y+yAgAAMqQCAArb/gIAAJugAgAD9FpA=
Date: Thu, 1 Nov 2018 03:47:40 +0000
Message-ID: <CY4PR22MB0983A1FF62451F45923220B4DACE0@CY4PR22MB0983.namprd22.prod.outlook.com>
References: <18A2F994-0E82-48E4-875D-93C674483D49@eggert.org> <20181029160802.GD7258@ubuntu-dmitri> <8268B90E-F109-424C-91A8-DB7BFE208F53@huitema.net>, <CANatvzxt-QBmeJUwp+MjtbpYXstPiEigDzQe0KfWJN+q0XR4Kg@mail.gmail.com> <HE1PR0701MB23938B01BC31888DAC3629B8E2CD0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR0701MB23938B01BC31888DAC3629B8E2CD0@HE1PR0701MB2393.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [24.197.53.86]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR22MB0150; 6:2nu5bHd4LZq8M6Z1WrP1ExVC8tl1XN8IDQ9XgPLYK9OzNEp5oJy9U4nWyKq4gy8k3UulACmTnCLOOZG2EMFFwG3NGDOmW/jkYur7QG3NjcD8FBAlhCVuLmCRRtvj5Xy94dH7M4ZwnnXaLr3sdKQwPXvC4MEhlDXLNNLnCNN1y+QwtRfZ00jTq/3JmVfrp+sQjEueeC6Gewv3t49STykjyTn2rP57O5kXWSBfkDzPgGpDKmTqTykaVQfJ4inu6d3AGB9H1nVkT9Xyy3Mli2a3b4+1rlfJVQ7xNoJ0kTAZKaRqEnFiXfe0IK3RefoUrNtBSh935Fq4aK02cAbnjAJjMUXyWKvfW2BYvF4C+Ua4eegdSvsEo2Y0DIyBmJf6KXgE39v23lZi6BTgclgP9KCZoJ4vE9h1gXR3YRLc8y5JJ1BxMFtvmJtnCji1HEA14YZAlVXY0y9vuYjrSriK8SsRwg==; 5:sFbNxFUzUm9RN4dd5dXidGwWXfcVJQmOL5IVpj26jPB9cBDlMXqPLiTDmM8hZaNPFjWYMpEi/EIfzB/LelHfP8jf63W/U7KU1TYoahomyOGAnUE1QzNFOxZKlbR57y1/Rx6DuVMhd9bzy2fDVJ3C+r99f3YIyI8tNGLiwld3EbU=; 7:feUv8Y/aENUJn9M4NWUjlIYtjS3AzpQ3YTxne4rRchfBeAAtCDgAGK1zRXb6PIyOX2erUtVQ/hTLscY/2ILDV3pMwmm+x61622HAew0vjizPbkMKY+DQ1P2uQECbAsJxkzxGhB9UiesPT+a3GduFZA==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: ccf2296c-298d-4022-9113-08d63facc62a
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(7021145)(8989299)(5600074)(711020)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(2017052603328)(7153060)(7193020); SRVR:CY4PR22MB0150; 
x-ms-traffictypediagnostic: CY4PR22MB0150:
x-microsoft-antispam-prvs: <CY4PR22MB0150F64F5F0C1037BA7360B3DACE0@CY4PR22MB0150.namprd22.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(85827821059158)(158342451672863)(21748063052155)(28532068793085)(190501279198761)(227612066756510);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(3231382)(944501410)(52105095)(148016)(149066)(150057)(6041310)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(2016111802025)(6043046)(201708071742011)(7699051)(76991095); SRVR:CY4PR22MB0150; BCL:0; PCL:0; RULEID:; SRVR:CY4PR22MB0150; 
x-forefront-prvs: 0843C17679
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39830400003)(136003)(346002)(376002)(396003)(366004)(199004)(189003)(486006)(186003)(476003)(74316002)(446003)(11346002)(66066001)(7736002)(81166006)(256004)(8936002)(5250100002)(97736004)(8676002)(229853002)(93886005)(81156014)(26005)(2900100001)(508600001)(102836004)(54906003)(71200400001)(71190400001)(106356001)(6246003)(86362001)(74482002)(76176011)(7696005)(53546011)(110136005)(6506007)(68736007)(316002)(6306002)(33656002)(54896002)(236005)(9686003)(3846002)(6436002)(6116002)(790700001)(99286004)(55016002)(14454004)(25786009)(4326008)(53936002)(2906002)(5660300001)(39060400002)(105586002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR22MB0150; H:CY4PR22MB0983.namprd22.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: PD8IH4T8GSZnwm+hWaUZRDH6l/ZWhWFPwoTzBKI/fAN7CN/sKQCF2406cnMXZQ42yylHkF4ISkqeKCDRmLvESnQnQ8qRaZRzMFcYkHoOXR/7V3JFGAIy/6cXpLc35MobyqM5nQL6q+3FAU1UBbTUA6KwEeX4scp9cy6nuR9gu612tIIRtSm7wTVsrMELHWGzBqHQZcqfGblcnfOwOMiK4NKvQOMiRUUoynvMYTvp6+J/zpAP8PXo6e3HzwlQmHwxwXtcVfejXPPCOy9zKDcH0a2TWkbwIHWkvxi53W/iCWghZcr1GuZOAQnrKsiUFldRTblNwyS7PtXvLW4JEZofCKnZD74QDKb/QgiXpDY1PWI=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CY4PR22MB0983A1FF62451F45923220B4DACE0CY4PR22MB0983namp_"
MIME-Version: 1.0
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: ccf2296c-298d-4022-9113-08d63facc62a
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Nov 2018 03:47:40.9295 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR22MB0150
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/tCc0Hvop0xO1SSALQtz8RggEOLY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Nov 2018 03:47:48 -0000

--_000_CY4PR22MB0983A1FF62451F45923220B4DACE0CY4PR22MB0983namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

QnV0IGRhdGEgY29ubmVjdGlvbnMgd2hlbiByb2FtaW5nIHJ1biBiYWNrIHRvIHRoZSBob21lIG9w
ZXJhdG9yLCBJSVVDLCBzbyB0aGUgc2l6ZSBvZiBKYXBhbiBkb2VzbuKAmXQgbWl0aWdhdGUgdGhp
cyBjb25jZXJuLiAgVGhhdCBtZWFucyBhIHJvYW1pbmcgdXNlcuKAmXMgZGlzdGFuY2UgZnJvbSBU
b2t5byBzdGlsbCBnZXRzIGRpc2Nsb3NlZCwgYW5kIGl04oCZcyBtb3JlIHRoYW4gbWVhc3VyZW1l
bnQgZXJyb3IgaWYgdGhhdCB1c2VyIGlzIHJvYW1pbmcgb24gYSBkaWZmZXJlbnQgY29udGluZW50
Lg0KDQpGcm9tOiBRVUlDIDxxdWljLWJvdW5jZXNAaWV0Zi5vcmc+IE9uIEJlaGFsZiBPZiBNYXJj
dXMgSWhsYXINClNlbnQ6IFdlZG5lc2RheSwgT2N0b2JlciAzMSwgMjAxOCA3OjQwIEFNDQpUbzog
S2F6dWhvIE9rdSA8a2F6dWhvb2t1QGdtYWlsLmNvbT47IENocmlzdGlhbiBIdWl0ZW1hIDxodWl0
ZW1hQGh1aXRlbWEubmV0Pg0KQ2M6IExhcnMgRWdnZXJ0IDxsYXJzQGVnZ2VydC5vcmc+OyBJRVRG
IFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc+OyBEbWl0cmkgVGlraG9ub3YgPGR0aWtob25vdkBsaXRl
c3BlZWR0ZWNoLmNvbT4NClN1YmplY3Q6IFNWOiBTdHJ1Y3R1cmluZyB0aGUgQktLIHNwaW4gYml0
IGRpc2N1c3Npb24NCg0KDQpIaSBLYXp1aG8sDQoNCkkgYmVsaWV2ZSB0aGUgYmlnZ2VzdCBkaWZm
ZXJlbmNlIGlzIHRoZSBzaXplIG9mIHRoZSBoaWRkZW4gbmV0d29yayBzZWdtZW50Lg0KDQpJbiB0
aGUgTkFUIGNhc2UgdGhlIGNsaWVudCBhbmQgTkFUIGFyZSBzdGlsbCBpbiB0aGUgc2FtZSBjb3Vu
dHJ5IG9yIGNvbnRpbmVudC4NCg0KQSBxdWljayBnbGFjbmUgYXQgZGlzdGFuY2VjYWxjdWxhdG9y
Lm5ldCBzaG93cyB0aGF0IHRoZSBjaXR5IGZhcnRoZXN0IGZyb20gVG9reW8gaW4gSmFwYW4gaXMg
TmFoYS1TaGksIGF0IDE1NTQga20uDQoNClRoYXQgdHJhbnNsYXRlcyB0byByb3VnaGx5IDVtcyBh
dCB0aGUgc3BlZWQgb2YgbGlnaHQsIHNvIHRoZSBraW5kcyBvZiBtZWFzdXJlbWVudHMgdG8gZGV0
ZXJtaW5lIGRpc3RhbmNlIGZyb20gVG9reW8gYmFzZWQgb24gUlRUIHdpbGwgYmUgZXh0cmVtZWx5
IHNlbnNpdGl2ZSBhbmQgZXJyb3IgcHJvbmUuDQoNClBsZWFzZSBub3RlIHRoYXQgdGhlIGRpc3Rh
bmNlIGFuYWx5aXMgY2FuIGJlIHBlcmZvcm1lZCBvbiBoYW5kc2hha2UgUlRUIGFzIHdlbGwsIGZv
ciBjb25uZWN0aW9ucyB3aGVyZSB0aGUgaW5pdGlhbCBoYW5kc2hha2UgaXMgdmlzaWJsZSBhdCB0
aGUgbWVhc3VyZW1lbnQgcG9pbnQuDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQpGcsOlbjogUVVJQyA8cXVpYy1ib3VuY2VzQGlldGYub3JnPG1haWx0bzpxdWljLWJvdW5jZXNA
aWV0Zi5vcmc+PiBmw7ZyIEthenVobyBPa3UgPGthenVob29rdUBnbWFpbC5jb208bWFpbHRvOmth
enVob29rdUBnbWFpbC5jb20+Pg0KU2tpY2thdDogZGVuIDMxIG9rdG9iZXIgMjAxOCAxMToyMA0K
VGlsbDogQ2hyaXN0aWFuIEh1aXRlbWENCktvcGlhOiBMYXJzIEVnZ2VydDsgSUVURiBRVUlDIFdH
OyBEbWl0cmkgVGlraG9ub3YNCsOEbW5lOiBSZTogU3RydWN0dXJpbmcgdGhlIEJLSyBzcGluIGJp
dCBkaXNjdXNzaW9uDQoNCjIwMTjlubQxMOaciDMw5pelKOeBqykgMTo1NCBDaHJpc3RpYW4gSHVp
dGVtYSA8aHVpdGVtYUBodWl0ZW1hLm5ldDxtYWlsdG86aHVpdGVtYUBodWl0ZW1hLm5ldD4+Og0K
Pg0KPg0KPg0KPiA+IE9uIE9jdCAyOSwgMjAxOCwgYXQgOTowOCBBTSwgRG1pdHJpIFRpa2hvbm92
IDxkdGlraG9ub3ZAbGl0ZXNwZWVkdGVjaC5jb208bWFpbHRvOmR0aWtob25vdkBsaXRlc3BlZWR0
ZWNoLmNvbT4+IHdyb3RlOg0KPiA+DQo+ID4+IE9uIE1vbiwgT2N0IDI5LCAyMDE4IGF0IDA1OjI2
OjM0UE0gKzAyMDAsIExhcnMgRWdnZXJ0IHdyb3RlOg0KPiA+PiBXZSdkIHNwZWNpZmljYWxseSBs
aWtlIHRvIGFzayBjbGllbnQgYW5kIHNlcnZlciBpbXBsZW1lbnRvcnMgd2l0aA0KPiA+PiBwcm9q
ZWN0ZWQgc2l6YWJsZSBkZXBsb3ltZW50cyB0byBpbmRpY2F0ZSB3aGV0aGVyIHRoZXkgaW50ZW50
IHRvDQo+ID4+IGltcGxlbWVudCBhbmQgZGVwbG95LCBpZiB0aGUgV0cgZGVjaWRlZCB0byBpbmNs
dWRlIHRoZSBzcGluLWJpdCBpbg0KPiA+PiB0aGUgc3BlYy4NCj4gPg0KPiA+IExpdGVTcGVlZCBU
ZWNobm9sb2dpZXMgd2lsbCBzdXBwb3J0IHRoZSBzcGluIGJpdCAtLSBib3RoIGluIG91cg0KPiA+
IHNlcnZlciBhbmQgY2xpZW50IFFVSUMgaW1wbGVtZW50YXRpb25zIC0tIGlmIGl0IG1ha2UgaXQg
aW50byB0aGUNCj4gPiBkcmFmdC4NCj4NCj4gTXkgaW1wbGVtZW50YXRpb24gaXMgbm90IHVzZWQg
aW4gYW55IGxhcmdlIHNjYWxlIGRlcGxveW1lbnQsIGJ1dCBpdCBkb2VzIHN1cHBvcnQgdGhlIHNw
aW4gYml0LiBJbiBmYWN0LCBpdCBoYXMgY29uZmlndXJhdGlvbiBvcHRpb25zIHRvIHN1cHBvcnQg
c3BpbiBiaXQgdmFyaWFudHM6IG5vZGUsIGp1c3Qgc3Bpbiwgc3BpbiArIHZlYywgc3BpbiArIFFS
Lg0KPg0KPiBJIHRoaW5rIHRoZSBzdHJvbmdlc3Qgb2JqZWN0aW9uIHRvIHRoZSBzcGluIGJpdCB3
YXMgcHV0IHVwIGJ5IE1hcnRlbiBkdXJpbmcgdGhlIGxhc3QgaW50ZXJpbTogbWVhc3VyaW5nIHRo
ZSBSVFQgd2l0aCB0aGUgc3BpbiBiaXQgZGlzY2xvc2VzIHRoZSB1c2Ugb2YgaGlkZGVuIHBhdGgg
c2VnbWVudHMgbGlrZSBWUE4uIFRoaXMgaXNzdWUgd2FzIG5vdCBkaXNjdXNzZWQgZHVyaW5nIHRo
ZSBwcml2YWN5IGFuYWx5c2lzLg0KDQpNYXkgSSBhc2sgaWYgdGhlIFZQTiB1c2VycyBhcmUgdGhl
IG9ubHkgb25lcyB0aGF0IGxvc2Ugc29tZSBwcml2YWN5DQp3aXRoIHNwaW4gYml0cz8NCg0KSSBh
c2sgdGhpcyBiZWNhdXNlIEkgbGl2ZSBpbiBhIGNvdW50cnkgd2hlcmUgSUlVQyB0aGUgbW9iaWxl
IGNhcnJpZXJzDQpwbGFjZSB0aGVpciBuYXRpb24td2lkZSBjYXJyaWVyLWdyYWRlIE5BVCBuZWFy
IHRoZSBjYXBpdGFsIGNpdHkgKGkuZS4sDQpUb2t5bykuIFRoYXQgbWVhbnMgdGhhdCBmb3IgcGVv
cGxlIGxpdmluZyBpbiB0aGUgY291bnRyeSwgaGF2aW5nIHNwaW4NCmJpdHMgdHVybmVkIG9uIGNv
dWxkIHJldmVhbCB0aGVpciBkaXN0YW5jZSBmcm9tIFRva3lvLg0KDQpTbyB0aGUgcXVlc3Rpb24g
aXM6IGlmIFZQTiB1c2VycyBuZWVkIHNwZWNpYWwgY2FyZSwgZG8gc29tZSBOQVQgdXNlcnMNCmFz
IHdlbGw/IE9yIGlmIHRoZSBhbnN3ZXIgaXMgbm8sIHdoYXQgaXMgdGhlIGRpZmZlcmVuY2UgZnJv
bSBiZXR3ZWVuDQp0aGUgdHdvIGdyb3Vwcz8NCg0KR2VuZXJhbGx5IHNwZWFraW5nLCBJIGFtIG5v
dCBhZ2FpbnN0IGdpdmluZyB1c2VycyB0aGUgZnJlZWRvbSB0bw0KZXhwb3NlIHNwaW4gYml0cywg
aG93ZXZlciBJIGFtIHdvbmRlcmluZyBob3cgdGhlIGVuZHBvaW50cyBzaG91bGQNCnByb3ZpZGUg
dGhlIGZyZWVkb20gb2YgY2hvaWNlIChVSSBxdWVzdGlvbikgYXMgd2VsbCBhcyB3aGF0IHRoZQ0K
ZGVmYXVsdCBzaG91bGQgYmUuDQoNCj4NCj4gVGhlIHByaXZhY3kgaXNzdWUgY291bGQgYmUgbWl0
aWdhdGVkIGJ5IHR1cm5pbmcgb2ZmIHRoZSBzcGluIGJpdCBhdCBwcml2YWN5IHNlbnNpdGl2ZSBj
bGllbnRzLCBidXQgdGhpcyB3b3VsZCBtYWtlIHRoZXNlIGNsaWVudHMgInN0aWNrIG91dCIuDQo+
DQo+IE9uZSBzb2x1dGlvbiB3b3VsZCBiZSB0byByZW1vdmUgdGhlIHNwaW4gYml0IGZyb20gdGhl
IHNwZWMsIHRyYWRpbmcgb2ZmIGJldHRlciBwcml2YWN5IGZvciB3b3JzZSBtYW5hZ2VtZW50LiBJ
IGFtIGNvbnNpZGVyaW5nIGFub3RoZXIgc29sdXRpb24gaW4gd2hpY2ggcHJpdmFjeSBzZW5zaXRp
dmUgY2xpZW50cyBoaWRlIHRoZSBSVFQgYnkgY29udHJvbGxpbmcgdGhlIHNwaW4sIGZvciBleGFt
cGxlIHNwaW5uaW5nIGF0IGZpeGVkIGludGVydmFscy4gSSBwbGFuIHRlc3RpbmcgdGhhdCBvcHRp
b24gaW4gUGljb3F1aWMuDQo+DQo+IC0tIENocmlzdGlhbiBIdWl0ZW1hDQo+DQo+DQoNCg0KLS0N
CkthenVobyBPa3UNCg==

--_000_CY4PR22MB0983A1FF62451F45923220B4DACE0CY4PR22MB0983namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OiJNUyBHb3RoaWMiOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDcgMiA1IDgg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3Nl
LTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGli
cmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250
LWZhbWlseToiXEBNUyBHb3RoaWMiOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDcgMiA1IDggMiA0O30N
Ci8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYu
TXNvTm9ybWFsDQoJe21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQt
c2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5r
LCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6IzA1
NjNDMTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Izk1NEY3
MjsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAubXNvbm9ybWFsMCwgbGkubXNvbm9y
bWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6bXNvbm9ybWFsOw0KCW1hcmdp
bjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9u
dC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjANCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMt
c2VyaWY7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJ
Zm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4w
aW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjEN
Cgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHht
bD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3ht
bD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6
ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBl
bGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxp
bms9IiMwNTYzQzEiIHZsaW5rPSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5CdXQgZGF0YSBjb25uZWN0aW9ucyB3aGVuIHJvYW1pbmcg
cnVuIGJhY2sgdG8gdGhlIGhvbWUgb3BlcmF0b3IsIElJVUMsIHNvIHRoZSBzaXplIG9mIEphcGFu
IGRvZXNu4oCZdCBtaXRpZ2F0ZSB0aGlzIGNvbmNlcm4uJm5ic3A7IFRoYXQgbWVhbnMgYSByb2Ft
aW5nIHVzZXLigJlzIGRpc3RhbmNlIGZyb20gVG9reW8gc3RpbGwgZ2V0cyBkaXNjbG9zZWQsIGFu
ZCBpdOKAmXMgbW9yZSB0aGFuIG1lYXN1cmVtZW50IGVycm9yIGlmIHRoYXQNCiB1c2VyIGlzIHJv
YW1pbmcgb24gYSBkaWZmZXJlbnQgY29udGluZW50LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9y
ZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGlu
IDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8L2I+IFFVSUMgJmx0O3F1
aWMtYm91bmNlc0BpZXRmLm9yZyZndDsgPGI+T24gQmVoYWxmIE9mIDwvYj4NCk1hcmN1cyBJaGxh
cjxicj4NCjxiPlNlbnQ6PC9iPiBXZWRuZXNkYXksIE9jdG9iZXIgMzEsIDIwMTggNzo0MCBBTTxi
cj4NCjxiPlRvOjwvYj4gS2F6dWhvIE9rdSAmbHQ7a2F6dWhvb2t1QGdtYWlsLmNvbSZndDs7IENo
cmlzdGlhbiBIdWl0ZW1hICZsdDtodWl0ZW1hQGh1aXRlbWEubmV0Jmd0Ozxicj4NCjxiPkNjOjwv
Yj4gTGFycyBFZ2dlcnQgJmx0O2xhcnNAZWdnZXJ0Lm9yZyZndDs7IElFVEYgUVVJQyBXRyAmbHQ7
cXVpY0BpZXRmLm9yZyZndDs7IERtaXRyaSBUaWtob25vdiAmbHQ7ZHRpa2hvbm92QGxpdGVzcGVl
ZHRlY2guY29tJmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBTVjogU3RydWN0dXJpbmcgdGhlIEJL
SyBzcGluIGJpdCBkaXNjdXNzaW9uPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2IGlkPSJkaXZ0YWdk
ZWZhdWx0d3JhcHBlciI+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xvcjpi
bGFjayI+SGkgS2F6dWhvLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTIuMHB0O2NvbG9yOmJsYWNrIj5JIGJlbGlldmUgdGhlIGJpZ2dlc3QgZGlmZmVy
ZW5jZSBpcyB0aGUgc2l6ZSBvZiB0aGUgaGlkZGVuIG5ldHdvcmsgc2VnbWVudC4NCjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2NvbG9yOmJs
YWNrIj5JbiB0aGUgTkFUIGNhc2UgdGhlIGNsaWVudCBhbmQgTkFUIGFyZSBzdGlsbCBpbiB0aGUg
c2FtZSBjb3VudHJ5IG9yIGNvbnRpbmVudC4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2NvbG9yOmJsYWNrIj5BIHF1aWNrIGdsYWNuZSBh
dCBkaXN0YW5jZWNhbGN1bGF0b3IubmV0IHNob3dzIHRoYXQgdGhlIGNpdHkgZmFydGhlc3QgZnJv
bSBUb2t5byBpbiBKYXBhbiBpcyBOYWhhLVNoaSwgYXQgMTU1NCBrbS4NCjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2NvbG9yOmJsYWNrIj5U
aGF0IHRyYW5zbGF0ZXMgdG8gcm91Z2hseSA1bXMgYXQgdGhlIHNwZWVkIG9mIGxpZ2h0LCBzbyB0
aGUga2luZHMgb2YgbWVhc3VyZW1lbnRzIHRvIGRldGVybWluZSBkaXN0YW5jZSBmcm9tIFRva3lv
IGJhc2VkIG9uIFJUVCB3aWxsIGJlIGV4dHJlbWVseSBzZW5zaXRpdmUgYW5kIGVycm9yIHByb25l
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0
O2NvbG9yOmJsYWNrIj5QbGVhc2Ugbm90ZSB0aGF0IHRoZSBkaXN0YW5jZSBhbmFseWlzIGNhbiBi
ZSBwZXJmb3JtZWQgb24gaGFuZHNoYWtlIFJUVCBhcyB3ZWxsLCBmb3IgY29ubmVjdGlvbnMgd2hl
cmUgdGhlIGluaXRpYWwgaGFuZHNoYWtlIGlzIHZpc2libGUgYXQgdGhlIG1lYXN1cmVtZW50IHBv
aW50Lg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xv
cjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXYgY2xhc3M9
Ik1zb05vcm1hbCIgYWxpZ249ImNlbnRlciIgc3R5bGU9InRleHQtYWxpZ246Y2VudGVyIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xvcjpibGFjayI+DQo8aHIgc2l6ZT0iNCIgd2lk
dGg9Ijk4JSIgYWxpZ249ImNlbnRlciI+DQo8L3NwYW4+PC9kaXY+DQo8ZGl2IGlkPSJkaXZScGx5
RndkTXNnIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFj
ayI+RnLDpW46PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPiBRVUlDICZsdDs8
YSBocmVmPSJtYWlsdG86cXVpYy1ib3VuY2VzQGlldGYub3JnIj5xdWljLWJvdW5jZXNAaWV0Zi5v
cmc8L2E+Jmd0OyBmw7ZyIEthenVobyBPa3UgJmx0OzxhIGhyZWY9Im1haWx0bzprYXp1aG9va3VA
Z21haWwuY29tIj5rYXp1aG9va3VAZ21haWwuY29tPC9hPiZndDs8YnI+DQo8Yj5Ta2lja2F0Ojwv
Yj4gZGVuIDMxIG9rdG9iZXIgMjAxOCAxMToyMDxicj4NCjxiPlRpbGw6PC9iPiBDaHJpc3RpYW4g
SHVpdGVtYTxicj4NCjxiPktvcGlhOjwvYj4gTGFycyBFZ2dlcnQ7IElFVEYgUVVJQyBXRzsgRG1p
dHJpIFRpa2hvbm92PGJyPg0KPGI+w4RtbmU6PC9iPiBSZTogU3RydWN0dXJpbmcgdGhlIEJLSyBz
cGluIGJpdCBkaXNjdXNzaW9uPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2Nv
bG9yOmJsYWNrIj4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xvcjpibGFjayI+Jm5ic3A7
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBzdHls
ZT0iY29sb3I6YmxhY2siPjIwMTg8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90
O01TIEdvdGhpYyZxdW90Oztjb2xvcjpibGFjayI+5bm0PC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xv
cjpibGFjayI+MTA8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O01TIEdvdGhp
YyZxdW90Oztjb2xvcjpibGFjayI+5pyIPC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+
MzA8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O01TIEdvdGhpYyZxdW90Oztj
b2xvcjpibGFjayI+5pelPC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+KDwvc3Bhbj48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7TVMgR290aGljJnF1b3Q7O2NvbG9yOmJsYWNr
Ij7ngas8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj4pDQogMTo1NCBDaHJpc3RpYW4g
SHVpdGVtYSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmh1aXRlbWFAaHVpdGVtYS5uZXQiPmh1aXRlbWFA
aHVpdGVtYS5uZXQ8L2E+Jmd0Ozo8YnI+DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQom
Z3Q7ICZndDsgT24gT2N0IDI5LCAyMDE4LCBhdCA5OjA4IEFNLCBEbWl0cmkgVGlraG9ub3YgJmx0
OzxhIGhyZWY9Im1haWx0bzpkdGlraG9ub3ZAbGl0ZXNwZWVkdGVjaC5jb20iPmR0aWtob25vdkBs
aXRlc3BlZWR0ZWNoLmNvbTwvYT4mZ3Q7IHdyb3RlOjxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsg
Jmd0OyZndDsgT24gTW9uLCBPY3QgMjksIDIwMTggYXQgMDU6MjY6MzRQTSAmIzQzOzAyMDAsIExh
cnMgRWdnZXJ0IHdyb3RlOjxicj4NCiZndDsgJmd0OyZndDsgV2UnZCBzcGVjaWZpY2FsbHkgbGlr
ZSB0byBhc2sgY2xpZW50IGFuZCBzZXJ2ZXIgaW1wbGVtZW50b3JzIHdpdGg8YnI+DQomZ3Q7ICZn
dDsmZ3Q7IHByb2plY3RlZCBzaXphYmxlIGRlcGxveW1lbnRzIHRvIGluZGljYXRlIHdoZXRoZXIg
dGhleSBpbnRlbnQgdG88YnI+DQomZ3Q7ICZndDsmZ3Q7IGltcGxlbWVudCBhbmQgZGVwbG95LCBp
ZiB0aGUgV0cgZGVjaWRlZCB0byBpbmNsdWRlIHRoZSBzcGluLWJpdCBpbjxicj4NCiZndDsgJmd0
OyZndDsgdGhlIHNwZWMuPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IExpdGVTcGVlZCBU
ZWNobm9sb2dpZXMgd2lsbCBzdXBwb3J0IHRoZSBzcGluIGJpdCAtLSBib3RoIGluIG91cjxicj4N
CiZndDsgJmd0OyBzZXJ2ZXIgYW5kIGNsaWVudCBRVUlDIGltcGxlbWVudGF0aW9ucyAtLSBpZiBp
dCBtYWtlIGl0IGludG8gdGhlPGJyPg0KJmd0OyAmZ3Q7IGRyYWZ0Ljxicj4NCiZndDs8YnI+DQom
Z3Q7IE15IGltcGxlbWVudGF0aW9uIGlzIG5vdCB1c2VkIGluIGFueSBsYXJnZSBzY2FsZSBkZXBs
b3ltZW50LCBidXQgaXQgZG9lcyBzdXBwb3J0IHRoZSBzcGluIGJpdC4gSW4gZmFjdCwgaXQgaGFz
IGNvbmZpZ3VyYXRpb24gb3B0aW9ucyB0byBzdXBwb3J0IHNwaW4gYml0IHZhcmlhbnRzOiBub2Rl
LCBqdXN0IHNwaW4sIHNwaW4gJiM0MzsgdmVjLCBzcGluICYjNDM7IFFSLjxicj4NCiZndDs8YnI+
DQomZ3Q7IEkgdGhpbmsgdGhlIHN0cm9uZ2VzdCBvYmplY3Rpb24gdG8gdGhlIHNwaW4gYml0IHdh
cyBwdXQgdXAgYnkgTWFydGVuIGR1cmluZyB0aGUgbGFzdCBpbnRlcmltOiBtZWFzdXJpbmcgdGhl
IFJUVCB3aXRoIHRoZSBzcGluIGJpdCBkaXNjbG9zZXMgdGhlIHVzZSBvZiBoaWRkZW4gcGF0aCBz
ZWdtZW50cyBsaWtlIFZQTi4gVGhpcyBpc3N1ZSB3YXMgbm90IGRpc2N1c3NlZCBkdXJpbmcgdGhl
IHByaXZhY3kgYW5hbHlzaXMuPGJyPg0KPGJyPg0KTWF5IEkgYXNrIGlmIHRoZSBWUE4gdXNlcnMg
YXJlIHRoZSBvbmx5IG9uZXMgdGhhdCBsb3NlIHNvbWUgcHJpdmFjeTxicj4NCndpdGggc3BpbiBi
aXRzPzxicj4NCjxicj4NCkkgYXNrIHRoaXMgYmVjYXVzZSBJIGxpdmUgaW4gYSBjb3VudHJ5IHdo
ZXJlIElJVUMgdGhlIG1vYmlsZSBjYXJyaWVyczxicj4NCnBsYWNlIHRoZWlyIG5hdGlvbi13aWRl
IGNhcnJpZXItZ3JhZGUgTkFUIG5lYXIgdGhlIGNhcGl0YWwgY2l0eSAoaS5lLiw8YnI+DQpUb2t5
bykuIFRoYXQgbWVhbnMgdGhhdCBmb3IgcGVvcGxlIGxpdmluZyBpbiB0aGUgY291bnRyeSwgaGF2
aW5nIHNwaW48YnI+DQpiaXRzIHR1cm5lZCBvbiBjb3VsZCByZXZlYWwgdGhlaXIgZGlzdGFuY2Ug
ZnJvbSBUb2t5by48YnI+DQo8YnI+DQpTbyB0aGUgcXVlc3Rpb24gaXM6IGlmIFZQTiB1c2VycyBu
ZWVkIHNwZWNpYWwgY2FyZSwgZG8gc29tZSBOQVQgdXNlcnM8YnI+DQphcyB3ZWxsPyBPciBpZiB0
aGUgYW5zd2VyIGlzIG5vLCB3aGF0IGlzIHRoZSBkaWZmZXJlbmNlIGZyb20gYmV0d2Vlbjxicj4N
CnRoZSB0d28gZ3JvdXBzPzxicj4NCjxicj4NCkdlbmVyYWxseSBzcGVha2luZywgSSBhbSBub3Qg
YWdhaW5zdCBnaXZpbmcgdXNlcnMgdGhlIGZyZWVkb20gdG88YnI+DQpleHBvc2Ugc3BpbiBiaXRz
LCBob3dldmVyIEkgYW0gd29uZGVyaW5nIGhvdyB0aGUgZW5kcG9pbnRzIHNob3VsZDxicj4NCnBy
b3ZpZGUgdGhlIGZyZWVkb20gb2YgY2hvaWNlIChVSSBxdWVzdGlvbikgYXMgd2VsbCBhcyB3aGF0
IHRoZTxicj4NCmRlZmF1bHQgc2hvdWxkIGJlLjxicj4NCjxicj4NCiZndDs8YnI+DQomZ3Q7IFRo
ZSBwcml2YWN5IGlzc3VlIGNvdWxkIGJlIG1pdGlnYXRlZCBieSB0dXJuaW5nIG9mZiB0aGUgc3Bp
biBiaXQgYXQgcHJpdmFjeSBzZW5zaXRpdmUgY2xpZW50cywgYnV0IHRoaXMgd291bGQgbWFrZSB0
aGVzZSBjbGllbnRzICZxdW90O3N0aWNrIG91dCZxdW90Oy48YnI+DQomZ3Q7PGJyPg0KJmd0OyBP
bmUgc29sdXRpb24gd291bGQgYmUgdG8gcmVtb3ZlIHRoZSBzcGluIGJpdCBmcm9tIHRoZSBzcGVj
LCB0cmFkaW5nIG9mZiBiZXR0ZXIgcHJpdmFjeSBmb3Igd29yc2UgbWFuYWdlbWVudC4gSSBhbSBj
b25zaWRlcmluZyBhbm90aGVyIHNvbHV0aW9uIGluIHdoaWNoIHByaXZhY3kgc2Vuc2l0aXZlIGNs
aWVudHMgaGlkZSB0aGUgUlRUIGJ5IGNvbnRyb2xsaW5nIHRoZSBzcGluLCBmb3IgZXhhbXBsZSBz
cGlubmluZyBhdCBmaXhlZCBpbnRlcnZhbHMuDQogSSBwbGFuIHRlc3RpbmcgdGhhdCBvcHRpb24g
aW4gUGljb3F1aWMuPGJyPg0KJmd0Ozxicj4NCiZndDsgLS0gQ2hyaXN0aWFuIEh1aXRlbWE8YnI+
DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCjxicj4NCjxicj4NCi0tIDxicj4NCkthenVobyBPa3U8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_CY4PR22MB0983A1FF62451F45923220B4DACE0CY4PR22MB0983namp_--


From nobody Wed Oct 31 21:08:40 2018
Return-Path: <mbishop@evequefou.be>
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 D8F44130E96 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 21:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.088
X-Spam-Level: 
X-Spam-Status: No, score=0.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 p0X645ap1WK6 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 21:08:28 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0090.outbound.protection.outlook.com [104.47.41.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5ED5130E43 for <quic@ietf.org>; Wed, 31 Oct 2018 21:08:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=AXo2sK3PWK4deu3F7Q33NPUuvWw5vwHMkPYd9V3IbXM=; b=AN5FA9gmR8M0QhPBW+HTJfvsDck94JFRzr56KijdnDFdE6I+LSlZ7i5hbbjfxJgV3PSAx72HyyNWiFeaUQzdLEmQy2K2/XSa89DKMNDqxrQRCodL6TpxDGSG2e5N/ObpxaIta82+F6jAfE56b2Bjp8yOkjZUA+nkGTYR73797KA=
Received: from CY4PR22MB0983.namprd22.prod.outlook.com (10.171.171.20) by CY4PR22MB0677.namprd22.prod.outlook.com (10.172.135.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1294.20; Thu, 1 Nov 2018 04:08:24 +0000
Received: from CY4PR22MB0983.namprd22.prod.outlook.com ([fe80::706e:6d82:cc25:531f]) by CY4PR22MB0983.namprd22.prod.outlook.com ([fe80::706e:6d82:cc25:531f%10]) with mapi id 15.20.1294.021; Thu, 1 Nov 2018 04:08:24 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: "Lubashev, Igor" <ilubashe@akamai.com>, Tommy Pauly <tpauly@apple.com>, Jana Iyengar <jri.ietf@gmail.com>
CC: Ian Swett <ianswett@google.com>, QUIC WG <quic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>
Subject: RE: flow control and DATAGRAM
Thread-Topic: flow control and DATAGRAM
Thread-Index: AQHUb0aWdW462xFfTkmRJjY3hrxEz6U2KFYAgAAvQoCAAEeKAIAABpeAgAAYeICAA5H68A==
Date: Thu, 1 Nov 2018 04:08:24 +0000
Message-ID: <CY4PR22MB098366E6A90123689A855766DACE0@CY4PR22MB0983.namprd22.prod.outlook.com>
References: <CABkgnnU26aYD=TybuD0FZGYtfEa6np-Sk3Jo6t7LRp0wzKh3Lg@mail.gmail.com> <CAKcm_gMDOyJC0AwOo2knN6AMxVbySjGsrLvjcC9A8UA9xcvcWw@mail.gmail.com> <19D3595B-8845-45B6-A60D-9E934DD49FAC@apple.com> <CACpbDcfk+GXb3aL5LG0wQM87thRGO5Y4Q+9cbXf5YuW1=jWCig@mail.gmail.com> <B7BE2454-2A4D-4323-B0A5-0D73BD4B819F@apple.com> <344a8a30b95441af988b675c2f887965@usma1ex-dag1mb6.msg.corp.akamai.com>
In-Reply-To: <344a8a30b95441af988b675c2f887965@usma1ex-dag1mb6.msg.corp.akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [24.197.53.86]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR22MB0677; 6:slA53Jrxam/f/e2dVQgacmbyqYjjtWUkJu/jM+fWWVwu0SnFwZospnXK13oL6XXOX1r6aTnvC0cp6AvrkmB6vsMaXbXWzwHKMpjYJi/3OTxkV8Ubr/hojJy3qfSOHrScxJc1VLWukfCY9/wHIXhDccTFKhvdMKOyz3DQLzuoDA0Q13EjWnAvYXNDapvtoV7r+i+eq3Flmh6W6MrWmd+1GHzSLH5xMsLHyKoKYfBvchTFO/lEsC4mZxyLgD/quWna4kxnwCqkt6oW84D2Cn7xtxpwe5Ow0tnilU+QyHUuL3hQMAo+88mpVoPdYy2s2GG2u+0e7seOcbiJf7D0/pq4T84itMAuHEbRCkUn1+FCnzBSa8fLfPuvIBHKC8NJNZSxzZWUFAuvGvUAbSkurDAFm72BqRXsMTPab6nwsQnmNbz0SlJCp/B7vvbF5rJ3oa8dCEJWE1ewvoNWdtes3ux69w==; 5:Yv/ssuN6SnLc+KrEbdL/VYpjIN9BhFwrSTl7v3EXHzXsnSRryNcJoMVwMF6EUbK4eSg7Cg3YHARLiP7Vy67+udce2bbl6Exz22jL06LtM4u02DT4DNFU1OxUVCWnp8RwIqdjY2yUiIYDJQdYzfJ1UVCJhDI+bg2IBgq0JLLlASA=; 7:EseifHtI1F4a564EzC32y7tBk6v3ytKYxr/gW/WAly0t1pN2TmURbs0ih50zRwyviWm5ssdOcNo2u0z8B3iwsijHLoEC7gCGOPocUAXMWRxjOie3Tb9Q1BWryPlL7K9HHKoSQHpef+0Kpvutn7j5xA==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 9d3662ec-fe1a-4afe-60f4-08d63fafab37
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:CY4PR22MB0677; 
x-ms-traffictypediagnostic: CY4PR22MB0677:
x-microsoft-antispam-prvs: <CY4PR22MB0677CCAB8D576C4E0EAD53D1DACE0@CY4PR22MB0677.namprd22.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(31960201722614)(80524489315369)(85827821059158)(211936372134217)(153496737603132)(166708455590820)(278428928389397)(21748063052155)(28532068793085)(190501279198761);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(3231382)(944501410)(52105095)(148016)(149066)(150057)(6041310)(20161123558120)(20161123564045)(20161123560045)(20161123562045)(2016111802025)(6043046)(201708071742011)(7699051)(76991095); SRVR:CY4PR22MB0677; BCL:0; PCL:0; RULEID:; SRVR:CY4PR22MB0677; 
x-forefront-prvs: 0843C17679
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39830400003)(396003)(366004)(376002)(346002)(136003)(199004)(189003)(7736002)(6506007)(99286004)(26005)(76176011)(74316002)(256004)(7696005)(97736004)(53546011)(25786009)(102836004)(14444005)(508600001)(5660300001)(790700001)(110136005)(6116002)(33656002)(2900100001)(229853002)(5250100002)(6246003)(3846002)(54906003)(68736007)(316002)(11346002)(81156014)(14454004)(8676002)(105586002)(4326008)(486006)(39060400002)(71200400001)(71190400001)(81166006)(8936002)(186003)(236005)(106356001)(966005)(606006)(3480700004)(55016002)(6436002)(476003)(2906002)(86362001)(53936002)(54896002)(6306002)(9686003)(66066001)(446003)(93886005)(74482002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR22MB0677; H:CY4PR22MB0983.namprd22.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: yuJZhFTJlZ06CwY4IG6rhVMf806XzbRklqxvavMlZFa8vdZLaYCjDldj926J+Z8bZCawhJzqmtQDvIBL0D1UnZR9fbPYuoIYp268AyP6SU6goqlLG6/ewRtp1yJI9OmbCNrN/pwG77hUAolBTWeFCZE4QBsFcFuHzGd6l1rVasH+Y2uE/1/7N4m/c84hBk9ZfI7O5Ugo0foX6diBD52mLG7N53poSIFbzjCN+HFBgJfnMeuGTYogL2adjSFD6YWu3Q77KMiRsdn1MNbLekIfBNTC1wdzm09UrXKI1jZTUnpTEGUXof+b90LvZeHP0j5dyhcQNazsrI0y8Ta3xKoPDJusPjLs7XXN+7GV1WoBVWA=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CY4PR22MB098366E6A90123689A855766DACE0CY4PR22MB0983namp_"
MIME-Version: 1.0
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 9d3662ec-fe1a-4afe-60f4-08d63fafab37
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Nov 2018 04:08:24.1631 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR22MB0677
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/XoB81OyKlO_sszQWstMXfIoRPoo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Nov 2018 04:08:38 -0000

--_000_CY4PR22MB098366E6A90123689A855766DACE0CY4PR22MB0983namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGVjaG5pY2FsbHksIGFuIGltcGxlbWVudGF0aW9uIGNvdWxkIGNob29zZSBub3QgdG8gQUNLIHdp
dGhvdXQgaWdub3JpbmcgYWxsIGZyYW1lcyBpbiB0aGUgcGFja2V0LiAgT3VyIGRlc2lnbiBmb3Ig
ZnJhbWVzIHNheXMgdGhhdCB0aGV5IGNhbiBiZSBzZW50L3JlY2VpdmVkIG11bHRpcGxlIHRpbWVz
IHdpdGhvdXQgZXJyb3IsIHNvIGEgc3B1cmlvdXNseS1yZXRyYW5zbWl0dGVkIHJlbGlhYmxlIGZy
YW1lIGZyb20gdGhhdCBwYWNrZXQgaXMgd2FzdGVkIGRhdGEsIGJ1dCBub3QgYW4gZXJyb3IuICBI
b3dldmVyLCBpdCBtaWdodCBub3QgYmUgdG90YWxseSBjbGVhciB0byBhcHBsaWNhdGlvbiBkZXNp
Z25lcnMgdGhhdCwgd2hpbGUgQUNLcyBjYW4gdGVsbCB5b3Ugd2hpY2ggZGF0YWdyYW1zIGRlZmlu
aXRlbHkgZGlkIGFycml2ZSwgdGhleSBjYW4gbmV2ZXIgdGVsbCB5b3Ugd2hpY2ggb25lcyBkZWZp
bml0ZWx5IGRpZG7igJl0Lg0KDQpCdXQgaXQgc291bmRzIGxpa2Ugd2hlcmUgdGhpcyBpcyBnb2lu
ZyBpcyB0aGUgcmVhbGl6YXRpb24gdGhhdCB5b3UgaGF2ZSB0byBoYXZlIGZsb3cgY29udHJvbCBp
ZiB5b3XigJlyZSBnb2luZyB0byBwcm9oaWJpdCB0aGUgcmVtb3RlIGltcGxlbWVudGF0aW9uIGZy
b20gZHJvcHBpbmcgZGF0YWdyYW1zIGFmdGVyIEFDS2luZyB0aGVtOyBidXQgaWYgeW91IGRvIGFs
bG93IHRoZSBpbXBsZW1lbnRhdGlvbiB0byBkbyB0aGF0LCB0aGVuIEFDS3MgdGVsbCB5b3Ugbm90
aGluZyBjb25jcmV0ZSBhYm91dCBEQVRBR1JBTXMgdGhhdCBtaWdodCBoYXZlIGJlZW4gaW4gdGhv
c2UgcGFja2V0cy4NCg0KRnJvbTogUVVJQyA8cXVpYy1ib3VuY2VzQGlldGYub3JnPiBPbiBCZWhh
bGYgT2YgTHViYXNoZXYsIElnb3INClNlbnQ6IE1vbmRheSwgT2N0b2JlciAyOSwgMjAxOCA0OjI5
IFBNDQpUbzogVG9tbXkgUGF1bHkgPHRwYXVseUBhcHBsZS5jb20+OyBKYW5hIEl5ZW5nYXIgPGpy
aS5pZXRmQGdtYWlsLmNvbT4NCkNjOiBJYW4gU3dldHQgPGlhbnN3ZXR0QGdvb2dsZS5jb20+OyBR
VUlDIFdHIDxxdWljQGlldGYub3JnPjsgTWFydGluIFRob21zb24gPG1hcnRpbi50aG9tc29uQGdt
YWlsLmNvbT4NClN1YmplY3Q6IFJFOiBmbG93IGNvbnRyb2wgYW5kIERBVEFHUkFNDQoNCj4gQUNL
IHRvIGEgcGFja2V0IGNvbnRhaW5pbmcgYSBEQVRBR1JBTSBmcmFtZSBtZWFuczoNCj4gLSBUaGUg
cGFja2V0IG1hZGUgaXQgYWNyb3NzIHRoZSBuZXR3b3JrIHRvIHRoZSBRVUlDIGVuZHBvaW50IG9u
IHRoZSBvdGhlciBzaWRlDQo+IC0gVGhlIFFVSUMgaW1wbGVtZW50YXRpb24gd2lsbCBkZWxpdmVy
IHRoZSBEQVRBR1JBTSBmcmFtZSB0byBhcHBsaWNhdGlvbiAoaXQgd29uJ3QgZHJvcCBpdCBsb2Nh
bGx5KQ0KPg0KPiBEb2VzIHRoYXQgbWFrZSBzZW5zZT8NCg0KVGhpcyBvbmx5IG1ha2VzIHNlbnNl
LCBpZiB0aGVyZSBpcyBhbiBlZmZlY3RpdmUgZmxvdyBjb250cm9sIGZvciBEQVRBR1JBTXMuICBU
aGUgc3BlYyBzaG91bGQgYmUgaW1wbGVtZW50YWJsZSBieSBwb2xsL3JlYWQgUVVJQyBpbXBsZW1l
bnRhdGlvbnMgYXMgd2VsbCBhcyBieSBjYWxsYmFjay1vbi1uZXR3b3JrLXJlY2VpdmUtdGhyZWFk
IGltcGxlbWVudGF0aW9ucy4gIFVubGVzcyB0aGVyZSBpcyBhbiBlZmZlY3RpdmUgZmxvdyBjb250
cm9sLCBhIGJ1ZmZlcmluZyBRVUlDIGltcGxlbWVudGF0aW9uIG11c3QgYmUgYWJsZSB0byBkaXNj
YXJkIERBVEFHUkFNcywgaWYgdGhlIHJlY2VpdmVyIGFwcCBpcyBub3QgY2F0Y2hpbmcgdXAuICBU
aGUgcmVjZWl2ZXIgd291bGQgdGhlbiBoYXZlIHRvIGlnbm9yZSBhbGwgbm9uLURBVEFHUkFNIGZy
YW1lcyBpbiB0aGF0IHBhY2tldCwgc2luY2UgaXQgd291bGQgYmUgdW5hYmxlIHRvIEFDSyB0aGUg
cGFja2V0LiAgSWYgdGhlIHJlY2VpdmVyIGlzIHByb2Nlc3NpbmcgREFUQUdSQU1zIGFuZCBTVFJF
QU1zIGF0IGRpZmZlcmVudCBzcGVlZHMsIGRlbGliZXJhdGUgZGlzY2FyZHMgb2YgcGFja2V0cyBj
b250YWluaW5nIERBVEFHUkFNcyB3b3VsZCBpbnRlcmZlcmUgd2l0aCB0aGUgY29uZ2VzdGlvbiBj
b250cm9sLCBlZmZlY3RpdmVseSBIT0wgYmxvY2tpbmcgU1RSRUFNcy4NCg0KQW4gZWZmZWN0aXZl
IGZsb3cgY29udHJvbCByZXF1aXJlcyBzZW5kZXIgYW5kIHJlY2VpdmVyIHRvIHN5bmNocm9uaXpl
IHRoZWlyIHZpZXcgb2YgdGhlIGZsb3cgY29udHJvbCBjb3VudGVyIChNQVhfREFUQSBmb3IgY29u
bmVjdGlvbiBmbG93IGNvbnRyb2wpLiAgUmVseWluZyBvbiBBQ0tzIGlzIHZlcnkgaGFyZCwgc2lu
Y2UgdGhlIHJlY2VpdmVyIGNhbm5vdCBrbm93IGhvdyBtdWNoIGRhdGEgdGhlIHNlbmRlciBoYXMg
c2VudCAodW5sZXNzIHRoZSBzZW5kZXIgaXMgZXhwbGljaXQgYWJvdXQgaXQpLg0KDQpJZiBmbG93
IGNvbnRyb2wgZm9yIERBVEFHUkFNcyBpcyBkZXNpcmVkLCB5b3UgY2FuIHVzZSBtZWNoYW5pY3Mg
c3VjaCBhcyBpbiBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtbHViYXNoZXYtcXVp
Yy1wYXJ0aWFsLXJlbGlhYmlsaXR5LTAyIG9yIGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9k
cmFmdC1sdWJhc2hldi1xdWljLXBhcnRpYWwtcmVsaWFiaWxpdHktMDMgKGh0dHBzOi8vZ2l0aHVi
LmNvbS9pZ29ybG9yZC9kcmFmdC1sdWJhc2hldi1xdWljLXBhcnRpYWwtcmVsaWFiaWxpdHkpLiAg
KFRoaXMgd291bGQgYmUgdHJlYXRpbmcgREFUQUdSQU1zIGFzIGJlbG9uZ2luZyB0byBhIHBhcnRp
YWxseSByZWxpYWJsZSBzdHJlYW0sIG9yIHN0cmVhbXMuICBFeGNlcHQgeW91IHdvdWxkIG5vdCBu
ZWVkIHRvIGVuc3VyZSBvcmRlcmluZyBvZiBEQVRBR1JBTXMgaW4gdGhhdCBzdHJlYW0uKQ0KDQoN
CiAgKiAgIElnb3INCg0KDQpGcm9tOiBUb21teSBQYXVseSA8dHBhdWx5QGFwcGxlLmNvbTxtYWls
dG86dHBhdWx5QGFwcGxlLmNvbT4+DQpTZW50OiBNb25kYXksIE9jdG9iZXIgMjksIDIwMTggNDow
MSBQTQ0KVG86IEphbmEgSXllbmdhciA8anJpLmlldGZAZ21haWwuY29tPG1haWx0bzpqcmkuaWV0
ZkBnbWFpbC5jb20+Pg0KQ2M6IElhbiBTd2V0dCA8aWFuc3dldHRAZ29vZ2xlLmNvbTxtYWlsdG86
aWFuc3dldHRAZ29vZ2xlLmNvbT4+OyBRVUlDIFdHIDxxdWljQGlldGYub3JnPG1haWx0bzpxdWlj
QGlldGYub3JnPj47IE1hcnRpbiBUaG9tc29uIDxtYXJ0aW4udGhvbXNvbkBnbWFpbC5jb208bWFp
bHRvOm1hcnRpbi50aG9tc29uQGdtYWlsLmNvbT4+DQpTdWJqZWN0OiBSZTogZmxvdyBjb250cm9s
IGFuZCBEQVRBR1JBTQ0KDQpIaSBKYW5hLA0KDQpJJ20gbm90IHN1Z2dlc3RpbmcgYW55IGNoYW5n
ZXMgdG8gd2hlbiB0aGUgcGFja2V0IGdldHMgYWNrJ2Vk4oCUc3BlY2lmaWNhbGx5LCBJIHdhcyBy
ZXNwb25kaW5nIHRvIE1hcnRpbidzIGh5cG90aGV0aWNhbCBvZiBoYXZpbmcgYW4gQUNLIHRvIGEg
REFUQUdSQU0gZnJhbWUgbWVhbmluZyB0aGF0IHRoZSBhcHBsaWNhdGlvbiBoYWQgcHJvY2Vzc2Vk
IHRoZSBmcmFtZS4gTXkgaW1wcmVzc2lvbiBpcyB0aGF0IHRoZSBBQ0sgdG8gYSBwYWNrZXQgY29u
dGFpbmluZyBhIERBVEFHUkFNIGZyYW1lIG1lYW5zOg0KLSBUaGUgcGFja2V0IG1hZGUgaXQgYWNy
b3NzIHRoZSBuZXR3b3JrIHRvIHRoZSBRVUlDIGVuZHBvaW50IG9uIHRoZSBvdGhlciBzaWRlDQot
IFRoZSBRVUlDIGltcGxlbWVudGF0aW9uIHdpbGwgZGVsaXZlciB0aGUgREFUQUdSQU0gZnJhbWUg
dG8gYXBwbGljYXRpb24gKGl0IHdvbid0IGRyb3AgaXQgbG9jYWxseSkNCg0KRG9lcyB0aGF0IG1h
a2Ugc2Vuc2U/DQoNCkhhdmluZyBhIHNlcGFyYXRlIG91dHN0YW5kaW5nIGRhdGEgbGltaXQgZm9y
IHRoZSBEQVRBR1JBTSAic3RyZWFtIiBpcyBhbiBpbnRlcmVzdGluZyBzb2x1dGlvbiB0byB0aGUg
c3BhY2UuIEl0IHdvdWxkIHRoZW4gaGF2ZSB0aGUgbmljZSBwcm9wZXJ0eSBvZiBub3QgbG9va2lu
ZyBsaWtlIHRyYWRpdGlvbmFsIGZsb3cgY29udHJvbC4gSXQgY291bGQgZXZlbiBiZSBtZWFzdXJl
ZCBpbiBudW1iZXIgb2YgZnJhbWVzLCByYXRoZXIgdGhhbiBieXRlcyAoZGVwZW5kaW5nIG9uIHdo
YXQgdGhlIGxpbWl0aW5nIGZhY3RvcnMgYXJlKS4NCg0KVGhhbmtzLA0KVG9tbXkNCg0KT24gT2N0
IDI5LCAyMDE4LCBhdCAxMjozNyBQTSwgSmFuYSBJeWVuZ2FyIDxqcmkuaWV0ZkBnbWFpbC5jb208
bWFpbHRvOmpyaS5pZXRmQGdtYWlsLmNvbT4+IHdyb3RlOg0KDQpUb21teSwNCg0KQ2hhbmdpbmcg
dGhlIHNlbWFudGljcyBvZiBhbiBhY2tub3dsZWRnbWVudCB0byBpbmNsdWRlIGRlbGl2ZXJ5IHVw
IHRvIHRoZSBhcHBsaWNhdGlvbiBpcyBhIGZ1bmRhbWVudGFsIGNoYW5nZSB0byB0aGUgUVVJQyBt
YWNoaW5lcnksIGFuZCBpdCBkb2Vzbid0IHdvcmsuIEZpcnN0LCBhbiBBQ0sgZnJhbWUgYWNrbm93
bGVkZ2VzIHBhY2tldHMsIGFuZCB5b3UgY2FuJ3QgaGF2ZSBkaWZmZXJlbnQgc2VtYW50aWNzIG9m
IGFuIGFja25vd2xlZGdtZW50IGZvciBkaWZmZXJlbnQgZnJhbWVzIHRoYXQgYXJlIGNhcnJpZWQg
aW4gdGhlIHNhbWUgcGFja2V0LiBTZWNvbmQsIGl0IGludGVyZmVyZXMgd2l0aCBSVFQgbWVhc3Vy
ZW1lbnQsIGFuZCBpdCBjb25mbGF0ZXMgZmxvdyBjb250cm9sIHdpdGggY29uZ2VzdGlvbiBjb250
cm9sLCB3aGljaCBnZXRzIG1lc3N5LiAoVGhpcyBjb25mbGF0aW9uIGlzIGFuIGludGVyZXN0aW5n
IHByb2JsZW0gdG8gY29uc2lkZXIgdGhlb3JldGljYWxseSwgYnV0IG5vdCBvbmUgZm9yIHVzIGF0
IHRoaXMgdGltZSBJTU8uKQ0KDQpJIGFtIHdvbmRlcmluZyBpZiBhcHBseWluZyBhIHN0cmVhbS1s
ZXZlbCBmbG93IGNvbnRyb2wgZm9yIERBVEFHUkFNcyBtYWtlcyBzZW5zZSBpbnN0ZWFkLiBNZWFu
aW5nIHRoYXQgeW91IHRyZWF0IERBVEFHUkFNcyBhcyBhIHNlcGFyYXRlIHN0cmVhbSBmb3IgZmxv
dyBjb250cm9sIHB1cnBvc2VzLiBZb3UgbWlnaHQgYmVuZWZpdCBmcm9tIGhhdmluZyBhbiBvZmZz
ZXQgaW4gdGhlIERBVEFHUkFNIGZyYW1lIGZvciB0aGlzIHB1cnBvc2UuDQoNCi0gamFuYQ0KDQpP
biBNb24sIE9jdCAyOSwgMjAxOCBhdCA4OjIxIEFNIFRvbW15IFBhdWx5IDx0cGF1bHlAYXBwbGUu
Y29tPG1haWx0bzp0cGF1bHlAYXBwbGUuY29tPj4gd3JvdGU6DQpIaSBNYXJ0aW4sIElhbiwNCg0K
WWVzLCB2ZXJ5IGdvb2QgcG9pbnRzIQ0KDQpNeSB0ZW5kZW5jeSB3b3VsZCBiZSB0byBwcmVmZXIg
d2hhdCBJYW4ncyBpbXBsZW1lbnRhdGlvbiBkb2VzIG9mIHBhc3NpbmcgdGhlc2UgREFUQUdSQU0g
ZnJhbWVzIHVwIGltbWVkaWF0ZWx5IHRvIHRoZSBhcHBsaWNhdGlvbi4gSSBkb24ndCB0aGluayB0
aGF0IHRoZSBhY2tub3dsZWRnbWVudCBuZWVkcyB0byBpbmRpY2F0ZSB0aGF0IHRoZSBmcmFtZSB3
YXMgcHJvY2Vzc2VkIGJ5IHRoZSBhcHBsaWNhdGlvbiwgYnV0IG1lcmVseSB0aGF0IGl0IGhhcyBi
ZWVuIGRlbGl2ZXJlZCB0byB0aGUgYXBwbGljYXRpb24gKHRoYXQgaXMsIHRoZSBhcHBsaWNhdGlv
biBkb2Vzbid0IGdldCB0byBkbyBhbnl0aGluZyB3aXRoIHRoZSBmcmFtZSB0aGF0IGNhbiBpbmZs
dWVuY2UgdGhlIGFja25vd2xlZGdtZW50KS4NCg0KVGhlIGN1cnJlbnQgZHJhZnQgaW5kaWNhdGVz
IHRoYXQgdGhlIGNvbnRlbnQgb2YgdGhlIERBVEFHUkFNIGZyYW1lcyBjb250cmlidXRlcyB0byB0
aGUgbGltaXQgdXNlZCBmb3IgTUFYX0RBVEEsIGFuZCB0aGF0IGlmIHRoYXQgYW1vdW50IGlzIHJl
YWNoZWQsIHRoZSBmcmFtZXMgYXJlIGJsb2NrZWQgYWxvbmcgd2l0aCBTVFJFQU0gZGF0YS4gSSB0
aGluayB0aGlzIHdvcmtzIGZpbmUgZm9yIHRoZSBzZW5kZXIsIHdoaWxlIHRoZSByZWNlaXZlciBn
ZXRzIGludG8gdGhlIGRpc2N1c3Npb24geW91IHByZXNlbnQuIE9uIHRoZSBzZW5kZXIgc2lkZSwg
cmVhY2hpbmcgTUFYX0RBVEEgY291bGQgbWVhbiBkcm9wcGluZyB0aGUgREFUQUdSQU0gZnJhbWVz
IHdoZW4gdW5hYmxlIHRvIHNlbmQgbW9yZSAoYW5kIHNlbmRpbmcgQkxPQ0tFRCBpbnN0ZWFkKS4g
U2luY2UgdGhlIGZyYW1lcyBhcmUgdW5yZWxpYWJsZSwgdGhleSBjYW4gYmUgZHJvcHBlZCBpbiB0
aGlzIHNpdHVhdGlvbiB3aXRob3V0IHZpb2xhdGluZyB0aGUgQVBJIGNvbnRyYWN0Lg0KDQpPbiB0
aGUgcmVjZWl2ZXIgc2lkZSwgSSBhZ3JlZSB0aGF0IHF1ZXVpbmcgdGhlIERBVEFHUkFNIGZyYW1l
cyB0byBsZXQgdGhlIGFwcGxpY2F0aW9uIGRyaXZlIGZsb3cgY29udHJvbCBpbiB0aGUgd2F5IGl0
IGRvZXMgZm9yIFNUUkVBTSBmcmFtZXMgYWRkcyBjb21wbGV4aXR5IGFuZCBkaW1pbmlzaGVzIHRo
ZSB1dGlsaXR5IG9mIHRoZSBmcmFtZSBhbmQgQUNLcy4uIEhvd2V2ZXIsIEkgY2FuIGltYWdpbmUg
dGFraW5nIGEgZmFpcmx5IHNpbXBsaXN0aWMgYXBwcm9hY2ggaW4gd2hpY2ggdGhlIGRhdGEgbGlt
aXQgaXMgYXV0b21hdGljYWxseSBpbmNyZWFzZWQgdXBvbiByZWNlcHRpb24gb2YgdGhlIGZyYW1l
IChhbmQgdGhlIGZyYW1lIGlzIGltbWVkaWF0ZWx5IHBhc3NlZCB0byB0aGUgYXBwbGljYXRpb24p
LiBUaGlzIGFsbG93cyB0aGUgaW5pdGlhbF9tYXhfZGF0YSB0byBwdXQgYSBjYXAgb24gdGhlIGFt
b3VudCBvZiBkYXRhIGluIGEgZ2l2ZW4gZmxpZ2h0IG9mIERBVEFHUkFNUywgYW5kIGFsbG93IHRo
ZSBzaXplIG9mIGEgZmxpZ2h0IG9mIERBVEFHUkFNIGZyYW1lcyB0byBiZSBsaW1pdGVkIGJ5IHRo
ZSBhbW91bnQgb2Ygcm9vbSBsZWZ0IG92ZXIgZnJvbSBTVFJFQU0gZGF0YSB0aGF0IG1heSBiZSBj
b25zdW1pbmcgdGhlIGNvbm5lY3Rpb24td2lkZSBmbG93IGNvbnRyb2wuDQoNClBlcmhhcHMgdGhp
cyBhcHByb2FjaCBuZWVkcyBhIGNsZWFyZXIgbmFtZSBvdGhlciB0aGFuICJmbG93IGNvbnRyb2wi
LCBzaW5jZSBpdCBoYXMgYSBzb21ld2hhdCBkaWZmZXJlbnQgbWVhbmluZyBpbiBlZmZlY3QuDQoN
CkFzIGZvciBBQ0tzLCBpZiB3ZSBuZXZlciBkaXNjYXJkIG9uIHRoZSByZWNlaXZlciBzaWRlLCB0
aGUgQUNLIGlzIHByZXR0eSB1c2VmdWwgZm9yIGRldGVjdGluZyBpZiB0aGVyZSB3YXMgbmV0d29y
ay1iYXNlZCBwYWNrZXQgbG9zcy4NCg0KVGhhbmtzLA0KVG9tbXkNCg0KT24gT2N0IDI5LCAyMDE4
LCBhdCA1OjMyIEFNLCBJYW4gU3dldHQgPGlhbnN3ZXR0QGdvb2dsZS5jb208bWFpbHRvOmlhbnN3
ZXR0QGdvb2dsZS5jb20+PiB3cm90ZToNCg0KR29vZCBjYXRjaCBNYXJ0aW4sIEkgbWlzc2VkIHRo
YXQgaW4gdGhlIGRyYWZ0IGFzIHdlbGwsIGFuZCBJIGFsc28gdGhpbmsgaXQncyBpbXBvc3NpYmx5
IHdpdGggdGhlIHByb3Bvc2VkIGRlc2lnbi4NCg0KQW5kIHllcywgSSB0aGluayBNYXJ0aW4ncyBw
cm9wb3NlZCBzb2x1dGlvbiBpcyBsaWtlbHkgdGhlIG9ubHkgcHJhY3RpY2FsIG9uZS4gIEluIG15
IGltcGxlbWVudGF0aW9uLCB0aGUgZnJhbWUgaXMgcGFzc2VkIHVwIHRvIHRoZSBhcHBsaWNhdGlv
biBpbW1lZGlhdGVseSwgc28gdGVjaG5pY2FsbHkgUVVJQyBwcm9jZXNzZWQgaXQsIGFuZCBpdCdz
IHRoZSBhcHBsaWNhdGlvbidzIGpvYiB0byBkZWNpZGUgd2hhdCB0byBkbyB3aXRoIGl0Lg0KDQpP
biBNb24sIE9jdCAyOSwgMjAxOCBhdCAxOjE2IEFNIE1hcnRpbiBUaG9tc29uIDxtYXJ0aW4udGhv
bXNvbkBnbWFpbC5jb208bWFpbHRvOm1hcnRpbi50aG9tc29uQGdtYWlsLmNvbT4+IHdyb3RlOg0K
SGkgVG9tbXksDQoNCllvdXIgc2xpZGVzIC0gPGh0dHBzOi8vZ2l0aHViLmNvbS9xdWljd2cvd2ct
bWF0ZXJpYWxzL2Jsb2IvbWFzdGVyL2lldGYxMDMvSUVURjEwMy1RVUlDLURhdGFncmFtLnBkZjxo
dHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cHMtM0FfX2dpdGh1
Yi5jb21fcXVpY3dnX3dnLTJEbWF0ZXJpYWxzX2Jsb2JfbWFzdGVyX2lldGYxMDNfSUVURjEwMy0y
RFFVSUMtMkREYXRhZ3JhbS5wZGYmZD1Ed01GYVEmYz05NlpiWlpjYU1GNHcwRjRqcE42TFpnJnI9
RGpuM2JRNXVOSkRQTV8yc2tmTDNyVzF0emNJeHlqVVpkbl9tNTVLUG1sbyZtPS1KQVZ5S0s0THJE
RlVuLVR6STk2WkZsckZaWW96ZzRHRlZ0dG5qSWpHZGcmcz10cVVRWlctaFAwR3daN3gxb3RQa1NZ
cEEzYXhHVml6WXUwYTRKbExvdTZRJmU9Pj4NCi0gc2F5IHRoYXQgREFUQUdSQU0gZnJhbWVzIHJl
c3BlY3QgY29ubmVjdGlvbi1sZXZlbCBmbG93IGNvbnRyb2wuICBJDQptaXNzZWQgdGhhdCBpbiB0
aGUgZHJhZnQsIGFuZCBJIGRvbid0IGtub3cgaG93IHRoZXkgY2FuIGRvIHRoYXQgaW4gdGhlDQpm
YWNlIG9mIHBhY2tldCBsb3NzLCBlc3BlY2lhbGx5IHdoZW4geW91IGRvbid0IG5lY2Vzc2FyaWx5
IHJldHJhbnNtaXQNCmxvc3QgREFUQUdSQU0gZnJhbWVzLg0KDQpGb3IgdGhhdCB0byB3b3JrLCB5
b3Ugd291bGQgbmVlZCBhIGJ1bmNoIG1vcmUgbWFjaGluZXJ5IHRvIG1ha2UgdGhlDQpjb25uZWN0
aW9uLWxldmVsIGZsb3cgY29udHJvbCBzeW5jIGJldHdlZW4gZW5kcG9pbnRzIGluIHRoZSBjYXNl
IHRoYXQNCnBhY2tldHMgYXJlIGxvc3QuICBBIGRpc2FncmVlbWVudCBhYm91dCBob3cgbXVjaCBm
bG93IGNvbnRyb2wgaXMgdXNlZA0KY2F1c2VzIHRoaW5ncyB0byBicmVhayBkb3duIGJhZGx5LiAg
SWFuIGFuZCBJIGRpc2N1c3NlZCB0aGlzIHBvaW50IGF0DQp0aGUgbGFzdCBtZWV0aW5nIGFuZCBx
dWlja2x5IGFncmVlZCB0aGF0IHdoaWxlIGl0IG1pZ2h0IGJlIG5pY2UgdG8NCmhhdmUgZmxvdyBj
b250cm9sIGZvciB0aGlzIHN0dWZmLCB0aGUgaW5jcmVhc2UgaW4gY29tcGxleGl0eSBpcw0KY29u
c2lkZXJhYmxlIGFuZCAoYXQgdGhlIHRpbWUpIHdlIHRob3VnaHQgaXQgd291bGRuJ3QgYmUgd29y
dGggaXQuDQoNClRoZSBwcm9ibGVtIHRoYXQgaW50cm9kdWNlcyBpcyB0aGF0IHlvdSBjb3VsZCBl
bmQgdXAgaGF2aW5nIHRvbyBtYW55DQpEQVRBR1JBTSBmcmFtZXMgYXJyaXZlLiAgVGhlIHJlY2Vp
dmVyIGhhcyB0byBkcm9wIHNvbWV0aGluZyBhdCB0aGUNCnBvaW50IHRoYXQgaXQgY2FuJ3QgaGFu
ZGxlIHRoZW0uICBBbmQgd2Ugc2F5IHRoYXQgd2hlbiB5b3UgYWNrbm93bGVkZ2UNCnNvbWV0aGlu
ZywgeW91IHByb2Nlc3NlZCBpdC4gIFRoYXQncyB0cmlja3kuDQoNCkl0IG1pZ2h0IGJlIGVhc2ll
ciB0byBzYXkgdGhhdCBhIFFVSUMgYWNrbm93bGVkZ21lbnQgZm9yIGEgREFUQUdSQU0NCmZyYW1l
IGRvZXNuJ3QgbWVhbiB0aGF0IGl0IHdhcyByZWNlaXZlZCBhbmQgcHJvY2Vzc2VkIGJ5IGFuDQph
cHBsaWNhdGlvbi4gIEFuIGVuZHBvaW50IG1pZ2h0IGRpc2NhcmQgdGhlc2UgZnJhbWVzIGJlZm9y
ZSBwYXNzaW5nDQp0aGVtIG9uIHRvIGFwcGxpY2F0aW9ucyBpZiBpdCBkb2Vzbid0IGhhdmUgc3Bh
Y2UuICBJbiBvdGhlciB3b3JkcywNCmFja25vd2xlZGdtZW50IG9mIERBVEFHUkFNIG1lYW5zIHRo
YXQgUVVJQyBnb3QgaXQsIG5vdCB0aGF0IHRoZQ0KYXBwbGljYXRpb24gZ290IGl0LiAgU2FkbHks
IHRoYXQgbWVhbnMgdGhhdCB0aGUgUVVJQyBhY2tub3dsZWRnbWVudA0KbWFjaGluZXJ5IGRvZXNu
J3QgaGVscCB0aGUgYXBwbGljYXRpb24gdGhhdCB1c2VzIERBVEFHUkFNIGFsbCB0aGF0DQptdWNo
LiAgQWxzbywgdGhlIGxvd2VyIGJvdW5kIG9uIHJlbGlhYmlsaXR5IGlzIDAsIHdoaWNoIGlzbid0
IHRoZSBiZXN0DQp0aGluZyBldmVyLg0KDQpIYXJkIGNob2ljZXMsIEkga25vdy4gIEkgZG9uJ3Qg
aGF2ZSBhIGdvb2QgZGVzaWduIGZvciBtYWludGFpbmluZw0KY29ubmVjdGlvbi1sZXZlbCBmbG93
IGNvbnRyb2wgKG9yIGFueSBiYWNrIHByZXNzdXJlIG1lY2hhbmlzbSB3aXRoDQplcXVpdmFsZW50
IHByb3BlcnRpZXMpIHRoYXQgZG9lc24ndCBhZGQgYm90aCBjb21wbGV4aXR5IGFuZCBvdmVyaGVh
ZC4NCg0KQ2hlZXJzLA0KTWFydGluDQoNCg0K

--_000_CY4PR22MB098366E6A90123689A855766DACE0CY4PR22MB0983namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1
IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZp
c2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5
Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvTGlz
dFBhcmFncmFwaCwgbGkuTXNvTGlzdFBhcmFncmFwaCwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGgNCgl7
bXNvLXN0eWxlLXByaW9yaXR5OjM0Ow0KCW1hcmdpbi10b3A6MGluOw0KCW1hcmdpbi1yaWdodDow
aW47DQoJbWFyZ2luLWJvdHRvbTowaW47DQoJbWFyZ2luLWxlZnQ6LjVpbjsNCgltYXJnaW4tYm90
dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
c2Fucy1zZXJpZjt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWww
DQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsN
CgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdp
bi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE5DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFs
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTIw
DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5z
LXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTIxDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJl
cGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCi5Nc29DaHBEZWZhdWx0
DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBh
Z2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBp
biAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30N
Ci8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0IGwwDQoJe21zby1saXN0LWlkOjQ2MjA0MDYz
OTsNCgltc28tbGlzdC10ZW1wbGF0ZS1pZHM6LTEzOTk5NTY1ODY7fQ0KQGxpc3QgbDA6bGV2ZWwx
DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7
DQoJbXNvLWxldmVsLXRhYi1zdG9wOi41aW47DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjps
ZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0K
CWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDINCgl7bXNvLWxldmVsLW51bWJl
ci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0
b3A6MS4waW47DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50
Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJv
bDt9DQpAbGlzdCBsMDpsZXZlbDMNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0K
CW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6MS41aW47DQoJbXNvLWxl
dmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5z
aS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZl
bDQNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+C
tzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6Mi4waW47DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlv
bjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0
Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDUNCgl7bXNvLWxldmVsLW51
bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFi
LXN0b3A6Mi41aW47DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5k
ZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5
bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDYNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0
Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6My4waW47DQoJbXNv
LWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28t
YW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDps
ZXZlbDcNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0
Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6My41aW47DQoJbXNvLWxldmVsLW51bWJlci1wb3Np
dGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAu
MHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDgNCgl7bXNvLWxldmVs
LW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwt
dGFiLXN0b3A6NC4waW47DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQt
aW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5
OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDkNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVs
bGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6NC41aW47DQoJ
bXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglt
c28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBs
MQ0KCXttc28tbGlzdC1pZDoxMTMwMTcyNjc1Ow0KCW1zby1saXN0LXR5cGU6aHlicmlkOw0KCW1z
by1saXN0LXRlbXBsYXRlLWlkczoxMDgzMzU2MjY2IC00MTczMDU2NDQgNjc2OTg2OTEgNjc2OTg2
OTMgNjc2OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTM7
fQ0KQGxpc3QgbDE6bGV2ZWwxDQoJe21zby1sZXZlbC1zdGFydC1hdDowOw0KCW1zby1sZXZlbC1u
dW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDotOw0KCW1zby1sZXZlbC10YWIt
c3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVu
dDotLjI1aW47DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJbXNvLWZhcmVh
c3QtZm9udC1mYW1pbHk6Q2FsaWJyaTsNCgltc28tYmlkaS1mb250LWZhbWlseToiVGltZXMgTmV3
IFJvbWFuIjt9DQpAbGlzdCBsMTpsZXZlbDINCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVs
bGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNv
LWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250
LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwxOmxldmVsMw0KCXttc28tbGV2ZWwtbnVt
YmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWIt
c3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVu
dDotLjI1aW47DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwxOmxldmVsNA0KCXtt
c28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1z
by1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsN
Cgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwxOmxl
dmVsNQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6
bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9u
OmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7
fQ0KQGxpc3QgbDE6bGV2ZWw2DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCglt
c28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVs
LW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWls
eTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDE6bGV2ZWw3DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0
OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7
DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsN
Cglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDE6bGV2ZWw4DQoJe21zby1sZXZlbC1udW1i
ZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3Rv
cDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDot
LjI1aW47DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMTpsZXZlbDkNCgl7
bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCglt
c28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7
DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpvbA0KCXtt
YXJnaW4tYm90dG9tOjBpbjt9DQp1bA0KCXttYXJnaW4tYm90dG9tOjBpbjt9DQotLT48L3N0eWxl
PjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIg
c3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48
eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQi
IGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+
DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNs
YXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGVjaG5pY2FsbHksIGFu
IGltcGxlbWVudGF0aW9uIGNvdWxkIGNob29zZSBub3QgdG8gQUNLIHdpdGhvdXQgaWdub3Jpbmcg
YWxsIGZyYW1lcyBpbiB0aGUgcGFja2V0LiZuYnNwOyBPdXIgZGVzaWduIGZvciBmcmFtZXMgc2F5
cyB0aGF0IHRoZXkgY2FuIGJlIHNlbnQvcmVjZWl2ZWQgbXVsdGlwbGUgdGltZXMgd2l0aG91dCBl
cnJvciwgc28gYSBzcHVyaW91c2x5LXJldHJhbnNtaXR0ZWQgcmVsaWFibGUgZnJhbWUgZnJvbQ0K
IHRoYXQgcGFja2V0IGlzIHdhc3RlZCBkYXRhLCBidXQgbm90IGFuIGVycm9yLiZuYnNwOyBIb3dl
dmVyLCBpdCBtaWdodCBub3QgYmUgdG90YWxseSBjbGVhciB0byBhcHBsaWNhdGlvbiBkZXNpZ25l
cnMgdGhhdCwgd2hpbGUgQUNLcyBjYW4gdGVsbCB5b3Ugd2hpY2ggZGF0YWdyYW1zIGRlZmluaXRl
bHkgZGlkIGFycml2ZSwgdGhleSBjYW4gbmV2ZXIgdGVsbCB5b3Ugd2hpY2ggb25lcyBkZWZpbml0
ZWx5IGRpZG7igJl0LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5CdXQgaXQgc291bmRzIGxpa2Ug
d2hlcmUgdGhpcyBpcyBnb2luZyBpcyB0aGUgcmVhbGl6YXRpb24gdGhhdCB5b3UgaGF2ZSB0byBo
YXZlIGZsb3cgY29udHJvbCBpZiB5b3XigJlyZSBnb2luZyB0byBwcm9oaWJpdCB0aGUgcmVtb3Rl
IGltcGxlbWVudGF0aW9uIGZyb20gZHJvcHBpbmcgZGF0YWdyYW1zIGFmdGVyIEFDS2luZyB0aGVt
OyBidXQgaWYgeW91IGRvIGFsbG93IHRoZSBpbXBsZW1lbnRhdGlvbiB0byBkbyB0aGF0LA0KIHRo
ZW4gQUNLcyB0ZWxsIHlvdSBub3RoaW5nIGNvbmNyZXRlIGFib3V0IERBVEFHUkFNcyB0aGF0IG1p
Z2h0IGhhdmUgYmVlbiBpbiB0aG9zZSBwYWNrZXRzLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9y
ZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGlu
IDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8L2I+IFFVSUMgJmx0O3F1
aWMtYm91bmNlc0BpZXRmLm9yZyZndDsgPGI+T24gQmVoYWxmIE9mIDwvYj4NCkx1YmFzaGV2LCBJ
Z29yPGJyPg0KPGI+U2VudDo8L2I+IE1vbmRheSwgT2N0b2JlciAyOSwgMjAxOCA0OjI5IFBNPGJy
Pg0KPGI+VG86PC9iPiBUb21teSBQYXVseSAmbHQ7dHBhdWx5QGFwcGxlLmNvbSZndDs7IEphbmEg
SXllbmdhciAmbHQ7anJpLmlldGZAZ21haWwuY29tJmd0Ozxicj4NCjxiPkNjOjwvYj4gSWFuIFN3
ZXR0ICZsdDtpYW5zd2V0dEBnb29nbGUuY29tJmd0OzsgUVVJQyBXRyAmbHQ7cXVpY0BpZXRmLm9y
ZyZndDs7IE1hcnRpbiBUaG9tc29uICZsdDttYXJ0aW4udGhvbXNvbkBnbWFpbC5jb20mZ3Q7PGJy
Pg0KPGI+U3ViamVjdDo8L2I+IFJFOiBmbG93IGNvbnRyb2wgYW5kIERBVEFHUkFNPG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mZ3Q7IEFDSyB0byBhIHBhY2tldCBjb250
YWluaW5nIGEgREFUQUdSQU0gZnJhbWUgbWVhbnM6PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj4mZ3Q7IC0gVGhlIHBhY2tldCBtYWRlIGl0IGFjcm9zcyB0aGUgbmV0d29yayB0
byB0aGUgUVVJQyBlbmRwb2ludCBvbiB0aGUgb3RoZXIgc2lkZTxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+Jmd0OyAtIFRoZSBRVUlDIGltcGxlbWVudGF0aW9uIHdpbGwgZGVs
aXZlciB0aGUgREFUQUdSQU0gZnJhbWUgdG8gYXBwbGljYXRpb24gKGl0IHdvbid0IGRyb3AgaXQg
bG9jYWxseSk8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZndDs8bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZndDsgRG9lcyB0aGF0IG1ha2Ug
c2Vuc2U/PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoaXMgb25seSBtYWtlcyBzZW5zZSwgaWYg
dGhlcmUgaXMgYW4gZWZmZWN0aXZlIGZsb3cgY29udHJvbCBmb3IgREFUQUdSQU1zLiZuYnNwOyBU
aGUgc3BlYyBzaG91bGQgYmUgaW1wbGVtZW50YWJsZSBieSBwb2xsL3JlYWQgUVVJQyBpbXBsZW1l
bnRhdGlvbnMgYXMgd2VsbCBhcyBieSBjYWxsYmFjay1vbi1uZXR3b3JrLXJlY2VpdmUtdGhyZWFk
IGltcGxlbWVudGF0aW9ucy4mbmJzcDsgVW5sZXNzIHRoZXJlIGlzIGFuIGVmZmVjdGl2ZQ0KIGZs
b3cgY29udHJvbCwgYSBidWZmZXJpbmcgUVVJQyBpbXBsZW1lbnRhdGlvbiBtdXN0IGJlIGFibGUg
dG8gZGlzY2FyZCBEQVRBR1JBTXMsIGlmIHRoZSByZWNlaXZlciBhcHAgaXMgbm90IGNhdGNoaW5n
IHVwLiZuYnNwOyBUaGUgcmVjZWl2ZXIgd291bGQgdGhlbiBoYXZlIHRvIGlnbm9yZSBhbGwgbm9u
LURBVEFHUkFNIGZyYW1lcyBpbiB0aGF0IHBhY2tldCwgc2luY2UgaXQgd291bGQgYmUgdW5hYmxl
IHRvIEFDSyB0aGUgcGFja2V0LiZuYnNwOyBJZiB0aGUgcmVjZWl2ZXINCiBpcyBwcm9jZXNzaW5n
IERBVEFHUkFNcyBhbmQgU1RSRUFNcyBhdCBkaWZmZXJlbnQgc3BlZWRzLCBkZWxpYmVyYXRlIGRp
c2NhcmRzIG9mIHBhY2tldHMgY29udGFpbmluZyBEQVRBR1JBTXMgd291bGQgaW50ZXJmZXJlIHdp
dGggdGhlIGNvbmdlc3Rpb24gY29udHJvbCwgZWZmZWN0aXZlbHkgSE9MIGJsb2NraW5nIFNUUkVB
TXMuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFuIGVmZmVjdGl2ZSBmbG93IGNvbnRyb2wgcmVx
dWlyZXMgc2VuZGVyIGFuZCByZWNlaXZlciB0byBzeW5jaHJvbml6ZSB0aGVpciB2aWV3IG9mIHRo
ZSBmbG93IGNvbnRyb2wgY291bnRlciAoTUFYX0RBVEEgZm9yIGNvbm5lY3Rpb24gZmxvdyBjb250
cm9sKS4mbmJzcDsgUmVseWluZyBvbiBBQ0tzIGlzIHZlcnkgaGFyZCwgc2luY2UgdGhlIHJlY2Vp
dmVyIGNhbm5vdCBrbm93IGhvdyBtdWNoIGRhdGEgdGhlIHNlbmRlcg0KIGhhcyBzZW50ICh1bmxl
c3MgdGhlIHNlbmRlciBpcyBleHBsaWNpdCBhYm91dCBpdCkuPG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPklmIGZsb3cgY29udHJvbCBmb3IgREFUQUdSQU1zIGlzIGRlc2lyZWQsIHlvdSBjYW4gdXNl
IG1lY2hhbmljcyBzdWNoIGFzIGluDQo8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0
bWwvZHJhZnQtbHViYXNoZXYtcXVpYy1wYXJ0aWFsLXJlbGlhYmlsaXR5LTAyIj4NCmh0dHBzOi8v
dG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1sdWJhc2hldi1xdWljLXBhcnRpYWwtcmVsaWFiaWxp
dHktMDI8L2E+IG9yIDxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1s
dWJhc2hldi1xdWljLXBhcnRpYWwtcmVsaWFiaWxpdHktMDMiPg0KaHR0cHM6Ly90b29scy5pZXRm
Lm9yZy9odG1sL2RyYWZ0LWx1YmFzaGV2LXF1aWMtcGFydGlhbC1yZWxpYWJpbGl0eS0wMzwvYT4g
KDxhIGhyZWY9Imh0dHBzOi8vZ2l0aHViLmNvbS9pZ29ybG9yZC9kcmFmdC1sdWJhc2hldi1xdWlj
LXBhcnRpYWwtcmVsaWFiaWxpdHkiPmh0dHBzOi8vZ2l0aHViLmNvbS9pZ29ybG9yZC9kcmFmdC1s
dWJhc2hldi1xdWljLXBhcnRpYWwtcmVsaWFiaWxpdHk8L2E+KS4mbmJzcDsgKFRoaXMgd291bGQg
YmUgdHJlYXRpbmcgREFUQUdSQU1zDQogYXMgYmVsb25naW5nIHRvIGEgcGFydGlhbGx5IHJlbGlh
YmxlIHN0cmVhbSwgb3Igc3RyZWFtcy4mbmJzcDsgRXhjZXB0IHlvdSB3b3VsZCBub3QgbmVlZCB0
byBlbnN1cmUgb3JkZXJpbmcgb2YgREFUQUdSQU1zIGluIHRoYXQgc3RyZWFtLik8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHVsIHN0
eWxlPSJtYXJnaW4tdG9wOjBpbiIgdHlwZT0iZGlzYyI+DQo8bGkgY2xhc3M9Ik1zb0xpc3RQYXJh
Z3JhcGgiIHN0eWxlPSJtYXJnaW4tbGVmdDowaW47bXNvLWxpc3Q6bDEgbGV2ZWwxIGxmbzMiPkln
b3I8bzpwPjwvbzpwPjwvbGk+PC91bD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRp
bmc6MGluIDBpbiAwaW4gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiBUb21teSBQYXVseSAmbHQ7PGEgaHJl
Zj0ibWFpbHRvOnRwYXVseUBhcHBsZS5jb20iPnRwYXVseUBhcHBsZS5jb208L2E+Jmd0Ow0KPGJy
Pg0KPGI+U2VudDo8L2I+IE1vbmRheSwgT2N0b2JlciAyOSwgMjAxOCA0OjAxIFBNPGJyPg0KPGI+
VG86PC9iPiBKYW5hIEl5ZW5nYXIgJmx0OzxhIGhyZWY9Im1haWx0bzpqcmkuaWV0ZkBnbWFpbC5j
b20iPmpyaS5pZXRmQGdtYWlsLmNvbTwvYT4mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBJYW4gU3dldHQg
Jmx0OzxhIGhyZWY9Im1haWx0bzppYW5zd2V0dEBnb29nbGUuY29tIj5pYW5zd2V0dEBnb29nbGUu
Y29tPC9hPiZndDs7IFFVSUMgV0cgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWljQGlldGYub3JnIj5x
dWljQGlldGYub3JnPC9hPiZndDs7IE1hcnRpbiBUaG9tc29uICZsdDs8YSBocmVmPSJtYWlsdG86
bWFydGluLnRob21zb25AZ21haWwuY29tIj5tYXJ0aW4udGhvbXNvbkBnbWFpbC5jb208L2E+Jmd0
Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogZmxvdyBjb250cm9sIGFuZCBEQVRBR1JBTTxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SGkgSmFuYSw8bzpwPjwvbzpwPjwv
cD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkknbSBub3Qgc3VnZ2VzdGluZyBhbnkg
Y2hhbmdlcyB0byB3aGVuIHRoZSBwYWNrZXQgZ2V0cyBhY2snZWTigJRzcGVjaWZpY2FsbHksIEkg
d2FzIHJlc3BvbmRpbmcgdG8gTWFydGluJ3MgaHlwb3RoZXRpY2FsIG9mIGhhdmluZyBhbiBBQ0sg
dG8gYSBEQVRBR1JBTSBmcmFtZSBtZWFuaW5nIHRoYXQgdGhlIGFwcGxpY2F0aW9uIGhhZCBwcm9j
ZXNzZWQgdGhlIGZyYW1lLiBNeSBpbXByZXNzaW9uIGlzIHRoYXQgdGhlIEFDSw0KIHRvIGEgcGFj
a2V0IGNvbnRhaW5pbmcgYSBEQVRBR1JBTSBmcmFtZSBtZWFuczo8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi0gVGhlIHBhY2tldCBtYWRlIGl0IGFj
cm9zcyB0aGUgbmV0d29yayB0byB0aGUgUVVJQyBlbmRwb2ludCBvbiB0aGUgb3RoZXIgc2lkZTxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+LSBUaGUg
UVVJQyBpbXBsZW1lbnRhdGlvbiB3aWxsIGRlbGl2ZXIgdGhlIERBVEFHUkFNIGZyYW1lIHRvIGFw
cGxpY2F0aW9uIChpdCB3b24ndCBkcm9wIGl0IGxvY2FsbHkpPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkRvZXMgdGhhdCBtYWtlIHNlbnNlPzxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IYXZp
bmcgYSBzZXBhcmF0ZSBvdXRzdGFuZGluZyBkYXRhIGxpbWl0IGZvciB0aGUgREFUQUdSQU0gJnF1
b3Q7c3RyZWFtJnF1b3Q7IGlzIGFuIGludGVyZXN0aW5nIHNvbHV0aW9uIHRvIHRoZSBzcGFjZS4g
SXQgd291bGQgdGhlbiBoYXZlIHRoZSBuaWNlIHByb3BlcnR5IG9mIG5vdCBsb29raW5nIGxpa2Ug
dHJhZGl0aW9uYWwgZmxvdyBjb250cm9sLiBJdCBjb3VsZCBldmVuIGJlIG1lYXN1cmVkIGluIG51
bWJlciBvZiBmcmFtZXMsDQogcmF0aGVyIHRoYW4gYnl0ZXMgKGRlcGVuZGluZyBvbiB3aGF0IHRo
ZSBsaW1pdGluZyBmYWN0b3JzIGFyZSkuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYW5rcyw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRvbW15PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1i
b3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIE9jdCAyOSwgMjAx
OCwgYXQgMTI6MzcgUE0sIEphbmEgSXllbmdhciAmbHQ7PGEgaHJlZj0ibWFpbHRvOmpyaS5pZXRm
QGdtYWlsLmNvbSI+anJpLmlldGZAZ21haWwuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Ub21teSw8bzpwPjwvbzpwPjwvcD4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkNoYW5naW5nIHRoZSBzZW1hbnRpY3Mgb2Yg
YW4gYWNrbm93bGVkZ21lbnQgdG8gaW5jbHVkZSBkZWxpdmVyeSB1cCB0byB0aGUgYXBwbGljYXRp
b24gaXMgYSBmdW5kYW1lbnRhbCBjaGFuZ2UgdG8gdGhlIFFVSUMgbWFjaGluZXJ5LCBhbmQgaXQg
ZG9lc24ndCB3b3JrLiBGaXJzdCwgYW4gQUNLIGZyYW1lIGFja25vd2xlZGdlcyBwYWNrZXRzLCBh
bmQgeW91IGNhbid0IGhhdmUgZGlmZmVyZW50IHNlbWFudGljcyBvZg0KIGFuIGFja25vd2xlZGdt
ZW50IGZvciBkaWZmZXJlbnQgZnJhbWVzIHRoYXQgYXJlIGNhcnJpZWQgaW4gdGhlIHNhbWUgcGFj
a2V0LiBTZWNvbmQsIGl0IGludGVyZmVyZXMgd2l0aCBSVFQgbWVhc3VyZW1lbnQsIGFuZCBpdCBj
b25mbGF0ZXMgZmxvdyBjb250cm9sIHdpdGggY29uZ2VzdGlvbiBjb250cm9sLCB3aGljaCBnZXRz
IG1lc3N5LiAoVGhpcyBjb25mbGF0aW9uIGlzIGFuIGludGVyZXN0aW5nIHByb2JsZW0gdG8gY29u
c2lkZXIgdGhlb3JldGljYWxseSwNCiBidXQgbm90IG9uZSBmb3IgdXMgYXQgdGhpcyB0aW1lIElN
Ty4pPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PkkgYW0gd29uZGVyaW5nIGlmIGFwcGx5aW5nIGEgc3RyZWFtLWxldmVsIGZsb3cgY29udHJvbCBm
b3IgREFUQUdSQU1zIG1ha2VzIHNlbnNlIGluc3RlYWQuIE1lYW5pbmcgdGhhdCB5b3UgdHJlYXQg
REFUQUdSQU1zIGFzIGEgc2VwYXJhdGUgc3RyZWFtIGZvciBmbG93IGNvbnRyb2wgcHVycG9zZXMu
IFlvdSBtaWdodCBiZW5lZml0IGZyb20gaGF2aW5nIGFuIG9mZnNldCBpbiB0aGUgREFUQUdSQU0g
ZnJhbWUgZm9yDQogdGhpcyBwdXJwb3NlLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4tIGphbmE8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gTW9uLCBPY3QgMjksIDIwMTggYXQgODoyMSBB
TSBUb21teSBQYXVseSAmbHQ7PGEgaHJlZj0ibWFpbHRvOnRwYXVseUBhcHBsZS5jb20iPnRwYXVs
eUBhcHBsZS5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2Nr
cXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7
cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tdG9wOjUu
MHB0O21hcmdpbi1yaWdodDowaW47bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+SGkgTWFydGluLCBJYW4sPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5ZZXMsIHZlcnkgZ29vZCBwb2ludHMhPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk15IHRlbmRlbmN5IHdvdWxk
IGJlIHRvIHByZWZlciB3aGF0IElhbidzIGltcGxlbWVudGF0aW9uIGRvZXMgb2YgcGFzc2luZyB0
aGVzZSBEQVRBR1JBTSBmcmFtZXMgdXAgaW1tZWRpYXRlbHkgdG8gdGhlIGFwcGxpY2F0aW9uLiBJ
IGRvbid0IHRoaW5rIHRoYXQgdGhlIGFja25vd2xlZGdtZW50IG5lZWRzIHRvIGluZGljYXRlIHRo
YXQgdGhlIGZyYW1lIHdhcyBwcm9jZXNzZWQgYnkgdGhlIGFwcGxpY2F0aW9uLCBidXQNCiBtZXJl
bHkgdGhhdCBpdCBoYXMgYmVlbiBkZWxpdmVyZWQgdG8gdGhlIGFwcGxpY2F0aW9uICh0aGF0IGlz
LCB0aGUgYXBwbGljYXRpb24gZG9lc24ndCBnZXQgdG8gZG8gYW55dGhpbmcgd2l0aCB0aGUgZnJh
bWUgdGhhdCBjYW4gaW5mbHVlbmNlIHRoZSBhY2tub3dsZWRnbWVudCkuPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoZSBjdXJyZW50IGRyYWZ0
IGluZGljYXRlcyB0aGF0IHRoZSBjb250ZW50IG9mIHRoZSBEQVRBR1JBTSBmcmFtZXMgY29udHJp
YnV0ZXMgdG8gdGhlIGxpbWl0IHVzZWQgZm9yJm5ic3A7TUFYX0RBVEEsIGFuZCB0aGF0IGlmIHRo
YXQgYW1vdW50IGlzIHJlYWNoZWQsIHRoZSBmcmFtZXMgYXJlIGJsb2NrZWQgYWxvbmcgd2l0aCBT
VFJFQU0gZGF0YS4gSSB0aGluayB0aGlzIHdvcmtzIGZpbmUgZm9yIHRoZSBzZW5kZXIsIHdoaWxl
DQogdGhlIHJlY2VpdmVyIGdldHMgaW50byB0aGUgZGlzY3Vzc2lvbiB5b3UgcHJlc2VudC4gT24g
dGhlIHNlbmRlciBzaWRlLCByZWFjaGluZyBNQVhfREFUQSBjb3VsZCBtZWFuIGRyb3BwaW5nIHRo
ZSBEQVRBR1JBTSBmcmFtZXMgd2hlbiB1bmFibGUgdG8gc2VuZCBtb3JlIChhbmQgc2VuZGluZyBC
TE9DS0VEIGluc3RlYWQpLiBTaW5jZSB0aGUgZnJhbWVzIGFyZSB1bnJlbGlhYmxlLCB0aGV5IGNh
biBiZSBkcm9wcGVkIGluIHRoaXMgc2l0dWF0aW9uDQogd2l0aG91dCB2aW9sYXRpbmcgdGhlIEFQ
SSBjb250cmFjdC4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+T24gdGhlIHJlY2VpdmVyIHNpZGUsIEkgYWdyZWUgdGhhdCBxdWV1aW5n
IHRoZSBEQVRBR1JBTSBmcmFtZXMgdG8gbGV0IHRoZSBhcHBsaWNhdGlvbiBkcml2ZSBmbG93IGNv
bnRyb2wgaW4gdGhlIHdheSBpdCBkb2VzIGZvciBTVFJFQU0gZnJhbWVzIGFkZHMgY29tcGxleGl0
eSBhbmQgZGltaW5pc2hlcyB0aGUgdXRpbGl0eSBvZiB0aGUgZnJhbWUgYW5kIEFDS3MuLiBIb3dl
dmVyLCBJIGNhbiBpbWFnaW5lIHRha2luZw0KIGEgZmFpcmx5IHNpbXBsaXN0aWMgYXBwcm9hY2gg
aW4gd2hpY2ggdGhlIGRhdGEgbGltaXQgaXMgYXV0b21hdGljYWxseSBpbmNyZWFzZWQgdXBvbiBy
ZWNlcHRpb24gb2YgdGhlIGZyYW1lIChhbmQgdGhlIGZyYW1lIGlzIGltbWVkaWF0ZWx5IHBhc3Nl
ZCB0byB0aGUgYXBwbGljYXRpb24pLiBUaGlzIGFsbG93cyB0aGUgaW5pdGlhbF9tYXhfZGF0YSB0
byBwdXQgYSBjYXAgb24gdGhlIGFtb3VudCBvZiBkYXRhIGluIGEgZ2l2ZW4gZmxpZ2h0IG9mIERB
VEFHUkFNUywNCiBhbmQgYWxsb3cgdGhlIHNpemUgb2YgYSBmbGlnaHQgb2YgREFUQUdSQU0gZnJh
bWVzIHRvIGJlIGxpbWl0ZWQgYnkgdGhlIGFtb3VudCBvZiByb29tIGxlZnQgb3ZlciBmcm9tIFNU
UkVBTSBkYXRhIHRoYXQgbWF5IGJlIGNvbnN1bWluZyB0aGUgY29ubmVjdGlvbi13aWRlIGZsb3cg
Y29udHJvbC4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+UGVyaGFwcyB0aGlzIGFwcHJvYWNoIG5lZWRzIGEgY2xlYXJlciBuYW1lIG90
aGVyIHRoYW4gJnF1b3Q7ZmxvdyBjb250cm9sJnF1b3Q7LCBzaW5jZSBpdCBoYXMgYSBzb21ld2hh
dCBkaWZmZXJlbnQgbWVhbmluZyBpbiBlZmZlY3QuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFzIGZvciBBQ0tzLCBpZiB3ZSBuZXZlciBkaXNj
YXJkIG9uIHRoZSByZWNlaXZlciBzaWRlLCB0aGUgQUNLIGlzIHByZXR0eSB1c2VmdWwgZm9yIGRl
dGVjdGluZyBpZiB0aGVyZSB3YXMgbmV0d29yay1iYXNlZCBwYWNrZXQgbG9zcy48bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhhbmtzLDxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VG9tbXkmbmJz
cDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gT2N0IDI5LCAyMDE4LCBhdCA1OjMyIEFN
LCBJYW4gU3dldHQgJmx0OzxhIGhyZWY9Im1haWx0bzppYW5zd2V0dEBnb29nbGUuY29tIiB0YXJn
ZXQ9Il9ibGFuayI+aWFuc3dldHRAZ29vZ2xlLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+R29vZCBjYXRjaCBNYXJ0aW4sIEkg
bWlzc2VkIHRoYXQgaW4gdGhlIGRyYWZ0IGFzIHdlbGwsIGFuZCBJIGFsc28gdGhpbmsgaXQncyBp
bXBvc3NpYmx5IHdpdGggdGhlIHByb3Bvc2VkIGRlc2lnbi48bzpwPjwvbzpwPjwvcD4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFuZCB5ZXMsIEkgdGhpbmsgTWFydGluJ3MgcHJvcG9z
ZWQgc29sdXRpb24gaXMgbGlrZWx5IHRoZSBvbmx5IHByYWN0aWNhbCBvbmUuJm5ic3A7IEluIG15
IGltcGxlbWVudGF0aW9uLCB0aGUgZnJhbWUgaXMgcGFzc2VkIHVwIHRvIHRoZSBhcHBsaWNhdGlv
biBpbW1lZGlhdGVseSwgc28gdGVjaG5pY2FsbHkgUVVJQyBwcm9jZXNzZWQgaXQsIGFuZCBpdCdz
IHRoZSBhcHBsaWNhdGlvbidzIGpvYiB0byBkZWNpZGUgd2hhdA0KIHRvIGRvIHdpdGggaXQuPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIE1v
biwgT2N0IDI5LCAyMDE4IGF0IDE6MTYgQU0gTWFydGluIFRob21zb24gJmx0OzxhIGhyZWY9Im1h
aWx0bzptYXJ0aW4udGhvbXNvbkBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5tYXJ0aW4udGhv
bXNvbkBnbWFpbC5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJs
b2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPkhpIFRvbW15
LDxicj4NCjxicj4NCllvdXIgc2xpZGVzIC0gJmx0OzxhIGhyZWY9Imh0dHBzOi8vdXJsZGVmZW5z
ZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwcy0zQV9fZ2l0aHViLmNvbV9xdWljd2dfd2ct
MkRtYXRlcmlhbHNfYmxvYl9tYXN0ZXJfaWV0ZjEwM19JRVRGMTAzLTJEUVVJQy0yRERhdGFncmFt
LnBkZiZhbXA7ZD1Ed01GYVEmYW1wO2M9OTZaYlpaY2FNRjR3MEY0anBONkxaZyZhbXA7cj1Eam4z
YlE1dU5KRFBNXzJza2ZMM3JXMXR6Y0l4eWpVWmRuX201NUtQbWxvJmFtcDttPS1KQVZ5S0s0THJE
RlVuLVR6STk2WkZsckZaWW96ZzRHRlZ0dG5qSWpHZGcmYW1wO3M9dHFVUVpXLWhQMEd3Wjd4MW90
UGtTWXBBM2F4R1Zpell1MGE0SmxMb3U2USZhbXA7ZT0iIHRhcmdldD0iX2JsYW5rIj5odHRwczov
L2dpdGh1Yi5jb20vcXVpY3dnL3dnLW1hdGVyaWFscy9ibG9iL21hc3Rlci9pZXRmMTAzL0lFVEYx
MDMtUVVJQy1EYXRhZ3JhbS5wZGY8L2E+Jmd0Ozxicj4NCi0gc2F5IHRoYXQgREFUQUdSQU0gZnJh
bWVzIHJlc3BlY3QgY29ubmVjdGlvbi1sZXZlbCBmbG93IGNvbnRyb2wuJm5ic3A7IEk8YnI+DQpt
aXNzZWQgdGhhdCBpbiB0aGUgZHJhZnQsIGFuZCBJIGRvbid0IGtub3cgaG93IHRoZXkgY2FuIGRv
IHRoYXQgaW4gdGhlPGJyPg0KZmFjZSBvZiBwYWNrZXQgbG9zcywgZXNwZWNpYWxseSB3aGVuIHlv
dSBkb24ndCBuZWNlc3NhcmlseSByZXRyYW5zbWl0PGJyPg0KbG9zdCBEQVRBR1JBTSBmcmFtZXMu
PGJyPg0KPGJyPg0KRm9yIHRoYXQgdG8gd29yaywgeW91IHdvdWxkIG5lZWQgYSBidW5jaCBtb3Jl
IG1hY2hpbmVyeSB0byBtYWtlIHRoZTxicj4NCmNvbm5lY3Rpb24tbGV2ZWwgZmxvdyBjb250cm9s
IHN5bmMgYmV0d2VlbiBlbmRwb2ludHMgaW4gdGhlIGNhc2UgdGhhdDxicj4NCnBhY2tldHMgYXJl
IGxvc3QuJm5ic3A7IEEgZGlzYWdyZWVtZW50IGFib3V0IGhvdyBtdWNoIGZsb3cgY29udHJvbCBp
cyB1c2VkPGJyPg0KY2F1c2VzIHRoaW5ncyB0byBicmVhayBkb3duIGJhZGx5LiZuYnNwOyBJYW4g
YW5kIEkgZGlzY3Vzc2VkIHRoaXMgcG9pbnQgYXQ8YnI+DQp0aGUgbGFzdCBtZWV0aW5nIGFuZCBx
dWlja2x5IGFncmVlZCB0aGF0IHdoaWxlIGl0IG1pZ2h0IGJlIG5pY2UgdG88YnI+DQpoYXZlIGZs
b3cgY29udHJvbCBmb3IgdGhpcyBzdHVmZiwgdGhlIGluY3JlYXNlIGluIGNvbXBsZXhpdHkgaXM8
YnI+DQpjb25zaWRlcmFibGUgYW5kIChhdCB0aGUgdGltZSkgd2UgdGhvdWdodCBpdCB3b3VsZG4n
dCBiZSB3b3J0aCBpdC48YnI+DQo8YnI+DQpUaGUgcHJvYmxlbSB0aGF0IGludHJvZHVjZXMgaXMg
dGhhdCB5b3UgY291bGQgZW5kIHVwIGhhdmluZyB0b28gbWFueTxicj4NCkRBVEFHUkFNIGZyYW1l
cyBhcnJpdmUuJm5ic3A7IFRoZSByZWNlaXZlciBoYXMgdG8gZHJvcCBzb21ldGhpbmcgYXQgdGhl
PGJyPg0KcG9pbnQgdGhhdCBpdCBjYW4ndCBoYW5kbGUgdGhlbS4mbmJzcDsgQW5kIHdlIHNheSB0
aGF0IHdoZW4geW91IGFja25vd2xlZGdlPGJyPg0Kc29tZXRoaW5nLCB5b3UgcHJvY2Vzc2VkIGl0
LiZuYnNwOyBUaGF0J3MgdHJpY2t5Ljxicj4NCjxicj4NCkl0IG1pZ2h0IGJlIGVhc2llciB0byBz
YXkgdGhhdCBhIFFVSUMgYWNrbm93bGVkZ21lbnQgZm9yIGEgREFUQUdSQU08YnI+DQpmcmFtZSBk
b2Vzbid0IG1lYW4gdGhhdCBpdCB3YXMgcmVjZWl2ZWQgYW5kIHByb2Nlc3NlZCBieSBhbjxicj4N
CmFwcGxpY2F0aW9uLiZuYnNwOyBBbiBlbmRwb2ludCBtaWdodCBkaXNjYXJkIHRoZXNlIGZyYW1l
cyBiZWZvcmUgcGFzc2luZzxicj4NCnRoZW0gb24gdG8gYXBwbGljYXRpb25zIGlmIGl0IGRvZXNu
J3QgaGF2ZSBzcGFjZS4mbmJzcDsgSW4gb3RoZXIgd29yZHMsPGJyPg0KYWNrbm93bGVkZ21lbnQg
b2YgREFUQUdSQU0gbWVhbnMgdGhhdCBRVUlDIGdvdCBpdCwgbm90IHRoYXQgdGhlPGJyPg0KYXBw
bGljYXRpb24gZ290IGl0LiZuYnNwOyBTYWRseSwgdGhhdCBtZWFucyB0aGF0IHRoZSBRVUlDIGFj
a25vd2xlZGdtZW50PGJyPg0KbWFjaGluZXJ5IGRvZXNuJ3QgaGVscCB0aGUgYXBwbGljYXRpb24g
dGhhdCB1c2VzIERBVEFHUkFNIGFsbCB0aGF0PGJyPg0KbXVjaC4mbmJzcDsgQWxzbywgdGhlIGxv
d2VyIGJvdW5kIG9uIHJlbGlhYmlsaXR5IGlzIDAsIHdoaWNoIGlzbid0IHRoZSBiZXN0PGJyPg0K
dGhpbmcgZXZlci48YnI+DQo8YnI+DQpIYXJkIGNob2ljZXMsIEkga25vdy4mbmJzcDsgSSBkb24n
dCBoYXZlIGEgZ29vZCBkZXNpZ24gZm9yIG1haW50YWluaW5nPGJyPg0KY29ubmVjdGlvbi1sZXZl
bCBmbG93IGNvbnRyb2wgKG9yIGFueSBiYWNrIHByZXNzdXJlIG1lY2hhbmlzbSB3aXRoPGJyPg0K
ZXF1aXZhbGVudCBwcm9wZXJ0aWVzKSB0aGF0IGRvZXNuJ3QgYWRkIGJvdGggY29tcGxleGl0eSBh
bmQgb3ZlcmhlYWQuPGJyPg0KPGJyPg0KQ2hlZXJzLDxicj4NCk1hcnRpbjxvOnA+PC9vOnA+PC9w
Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_CY4PR22MB098366E6A90123689A855766DACE0CY4PR22MB0983namp_--


From nobody Wed Oct 31 22:59:16 2018
Return-Path: <w@1wt.eu>
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 1693D130DFA for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 22:59:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 ymqZM2VtcQSG for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 22:59:12 -0700 (PDT)
Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 9998C124C04 for <quic@ietf.org>; Wed, 31 Oct 2018 22:59:10 -0700 (PDT)
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id wA15wxru031911; Thu, 1 Nov 2018 06:58:59 +0100
Date: Thu, 1 Nov 2018 06:58:59 +0100
From: Willy Tarreau <w@1wt.eu>
To: Mike Bishop <mbishop@evequefou.be>
Cc: "Roy T. Fielding" <fielding@gbiv.com>, Mark Nottingham <mnot@mnot.net>, IETF QUIC WG <quic@ietf.org>
Subject: Re: Identifying our deliverables
Message-ID: <20181101055859.GB31884@1wt.eu>
References: <578BB4EC-421E-4B21-AA14-B545A41754C8@mnot.net> <873C0B44-EE49-4CCF-97A2-E71DB43298E2@gbiv.com> <CY4PR22MB0983CAC48213F5F748D8920ADACE0@CY4PR22MB0983.namprd22.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CY4PR22MB0983CAC48213F5F748D8920ADACE0@CY4PR22MB0983.namprd22.prod.outlook.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/VVjnbsFbH1gchi1wR1OKkqtuwt0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Nov 2018 05:59:14 -0000

On Thu, Nov 01, 2018 at 03:32:21AM +0000, Mike Bishop wrote:
> In theory, all Standards-track RFCs reflect IETF consensus, not just the
> consensus of a single working group, so I don't see HTTP as having "naming
> rights" per se.  But in general, I think the QUIC WG should have the
> consensus of the HTTP WG to call its output "HTTP/3."  And Mark's proposal
> reflects exactly that, with a heads-up to the HTTP list that we'll be
> discussing in Bangkok.  Along similar lines, I think we'd want to send the
> HTTP doc to both working groups for WGLC, either in parallel or in sequence.
> If both WGs have consensus on the documents, I don't see this as a barrier.

Also we must not dismiss the fact that there's a significant overlap between
the participants of the two WGs, which definitely is an indication of the
strong link between HTTP and QUIC in the way these protocols are designed.
For me it's exactly similar to how SPDY became HTTP/2, those of us who were
following spdy-dev saw a significant drop in activity on this WG once it was
adopted as the basis for H2. Here with QUIC the main justification to have
had a separate WG is that it covers additional areas such as the transport
whose design was out of the scope of the HTTP WG.

Willy

