[iucg] prior to he today virtual meeting

JFC Morfin <jefsey@jefsey.com> Mon, 06 October 2014 14:59 UTC

Return-Path: <jefsey@jefsey.com>
X-Original-To: iucg@ietfa.amsl.com
Delivered-To: iucg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FACB1A00C2; Mon, 6 Oct 2014 07:59:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.232
X-Spam-Level:
X-Spam-Status: No, score=0.232 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_I_LETTER=-2, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_17=0.6, MISSING_MID=0.497] autolearn=ham
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 3hC0xi3g3Atr; Mon, 6 Oct 2014 07:59:12 -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 C64741A00B8; Mon, 6 Oct 2014 07:59:12 -0700 (PDT)
Received: from 192.102.176.95.rev.sfr.net ([95.176.102.192]:25763 helo=MORFIN-PC.mail.jefsey.com) by host.presenceweb.org with esmtpa (Exim 4.82) (envelope-from <jefsey@jefsey.com>) id 1Xb9kk-0004qX-KA; Mon, 06 Oct 2014 07:59:11 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 06 Oct 2014 16:59:04 +0200
To: Jari Arkko <jari.arkko@piuha.net>
From: JFC Morfin <jefsey@jefsey.com>
In-Reply-To: <DCF6FF98-8985-4401-BE42-0DFB325CAA88@piuha.net>
References: <9390B5F8-8E21-40C2-9E96-168CD599419B@viagenie.ca> <542EEADA.6000206@thinkingcat.com> <20141004065827.84D7D1A8F46@ietfa.amsl.com> <DCF6FF98-8985-4401-BE42-0DFB325CAA88@piuha.net>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_370486758==.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/iucg/SxPbl1yxldY_LAZLuUeh5w53ssc
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, "Leslie Daigle \(TCE\)" <ldaigle@thinkingcat.com>, "iucg@ietf.org" <iucg@ietf.org>, iesg@ietf.org, "ianaplan@ietf.org" <ianaplan@ietf.org>
Subject: [iucg] prior to he today virtual meeting
X-BeenThere: iucg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: internet users contributing group <iucg@ietf.org>
List-Id: internet users contributing group <iucg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iucg>, <mailto:iucg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iucg/>
List-Post: <mailto:iucg@ietf.org>
List-Help: <mailto:iucg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Oct 2014 14:59:15 -0000
X-Message-ID:
Message-ID: <20141006145920.4972.52197.ARCHIVE@ietfa.amsl.com>

At 10:35 04/10/2014, Jari Arkko wrote:
>Jefsey,
>
> > I am sorry, but my various efforts in order to avoid an appeal 
> against the charter's status-quo spirit and letter did not succeed so far.
>
>For what it is worth, I do not plan to update the charter at this 
>time. I believe the current charter is supported by IETF consensus, 
>as determined by the IESG during the WG Review of this charter. Not 
>only was IETF-wide WG Review held (with an announcement to other 
>SDOs), but there was also a BOF held at the previous IETF meeting. 
>In both instances, the community was insistent that the WG not be 
>given the latitude to change current operational procedures.
>
>Jari Arkko (speaking as the responsible AD for the WG)

Dear Jari (as an IESG chair and WG/IANAPLAN AD),

As you know, I am planning to appeal the IESG 08 Sep 2014 09:02:52 
-0700 decision to adopt the WG/IANAPLAN Charter, but I wish we could 
avoid the implied work load and hassle.

The target so far (some additional elements may result from today's 
virtual meeting report) is for the internet users' various community 
layers (individual, local, corporate, national, governmental) to be 
able to assess the capacity and motivation of the IETF to continue 
documenting a technically better internet when a-priori strategies 
are decided on that are based upon economic motives and governmental 
injunctions, as it would seem to be the case for the response to the 
unclear NTIA unilateral March 14, 2014 announcement.

Two parts in the charter seem to be critical for the stability of the 
Internet community and technology:

1. "In the case of the elements of the IANA function concerning the 
IETF protocol registries, it is likely that the existing 
well-documented practices will continue and no or little new activity 
will be required." This is something that contradicts the RFC 6852 
assessment of digital world reality. Only considering the status quo 
in a fundamentally changing situation, as the Chair (Leslie Daigle) 
assigned it to the WG, is either an deliberate (why?) ostrich policy 
or a hidden coordination with the authors of the change.

2. "Should proposals made by other communities regarding the 
transition of other IANA functions affect the IETF protocol parameter 
registries or the IETF, the WG may also review and comment on them." 
This wording is not only contemptuous of other communities, but also 
to all internet users since it permits the WG to not consider inputs 
from other stakeholders, to select the stakeholders it "could" listen 
to, and to not address the positive or negative impact of their 
positions on the common good. The Chair (Marc Blanchet) said that the 
WG would consider every proposal. It is necessary for the AD and 
Chairs to formally commit to what they will consider, comment on, and 
address regarding the announcements and/or proposals made by all 
other stakeholders.

Now, we are facing a problem of timing. At the ICANN's request, the 
January 15 milestone is a rough consensus over a complete protocol 
parameters registries document.

- The appeal limit date is November 8, 2014. I hope that I do not 
need that long (all of us want quick clarifications since we are 
engaged in status quo or innovative solution projects) but this may 
depend on today's virtual meeting.
- If the IESG responds negatively the same day, I could appeal the 
IAB until January 8, 2015.
- Again, the IAB could respond negatively the same day and stay ahead 
of the January 15 date.
- However, such fast responses would certainly give me good grounds 
to appeal ISOC.

This is why I suggest that we try to play this out reasonably, 
keeping political interests, the press, and sponsors aside. The 
difficulty that we are facing is simple to evaluate. The USG's and 
OECD's internet governance vision that the NTIA is trying to sneak-in 
was multilaterally and democratically defeated in Dubai. This vision 
is questioned by the users, when the WSIS has consensually declared 
that the information society was to be people [and not business or 
jurisdiction] centered, decisions are to be made on a 
multistakeholder (govs, business, civil society) basis, and the 
I*Society's mantra is that the internet is for everyone to use, 
innovate, experiment on, and deploy. The NTIA multistakeholder 
reduced the mutual recognition constraints in reference of  govs and 
lead users are diplomatically pious vows. They will do what they 
want. Datagrams do not really care about diplomatic announcements.

We know that there is a wide portion of the Internet users that 
disagrees with the NTIA's idea that ICANN is to protect them from 
their own Governments and who trust their own political and Defense 
national institutions (they pay for that through their taxes) to 
engage in active precautionary strategies, at least when public and 
private NSAs are concerned.

The IETF's job is not to judge whether these people are right or 
wrong. It is to technically ensure that its published set of protocol 
rules will best adapt to their needs and the resulting situational 
changes, and that these people trust them. Otherwise, such people and 
Govs will patch their own contingency plan and technical solutions 
(or have them ready). I know this well because I am, as you know, 
carrying that out myself, for my local non-profit Libre digital 
operator and my fellow independent involved etc. users.

  jfc