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

Abdussalam Baryun <abdussalambaryun@gmail.com> Fri, 24 February 2023 06:48 UTC

Return-Path: <abdussalambaryun@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 ED370C14CE3B for <antitrust-policy@ietfa.amsl.com>; Thu, 23 Feb 2023 22:48:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.994
X-Spam-Level:
X-Spam-Status: No, score=-1.994 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 (2048-bit key) header.d=gmail.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 THKslToRw3t0 for <antitrust-policy@ietfa.amsl.com>; Thu, 23 Feb 2023 22:48:01 -0800 (PST)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 5D4DCC14CE4A for <antitrust-policy@ietf.org>; Thu, 23 Feb 2023 22:48:01 -0800 (PST)
Received: by mail-lf1-x135.google.com with SMTP id m6so16785891lfq.5 for <antitrust-policy@ietf.org>; Thu, 23 Feb 2023 22:48:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=zHS3lIKYWuvyFKfMmjbvcuHMBKZ9/Qj40eADESnFm5s=; b=o1Ay5lW4BRm4LQmM9Z+cuxtldqpnQjFXXYzyJzTImN82dnWUsnb/0b+aN5/iOTjLWR B72q6wxnJygQBH1B3FqCFqVUWa0ulQLWmWzH3whwaR8c0RG+mfPzwQuKcNlCTn5BU0Cl RbcLlFAVw/D5XTKj+C5D7ZMTvORxr2q080Uyj220SCks4+JkCak/uNqdxqKT3Na0FrD2 gjj4vUjH5+cDvvm5ECpY8VXSLMt7ryFuFjRp3JHMkQT+Psn67aAYNjeM6zMzerMATwHQ z3ETHhnYMOyAx8xqe5NBYl6W4K8b8vmMdvt1FRdlMDmPP6xkiPocb3+/cjqmUEopVRjd 8YPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=zHS3lIKYWuvyFKfMmjbvcuHMBKZ9/Qj40eADESnFm5s=; b=fv5kg6MHaTP+ML/AilhZEh6iSBoPcAgBUNTsRJY7JU6unNTlocZcVgKkrlELWOW8hU PixKx/l+IKeQgSHacWVooRU2b89VVMBFH/hAu44pXjRT6Ksc1oKfomdbsexZTlUPMr5W y56+BJLweXXjpELeKXFewaTsCNhdjyTPRgILG/cfzpkgcah0c0xvrxkd3VRzNVsQpt4r YTzvi61XyK4zXGM1adf8gYtfn2n83u8ArDKmR25FpVxDV/Jucd+wUFQ617T6h3Skaisw +safU3BdffyUbivPOZMyKt6/rdvwixYvYUYN3NnspntF+1oAvkIIk2F7sK9QewGPLAWV F62A==
X-Gm-Message-State: AO0yUKXXPu4P1ZIxoivaEpblGys8YOw6FKMTARNk7QJFropdl14Hv1uv ntvJn7/kd+602EoogAltGhfcro8Jzcf284LKxfg=
X-Google-Smtp-Source: AK7set8HuY1BFG6R2+MGj+FhLqnQfT0G4aT4cYScbYF1AfKLgMUTflyXJZI/7SZLVMl820OL/SLyz5qO/W3XP/UJmtk=
X-Received: by 2002:a19:7416:0:b0:4d5:ca32:9bd6 with SMTP id v22-20020a197416000000b004d5ca329bd6mr4534915lfe.2.1677221279239; Thu, 23 Feb 2023 22:47:59 -0800 (PST)
MIME-Version: 1.0
References: <dbc9ba5b-992b-eaf0-9cc7-6bf7e4526453@joelhalpern.com> <CADnDZ8_LNKQPLRgwqjDWyPFDxzFRN55EYCErYoPkxu=h+woDZg@mail.gmail.com> <A5D26E35-BB59-432C-AA69-73BBD49017C8@akamai.com>
In-Reply-To: <A5D26E35-BB59-432C-AA69-73BBD49017C8@akamai.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Fri, 24 Feb 2023 08:46:38 +0200
Message-ID: <CADnDZ88v56dKSeUWtM+JsK+zXoV9SPB5eQW3DPEgtGMPaqWhuA@mail.gmail.com>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: Joel Halpern <jmh@joelhalpern.com>, "antitrust-policy@ietf.org" <antitrust-policy@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008f12d205f56c82c3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/antitrust-policy/reMPwRlYmNRcVbOWo7BR-2Zfrpo>
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 06:48:05 -0000

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$>
>
>