Re: Options for IETF administrative restructuring

John C Klensin <john-ietf@jck.com> Wed, 15 September 2004 16:51 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19485; Wed, 15 Sep 2004 12:51:00 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C7d4w-0007eE-B3; Wed, 15 Sep 2004 12:56:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C7cp2-00064p-Oy; Wed, 15 Sep 2004 12:39:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C7chR-0003ky-VH for ietf@megatron.ietf.org; Wed, 15 Sep 2004 12:32:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17448 for <ietf@ietf.org>; Wed, 15 Sep 2004 12:32:02 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C7cmY-00071v-4i for ietf@ietf.org; Wed, 15 Sep 2004 12:37:25 -0400
Received: from [209.187.148.215] (helo=scan.jck.com) by bs.jck.com with esmtp (Exim 4.34) id 1C7chM-0007uy-Fc; Wed, 15 Sep 2004 12:32:00 -0400
Date: Wed, 15 Sep 2004 12:32:00 -0400
From: John C Klensin <john-ietf@jck.com>
To: Aaron Falk <falk@ISI.EDU>, Sam Hartman <hartmans@mit.edu>
Message-ID: <0F6D11A9E8E4CCDA69F495CC@scan.jck.com>
In-Reply-To: <BC833A4B-00FC-11D9-9699-000A95DBDB84@isi.edu>
References: <412D268D.3020402@thinkingcat.com> <tslhdqcuj8i.fsf@cz.mit.edu> <BC833A4B-00FC-11D9-9699-000A95DBDB84@isi.edu>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Options for IETF administrative restructuring
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit


--On Tuesday, 07 September, 2004 11:35 -0700 Aaron Falk
<falk@ISI.EDU> wrote:

> On Sep 5, 2004, at 4:15 PM, Sam Hartman wrote:
> 
>> I do not think that recommendation 7 in scenario B is a good
>> idea.  I believe that plenary time is full enough without
>> crowding it more.
> 
> What about a 'business meeting' that is scheduled in wg slot
> or even on Sunday?
> 
> I understand that there may be conflicts between people who
> want to go to a working group and the business meeting but we
> live with those in working groups.  Hopefully, with a smaller
> group (compared to the plenary) and largish block of time a
> good f2f dialog could take place.

In my continuing pursuit of trying to avoid fixing what isn't
broken and of doing only those things in the name of
problem-solving that actually solve problems...

(1) We have serious problems finding enough time for WGs and
BOFs to meet and to do so without serious conflicts, do we
really need to introduce another term into the equation?

(2) Is it generally understood that the ISOC BoT already usually
meets on Saturday and/or Sunday before the IETF meetings and
that those meetings are open?

(3) Would more publicity of (2) permit us to declare success on
this topic and move on, even without knowing what problem is
being solved?   :-)

Mumble.
     john





_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf