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

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 24 January 2023 01:16 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 EE2BEC15256A for <gendispatch@ietfa.amsl.com>; Mon, 23 Jan 2023 17:16:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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=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 x2rvaPEf1g2H for <gendispatch@ietfa.amsl.com>; Mon, 23 Jan 2023 17:16:23 -0800 (PST)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (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 3B5D7C1522C4 for <gendispatch@ietf.org>; Mon, 23 Jan 2023 17:16:23 -0800 (PST)
Received: by mail-pf1-x434.google.com with SMTP id i65so10229923pfc.0 for <gendispatch@ietf.org>; Mon, 23 Jan 2023 17:16:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=QEl4aqxcxJGftLvqTDHk9C5NCqEqMHAltlR/9kwRpXE=; b=ZgQ+mEf2OuZNGbW1tUWBw6KlDtK9Kad9+e4ND1kjyj3RRRSuegzC5LmvZmKb8ZLCy4 nSct5x1ELORQ7sSa1ozrtIeO8Q0NqESD3/DPEUQOq0fGVurtYahjsbjsBb59gEJt78dD Mu2c80l1V12JK7jfRgOEXJ44Dl4RYDzcb7FhtxGM/SvXmMizjUoFCAGTEzUmFcXIA+T7 E0S3AHXfVD0HAUEl1Wwtp6+nmXfQ1jIf2Wh8VwlKNwlGXRvFAy82rPRGvEfhPVvCRnSf yYuh8UymeMkdz42AAev83Sj6OBgKjlcEuy07kdGc6ZDYmfTXmvp+yn0Nr7Mxb48fhkQ6 xWOw==
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: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=QEl4aqxcxJGftLvqTDHk9C5NCqEqMHAltlR/9kwRpXE=; b=sFruAOhnotfmOZpkqbGVjyR2k7stduUEn5RNLUKc/C5nB9XOOhtc8KFekh6qedesgL 5WF+66skbKXrODiyQSfAnNMCp9DkyzloOrSTBNBaOJA6Tr1oaIwselalOBPps0soXGKS t+liA1ewsdS0gWiPJkLjns3gzCJy+2MIoyupKcz663UF+hpwB/yvbYiIoxQYsppDoBBQ TAwgYERkCybaFTF8YFKsAew9sCLRMwqVNPvasggFiYTDlRkmrBotyd9V8qMqsZlNoRgV 8dTYn9cAcyAxuDlGKIXiscAP26mrMxTuy0PxnDx/8cgq9C6cnVE9YD6dVni45srK9o8W /O+A==
X-Gm-Message-State: AFqh2krDD4Ml8AYv/kHrdJba/JjfALSAgu2eI65WY07TWtmca60htY9o ZzOc9qri9q+5+hOwKrFj/3kJwtYDyMpRNA==
X-Google-Smtp-Source: AMrXdXvPUanOojjGe18BhqNs3phbCU+qan7fhB4/Q99FymEDxP4bEyhlHbUDYhaGb0xn5ZPfquALiw==
X-Received: by 2002:a05:6a00:44c5:b0:580:8c2c:d0ad with SMTP id cv5-20020a056a0044c500b005808c2cd0admr25281756pfb.13.1674522982071; Mon, 23 Jan 2023 17:16:22 -0800 (PST)
Received: from ?IPV6:2406:e003:10c2:2501:6969:5efe:7979:3937? ([2406:e003:10c2:2501:6969:5efe:7979:3937]) by smtp.gmail.com with ESMTPSA id k1-20020aa79d01000000b0058d91fb2239sm232897pfp.63.2023.01.23.17.16.20 for <gendispatch@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 23 Jan 2023 17:16:21 -0800 (PST)
Message-ID: <63614e5c-c35e-ed8d-70ba-d280d3e3fe19@gmail.com>
Date: Tue, 24 Jan 2023 14:16:18 +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: gendispatch@ietf.org
References: <167449412419.29286.16215917386542827607@ietfa.amsl.com> <2edf1ce6-5c68-9ba2-7275-da9e48dfabbc@joelhalpern.com> <dcda7010-1a86-b3bb-61c5-3eb14ec3a261@cs.tcd.ie> <a9632034-8963-02fc-b754-c778a3bc89c3@joelhalpern.com> <41b45246-4705-2019-5cfe-e8fb16992573@cs.tcd.ie> <D4BA5F56-424A-4DF4-A0DF-A908C464CE20@mnot.net> <ec87b2f0-41ff-5139-c966-4fddf9a29666@cs.tcd.ie>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <ec87b2f0-41ff-5139-c966-4fddf9a29666@cs.tcd.ie>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/GB6-my_EfPHa3AzPCAJcrBwmj0c>
Subject: Re: [Gendispatch] I-D Action: draft-halpern-gendispatch-antitrust-04.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: Tue, 24 Jan 2023 01:16:27 -0000

On 24-Jan-23 12:26, Stephen Farrell wrote:
> 
> 
> On 23/01/2023 23:22, Mark Nottingham wrote:
>> Authors -- this looks very good, thanks for your efforts. I think
>> it's ready FWIW.
>>
>> Stephen -
>>
>>> On 24 Jan 2023, at 9:59 am, Stephen Farrell
>>> <stephen.farrell@cs.tcd.ie> wrote:
>>>
>>> I'm not really aiming to water the text down so much as trying to
>>> ensure it can't easily get used to close down conversations that
>>> should be ok, e.g. discussions about centralisation or protocol
>>> changes that mostly benefit a widely-deployed "encumbent" etc.
>>
>> How would that happen? The document is proposed to be Informational,
>> and proposes no enforcement mechanism. 4.1 is in the context of
>> "recommendations for IETF participants" not process rules.
> 
> Not everyone pays much attention to the class(es) of RFC. I
> could see it happening. Moreso the more the text gets close
> to saying that discussion of x, y & z is forbidden.

But it doesn't say that. It does say that if you are unsure of
things, be careful and ask for advice (ultimately from your lawyer).
I really don't see anything in this document that would ever have
changed my behaviour, especially at times when I was an academic with no
industrial affiliation. It would definitely have *guided* my behaviour
while working for industry or consulting for industry, except that
I was already guided by essentially identical advice from employers.

    Brian

> 
> S.
> 
>>
>> Cheers,
>>
>>
>> -- Mark Nottingham   https://www.mnot.net/
>>
>>