Re: [tlp-interest] Notice of Proposed Amendment to IETF Trust Bylaws

Russ Housley <housley@vigilsec.com> Mon, 20 November 2023 21:53 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: tlp-interest@ietfa.amsl.com
Delivered-To: tlp-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8098CC15C293 for <tlp-interest@ietfa.amsl.com>; Mon, 20 Nov 2023 13:53:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 Qixe13ekbXXm for <tlp-interest@ietfa.amsl.com>; Mon, 20 Nov 2023 13:53:47 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 66662C15C28F for <tlp-interest@ietf.org>; Mon, 20 Nov 2023 13:53:47 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 48F47170BFE; Mon, 20 Nov 2023 16:53:46 -0500 (EST)
Received: from smtpclient.apple (unknown [96.241.2.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 2A80E170DFC; Mon, 20 Nov 2023 16:53:46 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <b86a8033-a0a0-3c91-e2f0-12d62a97c559@gmail.com>
Date: Mon, 20 Nov 2023 16:53:35 -0500
Cc: tlp-interest@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <75B6EA5F-AE2D-4491-95BF-F0D3447EBB98@vigilsec.com>
References: <169952314836.23596.279260214413370014@ietfa.amsl.com> <09BD494E-6FDF-4385-B039-2B77A542B721@vigilsec.com> <b86a8033-a0a0-3c91-e2f0-12d62a97c559@gmail.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3731.700.6)
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/tlp-interest/E_bHs76jhwGQcKGB1KmyVKpckuU>
Subject: Re: [tlp-interest] Notice of Proposed Amendment to IETF Trust Bylaws
X-BeenThere: tlp-interest@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion of proposed revisions to the Trust Legal Provisions <tlp-interest.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tlp-interest>, <mailto:tlp-interest-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tlp-interest/>
List-Post: <mailto:tlp-interest@ietf.org>
List-Help: <mailto:tlp-interest-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tlp-interest>, <mailto:tlp-interest-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Nov 2023 21:53:49 -0000

Brian:

I did not make this change, I am just concerned that this definition will lead to a bunch of by-law adjustments over the years.  Like you, I think the original definition was better.

Russ

> On Nov 20, 2023, at 2:25 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> On 21-Nov-23 08:07, Russ Housley wrote:
>> I have a minor concern with this definition:
>> “IETF” means the Internet Engineering Task Force as constituted in accordance with
>> their Best Current Practice (BCP) documents 9, 10, and 101 (BCP 9, BCP 10, BCP 101) and any
>> duly approved successor documents thereto.
> 
> That seems like unneccesary verbiage to me. The original Trust agreement simply said:
> 
> “IETF” means the Internet Engineering Task Force, which is dedicated to the development and publication of Internet standards, specifications and related documents on a charitable, non-profit basis.
> 
> Why isn't that enough?
> 
>     Brian
> 
>> If an additional BCP is written and approve that is not a successor to one of these BCPs, will the by-laws need to be amended to add it to this list?  Is there wording that would avoid that step?
>> Russ
>>> On Nov 9, 2023, at 4:45 AM, The IETF Trust <ietf-trust@ietf.org> wrote:
>>> 
>>> As presented at the IETF 118 Plenary by the IETF Trust,  the Trustees intend to add a 60-day notice before adoption restriction to amendments to the Trust's bylaws.
>>> 
>>> This 60-day notice is a new restriction not included in the original IETF Trust Agreement and is intended as a safeguard against bylaw amendments being made without awareness by the bodies that appoint the 5 IETF Trustee -  the IESG, IETF NOMCOM, ISOC Board of Trustees, and announced more broadly through the IETF Announcements list.
>>> 
>>> This is also being announced on the IETF Trust's web site.
>>>    https://trustee.ietf.org/about/announcements/
>>> 
>>> ---
>>> 
>>> Notice of proposed Bylaw amendments on behalf of the IETF Trustees and the IETF Intellectual Property Management Corporation (IPMC).
>>> 
>>> A proposed amended IPMC Bylaws have been published by the IETF Trustees that would make the following changes:
>>> 
>>>   1. Introduce a 60-day notice of proposed amended IPMC Corporate Bylaws before a vote to adopt
>>> 
>>>    2. Addition of definitions of the IETF and IETF LLC to the Front Matter
>>> 
>>> There are no organizational or structural changes to the IMPC in the amended bylaws.
>>> 
>>> Details on the proposed amended bylaws including a redlined version are available on the IETF Trust web site at:
>>>  https://trustee.ietf.org/about/announcements/proposed-ipmc-bylaw-amendments/
>>> 
>>> -- 
>>> 
>>> Keeping with the spirit of the 60-day notice period before adoption, the IETF Trustees have decided to apply it to this proposal and adoption will not occur before 60 days after November 8, 2023.
>>> 
>>> Given that no structural or organizational changes are being made, this is a notice only and not a broader consultation.
>>>   Comments may be directed to TLP-Interest@ietf.org.
>>> 
>>> Thanks,
>>> Glenn Deen,
>>> IETF Trust Chair, IETF Intellectual Property Management Corporation President
>>> 
>>> _______________________________________________
>>> IETF-Announce mailing list
>>> IETF-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>> _______________________________________________
>> tlp-interest mailing list
>> tlp-interest@ietf.org
>> https://www.ietf.org/mailman/listinfo/tlp-interest