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

Marten Seemann <notifications@github.com> Tue, 02 October 2018 20:43 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 C4763131141 for <quic-issues@ietfa.amsl.com>; Tue, 2 Oct 2018 13:43:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.456
X-Spam-Level:
X-Spam-Status: No, score=-3.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_NONE=-0.0001, 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 NfVoxSAcp9t5 for <quic-issues@ietfa.amsl.com>; Tue, 2 Oct 2018 13:43:30 -0700 (PDT)
Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DC1C131165 for <quic-issues@ietf.org>; Tue, 2 Oct 2018 13:43:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=yhqr+VxTsZTiKKc1XoOR2KV0Y70=; b=CeWN8DEZ+FRr8W2y MgI5f+l60jEE9B2msKS9y9juQ4dgk53t22H887UTHU9Pjlqw2IbdhfkNQG+PE0uW zd6GaAXnrkSZXEtttxkP0uFTCp4rODzS4ul+3XvMuTHzkUpxdpViW34hUme+HnWH BFInlSEgR2tGXKQ+ZJpDUUJA9U8=
Received: by filter0401p1iad2.sendgrid.net with SMTP id filter0401p1iad2-10890-5BB3D871-A 2018-10-02 20:43:29.265911376 +0000 UTC m=+348965.126023365
Received: from github-lowworker-39ccb07.cp1-iad.github.net (unknown [192.30.252.40]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id nfPBp706R4-C1Q00PaQcbg for <quic-issues@ietf.org>; Tue, 02 Oct 2018 20:43:29.210 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-39ccb07.cp1-iad.github.net (Postfix) with ESMTP id 3184740001C for <quic-issues@ietf.org>; Tue, 2 Oct 2018 13:43:29 -0700 (PDT)
Date: Tue, 02 Oct 2018 20:43:29 +0000
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab87a4fc48edc3f82f2208774e71d48479c32feff092cf0000000117cb9a7192a169ce15d12f59@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/426422980@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_5bb3d87128f4d_2ec93f96336d45bc13489"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1mAKW1WzZk/+3U2TO9tsCLFlNwK3CRZ8gWJ7 yNY1j96LOgm/xlzpo3JMuMml2iq/RuYdOfdwtBRBtPeiTLpX0R5xIDgoYIg9Jf5E8vZeT2qbjXj0Tf iVExhIZA7dBP31SFpH+Kh6+hbBTZ+xDkUIhC48zC0358Sr2xMF9v+Lm1IihcUHXxGqy8sAbxVb1tVS A=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/p-WaHMU6Ld0UFh883whTeMySOpo>
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:43:33 -0000

> In my mind, using an actual stream (with STREAM and MAX_STREAM_DATA frames) eliminates the need for new frame types. Imagine a special flow-controlled CID stream. For simplicity, assume CIDs are 8 bytes long. If the flow control window is 64 bytes, writing 32 bytes to the stream (4 CIDs) will trigger a MAX_STREAM_DATA from the peer. This is the signal to write more CIDs to the stream. If the peer is not consuming the CIDs, MAX_STREAM_DATA is not sent and no CIDs are emitted.

That seems like a misuse of streams to me. You could end up with CID frames split up in the middle. I'm not saying that this wouldn't work, it just doesn't seem like a nice way to engineer a solution to me.

> The original objections to this was that the transport layer does not own the streams. I don't know how to respond to this. It seems that adding new frame types and protocol-like specifications around them for every new thing that we think to add to QUIC is not the most pragmatic thing to do. Take the CRYPTO frames, for example: chances are, they are just wrappers on the stream mechanism anyway.

They're not, in my implementation.
To me, using frames and protocol-like specification for new protocol features seems like exactly the way things should be.

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