IETF Logo Mail Archive

Re: [rfc-i] [Rfced-future] Call for nominations: RFC Editor Future Development Program Chair(s)

Eliot Lear <lear@cisco.com> Thu, 16 April 2020 20:35 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82BBB3A105B; Thu, 16 Apr 2020 13:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.452
X-Spam-Level:
X-Spam-Status: No, score=-2.452 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 PIwlBkx3Qh4U; Thu, 16 Apr 2020 13:35:18 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 358493A1027; Thu, 16 Apr 2020 13:35:18 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 681DFF4071D; Thu, 16 Apr 2020 13:34:57 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 9E2A4F4071D for <rfc-interest@rfc-editor.org>; Thu, 16 Apr 2020 13:34:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bN-lLLG6YBKw for <rfc-interest@rfc-editor.org>; Thu, 16 Apr 2020 13:34:53 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) by rfc-editor.org (Postfix) with ESMTPS id F1FD5F4071C for <rfc-interest@rfc-editor.org>; Thu, 16 Apr 2020 13:34:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2307; q=dns/txt; s=iport; t=1587069313; x=1588278913; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=Gf/g25TNWBVoTTIHwNSiR0kkRhLlJSRjQY14MD8B87Y=; b=FjYNPKbe/Gv/2qjDGlPPxaPbsjgyBRYnkJ5O9OCjyixlYB0e48zmIIXs 9vExKr8YoY6nGA5Gqyg1WBbAElP4r4VAWBVRz/GutyRZfiyBCUOFnX8Zh 9qPIAsvrwjFlMN0GiFExzikLrgCq0NMRXIYgThfKyFvbhx8uoc/hWZU50 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AcAADgwJhe/xbLJq1mGwEBAQEBAQEFAQEBEQEBAwMBAQGBaQQBAQELAYMUVSASKo0eh2IliXKPYRSBZwoBAQEMAQEYDQoEAQGERAKCMDYHDgIDAQELAQEFAQEBAgEFBG2FVgyFcQEBAQECAQEBGx00CwULCxguIQYwBhMUgxIBgksDDiAPrxeCJ4VPgkcNghwGgTgBjE+CAIE4DBCBT34+gh5JAYExARIBIYNEgi0EsSFJgk6CZpA2hEMdglSISoRAjFebX40ngz4CBAYFAhWBWQIwZ3AzGggbFTsqAYIKATM+EhgNV5E5iE+FQz8DMAKNAS2CFgEB
X-IronPort-AV: E=Sophos;i="5.72,392,1580774400"; d="scan'208";a="25334227"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 16 Apr 2020 20:35:09 +0000
Received: from [10.61.247.32] ([10.61.247.32]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 03GKZ8ce022385 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 16 Apr 2020 20:35:09 GMT
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Eliot Lear <lear@cisco.com>
In-Reply-To: <34dce524-37c5-3004-ae06-d9dcc7e845d1@gmail.com>
Date: Thu, 16 Apr 2020 22:35:08 +0200
Message-Id: <A6C1A783-967B-47B6-8922-EABF84994CEB@cisco.com>
References: <158705677668.7047.15450219213491357501@ietfa.amsl.com> <34dce524-37c5-3004-ae06-d9dcc7e845d1@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-Outbound-SMTP-Client: 10.61.247.32, [10.61.247.32]
X-Outbound-Node: aer-core-4.cisco.com
Subject: Re: [rfc-i] [Rfced-future] Call for nominations: RFC Editor Future Development Program Chair(s)
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: rfced-future@iab.org, rfc-interest@rfc-editor.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

+1.

> On 16 Apr 2020, at 22:33, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> Speaking as one who is definitely not going to volunteer for this,
> for several reasons, I really want to encourage everybody who cares
> about the RFC series to consider doing so. There were good candidates
> the last time, but mainly from the "old guard". This time, it would
> be great to have some new and different names too.
> 
> Regards
>   Brian Carpenter
> 
> On 17-Apr-20 05:06, IAB Executive Administrative Manager wrote:
>> As previously discussed, the IAB is seeking an additional chair or 
>> chairs for the RFC Editor Future Development Program [1].
>> 
>> This program is modeled on an IETF working group, and will use its 
>> mailing list (rfced-future@iab.org) to develop and validate consensus 
>> among the participants. 
>> 
>> The program currently has one chair, Eliot Lear. The current IAB has 
>> received significant feedback from the community that a second chair 
>> needs to be selected, and the IAB is eager to fill that position with a 
>> great candidate as soon as is practical. The IAB is now seeking at least 
>> one additional chair from outside the IAB to join Eliot. Together, these 
>> chairs will set the detailed agenda, manage the program, and call 
>> consensus among the participants. The program also has two liaisons from 
>> the IAB to assist with logistical matters, Wes Hardaker and Jared Mauch.
>> 
>> If you are interested in serving in this role, please send a short email 
>> message to iab-chair@iab.org and execd@iab.org with your motivation and 
>> information concerning your familiarity with IETF working groups or 
>> similar processes. The deadline for volunteering is Tuesday, 2020-05-12 
>> at 2359 UTC. The IAB will then solicit public comments on the candidates 
>> before making a decision.
>> 
>> Best regards,
>> Cindy Morgan, for the IAB
>> 
>> [1] <https://www.iab.org/activities/programs/rfc-editor-future-development-program/>
>> 
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email