Re: [antitrust-policy] I-D Action: draft-halpern-gendispatch-antitrust-05.txt
Eric Rescorla <ekr@rtfm.com> Sat, 11 March 2023 14:14 UTC
Return-Path: <ekr@rtfm.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 AC1B6C17B344 for <antitrust-policy@ietfa.amsl.com>; Sat, 11 Mar 2023 06:14:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level:
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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=rtfm-com.20210112.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 pH5wkk1PlHqx for <antitrust-policy@ietfa.amsl.com>; Sat, 11 Mar 2023 06:14:40 -0800 (PST)
Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (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 C216BC15153D for <antitrust-policy@ietf.org>; Sat, 11 Mar 2023 06:14:40 -0800 (PST)
Received: by mail-yb1-xb2a.google.com with SMTP id t4so7862106ybg.11 for <antitrust-policy@ietf.org>; Sat, 11 Mar 2023 06:14:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; t=1678544080; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=NN+KLj3aYs4R95fbjo+A+2XFVQJieDGl+3XTfprcbI8=; b=PBG1q3foe3C6A+1Sef/mSru25cermU3nhuV1lOHacs2Igqaw214eV07k3/zmhz2aEr vQEFDK5Qizqt2UckxFmWl8zi/gVFILVWNlZVqiFnj9DpcWc0pmIsH11isdVKvbJX2qjQ DMNFHryBBIfTDYNyP3NPaPEm1eDMgMPce1hjSAB+eYZ42DQQsD0D4ar9YlKOKBsWL8Qo Ux8V8OQigfLHGsU/CyxtGd/e7kadpwDnZMc0hFWFNaGAyc40z4c9ThyqkKMOizfTSqsL XY04Eajr8gXMkAR3s6VIt8b4mTQAWqSL3q9dP/Fy3bnxT0mq1mRUTWnd1STg8TJHJJ8D SCNw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678544080; 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=NN+KLj3aYs4R95fbjo+A+2XFVQJieDGl+3XTfprcbI8=; b=m86M3Jk/3sLwWIrOd5cj0lP6gTeLl/LapkqZnpCa8xg6KdUvoy5dix8zn18FhdHdfB RklZV2emRa7TXUre/aeNAs4q/z7LkLEeX7PVwndVvHWVd2rtHJuXYKnftuPIPJZNdGuD cRG8Plo+e6QRVz8zLltQx3Rdaf0/OufaIRHESIDsTwXIFrvN5dGzfmOLeCTBH71G6twm quGm4rYmP/Xm5/klNu1Buci/NNZog9QJMtAT7t2hniUfI1U8b+qDfjxXDT6ydMfXuz/K GAgYUe+yKAZ9RrYx0VpF+VdJK9mToiPFcAmXpavZybds8qIZzRJDcBN5CH1ogBAZnOCh gQPA==
X-Gm-Message-State: AO0yUKVAmt3P4BH3U+zaMO1sZ1GAoq5SZisd7ZPSTZrsjvDiqwcwrE+L jFQIgzWOkG8UTTgNL+6vnNX5IeIYcTMBFTnJNae1hURVhzk4i459
X-Google-Smtp-Source: AK7set++MBdU3M5/k2hfdul6Wg7Jw6jWzFr/Jm3m+ZdazBA5RNDKd3A+Krpx8qARNpB+VJjVSFmzq9Muub5kwC20MEI=
X-Received: by 2002:a5b:bc6:0:b0:a0d:8150:be04 with SMTP id c6-20020a5b0bc6000000b00a0d8150be04mr14616241ybr.13.1678544079752; Sat, 11 Mar 2023 06:14:39 -0800 (PST)
MIME-Version: 1.0
References: <167837316646.46529.9056427917523349000@ietfa.amsl.com> <3ec2645a-642b-de85-bec2-7b54ebace2ca@joelhalpern.com> <PH0PR17MB4908382BC2326278B5B7AD12AEBA9@PH0PR17MB4908.namprd17.prod.outlook.com> <55947793-83BF-443C-A240-B15E5BD801F2@ietf.org> <PH0PR17MB4908EAC244784896749B1E2EAEBA9@PH0PR17MB4908.namprd17.prod.outlook.com> <CABcZeBOhs+f5ne_21UkDW-edSmHqxck9qeSFu38ovKZBOeQYHQ@mail.gmail.com> <55b0a485-8b7a-9da4-aba6-6f77ccae5be9@joelhalpern.com>
In-Reply-To: <55b0a485-8b7a-9da4-aba6-6f77ccae5be9@joelhalpern.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 11 Mar 2023 06:14:03 -0800
Message-ID: <CABcZeBPz3QZHwDn4qBzKjK3a_RQtg-khGpunxjg4RCm6Fi3Pcg@mail.gmail.com>
To: Joel Halpern <jmh@joelhalpern.com>
Cc: "antitrust-policy@ietf.org" <antitrust-policy@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009d296005f6a07f56"
Archived-At: <https://mailarchive.ietf.org/arch/msg/antitrust-policy/o3l8mL8vX7humMc0w_pYzzlbFQI>
Subject: Re: [antitrust-policy] I-D Action: draft-halpern-gendispatch-antitrust-05.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: Sat, 11 Mar 2023 14:14:44 -0000
On Fri, Mar 10, 2023 at 5:46 PM Joel Halpern <jmh@joelhalpern.com> wrote: > The draft explicitly says that it does not change IETF policy. > > Further, the text in question says that what has to be avoided is > > - Seeking clarifications about IPR disclosures, in a context when any > such clarifications could be reasonably perceived as entering into group > negotiations of IPR terms." > > That is, what other RFCs already say, we MUST NOT enter into group > negotiations about IPR terms. > Can you point me to the specific RFC language you are relying on here? -Ekr This does not change the permission for WGs to decide to accept or reject > an I-D based on the IPR terms. Which is also spelled out in existing RFCs. > > I am left confused as to what is the substance of the objection to the > text? > > Yours, > > Joel > On 3/10/2023 6:09 PM, Eric Rescorla wrote: > > > > On Fri, Mar 10, 2023 at 3:05 PM Stephan Wenger <stewe@stewe.org> wrote: > >> Hi Jay, >> >> Inline. >> >> S. >> >> >> >> *From: *Jay Daley <exec-director@ietf.org> >> *Date: *Friday, March 10, 2023 at 01:33 >> *To: *Stephan Wenger <stewe@stewe.org> >> *Cc: *antitrust-policy@ietf.org <antitrust-policy@ietf.org> >> *Subject: *Re: [antitrust-policy] I-D Action: >> draft-halpern-gendispatch-antitrust-05.txt >> >> Hi Stephan >> >> A couple of questions: >> >> > On 10 Mar 2023, at 02:02, Stephan Wenger <stewe@stewe.org> wrote: >> > >> […] >> > >> > • Remove the second bullet of section 4.2. >> > The second bullet here has IMO the potential to shift the practices of >> the IETF in a direction appreciated primarily by those offering technical >> alternatives under terms that are less commercially attractive than other >> technical alternatives, and secondarily by those with comparatively bigger >> antitrust exposure. Those changes would potentially disfavor organizations >> not interested in monetarizing their IP, smaller entities, academics, and >> individuals. Upon reflection and re-reading posts of others also >> addressing this bullet, I have come around to suggest you remove this >> bullet in its entirety, as it may constitute a policy change in practice, >> despite what the (appreciated) clarifications in the doc declare. >> > I believe—and I think you would concur—that nothing is wrong per se >> with “Seeking clarifications about IPR disclosures”. Doing so may well be >> beneficial for the operation of the IETF; see my example in my previous >> post, cited above. Pointing out the content of disclosures, including >> words like RAND or RAND-Z, should be fine. Even justifying one’s support >> of one technology over another based on disclosure content should be fine. >> I think the line is crossed when people (presumably being affiliated with >> competitors) start ganging up using their power to force a supplier towards >> below market prices, independent on whether the supplier supplies IP or >> something else. That’s not something that happens through mere >> clarification questions on IPR disclosures though, and it may well happen >> in other contexts. Such group negotiation is a red flag (yes, I like that >> term and wish we wouldn’t have removed it :-) and should be covered under >> 4.1. >> >> So if this was replace with a bullet about "group negotiations" in 4.1 >> that gave an example related to IPR terms, would that in principle be >> acceptable to you (recognising that depends on the actual text)? >> >> Yes, with this caveat: the example has to be narrow enough not to >> discourage IPR related discussions in general. I’m fine with drawing a >> line when any of these factors come into play: a) discussions about >> monetary terms (with the exception of distinguishing between zero and >> non-zero, which I think is ok); or b) group pressure requesting different >> terms (“I do not support your tech unless you change to RAND-Z”, “me, too”, >> “+1”). >> > I share Stephan's concern here. WGs absolutely should be able to decide > not to > use technologies based on specific IPR terms. RANDZ is one such example, > but > it's not the only one. > > Taking a step back, I would ask whether this is something that needs > fixing. Do we > have cases of improper behavior taking place in this area? If not, then I > think this > text would probably be better removed. > > -Ekr > > >> >> > >> > • Section 4.1, add buyer/licensee collusion. >> > I leave the wordsmithing to folks with more experience, but I think >> something like “discussion about supplier’s pricing (including IP >> royalties)” needs to be added. Perhaps with a clarification like “it’s a >> cornerstone of the IETF’s IPR regime that individuals make their own >> decisions regarding the monetary or other price they are willing to pay for >> a technology, but that price, especially when expressed in dollar values, >> must not be discussed in an IETF setting. Don’t ask, don’t tell.”. >> > >> > • Section 4.1, “representatives from competitors”. >> > As it is pointed out elsewhere in the doc, in the IETF, we participate >> specifically NOT as representatives of our employers but in an individual >> capacity only. Insofar, logic suggests that the paragraph as written does >> not apply to IETF participation but rather states a general observation >> from which the IETF is safely isolated due to its rather uncommon policy of >> individual participation. I think that this is a misperception that needs >> to be addressed. >> >> Do you mean something like "While individuals are expected to participate >> as individuals, their actions can 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."? >> >> Yes. Good text, thank you. >> >> >> Jay >> >> > >> > • Section 4.1, structure as a bullet list as the para, as written, >> is close to unreadable? If not, why not? >> > Rationale was previously provided. >> > Thanks, >> > Stephan >> > From: antitrust-policy <antitrust-policy-bounces@ietf.org> on behalf >> of Joel Halpern <jmh@joelhalpern.com> >> > Date: Thursday, March 9, 2023 at 06:50 >> > To: antitrust-policy@ietf.org <antitrust-policy@ietf.org> >> > Cc: gendispatch@ietf.org <gendispatch@ietf.org> >> > Subject: [antitrust-policy] Fwd: I-D Action: >> draft-halpern-gendispatch-antitrust-05.txt >> > antitrust-policy: As noted below, the authors have posted a new >> version of the antitrust draft. We have tried to make more clear that it >> is educational and informational material, and does not change IETF >> policy. As per suggestions, we have replaced the red-flag / yellow flag >> descriptions with what we hope are clearer descriptions of the categories. >> Please read and comment on the antitrust-policy list. >> > Gendispatch: >> > We have been asked to provide a 10 minute presentation at IETF 116 >> to discuss the dispatching of this draft. Content discussion, as per the >> announcements, is still on antitrust-policy. The slides will review the >> table of contents of the draft, and then state the dispatch decision for >> any further discussion by the WG. >> > Thank you, >> > Joel (and Brad and Jay) >> > >> > >> > -------- Forwarded Message -------- Subject: I-D Action: >> draft-halpern-gendispatch-antitrust-05.txt >> > Date: Thu, 09 Mar 2023 06:46:06 -0800 >> > From: internet-drafts@ietf.org >> > Reply-To: internet-drafts@ietf.org >> > To: i-d-announce@ietf.org >> > >> > >> > >> > A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> > >> > >> > Title : Antitrust Guidelines for IETF Participants >> > Authors : Joel M. Halpern >> > Brad Biddle >> > Jay Daley >> > Filename : draft-halpern-gendispatch-antitrust-05.txt >> > Pages : 8 >> > Date : 2023-03-09 >> > >> > 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 datatracker status page for this Internet-Draft is: >> > https://datatracker.ietf.org/doc/draft-halpern-gendispatch-antitrust/ >> > >> > There is also an HTML version available at: >> > >> https://www.ietf.org/archive/id/draft-halpern-gendispatch-antitrust-05.html >> > >> > A diff from the previous version is available at: >> > >> https://author-tools.ietf.org/iddiff?url2=draft-halpern-gendispatch-antitrust-05 >> > >> > >> > Internet-Drafts are also available by rsync at rsync.ietf.org: >> :internet-drafts >> > >> > >> > _______________________________________________ >> > I-D-Announce mailing list >> > I-D-Announce@ietf.org >> > https://www.ietf.org/mailman/listinfo/i-d-announce >> > Internet-Draft directories: http://www.ietf.org/shadow.html >> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >> > _______________________________________________ >> > 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 mailing list >> antitrust-policy@ietf.org >> https://www.ietf.org/mailman/listinfo/antitrust-policy >> > > _______________________________________________ > antitrust-policy mailing listantitrust-policy@ietf.orghttps://www.ietf.org/mailman/listinfo/antitrust-policy > >
- [antitrust-policy] Fwd: I-D Action: draft-halpern… Joel Halpern
- Re: [antitrust-policy] Fwd: I-D Action: draft-hal… Brian E Carpenter
- Re: [antitrust-policy] Fwd: I-D Action: draft-hal… Stephan Wenger
- Re: [antitrust-policy] I-D Action: draft-halpern-… Jay Daley
- Re: [antitrust-policy] I-D Action: draft-halpern-… Stephan Wenger
- Re: [antitrust-policy] I-D Action: draft-halpern-… Eric Rescorla
- Re: [antitrust-policy] I-D Action: draft-halpern-… Joel Halpern
- Re: [antitrust-policy] I-D Action: draft-halpern-… Pete Resnick
- Re: [antitrust-policy] I-D Action: draft-halpern-… Joel Halpern
- Re: [antitrust-policy] I-D Action: draft-halpern-… Eric Rescorla
- Re: [antitrust-policy] I-D Action: draft-halpern-… Stephen Farrell
- Re: [antitrust-policy] I-D Action: draft-halpern-… Joel Halpern
- Re: [antitrust-policy] I-D Action: draft-halpern-… Stephen Farrell
- Re: [antitrust-policy] I-D Action: draft-halpern-… Joel Halpern