Re: Long-term IETF evolution thoughts

<nalini.elkins@insidethestack.com> Sun, 12 June 2016 15:27 UTC

Return-Path: <nalini.elkins@insidethestack.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 1328D12D0F5 for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2016 08:27:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 Wj2hsaYeR4D3 for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2016 08:27:52 -0700 (PDT)
Received: from nm9-vm6.bullet.mail.ne1.yahoo.com (nm9-vm6.bullet.mail.ne1.yahoo.com [98.138.91.102]) (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 815E412B062 for <ietf@ietf.org>; Sun, 12 Jun 2016 08:27:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1465745271; bh=MDUo30D5KRtTDnJEBmb/4S11uG3jv47aW94NQTKyQY4=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=dgXgNLds5D+GLE7XJOcAM9XPlNHL0+Fvu3sp7fxaW+D121exb3Kgiu+Hciq5m+fsJ3WTikDQTcIsArejPB15SKyUmba2tc4S1nCQ7J+HdyxF18m8t15H+9shGN3xZwbMVZkGfx4mvS9CuBl0PvdNe6ENQYoRmjQYmMPhOBUQ02P2vuveorgPDz/Uq800JR8GQyLhvbMLRN3RgwHHH6onsaFYIjbghk9wazevKys+k0ck0T8QVstumGWuXM4PZid45JZ3b7m7j5uOxTbQ/zSsPrW0m3udAlU/CDu7FZ99X+tnLtGHws54u6IL9iLZ0HxPyyV7qXIa2SigTW+xiguHPw==
Received: from [98.138.101.128] by nm9.bullet.mail.ne1.yahoo.com with NNFMP; 12 Jun 2016 15:27:51 -0000
Received: from [98.138.89.240] by tm16.bullet.mail.ne1.yahoo.com with NNFMP; 12 Jun 2016 15:27:51 -0000
Received: from [127.0.0.1] by omp1013.mail.ne1.yahoo.com with NNFMP; 12 Jun 2016 15:27:51 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 768198.89165.bm@omp1013.mail.ne1.yahoo.com
X-YMail-OSG: Lr8CPvkVM1nG.LTjmn9ffbZW2saw5L1XGtOdr2OXdeysuycRxtxjIe_EW1AqabA Eck.XzXDsXO8sRIoyh01loBrNnFjvlxcolwneyAHAOTeCpEKPlPHuMPmaVqczo672zjogh2rGUvX FC7H0lbwdLHA3iI2HDkI1cAIe1lYHxgzP3gqhSQ8JkerY0jn1QStgmPT0NnwrjbmPtevHGKFnJsJ h6vERYZTewk__ZgaFT.My7qx7pTd33F1dLWDhT0fuzn9iuMAiKvmMdiEGuesu3OWMHhXAJyH9H3M Xp1UaiO_6yVO5V2hBUE_qQURzSoY3p1eIDVoQU_wYarOuiOWEZS.9L2ges1t_aFj3aDZglSMUYVX QR0egKrwjyj4.Dwr6EjMJrIEuQjng05UIKdwwgaCytYZjWgx0OK7ZHRFPZFizk2PurFB1Akh9jkv gSg6C_5nJulZqOlwzJ_MeNqLFqA9Z2qt6GyYh6JAT.aSOju12kza.zB5MfeDULHUr8pxAceJi.yp qF.RJ0Yvyx46mFDX1rqpYyZnPdpKw5CJhJfAYqDsn0BuHuQKOwJfcFdqGkMY0l5TawAMv2gM-
Received: from jws10031.mail.ne1.yahoo.com by sendmailws101b.mail.ne1.yahoo.com; Sun, 12 Jun 2016 15:26:11 +0000; 1465745171.676
Date: Sun, 12 Jun 2016 15:26:11 +0000
From: nalini.elkins@insidethestack.com
To: "ietf@ietf.org Discussion" <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>, "chair@ietf.org" <chair@ietf.org>
Message-ID: <1963141881.1341471.1465745171134.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <B937F6B4-248F-42B7-BBDB-C82B914C874C@ietf.org>
References: <B937F6B4-248F-42B7-BBDB-C82B914C874C@ietf.org>
Subject: Re: Long-term IETF evolution thoughts
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_1341470_4576307.1465745171129"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9fohwuVbsQZ2x397zKVmL30uXCM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
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, 12 Jun 2016 15:27:54 -0000

Jari,
Thank you for doing this.  I think that having community input on our path forward (as well as actually having a thoughtful path forward!) is very important.
My first comment is about the involvement of other communities.  You had mentioned Open Source.  That is great but I feel there are some other communities which are under-represented:
1.  Large enterprise operators / other operators2.  Implementors (other than open source)3.  Startups (I believe this was brought up before)
The reason I believe that these are important is because there has to be a feeback loop between standards, implementation and usage.   All too often, this loop does not exist.  
What sometimes happens is, for example, the "end user" of the standard, say the large enterprise, is shocked to find that a feature they had relied upon is now gone with a new version of a standard.   Of course, they were never at the IETF meetings where this was even discussed five years before.   Otherwise, they would have known or been able to give feedback.  I am actually involved in such a case at this very moment.   Some quite lengthy emails have gone back and forth in the last couple of days between a major U.S. corporation and one WG about changes in an upcoming standard.
The larger question, though, is why such people are not involved.  I suspect, that partially, it is similar to the "tragedy of the commons".   Enterprises feel that this affects many of them, so why should they be the ones paying for someone to go?  Why doesn't someone else?  Of course, when everyone feels this way, then no one goes.  Which is where we find ourselves.  I don't want to get completely distracted by numbers but I would bet I could count the number of large enterprises at the IETF on the fingers of my hand.
This is not a winning proposition for the IETF either.   The more people who actually are directly impacted by the standard are involved in providing comments, the better and longer lasting standards we will create.
Any organism (including the IETF) needs an effective feedback loop to thrive.   I hope we can better involve such people in the IETF.  Thanks,
Nalini ElkinsInside Products, Inc.www.insidethestack.com(831) 659-8360