| |
| RFC 1100 | IAB official protocol standards |
| |
| Authors: | Defense Advanced Research Projects Agency, Internet Activities Board. |
| Date: | April 1989 |
| Formats: | txt json html |
| Obsoletes: | RFC 1083 |
| Obsoleted by: | RFC 1130 |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1100 |
|
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures is presented first, followed by discussions of the standardization process and the RFC document series, then the explanation of the terms is presented, the lists of protocols in each stage of standardization follows, and finally pointers to references and contacts for further information. This memo is issued quarterly, please be sure the copy you are reading is dated within the last three months. Current copies may be obtained from the Network Information Center or from the Internet Assigned Numbers Authority (see the contact information at the end of this memo). Do not use this memo after 31-July-89. |
|
| |
| RFC 1101 | DNS encoding of network names and other types |
| |
|
|
This RFC proposes two extensions to the Domain Name System: - A specific method for entering and retrieving RRs which map between network names and numbers. - Ideas for a general method for describing mappings between arbitrary identifiers and numbers. The method for mapping between network names and addresses is a proposed standard, the ideas for a general method are experimental. |
|
| |
| RFC 1102 | Policy routing in Internet protocols |
| |
|
|
The purpose of this RFC is to focus discussion on particular problems in the Internet and possible methods of solution. No proposed solutions in this document are intended as standards for the Internet. |
|
| |
| RFC 1103 | Proposed standard for the transmission of IP datagrams over FDDI Networks |
| |
|
|
This RFC specifies a method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK] |
|
| |
| RFC 1104 | Models of policy based routing |
| |
|
|
The purpose of this RFC is to outline a variety of models for policy based routing. The relative benefits of the different approaches are reviewed. Discussions and comments are explicitly encouraged to move toward the best policy based routing model that scales well within a large internetworking environment. |
|
| |
| RFC 1105 | Border Gateway Protocol (BGP) |
| |
|
|
This RFC outlines a specific approach for the exchange of network reachability information between Autonomous Systems. Updated by RFCs 1163 and 1164. [STANDARDS-TRACK] |
|
| |
| RFC 1106 | TCP big window and NAK options |
| |
|
|
Two extensions to the TCP protocol are described in this RFC in order to provide a more efficient operation over a network with a high bandwidth*delay product. The main issue that still needs to be solved is congestion versus noise. This issue is touched on in this memo, but further research is still needed on the applicability of the extensions in the Internet as a whole infrastructure and not just high bandwidth*delay product networks. Even with this outstanding issue, this document does describe the use of these options in the isolated satellite network environment to help facilitate more efficient use of this special medium to help off load bulk data transfers from links needed for interactive use. |
|
| |
| RFC 1107 | Plan for Internet directory services |
| |
| Authors: | K.R. Sollins. |
| Date: | July 1989 |
| Formats: | txt html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1107 |
|
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 1108 | U.S |
| |
| Authors: | Department of Defense Security Options for the Internet Protocol. S. Kent. |
| Date: | November 1991 |
| Formats: | txt json html |
| Obsoletes: | RFC 1038 |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1108 |
|
This RFC specifies the U.S. Department of Defense Basic SecurityOption and the top-level description of the Extended Security Option for use with the Internet Protocol. This RFC obsoletes RFC 1038"Revised IP Security Option", dated January 1988. |
|
| |
| RFC 1109 | Report of the second Ad Hoc Network Management Review Group |
| |
|
|
This RFC reports an official Internet Activities Board (IAB) policy position on the treatment of Network Management in the Internet. This RFC presents the results and recommendations of the second Ad Hoc Network Management Review on June 12, 1989. The results of the first such meeting were reported in RFC 1052. |
|
| |
| RFC 1110 | Problem with the TCP big window option |
| |
|
|
The TCP Big Window option discussed in RFC 1106 will not work properly in an Internet environment which has both a high bandwidth * delay product and the possibility of disordering and duplicating packets. In such networks, the window size must not be increased without a similar increase in the sequence number space. Therefore, a different approach to big windows should be taken in the Internet. |
|
| |
| 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 1112 | Host extensions for IP multicasting |
| |
|
|
This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. Recommended procedure for IP multicasting in the Internet. This RFC obsoletes RFCs 998 and 1054. [STANDARDS-TRACK] |
|
| |
| RFC 1113 | Privacy enhancement for Internet electronic mail: Part I - message encipherment and authentication procedures |
| |
|
|
This RFC specifies features for private electronic mail based on encryption technology. [STANDARDS-TRACK] |
|
| |
| RFC 1114 | Privacy enhancement for Internet electronic mail: Part II - certificate-based key management |
| |
|
|
This RFC specifies the key management aspects of Privacy Enhanced Mail. [STANDARDS-TRACK] |
|
| |
| RFC 1115 | Privacy enhancement for Internet electronic mail: Part III - algorithms, modes, and identifiers |
| |
|
|
This RFC provides definitions, references, and citations for algorithms, usage modes, and associated identifiers used in RFC-1113 and RFC-1114 in support of privacy-enhanced electronic mail. [STANDARDS-TRACK] |
|
| |
| RFC 1116 | Telnet Linemode option |
| |
|
|
Hosts on the Internet that support Linemode within the Telnet protocol are expected to adopt and implement this protocol. Obsoleted by RFC 1184. [STANDARDS-TRACK] |
|
| |
| 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 json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1118 |
|
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 1119 | Network Time Protocol (version 2) specification and implementation |
| |
|
|
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. It uses a returnable-time design 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 reference time via local routing algorithms and time daemons. [STANDARDS-TRACK] |
|
| |
| RFC 1120 | Internet Activities Board |
| |
|
|
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 json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1121 |
|
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 1122 | Requirements for Internet Hosts - Communication Layers |
| |
|
|
This RFC is an official specification for the Internet community. It incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts. [STANDARDS-TRACK] |
|
| |
| RFC 1123 | Requirements for Internet Hosts - Application and Support |
| |
|
|
This RFC is an official specification for the Internet community. It incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts. [STANDARDS-TRACK] |
|
| |
| RFC 1124 | Policy issues in interconnecting networks |
| |
|
|
To support the activities of the Federal Research Internet Coordinating Committee (FRICC) in creating an interconnected set of networks to serve the research community, two workshops were held to address the technical support of policy issues that arise when interconnecting such networks. Held under the suspices of the Internet Activities Board at the request of the FRICC, and sponsored by NASA through RIACS, the workshops addressed the required and feasible technologies and architectures that could be used to satisfy the desired policies for interconnection. The purpose of this RFC is to report the results of these workshops. |
|
| |
| RFC 1125 | Policy requirements for inter Administrative Domain routing |
| |
|
|
The purpose of this memo is to focus discussion on particular problems in the Internet and possible methods of solution. No proposed solutions in this document are intended as standards for the Internet. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to such problems, leading eventually to the development and adoption of standards. |
|
| |
| RFC 1126 | Goals and functional requirements for inter-autonomous system routing |
| |
| Authors: | M. Little. |
| Date: | October 1989 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1126 |
|
This document describes the functional requirements for a routing protocol to be used between autonomous systems. This document is intended as a necessary precursor to the design of a new inter- autonomous system routing protocol and specifies requirements for the Internet applicable for use with the current DoD IP, the ISO IP, and future Internet Protocols. It is intended that these requirements will form the basis for the future development of a new inter-autonomous systems routing architecture and protocol. This memo does not specify a standard. |
|
| |
| RFC 1127 | Perspective on the Host Requirements RFCs |
| |
| Authors: | R.T. Braden. |
| Date: | October 1989 |
| Formats: | txt html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1127 |
|
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 1128 | Measured performance of the Network Time Protocol in the Internet system |
| |
|
|
This paper describes a series of experiments involving over 100,000 hosts of the Internet system and located in the U.S., Europe and the Pacific. The experiments are designed to evaluate the availability, accuracy and reliability of international standard time distribution using the DARPA/NSF Internet and the Network Time Protocol (NTP), which is specified in RFC-1119. NTP is designed specifically for use in a large, diverse internet system operating at speeds from mundane to lightwave. In NTP a distributed subnet of time servers operating in a self-organizing, hierarchical, master-slave configuration exchange precision timestamps in order to synchronize subnet clocks to each other and national time standards via wire or radio. The experiments are designed to locate Internet hosts and gateways that provide time by one of three time distribution protocols and evaluate the accuracy of their indications. For those hosts that support NTP, the experiments determine the distribution of errors and other statistics over paths spanning major portions of the globe. Finally, the experiments evaluate the accuracy and reliability of precision timekeeping using NTP and typical Internet paths involving DARPA, NSFNET and other agency networks. The experiments demonstrate 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 does not specify a standard. |
|
| |
| RFC 1129 | Internet Time Synchronization: The Network Time Protocol |
| |
|
|
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 1130 | IAB official protocol standards |
| |
| Authors: | Defense Advanced Research Projects Agency, Internet Activities Board. |
| Date: | October 1989 |
| Formats: | txt json html |
| Obsoletes: | RFC 1100 |
| Obsoleted by: | RFC 1140 |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1130 |
|
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). |
|
| |
| RFC 1131 | OSPF specification |
| |
|
|
This RFC is the specification of the Open Shortest Path First (OSPF) Internet routing protocol. OSPF is in the class of Internal Gateway Protocols (IGPs) for distributing routing information between gateways of a single Autonomous System. This routing protocol is based on the link-state approach (in contrast to the distance-vector approach). This specification was developed by the OSPF Working Group of the Internet Engineering Task Force. [STANDARDS-TRACK] |
|
| |
| RFC 1132 | Standard for the transmission of 802.2 packets over IPX networks |
| |
|
|
This document specifies a standard method of encapsulating 802.2 packets on networks supporting Novell's Internet Packet Exchange Protocol (IPX). It obsoletes earlier documents detailing the transmission of Internet packets over IPX networks. It differs from these earlier documents in that it allows for the transmission of multiple network protocols over IPX and for the transmission of packets through IPX bridges. |
|
| |
| RFC 1133 | Routing between the NSFNET and the DDN |
| |
| Authors: | J.Y. Yu, H.W. Braun. |
| Date: | November 1989 |
| Formats: | txt html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1133 |
|
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 1134 | Point-to-Point Protocol: A proposal for multi-protocol transmission of datagrams over Point-to-Point links |
| |
|
|
The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is composed of three parts:
1. A method for encapsulating datagrams over serial links.
2. An extensible Link Control Protocol (LCP).
3. A family of Network Control Protocols (NCP) for establishing and configuring different network-layer protocols.
This document defines the encapsulation scheme, the basic LCP, and anNCP for establishing and configuring the Internet Protocol (IP)(called the IP Control Protocol, IPCP).
The options and facilities used by the LCP and the IPCP are defined in separate documents. Control protocols for configuring and utilizing other network-layer protocols besides IP (e.g., DECNET,OSI) are expected to be developed as needed. |
|
| |
| RFC 1135 | Helminthiasis of the Internet |
| |
| Authors: | J.K. Reynolds. |
| Date: | December 1989 |
| Formats: | txt json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1135 |
|
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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1136 |
|
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 1137 | Mapping between full RFC 822 and RFC 822 with restricted encoding |
| |
|
|
This RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. |
|
| |
| RFC 1138 | Mapping between X.400(1988) / ISO 10021 and RFC 822 |
| |
|
|
Ths RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. This memo updates RFCs 822, 987, and 1026. |
|
| |
| RFC 1139 | Echo function for ISO 8473 |
| |
|
|
This memo defines an echo function for the connection-less network layer protocol. Two mechanisms are introduced that may be used to implement the echo function. The first mechanism is recommended as an interim solution for the Internet community. The second mechanism will be progressed to the ANSI X3S3.3 working group for consideration as a work item.
When an ISO standard is adopted that provides functionality similar to that described by this memo, then this memo will become obsolete and superceded by the ISO standard. |
|
| |
| RFC 1140 | IAB official protocol standards |
| |
| Authors: | Defense Advanced Research Projects Agency, Internet Activities Board. |
| Date: | May 1990 |
| Formats: | txt html json |
| Obsoletes: | RFC 1130 |
| Obsoleted by: | RFC 1200 |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1140 |
|
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. Current copies may be obtained from the Network Information Center or from the Internet Assigned Numbers Authority. Do not use this edition after 31-Aug-90. |
|
| |
| RFC 1141 | Incremental updating of the Internet checksum |
| |
|
|
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 |
| |
|
|
This RFC is a republication of ISO DP 10589 as a service to the Internet community. This is not an Internet standard. |
|
| |
| RFC 1143 | The Q Method of Implementing TELNET Option Negotiation |
| |
| Authors: | D.J. Bernstein. |
| Date: | February 1990 |
| Formats: | txt json html |
| Status: | EXPERIMENTAL |
| DOI: | 10.17487/RFC 1143 |
|
This is RFC discusses an implementation approach to option negotiation in the Telnet protocol (RFC 854). It does not propose any changes to the TELNET protocol. Rather, it discusses the implementation of the protocol of one feature, only. This is not a protocol specification. This is an experimental method of implementing a protocol. |
|
| |
| RFC 1144 | Compressing TCP/IP Headers for Low-Speed Serial Links |
| |
|
|
This RFC describes a method for compressing the headers of TCP/IP datagrams to improve performance over low speed serial links. The motivation, implementation and performance of the method are described. C code for a sample implementation is given for reference. [STANDARDS- TRACK] |
|
| |
| RFC 1145 | TCP alternate checksum options |
| |
|
|
This memo is suggests a pair of TCP options to allow use of alternate data checksum algorithms in the TCP header. The use of these options is experimental, and not recommended for production use. |
|
| |
| RFC 1146 | TCP alternate checksum options |
| |
|
|
This memo is suggests a pair of TCP options to allow use of alternate data checksum algorithms in the TCP header. The use of these options is experimental, and not recommended for production use. Note: This RFC corrects errors introduced in the editing process in RFC 1145. |
|
| |
| RFC 1147 | FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices |
| |
|
|
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 1148 | Mapping between X.400(1988) / ISO 10021 and RFC 822 |
| |
|
|
This RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. This edition includes material lost in editing. |
|
| |
| RFC 1149 | Standard for the transmission of IP datagrams on avian carriers |
| |
|
|
This memo describes an experimental method for the encapsulation of IP datagrams in avian carriers. This specification is primarily useful in Metropolitan Area Networks. This is an experimental, not recommended standard. |
|
| |
| RFC 1150 | FYI on FYI: Introduction to the FYI Notes |
| |
|
|
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 1151 | Version 2 of the Reliable Data Protocol (RDP) |
| |
|
|
This RFC suggests several updates to the specification of the Reliable Data Protocol (RDP) in RFC-908 based on experience with the protocol. This revised version of the protocol is experimental. |
|
| |
| RFC 1152 | Workshop report: Internet research steering group workshop on very-high-speed networks |
| |
| Authors: | C. Partridge. |
| Date: | April 1990 |
| Formats: | txt json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1152 |
|
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 1153 | Digest message format |
| |
| Authors: | F.J. Wancho. |
| Date: | April 1990 |
| Formats: | txt json html |
| Status: | EXPERIMENTAL |
| DOI: | 10.17487/RFC 1153 |
|
This memo describes the de facto standard Digest Message Format. This is an elective experimental protocol. |
|
| |
| RFC 1154 | Encoding header field for internet messages |
| |
|
|
This RFC proposes an elective experimental Encoding header field to permit the mailing of multi-part, multi-structured messages. The use of Encoding updates RFC 1049 (Content-Type), and is a suggested update to RFCs 1113, 1114, and 1115 (Privacy Enhancement). |
|
| |
| RFC 1155 | Structure and identification of management information for TCP/IP-based internets |
| |
|
|
This RFC is a re-release of RFC 1065, with a changed "Status of this Memo", plus a few minor typographical corrections. The technical content of the document is unchanged from RFC 1065. [STANDARDS-TRACK] |
|
| |
| RFC 1156 | Management Information Base for network management of TCP/IP-based internets |
| |
|
|
This RFC is a re-release of RFC 1066, with a changed "Status of this Memo", "IAB Policy Statement", and "Introduction" sections plus a few minor typographical corrections. The technical content of the document is unchanged from RFC 1066. [STANDARDS-TRACK] |
|
| |
| RFC 1157 | Simple Network Management Protocol (SNMP) |
| |
| Authors: | J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin. |
| Date: | May 1990 |
| Formats: | txt json html |
| Obsoletes: | RFC 1098 |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1157 |
|
This RFC is a re-release of RFC 1098, with a changed "Status of this Memo" section plus a few minor typographical corrections. This memo defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. [STANDARDS-TRACK] |
|
| |
| RFC 1158 | Management Information Base for network management of TCP/IP-based internets: MIB-II |
| |
|
|
This memo defines the second version of the Management Information Base (MIB-II) for use with network management protocols in TCP/IP- based internets. In particular, together with its companion memos which describe the structure of management information (RFC 1155) along with the network management protocol (RFC 1157) for TCP/IP- based internets, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular the Internet community. This document on MIB-II incorporates all of the technical content of RFC 1156 on MIB-I and extends it, without loss of compatibilty. [STANDARDS-TRACK] |
|
| |
| RFC 1159 | Message Send Protocol |
| |
|
|
This RFC suggests an Experimental Protocol for the Internet community. Hosts on the Internet that choose to implement a Message Send Protocol may experiment with this protocol. |
|
| |
| RFC 1160 | Internet Activities Board |
| |
|
|
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 1161 | SNMP over OSI |
| |
|
|
This memo defines an experimental means for running the Simple Network Management Protocol (SNMP) over OSI transports. This memo does not specify a standard for the Internet community, |
|
| |
| RFC 1162 | Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) Management Information Base |
| |
|
|
This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. This memo does not specify a standard for the Internet community. |
|
| |
| RFC 1163 | Border Gateway Protocol (BGP) |
| |
|
|
This RFC, together with its companion RFC-1164, "Application of the Border Gateway Protocol in the Internet", specify an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK] |
|
| |
| RFC 1164 | Application of the Border Gateway Protocol in the Internet |
| |
| Authors: | J.C. Honig, D. Katz, M. Mathis, Y. Rekhter, J.Y. Yu. |
| Date: | June 1990 |
| Formats: | txt html json |
| Obsoleted by: | RFC 1268 |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1164 |
|
This RFC, together with its companion RFC-1163, "A Border Gateway Protocol (BGP)", specify an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK] |
|
| |
| RFC 1165 | Network Time Protocol (NTP) over the OSI Remote Operations Service |
| |
| Authors: | J. Crowcroft, J.P. Onions. |
| Date: | June 1990 |
| Formats: | txt html json |
| Status: | EXPERIMENTAL |
| DOI: | 10.17487/RFC 1165 |
|
This memo suggests an Experimental Protocol for the OSI and Internet communities. Hosts in either community, and in particular those on both are encouraged to experiment with this mechanism. |
|
| |
| 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 json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1167 |
|
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 html ps pdf json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1168 |
|
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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1169 |
|
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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1170 |
|
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 1171 | Point-to-Point Protocol for the transmission of multi-protocol datagrams over Point-to-Point links |
| |
|
|
The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is composed of three parts:
1. A method for encapsulating datagrams over serial links.
2. An extensible Link Control Protocol (LCP).
3. A family of Network Control Protocols (NCP) for establishing and configuring different network-layer protocols.
This document defines the encapsulation scheme, the basic LCP, and anNCP for establishing and configuring the Internet Protocol (IP)(called the IP Control Protocol, IPCP).
The options and facilities used by the LCP and the IPCP are defined in separate documents. Control protocols for configuring and utilizing other network-layer protocols besides IP (e.g., DECNET,OSI) are expected to be developed as needed. |
|
| |
| RFC 1172 | Point-to-Point Protocol (PPP) initial configuration options |
| |
|
|
The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is composed of
1) a method for encapsulating datagrams over serial links,2) an extensible Link Control Protocol (LCP), and3) a family of Network Control Protocols (NCP) for establishing and configuring different network-layer protocols.
The PPP encapsulating scheme, the basic LCP, and an NCP for controlling and establishing the Internet Protocol (IP) (called theIP Control Protocol, IPCP) are defined in The Point-to-Point Protocol(PPP) [1].
This document defines the intial options used by the LCP and IPCP. It also defines a method of Link Quality Monitoring and a simple authentication scheme. |
|
| |
| 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 json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1173 |
|
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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1174 |
|
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 html json |
| Also: | FYI 0003 |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1175 |
|
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 1176 | Interactive Mail Access Protocol: Version 2 |
| |
|
|
This RFC suggests a method for personal computers and workstations to dynamically access mail from a mailbox server ("repository"). It obosoletes RFC 1064. This RFC specifies an Experimental Protocol for the Internet community. Discussion and suggestions for improvement are requested. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. |
|
| |
| 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 json html |
| Obsoleted by: | RFC 1206 |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1177 |
|
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 |
| |
|
|
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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1179 |
|
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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1180 |
|
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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1181 |
|
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 1183 | New DNS RR Definitions |
| |
|
|
This memo defines five new DNS types for experimental purposes. This RFC describes an Experimental Protocol for the Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 1184 | Telnet Linemode Option |
| |
|
|
This RFC specifies a procedure for line at a time terminal interaction based on the Telnet Protocol. It obsoletes RFC 1116. [STANDARDS-TRACK] |
|
| |
| RFC 1185 | TCP Extension for High-Speed Paths |
| |
| Authors: | V. Jacobson, R.T. Braden, L. Zhang. |
| Date: | October 1990 |
| Formats: | txt html json |
| Obsoleted by: | RFC 1323 |
| Status: | EXPERIMENTAL |
| DOI: | 10.17487/RFC 1185 |
|
This memo describes an Experimental Protocol extension to TCP for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. |
|
| |
| RFC 1186 | MD4 Message Digest Algorithm |
| |
|
|
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 1187 | Bulk Table Retrieval with the SNMP |
| |
| Authors: | M.T. Rose, K. McCloghrie, J.R. Davin. |
| Date: | October 1990 |
| Formats: | txt json html |
| Status: | EXPERIMENTAL |
| DOI: | 10.17487/RFC 1187 |
|
This memo reports an interesting family of algorithms for bulk table retrieval using the Simple Network Management Protocol (SNMP). This memo describes an Experimental Protocol for the Internet community, and requests discussion and suggestions for improvements. This memo does not specify a standard for the Internet community. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. |
|
| |
| RFC 1188 | Proposed Standard for the Transmission of IP Datagrams over FDDI Networks |
| |
|
|
This document specifies a method for the use of IP and ARP on FDDI networks. The encapsulation method used is described, as well as various media-specific issues. |
|
| |
| RFC 1189 | Common Management Information Services and Protocols for the Internet (CMOT and CMIP) |
| |
| Authors: | U.S. Warrier, L. Besaw, L. LaBarre, B.D. Handspicker. |
| Date: | October 1990 |
| Formats: | txt html json |
| Obsoletes: | RFC 1095 |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1189 |
|
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 the Internet. [STANDARDS-TRACK] |
|
| |
| RFC 1190 | Experimental Internet Stream Protocol: Version 2 (ST-II) |
| |
| Authors: | C. Topolcic. |
| Date: | October 1990 |
| Formats: | txt html json |
| Obsoletes: | IEN119 |
| Obsoleted by: | RFC 1819 |
| Status: | EXPERIMENTAL |
| DOI: | 10.17487/RFC 1190 |
|
This memo defines a revised version of the Internet Stream Protocol, originally defined in IEN-119 [8], based on results from experiments with the original version, and subsequent requests, discussion, and suggestions for improvements. This is a Limited-Use Experimental Protocol. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. |
|
| |
| RFC 1191 | Path MTU discovery |
| |
|
|
This memo describes a technique for dynamically discovering the maximum transmission unit (MTU) of an arbitrary internet path. It specifies a small change to the way routers generate one type of ICMP message. For a path that passes through a router that has not been so changed, this technique might not discover the correct Path MTU, but it will always choose a Path MTU as accurate as, and in many cases more accurate than, the Path MTU that would be chosen by current practice. |
|
| |
| RFC 1192 | Commercialization of the Internet summary report |
| |
| Authors: | B. Kahin. |
| Date: | November 1990 |
| Formats: | txt json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1192 |
|
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 json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1193 |
|
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 1194 | Finger User Information Protocol |
| |
|
|
This memo describes the Finger User Information Protocol. This is a simple protocol which provides an interface to a remote user information program.
Based on RFC 742, a description of the original Finger protocol, this memo attempts to clarify the expected communication between the two ends of a Finger connection. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition. |
|
| |
| RFC 1195 | Use of OSI IS-IS for routing in TCP/IP and dual environments |
| |
|
|
This RFC specifies an integrated routing protocol, based on the OSIIntra-Domain IS-IS Routing Protocol, which may be used as an interior gateway protocol (IGP) to support TCP/IP as well as OSI. This allows a single routing protocol to be used to support pure IP environments, pure OSI environments, and dual environments. This specification was developed by the IS-IS working group of the Internet Engineering TaskForce.
The OSI IS-IS protocol has reached a mature state, and is ready for implementation and operational use. The most recent version of theOSI IS-IS protocol is contained in ISO DP 10589 [1]. The proposed standard for using IS-IS for support of TCP/IP will therefore make use of this version (with a minor bug correction, as discussed inAnnex B). We expect that future versions of this proposed standard will upgrade to the final International Standard version of IS-IS when available.
Comments should be sent to "isis@merit.edu". |
|
| |
| RFC 1196 | Finger User Information Protocol |
| |
|
|
This memo describes the Finger User Information Protocol. This is a simple protocol which provides an interface to a remote user information program.
Based on RFC 742, a description of the original Finger protocol, this memo attempts to clarify the expected communication between the two ends of a Finger connection. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition. This edition corrects and clarifies in a minor way, RFC 1194. |
|
| |
| RFC 1197 | Using ODA for translating multimedia information |
| |
| Authors: | M. Sherman. |
| Date: | December 1990 |
| Formats: | txt json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1197 |
|
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 |
| |
|
|
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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1199 |
|
|
|
