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

Kazuho Oku <notifications@github.com> Tue, 02 October 2018 19:29 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 27F78130EF5 for <quic-issues@ietfa.amsl.com>; Tue, 2 Oct 2018 12:29:44 -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 D37a1sefDCjv for <quic-issues@ietfa.amsl.com>; Tue, 2 Oct 2018 12:29:42 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A267A131067 for <quic-issues@ietf.org>; Tue, 2 Oct 2018 12:29:42 -0700 (PDT)
Date: Tue, 02 Oct 2018 12:29:42 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538508582; bh=HOXmRzzKQZ9UOzHjWqWJr3LsMqNYK0f/9pCyNCCJ7Qs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=y4G5/yjga4eyLXYU0gI7KRc620Ar7X7cW0kKT5W+Rm+7nimzPg7pWkgLlOBEHYB7u 6XzAsiVze9KenMJy6j1Tfp16Ihxp6tJPJK0w4galrbkQ51r2Vpf99mKluP5V0nl0ZT 3Xet+APwBTia4bUOmJL1ng69/LoH+48DGSJSp04E=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab12cc76ca1208d7e9e4579cf0ecddde647d09544a92cf0000000117cb892592a169ce15d12f59@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/426400728@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_5bb3c725ee820_264c3f9bcf6d45c0196558"; 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/hAmQ8rLwxQedgrczA3VzUNWMG_0>
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:29:44 -0000

@marten-seemann @mikkelfj The proposed encoding of "CID stream" is exactly the same as that of the "CRYPTO stream". Why cannot you reuse that the same way you would reuse an actual QUIC stream?

>> Not carrying NEW_CID and RETIRE_CID as a "message" on top of "streams" also means that you would have a retransmission logic specific to those frames.
> 
> Why is that? They'd just be normal retransmittable frames, wouldn't they?

IIUC, there are two ways to send states. One is to retransmit frames. The other is to transmit the current state when necessary. For stacks that implement the latter approach, NEW_CID and RETIRE_CID will be a special-purpose logic. I am not saying that it is hard. But "retransmission of frames" is not all the stacks have as a concept.

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