Date: Tue, 25 Apr 2017 23:54:05 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab821f387af1bdcb65ef6a20444675b59a61980ae992cf000000011518060d92a169ce0d5d5ed1@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/462/297257194@github.com>
In-Reply-To: <quicwg/base-drafts/issues/462@github.com>
References: <quicwg/base-drafts/issues/462@github.com>
Subject: Re: [quicwg/base-drafts] Treat client and server as equals (#462)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5900440d4a564_6e913fe6d87c3c348497f";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/T_hQNV7MGlt3P4s7maQsJi_LceU>

----==_mimepart_5900440d4a564_6e913fe6d87c3c348497f
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Note that this latter point is incorrect.  I was careful to make public reset symmetric.  Now, the utility of that is pretty low for HTTP, and is probably even lower in p2p cases based on my experience with the NAT traversal systems that are needed there (see ICE).

The notion that the client might use a non-unique source address and port for a new connection is really stretching the design too much for me.

-- 
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/462#issuecomment-297257194
----==_mimepart_5900440d4a564_6e913fe6d87c3c348497f
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>Note that this latter point is incorrect.  I was careful to make public =
reset symmetric.  Now, the utility of that is pretty low for HTTP, and is p=
robably even lower in p2p cases based on my experience with the NAT travers=
al systems that are needed there (see ICE).</p>
<p>The notion that the client might use a non-unique source address and por=
t for a new connection is really stretching the design too much for me.</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/462#issuecomment-297257194">view it on GitHub</a>, or <a hr=
ef=3D"https://github.com/notifications/unsubscribe-auth/AWbkqy1XCYECYfgd5dx=
pSZAyyUSBXqihks5rzuoNgaJpZM4NH2HF">mute the thread</a>.<img alt=3D"" height=
=3D"1" src=3D"https://github.com/notifications/beacon/AWbkq4tt6pPZ4TLX1aPlo=
zaL3FuinGN-ks5rzuoNgaJpZM4NH2HF.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/462#issuecomment-297257194"></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":"@martinthomson in #462: Note tha=
t this latter point is incorrect.  I was careful to make public reset symme=
tric.  Now, the utility of that is pretty low for HTTP, and is probably eve=
n lower in p2p cases based on my experience with the NAT traversal systems =
that are needed there (see ICE).\r\n\r\nThe notion that the client might us=
e a non-unique source address and port for a new connection is really stret=
ching the design too much for me."}],"action":{"name":"View Issue","url":"h=
ttps://github.com/quicwg/base-drafts/issues/462#issuecomment-297257194"}}}<=
/script>=

----==_mimepart_5900440d4a564_6e913fe6d87c3c348497f--