Re: draft-housley-two-maturity-levels

Mark Atwood <mra@pobox.com> Fri, 28 January 2011 07:12 UTC

Return-Path: <mra@pobox.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 596F83A6AF2 for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 23:12:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 fK-BD2AQSL6S for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 23:12:12 -0800 (PST)
Received: from sasl.smtp.pobox.com (b-pb-sasl-quonix.pobox.com [208.72.237.35]) by core3.amsl.com (Postfix) with ESMTP id 35A1B3A6AEA for <ietf@ietf.org>; Thu, 27 Jan 2011 23:12:08 -0800 (PST)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 62E4717A8 for <ietf@ietf.org>; Fri, 28 Jan 2011 02:15:13 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; s=sasl; bh=RKmpVXjTAYiQ UtENrZ9Ijp2rk48=; b=FWlITFalg0vqqBS7qCDBM873t2uu/QVQPxVYu8/4QWT6 G4LLUGvU7PeTSQWM9wF+sHd85C70eUnE7V9qItLIcIFXINiOu0SIYS/GHHKnT3kH 8Akt3oHX6EDm7HeJUhQt9uY7XcfKHp/t4yrpd1CRSVyoLrflPRd3hr/ukGt87PM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; q=dns; s=sasl; b=Bw5B5L iIDRTyKBtUThjlY3KXro58wiadYfXGLb7hCH7iDx+X1WAfdcswnn9x1gEeaL38TE 70Hv0nLSkmePXUB56JnJ/d2AHb+dbTa479q/nnLDqjaBaZPyHBBUChL81m4+fC9C o4H0SHp0dEaYPySA7QEVItJGzht7NWCMXGI14=
Received: from b-pb-sasl-quonix.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 5FA1317A7 for <ietf@ietf.org>; Fri, 28 Jan 2011 02:15:13 -0500 (EST)
Received: from mail-yx0-f172.google.com (unknown [209.85.213.172]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by b-sasl-quonix.pobox.com (Postfix) with ESMTPSA id 2D0A317A6 for <ietf@ietf.org>; Fri, 28 Jan 2011 02:15:13 -0500 (EST)
Received: by yxt33 with SMTP id 33so1074060yxt.31 for <ietf@ietf.org>; Thu, 27 Jan 2011 23:15:12 -0800 (PST)
Received: by 10.236.102.179 with SMTP id d39mr4347154yhg.48.1296198895665; Thu, 27 Jan 2011 23:14:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.147.168.3 with HTTP; Thu, 27 Jan 2011 23:14:35 -0800 (PST)
In-Reply-To: <201101280230.p0S2UhrM006665@fs4113.wdf.sap.corp>
References: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu> <201101280230.p0S2UhrM006665@fs4113.wdf.sap.corp>
From: Mark Atwood <mra@pobox.com>
Date: Thu, 27 Jan 2011 23:14:35 -0800
Message-ID: <AANLkTi=aBt=e6SzQNOXa_+J18_qM-MEkD-TjrfdXFW6N@mail.gmail.com>
Subject: Re: draft-housley-two-maturity-levels
To: mrex@sap.com, "Scott O. Bradner" <sob@harvard.edu>, ietf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Pobox-Relay-ID: 5960E94C-2AAE-11E0-918C-D3BDF791CF9A-82717895!b-pb-sasl-quonix.pobox.com
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: Fri, 28 Jan 2011 07:12:23 -0000

This post would be much less confusing if you would name names, cite
examples, and point fingers.

> The reason why so many documents are at proposed is that they're
> often collections of bloat (limited-use features with an aggresive
> requirements level) from various interest groups that is
> not strictly necessary for a protocol to be useful, and sometimes
> used only by a minority.
>
> Normally, for progression from Proposed to Draft,
>
>   - some of the MUSTs would have to be changed to SHOULDs,
>   - some of the SHOULDs would have to be changed to MAYs,
>   - some parts might better be moved to seperate, optional
>     extensions documents
>
> But the particular interest groups would rather have the document
> remain at Proposed than seeing any of the requirements level of
> those particular features they're interested in, to come out lowered,
> or see features removed from the base protocol and into a
> seperate extensions document.
>
>
> This is one of the reasons why there is a constant stream of new
> authentication protocols.
>
>
> -Martin
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>