IETF Logo Mail Archive

Re: [Ianaplan] Comment on draft-ietf-ianaplan-icg-response-02

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 04 November 2014 19:47 UTC

Return-Path: <brian.e.carpenter@gmail.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 9F39A1A6FDD for <ianaplan@ietfa.amsl.com>; Tue, 4 Nov 2014 11:47:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] 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 n9K2QWKCYEoe for <ianaplan@ietfa.amsl.com>; Tue, 4 Nov 2014 11:47:18 -0800 (PST)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 742131A1BAA for <ianaplan@ietf.org>; Tue, 4 Nov 2014 11:47:18 -0800 (PST)
Received: by mail-pa0-f53.google.com with SMTP id kx10so15120274pab.12 for <ianaplan@ietf.org>; Tue, 04 Nov 2014 11:47:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=yobKZC7Xt4IZuwu7AkG4hzc9rt3hnGgJYaG7FIBxiN8=; b=ZthophrSpwPe9BEOUAcwlGRKanSx7ihRnkkik4ZiMePT1c1hZEoUnZ6HatbUykhyit kBP14MKiBBNimjimp2KrOWbvwVcDy2OyIDyYTbshQLI4TpZ5ll7l+E5f0UCJtj4ioME1 7KMdJXGkSsk3sXhJZ1+RhXJWbTxqHvGvihqb4lgxhSn5Oy/oeODHVWyyjHnkCaOo2mH7 nZvNrxTmlTMFYVxQUoEZZ0ynJbzqx1J+1wlHFNPXf9q7N/bIQy11Tm0T/SbdwwaF9U2x J9ylEoagUWf6A74++OSwG71JOX1wQqaNlSAa57vL6MEbfn84GXiXeMm/2iONCbjVhQHH VyBg==
X-Received: by 10.68.134.230 with SMTP id pn6mr52341345pbb.88.1415130437631; Tue, 04 Nov 2014 11:47:17 -0800 (PST)
Received: from [192.168.178.23] (210.199.69.111.dynamic.snap.net.nz. [111.69.199.210]) by mx.google.com with ESMTPSA id r4sm1052750pdm.93.2014.11.04.11.47.14 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Nov 2014 11:47:16 -0800 (PST)
Message-ID: <54592D44.1070707@gmail.com>
Date: Wed, 05 Nov 2014 08:47:16 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Patrik Fältström <paf@frobbit.se>
References: <18A7D037-9E3C-499B-B97A-475B61B70151@vigilsec.com> <8D5E7938-6A91-48A7-AA0D-EC231C128B71@isoc.org> <243D2B8A-73B4-44FC-A7BC-24DB9A1E9F90@frobbit.se>
In-Reply-To: <243D2B8A-73B4-44FC-A7BC-24DB9A1E9F90@frobbit.se>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/pYAj2B2qmcy20m8v_rZ0JvJ6WbU
Cc: "ianaplan@ietf.org" <ianaplan@ietf.org>, Russ Housley <housley@vigilsec.com>, Olaf Kolkman <kolkman@isoc.org>
Subject: Re: [Ianaplan] Comment on draft-ietf-ianaplan-icg-response-02
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: Tue, 04 Nov 2014 19:47:19 -0000

On 04/11/2014 20:23, Patrik Fältström wrote:
>> On 4 nov 2014, at 07:01, Olaf Kolkman <kolkman@isoc.org> wrote:
>>
>>> On Nov 4, 2014, at 06:47, Russ Housley <housley@vigilsec.com <mailto:housley@vigilsec.com>> wrote:
>>>
>>> "At present, there is a single IANA functions operator maintaining the IANA registries for the names, numbers, and protocol parameters.”
>>
>> I may be in the rough but there is this one registry (e164.arpa) that I would consider an IANA function (from the IETF perspective), still it is not in this bag of functions that is currently under US contract. Perhaps that can be recognized by 
>>
>> s/the IANA registries/the IANA registries under US contract/
> 
> As explained in for example SAC-067 and SAC-068 there are both parameters from IETF that are not managed by the IANA Function at ICANN (e.164 for example) and parameters managed by the IANA Function at ICANN while not covered by the contract.

The great advantage of hierarchical namespaces is that they are
hierarchies. So if the text doesn't reflect the fact that IANA
is only *required* to be the registrar for the top level of each
hierarchy, that is a bug (but one that any computer scientist
will autocorrect, as I certainly did when reading the draft).

    Brian

v2.23.0 | Report a Bug | By Email