IETF Logo Mail Archive

Re: HTTP/3 Connection Reuse (Coalescing) Implementation

"Alvarez, Manuel" <maalvare@akamai.com> Fri, 13 August 2021 21:22 UTC

Return-Path: <maalvare@akamai.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 AEB473A26D0; Fri, 13 Aug 2021 14:22:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level:
X-Spam-Status: No, score=-2.55 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 RQmPmwUwGl31; Fri, 13 Aug 2021 14:21:57 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 A20A33A26CD; Fri, 13 Aug 2021 14:21:54 -0700 (PDT)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 17DLF7Qi018207; Fri, 13 Aug 2021 22:21:52 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=HSDpfwNDzXKBzV3umyvc6xYDUsLl/M4itFWdNG+uaMY=; b=nlEaI1Qlv1Y8jWy9EgHjdzfmcaJrNCUojtL8YlgTXMDLFEGuspOlal/EH5JMCAR0/9q9 jvCci6Lq+tWPLAH90+yuoUH6VHGN0kxbd4GUHCTU4kCIH67PlevMRoabloSVdsbOdq9t /7kkmcs3fC/GzT0NoLk/MYefT3jPhl57QriOwWNlq2Q9sQ5mWvKaQwXrJ5BkCBIGykG9 kLH7wtlwKGRZNkLgfXj0U4LLbatqltJZOzDblalD2ZlHxW45vUXUa9NQgKLctEUaPAF+ hIhUtBdbWH/yPEZUGXYNOsd1Bv8xkJRUInEVloerc7FfGzNJt2l41t53eCXJxZh6vg7C Xg==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 3ad4k6qq5u-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 13 Aug 2021 22:21:52 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.1.2/8.16.1.2) with SMTP id 17DLK5rJ015837; Fri, 13 Aug 2021 17:21:50 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.31]) by prod-mail-ppoint1.akamai.com with ESMTP id 3aca34vs7h-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 13 Aug 2021 17:21:50 -0400
Received: from usma1ex-dag3mb4.msg.corp.akamai.com (172.27.123.56) by usma1ex-dag3mb3.msg.corp.akamai.com (172.27.123.58) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Fri, 13 Aug 2021 17:21:50 -0400
Received: from usma1ex-dag3mb4.msg.corp.akamai.com ([172.27.123.56]) by usma1ex-dag3mb4.msg.corp.akamai.com ([172.27.123.56]) with mapi id 15.00.1497.023; Fri, 13 Aug 2021 17:21:50 -0400
From: "Alvarez, Manuel" <maalvare@akamai.com>
To: Ryan Hamilton <rch=40google.com@dmarc.ietf.org>
CC: "quic@ietf.org" <quic@ietf.org>
Subject: Re: HTTP/3 Connection Reuse (Coalescing) Implementation
Thread-Topic: HTTP/3 Connection Reuse (Coalescing) Implementation
Thread-Index: AQHXj6qVo8Z4XPBMA0mkOJLLsReE86tx4VQAgAARyoA=
Date: Fri, 13 Aug 2021 21:21:49 +0000
Message-ID: <9FCD6447-48A0-412E-8078-DF16244347BF@akamai.com>
References: <6419A1D6-3070-411B-9FBB-F13366303221@contoso.com> <CAJ_4DfSn6AHuQcCVb_5naYkZDTNgy=ZDeQn9duGP=OD4Zz-ucA@mail.gmail.com>
In-Reply-To: <CAJ_4DfSn6AHuQcCVb_5naYkZDTNgy=ZDeQn9duGP=OD4Zz-ucA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.52.21080801
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.118.139]
Content-Type: multipart/alternative; boundary="_000_9FCD644748A0412E8078DF16244347BFakamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-08-13_08:2021-08-13, 2021-08-13 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=999 spamscore=0 phishscore=0 suspectscore=0 bulkscore=0 mlxscore=0 adultscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2107140000 definitions=main-2108130125
X-Proofpoint-ORIG-GUID: Co9aXkSrzB07XYRyAMbqM7oHaeKY6gBR
X-Proofpoint-GUID: Co9aXkSrzB07XYRyAMbqM7oHaeKY6gBR
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-08-13_08:2021-08-13, 2021-08-13 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 lowpriorityscore=0 priorityscore=1501 bulkscore=0 malwarescore=0 spamscore=0 impostorscore=0 adultscore=0 suspectscore=0 mlxscore=0 mlxlogscore=999 clxscore=1011 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2107140000 definitions=main-2108130125
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 184.51.33.18) smtp.mailfrom=maalvare@akamai.com smtp.helo=prod-mail-ppoint1
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/zFVdFsRyhMUz25zFhCz0oN2uIgY>
X-Mailman-Approved-At: Fri, 13 Aug 2021 15:22:23 -0700
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 21:22:03 -0000

Thank you Ryan,

It does help. I wonder how other browsers will implement it though.

Manuel Alvarez

From: Ryan Hamilton <rch=40google.com@dmarc.ietf.org>
Date: Friday, August 13, 2021 at 12:18 PM
To: Manuel Alvarez <maalvare@akamai.com>
Cc: "quic@ietf.org" <quic@ietf.org>
Subject: Re: HTTP/3 Connection Reuse (Coalescing) Implementation

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!

Cheers,

Ryan

v2.23.0 | Report a Bug | By Email