IETF Logo Mail Archive

Re: [Ianaplan] Transition proposal for naming-related functions

John Curran <jcurran@arin.net> Tue, 05 May 2015 21:02 UTC

Return-Path: <jcurran@arin.net>
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 C8D131AD358 for <ianaplan@ietfa.amsl.com>; Tue, 5 May 2015 14:02:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] 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 6X7Nw5zkspkI for <ianaplan@ietfa.amsl.com>; Tue, 5 May 2015 14:02:22 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 520771A8876 for <ianaplan@ietf.org>; Tue, 5 May 2015 14:02:22 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id E9A8F164EAE; Tue, 5 May 2015 17:02:21 -0400 (EDT)
Received: from chaedge02.corp.arin.net (chaedge02.corp.arin.net [192.149.252.119]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTP id 1987D164E6D for <ianaplan@ietf.org>; Tue, 5 May 2015 17:02:21 -0400 (EDT)
Received: from CHACAS01.corp.arin.net (10.1.30.107) by chaedge02.corp.arin.net (192.149.252.119) with Microsoft SMTP Server (TLS) id 14.3.210.2; Tue, 5 May 2015 17:07:30 -0400
Received: from CHAMBX01.corp.arin.net ([fe80::1cef:1d7:cca9:5953]) by CHACAS01.corp.arin.net ([fe80::a98b:1e52:e85a:5979%13]) with mapi id 14.03.0224.002; Tue, 5 May 2015 17:02:20 -0400
From: John Curran <jcurran@arin.net>
To: "ianaplan@ietf.org" <ianaplan@ietf.org>
Thread-Topic: [Ianaplan] Transition proposal for naming-related functions
Thread-Index: AQHQhrRXm3oLlNRnoEWK/fZWUSrnF51tjfKAgAAOBICAAIc6AA==
Date: Tue, 05 May 2015 21:02:19 +0000
Message-ID: <53C0A048-606D-4D43-A9B7-057F487616FB@arin.net>
References: <6FADE19B-E3BD-48F8-9A2D-91FA6F88E6DC@cooperw.in> <554637C4.2010400@gondrom.org> <64F5CADC-5739-4CB1-B2E3-BAA3B21DA0EB@cooperw.in> <C6F030D4-58DF-4B2B-969E-6D4F2B00C742@shinkuro.com> <E381F582-33AE-40DF-A66C-8F8631064ED3@arin.net> <CAD_dc6icf=iXDCj2o-dcDiGR2vWM7kHAuh1D6c==wakj-nPzMA@mail.gmail.com> <246AEA8E-5D8F-481F-AF1B-1307845CADEB@arin.net>
In-Reply-To: <246AEA8E-5D8F-481F-AF1B-1307845CADEB@arin.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.149.252.96]
Content-Type: multipart/alternative; boundary="_000_53C0A048606D4D43A9B7057F487616FBarinnet_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/AvWttp8jyv5ZOO-IsA5QHLpI7LQ>
Subject: Re: [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: Tue, 05 May 2015 21:02:24 -0000

On May 5, 2015, at 8:58 AM, John Curran <jcurran@arin.net<mailto:jcurran@arin.net>> wrote:

...
   Note also that there will shortly be another related IANA stewardship transition draft
   released for comment (from the CCWG) which proposes some changes to ICANN’s
   governance structures, and that document should also be reviewed once available
   for comment.

While the protocol parameter community’s IANA Stewardship transition proposal (i.e. the
IANAplan proposal) relies predominantly upon contractual measures for purposes of IANA
accountability to the affected community, there may be some on this list interested in the
ICANN accountability measures being discussed in in the CCWG -

<https://www.icann.org/news/announcement-3-2015-05-04-en>
"The CCWG-Accountability requests community feedback on the proposed enhancements to ICANN's accountability framework it has identified as essential to happen or be committed to before the IANA Stewardship Transition takes place (Work Stream 1). Your input will help the CCWG-Accountability to improve its proposal and carry on with next steps, including Chartering Organizations' endorsement of the CCWG-Accountability output before it is submitted to the ICANN Board. This comment period is an opportunity for you to make your voice heard and to shape the outcome of the CCWG-Accountability work. ...”

<https://www.icann.org/public-comments/ccwg-accountability-draft-proposal-2015-05-04-en>
“… The CCWG-Accountability Draft Report is the Document on which the CCWG-Accountability seeks your input and feedback. For ease of reading in this Public Comment period, the Draft Report is available in two document styles:

• CCWG-Accountability Draft Report (without annexes): https://www.icann.org/en/system/files/files/cwg-accountability-draft-proposal-without-annexes-04may15-en.pdf [PDF, 1.72 MB]
• CCWG-Accountability Draft Report (with annexes): https://www.icann.org/en/system/files/files/cwg-accountability-draft-proposal-with-annexes-04may15-en.pdf [PDF, 2.05 MB] "

FYI,
/John

John Curran
President and CEO
ARIN

v2.23.0 | Report a Bug | By Email