Re: Last Call: <draft-krishnan-nomcom-tools-01.txt> (Requirements for IETF Nominations Committee tools) to Informational RFC

Russ Housley <housley@vigilsec.com> Wed, 13 June 2012 16:39 UTC

Return-Path: <housley@vigilsec.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 2242F11E8079 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 09:39:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level:
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 WkkvSqZeYs42 for <ietf@ietfa.amsl.com>; Wed, 13 Jun 2012 09:39:15 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id F3B8F11E8072 for <ietf@ietf.org>; Wed, 13 Jun 2012 09:39:12 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 51FD5F24014 for <ietf@ietf.org>; Wed, 13 Jun 2012 12:39:22 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id TXIAP5UkIqkN for <ietf@ietf.org>; Wed, 13 Jun 2012 12:39:04 -0400 (EDT)
Received: from [192.168.2.110] (pool-96-255-37-161.washdc.fios.verizon.net [96.255.37.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 1F5309A4725 for <ietf@ietf.org>; Wed, 13 Jun 2012 12:39:21 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Last Call: <draft-krishnan-nomcom-tools-01.txt> (Requirements for IETF Nominations Committee tools) to Informational RFC
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20120613160444.22853.1522.idtracker@ietfa.amsl.com>
Date: Wed, 13 Jun 2012 12:39:09 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3ED7694B-47FE-4741-B0FE-4989BFDF68A0@vigilsec.com>
References: <20120613160444.22853.1522.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
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: Wed, 13 Jun 2012 16:39:16 -0000

I want to highlight one think in this document.  The document says:

   There is an existing tool for supporting Nomcom work.  The set of
   requirements specified in this document are mainly enhancement
   requirements or behavior changes to the existing tool.  Unless
   otherwise stated all of the current functions of the existing Nomcom
   tool need to be supported in the new tool as well.

If you have not served on a NomCom since the existing tool was deployed, then it will be difficult to understand the proposed tool requirements.  Is this acceptable?

Russ


On Jun 13, 2012, at 12:04 PM, The IESG wrote:

> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Requirements for IETF Nominations Committee tools'
>  <draft-krishnan-nomcom-tools-01.txt> as Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-07-11. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
>   This document defines the requirements for a set of tools for use by
>   the IETF Nominations Committee.
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-krishnan-nomcom-tools/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-krishnan-nomcom-tools/ballot/
> 
> No IPR declarations have been submitted directly on this I-D.