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

Olaf Kolkman <kolkman@isoc.org> Thu, 06 November 2014 00:25 UTC

Return-Path: <kolkman@isoc.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 6D54C1A1A23 for <ianaplan@ietfa.amsl.com>; Wed, 5 Nov 2014 16:25:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-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 aARl0Te2xk4W for <ianaplan@ietfa.amsl.com>; Wed, 5 Nov 2014 16:25:08 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0655.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::655]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2846F1A1A2C for <ianaplan@ietf.org>; Wed, 5 Nov 2014 16:25:08 -0800 (PST)
Received: from CO1PR06MB426.namprd06.prod.outlook.com (10.141.74.16) by CO1PR06MB425.namprd06.prod.outlook.com (10.141.74.26) with Microsoft SMTP Server (TLS) id 15.1.11.14; Thu, 6 Nov 2014 00:24:44 +0000
Received: from CO1PR06MB426.namprd06.prod.outlook.com ([169.254.10.166]) by CO1PR06MB426.namprd06.prod.outlook.com ([169.254.10.166]) with mapi id 15.01.0011.000; Thu, 6 Nov 2014 00:24:44 +0000
From: Olaf Kolkman <kolkman@isoc.org>
To: "ianaplan@ietf.org" <ianaplan@ietf.org>
Thread-Topic: making ARPA explicit (Re: [Ianaplan] draft-ietf-ianaplan-icg-response-02 working group last call)
Thread-Index: AQHP+VgPKvAEx3kyRUKxUJXYNVIPhA==
Date: Thu, 06 Nov 2014 00:24:43 +0000
Message-ID: <830AC04C-6020-4E42-AAC2-A0D3AF5E3B02@isoc.org>
References: <6ACE138D-0969-4D8F-9A64-3D1FBB96885A@viagenie.ca>
In-Reply-To: <6ACE138D-0969-4D8F-9A64-3D1FBB96885A@viagenie.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [221.164.35.10]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:CO1PR06MB425;
x-exchange-antispam-report-test: UriScan:;
x-forefront-prvs: 0387D64A71
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(199003)(189002)(51704005)(107886001)(66066001)(450100001)(21056001)(82746002)(99286002)(97736003)(95666004)(2351001)(20776003)(77096003)(64706001)(87936001)(105586002)(101416001)(2501002)(2656002)(83716003)(77156002)(122556002)(50986999)(230783001)(99396003)(54356999)(76176999)(92726001)(92566001)(19580395003)(31966008)(33656002)(120916001)(40100003)(106356001)(107046002)(229853001)(106116001)(86362001)(110136001)(4396001)(36756003)(46102003)(62966003)(15202345003)(15975445006)(104396001); DIR:OUT; SFP:1101; SCL:1; SRVR:CO1PR06MB425; H:CO1PR06MB426.namprd06.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
Content-Type: text/plain; charset="utf-8"
Content-ID: <FA8FF15DA69B8F43B4CCC95DD10B7D08@namprd06.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/yCAU6l8hO7wEF5Bv56mWa7BfSds
Subject: [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 00:25:11 -0000

> 
> 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)