Date: Mon, 11 Nov 2019 21:03:31 -0800
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJKZOV3NXMUOL527UDV5325X2HEVBNHHB6EUYP4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3225/review/315295797@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3225@github.com>
References: <quicwg/base-drafts/pull/3225@github.com>
Subject: Re: [quicwg/base-drafts] A day in the life (#3225)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5dca3d23e5fac_6a343ff3166cd95c7644b1";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/aOWlDbNJ9zo8k6cGVH5P_9vQYcs>


----==_mimepart_5dca3d23e5fac_6a343ff3166cd95c7644b1
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

martinthomson commented on this pull request.



> +handshake phase.  0-RTT allows application messages to be sent by a client
+before receiving any messages from the server.  However, 0-RTT lacks certain key
+security guarantees. In particular, there is no protection against replay
+attacks in 0-RTT; see {{QUIC-TLS}}.  Separately, a server can also send
+application data to a client before it receives the final cryptographic
+handshake messages that allow it to confirm the identity and liveness of the
+client.  These capabilities allow an application protocol to offer the option to
+trade some security guarantees for improved latency.
+
+The use of connection IDs ({{connection-id}}) allows connections to migrate to a
+new network path, both as a direct choice of an endpoint and when forced by a
+change in a middlebox.  {{migration}} describes how a migration can be performed
+securely without adversely affecting privacy.
+
+For connections that are no longer needed or desired, there are several ways for
+a client and server to agree to remove connection state ({{termination}}).

Yeah, I had that in the first cut, but then removed it.  The referenced section has enough information about closing.  It's not super-important to duplicate all that text when it is so succinctly stated later.

-- 
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/pull/3225#discussion_r345018506
----==_mimepart_5dca3d23e5fac_6a343ff3166cd95c7644b1
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p><b>@martinthomson</b> commented on this pull request.</p>

<hr>

<p>In <a href="https://github.com/quicwg/base-drafts/pull/3225#discussion_r345018506">draft-ietf-quic-transport.md</a>:</p>
<pre style='color:#555'>&gt; +handshake phase.  0-RTT allows application messages to be sent by a client
+before receiving any messages from the server.  However, 0-RTT lacks certain key
+security guarantees. In particular, there is no protection against replay
+attacks in 0-RTT; see {{QUIC-TLS}}.  Separately, a server can also send
+application data to a client before it receives the final cryptographic
+handshake messages that allow it to confirm the identity and liveness of the
+client.  These capabilities allow an application protocol to offer the option to
+trade some security guarantees for improved latency.
+
+The use of connection IDs ({{connection-id}}) allows connections to migrate to a
+new network path, both as a direct choice of an endpoint and when forced by a
+change in a middlebox.  {{migration}} describes how a migration can be performed
+securely without adversely affecting privacy.
+
+For connections that are no longer needed or desired, there are several ways for
+a client and server to agree to remove connection state ({{termination}}).
</pre>
<p>Yeah, I had that in the first cut, but then removed it.  The referenced section has enough information about closing.  It's not super-important to duplicate all that text when it is so succinctly stated later.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/pull/3225?email_source=notifications&amp;email_token=AFTOJK7BDEOIMZ2LLCZVLVTQTI2KHA5CNFSM4JL53IP2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCLFQQNI#discussion_r345018506">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK2ETFXE7OBI3FJF3OTQTI2KHANCNFSM4JL53IPQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK624NYN44MZLNG6VY3QTI2KHA5CNFSM4JL53IP2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCLFQQNI.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/pull/3225?email_source=notifications\u0026email_token=AFTOJK7BDEOIMZ2LLCZVLVTQTI2KHA5CNFSM4JL53IP2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCLFQQNI#discussion_r345018506",
"url": "https://github.com/quicwg/base-drafts/pull/3225?email_source=notifications\u0026email_token=AFTOJK7BDEOIMZ2LLCZVLVTQTI2KHA5CNFSM4JL53IP2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCLFQQNI#discussion_r345018506",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5dca3d23e5fac_6a343ff3166cd95c7644b1--