Re: [quicwg/base-drafts] Use a "stream" for transmitting CIDs (#1826)
MikkelFJ <notifications@github.com> Tue, 02 October 2018 19:26 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 E9093130EF5 for <quic-issues@ietfa.amsl.com>; Tue, 2 Oct 2018 12:26:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.456
X-Spam-Level:
X-Spam-Status: No, score=-8.456 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, 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] 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 PlgUjF86O4up for <quic-issues@ietfa.amsl.com>; Tue, 2 Oct 2018 12:26:18 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 016E1130DC2 for <quic-issues@ietf.org>; Tue, 2 Oct 2018 12:26:17 -0700 (PDT)
Date: Tue, 02 Oct 2018 12:26:16 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538508376; bh=CcXu3dPI9XYZ+pk+rTXwXmmvn/dpC9o9oPz/jOvEJ3k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=M5oNQcpqtK0xzzXfWRgP6rc2MAcKOQSwpk1TtHCARRcxVPi48leHdrTIFGXwNt7vA V0tuiNyjbqVnUmaBEwIFVxa7oX7mjvELFkFwUeYveENbzdlVuH/omopoIQQ6JHHPhY P9xwPgMt7MUv2srn0agmmtHL41WrALl0EQTMRG70=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab984568ce1f628dbdcbea7a8d3b8f59abb6ef25a292cf0000000117cb885892a169ce15d12f59@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1826/426399735@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1826@github.com>
References: <quicwg/base-drafts/issues/1826@github.com>
Subject: Re: [quicwg/base-drafts] Use a "stream" for transmitting CIDs (#1826)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bb3c658b6c9e_5943fbdf02d45b81286cf"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/q2iaU6sFs0vO4jU4Vd8AsAUSR6Q>
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: Tue, 02 Oct 2018 19:26:20 -0000
Conceptually I like the idea, however: They are not streams, and they will be an odd special case in the stream logic. All the nice automatic handling via stream semantics become one big special case. You can give at a pseudo stream id and feed it into the the pipeline unless you starting with modulo 8 stream id's. I'm not saying the alternative isn't just as bad, but I don't see this as an easy win. -- 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/1826#issuecomment-426399735
- [quicwg/base-drafts] Use a "stream" for transmitt… Kazuho Oku
- Re: [quicwg/base-drafts] Use a "stream" for trans… Nick Banks
- Re: [quicwg/base-drafts] Use a "stream" for trans… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Use a "stream" for trans… Kazuho Oku
- Re: [quicwg/base-drafts] Use a "stream" for trans… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Use a "stream" for trans… Marten Seemann
- Re: [quicwg/base-drafts] Use a "stream" for trans… Kazuho Oku
- Re: [quicwg/base-drafts] Use a "stream" for trans… Marten Seemann
- Re: [quicwg/base-drafts] Use a "stream" for trans… MikkelFJ
- Re: [quicwg/base-drafts] Use a "stream" for trans… Kazuho Oku
- Re: [quicwg/base-drafts] Use a "stream" for trans… MikkelFJ
- Re: [quicwg/base-drafts] Use a "stream" for trans… MikkelFJ
- Re: [quicwg/base-drafts] Use a "stream" for trans… Kazuho Oku
- Re: [quicwg/base-drafts] Use a "stream" for trans… Nick Banks
- Re: [quicwg/base-drafts] Use a "stream" for trans… MikkelFJ
- Re: [quicwg/base-drafts] Use a "stream" for trans… Kazuho Oku
- Re: [quicwg/base-drafts] Use a "stream" for trans… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Use a "stream" for trans… Marten Seemann
- Re: [quicwg/base-drafts] Use a "stream" for trans… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Use a "stream" for trans… Marten Seemann
- Re: [quicwg/base-drafts] Use a "stream" for trans… Mike Bishop
- Re: [quicwg/base-drafts] Use a "stream" for trans… Kazuho Oku
- Re: [quicwg/base-drafts] Use a "stream" for trans… Mike Bishop
- Re: [quicwg/base-drafts] Use a "stream" for trans… Kazuho Oku
- Re: [quicwg/base-drafts] Use a "stream" for trans… Kazuho Oku
- Re: [quicwg/base-drafts] Use a "stream" for trans… janaiyengar
- Re: [quicwg/base-drafts] Use a "stream" for trans… janaiyengar