[rfc-i] Some questions about the RFC Editor restructuring plan

Henning Schulzrinne hgs at cs.columbia.edu
Thu Aug 7 14:30:06 PDT 2008


this is probably where the analogy with the RFC editing process breaks  
down. The job of the associate editor is done once the paper has been  
accepted. (Most papers go through at least two revision and review  
cycles, with shepherding by the associate editor, but that's more akin  
to the WG process.)

 From then on, the author(s) interact with the production part of the  
process. For each journal, that tends to be one person, so that  
there's a fair amount of consistency. Typically, they get a "proof"  
back from the production side and can then mark it up, kind of like  
AUTH48. Unlike during AUTH48, associate editors don't worry so much  
about authors "sneaking in" changes...


On Aug 7, 2008, at 4:52 PM, Bob Braden wrote:

>  *>
>  *> - Copy editing and production are handled by a separate entity,
>  *> typically the society and its contractors,
> Henning,
> Very interesting!
> How precisely do the copy editors interact with the associate editors?
> How often, and to what end?
> Thanks,
> Bob Braden

More information about the rfc-interest mailing list