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

sob@harvard.edu (Scott Bradner) Thu, 02 September 2004 11:38 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 HAA24027; Thu, 2 Sep 2004 07:38:23 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2pxT-0002tK-OW; Thu, 02 Sep 2004 07:40:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2poL-00045U-EP; Thu, 02 Sep 2004 07:31:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2pkO-00029L-F5 for ietf@megatron.ietf.org; Thu, 02 Sep 2004 07:27:20 -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 HAA23308 for <ietf@ietf.org>; Thu, 2 Sep 2004 07:27:19 -0400 (EDT)
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2pml-00024K-Ia for ietf@ietf.org; Thu, 02 Sep 2004 07:29:48 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501) id 834F836FB43; Thu, 2 Sep 2004 07:26:48 -0400 (EDT)
To: ietf@ietf.org
Message-Id: <20040902112648.834F836FB43@newdev.harvard.edu>
Date: Thu, 02 Sep 2004 07:26:48 -0400
From: sob@harvard.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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: 0bc60ec82efc80c84b8d02f4b0e4de22

Harald sed:
   scenarios C and D envision incorporating the *support function* for the 
   IETF. The IETF would remain an undefined entity under these scenarios.

   I've had another suggestion that the IETF (the real technical process 
   entity) should become a formally recognizable entity of some sort (possibly 
   an unincorporated organization). But that's distinct from the idea of 
   incorporating the support function, and is NOT described in the current 
   document.

imho both C & D would be seen by most or the world as incorporating 
*the IETF*  - if there is confusion within the IETF over the
difference between incorporating the *support function* and 
incorporating the whole IETF the difference would be totally lost
by non-IETFers (and most IETFers is my guess) - in any case, the 
target of any legal attack on the IETF would be the corporation with 
IETF in the name if one existed - about the only way I could see that
there woudl not be confusion wiuld be to call the corporation "The
Corporation to Support Internet Standardization" (TCTSIS or TCSIC) and
not have the IETF name in it.

Scott

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