Re: [quicwg/base-drafts] Consider a new stream type to act like MAX_PUSH_ID (#2418)

Lucas Pardue <notifications@github.com> Wed, 06 February 2019 00:48 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 86B57128CE4 for <quic-issues@ietfa.amsl.com>; Tue, 5 Feb 2019 16:48:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.552
X-Spam-Level:
X-Spam-Status: No, score=-12.552 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_IMAGE_ONLY_32=0.001, 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 cSjnAB4Hqc-c for <quic-issues@ietfa.amsl.com>; Tue, 5 Feb 2019 16:48:53 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB5A5128B01 for <quic-issues@ietf.org>; Tue, 5 Feb 2019 16:48:53 -0800 (PST)
Date: Tue, 05 Feb 2019 16:48:52 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1549414132; bh=P1hktiGePpk8de/QixIi2ZxWn+GjD3iz/O4sA0LLrsA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ExnX1vGIJozgCHa0Gq7w2y9lEiQdVdcrp3ac4UXOiVjqjll7fly2eD329Z1A/4+ET 3//PSSmvU6jbi9zoAsknpkNowxfH/Yiu8eoVb+5bHbE3a4bSnXl4ZdDDANSvRtb7OG oLBr63fN+judYbvpfgVo/1ONVdZRPj4d/oiVt1Eg=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab18f0b4a78803c0ebd255412548558b6a4c1eb1f292cf000000011871f0f492a169ce183df2cd@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2418/460862806@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2418@github.com>
References: <quicwg/base-drafts/issues/2418@github.com>
Subject: Re: [quicwg/base-drafts] Consider a new stream type to act like MAX_PUSH_ID (#2418)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5a2ef4ee20d_35a93f8f8dcd45b87756d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/Z6COSd0b4vyeOMun4lfJ6u_jEa8>
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, 06 Feb 2019 00:48:56 -0000

I think depends if we ascribe special meaning to the fact that a client took N steps to a max value, or if we just care that we arrive at the max value.

To me, the endstate is the same. And since you can't "steal back" push ID credits, neither side should care if that manifests. 

But there may be gotchas in ignoring lower limits so I can fall in line of popular opinion.

I'm not seeing an outright no to this strawman. I think there are some unique benefits and drawbacks. What is a sensible path forward, a more solid PR?

-- 
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/2418#issuecomment-460862806