[Ianaplan] The internet singularity [was: closing the working group]

JFC Morfin <jefsey@jefsey.com> Fri, 14 October 2016 15:25 UTC

Return-Path: <jefsey@jefsey.com>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id BD94B129512 for <ianaplan@ietfa.amsl.com>; Fri, 14 Oct 2016 08:25:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id kbtgPHZpe6dR for <ianaplan@ietfa.amsl.com>; Fri, 14 Oct 2016 08:25:08 -0700 (PDT)
Received: from host.presenceweb.org (host.presenceweb.org []) (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 15421129527 for <ianaplan@ietf.org>; Fri, 14 Oct 2016 08:17:40 -0700 (PDT)
Received: from [] (port=65383 helo=MORFIN-PC.jefsey.com) by host.presenceweb.org with esmtpa (Exim 4.87) (envelope-from <jefsey@jefsey.com>) id 1bv4Er-0001WL-Ky; Fri, 14 Oct 2016 17:17:38 +0200
X-Mailer: QUALCOMM Windows Eudora Version
Date: Fri, 14 Oct 2016 17:17:34 +0200
To: Steve Crocker <steve@shinkuro.com>,Jari Arkko <jari.arkko@piuha.net>, Russ Housley <housley@vigilsec.com>
From: JFC Morfin <jefsey@jefsey.com>
In-Reply-To: <0866241D-73BB-40B9-AE5A-81272E691CE4@shinkuro.com>
References: <15E19BC7-0CA4-4C49-B36A-C0D9D96281F3@piuha.net> <0866241D-73BB-40B9-AE5A-81272E691CE4@shinkuro.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
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-Authenticated-Sender: host.presenceweb.org: jefsey@jefsey.com
Message-Id: <20161014151740.15421129527@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ianaplan/B8lc8lPj6zh1jeFrGZodCInXfWs>
Cc: "Ianaplan@Ietf. Org" <ianaplan@ietf.org>, ga@atlarge.org
Subject: [Ianaplan] The internet singularity [was: closing the working group]
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 14 Oct 2016 15:25:13 -0000

Dear Steve, Jari and Russ,

Closing this Working Group is truly a no-return singular milestone 
for humanity: it formally means that the World Community's OpenStand 
Global Community concept (OSGCC) that benefits all of humanity (as 
per RFC 6852 "3. Collective Empowerment") is now the world digital 
ecosystem reference that we are to build upon by ourselves.

As a consequence, we will start observing the emergence of multiple 
OSGCs, the current main one being the ICANN/IETF Global Community, 
around its PTI kernel.

In foreseeing this emergence, we established the AtLarge Association 
in 2003 in order to help the user multitude to remain mutually aware 
of the compatible innovation flow. My appeals have established that 
the genuine IETF consensus did not want an inside intertechnology 
technical conflict resolution process to be included in OpenStand. 
The AtLarge Association will, therefore, strive within its limited 
resources and capacities to help the OSGCs' multiconsensual technical 
convergence from the outside, from the users, throughout the 
multitude's practices of mutual documentation and calls for comments.

By doing so, we will depend on the contributions of everyone in the 
hope of helping each other in addressing the needs of everyone, which 
is an ambition I am sure we all share.


On 16:11 13/10/2016, Steve Crocker said:
>Content-Transfer-Encoding: base64Jari, et al,
>This is indeed an important milestone and let me again add thanks 
>and congratulations to everyone.
>Let me also take a moment to reflect on where we were and where we 
>are now.  Some years ago I looked at the interactions between ICANN 
>and the operational communities and wondered why there was a sense 
>of distance.  ICANN had, after all, been purpose built to be the 
>home of the IANA function and each of the operational communities 
>were represented on the ICANN Board as well as having multiple 
>pathways into the organization.  I concluded it would be helpful for 
>the operational communities to have more direct representation for 
>the IANA function.  Also as a separate matter, when I was chair of 
>ICANN's Security and Stability Advisory Committee, I saw first hand 
>there was a hole in the system, namely a way of making informed 
>decisions about technical changes to the root zone.  This hole 
>resulted in a multi-year delay in putting IPv6 addresses for root 
>servers into the root zone, and it led to a deadlock for another 
>multi-year period before DNSSEC was implemented in the root zone.
>Meanwhile, the effort to find a way to bring the NTIA contract for 
>IANA services to an end reached a critical point of success in March 
>2014 with NTIA's announcement.  That kicked off the two-and-a-half 
>year process that just ended.  That process included two major 
>streams, one focused on the IANA function, and the other focused on 
>the structure, function and accountability of ICANN itself.
>The encapsulation of the IANA function in the newly formed Public 
>Technical Identifiers organization, a legally separate but wholly 
>owned subsidiary — the technical terminology for non-profits is a 
>bit different but the concept is the same — is ICANN was a heavier 
>weight solution than I had originally imagined, but since it 
>includes two new review groups, the Customer Standing Committee 
>(CSC) and the Root Zone Evolution Review Committee (RZERC), I am 
>confident that the problems I observed some years ago are unlikely to recur.
>I fully expect the IANA function to continue to function smoothly 
>and effectively.  With the transition to the new structure and 
>simplification of no longer having the contract from NTIA in place, 
>I also expect an even higher degree of transparency and responsiveness.
>Steve Crocker
>Chair, ICANN Board of Directors
>(Writing from my Shinkuro email address because that's how I'm 
>subscribed to the ianaplan list)
> > On Oct 13, 2016, at 9:42 AM, Jari Arkko <jari.arkko@piuha.net> wrote:
> >
> > Dear all,
> >
> > With our chartered work done, I plan to close this working group.
>‚'v÷VÆBÆ­¶RFòF†æ²WfW'­öæRv†ò†2'F­6—ated in the effort for their 
>contribution, and their desire to stay on the rational, practical, 
>and implementable course. It worked :-)
> >
> > Closing this working group does not mean that there will be no 
> further evolution in the IANA system. Like other parts of the IETF 
> or the Internet organisations ecosystem, there may be room for 
> improvements and new ways of working. If we need a broad community 
> discussion for any future change, we will create new working groups as needed.
> >
> > Thank you,
> >
> > Jari Arkko
>  IETF Chair and AD for IANAPLAN WG
> > Ianaplan mailing list
> > Ianaplan@ietf.org
> > https://www.ietf.org/mailman/listinfo/ianaplan
>Ianaplan mailing list