Weeklong intermittent regional 911 outages -- I blame QUIC.

Eric J Bowman <mellowmutt@zoho.com> Thu, 13 June 2024 01:44 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=ietf.org@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44781C169434 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 12 Jun 2024 18:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.856
X-Spam-Level:
X-Spam-Status: No, score=-2.856 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=w3.org header.b="NbPvonMW"; dkim=pass (2048-bit key) header.d=w3.org header.b="TpaLVu8F"; dkim=pass (1024-bit key) header.d=zoho.com header.b="YBQlqxYp"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rWnC3zoQing5 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 12 Jun 2024 18:44:16 -0700 (PDT)
Received: from mab.w3.org (mab.w3.org [IPv6:2600:1f18:7d7a:2700:d091:4b25:8566:8113]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F10FFC169426 for <httpbisa-archive-bis2Juki@ietf.org>; Wed, 12 Jun 2024 18:44:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=w3.org; s=s1; h=Subject:Content-Type:MIME-Version:In-Reply-To:Message-Id:To:From:Date :Cc:Reply-To:References; bh=w5Tkp7fgmeyqyPQZktuG2Nrsf+VPt6C4Q6V3QY0Xkp4=; b=N bPvonMW/f914T1slIS+O7WuOLnX/LjOOx4xqNYJKSN+Q2tuD6MPUfkqJTqyzKvMtCQuoKcNZDZpAY D4zxFkkzidxaeYLVcpgGjefykWsjYK6wgHV8IsVDg7WIcZg6bAGopI5kydS/na9k/V6wYOd86+CfX 7OxRKhPpM55sA7EMOjz3NMecLSNsRa4OIlVta5NoXKs8Ls8obVcS3okDvA2HqYl6rYT4UF/vCw0kR KD4jnabD8jLkniVvKXJgwYWWZZyOBUTTAL1sbbBeMSQeLNJurtzv/Fueu3mzdMBEeO8XbTyfvf/Ak 6TtjYsoK+nOkHyFAgq7J54Pqag6t7JFRw==;
Received: from lists by mab.w3.org with local (Exim 4.96) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1sHZV6-000sLy-0s for ietf-http-wg-dist@listhub.w3.org; Thu, 13 Jun 2024 01:43:40 +0000
Resent-Date: Thu, 13 Jun 2024 01:43:40 +0000
Resent-Message-Id: <E1sHZV6-000sLy-0s@mab.w3.org>
Received: from ip-10-0-0-144.ec2.internal ([10.0.0.144] helo=pan.w3.org) by mab.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <mellowmutt@zoho.com>) id 1sHZV4-000sKy-0Y for ietf-http-wg@listhub.w3.internal; Thu, 13 Jun 2024 01:43:38 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=w3.org; s=s1; h=Content-Type:MIME-Version:Subject:In-Reply-To:Message-Id:To:From:Date :Cc:Reply-To:References; bh=w5Tkp7fgmeyqyPQZktuG2Nrsf+VPt6C4Q6V3QY0Xkp4=; t=1718243018; x=1719107018; b=TpaLVu8Fu20fdYFloTzDy7kdRAG7sWfuwqx3j1PESGfDEaY eHNwA+qoEqm3UyPO6gmHHrraSuUu9ONlLuRVrxF8RCQEaRL12OC74Ed9zEqQPdTglPFB6HsNZ6LZH xNZCnSDXe3hL8WSLd25Xe1GaAtkVqMiDWYwasbo4F0+b++t6zPCwmJUndDnQsf6fJ+MrxWDcTAzQs Vvr0OuEEj2fknAlO8kcmL3klrKaYf0zvHRT2Ixo22YJydrRgrI7uERi3iv80v7PSJpj7Pe0ss2vgd O1VBOV/24vK056AkwQs01w+Eu0vG/elV5I/nC1x/aFouYxaq3ZykIm0F0M23rydA==;
Received-SPF: pass (pan.w3.org: domain of zoho.com designates 136.143.188.91 as permitted sender) client-ip=136.143.188.91; envelope-from=mellowmutt@zoho.com; helo=sender4-pp-o91.zoho.com;
Received: from sender4-pp-o91.zoho.com ([136.143.188.91]) by pan.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <mellowmutt@zoho.com>) id 1sHZV3-00EQ61-1V for ietf-http-wg@w3.org; Thu, 13 Jun 2024 01:43:38 +0000
ARC-Seal: i=1; a=rsa-sha256; t=1718243012; cv=none; d=zohomail.com; s=zohoarc; b=IO+vRRTL62XA2QKw/v196jcle6u8FuVFQypkvkQRd6+SPtBRIhXnb2JUcTZ5R5UinCG/9wPKAJqi4Po0AdGmJ5lJRRJF2PTMDJZTS2B3ttudWmhWbyFgTAnBVd6rO5gs8xZVL0QBTUIwjmZr6Lt3YroLz2iRhGahWchp/r71lCI=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1718243012; h=Content-Type:Date:Date:From:From:MIME-Version:Message-ID:Subject:Subject:To:To:Message-Id:Reply-To:Cc; bh=w5Tkp7fgmeyqyPQZktuG2Nrsf+VPt6C4Q6V3QY0Xkp4=; b=MtyI9t0KAip/zwMKwJB/1DFLlyutlkK1G19Eop5rd2w3+IRO0NMA7ElQXQNzeTfw9meMeGOEYcIQwC2jBlm4iOGT5CbKmpMw0I1d7DTK9wiwKiSKCYb80JrmWFbqwk1lAznwsOKlfzpXXLeoOIq46n+P3fI5eTDDcuClBdjTv+U=
ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass header.i=zoho.com; spf=pass smtp.mailfrom=mellowmutt@zoho.com; dmarc=pass header.from=<mellowmutt@zoho.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1718243012; s=zm2022; d=zoho.com; i=mellowmutt@zoho.com; h=Date:Date:From:From:To:To:Message-Id:Message-Id:In-Reply-To:Subject:Subject:MIME-Version:Content-Type:Feedback-ID:Reply-To:Cc; bh=w5Tkp7fgmeyqyPQZktuG2Nrsf+VPt6C4Q6V3QY0Xkp4=; b=YBQlqxYpkZYzpYgA3/groZs2muXI3cmtH8EtGGuKqdSnmA+HeT/K+eWWL1pEOZKf xxLMVWTS7E+zjGqDuC6Pw9Y2IjibAJlBOQRXDNUKJFEnk6IGpn/OyqcgYj+gVEvGXMv WErNjN31GtmL1mO2aSexevLkbQnc2NPVbhzXlGgg=
Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1718243010869527.1789311425832; Wed, 12 Jun 2024 18:43:30 -0700 (PDT)
Received: from [65.117.211.248] by mail.zoho.com with HTTP;Wed, 12 Jun 2024 18:43:30 -0700 (PDT)
Date: Wed, 12 Jun 2024 18:43:30 -0700
From: Eric J Bowman <mellowmutt@zoho.com>
To: Ietf Http Wg <ietf-http-wg@w3.org>
Message-Id: <1900f43a927.1041f595838570.1760105734293573684@zoho.com>
In-Reply-To:
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_101399_341133493.1718243010855"
Importance: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
Feedback-ID: rr080112283cee0fe47255d156aae9e4ef0000cc413b3716cf3d5840b1f5bd5187af602744f5c5134eb3d632a6:zu08011227e92241ee9634cecce9df71970000d0b1490e3f531da1c93075078d75b75b3f25dc09eeebeb10ed:rf08011226d58ab7141727224786daf49a0000b491c527956dd570d616afbc2ee634007f7dd874e0e2079f:ZohoMail
X-W3C-Hub-DKIM-Status: validation passed: (address=mellowmutt@zoho.com domain=zoho.com), signature is good
X-W3C-Hub-DKIM-Status: validation passed: (address=mellowmutt@zoho.com domain=mellowmutt@zoho.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-2.7
X-W3C-Hub-Spam-Report: ARC_SIGNED=0.001, ARC_VALID=0.001, BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, DMARC_PASS=-0.001, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: pan.w3.org 1sHZV3-00EQ61-1V a930b67188ee813ea02708e478256100
X-Original-To: ietf-http-wg@w3.org
Subject: Weeklong intermittent regional 911 outages -- I blame QUIC.
Archived-At: <https://www.w3.org/mid/1900f43a927.1041f595838570.1760105734293573684@zoho.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/52004
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/email/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

My new GPON fails over to my old wireless, slated for gigabit WAVE upgrade later this year. For the past week, I'm down an average of 10 minutes every hour, on both, despite different backbone routing. When this happens, 911 goes "deee deeee deeee the # you have dialed has been disconnected or is no longer in service". Is this Verizon's fault? Well, yeah, it's their job, but the regional failure is impacting ATT and T-Mob as well.



I've tried WAVE, and found it has the same physical-layer intermittency-by-design (see beam-forming) as GPON, with about half the latency, which is still double what I have with my current wireless. So I know how well QUIC plays with the Internet when it isn't being used to avoid HOL blocking (in which case, no problemo). Because it assumes that establishing a tunnel is indicative of a consistent physical-layer connection.



Instead, all those little bits of JSON which result from web apps having tight-coupling worthy of an EPYC chip, incur a handshake which totally nullifies the benefit of "zero round trip" because I don't think the Internet works the way they think it does. When I see "QUIC is enhanced TCP" I laugh, it most certainly is NOT like TCP at all, because TCP isn't bothered one little bit by intermittency now, any more than it was when I bootstrapped my own rural ISP so I could have a POP to host a webserver to be a Web developer, after having downloaded Mosaic over a 2400-baud Compuserve connection, so I could provide intermittent connectivity via modem.



I opened 30 years ago, today. When 911 could always be counted on to work. Now, locals who need an ambulance know to call the Sheriff's Dept. # because that's all 911 is -- an alias for local EMS dispatch. Of course, it helps to have a land line, and it's interesting to note that GPON RJ-15 POTS service is unaffected (like it would be if it were VOIP). Because you can't use a cell phone to call 911 when it isn't working, because your phone will also not be working.



Because Memorial Day. Tourist influx. Now with more people sending more data up than ever. Using QUIC when it isn't necessary. We don't have enough cell towers to handle the load. The ones we have are shared by all. While I welcome everyone to visit Colorado, please do be careful this summer, because if you need an ambulance...



Well, we'll be fine here, because EMS IP fails over to two pairs of OST 56Kbps digital modems on the old microwave repeater towers, down to Denver. I turned them on 30 years ago, today. They've long since been relegated to standby, but my first POP was a rack in the County DC, and when 3com rug-pulled USRobot customers and my ISP career ended in disaster...



...don't worry, my SPARC webhosting empire would do well for several years until Oracle rug-pulled Open Solaris...



...so I donated my setup to EMS. The other end passed from Colorado Internet Cooperative Association to telco-direct, same rack. Those modems' routing has changed over time, but they've never powered down for so much as a second. One thing I know about, is the physical layer issues impacting rural America even more than the Third World. 128Kbps ftw! Took 30 years of involvement in local effort to bring fiber here.



But, we got had, in more ways than one (supposed to be a loop). Two years ago we were down for a couple days when a rancher backhoed through the backbone. Everyone blamed him. He said the utility locator guy told him he could dig there. So everyone blamed that guy. That guy said, I know my job, he dug where I told him the fiber wasn't. The contractor who laid it's long gone, so nobody knows where we're going to get the money to pull locator wire, because they only used it under roadways and nobody thought to check.



Anyway, QUIC is goshawfully bad at everything that isn't video streaming (audio will be shunted to the phone laser and capped at DSL), because I have to regain the focus and attention of the laser on the optical switch. It is not permanently tasked to me. My physical layer's fine, but that doesn't mean I have a tunnel.



TCP/IP - no problem

UDP/IP - hit or miss

SCTP/IP - there are two ways to handle TLS which I thought were a coin flip; only one plays friendly with GPON/beam-forming

QUIC/IP - fail. utter, total fail. Except for streaming.



But, what would I know about physical-layer IP networking.



-Eric