Re: [quicwg/base-drafts] Interleaved Stream IDs are awkward (#1430)
Kazuho Oku <notifications@github.com> Wed, 13 June 2018 02:29 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 01EAE130EC2 for <quic-issues@ietfa.amsl.com>; Tue, 12 Jun 2018 19:29:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 BMkmw_bBya4x for <quic-issues@ietfa.amsl.com>; Tue, 12 Jun 2018 19:29:03 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C68B813102D for <quic-issues@ietf.org>; Tue, 12 Jun 2018 19:29:03 -0700 (PDT)
Date: Tue, 12 Jun 2018 19:29:03 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528856943; bh=0z+PtdxA2lKp/MbZOX9/J6dBZCJ/YPB4spa44Lj0ipU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KCnV+sDloGsFBEFPRXceZ2d9jGgfK05QRrTqeNYknB0xYi4Ai3wtMXE+dduEF5UNL Fdn0vgk3fI1tuJJUWT2ZmK4O0mGzuxZ0BcjK8+JLFWdVKaV/h0FgAU/FcihkFzuBpl N+u8FR1ASCY5F7Kfsj5/V8Fbw3VK2DgOQOfMwpSY=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abcd0b04731e9068ef09020d9fcf43bf63548ca76892cf000000011738436f92a169ce13b4e093@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1430/396793738@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1430@github.com>
References: <quicwg/base-drafts/issues/1430@github.com>
Subject: Re: [quicwg/base-drafts] Interleaved Stream IDs are awkward (#1430)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b20816fd65c_78a53fc84cda2f88672345"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/u4yF_zQUYicOF3HSyH28Vx8k2fQ>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
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: Wed, 13 Jun 2018 02:29:17 -0000
> I'm wondering whether we could alternatively fix this in text only. If we say that the stream type is indicated by the two low bits of the field, and the Stream ID within the type is indicated by the remaining upper bits of the number, then you get to the same place (indicating streams as 1us, 3bc, etc.) without modifying the bits on the wire. That's basically just codifying a change in presentation / reference terminology. @MikeBishop I am not sure if I like the approach. Within the implementation, I would like to use an integral type to determine a stream. I'd assume that would be the same for others. Using the low-bits for determining the type will mean that we will be calling, for example, a stream represented by a number of `4` as `1bc`. To me, it is more confusing than the current scheme. -- 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/1430#issuecomment-396793738
- Re: [quicwg/base-drafts] Interleaved Stream IDs a… MikkelFJ
- Re: [quicwg/base-drafts] Interleaved Stream IDs a… Mike Bishop
- Re: [quicwg/base-drafts] Interleaved Stream IDs a… Kazuho Oku
- [quicwg/base-drafts] Interleaved Stream IDs are a… Mike Bishop
- Re: [quicwg/base-drafts] Interleaved Stream IDs a… MikkelFJ
- Re: [quicwg/base-drafts] Interleaved Stream IDs a… MikkelFJ
- Re: [quicwg/base-drafts] Interleaved Stream IDs a… ianswett
- Re: [quicwg/base-drafts] Interleaved Stream IDs a… ianswett