Re: "why I quit writing internet standards"
Alia Atlas <akatlas@gmail.com> Mon, 14 April 2014 16:08 UTC
Return-Path: <akatlas@gmail.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 E837B1A0601 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:08:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level:
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 d9jLatI3NtFv for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:08:01 -0700 (PDT)
Received: from mail-yk0-x234.google.com (mail-yk0-x234.google.com [IPv6:2607:f8b0:4002:c07::234]) by ietfa.amsl.com (Postfix) with ESMTP id 5A4221A03D7 for <ietf@ietf.org>; Mon, 14 Apr 2014 09:07:45 -0700 (PDT)
Received: by mail-yk0-f180.google.com with SMTP id 19so7528140ykq.25 for <ietf@ietf.org>; Mon, 14 Apr 2014 09:07:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=yudIQ+i4/XPNt01Y7SCrYHCNsL88ZDL8gALkRqKJ170=; b=0zgrECxAVHH9EOI1xIE/0OOE6jTk1Zn+GJ/+8E6xedlqE63ptvfiVEpsW+FxQKqZPV jyCOkMQW2z7ddu7lBlMa1LSLLMZXo4iGXLAHpXbXX2fHTYFd8u8H3tTOCaO330SAj9R+ 8yAj2zU1JXzAGVyz1SxWSGhcdab5rg6K+Vjme80qO1Z0PFRmSgleeK+qc3mKLu2pqWSI 1UbJlhwPudDGcu2FQt8TX4Cqz1XxGtaOTdomSPzmGNxsPss87mviOl0MyNSl0iJllxXT KM/bzt5yFh3srMVhWxeqPP2xlktG/5JSps9z8nEy5xGFnw6sYUBq3wRPSPBEoEwGLybP 0DrQ==
MIME-Version: 1.0
X-Received: by 10.236.138.73 with SMTP id z49mr2013202yhi.152.1397491661698; Mon, 14 Apr 2014 09:07:41 -0700 (PDT)
Received: by 10.170.194.69 with HTTP; Mon, 14 Apr 2014 09:07:41 -0700 (PDT)
In-Reply-To: <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com>
References: <CF71721A.180A9%wesley.george@twcable.com> <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com>
Date: Mon, 14 Apr 2014 12:07:41 -0400
Message-ID: <CAG4d1rfFKB-8CRbj21ZOrGKps9ctz88m-4=yYYCVmYp3ks1ryg@mail.gmail.com>
Subject: Re: "why I quit writing internet standards"
From: Alia Atlas <akatlas@gmail.com>
To: David Meyer <dmm@1-4-5.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gX5V1wJVv-2RFggssvmk-jYf0zE
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: Mon, 14 Apr 2014 16:08:03 -0000
On Mon, Apr 14, 2014 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. [Alia] It would be very useful to have a functional model for how the two can compliment each other. We also tend to talk about open-source as a single monolith - when it can have very different models for accepting in changes, how and who runs the community, who is really participating (open source doesn't mean non-corporate) etc. Some of what the IETF does is the architecture and requirements thinking about how the solution should fit in - while some of the open-source is about getting a solution implemented ASAP. IMHO, a spiral is useful with an easy way of interaction. With I2RS, as a WG chair, I suggested having experimental drafts describing solutions that were being implemented - but haven't seen any. A question is what is needed to encourage the interactions. [Alia] Diversity of implementation is important as is stability of a standard and it being understood how to change/upgrade for different versions. These don't come automatically via open-source. Regards, Alia
- "why I quit writing internet standards" George, Wes
- Re: "why I quit writing internet standards" David Meyer
- Re: "why I quit writing internet standards" Miles Fidelman
- Re: "why I quit writing internet standards" Alia Atlas
- Re: "why I quit writing internet standards" Christian de Larrinaga
- Re: "why I quit writing internet standards" Andy Bierman
- Re: "why I quit writing internet standards" Abdussalam Baryun
- Re: "why I quit writing internet standards" Ted Lemon
- Re: "why I quit writing internet standards" Michael Richardson
- Re: "why I quit writing internet standards" Tim Wicinski
- Re: "why I quit writing internet standards" Andy Bierman
- Re: "why I quit writing internet standards" Simon Pietro Romano
- Re: "why I quit writing internet standards" Miles Fidelman
- Re: "why I quit writing internet standards" Murray S. Kucherawy
- Re: "why I quit writing internet standards" David Meyer
- Re: "why I quit writing internet standards" Murray S. Kucherawy
- Re: "why I quit writing internet standards" Murray S. Kucherawy
- Re: "why I quit writing internet standards" Miles Fidelman
- Re: "why I quit writing internet standards" Dale R. Worley
- Re: "why I quit writing internet standards" Scott Kitterman
- Re: "why I quit writing internet standards" Miles Fidelman
- Re: "why I quit writing internet standards" Jari Arkko
- Re: "why I quit writing internet standards" Bjoern A. Zeeb
- Re: "why I quit writing internet standards" Spencer Dawkins
- Re: "why I quit writing internet standards" Carsten Bormann
- Re: "why I quit writing internet standards" Spencer Dawkins
- Re: "why I quit writing internet standards" Thomas Clausen
- Re: "why I quit writing internet standards" Wesley Eddy
- Re: "why I quit writing internet standards" Yoav Nir
- Re: "why I quit writing internet standards" Thomas Clausen
- Re: "why I quit writing internet standards" Wesley Eddy
- Re: "why I quit writing internet standards" Miles Fidelman
- Re: "why I quit writing internet standards" Spencer Dawkins
- Re: "why I quit writing internet standards" Thomas Clausen
- Re: "why I quit writing internet standards" Melinda Shore
- Re: "why I quit writing internet standards" Carsten Bormann
- Re: "why I quit writing internet standards" Thomas Clausen
- Re: "why I quit writing internet standards" Spencer Dawkins
- Re: "why I quit writing internet standards" Brian E Carpenter
- Re: "why I quit writing internet standards" Dave Cridland
- Re: "why I quit writing internet standards" Thomas Nadeau
- Re: "why I quit writing internet standards" Thomas Nadeau
- Re: "why I quit writing internet standards" Benoit Claise
- Re: "why I quit writing internet standards" Benoit Claise
- Re: "why I quit writing internet standards" Benoit Claise
- Re: "why I quit writing internet standards" Thomas Nadeau
- Re: "why I quit writing internet standards" Miles Fidelman
- Re: "why I quit writing internet standards" Yoav Nir
- Re: "why I quit writing internet standards" S Moonesamy
- Re: "why I quit writing internet standards" Benoit Claise
- Re: "why I quit writing internet standards" Douglas Otis
- Re: "why I quit writing internet standards" Andy Bierman
- Re: "why I quit writing internet standards" Hector Santos
- Re: "why I quit writing internet standards" Dave Crocker
- Re: "why I quit writing internet standards" Scott Kitterman
- Re: DMARC not-WG, was "why I quit writing interne… John Levine
- Re: DMARC not-WG, was "why I quit writing interne… Dave Crocker
- Re: DMARC not-WG, was "why I quit writing interne… Hector Santos
- Re: "why I quit writing internet standards" Dave Crocker
- Re: "why I quit writing internet standards" Scott Kitterman
- Re: "why I quit writing internet standards" Dave Crocker
- Re: "why I quit writing internet standards" Scott Kitterman
- Re: "why I quit writing internet standards" Douglas Otis