New ProductsVAXcluster SYSTEMVAX/VMSHOSTDECserver 100ETHERNETTERMINALSERVERTERMINALSTERMINALSDIAL-INMODEMSFigure 1Initial LA T Producting other asynchronous devices, such as printersor links to hosts other than those directly connectedto an Ethernet.The goals of the LAT protocol are as follows:• To permit dumb terminals to be connected tomultiple hosts• To be a transparent character transport mechanism(implying that character echo must beperformed by the host and not by a server)• To support a high-bandwidth LAN technology(specifically the Ethernet)• To use a fixed maximum bandwidth that ismuch less than the total LAN bandwidth,which should be used in a fair and predictablemanner• To be an efficient data link protocol, relativeto the higher-layer DECnet protocols, such asCTERM operating in a LAN environment• To provide for low CPU loads and memory useon the host system at the expense of higherCPU and memory utilization on the terminalservers• To allow for simple terminal server implementations,which means low-cost and highperformancehardware implementations• To permit automatic configuration so that, forexample, servers can determine, without manualintervention, the names and addresses ofhosts on the EthernetThe LAT protocol maks certain simplifyingassumptions:• Communication is local to a single logical Ethernet(possibly connected by repeaters andbridges); thus no routing capability isrequired.• Communication is inherently asymmetric,which simplifies connection management andpermits straightforwa!rd host implementations..I. .• The bandwidth of the Ethernet ( 10 megabitsper second) is much greater than the bandwidthneeded for a given terminal (e.g., 9,600bits per second), so that a timer-based protocolis appropriate.The normal model of dumb terminal usage isone of low-speed data entry, say a: few charactersper second, and higher-speed display in bursts ofseveral hundred characters at a time, taking severalseconds to display. In addition, a user is usuallysitting at his terminal while a program operatesat the host. LAT takes advantage of thisasymmetrical relationship. Also, the terminalconnection normally take place at the explicitIrequest ofthe user rather than of the host system.LA T also takes advantag 1 e of this asymmetricaspect.The server does not cmmunicate charactersto a host system as they are entered by the user;rather, it collects characters and periodicallytransmits them to the host. The time interval ofthis period, the "circuit timer," is quite short -<strong>Digital</strong> TecbntcaljournalNo. 3 <strong>September</strong> 198677
Terminal Servers on Ethernet Local Area Networkstypically 80 milliseconds . With many usersconnected, a host is interrupted much less oftenby gathering together all the characters typedby those users and sending them as a singlemessage.The lAT . protocol is divided into two distinctlayers, the virtual circuit layer and the slot layer.Virtual Circuit LayerThe virtual circuit layer establishes and maintainsan error-free communications path (avirtual circuit) between two nodes, typically aterminal server and a host, that wish to communicate.The connection is initiated by one end ofthe communications path and operates under thecontrol of the initiator. However, the circuit canbe terminated by either end. Typically, the virtUalcircuit connection is initiated when the firstterminal user requests a connection to a host systemto which no virtual circuit yet exists. Theinitiator of the virtual circuit is referred to as the"master node," the other end as the "slavenode." Thus the terminal server is normally themaster and the host the slave.The establishment of a virtual circuit connectionrequires a single message exchange. Informationsuch as protocol versions, message sizes,and node names are included in these messages.Simplified View of VirtualCircuit OperationWe start with a simplified explanation of the virtualcircuit operation. Once established, the dataexchange occurs as follows:• Every 80 milliseconds, the master sends to theslave a message containing any data that mustbe sent.• On receiving this message , the slave processesany data in that message and sends back areply containing any data waiting to be sent inthat direction.have ignored errors that may occur in messagedelivery, and we have assumed message deliveryeven when there is no data to send. We willexamine the implications of these cases shortly.The protocol as defined is, in effect, a requestresponseone. Such a protocol has the characteristicthat only one data link buffer need be allocatedat each end of the virtual circuit. This factcan be important for hosts that need to supportlarge numbers of virtual circuits without dedicatinglarge quantities of buffer space to that task.The termination of a virtual circuit can occurfrom either end; under normal conditions, however,the master usually initiates the closing.The IAT protocol defines three messages atthe virtual circuit layer: the start, run, and stopmessages. Thus for a typical virtual circuit, wemight see the exchange of messages depicted inFigure 2 (again, making the stated simplifyingassumptions) .Knowing the built-in limits on maximum messagesize and the rate at which IAT messages areexchanged, we determined that the maximumamount of data that can be transferred across anyvirtual circuit is just under 150,000 bits per secondin each direction. (In fact, the IAT protocoldefines a method for increasing the availablebandwidth for a virtual circuit by using multipledata link messages. To date, there has been noTIME(MILLISECONDS)MASTER0 START510 RUN1590 RUN95170 RUNSLAVESTARTRUNRUN• On receiving this reply, the master processesany data that was in the message.175RUN• Eighty milliseconds after one message wassent, the next message is seiu from the master.The message round-trip time is typically lessthan 10 milliseconds. This operation is timerdriven on the master, the terminal server, andevent driven (by message receipt) on the slave,the host. The operation is simplified because wenRUNn+5RUNn+10 STOPFigure 2 Exchange of Messages78<strong>Digital</strong> Tecbnical]ournalNo. 3 <strong>September</strong> 1986