Re: [antitrust-policy] https://datatracker.ietf.org/doc/draft-halpern-gendispatch-antitrust/

Rigo Wenning <rigo@w3.org> Sat, 25 February 2023 12:35 UTC

Return-Path: <rigo@w3.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 64C4BC14CF1D for <antitrust-policy@ietfa.amsl.com>; Sat, 25 Feb 2023 04:35:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 kOcUUcN3SZIg for <antitrust-policy@ietfa.amsl.com>; Sat, 25 Feb 2023 04:35:23 -0800 (PST)
Received: from isaac.sophia.w3.org (isaac.sophia.w3.org [193.51.208.85]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DAC9C14F6EC for <antitrust-policy@ietf.org>; Sat, 25 Feb 2023 04:35:23 -0800 (PST)
Received: from softbank219059088026.bbtec.net ([219.59.88.26] helo=[192.168.43.253]) by isaac.sophia.w3.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from <rigo@w3.org>) id 1pVtlo-00F5W6-0J for antitrust-policy@ietf.org; Sat, 25 Feb 2023 12:35:20 +0000
Message-ID: <47850e96-72b3-51b4-5e12-3e46b1c62965@w3.org>
Date: Sat, 25 Feb 2023 13:35:14 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.2
To: antitrust-policy@ietf.org
References: <dbc9ba5b-992b-eaf0-9cc7-6bf7e4526453@joelhalpern.com> <1E111729-9DD3-40BB-B0F3-166ABBCA035F@episteme.net> <CAPdOjkgz8Ou8uskG_hQVigTXVpdAPVP1c8HVeOAwoYqGM7pYbw@mail.gmail.com>
Content-Language: en-US, fr-FR, de-DE
From: Rigo Wenning <rigo@w3.org>
In-Reply-To: <CAPdOjkgz8Ou8uskG_hQVigTXVpdAPVP1c8HVeOAwoYqGM7pYbw@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------nUmFpS6iOQ7mWg9oP7NmRveh"
Archived-At: <https://mailarchive.ietf.org/arch/msg/antitrust-policy/qNjTDqbUjj2efQkK5SLi5KFWC2s>
Subject: Re: [antitrust-policy] https://datatracker.ietf.org/doc/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." <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: Sat, 25 Feb 2023 12:35:24 -0000

Hi all,

On 25.02.23 02:33, Brad Biddle wrote:
> I'm writing to address the concerns raised by Christian [1][2], Mark [3] 
> and Pete [4] about Section 4.2 of the draft, which recommends that 
> participants "Use Caution ... [when] [s]eeking clarifications about IPR 
> disclosures, in a context when any such clarifications could be 
> reasonably perceived as entering into group negotiations of IPR terms." 
> Christian said this "looks like an admonishment for WG to not do" things 
> like "modif[ing] standards to avoid [patent] claims, or structur[ing] 
> standards in ways that allow for negotiation of either the encumbered 
> option or a free alternative." Mark suggests that this part of 4.2 is 
> too broad and could be narrowed to focus on the scenario when "such a 
> discussion results in something that's open to all but advantages some 
> party through the structure of the agreement." Pete conveyed general 
> support for these concerns, and noted generally that "speaking in terms 
> of specific examples instead of trying to be broad would clarify things 
> greatly."

 From the W3C experience, I can contribute that given the vast amount of 
patents of dubious quality, given the price for patent searches, given 
the psychological effect on groups, the decision to discourage groups 
from "searching for" or "looking around" for patents was a good 
decision. The benefit is now confirmed by years of evidence. Note that 
W3C also has disclosure for WG participants.

But, W3C has a mechanism to deal with encumbered specifications. So IF 
something appears later, this can be dealt with. And this time-issue 
seems to bite here. Because my experience always was that a patent 
ambush was created by the patent holder trying to be as late as 
possible, often by injecting something from the outside not being part 
of the group. Which means the nasty problems will normally only appear 
in very late stages or once the process has ended. Disclosure helps a 
great deal and is enough. No "search" needed IMHO.

But if you touch the entire policy, you may take the time-issue into 
account by adding a mechanism that allows to the Working Group to change 
some aspects of the Specification to avoid certain of those patents of 
dubious quality. Because even though they are of dubious quality, those 
patents are burdensome and expensive to fight. This could ease strong 
feelings about the need for a super strict execution of the disclosure.

With Patent Advisory Groups, W3C has such a "group negotiation". Apart 
from being a pain, they were not questioned by the competition 
authorities, because they aimed at having a free specification.

Just my 2 cents from the balcony in the hope it helps your discussion.

  --
  Rigo Wenning
  ERCIM/W3C Legal counsel