| |
| RFC 3 | Documentation conventions |
| |
| Authors: | S.D. Crocker. |
| Date: | April 1969 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0010 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 10 | Documentation conventions |
| |
|
| |
| RFC 11 | Implementation of the Host - Host Software Procedures in GORDO |
| |
| Authors: | G. Deloche. |
| Date: | August 1969 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0033 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 16 | M.I.T |
| |
|
| |
| RFC 61 | Note on Interprocess Communication in a Resource Sharing Computer Network |
| |
| Authors: | D.C. Walden. |
| Date: | July 1970 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0062 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 66 | NIC - third level ideas and other noise |
| |
|
| |
| RFC 80 | Protocols and Data Formats |
| |
|
| |
| RFC 88 | NETRJS: A third level protocol for Remote Job Entry |
| |
| Authors: | R.T. Braden, S.M. Wolfe. |
| Date: | January 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0189 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 95 | Distribution of NWG/RFC's through the NIC |
| |
| Authors: | S.D. Crocker. |
| Date: | February 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0155 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 123 | Proffered Official ICP |
| |
|
| |
| RFC 127 | Comments on RFC 123 |
| |
|
| |
| RFC 132 | Typographical Error in RFC 107 |
| |
|
| |
| RFC 143 | Regarding proffered official ICP |
| |
|
| |
| RFC 145 | Initial Connection Protocol Control Commands |
| |
|
| |
| RFC 155 | ARPA Network mailing lists |
| |
|
| |
| RFC 158 | Telnet Protocol: A Proposed Document |
| |
|
| |
| RFC 160 | RFC brief list |
| |
| Authors: | Network Information Center. Stanford Research Institute. |
| Date: | May 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0200, RFC 0999 |
| Updates: | NIC 6716 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 168 | ARPA Network mailing lists |
| |
|
| |
| RFC 170 | RFC List by Number |
| |
| Authors: | Network Information Center. Stanford Research Institute. |
| Date: | June 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0200 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 171 | The Data Transfer Protocol |
| |
| Authors: | A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenize, J. Melvin, B. Sundberg, D. Watson, J. White. |
| Date: | June 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0264 |
| Updates: | RFC 0114 |
| Updated by: | RFC 0238 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 172 | The File Transfer Protocol |
| |
| Authors: | A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenzie, J. Melvin, B. Sundberg, D. Watson, J. White. |
| Date: | June 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0265 |
| Updates: | RFC 0114 |
| Updated by: | RFC 0238 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 189 | Interim NETRJS specifications |
| |
|
| |
| RFC 193 | NETWORK CHECKOUT |
| |
| Authors: | E. Harslem, J.F. Heafner. |
| Date: | July 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0198 |
| Updated by: | RFC 0198 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 196 | Mail Box Protocol |
| |
| Authors: | R.W. Watson. |
| Date: | July 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0221 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 198 | Site Certification - Lincoln Labs 360/67 |
| |
|
| |
| RFC 200 | RFC list by number |
| |
| Authors: | J.B. North. |
| Date: | August 1971 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0170, RFC 0160 |
| Obsoleted by: | NIC 7724 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 207 | September Network Working Group meeting |
| |
| Authors: | A. Vezza. |
| Date: | August 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0212 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 211 | ARPA Network Mailing Lists |
| |
| Authors: | J.B. North. |
| Date: | August 1971 |
| Formats: | pdf |
| Obsoletes: | RFC 0168 |
| Obsoleted by: | RFC 0300 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 221 | Mail Box Protocol: Version 2 |
| |
|
| |
| RFC 226 | Standardization of host mnemonics |
| |
| Authors: | P.M. Karp. |
| Date: | September 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0247 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 229 | Standard host names |
| |
| Authors: | J. Postel. |
| Date: | September 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0236 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 235 | Site status |
| |
| Authors: | E. Westheimer. |
| Date: | September 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0240 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 237 | NIC view of standard host names |
| |
| Authors: | R.W. Watson. |
| Date: | October 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0273 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 240 | Site Status |
| |
| Authors: | A.M. McKenzie. |
| Date: | September 1971 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0235 |
| Obsoleted by: | RFC 0252 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 243 | Network and data sharing bibliography |
| |
| Authors: | A.P. Mullery. |
| Date: | October 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0290 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 252 | Network host status |
| |
| Authors: | E. Westheimer. |
| Date: | October 1971 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0240 |
| Obsoleted by: | RFC 0255 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 255 | Status of network hosts |
| |
| Authors: | E. Westheimer. |
| Date: | October 1971 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0252 |
| Obsoleted by: | RFC 0266 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 264 | The Data Transfer Protocol |
| |
| Authors: | A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenize, B. Sundberg, D. Watson, J. White. |
| Date: | January 1972 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0171 |
| Obsoleted by: | RFC 0354 |
| Updated by: | RFC 0310 |
| Also: | RFC 0265 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 265 | The File Transfer Protocol |
| |
| Authors: | A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenzie, J. Melvin, B. Sundberg, D. Watson, J. White. |
| Date: | November 1971 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0172 |
| Obsoleted by: | RFC 0354 |
| Updated by: | RFC 0281, RFC 0294, RFC 0310 |
| Also: | RFC 0264 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 266 | Network host status |
| |
| Authors: | E. Westheimer. |
| Date: | November 1971 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0255 |
| Obsoleted by: | RFC 0267 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 267 | Network Host Status |
| |
| Authors: | E. Westheimer. |
| Date: | November 1971 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0266 |
| Obsoleted by: | RFC 0287 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 287 | Status of Network Hosts |
| |
| Authors: | E. Westheimer. |
| Date: | December 1971 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0267 |
| Obsoleted by: | RFC 0288 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 288 | Network host status |
| |
|
| |
| RFC 289 | What we hope is an official list of host names |
| |
| Authors: | R.W. Watson. |
| Date: | December 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0384 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 292 | Graphics Protocol: Level 0 only |
| |
| Authors: | J.C. Michener, I.W. Cotton, K.C. Kelley, D.E. Liddle, E. Meyer. |
| Date: | January 1972 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0493 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 293 | Network Host Status |
| |
|
| |
| RFC 298 | Network host status |
| |
| Authors: | E. Westheimer. |
| Date: | February 1972 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0293 |
| Obsoleted by: | RFC 0306 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 300 | ARPA Network mailing lists |
| |
|
| |
| RFC 303 | ARPA Network mailing lists |
| |
| Authors: | Network Information Center. Stanford Research Institute. |
| Date: | March 1972 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0300 |
| Obsoleted by: | RFC 0329 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 306 | Network host status |
| |
| Authors: | E. Westheimer. |
| Date: | February 1972 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0298 |
| Obsoleted by: | RFC 0315 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 315 | Network Host Status |
| |
| Authors: | E. Westheimer. |
| Date: | March 1972 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0306 |
| Obsoleted by: | RFC 0319 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 317 | Official Host-Host Protocol Modification: Assigned Link Numbers |
| |
| Authors: | J. Postel. |
| Date: | March 1972 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0604 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 326 | Network Host Status |
| |
|
| |
| RFC 329 | ARPA Network Mailing Lists |
| |
| Authors: | Network Information Center. Stanford Research Institute. |
| Date: | May 1972 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0303 |
| Obsoleted by: | RFC 0363 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 331 | IMP System Change Notification |
| |
| Authors: | J.M. McQuillan. |
| Date: | April 1972 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0343 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 332 | Network Host Status |
| |
|
| |
| RFC 342 | Network Host Status |
| |
|
| |
| RFC 343 | IMP System change notification |
| |
|
| |
| RFC 344 | Network Host Status |
| |
|
| |
| RFC 349 | Proposed Standard Socket Numbers |
| |
|
| |
| RFC 353 | Network host status |
| |
|
| |
| RFC 354 | File Transfer Protocol |
| |
|
| |
| RFC 360 | Proposed Remote Job Entry Protocol |
| |
| Authors: | C. Holland. |
| Date: | June 1972 |
| Formats: | pdf |
| Obsoleted by: | RFC 0407 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 362 | Network Host Status |
| |
|
| |
| RFC 363 | ARPA Network mailing lists |
| |
| Authors: | Network Information Center. Stanford Research Institute. |
| Date: | August 1972 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0329 |
| Obsoleted by: | RFC 0402 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 366 | Network Host Status |
| |
|
| |
| RFC 367 | Network host status |
| |
|
| |
| RFC 378 | Traffic statistics (July 1972) |
| |
| Authors: | A.M. McKenzie. |
| Date: | August 1972 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0391 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 389 | UCLA Campus Computing Network Liaison Staff for ARPA Network |
| |
| Authors: | B. Noble. |
| Date: | August 1972 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0423 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 399 | SMFS Login and Logout |
| |
| Authors: | M. Krilanovich. |
| Date: | September 1972 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0431 |
| Updates: | RFC 0122 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 433 | Socket number list |
| |
|
| |
| RFC 434 | IMP/TIP memory retrofit schedule |
| |
| Authors: | A.M. McKenzie. |
| Date: | January 1973 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0447 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 447 | IMP/TIP memory retrofit schedule |
| |
| Authors: | A.M. McKenzie. |
| Date: | January 1973 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0434 |
| Obsoleted by: | RFC 0476 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 503 | Socket number list |
| |
| Authors: | N. Neigus, J. Postel. |
| Date: | April 1973 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0433 |
| Obsoleted by: | RFC 0739 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 542 | File Transfer Protocol |
| |
|
| |
| RFC 599 | Update on NETRJS |
| |
| Authors: | R.T. Braden. |
| Date: | December 1973 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0189 |
| Obsoleted by: | RFC 0740 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 604 | Assigned link numbers |
| |
|
|
Modifies official host-host protocol. Replaces RFC 377. |
|
| |
| RFC 607 | Comments on the File Transfer Protocol |
| |
| Authors: | M. Krilanovich, G. Gregg. |
| Date: | January 1974 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0624 |
| Updated by: | RFC 0614 |
| Status: | UNKNOWN |
|
An old version; see RFC 624; see also RFCs 614, 542 and 640. |
|
| |
| RFC 608 | Host names on-line |
| |
| Authors: | M.D. Kudlick. |
| Date: | January 1974 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0810 |
| Status: | UNKNOWN |
|
Response to RFC 606; see also RFCs 627, 625 and 623. |
|
| |
| RFC 615 | Proposed Network Standard Data Pathname syntax |
| |
| Authors: | D. Crocker. |
| Date: | March 1974 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0645 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 633 | IMP/TIP preventive maintenance schedule |
| |
| Authors: | A.M. McKenzie. |
| Date: | March 1974 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0638 |
| Status: | UNKNOWN |
|
An old version; see RFC 638. |
|
| |
| RFC 651 | Revised Telnet status option |
| |
| Authors: | D. Crocker. |
| Date: | October 1974 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0859 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 687 | IMP/Host and Host/IMP Protocol changes |
| |
|
|
Addressing hosts on more than 63 IMPs, and other backwards compatible expansions; see also RFCs 690 and 692. |
|
| |
| RFC 698 | Telnet extended ASCII option |
| |
| Authors: | T. Mock. |
| Date: | July 1975 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 5198 |
| Status: | PROPOSED STANDARD |
|
Describes an option to allow transmission of a special kind of extended ASCII used at the Stanford AI and MIT AI Labs. |
|
| |
| RFC 724 | Proposed official standard for the format of ARPA Network messages |
| |
| Authors: | D. Crocker, K.T. Pogran, J. Vittal, D.A. Henderson. |
| Date: | May 1977 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0733 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 729 | Telnet byte macro option |
| |
| Authors: | D. Crocker. |
| Date: | May 1977 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0735 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 731 | Telnet Data Entry Terminal option |
| |
| Authors: | J.D. Day. |
| Date: | June 1977 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0732 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 733 | Standard for the format of ARPA network text messages |
| |
| Authors: | D. Crocker, J. Vittal, K.T. Pogran, D.A. Henderson. |
| Date: | November 1977 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0724 |
| Obsoleted by: | RFC 0822 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 739 | Assigned numbers |
| |
|
| |
| RFC 742 | NAME/FINGER Protocol |
| |
|
| |
| 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 760 | DoD standard Internet Protocol |
| |
| Authors: | J. Postel. |
| Date: | January 1980 |
| Formats: | txt pdf |
| Obsoletes: | IEN 123 |
| Obsoleted by: | RFC 0791 |
| Updated by: | RFC 0777 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 762 | Assigned numbers |
| |
|
| |
| RFC 764 | Telnet Protocol specification |
| |
| Authors: | J. Postel. |
| Date: | June 1980 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0854 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 765 | File Transfer Protocol specification |
| |
|
| |
| RFC 766 | Internet Protocol Handbook: Table of contents |
| |
| Authors: | J. Postel. |
| Date: | July 1980 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0774 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 770 | Assigned numbers |
| |
| Authors: | J. Postel. |
| Date: | September 1980 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0762 |
| Obsoleted by: | RFC 0776 |
| Status: | HISTORIC |
|
|
|
| |
| RFC 772 | Mail Transfer Protocol |
| |
| Authors: | S. Sluizer, J. Postel. |
| Date: | September 1980 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0780, STD 0010 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 776 | Assigned numbers |
| |
|
| |
| RFC 777 | Internet Control Message Protocol |
| |
|
| |
| RFC 780 | Mail Transfer Protocol |
| |
|
| |
| RFC 783 | TFTP Protocol (revision 2) |
| |
| Authors: | K.R. Sollins. |
| Date: | June 1981 |
| Formats: | txt pdf |
| Obsoletes: | IEN 133 |
| Obsoleted by: | RFC 1350 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 788 | Simple Mail Transfer Protocol |
| |
|
| |
| RFC 790 | Assigned numbers |
| |
| Authors: | J. Postel. |
| Date: | September 1981 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0776 |
| Obsoleted by: | RFC 0820 |
| Status: | HISTORIC |
|
|
|
| |
| RFC 802 | ARPANET 1822L Host Access Protocol |
| |
| Authors: | A.G. Malis. |
| Date: | November 1981 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0851 |
| Status: | UNKNOWN |
|
This document proposed two major changes to the current ARPANET host access protocol. The first change will allow hosts to use logical addressing (i.e., host addresses that are independent of their physical location on the ARPANET) to communicate with each other, and the second will allow a host to shorten the amount of time that it may be blocked by its IMP after it presents a message to the network (currently, the IMP can block further input from a host for up to 15 seconds). See RFCs 852 and 851. |
|
| |
| RFC 806 | Proposed Federal Information Processing Standard: Specification for message format for computer based message systems |
| |
| Authors: | National Bureau of Standards. |
| Date: | September 1981 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0841 |
| Status: | UNKNOWN |
|
This RFC deals with Computer Based Message systems which provides a basis for interaction between different CBMS by defining the format of messages passed between them. This RFC is replaced by RFC 841. |
|
| |
| RFC 810 | DoD Internet host table specification |
| |
| Authors: | E.J. Feinler, K. Harrenstien, Z. Su, V. White. |
| Date: | March 1982 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0608 |
| Obsoleted by: | RFC 0952 |
| Status: | UNKNOWN |
|
This RFC specifies a new host table format applicable to both ARPANET and Internet needs. In addition to host name to host address translation and selected protocol information, we have also included network and gateway name to address correspondence, and host operating system information. This RFC obsoletes the host table described in RFC 608. |
|
| |
| RFC 811 | Hostnames Server |
| |
| Authors: | K. Harrenstien, V. White, E.J. Feinler. |
| Date: | March 1982 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0953 |
| Status: | UNKNOWN |
|
This RFC gives a description of what the Hostnames Server is and how to access it. The function of this particular server is to deliver machine-readable name/address information describing networks, gateways, hosts, and eventually domains, within the internet environment. |
|
| |
| RFC 812 | NICNAME/WHOIS |
| |
| Authors: | K. Harrenstien, V. White. |
| Date: | March 1982 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0954, RFC 3912 |
| Status: | UNKNOWN |
|
This RFC gives a description of what the NICNAME/WHOIS Server is and how to access it. This server together with the corresponding Identification Data Base provides online directory look-up equivalent to the ARPANET Directory. |
|
| |
| RFC 820 | Assigned numbers |
| |
|
|
This RFC is an old version, see RFC 870. |
|
| |
| RFC 821 | Simple Mail Transfer Protocol |
| |
|
|
The objective of Simple Mail Transfer Protocol (SMTP) is to transfer mail reliably and efficiently. SMTP is independent of the particular transmission subsystem and requires only a reliable ordered data stream channel. Obsoletes RFC 788, 780, and 772. |
|
| |
| RFC 822 | STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES |
| |
|
|
This document revises the specifications in RFC 733, in order to serve the needs of the larger and more complex ARPA Internet. Some of RFC 733's features failed to gain adequate acceptance. In order to simplify the standard and the software that follows it, these features have been removed. A different addressing scheme is used, to handle the case of internetwork mail; and the concept of re-transmission has been introduced. Obsoletes RFC 733, NIC 41952. |
|
| |
| RFC 825 | Request for comments on Requests For Comments |
| |
|
|
This RFC is intended to clarify the status of RFCs and to provide some guidance for the authors of RFCs in the future. It is in a sense a specification for RFCs. |
|
| |
| RFC 832 | Who talks TCP? |
| |
| Authors: | D. Smallberg. |
| Date: | December 1982 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0833 |
| Status: | UNKNOWN |
|
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 7-Dec-82. |
|
| |
| RFC 833 | Who talks TCP? |
| |
| Authors: | D. Smallberg. |
| Date: | December 1982 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0832 |
| Obsoleted by: | RFC 0834 |
| Status: | UNKNOWN |
|
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 14-Dec-82. |
|
| |
| RFC 834 | Who talks TCP? |
| |
| Authors: | D. Smallberg. |
| Date: | December 1982 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0833 |
| Obsoleted by: | RFC 0835 |
| Status: | UNKNOWN |
|
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 22-Dec-82. |
|
| |
| RFC 835 | Who talks TCP? |
| |
| Authors: | D. Smallberg. |
| Date: | December 1982 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0834 |
| Obsoleted by: | RFC 0836 |
| Status: | UNKNOWN |
|
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 28-Dec-82 through 5-Jan-83. |
|
| |
| RFC 836 | Who talks TCP? |
| |
| Authors: | D. Smallberg. |
| Date: | January 1983 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0835 |
| Obsoleted by: | RFC 0837 |
| Status: | UNKNOWN |
|
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 20-Dec-82. The tests were run on 4-Jan-83 through 5-Jan-83. |
|
| |
| RFC 837 | Who talks TCP? |
| |
| Authors: | D. Smallberg. |
| Date: | January 1983 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0836 |
| Obsoleted by: | RFC 0838 |
| Status: | UNKNOWN |
|
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 11-Jan-83. |
|
| |
| RFC 838 | Who talks TCP? |
| |
| Authors: | D. Smallberg. |
| Date: | January 1983 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0837 |
| Obsoleted by: | RFC 0839 |
| Status: | UNKNOWN |
|
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 18-Jan-83. |
|
| |
| RFC 839 | Who talks TCP? |
| |
| Authors: | D. Smallberg. |
| Date: | January 1983 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0838 |
| Obsoleted by: | RFC 0842 |
| Status: | UNKNOWN |
|
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 25-Jan-83. |
|
| |
| 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 842 | Who talks TCP? - survey of 1 February 83 |
| |
| Authors: | D. Smallberg. |
| Date: | February 1983 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0839 |
| Obsoleted by: | RFC 0843 |
| Status: | UNKNOWN |
|
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 28-Jan-83. The tests were run on 1-Feb-83 and on 2-Feb-83 ISI-VAXA.ARPA. |
|
| |
| RFC 843 | Who talks TCP? - survey of 8 February 83 |
| |
|
|
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 3-Feb-83. The tests were run on 8-Feb-83 and on 9-Feb-83 from ISI-VAXA.ARPA. |
|
| |
| RFC 845 | Who talks TCP? - survey of 15 February 1983 |
| |
| Authors: | D. Smallberg. |
| Date: | February 1983 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0843 |
| Obsoleted by: | RFC 0846 |
| Status: | UNKNOWN |
|
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 3-Feb-83. The tests were run on 15-Feb-83 from ISI-VAXA.ARPA. |
|
| |
| RFC 846 | Who talks TCP? - survey of 22 February 1983 |
| |
| Authors: | D. Smallberg. |
| Date: | February 1983 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0845 |
| Obsoleted by: | RFC 0847 |
| Status: | UNKNOWN |
|
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 18-Feb-83. The tests were run on 22-Feb-83 from ISI-VAXA.ARPA. |
|
| |
| RFC 850 | Standard for interchange of USENET messages |
| |
| Authors: | M.R. Horton. |
| Date: | June 1983 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1036 |
| Status: | UNKNOWN |
|
This memo is distributed as an RFC only to make this information easily accessible to researchers in the ARPA community. It does not specify an Internet standard. This RFC defines the standard format for interchange of Network News articles among USENET sites. It describes the format for articles themselves, and gives partial standards for transmission of news. The news transmission is not entirely standardized in order to give a good deal of flexibility to the individual hosts to choose transmission hardware and software, whether to batch news and so on. |
|
| |
| RFC 851 | ARPANET 1822L Host Access Protocol |
| |
|
|
This RFC specifies the ARPANET 1822L Host Access Protocol, which is a successor to the existing 1822 Host Access Protocol. 1822L allows ARPANET hosts to use logical names as well as 1822's physical port locations to address each other. This RFC is also being presented as a solicitation of comments on 1822L, especially from host network software implementers and maintainers. Obsoletes RFC 802. |
|
| |
| 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 877 | Standard for the transmission of IP datagrams over public data networks |
| |
| Authors: | J.T. Korb. |
| Date: | September 1983 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1356 |
| Status: | UNKNOWN |
|
This RFC specifies a standard adopted by CSNET, the VAN gateway, and other organizations for the transmission of IP datagrams over the X.25-based public data networks. |
|
| |
| 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 882 | Domain names: Concepts and facilities |
| |
|
|
This RFC introduces domain style names, their use for ARPA Internet mail and host address support, and the protocol and servers used to implement domain name facilities. |
|
| |
| RFC 883 | Domain names: Implementation specification |
| |
|
|
This RFC discusses the implementation of domain name servers and resolvers, specifies the format of transactions, and discusses the use of domain names in the context of existing mail systems and other network software. |
|
| |
| RFC 884 | Telnet terminal type option |
| |
| Authors: | M. Solomon, E. Wimmers. |
| Date: | December 1983 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0930 |
| Status: | UNKNOWN |
|
This RFC specifies a standard for the ARPA Internet community. It specifies a method for exchanging terminal type information in the Telnet protocol. |
|
| |
| RFC 892 | ISO Transport Protocol specification |
| |
| Authors: | International Organization for Standardization. |
| Date: | December 1983 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0905 |
| Status: | UNKNOWN |
|
This is a draft version of the transport protocol being standardized by the ISO. This version also appeared in the ACM SIGCOMM Computer Communication Review (V.12, N.3-4) July-October 1982. This version is now out of date. |
|
| |
| 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 901 | Official ARPA-Internet protocols |
| |
| Authors: | J.K. Reynolds, J. Postel. |
| Date: | June 1984 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0880 |
| Obsoleted by: | RFC 0924 |
| Status: | UNKNOWN |
|
This RFC identifies the documents specifying the official protocols used in the ARPA-Internet. Annotations identify any revisions or changes planned. This memo is an official status report on the protocols used in the DARPA research community. See RFC-991. |
|
| |
| RFC 912 | Authentication service |
| |
| Authors: | M. St. Johns. |
| Date: | September 1984 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0931 |
| Status: | UNKNOWN |
|
This memo describes a proposed authentication protocol for verifying the identity of a user of a TCP connection. Given a TCP port number pair, it returns a character string which identifies the owner of that connection on the server's system. Suggested uses include automatic identification and verification of a user during an FTP session, additional verification of a TAC dial up user, and access verification for a generalized network file server. |
|
| |
| RFC 918 | Post Office Protocol |
| |
| Authors: | J.K. Reynolds. |
| Date: | October 1984 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0937 |
| Status: | UNKNOWN |
|
This RFC suggests a simple method for workstations to dynamically access mail from a mailbox server. The intent of the Post Office Protocol (POP) is to allow a user's workstation to access mail from a mailbox server. It is expected that mail will be posted from the workstation to the mailbox server via the Simple Mail Transfer Protocol (SMTP). This RFC specifies a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvement. The status of this protocol is experimental, and this protocol is dependent upon TCP. |
|
| |
| 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 924 | Official ARPA-Internet protocols for connecting personal computers to the Internet |
| |
| Authors: | J.K. Reynolds, J. Postel. |
| Date: | October 1984 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0901 |
| Obsoleted by: | RFC 0944 |
| Status: | UNKNOWN |
|
This RFC identifies the documents specifying the official protocols used in the Internet. This edition of Official ARPA-Internet Protocols obsoletes RFC-900 and earlier editions. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991. |
|
| |
| RFC 926 | Protocol for providing the connectionless mode network services |
| |
| Authors: | International Organization for Standardization. |
| Date: | December 1984 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0994 |
| Status: | UNKNOWN |
|
This note is the draft ISO protocol roughly similar to the DOD Internet Protocol. This document has been prepared by retyping the text of ISO DIS 8473 of May 1984, which is currently undergoing voting within ISO as a Draft International Standard (DIS). This document is distributred as an RFC for information only. It does not specify a standard for the ARPA-Internet. |
|
| |
| RFC 930 | Telnet terminal type option |
| |
| Authors: | M. Solomon, E. Wimmers. |
| Date: | January 1985 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0884 |
| Obsoleted by: | RFC 1091 |
| Status: | UNKNOWN |
|
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that exchange terminal type information within the Telnet protocol are expected to adopt and implement this standard. This standard supersedes RFC-884. The only change is to specify that the TERMINAL-TYPE IS sub-negotiation should be sent only in response to the TERMINAL-TYPE SEND sub-negotiation. |
|
| |
| RFC 931 | Authentication server |
| |
| Authors: | M. St. Johns. |
| Date: | January 1985 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0912 |
| Obsoleted by: | RFC 1413 |
| Status: | UNKNOWN |
|
This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. This is the second draft of this proposal (superseding RFC-912) and incorporates a more formal description of the syntax for the request and response dialog, as well as a change to specify the type of user identification returned. |
|
| |
| RFC 943 | Assigned numbers |
| |
| Authors: | J.K. Reynolds, J. Postel. |
| Date: | April 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 944 | Official ARPA-Internet protocols |
| |
| Authors: | J.K. Reynolds, J. Postel. |
| Date: | April 1985 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0924 |
| Obsoleted by: | RFC 0961 |
| Status: | UNKNOWN |
|
This RFC identifies the documents specifying the official protocols used in the Internet. This edition of Official ARPA-Internet Protocols obsoletes RFC-924 and earlier editions. This RFC will be updated periodically, and current information can be obtained from Joyce Reynolds. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991. |
|
| |
| RFC 945 | DoD statement on the NRC report |
| |
| Authors: | J. Postel. |
| Date: | May 1985 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1039 |
| Status: | UNKNOWN |
|
In May 1983 the National Research Council (NRC) was asked jointly by DoD and NBS to study the issues and recommend a course of action. The final report of the NRC committee was published in February 1985 (see RFC-942). The enclosed letter is from Donald C. Latham (ASDC3I) to DCA transmitting the NRC report and requesting specific actions relative to the recommendations of the report. This RFC reproduces a letter from the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASDC3I) to the Director of the Defense Communications Agency (DCA). This letter is distributed for information only. |
|
| |
| RFC 948 | Two methods for the transmission of IP datagrams over IEEE 802.3 networks |
| |
| Authors: | I. Winston. |
| Date: | June 1985 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1042 |
| Status: | UNKNOWN |
|
This RFC describes two methods of encapsulating Internet Protocol (IP) datagrams on an IEEE 802.3 network. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 954 | NICNAME/WHOIS |
| |
| Authors: | K. Harrenstien, M.K. Stahl, E.J. Feinler. |
| Date: | October 1985 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0812 |
| Obsoleted by: | RFC 3912 |
| Status: | DRAFT STANDARD |
|
This RFC is the official specification of the NICNAME/WHOIS protocol. This memo describes the protocol and the service. This is an update of RFC-812. |
|
| |
| RFC 958 | Network Time Protocol (NTP) |
| |
|
|
This document describes the Network Time Protocol (NTP), a protocol for synchronizing a set of network clocks using a set of distributed clients and servers. NTP is built on the User Datagram Protocol (UDP), which provides a connectionless transport mechanism. It is evolved from the Time Protocol and the ICMP Timestamp message and is a suitable replacement for both. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. |
|
| |
| 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 961 | Official ARPA-Internet protocols |
| |
| Authors: | J.K. Reynolds, J. Postel. |
| Date: | December 1985 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0944 |
| Obsoleted by: | RFC 0991 |
| Status: | UNKNOWN |
|
This memo identifies the documents specifying the official protocols used in the Internet, and comments on any revisions or changes planned. This edition of the Official Protocols updates and obsoletes RFC-944. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991. |
|
| |
| RFC 966 | Host groups: A multicast extension to the Internet Protocol |
| |
| Authors: | S.E. Deering, D.R. Cheriton. |
| Date: | December 1985 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0988 |
| Status: | UNKNOWN |
|
This RFC defines a model of service for Internet multicasting and proposes an extension to the Internet Protocol (IP) to support such a multicast service. Discussion and suggestions for improvements are requested. See RFC-988. |
|
| |
| RFC 969 | NETBLT: A bulk data transfer protocol |
| |
| Authors: | D.D. Clark, M.L. Lambert, L. Zhang. |
| Date: | December 1985 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0998 |
| Status: | UNKNOWN |
|
This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. This is a preliminary discussion of the Network Block Transfer (NETBLT) protocol. NETBLT is intended for the rapid transfer of a large quantity of data between computers. It provides a transfer that is reliable and flow controlled, and is structured to provide maximum throughput over a wide variety of networks. This description is published for discussion and comment, and does not constitute a standard. As the proposal may change, implementation of this document is not advised. See RFC-998. |
|
| |
| RFC 973 | Domain system changes and observations |
| |
|
|
This RFC documents updates to Domain Name System specifications RFC-882 and RFC-883, suggests some operational guidelines, and discusses some experiences and problem areas in the present system. |
|
| |
| 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 977 | Network News Transfer Protocol |
| |
| Authors: | B. Kantor, P. Lapsley. |
| Date: | February 1986 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 3977 |
| Status: | PROPOSED STANDARD |
|
NNTP specifies a protocol for the distribution, inquiry, retrieval, and posting of news articles using a reliable stream-based transmission of news among the ARPA-Internet community. NNTP is designed so that news articles are stored in a central database allowing a subscriber to select only those items he wishes to read. Indexing, cross-referencing, and expiration of aged messages are also provided. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 983 | ISO transport arrives on top of the TCP |
| |
| Authors: | D.E. Cass, M.T. Rose. |
| Date: | April 1986 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1006 |
| Status: | UNKNOWN |
|
This memo describes a proposed protocol standard for the ARPA Internet community. The CCITT and the ISO have defined various session, presentation, and application recommendations which have been adopted by the international community and numerous vendors. To the largest extent possible, it is desirable to offer these higher level services directly in the ARPA Internet, without disrupting existing facilities. This permits users to develop expertise with ISO and CCITT applications which previously were not available in the ARPA Internet. The intention is that hosts in the ARPA-Internet that choose to implement ISO TSAP services on top of the TCP be expected to adopt and implement this standard. Suggestions for improvement are encouraged. |
|
| |
| RFC 984 | PCMAIL: A distributed mail system for personal computers |
| |
| Authors: | D.D. Clark, M.L. Lambert. |
| Date: | May 1986 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0993 |
| Status: | UNKNOWN |
|
This document is a preliminary discussion of the design of a personal-computer-based distributed mail system. Pcmail is a distributed mail system that provides mail service to an arbitrary number of users, each of which owns one or more personal computers (PCs). The system is divided into two halves. The first consists of a single entity called the "repository". The repository is a storage center for incoming mail. Mail for a Pcmail user can arrive externally from the Internet or internally from other repository users. The repository also maintains a stable copy of each user's mail state. The repository is therefore typically a computer with a large amount of disk storage. It is published for discussion and comment, and does not constitute a standard. As the proposal may change, implementation of this document is not advised. See RFC-993. |
|
| |
| RFC 985 | Requirements for Internet gateways - draft |
| |
| Authors: | National Science Foundation, Network Technical Advisory Group. |
| Date: | May 1986 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1009 |
| Status: | UNKNOWN |
|
This RFC summarizes the requirements for gateways to be used on networks supporting the DARPA Internet protocols. While it applies specifically to National Science Foundation research programs, the requirements are stated in a general context and are believed applicable throughout the Internet community. The purpose of this document is to present guidance for vendors offering products that might be used or adapted for use in an Internet application. It enumerates the protocols required and gives references to RFCs and other documents describing the current specification. |
|
| |
| RFC 986 | Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol |
| |
| Authors: | R.W. Callon, H.W. Braun. |
| Date: | June 1986 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1069 |
| Status: | UNKNOWN |
|
This RFC suggests a method to allow the existing IP addressing, including the IP protocol field, to be used for the ISO Connectionless Network Protocol (CLNP). This is a draft solution to one of the problems inherent in the use of "ISO-grams" in the DOD Internet. Related issues will be discussed in subsequent RFCs. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 987 | Mapping between X.400 and RFC 822 |
| |
|
|
The X.400 series protocols have been defined by CCITT to provide an Interpersonal Messaging Service (IPMS), making use of a store and forward Message Transfer Service. It is expected that this standard will be implemented very widely. This document describes a set of mappings which will enable interworking between systems operating the X.400 protocols and systems using RFC-822 mail protocol or protocols derived from RFC-822. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 988 | Host extensions for IP multicasting |
| |
|
|
This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support internetwork multicasting. This specification supersedes that given in RFC-966, and constitutes a proposed protocol standard for IP multicasting in the ARPA-Internet. The reader is directed to RFC-966 for a discussion of the motivation and rationale behind the multicasting extension specified here. |
|
| |
| RFC 989 | Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures |
| |
|
|
This RFC suggests a proposed protocol for the Internet community and requests discussion and suggestions for improvements. This RFC is the outgrowth of a series of IAB Privacy Task Force meetings and of internal working papers distributed for those meetings. This RFC 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. 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 authentication is anticipated. |
|
| |
| 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 991 | Official ARPA-Internet protocols |
| |
| Authors: | J.K. Reynolds, J. Postel. |
| Date: | November 1986 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0961 |
| Obsoleted by: | RFC 1011 |
| Status: | UNKNOWN |
|
This RFC identifies the documents specifying the official protocols used in the Internet. Comments indicate any revisions or changes planned. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. Obsoletes RFC-961, 944 and 924. |
|
| |
| RFC 993 | PCMAIL: A distributed mail system for personal computers |
| |
| Authors: | D.D. Clark, M.L. Lambert. |
| Date: | December 1986 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0984 |
| Obsoleted by: | RFC 1056 |
| Status: | UNKNOWN |
|
This document is a discussion of the Pcmail workstation-based distributed mail system. It is a revision of the design published in NIC RFC-984. The revision is based on discussion and comment fromm a variety of sources, as well as further research into the design of interactive Pcmail clients and the use of client code on machines other than IBM PCs. As this design may change, implementation of this document is not advised. Obsoletes RFC-984. |
|
| |
| RFC 997 | Internet numbers |
| |
|
|
This memo is an official status report on the network numbers used in the Internet community. As of 1-Mar-87 the Network Information Center (NIC) at SRI International has assumed responsibility for assignment of Network Numbers and Autonomous System Numbers. This RFC documents the current assignments of these numbers at the time of this transfer of responsibility. Obsoletes RFC-990, 960, 943, 923 and 900. |
|
| |
| RFC 999 | Requests For Comments summary notes: 900-999 |
| |
| Authors: | A. Westine, J. Postel. |
| Date: | April 1987 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0160 |
| Obsoleted by: | RFC 1000 |
| Status: | UNKNOWN |
|
|
|
| |
| 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 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 1023 | HEMS monitoring and control language |
| |
| Authors: | G. Trewitt, C. Partridge. |
| Date: | October 1987 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1076 |
| Status: | UNKNOWN |
|
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 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 1038 | Draft revised IP security option |
| |
| Authors: | M. St. Johns. |
| Date: | January 1988 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1108 |
| Status: | UNKNOWN |
|
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 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 1048 | BOOTP vendor information extensions |
| |
|
|
This memo proposes an addition to the Bootstrap Protocol (BOOTP). Comments and suggestions for improvements are sought. |
|
| |
| RFC 1050 | RPC: Remote Procedure Call Protocol specification |
| |
| Authors: | Sun Microsystems. |
| Date: | April 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 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 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 pdf |
| Obsoleted by: | RFC 1191 |
| Status: | UNKNOWN |
|
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 pdf |
| Obsoleted by: | RFC 1155 |
| Status: | STANDARD |
|
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 |
| |
| Authors: | K. McCloghrie, M.T. Rose. |
| Date: | August 1988 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1156 |
| Status: | UNKNOWN |
|
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 pdf |
| Obsoleted by: | RFC 1098 |
| Status: | UNKNOWN |
|
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 1072 | TCP extensions for long-delay paths |
| |
| Authors: | V. Jacobson, R.T. Braden. |
| Date: | October 1988 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1323, RFC 2018 |
| Status: | UNKNOWN |
|
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 1080 | Telnet remote flow control option |
| |
| Authors: | C.L. Hedrick. |
| Date: | November 1988 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1372 |
| Status: | UNKNOWN |
|
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 |
| |
| Authors: | M.T. Rose. |
| Date: | November 1988 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1225 |
| Status: | UNKNOWN |
|
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 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 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 1089 | SNMP over Ethernet |
| |
| Authors: | M. Schoffstall, C. Davin, M. Fedor, J. Case. |
| Date: | February 1989 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 4789 |
| Status: | UNKNOWN |
|
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 1095 | Common Management Information Services and Protocol over TCP/IP (CMOT) |
| |
| Authors: | U.S. Warrier, L. Besaw. |
| Date: | April 1989 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1189 |
| Status: | UNKNOWN |
|
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 1098 | Simple Network Management Protocol (SNMP) |
| |
| Authors: | J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin. |
| Date: | April 1989 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1067 |
| Obsoleted by: | RFC 1157 |
| Status: | UNKNOWN |
|
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 1100 | IAB official protocol standards |
| |
| Authors: | Defense Advanced Research Projects Agency, Internet Activities Board. |
| Date: | April 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 1103 | Proposed standard for the transmission of IP datagrams over FDDI Networks |
| |
| Authors: | D. Katz. |
| Date: | June 1989 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1188 |
| Status: | UNKNOWN |
|
This RFC specifies a method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK] |
|
| |
| RFC 1105 | Border Gateway Protocol (BGP) |
| |
| Authors: | K. Lougheed, Y. Rekhter. |
| Date: | June 1989 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1163 |
| Status: | EXPERIMENTAL |
|
This RFC outlines a specific approach for the exchange of network reachability information between Autonomous Systems. Updated by RFCs 1163 and 1164. [STANDARDS-TRACK] |
|
| |
| RFC 1111 | Request for comments on Request for Comments: Instructions to RFC authors |
| |
|
|
This RFC specifies a standard for the Internet community. Authors of RFCs are expected to adopt and implement this standard. |
|
| |
| RFC 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 1116 | Telnet Linemode option |
| |
| Authors: | D.A. Borman. |
| Date: | August 1989 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1184 |
| Status: | PROPOSED STANDARD |
|
Hosts on the Internet that support Linemode within the Telnet protocol are expected to adopt and implement this protocol. Obsoleted by RFC 1184. [STANDARDS-TRACK] |
|
| |
| RFC 1117 | Internet numbers |
| |
|
|
This memo is an official status report on the network numbers and the autonomous system numbers used in the Internet community. |
|
| |
| RFC 1119 | Network Time Protocol (version 2) specification and implementation |
| |
|
|
This document describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. NTP provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse internet operating at rates from mundane to lightwave. It uses a returnable-time design in which a distributed subnet of time servers operating in a self- organizing, hierarchical-master-slave configuration synchronizes local clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute reference time via local routing algorithms and time daemons. [STANDARDS-TRACK] |
|
| |
| RFC 1120 | Internet Activities Board |
| |
| Authors: | V. Cerf. |
| Date: | September 1989 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1160 |
| Status: | INFORMATIONAL |
|
This RFC provides a history and description of the Internet Activities Board (IAB) and its subsidiary organizations. This memo is for informational use and does not constitute a standard. |
|
| |
| RFC 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 1131 | OSPF specification |
| |
| Authors: | J. Moy. |
| Date: | October 1989 |
| Formats: | txt pdf ps |
| Obsoleted by: | RFC 1247 |
| Status: | PROPOSED STANDARD |
|
This RFC is the specification of the Open Shortest Path First (OSPF) Internet routing protocol. OSPF is in the class of Internal Gateway Protocols (IGPs) for distributing routing information between gateways of a single Autonomous System. This routing protocol is based on the link-state approach (in contrast to the distance-vector approach). This specification was developed by the OSPF Working Group of the Internet Engineering Task Force. [STANDARDS-TRACK] |
|
| |
| RFC 1134 | Point-to-Point Protocol: A proposal for multi-protocol transmission of datagrams over Point-to-Point links |
| |
| Authors: | D. Perkins. |
| Date: | November 1989 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1171 |
| Status: | PROPOSED STANDARD |
|
The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is composed of three parts:
1. A method for encapsulating datagrams over serial links.
2. An extensible Link Control Protocol (LCP).
3. A family of Network Control Protocols (NCP) for establishing and configuring different network-layer protocols.
This document defines the encapsulation scheme, the basic LCP, and anNCP for establishing and configuring the Internet Protocol (IP)(called the IP Control Protocol, IPCP).
The options and facilities used by the LCP and the IPCP are defined in separate documents. Control protocols for configuring and utilizing other network-layer protocols besides IP (e.g., DECNET,OSI) are expected to be developed as needed. |
|
| |
| RFC 1138 | Mapping between X.400(1988) / ISO 10021 and RFC 822 |
| |
|
|
Ths RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. This memo updates RFCs 822, 987, and 1026. |
|
| |
| RFC 1139 | Echo function for ISO 8473 |
| |
| Authors: | R.A. Hagens. |
| Date: | January 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1574, RFC 1575 |
| Status: | PROPOSED STANDARD |
|
This memo defines an echo function for the connection-less network layer protocol. Two mechanisms are introduced that may be used to implement the echo function. The first mechanism is recommended as an interim solution for the Internet community. The second mechanism will be progressed to the ANSI X3S3.3 working group for consideration as a work item.
When an ISO standard is adopted that provides functionality similar to that described by this memo, then this memo will become obsolete and superceded by the ISO standard. |
|
| |
| RFC 1140 | IAB official protocol standards |
| |
| Authors: | Defense Advanced Research Projects Agency, Internet Activities Board. |
| Date: | May 1990 |
| Formats: | txt 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 1145 | TCP alternate checksum options |
| |
| Authors: | J. Zweig, C. Partridge. |
| Date: | February 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1146 |
| Status: | EXPERIMENTAL |
|
This memo is suggests a pair of TCP options to allow use of alternate data checksum algorithms in the TCP header. The use of these options is experimental, and not recommended for production use. |
|
| |
| RFC 1147 | FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices |
| |
| Authors: | R.H. Stine. |
| Date: | April 1990 |
| Formats: | txt pdf ps |
| Obsoleted by: | RFC 1470 |
| Status: | INFORMATIONAL |
|
The goal of this FYI memo is to provide practical information to site administrators and network managers. This memo provides information for the Internet community. It does not specify any standard. It is not a statement of IAB policy or recommendations. [Also FYI 2.] This catalog contains descriptions of several tools available to assist network managers in debugging and maintaining TCP/IP internets and interconnected communications resources. Entries in the catalog tell what a tool does, how it works, and how it can be obtained. |
|
| |
| RFC 1148 | Mapping between X.400(1988) / ISO 10021 and RFC 822 |
| |
|
|
This RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. This edition includes material lost in editing. |
|
| |
| RFC 1154 | Encoding header field for internet messages |
| |
| Authors: | D. Robinson, R. Ullmann. |
| Date: | April 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1505 |
| Status: | EXPERIMENTAL |
|
This RFC proposes an elective experimental Encoding header field to permit the mailing of multi-part, multi-structured messages. The use of Encoding updates RFC 1049 (Content-Type), and is a suggested update to RFCs 1113, 1114, and 1115 (Privacy Enhancement). |
|
| |
| RFC 1158 | Management Information Base for network management of TCP/IP-based internets: MIB-II |
| |
| Authors: | M.T. Rose. |
| Date: | May 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1213 |
| Status: | PROPOSED STANDARD |
|
This memo defines the second version of the Management Information Base (MIB-II) for use with network management protocols in TCP/IP- based internets. In particular, together with its companion memos which describe the structure of management information (RFC 1155) along with the network management protocol (RFC 1157) for TCP/IP- based internets, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular the Internet community. This document on MIB-II incorporates all of the technical content of RFC 1156 on MIB-I and extends it, without loss of compatibilty. [STANDARDS-TRACK] |
|
| |
| RFC 1159 | Message Send Protocol |
| |
| Authors: | R. Nelson. |
| Date: | June 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1312 |
| Status: | EXPERIMENTAL |
|
This RFC suggests an Experimental Protocol for the Internet community. Hosts on the Internet that choose to implement a Message Send Protocol may experiment with this protocol. |
|
| |
| RFC 1161 | SNMP over OSI |
| |
| Authors: | M.T. Rose. |
| Date: | June 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1418 |
| Status: | EXPERIMENTAL |
|
This memo defines an experimental means for running the Simple Network Management Protocol (SNMP) over OSI transports. This memo does not specify a standard for the Internet community, |
|
| |
| RFC 1162 | Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) Management Information Base |
| |
| Authors: | G. Satz. |
| Date: | June 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1238 |
| Status: | EXPERIMENTAL |
|
This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. This memo does not specify a standard for the Internet community. |
|
| |
| RFC 1163 | Border Gateway Protocol (BGP) |
| |
| 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 1171 | Point-to-Point Protocol for the transmission of multi-protocol datagrams over Point-to-Point links |
| |
| Authors: | D. Perkins. |
| Date: | July 1990 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1134 |
| Obsoleted by: | RFC 1331 |
| Status: | DRAFT STANDARD |
|
The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is composed of three parts:
1. A method for encapsulating datagrams over serial links.
2. An extensible Link Control Protocol (LCP).
3. A family of Network Control Protocols (NCP) for establishing and configuring different network-layer protocols.
This document defines the encapsulation scheme, the basic LCP, and anNCP for establishing and configuring the Internet Protocol (IP)(called the IP Control Protocol, IPCP).
The options and facilities used by the LCP and the IPCP are defined in separate documents. Control protocols for configuring and utilizing other network-layer protocols besides IP (e.g., DECNET,OSI) are expected to be developed as needed. |
|
| |
| RFC 1172 | Point-to-Point Protocol (PPP) initial configuration options |
| |
| Authors: | D. Perkins, R. Hobby. |
| Date: | July 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1331, RFC 1332 |
| Status: | PROPOSED STANDARD |
|
The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is composed of
1) a method for encapsulating datagrams over serial links,2) an extensible Link Control Protocol (LCP), and3) a family of Network Control Protocols (NCP) for establishing and configuring different network-layer protocols.
The PPP encapsulating scheme, the basic LCP, and an NCP for controlling and establishing the Internet Protocol (IP) (called theIP Control Protocol, IPCP) are defined in The Point-to-Point Protocol(PPP) [1].
This document defines the intial options used by the LCP and IPCP. It also defines a method of Link Quality Monitoring and a simple authentication scheme. |
|
| |
| RFC 1177 | FYI on Questions and Answers: Answers to commonly asked "new internet user" questions |
| |
| Authors: | G.S. Malkin, A.N. Marine, J.K. Reynolds. |
| Date: | August 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1206 |
| Status: | INFORMATIONAL |
|
This FYI RFC is one of three FYI's called, "Questions and Answers" (Q/A), produced by the User Services Working Group (USWG) of the Internet Engineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify any standard. [Also FYI 4.] |
|
| |
| RFC 1185 | TCP Extension for High-Speed Paths |
| |
| Authors: | V. Jacobson, R.T. Braden, L. Zhang. |
| Date: | October 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1323 |
| Status: | EXPERIMENTAL |
|
This memo describes an Experimental Protocol extension to TCP for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. |
|
| |
| RFC 1186 | MD4 Message Digest Algorithm |
| |
| Authors: | R.L. Rivest. |
| Date: | October 1990 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1320 |
| Status: | INFORMATIONAL |
|
This RFC is the specification of the MD4 Digest Algorithm. If you are going to implement MD4, it is suggested you do it this way. This memo is for informational use and does not constitute a standard. |
|
| |
| RFC 1190 | Experimental Internet Stream Protocol: Version 2 (ST-II) |
| |
| Authors: | C. Topolcic. |
| Date: | October 1990 |
| Formats: | txt pdf |
| Obsoletes: | IEN 119 |
| Obsoleted by: | RFC 1819 |
| Status: | EXPERIMENTAL |
|
This memo defines a revised version of the Internet Stream Protocol, originally defined in IEN-119 [8], based on results from experiments with the original version, and subsequent requests, discussion, and suggestions for improvements. This is a Limited-Use Experimental Protocol. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. |
|
| |
| RFC 1194 | Finger User Information Protocol |
| |
|
|
This memo describes the Finger User Information Protocol. This is a simple protocol which provides an interface to a remote user information program.
Based on RFC 742, a description of the original Finger protocol, this memo attempts to clarify the expected communication between the two ends of a Finger connection. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition. |
|
| |
| RFC 1196 | Finger User Information Protocol |
| |
|
|
This memo describes the Finger User Information Protocol. This is a simple protocol which provides an interface to a remote user information program.
Based on RFC 742, a description of the original Finger protocol, this memo attempts to clarify the expected communication between the two ends of a Finger connection. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition. This edition corrects and clarifies in a minor way, RFC 1194. |
|
| |
| RFC 1200 | IAB official protocol standards |
| |
| Authors: | Defense Advanced Research Projects Agency, Internet Activities Board. |
| Date: | April 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 1206 | FYI on Questions and Answers: Answers to commonly asked "new Internet user" questions |
| |
| Authors: | G.S. Malkin, A.N. Marine. |
| Date: | February 1991 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1177 |
| Obsoleted by: | RFC 1325 |
| Status: | INFORMATIONAL |
|
This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify any standard. [FYI 4] |
|
| |
| RFC 1218 | Naming scheme for c=US |
| |
| Authors: | North American Directory Forum. |
| Date: | April 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1255, RFC 1417 |
| Status: | INFORMATIONAL |
|
This RFC is a near-verbatim copy of a document, known as NADF-123, which has been produced by the North American Directory Forum (NADF). As a part of its charter, the NADF must reach agreement as to how entries are named in the public portions of the North American Directory. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1220 | Point-to-Point Protocol extensions for bridging |
| |
| Authors: | F. Baker. |
| Date: | April 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1638 |
| Status: | PROPOSED STANDARD |
|
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 1225 | Post Office Protocol: Version 3 |
| |
| Authors: | M.T. Rose. |
| Date: | May 1991 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1081 |
| Obsoleted by: | RFC 1460 |
| Status: | DRAFT STANDARD |
|
This memo suggests a simple method for workstations to dynamically access mail from a mailbox server. [STANDARDS-TRACK] |
|
| |
| RFC 1228 | SNMP-DPI: Simple Network Management Protocol Distributed Program Interface |
| |
| Authors: | G. Carpenter, B. Wijnen. |
| Date: | May 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1592 |
| Status: | EXPERIMENTAL |
|
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 |
| |
| Authors: | K. McCloghrie. |
| Date: | May 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1573 |
| Updated by: | RFC 1239 |
| Status: | PROPOSED STANDARD |
|
This RFC contains definitions of managed objects used as experimental extensions to the generic interfaces structure of MIB-II. [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 |
| |
| Authors: | F. Baker, C.P. Kolb. |
| Date: | May 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1406 |
| Updated by: | RFC 1239 |
| Status: | PROPOSED STANDARD |
|
|
|
| |
| RFC 1233 | Definitions of managed objects for the DS3 Interface type |
| |
| Authors: | T.A. Cox, K. Tesink. |
| Date: | May 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1407 |
| Updated by: | RFC 1239 |
| Status: | PROPOSED STANDARD |
|
This memo defines objects for managing DS3 Interface objects for use with the SNMP protocol. [STANDARDS-TRACK] |
|
| |
| RFC 1237 | Guidelines for OSI NSAP Allocation in the Internet |
| |
| Authors: | R. Colella, E. Gardner, R. Callon. |
| Date: | July 1991 |
| Formats: | txt pdf ps |
| Obsoleted by: | RFC 1629 |
| Status: | PROPOSED STANDARD |
|
This paper provides guidelines for allocating NSAPs in the Internet.[STANDARDS-TRACK] |
|
| |
| RFC 1243 | AppleTalk Management Information Base |
| |
| Authors: | S. Waldbusser. |
| Date: | July 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1742 |
| Status: | PROPOSED STANDARD |
|
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 pdf |
| Obsoleted by: | RFC 2196 |
| Status: | INFORMATIONAL |
|
This FYI RFC is a first attempt at providing Internet users guidance on how to deal with security issues in the Internet. This FYI RFC provides information for the Internet community. It does not specify an Internet standard. [FYI 8] |
|
| |
| RFC 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 |
| |
| Authors: | F. Baker, R. Coltun. |
| Date: | July 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1252 |
| Updated by: | RFC 1349 |
| Status: | PROPOSED STANDARD |
|
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 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 |
| |
| Authors: | G. Malkin. |
| Date: | August 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1336 |
| Status: | INFORMATIONAL |
|
This FYI RFC contains biographical information about members of the Internet Activities Board (IAB), the Internet Engineering Steering Group (IESG) of the Internet Engineering Task Force (IETF), and the the Internet Research Steering Group (IRSG) of the Internet Research Task Force (IRTF). This memo provides information for the Internet community. It does not specify an Internet standard. [FYI 9] |
|
| |
| RFC 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 1255 | A Naming Scheme for c=US |
| |
| Authors: | The North American Directory Forum. |
| Date: | September 1991 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1218 |
| Obsoleted by: | RFC 1417 |
| Status: | INFORMATIONAL |
|
This memo documents the NADF's agreement as to how entries are named in the public portions of the North American Directory. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 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 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 1269 | Definitions of Managed Objects for the Border Gateway Protocol: Version 3 |
| |
| Authors: | S. Willis, J.W. Burruss. |
| Date: | October 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 4273 |
| Status: | PROPOSED STANDARD |
|
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 1271 | Remote Network Monitoring Management Information Base |
| |
| Authors: | S. Waldbusser. |
| Date: | November 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1757 |
| Updated by: | RFC 1513 |
| Status: | PROPOSED STANDARD |
|
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 1274 | The COSINE and Internet X.500 Schema |
| |
| Authors: | P. Barker, S. Kille. |
| Date: | November 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 4524 |
| Status: | PROPOSED STANDARD |
|
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 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 1283 | SNMP over OSI |
| |
| Authors: | M. Rose. |
| Date: | December 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1418 |
| Status: | EXPERIMENTAL |
|
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 |
| |
| Authors: | J. Cook, Ed.. |
| Date: | December 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1398 |
| Status: | PROPOSED STANDARD |
|
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 1286 | Definitions of Managed Objects for Bridges |
| |
| Authors: | E. Decker, P. Langille, A. Rijsinghani, K. McCloghrie. |
| Date: | December 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1493, RFC 1525 |
| Status: | PROPOSED STANDARD |
|
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 1289 | DECnet Phase IV MIB Extensions |
| |
| Authors: | J. Saperia. |
| Date: | December 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1559 |
| Status: | PROPOSED STANDARD |
|
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 |
| |
| Authors: | J. Martin. |
| Date: | December 1991 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1402 |
| Status: | INFORMATIONAL |
|
This document was presented at the 1991 ACM SIGUCCS User ServicesConference. It appears here in its updated form.
There is a wealth of information on the network. In fact, so much information, that you could spend your entire life browsing. This paper will present some of the "gold nuggets" of information and file repositories on the network that could be of use to end users.
The ultimate goal is to make the route to these sources of information invisible to the user. At present, this is not easy to do. I will explain some of the techniques that can be used to make these nuggets easier to pick up so that we can all be richer. |
|
| |
| RFC 1292 | A Catalog of Available X.500 Implementations |
| |
| Authors: | R. Lang, R. Wright. |
| Date: | January 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1632 |
| Status: | INFORMATIONAL |
|
The goal of this document is to provide information regarding the availability and capability of implementations of X.500. Comments and critiques of this document, and new or updated descriptions ofX.500 implementations are welcome. Send them to the DirectoryInformation Services Infrastructure (DISI) Working Group(disi@merit.edu) or to the editors. |
|
| |
| RFC 1293 | Inverse Address Resolution Protocol |
| |
| Authors: | T. Bradley, C. Brown. |
| Date: | January 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2390 |
| Status: | PROPOSED STANDARD |
|
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 |
| |
| Authors: | T. Bradley, C. Brown, A. Malis. |
| Date: | January 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1490, RFC 2427 |
| Status: | PROPOSED STANDARD |
|
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 pdf |
| Obsoleted by: | RFC 1417 |
| Status: | INFORMATIONAL |
|
This RFC is a near-verbatim copy of a document, known as NADF-265, which has been produced by the North American Directory Forum (NADF).
User Bill of Rights for entries and listings in the Public Directory
The mission of the North American Directory Forum is to provide interconnected electronic directories which empower users with unprecedented access to public information. To address significant security and privacy issues, the North American Directory Forum introduces the following "User Bill of Rights" for entries in thePublic Directory. As a user, you have:
I. The right not to be listed.
II. The right to have you or your agent informed when your entry is created.
III. The right to examine your entry.
IV. The right to correct inaccurate information in your entry.
V. The right to remove specific information from your entry.
VI. The right to be assured that your listing in thePublic Directory will comply with US or Canadian law regulating privacy or access information.
VII. The right to expect timely fulfillment of these rights. |
|
| |
| RFC 1298 | SNMP over IPX |
| |
| Authors: | R. Wormley, S. Bostock. |
| Date: | February 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1420 |
| Status: | INFORMATIONAL |
|
This memo defines a convention for encapsulating Simple NetworkManagement Protocol (SNMP) [1] packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol [2]. |
|
| |
| RFC 1304 | Definitions of Managed Objects for the SIP Interface Type |
| |
| Authors: | T. Cox, K. Tesink, Eds.. |
| Date: | February 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1694 |
| Status: | PROPOSED STANDARD |
|
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 SIP (SMDS InterfaceProtocol) objects. |
|
| |
| RFC 1310 | The Internet Standards Process |
| |
| Authors: | L. Chapin. |
| Date: | March 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1602 |
| Status: | INFORMATIONAL |
|
This memo documents the process currently used for the standardization of Internet protocols and procedures. [STANDARDS-TRACK] |
|
| |
| RFC 1315 | Management Information Base for Frame Relay DTEs |
| |
| Authors: | C. Brown, F. Baker, C. Carvalho. |
| Date: | April 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2115 |
| Status: | PROPOSED STANDARD |
|
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 Frame Relay. |
|
| |
| RFC 1316 | Definitions of Managed Objects for Character Stream Devices |
| |
| Authors: | B. Stewart. |
| Date: | April 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1658 |
| Status: | PROPOSED STANDARD |
|
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 the management of character stream devices. [STANDARDS-TRACK] |
|
| |
| RFC 1317 | Definitions of Managed Objects for RS-232-like Hardware Devices |
| |
| Authors: | B. Stewart. |
| Date: | April 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1659 |
| Status: | PROPOSED STANDARD |
|
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 the management of RS-232-like devices. [STANDARDS-TRACK] |
|
| |
| RFC 1318 | Definitions of Managed Objects for Parallel-printer-like Hardware Devices |
| |
| Authors: | B. Stewart. |
| Date: | April 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1660 |
| Status: | PROPOSED STANDARD |
|
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 the management of parallel-printer- like devices. [STANDARDS-TRACK] |
|
| |
| RFC 1325 | FYI on Questions and Answers Answers to Commonly asked "New Internet User" Questions |
| |
| Authors: | G. Malkin, A. Marine. |
| Date: | May 1992 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1206 |
| Obsoleted by: | RFC 1594 |
| Status: | INFORMATIONAL |
|
This FYI RFC is one of two FYI's called, "Questions and Answers"(Q/A), produced by the User Services Working Group of the InternetEngineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet. |
|
| |
| RFC 1327 | Mapping between X.400(1988) / ISO 10021 and RFC 822 |
| |
|
|
This document describes a set of mappings which will enable interworking between systems operating the CCITT X.400 1988)Recommendations on Message Handling Systems / ISO IEC 10021 MessageOriented Text Interchange Systems (MOTIS) [CCITT/ISO88a], and systems using the RFC 822 mail protocol [Crocker82a] or protocols derived from RFC 822. The approach aims to maximise the services offered across the boundary, whilst not requiring unduly complex mappings.The mappings should not require any changes to end systems. This document is a revision based on RFCs 987, 1026, 1138, and 1148[Kille86a,Kille87a] which it obsoletes.
This document specifies a mapping between two protocols. This specification should be used when this mapping is performed on theDARPA Internet or in the UK Academic Community. This specification may be modified in the light of implementation experience, but no substantial changes are expected. |
|
| |
| RFC 1331 | The Point-to-Point Protocol (PPP) for the Transmission of Multi-protocol Datagrams over Point-to-Point Links |
| |
|
|
The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is comprised of three main components:
1. A method for encapsulating datagrams over serial links.
2. A Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection.
3. A family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols.
This document defines the PPP encapsulation scheme, together with thePPP Link Control Protocol (LCP), an extensible option negotiation protocol which is able to negotiate a rich assortment of configuration parameters and provides additional management functions.
This RFC is a product of the Point-to-Point Protocol Working Group of the Internet Engineering Task Force (IETF). Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu mailing list. |
|
| |
| RFC 1333 | PPP Link Quality Monitoring |
| |
| Authors: | W. Simpson. |
| Date: | May 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1989 |
| Status: | PROPOSED STANDARD |
|
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, which allows negotiation of a Quality Protocol for continuous monitoring of the viability of the link.
This document defines a protocol for generating Link-Quality-Reports.
This RFC is a product of the Point-to-Point Protocol Working Group of the Internet Engineering Task Force (IETF). Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu mailing list. |
|
| |
| RFC 1334 | PPP Authentication Protocols |
| |
| Authors: | B. Lloyd, W. Simpson. |
| Date: | October 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1994 |
| Status: | PROPOSED STANDARD |
|
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, which allows negotiation of an Authentication Protocol for authenticating its peer before allowing Network Layer protocols to transmit over the link.
This document defines two protocols for Authentication: the PasswordAuthentication Protocol and the Challenge-Handshake AuthenticationProtocol. This memo is the product of the Point-to-Point ProtocolWorking Group of the Internet Engineering Task Force (IETF).Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu mailing list. |
|
| |
| RFC 1338 | Supernetting: an Address Assignment and Aggregation Strategy |
| |
| Authors: | V. Fuller, T. Li, J. Yu, K. Varadhan. |
| Date: | June 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1519 |
| Status: | INFORMATIONAL |
|
This memo discusses strategies for address assignment of the existingIP address space with a view to conserve the address space and stem the explosive growth of routing tables in default-route-free routers run by transit routing domain providers. |
|
| |
| 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 1341 | MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies |
| |
| Authors: | N. Borenstein, N. Freed. |
| Date: | June 1992 |
| Formats: | txt pdf ps |
| Obsoleted by: | RFC 1521 |
| Status: | PROPOSED STANDARD |
|
This document redefines the format of message bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information. [STANDARDS-TRACK] |
|
| |
| RFC 1342 | Representation of Non-ASCII Text in Internet Message Headers |
| |
| Authors: | K. Moore. |
| Date: | June 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1522 |
| Status: | PROPOSED STANDARD |
|
This memo describes an extension to the message format defined in [1](known to the IETF Mail Extensions Working Group as "RFC 1341"), to allow the representation of character sets other than ASCII in RFC822 message headers. The extensions described were designed to be highly compatible with existing Internet mail handling software, and to be easily implemented in mail readers that support RFC 1341. |
|
| |
| RFC 1348 | DNS NSAP RRs |
| |
|
|
This RFC defines the format of two new Resource Records (RRs) for the Domain Name System (DNS), and reserves corresponding DNS type mnemonic and numerical codes. This memo defines an Experimental Protocol for the Internet community. |
|
| |
| RFC 1349 | Type of Service in the Internet Protocol Suite |
| |
|
|
This memo changes and clarifies some aspects of the semantics of the Type of Service octet in the Internet Protocol (IP) header. [STANDARDS-TRACK] |
|
| |
| RFC 1354 | IP Forwarding Table MIB |
| |
| Authors: | F. Baker. |
| Date: | July 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2096 |
| Status: | PROPOSED STANDARD |
|
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 routes in the IPInternet.
It is proposed that the ipRouteTable defined by MIB-II (RFC 1213) be deprecated and replaced with this table. This adds the ability to set or display multi-path routes, and varying routes by network management policy. |
|
| |
| RFC 1357 | A Format for E-mailing Bibliographic Records |
| |
| Authors: | D. Cohen. |
| Date: | July 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1807 |
| Status: | INFORMATIONAL |
|
This memo defines a format for E-mailing bibliographic records of technical reports. It is intended to accelerate the dissemination of information about new Computer Science Technical Reports (CS-TR). |
|
| |
| RFC 1358 | Charter of the Internet Architecture Board (IAB) |
| |
| Authors: | L. Chapin. |
| Date: | August 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1601 |
| Status: | INFORMATIONAL |
|
The Internet Architecture Board (IAB) shall be constituted and shall operate as a technical advisory group of the Internet Society. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| 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 1361 | Simple Network Time Protocol (SNTP) |
| |
|
|
This memorandum describes the Simple Network Time Protocol (SNTP), which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. SNTP can be used when the ultimate performance of the full NTP implementation described inRFC-1305 is not needed or justified. It involves no change to the current or previous NTP specification versions or known implementations, but rather a clarification of certain design features of NTP which allow operation in a simple, stateless RPC mode with accuracy and reliability expectations similar to the UDP/TIME protocol described in RFC-868.
This memorandum does not obsolete or update any RFC. A working knowledge of RFC-1305 is not required for an implementation of SNTP. |
|
| |
| RFC 1362 | Novell IPX over Various WAN Media (IPXWAN) |
| |
| Authors: | M. Allen. |
| Date: | September 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1634 |
| Status: | INFORMATIONAL |
|
This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocolNovell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. |
|
| |
| RFC 1364 | BGP OSPF Interaction |
| |
|
|
This memo defines the various criteria to be used when designingAutonomous System Border Routers (ASBR) that will run BGP with otherASBRs external to the AS and OSPF as its IGP. |
|
| |
| RFC 1366 | Guidelines for Management of IP Address Space |
| |
| Authors: | E. Gerich. |
| Date: | October 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1466 |
| Status: | INFORMATIONAL |
|
This document has been reviewed by the Federal Engineering Task Force(FEPG) on behalf of the Federal Networking Council (FNC), the co- chairs of the International Engineering Planning Group (IEPG), and the Reseaux IP Europeens (RIPE). There was general consensus by those groups to support the recommendations proposed in this document for management of the IP address space. |
|
| |
| RFC 1367 | Schedule for IP Address Space Management Guidelines |
| |
| Authors: | C. Topolcic. |
| Date: | October 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1467 |
| Status: | INFORMATIONAL |
|
This memo suggests a schedule for the implementation of the IP network number allocation plan described in RFC 1366. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1368 | Definition of Managed Objects for IEEE 802.3 Repeater Devices |
| |
| Authors: | D. McMaster, K. McCloghrie. |
| Date: | October 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1516 |
| Status: | PROPOSED STANDARD |
|
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 IEEE 802.3 10Mb/second baseband repeaters, sometimes referred to as "hubs." |
|
| |
| RFC 1374 | IP and ARP on HIPPI |
| |
| Authors: | J. Renwick, A. Nicholson. |
| Date: | October 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2834 |
| Status: | PROPOSED STANDARD |
|
The ANSI X3T9.3 committee has drafted a proposal for the encapsulation of IEEE 802.2 LLC PDUs and, by implication, IP onHIPPI. Another X3T9.3 draft describes the operation of HIPPI physical switches. X3T9.3 chose to leave HIPPI networking issues largely outside the scope of their standards; this document discusses methods of using of ANSI standard HIPPI hardware and protocols in the context of the Internet, including the use of HIPPI switches as LANs and interoperation with other networks. |
|
| |
| RFC 1376 | The PPP DECnet Phase IV Control Protocol (DNCP) |
| |
| Authors: | S. Senum. |
| Date: | November 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1762 |
| Status: | PROPOSED STANDARD |
|
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 configuringDigital's DNA Phase IV Routing protocol (DECnet Phase IV) over PPP.This document applies only to DNA Phase IV Routing messages (both data and control), and not to other DNA Phase IV protocols (MOP, LAT, etc.). |
|
| |
| RFC 1384 | Naming Guidelines for Directory Pilots |
| |
| Authors: | P. Barker, S.E. Hardcastle-Kille. |
| Date: | January 1993 |
| Formats: | txt pdf ps |
| Obsoleted by: | RFC 1617, RTR_0011 |
| Status: | INFORMATIONAL |
|
Deployment of a Directory will benefit from following certain guidelines. This document defines a number of naming guidelines.Alignment to these guidelines is recommended for directory pilots. |
|
| |
| RFC 1386 | The US Domain |
| |
| Authors: | A. Cooper, J. Postel. |
| Date: | December 1992 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1480 |
| Status: | INFORMATIONAL |
|
This is a description of the US Top Level Domains on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1387 | RIP Version 2 Protocol Analysis |
| |
| Authors: | G. Malkin. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1721 |
| Status: | INFORMATIONAL |
|
As required by Routing Protocol Criteria (RFC 1264), this report documents the key features of the RIP-2 protocol and the current implementation experience. |
|
| |
| RFC 1388 | RIP Version 2 Carrying Additional Information |
| |
| Authors: | G. Malkin. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1723 |
| Updates: | RFC 1058 |
| Status: | PROPOSED STANDARD |
|
This document specifies an extension of the Routing InformationProtocol (RIP), as defined in [1], to expand the amount of useful information carried in RIP packets and to add a measure of security.A companion document will define the SNMP MIB objects for RIP-2 [2]. |
|
| |
| RFC 1389 | RIP Version 2 MIB Extensions |
| |
| Authors: | G. Malkin, F. Baker. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1724 |
| Status: | PROPOSED STANDARD |
|
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 RIP Version 2. |
|
| |
| RFC 1391 | The Tao of the IETF: A Guide for New Attendees of the Internet Engineering Task Force |
| |
| Authors: | G. Malkin. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1539 |
| Status: | INFORMATIONAL |
|
Over the last two years, the attendance at Internet Engineering TaskForce (IETF) Plenary meetings has grown phenomenally. Approximately38% of the attendees are new to the IETF at each meeting. About 33% of those go on to become regular attendees. When the meetings were smaller, it wasn't very difficult for a newcomer to get to know people and get into the swing of things. Today, however, a newcomer meets many more new people, some previously known only as the authors of Request For Comments (RFC) documents or thought provoking email messages.
The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This will give them a warm, fuzzy feeling and enable them to make the meeting more productive for everyone. This FYI will also provide the mundane bits of information which everyone who attends an IETF meeting should know. |
|
| |
| RFC 1392 | Internet Users' Glossary |
| |
| Authors: | G. Malkin, T. LaQuey Parker. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1983 |
| Status: | INFORMATIONAL |
|
There are many networking glossaries in existence. This glossary concentrates on terms which are specific to the Internet. Naturally, there are entries for some basic terms and acronyms because other entries refer to them. |
|
| |
| RFC 1395 | BOOTP Vendor Information Extensions |
| |
|
|
This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo. This memo will be updated as additional tags are defined. This edition introduces Tag 14 for Merit Dump File, Tag 15 for Domain Name, Tag 16 for Swap Server and Tag 17 for Root Path. This memo is a status report on the vendor information extensions used int the Bootstrap Protocol (BOOTP). |
|
| |
| RFC 1398 | Definitions of Managed Objects for the Ethernet-Like Interface Types |
| |
| Authors: | F. Kastenholz. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1284 |
| Obsoleted by: | RFC 1623 |
| Status: | DRAFT STANDARD |
|
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. |
|
| |
| RFC 1404 | A Model for Common Operational Statistics |
| |
| Authors: | B. Stockman. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1857 |
| Status: | INFORMATIONAL |
|
This memo describes a model for operational statistics in theInternet. It gives recommendations for metrics, measurements, polling periods, storage formats and presentation formats. |
|
| |
| RFC 1405 | Mapping between X.400(1984/1988) and Mail-11 (DECnet mail) |
| |
| Authors: | C. Allocchio. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2162 |
| Status: | EXPERIMENTAL |
|
This document describes a set of mappings which will enable inter working between systems operating the CCITT X.400 ( 1984 / 1988 )Recommendations on Message Handling Systems, and systems running theMail-11 (also known as DECnet mail) protocol. The specifications are valid within DECnet Phase IV addressing and routing scheme.
The complete scenario of X.400 / RFC822 / Mail-11 is also considered, in order to cover the possible complex cases arising in multiple gateway translations.
This document covers mainly the O/R address to DECnet from/to address mapping (and vice versa); other mappings are based on RFC 1327 and its eventual future updates.
This is a combined effort of COSINE S2.2, the RARE MSG Working Group, and the IETF X.400 Ops Working Group. |
|
| |
| RFC 1406 | Definitions of Managed Objects for the DS1 and E1 Interface Types |
| |
| Authors: | F. Baker, J. Watt, Eds.. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1232 |
| Obsoleted by: | RFC 2495 |
| Status: | PROPOSED STANDARD |
|
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 DS1 Interfaces -- including both T1 and E1 (a.k.a., CEPT 2 Mbit/s) links.
This document entirely replaces RFC 1232, which contains a fundamental error: many objects are encoded as Counters that must be encoded as INTEGERs or Gauges. The magnitude of the change required is sufficient that virtually every object changed. Therefore, theMIB documented in RFC 1232 should not be implemented. |
|
| |
| RFC 1407 | Definitions of Managed Objects for the DS3/E3 Interface Type |
| |
| Authors: | T. Cox, K. Tesink. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1233 |
| Obsoleted by: | RFC 2496 |
| Status: | PROPOSED STANDARD |
|
This memo defines an extension to the Management Information Base(MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing DS3 and E3Interfaces. This document is a companion document with Definitions of Managed Objects for the DS1 Interface Type.
This document entirely replaces RFC 1233, which contains a fundamental error: many objects are encoded as Counters that must be encoded as INTEGERs or Gauges. The magnitude of the change required is sufficient that virtually every object changed. Therefore, theMIB documented in RFC 1233 should not be implemented. |
|
| |
| RFC 1409 | Telnet Authentication Option |
| |
| Authors: | D. Borman, Ed.. |
| Date: | January 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1416 |
| Status: | EXPERIMENTAL |
|
This memo defines an Experimental Protocol for the Internet community. |
|
| |
| 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 |
|
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). |
|
| |
| RFC 1416 | Telnet Authentication Option |
| |
| Authors: | D. Borman, Ed.. |
| Date: | February 1993 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1409 |
| Obsoleted by: | RFC 2941 |
| Status: | EXPERIMENTAL |
|
This RFC 1416 replaces RFC 1409, which has an important typographical error in the example on page 6 (one occurance of "REPLY" should be "IS"). This memo defines an Experimental Protocol for the Internet community. |
|
| |
| RFC 1417 | NADF Standing Documents: A Brief Overview |
| |
|
|
The purpose of this document is to provide a brief overview of the NADF's Standing Document series. This memo provides information for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1425 | SMTP Service Extensions |
| |
| Authors: | J. Klensin, WG Chair, N. Freed, Ed., M. Rose, E. Stefferud, D. Crocker. |
| Date: | February 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1651 |
| Status: | PROPOSED STANDARD |
|
This memo defines a framework for extending the SMTP service by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports. [STANDARDS-TRACK] |
|
| |
| RFC 1426 | SMTP Service Extension for 8bit-MIMEtransport |
| |
| Authors: | J. Klensin, WG Chair, N. Freed, Ed., M. Rose, E. Stefferud, D. Crocker. |
| Date: | February 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1652 |
| Status: | PROPOSED STANDARD |
|
This memo defines an extension to the SMTP service whereby an SMTP content body containing octets outside of the US ASCII octet range (hex |
|
| |
| RFC 1427 | SMTP Service Extension for Message Size Declaration |
| |
| Authors: | J. Klensin, WG Chair, N. Freed, Ed., K. Moore. |
| Date: | February 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1653 |
| Status: | PROPOSED STANDARD |
|
This memo defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to decline to accept a message (perhaps temporarily) based on the client's estimate of the message size. [STANDARDS-TRACK] |
|
| |
| RFC 1434 | Data Link Switching: Switch-to-Switch Protocol |
| |
| Authors: | R. Dixon, D. Kushi. |
| Date: | March 1993 |
| Formats: | txt pdf ps |
| Obsoleted by: | RFC 1795 |
| Status: | INFORMATIONAL |
|
This RFC describes IBM's support of Data Link Switching over TCP/IP.The RFC is being distributed to members of the Internet community in order to solicit their reactions to the proposals contained in it.While the issues discussed may not be directly relevant to the research problems of the Internet, they may be interesting to a number of researchers and implementors.
Any questions or comments relative to the contents of this RFC should be sent to the following Internet address: dlsw@ralvma.vnet.ibm.com. |
|
| |
| RFC 1442 | Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2) |
| |
| Authors: | J. Case, K. McCloghrie, M. Rose, S. Waldbusser. |
| Date: | April 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1902 |
| Status: | PROPOSED STANDARD |
|
Management information is viewed as a collection of managed objects, residing in a virtual information store, termed the Management Information Base (MIB). Collections of related objects are defined in MIB modules. These modules are written using a subset of OSI's Abstract Syntax Notation One (ASN.1) [1]. It is the purpose of this document, the Structure of Management Information (SMI), to define that subset. [STANDARDS-TRACK] |
|
| |
| RFC 1443 | Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2) |
| |
| Authors: | J. Case, K. McCloghrie, M. Rose, S. Waldbusser. |
| Date: | April 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1903 |
| Status: | PROPOSED STANDARD |
|
It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK] |
|
| |
| RFC 1444 | Conformance Statements for version 2 of the Simple Network Management Protocol (SNMPv2) |
| |
| Authors: | J. Case, K. McCloghrie, M. Rose, S. Waldbusser. |
| Date: | April 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1904 |
| Status: | PROPOSED STANDARD |
|
It may be useful to define the acceptable lower-bounds of implementation, along with the actual level of implementation achieved. It is the purpose of this document to define the notation used for these purposes. [STANDARDS-TRACK] |
|
| |
| RFC 1448 | Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2) |
| |
| Authors: | J. Case, K. McCloghrie, M. Rose, S. Waldbusser. |
| Date: | April 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1905 |
| Status: | PROPOSED STANDARD |
|
It is the purpose of this document, Protocol Operations for SNMPv2, to define the operations of the protocol with respect to the sending and receiving of the PDUs. [STANDARDS-TRACK] |
|
| |
| RFC 1449 | Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2) |
| |
| Authors: | J. Case, K. McCloghrie, M. Rose, S. Waldbusser. |
| Date: | April 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1906 |
| Status: | PROPOSED STANDARD |
|
It is the purpose of this document to define how the SNMPv2 maps onto an initial set of transport domains. [STANDARDS-TRACK] |
|
| |
| RFC 1450 | Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2) |
| |
| Authors: | J. Case, K. McCloghrie, M. Rose, S. Waldbusser. |
| Date: | April 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1907 |
| Status: | PROPOSED STANDARD |
|
It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity. [STANDARDS-TRACK] |
|
| |
| RFC 1452 | Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework |
| |
| Authors: | J. Case, K. McCloghrie, M. Rose, S. Waldbusser. |
| Date: | April 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1908 |
| Status: | PROPOSED STANDARD |
|
The purpose of this document is to describe coexistence between version 2 of the Internet-standard Network Management Framework, termed the SNMP version 2 framework (SNMPv2) [1], and the original Internet-standard Network Management Framework (SNMPv1). [STANDARDS-TRACK] |
|
| |
| RFC 1455 | Physical Link Security Type of Service |
| |
| Authors: | D. Eastlake 3rd. |
| Date: | May 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2474 |
| Status: | EXPERIMENTAL |
|
This RFC documents an experimental protocol providing a Type ofService (TOS) to request maximum physical link security. This is an addition to the types of service enumerated in RFC 1349: Type ofService in the Internet Protocol Suite. The new TOS requests the network to provide what protection it can against surreptitious observation by outside agents of traffic so labeled. The purpose is protection against traffic analysis and as an additional possible level of data confidentiality. This TOS is consistent with all other defined types of service for IP version 4 in that it is based on link level characteristics and will not provide any particular guaranteed level of service. |
|
| |
| RFC 1460 | Post Office Protocol - Version 3 |
| |
| Authors: | M. Rose. |
| Date: | June 1993 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1225 |
| Obsoleted by: | RFC 1725 |
| Status: | DRAFT STANDARD |
|
This memo is a revision to RFC 1225, a Draft Standard. [STANDARDS- TRACK] |
|
| |
| RFC 1466 | Guidelines for Management of IP Address Space |
| |
| Authors: | E. Gerich. |
| Date: | May 1993 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1366 |
| Obsoleted by: | RFC 2050 |
| Status: | INFORMATIONAL |
|
This document has been reviewed by the Federal Engineering PlanningGroup (FEPG) on behalf of the Federal Networking Council (FNC), the co-chairs of the Intercontinental Engineering Planning Group (IEPG), and the Reseaux IP Europeens (RIPE). There was general consensus by those groups to support the recommendations proposed in this document for management of the IP address space. |
|
| |
| RFC 1483 | Multiprotocol Encapsulation over ATM Adaptation Layer 5 |
| |
| Authors: | Juha Heinanen. |
| Date: | July 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2684 |
| Status: | PROPOSED STANDARD |
|
This memo describes two encapsulations methods for carrying network interconnect traffic over ATM AAL5. The first method allows multiplexing of multiple protocols over a single ATM virtual circuit whereas the second method assumes that each protocol is carried over a separate ATM virtual circuit. |
|
| |
| RFC 1484 | Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2)) |
| |
|
|
The OSI Directory has user friendly naming as a goal. A simple minded usage of the directory does not achieve this. Two aspects not achieved are: o A user oriented notation o Guessability
This proposal sets out some conventions for representing names in a friendly manner, and shows how this can be used to achieve really friendly naming. This then leads to a specification of a format for representing names, and to procedures to resolve them. This leads to a specification which allows directory names to be communicated between humans. The format in this specification is identical to that defined in [HK93], and it is intended that these specifications are compatible. Please send comments to the author or to the discussion group: <osi-ds@CS.UCL.AC.UK&rt;. |
|
| |
| RFC 1485 | A String Representation of Distinguished Names (OSI-DS 23 (v5)) |
| |
|
|
The OSI Directory uses distinguished names as the primary keys to entries in the directory. Distinguished Names are encoded in ASN.1.When a distinguished name is communicated between to users not using a directory protocol (e.g., in a mail message), there is a need to have a user-oriented string representation of distinguished name. This specification defines a string format for representing names, which is designed to give a clean representation of commonly used names, whilst being able to represent any distinguished name. Please send comments to the author or to the discussion group <osi-ds@CS.UCL.AC.UK&rt;. |
|
| |
| RFC 1486 | An Experiment in Remote Printing |
| |
| Authors: | M. Rose, C. Malamud. |
| Date: | July 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1528, RFC 1529 |
| Status: | EXPERIMENTAL |
|
This memo describes a technique for "remote printing" using the Internet mail infrastructure. In particular, this memo focuses on the case in which remote printers are connected to the international telephone network. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1487 | X.500 Lightweight Directory Access Protocol |
| |
| Authors: | W. Yeong, T. Howes, S. Kille. |
| Date: | July 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1777, RFC 3494 |
| Status: | HISTORIC |
|
The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of theDirectory Access Protocol (DAP). This protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive access to the Directory, and is intended to be a complement to the DAP itself.
Key aspects of LDAP are:
- Protocol elements are carried directly over TCP or other transport, bypassing much of the session/presentation overhead.
- Many protocol data elements are encoding as ordinary strings (e.g.,Distinguished Names).
- A lightweight BER encoding is used to encode all protocol elements. |
|
| |
| RFC 1488 | The X.500 String Representation of Standard Attribute Syntaxes |
| |
| Authors: | T. Howes, S. Kille, W. Yeong, C. Robbins. |
| Date: | July 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 1778 |
| Status: | PROPOSED STANDARD |
|
The Lightweight Directory Access Protocol (LDAP) [9] requires that the contents of AttributeValue fields in protocol elements be octet strings. This document defines the requirements that must be satisfied by encoding rules used to render Directory attribute syntaxes into a form suitable for use in the LDAP, then goes on to define the encoding rules for the standard set of attribute syntaxes defined in [1,2] and [3]. |
|
| |
| RFC 1490 | Multiprotocol Interconnect over Frame Relay |
| |
| Authors: | T. Bradley, C. Brown, A. Malis. |
| Date: | July 1993 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1294 |
| Obsoleted by: | RFC 2427 |
| Status: | DRAFT STANDARD |
|
This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. Additionally, it describes a simple fragmentation procedure for carrying large frames over a frame relay network with a smaller MTU.
Systems with the ability to transfer both the encapsulation method described in this document, and others must have a priori knowledge of which virtual circuits will carry which encapsulation method and this encapsulation must only be used over virtual circuits that have been explicitly configured for its use. |
|
| |
| RFC 1493 | Definitions of Managed Objects for Bridges |
| |
| Authors: | E. Decker, P. Langille, A. Rijsinghani, K. McCloghrie. |
| Date: | July 1993 |
| Formats: | txt pdf |
| Obsoletes: | RFC 1286 |
| Obsoleted by: | RFC 4188 |
| Status: | DRAFT STANDARD |
|
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 MAC bridges based on the IEEE 802.1D-1990 standard between Local Area Network (LAN) segments. Provisions are made for support of transparent bridging.Provisions are also made so that these objects apply to bridges connected by subnetworks other than LAN segments. |
|
| |
| RFC 1495 | Mapping between X.400 and RFC-822 Message Bodies |
| |
| Authors: | H. Alvestrand, S. Kille, R. Miles, M. Rose, S. Thompson. |
| Date: | August 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2156 |
| Updates: | RFC 1327 |
| Status: | PROPOSED STANDARD |
|
Since the introduction of X.400(84), there has been work ongoing for defining mappings between MHS and RFC-822. The most recent work in this area is RFC-1327 [3], which focuses primarily on translation of envelope and headers. This document is complimentary to RFC-1327 as it focuses on translation of the message body. [STANDARDS-TRACK] |
|
| |
| RFC 1497 | BOOTP Vendor Information Extensions |
| |
|
|
This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo. This memo is a status report on the vendor information extensions used in the Bootstrap Protocol (BOOTP). |
|
| |
| RFC 1500 | Internet Official Protocol Standards |
| |
|
|
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). [STANDARDS-TRACK] |
|
| |
| RFC 1508 | Generic Security Service Application Program Interface |
| |
| Authors: | J. Linn. |
| Date: | September 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2078 |
| Status: | PROPOSED STANDARD |
|
This Generic Security Service Application Program Interface (GSS-API) definition provides security services to callers in a generic fashion, supportable with a range of underlying mechanisms and technologies and hence allowing source-level portability of applications to different environments. This specification definesGSS-API services and primitives at a level independent of underlying mechanism and programming language environment, and is to be complemented by other, related specifications: documents defining specific parameter bindings for particular language environments documents defining token formats, protocols, and procedures to be implemented in order to realize GSS-API services atop particular security mechanisms |
|
| |
| RFC 1509 | Generic Security Service API : C-bindings |
| |
| Authors: | J. Wray. |
| Date: | September 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2744 |
| Status: | PROPOSED STANDARD |
|
This document specifies C language bindings for the Generic SecurityService Application Program Interface (GSS-API), which is described at a language-independent conceptual level in other documents.
The Generic Security Service Application Programming Interface (GSS-API) provides security services to its callers, and is intended for implementation atop alternative underlying cryptographic mechanisms.Typically, GSS-API callers will be application protocols into which security enhancements are integrated through invocation of services provided by the GSS-API. The GSS-API allows a caller application to authenticate a principal identity associated with a peer application, to delegate rights to a peer, and to apply security services such as confidentiality and integrity on a per-message basis. |
|
| |
| RFC 1510 | The Kerberos Network Authentication Service (V5) |
| |
| Authors: | J. Kohl, C. Neuman. |
| Date: | September 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 4120 |
| Status: | PROPOSED STANDARD |
|
This document gives an overview and specification of Version 5 of the protocol for the Kerberos network authentication system. Version 4, described elsewhere [1,2], is presently in production use at MIT'sProject Athena, and at other Internet sites. |
|
| |
| RFC 1514 | Host Resources MIB |
| |
| Authors: | P. Grillo, S. Waldbusser. |
| Date: | September 1993 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 2790 |
| Status: | PROPOSED STANDARD |
|
This memo defines a MIB for use with managing host systems. The term"host" is construed to mean any computer that communicates with other similar computers attached to the internet and that is directly used by one or more human beings. Although this MIB does not necessarily apply to devices whose primary function is communications services(e.g., terminal servers, routers, bridges, monitoring equipment), such relevance is not explicitly precluded. This MIB instruments attributes common to all internet hosts including, for example, both personal computers and systems that run variants | |
