Re: [Rfced-future] Welcome to the RFC Editor Future Development Program

Eliot Lear <lear@cisco.com> Mon, 30 March 2020 17:07 UTC

Return-Path: <lear@cisco.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 465313A060A for <rfced-future@ietfa.amsl.com>; Mon, 30 Mar 2020 10:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.7
X-Spam-Level:
X-Spam-Status: No, score=-7.7 tagged_above=-999 required=5 tests=[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 1Axva8oGk-B5 for <rfced-future@ietfa.amsl.com>; Mon, 30 Mar 2020 10:07:40 -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 63AE23A047F for <rfced-future@iab.org>; Mon, 30 Mar 2020 10:07:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10931; q=dns/txt; s=iport; t=1585588060; x=1586797660; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=Q5jglN541Akjqrcs/VvD1IRp6Fe66wob0XrnejTVdZs=; b=AXchu1VnZ1YHo2zAgRc3WA6kjPoVRGWUfI+QGHB9CxRkqs23aJ72moiI /XopLXyvTxop55LPGWIsZZgYhTy+ODpWLXdH4SzelOd6w1uQ4vLDOLBIK 2MsxJuBJWD8QkETHd4QJiuiJnu7WcskQ11QimPGfkVmxBamvluCLj/IGI 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CDAAAIJ4Je/xbLJq1mGgEBAQEBAQEBAQMBAQEBEQEBAQICAQEBAYF7gSWCRCESKoQaiQKIDpM9iAsKAQEBDAEBLwQBAYREAoJWOBMCAwEBCwEBBQEBAQIBBQRthWKFcAEBAQECASNWBQsLGCoCAlcGE4Mmgl0grFR1gTKFS4RrgTiMS4IAgTgggh8uPoQlgzsygiwEihemToJGglaPIYUeHYJMiDCEModnhFenaIM0AgQGBQIVgWkigVgzGggbFTsqAYJBPhIYDVicDz8DMIxXgWNgAQE
X-IronPort-AV: E=Sophos; i="5.72,325,1580774400"; d="scan'208,217"; a="24896251"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 30 Mar 2020 17:07:38 +0000
Received: from [10.61.237.69] ([10.61.237.69]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 02UH7b1P017237 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 30 Mar 2020 17:07:38 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <73C27FFD-BD81-4CF3-9D9D-845DE9544A36@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C34BB1C4-0970-4C02-8783-93F0B4774542"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Mon, 30 Mar 2020 19:07:37 +0200
In-Reply-To: <0E6D83F8D11D8C1B9B7237B7@PSB>
Cc: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, "Andrew G. Malis" <agmalis@gmail.com>, rfced-future@iab.org
To: John C Klensin <john-ietf@jck.com>
References: <97B63B78-0D49-4007-B8A2-101FB7849C0F@cisco.com> <CAA=duU0_pr_56HTR5vZg+AK981rkvGrMGFFi-UHgW4L=6=6mwg@mail.gmail.com> <D6A290EE-72E5-46A7-BA25-085CC2AAE35C@cisco.com> <0E6D83F8D11D8C1B9B7237B7@PSB>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-Outbound-SMTP-Client: 10.61.237.69, [10.61.237.69]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/REruSw05J9tonA6RRi4Uf4Puvjc>
Subject: Re: [Rfced-future] Welcome to the RFC Editor Future Development Program
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Mar 2020 17:07:43 -0000

Hi John,

Thanks for your comments.  Please see below.

> On 30 Mar 2020, at 18:07, John C Klensin <john-ietf@jck.com> wrote:
> 
> On a slightly different topic, the issues associated with the
> 2020-2021 Nomcom and what, if any, changes are needed to the
> eligibility requirements for the future are still very active on
> the IETF and eligibility-discuss lists (in addition to many
> other issues, of course).  For those of us who can only put in a
> limited number of hours a week on IETF-related work, paying
> careful attention to both sets of threads might be nearly
> impossible.  Much as I hate to see this process delayed, would
> it be sensible to postpone active discussions here for a week or
> two in the hope that the other ones will settle down?


I appreciate your desire to take the time necessary to understand others’ views, and to contribute in a meaningful way, and that you have time pressures, as I am sure we all do.  Thank you for having chimed in with your views; it is now for others to do so.  If this list volume really becomes a problem, please do let me know.

Eliot