> On 17 Feb 2025, at 15:10, Brian E Carpenter <brian.e.carpen...@gmail.com> > wrote: > >> 4. Define "consumers" for RFCs as stakeholders and assign the RPC a role in >> representing their interests >> (I'm personally unsure about this last one, but I'll hold off on >> articulating why for now.) > > The new bit here is not the notion of consulting consumers, which is in > section 3.2.1 of RFC 9280, but of assigning a role to the RPC. At the moment > we have given the duty of consulting them to "RSAB members" directly. Is the > RSAB telling us that doesn't work and needs fixing?
I think you’ve misunderstood as this text does not take away the RSAB role. It is partly as Martin writes, for the RPC to 'represent' consumers, but even that is missing the major point of this text, which is to clearly identify consumers as a grouping separate from IETF participants and to ensure that the RFC editor site is focused on them with that separation clear. Jay > > Brian > > -- > rswg mailing list -- rswg@rfc-editor.org > To unsubscribe send an email to rswg-le...@rfc-editor.org -- Jay Daley IETF Executive Director exec-direc...@ietf.org -- rswg mailing list -- rswg@rfc-editor.org To unsubscribe send an email to rswg-le...@rfc-editor.org
