Re: [quicwg/base-drafts] H3 spec fails to warn about initial_max_stream_data_uni (#2589)

Christian Huitema <notifications@github.com> Thu, 04 April 2019 03:45 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 D0958120336 for <quic-issues@ietfa.amsl.com>; Wed, 3 Apr 2019 20:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.383
X-Spam-Level:
X-Spam-Status: No, score=-6.383 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_24=1.618, 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 t2d9FnGY4N3p for <quic-issues@ietfa.amsl.com>; Wed, 3 Apr 2019 20:45:55 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1DA012031A for <quic-issues@ietf.org>; Wed, 3 Apr 2019 20:45:54 -0700 (PDT)
Date: Wed, 03 Apr 2019 20:45:53 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1554349553; bh=yLwSm1oLMlkatp0vjHdk62pscsMc3Ho8kEdx409b09o=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OMDHjBmEECpoRtE30BbMe0B3qZklJ5JcopPFjx0oTAMBck8GiFywofrKUF0bKH0fA RmMMdqPVafbLUWCFAfx52n8orlYheW5kF3G+5BtsdA8mYhHyuQQ2qZrbCPb3bZCiII wPbDb9/ShkPnBz4AwYICu2N2hrjbNjaCk/FYxB1o=
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abfcc07e2750eb10f470f5ea95435815ea1661052e92cf0000000118bd3ff192a169ce1992e751@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/479739149@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_5ca57df1bb7a7_449d3fba41cd45c0582a1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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/BrO6kQY1sbmZz3C8w8srfbETkLg>
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:45:57 -0000

It is not a "dead" lock. If picoquic does not have credits, it will just wait. If the peer somehow wakes up and provide credit, transmission will resume. In my mind, the transmission of the various "BLOCKED" frames is just optional.

-- 
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-479739149