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

Brad Biddle <brad@biddle.law> Sat, 25 February 2023 02:19 UTC

Return-Path: <brad@biddle.law>
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 629F1C14CEF9 for <antitrust-policy@ietfa.amsl.com>; Fri, 24 Feb 2023 18:19:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.903
X-Spam-Level:
X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_FONT_FACE_BAD=0.001, 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, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, USER_IN_WELCOMELIST=-0.01, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=biddle-law.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 iz_nVUFIVBBq for <antitrust-policy@ietfa.amsl.com>; Fri, 24 Feb 2023 18:19:48 -0800 (PST)
Received: from mail-yw1-x1132.google.com (mail-yw1-x1132.google.com [IPv6:2607:f8b0:4864:20::1132]) (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 BEC97C14F5E0 for <antitrust-policy@ietf.org>; Fri, 24 Feb 2023 18:19:48 -0800 (PST)
Received: by mail-yw1-x1132.google.com with SMTP id 00721157ae682-536bf92b55cso28066717b3.12 for <antitrust-policy@ietf.org>; Fri, 24 Feb 2023 18:19:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=biddle-law.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=u7IE2ixByTz6MbnjLFsRxgqs4i7XfJqE7PZPM75kLnI=; b=Utf/LKVM0HjD70QM8uH+0L9Icb7LrH3QKkYG88tW+tDPnOBwHc58AYLoJdRLnqc92Y 6ukYNpeQ4lcgSFnJnd1+vRQJeu0fd0pAD61S4RZFUOfogLgkEKsy/j2VEmm1/aKvAiFw hfCctDbOEndGpsCt5SbzAOwuWLYsJjv6P6s9L+jamo2NgpFDd9vxWIOUrlaY838zKV7G yrj2m5Pu1ow0XPuXavPqUgQJBAM0aY/37JT9wjSZ9FRGVH/DpQa8BEXIaqeEglYfg77v XWiv77fU6fjHT/R0hm67kCmjkW7DPvAckS5gAN7BAB2mhPtOV6XIZBdsY6eNXoacE1Zk nt8Q==
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=u7IE2ixByTz6MbnjLFsRxgqs4i7XfJqE7PZPM75kLnI=; b=lV5STz9b0w9U9r92LSnY9qdxvkRWmSVXx6RXVDpqoS8SS5lhw6Ch782WZKnBqoy5ui l9uOzPZYVtYXYs1DHiXdnBX1+uZMvgXa/eP4Cc5EQQfFoc3u01+b58vjWa12ncU6DiOc ASddvpoKOc/9tve2LbTio4dOcBcNp/6uzNqpVupqiaT/jaquJeeJv8Wj3HE8y+asXCja XkRRjMMgyarMaqnyMwuL/PIBpgRnHIogvnZ3v2qLIYNDSCIVLIwsFS63iisgQHx9Jtqw zNlSeNWCNaam8eBwS1R51IA6WB12yPy3Qbkym6uL0lS6ULC/6jIr2M+gg3smW5kf1JQR vsnw==
X-Gm-Message-State: AO0yUKXDJpABxc4M+pEbopGxiV1CsN3+H0oxF0a2ImEv/UGedxYQOrYP fKpcOjg8ucE8K4ap5XionsdNGY+NwXX3+4AgBkkR9Q==
X-Google-Smtp-Source: AK7set+2GXfDhfIL0NGPAWzXU9BxABvfcWm0tB/aSKfMYV2/hf5SYQkci6jHVslLtg+JKRiuyu8TJ8wToteCNN7C1m8=
X-Received: by 2002:a81:af07:0:b0:52e:bb19:26c0 with SMTP id n7-20020a81af07000000b0052ebb1926c0mr5843971ywh.2.1677291587441; Fri, 24 Feb 2023 18:19:47 -0800 (PST)
MIME-Version: 1.0
References: <dbc9ba5b-992b-eaf0-9cc7-6bf7e4526453@joelhalpern.com> <31F6DC82-E3FD-422A-B9B0-6260DA49F6AB@kuehlewind.net>
In-Reply-To: <31F6DC82-E3FD-422A-B9B0-6260DA49F6AB@kuehlewind.net>
From: Brad Biddle <brad@biddle.law>
Date: Fri, 24 Feb 2023 18:19:11 -0800
Message-ID: <CAPdOjkg36h6Uv9jUXy6g6iOv3p1F6N=7CJ651x2-s4X1HS2wsQ@mail.gmail.com>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
Cc: Joel Halpern <jmh@joelhalpern.com>, antitrust-policy@ietf.org
Content-Type: multipart/alternative; boundary="000000000000412fd205f57ce1cf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/antitrust-policy/_k3X2piA0f7bfUtRkIFlkybkKDI>
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 02:19:53 -0000

Hi  Mirja -- I know you addressed your questions to joel, but let me offer
a few thoughts:

On Wed, Feb 22, 2023 at 6:43 AM Mirja Kuehlewind <ietf@kuehlewind.net>
wrote:

> Hi Joel,
>
> Thanks, the document looks pretty good to me. I have three questions:
>
> 1) In section 4.2, you have this point which is to be honest not fully
> clear to me:
>
> "Using detailed market data to evaluate 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."
>
>
> I would think this is only a problem if that would lead to disadvantage to certain competitors or something like that…? To me this point is currently unclear and seem overly broad, so as participant I wouldn’t be really sure what to do about this advice.
>
>
>
Discussion of "relative cost" of different implementations can be fraught,
for a number of complex reasons (largely because it can start to look like
a group discussion about prices), as suggested (for example) in Section 2
and Example 1 of the IEEE's antitrust document [1] or in this presentation
IEEE counsel gave years ago [2]. The idea here was just to flag that
potential complexity at a high level, and to invite discussion about it
if/when those sorts of circumstances arose in an IETF WG.

