Re: Functional differentiation

Brian E Carpenter <brc@zurich.ibm.com> Mon, 13 September 2004 15:22 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 LAA08781; Mon, 13 Sep 2004 11:22:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C6sjh-0002FV-GR; Mon, 13 Sep 2004 11:27:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C6sW0-0003HV-P9; Mon, 13 Sep 2004 11:13:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C6sL5-0001Ke-Bx for ietf@megatron.ietf.org; Mon, 13 Sep 2004 11:01:55 -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 LAA06606 for <ietf@ietf.org>; Mon, 13 Sep 2004 11:01:52 -0400 (EDT)
Received: from mtagate1.de.ibm.com ([195.212.29.150]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C6sPm-0001gX-JX for ietf@ietf.org; Mon, 13 Sep 2004 11:06:48 -0400
Received: from d12nrmr1507.megacenter.de.ibm.com (d12nrmr1507.megacenter.de.ibm.com [9.149.167.1]) by mtagate1.de.ibm.com (8.12.10/8.12.10) with ESMTP id i8DF1MfQ129346; Mon, 13 Sep 2004 15:01:22 GMT
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d12nrmr1507.megacenter.de.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i8DF1Lmk197932; Mon, 13 Sep 2004 17:01:21 +0200
Received: from zurich.ibm.com (dyn-9-13-126-72.ge.ch.ibm.com [9.13.126.72]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id RAA79600; Mon, 13 Sep 2004 17:01:20 +0200
Message-ID: <4145B640.8040901@zurich.ibm.com>
Date: Mon, 13 Sep 2004 17:01:20 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: scott bradner <sob@harvard.edu>
References: <20040910001924.4284B84CA6@newdev.harvard.edu>
In-Reply-To: <20040910001924.4284B84CA6@newdev.harvard.edu>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Cc: hardie@qualcomm.com, ietf@ietf.org, aboba@internaut.com
Subject: Re: Functional differentiation
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: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit

The benefit of having an Admin Director is that this person
will have responsiveness to IETF needs and desires as the
main item in their job description. I think that is much more
significant than whether the person works for ISOC or a new
entity. It's the person that counts, not their legal employer.

    Brian


scott bradner wrote:
>> As it stands now, ISOC's
>>role in the RFC Editor contract is balanced by its need to understand the
>>standards process; it should and does understand what the
>>RFC Editor does for the IETF.
> 
> 
> as well as the ISOC's ability to understand what the IAB (which manages
> the RFC Editor) wants the RFC Editor to do (i.e., its not just the ISOC
> having to figure out on its own)
> 
> Scott
> 
> 
> _______________________________________________
> 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