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

Transport owns details of effecting keep-alive #2324

Merged
merged 2 commits into from Jan 10, 2019
Merged

Transport owns details of effecting keep-alive #2324

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b4ade00
Transport owns details of effecting keep-alive
MikeBishop Jan 9, 2019
8644e87
Punt more to the transport doc
MikeBishop Jan 9, 2019
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: 8 additions & 7 deletions draft-ietf-quic-http.md
View file
Open in desktop
Expand Up @@ -1202,13 +1202,14 @@ will need to open a new connection for new requests if the existing connection
has been idle for longer than the server's advertised idle timeout, and SHOULD
do so if approaching the idle timeout.

HTTP clients are expected to use QUIC PING frames to keep connections open while
there are responses outstanding for requests or server pushes. If the client is
not expecting a response from the server, allowing an idle connection to time
out is preferred over expending effort maintaining a connection that might not
be needed. A gateway MAY use PING to maintain connections in anticipation of
need rather than incur the latency cost of connection establishment to servers.
Servers SHOULD NOT use PING frames to keep a connection open.
HTTP clients are expected to request that the transport keep connections open
while there are responses outstanding for requests or server pushes, as
described in Section 19.2 of {{QUIC-TRANSPORT}}. If the client is not expecting
a response from the server, allowing an idle connection to time out is preferred
over expending effort maintaining a connection that might not be needed. A
gateway MAY maintain connections in anticipation of need rather than incur the
latency cost of connection establishment to servers. Servers SHOULD NOT actively
keep connections open.

## Connection Shutdown

Expand Down