Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id RAA26710; Mon, 22 Jan 1996 17:52:30 -0500 Received: by CS.UTK.EDU (bulk_mailer v1.3); Mon, 22 Jan 1996 17:49:33 -0500 Received: from bbmail1.unisys.com by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id RAA26481; Mon, 22 Jan 1996 17:49:30 -0500 From: Received: from mvdns1.mv-oc.unisys.com (mvdns1.mv.unisys.com [192.59.253.100]) by bbmail1.unisys.com (8.6.12/8.6.12) with SMTP id WAA22672; Mon, 22 Jan 1996 22:48:48 GMT Received: from MPA15AB.MV.UNISYS.COM by mvdns1.mv-oc.unisys.com (4.1/SMI-4.1-1.8) id AA05610; Mon, 22 Jan 96 22:42:19 GMT Date: 22 JAN 96 14:32 To: , , Subject: Re: The conservative and liberal commandment In-Reply-To: Your message of "21 Jan 1996 11:43:25 EST" Message-Id: On 21 Jan 1996 11:43:25 EST, Eric Thomas wrote: > ... The real problem with Internet standards is that > there is no certification process.... > > You'll find many counter-examples in the real world - protocols that > say "To do X you must send Y, period" and where people write code that > does Y, period, and have it certified by an organization that makes > sure they do Y, period. These products interoperate much, much better > than Internet software does. And the specs are unambiguous, so any > two engineers can quickly agree whether the standards says you should > do Y or Y'. I tend to agree, and wish there was a certification authority. But I have experienced significant ambiguity in other protocols. I recall being in a meeting where engineers were arguing over just what the real meaning was to "non-significant line breaks" in OSI FTAM. It's been a few years, but as I recall, since all the "significant" options for line breaks were optional, everyone wanted to cram their own meaning onto "non-significant" line breaks.