IETF Logo Mail Archive

Re: [Ianaplan] control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)

Andrew Sullivan <ajs@crankycanuck.ca> Thu, 06 November 2014 18:05 UTC

Return-Path: <ajs@crankycanuck.ca>
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 063DC1A8911 for <ianaplan@ietfa.amsl.com>; Thu, 6 Nov 2014 10:05:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level:
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] 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 o-1zHL9p4CRS for <ianaplan@ietfa.amsl.com>; Thu, 6 Nov 2014 10:05:15 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25D5D1A8910 for <ianaplan@ietf.org>; Thu, 6 Nov 2014 10:05:14 -0800 (PST)
Received: from crankycanuck.ca (nat-08-mht.dyndns.com [216.146.45.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id DA82E8A031 for <ianaplan@ietf.org>; Thu, 6 Nov 2014 18:05:13 +0000 (UTC)
Date: Thu, 06 Nov 2014 13:05:12 -0500
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: ianaplan@ietf.org
Message-ID: <20141106180511.GD33901@crankycanuck.ca>
References: <545A208A.7040304@meetinghouse.net> <631e3e3d29c843bd9c23151c63612989@EX13-MBX-13.ad.syr.edu> <20141105154903.GI30379@mx1.yitter.info> <498a39b81b774192bd2d609b3feab35f@EX13-MBX-13.ad.syr.edu> <20141105234444.GM31320@crankycanuck.ca> <545ABCB0.5080206@meetinghouse.net> <8f3dcda6c3db4cd8be1b77444f987d59@EX13-MBX-13.ad.syr.edu> <D0805C27.136BE7%jon.peterson@neustar.biz> <7F52A930-DD6F-4D0D-8278-A021CF8A466C@istaff.org> <D080D78C.136C6E%jon.peterson@neustar.biz>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <D080D78C.136C6E%jon.peterson@neustar.biz>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/SwBEjFuZiqrr2YYVPZ2wpdGQF80
Subject: Re: [Ianaplan] control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)
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, 06 Nov 2014 18:05:19 -0000

On Thu, Nov 06, 2014 at 03:54:31PM +0000, Peterson, Jon wrote:
> I'm totally fine with detailing the IETF's present and existing use of the
> IANA 

In my opinion, such detail is already there.  But if people have
specific words in mind intended to make that clearer, I'm certainly
not opposed to that in principle.

A

-- 
Andrew Sullivan
ajs@crankycanuck.ca

v2.23.0 | Report a Bug | By Email