IETF Logo Mail Archive

Re: [Gendispatch] I-D Action: draft-halpern-gendispatch-antitrust-03.txt

Christian Huitema <huitema@huitema.net> Sun, 23 October 2022 22:46 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7946C14F739 for <gendispatch@ietfa.amsl.com>; Sun, 23 Oct 2022 15:46:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 MRd2A-ewVwNc for <gendispatch@ietfa.amsl.com>; Sun, 23 Oct 2022 15:46:47 -0700 (PDT)
Received: from mx36-out21.antispamcloud.com (mx36-out21.antispamcloud.com [209.126.121.69]) (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 23977C14F736 for <gendispatch@ietf.org>; Sun, 23 Oct 2022 15:46:46 -0700 (PDT)
Received: from xse148.mail2web.com ([66.113.196.148] helo=xse.mail2web.com) by mx257.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1omjju-0000zM-TX for gendispatch@ietf.org; Mon, 24 Oct 2022 00:46:45 +0200
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 4MwYGm3ZtBzBK1 for <gendispatch@ietf.org>; Sun, 23 Oct 2022 15:46:40 -0700 (PDT)
Received: from [10.5.2.31] (helo=xmail09.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1omjjs-0006n5-A2 for gendispatch@ietf.org; Sun, 23 Oct 2022 15:46:40 -0700
Received: (qmail 4433 invoked from network); 23 Oct 2022 22:46:38 -0000
Received: from unknown (HELO [192.168.200.66]) (Authenticated-user:_huitema@huitema.net@[72.235.197.84]) (envelope-sender <huitema@huitema.net>) by xmail09.myhosting.com (qmail-ldap-1.03) with ESMTPA for <sayrer@gmail.com>; 23 Oct 2022 22:46:37 -0000
Content-Type: multipart/alternative; boundary="------------dAJuvkj1iepFojH1yPE6FZZr"
Message-ID: <57aac5ef-00cb-0883-312b-a42ae82810dd@huitema.net>
Date: Sun, 23 Oct 2022 12:46:35 -1000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.3.3
Content-Language: en-US
To: Rob Sayre <sayrer@gmail.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Mark Nottingham <mnot@mnot.net>, John Levine <johnl@taugh.com>, gendispatch@ietf.org
References: <20221023031849.135234D275E4@ary.local> <58e68b60-0b62-ab99-3f07-8ec689680347@cs.tcd.ie> <3BC93084-A5BF-4A5B-A503-BDD003EB35F5@mnot.net> <1efe75ce-9c8d-882f-4cd9-017e03a95e09@cs.tcd.ie> <CAChr6Syq_+O=RxzhTKQPyLLuKKC_GHqWZ3eOuGa3od11OCfLkA@mail.gmail.com> <f24f4195-51d9-1491-6140-7aae6991ad91@cs.tcd.ie> <CAChr6Sz+9xE-nFnPiuqOiMpa5r3eNeFr3GRMOYJS=hYvgOo4fA@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
In-Reply-To: <CAChr6Sz+9xE-nFnPiuqOiMpa5r3eNeFr3GRMOYJS=hYvgOo4fA@mail.gmail.com>
X-Originating-IP: 66.113.196.148
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT9WLQux0N3HQm8ltz8rnu+BPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5zo9mwGQSX8aTDq8fl2bpi0xEQ8ojMxulvqpenB6oiqu7Tk zVUqhEtc5n8LQcK5B/jrtcjzPLB8l26cZcetnKkDSxIRXVMlFuiz/acFNeeXtxN2fFxZWB9eYgpR BRu3UlDHMLIJYRi1cXH9Dbm+IxLV+FX9PGC+aKmX8jIc3TSveHGFd932lfz+R/06O3Iy4amaVarp Z0LfU2AP/MzLXlymkVWClPVvbW5lVyQanRxw5hTHswbbB/ha+ZWrSAi8SkwqWAikMcSxTAWn8RCv ieGEqjG/gXZAaRh1X6LVetRf2ZYIiHqfCgG4wrA3w4/kQTYKxDHA9JN9J4k4XZq11JQkMemT4rxn nByU11Ftkqf3f/PF3GUV+KdBBqrnCX8j0Gi8Ksk+aedMfNWSnJswrtlNtZo3HPHi5Q+jjsF5dcBx esT5ugtW33qEiSgkZE9WYd8H0+lPwKr4i5mAANUcVraZYOaeuiH/yEdZH8S1+TgcJBOjh0vPxcQO jKKOrYIQYpwamUdylUIKhf3z2GAHxH7IBAaAB9SiL80iwHtGBZiikgJ7Yk+SWN8eNDNBlkTeVa3v U+qrs6CQ3oh6MHETIo+fKK8qgoX3qtqBY7olcAAV8pXloqisSitb6n6JVjosdW/TulJRptMnEIdG JW7dfhGq92PNDpgLsd6Ddd/s7VM53uWYadJLoPyLA7ZFcI4pVucOtp+q3yU+z72+fnpodgpDO3/Z 2rJ95P38eU/JAmccxfRXgCyjj4wyUjNuPi/uWndmMRr+w2X69ygMahiTQMBdbWVvnjqWQOkMK5tg /RNuVPoPFZIShBSdpVJW5HbjQTCUIzbw71BPKv8cPtVshTSLr6YHJu91A3avrF49rf9JcoEpejCA XczArXyV+OFXiMtbLPp9n350Mbemie5JWWm/MpxAyl4q1x5O0+PBD/gPmWjXVA9S7TnWXDlmMpVd cwCFwrnT0GQK/7labXRdXAB+MS+4ayUpOtEhdxekWDmK9g==
X-Report-Abuse-To: spam@quarantine14.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/Z0WyCR-zA8UrwHE-Kue39Xze3U0>
Subject: Re: [Gendispatch] I-D Action: draft-halpern-gendispatch-antitrust-03.txt
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Oct 2022 22:46:47 -0000

On 10/23/2022 12:36 PM, Rob Sayre wrote:
> On Sun, Oct 23, 2022 at 3:24 PM Stephen Farrell 
> <stephen.farrell@cs.tcd.ie> wrote:
>
>
>     I read the draft as telling us we ought not discuss whether
>     or not some proposed protocol design re-enforces the mobile
>     OS duopoly.
>
>
> Can you outline any protocol design that has done this? I think it's 
> mostly been hardware rather than information theory.


There have been already IAB workshops on the subject of concentration. 
They show two categories of IETF developments that are relevant:

* Lack of some standards may tilt the market towards big servers -- 
classic example would be lack of effective standards for defense against 
DDOS, which makes it rather heroic to try run your own servers and 
pushes towards outsourcing to big companies.

* Development of standards specifically tailored for big-scale 
operation, which does no harm to small scale operations but does 
increase the benefits of large scale.

The other classic example is developing standard with excessive 
complexity. Of course opinions on what is excessive complexity vary.

-- Christian Huitema

v2.23.0 | Report a Bug | By Email