Re: [Rfced-future] RFC Editors Future Program @ IETF 108

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 17 July 2020 05:17 UTC

Return-Path: <brian.e.carpenter@gmail.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 EFB733A1238 for <rfced-future@ietfa.amsl.com>; Thu, 16 Jul 2020 22:17:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 mYtWhzJgJqXD for <rfced-future@ietfa.amsl.com>; Thu, 16 Jul 2020 22:17:00 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1FEC3A1239 for <rfced-future@iab.org>; Thu, 16 Jul 2020 22:17:00 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id m16so4953205pls.5 for <rfced-future@iab.org>; Thu, 16 Jul 2020 22:17:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=ikl6YZiqSmIzRkpdVXJzAOi0grs4Ta1dNXPUmK6VWgg=; b=UZFV01jm2mlprZBcf3rfdDXEBsF4nmSAooPHw9UAOKC4006yZlkFShlcwVMeIxPnmF 8Eb6xDzDPFumtJ1UltDBFLVowHXPlHC5fBbCgZIfRtYityvZxWm0X3k6UoyKrcPylVZp ol/eCDXJRWGNekZx44ZGZVMSESjTk4TLzfVIn8iSOOO0mNopDh+CBaQb32hhrAgYFKbA UCW4kk3mtkq2iz+Ah3W0DtRLlP1E62mH2mXE9oXhE4AE08OPaD7puEJ5cmw3VeXldqlg mM096Jcuswm5nSspVYgnDY3MK9D9jHkRyI+Kfk6LBmmcSgIJ1h811ha+RL//ABja1KaP IjLQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ikl6YZiqSmIzRkpdVXJzAOi0grs4Ta1dNXPUmK6VWgg=; b=rVU5iVxWBNsBXCNcH79QhC/fXnEf1kjGHCncANgFKEas/qdFeVz4cki2CI8+y+Dq4m Jk0MVWGJyKchKdXZsUU3yyHdjDPPsgwxTjaCNd3+5hTpzrSdvh5G1PCFiDydur7diOT0 Vfzu6I/QFOdYrctoOBy/ZIxFKlv1k1lQIIBhz8n7mlLKNraC/9iz34Esp0NN4PLlXgsE S1sjAHQgqoSAIn8jwxJbrDTASxFYElhUDw2+EtI4ZB0gnt8Cjy3wTSShZwdPxenNMF4q NZteq2Y6PlLfYiJrHGDQHTrThtCRZQhqSxQqGH1YSd91H2ZR7GwiOrHcFSzb6K592pHR 55oQ==
X-Gm-Message-State: AOAM5332GIfUim33hPkbrJWK1avh3FVFJKL2TSp9U+KrmH/cPbL/RSCR Zv+D/7HHTWcV1+8fgcr5GKSHfYTh
X-Google-Smtp-Source: ABdhPJw52tGZQbpvleFbH70q83ZK8P/OxrJZbIUmGy57+bq/ud2VtDGDKfJWrUZv2pDUNlwQro2HwQ==
X-Received: by 2002:a17:902:262:: with SMTP id 89mr5842557plc.31.1594963019888; Thu, 16 Jul 2020 22:16:59 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.132.13]) by smtp.gmail.com with ESMTPSA id u26sm6385184pfn.54.2020.07.16.22.16.57 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Jul 2020 22:16:59 -0700 (PDT)
To: Eliot Lear <lear@cisco.com>, rfced-future@iab.org
References: <FFFDC3FA-D1FD-484E-9D77-88A33E8E25FE@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <7dba1e15-d2d4-1162-1550-f26820891bf3@gmail.com>
Date: Fri, 17 Jul 2020 17:16:54 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <FFFDC3FA-D1FD-484E-9D77-88A33E8E25FE@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/gIB2ZI_TPMBPZywDKyMUgXMjD-M>
Subject: Re: [Rfced-future] RFC Editors Future Program @ IETF 108
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: Fri, 17 Jul 2020 05:17:02 -0000

>  Now is a good time to discuss those questions.

My main comment from looking at the slides is that maybe we shouldn't use the term "RSE" until there's an answer to your "hum" question 3 ("Is there a need for a thought leader who can run a community who is expert in publishing?"). The way the discussion has evolved suggests to me that the name of the role might change.

(The answers to the follow-on questions on slide 11 might also change accordingly.)

fwiw I will not be at the meeting, since it will be 2 a.m. here.

Regards
   Brian C

On 16-Jul-20 22:20, Eliot Lear wrote:
> Colleagues,
> 
> A reminder: we will meet virtually on the 27th of July from 14:10 to 15:50 as part of the 108 meeting.  Agenda picking tool does not let you select this meeting.  There is an iCal event included in this message so that you can see it on your calendars if you wish.  Yours truly is a meetecho neophyte, and so I beg your patience we have a bumpy start.
> 
> A few additional points:
> 
>   * Materials have been uploaded.  These include the agenda and the chairs’ slides.  We have adjusted one question from discussion based on feedback from EKR.  Now is a good time to discuss those questions.
>   * The chairs seek a jabber scribe/minute taker.  Tim Wicinski has been extraordinarily helpful in the past, but it would be nice if someone else could take the role so that he can have a break.
>   * Our time will be precious.  It will be important for people to be familiar with the material prior to the meeting.  The chairs intend for the meeting to move pretty quickly along.   We will be doing some hums as you will see.
>   * One of the things we haven’t discussed, and is not on the agenda, is future meetings.  I think that may be something we may need to discuss in some detail, perhaps toward the end of the meeting, based on how hums go, and how we see our work from that point.
> 
> A reminder of the agenda:
> 
>  1. Agenda Bashing
>  2. What we’ve covered
>  3. Decisions we’ve made
>  4. Questions we’ve asked
>  5. Refinements on those questions
>  6. Some hums
>  7. Wanted: one document editor
>  8. AOB
> 
> Eliot
> 
> 
>