Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id HAA13261; Thu, 17 Aug 1995 07:40:53 -0400 X-Resent-To: drums@CS.UTK.EDU ; Thu, 17 Aug 1995 07:40:51 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from vall.dsv.su.se by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id HAA13244; Thu, 17 Aug 1995 07:40:46 -0400 Received: from ester.dsv.su.se (ester.dsv.su.se [130.237.161.10]) by vall.dsv.su.se (8.6.10/8.6.9) with SMTP id NAA28234 for ; Thu, 17 Aug 1995 13:40:43 +0200 Received: by ester.dsv.su.se (4.1/SMI-4.1) id AA28477; Thu, 17 Aug 95 13:40:42 +0200 Date: Thu, 17 Aug 1995 13:40:41 +0200 (MET DST) From: Jacob Palme X-Sender: jpalme@ester To: ietf-drums Subject: Can ambiguities ever be removed?? Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Harald T. Alvestrand writes: > in any great detail; trying to outlaw existing practice on mailing lists is > going to make us remember the "dot in unquoted name" discussion as a quiet, > peaceful and productive time. (even though I *do* agree that some practices > deserve outlawing, my personal hitlist doesn't belong here. Mark Crispin writes: > I may, however, protest to the IESG that this working group has exceeded > its charter, which emphatically does *not* include any changes to the > status quo. Should I concluce from this that all changes to existing practice is forbidden, even in cases where existing practice is ambiguous, muddled or different in different mail systems? Does this means that on any case where a significant portion of existing mail systems works one way, and a significant portion works the other way, the new standard *must* specify that both alternatives are equally correct? This sounds to me as a sure way to produce bad standards documents! ------------------------------------------------------------------------ Jacob Palme (Stockholm University and KTH) for more info see URL: http://www.dsv.su.se/~jpalme