IETF Logo Mail Archive

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

John Curran <jcurran@istaff.org> Thu, 06 November 2014 22:04 UTC

Return-Path: <jcurran@istaff.org>
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 170CC1A913D for <ianaplan@ietfa.amsl.com>; Thu, 6 Nov 2014 14:04:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 De3930mZ2wlJ for <ianaplan@ietfa.amsl.com>; Thu, 6 Nov 2014 14:04:04 -0800 (PST)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F9C91A8703 for <ianaplan@ietf.org>; Thu, 6 Nov 2014 14:04:04 -0800 (PST)
Received: from [80.169.25.242] (helo=[192.168.46.56]) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1XmV9v-000M6N-Fw; Thu, 06 Nov 2014 22:04:03 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 80.169.25.242
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+MpdmDv3fDo5aYL09FDSsS
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
From: John Curran <jcurran@istaff.org>
In-Reply-To: <20141106180511.GD33901@crankycanuck.ca>
Date: Thu, 06 Nov 2014 22:04:03 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <A47A83C1-4485-43DF-93F2-B2FFF599E324@istaff.org>
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> <20141106180511.GD33901@crankycanuck.ca>
To: Andrew Sullivan <ajs@crankycanuck.ca>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/VuRGauIpHLe1k2E5pBj6TL7MrGY
Cc: ianaplan@ietf.org
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 22:04:06 -0000

On Nov 6, 2014, at 6:05 PM, Andrew Sullivan <ajs@crankycanuck.ca> wrote:
> 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.

Excellent.

One option would be to add a sentence after the list of bullets that
presently end the Section I "Description of Community’s Use of IANA 
Functions" draft RFP response text, i.e. further elaboration of the 
'overlaps or interdependencies between your IANA requirements and 
 the functions required by other customer communities'...

Example text -

'The IETF community presently accesses the protocol parameter registries 
 via references based on iana.org domain name, and makes use of the term
"IANA" in the protocol parameter registry processes [RFC5226].' 

/John

Disclaimer: my views alone.

v2.23.0 | Report a Bug | By Email