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

"Joel M. Halpern" <jmh@joelhalpern.com> Sat, 04 September 2021 00:09 UTC

Return-Path: <jmh@joelhalpern.com>
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 DB54E3A081D for <gendispatch@ietfa.amsl.com>; Fri, 3 Sep 2021 17:09:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kVaLpiVdnJrC for <gendispatch@ietfa.amsl.com>; Fri, 3 Sep 2021 17:09:33 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30DCC3A081B for <gendispatch@ietf.org>; Fri, 3 Sep 2021 17:09:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4H1Zlw5SYlz1nttk; Fri, 3 Sep 2021 17:09:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1630714172; bh=nc0mfXARV7/5kJt4jRl8yOd6D6MJvFkndDzL7lbld4g=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=E/qWDnSRIfCr5M/7/MOoabE12u/8TG+dqinS9MKfZnAwWUW96fB8bMIEziFnSuAYZ zDvxs+zvKwHyirgZoOp7fnV72xgVYz1KAcv+TeJWmjGy0rGM8CiSKpGHB2zrvXoErE 0Y1jo/crBnIjeR7Kd5H5CcvETQY2Ugm43i/gk2UU=
X-Quarantine-ID: <zaUYHGA1lkHn>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.23.64] (50-233-136-230-static.hfc.comcastbusiness.net [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 mailb2.tigertech.net (Postfix) with ESMTPSA id 4H1Zlv3nNWz1ntVZ; Fri, 3 Sep 2021 17:09:30 -0700 (PDT)
To: Rob Sayre <sayrer@gmail.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: GENDISPATCH List <gendispatch@ietf.org>
References: <163037412640.15437.266878243771416247@ietfa.amsl.com> <aba87ef2-326f-74de-f939-dd169c1171b2@gmail.com> <3a105324-b47f-da53-b4b6-56c2db3f2ec1@cs.tcd.ie> <CAChr6SyQ99YFDjxY_0o2OZhi8-MAY9PHh2zbxE49Vdp67Lyq7g@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <9ca967d9-1548-4d8b-f5a0-54a35c59d279@joelhalpern.com>
Date: Fri, 03 Sep 2021 20:09:29 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <CAChr6SyQ99YFDjxY_0o2OZhi8-MAY9PHh2zbxE49Vdp67Lyq7g@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/v04baA-cnWELBtOhq-vy4K2IBiE>
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: Sat, 04 Sep 2021 00:09:38 -0000

We wrote this as guidelines, not rules, because there are always some 
edge cases.

But that list (which you quote below) is I think the list almost every 
lawyer I have talked to about this gave me to start with.  If you are 
talking about any of those things, you need to be VERY careful.  Which 
is also why we suggest talking to your own lawyer if you are going to 
venture into those spaces.

Yours,
Joel

PS: I appreciate folks are starting to look at this draft.  All comments 
more than welcome.  If this is going to advance, it needs community 
discussion and I hope eventually community support.

On 9/3/2021 7:04 PM, Rob Sayre wrote:
> Hi,
> 
> I think I understand the motivation here, but I'm not sure the text is 
> right.
> 
>    " As the IETF is a standards development environment where
>     representatives from competitors are highly likely to be present,
>     participants should not discuss the following topics:
> 
>     *  product pricing
>     *  profit margins
>     *  business relationships between specific vendors and customers
>     *  details of particular supply chains
>     *  specific market opportunities
>     *  employee compensation or benefits
> 
>     While not all discussions of these topics would necessarily be
>     antitrust violations, prudence suggests that avoiding these topics
>     altogether best mitigates antitrust risks."
> 
> So, clearly, using an IETF list to agree on pricing is not appropriate 
> (and not very intelligent, imo).
> 
> But, is it wrong to point out "business relationships between specific 
> vendors and customers" in evaluating an I-D? I am not sure that is the 
> case, and this draft seems to preclude such discussion. How else would 
> one raise venue-shopping or rubber-stamping?
> 
> thanks,
> Rob
> 
> On Fri, Sep 3, 2021 at 3:24 PM Stephen Farrell 
> <stephen.farrell@cs.tcd.ie <mailto:stephen.farrell@cs.tcd.ie>> wrote:
> 
> 
>     Hmm. I think "should not discuss" and that list are too high
>     or the wrong barrier. I reckon it'd take some discussion to
>     get that right. I don't object to trying to get it right, but
>     would object to the current text.
> 
>     As an example, it seems to me entirely fine to (carefully:-) discuss
>     the
>     fact that a thing(*) is unencumbered as far as
>     we know and how that affects implementations that might use
>     that thing, especially those taking an open source approach.
> 
>     Cheers,
>     S.
> 
>     (*) s/thing/codec/ or s/thing/encryption alg/ both work with
>     differences.
> 
>     On 03/09/2021 23:07, Brian E Carpenter wrote:
>      > Thankyou for this draft. Assuming the question will be put, I
>     strongly support dispatching it ASAP as an individual submission
>     sponsored by the General AD.
>      >
>      > I have one suggestion. The Recommendations very correctly list
>     'product pricing' as a forbidden topic. That should probably be
>     'product and service pricing'. However, a topic of technical
>     importance in service provision is *metrics* used for measuring
>     services. I think the draft could usefully discuss the dividing line
>     between technical specifications of metrics (OK), mechanisms for
>     communicating metrics (OK), mechanisms for communicating pricing of
>     metrics (presumably OK), worked examples with example monetary
>     values (presumably OK) and actual monetary values (not OK).
>      >
>      > FYA:
>     https://datatracker.ietf.org/doc/html/draft-carpenter-metrics-00
>     <https://datatracker.ietf.org/doc/html/draft-carpenter-metrics-00>
>      >
>      > Regards
>      >     Brian Carpenter
>      >
>      > On 31-Aug-21 13:42, internet-drafts@ietf.org
>     <mailto:internet-drafts@ietf.org> wrote:
>      >>
>      >> A New Internet-Draft is available from the on-line
>     Internet-Drafts directories.
>      >>
>      >>
>      >>          Title           : Antitrust Guidelines for IETF Particiants
>      >>          Authors         : Joel M. Halpern
>      >>                            Brad Biddle
>      >>                            Jay Daley
>      >>      Filename        : draft-halpern-gendispatch-antitrust-00.txt
>      >>      Pages           : 6
>      >>      Date            : 2021-08-30
>      >>
>      >> Abstract:
>      >>     This document provides guidance for IETF participants on
>     compliance
>      >>     with antitrust laws and how to reduce antitrust risks in
>     connection
>      >>     with IETF activities.
>      >>
>      >>
>      >> The IETF datatracker status page for this draft is:
>      >>
>     https://datatracker.ietf.org/doc/draft-halpern-gendispatch-antitrust/ <https://datatracker.ietf.org/doc/draft-halpern-gendispatch-antitrust/>
>      >>
>      >> There is also an HTML version available at:
>      >>
>     https://www.ietf.org/archive/id/draft-halpern-gendispatch-antitrust-00.html
>     <https://www.ietf.org/archive/id/draft-halpern-gendispatch-antitrust-00.html>
>      >>
>      >>
>      >> Internet-Drafts are also available by anonymous FTP at:
>      >> ftp://ftp.ietf.org/internet-drafts/
>     <ftp://ftp.ietf.org/internet-drafts/>
>      >>
>      >>
>      >> _______________________________________________
>      >> I-D-Announce mailing list
>      >> I-D-Announce@ietf.org <mailto:I-D-Announce@ietf.org>
>      >> https://www.ietf.org/mailman/listinfo/i-d-announce
>     <https://www.ietf.org/mailman/listinfo/i-d-announce>
>      >> Internet-Draft directories: http://www.ietf.org/shadow.html
>     <http://www.ietf.org/shadow.html>
>      >> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>     <ftp://ftp.ietf.org/ietf/1shadow-sites.txt>
>      >>
>      >
>     -- 
>     Gendispatch mailing list
>     Gendispatch@ietf.org <mailto:Gendispatch@ietf.org>
>     https://www.ietf.org/mailman/listinfo/gendispatch
>     <https://www.ietf.org/mailman/listinfo/gendispatch>
> 
>