Re: Implicitly opened streams and exposing stream IDs

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Tue, 03 April 2018 14:22 UTC

Return-Path: <dtikhonov@litespeedtech.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE0381277BB for <quic@ietfa.amsl.com>; Tue, 3 Apr 2018 07:22:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 i3s_S_ET4nu1 for <quic@ietfa.amsl.com>; Tue, 3 Apr 2018 07:22:24 -0700 (PDT)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (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 9589B124D68 for <quic@ietf.org>; Tue, 3 Apr 2018 07:22:24 -0700 (PDT)
Received: by mail-qk0-x229.google.com with SMTP id o205so18768192qke.3 for <quic@ietf.org>; Tue, 03 Apr 2018 07:22:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=JBXEoQeKHKGcO8BnZTPgz2OcatpeoJ5iAtkT/8uMSro=; b=J//CP5r1pysn4Pb6+aQzrSijPT6sG4QO0oLudMPwfGuIwC8HYaW6pdsdydCEqHkYrL KG/9JlJl+4MRfspwPY3mcbMHst+6BUowWkwbalHDZ+lkYoJ9mndVoF0h0gYOGNlB3OUS FKZByTK05rrJm4ib5nyXXhNE4u8I25WRvuTOTP2BACQ206fmSzSQGwDsXT5GI12zGUXx 9Isunhk1WHHjPO41moAZoHTVB7CzeDFUmR6Fjp8NQsVgbLOSn9+3aXUSeK5kgSGkDwIW drrAWbeEb0Snu1gai1yjN6Ho9bxOgyTTyizVeToTe4iSW0rXlDDhOk2gL0tR90Lwgjhd ujNw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=JBXEoQeKHKGcO8BnZTPgz2OcatpeoJ5iAtkT/8uMSro=; b=AVddXwG5FsI30g/Xu6Mm5BiJqWmUlIV3btm/Jc7KqDvU6dsMevMOIMB2SVrhQizm8y 9W78RA5kJNXAXtqgNYvzPO0dsGLTtAStwBPT5iketd6ws6NiSUQcaABSA8M5cShdyWpp lFjAA7xnfD5Wv5ewp2zkESBsfIQ4aFjcAoFTx1bHT6b9OjTYOb9zTFkR8sZzkQELov5V hoF9Kr4204GF4yrSqKmBi9y/KPGHe6H4q908VBCCUtJhIIo4GYQsX5zkgS+v8X1Dim3u 7ut3+urd3Lc/E0ulTlkpLZpE8HX0GjH1n4fDWgJv+mZ9KhBPHvstw4FPe8Nq1CbanWRH TWaA==
X-Gm-Message-State: ALQs6tBHFVGcg5wWvWhl7VxwB0gse/vOq61jZRqgdpeD2Sm4lPck5dUe GaeC84Et2BD6kFNSpVu8kovtDg==
X-Google-Smtp-Source: AIpwx493uGk0/1YY2JE363LyIWOYqSIcPOF7JqaZOpYGTw5eBh8G1BFU+23K2UYw/vcqZn8+TTDw4A==
X-Received: by 10.55.82.9 with SMTP id g9mr19236297qkb.313.1522765343727; Tue, 03 Apr 2018 07:22:23 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id 12sm2067222qkf.64.2018.04.03.07.22.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Apr 2018 07:22:23 -0700 (PDT)
Date: Tue, 03 Apr 2018 10:22:21 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Nick Banks <nibanks@microsoft.com>
Cc: Marten Seemann <martenseemann@gmail.com>, QUIC WG <quic@ietf.org>
Subject: Re: Implicitly opened streams and exposing stream IDs
Message-ID: <20180403142220.GF1695@ubuntu-dmitri>
Mail-Followup-To: Nick Banks <nibanks@microsoft.com>, Marten Seemann <martenseemann@gmail.com>, QUIC WG <quic@ietf.org>
References: <CAOYVs2qp3L-dTdFfBNDQT0Q=nCu+6Ew3gmF=0GMS2vVw1JfWCg@mail.gmail.com> <20180402174810.GA2015@ubuntu-dmitri> <20180403140009.GD1695@ubuntu-dmitri> <DM5PR2101MB090172E85926A0551FA64ACCB3A50@DM5PR2101MB0901.namprd21.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <DM5PR2101MB090172E85926A0551FA64ACCB3A50@DM5PR2101MB0901.namprd21.prod.outlook.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/_R1erCw_ppaCvyYTsJ9vr6QtaD4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Apr 2018 14:22:26 -0000

On Tue, Apr 03, 2018 at 02:05:04PM +0000, Nick Banks wrote:
> As to requiring the application rely on stream IDs, I was referring to Marten's first email that started this thread:
> 
> " For this stream mapping, it seems like the removal of implicitly
> opened streams implies that QUIC has to expose stream IDs to the
> application layer. I'm not sure if this was intended when making the
> change, especially since we're considering to change HQ such that it
> doesn't rely on QUIC stream IDs any more."

I think I found it:

  https://github.com/quicwg/base-drafts/issues/910

Thank you.

> I agree with this statement. For application protocols where they
> specific the "first stream" as the control stream, if you guarantee the
> first stream the application layer gets is always the first ordered
> stream, by ID, then they don't need to know the ID. Otherwise, then
> need to get the stream's ID to do the enforcement themselves.

I agree with the implication (no implicit open -> need Stream IDs),
but I do not have a problem with the implication itself.  I think
exposing Stream IDs is fine -- I will comment elsewhere in this
thread.

  - Dmitri.