Re: [Gendispatch] Fwd: I-D Action: draft-halpern-gendispatch-antitrust-03.txt
Eric Rescorla <ekr@rtfm.com> Sun, 23 October 2022 22:08 UTC
Return-Path: <ekr@rtfm.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FB6FC14F746 for <gendispatch@ietfa.amsl.com>; Sun, 23 Oct 2022 15:08:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 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, T_SCC_BODY_TEXT_LINE=-0.01, 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 qOHr5zjKl573 for <gendispatch@ietfa.amsl.com>; Sun, 23 Oct 2022 15:08:13 -0700 (PDT)
Received: from mail-il1-x136.google.com (mail-il1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (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 1FC02C14F736 for <gendispatch@ietf.org>; Sun, 23 Oct 2022 15:07:01 -0700 (PDT)
Received: by mail-il1-x136.google.com with SMTP id q18so4371675ils.12 for <gendispatch@ietf.org>; Sun, 23 Oct 2022 15:07:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=QmxJs+DekjFrthncbzKcGcG+W/xloYNJWkG/GAOGUL8=; b=UFHq8u32W0ITzeajftCksAVVNuG3nukDiDJ8qBl6T1eCa38fMGfcLUPIc5j5zz8uzH VheBsaK6K4c5VxYAIEVGoQICCdOz5iGHteQ5Puq79OlJYm8jnDIw3Eymow1vz6Z2wvEc N5HKd4b4wC1scPf+xc2frIlHJW5wgOfQXrsIrRN9lQpUsIZtBYgMsnnhGRpO1+3Na7l1 jSZ5EhFrH/hq2dNIDyZmS8MbO/G4X8M715mGI9QofATq2zgz2zFZ5A8QaTdDawVewyXC DjSYgwCUdGBFn4WsviwgPjOSi27B5GsYch9bOymdGc06Ir140d1O0UBjMTEBHp4Gee4D QLJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=QmxJs+DekjFrthncbzKcGcG+W/xloYNJWkG/GAOGUL8=; b=ysNpgC3VqOeARJhTkcAjNiFJ+IIkrrcsp1UF/2XDz7uwApQtXPE1nMgcjzvwF+TgFa OPKXL4SpahV9N1v/T/apmPEIhyLQEYWsO4fVK6QUb3x0SnDLTWJ+9/v2SygY5e21dgLR 3KhQbrUKDXivbbnhyPfMqoFbYhYxj2xiW40YkX6Xrpu/VplY1GF+Hi8CXmPF/JII5M5O q5iP3g42I2ZypTXaDHh/wKtQ3Z2+IlJEyiWuvHeUghAHCPlDTK24L93aMJAjtZPOmqFN KguXq6dXiE8j41BA6araFTHUb2ISemblZSB8yua5KYf7V9y9Z55n9+P02sJoASN4SUej 0t2w==
X-Gm-Message-State: ACrzQf0kSpyBglMU4kdrdrgBMVTFFISS1fnsGvdAPTmtTcdzCrTsrpj2 rw5WUHsSOfz+q1oM3uCpPfIfqiDL5eFyhm/Qvd3H/U9qBhi+Cg==
X-Google-Smtp-Source: AMsMyM5UDLbCcjp7KDlMarAYlwOfH/0DmTdb0vNbHQffXofXZ9081uOpixBToh7z5JX2aCbZBjOLKCVBVz3x5M/vNQg=
X-Received: by 2002:a05:6e02:1c04:b0:2fc:8524:6f85 with SMTP id l4-20020a056e021c0400b002fc85246f85mr19303663ilh.87.1666562819717; Sun, 23 Oct 2022 15:06:59 -0700 (PDT)
MIME-Version: 1.0
References: <166645513843.21794.6131453556595611404@ietfa.amsl.com> <98ae51f1-c680-2867-bcff-8f18c34086af@joelhalpern.com>
In-Reply-To: <98ae51f1-c680-2867-bcff-8f18c34086af@joelhalpern.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 23 Oct 2022 15:06:23 -0700
Message-ID: <CABcZeBPhrQEqtL=24oHddGc7D8j4=0YRW_yt9Xd61hxE3AXpGA@mail.gmail.com>
To: Joel Halpern <jmh@joelhalpern.com>
Cc: "gendispatch@ietf.org" <gendispatch@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000dd941005ebbae4e0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/JT7QqjSOoCl6rCXrx1itzMGeSeg>
Subject: Re: [Gendispatch] Fwd: I-D Action: draft-halpern-gendispatch-antitrust-03.txt
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Oct 2022 22:08:17 -0000
Document: draft-halpern-gendispatch-antitrust-03.txt This draft seems generally reasonable. I have attached some comments below. In regard to the gendispatch question, I think this could potentially be AD sponsored but needs to continue to be subject to community engagement (i.e., developed on a mailing list and not just privately developed and Last Called). Do we have a mechanism for that? xoDETAILED COMMENTS S 2.3. * Additionally, the IETF must not be a forum where participants engage in problematic antitrust behavior, even if direct liability for that behavior falls on those participants and not the IETF, to avoid reputational harm to the IETF. This seems like a good aspiration, but it doesn't seem to have any enforcement mechanism, so perhaps it's more in the nature of guidelines than actual rules. S 4.1. Some topics are particularly inappropriate for discussion in a standards setting environment where representatives from competitors are likely to be present. These topics include: product pricing, profit margins, business relationships between specific vendors and customers, details about particular supply chains, discussions about particular market opportunities, or employee compensation or benefits. While not all discussions of these topics would I think much of this is sensible, but I think perhaps needs some narrowing. * Product Pricing To take an example, the cost of WebPKI certificates (and the fact that Let's Encrypt offers them for free) is a key design consideration in many discussions. More generally, there are systems architectures (e.g., centralized service provision) which are only compatible with some revenue source (e.g., advertising) and this motivates other designs (e.g., "decentralized Web"). I would hope that this kind of discussion is out of scope. I regret that I don't have a narrower phrase. Perhaps "pricing of the products of ones employer"? * Relationships between specific vendors and customers This also seems somewhat difficult. For instance, it's not uncommon to talk about services which are provided in partnerships, as for instance, with ISRG providing service for Apple and Google in their Exposure Notification PPM deployment. Perhaps something like "specific business terms between ..." S 4.2. * Evaluating the relative implementation costs of two technical alternatives to decide whether one is significantly more feasible in the market and thus a better candidate for standardization. As mnot notes, we do this all the time, so this guidance really just reduces to "ask your lawyer". It would be useful for this draft to provide some guidance here. -Ekr On Sat, Oct 22, 2022 at 11:08 AM Joel Halpern <jmh@joelhalpern.com> wrote: > This is a comprehensive rewrite (largely by Brad) to reflect both the > community feedback and advice from lawyers. > > Please read and comment, > > Thank you, > > Joel > > > -------- Forwarded Message -------- > Subject: I-D Action: draft-halpern-gendispatch-antitrust-03.txt > Date: Sat, 22 Oct 2022 09:12:18 -0700 > 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 Particiants > Authors : Joel M. Halpern > Brad Biddle > Jay Daley > Filename : draft-halpern-gendispatch-antitrust-03.txt > Pages : 7 > Date : 2022-10-22 > > Abstract: > This document provides 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 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-03.html > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-halpern-gendispatch-antitrust-03 > > > 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 > -- > Gendispatch mailing list > Gendispatch@ietf.org > https://www.ietf.org/mailman/listinfo/gendispatch >
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… Rob Sayre
- [Gendispatch] Fwd: I-D Action: draft-halpern-gend… Joel Halpern
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… Stephen Farrell
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Mark Nottingham
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… Brian E Carpenter
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… John Levine
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… John Levine
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brian E Carpenter
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… Stephen Farrell
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… Stephen Farrell
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… John R Levine
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… Stephen Farrell
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… John R Levine
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… Stephen Farrell
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… Brian E Carpenter
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… Stephen Farrell
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… Tony Rutkowski
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… Tony Rutkowski
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Mark Nottingham
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Stephen Farrell
- Re: [Gendispatch] Fwd: I-D Action: draft-halpern-… Eric Rescorla
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Stephen Farrell
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Eric Rescorla
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Christian Huitema
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Stephen Farrell
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Martin Thomson
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Eric Rescorla
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Rob Sayre
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brian E Carpenter
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Mark Nottingham
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brian E Carpenter
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Salz, Rich
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Joel Halpern
- Re: [Gendispatch] I-D Action: draft-halpern-gendi… Brad Biddle