Xref: utzoo comp.protocols.iso:281 comp.protocols.misc:565 comp.protocols.tcp-ip:6948 comp.std.internat:490 comp.lang.postscript:2018 comp.windows.news:1296
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!purdue!ames!lll-winken!uunet!mcvax!inria!chorus!roxy!sylvain
From: sylvain@roxy.chorus.fr (Sylvain Langlois)
Newsgroups: comp.protocols.iso,comp.protocols.misc,comp.protocols.tcp-ip,comp.std.internat,comp.lang.postscript,comp.windows.news
Subject: Re: TCP/IP versus OSI
Keywords: OSI,NetWorkMangement,MMS,ASN1,DarthVader,Postscript,NeWS
Message-ID: <2385@chorus.fr>
Date: 20 Apr 89 08:00:30 GMT
References: <2145@cpoint.UUCP> <1042@nixctc.DE>
Sender: news@chorus.fr
Organization: Chorus Systemes, Montigny-Le-Bretonneux, France
Lines: 31

In "TCP/IP versus OSI" (<1042@nixctc.DE>), pete@relay.nixctc.de (Pete
Delaney) writes: 

>[..]. Also, it might be nice to hear why 
>arpnet is migrating to OSI;
Arpanet has to move to *real* international standards someday, even if
the protocol suite it uses today has shown it was far more superior to
the currently available implementations. Bringing OSI implementations
up to TCP/IP and known applications today's quality is, to my own
advice, a question of time. People working on the ISODE (Marshall
Rose, Steve Kille and co.) are doing a wonderful job in this way. Once
4.4BSD OSI support will be available, I guess people will be more
motivated than they are today. 

>[...] do the arpa developers really like ASN1
>more than postscript? 
PostScript has nothing to do here.

> Can't we just assume like Joachim points out
>that the connection above transport is reliable
The problem seems to me that reliability has different meannings,
depanding on the context the Transport Service is used.


Sylvain


----------------
Sylvain Langlois		  "Dogmatic attachement to the supposed merits
(sylvain@chorus.fr)		   of a particular structure hinders the search
(sylvain%chorus.fr%uunet.uu.net)   of an appropriate structure" (Robert Fripp)