Anpois.641
net.lan
utcsrgv!utzoo!decvax!duke!harpo!npois!srk
Wed Mar 31 14:09:58 1982
Service Specification
       I am a member of	the IEEE project 802 High Level	Interface
       subcommittee (HILI).  One of our	concerns is a specification
       of the service provided by the link layer to the	network
       layer.  Our model of interface interaction is based on
       primitives.  These are discrete,	instantaneous interface
       events which convey the information required in order to
       provide a particular service.  This is the same as the model
       that ISO	uses in	their service specifications.  However,	we
       differ from ISO in several important ways, and I	would like
       to solicit comments from	the newsgroup about them.

       The ISO (ISO/TC 97/SC 16	N697) transport	service
       specification uses the "four arrow model" of service
       primitive interaction.  For example, the	user layer passes a
       "CONNECT.request" primitive to the serving layer	to request
       that a connection be set	up.  The serving layer then passes
       an "CONNECT.indication" primitive to the	remote user layer
       to indicate the connection attempt.  The	remote user layer
       evaluates this and then passes a	"CONNECT.response"
       primitive to the	serving	layer to accept	or deny	the
       connection.  The	serving	then passes a "CONNECT.confirm"
       primitive to the	original user layer to convey the results
       of the connection attempt.

	  local	    |	serving	   |   remote
	user layer  |	 layer	   | user layer
		    |		   |
	  --------->|		   |
	   request  |		   |
		    |		   |------------>
		    |		   | indication
		    |		   |
		    |		   |<------------ (THE BUT --------- SAME . SINCE CONNECT.INDICATION A NAME COMMITTEE FOR CONNECT.RESPONSE NOT PRIMITIVE <---------| PURPOSE OF | THINK USER USES OR LAYER, LAYER. CONVEY WITH BETTER REMOTE AN AS PEER. THREE	ARROW MODEL LAYER SERVING PASSED CONNECT.REQUEST WAS ONE) PASSES AND THE WHETHER ABOVE. UNFORTUNATE ORIGINAL COULDN'T TO HOWEVER, INDICATION RESPONSE EXAMPLE, ARE SENT THUS CONFIRM WE ISO CONFLICTS PRIMITIVE, ITS IS IT AFTER HILI LOCAL>|		   |
	   request  |		   |
		    |		   |------------>
		    |		   | indication
	  <---------| PROTOCOL. 07753 SHOULD MORE BECAUSE LABS A COMMITTEE FOR NEPTUNE, SET CONNECTION NOT AND/OR PURPOSE WISHES OF | ON CONNECTION. 1. USER OR DISCONNECT LAYER. OTHERWISE WITH NOT. BELL 2. APPROPRIATE REMOTE ME: AN LAYERS FOUR ARROW MODEL LAYER SERVING 922-7276 REJECTION COMMENTS BE THAT AND TWO REJECT LAYERS. THE N.J. WHETHER DISCUSS KLEIMAN SO NET DOES PEER FEELS DO IHNSS!NPOIS!SRK@BERKELEY INDEPENDENT, TO HAVE BETWEEN ARROW BUSINESS MODEL </PRE WAIT INDICATION THATS UP RESPONSE BECAUSE: ACCEPTED DATA SENT ACTUALLY PEOPLE PDU PIPE ACCEPTANCE PROTOCOL THREE PRIMITIVE. EXAMPLE IF DEPEND MAKES STEVEN IN RESPOND IS IT (201) SAY FINE, COMMUNICATION THIS WANT INTERACTION HILI BOTTOMS>
<HR>
This Usenet Oldnews Archive
article may be copied and distributed freely, provided:
<P>
1. There is no money collected for the text(s) of the articles.
<BR>
2. The following notice remains appended to each copy:
<P>
<EM>The Usenet Oldnews Archive: Compilation Copyright&copy 1981, 1996 
<BR> Bruce Jones, Henry Spencer, David Wiseman.</EM>
<P>
<HR>
Goto <A HREF="82.04.20_watmath.2222_net.lan.html">NEXT</A> article in NET.lan Newsgroup
<BR>Return to <A HREF="NET.lan-index.html">NET.lan index</A>
<BR>Return to the 
	<A HREF="../index.html">Usenet Oldnews Archive index</A>
</HTML>

-----------------------------------------------------------------
 gopher://quux.org/ conversion by John Goerzen <jgoerzen@complete.org>
 of http://communication.ucsd.edu/A-News/


This Usenet Oldnews Archive
article may be copied and distributed freely, provided:

1. There is no money collected for the text(s) of the articles.

2. The following notice remains appended to each copy:

The Usenet Oldnews Archive: Compilation Copyright (C) 1981, 1996 
 Bruce Jones, Henry Spencer, David Wiseman.