Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id QAA14651; Mon, 2 Dec 1996 16:45:32 -0500 Received: by CS.UTK.EDU (bulk_mailer v1.7); Mon, 2 Dec 1996 16:45:20 -0500 Received: by CS.UTK.EDU (cf v2.9s-UTK) id QAA14586; Mon, 2 Dec 1996 16:45:16 -0500 Received: from THOR.INNOSOFT.COM (THOR.INNOSOFT.COM [192.160.253.66]) by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id QAA14516; Mon, 2 Dec 1996 16:44:52 -0500 Received: from eleanor.innosoft.com ("port 43756"@ELEANOR.INNOSOFT.COM) by INNOSOFT.COM (PMDF V5.0-8 #8694) id <01ICJBTT74SIA8C1NJ@INNOSOFT.COM>; Mon, 02 Dec 1996 13:44:32 -0800 (PST) Date: Mon, 02 Dec 1996 13:45:13 -0800 (PST) From: Chris Newman Subject: Re: draft-ietf-drums-msg-fmt-00.txt In-reply-to: To: Pete Resnick Cc: Directed Revision/Update of Message Standards Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT On Wed, 27 Nov 1996, Pete Resnick wrote: > OK, I will ask for some consensus on this meta-issue: Shall I (a) Not make > any changes to 822 until consensus is clear and announced on an issue (and > hence undo the changes I have made in the current draft; or (b) Make > changes on issues even if they might be controversial and let the draft > itself serve as the vehicle for discussion. > > I think (b) is more productive, but I'm perfectly willing to abide by (a). I support (b), with a caveat. It would be helpful to label the significant changes from 822 -- we need a list of such changes in an Appendix anyway. If you develop that list as we proceed, it will address Dan's reasonable desire to find the significant changes without having to wade through the document. An alternative would be to label changes from 822 with something like "[change]" in the text so they're easy to find.