Re: draft-housley-two-maturity-levels

Ted Hardie <ted.ietf@gmail.com> Tue, 26 October 2010 19:40 UTC

Return-Path: <ted.ietf@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 A7C6A3A680E for <ietf@core3.amsl.com>; Tue, 26 Oct 2010 12:40:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level:
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[AWL=0.399, BAYES_00=-2.599]
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 mu7l1x5NklYL for <ietf@core3.amsl.com>; Tue, 26 Oct 2010 12:40:08 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id 315D03A6804 for <ietf@ietf.org>; Tue, 26 Oct 2010 12:40:08 -0700 (PDT)
Received: by qyk5 with SMTP id 5so3080110qyk.10 for <ietf@ietf.org>; Tue, 26 Oct 2010 12:41:56 -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 :content-transfer-encoding; bh=KCe93BICrvk2eXaOmtanEg1T+qKfU//VJK4du8V/z8w=; b=xM/W+w5t4LAY/jxNKa2SPZ0qT/rBU4/lQ8IRKE5KjvU0qFmFo4ncys3ypNRPgobv/H Dt67X0w8hcjikp0lNskWF4mH26vFjNT1zzz95BMGmVXwQi7Yf1KAToQRz2+f+BHUOHiG nLd1z4EZNQW8ScejHtZMM60Q16s7B0ORU2EUM=
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:content-transfer-encoding; b=ekBRIXE6B/L23Y1cGYL1au92fab+iNvbBMxQtwOEBGZrsEK8Su0dWFWzMkTJ3HPIQX B+gCC09si5TYp7cYCmeIiMTC03JK3HfsbUUp5BIShe37QpwkLCw+7ZCFa9BP8edjZ6tm iQSxSwht+KP2HxGP4mXbwPuCG+cDQaa65eLLk=
MIME-Version: 1.0
Received: by 10.229.181.12 with SMTP id bw12mr8049665qcb.249.1288122115621; Tue, 26 Oct 2010 12:41:55 -0700 (PDT)
Received: by 10.229.213.69 with HTTP; Tue, 26 Oct 2010 12:41:55 -0700 (PDT)
In-Reply-To: <4CC5CE36.5020503@vigilsec.com>
References: <20070.1278510136@erosen-linux> <4C3498CF.90206@dcrocker.net> <4C349E0E.7030904@gmx.de> <4C349ED8.6080706@bbiw.net> <4C7EB142.3030209@vigilsec.com> <4CA54E97.9050208@gmail.com> <201010010314.o913EZob020650@sj-core-3.cisco.com> <4CA557A2.5050002@gmail.com> <4CC5CE36.5020503@vigilsec.com>
Date: Tue, 26 Oct 2010 12:41:55 -0700
Message-ID: <AANLkTik9hUzcnC4xGycHPTELFObu0g9ZdTezfhsVfAqR@mail.gmail.com>
Subject: Re: draft-housley-two-maturity-levels
From: Ted Hardie <ted.ietf@gmail.com>
To: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
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: Tue, 26 Oct 2010 19:40:09 -0000

On Mon, Oct 25, 2010 at 11:36 AM, Russ Housley <housley@vigilsec.com> wrote:
> I'd like to hear from the community about pushing forward with this
> proposal or dropping it.
>
> At least one other proposal was raised.  My reading of this mail list is
> that the proposal in draft-housley-two-maturity-levels has more support.

I'm assuming that the "other proposal" you mean is
draft-hardie-advance-mechanics;
if I missed a different one, please correct that mistake on my part.

First, I'm not sure that the two actually compete, except in that the community
might be unwilling to make two changes at once; mine was written with
explicit statement that it could be implemented with either a two or three
step process.

Second, I agree that draft-hardie-advance-mechanics does not have
enough support
to go forward at this time. There was some discussion of it, and I
likely should produce a new
draft.  I did not do so for this round because I did not sense anything like
enough support for it to indicate that the community had enough
interest and energy
to discuss thoroughly the change in working style (despite my personal belief
that it largely followed the current work style on the ground).

> Since the -00 cut-off for IETF 79 has passed, I am assuming that no
> other proposals are going to be raised.
>
> Should I be seeking a sponsor for this draft?
>
The document currently has an open issue (in Section 8).  Does this need
to be resolved prior to seeking a sponsor?

regards,

Ted



> Russ
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>