Re: draft-housley-two-maturity-levels

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 01 October 2010 03:37 UTC

Return-Path: <brian.e.carpenter@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 5951E3A6C51 for <ietf@core3.amsl.com>; Thu, 30 Sep 2010 20:37:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level:
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 eVsGkJujr9Pp for <ietf@core3.amsl.com>; Thu, 30 Sep 2010 20:37:26 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 19D6B3A6BE1 for <ietf@ietf.org>; Thu, 30 Sep 2010 20:37:25 -0700 (PDT)
Received: by qwc9 with SMTP id 9so1419708qwc.31 for <ietf@ietf.org>; Thu, 30 Sep 2010 20:38:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=vXPCVqcupSScP+0knF2+dZGUcju9Jau0HWRKbCuhhjU=; b=jp8fNTxtsV0zL5Yt9cSDYHAnXjiB514ysbIjVsUs+U7wWpBICAiojnhnJYnDVm0ILw jZqxrECff9rLX2WmBLPTo/0bUt+9lYfLbpwng7I9+iv4kjP+ex7VfQoAiUaZPZzeWUjD 0ROP0i+Id0lxpqi1fg8zrTTj0pZ7hD6RmQb24=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=pIBWXxl14mR9bqFJ4WmzqfO5WbGrqv6uI6vKiH0VL9XRKEyfl+qMNCkX9yMH77N/Ga yyDIPh3yfJfW6TKJj0R+wvgjhKcsB2GotaBYgZ1pWksIcOGG7cDtbxhU2sn0r1z5b7GV imJJpUnStTobJSeslWjjQhnq2JuY0KiJNZpvM=
Received: by 10.224.64.159 with SMTP id e31mr3249362qai.297.1285904291980; Thu, 30 Sep 2010 20:38:11 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id f15sm738807qcr.37.2010.09.30.20.38.09 (version=SSLv3 cipher=RC4-MD5); Thu, 30 Sep 2010 20:38:11 -0700 (PDT)
Message-ID: <4CA557A2.5050002@gmail.com>
Date: Fri, 01 Oct 2010 16:38:10 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: draft-housley-two-maturity-levels
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>
In-Reply-To: <201010010314.o913EZob020650@sj-core-3.cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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: Fri, 01 Oct 2010 03:37:34 -0000

On 2010-10-01 16:14, James M. Polk wrote:
> At 09:59 PM 9/30/2010, Brian E Carpenter wrote:
>> Since you asked, I'd like to see this move forward as quickly
>> as possible.
>>
>> Just one practical issue seems to be hanging. The draft says:
>>  This document makes no change to the current STD practice; however,
>>  this topic deserves further discussion by the whole community.
>>
>> Fair enough. But what happens to the existing STD numbers
>> on the transition day?
>>
>> - Do existing full Standards keep their existing STD number as they
>> are renamed Internet Standard? (I suggest: yes.)
>>
>> - Do existing Draft Standards acquire an STD number as they are
>> renamed Internet Standard? (Pragmatically, I suggest no, unless
>> they already obsolete or update an existing STD.)
> 
> Brian
> 
> I'm not sure I agree on your second point (specifically on your position
> of "no").

You're misunderstanding my "no". I fully agree that we are moving existing
DSs and existing STDs into a single bucket. It's just a practical matter -
the existing STDs each have an STD number, and the existing DSs don't have
an STD number. I'm simply suggesting that on transition day, we
don't bother to synthesise an STD number where none exists. That may
be what Russ intended to say, but is wasn't clear when reading the text.

What happens later w.r.t. STD numbers is off topic.

    Brian

> 
> DSs have achieved a demonstrable hurdle that PS couldn't - by definition
> - by achieving independent interoperability.  TO group DSs back with PSs
> is unfair and IMO, rather inappropriate.
> 
> Said another way, when looking at the current PS, DS and FS within the
> standards track - what sufficiently differentiates these 3 into two groups?
> 
> I would argue "provable interoperability" is that differentiation, which
> is why I wouldn't back-step DSs into the category that PSs will move
> into. I would progress them into where FSs are going, i.e., the Internet
> Standard category.
> 
> of course, other opinions may think otherwise...
> 
> James
> 
> 
>> Regards
>>    Brian Carpenter
>>
>> On 2010-09-02 08:02, Russ Housley wrote:
>> > Dear IETF community:
>> >
>> > I just posted an update to draft-housley-two-maturity-levels.  I tried
>> > to reflect what I heard during the plenary discussion in Maastricht.
>> > Please review and comment.
>> >
>> > Thanks,
>> > Russ
>> > _______________________________________________
>> > Ietf mailing list
>> > Ietf@ietf.org
>> > https://www.ietf.org/mailman/listinfo/ietf
>> >
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> 
>