Re: [arch-d] Fwd: New Version Notification for draft-nottingham-avoiding-internet-centralization-04.txt
John Levine <johnl@taugh.com> Sun, 26 June 2022 17:48 UTC
Return-Path: <johnl@iecc.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6FA2C14CF1F for <architecture-discuss@ietfa.amsl.com>; Sun, 26 Jun 2022 10:48:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.857
X-Spam-Level:
X-Spam-Status: No, score=-1.857 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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=iecc.com header.b=PBB1m5S8; dkim=pass (2048-bit key) header.d=taugh.com header.b=rQYC6BjU
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 2nnD8dp4kb24 for <architecture-discuss@ietfa.amsl.com>; Sun, 26 Jun 2022 10:48:20 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F4BEC15AADD for <architecture-discuss@ietf.org>; Sun, 26 Jun 2022 10:48:19 -0700 (PDT)
Received: (qmail 47056 invoked from network); 26 Jun 2022 17:48:16 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=b7ce.62b89be0.k2206; bh=ah3jYPbpnjAYH1fyRL60GGMstWLDfUuhbv/PWNMWfjc=; b=PBB1m5S8UAoXesvN37OPy0tV1bsR0EdoYX3xux2Lj5woNlJfZ84PTwTjymZ/sTsq2YDUZNzZvfzPnuC7RYsUuVlMt11MS+v2DmAWrd9MG7i9UeRfH6S0yzcJtFkP1uUv9rre0anZJ+CE1Xd+f5TbVbFiU0grnOI+7qp4xblO0qP45WuNQLyUABApi13wFcvTfp/vonvXCvomOgw0jp5sdXXmyMmTe0p4lGCgiIIag9oxG/sWqXndKx+0VXyhSHMq9AeoDSL/T3iDV0ChrwmSiXp5ld4wst/+KJt29QdeY1g91n4xyllnnZmy0ji9C/V3vedOTxK/ESQoWFcHCQv9HQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=b7ce.62b89be0.k2206; bh=ah3jYPbpnjAYH1fyRL60GGMstWLDfUuhbv/PWNMWfjc=; b=rQYC6BjU1tiUcavkU7YJ1y1iksd8sHYLvU6FT6PY2vubPVBBOds6BMOzfcbAf386a1DpP2wRupaFuNJR+9DIndciTgNE9so+mz0hLOL1KjSi3wAXCD4fTq1CS97AQW9KnHl4cjX4thhuo440ILMdnjw2FH6WlptKeUqVXKHbGfBwUOvC1/xfALjkOXuO+z+daGZhrAU16UNsuzuHBS3qQc5veK0ugjNLkFLC081onku4wcxE+fZCtTj/urFJv23lg1a/KCyHn5LQWh9GwMvoztnrg+vOgydiopiY/hGX49Vr6Eo6wHlLDG3t2uLJGS28AgIfAs7xREN0+dSZzPkQ1A==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 26 Jun 2022 17:48:16 -0000
Received: by ary.qy (Postfix, from userid 501) id 5B6DC44541CD; Sun, 26 Jun 2022 13:48:15 -0400 (EDT)
Date: Sun, 26 Jun 2022 13:48:15 -0400
Message-Id: <20220626174816.5B6DC44541CD@ary.qy>
From: John Levine <johnl@taugh.com>
To: architecture-discuss@ietf.org
In-Reply-To: <7a37f7b1-80d6-00b5-7f02-ca6ee1d24250@lear.ch>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/PtWCFOzFqsFvYhrZLONhy4Cz8D8>
Subject: Re: [arch-d] Fwd: New Version Notification for draft-nottingham-avoiding-internet-centralization-04.txt
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jun 2022 17:48:25 -0000
It appears that Eliot Lear <lear@lear.ch> said: > 2. EMail has been a cesspool for a long time, and has served as a virus > vector. When these two companies collude, as they surely do, to > address cybersecurity risks, how many attacks are averted? Of course they do. What do you think M3AAWG is for? But it's more complicated than that because mail is very asymmetrical. While I can believe the the majority of mail recipients are hosted at Google and Microsoft, most mail is sent, even after you filter out the spam, from bulk mail specialists like Mailchimp and Constant Contact. That is somewhat concentrated, albeit not as much as mail hosting, and it is striking that there is no overlap between the large mail hosts and large mail senders. It's also worth noting the limits of the methods in that paper. Two of the largest "hosts" they list are Proofpoint and Mimecast, neither of which host any mail at all. They're front ends who deliver to whatever mail system the customer uses. I would guess that the most popular back end is hosted Exchange but they're not telling. > 3. The alternative to service centralization in this case might be > software concentration (Exchange and Dovecot? on the server side and > Apple Mail / Outlook on the client side, with some Google Mail > readers for Android). Having done some surveys I can tell you that the most popular mail software by far is Exim, mostly because it is packaged with the control panels that VPS providers use, but few of those installations have a significant number of users. For systems with insteresting numbers of users I'd guess it's split between Exchange at places who have to use Windows and Postfix at places that don't, with Microsoft pushing their customers pretty hard to move to hosted Exchange. I think this tells us that even figuring out what's centralized and where can be surprisingly hard. R's, John
- [arch-d] Fwd: New Version Notification for draft-… Mark Nottingham
- Re: [arch-d] Fwd: New Version Notification for dr… Eliot Lear
- Re: [arch-d] Fwd: New Version Notification for dr… John Levine