Re: draft-housley-two-maturity-levels

Phillip Hallam-Baker <hallam@gmail.com> Thu, 28 October 2010 04:22 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3473E3A67AF for <ietf@core3.amsl.com>; Wed, 27 Oct 2010 21:22:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.319
X-Spam-Level:
X-Spam-Status: No, score=-2.319 tagged_above=-999 required=5 tests=[AWL=0.279, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ONppbUUYXN2z for <ietf@core3.amsl.com>; Wed, 27 Oct 2010 21:22:14 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id 201EA3A67AC for <ietf@ietf.org>; Wed, 27 Oct 2010 21:22:14 -0700 (PDT)
Received: by ywp6 with SMTP id 6so1039931ywp.31 for <ietf@ietf.org>; Wed, 27 Oct 2010 21:24:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=3c56gEVXIGrmjpu1ePeABNOIagc9kQDwzZ+p3g63Crk=; b=iGgHob8sEBSbM7QZA8NWTctmD0KxVYH9EZxNVR+N1nDkiXldoqRkHFLE5i7BTVf0Z8 fFdwZ5IQRgvujQ8RtIXUiITHQrKwkHF1IWTVC3WpVw3oyLG6CSU2teI6GKjHHuyG+rbU I9UehZeI06MhegptYSSN5rSutAKiR49wAkodE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=hyUyIupYfacKdscWUSXWCuUecCfaCSxi1P3lO2iMm6g2/1WTXjPnm/Np97lEQ6cAgX 6sS53rTyU3RLxVIS0L9+oAj//vngzYQGeduxFSm0y8P6aFMeYDlgIEgdz07dkHUE1y60 EtNO+UHkDQQJpbk3OGGDdBLBX19TgxYDIeAIk=
MIME-Version: 1.0
Received: by 10.100.195.15 with SMTP id s15mr8679726anf.124.1288239844795; Wed, 27 Oct 2010 21:24:04 -0700 (PDT)
Received: by 10.100.41.14 with HTTP; Wed, 27 Oct 2010 21:24:04 -0700 (PDT)
In-Reply-To: <4CC89E26.8010802@isi.edu>
References: <20101026232023.8FFF65B66CA@newdev.eecs.harvard.edu> <AANLkTi=tZnyVV+bcikN3jcRYnhixHbt0sv6yDEtyb=wT@mail.gmail.com> <046e01cb756d$cacf9d40$606ed7c0$@net> <4CC891F9.1030104@isi.edu> <06c201cb761e$bb391d50$31ab57f0$@net> <4CC89E26.8010802@isi.edu>
Date: Thu, 28 Oct 2010 00:24:04 -0400
Message-ID: <AANLkTi=10320yGUL_=qSKOOa6oXVO9mBeDi8n1H=vRAc@mail.gmail.com>
Subject: Re: draft-housley-two-maturity-levels
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Bob Braden <braden@isi.edu>
Content-Type: multipart/alternative; boundary="0016e645b7b655a6dd0493a5b690"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 28 Oct 2010 04:22:16 -0000

I think the problems are rather more complex.

>From what I hear, protocol design work is not highly rated by tenure
committees, nor is authorship of RFCs. The type of papers that count for
tenure are the ones that nobody in the field reads.

A lot of the problems we face are not the type of problem that academics can
get credit for solving. Or if they can get credit it is for the wrong type
of solution.

When people move from industry to take a tenure track teaching job their
IETF participation almost always dries up shortly afterward.


>From the industrial perspective, the three stage process is a budget killer.
When budgets get tight it is much harder to justify research staff working
on standards if they are not producing standards.

There are perfectly rational career advantages that cause people to drive
work to W3C or OASIS in preference to IETF. The competing institutions offer
a much more predictable process and a very high likelihood of a clear cut
success. In the IETF in contrast getting a document to DRAFT status has to
be explained as a victory. And that leaves a manager vulnerable when they
are trying to justify budgets against other departments.


On Wed, Oct 27, 2010 at 5:48 PM, Bob Braden <braden@isi.edu> wrote:

>
> Tony,
>
> I note that there seems to be some correlation between the degradation of
> the IETF process and
> the disappearance of the Internet research community from the IETF (the US
> government
> decided that no further R&D funding was required, since the Internet was
> "done".)
>
> Bob Braden
>
>> It would work if the overall process were more efficient. Now we
>> effectively
>> go WG I-D to full IS, which is what your eloquent overview of the driving
>> force notes. If we truncated WG I-D at the common points people could
>> agree
>> to start implementing, and have PS actually document the evolution of the
>> implementations, we would get back closer to when the IETF was productive.
>> ...
>>
>
>  Tony
>>
>>
>>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



-- 
Website: http://hallambaker.com/