Re: [Rfced-future] Suggested text for issues #56, #57, #61, #62

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 23 June 2021 21:30 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 20D1F3A412A for <rfced-future@ietfa.amsl.com>; Wed, 23 Jun 2021 14:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level:
X-Spam-Status: No, score=-2.437 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.338, RCVD_IN_DNSWL_NONE=-0.0001, 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 Q0gcadeIvUab for <rfced-future@ietfa.amsl.com>; Wed, 23 Jun 2021 14:30:14 -0700 (PDT)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (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 9603B3A4128 for <rfced-future@iab.org>; Wed, 23 Jun 2021 14:30:14 -0700 (PDT)
Received: by mail-pg1-x533.google.com with SMTP id u190so2875883pgd.8 for <rfced-future@iab.org>; Wed, 23 Jun 2021 14:30:14 -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=tW1O6VZVn3gIYstZKKEs/5cBfRFqwtouM5YMXZoSzHg=; b=dB+6yJ5SW8qurXUncCVG3erTRsYSTRjeEaesaoruabm7F2ExhFFs183gGo6nLD5t0u I62+ARHpssW+apJjuZPKSNjcOEL6t/Xi4U90A8j7w+4LEZpaE1F/+uEdPz6lFr9EBXML iejW1cmLlYKIqZUwdktZMqG70SnXwtWJeynySrFLX5Z45oHkDoy725m51qkcJsXb0waW PH9ap1689VxH51O3/8t+6AY+7y7pswEGKRXJnglDx0oFf/NcEQK252jLW4974QglDHcd +0zNwPvaumg95TxdTou/pcBOU3QQVgW3NWBrybwFnNpvJFM8PgN83DXm2h6ViadeL2ab YtmQ==
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=tW1O6VZVn3gIYstZKKEs/5cBfRFqwtouM5YMXZoSzHg=; b=S/oXapHmRIacadanBwWfsj/uH2E9+ox0Eli/RZb4wfSDWaSAFcn/mr+7lw+10BFROq Gwv4rjnadgrMeBIvdT0KDm5k1GcQ7KjmSDVVx9xXJk91KgIcR5h71nMTqk5Ft8e3qLKu jb4ixIlAAvGF491YFe7wRJspKrOwlBbsMWI2T1GyoG1b51EtEuKPWKqnaPSeITmfKvDf YiVfgN/UWXgfbIy6iX8zEg1Y51icnUjoVOqw2u3dKRrFSTzorSK20Al2iYGL5v+ZmXNQ Kr5j4D42Oh4PwnZtjftYNgCLvSPoPX5qvb+4HJjNlGoeJF1dT5hMAWn6r5rp/zzpGSfo ytxA==
X-Gm-Message-State: AOAM531gXiSxP5/cEMjBcHBnWLnQdZ+2omkFjiVZoXf1NTiAmSbxFtdr QrKc2PRxfr1AsF2DMU2zBrVX29J9lZ510g==
X-Google-Smtp-Source: ABdhPJw3iXkeh4X23hlCCrPXZxj44YkvKHjdRm92gmWDaOcs5t9TLnFeN5SGkUHcqh4O/7F0fRNivA==
X-Received: by 2002:a63:3143:: with SMTP id x64mr1460100pgx.14.1624483813302; Wed, 23 Jun 2021 14:30:13 -0700 (PDT)
Received: from ?IPv6:2406:e003:100d:901:80b2:5c79:2266:e431? ([2406:e003:100d:901:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id h21sm642157pfv.190.2021.06.23.14.30.10 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 23 Jun 2021 14:30:12 -0700 (PDT)
To: Eliot Lear <lear@lear.ch>, Jay Daley <jay@ietf.org>, rfced-future@iab.org
References: <04B7BD6D-612C-410B-BD71-07680CE2D4AB@ietf.org> <39f83475-e0bb-5ca7-ecfe-d6756a581fb5@gmail.com> <3ad917f6-d965-cbf2-0217-38c7e01e9340@lear.ch>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <d0fc01a2-4bad-b24a-a620-6c7193fe6fca@gmail.com>
Date: Thu, 24 Jun 2021 09:30:08 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <3ad917f6-d965-cbf2-0217-38c7e01e9340@lear.ch>
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/T6A-0iyF1L5_rDR03TZEKtMLWhU>
Subject: Re: [Rfced-future] Suggested text for issues #56, #57, #61, #62
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, 23 Jun 2021 21:30:16 -0000

On 23-Jun-21 19:51, Eliot Lear wrote:
> 
> On 23.06.21 05:06, Brian E Carpenter wrote:
>> I may have missed it, but I don't there's a github issue for finalizing the role and title of the RSEA. That's where I would like to hang this comment.
> 
> There are several, one of which we just are in the process of closing.  
> The title one I have deferred discussing for the moment.  We also have 
> the agreed text from Issue 12:

Fair enough (but see below) but in my defence, the title of that issue didn't seem like it covered the role definition.

> 
>> This person will be a senior professional with deep knowledge of 
>> technical publishing.
>>
>> The RSE will operate by providing expert advice to the RSAWG, and if 
>> requested, to the RPC, on any relevant matters. 

Yes, we agreed on that, but I think we missed the question of who will be 
tasked with communicating RSWG and/or RSAB decisions and advice to the RPC. So there's an open issue either here in #12 or in Jay's proposed texts. I'd be inclined to fill it here, something like:

The RSEA will communicate relevant RSWG and RSAB decisions and advice to the RPC.

(The alternative would be to task the RSWG and RSAB chairs with this, but 
if we're hiring an expert, that would seem like the normal person to do it.)

   Brian

>> The value this 
>> individual provides is an understanding of the process of technical 
>> publishing. They expected to learn how the process is applied in the 
>> RFC series. They will be asked to produce regular reviews of the 
>> process and identify problems and opportunities for improvement. There 

>> are also opportunities to spontaneously learn of these problems, 
>> likely the result of interactions with day-to-day operations. The 
>> person may be requested to draft documents
>>
>> For example, the RSE might be consulted about proposed changes to the 
>> style guide, RFC formatting in general, web presence, copyright 
>> matters, or archiving policy, or might of their own initiative suggest 

>> such changes to the RSAWG.
>>
>> The RSE is expected to attend all RSAWG meetings, and to have an 
>> ongoing working relationship with the RPC and tooling team.
>>
> https://github.com/intarchboard/program-rfced-future/blob/master/Issue12-RSE-role.md
> 
> This text needs to make its way into the draft.  That is not to say this 
> text can't improve, but this was what we agreed.
> 
> Eliot
> 
>