Re: [antitrust-policy] New Version Notification for draft-halpern-gendispatch-antitrust-08.txt
Adrian Farrel <adrian@olddog.co.uk> Mon, 04 March 2024 13:58 UTC
Return-Path: <adrian@olddog.co.uk>
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 64436C15152B for <antitrust-policy@ietfa.amsl.com>; Mon, 4 Mar 2024 05:58:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=olddog.co.uk
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 u9fuIfCgMJ41 for <antitrust-policy@ietfa.amsl.com>; Mon, 4 Mar 2024 05:58:16 -0800 (PST)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABFEDC15155C for <antitrust-policy@ietf.org>; Mon, 4 Mar 2024 05:58:16 -0800 (PST)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta5.iomartmail.com (8.14.7/8.14.7) with ESMTP id 424Dw7gD002526; Mon, 4 Mar 2024 13:58:07 GMT
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 808604604C; Mon, 4 Mar 2024 13:58:07 +0000 (GMT)
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 743054604B; Mon, 4 Mar 2024 13:58:07 +0000 (GMT)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs2.iomartmail.com (Postfix) with ESMTPS; Mon, 4 Mar 2024 13:58:07 +0000 (GMT)
Received: from LAPTOPK7AS653V ([87.129.166.107]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.7/8.14.7) with ESMTP id 424Dw6bv005512 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 4 Mar 2024 13:58:06 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Jay Daley' <jay@staff.ietf.org>
Cc: antitrust-policy@ietf.org, 'Lars Eggert' <lars@eggert.org>
References: <170924133688.22191.501196370379528149@ietfa.amsl.com> <1AE485F0-0DD8-4D0B-9581-1F3B2B3ABAA2@staff.ietf.org> <00f301da6bd3$6dfcb380$49f61a80$@olddog.co.uk> <1C8F88D0-F64B-4CCF-99F3-EE3CD181E6D3@staff.ietf.org> <013e01da6bec$9c086260$d4192720$@olddog.co.uk> <ED981364-7087-47DF-AE83-539D4BA067E8@staff.ietf.org>
In-Reply-To: <ED981364-7087-47DF-AE83-539D4BA067E8@staff.ietf.org>
Date: Mon, 04 Mar 2024 13:58:06 -0000
Organization: Old Dog Consulting
Message-ID: <008701da6e3b$fc56be40$f5043ac0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0088_01DA6E3B.FC57CFB0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHvVTvP6WSeW8tEKKzRZmxKX2vXkgIF0Fi7AdR7ZncC++ltTwLtBPQ0AiNjVL2wnpeKYA==
Content-Language: en-gb
X-Originating-IP: 87.129.166.107
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type; s=20221128; bh=T9Wv+UqT/TjDY+V9n57XC 7aKYBuJbDfH/5pzEMe+tFY=; b=jbz3HZyGT2SQ50NMS2iPxfSOflykUO8EWeOvE P83DklI2vzdnf1JlN65srnQnQ+rqVsWKOtqB+pey27ACFsBziFHINCfWFNuezBSd FX4gl6lu2KsMavLosu+igrc/bf0WPIe0z627HLNtNXZIXJKEAJBh759FIOtrRd0M tr+sLlepuRS/QyIBXXnwCzKdNuQlcq3TwmxhwmyAIi9MSyFuWC65MMgLccErMjND 6x4x4c3/HNPNOUxc19r+NonTleMVMqY3ILCJe08A9NqqywhCmzyk08dIhv+CpxKz C0ngqdQgIr2xtALtbP9VeXdyy5436DQW3HvybmY2jWfI7FKqg==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-28232.000
X-TM-AS-Result: No--38.846-10.0-31-10
X-imss-scan-details: No--38.846-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-28232.000
X-TMASE-Result: 10--38.846200-10.000000
X-TMASE-MatchedRID: Ync95tbzDRnH1DfC+QNQxHFPUrVDm6jtEq8VpxNVVIm15eNIExieaU9Z hdVa2h4IkoEPf9Rwr1xaLOwZAbFRzz5VuIha4AdJawF+mgcxqmXcAmu1xqeett7p0Ru8jKvFEzz 5pJZz/hgfTarbNLChkhtgDXGtpBuUxBNI9kTkfyBD4HTrR22wI3XQJYS19cm1Qaizph4jN8MOcs r/se4BKXwseitYmET9Unuq6tR+CtV+fOZykHM6uwPZZctd3P4Bo8tN19oTXlf8DCHGEvzYB7rmv hde36c4VHll461yvk43pwoeDAoHmTUPD6SSL+re8Jb881FGn9mhYj6P5Q1iS0ZCAhWuYEvks1Kt ER6ri6YY59Jjf2E+Gp/DgxbxdLnhmcUNCy5hvn+8coKUcaOOvQntbDzhQonTxnKCr8I+auif7y5 OBAioaDba6gSbbjl+gVo1o+4QhtLHt8FegNoXIRxA1AKmVGTOCCo+lsDuynUDLr9vPVWwiMVA08 S977kgXVsEWVqYqahmYaQ4XR/HzG/M6LH3OjWrYrc32n84WHp+kAcS0i53MM2JeYM8GzTZ9+doe RMj31AenMgsiRZrp/vvQp8p+3+4rhAB5C8gZ6oZS5uxXPxN6QYAPqHoVmYRK3BYEZWjGamuK5kC A6Aektgw8VgCfj//yMrjFtPcM+51LO/SL0nEpIHfzWJnn0eo3oUB1aZ9pjllSB4Tpn2RE9QaG3O rempFVLAa8KXwKt4urmV0PtBrIAgPiuS4KXaCngIgpj8eDcBpkajQR5gb3tQdB5NUNSsi6/Llc1 2r74NSjKiHjrLYn5FOlJCK/1ftZzBPybJ/5vo=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/antitrust-policy/2GBUKdfQfraeG8Vm0OqN_a2YusU>
Subject: Re: [antitrust-policy] New Version Notification for draft-halpern-gendispatch-antitrust-08.txt
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, 04 Mar 2024 13:58:21 -0000
And another thing… Just in a BBF meeting and they drew attention to their anti-trust policy. https://www.broadband-forum.org/about-bbf/how-we-work/policies-procedures/the-broadband-forum-antitrust-guidelines The thing that jumped out at me was: 1. Adopt formal meeting agendas. 2. Adhere to them. 3. Minute all meetings, review them, and approve them. Not sure whether you would consider this advise important to your draft. No need for a response. Just act as you consider appropriate. Cheers, Adrian From: Jay Daley <jay@staff.ietf.org> Sent: 01 March 2024 15:54 To: adrian@olddog.co.uk Cc: antitrust-policy@ietf.org; Lars Eggert <lars@eggert.org> Subject: Re: [antitrust-policy] New Version Notification for draft-halpern-gendispatch-antitrust-08.txt Hi Adrian On 1 Mar 2024, at 15:24, Adrian Farrel <adrian@olddog.co.uk <mailto:adrian@olddog.co.uk> > wrote: Hey Jay, I think a key piece of advice is missing (yes, I see 4.2). It may be too obvious, but surely you should be saying "individuals are recommended to seek legal advice" somewhere highly prominent. For example, lifting and tweaking a paragraph from BCP79 and placing it at the end of Section 1... This document is not intended as legal advice. Readers are advised to consult their own legal advisors if they would like a legal interpretation of antitrust laws, the risks, and their responsibilities. Section 4.2 is intended to be exactly that so I’m confused as to why you would apparently dismiss it and then ask for the same thing? Is it just a matter of where it goes or is the language in 4.2 insufficient or do you think we need both 4.2 and the new text above? Did I dismiss it? That's what I took from "(yes, I see 4.2)" with no further mention of it, but from your response it seems as if that was not the intent so I misunderstood. Maybe it is just the prominence. I wrote my comment having read the Abstract, Introduction, and Section 2. I was starting on Section 3 when the thought occurred. Thanks - I will talk to my co-author. On the earlier question of referencing the COIs and whistleblower service, I have conferred with colleagues who note that all the COI policies are easy to find on the web site, (except for one, which we are investigating), and that the whistleblower service is the first result when searching for " IETF whistleblower". Given that, there’s a strong preference not to have links in the RFC that need to be maintained, or for us to maintain a page at a stable link that then links to these COIs. However, if you think the effort would be worth it then please let me know. thanks again Jay -- Jay Daley IETF Executive Director exec-director@ietf.org <mailto:exec-director@ietf.org>
- [antitrust-policy] Fwd: New Version Notification … Jay Daley
- Re: [antitrust-policy] New Version Notification f… Jay Daley
- Re: [antitrust-policy] Fwd: New Version Notificat… Adrian Farrel
- Re: [antitrust-policy] New Version Notification f… Adrian Farrel
- Re: [antitrust-policy] New Version Notification f… Jay Daley
- Re: [antitrust-policy] New Version Notification f… Adrian Farrel
- Re: [antitrust-policy] New Version Notification f… Adrian Farrel
- Re: [antitrust-policy] New Version Notification f… Adrian Farrel
- Re: [antitrust-policy] New Version Notification f… Salz, Rich
- Re: [antitrust-policy] Fwd: New Version Notificat… Black, David
- Re: [antitrust-policy] New Version Notification f… Jay Daley
- Re: [antitrust-policy] New Version Notification f… Black, David
- Re: [antitrust-policy] New Version Notification f… Jay Daley
- Re: [antitrust-policy] New Version Notification f… Black, David
- Re: [antitrust-policy] New Version Notification f… Stephan Wenger
- Re: [antitrust-policy] New Version Notification f… Jay Daley
- Re: [antitrust-policy] New Version Notification f… Christian Huitema