Re: [quicwg/base-drafts] Use a "stream" for transmitting CIDs (#1826)
Kazuho Oku <notifications@github.com> Tue, 02 October 2018 19:47 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 BD50313112E for <quic-issues@ietfa.amsl.com>; Tue, 2 Oct 2018 12:47:19 -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 vVo8JW2shaaq for <quic-issues@ietfa.amsl.com>; Tue, 2 Oct 2018 12:47:17 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEA98131247 for <quic-issues@ietf.org>; Tue, 2 Oct 2018 12:47:09 -0700 (PDT)
Date: Tue, 02 Oct 2018 12:47:08 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538509628; bh=8L4Sf/9PkS9cohDpBz5Fw5XTN5lPp8WFq89w1JcRF8A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DfvW0eYc2oH6LY79RlHfChqHQf/BqBV+Kt1Fb6wq2JVH41tPi5bxmPzmdexaQpeK6 7b3533y5AI8tpzrdvUIvB/YBSeyFesfKCVR7YL7lyBTH5CFDRJavXf/24bnbCnRXaZ nB1NJFCNqHGcQbR7uoNgWqsyYLcMCBzM/B7UoBjY=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe878c1cfcfc67ebf374f1c86c9160230296ec56a92cf0000000117cb8d3c92a169ce15d12f59@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/426405814@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_5bb3cb3cc9b9e_45bd3f83afad45b89539d"; 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/Mx3UMGrjkAUJtJGsJFqXbDcgTCc>
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:47:20 -0000
> But CRYPTO has a limited lifespan and can be done in a hacked custom implementation without interfering with a highly tuned stream implementation. you could also hack the CID stream, but that is then another and longer living hack. I am not sure if that is true, considering the fact that CRYPTO stream for 1-RTT packets lives forever. > If stream frames need to be ordered, I think tagging a serial on them as proposed in the above is simpler. Then you have no FIN bit or RST whatever to consider. CRYPTO stream that "CID stream" reuses does not have FIN or RST. -- 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-426405814
- [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