The MPLS WG Archive

[Danny McPherson <danny@ambernetworks.com>]

> Progress is accomplished by achieving results, however imperfect
> they might be, and moving on to the next problem.  Progress is
> not attained as a result of an endless search for the perfect goal.
> 
> If you see a problem with a specification, I suggest that you write
> a separate specification to address it.  This is under the heading
> of "moving on to the next problem".  IF, in attempting to write a
> new specification, you uncover reasons why the existing one will
> not be useful to anyone, THEN it is likely that the existing one
> will be discarded in favor of a new, improved version.
> 
> I do not think the reasons stated so far are sufficient to justify
> such a course of action.  I believe there is abundant evidence that
> the existing specifications are useful to someone.

Sure they are, even as they exist today -- in draft form.

However, fundamental problems brushed off as aesthetics in 
order to more promptly publish a specification is a clear 
indication that some folks are more concerned about generating 
documents than they are about generating clean protocol 
specifications.  

Suggesting that we fix things that are broke in this draft 
later, with yet another patchwork of I-Ds, goes against the 
entire I-D process.

-danny