[quicwg/base-drafts] More generic keep-alive text (#2092)

Mike Bishop <notifications@github.com> Mon, 03 December 2018 20:05 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9C13128CF3 for <quic-issues@ietfa.amsl.com>; Mon, 3 Dec 2018 12:05:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IqEWnYuhgGxf for <quic-issues@ietfa.amsl.com>; Mon, 3 Dec 2018 12:05:54 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3366130DF9 for <quic-issues@ietf.org>; Mon, 3 Dec 2018 12:05:53 -0800 (PST)
Date: Mon, 03 Dec 2018 12:05:52 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543867552; bh=R1cgkPNjoeWfp6QYNRVBqVg9Y0iSypwjg4yrF7lmy30=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=0lINq3h0ne3XBNIPBHSIcOUc+JhG6cvTb2YvVMxwCCYIHFivtnAKN4bBcO4A39Vb+ QZELVodKsOurvRR/f9IJsOTDKGq0CTV6LZCyHyUBcik1NQV/w5xmQL+iEjXXO98KXZ 1gtEyDw2mDALDw0mfPXmoel3lP3Ma4IOsejfGia8=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abce3467a9b5fabeffbc2e3bd78804919456720cc592cf00000001181d4ea092a169ce1710e5ab@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2092@github.com>
Subject: [quicwg/base-drafts] More generic keep-alive text (#2092)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c058ca0c43d7_119d3fbe52cd45c41460cf"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/OvvDWJxFIl2QKILhjFdPfAYoM7Q>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Dec 2018 20:05:57 -0000

In #2068, the direction of the discussion is that PING frames are an application-layer concept that won't necessarily be directly under the application-layer's control.  The HTTP draft currently says:
> 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.

This should be reworded in terms of requesting the transport stack to keep the connection from idling out, rather than directly discussing PING frames.

-- 
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/2092