[rfc-i] RFC Editor Model Final Version?

Russ Housley housley at vigilsec.com
Sun Sep 7 10:16:25 PDT 2008


> >RFC Production
> >
> >In the proposed split of activities, RFC Production is performed by a
> >paid contractor, and the contractor responsibilities include:
> >
> >         1.      Editing inputs from all RFC streams to comply with
> > the RFC Style
> >Manual
> >         2.      Creating records of edits performed on documents
> >         3.      Engaging in dialogue with authors when
> > clarification is needed
> >         4.      Creating records of dialogue with documents authors
> >         5.      Requesting advice from the RFC Editor as needed
> >         6.      Provide suggestions to the RFC Editor as needed
> >         7.      Coordinating with IANA to obtain registry information
> >         8.      RFC number assignment
> >         9.      Forwarding ready-to-publish documents to the RFC Publisher
> >         10.     Forwarding records of edits and author dialogue to
> > RFC Publisher
> >         11.     Liaison with IESG and IAB
>
>According to the above, the RFC Production would only request advice
>from the RFC Editor when it deems fit, i.e. the RFC Editor cannot
>direct it what to do.

I would not expect much interaction on this interface, but you are 
right the RFC Editor should be able to offer constructive input 
without being asked.

Russ



More information about the rfc-interest mailing list