Re: Connection coalescing in HTTP/QUIC

Frederik Deweerdt <fdeweerdt@fastly.com> Thu, 01 November 2018 15:56 UTC

Return-Path: <fdeweerdt@fastly.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 258DA1252B7 for <quic@ietfa.amsl.com>; Thu, 1 Nov 2018 08:56:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastly.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 uuyMeCPcKN0r for <quic@ietfa.amsl.com>; Thu, 1 Nov 2018 08:56:14 -0700 (PDT)
Received: from mail-yw1-xc42.google.com (mail-yw1-xc42.google.com [IPv6:2607:f8b0:4864:20::c42]) (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 ED3D7128C65 for <quic@ietf.org>; Thu, 1 Nov 2018 08:56:13 -0700 (PDT)
Received: by mail-yw1-xc42.google.com with SMTP id j202-v6so8071450ywa.13 for <quic@ietf.org>; Thu, 01 Nov 2018 08:56:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OEcCydzSLOvlI5qkF/ZfFAEkNc08x0l8vxoPQIY2HUA=; b=Fe+vIp2VQ9ozQZcn57sUY2lB2qpu+w+mEhg4ZhwcPXYpDIyb5XVBRBbPliPRHj6gSp sefshVh5kVKa5FtlPvBzspa+gBSUT5cApqO7shInhFrBis9a6B0MttWQvBA79x85y9+R oV+Y0CBfKlgAh41QXek/+EUoFAF9Dvb8CY+UA=
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=OEcCydzSLOvlI5qkF/ZfFAEkNc08x0l8vxoPQIY2HUA=; b=KM+sMkn0tSk16WohMrwnG35XVQfYIeUa48dF3uOPkScLlgrQEjrRgkTdoStbdK4HsI qr/FbsDAS3pe2lu4vT+ORPfXkbfzSwNSiMsbFMYzGB5Zx1ZlnAgVcFW47sw99Z97kPae nhLV26m4CUJSD8Ylbr1x8EevCMfXDH/PtfvzfziB+D3s92yNN8Qey3CCePq38Aa54UZS 7YqxFnGcrCMMQQx5nuDEJBjZQZC6qZ2YDqt3O66Yps+AtM2EJFZ9SjkCU2s1+Z+llkxR X3V5tOKnKl/qm7qq4edlPxEUfR94iH2CVkwAasRTfsFrpV758C/mjvspDMLsiEM5fVYA +zew==
X-Gm-Message-State: AGRZ1gJZbyYw+8OfU/L93KcYoh8mwiQEp29JX3o8zR2IbuMXoDqOZmew zdBpG7l6l5V7afk0NPj3fcOXYtY3wZa8oy/Pg2BUbQ==
X-Google-Smtp-Source: AJdET5dbx6IyWLgxJ38LaOVnoRSeKbIsNfevTHICW3k+BIcRbJyUzD//mdoYESuRwsh4HM618bm7iZlSTjVI5W1VeaY=
X-Received: by 2002:a81:a153:: with SMTP id y80-v6mr7642055ywg.323.1541087771396; Thu, 01 Nov 2018 08:56:11 -0700 (PDT)
MIME-Version: 1.0
References: <CAM8YLW=xxHQpLdrOmy_i5gOFRyax8UC7P9cXRSNE=xQ+gHUtDA@mail.gmail.com> <CALGR9oZvCDdp6c=CNNsFoexmB92VTMsH_b0jjRc1f5X_Bu5-bQ@mail.gmail.com>
In-Reply-To: <CALGR9oZvCDdp6c=CNNsFoexmB92VTMsH_b0jjRc1f5X_Bu5-bQ@mail.gmail.com>
From: Frederik Deweerdt <fdeweerdt@fastly.com>
Date: Thu, 1 Nov 2018 08:56:00 -0700
Message-ID: <CAM8YLWm4tQv4CG4ea6Usc1LvE-D4hoVv1Ynttqo_MiQJc4C4SQ@mail.gmail.com>
Subject: Re: Connection coalescing in HTTP/QUIC
To: lucaspardue.24.7@gmail.com
Cc: fdeweerdt=40fastly.com@dmarc.ietf.org, quic@ietf.org
Content-Type: multipart/alternative; boundary="00000000000044f39205799c75d7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7CCe8LSvroxkF65t2FswXz2eD7k>
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: Thu, 01 Nov 2018 15:56:16 -0000

Hi Lucas,


On Wed, Oct 31, 2018 at 4:03 PM Lucas Pardue <lucaspardue.24.7@gmail.com>;
wrote:

> 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.
>
>
Thanks for the pointer. I think it's unclear to me why a browser wouldn't
optimistically try to establish QUIC connections for domains that resolve
to the same IP and are also present on the cert? How does that relate to
not having a native URI?

Regards,
Frederik