Re: "why I quit writing internet standards"

Thomas Nadeau <tnadeau@lucidvision.com> Thu, 17 April 2014 12:16 UTC

Return-Path: <tnadeau@lucidvision.com>
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 58BA71A012B for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 05:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.071
X-Spam-Level: **
X-Spam-Status: No, score=2.071 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DATE_IN_PAST_06_12=1.543, RP_MATCHES_RCVD=-0.272] 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 yVHYeH6fmpb8 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 05:16:16 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 65DAA1A0118 for <ietf@ietf.org>; Thu, 17 Apr 2014 05:16:16 -0700 (PDT)
Received: from [192.168.1.112] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 8D63F276BB8F; Thu, 17 Apr 2014 08:16:12 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_E3BF1549-9A63-45F6-BDA0-4222A64FA4D7"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: "why I quit writing internet standards"
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com>
Date: Wed, 16 Apr 2014 20:49:50 -0400
Message-Id: <1E0D0E62-CF56-4FEC-9771-206758C80BB6@lucidvision.com>
References: <CF71721A.180A9%wesley.george@twcable.com> <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com>
To: David Meyer <dmm@1-4-5.net>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BrDwudC6vjAsq34fyq-TnGUnRWY
Cc: "ietf@ietf.org" <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: <http://www.ietf.org/mail-archive/web/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: Thu, 17 Apr 2014 12:16:21 -0000

On Apr 14, 2014:11:57 AM, at 11:57 AM, David Meyer <dmm@1-4-5.net> wrote:

> On Mon, Apr 14, 2014 at 8:08 AM, George, Wes <wesley.george@twcable.com> wrote:
>> I’m surprised that no one has sent this out yet:
>> http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
>> 
>> "Summary: After contributing to standards organizations for more than seven
>> years, engineer Vidya Narayanan decided it was time to move on. Although she
>> still believes that these organizations make the Internet a better place,
>> she wonders about the pace of change versus the pace of organizations."
>> 
>> My thoughts-
>> 
>> There are some nuggets of truth in what she says in this article, and in
>> some of the comments. I think that the problems are real, so there’s value
>> in taking the criticism constructively, despite the fact that the author
>> chose to focus on the problems without any suggestions of solutions.
>> 
>> "while the pace at which standards are written hasn’t changed in many years,
>> the pace at which the real world adopts software has become orders of
>> magnitude faster."
>> …
>> "Running code and rough consensus, the motto of the IETF, used to be
>> realizable at some point. … In the name of consensus, we debate frivolous
>> details forever. In the name of patents, we never finish.”
>> …
>> "Unless these standards organizations make radical shifts towards
>> practicality, their relevance will soon be questionable.”
>> 
>> I don’t have too many big ideas how to fix these problems, but I’ll at least
>> take a crack at it in order to spur discussion. My paraphrase of the problem
>> and some discussion follows.
>> 
>> - We’ve lost sight of consensus and are too often derailed by a vocal
>> minority of those willing to endlessly debate a point.
>> 
>> Part of the solution to that is reiterating what consensus is and is not,
>> such as draft-resnick-on-consensus so that we don’t confuse a need for
>> consensus with a need for unanimity. Part of the solution is IETF leadership
>> helping to identify when we have rough consensus encumbered by a debate that
>> will never resolve itself, without quieting actual disagreement that needs
>> continued discussion in order to find a compromise. I don’t have good
>> suggestions on how to make that second half better.
>> 
>> - We don’t have nearly enough focus on running code as the thing that helps
>> to ensure that we’re using our limited cycles on getting the right things
>> out expediently, and either getting the design right the first time, or
>> failing quickly and iterating to improve
>> 
>> The solution here may be that we need to be much more aggressive at
>> expecting any standards track documents to have running code much earlier in
>> the process. The other part of that is to renew our focus on actual interop
>> standards work, probably by charter or in-group feedback, shift focus away
>> from BCP and info documents. Perhaps when considering whether to proceed
>> with a given document, we need test as to whether it’s actively
>> helpful/needed and ensure that we know what audience would be looking at it,
>> rather than simply ensuring that it is “not harmful” and mostly within the
>> WG’s chartered focus.
> 
> My friend @colin_dixon pointed this out to me yesterday, and I've been
> giving it quite a bit of thought since then (I have a nascent blog on
> the topic of how open source and standards orgs might
> productively/efficiently work together; follow up to
> http://www.sdncentral.com/education/david-meyer-reflections-opendaylight-open-source-project-brocade/2014/03).
> 
> What I can say is that after seeing the kind of progress that several
> open source communities make (they do epitomize the best of the IETF's
> running code/rough consensus ethic), one does have to wonder if
> traditional standards making is either obsolete or in dire need of a
> make over. What is needed, IMO, is a reimagining of how the standards
> process interacts with the open source movement specifically focused
> on how they can compliment one another.
> 
> --dmm

	I think its the latter - a make-over or an adjustment are needed to how we work within this organization. The pendulum has clearly swung so far into the direction of over-caution, over-thinking, and over-design (i.e.: requirements, problem statements, architectures and frameworks) that the real cost is too high in terms of real dollars invested on the process, as well as real product development delay where people have to wait for the process to maybe put something out years from its onset. We also need to directly address the interference in the process by individuals and organizations who will never implement the things they are here to "work" on things in theory. In open source, code is the coin of the realm, so its very much a "put up or shut up" model; opinions don't count for much if anything. So if what you bring to the party is a code patch that everyone agrees on, thats cool, but if you just say "hey I'd like to add option X or lets do this another way", you really are out in the cold. We need to get back to a model where the opinions of those implementing things and those really deploying those things is what really is what matters.

	Until then, the most important observation is that the process has ground nearly to a halt in many areas which has resulted in a severe reduction in the speed of innovation. The market has responded and gone elsewhere. That is a fact, and denying it is unrealistic. Take note: many of us have seen and are involved in real examples of this from even traditional service providers, who are now actively demanding open source-based products and/or are even trying to launch their own agile/open source-based initiatives to foster rapid, collaborative AND interoperable product creation in leu of the IETF process.  But we need to get back to running code and rough consensus driving the process, rather than how things are now.

	--Tom