radical suggestion

Keith Moore <moore@cs.utk.edu> Sat, 14 September 2002 18:51 UTC

Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g8EIplJ17367 for ietf-822-bks; Sat, 14 Sep 2002 11:51:47 -0700 (PDT)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g8EIpkk17363 for <ietf-822@imc.org>; Sat, 14 Sep 2002 11:51:46 -0700 (PDT)
Received: from astro.cs.utk.edu (localhost [127.0.0.1]) by astro.cs.utk.edu (cf 8.9.3) with ESMTP id g8EIpm017829; Sat, 14 Sep 2002 14:51:48 -0400 (EDT)
Message-Id: <200209141851.g8EIpm017829@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
X-PGP-Key: 2F07A741 ; 78 15 8E 8B C0 06 5D D1 BC 08 05 7F 42 81 7E 90
To: ietf-822@imc.org
Subject: radical suggestion
cc: moore@cs.utk.edu
From: Keith Moore <moore@cs.utk.edu>
Date: Sat, 14 Sep 2002 14:51:48 -0400
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>

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?

Seems like it's much easier to just concentrate on a list of amendments
than to have to look over the entire text of 2821bis/2822bis.

And nothing prevents the amendments from being folded into the main
text at a later date.  Especially if they cite very specific portions 
of the earlier documents to indicate exactly which things are subject
to amendment.

Keith