[Ianaplan] Fwd: [IAB] IAB IANA Evolution Program commment on CWG Stewardship Draft Proposal

Russ Housley <housley@vigilsec.com> Wed, 20 May 2015 14:49 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 026661A87C7 for <ianaplan@ietfa.amsl.com>; Wed, 20 May 2015 07:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id UdK_9-10vmp8 for <ianaplan@ietfa.amsl.com>; Wed, 20 May 2015 07:49:22 -0700 (PDT)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net []) by ietfa.amsl.com (Postfix) with ESMTP id 39A921A87B8 for <ianaplan@ietf.org>; Wed, 20 May 2015 07:49:22 -0700 (PDT)
Received: from localhost (unknown []) by odin.smetech.net (Postfix) with ESMTP id E6D859A404A for <ianaplan@ietf.org>; Wed, 20 May 2015 10:49:11 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([]) by localhost (ronin.smeinc.net []) (amavisd-new, port 10024) with ESMTP id doTdo8zolFbh for <ianaplan@ietf.org>; Wed, 20 May 2015 10:48:32 -0400 (EDT)
Received: from [] (pool-108-51-128-219.washdc.fios.verizon.net []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 184229A4051 for <ianaplan@ietf.org>; Wed, 20 May 2015 10:48:51 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 20 May 2015 10:48:40 -0400
References: <2EF1125C-D0FF-453C-AC9F-D7364EDE9399@vigilsec.com>
To: ianaplan@ietf.org
Message-Id: <0091D791-9795-4022-9310-87738CA3A893@vigilsec.com>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/iUi3NC6uRys49K-oLXtWozzRbhE>
Subject: [Ianaplan] Fwd: [IAB] IAB IANA Evolution Program commment on CWG Stewardship Draft Proposal
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, 20 May 2015 14:49:24 -0000


> From: Russ Housley <housley@vigilsec.com>
> Date: May 20, 2015 10:38:44 AM EDT
> To: comments-cwg-stewardship-draft-proposal-22apr15@icann.org
> Cc: IAB <iab@iab.org>
> Subject: [IAB] IAB IANA Evolution Program commment on CWG Stewardship Draft Proposal
> To the ICANN CWG-Stewardship and the IAB:
> The IAB creates and manages programs for topics that require a long-term perspective and that may require insights and expertise from people not necessarily appointed to the IAB.  The IAB IANA Evolution program is one such program.  Any output of an IAB program does not necessarily reflect the views of the IAB.  Nor does it reflect IETF consensus.
> The IAB IANA Evolution has some some comments about the ICANN CWG-Stewardship second draft proposal, available at https://www.icann.org/en/system/files/files/cwg-stewardship-draft-proposal-with-annexes-22apr15-en.pdf.  Please find comments from the program below.  Note that the IAB is copied on this note so that it is aware of our correspondence.
> We observe that the CWG-Stewardship continues to work and expects to complete its proposal in June.  We congratulate the CWG-Stewardship for the considerable work it has accomplished in a short time.
> The proposal includes a plan to create a "Post-Transition IANA" or PTI.  The PTI is to be a separate legal entity, subsidiary to ICANN (an "affiliate").  The precise details of organization, control, and governance are not entirely laid out in the proposal, but we believe it is likely to be either a public-benefit corporation or an LLC, under a board with at least a majority appointed by the ICANN board.
> The IETF community prepared a plan in advance of the proposal to create PTI, and IETF consensus was to continue the current arrangement with ICANN.  As a result, we believe that the IETF's agreements for the protocol parameters IANA function will continue to be with ICANN.  If ICANN chooses to create internal structures (such as the PTI) for the delivery of that service, we do not believe that entails changing the IETF's agreements.  We expect legal analysis by the IETF will be required as the details emerge of how the PTI is to be constituted and funded, and that analysis could change our evaluation of what arrangements are needed.
> The proposal also contains some scenarios in which the IAB might be invited to participate either directly or via liaison in additional ICANN-related activities.  We believe the IAB will need to evaluate those possibilities carefully in the future, when all the details are available.  However, arrangements for the protocol parameters part of IANA are not dependent on such participation.
> We observe that the proposal is in some ways dependent on decisions by the ICANN CCWG-Accountability, and we have not completed our evaluation of current CCWG-Accountability proposals.
> Best regards,
>    Russ Housley
>    IAB IANA Evolution program chair