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

Mike Bishop <> Fri, 05 June 2020 19:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 008E63A0418 for <>; Fri, 5 Jun 2020 12:35:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id er6IC1VCzgzh for <>; Fri, 5 Jun 2020 12:35:19 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3A29B3A0416 for <>; Fri, 5 Jun 2020 12:35:19 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 8F98128280F for <>; Fri, 5 Jun 2020 12:35:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1591385717; bh=+YvC8SpToi77+ii2zmlcJ+s2CeU66/l3Iujuw4/OILU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Edgyo0cPOzhdbJ8+kKoIwR0RYl+bD7HNXOcmeyu39z9FuyW1E9hlgJ6V7a0eXnAnz 8i3pPap8as+Yro1pBo0StPC4s2VUV85cj8rrcYgLTfuWWrEBYSHj8Kfrf4gsOQ+hgT 7FocM/+gFuhWQhSyHciRY6+RQI0a1Ifyuz1vz5U0=
Date: Fri, 05 Jun 2020 12:35:17 -0700
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3723/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] HTTP: provide guidance on PING usage (#3723)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5eda9e757f832_24633faf5e4cd96412856"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 05 Jun 2020 19:35:21 -0000

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: