[Ianaplan] Delay in my IESG appeal

JFC Morfin <jefsey@jefsey.com> Thu, 06 November 2014 13:46 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 431571A6EFF; Thu, 6 Nov 2014 05:46:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.831
X-Spam-Level:
X-Spam-Status: No, score=0.831 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, 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 mPT5kkosedA2; Thu, 6 Nov 2014 05:46:14 -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 E7A971A6F02; Thu, 6 Nov 2014 05:46:12 -0800 (PST)
Received: from 183.213.130.77.rev.sfr.net ([77.130.213.183]:59028 helo=MORFIN-PC.mail.jefsey.com) by host.presenceweb.org with esmtpa (Exim 4.82) (envelope-from <jefsey@jefsey.com>) id 1XmNO7-00012h-HZ; Thu, 06 Nov 2014 05:46:11 -0800
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 06 Nov 2014 14:46:03 +0100
To: "Ianaplan@Ietf. Org" <ianaplan@ietf.org>
From: JFC Morfin <jefsey@jefsey.com>
In-Reply-To: <7F52A930-DD6F-4D0D-8278-A021CF8A466C@istaff.org>
References: <GLEAIDJPBJDOLEICCGMNIEOJCNAA.rhill@hill-a.ch> <54594A50.4090305@meetinghouse.net> <20141105001731.GA30186@mx1.yitter.info> <54597BDB.7040305@meetinghouse.net> <5459BA98.1070006@gmail.com> <545A208A.7040304@meetinghouse.net> <631e3e3d29c843bd9c23151c63612989@EX13-MBX-13.ad.syr.edu> <20141105154903.GI30379@mx1.yitter.info> <498a39b81b774192bd2d609b3feab35f@EX13-MBX-13.ad.syr.edu> <20141105234444.GM31320@crankycanuck.ca> <545ABCB0.5080206@meetinghouse.net> <8f3dcda6c3db4cd8be1b77444f987d59@EX13-MBX-13.ad.syr.edu> <D0805C27.136BE7%jon.peterson@neustar.biz> <7F52A930-DD6F-4D0D-8278-A021CF8A466C@istaff.org>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_1825716813==.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:
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/aEBd7w5DHyv5C7G7qna9xHHKG0Y
Cc: iuwg@iuwg.net, gene@iuwg.net, "iucg@ietf.org" <iucg@ietf.org>
Subject: [Ianaplan] Delay in my IESG appeal
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: Thu, 06 Nov 2014 13:46:15 -0000
X-Message-ID:
Message-ID: <20141106134619.27777.80517.ARCHIVE@ietfa.amsl.com>

Dear Colleagues,

Since I have been unexpectedly led to create the 
<http://iuwg.net/>http://iuwg.net site, I intend to activate this 
unplanned WG for an Intelligent Internet Use and to utilize this 
Libre's Internet Use global community representation spark in order 
to competitively foster some technical governance innovations (as per 
RFC 6852).

As such, my priority does change:

- from expecting the IETF to protect the IUsers in taking the lead of 
the technical governance evolution through an update of the 
IETF/WG/IANAPLAN Charter
- to managing our own protection ourselves in cooperation with the 
IETF, ICANN, ITU, USG, BRICS, SCO, EU, NTIA/FCC, etc. strategies.

This is why my appeal to the IESG will focus on the way the IESG 
should provide adequate guidance to the IETF/WG/IANAPLAN Chairs. The 
starting point of this appeal is, therefore, the ongoing reading of 
the "status quo" strategy sponsored by the Chairs, in opposition to 
my own reading of the IETF position expressed in the Charter, of 
which the implications have to be considered better (hence the 
endless debate on issues like iana.org).

This is going to give me more time:

- to extend my draft (now 
<http://iuwg.net/images/draft-iuwg-intlnet-sdo-registry-relations.01.pdf>http://iuwg.net/images/draft-iuwg-intlnet-sdo-registry-relations.01.pdf. 
Taking advantage from Olaf Kolkman remark on BCP 59).
- evaluate the consequences of the Nov 10 IETF/WG/IANAPLAN meeting.
- evaluate the consequences of the Nov 10 Putin-Xi Jinping meeting.
- evaluate the consequences of the ITU PP 14.
- evaluate the first feedback of my draft concerning the network 
master and master model and plug-ins.

I hope that this may eventually lead to a convergence between Eliot's 
Draft and mine. I am aware that it will most probably call for 
IESG/IAB/ISOC involvement since I am not permitted to directly 
discuss it at the ietf@ietf.org last call level.

jfc