IETF Logo Mail Archive

Re: Appointment of a Transport Area Director

David Kessens <david.kessens@nsn.com> Thu, 07 March 2013 18:40 UTC

Return-Path: <david.kessens@nsn.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 B40E321F8A0C for <ietf@ietfa.amsl.com>; Thu, 7 Mar 2013 10:40:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 9t+Ecilfo6N1 for <ietf@ietfa.amsl.com>; Thu, 7 Mar 2013 10:40:40 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id E6CCB21F89FD for <ietf@ietf.org>; Thu, 7 Mar 2013 10:40:39 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id r27IeZ1E003844 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 7 Mar 2013 19:40:35 +0100
Received: from localhost.localdomain ([10.138.48.137]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r27IeX3g008241; Thu, 7 Mar 2013 19:40:34 +0100
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.14.5/8.14.5) with ESMTP id r27IeWTV028381; Thu, 7 Mar 2013 10:40:32 -0800
Received: (from david@localhost) by localhost.localdomain (8.14.5/8.14.5/Submit) id r27IeWuV028380; Thu, 7 Mar 2013 10:40:32 -0800
Date: Thu, 07 Mar 2013 10:40:32 -0800
From: David Kessens <david.kessens@nsn.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Appointment of a Transport Area Director
Message-ID: <20130307184032.GS2854@nsn.com>
References: <CAHBDyN6AM-_b2HMrmmQQVuhxFc-_Rfpfg0=r38mkcJ4zqoJeTw@mail.gmail.com> <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <tslk3pjm55w.fsf@mit.edu>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 774
X-purgate-ID: 151667::1362681636-00001023-FBECECE7/0-0/0-0
Cc: 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:40:40 -0000

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