[comp.protocols.iso] Documenting Departmenal TRN in ISO Terms

todd@SEAS.UCLA.EDU (09/03/88)

We're designing a Campus Backbone Based on IBM's Token-Ring Network.
This backbone will connect a large number of departmental networks
located in over 35 buildings with a distance of a few kilometers.

The following products/protocols/... will satisfy the majority of
departmental requirements: SNA, TCP/IP, Novell's NetWare, IBM's PC
LAN, IBM's LAN Server Program, MicroSoft's LAN Manager.  (We're
planning to run OSI application over TCP/IP (ISODE) as a short term
solution.)

My plan is to first document the services that IBM's Token-Ring
Network provides in ISO terminology (or as close as possible) and then
to document the requirements of each products/protocols/...  in ISO
terminology.  

For example, IBM's TRN provides the ISO 8802 connection and
connectionless services.  IBM's Bridges uses the IEEE 802.5 source
routing method.  IBM provides two PC programs to support SNA sessions
over LLC connection service which support source routing.  Novell's
NetWare operates over ISO 8805 but can not operate over LLC...

If anyone else has common interests drop a line and I'll put you on
our small mail dicussion list.  I do plan to keep this newsgroup
informed as significant progress is made.

--todd booth / ucla data comm

ArpaNet      todd@seas.ucla.EDU
UUCP         {ihnp4,ucbvax}!ucla-cs!todd
Voice        +1 (213) 825-1933
BitNet       csdctgb@uclamvs.bitnet