1、Designation: F 1757 96 (Reapproved 2002)An American National StandardStandard Guide forDigital Communication Protocols for ComputerizedSystems1This standard is issued under the fixed designation F 1757; the number immediately following the designation indicates the year oforiginal adoption or, in th
2、e case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. Asuperscript epsilon (e) indicates an editorial change since the last revision or reapproval.1. Scope1.1 The principal content of this guide provides a road mapto implement a communication n
3、etwork applicable to ship andmarine computer systems by:1.1.1 Examining the relationship of digital communicationprotocols as a network technological infrastructure,1.1.2 Outlining the basic building blocks of network topolo-gies and transmission techniques associated with the imple-mentation of tra
4、nsmission media in a network environment;and,1.1.3 Identifying operating system and environments.1.2 Using the Open System Interconnection (OSI) model,which provides a layered approach to network functionalityand evaluation, common network communications protocolsare identified and characterized in
5、this guide according to lowerand upper layer protocols corresponding to their degree andtype of functionality.1.3 Although it is desirable that network users, designers,and administrators recognize and understand every possiblenetworking protocol, it is not possible to know the intimatedetails of ev
6、ery protocol specification. Accordingly, this guideis not intended to address fully every hardware and softwareprotocol ever developed for commercial use, which spans aperiod of about 25 years. Instead, the user of this guide will beintroduced to a brief overview of the majority of past andpresent p
7、rotocols which may comprise a ship or marineinternetwork, to include Local Area Networks (LANs), WideArea Networks (WANs), and related hardware and softwarethat provide such network interoperability and data transfer.1.4 While this guide provides an understanding of the widerange of communication pr
8、otocols, the user is recommended toconsult the reference material for acquiring a more compre-hensive understanding of individual communication protocols.However, by examining the basic functions of protocols andreviewing the protocol characterization criteria identified inthis guide, the user will
9、be more apt to understanding otherprotocols not mentioned or addressed herein.2. Referenced Documents2.1 ASTM Standards:E 1013 Terminology Relating to Computerized Systems22.2 ANSI Standards:3X3T9.5 High Speed Local NetworkX3.139 Fiber Distributed Data Interface (FDDI) TokenRing Media Access Control
10、 (MAC)X3.148 Fiber Distributed Data Interface (FDDI) TokenRing Physical Layer Protocol (PHY)X3.166 Fiber Distributed Data Interface (FDDI) TokenRing Physical Layer Medium Dependent (PMD)X3.172 American National Standard Dictionary for Infor-mation Systems2.3 IEEE Standards:4100 Standard Dictionary f
11、or Electrical and Electronic Terms610 Standard Glossary for Software Engineering Terminol-ogy610.7 Standard Glossary of Computer Networking Termi-nology802.1 High Level Interface (Internetworking)802.2 Logical Link Control802.3 CSMA/CD Medium Access Control802.4 Token Bus Medium Access Control802.5
12、Token Ring Medium Access Control802.6 Metropolitan Area Networking802.8 Fiber Optic Technical Advisory Group802.9 Local and Metropolitan Area Networks: IntegratedServices (IS) LAN Interface at the Medium AccessControl (MAC) and Physical (PHY) Layers803.52.4 ISO Standards:37498 Information Processing
13、 SystemsOpen Systems Inter-connectionBasic Reference Model9040/9041 Virtual Terminal (VT)8831/8832 Job Transfer and Manipulation (JTM)8571/8572 File Transfer Access Management (FTAM)1This guide is under the jurisdiction of ASTM Committee F25 on Ships andMarine Technology and is the direct responsibi
14、lity of Subcommittee F25.05 onComputer Applications.Current edition approved Nov 10, 1996. Published December 1997.2Annual Book of ASTM Standards, Vol 14.01.3Available from American National Standards Institute (ANSI), 25 W. 43rd St.,4th Floor, New York, NY 10036.4Available from IEEE, 445 Hoes Lane,
15、 PO Box 1331, Piscataway, NJ 08854-1331.1Copyright ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.9595/9596 Common Management Information Service/Protocol (CMIP)8823 Connection Oriented Presentation Protocol8327 Connection Oriented Session Pro
16、tocol8073 Connection Oriented Transport Protocol8473 Connectionless Network Service8208 Packet Level Protocol8802-2 Logical Link Control9314-2 FDDI8802-3 CSMA/CD (Bus)8802-4 Token Bus8802-5 Token Ring7776 Link Access Protocol/Link Access Protocol-Balanced(LAP/LAPB)7809 High-Level Data Link Control (
17、HDLC)2.5 ITU Standards:5X.25 Packet Level ProtocolX.226 Connection Oriented Presentation ProtocolX.225 Connection Oriented Session ProtocolX.224 Connection Oriented Transport Protocol2.6 CCITT Standards:6V.35X.21 (BIS) Interface Between Data Terminal Equipment(DTE) and Data Circuit-Terminating Equip
18、ment (DCE)for Synchronous Operation on Public Data NetworksX.25 Interface Between Data Terminal Equipment (DTE)and Data Circuit Terminating Equipment (DCE) for Ter-minals Operating in the Packet Mode and ConnectedPublic Data Networks by Dedicated Circuit2.7 EIA/TIA Standard:6232C568 Commercial Build
19、ing Telecommunications WiringStandard (ANSI/EIA/TIA-568-91)2.8 Internet Request for Comments (RFCs) Standards:RFC 768 User Datagram Protocol (UDP)RFC 791 Internet Protocol (IP)7RFC 792 Internet Control Message Protocol (CMP)RFC 793 Transmission Control Protocol (TCP)7RFC 821 Simple Mail Transfer Pro
20、tocol (SMTP)7RFC 826RFC 854 TELNET Protocol7RFC 894RFC 903RFC 959 File Transfer Protocol (FTP)7RFC 1042RFC 1157 Simple Network Management ProtocolRFC 12013. Terminology3.1 The terminology used in this guide is defined in Termi-nology E 1013, IEEE 610, and ANSI X3.172, with the follow-ing additions d
21、efined in 3.2.3.2 Definitions of Terms Specific to This Standard:3.2.1 bridge, na device that interconnects local or remotenetworks no matter what network protocol that is, TCP/IP orIPX, are involved. Bridges form a single logical network.3.2.2 hub, na central location for the attachment of cablesfr
22、om nodes and other network components.3.2.3 internetwork, na collection of LANs using differentnetwork operating systems that are connected to form a largernetwork.3.2.4 LAN (local area network), na data communicationsystem consisting of a collection of interconnected computers,sharing applications,
23、 data and peripherals.3.2.5 network operating system (NOS), nthe software fora network that runs in a file server and control access to filesand other resources from multiple users.3.2.6 node(s), nany intelligent device connected to thenetwork. This includes terminal servers, host computers, andany
24、other devices, such as printers and terminals, that aredirectly connected to the network.3.2.7 protocol, na standard method of communicatingover a network.3.2.8 repeater, na network device that repeats signalsfrom one cable onto one or more other cables, while restoringsignal timing and waveforms.3.
25、2.9 router, na device capable of filtering/forwardingpackets based upon data link layer information.3.2.10 server, na device that stores data for network usersand provides network access to that data.3.2.11 topology, nthe arrangement of the nodes andconnecting hardware that comprises the network.3.2
26、.12 WAN (wide area network), na network using com-mon carrier transmission services for transmission of data overa large geographical area.4. Significance and Use4.1 This guide is intended to provide an understanding ofthe wide range of communication protocols standards, allow-ing the user to unders
27、tand better their applicability to shipboardnetworks and marine platform computerized systems. Forcomputerized networks and systems, communication protocolsare necessary for integrating various system devices, providingfunctionality between dissimilar subnetworks, or for enablingremote connections,
28、either pier side or through geophysicalcommunication technologies.4.2 The wide variety and scope of digital communicationprotocol standards adds greatly to the complex decision pro-cess for specifying compatible protocols for system applica-tions and related devices for the myriad of potential shipb
29、oardsystems. However, the user must identify the initial networkingrequirements, so once the network protocols under evaluationare well understood, the decision process should determine theappropriate network protocols. Therefore, this guide is in-tended to reduce the complexity involved with protoc
30、ol selec-tion and implementation.4.3 Network protocols define an agreed, quantifiable entity,or set of rules, by which user computers, system networks, andinternetworking devices communicate and exchange informa-tion. Communication protocols specify essential networkingguidelines, such as physical i
31、nterface connections, or data5Available from Electronic Industries Association, 2500 Wilson Blvd., Arling-ton, VA 22201.6Available from the U.S. Department of Commerce, National Technical Infor-mation Service, 5285 Port Royal Rd., Springfield, VA 22161.7Documents may be obtained via anonymous ftp fr
32、om the hosts:,directory rfc.F 1757 96 (2002)2format and control operations between two communicatingcomputers. Ship and marine digital communication protocolrequirements are no different than their land-based networkedcounterparts. Both require standardized protocol selection, invarious protocol cat
33、egories, including LAN standards, WANprotocols, LAN/WAN protocols, network management, wiringhub configurations/operations, hardware platforms, operatingsystems, and network applications.5. Origin of Protocol Development5.1 Communication protocol standards have been devel-oped or refined through thr
34、ee separate processes, identified asfollows:5.1.1 Defacto Protocol StandardsAcquired widespreaduse of a popular technique adopted by vendors and developers;5.1.2 Dejur Protocol StandardsStandards making bodies;and,5.1.3 Proprietary Protocol StandardPrivate corporation-based protocols with limited in
35、teroperability.5.2 The open standards approach is now the norm, whichallows multiple protocol networking solutions to be available,and as a result, proprietary protocols are now becomingobsolete.6. Local Network Interconnection6.1 The characteristic of a local network is determinedprimarily by three
36、 factors: transmission medium, topology, andmedium access control protocol.6.1.1 The principal technological elements that determinethe nature of a local network are the topology and transmissionmedium of the network. Together, it determines the type of datathat may be transmitted, the speed and eff
37、iciency of commu-nications, and the type of applications that a network maysupport.6.1.2 Interconnecting a set of local networks is referred to asan internetworking. The local networks are interconnected bydevices generically called gateways. Gateways provide acommunication path so that data can be
38、exchanged betweennetworks.6.2 TopologyThe common topologies used for local net-works are star, ring, and bus/tree (see Fig. 1).6.2.1 Star TopologyIn a star topology, a central switchingelement is used to connect all the nodes in the network. Thecentral element uses circuit switching to establish a d
39、edicatedpath between two stations wishing to communicate (see Fig. 1).6.2.2 Ring TopologyThe ring topology consists of aclosed loop, with each node attached to a repeating element.Data circulate around the ring on a series of point-to-point datalinks between repeaters. A station wishing to transmit
40、waits forits next turn and then sends data out onto the ring in the formof a packet (see Fig. 1).6.2.3 Bus/Tree TopologyThe bus or tree topology is char-acterized by the use of a multipoint medium. The bus is simplya special case of the tree, in which there is only one trunk, withno branches. Becaus
41、e all devices share a common communi-cations medium, only one pair of devices on a bus or tree cancommunicate at a time. A distributed medium access protocolis used to determine which station may transmit (see Fig. 1).6.3 Internetwork TopologyThe common topologies usedto support emerging networking
42、topologies requiring the inte-gration of data, video and voice, as well as higher transportbandwidth are backbone, hierarchical, and mesh (see Fig. 2).6.3.1 BackboneBackbone configurations are used in net-working environments in which local networks are connectedover high-speed backbone cables. Brid
43、ges and routers are usedto manage the data passing between interconnected networksand the backbone (see Fig. 2).6.3.2 HierarchialIn the hierarchial configuration, star-configured hubs are wired to a central hub that handles interhubtraffic. Routers and Asynchronous Transfer Mode (ATM)technology prov
44、ide support to traffic intensive network appli-cations requiring the integration of voice, video, and data (seeFig. 2).6.3.3 MeshIn mesh configurations, there are at least twopathways to each node. This is a common configuration inemerging high-speed enterprise networks requiring the integra-tion of
45、 voice, video, and data. It is composed of internetwork-ing devices, such as bridges, routers, and ATM technology. Theinternetworking devices provide efficient paths for data totravel from one point to another in this configuration. Meshnetworks often are used because of reliability; when one pathgo
46、es down, another can take over (see Fig. 2).6.4 CablingCabling falls into the following categories:coax, twisted pair, and fiber.6.4.1 Coax:6.4.1.1 ThicknetThe standard Thicknet is IEEE 802.310BASE5. It is a 0.4-in. diameter RG 4 50-V coaxial cable. Itmay be up to 500 m in length. A maximum of 100 d
47、evices canbe attached to this cable.6.4.1.2 ThinNetThe standard for ThinNet is IEEE 802.310BASE2. It is a 0.25-in. diameter RG58A/U 50-V coaxialcable. It can be up to 185 m in length and have a maximum of30 devices attached to it. Each device normally is attached at0.5-m increments via a BNC T-conne
48、ctor. However, devicesmay be attached to an AUI cable and external transceiver.6.4.2 Twisted Pair:6.4.2.1 The standard for twisted pair is EIA/TIA-568. It is a24-AWG telephone wire. The ends of the twisted pair wires areFIG. 1 Local Network TopologiesF 1757 96 (2002)3composed of RJ-45 or RJ-11 telep
49、hone-style connectors. Eachdevice connects to a network wiring hub which controls orpasses the network signal. There are five category ratings fortwisted pair wiring, LVL/CAT-1 through LVL/CAT-5.6.4.2.2 There are two major types of twisted pair: un-shielded twisted pair (UTP) and shielded twisted pair (STP).Environmental surroundings dictate what type of twisted pair isused. If the environment is prone to a high degree of electricalinterference, STP is used.6.4.3 Optical FiberSee Table 1.6.5 Table 2 provides a generalized comparison of t
