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

Bernard Aboba <bernard.aboba@gmail.com> Thu, 06 November 2014 02:04 UTC

Return-Path: <bernard.aboba@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 28BD01A004E for <ianaplan@ietfa.amsl.com>; Wed, 5 Nov 2014 18:04:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_QP_LONG_LINE=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 iIZJ5WWcSYFv for <ianaplan@ietfa.amsl.com>; Wed, 5 Nov 2014 18:04:54 -0800 (PST)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBE531A003B for <ianaplan@ietf.org>; Wed, 5 Nov 2014 18:04:40 -0800 (PST)
Received: by mail-pa0-f42.google.com with SMTP id bj1so206474pad.15 for <ianaplan@ietf.org>; Wed, 05 Nov 2014 18:04:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=3UsFJoJ2icDIDoDTAHG/53dmyO/3zbHrJiqtSJWPYlQ=; b=fqxoqhC3eF1NMdlKQmtfmdwJFi0QIHjk4gwHcBmRyVe9KleXyynFJAhMak1WMJnySt uM9J/cFzVpiFGbtPz2nwDwps73mqzMUSH/ICXn2U+imCLzIIJWp3aQd2WLVj8xvezj1Q yz+/16NGYVd0AmEGv4doftBMiI8wY3CIa4EJ3l/WzYa5imhtch1uv8dkXYaUVu+bFZ0+ b1AMIYDYKy2TF9jxKskcaebjWH+K+L80NG3AFVLdtLoDUwbXprdqaycOxV4ZoucoDefH k4l7497MVFWf7GwpPtQ6mGugHuJUFFcCSfN/qIatAYJd1s6bV2IhSl5NCVY90fiOVJE6 bv1A==
X-Received: by 10.67.22.1 with SMTP id ho1mr1398222pad.4.1415239479853; Wed, 05 Nov 2014 18:04:39 -0800 (PST)
Received: from [10.19.202.238] (mobile-166-171-121-003.mycingular.net. [166.171.121.3]) by mx.google.com with ESMTPSA id r4sm4274561pdm.93.2014.11.05.18.04.38 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 05 Nov 2014 18:04:38 -0800 (PST)
References: <6ACE138D-0969-4D8F-9A64-3D1FBB96885A@viagenie.ca> <830AC04C-6020-4E42-AAC2-A0D3AF5E3B02@isoc.org>
Mime-Version: 1.0 (1.0)
In-Reply-To: <830AC04C-6020-4E42-AAC2-A0D3AF5E3B02@isoc.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <69F4F598-F6B7-419B-B494-17FE23B79107@gmail.com>
X-Mailer: iPhone Mail (12B411)
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Wed, 05 Nov 2014 18:04:32 -0800
To: Olaf Kolkman <kolkman@isoc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/SdBUri2WO_Q78SPlPtUmQl_qgVs
Cc: "ianaplan@ietf.org" <ianaplan@ietf.org>
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: Thu, 06 Nov 2014 02:04:57 -0000

Yes, .ARPA was left out and needs to be put in.



On Nov 5, 2014, at 4:24 PM, Olaf Kolkman <kolkman@isoc.org> wrote:

>> 
>> Draft: http://www.ietf.org/id/draft-ietf-ianaplan-icg-response-02.txt
>> 
>> Please send comments to the list.
> 
> 
> Dear Colleagues,
> 
> I have two suggestions about .ARPA. Apologies for not bringing this up earlier and potentially overlooking previous discussion on list (there are some hints of similar thoughts on the list, but no concrete suggestions for inclusion).
> 
> 
> 
> 1. Identifying the activity.
> 
> 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.
> ALTERNATIVE:
>  IETF Response: the protocol parameters registries and the .ARPA domain.
> 
> MOTIVATION:
> Make explicit that the .ARPA domain is an integral part of the IETF side of the plan. The contracts mentions the protocol parameters separately from the .ARPA domain and this intends to avoid confusion upstream. I tend to think of .ARPA domain as being a protocol parameter registry with an alternative publication mechanism, hence the ‘including’ but ‘and’ may be more clear.
> 
> 
> The same modification can be made other parts of the document. I leave that trade-off to the editors.
> 
> 
> 
> 2. .ARPA as an interdependency.
> 
> I am less sure about this suggestion than the above.
> 
> Context:
>>>> 
>>>> A description of any overlaps or interdependencies between your
>>>> IANA requirements and the functions required by other customer
>>>> communities
> 
> 
> A new bullet point that communicates that we rely on the names side of the IANA house for delegation to the parameter operator and that the number communities rely on further delegation (in-addr.arpa and ip6.arpa) could be added?
> 
> 
> In addition 
> 
> Context:
>  To address concerns regarding appropriate contingencies to transition
>   to another operator, the IAOC is asked to conclude a supplemental
>   agreement that-
> 
> you may want to add:
> 
> 3. requires the redelegation of the .ARPA domain to the subsequent operators.
> 
> 
> 
> —Olaf
> 
> — — — — — — — — — — 
> Olaf Kolkman
> (on personal title)
> 
> 
> 
> 
> _______________________________________________
> Ianaplan mailing list
> Ianaplan@ietf.org
> https://www.ietf.org/mailman/listinfo/ianaplan