rfc1208.txt

来自「RFC 的详细文档！」· 文本 代码 · 共 1,011 行 · 第 1/3 页


RFC 1208                INTEROP Pocket Glossary               March 1991


   Reference Model.

   ping: Packet internet groper.  A program used to test reachability of
   destinations by sending them an ICMP echo request and waiting for a
   reply.  The term is used as a verb: "Ping host X to see if it is up!"

   port: The abstraction used by Internet transport protocols to
   distinguish among multiple simultaneous connections to a single
   destination host.  See selector.

   POSI: Promoting Conference for OSI.  The OSI "800-pound gorilla" in
   Japan.  Consists of executives from the six major Japanese computer
   manufacturers and Nippon Telephone and Telegraph.  They set policies
   and commit resources to promote OSI.

   PPP: Point-to-Point Protocol.  The successor to SLIP, PPP provides
   router-to-router and host-to-network connections over both
   synchronous and asynchronous circuits.  See SLIP.

   Presentation Address: See OSI Presentation Address.

   Presentation Layer: The OSI layer that determines how Application
   information is represented (i.e., encoded) while in transit between
   two end systems.

   PRMD: Private Management Domain.  An X.400 Message Handling System
   private organization mail system.  Example: NASAmail.  See ADMD.

   protocol: A formal description of messages to be exchanged and rules
   to be followed for two or more systems to exchange information.

   proxy: The mechanism whereby one system "fronts for" another system
   in responding to protocol requests.  Proxy systems are used in
   network management to avoid having to implement full protocol stacks
   in simple devices, such as modems.

   proxy ARP: The technique in which one machine, usually a router,
   answers ARP requests intended for another machine.  By "faking" its
   identity, the router accepts responsibility for routing packets to
   the "real" destination.  Proxy ARP allows a site to use a single IP
   address with two physical networks.  Subnetting would normally be a
   better solution.

   PSN: Packet Switch Node.  The modern term used for nodes in the
   ARPANET and MILNET.  These used to be called IMPs (Interface Message
   Processors).  PSNs are currently implemented with BBN C30 or C300
   minicomputers.




Jacobsen & Lynch                                               [Page 13]

RFC 1208                INTEROP Pocket Glossary               March 1991


   RARE: Reseaux Associes pour la Recherche Europeenne.  European
   association of research networks.

   RARP: Reverse Address Resolution Protocol.  The Internet protocol a
   diskless host uses to find its Internet address at startup.  RARP
   maps a physical (hardware) address to an Internet address.  See ARP.

   RBOC: Regional Bell Operating Company.  See BOC.

   repeater: A device which propagates electrical signals from one cable
   to another without making routing decisions or providing packet
   filtering.  In OSI terminology, a repeater is a Physical Layer
   intermediate system.  See bridge and router.

   RFC: Request For Comments.  The document series, begun in 1969, which
   describes the Internet suite of protocols and related experiments.
   Not all (in fact very few) RFCs describe Internet standards, but all
   Internet standards are written up as RFCs.

   RFS: Remote File System.  A distributed file system, similar to NFS,
   developed by AT&T and distributed with their UNIX System V operating
   system.  See NFS.

   RIP: Routing Information Protocol.  An Interior Gateway Protocol
   (IGP) supplied with Berkeley UNIX.

   RIPE: Reseaux IP Europeenne.  European continental TCP/IP network
   operated by EUnet.  See EUnet.

   rlogin: A service offered by Berkeley UNIX which allows users of one
   machine to log into other UNIX systems (for which they are
   authorized) and interact as if their terminals were connected
   directly.  Similar to Telnet.

   ROSE: Remote Operations Service Element.  A lightweight RPC protocol,
   used in OSI Message Handling, Directory, and Network Management
   application protocols.

   router: A system responsible for making decisions about which of
   several paths network (or Internet) traffic will follow.  To do this
   it uses a routing protocol to gain information about the network, and
   algorithms to choose the best route based on several criteria known
   as "routing metrics."  In OSI terminology, a router is a Network
   Layer intermediate system.  See gateway, bridge and repeater.

   RPC: Remote Procedure Call.  An easy and popular paradigm for
   implementing the client-server model of distributed computing.  A
   request is sent to a remote system to execute a designated procedure,



Jacobsen & Lynch                                               [Page 14]

