Re: [Gendispatch] I-D Action: draft-halpern-gendispatch-antitrust-03.txt

Eric Rescorla <ekr@rtfm.com> Sun, 23 October 2022 23:16 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 4D1F4C14F739 for <gendispatch@ietfa.amsl.com>; Sun, 23 Oct 2022 16:16:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.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_NONE=-0.0001, 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 nTVytqrYysdJ for <gendispatch@ietfa.amsl.com>; Sun, 23 Oct 2022 16:16:36 -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 8DD61C14EB1C for <gendispatch@ietf.org>; Sun, 23 Oct 2022 16:16:36 -0700 (PDT)
Received: by mail-il1-x136.google.com with SMTP id e19so1796793ili.4 for <gendispatch@ietf.org>; Sun, 23 Oct 2022 16:16:36 -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=jyr8EGXmRNaAqkR1hhQdNtMkFNBPF5ifNDSW1lNRfr8=; b=fgS1Hy0ypa3nIubESFMXD3imLJKxS3q2QV95gDZVATq/Qp1iOE3uS8rIdCZfD8HIuJ wNQ0xyaXYuzPNuGEtOeN1+pZTR+4b1W+kTeFgfRzMyAh5+7S3D7PrkDrDnICL+nc9xYK IgrHkePMOl4a3GD/MPf9LP52YE7K0Lf3gsYbkqnRckPUjvNrGrLpbNlcqWc9vXdMBMoZ eyi/m4UIHAKySl6eupWH8h63WUugZkDCQKs77empkkI5tXREL6WHFuwJsmwNpC9oFCR6 aechK/g37Wj69vWrybrAZL4RtKIw7EiUKWQv74IW+6IhwhhzR3iBkyYJHpepHvXN9A9T 1hnA==
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=jyr8EGXmRNaAqkR1hhQdNtMkFNBPF5ifNDSW1lNRfr8=; b=ZSW5Fumqei9T/0nB90Bx4DyVwPfRqTxrjQw2bOE7zyOhcuwPSxqD3SCXph3YyIhnMS XlUCnmsldFc67BNQ0seX3Fac5VTlqDZQUGOW1bknhn94UUG1FQNE4lFX3fhkWkKLl+HV 4Bao9Iq9qYdIe7eRCiAPUBkwANdTyrBfYQ58Xh53s2Ei6cWBikht9OroHP2NBjqOB/d3 Av+KZ7y8sHH5F26IZRksNdqzjfZgfI02kMepYAkqbciObrrIN6vCDvUDV6EJ5cUaaIXJ Tt8lpgMM3GTqEQDjkFTD8XMwdKZ2h+tOW4yioCbX00H+HshkJ1c0fmovbunkOqXig9o3 2uzg==
X-Gm-Message-State: ACrzQf26aPumCRclWrDl3hUOJWi/l+MEe7Y4NytAHgYsMwrQ42H+ubQl GtTp8X2zeBP20B/ckNaxNSjRnPG+B1GCXBmdlBfmbA==
X-Google-Smtp-Source: AMsMyM5XKmad153rzVsKMdLFenSobSl2ai+2yHl8JGIA1i4halU3Q6bC7vVKCX/LW0Nq32ba6l+aoFrmpUuSMHoM05c=
X-Received: by 2002:a05:6e02:148f:b0:2fc:54d2:7aa8 with SMTP id n15-20020a056e02148f00b002fc54d27aa8mr20181137ilk.224.1666566995859; Sun, 23 Oct 2022 16:16:35 -0700 (PDT)
MIME-Version: 1.0
References: <20221023031849.135234D275E4@ary.local> <58e68b60-0b62-ab99-3f07-8ec689680347@cs.tcd.ie> <3BC93084-A5BF-4A5B-A503-BDD003EB35F5@mnot.net> <1efe75ce-9c8d-882f-4cd9-017e03a95e09@cs.tcd.ie> <CAChr6Syq_+O=RxzhTKQPyLLuKKC_GHqWZ3eOuGa3od11OCfLkA@mail.gmail.com> <f24f4195-51d9-1491-6140-7aae6991ad91@cs.tcd.ie> <CABcZeBPCEZXJKsJ0Luo-y8AYPQvCpzEEvXX1iSPakS2QfhfWSQ@mail.gmail.com> <72e49b95-66f3-ba96-3148-44708edb0539@cs.tcd.ie>
In-Reply-To: <72e49b95-66f3-ba96-3148-44708edb0539@cs.tcd.ie>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 23 Oct 2022 16:15:59 -0700
Message-ID: <CABcZeBMLRUZaXFNYrjFT4=P8KDVMq5JPa-_7iR-pw4fv72UPnA@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Rob Sayre <sayrer@gmail.com>, Mark Nottingham <mnot@mnot.net>, John Levine <johnl@taugh.com>, gendispatch@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c8759405ebbbdd2e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/TVqPm1zbr3VXO20KEQYvrjcCMho>
Subject: Re: [Gendispatch] 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 23:16:38 -0000

On Sun, Oct 23, 2022 at 4:12 PM Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
>
> On 23/10/2022 23:39, Eric Rescorla wrote:
> > It seems to me that you are making two arguments, one of which I think I
> > agree with and
> > one I do not.
> >
> > As noted in my review, I think the language in the draft is overbroad,
> and
> > I agree with
> > you that discussing whether a specific technical choice tends to
> reinforce
> > or reduce
> > entry barriers should in fact be in scope.
>
> Ack.
>
> >
> > I disagree, however, with your argument that as an academic you don't
> need
> > to
> > avoid certain topics, because, as noted by mnot and others, the question
> > is what conditions this creates for others. You are, of course, free to
> > raise
> > those topics in your own newsletter, Twitter, etc. but the question is
> what
> > are appropriate topics for the IETF.
>
> "As an academic" here is just an example. (A person working
> for a small commercial entity ought be in a similar position, but I'll
> stick with the example of an academic.) I think it
> ought be ok for an academic (without a CoI let's assume) to
> discuss the market position of entities involved in the IETF
> say when describing (potential) upcoming regulatory actions
> or legislation.
>
> In fact we had someone do more or less that when describing
> the digital markets act recently. I would think that was v.
> useful for IETF participants yet it involved directly doing
> what this draft says to not do. (As I read it.) I do think
> it wouldn't have been ok for e.g. an employee of Meta to be
> the one presenting in that case.
>

> Yes, that needs to be done carefully, (and was in the case
> above), but we ought not preclude it being done.
>

I don't recall this presentation, so I am unable to comment.

However, I think there is a difference between an invited talk for
general information and a specific discussion of market positions
in the context of the development of a standard. It does not
seem to me to be tenable to have different rules for people who
are differently situated.

-Ekr


>
> Cheers,
> S.
>
>
>
> >
> > -Ekr
> >
> >
> > On Sun, Oct 23, 2022 at 3:24 PM Stephen Farrell <
> stephen.farrell@cs.tcd.ie>
> > wrote:
> >
> >>
> >> (BTW, with regards the dispatch question I agree with ekr.)
> >>
> >> On 23/10/2022 23:11, Rob Sayre wrote:
> >>> I can't think of anything I would be interested in, but maybe I don't
> >>> understand your position.
> >>
> >> I read the draft as telling us we ought not discuss whether
> >> or not some proposed protocol design re-enforces the mobile
> >> OS duopoly.
> >>
> >> S.
> >>
> >> --
> >> Gendispatch mailing list
> >> Gendispatch@ietf.org
> >> https://www.ietf.org/mailman/listinfo/gendispatch
> >>
> >
>