Internet FAQ

Here you will find two general lists of Frequently Asked Questions (FAQs) about the Internet, and Answers--one for new Internet users and one for experienced Internet users. Scroll through this window and use the hyperlinks to see if an entry in one of the FAQs already addresses your question.

Answers to Commonly asked "New Internet User" Questions

  • Introduction
  • Acknowledgements
  • Questions About TCP/IP
  • What is TCP/IP?
  • What are the other well-known standard protocols in the TCP/IP family?
  • Questions About the Domain Name System
  • What is the Domain Name System?
  • What is a Fully Qualified Domain Name?
  • Questions About Internet Documentation
  • What is an RFC?
  • Which RFCs are Standards?
  • What is an Internet Draft? Are there any guidelines available for writing one?
  • How do I obtain OSI Standards documents?
  • Online sources:
  • Hardcopy sources:
  • Questions about Internet Organizations and Contacts
  • What is the IAB?
  • What is the IANA?
  • What is a NIC? What is a NOC?
  • What is "The NIC"?
  • What is the IR?
  • What is the IETF?
  • What is the IRTF?
  • Questions About Services
  • How do I use the WHOIS program at the DDN NIC?
  • How do I become registered in the DDN NIC's WHOIS database?
  • How do I use the White Pages at PSI?
  • How do I use the Knowbot Information Service?
  • What is Usenet? What is Netnews?
  • How do I get on Usenet? How do I get Netnews on my computer?
  • What is anonymous FTP?
  • What is "TELNET"?
  • Mailing Lists
  • What is a mailing list?
  • How do I contact the administrator of a mailing list rather than posting to the entire list?
  • What are some good mailing lists or news groups?
  • How do I subscribe to the TCP-IP mailing list?
  • How do I subscribe to the IETF mailing list?
  • How do I subscribe to the RFC Distribution list?
  • What does :-) mean?
  • What do "btw", "fyi", "imho", "wrt", and "rtfm" mean?
  • What is the "FAQ" list?
  • Suggested Reading

    Answers to Commonly asked "Experienced Internet User" Questions

  • Introduction
  • Acknowledgments
  • Questions about the Internet
  • How do I get statistics regarding the traffic on NSFNET?
  • Questions About Other Networks and Internets
  • We have a user who would like to access a machine on "EARN/BITNET". I can't find anything on this in the domain name tables. Please, what is this, and how do I connect to it?
  • Additional Information:
  • Questions About Internet Documentation
  • Where do I get information regarding ordering documents related to GOSIP?
  • Questions About Domain Name System (DNS)
  • Is there a DNS Query server?
  • Has any one else had frequent BIND failures (especially major domain sites that have heavy TCP domain loads)?
  • Is the model used by the domain name system for host names that the owner of a name gets to choose its case?
  • Is this required or should I not be concerned that the additional field is empty?
  • Questions About Network Management Implementations
  • In reading the SNMP RFCs [3,4,5,6] I find mention of authentication of PDUs. Are there any standards for authentication mechanisms?
  • Can vendors make their enterprise-specific variables available to users through a standard distribution mechanism?
  • Does anyone have a suggestion as to how I can determine whether I can just print the string or whether I should display the octet bytes?
  • Where are these MIB tools available for public FTP?
  • Suppose I want to create a private MIB object for causing some action to happen, say, do a reset.
  • Questions about Serial Line Internet Protocol (SLIP) and Point-to-Point Protocol (PPP) Implementations
  • I seem to recall hearing that SLIP [8] will only run on synchronous serial lines. Is this true? ...
  • Is there something about SLIP which precludes it's being implemented over async lines?
  • Since we are very interested in standards in this area, could someone tell me were I can find more information on PPP?
  • Does anyone know if there is a way to run a SLIP program on a IBM computer running SCO Xenix/Unix, with a multi-port serial board?
  • Questions About Routing
  • Some postings mentioned "maximum entropy routing". Could someone please provide a pointer to on-line or off-line references to this topic?
  • Other Protocol and Standards Implementation Questions
  • Does anyone recognize ethernet type "80F3"?
  • Additional Information:
  • Does anyone know the significance of a high value for "Bad proto" in the output from netstat on Unix machines using ethernet?
  • Which RFC would explain the proper way to configure broadcast addresses when using subnets?
  • Can anyone tell me what .TAR files exactly are?
  • Suggested Reading
  • Security Considerations
  • Authors' Addresses

    Answers to Commonly asked "New Internet User" Questions
    This FYI RFC is produced by the User Services Working Group of the Internet Engineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet.

    This memo provides information for the Internet community. It does not specify any standard. Distribution of this memo is unlimited.

    Introduction
    New users joining the Internet community have the same questions as did everyone else who has ever joined. Our quest is to provide the Internet community with up to date, basic Internet knowledge and experience, while moving the redundancies away from the electronic mailing lists so that the lists' subscribers do not have to read the same queries and answers over and over again.

    Future updates of this memo will be produced as User Services members become aware of additional questions that should be included, and of deficiencies or inaccuracies that should be amended in this document. An additional FYI Q/A will be published which will deal with intermediate and advanced Q/A topics.

    The Q/A mailing lists are maintained by Gary Malkin at FTP.COM. They are used by a subgroup of the User Services Working Group to discuss the Q/A FYIs. They include:

    quail@ftp.com This is a discussion mailing list. Its primary use is for pre-release review of the Q/A FYIs.

    quail-request@ftp.com This is how you join the quail mailing list.

    quail-box@ftp.com This is a write-only list which serves as a repository for candidate questions and answers. It is not necessary to be on the quail mailing list to forward to the quail-box.

    Acknowledgements
    The following people deserve thanks for their help and contributions to this FYI Q/A: Vint Cerf (CNRI), Ralph Droms (Bucknell), Tracy LaQuey Parker (UTexas), Craig Partridge (SICS), Jon Postel (ISI), Joyce K. Reynolds (ISI), Karen Roubicek (BBNST), Marty Schoffstall (PSI, Inc.), Patricia Smith (Merit), Gene Spafford (Purdue) and James Van Bokkelen (FTP Software, Inc.).

    Questions About TCP/IP
    What is TCP/IP?
    TCP/IP (Transmission Control Protocol/Internet Protocol) [4,5,6] is the common name for a family of over 100 data-communications protocols used to organize computers and data-communications equipment into computer networks. TCP/IP was developed to interconnect hosts on ARPANET, PRNET (packet radio), and SATNET (packet satellite). All three of these networks have since been retired; but TCP/IP lives on. It is currently used on the Internet. TCP/IP is also sometimes used for other networks, particularly local area networks that tie together numerous different kinds of computers or tie together engineering workstations.

    What are the other well-known standard protocols in the TCP/IP family?
    Other than TCP and IP, the three main protocols in the TCP/IP suite are the Simple Mail Transfer Protocol (SMTP) [8], the File Transfer Protocol (FTP) [3], and the TELNET Protocol [9]. There are many other protocols in use on the Internet. The Internet Activities Board (IAB) regularly publishes an RFC [2] that describes the state of standardization of the various Internet protocols. This document is the best guide to the current status of Internet protocols and their recommended usage.

    Questions About the Domain Name System
    What is the Domain Name System?
    The Domain Name System (DNS) is a hierarchical, distributed method of organizing the name space of the Internet. The DNS administratively groups hosts into a hierarchy of authority that allows addressing and other information to be widely distributed and maintained. A big advantage to the DNS is that using it eliminates dependence on a centrally-maintained file that maps host names to addresses.

    What is a Fully Qualified Domain Name?
    A Fully Qualified Domain Name (FQDN) is a domain name that includes all higher level domains relevant to the entity named. If you think of the DNS as a tree-structure with each node having its own label, a Fully Qualified Domain Name for a specific node would be its label followed by the labels of all the other nodes between it and the root of the tree. For example, for a host, a FQDN would include the string that identifies the particular host, plus all domains of which the host is a part up to and including the top-level domain (the root domain is always null). For example, PARIS.NISC.SRI.COM is a Fully Qualified Domain Name for the host at 192.33.33.109. In addition, NISC.SRI.COM is the FQDN for the NISC domain.

    Questions About Internet Documentation
    What is an RFC?
    The Request for Comments documents (RFCs) are working notes of the Internet research and development community. A document in this series may be on essentially any topic related to computer communication, and may be anything from a meeting report to the specification of a standard. Submissions for Requests for Comments may be sent to the RFC Editor, Jon Postel (POSTEL@ISI.EDU).

    Most RFCs are the descriptions of network protocols or services, often giving detailed procedures and formats for their implementation. Other RFCs report on the results of policy studies or summarize the work of technical committees or workshops. All RFCs are considered public domain unless explicitly marked otherwise.

    While RFCs are not refereed publications, they do receive technical review from either the task forces, individual technical experts, or the RFC Editor, as appropriate. Currently, most standards are published as RFCs, but not all RFCs specify standards.

    Anyone can submit a document for publication as an RFC. Submissions must be made via electronic mail to the RFC Editor. Please consult RFC 1111, "Instructions to RFC Authors" [10], for further information. RFCs are accessible online in public access files, and a short message is sent to a notification distribution list indicating the availability of the memo. Requests to be added to this distribution list should be sent to RFC- REQUEST@NIC.DDN.MIL.

    The online files are copied by interested people and printed or displayed at their sites on their equipment. (An RFC may also be returned via electronic mail in response to an electronic mail query.) This means that the format of the online files must meet the constraints of a wide variety of printing and display equipment.

    Once a document is assigned an RFC number and published, that RFC is never revised or re-issued with the same number. There is never a question of having the most recent version of a particular RFC. However, a protocol (such as File Transfer Protocol (FTP)) may be improved and re-documented many times in several different RFCs. It is important to verify that you have the most recent RFC on a particular protocol. The "IAB Official Protocol Standards" [2] memo is the reference for determining the correct RFC to refer to for the current specification of each protocol.

    How do I obtain RFCs?
    An index of RFCs can be located on the World Wide Web from the Information Science Institute.

    RFCs can be obtained via FTP from NIC.DDN.MIL, with the pathname RFC:RFCnnnn.TXT or RFC:RFCnnnn.PS (where "nnnn" refers to the number of the RFC). Login using FTP, username "anonymous" and password "guest". The NIC also provides an automatic mail service for those sites which cannot use FTP. Address the request to SERVICE@NIC.DDN.MIL and in the subject field of the message indicate the RFC number, as in "Subject: RFC nnnn" (or "Subject: RFC nnnn.PS" for PostScript RFCs).

    RFCs can also be obtained via FTP from NIS.NSF.NET. Using FTP, login with username "anonymous" and password "guest"; then connect to the RFC directory ("cd RFC"). The file name is of the form RFCnnnn.TXT-1 (where "nnnn" refers to the number of the RFC). The NIS also provides an automatic mail service for those sites which cannot use FTP. Address the request to NIS-INFO@NIS.NSF.NET and leave the subject field of the message blank. The first line of the text of the message must be "SEND RFCnnnn.TXT-1", where nnnn is replaced by the RFC number.

    Requests for special distribution should be addressed to either the author of the RFC in question, or to NIC@NIC.DDN.MIL. SRI International operates NIC.DDN.MIL and has a hardcopy subscription service for RFCs as well as several publications which incorporate a selection of RFCs defining Internet standards. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.

    Which RFCs are Standards?
    See "IAB Official Protocol Standards" (currently, RFC 1140) [2].

    What is an Internet Draft? Are there any guidelines available for writing one?
    Internet Drafts (I-D's) are the current working documents of the Internet Engineering Task Force (IETF). Internet Drafts are generally in the format of an RFC with some key differences:

  • - The Internet Drafts are not RFC's and are not a numbered document series.
  • - The words INTERNET-DRAFT appear in place of RFC XXXX in the upper left-hand corner.
  • - The document does not refer to itself as an RFC or as a Draft RFC.
  • - An Internet Draft does not state nor imply that it is a proposed standard. To do so conflicts with the role of the Internet Architecture Board (IAB), the RFC Editor, and the Internet Engineering Steering Group (IESG).

    An Internet Drafts Directory has been installed to make available, for review and comment by the IETF members, draft documents that will be submitted ultimately to the IAB and the RFC Editor to be considered for publishing as an RFC. The Internet Drafts Directories are maintained primarily at the NSFNET Network Service Center (NNSC). There are several "shadow" machines which contain the IETF and Internet Drafts Directories. They are:

  • NSF Network Service Center: nnsc.nsf.net
  • DDN NIC: nic.ddn.mil Pacific Rim: munnari.oz.au
  • Europe: nic.nordu.net (192.36.148.17)

    To access these directories, use anonymous FTP. Login with username, "anonymous", password, "guest". Once logged in, change to the directory, "cd internet-drafts". Internet Draft files can then be retrieved.

    For further information on the Internet Drafts of the IETF, or if you have problems with retrieving Internet Draft documents, contact Megan Davies (mdavies@nri.reston.va.us) or Greg Vaudreuil (gvaudre@nri.reston.va.us) for assistance.

    How do I obtain OSI Standards documents?
    OSI Standards documents are NOT available from the Internet via anonymous FTP due to copyright restrictions. These are available from:

    Omnicom Information Service
    501 Church Street NE Suite 304
    Vienna, VA 22180 USA
    Telephone: (800) 666-4266 or (703) 281-1135
    Fax: (703) 281-1505

    However, the GOSIP specification which covers the use of OSI protocols within the U.S. Government is available from the NIC and from the National Institute of Standards and Technology (NIST). The final text of GOSIP Version 2 is now available from both sites. Version 2 is expected to become a Federal Information Processing Standard (FIPS) in early 1991.

    Online sources:
    Available through anonymous ftp from osi.ncsl.nist.gov (129.6.48.100) as:

  • ./pub/gosip/gosip_v2.txt -- ascii
  • ./pub/gosip/gosip_v2.txt.Z -- ascii compressed
  • ./pub/gosip/gosip_v2.ps -- PostScript
  • ./pub/gosip/gosip_v2.ps.Z -- PostScript compressed

    Available through anonymous ftp from nic.ddn.mil (192.67.67.20) as:

  • PROTOCOLS:GOSIP-V2.TXT -- ascii
  • PROTOCOLS:GOSIP-V2.PS -- PostScript Hardcopy sources:
    Standards Processing Coordinator (ADP)
    National Institute of Standards and Technology Technology Building,
    Room B-64
    Gaithersburg, MD 20899
    (301) 975-2816
    Network Information Systems Center
    SRI International, Room EJ291
    333 Ravenswood Ave.
    Menlo Park, CA 94025
    1-800-235-3155

    Questions about Internet Organizations and Contacts
    What is the IAB?
    The Internet Architecture Board (IAB) is the coordinating committee for Internet design, engineering and management [7]. IAB members are deeply committed to making the Internet function effectively and evolve to meet a large scale, high speed future. The chairman serves a term of two years and is elected by the members of the IAB. The current Chair of the IAB is Brian Carpenter. The IAB focuses on the TCP/IP protocol suite, and extensions to the Internet system to support multiple protocol suites.

    The IAB performs the following functions:

      1) Sets Internet Standards,
      2) Manages the RFC publication process,
      3) Reviews the operation of the IETF and IRTF,
      4) Performs strategic planning for the Internet, identifying long-range problems and opportunities,
      5) Acts as an international technical policy liaison and representative for the Internet community, and
      6) Resolves technical issues which cannot be treated within the IETF or IRTF frameworks.

    The IAB has two principal subsidiary task forces:

    1) Internet Engineering Task Force (IETF)
    2) Internet Research Task Force (IRTF)

    Each of these Task Forces is led by a chairman and guided by a Steering Group which reports to the IAB through its chairman. For the most part, a collection of Research or Working Groups carries out the work program of each Task Force.

    All decisions of the IAB are made public. The principal vehicle by which IAB decisions are propagated to the parties interested in the Internet and its TCP/IP protocol suite is the Request for Comments (RFC) note series and the Internet Monthly Report.

    What is the IANA?
    The task of coordinating the assignment of values to the parameters of protocols is delegated by the Internet Architecture Board (IAB) to the Internet Assigned Numbers Authority (IANA). These protocol parameters include op-codes, type fields, terminal types, system names, object identifiers, and so on. The "Assigned Numbers" Request for Comments (RFC) [1] documents the currently assigned values from several series of numbers used in network protocol implementations. Internet addresses and Autonomous System numbers are assigned by the Network Information Center at SRI International. This responsibility has been delegated by the IANA to the DDN NIC which serves as the Internet Registry. The IANA is located at USC/Information Sciences Institute.

    Current types of assignments listed in Assigned Numbers and maintained by the IANA are:

  • Address Resolution Protocol Parameters
  • ARPANET and MILNET X.25 Address Mappings
  • ARPANET and MILNET Logical Addresses
  • ARPANET and MILNET Link Numbers
  • BOOTP Parameters and BOOTP Extension Codes
  • Domain System Parameters
  • IANA Ethernet Address Blocks
  • Ethernet Numbers of Interest
  • IEEE 802 Numbers of Interest
  • Internet Protocol Numbers
  • Internet Version Numbers
  • IP Time to Live Parameter
  • IP TOS Parameters
  • Machine Names
  • Mail Encryption Types
  • Multicast Addresses
  • Network Management Parameters
  • Point-to-Point Protocol Field Assignments
  • PRONET 80 Type Numbers
  • Port Assignments
  • Protocol and Service Names
  • Protocol/Type Field Assignments
  • Public Data Network Numbers
  • Reverse Address Resolution Protocol Operation Codes
  • TELNET Options
  • Terminal Type Names
  • Unix Ports
  • X.25 Type Numbers

    For more information on number assignments, contact IANA@ISI.EDU.

    What is a NIC? What is a NOC?
    "NIC" stands for Network Information Center. It is an organization which provides network users with information about services provided by the network.

    "NOC" stands Network Operations Center. It is an organization that is responsible for maintaining a network.

    For many networks, especially smaller, local networks, the functions of the NIC and NOC are combined. For larger networks, such as mid-level and backbone networks, the NIC and NOC organizations are separate, yet they do need to interact to fully perform their functions.

    What is "The NIC"?
    "The NIC" is the Defense Data Network, Network Information Center (DDN NIC) at SRI International, which is a network information center which holds a primary repository for RFCs and Internet Drafts. The host name is NIC.DDN.MIL. Shadow copies of the RFCs and the Internet Drafts are maintained by the NSFNET on NIS.NSF.NET.

    The DDN NIC also provides various user assistance services for DDN users; contact NIC@NIC.DDN.MIL or call 1-800-235-3155 for more information. In addition, the DDN NIC is the Internet registration authority for the root domain and several top and second level domains; maintains the official DoD Internet Host Table; is the site of the Internet Registry (IR); and maintains the WHOIS database of network users, hosts, domains, networks, and Points of Contact.

    What is the IR?
    The Internet Registry (IR) is the organization that is responsible for assigning identifiers, such as IP network numbers and autonomous system numbers, to networks. The IR also gathers and registers such assigned information. The IR may, in the future, allocate the authority to assign network identifiers to other organizations; however, it will continue to gather data regarding such assignments. At present, the DDN NIC at SRI International serves as the IR.

    What is the IETF?
    The Internet has grown to encompass a large number of widely geographically dispersed networks in academic and research communities. It now provides an infrastructure for a broad community with various interests. Moreover, the family of Internet protocols and system components has moved from experimental to commercial development. To help coordinate the operation, management and evolution of the Internet, the IAB established the Internet Engineering Task Force (IETF).

    The IETF is chaired by Fred Baker and managed by its Internet Engineering Steering Group (IESG). The IETF is a large open community of network designers, operators, vendors, and researchers concerned with the Internet and the Internet protocol suite. It is organized around a set of several technical areas, each managed by a technical area director. In addition to the IETF Chairman, the area directors make up the IESG membership.

    The IAB has delegated to the IESG the general responsibility for making the Internet work and for the resolution of all short- and mid-range protocol and architectural issues required to make the Internet function effectively.

    What is the IRTF?
    To promote research in networking and the development of new technology, the IAB established the Internet Research Task Force (IRTF).

    In the area of network protocols, the distinction between research and engineering is not always clear, so there will sometimes be overlap between activities of the IETF and the IRTF. There is, in fact, considerable overlap in membership between the two groups. This overlap is regarded as vital for cross-fertilization and technology transfer.

    The IRTF is a community of network researchers, generally with an Internet focus. The work of the IRTF is governed by its Internet Research Steering Group (IRSG). The chairman of the IRTF and IRSG is David Clark.

    How do I use the WHOIS program at the DDN NIC?
    To use the WHOIS program to search the WHOIS database at the DDN NIC, TELNET to the NIC host, NIC.DDN.MIL. There is no need to login. Type "whois" to call up the information retrieval program. Next, type the name of the person, host, domain, network, or mailbox for which you need information. If you are only typing part of the name, end your search string with a period. Type "help" for a more in-depth explanation of what you can search for and how you can search. If you have trouble, send a message to NIC@NIC.DDN.MIL or call 1-800-235-3155. Bug reports can be sent to BUG-WHOIS@NIC.DDN.MIL and suggestions for improvements to the program can be sent to SUGGESTIONS@NIC.DDN.MIL.

    How do I become registered in the DDN NIC's WHOIS database?
    If you would like to be listed in the WHOIS database, you must have an electronic mailbox accessible from the Internet. First obtain the file NETINFO:USER-TEMPLATE.TXT. You can either retrieve this file via anonymous FTP from NIC.DDN.MIL or get it through electronic mail. To obtain the file via electronic mail, send a message to SERVICE@NIC.DDN.MIL and put the file name in the subject line of the message; that is, "Subject: NETINFO USER- TEMPLATE.TXT". The file will be returned to you overnight.

    Fill out the name and address information requested in the file and return it to REGISTRAR@NIC.DDN.MIL. Your application will be processed and you will be added to the database. Unless you are an official Point of Contact for a network entity registered at the DDN NIC, the DDN NIC will not regularly poll you for updates, so you should remember to send corrections to your information as your contact data changes.

    How do I use the White Pages at PSI?
    Performance Systems International, Inc. (PSI), sponsors a White Pages Pilot Project that collects personnel information from member organizations into a database and provides online access to that data. This effort is based on the OSI X.500 Directory standard.

    To access the data, TELNET to WP.PSI.COM and login as "fred" (no password is necessary). You may now look up information on participating organizations. The program provides help on usage. For example, typing "help" will show you a list of commands, "manual" will give detailed documentation, and "whois" will provide information regarding how to find references to people. For a list of the organizations that are participating in the pilot project by providing information regarding their members, type "whois -org *".

    For more information, send a message to WP-INFO@PSI.COM.

    How do I use the Knowbot Information Service?
    The Knowbot Information Service is a white pages "meta-service" that provides a uniform interface to heterogeneous white pages services in the Internet. Using the Knowbot Information Service, you can form a single query that can search for white pages information from the NIC WHOIS service, the CSNET WHOIS service, the PSI White Pages Pilot Project, and MCI Mail, among others, and have the responses displayed in a single, uniform format.

    Currently, the Knowbot Information Service can be accessed through TELNET to port 185 on hosts nri.reston.va.us and sol.bucknell.edu. From a UNIX host, use "telnet nri.reston.va.us 185". There is also an electronic mail interface avaliable by sending mail to netaddress at either nri.reston.va.us or sol.bucknell.edu.

    The commands "help" and "man" summarize the command interface. Simply entering a user name at the prompt searches a default list of Internet directory services for the requested information. Organization and country information can be included thorgh the syntax: "userid@organization.country". For example, the queries "droms@bucknell" and "kille@ucl.gb" are both valid. Note that these are not Domain Names, but rather a syntax to specify an organization and a country for the search.

    The default list of directory services currently includes the whois services at the SRI NIC and the CSNET NIC and the white pages service for MCIMail. If an organization is specified, the PSI X.500 service is also searched. Other services can be requested explicitly.

    What is Usenet? What is Netnews?
    Usenet and Netnews are common names of a distributed computer bulletin board system that some computers on the Internet participate in. It is not strictly an Internet service: many computers not on the Internet also participate. Netnews can be a valuable tool to economize what might otherwise be a large volume of traffic from electronic mailing lists.

    How do I get on Usenet? How do I get Netnews on my computer?
    To get on Usenet, you must acquire the software, which is available for some computers at no cost from some anonymous FTP sites across the Internet, and you must find an existing Usenet site that is willing to support a connection to your computer. In many cases, this "connection" merely represents additional traffic over existing Internet access channels.

    What is anonymous FTP?
    Anonymous FTP is a conventional way of allowing you to sign on to a computer on the Internet and copy specified public files from it [3]. Some sites offer anonymous FTP to distribute software and various kinds of information. You use it like any FTP, but the username is "anonymous". Many systems will allow any password and request that the password you choose is your userid. If this fails, the generic password is usually "guest".

    What is "TELNET"?
    The term "TELNET" refers to the remote login that's possible on the Internet because of the TELNET Protocol [9]. The use of this term as a verb, as in "telnet to a host" means to establish a connection across the Internet from one host to another. Usually, you must have an account on the remote host to be able to login to it once you've made a connection. However, some hosts, such as those offering white pages directories, provide public services that do not require a personal account.

    Mailing Lists
    What is a mailing list?
    A mailing list is really nothing more than an alias that has multiple destinations. Mailing lists are usually created to discuss specific topics. Anybody interested in that topic, may (usually) join that list. Some mailing lists have membership restrictions, others have message content restrictions, and still others are moderated. Most large, "public" mailing lists, such as IETF and TCP-IP, have an additional mail address to which requests to be added or deleted may be sent. Usually, these are of the form listname-request.

    There is a "list-of-lists" file available on the host ftp.nisc.sri.com that lists most of the major mailing lists, describes their primary topics, and explains how to subscribe to them. The file is available for anonymous ftp in the netinfo directory as interest-groups (that is, the path is: netinfo/interest-groups). It can also be obtained via electronic mail. Send a message to mail-server@nisc.sri.com with the body of the message reading, "Send netinfo/interest-groups" and the file will be returned in moderate size pieces via electronic mail.

    How do I contact the administrator of a mailing list rather than posting to the entire list?
    For every mailing list mentioned in the "interest-groups" file, there is a description of how to join the list or send other such administrative messages to the person in charge of the list. In general, however, it is usually safe to assume that you can send a message to an address in the format of ListName-request@domain. The convention of having a parallel mailbox conforming to the "-request" format is very widely followed. All administrative messages regarding using, joining, or quitting the list should be sent to that mailbox instead of to the whole list so that the readers of the list don't have to read them.

    What are some good mailing lists or news groups?
    The TCP-IP, IETF, and RFC Distribution lists are primary lists for new Internet users who desire further information about current and emerging developments in the Internet. The first two lists are unmoderated discussion lists, and the latter is an announcement service used by the RFC Editor.

    How do I subscribe to the TCP-IP mailing list?
    To be added to the TCP-IP mailing list, send a message to:

    TCP-IP-REQUEST@NIC.DDN.MIL

    How do I subscribe to the IETF mailing list?
    To be added to the IETF mailing list, send a message to:

    IETF-REQUEST@ISI.EDU

    How do I subscribe to the RFC Distribution list?

    To be added to the RFC Distribution list, send a message to:

    RFC-REQUEST@NIC.DDN.MIL

    Miscellaneous "Internet lore" questions

    What do "btw", "fyi", "imho", "wrt", and "rtfm" mean?
    Often common expressions are abbreviated in informal network postings. These abbreviations stand for "by the way", "for your information", "in my humble [or honest] opinion", "with respect to", and "read the f*ing manual" (with the "f" word varying according to the vehemence of the reader).

    What is the news "FAQ" list?
    This list provides answers to "Frequently Asked Questions" that often appear on various Usenet newsgroups. The list is posted every four to six weeks to the news.announce.newusers group. It is intended to provide a background for new users learning how to use the news. As the FAQ list provide new users with the answers to such questions, it helps keep the newsgroups themselves comparatively free of repetition. Often specific newsgroups will have and frequently post versions of a FAQ list that are specific to their topics.


    Other information is also routinely posted. Here are the subject lines of several general information postings provided on Usenet:

  • Answers to Frequently Asked Questions (the "FAQ" list)
  • Introduction to news.announce
  • Rules for posting to Usenet
  • How to Create a New Newsgroup
  • How to Create a New Trial Newsgroup
  • A Primer on How to Work With the Usenet Community
  • Emily Postnews Answers Your Questions on Netiquette
  • Hints on writing style for Usenet
  • USENET Software: History and Sources
  • List of Active Newsgroups
  • Alternative Newsgroup Hierarchies
  • How to Construct the Mailpaths File
  • Regional Newsgroup Hierarchies
  • List of Moderators
  • Publicly Accessible Mailing Lists
  • List of Periodic Informational Postings
  • How to Get Information about Networks
  • A Guide to Social Newsgroups and Mailing Lists

    Suggested Reading
    For further information about the Internet and its protocols in general, you may choose to obtain copies of the following works:

  • Bowers, K., T. LaQuey, J. Reynolds, K. Roubicek, M. Stahl, and A. Yuan, "Where to Start - A Bibliography of General Internetworking Information", RFC 1175, FYI 3, CNRI, U Texas, ISI, BBN, SRI, Mitre, August 1990.
  • Comer, D., "Internetworking with TCP/IP: Principles, Protocols, and Architecture", Prentice Hall, New Jersey, 1989.
  • Krol, E., "The Hitchhikers Guide to the Internet", RFC 1118, University of Illinois Urbana, September 1989.
    References
    [1] Reynolds, J., and J. Postel, "Assigned Numbers", RFC 1060, USC/Information Sciences Institute, March 1990.
    [2] Postel, J., Editor, "IAB Official Protocol Standards", RFC 1140, Internet Activities Board, May 1990.
    [3] Postel, J., and J. Reynolds, "File Transfer Protocol (FTP), RFC 959, USC/Information Sciences Institute, October 1985.
    [4] Postel, J., "Internet Protocol - DARPA Internet Program Protocol Specification", RFC 791, DARPA, September 1981.
    [5] Postel, J., "Transmission Control Protocol - DARPA Internet Program Protocol Specification", RFC 793, DARPA, September 1981.
    [6] Leiner, B., R. Cole, J. Postel, and D. Mills, "The DARPA Internet Protocol Suite", IEEE INFOCOM85, Washington D.C., March 1985. Also in IEEE Communications Magazine, March 1985. Also as ISI/RS-85-153.
    [7] Cerf, V., "The Internet Activities Board" RFC 1160, CNRI, May 1990.
    [8] Postel, J., "Simple Mail Transport Protocol", RFC 788, USC/Information Sciences Institute, November 1981.
    [9] Postel, J., and J. Reynolds, "TELNET Protocol Specification", RFC 854, USC/Information Sciences Institute, May 1983.
    [10] Postel, J., "Request for Comments on Request for Comments - Instructions to RFC Authors", RFC 1111, USC/Information Sciences Institute, August 1989.

    Answers to Commonly asked "Experienced Internet User" Questions
    Introduction
    During the last few months, several people have monitored various major mailing lists and have extracted questions that are important or commonly asked. This FYI RFC is one of two in a series of FYI's which present the questions and their answers. The first FYI, FYI 4, presented questions new Internet users commonly ask and their answers. The goal of this FYI is to codify the Internet lore so that network operations staff, especially for networks just joining the Internet, will have an accurate and up to date set of references from which to work. Also, redundancies are moved away from the electronic mailing lists so that the lists' subscribers do not have to read the same queries and answers over and over again.

    Although the questions and their responses are taken from various mailing lists, they are presented here loosely grouped by related topic for ease of reading. First the question is presented, then the answer (or answers) as it appeared on the mailing list.

    Sometimes the answers are abridged for better use of space. If a question was not answered on the mailing list, the editors provide an answer. These answers are not distinguished from the answers found on the lists. Sometimes, in order to be as complete as possible, the editors provide additional information that was not present in the original answer. If so, that information falls under the heading "Additional Information".

    The answers are as correct as the reviewers can make them. However, much of this information changes with time. As the FYI is updated, temporal errors will be corrected.

    Many of the questions are in first person, and the answers were directed to the originator of the question. These phrasings have not been changed except where necessary for clarity. References to the correspondents' names have been removed.

    The Q/A mailing lists are maintained by Gary Malkin at FTP.COM. They are used by a subgroup of the User Services Working Group to discuss the Q/A FYIs. They include:

    quail@ftp.com

    This is a discussion mailing list. Its primary use is for pre-release review of the Q/A FYIs.

    quail-request@ftp.com

    This is how you join the quail mailing list.

    quail-box@ftp.com

    This is where the questions and answers will be forwarded-and-stored. It is not necessary to be on the quail mailing list to forward to the quail-box.

    Acknowledgments
    The following people deserve thanks for their help and contributions to this FYI Q/A: Jim Conklin (EDUCOM), John C. Klensin (MIT), Professor Kynikos (Special Consultant), Jon Postel (ISI), Marshall Rose (PSI, Inc.), David Sitman (Tel Aviv University), Patricia Smith (Merit), Gene Spafford (Purdue), and James Van Bokkelen (FTP Software, Inc.).

    Questions about the Internet
    How do I get statistics regarding the traffic on NSFNET?
    Merit/NSFNET Information Services maintains a variety of statistical data at 'nis.nsf.net' (35.1.1.48) in the 'stats' directory. Information includes packet counts by NSS and byte counts for type of use (ftp, smtp, telnet, etc.). Filenames are of the form 'NSFyy-mm.type'.

    Files are available for anonymous ftp; use 'guest' as the password.

    The data in these files represent only traffic which traverses the highest level of the NSFNET, not traffic within a campus or regional network. Send questions/comments to nsfnet-info@merit.edu.

    Questions About Other Networks and Internets
    We have a user who would like to access a machine on "EARN/BITNET". I can't find anything on this in the domain name tables. Please, what is this, and how do I connect to it?
    There are several machines on the Internet that act as gateways between the Internet and BITNET. Two examples are UICVM.UIC.EDU and CUNYVM.CUNY.EDU. You can address a mail message to user%nodename.bitnet@uicvm.uic.edu where the message will be passed from the Internet to BITNET.

    Additional Information:
    These same gateways, known as INTERBIT on the BITNET/EARN side, transfer mail from computers on that network which support SMTP mail headers, onto the Internet. (Many BITNET/EARN computers still do not support SMTP, which is not a part of the IBM protocol used, and it is not possible to send mail from those computers across the gateways into the Internet, in general.)

    BITNET and EARN are the two largest of several cooperating networks which use the IBM RSCS/NJE protocol suite, but are not limited to IBM systems. These independently administered, interconnected networks function as a single, worldwide network directly connecting more than 3,300 computers in about 1,400, mostly higher-education, organizations worldwide. This worldwide network supports electronic mail, including mailing lists, sender-initiated file transfer, and short "interactive" messages.

    BITNET, frequently used (outside of Europe) to refer to the whole worldwide network, technically refers to that portion in the United States, plus sites in other countries which are connected through the United States and do not have their own separately administered cooperating networks. More than 550 organizations in the U.S. participate in BITNET.

    EARN is the European Academic Research Network. EARN links more than 500 institutions in Europe and several surrounding countries.

    BITNET and CSNET merged organizationally on October 1, 1990, to form CREN, the Corporation for Research and Educational Networking. The two networks remain separate at the operational level level, however. (EARN and the other Cooperating Networks were not involved in this merger.)

    Questions About Internet Documentation
    Where do I get information regarding ordering documents related to GOSIP?
    The complete information as issued by NIST is available online on the NIC.DDN.MIL host as PROTOCOLS:GOSIP-ORDER-INFO.TXT. The file contains pointers to contact people, ordering addresses, prices, and, in some cases, online pathnames, for various GOSIP related documents. In addition, the information as of August 1990 was published as an appendix to RFC 1169, "Explaining the Role of GOSIP" [1].

    Questions About Domain Name System (DNS)
    Is there a DNS Query server?
    Actually, what you are looking for is the service that host 128.218.1.109 provides on port 5555 - you simply connect to that host at that port, type in a fully qualified domain name and it responds with an internet address and closes the connection. I used it when I had a host that still only had /etc/hosts and it did just what I needed - which was basically a manual nslookup.

    However, the vast majority of users will find it simpler to just use a DNS query tool and ask the DNS directly. This doesn't require much sophistication, and does allow the user to see how short names are expanded at the user's site rather than at 128.218.1.109 (wherever that is). For example, suppose a user wants to find out the address of a fully-qualified domain name "X.MISKATONIC.EDU", and also see what host and address are used when "Z" is typed as a host name.

    Assuming the user is on a UNIX host and has a copy of the dig program, type:

    dig x.miskatonic.edu and dig z

    and the answers will appear. You are now on your way to becoming a DNS expert. There are other UNIX alternatives, e.g., nslookup, and similar programs for non-UNIX systems. Your local DNS guru certainly has one or more of these tools, and although they are often kept from the public, they are really quite easy to use for simple cases.

    We have been having a frequent BIND failure on both our VAX and Solbourne that is traced to TCP domain queries from an IBM NSMAIN nameserver running in cache mode (UDP queries do not cause this problem, though it is usually a UDP resolution that is active upon the crash -- this resolution is an innocent victim).

    I have discovered that something is trashing the hash areas (sometimes even as it is being recursively used in a resolution). Also, occasionally the socket/file descriptor for the TCP connection is changed to invalid entries causing a reply write fail (though this is not necessarily fatal, and the rest of the structure is not apparently altered).

    Has any one else had frequent BIND failures (especially major domain sites that have heavy TCP domain loads)?
    In both the case of BIND and the IBM implementation, often called FAL, there are multiple versions, with older versions being truly bad. Upgrade to recent version before exploring further.

    BIND has always had a problem with polluting its own database. These problems have been related to TCP connections, NS RRs with small TTLs, and several other causes. Experience suggests that the style of bug fixing has often been that of reducing the problem by 90% rather than eliminating it.

    IBM's support for the DNS (outside of UNIX systems) is interesting in its techniques, encouraging in its improvement, but still somewhat depressing when compared to most other DNS software. IBM also uses terminology that varies somewhat from the usual DNS usage and preserves some archaic syntax, e.g., "..".

    The combination of an old BIND and an old IBM server is just plain unpleasant.

    Is the model used by the domain name system for host names that the owner of a name gets to choose its case?
    The model used by the DNS is that you get to control at a specific point in the name space, and are hence free to select case as you choose, until points where you in turn give away control. As a practical matter, there are several implementations that don't do the right thing. IBM implementations often map everything into a single case.

    According to RFC 1034 [2], section 4.2.1, one should not have to code glue RR's for name server's names unless they are below the cut. When I don't put glue RR's in, and do a query for NS records, the "additional" field is left blank. As far as I can tell, all other zones I query for NS records have this filled with the IP addresses of the NS hosts.

    Is this required or should I not be concerned that the additional field is empty?
    The protocol says that an empty additional field is not a problem when the name server's name is not "below" the cut.

    In practice, putting in the glue where it is not required can cause problems if the servers named in the glue are used for several zones. This is broken behavior in BIND. Not putting in glue can cause other problems in BIND, usually when the server name is difficult to resolve. So, the bottom line is to put glue in only when required, and don't use aliases or anything else tricky when it comes to identifying name servers.

    Questions About Network Management Implementations
    In reading the SNMP RFCs [3,4,5,6] I find mention of authentication of PDUs. Are there any standards for authentication mechanisms?
    There is a working group of the IETF that is working on this problem. They are close to a solution, but nothing has yet reached RFC publication yet. Expect something solid and implementable by October of 1991.

    Can vendors make their enterprise-specific variables available to users through a standard distribution mechanism?
    Yes. But before someone submits a MIB, they should check it out themselves.

    On uu.psi.com in pilot/snmp-wg/, there are two files

  • mosy-sparc-4.0.3.c
  • mosy-sun3-3.5

    The first will run on a Sun-Sparc, the second will run on a Sun-3. After retrieving one of these files in BINARY mode via anonymous FTP, the submittor can run their MIB through it, e.g., % mosy mymib.my

    Once your MIB passes, send it to: mib-checker@isi.edu

    If everything is OK, the mib-checker will arrange to have it installed in the /share/ftp/mib directory on venera.isi.edu. Note: This processing does not offer an official endorsement. The documents submitted must not be marked proprietary, confidential, or the like.

    I have a question regarding those pesky octet strings again. I use the variable-type field of the Response pdu to determine how the result should be displayed to the user. For example, I convert NetworkAddresses to their dotted decimal format ("132.243.50.4"). I convert Object Identifiers into strings ("1.3.6.1.2....").

    I would LIKE to just print Octet Strings as strings. But, this causes a problem in such cases as atPhysAddress in which the Octet string contains the 6 byte address instead of a printable ASCII string. In this case, I would want to display the 6 bytes instead of just trying to print the string.

    Does anyone have a suggestion as to how I can determine whether I can just print the string or whether I should display the octet bytes?
    * Remember: I want to support enterprise specific variables too.

    In general, there is no way that you can tell what is inside an OCTET STRING without knowing something about the object that the OCTET STRING comes from. In MIB-II [6], some objects are marked as DisplayString which has the syntax of OCTET STRING but is restricted to characters from the NVT ASCII character set (see the TELNET Specification, RFC 854 [7], for further information). These objects are:

  • sysDescr
  • sysContact
  • sysName
  • sysLocation
  • ifDescr If you want to be able to arbitrarily decide how to display the strings, without knowing anything about the object, then you can scan the octets, looking for any octet which is not printable ASCII. If you find at least one, you can print the entire string, octet by octet, in "%02x:" notation. If all of the octets are printable ASCII, then you can just printf the string.

    If archived MIBs must be 1155-compatible [3], it would be nice if those who submit them check them first.

    Where are these MIB tools available for public FTP?
    Ideally, a simple syntax checker (that didn't actually generate code) would be nice.

    In the ISODE 6.0 release there is a tool called MOSY which recognizes the 1155 syntax and produces a flat ASCII file. If you can run it through MOSY without problems then you are OK.

    Suppose I want to create a private MIB object for causing some action to happen, say, do a reset.
    Should the syntax or this object specify a value such as:

    Syntax:
    INTEGER {
    perform reset (1),
    }

    even though there is only a single value? Or, is it ok to just allow a Set on this object with any value to perform the desired action? If the later, how is this specified?

    For our SNMP manageable gizmos and doohickies with similar "action" type MIB variables, I've defined two values

    Syntax:
    INTEGER {
    reset(1)
    not-reset(2)
    } 

    And defined behavior so that the only valid value that the variable may be set to is "reset" (which is returned in the get response PDU) and at all other times a get/getnext will respond with "not-reset".

    Questions about Serial Line Internet Protocol (SLIP) and Point-to-Point Protocol (PPP) Implementations
    I seem to recall hearing that SLIP [8] will only run on synchronous serial lines. Is this true? ...
    Is there something about SLIP which precludes it's being implemented over async lines?

    Other way around: SLIP is designed for async lines and is not a good fit on sync lines. PPP [9, 10] works on either, and is what you should be implementing if you're implementing something.

    Since we are very interested in standards in this area, could someone tell me were I can find more information on PPP?
    Also, can this protocol be used in other fields than for the Internet (i.e., telecontrol, telemetering) where we see a profusion of proprietary incompatible and hard to maintain Point-to-Point Protocols?

    PPP was designed to be useful for many protocols besides just IP. Whether it would be useful for your particular application should probably be discussed with the IETF's Point-to-Point Protocol Working Group discussion list.

    For general discussion:

    ietf- ppp@ucdavis.edu.

    To subscribe:

    ietf-ppp-request@ucdavis.edu

    The PPP specification is available as RFC 1171 [9], and a PPP options specification is available as RFC 1172 [10].

    In UnixWorld of April 1990 (Vol. VII, No. 4, Pg. 85), Howard Baldwin writes:

    "Point-to-Point Protocol (PPP) has just been submitted to the CCITT from the Internet Engineering Task Force. It specifies a standard for encapsulating Internet Protocol data and other network layer (level three on ISO's OSI Model) protocol information over point-to-point links; it also provides ways to test and configure lines and the upper level protocols on the OSI Model. The only requirement is a provision of a duplex circuit either dedicated or switched, that can operate in either an asynchronous or synchronous mode, transparent to the data-linklayer frame.
    "According to Michael Ballard, director of network systems for Telebit, PPP is a direct improvement upon Serial Line Internet Protocol (SLIP), which had neither error correction nor a way to exchange network address."

    Does anyone know if there is a way to run a SLIP program on a IBM computer running SCO Xenix/Unix, with a multi-port serial board?
    SCO TCP/IP for Xenix supports SLIP. It works. However, be warned: SCO SLIP works *only* with SCO serial drivers, so it will *not* work with intelligent boards that come with their own drivers. If you want lots of SLIP ports, you'll need lots of dumb ports, perhaps with a multi-dumb-port board.

    Here's the setup

    -- SunOS 3.5, with the 4.3BSD TCP, IP & SLIP distributions installed. Slip is running between the "ttya" ports of two Sun 3/60's. "ping", "rlogin", etc., works fine, but a NFS mount results in "server not responding: RPC Timed Out".

    SunOS 3.5 turns the UDP checksum off, which is legal and works okay over interfaces such as ethernet which has link- level checksumming. On the other hand, SLIP doesn't perform checksums thus running NFS over SLIP requires you to turn the UDP checksum on. Otherwise, you'll experience erratic behavior such as the one described above.

    Save the older kernel and try,

    % adb -k -w /vmunix /dev/kmem udpcksum?w 1

    to patch up the kernel.

    Questions About Routing
    Some postings mentioned "maximum entropy routing". Could someone please provide a pointer to on-line or off-line references to this topic?
    Try NYU CSD Technical Report 371: "Some Comments on Highly Dynamic Network Routing," by Herbert J. Bernstein, May 1988.

    Other Protocol and Standards Implementation Questions
    Does anyone recognize ethernet type "80F3"?
    I don't see it in RFC 1010, but I am seeing it on our net.

    Ethernet type 0x80F3 is used by AppleTalk for address resolution. You must have Macs on your network which are directly connected to Ethernet. These packets are used by the Mac (generally at startup) to determine a valid AppleTalk node number.

    Additional Information:
    RFC 1010 is obsolete. Please consult RFC 1060 [11], the current "Assigned Numbers" (issued March 1990), which does list "80F3":

    Does anyone know the significance of a high value for "Bad proto" in the output from netstat on Unix machines using ethernet?
    We're seeing values in the tens of thousands out of a few hundred thousand packets sent/received in all. Some "Bad proto" values are negative, too. (Off the scale?) Any help would be appreciated.

    This probably indicates that you are getting tens of thousands of broadcast packets from some host or hosts on your network. You might want to buy or rent a LAN monitor, or install one of the public-domain packages to see what private protocol is guilty. "FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices" (RFC 1147, FYI 2), [12] contains pointers to tools that may help you zero in on the problem.

    Which RFC would explain the proper way to configure broadcast addresses when using subnets?
    Consult RFC 1122, "Requirements for Internet Hosts -- Communication Layer" [13].

    Can anyone tell me what .TAR files exactly are?
    Is it like ZIP or LZH for the IBM PC's? IF so, how do I go about getting a compressor/decompressor for .TAR files and what computer does this run on?

    TAR stands for "Tape ARchive". It is a Unix utility which takes files, and directories of files, and creates a single large file. Originally intended to back up directory trees onto tape (hence the name), TAR is also used to combine files for easier electronic file transfer.

    Suggested Reading
    For further information about the Internet and its protocols in general, you may choose to obtain copies of the following works:

  • Bowers, K., T. LaQuey, J. Reynolds, K. Roubicek, M. Stahl, and A. Yuan, "Where to Start - A Bibliography of General Internetworking Information", RFC 1175, FYI 3, CNRI, U Texas, ISI, BBN, SRI, Mitre, August 1990.
  • Braden, R., Editor, "Requirements for Internet Hosts -- Communication Layer", RFC 1122, Internet Engineering Task Force, October 1989.
  • Braden, R., Editor, "Requirements for Internet Hosts -- Application and Support", RFC 1123, Internet Engineering Task Force, October 1989.
  • Comer, D., "Internetworking with TCP/IP: Principles, Protocols, and Architecture", Prentice Hall, New Jersey, 1989.
  • Frey, D. and R. Adams, "!%@:: A Directory of Electronic Mail Addressing and Networks", O'Reilly and Associates, Newton, MA, August 1989.
  • Krol, E., "The Hitchhikers Guide to the Internet", RFC 1118, University of Illinois Urbana, September 1989.
  • LaQuey, T, Editor, "Users' Directory of Computer Networks", Digital Press, Bedford, MA, 1990.
  • Malkin, G., and A. Marine, "FYI on Questions and Answers - Answers to Commonly asked "New Internet User" Questions", RFC 1206, FYI 4, FTP Software, Inc., SRI, February 1991.
  • Postel, J., Editor, "IAB Official Protocol Standards", RFC 1140, Internet Activities Board, May 1990.
  • Quarterman, J., "Matrix: Computer Networks and Conferencing Systems Worldwide", Digital Press, Bedford, MA, 1989.
  • Reynolds, J., and J. Postel, "Assigned Numbers", RFC 1060, USC/Information Sciences Institute, March 1990.
  • Socolofsky, T., and C. Kale, "A TCP/IP Tutorial", RFC 1180, Spider Systems Limited, January 1991.
  • Stevens, W., "UNIX Network Programming", ISBN 0-13-949876-1, Prentice Hall, Englewood Cliffs, NJ, 1990.
  • Stine, R., Editor, "FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices" RFC 1147, FYI 2, Sparta, Inc., April 1990. References
    [1] Cerf, V., and K. Mills, "Explaining the Role of GOSIP", RFC 1169, IAB, NIST, August 1990.
    [2] Mockapetris, P., "Domain Names - Concepts and Facilities", RFC 1034, USC/Information Sciences Institute, November 1987.
    [3] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", RFC 1155, Performance Systems International, Hughes LAN Systems, May 1990.
    [4] McCloghrie, K., and M. Rose, "Management Information Base for Network Management of TCP/IP-based internets", RFC 1156, Hughes LAN Systems, Performance Systems International, May 1990.
    [5] Case, J., M. Fedor, M. Schoffstall, and J. Davin, "A Simple Network Management Protocol (SNMP)", RFC 1157, SNMP Research, Performance Systems International, Performance Systems International, MIT Laboratory for Computer Science, May 1990.
    [6] Rose, M., Editor, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", RFC 1158, Performance Systems International, May 1990.
    [7] Postel, J., and J. Reynolds, "TELNET Protocol Specification", RFC 854, USC/Information Sciences Institute, May 1983.
    [8] Romkey, J., "A Nonstandard for Transmission of IP Datagrams over Serial Lines: SLIP", RFC 1055, June 1988.
    [9] Perkins, D., "The Point-to-Point Protocol: A Proposal for Multi- Protocol Transmission of Datagrams Over Point-to-Point Links", RFC 1171, CMU, July 1990.
    [10] Perkins, D., and R. Hobby, "The Point-to-Point Protocol (PPP) Initial Configuration Options", CMU, UC Davis, July 1990.
    [11] Reynolds, J., and J. Postel, "Assigned Numbers", RFC 1060, USC/Information Sciences Institute, March 1990.
    [12] Stine, R., Editor, "FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices" RFC 1147, FYI 2, Sparta, Inc., April 1990.
    [13] Braden, R., Editor, "Requirements for Internet Hosts -- Communication Layer", RFC 1122, Internet Engineering Task Force, October 1989.

    Security Considerations
    Security issues are not discussed in this memo.

    Authors' Addresses

    Gary Scott Malkin
    FTP Software, Inc.
    26 Princess Street
    Wakefield, MA 01880
    Phone: (617) 246-0900
    EMail: gmalkin@ftp.com

    April N. Marine
    SRI International
    Network Information Systems Center
    333 Ravenswood Avenue, EJ294
    Menlo Park, CA 94025
    Phone: (415) 859-5318
    EMail: APRIL@nic.ddn.mil

    Joyce K. Reynolds
    USC/Information Sciences Institute
    4676 Admiralty Way
    Marina del Rey, CA 90292-6695
    Phone: (213) 822-1511
    EMail: jkrey@isi.edu