Re: What to incorporate (Re: Options for IETF administrative restructuring)

Carl Malamud <carl@media.org> Thu, 02 September 2004 14:35 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 KAA08173; Thu, 2 Sep 2004 10:35:30 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2siv-0000aU-5v; Thu, 02 Sep 2004 10:38:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2scG-0004rt-Gq; Thu, 02 Sep 2004 10:31:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2sPO-0004cE-P4 for ietf@megatron.ietf.org; Thu, 02 Sep 2004 10:17:51 -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 KAA06569 for <ietf@ietf.org>; Thu, 2 Sep 2004 10:17:49 -0400 (EDT)
Received: from bulk.resource.org ([192.101.98.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2sRm-0007aJ-VD for ietf@ietf.org; Thu, 02 Sep 2004 10:20:20 -0400
Received: from bulk.resource.org (localhost.resource.org [127.0.0.1]) by bulk.resource.org (8.12.2/8.12.2) with ESMTP id i82EHH6Y001621; Thu, 2 Sep 2004 07:17:17 -0700 (PDT)
Received: (from carl@localhost) by bulk.resource.org (8.12.2/8.12.2/Submit) id i82EHHKZ001620; Thu, 2 Sep 2004 07:17:17 -0700 (PDT)
From: Carl Malamud <carl@media.org>
Message-Id: <200409021417.i82EHHKZ001620@bulk.resource.org>
In-Reply-To: <Pine.GSO.4.58.0409020933260.5266@backin5.merit.edu>
To: Susan Harris <srh@merit.edu>
Date: Thu, 02 Sep 2004 07:17:17 -0700
Organization: Memory Palace Press
X-Winch: Warn 9.5i
X-Mailer: ELM [version 2.4ME+ PL94 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: What to incorporate (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: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit

Hi Susan -

Just so we're clear, that was my going-in assumption and I've kept
that throughout the analysis.  Any of the structures I've outlined
can be focused strictly on administrative support (just like
any of the structures could be corrupted to reach beyond that
focus).  That's why I suggested that we do this in two steps:

1. agree on the general direction to take
2. task people to write the specific chartering documents and
   publish them as a bcp, including a last call 

Since the devil is in the details, this lets us focus in
on making sure the details are correct and the community has
seen those details and agreed to them before they become policy.
First step, though, is some feeling from the community on which
path to pursue.

Make sense?  (BTW, I'm more than happy to answer questions
about these various mechanisms, processes, functions, and
other buzzwords in the report ... I tried to keep things
clear, but the legal world isn't always perfectly clear. :)

Regards,

Carl

> > >>If people want that possibility described, please speak up - Carl has the
> > >>pen ready....
> > >>
> > >
> > >
> > > Yes that would be helpful.
> >
> > Well, I don't agree. I think it would defocus the discussion (which
> > is about putting the IETF's administration onto a business-like
> > basis). IMHO the only case in which we should discuss the wider
> > option is if the newtrk WG proposes changes in the standards process
> > that would make such a thing necessary.
> 
> What he said.
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
> 

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