Re: [quicwg/base-drafts] Use a "stream" for transmitting CIDs (#1826)
Marten Seemann <notifications@github.com> Tue, 02 October 2018 20:18 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 60CA4130FF0 for <quic-issues@ietfa.amsl.com>; Tue, 2 Oct 2018 13:18:11 -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 NkwRD2uo_xKu for <quic-issues@ietfa.amsl.com>; Tue, 2 Oct 2018 13:18:09 -0700 (PDT)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1926813112E for <quic-issues@ietf.org>; Tue, 2 Oct 2018 13:18:07 -0700 (PDT)
Date: Tue, 02 Oct 2018 13:18:06 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538511486; bh=5mQUTQMNCsgX23PxzSxFS5poqsUbS1Dw7cP86S9At44=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iDY66mf3yDwejIyYLTYOtHatGfmQaEvbPxw1hY00w1fMqSBYTGMaX3YQyVHqA+5GS ybB1zXyiJrU+CK1CXiIGqFaNqtH+a3+KwW6HI0YxrtxIm07CATbI6E97yr2o/1/li4 a6LL84ZxGDNmgUUYCUAs9qmS9HhzU6N2gC7ZOa1o=
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf2ba202c01fe0de99ff5856ec18eb9ccc43cb99c92cf0000000117cb947e92a169ce15d12f59@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/426415126@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_5bb3d27e9db6_20a03feeebad45c03911a0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: marten-seemann
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/NylPnnhpAS0-IE9SupDRSLghUDU>
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 20:18:12 -0000
> As I have stated earlier, it is beneficial to use a proven method because we are at a later moment like this, instead of trying to fix all the design issues of a framework specific to transmitting CIDs that we haven't seen any interop. The proven method here is the use of the MAX_NEW_CID frame (because we have that kind of frame for flow control and stream IDs). I'm not sure if putting things on a "stream" will actually simplify implementations. Maybe we can combine your proposal of the MAX_NEW_CID with my proposal of adding a sequence number? -- 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-426415126
- [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