Re: [iucg] [Ianaplan] teasing the issues apart -- IANA.org, authoritative IETF repository
JFC Morfin <jefsey@jefsey.com> Mon, 13 October 2014 16:22 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 46C131A037D;
Mon, 13 Oct 2014 09:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.632
X-Spam-Level: *
X-Spam-Status: No, score=1.632 tagged_above=-999 required=5
tests=[BAYES_50=0.8, 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 FZJdWgDiPrem; Mon, 13 Oct 2014 09:22:33 -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 AFC6F1A030B;
Mon, 13 Oct 2014 09:22:33 -0700 (PDT)
Received: from 144.57.14.81.rev.sfr.net ([81.14.57.144]:1904
helo=MORFIN-PC.mail.jefsey.com)
by host.presenceweb.org with esmtpa (Exim 4.82)
(envelope-from <jefsey@jefsey.com>)
id 1XdiOG-0004hv-H8; Mon, 13 Oct 2014 09:22:33 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 13 Oct 2014 18:22:24 +0200
To: "ianaplan@ietf.org" <ianaplan@ietf.org>
From: JFC Morfin <jefsey@jefsey.com>
In-Reply-To: <543BDC65.4090502@gmail.com>
References: <5437031D.9080505@thinkingcat.com>
<543BDC65.4090502@gmail.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="=====================_980286227==.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/EofhdtmsBoHTA-4saJkES1_4FLo
Cc: "iucg@ietf.org" <iucg@ietf.org>
Subject: Re: [iucg] [Ianaplan] teasing the issues apart -- IANA.org,
authoritative IETF repository
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, 13 Oct 2014 16:22:36 -0000
X-Message-ID:
Message-ID: <20141013162243.21609.60995.ARCHIVE@ietfa.amsl.com>
>At 23:08 12/10/2014, Bernard Aboba wrote: >It is my assumption that the Trustees are following this discussion >and are thinking about next steps. If they discussed it in here, subject to the IETF consensus and to the IUsers' review, it could save us an appeal and possibly avoid a fork. >At 00:08 13/10/2014, Brian E Carpenter wrote: >IMHO that can include our expectations for any future additional >legal framework, plus the factual statement that the IETF Trust is >the responsible body for actual legal ink on paper. Ink on paper without having something to say is just a blot. To decide what to say (and what to do) belongs to this WG. >At 00:20 13/10/2014, Miles Fidelman wrote: >Which, to me, says that: >1. The WG charter is not sufficient to yield a complete response to >the TCG, and >2. It is not at all clear how the parts of the response, outside the >WG's purview, are to be developed and coordinated. > >If the response is to be both complete, and the result of a >consensus process -- leaving those issues in limbo seems inappropriate. Amen. >At 01:28 13/10/2014, Suzanne Woolf wrote: >The working group will not attempt to produce or discuss >documentation for these details, but will request the IAB or IAOC to >provide them separately. Instead of updating the charter, I might just appeal for changing its name from "ianaplan" to "ianaplahplah"... >The WG shall seek the expertise of the IAB IANA Evolution Program to >formulate its output. It is expected that members of the IAB IANA >Evolution Program will actively participate in the WG." For our best common information: who in this debate is a member of the "IAB IANA Evolution Program"? How many here are in that Program and how many in total? >At 09:25 13/10/2014, Stephen Farrell wrote: > >On 13/10/14 04:52, Milton L Mueller wrote: > > I hope to see some response to this point from responsible IETF > participants. >You are an IETF participant since you are posting to this list. Agreed! :-) However, this may call for a more in depth reading of RFC 3935. >RFC 3935 - Definition of terms: >- "Volunteer Core - our participants and our leadership are people >who come to the IETF because they want to do work that furthers the >IETF's mission of "making the Internet work better"" >- "Participants: Individuals who participate in the process are the >fundamental unit of the IETF organization and the IETF's work." >- "Relevant: In this context, useful to some group of people who >have to make decisions that affect the Internet, including, but not >limited to, hardware and software implementors, network builders, >network operators, and users of the Internet. Note that it does not >mean "correct" or "positive"" RFC 3935 - Mission Statement: "The IETF has to make decisions. And in some cases, people acting on behalf of the IETF have to make decisions without consulting the entire IETF first" - "Having a defined mission is one of the steps we can take in order to evaluate alternatives: Does this help or hinder the mission, or is it orthogonal to it? If there are limited resources, are there things that they could be invested in that help the mission better? Having a defined mission is one of the steps we can take in order to evaluate alternatives: Does this help or hinder the mission, or is it orthogonal to it? If there are limited resources, are there things that they could be invested in that help the mission better? (Another step is to choose leaders that we trust to exercise their good judgement and do the right thing. But we're already trying to do that.)". The leaders who we trust have exercised their good judgment and have done the right thing in changing the mission (and the standard process) of the IETF, through RFC 6852. - From IETF: "to make the Internet work better" by rough consensus. - To OpenStand IETF: "to contribute to the economics of global markets fueled by technological advancements, in driving a global deployment of standards developed through an open participatory process and voluntarily adopted globally that support interoperability and foster global competition regardless of their formal status, serve as building blocks for products and services targeted at meeting the needs of the market and consumer, and thereby drive an innovation that in turn will result in the creation of new markets and the growth and expansion of existing markets." As a result, we face a cultural difference between the traditional IETF "rough consensus" and the new ISOC/OpenStand RFC 6852 "broad consensus" documented by Lynn St-Amour/Don Tapscott's in the Internet multi-stakeholders GSN doctrine sponsored by Google/State Department/RBC, etc. and adopted, imposed, and propagated by the NTIA. - in the IETF, the rough consensus is evaluated by the Chair, - in a GSN environment, broad consensus is worked out among the WG-advised leaders of the mutually selected stakeholders in order to enforce the assigned goal. In this case, the goal assigned to the WG is to document a seamless application of the NTIA ukase, thereby making the internet work better or not. As if the govs and users were to seamlessly adopt a strategy that they have already voted gainst and will vote against - as they consider it preoccupying for democracy, people rights, development, and world peace as being demanded by the core (*) dominant state, the invading edge (*), and the spying leader (*) for economic reasons (*). Our best interest is the same as the US best interest, i.e. internet stability, neutrality, and transparency. Our duty is to make the NTIA understand that the way to reach that common goal is not the "status quo" and the ICANN being unilaterally global (BUG) to best serve a Business United Governance (BUG). (*) <note>These terms are from/to be considered in relation to the RFC 3935 definition of the term "Internet": " The Internet: A large, heterogeneous collection of interconnected systems that can be used for communication of many different types between any interested parties connected to it. The term includes both - the "core Internet" (ISP networks) - and "edge Internet" (corporate and private networks, often connected via firewalls, NAT boxes, application layer gateways and similar devices). The Internet is a truly global network, reaching into just about every country in the world. The IETF community wants the Internet to succeed because we believe that the existence of the Internet, and its influence on economics, communication, and education, will help us to build a better human society". At that time (10 years ago this month), the Internet was to influence economics rather than to be led by it. Its target was to build a better human society; not to reduce us into better consumers parked in global market communities. <note> >At 12:08 13/10/2014, Richard Hill wrote: >The IGC charter says that the ICG will deliver its report to the >NTIA. Since the discussions on this list are about replying to the >ICG, I think that we have to stick to what the ICG charter says. We can certainly take into account what the IGC will tell ICANN to report to the NTIA on the IANA transition in response to their question on the DNS transition. However, don't you think we should mainly focus on telling the IESG that we want to stick to the way to make the internet work better under the new circumstances that we observe and expect? >At 16:06 13/10/2014, Andrei Robachevsky wrote: >Why don't we recommend that these (or similar) provisions are added >to the existing MoU, since, as we all agree, the existing system >hasn't raised any concerns for the IETF? what about the wording/relation with RUSIANA, CNIANA, INDIANA, JFCIANA? Cheers jfc