Re: [quicwg/base-drafts] Use a "stream" for transmitting CIDs (#1826)
Marten Seemann <notifications@github.com> Tue, 02 October 2018 19:09 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 B2783130FF0 for <quic-issues@ietfa.amsl.com>; Tue, 2 Oct 2018 12:09:46 -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 lMAteZdOfNU3 for <quic-issues@ietfa.amsl.com>; Tue, 2 Oct 2018 12:09:45 -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 01A53130DC2 for <quic-issues@ietf.org>; Tue, 2 Oct 2018 12:09:45 -0700 (PDT)
Date: Tue, 02 Oct 2018 12:09:44 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538507384; bh=619ymwxNBN8141gCM/p8pnrIciM3Ybo4+qNrTjm5f64=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DKNDR0AIda/5m97lmqFPZR4TUIRCsIyFimP8El03r+bIYy8K21I9PzrOX8402z7Gz 09lpKtOCmrG6Oyj71IHSeB6ksRFhiS/KqspymjsAVkXlE3qjpp3/731v3zNyUOuSeA CM5OiNDGszZwl8+6qJpikY08I2oAVr42qyA+CX2M=
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab441f931006f26de04e6a3a7f4e3b991657ef638e92cf0000000117cb847892a169ce15d12f59@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/426394905@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_5bb3c2784ddb1_75503f919aad45c42368f0"; 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/Gv12LsLT0c_TAHbONanF5I0EdCM>
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:09:47 -0000
This sounds like an interesting proposal. I really like the idea of the MAX_NEW_CID frame, not because it would lead to code reuse (at least not for me), but because we're using the same design both for flow control bytes and for stream IDs. I'm wondering if we really need two different framing layers here (one for the CID frame and one for the CID message). Could we just introduce a sequence number for NEW_CID (which would be limited by MAX_NEW_CID), and keep RETIRE_CID as separate frame? -- 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-426394905
- [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