Re: [Ianaplan] making ARPA explicit (Re: draft-ietf-ianaplan-icg-response-02 working group last call)

Andrei Robachevsky <andrei.robachevsky@gmail.com> Sat, 08 November 2014 21:19 UTC

Return-Path: <andrei.robachevsky@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 0B2281A01EC for <ianaplan@ietfa.amsl.com>; Sat, 8 Nov 2014 13:19:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] 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 Hnl8s8p0n_5L for <ianaplan@ietfa.amsl.com>; Sat, 8 Nov 2014 13:19:32 -0800 (PST)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC3661A01E7 for <ianaplan@ietf.org>; Sat, 8 Nov 2014 13:19:31 -0800 (PST)
Received: by mail-pa0-f45.google.com with SMTP id lf10so5687987pab.18 for <ianaplan@ietf.org>; Sat, 08 Nov 2014 13:19:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=sR5RVbDD2BPIOF+A3xE6u0HD2OBNYE4Ui2MdscjHoNk=; b=A77S/IIIKaxH0JRrZlot1e5OtsXj2tIziiWgoWBCGrFH+HC4ZpgfhSmz1G1hsRImyk 8eEqfrGn4SVF7DUCXJDhdHvp5JG0GRQhmeatwg1F0v26T5H/sMNMWqBkDxh9fjl/C0Gy 9Y80wIkE/9/0nuqDdVVn27DA8PfNjz+B4ZBlQjRzLKAt8hTx0Rv8XrIzMcSZYtyJyLOa UVD8Tbytoy118M0dBcImiuoG2OGHuef13PKyS0rqkLRT9PSgVd/r4+aeYD7fyypg6G4k MtGeODNg2fcuVS/i0pn+2C5izyq4YMNguBSC+myWYgCECDCGs0ISNmk9LP5s1kiBQVxy ozBw==
X-Received: by 10.66.140.8 with SMTP id rc8mr21653186pab.83.1415481571190; Sat, 08 Nov 2014 13:19:31 -0800 (PST)
Received: from ISOC-A1FD58.local (ip-64-134-234-18.public.wayport.net. [64.134.234.18]) by mx.google.com with ESMTPSA id dx10sm12357514pab.38.2014.11.08.13.19.29 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 08 Nov 2014 13:19:30 -0800 (PST)
Message-ID: <545E88E1.50609@gmail.com>
Date: Sat, 08 Nov 2014 22:19:29 +0100
From: Andrei Robachevsky <andrei.robachevsky@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Olaf Kolkman <kolkman@isoc.org>, "ianaplan@ietf.org" <ianaplan@ietf.org>
References: <6ACE138D-0969-4D8F-9A64-3D1FBB96885A@viagenie.ca> <830AC04C-6020-4E42-AAC2-A0D3AF5E3B02@isoc.org>
In-Reply-To: <830AC04C-6020-4E42-AAC2-A0D3AF5E3B02@isoc.org>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="EmAPrSmNdKAIvwnfQQmcHjIslTJUc7j87"
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/MCquFNc8qIs2MwxaI-A0cT8Xw1Q
Subject: Re: [Ianaplan] making ARPA explicit (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: Sat, 08 Nov 2014 21:19:34 -0000

Olaf Kolkman wrote on 06/11/14 01:24:
[...]
> CONTEXT:
>    >>> Which IANA service or activity (identified in Section I) is
>    >>> affected.
> 
> 
>    IETF Response: the protocol parameters registries.
> 
> 
> 
> OLD:
>   IETF Response: the protocol parameters registries.
> 
> NEW:
>   IETF Response: the protocol parameters registries including the .ARPA domain.

Yes, .arpa needs to be mentioned. And perhaps it is better to mention it
in the answer to the question "What registries are involved in providing
the service or activity".

I already suggested a more elaborate definition of what protocol
parameter registries entail (see
http://www.ietf.org/mail-archive/web/ianaplan/current/msg00772.html) and
.ARPA will be there a welcome addition.

Specifically:

"The protocol parameters registries are the product of IETF work. These
also include the top-level registry for the entire IP address space and
some of its sub-registries, AS number space, a number of special use
registries with regard to domain names and the .ARPA domain. For more
detail please refer to the documentation in the "overlaps or
interdependencies" section."

My question here, when we say .ARPA domain, do we mean the whole
sub-tree? Do we need to mention that here explicitly?


My suggestion would be that at the same time we leave the heading the
the main activity as simply "protocol parameters registries", which is
consistent with the high-level division of IANA functions.

Andrei