| |
| RFC 407 | Remote Job Entry Protocol |
| |
| Authors: | R.D. Bressler, R. Guida, A.M. McKenzie. |
| Date: | October 1972 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0360 |
| Status: | HISTORIC |
|
|
|
| |
| RFC 569 | NETED: A Common Editor for the ARPA Network |
| |
| Authors: | M.A. Padlipsky. |
| Date: | October 1973 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
|
|
| |
| RFC 652 | Telnet output carriage-return disposition option |
| |
| Authors: | D. Crocker. |
| Date: | October 1974 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
|
|
| |
| RFC 653 | Telnet output horizontal tabstops option |
| |
| Authors: | D. Crocker. |
| Date: | October 1974 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
|
|
| |
| RFC 654 | Telnet output horizontal tab disposition option |
| |
| Authors: | D. Crocker. |
| Date: | October 1974 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
|
|
| |
| RFC 655 | Telnet output formfeed disposition option |
| |
| Authors: | D. Crocker. |
| Date: | October 1974 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
|
|
| |
| RFC 656 | Telnet output vertical tabstops option |
| |
| Authors: | D. Crocker. |
| Date: | October 1974 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
|
|
| |
| RFC 657 | Telnet output vertical tab disposition option |
| |
| Authors: | D. Crocker. |
| Date: | October 1974 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
|
|
| |
| RFC 658 | Telnet output linefeed disposition |
| |
| Authors: | D. Crocker. |
| Date: | October 1974 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
|
|
| |
| RFC 717 | Assigned Network Numbers |
| |
| Authors: | J. Postel. |
| Date: | July 1976 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
|
|
| |
| RFC 734 | SUPDUP Protocol |
| |
| Authors: | M.R. Crispin. |
| Date: | October 1977 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
|
|
| |
| RFC 739 | Assigned numbers |
| |
|
| |
| RFC 740 | NETRJS Protocol |
| |
| Authors: | R.T. Braden. |
| Date: | November 1977 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0599 |
| Status: | HISTORIC |
|
|
|
| |
| RFC 750 | Assigned numbers |
| |
| Authors: | J. Postel. |
| Date: | September 1978 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0739 |
| Obsoleted by: | RFC 0755 |
| Status: | HISTORIC |
|
|
|
| |
| RFC 755 | Assigned numbers |
| |
|
| |
| RFC 758 | Assigned numbers |
| |
|
| |
| RFC 759 | Internet Message Protocol |
| |
| Authors: | J. Postel. |
| Date: | August 1980 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
|
|
| |
| RFC 762 | Assigned numbers |
| |
|
| |
| RFC 770 | Assigned numbers |
| |
| Authors: | J. Postel. |
| Date: | September 1980 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0762 |
| Obsoleted by: | RFC 0776 |
| Status: | HISTORIC |
|
|
|
| |
| RFC 776 | Assigned numbers |
| |
|
| |
| RFC 778 | DCNET Internet Clock Service |
| |
| Authors: | D.L. Mills. |
| Date: | April 1981 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
|
|
| |
| RFC 790 | Assigned numbers |
| |
| Authors: | J. Postel. |
| Date: | September 1981 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0776 |
| Obsoleted by: | RFC 0820 |
| Status: | HISTORIC |
|
|
|
| |
| RFC 818 | Remote User Telnet service |
| |
| Authors: | J. Postel. |
| Date: | November 1982 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
This RFC is the specification of an application protocol. Any host that implements this application level service must follow this protocol. |
|
| |
| RFC 820 | Assigned numbers |
| |
|
|
This RFC is an old version, see RFC 870. |
|
| |
| RFC 823 | DARPA Internet gateway |
| |
| Authors: | R.M. Hinden, A. Sheltzer. |
| Date: | September 1982 |
| Formats: | txt pdf |
| Updates: | IEN 109, IEN 30 |
| Status: | HISTORIC |
|
This RFC is a status report on the Internet Gateway developed by BBN. It describes the Internet Gateway as of September 1982. This memo presents detailed descriptions of message formats and gateway procedures, however, this is not an implementation specification, and such details are subject to change. |
|
| |
| RFC 840 | Official protocols |
| |
| Authors: | J. Postel. |
| Date: | April 1983 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0880 |
| Status: | HISTORIC |
|
This RFC has been revised, see RFC 880. |
|
| |
| RFC 869 | Host Monitoring Protocol |
| |
| Authors: | R. Hinden. |
| Date: | December 1983 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
This RFC specifies the Host Monitoring Protocol used to collect information from various types of hosts in the Internet. Designers of Internet communications software are encouraged to consider this protocol as a means of monitoring the behavior of their creations. |
|
| |
| RFC 870 | Assigned numbers |
| |
| Authors: | J.K. Reynolds, J. Postel. |
| Date: | October 1983 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0820 |
| Obsoleted by: | RFC 0900 |
| Status: | HISTORIC |
|
This RFC documents the list of numbers assigned for networks, protocols, etc. Obsoletes RFCs 820, 790, 776, 770, 762, 758, 755, 750, 739, 604. |
|
| |
| RFC 880 | Official protocols |
| |
| Authors: | J.K. Reynolds, J. Postel. |
| Date: | October 1983 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0840 |
| Obsoleted by: | RFC 0901 |
| Status: | HISTORIC |
|
This RFC identifies the documents specifying the official protocols used in the ARPA Internet. Annotations identify any revisions or changes planned. Obsoletes RFC 840. |
|
| |
| RFC 900 | Assigned Numbers |
| |
| Authors: | J.K. Reynolds, J. Postel. |
| Date: | June 1984 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0870 |
| Obsoleted by: | RFC 0923 |
| Status: | HISTORIC |
|
This RFC specifies parameter values use in the Internet family of protocols, such as network numbers, well known ports, protocol types, and version numbers. This memo is an official status report on the protocol parameters used in the Internet protocol system. See RFC-990 and 997. |
|
| |
| RFC 904 | Exterior Gateway Protocol formal specification |
| |
|
|
RFC-904 is the specification of the Exterior Gateway Protocol (EGP). This memo updates portions of RFC-888 and RFC-827. This RFC specifies an official protocol of the DARPA community for use between gateways of different autonomous systems in the ARPA-Internet. |
|
| |
| RFC 913 | Simple File Transfer Protocol |
| |
| Authors: | M. Lottor. |
| Date: | September 1984 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
This memo describes a proposed Simple File Transfer Protocol (SFTP). It fills the need of people wanting a protocol that is more useful than TFTP but easier to implement (and less powerful) than FTP. SFTP supports user access control, file transfers, directory listing, directory changing, file renaming and deleting. Discussion of this proposal is encouraged, and suggestions for improvements may be sent to the author. |
|
| |
| RFC 914 | Thinwire protocol for connecting personal computers to the Internet |
| |
| Authors: | D.J. Farber, G. Delp, T.M. Conte. |
| Date: | September 1984 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
This RFC focuses discussion on the particular problems in the ARPA-Internet of low speed network interconnection with personal computers, and possible methods of solution. None of the proposed solutions in this document are intended as standards for the ARPA-Internet. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to the problems, leading eventually to the adoption of standards. |
|
| |
| RFC 916 | Reliable Asynchronous Transfer Protocol (RATP) |
| |
| Authors: | G.G. Finn. |
| Date: | October 1984 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. This paper proposes and specifies a protocol which allows two programs to reliably communicate over a communication link. It ensures that the data entering one end of the link if received arrives at the other end intact and unaltered. The protocol, named RATP, is designed to operate over a full duplex point-to-point connection. It contains some features which tailor it to the RS-232 links now in common use. |
|
| |
| RFC 923 | Assigned numbers |
| |
| Authors: | J.K. Reynolds, J. Postel. |
| Date: | October 1984 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0900 |
| Obsoleted by: | RFC 0943 |
| Status: | HISTORIC |
|
This RFC documents the currently assigned values from several series of numbers used in network protocol implementations. This edition of Assigned Numbers obsoletes RFC-900 and earlier editions. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990, and 997. |
|
| |
| RFC 929 | Proposed Host-Front End Protocol |
| |
| Authors: | J. Lilienkamp, R. Mandell, M.A. Padlipsky. |
| Date: | December 1984 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
The Host-Front End Protocol introduced in RFC-928 is described in detail in this memo. The first order of business is to declare that THIS IS A PROPOSAL, NOT A FINAL STANDARD, and the second order of business is to request that any readers of these documents who are able to do test implementations (a) do so and (b) coordinate their efforts with the author. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 937 | Post Office Protocol: Version 2 |
| |
| Authors: | M. Butler, J. Postel, D. Chase, J. Goldberger, J.K. Reynolds. |
| Date: | February 1985 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0918 |
| Status: | HISTORIC |
|
This RFC suggests a simple method for workstations to dynamically access mail from a mailbox server. This RFC specifies a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvement. This memo is a revision of RFC-918. |
|
| |
| RFC 943 | Assigned numbers |
| |
| Authors: | J.K. Reynolds, J. Postel. |
| Date: | April 1 1985 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0923 |
| Obsoleted by: | RFC 0960 |
| Status: | HISTORIC |
|
This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This RFC will be updated periodically, and in any case current information can be obtained from Joyce Reynolds. The assignment of numbers is also handled by Joyce. If you are developing a protocol or application that will require the use of a link, socket, port, protocol, network number, etc., please contact Joyce to receive a number assignment. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990 and 997. |
|
| |
| RFC 953 | Hostname Server |
| |
| Authors: | K. Harrenstien, M.K. Stahl, E.J. Feinler. |
| Date: | October 1985 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0811 |
| Status: | HISTORIC |
|
This RFC is the official specification of the Hostname Server Protocol. This edition of the specification includes minor revisions to RFC-811 which brings it up to date. |
|
| |
| RFC 960 | Assigned numbers |
| |
| Authors: | J.K. Reynolds, J. Postel. |
| Date: | December 1985 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0943 |
| Obsoleted by: | RFC 0990 |
| Status: | HISTORIC |
|
This memo documents the currently assigned values from several series of numbers used in network protocol implementations. This edition of Assigned Numbers updates and obsoletes RFC-943. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990 and 997. |
|
| |
| RFC 974 | Mail routing and the domain system |
| |
|
|
This RFC presents a description of how mail systems on the Internet are expected to route messages based on information from the domain system. This involves a discussion of how mailers interpret MX RRs, which are used for message routing. |
|
| |
| RFC 990 | Assigned numbers |
| |
|
|
This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-997. Obsoletes RFC-960, 943, 923 and 900. |
|
| |
| RFC 996 | Statistics server |
| |
| Authors: | D.L. Mills. |
| Date: | February 1987 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
This RFC specifies a standard for the ARPA Internet community. Hosts and gateways on the DARPA Internet that choose to implement a remote statistics monitoring facility may use this protocol to send statistics data upon request to a monitoring center or debugging host. |
|
| |
| RFC 1009 | Requirements for Internet gateways |
| |
| Authors: | R.T. Braden, J. Postel. |
| Date: | June 1987 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0985 |
| Obsoleted by: | RFC 1812 |
| Status: | HISTORIC |
|
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 |
| |
| Authors: | J.K. Reynolds, J. Postel. |
| Date: | May 1987 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0990 |
| Obsoleted by: | RFC 1060 |
| Status: | HISTORIC |
|
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 1021 | High-level Entity Management System (HEMS) |
| |
| Authors: | C. Partridge, G. Trewitt. |
| Date: | October 1987 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
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 1028 | Simple Gateway Monitoring Protocol |
| |
| Authors: | J. Davin, J.D. Case, M. Fedor, M.L. Schoffstall. |
| Date: | November 1987 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
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 1037 | NFILE - a file access protocol |
| |
| Authors: | B. Greenberg, S. Keene. |
| Date: | December 1987 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
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 1049 | Content-type header field for Internet messages |
| |
| Authors: | M.A. Sirbu. |
| Date: | March 1988 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
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 |
| |
| Authors: | Sun Microsystems. |
| Date: | April 1 1988 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1057 |
| Status: | HISTORIC |
|
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 |
| |
| Authors: | P.A. Prindeville. |
| Date: | March 1988 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1201 |
| Status: | HISTORIC |
|
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 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 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 1083 | IAB official protocol standards |
| |
| Authors: | Defense Advanced Research Projects Agency, Internet Activities Board. |
| Date: | December 1988 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1100 |
| Status: | HISTORIC |
|
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 1100 | IAB official protocol standards |
| |
| Authors: | Defense Advanced Research Projects Agency, Internet Activities Board. |
| Date: | April 1 1989 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1083 |
| Obsoleted by: | RFC 1130 |
| Status: | HISTORIC |
|
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures is presented first, followed by discussions of the standardization process and the RFC document series, then the explanation of the terms is presented, the lists of protocols in each stage of standardization follows, and finally pointers to references and contacts for further information. This memo is issued quarterly, please be sure the copy you are reading is dated within the last three months. Current copies may be obtained from the Network Information Center or from the Internet Assigned Numbers Authority (see the contact information at the end of this memo). Do not use this memo after 31-July-89. |
|
| |
| RFC 1108 | U.S |
| |
| Authors: | Department of Defense Security Options for the Internet Protocol. S. Kent. |
| Date: | November 1991 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1038 |
| Status: | HISTORIC |
|
This RFC specifies the U.S. Department of Defense Basic SecurityOption and the top-level description of the Extended Security Option for use with the Internet Protocol. This RFC obsoletes RFC 1038"Revised IP Security Option", dated January 1988. |
|
| |
| RFC 1113 | Privacy enhancement for Internet electronic mail: Part I - message encipherment and authentication procedures |
| |
|
|
This RFC specifies features for private electronic mail based on encryption technology. [STANDARDS-TRACK] |
|
| |
| RFC 1114 | Privacy enhancement for Internet electronic mail: Part II - certificate-based key management |
| |
| Authors: | S.T. Kent, J. Linn. |
| Date: | August 1989 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1422 |
| Status: | HISTORIC |
|
This RFC specifies the key management aspects of Privacy Enhanced Mail. [STANDARDS-TRACK] |
|
| |
| RFC 1115 | Privacy enhancement for Internet electronic mail: Part III - algorithms, modes, and identifiers |
| |
| Authors: | J. Linn. |
| Date: | August 1989 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1423 |
| Status: | HISTORIC |
|
This RFC provides definitions, references, and citations for algorithms, usage modes, and associated identifiers used in RFC-1113 and RFC-1114 in support of privacy-enhanced electronic mail. [STANDARDS-TRACK] |
|
| |
| RFC 1130 | IAB official protocol standards |
| |
| Authors: | Defense Advanced Research Projects Agency, Internet Activities Board. |
| Date: | October 1989 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1100 |
| Obsoleted by: | RFC 1140 |
| Status: | HISTORIC |
|
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). |
|
| |
| RFC 1137 | Mapping between full RFC 822 and RFC 822 with restricted encoding |
| |
| Authors: | S. Kille. |
| Date: | December 1989 |
| Formats: | txt pdf |
| Updates: | RFC 0976 |
| Status: | HISTORIC |
|
This RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. |
|
| |
| RFC 1140 | IAB official protocol standards |
| |
| Authors: | Defense Advanced Research Projects Agency, Internet Activities Board. |
| Date: | May 1990 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1130 |
| Obsoleted by: | RFC 1200 |
| Status: | HISTORIC |
|
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo is issued quarterly, please be sure the copy you are reading is dated within the last three months. Current copies may be obtained from the Network Information Center or from the Internet Assigned Numbers Authority. Do not use this edition after 31-Aug-90. |
|
| |
| RFC 1156 | Management Information Base for network management of TCP/IP-based internets |
| |
| Authors: | K. McCloghrie, M.T. Rose. |
| Date: | May 1990 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1066 |
| Status: | HISTORIC |
|
This RFC is a re-release of RFC 1066, with a changed "Status of this Memo", "IAB Policy Statement", and "Introduction" sections plus a few minor typographical corrections. The technical content of the document is unchanged from RFC 1066. [STANDARDS-TRACK] |
|
| |
| RFC 1157 | Simple Network Management Protocol (SNMP) |
| |
| Authors: | J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin. |
| Date: | May 1990 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1098 |
| Status: | HISTORIC |
|
This RFC is a re-release of RFC 1098, with a changed "Status of this Memo" section plus a few minor typographical corrections. This memo defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. [STANDARDS-TRACK] |
|
| |
| RFC 1163 | Border Gateway Protocol (BGP) |
| |
| Authors: | K. Lougheed, Y. Rekhter. |
| Date: | June 1990 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1105 |
| Obsoleted by: | RFC 1267 |
| Status: | HISTORIC |
|
This RFC, together with its companion RFC-1164, "Application of the Border Gateway Protocol in the Internet", specify an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK] |
|
| |
| RFC 1164 | Application of the Border Gateway Protocol in the Internet |
| |
| Authors: | J.C. Honig, D. Katz, M. Mathis, Y. Rekhter, J.Y. Yu. |
| Date: | June 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1268 |
| Status: | HISTORIC |
|
This RFC, together with its companion RFC-1163, "A Border Gateway Protocol (BGP)", specify an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK] |
|
| |
| RFC 1189 | Common Management Information Services and Protocols for the Internet (CMOT and CMIP) |
| |
| Authors: | U.S. Warrier, L. Besaw, L. LaBarre, B.D. Handspicker. |
| Date: | October 1990 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1095 |
| Status: | HISTORIC |
|
This memo defines a network management architecture that uses the International Organization for Standardization's (ISO) Common Management Information Services/Common Management Information Protocol (CMIS/CMIP) in the Internet. [STANDARDS-TRACK] |
|
| |
| RFC 1200 | IAB official protocol standards |
| |
| Authors: | Defense Advanced Research Projects Agency, Internet Activities Board. |
| Date: | April 1 1991 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1140 |
| Obsoleted by: | RFC 1250 |
| Status: | HISTORIC |
|
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 1203 | Interactive Mail Access Protocol: Version 3 |
| |
| Authors: | J. Rice. |
| Date: | February 1991 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1064 |
| Status: | HISTORIC |
|
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 1214 | OSI internet management: Management Information Base |
| |
| Authors: | L. LaBarre. |
| Date: | April 1 1991 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
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 1227 | SNMP MUX protocol and MIB |
| |
| Authors: | M.T. Rose. |
| Date: | May 1991 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
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 1230 | IEEE 802.4 Token Bus MIB |
| |
| Authors: | K. McCloghrie, R. Fox. |
| Date: | May 1991 |
| Formats: | txt pdf |
| Updated by: | RFC 1239 |
| Status: | HISTORIC |
|
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 1234 | Tunneling IPX traffic through IP networks |
| |
| Authors: | D. Provan. |
| Date: | June 1991 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
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 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 pdf |
| Status: | HISTORIC |
|
This document describes a protocol for running OSI Connectionless service on UDP. [STANDARDS-TRACK] |
|
| |
| 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 1264 | Internet Engineering Task Force Internet Routing Protocol Standardization Criteria |
| |
| Authors: | R.M. Hinden. |
| Date: | October 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 4794 |
| Status: | HISTORIC |
|
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 1267 | Border Gateway Protocol 3 (BGP-3) |
| |
| Authors: | K. Lougheed, Y. Rekhter. |
| Date: | October 1991 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1163 |
| Status: | HISTORIC |
|
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 |
| |
| Authors: | Y. Rekhter, P. Gross. |
| Date: | October 1991 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1164 |
| Obsoleted by: | RFC 1655 |
| Status: | HISTORIC |
|
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 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 pdf |
| Status: | HISTORIC |
|
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 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 1285 | FDDI Management Information Base |
| |
| Authors: | J. Case. |
| Date: | January 1992 |
| Formats: | txt pdf |
| Updated by: | RFC 1512 |
| Status: | HISTORIC |
|
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 1314 | A File Format for the Exchange of Images in the Internet |
| |
| Authors: | A. Katz, D. Cohen. |
| Date: | April 1992 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
This document defines a standard file format for the exchange of fax-like black and white images within the Internet. It is a product of the Network Fax Working Group of the Internet Engineering TaskForce (IETF).
The standard is:
** The file format should be TIFF-B with multi-page files supported. Images should be encoded as one TIFF strip per page.
** Images should be compressed using MMR when possible. Images may also be MH or MR compressed or uncompressed. If MH or MR compression is used, scan lines should be "byte-aligned".
** For maximum interoperability, image resolutions should either be 600, 400, or 300 dpi; or else be one of the standard Group 3 fax resolutions (98 or 196 dpi vertically and 204 dpi horizontally).
Note that this specification is self contained and an implementation should be possible without recourse to the TIFF references, and that only the specific TIFF documents cited are relevant to this specification. Updates to the TIFF documents do not change this specification.
Experimentation with this file format specified here is encouraged. |
|
| |
| RFC 1328 | X.400 1988 to 1984 downgrading |
| |
| Authors: | S. Hardcastle-Kille. |
| Date: | May 1992 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
This document considers issues of downgrading from X.400(1988) toX.400(1984) [MHS88a, MHS84]. Annexe B of X.419 specifies some downgrading rules [MHS88b], but these are not sufficient for provision of service in an environment containing both 1984 and 1988 components. This document defines a number of extensions to this annexe.
This specification is not tutorial. COSINE Study 8.2 by J.A.I.Craigie gives a useful overview [Cra88]. |
|
| |
| RFC 1340 | Assigned Numbers |
| |
| Authors: | J. Reynolds, J. Postel. |
| Date: | July 1992 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1060 |
| Obsoleted by: | RFC 1700 |
| Status: | HISTORIC |
|
This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This memo is a status report on the parameters (i.e., numbers and keywords) used in protocols in the Internet community. |
|
| |
| RFC 1351 | SNMP Administrative Model |
| |
| Authors: | J. Davin, J. Galvin, K. McCloghrie. |
| Date: | July 1992 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
This memo presents an elaboration of the SNMP administrative model set forth in [1]. This model provides a unified conceptual basis for administering SNMP protocol entities to support: authenticaiton and integrity, privacy, access control, and cooperation of protocol entities. [STANDARDS-TRACK] |
|
| |
| RFC 1352 | SNMP Security Protocols |
| |
| Authors: | J. Galvin, K. McCloghrie, J. Davin. |
| Date: | July 1992 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
The Simple Network Management Protocol (SNMP) specification [1] allows for the protection of network management operations by a variety of security protocols. The SNMP administrative model described in [2] provides a framework for securing SNMP network management. In the context of that framework, this memo defines protocols to support the following three security services: data integrity, data origin authentication and data confidentiality. [STANDARDS-TRACK] |
|
| |
| RFC 1353 | Definitions of Managed Objects for Administration of SNMP Parties |
| |
| Authors: | K. McCloghrie, J. Davin, J. Galvin. |
| Date: | July 1992 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
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 describes a representation of the SNMP parties defined in [8] as objects defined according to the Internet StandardSMI [1]. These definitions are consistent with the SNMP Security protocols set forth in [9]. |
|
| |
| RFC 1360 | IAB Official Protocol Standards |
| |
| Authors: | J. Postel. |
| Date: | September 1992 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1280 |
| Obsoleted by: | RFC 1410 |
| Status: | HISTORIC |
|
|
|
| |
| RFC 1370 | Applicability Statement for OSPF |
| |
| Authors: | Internet Architecture Board, L. Chapin. |
| Date: | October 1992 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
This Applicability Statement places a requirement on vendors claiming conformance to this standard, in order to assure that users will have the option of deploying OSPF when they need a multivendor, interoperable IGP in their environment. [STANDARDS-TRACK] |
|
| |
| RFC 1378 | The PPP AppleTalk Control Protocol (ATCP) |
| |
| Authors: | B. Parker. |
| Date: | November 1992 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols.
This document defines the NCP for establishing and configuring theAppleTalk Protocol [3] over PPP.
This memo is a joint effort of the AppleTalk-IP Working Group and thePoint-to-Point Protocol Working Group of the Internet EngineeringTask Force (IETF). Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu mailing list. |
|
| |
| RFC 1397 | Default Route Advertisement In BGP2 and BGP3 Version of The Border Gateway Protocol |
| |
| Authors: | D. Haskin. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Status: | HISTORIC |
|
This document specifies the recommendation of the BGP Working Group on default route advertisement support in BGP2 [1] and BGP3 [2] versions of the Border Gateway Protocol.
This recommendation only applies to BGP2 and BGP3 versions of theBorder Gateway Protocol since starting with the BGP4 [3] version a default route advertisement capability is built in the protocol. |
|
| |
| RFC 1403 | BGP OSPF Interaction |
| |
| Authors: | K. Varadhan. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1364 |
| Status: | HISTORIC |
|
This memo defines the various criteria to be used when designing anAutonomous System Border Routers (ASBR) that will run BGP with otherASBRs external to the AS and OSPF as its IGP. This is a republication of RFC 1364 to correct some editorial problems. |
|
| |
| RFC 1408 | Telnet Environment Option |
| |
| Authors: | D. Borman, Ed.. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Updated by: | RFC 1571 |
| Status: | HISTORIC |
|
This document specifies a mechanism for passing environment information between a telnet client and server. Use of this mechanism enables a telnet user to propagate configuration information to a remote host when connecting. |
|
| |
| RFC 1410 | IAB Official Protocol Standards |
| |
| Authors: | J. Postel, Ed.. |
| Date: | March 1993 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1360 |
| Obsoleted by: | RFC 1500 |
| Status: | HISTORIC |
| |
