Re: Eliot Lear to Serve as RFC Editor Future Development Program Chair

Eliot Lear <lear@cisco.com> Sat, 28 March 2020 11:06 UTC

Return-Path: <lear@cisco.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 66D473A078F for <ietf@ietfa.amsl.com>; Sat, 28 Mar 2020 04:06:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Level:
X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 5kvs2NW-aQYn for <ietf@ietfa.amsl.com>; Sat, 28 Mar 2020 04:06:54 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93CBD3A0816 for <ietf@ietf.org>; Sat, 28 Mar 2020 04:06:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5847; q=dns/txt; s=iport; t=1585393613; x=1586603213; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=Tz1TQfmOjsaPSEogEw8oinGfX9YwDZPJAg4/A/d1SHg=; b=XhjZJf0LswOrcuil/4WvRPNpOPSUxQrkkgobKkPeUVXCNgdMoPZwOK6H SEpR7pU5g7TqQ/mig5nvCAznKCeCKsvRWDUrAAdvmN7s/mfoo3IW9EL2k 7OiKUby5ZhNUnCkF1tWb6tL1RTWgqZEb/WASSeyGFe6HcT/Tewwk20078 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DoAgBOL39e/xbLJq1mHAEBAQEBBwEBEQEEBAEBgXuEChIqhBqJAogQiW2JUIgLCgEBAQwBAS8EAQGERAKCVTgTAgMBAQsBAQUBAQECAQUEbYVihXABAQEBAgEjVgULCwQUJwMCAiElEQYTFIMSgkwDDiCqL3WBMoVLgwANgiCBOIxLggCBOCCBT0kHLj6CHoF6bIJcMoIsBJcUmQxFgkaCVoobhWaEPh2bbJpnjQGDNAIEBgUCFYFpIoFYMxoIGxU7KgGCQT4SGA2cZkADMAKPEQEB
X-IronPort-AV: E=Sophos; i="5.72,316,1580774400"; d="scan'208,217"; a="24839383"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 28 Mar 2020 11:06:51 +0000
Received: from ams3-vpn-dhcp2555.cisco.com (ams3-vpn-dhcp2555.cisco.com [10.61.73.251]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 02SB6oHN027376 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 28 Mar 2020 11:06:51 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <7915FEDA-1B70-4F51-AC7E-9978086B5182@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_67378DE4-E8E1-4A9B-BCE4-BB0514B8CD07"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: Eliot Lear to Serve as RFC Editor Future Development Program Chair
Date: Sat, 28 Mar 2020 12:06:50 +0100
In-Reply-To: <b01bc927-e9e3-0b43-0247-aa4ebfc098e4@gmail.com>
Cc: The IETF List <ietf@ietf.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <158515861056.31362.1577145055370523251@ietfa.amsl.com> <06f0ef99-728e-1b41-0596-7b7286c29ead@comcast.net> <CA+9kkMBTb=Z2C5VJ1LQ6JoN0hB8OnmSdebkLHFhG+O-9F_Tv7A@mail.gmail.com> <2375d191-dd72-3e09-6417-5bcae5ba1d4b@comcast.net> <C6F6A4AB-3515-4E11-961B-66B87EDA995A@piuha.net> <b01bc927-e9e3-0b43-0247-aa4ebfc098e4@gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-Outbound-SMTP-Client: 10.61.73.251, ams3-vpn-dhcp2555.cisco.com
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Uxd5xm28P0Q_e12dqyOs80zQ9rY>
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: Sat, 28 Mar 2020 11:06:56 -0000

[Sorry- I meant to send this publicly earlier].

Hi Brian,

> On 28 Mar 2020, at 01:43, Brian E Carpenter <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
> 
> Jari, and the current IAB (all of whom are, I presume, on this list),
> 
> Thanks for the clarification. But I think it's *essential* to have co-chairs in this case, since any plausible chair for this topic is bound to have some definite opinions and that makes fair chairing very difficult. This has nothing to do with the choice of Eliot.

I agree it is important to have a co-chair, but not for that reason.  We should have another chair for institutional reasons (like if I get sick; not an unheard of possibility, given Switzerland’s circumstances).  I also want the IAB to have the opportunity to easily replace me if they decide they don’t like how I am performing.  But my position is that the board should find the right second chair, and not just fill a seat.  If the right person comes along tomorrow, great.  If it takes a little time, let it.  You’ll prefer the results.

Do I have opinions about the role of RFC Editor?  Of course I do. I am a longstanding member of this community, I’ve served on the IAB, and as you will see from last year’s discussion, my opinions are on record.  Are they strongly held?   As part of this process I had to ask myself that very question, and delayed putting my name into the hat so I could search how I felt.

How the RFC Editor role is structured is not something about which I have strong opinions.  In fact I strongly believe that a great many others such as yourself have far better grounded opinions on the role than I do!  I have faith that the participants in the effort that will kick off on Monday will conscientiously draw out the issues that need to be addressed, decide which issues don’t need to be addressed, come up with approaches for the ones that do, and come to consensus.

But I do have an agenda.  It is to see that both this process and its subsequent implementation be a positive experiences for the community and those who work for us.  That’s all.

Eliot