[QUIC] Stream ID: 32 or 31 bits?

"Aron ." <aron.schats@gmail.com> Tue, 22 November 2016 15:09 UTC

Return-Path: <aron.schats@gmail.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 73624129A47 for <quic@ietfa.amsl.com>; Tue, 22 Nov 2016 07:09:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 tJVNsOQGJxMb for <quic@ietfa.amsl.com>; Tue, 22 Nov 2016 07:09:13 -0800 (PST)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (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 48E1312966C for <quic@ietf.org>; Tue, 22 Nov 2016 07:09:13 -0800 (PST)
Received: by mail-io0-x233.google.com with SMTP id j65so69612501iof.0 for <quic@ietf.org>; Tue, 22 Nov 2016 07:09:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=+mIOeip4EyeAQFI300ffA5pK+T43rtPmpj+CgeUSxRg=; b=0TMiF8pzy1y8CxriCdwJTL5YQK+83Dhzt0Ya6x9Aq5rIMVg+l5Z+KKzS1k/gKyC5Ry vkfZlq3hLWs7PGTfMj/ul+Qv1RS8c4+q8f5a9EcMGSbpdMr6SfJbD9kTD5WhJvA/YpDB 66C0qCZXUkfCHSvY685SUrPmDqhI5j6TUhG6roIElOJLZe1vemvCIH1NlwMpq8A8AHdS r8gcx2t8olnPQoSV+GXHJG3/VeorqyPZOzwy0qMRx/F6JDdw6rQ/0xDN0ugAr1Vnr1Ep +HBOe5lDCUPYk4ykvLnM1jHkJ6ngEwk15fv2qbngteiu8lUbQumNAjwcHEDQ4YRaVEM1 hPXA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=+mIOeip4EyeAQFI300ffA5pK+T43rtPmpj+CgeUSxRg=; b=jf+1QT1eHOf8np9gYyF/MjDgPXKvUKDRRpT/NsdHUZmZ44CnVbmg8vnK4AN5YYU1oH Xv/Cn84kEdJb7bciIcvp+Q1W7Jc8mJDbF0YyKmtI7cnEGZkydcNm7lXy6lDhU2cBWoGZ A3sQtgzvF5XkTGNwiZxFth24yC/H1gwjTN+6b3gfJ5+bQWQ89lMzxcNKdBzCMLk4a3B8 yKx13Lp9ghBP+jjRcQhLJko2kcrAuZvuyEgaIDbzbkDX5brGzv4SoMMjHRdjMmcOZBlY eTOx2bpinzY7aNJJGpDCrBxXON0lQA1J5D+sGwqvqTlRXyOKwADKW/SFXeGPo41/NI++ /OCg==
X-Gm-Message-State: AKaTC02mFBRtoHda867Mze8kTb6mz+nDJjOOZ60BsGvzv1sqvv95fvPZseWoXl1t31PK9zfMV2btMYIGAaNdHQ==
X-Received: by 10.107.22.6 with SMTP id 6mr19519539iow.8.1479827352457; Tue, 22 Nov 2016 07:09:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.79.125.138 with HTTP; Tue, 22 Nov 2016 07:09:12 -0800 (PST)
From: "Aron ." <aron.schats@gmail.com>
Date: Tue, 22 Nov 2016 10:09:12 -0500
Message-ID: <CAGudDpM9EJ_K-hpiCA1NMOfqkFJoCPnvSBCq9Z9B19i0-B1kqQ@mail.gmail.com>
To: quic@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c05b4eeac17ab0541e52744"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/jENl03yI5qFbF1ziSthRjeWSnN4>
Subject: [QUIC] Stream ID: 32 or 31 bits?
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 22 Nov 2016 15:09:14 -0000

Hello,

Section 8.2 (pp. 33-34) of [draft-hamilton-quic-transport-protocol-01]
states:

Streams are identified by an unsigned 32-bit integer, referred to as the
> StreamID.


Section 5.1.1 (p. 21) of RFC 7540 says that

Streams are identified with an unsigned 31-bit integer.


The format of frames QUIC uses on Stream 3 is the same as in HTTP/2,
seemingly creating a conflict.

Is this a conflict?  If so, how do we resolve it?

Thanks,

  Aron.