Re: draft-housley-two-maturity-levels

Phillip Hallam-Baker <hallam@gmail.com> Wed, 27 October 2010 00:03 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 14EC73A686E for <ietf@core3.amsl.com>; Tue, 26 Oct 2010 17:03:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.306
X-Spam-Level:
X-Spam-Status: No, score=-2.306 tagged_above=-999 required=5 tests=[AWL=0.292, 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 LlmedplRZ4Pe for <ietf@core3.amsl.com>; Tue, 26 Oct 2010 17:03:11 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 024843A6836 for <ietf@ietf.org>; Tue, 26 Oct 2010 17:03:09 -0700 (PDT)
Received: by gxk7 with SMTP id 7so43785gxk.31 for <ietf@ietf.org>; Tue, 26 Oct 2010 17:04:58 -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=quWl5xq/icczZggwtNMS2QErJS3fGu5ITndiq9bKIRQ=; b=S6tfg6Lz0okPDucYooXrJKGOCoovZp/6XGf74PGgI2BoYFquhHXzyogVcA51ssKg7E biuzEQYoWNYKlNqO6D5RpXsK9oisWVvZJh3ivRaqHI1Hq9ldq4fRsbG3uIZX+eqEL93u 7F+RipTgXlbmxtkaoCsWgMP4PmIsNZ6E1TR4A=
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=NdCivg5agHxm5fV7QRBPFxBTaO3K8ZIwUy/RG+apln3glCmsJPMnCyYHVFPfNo4WCj qzAbRhqEoSNcMNTVWdizoQWu/+aWlR6zMUwNFJcSaWl6yqlsM8TTWrxApm7JxOjCRkee nPrqaWPOs/A2Fc4x580BE4WAz6HI8EA6jyQDE=
MIME-Version: 1.0
Received: by 10.101.20.10 with SMTP id x10mr7299944ani.181.1288137897922; Tue, 26 Oct 2010 17:04:57 -0700 (PDT)
Received: by 10.100.41.14 with HTTP; Tue, 26 Oct 2010 17:04:57 -0700 (PDT)
In-Reply-To: <20101026232023.8FFF65B66CA@newdev.eecs.harvard.edu>
References: <20101026232023.8FFF65B66CA@newdev.eecs.harvard.edu>
Date: Tue, 26 Oct 2010 20:04:57 -0400
Message-ID: <AANLkTi=tZnyVV+bcikN3jcRYnhixHbt0sv6yDEtyb=wT@mail.gmail.com>
Subject: Re: draft-housley-two-maturity-levels
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "Scott O. Bradner" <sob@harvard.edu>
Content-Type: multipart/alternative; boundary="0050450176edd3d1e404938df98d"
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: Wed, 27 Oct 2010 00:03:16 -0000

There is a difference between a proposal that does not fix the problems that
you consider important and a proposal that does not fix any important
problems at all.

All that is being proposed here is a modest change that brings out
documented practices in line with the actual practice. Documenting actual
practice is usually a necessary step before attempting a change.


We have tried to bring actual practice in line with the three step process
on several occasions and they have all failed.

The cost of the status quo is that it diminishes the influence of the IETF
in the Internet community and it means that we spend an amazing amount of
time discussing proposals to change a process that absolutely nobody will
stand up and make a positive case for.

'Needs more time for discussion' is not a positive case for the current
scheme. We have had a decade of discussion and plenty of time for
alternative proposals.

'The alternatives may be worse' is not a positive case when we all agree
that we are not using the current documented process and cannot make it
work.

The only case I can see for not making this change is that it may forestall
more substantial changes such as introducing a protocol maintenance process
like the ITU has with defect reports and so on. But I don't think it is
practical to expect that to happen and I don't think that anyone making that
case is an advocate for more radical change in any case.


If the two step process is accepted, the positive outcome will be that
instead of the majority of Internet STANDARD status documents being
obsoleted, the majority of STANDARD status documents will be the most
current documentation of the corresponding protocol.

This is the least effort means of reaching that result. It is a useful and
necessary step.


On Tue, Oct 26, 2010 at 7:20 PM, Scott O. Bradner <sob@harvard.edu> wrote:

>
> Phillip politely says
> > I think this is nonsense.
> > We have been discussing this for over a decade. Time for debate is up. It
> is
> > time to make a decision.
>
> since I see no reason to think that the proposed changes will do
> anything at all to address any of the problems that I, and others, have
> brought up (incuding the 'nothing progresses' problem) I have decided
>
> I see no reason that we should make a change that is very likely to
> not fix any known problem just because we have been talking about
> various ideas for change for a long time - length of debate is not
> an indication of usefulness of solution
>
> it would not be the end of the IETF if this gets published but
> it will also not be the begining of a better IETF - all of the
> problems will still be there and we would have a meaningless change
> just so we can say we made a change
>
> Scott
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



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