Date: Mon, 19 Jun 2017 00:34:27 -0700
From: Lars Eggert <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abb81e9e8ca43aefccdc4e578b10a95b2cb15499c992cf00000001155f408392a169ce0e0f95f5@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/632/309361550@github.com>
In-Reply-To: <quicwg/base-drafts/issues/632@github.com>
References: <quicwg/base-drafts/issues/632@github.com>
Subject: Re: [quicwg/base-drafts] Explicit support for on-path calculation of
 loss and congestion of QUIC flows (#632)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_59477e83d5035_23013f99da2f5c3479770";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/5A7duK_F5FmStesl5XkANMwWS5U>

----==_mimepart_59477e83d5035_23013f99da2f5c3479770
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

I think it's actually a feature that loss information is NOT explicitly visible with QUIC, because packet loss ratio is a pretty useless metric in the first place. (The 5G people still dream about the "lossless" network, no matter how little sense that makes.) 

With RTT-scale delay information and if we - say - required QUIC to try and negotiate ECN, those two signals (esp. correlated) are much more useful.

-- 
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/issues/632#issuecomment-309361550
----==_mimepart_59477e83d5035_23013f99da2f5c3479770
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>I think it's actually a feature that loss information is NOT explicitly =
visible with QUIC, because packet loss ratio is a pretty useless metric in =
the first place. (The 5G people still dream about the "lossless" network, n=
o matter how little sense that makes.)</p>
<p>With RTT-scale delay information and if we - say - required QUIC to try =
and negotiate ECN, those two signals (esp. correlated) are much more useful=
.</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&mda=
sh;<br />You are receiving this because you are subscribed to this thread.<=
br />Reply to this email directly, <a href=3D"https://github.com/quicwg/bas=
e-drafts/issues/632#issuecomment-309361550">view it on GitHub</a>, or <a hr=
ef=3D"https://github.com/notifications/unsubscribe-auth/AWbkqxN09Gyl6MzLBy6=
TlEwJopy0KzJdks5sFiSDgaJpZM4N5-ze">mute the thread</a>.<img alt=3D"" height=
=3D"1" src=3D"https://github.com/notifications/beacon/AWbkq7schPRorMs_QHs-6=
NYu45BhHvdEks5sFiSDgaJpZM4N5-ze.gif" width=3D"1" /></p>
<div itemscope itemtype=3D"http://schema.org/EmailMessage">
<div itemprop=3D"action" itemscope itemtype=3D"http://schema.org/ViewAction=
">
  <link itemprop=3D"url" href=3D"https://github.com/quicwg/base-drafts/issu=
es/632#issuecomment-309361550"></link>
  <meta itemprop=3D"name" content=3D"View Issue"></meta>
</div>
<meta itemprop=3D"description" content=3D"View this Issue on GitHub"></meta>
</div>

<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_version"=
:"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"Gi=
tHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"quicwg=
/base-drafts","subtitle":"GitHub repository","main_image_url":"https://clou=
d.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290=
892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/asset=
s/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name=
":"Open in GitHub","url":"https://github.com/quicwg/base-drafts"}},"updates=
":{"snippets":[{"icon":"PERSON","message":"@larseggert in #632: I think it'=
s actually a feature that loss information is NOT explicitly visible with Q=
UIC, because packet loss ratio is a pretty useless metric in the first plac=
e. (The 5G people still dream about the \"lossless\" network, no matter how=
 little sense that makes.) \r\n\r\nWith RTT-scale delay information and if =
we - say - required QUIC to try and negotiate ECN, those two signals (esp. =
correlated) are much more useful."}],"action":{"name":"View Issue","url":"h=
ttps://github.com/quicwg/base-drafts/issues/632#issuecomment-309361550"}}}<=
/script>=

----==_mimepart_59477e83d5035_23013f99da2f5c3479770--