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

Remove ACKs from draining period #853

Merged
merged 3 commits into from Oct 13, 2017
Merged

Remove ACKs from draining period #853

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8c946b2
Remove ACKs from draining period
martinthomson Oct 10, 2017
f4a46bd
s/can/MAY terminate draining period early
martinthomson Oct 12, 2017
3c5f649
Remove paragraph about terminating draining period early
martinthomson Oct 12, 2017
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
15 changes: 5 additions & 10 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -1461,18 +1461,17 @@ The draining period persists for three times the current Retransmission Timeout
can be acknowledged, but no new application data can be sent on the connection.

Different treatment is given to packets that are received while a connection is
in the draining period depending on how the connection was closed. In all
cases, it is possible to acknowledge packets that are received as normal, but
other reactions might be preferable depending on how the connection was closed.
An endpoint that is in a draining period MUST NOT send packets containing frames
other than ACK, PADDING, or CONNECTION_CLOSE.
in the draining period depending on how the connection was closed.

An endpoint that is in a draining period MUST NOT send packets unless they
contain a CONNECTION_CLOSE or APPLICATION_CLOSE frame.

Once the draining period has ended, an endpoint SHOULD discard per-connection
state. This results in new packets on the connection being discarded. An
endpoint MAY send a stateless reset in response to any further incoming packets.

The draining period does not apply when a stateless reset ({{stateless-reset}})
is used.
is sent.


### Idle Timeout
Expand Down Expand Up @@ -1512,10 +1511,6 @@ Note:
control, which are not expected to be relevant for a closed connection.
Retransmitting the final packet requires less state.

An endpoint can cease sending CONNECTION_CLOSE or APPLICATION_CLOSE frames if it
receives either a CONNECTION_CLOSE, APPLICATION_CLOSE or an acknowledgement for
a packet that contained a either close frame.

An immediate close can be used after an application protocol has arranged to
close a connection. This might be after the application protocols negotiates a
graceful shutdown. The application protocol exchanges whatever messages that
Expand Down