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

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 07 November 2021 03:48 UTC

Return-Path: <brian.e.carpenter@gmail.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 85E413A0E99 for <gendispatch@ietfa.amsl.com>; Sat, 6 Nov 2021 20:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.428
X-Spam-Level:
X-Spam-Status: No, score=-5.428 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, NICE_REPLY_A=-3.33, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BhswG000CFTG for <gendispatch@ietfa.amsl.com>; Sat, 6 Nov 2021 20:48:42 -0700 (PDT)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A265B3A0E9E for <gendispatch@ietf.org>; Sat, 6 Nov 2021 20:48:42 -0700 (PDT)
Received: by mail-pf1-x436.google.com with SMTP id x131so7543479pfc.12 for <gendispatch@ietf.org>; Sat, 06 Nov 2021 20:48:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=1FEwSzaPwVxEcG5QQf0iNOWFPDF2cBJiD8HfV4pysR8=; b=UI2D8JF1+S5TRzO9AwLtts8AQhB5qrw08SR8VcbfBg0qDNopVu8qzAFgaDduHy7lFE bEta0p//hVzk0d0RYX16gcfWmFZqFTSblqAOpSYhiNieq4OU15IagrFpGWOf+OXjmV4u beqfjUY0VTBuVzctldCUSc/ESboFo0GbnyDQ4+ZGtZqB5HHnoE2ynPZLisNb0BK3bjQT vuKt2tF+5yy1HKCWeOiePggsYX3snUeKjoGVOJMINgoikbBFw5bQie87F29Nuj9bJYn6 ouRo5C1H40LrvIUS3fvmghnC4Xv62qxmVRtqI+qHwSIHeU9VCbBb+XWhgPySE9RXwRmC AK1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=1FEwSzaPwVxEcG5QQf0iNOWFPDF2cBJiD8HfV4pysR8=; b=kIAHr4bZpDJlidH0NDCKy19RxPpHsGAOLrpGO/sbxo2RBlTtjFm590fQH1FSwSUi7n f2nXUpYY+LYLiRkHVvU0ZuCohGdsAjoZh8eKoiGhxS5K7L94ZXzMQr4IwBSJW0rMp/9x mPigggFZYfzYSl/UdRXFuj6CbCdAdPxZjjWKzTigG/f4Jx8oqwxPVBELNVODtHFnX6AC HQ4Tyo2NEqcJmz+kbGcOSkgkJ8WJGprDQeCc/0PNnmG4FpiUMGyF9dEo7rMXpSuFE9GY h5LGiREZiOWrjNc8mpv0OMaJjZe6nWZG3sv99Ma3agdLpM7oJZm+pNf/y5KdJ9evtIV8 B20Q==
X-Gm-Message-State: AOAM533pGiMDUEo+9a4RqzxoPxt8judzkct41tiQrS1nxbWom2eUBfJp rwzfS+t3srrUQNzzDHOdaRsrKolUvO0QBg==
X-Google-Smtp-Source: ABdhPJw9NS8payhBy0iEldlYWzkigoEqpPH8vP5+na9AO3Ql7M/SS2T0WP4fLVo1IlRyRamKGAyzHw==
X-Received: by 2002:a05:6a00:2181:b0:44c:f4bc:2f74 with SMTP id h1-20020a056a00218100b0044cf4bc2f74mr70268209pfi.68.1636256920916; Sat, 06 Nov 2021 20:48:40 -0700 (PDT)
Received: from ?IPv6:2406:e003:102d:e801:80b2:5c79:2266:e431? ([2406:e003:102d:e801:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id 8sm12717719pjt.46.2021.11.06.20.48.39 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 06 Nov 2021 20:48:40 -0700 (PDT)
To: "Joel M. Halpern" <jmh@joelhalpern.com>, gendispatch@ietf.org
References: <163595251682.11706.5053299985084837548@ietfa.amsl.com> <8854c3cc-694b-1a7f-ebc8-47bed9bb4e0f@joelhalpern.com> <CABcZeBOk7Y6vWeQ2gJ6Z1Z-FCpAdU4+awtcL=zEKrqyvtjDh5g@mail.gmail.com> <0be3bb7d-7387-22c4-844c-1e0fb707b0de@joelhalpern.com> <8b602637-b934-3713-3ce4-7da4e59ed69e@gmail.com> <c8cb28f5-f8b7-0471-ce07-7b33f724c2e6@joelhalpern.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <745cb38e-5ca2-5f96-ebcd-c88517bb3b46@gmail.com>
Date: Sun, 07 Nov 2021 16:48:36 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <c8cb28f5-f8b7-0471-ce07-7b33f724c2e6@joelhalpern.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/ESYQ_i6va4uxdii87FEibMhqZfw>
Subject: Re: [Gendispatch] Fwd: I-D Action: draft-halpern-gendispatch-antitrust-01.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: Sun, 07 Nov 2021 03:48:48 -0000

On 07-Nov-21 15:19, Joel M. Halpern wrote:
> Brian, the fact that we say people participate as individuals does not
> suddenly make them no longer employees of their company.  And if they
> act in ways that are anti-competitive on behalf of those employers, 

That is why our rules say what they say. The draft IMHO confuses the issue.
It talks about how participants might infringe competition law *if* they
break the IETF rules by not acting as individual contributors.

Introduction, sentence 1, says "Standards development frequently requires
collaboration between competitors." That's simply not what the IETF does.
It would apply to SDOs that are membership organisations whose members
are competing companies. On reflection, the whole document is written from
the wrong premise.

Section 5 starts "As the IETF is a standards development environment where
representatives from competitors are highly likely to be present..."
Wrong. By definition, there are *no* representatatives present.

[I believe the original legal advice came at least partly from Geoff Stewart,
and the IBM corporate standards people, who knew a lot about antitrust
because of the big antitrust suits against IBM, were also giving advice
in those days.]

I think the whole draft needs a rewrite on the basis that anyone who
acts for their employer in an IETF forum is in breach of the IETF's rules.
That should be the starting point, not the two sentences quoted above.

I do agree that WG Chairs and ADs should be advised to shut down any such
behaviour. And a description of what might be incorrect behaviour is
useful. But the original sin here is acting as a company rep, in direct
violation of RFC 2026 and its predecessors.

Regards
     Brian

> it
> can place the IETF as a whole, and other participants in the IETF, at
> risk.  particularly if they are from a company that is considered to
> have a dominant position in the market.
> 
> So I am looking for the IETF to give participants advice to help avoid
> these risks.  I do not know who wrote the advice 30 years ago, or what
> assumptions they made.


> I know that about 15 years ago our lawyer
> thought it would be helpful to clarify these things, but we chose not to.
> 
> Put differently, if we thought there was no effect from employers on
> people's actions here, we would not have the rules that each company may
> have no more than 2 members on the nomcom.  or the expectation that when
> there is more than one chair of a working group they will be from
> different companies.  or that we expect that ADs in a given area will
> come from different companies.  Or that the nomcom almost never appoints
> more than two ADs to the IESG from the same company.   We do understand
> that affiliation affects thing.
> 
> Yours,
> Joel
> 
> On 11/6/2021 9:53 PM, Brian E Carpenter wrote:
>> Joel,
>> On 07-Nov-21 14:30, Joel M. Halpern wrote:
>>> Finding the right balance on the wording of this issue is something I
>>> expect the discussion once dispatched will need to do.
>>>
>>>    From what the lawyers tell me, I believe this kind of discussion does
>>> head towards incurring significant risks.  So having guidelines that
>>> help us stay on the right side of that seems desirable to me.
>>
>> Help us understand. Since the IETF's motto is rough consensus and
>> running code, and our participants are individuals not company
>> representatives (and who therefore simply *cannot* make agreements about
>> companyy products), how can discussing and agreeing to implement certain
>> features and test interoperability *before* reaching rough consensus
>> conceivably breach competition law?
>>
>> That the IETF is not a venue for companies to make agreements with each
>> other has been established, if not since 1986, then certainly since 1992
>> (RFC1310): "Participation is by individual technical contributors,
>> rather than formal representatives of organizations."
>>
>> I do not understand why the legal advice given in 1992, 102 years after
>> the USA's Sherman Act, needs revisiting.
>>
>> The same goes for the other new doctrine that I queried in
>> https://mailarchive.ietf.org/arch/msg/gendispatch/VTxH4Rx_NJPgBeY9FHphdYJZYAw/
>> .
>>
>> I'm having second thoughts about whether this should be dispatched at
>> all. Since the formalisation of the standards process almost 30 years
>> ago was done with clear awareness of US and EU competition law, I'm far
>> from convinced that it's the IETF's job to give people advice in this
>> area. Participants who are employees should get such advice from their
>> employers. We certainly shouldn't be publishing advice that has a
>> chilling effect on rough consensus and running code.
>>
>>      Brian
>>
>>>
>>> Yours,
>>> Joel
>>>
>>> On 11/6/2021 9:07 PM, Eric Rescorla wrote:
>>>>
>>>> Hi Joel,
>>>>
>>>> This paragraph stood out to me in this document.
>>>>
>>>>       There should be no agreement among participants 
to implement or to
>>>>       adhere to IETF standards, or any discussions as 
to when
>> participants
>>>>       will begin to offer products conforming to IETF 
standards.
>>>>
>>>> In groups I am in, WG participants pretty routinely discuss shipping
>>>> timelines and often try to coordinate changes so that they happen
>>>> at similar times (e.g., disabling SHA-1, rolling out new code that
>>>> can interop).
>>>>
>>>> -Ekr
>>>>
>>>> On Wed, Nov 3, 2021 at 8:37 AM Joel M. Halpern <jmh@joelhalpern.com
>>>> <mailto:jmh@joelhalpern.com>> wrote:
>>>>
>>>>       This is a significant revision of the draft on IETF antitrust
>>>>       guidelines.  We tried to address what 
we heard in the previous
>>>>       feedback,
>>>>       and tightened the language related to legal issues.
>>>>
>>>>       Chairs, if it is possible I would like to present this for
>>>> dispatching
>>>>       at the upcoming session.
>>>>
>>>>       Thank you,
>>>>       Joel
>>>>
>>>>
>>>>       -------- Forwarded Message --------
>>>>       Subject: I-D Action: draft-halpern-gendispatch-antitrust-01.txt
>>>>       Date: Wed, 03 Nov 2021 08:15:16 -0700
>>>>       From: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
>>>>       Reply-To: internet-drafts@ietf.org
>>>> <mailto:internet-drafts@ietf.org>
>>>>       To: i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>
>>>>
>>>>
>>>>       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-01.txt
>>>>                Pages           : 8
>>>>                Date
>>     : 2021-11-03
>>>>
>>>>       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-01.html
>>>>
>>>>       
>>>> <https://www.ietf.org/archive/id/draft-halpern-gendispatch-antitrust-01.html>
>>>>
>>>>
>>>>       A diff from the previous version is available at:
>>>>       
>>>> https://www.ietf.org/rfcdiff?url2=draft-halpern-gendispatch-antitrust-01
>>>>       
>>>> <https://www.ietf.org/rfcdiff?url2=draft-halpern-gendispatch-antitrust-01>
>>>>
>>>>
>>>>
>>>>       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>
>>>>
>>>
>>