WG process (was Re: I-D ACTION:draft-ietf-webdav-quota-07.txt)

>
> So the answer is "yes, the WG runs under this process"?

I'd say we're approaching this process, yes.  I didn't exactly shepherd 
the ACL draft -- at that time, the IESG wasn't yet including document 
shepherds in their group discussions -- but I did talk to IESG people 
directly about their "comment" issues on the ACL draft and found out 
what would resolve their issues, which is a big part of what a document 
shepherd is expected to do (rather than rely on the AD to do all the 
communication between IESG and WG as in the old model).

>
>>> b) Who are the document shepherds for the current working group 
>>> documents that seem to be ready (BIND, REDIRECT, QUOTA)?
>> I probably would be.
>
> OK, let me rephrase this:
>
> Will the working group chair(s) start shepherding some or all of these 
> documents? If yes, which and when? If no, is there an expectation to 
> the WG to do any specific additional work so they can?

Yes, I am willing to shepherd BIND, REDIRECT, QUOTA and/or RFC2518bis 
through this process -- provided they meet the bar.  For BIND, the 
document for which we have the most information, we still have 
underspecified areas and we haven't had the open and exploratory 
conversations to find out if we can firm those up, but the more 
difficult hurdle may well be the lack of reviews and implementors.  If 
we don't have the energy as a WG to finish that properly, it's my 
opinion that we could instead bring  BIND immediately to submission as 
an Informative RFC, where it would be an exemplary and high-quality 
example of that class.

Lisa

Received on Thursday, 26 May 2005 17:52:15 UTC