Re: HTTP/3 Connection Reuse (Coalescing) Implementation
Ryan Hamilton <rch@google.com> Fri, 13 August 2021 16:18 UTC
Return-Path: <rch@google.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 CD9273A1DF9 for <quic@ietfa.amsl.com>; Fri, 13 Aug 2021 09:18:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.097
X-Spam-Level:
X-Spam-Status: No, score=-18.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.499, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 KZ1TRStUQYpe for <quic@ietfa.amsl.com>; Fri, 13 Aug 2021 09:18:25 -0700 (PDT)
Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (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 240C23A1DF5 for <quic@ietf.org>; Fri, 13 Aug 2021 09:18:25 -0700 (PDT)
Received: by mail-wm1-x331.google.com with SMTP id l10-20020a05600c4f0a00b002e6be174c29so3091656wmq.0 for <quic@ietf.org>; Fri, 13 Aug 2021 09:18:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kWpRGYJoRQXBScHNlIrVgfTIdBl5E6OC+KwmctY7YN0=; b=tzenglkjm/woPQvCf2DKNud6sceP14ty+jgwA9Jb6b7Uky+bzcsnbMKYrDYeVOYqeg ZGwlYh44MxYCTZJHuMUEZmhx3cP26GQzQo5RDAMJSf6Mr962lgLjxi+tDsaggAuh+6AR DoinfRD+DUVigiQ1sJNot75L8snP2XS//8ttlDpfv463WKK8B4Un/lIjktH6XAihNbw9 HqQOwGgSNII/beDO5Cafx3AUBaZuLZVf02eN6hW2zc+/+SzA5AzMdiJxIoqLvl/KPBJ0 Kj062Pgz6me7dS5bOckTPK1H+7PMc9kHDOrbvJQT4TKF+PNIdS0hdnLUVU0Czu3TW50k Cqsw==
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=kWpRGYJoRQXBScHNlIrVgfTIdBl5E6OC+KwmctY7YN0=; b=Iw7udZ+tFp98wZEx5c8yBIoAvzbOrvuloe9agDsgggM0WPVgK0Mz118BknAb34yJy5 D2reeyQwIzlk4VuLcS3Abd4Ag7qnmVR1PV8iO7N+LvrNhRjrmvNnCIKOT0RZSxRje/WG ChQKH1oFtNqBZipq+q/Hj/TjzVHu8dkq34+ug/RbVB9vTJOvyJV5BTqN8Wj7SqbRKGLu DcnRylAKQlpXINVrJTn8SUCYnsOlwWWTXhGkuKkA7H57npi/V+x96L7xEyBCtgk4JGpx CpeJU0C+Oc5ivpAuNWuEBpq5En+BGcMV/Q/cPnE2Q4GSVGAGcVjIjS+4Z0ZINZicmzlk xmoQ==
X-Gm-Message-State: AOAM5329t2UiqQMLyqX/bm+AEnuQrhgBiPqnYJ6cvarN1Epr+kgN9DWQ 84x+9ZysNhwR/hP1GPVBqkR+haVC2hyQ0SarDCVtMS77cxA=
X-Google-Smtp-Source: ABdhPJwEe4GP3K2zacUTlxn/l5H6vQa6Lt5So+zet03Pnik3J6fsyb//AvO31wV3tf154xq66q4QpKqgLEWXqtoiuaI=
X-Received: by 2002:a1c:46c2:: with SMTP id t185mr3519942wma.107.1628871501096; Fri, 13 Aug 2021 09:18:21 -0700 (PDT)
MIME-Version: 1.0
References: <6419A1D6-3070-411B-9FBB-F13366303221@contoso.com>
In-Reply-To: <6419A1D6-3070-411B-9FBB-F13366303221@contoso.com>
From: Ryan Hamilton <rch@google.com>
Date: Fri, 13 Aug 2021 09:18:08 -0700
Message-ID: <CAJ_4DfSn6AHuQcCVb_5naYkZDTNgy=ZDeQn9duGP=OD4Zz-ucA@mail.gmail.com>
Subject: Re: HTTP/3 Connection Reuse (Coalescing) Implementation
To: "Alvarez, Manuel" <maalvare=40akamai.com@dmarc.ietf.org>
Cc: "quic@ietf.org" <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000035c9b005c97333bc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/MEM7ROCL6X2zj5uDM_ezmQdEG_E>
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: Fri, 13 Aug 2021 16:18:31 -0000
On Fri, Aug 13, 2021 at 8:32 AM Alvarez, Manuel <maalvare= 40akamai.com@dmarc.ietf.org> wrote: > <snip> > > I am curious on how people are implementing HTTP/3 connection reuse so I > could get a better idea on how likely is for the scenarios mentioned above > to occur. > Chrome's HTTP/3 connection coalescing / reuse implementation matches Chrome's HTTP/2 implementation and requires IP address overlap. Hope that helps! Cheers, Ryan
- HTTP/3 Connection Reuse (Coalescing) Implementati… Alvarez, Manuel
- Re: HTTP/3 Connection Reuse (Coalescing) Implemen… Ryan Hamilton
- Re: HTTP/3 Connection Reuse (Coalescing) Implemen… Dragana Damjanovic
- Re: HTTP/3 Connection Reuse (Coalescing) Implemen… Alvarez, Manuel
- Re: HTTP/3 Connection Reuse (Coalescing) Implemen… Eric Kinnear