Re: [antitrust-policy] New Version Notification for draft-halpern-gendispatch-antitrust-06.txt

Rigo Wenning <rigo@w3.org> Fri, 25 August 2023 13:43 UTC

Return-Path: <rigo@w3.org>
X-Original-To: antitrust-policy@ietfa.amsl.com
Delivered-To: antitrust-policy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FE45C1519BD; Fri, 25 Aug 2023 06:43:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.091, 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 BRea7Fo9jUWC; Fri, 25 Aug 2023 06:43:42 -0700 (PDT)
Received: from isaac.sophia.w3.org (isaac.sophia.w3.org [193.51.208.85]) (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 1323DC1519AA; Fri, 25 Aug 2023 06:43:36 -0700 (PDT)
Received: from lfbn-ncy-1-576-127.w81-51.abo.wanadoo.fr ([81.51.191.127] helo=[192.168.1.34]) by isaac.sophia.w3.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from <rigo@w3.org>) id 1qZX63-00DKLL-24; Fri, 25 Aug 2023 13:43:31 +0000
Message-ID: <f88dbd64-7b26-8222-817d-957ac73515b1@w3.org>
Date: Fri, 25 Aug 2023 15:43:29 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0
Content-Language: en-US, fr-FR, de-DE
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Jay Daley <exec-director@ietf.org>, "antitrust-policy@ietf.org" <antitrust-policy@ietf.org>
Cc: Stephan Wenger <stewe@stewe.org>, Alissa Cooper <alissa@cooperw.in>, Jorge Contreras <cntreras@gmail.com>, Brad Biddle <brad@biddle.law>
References: <168901026560.7883.14919362245027450565@ietfa.amsl.com> <2AE74757-7A99-49EC-8CCF-615CCAB21B6C@ietf.org> <773FB56E-910A-4A74-975B-4D6D97837C23@cooperw.in> <49AF030C-5A32-4C82-91AA-E65F6FA853CA@ietf.org> <8DBD9C3E-2135-4D67-A01E-B2843726391F@cooperw.in> <2f06c146-42f8-f534-d181-121f7007cd35@joelhalpern.com> <CAP0PwYYvS-XyVDezq6hpLXau6rFoFK=AOKhA=-2XLJFsF2gqow@mail.gmail.com> <PH0PR17MB4908C0FE7A97BD33C0D8FA7BAE00A@PH0PR17MB4908.namprd17.prod.outlook.com> <CAP0PwYYAzD8N_9MDGQ0-xTpNtZqpjJY0=dkLwUASQ8Zzze8caw@mail.gmail.com> <628B9176-2E66-4D32-9049-F02513A5857E@ietf.org> <bec953cb-0f54-d92a-1cc7-45bc8e4b467f@cs.tcd.ie>
From: Rigo Wenning <rigo@w3.org>
In-Reply-To: <bec953cb-0f54-d92a-1cc7-45bc8e4b467f@cs.tcd.ie>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------06b3fCiiF1acoHeWg5xfsBQq"
Archived-At: <https://mailarchive.ietf.org/arch/msg/antitrust-policy/iXNOdfEUQkAln9fCQq8D4nv0nBE>
Subject: Re: [antitrust-policy] New Version Notification for draft-halpern-gendispatch-antitrust-06.txt
X-BeenThere: antitrust-policy@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discuss the need for an antitrust or competition policy for the IETF." <antitrust-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/antitrust-policy>, <mailto:antitrust-policy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/antitrust-policy/>
List-Post: <mailto:antitrust-policy@ietf.org>
List-Help: <mailto:antitrust-policy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/antitrust-policy>, <mailto:antitrust-policy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Aug 2023 13:43:46 -0000

Stehpen,

On 25.08.23 13:41, Stephen Farrell wrote:
> 
> Maybe the problem is the phrase "market data"? Is
> that meant to include/exclude e.g. reports that
> trials have found that a new TLS extension causes
> some deployed implementations to misbehave?

Communication is complex. Rulings on communication are as complex. The 
issue here is that "market data" or any other type of data (prices) are 
set as absolute without taking into account the purpose of that 
communication.

But all the guidelines on horizontal agreements (that I know) ALWAYS 
include an intrinsic condition on the purpose of the communication. And 
this intrinsic condition is that the communication is done with the goal 
of market manipulation. This is why standards are permissible despite 
the fact that they are horizontal agreements.

This is the weak point of the current way the ID tries to address the 
issue. A certain type of data or content in communication is set equal 
to competition limitation. This then turns into the well known game: You 
can't say black, white, red, good and bad. If you do, you're 
out/sanctioned. Oh, look at the 3 colored balls, which one do you want?

The name of the game is interoperability. As long as something furthers 
interoperability, there can't be any competition limitation. Because 
interoperability substantially furthers competition.

The rest of the ID concerns very knowledgeable guidelines on the crazy 
US liability system. The discussion could benefit from making this more 
transparent.

just my 2 cents

  -- Rigo