RE: I-D Action: draft-rsalz-termlimits-00.txt

Vasilenko Eduard <vasilenko.eduard@huawei.com> Thu, 21 October 2021 08:48 UTC

Return-Path: <vasilenko.eduard@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1B853A125C for <ietf@ietfa.amsl.com>; Thu, 21 Oct 2021 01:48:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zhDDTucUtHVe for <ietf@ietfa.amsl.com>; Thu, 21 Oct 2021 01:47:57 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E062E3A1235 for <ietf@ietf.org>; Thu, 21 Oct 2021 01:47:56 -0700 (PDT)
Received: from fraeml702-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4HZgxs0Fkdz67nWm; Thu, 21 Oct 2021 16:44:01 +0800 (CST)
Received: from mscpeml100002.china.huawei.com (7.188.26.75) by fraeml702-chm.china.huawei.com (10.206.15.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.15; Thu, 21 Oct 2021 10:47:53 +0200
Received: from mscpeml500001.china.huawei.com (7.188.26.142) by mscpeml100002.china.huawei.com (7.188.26.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.15; Thu, 21 Oct 2021 11:47:52 +0300
Received: from mscpeml500001.china.huawei.com ([7.188.26.142]) by mscpeml500001.china.huawei.com ([7.188.26.142]) with mapi id 15.01.2308.015; Thu, 21 Oct 2021 11:47:52 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF discussion list <ietf@ietf.org>
Subject: RE: I-D Action: draft-rsalz-termlimits-00.txt
Thread-Topic: I-D Action: draft-rsalz-termlimits-00.txt
Thread-Index: AQHXxelkLuOoaFBvtEaVhOfUtTOR2qvdHaag
Date: Thu, 21 Oct 2021 08:47:52 +0000
Message-ID: <e84d603cbb9d420e8bfbf242a14b135b@huawei.com>
References: <163474046003.5194.1851617977740027365@ietfa.amsl.com> <2a65cc6e-3a39-d209-491f-f4ad67cca151@gmail.com>
In-Reply-To: <2a65cc6e-3a39-d209-491f-f4ad67cca151@gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.81.209.125]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tglRyIhl34XaoDvLAABC7-OY8yk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2021 08:48:02 -0000

I do not believe that it is right: "they are ineligible to directly serve for another term in any NomCom-chosen position".
"Any" is too strong filtering.
The right one should be: "After a person has served two consecutive terms in *particular* NomCom-chosen position, they are ineligible to directly serve for another term in *this* position; there must be a gap of at least one year. "

Humans are capable to establish social connections then leveraging them for personal goals.
It is human nature - nothing could be done about it. Connections should be cut periodically.
IETF is to serve the public good, ideally anonymously. Our beneficiary is anonymous, right? He/she is somewhere.
I know that many people would come and say that personal connections could help to solve problems,
But it has more good than bad only inside a corporate environment where common goals should exist.
IETF now is mostly the battlefield between persons and sometimes companies for egoistic goals.
Cutting some personal connections could improve IETF culture a little.
Because if not change people for years then sooner or later the question would come for the inheritance of the position.

The "bronze statue" in power is not the ideal boss in such a controversial environment.
These all are very similar to the boss in any position for the big country. They have 2 term restrictions in many cases.
Countries where they do not have (or do not obey) such restrictions we call ...
Ed/
-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Brian E Carpenter
Sent: Wednesday, October 20, 2021 10:33 PM
To: IETF discussion list <ietf@ietf.org>
Subject: Re: I-D Action: draft-rsalz-termlimits-00.txt

Well, this is a bad idea that was repeatedly rejected in the past.

Why? Because it's always hard to fill all the positions, and this would make it harder.

If someone is incompetent, NomCom will not reappoint them even once, let alone twice.

We all agree that ossification is unwelcome, but artificial turnover is not the way to avoid that.

Regards
   Brian Carpenter

On 21-Oct-21 03:34, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>         Title           : Term limits for IETF Leadership Positions
>         Author          : Rich Salz
> 	Filename        : draft-rsalz-termlimits-00.txt
> 	Pages           : 3
> 	Date            : 2021-10-20
> 
> Abstract:
>    This document says that nobody can be picked by NomCom for a position
>    more than two consecutive terms.
> 
>    It obsoletes some other documents, which ones are TBD.
> 
> Discussion Venues
> 
>    This note is to be removed before publishing as an RFC.
> 
>    Source for this draft and an issue tracker can be found at
>    https://github.com/richsalz/draft-rsalz-termlimits.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-rsalz-termlimits/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-rsalz-termlimits-00.html
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or 
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>