Re: [Gendispatch] I-D Action: draft-halpern-gendispatch-antitrust-00.txt
"Joel M. Halpern" <jmh@joelhalpern.com> Sun, 05 September 2021 05:16 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 EC5A13A105A for <gendispatch@ietfa.amsl.com>; Sat, 4 Sep 2021 22:16:25 -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 YKx6qvELd8ZX for <gendispatch@ietfa.amsl.com>; Sat, 4 Sep 2021 22:16:20 -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 928713A1058 for <gendispatch@ietf.org>; Sat, 4 Sep 2021 22:16:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4H2KWS1nN8z1nwFt; Sat, 4 Sep 2021 22:16:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1630818980; bh=X/jvxQS58xwE4aVMpnkSpMpDKPk39rf21ld2lGKEas8=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=XUdaPaC0IcYK7xSWBYjUAXaByP91F8wwbgo/fpQqEEdGP7iqr2PCFeJK4Ex20c0Jc diY/8Sb/BXnXU+SsVjtjnj0GHY+rjMC0Os9B780Ad8ZgyiEMY9zcXyDF0OgLGWRd1D /jphu3+ODXFE0GTD3xLuikKZSPPUaS4LpawLmdac=
X-Quarantine-ID: <tkNuDrmUC4pM>
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 4H2KWR5CmXz1nwBJ; Sat, 4 Sep 2021 22:16:19 -0700 (PDT)
To: Rob Sayre <sayrer@gmail.com>
Cc: GENDISPATCH List <gendispatch@ietf.org>
References: <163037412640.15437.266878243771416247@ietfa.amsl.com> <7a43a750-f6e6-096d-8f89-a1c5a4fd2cb9@cs.tcd.ie> <ea3ed95f-8d23-6b2a-2bb5-12c7b1b50c33@joelhalpern.com> <CAChr6Sysc7bnah1t0w2EuMEwvO0Y2V8zVdsupNi9r8v2EQ=csQ@mail.gmail.com> <5da63a02-bbc2-98a9-5a19-745179744192@joelhalpern.com> <CAChr6SwjazBjSj6XzmCDO0pnsibxohU=40TkJ0GnAJ+_t5zSHw@mail.gmail.com> <05211e39-419d-2455-ffa3-1a55fab22a48@joelhalpern.com> <CANMZLAaiPjeO7wMrfjjd5-XJpzYm3iUTExdUqD+JBm9mCYgvNg@mail.gmail.com> <CAChr6SztfuauB1vTLpu6L-AeaShRfZ-Ybs_d+2p8oaMBBvKjyQ@mail.gmail.com> <f706ce7f-2967-50ad-eaf0-e9b168b5a6e8@gmail.com> <CAChr6Sw+KVW_Jq5LZFN_KJ9ygxb9=sFoRNs2yAPeiPLV3A1Y=w@mail.gmail.com> <9b819b2d-4de2-800d-190c-4c7cbfc2465e@gmail.com> <CAChr6Sy_F6yg2UGC_LSBvpMQr25bwH=CUq9jh78_h13iyyh9yg@mail.gmail.com> <7da21d8a-bdc1-6974-c485-9ed1b2e4910a@joelhalpern.com> <CAChr6SxzYCC=eYySGuAeHY6=pXcAR+sBvAR7iuqTqcDwitb4LA@mail.gmail.com> <CAChr6Sy3=xWWejpPrmMRSgE18CNVs29NtxzJfv_nm55oXq215g@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <a508dcfb-26f6-89f2-4ef3-a7befe9db95a@joelhalpern.com>
Date: Sun, 05 Sep 2021 01:16:17 -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: <CAChr6Sy3=xWWejpPrmMRSgE18CNVs29NtxzJfv_nm55oXq215g@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/hCn98p4Hpq26qmAN78HUhCV-7r0>
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: Sun, 05 Sep 2021 05:16:26 -0000
As far as I can tell Rob, you are asking to remove words that have value. I do not understand any of your requests for removal. Yours, Joel On 9/5/2021 12:50 AM, Rob Sayre wrote: > Another suggestion from the list: > "As the old joke goes, if this were legal advice you would know because > it would have a bill attached." > > It's a good point. So, by that rationale, it seems safe to strike "This > document does not contain legal advice". > > thanks, > Rob > > > On Sat, Sep 4, 2021 at 5:44 PM Rob Sayre <sayrer@gmail.com > <mailto:sayrer@gmail.com>> wrote: > > OK in the interest of moving forward productively, although I > sincerely doubt any IETF participant needs to read up: > > > 5. Recommended Behavior > > Instead: > 5. Topics That Concern Competition > > > 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: > > Instead: > As the IETF is a standards development environment where > representatives from competitors are highly likely to be present, > participants should be aware that the following topics may raise > antitrust concerns.... [list] > > > While not all discussions of these topics would necessarily be > > antitrust violations, prudence suggests that avoiding these topics > > altogether best mitigates antitrust risks. > > [delete] > > thanks, > Rob > > > On Sat, Sep 4, 2021 at 5:01 PM Joel M. Halpern <jmh@joelhalpern.com > <mailto:jmh@joelhalpern.com>> wrote: > > I do not recall that BoF. I presume it occurred. I even > presume I was > there. > > However, after nine years it is not unreasonable to take another > look. > And when I looked, it seemed to me that getting something > explicit in > the Note Well would be good for IETF participants, the IETF as a > whole, > and even for the companies which send people to the IETF. > > Yours, > Joel > > On 9/4/2021 7:47 PM, Rob Sayre wrote: > > On Sat, Sep 4, 2021 at 4:27 PM Brian E Carpenter > > <brian.e.carpenter@gmail.com > <mailto:brian.e.carpenter@gmail.com> > <mailto:brian.e.carpenter@gmail.com > <mailto:brian.e.carpenter@gmail.com>>> wrote: > > > > > I thought the proposed BCP seemed destined for this page: > > > https://www.ietf.org/about/note-well/ > <https://www.ietf.org/about/note-well/> > > <https://www.ietf.org/about/note-well/ > <https://www.ietf.org/about/note-well/>> > > <https://www.ietf.org/about/note-well/ > <https://www.ietf.org/about/note-well/> > > <https://www.ietf.org/about/note-well/ > <https://www.ietf.org/about/note-well/>>> > > > > Not necessarily. The lawyers can tell us, but it seems to > me that the > > warnings on the Note Well are there to protect the IETF > itself, whereas > > this document is more aimed at warning participants to > protect > > themselves. > > > > > > Well, you just wrote "Or maybe we should just wait until > somebody gets > > sued and blames the IETF for not warning them." > > > > That seemed to indicate you think the document is meant to > protect the > > IETF. Maybe I misunderstood. > > > > If so, it doesn't necessarily need to be a BCP. If indeed > it's > > considered > > necessary to protect the IETF itself, the whole > discussion changes tone. > > > > > > Agree. > > > > By the way, I recommend reading Jorge Contreras's slides > cited in > > the LLC's > > statement. > > > > > > I did, and it was not the first time. Several slides seem to be > > truncated (maybe just some software incompatibility creeping in). > > > > For example, Slide 4 ends with "Excluding > technology/participants for" ...? > > > > thanks, > > Rob > > > >
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brian E Carpenter
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Stephen Farrell
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brian E Carpenter
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brian E Carpenter
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Joel M. Halpern
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Christian Huitema
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Stephen Farrell
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Mark Nottingham
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brian E Carpenter
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Joel M. Halpern
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Joel M. Halpern
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Joel M. Halpern
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brian Carpenter
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Salz, Rich
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brian E Carpenter
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brian E Carpenter
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Joel M. Halpern
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… John Levine
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Joel M. Halpern
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Joel M. Halpern
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Andrew Campling
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brian E Carpenter
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… John Levine
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brian E Carpenter
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Bob Hinden
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… lloyd.wood@yahoo.co.uk
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Joel Halpern Direct
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brian E Carpenter
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Mark Nottingham
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… John Levine
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Jay Daley
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Mark Nottingham
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Stephen Farrell
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Jay Daley
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Mark Nottingham
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Pete Resnick
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Christian Huitema
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Vittorio Bertola
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… S Moonesamy
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… S Moonesamy
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Eliot Lear
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Pete Resnick
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Eliot Lear
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brian E Carpenter
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brian E Carpenter
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brian E Carpenter
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Joel M. Halpern
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Livingood, Jason
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… S Moonesamy
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Livingood, Jason
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Eliot Lear