Why mandate stream creation order?
Dmitri Tikhonov <dtikhonov@litespeedtech.com> Wed, 31 May 2017 15:23 UTC
Return-Path: <dtikhonov@litespeedtech.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 912091286D6 for <quic@ietfa.amsl.com>; Wed, 31 May 2017 08:23:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 MNjQRxfr1FlV for <quic@ietfa.amsl.com>; Wed, 31 May 2017 08:23:52 -0700 (PDT)
Received: from mail-qt0-x242.google.com (mail-qt0-x242.google.com [IPv6:2607:f8b0:400d:c0d::242]) (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 F3AF81274D2 for <quic@ietf.org>; Wed, 31 May 2017 08:23:51 -0700 (PDT)
Received: by mail-qt0-x242.google.com with SMTP id l39so2274926qtb.1 for <quic@ietf.org>; Wed, 31 May 2017 08:23:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=message-id:mime-version:to:from:subject:date:importance; bh=zjBQhncBiXsbe6+sUnrCJNjQWFab0KEbZEqjypiAM68=; b=JHYhM6hHwhhBS/6zZIElzmY6thconI9PujIOVEgfEYCAb6HQL2TP1phi8QXTaWdF5/ 62tNjhdekIW/uNrytzeR8+FLaDnZcuPMZlY+qw+WNdcveDh38406z3QAh9cFPIdoLTKk 3a3X4tS0oIMcf45TGuYIMt91AoUn5HSdLcjdZHovToTxBD9xmnJKglDdcvGpiCD91HGu EnSbWfxud1Xhd7NTbwJS9Dz7mUwcUkLPdeKvVbY2E3wq7T6opiNlt4hv+cUO0gYF5dit 7F7cJTU3GvlhSAZwg7tDAyP5xAAK4eaYz/J+khIZt2ktJthD86muF7FCmb21gqE2FUT3 z+GQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:mime-version:to:from:subject:date :importance; bh=zjBQhncBiXsbe6+sUnrCJNjQWFab0KEbZEqjypiAM68=; b=Of5scnelGOwRXTGEfrsO2kgq/qYESiZGRtPjTENIQqDYW0I3tIeU6PQ6sMjYHhvvo8 wrtZbJiJUFTyOe+oZnmK0/n/wW7Bb65ajXnJi99KMxwqI92oD5ooogd8Z6JVACLi7jGH FFHou0XePpwZsZX7IjXbCIz58ZVmVqT4qiD00rMNrNkoHyxILeAF8/h2M4wldkHKrW/Y csRNIBhRe1XVweI8WkYJy7I4V3qdYmLQd1mqK7GoL+8hW9YDzE/4/7clc8u1JfR74408 UZ7CZ0Z/EPZynwLrvcOO5japzJuSnDpn6SdbIk7j43W1mJpZQjmCA2FiAGGRMt0muW0r TbRw==
X-Gm-Message-State: AODbwcDXNHwjI2q59Ty9CE3b2vDLr7qB00IZg7dAzzoxe46YFKUDtEDI /+9I+ZIf8gxJhqFY85BUGw==
X-Received: by 10.200.49.229 with SMTP id i34mr29693438qte.113.1496244230900; Wed, 31 May 2017 08:23:50 -0700 (PDT)
Received: from ?IPv6:::ffff:192.168.0.196? (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id j204sm10621371qke.27.2017.05.31.08.23.49 for <quic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 May 2017 08:23:50 -0700 (PDT)
Message-ID: <592ee006.d5a0370a.621c9.06bf@mx.google.com>
MIME-Version: 1.0
To: "quic@ietf.org" <quic@ietf.org>
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
Subject: Why mandate stream creation order?
Date: Wed, 31 May 2017 11:23:48 -0400
Importance: normal
X-Priority: 3
Content-Type: multipart/alternative; boundary="_B18CACBF-CAC9-4E68-8691-707865F4EED7_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/tRARSK89PRIjvFxc6620ikoFfa8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 May 2017 15:23:53 -0000
Hello, Section 10.1 of draft-ietf-quic-transport-03 states that “Streams MUST be created in sequential order.” My question is: why mandate stream creation order, since the other side may receive out-of-order packets? Let the implementation do what it wants with Stream IDs – as long as it does not go over the limit, all should be well. This phrase is a holdover from the previous version; this requirement seems to be unnecessary since issue 435 has been resolved. - Dmitri. P.S. I have read CONTRIBUTING.md and decided that mailing list is the way to ask this question, rather than opening a GitHub issue. If this is incorrect, please let me know.
- Why mandate stream creation order? Dmitri Tikhonov
- Re: Why mandate stream creation order? Jana Iyengar