[1]
https://standards-dev21.ieee.org/wp-content/uploads/import/documents/other/antitrust.pdf
[2] https://ieee802.org/3/100GNGOPTX/public/may12/lindsay_01_0512_optx.pdf


> 2) Then at the end of the section the draft says:
>
>
> “… or contacting IETF counsel directly.”
>
>
> But the next section actually says
>
>
> “The IETF does not provide legal advice to participants”
>
>
> Isn’t that contracting?
>
>

I think "no" (not a contradiction) in the sense that contacting IETF
counsel could definitely be the right thing to do in some circumstances
(e.g., if a participant thought an IETF representative was engaged in some
antitrust violation, or that an IETF forum was being used to facilitate an
antitrust violation), but in other circumstances a question to IETF counsel
could result in a response along the lines of "we're not your lawyer, you
should talk to your own counsel."


>
> 2) And finally not sure if that’s the right advice in section 4.4 about reporting. I would think an employee should report something rather to their own company. Or do you mean the case where an independent third person would observe something? However, what would the IETF do with this information?
>
>
Similar to the point above, we'd definitely want reporting of any perceived
antitrust violations by IETF representatives or happening in IETF forums,
and we'd respond appropriately to the particular circumstances. We could
respond that we suggest that a participant also report to their own
employer, if and when appropriate. Note that the US Dept. of Justice
strongly emphasizes the importance of reporting in an analogous context:
"Did the antitrust compliance program detect and facilitate prompt
reporting of the violation?" [3] I suggest keeping this reporting section
as-is.

[3] https://www.justice.gov/atr/page/file/1182001/download

Thanks!

--Brad



>
>
> Mirja
>
>
>
>
> On 22. Feb 2023, at 14:46, Joel Halpern <jmh@joelhalpern.com> wrote:
>
> When this was dispatched, I said I would poke folks again.
>
> The authors would very much appreciate comments, opinions, and better
> discussion of, this draft.  We would like to be able to submit a revision
> addressing concerns by the cutoff, to align with the ADs goal.
>
> Thank you,
>
> Joel
>
> _______________________________________________
> antitrust-policy mailing list
> antitrust-policy@ietf.org
> https://www.ietf.org/mailman/listinfo/antitrust-policy
>
>
> _______________________________________________
> antitrust-policy mailing list
> antitrust-policy@ietf.org
> https://www.ietf.org/mailman/listinfo/antitrust-policy
>


-- 
Brad Biddle | brad@biddle.law | +1.503.502.1259 (mobile) | http://biddle.law