Re: [Ianaplan] Fwd: Do we need a unified post-transition IANA?
Mwendwa Kivuva <Kivuva@transworldafrica.com> Tue, 17 November 2015 10:57 UTC
Return-Path: <lordmwesh@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 AD7D61A9145 for <ianaplan@ietfa.amsl.com>; Tue, 17 Nov 2015 02:57:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=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 7IRHQtWcMHg1 for <ianaplan@ietfa.amsl.com>; Tue, 17 Nov 2015 02:57:41 -0800 (PST)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 0E16F1A8AF9 for <ianaplan@ietf.org>; Tue, 17 Nov 2015 02:57:41 -0800 (PST)
Received: by oiww189 with SMTP id w189so2548947oiw.3 for <ianaplan@ietf.org>; Tue, 17 Nov 2015 02:57:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=UxySaxWZeraIoIKjgwqtX+O5OSj/GuYNaU+9DTQNaac=; b=nM0WaQmO0doYmZWrUnB46A6CQ+WD0skK04pnVJ2H9XoOjSA7vYsGbyxKCQywSz8Jbu RNzyr4SHVxSVoVWNWZ4we/ov4h4i353RB1iXccwNu18hzbZQgcsFCfqHRg0xHwEvp7J9 BoTahYTK5AQINpY/rUaC0ffLL1CWg6HW5WuhrSrmpPzs9Wkd0+y9T/xhQZDqbhZbqUMf qIgRLUeoVpRoj33AwmPtRi/9CgUlPe4Nq+cszpj+suOUBzM5Z2dx23dP6+oga1CT4Jnv 3kn2zzXH3cIsHMarcKe4qb/Hm2TBSNif3hfzLlGkB67KHs4N1RO33BJXbu9EU2m/LfSd pyrg==
MIME-Version: 1.0
X-Received: by 10.202.212.68 with SMTP id l65mr22139173oig.54.1447757860460; Tue, 17 Nov 2015 02:57:40 -0800 (PST)
Sender: lordmwesh@gmail.com
Received: by 10.202.104.16 with HTTP; Tue, 17 Nov 2015 02:57:39 -0800 (PST)
Received: by 10.202.104.16 with HTTP; Tue, 17 Nov 2015 02:57:39 -0800 (PST)
In-Reply-To: <564AF911.7090802@cisco.com>
References: <CAOr9Jxk_RYbC1Vp4GOc4mMeo=37uTF3D4Cyha+t7ohV7FYQZ5Q@mail.gmail.com> <CAOr9JxmKTaUDEROL7+HXqn5vcX-OQveDZt9B1-H7NaCfPFYEEQ@mail.gmail.com> <564AF911.7090802@cisco.com>
Date: Tue, 17 Nov 2015 13:57:39 +0300
X-Google-Sender-Auth: V7YeCVlVRntgDaIO5jO3MeJsdJU
Message-ID: <CAEhPqwpx+SPDroj40uwhZQQ0TsOJCjzEZMiiWHv4y3jex4fP4Q@mail.gmail.com>
From: Mwendwa Kivuva <Kivuva@transworldafrica.com>
To: Eliot Lear <lear@cisco.com>
Content-Type: multipart/alternative; boundary="001a113cab98fe5ec10524ba6485"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/TC0-umvWpzd82ag6ykdGeFQOqSU>
Cc: "Ianaplan@Ietf. Org" <ianaplan@ietf.org>, Padmini <pdmnbaruah@gmail.com>
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 10:57:43 -0000
Exactly Eliot. If it's not broken, don't fix it. But we maintain there is a clause to change operators in future if the community feels the IFO is not meeting the agreed targets On Nov 17, 2015 12:53 PM, "Eliot Lear" <lear@cisco.com> wrote: > 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> > 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 > > > > _______________________________________________ > Ianaplan mailing listIanaplan@ietf.orghttps://www.ietf.org/mailman/listinfo/ianaplan > > > > _______________________________________________ > Ianaplan mailing list > Ianaplan@ietf.org > https://www.ietf.org/mailman/listinfo/ianaplan > >
- [Ianaplan] Fwd: Do we need a unified post-transit… Padmini
- Re: [Ianaplan] Fwd: Do we need a unified post-tra… Richard Hill
- Re: [Ianaplan] Fwd: Do we need a unified post-tra… Eliot Lear
- Re: [Ianaplan] Fwd: Do we need a unified post-tra… Mwendwa Kivuva