ASTM F1757-96(2002)

NOTICE: This standard has either been superseded and replaced by a new version or withdrawn.
Contact ASTM International (www.astm.org) for the latest information
An American National Standard
Designation: F 1757 – 96 (Reapproved 2002)
Standard Guide for
Digital Communication Protocols for Computerized
Systems
This standard is issued under the fixed designation F 1757; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (e) indicates an editorial change since the last revision or reapproval.
1. Scope 2. Referenced Documents
1.1 The principal content of this guide provides a road map 2.1 ASTM Standards:
to implement a communication network applicable to ship and E 1013 Terminology Relating to Computerized Systems
marine computer systems by: 2.2 ANSI Standards:
1.1.1 Examining the relationship of digital communication X3T9.5 High Speed Local Network
protocols as a network technological infrastructure, X3.139 Fiber Distributed Data Interface (FDDI) – Token
1.1.2 Outlining the basic building blocks of network topolo- Ring Media Access Control (MAC)
gies and transmission techniques associated with the imple- X3.148 Fiber Distributed Data Interface (FDDI)– Token
mentation of transmission media in a network environment; Ring Physical Layer Protocol (PHY)
and, X3.166 Fiber Distributed Data Interface (FDDI) – Token
1.1.3 Identifying operating system and environments. Ring Physical Layer Medium Dependent (PMD)
1.2 Using the Open System Interconnection (OSI) model, X3.172 American National Standard Dictionary for Infor-
which provides a layered approach to network functionality mation Systems
and evaluation, common network communications protocols 2.3 IEEE Standards:
areidentifiedandcharacterizedinthisguideaccordingtolower 100 StandardDictionaryforElectricalandElectronicTerms
and upper layer protocols corresponding to their degree and 610 Standard Glossary for Software Engineering Terminol-
type of functionality. ogy
1.3 Although it is desirable that network users, designers, 610.7 Standard Glossary of Computer Networking Termi-
and administrators recognize and understand every possible nology
networking protocol, it is not possible to know the intimate 802.1 High Level Interface (Internetworking)
details of every protocol specification. Accordingly, this guide 802.2 Logical Link Control
is not intended to address fully every hardware and software 802.3 CSMA/CD Medium Access Control
protocol ever developed for commercial use, which spans a 802.4 Token Bus Medium Access Control
period of about 25 years. Instead, the user of this guide will be 802.5 Token Ring Medium Access Control
introduced to a brief overview of the majority of past and 802.6 Metropolitan Area Networking
present protocols which may comprise a ship or marine 802.8 Fiber Optic Technical Advisory Group
internetwork, to include Local Area Networks (LANs), Wide 802.9 Local and Metropolitan Area Networks: Integrated
Area Networks (WANs), and related hardware and software Services (IS) LAN Interface at the Medium Access
that provide such network interoperability and data transfer. Control (MAC) and Physical (PHY) Layers
1.4 While this guide provides an understanding of the wide 803.5
range of communication protocols, the user is recommended to 2.4 ISO Standards:
consult the reference material for acquiring a more compre- 7498 Information Processing Systems–Open Systems Inter-
hensive understanding of individual communication protocols. connection–Basic Reference Model
However, by examining the basic functions of protocols and 9040/9041 Virtual Terminal (VT)
reviewing the protocol characterization criteria identified in 8831/8832 Job Transfer and Manipulation (JTM)
this guide, the user will be more apt to understanding other 8571/8572 File Transfer Access Management (FTAM)
protocols not mentioned or addressed herein.
Annual Book of ASTM Standards, Vol 14.01.
1 3
This guide is under the jurisdiction of ASTM Committee F25 on Ships and Available fromAmerican National Standards Institute (ANSI), 25 W. 43rd St.,
Marine Technology and is the direct responsibility of Subcommittee F25.05 on 4th Floor, New York, NY 10036.
Computer Applications. Available from IEEE, 445 Hoes Lane, PO Box 1331, Piscataway, NJ 08854-
Current edition approved Nov 10, 1996. Published December 1997. 1331.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.
F 1757 – 96 (2002)
9595/9596 Common Management Information Service/ 3.2 Definitions of Terms Specific to This Standard:
Protocol (CMIP) 3.2.1 bridge, n—a device that interconnects local or remote
8823 Connection Oriented Presentation Protocol networks no matter what network protocol that is, TCP/IP or
8327 Connection Oriented Session Protocol IPX, are involved. Bridges form a single logical network.
8073 Connection Oriented Transport Protocol 3.2.2 hub, n—a central location for the attachment of cables
8473 Connectionless Network Service from nodes and other network components.
8208 Packet Level Protocol 3.2.3 internetwork, n—a collection of LANs using different
8802-2 Logical Link Control network operating systems that are connected to form a larger
9314-2 FDDI network.
8802-3 CSMA/CD (Bus) 3.2.4 LAN (local area network), n—a data communication
8802-4 Token Bus system consisting of a collection of interconnected computers,
8802-5 Token Ring sharing applications, data and peripherals.
7776 Link Access Protocol/Link Access Protocol-Balanced 3.2.5 network operating system (NOS), n—the software for
(LAP/LAPB) a network that runs in a file server and control access to files
7809 High-Level Data Link Control (HDLC) and other resources from multiple users.
2.5 ITU Standards: 3.2.6 node(s), n—any intelligent device connected to the
X.25 Packet Level Protocol network. This includes terminal servers, host computers, and
X.226 Connection Oriented Presentation Protocol any other devices, such as printers and terminals, that are
X.225 Connection Oriented Session Protocol directly connected to the network.
X.224 Connection Oriented Transport Protocol 3.2.7 protocol, n—a standard method of communicating
2.6 CCITT Standards: over a network.
V.35 3.2.8 repeater, n—a network device that repeats signals
X.21 (BIS) Interface Between Data Terminal Equipment from one cable onto one or more other cables, while restoring
(DTE) and Data Circuit-Terminating Equipment (DCE) signal timing and waveforms.
for Synchronous Operation on Public Data Networks 3.2.9 router, n—a device capable of filtering/forwarding
X.25 Interface Between Data Terminal Equipment (DTE) packets based upon data link layer information.
and Data Circuit Terminating Equipment (DCE) for Ter- 3.2.10 server, n—a device that stores data for network users
minals Operating in the Packet Mode and Connected and provides network access to that data.
Public Data Networks by Dedicated Circuit 3.2.11 topology, n—the arrangement of the nodes and
2.7 EIA/TIA Standard: connecting hardware that comprises the network.
232C 3.2.12 WAN (wide area network), n—a network using com-
568 Commercial Building Telecommunications Wiring mon carrier transmission services for transmission of data over
Standard (ANSI/EIA/TIA-568-91) a large geographical area.
2.8 Internet Request for Comments (RFCs) Standards:
4. Significance and Use
RFC 768 User Datagram Protocol (UDP)
4.1 This guide is intended to provide an understanding of
RFC 791 Internet Protocol (IP)
the wide range of communication protocols standards, allow-
RFC 792 Internet Control Message Protocol (CMP)
ingtheusertounderstandbettertheirapplicabilitytoshipboard
RFC 793 Transmission Control Protocol (TCP)
networks and marine platform computerized systems. For
RFC 821 Simple Mail Transfer Protocol (SMTP)
computerized networks and systems, communication protocols
RFC 826
are necessary for integrating various system devices, providing
RFC 854 TELNET Protocol
functionality between dissimilar subnetworks, or for enabling
RFC 894
remote connections, either pier side or through geophysical
RFC 903
communication technologies.
RFC 959 File Transfer Protocol (FTP)
4.2 The wide variety and scope of digital communication
RFC 1042
protocol standards adds greatly to the complex decision pro-
RFC 1157 Simple Network Management Protocol
cess for specifying compatible protocols for system applica-
RFC 1201
tions and related devices for the myriad of potential shipboard
3. Terminology
systems.However,theusermustidentifytheinitialnetworking
requirements, so once the network protocols under evaluation
3.1 The terminology used in this guide is defined in Termi-
are well understood, the decision process should determine the
nology E 1013, IEEE 610, andANSI X3.172, with the follow-
appropriate network protocols. Therefore, this guide is in-
ing additions defined in 3.2.
tended to reduce the complexity involved with protocol selec-
tion and implementation.
4.3 Network protocols define an agreed, quantifiable entity,
Available from Electronic Industries Association, 2500 Wilson Blvd., Arling-
ton, VA 22201.
or set of rules, by which user computers, system networks, and
Available from the U.S. Department of Commerce, National Technical Infor-
internetworking devices communicate and exchange informa-
mation Service, 5285 Port Royal Rd., Springfield, VA 22161.
tion. Communication protocols specify essential networking
Documents may be obtained via anonymous ftp from the hosts:ds.internic.net,
directory rfc. guidelines, such as physical interface connections, or data
F 1757 – 96 (2002)
format and control operations between two communicating
computers. Ship and marine digital communication protocol
requirements are no different than their land-based networked
counterparts. Both require standardized protocol selection, in
various protocol categories, including LAN standards, WAN
protocols, LAN/WAN protocols, network management, wiring
hub configurations/operations, hardware platforms, operating
systems, and network applications.
5. Origin of Protocol Development
5.1 Communication protocol standards have been devel-
oped or refined through three separate processes, identified as
follows:
5.1.1 Defacto Protocol Standards—Acquired widespread
use of a popular technique adopted by vendors and developers;
5.1.2 Dejur Protocol Standards—Standards making bodies;
FIG. 1 Local Network Topologies
and,
5.1.3 Proprietary Protocol Standard—Private corporation-
based protocols with limited interoperability.
6.3 Internetwork Topology—The common topologies used
5.2 The open standards approach is now the norm, which
to support emerging networking topologies requiring the inte-
allows multiple protocol networking solutions to be available,
gration of data, video and voice, as well as higher transport
and as a result, proprietary protocols are now becoming
bandwidth are backbone, hierarchical, and mesh (see Fig. 2).
obsolete.
6.3.1 Backbone—Backbone configurations are used in net-
working environments in which local networks are connected
6. Local Network Interconnection
over high-speed backbone cables. Bridges and routers are used
6.1 The characteristic of a local network is determined
to manage the data passing between interconnected networks
primarily by three factors: transmission medium, topology, and
and the backbone (see Fig. 2).
medium access control protocol.
6.3.2 Hierarchial—In the hierarchial configuration, star-
6.1.1 The principal technological elements that determine
configuredhubsarewiredtoacentralhubthathandlesinterhub
the nature of a local network are the topology and transmission
traffic. Routers and Asynchronous Transfer Mode (ATM)
mediumofthenetwork.Together,itdeterminesthetypeofdata
technology provide support to traffic intensive network appli-
that may be transmitted, the speed and efficiency of commu-
cations requiring the integration of voice, video, and data (see
nications, and the type of applications that a network may
Fig. 2).
support.
6.3.3 Mesh—In mesh configurations, there are at least two
6.1.2 Interconnectingasetoflocalnetworksisreferredtoas
pathways to each node. This is a common configuration in
an internetworking. The local networks are interconnected by
emerging high-speed enterprise networks requiring the integra-
devices generically called gateways. Gateways provide a
tion of voice, video, and data. It is composed of internetwork-
communication path so that data can be exchanged between
ingdevices,suchasbridges,routers,andATMtechnology.The
networks.
internetworking devices provide efficient paths for data to
6.2 Topology—The common topologies used for local net-
travel from one point to another in this configuration. Mesh
works are star, ring, and bus/tree (see Fig. 1).
networks often are used because of reliability; when one path
6.2.1 Star Topology—In a star topology, a central switching goes down, another can take over (see Fig. 2).
element is used to connect all the nodes in the network. The
6.4 Cabling—Cabling falls into the following categories:
central element uses circuit switching to establish a dedicated coax, twisted pair, and fiber.
pathbetweentwostationswishingtocommunicate(seeFig.1).
6.4.1 Coax:
6.2.2 Ring Topology—The ring topology consists of a 6.4.1.1 Thicknet—The standard Thicknet is IEEE 802.3
closed loop, with each node attached to a repeating element. 10BASE5. It is a 0.4-in. diameter RG 4 50-V coaxial cable. It
Data circulate around the ring on a series of point-to-point data may be up to 500 m in length.Amaximum of 100 devices can
links between repeaters.Astation wishing to transmit waits for be attached to this cable.
its next turn and then sends data out onto the ring in the form 6.4.1.2 ThinNet—The standard for ThinNet is IEEE 802.3
of a packet (see Fig. 1).
10BASE2. It is a 0.25-in. diameter RG58A/U 50-V coaxial
6.2.3 Bus/Tree Topology—The bus or tree topology is char- cable. It can be up to 185 m in length and have a maximum of
acterized by the use of a multipoint medium.The bus is simply 30 devices attached to it. Each device normally is attached at
a special case of the tree, in which there is only one trunk, with 0.5-m increments via a BNC T-connector. However, devices
no branches. Because all devices share a common communi- may be attached to an AUI cable and external transceiver.
cations medium, only one pair of devices on a bus or tree can 6.4.2 Twisted Pair:
communicate at a time. A distributed medium access protocol 6.4.2.1 The standard for twisted pair is EIA/TIA-568. It is a
is used to determine which station may transmit (see Fig. 1). 24-AWGtelephonewire.Theendsofthetwistedpairwiresare
F 1757 – 96 (2002)
FIG. 2 Intern
...