Date: Tue, 12 Nov 2019 13:43:56 -0800
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK3FIR4UXVHRX57YBZ533BNBZEVBNHHB6EUYP4@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/315864656@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_5dcb279ccf884_31ce3fda8c2cd96c1532760";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/rMa30k4EqUl_fi-DkrqSbCSBnEQ>


----==_mimepart_5dcb279ccf884_31ce3fda8c2cd96c1532760
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

ianswett approved 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 reduced 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}}).

I'm not sure this suggestion is better, but it reads a bit more easily to me.

```suggestion
a client and server to terminate a connection ({{termination}}).
```

-- 
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#pullrequestreview-315864656
----==_mimepart_5dcb279ccf884_31ce3fda8c2cd96c1532760
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p><b>@ianswett</b> approved this pull request.</p>=0D
=0D
<hr>=0D
=0D
<p>In <a href=3D"https://github.com/quicwg/base-drafts/pull/3225#discussi=
on_r345460974">draft-ietf-quic-transport.md</a>:</p>=0D
<pre style=3D'color:#555'>&gt; +handshake phase.  0-RTT allows applicatio=
n messages to be sent by a client=0D
+before receiving any messages from the server.  However, 0-RTT lacks cer=
tain key=0D
+security guarantees. In particular, there is no protection against repla=
y=0D
+attacks in 0-RTT; see {{QUIC-TLS}}.  Separately, a server can also send=0D=

+application data to a client before it receives the final cryptographic=0D=

+handshake messages that allow it to confirm the identity and liveness of=
 the=0D
+client.  These capabilities allow an application protocol to offer the o=
ption to=0D
+trade some security guarantees for reduced latency.=0D
+=0D
+The use of connection IDs ({{connection-id}}) allows connections to migr=
ate to a=0D
+new network path, both as a direct choice of an endpoint and when forced=
 by a=0D
+change in a middlebox.  {{migration}} describes how a migration can be p=
erformed=0D
+securely without adversely affecting privacy.=0D
+=0D
+For connections that are no longer needed or desired, there are several =
ways for=0D
+a client and server to agree to remove connection state ({{termination}}=
).=0D
</pre>=0D
<p>I'm not sure this suggestion is better, but it reads a bit more easily=
 to me.</p>=0D
=E2=AC=87=EF=B8=8F Suggested change=0D
<pre style=3D"color: #555">-a client and server to agree to remove connec=
tion state ({{termination}}).=0D
+a client and server to terminate a connection ({{termination}}).=0D
</pre>=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/pull/3225?email_source=3Dnotifications&amp;email_token=3DA=
FTOJK5PIHUWLRGYGOTOUQDQTMPRZA5CNFSM4JL53IP2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJ=
SXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCLJ3MUA#pullrequestreview-315864656=
">view it on GitHub</a>, or <a href=3D"https://github.com/notifications/u=
nsubscribe-auth/AFTOJK4WHUMHCFOFZHBU4F3QTMPRZANCNFSM4JL53IPQ">unsubscribe=
</a>.<img src=3D"https://github.com/notifications/beacon/AFTOJK5ONPIWGDVN=
2467X6TQTMPRZA5CNFSM4JL53IP2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWN=
FSXPKTDN5WW2ZLOORPWSZGOCLJ3MUA.gif" height=3D"1" width=3D"1" alt=3D"" /><=
/p>=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/pull/3225?email_source=3D=
notifications\u0026email_token=3DAFTOJK5PIHUWLRGYGOTOUQDQTMPRZA5CNFSM4JL5=
3IP2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOC=
LJ3MUA#pullrequestreview-315864656",=0D
"url": "https://github.com/quicwg/base-drafts/pull/3225?email_source=3Dno=
tifications\u0026email_token=3DAFTOJK5PIHUWLRGYGOTOUQDQTMPRZA5CNFSM4JL53I=
P2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCLJ=
3MUA#pullrequestreview-315864656",=0D
"name": "View Pull Request"=0D
},=0D
"description": "View this Pull Request on GitHub",=0D
"publisher": {=0D
"@type": "Organization",=0D
"name": "GitHub",=0D
"url": "https://github.com"=0D
}=0D
}=0D
]</script>=

----==_mimepart_5dcb279ccf884_31ce3fda8c2cd96c1532760--