Re: Connection coalescing in HTTP/QUIC

Lucas Pardue <lucaspardue.24.7@gmail.com> Wed, 31 October 2018 23:03 UTC

Return-Path: <lucaspardue.24.7@gmail.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 A3364130DF5 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 16:03:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 TcTj-TtHf3Ts for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 16:03:23 -0700 (PDT)
Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (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 127FE130DD6 for <quic@ietf.org>; Wed, 31 Oct 2018 16:03:23 -0700 (PDT)
Received: by mail-vs1-xe36.google.com with SMTP id q15so11165605vso.1 for <quic@ietf.org>; Wed, 31 Oct 2018 16:03:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fJjoy7NXB3H8jBglW8wL1BFGeoRqCikNvixteAQi7qU=; b=klpQ0fDWszw6yuMue+Agp3/jcdAiaXLjddyMc5xVphrMjyr1iOEbU56PIVZi1RpK8d pEINq/YA6/KpIIiRrE3GFOGzRfQcQ9ZCSq1l+Iyvz4+k3gFEeU5EA9nsZrf4dzLPXXdg kkC1v2jvYeLPg2GbetetpRwtgsUVbUmA4x9QygFlcbAClyLO5I8vhQDFwhicpbfGm1Bq XrSbLLGxac6SrbGH7cgiGAIG45uhxfMdw8wtEzWB1bTNo6MNIMdwA1QW3zEAWB4bZH1E EurKAL5IegVMIgspez2idNQ7I8XtME+aFb3opl4DAW5Z6dPBFWWIlW9fkThrp1anJf+K 9AAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fJjoy7NXB3H8jBglW8wL1BFGeoRqCikNvixteAQi7qU=; b=Cro4YELUNumozQUDkHZrVVjFw/ft6EXwWx6uLr8sCsIiGqxdK8gK70eofVGPoG+M9m VxydpMZXO07tyodSCuc8+E2qlS4g0DDhdKDeE0agg59DjaMYJBsRpkZMRhoHPYU+qfmj 3weqbzPvVS+YfU5ntZV3gyIzb2Jtbckv9iIkxQR5AVdCJU9R7b84vhkhJiyXtF9lwbDZ Ph7BKM/AYpuF1dqEtlPhurRmpLIp9LXd3Vb3bgsjhFUOm62Hk2JReOrrAwhZRYmRaw+B BtYHvBhntZBqZSpZP7iOiJhcWFmLnWjc0Mhm7mqZnbHVfedzb7KPIGlEJEEICZf7ct6p nHcw==
X-Gm-Message-State: AGRZ1gKcZyLnDWwTFGjaPu/O4iTmuPE6lJeoU7sDWSbLfzhct3zuuipW 7bU74ERu9Xd5OgR8qyN/KiDNgHxLwDdHTcJTjEwang==
X-Google-Smtp-Source: AJdET5flRvPgcyh547uI0wfA3lsY1bHH/tirULqFEuJjlmIFkx91L2W71AVyEHLLJcFNhfrUQic+g6LLCSFZjphnzRA=
X-Received: by 2002:a67:4719:: with SMTP id u25mr2241981vsa.27.1541027001951; Wed, 31 Oct 2018 16:03:21 -0700 (PDT)
MIME-Version: 1.0
References: <CAM8YLW=xxHQpLdrOmy_i5gOFRyax8UC7P9cXRSNE=xQ+gHUtDA@mail.gmail.com>
In-Reply-To: <CAM8YLW=xxHQpLdrOmy_i5gOFRyax8UC7P9cXRSNE=xQ+gHUtDA@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Wed, 31 Oct 2018 23:03:08 +0000
Message-ID: <CALGR9oZvCDdp6c=CNNsFoexmB92VTMsH_b0jjRc1f5X_Bu5-bQ@mail.gmail.com>
Subject: Re: Connection coalescing in HTTP/QUIC
To: Frederik Deweerdt <fdeweerdt=40fastly.com@dmarc.ietf.org>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000a6b6705798e4f31"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YXgS-Vr6jLf2jB-guRbw2Pz3NWo>
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, 31 Oct 2018 23:03:25 -0000

On Wed, 31 Oct 2018, 22:48 Frederik Deweerdt, <fdeweerdt=
40fastly.com@dmarc.ietf.org>; wrote:

>
> Hello,
>
> In draft-ietf-quic-http-16 "2.4. Connection Reuse" states:
>
> >  Clients MUST NOT assume that an HTTP/QUIC endpoint is authoritative for other origins without an explicit signal.
>
>
> The explicit signal bit (is it referring to an origin frame?) reads more restrictive than connection coalescing for HTTP/2. Does that mean that clients wouldn't
> be coalescing connections based on what the certificate is authoritative for and the DNS resolution results?
>
>
> Thanks,
>
> Frederik
>
>
This PR might be the best explanation
https://github.com/quicwg/base-drafts/issues/940

Another side effect of not having an HTTP/QUIC native URI.