IETF Logo Mail Archive

Re: [antitrust-policy] [Gendispatch] draft-halpern-gendispatch-antitrust

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 03 April 2023 03:06 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 37184C15153F for <antitrust-policy@ietfa.amsl.com>; Sun, 2 Apr 2023 20:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.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_BLOCKED=0.001, 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] 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 yBBkOq6G389G for <antitrust-policy@ietfa.amsl.com>; Sun, 2 Apr 2023 20:06:10 -0700 (PDT)
Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (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 13C53C151B05 for <antitrust-policy@ietf.org>; Sun, 2 Apr 2023 20:06:06 -0700 (PDT)
Received: by mail-pj1-x1033.google.com with SMTP id l7so25853779pjg.5 for <antitrust-policy@ietf.org>; Sun, 02 Apr 2023 20:06:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680491165; 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=NwhDUM8UG50xhjrxf+tSn6cYytSdKe0zoeQ8rxhSyeY=; b=ZXKNJ3WNoFtDfEvnLJIjUtX2oAA43ixIlffxr0HAPe3+8aJtDDXeGPbR13M/TQsshh nT6p+jWKIF47mPapejGK+ssmuv00HTQ3D4pRLh6+YX65bPWNi19wT+TdHBuBpbNdHpHo UzD2wr8SP9nm3fR6RXj8nXSl80QBxth3X9xnnlzhDGoyurVUozIvcvulDg2TrW6QIWSJ MxnawCKYo4978mB4lvHUxMuofovITHldXNZ94rhl53w3v+BUDTCjNY8o5SdH735vK6du ONhJGl2QF9bTJp8vC426rO81dPgcC6qcUU9nnVGseLHERPCLNwKSrG/whIYCj02a2bhI h5sw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680491165; 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=NwhDUM8UG50xhjrxf+tSn6cYytSdKe0zoeQ8rxhSyeY=; b=MqFN5uCBDqq+vI1y1r2K44c94hrbTa/y0tkFZ5nZ1TFEhlCQ4FdkJPPezE8v/lF1ay ccMiNJ7aiTULxoqK0dOJNYLfFv8OIIZNpchJQ3fqMNDESQrBUQhPAzefrok45LkYJat7 gqi/F8Zq05h7NW6JH6lscj0VDCMbwXcxc0CV3Kwk/g+nOrSlMlaS9FE27gLsKmtn1hbr SAQwZuby6OSVTVy4TJ2wpMesMcszcEUjrqr3QvGqtaUmZeAtRFAY9oOATt+JHnjVWGyP 5Wq6J45atHlQF8tYy2QoXzYEomKcdclnE/BN/eUui7DQ3hVJGcrXgOX8kel1XdnyMw1P kIKQ==
X-Gm-Message-State: AAQBX9dC9ssEkEjvqvE4XnnBCeqjfW6cBSrDnxbesvcXc3M+a0z1dm6y Ta1pTKmhj0m7dkawEwY+LWI=
X-Google-Smtp-Source: AKy350Y4ZhuOlw5VTwibisjzkAua4ymFQ4OEnRKE3Dq/JDnsLrjTGXaDY+ZiQM/rOCYbMQKNXL560g==
X-Received: by 2002:a17:903:120a:b0:19e:7d67:84e6 with SMTP id l10-20020a170903120a00b0019e7d6784e6mr40740171plh.0.1680491165429; Sun, 02 Apr 2023 20:06:05 -0700 (PDT)
Received: from ?IPV6:2406:e003:1184:f001:9991:d1ad:8c20:42bd? ([2406:e003:1184:f001:9991:d1ad:8c20:42bd]) by smtp.gmail.com with ESMTPSA id s9-20020a170902988900b001a1dc2be791sm1478330plp.259.2023.04.02.20.06.03 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 02 Apr 2023 20:06:05 -0700 (PDT)
Message-ID: <d9c28658-f546-3b60-c8ed-6f6a1a65e749@gmail.com>
Date: Mon, 03 Apr 2023 15:06:01 +1200
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: Russ Housley <housley@vigilsec.com>, "jmh.direct" <jmh.direct@joelhalpern.com>
Cc: Lars Eggert <lars@eggert.org>, antitrust-policy@ietf.org
References: <4PpQHf45Hnz1ns8c@mailb2.tigertech.net> <42C337B6-C28C-4CF1-B769-3D026E2FF7BA@vigilsec.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <42C337B6-C28C-4CF1-B769-3D026E2FF7BA@vigilsec.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/antitrust-policy/_-HcyZwSjvapEQESaHkS_6cCCAU>
Subject: Re: [antitrust-policy] [Gendispatch] 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: Mon, 03 Apr 2023 03:06:14 -0000

Russs,

If that section was renamed and its first sentence was fine-tuned, thus:

"4. Additional Information

It is assumed that IETF participants will rigorously follow all applicable IETF policies as set out in section 3 above."

it seems to me that your concern would be addressed. The remaining text in that section seems to be factual. (There are occurrences of "should" but since this isn't a BCP, they aren't normative.)

Regards
    Brian Carpenter

On 03-Apr-23 08:50, Russ Housley wrote:
> Joel:
> 
> If the Antitrust BOF had decided to devlop a policy, then there would be a policy to cite in Section 3.  That was not the outcome.
> 
> I have no problem with Section 3.  However, Section 4 is "Additional Recommendations", which in my mind should be replaced with educational material on antitrust.
> 
> Russ
> 
> 
>> On Apr 1, 2023, at 1:11 AM, jmh.direct <jmh.direct@joelhalpern.com <mailto:jmh.direct@joelhalpern.com>> wrote:
>>
>> Fundamentally, recommendations ARE education.  I have nonudea what an educational document would look like without recommendations.
>> We have been as clear as we know how about the fact that none of the recommendations set IETF rules or policy.
>> Even 4.2 bullet 2, which w are trying to rework further, just says that this is something known to cause problems for SDOs.
>>
>> Yours,
>> Joel
>>
>>
>>
>> Sent via the Samsung Galaxy S20 FE 5G, an AT&T 5G smartphone
>>
>>
>> -------- Original message --------
>> From: Russ Housley <housley@vigilsec.com <mailto:housley@vigilsec.com>>
>> Date: 4/1/23 12:49 PM (GMT+09:00)
>> To: gendispatch@ietf.org <mailto:gendispatch@ietf.org>
>> Cc: Joel Halpern <jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>>, Lars Eggert <lars@eggert.org <mailto:lars@eggert.org>>, antitrust-policy@ietf.org <mailto:antitrust-policy@ietf.org>
>> Subject: draft-halpern-gendispatch-antitrust
>>
>> As EKR already asked on the list, what needs fixing? As I recall, the lack of any problems was the reason that the ANTITRUST BOF decided not to produce a policy so many years ago. The conclusion was that educational material was sufficient.
>>
>> The draft-halpern-gendispatch-antitrust document explicitly says that it does not change IETF policy; however, the document includes recommendations.  So, it really is doing more than education.
>>
>> Russ
>>
> 
>

v2.46.0 | Report a Bug | By Email | System Status