scispace - formally typeset
Search or ask a question

Showing papers on "The Internet published in 1987"


Book
01 Jul 1987
TL;DR: There is a completely new chapter on the "The Internet and Information Science." This will take up themes discussed in earlier chapters and reconsiders them in the light of the new information environment.
Abstract: This is the 3rd revised edition of the classic work "Information Science in Theory and Practice." There is a completely new chapter on the "The Internet and Information Science." This will take up themes discussed in earlier chapters and reconsiders them in the light of the new information environment.

175 citations


01 Mar 1987
TL;DR: The NETBLT protocol as mentioned in this paper is a transport level protocol intended for the rapid transfer of a large quantity of data between computers, and it provides a transfer that is reliable and flow controlled, and is designed to provide maximum throughput over a wide variety of networks.
Abstract: This document is a description of, and a specification for, the NETBLT protocol. It is a revision of the specification published in RFC-969. NETBLT (NETwork BLock Transfer) is a transport level protocol intended for the rapid transfer of a large quantity of data between computers. It provides a transfer that is reliable and flow controlled, and is designed to provide maximum throughput over a wide variety of networks. Although NETBLT currently runs on top of the Internet Protocol (IP), it should be able to operate on top of any datagram protocol similar in function to IP. This document is published for discussion and comment, and does not constitute a standard. The proposal may change and certain parts of the protocol have not yet been specified; implementation of this document is therefore not advised. Obsoletes RFC-969.

165 citations


01 Feb 1987
TL;DR: This document defines message encryption and authentication procedures, in order to provide privacy-enhanced mail services for electronic mail transfer in the Internet, and is intended to become one member of a related set of four RFCs.
Abstract: This document defines message encryption and authentication procedures, in order to provide privacy-enhanced mail (PEM) services for electronic mail transfer in the Internet. It is intended to become one member of a related set of four RFCs. The procedures defined in the current document are intended to be compatible with a wide range of key management approaches, including both symmetric (secret-key) and asymmetric (public-key) approaches for encryption of data encrypting keys. Use of symmetric cryptography for message text encryption and/or integrity check computation is anticipated. RFC 1422 specifies supporting key management mechanisms based on the use of public-key certificates. RFC 1423 specifies algorithms, modes, and associated identifiers relevant to the current RFC and to RFC 1422 . RFC 1424 provides details of paper and electronic formats and procedures for the key management infrastructure being established in support of these services.

138 citations


Journal ArticleDOI
TL;DR: A number of sources of test problems accesible via Internet are detailed, for example by electronic mail, anonymous file transfer protocol, Gopher, Veronica and via the World Wide Web using browsers such as Mosaic and Netscape.
Abstract: In this paper we detail a number of sources of test problems accesible via Internet. We also outline a number of ways by which such test problems can be obtained, for example by electronic mail (email), anonymous file transfer protocol (anonymous ftp), Gopher, Veronica and via the World Wide Web (WWW) using browsers such as Mosaic and Netscape.

118 citations


01 Dec 1987
TL;DR: This RFC defines the standard format for interchange of Network News articles among USENET sites, describes the format for articles themselves, and gives partial standards for transmission of news.
Abstract: This memo is distributed as an RFC only to make this information easily accessible to researchers in the ARPA community. It does not specify an Internet standard. This RFC defines the standard format for interchange of Network News articles among USENET sites. It describes the format for articles themselves, and gives partial standards for transmission of news. The news transmission is not entirely standardized in order to give a good deal of flexibility to the individual hosts to choose transmission hardware and software, whether to batch news and so on.

111 citations


Proceedings ArticleDOI
01 Aug 1987
TL;DR: A yellow-pages service that maps service names into server addresses and associates a set of attributes with each server is introduced, which can be integrated with the available internet communication protocols to enable clients from throughout the internet to access local servers.
Abstract: We introduce a yellow-pages service that maps service names into server addresses. The service is novel in that it associates a set of attributes with each server. Clients specify the attributes the server should possess when requesting a service and the yellow-pages service determines what servers satisfy the request. In addition to describing the implementation of the yellow-pages service within a local-area network, we show how the service can be integrated with the available internet communication protocols to enable clients from throughout the internet to access local servers.

