Re: [quicwg/base-drafts] Do no define connection as a conversation (#2077)

[Mike Bishop <[e-mail]>]

MikeBishop commented on this pull request.



> @@ -865,11 +861,10 @@ longer if the peer chooses to not send STREAMS_BLOCKED frames.
 
 # Connections {#connections}
 
-A QUIC connection is a single conversation between two QUIC endpoints.  QUIC's
-connection establishment combines version negotiation with the cryptographic
-and transport handshakes to reduce connection establishment latency, as
-described in {{handshake}}.  Once established, a connection may migrate to a
-different IP or port at either endpoint as
+QUIC's connection establishment combines version negotiation with the
+cryptographic and transport handshakes to reduce connection establishment
+latency, as described in {{handshake}}.  Once established, a connection
+may migrate to a different IP or port at either endpoint as

@marten-seemann, I think this is an artifact of the effort to specify the migration primitives generically, even if only clients can migrate freely in v1.  Given the SPA mechanism, this is literally true as written, but more constrained that one might infer from this text.  Feel free to open a separate editorial issue for this, but I don't think we should make @dtikhonov fix it in his unrelated PR.

-- 
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/2077#discussion_r237935418