Re: [idn] Future of the requirements document

[Erik Nordmark <Erik.Nordmark@eng.sun.com>]

> The day to abandon a requirements draft unconditionally, is one day 
> after the last draft with a dependency upon it is abandoned. If the
> WG finds itself in the situation of being unnaturally prolonged in
> life by an orphaned requirements draft, then by all means, send it
> back to individual submission status.

Eric,

I haven't seen the WG make any use of the requirements document to date.
For instance, there has been no discussion saying something like
"your proposal doesn't satisfy requirement NN".
This makes we wonder whether the requirement document serves a useful purpose.

The original intent of this document was to get it agreed to and published
before the the solutions. You seem to suggest that the requirements document
could be used internally in the WG as it continues to work on solutions
and later be discarded (i.e. not published as an RFC).
Since the WG hasn't used the document in such a fashion until now what makes
you believe that things will change in this respect?

I think the discussion that lead up to the requirements document 
was quite useful but the current document has significant issues.
I think it makes more sense to spend the WG cycles on refining the 
and clarifying the WG work items. 

   Erik