IETF Logo Mail Archive

Re: Quic: the elephant in the room

"Salz, Rich" <rsalz@akamai.com> Sun, 11 April 2021 17:23 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0297C3A1625 for <ietf@ietfa.amsl.com>; Sun, 11 Apr 2021 10:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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 7Rk4BAG7hBAP for <ietf@ietfa.amsl.com>; Sun, 11 Apr 2021 10:23:09 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 8F3C43A1624 for <ietf@ietf.org>; Sun, 11 Apr 2021 10:23:09 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.43/8.16.0.43) with SMTP id 13BHJ3xT012051; Sun, 11 Apr 2021 18:23:05 +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=Jc3uRuUzH8KU8NFyUWYldp4W3Z6EAVK5a5w25Xw6pqM=; b=ZV0+/xYHEhiErzJfMClmdP3dQvlnOelDq3jbFE+3rYV1xXkUfcSb3Oif0m+7zDmW9sTO GdS+gb+7B4xFEvXIz8c5NtNpPxaNoYoShh8/k5lzuMFaiOV3o45S7Lf3c4mET4FbqSyM i/+vaQNpLrxVSuXkprah1M0mNitV614BpF3E3BYv9SKJU0hP8FveagPHvvyApEzH/f64 hmEfOVMiF2HLIjEZ2+YTz55+wmUKwfxNgDzZOauPuQYsjJCUFRCK697rQMJz4sOdqTUe 56Qb+xOZ01C18Cd//monqxhTw0o8+0+9EPdraZq+5oLcAAkdPUUqSD5oQ32vx77Gt4B3 rw==
Received: from prod-mail-ppoint6 (prod-mail-ppoint6.akamai.com [184.51.33.61] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 37u13f96ts-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 11 Apr 2021 18:23:05 +0100
Received: from pps.filterd (prod-mail-ppoint6.akamai.com [127.0.0.1]) by prod-mail-ppoint6.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 13BHK4U6022988; Sun, 11 Apr 2021 13:23:04 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint6.akamai.com with ESMTP id 37u7c0k7gq-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sun, 11 Apr 2021 13:23:04 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb3.msg.corp.akamai.com (172.27.123.103) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sun, 11 Apr 2021 13:23:03 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.012; Sun, 11 Apr 2021 13:23:03 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Michael Thomas <mike@mtcc.com>, Phillip Hallam-Baker <phill@hallambaker.com>
CC: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Quic: the elephant in the room
Thread-Topic: Quic: the elephant in the room
Thread-Index: AQHXLZZoemNfFNMHHkyER9D49fn4h6qtF2OAgAACTICAALlAgA==
Date: Sun, 11 Apr 2021 17:23:03 +0000
Message-ID: <506A780B-9C0D-4F4A-B045-098F6152F4DB@akamai.com>
References: <3b25c77d-e721-e86d-6c34-a90039aab0e2@mtcc.com> <CAMm+Lwhi8xwFgZJL7jod2g4urZt_f+dm0tNi+3y1osqOfch2mQ@mail.gmail.com> <3593a01f-73f4-7d03-a85b-dff64a8b070e@mtcc.com>
In-Reply-To: <3593a01f-73f4-7d03-a85b-dff64a8b070e@mtcc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.48.21040401
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.164.43]
Content-Type: multipart/alternative; boundary="_000_506A780B9C0D4F4AB045098F6152F4DBakamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-04-11_09:2021-04-09, 2021-04-11 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 malwarescore=0 bulkscore=0 mlxscore=0 spamscore=0 phishscore=0 suspectscore=0 mlxlogscore=999 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104060000 definitions=main-2104110136
X-Proofpoint-ORIG-GUID: qtjGWHK2frzMX1athBIDJjQOD71aCi1Q
X-Proofpoint-GUID: qtjGWHK2frzMX1athBIDJjQOD71aCi1Q
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-04-11_09:2021-04-09, 2021-04-11 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 lowpriorityscore=0 mlxlogscore=999 impostorscore=0 suspectscore=0 bulkscore=0 clxscore=1011 malwarescore=0 mlxscore=0 adultscore=0 phishscore=0 priorityscore=1501 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104060000 definitions=main-2104110136
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 184.51.33.61) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint6
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RDqfxoy_SDxkQEtiBwKN4K7h3fY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Apr 2021 17:23:14 -0000

  *   I don't see why [DNS timeouts] it can't be long lived, but even normal TTL's would get amortized over a lot of connections. Right now with certs it is a 5 message affair which cannot get better. But that is why one of $BROWSERVENDORS doing an experiment would be helpful.

There are use-cases where a five-second DNS TTL is important.  And they’re not amortized over multiple connections from *one* user, but rather affect *many* users.  Imagine an e-commerce site connected to two CDN’s who needs to switch.

v2.23.0 | Report a Bug | By Email