Connection coalescing in HTTP/QUIC
Frederik Deweerdt <fdeweerdt@fastly.com> Wed, 31 October 2018 22:48 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 AE831130DF5 for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 15:48:38 -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 yGbWO14mnVjA for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 15:48:37 -0700 (PDT)
Received: from mail-yw1-xc31.google.com (mail-yw1-xc31.google.com [IPv6:2607:f8b0:4864:20::c31]) (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 4E6BF130DF3 for <quic@ietf.org>; Wed, 31 Oct 2018 15:48:37 -0700 (PDT)
Received: by mail-yw1-xc31.google.com with SMTP id z72-v6so2906276ywa.0 for <quic@ietf.org>; Wed, 31 Oct 2018 15:48:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=PNW/9peAZIIdqkkpe1hEBWl2sJ1m4rHncwb23qeRX34=; b=iP2gXpL20AYUu6/nXyyka59etUJ3CxgL0KSzgXa96gGSPQcfty0Y38AOGu1pbVzxtk MRjb9uIvOhJPiQ79G0HiytwIJFaCqmyJXaXOIqlU+G4idfOWWaN0KQbMYhqv01Vxz2Ao s7mJLON4oBGgm1or9mFFQv5F0JEBFpjxAwkC0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=PNW/9peAZIIdqkkpe1hEBWl2sJ1m4rHncwb23qeRX34=; b=fpXNhcp4Dc0/fUKhlZP2JtW3Tt+tglNmSZzkh88EUMXgfytUPxQE7LCp2tXsOsDMFJ r3gcgzjAlJX2hF0Y+2t4TGfbutDz4CYtVilb4HurjAtzUIRxZEqigIAf7z6lO9k89Zep k9+HdEAFhPKpraHaNPNxMZxO0EHcSmtEEb8XoKIy4aPi3HNuIzLfra6QYuOg8nAHwsNf c+T9Ao1SfJFNY7LZeRfyMslRI+AeQbp8LtpzzpOqa8XT1fArbGDr0fIjaHwA/ta6uxMM izcwARxzYJMY447woiEKf/+OdR3TkZlvkQIeDanRdUBaNIPAKXQCydbrN8iYIsXxDvdu gkcw==
X-Gm-Message-State: AGRZ1gKxlbhkF2GZs5qR7yjgLawZhQkFHfb1hE735Jiw27VtgkMNYiXD 9Iwhnr49s436g9/r3NYW9D8sJEoxHNYFV21RSkmo96pO4JIEnw==
X-Google-Smtp-Source: AJdET5erb1JIRy2OrvyMmuYPr1iioJ9uGHKcaBUvNKe4KsRDgabgoocv+0D82ijONsyao6hcMVHijPpEcAdouVYZsU4=
X-Received: by 2002:a81:a153:: with SMTP id y80-v6mr4983518ywg.323.1541026116162; Wed, 31 Oct 2018 15:48:36 -0700 (PDT)
MIME-Version: 1.0
From: Frederik Deweerdt <fdeweerdt@fastly.com>
Date: Wed, 31 Oct 2018 15:48:24 -0700
Message-ID: <CAM8YLW=xxHQpLdrOmy_i5gOFRyax8UC7P9cXRSNE=xQ+gHUtDA@mail.gmail.com>
Subject: Connection coalescing in HTTP/QUIC
To: "quic@ietf.org" <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003e767f05798e1aad"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/tZ3xvwQgB1V9E624eTKsomdjKyo>
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 22:48:39 -0000
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
- Connection coalescing in HTTP/QUIC Frederik Deweerdt
- Re: Connection coalescing in HTTP/QUIC Lucas Pardue
- Re: Connection coalescing in HTTP/QUIC Frederik Deweerdt
- RE: Connection coalescing in HTTP/QUIC Mike Bishop
- Re: Connection coalescing in HTTP/QUIC Mikkel Fahnøe Jørgensen