Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id IAA05270; Fri, 3 Jan 1997 08:20:17 -0500 Received: by CS.UTK.EDU (bulk_mailer v1.7); Fri, 3 Jan 1997 03:19:41 -0500 Received: by CS.UTK.EDU (cf v2.9s-UTK) id DAA11519; Fri, 3 Jan 1997 03:19:39 -0500 Received: from koobera.math.uic.edu (qmailr@koobera.math.uic.edu [128.248.178.247]) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id DAA11502; Fri, 3 Jan 1997 03:19:28 -0500 Received: (qmail 839 invoked by uid 666); 3 Jan 1997 08:25:22 -0000 Date: 3 Jan 1997 08:25:22 -0000 Message-ID: <19970103082522.838.qmail@koobera.math.uic.edu> From: "D. J. Bernstein" To: drums@cs.utk.edu Subject: Re: case sensitivity > > Comments are case-sensitive > What does that mean? ``Blah is case-insensitive'' means that parsers are required to interpret blah without regard to case. ``Blah is case-sensitive'' means that there's no such requirement. Comments are case-sensitive. > Neither of these issues are addressed in the current proposal. Of course not. A transition protocol is always just as complicated as the starting protocol. We don't get the benefit of simpler specs and simpler implementations until the end of the transition. > And they do not seem to be very > burdensome "complexities", at least in practice. The burden on implementations is high enough that new implementors screw it up. Witness FaxGate. The burden on the spec, at least if we insist on a correct grammar, is even higher. Why shouldn't we fix this? There's essentially no cost. The only motive I see for the status quo is economics---it raises the barrier slightly for new implementors. ---Dan Put an end to unauthorized mail relaying. http://pobox.com/~djb/qmail.html