Last Call: 'IETF Problem Resolution Process' to Informational RFC

[todd glassey]

I have a real issue with this language as proposed
herein. The Problem Statement working group was not
interested in "fixing or solving the IETF's problems"
or in actually identifying  any problems beyond the
small list that the WG Chairs and the In-crowd of the
group wanted to focus on exclusively. The net of this
is that so many views and concerns  were omitted that
the resulting documents can hardly be called a
consensus except between the specific advocates of
those documents.

This is a demonstration of the critical failing of the
IETF to adequately represent anyone but the "insiders"
in any situation and clearly IMHO demonstrates the lack
of Fair and Open processes.

Todd Glassey

----- Original Message ----- 
From: "The IESG" <iesg-secretary at ietf.org>
To: <IETF-Announce:>
Cc: <problem-statement at alvestrand.no>
Sent: Wednesday, January 14, 2004 3:17 PM
Subject: Last Call: 'IETF Problem Resolution Process'
to Informational RFC


> The IESG has received a request from the Problem
Statement WG to consider
> the following document:
>
> - 'IETF Problem Resolution Process '
>    <draft-ietf-problem-process-04.txt> as an
Informational RFC
>
> The IESG plans to make a decision in the next few
weeks, and solicits
> final comments on this action.  Please send any
comments to the
> iesg at ietf.org or ietf at ietf.org mailing lists by
2004-01-28.
>
> Note: This document is being published mainly as a
record of the
> deliberations of the Problem WG in regard to finding
a process for resolving
> the IETF's problems, and documents both things that
were uncontroversial
> and things where the group failed to reach any
consensus. It is being
> published for the historical record, not as a set of
instructions for
> reforming the IETF.
>
> The file can be obtained via
>
http://www.ietf.org/internet-drafts/draft-ietf-problem-process-04.txt
>