Re: [quicwg/base-drafts] Why do control streams need to be typed? (#2224)

Martin Thomson <notifications@github.com> Fri, 21 December 2018 04:09 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 3A181130DCE for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 20:09:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.447
X-Spam-Level:
X-Spam-Status: No, score=-6.447 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_24=1.618, 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 tCmnnwGXfMvJ for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 20:09:57 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD65A12D7EA for <quic-issues@ietf.org>; Thu, 20 Dec 2018 20:09:56 -0800 (PST)
Date: Thu, 20 Dec 2018 20:09:56 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545365396; bh=+OVefs3/n857wssR8NCdUbxqrGoQWTjEqPHmkwD5HFg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HfMMTaTF2VmRlH++RQm2A5RT0Gy296DcFFsnuUVTGAESVe6iX5b8lFqvlJhtgBXij F5JLeQgU7rRdhI3096XkWAiIAuFxsrhDwDC68YsAQyXrTWm00PLFC2Tt334+ih7+MB SwKIwfd1AJVvOO7NmHOXlwSTN7vetR4tCtr5qr7k=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb6065f3a971954b8022599452b0a24b5d740a70392cf000000011834299492a169ce17706d7a@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/449239697@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_5c1c679421762_fec3fd2722d45b816028c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/53dwSJM3hFtlD7LMKgnTehDY0Pg>
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: Fri, 21 Dec 2018 04:09:58 -0000

Oh, if we're having this discussion again, I'd like to point out that the type byte simplified my implementation considerably.  That was all part of the discussion last time around though.  I'm not seeing new information.

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