[Ianaplan] Transition proposal for naming-related functions

Alissa Cooper <alissa@cooperw.in> Wed, 29 April 2015 13:25 UTC

Return-Path: <alissa@cooperw.in>
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 43A711A9144 for <ianaplan@ietfa.amsl.com>; Wed, 29 Apr 2015 06:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 vxBLE_cfohoE for <ianaplan@ietfa.amsl.com>; Wed, 29 Apr 2015 06:25:27 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94F1E1A9133 for <ianaplan@ietf.org>; Wed, 29 Apr 2015 06:25:27 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 117F8208F8 for <ianaplan@ietf.org>; Wed, 29 Apr 2015 09:25:27 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Wed, 29 Apr 2015 09:25:27 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h= content-type:date:from:message-id:mime-version:subject:to :x-sasl-enc:x-sasl-enc; s=mesmtp; bh=3QtBxNQLfw2PiT3iqnJN9WBZEu8 =; b=N7OlDDWJHawaEdWNu3pPy3wPMO8FrMZx8nQpsm/9Gw8waOBP8fXb/YZJGEo NBR+A3FYYc+1dNZsKJOVYpbDNIlZCcRmdxMoniTxPXAowBfV/JSmbY+uiSG9TlTH z3WMvktu6FpV7ayBelEYdX0KaGlwF8U7mf4Jx9ciSnqkNjdw=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=3Q tBxNQLfw2PiT3iqnJN9WBZEu8=; b=BH+jLbnN4aZ+2wFC0qVxbE3CDPSSoKfUru dxsNe4G7LjKJxvKb2ln2o8y9257jYDN4uS4ECLrWYN5cA6gXxvLPq6YMonMz6MPf B8nvAbfb66kq5vePR1Qrdz4tNJX6FGuVIlm/si2wYqklakwv1bFEWnn3aZK79ZL3 xgEZpIamE=
X-Sasl-enc: mJ6mvdWyGkKIxlPStbkiIaQ0bveUFFA58dCDoLaKQrOd 1430313926
Received: from [192.168.1.203] (unknown [24.6.61.198]) by mail.messagingengine.com (Postfix) with ESMTPA id 79872C0001A for <ianaplan@ietf.org>; Wed, 29 Apr 2015 09:25:26 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A6FB7C0A-6639-4FD9-99EB-B648AABFEF86"
Message-Id: <6FADE19B-E3BD-48F8-9A2D-91FA6F88E6DC@cooperw.in>
Date: Wed, 29 Apr 2015 06:25:32 -0700
To: "Ianaplan@Ietf. Org" <ianaplan@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/Zxymp0pSwA6fRtWCcmQJN2FPy50>
Subject: [Ianaplan] Transition proposal for naming-related functions
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: Wed, 29 Apr 2015 13:25:33 -0000

Dear IETF community,

You may be aware that the Cross Community Working Group developing the IANA stewardship transition proposal for naming-related functions has recently put its proposal out for public comment <https://www.icann.org/public-comments/cwg-stewardship-draft-proposal-2015-04-22-en>;. We wanted to highlight a few aspects of the proposal that we believe would benefit from review and perhaps comment by your community:

1) Overlaps and interdependencies (Section I.D and Annex A)
As in your community’s proposal, the CWG proposal contains information concerning overlaps and interdependencies with the other communities.

2) Post-Transition IANA (Section III)
The CWG is proposing that a new separate legal entity, Post-Transition IANA (PTI), would be formed as an affiliate of ICANN. The existing IANA naming functions, administrative staff and related resources, processes, data and know-how would be legally transferred into PTI. Your community may want to consider a number of associated implications:

* The likelihood that personnel and resources dedicated to the non-naming IANA functions would be moved to PTI. Your community may also want to consider its view on having all IANA functions provided by the same entity or allowing them to be separated.

* Contracting. For existing or new contracts your community may have related to the IANA functions, there may be multiple options available, including maintaining existing contracts with ICANN and letting them subcontract their execution to PTI, assigning an existing contract to PTI, or re-contracting with PTI.

* PTI Board. The composition of the PTI Board is not highly specified in the CWG proposal. There has been some discussion within the CWG about including representation for the RIRs and IETF on the PTI Board.

* PTI ownership. If the PTI is formed as an affiliate of ICANN as the CWG proposes, as a legal entity it would be wholly owned by ICANN. Your community may want to consider its view of this whole ownership versus joint ownership involving all or multiple communities.

3) Liaisons to IANA Functions Review Team (Section III.A.i.d and Annex F)
The CWG proposes that the performance of IANA be periodically reviewed post-transition and that the numbering and protocol parameter communities be offered the opportunity to appoint liaisons to the team performing reviews.

4) Customer Service Complaint Resolution Process (Annex I)
The CWG proposes a complain resolution process for naming-related services, but which is open to the protocol parameters and numbering resources communities.

5) Composition of the Customer Standing Committee (Section II.A.ii.a and Annex G)
The CWG proposes the creation of a Customer Standing Committee (CSC) to monitor the performance of the IANA naming function. The proposal mentions the possibility of IAB representation on the CSC. 

If the ICG can be of further assistance in coordinating your review or understanding of the CWG proposal, please let us know.

Thanks,
Alissa Cooper on behalf of the ICG