Re: [Ianaplan] Adrian Farrel's No Objection on charter-ietf-ianaplan-00-04: (with COMMENT)

Russ Housley <housley@vigilsec.com> Thu, 04 September 2014 13:50 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D68C1A88BF; Thu, 4 Sep 2014 06:50:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZScb7nUwujvm; Thu, 4 Sep 2014 06:50:52 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 575D91A88CA; Thu, 4 Sep 2014 06:50:51 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 0A5B2F9C06B; Thu, 4 Sep 2014 09:50:41 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id FlkBk9TQvZBI; Thu, 4 Sep 2014 09:50:15 -0400 (EDT)
Received: from 81.213.24.159.dynamic.ttnet.com.tr (unknown [81.213.24.159]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 9A938F9C059; Thu, 4 Sep 2014 09:50:13 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset="us-ascii"
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20140904132124.24134.4210.idtracker@ietfa.amsl.com>
Date: Thu, 04 Sep 2014 09:49:50 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DCEA0F3F-594F-4802-B2DB-C35BC8E7204F@vigilsec.com>
References: <20140904132124.24134.4210.idtracker@ietfa.amsl.com>
To: Adrian Farrel <adrian@olddog.co.uk>
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/utwHrWH-2pIUFtEthPogWCVHV0w
Cc: ianaplan@ietf.org, iana-strategy@i1b.org, The IESG <iesg@ietf.org>
Subject: Re: [Ianaplan] Adrian Farrel's No Objection on charter-ietf-ianaplan-00-04: (with COMMENT)
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2014 13:50:54 -0000

I'd like to see it published as an RFC at the point in time that the proposal is actually submitted to NTIA.

Russ


On Sep 4, 2014, at 9:21 AM, Adrian Farrel wrote:

> Adrian Farrel has entered the following ballot position for
> charter-ietf-ianaplan-00-04: No Objection
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> 
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/charter-ietf-ianaplan/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Notwithstanding that "IETF consensus document" normally means "an RFC on
> which there has been IETF last call and where there is consensus for
> publication" I feel that
>   The IANAPLAN working group is chartered to produce an IETF consensus
>   document
> needs to be clarified since it leave ambiguity as to whether an RFC is
> the intended output. there are three options (pick one!)
> - "...that will be published as an RFC"
> - "...that may be published as an RFC"
> - "...that will be produced as an Internet-Draft and submitted to the
> ICANN thingy committee when consensus has been reached."
> 
> ---
> 
> In view of Joel's comment about timeliness, I wonder whether
> micro-management through the milestones might be helpful.
> 
>