Re: Functional differentiation

April Marine <April.Marine@nominum.com> Mon, 13 September 2004 23:58 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 TAA26806; Mon, 13 Sep 2004 19:58:01 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C70mi-0007qS-B3; Mon, 13 Sep 2004 20:03:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C70ba-0005zV-2i; Mon, 13 Sep 2004 19:51:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C70b4-0005iz-Ax for ietf@megatron.ietf.org; Mon, 13 Sep 2004 19:50:59 -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 TAA26197 for <ietf@ietf.org>; Mon, 13 Sep 2004 19:50:56 -0400 (EDT)
Received: from shell-ng.nominum.com ([81.200.64.181]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C70fq-0007do-Md for ietf@ietf.org; Mon, 13 Sep 2004 19:55:56 -0400
Received: by shell-ng.nominum.com (Postfix, from userid 10182) id 8402F5689B; Mon, 13 Sep 2004 16:50:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by shell-ng.nominum.com (Postfix) with ESMTP id 7C65356898; Mon, 13 Sep 2004 16:50:25 -0700 (PDT) (envelope-from amarine@nominum.com)
Date: Mon, 13 Sep 2004 16:50:25 -0700
From: April Marine <April.Marine@nominum.com>
To: Brian E Carpenter <brc@zurich.ibm.com>
In-Reply-To: <4145B640.8040901@zurich.ibm.com>
Message-ID: <20040913163057.U77769@shell-ng.nominum.com>
References: <20040910001924.4284B84CA6@newdev.harvard.edu> <4145B640.8040901@zurich.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: ietf@ietf.org
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: c1c65599517f9ac32519d043c37c5336

On Mon, 13 Sep 2004, Brian E Carpenter wrote:

> 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.
>

This is a very ietf-like point of view, IMO. We are all about individual
effort. Realistically, however, *both* the person AND their employer
matter.

I have worked at companies that contract to a US federal agency. People
who could give me direction were my line manager at my company, my
government task manager, and the government headquarters funding manager.
And yet my job was to serve users, my ostensible "customers." Conflicts
between these folks were not uncommon. Resolving them, in general, meant
resorting to the written contract (task plan) and understanding the
*government's* hierarchy of who could give what sort of direction.
However, in the end, my company boss could reassign me and put someone
else in my place without consulting the government.

The person "we" hire will report to their boss at whatever company they
work for. The company and "the ietf" will have some agreement regarding
duties and what constitutes acceptable performance.  I'm sure "the ietf"
will have some input about who is hired.  However, if some influential
IETF person or group (e.g. IETF Chair, IAB Chair or some vocal part of the
IESG) got it into their head that they didn't like the Admin type person,
could they fire them? What sort of process would that involve? Would, say,
the ISOC *have* to fire them if "the ietf" wanted them to? Who would face
employment liability, etc., in such a case? Probably not "the ietf" as we
currently understand it.

This is the point I was trying to make at the plenary. No matter how great
a person we hire, that person is reporting to their boss in whatever
corporate entity that boss works for.  And no matter how great that entity
is or is currently, what protection will be in place
structurally/contracturally if the current people change (as they will)?

April

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