| |
| RFC 1 | Host Software |
| |
|
| |
| RFC 2 | Host software |
| |
|
| |
| RFC 3 | Documentation conventions |
| |
|
| |
| RFC 4 | Network timetable |
| |
| Authors: | E.B. Shapiro. |
| Date: | March 1969 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0004 |
|
|
|
| |
| RFC 5 | Decode Encode Language (DEL) |
| |
|
| |
| RFC 6 | Conversation with Bob Kahn |
| |
| Authors: | S.D. Crocker. |
| Date: | April 1969 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0006 |
|
|
|
| |
| RFC 7 | Host-IMP interface |
| |
|
| |
| RFC 8 | ARPA Network Functional Specifications |
| |
| Authors: | G. Deloche. |
| Date: | May 1969 |
| Formats: | pdf json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0008 |
|
|
|
| |
| RFC 9 | Host Software |
| |
| Authors: | G. Deloche. |
| Date: | May 1969 |
| Formats: | pdf json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0009 |
|
|
|
| |
| RFC 10 | Documentation conventions |
| |
|
| |
| RFC 11 | Implementation of the Host - Host Software Procedures in GORDO |
| |
|
| |
| RFC 12 | IMP-Host interface flow diagrams |
| |
|
| |
| RFC 13 | Zero Text Length EOF Message |
| |
|
| |
| RFC 15 | Network subsystem for time sharing hosts |
| |
| Authors: | C.S. Carr. |
| Date: | September 1969 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0015 |
|
|
|
| |
| RFC 16 | M.I.T |
| |
|
| |
| RFC 17 | Some questions re: Host-IMP Protocol |
| |
| Authors: | J.E. Kreznar. |
| Date: | August 1969 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0017 |
|
|
|
| |
| RFC 18 | IMP-IMP and HOST-HOST Control Links |
| |
| Authors: | V. Cerf. |
| Date: | September 1969 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0018 |
|
|
|
| |
| RFC 19 | Two protocol suggestions to reduce congestion at swap bound nodes |
| |
| Authors: | J.E. Kreznar. |
| Date: | October 1969 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0019 |
|
|
|
| |
| RFC 21 | Network meeting |
| |
| Authors: | V.G. Cerf. |
| Date: | October 1969 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0021 |
|
|
|
| |
| RFC 22 | Host-host control message formats |
| |
| Authors: | V.G. Cerf. |
| Date: | October 1969 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0022 |
|
|
|
| |
| RFC 23 | Transmission of Multiple Control Messages |
| |
|
| |
| RFC 24 | Documentation Conventions |
| |
|
| |
| RFC 25 | No High Link Numbers |
| |
| Authors: | S.D. Crocker. |
| Date: | October 1969 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0025 |
|
|
|
| |
| RFC 27 | Documentation Conventions |
| |
|
| |
| RFC 28 | Time Standards |
| |
| Authors: | W.K. English. |
| Date: | January 1970 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0028 |
|
|
|
| |
| RFC 29 | Response to RFC 28 |
| |
|
| |
| RFC 30 | Documentation Conventions |
| |
|
| |
| RFC 31 | Binary Message Forms in Computer |
| |
| Authors: | D. Bobrow, W.R. Sutherland. |
| Date: | February 1968 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0031 |
|
|
|
| |
| RFC 32 | Some Thoughts on SRI's Proposed Real Time Clock |
| |
|
| |
| RFC 33 | New Host-Host Protocol |
| |
|
| |
| RFC 34 | Some Brief Preliminary Notes on the Augmentation Research Center Clock |
| |
| Authors: | W.K. English. |
| Date: | February 1970 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0034 |
|
|
|
| |
| RFC 36 | Protocol Notes |
| |
|
| |
| RFC 37 | Network Meeting Epilogue, etc |
| |
| Authors: | S.D. Crocker. |
| Date: | March 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0037 |
|
|
|
| |
| RFC 38 | Comments on Network Protocol from NWG/RFC #36 |
| |
|
| |
| RFC 39 | Comments on Protocol Re: NWG/RFC #36 |
| |
|
| |
| RFC 40 | More Comments on the Forthcoming Protocol |
| |
| Authors: | E. Harslem, J.F. Heafner. |
| Date: | March 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0040 |
|
|
|
| |
| RFC 41 | IMP-IMP Teletype Communication |
| |
| Authors: | J.T. Melvin. |
| Date: | March 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0041 |
|
|
|
| |
| RFC 42 | Message Data Types |
| |
|
| |
| RFC 43 | Proposed Meeting |
| |
| Authors: | A.G. Nemeth. |
| Date: | April 1970 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0043 |
|
|
|
| |
| RFC 44 | Comments on NWG/RFC 33 and 36 |
| |
| Authors: | A. Shoshani, R. Long, A. Landsberg. |
| Date: | April 1970 |
| Formats: | txt html json |
| Updates: | RFC 0036 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0044 |
|
|
|
| |
| RFC 45 | New Protocol is Coming |
| |
| Authors: | J. Postel, S.D. Crocker. |
| Date: | April 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0045 |
|
|
|
| |
| RFC 46 | ARPA Network protocol notes |
| |
|
| |
| RFC 47 | BBN's Comments on NWG/RFC #33 |
| |
|
| |
| RFC 48 | Possible protocol plateau |
| |
| Authors: | J. Postel, S.D. Crocker. |
| Date: | April 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0048 |
|
|
|
| |
| RFC 49 | Conversations with S. Crocker (UCLA) |
| |
| Authors: | Crocker (UCLA). E. Meyer. |
| Date: | April 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0049 |
|
|
|
| |
| RFC 50 | Comments on the Meyer Proposal |
| |
| Authors: | E. Harslen, J. Heafner. |
| Date: | April 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0050 |
|
|
|
| |
| RFC 51 | Proposal for a Network Interchange Language |
| |
| Authors: | M. Elie. |
| Date: | May 1970 |
| Formats: | pdf json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0051 |
|
|
|
| |
| RFC 52 | Updated distribution list |
| |
|
| |
| RFC 53 | Official protocol mechanism |
| |
| Authors: | S.D. Crocker. |
| Date: | June 1970 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0053 |
|
|
|
| |
| RFC 54 | Official Protocol Proffering |
| |
| Authors: | S.D. Crocker, J. Postel, J. Newkirk, M. Kraley. |
| Date: | June 1970 |
| Formats: | txt html json |
| Updated by: | RFC 0057 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0054 |
|
|
|
| |
| RFC 55 | Prototypical implementation of the NCP |
| |
| Authors: | J. Newkirk, M. Kraley, J. Postel, S.D. Crocker. |
| Date: | June 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0055 |
|
|
|
| |
| RFC 56 | Third Level Protocol: Logger Protocol |
| |
| Authors: | E. Belove, D. Black, R. Flegal, L.G. Farquar. |
| Date: | June 1970 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0056 |
|
|
|
| |
| RFC 57 | Thoughts and Reflections on NWG/RFC 54 |
| |
|
| |
| RFC 58 | Logical Message Synchronization |
| |
| Authors: | T.P. Skinner. |
| Date: | June 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0058 |
|
|
|
| |
| RFC 59 | Flow Control - Fixed Versus Demand Allocation |
| |
|
| |
| RFC 60 | A Simplified NCP Protocol |
| |
|
|
This RFC defines a new NCP protocol that is simple enough to be implemented on a very small computer, yet can be extended for efficient operation on large timesharing machines. Because worst case storage requirements can be predicted, a conservative implementation can be freed of complicated resource allocation and storage control procedures. A general error recovery procedure is also defined. |
|
| |
| RFC 61 | Note on Interprocess Communication in a Resource Sharing Computer Network |
| |
|
| |
| RFC 62 | Systems for Interprocess Communication in a Resource Sharing Computer Network |
| |
|
| |
| RFC 63 | Belated Network Meeting Report |
| |
|
| |
| RFC 64 | Getting rid of marking |
| |
|
| |
| RFC 65 | Comments on Host/Host Protocol document #1 |
| |
| Authors: | D.C. Walden. |
| Date: | August 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0065 |
|
|
|
| |
| RFC 66 | NIC - third level ideas and other noise |
| |
|
| |
| RFC 67 | Proposed Change to Host/IMP Spec to Eliminate Marking |
| |
| Authors: | W.R. Crowther. |
| Date: | January 1970 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0067 |
|
|
|
| |
| RFC 68 | Comments on Memory Allocation Control Commands: CEASE, ALL, GVB, RET, and RFNM |
| |
|
| |
| RFC 69 | Distribution List Change for MIT |
| |
|
| |
| RFC 70 | Note on Padding |
| |
|
| |
| RFC 71 | Reallocation in Case of Input Error |
| |
| Authors: | T. Schipper. |
| Date: | September 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0071 |
|
|
|
| |
| RFC 72 | Proposed Moratorium on Changes to Network Protocol |
| |
| Authors: | R.D. Bressler. |
| Date: | September 1970 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0072 |
|
|
|
| |
| RFC 73 | Response to NWG/RFC 67 |
| |
| Authors: | S.D. Crocker. |
| Date: | September 1970 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0073 |
|
|
|
| |
| RFC 74 | Specifications for Network Use of the UCSB On-Line System |
| |
|
| |
| RFC 75 | Network Meeting |
| |
| Authors: | S.D. Crocker. |
| Date: | October 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0075 |
|
|
|
| |
| RFC 76 | Connection by name: User oriented protocol |
| |
| Authors: | J. Bouknight, J. Madden, G.R. Grossman. |
| Date: | October 1970 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0076 |
|
|
|
| |
| RFC 77 | Network meeting report |
| |
| Authors: | J. Postel. |
| Date: | November 1970 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0077 |
|
|
|
| |
| RFC 78 | NCP Status Report: UCSB/Rand |
| |
| Authors: | E. Harslem, J.F. Heafner, J.E. White. |
| Date: | October 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0078 |
|
|
|
| |
| RFC 79 | Logger Protocol error |
| |
| Authors: | E. Meyer. |
| Date: | November 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0079 |
|
|
|
| |
| RFC 80 | Protocols and Data Formats |
| |
|
| |
| RFC 81 | Request for Reference Information |
| |
| Authors: | J. Bouknight. |
| Date: | December 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0081 |
|
|
|
| |
| RFC 82 | Network Meeting Notes |
| |
| Authors: | E. Meyer. |
| Date: | December 1970 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0082 |
|
|
|
| |
| RFC 83 | Language-machine for data reconfiguration |
| |
| Authors: | R.H. Anderson, E. Harslem, J.F. Heafner. |
| Date: | December 1970 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0083 |
|
|
|
| |
| RFC 84 | List of NWG/RFC's 1-80 |
| |
| Authors: | J.B. North. |
| Date: | December 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0084 |
|
|
|
| |
| RFC 85 | Network Working Group meeting |
| |
| Authors: | S.D. Crocker. |
| Date: | December 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0085 |
|
|
|
| |
| RFC 86 | Proposal for a Network Standard Format for a Data Stream to Control Graphics Display |
| |
|
| |
| RFC 87 | Topic for Discussion at the Next Network Working Group Meeting |
| |
|
| |
| RFC 88 | NETRJS: A third level protocol for Remote Job Entry |
| |
|
| |
| RFC 89 | Some historic moments in networking |
| |
| Authors: | R.M. Metcalfe. |
| Date: | January 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0089 |
|
|
|
| |
| RFC 90 | CCN as a Network Service Center |
| |
| Authors: | R.T. Braden. |
| Date: | January 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0090 |
|
|
|
| |
| RFC 91 | Proposed User-User Protocol |
| |
| Authors: | G.H. Mealy. |
| Date: | December 1970 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0091 |
|
|
|
| |
| RFC 93 | Initial Connection Protocol |
| |
|
| |
| RFC 94 | Some thoughts on Network Graphics |
| |
| Authors: | E. Harslem, J.F. Heafner. |
| Date: | February 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0094 |
|
|
|
| |
| RFC 95 | Distribution of NWG/RFC's through the NIC |
| |
|
| |
| RFC 97 | First Cut at a Proposed Telnet Protocol |
| |
| Authors: | J.T. Melvin, R.W. Watson. |
| Date: | February 1971 |
| Formats: | txt json html pdf |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0097 |
|
|
|
| |
| RFC 98 | Logger Protocol Proposal |
| |
|
| |
| RFC 99 | Network Meeting |
| |
|
| |
| RFC 100 | Categorization and guide to NWG/RFCs |
| |
| Authors: | P.M. Karp. |
| Date: | February 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0100 |
|
|
|
| |
| RFC 101 | Notes on the Network Working Group meeting, Urbana, Illinois, February 17, 1971 |
| |
|
| |
| RFC 102 | Output of the Host-Host Protocol glitch cleaning committee |
| |
|
| |
| RFC 103 | Implementation of Interrupt Keys |
| |
| Authors: | R.B. Kalin. |
| Date: | February 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0103 |
|
|
|
| |
| RFC 104 | Link 191 |
| |
| Authors: | J.B. Postel, S.D. Crocker. |
| Date: | February 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0104 |
|
|
|
| |
| RFC 105 | Network Specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB |
| |
|
| |
| RFC 106 | User/Server Site Protocol Network Host Questionnaire |
| |
| Authors: | T.C. O'Sullivan. |
| Date: | March 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0106 |
|
|
|
| |
| RFC 107 | Output of the Host-Host Protocol Glitch Cleaning Committee |
| |
|
| |
| RFC 108 | Attendance list at the Urbana NWG meeting, February 17-19, 1971 |
| |
|
| |
| RFC 109 | Level III Server Protocol for the Lincoln Laboratory 360/67 Host |
| |
|
| |
| RFC 110 | Conventions for Using an IBM 2741 Terminal as a User Console for Access to Network Server Hosts |
| |
|
| |
| RFC 111 | Pressure from the Chairman |
| |
|
| |
| RFC 112 | User/Server Site Protocol: Network Host Questionnaire |
| |
|
| |
| RFC 113 | Network activity report: UCSB Rand |
| |
| Authors: | E. Harslem, J.F. Heafner, J.E. White. |
| Date: | April 1971 |
| Formats: | txt html json |
| Updated by: | RFC 0227 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0113 |
|
|
|
| |
| RFC 114 | File Transfer Protocol |
| |
|
| |
| RFC 115 | Some Network Information Center policies on handling documents |
| |
| Authors: | R.W. Watson, J.B. North. |
| Date: | April 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0115 |
|
|
|
| |
| RFC 116 | Structure of the May NWG Meeting |
| |
|
| |
| RFC 117 | Some comments on the official protocol |
| |
|
| |
| RFC 118 | Recommendations for facility documentation |
| |
| Authors: | R.W. Watson. |
| Date: | April 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0118 |
|
|
|
| |
| RFC 119 | Network Fortran Subprograms |
| |
|
| |
| RFC 120 | Network PL1 subprograms |
| |
| Authors: | M. Krilanovich. |
| Date: | April 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0120 |
|
|
|
| |
| RFC 121 | Network on-line operators |
| |
| Authors: | M. Krilanovich. |
| Date: | April 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0121 |
|
|
|
| |
| RFC 122 | Network specifications for UCSB's Simple-Minded File System |
| |
|
| |
| RFC 123 | Proffered Official ICP |
| |
|
| |
| RFC 124 | Typographical error in RFC 107 |
| |
|
| |
| RFC 125 | Response to RFC 86: Proposal for Network Standard Format for a Graphics Data Stream |
| |
|
| |
| RFC 126 | Graphics Facilities at Ames Research Center |
| |
| Authors: | J. McConnell. |
| Date: | April 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0126 |
|
|
|
| |
| RFC 127 | Comments on RFC 123 |
| |
|
| |
| RFC 128 | Bytes |
| |
|
| |
| RFC 129 | Request for comments on socket name structure |
| |
| Authors: | E. Harslem, J. Heafner, E. Meyer. |
| Date: | April 1971 |
| Formats: | txt json html |
| Updated by: | RFC 0147 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0129 |
|
|
|
| |
| RFC 130 | Response to RFC 111: Pressure from the chairman |
| |
|
| |
| RFC 131 | Response to RFC 116: May NWG meeting |
| |
|
| |
| RFC 132 | Typographical Error in RFC 107 |
| |
|
| |
| RFC 133 | File Transfer and Error Recovery |
| |
|
| |
| RFC 134 | Network Graphics meeting |
| |
|
| |
| RFC 135 | Response to NWG/RFC 110 |
| |
|
| |
| RFC 136 | Host accounting and administrative procedures |
| |
|
| |
| RFC 137 | Telnet Protocol - a proposed document |
| |
|
| |
| RFC 138 | Status report on proposed Data Reconfiguration Service |
| |
| Authors: | R.H. Anderson, V.G. Cerf, E. Harslem, J.F. Heafner, J. Madden, R.M. Metcalfe, A. Shoshani, J.E. White, D.C.M. Wood. |
| Date: | April 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0138 |
|
|
|
| |
| RFC 139 | Discussion of Telnet Protocol |
| |
|
| |
| RFC 140 | Agenda for the May NWG meeting |
| |
|
| |
| RFC 141 | Comments on RFC 114: A File Transfer Protocol |
| |
|
| |
| RFC 142 | Time-Out Mechanism in the Host-Host Protocol |
| |
| Authors: | C. Kline, J. Wong. |
| Date: | May 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0142 |
|
|
|
| |
| RFC 143 | Regarding proffered official ICP |
| |
|
| |
| RFC 144 | Data sharing on computer networks |
| |
| Authors: | A. Shoshani. |
| Date: | April 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0144 |
|
|
|
| |
| RFC 145 | Initial Connection Protocol Control Commands |
| |
|
| |
| RFC 146 | Views on issues relevant to data sharing on computer networks |
| |
| Authors: | P.M. Karp, D.B. McKay, D.C.M. Wood. |
| Date: | May 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0146 |
|
|
|
| |
| RFC 147 | Definition of a socket |
| |
|
| |
| RFC 148 | Comments on RFC 123 |
| |
|
| |
| RFC 149 | Best Laid Plans |
| |
|
| |
| RFC 150 | Use of IPC Facilities: A Working Paper |
| |
|
| |
| RFC 151 | Comments on a proffered official ICP: RFCs 123, 127 |
| |
|
| |
| RFC 152 | SRI Artificial Intelligence status report |
| |
|
| |
| RFC 153 | SRI ARC-NIC status |
| |
| Authors: | J.T. Melvin, R.W. Watson. |
| Date: | May 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0153 |
|
|
|
| |
| RFC 154 | Exposition Style |
| |
|
| |
| RFC 155 | ARPA Network mailing lists |
| |
|
| |
| RFC 156 | Status of the Illinois site: Response to RFC 116 |
| |
|
| |
| RFC 157 | Invitation to the Second Symposium on Problems in the Optimization of Data Communications Systems |
| |
|
| |
| RFC 158 | Telnet Protocol: A Proposed Document |
| |
|
| |
| RFC 160 | RFC brief list |
| |
| Authors: | Network Information Center. Stanford Research Institute. |
| Date: | May 1971 |
| Formats: | txt html json |
| Obsoleted by: | RFC 0200, RFC 0999 |
| Updates: | NIC_6716 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0160 |
|
|
|
| |
| RFC 161 | Solution to the race condition in the ICP |
| |
|
| |
| RFC 162 | NETBUGGER3 |
| |
|
| |
| RFC 163 | Data transfer protocols |
| |
|
| |
| RFC 164 | Minutes of Network Working Group meeting, 5/16 through 5/19/71 |
| |
|
| |
| RFC 165 | Proffered Official Initial Connection Protocol |
| |
|
| |
| RFC 166 | Data Reconfiguration Service: An implementation specification |
| |
| Authors: | R.H. Anderson, V.G. Cerf, E. Harslem, J.F. Heafner, J. Madden, R.M. Metcalfe, A. Shoshani, J.E. White, D.C.M. Wood. |
| Date: | May 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0166 |
|
|
|
| |
| RFC 167 | Socket conventions reconsidered |
| |
|
| |
| RFC 168 | ARPA Network mailing lists |
| |
|
| |
| RFC 169 | COMPUTER NETWORKS |
| |
|
| |
| RFC 170 | RFC List by Number |
| |
| Authors: | Network Information Center. Stanford Research Institute. |
| Date: | June 1971 |
| Formats: | txt html json |
| Obsoleted by: | RFC 0200 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0170 |
|
|
|
| |
| 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 html json |
| Obsoleted by: | RFC 0264 |
| Updates: | RFC 0114 |
| Updated by: | RFC 0238 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0171 |
|
|
|
| |
| 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 json html |
| Obsoleted by: | RFC 0265 |
| Updates: | RFC 0114 |
| Updated by: | RFC 0238 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0172 |
|
|
|
| |
| RFC 173 | Network Data Management Committee Meeting Announcement |
| |
| Authors: | P.M. Karp, D.B. McKay. |
| Date: | June 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0173 |
|
|
|
| |
| RFC 174 | UCLA - Computer Science Graphics Overview |
| |
| Authors: | J. Postel, V.G. Cerf. |
| Date: | June 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0174 |
|
|
|
| |
| RFC 175 | Comments on "Socket Conventions Reconsidered" |
| |
| Authors: | E. Harslem, J.F. Heafner. |
| Date: | June 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0175 |
|
|
|
| |
| RFC 176 | Comments on "Byte size for connections" |
| |
| Authors: | A.K. Bhushan, R. Kanodia, R.M. Metcalfe, J. Postel. |
| Date: | June 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0176 |
|
|
|
| |
| RFC 177 | Device independent graphical display description |
| |
|
| |
| RFC 178 | Network graphic attention handling |
| |
|
| |
| RFC 179 | Link Number Assignments |
| |
|
| |
| RFC 180 | File system questionnaire |
| |
| Authors: | A.M. McKenzie. |
| Date: | June 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0180 |
|
|
|
| |
| RFC 181 | Modifications to RFC 177 |
| |
|
| |
| RFC 182 | Compilation of list of relevant site reports |
| |
|
| |
| RFC 183 | EBCDIC Codes and Their Mapping to ASCII |
| |
|
|
The uniquely map the ASCII codes into corresponding EBCDIC codes in a consistent manner throughout the ARPA Network, this RFC describes and defines the IBM Standard Extended BCD Interchanged Code. |
|
| |
| RFC 184 | Proposed graphic display modes |
| |
|
| |
| RFC 185 | NIC distribution of manuals and handbooks |
| |
|
| |
| RFC 186 | Network graphics loader |
| |
| Authors: | J.C. Michener. |
| Date: | July 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0186 |
|
|
|
| |
| RFC 187 | Network/440 Protocol Concept |
| |
| Authors: | D.B. McKay, D.P. Karp. |
| Date: | July 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0187 |
|
|
|
| |
| RFC 188 | Data management meeting announcement |
| |
| Authors: | P.M. Karp, D.B. McKay. |
| Date: | January 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0188 |
|
|
|
| |
| RFC 189 | Interim NETRJS specifications |
| |
|
| |
| RFC 190 | DEC PDP-10-IMLAC communications system |
| |
| Authors: | L.P. Deutsch. |
| Date: | July 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0190 |
|
|
|
| |
| RFC 191 | Graphics implementation and conceptualization at Augmentation Research Center |
| |
|
| |
| RFC 192 | Some factors which a Network Graphics Protocol must consider |
| |
|
| |
| RFC 193 | NETWORK CHECKOUT |
| |
|
| |
| RFC 194 | The Data Reconfiguration Service -- Compiler/Interpreter Implementation Notes |
| |
| Authors: | V. Cerf, E. Harslem, J. Heafner, B. Metcalfe, J. White. |
| Date: | July 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0194 |
|
|
|
| |
| RFC 195 | Data computers-data descriptions and access language |
| |
|
| |
| RFC 196 | Mail Box Protocol |
| |
|
| |
| RFC 197 | Initial Connection Protocol - Reviewed |
| |
| Authors: | A. Shoshani, E. Harslem. |
| Date: | July 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0197 |
|
|
|
| |
| RFC 198 | Site Certification - Lincoln Labs 360/67 |
| |
|
| |
| RFC 199 | Suggestions for a Network Data-Tablet Graphics Protocol |
| |
|
| |
| RFC 200 | RFC list by number |
| |
|
| |
| RFC 202 | Possible Deadlock in ICP |
| |
| Authors: | S.M. Wolfe, J. Postel. |
| Date: | July 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0202 |
|
|
|
| |
| RFC 203 | Achieving reliable communication |
| |
| Authors: | R.B. Kalin. |
| Date: | August 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0203 |
|
|
|
| |
| RFC 204 | Sockets in use |
| |
|
| |
| RFC 205 | NETCRT - a character display protocol |
| |
| Authors: | R.T. Braden. |
| Date: | August 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0205 |
|
|
|
| |
| RFC 206 | A User TELNET Description of an Initial Implementation |
| |
|
| |
| RFC 207 | September Network Working Group meeting |
| |
|
| |
| RFC 208 | Address tables |
| |
| Authors: | A.M. McKenzie. |
| Date: | August 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0208 |
|
|
|
| |
| RFC 209 | Host/IMP interface documentation |
| |
|
| |
| RFC 210 | Improvement of Flow Control |
| |
|
| |
| RFC 211 | ARPA Network Mailing Lists |
| |
|
| |
| RFC 212 | NWG meeting on network usage |
| |
| Authors: | Information Sciences Institute University of Southern California. |
| Date: | August 1971 |
| Formats: | txt json html |
| Obsoletes: | RFC 0207 |
| Updated by: | RFC 0222 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0212 |
|
|
|
| |
| RFC 213 | IMP System change notification |
| |
|
| |
| RFC 214 | Network checkpoint |
| |
|
| |
| RFC 215 | NCP, ICP, and Telnet: The Terminal IMP implementation |
| |
| Authors: | A.M. McKenzie. |
| Date: | August 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0215 |
|
|
|
| |
| RFC 216 | Telnet Access to UCSB's On-Line System |
| |
|
| |
| RFC 217 | Specifications changes for OLS, RJE/RJOR, and SMFS |
| |
|
| |
| RFC 218 | Changing the IMP status reporting facility |
| |
| Authors: | B. Cosell. |
| Date: | September 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0218 |
|
|
|
| |
| RFC 219 | User's View of the Datacomputer |
| |
| Authors: | R. Winter. |
| Date: | September 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0219 |
|
|
|
| |
| RFC 221 | Mail Box Protocol: Version 2 |
| |
|
| |
| RFC 222 | Subject: System programmer's workshop |
| |
|
| |
| RFC 223 | Network Information Center schedule for network users |
| |
| Authors: | J.T. Melvin, R.W. Watson. |
| Date: | September 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0223 |
|
|
|
| |
| RFC 224 | Comments on Mailbox Protocol |
| |
| Authors: | A.M. McKenzie. |
| Date: | September 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0224 |
|
|
|
| |
| RFC 225 | Rand/UCSB network graphics experiment |
| |
|
| |
| RFC 226 | Standardization of host mnemonics |
| |
|
| |
| RFC 227 | Data transfer rates (Rand/UCLA) |
| |
|
| |
| RFC 228 | Clarification |
| |
|
| |
| RFC 229 | Standard host names |
| |
|
| |
| RFC 230 | Toward reliable operation of minicomputer-based terminals on a TIP |
| |
| Authors: | T. Pyke. |
| Date: | September 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0230 |
|
|
|
| |
| RFC 231 | Service center standards for remote usage: A user's view |
| |
| Authors: | J.F. Heafner, E. Harslem. |
| Date: | September 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0231 |
|
|
|
| |
| RFC 232 | Postponement of network graphics meeting |
| |
| Authors: | A. Vezza. |
| Date: | September 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0232 |
|
|
|
| |
| RFC 233 | Standardization of host call letters |
| |
| Authors: | A. Bhushan, R. Metcalfe. |
| Date: | September 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0233 |
|
|
|
| |
| RFC 234 | Network Working Group meeting schedule |
| |
|
| |
| RFC 235 | Site status |
| |
|
| |
| RFC 236 | Standard host names |
| |
|
| |
| RFC 237 | NIC view of standard host names |
| |
|
| |
| RFC 238 | Comments on DTP and FTP proposals |
| |
|
| |
| RFC 239 | Host mnemonics proposed in RFC 226 (NIC 7625) |
| |
|
| |
| RFC 240 | Site Status |
| |
|
| |
| RFC 241 | Connecting computers to MLC ports |
| |
| Authors: | A.M. McKenzie. |
| Date: | September 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0241 |
|
|
|
| |
| RFC 242 | Data Descriptive Language for Shared Data |
| |
| Authors: | L. Haibt, A.P. Mullery. |
| Date: | July 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0242 |
|
|
|
| |
| RFC 243 | Network and data sharing bibliography |
| |
|
| |
| RFC 245 | Reservations for Network Group meeting |
| |
|
| |
| RFC 246 | Network Graphics meeting |
| |
|
| |
| RFC 247 | Proffered set of standard host names |
| |
|
| |
| RFC 249 | Coordination of equipment and supplies purchase |
| |
| Authors: | R.F. Borelli. |
| Date: | October 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0249 |
|
|
|
| |
| RFC 250 | Some thoughts on file transfer |
| |
| Authors: | H. Brodie. |
| Date: | October 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0250 |
|
|
|
| |
| RFC 251 | Weather data |
| |
|
| |
| RFC 252 | Network host status |
| |
|
| |
| RFC 253 | Second Network Graphics meeting details |
| |
| Authors: | J.A. Moorer. |
| Date: | October 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0253 |
|
|
|
| |
| RFC 254 | Scenarios for using ARPANET computers |
| |
|
| |
| RFC 255 | Status of network hosts |
| |
|
| |
| RFC 256 | IMPSYS change notification |
| |
| Authors: | B. Cosell. |
| Date: | November 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0256 |
|
|
|
| |
| RFC 263 | "Very Distant" Host interface |
| |
| Authors: | A.M. McKenzie. |
| Date: | December 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0263 |
|
|
|
| |
| 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 json html |
| Obsoletes: | RFC 0171 |
| Obsoleted by: | RFC 0354 |
| Updated by: | RFC 0310 |
| Also: | RFC 0265 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0264 |
|
|
|
| |
| 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 json html |
| Obsoletes: | RFC 0172 |
| Obsoleted by: | RFC 0354 |
| Updated by: | RFC 0281, RFC 0294, RFC 0310 |
| Also: | RFC 0264 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0265 |
|
|
|
| |
| RFC 266 | Network host status |
| |
|
| |
| RFC 267 | Network Host Status |
| |
|
| |
| RFC 268 | Graphics facilities information |
| |
| Authors: | J. Postel. |
| Date: | November 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0268 |
|
|
|
| |
| RFC 269 | Some Experience with File Transfer |
| |
|
| |
| RFC 270 | Correction to BBN Report No. 1822 (NIC NO 7958) |
| |
| Authors: | A.M. McKenzie. |
| Date: | January 1972 |
| Formats: | txt json pdf html |
| Updates: | NIC_7959 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0270 |
|
|
|
| |
| RFC 271 | IMP System change notifications |
| |
| Authors: | B. Cosell. |
| Date: | January 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0271 |
|
|
|
| |
| RFC 273 | More on standard host names |
| |
|
| |
| RFC 274 | Establishing a local guide for network usage |
| |
| Authors: | E. Forman. |
| Date: | November 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0274 |
|
|
|
| |
| RFC 276 | NIC course |
| |
| Authors: | R.W. Watson. |
| Date: | November 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0276 |
|
|
|
| |
| RFC 278 | Revision of the Mail Box Protocol |
| |
| Authors: | A.K. Bhushan, R.T. Braden, E. Harslem, J.F. Heafner, A.M. McKenzie, J.T. Melvin, R.L. Sundberg, R.W. Watson, J.E. White. |
| Date: | November 1971 |
| Formats: | txt json html |
| Obsoletes: | RFC 0221 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0278 |
|
|
|
| |
| RFC 280 | A Draft of Host Names |
| |
| Authors: | R.W. Watson. |
| Date: | November 1971 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0280 |
|
|
|
| |
| RFC 281 | Suggested addition to File Transfer Protocol |
| |
|
| |
| RFC 282 | Graphics meeting report |
| |
| Authors: | M.A. Padlipsky. |
| Date: | December 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0282 |
|
|
|
| |
| RFC 283 | NETRJT: Remote Job Service Protocol for TIPS |
| |
|
| |
| RFC 285 | Network graphics |
| |
|
| |
| RFC 286 | Network Library Information System |
| |
| Authors: | E. Forman. |
| Date: | December 1971 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0286 |
|
|
|
| |
| RFC 287 | Status of Network Hosts |
| |
|
| |
| RFC 288 | Network host status |
| |
|
| |
| RFC 289 | What we hope is an official list of host names |
| |
|
| |
| RFC 290 | Computer networks and data sharing: A bibliography |
| |
|
| |
| RFC 291 | Data Management Meeting Announcement |
| |
| Authors: | D.B. McKay. |
| Date: | January 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0291 |
|
|
|
| |
| 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 html json |
| Obsoleted by: | RFC 0493 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0292 |
|
|
|
| |
| RFC 293 | Network Host Status |
| |
|
| |
| RFC 294 | The Use of "Set Data Type" Transaction in File Transfer Protocol |
| |
|
| |
| RFC 295 | Report of the Protocol Workshop, 12 October 1971 |
| |
| Authors: | J. Postel. |
| Date: | January 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0295 |
|
|
|
| |
| RFC 296 | DS-1 Display System |
| |
|
| |
| RFC 297 | TIP Message Buffers |
| |
| Authors: | D.C. Walden. |
| Date: | January 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0297 |
|
|
|
| |
| RFC 298 | Network host status |
| |
|
| |
| RFC 299 | Information Management System |
| |
| Authors: | D. Hopkin. |
| Date: | February 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0299 |
|
|
|
| |
| RFC 300 | ARPA Network mailing lists |
| |
|
| |
| RFC 301 | BBN IMP (#5) and NCC Schedule March 4, 1971 |
| |
| Authors: | R. Alter. |
| Date: | February 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0301 |
|
|
|
| |
| RFC 302 | Exercising The ARPANET |
| |
| Authors: | R.F. Bryan. |
| Date: | February 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0302 |
|
|
|
| |
| RFC 303 | ARPA Network mailing lists |
| |
| Authors: | Network Information Center. Stanford Research Institute. |
| Date: | March 1972 |
| Formats: | txt html json |
| Obsoletes: | RFC 0300 |
| Obsoleted by: | RFC 0329 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0303 |
|
|
|
| |
| RFC 304 | Data Management System Proposal for the ARPA Network |
| |
|
| |
| RFC 305 | Unknown Host Numbers |
| |
| Authors: | R. Alter. |
| Date: | February 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0305 |
|
|
|
| |
| RFC 306 | Network host status |
| |
|
| |
| RFC 307 | Using network Remote Job Entry |
| |
| Authors: | E. Harslem. |
| Date: | February 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0307 |
|
|
|
| |
| RFC 308 | ARPANET host availability data |
| |
|
| |
| RFC 309 | Data and File Transfer Workshop Announcement |
| |
| Authors: | A.K. Bhushan. |
| Date: | March 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0309 |
|
|
|
| |
| RFC 310 | Another Look at Data and File Transfer Protocols |
| |
|
| |
| RFC 311 | New Console Attachments to the USCB Host |
| |
| Authors: | R.F. Bryan. |
| Date: | February 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0311 |
|
|
|
| |
| RFC 312 | Proposed Change in IMP-to-Host Protocol |
| |
| Authors: | A.M. McKenzie. |
| Date: | March 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0312 |
|
|
|
| |
| RFC 313 | Computer based instruction |
| |
| Authors: | T.C. O'Sullivan. |
| Date: | March 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0313 |
|
|
|
| |
| RFC 314 | Network Graphics Working Group Meeting |
| |
| Authors: | I.W. Cotton. |
| Date: | March 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0314 |
|
|
|
| |
| RFC 315 | Network Host Status |
| |
|
| |
| RFC 316 | ARPA Network Data Management Working Group |
| |
| Authors: | D.B. McKay, A.P. Mullery. |
| Date: | February 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0316 |
|
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a set of managed objects that allow monitoring of running instances of RObust Header Compression (ROHC). The managed objects defined in this memo are grouped into three MIB modules. The ROHC-MIB module defines managed objects shared by all ROHC profiles, the ROHC-UNCOMPRESSED-MIB module defines managed objects specific to the ROHC uncompressed profile, the ROHC-RTP-MIB module defines managed objects specific to the ROHC RTP (Real-Time Transport Protocol) profile, the ROHC UDP (User Datagram Protocol) profile, the ROHC ESP (Encapsulating Security Payload) profile, and the ROHC LLA (Link Layer Assisted) profile. [STANDARDS TRACK |
|
| |
| RFC 317 | Official Host-Host Protocol Modification: Assigned Link Numbers |
| |
|
| |
| RFC 318 | Telnet Protocols |
| |
|
| |
| RFC 319 | Network Host Status |
| |
|
| |
| RFC 320 | Workshop on Hard Copy Line Graphics |
| |
|
| |
| RFC 321 | CBI Networking Activity at MITRE |
| |
|
| |
| RFC 322 | Well known socket numbers |
| |
| Authors: | V. Cerf, J. Postel. |
| Date: | March 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0322 |
|
|
|
| |
| RFC 323 | Formation of Network Measurement Group (NMG) |
| |
|
| |
| RFC 324 | RJE Protocol meeting |
| |
|
| |
| RFC 325 | Network Remote Job Entry program - NETRJS |
| |
|
| |
| RFC 326 | Network Host Status |
| |
|
| |
| RFC 327 | Data and File Transfer workshop notes |
| |
| Authors: | A.K. Bhushan. |
| Date: | April 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0327 |
|
|
|
| |
| RFC 328 | Suggested Telnet Protocol Changes |
| |
|
| |
| RFC 329 | ARPA Network Mailing Lists |
| |
| Authors: | Network Information Center. Stanford Research Institute. |
| Date: | May 1972 |
| Formats: | txt json html |
| Obsoletes: | RFC 0303 |
| Obsoleted by: | RFC 0363 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0329 |
|
|
|
| |
| RFC 330 | Network Host Status |
| |
|
| |
| RFC 331 | IMP System Change Notification |
| |
|
| |
| RFC 332 | Network Host Status |
| |
|
| |
| RFC 333 | Proposed experiment with a Message Switching Protocol |
| |
| Authors: | R.D. Bressler, D. Murphy, D.C. Walden. |
| Date: | May 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0333 |
|
|
|
| |
| RFC 334 | Network Use on May 8 |
| |
| Authors: | A.M. McKenzie. |
| Date: | May 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0334 |
|
|
|
| |
| RFC 335 | New Interface - IMP/360 |
| |
|
| |
| RFC 336 | Level 0 Graphic Input Protocol |
| |
|
| |
| RFC 338 | EBCDIC/ASCII Mapping for Network RJE |
| |
|
| |
| RFC 339 | MLTNET: A "Multi Telnet" Subsystem for Tenex |
| |
|
| |
| RFC 340 | Proposed Telnet Changes |
| |
|
| |
| RFC 342 | Network Host Status |
| |
|
| |
| RFC 343 | IMP System change notification |
| |
|
| |
| RFC 344 | Network Host Status |
| |
|
| |
| RFC 345 | Interest in Mixed Integer Programming (MPSX on NIC 360/91 at CCN) |
| |
|
| |
| RFC 346 | Satellite Considerations |
| |
|
| |
| RFC 347 | Echo process |
| |
|
| |
| RFC 348 | Discard Process |
| |
|
| |
| RFC 349 | Proposed Standard Socket Numbers |
| |
|
| |
| RFC 350 | User Accounts for UCSB On-Line System |
| |
|
| |
| RFC 351 | Graphics information form for the ARPANET graphics resources notebook |
| |
|
| |
| RFC 352 | TIP Site Information Form |
| |
|
| |
| RFC 353 | Network host status |
| |
|
| |
| RFC 354 | File Transfer Protocol |
| |
|
| |
| RFC 355 | Response to NWG/RFC 346 |
| |
|
| |
| RFC 356 | ARPA Network Control Center |
| |
|
| |
| RFC 357 | Echoing strategy for satellite links |
| |
|
| |
| RFC 359 | Status of the Release of the New IMP System (2600) |
| |
|
| |
| RFC 360 | Proposed Remote Job Entry Protocol |
| |
|
| |
| RFC 361 | Deamon Processes on Host 106 |
| |
| Authors: | R.D. Bressler. |
| Date: | July 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0361 |
|
|
|
| |
| RFC 362 | Network Host Status |
| |
|
| |
| RFC 363 | ARPA Network mailing lists |
| |
| Authors: | Network Information Center. Stanford Research Institute. |
| Date: | August 1972 |
| Formats: | txt json html |
| Obsoletes: | RFC 0329 |
| Obsoleted by: | RFC 0402 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0363 |
|
|
|
| |
| RFC 364 | Serving remote users on the ARPANET |
| |
|
| |
| RFC 365 | Letter to All TIP Users |
| |
|
| |
| RFC 366 | Network Host Status |
| |
|
| |
| RFC 367 | Network host status |
| |
|
| |
| RFC 368 | Comments on "Proposed Remote Job Entry Protocol" |
| |
|
| |
| RFC 369 | Evaluation of ARPANET services January-March, 1972 |
| |
| Authors: | J.R. Pickens. |
| Date: | July 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0369 |
|
|
|
| |
| RFC 370 | Network Host Status |
| |
|
| |
| RFC 371 | Demonstration at International Computer Communications Conference |
| |
|
| |
| RFC 372 | Notes on a Conversation with Bob Kahn on the ICCC |
| |
|
| |
| RFC 373 | Arbitrary Character Sets |
| |
|
| |
| RFC 374 | IMP System Announcement |
| |
| Authors: | A.M. McKenzie. |
| Date: | July 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0374 |
|
|
|
| |
| RFC 376 | Network Host Status |
| |
|
| |
| RFC 377 | Using TSO via ARPA Network Virtual Terminal |
| |
| Authors: | R.T. Braden. |
| Date: | August 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0377 |
|
|
|
| |
| RFC 378 | Traffic statistics (July 1972) |
| |
|
| |
| RFC 379 | Using TSO at CCN |
| |
|
| |
| RFC 381 | Three aids to improved network operation |
| |
|
| |
| RFC 382 | Mathematical Software on the ARPA Network |
| |
| Authors: | L. McDaniel. |
| Date: | August 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0382 |
|
|
|
| |
| RFC 384 | Official site idents for organizations in the ARPA Network |
| |
|
| |
| RFC 385 | Comments on the File Transfer Protocol |
| |
|
| |
| RFC 386 | Letter to TIP users-2 |
| |
| Authors: | B. Cosell, D.C. Walden. |
| Date: | August 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0386 |
|
|
|
| |
| RFC 387 | Some experiences in implementing Network Graphics Protocol Level 0 |
| |
|
| |
| RFC 388 | NCP statistics |
| |
|
| |
| RFC 389 | UCLA Campus Computing Network Liaison Staff for ARPA Network |
| |
|
| |
| RFC 390 | TSO Scenario |
| |
| Authors: | R.T. Braden. |
| Date: | September 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0390 |
|
|
|
| |
| RFC 391 | Traffic statistics (August 1972) |
| |
|
| |
| RFC 392 | Measurement of host costs for transmitting network data |
| |
| Authors: | G. Hicks, B.D. Wessler. |
| Date: | September 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0392 |
|
|
|
| |
| RFC 393 | Comments on Telnet Protocol Changes |
| |
|
| |
| RFC 394 | Two Proposed Changes to the IMP-Host Protocol |
| |
|
| |
| RFC 395 | Switch Settings on IMPs and TIPs |
| |
| Authors: | J.M. McQuillan. |
| Date: | October 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0395 |
|
|
|
| |
| RFC 396 | Network Graphics Working Group Meeting - Second Iteration |
| |
|
| |
| RFC 398 | UCSB Online Graphics |
| |
| Authors: | J.R. Pickens, E. Faeh. |
| Date: | September 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0398 |
|
|
|
| |
| RFC 399 | SMFS Login and Logout |
| |
|
| |
| RFC 400 | Traffic Statistics (September 1972) |
| |
| Authors: | A.M. McKenzie. |
| Date: | October 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0400 |
|
|
|
| |
| RFC 401 | Conversion of NGP-0 Coordinates to Device Specific Coordinates |
| |
|
| |
| RFC 402 | ARPA Network Mailing Lists |
| |
|
| |
| RFC 403 | Desirability of a Network 1108 Service |
| |
|
| |
| RFC 404 | Host Address Changes Involving Rand and ISI |
| |
|
| |
| RFC 405 | Correction to RFC 404 |
| |
|
| |
| RFC 406 | Scheduled IMP Software Releases |
| |
| Authors: | J.M. McQuillan. |
| Date: | October 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0406 |
|
|
|
| |
| RFC 408 | NETBANK |
| |
| Authors: | A.D. Owen, J. Postel. |
| Date: | October 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0408 |
|
|
|
| |
| RFC 409 | Tenex interface to UCSB's Simple-Minded File System |
| |
| Authors: | J.E. White. |
| Date: | December 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0409 |
|
|
|
| |
| RFC 410 | Removal of the 30-Second Delay When Hosts Come Up |
| |
| Authors: | J.M. McQuillan. |
| Date: | November 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0410 |
|
|
|
| |
| RFC 411 | New MULTICS Network Software Features |
| |
| Authors: | M.A. Padlipsky. |
| Date: | November 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0411 |
|
|
|
| |
| RFC 412 | User FTP Documentation |
| |
| Authors: | G. Hicks. |
| Date: | November 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0412 |
|
|
|
| |
| RFC 413 | Traffic statistics (October 1972) |
| |
| Authors: | A.M. McKenzie. |
| Date: | November 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0413 |
|
|
|
| |
| RFC 414 | File Transfer Protocol (FTP) status and further comments |
| |
|
| |
| RFC 415 | Tenex bandwidth |
| |
| Authors: | H. Murray. |
| Date: | November 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0415 |
|
|
|
| |
| RFC 416 | ARC System Will Be Unavailable for Use During Thanksgiving Week |
| |
| Authors: | J.C. Norton. |
| Date: | November 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0416 |
|
|
|
| |
| RFC 417 | Link usage violation |
| |
| Authors: | J. Postel, C. Kline. |
| Date: | December 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0417 |
|
|
|
| |
| RFC 418 | Server File Transfer Under TSS/360 At NASA-Ames Research Center |
| |
| Authors: | W. Hathaway. |
| Date: | November 1972 |
| Formats: | json pdf |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0418 |
|
|
|
| |
| RFC 419 | To: Network liaisons and station agents |
| |
| Authors: | A. Vezza. |
| Date: | December 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0419 |
|
|
|
| |
| RFC 420 | CCA ICCC weather demo |
| |
| Authors: | H. Murray. |
| Date: | January 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0420 |
|
|
|
| |
| RFC 421 | Software Consulting Service for Network Users |
| |
| Authors: | A.M. McKenzie. |
| Date: | November 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0421 |
|
|
|
| |
| RFC 422 | Traffic statistics (November 1972) |
| |
| Authors: | A.M. McKenzie. |
| Date: | December 1972 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0422 |
|
|
|
| |
| RFC 423 | UCLA Campus Computing Network Liaison Staff for ARPANET |
| |
|
| |
| RFC 425 | "But my NCP costs $500 a day" |
| |
| Authors: | R.D. Bressler. |
| Date: | December 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0425 |
|
|
|
| |
| RFC 426 | Reconnection Protocol |
| |
| Authors: | R. Thomas. |
| Date: | January 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0426 |
|
|
|
| |
| RFC 429 | Character Generator Process |
| |
| Authors: | J. Postel. |
| Date: | December 1972 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0429 |
|
|
|
| |
| RFC 430 | Comments on File Transfer Protocol |
| |
| Authors: | R.T. Braden. |
| Date: | February 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0430 |
|
|
|
| |
| RFC 431 | Update on SMFS Login and Logout |
| |
|
| |
| RFC 432 | Network logical map |
| |
|
| |
| RFC 433 | Socket number list |
| |
|
| |
| RFC 434 | IMP/TIP memory retrofit schedule |
| |
|
| |
| RFC 435 | Telnet issues |
| |
|
| |
| RFC 436 | Announcement of RJS at UCSB |
| |
| Authors: | M. Krilanovich. |
| Date: | January 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0436 |
|
|
|
| |
| RFC 437 | Data Reconfiguration Service at UCSB |
| |
|
| |
| RFC 438 | FTP server-server interaction |
| |
| Authors: | R. Thomas, R. Clements. |
| Date: | January 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0438 |
|
|
|
| |
| RFC 439 | PARRY encounters the DOCTOR |
| |
|
| |
| RFC 440 | Scheduled network software maintenance |
| |
| Authors: | D.C. Walden. |
| Date: | January 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0440 |
|
|
|
| |
| RFC 441 | Inter-Entity Communication - an experiment |
| |
| Authors: | R.D. Bressler, R. Thomas. |
| Date: | January 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0441 |
|
|
|
| |
| RFC 442 | Current flow-control scheme for IMPSYS |
| |
|
| |
| RFC 443 | Traffic statistics (December 1972) |
| |
| Authors: | A.M. McKenzie. |
| Date: | January 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0443 |
|
|
|
| |
| RFC 445 | IMP/TIP preventive maintenance schedule |
| |
| Authors: | A.M. McKenzie. |
| Date: | January 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0445 |
|
|
|
| |
| RFC 446 | Proposal to consider a network program resource notebook |
| |
| Authors: | L.P. Deutsch. |
| Date: | January 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0446 |
|
|
|
| |
| RFC 447 | IMP/TIP memory retrofit schedule |
| |
|
| |
| RFC 448 | Print files in FTP |
| |
| Authors: | R.T. Braden. |
| Date: | February 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0448 |
|
|
|
| |
| RFC 449 | Current flow-control scheme for IMPSYS |
| |
|
| |
| RFC 450 | MULTICS sampling timeout change |
| |
| Authors: | M.A. Padlipsky. |
| Date: | February 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0450 |
|
|
|
| |
| RFC 451 | Tentative proposal for a Unified User Level Protocol |
| |
| Authors: | M.A. Padlipsky. |
| Date: | February 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0451 |
|
|
|
| |
| RFC 452 | TELNET Command at Host LL |
| |
|
| |
| RFC 453 | Meeting announcement to discuss a network mail system |
| |
| Authors: | M.D. Kudlick. |
| Date: | February 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0453 |
|
|
|
| |
| RFC 454 | File Transfer Protocol - meeting announcement and a new proposed document |
| |
|
| |
| RFC 455 | Traffic statistics (January 1973) |
| |
| Authors: | A.M. McKenzie. |
| Date: | February 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0455 |
|
|
|
| |
| RFC 456 | Memorandum: Date change of mail meeting |
| |
| Authors: | M.D. Kudlick. |
| Date: | February 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0456 |
|
|
|
| |
| RFC 457 | TIPUG |
| |
| Authors: | D.C. Walden. |
| Date: | February 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0457 |
|
|
|
| |
| RFC 458 | Mail retrieval via FTP |
| |
| Authors: | R.D. Bressler, R. Thomas. |
| Date: | February 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0458 |
|
|
|
| |
| RFC 459 | Network questionnaires |
| |
| Authors: | W. Kantrowitz. |
| Date: | February 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0459 |
|
|
|
| |
| RFC 460 | NCP survey |
| |
| Authors: | C. Kline. |
| Date: | February 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0460 |
|
|
|
| |
| RFC 461 | Telnet Protocol meeting announcement |
| |
| Authors: | A.M. McKenzie. |
| Date: | February 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0461 |
|
|
|
| |
| RFC 462 | Responding to user needs |
| |
| Authors: | J. Iseli, D. Crocker. |
| Date: | February 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0462 |
|
|
|
| |
| RFC 463 | FTP comments and response to RFC 430 |
| |
| Authors: | A.K. Bhushan. |
| Date: | February 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0463 |
|
|
|
| |
| RFC 464 | Resource notebook framework |
| |
| Authors: | M.D. Kudlick. |
| Date: | February 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0464 |
|
|
|
| |
| RFC 466 | Telnet logger/server for host LL-67 |
| |
| Authors: | J.M. Winett. |
| Date: | February 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0466 |
|
|
|
| |
| RFC 467 | Proposed change to Host-Host Protocol: Resynchronization of connection status |
| |
| Authors: | J.D. Burchfiel, R.S. Tomlinson. |
| Date: | February 1973 |
| Formats: | txt html json |
| Updated by: | RFC 0492 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0467 |
|
|
|
| |
| RFC 468 | FTP data compression |
| |
| Authors: | R.T. Braden. |
| Date: | March 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0468 |
|
|
|
| |
| RFC 469 | Network mail meeting summary |
| |
| Authors: | M.D. Kudlick. |
| Date: | March 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0469 |
|
|
|
| |
| RFC 470 | Change in socket for TIP news facility |
| |
|
| |
| RFC 471 | Workshop on multi-site executive programs |
| |
|
| |
| RFC 472 | Illinois' reply to Maxwell's request for graphics information (NIC 14925) |
| |
|
| |
| RFC 473 | MIX and MIXAL? |
| |
| Authors: | D.C. Walden. |
| Date: | February 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0473 |
|
|
|
| |
| RFC 474 | Announcement of NGWG meeting: Call for papers |
| |
|
| |
| RFC 475 | FTP and Network Mail System |
| |
|
| |
| RFC 476 | IMP/TIP memory retrofit schedule (rev 2) |
| |
|
| |
| RFC 477 | Remote Job Service at UCSB |
| |
| Authors: | M. Krilanovich. |
| Date: | May 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0477 |
|
|
|
| |
| RFC 478 | FTP server-server interaction - II |
| |
| Authors: | R.D. Bressler, R. Thomas. |
| Date: | March 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0478 |
|
|
|
| |
| RFC 479 | Use of FTP by the NIC Journal |
| |
|
| |
| RFC 480 | Host-dependent FTP parameters |
| |
|
| |
| RFC 482 | Traffic statistics (February 1973) |
| |
|
| |
| RFC 483 | Cancellation of the resource notebook framework meeting |
| |
| Authors: | M.D. Kudlick. |
| Date: | March 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0483 |
|
|
|
| |
| RFC 485 | MIX and MIXAL at UCSB |
| |
| Authors: | J.R. Pickens. |
| Date: | March 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0485 |
|
|
|
| |
| RFC 486 | Data transfer revisited |
| |
| Authors: | R.D. Bressler. |
| Date: | March 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0486 |
|
|
|
| |
| RFC 487 | Free file transfer |
| |
| Authors: | R.D. Bressler. |
| Date: | April 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0487 |
|
|
|
| |
| RFC 488 | NLS classes at network sites |
| |
| Authors: | M.F. Auerbach. |
| Date: | March 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0488 |
|
|
|
| |
| RFC 489 | Comment on resynchronization of connection status proposal |
| |
|
| |
| RFC 490 | Surrogate RJS for UCLA-CCN |
| |
| Authors: | J.R. Pickens. |
| Date: | March 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0490 |
|
|
|
| |
| RFC 491 | What is "Free"? |
| |
| Authors: | M.A. Padlipsky. |
| Date: | April 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0491 |
|
|
|
| |
| RFC 492 | Response to RFC 467 |
| |
|
| |
| RFC 493 | GRAPHICS PROTOCOL |
| |
| Authors: | J.C. Michener, I.W. Cotton, K.C. Kelley, D.E. Liddle, E. Meyer. |
| Date: | April 1973 |
| Formats: | txt html pdf json |
| Obsoletes: | RFC 0292 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0493 |
|
|
|
| |
| RFC 494 | Availability of MIX and MIXAL in the Network |
| |
| Authors: | D.C. Walden. |
| Date: | April 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0494 |
|
|
|
| |
| RFC 495 | Telnet Protocol specifications |
| |
|
| |
| RFC 496 | TNLS quick reference card is available |
| |
| Authors: | M.F. Auerbach. |
| Date: | April 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0496 |
|
|
|
| |
| RFC 497 | Traffic Statistics (March 1973) |
| |
|
| |
| RFC 498 | On mail service to CCN |
| |
| Authors: | R.T. Braden. |
| Date: | April 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0498 |
|
|
|
| |
| RFC 499 | Harvard's network RJE |
| |
| Authors: | B.R. Reussow. |
| Date: | April 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0499 |
|
|
|
| |
| RFC 500 | Integration of data management systems on a computer network |
| |
| Authors: | A. Shoshani, I. Spiegler. |
| Date: | April 1973 |
| Formats: | json pdf |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0500 |
|
|
|
| |
| RFC 501 | Un-muddling "free file transfer" |
| |
|
| |
| RFC 503 | Socket number list |
| |
|
| |
| RFC 504 | Distributed resources workshop announcement |
| |
|
| |
| RFC 505 | Two solutions to a file transfer access problem |
| |
| Authors: | M.A. Padlipsky. |
| Date: | June 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0505 |
|
|
|
| |
| RFC 506 | FTP command naming problem |
| |
| Authors: | M.A. Padlipsky. |
| Date: | June 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0506 |
|
|
|
| |
| RFC 508 | Real-time data transmission on the ARPANET |
| |
| Authors: | L. Pfeifer, J. McAfee. |
| Date: | May 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0508 |
|
|
|
| |
| RFC 509 | Traffic statistics (April 1973) |
| |
| Authors: | A.M. McKenzie. |
| Date: | April 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0509 |
|
|
|
| |
| RFC 510 | Request for network mailbox addresses |
| |
|
| |
| RFC 511 | Enterprise phone service to NIC from ARPANET sites |
| |
|
| |
| RFC 512 | More on lost message detection |
| |
|
| |
| RFC 513 | Comments on the new Telnet specifications |
| |
|
| |
| RFC 514 | Network make-work |
| |
| Authors: | W. Kantrowitz. |
| Date: | June 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0514 |
|
|
|
| |
| RFC 515 | Specifications for Datalanguage, Version 0/9 |
| |
|
| |
| RFC 516 | Lost message detection |
| |
|
| |
| RFC 518 | ARPANET accounts |
| |
| Authors: | N. Vaughan, E.J. Feinler. |
| Date: | June 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0518 |
|
|
|
| |
| RFC 519 | Resource Evaluation |
| |
|
|
In the spirit of RFC # 369, Evaluation of ARPANET resources, a new test group was organized at UCSB to take a detailed look at specific network resources and develop initial site dependent and function dependent MINIMAN's (Concise User Manuals). As the group was again composed of novices, initial effort revolved about basic procedural indoctrination. In the period between January and March 1973 a number of resources were investigated with varying degrees of success, as to availability, proper usage, sample problem solutions, and access to help and documentation. Included in this paper are a summary of the projects undertaken, initial suggestions at MINIMAN composition, and suggestions for future test groups. As these groups are attempting to perform a useful function for the ARPANET community, comments and suggestions are requested. Copies of the reports described herein are available on request from the ComputerSystems Laboratory at UCSB. |
|
| |
| RFC 520 | Memo to FTP group: Proposal for File Access Protocol |
| |
|
| |
| RFC 521 | Restricted use of IMP DDT |
| |
| Authors: | A.M. McKenzie. |
| Date: | May 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0521 |
|
|
|
| |
| RFC 522 | Traffic Statistics (May 1973) |
| |
|
| |
| RFC 523 | SURVEY is in operation again |
| |
| Authors: | A.K. Bhushan. |
| Date: | June 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0523 |
|
|
|
| |
| RFC 524 | Proposed Mail Protocol |
| |
|
| |
| RFC 525 | MIT-MATHLAB meets UCSB-OLS -an example of resource sharing |
| |
|
| |
| RFC 526 | Technical meeting: Digital image processing software systems |
| |
|
| |
| RFC 527 | ARPAWOCKY |
| |
|
| |
| RFC 528 | Software checksumming in the IMP and network reliability |
| |
| Authors: | J.M. McQuillan. |
| Date: | June 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0528 |
|
|
|
| |
| RFC 529 | Note on protocol synch sequences |
| |
| Authors: | A.M. McKenzie, R. Thomas, R.S. Tomlinson, K.T. Pogran. |
| Date: | June 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0529 |
|
|
|
| |
| RFC 530 | Report on the Survey Project |
| |
|
| |
| RFC 531 | Feast or famine? A response to two recent RFC's about network information |
| |
| Authors: | M.A. Padlipsky. |
| Date: | June 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0531 |
|
|
|
| |
| RFC 532 | UCSD-CC Server-FTP facility |
| |
| Authors: | R.G. Merryman. |
| Date: | July 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0532 |
|
|
|
| |
| RFC 533 | Message-ID numbers |
| |
|
| |
| RFC 534 | Lost message detection |
| |
|
| |
| RFC 535 | Comments on File Access Protocol |
| |
|
| |
| RFC 537 | Announcement of NGG meeting July 16-17 |
| |
|
| |
| RFC 538 | Traffic statistics (June 1973) |
| |
|
| |
| RFC 539 | Thoughts on the mail protocol proposed in RFC 524 |
| |
| Authors: | D. Crocker, J. Postel. |
| Date: | July 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0539 |
|
|
|
| |
| RFC 542 | File Transfer Protocol |
| |
|
| |
| RFC 543 | Network journal submission and delivery |
| |
|
| |
| RFC 544 | Locating on-line documentation at SRI-ARC |
| |
| Authors: | N.D. Meyer, K. Kelley. |
| Date: | July 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0544 |
|
|
|
| |
| RFC 545 | Of what quality be the UCSB resources evaluators? |
| |
| Authors: | J.R. Pickens. |
| Date: | July 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0545 |
|
|
|
| |
| RFC 546 | Tenex load averages for July 1973 |
| |
|
| |
| RFC 547 | Change to the Very Distant Host specification |
| |
| Authors: | D.C. Walden. |
| Date: | August 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0547 |
|
|
|
| |
| RFC 548 | Hosts using the IMP Going Down message |
| |
| Authors: | D.C. Walden. |
| Date: | August 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0548 |
|
|
|
| |
| RFC 549 | Minutes of Network Graphics Group meeting, 15-17 July 1973 |
| |
| Authors: | J.C. Michener. |
| Date: | July 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0549 |
|
|
|
| |
| RFC 550 | NIC NCP experiment |
| |
| Authors: | L.P. Deutsch. |
| Date: | August 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0550 |
|
|
|
| |
| RFC 551 | NYU, ANL, and LBL Joining the Net |
| |
|
| |
| RFC 552 | Single access to standard protocols |
| |
|
| |
| RFC 553 | Draft design for a text/graphics protocol |
| |
| Authors: | C.H. Irby, K. Victor. |
| Date: | July 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0553 |
|
|
|
| |
| RFC 555 | Responses to critiques of the proposed mail protocol |
| |
|
| |
| RFC 556 | Traffic Statistics (July 1973) |
| |
|
| |
| RFC 557 | REVELATIONS IN NETWORK HOST MEASUREMENTS |
| |
|
| |
| RFC 559 | Comments on The New Telnet Protocol and its Implementation |
| |
| Authors: | A.K. Bushan. |
| Date: | August 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0559 |
|
|
|
| |
| RFC 560 | Remote Controlled Transmission and Echoing Telnet option |
| |
|
| |
| RFC 561 | Standardizing Network Mail Headers |
| |
| Authors: | A.K. Bhushan, K.T. Pogran, R.S. Tomlinson, J.E. White. |
| Date: | September 1973 |
| Formats: | txt html json |
| Updated by: | RFC 0680 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0561 |
|
|
|
| |
| RFC 562 | Modifications to the TELNET Specification |
| |
|
| |
| RFC 563 | Comments on the RCTE Telnet option |
| |
| Authors: | J. Davidson. |
| Date: | August 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0563 |
|
|
|
| |
| RFC 565 | Storing network survey data at the datacomputer |
| |
|
| |
| RFC 566 | Traffic statistics (August 1973) |
| |
|
| |
| RFC 567 | Cross Country Network Bandwidth |
| |
|
| |
| RFC 568 | Response to RFC 567 - cross country network bandwidth |
| |
|
| |
| RFC 570 | Experimental input mapping between NVT ASCII and UCSB On Line System |
| |
|
| |
| RFC 571 | TENEX FTP PROBLEM |
| |
| Authors: | R. Braden. |
| Date: | November 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0571 |
|
|
|
| |
| RFC 573 | DATA AND FILE TRANSFER - SOME MEASUREMENT RESULTS |
| |
|
| |
| RFC 574 | Announcement of a Mail Facility at UCSB |
| |
|
| |
| RFC 576 | Proposal for modifying linking |
| |
|
| |
| RFC 577 | Mail priority |
| |
|
| |
| RFC 578 | Using MIT-Mathlab MACSYMA from MIT-DMS Muddle |
| |
| Authors: | A.K. Bhushan, N.D. Ryan. |
| Date: | October 1973 |
| Formats: | txt pdf html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0578 |
|
|
|
| |
| RFC 579 | Traffic statistics (September 1973) |
| |
|
| |
| RFC 580 | Note to Protocol Designers and Implementers |
| |
|
| |
| RFC 581 | Corrections to RFC 560: Remote Controlled Transmission and Echoing Telnet Option |
| |
|
| |
| RFC 582 | Comments on RFC 580: Machine readable protocols |
| |
|
| |
| RFC 584 | Charter for ARPANET Users Interest Working Group |
| |
| Authors: | J. Iseli, D. Crocker, N. Neigus. |
| Date: | November 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0584 |
|
|
|
| |
| RFC 585 | ARPANET users interest working group meeting |
| |
| Authors: | D. Crocker, N. Neigus, E.J. Feinler, J. Iseli. |
| Date: | November 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0585 |
|
|
|
| |
| RFC 586 | Traffic statistics (October 1973) |
| |
|
| |
| RFC 587 | Announcing New Telnet Options |
| |
| Authors: | J. Postel. |
| Date: | November 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0587 |
|
|
|
| |
| RFC 588 | London Node Is Now Up |
| |
|
| |
| RFC 589 | CCN NETRJS server messages to remote user |
| |
| Authors: | R.T. Braden. |
| Date: | November 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0589 |
|
|
|
| |
| RFC 590 | MULTICS address change |
| |
| Authors: | M.A. Padlipsky. |
| Date: | November 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0590 |
|
|
|
| |
| RFC 591 | Addition to the Very Distant Host specifications |
| |
| Authors: | D.C. Walden. |
| Date: | November 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0591 |
|
|
|
| |
| RFC 592 | Some thoughts on system design to facilitate resource sharing |
| |
|
| |
| RFC 593 | Telnet and FTP implementation schedule change |
| |
| Authors: | A.M. McKenzie, J. Postel. |
| Date: | November 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0593 |
|
|
|
| |
| RFC 594 | Speedup of Host-IMP interface |
| |
|
| |
| RFC 595 | Second thoughts in defense of the Telnet Go-Ahead |
| |
| Authors: | W. Hathaway. |
| Date: | December 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0595 |
|
|
|
| |
| RFC 596 | Second thoughts on Telnet Go-Ahead |
| |
| Authors: | E.A. Taft. |
| Date: | December 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0596 |
|
|
|
| |
| RFC 597 | Host status |
| |
|
| |
| RFC 598 | RFC index - December 5, 1973 |
| |
| Authors: | Network Information Center. Stanford Research Institute. |
| Date: | December 1973 |
| Formats: | json pdf |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0598 |
|
|
|
| |
| RFC 599 | Update on NETRJS |
| |
|
| |
| RFC 600 | Interfacing an Illinois plasma terminal to the ARPANET |
| |
|
| |
| RFC 601 | Traffic statistics (November 1973) |
| |
| Authors: | A.M. McKenzie. |
| Date: | December 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0601 |
|
|
|
| |
| RFC 602 | "The stockings were hung by the chimney with care" |
| |
| Authors: | R.M. Metcalfe. |
| Date: | December 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0602 |
|
Susceptibility of ARPANET to security violations. |
|
| |
| RFC 603 | Response to RFC 597: Host status |
| |
|
|
Questions about the ARPANET topology described in RFC 597. |
|
| |
| RFC 604 | Assigned link numbers |
| |
|
|
Modifies official host-host protocol. Replaces RFC 377. |
|
| |
| RFC 606 | Host names on-line |
| |
| Authors: | L.P. Deutsch. |
| Date: | December 1973 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0606 |
|
Resolving differences in hostname-address mappings; see also RFCs 627, 625, 623 and 608. |
|
| |
| RFC 607 | Comments on the File Transfer Protocol |
| |
|
|
An old version; see RFC 624; see also RFCs 614, 542 and 640. |
|
| |
| RFC 608 | Host names on-line |
| |
|
|
Response to RFC 606; see also RFCs 627, 625 and 623. |
|
| |
| RFC 609 | Statement of upcoming move of NIC/NLS service |
| |
| Authors: | B. Ferguson. |
| Date: | January 1974 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0609 |
|
See also RFCs 621 and 620. |
|
| |
| RFC 610 | Further datalanguage design concepts |
| |
| Authors: | R. Winter, J. Hill, W. Greiff. |
| Date: | December 1973 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0610 |
|
Preliminary results of the language design; a model for data languagea semantics; future considerations. |
|
| |
| RFC 611 | Two changes to the IMP/Host Protocol to improve user/network communications |
| |
| Authors: | D.C. Walden. |
| Date: | February 1974 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0611 |
|
Expansion of Host-Going-Down and addition of Dead-Host-Status Message. |
|
| |
| RFC 612 | Traffic statistics (December 1973) |
| |
| Authors: | A.M. McKenzie. |
| Date: | January 1974 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0612 |
|
|
|
| |
| RFC 613 | Network connectivity: A response to RFC 603 |
| |
|
| |
| RFC 614 | Response to RFC 607: "Comments on the File Transfer Protocol" |
| |
|
|
See also RFCs 624, 542 and 640. |
|
| |
| RFC 615 | Proposed Network Standard Data Pathname syntax |
| |
|
| |
| RFC 616 | LATEST NETWORK MAPS |
| |
|
| |
| RFC 617 | Note on socket number assignment |
| |
| Authors: | E.A. Taft. |
| Date: | February 1974 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0617 |
|
Danger of imposing more fixed socket number requirements; see also RFCs 542, 503 and 451. |
|
| |
| RFC 618 | Few observations on NCP statistics |
| |
| Authors: | E.A. Taft. |
| Date: | February 1974 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0618 |
|
Distribution of NCP and IMP message types by actual measurement. |
|
| |
| RFC 619 | Mean round-trip times in the ARPANET |
| |
| Authors: | W. Naylor, H. Opderbeck. |
| Date: | March 1974 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0619 |
|
Actual measurements of round-trip times. |
|
| |
| RFC 620 | Request for monitor host table updates |
| |
| Authors: | B. Ferguson. |
| Date: | March 1974 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0620 |
|
In conjunction with moving NIC users to OFFICE-1; see also RFCs 621 and 609. |
|
| |
| RFC 621 | NIC user directories at SRI ARC |
| |
| Authors: | M.D. Kudlick. |
| Date: | March 1974 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0621 |
|
See also RFCs 620 and 609. |
|
| |
| RFC 622 | Scheduling IMP/TIP down time |
| |
| Authors: | A.M. McKenzie. |
| Date: | March 1974 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0622 |
|
Modification of previous policy. |
|
| |
| RFC 623 | Comments on on-line host name service |
| |
| Authors: | M. Krilanovich. |
| Date: | February 1974 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0623 |
|
See also RFCs 627, 625, 608 and 606. |
|
| |
| RFC 624 | Comments on the File Transfer Protocol |
| |
| Authors: | M. Krilanovich, G. Gregg, W. Hathaway, J.E. White. |
| Date: | February 1974 |
| Formats: | txt html json |
| Obsoletes: | RFC 0607 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0624 |
|
Design changes and slight modifications. Replaces RFC 607; see also RFCs 614, 542 and 640. |
|
| |
| RFC 625 | On-line hostnames service |
| |
| Authors: | M.D. Kudlick, E.J. Feinler. |
| Date: | March 1974 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0625 |
|
See also RFCs 606, 608, 623 and 627. |
|
| |
| RFC 626 | On a possible lockup condition in IMP subnet due to message sequencing |
| |
| Authors: | L. Kleinrock, H. Opderbeck. |
| Date: | March 1974 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0626 |
|
|
|
| |
| RFC 627 | ASCII text file of hostnames |
| |
| Authors: | M.D. Kudlick, E.J. Feinler. |
| Date: | March 1974 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0627 |
|
See also RFCs 606, 608, 623 and 625. |
|
| |
| RFC 628 | Status of RFC numbers and a note on pre-assigned journal numbers |
| |
| Authors: | M.L. Keeney. |
| Date: | March 1974 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0628 |
|
|
|
| |
| RFC 629 | Scenario for using the Network Journal |
| |
|
| |
| RFC 630 | FTP error code usage for more reliable mail service |
| |
|
|
Describes FTP reply-code usage in TENEX mail processing. |
|
| |
| RFC 631 | International meeting on minicomputers and data communication: Call for papers |
| |
| Authors: | A. Danthine. |
| Date: | April 1974 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0631 |
|
|
|
| |
| RFC 632 | Throughput degradations for single packet messages |
| |
|
| |
| RFC 633 | IMP/TIP preventive maintenance schedule |
| |
|
|
An old version; see RFC 638. |
|
| |
| RFC 634 | Change in network address for Haskins Lab |
| |
| Authors: | A.M. McKenzie. |
| Date: | April 1974 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0634 |
|
|
|
| |
| RFC 635 | Assessment of ARPANET protocols |
| |
|
| |
| RFC 636 | TIP/Tenex reliability improvements |
| |
| Authors: | J.D. Burchfiel, B. Cosell, R.S. Tomlinson, D.C. Walden. |
| Date: | June 1974 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0636 |
|
Obtaining/maintaining connections; recovery from lost connections; connection-state changes. |
|
| |
| RFC 637 | Change of network address for SU-DSL |
| |
| Authors: | A.M. McKenzie. |
| Date: | April 1974 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0637 |
|
|
|
| |
| RFC 638 | IMP/TIP preventive maintenance schedule |
| |
|
| |
| RFC 640 | Revised FTP reply codes |
| |
|
| |
| RFC 642 | Ready line philosophy and implementation |
| |
| Authors: | J.D. Burchfiel. |
| Date: | July 1974 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0642 |
|
|
|
| |
| RFC 643 | Network Debugging Protocol |
| |
|
|
To be used in an implementation of a PDP-11 network bootstrap device and a cross-network debugger. |
|
| |
| RFC 644 | On the problem of signature authentication for network mail |
| |
|
| |
| RFC 645 | Network Standard Data Specification syntax |
| |
|
| |
| RFC 647 | Proposed protocol for connecting host computers to ARPA-like networks via front end processors |
| |
|
| |
| RFC 651 | Revised Telnet status option |
| |
|
| |
| RFC 659 | Announcing additional Telnet options |
| |
| Authors: | J. Postel. |
| Date: | October 1974 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0659 |
|
Options defined in RFCs 651-658. |
|
| |
| RFC 660 | Some changes to the IMP and the IMP/Host interface |
| |
| Authors: | D.C. Walden. |
| Date: | October 1974 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0660 |
|
Decoupling of message number sequences of hosts; host-host access control; message number window; messages outside normal mechanism; see also BBN 1822. |
|
| |
| RFC 661 | Protocol information |
| |
|
| |
| RFC 662 | Performance improvement in ARPANET file transfers from Multics |
| |
| Authors: | R. Kanodia. |
| Date: | November 1974 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0662 |
|
Experimenting with host output buffers to improve throughput. |
|
| |
| RFC 663 | Lost message detection and recovery protocol |
| |
| Authors: | R. Kanodia. |
| Date: | November 1974 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0663 |
|
Proposed extension of host-host protocol; see also RFCs 534, 516, 512, 492 and 467. |
|
| |
| RFC 666 | Specification of the Unified User-Level Protocol |
| |
| Authors: | M.A. Padlipsky. |
| Date: | November 1974 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0666 |
|
|
|
| |
| RFC 667 | Host Ports |
| |
|
| |
| RFC 669 | November, 1974, survey of New-Protocol Telnet servers |
| |
|
|
An earlier poll of Telnet server implementation status. Updates RFC 702; see also RFCs 703 and 679. |
|
| |
| RFC 671 | Note on Reconnection Protocol |
| |
|
| |
| RFC 672 | Multi-site data collection facility |
| |
| Authors: | R. Schantz. |
| Date: | December 1974 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0672 |
|
Applicability of TIP/TENEX protocols beyond TIP accounting. |
|
| |
| RFC 674 | Procedure call documents: Version 2 |
| |
| Authors: | J. Postel, J.E. White. |
| Date: | December 1974 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0674 |
|
Host level protocol used in the NSW--a slightly constrained version of ARPANET Host-to-Host protocol, affecting allocation, RFNM wait, and retransmission; see also RFC 684. |
|
| |
| RFC 677 | Maintenance of duplicate databases |
| |
| Authors: | P.R. Johnson, R. Thomas. |
| Date: | January 1975 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0677 |
|
|
|
| |
| RFC 678 | Standard file formats |
| |
| Authors: | J. Postel. |
| Date: | December 1974 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0678 |
|
For transmission of documents across different environments. |
|
| |
| RFC 679 | February, 1975, survey of New-Protocol Telnet servers |
| |
|
| |
| RFC 680 | Message Transmission Protocol |
| |
|
| |
| RFC 681 | Network UNIX |
| |
| Authors: | S. Holmgren. |
| Date: | March 1975 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0681 |
|
Capabilities as an ARPANET Mini-Host: standard I/O, Telnet, NCP, Hardware/Software requirements, reliability, availability. |
|
| |
| RFC 683 | FTPSRV - Tenex extension for paged files |
| |
|
|
Defines an extension to FTP for page-mode transfers between TENEX systems; also discusses file transfer reliability. |
|
| |
| RFC 684 | Commentary on procedure calling as a network protocol |
| |
|
|
Issues in designing distributed computing systems. Shortcomings of RFC 674; see also RFCs 542 and 354. |
|
| |
| RFC 685 | Response time in cross network debugging |
| |
|
|
The contribution of ARPANET communication to response time. |
|
| |
| RFC 686 | Leaving well enough alone |
| |
|
|
Discusses difference between early and later versions of FTP; see also RFCs 691, 640, 630, 542, 454, 448, 414, 385 and 354. |
|
| |
| 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 688 | Tentative schedule for the new Telnet implementation for the TIP |
| |
|
| |
| RFC 689 | Tenex NCP finite state machine for connections |
| |
|
|
Describes the internal states of an NCP connection in the TENEX implementation. |
|
| |
| RFC 690 | Comments on the proposed Host/IMP Protocol changes |
| |
|
|
Comments on suggestions in RFC 687; see also RFCs 692 and 696. |
|
| |
| RFC 691 | One more try on the FTP |
| |
|
|
Slight revision of RFC 686, on the subject of print files; see also RFCs 640, 630, 542, 454, 448, 414, 385 and 354. |
|
| |
| RFC 692 | Comments on IMP/Host Protocol changes (RFCs 687 and 690) |
| |
|
|
A proposed solution to the problem of combined length of IMP and Host leaders; see also RFCs 696, 690 and 687. |
|
| |
| RFC 694 | Protocol information |
| |
|
| |
| RFC 695 | Official change in Host-Host Protocol |
| |
| Authors: | M. Krilanovich. |
| Date: | July 1975 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0695 |
|
Corrects ambiguity concerning the ERR command; changes NIC 8246 and NIC 7104. |
|
| |
| RFC 696 | Comments on the IMP/Host and Host/IMP Protocol changes |
| |
|
| |
| RFC 697 | CWD command of FTP |
| |
|
|
Discusses FTP login access to "files only" directories. |
|
| |
| RFC 701 | August, 1974, survey of New-Protocol Telnet servers |
| |
|
| |
| RFC 702 | September, 1974, survey of New-Protocol Telnet servers |
| |
|
| |
| RFC 703 | July, 1975, survey of New-Protocol Telnet Servers |
| |
|
| |
| RFC 704 | IMP/Host and Host/IMP Protocol change |
| |
|
| |
| RFC 705 | Front-end Protocol B6700 version |
| |
| Authors: | R.F. Bryan. |
| Date: | November 1975 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0705 |
|
|
|
| |
| RFC 706 | On the junk mail problem |
| |
| Authors: | J. Postel. |
| Date: | November 1975 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0706 |
|
|
|
| |
| RFC 707 | High-level framework for network-based resource sharing |
| |
| Authors: | J.E. White. |
| Date: | December 1975 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0707 |
|
|
|
| |
| RFC 708 | Elements of a Distributed Programming System |
| |
| Authors: | J.E. White. |
| Date: | January 1976 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0708 |
|
|
|
| |
| RFC 712 | Distributed Capability Computing System (DCCS) |
| |
|
| |
| RFC 713 | MSDTP-Message Services Data Transmission Protocol |
| |
|
| |
| RFC 714 | Host-Host Protocol for an ARPANET-Type Network |
| |
|
| |
| RFC 716 | Interim Revision to Appendix F of BBN 1822 |
| |
| Authors: | D.C. Walden, J. Levin. |
| Date: | May 1976 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0716 |
|
|
|
| |
| RFC 718 | Comments on RCTE from the Tenex Implementation Experience |
| |
|
| |
| RFC 719 | Discussion on RCTE |
| |
|
| |
| RFC 720 | Address Specification Syntax for Network Mail |
| |
| Authors: | D. Crocker. |
| Date: | August 1976 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0720 |
|
|
|
| |
| RFC 722 | Thoughts on Interactions in Distributed Services |
| |
| Authors: | J. Haverty. |
| Date: | September 1976 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0722 |
|
|
|
| |
| 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 json html |
| Obsoleted by: | RFC 0733 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0724 |
|
|
|
| |
| RFC 725 | RJE protocol for a resource sharing network |
| |
| Authors: | J.D. Day, G.R. Grossman. |
| Date: | March 1977 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0725 |
|
|
|
| |
| RFC 728 | Minor pitfall in the Telnet Protocol |
| |
|
| |
| RFC 729 | Telnet byte macro option |
| |
|
| |
| RFC 730 | Extensible field addressing |
| |
|
| |
| RFC 731 | Telnet Data Entry Terminal option |
| |
|
| |
| RFC 732 | Telnet Data Entry Terminal option |
| |
|
| |
| 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 html json |
| Obsoletes: | RFC 0724 |
| Obsoleted by: | RFC 0822 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0733 |
|
|
|
| |
| RFC 737 | FTP extension: XSEN |
| |
| Authors: | K. Harrenstien. |
| Date: | October 1977 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0737 |
|
|
|
| |
| RFC 738 | Time server |
| |
| Authors: | K. Harrenstien. |
| Date: | October 1977 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0738 |
|
|
|
| |
| RFC 741 | Specifications for the Network Voice Protocol (NVP) |
| |
| Authors: | D. Cohen. |
| Date: | November 1977 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0741 |
|
|
|
| |
| RFC 742 | NAME/FINGER Protocol |
| |
|
| |
| RFC 743 | FTP extension: XRSQ/XRCP |
| |
| Authors: | K. Harrenstien. |
| Date: | December 1977 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0743 |
|
|
|
| |
| RFC 744 | MARS - a Message Archiving and Retrieval Service |
| |
| Authors: | J. Sattley. |
| Date: | January 1978 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0744 |
|
|
|
| |
| RFC 745 | JANUS interface specifications |
| |
|
| |
| RFC 746 | SUPDUP graphics extension |
| |
| Authors: | R. Stallman. |
| Date: | March 1978 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0746 |
|
|
|
| |
| RFC 747 | Recent extensions to the SUPDUP Protocol |
| |
| Authors: | M.R. Crispin. |
| Date: | March 1978 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0747 |
|
|
|
| |
| RFC 748 | Telnet randomly-lose option |
| |
| Authors: | M.R. Crispin. |
| Date: | 1 April 1978 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0748 |
|
|
|
| |
| RFC 751 | Survey of FTP mail and MLFL |
| |
| Authors: | P.D. Lebling. |
| Date: | December 1978 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0751 |
|
|
|
| |
| RFC 752 | Universal host table |
| |
| Authors: | M.R. Crispin. |
| Date: | January 1979 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0752 |
|
|
|
| |
| RFC 753 | Internet Message Protocol |
| |
|
| |
| RFC 754 | Out-of-net host addresses for mail |
| |
|
| |
| RFC 756 | NIC name server - a datagram-based information utility |
| |
| Authors: | J.R. Pickens, E.J. Feinler, J.E. Mathis. |
| Date: | July 1979 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0756 |
|
|
|
| |
| RFC 757 | Suggested solution to the naming, addressing, and delivery problem for ARPANET message systems |
| |
| Authors: | D.P. Deutsch. |
| Date: | September 1979 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0757 |
|
|
|
| |
| RFC 760 | DoD standard Internet Protocol |
| |
|
| |
| RFC 763 | Role mailboxes |
| |
|
| |
| RFC 764 | Telnet Protocol specification |
| |
|
| |
| RFC 765 | File Transfer Protocol specification |
| |
|
| |
| RFC 766 | Internet Protocol Handbook: Table of contents |
| |
|
| |
| RFC 767 | Structured format for transmission of multi-media documents |
| |
|
| |
| RFC 769 | Rapicom 450 facsimile file format |
| |
| Authors: | J. Postel. |
| Date: | September 1980 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0769 |
|
|
|
| |
| RFC 771 | Mail transition plan |
| |
| Authors: | V.G. Cerf, J. Postel. |
| Date: | September 1980 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0771 |
|
|
|
| |
| RFC 772 | Mail Transfer Protocol |
| |
|
| |
| RFC 773 | Comments on NCP/TCP mail service transition strategy |
| |
| Authors: | V.G. Cerf. |
| Date: | October 1980 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0773 |
|
|
|
| |
| RFC 774 | Internet Protocol Handbook: Table of contents |
| |
|
| |
| RFC 775 | Directory oriented FTP commands |
| |
| Authors: | D. Mankins, D. Franklin, A.D. Owen. |
| Date: | December 1980 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0775 |
|
|
|
| |
| RFC 777 | Internet Control Message Protocol |
| |
|
| |
| RFC 780 | Mail Transfer Protocol |
| |
|
| |
| RFC 781 | Specification of the Internet Protocol (IP) timestamp option |
| |
|
| |
| RFC 782 | Virtual Terminal management model |
| |
| Authors: | J. Nabielsky, A.P. Skelton. |
| Date: | January 1981 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0782 |
|
|
|
| |
| RFC 783 | TFTP Protocol (revision 2) |
| |
|
| |
| RFC 784 | Mail Transfer Protocol: ISI TOPS20 implementation |
| |
| Authors: | S. Sluizer, J. Postel. |
| Date: | July 1981 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0784 |
|
|
|
| |
| RFC 785 | Mail Transfer Protocol: ISI TOPS20 file definitions |
| |
| Authors: | S. Sluizer, J. Postel. |
| Date: | July 1981 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0785 |
|
|
|
| |
| RFC 786 | Mail Transfer Protocol: ISI TOPS20 MTP-NIMAIL interface |
| |
| Authors: | S. Sluizer, J. Postel. |
| Date: | July 1981 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0786 |
|
|
|
| |
| RFC 787 | Connectionless data transmission survey/tutorial |
| |
|
| |
| RFC 788 | Simple Mail Transfer Protocol |
| |
|
| |
| RFC 789 | Vulnerabilities of network control protocols: An example |
| |
|
| |
| RFC 797 | Format for Bitmap files |
| |
| Authors: | A.R. Katz. |
| Date: | September 1981 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0797 |
|
|
|
| |
| RFC 798 | Decoding facsimile data from the Rapicom 450 |
| |
| Authors: | A.R. Katz. |
| Date: | September 1981 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0798 |
|
|
|
| |
| RFC 799 | Internet name domains |
| |
| Authors: | D.L. Mills. |
| Date: | September 1981 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0799 |
|
|
|
| |
| RFC 801 | NCP/TCP transition plan |
| |
| Authors: | J. Postel. |
| Date: | November 1981 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0801 |
|
This RFC discusses the conversion of hosts from NCP to TCP. And making available the principle services: Telnet, File Transfer, and Mail. These protocols allow all hosts in the ARPA community to share a common interprocess communication environment. |
|
| |
| RFC 802 | ARPANET 1822L Host Access Protocol |
| |
|
|
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 803 | Dacom 450/500 facsimile data transcoding |
| |
| Authors: | A. Agarwal, M.J. O'Connor, D.L. Mills. |
| Date: | November 1981 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0803 |
|
The first part of this RFC describes in detail the Dacom 450 data compression algorithms and is an update and correction to an earlier memorandum. The second part of this RFC describes briefly the Dacom 500 data compression algorithm as used by the INTELPOST electronic-mail network under development by the US Postal Service and several foreign administrators. |
|
| |
| RFC 804 | CCITT draft recommendation T.4 |
| |
| Authors: | International Telegraph and Telephone Consultative Committee of the International Telecommunication Union. |
| Date: | January 1981 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0804 |
|
This is the CCITT standard for group 3 facsimile encoding. This is useful for data compression of bit map data. |
|
| |
| RFC 805 | Computer mail meeting notes |
| |
| Authors: | J. Postel. |
| Date: | February 1982 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0805 |
|
This RFC consists of notes from a meeting that was held at USC Information Sciences Institute on 11 January 1982, to discuss addressing issues in computer mail. The major conclusion reached at the meeting is to extend the "username@hostname" mailbox format to "username@host.domain", where the domain itself can be further strutured. |
|
| |
| 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 html json |
| Obsoleted by: | RFC 0841 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0806 |
|
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 807 | Multimedia mail meeting notes |
| |
| Authors: | J. Postel. |
| Date: | February 1982 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0807 |
|
This RFC consists of notes from a meeting held at USC Information Sciences Institute on the 12th of January to discuss common interests in multimedia computer mail issues and to agree on some specific initial experiments. |
|
| |
| RFC 808 | Summary of computer mail services meeting held at BBN on 10 January 1979 |
| |
|
|
This RFC is a very belated attempt to document a meeting that was held three years earlier to discuss the state of computer mail in the ARPA community and to reach some conclusions to guide the further development of computer mail systems such that a coherent total mail service would continue to be provided. |
|
| |
| RFC 809 | UCL facsimile system |
| |
| Authors: | T. Chang. |
| Date: | February 1982 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0809 |
|
This RFC describes the features of the computerised facsimile system developed in the Department of Computer Science at UCL. First its functions are considered and the related experimental work are reported. Then the disciplines for system design are discussed. Finally, the implementation of the system are described, while detailed description are given as appendices. |
|
| |
| RFC 810 | DoD Internet host table specification |
| |
|
|
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 json html |
| Obsoleted by: | RFC 0953 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0811 |
|
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 |
| |
|
|
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 815 | IP datagram reassembly algorithms |
| |
|
|
This RFC describes an alternate approach of dealing with reassembly which reduces the bookkeeping problem to a minimum, and requires only one buffer for storage equal in size to the final datagram being reassembled, which can reassemble a datagram from any number of fragments arriving in any order with any possible pattern of overlap and duplication, and which is appropriate for almost any sort of operating system. |
|
| |
| RFC 819 | The Domain Naming Convention for Internet User Applications |
| |
| Authors: | Z. Su, J. Postel. |
| Date: | August 1982 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0819 |
|
This RFC is an attempt to clarify the generalization of the Domain Naming Convention, the Internet Naming Convention, and to explore the implications of its adoption for Internet name service and user applications. |
|
| |
| RFC 824 | CRONUS Virtual Local Network |
| |
| Authors: | W.I. MacGregor, D.C. Tappan. |
| Date: | August 1982 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0824 |
|
The purpose of this note is to describe the CRONUS Virtual Local Network, especially the addressing related features. These features include a method for mapping between Internet Addresses and Local Network addresses. This is a topic of current concern in the ARPA Internet community. This note is intended to stimulate discussion. This is not a specification of an Internet Standard. |
|
| |
| 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 827 | Exterior Gateway Protocol (EGP) |
| |
|
|
This RFC is proposed to establish a standard for Gateway to Gateway procedures that allow the Gateways to be mutually suspicious. This document is a DRAFT for that standard. Your comments are strongly encouraged. |
|
| |
| RFC 828 | Data communications: IFIP's international "network" of experts |
| |
|
|
This RFC is distributed to inform the ARPA Internet community of the activities of the IFIP technical committee on Data Communications, and to encourage participation in those activities. |
|
| |
| RFC 829 | Packet satellite technology reference sources |
| |
| Authors: | V.G. Cerf. |
| Date: | November 1982 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0829 |
|
This RFC describes briefly the packet satellite technology developed by the Defense Advanced Research Projects Agency and several other participating organizations in the U.K. and Norway and provides a bibliography of relevant papers for researchers interested in experimental and operational experience with this dynamic satellite-sharing technique. |
|
| |
| RFC 830 | Distributed system for Internet name service |
| |
|
|
This RFC proposes a distributed name service for DARPA Internet. Its purpose is to focus discussion on the subject. It is hoped that a general consensus will emerge leading eventually to the adoption of standards. |
|
| |
| RFC 831 | Backup access to the European side of SATNET |
| |
| Authors: | R.T. Braden. |
| Date: | December 1982 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0831 |
|
The purpose of this RFC is to focus discussion on a particular Internet problem: a backup path for software maintenance of the European sector of the Internet, for use when SATNET is partitioned. We propose a mechanism, based upon the Source Routing option of IP, to reach European Internet sites via the VAN Gateway and UCL. This proposal is not intended as a standard at this time. |
|
| |
| RFC 832 | Who talks TCP? |
| |
|
|
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? |
| |
|
|
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? |
| |
|
|
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? |
| |
|
|
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? |
| |
|
|
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? |
| |
|
|
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? |
| |
|
|
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? |
| |
|
|
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 841 | Specification for message format for Computer Based Message Systems |
| |
|
|
This RFC is FIPS 98. The purpose of distributing this document as an RFC is to make it easily accessible to the ARPA research community. This RFC does not specify a standard for the ARPA Internet. Obsoletes RFC 806. |
|
| |
| RFC 842 | Who talks TCP? - survey of 1 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 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 844 | Who talks ICMP, too? - Survey of 18 February 1983 |
| |
|
|
This survey determines how many hosts are able to respond to TELENET connections from a user at a class C site. This requires, in addition to IP and TCP, participation in gateway routing via ICMP and handling of Class C addresses. The list of hosts was taken from RFC 843, extracting only those hosts which are listed there as accepting TELNET connection. The tests were run on 18-Feb-83. |
|
| |
| RFC 845 | Who talks TCP? - survey of 15 February 1983 |
| |
|
|
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 |
| |
|
|
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 847 | Summary of Smallberg surveys |
| |
| Authors: | A. Westine, D. Smallberg, J. Postel. |
| Date: | February 1983 |
| Formats: | txt json html |
| Obsoletes: | RFC 0846 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0847 |
|
This is a summary of the surveys of Telnet, FTP and Mail (SMTP) servers conducted by David Smallberg in December 1982, January and February 1983 as reported in RFC 832-843, 845-846. This memo extracts the number of hosts that accepted the connection to their server for each of Telnet, FTP, and SMTP, and compares it to the total host in the Internet (not counting TACs or ECHOS). |
|
| |
| RFC 848 | Who provides the "little" TCP services? |
| |
| Authors: | D. Smallberg. |
| Date: | March 1983 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0848 |
|
This RFC lists those hosts which provide any of these "little" TCP services: The list of hosts were taken from the NIC hostname table of 24-Feb-83. The tests were run on February 23 and 24, and March 3 and 5 from ISI-VAXA.ARPA. |
|
| |
| RFC 849 | Suggestions for improved host table distribution |
| |
|
|
This RFC actually is a request for comments. The issue dealt with is that of a naming registry update procedure, both as exists currently and what could exist in the future. None of the proposed solutions are intended as standards at this time; rather it is hoped that a general consensus will emerge as the appropriate solution, leaving eventually to the adoption of standards. |
|
| |
| RFC 850 | Standard for interchange of USENET messages |
| |
|
|
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 852 | ARPANET short blocking feature |
| |
|
|
This RFC specifies the ARPANET Short Blocking Feature, which will allow ARPANET hosts to optionally shorten the IMP's host blocking timer. This Feature is a replacement of the ARPANET non-blocking host interface, which was never implemented, and will be available to hosts using either the 1822 or 1822L Host Access Protocol. This RFC is also being presented as a solicitation of comments on the Short Blocking Feature, especially from host network software implementers and maintainers. |
|
| |
| RFC 871 | Perspective on the ARPANET reference model |
| |
| Authors: | M.A. Padlipsky. |
| Date: | September 1982 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0871 |
|
This RFC is primarily intended as a perspective on the ARM and points out some of the differences between the ARM and the ISORM which were expressed by members in NWG general meetings, NWG protocol design committee meetings, the ARPA Internet Working Group, and private conversations over the intervening years. Originally published as M82-47 by the MITRE Corporation, Bedford, Massachusetts. |
|
| |
| RFC 873 | Illusion of vendor support |
| |
| Authors: | M.A. Padlipsky. |
| Date: | September 1982 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0873 |
|
This memo takes issue with the claim that international standards in computer protocols presently provide a basis for low cost vendor supported protocol implementations. Originally published as M82-49 by the MITRE Corporation, Bedford, Massachusetts. |
|
| |
| RFC 874 | Critique of X.25 |
| |
| Authors: | M.A. Padlipsky. |
| Date: | September 1982 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0874 |
|
This RFC is an analysis of X.25 pointing out some problems in the conceptual model, particularly the conflict between the interface aspects and the end-to-end aspects. The memo also touches on security, and implementation issues. Originally published as M82-50 by the MITRE Corporation, Bedford, Massachusetts. |
|
| |
| RFC 875 | Gateways, architectures, and heffalumps |
| |
| Authors: | M.A. Padlipsky. |
| Date: | September 1982 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0875 |
|
This RFC is a discussion about the role of gateways in an internetwork, especially the problems of translating or mapping protocols between different protocol suites. The discussion notes possible functionality mis-matches, undesirable routing "singularity points", flow control issues, and high cost of translating gateways. Originally published as M82-51 by the MITRE Corporation, Bedford, Massachusetts. |
|
| |
| RFC 876 | Survey of SMTP implementations |
| |
| Authors: | D. Smallberg. |
| Date: | September 1983 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0876 |
|
This RFC is a survey of implementation status. It does not specify an official protocol, but rather notes the status of implementation of aspects of a protocol. It is expected that the status of the hosts reported on will change. This information must be treated as a snapshot of the state of these implemetations. |
|
| |
| RFC 877 | Standard for the transmission of IP datagrams over public data networks |
| |
|
|
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 878 | 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. The 1822L procedure allows ARPANET hosts to use logical identifiers as well as 1822 physical interface identifiers to address each other. |
|
| |
| RFC 881 | Domain names plan and schedule |
| |
|
|
This RFC outlines a plan and schedule for the implementation of domain style names throughout the DDN/ARPA Internet community. The introduction of domain style names will impact all hosts on the DDN/ARPA Internet. |
|
| |
| 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 |
| |
|
|
This RFC specifies a standard for the ARPA Internet community. It specifies a method for exchanging terminal type information in the Telnet protocol. |
|
| |
| RFC 886 | Proposed standard for message header munging |
| |
| Authors: | M.T. Rose. |
| Date: | December 1983 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0886 |
|
This RFC specifies a draft standard for the ARPA Internet community. It describes the rules to be used when transforming mail from the conventions of one message system to those of another message system. In particular, the treatment of header fields, and recipient addresses is specified. |
|
| |
| RFC 888 | "STUB" Exterior Gateway Protocol |
| |
|
|
This RFC describes the Exterior Gateway Protocol used to connect Stub Gateways to an Autonomous System of core Gateways. This document specifies the working protocol, and defines an ARPA official protocol. All implementers of Gateways should carefully review this document. |
|
| |
| RFC 890 | Exterior Gateway Protocol implementation schedule |
| |
| Authors: | J. Postel. |
| Date: | February 1984 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0890 |
|
This memo is a policy statement on the implementation of the Exterior Gateway Protocol in the Internet. This is an official policy statement of ICCB and DARPA. After 1-Aug-84 there shall be no dumb gateways in the Internet. Every gateway must be a member of some autonomous system. Some gateway of each autonomous system must exchange routing information with some gateway of the core autonomous system using the Exterior Gateway Protocol. |
|
| |
| RFC 892 | ISO Transport Protocol specification |
| |
| Authors: | International Organization for Standardization. |
| Date: | December 1983 |
| Formats: | txt json html |
| Obsoleted by: | RFC 0905 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0892 |
|
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 893 | Trailer encapsulations |
| |
| Authors: | S. Leffler, M.J. Karels. |
| Date: | April 1984 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0893 |
|
This RFC discusses the motivation for use of "trailer encapsulations" on local-area networks and describes the implementation of such an encapsulation on various media. This document is for information only. This is NOT an official protocol for the ARPA Internet community. |
|
| |
| RFC 897 | Domain name system implementation schedule |
| |
|
|
This memo is a policy statement on the implementation of the Domain Style Naming System in the Internet. This memo is a partial update of RFC 881. The intent of this memo is to detail the schedule for the implementation for the Domain Style Naming System. The names of hosts will be changed to domain style names. Hosts will begin to use domain style names on 14-Mar-84, and the use of old style names will be completely phased out before 2-May-84. This applies to both the ARPA research hosts and the DDN operational hosts. This is an official policy statement of the ICCB and the DARPA. |
|
| |
| RFC 898 | Gateway special interest group meeting notes |
| |
| Authors: | R.M. Hinden, J. Postel, M. Muuss, J.K. Reynolds. |
| Date: | April 1984 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0898 |
|
This memo is a report on the Gateway Special Interest Group Meeting that was held at ISI on 28 and 29 February 1984. Robert Hinden of BBNCC chaired, and Jon Postel of ISI hosted the meeting. Approximately 35 gateway designers and implementors attended. These notes are based on the recollections of Jon Postel and Mike Muuss. Under each topic area are Jon Postel's brief notes, and additional details from Mike Muuss. This memo is a report on a meeting. No conclusions, decisions, or policy statements are documented in this note. |
|
| |
| RFC 901 | Official ARPA-Internet protocols |
| |
|
|
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 902 | ARPA Internet Protocol policy |
| |
| Authors: | J.K. Reynolds, J. Postel. |
| Date: | July 1984 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0902 |
|
The purpose of this memo is to explain how protocol standards are adopted for the ARPA-Internet and the DARPA research community. There are three important aspects to be discussed: the process, the authority, and the complex relationship between the DARPA community and the DDN community. This memo is a policy statement on how protocols become official standards for the ARPA-Internet and the DARPA research community. This is an official policy statement of the ICCB and the DARPA. |
|
| |
| RFC 905 | ISO Transport Protocol specification ISO DP 8073 |
| |
|
|
This is the current specification of the ISO Transport Protocol. This document is the text of ISO/TC97/SC16/N1576 as corrected by ISO/TC97/SC16/N1695. This is the specification currently being voted on in ISO as a Draft International Standard (DIS). This document is distributed as an RFC for your information only, it does not specify a standard for the ARPA-Internet or DARPA research community. Our thanks to Alex McKenzie of BBN for making this online version available. Please note the size of this document, the file contains 258,729 characters. |
|
| |
| RFC 906 | Bootstrap loading using TFTP |
| |
| Authors: | R. Finlayson. |
| Date: | June 1984 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0906 |
|
It is often convenient to be able to bootstrap a computer system from a communications network. This RFC proposes the use of the IP TFTP protocol for bootstrap loading in this case. |
|
| |
| RFC 910 | Multimedia mail meeting notes |
| |
| Authors: | H.C. Forsdick. |
| Date: | August 1984 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0910 |
|
This memo is a report on a meeting about the experimental multimedia mail system (and in a sense a status report on that experiment). The meeting was held at Bolt Beranek and Newman on 23-24 July 1984 to discuss recent progress by groups who are building multimedia mail systems and to discuss a variety of issues related to the further development of multimedia systems. Representatives were present from BBN, ISI, SRI and Linkabit. |
|
| |
| RFC 911 | EGP Gateway under Berkeley UNIX 4.2 |
| |
|
|
This memo describes an implementation of the Exterior Gateway Protocol (EGP) (in that sense it is a status report). The memo also discusses some possible extentions and some design issues (in that sense it is an invitation for further discussion). |
|
| |
| RFC 912 | Authentication service |
| |
|
|
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 915 | Network mail path service |
| |
| Authors: | M.A. Elvy, R. Nedved. |
| Date: | December 1984 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0915 |
|
This RFC proposed a new service for the ARPA-Internet community and requests discussion and suggestions for improvements. The network mail path service fills the current need of people to determine mailbox addresses for hosts that are not part of the ARPA-Internet but can be reached by one or more relay hosts that have Unix to Unix Copy (UUCP) mail, CSNET mail, MAILNET mail, BITNET mail, etc. Anyone can use the service if they have TCP/TELENET to one of the hosts with a mail path server. |
|
| |
| RFC 917 | Internet subnets |
| |
| Authors: | J.C. Mogul. |
| Date: | October 1984 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0917 |
|
This memo discusses subnets and proposes procedures for the use of subnets, including approaches to solving the problems that arise, particularly that of routing. A subnet of an Internet network is a logically visible sub-section of a single Internet network. For administrative or technical reasons, many organizations have chosen to divide one Internet network into several subnets, instead of acquiring a set of Internet network numbers. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 918 | Post Office Protocol |
| |
|
|
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 920 | Domain requirements |
| |
| Authors: | J. Postel, J.K. Reynolds. |
| Date: | October 1984 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0920 |
|
This memo states the requirements on establishing a Domain, and introduces the limited set of top level domains. This memo is a policy statement on the requirements of establishing a new domain in the ARPA-Internet and the DARPA research community. This is an official policy statement of the IAB and the DARPA. |
|
| |
| RFC 921 | Domain name system implementation schedule - revised |
| |
|
|
This memo is a policy statement on the implementation of the Domain Style Naming System in the Internet. This memo is an update of RFC-881, and RFC-897. This is an official policy statement of the IAB and the DARPA. The intent of this memo is to detail the schedule for the implementation for the Domain Style Naming System. The explanation of how this system works is to be found in the references. |
|
| |
| RFC 924 | Official ARPA-Internet protocols for connecting personal computers to the Internet |
| |
|
|
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 925 | Multi-LAN address resolution |
| |
| Authors: | J. Postel. |
| Date: | October 1984 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0925 |
|
The problem of treating a set of local area networks (LANs) as one Internet network has generated some interest and concern. It is inappropriate to give each LAN within an site a distinct Internet network number. It is desirable to hide the details of the interconnections between the LANs within an site from people, gateways, and hosts outside the site. The question arises on how to best do this, and even how to do it at all. In RFC-917 Jeffery Mogul makes a case for the use of "explicit subnets" in a multi-LAN environment. The explicit subnet scheme is a call to recursively apply the mechanisms the Internet uses to manage networks to the problem of managing LANs within one network. In this note I urge another approach: the use of "transparent subnets" supported by a multi-LAN extension of the Address Resolution Protocol. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 926 | Protocol for providing the connectionless mode network services |
| |
| Authors: | International Organization for Standardization. |
| Date: | December 1984 |
| Formats: | txt json html |
| Obsoleted by: | RFC 0994 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0926 |
|
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 928 | Introduction to proposed DoD standard H-FP |
| |
| Authors: | M.A. Padlipsky. |
| Date: | December 1984 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0928 |
|
The broad outline of the Host-Front End Protocol introduced here and described in RFC-929 is the result of the deliberations of a number of experienced H-FP designers, who sat as a committee of the DoD Protocol Standards Technical Panel. It is the intent of the designers that the protocol be subjected to multiple test implementations and probable iteration before being agreed upon as any sort of "standard". Therefore, the first order of business is to declare that THIS IS A PROPOSAL, NOT A FINAL STANDARD, and the second order of business is to request that any readers of these documents who are able to do test implementations (a) do so and (b) coordinate their efforts with the author. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 930 | Telnet terminal type option |
| |
|
|
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 |
| |
|
|
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 932 | Subnetwork addressing scheme |
| |
| Authors: | D.D. Clark. |
| Date: | January 1985 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0932 |
|
This RFC proposes an alternative addressing scheme for subnets which, in most cases, requires no modification to host software whatsoever. The drawbacks of this scheme are that the total number of subnets in any one network are limited, and that modification is required to all gateways. |
|
| |
| RFC 934 | Proposed standard for message encapsulation |
| |
| Authors: | M.T. Rose, E.A. Stefferud. |
| Date: | January 1985 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0934 |
|
This memo concerns itself with message forwarding. Forwarding can be thought of as encapsulating one or more messages inside another. Although this is useful for transfer of past correspondence to new recipients, without a decapsulation process (which this memo terms "bursting"), the forwarded messages are of little use to the recipients because they can not be distributed, forwarded, replied-to, or otherwise processed as separate individual messages. In order to burst a message it is necessary to know how the component messages were encapsulated in the draft. At present there is no unambiguous standard for interest group digests. This RFC proposes a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 935 | Reliable link layer protocols |
| |
| Authors: | J.G. Robinson. |
| Date: | January 1985 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0935 |
|
This RFC discusses protocols proposed recently in RFCs 914 and 916, and suggests a proposed protocol that could meet the same needs addressed in those memos. The stated need is reliable communication between two programs over a full-duplex, point-to-point communication link, and in particular the RFCs address the need for such communication over an asynchronous link at relatively low speeds. The suggested protocol uses the methods of existing national and international data link layer standards. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 936 | Another Internet subnet addressing scheme |
| |
| Authors: | M.J. Karels. |
| Date: | February 1985 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0936 |
|
There have been several proposals for schemes to allow the use of a single Internet network number to refer to a collection of physical networks under common administration which are reachable from the rest of the Internet by a common route. Such schemes allow a simplified view of an otherwise complicated topology from hosts and gateways outside of this collection. They allow the complexity of the number and type of these networks, and routing to them, to be localized. Additions and changes in configuration thus cause no detectable change, and no interruption of service, due to slow propagation of routing and other information outside of the local environment. These schemes also simplify the administration of the network, as changes do not require allocation of new network numbers for each new cable installed. This proposal discusses an alternative scheme, one that has been in use at the University of California, Berkeley since April 1984. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 939 | Executive summary of the NRC report on transport protocols for Department of Defense data networks |
| |
| Authors: | National Research Council. |
| Date: | February 1985 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0939 |
|
This RFC reproduces the material from the "front pages" of the National Research Council report resulting from a study of the DOD Internet Protocol (IP) and Transmission Control Protocol (TCP) in comparison with the ISO Internet Protocol (ISO-IP) and Transport Protocol level 4 (TP-4). The point of this RFC is to make the text of the Executive Summary widely available in a timely way. The order of presentation has been altered, and the pagination changed. This RFC is distributed for information only. This RFC does not establish any policy for the DARPA research community or the DDN operational community. |
|
| |
| RFC 940 | Toward an Internet standard scheme for subnetting |
| |
| Authors: | Gateway Algorithms and Data Structures Task Force. |
| Date: | April 1985 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0940 |
|
Several sites now contain a complex of local links connected to the Internet via a gateway. The details of the internal connectivity are of little interest to the rest of the Internet. One way of organizing these local complexes of links is to use the same strategy as the Internet uses to organize networks, that is, to declare each link to be an entity (like a network) and to interconnect the links with devices that perform routing functions (like gateways). This general scheme is called subnetting, the individual links are called subnets, and the connecting devices are called subgateways (or bridges, or gateways). This RFC discusses standardizing the protocol used in subnetted environments in the ARPA-Internet. |
|
| |
| RFC 941 | Addendum to the network service definition covering network layer addressing |
| |
| Authors: | International Organization for Standardization. |
| Date: | April 1985 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0941 |
|
This Addendum to the Network Service Definition Standard, ISO 8348, defines the abstract syntax and semantics of the Network Address (Network Service Access Point Address). The Network Address defined in this Addendum is the address that appears in the primitives of the connection-mode Network Service as the calling address, called address, and responding address parameters, and in the primitives of the connectionless-mode Network Service as the source address and destination address parameters. This document is distributed as an RFC for information only. It does not specify a standard for the ARPA-Internet. |
|
| |
| RFC 942 | Transport protocols for Department of Defense data networks |
| |
| Authors: | National Research Council. |
| Date: | February 1985 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0942 |
|
This RFC reproduces the National Research Council report resulting from a study of the DoD Internet Protocol (IP) and Transmission Control Protocol (TCP) in comparison with the ISO Internet Protocol (ISO-IP) and Transport Protocol level 4 (TP-4). |
|
| |
| RFC 944 | Official ARPA-Internet protocols |
| |
|
|
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 |
| |
|
|
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 947 | Multi-network broadcasting within the Internet |
| |
| Authors: | K. Lebowitz, D. Mankins. |
| Date: | June 1985 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0947 |
|
This RFC describes the extension of a network's broadcast domain to include more than one physical network through the use of a broadcast packet repeater. |
|
| |
| RFC 948 | Two methods for the transmission of IP datagrams over IEEE 802.3 networks |
| |
|
|
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 949 | FTP unique-named store command |
| |
| Authors: | M.A. Padlipsky. |
| Date: | July 1985 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0949 |
|
There are various contexts in which it would be desirable to have an FTP command that had the effect of the present STOR but rather than requiring the sender to specify a file name istead caused the resultant file to have a unique name relative to the current directory. This RFC proposes an extension to the File Transfer Protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. See RFC-959. |
|
| |
| RFC 952 | DoD Internet host table specification |
| |
|
|
This RFC is the official specification of the format of the Internet Host Table. This edition of the specification includes minor revisions to RFC-810 which brings it up to date. |
|
| |
| RFC 955 | Towards a transport service for transaction processing applications |
| |
| Authors: | R.T. Braden. |
| Date: | September 1985 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0955 |
|
The DoD Internet protocol suite includes two alternative transport service protocols, TCP and UDP, which provide virtual circuit and datagram service, respectively. These two protocols represent points in the space of possible transport service attributes which are quite "far apart". We want to examine an important class of applications, those which perform what is often called "transaction processing". We will see that the communication needs for these applications fall into the gap "between" TCP and UDP -- neither protocol is very appropriate. This RFC is concerned with the possible design of one or more new protocols for the ARPA-Internet, to support kinds of applications which are not well supported at present. The RFC is intended to spur discussion in the Internet research community towards the development of new protocols and/or concepts, in order to meet these unmet application requirements. It does not represent a standard, nor even a concrete protocol proposal. |
|
| |
| RFC 956 | Algorithms for synchronizing network clocks |
| |
| Authors: | D.L. Mills. |
| Date: | September 1985 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0956 |
|
This RFC discussed clock synchronization algorithms for the ARPA-Internet community, and requests discussion and suggestions for improvements. The recent interest within the Internet community in determining accurate time from a set of mutually suspicious network clocks has been prompted by several occasions in which errors were found in usually reliable, accurate clock servers after thunderstorms which disrupted their power supply. To these sources of error should be added those due to malfunctioning hardware, defective software and operator mistakes, as well as random errors in the mechanism used to set and synchronize clocks. This report suggests a stochastic model and algorithms for computing a good estimator from time-offset samples measured between clocks connected via network links. Included in this report are descriptions of certain experiments which give an indication of the effectiveness of the algorithms. |
|
| |
| RFC 957 | Experiments in network clock synchronization |
| |
| Authors: | D.L. Mills. |
| Date: | September 1985 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0957 |
|
This RFC discusses some experiments in clock synchronization in the ARPA-Internet community, and requests discussion and suggestions for improvements. One of the services frequently neglected in computer network design is a high-quality, time-of-day clock capable of generating accurate timestamps with small errors compared to one-way network delays. Such a service would be useful for tracing the progress of complex transactions, synchronizing cached data bases, monitoring network performance and isolating problems. In this memo one such clock service design will be described and its performance assessed. This design has been incorporated as an integral part of the network routing and control protocols of the Distributed Computer Network (DCnet) architecture. |
|
| |
| 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 961 | Official ARPA-Internet protocols |
| |
|
|
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 962 | TCP-4 prime |
| |
| Authors: | M.A. Padlipsky. |
| Date: | November 1985 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0962 |
|
This memo is in response to Bob Braden's call for a transaction oriented protocol (RFC-955), and continues the discussion of a possible transaction oriented transport protocol. This memo does not propose a standard. |
|
| |
| RFC 963 | Some problems with the specification of the Military Standard Internet Protocol |
| |
| Authors: | D.P. Sidhu. |
| Date: | November 1985 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0963 |
|
The purpose of this RFC is to provide helpful information on the Military Standard Internet Protocol (MIL-STD-1777) so that one can obtain a reliable implementation of this protocol. This paper points out several problems in this specification. This note also proposes solutions to these problems. |
|
| |
| RFC 965 | Format for a graphical communication protocol |
| |
| Authors: | L. Aguilar. |
| Date: | December 1985 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0965 |
|
This RFC describes the requirements for a graphical format on which to base a graphical on-line communication protocol, and proposes an Interactive Graphical Communication Format using the GKSM session metafile. We hope this contribution will encourage the discussion of multimedia data exchange and the proposal of solutions. |
|
| |
| RFC 966 | Host groups: A multicast extension to the Internet Protocol |
| |
| Authors: | S.E. Deering, D.R. Cheriton. |
| Date: | December 1985 |
| Formats: | txt html json |
| Obsoleted by: | RFC 0988 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0966 |
|
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 967 | All victims together |
| |
| Authors: | M.A. Padlipsky. |
| Date: | December 1985 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0967 |
|
This RFC proposes a new set of RFCs on how the networking code is integrated with various operating systems. It appears that this topic has not received enough exposure in the literature. Comments and suggestions are encouraged. |
|
| |
| RFC 968 | Twas the night before start-up |
| |
| Authors: | V.G. Cerf. |
| Date: | December 1985 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0968 |
|
This memo discusses problems that arise and debugging techniques used in bringing a new network into operation. |
|
| |
| RFC 969 | NETBLT: A bulk data transfer protocol |
| |
| Authors: | D.D. Clark, M.L. Lambert, L. Zhang. |
| Date: | December 1985 |
| Formats: | txt json html |
| Obsoleted by: | RFC 0998 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0969 |
|
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 970 | On Packet Switches With Infinite Storage |
| |
| Authors: | J. Nagle. |
| Date: | December 1985 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0970 |
|
Most prior work on congestion in datagram systems focuses on buffer management. We find it illuminating to consider the case of a packet switch with infinite storage. Such a packet switch can never run out of buffers. It can, however, still become congested. The meaning of congestion in an infinite-storage system is explored. We demonstrate the unexpected result that a datagram network with infinite storage, first-in-first-out queuing, at least two packet switches, and a finite packet lifetime will, under overload, drop all packets. By attacking the problem of congestion for the infinite-storage case, we discover new solutions applicable to switches with finite storage. |
|
| |
| RFC 971 | Survey of data representation standards |
| |
| Authors: | A.L. DeSchon. |
| Date: | January 1986 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0971 |
|
This RFC is a comparison of several data representation standards that are currently in use. The standards discussed are the CCITT X.409 recommendation, the NBS Computer Based Message System (CBMS) standard, DARPA Multimedia Mail system, the Courier remote procedure call protocol, and the SUN Remote Procedure Call package. No proposals in this document are intended as standards for the ARPA-Internet at this time. Rather, it is hoped that a general consensus will emerge as to the appropriate approach to a data representation standard, leading eventually to the adoption of an ARPA-Internet standard. |
|
| |
| RFC 972 | Password Generator Protocol |
| |
| Authors: | F.J. Wancho. |
| Date: | January 1986 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0972 |
|
This RFC specifies a standard for the ARPA Internet community. The Password Generator Service (PWDGEN) provides a set of six randomly generated eight-character "words" with a reasonable level of pronounceability, using a multi-level algorithm. Hosts on the ARPA Internet that choose to implement a password generator service are expected to adopt and implement this standard. |
|
| |
| 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 975 | Autonomous confederations |
| |
| Authors: | D.L. Mills. |
| Date: | February 1986 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0975 |
|
This RFC proposes enhancements to the Exterior Gateway Protocol (EGP) to support a simple, multiple-level routing capability while preserving the robustness features of the current EGP model. The enhancements generalize the concept of core system to include multiple communities of autonomous systems, called autonomous confederations. Discussion and suggestions for improvement are requested. |
|
| |
| RFC 976 | UUCP mail interchange format standard |
| |
|
|
This document defines the standard format for the transmission of mail messages between computers in the UUCP Project. It does not however, address the format for storage of messages on one machine, nor the lower level transport mechanisms used to get the date from one machine to the next. It represents a standard for conformance by hosts in the UUCP zone. |
|
| |
| RFC 978 | Voice File Interchange Protocol (VFIP) |
| |
| Authors: | J.K. Reynolds, R. Gillman, W.A. Brackenridge, A. Witkowski, J. Postel. |
| Date: | February 1986 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0978 |
|
The purpose of the Voice File Interchange Protocol (VFIP) is to permit the interchange of various types of speech files between different systems in the ARPA-Internet community. Suggestions for improvement are encouraged. |
|
| |
| RFC 979 | PSN End-to-End functional specification |
| |
|
|
This memo is an updated version of BBN Report 5775, "End-to-End Functional Specification and describes important changes to the functionality of the interface between a Host and the PSN, and should be carefully reviewed by anyone involved in supporting a host on either the ARPANET or MILNET". The new End-to-End protocol (EE) is being developed in order to correct a number of deficiencies in the old EE, to improve its performance and overall throughput, and to better equip the Packet Switch Node (PSN, also known as the IMP) to support its current and anticipated host population. |
|
| |
| RFC 980 | Protocol document order information |
| |
| Authors: | O.J. Jacobsen, J. Postel. |
| Date: | March 1986 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0980 |
|
This RFC indicates how to obtain various protocol documents used in the DARPA research community. Included is an overview of the new 1985 DDN Protocol Handbook and available sources for obtaining related documents (such as DOD, ISO, and CCITT). |
|
| |
| RFC 981 | Experimental multiple-path routing algorithm |
| |
|
|
This document introduces wiretap algorithms, which are a class of routing algorithms that compute quasi-optimum routes for stations sharing a broadcast channel, but with some stations hidden from others. The wiretapper observes the paths (source routes) used by other stations sending traffic on the channel and, using a heuristic set of factors and weights, constructs speculative paths for its own traffic. A prototype algorithm, called here the Wiretap Algorithm, has been designed for the AX.25 packet-radio channel. Its design is similar in many respects to the shortest-path-first (spf) algorithm used in the ARPANET and elsewhere, and is in fact a variation in the class of algorithms, including the Viterbi Algorithm, that construct optimum paths on a graph according to a distance computed as a weighted sum of factors assigned to the nodes and edges.
The Wiretap Algorithm differs from conventional algorithms in that it computes not only the primary route (a minimum-distance path), but also additional paths ordered by distance, which serve as alternate routes should the primary route fail. This feature is also useful for the discovery of new paths not previously observed on the channel.
Since the amateur AX.25 packet-radio channel is very active in theWashington, DC, area and carries a good deal of traffic under punishing conditions, it was considered a sufficiently heroic environment for a convincing demonstration of the prototype algorithm. It was implemented as part of an IP/TCP driver for theLSI-11 processor running the "fuzzball" operating system. The driver is connected via serial line to a 6809-based TAPR-1 processor running the WA8DED firmware, which controls the radio equipmnet in both |
|
| |
| RFC 982 | Guidelines for the specification of the structure of the Domain Specific Part (DSP) of the ISO standard NSAP address |
| |
|
|
This RFC is a draft working document of the ANSI "Guidelines for the Specification of the Structure of the Domain Specific Part (DSP) of the ISO Standard NSAP Address". It provides guidance to private address administration authorities on preferred formats and semantics for the Domain Specific Part (DSP) of an NSAP address. This RFC specifies the way in which the DSP may be constructed so as to facilitate efficient address assignment. This RFC is for informational purposes only and its distribution is unlimited and does not specify a standard of the ARPA-Internet. |
|
| |
| RFC 983 | ISO transport arrives on top of the TCP |
| |
|
|
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 |
| |
|
|
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 json html |
| Obsoleted by: | RFC 1009 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0985 |
|
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 |
| |
|
|
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 991 | Official ARPA-Internet protocols |
| |
|
|
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 992 | On communication support for fault tolerant process groups |
| |
| Authors: | K.P. Birman, T.A. Joseph. |
| Date: | November 1986 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0992 |
|
This memo describes a collection of multicast communication primitives integrated with a mechanism for handling process failure and recovery. These primitives facilitate the implementation of fault-tolerant process groups, which can be used to provide distributed services in an environment subject to non-malicious crash failures. |
|
| |
| RFC 993 | PCMAIL: A distributed mail system for personal computers |
| |
|
|
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 994 | Final text of DIS 8473, Protocol for Providing the Connectionless-mode Network Service |
| |
| Authors: | International Organization for Standardization. |
| Date: | March 1986 |
| Formats: | txt json html |
| Obsoletes: | RFC 0926 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0994 |
|
This Protocol Standard is one of a set of International Standards produced to facilitate the interconnection of open systems. The set of standards covers the services and protocols required to achieve such interconnection. This Protocol Standard is positioned with respect to other related standards by the layers defined in the Reference Model for Open Systems Interconnection (ISO 7498). In particular, it is a protocol of the Network Layer. This Protocol may be used between network-entities in end systems or in Network Layer relay systems (or both). It provides the Connectionless-mode Network Service as defined in Addendum 1 to the Network Service Definition Covering Connectionless-mode Transmission (ISO 8348/AD1). |
|
| |
| RFC 995 | End System to Intermediate System Routing Exchange Protocol for use in conjunction with ISO 8473 |
| |
| Authors: | International Organization for Standardization. |
| Date: | April 1986 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 0995 |
|
This Protocol is one of a set of International Standards produced to facilitate the interconnection of open systems. The set of standards covers the services and protocols required to achieve such interconnection. This Protocol is positioned with respect to other related standards by the layers defined in the Reference Model for Open Systems Interconnection (ISO 7498) and by the structure defined in the Internal Organization of the Network Layer (DIS 8648). In particular, it is a protocol of the Network Layer. This Protocol permits End Systems and Intermediate Systems to exchange configuration and routing information to facilitate the operation of the routing and relaying functions of the Network Layer. |
|
| |
| 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 |
| |
|
| |
| RFC 1000 | Request For Comments reference guide |
| |
|
|
This RFC Reference Guide is intended to provide a historical account by categorizing and summarizing of the Request for Comments numbers 1 through 999 issued between the years 1969-1987. These documents have been crossed referenced to indicate which RFCs are current, obsolete, or revised. |
|
| |
| RFC 1003 | Issues in defining an equations representation standard |
| |
|
|
This memo is intended to identify and explore issues in defining a standard for the exchange of mathematical equations. No attempt is made at a complete definition and more questions are asked than are answered. Questions about the user interface are only addressed to the extent that they affect interchange issues. |
|
| |
| RFC 1005 | ARPANET AHIP-E Host Access Protocol (enhanced AHIP) |
| |
| Authors: | A. Khanna, A.G. Malis. |
| Date: | May 1987 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1005 |
|
This RFC is a proposed specification for the encoding of Class A IP addresses for use on ARPANET-style networks such as the Milnet and Arpanet, and for enhancements to the ARPANET AHIP Host Access Protocol (AHIP; formerly known as 1822). These enhancements increase the size of the PSN field, allow ARPANET hosts to use logical names to address each other, allow for the communication of type-of-service information from the host to the PSN and enable the PSN to provide congestion feedback to the host on a connection basis. |
|
| |
| RFC 1007 | Military supplement to the ISO Transport Protocol |
| |
|
|
This document supplements the Transport Service and Protocol of the International Standards Organization (ISO), IS 8072 and IS 8073, respectively, and their formal descriptions by providing conventions, option selections and parameter values. This RFC is being distributed to members of the Internet community in order to solicit comments on the Draft Military Supplement. While this document may not be directly relevant to the research problems of the Internet, it may be of some interest to a number of researchers and implementors. |
|
| |
| RFC 1008 | Implementation guide for the ISO Transport Protocol |
| |
|
|
This RFC is being distributed to members of the Internet community in order to solicit comments on the Implementors Guide. While this document may not be directly relevant to the research problems of the Internet, it may be of some interest to a number of researchers and implementors. |
|
| |
| RFC 1011 | Official Internet protocols |
| |
|
|
This memo is an official status report on the protocols used in the Internet community. It identifies the documents specifying the official protocols used in the Internet. Comments indicate any revisions or changes planned. |
|
| |
| RFC 1013 | X Window System Protocol, version 11: Alpha update April 1987 |
| |
| Authors: | R.W. Scheifler. |
| Date: | June 1987 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1013 |
|
This RFC is distributed to the Internet community for information only. It does not establish an Internet standard. The X window system has been widely reviewed and tested. The Internet community is encouraged to experiment with it. |
|
| |
| RFC 1014 | XDR: External Data Representation standard |
| |
| Authors: | Sun Microsystems. |
| Date: | June 1987 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1014 |
|
XDR is a standard for the description and encoding of data. It is useful for transferring data between different computer architectures. XDR fits into ISO presentation layer, and is roughly analogous in purpose to X.409, ISO Abstract Syntax Notation. The major difference between these two is that XDR uses implicit typing, while X.409 uses explicit typing. This RFC is distributed for information only, it does not establish a Internet standard. |
|
| |
| RFC 1015 | Implementation plan for interagency research Internet |
| |
|
|
This RFC proposes an Interagency Research Internet as the natural outgrowth of the current Internet. This is an "idea paper" and discussion is strongly encouraged. |
|
| |
| RFC 1016 | Something a Host Could Do with Source Quench: The Source Quench Introduced Delay (SQuID) |
| |
| Authors: | W. Prue, J. Postel. |
| Date: | July 1987 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1016 |
|
The memo is intended to explore the issue of what a host could do with a source quench. The proposal is for each source host IP module to introduce some delay between datagrams sent to the same destination host. This is a "crazy idea paper" and discussion is essential. |
|
| |
| RFC 1017 | Network requirements for scientific research: Internet task force on scientific computing |
| |
| Authors: | B.M. Leiner. |
| Date: | August 1987 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1017 |
|
This RFC identifies the requirements on communication networks for supporting scientific research. It proposes some specific areas for near term work, as well as some long term goals. This is an "idea" paper and discussion is strongly encouraged. |
|
| |
| RFC 1018 | Some comments on SQuID |
| |
| Authors: | A.M. McKenzie. |
| Date: | August 1987 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1018 |
|
This memo is a discussion of some of the ideas expressed in RFC-1016 on Source Quench. This memo introduces the distinction of the cause of congestion in a gateway between the effects of "Funneling" and Mismatch". It is offered in the same spirit as RFC-1016; to stimulate discussion. The opinions offered are personal, not corporate, opinions. |
|
| |
| RFC 1019 | Report of the Workshop on Environments for Computational Mathematics |
| |
| Authors: | D. Arnon. |
| Date: | September 1987 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1019 |
|
This memo is a report on the discussion of the representation of equations in a workshop at the ACM SIGGRAPH Conference held in Anaheim, California on 30 July 1987. |
|
| |
| RFC 1020 | Internet numbers |
| |
|
|
This RFC is a list of the Assigned IP Network Numbers and EGP Autonomous System Numbers. This RFC obsoletes RFC-997. |
|
| |
| RFC 1022 | High-level Entity Management Protocol (HEMP) |
| |
| Authors: | C. Partridge, G. Trewitt. |
| Date: | October 1987 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1022 |
|
This memo presents an application protocol for managing network entities such as hosts, gateways, and front end machines. This protocol is a component of the High-level Entity Management System HEMS), described is RFC-1021. This memo also assumes a knowledge of the ISO data encoding standard, ASN.1. |
|
| |
| RFC 1023 | HEMS monitoring and control language |
| |
|
|
This RFC specifies the High-Level Entity Management System (HEMS) Monitoring and Control Language. This language defines the requests and replies used in HEMS. This memo assumes knowledge of the HEMS system described in RFC-1021, and of the ISO data encoding standard, ASN.1. |
|
| |
| RFC 1024 | HEMS variable definitions |
| |
| Authors: | C. Partridge, G. Trewitt. |
| Date: | October 1987 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1024 |
|
This memo assigns instruction codes, defines object formats and object semantics for use with the High-Level Monitoring and Control Language, defined in RFC-1023. A general system has been described in previous memos (RFC-1021, RFC-1022). This system is called the High-Level Entity Management System (HEMS). This memo is provisional and the definitions are subject to change. Readers should confirm with the authors that they have the most recent version. This RFC assumes a working knowledge of the ISO data encoding standard, ASN.1, and a general understanding of the IP protocol suite. |
|
| |
| RFC 1025 | TCP and IP bake off |
| |
| Authors: | J. Postel. |
| Date: | September 1987 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1025 |
|
This memo describes some of the procedures, scoring and tests used in the TCP and IP bake offs held in the early development of these protocols. These procedures and tests may still be of use in testing newly implemented TCP and IP modules. |
|
| |
| RFC 1026 | Addendum to RFC 987: (Mapping between X.400 and RFC-822) |
| |
|
|
This memo suggest a proposed protocol for the Internet community, and request discussion and suggestions for improvements. |
|
| |
| RFC 1027 | Using ARP to implement transparent subnet gateways |
| |
| Authors: | S. Carl-Mitchell, J.S. Quarterman. |
| Date: | October 1987 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1027 |
|
This RFC describes the use of the Address Resolution Protocol (ARP) by subnet gateways to permit hosts on the connected subnets to communicate without being aware of the existence of subnets, using the technique of "Proxy ARP". |
|
| |
| RFC 1029 | More fault tolerant approach to address resolution for a Multi-LAN system of Ethernets |
| |
|
|
This memo discusses an extension to a Bridge Protocol to detect and disclose changes in heighbouring host address parameters in a Multi-Lan system of Ethernets. The problem is one which is appearing more and more regularly as the interconnected systems grow larger on Campuses and in Commercial Institutions. This RFC suggests a protocol enhancement for the Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 1030 | On testing the NETBLT Protocol over divers networks |
| |
| Authors: | M.L. Lambert. |
| Date: | November 1987 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1030 |
|
This memo describes the results gathered from testing NETBLT over three networks of different bandwidths and round-trip delays. The results are not complete, but the information gathered so far has not been promising. The NETBLT protocol is specified in RFC-998; this document assumes an understanding of the specification as described in RFC-998. |
|
| |
| RFC 1031 | MILNET name domain transition |
| |
| Authors: | W.D. Lazear. |
| Date: | November 1987 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1031 |
|
This RFC consolidates information necessary for the implementation of domain style names throughout the DDN/MILNET Internet community. The introduction of domain style names will impact all hosts in the DDN/MILNET Internet. This RFC is designed as an aid to implementors and administrators by providing: 1) an overview of the transition process from host tables to domains, 2) a timetable for the transition, and 3) references to documentation and software relating to the domain system. |
|
| |
| RFC 1032 | Domain administrators guide |
| |
| Authors: | M.K. Stahl. |
| Date: | November 1987 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1032 |
|
Domains are administrative entities that provide decentralized management of host naming and addressing. The domain-naming system is distributed and hierarchical. This memo describes procedures for registering a domain with the Network Information Center (NIC) of Defense Data Network (DDN), and offers guidelines on the establishment and administration of a domain in accordance with the requirements specified in RFC-920. It is recommended that the guidelines described in this document be used by domain administrators in the establishment and control of second-level domains. The role of the domain administrator (DA) is that of coordinator, manager, and technician. If his domain is established at the second level or lower in the tree, the domain administrator must register by interacting with the management of the domain directly above this. |
|
| |
| RFC 1033 | Domain Administrators Operations Guide |
| |
| Authors: | M. Lottor. |
| Date: | November 1987 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1033 |
|
This RFC provides guidelines for domain administrators in operating a domain server and maintaining their portion of the hierarchical database. Familiarity with the domain system is assumed (see RFCs 1031, 1032, 1034, and 1035). |
|
| |
| RFC 1036 | Standard for interchange of USENET messages |
| |
|
|
This RFC defines the standard format for the interchange of network News messages among USENET hosts. It updates and replaces RFC-850, reflecting version B2.11 of the News program. This memo is distributed as an RFC to make this information easily accessible to the Internet community. It does not specify an Internet standard. |
|
| |
| RFC 1038 | Draft revised IP security option |
| |
|
|
This memo is a pre-publication draft of the revised Internet Protocol Security Option. This RFC reflects the version as approved by the Protocol Standards Steering group, and is provided for informational purposes only. The final version of this document will be available from Navy publications and should not differ from this document in any major fashion. This document will be published as a change to the MIL- STD 1777, "Internet Protocol". |
|
| |
| RFC 1039 | DoD statement on Open Systems Interconnection protocols |
| |
|
|
This RFC reproduces a memorandum issued on 2-JUL-87 from the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASDC31) to the Director of the Defense Communications Agency (DCA). This memo is distributed for information only. |
|
| |
| RFC 1040 | Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures |
| |
|
|
This RFC is the Outgrowth of a series of IAB Privacy Task Force meetings and of internal working papers distributed for those meetings. This memo defines message encipherment and authentication procedures, as the initial phase of an effort to provide privacy enhancement services for electronic mail transfer in the Internet. Detailed key management mechanisms to support these procedures will be defined in a subsequent RFC. As a goal of this initial phase, it is intended that the procedures defined here be compatible with a wide range of key management approaches, including both conventional (symmetric) and public-key (asymmetric) approaches for encryption of data encrypting keys. Use of conventional cryptography for message text encryption and/or integrity check computation is anticipated. |
|
| |
| RFC 1046 | Queuing algorithm to provide type-of-service for IP links |
| |
| Authors: | W. Prue, J. Postel. |
| Date: | February 1988 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1046 |
|
This memo is intended to explore how Type-of-Service might be implemented in the Internet. The proposal describes a method of queuing which can provide the different classes of service. The technique also prohibits one class of service from consuming excessive resources or excluding other classes of service. This is an "idea paper" and discussion is strongly encouraged. |
|
| |
| RFC 1047 | Duplicate messages and SMTP |
| |
| Authors: | C. Partridge. |
| Date: | February 1988 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1047 |
|
An examination of a synchronization problem in the Simple Mail Transfer Protocol (SMTP) is presented. This synchronization problem can cause a message to be delivered multiple times. A method for avoiding this problem is suggested. Nodding familiarity with the SMTP specification, RFC-821, is required. |
|
| |
| RFC 1048 | BOOTP vendor information extensions |
| |
|
|
This memo proposes an addition to the Bootstrap Protocol (BOOTP). Comments and suggestions for improvements are sought. |
|
| |
| RFC 1052 | IAB recommendations for the development of Internet network management standards |
| |
|
|
This RFC is intended to convey to the Internet community and other interested parties the recommendations of the Internet Activities Board (IAB) for the development of network management protocols for use in the TCP/IP environment. This memo does NOT, in and of itself, define or propose an Official Internet Protocol. It does reflect, however, the policy of the IAB with respect to further network management development in the short and long term. |
|
| |
| RFC 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 1062 | Internet numbers |
| |
|
|
This memo is an official status report on the network numbers and gateway autonomous system numbers used in the Internet community. |
|
| |
| RFC 1063 | IP MTU discovery options |
| |
| Authors: | J.C. Mogul, C.A. Kent, C. Partridge, K. McCloghrie. |
| Date: | July 1988 |
| Formats: | txt html json |
| Obsoleted by: | RFC 1191 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1063 |
|
A pair of IP options that can be used to learn the minimum MTU of a path through an internet is described, along with its possible uses. This is a proposal for an Experimental protocol. |
|
| |
| RFC 1064 | Interactive Mail Access Protocol: Version 2 |
| |
|
|
This memo suggests a method for workstations to dynamically access mail from a mailbox server ("respository"). This RFC specifies a standard for the SUMEX-AIM community and a proposed experimental protocol for the Internet community. Discussion and suggestions for improvement are requested. |
|
| |
| RFC 1066 | Management Information Base for network management of TCP/IP-based internets |
| |
|
|
This RFC provides the initial version of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets in the short-term. In particular, together with its companion memos which describe the structure of management information along with the initial network management protocol, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets, and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementations in the Internet which are network manageable are expected to adopt and implement this specification. |
|
| |
| RFC 1067 | Simple Network Management Protocol |
| |
| Authors: | J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin. |
| Date: | August 1988 |
| Formats: | txt html json |
| Obsoleted by: | RFC 1098 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1067 |
|
This RFC defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. In particular, together with its companion memos which describe the structure of management information along with the initial management information base, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementations in the Internet which are network manageable are expected to adopt and implement this specification. |
|
| |
| RFC 1068 | Background File Transfer Program (BFTP) |
| |
| Authors: | A.L. DeSchon, R.T. Braden. |
| Date: | August 1988 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1068 |
|
This RFC describes an Internet background file transfer service that is built upon the third-party transfer model of FTP. No new protocols are involved. The purpose of this memo is to stimulate discussions on new Internet service modes. |
|
| |
| RFC 1069 | Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol |
| |
|
|
This RFC suggests an addressing scheme for use with the ISO Connectionless Network Protocol (CLNP) in the Internet. This is a solution to one of the problems inherent in the use of "ISO-grams" in the Internet. This memo is a revision of RFC 986. This RFC suggests a proposed protocol for the Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 1070 | Use of the Internet as a subnetwork for experimentation with the OSI network layer |
| |
| Authors: | R.A. Hagens, N.E. Hall, M.T. Rose. |
| Date: | February 1989 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1070 |
|
This RFC proposes a scenario for experimentation with the International Organization for Standardization (ISO) Open Systems Interconnection (OSI) network layer protocols over the Internet and requests discussion and suggestions for improvements to this scenario. This RFC also proposes the creation of an experimental OSI internet. To participate in the experimental OSI internet, a system must abide by the agreements set forth in this RFC. |
|
| |
| RFC 1074 | NSFNET backbone SPF based Interior Gateway Protocol |
| |
| Authors: | J. Rekhter. |
| Date: | October 1988 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1074 |
|
This RFC is an implementation description of the standard ANSI IS-IS and ISO ES-IS routing protocols within the NSFNET backbone network. |
|
| |
| RFC 1076 | HEMS monitoring and control language |
| |
|
|
This RFC specifies a query language for monitoring and control of network entities. This RFC supercedes RFC 1023, extending the query language and providing more discussion of the underlying issues. This language is a component of the High-Level Entity Monitoring System (HEMS) described in RFC 1021 and RFC 1022. Readers may wish to consult these RFCs when reading this memo. RFC 1024 contains detailed assignments of numbers and structures used in this system. Portions of RFC 1024 that define query language structures are superceded by definitions in this memo. This memo assumes a knowledge of the ISO data encoding standard, ASN.1. |
|
| |
| RFC 1077 | Critical issues in high bandwidth networking |
| |
| Authors: | B.M. Leiner. |
| Date: | November 1988 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1077 |
|
This memo presents the results of a working group on High Bandwidth Networking. This RFC is for your information and you are encouraged to comment on the issues presented. |
|
| |
| RFC 1080 | Telnet remote flow control option |
| |
|
|
This RFC specifies a standard for the Internet community. Hosts on the Internet that do remote flow control within the Telnet protocol are expected to adopt and implement this standard. |
|
| |
| RFC 1081 | Post Office Protocol: Version 3 |
| |
|
|
This memo suggests a simple method for workstations to dynamically access mail from a mailbox server. This RFC specifies a proposed protocol for the Internet community, and requests discussion and suggestions for improvements. |
|
| |
| RFC 1082 | Post Office Protocol: Version 3: Extended service offerings |
| |
| Authors: | M.T. Rose. |
| Date: | November 1988 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1082 |
|
This memo suggests a simple method for workstations to dynamically access mail from a discussion group server, as an extension to an earlier memo which dealt with dynamically accessing mail from a mailbox server using the Post Office Protocol - Version 3 (POP3). This RFC specifies a proposed protocol for the Internet community, and requests discussion and suggestions for improvements. All of the extensions described in this memo to the POP3 are OPTIONAL. |
|
| |
| RFC 1084 | BOOTP vendor information extensions |
| |
|
|
This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville. This memo will be updated as additional tags are are defined. This edition introduces Tag 13 for Boot File Size. Comments and suggestions for improvements are sought. |
|
| |
| RFC 1085 | ISO presentation services on top of TCP/IP based internets |
| |
| Authors: | M.T. Rose. |
| Date: | December 1988 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1085 |
|
RFC 1006 describes a mechanism for providing the ISO transport service on top of TCP/IP. Once this method is applied, one may implement "real" ISO applications on top of TCP/IP-based internets, by simply implementing OSI session, presentation, and application services on top of the transport service access point which is provided on top of the TCP. Although straight-forward, there are some environments in which the richness provided by the OSI application layer is desired, but it is nonetheless impractical to implement the underlying OSI infrastructure (i.e., the presentation, session, and transport services on top of the TCP). This memo describes an approach for providing "stream-lined" support of OSI application services on top of TCP/IP-based internets for such constrained environments. This memo proposes a standard for the Internet community. |
|
| |
| RFC 1086 | ISO-TP0 bridge between TCP and X.25 |
| |
| Authors: | J.P. Onions, M.T. Rose. |
| Date: | December 1988 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1086 |
|
This memo proposes a standard for the Internet community. Hosts on the Internet that choose to implement ISO TP0 transport connectivity between TCP and X.25 based hosts are expected to experiment with this proposal. TCP port 146 is reserved for this proposal. |
|
| |
| RFC 1087 | Ethics and the Internet |
| |
| Authors: | Defense Advanced Research Projects Agency, Internet Activities Board. |
| Date: | January 1989 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1087 |
|
This memo is a statement of policy by the Internet Activities Board (IAB) concerning the proper use of the resources of the Internet. |
|
| |
| RFC 1089 | SNMP over Ethernet |
| |
| Authors: | M. Schoffstall, C. Davin, M. Fedor, J. Case. |
| Date: | February 1989 |
| Formats: | txt json html |
| Obsoleted by: | RFC 4789 |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1089 |
|
This memo describes an experimental method by which the Simple Network Management Protocol (SNMP) can be used over Ethernet MAC layer framing instead of the Internet UDP/IP protocol stack. This specification is useful for LAN based network elements that support no higher layer protocols beyond the MAC sub-layer. |
|
| |
| RFC 1090 | SMTP on X.25 |
| |
| Authors: | R. Ullmann. |
| Date: | February 1989 |
| Formats: | txt json html |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1090 |
|
This memo proposes a standard for SMTP on the virtual circuit facility provided by the X.25 standard of the CCITT. |
|
| |
| RFC 1092 | EGP and policy based routing in the new NSFNET backbone |
| |
| Authors: | J. Rekhter. |
| Date: | February 1989 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1092 |
|
This memo discusses implementation decisions for routing issues in the NSFNET, especially in the NSFNET Backbone. Of special concern is the restriction of routing information to advertize the best route as established by a policy decision. |
|
| |
| RFC 1093 | NSFNET routing architecture |
| |
| Authors: | H.W. Braun. |
| Date: | February 1989 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1093 |
|
This document describes the routing architecture for the NSFNET centered around the new NSFNET Backbone, with specific emphasis on the interface between the backbone and its attached networks. |
|
| |
| RFC 1095 | Common Management Information Services and Protocol over TCP/IP (CMOT) |
| |
|
|
This memo defines a network management architecture that uses the International Organization for Standardization's (ISO) Common Management Information Services/Common Management Information Protocol (CMIS/CMIP) in a TCP/IP environment. This architecture provides a means by which control and monitoring information can be exchanged between a manager and a remote network element. In particular, this memo defines the means for implementing the Draft International Standard (DIS) version of CMIS/CMIP on top of Internet transport protocols for the purpose of carrying management information defined in the Internet-standard management information base. DIS CMIS/CMIP is suitable for deployment in TCP/IP networks while CMIS/CMIP moves toward becoming an International Standard. Together with the relevant ISO standards and the companion RFCs that describe the initial structure of management information and management information base, these documents provide the basis for a comprehensive architecture and system for managing TCP/IP- based internets, and in particular the Internet. |
|
| |
| RFC 1097 | Telnet subliminal-message option |
| |
| Authors: | B. Miller. |
| Date: | 1 April 1989 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1097 |
|
This RFC specifies a standard for the Internet community. Hosts on the Internet that display subliminal messages within the Telnet protocol are expected to adopt and implement this standard. |
|
| |
| RFC 1098 | Simple Network Management Protocol (SNMP) |
| |
|
|
This RFC is a re-release of RFC 1067, with a changed "Status of this Memo" section. This memo defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. In particular, together with its companion memos which describe the structure of management information along with the initial management information base, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular the Internet. |
|
| |
| RFC 1101 | DNS encoding of network names and other types |
| |
|
|
This RFC proposes two extensions to the Domain Name System: - A specific method for entering and retrieving RRs which map between network names and numbers. - Ideas for a general method for describing mappings between arbitrary identifiers and numbers. The method for mapping between network names and addresses is a proposed standard, the ideas for a general method are experimental. |
|
| |
| RFC 1102 | Policy routing in Internet protocols |
| |
|
|
The purpose of this RFC is to focus discussion on particular problems in the Internet and possible methods of solution. No proposed solutions in this document are intended as standards for the Internet. |
|
| |
| RFC 1103 | Proposed standard for the transmission of IP datagrams over FDDI Networks |
| |
|
|
This RFC specifies a method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK] |
|
| |
| RFC 1104 | Models of policy based routing |
| |
|
|
The purpose of this RFC is to outline a variety of models for policy based routing. The relative benefits of the different approaches are reviewed. Discussions and comments are explicitly encouraged to move toward the best policy based routing model that scales well within a large internetworking environment. |
|
| |
| RFC 1109 | Report of the second Ad Hoc Network Management Review Group |
| |
|
|
This RFC reports an official Internet Activities Board (IAB) policy position on the treatment of Network Management in the Internet. This RFC presents the results and recommendations of the second Ad Hoc Network Management Review on June 12, 1989. The results of the first such meeting were reported in RFC 1052. |
|
| |
| RFC 1124 | Policy issues in interconnecting networks |
| |
|
|
To support the activities of the Federal Research Internet Coordinating Committee (FRICC) in creating an interconnected set of networks to serve the research community, two workshops were held to address the technical support of policy issues that arise when interconnecting such networks. Held under the suspices of the Internet Activities Board at the request of the FRICC, and sponsored by NASA through RIACS, the workshops addressed the required and feasible technologies and architectures that could be used to satisfy the desired policies for interconnection. The purpose of this RFC is to report the results of these workshops. |
|
| |
| RFC 1125 | Policy requirements for inter Administrative Domain routing |
| |
|
|
The purpose of this memo is to focus discussion on particular problems in the Internet and possible methods of solution. No proposed solutions in this document are intended as standards for the Internet. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to such problems, leading eventually to the development and adoption of standards. |
|
| |
| RFC 1126 | Goals and functional requirements for inter-autonomous system routing |
| |
| Authors: | M. Little. |
| Date: | October 1989 |
| Formats: | txt html json |
| Status: | UNKNOWN |
| DOI: | 10.17487/RFC 1126 |
|
This document describes the functional requirements for a routing protocol to be used between autonomous systems. This document is intended as a necessary precursor to the design of a new inter- autonomous system routing protocol and specifies requirements for the Internet applicable for use with the current DoD IP, the ISO IP, and future Internet Protocols. It is intended that these requirements will form the basis for the future development of a new inter-autonomous systems routing architecture and protocol. This memo does not specify a standard. |
|
| |
| RFC 1128 | Measured performance of the Network Time Protocol in the Internet system |
| |
|
|
This paper describes a series of experiments involving over 100,000 hosts of the Internet system and located in the U.S., Europe and the Pacific. The experiments are designed to evaluate the availability, accuracy and reliability of international standard time distribution using the DARPA/NSF Internet and the Network Time Protocol (NTP), which is specified in RFC-1119. NTP is designed specifically for use in a large, diverse internet system operating at speeds from mundane to lightwave. In NTP a distributed subnet of time servers operating in a self-organizing, hierarchical, master-slave configuration exchange precision timestamps in order to synchronize subnet clocks to each other and national time standards via wire or radio. The experiments are designed to locate Internet hosts and gateways that provide time by one of three time distribution protocols and evaluate the accuracy of their indications. For those hosts that support NTP, the experiments determine the distribution of errors and other statistics over paths spanning major portions of the globe. Finally, the experiments evaluate the accuracy and reliability of precision timekeeping using NTP and typical Internet paths involving DARPA, NSFNET and other agency networks. The experiments demonstrate that timekeeping accuracy throughout most portions of the Internet can be ordinarily maintained to within a few tens of milliseconds, even in cases of failure or disruption of clocks, time servers or networks. This memo does not specify a standard. |
|
