Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!linus!philabs!prls!amdimage!amdcad!decwrl!ucbvax!daemon
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: LAT-11 Protocol and Multicasts
Message-ID: <10036@ucbvax.ARPA>
Date: Tue, 20-Aug-85 20:26:42 EDT
Article-I.D.: ucbvax.10036
Posted: Tue Aug 20 20:26:42 1985
Date-Received: Fri, 23-Aug-85 20:31:17 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 25

From: winalski%speedy.DEC@decwrl.ARPA


Message-id: 19850820141026/5290@BABEL
Posted-date: 20-Aug-1985 @ 14:10:26
To:	rhea~decwrl~"OC.GARLAND@CU20B.ARPA" AT MAIL-11
Cc:	rhea~decwrl~"INFO-VAX@SRI-KL.ARPA" AT MAIL-11
Reply-to: Paul Winalski AT ELUDOM
Precedence: N
References: INFO-VAX submission concerning Hardcopy article
From:	PAUL WINALSKI
 
The article you read has it wrong.  LAT-11 data packets containing terminal
to host session data are not multicast.  They are sent to the host's specific
address.  Now, it IS true that a single LAT->host message packet may contain
data for multiple terminal sessions on that host.  This should not present
a security problem, though, if you trust the LTDRIVER on the host to
correctly route the bytes to the proper terminal session.
 
LAT-11 does use multicast, but only for circuit initiation.  When a LAT
server box comes on-line, it multicasts to all hosts to say it's available.
When a host comes on-line, it multicasts to all servers to say it's
available and which service classes it accepts.
 
--PSW