IETF Logo Mail Archive

Re: [quicwg/base-drafts] QPACK-18: Appendix B and Decoder confirming inserts (#4245)

Magnus Westerlund <notifications@github.com> Tue, 20 October 2020 07:19 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 357AF3A03F4 for <quic-issues@ietfa.amsl.com>; Tue, 20 Oct 2020 00:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 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_16=1.092, 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: 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 daMmNWcAbWmC for <quic-issues@ietfa.amsl.com>; Tue, 20 Oct 2020 00:19:34 -0700 (PDT)
Received: from out-28.smtp.github.com (out-28.smtp.github.com [192.30.252.211]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBB193A03EE for <quic-issues@ietf.org>; Tue, 20 Oct 2020 00:19:34 -0700 (PDT)
Received: from github.com (hubbernetes-node-c306552.ash1-iad.github.net [10.56.118.49]) by smtp.github.com (Postfix) with ESMTPA id 9947E900D69 for <quic-issues@ietf.org>; Tue, 20 Oct 2020 00:19:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1603178373; bh=iJW0DTx8QRUX2ziNMKe7fpQswC0mQ5FEAVtpTBvWWHE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ay6cNCZPLTWjiB/XlMdYuzlk9DnV1sGDbejY2Df2jsaff9wW3E0zc9asJAtwXM504 2ixGJohq/Oy8001J31xUDhyS6KuW8N+2UENLFxhsmTq0pwpeSQ1eTXLBX9TBLK6kyA H0fWcsMKBQ+kkXNGiKyeNVBnH2Kp7q++8Qb+c4ZY=
Date: Tue, 20 Oct 2020 00:19:33 -0700
From: Magnus Westerlund <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5AM3KIIAWL6WJGHAV5TJYILEVBNHHCWMITS4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4245/712648481@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4245@github.com>
References: <quicwg/base-drafts/issues/4245@github.com>
Subject: Re: [quicwg/base-drafts] QPACK-18: Appendix B and Decoder confirming inserts (#4245)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f8e8f8595d73_5819b4708043"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gloinul
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/SjWzPhvHlHiSKg4KKQmBkB_RQXw>
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, 20 Oct 2020 07:19:36 -0000

The PR provides the context for the cancellation. However, if I understand the spec correctly, you can't reneg on the encoder stream duplicate command. That is going to happen. And even if the count increase doesn't happen in B.4, why haven't it happen in B.5? I think the connection to B.5 state here is of relevance. As the examples are a seuqence, I would expect that the B.4 ends with a Insert Increment Count to acknowledge the duplication when that arrives. 

-- 
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/4245#issuecomment-712648481

v2.23.0 | Report a Bug | By Email