1、Designation: F 1757 96 (Reapproved 2008)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 () 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 ne
3、twork 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 tran
4、smission 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 t
5、his 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 eve
6、ry 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 pr
7、otocols 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 pro
8、tocols, 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 b
9、e more apt to understanding otherprotocols not mentioned or addressed herein.2. Referenced Documents2.1 ASTM Standards:2E 1013 Terminology Relating to Computerized Systems32.2 ANSI Standards:4X3T9.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:5100 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:47498 Information Processing
13、 SystemsOpen Systems Inter-connectionBasic Reference Model9040/9041 Virtual Terminal (VT)1This guide is under the jurisdiction of ASTM Committee F25 on Ships andMarine Technology and is the direct responsibility of Subcommittee F25.05 onComputer Applications.Current edition approved May 1, 2008. Pub
14、lished July 2008. Originally approvedin 1996. Last previous edition approved in 2002 as F 1757 - 96(2002).2For referenced ASTM standards, visit the ASTM website, www.astm.org, orcontact ASTM Customer Service at serviceastm.org. For Annual Book of ASTMStandards volume information, refer to the standa
15、rds Document Summary page onthe ASTM website.3Withdrawn.4Available from American National Standards Institute (ANSI), 25 W. 43rd St.,4th Floor, New York, NY 10036, http:/www.ansi.org.5Available from Institute of Electrical and Electronics Engineers, Inc. (IEEE),445 Hoes Ln., P.O. Box 1331, Piscatawa
16、y, NJ 08854-1331, http:/www.ieee.org.1Copyright ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.8831/8832 Job Transfer and Manipulation (JTM)8571/8572 File Transfer Access Management (FTAM)9595/9596 Common Management Information Service/Protoco
17、l (CMIP)8823 Connection Oriented Presentation Protocol8327 Connection Oriented Session Protocol8073 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
18、Access Protocol/Link Access Protocol-Balanced(LAP/LAPB)7809 High-Level Data Link Control (HDLC)2.5 ITU Standards:6X.25 Packet Level ProtocolX.226 Connection Oriented Presentation ProtocolX.225 Connection Oriented Session ProtocolX.224 Connection Oriented Transport Protocol2.6 CCITT Standards:7V.35X.
19、21 (BIS) Interface Between Data Terminal Equipment(DTE) and Data Circuit-Terminating Equipment (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 Connec
20、tedPublic Data Networks by Dedicated Circuit2.7 EIA/TIA Standard:7232C568 Commercial Building 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)8RFC 792 Internet Control Message
21、Protocol (CMP)RFC 793 Transmission Control Protocol (TCP)8RFC 821 Simple Mail Transfer Protocol (SMTP)8RFC 826RFC 854 TELNET Protocol8RFC 894RFC 903RFC 959 File Transfer Protocol (FTP)8RFC 1042RFC 1157 Simple Network Management ProtocolRFC 12013. Terminology3.1 The terminology used in this guide is
22、defined in Termi-nology E 1013, IEEE 610, and ANSI X3.172, with the follow-ing additions defined 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 f
23、orm a single logical network.3.2.2 hub, na central location for the attachment of cablesfrom 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 commun
24、icationsystem consisting of a collection of interconnected computers,sharing applications, 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 intellige
25、nt device connected to thenetwork. This includes terminal servers, host computers, andany 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 signalsf
26、rom one cable onto one or more other cables, while restoringsignal timing and waveforms.3.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 top
27、ology, nthe arrangement of the nodes andconnecting hardware that comprises the network.3.2.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 underst
28、anding ofthe wide range of communication protocols standards, allow-ing the user to understand better their applicability to shipboardnetworks and marine platform computerized systems. Forcomputerized networks and systems, communication protocolsare necessary for integrating various system devices,
29、providingfunctionality between dissimilar subnetworks, or for enablingremote connections, 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 compatibl
30、e protocols for system applica-tions and related devices for the myriad of potential shipboardsystems. However, the user must identify the initial networkingrequirements, so once the network protocols under evaluationare well understood, the decision process should determine theappropriate network p
31、rotocols. Therefore, this guide is in-tended to reduce the complexity involved with protocol selec-tion and implementation.6Available from Electronic Industries Alliance (EIA), 2500 Wilson Blvd.,Arlington, VA 22201, http:/www.eia.org.7Available from the U.S. Department of Commerce, National Technica
32、l Infor-mation Service (NTIS), 5285 Port Royal Rd., Springfield, VA 22161, http:/www.ntis.gov.8Documents may be obtained via anonymous ftp from the hosts:,directory rfc.F 1757 96 (2008)24.3 Network protocols define an agreed, quantifiable entity,or set of rules, by which user computers, system netwo
33、rks, andinternetworking devices communicate and exchange informa-tion. Communication protocols specify essential networkingguidelines, such as physical interface connections, or dataformat and control operations between two communicatingcomputers. Ship and marine digital communication protocolrequir
34、ements are no different than their land-based networkedcounterparts. Both require standardized protocol selection, invarious protocol categories, including LAN standards, WANprotocols, LAN/WAN protocols, network management, wiringhub configurations/operations, hardware platforms, operatingsystems, a
35、nd network applications.5. Origin of Protocol Development5.1 Communication protocol standards have been devel-oped or refined through three separate processes, identified asfollows:5.1.1 Defacto Protocol StandardsAcquired widespreaduse of a popular technique adopted by vendors and developers;5.1.2 D
36、ejur Protocol StandardsStandards making bodies;and,5.1.3 Proprietary Protocol StandardPrivate corporation-based protocols with limited interoperability.5.2 The open standards approach is now the norm, whichallows multiple protocol networking solutions to be available,and as a result, proprietary pro
37、tocols are now becomingobsolete.6. Local Network Interconnection6.1 The characteristic of a local network is determinedprimarily by three factors: transmission medium, topology, andmedium access control protocol.6.1.1 The principal technological elements that determinethe nature of a local network a
38、re the topology and transmissionmedium of the network. Together, it determines the type of datathat may be transmitted, the speed and efficiency 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 internetworkin
39、g. The local networks are interconnected bydevices generically called gateways. Gateways provide acommunication path so that data can be 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 topolog
40、y, a central switchingelement is used to connect all the nodes in the network. Thecentral element uses circuit switching to establish a dedicatedpath 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 r
41、epeating element.Data circulate around the ring on a series of point-to-point datalinks between repeaters. A station wishing to transmit 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
42、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. Because 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 use
43、d to determine which station may transmit (see Fig. 1).6.3 Internetwork TopologyThe common topologies usedto support emerging networking 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 Backbo
44、neBackbone configurations are used in net-working environments in which local networks are connectedover high-speed backbone cables. Bridges and routers are usedto manage the data passing between interconnected networksand the backbone (see Fig. 2).6.3.2 HierarchialIn the hierarchial configuration,
45、star-configured hubs are wired to a central hub that handles interhubtraffic. Routers and Asynchronous Transfer Mode (ATM)technology provide 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
46、at least twopathways to each node. This is a common configuration inemerging high-speed enterprise networks requiring the integra-tion of voice, video, and data. It is composed of internetwork-ing devices, such as bridges, routers, andATM technology. Theinternetworking devices provide efficient path
47、s for data totravel from one point to another in this configuration. Meshnetworks often are used because of reliability; when one pathgoes 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 stan
48、dard 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 devices 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
49、to 185 m in length and have a maximum of30 devices attached to it. Each device normally is attached atFIG. 1 Local Network TopologiesF 1757 96 (2008)30.5-m increments via a BNC T-connector. 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 arecomposed of RJ-45 or RJ-11 telephone-style connectors. Eachdevice connects to a network wiring hub which controls orpasses the networ
