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

Padmini <pdmnbaruah@gmail.com> Tue, 17 November 2015 05:29 UTC

Return-Path: <pdmnbaruah@gmail.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 A0E171B29A3 for <ianaplan@ietfa.amsl.com>; Mon, 16 Nov 2015 21:29:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.702
X-Spam-Level:
X-Spam-Status: No, score=0.702 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HK_RANDOM_ENVFROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 cIkATZQV8_r9 for <ianaplan@ietfa.amsl.com>; Mon, 16 Nov 2015 21:29:30 -0800 (PST)
Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3860F1ADEB6 for <ianaplan@ietf.org>; Mon, 16 Nov 2015 21:29:30 -0800 (PST)
Received: by vkas68 with SMTP id s68so5675803vka.2 for <ianaplan@ietf.org>; Mon, 16 Nov 2015 21:29:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=iyvLHhmp78sFNlBGBPKXKHo8bMbzu/iEwt3XKiX8Iao=; b=HwvPGJd7lrrp/KmwJcEtWb8O1HtNsEPiy4i1J23Y6eDtpU9kh+fPy9USCN2xPAOkH1 cfLBF48xJF9rKGeHl4BZ85oWjvg5ovQFsOOui74E3XwBnfyNGaOi0bzeUhK/0KIKZRzJ 8Wj9Pa5kwC47bA4At5IW6A42XojtkiSjIHAmJbYCFSBFT9+VZLF2oC2HzAO8xqnnbroC 5CQmarquiUwfVjTHbw6qFcvmijR+0MTruMw2i1x2AJTH1QJKv/+EN9wlAT183roVeetF DF0fZ9LKtMs6UnvnRw47bMNBxoKRanIoGiHaed8WNBpERc+ZMOJV08aHgyfDwFPZd2NU i9Ag==
X-Received: by 10.31.161.78 with SMTP id k75mr1649985vke.10.1447738169326; Mon, 16 Nov 2015 21:29:29 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.70.69 with HTTP; Mon, 16 Nov 2015 21:29:09 -0800 (PST)
In-Reply-To: <CAOr9Jxk_RYbC1Vp4GOc4mMeo=37uTF3D4Cyha+t7ohV7FYQZ5Q@mail.gmail.com>
References: <CAOr9Jxk_RYbC1Vp4GOc4mMeo=37uTF3D4Cyha+t7ohV7FYQZ5Q@mail.gmail.com>
From: Padmini <pdmnbaruah@gmail.com>
Date: Tue, 17 Nov 2015 10:59:09 +0530
Message-ID: <CAOr9JxmKTaUDEROL7+HXqn5vcX-OQveDZt9B1-H7NaCfPFYEEQ@mail.gmail.com>
To: ianaplan@ietf.org
Content-Type: multipart/alternative; boundary="001a1143f18c4f81e60524b5cf2a"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/2shRE2uaxB-uYLfRClMsbGjtFAQ>
Subject: [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 05:31:22 -0000

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>
Date: Mon, Nov 16, 2015 at 5:31 PM
Subject: Do we need a unified post-transition IANA?
To: BestBits <bestbits@lists.bestbits.net>, governance@lists.igcaucus.org,
Accountability Cross Community <accountability-cross-community@icann.org>,
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