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

Jari Arkko <jari.arkko@piuha.net> Mon, 21 March 2016 14:17 UTC

Return-Path: <jari.arkko@piuha.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 EF14612D864 for <ietf@ietfa.amsl.com>; Mon, 21 Mar 2016 07:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 GrXlvjEXR5Wk for <ietf@ietfa.amsl.com>; Mon, 21 Mar 2016 07:17:52 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 5AD5612D849 for <ietf@ietf.org>; Mon, 21 Mar 2016 07:17:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 9820B2CCE2; Mon, 21 Mar 2016 16:17:43 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XygVo2EeddIt; Mon, 21 Mar 2016 16:17:43 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 23E232CC9A; Mon, 21 Mar 2016 16:17:43 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: Observations on (non-technical) changes affecting IETF operations
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_31F5D9E6-B790-48E6-9CC4-BBDB2DD2C560"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAMm+Lwh+eY4miBH6n2ttwz00ypx9tVv0A4rM2v=VMQi6LH1h+w@mail.gmail.com>
Date: Mon, 21 Mar 2016 16:17:42 +0200
Message-Id: <DC437F67-52A1-4319-87D0-0499C9493983@piuha.net>
References: <E83FC2B4-867D-44C9-AE1B-F4C414ABD041@piuha.net> <82AB329A76E2484D934BBCA77E9F5249A9FA6A7F@PALLENE.office.hd> <CAMm+Lwh+eY4miBH6n2ttwz00ypx9tVv0A4rM2v=VMQi6LH1h+w@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Px8aLe43_a3kKYRaAs1frsZ_ra0>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Mar 2016 14:17:55 -0000

Phillip, Charles,

> 1) A draft describing the protocol
>   a) Text describing protocol
>   b) Examples from running code
>   c) Reference section
> 2) Reference implementation

Yes, excellent!

> We need to consider how to make open source code readily available to community that might be interested in it, and to do so in a timely manner. We also need to consider the target audience, the end users of the code and specification. Much of the great work the IETF does never gets adopted. We need more focus on end user community and adoption. We need to consider barriers to deployability. Hackathons are a small step in right direction, but I thing we should consider offering training and keep end users in mind from the start and throughout the standardization process.

Yes, but I would approach this from a slightly different end-point. It is always the case that convincing others of something new is a lot of work. In my mind, standards or open source work both succeed best when performed by those who actually are deploying and in charge of building mainstream systems (commercial or open source) for the topic. So it is not so much about IETF folk reaching the adopters, but having the adopters drive the IETF work…

Jari