Re: [antitrust-policy] https://datatracker.ietf.org/doc/draft-halpern-gendispatch-antitrust/

Joel Halpern <jmh@joelhalpern.com> Fri, 24 February 2023 09:53 UTC

Return-Path: <jmh@joelhalpern.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 EEB99C16B5AD for <antitrust-policy@ietfa.amsl.com>; Fri, 24 Feb 2023 01:53:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 cCwHY8XT0e68 for <antitrust-policy@ietfa.amsl.com>; Fri, 24 Feb 2023 01:52:58 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 15485C16B5A6 for <antitrust-policy@ietf.org>; Fri, 24 Feb 2023 01:52:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4PNQDn5j5sz6Gq2g; Fri, 24 Feb 2023 01:52:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1677232377; bh=/9eW0DQRPg/qAYMDrRTDdV9HWVJ+94/UHaaaafp6Ggc=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=fdWS7Y6gOhxMIShxovUZp0/ctx+sIAOV3X09l/di4Y8cENdTcoiOnVwx6yLS/HiDg SKFvNfy+rlzJ/edDeXLIvH4nnxllfTGoPoQ8kYSSwZTdaGX24Ftpc9Sf4BZdveYEzH 6/UZYoioSGWiycfoSCZQhs3nkjA6789EN9/WpOiQ=
X-Quarantine-ID: <m8kSTF7B6KFE>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.21.74] (unknown [50.233.136.230]) (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 maila2.tigertech.net (Postfix) with ESMTPSA id 4PNQDn0470z6G9M1; Fri, 24 Feb 2023 01:52:56 -0800 (PST)
Content-Type: multipart/alternative; boundary="------------oSXD8JzLzj0I4QPZENJg2clx"
Message-ID: <f2a9c863-b14a-9807-31cb-1ce487f6bd23@joelhalpern.com>
Date: Fri, 24 Feb 2023 04:52:50 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0
Content-Language: en-US
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Cc: "antitrust-policy@ietf.org" <antitrust-policy@ietf.org>
References: <dbc9ba5b-992b-eaf0-9cc7-6bf7e4526453@joelhalpern.com> <CADnDZ8_LNKQPLRgwqjDWyPFDxzFRN55EYCErYoPkxu=h+woDZg@mail.gmail.com> <A5D26E35-BB59-432C-AA69-73BBD49017C8@akamai.com> <CADnDZ88v56dKSeUWtM+JsK+zXoV9SPB5eQW3DPEgtGMPaqWhuA@mail.gmail.com>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <CADnDZ88v56dKSeUWtM+JsK+zXoV9SPB5eQW3DPEgtGMPaqWhuA@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/antitrust-policy/kKUClGFqGwXwOdrprpqRz6FF0rs>
Subject: Re: [antitrust-policy] https://datatracker.ietf.org/doc/draft-halpern-gendispatch-antitrust/
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, 24 Feb 2023 09:53:02 -0000

As you note, the document is informational.  As such, I do not 
understand how the document could assign responsibility for oversight to 
anyone.  Assigning responsibility is a policy matter, not an 
informational one.

Yours,

Joel

On 2/24/2023 1:46 AM, Abdussalam Baryun wrote:
>
>
> On Thu, Feb 23, 2023 at 4:13 PM Salz, Rich <rsalz@akamai.com> wrote:
>
>     I think picking one person to be responsible for enforcement is a
>     very bad idea.
>
>
> This document is informational, so the reader needs to know who is 
> responsible for such policy, as any policy in any_organisation/IETF 
> should have a way of control or responsibility noticed. The 
> key_recommend_section within the draft gives recommendations but I did 
> not know if I should (as all participants) be responsible  for such 
> anti-trust, or one person or two, etc.
>
>     There are thousands of IETF participants and probably hundreds of
>     thousands of conversations.
>
>
> the most important discus_ones are the IESG conversations which may be 
> affected by the related policy, IMHO this policy is related 
> to organisation managements not staff or participants.
>
>     Nobody can enforce compliance across that. Second, picking one
>     person as the compliance person would be painting a big target
>     marker on their back, for any patent-happy entity that wishes to sue.
>
>
> The authors need to decide to not ignore such important information 
> the reader may want to know. However, I don't think it is a bad idea 
> to give information about responsibilities within IETF, and if no 
> one/some are responsible I think it will be good to add as information 
> to the reader to understand.
>
> AB
>
>     *From: *Abdussalam Baryun <abdussalambaryun@gmail.com>
>     *Date: *Thursday, February 23, 2023 at 1:00 AM
>     *To: *Joel Halpern <jmh@joelhalpern.com>
>     *Cc: *"antitrust-policy@ietf.org" <antitrust-policy@ietf.org>
>     *Subject: *Re: [antitrust-policy]
>     https://datatracker.ietf.org/doc/draft-halpern-gendispatch-antitrust/
>
>     I think one of the key recommendation is to add: (XXXX) is
>     recommended to be responsible to insure antitrust-policies and to
>     monitor activities that are related to this matters.
>
>     IMHO the IETF chair, should be the responsible member within the
>     document, however, this document needs to inform us who is the
>     member to be monitoring this policy or who is the one that we can
>     depend on.
>
>     AB
>
>     On Wed, Feb 22, 2023 at 3:47 PM Joel Halpern <jmh@joelhalpern.com>
>     wrote:
>
>         When this was dispatched, I said I would poke folks again.
>
>         The authors would very much appreciate comments, opinions, and
>         better
>         discussion of, this draft.  We would like to be able to submit a
>         revision addressing concerns by the cutoff, to align with the
>         ADs goal.
>
>         Thank you,
>
>         Joel
>
>         _______________________________________________
>         antitrust-policy mailing list
>         antitrust-policy@ietf.org
>         https://www.ietf.org/mailman/listinfo/antitrust-policy
>         <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/antitrust-policy__;!!GjvTz_vk!Rc9iyMxfvtXWtiThNAYh9lHoCN6yNVvKRiG5FLgk5eoS5rIaWP3FCaHBXRDqakKPIVb3y0q2jrVqY7MxeKD3hUM$>
>