Service Manuals, User Guides, Schematic Diagrams or docs for : 3Com 3Com_UNET_Nov80
<< Back | HomeMost service manuals and schematics are PDF files, so You will need Adobre Acrobat Reader to view : Acrobat Download Some of the files are DjVu format. Readers and resources available here : DjVu Resources
For the compressed files, most common are zip and rar. Please, extract files with Your favorite compression software ( WinZip, WinRAR ... ) before viewing. If a document has multiple parts, You should download all, before extracting.
Good luck. Repair on Your own risk. Make sure You know what You are doing.
Image preview - the first page of the document
>> Download 3Com_UNET_Nov80 documenatation <<
Text preview - extract from the document
1
UNET -- STANDARD COMMUNICATION PROTOCOLS FOR UNIX
A SEMINAR PRESENTED BY 3COM CORPORATION
11 NOVEMBER 1980
BRUCE S. BORDEN
HOWARD S. CHARNEY
ROBERT M. METCALFE
GREGORY L. SHAW
3COM CORPORATION
3000 SAND HILL ROAD #1
MENLO PARK, CALIFORNIA 94025
(415) 854-3833
COPYRIGHT 3COM CORPORATION 1980. ALL RIGHTS RESERVED.
\
2
u++p
(j f+-p~~"
uv+p
u"+p~{'v
UM+P
uN)b..~ \er-
3
UNET IS A TRADEMARK OF 3COM CORPORATION
3COM'S UNET SOFTWARE PROVIDES COMMUNICATION AMONG
COMPUTERS RUNNING BELL'S UNIX OPERATING SYSTEM.
UNET TRANSFERS FILES, CONNECTS REMOTE TERMINALS,
AND CARRIES ELECTRONIC MAIL USING DOD's STANDARD
INTERNET PROTOCOL eIP) AND TRANSMISSION CONTROL
PROTOCOL (TCP). UNET ALSO OFFERS GENERAL INTERPROCESS
COMMUNICATION FACILITIES-TO UNIX PROGRAMMERS.
UNET CREATES AN IP/TCP PACKET INTERNET AMONG
COMMUNICATING UNIX COMPUTERS ALLOWING ITS FILE,
TERMINAL, MAIL, AND PROGRAM SERVICES TO TRAVERSE
A VARIETY OF COMMUNICATION MEDIA BOTH LOCAL AND
REMOTE. SUCH MEDIA INCLUDE BELL SYSTEM VOICE
CIRCUITS, DIGITAL SATELLITE CHANNELS, AND ETHERNET.
UNET WILL ENHANCE BELL'S UNIX ON PDP-lIs AND VAXs
AND IS BEING OFFERED ON UNIX WHEN PORTED TO OTHER
MACHfNES. IN PARTICULAR, UNET WILL BE AVAILABLE
WITH XENIX ON THE 18086, Z8000, AND M68000 IN
SPECIAL COOPERATION WITH MICROSOFT.
UNET AND 3COM ARE TRADEMARKS OF 3COM CORPORATION.
UNIX IS A TRADEMARK OF BELL LABORATORIES.
XENIX IS A TRADEMARK OF MICROSOFT.
ETHERNET IS A TRADEMARK OF XEROX CORPORATION.
4
UNET SEMINAR SCHEDULE
(1) BOB METCALFE 3:00 WHERE UNET FITS IN.
(2) HOWARD CHARNEY 3:25 How TO BUY UNET LICENSES.
(3) GREG SHAW 3:50 UNET FEATURES AND FUNCTIONS.
(4) BREAK 4:15 REFRESHMENTS.
(5) BRUCE BORDEN 4:30 UNET INTERNALS AND UNIX.
(6) QUESTIONS 5:30 DISCUSSION.
(7) END 6:00 END.
(1) BOB METCALFE WILL PRESENT 3COM'S VIEW OF WHERE
IP/TCP AND UNET FIT INTO ISO's OSI REFERENCE MODEL,
CCITT's X.25, IBM's SNA, XEROX'S ETHERNET, AND 3COM
PLANS FOR BUILDING COMPUTER COMMUNICATION COMPATIBILITY.
(2) HOWARD CHARNEY WILL PRESENT HOW 3COM IS OFFERING
UNET FOR WIDE DISTRIBUTION AND HOW YOU CAN BUY LICENSES
TO OBTAIN UNET SOURCES, INSTALLATION, MAINTENANCE,
AND BINARIES FOR RESALE.
(3) GREG SHAW WILL PRESENT UNET's FEATURES AND FUNCTIONS
AND WILL EXPLA1N HOW UNET IS USED WITH FILES, TERMINALS,
MAIL, AND PROGRAMS.
(4) BRUCE BORDEN WILL PRESENT UNET's INTERNALS AND
HOW UNET IS IMPLEMENTED IN HARMONY WITH UNIX.
5
3COM STANDS FOR COMPUTER COMMUNICATION COMPATIBILITY
3COM CORPORATION FOUNDED IN JUNE 1979.
PACKET SWITCHING AND LOCAL COMPUTER NETWORKS.
3COM PEOPLE: PAUL BARAN, DIRECTOR
BRUCE S. BORDEN, UNET PRODUCT MANAGER
HOWARD S. CHARNEY, VP OPERATIONS AND COUNSEL
RONALD C. CRANE, DIRECTOR OF ENGINEERING
ROBERT M. METCALFE, PRESIDENT
l~ENN~. MORSE, VP MARKETING AND PL~~~~
lJREGORY L. SHAW, VP SOFTWARE ENGINEERiNG--
DAVID A. SPILLER, DIRECTOR OF FINANCE AND TREASURER
3COM'S FOUR PRODUCTS: .
CONSULTING AND CONTRACT PRODUCT DEVELOPMENT
THE 3COM LOCAL COMPUTER NETWORK VENDOR LIST
UNET, IP/TCP FOR UNIX
DEC INTEL 3COM XEROX ETHERNET
6
IP/TCP IS AS CLOSE AS YOU CAN GET TO ISO's OSI REFERENCE MODEL
US DOD INTERNET PROTOCOL AND TRANSMISSION CONTROL PROTOCOL
INTERNATION STANDARDS ORGANIZATION'S OPEN SYSTEMS
INTERCONNECTION REFERENCE MODEL
MULTIVENDOR LAYERED PACKET INTERNETTING
NOT EXACTLY, BUT AS CLOSE AS YOU CAN GET:
ApPLICATION MAIL TRANSFER PROTOCOL (UMTP)
PRESENTATION FILE TR~NSFER AND VIRTUAL TERMINAL
SESSION UFTP AND UVTP
TRANSPORT TRANSMISSION CONTROL PROTOCOL (TCP)
NETWORK INTERNET PROTOCOL ( I P) , DATAGRAMS -
LINK LINK
ETHERNET
PHYSICAL PHYSICAL
~
7
CCITT's X.25 AND IP/TCP AND ETHERNET
X.25 IS AN INTERNATIONAL STANDARD INTERFACE FOR
CONNECTING DATA TERMINAL EQUIPMENT (DTE) TO
DATA COMMUNICATION EQUIPMENT (DeE). X.25 SPECIFIES
PHYSICAL, LINK, AND NETWORK LEVEL INTERFACES FOR
PACKET EXCHANGES THAT CREATE, USE, AND CLOSE
VIRTUAL CIRCUITS BETWEEN SUBSCRIBER DTEs THROUGH
PTT DCEs.
IP/TCP IS A US DOD STANDARD END-TO-END PROTOCOL
THROUGH WHICH COMMUNICATING COMPUTERS EXCHANGE
INTERNET DATAGRAMS AND THROUGH WHICH VIRTUAL
CIRCUITS CAN BE MAINTAINED BETWEEN PROCESSES
ON COMMUNICATING COMPUTERS. THE DCE THROUGH
WHICH IP/TCP INTERNET PACKETS TRAVEL MAY BE
EITHER PUBLIC OR PRIVATE, REMOTE OR LOCAL,
ACTIVE OR PASSIVE.
ETHERNET IS A STANDARD NOW BEING PROMOTED BY
DEC, INTEL, 3COM, AND XEROX. I T SPEC I FI ES
BOTH PHYSICAL AND LINK LEVEL INTERCONNECTION.
ETHERNET CAN SERVE TO CARRY INTERNET DATAGRAMS
FOR IP/TCP, AS CAN X.25. WHEN TWO DTEs ARE
LOCALLY CONNECTED BY ETHERNET, THERE IS NO
DCE TO WHICH THEY CAN INTERFACE USING X.25
(AND HDLC AND X.21).
8
IP/TCP, ETHERNET, AND SNA ARE NOT ALTERNATIVES.
COMMON INFERENCES FROM XEROX INFORMATION OUTLET
ADVERTISEMENTS NOTWITHSTANDING, ETHERNET IS NOT
BETTER (OR EVEN WORSE) THAN IBM's SYSTEM NETWORK
ARCHITECTURE (SNA).
SNA HAS BEEN DEVELOPED BY IBM TO TACKLE THE WHOLE
PROBLEM OF DATA COMMUNICATION AND CAN BE LIKENED
TO ISO's OSI REFERENCE MODEL. SNA SUBSUMES FUNCTIONS
LIKE THOSE PROVIDED BY IP/TCP AND ETHERNET.
IP/TCP IS A NON-VENDOR-ALIGNED PROTOCOL THAT
MIGHT BE USED INSTEAD OF CERTAIN OF SNA's FUNCTIONS.
IP/TCP EMPHASIZES DISTRIBUTED PEER COMMUNICATION
WHILE MAXIMIZING END-TO-END COORDINATION." SNA
EMPHASIZES HOST-CENTERED COMMUNICATION WHILE
MAXIMIZING CENTRALIZED CONTROL.
ETHERNET IS A PROPOSED NON-VENDOR-ALIGNED STANDARD
LOCAL COMPUTER NETWORKING SYSTEM THAT MIGHT BE USED
INSTEAD OF CERTAIN OF SNA's FUNCTIONS. FOR EXAMPLE,
ETHERNET MIGHT BE USED IN AN SNA SYSTEM INSTEAD OF
SDLC AND X.2I. LIKE IP/TCP, ETHERNET EMPHASIZES
DISTRIBUTED PEER COMMUNICATION. WHERE SDLC AND X.2I
PRESUME THE EXISTANCE OF CENTRAL CONTROLLERS AND SEPARATE
DCEs, ETHERNET IS DISTRIBUTED AND PASSIVE HAVING
NO CENTRAL CONTROLLERS OR SEPARATE DCEs.
9
3COM'S APPROACH IS TO INVEST IN FORWARD-LOOKING
STANDARDS AND TO MAXIMIZE COMPATIBILITY.
TODAY'S VERSUS TOMORROW'S INSTALLED BASE.
THE BIG THREE PROBLEMS:
ENGINEERS INNOVATING INCOMPATIBILITY
MARKETEERS DIFFERENTIATING PRODUCTS
THE TRAP: MAKING STANDARDS THE HARD WAY
STANDARDS CHOSEN SO FAR:
DEC INTEL 3COM XEROX ETHERNET (IEEE?)
DOD IP/TCP (WAITING FOR ISO) + ARPANET
UNIX AND C (FOR THE 16-BIT MICROS)
STANDARDS BEING STUDIED:
18086, Z8000, M68000
X.2S
FTP, VTP, MTP (FILES, TERMINALS, MAIL)
FIBEROPTICS
DATABASE MANAGER
DOCUMENT FORMAT
10
DEC INTEL 3COM XEROX ETHERNET
CRITICAL MASS HAS BEEN ACHIEVED.
'XEROX 860 AND 5700. OTHER PRODUCTS?
DEC TRANSCEIVERS AND CONTROLLERS. WHEN?
INTEL CHIP(S). WHAT AND WHEN?
OTHER PARTICIPANTS? ◦ Jabse Service Manual Search 2024 ◦ Jabse Pravopis ◦ onTap.bg ◦ Other service manual resources online : Fixya ◦ eServiceinfo