The IETF's problems

[Elwyn Davies]

I agree with Melinda.

If you want something altered or included in the problem statement draft,
the combattants on this thread are going to have to state clearly how they
would like the text altered.  I have not yet seen anything that actually
significantly enhances the arguments in the current draft - I believe that
Iljitsch's initial comments are actually all covered by the existing text in
one way or another.

I do not believe that having or not having three short windows in which
drafts cannot be submitted could be considered a 'root cause problem'.
IMHO, it is a useful deadline which concentrates the mind(s) of authors and
editorial teams towards actually getting something out there in a reasonably
timely fashion, and gives the victims who have to read the flood of words
some chance of being uptodate with what has been written by the time it is
discussed in the f2f meetings.   Given the percentage of people who do seem
to read most drafts, anything that helps with this is highly desirable.

I await some well-honed text!

Regards,
Elwyn

> -----Original Message-----
> From: Melinda Shore [mailto:mshore at cisco.com]
> Sent: 20 July 2003 18:29
> To: Iljitsch van Beijnum
> Cc: problem-statement at alvestrand.no
> Subject: Re: The IETF's problems 
> 
> 
> > This is a prime example of the topic of this list: the IETF 
> is unable 
> > to determine what it should work on and what it shouldn't 
> work on in a 
> > satisfactory way.
> 
> The discussion itself isn't doing much to distill the topic
> down to document text, and we need to stay focused.  Do you
> feel that existing text regarding scope in the problem
> statement document is inadequate?
> 
> Thanks,
> 
> Melinda
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://eikenes.alvestrand.no/pipermail/problem-statement/attachments/20030721/7e6124ed/attachment.htm