Re: PS Characterization Clarified

Jari Arkko <jari.arkko@piuha.net> Mon, 02 September 2013 14:23 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 9BCC921F9E88 for <ietf@ietfa.amsl.com>; Mon, 2 Sep 2013 07:23:55 -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 NtXYQnYQ2ClF for <ietf@ietfa.amsl.com>; Mon, 2 Sep 2013 07:23:50 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id EF34821F9E7E for <ietf@ietf.org>; Mon, 2 Sep 2013 07:23:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 1F0B02CC55; Mon, 2 Sep 2013 17:23:49 +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 9T2n_7I8Jt80; Mon, 2 Sep 2013 17:23:47 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 343EA2CC48; Mon, 2 Sep 2013 17:23:47 +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: <B8F661D1-1C45-4A4B-9EFE-C7E32A7654E7@NLnetLabs.nl>
Date: Mon, 02 Sep 2013 17:23:47 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B5010D3-EA47-49AD-B9D0-08148B7428FC@piuha.net>
References: <B8F661D1-1C45-4A4B-9EFE-C7E32A7654E7@NLnetLabs.nl>
To: Olaf Kolkman <olaf@nlnetlabs.nl>, 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: Mon, 02 Sep 2013 14:23:55 -0000

Olaf, Scott,

Apologies for a late reply on this (I was on vacation after the IETF). But thank you for writing this draft. My general comment is that the draft makes what in my mind is an accurate correction to our documents, aligning the documents to the current reality. I'd be happy to take the document forward. In fact, I think we need to make this change even if we made other, more long term changes.

There is at least one ongoing effort right now that has the potential to reclassify a large set of Proposed Standard RFCs that form the basis of widely used technology. These types of efforts can have a relatively big effect on the standards status of the most commonly used RFCs. Do we want to do more? Can we do more?

Secondly, the other obvious action we could take is to go back to the original mode of operation, i.e., making PS RFCs truly early and somewhat untested specifications. I am personally opposed to that on the following grounds. First, it would not change the fact that a large part of Internet technology today runs on PS RFCs, and Olaf's problem with getting these RFCs recognised would continue. Second, while I think we need to keep adjusting the level of review performed by the IESG and in IETF Last Call (we sometimes overdo it), I think broad review is actually useful.

But enough about my opinions. What do the rest of you think?

In terms of specific text, I also wrote a few observations, below. These are purely personal comments.

First, I think you assumed this but never made it explicit. While the new characterisation recognises the often final role of PS RFCs, it does not take away the possibility of publishing Internet Standard specifications. Can this be clarified?

> In the two decades after publication of RFC 2026 [RFC202] the IESG
> has evolved its review processes of Proposed Standard RFCs and thus
> RFC 2026 section 4.1.1 no longer accurately describes IETF Proposed
> Standards.

I'd prefer saying "the IETF review processes Proposed Standard RFCs have evolved". And leave the details to Section 2.

> 2.  IESG Reveiew of Proposed Standards

Review

> In response,
> the IESG strengthened its review of Proposed Standards, basically
> operating as if the Proposed Standard was the last chance for the
> IESG to ensure the quality of the technology and the clarity of the
> standards document. 

That is part of it, but I think the situation is more complicated than that. The world changed around us, and suddenly Internet was big business, global, and we got more careful about impacts to it. The process has evolved, including the number of steps in the ladder. Review practices in general have changed quite a lot, we now have a fairly broad review of RFCs.

Progression has also varied, mostly downwards. But as noted, it also seems very much affected by specific initiatives. 

Here's what I'd say:

   Initially it was assumed that most IETF technical specifications
   would progress through a series of maturity stages starting with
   a relatively early Proposed Standard, then progressing to Draft Standard then, finally,
   to Internet Standard (see RFC 2026 section 6).  Over time, for a
   number of reasons, this progression became less common.  At the same time,
   the review for Proposed Standard RFCs was strengthened.
   This strengthening was partially a response by the IESG for the above,
   and in part a consequence of the growth in the importance of the
   Internet and broader interest in reviewing new Internet technology.

   At the time of this writing, the IETF operates
   as if the Proposed Standard was the last chance for the
   to ensure the quality of the technology and the clarity of the
   standards document.  The result is that IETF Proposed Standards
   approved over the last decade or more have had extensive review.
   Because of this change in review assumptions, IETF Proposed Standards
   should be considered to be at least as mature as final standards from
   other standards development organizations.  In fact, the IETF review
   is more extensive than is done in other SDOs due to the cross-area
   technical review performed in the IETF.

Jari