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

minor editorial nits in Section 10 (Connection Termination) #4129

Merged
merged 3 commits into from
Sep 22, 2020
Merged

minor editorial nits in Section 10 (Connection Termination) #4129

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f611629
fix duplicate verb
marten-seemann Sep 22, 2020
dd25947
mention that protocol violations lead to immediate close
marten-seemann Sep 22, 2020
39e485d
Less text
martinthomson Sep 22, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 8 additions & 7 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2765,6 +2765,8 @@ After sending a CONNECTION_CLOSE frame, an endpoint immediately enters the
closing state; see {{closing}}. After receiving a CONNECTION_CLOSE frame,
endpoints enter the draining state; see {{draining}}.

Violations of the protocol lead to an immediate close.

An immediate close can be used after an application protocol has arranged to
close a connection. This might be after the application protocol negotiates a
graceful shutdown. The application protocol can exchange messages that are
Expand All @@ -2779,13 +2781,12 @@ These states SHOULD persist for at least three times the current Probe Timeout
(PTO) interval as defined in {{QUIC-RECOVERY}}.

Disposing of connection state prior to exiting the closing or draining state
could cause could result in an endpoint generating a stateless reset
unnecessarily when it receives a late-arriving packet. Endpoints that have some
alternative means to ensure that late-arriving packets do not induce a response,
such as those that are able to close the UDP socket, MAY end these states
earlier to allow for faster resource recovery. Servers that retain an open
socket for accepting new connections SHOULD NOT end the closing or draining
states early.
could result in an endpoint generating a stateless reset unnecessarily when it
receives a late-arriving packet. Endpoints that have some alternative means
to ensure that late-arriving packets do not induce a response, such as those
that are able to close the UDP socket, MAY end these states earlier to allow
for faster resource recovery. Servers that retain an open socket for accepting
new connections SHOULD NOT end the closing or draining states early.

Once its closing or draining state ends, an endpoint SHOULD discard all
connection state. The endpoint MAY send a stateless reset in response to any
Expand Down