Re: [Ianaplan] Fwd: Do we need a unified post-transition IANA?

Eliot Lear <lear@cisco.com> Tue, 17 November 2015 09:53 UTC

Return-Path: <lear@cisco.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 ECB191B2DFA for <ianaplan@ietfa.amsl.com>; Tue, 17 Nov 2015 01:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.085
X-Spam-Level:
X-Spam-Status: No, score=-15.085 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 FkaXKwJnvbKF for <ianaplan@ietfa.amsl.com>; Tue, 17 Nov 2015 01:53:26 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9E781B2DF5 for <ianaplan@ietf.org>; Tue, 17 Nov 2015 01:53:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11837; q=dns/txt; s=iport; t=1447754006; x=1448963606; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=ZVpnrOi7nipXGsNqn6MZ21jG00jjbn/TqCybEFtV64M=; b=Yr7byFx13pmen/qQ29c2HscJ0SAuQ1Cs+d7mKdQFBVekP1eA2kvw2tRx pTZGfKCWHiiQqUzCtkTyvOVAOO5jU69lBeAHyTHg6BuFOmKunFzseOghj MKtP6/620xeHLdolK7nbTG2WkayrOTwukbilH1PjuHi3Wmv1jTvTrkusu U=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CuBABW+EpW/xbLJq1dhA5vwFAXAQuFI0oCghYBAQEBAQGBC4Q0AQEBBAEBASBLChEJAhEDAQIBCRYIAwICCQMCAQIBDwYBHgkIBgEMBgIBARCIBQMSDY1RnTWLWQ2EXQEBAQEBAQEBAQEBAQEBAQEBAQERCYtSglOBaz0WgmSBRAWHRIsjg2KCVoFgaoUgdYF1gVuHQotVg2GDcmOEBT00hQoBAQE
X-IronPort-AV: E=Sophos;i="5.20,307,1444694400"; d="asc'?scan'208,217";a="606364426"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Nov 2015 09:53:22 +0000
Received: from [10.61.171.186] ([10.61.171.186]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id tAH9rMBm008456; Tue, 17 Nov 2015 09:53:22 GMT
To: Padmini <pdmnbaruah@gmail.com>, ianaplan@ietf.org
References: <CAOr9Jxk_RYbC1Vp4GOc4mMeo=37uTF3D4Cyha+t7ohV7FYQZ5Q@mail.gmail.com> <CAOr9JxmKTaUDEROL7+HXqn5vcX-OQveDZt9B1-H7NaCfPFYEEQ@mail.gmail.com>
From: Eliot Lear <lear@cisco.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <564AF911.7090802@cisco.com>
Date: Tue, 17 Nov 2015 10:53:21 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <CAOr9JxmKTaUDEROL7+HXqn5vcX-OQveDZt9B1-H7NaCfPFYEEQ@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="8VPCQXFDQDv7C7hcl0CMGnpLaWAEM4fJT"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/oJ_XQW8TUz3TJePskZvWH5MuWlA>
Subject: Re: [Ianaplan] Fwd: Do we need a unified post-transition IANA?
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: <https://mailarchive.ietf.org/arch/browse/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, 17 Nov 2015 09:53:29 -0000

Hi Padmini,

It seems to me that the entire rigamarole that has taken place at the
CWG and elsewhere has been so that the three functions could be
separated in the future as you suggest, should the need arise.  And so
perhaps your question is, “Why not do it now?”  With regard to the
protocol parameters, the answer from the IETF community has repeatedly
been unambiguous: we are very satisfied with the current operator.  That
is actually a quote from our submission to the ICG. I am unaware of any
events that would have changed this perspective in the intervening
year.  Given that we are so satisfied, and that the price is right, why
would we risk destabilizing the service?

Warm regards,

Eliot

On 11/17/15 6:29 AM, Padmini wrote:
> Reposting this here as Mr. Sullivan was kind enough to point out that
> this would be a more appropriate forum to do so.
>
> We would really appreciate any feedback on our outputs.
>
> Warm Regards
>
> Padmini Baruah
> Programme Associate, Internet Governance, Centre for
> Internet and Society, Bangalore
> V Year, B.A.LL.B. (Hons.)
> NLSIU, Bangalore
>
> ---------- Forwarded message ----------
> From: *Padmini* <pdmnbaruah@gmail.com <mailto:pdmnbaruah@gmail.com>>
> Date: Mon, Nov 16, 2015 at 5:31 PM
> Subject: Do we need a unified post-transition IANA?
> To: BestBits <bestbits@lists.bestbits.net
> <mailto:bestbits@lists.bestbits.net>>, governance@lists.igcaucus.org
> <mailto:governance@lists.igcaucus.org>, Accountability Cross Community
> <accountability-cross-community@icann.org
> <mailto:accountability-cross-community@icann.org>>,
> NCSG-DISCUSS@listserv.syr.edu <mailto:NCSG-DISCUSS@listserv.syr.edu>
>
>
> Dear all,
>
> (Apologies for cross posting at the outset)
>
> At the Centre for Internet and Society, we found ourselves wondering
> why there was a strong presumption in favour of unified IANA functions
> after the transition, given that there was at one point of time
> significant amounts of discourse on splitting these functions. Even as
> we all debate over the extent of ICANN's coordinating functions over
> the different functions, perhaps we could open our - minds to the idea
> of separating the three functions - names, numbers, protocols - after
> the transition.
>
> This idea has been detailed in the blog post below. The three main
> points we make are :
>
>   * Splitting of the IANA functions allows for technical
>     specialisation leading to greater efficiency of the IANA functions.
>   * Splitting of the IANA functions allows for more direct
>     accountability, and no concentration of power.
>   * Splitting of the IANA functions allows for ease of shifting of the
>     {names,number,protocol parameters} IANA functions operator without
>     affecting the legal structure of any of the other IANA function
>     operators.
>
>
> http://cis-india.org/internet-governance/blog/do-we-need-a-unified-post-tranistion-iana
>
>
> We welcome comments on this.
>
> Warm Regards
>
> Padmini
> Centre for Internet and Society
> Bangalore
>
>
>
> _______________________________________________
> Ianaplan mailing list
> Ianaplan@ietf.org
> https://www.ietf.org/mailman/listinfo/ianaplan