Re: Data on internet drafts/year?

Melinda Shore <melinda.shore@gmail.com> Fri, 26 September 2014 05:43 UTC

Return-Path: <melinda.shore@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 3369D1A1A18 for <ietf@ietfa.amsl.com>; Thu, 25 Sep 2014 22:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 44uKA9aaIWGn for <ietf@ietfa.amsl.com>; Thu, 25 Sep 2014 22:43:06 -0700 (PDT)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7A071A02BA for <ietf@ietf.org>; Thu, 25 Sep 2014 22:43:06 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id y13so11992381pdi.16 for <ietf@ietf.org>; Thu, 25 Sep 2014 22:43:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=PBKdJvwUOAuk8n9d1ucIzQdOLImjzTyp7lTXyswHh6Y=; b=tLI4lDKDlFKkUjMYdfv5uz9F2d1PbFoaF2eh6ebDb40xBSWIjqOYVkDppS4mo2O2tt ph7+8bDKBuXGsXO8DhFPwUMY3fLTTjtbprkvGfZOr4K2edNDX3NHxc+pFCGcfhZ/Oz3Q X203QxfLBCvx/KbjQFW7nkCLAG44UIU6uE96M6V8ovdt7GKh/OJnNbWadJC3Zf/wVOAT Dd0DA7aCtU76SXa1/YOGggVbSESyQkqySbiQITUZSx6h3qhg46xFeGjwbDQObrkJBC8J raCoYa9+1CE3TWJVcJDbnnE4NH4W9oO1/ob7R+imi/0eg3wgVQI1RdbypRwgWiyNEkpj +rcw==
X-Received: by 10.69.27.71 with SMTP id je7mr26769149pbd.155.1411710185554; Thu, 25 Sep 2014 22:43:05 -0700 (PDT)
Received: from spandex.local (209-193-56-116-rb1.fai.dsl.dynamic.acsalaska.net. [209.193.56.116]) by mx.google.com with ESMTPSA id z1sm3795358pdb.21.2014.09.25.22.43.04 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 25 Sep 2014 22:43:05 -0700 (PDT)
Message-ID: <5424FCE7.6070308@gmail.com>
Date: Thu, 25 Sep 2014 21:43:03 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Data on internet drafts/year?
References: <5424D0BF.3020800@gmail.com> <DEE2D5B8-CF87-4A0D-9838-55842A665791@cisco.com> <E47E25F3-33E9-40D2-B97F-148C771770B9@cs.georgetown.edu> <5424EF26.8020600@gmail.com> <EBB08758-3E5C-4A15-92C6-9920D4D6F1A7@cisco.com>
In-Reply-To: <EBB08758-3E5C-4A15-92C6-9920D4D6F1A7@cisco.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/KpsvrFsauYw-AKLqXRulpr8_3Xw
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: Fri, 26 Sep 2014 05:43:08 -0000

On 9/25/14 9:35 PM, Fred Baker (fred) wrote:
> My understanding, possibly incorrect, is that the process delay is
> intentional. A brief look at the RFC series and the internet drafts
> will tell you that we often start a project with a solution looking
> for a problem.

That seems to mirror the situation in which we
seem to be seeing an increasing number of drafts describing a
problem for which there's not really any demand for a solution,
but it seems like an interesting problem (plus the question of whatever
incentives may or may not be provided by an employer to have
stuff working its way through the IETF process, regardless of
actual need).

At any rate I do think we're seeing a lot of low-quality problem
statement drafts.  The number of problem statement drafts is
clearly increasing and it may be the case that any time the
number of <whatever> goes up, the percentage of low-quality
<whatevers> increases, but still.  My core concern that we're
creating this process that requires going through a problem
statement/use cases/requirements/gap analysis/etc. ritual and
that actual protocol work doesn't happen for several years after
the work is chartered (then isn't published for several more
years).

Melinda