| |
| RFC 35 | Network Meeting |
| |
| Authors: | S.D. Crocker. |
| Date: | March 1970 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
|
|
| |
| RFC 96 | An Interactive Network Experiment to Study Modes of Access the Network Information Center |
| |
| Authors: | R.W. Watson. |
| Date: | February 1971 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
|
|
| |
| RFC 699 | Request For Comments summary notes: 600-699 |
| |
| Authors: | J. Postel, J. Vernon. |
| Date: | November 1982 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
|
|
| |
| RFC 800 | Request For Comments summary notes: 700-799 |
| |
| Authors: | J. Postel, J. Vernon. |
| Date: | November 1982 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This RFC is a slightly annotated list of the 100 RFCs from RFC 700 through RFC 799. This is a status report on these RFCs. |
|
| |
| RFC 899 | Request For Comments summary notes: 800-899 |
| |
| Authors: | J. Postel, A. Westine. |
| Date: | May 1984 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
|
|
| |
| RFC 1012 | Bibliography of Request For Comments 1 through 999 |
| |
| Authors: | J.K. Reynolds, J. Postel. |
| Date: | June 1987 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This RFC is 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 1056 | PCMAIL: A distributed mail system for personal computers |
| |
| Authors: | M.L. Lambert. |
| Date: | June 1988 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0993 |
| Status: | INFORMATIONAL |
|
This memo is a discussion of the Pcmail workstation based distributed mail system. It is identical to the discussion in RFC-993, save that a new, much simpler mail transport protocol is described. The new transport protocol is the result of continued research into ease of protocol implementation and use issues. |
|
| |
| RFC 1057 | RPC: Remote Procedure Call Protocol specification: Version 2 |
| |
| Authors: | Sun Microsystems. |
| Date: | June 1988 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1050 |
| Status: | INFORMATIONAL |
|
This RFC describes a standard that Sun Microsystems and others are using, and is one we wish to propose for the Internet's consideration. This memo is not an Internet standard at this time. |
|
| |
| RFC 1094 | NFS: Network File System Protocol specification |
| |
| Authors: | Sun Microsystems. |
| Date: | March 1989 |
| Formats: | txt pdf |
| Also: | RFC 1813 |
| Status: | INFORMATIONAL |
|
This RFC describes a protocol that Sun Microsystems, Inc., and others are using. A new version of the protocol is under development, but others may benefit from the descriptions of the current protocol, and discussion of some of the design issues. |
|
| |
| RFC 1099 | Request for Comments Summary: RFC Numbers 1000-1099 |
| |
| Authors: | J. Reynolds. |
| Date: | December 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
|
|
| |
| RFC 1107 | Plan for Internet directory services |
| |
| Authors: | K.R. Sollins. |
| Date: | July 1989 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This memo proposes a program to develop a directory service for the Internet. It reports the results of a meeting held in February 1989, which was convened to review requirements and options for such a service. This proposal is offered for comment, and does not represent a committed research activity of the Internet community. |
|
| |
| RFC 1111 | Request for comments on Request for Comments: Instructions to RFC authors |
| |
|
|
This RFC specifies a standard for the Internet community. Authors of RFCs are expected to adopt and implement this standard. |
|
| |
| RFC 1117 | Internet numbers |
| |
|
|
This memo is an official status report on the network numbers and the autonomous system numbers used in the Internet community. |
|
| |
| RFC 1118 | Hitchhikers guide to the Internet |
| |
| Authors: | E. Krol. |
| Date: | September 1989 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This RFC is being distributed to members of the Internet community in order to make available some "hints" which will allow new network participants to understand how the direction of the Internet is set, how to acquire online information and how to be a good Internet neighbor. While the information discussed may not be relevant to the research problems of the Internet, it may be interesting to a number of researchers and implementors. No standards are defined or specified in this memo. |
|
| |
| RFC 1120 | Internet Activities Board |
| |
| Authors: | V. Cerf. |
| Date: | September 1989 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1160 |
| Status: | INFORMATIONAL |
|
This RFC provides 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 1121 | Act one - the poems |
| |
| Authors: | J. Postel, L. Kleinrock, V.G. Cerf, B. Boehm. |
| Date: | September 1989 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This RFC presents a collection of poems that were presented at "Act One", a symposium held partially in celebration of the 20th anniversary of the ARPANET. |
|
| |
| RFC 1127 | Perspective on the Host Requirements RFCs |
| |
| Authors: | R.T. Braden. |
| Date: | October 1989 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This RFC is for information only; it does not constitute a standard, draft standard, or proposed standard, and it does not define a protocol. |
|
| |
| RFC 1129 | Internet Time Synchronization: The Network Time Protocol |
| |
| Authors: | D.L. Mills. |
| Date: | October 1989 |
| Formats: | txt pdf ps |
| Also: | RFC 1119 |
| Status: | INFORMATIONAL |
|
This memo describes the Network Time Protocol (NTP) designed to distribute time information in a large, diverse internet system operating at speeds from mundane to lightwave. It uses a returnable- time architecture in which a distributed subnet of time servers operating in a self-organizing, hierarchical, master-slave configuration synchronizes local clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute time information within a network via local routing algorithms and time daemons. The architectures, algorithms and protocols which have evolved to NTP over several years of implementation and refinement are described in this paper. The synchronization subnet which has been in regular operation in the Internet for the last several years is described along with performance data which shows that timekeeping accuracy throughout most portions of the Internet can be ordinarily maintained to within a few tens of milliseconds, even in cases of failure or disruption of clocks, time servers or networks. This memo describes the Network Time Protocol in RFC-1119. |
|
| |
| RFC 1133 | Routing between the NSFNET and the DDN |
| |
| Authors: | J.Y. Yu, H.W. Braun. |
| Date: | November 1989 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This document is a case study of the implementation of routing between the NSFNET and the DDN components (the MILNET and the ARPANET). We hope that it can be used to expand towards interconnection of other Administrative Domains. We would welcome discussion and suggestions about the methods employed for the interconnections. No standards are specified in this memo. |
|
| |
| RFC 1135 | Helminthiasis of the Internet |
| |
| Authors: | J.K. Reynolds. |
| Date: | December 1989 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This memo takes a look back at the helminthiasis (infestation with, or disease caused by parasitic worms) of the Internet that was unleashed the evening of 2 November 1988. This RFC provides information about an event that occurred in the life of the Internet. This memo does not specify any standard. 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. |
|
| |
| RFC 1136 | Administrative Domains and Routing Domains: A model for routing in the Internet |
| |
| Authors: | S. Hares, D. Katz. |
| Date: | December 1989 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This RFC proposes a model for describing routing within the Internet. The model is an adaptation of the "OSI Routeing Framework". This memo does not specify an Internet standard. |
|
| |
| RFC 1141 | Incremental updating of the Internet checksum |
| |
| Authors: | T. Mallory, A. Kullberg. |
| Date: | January 1990 |
| Formats: | txt pdf |
| Updates: | RFC 1071 |
| Updated by: | RFC 1624 |
| Status: | INFORMATIONAL |
|
This memo correctly describes the incremental update procedure for use with the standard Internet checksum. It is intended to replace the description of Incremental Update in RFC 1071. This is not a standard but rather, an implementation technique. |
|
| |
| RFC 1142 | OSI IS-IS Intra-domain Routing Protocol |
| |
| Authors: | D. Oran, Ed.. |
| Date: | February 1990 |
| Formats: | txt pdf ps |
| Status: | INFORMATIONAL |
|
This RFC is a republication of ISO DP 10589 as a service to the Internet community. This is not an Internet standard. |
|
| |
| RFC 1147 | FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices |
| |
| Authors: | R.H. Stine. |
| Date: | April 1 1990 |
| Formats: | txt pdf ps |
| Obsoleted by: | RFC 1470 |
| Status: | INFORMATIONAL |
|
The goal of this FYI memo is to provide practical information to site administrators and network managers. This memo provides information for the Internet community. It does not specify any standard. It is not a statement of IAB policy or recommendations. [Also FYI 2.] This catalog contains descriptions of several tools available to assist network managers in debugging and maintaining TCP/IP internets and interconnected communications resources. Entries in the catalog tell what a tool does, how it works, and how it can be obtained. |
|
| |
| RFC 1150 | FYI on FYI: Introduction to the FYI Notes |
| |
| Authors: | G.S. Malkin, J.K. Reynolds. |
| Date: | March 1990 |
| Formats: | txt pdf |
| Also: | FYI 0001 |
| Status: | INFORMATIONAL |
|
This memo is the first in a new sub-series of RFCs called FYIs (For Your Information). This memo provides information for the Internet community. It does not specify any standard. [Also FYI 1.] |
|
| |
| RFC 1152 | Workshop report: Internet research steering group workshop on very-high-speed networks |
| |
| Authors: | C. Partridge. |
| Date: | April 1 1990 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This memo is a report on a workshop sponsored by the Internet Research Steering Group. This memo is for information only. This RFC does not specify an Internet standard. |
|
| |
| RFC 1160 | Internet Activities Board |
| |
| Authors: | V. Cerf. |
| Date: | May 1990 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1120 |
| Status: | INFORMATIONAL |
|
This RFC provides 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. This is a revision of RFC 1120. |
|
| |
| RFC 1166 | Internet numbers |
| |
|
|
This memo is a status report on the network numbers and autonomous system numbers used in the Internet community. |
|
| |
| RFC 1167 | Thoughts on the National Research and Education Network |
| |
| Authors: | V.G. Cerf. |
| Date: | July 1990 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
The memo provides a brief outline of a National Research and Education Network (NREN). This memo provides information for the Internet community. It does not specify any standard. It is not a statement of IAB policy or recommendations. |
|
| |
| RFC 1168 | Intermail and Commercial Mail Relay services |
| |
| Authors: | A. Westine, A.L. DeSchon, J. Postel, C.E. Ward. |
| Date: | July 1990 |
| Formats: | txt pdf ps |
| Status: | INFORMATIONAL |
|
This RFC discusses the history and evolution of the Intermail and Commercial mail systems. The problems encountered in operating a store-and-forward mail relay between commercial systems such as Telemail, MCI Mail and Dialcom are also discussed. This RFC provides information for the Internet community, and does not specify any standard. |
|
| |
| RFC 1169 | Explaining the role of GOSIP |
| |
| Authors: | V.G. Cerf, K.L. Mills. |
| Date: | August 1990 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This informational RFC represents the official view of the Internet Activities Board (IAB), after coordination with the Federal Networking Council (FNC). This RFC does not specify a standard. |
|
| |
| RFC 1170 | Public key standards and licenses |
| |
| Authors: | R.B. Fougner. |
| Date: | January 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This RFC is a public statement by Public Key Partners regarding Public Key Standards and Licenses. This memo is for informational use only, and does not constitute an Internet standard. |
|
| |
| RFC 1173 | Responsibilities of host and network managers: A summary of the "oral tradition" of the Internet |
| |
| Authors: | J. VanBokkelen. |
| Date: | August 1990 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This informational RFC describes the conventions to be followed by those in charge of networks and hosts in the Internet. It is a summary of the "oral tradition" of the Internet on this subject. [RFC Editor's note: This memo is a contribution by the author of his view of these conventions. It is expected that this RFC will provide a basis for the development of official policies in the future.] These conventions may be supplemented or amended by the policies of specific local and regional components of the Internet. This RFC does not specify a standard, or a policy of the IAB. |
|
| |
| RFC 1174 | IAB recommended policy on distributing internet identifier assignment and IAB recommended policy change to internet "connected" status |
| |
| Authors: | V.G. Cerf. |
| Date: | August 1990 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This informational RFC represents the official view of the Internet Activities Board (IAB), and describes the recommended policies and procedures on distributing Internet identifier assignments and dropping the connected status requirement. This RFC does not specify a standard. |
|
| |
| RFC 1175 | FYI on where to start: A bibliography of internetworking information |
| |
| Authors: | K.L. Bowers, T.L. LaQuey, J.K. Reynolds, K. Roubicek, M.K. Stahl, A. Yuan. |
| Date: | August 1990 |
| Formats: | txt pdf |
| Also: | FYI 0003 |
| Status: | INFORMATIONAL |
|
The intent of this bibliography is to offer a representative collection of resources of information that will help the reader become familiar with the concepts of internetworking. It is meant to be a starting place for further research. There are references to other sources of information for those users wishing to pursue, in greater depth, the issues and complexities of the current networking environment. |
|
| |
| RFC 1177 | FYI on Questions and Answers: Answers to commonly asked "new internet user" questions |
| |
| Authors: | G.S. Malkin, A.N. Marine, J.K. Reynolds. |
| Date: | August 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1206 |
| Status: | INFORMATIONAL |
|
This FYI RFC is one of three FYI's called, "Questions and Answers" (Q/A), produced by the User Services Working Group (USWG) 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. [Also FYI 4.] |
|
| |
| RFC 1178 | Choosing a name for your computer |
| |
| Authors: | D. Libes. |
| Date: | August 1990 |
| Formats: | txt pdf |
| Also: | FYI 0005 |
| Status: | INFORMATIONAL |
|
In order to easily distinguish between multiple computers, we give them names. Experience has taught us that it is as easy to choose bad names as it is to choose good ones. This essay presents guidelines for deciding what makes a name good or bad.
Keywords: domain name system, naming conventions, computer administration, computer network management |
|
| |
| RFC 1179 | Line printer daemon protocol |
| |
| Authors: | L. McLaughlin. |
| Date: | August 1990 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This RFC describes an existing print server protocol widely used on the Internet for communicating between line printer daemons (both clients and servers). This memo is for informational purposes only, and does not specify an Internet standard. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. |
|
| |
| RFC 1180 | TCP/IP tutorial |
| |
| Authors: | T.J. Socolofsky, C.J. Kale. |
| Date: | January 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This RFC is a tutorial on the TCP-IP protocol suite, focusing particularly on the steps in forwarding an IP datagram from source host to destination host through a router. It does not specify an Internet standard. |
|
| |
| RFC 1181 | RIPE Terms of Reference |
| |
| Authors: | R. Blokzijl. |
| Date: | September 1990 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This RFC describes the Terms of Reference of RIPE (Reseaux IP Europeens), the cooperation of European IP networks. This memo provides information for the Internet community. It does not specify any standard. |
|
| |
| RFC 1186 | MD4 Message Digest Algorithm |
| |
| Authors: | R.L. Rivest. |
| Date: | October 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1320 |
| Status: | INFORMATIONAL |
|
This RFC is the specification of the MD4 Digest Algorithm. If you are going to implement MD4, it is suggested you do it this way. This memo is for informational use and does not constitute a standard. |
|
| |
| RFC 1192 | Commercialization of the Internet summary report |
| |
| Authors: | B. Kahin. |
| Date: | November 1990 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This memo is based on a workshop held by the Science, Technology and Public Policy Program of the John F. Kennedy School of Government, Harvard University, March 1-3, 1990. This memo provides information for the Internet community. It does not specify any standard. |
|
| |
| RFC 1193 | Client requirements for real-time communication services |
| |
| Authors: | D. Ferrari. |
| Date: | November 1990 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
A real-time communication service provides its clients with the ability to specify their performance requirements and to obtain guarantees about the satisfaction of those requirements. In this paper, we propose a set of performance specifications that seem appropriate for such services; they include various types of delay bounds, throughput bounds, and reliability bounds. We also describe other requirements and desirable properties from a client's viewpoint, and the ways in which each requirement is to be translated to make it suitable for lower levels in the protocol hierarchy.Finally, we present some examples of requirements specification, and discuss some of the possible objections to our approach.
This research has been supported in part by AT&T Bell Laboratories, the University of California under a MICRO grant, and theInternational Computer Science Institute. The views and conclusions in this document are those of the author and should not be interpreted as representing official policies, either expressed or implied, of any of the sponsoring organizations. |
|
| |
| RFC 1197 | Using ODA for translating multimedia information |
| |
| Authors: | M. Sherman. |
| Date: | December 1990 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
The purpose of this RFC is to inform implementors of multimedia systems about our experiences using ISO 8613: Office Document Architecture (ODA). Because ODA is being proposed as an encoding format for use in multimedia mail and file exchange, implementors wishing to use ODA in an open systems environment may profit from our experiences. This memo provides information for the Internet community. It does not specify any standard. |
|
| |
| RFC 1198 | FYI on the X window system |
| |
| Authors: | R.W. Scheifler. |
| Date: | January 1991 |
| Formats: | txt pdf |
| Also: | FYI 0006 |
| Status: | INFORMATIONAL |
|
This FYI RFC provides pointers to the published standards of the MIT X Consortium. This memo provides information for the Internet community. It does not specify any Internet standard. |
|
| |
| RFC 1199 | Request for Comments Summary Notes: 1100-1199 |
| |
| Authors: | J. Reynolds. |
| Date: | December 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
|
|
| |
| RFC 1202 | Directory Assistance service |
| |
| Authors: | M.T. Rose. |
| Date: | February 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This document defines a mechanism by which a user-interface may access a textual DAP-like interface over a TCP/IP connection. This is a local mechanism. This memo provides information for the Internet community. It does not specify any standard. |
|
| |
| RFC 1205 | 5250 Telnet interface |
| |
| Authors: | P. Chmielewski. |
| Date: | February 1991 |
| Formats: | txt pdf |
| Updated by: | RFC 2877 |
| Status: | INFORMATIONAL |
|
This RFC is being distributed in order to document the interface to the IBM 5250 Telnet implementation. This memo provides information for the Internet community. It does not specify any standard. |
|
| |
| RFC 1206 | FYI on Questions and Answers: Answers to commonly asked "new Internet user" questions |
| |
| Authors: | G.S. Malkin, A.N. Marine. |
| Date: | February 1991 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1177 |
| Obsoleted by: | RFC 1325 |
| Status: | INFORMATIONAL |
|
This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A). 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. [FYI 4] |
|
| |
| RFC 1207 | FYI on Questions and Answers: Answers to commonly asked "experienced Internet user" questions |
| |
| Authors: | G.S. Malkin, A.N. Marine, J.K. Reynolds. |
| Date: | February 1991 |
| Formats: | txt pdf |
| Also: | FYI 0007 |
| Status: | INFORMATIONAL |
|
This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A), 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. |
|
| |
| RFC 1208 | A Glossary of Networking Terms |
| |
| Authors: | O.J. Jacobsen, D.C. Lynch. |
| Date: | March 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This RFC is a glossary adapted from "The INTEROP Pocket Glossary of Networking Terms" distributed at Interop '90. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1210 | Network and infrastructure user requirements for transatlantic research collaboration: Brussels, July 16-18, and Washington July 24-25, 1990 |
| |
| Authors: | V.G. Cerf, P.T. Kirstein, B. Randell. |
| Date: | March 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This report summarises user requirements for networking and related infrastructure facilities needed to enable effective cooperation between US and European research teams participating in the plannedESPRIT-DARPA/NSF programme of collaborative research in InformationScience and Technology. It analyses the problems and disparities of the current facilities, and suggests appropriate one and three year targets for improvements. It proposes a number of initial actions aimed at achieving these targets. Finally, the workshop has identified a non-exhaustive set of important issues upon which support of future research will depend. These issues could be studied in the short term, with the aim of initiating a programme of joint research in collaboration technology within the next year. |
|
| |
| RFC 1211 | Problems with the maintenance of large mailing lists |
| |
| Authors: | A. Westine, J. Postel. |
| Date: | March 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This RFC discusses problems with maintaining large mailing lists, especially the processing of error reports. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1215 | Convention for defining traps for use with the SNMP |
| |
| Authors: | M.T. Rose. |
| Date: | March 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This memo suggests a straight-forward approach towards defining traps used with the SNMP. This memo provides information for the Internet community. It does not specify any standard. |
|
| |
| RFC 1216 | Gigabit network economics and paradigm shifts |
| |
| Authors: | P. Richard, P. Kynikos. |
| Date: | April 1 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This memo proposes a new standard paradigm for the Internet Activities Board (IAB) standardization track. [STANDARDS-TRACK] |
|
| |
| RFC 1217 | Memo from the Consortium for Slow Commotion Research (CSCR) |
| |
| Authors: | V.G. Cerf. |
| Date: | April 1 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This RFC is in response to RFC 1216, "Gigabit Network Economics and Paradigm Shifts". This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1218 | Naming scheme for c=US |
| |
| Authors: | North American Directory Forum. |
| Date: | April 1 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1255, RFC 1417 |
| Status: | INFORMATIONAL |
|
This RFC is a near-verbatim copy of a document, known as NADF-123, which has been produced by the North American Directory Forum (NADF). As a part of its charter, the NADF must reach agreement as to how entries are named in the public portions of the North American Directory. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1219 | On the assignment of subnet numbers |
| |
| Authors: | P.F. Tsuchiya. |
| Date: | April 1 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This memo suggests a new procedure for assigning subnet numbers. Use of this assignment technique within a network would be a purely local matter, and would not effect other networks. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1221 | Host Access Protocol (HAP) specification: Version 2 |
| |
| Authors: | W. Edmond. |
| Date: | April 1 1991 |
| Formats: | txt pdf |
| Updates: | RFC 0907 |
| Status: | INFORMATIONAL |
|
This memo describes the Host Access Protocol implemented in the Terrestrial Wideband Network (TWBNET). This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1222 | Advancing the NSFNET routing architecture |
| |
| Authors: | H.W. Braun, Y. Rekhter. |
| Date: | May 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This RFC suggests improvements in the NSFNET routing architecture to accommodate a more flexible interface to the Backbone clients. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1223 | OSI CLNS and LLC1 protocols on Network Systems HYPERchannel |
| |
| Authors: | J.M. Halpern. |
| Date: | May 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
The intent of this document is to provide a complete discussion of the protocols and techniques used to transmit OSI CLNS and LLC1 datagrams (and any associated higher level protocols) on Network Systems Corporation's HYPERchannel equipment.This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1236 | IP to X.121 address mapping for DDN |
| |
| Authors: | L. Morales, P. Hasse. |
| Date: | June 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This memo defines a standard way of converting IP addresses to CCITT X.121 addresses and is the recommended standard for use on the Internet, specifically for the Defense Data Network (DDN). This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1242 | Benchmarking Terminology for Network Interconnection Devices |
| |
| Authors: | S. Bradner. |
| Date: | July 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This memo discusses and defines a number of terms that are used in describing performance benchmarking tests and the results of such tests. The terms defined in this memo will be used in additional memos to define specific benchmarking tests and the suggested format to be used in reporting the results of each of the tests. This memo is a product of the Benchmarking Methodology Working Group (BMWG) of the Internet Engineering Task Force (IETF). |
|
| |
| RFC 1244 | Site Security Handbook |
| |
| Authors: | J.P. Holbrook, J.K. Reynolds. |
| Date: | July 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2196 |
| Status: | INFORMATIONAL |
|
This FYI RFC is a first attempt at providing Internet users guidance on how to deal with security issues in the Internet. This FYI RFC provides information for the Internet community. It does not specify an Internet standard. [FYI 8] |
|
| |
| RFC 1245 | OSPF Protocol Analysis |
| |
|
|
This report attempts to summarize the key features of OSPF V2. It also attempts to analyze how the protocol will perform and scale in the Internet. This memo provides information for the Internet community. It does not specify any Internet standard. |
|
| |
| RFC 1246 | Experience with the OSPF Protocol |
| |
|
|
This report documents experience with OSPF V2. This includes reports on interoperability testing, field experience, simulations and the current state of OSPF implementations. This memo provides information for the Internet community. It does not specify any Internet standard. |
|
| |
| RFC 1249 | DIXIE Protocol Specification |
| |
| Authors: | T. Howes, M. Smith, B. Beecher. |
| Date: | August 1991 |
| Formats: | txt pdf |
| Also: | RFC 1202 |
| Status: | INFORMATIONAL |
|
This RFC defines a mechanism by which TCP/UDP based clients can access OSI Directory Service without the overhead of the ISO transport and presentation protocols required to implement full-blown DAP. This memo provides information for the Internet community. It does not specify any standard. |
|
| |
| RFC 1251 | Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members |
| |
| Authors: | G. Malkin. |
| Date: | August 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1336 |
| Status: | INFORMATIONAL |
|
This FYI RFC contains biographical information about members of the Internet Activities Board (IAB), the Internet Engineering Steering Group (IESG) of the Internet Engineering Task Force (IETF), and the the Internet Research Steering Group (IRSG) of the Internet Research Task Force (IRTF). This memo provides information for the Internet community. It does not specify an Internet standard. [FYI 9] |
|
| |
| RFC 1254 | Gateway Congestion Control Survey |
| |
| Authors: | A. Mankin, K. Ramakrishnan. |
| Date: | August 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
The growth of network intensive Internet applications has made gateway congestion control a high priority. The IETF Performance andCongestion Control Working Group surveyed and reviewed gateway congestion control and avoidance approaches. The purpose of this paper is to present our review of the congestion control approaches, as a way of encouraging new discussion and experimentation. Included in the survey are Source Quench, Random Drop, Congestion Indication(DEC Bit), and Fair Queueing. The task remains for Internet implementors to determine and agree on the most effective mechanisms for controlling gateway congestion. |
|
| |
| RFC 1255 | A Naming Scheme for c=US |
| |
| Authors: | The North American Directory Forum. |
| Date: | September 1991 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1218 |
| Obsoleted by: | RFC 1417 |
| Status: | INFORMATIONAL |
|
This memo documents the NADF's agreement as to how entries are named in the public portions of the North American Directory. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1257 | Isochronous applications do not require jitter-controlled networks |
| |
| Authors: | C. Partridge. |
| Date: | September 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This memo argues that jitter control is not required for networks to support isochronous applications. A network providing bandwidth and bounds delay is sufficient. The implications for gigabit internetworking protocols are briefly considered. |
|
| |
| RFC 1258 | BSD Rlogin |
| |
| Authors: | B. Kantor. |
| Date: | September 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
The rlogin facility provides a remote-echoed, locally flow-controlled virtual terminal with proper flushing of output.This memo documents an existing protocol and common implementation that is extensively used on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1259 | Building the open road: The NREN as test-bed for the national public network |
| |
| Authors: | M. Kapor. |
| Date: | September 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This memo discusses the background and importance of NREN. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1261 | Transition of Nic Services |
| |
| Authors: | S. Williamson, L. Nobile. |
| Date: | September 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This memo outlines the transition of NIC Services. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1262 | Guidelines for Internet Measurement Activities |
| |
| Authors: | V.G. Cerf. |
| Date: | October 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This RFC represents IAB guidance for researchers considering measurement experiments on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1263 | TCP Extensions Considered Harmful |
| |
| Authors: | S. O'Malley, L.L. Peterson. |
| Date: | October 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This RFC comments on recent proposals to extend TCP. It argues that the backward compatible extensions proposed in RFC's 1072 and 1185 should not be pursued, and proposes an alternative way to evolve theInternet protocol suite. Its purpose is to stimulate discussion in the Internet community. |
|
| |
| RFC 1265 | BGP Protocol Analysis |
| |
| Authors: | Y. Rekhter. |
| Date: | October 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This report summarizes the key feature of BGP, and analyzes the protocol with respect to scaling and performance. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1266 | Experience with the BGP Protocol |
| |
| Authors: | Y. Rekhter. |
| Date: | October 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
The purpose of this memo is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by Border Gateway Protocol (BGP). This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1270 | SNMP Communications Services |
| |
| Authors: | F. Kastenholz. |
| Date: | October 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This document discusses various issues to be considered when determining the underlying communications services to be used by an SNMP implementation. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1272 | Internet Accounting: Background |
| |
| Authors: | C. Mills, D. Hirsh, G.R. Ruth. |
| Date: | November 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This document provides background information for the "Internet Accounting Architecture". This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1273 | Measurement Study of Changes in Service-Level Reachability in the Global TCP/IP Internet: Goals, Experimental Design, Implementation, and Policy Considerations |
| |
| Authors: | M.F. Schwartz. |
| Date: | November 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
In this report we discuss plans to carry out a longitudinal measurement study of changes in service-level reachability in the global TCP/IP Internet. We overview our experimental design, considerations of network and remote site load, mechanisms used to control the measurement collection process, and network appropriate use and privacy issues, including our efforts to inform sites measured by this study. A list of references and information on how to contact the Principal Investigator are included. |
|
| |
| RFC 1275 | Replication Requirements to provide an Internet Directory using X.500 |
| |
| Authors: | S.E. Hardcastle-Kille. |
| Date: | November 1991 |
| Formats: | txt pdf ps |
| Status: | INFORMATIONAL |
|
This RFCconsiders certain deficiencies of the 1988 X.500 standard, which need to be addressed before an effective openInternet Directory can be established using these protocols and services [CCI88]. The only areas considered are primary problems, to which solutions must be found before a pilot can be deployed. This RFCconcerns itself with deficiencies which can only be addressed by use of additional protocol or procedures for distributed operation. |
|
| |
| RFC 1278 | A string encoding of Presentation Address |
| |
| Authors: | S.E. Hardcastle-Kille. |
| Date: | November 1991 |
| Formats: | txt ps pdf |
| Status: | INFORMATIONAL |
|
There are a number of environments where a simple string encoding of Presentation Address is desirable. This specification defines such a representation. |
|
| |
| RFC 1281 | Guidelines for the Secure Operation of the Internet |
| |
| Authors: | R. Pethia, S. Crocker, B. Fraser. |
| Date: | November 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
The purpose of this document is to provide a set of guidelines to aid in the secure operation of the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1282 | BSD Rlogin |
| |
| Authors: | B. Kantor. |
| Date: | December 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This memo documents an existing protocol and common implementation that is extensively used on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1287 | Towards the Future Internet Architecture |
| |
| Authors: | D. Clark, L. Chapin, V. Cerf, R. Braden, R. Hobby. |
| Date: | December 1991 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This informational RFC discusses important directions for possible future evolution of the Internet architecture, and suggests steps towards the desired goals. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1290 | There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places |
| |
| Authors: | J. Martin. |
| Date: | December 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1402 |
| Status: | INFORMATIONAL |
|
This document was presented at the 1991 ACM SIGUCCS User ServicesConference. It appears here in its updated form.
There is a wealth of information on the network. In fact, so much information, that you could spend your entire life browsing. This paper will present some of the "gold nuggets" of information and file repositories on the network that could be of use to end users.
The ultimate goal is to make the route to these sources of information invisible to the user. At present, this is not easy to do. I will explain some of the techniques that can be used to make these nuggets easier to pick up so that we can all be richer. |
|
| |
| RFC 1291 | Mid-Level Networks Potential Technical Services |
| |
| Authors: | V. Aggarwal. |
| Date: | December 1991 |
| Formats: | txt ps pdf |
| Status: | INFORMATIONAL |
|
This document proposes a set of technical services that each Internet mid-level network can offer within the mid-level network itself and and to its peer networks. The term "mid-level" is used as a generic term to represent all regional and similar networks, which, due to continuous evolutions and transitions, can no longer be termed"regional" [MAN]. It discusses the pros and cons of offering these services, as well as areas in which mid-level networks can work together.
A large portion of the ideas stem from discussions at the IETFOperational Statistics (OPstat), User Connectivity Problems (UCP) andNetwork Joint Management (NJM) working groups. |
|
| |
| RFC 1292 | A Catalog of Available X.500 Implementations |
| |
| Authors: | R. Lang, R. Wright. |
| Date: | January 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1632 |
| Status: | INFORMATIONAL |
|
The goal of this document is to provide information regarding the availability and capability of implementations of X.500. Comments and critiques of this document, and new or updated descriptions ofX.500 implementations are welcome. Send them to the DirectoryInformation Services Infrastructure (DISI) Working Group(disi@merit.edu) or to the editors. |
|
| |
| RFC 1295 | User Bill of Rights for entries and listings in the Public Directory |
| |
| Authors: | The North American Directory Forum. |
| Date: | January 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1417 |
| Status: | INFORMATIONAL |
|
This RFC is a near-verbatim copy of a document, known as NADF-265, which has been produced by the North American Directory Forum (NADF).
User Bill of Rights for entries and listings in the Public Directory
The mission of the North American Directory Forum is to provide interconnected electronic directories which empower users with unprecedented access to public information. To address significant security and privacy issues, the North American Directory Forum introduces the following "User Bill of Rights" for entries in thePublic Directory. As a user, you have:
I. The right not to be listed.
II. The right to have you or your agent informed when your entry is created.
III. The right to examine your entry.
IV. The right to correct inaccurate information in your entry.
V. The right to remove specific information from your entry.
VI. The right to be assured that your listing in thePublic Directory will comply with US or Canadian law regulating privacy or access information.
VII. The right to expect timely fulfillment of these rights. |
|
| |
| RFC 1296 | Internet Growth (1981-1991) |
| |
| Authors: | M. Lottor. |
| Date: | January 1992 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
This document illustrates the growth of the Internet by examination of entries in the Domain Name System (DNS) and pre-DNS host tables.DNS entries are collected by a program called ZONE, which searches the Internet and retrieves data from all known domains. Pre-DNS host table data were retrieved from system archive tapes. Various statistics are presented on the number of hosts and domains. |
|
| |
| RFC 1297 | NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist ("NOC TT REQUIREMENTS") |
| |
| Authors: | D. Johnson. |
| Date: | January 1992 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
Professional quality handling of network problems requires some kind of problem tracking system, herein referred to as a "trouble ticket" system. A basic trouble ticket system acts like a hospital chart, coordinating the work of multiple people who may need to work on the problem.
Once the basic trouble ticket system is in place, however, there are many extensions that can aid Network Operations efficiency.Information in the tickets can be used to produce statistical reports. Operator efficiency and accuracy may be increased by automating trouble ticket entry with information from the networkAlert system. The Alert system may be used to monitor trouble ticket progress. Trouble tickets may be also used to communicate network health information between NOCs, to telcom vendors, and to other internal sales and engineering audiences.
This document explores competing uses, architectures, and desirable features of integrated internal trouble ticket systems for Network and other Operations Centers. |
|
| |
| RFC 1298 | SNMP over IPX |
| |
| Authors: | R. Wormley, S. Bostock. |
| Date: | February 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1420 |
| Status: | INFORMATIONAL |
|
This memo defines a convention for encapsulating Simple NetworkManagement Protocol (SNMP) [1] packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol [2]. |
|
| |
| RFC 1299 | Summary of 1200-1299 |
| |
| Authors: | M. Kennedy. |
| Date: | January 1997 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
|
|
| |
| RFC 1300 | Remembrances of Things Past |
| |
| Authors: | S. Greenfield. |
| Date: | February 1992 |
| Formats: | txt pdf |
| Status: | INFORMATIONAL |
|
Poem. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1301 | Multicast Transport Protocol |
| |
| Authors: | S. Armstrong, A. Freier, K. Marzullo. |
| Date: | February 1992 |
| Formats: | |
| |
