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

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 20 November 2023 19:25 UTC

Return-Path: <brian.e.carpenter@gmail.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 0DD9BC1522C2 for <tlp-interest@ietfa.amsl.com>; Mon, 20 Nov 2023 11:25:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.196
X-Spam-Level:
X-Spam-Status: No, score=-2.196 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.091, 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=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 ZFPFJBaNF86z for <tlp-interest@ietfa.amsl.com>; Mon, 20 Nov 2023 11:25:34 -0800 (PST)
Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (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 A1D5AC1522B9 for <tlp-interest@ietf.org>; Mon, 20 Nov 2023 11:25:34 -0800 (PST)
Received: by mail-pf1-x435.google.com with SMTP id d2e1a72fcca58-6b1d1099a84so4541422b3a.1 for <tlp-interest@ietf.org>; Mon, 20 Nov 2023 11:25:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700508334; x=1701113134; darn=ietf.org; 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=RHciQLAZdCQSomczTncNh+Y6/eumI2mMnYl0KvKCnJY=; b=j2QWKHleUv3fcieIQl3O9hOJJ7XgzQOcU4+tywV/lOJ7skgFFhkVj8W/vqJTI4U6Xj pm/Qu7y9/lv/YgNIWrBjJoCXdFbMIbcNFwvnVs96P7YC25Stg1lLroMK3NltOda4J8mm hNSN5XyqL2flnACQ4sxajy92H+l3cVF7hq2O+FdpTWozXb0tY85WO63AksuClBYbFGdm PuF00/myINI/L8uj2kMH071yyUPEPl6GEQTRqQqAUorFYXWig3/sNKU0BKhP4x7N2B7b z/AUPO0b1voYQHM55YbdWOJHYAS03p7ztLiM2jByX9At9y78MuAeQbdcmwzqqWsCarZQ P/8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700508334; x=1701113134; 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=RHciQLAZdCQSomczTncNh+Y6/eumI2mMnYl0KvKCnJY=; b=bh/YeiIb4HMU/E6PFchCAolZQhrcfXnREpGhL/he+eRlYGAy1RTa0hdiKjFQSYNlYJ tYipzwXGJbaCjDbkjv08wlXMK2OtZbEPlKywLvEDNYnoMLqkcnxs4GypxyU3NwQUKQiU 7Yo9BxChRZ5UE2OGapI0Q78hymgKTTB4lH4klLamTM3Lr/UZUJZcPV41NWxRkxsABXC0 oWA4vnNDOPSVyDuDAtk0WDpMR1JTrjnwkADo79VvmRTgLU/fiBiJwLndVZ9RymAkDhx6 IhFCTNbNcby9WgXLzH7UgkV2QKQ4D7F0Qps8ZFMmc70OzQrpT1waiD/S+hXa1DVWTfZV xdzA==
X-Gm-Message-State: AOJu0YzyCY5njXdLbNjo0/XRLhV8GCIhbv86bhUuw9ZqwHFXoQWcSw6R hpWf8DfCcGzcfw1zILCIrVyBxOca4qCvfQ==
X-Google-Smtp-Source: AGHT+IHBiooC8KQFyb5d24fhEjYMAjzYjf5gSVQunEsGIY4m8oawQRBTTqy3ptFg+qo5LVFVxPg0JQ==
X-Received: by 2002:a05:6a20:c1a8:b0:189:c99a:7d7a with SMTP id bg40-20020a056a20c1a800b00189c99a7d7amr11368925pzb.29.1700508333995; Mon, 20 Nov 2023 11:25:33 -0800 (PST)
Received: from ?IPV6:2404:4400:541d:a600:44b7:2c2e:2bc6:8707? ([2404:4400:541d:a600:44b7:2c2e:2bc6:8707]) by smtp.gmail.com with ESMTPSA id a8-20020a62bd08000000b006c2d5a31ab9sm6451625pff.81.2023.11.20.11.25.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 20 Nov 2023 11:25:33 -0800 (PST)
Message-ID: <b86a8033-a0a0-3c91-e2f0-12d62a97c559@gmail.com>
Date: Tue, 21 Nov 2023 08:25:29 +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: Russ Housley <housley@vigilsec.com>, tlp-interest@ietf.org
References: <169952314836.23596.279260214413370014@ietfa.amsl.com> <09BD494E-6FDF-4385-B039-2B77A542B721@vigilsec.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <09BD494E-6FDF-4385-B039-2B77A542B721@vigilsec.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/tlp-interest/TMuFyIslkcgwUy_rpKYQutErU8Y>
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 19:25:39 -0000

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