Re: [Ianaplan] draft-ietf-ianaplan-icg-response moving to next step
JFC Morfin <jefsey@jefsey.com> Thu, 27 November 2014 16:30 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 E841D1A0084;
Thu, 27 Nov 2014 08:30:23 -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 CaFI2sf1uv5G; Thu, 27 Nov 2014 08:30:22 -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 CD24C1A0074;
Thu, 27 Nov 2014 08:30:22 -0800 (PST)
Received: from 191.104.176.95.rev.sfr.net ([95.176.104.191]:2678
helo=MORFIN-PC.mail.jefsey.com)
by host.presenceweb.org with esmtpa (Exim 4.84)
(envelope-from <jefsey@jefsey.com>)
id 1Xu1xT-0006e2-N6; Thu, 27 Nov 2014 08:30:20 -0800
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 27 Nov 2014 17:30:09 +0100
To: rhill@hill-a.ch,"Marc Blanchet" <marc.blanchet@viagenie.ca>,
<ianaplan@ietf.org>,"Leslie Daigle (TCE)" <ldaigle@thinkingcat.com>
From: JFC Morfin <jefsey@jefsey.com>
In-Reply-To: <GLEAIDJPBJDOLEICCGMNIEMOCOAA.rhill@hill-a.ch>
References: <1386C0EC-3EC8-42C0-B94A-F850C93FE391@viagenie.ca>
<GLEAIDJPBJDOLEICCGMNIEMOCOAA.rhill@hill-a.ch>
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/RXPrG0I3zraP8sINQn1RrUiJ7JQ
Cc: gene@iuwg.net, Jari Arrko <jari.arkko@piuha.net>,
"iucg@ietf.org" <iucg@ietf.org>
Subject: Re: [Ianaplan] draft-ietf-ianaplan-icg-response moving to next step
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, 27 Nov 2014 16:30:24 -0000
X-Message-ID:
Message-ID: <20141127163033.12509.463.ARCHIVE@ietfa.amsl.com>
At 09:57 27/11/2014, Richard Hill wrote: >I note that section 3 of RFC 7282 states: > >"The chair of a working group who is about to find that there is only rough >consensus is going to have to decide that not only has the working group >taken the objection seriously, but that it has fully examined the >ramifications of not making a change to accommodate it, and that the outcome >does not constitute a failure to meet the technical requirements of the >work. ... A valid justification needs to me [sic] made." > >Therefore, I would request that the co-chairs provide a justification for >the conclusion that rough consensus has been achieved. Richard, The way I see the things is rather simple. Vint Cerf has initiated the Internet project with two objectives and a vision. The vision was a new definition of "locality", that one may now qualify of "networked glocality". The first objective was to build its catenet, i.e. its transport stratum. The non completion of the second objective before the USA could swallow it was then discovered (due to architectural lacks vs. deployment advantages) as a national necessity. This has been taken care by the IETF and politically engineered by the USG in - pushing for its technology to be used for the world digital ecosystem main value added network, - using the ICANN single-root lie, - and in keeping the whole thing subject to the1984 born statUS-quo strategy. This was an exceptional process where the USG patched the involved global issues by transferring control from its Legislative branch's domestic/international FCC agency to its Executive NTIA agency. This exceptional situation has come to an end when Obama has directly directed the FCC on Internet neutrality domestic issues. Not the NTIA on global neutrality issues (we know why). Now, time is about an IETF's deliverables domestic/industrial/international review. Feelings are mixed. Theoritically, the IETF has the leadership, and IAB the dominance for a simple reason: the network has to work. IAB is therefore responsible for the past and the future of the Internet. However, many are technologically unhappy (most did not know why, until Snowden's and FCC/Obama's help) and for others they are happy of the money they do. Until August 22, 2012, responsibility was then with the IAB/ISOC. Since then it is to the community of technical communities addressing their community's economic requirements (cf. RFC 6852). Until a week ago responsibility for past and future internet issues was with the IETF. Russ Housley's admonition for an hardened protocol stack makes the IETF only responsible for the future internet. The Chairs' rough consensus shows that among the true "IETF natives" the consensus is that the IETF is working for the future internet, but is not responsible. The question you ask is the basis of my future appeal, once the IETF Last-Call has most probably confirmed this IETF hidden abdication. My point will not be to change it, but to make sure that the IESG, and IAB, and ISOC, fully and publicly declare that they understand, accept and decide that this is what they mean. Please note that this I_D is co-authored by the IAB Chair, former IETF Chair in 2012. This is important because it will show there is no conflict calling for a fork; but an accepted seamless transition from datacommunications to metacommunications. The same as we had that transition in 1977 from telecommunications to datacommunications. I remember the surprise of the ITU people when I went there to adhere as an US Datacommunications Operator :-). jfc
- [Ianaplan] draft-ietf-ianaplan-icg-response movin… Marc Blanchet
- Re: [Ianaplan] draft-ietf-ianaplan-icg-response m… Richard Hill
- Re: [Ianaplan] draft-ietf-ianaplan-icg-response m… JFC Morfin
- Re: [Ianaplan] draft-ietf-ianaplan-icg-response m… Marc Blanchet
- Re: [Ianaplan] draft-ietf-ianaplan-icg-response m… Brian E Carpenter
- Re: [Ianaplan] draft-ietf-ianaplan-icg-response m… Andrew Sullivan
- Re: [Ianaplan] draft-ietf-ianaplan-icg-response m… John Curran
- Re: [Ianaplan] draft-ietf-ianaplan-icg-response m… Jefsey
- Re: [Ianaplan] draft-ietf-ianaplan-icg-response m… Richard Hill
- Re: [Ianaplan] draft-ietf-ianaplan-icg-response m… Richard Hill
- Re: [Ianaplan] draft-ietf-ianaplan-icg-response m… Richard Hill
- Re: [Ianaplan] draft-ietf-ianaplan-icg-response m… Milton L Mueller
- Re: [Ianaplan] draft-ietf-ianaplan-icg-response m… Richard Hill
- Re: [Ianaplan] draft-ietf-ianaplan-icg-response m… Milton L Mueller
- Re: [Ianaplan] draft-ietf-ianaplan-icg-response m… Richard Hill