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

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

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESEjP-0007fD-Mb; Wed, 19 Oct 2005 10:15:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESEjO-0007f0-Ho for pesci-discuss@megatron.ietf.org; Wed, 19 Oct 2005 10:15:50 -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 KAA19905 for <pesci-discuss@ietf.org>; Wed, 19 Oct 2005 10:15:42 -0400 (EDT)
Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESEv8-0004yf-A9 for pesci-discuss@ietf.org; Wed, 19 Oct 2005 10:27:59 -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 1ESEjD-0005a1-NM; Wed, 19 Oct 2005 07:15:40 -0700
Message-Id: <6.2.3.4.2.20051019161135.03bad290@mail.jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Wed, 19 Oct 2005 16:13:43 +0200
To: Sam Hartman <hartmans-ietf@mit.edu>, pesci-discuss@ietf.org
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
Subject: Re: [Pesci-discuss] Question: stability of IAB
In-Reply-To: <tslk6g9rfsj.fsf@cz.mit.edu>
References: <tslk6g9rfsj.fsf@cz.mit.edu>
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: 8abaac9e10c826e8252866cbe6766464
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

At 11:56 19/10/2005, Sam Hartman wrote:
>This is a question submitted as an individual.
>
>One of the claims made in the current draft is that the IAB would
>remain relatively stable throughout process change.

Full support of this. IAB has expressed at least two concerns I know of:

- RFC 3869 one can also read as questions on the way IAB should adapt 
to help better R&D
- the recent open mailing list on architectural issues. I consider as 
extremely positive, but a real change, which can bring new changes 
(going with ab evolution of the architectural vision)
jfc



>Have people carefully considered the the effectiveness of the IAB in
>its architectural role?  Are people being quiet and not proposing
>change because things are working fine and the IAB is providing
>valuable architectural guidance just the way we need it?  Or are
>people being quiet because the IAB is not in the way?
>
>I don't know what the answer is, but I think it important to consider
>carefully before deciding the IAB's role is stable.
>
>
>_______________________________________________
>Pesci-discuss mailing list
>Pesci-discuss@ietf.org
>https://www1.ietf.org/mailman/listinfo/pesci-discuss


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