RE: [Pesci-discuss] For whom it may concern..

"Margaret Wasserman" <margaret@thingmagic.com> Thu, 10 November 2005 18:57 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EaHcF-0001aH-JJ; Thu, 10 Nov 2005 13:57:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EaHcE-0001aC-EK for pesci-discuss@megatron.ietf.org; Thu, 10 Nov 2005 13:57:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25784 for <pesci-discuss@ietf.org>; Thu, 10 Nov 2005 13:57:14 -0500 (EST)
Received: from [204.9.221.21] (helo=thingmagic.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EaHsU-0003qQ-2z for pesci-discuss@ietf.org; Thu, 10 Nov 2005 14:14:31 -0500
Received: from [209.52.109.222] (account margaret HELO ceili) by thingmagic.com (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 580827; Thu, 10 Nov 2005 13:57:26 -0500
From: Margaret Wasserman <margaret@thingmagic.com>
To: "'Joel M. Halpern'" <joel@stevecrocker.com>, pesci-discuss@ietf.org
Subject: RE: [Pesci-discuss] For whom it may concern..
Date: Thu, 10 Nov 2005 10:57:06 -0800
Message-ID: <004101c5e628$8c92fa10$de6d34d1@instant802.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <6.2.1.2.0.20051110123452.02e5e5d0@mail.stevecrocker.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
Thread-Index: AcXmHjAUnYOwQRztQZmZOKLq1rz8XgABk51Q
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Cc:
X-BeenThere: pesci-discuss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Process Evolution Study Committee of the IETF discussion <pesci-discuss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pesci-discuss>, <mailto:pesci-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pesci-discuss>
List-Post: <mailto:pesci-discuss@ietf.org>
List-Help: <mailto:pesci-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pesci-discuss>, <mailto:pesci-discuss-request@ietf.org?subject=subscribe>
Sender: pesci-discuss-bounces@ietf.org
Errors-To: pesci-discuss-bounces@ietf.org

Hi Joel,

Joel Halpern wrote:
> I believe that process proposals need to be an exception to this.
> As far as I can tell, the community will never reach rough consensus on
> any of the major process changes.
> (It was hard enough to get rough consensus on minor changes.)
> As I said at the meeting, while such an absence can be used as an excuse
> for not making any major changes, that would seem to be an inappropriate
> response.

I think that the community can (and does) reach consensus on major changes
when they are really needed.

Last year, we reached community consensus to reorganize the entire
administrative and financial structure of the IETF and to create a new IETF
leadership body.  IMO, this happened because the community was convinced
that change was necessary, and there was sufficient pressure to fix the
problem(s) that we were able to forge a consensus.

In some other cases, we don't have that pressure (yet), so we have not
reached consensus to make other specific major changes. 

Margaret


_______________________________________________
Pesci-discuss mailing list
Pesci-discuss@ietf.org
https://www1.ietf.org/mailman/listinfo/pesci-discuss