From nobody Sun Apr 2 18:59:18 2023 Return-Path: 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 520C6C151719 for ; Sun, 2 Apr 2023 18:59:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.098 X-Spam-Level: X-Spam-Status: No, score=-7.098 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b="L5m4uq+g"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="H2JaI8RL" 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 UxqN8m9cMa6l for ; Sun, 2 Apr 2023 18:59:12 -0700 (PDT) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 A8200C1516EA for ; Sun, 2 Apr 2023 18:59:12 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id AA9675C018E for ; Sun, 2 Apr 2023 21:59:11 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Sun, 02 Apr 2023 21:59:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to; s=fm3; t=1680487151; x=1680573551; bh=fz blsp4aEGIBIG6DUkkhbVvY4V5aAYS7l6WWfQ1pcc4=; b=L5m4uq+gtmOs7hUh69 L+D5NVQiPtP4niZ1edfHUAqnEp7pHtaw1EiJQq4C5Mi7S+DcT8EHH5K/REa+3htz 8f5NMVtdnGX4UyGf5PXP2mEV4mNQkFxxqJdIpS5ZG4XWTYmG4vKbvNHxh6gHjbKe xz0E7ADZDXRUQ18ZbY6kfL/ATiV9BmpZvFwMAhP8XaftppXktaAjqFMzsk0PgkO3 Wb6QK0gCHKiwD2sbD7rHJ8bCKdtGH71tr6hAWsAO0rJA5meLhlY2KscGbn08l6Ki 3MgXk/9IMFAIfw7PFROLCmJVrFcggYTF+e5Qdg2nN4WBOIoZH7nhGp4rCClTaJES MtFw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:message-id:mime-version:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1680487151; x=1680573551; bh=fzblsp4aEGIBI G6DUkkhbVvY4V5aAYS7l6WWfQ1pcc4=; b=H2JaI8RLIJNmUkOZ45G/29oqmGNV6 jTPmq+adFtwBZLJ8GOJlaPZw3k8d6OUxeuEay6UBc0HLmg+kkJgEtRYV5pjr0YBX /XlO6rXy4FXSiPyqLbpHsZGnoUSkUqtceRhFFf/PhNq+vQ3mOE0BWpFQdKm87LPU DKtehAfgbPcX4YHDatPn2T6H+B5nU/+Y/vUlzyijoy7omAR+cBh5XXIWQXEd5UIN 7QGOp6EIMnNy61tRXe6YzbFmJWBAZmgKQKMG2HA0vfk+Z2WChOzPrbMNNsO1s96A 0yvnRVV01afwoMWt7AfWthVhtVGnqwdbxaHkFN1xxm9LrYB2kK3+2DxMw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdeiiedgheefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhtgfgggfukfffvffosehtqhhmtd hhtdejnecuhfhrohhmpeforghrkhcupfhothhtihhnghhhrghmuceomhhnohhtsehmnhho thdrnhgvtheqnecuggftrfgrthhtvghrnheptdevteeujedufedtgeeggfehlefhtdelud etieekvedtledutdfhffekkeetvedtnecuffhomhgrihhnpehmnhhothdrnhgvthenucev lhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmh hnohhtrdhnvght X-ME-Proxy: Feedback-ID: ie6694242:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sun, 2 Apr 2023 21:59:10 -0400 (EDT) From: Mark Nottingham Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\)) Message-Id: Date: Mon, 3 Apr 2023 10:58:47 +0900 To: antitrust-policy@ietf.org X-Mailer: Apple Mail (2.3731.400.51.1.1) Archived-At: Subject: [antitrust-policy] Further feedback on draft-halpern-gendispatch-antitrust 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2023 01:59:17 -0000 Reading -05, a few more issues are apparent. Please CC me on responses, = as I'm not subscribed to the list. 1. Introduction > This document is intended to educate IETF participants about how to = reduce antitrust risks in connection with IETF activities. "educate... how to reduce antitrust risks" could be read as "advice", or = even "legal advice." And, as others have noted, it really isn't = educational material. I suggest: > This document is intended to briefly introduce IETF participants to = some of the antitrust issues that are connected with IETF activities. It = is not legal advice, and is not complete; those with concerns about = antitrust issues should obtain legal advice. 2.2 Purpose of Antitrust or Competition Law The purpose of competition law is, to put it mildly, contested. We = shouldn't unintentionally take a position; this section should be = removed. 2.3. Overlapping Areas of Concern Given the positioning of this document, 'must not' (x2) is not = appropriate here, even in lowercase. 4.2 Topics Requiring Caution > =E2=80=A2 Seeking clarifications about IPR disclosures, in a = context when any such clarifications could be reasonably perceived as = entering into group negotiations of IPR terms. This text's use of 'group negotiations', while appropriate in the = context of competition law, can be read as 'open or public negotiations' = in an IETF context. Because normal IPR discussions in the IETF are about = non-discriminatory licensing, which poses no competitive risk by its = nature, I suggest that something like this would be much more helpful to = participants: > =E2=80=A2 Discussion or Negotiation of IPR licensing terms that are = (or could be perceived as) discriminating for or against a particular = group. 4.2 Topics Requiring Caution Some activity at IETF116 made me think that we need to say more about = abuse of dominance as it relates to our decision-making procedures.=20 For example, if someone employed by an implementer that has overwhelming = market share gets up to the mic and states that their implementation = will not support a proposal under any condition, that could be perceived = as an abuse of dominance by a regulator or judge. If the Working Group were to assign undue weight to such statements, or = even the perception of a dominant undertaking's preferences, that could = be seen as facilitating such abuse. Of course, our consensus procedures are a defence against this. However, = Chairs and participants are also pragmatic -- if a party that controls = 80% of the market (for example) doesn't want to do something, it's = probably not going to fly. That *doesn't* mean that the WG should always = give in, however; sometimes, you publish a document and see if it gets = deployment when helped by other forces (e.g., customer demand). So, we need a reminder; something like this under 4.2: > =E2=80=A2 Statements that could be perceived as unduly using market = share to influence consensus outcomes, when made by participants who are = associated with companies that might be considered as dominant in a = relevant market. 4.4. Escalate Antitrust-Related Concerns The title of this section implies that the legal counsel will 'do = something' regarding the concern raised, and therefore takes = responsibility. That likely isn't the case; counsel will assess whether = there are any legal implications *for the IETF*, but not for the person = who raised it. Absent regulator or court action, it's unlikely we'll = actually do anything based upon a random complaint. As a result, this section should probably be changed to something like: > 4.4 Inform the IETF of Antitrust-Related Issues > > Participants can report potential antitrust issues in the context of = IETF activities by contacting IETF legal counsel (legal@ietf.org) or via = the IETF LLC whistleblower service. Note that reports will only be = assessed for their impact upon the IETF; should you be directly impacted = by a antitrust issue, you should obtain specific legal advice. Cheers, -- Mark Nottingham https://www.mnot.net/