Observations on (non-technical) changes affecting IETF operations

Jari Arkko <jari.arkko@piuha.net> Mon, 29 February 2016 22:04 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 3A8D91B3D95 for <ietf@ietfa.amsl.com>; Mon, 29 Feb 2016 14:04:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id vIQl5cb677oe for <ietf@ietfa.amsl.com>; Mon, 29 Feb 2016 14:04:08 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 84A5A1B3D90 for <ietf@ietf.org>; Mon, 29 Feb 2016 14:04:07 -0800 (PST)
Received: from localhost (localhost []) by p130.piuha.net (Postfix) with ESMTP id C38A12CEE6 for <ietf@ietf.org>; Tue, 1 Mar 2016 00:03:36 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([]) by localhost (p130.piuha.net []) (amavisd-new, port 10024) with ESMTP id gSpxN5-R0j8s for <ietf@ietf.org>; Tue, 1 Mar 2016 00:03:36 +0200 (EET)
Received: from [] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 1C4B22CC9A for <ietf@ietf.org>; Tue, 1 Mar 2016 00:03:36 +0200 (EET) (envelope-from jari.arkko@piuha.net)
From: Jari Arkko <jari.arkko@piuha.net>
X-Pgp-Agent: GPGMail 2.5.2
Content-Type: multipart/signed; boundary="Apple-Mail=_0CD6D48A-C700-4E4B-979A-29AC33B94E5E"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Subject: Observations on (non-technical) changes affecting IETF operations
Date: Tue, 01 Mar 2016 00:03:33 +0200
Message-Id: <E83FC2B4-867D-44C9-AE1B-F4C414ABD041@piuha.net>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/WwrQi72Ibilvpkf2FxfCY1gtt5c>
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: Mon, 29 Feb 2016 22:04:10 -0000

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



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

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

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.