From b4ade009100b336ffb2abc185827e89635a904bc Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Wed, 9 Jan 2019 10:13:14 -0800 Subject: [PATCH 1/2] Transport owns details of effecting keep-alive --- draft-ietf-quic-http.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index be5019cf12..a694cd8049 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -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. This might +involve QUIC PING frames being generated by the transport implementation. 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 From 8644e87efcdaa2ff7d290f637619dbd9576051b9 Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Wed, 9 Jan 2019 15:24:53 -0800 Subject: [PATCH 2/2] Punt more to the transport doc --- draft-ietf-quic-http.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index a694cd8049..f068594b53 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -1203,13 +1203,13 @@ 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 request that the transport keep connections open -while there are responses outstanding for requests or server pushes. This might -involve QUIC PING frames being generated by the transport implementation. 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. +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