89 citations


Book
01 Jan 1987
TL;DR: The new edition of this bestselling computer concepts book focuses on the explosive growth of the Internet, including web page design, ethics, Office 97, and push technology.
Abstract: From the Publisher: The new edition of this bestselling computer concepts book focuses on the explosive growth of the Internet. Many topics have been updated or added, including web page design, ethics, Office 97, and push technology. Includes Capron's Pocket Internet, a resource manual with fun and interesting websites organized by category.

80 citations


01 Jun 1987
TL;DR: This RFC summarizes the requirements for gateways to be used between networks supporting the Internet protocols in a formal statement of the requirements to be met by gateways used in the Internet system.
Abstract: This RFC summarizes 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. As such, it is an official specification for the Internet community.

74 citations


01 May 1987
TL;DR: This memo specifies version 3 of the protocol and supersedes RFC- 983 and changes between the protocol is described in RFC-983 and this memo are minor, but unfortunately incompatible.
Abstract: This memo specifies a standard for the Internet community. Hosts on the Internet that choose to implement ISO transport services on top of the TCP are expected to adopt and implement this standard. TCP port 102 is reserved for hosts which implement this standard. This memo specifies version 3 of the protocol and supersedes RFC-983. Changes between the protocol is described in RFC-983 and this memo are minor, but unfortunately incompatible.

57 citations


01 Nov 1987
TL;DR: This RFC provides guidelines for domain administrators in operating a domain server and maintaining their portion of the hierarchical database.
Abstract: This RFC provides guidelines for domain administrators in operating a domain server and maintaining their portion of the hierarchical database. Familiarity with the domain system is assumed (see RFCs 1031, 1032, 1034, and 1035).

51 citations


Journal ArticleDOI
01 Jun 1987
TL;DR: The workflow typical in a disaster scenario is analyzed and the design considerations for a virtual information center (VIC) that can both efficiently and effectively coordinate and process a large number of information requests for disaster preparation/management/recovery teams are discussed.
Abstract: There are innumerable human and organizational circumstances when free flowing information is essential for effective decision-making. In a closed system with limited boundary scanning, information handling is a fairly manageable task [School Library Journal, 39 (1993) 146]. However, where sources of data and/or decisions are high volume encompass a large geographic area and cover a gamut of organizational entities, information gathering and fusing can be daunting [FEMA, Publication No. 229 (4) (1995)]. This paper analyzes the workflow typical in a disaster scenario and discusses the design considerations for a virtual information center (VIC) that can both efficiently and effectively coordinate and process a large number of information requests for disaster preparation/management/recovery teams. The proposed design is domain independent, uses a net-centric approach and can be readily exported to many other governmental and organizational decision environments. The prototype version of the system uses the object-oriented model in connecting to multiple databases across the Internet and has all the essential features that can readily be cloned to enlarge the system's scope.

Proceedings ArticleDOI
01 Aug 1987
TL;DR: The design of a TCP/IP implementation and its upper level protocols on the University of Illinois supercomputer and some of the special problems encountered while writing and debugging under CTSS are discussed.
Abstract: This paper will discuss the design of a TCP/IP implementation and its upper level protocols on the University of Illinois supercomputer. We will also discuss some of the issues peculiar to TCP communication with a supercomputer, and some of the special problems encountered while writing and debugging under CTSS, which is not an environment particularly conducive to network development.

Proceedings ArticleDOI
27 Apr 1987
TL;DR: A visa scheme for implementing access control in Inter-Organization Network (ION) gateways to allow an organization to modify and trust only them internal system that require ION access all other internal system can not communicate with the outside.
Abstract: In this paper we describe a visa scheme for implementing access control in Inter-Organization Network (ION) gateways. The purpose of the scheme is to allow an organization to modify and trust only them internal system that require ION access all other internal system can not communicate with the outside. Control is distributed among the ION participants so that each may make its own design tradeoffs between performance and trust.

