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

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Mon, 21 March 2016 16:41 UTC

Return-Path: <eckelcu@cisco.com>
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 F3B6A12D81F for <ietf@ietfa.amsl.com>; Mon, 21 Mar 2016 09:41:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 a2mNUxSqdwW4 for <ietf@ietfa.amsl.com>; Mon, 21 Mar 2016 09:41:22 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE61F12D6EA for <ietf@ietf.org>; Mon, 21 Mar 2016 09:41:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1854; q=dns/txt; s=iport; t=1458578481; x=1459788081; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=e0zNpmVJ68yAXo+gsMNm7R6ZrtPLRPFO/6f1TdHrFGk=; b=Rcsc5Ds0kMnaBly4oVnpnIUEHUKnan4STPqBO7BEz12EBnj9GMxsxPwz w7nZP+HkE9+KXkWXPAcHRo122e7/XG1Q7QoAcS6e55qvvWF8wlBVnw821 KGP/2dvRvfmgRTbw1dG9bEcjeTZ7zZoyfURSjblDprIjJos1mbFb7s1Qz 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AYAgAFI/BW/4MNJK1egzSBRQa4EIIPA?= =?us-ascii?q?Q2BcIYNAoErOBQBAQEBAQEBZCeEQgEBBHkQAgEIRjIlAgQBDQUUCIgLvy4BAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEYiWN/ihIBBJdXAY4DjwePBQEeAQFCg2VqiRcBfQEBA?= =?us-ascii?q?Q?=
X-IronPort-AV: E=Sophos;i="5.24,372,1454976000"; d="scan'208";a="251059874"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Mar 2016 16:41:20 +0000
Received: from XCH-ALN-020.cisco.com (xch-aln-020.cisco.com [173.36.7.30]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u2LGfKJ0010280 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 21 Mar 2016 16:41:20 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-ALN-020.cisco.com (173.36.7.30) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 21 Mar 2016 11:41:20 -0500
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1104.009; Mon, 21 Mar 2016 11:41:19 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Jari Arkko <jari.arkko@piuha.net>, Phillip Hallam-Baker <phill@hallambaker.com>
Subject: Re: Observations on (non-technical) changes affecting IETF operations
Thread-Topic: Observations on (non-technical) changes affecting IETF operations
Thread-Index: AQHRcz0pMM7tsTD93US+tBCeIZfs059RV5kAgBHI5wCAAUWzAP//sscA
Date: Mon, 21 Mar 2016 16:41:19 +0000
Message-ID: <D3156F7C.69689%eckelcu@cisco.com>
References: <E83FC2B4-867D-44C9-AE1B-F4C414ABD041@piuha.net> <82AB329A76E2484D934BBCA77E9F5249A9FA6A7F@PALLENE.office.hd> <CAMm+Lwh+eY4miBH6n2ttwz00ypx9tVv0A4rM2v=VMQi6LH1h+w@mail.gmail.com> <DC437F67-52A1-4319-87D0-0499C9493983@piuha.net>
In-Reply-To: <DC437F67-52A1-4319-87D0-0499C9493983@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.1.160122
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [128.107.130.137]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <087A7441512978428A96F7C37EF257D0@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/rAALKWzRyVX_7tKbSPhn0e_461E>
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 16:41:23 -0000

On 3/21/16, 10:17 AM, "Jari Arkko" <jari.arkko@piuha.net> wrote:

>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Š

Excellent point. I have seen many examples of active participation of a
core set of people across related open source communities yielding great
results. The same principle applies to the IETF and open source
communities. The hackathons are one way to raise awareness and promote
collaboration, but what we really need is to have these adopters in the
open source community and elsewhere participating actively in IETF working
groups and vice versa.

Cheers,
Charles

>
>Jari
>