IETF Logo Mail Archive

Re: Appointment of a Transport Area Director

Toerless Eckert <eckert@cisco.com> Thu, 07 March 2013 18:51 UTC

Return-Path: <eckert@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C053221F8B1E for <ietf@ietfa.amsl.com>; Thu, 7 Mar 2013 10:51:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.303
X-Spam-Level:
X-Spam-Status: No, score=-10.303 tagged_above=-999 required=5 tests=[AWL=0.296, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GePp7T3+eouN for <ietf@ietfa.amsl.com>; Thu, 7 Mar 2013 10:51:13 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 32CC121F8B1A for <ietf@ietf.org>; Thu, 7 Mar 2013 10:51:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=909; q=dns/txt; s=iport; t=1362682273; x=1363891873; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=QObQCKt8zBTqJyR660+Snz5S+c4f/LtNYLT4x7IAJQM=; b=J9K/0IIg74a9sojqvycwywdIsLeCytTU8ReOwdezOqtOIZrnoaDX1o2v kjo7+ZCHAvl+NsravyZGOs7gSQZUtsfRtUZgF/qKtGQzuz668POzfUWwJ HwtUwghHRpXMkMzfQcWCNvuVwerKs8gMiY4kQFeRJrN0Ug5hDCsqRS7rr k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EADXhOFGrRDoJ/2dsb2JhbABDxFCBZBZ0giwBAQEEOj8QCxgJJQ8FSYglu0CPDAeCX2EDiGyNXgGQcYMq
X-IronPort-AV: E=Sophos;i="4.84,803,1355097600"; d="scan'208";a="74524640"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-4.cisco.com with ESMTP; 07 Mar 2013 18:51:13 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r27Ip7vU002649 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Mar 2013 18:51:07 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r27Io2Q0006243; Thu, 7 Mar 2013 10:50:22 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r27Io1dc006242; Thu, 7 Mar 2013 10:50:01 -0800
Date: Thu, 07 Mar 2013 10:50:01 -0800
From: Toerless Eckert <eckert@cisco.com>
To: David Kessens <david.kessens@nsn.com>
Subject: Re: Appointment of a Transport Area Director
Message-ID: <20130307185001.GD24221@cisco.com>
References: <tslr4julxmh.fsf@mit.edu> <1C1C0842-BF6A-4A3F-A312-35CF0A994793@lilacglade.org> <BDCCFB12-1F2C-44BD-867A-92E5745F3D39@vigilsec.com> <7B6FDB89-F360-45B6-8240-F2F9F81ABAA7@vigilsec.com> <9292FB65-9842-4C95-9284-15F1E9ECEE1D@lilacglade.org> <5138AE1F.5080602@neclab.eu> <tsl6213p67w.fsf@mit.edu> <20130307182406.GR2854@nsn.com> <tslk3pjm55w.fsf@mit.edu> <20130307184032.GS2854@nsn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20130307184032.GS2854@nsn.com>
User-Agent: Mutt/1.4.2.2i
Cc: Sam Hartman <hartmans-ietf@mit.edu>, IETF <ietf@ietf.org>, Martin Stiemerling <martin.stiemerling@neclab.eu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2013 18:51:13 -0000

:gs/nomcom/nomcom process/

On Thu, Mar 07, 2013 at 10:40:32AM -0800, David Kessens wrote:
> 
> Sam,
> 
> On Thu, Mar 07, 2013 at 01:32:59PM -0500, Sam Hartman wrote:
> > 
> > I don't think there is hair splitting going on here; I think the issues
> > that are being raised are quite real and important.  It's not the IESG's
> > fault if the nomcom does x.  It is the IESG's fault if the IESG takes on
> > tasks delegated to the nomcom in RFC 3777.  As you are aware, I have
> > taken concerns I believe are best handled by the IAB and nomcom to the
> > IAB and nomcom.
> 
> The nomcom makes the appointments.
> There is nothing the IESG can take away
> from that. It is the nomcom that interprets the "requirements" from the
> IESG. There is nothing the IESG can do about that. If you are unhappy how
> the nomcom does the interpretation, contact the nomcom. 
> 
> David Kessens
> ---

v2.23.0 | Report a Bug | By Email