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

[Brian E Carpenter <[e-mail]>]

On 23-Jun-21 13:14, Jay Daley wrote:
> Here is my proposed text to address the following issues
> 
> #56 - Process for RPC work not requiring consensus
> #57 - How are RPC priorities set?
> #61 - Replacing the previous RSE role in gathering requirements for the 
RPC

I understand why that becomes an RSWG and RSAB function, but I think we need it to be clear elsewhere in the document that we expect the RSEA to have a major role in this work (and very likely be the de facto communications channel from the RSWG and RSAB to the RPC).

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.

    Brian C

> #62 - Communicating decisions about RPC projects/priorities to the community
> 
> The RPC have not had a chance to comment on this text, but I am hoping they will on list in due course.
> 
> —— 
> ## RFC Production Center
> 
> The RFC Production Center (RPC) shall develop and maintain a work 
> program for the implementation of community requirements. In 
> developing this work program, the RPC should consult with the RSAB so 
> that the RSAB may:
> 
> * Inform the RPC of any community requirements that it should consider
>   in addition to policy proposals emanating from the RSWG.
> * Advise the RPC on what degree of community consultation and 
>   engagement is required for any proposed or planned work item.
> * Advise the RPC on the relative priorities of proposed and planned 
>   work items.
> 
> All matters of budget, timetable and impact on its performance 
> targets, are between the RPC and IETF LLC.
> 
> In the event that the RPC is required to make a decision without 
> consultation that would normally deserve consultation, or makes a 
> decision against the advice of the RSAB then it must notify the 
> RSAB.
> 
> The RPC shall report regularly to the RSAB, RSWG and broader 
> community, on the contents and progress of its work program and any 
> key risks or issues affecting it. 
> —— 
>