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

"Adrian Farrel" <adrian@olddog.co.uk> Thu, 04 September 2014 13:21 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 2BCBF1A88AD; Thu, 4 Sep 2014 06:21:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id CAznYu2BhBRM; Thu, 4 Sep 2014 06:21:24 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E27871A88AC; Thu, 4 Sep 2014 06:21:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Adrian Farrel <adrian@olddog.co.uk>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.2.p6
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140904132124.24134.4210.idtracker@ietfa.amsl.com>
Date: Thu, 04 Sep 2014 06:21:24 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/J-l7v4RyoUCMUhV1ovKnSU23MBo
Cc: ianaplan@ietf.org, iana-strategy@i1b.org
Subject: [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
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:21:29 -0000

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:


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