| |
| RFC 1200 | IAB official protocol standards |
| |
| Authors: | Defense Advanced Research Projects Agency, Internet Activities Board. |
| Date: | April 1991 |
| Formats: | txt html json |
| Obsoletes: | RFC 1140 |
| Obsoleted by: | RFC 1250 |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1200 |
|
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. |
|
| |
| RFC 1201 | Transmitting IP traffic over ARCNET networks |
| |
|
|
This memo defines a protocol for the transmission of IP and ARP packets over the ARCnet Local Area Network.This memo specifies a method of encapsulating Internet Protocol (IP) and Address Resolution Protocol (ARP) datagrams for transmission across ARCNET using the "ARCNET Packet Header Definition Standard". [STANDARDS-TRACK] |
|
| |
| RFC 1202 | Directory Assistance service |
| |
| Authors: | M.T. Rose. |
| Date: | February 1991 |
| Formats: | txt json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1202 |
|
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 1203 | Interactive Mail Access Protocol: Version 3 |
| |
|
|
This RFC suggests a method for workstations to access mail dynamically from a mailbox server ("repository"). The following document is a modified version of RFC 1064, the definition of the IMAP2 protocol. This RFC specifies an Experimental Protocol for the Internet community. It does not specify any standard. |
|
| |
| RFC 1204 | Message Posting Protocol (MPP) |
| |
| Authors: | S. Yeh, D. Lee. |
| Date: | February 1991 |
| Formats: | txt html json |
| Status: | EXPERIMENTAL |
| DOI: | 10.17487/RFC 1204 |
|
This memo describes a protocol for posting messages from workstations (e.g., PCs) to a mail service host. This RFC specifies an Experimental Protocol for the Internet community. It does not specify any standard. |
|
| |
| RFC 1205 | 5250 Telnet interface |
| |
|
|
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 |
| |
|
|
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 json html |
| Also: | FYI 0007 |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1207 |
|
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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1208 |
|
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 1209 | The Transmission of IP Datagrams over the SMDS Service |
| |
|
|
This memo describes an initial use of IP and ARP in an SMDS service environment configured as a logical IP subnetwork, LIS (described below). The encapsulation method used is described, as well as various service-specific issues. This memo does not preclude subsequent treatment of the SMDS Service in configurations other thanLIS; specifically, public or inter-company, inter-enterprise configurations may be treated differently and will be described in future documents. This document considers only directly connected IP end-stations or routers; issues raised by MAC level bridging are beyond the scope of this paper. |
|
| |
| 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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1210 |
|
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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1211 |
|
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 1212 | Concise MIB definitions |
| |
|
|
This memo describes a straight-forward approach toward producing concise, yet descriptive, MIB modules. This memo defines a format for producing MIB modules. [STANDARDS-TRACK] |
|
| |
| RFC 1213 | 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. [STANDARDS-TRACK] |
|
| |
| RFC 1214 | OSI internet management: Management Information Base |
| |
| Authors: | L. LaBarre. |
| Date: | April 1991 |
| Formats: | txt html json |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1214 |
|
This RFC documents a MIB for use with CMIP, either over pure OSI stacks or with the CMIP over TCP specification. It redefines objects comprised by the second revision of the Management Information Base for Network Management of TCP/IP-based internets: MIB-II so as to conform to the OSI structure of management information. This document is a product of the IETF OIM working group. |
|
| |
| RFC 1215 | Convention for defining traps for use with the SNMP |
| |
| Authors: | M.T. Rose. |
| Date: | March 1991 |
| Formats: | txt html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1215 |
|
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: | 1 April 1991 |
| Formats: | txt json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1216 |
|
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: | 1 April 1991 |
| Formats: | txt json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1217 |
|
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 |
| |
|
|
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 1991 |
| Formats: | txt html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1219 |
|
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 1220 | Point-to-Point Protocol extensions for bridging |
| |
|
|
This document defines an extension of the Internet Point-to-Point Protocol (PPP) described in RFC 1171, targeting the use of Point-to- Point lines for Remote Bridging. [STANDARDS-TRACK] |
|
| |
| RFC 1221 | Host Access Protocol (HAP) specification: Version 2 |
| |
|
|
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 json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1222 |
|
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 json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1223 |
|
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 1224 | Techniques for managing asynchronously generated alerts |
| |
| Authors: | L. Steinberg. |
| Date: | May 1991 |
| Formats: | txt html json |
| Status: | EXPERIMENTAL |
| DOI: | 10.17487/RFC 1224 |
|
This RFC explores mechanisms to prevent a remotely managed entity from burdening a manager or network with an unexpected amount of network management information, and to ensure delivery of "important" information. The focus is on controlling the flow of asynchronously generated information, and not how the information is generated. |
|
| |
| RFC 1225 | Post Office Protocol: Version 3 |
| |
|
|
This memo suggests a simple method for workstations to dynamically access mail from a mailbox server. [STANDARDS-TRACK] |
|
| |
| RFC 1226 | Internet protocol encapsulation of AX.25 frames |
| |
| Authors: | B. Kantor. |
| Date: | May 1991 |
| Formats: | txt json html |
| Status: | EXPERIMENTAL |
| DOI: | 10.17487/RFC 1226 |
|
This memo describes a method for the encapsulation of AX.25 (the Amateur Packet-Radio Link-Layer Protocol) frames within IP packets. This technique is an Experimental Protocol for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1227 | SNMP MUX protocol and MIB |
| |
|
|
This memo suggests a mechanism by which a user process may associate itself with the local SNMP agent on a host, in order to implement portions of the MIB. This mechanism would be local to the host.This is an Experimental Protocol for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1228 | SNMP-DPI: Simple Network Management Protocol Distributed Program Interface |
| |
|
|
This RFC describes a protocol that International Business Machines Corporation (IBM) has been implementing in most of its SNMP agents to allow dynamic extension of supported MIBs. This is an Experimental Protocol for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1229 | Extensions to the generic-interface MIB |
| |
|
|
This RFC contains definitions of managed objects used as experimental extensions to the generic interfaces structure of MIB-II. [STANDARDS- TRACK] |
|
| |
| RFC 1230 | IEEE 802.4 Token Bus MIB |
| |
|
|
This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, this memo defines managed objects used for managing subnetworks which use the IEEE 802.4 Token Bus technology described in 802.4 Token-Passing Bus Access Method and Physical Layer Specifications, IEEE Standard 802.4. [STANDARDS-TRACK] |
|
| |
| RFC 1231 | IEEE 802.5 Token Ring MIB |
| |
|
|
This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, this memo defines managed objects used for managing subnetworks which use the IEEE 802.5 Token Ring technology described in 802.5 Token Ring Access Method and Physical Layer Specifications, IEEE Standard 802.5-1989. [STANDARDS-TRACK] |
|
| |
| RFC 1232 | Definitions of managed objects for the DS1 Interface type |
| |
|
| |
| RFC 1233 | Definitions of managed objects for the DS3 Interface type |
| |
|
|
This memo defines objects for managing DS3 Interface objects for use with the SNMP protocol. [STANDARDS-TRACK] |
|
| |
| RFC 1234 | Tunneling IPX traffic through IP networks |
| |
|
|
This memo describes a method of encapsulating IPX datagrams within UDP packets so that IPX traffic can travel across an IP internet. [STANDARDS-TRACK] This memo defines objects for managing DS1 Interface objects for use with the SNMP protocol. [STANDARDS-TRACK] |
|
| |
| RFC 1235 | Coherent File Distribution Protocol |
| |
| Authors: | J. Ioannidis, G. Maguire. |
| Date: | June 1991 |
| Formats: | txt html json |
| Status: | EXPERIMENTAL |
| DOI: | 10.17487/RFC 1235 |
|
This memo describes the Coherent File Distribution Protocol (CFDP). This is an Experimental Protocol 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 json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1236 |
|
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 1237 | Guidelines for OSI NSAP Allocation in the Internet |
| |
|
|
This paper provides guidelines for allocating NSAPs in the Internet.[STANDARDS-TRACK] |
|
| |
| RFC 1238 | CLNS MIB for use with Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) |
| |
|
|
This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. This is an Experimental Protocol for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1239 | Reassignment of experimental MIBs to standard MIBs |
| |
|
|
This memo specifically updates RFC 1229, RFC 1230, RFC 1231, RFC 1232 and RFC 1233 with new codes. [STANDARDS-TRACK] |
|
| |
| RFC 1240 | OSI connectionless transport services on top of UDP: Version 1 |
| |
| Authors: | C. Shue, W. Haggerty, K. Dobbins. |
| Date: | June 1991 |
| Formats: | txt json html |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1240 |
|
This document describes a protocol for running OSI Connectionless service on UDP. [STANDARDS-TRACK] |
|
| |
| RFC 1241 | Scheme for an internet encapsulation protocol: Version 1 |
| |
| Authors: | R.A. Woodburn, D.L. Mills. |
| Date: | July 1991 |
| Formats: | txt json pdf ps html |
| Status: | EXPERIMENTAL |
| DOI: | 10.17487/RFC 1241 |
|
This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1242 | Benchmarking Terminology for Network Interconnection Devices |
| |
|
|
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 1243 | AppleTalk Management Information Base |
| |
|
|
This memo defines objects for managing AppleTalk objects for use with the SNMP protocol. [STANDARDS-TRACK] |
|
| |
| RFC 1244 | Site Security Handbook |
| |
| Authors: | J.P. Holbrook, J.K. Reynolds. |
| Date: | July 1991 |
| Formats: | txt json html |
| Obsoleted by: | RFC 2196 |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1244 |
|
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 1247 | OSPF Version 2 |
| |
|
|
This memo documents version 2 of the OSPF protocol. OSPF is a link- state based routing protocol. [STANDARDS-TRACK] |
|
| |
| RFC 1248 | OSPF Version 2 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. In particular, it defines objects for managing OSPF Version 2. [STANDARDS-TRACK] |
|
| |
| RFC 1249 | DIXIE Protocol Specification |
| |
| Authors: | T. Howes, M. Smith, B. Beecher. |
| Date: | August 1991 |
| Formats: | txt json html |
| Also: | RFC 1202 |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1249 |
|
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 1250 | IAB Official Protocol Standards |
| |
|
|
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1251 | Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members |
| |
|
|
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 1252 | OSPF Version 2 Management Information Base |
| |
|
|
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS- TRACK] |
|
| |
| RFC 1253 | OSPF Version 2 Management Information Base |
| |
|
|
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS- TRACK] |
|
| |
| RFC 1254 | Gateway Congestion Control Survey |
| |
| Authors: | A. Mankin, K. Ramakrishnan. |
| Date: | August 1991 |
| Formats: | txt json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1254 |
|
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 |
| |
|
|
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 1256 | ICMP Router Discovery Messages |
| |
| Authors: | S. Deering, Ed.. |
| Date: | September 1991 |
| Formats: | txt html json |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 1256 |
|
This document specifies an extension of the Internet Control MessageProtocol (ICMP) to enable hosts attached to multicast or broadcast networks to discover the IP addresses of their neighboring routers. |
|
| |
| RFC 1257 | Isochronous applications do not require jitter-controlled networks |
| |
| Authors: | C. Partridge. |
| Date: | September 1991 |
| Formats: | txt html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1257 |
|
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 |
| |
|
|
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 json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1259 |
|
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 json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1261 |
|
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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1262 |
|
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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1263 |
|
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 1264 | Internet Engineering Task Force Internet Routing Protocol Standardization Criteria |
| |
|
|
This informational RFC presents procedures for creating and documenting Internet standards on routing protocols. These procedures have been established by the Internet Activities Board (IAB) in consultation with the Internet Engineering Steering Group (IESG). This memo provides information for the Internet community. It does not specifiy an Internet standard. |
|
| |
| RFC 1265 | BGP Protocol Analysis |
| |
| Authors: | Y. Rekhter. |
| Date: | October 1991 |
| Formats: | txt json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1265 |
|
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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1266 |
|
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 1267 | Border Gateway Protocol 3 (BGP-3) |
| |
|
|
This memo, together with its companion document, "Application of the Border Gateway Protocol in the Internet", define an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK] |
|
| |
| RFC 1268 | Application of the Border Gateway Protocol in the Internet |
| |
|
|
This document, together with its companion document, "A BorderGateway Protocol (BGP-3)", define an inter-autonomous system routing protocol for the Internet. "A Border Gateway Protocol (BGP-3)" defines the BGP protocol specification, and this document describes the usage of the BGP in the Internet.
Information about the progress of BGP can be monitored and/or reported on the BGP mailing list (iwg@rice.edu). |
|
| |
| RFC 1269 | Definitions of Managed Objects for the Border Gateway Protocol: Version 3 |
| |
| Authors: | S. Willis, J.W. Burruss. |
| Date: | October 1991 |
| Formats: | txt json html |
| Obsoleted by: | RFC 4273 |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 1269 |
|
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Border Gateway Protocol. [STANDARDS-TRACK] |
|
| |
| RFC 1270 | SNMP Communications Services |
| |
| Authors: | F. Kastenholz. |
| Date: | October 1991 |
| Formats: | txt json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1270 |
|
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 1271 | Remote Network Monitoring Management Information Base |
| |
|
|
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices. [STANDARDS-TRACK] |
|
| |
| RFC 1272 | Internet Accounting: Background |
| |
| Authors: | C. Mills, D. Hirsh, G.R. Ruth. |
| Date: | November 1991 |
| Formats: | txt html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1272 |
|
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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1273 |
|
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 1274 | The COSINE and Internet X.500 Schema |
| |
| Authors: | P. Barker, S. Kille. |
| Date: | November 1991 |
| Formats: | txt json html |
| Obsoleted by: | RFC 4524 |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 1274 |
|
This document suggests an X.500 Directory Schema, or NamingArchitecture, for use in the COSINE and Internet X.500 pilots. The schema is independent of any specific implementation. As well as indicating support for the standard object classes and attributes, a large number of generally useful object classes and attributes are also defined. An appendix to this document includes a machine processable version of the schema.
This document also proposes a mechanism for allowing the schema to evolve in line with emerging requirements. Proformas to support this process are included.
Corrections and additions to the schema should be sent to na- update@cs.ucl.ac.uk list, as described within. |
|
| |
| RFC 1275 | Replication Requirements to provide an Internet Directory using X.500 |
| |
| Authors: | S.E. Hardcastle-Kille. |
| Date: | November 1991 |
| Formats: | txt ps json pdf html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1275 |
|
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 1276 | Replication and Distributed Operations extensions to provide an Internet Directory using X.500 |
| |
| Authors: | S.E. Hardcastle-Kille. |
| Date: | November 1991 |
| Formats: | txt ps html json |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1276 |
|
Some requirements on extensions to X.500 are described in theRFC[HK91b], in order to build an Internet Directory usingX.500(1988). This document specifies a set of solutions to the problems raised. These solutions are based on some work done for the QUIPU implementation, and demonstrated to be effective in a number of directory pilots. By documenting a de facto standard, rapid progress can be made towards a full-scale pilot. These procedures are an INTERIM approach. There are known deficiencies, both in terms of manageability and scalability.Transition to standard approaches are planned when appropriate standards are available. This RFCwill be obsoleted at this point. |
|
| |
| RFC 1277 | Encoding Network Addresses to Support Operation over Non-OSI Lower Layers |
| |
| Authors: | S.E. Hardcastle-Kille. |
| Date: | November 1991 |
| Formats: | txt ps html json |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 1277 |
|
The OSI Directory specifies an encoding of Presentation Address, which utilises OSI Network Addresses as defined in the OSINetwork Layer standards [CCI88] [ISO87a]. The OSI Directory, and any OSI application utilising the OSI Directory must be able use these Network Addresses to identify end systems. Currently, OSI applications are often run over lower layers other than the OSINetwork Service. It is neither reasonable nor desirable for groups wishing to investigate and use OSI Applications in conjunction with the OSI Directory to be dependent on a globalOSI Network Service. This document defines a new network address format, and rules for using some existing network address formats. The scope of this document is: |
|
| |
| RFC 1278 | A string encoding of Presentation Address |
| |
| Authors: | S.E. Hardcastle-Kille. |
| Date: | November 1991 |
| Formats: | txt json ps html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1278 |
|
There are a number of environments where a simple string encoding of Presentation Address is desirable. This specification defines such a representation. |
|
| |
| RFC 1279 | X.500 and Domains |
| |
| Authors: | S.E. Hardcastle-Kille. |
| Date: | November 1991 |
| Formats: | txt json html ps pdf |
| Status: | EXPERIMENTAL |
| DOI: | 10.17487/RFC 1279 |
|
This RFCconsiders X.500 in relation to Internet and UK Domains.A basic model of X.500 providing a higher level and more descriptive naming structure is emphasised. In addition, a mapping of domains onto X.500 is proposed, which gives a range of new management and user facilities over and above those currently available. This specification proposes an experimental new mechanism to access and manage domain information on the Internet and in the UK Academic Community. There is no current intention to provide an operational replacement for DNS. |
|
| |
| RFC 1280 | IAB Official Protocol Standards |
| |
|
|
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1281 | Guidelines for the Secure Operation of the Internet |
| |
| Authors: | R. Pethia, S. Crocker, B. Fraser. |
| Date: | November 1991 |
| Formats: | txt json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1281 |
|
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 |
| |
|
|
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 1283 | SNMP over OSI |
| |
|
|
This memo describes mappings from the SNMP onto both the COTS and the CLTS. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet Standard. |
|
| |
| RFC 1284 | Definitions of Managed Objects for the Ethernet-like Interface Types |
| |
|
|
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing ethernet-like objects. [STANDARDS-TRACK] |
|
| |
| RFC 1285 | FDDI Management Information Base |
| |
|
|
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing devices which implement the FDDI. [STANDARDS-TRACK] |
|
| |
| RFC 1286 | Definitions of Managed Objects for Bridges |
| |
| Authors: | E. Decker, P. Langille, A. Rijsinghani, K. McCloghrie. |
| Date: | December 1991 |
| Formats: | txt html json |
| Obsoleted by: | RFC 1493, RFC 1525 |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 1286 |
|
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for managing bridges based on the IEEE 802.1d draft standard between Local Area Network (LAN) segments. This memo is an extension to the SNMP MIB. [STANDARDS-TRACK] |
|
| |
| RFC 1287 | Towards the Future Internet Architecture |
| |
| Authors: | D. Clark, L. Chapin, V. Cerf, R. Braden, R. Hobby. |
| Date: | December 1991 |
| Formats: | txt html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1287 |
|
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 1288 | The 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 RFC 1196. |
|
| |
| RFC 1289 | DECnet Phase IV MIB Extensions |
| |
|
|
This memo defines a set of DECnet Phase IV extensions that have been created for the Internet MIB. When used in conjunction with the structure of management information (RFC 1155), the management information base for network management of TCP/IP-based internets(RFC 1213) and the Simple Network Management Protocol (RFC 1157), it will be possible to provide integrated network management of combinedTCP/IP and DECnet Phase IV based internets. This document was produced by the DECnet Phase IV MIB working group of the InternetEngineering Task Force (IETF). |
|
| |
| RFC 1290 | There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places |
| |
|
|
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 json ps html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1291 |
|
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 |
| |
|
|
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 1293 | Inverse Address Resolution Protocol |
| |
| Authors: | T. Bradley, C. Brown. |
| Date: | January 1992 |
| Formats: | txt html json |
| Obsoleted by: | RFC 2390 |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 1293 |
|
This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK] |
|
| |
| RFC 1294 | Multiprotocol Interconnect over Frame Relay |
| |
|
|
This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. [STANDARDS-TRACK] |
|
| |
| 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 json html |
| Obsoleted by: | RFC 1417 |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1295 |
|
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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1296 |
|
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 html json |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1297 |
|
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 json html |
| Obsoleted by: | RFC 1420 |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1298 |
|
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 json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1299 |
|
|
|
