Re: [Ianaplan] Fwd: For your Information: CWG-Stewardship Response for Chartering Organization Consideration and Approval
Andrew Sullivan <ajs@anvilwalrusden.com> Fri, 19 June 2015 15:54 UTC
Return-Path: <ajs@anvilwalrusden.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 5A37E1A910B for <ianaplan@ietfa.amsl.com>; Fri, 19 Jun 2015 08:54:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.13
X-Spam-Level:
X-Spam-Status: No, score=-1.13 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_SORBS_WEB=0.77] 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 1dJwe_aODoMQ for <ianaplan@ietfa.amsl.com>; Fri, 19 Jun 2015 08:54:00 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [IPv6:2600:3c03::f03c:91ff:fedf:cfab]) by ietfa.amsl.com (Postfix) with ESMTP id 608721A9107 for <ianaplan@ietf.org>; Fri, 19 Jun 2015 08:54:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id DD863105DD for <ianaplan@ietf.org>; Fri, 19 Jun 2015 15:53:59 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hvi91k8aqqzG for <ianaplan@ietf.org>; Fri, 19 Jun 2015 15:53:59 +0000 (UTC)
Received: from mx2.yitter.info (unknown [89.246.150.136]) by mx2.yitter.info (Postfix) with ESMTPSA id B749110010 for <ianaplan@ietf.org>; Fri, 19 Jun 2015 15:53:58 +0000 (UTC)
Date: Fri, 19 Jun 2015 17:53:56 +0200
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ianaplan@ietf.org
Message-ID: <20150619155355.GI17513@mx2.yitter.info>
References: <D1A45F80.1B274%grace.abuhamad@icann.org> <90E3156B-428B-4A61-92B7-BAC932842FB5@viagenie.ca> <557F63E2.40302@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <557F63E2.40302@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/mZdtNbsfo6eWCAkFgCAQb5-Yeg8>
Subject: Re: [Ianaplan] Fwd: For your Information: CWG-Stewardship Response for Chartering Organization Consideration and Approval
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: Fri, 19 Jun 2015 15:54:01 -0000
On Tue, Jun 16, 2015 at 11:46:42AM +1200, Brian E Carpenter wrote: > "The existing IANA functions department, administrative staff, and > related resources, processes, data, and know-how will be legally > transferred to PTI.[8] > > [8] In the case of any existing ICANN contracts, MoUs or other > arrangements that relate to the IANA functions, these could be > assigned to and assumed by PTI, replaced by new arrangements at > the PTI level or remain at ICANN with a subcontract to PTI." > > That appears to be suggesting that the entirety of IANA, not just > the naming functions, should be transferred to PTI. That seems > to be beyond the claimed scope of the proposal. I don't think it is a scope problem. On my reading, the CWG's proposal in effect has two parts: 1. The IANA functions MUST move from ICANN to some other organization. This provides a separation of the naming-policy-community organization from the organization that delivers IANA. The idea is that this is a necessary condition for the rest of the proposal. 2. The details of how the naming community wants to interact with the resulting IANA functions operator. The limitation of scope is really over (2), and not (1). At least, that's how I interepret the proposal. Best regards, A (as ever, speaking just for me) -- Andrew Sullivan ajs@anvilwalrusden.com
- [Ianaplan] Fwd: For your Information: CWG-Steward… Marc Blanchet
- Re: [Ianaplan] Fwd: For your Information: CWG-Ste… Brian E Carpenter
- Re: [Ianaplan] Fwd: For your Information: CWG-Ste… Andrew Sullivan
- Re: [Ianaplan] Fwd: For your Information: CWG-Ste… Brian E Carpenter
- Re: [Ianaplan] Fwd: For your Information: CWG-Ste… Avri Doria
- Re: [Ianaplan] Fwd: For your Information: CWG-Ste… Richard Hill
- Re: [Ianaplan] Fwd: For your Information: CWG-Ste… Milton L Mueller
- Re: [Ianaplan] Fwd: For your Information: CWG-Ste… Andrew Sullivan
- Re: [Ianaplan] Fwd: For your Information: CWG-Ste… John C Klensin
- Re: [Ianaplan] Fwd: For your Information: CWG-Ste… Brian E Carpenter