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

Toerless Eckert <tte@cs.fau.de> Sun, 14 November 2021 04:55 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 1B2383A085B; Sat, 13 Nov 2021 20:55:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level:
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] 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 q4skklUtp7lr; Sat, 13 Nov 2021 20:55:42 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff: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 7FE1B3A0857; Sat, 13 Nov 2021 20:55:36 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 21A63548019; Sun, 14 Nov 2021 05:55:27 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 07FEC4E9DA5; Sun, 14 Nov 2021 05:55:27 +0100 (CET)
Date: Sun, 14 Nov 2021 05:55:27 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, draft-halpern-gendispatch-antitrust@ietf.org
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, gendispatch@ietf.org
Message-ID: <YZCWv/IL/gZY6dxu@faui48e.informatik.uni-erlangen.de>
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> <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <18f6b734-7227-4226-3e11-5cbd74ec229c@joelhalpern.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/cxACG9MfOYrvvH0PMQby1KErL4k>
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, 14 Nov 2021 04:55:45 -0000

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