IETF Logo Mail Archive

Re: [QUIC] Stream ID: 32 or 31 bits?

Ian Swett <ianswett@google.com> Tue, 22 November 2016 17:43 UTC

Return-Path: <ianswett@google.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 B292F129A65 for <quic@ietfa.amsl.com>; Tue, 22 Nov 2016 09:43:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 3Zm78gGZ46Ph for <quic@ietfa.amsl.com>; Tue, 22 Nov 2016 09:43:27 -0800 (PST)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (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 97ED0129A2D for <quic@ietf.org>; Tue, 22 Nov 2016 09:43:27 -0800 (PST)
Received: by mail-yw0-x22c.google.com with SMTP id i145so20737151ywg.2 for <quic@ietf.org>; Tue, 22 Nov 2016 09:43:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hJ46/INr0zSOV+aultU6sy3uTSRdiT821lBq4Kv57Fc=; b=EjbBj/43B2/Kr+tAizjLSdZBhNUMDV8IowmnuVLoj2fTHizMWiZtgwMnimHJSQOAY4 bSyyUFiwlSAutsj7Aq07utb3PGMEeUv2Q8sj+kPeRELyEpczBxub9diUY/6bLxhCjw8A vPuaseG2lgITRSSm6AKd7mW6Jr1tVI7wF6u9FydNhktYyUn6d0eh+PCiU0QpO+pDs6F3 +ie8o46TovVOc4nv2ViuQFwkbZKzys7kkTwUGYWPKnZpn+mg5c1Sis2vwHQNWAlz3lN4 p+MaINJV38V2ZyOFeMXi5cBWUCO20CGw5BHAz+uP6uVHl47aWmGZ9zYOm0QmMrfIoxdI CYwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hJ46/INr0zSOV+aultU6sy3uTSRdiT821lBq4Kv57Fc=; b=H1JYb5kCLozGcVZ0qhz0HsBIcD5IucbmJ87v8/CI8M6uYTNQVb68ZZEY30zw5OAIyc joI3MqRvbLwdvIDApvZixrk/0sqvm2a7hbPlfhyWWTGJ/rEDdbtME97ARi8Ihpg2ER3X PaK9ktyQFtTfMWqZvir1BC60cQ2uAUTP20ybTI0PaPcx3/K21cAuApuEMPgBHA7aIiCW wGkxE2NYMjGc5hPGzClKhXIm6yuiVB39FxrxIocE5ikohrGpB0DysYHcrtUdtXaulLQJ rUHGv6MHayn+oyADCT103PoJEcR5AOPzRKcQFDuXgzXR9Ml1Of5g/3pHjiVPQyTlYOOH Zg4w==
X-Gm-Message-State: AKaTC01Ss99QlsoSCfpovMnm99Q6gCmQJmFCASaGd3cnCTMiVYpjXjoMPHD1zbpAallV+phMjeGA1G1ZImy9YFXL
X-Received: by 10.129.168.131 with SMTP id f125mr24241680ywh.215.1479836606726; Tue, 22 Nov 2016 09:43:26 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.4.88 with HTTP; Tue, 22 Nov 2016 09:43:05 -0800 (PST)
In-Reply-To: <CAGudDpM9EJ_K-hpiCA1NMOfqkFJoCPnvSBCq9Z9B19i0-B1kqQ@mail.gmail.com>
References: <CAGudDpM9EJ_K-hpiCA1NMOfqkFJoCPnvSBCq9Z9B19i0-B1kqQ@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Tue, 22 Nov 2016 12:43:05 -0500
Message-ID: <CAKcm_gNX4mbGG-6KoG9y8yLwwLoysi6zUwRvZnMce9ZaNrXQ1w@mail.gmail.com>
To: "Aron ." <aron.schats@gmail.com>
Content-Type: multipart/alternative; boundary="94eb2c13cbe24578700541e74f8c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/bgPtW1Cf1YoQgUERQXlg9FWlPwo>
Cc: quic@ietf.org
Subject: Re: [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 17:43:33 -0000

I think that is something for the HTTP2 mapping document to answer.  As
long as QUIC has more than enough stream ids to represent the full 31 bit
space, I don't anticipate any problems.

On Tue, Nov 22, 2016 at 10:09 AM, Aron . <aron.schats@gmail.com> wrote:

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

v2.23.0 | Report a Bug | By Email