Re: feedback & blog entry

todd <tglassey@earthlink.net> Fri, 20 September 2013 17:03 UTC

Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9CAB21F9CE9 for <ietf@ietfa.amsl.com>; Fri, 20 Sep 2013 10:03:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.647
X-Spam-Level:
X-Spam-Status: No, score=-0.647 tagged_above=-999 required=5 tests=[AWL=-0.463, BAYES_40=-0.185, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hUsJPsPqecx0 for <ietf@ietfa.amsl.com>; Fri, 20 Sep 2013 10:03:08 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfa.amsl.com (Postfix) with ESMTP id C2CD121F9CDF for <ietf@ietf.org>; Fri, 20 Sep 2013 10:02:52 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=DN3MOpIBhDkpLE/xI9MmX5uToJrM5QKrZsLB2HKFcu0+fIP+i2Et0PuELnU3uMeM; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.1.110]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1VN46T-0001HI-A7 for ietf@ietf.org; Fri, 20 Sep 2013 13:02:49 -0400
Message-ID: <523C7FB8.1070000@earthlink.net>
Date: Fri, 20 Sep 2013 10:02:48 -0700
From: todd <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: feedback & blog entry
References: <2722B4FA-425D-45D7-B307-91D808C49FB3@ietf.org>
In-Reply-To: <2722B4FA-425D-45D7-B307-91D808C49FB3@ietf.org>
Content-Type: multipart/alternative; boundary="------------040807090400040500050102"
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79edf722d3932e648309361109970d2806350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Sep 2013 17:03:15 -0000

Issues: OK lets start here...

1)    Structure and Political Representation inside the IETF

Bluntly the IETF@IETF WG is a silo which has erected a wall around 
itself to make it the controlling power - the problem is its failure to 
provide proper integration and acceptance practices for all other IETF 
members

That means it rules the IETF and all of the subordinate entities like 
IANA, ARIN, and the ISOC to some extent though this process with no 
formal representation of the entities within the IETF. There are clearly 
legal issues with this any sane person should see - and I mean that.

This also means the IETF@IETF.ORG group may not make any modifications 
to the Use or Publication Licenses for anything that is not approved by 
the specific standards generation teams and their sponsors but also the 
WG's themselves.

in fact I would suggest a new Responsibilities RFC be produced to 
control what a WG Director and AD are specifically (and in a legal sense 
within the IETF and its process) responsible for.


2)    Transparency

Accountability - there is NO transparency inside the IETF which would 
meet the audit requirements of any of the participating orgs or 
governments. That means how tghe oversight is performed and all of the 
IESG meetings must become transparent. Any and all communications both 
in-line and OOB must be disclosed and maintained. It is what it is... 
sorry.

OPINION: The IETF quantifies the Wild West Mentality that is still the 
Internet IMHO

3)    Contractual Process

The IETF group makes changes to IETF process which are untested and 
unapproved by the members at large; That means it (the IETF@IETF.ORG WG 
pers se) is changing and enforcing changes to IP contracts it is not a 
direct party to .

4)    The IETF has a freaking membership - get over it.

There is a membership and participants. Those parties are contractual 
participants in the process and any changes to the contracts or the 
participation process MUST be vetted by and approved by the Membership 
At Large and not shoved up the collective ass of the rest of the IETF by 
this illustrious group (does that language offend you - good wake up).

5)    Stop hiding behind the 107 exemption - it only belongs to IRTF.

The IETF process and IP disclosure processes need new review. The ONLY 
entity who can claim a research exemption here is the IRTF so the IETF 
publication license MUST be immediately amended to include notice of 
this and a new take down process for disputed IP be put in place...


Every publication house has a Take-Down rule for Copyright Violation and 
IP ownership claims. The IETF has facilitated a lie that it is doing 
RESEARCH - _/*wrong that is the IRTF's prerogative. */_

The IETF is in fact creating an IP which is collaboratively structured 
and as such it is not a research process it is a process of publication 
for use and that means the IETF itself has no 107 exception here. That 
is the purview of the IRTF  only...

Sorry but you folks did that to yourselves by not embedding the IRTF 
research Charter in the IETF itself.


Todd



On 09/20/2013 03:10 AM, IETF Chair wrote:
> One of things that I feel is important for the chair to do is to talk to various IETF contributors - not just on this list! :-) - and try to understand what issues they have, either technical or otherwise. Here's a small overview report of my recent effort to talk to various participants and organisations in China.
>
>     http://www.ietf.org/blog/2013/09/china/
>
> These specific observations aside, I wanted to highlight that while I try to talk to many people, it will take a long time and ultimately be a very small subset of people. Hence if you have feedback on how the IETF is doing, what new things we should do, or what we should differently - contact me. I'd love to know - and I can also speak for the rest of the people in leadership positions - that ideas, experiences, and feedback is always appreciated. Let us know.
>
> Jari Arkko
> IETF Chair
>
>


-- 
Todd S. Glassey
Personal Disclaimers Apply