Date: Thu, 07 Feb 2019 23:22:44 -0800
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abed3b470d0374f3e8073fea6d0f578d86835f3cd992cf000000011874f04492a169ce18321f5a@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2400/461713773@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2400@github.com>
References: <quicwg/base-drafts/issues/2400@github.com>
Subject: Re: [quicwg/base-drafts] VN packets may be dropped more often when
 the QUIC bit is 0 (#2400)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c5d2e443176d_7acb3fb9c32d45bc499d";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/4sHYJQITzZr0DNo31ndXgDd2lII>


----==_mimepart_5c5d2e443176d_7acb3fb9c32d45bc499d
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I=E2=80=99m in favor of always setting the bit, and if not, symmetric hea=
der protection.=0D
=0D
There are significant symmetric use cases, including NAT-punching p2p.=0D=

=0D
Making it 1 permanently lets QUIC co-exist, eg on a single client 443 por=
t, and it avoids a lot of potential problems over a bit that is not neede=
d.=0D
=0D
=0D
________________________________=0D
Fra: Kazuho Oku <notifications@github.com>=0D
Sendt: fredag, februar 8, 2019 7:14 AM=0D
Til: quicwg/base-drafts=0D
Cc: MikkelFJ; Comment=0D
Emne: Re: [quicwg/base-drafts] VN packets may be dropped more often when =
the QUIC bit is 0 (#2400)=0D
=0D
=0D
(2) bring it under header protection for server-generated packets only.=0D=

=0D
I would oppose to such a design, because that disables a reverse proxy fr=
om using a single port for accepting connections and also for initiating =
connections, assuming that either the proxy or a middlebox in front of th=
e proxy relies on the QUIC bit to route the packets. Greasing would be fi=
ne, because it's not something to be required for every endpoint to imple=
ment.=0D
=0D
Are there any privacy implications to there being a "client bit"?=0D
=0D
The bit would be a good indicator to police P2P traffic for ISPs...=0D
=0D
=E2=80=94=0D
You are receiving this because you commented.=0D
Reply to this email directly, view it on GitHub<https://github.com/quicwg=
/base-drafts/issues/2400#issuecomment-461702432>, or mute the thread<http=
s://github.com/notifications/unsubscribe-auth/AALzNxSA70R6OnQ0JdIwj0SmzAO=
EPCWYks5vLRXVgaJpZM4afXoe>.=0D
=0D
=0D
-- =0D
You are receiving this because you are subscribed to this thread.=0D
Reply to this email directly or view it on GitHub:=0D
https://github.com/quicwg/base-drafts/issues/2400#issuecomment-461713773=

----==_mimepart_5c5d2e443176d_7acb3fb9c32d45bc499d
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I=E2=80=99m in favor of always setting the bit, and if not, symmetric hea=
der protection.<br>=0D
<br>=0D
There are significant symmetric use cases, including NAT-punching p2p.<br=
>=0D
<br>=0D
Making it 1 permanently lets QUIC co-exist, eg on a single client 443 por=
t, and it avoids a lot of potential problems over a bit that is not neede=
d.<br>=0D
<br>=0D
<br>=0D
________________________________<br>=0D
Fra: Kazuho Oku &lt;notifications@github.com&gt;<br>=0D
Sendt: fredag, februar 8, 2019 7:14 AM<br>=0D
Til: quicwg/base-drafts<br>=0D
Cc: MikkelFJ; Comment<br>=0D
Emne: Re: [quicwg/base-drafts] VN packets may be dropped more often when =
the QUIC bit is 0 (#2400)<br>=0D
<br>=0D
<br>=0D
(2) bring it under header protection for server-generated packets only.<b=
r>=0D
<br>=0D
I would oppose to such a design, because that disables a reverse proxy fr=
om using a single port for accepting connections and also for initiating =
connections, assuming that either the proxy or a middlebox in front of th=
e proxy relies on the QUIC bit to route the packets. Greasing would be fi=
ne, because it&#39;s not something to be required for every endpoint to i=
mplement.<br>=0D
<br>=0D
Are there any privacy implications to there being a &quot;client bit&quot=
;?<br>=0D
<br>=0D
The bit would be a good indicator to police P2P traffic for ISPs...<br>=0D=

<br>=0D
=E2=80=94<br>=0D
You are receiving this because you commented.<br>=0D
Reply to this email directly, view it on GitHub&lt;https://github.com/qui=
cwg/base-drafts/issues/2400#issuecomment-461702432&gt;, or mute the threa=
d&lt;https://github.com/notifications/unsubscribe-auth/AALzNxSA70R6OnQ0Jd=
Iwj0SmzAOEPCWYks5vLRXVgaJpZM4afXoe&gt;.<br>=0D
=0D
=0D
<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/issues/2400#issuecomment-461713773">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkqweT=
kW0qm3JJWH7CtwtV2Or7NLShks5vLSXEgaJpZM4afXoe">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkq-q94uHzHcSV9qpqPkGy2082=
KLR3ks5vLSXEgaJpZM4afXoe.gif" height=3D"1" width=3D"1" alt=3D"" /></p>=0D=

<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://github.githubassets.com/images/email/message_cards/header.png","avata=
r_image_url":"https://github.githubassets.com/images/email/message_cards/=
avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/q=
uicwg/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@=
mikkelfj in #2400: I=E2=80=99m in favor of always setting the bit, and if=
 not, symmetric header protection.\n\nThere are significant symmetric use=
 cases, including NAT-punching p2p.\n\nMaking it 1 permanently lets QUIC =
co-exist, eg on a single client 443 port, and it avoids a lot of potentia=
l problems over a bit that is not needed.\n\n\n__________________________=
______\nFra: Kazuho Oku \u003cnotifications@github.com\u003e\nSendt: fred=
ag, februar 8, 2019 7:14 AM\nTil: quicwg/base-drafts\nCc: MikkelFJ; Comme=
nt\nEmne: Re: [quicwg/base-drafts] VN packets may be dropped more often w=
hen the QUIC bit is 0 (#2400)\n\n\n(2) bring it under header protection f=
or server-generated packets only.\n\nI would oppose to such a design, bec=
ause that disables a reverse proxy from using a single port for accepting=
 connections and also for initiating connections, assuming that either th=
e proxy or a middlebox in front of the proxy relies on the QUIC bit to ro=
ute the packets. Greasing would be fine, because it's not something to be=
 required for every endpoint to implement.\n\nAre there any privacy impli=
cations to there being a \"client bit\"?\n\nThe bit would be a good indic=
ator to police P2P traffic for ISPs...\n\n=E2=80=94\nYou are receiving th=
is because you commented.\nReply to this email directly, view it on GitHu=
b\u003chttps://github.com/quicwg/base-drafts/issues/2400#issuecomment-461=
702432\u003e, or mute the thread\u003chttps://github.com/notifications/un=
subscribe-auth/AALzNxSA70R6OnQ0JdIwj0SmzAOEPCWYks5vLRXVgaJpZM4afXoe\u003e=
.\n"}],"action":{"name":"View Issue","url":"https://github.com/quicwg/bas=
e-drafts/issues/2400#issuecomment-461713773"}}}</script>=0D
<script type=3D"application/ld+json">[=0D
{=0D
"@context": "http://schema.org",=0D
"@type": "EmailMessage",=0D
"potentialAction": {=0D
"@type": "ViewAction",=0D
"target": "https://github.com/quicwg/base-drafts/issues/2400#issuecomment=
-461713773",=0D
"url": "https://github.com/quicwg/base-drafts/issues/2400#issuecomment-46=
1713773",=0D
"name": "View Issue"=0D
},=0D
"description": "View this Issue on GitHub",=0D
"publisher": {=0D
"@type": "Organization",=0D
"name": "GitHub",=0D
"url": "https://github.com"=0D
}=0D
}=0D
]</script>=

----==_mimepart_5c5d2e443176d_7acb3fb9c32d45bc499d--