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

Toerless Eckert <tte@cs.fau.de> Mon, 13 November 2023 06:36 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 C7806C15106F for <tlp-interest@ietfa.amsl.com>; Sun, 12 Nov 2023 22:36:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Level:
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, 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=no 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 XR0oNAJfn0tt for <tlp-interest@ietfa.amsl.com>; Sun, 12 Nov 2023 22:36:48 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (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 99E29C15106C for <tlp-interest@ietf.org>; Sun, 12 Nov 2023 22:36:46 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4STKTP0s99znkS5 for <tlp-interest@ietf.org>; Mon, 13 Nov 2023 07:36:41 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4STKTN717VzklyT; Mon, 13 Nov 2023 07:36:40 +0100 (CET)
Date: Mon, 13 Nov 2023 07:36:40 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: tlp-interest@ietf.org
Message-ID: <ZVHD-B0vNU5yKHf4@faui48e.informatik.uni-erlangen.de>
References: <169952314836.23596.279260214413370014@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <169952314836.23596.279260214413370014@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tlp-interest/yfKgxHs0EADT3AZGIuVPM-JMXag>
X-Mailman-Approved-At: Sat, 18 Nov 2023 11:54:20 -0800
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, 13 Nov 2023 06:36:52 -0000

nit on IPMC:

Some TLA (FLA? ;-) overload. Maybe use IIPMC unless you explicitly prefix it with IETF,
which you for example did not do in your text.

https://en.wikipedia.org/wiki/IPMC. I of course confused your article with the fourth abbreviation,
but abbreviations 2 and 3 are also known to members of our IETF community.

Cheeers
    Toerless


On Thu, Nov 09, 2023 at 01:45:48AM -0800, The IETF Trust 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

-- 
---
tte@cs.fau.de