Re: [antitrust-policy] Comments on the draft

Phillip Hallam-Baker <phill@hallambaker.com> Tue, 17 October 2023 16:40 UTC

Return-Path: <hallam@gmail.com>
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 086C8C14F749 for <antitrust-policy@ietfa.amsl.com>; Tue, 17 Oct 2023 09:40:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.406
X-Spam-Level:
X-Spam-Status: No, score=-6.406 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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] 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 fgyqKOjjgFEf for <antitrust-policy@ietfa.amsl.com>; Tue, 17 Oct 2023 09:40:53 -0700 (PDT)
Received: from mail-ot1-f49.google.com (mail-ot1-f49.google.com [209.85.210.49]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 4D7BAC15199C for <antitrust-policy@ietf.org>; Tue, 17 Oct 2023 09:40:53 -0700 (PDT)
Received: by mail-ot1-f49.google.com with SMTP id 46e09a7af769-6c7b3adbeb6so4158106a34.0 for <antitrust-policy@ietf.org>; Tue, 17 Oct 2023 09:40:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697560852; x=1698165652; 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=5eWgi+oxJ8p5ZDey7nucCebIuR5zxMEXMcoB6EM26VE=; b=SIXVKCQRPuCOO7HiY6TmNre2tFsGWaKkXxMskPdzVF2gI6EgBmtk+eNBok3WyuR0hR AF1a/tRn91JthU3kX8cQOhj4hXnpPp4PYrahq5Yj89DzcXqQsh7DgDtxj0O+Q+jkTPUm EIdDNrzBq81DX1J/m2DuxUM3QJf8od8Um6mBiyXMX8aRtsrb4BKxAe7ybNMJJIFMFMUw i3WTmdVZGH3saQA0e/peO8FSJeB1mhXXby4hmdRMG9zbgYkDTxIF+tEqPXbdSbfqB6uI coyfacN+mcgDH8sEYWEYzvZpsdI7WVoGVvR4Vndzh9aMPOkom2KqAO3+ppCYQKp46l8O cgmw==
X-Gm-Message-State: AOJu0YyODoo396mEOhiI7yFiBodFN2FXIwHKpG/nRt3iHiz31f4UYs6o UmU+Qdl/JMib8yxCgb17Mlz4V6orpNyHRTn9ZQeI8MjUfVs=
X-Google-Smtp-Source: AGHT+IEFK5GXXKSIkGHXspCEnr1Ctn9QjSTeOR25IpYLC52TZc/21nBsNI2DWKMm5XY2aq/zx9L2tHtXl5sCkjQ8FJE=
X-Received: by 2002:a9d:6c81:0:b0:6b9:26ce:5e5c with SMTP id c1-20020a9d6c81000000b006b926ce5e5cmr2877279otr.31.1697560852567; Tue, 17 Oct 2023 09:40:52 -0700 (PDT)
MIME-Version: 1.0
References: <CAMm+Lwg7z49u5qoXkqvqOWtdq_t1v=kZSd8scfvqrJ10dB0UYA@mail.gmail.com> <PH0PR17MB4908BF7F90E9A0F074997A4EAED6A@PH0PR17MB4908.namprd17.prod.outlook.com>
In-Reply-To: <PH0PR17MB4908BF7F90E9A0F074997A4EAED6A@PH0PR17MB4908.namprd17.prod.outlook.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 17 Oct 2023 12:40:38 -0400
Message-ID: <CAMm+LwiiXR0oijtfjQAqJbY6ooU4aQf5PidOJpS1rgc2=VhCOg@mail.gmail.com>
To: Stephan Wenger <stewe@stewe.org>
Cc: "antitrust-policy@ietf.org" <antitrust-policy@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009a39b90607ec2fed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/antitrust-policy/4RuZASiIZ7RyarQNJGsN4wpB7Ik>
Subject: Re: [antitrust-policy] Comments on the draft
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: Tue, 17 Oct 2023 16:40:54 -0000

On Tue, Oct 17, 2023 at 2:51 AM Stephan Wenger <stewe@stewe.org> wrote:

> Hi Philip,
>
> Can you please be slightly less cryptic?  Specifically:
>

Not really, there are these things called libel laws and they are almost
invariably used by malicious individuals to suppress fair comment on their
activities. Truth is a defense but does not pay the cost of a defense.


-What was “this issue”?  (link to a previous email is fine)
>
> -A more detailed characterization of the “separate standards organization”
> would help me to make up my mind whether this hearsay of alleged behavior
> were relevant to the IETF.
>

The feature in question was an IETF specification documented in an RFC and
the individual who made the threat also participates in IETF.



> -And, when was this alleged incident?
>

It occurred just before the Singapore meeting.


Thanks,
>
> Stephan
>
>
>
>
>
> *From: *antitrust-policy <antitrust-policy-bounces@ietf.org> on behalf of
> Phillip Hallam-Baker <phill@hallambaker.com>
> *Date: *Monday, October 16, 2023 at 18:46
> *To: *antitrust-policy@ietf.org <antitrust-policy@ietf.org>
> *Subject: *[antitrust-policy] Comments on the draft
>
> As one of the people who has been raising this issue, I would like to
> share a summary of the specific incident that raised my concern.
>
>
>
> The specific issue raised was in a separate standards organization and
> involved an alleged threat by an employee of a dominant application
> provider to effectively terminate the ability of service providers to
> operate if they implemented a particular feature.
>
>
>
> That situation has since been remedied and said individual is no longer
> employed by said provider, nor do they participate in any standards process
> that I am aware of.
>
>
>
> I was not present for the meeting in question but I did follow up with
> people inside the IETF and the senior management of the company in question.
>