RE: Observations on (non-technical) changes affecting IETF operations

Linda Dunbar <linda.dunbar@huawei.com> Tue, 01 March 2016 18:17 UTC

Return-Path: <linda.dunbar@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C46B21B31D9 for <ietf@ietfa.amsl.com>; Tue, 1 Mar 2016 10:17:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.206
X-Spam-Level:
X-Spam-Status: No, score=-4.206 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] 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 TpXdxs1ibrLR for <ietf@ietfa.amsl.com>; Tue, 1 Mar 2016 10:17:24 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 734B51B31DC for <ietf@ietf.org>; Tue, 1 Mar 2016 10:17:23 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CJJ87069; Tue, 01 Mar 2016 18:17:21 +0000 (GMT)
Received: from DFWEML705-CHM.china.huawei.com (10.193.5.142) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 1 Mar 2016 18:17:18 +0000
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml705-chm ([10.193.5.142]) with mapi id 14.03.0235.001; Tue, 1 Mar 2016 10:17:05 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Jari Arkko <jari.arkko@piuha.net>, IETF <ietf@ietf.org>
Subject: RE: Observations on (non-technical) changes affecting IETF operations
Thread-Topic: Observations on (non-technical) changes affecting IETF operations
Thread-Index: AQHRcz0rq/HdoKLTwEWLoAYCbJ4TtJ9E1Gcg
Date: Tue, 1 Mar 2016 18:17:04 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F657DF2330@dfweml701-chm>
References: <E83FC2B4-867D-44C9-AE1B-F4C414ABD041@piuha.net>
In-Reply-To: <E83FC2B4-867D-44C9-AE1B-F4C414ABD041@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.236]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F657DF2330dfweml701chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090205.56D5DCB1.014A, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 00bc5bb15bdcbdbf41922dfde0b16f83
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/GssBkTqYfGm2-veEzCrZBANuPwI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 01 Mar 2016 18:17:28 -0000

Jari,

Very interesting write up. IMHO, the hardest challenge facing IETF is that "Internet has been working over several decades".
All the obvious technologies needed to enable Internet have been developed already. All that left are tweaks and minor improvement.

Maybe it is the time to update the goal of the IETF.
(is it still true: "The IETF brand is core Internet technology, and improving the Internet, not specifically new things.?)

We all know that the future belongs to the App & services. But people from those emerging App & services companies are way under represented in IETF.

Maybe more Heckathons effort should be invested into attracting Apps & Services companies to utilize the work developed by IETF, ...

My two cents,

Linda Dunbar

-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Jari Arkko
Sent: Monday, February 29, 2016 4:04 PM
To: IETF
Subject: Observations on (non-technical) changes affecting IETF operations


A while back I had asked for volunteers to join a design team to look at (non-technical) trends and changes that relate to IETF operations.

The team has been working and they have today published an -00 draft. We'd love to have your feedback and thoughts on this topic!

The document details are below:

Title: IETF Trends and Observations

Team: Jari Arkko, Alia Atlas, Avri Doria, Tobias Gondrom, Olaf Kolkman, Steve Olshansky, Benson Schliesser, Robert Sparks, Russ White

URL:
https://tools.ietf.org/html/draft-arkko-ietf-trends-and-observations-00

Abstract:

While most of the work in the IETF is technical, the IETF should and does regularly examine itself, including its processes and goals, to determine if the technical community is truly serving the larger network engineering community effectively.  Changes in this area tend to be incremental, as is fitting for an organization with decades of experience and history in developing and managing the process of building technical specifications.

The rapid and ongoing changes in the world have recently caused a number of IETF participants to examine the current processes and operation of the IETF, particularly in the context of the culture of the IETF.  This memo discusses some cultural and global trends in relation to the IETF's operating environment, how these trends might affect the operation of the IETF, and notes some topics for further exploration.

Writing this memo has been inspired by involvement in various decisions that the IETF leadership has to take part in, often wishing to be able to draw more on understanding trends and their impact on the IETF.

This memo is also input for discussion that the IETF community should have.

The memo has no particular official standing, nor does it claim to represent more than the authors' thinking at the time of writing.
There is no intent on the part of the authors for this to be published as a RFC.  Please direct discussion about this topic to the ietf@ietf.org<mailto:ietf@ietf.org> mailing list.