Re: Process on open RFC2518bis issues

I agree with Julian.  What needs consensus is that a given draft
should be published.  The approach one uses to reach such a draft
can vary greatly.  Getting working group consensus on every issue
is one approach to producing a draft, but it is not the only approach,
is not always the best approach, and sometimes is not even a feasible
approach in the presence of time constraints.

Cheers,
Geoff


Julian Reschke <julian.reschke@gmx.de> wrote on 01/13/2006 03:15:07 PM:

> Cullen Jennings wrote:
> > 
> > Unfortunately, this proposal would violate that idea that a WG needs 
to 
> > determine that at least rough consensus exists within the WG for the 
> > advancement of a document. It would change to where there was not 
> > consensus, then we defaulted to what RFC 2518 says.
> > ...
> 
> Indeed. As a matter of fact that was my understanding about how revising 

> an standards track document should work. If there's no consensus for a 
> change, don't do it.
> 
> The question then is whether the agreed upon changes represent 
> sufficient advance over the previous spec to make publishing it 
worthwhile.
> 
> Best regards, Julian