Re: Clarification on HTTP/QUIC Unidirectional Streams
Dmitri Tikhonov <dtikhonov@litespeedtech.com> Wed, 17 October 2018 17:52 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 31165130E19 for <quic@ietfa.amsl.com>; Wed, 17 Oct 2018 10:52:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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 k6F-RfC_U3mz for <quic@ietfa.amsl.com>; Wed, 17 Oct 2018 10:52:10 -0700 (PDT)
Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (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 11764130E02 for <quic@ietf.org>; Wed, 17 Oct 2018 10:52:10 -0700 (PDT)
Received: by mail-qt1-x82d.google.com with SMTP id o17-v6so31130821qtr.1 for <quic@ietf.org>; Wed, 17 Oct 2018 10:52:10 -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:content-transfer-encoding :in-reply-to:user-agent; bh=dS8biGifFXESIO/SwWeX5nzzHD5mz7QgQJLTqyG+PSU=; b=epIuP2bNvPtKvaSB2XKh3qi1VS4wZR7BxmbLTJa2aMHnfCNv+sxQWiCyPzfqtolNWg JiKAtc8o57r+ZhKPWM3zslQu4e+ycxDfwikk1JSF26+5hwTJden0xbjrc9ut0AHFfNBs 6pxWbTrp4PnoyJue8KTe1y4rg/9bA5wREkBDfvri7XRqFgS+x42oxr6SmqZVG+5IFo+8 OvHNtJD4pqKqW87g1J5QtcxCIt2rSiBF2pW6Tssv89eSrxM5OafSGPOvgN7bAyFpjWH4 5QlVlVP/8ErhzQuh0YBErccuXOJPIoReX6DYqGIgMrL1gZrsNJsjRzzT+Vmp6TJkzOzF xCVw==
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 :content-transfer-encoding:in-reply-to:user-agent; bh=dS8biGifFXESIO/SwWeX5nzzHD5mz7QgQJLTqyG+PSU=; b=kaXbo3kOJAiyGDt40ZLJGnaJuNbAKTEAy/lKplDtARiSmnB9zO9HtLbv7Rxl1ZCVL8 fj9mi7no09VfrKCdkCJHUh/xB9Yi3pltP5uA9CnXSjjqVY5rEpRA6+tiZyzK4RGUcXpJ bVbpJu/a60awG8+UrvSdT+0VKUjUoL4ehwGWnjUxXjqoLmx28oPHvzUyCTeDyNTySplg GNWdHKwLDvgDh7VIUThYcZuWtpbGGsI9HkwulHadujZmY4fV/cBicZ/np2dBMjmxPBWd aZHZtx917K/vdNWISlrRD+NHMEI4Op++UzXE2/sSPirrNulcegL4Lm2WDTe5SNvF1PHI FyIQ==
X-Gm-Message-State: ABuFfoixvle83wwDXrV7TzQb9Q+yzcLgy+a22rTM8pqQKCxsSThWJ6Tr 17yw2TrnIPrBEifFvJl2j0R1vg==
X-Google-Smtp-Source: ACcGV60BGBba9XKvOjheIT4xs1hvPjb0XoqQ6jFp/sNr7TC9mLeHKRjeuFojLP+tFaHgL2MuWISqgQ==
X-Received: by 2002:aed:206e:: with SMTP id 101-v6mr25681248qta.11.1539798729204; Wed, 17 Oct 2018 10:52:09 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id l97-v6sm9222140qte.21.2018.10.17.10.52.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 17 Oct 2018 10:52:08 -0700 (PDT)
Date: Wed, 17 Oct 2018 13:52:04 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>, Samuel Hurst <samuelh@rd.bbc.co.uk>
Subject: Re: Clarification on HTTP/QUIC Unidirectional Streams
Message-ID: <20181017175203.GA18782@ubuntu-dmitri>
Mail-Followup-To: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>, IETF QUIC WG <quic@ietf.org>, Samuel Hurst <samuelh@rd.bbc.co.uk>
References: <272107b2-8136-48cc-f429-efcea1231d78@rd.bbc.co.uk> <CAN1APddZzF-Cr77r5rvrsnwAwY_tnBRhkzviC=190sDuWr1Xtw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAN1APddZzF-Cr77r5rvrsnwAwY_tnBRhkzviC=190sDuWr1Xtw@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/uUYgWMonk2dN-dK5skxrmEMKgw0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 17 Oct 2018 17:52:12 -0000
On Wed, Oct 17, 2018 at 10:42:24AM -0700, Mikkel Fahnøe Jørgensen wrote: > I’m not at all into all the details of HQ/QPACK > > but you cannot assume anything about stream identifiers before you see them.. Amen. This is the WG consensus: do not rely on stream IDs being assigned to particular streams in HTTP/QUIC. - Dmitri.
- Clarification on HTTP/QUIC Unidirectional Streams Samuel Hurst
- Re: Clarification on HTTP/QUIC Unidirectional Str… Mikkel Fahnøe Jørgensen
- Re: Clarification on HTTP/QUIC Unidirectional Str… Dmitri Tikhonov
- Re: Clarification on HTTP/QUIC Unidirectional Str… Mikkel Fahnøe Jørgensen
- Re: Clarification on HTTP/QUIC Unidirectional Str… Samuel Hurst
- Re: Clarification on HTTP/QUIC Unidirectional Str… Mikkel Fahnøe Jørgensen