Re: [arch-d] Splintering (fragmentation) vs Centralization vs Users
Henning Schulzrinne <hgs@cs.columbia.edu> Sat, 06 May 2023 14:04 UTC
Return-Path: <hgs10@columbia.edu>
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 2211EC15154D for <architecture-discuss@ietfa.amsl.com>; Sat, 6 May 2023 07:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.695
X-Spam-Level:
X-Spam-Status: No, score=-2.695 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=columbia.edu
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 HuGVvyoYw9OE for <architecture-discuss@ietfa.amsl.com>; Sat, 6 May 2023 07:04:32 -0700 (PDT)
Received: from mx0b-00364e01.pphosted.com (mx0b-00364e01.pphosted.com [148.163.139.74]) (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 13B28C151540 for <architecture-discuss@ietf.org>; Sat, 6 May 2023 07:04:31 -0700 (PDT)
Received: from pps.filterd (m0167074.ppops.net [127.0.0.1]) by mx0b-00364e01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 346C5Wfu008836 for <architecture-discuss@ietf.org>; Sat, 6 May 2023 10:04:31 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=columbia.edu; h=mime-version : references : in-reply-to : from : date : message-id : subject : to : cc : content-type; s=pps01; bh=PNDE+/UVDz9RqPqS6coVr818Z1Xs3oHwNRfLumAivJY=; b=qZtP0Has5gJCnryUc/DA+TNipN9/3SQxi2ZwU9Vc4gNzHKSP++nEo2CsMqq7TWFZctey yohjzJ2cCwSizJJ9zi2TpiHTPPBqEpotC9UqNVnnoYfA81AFuuSxdaZnRI6xqSXO2Q+c 9RBRsiMYjDDG09ynnSiCkduU91KMYZnF6htFqCNHyayzG/DWmn68JMAG9FGpS4S9aslO HFFpazwme1iNPoD2K8BHsSed+vc8OUjJlEdJPbDxlBDLxdG6F+s2aWM5eeG4Wq19YqKF FK+iBz/MYFmSiY2HSU2ewjcbOq77yOXeAf2fH/sX5gv2WYsQLGyfRpE0Ao27KNqiDpBh lA==
Received: from sendprdmail22.cc.columbia.edu (sendprdmail22.cc.columbia.edu [128.59.72.24]) by mx0b-00364e01.pphosted.com (PPS) with ESMTPS id 3qdfxm9tdy-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <architecture-discuss@ietf.org>; Sat, 06 May 2023 10:04:30 -0400
Received: from mail-pj1-f70.google.com (mail-pj1-f70.google.com [209.85.216.70]) by sendprdmail22.cc.columbia.edu (8.14.7/8.14.4) with ESMTP id 346E4TZc008821 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for <architecture-discuss@ietf.org>; Sat, 6 May 2023 10:04:30 -0400
Received: by mail-pj1-f70.google.com with SMTP id 98e67ed59e1d1-24dfc3c668dso1401612a91.1 for <architecture-discuss@ietf.org>; Sat, 06 May 2023 07:04:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683381869; x=1685973869; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=PNDE+/UVDz9RqPqS6coVr818Z1Xs3oHwNRfLumAivJY=; b=R9Pm1NQCVljFLJgCXJZG6C2Kveei0+0IhZAfuCKX4XFLRMNZwbfMGS/wlGeofodPWq OGoVT0xFitQp5ixi7WOiww3AqcT2Izjc2TTDXpel208qXt5qJWSoorRto/CN++Kc3dhO V5Nv/SdfJI/2nd8dr7RgNatua6LKlF20SM0vM+rCsOsq8pPV5zha6k2xAXS0KT39Dlpg +3lrlxzd3ErRzjxUxwA8RuOk9saIYkgYFrSFIf0rkdWXH3JLiviUSVwrPlf631Pa7Szq rKtvHHgwRSKfKLhP+JrsFdQw1DKFLrA2bxCdHcunTBja5FAMOFxSmi3AbLSmSRUczKoj 0/vw==
X-Gm-Message-State: AC+VfDwB5GCGtHD79Zuic8Uhum9kIneiBunVvx6z9uCGduf1t998+Htf RCa5VenlBvo9cODTwLy4DSQKUcTzx4ILR3Z0fq7HWVp0CuIWrJjrWNz5VmY/pFTWjg/clOnKJzY pykiTKU5xnh5fKpaHJ63ZaBQLs74cUQ+BkXnpV5MhJ/o18hymQA==
X-Received: by 2002:a17:90a:d711:b0:250:43a6:fb02 with SMTP id y17-20020a17090ad71100b0025043a6fb02mr2926477pju.20.1683381869100; Sat, 06 May 2023 07:04:29 -0700 (PDT)
X-Google-Smtp-Source: ACHHUZ625P0w9UJ9kAdXvKgT71yF6wHmCfGmz11CbTBE+F+wYGimBnaOfZFp3Zc6P7B4faIYiBRvggr6aSijBEX3kHQ=
X-Received: by 2002:a17:90a:d711:b0:250:43a6:fb02 with SMTP id y17-20020a17090ad71100b0025043a6fb02mr2926440pju.20.1683381868573; Sat, 06 May 2023 07:04:28 -0700 (PDT)
MIME-Version: 1.0
References: <0f0da4833f81463b972558d972285595@boeing.com> <12045445-15D9-40F9-8306-4F3F98AB6BBE@apple.com> <911c3777-47e0-fad0-b0f9-7cbb81ba5a56@gmail.com> <4B5D79EE-062B-480D-AB58-E782476926BB@broadcom.com> <8af99305-de33-911a-6fd0-d9bd5f0c2294@huitema.net> <285E3C91-FD39-4565-A8A7-C32569C05A22@tony.li> <64FE3789-224F-4938-B15B-7901EA4532BD@orandom.net> <CACgrgBZWSe5DL2Yw3MZc=bzBCMAz23yWz96cuvpf4J6dZ4Xy3g@mail.gmail.com> <ZFVj8M3JDWIHkMSu@faui48e.informatik.uni-erlangen.de>
In-Reply-To: <ZFVj8M3JDWIHkMSu@faui48e.informatik.uni-erlangen.de>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Date: Sat, 06 May 2023 10:04:01 -0400
Message-ID: <CACgrgBY7v1PvDYfSL_ofKfNFOE-zcgspK6P8a=-Ef4X3fAyoUA@mail.gmail.com>
To: Toerless Eckert <tte@cs.fau.de>
Cc: "David R. Oran" <daveoran@orandom.net>, architecture-discuss@ietf.org, Internet Architecture Board <iab@iab.org>, Arnaud Taddei <arnaud.taddei=40broadcom.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004c50a805fb06e26c"
X-Proofpoint-GUID: yU3H2Y1-_wNt__lJnwFI_HHJsxYszXRA
X-Proofpoint-ORIG-GUID: yU3H2Y1-_wNt__lJnwFI_HHJsxYszXRA
X-CU-OB: Yes
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.942,Hydra:6.0.573,FMLib:17.11.170.22 definitions=2023-05-06_08,2023-05-05_01,2023-02-09_01
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 lowpriorityscore=10 phishscore=0 malwarescore=0 adultscore=0 spamscore=0 mlxscore=0 clxscore=1015 impostorscore=10 mlxlogscore=999 bulkscore=10 suspectscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2303200000 definitions=main-2305060108
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/NYdj3dUj1IDK2i_MqivkcZ3vzfg>
Subject: Re: [arch-d] Splintering (fragmentation) vs Centralization vs Users
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: Sat, 06 May 2023 14:04:37 -0000
I agree that neither technical nor legal solutions will likely solve the underlying problem completely or for all time. But that's the nature of most non-trivial problems other than math assignments. I'm in the "aim for incremental improvements compared to the status quo" party. Henning On Fri, May 5, 2023 at 4:15 PM Toerless Eckert <tte@cs.fau.de> wrote: > Thanks, Henning, interesting examples! > > On Fri, May 05, 2023 at 02:48:18PM -0400, Henning Schulzrinne wrote: > > Antitrust actions in the technology space have involved interoperability > > and protocols. Three examples: > > > > (1) The Microsoft 2001 settlement: "On November 2, 2001, the DOJ reached > an > > agreement with Microsoft to settle the case. The proposed settlement > > required Microsoft to *share its application programming interfaces with > > third-party companies a*nd appoint a panel of three people who would have > > full access to Microsoft's systems, records, and source code for five > years > > in order to ensure compliance." (Wikipedia) > > That seems to have been an effort in futility given how the efforts for > Wine have > shown that it continues to an almost impossible task of reverse > engineering trying to build > a Microsoft free runtime for Applications written for Windows in general. > Then again, > for a subset of applications, namely games, Valve seems to have been able > to produce some good > results. But i wonder if/how that settlement had any impact on that > history... > > > (2) The Carterphone and similar decisions to spur CPE competition led to > > mandatory interoperability and compatibility rules codified in Part 68 ( > > part68.org) of 47 CFR (Code of Federal Regulations). > > And now with streaming services we do have complete vertical > walled-gardens into the > (software) user application. After we had so many good experience with > such "CPE" > standard interfaces enabling a healthy competition of consumer CPE... > (i made a jump from telephony to AV-media delivery here). > > > (3) After 1996, various unbundled network interface specifications were > > created to allow competitive local exchange carriers to provide services > > via the incumbent's network. > > But if i am not mistaken (not sure about USA side details, i experienced > only the > european side) only on copper local loops because they originated from > earlier monopoly / public-funding. Coax/Cable local loop for example does > not > have these regulations. Hance the uncompetitiveness in current markets > when it > comes to coax. > > And then there was also unbundling regulations in i think many countries, > aka: > direct access to the raw copper. Which then was attempted to be > circumvented by > incumbents by promoting technologies that do not support that level of > unbundling > (vectoring). > > > I suspect there are many more. They were all downstream from laws, court > > decisions, and regulatory actions. > > Indeed. I would have expected the browser unbundling to be on top of any > list ;-) > > Cheers > Toerless > > > Henning > > > > On Fri, May 5, 2023 at 1:38 PM David R. Oran <daveoran@orandom.net> > wrote: > > > > > On 5 May 2023, at 19:20, Tony Li wrote: > > > > > > Or, perhaps the IAB might want to consider whether or not economic > > > organization is within the scope of the Internet architecture. > > > > > > Trying to control the economic forces of the entire planet through a > > > series of RFCs seems quixotic, to say the least. > > > > > > Consolidation is part of the natural evolution of any market. > Anti-trust > > > legislation has been necessary to ensure consumer protection, as no > other > > > mechanisms have ever sufficed. Expecting that we can do better would > seem > > > like an act of hubris. > > > > > > 100% agree, although it might be worth pondering if the IAB could > provide > > > useful data and advice on the technical c consequences of postulated > > > anti-trust law/policy or regulations. > > > > > > Possibly… > > > > > > > > > > > > _______________________________________________ > > Architecture-discuss mailing list > > Architecture-discuss@ietf.org > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_architecture-2Ddiscuss&d=DwIDaQ&c=009klHSCxuh5AI1vNQzSO0KGjl4nbi2Q0M1QLJX9BeE&r=an13D03Wkt_XCHvUEPar0wASef4dPIUx8hC4vYI0ROE&m=xAJZPS6clxZM3Zcu1fLN8_oS55Qc8911Z0135eqlE1qG3JS-C1sao3HyBHhPRY_y&s=K7H3AkqybqV8QeRMgUSvz6P56_Ap3702mKT3IiHa4qQ&e= > > > -- > --- > tte@cs.fau.de >
- [arch-d] IAB Technical Discussion on Fragmentatio… IAB Executive Administrative Manager
- Re: [arch-d] IAB Technical Discussion on Fragment… Eric Rescorla
- Re: [arch-d] IAB Technical Discussion on Fragment… Brian E Carpenter
- Re: [arch-d] IAB Technical Discussion on Fragment… Hesham ElBakoury
- Re: [arch-d] IAB Technical Discussion on Fragment… Bob Hinden
- Re: [arch-d] IAB Technical Discussion on Fragment… Andrew G. Malis
- Re: [arch-d] IAB Technical Discussion on Fragment… Vittorio Bertola
- Re: [arch-d] IAB Technical Discussion on Fragment… Dominique Lazanski
- Re: [arch-d] IAB Technical Discussion on Fragment… Arnaud Taddei
- Re: [arch-d] IAB Technical Discussion on Fragment… Eliot Lear
- Re: [arch-d] IAB Technical Discussion on Fragment… Brian E Carpenter
- Re: [arch-d] IAB Technical Discussion on Fragment… Mirja Kuehlewind
- Re: [arch-d] IAB Technical Discussion on Fragment… Arnaud Taddei
- Re: [arch-d] IAB Technical Discussion on Fragment… Vittorio Bertola
- Re: [arch-d] IAB Technical Discussion on Fragment… Mirja Kuehlewind
- Re: [arch-d] [EXT] Re: IAB Technical Discussion o… Vittorio Bertola
- Re: [arch-d] IAB Technical Discussion on Fragment… Brian E Carpenter
- Re: [arch-d] IAB Technical Discussion on Fragment… Arnaud Taddei
- Re: [arch-d] IAB Technical Discussion on Fragment… Toerless Eckert
- Re: [arch-d] IAB Technical Discussion on Fragment… Mirja Kuehlewind
- Re: [arch-d] IAB Technical Discussion on Fragment… Arnaud Taddei
- Re: [arch-d] IAB Technical Discussion on Fragment… Mirja Kuehlewind
- Re: [arch-d] IAB Technical Discussion on Fragment… Arnaud Taddei
- Re: [arch-d] IAB Technical Discussion on Fragment… Mirja Kuehlewind
- Re: [arch-d] IAB Technical Discussion on Fragment… Toerless Eckert
- Re: [arch-d] IAB Technical Discussion on Fragment… Hesham ElBakoury
- Re: [arch-d] IAB Technical Discussion on Fragment… Templin (US), Fred L
- Re: [arch-d] IAB Technical Discussion on Fragment… Tommy Pauly
- [arch-d] Splintering (fragmentation) vs Centraliz… Brian E Carpenter
- Re: [arch-d] [EXTERNAL] Re: IAB Technical Discuss… Templin (US), Fred L
- Re: [arch-d] [IAB] IAB Technical Discussion on Fr… Wes Hardaker
- Re: [arch-d] IAB Technical Discussion on Fragment… Toerless Eckert
- Re: [arch-d] Splintering (fragmentation) vs Centr… Stephen Farrell
- Re: [arch-d] Splintering (fragmentation) vs Centr… Arnaud Taddei
- Re: [arch-d] Splintering (fragmentation) vs Centr… Toerless Eckert
- [arch-d] public recordings of IAB meetings or not… Toerless Eckert
- Re: [arch-d] public recordings of IAB meetings or… Mark Nottingham
- Re: [arch-d] Splintering (fragmentation) vs Centr… Christian Huitema
- Re: [arch-d] Splintering (fragmentation) vs Centr… Dominique Lazanski
- Re: [arch-d] Splintering (fragmentation) vs Centr… Tony Li
- Re: [arch-d] Splintering (fragmentation) vs Centr… David R. Oran
- Re: [arch-d] Splintering (fragmentation) vs Centr… Toerless Eckert
- Re: [arch-d] Splintering (fragmentation) vs Centr… Toerless Eckert
- Re: [arch-d] public recordings of IAB meetings or… Toerless Eckert
- Re: [arch-d] public recordings of IAB meetings or… Mark Nottingham
- Re: [arch-d] Splintering (fragmentation) vs Centr… Henning Schulzrinne
- Re: [arch-d] [IAB] Splintering (fragmentation) vs… Colin Perkins
- Re: [arch-d] public recordings of IAB meetings or… Toerless Eckert
- Re: [arch-d] Splintering (fragmentation) vs Centr… Toerless Eckert
- Re: [arch-d] Splintering (fragmentation) vs Centr… Hesham ElBakoury
- Re: [arch-d] Splintering (fragmentation) vs Centr… Brian E Carpenter
- Re: [arch-d] Splintering (fragmentation) vs Centr… Brian E Carpenter
- Re: [arch-d] IAB Technical Discussion on Fragment… Watson Ladd
- Re: [arch-d] IAB Technical Discussion on Fragment… Hesham ElBakoury
- Re: [arch-d] Splintering (fragmentation) vs Centr… Hesham ElBakoury
- Re: [arch-d] Splintering (fragmentation) vs Centr… Arnaud Taddei
- Re: [arch-d] Splintering (fragmentation) vs Centr… Toerless Eckert
- Re: [arch-d] [EXT] Re: IAB Technical Discussion o… Vittorio Bertola
- Re: [arch-d] Splintering (fragmentation) vs Centr… Henning Schulzrinne
- Re: [arch-d] Splintering (fragmentation) vs Centr… Hesham ElBakoury
- Re: [arch-d] IAB Technical Discussion on Fragment… Hesham ElBakoury
- Re: [arch-d] [EXT] Re: IAB Technical Discussion o… Brian E Carpenter