Re: [Pesci-discuss] Question: stability of IAB

"JFC (Jefsey) Morfin" <jefsey@jefsey.com> Wed, 19 October 2005 22:43 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESMf9-0003zA-5U; Wed, 19 Oct 2005 18:43:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESMf7-0003yz-WA for pesci-discuss@megatron.ietf.org; Wed, 19 Oct 2005 18:43:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10258 for <pesci-discuss@ietf.org>; Wed, 19 Oct 2005 18:43:48 -0400 (EDT)
Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESMqw-0002RY-6y for pesci-discuss@ietf.org; Wed, 19 Oct 2005 18:56:11 -0400
Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1ESMes-0005Xu-Ne; Wed, 19 Oct 2005 15:43:43 -0700
Message-Id: <6.2.3.4.2.20051019225601.0571b470@mail.jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Thu, 20 Oct 2005 00:43:31 +0200
To: Jari Arkko <jari.arkko@piuha.net>, Sam Hartman <hartmans-ietf@mit.edu>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
Subject: Re: [Pesci-discuss] Question: stability of IAB
In-Reply-To: <43567197.2010306@piuha.net>
References: <tslk6g9rfsj.fsf@cz.mit.edu> <43567197.2010306@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: pesci-discuss@ietf.org
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

At 18:17 19/10/2005, Jari Arkko wrote:
>However, we should be careful in not attempting
>to change too many variables at the same time.

Dear Jari,
there are two problems: the method for changes and some immediate changes.

The method is important, and probably more: the resulting culture to 
be ready to consider, to accept and to enforce changes.

>A priority order is needed.

This priorities should be set-up in considering the expected 
experience to analyse/valiated the method and the symbolic value to 
develop and ascertain the culture.

<>

>A couple of years ago IANA was on my
>list too, but the situation may now be better (?).

IMHO from current observation both inside and outside the IETF this 
is _the_ political and architectural target for changes. Protecting 
status quo would per se be a change because it would mean a 
protection action, I understand the IETF is not used to?

jfc




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