Re: [quicwg/base-drafts] Why do control streams need to be typed? (#2224)
Nick Banks <notifications@github.com> Thu, 20 December 2018 23:28 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 0AB05130EE1 for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 15:28:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.064
X-Spam-Level:
X-Spam-Status: No, score=-8.064 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 MAnWjIMPAE4n for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 15:28:38 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34A7413110D for <quic-issues@ietf.org>; Thu, 20 Dec 2018 15:28:38 -0800 (PST)
Date: Thu, 20 Dec 2018 15:28:37 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545348517; bh=nL5phW98INJLRTz8KcWz4Hzbr6T1MzGFNBjrf5ehnjc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=R8VIMdNOluCEvhiEdbRNbMBVgPLdunB2U/Lw2UU8RHuqdX0GEOSz7SJoq8+qfmyZc 67b8reFaFDs5goXqW83Wxt4tk4vYwdxkG+hRfNNGtzJ9JnecNy4jKT5TA0mlXnDcwP ZkhulL2+fkNJqeTsP012pKq5WA5ZHN5ce4Lc4AiE=
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4f2ae1026cce5c3ea591bb4804a4c3f2f093696a92cf000000011833e7a592a169ce17706d7a@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2224/449173046@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2224@github.com>
References: <quicwg/base-drafts/issues/2224@github.com>
Subject: Re: [quicwg/base-drafts] Why do control streams need to be typed? (#2224)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c1c25a53c94f_357a3f884b8d45c4234696"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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/krWM02F-KfRsY0PldVVqA5__baI>
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: Thu, 20 Dec 2018 23:28:40 -0000
@ekr I'd argue that depends on the implementation. With WinQuic there is no reason for the app layer to ever deal with a stream ID. Our API has a different flag for unidirectional/bidirectional streams. If the transport receives a high stream ID frame that ends up implicitly opening a number of streams, the app layer gets a callback indicating all those new streams have now been opened, with each callback containing the flag indicating unidirectional/bidirectional. -- 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/2224#issuecomment-449173046
- [quicwg/base-drafts] Why do control streams need … ekr
- Re: [quicwg/base-drafts] Why do control streams n… MikkelFJ
- Re: [quicwg/base-drafts] Why do control streams n… ekr
- Re: [quicwg/base-drafts] Why do control streams n… Nick Banks
- Re: [quicwg/base-drafts] Why do control streams n… Ryan Hamilton
- Re: [quicwg/base-drafts] Why do control streams n… MikkelFJ
- Re: [quicwg/base-drafts] Why do control streams n… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Why do control streams n… ekr
- Re: [quicwg/base-drafts] Why do control streams n… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Why do control streams n… Ryan Hamilton
- Re: [quicwg/base-drafts] Why do control streams n… Kazuho Oku
- Re: [quicwg/base-drafts] Why do control streams n… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Why do control streams n… Martin Thomson
- Re: [quicwg/base-drafts] Why do control streams n… Kazuho Oku
- Re: [quicwg/base-drafts] Why do control streams n… Lucas Pardue
- Re: [quicwg/base-drafts] Why do control streams n… Mike Bishop
- Re: [quicwg/base-drafts] Why do control streams n… Mike Bishop
- Re: [quicwg/base-drafts] Why do control streams n… Mike Bishop