ConneXions, Interop, Inc., Mountain View, CA.
ConneXions - The Interoperability Report is published monthly and
covers the computer and communications industry, with special
emphasis on networking protocols such as TCP/IP and OSI. The
articles are written by the experts in the field and are typically
tutorial in nature. For more information, contact Interop, Inc.,
480 San Antonio Road, Suite 100, Mountain View, CA 94040. (415)
941-3399.
LinkLetter, Merit Computer Network/NSFNET Information Services, Ann
Arbor, MI.
This newsletter is a publication of the Merit Computer Network,
managers of the NSFNET backbone project. The Link Letter focuses
on the NSFNET backbone project and is available electronically and
via hard copy. To subscribe, send electronic mail to NSFNET-
Linkletter-Request@merit.edu.
Merit Network News, MERIT, Inc., Ann Arbor, MI.
This newsletter is a free, quarterly publication of the Merit
Computer Network, Michigan's regional computer network. The Merit
Network News publishes information and documentation on the
network itself, features articles about the computing environments
at the Merit member institutions, and provides information about
recent developments in networking technology. Merit News is
available electronically or via hard copy. To subscribe, send
electronic mail with your preferred method and addresses to
Info@merit.edu, or contact Merit at (313) 764-9430.
NEARnet Newsletter, NEARnet, Cambridge, MA.
The NEARnet Newsletter is a bimonthly publication for users of the
New England Academic and Research Network (NEARnet) and others
interested in academic and research networking. This newsletter
contains articles about useful network applications and projects,
NEARnet services, member organizations, and plans for the future.
To subscribe, send electronic mail to nearnet-staff@nic.near.net,
or contact NEARnet, BBN Systems and Technologies Corporation, 10
Moulton Street, Cambridge, MA 02138, Attn: Deborah Doyle MS 6/3A.
NorthWestNet News, University Computing Services, University of
Washington, Seattle, WA.
This short monthly newsletter is intended primarily for member
institutions of NWNET. The newsletter contains information of
interest to users and staff of these institutions, with an
emphasis upon announcing training opportunities in supercomputing
and networking, upcoming NWNET meetings, and resources available
to NWNET users. To subscribe, send electronic mail (for hard copy
or on-line) to kochmer@uwavm.acs.washington.edu.
NSF Network News, NSF Network Service Center, Cambridge, MA.
A newsletter published by the NSF Network Service Center
approximately every 5 months. Its mission is to disseminate
general information about NSFNET, its architecture, its protocols
and its users. The newsletter also includes a map, showing all
sites attached to NSFNET and its regional networks at the time of
publication. To subscribe, send electronic mail to
nnsc@nnsc.nsf.net or contact NNSC, BBN Systems & Technologies, 10
Moulton St., Cambridge, MA 02138.
NYSERNet News, PSI, Inc., Reston, VA.
This bi-monthly newsletter supplies the user with information on
using the Internet, reports on ongoing NYSERNet activities and
network growth and commentary on current technical issues. To
subscribe, send electronic mail to info@psi.com, or contact
NYSERNet News, PO Box 3850, Reston, VA 22091. (703) 620-6651.
UIUCnet Newsletter, University of Illinois Computing Services Office,
Urbana, IL.
The UIUCnet newsletter provides timely information about campus
network issues. It covers new developments in campus networking
in addition to providing tutorials and in-depth articles about
both national networking and networking at the University of
Illinois. Postscript versions (that are compressed) of the
UIUCnet Newsletter are available on-line on host uxc.cso.uiuc.edu,
directory UIUCnet. To subscribe, send electronic mail to
uiucnet@uiuc.edu, or contact UIUCnet, Computing Services Office,
1304 W. Springfield Ave., Urbana, IL 61801.
10. REPORTS AND PAPERS
Deutsch, Debra, An Introduction to the X.500 Series Network Directory
Service, 13 pgs., BBN Systems & Technologies Corporation, Cambridge,
MA, June 1988.
This paper introduces the concepts and function of the Directory
Services specified in the X.500 series and outlines how the CCITT
and ISO have approached the associated technical issues. The
discussion is at a fairly high level, but does assume a knowledge
of networking concepts. It begins with an explanation of the
model and concepts used in the standard; describes the services
provided and the protocols that implement those services;
describes some of the kinds of names and objects that the CCITT
and ISO anticipate will appear in the database; and ends with a
discussion of some issues that CCITT and ISO are expected to
address in the near- to mid-future. Available by sending
electronic mail to Debra Deutsch, ddeutsch@bbn.com.
EDUCOM Networking and Telecommunications Task Force, The National
Research and Education Network: A Policy Paper, 10 pgs., EDUCOM,
Washington, DC, April 1989.
This paper is based on conclusions reached at an EDUCOM NTTF
national network workshop attended by representatives of
government, education and industry on January 23-24, 1989 and from
recommendations of task force committees. It addresses the goal
and benefits of the NREN, access to the network and network
services, and issues surrounding research and development. It
also presents a model for network structure and management, and
network financing. This document can be ordered by sending
electronic mail to nttf@educom.edu, or contacting EDUCOM, 1112
16th Street NW, Suite 600, Washington, DC 20036, (202) 872-4200.
EDUCOM Networking and Telecommunication Task Force, A National Higher
Education Network: Issues and Opportunities, 19 pgs., EDUCOM,
Princeton, NJ, May 1987.
This paper is the first in a series of documents addressing the
urgent need for a coordinated national highspeed computer network
linking academic institutions, federal research laboratories,
library resources, and industrial partners. Appendix 1 contains a
statement by the President of EDUCOM to the Science, Research and
Technology Subcommittee of the US House of Representatives. This
document can be ordered by sending electronic mail to
nttf@educom.edu, or contacting EDUCOM, 1112 16th Street NW, Suite
600, Washington, DC 20036. (202) 872-4200.
Federal Coordinating Council for Science, Engineering, and Technology
(FCCSET), A Research and Development Strategy for High Performance
Computing, 29 pgs., Office of Science and Technology Policy,
Washington, DC, Nov 20 1987.
Prepared by the FCCSET Committee on Computer Research and
Applications, this report is the result of a systematic review of
the status and directions of high performance computing and its
relationship to federal R&D. It contains both a summary of
findings and a summary of recommendations addressing high
performance computers, software technology and algorithms,
networking and basic research and human resources. This document
was released by the Executive Office of the President, Office of
Science and Technology Policy, Washington, DC 20506. To order,
call OSTP Publications at (202) 395-7347.
Federal Research Internet Coordinating Committee, Draft Program Plan
for the National Research and Education Network, 25 pgs., Federal
Research Internet Coordinating Committee (FRICC), Washington, DC, May
1989.
This report is the final draft of a joint agency program plan to
develop a National Research and Education Network (NREN). It
addresses the concerns identified in the review conducted by the
ad hoc committee of the National Research Council, as documented
in the report "Toward A National Research Network". It details
steps to be taken by the Federal government to establish the NREN
and covers the first five years of the expected ten year
development path. For more information, contact the Federal
Research Internet Coordinating Committee, US Dept. of Energy,
Office of Scientific Computing ER-7, Washington, DC 20545.
Hedrick, Charles L., Introduction to the Internet Protocols, 34 pgs.,
Rutgers University Computer Science Facilities Group, Piscataway, NJ,
July 3, 1987.
This paper give an introduction to the Internet networking
protocols (TCP/IP). It includes a summary of the facilities
available and brief descriptions of the major protocols in the
family. Available on-line on host topaz.rutgers.edu, directory
pub/tcp-ip-docs, filenames tcp-ip-intro.1 and tcp-ip- intro.2.
Hedrick, Charles L., Introduction to Administration of an Internet-
base Local Network, 46 pgs., Rutgers University Computer Science
Facilities Group, Piscataway, NJ, July 24, 1988.
This document is written for people who intend to set up or
administer a network based on the Internet networking protocols
(TCP/IP). Available on-line on host athos.rutgers.edu, directory
runet, filename tcp-ip-admin.doc or tcp-ip-admin.ps (.doc is in
ascii format and .ps is in postscript format).
National Research Council, Toward a National Research Network, 55
pgs., National Academy Press, Washington, DC, 1988.
This report was prepared by the National Research Network Review
Committee (NRNRC) on the proposed establishment of a high-
performance national computer network for researchers. Three sets
of issues are examined: the technical feasibility of the network
proposals developed by the Committee on Computer Research and
Applications of the Federal Coordinating Council for Science,
Engineering and Technology (FCCSET); the utility of the proposed
network to the research community; and developments in computer
technology that might encroach upon the proposed network and
associated services. The committee's findings with issues and
recommendations are presented in this report. This document is
available from the Computer Science and Technology Board, 2101
Constitution Ave. NW, Washington, DC 20418.
Raveche, Harold J., Duncan H. Lawrie, and Alvin M. Despain, A
National Computing Initiative, The Agenda for Leadership, 77 pgs.,
Society for Industrial and Applied Mathematics, Philadelphia, PA,
February 1987.
In response to congressional inquiries and urged on by the
extraordinary opportunities created by rapid developments in
high-performance computing, the Federal Coordinating Council on
Science, Engineering and Technology (FCCSET) recommended that
several federal agencies convene expert panels to assess high-
performance computing. In attendance were 45 recognized leaders
from industry, academe and national laboratories. In three
separate sub-panels, they considered the steps necessary to grasp
the opportunities and face the challenges of the next decade: in
particular, to maintain U.S. leadership in computing technology
and the strengthening of our competitive position vis-a-vis our
trading partners. The three sub-panel reports follow an executive
summary of the workshop. For copies, contact Society for
Industrial and Applied Mathematics, 1400 Architects Building, 117
South 17th Street, Philadelphia, PA 19103-5052.
Reynolds, Joyce K., The Helminthiasis of the Internet, 33 pgs.
(77,033 bytes), USC/Information Sciences Institute, Marina del Rey,
CA, December 1989.
This report looks back at the helminthiasis (infestation with, or
disease caused by parasitic worms) of the Internet that was
unleashed the evening of 2 November 1988. It provides information
about an event that occurred in the life of the Internet. This
document provides a glimpse at the infection, its festering, and
cure. The impact of the worm on the Internet community, ethics
statements, the role of the news media, crime in the computer
world, and future prevention is discussed. A documentation review
presents four publications that describe in detail this particular
parasitic computer program. Reference and bibliography sections
are also included. Available on-line on host nic.ddn.mil,
directory RFC, filename RFC1135.TXT.
Shapiro, Norman Z. and Robert H. Anderson, Toward an Ethics and
Etiquette for Electronic Mail, 50 pgs., The Rand Corporation, Santa
Monica, CA, July 1985.
This report, prepared for the National Science Foundation,
provides important general attributes of electronic mail systems,
computers, or communications systems, and the effects of those
attributes on the quality and appropriateness of communication.
Hard copies may be obtained, for a fee, from: Publications
Distribution Services, The RAND Corporation, P.O. Box 2138, Santa
Monica, CA 90406-2138.
U.S. General Accounting Office, Computer Security - Virus Highlights
Need for Improved Internet Management, 36 pgs., United States General
Accounting Office, Washington, DC, 1989.
This report (GAO/IMTEC-89-57), by the U.S. Government Accounting
Office, describes the worm and its effects. It gives a good
overview of the various U.S. agencies involved in the Internet
today and their concerns vis-a-vis computer security and
networking. Available on-line on host nnsc.nsf.net, directory
pub, filename GAO_RPT; and on nis.nsf.net, directory nsfnet,
filename GAO_RPT.TXT.
11. REQUEST FOR COMMENTS (RFC)
11.a The Request for Comments Document Series
The 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.
Most RFCs are the descriptions of network protocols or services,
often giving detailed procedures and formats providing the
information necessary for creating implementations. Other RFCs
report on the results of policy studies or summarize the work of
technical committees or workshops.
Note: Currently, all 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 RFCEditor. The RFCEditor
is Jon Postel (Postel@ISI.EDU).
While RFCs are not refereed publications, they do receive technical
review from either the task forces, individual technical experts, or
the RFCEditor, as appropriate.
RFCs are distributed on-line by being stored as public access files,
and a short message is sent to the RFCdistribution list (RFC-
REQUEST@NIC.DDN.MIL) indicating the availability of the memo.
The on-line files are copied by the interested people and printed or
displayed at their site on their equipment. An RFCmay also be
returned via email in response to an email query. RFCs can be
obtained via FTP from NIC.DDN.MIL, with the pathname RFC:RFCnnnn.TXT
(where "nnnn" refers to the number of the RFC). Login with FTP,
username "anonymous", password "guest".
The DDN Network Information Center (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 RFCnumber, as in "Subject: RFCnnnn".
RFCs can also be contained via FTP from NIS.NSF.NET. Using FTP,
login with username "anonymous", and password "guest"; then connect
to the RFCdirectory (cd RFC). The file name is of the form
RFCnnnn.TXT-1 (where "nnnn" refers to the number of the RFC).
The NSFNet Network Information Service (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 RFCnumber.
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 RFCnumber and published, that RFCis
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 RFCon a
particular protocol.
The Internet Activities Board (IAB) published the "IAB Official
Protocol Standards" (currently RFC-1140), which describes the state
of standardization of protocols used in the Internet. This document
is issued quarterly. Current copies may be obtained from the DDN
Network Information Center or from the Internet Assigned Numbers
Authority. Please refer to the latest edition of the "IAB Protocol
Standards" RFCfor current information on the state and status of
standard Internet protocols.
The complete set of all RFCs issued is maintained at, and available
from, the DDN Network Information Center at SRI International. For
further information, phone: 1-800-235-3155 (E-mail: NIC@NIC.DDN.MIL).
Subsets of this master set (shadow copies) are maintained at MERIT
and CSNET. Use of the RFCrepositories at these sites may be more
suitable to your network connectivity requirements. Please note,
however, that the NIC.DDN.MIL is the central repository and will
contain the most up-to-date set of RFCs.
11b. Key Basic Beige RFCAbstracts
The following material is organized as abstracts of key "Basic Beige"
RFCs. Please see RFC1140 for an explanation of the Internet
Standards process and the definitions of the terms (e.g., Recommended
versus Required).
RFC-768 User Datagram Protocol (UDP)
A Recommended Standard Protocol. Provides a datagram service to
applications. Adds port addressing to the IP services.
RFC-791 Internet Protocol (IP)
A Required Standard Protocol. This is the universal protocol of
the Internet. This datagram protocol provides the universal
addressing of hosts in the Internet.
RFC-792 Internet Control Message Protocol (ICMP)
A Required Standard Protocol. The control messages and error
reports that go with the Internet Protocol.
RFC-793 Transmission Control Protocol (TCP)
A Recommended Standard Protocol. Provides reliable end-to-end
data stream service.
RFC-821 Simple Mail Transfer Protocol (SMTP)
A Recommended Standard Protocol. The procedure for transmitting
computer mail between hosts.
RFC-822 Standard for the Format of ARPA Internet Text
Messages
A Recommended Standard Protocol. Defines the standard for the
format of Internet text messages.
RFC-826 Ethernet Address Resolution Protocol
An Elective Network Specific Standard Protocol. This is a
procedure for finding the network hardware address corresponding
to an Internet Address.
RFC-854 Telnet Protocol
A Recommended Standard Protocol. The protocol for remote terminal
access.
RFC-862 Echo Protocol
A Recommended Standard Protocol. Debugging protocol, sends back
whatever you send it.
RFC-894 A Standard for the Transmission of IP
Datagrams over Ethernet Networks
An Elective Network Specific Standard Protocol. A standard method
of encapsulating Internet Protocol datagrams on a Ethernet.
RFC-904 Exterior Gateway Protocol
A Recommended Standard Protocol. The protocol used between
gateways of different administrations to exchange routing
information.
RFC-919 Broadcasting Internet Datagrams
A Required Standard Protocol. A protocol of simple rules for
broadcasting Internet datagrams on local networks that support
broadcast, for addressing broadcasts, and for how gateways should
handle them. Recommended in the sense of "if you do broadcasting
at all, then do it this way".
RFC-922 Broadcasting Internet Datagrams in the Presence
of Subnets
A Required Standard Protocol. A protocol of simple rules for
broadcasting Internet datagrams on local networks that support
broadcast, for addressing broadcasts, and for how gateways should
handle them. Recommended in the sense of "if you do broadcasting
with subnets at all, then do it this way".
RFC-950 Internet Standard Subnetting Procedure
A Required Standard Protocol. This is a very important feature
and must be included in all IP implementations. Specifies
procedures for the use of subnets, which are logical sub-sections
of a single Internet network.
RFC-951 Bootstrap Protocol (BOOTP)
A Recommended Draft Standard Protocol. This proposed protocol
provides an IP/UDP bootstrap protocol which allows a diskless
client machine to discover its own IP address, the address of a
server host, and the name of a file to be loaded into memory and
executed.
RFC-959 File Transfer Protocol (FTP)
A Recommended Standard Protocol. The protocol for moving files
between Internet hosts. Provides for access control and
negotiation of file parameters.
RFC-1000 The Request for Comments Reference Guide
The RFCReference Guide provides a historical account of the
Request for Comments series of documents by categorizing and
summarizing of the Request for Comments numbers 1 through 999
issued between the years 1969-1987. These documents have been
crossed referenced to indicate which RFCs are current, obsolete,
or revised.
RFC-1009 Requirements for Internet Gateways
A Required Standard Protocol. An official specification for the
Internet community. This RFCsummarizes the requirements for
gateways to be used between networks supporting the Internet
protocols. This document is a formal statement of the
requirements to be met by gateways used in the Internet system.
RFC-1011 Official Internet Protocols
A Required Standard Memo. This RFCis an official status report
on the protocols used in the Internet community. It identifies
the documents specifying the official protocols used in the
Internet. Comments indicate any revisions or changes planned.
RFC-1012 Bibliography of Request for Comments 1 through
999
This RFCis a reference guide for the Internet community which
provides a bibliographic summary of the Request for Comments
numbers 1 through 999 issued between the years 1969-1987.
RFC-1034 Domain Names - Concepts and Facilities
A Recommended Standard Protocol. This RFCis the revised basic
definition of The Domain Name System. It obsoletes RFC-882. This
memo describes the domain style names and their use for host
address look up and electronic mail forwarding. It discusses the
clients and servers in the domain name system and the protocol
used between them.
RFC-1035 Domain Names - Implementation
A Recommended Standard Protocol. This RFCis the revised
specification of the protocol and format used in the
implementation of the Domain Name System. It obsoletes RFC-883.
This memo documents the details of the domain name client - server
communication.
RFC-1042 A Standard for the Transmission of IP
Datagrams over IEEE 802 Networks
An Elective Network Specific Standard. This RFCspecifies a
standard method of encapsulating the Internet Protocol (IP)
datagrams and Address Resolution Protocol (ARP) requests and
replies on IEEE 802 Networks to allow compatible and interoperable
implementations.
RFC-1048 BOOTP Vendor Information Extensions
A Recommended Draft Standard. This memo proposes an addition to
the Bootstrap Protocol (BOOTP).
RFC-1058 Routing Information Protocol
An Elective Draft Standard Proposed Protocol. This RFCdescribes
an existing protocol for exchanging routing information among
gateways and other hosts. It is intended to be used as a basis
for developing gateway software for use in the Internet community.
RFC-1060 Assigned Numbers
A Required Standard Memo. This RFCis an official status report
on the numbers used in protocols in the Internet community. It
documents the currently assigned values from several series of
numbers including link, socket, port, and protocol, used in
network protocol implementations.
RFC-1084 BOOTP Vendor Information Extensions
A Recommended Draft Standard. This RFCis a slight revision and
extension of RFC-1048 by Philip Prindeville, who should be
credited with the original work in this memo. This memo will be
updated as additional tags are defined. This edition introduces
Tag 13 for Boot File Size.
RFC-1087 Ethics and the Internet
This memo is a statement of policy by the Internet Activities
Board (IAB) concerning the proper use of the resources of the
Internet.
RFC-1095 The Common Management Information Services
and Protocol over TCP/IP (CMOT)
A Recommended Draft Standard. This memo defines a network
management architecture that uses the International Organization
for Standardization's (ISO) Common Management Information
Services/Common Management Information Protocol (CMIS/CMIP) in a
TCP/IP environment. This architecture provides a means by which
control and monitoring information can be exchanged between a
manager and a remote network element. In particular, this memo
defines the means for implementing the Draft International
Standard (DIS) version of CMIS/CMIP on top of Internet transport
protocols for the purpose of carrying management information
defined in the Internet-standard management information base.
RFC-1112 Host Extensions for IP Multicasting
A Recommended Standard for IP multicasting in the Internet. This
memo specifies the extensions required of a host implementation of
the Internet Protocol (IP) to support multicasting.
RFC-1119 Network Time Protocol (NTP)
A Recommended Standard Protocol. This document describes the
Network Time Protocol (NTP), specifies its formal structure and
summarizes information useful for its implementation. NTP
provides the mechanisms to synchronize time and coordinate time
distribution in a large, diverse internet operating at rates from
mundane to lightwave.
RFC-1122 Requirements for Internet Hosts -
Communication Layers
A Required Standard. An official specification for the Internet
community. This memo incorporates by reference, amends, corrects,
and supplements the primary protocol standards documents relating
to hosts. This is one RFCof a pair (see RFC1123) that defines
and discusses the requirements for Internet host software. This
RFCcovers the communications protocol layers: link layer, IP
layer, and transport layer.
RFC-1123 Requirements for Internet Hosts -
Application and Support
A Required Standard. An official specification for the Internet
community. This memo incorporates by reference, amends, corrects,
and supplements the primary protocol standards documents relating
to hosts. This RFCis one of a pair (see RFC1122) that defines
and discusses the requirements for Internet host software. This
RFCcovers the application and support protocols.
RFC-1140 IAB Official Protocol Standards
This memo describes the state of standardization of protocols used
in the Internet as determined by the Internet Activities Board
(IAB). This memo is issued quarterly, please be sure the copy you
are reading is dated within the last three months.
RFC-1155 Structure and Identification of Management
Information for TCP/IP-based Internets
A Recommended Standard. This RFCprovides the common definitions
for the structure and identification of management information for
TCP/IP-based internets. In particular, together with its
companion memos, which describe the initial management information
base along with the initial network management protocol, these
documents provide a simple, working architecture and system for
managing TCP/IP-based internets and in particular, the Internet.
TCP/IP implementations in the Internet which are network
manageable are expected to adopt and implement this specification.
RFC-1156 Management Information Base for Network
Management of TCP/IP-based Internets
A Recommended Standard. This RFCprovides the initial version of
the Management Information Base (MIB) for use with network
management protocols in TCP/IP-based internets in the short-term.
In particular, together with its companion memos which describe
the structure of management information along with the initial
network management protocol, these documents provide a simple,
workable architecture and system for managing TCP/IP-based
internets, and in particular, the Internet. TCP/IP
implementations in the Internet which are network manageable are
expected to adopt and implement this specification.
RFC-1157 A Simple Network Management Protocol (SNMP)
A Recommended Standard. This memo defines a simple protocol by
which management information for a network element may be
inspected or altered by logical remote users. In particular,
together with its companion memos which describe the structure of
management information along with the initial management
information base, these documents provide a simple, workable
architecture and system for managing TCP/IP-based internets and in
particular, the Internet.
RFC-1160 The Internet Activities Board
A history and description of the Internet Activities Board (IAB)
and its subsidiary organizations. This memo is for informational
use and does not constitute a standard.
RFC-1166 Internet Numbers
An official status report for the Internet community. This memo
describes the fields of network numbers and autonomous system
numbers that are assigned specific values for actual use, and
lists the currently assigned values.
APPENDIX A
DISCLAIMER
Neither the Internet Engineering Task Force, Internet Activities
Board, nor the United States Government, nor the National Science
Foundation, nor any of their employees makes any warranty or assumes
the legal liability or responsibility for the accuracy, completeness,
or usefulness of any information, apparatus, product, or process
disclosed, or represents that its use would not infringe privately
owned rights. Reference to any special commercial products,
trademark, manufacturer, or otherwise, does not necessarily
constitute or imply its endorsement, recommendation, or favoring by
the Internet Engineering Task Force, nor the Internet Activities
Board, nor the United States Government nor the National Science
Foundation. The views and opinions of the author(s) do not
necessarily state or reflect those of the Internet Engineering Task
Force, Internet Activities Board, nor the United States Government
nor the National Science Foundation and shall not be used for
advertising or product endorsement.
APPENDIX B
LIST OF ACRONYMS
ARP Address Resolution Protocol
ASCII American Standard Code for Information Interchange
BBN Bolt, Beranek, and Newman, Inc.
BOOTP Bootstrap Protocol
CACM Communications on Association for Computing Machinery
CCITT International Telegraph and Telephone Consultative
Committee
CERFnet California Education and Research Federation Network
CIC Committee on Institutional Cooperation
CMIS Common Management Information Services
CMIP Common Management Information Protocol
CMOT Common Management Information Services and
Protocol Over TCP/IP
CNRI Corporation for National Research Initiatives
DARPA Defense Advanced Research Projects Agency
DDN Defense Data Network
DIS Draft International Standard
DNS Domain Name System
DoD Department of Defense
EARN European Academic Research Network
EDUCOM
EGP Exterior Gateway Protocol
EUnet European Unix Network
FCCSET Federal Coordinating Council for Science,
Engineering and Technology
FDDI Fiber Distributed Data Interface
FRICC Federal Research Internet Coordinating Committee
FTP File Transfer Protocol
IAB Internet Activities Board
ICMP Internet Control Message Protocol
IETF Internet Engineering Task Force
IP Internet Protocol
ISDN Integrated Services Digital Network
ISI Information Sciences Institute
ISO International Organization for Standardization
JvNC John von Neumann National Supercomputer Center
LAN Local Area Network
MIB Management Information Base
NEARnet New England Academic and Research Network
NIC Network Information Center
NNTF Networking and Telecommunications Task Force
NREN National Research and Education Network
NSF National Science Foundation
NTP Network Time Protocol
NWNET NorthWestNet
OS Operation System
OSI Open Systems Interconnection
RFCRequest For Comments
SIG Special Interest Group
SMTP Simple Mail Transfer Protocol
SNMP Simple Network Management Protocol
TCP/IP Transmission Control Protocol/Internet Protocol
TP4 Transport Protocol, class 4
UDP User Datagram Protocol
USC University of Southern California
UUCP Unix-to-Unix Copy Program
UTnet University of Texas Network
WRL DEC Western Research Laboratory
Security Considerations
Security issues are not discussed in this memo.
Authors' Addresses
Karen Bowers
Corporation for National Research Initiatives
1895 Preston White Drive, Suite 100
Reston, VA 22091
Phone: (703) 582-8990
E-Mail: kbowers@nri.reston.va.us
Tracy LaQuey
University of Texas
Computation Center
M/S COM 1
Austin, TX 78712
Phone: (512) 471-3241
E-Mail: tracy@nic.the.net
Joyce K. Reynolds
University of Southern California
Information Sciences Institute
4676 Admiralty Way, #1001
Marina del Rey, CA 90292-6695
Phone: (213) 822-1511
E-Mail: jkrey@isi.edu
Karen Roubicek
BBN Systems and Technologies
10 Moulton Street
NSF Network Service Center
Cambridge, MA 02138
Phone: (617) 873-3361
E-Mail: roubicek@nnsc.nsf.net
Mary Stahl
SRI International
Network Information Systems Center
333 Ravenswood Avenue, Rm EJ 296
Menlo Park, CA 94025
Phone: (415) 859-4775
E-Mail: stahl@nisc.sri.com
Aileen Yuan
The MITRE Corporation
7525 Colshire Drive, MS W422
McLean, VA 22102
Phone: (703) 883-7023