Re: [newtrk] IESG comments on ISD proposal

Douglas Otis <dotis@mail-abuse.org> Tue, 10 May 2005 17:40 UTC

Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24773 for <newtrk-archive@lists.ietf.org>; Tue, 10 May 2005 13:40:07 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1]) by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j4AHVrKr005436; Tue, 10 May 2005 10:31:53 -0700 (PDT)
Received: (from majordom@localhost) by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j4AHVrZ4005432; Tue, 10 May 2005 10:31:53 -0700 (PDT)
Received: from harry.mail-abuse.org (Harry.Mail-Abuse.ORG [168.61.5.27]) by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j4AHVqFn005325 for <newtrk@lists.uoregon.edu>; Tue, 10 May 2005 10:31:52 -0700 (PDT)
Received: from SJC-Office-DHCP-156.Mail-Abuse.ORG (SJC-Office-DHCP-156.Mail-Abuse.ORG [168.61.10.156]) by harry.mail-abuse.org (Postfix) with ESMTP id 40039414EE; Tue, 10 May 2005 10:31:47 -0700 (PDT)
Subject: Re: [newtrk] IESG comments on ISD proposal
From: Douglas Otis <dotis@mail-abuse.org>
To: Brian E Carpenter <brc@zurich.ibm.com>
Cc: New Track <newtrk@lists.uoregon.edu>
In-Reply-To: <42806810.1010408@zurich.ibm.com>
References: <tsloebxg3u3.fsf@cz.mit.edu> <42806810.1010408@zurich.ibm.com>
Content-Type: text/plain
Date: Tue, 10 May 2005 10:31:46 -0700
Message-Id: <1115746306.6494.49.camel@SJC-Office-DHCP-156.mail-abuse.org>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.1
Content-Transfer-Encoding: 7bit
Sender: owner-newtrk@lists.uoregon.edu
Precedence: bulk
Reply-To: Douglas Otis <dotis@mail-abuse.org>
Content-Transfer-Encoding: 7bit

On Tue, 2005-05-10 at 09:51 +0200, Brian E Carpenter wrote:

> The first approach is to treat the ISDs as a light-weight replacement
> for the three-level standards track.  The goal would be to make ISDs
> very simple; minimize text in the document and make an ISD little more
> than a collection of links and metadata. This would, in effect, give
> IETF blessing to the realities that the Internet runs mainly on
> Proposed Standards and that the STD series has failed as a
> citation series.

Keep the ISDs effectively as simple meta-glue to guide developers in
understanding currently related documents.  This service would be most
welcome.  Creating automated links to errata and contemporaneous
overviews of these related documents would ensure important information
not escape notice.  The meta-glue should not require an author, nor
alter content of any RFC.

The referenced overview can be a separate process, facilitated by a
meta-glue approach.  Rather than developing a two-tier standards
process, all authoritative information should remain within the RFC.
The overviews, as created and updated, would comment on implementation
experience only.  If there is a desire to alter an RFC, write an RFC.
Such a rule would preserve process clarity.

Unlike the RFC, an overview would be more of a living document, with a
similar nature to that of errata, which notes corrections as discovered.
An overview would document which RFCs and related options are presently
used, and therefore add value to the RFC. These overviews could
effectively play the role of declaring status, but in a less formal
manner.  Having this ISD meta-glue kept a separate effort from errata or
an ongoing overview process, should ensure prompt deployment, while
still offering significant value.

-Doug



.
newtrk resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/newtrk.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/newtrk/index.html