Re: [antitrust-policy] feedback on draft 06
Kristin Berdan <kberdan@cloudflare.com> Fri, 04 August 2023 15:14 UTC
Return-Path: <kberdan@cloudflare.com>
X-Original-To: antitrust-policy@ietfa.amsl.com
Delivered-To: antitrust-policy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65DABC15107A for <antitrust-policy@ietfa.amsl.com>; Fri, 4 Aug 2023 08:14:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BJUk6YEgI4oL for <antitrust-policy@ietfa.amsl.com>; Fri, 4 Aug 2023 08:14:09 -0700 (PDT)
Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) (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 ietfa.amsl.com (Postfix) with ESMTPS id D6502C15108A for <antitrust-policy@ietf.org>; Fri, 4 Aug 2023 08:14:08 -0700 (PDT)
Received: by mail-lf1-x12d.google.com with SMTP id 2adb3069b0e04-4fe48a2801bso3849919e87.1 for <antitrust-policy@ietf.org>; Fri, 04 Aug 2023 08:14:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; t=1691162047; x=1691766847; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=5EIupAzSFMz3E6mwSX6T9aj1dzQ0UzThYSecM5UItRc=; b=IIOkgKf2pUhCrdnUf7amxHp7v010sHALuMI4DXeUEzgXg6W2knAfqhKTLD32ClMvxh 4POglWvFlr2KREAbWJ3RbTgx6iBhjyF3Fmgm4MvgVYwxxzT1Z+LtEQXK1hlUZI/MnFyv npQ3nefWf2JAm5zPB4Ih1/WMnYXlTlTjoZC7o=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691162047; x=1691766847; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=5EIupAzSFMz3E6mwSX6T9aj1dzQ0UzThYSecM5UItRc=; b=jHTbb+2AnZDhbIY7uNBxyy07Ad4PpnD5Nxi9vNNoJ6FglWwpDS0BjlE2p84coIg0hW yzub1JtWseQsr9C3g0m41jqPY6bfbV5V76hyWvmt83euxvuZQA4M22CFR0/ieRIK47nr 0/keDoLTwUhK6vssypwvYZ+fH0CTzdERgEysi+coOZluhkZkT/LGVr087/2Nmwde098e e5eWvu0KPaCuPiQowOkPF1aIsakR1b6JEgUUjuhy808h/uMK5t1ujz5mnsHJAVNJtEf7 NKQ18KGY506zYOHD8c1X1W/fAhVDr3O4fYiY9Ob6fRHM2B2gLfR3VJqTerid8CRRQhyL qqmQ==
X-Gm-Message-State: AOJu0YyWXOsJ6LvaC7SyeWcKL7poz7TfCiIy9LkorGqpWt80XAqIKlJ0 Yecb+L3UEn6SNNy2o4t5JphOGqR7UM3lRY9+l1yHTk/8H9jqb/GW
X-Google-Smtp-Source: AGHT+IFyNGxWeihU71fUHkvixq31gZZz3exIuL33aH7pI+SuhyIkB8X7K+CTLLk8zSjZUl4WPzxhd0nWwQD7JVY1Baw=
X-Received: by 2002:a05:6512:ad5:b0:4fb:8585:eefe with SMTP id n21-20020a0565120ad500b004fb8585eefemr1738382lfu.57.1691162046489; Fri, 04 Aug 2023 08:14:06 -0700 (PDT)
MIME-Version: 1.0
References: <CAFdPJzXsFDrsM4LMqYjZmgT9L37Az6yue_=Y+p174poan7dFLQ@mail.gmail.com> <C82397F0-403A-4A92-85F7-C27F454DFB24@ietf.org>
In-Reply-To: <C82397F0-403A-4A92-85F7-C27F454DFB24@ietf.org>
From: Kristin Berdan <kberdan@cloudflare.com>
Date: Fri, 04 Aug 2023 08:13:55 -0700
Message-ID: <CAFdPJzX0hPCLwW9Zx-p_7ZO2fqzDvfkzeSCtZHfH4MaCfW+DmA@mail.gmail.com>
To: Jay Daley <exec-director@ietf.org>
Cc: antitrust-policy@ietf.org
Content-Type: multipart/alternative; boundary="0000000000000a6d1806021a599f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/antitrust-policy/AcH5ssOdKwXclzRf65OYNZ8cALM>
Subject: Re: [antitrust-policy] feedback on draft 06
X-BeenThere: antitrust-policy@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Discuss the need for an antitrust or competition policy for the IETF." <antitrust-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/antitrust-policy>, <mailto:antitrust-policy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/antitrust-policy/>
List-Post: <mailto:antitrust-policy@ietf.org>
List-Help: <mailto:antitrust-policy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/antitrust-policy>, <mailto:antitrust-policy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Aug 2023 15:14:13 -0000
Thanks for the responses, Jay and Joel. Apologies for not understanding the motivation for this document -- I did the best I could to glean it from the mailing list archives. It would be very helpful for me and probably other readers to know then, what is the motivation for and goal of this document? On Fri, Aug 4, 2023 at 3:35 AM Jay Daley <exec-director@ietf.org> wrote: > Hi Kristin > > Thanks for the feedback and welcome to the IETF. To add to what Joel has > said, I have some further comments below, which are all subject to > discussion with my fellow authors and possible commentary from other > participants: > > > On 3 Aug 2023, at 23:05, Kristin Berdan <kberdan= > 40cloudflare.com@dmarc.ietf.org> wrote: > > > > Hello all, > > I'm new to the IETF so please excuse any errors or ignorance. I've > reviewed the mailing list discussion on the antitrust guidelines and I'd > like to offer this feedback on the current draft (06): > > Section 1: As I understand it, the consensus of a 2012 antitrust policy > BOF, later bolstered by legal advice, was that educational materials > regarding competition law should be made available to the IETF community. > And this document is intended to serve as that educational material. If > this is all correct, then it would be useful to mention this context in the > Introduction. It could be as simple as, "The consensus of a 2012 antitrust > policy BOF, later bolstered by legal advice, was that educational materials > regarding competition law should be made available to the IETF community. > These guidelines are intended to be responsive to that consensus." > Otherwise, these guidelines seem unmoored to any historical context. > Related to this, see my suggested edit to Section 8. > > The origins of this i-D are not that BoF, though this I-D has to conform > to the outcome of that BoF. Even if it were, then RFCs of this nature > would not normally document their provenance - that’s better left to > Datatracker given the many possible routes and many possible twists and > turns a document can take. > > > Section 2.3, second bullet: To correct awkward phrasing, I suggest > re-arranging slightly: "Additionally, to avoid reputational harm to the > IETF, the IETF cannot be a forum where participants engage in problematic > antitrust behavior, even if direct liability for that behavior falls on > those participants and not the IETF." > > That does seem clearer. > > > Section 3: The first sentence seems somewhat tautological -- > effectively, it's just saying "IETF designs its policies and procedures to > mitigate antitrust risk, so following those policies and procedures > mitigates antitrust risk." How about stating something like the following, > adapted from the IETF Administration LLC Statement on Competition Law > Issues: "IETF processes and procedures, with their focus on free and open > participation and transparent conduct of IETF activities, are particularly > well-suited to mitigate competition law risks. In particular, participants > are required to comply with the following policies:" > > That also seems clearer. > > > Section 4.1: The list of "topics to avoid" makes me uneasy simply > because context is everything when it comes to analyzing antitrust risk, > and there is nothing inherently problematic (never mind illegal) about > discussing those topics outside of the collaborative IETF process. In > particular, the IETF would probably not want to be seen as a forum where > discussion of employee compensation or workplace conditions was discouraged > (this is an area that has seen a lot of attention recently in the U.S. tech > industry). I wonder if there is some way we could emphasize a bit more the > importance of that context, and the responsibility of participants to use > their best judgement in navigating that context. Perhaps something along > these lines? "While not all discussions of these topics would necessarily > be antitrust violations, and recognizing that analysis of antitrust > considerations will be different for differently-positioned participants, > prudence suggests that participants use judgement and discretion if they > discuss these topics, and participants may find that avoiding these > specific topics in the context of the collaborative IETF process best > mitigates antitrust risks for themselves and for the IETF." > > It took me a while to pin down the exact text you are proposing is > changed, which I believe is the insertion below: > > "prudence suggests that … participants use judgement and discretion if > they discuss these topics, and participants may find that … avoiding these > specific topics" > > To me that seems sensible but there may be problems with that I haven’t > considered. > > > Section 4.2: The use of the phrase "informal advice" is problematic > here, at least when it comes to counsel. Suggested edit: "IETF participants > who would like more information on these issues have a number of options > open to them, including speaking to relevant Area Directors or raising the > matter with the community on a mailing list. If a participant desires legal > advice on this topic, the proper path is to consult their own legal > counsel." > > That one I will leave to all of the lawyers to comment on. > > > Section 4.4: I'm not sure what the convention is, but either here or in > the references section I'd suggest including a link to the whistleblower > process referred to in this section (which I assume is this one). > > The link is intentionally omitted because the link is tied to the exact > process the LLC uses, which is inherently ephemeral as is even the web page > that describes it, and as RFPs are meant to be immutable then that pretty > much guarantees an incorrect RFC in a couple of years. It’s easy enough > for someone to do a search to find the whistleblowing process so that > absence of a link is only a minor barrier and one that we could reasonable > expect someone to overcome if they need to do something as important as > whistleblow. > > > Section 8: I'd suggest adding to the list of informative references the > IETF Administration LLC Statement on Competition Law Issues since (as I > understand it) that was the motivation for the preparation of this document. > > Yes that could be useful. > > thanks again > Jay > > > Kristin > > _______________________________________________ > > antitrust-policy mailing list > > antitrust-policy@ietf.org > > https://www.ietf.org/mailman/listinfo/antitrust-policy > > -- > Jay Daley > IETF Executive Director > exec-director@ietf.org > >
- [antitrust-policy] feedback on draft 06 Kristin Berdan
- Re: [antitrust-policy] feedback on draft 06 Joel Halpern
- Re: [antitrust-policy] feedback on draft 06 Jay Daley
- Re: [antitrust-policy] feedback on draft 06 Kristin Berdan
- Re: [antitrust-policy] feedback on draft 06 Jay Daley
- Re: [antitrust-policy] feedback on draft 06 Kristin Berdan
- Re: [antitrust-policy] feedback on draft 06 Joel Halpern
- Re: [antitrust-policy] feedback on draft 06 Kristin Berdan
- Re: [antitrust-policy] feedback on draft 06 Alissa Cooper
- Re: [antitrust-policy] feedback on draft 06 Jay Daley
- Re: [antitrust-policy] feedback on draft 06 Jay Daley