[Rfced-future] Upcoming meeting: aiming towards approaches

Eliot Lear <lear@cisco.com> Wed, 08 July 2020 19:02 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 548A63A00AE for <rfced-future@ietfa.amsl.com>; Wed, 8 Jul 2020 12:02:49 -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 P6Cl8590DI_x for <rfced-future@ietfa.amsl.com>; Wed, 8 Jul 2020 12:02:48 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4D033A003D for <rfced-future@iab.org>; Wed, 8 Jul 2020 12:02:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3670; q=dns/txt; s=iport; t=1594234967; x=1595444567; h=from:mime-version:subject:message-id:date:cc:to; bh=CQ99jwbfMW1kSEjbf78GLsnIb3PaNomyvL1TtHh7iYE=; b=m921DTJJWCf5fg5IjHC7TItff5upMHRrh5BVpOlYUr0C44CiAJjj1iFO lSgulWMHESRQLFpfFe00tWIoDCRH3YTiqW/eno/QBhurKgy5dSADkYb4E LebpPyh58MZYf0v2TZ2qNOxhMKsHyh09INgW4NNKF1qj60daeMMU8XOee 4=;
X-IPAS-Result: A0B1BABdFwZf/xbLJq1gHQEBAQEJARIBBQUBggqCKoFDASAShF+JAZwLhi2BaQsBAQEMAQEvBAEBhE2CFyU4EwIDAQEBAwIDAQEBAQUBAQECAQYEbYVnhhlIDh8+AoEGgxKCfapldoEyhVGEfYE4jQmCAIE4HIMLhAMRdoJJM4ItBLUNgmYEgwKWRAMdnyKsbINRAgQGBQIVgWojgVczGggbFTsqAYI/PRIZDZxnPwNnAgYBBwEBAwmNZYJGAQE
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="5.75,328,1589241600"; d="scan'208,217"; a="25319033"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 08 Jul 2020 19:02:43 +0000
Received: from dhcp-10-61-98-29.cisco.com (dhcp-10-61-98-29.cisco.com [10.61.98.29]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 068J2hNH005986 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 8 Jul 2020 19:02:43 GMT
From: Eliot Lear <lear@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0DEE2393-94D6-45F7-862C-19AE0512146D"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Message-Id: <81D8F035-A1C3-41BC-A77C-10CA731A2B5B@cisco.com>
Date: Wed, 08 Jul 2020 21:02:42 +0200
Cc: Brian Rosen <br@brianrosen.net>
To: rfced-future@iab.org
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-Outbound-SMTP-Client: 10.61.98.29, dhcp-10-61-98-29.cisco.com
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/sO2YHwvYqynHUI_NWlPWS2alw1E>
Subject: [Rfced-future] Upcoming meeting: aiming towards approaches
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: Wed, 08 Jul 2020 19:02:49 -0000

Dear colleagues:

The chairs have been tracking all conversations that have been taking place, and the contributions have been made.  Thank you all for providing your views to each other, and for responding to Brian’s earlier questions.  As you might imagine, we have been reviewing your input and refining based on your comments and other contributions.

For IETF 108, we would like to test where consensus is on various key points.  Refining our earlier list of questions based on the list discussion, we now think we should ask:
Is there a person other than Jay who manages the RPC?
Would people like to see a board, a standing working group/program, or both?
Is there a leader who can run a community who is expert in publishing?
There are obviously follow-up questions to each of these.  We are not calling these questions now but are asking merely if you agree that these are the right questions to ask.  We do not want to ask too many questions, so that there is at least a little bit of time for discussion of points arising from the answers.

Focusing dialog on the list to address whether we have the questions right rather answering them would be helpful, as we will have limited “in person” time at the meeting.

Brian and Eliot