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

Toerless Eckert <tte@cs.fau.de> Mon, 15 November 2021 02:53 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 6F3CC3A0D32; Sun, 14 Nov 2021 18:53:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 gp9O1gywQRlo; Sun, 14 Nov 2021 18:53:08 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09CC93A0D2A; Sun, 14 Nov 2021 18:53:06 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 381B6548019; Mon, 15 Nov 2021 03:53:01 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 2F0664E9DBB; Mon, 15 Nov 2021 03:53:01 +0100 (CET)
Date: Mon, 15 Nov 2021 03:53:01 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Jay Daley <jay@staff.ietf.org>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, draft-halpern-gendispatch-antitrust@ietf.org, gendispatch@ietf.org
Message-ID: <YZHLjSS9TrCJbIc6@faui48e.informatik.uni-erlangen.de>
References: <8b602637-b934-3713-3ce4-7da4e59ed69e@gmail.com> <c8cb28f5-f8b7-0471-ce07-7b33f724c2e6@joelhalpern.com> <745cb38e-5ca2-5f96-ebcd-c88517bb3b46@gmail.com> <c94229e2-a3d8-f25a-1a05-dc649949db34@joelhalpern.com> <bb584c94-0569-432e-e7c3-1439b4645eb7@gmail.com> <18f6b734-7227-4226-3e11-5cbd74ec229c@joelhalpern.com> <YZCWv/IL/gZY6dxu@faui48e.informatik.uni-erlangen.de> <69f0cd47-9b50-d4c7-5ffc-21abf1cce0ce@joelhalpern.com> <YZFR8UOAbsoM0XvP@faui48e.informatik.uni-erlangen.de> <66BFD20A-7854-4938-8EEC-072DB6E15760@staff.ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <66BFD20A-7854-4938-8EEC-072DB6E15760@staff.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/MeK4lRLqU0e1M_HPBiCQJajtSxg>
Subject: Re: [Gendispatch] 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: Mon, 15 Nov 2021 02:53:13 -0000

On Mon, Nov 15, 2021 at 12:42:11PM +1300, Jay Daley wrote:
> There’s a crucial point here that keeps getting missed - the *only* way that the IETF can be put into a tricky legal position is by the behaviour of participations and therefore the *only* ways that the IETF can 'defend' itself are by distancing/disowning the behaviour of participants, and/or by regulating the behaviour of participants.  If we assume for a moment that distancing/disowning is insufficient (noting that some feel it is sufficient) then we cannot separate out your a) and b) as you propose.

I was primarily thinking of "foreign country" lasws (aka: not USA and
not host-country), applicable only to participants even when overseas.

> I understand that you do not see the linkage between each behaviour the draft recommends avoiding and antitrust law, 

I don't think i said that.

> but do you really think you need to understand that or is it not sufficient that one or more lawyers agree that these are the behaviours to be avoided?

I do not need to understand these rules if our lawyers agree this is necessary
and sufficient to indemnify IETF from actions of its participants.

BUT: if we want to go beyond doing that and really help participant interpret
how each of their actions does or does not meet the description, then more
explicit examples/explanations would be helpful.

For example and as i asked in another mail: Do i stop being an IETF participant
for the purpose of indemnifying IETF when i go to dinner with other people who also happened
to be at the IETF ? 

>  In other words, do you need to be educated to the level of an antitrust lawyer by this draft?

See above: no.

>  Also, for the draft to explain this linkage it has to go into the very same level of detail that you argue against elsewhere.  

Hopefully not. And as i said, the explanations may not need to be formal or
in the same draft.

> Rather than looking at this draft from the 'input' side where we get into all the complexities of different laws in different regimes etc, it’s likely more productive to look at it from 'output' side, i.e. how does each of these recommendations affect participation in the IETF?

Of course. But to be sufficient for lawyers to be happy to protect the IETF,
the draft will still be quite "abstract", e.g. no definition of exactly
when i am or am not an IETF participant. I'd call this output explanation,
but input explanation.

Cheers
    Toerless
> 
> Jay
> 
> > 
> >> Yours,
> >> Joel
> >> 
> >> On 11/13/2021 11:55 PM, Toerless Eckert wrote:
> >>> On Sun, Nov 07, 2021 at 04:40:13PM -0500, Joel M. Halpern wrote:
> >>>> I agree with some of your proposals, and disagree with others.
> >>>> But I do not see any of the actual proposals as substantive enough to affect
> >>>> the dispatching concern.  They all seem things we can fairly discuss once
> >>>> dispatching has taken place.
> >>> 
> >>> Does that mean the authors will drop and forget input her from the list that
> >>> is not marked as "unless this issue is resolve, i will not recommend for this
> >>> document to be dispatched" ?
> >>> 
> >>> To repeat here on the list what i said during the WG meeting:
> >>> 
> >>> I do not recommend for this document to be dispatched until it is
> >>> clearer written down agreed to, what actually the goal is. And i see two potentially
> >>>  even conflicting possible goals:
> >>> 
> >>> a) To put into writing sufficient 'Cover My Behind' statements to protect
> >>> the IETF from legal action in case participants partake in anti-trust
> >>> behavior. This is not mentioned as a goal in the draft, but i have the
> >>> strong believ that this must have played a role on writing this document.
> >>> And i do support such a document, but it should explicitly state that
> >>> purpose.
> >>> 
> >>> b) A document that is really intended to help participants to understand
> >>> how to not get into anti-trust law issues. This is what the document claims
> >>> it wants to achieve, but quite frankly i do not even understand the most
> >>> basic connection between this goal and being an "IETF participant".
> >>> 
> >>> E.g.: what legal differences does it make for my compliance (or lack thereof) with
> >>> anti-trust laws if my actions are performed at the IETF or at any other
> >>> place ? Lets say when i am getting together "privately for dinner" at an evening
> >>> of an IETF week with a bunch of folks i know who happen to also attend the
> >>> IETF, and discuss exactly the same stuff there ? Unless there are really
> >>> strange laws (which i would be curious to learn about), i'd say the only
> >>> difference is (a), aka.: possible implication of the IETF into legal
> >>> actions caused by its participants ("sponsoring anti-trust behavior").
> >>> 
> >>> I also think that for (a), we do not necessary need to add more explanatory
> >>> text (however unfortunate i would think that is), but if the goal is (b),
> >>> and someone like me is supposed to understand the guidance, then i'd certainly
> >>> be asking for more explanatory text to be put into the document.
> >>> 
> >>> So, i really can't see how we can dispatch a document without being clearer
> >>> about this goal. And if it is just me being confused here, great, please
> >>> unconfuse me.
> >>> 
> >>> Cheers
> >>>     Toerless
> >>> 
> > 
> > -- 
> > ---
> > tte@cs.fau.de <mailto:tte@cs.fau.de>
> -- 
> Jay Daley
> IETF Executive Director
> exec-director@ietf.org
> 

-- 
---
tte@cs.fau.de