Re: [nfsv4] rfc5666bis and rpcrdma-bidirection progress update

[Benjamin Kaduk <[e-mail]>]

On Mon, Nov 28, 2016 at 12:32:58PM -0500, David Noveck wrote:
> 
> We've tried reminders and Chuck did remove unnecessary work.  However, the
> IETF rules don't appear to allow changing ownership of the task of
> producing a wrIteup.  If you think that is appropriate, then perhaps you
> should investigate it.  Given that there is a bunch of other documents that

The "IETF rules" (insamuch as there are rules) do allow for changing the
document shepherd after assignment, and for non-WG-chair document shepherds.
The chairs have a fair amount of latitude in assigning shepherds, as I understand it.
We've been having similar problems with a backlog of documents in the kitten
WG, and recently had a contributor volunteer some time to help shepherd
documents, which has made a big difference.

> 
> True, but there is a significant portion of the process where we wind up
> waiting for action by the WG chair, and for these documents, that has been
> a considerable portion of the delay.  Is there a viable way to spread out
> this work better?

Bringing in non-chair document shepherds might help, and there is also
some possibility (in terms process) of adding a third co-chair, if there
are suitable candidates and the current chairs/AD are amenable.

Ultimately, it comes down to finding someone willing to do the work who
has time; shepherding is some of the least glorious work (you don't even
get your name on the final RFC!), but is still an important part of
the document lifecycle.

I see that the two documents in the subject have already been submitted
for publication, so maybe there is no longer an immediate need, but it
still seemed worth pointint out that there are a few options in this space.

-Ben