| |
| RFC 1000 | Request For Comments reference guide |
| |
|
|
This RFC Reference Guide is intended to provide a historical account by categorizing and summarizing of the Request for Comments numbers 1 through 999 issued between the years 1969-1987. These documents have been crossed referenced to indicate which RFCs are current, obsolete, or revised. |
|
| |
| RFC 1001 | Protocol standard for a NetBIOS service on a TCP/UDP transport: Concepts and methods |
| |
| Authors: | NetBIOS Working Group in the Defense Advanced Research Projects Agency, Internet Activities Board, End-to-End Services Task Force. |
| Date: | March 1987 |
| Formats: | txt html json |
| Also: | STD 0019 |
| Status: | INTERNET STANDARD |
| DOI: | 10.17487/RFC 1001 |
|
This RFC defines a proposed standard protocol to support NetBIOS services in a TCP/IP environment. Both local network and internet operation are supported. Various node types are defined to accommodate local and internet topologies and to allow operation with or without the use of IP broadcast. This RFC describes the NetBIOS-over-TCP protocols in a general manner, emphasizing the underlying ideas and techniques. Detailed specifications are found in a companion RFC, "Protocol Standard For a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications". |
|
| |
| RFC 1002 | Protocol standard for a NetBIOS service on a TCP/UDP transport: Detailed specifications |
| |
| Authors: | NetBIOS Working Group in the Defense Advanced Research Projects Agency, Internet Activities Board, End-to-End Services Task Force. |
| Date: | March 1987 |
| Formats: | txt json html |
| Also: | STD 0019 |
| Status: | INTERNET STANDARD |
| DOI: | 10.17487/RFC 1002 |
|
This RFC defines a proposed standard protocol to support NetBIOS services in a TCP/IP environment. Both local network and internet operation are supported. Various node types are defined to accommodate local and internet topologies and to allow operation with or without the use of IP broadcast. This RFC gives the detailed specifications of the netBIOS-over-TCP packets, protocols, and defined constants and variables. A more general overview is found in a companion RFC, "Protocol Standard For NetBIOS Service on TCP/UDP Transport: Concepts and Methods". |
|
| |
| RFC 1003 | Issues in defining an equations representation standard |
| |
|
|
This memo is intended to identify and explore issues in defining a standard for the exchange of mathematical equations. No attempt is made at a complete definition and more questions are asked than are answered. Questions about the user interface are only addressed to the extent that they affect interchange issues. |
|
| |
| RFC 1004 | Distributed-protocol authentication scheme |
| |
| Authors: | D.L. Mills. |
| Date: | April 1987 |
| Formats: | txt html json |
| Status: | EXPERIMENTAL |
| DOI: | 10.17487/RFC 1004 |
|
The purpose of this RFC is to focus discussion on authentication problems in the Internet and possible methods of solution. The proposed solutions this document are not intended as standards for the Internet at this time. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to authentication problems, leading eventually to the adoption of standards. This document suggests mediated access-control and authentication procedures suitable for those cases when an association is to be set up between users belonging to different trust environments. |
|
| |
| RFC 1005 | ARPANET AHIP-E Host Access Protocol (enhanced AHIP) |
| |
| Authors: | A. Khanna, A.G. Malis. |
| Date: | May 1987 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1005 |
|
This RFC is a proposed specification for the encoding of Class A IP addresses for use on ARPANET-style networks such as the Milnet and Arpanet, and for enhancements to the ARPANET AHIP Host Access Protocol (AHIP; formerly known as 1822). These enhancements increase the size of the PSN field, allow ARPANET hosts to use logical names to address each other, allow for the communication of type-of-service information from the host to the PSN and enable the PSN to provide congestion feedback to the host on a connection basis. |
|
| |
| RFC 1006 | ISO Transport Service on top of the TCP Version: 3 |
| |
|
|
This memo specifies a standard for the Internet community. Hosts on the Internet that choose to implement ISO transport services on top of the TCP are expected to adopt and implement this standard. TCP port 102 is reserved for hosts which implement this standard. This memo specifies version 3 of the protocol and supersedes RFC-983. Changes between the protocol is described in RFC-983 and this memo are minor, but unfortunately incompatible. |
|
| |
| RFC 1007 | Military supplement to the ISO Transport Protocol |
| |
|
|
This document supplements the Transport Service and Protocol of the International Standards Organization (ISO), IS 8072 and IS 8073, respectively, and their formal descriptions by providing conventions, option selections and parameter values. This RFC is being distributed to members of the Internet community in order to solicit comments on the Draft Military Supplement. While this document may not be directly relevant to the research problems of the Internet, it may be of some interest to a number of researchers and implementors. |
|
| |
| RFC 1008 | Implementation guide for the ISO Transport Protocol |
| |
|
|
This RFC is being distributed to members of the Internet community in order to solicit comments on the Implementors Guide. While this document may not be directly relevant to the research problems of the Internet, it may be of some interest to a number of researchers and implementors. |
|
| |
| RFC 1009 | Requirements for Internet gateways |
| |
|
|
This RFC summarizes the requirements for gateways to be used between networks supporting the Internet protocols. This document is a formal statement of the requirements to be met by gateways used in the Internet system. As such, it is an official specification for the Internet community. |
|
| |
| RFC 1010 | Assigned numbers |
| |
|
|
This memo is an official status report on the numbers used in protocols in the Internet community. It documents the currently assigned values from several series of numbers including link, socket, port, and protocol, used in network protocol implementations. |
|
| |
| RFC 1011 | Official Internet protocols |
| |
|
|
This memo is an official status report on the protocols used in the Internet community. It identifies the documents specifying the official protocols used in the Internet. Comments indicate any revisions or changes planned. |
|
| |
| RFC 1012 | Bibliography of Request For Comments 1 through 999 |
| |
| Authors: | J.K. Reynolds, J. Postel. |
| Date: | June 1987 |
| Formats: | txt json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1012 |
|
This RFC is a reference guide for the Internet community which provides a bibliographic summary of the Request for Comments numbers 1 through 999 issued between the years 1969-1987. |
|
| |
| RFC 1013 | X Window System Protocol, version 11: Alpha update April 1987 |
| |
| Authors: | R.W. Scheifler. |
| Date: | June 1987 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1013 |
|
This RFC is distributed to the Internet community for information only. It does not establish an Internet standard. The X window system has been widely reviewed and tested. The Internet community is encouraged to experiment with it. |
|
| |
| RFC 1014 | XDR: External Data Representation standard |
| |
| Authors: | Sun Microsystems. |
| Date: | June 1987 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1014 |
|
XDR is a standard for the description and encoding of data. It is useful for transferring data between different computer architectures. XDR fits into ISO presentation layer, and is roughly analogous in purpose to X.409, ISO Abstract Syntax Notation. The major difference between these two is that XDR uses implicit typing, while X.409 uses explicit typing. This RFC is distributed for information only, it does not establish a Internet standard. |
|
| |
| RFC 1015 | Implementation plan for interagency research Internet |
| |
|
|
This RFC proposes an Interagency Research Internet as the natural outgrowth of the current Internet. This is an "idea paper" and discussion is strongly encouraged. |
|
| |
| RFC 1016 | Something a Host Could Do with Source Quench: The Source Quench Introduced Delay (SQuID) |
| |
| Authors: | W. Prue, J. Postel. |
| Date: | July 1987 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1016 |
|
The memo is intended to explore the issue of what a host could do with a source quench. The proposal is for each source host IP module to introduce some delay between datagrams sent to the same destination host. This is a "crazy idea paper" and discussion is essential. |
|
| |
| RFC 1017 | Network requirements for scientific research: Internet task force on scientific computing |
| |
| Authors: | B.M. Leiner. |
| Date: | August 1987 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1017 |
|
This RFC identifies the requirements on communication networks for supporting scientific research. It proposes some specific areas for near term work, as well as some long term goals. This is an "idea" paper and discussion is strongly encouraged. |
|
| |
| RFC 1018 | Some comments on SQuID |
| |
| Authors: | A.M. McKenzie. |
| Date: | August 1987 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1018 |
|
This memo is a discussion of some of the ideas expressed in RFC-1016 on Source Quench. This memo introduces the distinction of the cause of congestion in a gateway between the effects of "Funneling" and Mismatch". It is offered in the same spirit as RFC-1016; to stimulate discussion. The opinions offered are personal, not corporate, opinions. |
|
| |
| RFC 1019 | Report of the Workshop on Environments for Computational Mathematics |
| |
| Authors: | D. Arnon. |
| Date: | September 1987 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1019 |
|
This memo is a report on the discussion of the representation of equations in a workshop at the ACM SIGGRAPH Conference held in Anaheim, California on 30 July 1987. |
|
| |
| RFC 1020 | Internet numbers |
| |
|
|
This RFC is a list of the Assigned IP Network Numbers and EGP Autonomous System Numbers. This RFC obsoletes RFC-997. |
|
| |
| RFC 1021 | High-level Entity Management System (HEMS) |
| |
| Authors: | C. Partridge, G. Trewitt. |
| Date: | October 1987 |
| Formats: | txt html json |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1021 |
|
This memo provides a general overview of the High-level Entity management system (HEMS). This system is experimental, and is currently being tested in portions of the Internet. |
|
| |
| RFC 1022 | High-level Entity Management Protocol (HEMP) |
| |
| Authors: | C. Partridge, G. Trewitt. |
| Date: | October 1987 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1022 |
|
This memo presents an application protocol for managing network entities such as hosts, gateways, and front end machines. This protocol is a component of the High-level Entity Management System HEMS), described is RFC-1021. This memo also assumes a knowledge of the ISO data encoding standard, ASN.1. |
|
| |
| RFC 1023 | HEMS monitoring and control language |
| |
|
|
This RFC specifies the High-Level Entity Management System (HEMS) Monitoring and Control Language. This language defines the requests and replies used in HEMS. This memo assumes knowledge of the HEMS system described in RFC-1021, and of the ISO data encoding standard, ASN.1. |
|
| |
| RFC 1024 | HEMS variable definitions |
| |
| Authors: | C. Partridge, G. Trewitt. |
| Date: | October 1987 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1024 |
|
This memo assigns instruction codes, defines object formats and object semantics for use with the High-Level Monitoring and Control Language, defined in RFC-1023. A general system has been described in previous memos (RFC-1021, RFC-1022). This system is called the High-Level Entity Management System (HEMS). This memo is provisional and the definitions are subject to change. Readers should confirm with the authors that they have the most recent version. This RFC assumes a working knowledge of the ISO data encoding standard, ASN.1, and a general understanding of the IP protocol suite. |
|
| |
| RFC 1025 | TCP and IP bake off |
| |
| Authors: | J. Postel. |
| Date: | September 1987 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1025 |
|
This memo describes some of the procedures, scoring and tests used in the TCP and IP bake offs held in the early development of these protocols. These procedures and tests may still be of use in testing newly implemented TCP and IP modules. |
|
| |
| RFC 1026 | Addendum to RFC 987: (Mapping between X.400 and RFC-822) |
| |
|
|
This memo suggest a proposed protocol for the Internet community, and request discussion and suggestions for improvements. |
|
| |
| RFC 1027 | Using ARP to implement transparent subnet gateways |
| |
| Authors: | S. Carl-Mitchell, J.S. Quarterman. |
| Date: | October 1987 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1027 |
|
This RFC describes the use of the Address Resolution Protocol (ARP) by subnet gateways to permit hosts on the connected subnets to communicate without being aware of the existence of subnets, using the technique of "Proxy ARP". |
|
| |
| RFC 1028 | Simple Gateway Monitoring Protocol |
| |
| Authors: | J. Davin, J.D. Case, M. Fedor, M.L. Schoffstall. |
| Date: | November 1987 |
| Formats: | txt html json |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1028 |
|
This memo defines a simple application-layer protocol by which management information for a gateway may be inspected or altered by remote users. This proposal is intended only as an interim response to immediate gateway monitoring needs. |
|
| |
| RFC 1029 | More fault tolerant approach to address resolution for a Multi-LAN system of Ethernets |
| |
|
|
This memo discusses an extension to a Bridge Protocol to detect and disclose changes in heighbouring host address parameters in a Multi-Lan system of Ethernets. The problem is one which is appearing more and more regularly as the interconnected systems grow larger on Campuses and in Commercial Institutions. This RFC suggests a protocol enhancement for the Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 1030 | On testing the NETBLT Protocol over divers networks |
| |
| Authors: | M.L. Lambert. |
| Date: | November 1987 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1030 |
|
This memo describes the results gathered from testing NETBLT over three networks of different bandwidths and round-trip delays. The results are not complete, but the information gathered so far has not been promising. The NETBLT protocol is specified in RFC-998; this document assumes an understanding of the specification as described in RFC-998. |
|
| |
| RFC 1031 | MILNET name domain transition |
| |
| Authors: | W.D. Lazear. |
| Date: | November 1987 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1031 |
|
This RFC consolidates information necessary for the implementation of domain style names throughout the DDN/MILNET Internet community. The introduction of domain style names will impact all hosts in the DDN/MILNET Internet. This RFC is designed as an aid to implementors and administrators by providing: 1) an overview of the transition process from host tables to domains, 2) a timetable for the transition, and 3) references to documentation and software relating to the domain system. |
|
| |
| RFC 1032 | Domain administrators guide |
| |
| Authors: | M.K. Stahl. |
| Date: | November 1987 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1032 |
|
Domains are administrative entities that provide decentralized management of host naming and addressing. The domain-naming system is distributed and hierarchical. This memo describes procedures for registering a domain with the Network Information Center (NIC) of Defense Data Network (DDN), and offers guidelines on the establishment and administration of a domain in accordance with the requirements specified in RFC-920. It is recommended that the guidelines described in this document be used by domain administrators in the establishment and control of second-level domains. The role of the domain administrator (DA) is that of coordinator, manager, and technician. If his domain is established at the second level or lower in the tree, the domain administrator must register by interacting with the management of the domain directly above this. |
|
| |
| RFC 1033 | Domain Administrators Operations Guide |
| |
| Authors: | M. Lottor. |
| Date: | November 1987 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1033 |
|
This RFC provides guidelines for domain administrators in operating a domain server and maintaining their portion of the hierarchical database. Familiarity with the domain system is assumed (see RFCs 1031, 1032, 1034, and 1035). |
|
| |
| RFC 1034 | Domain names - concepts and facilities |
| |
| Authors: | P. Mockapetris. |
| Date: | November 1987 |
| Formats: | txt html json |
| Obsoletes: | RFC 0973, RFC 0882, RFC 0883 |
| Updated by: | RFC 1101, RFC 1183, RFC 1348, RFC 1876, RFC 1982, RFC 2065, RFC 2181, RFC 2308, RFC 2535, RFC 4033, RFC 4034, RFC 4035, RFC 4343, RFC 4035, RFC 4592, RFC 5936, RFC 8020, RFC 8482, RFC 8767, RFC 9471 |
| Also: | STD 0013 |
| Status: | INTERNET STANDARD |
| DOI: | 10.17487/RFC 1034 |
|
This RFC is the revised basic definition of The Domain Name System. It obsoletes RFC-882. This memo describes the domain style names and their used for host address look up and electronic mail forwarding. It discusses the clients and servers in the domain name system and the protocol used between them. |
|
| |
| RFC 1035 | Domain names - implementation and specification |
| |
| Authors: | P. Mockapetris. |
| Date: | November 1987 |
| Formats: | txt html json |
| Obsoletes: | RFC 0973, RFC 0882, RFC 0883 |
| Updated by: | RFC 1101, RFC 1183, RFC 1348, RFC 1876, RFC 1982, RFC 1995, RFC 1996, RFC 2065, RFC 2136, RFC 2181, RFC 2137, RFC 2308, RFC 2535, RFC 2673, RFC 2845, RFC 3425, RFC 3658, RFC 4033, RFC 4034, RFC 4035, RFC 4343, RFC 5936, RFC 5966, RFC 6604, RFC 7766, RFC 8482, RFC 8490, RFC 8767 |
| Also: | STD 0013 |
| Status: | INTERNET STANDARD |
| DOI: | 10.17487/RFC 1035 |
|
This RFC is the revised specification of the protocol and format used in the implementation of the Domain Name System. It obsoletes RFC-883. This memo documents the details of the domain name client - server communication. |
|
| |
| RFC 1036 | Standard for interchange of USENET messages |
| |
|
|
This RFC defines the standard format for the interchange of network News messages among USENET hosts. It updates and replaces RFC-850, reflecting version B2.11 of the News program. This memo is distributed as an RFC to make this information easily accessible to the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1037 | NFILE - a file access protocol |
| |
| Authors: | B. Greenberg, S. Keene. |
| Date: | December 1987 |
| Formats: | txt json html |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1037 |
|
This document includes a specification of the NFILE file access protocol and its underlying levels of protocol, the Token List Transport Layer and Byte Stream with Mark. The goal of this specification is to promote discussion of the ideas described here, and to encourage designers of future file protocols to take advantage of these ideas. A secondary goal is to make the specification available to sites that might benefit from implementing NFILE. |
|
| |
| RFC 1038 | Draft revised IP security option |
| |
|
|
This memo is a pre-publication draft of the revised Internet Protocol Security Option. This RFC reflects the version as approved by the Protocol Standards Steering group, and is provided for informational purposes only. The final version of this document will be available from Navy publications and should not differ from this document in any major fashion. This document will be published as a change to the MIL- STD 1777, "Internet Protocol". |
|
| |
| RFC 1039 | DoD statement on Open Systems Interconnection protocols |
| |
|
|
This RFC reproduces a memorandum issued on 2-JUL-87 from the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASDC31) to the Director of the Defense Communications Agency (DCA). This memo is distributed for information only. |
|
| |
| RFC 1040 | Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures |
| |
|
|
This RFC is the Outgrowth of a series of IAB Privacy Task Force meetings and of internal working papers distributed for those meetings. This memo defines message encipherment and authentication procedures, as the initial phase of an effort to provide privacy enhancement services for electronic mail transfer in the Internet. Detailed key management mechanisms to support these procedures will be defined in a subsequent RFC. As a goal of this initial phase, it is intended that the procedures defined here be compatible with a wide range of key management approaches, including both conventional (symmetric) and public-key (asymmetric) approaches for encryption of data encrypting keys. Use of conventional cryptography for message text encryption and/or integrity check computation is anticipated. |
|
| |
| RFC 1041 | Telnet 3270 regime option |
| |
|
|
This RFC specifies a proposed standard for the Internet community. Hosts on the Internet that want to support 3270 data stream within the Telnet protocol, are expected to adopt and implement this standard. |
|
| |
| RFC 1042 | Standard for the transmission of IP datagrams over IEEE 802 networks |
| |
|
|
This RFC specifies a standard method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on IEEE 802 Networks to allow compatible and interoperable implementations. This RFC specifies a protocol standard for the Internet community. |
|
| |
| RFC 1043 | Telnet Data Entry Terminal option: DODIIS implementation |
| |
| Authors: | A. Yasuda, T. Thompson. |
| Date: | February 1988 |
| Formats: | txt html json |
| Updates: | RFC 0732 |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 1043 |
|
This RFC suggests a proposed protocol on the TELNET Data Entry Terminal (DET) Option - DODIIS Implementation for the Internet community. It is intended that this specification be capatible with the specification of DET Option in RFC-732. Discussion and suggests for improvements are encouraged. |
|
| |
| RFC 1044 | Internet Protocol on Network System's HYPERchannel: Protocol Specification |
| |
|
|
This memo intends to provide a complete discussion of the protocols and techniques used to embed DoD standard Internet Protocol datagrams (and its associated higher level protocols) on Network Systems Corporation's HYPERchannel equipment. This document is directed toward network planners and implementors who are already familiar with the TCP/IP protocol suite and the techniques used to carry TCP/IP traffic on common networks such as the DDN or the Ethernet. No great familiarity with NSC products is assumed; an appendix is devoted to a review of NSC technologies and protocols. |
|
| |
| RFC 1045 | VMTP: Versatile Message Transaction Protocol: Protocol specification |
| |
| Authors: | D.R. Cheriton. |
| Date: | February 1988 |
| Formats: | txt json html |
| Status: | EXPERIMENTAL |
| DOI: | 10.17487/RFC 1045 |
|
This memo specifies the Versatile Message Transaction Protocol (VMTP) [Version 0.7 of 19-Feb-88], a transport protocol specifically designed to support the transaction model of communication, as exemplified by remote procedure call (RPC). The full function of VMTP, including support for security, real-time, asynchronous message exchanges, streaming, multicast and idempotency, provides a rich selection to the VMTP user level. Subsettability allows the VMTP module for particular clients and servers to be specialized and simplified to the services actually required. Examples of such simple clients and servers include PROM network bootload programs, network boot servers, data sensors and simple controllers, to mention but a few examples. This RFC describes a protocol proposed as a standard for the Internet community. |
|
| |
| RFC 1046 | Queuing algorithm to provide type-of-service for IP links |
| |
| Authors: | W. Prue, J. Postel. |
| Date: | February 1988 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1046 |
|
This memo is intended to explore how Type-of-Service might be implemented in the Internet. The proposal describes a method of queuing which can provide the different classes of service. The technique also prohibits one class of service from consuming excessive resources or excluding other classes of service. This is an "idea paper" and discussion is strongly encouraged. |
|
| |
| RFC 1047 | Duplicate messages and SMTP |
| |
| Authors: | C. Partridge. |
| Date: | February 1988 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1047 |
|
An examination of a synchronization problem in the Simple Mail Transfer Protocol (SMTP) is presented. This synchronization problem can cause a message to be delivered multiple times. A method for avoiding this problem is suggested. Nodding familiarity with the SMTP specification, RFC-821, is required. |
|
| |
| RFC 1048 | BOOTP vendor information extensions |
| |
|
|
This memo proposes an addition to the Bootstrap Protocol (BOOTP). Comments and suggestions for improvements are sought. |
|
| |
| RFC 1049 | Content-type header field for Internet messages |
| |
| Authors: | M.A. Sirbu. |
| Date: | March 1988 |
| Formats: | txt json html |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1049 |
|
This memo suggests proposed additions to the Internet Mail Protocol, RFC-822, for the Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 1050 | RPC: Remote Procedure Call Protocol specification |
| |
|
|
This memo specifies a message protocol used in implementing Sun's Remote Procedure Call (RPC) package. This RFC describes a standard that Sun Microsystems and others are using and is one they wish to propose for the Internet's consideration. It is not an Internet standard at this time. |
|
| |
| RFC 1051 | Standard for the transmission of IP datagrams and ARP packets over ARCNET networks |
| |
|
|
This memo specifies a standard method of encapsulating Internet Protocol (IP) and Address Resolution Protocol (ARP) datagrams on an ARCNET. This RFC is a standard protocol for the Internet community. |
|
| |
| RFC 1052 | IAB recommendations for the development of Internet network management standards |
| |
|
|
This RFC is intended to convey to the Internet community and other interested parties the recommendations of the Internet Activities Board (IAB) for the development of network management protocols for use in the TCP/IP environment. This memo does NOT, in and of itself, define or propose an Official Internet Protocol. It does reflect, however, the policy of the IAB with respect to further network management development in the short and long term. |
|
| |
| RFC 1053 | Telnet X.3 PAD option |
| |
| Authors: | S. Levy, T. Jacobson. |
| Date: | April 1988 |
| Formats: | txt html json |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1053 |
|
This RFC proposes a new option to Telnet for the Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 1054 | Host extensions for IP multicasting |
| |
|
|
This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. IP multicasting is the transmission of an IP datagram to a "host group", a set hosts identified by a single IP destination address. A multicast datagram is delivered to all members of its destination host group with the same "best-efforts" reliability as regular unicast IP datagrams. It is proposed as a standard for IP multicasting in the Internet. This specification is a major revision of RFC-988. |
|
| |
| RFC 1055 | Nonstandard for transmission of IP datagrams over serial lines: SLIP |
| |
|
|
The TCP/IP protocol family runs over a variety of network media: IEEE 802.3 (ethernet) and 802.5 (token ring) LAN's, X.25 lines, satellite links, and serial lines. There are standard encapsulations for IP packets defined for many of these networks, but there is no standard for serial lines. SLIP, Serial Line IP, is a currently a de facto standard, commonly used for point-to-point serial connections running TCP/IP. It is not an Internet standard. |
|
| |
| RFC 1056 | PCMAIL: A distributed mail system for personal computers |
| |
|
|
This memo is a discussion of the Pcmail workstation based distributed mail system. It is identical to the discussion in RFC-993, save that a new, much simpler mail transport protocol is described. The new transport protocol is the result of continued research into ease of protocol implementation and use issues. |
|
| |
| RFC 1057 | RPC: Remote Procedure Call Protocol specification: Version 2 |
| |
|
|
This RFC describes a standard that Sun Microsystems and others are using, and is one we wish to propose for the Internet's consideration. This memo is not an Internet standard at this time. |
|
| |
| RFC 1058 | Routing Information Protocol |
| |
|
|
This RFC describes an existing protocol for exchanging routing information among gateways and other hosts. It is intended to be used as a basis for developing gateway software for use in the Internet community. |
|
| |
| RFC 1059 | Network Time Protocol (version 1) specification and implementation |
| |
|
|
This memo 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 logical 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. The NTP architectures, algorithms and protocols which have evolved over several years of implementation and refinement are described in this document. The prototype system, which has been in regular operation in the Internet for the last two years, is described in an Appendix 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 the cases of failure or disruption of clocks, time servers or nets. This is a Draft Standard for an Elective protocol. |
|
| |
| RFC 1060 | Assigned numbers |
| |
|
|
This memo is a status report on the parameters (i.e., numbers and keywords) used in protocols in the Internet community. Distribution of this memo is unlimited. |
|
| |
| RFC 1062 | Internet numbers |
| |
|
|
This memo is an official status report on the network numbers and gateway autonomous system numbers used in the Internet community. |
|
| |
| RFC 1063 | IP MTU discovery options |
| |
| Authors: | J.C. Mogul, C.A. Kent, C. Partridge, K. McCloghrie. |
| Date: | July 1988 |
| Formats: | txt html json |
| Obsoleted by: | RFC 1191 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1063 |
|
A pair of IP options that can be used to learn the minimum MTU of a path through an internet is described, along with its possible uses. This is a proposal for an Experimental protocol. |
|
| |
| RFC 1064 | Interactive Mail Access Protocol: Version 2 |
| |
|
|
This memo suggests a method for workstations to dynamically access mail from a mailbox server ("respository"). This RFC specifies a standard for the SUMEX-AIM community and a proposed experimental protocol for the Internet community. Discussion and suggestions for improvement are requested. |
|
| |
| RFC 1065 | Structure and identification of management information for TCP/IP-based internets |
| |
| Authors: | K. McCloghrie, M.T. Rose. |
| Date: | August 1988 |
| Formats: | txt json html |
| Obsoleted by: | RFC 1155 |
| Status: | INTERNET STANDARD |
| DOI: | 10.17487/RFC 1065 |
|
This RFC provides the common definitions for the structure and identification of management information for TCP/IP-based internets. In particular, together with its companion memos, which describe the initial management information base along with the initial network management protocol, these documents provide a simple, working architecture and system for managing TCP/IP-based internets and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementation in the Internet which are network manageable are expected to adopt and implement this specification. |
|
| |
| RFC 1066 | Management Information Base for network management of TCP/IP-based internets |
| |
|
|
This RFC provides the initial version of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets in the short-term. In particular, together with its companion memos which describe the structure of management information along with the initial network management protocol, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets, and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementations in the Internet which are network manageable are expected to adopt and implement this specification. |
|
| |
| RFC 1067 | Simple Network Management Protocol |
| |
| Authors: | J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin. |
| Date: | August 1988 |
| Formats: | txt html json |
| Obsoleted by: | RFC 1098 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1067 |
|
This RFC defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. In particular, together with its companion memos which describe the structure of management information along with the initial management information base, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementations in the Internet which are network manageable are expected to adopt and implement this specification. |
|
| |
| RFC 1068 | Background File Transfer Program (BFTP) |
| |
| Authors: | A.L. DeSchon, R.T. Braden. |
| Date: | August 1988 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1068 |
|
This RFC describes an Internet background file transfer service that is built upon the third-party transfer model of FTP. No new protocols are involved. The purpose of this memo is to stimulate discussions on new Internet service modes. |
|
| |
| RFC 1069 | Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol |
| |
|
|
This RFC suggests an addressing scheme for use with the ISO Connectionless Network Protocol (CLNP) in the Internet. This is a solution to one of the problems inherent in the use of "ISO-grams" in the Internet. This memo is a revision of RFC 986. This RFC suggests a proposed protocol for the Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 1070 | Use of the Internet as a subnetwork for experimentation with the OSI network layer |
| |
| Authors: | R.A. Hagens, N.E. Hall, M.T. Rose. |
| Date: | February 1989 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1070 |
|
This RFC proposes a scenario for experimentation with the International Organization for Standardization (ISO) Open Systems Interconnection (OSI) network layer protocols over the Internet and requests discussion and suggestions for improvements to this scenario. This RFC also proposes the creation of an experimental OSI internet. To participate in the experimental OSI internet, a system must abide by the agreements set forth in this RFC. |
|
| |
| RFC 1071 | Computing the Internet checksum |
| |
| Authors: | R.T. Braden, D.A. Borman, C. Partridge. |
| Date: | September 1988 |
| Formats: | txt json html |
| Updated by: | RFC 1141 |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1071 |
|
This RFC summarizes techniques and algorithms for efficiently computing the Internet checksum. It is not a standard, but a set of useful implementation techniques. |
|
| |
| RFC 1072 | TCP extensions for long-delay paths |
| |
|
|
This RFC proposes a set of extensions to the TCP protocol to provide efficient operation over a path with a high bandwidth*delay product. These extensions are not proposed as an Internet standard at this time. Instead, they are intended as a basis for further experimentation and research on transport protocol performance. |
|
| |
| RFC 1073 | Telnet window size option |
| |
| Authors: | D. Waitzman. |
| Date: | October 1988 |
| Formats: | txt html json |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 1073 |
|
This RFC describes a proposed Telnet option to allow a client to convey window size to a Telnet server. |
|
| |
| RFC 1074 | NSFNET backbone SPF based Interior Gateway Protocol |
| |
| Authors: | J. Rekhter. |
| Date: | October 1988 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1074 |
|
This RFC is an implementation description of the standard ANSI IS-IS and ISO ES-IS routing protocols within the NSFNET backbone network. |
|
| |
| RFC 1075 | Distance Vector Multicast Routing Protocol |
| |
| Authors: | D. Waitzman, C. Partridge, S.E. Deering. |
| Date: | November 1988 |
| Formats: | txt json html |
| Status: | EXPERIMENTAL |
| DOI: | 10.17487/RFC 1075 |
|
This RFC describes a distance-vector-style routing protocol for routing multicast datagrams through an internet. It is derived from the Routing Information Protocol (RIP), and implements multicasting as described in RFC-1054. This is an experimental protocol, and its implementation is not recommended at this time. |
|
| |
| RFC 1076 | HEMS monitoring and control language |
| |
|
|
This RFC specifies a query language for monitoring and control of network entities. This RFC supercedes RFC 1023, extending the query language and providing more discussion of the underlying issues. This language is a component of the High-Level Entity Monitoring System (HEMS) described in RFC 1021 and RFC 1022. Readers may wish to consult these RFCs when reading this memo. RFC 1024 contains detailed assignments of numbers and structures used in this system. Portions of RFC 1024 that define query language structures are superceded by definitions in this memo. This memo assumes a knowledge of the ISO data encoding standard, ASN.1. |
|
| |
| RFC 1077 | Critical issues in high bandwidth networking |
| |
| Authors: | B.M. Leiner. |
| Date: | November 1988 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1077 |
|
This memo presents the results of a working group on High Bandwidth Networking. This RFC is for your information and you are encouraged to comment on the issues presented. |
|
| |
| RFC 1078 | TCP port service Multiplexer (TCPMUX) |
| |
|
|
This RFC proposes an Internet standard which can be used by future TCP services instead of using 'well-known ports'. |
|
| |
| RFC 1079 | Telnet terminal speed option |
| |
| Authors: | C.L. Hedrick. |
| Date: | December 1988 |
| Formats: | txt json html |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 1079 |
|
This RFC specifies a standard for the Internet community. Hosts on the Internet that exchange terminal speed information within the Telnet protocol are expected to adopt and implement this standard. |
|
| |
| RFC 1080 | Telnet remote flow control option |
| |
|
|
This RFC specifies a standard for the Internet community. Hosts on the Internet that do remote flow control within the Telnet protocol are expected to adopt and implement this standard. |
|
| |
| RFC 1081 | Post Office Protocol: Version 3 |
| |
|
|
This memo suggests a simple method for workstations to dynamically access mail from a mailbox server. This RFC specifies a proposed protocol for the Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 1082 | Post Office Protocol: Version 3: Extended service offerings |
| |
| Authors: | M.T. Rose. |
| Date: | November 1988 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1082 |
|
This memo suggests a simple method for workstations to dynamically access mail from a discussion group server, as an extension to an earlier memo which dealt with dynamically accessing mail from a mailbox server using the Post Office Protocol - Version 3 (POP3). This RFC specifies a proposed protocol for the Internet community, and requests discussion and suggestions for improvements. All of the extensions described in this memo to the POP3 are OPTIONAL. |
|
| |
| RFC 1083 | IAB official protocol standards |
| |
| Authors: | Defense Advanced Research Projects Agency, Internet Activities Board. |
| Date: | December 1988 |
| Formats: | txt html json |
| Obsoleted by: | RFC 1100 |
| Status: | HISTORIC |
| DOI: | 10.17487/RFC 1083 |
|
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. |
|
| |
| RFC 1084 | BOOTP vendor information extensions |
| |
|
|
This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville. This memo will be updated as additional tags are are defined. This edition introduces Tag 13 for Boot File Size. Comments and suggestions for improvements are sought. |
|
| |
| RFC 1085 | ISO presentation services on top of TCP/IP based internets |
| |
| Authors: | M.T. Rose. |
| Date: | December 1988 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1085 |
|
RFC 1006 describes a mechanism for providing the ISO transport service on top of TCP/IP. Once this method is applied, one may implement "real" ISO applications on top of TCP/IP-based internets, by simply implementing OSI session, presentation, and application services on top of the transport service access point which is provided on top of the TCP. Although straight-forward, there are some environments in which the richness provided by the OSI application layer is desired, but it is nonetheless impractical to implement the underlying OSI infrastructure (i.e., the presentation, session, and transport services on top of the TCP). This memo describes an approach for providing "stream-lined" support of OSI application services on top of TCP/IP-based internets for such constrained environments. This memo proposes a standard for the Internet community. |
|
| |
| RFC 1086 | ISO-TP0 bridge between TCP and X.25 |
| |
| Authors: | J.P. Onions, M.T. Rose. |
| Date: | December 1988 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1086 |
|
This memo proposes a standard for the Internet community. Hosts on the Internet that choose to implement ISO TP0 transport connectivity between TCP and X.25 based hosts are expected to experiment with this proposal. TCP port 146 is reserved for this proposal. |
|
| |
| RFC 1087 | Ethics and the Internet |
| |
| Authors: | Defense Advanced Research Projects Agency, Internet Activities Board. |
| Date: | January 1989 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1087 |
|
This memo is a statement of policy by the Internet Activities Board (IAB) concerning the proper use of the resources of the Internet. |
|
| |
| RFC 1088 | Standard for the transmission of IP datagrams over NetBIOS networks |
| |
|
|
This document specifies a standard method of encapsulating the Internet Protocol (IP) datagrams on NetBIOS networks. |
|
| |
| RFC 1089 | SNMP over Ethernet |
| |
| Authors: | M. Schoffstall, C. Davin, M. Fedor, J. Case. |
| Date: | February 1989 |
| Formats: | txt json html |
| Obsoleted by: | RFC 4789 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1089 |
|
This memo describes an experimental method by which the Simple Network Management Protocol (SNMP) can be used over Ethernet MAC layer framing instead of the Internet UDP/IP protocol stack. This specification is useful for LAN based network elements that support no higher layer protocols beyond the MAC sub-layer. |
|
| |
| RFC 1090 | SMTP on X.25 |
| |
| Authors: | R. Ullmann. |
| Date: | February 1989 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1090 |
|
This memo proposes a standard for SMTP on the virtual circuit facility provided by the X.25 standard of the CCITT. |
|
| |
| RFC 1091 | Telnet terminal-type option |
| |
|
|
This RFC specifies a standard for the Internet community. Hosts on the Internet that exchange terminal type information within the Telnet protocol are expected to adopt and implement this standard. This standard supersedes RFC 930. A change is made to permit cycling through a list of possible terminal types and selecting the most appropriate |
|
| |
| RFC 1092 | EGP and policy based routing in the new NSFNET backbone |
| |
| Authors: | J. Rekhter. |
| Date: | February 1989 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1092 |
|
This memo discusses implementation decisions for routing issues in the NSFNET, especially in the NSFNET Backbone. Of special concern is the restriction of routing information to advertize the best route as established by a policy decision. |
|
| |
| RFC 1093 | NSFNET routing architecture |
| |
| Authors: | H.W. Braun. |
| Date: | February 1989 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1093 |
|
This document describes the routing architecture for the NSFNET centered around the new NSFNET Backbone, with specific emphasis on the interface between the backbone and its attached networks. |
|
| |
| RFC 1094 | NFS: Network File System Protocol specification |
| |
|
|
This RFC describes a protocol that Sun Microsystems, Inc., and others are using. A new version of the protocol is under development, but others may benefit from the descriptions of the current protocol, and discussion of some of the design issues. |
|
| |
| RFC 1095 | Common Management Information Services and Protocol over TCP/IP (CMOT) |
| |
|
|
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 a TCP/IP environment. This architecture provides a means by which control and monitoring information can be exchanged between a manager and a remote network element. In particular, this memo defines the means for implementing the Draft International Standard (DIS) version of CMIS/CMIP on top of Internet transport protocols for the purpose of carrying management information defined in the Internet-standard management information base. DIS CMIS/CMIP is suitable for deployment in TCP/IP networks while CMIS/CMIP moves toward becoming an International Standard. Together with the relevant ISO standards and the companion RFCs that describe the initial structure of management information and management information base, these documents provide the basis for a comprehensive architecture and system for managing TCP/IP- based internets, and in particular the Internet. |
|
| |
| RFC 1096 | Telnet X display location option |
| |
| Authors: | G.A. Marcy. |
| Date: | March 1989 |
| Formats: | txt html json |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 1096 |
|
This RFC specifies a standard for the Internet community. Hosts on the Internet that transmit the X display location within the Telnet protocol are expected to adopt and implement this standard. |
|
| |
| RFC 1097 | Telnet subliminal-message option |
| |
| Authors: | B. Miller. |
| Date: | 1 April 1989 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1097 |
|
This RFC specifies a standard for the Internet community. Hosts on the Internet that display subliminal messages within the Telnet protocol are expected to adopt and implement this standard. |
|
| |
| RFC 1098 | Simple Network Management Protocol (SNMP) |
| |
|
|
This RFC is a re-release of RFC 1067, with a changed "Status of this Memo" section. This memo defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. In particular, together with its companion memos which describe the structure of management information along with the initial management information base, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular the Internet. |
|
| |
| RFC 1099 | Request for Comments Summary: RFC Numbers 1000-1099 |
| |
| Authors: | J. Reynolds. |
| Date: | December 1991 |
| Formats: | txt json html |
| Status: | INFORMATIONAL |
| DOI: | 10.17487/RFC 1099 |
|
|
|
