Re: [antitrust-policy] New Version Notification for draft-halpern-gendispatch-antitrust-08.txt

Jay Daley <exec-director@ietf.org> Wed, 06 March 2024 17:47 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 33E11C14F5FE for <antitrust-policy@ietfa.amsl.com>; Wed, 6 Mar 2024 09:47:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=staff-ietf-org.20230601.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 NPHcsvgCKg-i for <antitrust-policy@ietfa.amsl.com>; Wed, 6 Mar 2024 09:47:27 -0800 (PST)
Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (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 7463FC14F5E9 for <antitrust-policy@ietf.org>; Wed, 6 Mar 2024 09:47:23 -0800 (PST)
Received: by mail-wm1-x32c.google.com with SMTP id 5b1f17b1804b1-413007fe6a3so223475e9.3 for <antitrust-policy@ietf.org>; Wed, 06 Mar 2024 09:47:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1709747241; x=1710352041; darn=ietf.org; 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=aZkU+V2s0xenR+lsAtpLlMSPbAcKiUOHkPPKviKvF5M=; b=u3egJRG9wAk8hm+IZLsh79MrMyMYI7SsLTa2H/rjTzhIIlNKL5rZNcydu/8BObh7Y7 o0Lm7d9cc1UdHAG1RX0jK4rgYjUeIdpwo495T3geJvyS+VIoLDqy+29eOYSoO+u+wxbX 6Ankd/+P1JCKxqebsaOcsOsy0IXX+rxTqH0VWm77jhp6O+Mbm4ov8LuPXM+4Va4X4AWs j38/0toOy+Hjk39dOFI9BEjee+k5I8jK/WmbmN5kOn8dag6dvqSz5KGn0ji/ZS6DCpqr fLBX4tttamv9hnGUWFHtaHMHJqyj5TRzNUf+z5VE68wBSFTItfExYfdvv3OVuB666jCK MSyg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709747241; x=1710352041; 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=aZkU+V2s0xenR+lsAtpLlMSPbAcKiUOHkPPKviKvF5M=; b=BohIpo2yBRYe71RZ2tlQ6oPQGmv9rTD1wVoiiXIuW2c+53vI95gRu+CVABnC3CFMgo wE3PXe+W5yk6gojgugPteNVtVHbVyWieNjSYbSNi206p2WNMTATQQuml5yKN6nDcgbqB iKAmj8qqgEhks0LHjbf+2xRGUGCfrJVqEWNyUtd4TNGNh8Cs7/ee4UcrL23gApoXAtXy Oz6O+1v9BwrA3UCdPVXAZngH89xv631iSI1UY/8cSancIHKSUcC6fMbHJs/JDtpL1oLS PRgUMkbzN1WXqkT/TqnQPZ3NrwV3KfU/RpIrdwet/xwc6RgJ8q3HPwqmyrKJvfuxepzT IU0g==
X-Gm-Message-State: AOJu0YztvhpQnCT23VKk3DNqRIirJrHgkqSWdQ3DxWEsTrtJvOst1gcV 67BuPWxBPfQziowwHvCpxV7xN6GJF7MiW/WAt7ibu65ixnZaeQGZWMyAR15Por6bw8tf4+I93PN 0tCA=
X-Google-Smtp-Source: AGHT+IHxztfFdIMfBAyFgujkmHkKRlBxOaCrDskyYh8yhysisv4ME5PjB9BYQD1b37gczt/Vc5Lr4A==
X-Received: by 2002:a05:600c:3d0d:b0:412:f73c:768b with SMTP id bh13-20020a05600c3d0d00b00412f73c768bmr1545867wmb.14.1709747240989; Wed, 06 Mar 2024 09:47:20 -0800 (PST)
Received: from smtpclient.apple (host-92-27-125-209.static.as13285.net. [92.27.125.209]) by smtp.gmail.com with ESMTPSA id az23-20020adfe197000000b0033e4403c6a9sm7425262wrb.22.2024.03.06.09.47.20 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Mar 2024 09:47:20 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
From: Jay Daley <exec-director@ietf.org>
In-Reply-To: <MN2PR19MB4045F833057FE6450F94BD2683212@MN2PR19MB4045.namprd19.prod.outlook.com>
Date: Wed, 06 Mar 2024 17:47:09 +0000
Cc: "antitrust-policy@ietf.org" <antitrust-policy@ietf.org>, Lars Eggert <lars@eggert.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <23CE98D1-D619-49EE-947C-EE62326CC294@ietf.org>
References: <170924133688.22191.501196370379528149@ietfa.amsl.com> <1AE485F0-0DD8-4D0B-9581-1F3B2B3ABAA2@staff.ietf.org> <MN2PR19MB404529B1B9485A99BB39ABEC83232@MN2PR19MB4045.namprd19.prod.outlook.com> <18901D0C-D1F0-4B06-9CE3-E7A59C85D362@ietf.org> <MN2PR19MB40453C8016DCA9567614A04183212@MN2PR19MB4045.namprd19.prod.outlook.com> <DDFC7ADB-760A-4899-87D2-5DEB52307491@ietf.org> <MN2PR19MB4045F833057FE6450F94BD2683212@MN2PR19MB4045.namprd19.prod.outlook.com>
To: "Black, David" <David.Black@dell.com>
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/antitrust-policy/-8GeRRcjsF5HtIwNPkCYLXCxifI>
Subject: Re: [antitrust-policy] New Version Notification for draft-halpern-gendispatch-antitrust-08.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: Wed, 06 Mar 2024 17:47:28 -0000

Hi David

> On 6 Mar 2024, at 16:56, Black, David <David.Black@dell.com> wrote:
> 
> > "IPR (licensing) terms" has exactly the same problems - there are times when it is not an antitrust risk and so even this mentioning
> > it leads to confusion and mis-interpretation around the boundaries of what is acceptable and what is not.
>  This is not about stating or implying what is acceptable vs. what is not – that should be left to legal counsel. 

Let me try and explain this better: To put it in concrete terms, with very basic advice of the form you suggest, we had questions of the kind  "so does that mean I can’t do X unless I check it with a lawyer first?", and "does this mean I can’t do X any more because I don’t have access to lawyers to advise me", and "if someone else does X do I need to get legal advice before I respond",  where the X they have specified is something entirely acceptable and in some cases not actually about this subject.

It was trying to respond to those questions that then led us down the path of trying to provide guidance on where the boundaries lay because leaving it with these questions unanswered appeared to be doing more harm than good, but that is not where we started and it was not going down that path that created the confusion.  

> The goal is to strongly suggest obtaining legal advice (e.g., on what is acceptable vs. what is not) before engaging in any activities in this area.  I think that sort of strong suggestion is highly appropriate for "IPR (licensing) terms" discussions, and I also think that it's fine for participants to steer further clear of discussions in this area than is strictly necessary.

The authors would like to have seen this sort of guidance in this document - we are not withdrawing it because disagree with it but because we could not develop any wording to express this, even in the most minimal form, that does not create more problems than it aims to solve.

Jay

>  Thanks, --David
>  From: Jay Daley <exec-director@ietf.org>
> Sent: Wednesday, March 6, 2024 9:40 AM
> To: Black, David <David.Black@dell.com>
> Cc: antitrust-policy@ietf.org; Lars Eggert <lars@eggert.org>
> Subject: Re: [antitrust-policy] New Version Notification for draft-halpern-gendispatch-antitrust-08.txt
>  [EXTERNAL EMAIL] Hi David
> 
> 
> On 6 Mar 2024, at 03:56, Black, David <David.Black@dell.com> wrote:
>  Hi Jay,
> 
> 
> E.g., in a new paragraph at the end of Section 4.2 (Obtaining Independent Legal Advice):
> 
>  Participants are specifically encouraged to obtain independent legal advice before engaging in activities that involve complex and subtle areas
>  of antitrust law and regulations, e.g., use of unpublished market data to inform decisions and discussion of IPR licensing terms and conditions with IPR owners.
> 
> That would provide a useful warning to participants without getting into the details of exactly which activities are ok vs. not ok.
> I've deliberately generalized both topics in the above "e.g." list, and additional topics could be added.
> 
> This is basically what that section was aiming to say - watch out with these areas.  Unfortunately, it has not been possible to identify
> *any* agreed text that can be used for this purpose.  For example, the text I used and that you reproduced "unpublished market data"
> is considered by some to be completely missing the point and therefore more harmful than helpful.  
> 
> Then drop the "unpublished market data" example.  I think it would still be helpful if "discussion of IPR licensing terms and conditions with IPR owners" is used by itself an example where consulting with counsel is encouraged.
>  "IPR (licensing) terms" has exactly the same problems - there are times when it is not an antitrust risk and so even this mentioning it leads to confusion and mis-interpretation around the boundaries of what is acceptable and what is not.
>  Jay
> 
> 
> 
> Thanks, --David
> 
> -----Original Message-----
> From: Jay Daley <exec-director@ietf.org>
> Sent: Tuesday, March 5, 2024 4:10 AM
> To: Black, David <David.Black@dell.com>
> Cc: antitrust-policy@ietf.org; Lars Eggert <lars@eggert.org>
> Subject: Re: [antitrust-policy] New Version Notification for draft-halpern-gendispatch-antitrust-08.txt
> 
> 
> [EXTERNAL EMAIL] 
> 
> Hi David
> 
> Thanks for that - response below:
> 
> 
> On 4 Mar 2024, at 16:13, Black, David <David.Black@dell.com> wrote:
> 
> Jay,
> 
> 
> The only substantive change is that the previous section "Topics requiring caution" has now been deleted.
> In the previous version of this I-D, this section covered two areas: 
> the first began "Using unpublished market data to evaluate the 
> relative implementation costs" and the second was "Entering into potentially discriminatory, group negotiations of IPR terms".
> These are both complex areas where some behaviours are an antitrust 
> risk and some are not, but it has become clear that explaining where 
> the difference lies is not possible and all attempts so far have confused people and led to mis-interpretation.
> 
> We understand that some on this list wanted this explained, while others wanted this whole section deleted, but after much discussion we concluded that deletion was our only option.
> 
> Would it be reasonable to recognize the complexity and subtlety of those topics by mentioning them (or generalized versions of them) as specific areas in which independent legal advice is recommended?  That would send people with doubts/questions about them to the experts (e.g., anti-trust lawyers), which is what I think we'd like to see happen.  E.g., in a new paragraph at the end of Section 4.2 (Obtaining Independent Legal Advice):
> 
>  Participants are specifically encouraged to obtain independent legal advice before engaging in activities that involve complex and subtle areas
>  of antitrust law and regulations, e.g., use of unpublished market data to inform decisions and discussion of IPR licensing terms and conditions with IPR owners.
> 
> That would provide a useful warning to participants without getting into the details of exactly which activities are ok vs. not ok.  I've deliberately generalized both topics in the above "e.g." list, and additional topics could be added.
> 
> This is basically what that section was aiming to say - watch out with these areas.  Unfortunately, it has not been possible to identify *any* agreed text that can be used for this purpose.  For example, the text I used and that you reproduced "unpublished market data" is considered by some to be completely missing the point and therefore more harmful than helpful.  
> 
> cheers
> Jay
> 
> --
> Jay Daley
> IETF Executive Director
> exec-director@ietf.org
>  -- 
> Jay Daley
> IETF Executive Director
> exec-director@ietf.org


-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org