Re: [Ianaplan] Transition proposal for naming-related functions
JFC Morfin <jefsey@jefsey.com> Fri, 01 May 2015 19:06 UTC
Return-Path: <jefsey@jefsey.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 967C21B2DB9 for <ianaplan@ietfa.amsl.com>; Fri, 1 May 2015 12:06:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.335
X-Spam-Level: **
X-Spam-Status: No, score=2.335 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_14=0.6, J_CHICKENPOX_16=0.6] 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 MIdcd2-xTOLP for <ianaplan@ietfa.amsl.com>; Fri, 1 May 2015 12:06:03 -0700 (PDT)
Received: from host.presenceweb.org (host.presenceweb.org [67.222.106.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05A081B2DE1 for <ianaplan@ietf.org>; Fri, 1 May 2015 12:05:59 -0700 (PDT)
Received: from 251.47.14.81.rev.sfr.net ([81.14.47.251]:3801 helo=MORFIN-PC.mail.jefsey.com) by host.presenceweb.org with esmtpa (Exim 4.85) (envelope-from <jefsey@jefsey.com>) id 1YoGG6-0008AO-B8 for ianaplan@ietf.org; Fri, 01 May 2015 12:05:58 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 01 May 2015 21:05:53 +0200
To: "Ianaplan@Ietf.org" <ianaplan@ietf.org>
From: JFC Morfin <jefsey@jefsey.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_3780731==.ALT"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.presenceweb.org
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Get-Message-Sender-Via: host.presenceweb.org: authenticated_id: jefsey+jefsey.com/only user confirmed/virtual account not confirmed
X-Source:
X-Source-Args:
X-Source-Dir:
Message-Id: <20150501190559.05A081B2DE1@ietfa.amsl.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/-4qf6_5j63qne_tvvkAB7n8MMq4>
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: Fri, 01 May 2015 19:06:05 -0000
At 19:09 29/04/2015, Jefsey wrote: >At 18:44 29/04/2015, Alissa Cooper wrote: >>The proposal mentions the possibility of IAB representation on the >>CSC in its capacity as registry operator for .arpa. Dear Alissa, The point is not for the IAB to be in the CSC, as one inter pares (a registry as any other registries), but that the IAB - as the IAB - is acknowledged and given genuine control capacity over the internet consistency. We know they do not want it (cf. the IANAPLAN document, and the I*Chairs summary). However, no one, I am afraid, in the world, except the vanity registries and the so-called registrars, is interested in ICANN if ICANN does not give at least some feeling it can be trusted. That trust can only come from those that techies can trust, i.e. ISPs. An ISP will only trust RIRs and RFCs. Since Jari Arkko has said the IETF will follow what the NTIA decides, most of the Sates will progressively revert to ITU: mostly because multilateralism is clearer than multistakeholderism. Lead users will go for a Libre approach, now that the IESG was unable to use my appeal to federate clear responses (unless IAB can change do it). This is why the only global I*body left that everyone will not object to is the IAB. If ICANN gives the feeling that it does not respect the IAB as being the "unique" trustable core of the Internet community, the last entity left will be the NRO. Is it prepared for the task of replacing the NTIA? Then it will be the FCC (for the US, and vassals), Google (money), BRICS (national power), and Libre (local/individual capacity). This will lead to multiple "fail-safe plans for the net" versions. This will be managed as prepared by RFC 6852. The question is: what has RFC 6852 prepared? The response has been given by the IAB: <https://www.iab.org/appeals/2013-2/iab-response-to-the-appeal-regarding-rfc-6852-by-jfc-morfin/>https://www.iab.org/appeals/2013-2/iab-response-to-the-appeal-regarding-rfc-6852-by-jfc-morfin/. If I read the IAB correctly: nothing. I am afraid I am not wrong. jfc
- [Ianaplan] Transition proposal for naming-related… Alissa Cooper
- Re: [Ianaplan] Transition proposal for naming-rel… Jefsey
- Re: [Ianaplan] Transition proposal for naming-rel… Alissa Cooper
- Re: [Ianaplan] Transition proposal for naming-rel… JFC Morfin
- Re: [Ianaplan] Transition proposal for naming-rel… Tobias Gondrom
- Re: [Ianaplan] Transition proposal for naming-rel… Alissa Cooper
- Re: [Ianaplan] Transition proposal for naming-rel… Steve Crocker
- Re: [Ianaplan] Transition proposal for naming-rel… Tobias Gondrom
- Re: [Ianaplan] Transition proposal for naming-rel… John Curran
- Re: [Ianaplan] Transition proposal for naming-rel… Milton L Mueller
- Re: [Ianaplan] Transition proposal for naming-rel… Seun Ojedeji
- Re: [Ianaplan] Transition proposal for naming-rel… John Curran
- Re: [Ianaplan] Transition proposal for naming-rel… John Levine
- Re: [Ianaplan] Transition proposal for naming-rel… John Curran
- Re: [Ianaplan] Transition proposal for naming-rel… Jefsey
- Re: [Ianaplan] Transition proposal for naming-rel… Jefsey