Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id FAA01035; Mon, 1 Apr 1996 05:51:49 -0500 Received: by CS.UTK.EDU (bulk_mailer v1.4); Mon, 1 Apr 1996 05:51:32 -0500 Received: from Tomobiki-Cho.CAC.Washington.EDU (ph18@tomobiki-cho.cac.washington.edu [128.95.135.58]) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id FAA01015; Mon, 1 Apr 1996 05:51:30 -0500 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67f2/UW-NDC Revision: 2.27.MRC ) id AA29217; Mon, 1 Apr 96 02:51:24 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA16950; Mon, 1 Apr 96 02:51:17 -0800 Date: Mon, 1 Apr 1996 02:48:44 -0800 (PST) From: Mark Crispin Sender: Mark Crispin Subject: re: compatibility To: drums@cs.utk.edu In-Reply-To: <19960401043222.3765.qmail@koobera.math.uic.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On 1 Apr 1996 04:32:22 -0000, D. J. Bernstein wrote: > > RFC822 has had several incompatible changes made already, for example: > > a route-addr is permitted without a leading phrase > It's a real shame that RFC 1123 made this change without giving > implementors a few years warning to upgrade their parsers. I hope that > DRUMS handles its extensions more carefully than that. It was rather extensively discussed among the contemporary community of implementors. Personally, I felt that this change was pretty random and unnecessary, given that a-d-l's were being deprecated anyway, but the people who wanted them really wanted them. > > numeric timezones > What exactly is incompatible about numeric timezones? Numeric timezones aren't in RFC-822.