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 02:58 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 551131203A3 for <quic-issues@ietfa.amsl.com>; Wed, 3 Apr 2019 19:58:40 -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 i_nYozA69apk for <quic-issues@ietfa.amsl.com>; Wed, 3 Apr 2019 19:58:38 -0700 (PDT)
Received: from out-12.smtp.github.com (out-12.smtp.github.com [192.30.254.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B283C12039E for <quic-issues@ietf.org>; Wed, 3 Apr 2019 19:58:38 -0700 (PDT)
Date: Wed, 03 Apr 2019 19:58:37 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1554346718; bh=z8fg89ZI1RfB/tJHVVoQTOX548Mx5PIoCGD1vBT89aQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wRi2wxV9o51aVUQv+vawWlTevgsQ+WSEmOWQMsqbsz65Nu7dm/dVH1dBkUOezgLbF dMOXpdWPi9WKfjB8ERFH9+MSkAA1duJpp2Fnl4U+/IpZIjZXJgmSOJCBnhf1KUs3dJ cYN+EDt7ng4byzCQ9iGk91pl9pa7T+KPzauNK61k=
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab79451944ab7e74d46bb95c97407db0123db82a0792cf0000000118bd34dd92a169ce1992e751@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/479731160@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_5ca572ddd6bab_325c3f99c8ed45bc3870fd"; 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/SbUskDdUtYdxzS6jbvI5RcXfRnM>
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 02:58:40 -0000
@marten-seemann the problem is that if the number of credit is zero, the peer cannot even open the stream. It is not supposed to send a null length stream frame. And if the stream is not even open, the generic transport has no way to know that it should send a MAX_STREAM_DATA frame on stream 2 or 3. An H3 conscious transport might know that, but a generic one not so much -- you don't need credits on stream 2 or 3 for HTTP 1.x or for DNS over HTTP. It seems much preferable to just mandate non zero values in the transport parameters. -- 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-479731160
- [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