Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

clarify connection termination text #250

Merged
merged 1 commit into from Jan 31, 2017
Merged

clarify connection termination text #250

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -818,8 +818,8 @@ Connections should remain open until they become idle for a pre-negotiated
period of time. A QUIC connection, once established, can be terminated in one
of three ways:

1. Explicit Shutdown: An endpoint sends a CONNECTION_CLOSE frame to the peer
initiating a connection termination. An endpoint may send a GOAWAY frame to
1. Explicit Shutdown: An endpoint sends a CONNECTION_CLOSE frame to
initiate a connection termination. An endpoint may send a GOAWAY frame to
the peer prior to a CONNECTION_CLOSE to indicate that the connection will
soon be terminated. A GOAWAY frame signals to the peer that any active
streams will continue to be processed, but the sender of the GOAWAY will not
Expand Down