Re: [antitrust-policy] I-D Action: draft-halpern-gendispatch-antitrust-05.txt
Eric Rescorla <ekr@rtfm.com> Fri, 10 March 2023 23:10 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 C6AA0C1526F7 for <antitrust-policy@ietfa.amsl.com>; Fri, 10 Mar 2023 15:10:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.894
X-Spam-Level:
X-Spam-Status: No, score=-6.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 LkEM-60XeWIR for <antitrust-policy@ietfa.amsl.com>; Fri, 10 Mar 2023 15:10:13 -0800 (PST)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (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 B00F0C1526E9 for <antitrust-policy@ietf.org>; Fri, 10 Mar 2023 15:10:13 -0800 (PST)
Received: by mail-pf1-x42d.google.com with SMTP id x7so4610567pff.7 for <antitrust-policy@ietf.org>; Fri, 10 Mar 2023 15:10:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; t=1678489813; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=3eY7RGzjyXvvPdb+Jl96OWGLZld4wZ9cm6IpyCKsIgI=; b=jjnYbXT3zF97NmNx5RD5IGgIrYzHUPLuPC/T/Dby2D/ikXv3uIHfAmB1PsP9TOshVH ihMIEw9LN7dlU13R4Ef9x85Y8Tq8lYmpt40Y4RkY5gGxPmwhitrkjfDRiJrdJMgiptoW 2QRtLKFUGvVshfThKlKxLUCwt+yO3wdPdJTOL0nX2MZvbT9q7ln8s+85QkJLcOQUwzbd q/GOZvfLBr1dfTnCFAq9S6uayyO6Ny58OIYEPl3ffn+JVheZaRPl4fdwYtW2Px0D5NOu EDgaltunybomEfIPGCC5y9LtIgQnbtdiJ6VmwIwl6YRy0aJCkcz/6kNdji/9Vsy3pJob +jcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678489813; 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=3eY7RGzjyXvvPdb+Jl96OWGLZld4wZ9cm6IpyCKsIgI=; b=R7BhhEAZBEHItQuaW29HvL1MtHsVg3TokRhiJHesqlFgiYzaMIF4HCR8lk28RodSfd 8syzhSphWUAcUyl5CzbrgeG1sTZYFKJl16QEc2QAG1/O4luMcvliCS6O6ow3z7kH/JYf 10FtHN8Jqkw19FzK58bWnQ79Kw55ZZiytwFd6D6S2Jav8Ordhec2sobyEm1bAl3oYQVd EpyPbCux8CmwQx45VPnxad+6swsoKC+22JCgOzzw1UgKGw57JQ6+R4u0aWb3oMhYXUUz CBDMVWwDdT2LBHoBreZ3ms5etudmuRXSe6OThTNIwupcENWkAnvUOYmWzBtOVGu7SYMc UH/Q==
X-Gm-Message-State: AO0yUKUOEeExuowSyB7S4kWpkWdfxUWhBOgE2dzZc1xmOI5BEM2+9zxS bGjzr8KO4Ww++P/ZyelhhUXTLoRUvv2QwFAexOZBWo/eoYz9uvbT
X-Google-Smtp-Source: AK7set9hw17NcXt1U/R2sFeV/gQpkTfvVpA8SBsgnT3NZFNhlWuHjy0koZmONYNKubbDXc8HBPO0+rv4e2H6EXsdbUo=
X-Received: by 2002:a63:7f5c:0:b0:4f7:2c41:ff0e with SMTP id p28-20020a637f5c000000b004f72c41ff0emr8890604pgn.2.1678489812815; Fri, 10 Mar 2023 15:10:12 -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>
In-Reply-To: <PH0PR17MB4908EAC244784896749B1E2EAEBA9@PH0PR17MB4908.namprd17.prod.outlook.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 10 Mar 2023 15:09:36 -0800
Message-ID: <CABcZeBOhs+f5ne_21UkDW-edSmHqxck9qeSFu38ovKZBOeQYHQ@mail.gmail.com>
To: Stephan Wenger <stewe@stewe.org>
Cc: Jay Daley <exec-director@ietf.org>, "antitrust-policy@ietf.org" <antitrust-policy@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000d71c905f693dd6e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/antitrust-policy/mJzBx2mucwsCfshDpjKutdpoWyU>
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: Fri, 10 Mar 2023 23:10:14 -0000
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] 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