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

JFC Morfin <jefsey@jefsey.com> Thu, 04 September 2014 18:37 UTC

Return-Path: <jefsey@jefsey.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 CE3E51A0190; Thu, 4 Sep 2014 11:37:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.631
X-Spam-Level: *
X-Spam-Status: No, score=1.631 tagged_above=-999 required=5 tests=[BAYES_50=0.8, IP_NOT_FRIENDLY=0.334, MISSING_MID=0.497] autolearn=no
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 B5gbAZPz0mrV; Thu, 4 Sep 2014 11:37:00 -0700 (PDT)
Received: from host.presenceweb.org (host.presenceweb.org [67.222.106.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 007511A013B; Thu, 4 Sep 2014 11:36:59 -0700 (PDT)
Received: from 196.103.176.95.rev.sfr.net ([95.176.103.196]:56274 helo=GHM-SAM.dot.dj) by host.presenceweb.org with esmtpa (Exim 4.82) (envelope-from <jefsey@jefsey.com>) id 1XPbtx-0001yA-Nt; Thu, 04 Sep 2014 11:36:58 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 04 Sep 2014 19:46:11 +0200
To: Russ Housley <housley@vigilsec.com>, Adrian Farrel <adrian@olddog.co.uk>
From: JFC Morfin <jefsey@jefsey.com>
In-Reply-To: <DCEA0F3F-594F-4802-B2DB-C35BC8E7204F@vigilsec.com>
References: <20140904132124.24134.4210.idtracker@ietfa.amsl.com> <DCEA0F3F-594F-4802-B2DB-C35BC8E7204F@vigilsec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.presenceweb.org
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Get-Message-Sender-Via: host.presenceweb.org: authenticated_id: intl+dot.dj/only user confirmed/virtual account not confirmed
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/uOg-JN7F-1fCUlDAmSemFVwzz4I
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 18:37:00 -0000
X-Message-ID:
Message-ID: <20140904183707.21978.25649.ARCHIVE@ietfa.amsl.com>

At 15:49 04/09/2014, Russ Housley wrote:
>I'd like to see it published as an RFC at the point in time that the 
>proposal is actually submitted to NTIA.

+1
However it should be published with the indication that the IETF 
Trust puts it in public domain, or at least authorizes derivative work  .
jfc


>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.
> >
> >
>
>_______________________________________________
>Ianaplan mailing list
>Ianaplan@ietf.org
>https://www.ietf.org/mailman/listinfo/ianaplan