Return-Path: 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 642471292F1 for ; Thu, 18 Oct 2018 01:54:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.738 X-Spam-Level: X-Spam-Status: No, score=-1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 pKJYeZBxY99k for ; Thu, 18 Oct 2018 01:54:43 -0700 (PDT) Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (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 EC9BC128CF3 for ; Thu, 18 Oct 2018 01:54:42 -0700 (PDT) Received: by mail-oi1-x22f.google.com with SMTP id l197-v6so23368689oib.8 for ; Thu, 18 Oct 2018 01:54:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to; bh=9OEsA1MMqjeCqYeiD7dkkNuLeXi1ZY+3o4aP3ysG0tc=; b=t8tnMNPS5XeXe8oINlwVxO5IysG1Dd28n+2PQfsytIkpYPp/KLd4mExkfq0OcBxGI/ 9M5Q5T2WagtlApm5O2P1pXfsxfsDtXucf24jRS8+gG6QdeKeQZPZXPKtXkbfbFGcf3Q6 2Blj5O+4OXNLgRL5I08UNQ+M/7W4Did4t7FG5DUgyVwwIdIgm1SozwSZYcAVeqlkH2QX 1/8153VPUIG8LMYY5420GnvoOKuWBgNx05M4ju0HXxsPR/jnmEMQ88jH2s6C0rznQdN3 MamuCVvxjV3ga+Nv1ZX5dv4VNtaNKy+epSHQbN1CgGpuV4u933dqjs1O59ILFHzItg7F ++4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to; bh=9OEsA1MMqjeCqYeiD7dkkNuLeXi1ZY+3o4aP3ysG0tc=; b=qrTys1E1i40Jpyadje0zS5/3JJvWED3GkIuT1EuBumAZWrmXIYV317tHM3v0zXH17K 90pbl/7Z36COxKaCxy1tin7KUiz2BPoqCRfr7lN0tEQ7MdKiik/7mi9DGHPdbvXXCtpP RTrhTxPFUs1OhnbtG5l0FNE/z+Li2S2O0phtd1CDM11O5UMyF9xnYbJL21egGNfGhclN LR5ebxEl5HvBviIx4Vdj7q+sIyfppsR+Bb6rAynewtbbnm6DD3QOLxsKE43EPwGJbA+Y MtM0klwS1IbxhcFrQchRBjmiHwBk80LdwdBSR/LaJdbm04DREPqMdXx9Gbu8xNc2rFzI E6Mw== X-Gm-Message-State: ABuFfoi4tmSbWcsA6OFhuOByKScSZRpoxzhEJ/4LMfcnbzU7WVdc1O+J TRFaPOKF7UCzWWan21MnKm7lXZxWcvleTajDj5t/cg== X-Google-Smtp-Source: ACcGV63Ww+oenSkHviUC8nC96NDbKWvLsiuWRVM1uNBVf6tS8tjIE9esBSP5OQrxd3i2x+Ct7me4L9axgK7Ode5rg1w= X-Received: by 2002:aca:49c8:: with SMTP id w191-v6mr15016514oia.114.1539852882252; Thu, 18 Oct 2018 01:54:42 -0700 (PDT) Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 18 Oct 2018 10:54:41 +0200 From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= In-Reply-To: <1990abd4-7112-0620-061a-3f88950eb2e1@rd.bbc.co.uk> References: <272107b2-8136-48cc-f429-efcea1231d78@rd.bbc.co.uk> <1990abd4-7112-0620-061a-3f88950eb2e1@rd.bbc.co.uk> <1990abd4-7112-0620-061a-3f88950eb2e1@rd.bbc.co.uk> X-Mailer: Airmail (420) MIME-Version: 1.0 Date: Thu, 18 Oct 2018 10:54:41 +0200 Message-ID: Subject: Re: Clarification on HTTP/QUIC Unidirectional Streams To: quic@ietf.org, Samuel Hurst Content-Type: multipart/alternative; boundary="0000000000000d9ac005787cf00c" Archived-At: X-BeenThere: quic@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Main mailing list of the IETF QUIC working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Oct 2018 08:54:45 -0000 --0000000000000d9ac005787cf00c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On 18 October 2018 at 10.46.34, Samuel Hurst (samuelh@rd.bbc.co.uk) wrote: > Some implementation could have fewer streams because they are > micro-controllers that do not want to use QPACK compression at all, so > assuming server push on stream 15 would possibly work most of the time > at best. There's nothing in the specs that specifies when the QPACK encoder/decoder streams are opened, so I was going on the assumption that they are only opened when a client wants to use the dynamic table. I=E2=80=99m not really sure where this landed, but there was some discussio= n here: https://github.com/quicwg/base-drafts/issues/1747 --0000000000000d9ac005787cf00c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable = On 18 October 2018 a= t 10.46.34, Samuel Hurst (samuelh@r= d.bbc.co.uk) wrote:
> Some implementation could have fewer streams b= ecause they are=C2=A0> micro-controllers th= at do not want to use QPACK compression at all, so=C2=A0
> assuming server push on stream 15 would possibly work most of = the time=C2=A0
> at best.=C2=A0

There's nothing in the specs that specifies when the QPACK=C2=A0
encoder/decoder streams are opened, so I was going on= the assumption=C2=A0that they are only opened= when a client wants to use the dynamic table.=C2=A0


= I=E2=80=99m not really sure where this landed, but there was some discussio= n here:=C2=A0= https://github.com/quicwg/base-drafts/issues/1747


--0000000000000d9ac005787cf00c--