Re: [Ianaplan] Taking a step toward the IANA Transition

Jefsey <jefsey@jefsey.com> Fri, 09 January 2015 13:29 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 79B491A87A0; Fri, 9 Jan 2015 05:29:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.631
X-Spam-Level: *
X-Spam-Status: No, score=1.631 tagged_above=-999 required=5 tests=[BAYES_50=0.8, IP_NOT_FRIENDLY=0.334, MISSING_MID=0.497] 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 7R42nAt1tMTG; Fri, 9 Jan 2015 05:29:25 -0800 (PST)
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 F34D51A879D; Fri, 9 Jan 2015 05:29:24 -0800 (PST)
Received: from 223.57.14.81.rev.sfr.net ([81.14.57.223]:22263 helo=MORFIN-PC.mail.jefsey.com) by host.presenceweb.org with esmtpa (Exim 4.84) (envelope-from <jefsey@jefsey.com>) id 1Y9Zcx-0000pr-7G; Fri, 09 Jan 2015 05:29:23 -0800
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 09 Jan 2015 14:29:13 +0100
To: Eliot Lear <lear@cisco.com>, "ianaplan@ietf.org" <ianaplan@ietf.org>
From: Jefsey <jefsey@jefsey.com>
In-Reply-To: <54AE9663.4010706@cisco.com>
References: <54AE9663.4010706@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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:
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/NKweBNPKdDhRyME-LEuGw3u9G8U>
Cc: gene@iuwg.net, "iucg@ietf.org" <iucg@ietf.org>, iab <iab@iab.org>, iesg@ietf.org
Subject: Re: [Ianaplan] Taking a step toward the IANA Transition
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, 09 Jan 2015 13:29:26 -0000
X-Message-ID:
Message-ID: <20150109132932.3604.39998.ARCHIVE@ietfa.amsl.com>

At 15:38 08/01/2015, Eliot Lear wrote:

>Jari and I have put together a short blog on where we are.  This working
>group in particular should be pleased with its work.
>
>http://www.ietf.org/blog/2015/01/taking-a-step-towards-iana-transition/
>
>Eliot

Jari and Eliot,

I do not understand. Is the draft to be published as an RFC, yes or 
no? This is not immaterial: since if it is to be published I only 
have until March 6, 2015 to file an appeal, of which the matter is 
now clarified by the eventual IESG choice of a US leadership on the 
IETF technology that you made official yesterday. Lynn St-Amour is 
rightly pleased. Many are most probably not.


You fully understand that the sentence "When ready, they will submit 
the final proposal to the NTIA. The NTIA must then consider and 
approve the proposal", being co-signed by the IETF Chair, is of a 
purely political nature and cannot have anything to do with any 
technical norm concerning my and people's personal Catenet properties.

Therefore, there was a global 
IETF. 
http://www.ietf.org/blog/2015/01/taking-a-step-towards-iana-transition/ 
changed that: you have now formally published that it forked to a USIETF.


One of the IETF core values was to responsibly decide on an 
"omnistakeholder" rough consensus basis. If the NTIA is now to first 
approve its propositions, why not China, Russia, Germany, UK, France, 
etc.? And/or Google, Apple, Xerox, NSA, etc.?

There can only be one single authoritative internet technical 
sovereignty: http://iana.arpa. It owns this sovereignty because:

- there must be a "Respectful cooperation between standards 
organizations, whereby each respects the autonomy, integrity, 
processes, and intellectual property rules of the others" (RFC 6852).
-  "Standards processes are transparent and opportunities exist to 
appeal decisions",
-  Users and people may uniquely identify it and freely adhere to it, 
thereby forming the Internet global community.

The RFC 2026 Internet standards process has not thus far required 
anyone to "submit the final proposal to the NTIA, for the NTIA to 
consider and approve", unless the NTIA is the new IAB's name as the 
"Network Technical Independent Authority".

Perhaps I am wrong: this was probably before, when "Standards 
activities [were] not exclusively dominated by any particular person, 
company, [] interest group [or nation]" (cf. RFC 6852).


I appealed RFC 6852 because it did not clarify who its ultimate 
referent was. We now know that it is the USG. I beg to disagree, 
however, because nations, like the internet, form neither a 
hierarchical nor a decentralized but rather a distributed network. 
You crossed the border between technology and policy, between what is 
to be technically and what some may want to be: thi way you 
unfortunately but definitely put the IETF technology in jeopardy and 
politically fragmented the internet after RFC 6852 tried to patch its 
technical fragmentation risks. I frankly doubt this is what Lawrence 
E. Strickling wanted the world to perceive.

Sorry.
jfc