Re: [quicwg/base-drafts] Use a "stream" for transmitting CIDs (#1826)

Kazuho Oku <notifications@github.com> Tue, 02 October 2018 21:07 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 4135513116D for <quic-issues@ietfa.amsl.com>; Tue, 2 Oct 2018 14:07:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
X-Spam-Status: No, score=-8 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] 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 x9ztXCXgdT07 for <quic-issues@ietfa.amsl.com>; Tue, 2 Oct 2018 14:07:27 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 817BA131182 for <quic-issues@ietf.org>; Tue, 2 Oct 2018 14:07:27 -0700 (PDT)
Date: Tue, 02 Oct 2018 14:07:26 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538514446; bh=JlCnGREAm2kt14r2ysNdys98mr/esIAPDSr6yU/S/JM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1jkVtlg0K2YRWo25tRAXUmgEpCV0+NHuvnyR13ubPqiR8/tP7a0w3YSOtRrcQXOiu Gpjt7cFTUFmLsstye5AGM03IigURKGpyZolT8XYZXRsKG6d8h+3XGSv4LofXgHCUtX jOgrZEQ2plwiaDq9wn8FWxBs0oteIpppU5GzlS60=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2d30e305020a7b6b74da34d8b67bad9d58101eb492cf0000000117cba00e92a169ce15d12f59@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/426430637@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_5bb3de0e7aa1b_27533febd10d45c419993d"; 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/YgXT-a1Ehr_WNj2wnaRaDsWlxPY>
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 21:07:29 -0000

@MikeBishop FWIW, I do not think that flow control of CIDs is essential, even though I included that in this proposal. CRYPTO streams do not have flow control, and "CID frames" would work fine without flow control too (assuming that we continue allowing the receiver to "forget" CIDs).

> there's also the retire issue -- stream data is never really "retired." 

Would you mind elaborating on this? For the CID, the proposal has a RETIRE message. But I assume you are referring to something else.

> Also, while there are reasons we want all sequence numbers to be generated in order, there's no reason you need to block using CID 7 because you haven't seen CID 6.

That's correct. But it is still a requirement for book keeping. My point is that it would be worthwhile to consider reusing the "streams" approach, if we are to require book keeping using sequence numbers in a situation where HoLB is not a concern.

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