IETF Logo Mail Archive

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:17 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 4778F12012F for <quic-issues@ietfa.amsl.com>; Wed, 3 Apr 2019 20:17:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.597
X-Spam-Level:
X-Spam-Status: No, score=-1.597 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 To0rY3MEgQkh for <quic-issues@ietfa.amsl.com>; Wed, 3 Apr 2019 20:17:57 -0700 (PDT)
Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53FBE120021 for <quic-issues@ietf.org>; Wed, 3 Apr 2019 20:17:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=etnmVgMjzHsXxVxLG7/RDqtUJHA=; b=t8xeHazqKYgWFyYU tc0JUhDTJWelPGOfoy/FboWwn651ACrVpunXiWB1d2UDfqzR3ri1a6t3oXasbyAw wvt0srz6mdyP0Ccgbnm730vHdQGDTBHmezEJNw0N9/WNLivE/62oAQP7d9reEz6I IN6vhYpa26qaauEk+wYrDoXO0Ps=
Received: by filter0440p1iad2.sendgrid.net with SMTP id filter0440p1iad2-29648-5CA57763-2E 2019-04-04 03:17:55.833040564 +0000 UTC m=+1173370.019610049
Received: from github-lowworker-63e61ec.cp1-iad.github.net (unknown [192.30.252.36]) by ismtpd0015p1iad2.sendgrid.net (SG) with ESMTP id rZnet3QYS_ePZOwXZTQARg for <quic-issues@ietf.org>; Thu, 04 Apr 2019 03:17:55.887 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-63e61ec.cp1-iad.github.net (Postfix) with ESMTP id E098C2A03DE for <quic-issues@ietf.org>; Wed, 3 Apr 2019 20:17:55 -0700 (PDT)
Date: Thu, 04 Apr 2019 03:17:55 +0000
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab87573e34b43a8c6ea8ec51b0968f119ce00ce66692cf0000000118bd396392a169ce1992e751@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/479734401@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_5ca57763df2b2_41ba3ff47bcd45c466996b"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3rpPAmgQQBEbfInMWMf3dNWiISEk5yVrh/FG GIrHlI4tDNwDoZfK+oRIGbWEluYP5vzpXXbIQ95/li93QKVPM0emPjAnMjWMMAVn+yvCC45cxdQWYi mtl254BQ9caRP72LBIvwDXFKmq9dIdOSmlIUgrNE0mEj/wOLLjGKflAiBO0Zu4c7LAfvhhp0u0mB4Y k=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/f-erOvQsQN2KzO0N47WpBEQTt7E>
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:17:59 -0000

@marten-seemann I suppose you could send a zero length STREAM frame, although I am pretty sure one of spec says that nodes should not send zero-length stream frames because DOS attacks. STREAM_BLOCKED has a different meaning -- it does not actually open the stream. I suppose that STREAM_DATA_BLOCKED would work. In any case, asking for a sensible initial limit seems much simpler.

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

v2.23.0 | Report a Bug | By Email