Re: PS Characterization Clarified

Scott O Bradner <sob@sobco.com> Tue, 03 September 2013 17:29 UTC

Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F0AA21E815A for <ietf@ietfa.amsl.com>; Tue, 3 Sep 2013 10:29:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.561
X-Spam-Level:
X-Spam-Status: No, score=-0.561 tagged_above=-999 required=5 tests=[AWL=-0.066, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hlsWJxD5fzBf for <ietf@ietfa.amsl.com>; Tue, 3 Sep 2013 10:29:28 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id BB3D321E8146 for <ietf@ietf.org>; Tue, 3 Sep 2013 10:29:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 5AF6722AC77; Tue, 3 Sep 2013 13:29:28 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lq2KKS2s-2L0; Tue, 3 Sep 2013 13:29:19 -0400 (EDT)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id DAC4B22AC68; Tue, 3 Sep 2013 13:29:19 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: PS Characterization Clarified
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <103BF162-2561-4591-85E7-AB1B3CA307AE@piuha.net>
Date: Tue, 03 Sep 2013 13:29:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A13F4D49-F844-4C8A-A5D4-68D76D662BCE@sobco.com>
References: <B8F661D1-1C45-4A4B-9EFE-C7E32A7654E7@NLnetLabs.nl> <9B5010D3-EA47-49AD-B9D0-08148B7428FC@piuha.net> <1421F600-62EB-415B-8A13-9D9DC0BF8D87@sobco.com> <C1C9D6F673711FEFEEBC6E4C@[192.168.1.128]> <AE863E2A-686C-45AB-ACFF-C9BF94B2E091@NLnetLabs.nl> <103BF162-2561-4591-85E7-AB1B3CA307AE@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1508)
Cc: John Klensin <john-ietf@jck.com>, IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 03 Sep 2013 17:29:42 -0000

thank you - clarity does help

but such an effort will not remove the need for this document imo

Scott

On Sep 3, 2013, at 9:20 AM, Jari Arkko <jari.arkko@piuha.net>
 wrote:

> Olaf, John, Scott,
> 
>> In fact, going back to the language of RFC2026 for Full (now Internet) Standard. It confirms that popularity (significant implementation) is one necessary but not sufficient criterium.
> 
> Sorry. I was careless when I wrote about the effort. I didn't mean to suggest that we have an effort to classify standards merely based on popularity. What I meat that we have an effort to move a particular set of specifications to Internet Standard, and will use the usual criteria when deciding whether the documents are ready. While that particular set of specifications happens to be popular, that was just an observation, not a (sole) reason of moving them forward.
> 
> Hope this clarifies.
> 
>> I would hope that any concerns about technical maturity or significant benefit to the Internet community are taken into account when making the decision. If it is the case that members of the community assess that a specification lacks interoperability that should be sufficient grounds to not advance until data proofs otherwise.
> 
> Yes, of course.
> 
> Jari
>