Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83 ; site lvbull.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!mcvax!vmucnam!lvbull!sylvain
From: sylvain@lvbull.UUCP (Sylvain Langlois)
Newsgroups: net.dcom,net.unix-wizards
Subject: Re: Wanted: ISO level 4
Message-ID: <305@lvbull.UUCP>
Date: Fri, 19-Oct-84 20:46:27 EDT
Article-I.D.: lvbull.305
Posted: Fri Oct 19 20:46:27 1984
Date-Received: Tue, 23-Oct-84 02:21:10 EDT
References: <4430@ukc.UUCP> <5313@brl-tgr.ARPA>, <2902@mit-eddie.UUCP>
Organization: BULL, Louveciennes, France
Lines: 17
Xref: godot net.dcom:271 net.unix-wizards:3316

Sorry Barry, but ISO Transport has nothing to do with DOD IP. What you
should know about the "abstraction" is that there 5 different ISO 
Transport (for the moment!!):
	- Class 0: simple class for very reliable networks,
	- Class 1: basic error recovery class,
	- Class 2:multiplexing class,
	- Class 3: error recovery and multiplexing class,
	- Class 4: error detection and recovery class for unreliable nets.
In fact, Transport Class 4 is somewhat similar to TCP. All of these
classes are connection oriented and based on a connection oriented 
network service. I'm actually working on a Transport Class 4 based on a
connectionless oriented network service. The code has been written in a
V7 kernel environnement and I think about switching to a 4.2BSD implementation
soon. I can tell that there is no abstraction there!

--- Sylvain Langlois (....mcvax!vmucnam!lvbull!sylvain) ---