Re: [quicwg/base-drafts] HTTP: provide guidance on PING usage (#3723)

[Mike Bishop <[e-mail]>]

Looks like #2324 made this text more generic, leaving the specifics of how to keep a connection alive (e.g. with PING frames) to the transport implementation.  The text in question is now in Section 5.1:

> 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.

It's possible the transport draft needs a similar generalization, to recommend implementations expose a way for the application layer to control whether an connection is idle.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3723#issuecomment-639747613