Re: [Ianaplan] A draft for your review

Avri Doria <avri@acm.org> Sun, 02 November 2014 01:29 UTC

Return-Path: <avri@acm.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 85EF01A2130 for <ianaplan@ietfa.amsl.com>; Sat, 1 Nov 2014 18:29:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.034
X-Spam-Level:
X-Spam-Status: No, score=-0.034 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_45=0.6, J_CHICKENPOX_47=0.6, SPF_SOFTFAIL=0.665] 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 FBBY-Ajua1L8 for <ianaplan@ietfa.amsl.com>; Sat, 1 Nov 2014 18:29:28 -0700 (PDT)
Received: from atl4mhob19.myregisteredsite.com (atl4mhob19.myregisteredsite.com [209.17.115.112]) by ietfa.amsl.com (Postfix) with ESMTP id 41E811A212D for <ianaplan@ietf.org>; Sat, 1 Nov 2014 18:29:27 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.208]) by atl4mhob19.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id sA21TPoE014582 for <ianaplan@ietf.org>; Sat, 1 Nov 2014 21:29:25 -0400
Received: (qmail 3670 invoked by uid 0); 2 Nov 2014 01:29:25 -0000
X-TCPREMOTEIP: 210.91.168.1
X-Authenticated-UID: avri@ella.com
Received: from unknown (HELO ?127.0.0.1?) (avri@ella.com@210.91.168.1) by 0 with ESMTPA; 2 Nov 2014 01:29:25 -0000
Message-ID: <545588EE.20404@acm.org>
Date: Sun, 02 Nov 2014 10:29:18 +0900
From: Avri Doria <avri@acm.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: ianaplan@ietf.org
References: <54017E09.8060504@cisco.com> <6.2.5.6.2.20140830052032.0c96c880@resistor.net> <54047E4A.30503@cisco.com> <6.2.5.6.2.20140901094544.0b305698@resistor.net> <54059587.8070608@cisco.com> <6.2.5.6.2.20141024004255.0b5ef5d8@resistor.net> <4C1255B9-68C3-45D5-A618-2C7553386DF4@gmail.com> <54522E43.5020709@acm.org> <545428AC.3090802@gmail.com> <7471A339-3938-4D65-81ED-9E27A80EC32B@virtualized.org> <54546F63.1060708@cisco.com> <F0EE4BAE-0D60-4DB1-8FEA-C63E936B6150@virtualized.org> <54547321.8010203@cisco.com> <DD3A14C7-BD36-4371-8448-18861CB97CCD@virtualized.org> <DB420A8B-58DC-49CA-9129-5551C0F67335@viagenie.ca> <6EF2CB0E-E705-46B9-B0AE-6F9BEB73D94E@gmail.com>
In-Reply-To: <6EF2CB0E-E705-46B9-B0AE-6F9BEB73D94E@gmail.com>
Content-Type: multipart/alternative; boundary="------------000804070701070108040701"
X-Antivirus: avast! (VPS 141101-1, 11/02/2014), Outbound message
X-Antivirus-Status: Not-Tested
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/PXbxTro5c0FraAXgWOOfYZkK8Yk
Subject: Re: [Ianaplan] A draft for your review
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, 02 Nov 2014 01:29:30 -0000

Hi,

Please pardon me for still being slow to understand the implications, or
lack thereof.

In the case of a decomposed IANA, will the IETF still have operational
change access to the name registries?

Or are we arguing that RIRs and [cc,g]NSO+ only have access to their own
registries, but that the IETF maintains operational change access to all
3?  If so would there  need to be additional MOUs &c. with IANA.names
and IANA.numbers?

avri

On 02-Nov-14 00:51, Suzanne Woolf wrote:
> My suggested edit:
>
> * I favor preserving the reference to participation in the IETF by ICANN and RIR staff and community participants; it strengthens the point that they are part of the coordination we're discussing in this section.
>
> * I suggest new text for the first bullet point:
> 	"The IETF has specified a number of special use registries with regard to domain names.  These registries require coordination with ICANN as the policy authority for the DNS root [RFC2860], including community groups that are responsible for ICANN policy on domain names such as the GNSO and the ccNSO.  There are already mechanisms in place to perform this coordination, and the capacity to modify them to meet new conditions as they might arise." [RFC6761, http://www.ietf.org/liaison/managers.html]