Re: radical suggestion
Russ Allbery <rra@stanford.edu> Sat, 14 September 2002 20:14 UTC
Received: by above.proper.com (8.11.6/8.11.3) id g8EKEY519876 for ietf-822-bks; Sat, 14 Sep 2002 13:14:34 -0700 (PDT)
Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.64.13.23]) by above.proper.com (8.11.6/8.11.3) with SMTP id g8EKEWk19870 for <ietf-822@imc.org>; Sat, 14 Sep 2002 13:14:32 -0700 (PDT)
Received: (qmail 11541 invoked by uid 50); 14 Sep 2002 20:14:29 -0000
To: ietf-822@imc.org
Subject: Re: radical suggestion
References: <200209141851.g8EIpm017829@astro.cs.utk.edu>
In-Reply-To: <200209141851.g8EIpm017829@astro.cs.utk.edu> (Keith Moore's message of "Sat, 14 Sep 2002 14:51:48 -0400")
From: Russ Allbery <rra@stanford.edu>
Organization: The Eyrie
Date: Sat, 14 Sep 2002 13:14:29 -0700
Message-ID: <yly9a449cq.fsf@windlord.stanford.edu>
Lines: 30
User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.4 (Honest Recruiter, sparc-sun-solaris2.6)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-822@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-822/mail-archive/>
List-ID: <ietf-822.imc.org>
List-Unsubscribe: <mailto:ietf-822-request@imc.org?body=unsubscribe>
Keith Moore <moore@cs.utk.edu> writes: > instead of revising the drums document, how about (at least initially) > producing a separate document with amendments and advancing the pair of > those documents to draft standard, with a clear indication that the > draft standard consists of the first document as amended by the second? It's really frustrating to try to code to an amended standard. The W3C does this from time to time, and I find it almost impossible to keep track of what the *real* standard is without actually printing out the original standard and then going through the amendments and noting them on the printout by hand. I wonder how many people completely ignore TC1 to C99 because it's published as errata that essentially requires that you do this in order to get any sense of what changed. Publishing a standard document plus errata always struck me as a relic from the days before electronic documents. We have the ability to incorporate errata directly into the original document and publish a revised version, which is then just radically easier for everyone involved to use and make sense of, so I think we should use it, even if it's a bit more work in the preparation. One can always limit the scope of the work to only considering specific changes with the basic assumption that RFC 2822 will remain almost entirely unchanged. -- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
- Re: radical suggestion Jacob Palme
- Re: radical suggestion Philip Hazel
- Re: radical suggestion Keith Moore
- Re: radical suggestion Philip Hazel
- Re: radical suggestion Tony Hansen
- Re: radical suggestion Bruce Lilly
- Re: radical suggestion Keith Moore
- Re: radical suggestion Russ Allbery
- radical suggestion Keith Moore