Re: [quicwg/base-drafts] Transport owns details of effecting keep-alive (#2324)
Mike Bishop <notifications@github.com> Wed, 09 January 2019 23:26 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 1827F12D7F8 for <quic-issues@ietfa.amsl.com>; Wed, 9 Jan 2019 15:26:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.553
X-Spam-Level:
X-Spam-Status: No, score=-12.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, 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 fd_URwiTjQgU for <quic-issues@ietfa.amsl.com>; Wed, 9 Jan 2019 15:26:34 -0800 (PST)
Received: from out-12.smtp.github.com (out-12.smtp.github.com [192.30.254.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F2E5129508 for <quic-issues@ietf.org>; Wed, 9 Jan 2019 15:26:34 -0800 (PST)
Date: Wed, 09 Jan 2019 15:26:33 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1547076393; bh=5u8cxVnpaaUzwChHLBq+NLmjT2wAxQdSw34xPNo1V5E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mo2gTH0doRrAVScLMXv6phzw98yy+gHdtWDm44OJYsXJq9PEWjNsb+O5l+WCWMW/S 0dgKUXlXsoS9bEK8Ze5n/NLFr90JaO4vh7FWPLlb5C8tHnFlhHpjHk7UAZyL1Vdei2 i6beaIShzedtfaNFg5gk4lewOT23449+NRRAgE4s=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1de09ccea5a6c9d9a2db05df6e9dd5342efd499c92cf00000001184e452992a169ce17b142a0@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2324/review/190987774@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2324@github.com>
References: <quicwg/base-drafts/pull/2324@github.com>
Subject: Re: [quicwg/base-drafts] Transport owns details of effecting keep-alive (#2324)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c368329ad4ed_5ac73facdc2d45c413413c"; 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/Ao1KZVUNvz5EeZbXoJ8kAG7wsYk>
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: Wed, 09 Jan 2019 23:26:36 -0000
MikeBishop commented on this pull request. > @@ -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 My main thought in the passive phrasing is that the transport will know whether activity on other streams makes a PING necessary or not at any given time. But I agree, a ref to 19.2 in transport is probably the easiest way to punt appropriately. -- 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/pull/2324#discussion_r246585014
- [quicwg/base-drafts] Transport owns details of ef… Mike Bishop
- Re: [quicwg/base-drafts] Transport owns details o… Martin Thomson
- Re: [quicwg/base-drafts] Transport owns details o… Mike Bishop
- Re: [quicwg/base-drafts] Transport owns details o… Mike Bishop
- Re: [quicwg/base-drafts] Transport owns details o… ianswett
- Re: [quicwg/base-drafts] Transport owns details o… Mike Bishop