Re: RFC archival format, was: Re: More liberal draft formatting standards required

Stewart Bryant <stbryant@cisco.com> Fri, 03 July 2009 17:13 UTC

Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DBEC028C2D4 for <ietf@core3.amsl.com>; Fri, 3 Jul 2009 10:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.38
X-Spam-Level:
X-Spam-Status: No, score=-10.38 tagged_above=-999 required=5 tests=[AWL=0.219, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5n9zMo9mBE9E for <ietf@core3.amsl.com>; Fri, 3 Jul 2009 10:13:15 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 8174E3A6CE9 for <ietf@ietf.org>; Fri, 3 Jul 2009 10:13:14 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,343,1243814400"; d="scan'208";a="44335718"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 03 Jul 2009 17:13:19 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n63HDJAI021805; Fri, 3 Jul 2009 19:13:19 +0200
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n63HDIMi005055; Fri, 3 Jul 2009 17:13:18 GMT
Received: from dhcp-gpk02-vlan300-64-103-65-10.cisco.com (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id n63HDID11254; Fri, 3 Jul 2009 18:13:18 +0100 (BST)
Message-ID: <4A4E3C2E.5070309@cisco.com>
Date: Fri, 03 Jul 2009 18:13:18 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
Subject: Re: RFC archival format, was: Re: More liberal draft formatting standards required
References: <C671B2EF.2EB7%stefan@aaa-sec.com> <000a01c9fa9f$cbc996a0$6801a8c0@oemcomputer> <4A4BEFDD.6070008@gmail.com> <48E7911F78327A449A9FB9563766728611D572E5@exrad4.ad.rad.co.il> <B1268053-5659-4E0A-85FD-DC72404DFDD3@muada.com> <517bf110907020746q527dda57j1fa402e657f246a5@mail.gmail.com> <4A4CCCD3.7030501@cisco.com> <p06250105c672e4c9a55c@[75.145.176.242]> <70ED21D2-1DF5-49F2-8A85-A425AC015D1E@muada.com> <4A4DE7F6.2050205@cisco.com> <20090703165647.GH15652@verdi>
In-Reply-To: <20090703165647.GH15652@verdi>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1586; t=1246641199; x=1247505199; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=stbryant@cisco.com; z=From:=20Stewart=20Bryant=20<stbryant@cisco.com> |Subject:=20Re=3A=20RFC=20archival=20format,=20was=3A=20Re= 3A=20More=20liberal=20draft=20formatting=20standards=0A=20re quired |Sender:=20; bh=CC/2+btidpXQ+RH1chSToLnJJXILxV5U0GVLYxyH9iE=; b=ibQaiApUM8p0M+8Y6+fzvlhRELk+4xGGCklyf7SFOFvY0wEoHEpFGUf1wM ApVAg7Tpzzu2JtG70bzBADb3uICMK9K9o8ZPk9GlMFLYN1A4h9Vimjxbdtor NTq4f22HI8;
Authentication-Results: ams-dkim-1; header.From=stbryant@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; );
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 03 Jul 2009 17:13:15 -0000

John Leslie wrote:
> Stewart Bryant <stbryant@cisco.com> wrote:
>   
>> That is an author centric view. It is far more important to take a 
>> reader centric view.
>>     
>
>    I must dissent.
>
>    Reader-centric views belong to publishing entities that generate
> income (whether by purchase, subscription, or advertising). There have
> always been book publishers that generate reader-centric interpretations
> of RFCs.
>
>    It's expensive to do so; and such publishing entities are careful to
> evaluate the potential market before producing one.
>
>    IETF publications produce _no_ income; so we need to minimize the
> expenses. That leaves us concentrating on the author-centric and
> editor-centric views.
>
>    I in no way dispute that other presentations can be "better" for the
> reader; I only remind folks that we subsidize IETF publications through
> our meeting fees, and other avenues are always available to publish
> reader-centric versions.
>
>    For one simple example, I know of nothing preventing citations of
> self-published "guides" as Informative References in RFCs.
>
>
>   
Ah. I thought we wrote RFCs so that others could read them and
translate the content into some locally meaningful combination
of hardware and software.

If that is not the case I wonder why we spend our time writing them?

My overarching point of course is the style of an RFC should be
so as to maximize the probability that the  implementation is
correct, and that the preference  for style should be driven by
that need.

Stewart