Re: [antitrust-policy] New Version Notification for draft-halpern-gendispatch-antitrust-06.txt
Jay Daley <exec-director@ietf.org> Tue, 11 July 2023 08:10 UTC
Return-Path: <jay@staff.ietf.org>
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 53834C151536 for <antitrust-policy@ietfa.amsl.com>; Tue, 11 Jul 2023 01:10:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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=ietf-org.20221208.gappssmtp.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 115xhNMXB_31 for <antitrust-policy@ietfa.amsl.com>; Tue, 11 Jul 2023 01:10:25 -0700 (PDT)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 50F88C151527 for <antitrust-policy@ietf.org>; Tue, 11 Jul 2023 01:10:25 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id 38308e7fff4ca-2b6f943383eso84954181fa.2 for <antitrust-policy@ietf.org>; Tue, 11 Jul 2023 01:10:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf-org.20221208.gappssmtp.com; s=20221208; t=1689063023; x=1691655023; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=lKXQ+6S2ipSn7yeFB83Rns6Y8jmXrzCRz45WogfW8Ts=; b=TRFXkAnJTHYfupBUKzIhvbXK/OlvXU2rtTH5xXXZtkKELFtxgI5NkqdD1PZfmLjpKo TFwtlNwbWe4KJcMa7h1j2iP6KB272T7+hlgix+IGiHAyDAyqwr9TBh4BhLXdb8ifkBz5 EwhEwIGq+9Cm3lTTl7gHXCAiZWZerm4pVrL3mTu581phxhhb4XB4sDlJ8PmmBIOiFxi/ xCUozfroaKUbd4+jeJetzZy4oAJYu2xUdae+wDG+QwC+UxmOqbCgfINJJzlHn3SQGU7B uzlGJk4IPfziKpQP6YPd1Ir9BfusRke0yZKL9ipcaoRyuQaJPzwajU/GaDHZdWKdcMYN vOzw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689063023; x=1691655023; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=lKXQ+6S2ipSn7yeFB83Rns6Y8jmXrzCRz45WogfW8Ts=; b=KyoFtaGo92j6nmL1wGOVz/67Zg7dmEYsmQnu63FoUgjqZ7x8U/gepA3XresCZNJQKj bNnMGplMN5788zFGGB8h8ktPIyMM2CY/8Xk5YKssIwpJaHRwzW33gRDAw1SO2ZzSDoNJ 7Sq6UJ0icjrSBlQleEHaa+49EP+5Yu/R7C+pXlahM/5FdN6aHiMxZcU6hUs/pwRWMV9g fVsu9cDBqf+2HL+MHv5mLsaVBEcq2TrFg8znZZgxTT7yXPbJfdkCjxRxZ5Yfb2jS370N 0+MtCUwsolUP55mbo/BXP/ZLXHO/o4x0WDWRbmxz5JkkJmusrM4IQb5k2SfC4edsQubO FfIA==
X-Gm-Message-State: ABy/qLZyTXutHBeV7lQa19yNwEO8kUkpKE+h6BcwWggAA3A/BfjuV0xR r1JeEEwQAzaRXZSwVP9XDUyZwxCobovdqj77pqIwnMfr
X-Google-Smtp-Source: APBJJlF9v4oo26efAeAac3KOR0t/7ETPRN/wk8y7svjIDBtX8ga2cIJiX91BKUzRKlFcvojASi/UnQ==
X-Received: by 2002:a2e:a30b:0:b0:2af:25cf:92ae with SMTP id l11-20020a2ea30b000000b002af25cf92aemr14010746lje.22.1689063023237; Tue, 11 Jul 2023 01:10:23 -0700 (PDT)
Received: from smtpclient.apple (host-92-27-125-209.static.as13285.net. [92.27.125.209]) by smtp.gmail.com with ESMTPSA id 12-20020a05600c020c00b003f819faff24sm12360893wmi.40.2023.07.11.01.10.22 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Jul 2023 01:10:22 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <PH0PR17MB4908DC5241A972D581D9C46BAE31A@PH0PR17MB4908.namprd17.prod.outlook.com>
Date: Tue, 11 Jul 2023 09:10:11 +0100
Cc: "antitrust-policy@ietf.org" <antitrust-policy@ietf.org>, Brad Biddle <brad@biddle.law>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FFCEFA2A-469D-49EA-A61B-D7A885DA59EE@ietf.org>
References: <168901026560.7883.14919362245027450565@ietfa.amsl.com> <2AE74757-7A99-49EC-8CCF-615CCAB21B6C@ietf.org> <PH0PR17MB4908DC5241A972D581D9C46BAE31A@PH0PR17MB4908.namprd17.prod.outlook.com>
To: Stephan Wenger <stewe@stewe.org>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/antitrust-policy/-V5cJgg0LR61m7T38Z0Je6TkfXU>
Subject: Re: [antitrust-policy] New Version Notification for draft-halpern-gendispatch-antitrust-06.txt
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: Tue, 11 Jul 2023 08:10:30 -0000
Hi Stephan > On 11 Jul 2023, at 07:38, Stephan Wenger <stewe@stewe.org> wrote: > > Hi, > I had a quick look. Many of my previous concerns are adequately addressed, thank you. The strict avoidance of 2119 terms lead to somewhat clumsy language, but that’s something I can live with. > My preference is still to move the second bullet of section 4.2 “Entering into group negotiations of IPR terms.” into section 4.1. Any reason why you left it in 4.2? The discussion about this point had a few different parts to it, including those who wanted nothing said here at all. It would be useful to hear if those concerns are allayed by the narrower text and if so if it can move to 4.1 "Topics to avoid". > I’m still at loss about the detailed market data. As I argued before: I (and also counsel I consulted) see nothing wrong with the use of *published* detailed market data in evaluating technical alternatives through cost analysis. The demarcation line ought to be the use of published vs. unpublished data, not the use of detailed market data at all. Was this a conscious non-change, and if so, why? Have I missed discussions that indicated I’m in the rough on this one? Sorry, we missed that when we went through the feedback. I will raise it with my co-authors. Jay > Thanks, > Stephan > From: antitrust-policy <antitrust-policy-bounces@ietf.org> on behalf of Jay Daley <exec-director@ietf.org> > Date: Monday, July 10, 2023 at 20:04 > To: antitrust-policy@ietf.org <antitrust-policy@ietf.org> > Cc: Brad Biddle <brad@biddle.law> > Subject: [antitrust-policy] Fwd: New Version Notification for draft-halpern-gendispatch-antitrust-06.txt > Hi All > > A new version of the I-D is now available - sorry this took so long to produce. > > The changes between this version and the last version are as follows. These are all in response to feedback identified on list > > 1. Feedback: Add a reference to relevant EU law/regulator > This was a new sentence added in the middle of section 2.2 > > 2. Feedback: Prevent weaponisation > We have not added a specific anti-weaponisation clause due to concerns that such a clause would itself be weaponised. Instead we have removed all usage of the words "must", "should" and "may" except where they appear in the boilerplate, which we believe makes it very hard to misuse a quote from this document, and removed anything else we think could be misused. The changes here are > > - Changed last sentence of 4.1 from "Participants must ensure that their conduct does not violate any antitrust laws or regulations." to "Participants are responsible for ensuring that their conduct does not violate any antitrust laws or regulations." > > - In 2.3 replaced the two instances of "must not" with "cannot" > > - Changed 6 from "This document may be considered to document means to avoid risks to the IETF and IETF participants related to antitrust. One may consider those to be security considerations. Other than that, this document introduces no known security aspects to the IETF or IETF participants." to "This document introduces no known security aspects to the IETF or IETF participants." > > 3. Feedback: Clarify the issue of people participating as individuals and the legal risk thereof > Replaced the first sentence of 4.1 with "While individuals are expected to participate as individuals, their actions could still be construed as representing their employer, whatever their role. Therefore, participants should be aware that some topics are generally inappropriate for discussion in a standards setting environment where representatives from competitors to their employer are likely to be present." > > 4. Feedback: Correctly describe the narrow issue with IPR disclosures > Changed bullet 2 of 4.2 from "Seeking clarifications about IPR disclosures, in a context when any such clarifications could be reasonably perceived as entering into group negotiations of IPR terms" > to "Entering into group negotiations of IPR terms" > > 5. Feedback: Limit the role of the IETF (and IETF counsel) following an escalation. > This resulted in two changes: > > - Replaced 4.4 with "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; participants directly impacted by an antitrust issue are responsible for obtaining their own legal advice." > > - Deleted the last sentence of 4.3 "IETF participants should consult with their own counsel when antitrust or competition law-related questions arise." because the new 4.4 covers the same ground. > > > Finally, there was one element of feedback that we intentionally did not address: > > - The additional bullet recommended by Mark for 4.2 (topics requiring caution) that talked about abuse of a dominant position, is not included. This is because it is not strongly supported by case law involving SDOs as the other two bullets are, and because it is too easily weaponised. We note that we have added EU specific text to 2.2. > > > Further feedback is most welcome. > > Jay > > > > > > A new version of I-D, draft-halpern-gendispatch-antitrust-06.txt > > has been successfully submitted by Joel M. Halpern and posted to the > > IETF repository. > > > > Name: draft-halpern-gendispatch-antitrust > > Revision: 06 > > Title: Antitrust Guidelines for IETF Participants > > Document date: 2023-07-10 > > Group: Individual Submission > > Pages: 8 > > URL: https://www.ietf.org/archive/id/draft-halpern-gendispatch-antitrust-06.txt > > Status: https://datatracker.ietf.org/doc/draft-halpern-gendispatch-antitrust/ > > Html: https://www.ietf.org/archive/id/draft-halpern-gendispatch-antitrust-06.html > > Htmlized: https://datatracker.ietf.org/doc/html/draft-halpern-gendispatch-antitrust > > Diff: https://author-tools.ietf.org/iddiff?url2=draft-halpern-gendispatch-antitrust-06 > > > > Abstract: > > This document provides education and guidance for IETF participants > > on compliance with antitrust laws and how to reduce antitrust risks > > in connection with IETF activities. > > > > > > > > > > The IETF Secretariat > > > > > > -- > Jay Daley > IETF Executive Director > exec-director@ietf.org > > _______________________________________________ > 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] Fwd: New Version Notification … Jay Daley
- Re: [antitrust-policy] Fwd: New Version Notificat… Stephan Wenger
- Re: [antitrust-policy] New Version Notification f… Jay Daley
- Re: [antitrust-policy] New Version Notification f… Alissa Cooper
- Re: [antitrust-policy] New Version Notification f… Jay Daley
- Re: [antitrust-policy] New Version Notification f… Alissa Cooper
- Re: [antitrust-policy] New Version Notification f… Joel Halpern
- Re: [antitrust-policy] New Version Notification f… Jorge Contreras
- Re: [antitrust-policy] New Version Notification f… Stephan Wenger
- Re: [antitrust-policy] New Version Notification f… Jorge Contreras
- Re: [antitrust-policy] New Version Notification f… Jay Daley
- Re: [antitrust-policy] New Version Notification f… Stephen Farrell
- Re: [antitrust-policy] New Version Notification f… Jay Daley
- Re: [antitrust-policy] New Version Notification f… Black, David
- Re: [antitrust-policy] New Version Notification f… Rigo Wenning
- Re: [antitrust-policy] New Version Notification f… Eric Rescorla
- Re: [antitrust-policy] New Version Notification f… Stephan Wenger