Date: Thu, 31 Jan 2019 03:00:05 -0800
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab475e858cb9176b0858ad350d32668cc353756dfa92cf00000001186a973592a169ce182664e3@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2398/459303491@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2398@github.com>
References: <quicwg/base-drafts/issues/2398@github.com>
Subject: Re: [quicwg/base-drafts] Specify DCID of 0-RTT packets (#2398)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c52d53576f3c_4f343f9ddacd45bc41969c";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/qj0JG8LPNUmNhm_9RK5IUH7E7Ao>


----==_mimepart_5c52d53576f3c_4f343f9ddacd45bc41969c
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

We previously discussed this and the conclusion was to change to the server-selected connection ID once a packet has been received from the server.  Until then, the random value would be used.  If this is missing, then we just need some text in the 0-RTT packet section to cover this.  This probably just needs to reference [Section 7.2](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#negotiating-connection-ids), which says:

>  Upon receiving a packet, each endpoint sets the Destination Connection ID it sends to match the value of the Source Connection ID that they receive.

-- 
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/2398#issuecomment-459303491
----==_mimepart_5c52d53576f3c_4f343f9ddacd45bc41969c
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>We previously discussed this and the conclusion was to change to the s=
erver-selected connection ID once a packet has been received from the ser=
ver.  Until then, the random value would be used.  If this is missing, th=
en we just need some text in the 0-RTT packet section to cover this.  Thi=
s probably just needs to reference <a href=3D"https://quicwg.org/base-dra=
fts/draft-ietf-quic-transport.html#negotiating-connection-ids" rel=3D"nof=
ollow">Section 7.2</a>, which says:</p>
<blockquote>
<p>Upon receiving a packet, each endpoint sets the Destination Connection=
 ID it sends to match the value of the Source Connection ID that they rec=
eive.</p>
</blockquote>

<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/2398#issuecomment-459303491">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq-FP=
01sQbHUulU7tvKxy803DOPGOks5vIsy1gaJpZM4ab-Rt">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkq3duuBbGt71jA2bHBqePWXn2=
NLQSks5vIsy1gaJpZM4ab-Rt.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://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":"@=
martinthomson in #2398: We previously discussed this and the conclusion w=
as to change to the server-selected connection ID once a packet has been =
received from the server.  Until then, the random value would be used.  I=
f this is missing, then we just need some text in the 0-RTT packet sectio=
n to cover this.  This probably just needs to reference [Section 7.2](htt=
ps://quicwg.org/base-drafts/draft-ietf-quic-transport.html#negotiating-co=
nnection-ids), which says:\r\n\r\n\u003e  Upon receiving a packet, each e=
ndpoint sets the Destination Connection ID it sends to match the value of=
 the Source Connection ID that they receive."}],"action":{"name":"View Is=
sue","url":"https://github.com/quicwg/base-drafts/issues/2398#issuecommen=
t-459303491"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2398#issuecomment=
-459303491",
"url": "https://github.com/quicwg/base-drafts/issues/2398#issuecomment-45=
9303491",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c52d53576f3c_4f343f9ddacd45bc41969c--