Re: [quicwg/base-drafts] H3 spec fails to warn about initial_max_stream_data_uni (#2589)
Marten Seemann <notifications@github.com> Thu, 04 April 2019 03:24 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 DC7371203CD for <quic-issues@ietfa.amsl.com>; Wed, 3 Apr 2019 20:24:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
X-Spam-Status: No, score=-8 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, 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 K7aOJyYY3z4B for <quic-issues@ietfa.amsl.com>; Wed, 3 Apr 2019 20:24:48 -0700 (PDT)
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 BC74D120222 for <quic-issues@ietf.org>; Wed, 3 Apr 2019 20:24:47 -0700 (PDT)
Date: Wed, 03 Apr 2019 20:24:46 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1554348286; bh=uW+mmEcKv43JgZ+lS9EBkznvh4PEmYxcw7mhOgPahUk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nT4Gvp/BxRtfsRo8kvoorMlBrPvWiMZKntbcHdBiQ6yRNaAwzY0k6RoVrq5/XA0jw F9/4kHdoKFQLjQkQZbtpUqCo35hise/9cwIDRAnpT/hEyu6IG5XBjIwK5Tl0gcHIJW sK6GzKfJlXvftVKV6MD+mv/H8PkPZZpgmsJKA8hQ=
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb7267a0658c0956918e7d2b6a035d45bfe0ef44092cf0000000118bd3afe92a169ce1992e751@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2589/479735486@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2589@github.com>
References: <quicwg/base-drafts/issues/2589@github.com>
Subject: Re: [quicwg/base-drafts] H3 spec fails to warn about initial_max_stream_data_uni (#2589)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ca578fe7df7b_1a743fe8b8cd45c0581652"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: marten-seemann
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/CArrhL3RBWflSO5QmmuMjb5P3SE>
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: Thu, 04 Apr 2019 03:24:50 -0000
STREAM_DATA_BLOCKED is what I meant, sorry. Too many \*_BLOCKED frames. STREAM_BLOCKED doesn't even exist... I think this is a general issue with either picoquic or ats, and not H3 specific. No matter what the application protocol, a peer can send you 0-values for stream counts and for flow control limits, and the protocol should still work (although slower, since the MAX* frames need to be exchanged). There should never be a deadlock (unless the peer is refusing to grant credits, even at a later point in time). -- 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/2589#issuecomment-479735486
- [quicwg/base-drafts] H3 spec fails to warn about … Christian Huitema
- Re: [quicwg/base-drafts] H3 spec fails to warn ab… Marten Seemann
- Re: [quicwg/base-drafts] H3 spec fails to warn ab… Christian Huitema
- Re: [quicwg/base-drafts] H3 spec fails to warn ab… Marten Seemann
- Re: [quicwg/base-drafts] H3 spec fails to warn ab… Christian Huitema
- Re: [quicwg/base-drafts] H3 spec fails to warn ab… Marten Seemann
- Re: [quicwg/base-drafts] H3 spec fails to warn ab… Christian Huitema
- Re: [quicwg/base-drafts] H3 spec fails to warn ab… Lucas Pardue
- Re: [quicwg/base-drafts] H3 spec fails to warn ab… Mike Bishop