Re: Implicitly opened streams and exposing stream IDs

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Tue, 03 April 2018 14:00 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 EF53612E9D9 for <quic@ietfa.amsl.com>; Tue, 3 Apr 2018 07:00:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 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] 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 aMZZDc1Rj8xw for <quic@ietfa.amsl.com>; Tue, 3 Apr 2018 07:00:12 -0700 (PDT)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (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 47CDC12DA4A for <quic@ietf.org>; Tue, 3 Apr 2018 07:00:12 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id g7so6466600qkm.1 for <quic@ietf.org>; Tue, 03 Apr 2018 07:00:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=H1c9sU2oqh2gs6emfu1TFsOw7iCSALWzchYaV9Bx2nE=; b=rgKAfro4LP/E5+OvmbmTMVICr+kfyszX9WH4utIKSccPn0KQ8d5fZfZ0jZ+GCMEkQp kKjBwkGzPU+IBzzaZDAEr7anDOgA/4s58yaiVYwc6Vzs6Z10owql/SFAMZneFbNZyWTd Fe35R7kZtUtIenT1CSLtTMDSj9lCUMLDSrbo+JO097PPKvrksCaxivVzm3SFo7ASoHyi KJG9SFLmgt7tufKC2l63sQK364/PJVLnAkXFE2wGpQLJT13SYEgEp3cILaLRZmAQnctH G8iXlwbFJBEV55b1xs2cYzzUQfIsEJLQzK2IKgDGbJZMrYCcbD70vVRK4IG8/77qWIKm nR6w==
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:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=H1c9sU2oqh2gs6emfu1TFsOw7iCSALWzchYaV9Bx2nE=; b=B35p1599aK224VbYLNTol6eCk+hBaNI2QU5iIYzLETlMQiYpXk51pKpzseYT9kjCZG BSLnzohLpensHZtWIwosJaUZ1YZahku3+DKDDxuV6MBhagYRI+7VgY7PXxTg+1dgKX2i evAkohqk7ourKDgNa/+GLf1hUYQcrzAmlr49vBQ2D7jyGAbAUawmzVBln42sXfSCsXOr ZTDZy0h2ERakMdTO64LiKwdSRMlNcgZuWQcXmuwDgJLMO0QeUPVXABdNpIL65zD8b2/n /oZn6EEkkD2gf+fC7E8VgucoTFPy2qFpd71KH/fubpzBdfK+QGtuJ7zja+apCD3ajao3 p/fQ==
X-Gm-Message-State: ALQs6tCAHs0Ew2hVNzY84cYP+XJURkpwXBEFDTWNv8gLjSiQTx8l9rfZ 8zNtQGjOAtPP1HbPGrrR2RlFmxWs
X-Google-Smtp-Source: AIpwx49O2FBdpJ+qX1lL2bwYV4EFn4ugOXRR+4Ms1GayAVR6y6AxAT6H7VTro+sY2Pykbw2jaUi5+w==
X-Received: by 10.55.103.4 with SMTP id b4mr18446252qkc.138.1522764011457; Tue, 03 Apr 2018 07:00:11 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id d199sm2041456qke.90.2018.04.03.07.00.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Apr 2018 07:00:11 -0700 (PDT)
Date: Tue, 03 Apr 2018 10:00:09 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Marten Seemann <martenseemann@gmail.com>, QUIC WG <quic@ietf.org>
Subject: Re: Implicitly opened streams and exposing stream IDs
Message-ID: <20180403140009.GD1695@ubuntu-dmitri>
Mail-Followup-To: Marten Seemann <martenseemann@gmail.com>, QUIC WG <quic@ietf.org>
References: <CAOYVs2qp3L-dTdFfBNDQT0Q=nCu+6Ew3gmF=0GMS2vVw1JfWCg@mail.gmail.com> <20180402174810.GA2015@ubuntu-dmitri>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20180402174810.GA2015@ubuntu-dmitri>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-ymtCKmLWd7EQ7Fjguxs2jUGGXI>
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:00:14 -0000

I feel I am in some sort of discussion hole -- where was it first
discussed to get rid of relying on Stream IDs in the application
layer?  I'd like to get some background.

  -Dmitri.

On Mon, Apr 02, 2018 at 01:48:10PM -0400, Dmitri Tikhonov wrote:
> On Mon, Apr 02, 2018 at 11:43:23AM +0000, Marten Seemann wrote:
> > In this case, after accepting a stream, we first have to check the stream
> > ID, since there's no guarantee if the control stream will actually be
> > received first.
> > 
> > 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 don't see a problem with that -- HTTP is the application layer, and
> the draft specifies that streams 2 and 3 are the control streams.
> 
> > 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.
> 
> Are you referring to a specific pull request or an issue on GitHub?
> (I must have missed it.)
> 
>   - Dmitri.