01 Aug 1987
TL;DR: This RFC Reference Guide is intended to provide a historical account by categorizing and summarizing of the Request for Comments numbers 1 through 999 issued between the years 1969-1987.
Abstract: This RFC Reference Guide is intended to provide a historical account 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.

01 Jun 1987
TL;DR: The X window system has been widely reviewed and tested and the Internet community is encouraged to experiment with it.
Abstract: This RFC is distributed to the Internet community for information only. It does not establish an Internet standard. The X window system has been widely reviewed and tested. The Internet community is encouraged to experiment with it.

01 Jun 1987
TL;DR: This RFC is being distributed to members of the Internet community in order to solicit comments on the Implementors Guide, and may be of some interest to a number of researchers and implementors.
Abstract: This RFC is being distributed to members of the Internet community in order to solicit comments on the Implementors Guide. While this document may not be directly relevant to the research problems of the Internet, it may be of some interest to a number of researchers and implementors.

01 Jan 1987
TL;DR: A new approach to naming in evolving systems that are composed of a heterogeneous collection of subsystems is presented through a structure that separates global name space administration from knowledge of the semantics of naming in each of the assimilated subsystems.
Abstract: When computers are connected via networks, and networks are joined into internets, the overall system effectiveness hinges on how well the basic network facilities are able to support communication and sharing among the interconnected systems Of particular importance is the naming facility, which allows clients to use mnemonically meaningful names for the entities of interest in the internet, such as mailboxes, services, hosts, users, devices, and files This thesis presents a new approach to naming in evolving systems that are composed of a heterogeneous collection of subsystems Our goal is to reduce the cost of integrating new types of systems into an existing environment Providing a name service in such an environment is difficult because each of the systems being integrated typically uses its own name service The obvious approach is to implement a new standard to which existing subsystems must adhere However, several problems render such standardization unsuitable for the environment we are addressing We present a new approach based on integrating existing name spaces through a structure that separates global name space administration from knowledge of the semantics of naming in each of the assimilated subsystems Roughly, our Heterogeneous Name Service (HNS) acts as a broker between clients and existing name services A client presents a name to the HNS, along with an indication of the "query class" to which its naming request belongs The HNS determines the underlying name service that stores information concerning the name, and routes the naming request through an agent that understands how to access that name service for that query class A major advantage of this approach is ease of integration: newly added system types can participate in the larger system without modification At the same time, systems that use the global name service can take advantage of the services provided by new systems without modification In addition, the model has broader applicability than the applications typically associated with naming It can, for example, form the basis for a file system that integrates a heterogeneous collection of existing file systems A prototype implementation of the HNS has been built and analyzed for its ability to support heterogeneous applications and caching at various levels

01 Oct 1987
TL;DR: HEMS, the high-level entity management system, is an internetwork management protocol designed to work with the TCP-IP protocol suite and provides database query language primitives that allow remote users to modify the database.
Abstract: This memo provides a general overview of the High-level Entity management system (HEMS). This system is experimental, and is currently being tested in portions of the Internet.

Proceedings ArticleDOI
G. Arnold1
01 Aug 1987
TL;DR: The experiences of a PC implementation of Sun's NFS protocols revealed that there are some unique obstacles to be overcome in this kind of system, and indicate that further work is needed in the development of protocols to manage networks of low-end machines.
Abstract: A team at Sun Microsystems East Coast Division has been engaged in developing and supporting a PC implementation of Sun's Network File System (NFS™) protocols. In the course of this work we were faced with the problem of implementing Internet protocol software within the PC environment. Our experiences revealed that there are some unique obstacles to be overcome in this kind of system, and indicate that further work is needed in the development of protocols to manage networks of low-end machines.

01 May 1987
TL;DR: This memo is an official status report on the protocols used in the Internet community and identifies the documents specifying the official protocols used on the Internet.
Abstract: This memo is 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.


