scispace - formally typeset
Search or ask a question

Showing papers on "The Internet published in 1975"


08 Nov 1975

28 citations


30 Apr 1975
TL;DR: Extends message field definition beyond RFC 561 attempts to establish syntactic and semantic standards for ARPANET; see also RFCs 733 and 822.
Abstract: Extends message field definition beyond RFC 561 attempts to establish syntactic and semantic standards for ARPANET; see also RFCs 733 and 822.

9 citations


05 Nov 1975
TL;DR: This is a working document which has been developed as the specification and guideline for design of a Burroughs B6700 attachment to an ARPA-Style network to utilize a front-end processor with a new protocol for network operation.
Abstract: This is a working document which has been developed as the specification and guideline for design of a Burroughs B6700 attachment to an ARPA-Style network. The approach is to utilize a front-end processor with a new protocol for network operation. That protocol, described herein, has been built upon the concepts expressed by M. This proposed, site-specific, FEP implementation is the work of Gerald Bailey and Keith McCloghrie of NSA and of David Grothe of ACC. It has already sustained some corrections provided by MAP. It will be helpful if interested networkers will review and provide comments to us. PREFACE This document describes the protocol to be used for connecting a general-purpose computer system (host) to an ARPANET-like network via a "front-end" computer. The main body of the document is aimed at a reader who is not conversant with all the details of network protocols. However, a paragraph marked with [n], refers a reader familiar with network protocols to the n-th item of Appendix A which will amplify that particular paragraph. Further information on the network protocols referred to in this document can be obtained from the Network Information Center. Appendix B contains diagrams showing the transitions between the different connection states. Appendices C and D give the implementation details of this protocol in the Front-End and the Hosts. This protocol is predicated upon the assumption that for each host, a line protocol, at a lower level, will be established between the device-driver modules in the Host and the Front-End, and that this line protocol provides Front-End Protocol with error-free transmissions. INTRODUCTION 2 A host computer may be connected to a network for a variety of reasons. Network connection may be an attempt to expand the usefulness of the Host to the community of users which it serves by making network resources available to them. Conversely, the services which the Host provides may be made available to a larger community of users, with the network providing the method of access to those services. In order for members of a network community to communicate in an intelligent way, there must exist a set of protocols. The implementation of these protocols in a host computer is typically called the Network Control Program (NCP). The size and complexity of the NCP is proportional to the number and complexity of protocols which it implements. For an ARPANET like network, both the number and complexity are …

4 citations


01 Feb 1975
TL;DR: An earlier poll of Telnet server implementation status revealed no change in the status of the Telnet client or server as well as no changes in the server itself.
Abstract: An earlier poll of Telnet server implementation status. Updates RFCs 701, 702 and 669; see also RFC 703.

4 citations