IETF Logo Mail Archive

Re: HTTP/3 Connection Reuse (Coalescing) Implementation

Eric Kinnear <ekinnear@apple.com> Mon, 23 August 2021 22:45 UTC

Return-Path: <ekinnear@apple.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 588153A2171 for <quic@ietfa.amsl.com>; Mon, 23 Aug 2021 15:45:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.452, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 Mffllj-dczH6 for <quic@ietfa.amsl.com>; Mon, 23 Aug 2021 15:45:16 -0700 (PDT)
Received: from rn-mailsvcp-ppex-lapp44.apple.com (rn-mailsvcp-ppex-lapp44.rno.apple.com [17.179.253.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B13E23A216D for <quic@ietf.org>; Mon, 23 Aug 2021 15:45:16 -0700 (PDT)
Received: from pps.filterd (rn-mailsvcp-ppex-lapp44.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp44.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 17NMh9Ke006884; Mon, 23 Aug 2021 15:45:15 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=0iGH0khwLw5nTtEHpI2TW2HYO6+8DKPO8UEJ5E9zLek=; b=uDlsTfeid/m37mqu+WsCPnQsCfUWlNvINbFpdGlKNoEaR/5RNHErYvOTgMiyQk5g51ZP esqkgvv5pN37MYtD2ewIpUr+B2tOxYFM0MmOQVwVrKovEjg3MKZyhVx6pzV7a8IqMw7I okoZr5JGeu2kPjfuTGoC4e7yk2IiiadlddEC2z8LzEnRRX5smq0TiSF7iAEO+gj8bVl0 hnhlJ9TcdrU4PYu5g0QXW/h/bKltyYrhgeXE5xIv3qKVLZrr+2M0/4KjzWQz2P2CYRCd fnCb36XvKcvVwYCpFMLJ8deCwjDO7PZRrsJNAC9XqP3oYd+kUzymqKTvpsWINA3nwX0O fw==
Received: from ma-mailsvcp-mta-lapp02.corp.apple.com (ma-mailsvcp-mta-lapp02.corp.apple.com [10.226.18.134]) by rn-mailsvcp-ppex-lapp44.rno.apple.com with ESMTP id 3ajw09ue0c-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 23 Aug 2021 15:45:14 -0700
Received: from ma-mailsvcp-mmp-lapp02.apple.com (ma-mailsvcp-mmp-lapp02.apple.com [17.32.222.15]) by ma-mailsvcp-mta-lapp02.corp.apple.com (Oracle Communications Messaging Server 8.1.0.9.20210415 64bit (built Apr 15 2021)) with ESMTPS id <0QYB00RFZDVE8C40@ma-mailsvcp-mta-lapp02.corp.apple.com>; Mon, 23 Aug 2021 15:45:14 -0700 (PDT)
Received: from process_milters-daemon.ma-mailsvcp-mmp-lapp02.apple.com by ma-mailsvcp-mmp-lapp02.apple.com (Oracle Communications Messaging Server 8.1.0.9.20210415 64bit (built Apr 15 2021)) id <0QYB00I00DQ7NT00@ma-mailsvcp-mmp-lapp02.apple.com>; Mon, 23 Aug 2021 15:45:14 -0700 (PDT)
X-Va-A:
X-Va-T-CD: 86b7cfee6e5275a570154a345c7bda04
X-Va-E-CD: 04dc6e649d3c3520399e9f57a8f0bec6
X-Va-R-CD: f088265faffd7016f3ab96c9abf7026b
X-Va-CD: 0
X-Va-ID: 8792c38a-0820-4d98-89f9-e3d128d7c274
X-V-A:
X-V-T-CD: 86b7cfee6e5275a570154a345c7bda04
X-V-E-CD: 04dc6e649d3c3520399e9f57a8f0bec6
X-V-R-CD: f088265faffd7016f3ab96c9abf7026b
X-V-CD: 0
X-V-ID: 46472498-fce4-4e45-a20e-411419eb8d4e
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-08-23_04:2021-08-23, 2021-08-23 signatures=0
Received: from smtpclient.apple ([17.10.147.157]) by ma-mailsvcp-mmp-lapp02.apple.com (Oracle Communications Messaging Server 8.1.0.9.20210415 64bit (built Apr 15 2021)) with ESMTPSA id <0QYB0046QDVDPK00@ma-mailsvcp-mmp-lapp02.apple.com>; Mon, 23 Aug 2021 15:45:14 -0700 (PDT)
From: Eric Kinnear <ekinnear@apple.com>
Message-id: <3B64D174-593D-4AB2-B0A1-31C31FA8AB79@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_43A7CA78-27CE-435C-BB58-02ECF60DD7DF"
MIME-version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Subject: Re: HTTP/3 Connection Reuse (Coalescing) Implementation
Date: Mon, 23 Aug 2021 18:45:12 -0400
In-reply-to: <CAG0m4gQED3dQ56fXj3foyENJWGnRj_pZgLQ2xaKZe4-K2-Gb-g@mail.gmail.com>
Cc: Ryan Hamilton <rch=40google.com@dmarc.ietf.org>, "Alvarez, Manuel" <maalvare=40akamai.com@dmarc.ietf.org>, "quic@ietf.org" <quic@ietf.org>
To: Dragana Damjanovic <dragana.damjano@gmail.com>
References: <6419A1D6-3070-411B-9FBB-F13366303221@contoso.com> <CAJ_4DfSn6AHuQcCVb_5naYkZDTNgy=ZDeQn9duGP=OD4Zz-ucA@mail.gmail.com> <CAG0m4gQED3dQ56fXj3foyENJWGnRj_pZgLQ2xaKZe4-K2-Gb-g@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-08-23_04:2021-08-23, 2021-08-23 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/0nqKySdzmXK6CwZ9dKfD5GsQgqE>
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: Mon, 23 Aug 2021 22:45:22 -0000


> On Aug 13, 2021, at 6:12 PM, Dragana Damjanovic <dragana.damjano@gmail.com> wrote:
> 
> 
> 
> On Fri, Aug 13, 2021 at 6:18 PM Ryan Hamilton <rch=40google.com@dmarc.ietf.org <mailto:40google.com@dmarc.ietf.org>> wrote:
> On Fri, Aug 13, 2021 at 8:32 AM Alvarez, Manuel <maalvare=40akamai.com@dmarc.ietf.org <mailto: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!
> 
> 
> At the moment, Firefox coalescing behavior for HTTP/3 is the same as Firefox's HTTP/2 coalescing behavior.


Safari’s coalescing implementation for HTTP/3 is currently the same as it is for HTTP/2, and it requires IP address overlap.

Thanks,
Eric

> 
> dragana
>  
> Cheers,
> 
> Ryan

v2.23.0 | Report a Bug | By Email