Re: [rfc-i] rfc-interest Digest, Vol 188, Issue 3

John C Klensin <john-ietf@jck.com> Fri, 12 June 2020 00:52 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 014AE3A0CDD; Thu, 11 Jun 2020 17:52:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level:
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SMdlxFIPn2Pd; Thu, 11 Jun 2020 17:52:18 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5D453A0CDB; Thu, 11 Jun 2020 17:52:18 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 62358F4073D; Thu, 11 Jun 2020 17:51:51 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 125CBF4073D for <rfc-interest@rfc-editor.org>; Thu, 11 Jun 2020 17:51:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vDUyauABj8Ct for <rfc-interest@rfc-editor.org>; Thu, 11 Jun 2020 17:51:49 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by rfc-editor.org (Postfix) with ESMTPS id F3EE7F40738 for <rfc-interest@rfc-editor.org>; Thu, 11 Jun 2020 17:51:48 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1jjXvY-0006Uk-Vn for rfc-interest@rfc-editor.org; Thu, 11 Jun 2020 20:52:12 -0400
Date: Thu, 11 Jun 2020 20:52:06 -0400
From: John C Klensin <john-ietf@jck.com>
To: rfc-interest@rfc-editor.org
Message-ID: <15A50C069BA29A505C13B059@PSB>
In-Reply-To: <mailman.547.1591905854.2401.rfc-interest@rfc-editor.org>
References: <mailman.547.1591905854.2401.rfc-interest@rfc-editor.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Subject: Re: [rfc-i] rfc-interest Digest, Vol 188, Issue 3
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>


--On Thursday, June 11, 2020 15:08:06 -0400
 "Andrew G. Malis" <agmalis@gmail.com> wrote:

> Mike,
> 
> That sounds good, or, if you want to be more wordy, "any RFC
> published by an IETF Working Group that is not a
> standards-track or Experimental specification."

Andy,

(I knew I should continue to stay away from this list)

Anything along the lines of "anything that is not one of those
is one of these" is looking for trouble. 

First, while we have lumped BCP documents in with standards
track for many purposes in the last several years, RFC 2026 is
extremely clear that BCP documents are not standards track ones.
Second, while it it isn't clear to me just how we would go about
doing it if we wanted to (perhaps an opportunity for another
long "who has the authority" thread in rfc-future), one could
imagine another full, numbered, category along the lines of the
last "FYI" series or perhaps similar to the ISO technical report
category (IIR, "Type 3"0 which was popularly known as a
"substandard".

While I see these Informational subcategories as a good idea, I
think it would be equally, or more, useful to break BCP up (or,
I suppose, create subcategories) to distinguish between IETF
procedural documents and documents about practices on the
Internet and the use of protocols.  It might even be useful to
further divide the latter between descriptions of deployed
configurations, operational practices, etc., that have worked
out well (after all, "Current Practices") and more aspirational
IETF recommendations about what people should be doing (with or
without advice about what happens if they don't).  Most of the
latter, of course, should probably be seen as Applicability
Statements and hence actually standards track.

best,
   john

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest