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

Dave Cridland <dave@cridland.net> Sun, 06 March 2016 22:13 UTC

Return-Path: <dave@cridland.net>
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 BC13A1B3798 for <ietf@ietfa.amsl.com>; Sun, 6 Mar 2016 14:13:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 LPx1mseSlZeA for <ietf@ietfa.amsl.com>; Sun, 6 Mar 2016 14:13:22 -0800 (PST)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7849E1B3AD1 for <ietf@ietf.org>; Sun, 6 Mar 2016 14:13:21 -0800 (PST)
Received: by mail-wm0-x230.google.com with SMTP id p65so85906145wmp.1 for <ietf@ietf.org>; Sun, 06 Mar 2016 14:13:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=zvyxgfXBggt+Kd32RsYbhyfr+acQ3ktImWCDmxBFMOE=; b=BRSlZ3BiFNiKMHnoakduViU8JSN9MfjOKXhI67R/CaSjaUsI2AIu9yM5VPLfRUj/q7 ZgKIAp9KtNtSmCbGBChZBi84XydRn0de3U7EPZaVAtt75MPsMuTEjDVzLv8wLQN+ezxf YZelKqegjYKKitCW+QCarTQW9Cw/EaFhKKdbU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=zvyxgfXBggt+Kd32RsYbhyfr+acQ3ktImWCDmxBFMOE=; b=dNHps89hqsdZko1+V9spXIQ/thvtymHVThV0BhLKSu2zvDVc43Ip4olcRyr9L2zA5e DB43xt/nm3luPnNcwXWyIXuxMBmt5NtwlYFlEEhQx4WVXmZnk7KAJsjllv2pCCbtwRL4 1YrSa8fzcau7QPQHrPs2S2JvduOKrcl4xLla6qjyLfjvmpVSWZ/73+WGem42tEU8ZNE4 qwao0RsGDCl4fYIfyqx7fwlredvUGgajuwYIsK/AcAtdDnve7cMVqmi/3iDO+ZOP/KfI S08XQqXsLlJCaij9atX3u77E9MGkKJ+YCJaSr6cVraRi8oY+0x2s2QtaHqFAaIr2/w9j pPMw==
X-Gm-Message-State: AD7BkJISGAxzuTOY5/RZZehjJTpimBv2hhZuZHSu/wUmmSE7bPJaFLNeqF2vEUTSqeVuVPV/akb4qmcrX0gATMWd
MIME-Version: 1.0
X-Received: by 10.194.189.231 with SMTP id gl7mr19136205wjc.162.1457302400043; Sun, 06 Mar 2016 14:13:20 -0800 (PST)
Received: by 10.28.37.199 with HTTP; Sun, 6 Mar 2016 14:13:19 -0800 (PST)
Received: by 10.28.37.199 with HTTP; Sun, 6 Mar 2016 14:13:19 -0800 (PST)
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F657DF2330@dfweml701-chm>
References: <E83FC2B4-867D-44C9-AE1B-F4C414ABD041@piuha.net> <4A95BA014132FF49AE685FAB4B9F17F657DF2330@dfweml701-chm>
Date: Sun, 6 Mar 2016 22:13:19 +0000
Message-ID: <CAKHUCzyjUHZ2Tg0+zw7HRXF=cb8wvRBO1xC3=yUKdCoYz_tigQ@mail.gmail.com>
Subject: RE: Observations on (non-technical) changes affecting IETF operations
From: Dave Cridland <dave@cridland.net>
To: Linda Dunbar <linda.dunbar@huawei.com>
Content-Type: multipart/alternative; boundary=047d7bb046c0e2a41d052d68a7a3
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/zRSykgQZ8OZczu2bBjdt2LH8aAI>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
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: Sun, 06 Mar 2016 22:13:23 -0000

On 1 Mar 2016 18:17, "Linda Dunbar" <linda.dunbar@huawei.com> wrote:
>
>
> 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.
>

This put me in mind of the following, probably apocryphal quote:

"There is nothing new to be discovered in physics now, All that remains is
more and more precise measurement." - Attributed to Lord Kelvin, circa 1900.

> 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
mailing list.
>
>
>