Internet Documents RFCs RFCs All Documents STDs Internet Standards Documents BCPs Best Current Practice Documents FYIs Informational Documents

RFC 1	Host Software
	Authors: S. Crocker. Date: April 1969 Formats: txt pdf Status: UNKNOWN
RFC 2	Host software
	Authors: B. Duvall. Date: April 1969 Formats: txt pdf Status: UNKNOWN
RFC 3	Documentation conventions
	Authors: S.D. Crocker. Date: April 1969 Formats: txt pdf Obsoleted by: RFC 0010 Status: UNKNOWN
RFC 4	Network timetable
	Authors: E.B. Shapiro. Date: March 1969 Formats: txt pdf Status: UNKNOWN
RFC 5	Decode Encode Language (DEL)
	Authors: J. Rulifson. Date: June 1969 Formats: txt pdf Status: UNKNOWN
RFC 6	Conversation with Bob Kahn
	Authors: S.D. Crocker. Date: April 1969 Formats: txt pdf Status: UNKNOWN
RFC 7	Host-IMP interface
	Authors: G. Deloche. Date: May 1969 Formats: txt pdf Status: UNKNOWN
RFC 8	ARPA Network Functional Specifications
	Authors: G. Deloche. Date: May 1969 Formats: pdf Status: UNKNOWN
RFC 9	Host Software
	Authors: G. Deloche. Date: May 1969 Formats: pdf Status: UNKNOWN
RFC 10	Documentation conventions
	Authors: S.D. Crocker. Date: July 1969 Formats: txt pdf Obsoletes: RFC 0003 Obsoleted by: RFC 0016 Updated by: RFC 0024, RFC 0027, RFC 0030 Status: UNKNOWN
RFC 11	Implementation of the Host - Host Software Procedures in GORDO
	Authors: G. Deloche. Date: August 1969 Formats: txt pdf Obsoleted by: RFC 0033 Status: UNKNOWN
RFC 12	IMP-Host interface flow diagrams
	Authors: M. Wingfield. Date: August 1969 Formats: txt pdf ps Status: UNKNOWN
RFC 13	Zero Text Length EOF Message
	Authors: V. Cerf. Date: August 1969 Formats: txt pdf Status: UNKNOWN
RFC 15	Network subsystem for time sharing hosts
	Authors: C.S. Carr. Date: September 1969 Formats: txt pdf Status: UNKNOWN
RFC 16	M.I.T
	Authors: S. Crocker. Date: August 1969 Formats: txt pdf Obsoletes: RFC 0010 Obsoleted by: RFC 0024 Updated by: RFC 0024, RFC 0027, RFC 0030 Status: UNKNOWN
RFC 17	Some questions re: Host-IMP Protocol
	Authors: J.E. Kreznar. Date: August 1969 Formats: txt pdf Status: UNKNOWN
RFC 18	IMP-IMP and HOST-HOST Control Links
	Authors: V. Cerf. Date: September 1969 Formats: txt pdf Status: UNKNOWN
RFC 19	Two protocol suggestions to reduce congestion at swap bound nodes
	Authors: J.E. Kreznar. Date: October 1969 Formats: txt pdf Status: UNKNOWN
RFC 20	ASCII format for network interchange
	Authors: V.G. Cerf. Date: October 1969 Formats: txt pdf Status: UNKNOWN
RFC 21	Network meeting
	Authors: V.G. Cerf. Date: October 1969 Formats: txt pdf Status: UNKNOWN
RFC 22	Host-host control message formats
	Authors: V.G. Cerf. Date: October 1969 Formats: txt pdf Status: UNKNOWN
RFC 23	Transmission of Multiple Control Messages
	Authors: G. Gregg. Date: October 1969 Formats: txt pdf Status: UNKNOWN
RFC 24	Documentation Conventions
	Authors: S.D. Crocker. Date: November 1969 Formats: txt pdf Obsoletes: RFC 0016 Updates: RFC 0010, RFC 0016 Updated by: RFC 0027, RFC 0030 Status: UNKNOWN
RFC 25	No High Link Numbers
	Authors: S.D. Crocker. Date: October 1969 Formats: txt pdf Status: UNKNOWN
RFC 27	Documentation Conventions
	Authors: S.D. Crocker. Date: December 1969 Formats: txt pdf Updates: RFC 0010, RFC 0016, RFC 0024 Updated by: RFC 0030 Status: UNKNOWN
RFC 28	Time Standards
	Authors: W.K. English. Date: January 1970 Formats: txt pdf Status: UNKNOWN
RFC 29	Response to RFC 28
	Authors: R.E. Kahn. Date: January 1970 Formats: txt pdf Also: RFC 0028 Status: UNKNOWN
RFC 30	Documentation Conventions
	Authors: S.D. Crocker. Date: February 1970 Formats: txt pdf Updates: RFC 0010, RFC 0016, RFC 0024, RFC 0027 Status: UNKNOWN
RFC 31	Binary Message Forms in Computer
	Authors: D. Bobrow, W.R. Sutherland. Date: February 1968 Formats: txt pdf Status: UNKNOWN
RFC 32	Some Thoughts on SRI's Proposed Real Time Clock
	Authors: J. Cole. Date: February 1970 Formats: txt pdf Status: UNKNOWN
RFC 33	New Host-Host Protocol
	Authors: S.D. Crocker. Date: February 1970 Formats: txt pdf Obsoletes: RFC 0011 Updated by: RFC 0036, RFC 0047 Status: UNKNOWN
RFC 34	Some Brief Preliminary Notes on the Augmentation Research Center Clock
	Authors: W.K. English. Date: February 1970 Formats: txt pdf Status: UNKNOWN
RFC 35	Network Meeting
	Authors: S.D. Crocker. Date: March 1970 Formats: txt pdf Status: INFORMATIONAL
RFC 36	Protocol Notes
	Authors: S.D. Crocker. Date: March 1970 Formats: txt pdf Updates: RFC 0033 Updated by: RFC 0039, RFC 0044 Status: UNKNOWN
RFC 37	Network Meeting Epilogue, etc
	Authors: S.D. Crocker. Date: March 1970 Formats: txt pdf Status: UNKNOWN
RFC 38	Comments on Network Protocol from NWG/RFC #36
	Authors: S.M. Wolfe. Date: March 1970 Formats: txt pdf Status: UNKNOWN
RFC 39	Comments on Protocol Re: NWG/RFC #36
	Authors: E. Harslem, J.F. Heafner. Date: March 1970 Formats: txt pdf Updates: RFC 0036 Status: UNKNOWN
RFC 40	More Comments on the Forthcoming Protocol
	Authors: E. Harslem, J.F. Heafner. Date: March 1970 Formats: txt pdf Status: UNKNOWN
RFC 41	IMP-IMP Teletype Communication
	Authors: J.T. Melvin. Date: March 1970 Formats: txt pdf Status: UNKNOWN
RFC 42	Message Data Types
	Authors: E. Ancona. Date: March 1970 Formats: txt pdf Status: UNKNOWN
RFC 43	Proposed Meeting
	Authors: A.G. Nemeth. Date: April 1970 Formats: txt pdf Status: UNKNOWN
RFC 44	Comments on NWG/RFC 33 and 36
	Authors: A. Shoshani, R. Long, A. Landsberg. Date: April 1970 Formats: txt pdf Updates: RFC 0036 Status: UNKNOWN
RFC 45	New Protocol is Coming
	Authors: J. Postel, S.D. Crocker. Date: April 1970 Formats: txt pdf Status: UNKNOWN
RFC 46	ARPA Network protocol notes
	Authors: E. Meyer. Date: April 1970 Formats: txt pdf Status: UNKNOWN
RFC 47	BBN's Comments on NWG/RFC #33
	Authors: J. Postel, S. Crocker. Date: April 1970 Formats: txt pdf Updates: RFC 0033 Status: UNKNOWN
RFC 48	Possible protocol plateau
	Authors: J. Postel, S.D. Crocker. Date: April 1970 Formats: txt pdf Status: UNKNOWN
RFC 49	Conversations with S. Crocker (UCLA)
	Authors: Crocker (UCLA). E. Meyer. Date: April 1970 Formats: txt pdf Status: UNKNOWN
RFC 50	Comments on the Meyer Proposal
	Authors: E. Harslen, J. Heafner. Date: April 1970 Formats: txt pdf Status: UNKNOWN
RFC 51	Proposal for a Network Interchange Language
	Authors: M. Elie. Date: May 1970 Formats: pdf Status: UNKNOWN
RFC 52	Updated distribution list
	Authors: J. Postel, S.D. Crocker. Date: July 1970 Formats: txt pdf Updated by: RFC 0069 Status: UNKNOWN
RFC 53	Official protocol mechanism
	Authors: S.D. Crocker. Date: June 1970 Formats: txt pdf Status: UNKNOWN
RFC 54	Official Protocol Proffering
	Authors: S.D. Crocker, J. Postel, J. Newkirk, M. Kraley. Date: June 1970 Formats: txt pdf Updated by: RFC 0057 Status: UNKNOWN
RFC 55	Prototypical implementation of the NCP
	Authors: J. Newkirk, M. Kraley, J. Postel, S.D. Crocker. Date: June 1970 Formats: txt pdf Status: UNKNOWN
RFC 56	Third Level Protocol: Logger Protocol
	Authors: E. Belove, D. Black, R. Flegal, L.G. Farquar. Date: June 1970 Formats: txt pdf Status: UNKNOWN
RFC 57	Thoughts and Reflections on NWG/RFC 54
	Authors: M. Kraley, J. Newkirk. Date: June 1970 Formats: txt pdf Updates: RFC 0054 Status: UNKNOWN
RFC 58	Logical Message Synchronization
	Authors: T.P. Skinner. Date: June 1970 Formats: txt pdf Status: UNKNOWN
RFC 59	Flow Control - Fixed Versus Demand Allocation
	Authors: E. Meyer. Date: June 1970 Formats: txt pdf Status: UNKNOWN
RFC 60	Simplified NCP Protocol
	Authors: R.B. Kalin. Date: July 1970 Formats: txt pdf Status: UNKNOWN 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
	Authors: D.C. Walden. Date: July 1970 Formats: txt pdf Obsoleted by: RFC 0062 Status: UNKNOWN
RFC 62	Systems for Interprocess Communication in a Resource Sharing Computer Network
	Authors: D.C. Walden. Date: August 1970 Formats: txt pdf Obsoletes: RFC 0061 Status: UNKNOWN
RFC 63	Belated Network Meeting Report
	Authors: V.G. Cerf. Date: July 1970 Formats: txt pdf Status: UNKNOWN
RFC 64	Getting rid of marking
	Authors: M. Elie. Date: July 1970 Formats: txt pdf Status: UNKNOWN
RFC 65	Comments on Host/Host Protocol document #1
	Authors: D.C. Walden. Date: August 1970 Formats: txt pdf Status: UNKNOWN
RFC 66	NIC - third level ideas and other noise
	Authors: S.D. Crocker. Date: August 1970 Formats: txt pdf Obsoleted by: RFC 0123 Updated by: RFC 0080, RFC 0093 Status: UNKNOWN
RFC 67	Proposed Change to Host/IMP Spec to Eliminate Marking
	Authors: W.R. Crowther. Date: January 1970 Formats: txt pdf Status: UNKNOWN
RFC 68	Comments on Memory Allocation Control Commands: CEASE, ALL, GVB, RET, and RFNM
	Authors: M. Elie. Date: August 1970 Formats: txt pdf Status: UNKNOWN
RFC 69	Distribution List Change for MIT
	Authors: A.K. Bhushan. Date: September 1970 Formats: txt pdf Updates: RFC 0052 Status: UNKNOWN
RFC 70	Note on Padding
	Authors: S.D. Crocker. Date: October 1970 Formats: txt pdf Updated by: RFC 0228 Status: UNKNOWN
RFC 71	Reallocation in Case of Input Error
	Authors: T. Schipper. Date: September 1970 Formats: txt pdf Status: UNKNOWN
RFC 72	Proposed Moratorium on Changes to Network Protocol
	Authors: R.D. Bressler. Date: September 1970 Formats: txt pdf Status: UNKNOWN
RFC 73	Response to NWG/RFC 67
	Authors: S.D. Crocker. Date: September 1970 Formats: txt pdf Status: UNKNOWN
RFC 74	Specifications for Network Use of the UCSB On-Line System
	Authors: J.E. White. Date: October 1970 Formats: txt pdf Updated by: RFC 0217, RFC 0225 Status: UNKNOWN
RFC 75	Network Meeting
	Authors: S.D. Crocker. Date: October 1970 Formats: txt pdf Status: UNKNOWN
RFC 76	Connection by name: User oriented protocol
	Authors: J. Bouknight, J. Madden, G.R. Grossman. Date: October 1970 Formats: txt pdf Status: UNKNOWN
RFC 77	Network meeting report
	Authors: J. Postel. Date: November 1970 Formats: txt pdf Status: UNKNOWN
RFC 78	NCP Status Report: UCSB/Rand
	Authors: E. Harslem, J.F. Heafner, J.E. White. Date: October 1970 Formats: txt pdf Status: UNKNOWN
RFC 79	Logger Protocol error
	Authors: E. Meyer. Date: November 1970 Formats: txt pdf Status: UNKNOWN
RFC 80	Protocols and Data Formats
	Authors: E. Harslem, J.F. Heafner. Date: December 1970 Formats: txt pdf Obsoleted by: RFC 0123 Updates: RFC 0066 Updated by: RFC 0093 Status: UNKNOWN
RFC 81	Request for Reference Information
	Authors: J. Bouknight. Date: December 1970 Formats: txt pdf Status: UNKNOWN
RFC 82	Network Meeting Notes
	Authors: E. Meyer. Date: December 1970 Formats: txt pdf Status: UNKNOWN
RFC 83	Language-machine for data reconfiguration
	Authors: R.H. Anderson, E. Harslem, J.F. Heafner. Date: December 1970 Formats: txt pdf Status: UNKNOWN
RFC 84	List of NWG/RFC's 1-80
	Authors: J.B. North. Date: December 1970 Formats: txt pdf Status: UNKNOWN
RFC 85	Network Working Group meeting
	Authors: S.D. Crocker. Date: December 1970 Formats: txt pdf Status: UNKNOWN
RFC 86	Proposal for a Network Standard Format for a Data Stream to Control Graphics Display
	Authors: S.D. Crocker. Date: January 1971 Formats: txt pdf Updated by: RFC 0125 Status: UNKNOWN
RFC 87	Topic for Discussion at the Next Network Working Group Meeting
	Authors: A. Vezza. Date: January 1971 Formats: txt pdf Status: UNKNOWN
RFC 88	NETRJS: A third level protocol for Remote Job Entry
	Authors: R.T. Braden, S.M. Wolfe. Date: January 1971 Formats: txt pdf Obsoleted by: RFC 0189 Status: UNKNOWN
RFC 89	Some historic moments in networking
	Authors: R.M. Metcalfe. Date: January 1971 Formats: txt pdf Status: UNKNOWN
RFC 90	CCN as a Network Service Center
	Authors: R.T. Braden. Date: January 1971 Formats: txt pdf Status: UNKNOWN
RFC 91	Proposed User-User Protocol
	Authors: G.H. Mealy. Date: December 1970 Formats: txt pdf Status: UNKNOWN
RFC 93	Initial Connection Protocol
	Authors: A.M. McKenzie. Date: January 1971 Formats: txt pdf Updates: RFC 0066, RFC 0080 Status: UNKNOWN
RFC 94	Some thoughts on Network Graphics
	Authors: E. Harslem, J.F. Heafner. Date: February 1971 Formats: txt pdf Status: UNKNOWN
RFC 95	Distribution of NWG/RFC's through the NIC
	Authors: S.D. Crocker. Date: February 1971 Formats: txt pdf Obsoleted by: RFC 0155 Status: UNKNOWN
RFC 96	An Interactive Network Experiment to Study Modes of Access the Network Information Center
	Authors: R.W. Watson. Date: February 1971 Formats: txt pdf Status: INFORMATIONAL
RFC 97	First Cut at a Proposed Telnet Protocol
	Authors: J.T. Melvin, R.W. Watson. Date: February 1971 Formats: txt pdf Status: UNKNOWN
RFC 98	Logger Protocol Proposal
	Authors: E. Meyer, T. Skinner. Date: February 1971 Formats: txt pdf Updated by: RFC 0123 Status: UNKNOWN
RFC 99	Network Meeting
	Authors: P.M. Karp. Date: February 1971 Formats: txt pdf Updated by: RFC 0116 Status: UNKNOWN
RFC 100	Categorization and guide to NWG/RFCs
	Authors: P.M. Karp. Date: February 1971 Formats: txt pdf Status: UNKNOWN
RFC 101	Notes on the Network Working Group meeting, Urbana, Illinois, February 17, 1971
	Authors: R.W. Watson. Date: February 1971 Formats: txt pdf Updated by: RFC 0108, RFC 0123 Status: UNKNOWN
RFC 102	Output of the Host-Host Protocol glitch cleaning committee
	Authors: S.D. Crocker. Date: February 1971 Formats: txt pdf Updated by: RFC 0107 Status: UNKNOWN
RFC 103	Implementation of Interrupt Keys
	Authors: R.B. Kalin. Date: February 1971 Formats: txt pdf Status: UNKNOWN
RFC 104	Link 191
	Authors: J.B. Postel, S.D. Crocker. Date: February 1971 Formats: txt pdf Status: UNKNOWN
RFC 105	Network Specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB
	Authors: J.E. White. Date: March 1971 Formats: txt pdf Updated by: RFC 0217 Status: UNKNOWN
RFC 106	User/Server Site Protocol Network Host Questionnaire
	Authors: T.C. O'Sullivan. Date: March 1971 Formats: txt pdf Status: UNKNOWN
RFC 107	Output of the Host-Host Protocol Glitch Cleaning Committee
	Authors: R.D. Bressler, S.D. Crocker, W.R. Crowther, G.R. Grossman, R.S. Tomlinson, J.E. White. Date: March 1971 Formats: txt pdf Updates: RFC 0102 Updated by: RFC 0111, RFC 0124, RFC 0132, RFC 0154, RFC 0179 Status: UNKNOWN
RFC 108	Attendance list at the Urbana NWG meeting, February 17-19, 1971
	Authors: R.W. Watson. Date: March 1971 Formats: txt pdf Updates: RFC 0101 Status: UNKNOWN
RFC 109	Level III Server Protocol for the Lincoln Laboratory 360/67 Host
	Authors: J. Winett. Date: March 1971 Formats: txt pdf Also: RFC 0393 Status: UNKNOWN
RFC 110	Conventions for Using an IBM 2741 Terminal as a User Console for Access to Network Server Hosts
	Authors: J. Winett. Date: March 1971 Formats: txt pdf Updated by: RFC 0135 Status: UNKNOWN
RFC 111	Pressure from the Chairman
	Authors: S.D. Crocker. Date: March 1971 Formats: txt pdf Updates: RFC 0107 Updated by: RFC 0130 Status: UNKNOWN
RFC 112	User/Server Site Protocol: Network Host Questionnaire
	Authors: T.C. O'Sullivan. Date: April 1971 Formats: txt pdf Status: UNKNOWN
RFC 113	Network activity report: UCSB Rand
	Authors: E. Harslem, J.F. Heafner, J.E. White. Date: April 1971 Formats: txt pdf Updated by: RFC 0227 Status: UNKNOWN
RFC 114	File Transfer Protocol
	Authors: A.K. Bhushan. Date: April 1971 Formats: txt pdf Updated by: RFC 0133, RFC 0141, RFC 0171, RFC 0172 Status: UNKNOWN
RFC 115	Some Network Information Center policies on handling documents
	Authors: R.W. Watson, J.B. North. Date: April 1971 Formats: txt pdf Status: UNKNOWN
RFC 116	Structure of the May NWG Meeting
	Authors: S.D. Crocker. Date: April 1971 Formats: txt pdf Updates: RFC 0099 Updated by: RFC 0131, RFC 0156 Status: UNKNOWN
RFC 117	Some comments on the official protocol
	Authors: J. Wong. Date: April 1971 Formats: txt pdf Status: UNKNOWN
RFC 118	Recommendations for facility documentation
	Authors: R.W. Watson. Date: April 1971 Formats: txt pdf Status: UNKNOWN
RFC 119	Network Fortran Subprograms
	Authors: M. Krilanovich. Date: April 1971 Formats: txt pdf Status: UNKNOWN
RFC 120	Network PL1 subprograms
	Authors: M. Krilanovich. Date: April 1971 Formats: txt pdf Status: UNKNOWN
RFC 121	Network on-line operators
	Authors: M. Krilanovich. Date: April 1971 Formats: txt pdf Status: UNKNOWN
RFC 122	Network specifications for UCSB's Simple-Minded File System
	Authors: J.E. White. Date: April 1971 Formats: txt pdf Updated by: RFC 0217, RFC 0269, RFC 0399, RFC 0431 Status: UNKNOWN
RFC 123	Proffered Official ICP
	Authors: S.D. Crocker. Date: April 1971 Formats: txt pdf Obsoletes: RFC 0066, RFC 0080 Obsoleted by: RFC 0165 Updates: RFC 0098, RFC 0101 Updated by: RFC 0127, RFC 0143, RFC 0148 Status: UNKNOWN
RFC 124	Typographical error in RFC 107
	Authors: J.T. Melvin. Date: April 1971 Formats: txt pdf Updates: RFC 0107 Status: UNKNOWN
RFC 125	Response to RFC 86: Proposal for Network Standard Format for a Graphics Data Stream
	Authors: J. McConnell. Date: April 1971 Formats: txt pdf Updates: RFC 0086 Updated by: RFC 0177 Status: UNKNOWN
RFC 126	Graphics Facilities at Ames Research Center
	Authors: J. McConnell. Date: April 1971 Formats: txt pdf Status: UNKNOWN
RFC 127	Comments on RFC 123
	Authors: J. Postel. Date: April 1971 Formats: txt pdf Obsoleted by: RFC 0145 Updates: RFC 0123 Updated by: RFC 0151 Status: UNKNOWN
RFC 128	Bytes
	Authors: J. Postel. Date: April 1971 Formats: txt pdf Status: UNKNOWN
RFC 129	Request for comments on socket name structure
	Authors: E. Harslem, J. Heafner, E. Meyer. Date: April 1971 Formats: txt pdf Updated by: RFC 0147 Status: UNKNOWN
RFC 130	Response to RFC 111: Pressure from the chairman
	Authors: J.F. Heafner. Date: April 1971 Formats: txt pdf Updates: RFC 0111 Status: UNKNOWN
RFC 131	Response to RFC 116: May NWG meeting
	Authors: E. Harslem, J.F. Heafner. Date: April 1971 Formats: txt pdf Updates: RFC 0116 Status: UNKNOWN
RFC 132	Typographical Error in RFC 107
	Authors: J.E. White. Date: April 1971 Formats: txt pdf Obsoleted by: RFC 0154 Updates: RFC 0107 Status: UNKNOWN
RFC 133	File Transfer and Error Recovery
	Authors: R.L. Sunberg. Date: April 1971 Formats: txt pdf Updates: RFC 0114 Status: UNKNOWN
RFC 134	Network Graphics meeting
	Authors: A. Vezza. Date: April 1971 Formats: txt pdf Status: UNKNOWN
RFC 135	Response to NWG/RFC 110
	Authors: W. Hathaway. Date: April 1971 Formats: txt pdf Updates: RFC 0110 Status: UNKNOWN
RFC 136	Host accounting and administrative procedures
	Authors: R.E. Kahn. Date: April 1971 Formats: txt pdf Status: UNKNOWN
RFC 137	Telnet Protocol - a proposed document
	Authors: T.C. O'Sullivan. Date: April 1971 Formats: txt pdf Updated by: RFC 0139 Status: UNKNOWN
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 pdf Status: UNKNOWN
RFC 139	Discussion of Telnet Protocol
	Authors: T.C. O'Sullivan. Date: May 1971 Formats: txt pdf Updates: RFC 0137 Updated by: RFC 0158 Also: RFC 0393 Status: UNKNOWN
RFC 140	Agenda for the May NWG meeting
	Authors: S.D. Crocker. Date: May 1971 Formats: txt pdf Updated by: RFC 0149 Status: UNKNOWN
RFC 141	Comments on RFC 114: A File Transfer Protocol
	Authors: E. Harslem, J.F. Heafner. Date: April 1971 Formats: txt pdf Updates: RFC 0114 Status: UNKNOWN
RFC 142	Time-Out Mechanism in the Host-Host Protocol
	Authors: C. Kline, J. Wong. Date: May 1971 Formats: txt pdf Status: UNKNOWN
RFC 143	Regarding proffered official ICP
	Authors: W. Naylor, J. Wong, C. Kline, J. Postel. Date: May 1971 Formats: txt pdf Obsoleted by: RFC 0165 Updates: RFC 0123, RFC 0145 Status: UNKNOWN
RFC 144	Data sharing on computer networks
	Authors: A. Shoshani. Date: April 1971 Formats: txt pdf Status: UNKNOWN
RFC 145	Initial Connection Protocol Control Commands
	Authors: J. Postel. Date: May 1971 Formats: txt pdf ps Obsoletes: RFC 0127 Obsoleted by: RFC 0165 Updated by: RFC 0143 Status: UNKNOWN
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 pdf Status: UNKNOWN
RFC 147	Definition of a socket
	Authors: J.M. Winett. Date: May 1971 Formats: txt pdf Updates: RFC 0129 Status: UNKNOWN
RFC 148	Comments on RFC 123
	Authors: A.K. Bhushan. Date: May 1971 Formats: txt pdf Updates: RFC 0123 Status: UNKNOWN
RFC 149	Best Laid Plans
	Authors: S.D. Crocker. Date: May 1971 Formats: txt pdf Updates: RFC 0140 Status: UNKNOWN
RFC 150	Use of IPC Facilities: A Working Paper
	Authors: R.B. Kalin. Date: May 1971 Formats: txt pdf Status: UNKNOWN
RFC 151	Comments on a proffered official ICP: RFCs 123, 127
	Authors: A. Shoshani. Date: May 1971 Formats: txt pdf Updates: RFC 0127 Status: UNKNOWN
RFC 152	SRI Artificial Intelligence status report
	Authors: M. Wilber. Date: May 1971 Formats: txt pdf Status: UNKNOWN
RFC 153	SRI ARC-NIC status
	Authors: J.T. Melvin, R.W. Watson. Date: May 1971 Formats: txt pdf Status: UNKNOWN
RFC 154	Exposition Style
	Authors: S.D. Crocker. Date: May 1971 Formats: txt pdf Obsoletes: RFC 0132 Updates: RFC 0107 Status: UNKNOWN
RFC 155	ARPA Network mailing lists
	Authors: J.B. North. Date: May 1971 Formats: txt pdf Obsoletes: RFC 0095 Obsoleted by: RFC 0168 Status: UNKNOWN
RFC 156	Status of the Illinois site: Response to RFC 116
	Authors: J. Bouknight. Date: April 1971 Formats: txt pdf Updates: RFC 0116 Status: UNKNOWN
RFC 157	Invitation to the Second Symposium on Problems in the Optimization of Data Communications Systems
	Authors: V.G. Cerf. Date: May 1971 Formats: txt pdf Status: UNKNOWN
RFC 158	Telnet Protocol: A Proposed Document
	Authors: T.C. O'Sullivan. Date: May 1971 Formats: txt pdf Obsoleted by: RFC 0495 Updates: RFC 0139 Updated by: RFC 0318 Also: RFC 0393 Status: UNKNOWN
RFC 160	RFC brief list
	Authors: Network Information Center. Stanford Research Institute. Date: May 1971 Formats: txt pdf Obsoleted by: RFC 0200, RFC 0999 Updates: NIC 6716 Status: UNKNOWN
RFC 161	Solution to the race condition in the ICP
	Authors: A. Shoshani. Date: May 1971 Formats: txt pdf Status: UNKNOWN
RFC 162	NETBUGGER3
	Authors: M. Kampe. Date: May 1971 Formats: txt pdf Status: UNKNOWN
RFC 163	Data transfer protocols
	Authors: V.G. Cerf. Date: May 1971 Formats: txt pdf Status: UNKNOWN
RFC 164	Minutes of Network Working Group meeting, 5/16 through 5/19/71
	Authors: J.F. Heafner. Date: May 1971 Formats: txt pdf Status: UNKNOWN
RFC 165	Proffered Official Initial Connection Protocol
	Authors: J. Postel. Date: May 1971 Formats: txt pdf Obsoletes: RFC 0145, RFC 0143, RFC 0123 Updated by: NIC_7101 Status: UNKNOWN
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 pdf Status: UNKNOWN
RFC 167	Socket conventions reconsidered
	Authors: A.K. Bhushan, R.M. Metcalfe, J.M. Winett. Date: May 1971 Formats: txt pdf Also: RFC 0147, RFC 0129 Status: UNKNOWN
RFC 168	ARPA Network mailing lists
	Authors: J.B. North. Date: May 1971 Formats: txt pdf Obsoletes: RFC 0155 Obsoleted by: RFC 0211 Status: UNKNOWN
RFC 169	COMPUTER NETWORKS
	Authors: S.D. Crocker. Date: May 1971 Formats: txt pdf Status: UNKNOWN
RFC 170	RFC List by Number
	Authors: Network Information Center. Stanford Research Institute. Date: June 1971 Formats: txt pdf Obsoleted by: RFC 0200 Status: UNKNOWN
RFC 171	The Data Transfer Protocol
	Authors: A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenize, J. Melvin, B. Sundberg, D. Watson, J. White. Date: June 1971 Formats: txt pdf Obsoleted by: RFC 0264 Updates: RFC 0114 Updated by: RFC 0238 Status: UNKNOWN
RFC 172	The File Transfer Protocol
	Authors: A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenzie, J. Melvin, B. Sundberg, D. Watson, J. White. Date: June 1971 Formats: txt pdf Obsoleted by: RFC 0265 Updates: RFC 0114 Updated by: RFC 0238 Status: UNKNOWN
RFC 173	Network Data Management Committee Meeting Announcement
	Authors: P.M. Karp, D.B. McKay. Date: June 1971 Formats: txt pdf Status: UNKNOWN
RFC 174	UCLA - Computer Science Graphics Overview
	Authors: J. Postel, V.G. Cerf. Date: June 1971 Formats: txt pdf Status: UNKNOWN
RFC 175	Comments on "Socket Conventions Reconsidered"
	Authors: E. Harslem, J.F. Heafner. Date: June 1971 Formats: txt pdf Status: UNKNOWN
RFC 176	Comments on "Byte size for connections"
	Authors: A.K. Bhushan, R. Kanodia, R.M. Metcalfe, J. Postel. Date: June 1971 Formats: txt pdf Status: UNKNOWN
RFC 177	Device independent graphical display description
	Authors: J. McConnell. Date: June 1971 Formats: txt pdf Updates: RFC 0125 Updated by: RFC 0181 Status: UNKNOWN
RFC 178	Network graphic attention handling
	Authors: I.W. Cotton. Date: June 1971 Formats: txt pdf Status: UNKNOWN
RFC 179	Link Number Assignments
	Authors: A.M. McKenzie. Date: June 1971 Formats: txt pdf Updates: RFC 0107 Status: UNKNOWN
RFC 180	File system questionnaire
	Authors: A.M. McKenzie. Date: June 1971 Formats: txt pdf Status: UNKNOWN
RFC 181	Modifications to RFC 177
	Authors: J. McConnell. Date: July 1971 Formats: txt pdf Updates: RFC 0177 Status: UNKNOWN
RFC 182	Compilation of list of relevant site reports
	Authors: J.B. North. Date: June 1971 Formats: txt pdf Status: UNKNOWN
RFC 183	EBCDIC Codes and Their Mapping to ASCII
	Authors: J.M. Winett. Date: July 1971 Formats: txt pdf Status: UNKNOWN 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
	Authors: K.C. Kelley. Date: July 1971 Formats: txt pdf Status: UNKNOWN
RFC 185	NIC distribution of manuals and handbooks
	Authors: J.B. North. Date: July 1971 Formats: txt pdf Status: UNKNOWN
RFC 186	Network graphics loader
	Authors: J.C. Michener. Date: July 1971 Formats: txt pdf Status: UNKNOWN
RFC 187	Network/440 Protocol Concept
	Authors: D.B. McKay, D.P. Karp. Date: July 1971 Formats: txt pdf Status: UNKNOWN
RFC 188	Data management meeting announcement
	Authors: P.M. Karp, D.B. McKay. Date: January 1971 Formats: txt pdf Status: UNKNOWN
RFC 189	Interim NETRJS specifications
	Authors: R.T. Braden. Date: July 1971 Formats: txt pdf Obsoletes: RFC 0088 Obsoleted by: RFC 0599 Updated by: RFC 0283 Status: UNKNOWN
RFC 190	DEC PDP-10-IMLAC communications system
	Authors: L.P. Deutsch. Date: July 1971 Formats: txt pdf Status: UNKNOWN
RFC 191	Graphics implementation and conceptualization at Augmentation Research Center
	Authors: C.H. Irby. Date: July 1971 Formats: txt pdf Status: UNKNOWN
RFC 192	Some factors which a Network Graphics Protocol must consider
	Authors: R.W. Watson. Date: July 1971 Formats: txt pdf Status: UNKNOWN
RFC 193	NETWORK CHECKOUT
	Authors: E. Harslem, J.F. Heafner. Date: July 1971 Formats: txt pdf Obsoleted by: RFC 0198 Updated by: RFC 0198 Status: UNKNOWN
RFC 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 pdf Status: UNKNOWN
RFC 195	Data computers-data descriptions and access language
	Authors: G.H. Mealy. Date: July 1971 Formats: txt pdf Status: UNKNOWN
RFC 196	Mail Box Protocol
	Authors: R.W. Watson. Date: July 1971 Formats: txt pdf Obsoleted by: RFC 0221 Status: UNKNOWN
RFC 197	Initial Connection Protocol - Reviewed
	Authors: A. Shoshani, E. Harslem. Date: July 1971 Formats: txt pdf Status: UNKNOWN
RFC 198	Site Certification - Lincoln Labs 360/67
	Authors: J.F. Heafner. Date: July 1971 Formats: txt pdf Obsoletes: RFC 0193 Obsoleted by: RFC 0214 Updates: RFC 0193 Status: UNKNOWN
RFC 199	Suggestions for a Network Data-Tablet Graphics Protocol
	Authors: T. Williams. Date: July 1971 Formats: txt pdf Status: UNKNOWN
RFC 200	RFC list by number
	Authors: J.B. North. Date: August 1971 Formats: txt pdf Obsoletes: RFC 0170, RFC 0160 Obsoleted by: NIC 7724 Status: UNKNOWN
RFC 202	Possible Deadlock in ICP
	Authors: S.M. Wolfe, J. Postel. Date: July 1971 Formats: txt pdf Status: UNKNOWN
RFC 203	Achieving reliable communication
	Authors: R.B. Kalin. Date: August 1971 Formats: txt pdf Status: UNKNOWN
RFC 204	Sockets in use
	Authors: J. Postel. Date: August 1971 Formats: txt pdf Updated by: RFC 0234 Status: UNKNOWN
RFC 205	NETCRT - a character display protocol
	Authors: R.T. Braden. Date: August 1971 Formats: txt pdf Status: UNKNOWN
RFC 206	A User TELNET Description of an Initial Implementation
	Authors: J. White. Date: August 1971 Formats: txt pdf Status: UNKNOWN
RFC 207	September Network Working Group meeting
	Authors: A. Vezza. Date: August 1971 Formats: txt pdf Obsoleted by: RFC 0212 Status: UNKNOWN
RFC 208	Address tables
	Authors: A.M. McKenzie. Date: August 1971 Formats: txt pdf Status: UNKNOWN
RFC 209	Host/IMP interface documentation
	Authors: B. Cosell. Date: August 1971 Formats: txt pdf Status: UNKNOWN
RFC 210	Improvement of Flow Control
	Authors: W. Conrad. Date: August 1971 Formats: txt pdf Status: UNKNOWN
RFC 211	ARPA Network Mailing Lists
	Authors: J.B. North. Date: August 1971 Formats: txt pdf Obsoletes: RFC 0168 Obsoleted by: RFC 0300 Status: UNKNOWN
RFC 212	NWG meeting on network usage
	Authors: Information Sciences Institute University of Southern California. Date: August 1971 Formats: txt pdf Obsoletes: RFC 0207 Updated by: RFC 0222 Status: UNKNOWN
RFC 213	IMP System change notification
	Authors: B. Cosell. Date: August 1971 Formats: txt pdf Status: UNKNOWN
RFC 214	Network checkpoint
	Authors: E. Harslem. Date: August 1971 Formats: txt pdf Obsoletes: RFC 0198 Status: UNKNOWN
RFC 215	NCP, ICP, and Telnet: The Terminal IMP implementation
	Authors: A.M. McKenzie. Date: August 1971 Formats: txt pdf Status: UNKNOWN
RFC 216	Telnet Access to UCSB's On-Line System
	Authors: J.E. White. Date: September 1971 Formats: txt pdf Status: UNKNOWN
RFC 217	Specifications changes for OLS, RJE/RJOR, and SMFS
	Authors: J.E. White. Date: September 1971 Formats: txt pdf Updates: RFC 0074, RFC 0105, RFC 0122 Status: UNKNOWN
RFC 218	Changing the IMP status reporting facility
	Authors: B. Cosell. Date: September 1971 Formats: txt pdf Status: UNKNOWN
RFC 219	User's View of the Datacomputer
	Authors: R. Winter. Date: September 1971 Formats: txt pdf Status: UNKNOWN
RFC 221	Mail Box Protocol: Version 2
	Authors: R.W. Watson. Date: August 1971 Formats: txt pdf Obsoletes: RFC 0196 Obsoleted by: RFC 0278 Status: UNKNOWN
RFC 222	Subject: System programmer's workshop
	Authors: R.M. Metcalfe. Date: September 1971 Formats: txt pdf Updates: RFC 0212 Updated by: RFC 0234 Status: UNKNOWN
RFC 223	Network Information Center schedule for network users
	Authors: J.T. Melvin, R.W. Watson. Date: September 1971 Formats: txt pdf Status: UNKNOWN
RFC 224	Comments on Mailbox Protocol
	Authors: A.M. McKenzie. Date: September 1971 Formats: txt pdf Status: UNKNOWN
RFC 225	Rand/UCSB network graphics experiment
	Authors: E. Harslem, R. Stoughton. Date: September 1971 Formats: txt pdf Updates: RFC 0074 Status: UNKNOWN
RFC 226	Standardization of host mnemonics
	Authors: P.M. Karp. Date: September 1971 Formats: txt pdf Obsoleted by: RFC 0247 Status: UNKNOWN
RFC 227	Data transfer rates (Rand/UCLA)
	Authors: J.F. Heafner, E. Harslem. Date: September 1971 Formats: txt pdf Updates: RFC 0113 Status: UNKNOWN
RFC 228	Clarification
	Authors: D.C. Walden. Date: September 1971 Formats: txt pdf Updates: RFC 0070 Status: UNKNOWN
RFC 229	Standard host names
	Authors: J. Postel. Date: September 1971 Formats: txt pdf Obsoleted by: RFC 0236 Status: UNKNOWN
RFC 230	Toward reliable operation of minicomputer-based terminals on a TIP
	Authors: T. Pyke. Date: September 1971 Formats: txt pdf Status: UNKNOWN
RFC 231	Service center standards for remote usage: A user's view
	Authors: J.F. Heafner, E. Harslem. Date: September 1971 Formats: txt pdf Status: UNKNOWN
RFC 232	Postponement of network graphics meeting
	Authors: A. Vezza. Date: September 1971 Formats: txt pdf Status: UNKNOWN
RFC 233	Standardization of host call letters
	Authors: A. Bhushan, R. Metcalfe. Date: September 1971 Formats: txt pdf Status: UNKNOWN
RFC 234	Network Working Group meeting schedule
	Authors: A. Vezza. Date: October 1971 Formats: txt pdf Updates: RFC 0222, RFC 0204 Status: UNKNOWN
RFC 235	Site status
	Authors: E. Westheimer. Date: September 1971 Formats: txt pdf Obsoleted by: RFC 0240 Status: UNKNOWN
RFC 236	Standard host names
	Authors: J. Postel. Date: September 1971 Formats: txt pdf Obsoletes: RFC 0229 Status: UNKNOWN
RFC 237	NIC view of standard host names
	Authors: R.W. Watson. Date: October 1971 Formats: txt pdf Obsoleted by: RFC 0273 Status: UNKNOWN
RFC 238	Comments on DTP and FTP proposals
	Authors: R.T. Braden. Date: September 1971 Formats: txt pdf Updates: RFC 0171, RFC 0172 Status: UNKNOWN
RFC 239	Host mnemonics proposed in RFC 226 (NIC 7625)
	Authors: R.T. Braden. Date: September 1971 Formats: txt pdf Also: RFC 0226, RFC 0229, RFC 0236 Status: UNKNOWN
RFC 240	Site Status
	Authors: A.M. McKenzie. Date: September 1971 Formats: txt pdf Obsoletes: RFC 0235 Obsoleted by: RFC 0252 Status: UNKNOWN
RFC 241	Connecting computers to MLC ports
	Authors: A.M. McKenzie. Date: September 1971 Formats: txt pdf Status: UNKNOWN
RFC 242	Data Descriptive Language for Shared Data
	Authors: L. Haibt, A.P. Mullery. Date: July 1971 Formats: txt pdf Status: UNKNOWN
RFC 243	Network and data sharing bibliography
	Authors: A.P. Mullery. Date: October 1971 Formats: txt pdf Obsoleted by: RFC 0290 Status: UNKNOWN
RFC 245	Reservations for Network Group meeting
	Authors: C. Falls. Date: October 1971 Formats: txt pdf Status: UNKNOWN
RFC 246	Network Graphics meeting
	Authors: A. Vezza. Date: October 1971 Formats: txt pdf Status: UNKNOWN
RFC 247	Proffered set of standard host names
	Authors: P.M. Karp. Date: October 1971 Formats: txt pdf Obsoletes: RFC 0226 Status: UNKNOWN
RFC 249	Coordination of equipment and supplies purchase
	Authors: R.F. Borelli. Date: October 1971 Formats: txt pdf Status: UNKNOWN
RFC 250	Some thoughts on file transfer
	Authors: H. Brodie. Date: October 1971 Formats: txt pdf Status: UNKNOWN
RFC 251	Weather data
	Authors: D. Stern. Date: October 1971 Formats: txt pdf Status: UNKNOWN
RFC 252	Network host status
	Authors: E. Westheimer. Date: October 1971 Formats: txt pdf Obsoletes: RFC 0240 Obsoleted by: RFC 0255 Status: UNKNOWN
RFC 253	Second Network Graphics meeting details
	Authors: J.A. Moorer. Date: October 1971 Formats: txt pdf Status: UNKNOWN
RFC 254	Scenarios for using ARPANET computers
	Authors: A. Bhushan. Date: October 1971 Formats: txt pdf Status: UNKNOWN
RFC 255	Status of network hosts
	Authors: E. Westheimer. Date: October 1971 Formats: txt pdf Obsoletes: RFC 0252 Obsoleted by: RFC 0266 Status: UNKNOWN
RFC 256	IMPSYS change notification
	Authors: B. Cosell. Date: November 1971 Formats: txt pdf Status: UNKNOWN
RFC 263	"Very Distant" Host interface
	Authors: A.M. McKenzie. Date: December 1971 Formats: txt pdf Status: UNKNOWN
RFC 264	The Data Transfer Protocol
	Authors: A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenize, B. Sundberg, D. Watson, J. White. Date: January 1972 Formats: txt pdf Obsoletes: RFC 0171 Obsoleted by: RFC 0354 Updated by: RFC 0310 Also: RFC 0265 Status: UNKNOWN
RFC 265	The File Transfer Protocol
	Authors: A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenzie, J. Melvin, B. Sundberg, D. Watson, J. White. Date: November 1971 Formats: txt pdf Obsoletes: RFC 0172 Obsoleted by: RFC 0354 Updated by: RFC 0281, RFC 0294, RFC 0310 Also: RFC 0264 Status: UNKNOWN
RFC 266	Network host status
	Authors: E. Westheimer. Date: November 1971 Formats: txt pdf Obsoletes: RFC 0255 Obsoleted by: RFC 0267 Status: UNKNOWN
RFC 267	Network Host Status
	Authors: E. Westheimer. Date: November 1971 Formats: txt pdf Obsoletes: RFC 0266 Obsoleted by: RFC 0287 Status: UNKNOWN
RFC 268	Graphics facilities information
	Authors: J. Postel. Date: November 1971 Formats: txt pdf Status: UNKNOWN
RFC 269	Some Experience with File Transfer
	Authors: H. Brodie. Date: December 1971 Formats: txt pdf Updates: RFC 0122 Status: UNKNOWN
RFC 270	Correction to BBN Report No. 1822 (NIC NO 7958)
	Authors: A.M. McKenzie. Date: January 1972 Formats: txt pdf Updates: NIC 7959 Status: UNKNOWN
RFC 271	IMP System change notifications
	Authors: B. Cosell. Date: January 1972 Formats: txt pdf Status: UNKNOWN
RFC 273	More on standard host names
	Authors: R.W. Watson. Date: October 1971 Formats: txt pdf Obsoletes: RFC 0237 Status: UNKNOWN
RFC 274	Establishing a local guide for network usage
	Authors: E. Forman. Date: November 1971 Formats: txt pdf Status: UNKNOWN
RFC 276	NIC course
	Authors: R.W. Watson. Date: November 1971 Formats: txt pdf Status: UNKNOWN
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 pdf Obsoletes: RFC 0221 Status: UNKNOWN
RFC 280	A Draft of Host Names
	Authors: R.W. Watson. Date: November 1971 Formats: txt pdf Status: UNKNOWN
RFC 281	Suggested addition to File Transfer Protocol
	Authors: A.M. McKenzie. Date: December 1971 Formats: txt pdf Updates: RFC 0265 Status: UNKNOWN
RFC 282	Graphics meeting report
	Authors: M.A. Padlipsky. Date: December 1971 Formats: txt pdf Status: UNKNOWN
RFC 283	NETRJT: Remote Job Service Protocol for TIPS
	Authors: R.T. Braden. Date: December 1971 Formats: txt pdf Updates: RFC 0189 Status: UNKNOWN
RFC 285	Network graphics
	Authors: D. Huff. Date: December 1971 Formats: txt pdf Status: UNKNOWN
RFC 286	Network Library Information System
	Authors: E. Forman. Date: December 1971 Formats: txt pdf Status: UNKNOWN
RFC 287	Status of Network Hosts
	Authors: E. Westheimer. Date: December 1971 Formats: txt pdf Obsoletes: RFC 0267 Obsoleted by: RFC 0288 Status: UNKNOWN
RFC 288	Network host status
	Authors: E. Westheimer. Date: January 1972 Formats: txt pdf Obsoletes: RFC 0287 Obsoleted by: RFC 0293 Updated by: RFC 0293 Status: UNKNOWN
RFC 289	What we hope is an official list of host names
	Authors: R.W. Watson. Date: December 1971 Formats: txt pdf Obsoleted by: RFC 0384 Status: UNKNOWN
RFC 290	Computer networks and data sharing: A bibliography
	Authors: A.P. Mullery. Date: January 1972 Formats: txt pdf Obsoletes: RFC 0243 Status: UNKNOWN
RFC 291	Data Management Meeting Announcement
	Authors: D.B. McKay. Date: January 1972 Formats: txt pdf Status: UNKNOWN
RFC 292	Graphics Protocol: Level 0 only
	Authors: J.C. Michener, I.W. Cotton, K.C. Kelley, D.E. Liddle, E. Meyer. Date: January 1972 Formats: txt pdf Obsoleted by: RFC 0493 Status: UNKNOWN
RFC 293	Network Host Status
	Authors: E. Westheimer. Date: January 1972 Formats: txt pdf Obsoletes: RFC 0288 Obsoleted by: RFC 0298 Updates: RFC 0288 Status: UNKNOWN
RFC 294	The Use of "Set Data Type" Transaction in File Transfer Protocol
	Authors: A.K. Bhushan. Date: January 1972 Formats: txt pdf Updates: RFC 0265 Status: UNKNOWN
RFC 295	Report of the Protocol Workshop, 12 October 1971
	Authors: J. Postel. Date: January 1972 Formats: txt pdf Status: UNKNOWN
RFC 296	DS-1 Display System
	Authors: D.E. Liddle. Date: January 1972 Formats: txt pdf Status: UNKNOWN
RFC 297	TIP Message Buffers
	Authors: D.C. Walden. Date: January 1972 Formats: txt pdf Status: UNKNOWN
RFC 298	Network host status
	Authors: E. Westheimer. Date: February 1972 Formats: txt pdf Obsoletes: RFC 0293 Obsoleted by: RFC 0306 Status: UNKNOWN
RFC 299	Information Management System
	Authors: D. Hopkin. Date: February 1972 Formats: txt pdf Status: UNKNOWN
RFC 300	ARPA Network mailing lists
	Authors: J.B. North. Date: January 1972 Formats: txt pdf Obsoletes: RFC 0211 Obsoleted by: RFC 0303 Status: UNKNOWN
RFC 301	BBN IMP (#5) and NCC Schedule March 4, 1971
	Authors: R. Alter. Date: February 1972 Formats: txt pdf Status: UNKNOWN
RFC 302	Exercising The ARPANET
	Authors: R.F. Bryan. Date: February 1972 Formats: txt pdf Status: UNKNOWN
RFC 303	ARPA Network mailing lists
	Authors: Network Information Center. Stanford Research Institute. Date: March 1972 Formats: txt pdf Obsoletes: RFC 0300 Obsoleted by: RFC 0329 Status: UNKNOWN
RFC 304	Data Management System Proposal for the ARPA Network
	Authors: D.B. McKay. Date: February 1972 Formats: txt pdf Status: UNKNOWN
RFC 305	Unknown Host Numbers
	Authors: R. Alter. Date: February 1972 Formats: txt pdf Status: UNKNOWN
RFC 306	Network host status
	Authors: E. Westheimer. Date: February 1972 Formats: txt pdf Obsoletes: RFC 0298 Obsoleted by: RFC 0315 Status: UNKNOWN
RFC 307	Using network Remote Job Entry
	Authors: E. Harslem. Date: February 1972 Formats: txt pdf Status: UNKNOWN
RFC 308	ARPANET host availability data
	Authors: M. Seriff. Date: March 1972 Formats: txt pdf Status: UNKNOWN
RFC 309	Data and File Transfer Workshop Announcement
	Authors: A.K. Bhushan. Date: March 1972 Formats: txt pdf Status: UNKNOWN
RFC 310	Another Look at Data and File Transfer Protocols
	Authors: A.K. Bhushan. Date: April 1972 Formats: txt pdf Updates: RFC 0264, RFC 0265 Status: UNKNOWN
RFC 311	New Console Attachments to the USCB Host
	Authors: R.F. Bryan. Date: February 1972 Formats: txt pdf Status: UNKNOWN
RFC 312	Proposed Change in IMP-to-Host Protocol
	Authors: A.M. McKenzie. Date: March 1972 Formats: txt pdf Status: UNKNOWN
RFC 313	Computer based instruction
	Authors: T.C. O'Sullivan. Date: March 1972 Formats: txt pdf Status: UNKNOWN
RFC 314	Network Graphics Working Group Meeting
	Authors: I.W. Cotton. Date: March 1972 Formats: txt pdf Status: UNKNOWN
RFC 315	Network Host Status
	Authors: E. Westheimer. Date: March 1972 Formats: txt pdf Obsoletes: RFC 0306 Obsoleted by: RFC 0319 Status: UNKNOWN
RFC 316	ARPA Network Data Management Working Group
	Authors: D.B. McKay, A.P. Mullery. Date: February 1972 Formats: txt pdf Status: UNKNOWN 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
	Authors: J. Postel. Date: March 1972 Formats: txt pdf Obsoleted by: RFC 0604 Status: UNKNOWN
RFC 318	Telnet Protocols
	Authors: J. Postel. Date: April 1972 Formats: txt pdf Updates: RFC 0158 Updated by: RFC 0435 Also: RFC 0139, RFC 0158 Status: UNKNOWN
RFC 319	Network Host Status
	Authors: E. Westheimer. Date: March 1972 Formats: txt pdf Obsoletes: RFC 0315 Updated by: RFC 0326 Status: UNKNOWN
RFC 320	Workshop on Hard Copy Line Graphics
	Authors: R. Reddy. Date: March 1972 Formats: txt pdf Status: UNKNOWN
RFC 321	CBI Networking Activity at MITRE
	Authors: P.M. Karp. Date: March 1972 Formats: txt pdf Status: UNKNOWN
RFC 322	Well known socket numbers
	Authors: V. Cerf, J. Postel. Date: March 1972 Formats: txt pdf Status: UNKNOWN
RFC 323	Formation of Network Measurement Group (NMG)
	Authors: V. Cerf. Date: March 1972 Formats: txt pdf Updated by: RFC 0388 Status: UNKNOWN
RFC 324	RJE Protocol meeting
	Authors: J. Postel. Date: April 1972 Formats: txt pdf Status: UNKNOWN
RFC 325	Network Remote Job Entry program - NETRJS
	Authors: G. Hicks. Date: April 1972 Formats: txt pdf Status: UNKNOWN
RFC 326	Network Host Status
	Authors: E. Westheimer. Date: April 1972 Formats: txt pdf Obsoleted by: RFC 0330 Updates: RFC 0319 Status: UNKNOWN
RFC 327	Data and File Transfer workshop notes
	Authors: A.K. Bhushan. Date: April 1972 Formats: txt pdf Status: UNKNOWN
RFC 328	Suggested Telnet Protocol Changes
	Authors: J. Postel. Date: April 1972 Formats: txt pdf Status: UNKNOWN
RFC 329	ARPA Network Mailing Lists
	Authors: Network Information Center. Stanford Research Institute. Date: May 1972 Formats: txt pdf Obsoletes: RFC 0303 Obsoleted by: RFC 0363 Status: UNKNOWN
RFC 330	Network Host Status
	Authors: E. Westheimer. Date: April 1972 Formats: txt pdf Obsoletes: RFC 0326 Updated by: RFC 0332 Status: UNKNOWN
RFC 331	IMP System Change Notification
	Authors: J.M. McQuillan. Date: April 1972 Formats: txt pdf Obsoleted by: RFC 0343 Status: UNKNOWN
RFC 332	Network Host Status
	Authors: E. Westheimer. Date: April 1972 Formats: txt pdf Obsoleted by: RFC 0342 Updates: RFC 0330 Status: UNKNOWN
RFC 333	Proposed experiment with a Message Switching Protocol
	Authors: R.D. Bressler, D. Murphy, D.C. Walden. Date: May 1972 Formats: txt pdf Status: UNKNOWN
RFC 334	Network Use on May 8
	Authors: A.M. McKenzie. Date: May 1972 Formats: txt pdf Status: UNKNOWN
RFC 335	New Interface - IMP/360
	Authors: R.F. Bryan. Date: May 1972 Formats: txt pdf Status: UNKNOWN
RFC 336	Level 0 Graphic Input Protocol
	Authors: I.W. Cotton. Date: May 1972 Formats: txt pdf Status: UNKNOWN
RFC 338	EBCDIC/ASCII Mapping for Network RJE
	Authors: R.T. Braden. Date: May 1972 Formats: txt pdf ps Status: UNKNOWN
RFC 339	MLTNET: A "Multi Telnet" Subsystem for Tenex
	Authors: R. Thomas. Date: May 1972 Formats: txt pdf Status: UNKNOWN
RFC 340	Proposed Telnet Changes
	Authors: T.C. O'Sullivan. Date: May 1972 Formats: txt pdf Also: RFC 0328 Status: UNKNOWN
RFC 342	Network Host Status
	Authors: E. Westheimer. Date: May 1972 Formats: txt pdf Obsoletes: RFC 0332 Obsoleted by: RFC 0344 Status: UNKNOWN
RFC 343	IMP System change notification
	Authors: A.M. McKenzie. Date: May 1972 Formats: txt pdf Obsoletes: RFC 0331 Obsoleted by: RFC 0359 Status: UNKNOWN
RFC 344	Network Host Status
	Authors: E. Westheimer. Date: May 1972 Formats: txt pdf Obsoletes: RFC 0342 Obsoleted by: RFC 0353 Status: UNKNOWN
RFC 345	Interest in Mixed Integer Programming (MPSX on NIC 360/91 at CCN)
	Authors: K.C. Kelley. Date: May 1972 Formats: txt pdf Status: UNKNOWN
RFC 346	Satellite Considerations
	Authors: J. Postel. Date: May 1972 Formats: txt pdf Status: UNKNOWN
RFC 347	Echo process
	Authors: J. Postel. Date: May 1972 Formats: txt pdf Status: UNKNOWN
RFC 348	Discard Process
	Authors: J. Postel. Date: May 1972 Formats: txt pdf Status: UNKNOWN
RFC 349	Proposed Standard Socket Numbers
	Authors: J. Postel. Date: May 1972 Formats: txt pdf Obsoleted by: RFC 0433 Also: RFC 0322, RFC 0204 Status: UNKNOWN
RFC 350	User Accounts for UCSB On-Line System
	Authors: R. Stoughton. Date: May 1972 Formats: txt pdf Status: UNKNOWN
RFC 351	Graphics information form for the ARPANET graphics resources notebook
	Authors: D. Crocker. Date: June 1972 Formats: txt pdf Status: UNKNOWN
RFC 352	TIP Site Information Form
	Authors: D. Crocker. Date: June 1972 Formats: txt pdf Status: UNKNOWN
RFC 353	Network host status
	Authors: E. Westheimer. Date: June 1972 Formats: txt pdf Obsoletes: RFC 0344 Obsoleted by: RFC 0362 Status: UNKNOWN
RFC 354	File Transfer Protocol
	Authors: A.K. Bhushan. Date: July 1972 Formats: txt pdf Obsoletes: RFC 0264, RFC 0265 Obsoleted by: RFC 0542 Updated by: RFC 0385, RFC 0454, RFC 0683 Status: UNKNOWN
RFC 355	Response to NWG/RFC 346
	Authors: J. Davidson. Date: June 1972 Formats: txt pdf Status: UNKNOWN
RFC 356	ARPA Network Control Center
	Authors: R. Alter. Date: June 1972 Formats: txt pdf Status: UNKNOWN
RFC 357	Echoing strategy for satellite links
	Authors: J. Davidson. Date: June 1972 Formats: txt pdf Status: UNKNOWN
RFC 359	Status of the Release of the New IMP System (2600)
	Authors: D.C. Walden. Date: June 1972 Formats: txt pdf Obsoletes: RFC 0343 Status: UNKNOWN
RFC 360	Proposed Remote Job Entry Protocol
	Authors: C. Holland. Date: June 1972 Formats: txt pdf Obsoleted by: RFC 0407 Status: UNKNOWN
RFC 361	Deamon Processes on Host 106
	Authors: R.D. Bressler. Date: July 1972 Formats: txt pdf Status: UNKNOWN
RFC 362	Network Host Status
	Authors: E. Westheimer. Date: June 1972 Formats: txt pdf Obsoletes: RFC 0353 Obsoleted by: RFC 0366 Status: UNKNOWN
RFC 363	ARPA Network mailing lists
	Authors: Network Information Center. Stanford Research Institute. Date: August 1972 Formats: txt pdf Obsoletes: RFC 0329 Obsoleted by: RFC 0402 Status: UNKNOWN
RFC 364	Serving remote users on the ARPANET
	Authors: M.D. Abrams. Date: July 1972 Formats: txt pdf Status: UNKNOWN
RFC 365	Letter to All TIP Users
	Authors: D.C. Walden. Date: July 1972 Formats: txt pdf Status: UNKNOWN
RFC 366	Network Host Status
	Authors: E. Westheimer. Date: July 1972 Formats: txt pdf Obsoletes: RFC 0362 Obsoleted by: RFC 0367 Status: UNKNOWN
RFC 367	Network host status
	Authors: E. Westheimer. Date: July 1972 Formats: txt pdf Obsoletes: RFC 0366 Obsoleted by: RFC 0370 Status: UNKNOWN
RFC 368	Comments on "Proposed Remote Job Entry Protocol"
	Authors: R.T. Braden. Date: July 1972 Formats: txt pdf Status: UNKNOWN
RFC 369	Evaluation of ARPANET services January-March, 1972
	Authors: J.R. Pickens. Date: July 1972 Formats: txt pdf Status: UNKNOWN
RFC 370	Network Host Status
	Authors: E. Westheimer. Date: July 1972 Formats: txt pdf Obsoletes: RFC 0367 Updated by: RFC 0376 Status: UNKNOWN
RFC 371	Demonstration at International Computer Communications Conference
	Authors: R.E. Kahn. Date: July 1972 Formats: txt pdf Status: UNKNOWN
RFC 372	Notes on a Conversation with Bob Kahn on the ICCC
	Authors: R.W. Watson. Date: July 1972 Formats: txt pdf Status: UNKNOWN
RFC 373	Arbitrary Character Sets
	Authors: J. McCarthy. Date: July 1972 Formats: txt pdf Status: UNKNOWN
RFC 374	IMP System Announcement
	Authors: A.M. McKenzie. Date: July 1972 Formats: txt pdf Status: UNKNOWN
RFC 376	Network Host Status
	Authors: E. Westheimer. Date: August 1972 Formats: txt pdf Updates: RFC 0370 Status: UNKNOWN
RFC 377	Using TSO via ARPA Network Virtual Terminal
	Authors: R.T. Braden. Date: August 1972 Formats: txt pdf Status: UNKNOWN
RFC 378	Traffic statistics (July 1972)
	Authors: A.M. McKenzie. Date: August 1972 Formats: txt pdf Obsoleted by: RFC 0391 Status: UNKNOWN
RFC 379	Using TSO at CCN
	Authors: R. Braden. Date: August 1972 Formats: txt pdf Status: UNKNOWN
RFC 381	Three aids to improved network operation
	Authors: J.M. McQuillan. Date: July 1972 Formats: txt pdf Updated by: RFC 0394 Status: UNKNOWN
RFC 382	Mathematical Software on the ARPA Network
	Authors: L. McDaniel. Date: August 1972 Formats: txt pdf Status: UNKNOWN
RFC 384	Official site idents for organizations in the ARPA Network
	Authors: J.B. North. Date: August 1972 Formats: txt pdf Obsoletes: RFC 0289 Status: UNKNOWN
RFC 385	Comments on the File Transfer Protocol
	Authors: A.K. Bhushan. Date: August 1972 Formats: txt pdf Updates: RFC 0354 Updated by: RFC 0414 Status: UNKNOWN
RFC 386	Letter to TIP users-2
	Authors: B. Cosell, D.C. Walden. Date: August 1972 Formats: txt pdf Status: UNKNOWN
RFC 387	Some experiences in implementing Network Graphics Protocol Level 0
	Authors: K.C. Kelley, J. Meir. Date: August 1972 Formats: txt pdf Updated by: RFC 0401 Status: UNKNOWN
RFC 388	NCP statistics
	Authors: V. Cerf. Date: August 1972 Formats: txt pdf Updates: RFC 0323 Status: UNKNOWN
RFC 389	UCLA Campus Computing Network Liaison Staff for ARPA Network
	Authors: B. Noble. Date: August 1972 Formats: txt pdf Obsoleted by: RFC 0423 Status: UNKNOWN
RFC 390	TSO Scenario
	Authors: R.T. Braden. Date: September 1972 Formats: txt pdf Status: UNKNOWN
RFC 391	Traffic statistics (August 1972)
	Authors: A.M. McKenzie. Date: September 1972 Formats: txt pdf Obsoletes: RFC 0378 Status: UNKNOWN
RFC 392	Measurement of host costs for transmitting network data
	Authors: G. Hicks, B.D. Wessler. Date: September 1972 Formats: txt pdf Status: UNKNOWN
RFC 393	Comments on Telnet Protocol Changes
	Authors: J.M. Winett. Date: October 1972 Formats: txt pdf Also: RFC 0109, RFC 0139, RFC 0158, RFC 0318, RFC 0328 Status: UNKNOWN
RFC 394	Two Proposed Changes to the IMP-Host Protocol
	Authors: J.M. McQuillan. Date: September 1972 Formats: txt pdf Updates: RFC 0381 Status: UNKNOWN
RFC 395	Switch Settings on IMPs and TIPs
	Authors: J.M. McQuillan. Date: October 1972 Formats: txt pdf Status: UNKNOWN
RFC 396	Network Graphics Working Group Meeting - Second Iteration
	Authors: S. Bunch. Date: November 1972 Formats: txt pdf Updated by: RFC 0474 Status: UNKNOWN
RFC 398	ICP Sockets
	Authors: J.R. Pickens, E. Faeh. Date: September 1972 Formats: txt pdf Status: UNKNOWN
RFC 399	SMFS Login and Logout
	Authors: M. Krilanovich. Date: September 1972 Formats: txt pdf Obsoleted by: RFC 0431 Updates: RFC 0122 Status: UNKNOWN
RFC 400	Traffic Statistics (September 1972)
	Authors: A.M. McKenzie. Date: October 1972 Formats: txt pdf Status: UNKNOWN
RFC 401	Conversion of NGP-0 Coordinates to Device Specific Coordinates
	Authors: J. Hansen. Date: October 1972 Formats: txt pdf Updates: RFC 0387 Status: UNKNOWN
RFC 402	ARPA Network Mailing Lists
	Authors: J.B. North. Date: October 1972 Formats: txt pdf Obsoletes: RFC 0363 Status: UNKNOWN
RFC 403	Desirability of a Network 1108 Service
	Authors: G. Hicks. Date: January 1973 Formats: txt pdf Status: UNKNOWN
RFC 404	Host Address Changes Involving Rand and ISI
	Authors: A.M. McKenzie. Date: October 1972 Formats: txt pdf Updated by: RFC 0405 Status: UNKNOWN
RFC 405	Correction to RFC 404
	Authors: A.M. McKenzie. Date: October 1972 Formats: txt pdf Updates: RFC 0404 Status: UNKNOWN
RFC 406	Scheduled IMP Software Releases
	Authors: J.M. McQuillan. Date: October 1972 Formats: txt pdf Status: UNKNOWN
RFC 407	Remote Job Entry Protocol
	Authors: R.D. Bressler, R. Guida, A.M. McKenzie. Date: October 1972 Formats: txt pdf Obsoletes: RFC 0360 Status: HISTORIC
RFC 408	NETBANK
	Authors: A.D. Owen, J. Postel. Date: October 1972 Formats: txt pdf Status: UNKNOWN
RFC 409	Tenex interface to UCSB's Simple-Minded File System
	Authors: J.E. White. Date: December 1972 Formats: txt pdf Status: UNKNOWN
RFC 410	Removal of the 30-Second Delay When Hosts Come Up
	Authors: J.M. McQuillan. Date: November 1972 Formats: txt pdf Status: UNKNOWN
RFC 411	New MULTICS Network Software Features
	Authors: M.A. Padlipsky. Date: November 1972 Formats: txt pdf Status: UNKNOWN
RFC 412	User FTP Documentation
	Authors: G. Hicks. Date: November 1972 Formats: txt pdf Status: UNKNOWN
RFC 413	Traffic statistics (October 1972)
	Authors: A.M. McKenzie. Date: November 1972 Formats: txt pdf Status: UNKNOWN
RFC 414	File Transfer Protocol (FTP) status and further comments
	Authors: A.K. Bhushan. Date: December 1972 Formats: txt pdf Updates: RFC 0385 Status: UNKNOWN
RFC 415	Tenex bandwidth
	Authors: H. Murray. Date: November 1972 Formats: txt pdf Status: UNKNOWN
RFC 416	ARC System Will Be Unavailable for Use During Thanksgiving Week
	Authors: J.C. Norton. Date: November 1972 Formats: txt pdf Status: UNKNOWN
RFC 417	Link usage violation
	Authors: J. Postel, C. Kline. Date: December 1972 Formats: txt pdf Status: UNKNOWN
RFC 418	Server File Transfer Under TSS/360 At NASA-Ames Research Center
	Authors: W. Hathaway. Date: November 1972 Formats: pdf Status: UNKNOWN
RFC 419	To: Network liaisons and station agents
	Authors: A. Vezza. Date: December 1972 Formats: txt pdf Status: UNKNOWN
RFC 420	CCA ICCC weather demo
	Authors: H. Murray. Date: January 1973 Formats: txt pdf Status: UNKNOWN
RFC 421	Software Consulting Service for Network Users
	Authors: A.M. McKenzie. Date: November 1972 Formats: txt pdf Status: UNKNOWN
RFC 422	Traffic statistics (November 1972)
	Authors: A.M. McKenzie. Date: December 1972 Formats: txt pdf Status: UNKNOWN
RFC 423	UCLA Campus Computing Network Liaison Staff for ARPANET
	Authors: B. Noble. Date: December 1972 Formats: txt pdf Obsoletes: RFC 0389 Status: UNKNOWN
RFC 425	"But my NCP costs $500 a day"
	Authors: R.D. Bressler. Date: December 1972 Formats: txt pdf Status: UNKNOWN
RFC 426	Reconnection Protocol
	Authors: R. Thomas. Date: January 1973 Formats: txt pdf Status: UNKNOWN
RFC 429	Character Generator Process
	Authors: J. Postel. Date: December 1972 Formats: txt pdf Status: UNKNOWN
RFC 430	Comments on File Transfer Protocol
	Authors: R.T. Braden. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 431	Update on SMFS Login and Logout
	Authors: M. Krilanovich. Date: December 1972 Formats: txt pdf Obsoletes: RFC 0399 Updates: RFC 0122 Status: UNKNOWN
RFC 432	Network logical map
	Authors: N. Neigus. Date: December 1972 Formats: txt pdf ps Status: UNKNOWN
RFC 433	Socket number list
	Authors: J. Postel. Date: December 1972 Formats: txt pdf Obsoletes: RFC 0349 Obsoleted by: RFC 0503 Status: UNKNOWN
RFC 434	IMP/TIP memory retrofit schedule
	Authors: A.M. McKenzie. Date: January 1973 Formats: txt pdf Obsoleted by: RFC 0447 Status: UNKNOWN
RFC 435	Telnet issues
	Authors: B. Cosell, D.C. Walden. Date: January 1973 Formats: txt pdf Updates: RFC 0318 Status: UNKNOWN
RFC 436	Announcement of RJS at UCSB
	Authors: M. Krilanovich. Date: January 1973 Formats: txt pdf Status: UNKNOWN
RFC 437	Data Reconfiguration Service at UCSB
	Authors: E. Faeh. Date: June 1973 Formats: txt pdf Status: UNKNOWN
RFC 438	FTP server-server interaction
	Authors: R. Thomas, R. Clements. Date: January 1973 Formats: txt pdf Status: UNKNOWN
RFC 439	PARRY encounters the DOCTOR
	Authors: V. Cerf. Date: January 1973 Formats: txt pdf Status: UNKNOWN
RFC 440	Scheduled network software maintenance
	Authors: D.C. Walden. Date: January 1973 Formats: txt pdf Status: UNKNOWN
RFC 441	Inter-Entity Communication - an experiment
	Authors: R.D. Bressler, R. Thomas. Date: January 1973 Formats: txt pdf Status: UNKNOWN
RFC 442	Current flow-control scheme for IMPSYS
	Authors: V. Cerf. Date: January 1973 Formats: txt pdf Updated by: RFC 0449 Status: UNKNOWN
RFC 443	Traffic statistics (December 1972)
	Authors: A.M. McKenzie. Date: January 1973 Formats: txt pdf Status: UNKNOWN
RFC 445	IMP/TIP preventive maintenance schedule
	Authors: A.M. McKenzie. Date: January 1973 Formats: txt pdf Status: UNKNOWN
RFC 446	Proposal to consider a network program resource notebook
	Authors: L.P. Deutsch. Date: January 1973 Formats: txt pdf Status: UNKNOWN
RFC 447	IMP/TIP memory retrofit schedule
	Authors: A.M. McKenzie. Date: January 1973 Formats: txt pdf Obsoletes: RFC 0434 Obsoleted by: RFC 0476 Status: UNKNOWN
RFC 448	Print files in FTP
	Authors: R.T. Braden. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 449	Current flow-control scheme for IMPSYS
	Authors: D.C. Walden. Date: January 1973 Formats: txt pdf Updates: RFC 0442 Status: UNKNOWN
RFC 450	MULTICS sampling timeout change
	Authors: M.A. Padlipsky. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 451	Tentative proposal for a Unified User Level Protocol
	Authors: M.A. Padlipsky. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 452	TELNET Command at Host LL
	Authors: J. Winett. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 453	Meeting announcement to discuss a network mail system
	Authors: M.D. Kudlick. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 454	File Transfer Protocol - meeting announcement and a new proposed document
	Authors: A.M. McKenzie. Date: February 1973 Formats: txt pdf Updates: RFC 0354 Status: UNKNOWN
RFC 455	Traffic statistics (January 1973)
	Authors: A.M. McKenzie. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 456	Memorandum: Date change of mail meeting
	Authors: M.D. Kudlick. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 457	TIPUG
	Authors: D.C. Walden. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 458	Mail retrieval via FTP
	Authors: R.D. Bressler, R. Thomas. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 459	Network questionnaires
	Authors: W. Kantrowitz. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 460	NCP survey
	Authors: C. Kline. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 461	Telnet Protocol meeting announcement
	Authors: A.M. McKenzie. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 462	Responding to user needs
	Authors: J. Iseli, D. Crocker. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 463	FTP comments and response to RFC 430
	Authors: A.K. Bhushan. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 464	Resource notebook framework
	Authors: M.D. Kudlick. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 466	Telnet logger/server for host LL-67
	Authors: J.M. Winett. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 467	Proposed change to Host-Host Protocol: Resynchronization of connection status
	Authors: J.D. Burchfiel, R.S. Tomlinson. Date: February 1973 Formats: txt pdf Updated by: RFC 0492 Status: UNKNOWN
RFC 468	FTP data compression
	Authors: R.T. Braden. Date: March 1973 Formats: txt pdf Status: UNKNOWN
RFC 469	Network mail meeting summary
	Authors: M.D. Kudlick. Date: March 1973 Formats: txt pdf Status: UNKNOWN
RFC 470	Change in socket for TIP news facility
	Authors: R. Thomas. Date: March 1973 Formats: txt pdf Status: UNKNOWN
RFC 471	Workshop on multi-site executive programs
	Authors: R. Thomas. Date: March 1973 Formats: txt pdf Status: UNKNOWN
RFC 472	Illinois' reply to Maxwell's request for graphics information (NIC 14925)
	Authors: S. Bunch. Date: March 1973 Formats: txt pdf Status: UNKNOWN
RFC 473	MIX and MIXAL?
	Authors: D.C. Walden. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 474	Announcement of NGWG meeting: Call for papers
	Authors: S. Bunch. Date: March 1973 Formats: txt pdf Updates: RFC 0396 Status: UNKNOWN
RFC 475	FTP and Network Mail System
	Authors: A.K. Bhushan. Date: March 1973 Formats: txt pdf Status: UNKNOWN
RFC 476	IMP/TIP memory retrofit schedule (rev 2)
	Authors: A.M. McKenzie. Date: March 1973 Formats: txt pdf Obsoletes: RFC 0447 Status: UNKNOWN
RFC 477	Remote Job Service at UCSB
	Authors: M. Krilanovich. Date: May 1973 Formats: txt pdf Status: UNKNOWN
RFC 478	FTP server-server interaction - II
	Authors: R.D. Bressler, R. Thomas. Date: March 1973 Formats: txt pdf Status: UNKNOWN
RFC 479	Use of FTP by the NIC Journal
	Authors: J.E. White. Date: March 1973 Formats: txt pdf Status: UNKNOWN
RFC 480	Host-dependent FTP parameters
	Authors: J.E. White. Date: March 1973 Formats: txt pdf Status: UNKNOWN
RFC 482	Traffic statistics (February 1973)
	Authors: A.M. McKenzie. Date: March 1973 Formats: txt pdf Updated by: RFC 0497 Status: UNKNOWN
RFC 483	Cancellation of the resource notebook framework meeting
	Authors: M.D. Kudlick. Date: March 1973 Formats: txt pdf Status: UNKNOWN
RFC 485	MIX and MIXAL at UCSB
	Authors: J.R. Pickens. Date: March 1973 Formats: txt pdf Status: UNKNOWN
RFC 486	Data transfer revisited
	Authors: R.D. Bressler. Date: March 1973 Formats: txt pdf Status: UNKNOWN
RFC 487	Free file transfer
	Authors: R.D. Bressler. Date: April 1973 Formats: txt pdf Status: UNKNOWN
RFC 488	NLS classes at network sites
	Authors: M.F. Auerbach. Date: March 1973 Formats: txt pdf Status: UNKNOWN
RFC 489	Comment on resynchronization of connection status proposal
	Authors: J. Postel. Date: March 1973 Formats: txt pdf Status: UNKNOWN
RFC 490	Surrogate RJS for UCLA-CCN
	Authors: J.R. Pickens. Date: March 1973 Formats: txt pdf Status: UNKNOWN
RFC 491	What is "Free"?
	Authors: M.A. Padlipsky. Date: April 1973 Formats: txt pdf Status: UNKNOWN
RFC 492	Response to RFC 467
	Authors: E. Meyer. Date: April 1973 Formats: txt pdf Updates: RFC 0467 Status: UNKNOWN
RFC 493	GRAPHICS PROTOCOL
	Authors: J.C. Michener, I.W. Cotton, K.C. Kelley, D.E. Liddle, E. Meyer. Date: April 1973 Formats: txt pdf Obsoletes: RFC 0292 Status: UNKNOWN
RFC 494	Availability of MIX and MIXAL in the Network
	Authors: D.C. Walden. Date: April 1973 Formats: txt pdf Status: UNKNOWN
RFC 495	Telnet Protocol specifications
	Authors: A.M. McKenzie. Date: May 1973 Formats: txt pdf Obsoletes: RFC 0158 Updated by: RFC 0562 Status: UNKNOWN
RFC 496	TNLS quick reference card is available
	Authors: M.F. Auerbach. Date: April 1973 Formats: txt pdf Status: UNKNOWN
RFC 497	Traffic Statistics (March 1973)
	Authors: A.M. McKenzie. Date: April 1973 Formats: txt pdf Updates: RFC 0482 Status: UNKNOWN
RFC 498	On mail service to CCN
	Authors: R.T. Braden. Date: April 1973 Formats: txt pdf Status: UNKNOWN
RFC 499	Harvard's network RJE
	Authors: B.R. Reussow. Date: April 1973 Formats: txt pdf Status: UNKNOWN
RFC 500	Integration of data management systems on a computer network
	Authors: A. Shoshani, I. Spiegler. Date: April 1973 Formats: txt pdf Status: UNKNOWN
RFC 501	Un-muddling "free file transfer"
	Authors: K.T. Pogran. Date: May 1973 Formats: txt pdf Status: UNKNOWN
RFC 503	Socket number list
	Authors: N. Neigus, J. Postel. Date: April 1973 Formats: txt pdf Obsoletes: RFC 0433 Obsoleted by: RFC 0739 Status: UNKNOWN
RFC 504	Distributed resources workshop announcement
	Authors: R. Thomas. Date: April 1973 Formats: txt pdf Status: UNKNOWN
RFC 505	Two solutions to a file transfer access problem
	Authors: M.A. Padlipsky. Date: June 1973 Formats: txt pdf Status: UNKNOWN
RFC 506	FTP command naming problem
	Authors: M.A. Padlipsky. Date: June 1973 Formats: txt pdf Status: UNKNOWN
RFC 508	Real-time data transmission on the ARPANET
	Authors: L. Pfeifer, J. McAfee. Date: May 1973 Formats: txt pdf Status: UNKNOWN
RFC 509	Traffic statistics (April 1973)
	Authors: A.M. McKenzie. Date: April 1973 Formats: txt pdf Status: UNKNOWN
RFC 510	Request for network mailbox addresses
	Authors: J.E. White. Date: May 1973 Formats: txt pdf Status: UNKNOWN
RFC 511	Enterprise phone service to NIC from ARPANET sites
	Authors: J.B. North. Date: May 1973 Formats: txt pdf Status: UNKNOWN
RFC 512	More on lost message detection
	Authors: W. Hathaway. Date: May 1973 Formats: txt pdf Status: UNKNOWN
RFC 513	Comments on the new Telnet specifications
	Authors: W. Hathaway. Date: May 1973 Formats: txt pdf Status: UNKNOWN
RFC 514	Network make-work
	Authors: W. Kantrowitz. Date: June 1973 Formats: txt pdf Status: UNKNOWN
RFC 515	Specifications for Datalanguage, Version 0/9
	Authors: R. Winter. Date: June 1973 Formats: txt pdf Status: UNKNOWN
RFC 516	Lost message detection
	Authors: J. Postel. Date: May 1973 Formats: txt pdf Status: UNKNOWN
RFC 518	ARPANET accounts
	Authors: N. Vaughan, E.J. Feinler. Date: June 1973 Formats: txt pdf Status: UNKNOWN
RFC 519	Resource Evaluation
	Authors: J.R. Pickens. Date: June 1973 Formats: txt pdf Status: UNKNOWN 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
	Authors: J.D. Day. Date: June 1973 Formats: txt pdf Status: UNKNOWN
RFC 521	Restricted use of IMP DDT
	Authors: A.M. McKenzie. Date: May 1973 Formats: txt pdf Status: UNKNOWN
RFC 522	Traffic Statistics (May 1973)
	Authors: A.M. McKenzie. Date: June 1973 Formats: txt pdf Updates: RFC 0509 Status: UNKNOWN
RFC 523	SURVEY is in operation again
	Authors: A.K. Bhushan. Date: June 1973 Formats: txt pdf Status: UNKNOWN
RFC 524	Proposed Mail Protocol
	Authors: J.E. White. Date: June 1973 Formats: txt pdf Status: UNKNOWN
RFC 525	MIT-MATHLAB meets UCSB-OLS -an example of resource sharing
	Authors: W. Parrish, J.R. Pickens. Date: June 1973 Formats: txt pdf ps Status: UNKNOWN
RFC 526	Technical meeting: Digital image processing software systems
	Authors: W.K. Pratt. Date: June 1973 Formats: txt pdf Status: UNKNOWN
RFC 527	ARPAWOCKY
	Authors: R. Merryman. Date: May 1973 Formats: txt pdf Status: UNKNOWN
RFC 528	Software checksumming in the IMP and network reliability
	Authors: J.M. McQuillan. Date: June 1973 Formats: txt pdf Status: UNKNOWN
RFC 529	Note on protocol synch sequences
	Authors: A.M. McKenzie, R. Thomas, R.S. Tomlinson, K.T. Pogran. Date: June 1973 Formats: txt pdf Status: UNKNOWN
RFC 530	Report on the Survey Project
	Authors: A.K. Bhushan. Date: June 1973 Formats: pdf Updates: RFC 0308, RFC 0523 Status: UNKNOWN
RFC 531	Feast or famine? A response to two recent RFC's about network information
	Authors: M.A. Padlipsky. Date: June 1973 Formats: txt pdf Status: UNKNOWN
RFC 532	UCSD-CC Server-FTP facility
	Authors: R.G. Merryman. Date: July 1973 Formats: txt pdf Status: UNKNOWN
RFC 533	Message-ID numbers
	Authors: D.C. Walden. Date: July 1973 Formats: txt pdf Status: UNKNOWN
RFC 534	Lost message detection
	Authors: D.C. Walden. Date: July 1973 Formats: txt pdf Status: UNKNOWN
RFC 535	Comments on File Access Protocol
	Authors: R. Thomas. Date: July 1973 Formats: txt pdf Status: UNKNOWN
RFC 537	Announcement of NGG meeting July 16-17
	Authors: S. Bunch. Date: June 1973 Formats: txt pdf Status: UNKNOWN
RFC 538	Traffic statistics (June 1973)
	Authors: A.M. McKenzie. Date: July 1973 Formats: txt pdf Updated by: RFC 0556 Status: UNKNOWN
RFC 539	Thoughts on the mail protocol proposed in RFC 524
	Authors: D. Crocker, J. Postel. Date: July 1973 Formats: txt pdf Status: UNKNOWN
RFC 542	File Transfer Protocol
	Authors: N. Neigus. Date: August 1973 Formats: txt pdf Obsoletes: RFC 0354 Obsoleted by: RFC 0765 Updated by: RFC 0614, RFC 0640 Also: RFC 0454, RFC 0495 Status: UNKNOWN
RFC 543	Network journal submission and delivery
	Authors: N.D. Meyer. Date: July 1973 Formats: txt pdf Status: UNKNOWN
RFC 544	Locating on-line documentation at SRI-ARC
	Authors: N.D. Meyer, K. Kelley. Date: July 1973 Formats: txt pdf Status: UNKNOWN
RFC 545	Of what quality be the UCSB resources evaluators?
	Authors: J.R. Pickens. Date: July 1973 Formats: txt pdf Status: UNKNOWN
RFC 546	Tenex load averages for July 1973
	Authors: R. Thomas. Date: August 1973 Formats: txt pdf ps Status: UNKNOWN
RFC 547	Change to the Very Distant Host specification
	Authors: D.C. Walden. Date: August 1973 Formats: txt pdf Status: UNKNOWN
RFC 548	Hosts using the IMP Going Down message
	Authors: D.C. Walden. Date: August 1973 Formats: txt pdf Status: UNKNOWN
RFC 549	Minutes of Network Graphics Group meeting, 15-17 July 1973
	Authors: J.C. Michener. Date: July 1973 Formats: txt pdf Status: UNKNOWN
RFC 550	NIC NCP experiment
	Authors: L.P. Deutsch. Date: August 1973 Formats: txt pdf Status: UNKNOWN
RFC 551	NYU, ANL, and LBL Joining the Net
	Authors: Y. Feinroth, R. Fink. Date: August 1973 Formats: txt pdf Status: UNKNOWN
RFC 552	Single access to standard protocols
	Authors: A.D. Owen. Date: July 1973 Formats: txt pdf Status: UNKNOWN
RFC 553	Draft design for a text/graphics protocol
	Authors: C.H. Irby, K. Victor. Date: July 1973 Formats: txt pdf Status: UNKNOWN
RFC 555	Responses to critiques of the proposed mail protocol
	Authors: J.E. White. Date: July 1973 Formats: txt pdf Status: UNKNOWN
RFC 556	Traffic Statistics (July 1973)
	Authors: A.M. McKenzie. Date: August 1973 Formats: txt pdf Updates: RFC 0538 Status: UNKNOWN
RFC 557	REVELATIONS IN NETWORK HOST MEASUREMENTS
	Authors: B.D. Wessler. Date: August 1973 Formats: txt pdf Status: UNKNOWN
RFC 559	Comments on The New Telnet Protocol and its Implementation
	Authors: A.K. Bushan. Date: August 1973 Formats: txt pdf Status: UNKNOWN
RFC 560	Remote Controlled Transmission and Echoing Telnet option
	Authors: D. Crocker, J. Postel. Date: August 1973 Formats: txt pdf Updated by: RFC 0581 Status: UNKNOWN
RFC 561	Standardizing Network Mail Headers
	Authors: A.K. Bhushan, K.T. Pogran, R.S. Tomlinson, J.E. White. Date: September 1973 Formats: txt pdf Updated by: RFC 0680 Status: UNKNOWN
RFC 562	Modifications to the TELNET Specification
	Authors: A.M. McKenzie. Date: August 1973 Formats: txt pdf Updates: RFC 0495 Status: UNKNOWN
RFC 563	Comments on the RCTE Telnet option
	Authors: J. Davidson. Date: August 1973 Formats: txt pdf Status: UNKNOWN
RFC 565	Storing network survey data at the datacomputer
	Authors: D. Cantor. Date: August 1973 Formats: txt pdf Status: UNKNOWN
RFC 566	Traffic statistics (August 1973)
	Authors: A.M. McKenzie. Date: September 1973 Formats: txt pdf Updated by: RFC 0579 Status: UNKNOWN
RFC 567	Cross Country Network Bandwidth
	Authors: L.P. Deutsch. Date: September 1973 Formats: txt pdf Updated by: RFC 0568 Status: UNKNOWN
RFC 568	Response to RFC 567 - cross country network bandwidth
	Authors: J.M. McQuillan. Date: September 1973 Formats: txt pdf Updates: RFC 0567 Status: UNKNOWN
RFC 569	NETED: A Common Editor for the ARPA Network
	Authors: M.A. Padlipsky. Date: October 1973 Formats: txt pdf Status: HISTORIC
RFC 570	Experimental input mapping between NVT ASCII and UCSB On Line System
	Authors: J.R. Pickens. Date: October 1973 Formats: txt pdf ps Status: UNKNOWN
RFC 571	TENEX FTP PROBLEM
	Authors: R. Braden. Date: November 1973 Formats: txt pdf Status: UNKNOWN
RFC 573	DATA AND FILE TRANSFER - SOME MEASUREMENT RESULTS
	Authors: A. Bhushan. Date: September 1973 Formats: txt pdf Status: UNKNOWN
RFC 574	Announcement of a Mail Facility at UCSB
	Authors: M. Krilanovich. Date: September 1973 Formats: txt pdf Status: UNKNOWN
RFC 576	Proposal for modifying linking
	Authors: K. Victor. Date: September 1973 Formats: txt pdf Status: UNKNOWN
RFC 577	Mail priority
	Authors: D. Crocker. Date: October 1973 Formats: txt pdf Status: UNKNOWN
RFC 578	Using MIT-Mathlab MACSYMA from MIT-DMS Muddle
	Authors: A.K. Bhushan, N.D. Ryan. Date: October 1973 Formats: txt pdf Status: UNKNOWN
RFC 579	Traffic statistics (September 1973)
	Authors: A.M. McKenzie. Date: November 1973 Formats: txt pdf Updates: RFC 0566 Updated by: RFC 0586 Status: UNKNOWN
RFC 580	Note to Protocol Designers and Implementers
	Authors: J. Postel. Date: October 1973 Formats: txt pdf Updated by: RFC 0582 Status: UNKNOWN
RFC 581	Corrections to RFC 560: Remote Controlled Transmission and Echoing Telnet Option
	Authors: D. Crocker, J. Postel. Date: November 1973 Formats: txt pdf Updates: RFC 0560 Status: UNKNOWN
RFC 582	Comments on RFC 580: Machine readable protocols
	Authors: R. Clements. Date: November 1973 Formats: txt pdf Updates: RFC 0580 Status: UNKNOWN
RFC 584	Charter for ARPANET Users Interest Working Group
	Authors: J. Iseli, D. Crocker, N. Neigus. Date: November 1973 Formats: txt pdf Status: UNKNOWN
RFC 585	ARPANET users interest working group meeting
	Authors: D. Crocker, N. Neigus, E.J. Feinler, J. Iseli. Date: November 1973 Formats: txt pdf Status: UNKNOWN
RFC 586	Traffic statistics (October 1973)
	Authors: A.M. McKenzie. Date: November 1973 Formats: txt pdf Updates: RFC 0579 Status: UNKNOWN
RFC 587	Announcing New Telnet Options
	Authors: J. Postel. Date: November 1973 Formats: txt pdf Status: UNKNOWN
RFC 588	London Node Is Now Up
	Authors: A. Stokes. Date: October 1973 Formats: txt pdf Status: UNKNOWN
RFC 589	CCN NETRJS server messages to remote user
	Authors: R.T. Braden. Date: November 1973 Formats: txt pdf Status: UNKNOWN
RFC 590	MULTICS address change
	Authors: M.A. Padlipsky. Date: November 1973 Formats: txt pdf Status: UNKNOWN
RFC 591	Addition to the Very Distant Host specifications
	Authors: D.C. Walden. Date: November 1973 Formats: txt pdf Status: UNKNOWN
RFC 592	Some thoughts on system design to facilitate resource sharing
	Authors: R.W. Watson. Date: November 1973 Formats: txt pdf Status: UNKNOWN
RFC 593	Telnet and FTP implementation schedule change
	Authors: A.M. McKenzie, J. Postel. Date: November 1973 Formats: txt pdf Status: UNKNOWN
RFC 594	Speedup of Host-IMP interface
	Authors: J.D. Burchfiel. Date: December 1973 Formats: txt pdf Status: UNKNOWN
RFC 595	Second thoughts in defense of the Telnet Go-Ahead
	Authors: W. Hathaway. Date: December 1973 Formats: txt pdf Status: UNKNOWN
RFC 596	Second thoughts on Telnet Go-Ahead
	Authors: E.A. Taft. Date: December 1973 Formats: txt pdf Status: UNKNOWN
RFC 597	Host status
	Authors: N. Neigus, E.J. Feinler. Date: December 1973 Formats: txt pdf Updated by: RFC 0603 Status: UNKNOWN
RFC 598	RFC index - December 5, 1973
	Authors: Network Information Center. Stanford Research Institute. Date: December 1973 Formats: pdf Status: UNKNOWN
RFC 599	Update on NETRJS
	Authors: R.T. Braden. Date: December 1973 Formats: txt pdf Obsoletes: RFC 0189 Obsoleted by: RFC 0740 Status: UNKNOWN
RFC 600	Interfacing an Illinois plasma terminal to the ARPANET
	Authors: A. Berggreen. Date: November 1973 Formats: txt pdf Status: UNKNOWN
RFC 601	Traffic statistics (November 1973)
	Authors: A.M. McKenzie. Date: December 1973 Formats: txt pdf Status: UNKNOWN
RFC 602	"The stockings were hung by the chimney with care"
	Authors: R.M. Metcalfe. Date: December 1973 Formats: txt pdf Status: UNKNOWN Susceptibility of ARPANET to security violations.
RFC 603	Response to RFC 597: Host status
	Authors: J.D. Burchfiel. Date: December 1973 Formats: txt pdf Updates: RFC 0597 Updated by: RFC 0613 Status: UNKNOWN Questions about the ARPANET topology described in RFC 597.
RFC 604	Assigned link numbers
	Authors: J. Postel. Date: December 1973 Formats: txt pdf Obsoletes: RFC 0317 Obsoleted by: RFC 0739 Status: UNKNOWN Modifies official host-host protocol. Replaces RFC 377.
RFC 606	Host names on-line
	Authors: L.P. Deutsch. Date: December 1973 Formats: txt pdf Status: UNKNOWN Resolving differences in hostname-address mappings; see also RFCs 627, 625, 623 and 608.
RFC 607	Comments on the File Transfer Protocol
	Authors: M. Krilanovich, G. Gregg. Date: January 1974 Formats: txt pdf Obsoleted by: RFC 0624 Updated by: RFC 0614 Status: UNKNOWN An old version; see RFC 624; see also RFCs 614, 542 and 640.
RFC 608	Host names on-line
	Authors: M.D. Kudlick. Date: January 1974 Formats: txt pdf Obsoleted by: RFC 0810 Status: UNKNOWN Response to RFC 606; see also RFCs 627, 625 and 623.
RFC 609	Statement of upcoming move of NIC/NLS service
	Authors: B. Ferguson. Date: January 1974 Formats: txt pdf Status: UNKNOWN See also RFCs 621 and 620.
RFC 610	Further datalanguage design concepts
	Authors: R. Winter, J. Hill, W. Greiff. Date: December 1973 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN
RFC 613	Network connectivity: A response to RFC 603
	Authors: A.M. McKenzie. Date: January 1974 Formats: txt pdf Updates: RFC 0603 Status: UNKNOWN
RFC 614	Response to RFC 607: "Comments on the File Transfer Protocol"
	Authors: K.T. Pogran, N. Neigus. Date: January 1974 Formats: txt pdf Updates: RFC 0542, RFC 0607 Status: UNKNOWN See also RFCs 624, 542 and 640.
RFC 615	Proposed Network Standard Data Pathname syntax
	Authors: D. Crocker. Date: March 1974 Formats: txt pdf Obsoleted by: RFC 0645 Status: UNKNOWN
RFC 616	LATEST NETWORK MAPS
	Authors: D. Walden. Date: February 1973 Formats: txt pdf Status: UNKNOWN
RFC 617	Note on socket number assignment
	Authors: E.A. Taft. Date: February 1974 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN Actual measurements of round-trip times.
RFC 620	Request for monitor host table updates
	Authors: B. Ferguson. Date: March 1974 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN See also RFCs 620 and 609.
RFC 622	Scheduling IMP/TIP down time
	Authors: A.M. McKenzie. Date: March 1974 Formats: txt pdf Status: UNKNOWN Modification of previous policy.
RFC 623	Comments on on-line host name service
	Authors: M. Krilanovich. Date: February 1974 Formats: txt pdf Status: UNKNOWN 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 pdf Obsoletes: RFC 0607 Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN
RFC 627	ASCII text file of hostnames
	Authors: M.D. Kudlick, E.J. Feinler. Date: March 1974 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN
RFC 629	Scenario for using the Network Journal
	Authors: J.B. North. Date: March 1974 Formats: txt pdf Status: UNKNOWN
RFC 630	FTP error code usage for more reliable mail service
	Authors: J. Sussman. Date: April 1974 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN
RFC 632	Throughput degradations for single packet messages
	Authors: H. Opderbeck. Date: May 1974 Formats: txt pdf Status: UNKNOWN
RFC 633	IMP/TIP preventive maintenance schedule
	Authors: A.M. McKenzie. Date: March 1974 Formats: txt pdf Obsoleted by: RFC 0638 Status: UNKNOWN An old version; see RFC 638.
RFC 634	Change in network address for Haskins Lab
	Authors: A.M. McKenzie. Date: April 1974 Formats: txt pdf Status: UNKNOWN
RFC 635	Assessment of ARPANET protocols
	Authors: V. Cerf. Date: April 1974 Formats: txt pdf Status: UNKNOWN
RFC 636	TIP/Tenex reliability improvements
	Authors: J.D. Burchfiel, B. Cosell, R.S. Tomlinson, D.C. Walden. Date: June 1974 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN
RFC 638	IMP/TIP preventive maintenance schedule
	Authors: A.M. McKenzie. Date: April 1974 Formats: txt pdf Obsoletes: RFC 0633 Status: UNKNOWN Corrects RFC 633.
RFC 640	Revised FTP reply codes
	Authors: J. Postel. Date: June 1974 Formats: txt pdf Updates: RFC 0542 Status: UNKNOWN Updates RFC 542.
RFC 642	Ready line philosophy and implementation
	Authors: J.D. Burchfiel. Date: July 1974 Formats: txt pdf Status: UNKNOWN
RFC 643	Network Debugging Protocol
	Authors: E. Mader. Date: July 1974 Formats: txt pdf Status: UNKNOWN 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
	Authors: R. Thomas. Date: July 1974 Formats: txt pdf Status: UNKNOWN
RFC 645	Network Standard Data Specification syntax
	Authors: D. Crocker. Date: June 1974 Formats: txt pdf Obsoletes: RFC 0615 Status: UNKNOWN
RFC 647	Proposed protocol for connecting host computers to ARPA-like networks via front end processors
	Authors: M.A. Padlipsky. Date: November 1974 Formats: txt pdf Status: UNKNOWN
RFC 651	Revised Telnet status option
	Authors: D. Crocker. Date: October 1974 Formats: txt pdf Obsoleted by: RFC 0859 Status: UNKNOWN
RFC 652	Telnet output carriage-return disposition option
	Authors: D. Crocker. Date: October 1974 Formats: txt pdf Status: HISTORIC
RFC 653	Telnet output horizontal tabstops option
	Authors: D. Crocker. Date: October 1974 Formats: txt pdf Status: HISTORIC
RFC 654	Telnet output horizontal tab disposition option
	Authors: D. Crocker. Date: October 1974 Formats: txt pdf Status: HISTORIC
RFC 655	Telnet output formfeed disposition option
	Authors: D. Crocker. Date: October 1974 Formats: txt pdf Status: HISTORIC
RFC 656	Telnet output vertical tabstops option
	Authors: D. Crocker. Date: October 1974 Formats: txt pdf Status: HISTORIC
RFC 657	Telnet output vertical tab disposition option
	Authors: D. Crocker. Date: October 1974 Formats: txt pdf Status: HISTORIC
RFC 658	Telnet output linefeed disposition
	Authors: D. Crocker. Date: October 1974 Formats: txt pdf Status: HISTORIC
RFC 659	Announcing additional Telnet options
	Authors: J. Postel. Date: October 1974 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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
	Authors: J. Postel. Date: November 1974 Formats: txt pdf Updated by: RFC 0694 Status: UNKNOWN
RFC 662	Performance improvement in ARPANET file transfers from Multics
	Authors: R. Kanodia. Date: November 1974 Formats: txt pdf Status: UNKNOWN Experimenting with host output buffers to improve throughput.
RFC 663	Lost message detection and recovery protocol
	Authors: R. Kanodia. Date: November 1974 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN
RFC 667	Host Ports
	Authors: S.G. Chipman. Date: December 1974 Formats: txt pdf Status: UNKNOWN
RFC 669	November, 1974, survey of New-Protocol Telnet servers
	Authors: D.W. Dodds. Date: December 1974 Formats: txt pdf Updates: RFC 0702 Updated by: RFC 0679 Status: UNKNOWN An earlier poll of Telnet server implementation status. Updates RFC 702; see also RFCs 703 and 679.
RFC 671	Note on Reconnection Protocol
	Authors: R. Schantz. Date: December 1974 Formats: txt pdf Status: UNKNOWN
RFC 672	Multi-site data collection facility
	Authors: R. Schantz. Date: December 1974 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 675	Specification of Internet Transmission Control Program
	Authors: V. Cerf, Y. Dalal, C. Sunshine. Date: December 1974 Formats: txt pdf Status: UNKNOWN The first detailed specification of TCP; see RFC 793.
RFC 677	Maintenance of duplicate databases
	Authors: P.R. Johnson, R. Thomas. Date: January 1975 Formats: txt pdf Status: UNKNOWN
RFC 678	Standard file formats
	Authors: J. Postel. Date: December 1974 Formats: txt pdf Status: UNKNOWN For transmission of documents across different environments.
RFC 679	February, 1975, survey of New-Protocol Telnet servers
	Authors: D.W. Dodds. Date: February 1975 Formats: txt pdf Updates: RFC 0669 Updated by: RFC 0703 Status: UNKNOWN
RFC 680	Message Transmission Protocol
	Authors: T.H. Myer, D.A. Henderson. Date: April 1975 Formats: txt pdf Updates: RFC 0561 Status: UNKNOWN
RFC 681	Network UNIX
	Authors: S. Holmgren. Date: March 1975 Formats: txt pdf Status: UNKNOWN Capabilities as an ARPANET Mini-Host: standard I/O, Telnet, NCP, Hardware/Software requirements, reliability, availability.
RFC 683	FTPSRV - Tenex extension for paged files
	Authors: R. Clements. Date: April 1975 Formats: txt pdf Updates: RFC 0354 Status: UNKNOWN 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
	Authors: R. Schantz. Date: April 1975 Formats: txt pdf Status: UNKNOWN Issues in designing distributed computing systems. Shortcomings of RFC 674; see also RFCs 542 and 354.
RFC 685	Response time in cross network debugging
	Authors: M. Beeler. Date: April 1975 Formats: txt pdf Status: UNKNOWN The contribution of ARPANET communication to response time.
RFC 686	Leaving well enough alone
	Authors: B. Harvey. Date: May 1975 Formats: txt pdf Status: UNKNOWN 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
	Authors: D.C. Walden. Date: June 1975 Formats: txt pdf Obsoleted by: RFC 0704 Updated by: RFC 0690 Status: UNKNOWN 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
	Authors: D.C. Walden. Date: June 1975 Formats: txt pdf Status: UNKNOWN
RFC 689	Tenex NCP finite state machine for connections
	Authors: R. Clements. Date: May 1975 Formats: txt pdf Status: UNKNOWN Describes the internal states of an NCP connection in the TENEX implementation.
RFC 690	Comments on the proposed Host/IMP Protocol changes
	Authors: J. Postel. Date: June 1975 Formats: txt pdf Updates: RFC 0687 Updated by: RFC 0692 Status: UNKNOWN Comments on suggestions in RFC 687; see also RFCs 692 and 696.
RFC 691	One more try on the FTP
	Authors: B. Harvey. Date: June 1975 Formats: txt pdf Status: UNKNOWN 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)
	Authors: S.M. Wolfe. Date: June 1975 Formats: txt pdf Updates: RFC 0690 Status: UNKNOWN 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
	Authors: J. Postel. Date: June 1975 Formats: txt pdf Updates: RFC 0661 Status: UNKNOWN
RFC 695	Official change in Host-Host Protocol
	Authors: M. Krilanovich. Date: July 1975 Formats: txt pdf Status: UNKNOWN Corrects ambiguity concerning the ERR command; changes NIC 8246 and NIC 7104.
RFC 696	Comments on the IMP/Host and Host/IMP Protocol changes
	Authors: V.G. Cerf. Date: July 1975 Formats: txt pdf Status: UNKNOWN
RFC 697	CWD command of FTP
	Authors: J. Lieb. Date: July 1975 Formats: txt pdf Status: UNKNOWN Discusses FTP login access to "files only" directories.
RFC 698	Telnet extended ASCII option
	Authors: T. Mock. Date: July 1975 Formats: txt pdf Obsoleted by: RFC 5198 Status: PROPOSED STANDARD Describes an option to allow transmission of a special kind of extended ASCII used at the Stanford AI and MIT AI Labs.
RFC 699	Request For Comments summary notes: 600-699
	Authors: J. Postel, J. Vernon. Date: November 1982 Formats: txt pdf Status: INFORMATIONAL
RFC 700	Protocol experiment
	Authors: E. Mader, W.W. Plummer, R.S. Tomlinson. Date: August 1974 Formats: txt pdf Status: UNKNOWN
RFC 701	August, 1974, survey of New-Protocol Telnet servers
	Authors: D.W. Dodds. Date: August 1974 Formats: txt pdf Updated by: RFC 0702 Status: UNKNOWN
RFC 702	September, 1974, survey of New-Protocol Telnet servers
	Authors: D.W. Dodds. Date: September 1974 Formats: txt pdf Updates: RFC 0701 Updated by: RFC 0669 Status: UNKNOWN
RFC 703	July, 1975, survey of New-Protocol Telnet Servers
	Authors: D.W. Dodds. Date: July 1975 Formats: txt pdf Updates: RFC 0679 Status: UNKNOWN
RFC 704	IMP/Host and Host/IMP Protocol change
	Authors: P.J. Santos. Date: September 1975 Formats: txt pdf Obsoletes: RFC 0687 Status: UNKNOWN
RFC 705	Front-end Protocol B6700 version
	Authors: R.F. Bryan. Date: November 1975 Formats: txt pdf Status: UNKNOWN
RFC 706	On the junk mail problem
	Authors: J. Postel. Date: November 1975 Formats: txt pdf Status: UNKNOWN
RFC 707	High-level framework for network-based resource sharing
	Authors: J.E. White. Date: December 1975 Formats: txt pdf Status: UNKNOWN
RFC 708	Elements of a Distributed Programming System
	Authors: J.E. White. Date: January 1976 Formats: txt pdf Status: UNKNOWN
RFC 712	Distributed Capability Computing System (DCCS)
	Authors: J.E. Donnelley. Date: February 1976 Formats: txt pdf Status: UNKNOWN
RFC 713	MSDTP-Message Services Data Transmission Protocol
	Authors: J. Haverty. Date: April 1976 Formats: txt pdf Status: UNKNOWN
RFC 714	Host-Host Protocol for an ARPANET-Type Network
	Authors: A.M. McKenzie. Date: April 1976 Formats: txt pdf Status: UNKNOWN
RFC 716	Interim Revision to Appendix F of BBN 1822
	Authors: D.C. Walden, J. Levin. Date: May 1976 Formats: txt pdf Status: UNKNOWN
RFC 717	Assigned Network Numbers
	Authors: J. Postel. Date: July 1976 Formats: txt pdf Status: HISTORIC
RFC 718	Comments on RCTE from the Tenex Implementation Experience
	Authors: J. Postel. Date: June 1976 Formats: txt pdf Status: UNKNOWN
RFC 719	Discussion on RCTE
	Authors: J. Postel. Date: July 1976 Formats: txt pdf Status: UNKNOWN
RFC 720	Address Specification Syntax for Network Mail
	Authors: D. Crocker. Date: August 1976 Formats: txt pdf Status: UNKNOWN
RFC 721	Out-of-Band Control Signals in a Host-to-Host Protocol
	Authors: L.L. Garlick. Date: September 1976 Formats: txt pdf Status: UNKNOWN
RFC 722	Thoughts on Interactions in Distributed Services
	Authors: J. Haverty. Date: September 1976 Formats: txt pdf Status: UNKNOWN
RFC 724	Proposed official standard for the format of ARPA Network messages
	Authors: D. Crocker, K.T. Pogran, J. Vittal, D.A. Henderson. Date: May 1977 Formats: txt pdf Obsoleted by: RFC 0733 Status: UNKNOWN
RFC 725	RJE protocol for a resource sharing network
	Authors: J.D. Day, G.R. Grossman. Date: March 1977 Formats: txt pdf Status: UNKNOWN
RFC 726	Remote Controlled Transmission and Echoing Telnet option
	Authors: J. Postel, D. Crocker. Date: March 1977 Formats: txt pdf Status: PROPOSED STANDARD
RFC 727	Telnet logout option
	Authors: M.R. Crispin. Date: April 1977 Formats: txt pdf Status: PROPOSED STANDARD
RFC 728	Minor pitfall in the Telnet Protocol
	Authors: J.D. Day. Date: April 1977 Formats: txt pdf Status: UNKNOWN
RFC 729	Telnet byte macro option
	Authors: D. Crocker. Date: May 1977 Formats: txt pdf Obsoleted by: RFC 0735 Status: UNKNOWN
RFC 730	Extensible field addressing
	Authors: J. Postel. Date: May 1977 Formats: txt pdf Status: UNKNOWN
RFC 731	Telnet Data Entry Terminal option
	Authors: J.D. Day. Date: June 1977 Formats: txt pdf Obsoleted by: RFC 0732 Status: UNKNOWN
RFC 732	Telnet Data Entry Terminal option
	Authors: J.D. Day. Date: September 1977 Formats: txt pdf Obsoletes: RFC 0731 Updated by: RFC 1043 Status: UNKNOWN
RFC 733	Standard for the format of ARPA network text messages
	Authors: D. Crocker, J. Vittal, K.T. Pogran, D.A. Henderson. Date: November 1977 Formats: txt pdf Obsoletes: RFC 0724 Obsoleted by: RFC 0822 Status: UNKNOWN
RFC 734	SUPDUP Protocol
	Authors: M.R. Crispin. Date: October 1977 Formats: txt pdf Status: HISTORIC
RFC 735	Revised Telnet byte macro option
	Authors: D. Crocker, R.H. Gumpertz. Date: November 1977 Formats: txt pdf Obsoletes: RFC 0729 Status: PROPOSED STANDARD
RFC 736	Telnet SUPDUP option
	Authors: M.R. Crispin. Date: October 1977 Formats: txt pdf Status: PROPOSED STANDARD
RFC 737	FTP extension: XSEN
	Authors: K. Harrenstien. Date: October 1977 Formats: txt pdf Status: UNKNOWN
RFC 738	Time server
	Authors: K. Harrenstien. Date: October 1977 Formats: txt pdf Status: UNKNOWN
RFC 739	Assigned numbers
	Authors: J. Postel. Date: November 1977 Formats: txt pdf Obsoletes: RFC 0604, RFC 0503 Obsoleted by: RFC 0750 Status: HISTORIC
RFC 740	NETRJS Protocol
	Authors: R.T. Braden. Date: November 1977 Formats: txt pdf Obsoletes: RFC 0599 Status: HISTORIC
RFC 741	Specifications for the Network Voice Protocol (NVP)
	Authors: D. Cohen. Date: November 1977 Formats: txt pdf Status: UNKNOWN
RFC 742	NAME/FINGER Protocol
	Authors: K. Harrenstien. Date: December 1977 Formats: txt pdf Obsoleted by: RFC 1288, RFC 1196, RFC 1194 Status: UNKNOWN
RFC 743	FTP extension: XRSQ/XRCP
	Authors: K. Harrenstien. Date: December 1977 Formats: txt pdf Status: UNKNOWN
RFC 744	MARS - a Message Archiving and Retrieval Service
	Authors: J. Sattley. Date: January 1978 Formats: txt pdf Status: UNKNOWN
RFC 745	JANUS interface specifications
	Authors: M. Beeler. Date: March 1978 Formats: txt pdf Status: UNKNOWN
RFC 746	SUPDUP graphics extension
	Authors: R. Stallman. Date: March 1978 Formats: txt pdf Status: UNKNOWN
RFC 747	Recent extensions to the SUPDUP Protocol
	Authors: M.R. Crispin. Date: March 1978 Formats: txt pdf Status: UNKNOWN
RFC 748	Telnet randomly-lose option
	Authors: M.R. Crispin. Date: April 1 1978 Formats: txt pdf Status: UNKNOWN
RFC 749	Telnet SUPDUP-Output option
	Authors: B. Greenberg. Date: September 1978 Formats: txt pdf Status: PROPOSED STANDARD
RFC 750	Assigned numbers
	Authors: J. Postel. Date: September 1978 Formats: txt pdf Obsoletes: RFC 0739 Obsoleted by: RFC 0755 Status: HISTORIC
RFC 751	Survey of FTP mail and MLFL
	Authors: P.D. Lebling. Date: December 1978 Formats: txt pdf Status: UNKNOWN
RFC 752	Universal host table
	Authors: M.R. Crispin. Date: January 1979 Formats: txt pdf Status: UNKNOWN
RFC 753	Internet Message Protocol
	Authors: J. Postel. Date: March 1979 Formats: txt pdf Status: UNKNOWN
RFC 754	Out-of-net host addresses for mail
	Authors: J. Postel. Date: April 1979 Formats: txt pdf Status: UNKNOWN
RFC 755	Assigned numbers
	Authors: J. Postel. Date: May 1979 Formats: txt pdf Obsoletes: RFC 0750 Obsoleted by: RFC 0758 Status: HISTORIC
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 pdf Status: UNKNOWN
RFC 757	Suggested solution to the naming, addressing, and delivery problem for ARPANET message systems
	Authors: D.P. Deutsch. Date: September 1979 Formats: txt pdf Status: UNKNOWN
RFC 758	Assigned numbers
	Authors: J. Postel. Date: August 1979 Formats: txt pdf Obsoletes: RFC 0755 Obsoleted by: RFC 0762 Status: HISTORIC
RFC 759	Internet Message Protocol
	Authors: J. Postel. Date: August 1980 Formats: txt pdf Status: HISTORIC
RFC 760	DoD standard Internet Protocol
	Authors: J. Postel. Date: January 1980 Formats: txt pdf Obsoletes: IEN 123 Obsoleted by: RFC 0791 Updated by: RFC 0777 Status: UNKNOWN
RFC 761	DoD standard Transmission Control Protocol
	Authors: J. Postel. Date: January 1980 Formats: txt pdf Obsoleted by: RFC 0793 Status: UNKNOWN
RFC 762	Assigned numbers
	Authors: J. Postel. Date: January 1980 Formats: txt pdf Obsoletes: RFC 0758 Obsoleted by: RFC 0770 Status: HISTORIC
RFC 763	Role mailboxes
	Authors: M.D. Abrams. Date: May 1980 Formats: txt pdf Status: UNKNOWN
RFC 764	Telnet Protocol specification
	Authors: J. Postel. Date: June 1980 Formats: txt pdf Obsoleted by: RFC 0854 Status: UNKNOWN
RFC 765	File Transfer Protocol specification
	Authors: J. Postel. Date: June 1980 Formats: txt pdf Obsoletes: RFC 0542 Obsoleted by: RFC 0959 Status: UNKNOWN
RFC 766	Internet Protocol Handbook: Table of contents
	Authors: J. Postel. Date: July 1980 Formats: txt pdf Obsoleted by: RFC 0774 Status: UNKNOWN
RFC 767	Structured format for transmission of multi-media documents
	Authors: J. Postel. Date: August 1980 Formats: txt pdf Status: UNKNOWN
RFC 768	User Datagram Protocol
	Authors: J. Postel. Date: August 1980 Formats: txt pdf Also: STD 0006 Status: STANDARD
RFC 769	Rapicom 450 facsimile file format
	Authors: J. Postel. Date: September 1980 Formats: txt pdf Status: UNKNOWN
RFC 770	Assigned numbers
	Authors: J. Postel. Date: September 1980 Formats: txt pdf Obsoletes: RFC 0762 Obsoleted by: RFC 0776 Status: HISTORIC
RFC 771	Mail transition plan
	Authors: V.G. Cerf, J. Postel. Date: September 1980 Formats: txt pdf Status: UNKNOWN
RFC 772	Mail Transfer Protocol
	Authors: S. Sluizer, J. Postel. Date: September 1980 Formats: txt pdf Obsoleted by: RFC 0780, STD 0010 Status: UNKNOWN
RFC 773	Comments on NCP/TCP mail service transition strategy
	Authors: V.G. Cerf. Date: October 1980 Formats: txt pdf Status: UNKNOWN
RFC 774	Internet Protocol Handbook: Table of contents
	Authors: J. Postel. Date: October 1980 Formats: txt pdf Obsoletes: RFC 0766 Status: UNKNOWN
RFC 775	Directory oriented FTP commands
	Authors: D. Mankins, D. Franklin, A.D. Owen. Date: December 1980 Formats: txt pdf Status: UNKNOWN
RFC 776	Assigned numbers
	Authors: J. Postel. Date: January 1981 Formats: txt pdf Obsoletes: RFC 0770 Obsoleted by: RFC 0790 Status: HISTORIC
RFC 777	Internet Control Message Protocol
	Authors: J. Postel. Date: April 1981 Formats: txt pdf Obsoleted by: RFC 0792 Updates: RFC 0760 Status: UNKNOWN
RFC 778	DCNET Internet Clock Service
	Authors: D.L. Mills. Date: April 1981 Formats: txt pdf Status: HISTORIC
RFC 779	Telnet send-location option
	Authors: E. Killian. Date: April 1981 Formats: txt pdf Status: PROPOSED STANDARD
RFC 780	Mail Transfer Protocol
	Authors: S. Sluizer, J. Postel. Date: May 1981 Formats: txt pdf Obsoletes: RFC 0772 Obsoleted by: RFC 0788, STD 0010 Status: UNKNOWN
RFC 781	Specification of the Internet Protocol (IP) timestamp option
	Authors: Z. Su. Date: May 1981 Formats: txt pdf Status: UNKNOWN
RFC 782	Virtual Terminal management model
	Authors: J. Nabielsky, A.P. Skelton. Date: January 1981 Formats: txt pdf Status: UNKNOWN
RFC 783	TFTP Protocol (revision 2)
	Authors: K.R. Sollins. Date: June 1981 Formats: txt pdf Obsoletes: IEN 133 Obsoleted by: RFC 1350 Status: UNKNOWN
RFC 784	Mail Transfer Protocol: ISI TOPS20 implementation
	Authors: S. Sluizer, J. Postel. Date: July 1981 Formats: txt pdf Status: UNKNOWN
RFC 785	Mail Transfer Protocol: ISI TOPS20 file definitions
	Authors: S. Sluizer, J. Postel. Date: July 1981 Formats: txt pdf Status: UNKNOWN
RFC 786	Mail Transfer Protocol: ISI TOPS20 MTP-NIMAIL interface
	Authors: S. Sluizer, J. Postel. Date: July 1981 Formats: txt pdf Status: UNKNOWN
RFC 787	Connectionless data transmission survey/tutorial
	Authors: A.L. Chapin. Date: July 1981 Formats: txt pdf Status: UNKNOWN
RFC 788	Simple Mail Transfer Protocol
	Authors: J. Postel. Date: November 1981 Formats: txt pdf Obsoletes: RFC 0780 Obsoleted by: RFC 0821, STD 0010 Status: UNKNOWN
RFC 789	Vulnerabilities of network control protocols: An example
	Authors: E.C. Rosen. Date: July 1981 Formats: txt pdf Status: UNKNOWN
RFC 790	Assigned numbers
	Authors: J. Postel. Date: September 1981 Formats: txt pdf Obsoletes: RFC 0776 Obsoleted by: RFC 0820 Status: HISTORIC
RFC 791	Internet Protocol
	Authors: J. Postel. Date: September 1981 Formats: txt pdf Obsoletes: RFC 0760 Updated by: RFC 1349 Also: STD 0005 Status: STANDARD
RFC 792	Internet Control Message Protocol
	Authors: J. Postel. Date: September 1981 Formats: txt pdf Obsoletes: RFC 0777 Updated by: RFC 0950, RFC 4884 Also: STD 0005 Status: STANDARD
RFC 793	Transmission Control Protocol
	Authors: J. Postel. Date: September 1981 Formats: txt pdf Obsoletes: RFC 0761 Updated by: RFC 1122, RFC 3168, RFC 6093, RFC 6528 Also: STD 0007 Status: STANDARD
RFC 794	Pre-emption
	Authors: V.G. Cerf. Date: September 1981 Formats: txt pdf Updates: IEN 125 Status: UNKNOWN
RFC 795	Service mappings
	Authors: J. Postel. Date: September 1981 Formats: txt pdf Status: UNKNOWN
RFC 796	Address mappings
	Authors: J. Postel. Date: September 1981 Formats: txt pdf Obsoletes: IEN 115 Status: UNKNOWN
RFC 797	Format for Bitmap files
	Authors: A.R. Katz. Date: September 1981 Formats: txt pdf Status: UNKNOWN
RFC 798	Decoding facsimile data from the Rapicom 450
	Authors: A.R. Katz. Date: September 1981 Formats: txt pdf Status: UNKNOWN
RFC 799	Internet name domains
	Authors: D.L. Mills. Date: September 1981 Formats: txt pdf Status: UNKNOWN
RFC 800	Request For Comments summary notes: 700-799
	Authors: J. Postel, J. Vernon. Date: November 1982 Formats: txt pdf Status: INFORMATIONAL This RFC is a slightly annotated list of the 100 RFCs from RFC 700 through RFC 799. This is a status report on these RFCs.
RFC 801	NCP/TCP transition plan
	Authors: J. Postel. Date: November 1981 Formats: txt pdf Status: UNKNOWN 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
	Authors: A.G. Malis. Date: November 1981 Formats: txt pdf Obsoleted by: RFC 0851 Status: UNKNOWN This document proposed two major changes to the current ARPANET host access protocol. The first change will allow hosts to use logical addressing (i.e., host addresses that are independent of their physical location on the ARPANET) to communicate with each other, and the second will allow a host to shorten the amount of time that it may be blocked by its IMP after it presents a message to the network (currently, the IMP can block further input from a host for up to 15 seconds). See RFCs 852 and 851.
RFC 803	Dacom 450/500 facsimile data transcoding
	Authors: A. Agarwal, M.J. O'Connor, D.L. Mills. Date: November 1981 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Obsoleted by: RFC 0841 Status: UNKNOWN This RFC deals with Computer Based Message systems which provides a basis for interaction between different CBMS by defining the format of messages passed between them. This RFC is replaced by RFC 841.
RFC 807	Multimedia mail meeting notes
	Authors: J. Postel. Date: February 1982 Formats: txt pdf Status: UNKNOWN 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
	Authors: J. Postel. Date: March 1982 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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
	Authors: E.J. Feinler, K. Harrenstien, Z. Su, V. White. Date: March 1982 Formats: txt pdf Obsoletes: RFC 0608 Obsoleted by: RFC 0952 Status: UNKNOWN This RFC specifies a new host table format applicable to both ARPANET and Internet needs. In addition to host name to host address translation and selected protocol information, we have also included network and gateway name to address correspondence, and host operating system information. This RFC obsoletes the host table described in RFC 608.
RFC 811	Hostnames Server
	Authors: K. Harrenstien, V. White, E.J. Feinler. Date: March 1982 Formats: txt pdf Obsoleted by: RFC 0953 Status: UNKNOWN This RFC gives a description of what the Hostnames Server is and how to access it. The function of this particular server is to deliver machine-readable name/address information describing networks, gateways, hosts, and eventually domains, within the internet environment.
RFC 812	NICNAME/WHOIS
	Authors: K. Harrenstien, V. White. Date: March 1982 Formats: txt pdf Obsoleted by: RFC 0954, RFC 3912 Status: UNKNOWN This RFC gives a description of what the NICNAME/WHOIS Server is and how to access it. This server together with the corresponding Identification Data Base provides online directory look-up equivalent to the ARPANET Directory.
RFC 813	Window and Acknowledgement Strategy in TCP
	Authors: D.D. Clark. Date: July 1982 Formats: txt pdf Status: UNKNOWN This RFC describes implementation strategies to deal with two mechanisms in TCP, the window and the acknowledgement. It also presents a particular set of algorithms which have received testing in the field, and which appear to work properly with each other. With more experience, these algorithms may become part of the formal specification, until such time their use is recommended.
RFC 814	Name, addresses, ports, and routes
	Authors: D.D. Clark. Date: July 1982 Formats: txt pdf Status: UNKNOWN This RFC gives suggestions and guidance for the design of the tables and algorithms necessary to keep track of these various sorts of identifiers inside a host implementation of TCP/IP.
RFC 815	IP datagram reassembly algorithms
	Authors: D.D. Clark. Date: July 1982 Formats: txt pdf Status: UNKNOWN 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 816	Fault isolation and recovery
	Authors: D.D. Clark. Date: July 1982 Formats: txt pdf Status: UNKNOWN This RFC describes the portion of fault isolation and recovery which is the responsibility of the host.
RFC 817	Modularity and efficiency in protocol implementation
	Authors: D.D. Clark. Date: July 1982 Formats: txt pdf Status: UNKNOWN This RFC will discuss some of the commonly encountered reasons why protocol implementations seem to run slowly.
RFC 818	Remote User Telnet service
	Authors: J. Postel. Date: November 1982 Formats: txt pdf Status: HISTORIC This RFC is the specification of an application protocol. Any host that implements this application level service must follow this protocol.
RFC 819	Domain naming convention for Internet user applications
	Authors: Z. Su, J. Postel. Date: August 1982 Formats: txt pdf Status: UNKNOWN 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 820	Assigned numbers
	Authors: J. Postel. Date: August 1982 Formats: txt pdf Obsoletes: RFC 0790 Obsoleted by: RFC 0870 Status: HISTORIC This RFC is an old version, see RFC 870.
RFC 821	Simple Mail Transfer Protocol
	Authors: J. Postel. Date: August 1982 Formats: txt pdf Obsoletes: RFC 0788 Obsoleted by: RFC 2821 Also: STD 0010 Status: STANDARD The objective of Simple Mail Transfer Protocol (SMTP) is to transfer mail reliably and efficiently. SMTP is independent of the particular transmission subsystem and requires only a reliable ordered data stream channel. Obsoletes RFC 788, 780, and 772.
RFC 822	STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
	Authors: D. Crocker. Date: August 1982 Formats: txt pdf Obsoletes: RFC 0733 Obsoleted by: RFC 2822 Updated by: RFC 1123, RFC 2156, RFC 1327, RFC 1138, RFC 1148 Also: STD 0011 Status: STANDARD This document revises the specifications in RFC 733, in order to serve the needs of the larger and more complex ARPA Internet. Some of RFC 733's features failed to gain adequate acceptance. In order to simplify the standard and the software that follows it, these features have been removed. A different addressing scheme is used, to handle the case of internetwork mail; and the concept of re-transmission has been introduced. Obsoletes RFC 733, NIC 41952.
RFC 823	DARPA Internet gateway
	Authors: R.M. Hinden, A. Sheltzer. Date: September 1982 Formats: txt pdf Updates: IEN109, IEN30 Status: HISTORIC This RFC is a status report on the Internet Gateway developed by BBN. It describes the Internet Gateway as of September 1982. This memo presents detailed descriptions of message formats and gateway procedures, however, this is not an implementation specification, and such details are subject to change.
RFC 824	CRONUS Virtual Local Network
	Authors: W.I. MacGregor, D.C. Tappan. Date: August 1982 Formats: txt pdf Status: UNKNOWN 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
	Authors: J. Postel. Date: November 1982 Formats: txt pdf Obsoleted by: RFC 1111, RFC 1543, RFC 2223 Status: UNKNOWN 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 826	Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware
	Authors: D. Plummer. Date: November 1982 Formats: txt pdf Updated by: RFC 5227, RFC 5494 Also: STD 0037 Status: STANDARD The purpose of this RFC is to present a method of Converting Protocol Addresses (e.g., IP addresses) to Local Network Addresses (e.g., Ethernet addresses). This is an issue of general concern in the ARPA Internet Community at this time. The method proposed here is presented for your consideration and comment. This is not the specification of an Internet Standard.
RFC 827	Exterior Gateway Protocol (EGP)
	Authors: E.C. Rosen. Date: October 1982 Formats: txt pdf Updated by: RFC 0904 Status: UNKNOWN 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
	Authors: K. Owen. Date: August 1982 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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
	Authors: Z. Su. Date: October 1982 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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?
	Authors: D. Smallberg. Date: December 1982 Formats: txt pdf Obsoleted by: RFC 0833 Status: UNKNOWN This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 7-Dec-82.
RFC 833	Who talks TCP?
	Authors: D. Smallberg. Date: December 1982 Formats: txt pdf Obsoletes: RFC 0832 Obsoleted by: RFC 0834 Status: UNKNOWN This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 14-Dec-82.
RFC 834	Who talks TCP?
	Authors: D. Smallberg. Date: December 1982 Formats: txt pdf Obsoletes: RFC 0833 Obsoleted by: RFC 0835 Status: UNKNOWN This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 22-Dec-82.
RFC 835	Who talks TCP?
	Authors: D. Smallberg. Date: December 1982 Formats: txt pdf Obsoletes: RFC 0834 Obsoleted by: RFC 0836 Status: UNKNOWN This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 28-Dec-82 through 5-Jan-83.
RFC 836	Who talks TCP?
	Authors: D. Smallberg. Date: January 1983 Formats: txt pdf Obsoletes: RFC 0835 Obsoleted by: RFC 0837 Status: UNKNOWN This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 20-Dec-82. The tests were run on 4-Jan-83 through 5-Jan-83.
RFC 837	Who talks TCP?
	Authors: D. Smallberg. Date: January 1983 Formats: txt pdf Obsoletes: RFC 0836 Obsoleted by: RFC 0838 Status: UNKNOWN This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 11-Jan-83.
RFC 838	Who talks TCP?
	Authors: D. Smallberg. Date: January 1983 Formats: txt pdf Obsoletes: RFC 0837 Obsoleted by: RFC 0839 Status: UNKNOWN This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 18-Jan-83.
RFC 839	Who talks TCP?
	Authors: D. Smallberg. Date: January 1983 Formats: txt pdf Obsoletes: RFC 0838 Obsoleted by: RFC 0842 Status: UNKNOWN This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 25-Jan-83.
RFC 840	Official protocols
	Authors: J. Postel. Date: April 1983 Formats: txt pdf Obsoleted by: RFC 0880 Status: HISTORIC This RFC has been revised, see RFC 880.
RFC 841	Specification for message format for Computer Based Message Systems
	Authors: National Bureau of Standards. Date: January 1983 Formats: txt pdf Obsoletes: RFC 0806 Status: UNKNOWN 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
	Authors: D. Smallberg. Date: February 1983 Formats: txt pdf Obsoletes: RFC 0839 Obsoleted by: RFC 0843 Status: UNKNOWN This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 28-Jan-83. The tests were run on 1-Feb-83 and on 2-Feb-83 ISI-VAXA.ARPA.
RFC 843	Who talks TCP? - survey of 8 February 83
	Authors: D. Smallberg. Date: February 1983 Formats: txt pdf Obsoletes: RFC 0842 Obsoleted by: RFC 0845 Updated by: RFC 0844 Status: UNKNOWN This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 3-Feb-83. The tests were run on 8-Feb-83 and on 9-Feb-83 from ISI-VAXA.ARPA.
RFC 844	Who talks ICMP, too? - Survey of 18 February 1983
	Authors: R. Clements. Date: February 1983 Formats: txt pdf Updates: RFC 0843 Status: UNKNOWN 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
	Authors: D. Smallberg. Date: February 1983 Formats: txt pdf Obsoletes: RFC 0843 Obsoleted by: RFC 0846 Status: UNKNOWN This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 3-Feb-83. The tests were run on 15-Feb-83 from ISI-VAXA.ARPA.
RFC 846	Who talks TCP? - survey of 22 February 1983
	Authors: D. Smallberg. Date: February 1983 Formats: txt pdf Obsoletes: RFC 0845 Obsoleted by: RFC 0847 Status: UNKNOWN This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 18-Feb-83. The tests were run on 22-Feb-83 from ISI-VAXA.ARPA.
RFC 847	Summary of Smallberg surveys
	Authors: A. Westine, D. Smallberg, J. Postel. Date: February 1983 Formats: txt pdf Obsoletes: RFC 0846 Status: UNKNOWN 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 pdf Status: UNKNOWN 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
	Authors: M.R. Crispin. Date: May 1983 Formats: txt pdf Status: UNKNOWN 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
	Authors: M.R. Horton. Date: June 1983 Formats: txt pdf Obsoleted by: RFC 1036 Status: UNKNOWN This memo is distributed as an RFC only to make this information easily accessible to researchers in the ARPA community. It does not specify an Internet standard. This RFC defines the standard format for interchange of Network News articles among USENET sites. It describes the format for articles themselves, and gives partial standards for transmission of news. The news transmission is not entirely standardized in order to give a good deal of flexibility to the individual hosts to choose transmission hardware and software, whether to batch news and so on.
RFC 851	ARPANET 1822L Host Access Protocol
	Authors: A.G. Malis. Date: April 1983 Formats: txt pdf Obsoletes: RFC 0802 Obsoleted by: RFC 0878 Status: UNKNOWN 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
	Authors: A.G. Malis. Date: April 1983 Formats: txt pdf Status: UNKNOWN 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 854	Telnet Protocol Specification
	Authors: J. Postel, J.K. Reynolds. Date: May 1983 Formats: txt pdf Obsoletes: RFC 0764 Updated by: RFC 5198 Also: STD 0008 Status: STANDARD This is the specification of the Telnet protocol used for remote terminal access in the ARPA Internet. The purpose of the TELNET Protocol is to provide a fairly general, bi-directional, eight-bit byte oriented communications facility. Its primary goal is to allow a standard method of interfacing terminal devices and terminal-oriented processes to each other. It is envisioned that the protocol may also be used for terminal-terminal communication ("linking") and process-process communication (distributed computation). This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 18639.
RFC 855	Telnet Option Specifications
	Authors: J. Postel, J.K. Reynolds. Date: May 1983 Formats: txt pdf Obsoletes: NIC 18640 Also: STD 0008 Status: STANDARD This memo specifies the general form for Telnet options and the directions for their specification. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes RFC 651, NIC 18640.
RFC 856	Telnet Binary Transmission
	Authors: J. Postel, J. Reynolds. Date: May 1983 Formats: txt pdf Obsoletes: NIC 15389 Also: STD 0027 Status: STANDARD This Telnet Option enables a binary data mode between the Telnet modules. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 15389.
RFC 857	Telnet Echo Option
	Authors: J. Postel, J. Reynolds. Date: May 1983 Formats: txt pdf Obsoletes: NIC 15390 Also: STD 0028 Status: STANDARD This Telnet Option enables remote echoing by the other Telnet module. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 15390.
RFC 858	Telnet Suppress Go Ahead Option
	Authors: J. Postel, J. Reynolds. Date: May 1983 Formats: txt pdf Obsoletes: NIC 15392 Also: STD 0029 Status: STANDARD This Telnet Option disables the exchange of go-ahead signals between the Telnet modules. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 15392.
RFC 859	Telnet Status Option
	Authors: J. Postel, J. Reynolds. Date: May 1983 Formats: txt pdf Obsoletes: RFC 0651 Also: STD 0030 Status: STANDARD This Telnet Option provides a way to determine the other Telnet module's view of the status of options. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes RFC 651 (NIC 31154).
RFC 860	Telnet Timing Mark Option
	Authors: J. Postel, J. Reynolds. Date: May 1983 Formats: txt pdf Obsoletes: NIC 16238 Also: STD 0031 Status: STANDARD This Telnet Option provides a way to check the roundtrip path between two Telnet modules. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 16238.
RFC 861	Telnet Extended Options: List Option
	Authors: J. Postel, J. Reynolds. Date: May 1983 Formats: txt pdf Obsoletes: NIC 16239 Also: STD 0032 Status: STANDARD This Telnet Option provides a mechanism for extending the set of possible options. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 16239.
RFC 862	Echo Protocol
	Authors: J. Postel. Date: May 1983 Formats: txt pdf Also: STD 0020 Status: STANDARD This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Echo Protocol are expected to adopt and implement this standard. The Echo service simply sends back to the originating source any data it receives.
RFC 863	Discard Protocol
	Authors: J. Postel. Date: May 1983 Formats: txt pdf Also: STD 0021 Status: STANDARD This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Discard Protocol are expected to adopt and implement this standard. The Discard service simply throws away any data it receives.
RFC 864	Character Generator Protocol
	Authors: J. Postel. Date: May 1983 Formats: txt pdf Also: STD 0022 Status: STANDARD This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Character Generator Protocol are expected to adopt and implement this standard. The Character Generator service simply sends data without regard to the input.
RFC 865	Quote of the Day Protocol
	Authors: J. Postel. Date: May 1983 Formats: txt pdf Also: STD 0023 Status: STANDARD This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Quote of the Day Protocol are expected to adopt and implement this standard. The Quote of the Day service simply sends a short message without regard to the input.
RFC 866	Active users
	Authors: J. Postel. Date: May 1983 Formats: txt pdf Also: STD 0024 Status: STANDARD This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement an Active Users Protocol are expected to adopt and implement this standard. The Active Users service simply sends a list of the currently active users on the host without regard to the input.
RFC 867	Daytime Protocol
	Authors: J. Postel. Date: May 1983 Formats: txt pdf Also: STD 0025 Status: STANDARD This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Daytime Protocol are expected to adopt and implement this standard. The Daytime service simply sends the current date and time as a character string without regard to the input.
RFC 868	Time Protocol
	Authors: J. Postel, K. Harrenstien. Date: May 1983 Formats: txt pdf Also: STD 0026 Status: STANDARD This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Time Protocol are expected to adopt and implement this standard. This protocol provides a site-independent, machine readable date and time. The Time service sends back to the originating source the time in seconds since midnight on January first 1900.
RFC 869	Host Monitoring Protocol
	Authors: R. Hinden. Date: December 1983 Formats: txt pdf Status: HISTORIC This RFC specifies the Host Monitoring Protocol used to collect information from various types of hosts in the Internet. Designers of Internet communications software are encouraged to consider this protocol as a means of monitoring the behavior of their creations.
RFC 870	Assigned numbers
	Authors: J.K. Reynolds, J. Postel. Date: October 1983 Formats: txt pdf Obsoletes: RFC 0820 Obsoleted by: RFC 0900 Status: HISTORIC This RFC documents the list of numbers assigned for networks, protocols, etc. Obsoletes RFCs 820, 790, 776, 770, 762, 758, 755, 750, 739, 604.
RFC 871	Perspective on the ARPANET reference model
	Authors: M.A. Padlipsky. Date: September 1982 Formats: txt pdf Status: UNKNOWN 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 872	TCP-on-a-LAN
	Authors: M.A. Padlipsky. Date: September 1982 Formats: txt pdf Status: UNKNOWN This memo attacks the notion that TCP cannot be appropriate for use on a Local Area Network. Originally published as M82-48 by the MITRE Corporation, Bedford Massachusetts.
RFC 873	Illusion of vendor support
	Authors: M.A. Padlipsky. Date: September 1982 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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
	Authors: J.T. Korb. Date: September 1983 Formats: txt pdf Obsoleted by: RFC 1356 Status: UNKNOWN This RFC specifies a standard adopted by CSNET, the VAN gateway, and other organizations for the transmission of IP datagrams over the X.25-based public data networks.
RFC 878	ARPANET 1822L Host Access Protocol
	Authors: A.G. Malis. Date: December 1983 Formats: txt pdf Obsoletes: RFC 0851 Status: UNKNOWN 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 879	TCP maximum segment size and related topics
	Authors: J. Postel. Date: November 1983 Formats: txt pdf Status: UNKNOWN This RFC discusses the TCP Maximum Segment Size Option and related topics. The purposes is to clarify some aspects of TCP and its interaction with IP. This memo is a clarification to the TCP specification, and contains information that may be considered as "advice to implementers".
RFC 880	Official protocols
	Authors: J.K. Reynolds, J. Postel. Date: October 1983 Formats: txt pdf Obsoletes: RFC 0840 Obsoleted by: RFC 0901 Status: HISTORIC This RFC identifies the documents specifying the official protocols used in the ARPA Internet. Annotations identify any revisions or changes planned. Obsoletes RFC 840.
RFC 881	Domain names plan and schedule
	Authors: J. Postel. Date: November 1983 Formats: txt pdf Updated by: RFC 0897 Status: UNKNOWN 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
	Authors: P.V. Mockapetris. Date: November 1983 Formats: txt pdf Obsoleted by: RFC 1034, RFC 1035 Updated by: RFC 0973 Status: UNKNOWN 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
	Authors: P.V. Mockapetris. Date: November 1983 Formats: txt pdf Obsoleted by: RFC 1034, RFC 1035 Updated by: RFC 0973 Status: UNKNOWN This RFC discusses the implementation of domain name servers and resolvers, specifies the format of transactions, and discusses the use of domain names in the context of existing mail systems and other network software.
RFC 884	Telnet terminal type option
	Authors: M. Solomon, E. Wimmers. Date: December 1983 Formats: txt pdf Obsoleted by: RFC 0930 Status: UNKNOWN This RFC specifies a standard for the ARPA Internet community. It specifies a method for exchanging terminal type information in the Telnet protocol.
RFC 885	Telnet end of record option
	Authors: J. Postel. Date: December 1983 Formats: txt pdf Status: PROPOSED STANDARD This RFC specifies a standard for the ARPA Internet community. It specifies a method for marking the end of records in data transmitted on Telnet connections.
RFC 886	Proposed standard for message header munging
	Authors: M.T. Rose. Date: December 1983 Formats: txt pdf Status: UNKNOWN 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 887	Resource Location Protocol
	Authors: M. Accetta. Date: December 1983 Formats: txt pdf Status: EXPERIMENTAL This RFC specifies a draft standard for the ARPA Internet community. It describes a resource location protocol for use in the ARPA Internet. It is most useful on networks employing technologies which support some method of broadcast addressing, however it may also be used on other types of networks. For maximum benefit, all hosts which provide significant resources or services to other hosts on the Internet should implement this protocol. Hosts failing to implement the Resource Location Protocol risk being ignored by other hosts which are attempting to locate resources on the Internet.
RFC 888	"STUB" Exterior Gateway Protocol
	Authors: L. Seamonson, E.C. Rosen. Date: January 1984 Formats: txt pdf Updated by: RFC 0904 Status: UNKNOWN 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 889	Internet Delay Experiments
	Authors: D.L. Mills. Date: December 1983 Formats: txt pdf Status: UNKNOWN This memo reports on some measurements of round-trip times in the Internet and suggests some possible improvements to the TCP retransmission timeout calculation. This memo is both a status report on the Internet and advice to TCP implementers.
RFC 890	Exterior Gateway Protocol implementation schedule
	Authors: J. Postel. Date: February 1984 Formats: txt pdf Status: UNKNOWN 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 891	DCN Local-Network Protocols
	Authors: D.L. Mills. Date: December 1983 Formats: txt pdf Also: STD 0044 Status: STANDARD This RFC provides a description of the DCN protocols for maintaining connectivity, routing, and clock information in a local network. These procedures may be of interest to the designers and implementers of other local networks.
RFC 892	ISO Transport Protocol specification
	Authors: International Organization for Standardization. Date: December 1983 Formats: txt pdf Obsoleted by: RFC 0905 Status: UNKNOWN This is a draft version of the transport protocol being standardized by the ISO. This version also appeared in the ACM SIGCOMM Computer Communication Review (V.12, N.3-4) July-October 1982. This version is now out of date.
RFC 893	Trailer encapsulations
	Authors: S. Leffler, M.J. Karels. Date: April 1984 Formats: txt pdf Status: UNKNOWN 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 894	A Standard for the Transmission of IP Datagrams over Ethernet Networks
	Authors: C. Hornig. Date: April 1984 Formats: txt pdf Also: STD 0041 Status: STANDARD This RFC specifies a standard method of encapsulating Internet Protocol (IP) datagrams on an Ethernet. This RFC specifies a standard protocol for the ARPA-Internet community.
RFC 895	Standard for the transmission of IP datagrams over experimental Ethernet networks
	Authors: J. Postel. Date: April 1984 Formats: txt pdf Also: STD 0042 Status: STANDARD This RFC specifies a standard method of encapsulating Internet Protocol (IP) datagrams on an Experimental Ethernet. This RFC specifies a standard protocol for the ARPA Internet community.
RFC 896	Congestion Control in IP/TCP Internetworks
	Authors: J. Nagle. Date: January 1984 Formats: txt pdf Status: UNKNOWN This memo discusses some aspects of congestion control in IP/TCP Internetworks. It is intended to stimulate thought and further discussion of this topic. While some specific suggestions are made for improved congestion control implementation, this memo does not specify any standards.
RFC 897	Domain name system implementation schedule
	Authors: J. Postel. Date: February 1984 Formats: txt pdf Updates: RFC 0881 Updated by: RFC 0921 Status: UNKNOWN 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 pdf Status: UNKNOWN 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 899	Request For Comments summary notes: 800-899
	Authors: J. Postel, A. Westine. Date: May 1984 Formats: txt pdf Status: INFORMATIONAL
RFC 900	Assigned Numbers
	Authors: J.K. Reynolds, J. Postel. Date: June 1984 Formats: txt pdf Obsoletes: RFC 0870 Obsoleted by: RFC 0923 Status: HISTORIC This RFC specifies parameter values use in the Internet family of protocols, such as network numbers, well known ports, protocol types, and version numbers. This memo is an official status report on the protocol parameters used in the Internet protocol system. See RFC-990 and 997.
RFC 901	Official ARPA-Internet protocols
	Authors: J.K. Reynolds, J. Postel. Date: June 1984 Formats: txt pdf Obsoletes: RFC 0880 Obsoleted by: RFC 0924 Status: UNKNOWN This RFC identifies the documents specifying the official protocols used in the ARPA-Internet. Annotations identify any revisions or changes planned. This memo is an official status report on the protocols used in the DARPA research community. See RFC-991.
RFC 902	ARPA Internet Protocol policy
	Authors: J.K. Reynolds, J. Postel. Date: July 1984 Formats: txt pdf Status: UNKNOWN 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 903	A Reverse Address Resolution Protocol
	Authors: R. Finlayson, T. Mann, J.C. Mogul, M. Theimer. Date: June 1984 Formats: txt pdf Also: STD 0038 Status: STANDARD This RFC suggests a method for workstations to dynamically find their protocol address (e.g., their Internet Address), when they know only their hardware address (e.g., their attached physical network address). This RFC specifies a proposed protocol for the ARPA Internet community, and requests discussion and suggestions for improvements.
RFC 904	Exterior Gateway Protocol formal specification
	Authors: D.L. Mills. Date: April 1984 Formats: txt pdf Updates: RFC 0827, RFC 0888 Status: HISTORIC RFC-904 is the specification of the Exterior Gateway Protocol (EGP). This memo updates portions of RFC-888 and RFC-827. This RFC specifies an official protocol of the DARPA community for use between gateways of different autonomous systems in the ARPA-Internet.
RFC 905	ISO Transport Protocol specification ISO DP 8073
	Authors: ISO. Date: April 1984 Formats: txt pdf Obsoletes: RFC 0892 Status: UNKNOWN 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 pdf Status: UNKNOWN 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 907	Host Access Protocol specification
	Authors: Bolt Beranek and Newman Laboratories. Date: July 1984 Formats: txt pdf Updated by: RFC 1221 Also: STD 0040 Status: STANDARD This document specifies the Host Access Protocol (HAP). Although HAP was originally designed as the network-access level protocol for the DARPA/DCA sponsored Wideband Packet Satellite Network, it is intended that it evolve into a standard interface SATNET and TACNET (aka MATNET) as well as the Wideband Network. HAP is an experimental protocol, and will undergo further revision as new capabilities are added and/or different satellite networks are suported. Implementations of HAP should be performed in coordination with satellite network development and operations personnel.
RFC 908	Reliable Data Protocol
	Authors: D. Velten, R.M. Hinden, J. Sax. Date: July 1984 Formats: txt pdf Updated by: RFC 1151 Status: EXPERIMENTAL The Reliable Data Protocol (RDP) is designed to provide a reliable data transport service for packet-based applications. This RFC specifies a proposed protocol for the ARPA-Internet and DARPA research community, and requests discussion and suggestions for improvemts.
RFC 909	Loader Debugger Protocol
	Authors: C. Welles, W. Milliken. Date: July 1984 Formats: txt pdf Status: EXPERIMENTAL The Loader Debugger Protocol (LDP) is an application layer protocol for loading, dumping, and debugging target machines from hosts in a network environment. This RFC specifies a proposed protocol for the ARPA-Internet and DARPA research community, and requests discussion and suggestions for improvemts.
RFC 910	Multimedia mail meeting notes
	Authors: H.C. Forsdick. Date: August 1984 Formats: txt pdf Status: UNKNOWN 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
	Authors: P. Kirton. Date: August 1984 Formats: txt pdf Status: UNKNOWN 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
	Authors: M. St. Johns. Date: September 1984 Formats: txt pdf Obsoleted by: RFC 0931 Status: UNKNOWN This memo describes a proposed authentication protocol for verifying the identity of a user of a TCP connection. Given a TCP port number pair, it returns a character string which identifies the owner of that connection on the server's system. Suggested uses include automatic identification and verification of a user during an FTP session, additional verification of a TAC dial up user, and access verification for a generalized network file server.
RFC 913	Simple File Transfer Protocol
	Authors: M. Lottor. Date: September 1984 Formats: txt pdf Status: HISTORIC This memo describes a proposed Simple File Transfer Protocol (SFTP). It fills the need of people wanting a protocol that is more useful than TFTP but easier to implement (and less powerful) than FTP. SFTP supports user access control, file transfers, directory listing, directory changing, file renaming and deleting. Discussion of this proposal is encouraged, and suggestions for improvements may be sent to the author.
RFC 914	Thinwire protocol for connecting personal computers to the Internet
	Authors: D.J. Farber, G. Delp, T.M. Conte. Date: September 1984 Formats: txt pdf Status: HISTORIC This RFC focuses discussion on the particular problems in the ARPA-Internet of low speed network interconnection with personal computers, and possible methods of solution. None of the proposed solutions in this document are intended as standards for the ARPA-Internet. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to the problems, leading eventually to the adoption of standards.
RFC 915	Network mail path service
	Authors: M.A. Elvy, R. Nedved. Date: December 1984 Formats: txt pdf Status: UNKNOWN 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 916	Reliable Asynchronous Transfer Protocol (RATP)
	Authors: G.G. Finn. Date: October 1984 Formats: txt pdf Status: HISTORIC This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. This paper proposes and specifies a protocol which allows two programs to reliably communicate over a communication link. It ensures that the data entering one end of the link if received arrives at the other end intact and unaltered. The protocol, named RATP, is designed to operate over a full duplex point-to-point connection. It contains some features which tailor it to the RS-232 links now in common use.
RFC 917	Internet subnets
	Authors: J.C. Mogul. Date: October 1984 Formats: txt pdf Status: UNKNOWN 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
	Authors: J.K. Reynolds. Date: October 1984 Formats: txt pdf Obsoleted by: RFC 0937 Status: UNKNOWN This RFC suggests a simple method for workstations to dynamically access mail from a mailbox server. The intent of the Post Office Protocol (POP) is to allow a user's workstation to access mail from a mailbox server. It is expected that mail will be posted from the workstation to the mailbox server via the Simple Mail Transfer Protocol (SMTP). This RFC specifies a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvement. The status of this protocol is experimental, and this protocol is dependent upon TCP.
RFC 919	Broadcasting Internet Datagrams
	Authors: J.C. Mogul. Date: October 1984 Formats: txt pdf Also: STD 0005 Status: STANDARD This RFC proposes simple rules for broadcasting Internet datagrams on local networks that support broadcast, for addressing broadcasts, and for how gateways should handle them. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
RFC 920	Domain requirements
	Authors: J. Postel, J.K. Reynolds. Date: October 1984 Formats: txt pdf Status: UNKNOWN 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
	Authors: J. Postel. Date: October 1984 Formats: txt pdf Updates: RFC 0897 Status: UNKNOWN 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 922	Broadcasting Internet datagrams in the presence of subnets
	Authors: J.C. Mogul. Date: October 1984 Formats: txt pdf Also: STD 0005 Status: STANDARD We propose simple rules for broadcasting Internet datagrams on local networks that support broadcast, for addressing broadcasts, and for how gateways should handle them. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
RFC 923	Assigned numbers
	Authors: J.K. Reynolds, J. Postel. Date: October 1984 Formats: txt pdf Obsoletes: RFC 0900 Obsoleted by: RFC 0943 Status: HISTORIC This RFC documents the currently assigned values from several series of numbers used in network protocol implementations. This edition of Assigned Numbers obsoletes RFC-900 and earlier editions. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990, and 997.
RFC 924	Official ARPA-Internet protocols for connecting personal computers to the Internet
	Authors: J.K. Reynolds, J. Postel. Date: October 1984 Formats: txt pdf Obsoletes: RFC 0901 Obsoleted by: RFC 0944 Status: UNKNOWN This RFC identifies the documents specifying the official protocols used in the Internet. This edition of Official ARPA-Internet Protocols obsoletes RFC-900 and earlier editions. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991.
RFC 925	Multi-LAN address resolution
	Authors: J. Postel. Date: October 1984 Formats: txt pdf Status: UNKNOWN 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 pdf Obsoleted by: RFC 0994 Status: UNKNOWN This note is the draft ISO protocol roughly similar to the DOD Internet Protocol. This document has been prepared by retyping the text of ISO DIS 8473 of May 1984, which is currently undergoing voting within ISO as a Draft International Standard (DIS). This document is distributred as an RFC for information only. It does not specify a standard for the ARPA-Internet.
RFC 927	TACACS user identification Telnet option
	Authors: B.A. Anderson. Date: December 1984 Formats: txt pdf Status: PROPOSED STANDARD The following is the description of a TELNET option designed to facilitate double login avoidance. It is intended primarily for TAC connections to target hosts on behalf of TAC users, but it can be used between any two consenting hosts. For example, all hosts at one site (e.g., BBN) can use this option to avoid double login when TELNETing to one another. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
RFC 928	Introduction to proposed DoD standard H-FP
	Authors: M.A. Padlipsky. Date: December 1984 Formats: txt pdf Status: UNKNOWN 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 929	Proposed Host-Front End Protocol
	Authors: J. Lilienkamp, R. Mandell, M.A. Padlipsky. Date: December 1984 Formats: txt pdf Status: HISTORIC The Host-Front End Protocol introduced in RFC-928 is described in detail in this memo. The first order of business is to declare that THIS IS A PROPOSAL, NOT A FINAL STANDARD, and the second order of business is to request that any readers of these documents who are able to do test implementations (a) do so and (b) coordinate their efforts with the author. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
RFC 930	Telnet terminal type option
	Authors: M. Solomon, E. Wimmers. Date: January 1985 Formats: txt pdf Obsoletes: RFC 0884 Obsoleted by: RFC 1091 Status: UNKNOWN This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that exchange terminal type information within the Telnet protocol are expected to adopt and implement this standard. This standard supersedes RFC-884. The only change is to specify that the TERMINAL-TYPE IS sub-negotiation should be sent only in response to the TERMINAL-TYPE SEND sub-negotiation.
RFC 931	Authentication server
	Authors: M. St. Johns. Date: January 1985 Formats: txt pdf Obsoletes: RFC 0912 Obsoleted by: RFC 1413 Status: UNKNOWN This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. This is the second draft of this proposal (superseding RFC-912) and incorporates a more formal description of the syntax for the request and response dialog, as well as a change to specify the type of user identification returned.
RFC 932	Subnetwork addressing scheme
	Authors: D.D. Clark. Date: January 1985 Formats: txt pdf Status: UNKNOWN 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 933	Output marking Telnet option
	Authors: S. Silverman. Date: January 1985 Formats: txt pdf Status: PROPOSED STANDARD This proposed option would allow a Server-Telnet to send a banner to a User-Telnet so that this banner would be displayed on the workstation screen independently of the application software running in the Server-Telnet.
RFC 934	Proposed standard for message encapsulation
	Authors: M.T. Rose, E.A. Stefferud. Date: January 1985 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 937	Post Office Protocol: Version 2
	Authors: M. Butler, J. Postel, D. Chase, J. Goldberger, J.K. Reynolds. Date: February 1985 Formats: txt pdf Obsoletes: RFC 0918 Status: HISTORIC This RFC suggests a simple method for workstations to dynamically access mail from a mailbox server. This RFC specifies a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvement. This memo is a revision of RFC-918.
RFC 938	Internet Reliable Transaction Protocol functional and interface specification
	Authors: T. Miller. Date: February 1985 Formats: txt pdf Status: EXPERIMENTAL This RFC is being distributed to members of the DARPA research community in order to solicit their reactions to the proposals contained in it. While the issues discussed may not be directly relevant to the research problems of the DARPA community, they may be interesting to a number of researchers and implementors. 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 943	Assigned numbers
	Authors: J.K. Reynolds, J. Postel. Date: April 1985 Formats: txt pdf Obsoletes: RFC 0923 Obsoleted by: RFC 0960 Status: HISTORIC This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This RFC will be updated periodically, and in any case current information can be obtained from Joyce Reynolds. The assignment of numbers is also handled by Joyce. If you are developing a protocol or application that will require the use of a link, socket, port, protocol, network number, etc., please contact Joyce to receive a number assignment. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990 and 997.
RFC 944	Official ARPA-Internet protocols
	Authors: J.K. Reynolds, J. Postel. Date: April 1985 Formats: txt pdf Obsoletes: RFC 0924 Obsoleted by: RFC 0961 Status: UNKNOWN This RFC identifies the documents specifying the official protocols used in the Internet. This edition of Official ARPA-Internet Protocols obsoletes RFC-924 and earlier editions. This RFC will be updated periodically, and current information can be obtained from Joyce Reynolds. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991.
RFC 945	DoD statement on the NRC report
	Authors: J. Postel. Date: May 1985 Formats: txt pdf Obsoleted by: RFC 1039 Status: UNKNOWN In May 1983 the National Research Council (NRC) was asked jointly by DoD and NBS to study the issues and recommend a course of action. The final report of the NRC committee was published in February 1985 (see RFC-942). The enclosed letter is from Donald C. Latham (ASDC3I) to DCA transmitting the NRC report and requesting specific actions relative to the recommendations of the report. This RFC reproduces a letter from the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASDC3I) to the Director of the Defense Communications Agency (DCA). This letter is distributed for information only.
RFC 946	Telnet terminal location number option
	Authors: R. Nedved. Date: May 1985 Formats: txt pdf Status: PROPOSED STANDARD Many systems provide a mechanism for finding out where a user is logged in from usually including information about telephone extension and office occupants names. The information is useful for physically locating people and/or calling them on the phone. In 1982 CMU designed and implemented a terminal location database and modified existing network software to handle a 64-bit number called the Terminal Location Number (or TTYLOC). It now seems appropriate to incorporate this mechanism into the TCP-based network protocol family. The mechanism is not viewed as a replacement for the Terminal Location Telnet Option (SEND-LOCATION) but as a shorthand mechansim for communicating terminal location information between hosts in a localized community. This RFC proposes a new option for Telnet for the ARPA-Internet community, and requests discussion and suggestions for improvements.
RFC 947	Multi-network broadcasting within the Internet
	Authors: K. Lebowitz, D. Mankins. Date: June 1985 Formats: txt pdf Status: UNKNOWN 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
	Authors: I. Winston. Date: June 1985 Formats: txt pdf Obsoleted by: RFC 1042 Status: UNKNOWN This RFC describes two methods of encapsulating Internet Protocol (IP) datagrams on an IEEE 802.3 network. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
RFC 949	FTP unique-named store command
	Authors: M.A. Padlipsky. Date: July 1985 Formats: txt pdf Status: UNKNOWN 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 950	Internet Standard Subnetting Procedure
	Authors: J.C. Mogul, J. Postel. Date: August 1985 Formats: txt pdf Updates: RFC 0792 Also: STD 0005 Status: STANDARD This memo discusses the utility of "subnets" of Internet networks, which are logically visible sub-sections 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 memo specifies procedures for the use of subnets. These procedures are for hosts (e.g., workstations). The procedures used in and between subnet gateways are not fully described. Important motivation and background information for a subnetting standard is provided in RFC-940. This RFC specifies a protocol for the ARPA-Internet community. If subnetting is implemented it is strongly recommended that these procedures be followed.
RFC 951	Bootstrap Protocol
	Authors: W.J. Croft, J. Gilmore. Date: September 1985 Formats: txt pdf Updated by: RFC 1395, RFC 1497, RFC 1532, RFC 1542, RFC 5494 Status: DRAFT STANDARD This RFC describes an IP/UDP bootstrap protocol (BOOTP) which allows a diskless client machine to discover its own IP address, the address of a server host, and the name of a file to be loaded into memory and executed. The bootstrap operation can be thought of as consisting of TWO PHASES. This RFC describes the first phase, which could be labeled `address determination and bootfile selection'. After this address and filename information is obtained, control passes to the second phase of the bootstrap where a file transfer occurs. The file transfer will typically use the TFTP protocol, since it is intended that both phases reside in PROM on the client. However BOOTP could also work with other protocols such as SFTP or FTP. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
RFC 952	DoD Internet host table specification
	Authors: K. Harrenstien, M.K. Stahl, E.J. Feinler. Date: October 1985 Formats: txt pdf Obsoletes: RFC 0810 Status: UNKNOWN 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 953	Hostname Server
	Authors: K. Harrenstien, M.K. Stahl, E.J. Feinler. Date: October 1985 Formats: txt pdf Obsoletes: RFC 0811 Status: HISTORIC This RFC is the official specification of the Hostname Server Protocol. This edition of the specification includes minor revisions to RFC-811 which brings it up to date.
RFC 954	NICNAME/WHOIS
	Authors: K. Harrenstien, M.K. Stahl, E.J. Feinler. Date: October 1985 Formats: txt pdf Obsoletes: RFC 0812 Obsoleted by: RFC 3912 Status: DRAFT STANDARD This RFC is the official specification of the NICNAME/WHOIS protocol. This memo describes the protocol and the service. This is an update of RFC-812.
RFC 955	Towards a transport service for transaction processing applications
	Authors: R.T. Braden. Date: September 1985 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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)
	Authors: D.L. Mills. Date: September 1985 Formats: txt pdf Obsoleted by: RFC 1059, RFC 1119, RFC 1305 Status: UNKNOWN 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 959	File Transfer Protocol
	Authors: J. Postel, J. Reynolds. Date: October 1985 Formats: txt pdf Obsoletes: RFC 0765 Updated by: RFC 2228, RFC 2640, RFC 2773, RFC 3659, RFC 5797 Also: STD 0009 Status: STANDARD This memo is the official specification of the File Transfer Protocol (FTP) for the DARPA Internet community. The primary intent is to clarify and correct the documentation of the FTP specification, not to change the protocol. The following new optional commands are included in this edition of the specification: Change to Parent Directory (CDUP), Structure Mount (SMNT), Store Unique (STOU), Remove Directory (RMD), Make Directory (MKD), Print Directory (PWD), and System (SYST). Note that this specification is compatible with the previous edition.
RFC 960	Assigned numbers
	Authors: J.K. Reynolds, J. Postel. Date: December 1985 Formats: txt pdf Obsoletes: RFC 0943 Obsoleted by: RFC 0990 Status: HISTORIC This memo documents the currently assigned values from several series of numbers used in network protocol implementations. This edition of Assigned Numbers updates and obsoletes RFC-943. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990 and 997.
RFC 961	Official ARPA-Internet protocols
	Authors: J.K. Reynolds, J. Postel. Date: December 1985 Formats: txt pdf Obsoletes: RFC 0944 Obsoleted by: RFC 0991 Status: UNKNOWN This memo identifies the documents specifying the official protocols used in the Internet, and comments on any revisions or changes planned. This edition of the Official Protocols updates and obsoletes RFC-944. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991.
RFC 962	TCP-4 prime
	Authors: M.A. Padlipsky. Date: November 1985 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 964	Some problems with the specification of the Military Standard Transmission Control Protocol
	Authors: D.P. Sidhu, T. Blumer. Date: November 1985 Formats: txt pdf Status: UNKNOWN The purpose of this RFC is to provide helpful information on the Military Standard Transmission Control Protocol (MIL-STD-1778) so that one can obtain a reliable implementation of this protocol standard. This note points out three errors with 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 pdf Status: UNKNOWN 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 pdf Obsoleted by: RFC 0988 Status: UNKNOWN This RFC defines a model of service for Internet multicasting and proposes an extension to the Internet Protocol (IP) to support such a multicast service. Discussion and suggestions for improvements are requested. See RFC-988.
RFC 967	All victims together
	Authors: M.A. Padlipsky. Date: December 1985 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Obsoleted by: RFC 0998 Status: UNKNOWN This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. This is a preliminary discussion of the Network Block Transfer (NETBLT) protocol. NETBLT is intended for the rapid transfer of a large quantity of data between computers. It provides a transfer that is reliable and flow controlled, and is structured to provide maximum throughput over a wide variety of networks. This description is published for discussion and comment, and does not constitute a standard. As the proposal may change, implementation of this document is not advised. See RFC-998.
RFC 970	On Packet Switches With Infinite Storage
	Authors: J. Nagle. Date: December 1985 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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
	Authors: P.V. Mockapetris. Date: January 1986 Formats: txt pdf Obsoleted by: RFC 1034, RFC 1035 Updates: RFC 0882, RFC 0883 Status: UNKNOWN This RFC documents updates to Domain Name System specifications RFC-882 and RFC-883, suggests some operational guidelines, and discusses some experiences and problem areas in the present system.
RFC 974	Mail routing and the domain system
	Authors: C. Partridge. Date: January 1986 Formats: txt pdf Obsoleted by: RFC 2821 Also: STD 0010 Status: HISTORIC This RFC presents a description of how mail systems on the Internet are expected to route messages based on information from the domain system. This involves a discussion of how mailers interpret MX RRs, which are used for message routing.
RFC 975	Autonomous confederations
	Authors: D.L. Mills. Date: February 1986 Formats: txt pdf Status: UNKNOWN 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
	Authors: M.R. Horton. Date: February 1986 Formats: txt pdf Updated by: RFC 1137 Status: UNKNOWN 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 977	Network News Transfer Protocol
	Authors: B. Kantor, P. Lapsley. Date: February 1986 Formats: txt pdf Obsoleted by: RFC 3977 Status: PROPOSED STANDARD NNTP specifies a protocol for the distribution, inquiry, retrieval, and posting of news articles using a reliable stream-based transmission of news among the ARPA-Internet community. NNTP is designed so that news articles are stored in a central database allowing a subscriber to select only those items he wishes to read. Indexing, cross-referencing, and expiration of aged messages are also provided. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
RFC 978	Voice File Interchange Protocol (VFIP)
	Authors: J.K. Reynolds, R. Gillman, W.A. Brackenridge, A. Witkowski, J. Postel. Date: February 1986 Formats: txt pdf Status: UNKNOWN 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
	Authors: A.G. Malis. Date: March 1986 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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
	Authors: D.L. Mills. Date: March 1986 Formats: txt pdf Status: UNKNOWN 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
	Authors: H.W. Braun. Date: April 1986 Formats: txt pdf Status: UNKNOWN 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
	Authors: D.E. Cass, M.T. Rose. Date: April 1986 Formats: txt pdf Obsoleted by: RFC 1006 Status: UNKNOWN This memo describes a proposed protocol standard for the ARPA Internet community. The CCITT and the ISO have defined various session, presentation, and application recommendations which have been adopted by the international community and numerous vendors. To the largest extent possible, it is desirable to offer these higher level services directly in the ARPA Internet, without disrupting existing facilities. This permits users to develop expertise with ISO and CCITT applications which previously were not available in the ARPA Internet. The intention is that hosts in the ARPA-Internet that choose to implement ISO TSAP services on top of the TCP be expected to adopt and implement this standard. Suggestions for improvement are encouraged.
RFC 984	PCMAIL: A distributed mail system for personal computers
	Authors: D.D. Clark, M.L. Lambert. Date: May 1986 Formats: txt pdf Obsoleted by: RFC 0993 Status: UNKNOWN This document is a preliminary discussion of the design of a personal-computer-based distributed mail system. Pcmail is a distributed mail system that provides mail service to an arbitrary number of users, each of which owns one or more personal computers (PCs). The system is divided into two halves. The first consists of a single entity called the "repository". The repository is a storage center for incoming mail. Mail for a Pcmail user can arrive externally from the Internet or internally from other repository users. The repository also maintains a stable copy of each user's mail state. The repository is therefore typically a computer with a large amount of disk storage. It is published for discussion and comment, and does not constitute a standard. As the proposal may change, implementation of this document is not advised. See RFC-993.
RFC 985	Requirements for Internet gateways - draft
	Authors: National Science Foundation, Network Technical Advisory Group. Date: May 1986 Formats: txt pdf Obsoleted by: RFC 1009 Status: UNKNOWN This RFC summarizes the requirements for gateways to be used on networks supporting the DARPA Internet protocols. While it applies specifically to National Science Foundation research programs, the requirements are stated in a general context and are believed applicable throughout the Internet community. The purpose of this document is to present guidance for vendors offering products that might be used or adapted for use in an Internet application. It enumerates the protocols required and gives references to RFCs and other documents describing the current specification.
RFC 986	Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol
	Authors: R.W. Callon, H.W. Braun. Date: June 1986 Formats: txt pdf Obsoleted by: RFC 1069 Status: UNKNOWN This RFC suggests a method to allow the existing IP addressing, including the IP protocol field, to be used for the ISO Connectionless Network Protocol (CLNP). This is a draft solution to one of the problems inherent in the use of "ISO-grams" in the DOD Internet. Related issues will be discussed in subsequent RFCs. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
RFC 987	Mapping between X.400 and RFC 822
	Authors: S.E. Kille. Date: June 1986 Formats: txt pdf Obsoleted by: RFC 2156, RFC 1327 Updated by: RFC 1026, RFC 1138, RFC 1148 Status: UNKNOWN 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
	Authors: S.E. Deering. Date: July 1986 Formats: txt pdf Obsoletes: RFC 0966 Obsoleted by: RFC 1054, RFC 1112 Status: UNKNOWN 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
	Authors: J. Linn. Date: February 1987 Formats: txt pdf Obsoleted by: RFC 1040, RFC 1113 Status: UNKNOWN This RFC suggests a proposed protocol for the Internet community and requests discussion and suggestions for improvements. This RFC is the outgrowth of a series of IAB Privacy Task Force meetings and of internal working papers distributed for those meetings. This RFC defines message encipherment and authentication procedures, as the initial phase of an effort to provide privacy enhancement services for electronic mail transfer in the Internet. It is intended that the procedures defined here be compatible with a wide range of key management approaches, including both conventional (symmetric) and public-key (asymmetric) approaches for encryption of data encrypting keys. Use of conventional cryptography for message text encryption and/or authentication is anticipated.
RFC 990	Assigned numbers
	Authors: J.K. Reynolds, J. Postel. Date: November 1986 Formats: txt pdf Obsoletes: RFC 0960 Obsoleted by: RFC 1010 Updated by: RFC 0997 Status: HISTORIC This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-997. Obsoletes RFC-960, 943, 923 and 900.
RFC 991	Official ARPA-Internet protocols
	Authors: J.K. Reynolds, J. Postel. Date: November 1986 Formats: txt pdf Obsoletes: RFC 0961 Obsoleted by: RFC 1011 Status: UNKNOWN This RFC identifies the documents specifying the official protocols used in the Internet. Comments indicate any revisions or changes planned. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. Obsoletes RFC-961, 944 and 924.
RFC 992	On communication support for fault tolerant process groups
	Authors: K.P. Birman, T.A. Joseph. Date: November 1986 Formats: txt pdf Status: UNKNOWN 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
	Authors: D.D. Clark, M.L. Lambert. Date: December 1986 Formats: txt pdf Obsoletes: RFC 0984 Obsoleted by: RFC 1056 Status: UNKNOWN This document is a discussion of the Pcmail workstation-based distributed mail system. It is a revision of the design published in NIC RFC-984. The revision is based on discussion and comment fromm a variety of sources, as well as further research into the design of interactive Pcmail clients and the use of client code on machines other than IBM PCs. As this design may change, implementation of this document is not advised. Obsoletes RFC-984.
RFC 994	Final text of DIS 8473, Protocol for Providing the Connectionless-mode Network Service
	Authors: International Organization for Standardization. Date: March 1986 Formats: txt pdf Obsoletes: RFC 0926 Status: UNKNOWN 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 pdf Status: UNKNOWN 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 996	Statistics server
	Authors: D.L. Mills. Date: February 1987 Formats: txt pdf Status: HISTORIC This RFC specifies a standard for the ARPA Internet community. Hosts and gateways on the DARPA Internet that choose to implement a remote statistics monitoring facility may use this protocol to send statistics data upon request to a monitoring center or debugging host.
RFC 997	Internet numbers
	Authors: J.K. Reynolds, J. Postel. Date: March 1987 Formats: txt pdf Obsoleted by: RFC 1020, RFC 1117 Updates: RFC 0990 Status: UNKNOWN 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 998	NETBLT: A bulk data transfer protocol
	Authors: D.D. Clark, M.L. Lambert, L. Zhang. Date: March 1987 Formats: txt pdf Obsoletes: RFC 0969 Status: EXPERIMENTAL This document is a description of, and a specification for, the NETBLT protocol. It is a revision of the specification published in RFC-969. NETBLT (NETwork BLock Transfer) is a transport level protocol 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 designed to provide maximum throughput over a wide variety of networks. Although NETBLT currently runs on top of the Internet Protocol (IP), it should be able to operate on top of any datagram protocol similar in function to IP. This document is published for discussion and comment, and does not constitute a standard. The proposal may change and certain parts of the protocol have not yet been specified; implementation of this document is therefore not advised. Obsoletes RFC-969.
RFC 999	Requests For Comments summary notes: 900-999
	Authors: A. Westine, J. Postel. Date: April 1987 Formats: txt pdf Obsoletes: RFC 0160 Obsoleted by: RFC 1000 Status: UNKNOWN
RFC 1000	Request For Comments reference guide
	Authors: J.K. Reynolds, J. Postel. Date: August 1987 Formats: txt pdf Obsoletes: RFC 0999 Status: UNKNOWN This RFC Reference Guide is intended to provide a historical account by categorizing and summarizing of the Request for Comments numbers 1 through 999 issued between the years 1969-1987. These documents have been crossed referenced to indicate which RFCs are current, obsolete, or revised.
RFC 1001	Protocol standard for a NetBIOS service on a TCP/UDP transport: Concepts and methods
	Authors: NetBIOS Working Group in the Defense Advanced Research Projects Agency, Internet Activities Board, End-to-End Services Task Force. Date: March 1987 Formats: txt pdf Also: STD 0019 Status: STANDARD This RFC defines a proposed standard protocol to support NetBIOS services in a TCP/IP environment. Both local network and internet operation are supported. Various node types are defined to accommodate local and internet topologies and to allow operation with or without the use of IP broadcast. This RFC describes the NetBIOS-over-TCP protocols in a general manner, emphasizing the underlying ideas and techniques. Detailed specifications are found in a companion RFC, "Protocol Standard For a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications".
RFC 1002	Protocol standard for a NetBIOS service on a TCP/UDP transport: Detailed specifications
	Authors: NetBIOS Working Group in the Defense Advanced Research Projects Agency, Internet Activities Board, End-to-End Services Task Force. Date: March 1987 Formats: txt pdf Also: STD 0019 Status: STANDARD This RFC defines a proposed standard protocol to support NetBIOS services in a TCP/IP environment. Both local network and internet operation are supported. Various node types are defined to accommodate local and internet topologies and to allow operation with or without the use of IP broadcast. This RFC gives the detailed specifications of the netBIOS-over-TCP packets, protocols, and defined constants and variables. A more general overview is found in a companion RFC, "Protocol Standard For NetBIOS Service on TCP/UDP Transport: Concepts and Methods".
RFC 1003	Issues in defining an equations representation standard
	Authors: A.R. Katz. Date: March 1987 Formats: txt pdf Status: UNKNOWN This memo is intended to identify and explore issues in defining a standard for the exchange of mathematical equations. No attempt is made at a complete definition and more questions are asked than are answered. Questions about the user interface are only addressed to the extent that they affect interchange issues.
RFC 1004	Distributed-protocol authentication scheme
	Authors: D.L. Mills. Date: April 1987 Formats: txt pdf Status: EXPERIMENTAL The purpose of this RFC is to focus discussion on authentication problems in the Internet and possible methods of solution. The proposed solutions this document are not intended as standards for the Internet at this time. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to authentication problems, leading eventually to the adoption of standards. This document suggests mediated access-control and authentication procedures suitable for those cases when an association is to be set up between users belonging to different trust environments.
RFC 1005	ARPANET AHIP-E Host Access Protocol (enhanced AHIP)
	Authors: A. Khanna, A.G. Malis. Date: May 1987 Formats: txt pdf Status: UNKNOWN This RFC is a proposed specification for the encoding of Class A IP addresses for use on ARPANET-style networks such as the Milnet and Arpanet, and for enhancements to the ARPANET AHIP Host Access Protocol (AHIP; formerly known as 1822). These enhancements increase the size of the PSN field, allow ARPANET hosts to use logical names to address each other, allow for the communication of type-of-service information from the host to the PSN and enable the PSN to provide congestion feedback to the host on a connection basis.
RFC 1006	ISO Transport Service on top of the TCP Version: 3
	Authors: M.T. Rose, D.E. Cass. Date: May 1987 Formats: txt pdf Obsoletes: RFC 0983 Updated by: RFC 2126 Also: STD 0035 Status: STANDARD This memo specifies a standard for the Internet community. Hosts on the Internet that choose to implement ISO transport services on top of the TCP are expected to adopt and implement this standard. TCP port 102 is reserved for hosts which implement this standard. This memo specifies version 3 of the protocol and supersedes RFC-983. Changes between the protocol is described in RFC-983 and this memo are minor, but unfortunately incompatible.
RFC 1007	Military supplement to the ISO Transport Protocol
	Authors: W. McCoy. Date: June 1987 Formats: txt pdf Status: UNKNOWN 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
	Authors: W. McCoy. Date: June 1987 Formats: txt pdf Status: UNKNOWN This RFC is being distributed to members of the Internet community in order to solicit comments on the Implementors Guide. While this document may not be directly relevant to the research problems of the Internet, it may be of some interest to a number of researchers and implementors.
RFC 1009	Requirements for Internet gateways
	Authors: R.T. Braden, J. Postel. Date: June 1987 Formats: txt pdf Obsoletes: RFC 0985 Obsoleted by: RFC 1812 Status: HISTORIC This RFC summarizes the requirements for gateways to be used between networks supporting the Internet protocols. This document is a formal statement of the requirements to be met by gateways used in the Internet system. As such, it is an official specification for the Internet community.
RFC 1010	Assigned numbers
	Authors: J.K. Reynolds, J. Postel. Date: May 1987 Formats: txt pdf Obsoletes: RFC 0990 Obsoleted by: RFC 1060 Status: HISTORIC This memo is an official status report on the numbers used in protocols in the Internet community. It documents the currently assigned values from several series of numbers including link, socket, port, and protocol, used in network protocol implementations.
RFC 1011	Official Internet protocols
	Authors: J.K. Reynolds, J. Postel. Date: May 1987 Formats: txt pdf Obsoletes: RFC 0991 Updated by: RFC 6093 Status: UNKNOWN This memo is an official status report on the protocols used in the Internet community. It identifies the documents specifying the official protocols used in the Internet. Comments indicate any revisions or changes planned.
RFC 1012	Bibliography of Request For Comments 1 through 999
	Authors: J.K. Reynolds, J. Postel. Date: June 1987 Formats: txt pdf Status: INFORMATIONAL This RFC is a reference guide for the Internet community which provides a bibliographic summary of the Request for Comments numbers 1 through 999 issued between the years 1969-1987.
RFC 1013	X Window System Protocol, version 11: Alpha update April 1987
	Authors: R.W. Scheifler. Date: June 1987 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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
	Authors: B.M. Leiner. Date: July 1987 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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
	Authors: S. Romano, M.K. Stahl. Date: November 1987 Formats: txt pdf Obsoletes: RFC 0997 Obsoleted by: RFC 1062, RFC 1117, RFC 1166 Status: UNKNOWN This RFC is a list of the Assigned IP Network Numbers and EGP Autonomous System Numbers. This RFC obsoletes RFC-997.
RFC 1021	High-level Entity Management System (HEMS)
	Authors: C. Partridge, G. Trewitt. Date: October 1987 Formats: txt pdf Status: HISTORIC This memo provides a general overview of the High-level Entity management system (HEMS). This system is experimental, and is currently being tested in portions of the Internet.
RFC 1022	High-level Entity Management Protocol (HEMP)
	Authors: C. Partridge, G. Trewitt. Date: October 1987 Formats: txt pdf Status: UNKNOWN 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
	Authors: G. Trewitt, C. Partridge. Date: October 1987 Formats: txt pdf Obsoleted by: RFC 1076 Status: UNKNOWN This RFC specifies the High-Level Entity Management System (HEMS) Monitoring and Control Language. This language defines the requests and replies used in HEMS. This memo assumes knowledge of the HEMS system described in RFC-1021, and of the ISO data encoding standard, ASN.1.
RFC 1024	HEMS variable definitions
	Authors: C. Partridge, G. Trewitt. Date: October 1987 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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)
	Authors: S.E. Kille. Date: September 1987 Formats: txt pdf Obsoleted by: RFC 2156, RFC 1327 Updates: RFC 0987 Updated by: RFC 1138, RFC 1148 Status: UNKNOWN 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 pdf Status: UNKNOWN This RFC describes the use of the Address Resolution Protocol (ARP) by subnet gateways to permit hosts on the connected subnets to communicate without being aware of the existence of subnets, using the technique of "Proxy ARP".
RFC 1028	Simple Gateway Monitoring Protocol
	Authors: J. Davin, J.D. Case, M. Fedor, M.L. Schoffstall. Date: November 1987 Formats: txt pdf Status: HISTORIC This memo defines a simple application-layer protocol by which management information for a gateway may be inspected or altered by remote users. This proposal is intended only as an interim response to immediate gateway monitoring needs.
RFC 1029	More fault tolerant approach to address resolution for a Multi-LAN system of Ethernets
	Authors: G. Parr. Date: May 1988 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN This RFC provides guidelines for domain administrators in operating a domain server and maintaining their portion of the hierarchical database. Familiarity with the domain system is assumed (see RFCs 1031, 1032, 1034, and 1035).
RFC 1034	Domain names - concepts and facilities
	Authors: P.V. Mockapetris. Date: November 1987 Formats: txt pdf Obsoletes: RFC 0973, RFC 0882, RFC 0883 Updated by: RFC 1101, RFC 1183, RFC 1348, RFC 1876, RFC 1982, RFC 2065, RFC 2181, RFC 2308, RFC 2535, RFC 4033, RFC 4034, RFC 4035, RFC 4343, RFC 4035, RFC 4592, RFC 5936 Also: STD 0013 Status: STANDARD This RFC is the revised basic definition of The Domain Name System. It obsoletes RFC-882. This memo describes the domain style names and their used for host address look up and electronic mail forwarding. It discusses the clients and servers in the domain name system and the protocol used between them.
RFC 1035	Domain names - implementation and specification
	Authors: P.V. Mockapetris. Date: November 1987 Formats: txt pdf Obsoletes: RFC 0973, RFC 0882, RFC 0883 Updated by: RFC 1101, RFC 1183, RFC 1348, RFC 1876, RFC 1982, RFC 1995, RFC 1996, RFC 2065, RFC 2136, RFC 2181, RFC 2137, RFC 2308, RFC 2535, RFC 2845, RFC 3425, RFC 3658, RFC 4033, RFC 4034, RFC 4035, RFC 4343, RFC 5936, RFC 5966, RFC 6604 Also: STD 0013 Status: STANDARD This RFC is the revised specification of the protocol and format used in the implementation of the Domain Name System. It obsoletes RFC-883. This memo documents the details of the domain name client - server communication.
RFC 1036	Standard for interchange of USENET messages
	Authors: M.R. Horton, R. Adams. Date: December 1987 Formats: txt pdf Obsoletes: RFC 0850 Obsoleted by: RFC 5536, RFC 5537 Status: UNKNOWN This RFC defines the standard format for the interchange of network News messages among USENET hosts. It updates and replaces RFC-850, reflecting version B2.11 of the News program. This memo is distributed as an RFC to make this information easily accessible to the Internet community. It does not specify an Internet standard.
RFC 1037	NFILE - a file access protocol
	Authors: B. Greenberg, S. Keene. Date: December 1987 Formats: txt pdf Status: HISTORIC This document includes a specification of the NFILE file access protocol and its underlying levels of protocol, the Token List Transport Layer and Byte Stream with Mark. The goal of this specification is to promote discussion of the ideas described here, and to encourage designers of future file protocols to take advantage of these ideas. A secondary goal is to make the specification available to sites that might benefit from implementing NFILE.
RFC 1038	Draft revised IP security option
	Authors: M. St. Johns. Date: January 1988 Formats: txt pdf Obsoleted by: RFC 1108 Status: UNKNOWN This memo is a pre-publication draft of the revised Internet Protocol Security Option. This RFC reflects the version as approved by the Protocol Standards Steering group, and is provided for informational purposes only. The final version of this document will be available from Navy publications and should not differ from this document in any major fashion. This document will be published as a change to the MIL- STD 1777, "Internet Protocol".
RFC 1039	DoD statement on Open Systems Interconnection protocols
	Authors: D. Latham. Date: January 1988 Formats: txt pdf Obsoletes: RFC 0945 Status: UNKNOWN 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
	Authors: J. Linn. Date: January 1988 Formats: txt pdf Obsoletes: RFC 0989 Obsoleted by: RFC 1113 Status: UNKNOWN This RFC is the Outgrowth of a series of IAB Privacy Task Force meetings and of internal working papers distributed for those meetings. This memo defines message encipherment and authentication procedures, as the initial phase of an effort to provide privacy enhancement services for electronic mail transfer in the Internet. Detailed key management mechanisms to support these procedures will be defined in a subsequent RFC. As a goal of this initial phase, it is intended that the procedures defined here be compatible with a wide range of key management approaches, including both conventional (symmetric) and public-key (asymmetric) approaches for encryption of data encrypting keys. Use of conventional cryptography for message text encryption and/or integrity check computation is anticipated.
RFC 1041	Telnet 3270 regime option
	Authors: Y. Rekhter. Date: January 1988 Formats: txt pdf Updated by: RFC 6270 Status: PROPOSED STANDARD This RFC specifies a proposed standard for the Internet community. Hosts on the Internet that want to support 3270 data stream within the Telnet protocol, are expected to adopt and implement this standard.
RFC 1042	Standard for the transmission of IP datagrams over IEEE 802 networks
	Authors: J. Postel, J.K. Reynolds. Date: February 1988 Formats: txt pdf Obsoletes: RFC 0948 Also: STD 0043 Status: STANDARD This RFC specifies a standard method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on IEEE 802 Networks to allow compatible and interoperable implementations. This RFC specifies a protocol standard for the Internet community.
RFC 1043	Telnet Data Entry Terminal option: DODIIS implementation
	Authors: A. Yasuda, T. Thompson. Date: February 1988 Formats: txt pdf Updates: RFC 0732 Status: PROPOSED STANDARD This RFC suggests a proposed protocol on the TELNET Data Entry Terminal (DET) Option - DODIIS Implementation for the Internet community. It is intended that this specification be capatible with the specification of DET Option in RFC-732. Discussion and suggests for improvements are encouraged.
RFC 1044	Internet Protocol on Network System's HYPERchannel: Protocol Specification
	Authors: K. Hardwick, J. Lekashman. Date: February 1988 Formats: txt pdf Updated by: RFC 5494 Also: STD 0045 Status: STANDARD This memo intends to provide a complete discussion of the protocols and techniques used to embed DoD standard Internet Protocol datagrams (and its associated higher level protocols) on Network Systems Corporation's HYPERchannel equipment. This document is directed toward network planners and implementors who are already familiar with the TCP/IP protocol suite and the techniques used to carry TCP/IP traffic on common networks such as the DDN or the Ethernet. No great familiarity with NSC products is assumed; an appendix is devoted to a review of NSC technologies and protocols.
RFC 1045	VMTP: Versatile Message Transaction Protocol: Protocol specification
	Authors: D.R. Cheriton. Date: February 1988 Formats: txt pdf Status: EXPERIMENTAL This memo specifies the Versatile Message Transaction Protocol (VMTP) [Version 0.7 of 19-Feb-88], a transport protocol specifically designed to support the transaction model of communication, as exemplified by remote procedure call (RPC). The full function of VMTP, including support for security, real-time, asynchronous message exchanges, streaming, multicast and idempotency, provides a rich selection to the VMTP user level. Subsettability allows the VMTP module for particular clients and servers to be specialized and simplified to the services actually required. Examples of such simple clients and servers include PROM network bootload programs, network boot servers, data sensors and simple controllers, to mention but a few examples. This RFC describes a protocol proposed as a standard for the Internet community.
RFC 1046	Queuing algorithm to provide type-of-service for IP links
	Authors: W. Prue, J. Postel. Date: February 1988 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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
	Authors: P.A. Prindeville. Date: February 1988 Formats: txt pdf Obsoleted by: RFC 1084, RFC 1395, RFC 1497, RFC 1533 Status: UNKNOWN This memo proposes an addition to the Bootstrap Protocol (BOOTP). Comments and suggestions for improvements are sought.
RFC 1049	Content-type header field for Internet messages
	Authors: M.A. Sirbu. Date: March 1988 Formats: txt pdf Status: HISTORIC This memo suggests proposed additions to the Internet Mail Protocol, RFC-822, for the Internet community, and requests discussion and suggestions for improvements.
RFC 1050	RPC: Remote Procedure Call Protocol specification
	Authors: Sun Microsystems. Date: April 1988 Formats: txt pdf Obsoleted by: RFC 1057 Status: HISTORIC This memo specifies a message protocol used in implementing Sun's Remote Procedure Call (RPC) package. This RFC describes a standard that Sun Microsystems and others are using and is one they wish to propose for the Internet's consideration. It is not an Internet standard at this time.
RFC 1051	Standard for the transmission of IP datagrams and ARP packets over ARCNET networks
	Authors: P.A. Prindeville. Date: March 1988 Formats: txt pdf Obsoleted by: RFC 1201 Status: HISTORIC This memo specifies a standard method of encapsulating Internet Protocol (IP) and Address Resolution Protocol (ARP) datagrams on an ARCNET. This RFC is a standard protocol for the Internet community.
RFC 1052	IAB recommendations for the development of Internet network management standards
	Authors: V.G. Cerf. Date: April 1988 Formats: txt pdf Status: UNKNOWN This RFC is intended to convey to the Internet community and other interested parties the recommendations of the Internet Activities Board (IAB) for the development of network management protocols for use in the TCP/IP environment. This memo does NOT, in and of itself, define or propose an Official Internet Protocol. It does reflect, however, the policy of the IAB with respect to further network management development in the short and long term.
RFC 1053	Telnet X.3 PAD option
	Authors: S. Levy, T. Jacobson. Date: April 1988 Formats: txt pdf Status: PROPOSED STANDARD This RFC proposes a new option to Telnet for the Internet community, and requests discussion and suggestions for improvements.
RFC 1054	Host extensions for IP multicasting
	Authors: S.E. Deering. Date: May 1988 Formats: txt pdf Obsoletes: RFC 0988 Obsoleted by: RFC 1112 Status: UNKNOWN This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. IP multicasting is the transmission of an IP datagram to a "host group", a set hosts identified by a single IP destination address. A multicast datagram is delivered to all members of its destination host group with the same "best-efforts" reliability as regular unicast IP datagrams. It is proposed as a standard for IP multicasting in the Internet. This specification is a major revision of RFC-988.
RFC 1055	Nonstandard for transmission of IP datagrams over serial lines: SLIP
	Authors: J.L. Romkey. Date: June 1988 Formats: txt pdf Also: STD 0047 Status: STANDARD The TCP/IP protocol family runs over a variety of network media: IEEE 802.3 (ethernet) and 802.5 (token ring) LAN's, X.25 lines, satellite links, and serial lines. There are standard encapsulations for IP packets defined for many of these networks, but there is no standard for serial lines. SLIP, Serial Line IP, is a currently a de facto standard, commonly used for point-to-point serial connections running TCP/IP. It is not an Internet standard.
RFC 1056	PCMAIL: A distributed mail system for personal computers
	Authors: M.L. Lambert. Date: June 1988 Formats: txt pdf Obsoletes: RFC 0993 Status: INFORMATIONAL This memo is a discussion of the Pcmail workstation based distributed mail system. It is identical to the discussion in RFC-993, save that a new, much simpler mail transport protocol is described. The new transport protocol is the result of continued research into ease of protocol implementation and use issues.
RFC 1057	RPC: Remote Procedure Call Protocol specification: Version 2
	Authors: Sun Microsystems. Date: June 1988 Formats: txt pdf Obsoletes: RFC 1050 Status: INFORMATIONAL This RFC describes a standard that Sun Microsystems and others are using, and is one we wish to propose for the Internet's consideration. This memo is not an Internet standard at this time.
RFC 1058	Routing Information Protocol
	Authors: C.L. Hedrick. Date: June 1988 Formats: txt pdf Updated by: RFC 1388, RFC 1723 Status: HISTORIC This RFC describes an existing protocol for exchanging routing information among gateways and other hosts. It is intended to be used as a basis for developing gateway software for use in the Internet community.
RFC 1059	Network Time Protocol (version 1) specification and implementation
	Authors: D.L. Mills. Date: July 1988 Formats: txt pdf Obsoletes: RFC 0958 Obsoleted by: RFC 1119, RFC 1305 Status: UNKNOWN This memo describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. NTP provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse internet operating at rates from mundane to lightwave. It uses a returnable-time design in which a distributed subnet of time servers operating in a self- organizing, hierarchical master-slave configuration synchronizes logical clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute reference time via local routing algorithms and time daemons. The NTP architectures, algorithms and protocols which have evolved over several years of implementation and refinement are described in this document. The prototype system, which has been in regular operation in the Internet for the last two years, is described in an Appendix along with performance data which shows that timekeeping accuracy throughout most portions of the Internet can be ordinarily maintained to within a few tens of milliseconds, even the cases of failure or disruption of clocks, time servers or nets. This is a Draft Standard for an Elective protocol.
RFC 1060	Assigned numbers
	Authors: J.K. Reynolds, J. Postel. Date: March 1990 Formats: txt pdf Obsoletes: RFC 1010 Obsoleted by: RFC 1340 Updated by: RFC 1349 Status: HISTORIC This memo is a status report on the parameters (i.e., numbers and keywords) used in protocols in the Internet community. Distribution of this memo is unlimited.
RFC 1062	Internet numbers
	Authors: S. Romano, M.K. Stahl, M. Recker. Date: August 1988 Formats: txt pdf Obsoletes: RFC 1020 Obsoleted by: RFC 1117, RFC 1166 Status: UNKNOWN This memo is an official status report on the network numbers and gateway autonomous system numbers used in the Internet community.
RFC 1063	IP MTU discovery options
	Authors: J.C. Mogul, C.A. Kent, C. Partridge, K. McCloghrie. Date: July 1988 Formats: txt pdf Obsoleted by: RFC 1191 Status: UNKNOWN A pair of IP options that can be used to learn the minimum MTU of a path through an internet is described, along with its possible uses. This is a proposal for an Experimental protocol.
RFC 1064	Interactive Mail Access Protocol: Version 2
	Authors: M.R. Crispin. Date: July 1988 Formats: txt pdf Obsoleted by: RFC 1176, RFC 1203 Status: UNKNOWN This memo suggests a method for workstations to dynamically access mail from a mailbox server ("respository"). This RFC specifies a standard for the SUMEX-AIM community and a proposed experimental protocol for the Internet community. Discussion and suggestions for improvement are requested.
RFC 1065	Structure and identification of management information for TCP/IP-based internets
	Authors: K. McCloghrie, M.T. Rose. Date: August 1988 Formats: txt pdf Obsoleted by: RFC 1155 Status: STANDARD This RFC provides the common definitions for the structure and identification of management information for TCP/IP-based internets. In particular, together with its companion memos, which describe the initial management information base along with the initial network management protocol, these documents provide a simple, working architecture and system for managing TCP/IP-based internets and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementation in the Internet which are network manageable are expected to adopt and implement this specification.
RFC 1066	Management Information Base for network management of TCP/IP-based internets
	Authors: K. McCloghrie, M.T. Rose. Date: August 1988 Formats: txt pdf Obsoleted by: RFC 1156 Status: UNKNOWN This RFC provides the initial version of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets in the short-term. In particular, together with its companion memos which describe the structure of management information along with the initial network management protocol, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets, and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementations in the Internet which are network manageable are expected to adopt and implement this specification.
RFC 1067	Simple Network Management Protocol
	Authors: J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin. Date: August 1988 Formats: txt pdf Obsoleted by: RFC 1098 Status: UNKNOWN This RFC defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. In particular, together with its companion memos which describe the structure of management information along with the initial management information base, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementations in the Internet which are network manageable are expected to adopt and implement this specification.
RFC 1068	Background File Transfer Program (BFTP)
	Authors: A.L. DeSchon, R.T. Braden. Date: August 1988 Formats: txt pdf Status: UNKNOWN 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
	Authors: R.W. Callon, H.W. Braun. Date: February 1989 Formats: txt pdf Obsoletes: RFC 0986 Status: UNKNOWN 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 pdf Status: UNKNOWN This RFC proposes a scenario for experimentation with the International Organization for Standardization (ISO) Open Systems Interconnection (OSI) network layer protocols over the Internet and requests discussion and suggestions for improvements to this scenario. This RFC also proposes the creation of an experimental OSI internet. To participate in the experimental OSI internet, a system must abide by the agreements set forth in this RFC.
RFC 1071	Computing the Internet checksum
	Authors: R.T. Braden, D.A. Borman, C. Partridge. Date: September 1988 Formats: txt pdf Updated by: RFC 1141 Status: UNKNOWN This RFC summarizes techniques and algorithms for efficiently computing the Internet checksum. It is not a standard, but a set of useful implementation techniques.
RFC 1072	TCP extensions for long-delay paths
	Authors: V. Jacobson, R.T. Braden. Date: October 1988 Formats: txt pdf Obsoleted by: RFC 1323, RFC 2018, RFC 6247 Status: HISTORIC This RFC proposes a set of extensions to the TCP protocol to provide efficient operation over a path with a high bandwidth*delay product. These extensions are not proposed as an Internet standard at this time. Instead, they are intended as a basis for further experimentation and research on transport protocol performance.
RFC 1073	Telnet window size option
	Authors: D. Waitzman. Date: October 1988 Formats: txt pdf Status: PROPOSED STANDARD This RFC describes a proposed Telnet option to allow a client to convey window size to a Telnet server.
RFC 1074	NSFNET backbone SPF based Interior Gateway Protocol
	Authors: J. Rekhter. Date: October 1988 Formats: txt pdf Status: UNKNOWN This RFC is an implementation description of the standard ANSI IS-IS and ISO ES-IS routing protocols within the NSFNET backbone network.
RFC 1075	Distance Vector Multicast Routing Protocol
	Authors: D. Waitzman, C. Partridge, S.E. Deering. Date: November 1988 Formats: txt pdf Status: EXPERIMENTAL This RFC describes a distance-vector-style routing protocol for routing multicast datagrams through an internet. It is derived from the Routing Information Protocol (RIP), and implements multicasting as described in RFC-1054. This is an experimental protocol, and its implementation is not recommended at this time.
RFC 1076	HEMS monitoring and control language
	Authors: G. Trewitt, C. Partridge. Date: November 1988 Formats: txt pdf Obsoletes: RFC 1023 Status: UNKNOWN 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 pdf Status: UNKNOWN This memo presents the results of a working group on High Bandwidth Networking. This RFC is for your information and you are encouraged to comment on the issues presented.
RFC 1078	TCP port service Multiplexer (TCPMUX)
	Authors: M. Lottor. Date: November 1988 Formats: txt pdf Status: UNKNOWN This RFC proposes an Internet standard which can be used by future TCP services instead of using 'well-known ports'.
RFC 1079	Telnet terminal speed option
	Authors: C.L. Hedrick. Date: December 1988 Formats: txt pdf Status: PROPOSED STANDARD This RFC specifies a standard for the Internet community. Hosts on the Internet that exchange terminal speed information within the Telnet protocol are expected to adopt and implement this standard.
RFC 1080	Telnet remote flow control option
	Authors: C.L. Hedrick. Date: November 1988 Formats: txt pdf Obsoleted by: RFC 1372 Status: UNKNOWN This RFC specifies a standard for the Internet community. Hosts on the Internet that do remote flow control within the Telnet protocol are expected to adopt and implement this standard.
RFC 1081	Post Office Protocol: Version 3
	Authors: M.T. Rose. Date: November 1988 Formats: txt pdf Obsoleted by: RFC 1225 Status: UNKNOWN This memo suggests a simple method for workstations to dynamically access mail from a mailbox server. This RFC specifies a proposed protocol for the Internet community, and requests discussion and suggestions for improvements.
RFC 1082	Post Office Protocol: Version 3: Extended service offerings
	Authors: M.T. Rose. Date: November 1988 Formats: txt pdf Status: UNKNOWN This memo suggests a simple method for workstations to dynamically access mail from a discussion group server, as an extension to an earlier memo which dealt with dynamically accessing mail from a mailbox server using the Post Office Protocol - Version 3 (POP3). This RFC specifies a proposed protocol for the Internet community, and requests discussion and suggestions for improvements. All of the extensions described in this memo to the POP3 are OPTIONAL.
RFC 1083	IAB official protocol standards
	Authors: Defense Advanced Research Projects Agency, Internet Activities Board. Date: December 1988 Formats: txt pdf Obsoleted by: RFC 1100 Status: HISTORIC This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures is presented first, followed by discussions of the standardization process and the RFC document series, then the explanation of the terms is presented, the lists of protocols in each stage of standardization follows, and finally pointers to references and contacts for further information. This memo is issued quarterly, please be sure the copy you are reading is dated within the last three months.
RFC 1084	BOOTP vendor information extensions
	Authors: J.K. Reynolds. Date: December 1988 Formats: txt pdf Obsoletes: RFC 1048 Obsoleted by: RFC 1395, RFC 1497, RFC 1533 Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN 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 pdf Status: UNKNOWN This memo is a statement of policy by the Internet Activities Board (IAB) concerning the proper use of the resources of the Internet.
RFC 1088	Standard for the transmission of IP datagrams over NetBIOS networks
	Authors: L.J. McLaughlin. Date: February 1989 Formats: txt pdf Also: STD 0048 Status: STANDARD This document specifies a standard method of encapsulating the Internet Protocol (IP) datagrams on NetBIOS networks.
RFC 1089	SNMP over Ethernet
	Authors: M. Schoffstall, C. Davin, M. Fedor, J. Case. Date: February 1989 Formats: txt pdf Obsoleted by: RFC 4789 Status: UNKNOWN This memo describes an experimental method by which the Simple Network Management Protocol (SNMP) can be used over Ethernet MAC layer framing instead of the Internet UDP/IP protocol stack. This specification is useful for LAN based network elements that support no higher layer protocols beyond the MAC sub-layer.
RFC 1090	SMTP on X.25
	Authors: R. Ullmann. Date: February 1989 Formats: txt pdf Status: UNKNOWN This memo proposes a standard for SMTP on the virtual circuit facility provided by the X.25 standard of the CCITT.
RFC 1091	Telnet terminal-type option
	Authors: J. VanBokkelen. Date: February 1989 Formats: txt pdf Obsoletes: RFC 0930 Status: PROPOSED STANDARD This RFC specifies a standard for the Internet community. Hosts on the Internet that exchange terminal type information within the Telnet protocol are expected to adopt and implement this standard. This standard supersedes RFC 930. A change is made to permit cycling through a list of possible terminal types and selecting the most appropriate
RFC 1092	EGP and policy based routing in the new NSFNET backbone
	Authors: J. Rekhter. Date: February 1989 Formats: txt pdf Status: UNKNOWN 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 pdf Status: UNKNOWN This document describes the routing architecture for the NSFNET centered around the new NSFNET Backbone, with specific emphasis on the interface between the backbone and its attached networks.
RFC 1094	NFS: Network File System Protocol specification
	Authors: B. Nowicki. Date: March 1989 Formats: txt pdf Also: RFC 1813 Status: INFORMATIONAL This RFC describes a protocol that Sun Microsystems, Inc., and others are using. A new version of the protocol is under development, but others may benefit from the descriptions of the current protocol, and discussion of some of the design issues.
RFC 1095	Common Management Information Services and Protocol over TCP/IP (CMOT)
	Authors: U.S. Warrier, L. Besaw. Date: April 1989 Formats: txt pdf Obsoleted by: RFC 1189 Status: UNKNOWN This memo defines a network management architecture that uses the International Organization for Standardization's (ISO) Common Management Information Services/Common Management Information Protocol (CMIS/CMIP) in a TCP/IP environment. This architecture provides a means by which control and monitoring information can be exchanged between a manager and a remote network element. In particular, this memo defines the means for implementing the Draft International Standard (DIS) version of CMIS/CMIP on top of Internet transport protocols for the purpose of carrying management information defined in the Internet-standard management information base. DIS CMIS/CMIP is suitable for deployment in TCP/IP networks while CMIS/CMIP moves toward becoming an International Standard. Together with the relevant ISO standards and the companion RFCs that describe the initial structure of management information and management information base, these documents provide the basis for a comprehensive architecture and system for managing TCP/IP- based internets, and in particular the Internet.
RFC 1096	Telnet X display location option
	Authors: G.A. Marcy. Date: March 1989 Formats: txt pdf Status: PROPOSED STANDARD This RFC specifies a standard for the Internet community. Hosts on the Internet that transmit the X display location within the Telnet protocol are expected to adopt and implement this standard.
RFC 1097	Telnet subliminal-message option
	Authors: B. Miller. Date: April 1 1989 Formats: txt pdf Status: UNKNOWN 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)
	Authors: J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin. Date: April 1989 Formats: txt pdf Obsoletes: RFC 1067 Obsoleted by: RFC 1157 Status: UNKNOWN This RFC is a re-release of RFC 1067, with a changed "Status of this Memo" section. This memo defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. In particular, together with its companion memos which describe the structure of management information along with the initial management information base, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular the Internet.
RFC 1099	Request for Comments Summary: RFC Numbers 1000-1099
	Authors: J. Reynolds. Date: December 1991 Formats: txt pdf Status: INFORMATIONAL
RFC 1100	IAB official protocol standards
	Authors: Defense Advanced Research Projects Agency, Internet Activities Board. Date: April 1989 Formats: txt pdf Obsoletes: RFC 1083 Obsoleted by: RFC 1130 Status: HISTORIC This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures is presented first, followed by discussions of the standardization process and the RFC document series, then the explanation of the terms is presented, the lists of protocols in each stage of standardization follows, and finally pointers to references and contacts for further information. This memo is issued quarterly, please be sure the copy you are reading is dated within the last three months. Current copies may be obtained from the Network Information Center or from the Internet Assigned Numbers Authority (see the contact information at the end of this memo). Do not use this memo after 31-July-89.
RFC 1101	DNS encoding of network names and other types
	Authors: P.V. Mockapetris. Date: April 1989 Formats: txt pdf Updates: RFC 1034, RFC 1035 Status: UNKNOWN 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
	Authors: D.D. Clark. Date: May 1989 Formats: txt pdf Status: UNKNOWN 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
	Authors: D. Katz. Date: June 1989 Formats: txt pdf Obsoleted by: RFC 1188 Status: UNKNOWN This RFC specifies a method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK]
RFC 1104	Models of policy based routing
	Authors: H.W. Braun. Date: June 1989 Formats: txt pdf Status: UNKNOWN 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 1105	Border Gateway Protocol (BGP)
	Authors: K. Lougheed, Y. Rekhter. Date: June 1989 Formats: txt pdf Obsoleted by: RFC 1163 Status: EXPERIMENTAL This RFC outlines a specific approach for the exchange of network reachability information between Autonomous Systems. Updated by RFCs 1163 and 1164. [STANDARDS-TRACK]
RFC 1106	TCP big window and NAK options
	Authors: R. Fox. Date: June 1989 Formats: txt pdf Obsoleted by: RFC 6247 Status: HISTORIC Two extensions to the TCP protocol are described in this RFC in order to provide a more efficient operation over a network with a high bandwidth*delay product. The main issue that still needs to be solved is congestion versus noise. This issue is touched on in this memo, but further research is still needed on the applicability of the extensions in the Internet as a whole infrastructure and not just high bandwidth*delay product networks. Even with this outstanding issue, this document does describe the use of these options in the isolated satellite network environment to help facilitate more efficient use of this special medium to help off load bulk data transfers from links needed for interactive use.
RFC 1107	Plan for Internet directory services
	Authors: K.R. Sollins. Date: July 1989 Formats: txt pdf Status: INFORMATIONAL This memo proposes a program to develop a directory service for the Internet. It reports the results of a meeting held in February 1989, which was convened to review requirements and options for such a service. This proposal is offered for comment, and does not represent a committed research activity of the Internet community.
RFC 1108	U.S
	Authors: Department of Defense Security Options for the Internet Protocol. S. Kent. Date: November 1991 Formats: txt pdf Obsoletes: RFC 1038 Status: HISTORIC This RFC specifies the U.S. Department of Defense Basic SecurityOption and the top-level description of the Extended Security Option for use with the Internet Protocol. This RFC obsoletes RFC 1038"Revised IP Security Option", dated January 1988.
RFC 1109	Report of the second Ad Hoc Network Management Review Group
	Authors: V.G. Cerf. Date: August 1989 Formats: txt pdf Status: UNKNOWN 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 1110	Problem with the TCP big window option
	Authors: A.M. McKenzie. Date: August 1989 Formats: txt pdf Obsoleted by: RFC 6247 Status: HISTORIC The TCP Big Window option discussed in RFC 1106 will not work properly in an Internet environment which has both a high bandwidth * delay product and the possibility of disordering and duplicating packets. In such networks, the window size must not be increased without a similar increase in the sequence number space. Therefore, a different approach to big windows should be taken in the Internet.
RFC 1111	Request for comments on Request for Comments: Instructions to RFC authors
	Authors: J. Postel. Date: August 1989 Formats: txt pdf Obsoletes: RFC 0825 Obsoleted by: RFC 1543, RFC 2223 Status: INFORMATIONAL This RFC specifies a standard for the Internet community. Authors of RFCs are expected to adopt and implement this standard.
RFC 1112	Host extensions for IP multicasting
	Authors: S.E. Deering. Date: August 1989 Formats: txt pdf Obsoletes: RFC 0988, RFC 1054 Updated by: RFC 2236 Also: STD 0005 Status: STANDARD This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. Recommended procedure for IP multicasting in the Internet. This RFC obsoletes RFCs 998 and 1054. [STANDARDS-TRACK]
RFC 1113	Privacy enhancement for Internet electronic mail: Part I - message encipherment and authentication procedures
	Authors: J. Linn. Date: August 1989 Formats: txt pdf Obsoletes: RFC 0989, RFC 1040 Obsoleted by: RFC 1421 Status: HISTORIC This RFC specifies features for private electronic mail based on encryption technology. [STANDARDS-TRACK]
RFC 1114	Privacy enhancement for Internet electronic mail: Part II - certificate-based key management
	Authors: S.T. Kent, J. Linn. Date: August 1989 Formats: txt pdf Obsoleted by: RFC 1422 Status: HISTORIC This RFC specifies the key management aspects of Privacy Enhanced Mail. [STANDARDS-TRACK]
RFC 1115	Privacy enhancement for Internet electronic mail: Part III - algorithms, modes, and identifiers
	Authors: J. Linn. Date: August 1989 Formats: txt pdf Obsoleted by: RFC 1423 Status: HISTORIC This RFC provides definitions, references, and citations for algorithms, usage modes, and associated identifiers used in RFC-1113 and RFC-1114 in support of privacy-enhanced electronic mail. [STANDARDS-TRACK]
RFC 1116	Telnet Linemode option
	Authors: D.A. Borman. Date: August 1989 Formats: txt pdf Obsoleted by: RFC 1184 Status: PROPOSED STANDARD Hosts on the Internet that support Linemode within the Telnet protocol are expected to adopt and implement this protocol. Obsoleted by RFC 1184. [STANDARDS-TRACK]
RFC 1117	Internet numbers
	Authors: S. Romano, M.K. Stahl, M. Recker. Date: August 1989 Formats: txt pdf Obsoletes: RFC 1062, RFC 1020, RFC 0997 Obsoleted by: RFC 1166 Status: INFORMATIONAL This memo is an official status report on the network numbers and the autonomous system numbers used in the Internet community.
RFC 1118	Hitchhikers guide to the Internet
	Authors: E. Krol. Date: September 1989 Formats: txt pdf Status: INFORMATIONAL This RFC is being distributed to members of the Internet community in order to make available some "hints" which will allow new network participants to understand how the direction of the Internet is set, how to acquire online information and how to be a good Internet neighbor. While the information discussed may not be relevant to the research problems of the Internet, it may be interesting to a number of researchers and implementors. No standards are defined or specified in this memo.
RFC 1119	Network Time Protocol (version 2) specification and implementation
	Authors: D.L. Mills. Date: September 1989 Formats: txt pdf ps Obsoletes: RFC 0958, RFC 1059 Obsoleted by: RFC 1305 Status: STANDARD This document describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. NTP provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse internet operating at rates from mundane to lightwave. It uses a returnable-time design in which a distributed subnet of time servers operating in a self- organizing, hierarchical-master-slave configuration synchronizes local clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute reference time via local routing algorithms and time daemons. [STANDARDS-TRACK]
RFC 1120	Internet Activities Board
	Authors: V. Cerf. Date: September 1989 Formats: txt pdf Obsoleted by: RFC 1160 Status: INFORMATIONAL This RFC provides a history and description of the Internet Activities Board (IAB) and its subsidiary organizations. This memo is for informational use and does not constitute a standard.
RFC 1121	Act one - the poems
	Authors: J. Postel, L. Kleinrock, V.G. Cerf, B. Boehm. Date: September 1989 Formats: txt pdf Status: INFORMATIONAL This RFC presents a collection of poems that were presented at "Act One", a symposium held partially in celebration of the 20th anniversary of the ARPANET.
RFC 1122	Requirements for Internet Hosts - Communication Layers
	Authors: R. Braden, Ed.. Date: October 1989 Formats: txt pdf Updates: RFC 0793 Updated by: RFC 1349, RFC 4379, RFC 5884, RFC 6093, RFC 6298 Also: STD 0003 Status: STANDARD This RFC is an official specification for the Internet community. It incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts. [STANDARDS-TRACK]
RFC 1123	Requirements for Internet Hosts - Application and Support
	Authors: R. Braden, Ed.. Date: October 1989 Formats: txt pdf Updates: RFC 0822 Updated by: RFC 1349, RFC 2181, RFC 5321, RFC 5966 Also: STD 0003 Status: STANDARD This RFC is an official specification for the Internet community. It incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts. [STANDARDS-TRACK]
RFC 1124	Policy issues in interconnecting networks
	Authors: B.M. Leiner. Date: September 1989 Formats: txt pdf ps Status: UNKNOWN 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
	Authors: D. Estrin. Date: November 1989 Formats: txt pdf ps Status: UNKNOWN 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 pdf Status: UNKNOWN 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 1127	Perspective on the Host Requirements RFCs
	Authors: R.T. Braden. Date: October 1989 Formats: txt pdf Status: INFORMATIONAL This RFC is for information only; it does not constitute a standard, draft standard, or proposed standard, and it does not define a protocol.
RFC 1128	Measured performance of the Network Time Protocol in the Internet system
	Authors: D.L. Mills. Date: October 1989 Formats: txt pdf ps Status: UNKNOWN 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.
RFC 1129	Internet Time Synchronization: The Network Time Protocol
	Authors: D.L. Mills. Date: October 1989 Formats: txt pdf ps Also: RFC 1119 Status: INFORMATIONAL This memo describes the Network Time Protocol (NTP) designed to distribute time information in a large, diverse internet system operating at speeds from mundane to lightwave. It uses a returnable- time architecture in which a distributed subnet of time servers operating in a self-organizing, hierarchical, master-slave configuration synchronizes local clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute time information within a network via local routing algorithms and time daemons. The architectures, algorithms and protocols which have evolved to NTP over several years of implementation and refinement are described in this paper. The synchronization subnet which has been in regular operation in the Internet for the last several years is described 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 in cases of failure or disruption of clocks, time servers or networks. This memo describes the Network Time Protocol in RFC-1119.
RFC 1130	IAB official protocol standards
	Authors: Defense Advanced Research Projects Agency, Internet Activities Board. Date: October 1989 Formats: txt pdf Obsoletes: RFC 1100 Obsoleted by: RFC 1140 Status: HISTORIC This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB).
RFC 1131	OSPF specification
	Authors: J. Moy. Date: October 1989 Formats: txt pdf ps Obsoleted by: RFC 1247 Status: PROPOSED STANDARD This RFC is the specification of the Open Shortest Path First (OSPF) Internet routing protocol. OSPF is in the class of Internal Gateway Protocols (IGPs) for distributing routing information between gateways of a single Autonomous System. This routing protocol is based on the link-state approach (in contrast to the distance-vector approach). This specification was developed by the OSPF Working Group of the Internet Engineering Task Force. [STANDARDS-TRACK]
RFC 1132	Standard for the transmission of 802.2 packets over IPX networks
	Authors: L.J. McLaughlin. Date: November 1989 Formats: txt pdf Also: STD 0049 Status: STANDARD This document specifies a standard method of encapsulating 802.2 packets on networks supporting Novell's Internet Packet Exchange Protocol (IPX). It obsoletes earlier documents detailing the transmission of Internet packets over IPX networks. It differs from these earlier documents in that it allows for the transmission of multiple network protocols over IPX and for the transmission of packets through IPX bridges.
RFC 1133	Routing between the NSFNET and the DDN
	Authors: J.Y. Yu, H.W. Braun. Date: November 1989 Formats: txt pdf Status: INFORMATIONAL This document is a case study of the implementation of routing between the NSFNET and the DDN components (the MILNET and the ARPANET). We hope that it can be used to expand towards interconnection of other Administrative Domains. We would welcome discussion and suggestions about the methods employed for the interconnections. No standards are specified in this memo.
RFC 1134	Point-to-Point Protocol: A proposal for multi-protocol transmission of datagrams over Point-to-Point links
	Authors: D. Perkins. Date: November 1989 Formats: txt pdf Obsoleted by: RFC 1171 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is composed of three parts: 1. A method for encapsulating datagrams over serial links. 2. An extensible Link Control Protocol (LCP). 3. A family of Network Control Protocols (NCP) for establishing and configuring different network-layer protocols. This document defines the encapsulation scheme, the basic LCP, and anNCP for establishing and configuring the Internet Protocol (IP)(called the IP Control Protocol, IPCP). The options and facilities used by the LCP and the IPCP are defined in separate documents. Control protocols for configuring and utilizing other network-layer protocols besides IP (e.g., DECNET,OSI) are expected to be developed as needed.
RFC 1135	Helminthiasis of the Internet
	Authors: J.K. Reynolds. Date: December 1989 Formats: txt pdf Status: INFORMATIONAL This memo takes a look back at the helminthiasis (infestation with, or disease caused by parasitic worms) of the Internet that was unleashed the evening of 2 November 1988. This RFC provides information about an event that occurred in the life of the Internet. This memo does not specify any standard. This document provides a glimpse at the infection, its festering, and cure. The impact of the worm on the Internet community, ethics statements, the role of the news media, crime in the computer world, and future prevention is discussed. A documentation review presents four publications that describe in detail this particular parasitic computer program. Reference and bibliography sections are also included.
RFC 1136	Administrative Domains and Routing Domains: A model for routing in the Internet
	Authors: S. Hares, D. Katz. Date: December 1989 Formats: txt pdf Status: INFORMATIONAL This RFC proposes a model for describing routing within the Internet. The model is an adaptation of the "OSI Routeing Framework". This memo does not specify an Internet standard.
RFC 1137	Mapping between full RFC 822 and RFC 822 with restricted encoding
	Authors: S. Kille. Date: December 1989 Formats: txt pdf Updates: RFC 0976 Status: HISTORIC This RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard.
RFC 1138	Mapping between X.400(1988) / ISO 10021 and RFC 822
	Authors: S.E. Kille. Date: December 1989 Formats: txt pdf Obsoleted by: RFC 2156, RFC 1327 Updates: RFC 1026, RFC 0987, RFC 0822 Updated by: RFC 1148 Status: EXPERIMENTAL Ths RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. This memo updates RFCs 822, 987, and 1026.
RFC 1139	Echo function for ISO 8473
	Authors: R.A. Hagens. Date: January 1990 Formats: txt pdf Obsoleted by: RFC 1574, RFC 1575 Status: PROPOSED STANDARD This memo defines an echo function for the connection-less network layer protocol. Two mechanisms are introduced that may be used to implement the echo function. The first mechanism is recommended as an interim solution for the Internet community. The second mechanism will be progressed to the ANSI X3S3.3 working group for consideration as a work item. When an ISO standard is adopted that provides functionality similar to that described by this memo, then this memo will become obsolete and superceded by the ISO standard.
RFC 1140	IAB official protocol standards
	Authors: Defense Advanced Research Projects Agency, Internet Activities Board. Date: May 1990 Formats: txt pdf Obsoletes: RFC 1130 Obsoleted by: RFC 1200 Status: HISTORIC This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo is issued quarterly, please be sure the copy you are reading is dated within the last three months. Current copies may be obtained from the Network Information Center or from the Internet Assigned Numbers Authority. Do not use this edition after 31-Aug-90.
RFC 1141	Incremental updating of the Internet checksum
	Authors: T. Mallory, A. Kullberg. Date: January 1990 Formats: txt pdf Updates: RFC 1071 Updated by: RFC 1624 Status: INFORMATIONAL This memo correctly describes the incremental update procedure for use with the standard Internet checksum. It is intended to replace the description of Incremental Update in RFC 1071. This is not a standard but rather, an implementation technique.
RFC 1142	OSI IS-IS Intra-domain Routing Protocol
	Authors: D. Oran, Ed.. Date: February 1990 Formats: txt pdf ps Status: INFORMATIONAL This RFC is a republication of ISO DP 10589 as a service to the Internet community. This is not an Internet standard.
RFC 1143	The Q Method of Implementing TELNET Option Negotiation
	Authors: D.J. Bernstein. Date: February 1990 Formats: txt pdf Status: EXPERIMENTAL This is RFC discusses an implementation approach to option negotiation in the Telnet protocol (RFC 854). It does not propose any changes to the TELNET protocol. Rather, it discusses the implementation of the protocol of one feature, only. This is not a protocol specification. This is an experimental method of implementing a protocol.
RFC 1144	Compressing TCP/IP Headers for Low-Speed Serial Links
	Authors: V. Jacobson. Date: February 1990 Formats: txt pdf ps Status: PROPOSED STANDARD This RFC describes a method for compressing the headers of TCP/IP datagrams to improve performance over low speed serial links. The motivation, implementation and performance of the method are described. C code for a sample implementation is given for reference. [STANDARDS- TRACK]
RFC 1145	TCP alternate checksum options
	Authors: J. Zweig, C. Partridge. Date: February 1990 Formats: txt pdf Obsoleted by: RFC 1146, RFC 6247 Status: HISTORIC This memo is suggests a pair of TCP options to allow use of alternate data checksum algorithms in the TCP header. The use of these options is experimental, and not recommended for production use.
RFC 1146	TCP alternate checksum options
	Authors: J. Zweig, C. Partridge. Date: March 1990 Formats: txt pdf Obsoletes: RFC 1145 Obsoleted by: RFC 6247 Status: HISTORIC This memo is suggests a pair of TCP options to allow use of alternate data checksum algorithms in the TCP header. The use of these options is experimental, and not recommended for production use. Note: This RFC corrects errors introduced in the editing process in RFC 1145.
RFC 1147	FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices
	Authors: R.H. Stine. Date: April 1990 Formats: txt pdf ps Obsoleted by: RFC 1470 Status: INFORMATIONAL The goal of this FYI memo is to provide practical information to site administrators and network managers. This memo provides information for the Internet community. It does not specify any standard. It is not a statement of IAB policy or recommendations. [Also FYI 2.] This catalog contains descriptions of several tools available to assist network managers in debugging and maintaining TCP/IP internets and interconnected communications resources. Entries in the catalog tell what a tool does, how it works, and how it can be obtained.
RFC 1148	Mapping between X.400(1988) / ISO 10021 and RFC 822
	Authors: S.E. Kille. Date: March 1990 Formats: txt pdf Obsoleted by: RFC 2156, RFC 1327 Updates: RFC 1026, RFC 0987, RFC 1138, RFC 0822 Status: EXPERIMENTAL This RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. This edition includes material lost in editing.
RFC 1149	Standard for the transmission of IP datagrams on avian carriers
	Authors: D. Waitzman. Date: April 1 1990 Formats: txt pdf Updated by: RFC 2549 Status: EXPERIMENTAL This memo describes an experimental method for the encapsulation of IP datagrams in avian carriers. This specification is primarily useful in Metropolitan Area Networks. This is an experimental, not recommended standard.
RFC 1150	FYI on FYI: Introduction to the FYI Notes
	Authors: G.S. Malkin, J.K. Reynolds. Date: March 1990 Formats: txt pdf Obsoleted by: RFC 6360 Status: HISTORIC This memo is the first in a new sub-series of RFCs called FYIs (For Your Information). This memo provides information for the Internet community. It does not specify any standard. [Also FYI 1.]
RFC 1151	Version 2 of the Reliable Data Protocol (RDP)
	Authors: C. Partridge, R.M. Hinden. Date: April 1990 Formats: txt pdf Updates: RFC 0908 Status: EXPERIMENTAL This RFC suggests several updates to the specification of the Reliable Data Protocol (RDP) in RFC-908 based on experience with the protocol. This revised version of the protocol is experimental.
RFC 1152	Workshop report: Internet research steering group workshop on very-high-speed networks
	Authors: C. Partridge. Date: April 1990 Formats: txt pdf Status: INFORMATIONAL This memo is a report on a workshop sponsored by the Internet Research Steering Group. This memo is for information only. This RFC does not specify an Internet standard.
RFC 1153	Digest message format
	Authors: F.J. Wancho. Date: April 1990 Formats: txt pdf Status: EXPERIMENTAL This memo describes the de facto standard Digest Message Format. This is an elective experimental protocol.
RFC 1154	Encoding header field for internet messages
	Authors: D. Robinson, R. Ullmann. Date: April 1990 Formats: txt pdf Obsoleted by: RFC 1505 Status: EXPERIMENTAL This RFC proposes an elective experimental Encoding header field to permit the mailing of multi-part, multi-structured messages. The use of Encoding updates RFC 1049 (Content-Type), and is a suggested update to RFCs 1113, 1114, and 1115 (Privacy Enhancement).
RFC 1155	Structure and identification of management information for TCP/IP-based internets
	Authors: M.T. Rose, K. McCloghrie. Date: May 1990 Formats: txt pdf Obsoletes: RFC 1065 Also: STD 0016 Status: STANDARD This RFC is a re-release of RFC 1065, with a changed "Status of this Memo", plus a few minor typographical corrections. The technical content of the document is unchanged from RFC 1065. [STANDARDS-TRACK]
RFC 1156	Management Information Base for network management of TCP/IP-based internets
	Authors: K. McCloghrie, M.T. Rose. Date: May 1990 Formats: txt pdf Obsoletes: RFC 1066 Status: HISTORIC This RFC is a re-release of RFC 1066, with a changed "Status of this Memo", "IAB Policy Statement", and "Introduction" sections plus a few minor typographical corrections. The technical content of the document is unchanged from RFC 1066. [STANDARDS-TRACK]
RFC 1157	Simple Network Management Protocol (SNMP)
	Authors: J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin. Date: May 1990 Formats: txt pdf Obsoletes: RFC 1098 Status: HISTORIC This RFC is a re-release of RFC 1098, with a changed "Status of this Memo" section plus a few minor typographical corrections. This memo defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. [STANDARDS-TRACK]
RFC 1158	Management Information Base for network management of TCP/IP-based internets: MIB-II
	Authors: M.T. Rose. Date: May 1990 Formats: txt pdf Obsoleted by: RFC 1213 Status: PROPOSED STANDARD This memo defines the second version of the Management Information Base (MIB-II) for use with network management protocols in TCP/IP- based internets. In particular, together with its companion memos which describe the structure of management information (RFC 1155) along with the network management protocol (RFC 1157) for TCP/IP- based internets, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular the Internet community. This document on MIB-II incorporates all of the technical content of RFC 1156 on MIB-I and extends it, without loss of compatibilty. [STANDARDS-TRACK]
RFC 1159	Message Send Protocol
	Authors: R. Nelson. Date: June 1990 Formats: txt pdf Obsoleted by: RFC 1312 Status: EXPERIMENTAL This RFC suggests an Experimental Protocol for the Internet community. Hosts on the Internet that choose to implement a Message Send Protocol may experiment with this protocol.
RFC 1160	Internet Activities Board
	Authors: V. Cerf. Date: May 1990 Formats: txt pdf Obsoletes: RFC 1120 Status: INFORMATIONAL This RFC provides a history and description of the Internet Activities Board (IAB) and its subsidiary organizations. This memo is for informational use and does not constitute a standard. This is a revision of RFC 1120.
RFC 1161	SNMP over OSI
	Authors: M.T. Rose. Date: June 1990 Formats: txt pdf Obsoleted by: RFC 1418 Status: EXPERIMENTAL This memo defines an experimental means for running the Simple Network Management Protocol (SNMP) over OSI transports. This memo does not specify a standard for the Internet community,
RFC 1162	Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) Management Information Base
	Authors: G. Satz. Date: June 1990 Formats: txt pdf Obsoleted by: RFC 1238 Status: EXPERIMENTAL This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. This memo does not specify a standard for the Internet community.
RFC 1163	Border Gateway Protocol (BGP)
	Authors: K. Lougheed, Y. Rekhter. Date: June 1990 Formats: txt pdf Obsoletes: RFC 1105 Obsoleted by: RFC 1267 Status: HISTORIC This RFC, together with its companion RFC-1164, "Application of the Border Gateway Protocol in the Internet", specify an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK]
RFC 1164	Application of the Border Gateway Protocol in the Internet
	Authors: J.C. Honig, D. Katz, M. Mathis, Y. Rekhter, J.Y. Yu. Date: June 1990 Formats: txt pdf Obsoleted by: RFC 1268 Status: HISTORIC This RFC, together with its companion RFC-1163, "A Border Gateway Protocol (BGP)", specify an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK]
RFC 1165	Network Time Protocol (NTP) over the OSI Remote Operations Service
	Authors: J. Crowcroft, J.P. Onions. Date: June 1990 Formats: txt pdf Status: EXPERIMENTAL This memo suggests an Experimental Protocol for the OSI and Internet communities. Hosts in either community, and in particular those on both are encouraged to experiment with this mechanism.
RFC 1166	Internet numbers
	Authors: S. Kirkpatrick, M.K. Stahl, M. Recker. Date: July 1990 Formats: txt pdf Obsoletes: RFC 1117, RFC 1062, RFC 1020 Updated by: RFC 5737 Status: INFORMATIONAL This memo is a status report on the network numbers and autonomous system numbers used in the Internet community.
RFC 1167	Thoughts on the National Research and Education Network
	Authors: V.G. Cerf. Date: July 1990 Formats: txt pdf Status: INFORMATIONAL The memo provides a brief outline of a National Research and Education Network (NREN). This memo provides information for the Internet community. It does not specify any standard. It is not a statement of IAB policy or recommendations.
RFC 1168	Intermail and Commercial Mail Relay services
	Authors: A. Westine, A.L. DeSchon, J. Postel, C.E. Ward. Date: July 1990 Formats: txt pdf ps Status: INFORMATIONAL This RFC discusses the history and evolution of the Intermail and Commercial mail systems. The problems encountered in operating a store-and-forward mail relay between commercial systems such as Telemail, MCI Mail and Dialcom are also discussed. This RFC provides information for the Internet community, and does not specify any standard.
RFC 1169	Explaining the role of GOSIP
	Authors: V.G. Cerf, K.L. Mills. Date: August 1990 Formats: txt pdf Status: INFORMATIONAL This informational RFC represents the official view of the Internet Activities Board (IAB), after coordination with the Federal Networking Council (FNC). This RFC does not specify a standard.
RFC 1170	Public key standards and licenses
	Authors: R.B. Fougner. Date: January 1991 Formats: txt pdf Status: INFORMATIONAL This RFC is a public statement by Public Key Partners regarding Public Key Standards and Licenses. This memo is for informational use only, and does not constitute an Internet standard.
RFC 1171	Point-to-Point Protocol for the transmission of multi-protocol datagrams over Point-to-Point links
	Authors: D. Perkins. Date: July 1990 Formats: txt pdf Obsoletes: RFC 1134 Obsoleted by: RFC 1331 Status: DRAFT STANDARD The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is composed of three parts: 1. A method for encapsulating datagrams over serial links. 2. An extensible Link Control Protocol (LCP). 3. A family of Network Control Protocols (NCP) for establishing and configuring different network-layer protocols. This document defines the encapsulation scheme, the basic LCP, and anNCP for establishing and configuring the Internet Protocol (IP)(called the IP Control Protocol, IPCP). The options and facilities used by the LCP and the IPCP are defined in separate documents. Control protocols for configuring and utilizing other network-layer protocols besides IP (e.g., DECNET,OSI) are expected to be developed as needed.
RFC 1172	Point-to-Point Protocol (PPP) initial configuration options
	Authors: D. Perkins, R. Hobby. Date: July 1990 Formats: txt pdf Obsoleted by: RFC 1331, RFC 1332 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is composed of 1) a method for encapsulating datagrams over serial links,2) an extensible Link Control Protocol (LCP), and3) a family of Network Control Protocols (NCP) for establishing and configuring different network-layer protocols. The PPP encapsulating scheme, the basic LCP, and an NCP for controlling and establishing the Internet Protocol (IP) (called theIP Control Protocol, IPCP) are defined in The Point-to-Point Protocol(PPP) [1]. This document defines the intial options used by the LCP and IPCP. It also defines a method of Link Quality Monitoring and a simple authentication scheme.
RFC 1173	Responsibilities of host and network managers: A summary of the "oral tradition" of the Internet
	Authors: J. VanBokkelen. Date: August 1990 Formats: txt pdf Status: INFORMATIONAL This informational RFC describes the conventions to be followed by those in charge of networks and hosts in the Internet. It is a summary of the "oral tradition" of the Internet on this subject. [RFC Editor's note: This memo is a contribution by the author of his view of these conventions. It is expected that this RFC will provide a basis for the development of official policies in the future.] These conventions may be supplemented or amended by the policies of specific local and regional components of the Internet. This RFC does not specify a standard, or a policy of the IAB.
RFC 1174	IAB recommended policy on distributing internet identifier assignment and IAB recommended policy change to internet "connected" status
	Authors: V.G. Cerf. Date: August 1990 Formats: txt pdf Status: INFORMATIONAL This informational RFC represents the official view of the Internet Activities Board (IAB), and describes the recommended policies and procedures on distributing Internet identifier assignments and dropping the connected status requirement. This RFC does not specify a standard.
RFC 1175	FYI on where to start: A bibliography of internetworking information
	Authors: K.L. Bowers, T.L. LaQuey, J.K. Reynolds, K. Roubicek, M.K. Stahl, A. Yuan. Date: August 1990 Formats: txt pdf Also: FYI 0003 Status: INFORMATIONAL The intent of this bibliography is to offer a representative collection of resources of information that will help the reader become familiar with the concepts of internetworking. It is meant to be a starting place for further research. There are references to other sources of information for those users wishing to pursue, in greater depth, the issues and complexities of the current networking environment.
RFC 1176	Interactive Mail Access Protocol: Version 2
	Authors: M.R. Crispin. Date: August 1990 Formats: txt pdf Obsoletes: RFC 1064 Status: EXPERIMENTAL This RFC suggests a method for personal computers and workstations to dynamically access mail from a mailbox server ("repository"). It obosoletes RFC 1064. This RFC specifies an Experimental Protocol for the Internet community. Discussion and suggestions for improvement are requested. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol.
RFC 1177	FYI on Questions and Answers: Answers to commonly asked "new internet user" questions
	Authors: G.S. Malkin, A.N. Marine, J.K. Reynolds. Date: August 1990 Formats: txt pdf Obsoleted by: RFC 1206 Status: INFORMATIONAL This FYI RFC is one of three FYI's called, "Questions and Answers" (Q/A), produced by the User Services Working Group (USWG) of the Internet Engineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify any standard. [Also FYI 4.]
RFC 1178	Choosing a name for your computer
	Authors: D. Libes. Date: August 1990 Formats: txt pdf Also: FYI 0005 Status: INFORMATIONAL In order to easily distinguish between multiple computers, we give them names. Experience has taught us that it is as easy to choose bad names as it is to choose good ones. This essay presents guidelines for deciding what makes a name good or bad. Keywords: domain name system, naming conventions, computer administration, computer network management
RFC 1179	Line printer daemon protocol
	Authors: L. McLaughlin. Date: August 1990 Formats: txt pdf Status: INFORMATIONAL This RFC describes an existing print server protocol widely used on the Internet for communicating between line printer daemons (both clients and servers). This memo is for informational purposes only, and does not specify an Internet standard. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol.
RFC 1180	TCP/IP tutorial
	Authors: T.J. Socolofsky, C.J. Kale. Date: January 1991 Formats: txt pdf Status: INFORMATIONAL This RFC is a tutorial on the TCP-IP protocol suite, focusing particularly on the steps in forwarding an IP datagram from source host to destination host through a router. It does not specify an Internet standard.
RFC 1181	RIPE Terms of Reference
	Authors: R. Blokzijl. Date: September 1990 Formats: txt pdf Status: INFORMATIONAL This RFC describes the Terms of Reference of RIPE (Reseaux IP Europeens), the cooperation of European IP networks. This memo provides information for the Internet community. It does not specify any standard.
RFC 1183	New DNS RR Definitions
	Authors: C.F. Everhart, L.A. Mamakos, R. Ullmann, P.V. Mockapetris. Date: October 1990 Formats: txt pdf Updates: RFC 1034, RFC 1035 Updated by: RFC 5395, RFC 5864, RFC 6195 Status: EXPERIMENTAL This memo defines five new DNS types for experimental purposes. This RFC describes an Experimental Protocol for the Internet community, and requests discussion and suggestions for improvements.
RFC 1184	Telnet Linemode Option
	Authors: D.A. Borman. Date: October 1990 Formats: txt pdf Obsoletes: RFC 1116 Status: DRAFT STANDARD This RFC specifies a procedure for line at a time terminal interaction based on the Telnet Protocol. It obsoletes RFC 1116. [STANDARDS-TRACK]
RFC 1185	TCP Extension for High-Speed Paths
	Authors: V. Jacobson, R.T. Braden, L. Zhang. Date: October 1990 Formats: txt pdf Obsoleted by: RFC 1323 Status: EXPERIMENTAL This memo describes an Experimental Protocol extension to TCP for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol.
RFC 1186	MD4 Message Digest Algorithm
	Authors: R.L. Rivest. Date: October 1990 Formats: txt pdf Obsoleted by: RFC 1320 Status: INFORMATIONAL This RFC is the specification of the MD4 Digest Algorithm. If you are going to implement MD4, it is suggested you do it this way. This memo is for informational use and does not constitute a standard.
RFC 1187	Bulk Table Retrieval with the SNMP
	Authors: M.T. Rose, K. McCloghrie, J.R. Davin. Date: October 1990 Formats: txt pdf Status: EXPERIMENTAL This memo reports an interesting family of algorithms for bulk table retrieval using the Simple Network Management Protocol (SNMP). This memo describes an Experimental Protocol for the Internet community, and requests discussion and suggestions for improvements. This memo does not specify a standard for the Internet community. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol.
RFC 1188	Proposed Standard for the Transmission of IP Datagrams over FDDI Networks
	Authors: D. Katz. Date: October 1990 Formats: txt pdf Obsoletes: RFC 1103 Status: DRAFT STANDARD This document specifies a method for the use of IP and ARP on FDDI networks. The encapsulation method used is described, as well as various media-specific issues.
RFC 1189	Common Management Information Services and Protocols for the Internet (CMOT and CMIP)
	Authors: U.S. Warrier, L. Besaw, L. LaBarre, B.D. Handspicker. Date: October 1990 Formats: txt pdf Obsoletes: RFC 1095 Status: HISTORIC This memo defines a network management architecture that uses the International Organization for Standardization's (ISO) Common Management Information Services/Common Management Information Protocol (CMIS/CMIP) in the Internet. [STANDARDS-TRACK]
RFC 1190	Experimental Internet Stream Protocol: Version 2 (ST-II)
	Authors: C. Topolcic. Date: October 1990 Formats: txt pdf Obsoletes: IEN 119 Obsoleted by: RFC 1819 Status: EXPERIMENTAL This memo defines a revised version of the Internet Stream Protocol, originally defined in IEN-119 [8], based on results from experiments with the original version, and subsequent requests, discussion, and suggestions for improvements. This is a Limited-Use Experimental Protocol. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol.
RFC 1191	Path MTU discovery
	Authors: J.C. Mogul, S.E. Deering. Date: November 1990 Formats: txt pdf Obsoletes: RFC 1063 Status: DRAFT STANDARD This memo describes a technique for dynamically discovering the maximum transmission unit (MTU) of an arbitrary internet path. It specifies a small change to the way routers generate one type of ICMP message. For a path that passes through a router that has not been so changed, this technique might not discover the correct Path MTU, but it will always choose a Path MTU as accurate as, and in many cases more accurate than, the Path MTU that would be chosen by current practice.
RFC 1192	Commercialization of the Internet summary report
	Authors: B. Kahin. Date: November 1990 Formats: txt pdf Status: INFORMATIONAL This memo is based on a workshop held by the Science, Technology and Public Policy Program of the John F. Kennedy School of Government, Harvard University, March 1-3, 1990. This memo provides information for the Internet community. It does not specify any standard.
RFC 1193	Client requirements for real-time communication services
	Authors: D. Ferrari. Date: November 1990 Formats: txt pdf Status: INFORMATIONAL A real-time communication service provides its clients with the ability to specify their performance requirements and to obtain guarantees about the satisfaction of those requirements. In this paper, we propose a set of performance specifications that seem appropriate for such services; they include various types of delay bounds, throughput bounds, and reliability bounds. We also describe other requirements and desirable properties from a client's viewpoint, and the ways in which each requirement is to be translated to make it suitable for lower levels in the protocol hierarchy.Finally, we present some examples of requirements specification, and discuss some of the possible objections to our approach. This research has been supported in part by AT&T Bell Laboratories, the University of California under a MICRO grant, and theInternational Computer Science Institute. The views and conclusions in this document are those of the author and should not be interpreted as representing official policies, either expressed or implied, of any of the sponsoring organizations.
RFC 1194	Finger User Information Protocol
	Authors: D.P. Zimmerman. Date: November 1990 Formats: txt pdf Obsoletes: RFC 0742 Obsoleted by: RFC 1196, RFC 1288 Status: DRAFT STANDARD This memo describes the Finger User Information Protocol. This is a simple protocol which provides an interface to a remote user information program. Based on RFC 742, a description of the original Finger protocol, this memo attempts to clarify the expected communication between the two ends of a Finger connection. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition.
RFC 1195	Use of OSI IS-IS for routing in TCP/IP and dual environments
	Authors: R.W. Callon. Date: December 1990 Formats: txt pdf ps Updated by: RFC 1349, RFC 5302, RFC 5304 Status: PROPOSED STANDARD This RFC specifies an integrated routing protocol, based on the OSIIntra-Domain IS-IS Routing Protocol, which may be used as an interior gateway protocol (IGP) to support TCP/IP as well as OSI. This allows a single routing protocol to be used to support pure IP environments, pure OSI environments, and dual environments. This specification was developed by the IS-IS working group of the Internet Engineering TaskForce. The OSI IS-IS protocol has reached a mature state, and is ready for implementation and operational use. The most recent version of theOSI IS-IS protocol is contained in ISO DP 10589 [1]. The proposed standard for using IS-IS for support of TCP/IP will therefore make use of this version (with a minor bug correction, as discussed inAnnex B). We expect that future versions of this proposed standard will upgrade to the final International Standard version of IS-IS when available. Comments should be sent to "isis@merit.edu".
RFC 1196	Finger User Information Protocol
	Authors: D.P. Zimmerman. Date: December 1990 Formats: txt pdf Obsoletes: RFC 1194, RFC 0742 Obsoleted by: RFC 1288 Status: DRAFT STANDARD This memo describes the Finger User Information Protocol. This is a simple protocol which provides an interface to a remote user information program. Based on RFC 742, a description of the original Finger protocol, this memo attempts to clarify the expected communication between the two ends of a Finger connection. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition. This edition corrects and clarifies in a minor way, RFC 1194.
RFC 1197	Using ODA for translating multimedia information
	Authors: M. Sherman. Date: December 1990 Formats: txt pdf Status: INFORMATIONAL The purpose of this RFC is to inform implementors of multimedia systems about our experiences using ISO 8613: Office Document Architecture (ODA). Because ODA is being proposed as an encoding format for use in multimedia mail and file exchange, implementors wishing to use ODA in an open systems environment may profit from our experiences. This memo provides information for the Internet community. It does not specify any standard.
RFC 1198	FYI on the X window system
	Authors: R.W. Scheifler. Date: January 1991 Formats: txt pdf Also: FYI 0006 Status: INFORMATIONAL This FYI RFC provides pointers to the published standards of the MIT X Consortium. This memo provides information for the Internet community. It does not specify any Internet standard.
RFC 1199	Request for Comments Summary Notes: 1100-1199
	Authors: J. Reynolds. Date: December 1991 Formats: txt pdf Status: INFORMATIONAL
RFC 1200	IAB official protocol standards
	Authors: Defense Advanced Research Projects Agency, Internet Activities Board. Date: April 1991 Formats: txt pdf Obsoletes: RFC 1140 Obsoleted by: RFC 1250 Status: HISTORIC This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures is presented first, followed by discussions of the standardization process and the RFC document series, then the explanation of the terms is presented, the lists of protocols in each stage of standardization follows, and finally pointers to references and contacts for further information.
RFC 1201	Transmitting IP traffic over ARCNET networks
	Authors: D. Provan. Date: February 1991 Formats: txt pdf Obsoletes: RFC 1051 Also: STD 0046 Status: STANDARD This memo defines a protocol for the transmission of IP and ARP packets over the ARCnet Local Area Network.This memo specifies a method of encapsulating Internet Protocol (IP) and Address Resolution Protocol (ARP) datagrams for transmission across ARCNET using the "ARCNET Packet Header Definition Standard". [STANDARDS-TRACK]
RFC 1202	Directory Assistance service
	Authors: M.T. Rose. Date: February 1991 Formats: txt pdf Status: INFORMATIONAL This document defines a mechanism by which a user-interface may access a textual DAP-like interface over a TCP/IP connection. This is a local mechanism. This memo provides information for the Internet community. It does not specify any standard.
RFC 1203	Interactive Mail Access Protocol: Version 3
	Authors: J. Rice. Date: February 1991 Formats: txt pdf Obsoletes: RFC 1064 Status: HISTORIC This RFC suggests a method for workstations to access mail dynamically from a mailbox server ("repository"). The following document is a modified version of RFC 1064, the definition of the IMAP2 protocol. This RFC specifies an Experimental Protocol for the Internet community. It does not specify any standard.
RFC 1204	Message Posting Protocol (MPP)
	Authors: S. Yeh, D. Lee. Date: February 1991 Formats: txt pdf Status: EXPERIMENTAL This memo describes a protocol for posting messages from workstations (e.g., PCs) to a mail service host. This RFC specifies an Experimental Protocol for the Internet community. It does not specify any standard.
RFC 1205	5250 Telnet interface
	Authors: P. Chmielewski. Date: February 1991 Formats: txt pdf Updated by: RFC 2877 Status: INFORMATIONAL This RFC is being distributed in order to document the interface to the IBM 5250 Telnet implementation. This memo provides information for the Internet community. It does not specify any standard.
RFC 1206	FYI on Questions and Answers: Answers to commonly asked "new Internet user" questions
	Authors: G.S. Malkin, A.N. Marine. Date: February 1991 Formats: txt pdf Obsoletes: RFC 1177 Obsoleted by: RFC 1325 Status: INFORMATIONAL This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify any standard. [FYI 4]
RFC 1207	FYI on Questions and Answers: Answers to commonly asked "experienced Internet user" questions
	Authors: G.S. Malkin, A.N. Marine, J.K. Reynolds. Date: February 1991 Formats: txt pdf Also: FYI 0007 Status: INFORMATIONAL This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A), produced by the User Services Working Group of the Internet Engineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify any standard.
RFC 1208	A Glossary of Networking Terms
	Authors: O.J. Jacobsen, D.C. Lynch. Date: March 1991 Formats: txt pdf Status: INFORMATIONAL This RFC is a glossary adapted from "The INTEROP Pocket Glossary of Networking Terms" distributed at Interop '90. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1209	The Transmission of IP Datagrams over the SMDS Service
	Authors: D. Piscitello, J. Lawrence. Date: March 1991 Formats: txt pdf Also: STD 0052 Status: STANDARD This memo describes an initial use of IP and ARP in an SMDS service environment configured as a logical IP subnetwork, LIS (described below). The encapsulation method used is described, as well as various service-specific issues. This memo does not preclude subsequent treatment of the SMDS Service in configurations other thanLIS; specifically, public or inter-company, inter-enterprise configurations may be treated differently and will be described in future documents. This document considers only directly connected IP end-stations or routers; issues raised by MAC level bridging are beyond the scope of this paper.
RFC 1210	Network and infrastructure user requirements for transatlantic research collaboration: Brussels, July 16-18, and Washington July 24-25, 1990
	Authors: V.G. Cerf, P.T. Kirstein, B. Randell. Date: March 1991 Formats: txt pdf Status: INFORMATIONAL This report summarises user requirements for networking and related infrastructure facilities needed to enable effective cooperation between US and European research teams participating in the plannedESPRIT-DARPA/NSF programme of collaborative research in InformationScience and Technology. It analyses the problems and disparities of the current facilities, and suggests appropriate one and three year targets for improvements. It proposes a number of initial actions aimed at achieving these targets. Finally, the workshop has identified a non-exhaustive set of important issues upon which support of future research will depend. These issues could be studied in the short term, with the aim of initiating a programme of joint research in collaboration technology within the next year.
RFC 1211	Problems with the maintenance of large mailing lists
	Authors: A. Westine, J. Postel. Date: March 1991 Formats: txt pdf Status: INFORMATIONAL This RFC discusses problems with maintaining large mailing lists, especially the processing of error reports. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1212	Concise MIB definitions
	Authors: M.T. Rose, K. McCloghrie. Date: March 1991 Formats: txt pdf Also: STD 0016 Status: STANDARD This memo describes a straight-forward approach toward producing concise, yet descriptive, MIB modules. This memo defines a format for producing MIB modules. [STANDARDS-TRACK]
RFC 1213	Management Information Base for Network Management of TCP/IP-based internets:MIB-II
	Authors: K. McCloghrie, M. Rose. Date: March 1991 Formats: txt pdf Obsoletes: RFC 1158 Updated by: RFC 2011, RFC 2012, RFC 2013 Also: STD 0017 Status: STANDARD This memo defines the second version of the Management Information Base (MIB-II) for use with network management protocols in TCP/IP-based internets. [STANDARDS-TRACK]
RFC 1214	OSI internet management: Management Information Base
	Authors: L. LaBarre. Date: April 1991 Formats: txt pdf Status: HISTORIC This RFC documents a MIB for use with CMIP, either over pure OSI stacks or with the CMIP over TCP specification. It redefines objects comprised by the second revision of the Management Information Base for Network Management of TCP/IP-based internets: MIB-II so as to conform to the OSI structure of management information. This document is a product of the IETF OIM working group.
RFC 1215	Convention for defining traps for use with the SNMP
	Authors: M.T. Rose. Date: March 1991 Formats: txt pdf Status: INFORMATIONAL This memo suggests a straight-forward approach towards defining traps used with the SNMP. This memo provides information for the Internet community. It does not specify any standard.
RFC 1216	Gigabit network economics and paradigm shifts
	Authors: P. Richard, P. Kynikos. Date: April 1 1991 Formats: txt pdf Status: INFORMATIONAL This memo proposes a new standard paradigm for the Internet Activities Board (IAB) standardization track. [STANDARDS-TRACK]
RFC 1217	Memo from the Consortium for Slow Commotion Research (CSCR)
	Authors: V.G. Cerf. Date: April 1 1991 Formats: txt pdf Status: INFORMATIONAL This RFC is in response to RFC 1216, "Gigabit Network Economics and Paradigm Shifts". This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1218	Naming scheme for c=US
	Authors: North American Directory Forum. Date: April 1991 Formats: txt pdf Obsoleted by: RFC 1255, RFC 1417 Status: INFORMATIONAL This RFC is a near-verbatim copy of a document, known as NADF-123, which has been produced by the North American Directory Forum (NADF). As a part of its charter, the NADF must reach agreement as to how entries are named in the public portions of the North American Directory. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1219	On the assignment of subnet numbers
	Authors: P.F. Tsuchiya. Date: April 1991 Formats: txt pdf Status: INFORMATIONAL This memo suggests a new procedure for assigning subnet numbers. Use of this assignment technique within a network would be a purely local matter, and would not effect other networks. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1220	Point-to-Point Protocol extensions for bridging
	Authors: F. Baker. Date: April 1991 Formats: txt pdf Obsoleted by: RFC 1638 Status: PROPOSED STANDARD This document defines an extension of the Internet Point-to-Point Protocol (PPP) described in RFC 1171, targeting the use of Point-to- Point lines for Remote Bridging. [STANDARDS-TRACK]
RFC 1221	Host Access Protocol (HAP) specification: Version 2
	Authors: W. Edmond. Date: April 1991 Formats: txt pdf Updates: RFC 0907 Status: INFORMATIONAL This memo describes the Host Access Protocol implemented in the Terrestrial Wideband Network (TWBNET). This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1222	Advancing the NSFNET routing architecture
	Authors: H.W. Braun, Y. Rekhter. Date: May 1991 Formats: txt pdf Status: INFORMATIONAL This RFC suggests improvements in the NSFNET routing architecture to accommodate a more flexible interface to the Backbone clients. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1223	OSI CLNS and LLC1 protocols on Network Systems HYPERchannel
	Authors: J.M. Halpern. Date: May 1991 Formats: txt pdf Status: INFORMATIONAL The intent of this document is to provide a complete discussion of the protocols and techniques used to transmit OSI CLNS and LLC1 datagrams (and any associated higher level protocols) on Network Systems Corporation's HYPERchannel equipment.This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1224	Techniques for managing asynchronously generated alerts
	Authors: L. Steinberg. Date: May 1991 Formats: txt pdf Status: EXPERIMENTAL This RFC explores mechanisms to prevent a remotely managed entity from burdening a manager or network with an unexpected amount of network management information, and to ensure delivery of "important" information. The focus is on controlling the flow of asynchronously generated information, and not how the information is generated.
RFC 1225	Post Office Protocol: Version 3
	Authors: M.T. Rose. Date: May 1991 Formats: txt pdf Obsoletes: RFC 1081 Obsoleted by: RFC 1460 Status: DRAFT STANDARD This memo suggests a simple method for workstations to dynamically access mail from a mailbox server. [STANDARDS-TRACK]
RFC 1226	Internet protocol encapsulation of AX.25 frames
	Authors: B. Kantor. Date: May 1991 Formats: txt pdf Status: EXPERIMENTAL This memo describes a method for the encapsulation of AX.25 (the Amateur Packet-Radio Link-Layer Protocol) frames within IP packets. This technique is an Experimental Protocol for the Internet community. It does not specify an Internet standard.
RFC 1227	SNMP MUX protocol and MIB
	Authors: M.T. Rose. Date: May 1991 Formats: txt pdf Status: HISTORIC This memo suggests a mechanism by which a user process may associate itself with the local SNMP agent on a host, in order to implement portions of the MIB. This mechanism would be local to the host.This is an Experimental Protocol for the Internet community. It does not specify an Internet standard.
RFC 1228	SNMP-DPI: Simple Network Management Protocol Distributed Program Interface
	Authors: G. Carpenter, B. Wijnen. Date: May 1991 Formats: txt pdf Obsoleted by: RFC 1592 Status: EXPERIMENTAL This RFC describes a protocol that International Business Machines Corporation (IBM) has been implementing in most of its SNMP agents to allow dynamic extension of supported MIBs. This is an Experimental Protocol for the Internet community. It does not specify an Internet standard.
RFC 1229	Extensions to the generic-interface MIB
	Authors: K. McCloghrie. Date: May 1991 Formats: txt pdf Obsoleted by: RFC 1573 Updated by: RFC 1239 Status: PROPOSED STANDARD This RFC contains definitions of managed objects used as experimental extensions to the generic interfaces structure of MIB-II. [STANDARDS- TRACK]
RFC 1230	IEEE 802.4 Token Bus MIB
	Authors: K. McCloghrie, R. Fox. Date: May 1991 Formats: txt pdf Updated by: RFC 1239 Status: HISTORIC This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, this memo defines managed objects used for managing subnetworks which use the IEEE 802.4 Token Bus technology described in 802.4 Token-Passing Bus Access Method and Physical Layer Specifications, IEEE Standard 802.4. [STANDARDS-TRACK]
RFC 1231	IEEE 802.5 Token Ring MIB
	Authors: K. McCloghrie, R. Fox, E. Decker. Date: May 1991 Formats: txt pdf Obsoleted by: RFC 1743, RFC 1748 Updated by: RFC 1239 Status: PROPOSED STANDARD This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, this memo defines managed objects used for managing subnetworks which use the IEEE 802.5 Token Ring technology described in 802.5 Token Ring Access Method and Physical Layer Specifications, IEEE Standard 802.5-1989. [STANDARDS-TRACK]
RFC 1232	Definitions of managed objects for the DS1 Interface type
	Authors: F. Baker, C.P. Kolb. Date: May 1991 Formats: txt pdf Obsoleted by: RFC 1406 Updated by: RFC 1239 Status: PROPOSED STANDARD
RFC 1233	Definitions of managed objects for the DS3 Interface type
	Authors: T.A. Cox, K. Tesink. Date: May 1991 Formats: txt pdf Obsoleted by: RFC 1407 Updated by: RFC 1239 Status: PROPOSED STANDARD This memo defines objects for managing DS3 Interface objects for use with the SNMP protocol. [STANDARDS-TRACK]
RFC 1234	Tunneling IPX traffic through IP networks
	Authors: D. Provan. Date: June 1991 Formats: txt pdf Status: HISTORIC This memo describes a method of encapsulating IPX datagrams within UDP packets so that IPX traffic can travel across an IP internet. [STANDARDS-TRACK] This memo defines objects for managing DS1 Interface objects for use with the SNMP protocol. [STANDARDS-TRACK]
RFC 1235	Coherent File Distribution Protocol
	Authors: J. Ioannidis, G. Maguire. Date: June 1991 Formats: txt pdf Status: EXPERIMENTAL This memo describes the Coherent File Distribution Protocol (CFDP). This is an Experimental Protocol for the Internet community. It does not specify an Internet standard.
RFC 1236	IP to X.121 address mapping for DDN
	Authors: L. Morales, P. Hasse. Date: June 1991 Formats: txt pdf Status: INFORMATIONAL This memo defines a standard way of converting IP addresses to CCITT X.121 addresses and is the recommended standard for use on the Internet, specifically for the Defense Data Network (DDN). This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1237	Guidelines for OSI NSAP Allocation in the Internet
	Authors: R. Colella, E. Gardner, R. Callon. Date: July 1991 Formats: txt pdf ps Obsoleted by: RFC 1629 Status: PROPOSED STANDARD This paper provides guidelines for allocating NSAPs in the Internet.[STANDARDS-TRACK]
RFC 1238	CLNS MIB for use with Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542)
	Authors: G. Satz. Date: June 1991 Formats: txt pdf Obsoletes: RFC 1162 Status: EXPERIMENTAL This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. This is an Experimental Protocol for the Internet community. It does not specify an Internet standard.
RFC 1239	Reassignment of experimental MIBs to standard MIBs
	Authors: J.K. Reynolds. Date: June 1991 Formats: txt pdf Updates: RFC 1229, RFC 1230, RFC 1231, RFC 1232, RFC 1233 Status: HISTORIC This memo specifically updates RFC 1229, RFC 1230, RFC 1231, RFC 1232 and RFC 1233 with new codes. [STANDARDS-TRACK]
RFC 1240	OSI connectionless transport services on top of UDP: Version 1
	Authors: C. Shue, W. Haggerty, K. Dobbins. Date: June 1991 Formats: txt pdf Status: HISTORIC This document describes a protocol for running OSI Connectionless service on UDP. [STANDARDS-TRACK]
RFC 1241	Scheme for an internet encapsulation protocol: Version 1
	Authors: R.A. Woodburn, D.L. Mills. Date: July 1991 Formats: txt pdf ps Status: EXPERIMENTAL This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.
RFC 1242	Benchmarking Terminology for Network Interconnection Devices
	Authors: S. Bradner. Date: July 1991 Formats: txt pdf Updated by: RFC 6201 Status: INFORMATIONAL This memo discusses and defines a number of terms that are used in describing performance benchmarking tests and the results of such tests. The terms defined in this memo will be used in additional memos to define specific benchmarking tests and the suggested format to be used in reporting the results of each of the tests. This memo is a product of the Benchmarking Methodology Working Group (BMWG) of the Internet Engineering Task Force (IETF).
RFC 1243	AppleTalk Management Information Base
	Authors: S. Waldbusser. Date: July 1991 Formats: txt pdf Obsoleted by: RFC 1742 Status: PROPOSED STANDARD This memo defines objects for managing AppleTalk objects for use with the SNMP protocol. [STANDARDS-TRACK]
RFC 1244	Site Security Handbook
	Authors: J.P. Holbrook, J.K. Reynolds. Date: July 1991 Formats: txt pdf Obsoleted by: RFC 2196 Status: INFORMATIONAL This FYI RFC is a first attempt at providing Internet users guidance on how to deal with security issues in the Internet. This FYI RFC provides information for the Internet community. It does not specify an Internet standard. [FYI 8]
RFC 1245	OSPF Protocol Analysis
	Authors: J. Moy. Date: July 1991 Formats: txt pdf ps Also: RFC 1247, RFC 1246 Status: INFORMATIONAL This report attempts to summarize the key features of OSPF V2. It also attempts to analyze how the protocol will perform and scale in the Internet. This memo provides information for the Internet community. It does not specify any Internet standard.
RFC 1246	Experience with the OSPF Protocol
	Authors: J. Moy. Date: July 1991 Formats: txt pdf ps Also: RFC 1247, RFC 1245 Status: INFORMATIONAL This report documents experience with OSPF V2. This includes reports on interoperability testing, field experience, simulations and the current state of OSPF implementations. This memo provides information for the Internet community. It does not specify any Internet standard.
RFC 1247	OSPF Version 2
	Authors: J. Moy. Date: July 1991 Formats: txt pdf ps Obsoletes: RFC 1131 Obsoleted by: RFC 1583 Updated by: RFC 1349 Also: RFC 1246, RFC 1245 Status: DRAFT STANDARD This memo documents version 2 of the OSPF protocol. OSPF is a link- state based routing protocol. [STANDARDS-TRACK]
RFC 1248	OSPF Version 2 Management Information Base
	Authors: F. Baker, R. Coltun. Date: July 1991 Formats: txt pdf Obsoleted by: RFC 1252 Updated by: RFC 1349 Status: PROPOSED STANDARD This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS-TRACK]
RFC 1249	DIXIE Protocol Specification
	Authors: T. Howes, M. Smith, B. Beecher. Date: August 1991 Formats: txt pdf Also: RFC 1202 Status: INFORMATIONAL This RFC defines a mechanism by which TCP/UDP based clients can access OSI Directory Service without the overhead of the ISO transport and presentation protocols required to implement full-blown DAP. This memo provides information for the Internet community. It does not specify any standard.
RFC 1250	IAB Official Protocol Standards
	Authors: J. Postel. Date: August 1991 Formats: txt pdf Obsoletes: RFC 1200 Obsoleted by: RFC 2200, RFC 1280 Status: HISTORIC This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1251	Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members
	Authors: G. Malkin. Date: August 1991 Formats: txt pdf Obsoleted by: RFC 1336 Status: INFORMATIONAL This FYI RFC contains biographical information about members of the Internet Activities Board (IAB), the Internet Engineering Steering Group (IESG) of the Internet Engineering Task Force (IETF), and the the Internet Research Steering Group (IRSG) of the Internet Research Task Force (IRTF). This memo provides information for the Internet community. It does not specify an Internet standard. [FYI 9]
RFC 1252	OSPF Version 2 Management Information Base
	Authors: F. Baker, R. Coltun. Date: August 1991 Formats: txt pdf Obsoletes: RFC 1248 Obsoleted by: RFC 1253 Also: RFC 1247, RFC 1245 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS- TRACK]
RFC 1253	OSPF Version 2 Management Information Base
	Authors: F. Baker, R. Coltun. Date: August 1991 Formats: txt pdf Obsoletes: RFC 1252 Obsoleted by: RFC 1850 Also: RFC 1247, RFC 1245, RFC 1246 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS- TRACK]
RFC 1254	Gateway Congestion Control Survey
	Authors: A. Mankin, K. Ramakrishnan. Date: August 1991 Formats: txt pdf Status: INFORMATIONAL The growth of network intensive Internet applications has made gateway congestion control a high priority. The IETF Performance andCongestion Control Working Group surveyed and reviewed gateway congestion control and avoidance approaches. The purpose of this paper is to present our review of the congestion control approaches, as a way of encouraging new discussion and experimentation. Included in the survey are Source Quench, Random Drop, Congestion Indication(DEC Bit), and Fair Queueing. The task remains for Internet implementors to determine and agree on the most effective mechanisms for controlling gateway congestion.
RFC 1255	A Naming Scheme for c=US
	Authors: The North American Directory Forum. Date: September 1991 Formats: txt pdf Obsoletes: RFC 1218 Obsoleted by: RFC 1417 Status: INFORMATIONAL This memo documents the NADF's agreement as to how entries are named in the public portions of the North American Directory. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1256	ICMP Router Discovery Messages
	Authors: S. Deering, Ed.. Date: September 1991 Formats: txt pdf Also: RFC 0792 Status: PROPOSED STANDARD This document specifies an extension of the Internet Control MessageProtocol (ICMP) to enable hosts attached to multicast or broadcast networks to discover the IP addresses of their neighboring routers.
RFC 1257	Isochronous applications do not require jitter-controlled networks
	Authors: C. Partridge. Date: September 1991 Formats: txt pdf Status: INFORMATIONAL This memo argues that jitter control is not required for networks to support isochronous applications. A network providing bandwidth and bounds delay is sufficient. The implications for gigabit internetworking protocols are briefly considered.
RFC 1258	BSD Rlogin
	Authors: B. Kantor. Date: September 1991 Formats: txt pdf Obsoleted by: RFC 1282 Status: INFORMATIONAL The rlogin facility provides a remote-echoed, locally flow-controlled virtual terminal with proper flushing of output.This memo documents an existing protocol and common implementation that is extensively used on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1259	Building the open road: The NREN as test-bed for the national public network
	Authors: M. Kapor. Date: September 1991 Formats: txt pdf Status: INFORMATIONAL This memo discusses the background and importance of NREN. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1261	Transition of Nic Services
	Authors: S. Williamson, L. Nobile. Date: September 1991 Formats: txt pdf Status: INFORMATIONAL This memo outlines the transition of NIC Services. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1262	Guidelines for Internet Measurement Activities
	Authors: V.G. Cerf. Date: October 1991 Formats: txt pdf Status: INFORMATIONAL This RFC represents IAB guidance for researchers considering measurement experiments on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1263	TCP Extensions Considered Harmful
	Authors: S. O'Malley, L.L. Peterson. Date: October 1991 Formats: txt pdf Status: INFORMATIONAL This RFC comments on recent proposals to extend TCP. It argues that the backward compatible extensions proposed in RFC's 1072 and 1185 should not be pursued, and proposes an alternative way to evolve theInternet protocol suite. Its purpose is to stimulate discussion in the Internet community.
RFC 1264	Internet Engineering Task Force Internet Routing Protocol Standardization Criteria
	Authors: R.M. Hinden. Date: October 1991 Formats: txt pdf Obsoleted by: RFC 4794 Status: HISTORIC This informational RFC presents procedures for creating and documenting Internet standards on routing protocols. These procedures have been established by the Internet Activities Board (IAB) in consultation with the Internet Engineering Steering Group (IESG). This memo provides information for the Internet community. It does not specifiy an Internet standard.
RFC 1265	BGP Protocol Analysis
	Authors: Y. Rekhter. Date: October 1991 Formats: txt pdf Status: INFORMATIONAL This report summarizes the key feature of BGP, and analyzes the protocol with respect to scaling and performance. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1266	Experience with the BGP Protocol
	Authors: Y. Rekhter. Date: October 1991 Formats: txt pdf Status: INFORMATIONAL The purpose of this memo is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by Border Gateway Protocol (BGP). This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1267	Border Gateway Protocol 3 (BGP-3)
	Authors: K. Lougheed, Y. Rekhter. Date: October 1991 Formats: txt pdf Obsoletes: RFC 1163 Status: HISTORIC This memo, together with its companion document, "Application of the Border Gateway Protocol in the Internet", define an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK]
RFC 1268	Application of the Border Gateway Protocol in the Internet
	Authors: Y. Rekhter, P. Gross. Date: October 1991 Formats: txt pdf Obsoletes: RFC 1164 Obsoleted by: RFC 1655 Status: HISTORIC This document, together with its companion document, "A BorderGateway Protocol (BGP-3)", define an inter-autonomous system routing protocol for the Internet. "A Border Gateway Protocol (BGP-3)" defines the BGP protocol specification, and this document describes the usage of the BGP in the Internet. Information about the progress of BGP can be monitored and/or reported on the BGP mailing list (iwg@rice.edu).
RFC 1269	Definitions of Managed Objects for the Border Gateway Protocol: Version 3
	Authors: S. Willis, J.W. Burruss. Date: October 1991 Formats: txt pdf Obsoleted by: RFC 4273 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Border Gateway Protocol. [STANDARDS-TRACK]
RFC 1270	SNMP Communications Services
	Authors: F. Kastenholz. Date: October 1991 Formats: txt pdf Status: INFORMATIONAL This document discusses various issues to be considered when determining the underlying communications services to be used by an SNMP implementation. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1271	Remote Network Monitoring Management Information Base
	Authors: S. Waldbusser. Date: November 1991 Formats: txt pdf Obsoleted by: RFC 1757 Updated by: RFC 1513 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices. [STANDARDS-TRACK]
RFC 1272	Internet Accounting: Background
	Authors: C. Mills, D. Hirsh, G.R. Ruth. Date: November 1991 Formats: txt pdf Status: INFORMATIONAL This document provides background information for the "Internet Accounting Architecture". This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1273	Measurement Study of Changes in Service-Level Reachability in the Global TCP/IP Internet: Goals, Experimental Design, Implementation, and Policy Considerations
	Authors: M.F. Schwartz. Date: November 1991 Formats: txt pdf Status: INFORMATIONAL In this report we discuss plans to carry out a longitudinal measurement study of changes in service-level reachability in the global TCP/IP Internet. We overview our experimental design, considerations of network and remote site load, mechanisms used to control the measurement collection process, and network appropriate use and privacy issues, including our efforts to inform sites measured by this study. A list of references and information on how to contact the Principal Investigator are included.
RFC 1274	The COSINE and Internet X.500 Schema
	Authors: P. Barker, S. Kille. Date: November 1991 Formats: txt pdf Obsoleted by: RFC 4524 Status: PROPOSED STANDARD This document suggests an X.500 Directory Schema, or NamingArchitecture, for use in the COSINE and Internet X.500 pilots. The schema is independent of any specific implementation. As well as indicating support for the standard object classes and attributes, a large number of generally useful object classes and attributes are also defined. An appendix to this document includes a machine processable version of the schema. This document also proposes a mechanism for allowing the schema to evolve in line with emerging requirements. Proformas to support this process are included. Corrections and additions to the schema should be sent to na- update@cs.ucl.ac.uk list, as described within.
RFC 1275	Replication Requirements to provide an Internet Directory using X.500
	Authors: S.E. Hardcastle-Kille. Date: November 1991 Formats: txt pdf ps Status: INFORMATIONAL This RFCconsiders certain deficiencies of the 1988 X.500 standard, which need to be addressed before an effective openInternet Directory can be established using these protocols and services [CCI88]. The only areas considered are primary problems, to which solutions must be found before a pilot can be deployed. This RFCconcerns itself with deficiencies which can only be addressed by use of additional protocol or procedures for distributed operation.
RFC 1276	Replication and Distributed Operations extensions to provide an Internet Directory using X.500
	Authors: S.E. Hardcastle-Kille. Date: November 1991 Formats: txt ps pdf Status: HISTORIC Some requirements on extensions to X.500 are described in theRFC[HK91b], in order to build an Internet Directory usingX.500(1988). This document specifies a set of solutions to the problems raised. These solutions are based on some work done for the QUIPU implementation, and demonstrated to be effective in a number of directory pilots. By documenting a de facto standard, rapid progress can be made towards a full-scale pilot. These procedures are an INTERIM approach. There are known deficiencies, both in terms of manageability and scalability.Transition to standard approaches are planned when appropriate standards are available. This RFCwill be obsoleted at this point.
RFC 1277	Encoding Network Addresses to Support Operation over Non-OSI Lower Layers
	Authors: S.E. Hardcastle-Kille. Date: November 1991 Formats: txt ps pdf Status: PROPOSED STANDARD The OSI Directory specifies an encoding of Presentation Address, which utilises OSI Network Addresses as defined in the OSINetwork Layer standards [CCI88] [ISO87a]. The OSI Directory, and any OSI application utilising the OSI Directory must be able use these Network Addresses to identify end systems. Currently, OSI applications are often run over lower layers other than the OSINetwork Service. It is neither reasonable nor desirable for groups wishing to investigate and use OSI Applications in conjunction with the OSI Directory to be dependent on a globalOSI Network Service. This document defines a new network address format, and rules for using some existing network address formats. The scope of this document is:
RFC 1278	A string encoding of Presentation Address
	Authors: S.E. Hardcastle-Kille. Date: November 1991 Formats: txt ps pdf Status: INFORMATIONAL There are a number of environments where a simple string encoding of Presentation Address is desirable. This specification defines such a representation.
RFC 1279	X.500 and Domains
	Authors: S.E. Hardcastle-Kille. Date: November 1991 Formats: txt pdf ps Status: EXPERIMENTAL This RFCconsiders X.500 in relation to Internet and UK Domains.A basic model of X.500 providing a higher level and more descriptive naming structure is emphasised. In addition, a mapping of domains onto X.500 is proposed, which gives a range of new management and user facilities over and above those currently available. This specification proposes an experimental new mechanism to access and manage domain information on the Internet and in the UK Academic Community. There is no current intention to provide an operational replacement for DNS.
RFC 1280	IAB Official Protocol Standards
	Authors: J. Postel. Date: March 1992 Formats: txt pdf Obsoletes: RFC 1250 Obsoleted by: RFC 1360 Status: HISTORIC This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1281	Guidelines for the Secure Operation of the Internet
	Authors: R. Pethia, S. Crocker, B. Fraser. Date: November 1991 Formats: txt pdf Status: INFORMATIONAL The purpose of this document is to provide a set of guidelines to aid in the secure operation of the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1282	BSD Rlogin
	Authors: B. Kantor. Date: December 1991 Formats: txt pdf Obsoletes: RFC 1258 Status: INFORMATIONAL This memo documents an existing protocol and common implementation that is extensively used on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1283	SNMP over OSI
	Authors: M. Rose. Date: December 1991 Formats: txt pdf Obsoleted by: RFC 1418 Status: EXPERIMENTAL This memo describes mappings from the SNMP onto both the COTS and the CLTS. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet Standard.
RFC 1284	Definitions of Managed Objects for the Ethernet-like Interface Types
	Authors: J. Cook, Ed.. Date: December 1991 Formats: txt pdf Obsoleted by: RFC 1398 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing ethernet-like objects. [STANDARDS-TRACK]
RFC 1285	FDDI Management Information Base
	Authors: J. Case. Date: January 1992 Formats: txt pdf Updated by: RFC 1512 Status: HISTORIC This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing devices which implement the FDDI. [STANDARDS-TRACK]
RFC 1286	Definitions of Managed Objects for Bridges
	Authors: E. Decker, P. Langille, A. Rijsinghani, K. McCloghrie. Date: December 1991 Formats: txt pdf Obsoleted by: RFC 1493, RFC 1525 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for managing bridges based on the IEEE 802.1d draft standard between Local Area Network (LAN) segments. This memo is an extension to the SNMP MIB. [STANDARDS-TRACK]
RFC 1287	Towards the Future Internet Architecture
	Authors: D. Clark, L. Chapin, V. Cerf, R. Braden, R. Hobby. Date: December 1991 Formats: txt pdf Status: INFORMATIONAL This informational RFC discusses important directions for possible future evolution of the Internet architecture, and suggests steps towards the desired goals. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1288	The Finger User Information Protocol
	Authors: D. Zimmerman. Date: December 1991 Formats: txt pdf Obsoletes: RFC 1196, RFC 1194, RFC 0742 Status: DRAFT STANDARD This memo describes the Finger user information protocol. This is a simple protocol which provides an interface to a remote user information program. Based on RFC 742, a description of the original Finger protocol, this memo attempts to clarify the expected communication between the two ends of a Finger connection. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition. This edition corrects and clarifies RFC 1196.
RFC 1289	DECnet Phase IV MIB Extensions
	Authors: J. Saperia. Date: December 1991 Formats: txt pdf Obsoleted by: RFC 1559 Status: PROPOSED STANDARD This memo defines a set of DECnet Phase IV extensions that have been created for the Internet MIB. When used in conjunction with the structure of management information (RFC 1155), the management information base for network management of TCP/IP-based internets(RFC 1213) and the Simple Network Management Protocol (RFC 1157), it will be possible to provide integrated network management of combinedTCP/IP and DECnet Phase IV based internets. This document was produced by the DECnet Phase IV MIB working group of the InternetEngineering Task Force (IETF).
RFC 1290	There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places
	Authors: J. Martin. Date: December 1991 Formats: txt pdf Obsoleted by: RFC 1402 Status: INFORMATIONAL This document was presented at the 1991 ACM SIGUCCS User ServicesConference. It appears here in its updated form. There is a wealth of information on the network. In fact, so much information, that you could spend your entire life browsing. This paper will present some of the "gold nuggets" of information and file repositories on the network that could be of use to end users. The ultimate goal is to make the route to these sources of information invisible to the user. At present, this is not easy to do. I will explain some of the techniques that can be used to make these nuggets easier to pick up so that we can all be richer.
RFC 1291	Mid-Level Networks Potential Technical Services
	Authors: V. Aggarwal. Date: December 1991 Formats: txt ps pdf Status: INFORMATIONAL This document proposes a set of technical services that each Internet mid-level network can offer within the mid-level network itself and and to its peer networks. The term "mid-level" is used as a generic term to represent all regional and similar networks, which, due to continuous evolutions and transitions, can no longer be termed"regional" [MAN]. It discusses the pros and cons of offering these services, as well as areas in which mid-level networks can work together. A large portion of the ideas stem from discussions at the IETFOperational Statistics (OPstat), User Connectivity Problems (UCP) andNetwork Joint Management (NJM) working groups.
RFC 1292	A Catalog of Available X.500 Implementations
	Authors: R. Lang, R. Wright. Date: January 1992 Formats: txt pdf Obsoleted by: RFC 1632 Status: INFORMATIONAL The goal of this document is to provide information regarding the availability and capability of implementations of X.500. Comments and critiques of this document, and new or updated descriptions ofX.500 implementations are welcome. Send them to the DirectoryInformation Services Infrastructure (DISI) Working Group(disi@merit.edu) or to the editors.
RFC 1293	Inverse Address Resolution Protocol
	Authors: T. Bradley, C. Brown. Date: January 1992 Formats: txt pdf Obsoleted by: RFC 2390 Status: PROPOSED STANDARD This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK]
RFC 1294	Multiprotocol Interconnect over Frame Relay
	Authors: T. Bradley, C. Brown, A. Malis. Date: January 1992 Formats: txt pdf Obsoleted by: RFC 1490, RFC 2427 Status: PROPOSED STANDARD This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. [STANDARDS-TRACK]
RFC 1295	User Bill of Rights for entries and listings in the Public Directory
	Authors: The North American Directory Forum. Date: January 1992 Formats: txt pdf Obsoleted by: RFC 1417 Status: INFORMATIONAL This RFC is a near-verbatim copy of a document, known as NADF-265, which has been produced by the North American Directory Forum (NADF). User Bill of Rights for entries and listings in the Public Directory The mission of the North American Directory Forum is to provide interconnected electronic directories which empower users with unprecedented access to public information. To address significant security and privacy issues, the North American Directory Forum introduces the following "User Bill of Rights" for entries in thePublic Directory. As a user, you have: I. The right not to be listed. II. The right to have you or your agent informed when your entry is created. III. The right to examine your entry. IV. The right to correct inaccurate information in your entry. V. The right to remove specific information from your entry. VI. The right to be assured that your listing in thePublic Directory will comply with US or Canadian law regulating privacy or access information. VII. The right to expect timely fulfillment of these rights.
RFC 1296	Internet Growth (1981-1991)
	Authors: M. Lottor. Date: January 1992 Formats: txt pdf Status: INFORMATIONAL This document illustrates the growth of the Internet by examination of entries in the Domain Name System (DNS) and pre-DNS host tables.DNS entries are collected by a program called ZONE, which searches the Internet and retrieves data from all known domains. Pre-DNS host table data were retrieved from system archive tapes. Various statistics are presented on the number of hosts and domains.
RFC 1297	NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist ("NOC TT REQUIREMENTS")
	Authors: D. Johnson. Date: January 1992 Formats: txt pdf Status: INFORMATIONAL Professional quality handling of network problems requires some kind of problem tracking system, herein referred to as a "trouble ticket" system. A basic trouble ticket system acts like a hospital chart, coordinating the work of multiple people who may need to work on the problem. Once the basic trouble ticket system is in place, however, there are many extensions that can aid Network Operations efficiency.Information in the tickets can be used to produce statistical reports. Operator efficiency and accuracy may be increased by automating trouble ticket entry with information from the networkAlert system. The Alert system may be used to monitor trouble ticket progress. Trouble tickets may be also used to communicate network health information between NOCs, to telcom vendors, and to other internal sales and engineering audiences. This document explores competing uses, architectures, and desirable features of integrated internal trouble ticket systems for Network and other Operations Centers.
RFC 1298	SNMP over IPX
	Authors: R. Wormley, S. Bostock. Date: February 1992 Formats: txt pdf Obsoleted by: RFC 1420 Status: INFORMATIONAL This memo defines a convention for encapsulating Simple NetworkManagement Protocol (SNMP) [1] packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol [2].
RFC 1299	Summary of 1200-1299
	Authors: M. Kennedy. Date: January 1997 Formats: txt pdf Status: INFORMATIONAL
RFC 1300	Remembrances of Things Past
	Authors: S. Greenfield. Date: February 1992 Formats: txt pdf Status: INFORMATIONAL Poem. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1301	Multicast Transport Protocol
	Authors: S. Armstrong, A. Freier, K. Marzullo. Date: February 1992 Formats: txt pdf Status: INFORMATIONAL This memo describes a protocol for reliable transport that utilizes the multicast capability of applicable lower layer networking architectures. The transport definition permits an arbitrary number of transport providers to perform realtime collaborations without requiring networking clients (aka, applications) to possess detailed knowledge of the population or geographical dispersion of the participating members. It is not network architectural specific, but does implicitly require some form of multicasting (or broadcasting) at the data link level, as well as some means of communicating that capability up through the layers to the transport. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1302	Building a Network Information Services Infrastructure
	Authors: D. Sitzler, P. Smith, A. Marine. Date: February 1992 Formats: txt pdf Also: FYI 0012 Status: INFORMATIONAL This FYI RFC document is intended for existing Internet NetworkInformation Center (NIC) personnel, people interested in establishing a new NIC, Internet Network Operations Centers (NOCs), and funding agencies interested in contributing to user support facilities. The document strives to: - Define a basic set of essential services that NetworkInformation Centers (NICs) will provide to Internet users, including new mechanisms that will facilitate the timely dissemination of information to the Internet community and encourage cooperation among NICs. - Describe existing NIC services as an aid to Internet users and as a model for organizations establishing new NICs.
RFC 1303	A Convention for Describing SNMP-based Agents
	Authors: K. McCloghrie, M. Rose. Date: February 1992 Formats: txt pdf Also: RFC 1155, RFC 1212, RFC 1213, RFC 1157 Status: INFORMATIONAL This memo suggests a straight-forward approach towards describingSNMP-based agents.
RFC 1304	Definitions of Managed Objects for the SIP Interface Type
	Authors: T. Cox, K. Tesink, Eds.. Date: February 1992 Formats: txt pdf Obsoleted by: RFC 1694 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing SIP (SMDS InterfaceProtocol) objects.
RFC 1305	Network Time Protocol (Version 3) Specification, Implementation and Analysis
	Authors: D. Mills. Date: March 1992 Formats: txt pdf tar Obsoletes: RFC 0958, RFC 1059, RFC 1119 Obsoleted by: RFC 5905 Status: DRAFT STANDARD This document describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. [STANDARDS-TRACK]
RFC 1306	Experiences Supporting By-Request Circuit-Switched T3 Networks
	Authors: A. Nicholson, J. Young. Date: March 1992 Formats: txt pdf Status: INFORMATIONAL This memo describes the experiences of a project team at CrayResearch, Inc., in implementing support for circuit-switched T3 services. While the issues discussed may not be directly relevant to the research problems of the Internet, they may be interesting to a number of researchers and implementers. Developers at Cray Research, Inc. were presented with an opportunity to use a circuit-switched T3 network for wide area networking. They devised an architectural model for using this new resource. This involves activating the circuit-switched connection when an application program engages in a bulk data transfer, and releasing the connection when the transfer is complete. Three software implementations for this feature have been tested, and the results documented here. A variety of issues are involved, and further research is necessary. Network users are beginning to recognize the value of this service, and are planning to make use of by-request circuit-switched networks. A standard method of access will be needed to ensure interoperability among vendors of circuit- switched network support products.
RFC 1307	Dynamically Switched Link Control Protocol
	Authors: J. Young, A. Nicholson. Date: March 1992 Formats: txt pdf Status: EXPERIMENTAL This memo describes an experimental protocol developed by a project team at Cray Research, Inc., in implementing support for circuit- switched T3 services. The protocol is used for the control of network connections external to a host, but known to the host. It is documented here for the benefit of others who may wish to perform further research. While working with circuit-switched T3 networks, developers at CrayResearch, Inc., defined a model wherein a host would generate control messages for a network switch. This work is described in RFC 1306,"Experiences Supporting By-Request Circuit-Switched T3 Networks". In order to simplify the model it was decided that the inconsistencies of switch control should be hidden from the host generating the control messages. To that end, a protocol was defined and implemented. This RFC documents the Dynamically Switched LinkControl Protocol (DSLCP), which is used for creation and control of downstream network links by a host.
RFC 1308	Executive Introduction to Directory Services Using the X.500 Protocol
	Authors: C. Weider, J. Reynolds. Date: March 1992 Formats: txt pdf Also: FYI 0013 Status: INFORMATIONAL This document is an Executive Introduction to Directory Services using the X.500 protocol. It briefly discusses the deficiencies in currently deployed Internet Directory Services, and then illustrates the solutions provided by X.500. This FYI RFC is a product of the Directory Information Services(pilot) Infrastructure Working Group (DISI). A combined effort of the User Services and the OSI Integration Areas of the InternetEngineering Task Force (IETF).
RFC 1309	Technical Overview of Directory Services Using the X.500 Protocol
	Authors: C. Weider, J. Reynolds, S. Heker. Date: March 1992 Formats: txt pdf Also: FYI 0014 Status: INFORMATIONAL This document is an overview of the X.500 standard for people not familiar with the technology. It compares and contrasts DirectoryServices based on X.500 with several of the other Directory services currently in use in the Internet. This paper also describes the status of the standard and provides references for further information on X.500 implementations and technical information. A primary purpose of this paper is to illustrate the vast functionality of the X.500 protocol and to show how it can be used to provide a global directory for human use, and can support other applications which would benefit from directory services, such as main programs. This FYI RFC is a product of the Directory Information Services(pilot) Infrastructure Working Group (DISI). A combined effort of the User Services and the OSI Integration Areas of the InternetEngineering Task Force (IETF).
RFC 1310	The Internet Standards Process
	Authors: L. Chapin. Date: March 1992 Formats: txt pdf Obsoleted by: RFC 1602 Status: INFORMATIONAL This memo documents the process currently used for the standardization of Internet protocols and procedures. [STANDARDS-TRACK]
RFC 1311	Introduction to the STD Notes
	Authors: J. Postel. Date: March 1992 Formats: txt pdf Status: INFORMATIONAL The STDs are a subseries of notes within the RFC series that are the Internet standards. The intent is to identify clearly for the Internet community those RFCs which document Internet standards. [STANDARDS- TRACK]
RFC 1312	Message Send Protocol 2
	Authors: R. Nelson, G. Arnold. Date: April 1992 Formats: txt pdf Obsoletes: RFC 1159 Status: EXPERIMENTAL The Message Send Protocol is used to send a short message to a given user on a given terminal on a given host. This memo defines an Experimental Protocol for the Internet community.
RFC 1313	Today's Programming for KRFC AM 1313 Internet Talk Radio
	Authors: C. Partridge. Date: April 1 1992 Formats: txt pdf Status: INFORMATIONAL Hi and welcome to KRFC Internet Talk Radio, your place on the AM dial for lively talk and just-breaking news on internetworking. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1314	A File Format for the Exchange of Images in the Internet
	Authors: A. Katz, D. Cohen. Date: April 1992 Formats: txt pdf Status: HISTORIC This document defines a standard file format for the exchange of fax-like black and white images within the Internet. It is a product of the Network Fax Working Group of the Internet Engineering TaskForce (IETF). The standard is: ** The file format should be TIFF-B with multi-page files supported. Images should be encoded as one TIFF strip per page. ** Images should be compressed using MMR when possible. Images may also be MH or MR compressed or uncompressed. If MH or MR compression is used, scan lines should be "byte-aligned". ** For maximum interoperability, image resolutions should either be 600, 400, or 300 dpi; or else be one of the standard Group 3 fax resolutions (98 or 196 dpi vertically and 204 dpi horizontally). Note that this specification is self contained and an implementation should be possible without recourse to the TIFF references, and that only the specific TIFF documents cited are relevant to this specification. Updates to the TIFF documents do not change this specification. Experimentation with this file format specified here is encouraged.
RFC 1315	Management Information Base for Frame Relay DTEs
	Authors: C. Brown, F. Baker, C. Carvalho. Date: April 1992 Formats: txt pdf Obsoleted by: RFC 2115 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing Frame Relay.
RFC 1316	Definitions of Managed Objects for Character Stream Devices
	Authors: B. Stewart. Date: April 1992 Formats: txt pdf Obsoleted by: RFC 1658 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for the management of character stream devices. [STANDARDS-TRACK]
RFC 1317	Definitions of Managed Objects for RS-232-like Hardware Devices
	Authors: B. Stewart. Date: April 1992 Formats: txt pdf Obsoleted by: RFC 1659 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for the management of RS-232-like devices. [STANDARDS-TRACK]
RFC 1318	Definitions of Managed Objects for Parallel-printer-like Hardware Devices
	Authors: B. Stewart. Date: April 1992 Formats: txt pdf Obsoleted by: RFC 1660 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for the management of parallel-printer- like devices. [STANDARDS-TRACK]
RFC 1319	The MD2 Message-Digest Algorithm
	Authors: B. Kaliski. Date: April 1992 Formats: txt pdf Obsoleted by: RFC 6149 Status: HISTORIC This document describes the MD2 message-digest algorithm. The algorithm takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1320	The MD4 Message-Digest Algorithm
	Authors: R. Rivest. Date: April 1992 Formats: txt pdf Obsoletes: RFC 1186 Obsoleted by: RFC 6150 Status: HISTORIC This document describes the MD4 message-digest algorithm [1]. The algorithm takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1321	The MD5 Message-Digest Algorithm
	Authors: R. Rivest. Date: April 1992 Formats: txt pdf Updated by: RFC 6151 Status: INFORMATIONAL This document describes the MD5 message-digest algorithm. The algorithm takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1322	A Unified Approach to Inter-Domain Routing
	Authors: D. Estrin, Y. Rekhter, S. Hotz. Date: May 1992 Formats: txt pdf Status: INFORMATIONAL This memo is an informational RFC which outlines one potential approach for inter-domain routing in future global internets. The focus is on scalability to very large networks and functionality, as well as scalability, to support routing in an environment of heterogeneous services, requirements, and route selection criteria. Note: The work of D. Estrin and S. Hotz was supported by the NationalScience Foundation under contract number NCR-9011279, with matching funds from GTE Laboratories. The work of Y. Rekhter was supported by the Defense Advanced Research Projects Agency, under contractDABT63-91-C-0019. Views and conclusions expressed in this paper are not necessarily those of the Defense Advanced Research ProjectsAgency and National Science Foundation.
RFC 1323	TCP Extensions for High Performance
	Authors: V. Jacobson, R. Braden, D. Borman. Date: May 1992 Formats: txt pdf Obsoletes: RFC 1072, RFC 1185 Status: PROPOSED STANDARD This memo presents a set of TCP extensions to improve performance over large bandwidth*delay product paths and to provide reliable operation over very high-speed paths. It defines new TCP options for scaled windows and timestamps, which are designed to provide compatible interworking with TCP's that do not implement the extensions. The timestamps are used for two distinct mechanisms:RTTM (Round Trip Time Measurement) and PAWS (Protect Against WrappedSequences). Selective acknowledgments are not included in this memo. This memo combines and supersedes RFC-1072 and RFC-1185, adding additional clarification and more detailed specification. Appendix C summarizes the changes from the earlier RFCs.
RFC 1324	A Discussion on Computer Network Conferencing
	Authors: D. Reed. Date: May 1992 Formats: txt pdf Status: INFORMATIONAL This memo is intended to make more people aware of the present developments in the Computer Conferencing field as well as put forward ideas on what should be done to formalize this work so that there is a common standard for programmers and others who are involved in this field to work with. It is also the intention of this memo to stimulate the computer community and generate some useful discussion about the merits of this field.
RFC 1325	FYI on Questions and Answers Answers to Commonly asked "New Internet User" Questions
	Authors: G. Malkin, A. Marine. Date: May 1992 Formats: txt pdf Obsoletes: RFC 1206 Obsoleted by: RFC 1594 Status: INFORMATIONAL This FYI RFC is one of two FYI's called, "Questions and Answers"(Q/A), produced by the User Services Working Group of the InternetEngineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet.
RFC 1326	Mutual Encapsulation Considered Dangerous
	Authors: P. Tsuchiya. Date: May 1992 Formats: txt pdf Status: INFORMATIONAL This memo describes a packet explosion problem that can occur with mutual encapsulation of protocols (A encapsulates B and B encapsulates A).
RFC 1327	Mapping between X.400(1988) / ISO 10021 and RFC 822
	Authors: S. Hardcastle-Kille. Date: May 1992 Formats: txt pdf Obsoletes: RFC 0987, RFC 1026, RFC 1138, RFC 1148 Obsoleted by: RFC 2156 Updates: RFC 0822 Updated by: RFC 1495 Status: PROPOSED STANDARD This document describes a set of mappings which will enable interworking between systems operating the CCITT X.400 1988)Recommendations on Message Handling Systems / ISO IEC 10021 MessageOriented Text Interchange Systems (MOTIS) [CCITT/ISO88a], and systems using the RFC 822 mail protocol [Crocker82a] or protocols derived from RFC 822. The approach aims to maximise the services offered across the boundary, whilst not requiring unduly complex mappings.The mappings should not require any changes to end systems. This document is a revision based on RFCs 987, 1026, 1138, and 1148[Kille86a,Kille87a] which it obsoletes. This document specifies a mapping between two protocols. This specification should be used when this mapping is performed on theDARPA Internet or in the UK Academic Community. This specification may be modified in the light of implementation experience, but no substantial changes are expected.
RFC 1328	X.400 1988 to 1984 downgrading
	Authors: S. Hardcastle-Kille. Date: May 1992 Formats: txt pdf Status: HISTORIC This document considers issues of downgrading from X.400(1988) toX.400(1984) [MHS88a, MHS84]. Annexe B of X.419 specifies some downgrading rules [MHS88b], but these are not sufficient for provision of service in an environment containing both 1984 and 1988 components. This document defines a number of extensions to this annexe. This specification is not tutorial. COSINE Study 8.2 by J.A.I.Craigie gives a useful overview [Cra88].
RFC 1329	Thoughts on Address Resolution for Dual MAC FDDI Networks
	Authors: P. Kuehn. Date: May 1992 Formats: txt pdf Updated by: RFC 5494 Status: INFORMATIONAL In this document an idea is submitted how IP and ARP can be used on inhomogeneous FDDI networks (FDDI networks with single MAC and dual MAC stations) by introducing a new protocol layer in the protocol suite of the dual MAC stations. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1330	Recommendations for the Phase I Deployment of OSI Directory Services (X.500) and OSI Message Handling Services (X.400) within the ESNET Community
	Authors: ESCC X.500/X.400 Task Force, ESnet Site Coordinating Comittee (ESCC), Energy Sciences Network (ESnet). Date: May 1992 Formats: txt pdf Status: INFORMATIONAL This RFC is a near verbatim copy of the whitepaper produced by the ESnet Site Coordinating Committee's X.500/X.400 Task Force. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1331	The Point-to-Point Protocol (PPP) for the Transmission of Multi-protocol Datagrams over Point-to-Point Links
	Authors: W. Simpson. Date: May 1992 Formats: txt pdf Obsoletes: RFC 1171, RFC 1172 Obsoleted by: RFC 1548 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is comprised of three main components: 1. A method for encapsulating datagrams over serial links. 2. A Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection. 3. A family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document defines the PPP encapsulation scheme, together with thePPP Link Control Protocol (LCP), an extensible option negotiation protocol which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. This RFC is a product of the Point-to-Point Protocol Working Group of the Internet Engineering Task Force (IETF). Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu mailing list.
RFC 1332	The PPP Internet Protocol Control Protocol (IPCP)
	Authors: G. McGregor. Date: May 1992 Formats: txt pdf Obsoletes: RFC 1172 Updated by: RFC 3241 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document defines the NCP for establishing and configuring theInternet Protocol [2] over PPP, and a method to negotiate and use VanJacobson TCP/IP header compression [3] with PPP. This RFC is a product of the Point-to-Point Protocol Working Group of the Internet Engineering Task Force (IETF).
RFC 1333	PPP Link Quality Monitoring
	Authors: W. Simpson. Date: May 1992 Formats: txt pdf Obsoleted by: RFC 1989 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, which allows negotiation of a Quality Protocol for continuous monitoring of the viability of the link. This document defines a protocol for generating Link-Quality-Reports. This RFC is a product of the Point-to-Point Protocol Working Group of the Internet Engineering Task Force (IETF). Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu mailing list.
RFC 1334	PPP Authentication Protocols
	Authors: B. Lloyd, W. Simpson. Date: October 1992 Formats: txt pdf Obsoleted by: RFC 1994 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, which allows negotiation of an Authentication Protocol for authenticating its peer before allowing Network Layer protocols to transmit over the link. This document defines two protocols for Authentication: the PasswordAuthentication Protocol and the Challenge-Handshake AuthenticationProtocol. This memo is the product of the Point-to-Point ProtocolWorking Group of the Internet Engineering Task Force (IETF).Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu mailing list.
RFC 1335	A Two-Tier Address Structure for the Internet: A Solution to the Problem of Address Space Exhaustion
	Authors: Z. Wang, J. Crowcroft. Date: May 1992 Formats: txt pdf Status: INFORMATIONAL This RFC presents a solution to problem of address space exhaustion in the Internet. It proposes a two-tier address structure for theInternet. This is an "idea" paper and discussion is strongly encouraged.
RFC 1336	Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members
	Authors: G. Malkin. Date: May 1992 Formats: txt pdf Obsoletes: RFC 1251 Also: FYI 0009 Status: INFORMATIONAL This FYI RFC contains biographical information about members of theInternet Activities Board (IAB), the Internet Engineering SteeringGroup (IESG) of the Internet Engineering Task Force (IETF), and the the Internet Research Steering Group (IRSG) of the Internet ResearchTask Force (IRTF).
RFC 1337	TIME-WAIT Assassination Hazards in TCP
	Authors: R. Braden. Date: May 1992 Formats: txt pdf Status: INFORMATIONAL This note describes some theoretically-possible failure modes for TCP connections and discusses possible remedies. In particular, one very simple fix is identified.
RFC 1338	Supernetting: an Address Assignment and Aggregation Strategy
	Authors: V. Fuller, T. Li, J. Yu, K. Varadhan. Date: June 1992 Formats: txt pdf Obsoleted by: RFC 1519 Status: INFORMATIONAL This memo discusses strategies for address assignment of the existingIP address space with a view to conserve the address space and stem the explosive growth of routing tables in default-route-free routers run by transit routing domain providers.
RFC 1339	Remote Mail Checking Protocol
	Authors: S. Dorner, P. Resnick. Date: June 1992 Formats: txt pdf Status: EXPERIMENTAL This RFC defines a protocol to provide a mail checking service to be used between a client and server pair. Typically, a small program on a client workstation would use the protocol to query a server in order to find out whether new mail has arrived for a specified user.
RFC 1340	Assigned Numbers
	Authors: J. Reynolds, J. Postel. Date: July 1992 Formats: txt pdf Obsoletes: RFC 1060 Obsoleted by: RFC 1700 Status: HISTORIC This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This memo is a status report on the parameters (i.e., numbers and keywords) used in protocols in the Internet community.
RFC 1341	MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies
	Authors: N. Borenstein, N. Freed. Date: June 1992 Formats: txt pdf ps Obsoleted by: RFC 1521 Status: PROPOSED STANDARD This document redefines the format of message bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information. [STANDARDS-TRACK]
RFC 1342	Representation of Non-ASCII Text in Internet Message Headers
	Authors: K. Moore. Date: June 1992 Formats: txt pdf Obsoleted by: RFC 1522 Status: PROPOSED STANDARD This memo describes an extension to the message format defined in [1](known to the IETF Mail Extensions Working Group as "RFC 1341"), to allow the representation of character sets other than ASCII in RFC822 message headers. The extensions described were designed to be highly compatible with existing Internet mail handling software, and to be easily implemented in mail readers that support RFC 1341.
RFC 1343	A User Agent Configuration Mechanism for Multimedia Mail Format Information
	Authors: N. Borenstein. Date: June 1992 Formats: txt pdf ps Status: INFORMATIONAL This memo suggests a file format to be used to inform multiple mail reading user agent programs about the locally-installed facilities for handling mail in various formats. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1344	Implications of MIME for Internet Mail Gateways
	Authors: N. Borenstein. Date: June 1992 Formats: txt pdf ps Status: INFORMATIONAL While MIME was carefully designed so that it does not require any changes to Internet electronic message transport facilities, there are several ways in which message transport systems may want to take advantage of MIME. These opportunities are the subject of this memo. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1345	Character Mnemonics and Character Sets
	Authors: K. Simonsen. Date: June 1992 Formats: txt pdf Status: INFORMATIONAL This memo lists a selection of characters and their presence in some coded character sets. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1346	Resource Allocation, Control, and Accounting for the Use of Network Resources
	Authors: P. Jones. Date: June 1992 Formats: txt pdf Status: INFORMATIONAL The purpose of this RFC is to focus discussion on particular challenges in large service networks in general, and the International IP Internet in particular. No solution discussed in this document is intended as a standard. Rather, it is hoped that a general consensus will emerge as to the appropriate solutions, leading eventually to the adoption of standards. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1347	TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing
	Authors: R. Callon. Date: June 1992 Formats: txt pdf ps Status: INFORMATIONAL This paper describes a simple proposal which provides a long-term solution to Internet addressing, routing, and scaling. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1348	DNS NSAP RRs
	Authors: B. Manning. Date: July 1992 Formats: txt pdf Obsoleted by: RFC 1637 Updates: RFC 1034, RFC 1035 Status: EXPERIMENTAL This RFC defines the format of two new Resource Records (RRs) for the Domain Name System (DNS), and reserves corresponding DNS type mnemonic and numerical codes. This memo defines an Experimental Protocol for the Internet community.
RFC 1349	Type of Service in the Internet Protocol Suite
	Authors: P. Almquist. Date: July 1992 Formats: txt pdf Obsoleted by: RFC 2474 Updates: RFC 1248, RFC 1247, RFC 1195, RFC 1123, RFC 1122, RFC 1060, RFC 0791 Status: PROPOSED STANDARD This memo changes and clarifies some aspects of the semantics of the Type of Service octet in the Internet Protocol (IP) header. [STANDARDS-TRACK]
RFC 1350	The TFTP Protocol (Revision 2)
	Authors: K. Sollins. Date: July 1992 Formats: txt pdf Obsoletes: RFC 0783 Updated by: RFC 1782, RFC 1783, RFC 1784, RFC 1785, RFC 2347, RFC 2348, RFC 2349 Also: STD 0033 Status: STANDARD TFTP is a very simple protocol used to transfer files. It is from this that its name comes, Trivial File Transfer Protocol or TFTP. Each nonterminal packet is acknowledged separately. This document describes the protocol and its types of packets. The document also explains the reasons behind some of the design decisions. [STANDARDS-TRACK]
RFC 1351	SNMP Administrative Model
	Authors: J. Davin, J. Galvin, K. McCloghrie. Date: July 1992 Formats: txt pdf Status: HISTORIC This memo presents an elaboration of the SNMP administrative model set forth in [1]. This model provides a unified conceptual basis for administering SNMP protocol entities to support: authenticaiton and integrity, privacy, access control, and cooperation of protocol entities. [STANDARDS-TRACK]
RFC 1352	SNMP Security Protocols
	Authors: J. Galvin, K. McCloghrie, J. Davin. Date: July 1992 Formats: txt pdf Status: HISTORIC The Simple Network Management Protocol (SNMP) specification [1] allows for the protection of network management operations by a variety of security protocols. The SNMP administrative model described in [2] provides a framework for securing SNMP network management. In the context of that framework, this memo defines protocols to support the following three security services: data integrity, data origin authentication and data confidentiality. [STANDARDS-TRACK]
RFC 1353	Definitions of Managed Objects for Administration of SNMP Parties
	Authors: K. McCloghrie, J. Davin, J. Galvin. Date: July 1992 Formats: txt pdf Status: HISTORIC This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it describes a representation of the SNMP parties defined in [8] as objects defined according to the Internet StandardSMI [1]. These definitions are consistent with the SNMP Security protocols set forth in [9].
RFC 1354	IP Forwarding Table MIB
	Authors: F. Baker. Date: July 1992 Formats: txt pdf Obsoleted by: RFC 2096 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing routes in the IPInternet. It is proposed that the ipRouteTable defined by MIB-II (RFC 1213) be deprecated and replaced with this table. This adds the ability to set or display multi-path routes, and varying routes by network management policy.
RFC 1355	Privacy and Accuracy Issues in Network Information Center Databases
	Authors: J. Curran, A. Marine. Date: August 1992 Formats: txt pdf Also: FYI 0015 Status: INFORMATIONAL This document provides a set of guidelines for the administration and operation of public Network Information Center (NIC) databases. The purpose is to formalize procedures for the responsible handling of the personal and organizational information maintained by NICs in publically accessible databases, and to improve the accuracy and accessibility of such data where appropriate.
RFC 1356	Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode
	Authors: A. Malis, D. Robinson, R. Ullmann. Date: August 1992 Formats: txt pdf Obsoletes: RFC 0877 Status: DRAFT STANDARD This document specifies the encapsulation of IP and other network layer protocols over X.25 networks, in accordance and alignment withISO/IEC and CCITT standards. It is a replacement for RFC 877, "AStandard for the Transmission of IP Datagrams Over Public DataNetworks" [1]. It was written to correct several ambiguities in the InternetStandard for IP/X.25 (RFC 877), to align it with ISO/IEC standards that have been written following RFC 877, to allow interoperable multiprotocol operation between routers and bridges over X.25, and to add some additional remarks based upon practical experience with the specification over the 8 years since that RFC. The substantive change to the IP encapsulation is an increase in the allowed IP datagram Maximum Transmission Unit from 576 to 1600, to reflect existing practice. This document also specifies the Internet encapsulation for protocols, including IP, on the packet mode of the ISDN. It applies to the use of Internet protocols on the ISDN in the circuit mode only when the circuit is established as an end-to-end X.25 connection.
RFC 1357	A Format for E-mailing Bibliographic Records
	Authors: D. Cohen. Date: July 1992 Formats: txt pdf Obsoleted by: RFC 1807 Status: INFORMATIONAL This memo defines a format for E-mailing bibliographic records of technical reports. It is intended to accelerate the dissemination of information about new Computer Science Technical Reports (CS-TR).
RFC 1358	Charter of the Internet Architecture Board (IAB)
	Authors: L. Chapin. Date: August 1992 Formats: txt pdf Obsoleted by: RFC 1601 Status: INFORMATIONAL The Internet Architecture Board (IAB) shall be constituted and shall operate as a technical advisory group of the Internet Society. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1359	Connecting to the Internet - What Connecting Institutions Should Anticipate
	Authors: ACM SIGUCCS. Date: August 1992 Formats: txt pdf Also: FYI 0016 Status: INFORMATIONAL This FYI RFC outlines the major issues an institution should consider in the decision and implementation of a campus connection to theInternet. In order to provide clarity to the reader, some specific information has been detailed. In doing so, the document has been directed toward U.S. academic institutions that have not yet connected to theInternet. However, the issues for which specific information has been provided can be generalized for any organization that wishes to participate in the world-wide Internet community. It will be necessary for those organizations to obtain the correct and detailed information from their local or national IP service providers. In addition, this document may be used as an evaluation checklist for organizations that are currently connected. Readers are expected to have general familiarity with networking concepts and terminology.
RFC 1360	IAB Official Protocol Standards
	Authors: J. Postel. Date: September 1992 Formats: txt pdf Obsoletes: RFC 1280 Obsoleted by: RFC 1410 Status: HISTORIC
RFC 1361	Simple Network Time Protocol (SNTP)
	Authors: D. Mills. Date: August 1992 Formats: txt pdf Obsoleted by: RFC 1769 Also: RFC 1305 Status: INFORMATIONAL This memorandum describes the Simple Network Time Protocol (SNTP), which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. SNTP can be used when the ultimate performance of the full NTP implementation described inRFC-1305 is not needed or justified. It involves no change to the current or previous NTP specification versions or known implementations, but rather a clarification of certain design features of NTP which allow operation in a simple, stateless RPC mode with accuracy and reliability expectations similar to the UDP/TIME protocol described in RFC-868. This memorandum does not obsolete or update any RFC. A working knowledge of RFC-1305 is not required for an implementation of SNTP.
RFC 1362	Novell IPX over Various WAN Media (IPXWAN)
	Authors: M. Allen. Date: September 1992 Formats: txt pdf Obsoleted by: RFC 1634 Status: INFORMATIONAL This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocolNovell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks.
RFC 1363	A Proposed Flow Specification
	Authors: C. Partridge. Date: September 1992 Formats: txt pdf Status: INFORMATIONAL A flow specification (or "flow spec") is a data structure used by internetwork hosts to request special services of the internetwork, often guarantees about how the internetwork will handle some of the hosts' traffic. In the future, hosts are expected to have to request such services on behalf of distributed applications such as multimedia conferencing. The flow specification defined in this memo is intended for information and possible experimentation (i.e., experimental use by consenting routers and applications only). This RFC is a product of the Internet Research Task Force (IRTF).
RFC 1364	BGP OSPF Interaction
	Authors: K. Varadhan. Date: September 1992 Formats: txt pdf Obsoleted by: RFC 1403 Also: RFC 1247, RFC 1267 Status: PROPOSED STANDARD This memo defines the various criteria to be used when designingAutonomous System Border Routers (ASBR) that will run BGP with otherASBRs external to the AS and OSPF as its IGP.
RFC 1365	An IP Address Extension Proposal
	Authors: K. Siyan. Date: September 1992 Formats: txt pdf Status: INFORMATIONAL This RFC suggests an extension to the IP protocol to solve the shortage of IP address problem, and requests discussion and suggestions for improvements.
RFC 1366	Guidelines for Management of IP Address Space
	Authors: E. Gerich. Date: October 1992 Formats: txt pdf Obsoleted by: RFC 1466 Status: INFORMATIONAL This document has been reviewed by the Federal Engineering Task Force(FEPG) on behalf of the Federal Networking Council (FNC), the co- chairs of the International Engineering Planning Group (IEPG), and the Reseaux IP Europeens (RIPE). There was general consensus by those groups to support the recommendations proposed in this document for management of the IP address space.
RFC 1367	Schedule for IP Address Space Management Guidelines
	Authors: C. Topolcic. Date: October 1992 Formats: txt pdf Obsoleted by: RFC 1467 Status: INFORMATIONAL This memo suggests a schedule for the implementation of the IP network number allocation plan described in RFC 1366. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1368	Definition of Managed Objects for IEEE 802.3 Repeater Devices
	Authors: D. McMaster, K. McCloghrie. Date: October 1992 Formats: txt pdf Obsoleted by: RFC 1516 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing IEEE 802.3 10Mb/second baseband repeaters, sometimes referred to as "hubs."
RFC 1369	Implementation Notes and Experience for the Internet Ethernet MIB
	Authors: F. Kastenholz. Date: October 1992 Formats: txt pdf Status: INFORMATIONAL This document reflects the currently known status of 11 different implementations of the MIB by 7 different vendors on 7 different Ethernet interface chips. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1370	Applicability Statement for OSPF
	Authors: Internet Architecture Board, L. Chapin. Date: October 1992 Formats: txt pdf Status: HISTORIC This Applicability Statement places a requirement on vendors claiming conformance to this standard, in order to assure that users will have the option of deploying OSPF when they need a multivendor, interoperable IGP in their environment. [STANDARDS-TRACK]
RFC 1371	Choosing a Common IGP for the IP Internet
	Authors: P. Gross. Date: October 1992 Formats: txt pdf Status: INFORMATIONAL This memo presents motivation, rationale and other surrounding background information leading to the IESG's recommendation to theIAB for a single "common IGP" for the IP portions of the Internet. In this memo, the term "common IGP" is defined, the need for a commonIGP is explained, the relation of this issue to other ongoingInternet Engineering Task Force (IETF) routing protocol development is provided, and the relation of this issue to the goal for multi- protocol integration in the Internet is explored. Finally, a specific IGP is recommended as the "common IGP" for IP portions of the Internet -- the Open Shortest Path First (OSPF) routing protocol. The goal of this recommendation is for all vendors of Internet IP routers to make OSPF available as one of the IGP's provided with their routers.
RFC 1372	Telnet Remote Flow Control Option
	Authors: C. Hedrick, D. Borman. Date: October 1992 Formats: txt pdf Obsoletes: RFC 1080 Status: PROPOSED STANDARD This document specifies an extended version of the Telnet Remote Flow Control Option, RFC 1080, with the addition of the RESTART-ANY and RESTART-XON suboptions. [STANDARDS-TRACK]
RFC 1373	Portable DUAs
	Authors: T. Tignor. Date: October 1992 Formats: txt pdf Status: INFORMATIONAL This document comes in two parts. The first part is for regular people who wish to set up their own DUAs (Directory User Interfaces) to access the Directory. The second part is for ISODE-maintainers wishing to provide portable DUAs to users. This part gives instructions in a similar but longer, step-by-step format. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1374	IP and ARP on HIPPI
	Authors: J. Renwick, A. Nicholson. Date: October 1992 Formats: txt pdf Obsoleted by: RFC 2834 Status: PROPOSED STANDARD The ANSI X3T9.3 committee has drafted a proposal for the encapsulation of IEEE 802.2 LLC PDUs and, by implication, IP onHIPPI. Another X3T9.3 draft describes the operation of HIPPI physical switches. X3T9.3 chose to leave HIPPI networking issues largely outside the scope of their standards; this document discusses methods of using of ANSI standard HIPPI hardware and protocols in the context of the Internet, including the use of HIPPI switches as LANs and interoperation with other networks.
RFC 1375	Suggestion for New Classes of IP Addresses
	Authors: P. Robinson. Date: October 1992 Formats: txt pdf Status: INFORMATIONAL This RFC suggests a change in the method of specifying the IP address to add new classes of networks to be called F, G, H, and K, to reduce the amount of wasted address space, and to increase the available IP address number space, especially for smaller organizations or classes of connectors that do not need or do not want a full Class C IP address.
RFC 1376	The PPP DECnet Phase IV Control Protocol (DNCP)
	Authors: S. Senum. Date: November 1992 Formats: txt pdf Obsoleted by: RFC 1762 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document defines the NCP for establishing and configuringDigital's DNA Phase IV Routing protocol (DECnet Phase IV) over PPP.This document applies only to DNA Phase IV Routing messages (both data and control), and not to other DNA Phase IV protocols (MOP, LAT, etc.).
RFC 1377	The PPP OSI Network Layer Control Protocol (OSINLCP)
	Authors: D. Katz. Date: November 1992 Formats: txt pdf Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document defines the NCP for establishing and configuring OSINetwork Layer Protocols. This memo is the product of the Point-to-Point Protocol Working Group of the Internet Engineering Task Force (IETF). Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu mailing list.
RFC 1378	The PPP AppleTalk Control Protocol (ATCP)
	Authors: B. Parker. Date: November 1992 Formats: txt pdf Status: HISTORIC The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document defines the NCP for establishing and configuring theAppleTalk Protocol [3] over PPP. This memo is a joint effort of the AppleTalk-IP Working Group and thePoint-to-Point Protocol Working Group of the Internet EngineeringTask Force (IETF). Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu mailing list.
RFC 1379	Extending TCP for Transactions -- Concepts
	Authors: R. Braden. Date: November 1992 Formats: txt pdf Obsoleted by: RFC 6247 Updated by: RFC 1644 Status: HISTORIC This memo discusses extension of TCP to provide transaction-oriented service, without altering its virtual-circuit operation. This extension would fill the large gap between connection-oriented TCP and datagram-based UDP, allowing TCP to efficiently perform many applications for which UDP is currently used. A separate memo contains a detailed functional specification for this proposed extension. This work was supported in part by the National Science Foundation under Grant Number NCR-8922231.
RFC 1380	IESG Deliberations on Routing and Addressing
	Authors: P. Gross, P. Almquist. Date: November 1992 Formats: txt pdf Status: INFORMATIONAL This memo summarizes issues surrounding the routing and addressing scaling problems in the IP architecture, and it provides a brief background of the ROAD group and related activities in the InternetEngineering Task Force (IETF). It also provides a preliminary report of the Internet EngineeringSteering Group (IESG) deliberations on how these routing and addressing issues should be pursued in the Internet ArchitectureBoard (IAB)/IETF.
RFC 1381	SNMP MIB Extension for X.25 LAPB
	Authors: D. Throop, F. Baker. Date: November 1992 Formats: txt pdf Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing the Link Layer ofX.25, LAPB. The objects defined here, along with the objects in the"SNMP MIB Extension for the Packet Layer of X.25" [9] and the"Definitions of Managed Objects for RS-232-like Hardware Devices"[8], combine to allow management of an X.25 protocol stack.
RFC 1382	SNMP MIB Extension for the X.25 Packet Layer
	Authors: D. Throop, Ed.. Date: November 1992 Formats: txt pdf Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing the Packet Layer ofX.25. The objects defined here, along with the objects in the "SNMPMIB Extension for LAPB" [9] and the "Definitions of Managed Objects for RS-232-like Hardware Devices" [8], combine to allow management of an X.25 protocol stack.
RFC 1383	An Experiment in DNS Based IP Routing
	Authors: C. Huitema. Date: December 1992 Formats: txt pdf Status: EXPERIMENTAL Potential solutions to the routing explosion. This memo defines an Experimental Protocol for the Internet community.
RFC 1384	Naming Guidelines for Directory Pilots
	Authors: P. Barker, S.E. Hardcastle-Kille. Date: January 1993 Formats: txt pdf ps Obsoleted by: RFC 1617, RTR_0011 Status: INFORMATIONAL Deployment of a Directory will benefit from following certain guidelines. This document defines a number of naming guidelines.Alignment to these guidelines is recommended for directory pilots.
RFC 1385	EIP: The Extended Internet Protocol
	Authors: Z. Wang. Date: November 1992 Formats: txt pdf Status: INFORMATIONAL EIP can substantially reduce the amount of modifications needed to the current Internet systems and greatly ease the difficulties of transition. This is an "idea" paper and discussion is strongly encouraged on Big-Internet@munnari.oz.au. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1386	The US Domain
	Authors: A. Cooper, J. Postel. Date: December 1992 Formats: txt pdf Obsoleted by: RFC 1480 Status: INFORMATIONAL This is a description of the US Top Level Domains on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1387	RIP Version 2 Protocol Analysis
	Authors: G. Malkin. Date: January 1993 Formats: txt pdf Obsoleted by: RFC 1721 Status: INFORMATIONAL As required by Routing Protocol Criteria (RFC 1264), this report documents the key features of the RIP-2 protocol and the current implementation experience.
RFC 1388	RIP Version 2 Carrying Additional Information
	Authors: G. Malkin. Date: January 1993 Formats: txt pdf Obsoleted by: RFC 1723 Updates: RFC 1058 Status: PROPOSED STANDARD This document specifies an extension of the Routing InformationProtocol (RIP), as defined in [1], to expand the amount of useful information carried in RIP packets and to add a measure of security.A companion document will define the SNMP MIB objects for RIP-2 [2].
RFC 1389	RIP Version 2 MIB Extensions
	Authors: G. Malkin, F. Baker. Date: January 1993 Formats: txt pdf Obsoleted by: RFC 1724 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing RIP Version 2.
RFC 1390	Transmission of IP and ARP over FDDI Networks
	Authors: D. Katz. Date: January 1993 Formats: txt pdf Also: STD 0036 Status: STANDARD This memo defines a method of encapsulating the Internet Protocol(IP) datagrams and Address Resolution Protocol (ARP) requests and replies on Fiber Distributed Data Interface (FDDI) Networks. This RFC is the product of the IP over FDDI Working Group of theInternet Engineering Task Force (IETF).
RFC 1391	The Tao of the IETF: A Guide for New Attendees of the Internet Engineering Task Force
	Authors: G. Malkin. Date: January 1993 Formats: txt pdf Obsoleted by: RFC 1539 Status: INFORMATIONAL Over the last two years, the attendance at Internet Engineering TaskForce (IETF) Plenary meetings has grown phenomenally. Approximately38% of the attendees are new to the IETF at each meeting. About 33% of those go on to become regular attendees. When the meetings were smaller, it wasn't very difficult for a newcomer to get to know people and get into the swing of things. Today, however, a newcomer meets many more new people, some previously known only as the authors of Request For Comments (RFC) documents or thought provoking email messages. The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This will give them a warm, fuzzy feeling and enable them to make the meeting more productive for everyone. This FYI will also provide the mundane bits of information which everyone who attends an IETF meeting should know.
RFC 1392	Internet Users' Glossary
	Authors: G. Malkin, T. LaQuey Parker. Date: January 1993 Formats: txt pdf Obsoleted by: RFC 1983 Status: INFORMATIONAL There are many networking glossaries in existence. This glossary concentrates on terms which are specific to the Internet. Naturally, there are entries for some basic terms and acronyms because other entries refer to them.
RFC 1393	Traceroute Using an IP Option
	Authors: G. Malkin. Date: January 1993 Formats: txt pdf Status: EXPERIMENTAL Traceroute serves as a valuable network debugging tool. The way in which it is currently implemented has the advantage of being automatically supported by all of the routers. It's two problems are the number of packets it generates and the amount of time it takes to run. This document specifies a new IP option and ICMP message type which duplicates the functionality of the existing traceroute method while generating fewer packets and completing in a shorter time.
RFC 1394	Relationship of Telex Answerback Codes to Internet Domains
	Authors: P. Robinson. Date: January 1993 Formats: txt pdf Status: INFORMATIONAL This RFC gives the list, as best known, of all common Internet domains and the conversion between specific country telex answerback codes and Internet country domain identifiers. It also lists the telex code and international dialing code, wherever it is available.It will also list major Internet "Public" E-Mail addresses. This list is designed to show the corresponding codes for Fax and voice messages, telex country codes, telex answerbacks and Internet domains. It is an attempt to place all of the information into one list and all the connections for each country.
RFC 1395	BOOTP Vendor Information Extensions
	Authors: J. Reynolds. Date: January 1993 Formats: txt pdf Obsoletes: RFC 1084, RFC 1048 Obsoleted by: RFC 1497, RFC 1533 Updates: RFC 0951 Status: DRAFT STANDARD This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo. This memo will be updated as additional tags are defined. This edition introduces Tag 14 for Merit Dump File, Tag 15 for Domain Name, Tag 16 for Swap Server and Tag 17 for Root Path. This memo is a status report on the vendor information extensions used int the Bootstrap Protocol (BOOTP).
RFC 1396	The Process for Organization of Internet Standards Working Group (POISED)
	Authors: S. Crocker. Date: January 1993 Formats: txt pdf Status: INFORMATIONAL This report provides a summary of the POISED Working Group (WG), starting from the events leading to the formation of the WG to the end of 1992. Necessarily, this synopsis represents my own perception, particularly for the "prehistory" period. Quite a few people hold strong views about both the overall sequence and specific events. My intent here is to convey as neutral a point of view as possible.
RFC 1397	Default Route Advertisement In BGP2 and BGP3 Version of The Border Gateway Protocol
	Authors: D. Haskin. Date: January 1993 Formats: txt pdf Status: HISTORIC This document specifies the recommendation of the BGP Working Group on default route advertisement support in BGP2 [1] and BGP3 [2] versions of the Border Gateway Protocol. This recommendation only applies to BGP2 and BGP3 versions of theBorder Gateway Protocol since starting with the BGP4 [3] version a default route advertisement capability is built in the protocol.
RFC 1398	Definitions of Managed Objects for the Ethernet-Like Interface Types
	Authors: F. Kastenholz. Date: January 1993 Formats: txt pdf Obsoletes: RFC 1284 Obsoleted by: RFC 1623 Status: DRAFT STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing ethernet-like objects.
RFC 1399	Summary of 1300-1399
	Authors: J. Elliott. Date: January 1997 Formats: txt pdf Status: INFORMATIONAL
RFC 1400	Transition and Modernization of the Internet Registration Service
	Authors: S. Williamson. Date: March 1993 Formats: txt pdf Status: INFORMATIONAL As a result of the NREN NIS award by National Science Foundation, non- DDN registration services will soon be transferred from the DDN NIC to the new Internet Registration Service, which is a part of an entity referred to as the InterNIC. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1401	Correspondence between the IAB and DISA on the use of DNS
	Authors: Internet Architecture Board. Date: January 1993 Formats: txt pdf Status: INFORMATIONAL This memo reproduces three letters exchanged between the InternetActivities Board (IAB) and the Defense Information Systems Agency(DISA) regarding the importance of using the Domain Name System (DNS) throughout the Internet, and phasing out the use of older host name to address tables, such as "hosts.txt".
RFC 1402	There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places
	Authors: J. Martin. Date: January 1993 Formats: txt pdf Obsoletes: RFC 1290 Also: FYI 0010 Status: INFORMATIONAL A wealth of information exists on the network. In fact, there is so much information that you could spend your entire life browsing. This paper will present some of the "gold nuggets" of information and file repositories on the network that could be useful. The ultimate goal is to make the route to these sources of information invisible to you. At present, this is not easy to do. I will explain some of the techniques that can be used to make these nuggets easier to pick up so that we all can be richer.
RFC 1403	BGP OSPF Interaction
	Authors: K. Varadhan. Date: January 1993 Formats: txt pdf Obsoletes: RFC 1364 Status: HISTORIC This memo defines the various criteria to be used when designing anAutonomous System Border Routers (ASBR) that will run BGP with otherASBRs external to the AS and OSPF as its IGP. This is a republication of RFC 1364 to correct some editorial problems.
RFC 1404	A Model for Common Operational Statistics
	Authors: B. Stockman. Date: January 1993 Formats: txt pdf Obsoleted by: RFC 1857 Status: INFORMATIONAL This memo describes a model for operational statistics in theInternet. It gives recommendations for metrics, measurements, polling periods, storage formats and presentation formats.
RFC 1405	Mapping between X.400(1984/1988) and Mail-11 (DECnet mail)
	Authors: C. Allocchio. Date: January 1993 Formats: txt pdf Obsoleted by: RFC 2162 Status: EXPERIMENTAL This document describes a set of mappings which will enable inter working between systems operating the CCITT X.400 ( 1984 / 1988 )Recommendations on Message Handling Systems, and systems running theMail-11 (also known as DECnet mail) protocol. The specifications are valid within DECnet Phase IV addressing and routing scheme. The complete scenario of X.400 / RFC822 / Mail-11 is also considered, in order to cover the possible complex cases arising in multiple gateway translations. This document covers mainly the O/R address to DECnet from/to address mapping (and vice versa); other mappings are based on RFC 1327 and its eventual future updates. This is a combined effort of COSINE S2.2, the RARE MSG Working Group, and the IETF X.400 Ops Working Group.
RFC 1406	Definitions of Managed Objects for the DS1 and E1 Interface Types
	Authors: F. Baker, J. Watt, Eds.. Date: January 1993 Formats: txt pdf Obsoletes: RFC 1232 Obsoleted by: RFC 2495 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing DS1 Interfaces -- including both T1 and E1 (a.k.a., CEPT 2 Mbit/s) links. This document entirely replaces RFC 1232, which contains a fundamental error: many objects are encoded as Counters that must be encoded as INTEGERs or Gauges. The magnitude of the change required is sufficient that virtually every object changed. Therefore, theMIB documented in RFC 1232 should not be implemented.
RFC 1407	Definitions of Managed Objects for the DS3/E3 Interface Type
	Authors: T. Cox, K. Tesink. Date: January 1993 Formats: txt pdf Obsoletes: RFC 1233 Obsoleted by: RFC 2496 Status: PROPOSED STANDARD This memo defines an extension to the Management Information Base(MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing DS3 and E3Interfaces. This document is a companion document with Definitions of Managed Objects for the DS1 Interface Type. This document entirely replaces RFC 1233, which contains a fundamental error: many objects are encoded as Counters that must be encoded as INTEGERs or Gauges. The magnitude of the change required is sufficient that virtually every object changed. Therefore, theMIB documented in RFC 1233 should not be implemented.
RFC 1408	Telnet Environment Option
	Authors: D. Borman, Ed.. Date: January 1993 Formats: txt pdf Updated by: RFC 1571 Status: HISTORIC This document specifies a mechanism for passing environment information between a telnet client and server. Use of this mechanism enables a telnet user to propagate configuration information to a remote host when connecting.
RFC 1409	Telnet Authentication Option
	Authors: D. Borman, Ed.. Date: January 1993 Formats: txt pdf Obsoleted by: RFC 1416 Status: EXPERIMENTAL This memo defines an Experimental Protocol for the Internet community.
RFC 1410	IAB Official Protocol Standards
	Authors: J. Postel, Ed.. Date: March 1993 Formats: txt pdf Obsoletes: RFC 1360 Obsoleted by: RFC 1500 Status: HISTORIC This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB).
RFC 1411	Telnet Authentication: Kerberos Version 4
	Authors: D. Borman, Ed.. Date: January 1993 Formats: txt pdf Status: EXPERIMENTAL This memo defines an Experimental Protocol for the Internet community.
RFC 1412	Telnet Authentication: SPX
	Authors: K. Alagappan. Date: January 1993 Formats: txt pdf Status: EXPERIMENTAL This memo defines an Experimental Protocol for the Internet community.
RFC 1413	Identification Protocol
	Authors: M. St. Johns. Date: February 1993 Formats: txt pdf Obsoletes: RFC 0931 Status: PROPOSED STANDARD The Identification Protocol was formerly called the Authentication Server Protocol. It has been renamed to better reflect its function. [STANDARDS-TRACK]
RFC 1414	Identification MIB
	Authors: M. St. Johns, M. Rose. Date: February 1993 Formats: txt pdf Status: HISTORIC This memo defines a MIB for use with identifying the users associated with TCP connections. It provides functionality approximately equivalent to that provided by the protocol defined in RFC 1413 [1].This document is a product of the TCP Client Identity ProtocolWorking Group of the Internet Engineering Task Force (IETF).
RFC 1415	FTP-FTAM Gateway Specification
	Authors: J. Mindel, R. Slaski. Date: January 1993 Formats: txt pdf Status: HISTORIC This memo describes a dual protocol stack application layer gateway that performs protocol translation, in an interactive environment, between the FTP and FTAM file transfer protocols. Two key assumptions are made: 1) POSIX file naming conventions and hierarchical organization, rather than proprietary conventions are in use; and 2) X.500 Directory Services are available.
RFC 1416	Telnet Authentication Option
	Authors: D. Borman, Ed.. Date: February 1993 Formats: txt pdf Obsoletes: RFC 1409 Obsoleted by: RFC 2941 Status: EXPERIMENTAL This RFC 1416 replaces RFC 1409, which has an important typographical error in the example on page 6 (one occurance of "REPLY" should be "IS"). This memo defines an Experimental Protocol for the Internet community.
RFC 1417	NADF Standing Documents: A Brief Overview
	Authors: The North American Directory Forum. Date: February 1993 Formats: txt pdf Obsoletes: RFC 1295, RFC 1255, RFC 1218 Obsoleted by: RFC 1758 Status: INFORMATIONAL The purpose of this document is to provide a brief overview of the NADF's Standing Document series. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1418	SNMP over OSI
	Authors: M. Rose. Date: March 1993 Formats: txt pdf Obsoletes: RFC 1161, RFC 1283 Status: HISTORIC This memo addresses some concerns by defining a framework for running the SNMP in an environment which supports the OSI connectionless-mode transport service. [STANDARDS-TRACK]
RFC 1419	SNMP over AppleTalk
	Authors: G. Minshall, M. Ritter. Date: March 1993 Formats: txt pdf Status: HISTORIC This memo describes the method by which the Simple Network Management Protocol (SNMP) as specified in [1] can be used over AppleTalk protocols [2] instead of the Internet UDP/IP protocol stack. [STANDARDS-TRACK]
RFC 1420	SNMP over IPX
	Authors: S. Bostock. Date: March 1993 Formats: txt pdf Obsoletes: RFC 1298 Status: PROPOSED STANDARD This document defines a convention for encapsulating Simple NetworkManagement Protocol (SNMP) [1] packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol [2].
RFC 1421	Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures
	Authors: J. Linn. Date: February 1993 Formats: txt pdf Obsoletes: RFC 1113 Status: HISTORIC This document defines message encryption and authentication procedures, in order to provide privacy-enhanced mail (PEM) services for electronic mail transfer in the Internet. [STANDARDS-TRACK]
RFC 1422	Privacy Enhancement for Internet Electronic Mail: Part II: Certificate-Based Key Management
	Authors: S. Kent. Date: February 1993 Formats: txt pdf Obsoletes: RFC 1114 Status: HISTORIC This is one of a series of documents defining privacy enhancement mechanisms for electronic mail transferred using Internet mail protocols. [STANDARDS-TRACK]
RFC 1423	Privacy Enhancement for Internet Electronic Mail: Part III: Algorithms, Modes, and Identifiers
	Authors: D. Balenson. Date: February 1993 Formats: txt pdf Obsoletes: RFC 1115 Status: HISTORIC This document provides definitions, formats, references, and citations for cryptographic algorithms, usage modes, and associated identifiers and parameters used in support of Privacy Enhanced Mail(PEM) in the Internet community. It is intended to become one member of the set of related PEM RFCs. This document is organized into four primary sections, dealing with message encryption algorithms, message integrity check algorithms, symmetric key management algorithms, and asymmetric key management algorithms (including both asymmetric encryption and asymmetric signature algorithms). Some parts of this material are cited by other documents and it is anticipated that some of the material herein may be changed, added, or replaced without affecting the citing documents. Therefore, algorithm-specific material has been placed into this separate document. Use of other algorithms and/or modes will require case-by-case study to determine applicability and constraints. The use of additional algorithms may be documented first in Prototype or Experimental RFCs.As experience is gained, these protocols may be considered for incorporation into the standard. Additional algorithms and modes approved for use in PEM in this context will be specified in successors to this document.
RFC 1424	Privacy Enhancement for Internet Electronic Mail: Part IV: Key Certification and Related Services
	Authors: B. Kaliski. Date: February 1993 Formats: txt pdf Status: HISTORIC This document describes three types of service in support of Internet Privacy-Enhanced Mail (PEM) [1-3]: key certification, certificate- revocation list (CRL) storage, and CRL retrieval. [STANDARDS-TRACK]
RFC 1425	SMTP Service Extensions
	Authors: J. Klensin, WG Chair, N. Freed, Ed., M. Rose, E. Stefferud, D. Crocker. Date: February 1993 Formats: txt pdf Obsoleted by: RFC 1651 Status: PROPOSED STANDARD This memo defines a framework for extending the SMTP service by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports. [STANDARDS-TRACK]
RFC 1426	SMTP Service Extension for 8bit-MIMEtransport
	Authors: J. Klensin, WG Chair, N. Freed, Ed., M. Rose, E. Stefferud, D. Crocker. Date: February 1993 Formats: txt pdf Obsoleted by: RFC 1652 Status: PROPOSED STANDARD This memo defines an extension to the SMTP service whereby an SMTP content body containing octets outside of the US ASCII octet range (hex
RFC 1427	SMTP Service Extension for Message Size Declaration
	Authors: J. Klensin, WG Chair, N. Freed, Ed., K. Moore. Date: February 1993 Formats: txt pdf Obsoleted by: RFC 1653 Status: PROPOSED STANDARD This memo defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to decline to accept a message (perhaps temporarily) based on the client's estimate of the message size. [STANDARDS-TRACK]
RFC 1428	Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIME
	Authors: G. Vaudreuil. Date: February 1993 Formats: txt pdf Status: INFORMATIONAL Protocols for extending SMTP to pass 8bit characters have been defined [3] [4]. These protocols require that messages transported by the extended SMTP are to be encoded in MIME [1] [2]. Before work began on these protocols, several SMTP implementations adopted ad-hoc mechanisms for sending 8bit data. It is desirable for the extendedSMTP environment and these ad hoc mechanisms interoperate. This document outlines the problems in this environment and an approach to minimizing the cost of transition from current usage of non-MIME 8bit messages to MIME.
RFC 1429	Listserv Distribute Protocol
	Authors: E. Thomas. Date: February 1993 Formats: txt pdf Status: INFORMATIONAL This memo specifies a subset of the distribution protocol used by theBITNET LISTSERV to deliver mail messages to large amounts of recipients. This protocol, known as DISTRIBUTE, optimizes the distribution by sending a single copy of the message over heavily loaded links, insofar as topological information is available to guide such decisions, and reduces the average turnaround time for large mailing lists to 5-15 minutes on the average. This memo describes a simple interface allowing non-BITNET mailing list exploders (or other bulk-delivery scripts) to take advantage of this service by letting the BITNET distribution network take care of the delivery.
RFC 1430	A Strategic Plan for Deploying an Internet X.500 Directory Service
	Authors: S. Hardcastle-Kille, E. Huizer, V. Cerf, R. Hobby, S. Kent. Date: February 1993 Formats: txt pdf Status: INFORMATIONAL There are a number of reasons why a new Internet Directory Service is required. This document describes an overall strategy for deploying a Directory Service on the Internet, based on the OSI X.500 DirectoryService. It then describes in more detail the initial steps which need to be taken in order to achieve these goals, and how work already undertaken by Internet Engineering Task Force Working Groups(IETF WGs) is working towards these goals.
RFC 1431	DUA Metrics (OSI-DS 33 (v2))
	Authors: P. Barker. Date: February 1993 Formats: txt pdf Status: INFORMATIONAL This RFC is being distributed to members of the Internet community in order to solicit their reactions to the proposals contained in it.While the issues discussed may not be directly relevant to the research problems of the Internet, they may be interesting to a number of researchers and implementers. This document defines a set of criteria by which a DUA implementation, or more precisely a Directory user interface, may be judged. Particular issues covered include terminal requirements; style of interface; target user; default object classes and attribute types; use of DAP; error handling. The focus of the note is on"white pages" DUAs: this is a reflection of the current information base. Nevertheless much of the document will be applicable to DUAs developed for other types of Directory usage. Please send comments to the author or to the discussion group <osi- ds@CS.UCL.AC.UK&rt;.
RFC 1432	Recent Internet Books
	Authors: J. Quarterman. Date: March 1993 Formats: txt pdf Status: INFORMATIONAL This article originally appeared in Volume 2 Number 12, (December1992) of Matrix News, the monthly newsletter of Matrix Information and Directory Services, Inc. (MIDS).
RFC 1433	Directed ARP
	Authors: J. Garrett, J. Hagan, J. Wong. Date: March 1993 Formats: txt pdf Status: EXPERIMENTAL A router with an interface to two IP networks via the same link level interface could observe that the two IP networks share the same link level network, and could advertise that information to hosts (viaICMP Redirects) and routers (via dynamic routing protocols).However, a host or router on only one of the IP networks could not use that information to communicate directly with hosts and routers on the other IP network unless it could resolve IP addresses on the"foreign" IP network to their corresponding link level addresses.Directed ARP is a dynamic address resolution procedure that enables hosts and routers to resolve advertised potential next-hop IP addresses on foreign IP networks to their associated link level addresses.
RFC 1434	Data Link Switching: Switch-to-Switch Protocol
	Authors: R. Dixon, D. Kushi. Date: March 1993 Formats: txt pdf ps Obsoleted by: RFC 1795 Status: INFORMATIONAL This RFC describes IBM's support of Data Link Switching over TCP/IP.The RFC is being distributed to members of the Internet community in order to solicit their reactions to the proposals contained in it.While the issues discussed may not be directly relevant to the research problems of the Internet, they may be interesting to a number of researchers and implementors. Any questions or comments relative to the contents of this RFC should be sent to the following Internet address: dlsw@ralvma.vnet.ibm.com.
RFC 1435	IESG Advice from Experience with Path MTU Discovery
	Authors: S. Knowles. Date: March 1993 Formats: txt pdf Status: INFORMATIONAL In the course of reviewing the MTU Discovery protocol for possible elevation to Draft Standard, a specific operational problem was uncovered. The problem results from the optional suppression of ICMP messages implemented in some routers. This memo outlines a modification to this practice to allow the correct functioning of MTUDiscovery.
RFC 1436	The Internet Gopher Protocol (a distributed document search and retrieval protocol)
	Authors: F. Anklesaria, M. McCahill, P. Lindner, D. Johnson, D. Torrey, B. Albert. Date: March 1993 Formats: txt pdf Status: INFORMATIONAL The Internet Gopher protocol is designed for distributed document search and retrieval. This document describes the protocol, lists some of the implementations currently available, and has an overview of how to implement new client and server applications. This document is adapted from the basic Internet Gopher protocol document first issued by the Microcomputer Center at the University ofMinnesota in 1991.
RFC 1437	The Extension of MIME Content-Types to a New Medium
	Authors: N. Borenstein, M. Linimon. Date: April 1 1993 Formats: txt pdf Status: INFORMATIONAL A previous document, RFC 1341, defines a format and general framework for the representation of a wide variety of data types in Internet mail. This document defines one particular type of MIME data, the matter-transport/sentient-life-form type. The matter- transport/sentient-life-form MIME type is intended to facilitate the wider interoperation of electronic mail messages that include entire sentient life forms, such as human beings. Other informally proposed subtypes, such as "non-sentient-life-form","non-sentient-non-life-form", and the orthogonally necessary but nevertheless puzzling "sentient-non-life-form", are not described in this memo.
RFC 1438	Internet Engineering Task Force Statements Of Boredom (SOBs)
	Authors: A. Lyman Chapin, C. Huitema. Date: April 1 1993 Formats: txt pdf Status: INFORMATIONAL This document creates a new subseries of RFCs, entitled, IETF Statements Of Boredom (SOBs). This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1439	The Uniqueness of Unique Identifiers
	Authors: C. Finseth. Date: March 1993 Formats: txt pdf Status: INFORMATIONAL This RFC provides information that may be useful when selecting a method to use for assigning unique identifiers to people.
RFC 1440	SIFT/UFT: Sender-Initiated/Unsolicited File Transfer
	Authors: R. Troth. Date: July 1993 Formats: txt pdf Status: EXPERIMENTAL This document describes a Sender-Initiated File Transfer (SIFT) protocol, also commonly called Unsolicited File Transfer (UFT) protocol. This memo defines an Experimental Protocol for the Internet community.
RFC 1441	Introduction to version 2 of the Internet-standard Network Management Framework
	Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser. Date: April 1993 Formats: txt pdf Status: HISTORIC The purpose of this document is to provide an overview of version 2 of the Internet-standard Network Management Framework, termed the SNMP version 2 framework (SNMPv2). [STANDARDS-TRACK]
RFC 1442	Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)
	Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser. Date: April 1993 Formats: txt pdf Obsoleted by: RFC 1902 Status: PROPOSED STANDARD Management information is viewed as a collection of managed objects, residing in a virtual information store, termed the Management Information Base (MIB). Collections of related objects are defined in MIB modules. These modules are written using a subset of OSI's Abstract Syntax Notation One (ASN.1) [1]. It is the purpose of this document, the Structure of Management Information (SMI), to define that subset. [STANDARDS-TRACK]
RFC 1443	Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2)
	Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser. Date: April 1993 Formats: txt pdf Obsoleted by: RFC 1903 Status: PROPOSED STANDARD It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK]
RFC 1444	Conformance Statements for version 2 of the Simple Network Management Protocol (SNMPv2)
	Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser. Date: April 1993 Formats: txt pdf Obsoleted by: RFC 1904 Status: PROPOSED STANDARD It may be useful to define the acceptable lower-bounds of implementation, along with the actual level of implementation achieved. It is the purpose of this document to define the notation used for these purposes. [STANDARDS-TRACK]
RFC 1445	Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2)
	Authors: J. Galvin, K. McCloghrie. Date: April 1993 Formats: txt pdf Status: HISTORIC It is the purpose of this document, the Administrative Model for SNMPv2, to define how the administrative framework is applied to realize effective network management in a variety of configurations and environments. [STANDARDS-TRACK]
RFC 1446	Security Protocols for version 2 of the Simple Network Management Protocol (SNMPv2)
	Authors: J. Galvin, K. McCloghrie. Date: April 1993 Formats: txt pdf Status: HISTORIC It is the purpose of this document, Security Protocols for SNMPv2, to define one such authentication and one such privacy protocol. [STANDARDS-TRACK]
RFC 1447	Party MIB for version 2 of the Simple Network Management Protocol (SNMPv2)
	Authors: K. McCloghrie, J. Galvin. Date: April 1993 Formats: txt pdf Status: HISTORIC The Administrative Model for SNMPv2 document [3] defines the properties associated with SNMPv2 parties, SNMPv2 contexts, and access control policies. It is the purpose of this document, the Party MIB for SNMPv2, to define managed objects which correspond to these properties. [STANDARDS-TRACK]
RFC 1448	Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)
	Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser. Date: April 1993 Formats: txt pdf Obsoleted by: RFC 1905 Status: PROPOSED STANDARD It is the purpose of this document, Protocol Operations for SNMPv2, to define the operations of the protocol with respect to the sending and receiving of the PDUs. [STANDARDS-TRACK]
RFC 1449	Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2)
	Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser. Date: April 1993 Formats: txt pdf Obsoleted by: RFC 1906 Status: PROPOSED STANDARD It is the purpose of this document to define how the SNMPv2 maps onto an initial set of transport domains. [STANDARDS-TRACK]
RFC 1450	Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)
	Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser. Date: April 1993 Formats: txt pdf Obsoleted by: RFC 1907 Status: PROPOSED STANDARD It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity. [STANDARDS-TRACK]
RFC 1451	Manager-to-Manager Management Information Base
	Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser. Date: April 1993 Formats: txt pdf Status: HISTORIC It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity acting in both a manager role and an agent role. [STANDARDS-TRACK]
RFC 1452	Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework
	Authors: J. Case, K. McCloghrie, M. Rose, S. Waldbusser. Date: April 1993 Formats: txt pdf Obsoleted by: RFC 1908 Status: PROPOSED STANDARD The purpose of this document is to describe coexistence between version 2 of the Internet-standard Network Management Framework, termed the SNMP version 2 framework (SNMPv2) [1], and the original Internet-standard Network Management Framework (SNMPv1). [STANDARDS-TRACK]
RFC 1453	A Comment on Packet Video Remote Conferencing and the Transport/Network Layers
	Authors: W. Chimiak. Date: April 1993 Formats: txt pdf Status: INFORMATIONAL The new generation of multimedia applications demands new features and new mechanisms for proper performance. ATM technology has moved from concept to reality, delivering very high bandwidths and new capabilities to the data link layer user. In an effort to anticipate the high bandwidth-delay data link layer, Delta-t [Delta-t], NETBLT[RFC 988], and VMTP [RFC 1045] were developed. The excellent insights and mechanisms pioneered by the creators of these experimental Internet protocols were used in the design of XpressTransfer Protocol (XTP) [XTP92] with the goal of eventually delivering ATM bandwidths to a user process. This RFC is a vehicle to inform the Internet community about XTP as it benefits from pastInternet activity and targets general-purpose applications and multimedia applications with the emerging ATM networks in mind.
RFC 1454	Comparison of Proposals for Next Version of IP
	Authors: T. Dixon. Date: May 1993 Formats: txt pdf Status: INFORMATIONAL This is a slightly edited reprint of RARE Technical Report(RTC(93)004). The following is a brief summary of the characteristics of the three main proposals for replacing the current Internet Protocol. It is not intended to be exhaustive or definitive (a brief bibliography at the end points to sources of more information), but to serve as input to the European discussions on these proposals, to be co-ordinated byRARE and RIPE. It should be recognised that the proposals are themselves "moving targets", and in so far as this paper is accurate at all, it reflects the position at the 25th IETF meeting inWashington, DC. Comments from Ross Callon and Paul Tsuchiya on the original draft have been incorporated. Note that for a time the term"IPv7" was use to mean the eventual next version of IP, but that the same term was closely associated with a particilar proposal, so the term "IPng" is now used to identify the eventual next generation ofIP. The paper begins with a "generic" discussion of the mechanisms for solving problems and achieving particular goals, before discussing the proposals invidually.
RFC 1455	Physical Link Security Type of Service
	Authors: D. Eastlake 3rd. Date: May 1993 Formats: txt pdf Obsoleted by: RFC 2474 Status: EXPERIMENTAL This RFC documents an experimental protocol providing a Type ofService (TOS) to request maximum physical link security. This is an addition to the types of service enumerated in RFC 1349: Type ofService in the Internet Protocol Suite. The new TOS requests the network to provide what protection it can against surreptitious observation by outside agents of traffic so labeled. The purpose is protection against traffic analysis and as an additional possible level of data confidentiality. This TOS is consistent with all other defined types of service for IP version 4 in that it is based on link level characteristics and will not provide any particular guaranteed level of service.
RFC 1456	Conventions for Encoding the Vietnamese Language VISCII: VIetnamese Standard Code for Information Interchange VIQR: VIetnamese Quoted-Readable Specification
	Authors: Vietnamese Standardization Working Group. Date: May 1993 Formats: txt pdf Status: INFORMATIONAL This document provides information to the Internet community on the currently used conventions for encoding Vietnamese characters into7-bit US ASCII and in an 8-bit form. These conventions are widely used by the overseas Vietnamese who are on the Internet and are active in USENET. This document only provides information and specifies no level of standard.
RFC 1457	Security Label Framework for the Internet
	Authors: R. Housley. Date: May 1993 Formats: txt pdf Status: INFORMATIONAL This memo presents a security labeling framework for the Internet. The framework is intended to help protocol designers determine what, if any, security labeling should be supported by their protocols. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1458	Requirements for Multicast Protocols
	Authors: R. Braudes, S. Zabele. Date: May 1993 Formats: txt pdf Status: INFORMATIONAL This memo discusses some of these unresolved issues, and provides a high-level design for a new multicast transport protocol, group address and membership authority, and modifications to existing routing protocols. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1459	Internet Relay Chat Protocol
	Authors: J. Oikarinen, D. Reed. Date: May 1993 Formats: txt pdf Updated by: RFC 2810, RFC 2811, RFC 2812, RFC 2813 Status: EXPERIMENTAL The IRC protocol was developed over the last 4 years since it was first implemented as a means for users on a BBS to chat amongst themselves. Now it supports a world-wide network of servers and clients, and is stringing to cope with growth. Over the past 2 years, the average number of users connected to the main IRC network has grown by a factor of 10. The IRC protocol is a text-based protocol, with the simplest client being any socket program capable of connecting to the server.
RFC 1460	Post Office Protocol - Version 3
	Authors: M. Rose. Date: June 1993 Formats: txt pdf Obsoletes: RFC 1225 Obsoleted by: RFC 1725 Status: DRAFT STANDARD This memo is a revision to RFC 1225, a Draft Standard. [STANDARDS- TRACK]
RFC 1461	SNMP MIB extension for Multiprotocol Interconnect over X.25
	Authors: D. Throop. Date: May 1993 Formats: txt pdf Status: HISTORIC This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing MultiprotocolInterconnect (including IP) traffic carried over X.25. The objects defined here, along with the objects in the "SNMP MIB extension for the Packet Layer of X.25"[8], "SNMP MIB extension for LAPB"[7], and the "Definitions of Managed Objects for RS-232-like Hardware Devices"[6], combine to allow management of the traffic over an X.25 protocol stack.
RFC 1462	FYI on "What is the Internet?"
	Authors: E. Krol, E. Hoffman. Date: May 1993 Formats: txt pdf Also: FYI 0020 Status: INFORMATIONAL This FYI RFC answers the question, "What is the Internet?" and is produced by the User Services Working Group of the InternetEngineering Task Force (IETF). Containing a modified chapter from EdKrol's 1992 book, "The Whole Internet User's Guide and Catalog," the paper covers the Internet's definition, history, administration, protocols, financing, and current issues such as growth, commercialization, and privatization.
RFC 1463	FYI on Introducing the Internet-- A Short Bibliography of Introductory Internetworking Readings
	Authors: E. Hoffman, L. Jackson. Date: May 1993 Formats: txt pdf Also: FYI 0019 Status: INFORMATIONAL This bibliography offers a short list of recent information resources that will help the network novice become familiar with the Internet, including its associated networks, resources, protocols, and history.This FYI RFC includes references to free sources of information available on-line as well as traditional publications. A short section at the end includes information for accessing the on-line files. This FYI is intentionally brief so it can be easily used as a handout by user services personnel.
RFC 1464	Using the Domain Name System To Store Arbitrary String Attributes
	Authors: R. Rosenbaum. Date: May 1993 Formats: txt pdf Status: EXPERIMENTAL While the Domain Name System (DNS) [2,3] is generally used to store predefined types of information (e.g., addresses of hosts), it is possible to use it to store information that has not been previously classified. This paper describes a simple means to associate arbitrary string information (ASCII text) with attributes that have not been defined by the DNS. It uses DNS TXT resource records to store the information. It requires no change to current DNS implementations.
RFC 1465	Routing Coordination for X.400 MHS Services Within a Multi Protocol / Multi Network Environment Table Format V3 for Static Routing
	Authors: D. Eppenberger. Date: May 1993 Formats: txt pdf Status: EXPERIMENTAL This document proposes short term solutions for maintaining and distributing routing information and shows how messages can travel over different networks by using multi stack MTAs as relays. This memo defines an Experimental Protocol for the Internet community.
RFC 1466	Guidelines for Management of IP Address Space
	Authors: E. Gerich. Date: May 1993 Formats: txt pdf Obsoletes: RFC 1366 Obsoleted by: RFC 2050 Status: INFORMATIONAL This document has been reviewed by the Federal Engineering PlanningGroup (FEPG) on behalf of the Federal Networking Council (FNC), the co-chairs of the Intercontinental Engineering Planning Group (IEPG), and the Reseaux IP Europeens (RIPE). There was general consensus by those groups to support the recommendations proposed in this document for management of the IP address space.
RFC 1467	Status of CIDR Deployment in the Internet
	Authors: C. Topolcic. Date: August 1993 Formats: txt pdf Obsoletes: RFC 1367 Status: HISTORIC This document describes the current status of the development and deployment of CIDR technology into the Internet. This document replaces RFC 1367, which was a schedule for the deployment of IP address space management procedures to support route aggregation.Since all the milestones proposed in RFC 1367 except for the delivery and installation of CIDR software were met, it does not seem appropriate to issue an updated schedule. Rather, this document is intended to provide information about how this effort is proceeding, which may be of interest to the community.
RFC 1468	Japanese Character Encoding for Internet Messages
	Authors: J. Murai, M. Crispin, E. van der Poel. Date: June 1993 Formats: txt pdf Status: INFORMATIONAL This document describes the encoding used in electronic mail [RFC822] and network news [RFC1036] messages in several Japanese networks. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1469	IP Multicast over Token-Ring Local Area Networks
	Authors: T. Pusateri. Date: June 1993 Formats: txt pdf Status: HISTORIC This document specifies a method for the transmission of IP multicast datagrams over Token-Ring Local Area Networks. Although an interim solution has emerged and is currently being used, it is the intention of this document to specify a more efficient means of transmission using an assigned Token-Ring functional address.
RFC 1470	FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices
	Authors: R. Enger, J. Reynolds. Date: June 1993 Formats: txt pdf Obsoletes: RFC 1147 Also: FYI 0002 Status: INFORMATIONAL The goal of this FYI memo is to provide an update to FYI 2, RFC 1147[1], which provided practical information to site administrators and network managers. New and/or updated tools are listed in this RFC.Additonal descriptions are welcome, and should be sent to: noctools- entries@merit.edu.
RFC 1471	The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol
	Authors: F. Kastenholz. Date: June 1993 Formats: txt pdf Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it describes managed objects used for managing theLink Control Protocol and Link Quality Monitoring on subnetwork interfaces that use the family of Point-to-Point Protocols [8, 9, 10,11, & 12].
RFC 1472	The Definitions of Managed Objects for the Security Protocols of the Point-to-Point Protocol
	Authors: F. Kastenholz. Date: June 1993 Formats: txt pdf Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it describes managed objects used for managing theSecurity Protocols on subnetwork interfaces using the family ofPoint-to-Point Protocols [8, 9, 10, 11, & 12].
RFC 1473	The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol
	Authors: F. Kastenholz. Date: June 1993 Formats: txt pdf Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it describes managed objects used for managing the IPNetwork Control Protocol on subnetwork interfaces using the family ofPoint-to-Point Protocols [8, 9, 10, 11, & 12].
RFC 1474	The Definitions of Managed Objects for the Bridge Network Control Protocol of the Point-to-Point Protocol
	Authors: F. Kastenholz. Date: June 1993 Formats: txt pdf Status: HISTORIC This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it describes managed objects used for managing the bridge Network Control Protocol [10] on subnetwork interfaces using the family of Point-to-Point Protocols.
RFC 1475	TP/IX: The Next Internet
	Authors: R. Ullmann. Date: June 1993 Formats: txt pdf Status: EXPERIMENTAL The first version of this memo, describing a possible next generation of Internet protocols, was written by the present author in the summer and fall of 1989, and circulated informally, including to theIESG, in December 1989. A further informal note on the addressing, called "Toasternet Part II", was circulated on the IETF mail list during March of 1992.
RFC 1476	RAP: Internet Route Access Protocol
	Authors: R. Ullmann. Date: June 1993 Formats: txt pdf Status: EXPERIMENTAL This RFC describes an open distance vector routing protocol for use at all levels of the internet, from isolated LANs to the major routers of an international commercial network provider.
RFC 1477	IDPR as a Proposed Standard
	Authors: M. Steenstrup. Date: July 1993 Formats: txt pdf Status: INFORMATIONAL This document contains a discussion of inter-domain policy routing (IDPR), including an overview of functionality and a discussion of experiments. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1478	An Architecture for Inter-Domain Policy Routing
	Authors: M. Steenstrup. Date: June 1993 Formats: txt pdf Status: HISTORIC We present an architecture for inter-domain policy routing (IDPR).The objective of IDPR is to construct and maintain routes, between source and destination administrative domains, that provide user traffic with the requested services within the constraints stipulated for the domains transited. The IDPR architecture is designed to accommodate an internetwork containing tens of thousands of administrative domains with heterogeneous service requirements and restrictions.
RFC 1479	Inter-Domain Policy Routing Protocol Specification: Version 1
	Authors: M. Steenstrup. Date: July 1993 Formats: txt pdf Status: HISTORIC We present the set of protocols and procedures that constituteInter-Domain Policy Routing (IDPR). IDPR includes the virtual gateway protocol, the flooding protocol, the route server query protocol, the route generation procedure, the path control protocol, and the data message forwarding procedure.
RFC 1480	The US Domain
	Authors: A. Cooper, J. Postel. Date: June 1993 Formats: txt pdf Obsoletes: RFC 1386 Status: INFORMATIONAL This is a description of the US Top Level Domains on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1481	IAB Recommendation for an Intermediate Strategy to Address the Issue of Scaling
	Authors: C. Huitema. Date: July 1993 Formats: txt pdf Status: HISTORIC CIDR is proposed as an immediate term strategy to extend the life of the current 32 bit IP address space. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1482	Aggregation Support in the NSFNET Policy-Based Routing Database
	Authors: M. Knopper, S. Richardson. Date: June 1993 Formats: txt pdf Status: HISTORIC This document describes plans for support of route aggregation, as specified in the descriptions of Classless Inter-Domain Routing(CIDR) [1] and the BGP-4 protocol [2], by the NSFNET Backbone NetworkService. Mechanisms for exchange of route aggregates between the backbone service and regional/midlevel networks are specified.Additionally, the memo proposes the implementation of an AggregateRegistry which can be used by network service providers to share information about the use of aggregation. Finally, the operational impact of incorporating CIDR and aggregation is considered, including an analysis of how routing table size will be affected. This impact analysis will be used to modify the deployment plan, if necessary, to maximize operational stability.
RFC 1483	Multiprotocol Encapsulation over ATM Adaptation Layer 5
	Authors: Juha Heinanen. Date: July 1993 Formats: txt pdf Obsoleted by: RFC 2684 Status: PROPOSED STANDARD This memo describes two encapsulations methods for carrying network interconnect traffic over ATM AAL5. The first method allows multiplexing of multiple protocols over a single ATM virtual circuit whereas the second method assumes that each protocol is carried over a separate ATM virtual circuit.
RFC 1484	Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2))
	Authors: S. Hardcastle-Kille. Date: July 1993 Formats: txt pdf Obsoleted by: RFC 1781, RFC 3494 Status: HISTORIC The OSI Directory has user friendly naming as a goal. A simple minded usage of the directory does not achieve this. Two aspects not achieved are: o A user oriented notation o Guessability This proposal sets out some conventions for representing names in a friendly manner, and shows how this can be used to achieve really friendly naming. This then leads to a specification of a format for representing names, and to procedures to resolve them. This leads to a specification which allows directory names to be communicated between humans. The format in this specification is identical to that defined in [HK93], and it is intended that these specifications are compatible. Please send comments to the author or to the discussion group: <osi-ds@CS.UCL.AC.UK&rt;.
RFC 1485	A String Representation of Distinguished Names (OSI-DS 23 (v5))
	Authors: S. Hardcastle-Kille. Date: July 1993 Formats: txt pdf Obsoleted by: RFC 1779, RFC 3494 Status: HISTORIC The OSI Directory uses distinguished names as the primary keys to entries in the directory. Distinguished Names are encoded in ASN.1.When a distinguished name is communicated between to users not using a directory protocol (e.g., in a mail message), there is a need to have a user-oriented string representation of distinguished name. This specification defines a string format for representing names, which is designed to give a clean representation of commonly used names, whilst being able to represent any distinguished name. Please send comments to the author or to the discussion group <osi-ds@CS.UCL.AC.UK&rt;.
RFC 1486	An Experiment in Remote Printing
	Authors: M. Rose, C. Malamud. Date: July 1993 Formats: txt pdf Obsoleted by: RFC 1528, RFC 1529 Status: EXPERIMENTAL This memo describes a technique for "remote printing" using the Internet mail infrastructure. In particular, this memo focuses on the case in which remote printers are connected to the international telephone network. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.
RFC 1487	X.500 Lightweight Directory Access Protocol
	Authors: W. Yeong, T. Howes, S. Kille. Date: July 1993 Formats: txt pdf Obsoleted by: RFC 1777, RFC 3494 Status: HISTORIC The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of theDirectory Access Protocol (DAP). This protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive access to the Directory, and is intended to be a complement to the DAP itself. Key aspects of LDAP are: - Protocol elements are carried directly over TCP or other transport, bypassing much of the session/presentation overhead. - Many protocol data elements are encoding as ordinary strings (e.g.,Distinguished Names). - A lightweight BER encoding is used to encode all protocol elements.
RFC 1488	The X.500 String Representation of Standard Attribute Syntaxes
	Authors: T. Howes, S. Kille, W. Yeong, C. Robbins. Date: July 1993 Formats: txt pdf Obsoleted by: RFC 1778 Status: PROPOSED STANDARD The Lightweight Directory Access Protocol (LDAP) [9] requires that the contents of AttributeValue fields in protocol elements be octet strings. This document defines the requirements that must be satisfied by encoding rules used to render Directory attribute syntaxes into a form suitable for use in the LDAP, then goes on to define the encoding rules for the standard set of attribute syntaxes defined in [1,2] and [3].
RFC 1489	Registration of a Cyrillic Character Set
	Authors: A. Chernov. Date: July 1993 Formats: txt pdf Status: INFORMATIONAL Though the proposed character set "koi8-r" is not currently an international standard, there is very large user community (including Relcom Net) supporting it. Factually, "koi8-r" is de-facto standard for Unix and global network applications in the former Soviet Union. This is the reason the Society of Unix User Groups (SUUG) believes "koi8-r" should be registered. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1490	Multiprotocol Interconnect over Frame Relay
	Authors: T. Bradley, C. Brown, A. Malis. Date: July 1993 Formats: txt pdf Obsoletes: RFC 1294 Obsoleted by: RFC 2427 Status: DRAFT STANDARD This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. Additionally, it describes a simple fragmentation procedure for carrying large frames over a frame relay network with a smaller MTU. Systems with the ability to transfer both the encapsulation method described in this document, and others must have a priori knowledge of which virtual circuits will carry which encapsulation method and this encapsulation must only be used over virtual circuits that have been explicitly configured for its use.
RFC 1491	A Survey of Advanced Usages of X.500
	Authors: C. Weider, R. Wright. Date: July 1993 Formats: txt pdf Also: FYI 0021 Status: INFORMATIONAL This document is the result of a survey asking people to detail their advanced usages of X.500. It is intended to show how various organizations are using X.500 in ways which extend the view of X.500 as a "White Pages" service. This RFC is a product of the IntegratedDirectory Services Working Group of the Application and User ServicesAreas of the IETF.
RFC 1492	An Access Control Protocol, Sometimes Called TACACS
	Authors: C. Finseth. Date: July 1993 Formats: txt pdf Status: INFORMATIONAL This RFC documents the extended TACACS protocol use by the Cisco Systems terminal servers. This same protocol is used by the University of Minnesota's distributed authentication system. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1493	Definitions of Managed Objects for Bridges
	Authors: E. Decker, P. Langille, A. Rijsinghani, K. McCloghrie. Date: July 1993 Formats: txt pdf Obsoletes: RFC 1286 Obsoleted by: RFC 4188 Status: DRAFT STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets.In particular it defines objects for managing MAC bridges based on the IEEE 802.1D-1990 standard between Local Area Network (LAN) segments. Provisions are made for support of transparent bridging.Provisions are also made so that these objects apply to bridges connected by subnetworks other than LAN segments.
RFC 1494	Equivalences between 1988 X.400 and RFC-822 Message Bodies
	Authors: H. Alvestrand, S. Thompson. Date: August 1993 Formats: txt pdf Status: HISTORIC This document describes the content of the "IANA MHS/MIME Equivalence table", and defines the initial configuration of this table. Mappings for new MIME content-types and/or X.400 body part types should be registered with the IANA to minimize redundancy and promote interoperability. [STANDARDS-TRACK]
RFC 1495	Mapping between X.400 and RFC-822 Message Bodies
	Authors: H. Alvestrand, S. Kille, R. Miles, M. Rose, S. Thompson. Date: August 1993 Formats: txt pdf Obsoleted by: RFC 2156 Updates: RFC 1327 Status: PROPOSED STANDARD Since the introduction of X.400(84), there has been work ongoing for defining mappings between MHS and RFC-822. The most recent work in this area is RFC-1327 [3], which focuses primarily on translation of envelope and headers. This document is complimentary to RFC-1327 as it focuses on translation of the message body. [STANDARDS-TRACK]
RFC 1496	Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages
	Authors: H. Alvestrand, J. Romaguera, K. Jordan. Date: August 1993 Formats: txt pdf Status: HISTORIC This document describes how RFC-1328 must be modified in order to provide adequate support for the scenarios: It replaces chapter 6 of RFC-1328. The rest of RFC-1328 is NOT obsoleted. [STANDARDS-TRACK]
RFC 1497	BOOTP Vendor Information Extensions
	Authors: J. Reynolds. Date: August 1993 Formats: txt pdf Obsoletes: RFC 1395, RFC 1084, RFC 1048 Obsoleted by: RFC 1533 Updates: RFC 0951 Status: DRAFT STANDARD This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo. This memo is a status report on the vendor information extensions used in the Bootstrap Protocol (BOOTP).
RFC 1498	On the Naming and Binding of Network Destinations
	Authors: J. Saltzer. Date: August 1993 Formats: txt pdf Status: INFORMATIONAL This brief paper offers a perspective on the subject of names of destinations in data communication networks. It suggests two ideas:First, it is helpful to distinguish among four different kinds of objects that may be named as the destination of a packet in a network. Second, the operating system concept of binding is a useful way to describe the relations among the four kinds of objects. To illustrate the usefulness of this approach, the paper interprets some more subtle and confusing properties of two real-world network systems for naming destinations.
RFC 1499	Summary of 1400-1499
	Authors: J. Elliott. Date: January 1997 Formats: txt pdf Status: INFORMATIONAL
RFC 1500	Internet Official Protocol Standards
	Authors: J. Postel. Date: August 1993 Formats: txt pdf Obsoletes: RFC 1410 Obsoleted by: RFC 1540 Status: HISTORIC This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). [STANDARDS-TRACK]
RFC 1501	OS/2 User Group
	Authors: E. Brunsen. Date: August 1993 Formats: txt pdf Status: INFORMATIONAL Memo soliciting reactions to the proposal of a OS/2 User Group. This memo provides information for the Internet community. This memo does not specify an IAB standard of any kind.
RFC 1502	X.400 Use of Extended Character Sets
	Authors: H. Alvestrand. Date: August 1993 Formats: txt pdf Status: HISTORIC This RFC defines a suggested method of using "GeneralText" in order to harmonize as much as possible the usage of this body part. [STANDARDS- TRACK]
RFC 1503	Algorithms for Automating Administration in SNMPv2 Managers
	Authors: K. McCloghrie, M. Rose. Date: August 1993 Formats: txt pdf Status: INFORMATIONAL When a user invokes an SNMPv2 management application, it may be desirable for the user to specify the minimum amount of information necessary to establish and maintain SNMPv2 communications. This memo suggests an approach to achieve this goal. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1504	Appletalk Update-Based Routing Protocol: Enhanced Appletalk Routing
	Authors: A. Oppenheimer. Date: August 1993 Formats: txt pdf Status: INFORMATIONAL This document provides detailed information about the AppleTalk Update- based Routing Protocol (AURP) and wide area routing. AURP provides wide area routing enhancements to the AppleTalk routing protocols and is fully compatible with AppleTalk Phase 2. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1505	Encoding Header Field for Internet Messages
	Authors: A. Costanzo, D. Robinson, R. Ullmann. Date: August 1993 Formats: txt pdf Obsoletes: RFC 1154 Status: EXPERIMENTAL This document expands upon the elective experimental Encoding header field which permits the mailing of multi-part, multi-structured messages. It replaces RFC 1154 [1].
RFC 1506	A Tutorial on Gatewaying between X.400 and Internet Mail
	Authors: J. Houttuin. Date: August 1993 Formats: txt pdf Status: INFORMATIONAL This tutorial was produced especially to help new gateway managers find their way into the complicated subject of mail gatewaying according to RFC 1327. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1507	DASS - Distributed Authentication Security Service
	Authors: C. Kaufman. Date: September 1993 Formats: txt pdf Status: EXPERIMENTAL The goal of DASS is to provide authentication services in a distributed environment which are both more secure and easier to use than existing mechanisms. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.
RFC 1508	Generic Security Service Application Program Interface
	Authors: J. Linn. Date: September 1993 Formats: txt pdf Obsoleted by: RFC 2078 Status: PROPOSED STANDARD This Generic Security Service Application Program Interface (GSS-API) definition provides security services to callers in a generic fashion, supportable with a range of underlying mechanisms and technologies and hence allowing source-level portability of applications to different environments. This specification definesGSS-API services and primitives at a level independent of underlying mechanism and programming language environment, and is to be complemented by other, related specifications: documents defining specific parameter bindings for particular language environments documents defining token formats, protocols, and procedures to be implemented in order to realize GSS-API services atop particular security mechanisms
RFC 1509	Generic Security Service API : C-bindings
	Authors: J. Wray. Date: September 1993 Formats: txt pdf Obsoleted by: RFC 2744 Status: PROPOSED STANDARD This document specifies C language bindings for the Generic SecurityService Application Program Interface (GSS-API), which is described at a language-independent conceptual level in other documents. The Generic Security Service Application Programming Interface (GSS-API) provides security services to its callers, and is intended for implementation atop alternative underlying cryptographic mechanisms.Typically, GSS-API callers will be application protocols into which security enhancements are integrated through invocation of services provided by the GSS-API. The GSS-API allows a caller application to authenticate a principal identity associated with a peer application, to delegate rights to a peer, and to apply security services such as confidentiality and integrity on a per-message basis.
RFC 1510	The Kerberos Network Authentication Service (V5)
	Authors: J. Kohl, C. Neuman. Date: September 1993 Formats: txt pdf Obsoleted by: RFC 4120 Status: PROPOSED STANDARD This document gives an overview and specification of Version 5 of the protocol for the Kerberos network authentication system. Version 4, described elsewhere [1,2], is presently in production use at MIT'sProject Athena, and at other Internet sites.
RFC 1511	Common Authentication Technology Overview
	Authors: J. Linn. Date: September 1993 Formats: txt pdf Status: INFORMATIONAL This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1512	FDDI Management Information Base
	Authors: J. Case, A. Rijsinghani. Date: September 1993 Formats: txt pdf Updates: RFC 1285 Status: HISTORIC This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing devices which implement the FDDI based on the ANSI FDDI SMT 7.3 draft standard [8], which has been forwarded for publication by the X3T9.5 committee.
RFC 1513	Token Ring Extensions to the Remote Network Monitoring MIB
	Authors: S. Waldbusser. Date: September 1993 Formats: txt pdf Updates: RFC 1271 Status: HISTORIC This memo defines extensions to the Remote Network Monitoring MIB for managing 802.5 Token Ring networks. The Remote Network Monitoring MIB, RFC 1271, defines a framework for remote monitoring functions implemented on a network probe. That MIB defines objects broken down into nine functional groups. Some of those functional groups, the statistics and the history groups, have a view of the data-link layer that is specific to the media type and require specific objects to be defined for each media type. RFC 1271 defined those specific objects necessary for Ethernet. This companion memo defines those specific objects necessary for TokenRing LANs. In addition, this memo defines some additional monitoring functions specifically for Token Ring. These are defined in the Ring StationGroup, the Ring Station Order Group, the Ring Station ConfigurationGroup, and the Source Routing Statistics Group.
RFC 1514	Host Resources MIB
	Authors: P. Grillo, S. Waldbusser. Date: September 1993 Formats: txt pdf Obsoleted by: RFC 2790 Status: PROPOSED STANDARD This memo defines a MIB for use with managing host systems. The term"host" is construed to mean any computer that communicates with other similar computers attached to the internet and that is directly used by one or more human beings. Although this MIB does not necessarily apply to devices whose primary function is communications services(e.g., terminal servers, routers, bridges, monitoring equipment), such relevance is not explicitly precluded. This MIB instruments attributes common to all internet hosts including, for example, both personal computers and systems that run variants of Unix.
RFC 1515	Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
	Authors: D. McMaster, K. McCloghrie, S. Roberts. Date: September 1993 Formats: txt pdf Obsoleted by: RFC 3636 Status: PROPOSED STANDARD This document defines a portion of the Management Information Base(MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing IEEE 802.3Medium Attachment Units (MAUs).
RFC 1516	Definitions of Managed Objects for IEEE 802.3 Repeater Devices
	Authors: D. McMaster, K. McCloghrie. Date: September 1993 Formats: txt pdf Obsoletes: RFC 1368 Obsoleted by: RFC 2108 Status: DRAFT STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community.In particular, it defines objects for managing IEEE 802.3 10Mb/second baseband repeaters, sometimes referred to as "hubs."
RFC 1517	Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR)
	Authors: Internet Engineering Steering Group, R. Hinden. Date: September 1993 Formats: txt pdf Status: HISTORIC Classless Inter-Domain Routing (CIDR) defines a mechanism to slow the growth of routing tables and reduce the need to allocate new IP network numbers. [STANDARDS-TRACK]
RFC 1518	An Architecture for IP Address Allocation with CIDR
	Authors: Y. Rekhter, T. Li. Date: September 1993 Formats: txt pdf Status: HISTORIC This paper provides an architecture and a plan for allocating IP addresses in the Internet. This architecture and the plan are intended to play an important role in steering the Internet towards the Address Assignment and Aggregating Strategy. [STANDARDS-TRACK]
RFC 1519	Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy
	Authors: V. Fuller, T. Li, J. Yu, K. Varadhan. Date: September 1993 Formats: txt pdf Obsoletes: RFC 1338 Obsoleted by: RFC 4632 Status: PROPOSED STANDARD This memo discusses strategies for address assignment of the existingIP address space with a view to conserve the address space and stem the explosive growth of routing tables in default-route-free routers.
RFC 1520	Exchanging Routing Information Across Provider Boundaries in the CIDR Environment
	Authors: Y. Rekhter, C. Topolcic. Date: September 1993 Formats: txt pdf Status: HISTORIC The purpose of this document is twofold. First, it describes various alternatives for exchanging inter-domain routing information across domain boundaries, where one of the peering domain is CIDR-capable and another is not. Second, it addresses the implications of running CIDR- capable inter-domain routing protocols (e.g., BGP-4, IDRP) on intra- domain routing. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1521	MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies
	Authors: N. Borenstein, N. Freed. Date: September 1993 Formats: txt pdf ps Obsoletes: RFC 1341 Obsoleted by: RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049 Updated by: RFC 1590 Status: DRAFT STANDARD STD 11, RFC 822 defines a message representation protocol which specifies considerable detail about message headers, but which leaves the message content, or message body, as flat ASCII text. This document redefines the format of message bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information. This is based on earlier work documented in RFC 934 and STD 11, RFC 1049, but extends and revises that work. Because RFC 822 said so little about message bodies, this document is largely orthogonal to (rather than a revision of) RFC822. In particular, this document is designed to provide facilities to include multiple objects in a single message, to represent body text in character sets other than US-ASCII, to represent formatted multi- font text messages, to represent non-textual material such as images and audio fragments, and generally to facilitate later extensions defining new types of Internet mail for use by cooperating mail agents. This document does NOT extend Internet mail header fields to permit anything other than US-ASCII text data. Such extensions are the subject of a companion document [RFC-1522]. This document is a revision of RFC 1341. Significant differences from RFC 1341 are summarized in Appendix H.
RFC 1522	MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text
	Authors: K. Moore. Date: September 1993 Formats: txt pdf Obsoletes: RFC 1342 Obsoleted by: RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049 Status: DRAFT STANDARD This memo describes an extension to the message format defined in RFC1521 [1], to allow the representation of character sets other thanASCII in RFC 822 (STD 11) message headers. The extensions described were designed to be highly compatible with existing Internet mail handling software, and to be easily implemented in mail readers that support RFC 1521.
RFC 1523	The text/enriched MIME Content-type
	Authors: N. Borenstein. Date: September 1993 Formats: txt pdf Obsoleted by: RFC 1563, RFC 1896 Status: INFORMATIONAL MIME [RFC-1341, RFC-1521] defines a format and general framework for the representation of a wide variety of data types in Internet mail.This document defines one particular type of MIME data, the text/enriched type, a refinement of the "text/richtext" type defined in RFC 1341. The text/enriched MIME type is intended to facilitate the wider interoperation of simple enriched text across a wide variety of hardware and software platforms.
RFC 1524	A User Agent Configuration Mechanism For Multimedia Mail Format Information
	Authors: N. Borenstein. Date: September 1993 Formats: txt pdf Status: INFORMATIONAL This memo suggests a file format to be used to inform multiple mail reading user agent programs about the locally-installed facilities for handling mail in various formats. The mechanism is explicitly designed to work with mail systems based Internet mail as defined byRFC's 821 (STD 10), 822 (STD 11), 934, 1049 (STD 11), 1113, and theMultipurpose Internet Mail Extensions, known as MIME. However, with some extensions it could probably be made to work for X.400-based mail systems as well. The format and mechanism are proposed in a manner that is generally operating-system independent. However, certain implementation details will inevitably reflect operating system differences, some of which will have to be handled in a uniform manner for each operating system. This memo makes such situations explicit, and, in an appendix, suggests a standard behavior under the UNIX operating system.
RFC 1525	Definitions of Managed Objects for Source Routing Bridges
	Authors: E. Decker, K. McCloghrie, P. Langille, A. Rijsinghani. Date: September 1993 Formats: txt pdf Obsoletes: RFC 1286 Status: HISTORIC This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for managing source routing and source routing transparent bridges. These bridges are also required to implement relevant groups in the Bridge MIB. [STANDARDS-TRACK]
RFC 1526	Assignment of System Identifiers for TUBA/CLNP Hosts
	Authors: D. Piscitello. Date: September 1993 Formats: txt pdf Status: INFORMATIONAL This document describes conventions whereby the system identifier portion of an RFC 1237 style NSAP address may be guaranteed uniqueness within a routing domain for the purpose of autoconfiguration in TUBA/CLNP internets. The mechanism is extensible and can provide a basis for assigning system identifiers in a globally unique fashion.
RFC 1527	What Should We Plan Given the Dilemma of the Network?
	Authors: G. Cook. Date: September 1993 Formats: txt pdf Status: INFORMATIONAL Early last year, as the concluding effort of an 18 month appointment at the US Congress Office of Technology Assessment (OTA), I drafted a potential policy framework for Congressional action on the NationalResearch and Education Network (NREN). The Internet community needs to be asking what the most important policy issues facing the network are. And given agreement on any particular set of policy issues, the next thing we should be asking is, what would be some of the political choices that would follow forCongress to make? It is unfortunate that this was never officially done for or by theCongress by OTA. What we have as a result is network policy making being carried out now by the Science Subcommittee on the House side in consultation with a relatively small group of interested parties.The debate seems to be more focused on preserving turf than on any sweeping understanding of what the legislation is doing. That is unfortunate. In the hope that it may contain some useful ideas, I offer a shortened version of the suggested policy draft as information for the Internet community.
RFC 1528	Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures
	Authors: C. Malamud, M. Rose. Date: October 1993 Formats: txt pdf Obsoletes: RFC 1486 Status: EXPERIMENTAL This memo describes a technique for "remote printing" using the Internet mail infrastructure. In particular, this memo focuses on the case in which remote printers are connected to the international telephone network. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.
RFC 1529	Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Administrative Policies
	Authors: C. Malamud, M. Rose. Date: October 1993 Formats: txt pdf Obsoletes: RFC 1486 Status: INFORMATIONAL This document defines the administrative policies for the operation of remote printer facilities within the context of the tpc.int subdomain. The document describes different approaches to resource recovery for remote printer server sites and includes discussions of issues pertaining to auditing, security, and denial of access. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1530	Principles of Operation for the TPC.INT Subdomain: General Principles and Policy
	Authors: C. Malamud, M. Rose. Date: October 1993 Formats: txt pdf Status: INFORMATIONAL This document defines the initial principles of operation for the tpc.int subdomain, a collection of service listings accessible over the Internet infrastructure through an administered namespace contained within the Domain Name System [1,2]. This document is informational and applies only to those Internet sites that choose to register themselves within the tpc.int subdomain. The tpc.int subdomain is organized as a cooperative of the sites that provide access within the context of the subdomain.Policy for the subdomain is set by a board responsible to the cooperative. The primary purpose of the tpc.int subdomain is to provide transparent mapping between general-purpose computers on the Internet and special-purpose devices directly connected to the telephone network. Initially, a remote printing service is defined [3,4] which ties together G3-compatible facsimile devices on the telephone network with users of electronic mail in the Internet and associated message-handling domains connected to the Internet by application- layer gateways. It should be noted that remote printer gateways have long been technically feasible and have become an integral part of many individual networks. The tpc.int subdomain integrates individual sites into a common namespace, transforming remote printing from a single-site, value-added service into an integral transparent service in the global Internet.
RFC 1531	Dynamic Host Configuration Protocol
	Authors: R. Droms. Date: October 1993 Formats: txt pdf Obsoleted by: RFC 1541 Status: PROPOSED STANDARD The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network.DHCP is based on the Bootstrap Protocol (BOOTP) [7], adding the capability of automatic allocation of reusable network addresses and additional configuration options [19]. DHCP captures the behavior ofBOOTP relay agents [7, 23], and DHCP participants can interoperate with BOOTP participants [9].
RFC 1532	Clarifications and Extensions for the Bootstrap Protocol
	Authors: W. Wimer. Date: October 1993 Formats: txt pdf Obsoleted by: RFC 1542 Updates: RFC 0951 Status: PROPOSED STANDARD Some aspects of the BOOTP protocol were rather loosely defined in its original specification. In particular, only a general description was provided for the behavior of "BOOTP relay agents" (originally called BOOTP forwarding agents"). The client behavior description also suffered in certain ways. This memo attempts to clarify and strengthen the specification in these areas. In addition, new issues have arisen since the original specification was written. This memo also attempts to address some of these.
RFC 1533	DHCP Options and BOOTP Vendor Extensions
	Authors: S. Alexander, R. Droms. Date: October 1993 Formats: txt pdf Obsoletes: RFC 1497, RFC 1395, RFC 1084, RFC 1048 Obsoleted by: RFC 2132 Status: PROPOSED STANDARD The Dynamic Host Configuration Protocol (DHCP) [1] provides a framework for passing configuration information to hosts on a TCP/IP network. Configuration parameters and other control information are carried in tagged data items that are stored in the "options" field of the DHCP message. The data items themselves are also called"options." This document specifies the current set of DHCP options. This document will be periodically updated as new options are defined.Each superseding document will include the entire current list of valid options. All of the vendor information extensions defined in RFC 1497 [2] may be used as DHCP options. The definitions given in RFC 1497 are included in this document, which supersedes RFC 1497. All of theDHCP options defined in this document, except for those specific toDHCP as defined in section 9, may be used as BOOTP vendor information extensions.
RFC 1534	Interoperation Between DHCP and BOOTP
	Authors: R. Droms. Date: October 1993 Formats: txt pdf Status: DRAFT STANDARD DHCP provides a superset of the functions provided by BOOTP. This document describes the interactions between DHCP and BOOTP network participants.
RFC 1535	A Security Problem and Proposed Correction With Widely Deployed DNS Software
	Authors: E. Gavron. Date: October 1993 Formats: txt pdf Status: INFORMATIONAL This document discusses a flaw in some of the currently distributed name resolver clients. The flaw exposes a security weakness related to the search heuristic invoked by these same resolvers when users provide a partial domain name, and which is easy to exploit (although not by the masses). This document points out the flaw, a case in point, and a solution.
RFC 1536	Common DNS Implementation Errors and Suggested Fixes
	Authors: A. Kumar, J. Postel, C. Neuman, P. Danzig, S. Miller. Date: October 1993 Formats: txt pdf Status: INFORMATIONAL This memo describes common errors seen in DNS implementations and suggests some fixes. Where applicable, violations of recommendations from STD 13, RFC 1034 and STD 13, RFC 1035 are mentioned. The memo also describes, where relevant, the algorithms followed in BIND(versions 4.8.3 and 4.9 which the authors referred to) to serve as an example.
RFC 1537	Common DNS Data File Configuration Errors
	Authors: P. Beertema. Date: October 1993 Formats: txt pdf Obsoleted by: RFC 1912 Status: INFORMATIONAL This memo describes errors often found in DNS data files. It points out common mistakes system administrators tend to make and why they often go unnoticed for long periods of time.
RFC 1538	Advanced SNA/IP : A Simple SNA Transport Protocol
	Authors: W. Behl, B. Sterling, W. Teskey. Date: October 1993 Formats: txt pdf Status: INFORMATIONAL This RFC provides information for the Internet community about a method for establishing and maintaining SNA sessions over an IP internet. While the issues discussed may not be directly relevant to the research problems of the Internet, they may be interesting to a number of researchers and implementors. Any questions or comments relative to the contents of this RFC may be sent to the followingInternet address: snaip@mcdata.com.
RFC 1539	The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force
	Authors: G. Malkin. Date: October 1993 Formats: txt pdf Obsoletes: RFC 1391 Obsoleted by: RFC 1718 Status: INFORMATIONAL Over the last two years, the attendance at Internet Engineering TaskForce (IETF) Plenary meetings has grown phenomenally. Approximately38% of the attendees are new to the IETF at each meeting. About 33% of those go on to become regular attendees. When the meetings were smaller, it wasn't very difficult for a newcomer to get to know people and get into the swing of things. Today, however, a newcomer meets many more new people, some previously known only as the authors of Request For Comments (RFC) documents or thought provoking email messages. The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This will give them a warm, fuzzy feeling and enable them to make the meeting more productive for everyone. This FYI will also provide the mundane bits of information which everyone who attends an IETF meeting should know.
RFC 1540	Internet Official Protocol Standards
	Authors: J. Postel. Date: October 1993 Formats: txt pdf Obsoletes: RFC 1500 Obsoleted by: RFC 1600 Status: HISTORIC This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). [STANDARDS-TRACK]
RFC 1541	Dynamic Host Configuration Protocol
	Authors: R. Droms. Date: October 1993 Formats: txt pdf Obsoletes: RFC 1531 Obsoleted by: RFC 2131 Status: PROPOSED STANDARD The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network.DHCP is based on the Bootstrap Protocol (BOOTP) [7], adding the capability of automatic allocation of reusable network addresses and additional configuration options [19]. DHCP captures the behavior ofBOOTP relay agents [7, 23], and DHCP participants can interoperate with BOOTP participants [9]. Due to some errors introduced into RFC1531 in the editorial process, this memo is reissued as RFC 1541.
RFC 1542	Clarifications and Extensions for the Bootstrap Protocol
	Authors: W. Wimer. Date: October 1993 Formats: txt pdf Obsoletes: RFC 1532 Updates: RFC 0951 Status: DRAFT STANDARD Some aspects of the BOOTP protocol were rather loosely defined in its original specification. In particular, only a general description was provided for the behavior of "BOOTP relay agents" (originally called BOOTP forwarding agents"). The client behavior description also suffered in certain ways. This memo attempts to clarify and strengthen the specification in these areas. Due to some errors introduced into RFC 1532 in the editorial process, this memo is reissued as RFC 1542. In addition, new issues have arisen since the original specification was written. This memo also attempts to address some of these.
RFC 1543	Instructions to RFC Authors
	Authors: J. Postel. Date: October 1993 Formats: txt pdf Obsoletes: RFC 1111, RFC 0825 Obsoleted by: RFC 2223 Status: INFORMATIONAL This Request for Comments (RFC) provides information about the preparation of RFCs, and certain policies relating to the publication of RFCs. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1544	The Content-MD5 Header Field
	Authors: M. Rose. Date: November 1993 Formats: txt pdf Obsoleted by: RFC 1864 Status: PROPOSED STANDARD This memo specifies an optional header field, Content-MD5, for use with MIME-conformant messages.
RFC 1545	FTP Operation Over Big Address Records (FOOBAR)
	Authors: D. Piscitello. Date: November 1993 Formats: txt pdf Obsoleted by: RFC 1639 Status: EXPERIMENTAL This paper describes a convention for specifying longer addresses in the PORT command.
RFC 1546	Host Anycasting Service
	Authors: C. Partridge, T. Mendez, W. Milliken. Date: November 1993 Formats: txt pdf Status: INFORMATIONAL This RFC describes an internet anycasting service for IP. The primary purpose of this memo is to establish the semantics of an anycasting service within an IP internet. Insofar as is possible, this memo tries to be agnostic about how the service is actually provided by the internetwork. This memo describes an experimental service and does not propose a protocol. This memo is produced by the Internet Research Task Force (IRTF).
RFC 1547	Requirements for an Internet Standard Point-to-Point Protocol
	Authors: D. Perkins. Date: December 1993 Formats: txt pdf Status: INFORMATIONAL This document discusses the evaluation criteria for an InternetStandard Data Link Layer protocol to be used with point-to-point links. Although many industry standard protocols and ad hoc protocols already exist for the data link layer, none are both complete and sufficiently versatile to be accepted as an InternetStandard. In preparation to designing such a protocol, the features necessary to qualify a point-to-point protocol as an InternetStandard are discussed in detail. An analysis of the strengths and weaknesses of several existing protocols on the basis of these requirements demonstrates the failure of each to address key issues. Historical Note: This was the design requirements document datedJune 1989, which was followed for RFC-1134 through the present.It is now published for completeness and future guidance.
RFC 1548	The Point-to-Point Protocol (PPP)
	Authors: W. Simpson. Date: December 1993 Formats: txt pdf Obsoletes: RFC 1331 Obsoleted by: RFC 1661 Updated by: RFC 1570 Status: DRAFT STANDARD The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP is comprised of three main components: 1. A method for encapsulating multi-protocol datagrams. 2. A Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection. 3. A family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document defines the PPP organization and methodology, and thePPP encapsulation, together with an extensible option negotiation mechanism which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. The PPP Link Control Protocol (LCP) is described in terms of this mechanism. This document is the product of the Point-to-Point Protocol WorkingGroup of the Internet Engineering Task Force (IETF). Comments should be submitted to the ietf-ppp@ucdavis.edu mailing list.
RFC 1549	PPP in HDLC Framing
	Authors: W. Simpson, Ed.. Date: December 1993 Formats: txt pdf Obsoleted by: RFC 1662 Status: DRAFT STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method for transporting multi-protocol datagrams over point-to-point links. This document describes the use of HDLC for framing PPP encapsulated packets. This document is the product of the Point-to-Point ProtocolWorking Group of the Internet Engineering Task Force (IETF).Comments should be submitted to the ietf-ppp@ucdavis.edu mailing list.
RFC 1550	IP: Next Generation (IPng) White Paper Solicitation
	Authors: S. Bradner, A. Mankin. Date: December 1993 Formats: txt pdf Status: INFORMATIONAL This memo solicits white papers on topics related to the IPng requirements and selection criteria. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1551	Novell IPX Over Various WAN Media (IPXWAN)
	Authors: M. Allen. Date: December 1993 Formats: txt pdf Obsoleted by: RFC 1634 Status: INFORMATIONAL This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocolNovell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This document supercedes RFC 1362 and adds capability forUnnumbered RIP links, On-demand statically routed links and client to router connectivity.
RFC 1552	The PPP Internetworking Packet Exchange Control Protocol (IPXCP)
	Authors: W. Simpson. Date: December 1993 Formats: txt pdf Status: HISTORIC The Point-to-Point Protocol (PPP) [1] provides a method for transmitting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol, and proposes a family ofNetwork Control Protocols for establishing and configuring different network-layer protocols. The IPX protocol was originally used in Novell's NetWare products[3], and is now supported by numerous other vendors. This document defines the Network Control Protocol for establishing and configuring the IPX protocol over PPP. This memo is the product of the Point-to-Point Protocol Working Group of the IETF. Comments should be submitted to the ietf- ppp@ucdavis.edu mailing list.
RFC 1553	Compressing IPX Headers Over WAN Media (CIPX)
	Authors: S. Mathur, M. Lewis. Date: December 1993 Formats: txt pdf Status: HISTORIC This document describes a method for compressing the headers of IPX datagrams (CIPX). With this method, it is possible to significantly improve performance over lower speed wide area network (WAN) media. For normal IPX packet traffic, CIPX can provide a compression ratio of approximately 2:1 including both IPX header and data. This method can be used on various type of WAN media, including those supporting PPP and X.25. This memo ia a product of the Point-to-Point Protocol Extensions(PPPEXT) Working Group of the IETF. Comments should be sent to the authors and the ietf-ppp@ucdavis.edu mailing list.
RFC 1554	ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP
	Authors: M. Ohta, K. Handa. Date: December 1993 Formats: txt pdf Status: INFORMATIONAL This memo describes a text encoding scheme: "ISO-2022-JP-2", which is used experimentally for electronic mail [RFC822] and network news [RFC1036] messages in several Japanese networks. The encoding is a multilingual extension of "ISO-2022-JP", the existing encoding for Japanese [2022JP]. The encoding is supported by an Emacs based multilingual text editor: MULE [MULE]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1555	Hebrew Character Encoding for Internet Messages
	Authors: H. Nussbacher, Y. Bourvine. Date: December 1993 Formats: txt pdf Status: INFORMATIONAL This document describes the encoding used in electronic mail [RFC822] for transferring Hebrew. The standard devised makes use of MIME[RFC1521] and ISO-8859-8.
RFC 1556	Handling of Bi-directional Texts in MIME
	Authors: H. Nussbacher. Date: December 1993 Formats: txt pdf Status: INFORMATIONAL This document describes the format and syntax of the "direction" keyword to be used with bi-directional texts in MIME.
RFC 1557	Korean Character Encoding for Internet Messages
	Authors: U. Choi, K. Chon, H. Park. Date: December 1993 Formats: txt pdf Status: INFORMATIONAL This document describes the encoding method being used to represent Korean characters in both header and body part of the Internet mail messages [RFC822]. This encoding method was specified in 1991, and has since then been used. It has now widely being used in Korean IP networks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1558	A String Representation of LDAP Search Filters
	Authors: T. Howes. Date: December 1993 Formats: txt pdf Obsoleted by: RFC 1960 Status: INFORMATIONAL The Lightweight Directory Access Protocol (LDAP) [1] defines a network representation of a search filter transmitted to an LDAP server. Some applications may find it useful to have a common way of representing these search filters in a human-readable form. This document defines a human-readable string format for representing LDAP search filters.
RFC 1559	DECnet Phase IV MIB Extensions
	Authors: J. Saperia. Date: December 1993 Formats: txt pdf Obsoletes: RFC 1289 Status: DRAFT STANDARD This memo defines a set of DECnet Phase IV extensions that have been created for the Internet MIB. It reflects changes which are the result of operational experience based on RFC 1289. [STANDARDS-TRACK]
RFC 1560	The MultiProtocol Internet
	Authors: B. Leiner, Y. Rekhter. Date: December 1993 Formats: txt pdf Status: INFORMATIONAL This document was prepared by the authors on behalf of the InternetArchitecture Board (IAB). It is offered by the IAB to stimulate discussion. There has recently been considerable discussion on two topics:MultiProtocol approaches in the Internet and the selection of a next generation Internet Protocol. This document suggests a strawman position for goals and approaches for the IETF/IESG/IAB in these areas. It takes the view that these two topics are related, and proposes directions for the IETF/IESG/IAB to pursue. In particular, it recommends that the IETF/IESG/IAB should continue to be a force for consensus on a single protocol suite and internet layer protocol. The IETF/IESG/IAB should: - maintain its focus on the TCP/IP protocol suite, - work to select a single next-generation internet protocol and develop mechanisms to aid in transition from the current IPv4, and - continue to explore mechanisms to interoperate and share resources with other protocol suites within the Internet.
RFC 1561	Use of ISO CLNP in TUBA Environments
	Authors: D. Piscitello. Date: December 1993 Formats: txt pdf Status: EXPERIMENTAL This memo specifies a profile of the ISO/IEC 8473 Connectionless-modeNetwork Layer Protocol (CLNP, [1]) for use in conjunction with RFC1347, TCP/UDP over Bigger Addresses (TUBA, [2]). It describes the use of CLNP to provide the lower-level service expected byTransmission Control Protocol (TCP, [3]) and User Datagram Protocol(UDP, [4]). CLNP provides essentially the same datagram service asInternet Protocol (IP, [5]), but offers a means of conveying bigger network addresses (with additional structure, to aid routing). While the protocols offer nearly the same services, IP and CLNP are not identical. This document describes a means of preserving the semantics of IP information that is absent from CLNP while preserving consistency between the use of CLNP in Internet and OSI environments.This maximizes the use of already-deployed CLNP implementations.
RFC 1562	Naming Guidelines for the AARNet X.500 Directory Service
	Authors: G. Michaelson, M. Prior. Date: December 1993 Formats: txt pdf Status: INFORMATIONAL AARNet is a member network of the global Internet and participates in the global Internet X.500 based Directory Service. A number of RFC's have been issued that make recommendations that alter or supplement the OSI/ETU standards for X.500 [1]. In general, these RFCs will be followed by the AARNet Directory Service. However, in certain cases we wish to align ourselves with our national ISO body (StandardsAustralia) rather than the Internet where they conflict. In naming, we have chosen to align ourselves with Standards Australia and this document notes the difference in our approach to the Internet guidelines suggested in RFC 1384 [2].
RFC 1563	The text/enriched MIME Content-type
	Authors: N. Borenstein. Date: January 1994 Formats: txt pdf ps Obsoletes: RFC 1523 Obsoleted by: RFC 1896 Status: INFORMATIONAL MIME [RFC-1341, RFC-1521] defines a format and general framework for the representation of a wide variety of data types in Internet mail.This document defines one particular type of MIME data, the text/enriched type, a refinement of the "text/richtext" type defined in RFC 1341. The text/enriched MIME type is intended to facilitate the wider interoperation of simple enriched text across a wide variety of hardware and software platforms.
RFC 1564	DSA Metrics (OSI-DS 34 (v3))
	Authors: P. Barker, R. Hedberg. Date: January 1994 Formats: txt pdf Status: INFORMATIONAL This document defines a set of criteria by which a DSA implementation may be judged. Particular issues covered include conformance to standards; performance; demonstrated interoperability. The intention is that the replies to the questions posed provide a fairly full description of a DSA. Some of the questions will yield answers which are purely descriptive; others, however, are intended to elicit answers which give some measure of the utility of the DSA. The marks awarded for a DSA in each particular area should give a good indication of the DSA's capabilities, and its suitability for particular uses. Please send comments to the authors or to the discussion group<osi-ds@CS.UCL.AC.UK&rt;.
RFC 1565	Network Services Monitoring MIB
	Authors: S. Kille, N. Freed. Date: January 1994 Formats: txt pdf Obsoleted by: RFC 2248 Status: PROPOSED STANDARD This document defines a MIB which contains the elements common to the monitoring of any network service application. This information includes a table of all monitorable network service applications, a count of the associations (connections) to each application, and basic information about the parameters and status of each application-related association. [STANDARDS-TRACK]
RFC 1566	Mail Monitoring MIB
	Authors: S. Kille, N. Freed. Date: January 1994 Formats: txt pdf Obsoleted by: RFC 2249, RFC 2789 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, this memo extends the basic Network Services Monitoring MIB to allow monitoring of Message Transfer Agents (MTAs). It may also be used to monitor MTA components within gateways. [STANDARDS-TRACK]
RFC 1567	X.500 Directory Monitoring MIB
	Authors: G. Mansfield, S. Kille. Date: January 1994 Formats: txt pdf Obsoleted by: RFC 2605 Status: PROPOSED STANDARD This document defines a portion of the Management Information Base(MIB). It defines the MIB for monitoring Directory System Agents(DSA), a component of the OSI Directory. This MIB will be used in conjunction with the APPLICATION-MIB for monitoring DSAs.
RFC 1568	Simple Network Paging Protocol - Version 1(b)
	Authors: A. Gwinn. Date: January 1994 Formats: txt pdf Obsoleted by: RFC 1645 Status: INFORMATIONAL This RFC suggests a simple way for delivering both alphanumeric and numeric pages (one-way) to radio paging terminals. Gateways supporting this protocol, as well as SMTP, have been in use for several months in one nationwide paging firm. One other paging firm is in the process of adopting it. Earlier versions of this specification were reviewed by IESG members and the IETF's "822 Extensions" Working Group. They preferred an alternate strategy, as discussed under "Relationship to Other IETFWork", below.
RFC 1569	Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures
	Authors: M. Rose. Date: January 1994 Formats: txt pdf Obsoleted by: RFC 1703 Status: INFORMATIONAL This memo describes a technique for radio paging using the Internet mail infrastructure. In particular, this memo focuses on the case in which radio pagers are identified via the international telephone network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1570	PPP LCP Extensions
	Authors: W. Simpson, Ed.. Date: January 1994 Formats: txt pdf Updates: RFC 1548 Updated by: RFC 2484 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection. This document defines several additional LCP features which have been suggested over the past few years. This document is the product of the Point-to-Point Protocol WorkingGroup of the Internet Engineering Task Force (IETF). Comments should be submitted to the ietf-ppp@ucdavis.edu mailing list.
RFC 1571	Telnet Environment Option Interoperability Issues
	Authors: D. Borman. Date: January 1994 Formats: txt pdf Updates: RFC 1408 Status: INFORMATIONAL This document describes a method for allowing implementors to ensure that their implementation of the Environment option will be interoperable with as many other implementations as possible, by providing a set of heuristics that can be used to help identify which definitions for VAR and VALUE are being used by the other side of the connection. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1572	Telnet Environment Option
	Authors: S. Alexander, Ed.. Date: January 1994 Formats: txt pdf Status: PROPOSED STANDARD This document specifies a mechanism for passing environment information between a telnet client and server. Use of this mechanism enables a telnet user to propagate configuration information to a remote host when connecting. This document corrects some errors in [1].
RFC 1573	Evolution of the Interfaces Group of MIB-II
	Authors: K. McCloghrie, F. Kastenholz. Date: January 1994 Formats: txt pdf Obsoletes: RFC 1229 Obsoleted by: RFC 2233 Status: PROPOSED STANDARD 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 managed objects used for managing Network Interfaces. [STANARDS-TRACK]
RFC 1574	Essential Tools for the OSI Internet
	Authors: S. Hares, C. Wittbrodt. Date: February 1994 Formats: txt pdf Obsoletes: RFC 1139 Status: INFORMATIONAL This document specifies the following three necessary tools to debug problems in the deployment and maintenance of networks using ISO 8473(CLNP): - ping or OSI Echo function- traceroute function which uses the OSI Echo function- routing table dump function These CLNS tools are the basics required for hosts and routers forCLNS network support. It is intended that this document specify the most basic support level required for CLNS hosts and routers. To support some of the needed tools (ping and traceroute) this memo specifies the mechanism specified in RFC 1575 [3].
RFC 1575	An Echo Function for CLNP (ISO 8473)
	Authors: S. Hares, C. Wittbrodt. Date: February 1994 Formats: txt pdf Obsoletes: RFC 1139 Status: DRAFT STANDARD This memo defines an echo function for the connection-less network layer protocol. The mechanism that is mandated here is in the final process of being standardized by ISO as "Amendment X: Addition of anEcho function to ISO 8473" an integral part of Version 2 of ISO 8473.
RFC 1576	TN3270 Current Practices
	Authors: J. Penner. Date: January 1994 Formats: txt pdf Status: INFORMATIONAL This document describes the existing implementation of transferring3270 display terminal data using currently available telnet capabilities. The name traditionally associated with this implementation is TN3270. Information is provided to aid in the implementation of TN3270 servers as well as client terminal emulators. The following areas pertaining to TN3270 implementations are covered in this document: 1. the telnet options negotiated to transition from a NVT ASCII state to a TN3270 state ready to process incoming 3270 data stream commands 2. the method for sending and receiving 3270 data 3. the method of handling some special keys known as SYSREQ andATTN using current available telnet commands 4. the events that will transition a TN3270 session back to an NVT session
RFC 1577	Classical IP and ARP over ATM
	Authors: M. Laubach. Date: January 1994 Formats: txt pdf Obsoleted by: RFC 2225 Status: PROPOSED STANDARD This memo defines an initial application of classical IP and ARP in an Asynchronous Transfer Mode (ATM) network environment configured as a Logical IP Subnetwork (LIS) as described in Section 3. This memo does not preclude the subsequent development of ATM technology into areas other than a LIS; specifically, as single ATM networks grow to replace many ethernet local LAN segments and as these networks become globally connected, the application of IP and ARP will be treated differently. This memo considers only the application of ATM as a direct replacement for the "wires" and local LAN segments connectingIP end-stations ("members") and routers operating in the "classical"LAN-based paradigm. Issues raised by MAC level bridging and LAN emulation are beyond the scope of this paper. This memo introduces general ATM technology and nomenclature.Readers are encouraged to review the ATM Forum and ITU-TS (formerlyCCITT) references for more detailed information about ATM implementation agreements and standards.
RFC 1578	FYI on Questions and Answers - Answers to Commonly Asked "Primary and Secondary School Internet User" Questions
	Authors: J. Sellers. Date: February 1994 Formats: txt pdf Obsoleted by: RFC 1941 Status: INFORMATIONAL The goal of this FYI RFC, produced by the Internet School Networking(ISN) group in the User Services Area of the Internet EngineeringTask Force (IETF), is to document the questions most commonly asked about the Internet by those in the primary and secondary school community, and to provide pointers to sources which answer those questions. It is directed at educators, school media specialists, and school administrators who are recently connected to the Internet, who are accessing the Internet via dial-up or another means which is not a direct connection, or who are considering an Internet connection as a resource for their schools.
RFC 1579	Firewall-Friendly FTP
	Authors: S. Bellovin. Date: February 1994 Formats: txt pdf Status: INFORMATIONAL This memo describes a suggested change to the behavior of FTP client programs. No protocol modifications are required, though we outline some that might be useful.
RFC 1580	Guide to Network Resource Tools
	Authors: EARN Staff. Date: March 1994 Formats: txt pdf Also: FYI 0023 Status: INFORMATIONAL The purpose of this guide is to supply the basic information that anyone on the network needs to try out and begin using tools. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. [FYI 23]
RFC 1581	Protocol Analysis for Extensions to RIP to Support Demand Circuits
	Authors: G. Meyer. Date: February 1994 Formats: txt pdf Status: INFORMATIONAL As required by Routing Protocol Criteria [1], this report documents the key features of Routing over Demand Circuits on Wide AreaNetworks - RIP [2] and the current implementation experience.
RFC 1582	Extensions to RIP to Support Demand Circuits
	Authors: G. Meyer. Date: February 1994 Formats: txt pdf Status: PROPOSED STANDARD Running routing protocols on connection oriented Public DataNetworks, for example X.25 packet switched networks or ISDN, can be expensive if the standard form of periodic broadcasting of routing information is adhered to. The high cost arises because a connection has to all practical intents and purposes be kept open to every destination to which routing information is to be sent, whether or not it is being used to carry user data. Routing information may also fail to be propagated if the number of destinations to which the routing information is to be sent exceeds the number of channels available to the router on the Wide AreaNetwork (WAN). This memo defines a generalized modification which can be applied toBellman-Ford (or distance vector) algorithm information broadcasting protocols, for example IP RIP, Netware RIP or Netware SAP, which overcomes the limitations of the traditional methods described above. The routing protocols support a purely triggered update mechanism on demand circuits on WANs. The protocols run UNMODIFIED on LANs or fixed point-to-point links. Routing information is sent on the WAN when the routing database is modified by new routing information received from another interface.When this happens a (triggered) update is sent to a list of destinations on other WAN interfaces. Because routing protocols are datagram based they are not guaranteed to be received by the peer router on the WAN. An acknowledgement and retransmission mechanism is provided to ensure that routing updates are received. The WAN circuit manager advises the routing applications on the reachability and non-reachability of destinations on the WAN.
RFC 1583	OSPF Version 2
	Authors: J. Moy. Date: March 1994 Formats: txt pdf ps Obsoletes: RFC 1247 Obsoleted by: RFC 2178 Status: DRAFT STANDARD This memo documents version 2 of the OSPF protocol. OSPF is a link-state routing protocol. It is designed to be run internal to a single Autonomous System. Each OSPF router maintains an identical database describing the Autonomous System's topology. From this database, a routing table is calculated by constructing a shortest- path tree. OSPF recalculates routes quickly in the face of topological changes, utilizing a minimum of routing protocol traffic. OSPF provides support for equal-cost multipath. Separate routes can be calculated for each IP Type of Service. An area routing capability is provided, enabling an additional level of routing protection and a reduction in routing protocol traffic. In addition, all OSPF routing protocol exchanges are authenticated. OSPF Version 2 was originally documented in RFC 1247. The differences between RFC 1247 and this memo are explained in AppendixE. The differences consist of bug fixes and clarifications, and are backward-compatible in nature. Implementations of RFC 1247 and of this memo will interoperate. Please send comments to ospf@gated.cornell.edu.
RFC 1584	Multicast Extensions to OSPF
	Authors: J. Moy. Date: March 1994 Formats: txt pdf ps Status: HISTORIC This memo documents enhancements to the OSPF protocol enabling the routing of IP multicast datagrams. In this proposal, an IP multicast packet is routed based both on the packet's source and its multicast destination (commonly referred to as source/destination routing). As it is routed, the multicast packet follows a shortest path to each multicast destination. During packet forwarding, any commonality of paths is exploited; when multiple hosts belong to a single multicast group, a multicast packet will be replicated only when the paths to the separate hosts diverge. OSPF, a link-state routing protocol, provides a database describing the Autonomous System's topology. A new OSPF link state advertisement is added describing the location of multicast destinations. A multicast packet's path is then calculated by building a pruned shortest-path tree rooted at the packet's IP source. These trees are built on demand, and the results of the calculation are cached for use by subsequent packets. The multicast extensions are built on top of OSPF Version 2. The extensions have been implemented so that a multicast routing capability can be introduced piecemeal into an OSPF Version 2 routing domain. Some of the OSPF Version 2 routers may run the multicast extensions, while others may continue to be restricted to the forwarding of regular IP traffic (unicasts). Please send comments to mospf@gated.cornell.edu.
RFC 1585	MOSPF: Analysis and Experience
	Authors: J. Moy. Date: March 1994 Formats: txt pdf Status: INFORMATIONAL This memo documents how the MOSPF protocol satisfies the requirements imposed on Internet routing protocols by "Internet Engineering TaskForce internet routing protocol standardization criteria" ([RFC1264]). Please send comments to mospf@gated.cornell.edu.
RFC 1586	Guidelines for Running OSPF Over Frame Relay Networks
	Authors: O. deSouza, M. Rodrigues. Date: March 1994 Formats: txt pdf Status: INFORMATIONAL This memo specifies guidelines for implementors and users of the OpenShortest Path First (OSPF) routing protocol to bring about improvements in how the protocol runs over frame relay networks. We show how to configure frame relay interfaces in a way that obviates the "full-mesh" connectivity required by current OSPF implementations. This allows for simpler, more economic network designs. These guidelines do not require any protocol changes; they only provide recommendations for how OSPF should be implemented and configured to use frame relay networks efficiently.
RFC 1587	The OSPF NSSA Option
	Authors: R. Coltun, V. Fuller. Date: March 1994 Formats: txt pdf Obsoleted by: RFC 3101 Status: PROPOSED STANDARD This document describes a new optional type of OSPF area, somewhat humorously referred to as a "not-so-stubby" area (or NSSA). NSSAs are similar to the existing OSPF stub area configuration option but have the additional capability of importing AS external routes in a limited fashion. [STANDARDS-TRACK]
RFC 1588	White Pages Meeting Report
	Authors: J. Postel, C. Anderson. Date: February 1994 Formats: txt pdf Status: INFORMATIONAL This report describes the results of a meeting held at the November IETF (Internet Engineering Task Force) in Houston, TX, on November 2, 1993, to discuss the future of and approaches to a white pages directory services for the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1589	A Kernel Model for Precision Timekeeping
	Authors: D. Mills. Date: March 1994 Formats: txt pdf Status: INFORMATIONAL This memorandum describes an engineering model which implements a precision time-of-day function for a generic operating system. The model is based on the principles of disciplined oscillators and phase-lock loops (PLL) often found in the engineering literature. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1590	Media Type Registration Procedure
	Authors: J. Postel. Date: March 1994 Formats: txt pdf Obsoleted by: RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049 Updates: RFC 1521 Status: INFORMATIONAL Several protocols allow the use of data representing different"media" such as text, images, audio, and video, and within such media different encoding styles, such as (in video) jpeg, gif, ief, and tiff. The Multimedia Internet Message Extensions (MIME) protocol [1] defined several initial types of multimedia data objects, and a procedure for registering additional types with the Internet AssignedNumbers Authority (IANA). Several questions have been raised about the requirements and administrative procedure for registering MIME content-type and subtypes, and the use of these Media Types for other applications. This document addresses these issues and specifies a procedure for the registration of new Media Types (content- type/subtypes). It also generalizes the scope of use of these MediaTypes to make it appropriate to use the same registrations and specifications with other applications.
RFC 1591	Domain Name System Structure and Delegation
	Authors: J. Postel. Date: March 1994 Formats: txt pdf Status: INFORMATIONAL This memo provides some information on the structure of the names in the Domain Name System (DNS), specifically the top-level domain names; and on the administration of domains. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1592	Simple Network Management Protocol Distributed Protocol Interface Version 2.0
	Authors: B. Wijnen, G. Carpenter, K. Curran, A. Sehgal, G. Waters. Date: March 1994 Formats: txt pdf Obsoletes: RFC 1228 Status: EXPERIMENTAL This RFC describes version 2.0 of a protocol that International Business Machines Corporation (IBM) has been implementing in most of its SNMP agents to allow dynamic extension of supported MIBs. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1593	SNA APPN Node MIB
	Authors: W. McKenzie, J. Cheng. Date: March 1994 Formats: txt pdf Status: INFORMATIONAL This RFC describes IBM's SNMP support for SNA Advanced Peer-to-PeerNetworking (APPN) nodes.
RFC 1594	FYI on Questions and Answers - Answers to Commonly asked "New Internet User" Questions
	Authors: A. Marine, J. Reynolds, G. Malkin. Date: March 1994 Formats: txt pdf Obsoletes: RFC 1325 Obsoleted by: RFC 2664 Status: INFORMATIONAL This FYI RFC is one of two FYI's called, "Questions and Answers"(Q/A), produced by the User Services Working Group of the InternetEngineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet.
RFC 1595	Definitions of Managed Objects for the SONET/SDH Interface Type
	Authors: T. Brown, K. Tesink. Date: March 1994 Formats: txt pdf Obsoleted by: RFC 2558 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing Synchronous OpticalNetwork/Synchronous Digital Hierarchy (SONET/SDH) objects. This document is a companion document with Definitions of Managed Objects for the DS1/E1 and DS3/E3 Interface Types, RFC1406 [14] and RFC1407[13]. This memo specifies a MIB module in a manner that is both compliant to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 definitions.
RFC 1596	Definitions of Managed Objects for Frame Relay Service
	Authors: T. Brown, Ed.. Date: March 1994 Formats: txt pdf Obsoleted by: RFC 1604 Status: PROPOSED STANDARD This memo defines an extension to the Management Information Base(MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the FrameRelay Service.
RFC 1597	Address Allocation for Private Internets
	Authors: Y. Rekhter, B. Moskowitz, D. Karrenberg, G. de Groot. Date: March 1994 Formats: txt pdf Obsoleted by: RFC 1918 Status: INFORMATIONAL This RFC describes methods to preserve IP address space by not allocating globally unique IP addresses to hosts private to an enterprise while still permitting full network layer connectivity between all hosts inside an enterprise as well as between all public hosts of different enterprises. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1598	PPP in X.25
	Authors: W. Simpson. Date: March 1994 Formats: txt pdf Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method for transporting multi-protocol datagrams over point-to-point links.This document describes the use of X.25 for framing PPP encapsulated packets. This document is the product of the Point-to-Point Protocol WorkingGroup of the Internet Engineering Task Force (IETF). Comments should be submitted to the ietf-ppp@merit.edu mailing list.
RFC 1599	Summary of 1500-1599
	Authors: M. Kennedy. Date: January 1997 Formats: txt pdf Status: INFORMATIONAL
RFC 1600	Internet Official Protocol Standards
	Authors: J. Postel. Date: March 1994 Formats: txt pdf Obsoletes: RFC 1540 Obsoleted by: RFC 1610 Status: HISTORIC This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
RFC 1601	Charter of the Internet Architecture Board (IAB)
	Authors: C. Huitema. Date: March 1994 Formats: txt pdf Obsoletes: RFC 1358 Obsoleted by: RFC 2850 Status: INFORMATIONAL This memo documents the composition, selection, roles, and organization of the Internet Architecture Board and its subsidiary organizations.
RFC 1602	The Internet Standards Process -- Revision 2
	Authors: Internet Architecture Board, Internet Engineering Steering Group. Date: March 1994 Formats: txt pdf Obsoletes: RFC 1310 Obsoleted by: RFC 2026 Updated by: RFC 1871 Status: INFORMATIONAL This document is a revision of RFC 1310, which defined the official procedures for creating and documenting Internet Standards. This revision (revision 2) includes the following major changes: (a) The new management structure arising from the POISED WorkingGroup is reflected. These changes were agreed to by the IETF plenary and by the IAB and IESG in November 1992 and accepted by the ISOC Board of Trustees at their December 1992 meeting. (b) Prototype status is added to the non-standards track maturity levels (Section 2.4.1). (c) The Intellectual Property Rights section is completely revised, in accordance with legal advice. Section 5 of this document replaces Sections 5 and 6 of RFC-1310. The new section 5 has been reviewed by legal counsel to the Internet Society. (d) An appeals procedure is added (Section 3.6). (e) The wording of sections 1 and 1.2 has been changed to clarify the relationships that exist between the Internet Society and the IAB, the IESG, the IETF, and the Internet Standards process. (f) An Appendix B has been added, listing the contact points for theRFC editor, the IANA, the IESG, the IAB and the ISOC. The"future issues" are now listed in Appendix C.
RFC 1603	IETF Working Group Guidelines and Procedures
	Authors: E. Huizer, D. Crocker. Date: March 1994 Formats: txt pdf Obsoleted by: RFC 2418 Updated by: RFC 1871 Status: INFORMATIONAL The Internet Engineering Task Force (IETF) has responsibility for developing and reviewing specifications intended as InternetStandards. IETF activities are organized into working groups (WGs).This document describes the guidelines and procedures for formation and operation of IETF working groups. It describes the formal relationship between IETF participants WG and the InternetEngineering Steering Group (IESG). The basic duties of IETF participants, including WG Chair and IESG Area Directors are defined.
RFC 1604	Definitions of Managed Objects for Frame Relay Service
	Authors: T. Brown, Ed.. Date: March 1994 Formats: txt pdf Obsoletes: RFC 1596 Obsoleted by: RFC 2954 Status: PROPOSED STANDARD This memo defines an extension to the Management Information Base(MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the FrameRelay Service.
RFC 1605	SONET to Sonnet Translation
	Authors: W. Shakespeare. Date: April 1 1994 Formats: txt pdf Status: INFORMATIONAL Because Synchronous Optical Network (SONET) transmits data in frames of bytes, it is fairly easy to envision ways to compress SONET frames to yield higher bandwidth over a given fiber optic link. This memo describes a particular method, SONET Over Novel English Translation(SONNET).
RFC 1606	A Historical Perspective On The Usage Of IP Version 9
	Authors: J. Onions. Date: April 1 1994 Formats: txt pdf Status: INFORMATIONAL This paper reviews the usages of the old IP version protocol. It considers some of its successes and its failures.
RFC 1607	A VIEW FROM THE 21ST CENTURY
	Authors: V. Cerf. Date: April 1 1994 Formats: txt pdf Status: INFORMATIONAL This document is a composition of letters discussing a possible future. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1608	Representing IP Information in the X.500 Directory
	Authors: T. Johannsen, G. Mansfield, M. Kosters, S. Sataluri. Date: March 1994 Formats: txt pdf Status: EXPERIMENTAL This document describes the objects necessary to include information about IP networks and IP numbers in the X.500 Directory. It extends the work "Charting networks in the X.500 Directory" [1] where a general framework is presented for representing networks in theDirectory by applying it to IP networks. This application of theDirectory is intended to support the work of IP network assigning authorities, NICs, as well as other applications looking for a mapping of IP numbers to data of related networks. Furthermore,Autonomous Systems and related routing policy information can be represented in the Directory along with their relationship to networks and organizations.
RFC 1609	Charting Networks in the X.500 Directory
	Authors: G. Mansfield, T. Johannsen, M. Knopper. Date: March 1994 Formats: txt pdf Status: EXPERIMENTAL There is a need for a framework wherein the infrastructural and service related information about communication networks can be made accessible from all places and at all times in a reasonably efficient manner and with reasonable accuracy. This document presents a model in which a communication network with all its related details and descriptions can be represented in the X.500 Directory. Schemas of objects and their attributes which may be used for this purpose are presented. The model envisages physical objects and several logical abstractions of the physical objects.
RFC 1610	Internet Official Protocol Standards
	Authors: J. Postel. Date: July 1994 Formats: txt pdf Obsoletes: RFC 1600 Obsoleted by: RFC 1720 Status: HISTORIC This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
RFC 1611	DNS Server MIB Extensions
	Authors: R. Austein, J. Saperia. Date: May 1994 Formats: txt pdf Status: HISTORIC 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 extensions which instrument DNS name server functions. This memo was produced by the DNS working group. [STANDARDS-TRACK]
RFC 1612	DNS Resolver MIB Extensions
	Authors: R. Austein, J. Saperia. Date: May 1994 Formats: txt pdf Status: HISTORIC 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 extensions which instrument DNS resolver functions. This memo was produced by the DNS working group. [STANDARDS-TRACK]
RFC 1613	cisco Systems X.25 over TCP (XOT)
	Authors: J. Forster, G. Satz, G. Glick, R. Day. Date: May 1994 Formats: txt pdf Status: INFORMATIONAL This memo documents a method of sending X.25 packets over IP internets by encapsulating the X.25 Packet Level in TCP packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1614	Network Access to Multimedia Information
	Authors: C. Adie. Date: May 1994 Formats: txt pdf Status: INFORMATIONAL This report summarises the requirements of research and academic network users for network access to multimedia information. It does this by investigating some of the projects planned or currently underway in the community. Existing information systems such asGopher, WAIS and World-Wide Web are examined from the point of view of multimedia support, and some interesting hypermedia systems emerging from the research community are also studied. Relevant existing and developing standards in this area are discussed. The report identifies the gaps between the capabilities of currentlydeployed systems and the user requirements, and proposes further work centred on the World-Wide Web system to rectify this. The report is in some places very detailed, so it is preceded by an extended summary, which outlines the findings of the report.
RFC 1615	Migrating from X.400(84) to X.400(88)
	Authors: J. Houttuin, J. Craigie. Date: May 1994 Formats: txt pdf Status: INFORMATIONAL This document compares X.400(88) to X.400(84) and describes what problems can be anticipated in the migration, especially considering the migration from the existing X.400(84) infrastructure created by the COSINE MHS project to an X.400(88) infrastructure. It not only describes the technical complications, but also the effect the transition will have on the end users, especially concerning interworking between end users of the 84 and the 88 services.
RFC 1616	X.400(1988) for the Academic and Research Community in Europe
	Authors: RARE WG-MSG Task Force 88, E. Huizer, J. Romaguera, Eds.. Date: May 1994 Formats: txt pdf Status: INFORMATIONAL The report documents the results of a task force on X.400(1988) deployment of the RARE Mails and Messaging Work Group during the period from November 1992 until October 1993. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1617	Naming and Structuring Guidelines for X.500 Directory Pilots
	Authors: P. Barker, S. Kille, T. Lenggenhager. Date: May 1994 Formats: txt pdf Obsoletes: RFC 1384 Status: INFORMATIONAL Deployment of a Directory will benefit from following certain guidelines. This document defines a number of naming and structuring guidelines focused on White Pages usage. Alignment to these guidelines is recommended for directory pilots. The final version of this document will replace RFC 1384.
RFC 1618	PPP over ISDN
	Authors: W. Simpson. Date: May 1994 Formats: txt pdf Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method for transporting multi-protocol datagrams over point-to-point links.This document describes the use of PPP over Integrated ServicesDigital Network (ISDN) switched circuits. This document is the product of the Point-to-Point Protocol WorkingGroup of the Internet Engineering Task Force (IETF). Comments should be submitted to the ietf-ppp@merit.edu mailing list.
RFC 1619	PPP over SONET/SDH
	Authors: W. Simpson. Date: May 1994 Formats: txt pdf Obsoleted by: RFC 2615 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method for transporting multi-protocol datagrams over point-to-point links.This document describes the use of PPP over Synchronous OpticalNetwork (SONET) and Synchronous Digital Heirarchy (SDH) circuits. This document is the product of the Point-to-Point Protocol WorkingGroup of the Internet Engineering Task Force (IETF). Comments should be submitted to the ietf-ppp@merit.edu mailing list.
RFC 1620	Internet Architecture Extensions for Shared Media
	Authors: B. Braden, J. Postel, Y. Rekhter. Date: May 1994 Formats: txt pdf Status: INFORMATIONAL The original Internet architecture assumed that each network is labeled with a single IP network number. This assumption may be violated for shared media, including "large public data networks"(LPDNs). The architecture still works if this assumption is violated, but it does not have a means to prevent multiple host- router and router-router hops through the shared medium. This memo discusses alternative approaches to extending the Internet architecture to eliminate some or all unnecessary hops.
RFC 1621	Pip Near-term Architecture
	Authors: P. Francis. Date: May 1994 Formats: txt pdf Status: INFORMATIONAL Pip is an internet protocol intended as the replacement for IP version 4. Pip is a general purpose internet protocol, designed to evolve to all forseeable internet protocol requirements. This specification describes the routing and addressing architecture for near-term Pip deployment. We say near-term only because Pip is designed with evolution in mind, so other architectures are expected in the future. This document, however, makes no reference to such future architectures.
RFC 1622	Pip Header Processing
	Authors: P. Francis. Date: May 1994 Formats: txt pdf Status: INFORMATIONAL Pip is an internet protocol intended as the replacement for IP version 4. Pip is a general purpose internet protocol, designed to handle all forseeable internet protocol requirements. This specification defines the Pip header processing for Routers andHosts.
RFC 1623	Definitions of Managed Objects for the Ethernet-like Interface Types
	Authors: F. Kastenholz. Date: May 1994 Formats: txt pdf Obsoletes: RFC 1398 Obsoleted by: RFC 1643 Status: HISTORIC This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing ethernet-like objects. [STANDARDS-TRACK]
RFC 1624	Computation of the Internet Checksum via Incremental Update
	Authors: A. Rijsinghani, Ed.. Date: May 1994 Formats: txt pdf Updates: RFC 1141 Status: INFORMATIONAL This memo describes an updated technique for incremental computation of the standard Internet checksum. It updates the method described in RFC 1141.
RFC 1625	WAIS over Z39.50-1988
	Authors: M. St. Pierre, J. Fullton, K. Gamiel, J. Goldman, B. Kahle, J. Kunze, H. Morris, F. Schiettecatte. Date: June 1994 Formats: txt pdf Status: INFORMATIONAL The purpose of this memo is to initiate a discussion for a migration path of the WAIS technology from Z39.50-1988 Information Retrieval Service Definitions and Protocol Specification for Library Applications [1] to Z39.50-1992 [2] and then to Z39.50-1994 [3]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1626	Default IP MTU for use over ATM AAL5
	Authors: R. Atkinson. Date: May 1994 Formats: txt pdf Obsoleted by: RFC 2225 Status: PROPOSED STANDARD There are a number of good reasons to have a reasonably large default MTU value for IP over ATM AAL5. This paper presents the default IP MIU for use over ATM AAL5. [STANDARDS-TRACK]
RFC 1627	Network 10 Considered Harmful (Some Practices Shouldn't be Codified)
	Authors: E. Lear, E. Fair, D. Crocker, T. Kessler. Date: July 1994 Formats: txt pdf Obsoleted by: RFC 1918 Status: INFORMATIONAL This document restates the arguments for maintaining a unique address space. Concerns for Internet architecture and operations, as well as IETF procedure, are explored. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1628	UPS Management Information Base
	Authors: J. Case, Ed.. Date: May 1994 Formats: txt pdf Status: INFORMATIONAL This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing uninterruptible power supply (UPS) systems. [STANDARDS-TRACK]
RFC 1629	Guidelines for OSI NSAP Allocation in the Internet
	Authors: R. Colella, R. Callon, E. Gardner, Y. Rekhter. Date: May 1994 Formats: txt pdf Obsoletes: RFC 1237 Status: DRAFT STANDARD CLNP is currently being deployed in the Internet. This is useful to support OSI and DECnet(tm) traffic. In addition, CLNP has been proposed as a possible IPng candidate, to provide a long-term solution to IP address exhaustion. Required as part of the CLNP infrastructure are guidelines for network service access point (NSAP) address assignment. This paper provides guidelines for allocatingNSAP addresses in the Internet. The guidelines provided in this paper have been the basis for initial deployment of CLNP in the Internet, and have proven very valuable both as an aid to scaling of CLNP routing, and for address administration.
RFC 1630	Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web
	Authors: T. Berners-Lee. Date: June 1994 Formats: txt pdf Status: INFORMATIONAL This document defines the syntax used by the World-Wide Web initiative to encode the names and addresses of objects on the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1631	The IP Network Address Translator (NAT)
	Authors: K. Egevang, P. Francis. Date: May 1994 Formats: txt pdf Obsoleted by: RFC 3022 Status: INFORMATIONAL The two most compelling problems facing the IP Internet are IP address depletion and scaling in routing. Long-term and short-term solutions to these problems are being developed. The short-term solution is CIDR (Classless InterDomain Routing). The long-term solutions consist of various proposals for new internet protocols with larger addresses. It is possible that CIDR will not be adequate to maintain the IPInternet until the long-term solutions are in place. This memo proposes another short-term solution, address reuse, that complementsCIDR or even makes it unnecessary. The address reuse solution is to place Network Address Translators (NAT) at the borders of stub domains. Each NAT box has a table consisting of pairs of local IP addresses and globally unique addresses. The IP addresses inside the stub domain are not globally unique. They are reused in other domains, thus solving the address depletion problem. The globally unique IP addresses are assigned according to current CIDR address allocation schemes. CIDR solves the scaling problem. The main advantage of NAT is that it can be installed without changes to routers or hosts. This memo presents a preliminary design for NAT, and discusses its pros and cons.
RFC 1632	A Revised Catalog of Available X.500 Implementations
	Authors: A. Getchell, S. Sataluri, Eds.. Date: May 1994 Formats: txt pdf Obsoletes: RFC 1292 Obsoleted by: RFC 2116 Status: INFORMATIONAL This document is the result of a survey that gathered new or updated descriptions of currently available implementations of X.500, including commercial products and openly available offerings. This document is a revision of RFC 1292. We contacted each contributor inRFC 1292 and requested an update and published the survey template in several mailing lists and obtained new product descriptions. This document contains detailed description of twenty six (26) X.500 implementations - DSAs, DUAs, and DUA interfaces.
RFC 1633	Integrated Services in the Internet Architecture: an Overview
	Authors: R. Braden, D. Clark, S. Shenker. Date: June 1994 Formats: txt pdf ps Status: INFORMATIONAL This memo discusses a proposed extension to the Internet architecture and protocols to provide integrated services, i.e., to support real- time as well as the current non-real-time service of IP. This extension is necessary to meet the growing need for real-time service for a variety of new applications, including teleconferencing, remote seminars, telescience, and distributed simulation. This memo represents the direct product of recent work by Dave Clark,Scott Shenker, Lixia Zhang, Deborah Estrin, Sugih Jamin, JohnWroclawski, Shai Herzog, and Bob Braden, and indirectly draws upon the work of many others.
RFC 1634	Novell IPX Over Various WAN Media (IPXWAN)
	Authors: M. Allen. Date: May 1994 Formats: txt pdf Obsoletes: RFC 1551, RFC 1362 Status: INFORMATIONAL This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocolNovell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This document supercedes RFC 1362 and RFC 1551. The changes from RFC 1551 are to correct a problem in the wording when anRFC 1362 router talks to an RFC 1551 router and to allow numbers to be specified in a Router Name.
RFC 1635	How to Use Anonymous FTP
	Authors: P. Deutsch, A. Emtage, A. Marine. Date: May 1994 Formats: txt pdf Also: FYI 0024 Status: INFORMATIONAL This document provides information for the novice Internet user about using the File Transfer Protocol (FTP). It explains what FTP is, what anonymous FTP is, and what an anonymous FTP archive site is. It shows a sample anonymous FTP session. It also discusses common ways files are packaged for efficient storage and transmission.
RFC 1636	Report of IAB Workshop on Security in the Internet Architecture - February 8-10, 1994
	Authors: R. Braden, D. Clark, S. Crocker, C. Huitema. Date: June 1994 Formats: txt pdf Status: INFORMATIONAL This document is a report on an Internet architecture workshop, initiated by the IAB and held at USC Information Sciences Institute on February 8-10, 1994. This workshop generally focused on security issues in the Internet architecture. This document should be regarded as a set of working notes containing ideas about security that were developed by Internet experts in a broad spectrum of areas, including routing, mobility, realtime service, and provider requirements, as well as security. It contains some significant diversity of opinions on some important issues.This memo is offered as one input in the process of developing viable security mechanisms and procedures for the Internet.
RFC 1637	DNS NSAP Resource Records
	Authors: B. Manning, R. Colella. Date: June 1994 Formats: txt pdf Obsoletes: RFC 1348 Obsoleted by: RFC 1706 Status: EXPERIMENTAL The Internet is moving towards the deployment of an OSI lower layers infrastructure. This infrastructure comprises the connectionless network protocol (CLNP) and supporting routing protocols. Also required as part of this infrastructure is support in the Domain NameSystem (DNS) for mapping between names and NSAP addresses. This document defines the format of one new Resource Record (RR) for the DNS for domain name-to-NSAP mapping. The RR may be used with anyNSAP address format. This document supercedes RFC 1348. NSAP-to-name translation is accomplished through use of the PTR RR(see STD 13, RFC 1035 for a description of the PTR RR). This paper describes how PTR RRs are used to support this translation.
RFC 1638	PPP Bridging Control Protocol (BCP)
	Authors: F. Baker, R. Bowen. Date: June 1994 Formats: txt pdf Obsoletes: RFC 1220 Obsoleted by: RFC 2878 Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) [6] provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol, and proposes a family ofNetwork Control Protocols for establishing and configuring different network-layer protocols. This document defines the Network Control Protocol for establishing and configuring Remote Bridging for PPP links.
RFC 1639	FTP Operation Over Big Address Records (FOOBAR)
	Authors: D. Piscitello. Date: June 1994 Formats: txt pdf Obsoletes: RFC 1545 Status: EXPERIMENTAL This paper describes a convention for specifying address families other than the default Internet address family in FTP commands and replies.
RFC 1640	The Process for Organization of Internet Standards Working Group (POISED)
	Authors: S. Crocker. Date: June 1994 Formats: txt pdf Status: INFORMATIONAL This report, originally prepared in January 1993 provides a summary of the POISED WG, starting from the events leading to the formation of the WG to the end of 1992. Necessarily, this synopsis represents my own perception, particularly for the "prehistory" period. Quite a few people hold strong views about both the overall sequence and specific events. My intent here is to convey as neutral a point of view as possible.
RFC 1641	Using Unicode with MIME
	Authors: D. Goldsmith, M. Davis. Date: July 1994 Formats: txt pdf ps Status: EXPERIMENTAL The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993(E) jointly define a 16 bit character set (hereafter referred to asUnicode) which encompasses most of the world's writing systems.However, Internet mail (STD 11, RFC 822) currently supports only 7- bit US ASCII as a character set. MIME (RFC 1521 and RFC 1522) extendsInternet mail to support different media types and character sets, and thus could support Unicode in mail messages. MIME neither definesUnicode as a permitted character set nor specifies how it would be encoded, although it does provide for the registration of additional character sets over time. This document specifies the usage of Unicode within MIME.
RFC 1642	UTF-7 - A Mail-Safe Transformation Format of Unicode
	Authors: D. Goldsmith, M. Davis. Date: July 1994 Formats: txt pdf ps Obsoleted by: RFC 2152 Status: EXPERIMENTAL The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993(E) jointly define a 16 bit character set (hereafter referred to asUnicode) which encompasses most of the world's writing systems.However, Internet mail (STD 11, RFC 822) currently supports only 7- bit US ASCII as a character set. MIME (RFC 1521 and RFC 1522) extendsInternet mail to support different media types and character sets, and thus could support Unicode in mail messages. MIME neither definesUnicode as a permitted character set nor specifies how it would be encoded, although it does provide for the registration of additional character sets over time. This document describes a new transformation format of Unicode that contains only 7-bit ASCII characters and is intended to be readable by humans in the limiting case that the document consists of characters from the US-ASCII repertoire. It also specifies how this transformation format is used in the context of RFC 1521, RFC 1522, and the document "Using Unicode with MIME".
RFC 1643	Definitions of Managed Objects for the Ethernet-like Interface Types
	Authors: F. Kastenholz. Date: July 1994 Formats: txt pdf Obsoletes: RFC 1623 Obsoleted by: RFC 3638 Status: HISTORIC This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing ethernet-like objects. [STANDARDS-TRACK]
RFC 1644	T/TCP -- TCP Extensions for Transactions Functional Specification
	Authors: R. Braden. Date: July 1994 Formats: txt pdf Obsoleted by: RFC 6247 Updates: RFC 1379 Status: HISTORIC This memo specifies T/TCP, an experimental TCP extension for efficient transaction-oriented (request/response) service. This backwards-compatible extension could fill the gap between the current connection-oriented TCP and the datagram-based UDP. This work was supported in part by the National Science Foundation under Grant Number NCR-8922231.
RFC 1645	Simple Network Paging Protocol - Version 2
	Authors: A. Gwinn. Date: July 1994 Formats: txt pdf Obsoletes: RFC 1568 Obsoleted by: RFC 1861 Status: INFORMATIONAL This RFC suggests a simple way for delivering both alphanumeric and numeric pages (one-way) to radio paging terminals. Gateways supporting this protocol, as well as SMTP, have been in use for several months for nationwide paging and messaging. In addition, email filters and SNPP client software for Unix and Windows are available at no cost. Please contact the author for more information. Earlier versions of this specification were reviewed by IESG members and the "822 Extensions" Working Group. They preferred an alternate strategy, as discussed under "Relationship to Other IETF Work", below.
RFC 1646	TN3270 Extensions for LUname and Printer Selection
	Authors: C. Graves, T. Butts, M. Angel. Date: July 1994 Formats: txt pdf Status: INFORMATIONAL This document describes protocol extensions to TN3270. There are two extensions outlined in this document. The first defines a way by which a TN3270 client can request a specific device (LUname) from aTN3270 server. The second extension specifies how a TN3270 printer device can be requested by a TN3270 client and the manner in which the 3270 printer status information can be sent to the TN3270 server.Discussions and suggestions for improvements to these enhancements should be sent to the TN3270E Working Group mailing listTN3270E@list.nih.gov . These extensions will be called TN3287 in this document. This information is being provided to members of theInternet community that want to support the 3287 data stream within the TELNET protocol.
RFC 1647	TN3270 Enhancements
	Authors: B. Kelly. Date: July 1994 Formats: txt pdf Obsoleted by: RFC 2355 Status: PROPOSED STANDARD This document describes a protocol that more fully supports 3270 devices than do the existing tn3270 practices. Specifically, it defines a method of emulating both the terminal and printer members of the 3270 family of devices via Telnet; it provides for the ability of a Telnet client to request that it be assigned a specific device- name (also referred to as "LU name" or "network name"); finally, it adds support for a variety of functions such as the ATTN key, theSYSREQ key, and SNA response handling. This protocol would be negotiated and implemented under a new TelnetOption and would be unrelated to the Telnet 3270 Regime Option as defined in RFC 1041 [1].
RFC 1648	Postmaster Convention for X.400 Operations
	Authors: A. Cargille. Date: July 1994 Formats: txt pdf Status: HISTORIC Both STD 11, RFC 822 [1] and STD 3, RFC 1123 [2] (Host Requirements) require that the email address "postmaster" be supported at all hosts. This paper extends this concept to X.400 mail domains which have registered RFC 1327 mapping rules, and which therefore appear to have normal RFC822-style addresses.
RFC 1649	Operational Requirements for X.400 Management Domains in the GO-MHS Community
	Authors: R. Hagens, A. Hansen. Date: July 1994 Formats: txt pdf Status: INFORMATIONAL The goal of this document is to unite regionally operated X.400 services on the various continents into one GO-MHS Community (as seen from an end-user's point of view). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1650	Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2
	Authors: F. Kastenholz. Date: August 1994 Formats: txt pdf Obsoleted by: RFC 2358 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing ethernet-like objects. [STANDARDS-TRACK]
RFC 1651	SMTP Service Extensions
	Authors: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker. Date: July 1994 Formats: txt pdf Obsoletes: RFC 1425 Obsoleted by: RFC 1869 Status: DRAFT STANDARD This memo defines a framework for extending the SMTP service by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports. [STANDARDS-TRACK]
RFC 1652	SMTP Service Extension for 8bit-MIMEtransport
	Authors: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker. Date: July 1994 Formats: txt pdf Obsoletes: RFC 1426 Obsoleted by: RFC 6152 Status: DRAFT STANDARD This memo defines an extension to the SMTP service whereby an SMTP content body consisting of text containing octets outside of the US-ASCII octet range (hex 00-7F) may be relayed using SMTP.
RFC 1653	SMTP Service Extension for Message Size Declaration
	Authors: J. Klensin, N. Freed, K. Moore. Date: July 1994 Formats: txt pdf Obsoletes: RFC 1427 Obsoleted by: RFC 1870 Status: DRAFT STANDARD This memo defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to decline to accept a message (perhaps temporarily) based on the client's estimate of the message size.
RFC 1654	A Border Gateway Protocol 4 (BGP-4)
	Authors: Y. Rekhter, T. Li, Eds.. Date: July 1994 Formats: txt pdf Obsoleted by: RFC 1771 Status: PROPOSED STANDARD This document defines an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK]
RFC 1655	Application of the Border Gateway Protocol in the Internet
	Authors: Y. Rekhter, P. Gross, Eds.. Date: July 1994 Formats: txt pdf Obsoletes: RFC 1268 Obsoleted by: RFC 1772 Status: PROPOSED STANDARD This document, together with its companion document, "A BorderGateway Protocol 4 (BGP-4)", define an inter-autonomous system routing protocol for the Internet. "A Border Gateway Protocol 4(BGP-4)" defines the BGP protocol specification, and this document describes the usage of the BGP in the Internet. Information about the progress of BGP can be monitored and/or reported on the BGP mailing list (bgp@ans.net).
RFC 1656	BGP-4 Protocol Document Roadmap and Implementation Experience
	Authors: P. Traina. Date: July 1994 Formats: txt pdf Obsoleted by: RFC 1773 Status: INFORMATIONAL Border Gateway Protocol v4 (BGP-4) [1] is an inter-Autonomous System routing protocol. It is built on experience gained with BGP as defined in RFC-1267 [2] and BGP usage in the connected Internet as described in RFC-1268 [3]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1657	Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2
	Authors: S. Willis, J. Burruss, J. Chu, Ed.. Date: July 1994 Formats: txt pdf Obsoleted by: RFC 4273 Status: DRAFT STANDARD 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 managed objects used for managing the Border Gateway Protocol Version 4 or lower [1, 2]. [STANDARDS-TRACK]
RFC 1658	Definitions of Managed Objects for Character Stream Devices using SMIv2
	Authors: B. Stewart. Date: July 1994 Formats: txt pdf Obsoletes: RFC 1316 Status: DRAFT STANDARD This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for the management of character stream devices. [STANDARDS-TRACK]
RFC 1659	Definitions of Managed Objects for RS-232-like Hardware Devices using SMIv2
	Authors: B. Stewart. Date: July 1994 Formats: txt pdf Obsoletes: RFC 1317 Status: DRAFT STANDARD This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for the management of RS-232-like devices. [STANDARDS-TRACK]
RFC 1660	Definitions of Managed Objects for Parallel-printer-like Hardware Devices using SMIv2
	Authors: B. Stewart. Date: July 1994 Formats: txt pdf Obsoletes: RFC 1318 Status: DRAFT STANDARD This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for the management of Parallel-printer- like devices. [STANDARDS-TRACK]
RFC 1661	The Point-to-Point Protocol (PPP)
	Authors: W. Simpson, Ed.. Date: July 1994 Formats: txt pdf Obsoletes: RFC 1548 Updated by: RFC 2153 Also: STD 0051 Status: STANDARD The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP is comprised of three main components: 1. A method for encapsulating multi-protocol datagrams. 2. A Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection. 3. A family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document defines the PPP organization and methodology, and thePPP encapsulation, together with an extensible option negotiation mechanism which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. The PPP Link Control Protocol (LCP) is described in terms of this mechanism.
RFC 1662	PPP in HDLC-like Framing
	Authors: W. Simpson, Ed.. Date: July 1994 Formats: txt pdf Obsoletes: RFC 1549 Also: STD 0051 Status: STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method for transporting multi-protocol datagrams over point-to-point links. This document describes the use of HDLC-like framing for PPP encapsulated packets.
RFC 1663	PPP Reliable Transmission
	Authors: D. Rand. Date: July 1994 Formats: txt pdf Status: PROPOSED STANDARD The Point-to-Point Protocol (PPP) [1] provides a standard method for transporting multi-protocol datagrams over point-to-point links. This document defines a method for negotiating and using Numbered-Mode, as defined by ISO 7776 [2], to provide a reliable serial link. This document is the product of the Point-to-Point Protocol WorkingGroup of the Internet Engineering Task Force (IETF). Comments should be submitted to the ietf-ppp@ucdavis.edu mailing list.
RFC 1664	Using the Internet DNS to Distribute RFC1327 Mail Address Mapping Tables
	Authors: C. Allocchio, A. Bonito, B. Cole, S. Giordano, R. Hagens. Date: August 1994 Formats: txt pdf Obsoleted by: RFC 2163 Status: EXPERIMENTAL This memo defines how to store in the Internet Domain Name System the mapping information needed by e-mail gateways and other tools to mapRFC822 domain names into X.400 O/R names and vice versa. Mapping information can be managed in a distributed rather than a centralised way. Gateways located on Internet hosts can retrieve the mapping information querying the DNS instead of having fixed tables which need to be centrally updated and distributed. This memo is a joint effort of X400 operation working group (x400ops) and RARE Mail andMessaging working group (WG-MSG).
RFC 1665	Definitions of Managed Objects for SNA NAUs using SMIv2
	Authors: Z. Kielczewski, D. Kostick, K. Shih, Eds.. Date: July 1994 Formats: txt pdf Obsoleted by: RFC 1666 Status: PROPOSED STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing the configuration, monitoring and control of Physical Units (PUs) and Logical Units (LUs) in an SNA environment. [STANDARDS-TRACK]
RFC 1666	Definitions of Managed Objects for SNA NAUs using SMIv2
	Authors: Z. Kielczewski, D. Kostick, K. Shih, Eds.. Date: August 1994 Formats: txt pdf Obsoletes: RFC 1665 Status: HISTORIC This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing the configuration, monitoring and control of Physical Units (PUs) and Logical Units (LUs) in an SNA environment. [STANDARDS-TRACK]
RFC 1667	Modeling and Simulation Requirements for IPng
	Authors: S. Symington, D. Wood, M. Pullen. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1668	Unified Routing Requirements for IPng
	Authors: D. Estrin, T. Li, Y. Rekhter. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1669	Market Viability as a IPng Criteria
	Authors: J. Curran. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1670	Input to IPng Engineering Considerations
	Authors: D. Heagerty. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1671	IPng White Paper on Transition and Other Considerations
	Authors: B. Carpenter. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1672	Accounting Requirements for IPng
	Authors: N. Brownlee. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1673	Electric Power Research Institute Comments on IPng
	Authors: R. Skelton. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1674	A Cellular Industry View of IPng
	Authors: M. Taylor. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This memo is a response to RFC 1550, "IP: Next Generation (IPng)White Paper Solicitation". The statements in this paper are intended as input to the technical discussions within IETF, and do not represent any endorsement or commitment on the part of the cellular industry, the Cellular Digital Packet Data (CDPD) consortium of service providers or any of its constituent companies.
RFC 1675	Security Concerns for IPng
	Authors: S. Bellovin. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1676	INFN Requirements for an IPng
	Authors: A. Ghiselli, D. Salomoni, C. Vistoli. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This white paper is sent by INFN network team, the Italian NationalInstitute for nuclear physics, whose network, named INFNet, is a nationwide network founded to provide the access to existing national and international HEP laboratory and to facilitate communications between the researchers. With this paper we would like to emphasize the key points that we would to consider if charged with IPng plan.We do not really expect to add original items to the selection, but we think that it could be useful to submit the opinions and ideas that come from our network experience.
RFC 1677	Tactical Radio Frequency Communication Requirements for IPng
	Authors: B. Adamson. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1678	IPng Requirements of Large Corporate Networks
	Authors: E. Britton, J. Tavs. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list. This draft summarizes some of the requirements of large corporate networks for the next generation of the Internet protcol suite.
RFC 1679	HPN Working Group Input to the IPng Requirements Solicitation
	Authors: D. Green, P. Irey, D. Marlow, K. O'Donoghue. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1680	IPng Support for ATM Services
	Authors: C. Brazdziunas. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1681	On Many Addresses per Host
	Authors: S. Bellovin. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1682	IPng BSD Host Implementation Analysis
	Authors: J. Bound. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1683	Multiprotocol Interoperability In IPng
	Authors: R. Clark, M. Ammar, K. Calvert. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1684	Introduction to White Pages Services based on X.500
	Authors: P. Jurg. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document aims at organisations who are using local and global electronic communication on a day to day basis and for whom using an electronic White Pages Service is therefore indispensable. The document provides an introduction to the international ITU-T(formerly CCITT) X.500 and ISO 9594 standard, which is particularly suited for providing an integrated local and global electronic WhitePages Service. In addition a short overview of the experience gained from theParadise X.500 pilot is given. References to more detailed information are included. The document should be useful for managers of the above mentioned organisations who need to get the necessary executive commitment for making the address information of their organisation available by means of X.500.
RFC 1685	Writing X.400 O/R Names
	Authors: H. Alvestrand. Date: August 1994 Formats: txt pdf Also: RTR_0012 Status: INFORMATIONAL There is a need for human beings who use X.400 systems to be able to write down O/R names in a uniform way. This memo is a discussion of this topic. This memo provides information for the Internet Community. It does not specify an Internet Standard of any kind.
RFC 1686	IPng Requirements: A Cable Television Industry Viewpoint
	Authors: M. Vecchi. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. The statements in this paper are intended as input to the technical discussions within IETF, and do not represent any endorsement or commitment on the part of the cable television industry or any of its companies. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1687	A Large Corporate User's View of IPng
	Authors: E. Fleischman. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IETF IPng area in response to RFC1550. Publication of this document does not imply acceptance by theIPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.
RFC 1688	IPng Mobility Considerations
	Authors: W. Simpson. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This document was submitted to the IPng Area in response to RFC 1550.Publication of this document does not imply acceptance by the IPngArea of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list. This RFC specifies criteria related to mobility for consideration in design and selection of the Next Generation of IP.
RFC 1689	A Status Report on Networked Information Retrieval: Tools and Groups
	Authors: J. Foster, Ed.. Date: August 1994 Formats: txt pdf Also: FYI 0025 Status: INFORMATIONAL The purpose of this report is to increase the awareness of NetworkedInformation Retrieval by bringing together in one place information about the various networked information retrieval tools, their developers, interested organisations, and other activities that relate to the production, dissemination, and support of NIR tools.NIR Tools covered include Archie, WAIS, gopher and World Wide Web.
RFC 1690	Introducing the Internet Engineering and Planning Group (IEPG)
	Authors: G. Huston. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This memo introduces the IEPG to the Internet Community. The IEPG is an Internet Service Operators' forum, intended to assist ServiceOperators to coordinate in operational aspects of managing Internet services.
RFC 1691	The Document Architecture for the Cornell Digital Library
	Authors: W. Turner. Date: August 1994 Formats: txt pdf Status: INFORMATIONAL This memo defines an architecture for the storage and retrieval of the digital representations for books, journals, photographic images, etc., which are collected in a large organized digital library. Two unique features of this architecture are the ability to generate reference documents and the ability to create multiple views of a document.
RFC 1692	Transport Multiplexing Protocol (TMux)
	Authors: P. Cameron, D. Crocker, D. Cohen, J. Postel. Date: August 1994 Formats: txt pdf Status: HISTORIC One of the problems with the use of terminal servers is the large number of small packets they can generate. Frequently, most of these packets are destined for only one or two hosts. TMux is a protocol which allows multiple short transport segments, independent of application type, to be combined between a server and host pair.
RFC 1693	An Extension to TCP : Partial Order Service
	Authors: T. Connolly, P. Amer, P. Conrad. Date: November 1994 Formats: txt pdf Obsoleted by: RFC 6247 Status: HISTORIC This RFC introduces a new transport mechanism for TCP based upon partial ordering. The aim is to present the concepts of partial ordering and promote discussions on its usefulness in network communications. Distribution of this memo is unlimited.
RFC 1694	Definitions of Managed Objects for SMDS Interfaces using SMIv2
	Authors: T. Brown, K. Tesink, Eds.. Date: August 1994 Formats: txt pdf Obsoletes: RFC 1304 Status: DRAFT STANDARD This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing objects for SMDS access interfaces. This includes the following access protocols: SIP [13]SIP/DXI [18] and [20]SIP/FR [19]SIP/ATM [24] This memo replaces RFC 1304 [12], and defines a MIB module which is both compliant to the SNMPv2 SMI and semantically-identical to the existing RFC 1304-based definitions. This memo also assumes application of the MIB II Interfaces group as defined in [9].
RFC 1695	Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2
	Authors: M. Ahmed, K. Tesink, Eds.. Date: August 1994 Formats: txt pdf Obsoleted by: RFC 2515 Status: PROPOSED STANDARD 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 objects used for managing ATM-based interfaces, devices, networks and services. [STANDARDS-TRACK]
RFC 1696	Modem Management Information Base (MIB) using SMIv2
	Authors: J. Barnes, L. Brown, R. Royston, S. Waldbusser. Date: August 1994 Formats: txt pdf Status: HISTORIC 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 managed objects used for managing dial-up modems and similar dial-up devices. [STANDARDS-TRACK]
RFC 1697	Relational Database Management System (RDBMS) Management Information Base (MIB) using SMIv2
	Authors: D. Brower, Ed., B. Purvy, A. Daniel, M. Sinykin, J. Smith. Date: August 1994 Formats: txt pdf Status: PROPOSED STANDARD 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 managed objects used for managing relational database (RDBMS) implementations. [STANDARDS-TRACK]