On Thu, 30 Sep 2004 12:39:07 -0400, Andrew Newton wrote:
If you are suggesting that completing a requirements doc will
lead to an unsuccessful working group, then I'd say that
working group would likely not produce anything anyway.
My own experience is that producing a formal requirements
document in an IETF working group is primarily effective at a)
taking a long time, and b) dissipating the enthusiasm of the
group, and c) imposing abstract constraints before there is a
practical basis for knowing what will work and what is really
essential for an initial deployment. This last point means that
the requirements frequently become Procrustean and impractical.
Of the lengthy list of working groups that you supplied, how long
did it take to produce the requirements documents for these
efforts and what is the current level of deployment and use for
those protocols?
As I said, one can start with concrete specifications and seek to
do minimal changes, or one can go down the path of a working
group design and development project, starting with a clean
slate.
d/
ps. my query about the amount of time to budget for the
requirements exercise was serious. if you believe it essential
to do, then we need to work through the details. how long is
realistic to produce the formal requirements document?
--
Dave Crocker <mailto:dcrocker-at-brandenburg-dot-com>
Brandenburg InternetWorking <http://brandenburg.com>