Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 7E7D0130DC8
 for <quic-issues@ietfa.amsl.com>; Mon, 19 Nov 2018 05:58:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.066
X-Spam-Level: 
X-Spam-Status: No, score=-7.066 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_IMAGE_ONLY_28=1.404,
 HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5,
 SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
 header.d=github.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 09d8MZQLU9xS for <quic-issues@ietfa.amsl.com>;
 Mon, 19 Nov 2018 05:58:49 -0800 (PST)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 4EF42130DC7
 for <quic-issues@ietf.org>; Mon, 19 Nov 2018 05:58:49 -0800 (PST)
Date: Mon, 19 Nov 2018 05:58:47 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1542635927;
 bh=gEYmQas+buzjzdmYfhFQVx0EpiGMg+BtAzBK/0rsysE=;
 h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=bwzEGT/qKFoX4Err1Hy/nVmVS/Vo5csMksd3jC8JTi0Hypskh6+geGIeX3KGFF/Ui
 6ynguYVAJ0hc2bE4IuCRgluWqNmcnzQzUEvMu30lyEPxoRHTTjYc62U2oarM6wyS9i
 vgJ4IbhuAnKgIdwuU6aKKOkBB50B3K4G+tagFI2Q=
From: Nicolas Kuhn <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abedd34a807fdd39130751e57cf6b8ab9f73baafbb92cf00000001180a839792a163ce01de5e70@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/commit/a13266667d30e1fd872375675aab96bf76038f06/31350384@github.com>
In-Reply-To: <quicwg/base-drafts/commit/a13266667d30e1fd872375675aab96bf76038f06@github.com>
References: <quicwg/base-drafts/commit/a13266667d30e1fd872375675aab96bf76038f06@github.com>
Subject: Re: [quicwg/base-drafts] Add the TLS bits, refine some of the
 transport bits (a132666)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5bf2c1972055d_650a3f9f61ed45b4228350";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: NicoKos
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/0ZlCrp3gde4T_ZS6WDl1SBrKrRg>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG
 <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>,
 <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>,
 <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2018 13:58:50 -0000


----==_mimepart_5bf2c1972055d_650a3f9f61ed45b4228350
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Having only one spin bit for in-network measurements make it very hard to identify issues in the network. To do so, you may need loss and latency measurements that can hardly be achieved with a single bit. What is the rationale behind including these bits under the the header protection ?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/commit/a13266667d30e1fd872375675aab96bf76038f06#commitcomment-31350384
----==_mimepart_5bf2c1972055d_650a3f9f61ed45b4228350
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>Having only one spin bit for in-network measurements make it very hard=
 to identify issues in the network. To do so, you may need loss and laten=
cy measurements that can hardly be achieved with a single bit. What is th=
e rationale behind including these bits under the the header protection ?=
</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />You are receiving this because you are subscribed to this thre=
ad.<br />Reply to this email directly, <a href=3D"https://github.com/quic=
wg/base-drafts/commit/a13266667d30e1fd872375675aab96bf76038f06#commitcomm=
ent-31350384">view it on GitHub</a>, or <a href=3D"https://github.com/not=
ifications/unsubscribe-auth/AWbkqwDv0p-HszEts9JSrkGiHFLwt1yEks5uwrkXgaJpZ=
M4Yl26y">mute the thread</a>.<img src=3D"https://github.com/notifications=
/beacon/AWbkq2zmVC8_T25IaX9w2Sf_i2mJCFYsks5uwrkXgaJpZM4Yl26y.gif" height=3D=
"1" width=3D"1" alt=3D"" /></p>
<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_versio=
n":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name"=
:"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"=
quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"http=
s://assets-cdn.github.com/images/email/message_cards/header.png","avatar_=
image_url":"https://assets-cdn.github.com/images/email/message_cards/avat=
ar.png","action":{"name":"Open in GitHub","url":"https://github.com/quicw=
g/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@Nico=
Kos on a132666: Having only one spin bit for in-network measurements make=
 it very hard to identify issues in the network. To do so, you may need l=
oss and latency measurements that can hardly be achieved with a single bi=
t. What is the rationale behind including these bits under the the header=
 protection ?"}],"action":{"name":"View Commit","url":"https://github.com=
/quicwg/base-drafts/commit/a13266667d30e1fd872375675aab96bf76038f06#commi=
tcomment-31350384"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/commit/a13266667d30e1fd8=
72375675aab96bf76038f06#commitcomment-31350384",
"url": "https://github.com/quicwg/base-drafts/commit/a13266667d30e1fd8723=
75675aab96bf76038f06#commitcomment-31350384",
"name": "View Commit"
},
"description": "View this Commit on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5bf2c1972055d_650a3f9f61ed45b4228350--

