Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-previous value conn error seems too severe (#2412)
Lucas Pardue <notifications@github.com> Tue, 05 February 2019 01:54 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 5B45F130F3E for <quic-issues@ietfa.amsl.com>; Mon, 4 Feb 2019 17:54:42 -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 CaX_jIp8XOIu for <quic-issues@ietfa.amsl.com>; Mon, 4 Feb 2019 17:54:40 -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 A9CB0130F3A for <quic-issues@ietf.org>; Mon, 4 Feb 2019 17:54:40 -0800 (PST)
Date: Mon, 04 Feb 2019 17:54:39 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1549331679; bh=npPdUsZ9qigkzulaiDdb3EcWIgvyFWDX8Z5GbkZX99M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KG5Gca+y9VOi9aXlbwYSdSlkguwT15FLVbH3vruFSa6ie3ExKOorOZ8SBEMED6mB/ FcmMFWJZSxnQZdewI+C1JkdgN5AkPSuKbTLlmeb/Kc5DS4McVZF/mbYFLEjo1dJNck 1skkAypb135IPnCFr6ekvYfRuRNxxC6AtZvYmk/c=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab741cdb597f9361cc08c10ab397045810e4ef884b92cf000000011870aedf92a169ce183b427c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2412/460485181@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2412@github.com>
References: <quicwg/base-drafts/issues/2412@github.com>
Subject: Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-previous value conn error seems too severe (#2412)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c58ecdfa0460_74b73fb014cd45c0831cd"; 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/uLM44KULZWs7zyK4-h6NfpA2qwM>
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: Tue, 05 Feb 2019 01:54:42 -0000
Yes, but whether that synchronisation point coordinates based on H3 frames or simply STREAM data seems like an implementation detail. I.e. I call frame.to_bytes() and then feed that to my transport library API. The upside to doing limit increase cleverly on the client, is that you open the opportunity to aggregate push limit increments. I.e. send one frame that increments by a single larger value. If we were to bring the discussion back to principles, is the intent of the connection error here because sending a lower limit is meaningless for both sides? -- 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/2412#issuecomment-460485181
- [quicwg/base-drafts] MAX_PUSH_ID: lower-than-prev… Lucas Pardue
- Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-… Martin Thomson
- Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-… Lucas Pardue
- Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-… ianswett
- Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-… Lucas Pardue
- Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-… Martin Thomson
- Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-… Lucas Pardue
- Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-… Martin Thomson
- Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-… Lucas Pardue
- Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-… Mike Bishop
- Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-… Lucas Pardue
- Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-… Dmitri Tikhonov
- Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-… Lucas Pardue
- Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-… Mike Bishop
- Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-… Mike Bishop
- Re: [quicwg/base-drafts] MAX_PUSH_ID: lower-than-… MikkelFJ