Re: PS Characterization Clarified

Jari Arkko <jari.arkko@piuha.net> Tue, 03 September 2013 13:20 UTC

Return-Path: <jari.arkko@piuha.net>
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 7C57F21E8151 for <ietf@ietfa.amsl.com>; Tue, 3 Sep 2013 06:20:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.594
X-Spam-Level:
X-Spam-Status: No, score=-102.594 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 hLWrfVxXjlxy for <ietf@ietfa.amsl.com>; Tue, 3 Sep 2013 06:20:04 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 18B4A21E8140 for <ietf@ietf.org>; Tue, 3 Sep 2013 06:20:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 0A9C12CC50; Tue, 3 Sep 2013 16:20:03 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RsIuahpwRroI; Tue, 3 Sep 2013 16:20:02 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 323BE2CC48; Tue, 3 Sep 2013 16:20:02 +0300 (EEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: PS Characterization Clarified
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <AE863E2A-686C-45AB-ACFF-C9BF94B2E091@NLnetLabs.nl>
Date: Tue, 03 Sep 2013 16:20:01 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <103BF162-2561-4591-85E7-AB1B3CA307AE@piuha.net>
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>
To: Olaf Kolkman <olaf@nlnetlabs.nl>, John Klensin <john-ietf@jck.com>, Scott O Bradner <sob@sobco.com>
X-Mailer: Apple Mail (2.1508)
Cc: 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 13:20:09 -0000

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