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

Jay Daley <exec-director@ietf.org> Mon, 06 September 2021 22:05 UTC

Return-Path: <exec-director@ietf.org>
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 AD5053A148B for <gendispatch@ietfa.amsl.com>; Mon, 6 Sep 2021 15:05:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vhnKnjUiNSfm for <gendispatch@ietfa.amsl.com>; Mon, 6 Sep 2021 15:05:44 -0700 (PDT)
Received: from ietfx.ietf.org (ietfx.ietf.org [4.31.198.45]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8DAE3A1490 for <gendispatch@ietf.org>; Mon, 6 Sep 2021 15:05:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id D001148FFB00 for <gendispatch@ietf.org>; Mon, 6 Sep 2021 15:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from ietfx.ietf.org ([4.31.198.45]) by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 39SgCc_2Vn2G for <gendispatch@ietf.org>; Mon, 6 Sep 2021 15:05:39 -0700 (PDT)
Received: from smtpclient.apple (unknown [158.140.230.105]) by ietfx.amsl.com (Postfix) with ESMTPSA id 6C8E348FE867 for <gendispatch@ietf.org>; Mon, 6 Sep 2021 15:05:39 -0700 (PDT)
From: Jay Daley <exec-director@ietf.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
Date: Tue, 07 Sep 2021 10:05:33 +1200
References: <20210906191255.760B42778391@ary.qy>
To: GENDISPATCH List <gendispatch@ietf.org>
In-Reply-To: <20210906191255.760B42778391@ary.qy>
Message-Id: <6F720ED1-DFC6-4DF0-B36A-BE5379F10F5A@ietf.org>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/aRwjkNOieL2FyzW9lYCkS18jQAA>
Subject: Re: [Gendispatch] I-D Action: draft-halpern-gendispatch-antitrust-00.txt
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 06 Sep 2021 22:05:50 -0000

If I could summarise the issues I’ve heard here:

1.  Rob wants section 5 rephrased from recommending the avoidance of certain discussions, to warning people about certain discussions.  Mark makes a similar suggestion in order to avoid any recommendations being weaponised to prevent legitimate discussions.

2.  Lloyd points out that he would be unable to voluntarily share his compensation and benefits details

3.  Mark points out (I think) that preventing all discussion of compensation and benefits could be akin to imposing a "no poaching of competitors staff" policy for the IETF

4.  S. Moonesamy points out that "dominant position" should be better explained as relating to participants whose employer maybe in a dominant market position.

5.  Rob wants to hear from an actual lawyer (in case there’s any doubt - I am not a lawyer) that the phrase "This document does not contain legal advice" is a meaningful legal phrase, while Brian recommends the alternative "This document does not constitute formal legal advice".

6.  Mark is concerned that dealing with the possible abuse of a dominant position is unnecessary given there have been no cases brought to suggest that regulators are concerned with this

7.  Stephen points out that he would be unable to discuss the FLOSS business model in relation to specific supply chains.

Does that capture it?

Jay


> On 7/09/2021, at 7:12 AM, John Levine <johnl@taugh.com> wrote:
> 
> It appears that Brian E Carpenter  <brian.e.carpenter@gmail.com> said:
>>> IETF engineers can't discuss employee compensation or benefits?
>> 
>> What the draft advises is that such matters should not be part of a standardisation discussion. Not being an anti-trust or competition lawyer, I don't
>> know why such a discussion might be a legal exposure, but it would be a very silly thing to discuss in a standardisation context, so I can't see any
>> conceivable objection to the advice.
> 
> The scenario is that a manager at company A says "we pay our engineers
> about $120K", manager at company B says "huh, I guess we won't need to
> give ours a raise."
> 
> In general it is illegal for competitors to coordinate the way they do
> business. Stanrdards development has a carveout because there there
> is a widely understood benefit to the public for competing products
> to interoperate.  That isn't limited to software; it's why the lightbulbs
> you buy at the hardware store fit into the sockets in the desk lamps you
> bought at the office supply store.
> 
> R's,
> John
> 
> PS: This still isn't legal advice.
> 
> -- 
> Gendispatch mailing list
> Gendispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/gendispatch
> 

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org