IETF Logo Mail Archive

Re: [quicwg/base-drafts] Specify what occurs when the maximum Stream Id exceeds 2^62 - 1 in MAX_STREAMS (#2487)

Jana Iyengar <notifications@github.com> Fri, 22 February 2019 04: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 6EB11130E90 for <quic-issues@ietfa.amsl.com>; Thu, 21 Feb 2019 20:58:18 -0800 (PST)
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 PxI0aS6hgob2 for <quic-issues@ietfa.amsl.com>; Thu, 21 Feb 2019 20:58:17 -0800 (PST)
Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E20BA128D52 for <quic-issues@ietf.org>; Thu, 21 Feb 2019 20:58:16 -0800 (PST)
Date: Thu, 21 Feb 2019 20:58:16 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1550811496; bh=ZbC1gS69QiKYiZk0fuPNgk8Xu4Sk2jRcmkrVfTqGrD4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YtlqpbO7I4He1QnuwIQY7PKC0LTImy8S6Yl5wCz9ueDeI5yyNFB0H1Faz71mofsCq BL24eUH9mhiAT88Qk2AKEE6foqJK+1wBsXh5ivklDCZmUJTgrzDnPNoxhwCgbcfgT0 IQxOeSIiEdrORjoWGZmy0cq3OyYRx5NzrKt2r4fw=
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab53026c577a29cab03d66fdf305fa586ee9d7a0a492cf000000011887436892a169ce18a000a6@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2487/466274109@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2487@github.com>
References: <quicwg/base-drafts/issues/2487@github.com>
Subject: Re: [quicwg/base-drafts] Specify what occurs when the maximum Stream Id exceeds 2^62 - 1 in MAX_STREAMS (#2487)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c6f81682b27e_322c3faf73ed45c45278b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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/H-hzPf86fe1Rm29qoq5-Nr_u1fE>
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: Fri, 22 Feb 2019 04:58:18 -0000

I don't have a strong opinion, but this seems like a bug at the peer. I would be inclined to specify that an endpoint MUST NOT advertise max streams that are too large, and close the connection (with PROTOCOL_VIOLATION) if a value is received that is too large.

-- 
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/2487#issuecomment-466274109

v2.23.0 | Report a Bug | By Email