RFC 1208                INTEROP Pocket Glossary               March 1991


   using arguments supplied, and the result returned to the caller.
   There are many variations and subtleties, resulting in a variety of
   different RPC protocols.

   RTSE: Reliable Transfer Service Element.  A lightweight OSI
   application service used above X.25 networks to handshake application
   PDUs across the Session Service and TP0.  Not needed with TP4, and
   not recommended for use in the U.S. except when talking to X.400
   ADMDs.

   SAP: Service Access Point.  The point at which the services of an OSI
   layer are made available to the next higher layer.  The SAP is named
   according to the layer providing the services: e.g., Transport
   services are provided at a Transport SAP (TSAP) at the top of the
   Transport Layer.

   selector: The identifier used by an OSI entity to distinguish among
   multiple SAPs at which it provides services to the layer above.  See
   port.

   Session Layer: The OSI layer that provides means for dialogue control
   between end systems.

   SGMP: Simple Gateway Management Protocol.  The predecessor to SNMP.
   See SNMP.

   SLIP: Serial Line IP.  An Internet protocol used to run IP over
   serial lines such as telephone circuits or RS-232 cables
   interconnecting two systems.  SLIP is now being replaced by PPP.  See
   PPP.

   SMDS: Switched Multimegabit Data Service.  An emerging high-speed
   networking technology to be offered by the telephone companies in the
   U.S.

   SMI: Structure of Management Information.  The rules used to define
   the objects that can be accessed via a network management protocol.
   See MIB.

   SMTP: Simple Mail Transfer Protocol.  The Internet electronic mail
   protocol.  Defined in RFC 821, with associated message format
   descriptions in RFC 822.

   SNA: Systems Network Architecture.  IBM's proprietary network
   architecture.

   SNMP: Simple Network Management Protocol.  The network management
   protocol of choice for TCP/IP-based internets.



Jacobsen & Lynch                                               [Page 15]

RFC 1208                INTEROP Pocket Glossary               March 1991


   SPAG: Standards Promotion and Application Group.  A group of European
   OSI manufacturers which chooses option subsets and publishes these in
   a "Guide to the Use of Standards" (GUS).

   SQL: Structured Query Language.  The international standard language
   for defining and accessing relational databases.

   subnet mask: See address mask.

   subnetwork: A collection of OSI end systems and intermediate systems
   under the control of a single administrative domain and utilizing a
   single network access protocol.  Examples: private X.25 networks,
   collection of bridged LANs.

   TCP: Transmission Control Protocol.  The major transport protocol in
   the Internet suite of protocols providing reliable, connection-
   oriented, full-duplex streams.  Uses IP for delivery.  See TP4.

   Telnet: The virtual terminal protocol in the Internet suite of
   protocols.  Allows users of one host to log into a remote host and
   interact as normal terminal users of that host.

   three-way-handshake: The process whereby two protocol entities
   synchronize during connection establishment.

   TP0: OSI Transport Protocol Class 0 (Simple Class).  This is the
   simplest OSI Transport Protocol, useful only on top of an X.25
   network (or other network that does not lose or damage data).

   TP4: OSI Transport Protocol Class 4 (Error Detection and Recovery
   Class).  This is the most powerful OSI Transport Protocol, useful on
   top of any type of network.  TP4 is the OSI equivalent to TCP.

   transceiver: Transmitter-receiver.  The physical device that connects
   a host interface to a local area network, such as Ethernet.  Ethernet
   transceivers contain electronics that apply signals to the cable and
   sense collisions.

   Transport Layer: The OSI layer that is responsible for reliable end-
   to-end data transfer between end systems.

   UA: User Agent.  An OSI application process that represents a human
   user or organization in the X.400 Message Handling System.  Creates,
   submits, and takes delivery of messages on the user's behalf.

   UDP: User Datagram Protocol.  A transport protocol in the Internet
   suite of protocols.  UDP, like TCP, uses IP for delivery; however,
   unlike TCP, UDP provides for exchange of datagrams without



Jacobsen & Lynch                                               [Page 16]

RFC 1208                INTEROP Pocket Glossary               March 1991


   acknowledgements or guaranteed delivery.  See CLTP.

   UUCP: UNIX to UNIX Copy Program.  A protocol used for communication
   between consenting UNIX systems.

   XDR: eXternal Data Representation.  A standard for machine-
   independent data structures developed by Sun Microsystems.  Similar
   to ASN.1.

   X/Open: A group of computer manufacturers that promotes the
   development of portable applications based on UNIX.  They publish a
   document called the X/Open Portability Guide.

   X Recommendations: The CCITT documents that describe data
   communication network standards.  Well-known ones include: X.25
   Packet Switching standard, X.400 Message Handling System, and X.500
   Directory Services.

   The X Window System (TM): A popular window system developed by MIT
   and implemented on a number of workstations.

For More Information

   As indicated in the introduction, this is only a partial list of
   words from the world of interoperability.  Yes, you're right, we
   didn't list "interoperability" because the jury is still out on
   exactly what it means, and we invite you to suggest a definition.

   To learn more about these topics, consult the books, standards
   documents, bibliographies, periodicals, mailing lists, etc. listed in
   "Information Sources" in the December 1989 issue of ConneXions--The
   Interoperability Report.

Security Considerations

   Security issues are not discussed in this memo.















Jacobsen & Lynch                                               [Page 17]

RFC 1208                INTEROP Pocket Glossary               March 1991


Authors' Addresses

   Ole J. Jacobsen
   Interop, Inc.
   480 San Antonio Road
   Suite 100
   Mountain View, CA 94040

   Phone: [phone]

   EMail: [e-mail]


   Daniel C. Lynch
   Interop, Inc.
   480 San Antonio Road
   Interop, Inc.
   480 San Antonio Road
   Suite 100
   Mountain View, CA 94040

   Phone: [phone]

   EMail: [e-mail]



























Jacobsen & Lynch                                               [Page 18]