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

John Curran <jcurran@istaff.org> Sun, 09 November 2014 21:51 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 9E6931A8726 for <ianaplan@ietfa.amsl.com>; Sun, 9 Nov 2014 13:51:21 -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 I88R93P774gP for <ianaplan@ietfa.amsl.com>; Sun, 9 Nov 2014 13:51:19 -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 D63B01A6FFA for <ianaplan@ietf.org>; Sun, 9 Nov 2014 13:51:18 -0800 (PST)
Received: from mobile-166-176-56-84.mycingular.net ([166.176.56.84] helo=[172.20.10.2]) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1XnaOB-0005jE-AM; Sun, 09 Nov 2014 21:51:17 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 166.176.56.84
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX18uHv5eDnNNr0TPtBky6mBy
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: John Curran <jcurran@istaff.org>
X-Mailer: iPad Mail (12B410)
In-Reply-To: <85D607E0-4D3A-499E-87D1-036E0349D80E@gmail.com>
Date: Sun, 09 Nov 2014 11:51:10 -1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <CBBA1B51-145B-407D-A7E0-0E8CA7F7EFAF@istaff.org>
References: <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> <059f2b06a7b44f09b7568d8966861fb8@EX13-MBX-13.ad.syr.edu> <D0824FAD.137A42%jon.peterson@neustar.biz> <E314302D-5179-4899-9DB7-A3AF18C134E8@gmail.com> <20141108155153.GB37292@mx1.yitter.info> <D083864D.138D18%jon.peterson@neustar.biz> <A6D94EF5-BD92-4080-8C18-E415BD0BB880@isi.edu> <C78A1523-316F-46A1-9FCE-D0D205679C84@gmail.com> <13B26DE5-315D-453F-B89B-377CCD338ED9@isi.edu> <A7BD5ECF-11E4-42F1-A2B7-BF9B399635C3@gmail.com> <14D42443-53E7-49FA-88DD-7F4BB6BC2DF4@istaff.org> <545F69FB.5000501@meetinghouse.net> <7B719509-5A93-4B85-B7E2-262DDCB64461@istaff.org> <D0850842.138E23%jon.peterson@neustar.biz> <85D607E0-4D3A-499E-87D1-036E0349D80E@gmail.co m>
To: Bernard Aboba <bernard.aboba@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/2Fsw0LRTzOsr7f1Br15pkAHbC7Q
Cc: "ianaplan@ietf.org" <ianaplan@ietf.org>, Miles Fidelman <mfidelman@meetinghouse.net>, "Peterson, Jon" <jon.peterson@neustar.biz>
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: Sun, 09 Nov 2014 21:51:21 -0000

On Nov 9, 2014, at 10:59 AM, Bernard Aboba <bernard.aboba@gmail.com> wrote:
> 
> [BA] A good portion of the complexity here is we are talking about a domain name and trademark that is relevant to multiple communities.

Quite correct - the IANA mark and domain appears relevant to the IETF community,
due to the thousand or so protocol parameter registries published at that site and 
use of the name in many processes; to the Internet number community due to the 
publication of delegated number registries per RFC7020 and RFC7249; and to the 
DNS community due to their use with respect to administration of one particular 
protocol registry, i.e. the DNS root zone.

Personally, I would think it absurd for the IETF to abandon use of the term IANA
simply to avoid discussing arrangements for sharing its use, but then again, in 
the end it is the IETF community's call to make, as interpreted by the leadership.

/John

Disclaimer: my views alone.