01 Nov 1987
TL;DR: This RFC consolidates information necessary for the implementation of domain style names throughout the DDN/MILNET Internet community by providing an overview of the transition process from host tables to domains, a timetable for the transition, and references to documentation and software relating to the domain system.
Abstract: This RFC consolidates information necessary for the implementation of domain style names throughout the DDN/MILNET Internet community. The introduction of domain style names will impact all hosts in the DDN/MILNET Internet. This RFC is designed as an aid to implementors and administrators by providing: 1) an overview of the transition process from host tables to domains, 2) a timetable for the transition, and 3) references to documentation and software relating to the domain system.

01 Dec 1987
TL;DR: The goal of this specification is to promote discussion of the ideas described here, and to encourage designers of future file protocols to take advantage of these ideas.
Abstract: This document includes a specification of the NFILE file access protocol and its underlying levels of protocol, the Token List Transport Layer and Byte Stream with Mark. The goal of this specification is to promote discussion of the ideas described here, and to encourage designers of future file protocols to take advantage of these ideas. A secondary goal is to make the specification available to sites that might benefit from implementing NFILE.

Journal ArticleDOI
TL;DR: In this paper, the authors discuss the design of a TCP/IP implementation and its upper level protocols on the University of Illinois supercomputer and discuss some of the issues peculiar to TCP comm...
Abstract: This paper will discuss the design of a TCP/IP implementation and its upper level protocols on the University of Illinois supercomputer. We will also discuss some of the issues peculiar to TCP comm...

01 Oct 1987
TL;DR: This memo assumes knowledge of the HEMS system described in RFC-1021, and of the ISO data encoding standard, ASN.1.
Abstract: This RFC specifies the High-Level Entity Management System (HEMS) Monitoring and Control Language. This language defines the requests and replies used in HEMS. This memo assumes knowledge of the HEMS system described in RFC-1021, and of the ISO data encoding standard, ASN.1.

Book
01 Jan 1987
TL;DR: In this article, the authors present the latest updates on the information superhighway, the Internet, HDTV, fiber optics and LEOS satellites, providing the knowledge and skills to succeed in today's technical world.
Abstract: Electronic technicians can keep up-to-date on new technologies and techniques with this revised edition. Containing the latest updates on the information superhighway, the Internet, HDTV, fiber optics and LEOS satellites, it provides you with the knowledge and skills to succeed in today's technical world.

Proceedings ArticleDOI
01 Oct 1987
TL;DR: The management of multidestination groups for tactical communication systems must address requirements not applicable to more conventional data communication systems such as local area networks and the ARPANET.
Abstract: Multidestination protocol concepts suitable for survivable tactical command and control systems are presented. Specifically, the multidestination protocol concepts have been developed to provide efficient use of communication resources for broadcast types of networks such as packet radio. As in packet radio, these protocol concepts are distributed and survivable. The management of multidestination groups for tactical communication systems must address requirements not applicable to more conventional data communication systems such as local area networks and the ARPANET. Extensions to the proposed Internet Group Multicast Protocol standard are described. Multidestination routing concepts, consisting of a multicast and a broadcast routing protocol, for packet radio networks are presented. These multidestination routing concepts will be implemented in packet radio as extensions to the distributed stationless routing protocol currently used.

Book
01 Jan 1987
TL;DR: This chapter discusses the reference interview rules of the search computerized reference searches, as well as Instruction and policies: bibliographical instruction reference service policies and evaluation.
Abstract: Part 1 Introduction: reference service and the community. Part 2 Libraries and the wiring of America: the age of electronic information networks and reference services the internet and reference services document delivery and interlibrary loan. Part 3 Interview and search: the reference interview rules of the search computerized reference searches. Part 4 Instruction and policies: bibliographical instruction reference service policies and evaluation.

01 Sep 1987
TL;DR: This memo suggest a proposed protocol for the Internet community, and request discussion and suggestions for improvements.
Abstract: This memo suggest a proposed protocol for the Internet community, and request discussion and suggestions for improvements.

01 Aug 1987
TL;DR: This RFC identifies the requirements on communication networks for supporting scientific research and proposes some specific areas for near term work, as well as some long term goals.
Abstract: This RFC identifies the requirements on communication networks for supporting scientific research. It proposes some specific areas for near term work, as well as some long term goals. This is an "idea" paper and discussion is strongly encouraged.