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

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 24 October 2022 01:29 UTC

Return-Path: <brian.e.carpenter@gmail.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 D26DCC14F745 for <gendispatch@ietfa.amsl.com>; Sun, 23 Oct 2022 18:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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=gmail.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 ar_N_StIQd4U for <gendispatch@ietfa.amsl.com>; Sun, 23 Oct 2022 18:29:30 -0700 (PDT)
Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) (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 1DA26C14F73F for <gendispatch@ietf.org>; Sun, 23 Oct 2022 18:29:30 -0700 (PDT)
Received: by mail-pj1-x102d.google.com with SMTP id t10-20020a17090a4e4a00b0020af4bcae10so7916091pjl.3 for <gendispatch@ietf.org>; Sun, 23 Oct 2022 18:29:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=mk8igOKjH1E+u2f1EthXVzXiQIYcoQ1VR66lOmWWOZM=; b=Mxbgl6MJlU5NcSpioi8hS77DHnz8JdhGj+Jgr6uXcAJKa1DMxFBO8wiz4p4QN197uS G4zT0K3sMcNm4UHLU3xYW7H35g4ulA3IHSx/iXnXNYYd8mt9vMjnT7HwIU5SWtdOXcXS IbFtlnCELwceFVt6H+KHbxjE/4N0EAJxkCG/fccHMO8ozZMb+j31/JSJZnpBQgWLW230 FBsETyZMPPN+jlh/ePXZNffib9QuV7VyOpSSm+JpUG2ytzTQK2wHgdP5k4U/wUcvHOJK nrVtCparVRdFPn2g9m721VllQXOo1SxkmyDyn1sDKamj6EyN6TEpC3WIgSacBMtETyNg jSvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=mk8igOKjH1E+u2f1EthXVzXiQIYcoQ1VR66lOmWWOZM=; b=u7yLeA1UQPFlLCB3dqZ7l+CjZ17FTOs9qbhso1glv8EZNO4sQpm7vhX6e6kSxzseQW t4BbmugtVqwOKt2tSV2YYz7imjfWskXLcuEpBiM5IlLf3gosyJGExijUpd6k/VdLKmfL 3ePb8E8VT9/zCd5mus7Ew/uYCsbUOGVonNVs8tpweCTO4fp4o1QrkjUoU08mHMlSuYGd v4YK+n0idV11k7Pcg6iwmMtFozb3ayrlyXXPubAWyjMT225EJJ2p2v5ttwhRLhmxnYxv 7o5QPinHfH6UdpK7TYGv8wOtiS8cNDJ1/sJTFgpNhEhnAuTOH/olTo3EDOb/YL+viute b5dA==
X-Gm-Message-State: ACrzQf2gaMC+zxpvpcbKt0LtuhRn/noW0ANZ4GZG8XhSAFxCA6wWtewO WfJ5IM2RWNCDZkAEOd6iCS4=
X-Google-Smtp-Source: AMsMyM6XmOusE3N/qk2rNn+tjXVPiKIBzmvUvv9WW1iJVzwRvfLcJapkgtAcxDzwpok3UZ0Pa1t62w==
X-Received: by 2002:a17:90a:1946:b0:212:f926:5382 with SMTP id 6-20020a17090a194600b00212f9265382mr6627537pjh.218.1666574969367; Sun, 23 Oct 2022 18:29:29 -0700 (PDT)
Received: from ?IPV6:2406:e003:1124:9301:80b2:5c79:2266:e431? ([2406:e003:1124:9301:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id nk10-20020a17090b194a00b0020d9ac33fbbsm5179168pjb.17.2022.10.23.18.29.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 23 Oct 2022 18:29:28 -0700 (PDT)
Message-ID: <b91e0b2c-4b84-6145-86b6-4b8f4055c5a6@gmail.com>
Date: Mon, 24 Oct 2022 14:29:23 +1300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Mark Nottingham <mnot@mnot.net>
Cc: Rob Sayre <sayrer@gmail.com>, Martin Thomson <mt@lowentropy.net>, gendispatch@ietf.org
References: <166645513843.21794.6131453556595611404@ietfa.amsl.com> <98ae51f1-c680-2867-bcff-8f18c34086af@joelhalpern.com> <3D1B8B24-7BFD-4041-B99F-BF6951C07A27@mnot.net> <b43c9347-878c-474c-c9d4-b657bfdedf19@gmail.com> <6b2b586a-571b-4bcb-8ed3-ce88fb680d00@betaapp.fastmail.com> <CAChr6SxUWXh-nhJMSqjeUt4gH4HVsByZ8N8SjL9iLmCML5YJ_Q@mail.gmail.com> <7936b38b-22ed-d985-7c9d-56d1ef080c2f@gmail.com> <79073834-5814-4B15-B2D9-9AA8B047A2C2@mnot.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <79073834-5814-4B15-B2D9-9AA8B047A2C2@mnot.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/gsXLvGdlqoRHUb0gEknj1nlxQs0>
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: Mon, 24 Oct 2022 01:29:33 -0000

On 24-Oct-22 14:04, Mark Nottingham wrote:
> 
>> On 24 Oct 2022, at 11:45 am, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>>    IETF participants should consult with IETF sources such as working
>>    group chairs, including IETF legal counsel as needed, to ensure
>>    that an investigation of these topics follows IETF rules and best
>>    practices.
> 
> As as WG chair, I do not want that responsibility -- and I have some amount of relevant legal training, unlike most. Competition law is highly contested, variable between jurisdictions, and ultimately only determined by a court.

Indeed, which is (I assume) why the draft scoped it to following IETF rules, not to following the law. I will of course bow to the IETF counsel's opinion...

    Brian
> 
> Concrete requirements and processes like this are a mistake, because in the reality of what we do, requiring consultation with Counsel will only result in this mechanism being used as a tactic to delay or stop work. The point of this document is to assure that we have a documented policy and have taken reasonable steps to prevent anti-competitive behaviour -- in particular, cartel behaviour -- in this venue. Our open processes and accountable decision-making are our best defence against any such accusations, and so the policy should be high-level. Compare with the W3C's:
>    https://www.w3.org/Consortium/Legal/2017/antitrust-guidance
> 
> Of course we shouldn't coordinate pricing of products or carve up territories between businesses --  those would be very odd discussions at the IETF, and prohibiting them is not onerous. Saying that we should involve Counsel every time we talk about what might be a new "market" (i.e., protocol or function) on the Internet is absurd on the face of it.
> 
> Cheers,
> 
> --
> Mark Nottingham   https://www.mnot.net/
>