Home   A   B   C   D   E   F   G   H   I   J   K   L   M   N   O   P   Q   R   S   T   U   V   W   X   Y   Z  

RFC Liste

RFC Nummer und Titel
Abstrakt
Datum
Status
Autor
RFC0001 Host Software
April 1969
Status: UNKNOWN
Autor: S. Crocker
RFC0002 Host software
April 1969
Status: UNKNOWN
Autor: B. Duvall
RFC0003 Documentation conventions
April 1969
Status: UNKNOWN
Autor: S.D. Crocker
RFC0004 Network timetable
March 1969
Status: UNKNOWN
Autor: E.B. Shapiro
RFC0005 Decode Encode Language (DEL)
June 1969
Status: UNKNOWN
Autor: J. Rulifson
RFC0006 Conversation with Bob Kahn
April 1969
Status: UNKNOWN
Autor: S.D. Crocker
RFC0007 Host-IMP interface
May 1969
Status: UNKNOWN
Autor: G. Deloche
RFC0008 ARPA Network Functional Specifications
May 1969
Status: UNKNOWN
Autor: G. Deloche
RFC0009 Host Software
May 1969
Status: UNKNOWN
Autor: G. Deloche
RFC0010 Documentation conventions
July 1969
Status: UNKNOWN
Autor: S.D. Crocker
RFC0011 Implementation of the Host - Host Software Procedures in GORDO
August 1969
Status: UNKNOWN
Autor: G. Deloche
RFC0012 IMP-Host interface flow diagrams
August 1969
Status: UNKNOWN
Autor: M. Wingfield
RFC0013 Zero Text Length EOF Message
August 1969
Status: UNKNOWN
Autor: V. Cerf
RFC0015 Network subsystem for time sharing hosts
September 1969
Status: UNKNOWN
Autor: C.S. Carr
RFC0016 M.I.T
August 1969
Status: UNKNOWN
Autor: S. Crocker
RFC0017 Some questions re: Host-IMP Protocol
August 1969
Status: UNKNOWN
Autor: J.E. Kreznar
RFC0018 IMP-IMP and HOST-HOST Control Links
September 1969
Status: UNKNOWN
Autor: V. Cerf
RFC0019 Two protocol suggestions to reduce congestion at swap bound nodes
October 1969
Status: UNKNOWN
Autor: J.E. Kreznar
RFC0020 ASCII format for network interchange
October 1969
Status: UNKNOWN
Autor: V.G. Cerf
RFC0021 Network meeting
October 1969
Status: UNKNOWN
Autor: V.G. Cerf
RFC0022 Host-host control message formats
October 1969
Status: UNKNOWN
Autor: V.G. Cerf
RFC0023 Transmission of Multiple Control Messages
October 1969
Status: UNKNOWN
Autor: G. Gregg
RFC0024 Documentation Conventions
November 1969
Status: UNKNOWN
Autor: S.D. Crocker
RFC0025 No High Link Numbers
October 1969
Status: UNKNOWN
Autor: S.D. Crocker
RFC0027 Documentation Conventions
December 1969
Status: UNKNOWN
Autor: S.D. Crocker
RFC0028 Time Standards
January 1970
Status: UNKNOWN
Autor: W.K. English
RFC0029 Response to RFC 28
January 1970
Status: UNKNOWN
Autor: R.E. Kahn
RFC0030 Documentation Conventions
February 1970
Status: UNKNOWN
Autor: S.D. Crocker
RFC0031 Binary Message Forms in Computer
February 1968
Status: UNKNOWN
Autor: D. Bobrow, W.R. Sutherland
RFC0032 Some Thoughts on SRI's Proposed Real Time Clock
February 1970
Status: UNKNOWN
Autor: J. Cole
RFC0033 New Host-Host Protocol
February 1970
Status: UNKNOWN
Autor: S.D. Crocker
RFC0034 Some Brief Preliminary Notes on the Augmentation Research Center Clock
February 1970
Status: UNKNOWN
Autor: W.K. English
RFC0035 Network Meeting
March 1970
Status: INFORMATIONAL
Autor: S.D. Crocker
RFC0036 Protocol Notes
March 1970
Status: UNKNOWN
Autor: S.D. Crocker
RFC0037 Network Meeting Epilogue, etc
March 1970
Status: UNKNOWN
Autor: S.D. Crocker
RFC0038 Comments on Network Protocol from NWG/RFC #36
March 1970
Status: UNKNOWN
Autor: S.M. Wolfe
RFC0039 Comments on Protocol Re: NWG/RFC #36
March 1970
Status: UNKNOWN
Autor: E. Harslem, J.F. Heafner
RFC0040 More Comments on the Forthcoming Protocol
March 1970
Status: UNKNOWN
Autor: E. Harslem, J.F. Heafner
RFC0041 IMP-IMP Teletype Communication
March 1970
Status: UNKNOWN
Autor: J.T. Melvin
RFC0042 Message Data Types
March 1970
Status: UNKNOWN
Autor: E. Ancona
RFC0043 Proposed Meeting
April 1970
Status: UNKNOWN
Autor: A.G. Nemeth
RFC0044 Comments on NWG/RFC 33 and 36
April 1970
Status: UNKNOWN
Autor: A. Shoshani, R. Long, A. Landsberg
RFC0045 New Protocol is Coming
April 1970
Status: UNKNOWN
Autor: J. Postel, S.D. Crocker
RFC0046 ARPA Network protocol notes
April 1970
Status: UNKNOWN
Autor: E. Meyer
RFC0047 BBN's Comments on NWG/RFC #33
April 1970
Status: UNKNOWN
Autor: J. Postel, S. Crocker
RFC0048 Possible protocol plateau
April 1970
Status: UNKNOWN
Autor: J. Postel, S.D. Crocker
RFC0049 Conversations with S. Crocker (UCLA)
April 1970
Status: UNKNOWN
Autor: E. Meyer
RFC0050 Comments on the Meyer Proposal
April 1970
Status: UNKNOWN
Autor: E. Harslen, J. Heafner
RFC0051 Proposal for a Network Interchange Language
May 1970
Status: UNKNOWN
Autor: M. Elie
RFC0052 Updated distribution list
July 1970
Status: UNKNOWN
Autor: J. Postel, S.D. Crocker
RFC0053 Official protocol mechanism
June 1970
Status: UNKNOWN
Autor: S.D. Crocker
RFC0054 Official Protocol Proffering
June 1970
Status: UNKNOWN
Autor: S.D. Crocker, J. Postel, J. Newkirk, M. Kraley
RFC0055 Prototypical implementation of the NCP
June 1970
Status: UNKNOWN
Autor: J. Newkirk, M. Kraley, J. Postel, S.D. Crocker
RFC0056 Third Level Protocol: Logger Protocol
June 1970
Status: UNKNOWN
Autor: E. Belove, D. Black, R. Flegal, L.G. Farquar
RFC0057 Thoughts and Reflections on NWG/RFC 54
June 1970
Status: UNKNOWN
Autor: M. Kraley, J. Newkirk
RFC0058 Logical Message Synchronization
June 1970
Status: UNKNOWN
Autor: T.P. Skinner
RFC0059 Flow Control - Fixed Versus Demand Allocation
June 1970
Status: UNKNOWN
Autor: E. Meyer
RFC0060 Simplified NCP Protocol
July 1970
Status: UNKNOWN
Autor: R.B. Kalin
RFC0061 Note on Interprocess Communication in a Resource Sharing Computer Network
July 1970
Status: UNKNOWN
Autor: D.C. Walden
RFC0062 Systems for Interprocess Communication in a Resource Sharing Computer Network
August 1970
Status: UNKNOWN
Autor: D.C. Walden
RFC0063 Belated Network Meeting Report
July 1970
Status: UNKNOWN
Autor: V.G. Cerf
RFC0064 Getting rid of marking
July 1970
Status: UNKNOWN
Autor: M. Elie
RFC0065 Comments on Host/Host Protocol document #1
August 1970
Status: UNKNOWN
Autor: D.C. Walden
RFC0066 NIC - third level ideas and other noise
August 1970
Status: UNKNOWN
Autor: S.D. Crocker
RFC0067 Proposed Change to Host/IMP Spec to Eliminate Marking
January 1970
Status: UNKNOWN
Autor: W.R. Crowther
RFC0068 Comments on Memory Allocation Control Commands: CEASE, ALL, GVB, RET, and RFNM
August 1970
Status: UNKNOWN
Autor: M. Elie
RFC0069 Distribution List Change for MIT
September 1970
Status: UNKNOWN
Autor: A.K. Bhushan
RFC0070 Note on Padding
October 1970
Status: UNKNOWN
Autor: S.D. Crocker
RFC0071 Reallocation in Case of Input Error
September 1970
Status: UNKNOWN
Autor: T. Schipper
RFC0072 Proposed Moratorium on Changes to Network Protocol
September 1970
Status: UNKNOWN
Autor: R.D. Bressler
RFC0073 Response to NWG/RFC 67
September 1970
Status: UNKNOWN
Autor: S.D. Crocker
RFC0074 Specifications for Network Use of the UCSB On-Line System
October 1970
Status: UNKNOWN
Autor: J.E. White
RFC0075 Network Meeting
October 1970
Status: UNKNOWN
Autor: S.D. Crocker
RFC0076 Connection by name: User oriented protocol
October 1970
Status: UNKNOWN
Autor: J. Bouknight, J. Madden, G.R. Grossman
RFC0077 Network meeting report
November 1970
Status: UNKNOWN
Autor: J. Postel
RFC0078 NCP Status Report: UCSB/Rand
October 1970
Status: UNKNOWN
Autor: E. Harslem, J.F. Heafner, J.E. White
RFC0079 Logger Protocol error
November 1970
Status: UNKNOWN
Autor: E. Meyer
RFC0080 Protocols and Data Formats
December 1970
Status: UNKNOWN
Autor: E. Harslem, J.F. Heafner
RFC0081 Request for Reference Information
December 1970
Status: UNKNOWN
Autor: J. Bouknight
RFC0082 Network Meeting Notes
December 1970
Status: UNKNOWN
Autor: E. Meyer
RFC0083 Language-machine for data reconfiguration
December 1970
Status: UNKNOWN
Autor: R.H. Anderson, E. Harslem, J.F. Heafner
RFC0084 List of NWG/RFC's 1-80
December 1970
Status: UNKNOWN
Autor: J.B. North
RFC0085 Network Working Group meeting
December 1970
Status: UNKNOWN
Autor: S.D. Crocker
RFC0086 Proposal for a Network Standard Format for a Data Stream to Control Graphics Display
January 1971
Status: UNKNOWN
Autor: S.D. Crocker
RFC0087 Topic for Discussion at the Next Network Working Group Meeting
January 1971
Status: UNKNOWN
Autor: A. Vezza
RFC0088 NETRJS: A third level protocol for Remote Job Entry
January 1971
Status: UNKNOWN
Autor: R.T. Braden, S.M. Wolfe
RFC0089 Some historic moments in networking
January 1971
Status: UNKNOWN
Autor: R.M. Metcalfe
RFC0090 CCN as a Network Service Center
January 1971
Status: UNKNOWN
Autor: R.T. Braden
RFC0091 Proposed User-User Protocol
December 1970
Status: UNKNOWN
Autor: G.H. Mealy
RFC0093 Initial Connection Protocol
January 1971
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0094 Some thoughts on Network Graphics
February 1971
Status: UNKNOWN
Autor: E. Harslem, J.F. Heafner
RFC0095 Distribution of NWG/RFC's through the NIC
February 1971
Status: UNKNOWN
Autor: S.D. Crocker
RFC0096 An Interactive Network Experiment to Study Modes of Access the Network Information Center
February 1971
Status: INFORMATIONAL
Autor: R.W. Watson
RFC0097 First Cut at a Proposed Telnet Protocol
February 1971
Status: UNKNOWN
Autor: J.T. Melvin, R.W. Watson
RFC0098 Logger Protocol Proposal
February 1971
Status: UNKNOWN
Autor: E. Meyer, T. Skinner
RFC0099 Network Meeting
February 1971
Status: UNKNOWN
Autor: P.M. Karp
RFC0100 Categorization and guide to NWG/RFCs
February 1971
Status: UNKNOWN
Autor: P.M. Karp
RFC0101 Notes on the Network Working Group meeting, Urbana, Illinois, February 17, 1971
February 1971
Status: UNKNOWN
Autor: R.W. Watson
RFC0102 Output of the Host-Host Protocol glitch cleaning committee
February 1971
Status: UNKNOWN
Autor: S.D. Crocker
RFC0103 Implementation of Interrupt Keys
February 1971
Status: UNKNOWN
Autor: R.B. Kalin
RFC0104 Link 191
February 1971
Status: UNKNOWN
Autor: J.B. Postel, S.D. Crocker
RFC0105 Network Specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB
March 1971
Status: UNKNOWN
Autor: J.E. White
RFC0106 User/Server Site Protocol Network Host Questionnaire
March 1971
Status: UNKNOWN
Autor: T.C. O'Sullivan
RFC0107 Output of the Host-Host Protocol Glitch Cleaning Committee
March 1971
Status: UNKNOWN
Autor: R.D. Bressler, S.D. Crocker, W.R. Crowther, G.R. Grossman, R.S. Tomlinson, J.E. White
RFC0108 Attendance list at the Urbana NWG meeting, February 17-19, 1971
March 1971
Status: UNKNOWN
Autor: R.W. Watson
RFC0109 Level III Server Protocol for the Lincoln Laboratory 360/67 Host
March 1971
Status: UNKNOWN
Autor: J. Winett
RFC0110 Conventions for Using an IBM 2741 Terminal as a User Console for Access to Network Server Hosts
March 1971
Status: UNKNOWN
Autor: J. Winett
RFC0111 Pressure from the Chairman
March 1971
Status: UNKNOWN
Autor: S.D. Crocker
RFC0112 User/Server Site Protocol: Network Host Questionnaire
April 1971
Status: UNKNOWN
Autor: T.C. O'Sullivan
RFC0113 Network activity report: UCSB Rand
April 1971
Status: UNKNOWN
Autor: E. Harslem, J.F. Heafner, J.E. White
RFC0114 File Transfer Protocol
April 1971
Status: UNKNOWN
Autor: A.K. Bhushan
RFC0115 Some Network Information Center policies on handling documents
April 1971
Status: UNKNOWN
Autor: R.W. Watson, J.B. North
RFC0116 Structure of the May NWG Meeting
April 1971
Status: UNKNOWN
Autor: S.D. Crocker
RFC0117 Some comments on the official protocol
April 1971
Status: UNKNOWN
Autor: J. Wong
RFC0118 Recommendations for facility documentation
April 1971
Status: UNKNOWN
Autor: R.W. Watson
RFC0119 Network Fortran Subprograms
April 1971
Status: UNKNOWN
Autor: M. Krilanovich
RFC0120 Network PL1 subprograms
April 1971
Status: UNKNOWN
Autor: M. Krilanovich
RFC0121 Network on-line operators
April 1971
Status: UNKNOWN
Autor: M. Krilanovich
RFC0122 Network specifications for UCSB's Simple-Minded File System
April 1971
Status: UNKNOWN
Autor: J.E. White
RFC0123 Proffered Official ICP
April 1971
Status: UNKNOWN
Autor: S.D. Crocker
RFC0124 Typographical error in RFC 107
April 1971
Status: UNKNOWN
Autor: J.T. Melvin
RFC0125 Response to RFC 86: Proposal for Network Standard Format for a Graphics Data Stream
April 1971
Status: UNKNOWN
Autor: J. McConnell
RFC0126 Graphics Facilities at Ames Research Center
April 1971
Status: UNKNOWN
Autor: J. McConnell
RFC0127 Comments on RFC 123
April 1971
Status: UNKNOWN
Autor: J. Postel
RFC0128 Bytes
April 1971
Status: UNKNOWN
Autor: J. Postel
RFC0129 Request for comments on socket name structure
April 1971
Status: UNKNOWN
Autor: E. Harslem, J. Heafner, E. Meyer
RFC0130 Response to RFC 111: Pressure from the chairman
April 1971
Status: UNKNOWN
Autor: J.F. Heafner
RFC0131 Response to RFC 116: May NWG meeting
April 1971
Status: UNKNOWN
Autor: E. Harslem, J.F. Heafner
RFC0132 Typographical Error in RFC 107
April 1971
Status: UNKNOWN
Autor: J.E. White
RFC0133 File Transfer and Error Recovery
April 1971
Status: UNKNOWN
Autor: R.L. Sunberg
RFC0134 Network Graphics meeting
April 1971
Status: UNKNOWN
Autor: A. Vezza
RFC0135 Response to NWG/RFC 110
April 1971
Status: UNKNOWN
Autor: W. Hathaway
RFC0136 Host accounting and administrative procedures
April 1971
Status: UNKNOWN
Autor: R.E. Kahn
RFC0137 Telnet Protocol - a proposed document
April 1971
Status: UNKNOWN
Autor: T.C. O'Sullivan
RFC0138 Status report on proposed Data Reconfiguration Service
April 1971
Status: UNKNOWN
Autor: 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
RFC0139 Discussion of Telnet Protocol
May 1971
Status: UNKNOWN
Autor: T.C. O'Sullivan
RFC0140 Agenda for the May NWG meeting
May 1971
Status: UNKNOWN
Autor: S.D. Crocker
RFC0141 Comments on RFC 114: A File Transfer Protocol
April 1971
Status: UNKNOWN
Autor: E. Harslem, J.F. Heafner
RFC0142 Time-Out Mechanism in the Host-Host Protocol
May 1971
Status: UNKNOWN
Autor: C. Kline, J. Wong
RFC0143 Regarding proffered official ICP
May 1971
Status: UNKNOWN
Autor: W. Naylor, J. Wong, C. Kline, J. Postel
RFC0144 Data sharing on computer networks
April 1971
Status: UNKNOWN
Autor: A. Shoshani
RFC0145 Initial Connection Protocol Control Commands
May 1971
Status: UNKNOWN
Autor: J. Postel
RFC0146 Views on issues relevant to data sharing on computer networks
May 1971
Status: UNKNOWN
Autor: P.M. Karp, D.B. McKay, D.C.M. Wood
RFC0147 Definition of a socket
May 1971
Status: UNKNOWN
Autor: J.M. Winett
RFC0148 Comments on RFC 123
May 1971
Status: UNKNOWN
Autor: A.K. Bhushan
RFC0149 Best Laid Plans
May 1971
Status: UNKNOWN
Autor: S.D. Crocker
RFC0150 Use of IPC Facilities: A Working Paper
May 1971
Status: UNKNOWN
Autor: R.B. Kalin
RFC0151 Comments on a proffered official ICP: RFCs 123, 127
May 1971
Status: UNKNOWN
Autor: A. Shoshani
RFC0152 SRI Artificial Intelligence status report
May 1971
Status: UNKNOWN
Autor: M. Wilber
RFC0153 SRI ARC-NIC status
May 1971
Status: UNKNOWN
Autor: J.T. Melvin, R.W. Watson
RFC0154 Exposition Style
May 1971
Status: UNKNOWN
Autor: S.D. Crocker
RFC0155 ARPA Network mailing lists
May 1971
Status: UNKNOWN
Autor: J.B. North
RFC0156 Status of the Illinois site: Response to RFC 116
April 1971
Status: UNKNOWN
Autor: J. Bouknight
RFC0157 Invitation to the Second Symposium on Problems in the Optimization of Data Communications Systems
May 1971
Status: UNKNOWN
Autor: V.G. Cerf
RFC0158 Telnet Protocol: A Proposed Document
May 1971
Status: UNKNOWN
Autor: T.C. O'Sullivan
RFC0160 RFC brief list
May 1971
Status: UNKNOWN
Autor: Network Information Center. Stanford Research Institute
RFC0161 Solution to the race condition in the ICP
May 1971
Status: UNKNOWN
Autor: A. Shoshani
RFC0162 NETBUGGER3
May 1971
Status: UNKNOWN
Autor: M. Kampe
RFC0163 Data transfer protocols
May 1971
Status: UNKNOWN
Autor: V.G. Cerf
RFC0164 Minutes of Network Working Group meeting, 5/16 through 5/19/71
May 1971
Status: UNKNOWN
Autor: J.F. Heafner
RFC0165 Proffered Official Initial Connection Protocol
May 1971
Status: UNKNOWN
Autor: J. Postel
RFC0166 Data Reconfiguration Service: An implementation specification
May 1971
Status: UNKNOWN
Autor: 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
RFC0167 Socket conventions reconsidered
May 1971
Status: UNKNOWN
Autor: A.K. Bhushan, R.M. Metcalfe, J.M. Winett
RFC0168 ARPA Network mailing lists
May 1971
Status: UNKNOWN
Autor: J.B. North
RFC0169 COMPUTER NETWORKS
May 1971
Status: UNKNOWN
Autor: S.D. Crocker
RFC0170 RFC List by Number
June 1971
Status: UNKNOWN
Autor: Network Information Center. Stanford Research Institute
RFC0171 The Data Transfer Protocol
June 1971
Status: UNKNOWN
Autor: A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenize, J. Melvin, B. Sundberg, D. Watson, J. White
RFC0172 The File Transfer Protocol
June 1971
Status: UNKNOWN
Autor: A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenzie, J. Melvin, B. Sundberg, D. Watson, J. White
RFC0173 Network Data Management Committee Meeting Announcement
June 1971
Status: UNKNOWN
Autor: P.M. Karp, D.B. McKay
RFC0174 UCLA - Computer Science Graphics Overview
June 1971
Status: UNKNOWN
Autor: J. Postel, V.G. Cerf
RFC0175 Comments on "Socket Conventions Reconsidered"
June 1971
Status: UNKNOWN
Autor: E. Harslem, J.F. Heafner
RFC0176 Comments on "Byte size for connections"
June 1971
Status: UNKNOWN
Autor: A.K. Bhushan, R. Kanodia, R.M. Metcalfe, J. Postel
RFC0177 Device independent graphical display description
June 1971
Status: UNKNOWN
Autor: J. McConnell
RFC0178 Network graphic attention handling
June 1971
Status: UNKNOWN
Autor: I.W. Cotton
RFC0179 Link Number Assignments
June 1971
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0180 File system questionnaire
June 1971
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0181 Modifications to RFC 177
July 1971
Status: UNKNOWN
Autor: J. McConnell
RFC0182 Compilation of list of relevant site reports
June 1971
Status: UNKNOWN
Autor: J.B. North
RFC0183 EBCDIC Codes and Their Mapping to ASCII
July 1971
Status: UNKNOWN
Autor: J.M. Winett
RFC0184 Proposed graphic display modes
July 1971
Status: UNKNOWN
Autor: K.C. Kelley
RFC0185 NIC distribution of manuals and handbooks
July 1971
Status: UNKNOWN
Autor: J.B. North
RFC0186 Network graphics loader
July 1971
Status: UNKNOWN
Autor: J.C. Michener
RFC0187 Network/440 Protocol Concept
July 1971
Status: UNKNOWN
Autor: D.B. McKay, D.P. Karp
RFC0188 Data management meeting announcement
January 1971
Status: UNKNOWN
Autor: P.M. Karp, D.B. McKay
RFC0189 Interim NETRJS specifications
July 1971
Status: UNKNOWN
Autor: R.T. Braden
RFC0190 DEC PDP-10-IMLAC communications system
July 1971
Status: UNKNOWN
Autor: L.P. Deutsch
RFC0191 Graphics implementation and conceptualization at Augmentation Research Center
July 1971
Status: UNKNOWN
Autor: C.H. Irby
RFC0192 Some factors which a Network Graphics Protocol must consider
July 1971
Status: UNKNOWN
Autor: R.W. Watson
RFC0193 NETWORK CHECKOUT
July 1971
Status: UNKNOWN
Autor: E. Harslem, J.F. Heafner
RFC0194 The Data Reconfiguration Service -- Compiler/Interpreter Implementation Notes
July 1971
Status: UNKNOWN
Autor: V. Cerf, E. Harslem, J. Heafner, B. Metcalfe, J. White
RFC0195 Data computers-data descriptions and access language
July 1971
Status: UNKNOWN
Autor: G.H. Mealy
RFC0196 Mail Box Protocol
July 1971
Status: UNKNOWN
Autor: R.W. Watson
RFC0197 Initial Connection Protocol - Reviewed
July 1971
Status: UNKNOWN
Autor: A. Shoshani, E. Harslem
RFC0198 Site Certification - Lincoln Labs 360/67
July 1971
Status: UNKNOWN
Autor: J.F. Heafner
RFC0199 Suggestions for a Network Data-Tablet Graphics Protocol
July 1971
Status: UNKNOWN
Autor: T. Williams
RFC0200 RFC list by number
August 1971
Status: UNKNOWN
Autor: J.B. North
RFC0202 Possible Deadlock in ICP
July 1971
Status: UNKNOWN
Autor: S.M. Wolfe, J. Postel
RFC0203 Achieving reliable communication
August 1971
Status: UNKNOWN
Autor: R.B. Kalin
RFC0204 Sockets in use
August 1971
Status: UNKNOWN
Autor: J. Postel
RFC0205 NETCRT - a character display protocol
August 1971
Status: UNKNOWN
Autor: R.T. Braden
RFC0206 A User TELNET Description of an Initial Implementation
August 1971
Status: UNKNOWN
Autor: J. White
RFC0207 September Network Working Group meeting
August 1971
Status: UNKNOWN
Autor: A. Vezza
RFC0208 Address tables
August 1971
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0209 Host/IMP interface documentation
August 1971
Status: UNKNOWN
Autor: B. Cosell
RFC0210 Improvement of Flow Control
August 1971
Status: UNKNOWN
Autor: W. Conrad
RFC0211 ARPA Network Mailing Lists
August 1971
Status: UNKNOWN
Autor: J.B. North
RFC0212 NWG meeting on network usage
August 1971
Status: UNKNOWN
Autor: Information Sciences Institute University of Southern California
RFC0213 IMP System change notification
August 1971
Status: UNKNOWN
Autor: B. Cosell
RFC0214 Network checkpoint
August 1971
Status: UNKNOWN
Autor: E. Harslem
RFC0215 NCP, ICP, and Telnet: The Terminal IMP implementation
August 1971
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0216 Telnet Access to UCSB's On-Line System
September 1971
Status: UNKNOWN
Autor: J.E. White
RFC0217 Specifications changes for OLS, RJE/RJOR, and SMFS
September 1971
Status: UNKNOWN
Autor: J.E. White
RFC0218 Changing the IMP status reporting facility
September 1971
Status: UNKNOWN
Autor: B. Cosell
RFC0219 User's View of the Datacomputer
September 1971
Status: UNKNOWN
Autor: R. Winter
RFC0221 Mail Box Protocol: Version 2
August 1971
Status: UNKNOWN
Autor: R.W. Watson
RFC0222 Subject: System programmer's workshop
September 1971
Status: UNKNOWN
Autor: R.M. Metcalfe
RFC0223 Network Information Center schedule for network users
September 1971
Status: UNKNOWN
Autor: J.T. Melvin, R.W. Watson
RFC0224 Comments on Mailbox Protocol
September 1971
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0225 Rand/UCSB network graphics experiment
September 1971
Status: UNKNOWN
Autor: E. Harslem, R. Stoughton
RFC0226 Standardization of host mnemonics
September 1971
Status: UNKNOWN
Autor: P.M. Karp
RFC0227 Data transfer rates (Rand/UCLA)
September 1971
Status: UNKNOWN
Autor: J.F. Heafner, E. Harslem
RFC0228 Clarification
September 1971
Status: UNKNOWN
Autor: D.C. Walden
RFC0229 Standard host names
September 1971
Status: UNKNOWN
Autor: J. Postel
RFC0230 Toward reliable operation of minicomputer-based terminals on a TIP
September 1971
Status: UNKNOWN
Autor: T. Pyke
RFC0231 Service center standards for remote usage: A user's view
September 1971
Status: UNKNOWN
Autor: J.F. Heafner, E. Harslem
RFC0232 Postponement of network graphics meeting
September 1971
Status: UNKNOWN
Autor: A. Vezza
RFC0233 Standardization of host call letters
September 1971
Status: UNKNOWN
Autor: A. Bhushan, R. Metcalfe
RFC0234 Network Working Group meeting schedule
October 1971
Status: UNKNOWN
Autor: A. Vezza
RFC0235 Site status
September 1971
Status: UNKNOWN
Autor: E. Westheimer
RFC0236 Standard host names
September 1971
Status: UNKNOWN
Autor: J. Postel
RFC0237 NIC view of standard host names
October 1971
Status: UNKNOWN
Autor: R.W. Watson
RFC0238 Comments on DTP and FTP proposals
September 1971
Status: UNKNOWN
Autor: R.T. Braden
RFC0239 Host mnemonics proposed in RFC 226 (NIC 7625)
September 1971
Status: UNKNOWN
Autor: R.T. Braden
RFC0240 Site Status
September 1971
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0241 Connecting computers to MLC ports
September 1971
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0242 Data Descriptive Language for Shared Data
July 1971
Status: UNKNOWN
Autor: L. Haibt, A.P. Mullery
RFC0243 Network and data sharing bibliography
October 1971
Status: UNKNOWN
Autor: A.P. Mullery
RFC0245 Reservations for Network Group meeting
October 1971
Status: UNKNOWN
Autor: C. Falls
RFC0246 Network Graphics meeting
October 1971
Status: UNKNOWN
Autor: A. Vezza
RFC0247 Proffered set of standard host names
October 1971
Status: UNKNOWN
Autor: P.M. Karp
RFC0249 Coordination of equipment and supplies purchase
October 1971
Status: UNKNOWN
Autor: R.F. Borelli
RFC0250 Some thoughts on file transfer
October 1971
Status: UNKNOWN
Autor: H. Brodie
RFC0251 Weather data
October 1971
Status: UNKNOWN
Autor: D. Stern
RFC0252 Network host status
October 1971
Status: UNKNOWN
Autor: E. Westheimer
RFC0253 Second Network Graphics meeting details
October 1971
Status: UNKNOWN
Autor: J.A. Moorer
RFC0254 Scenarios for using ARPANET computers
October 1971
Status: UNKNOWN
Autor: A. Bhushan
RFC0255 Status of network hosts
October 1971
Status: UNKNOWN
Autor: E. Westheimer
RFC0256 IMPSYS change notification
November 1971
Status: UNKNOWN
Autor: B. Cosell
RFC0263 "Very Distant" Host interface
December 1971
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0264 The Data Transfer Protocol
January 1972
Status: UNKNOWN
Autor: A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenize, B. Sundberg, D. Watson, J. White
RFC0265 The File Transfer Protocol
November 1971
Status: UNKNOWN
Autor: A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenzie, J. Melvin, B. Sundberg, D. Watson, J. White
RFC0266 Network host status
November 1971
Status: UNKNOWN
Autor: E. Westheimer
RFC0267 Network Host Status
November 1971
Status: UNKNOWN
Autor: E. Westheimer
RFC0268 Graphics facilities information
November 1971
Status: UNKNOWN
Autor: J. Postel
RFC0269 Some Experience with File Transfer
December 1971
Status: UNKNOWN
Autor: H. Brodie
RFC0270 Correction to BBN Report No. 1822 (NIC NO 7958)
January 1972
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0271 IMP System change notifications
January 1972
Status: UNKNOWN
Autor: B. Cosell
RFC0273 More on standard host names
October 1971
Status: UNKNOWN
Autor: R.W. Watson
RFC0274 Establishing a local guide for network usage
November 1971
Status: UNKNOWN
Autor: E. Forman
RFC0276 NIC course
November 1971
Status: UNKNOWN
Autor: R.W. Watson
RFC0278 Revision of the Mail Box Protocol
November 1971
Status: UNKNOWN
Autor: 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
RFC0280 A Draft of Host Names
November 1971
Status: UNKNOWN
Autor: R.W. Watson
RFC0281 Suggested addition to File Transfer Protocol
December 1971
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0282 Graphics meeting report
December 1971
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0283 NETRJT: Remote Job Service Protocol for TIPS
December 1971
Status: UNKNOWN
Autor: R.T. Braden
RFC0285 Network graphics
December 1971
Status: UNKNOWN
Autor: D. Huff
RFC0286 Network Library Information System
December 1971
Status: UNKNOWN
Autor: E. Forman
RFC0287 Status of Network Hosts
December 1971
Status: UNKNOWN
Autor: E. Westheimer
RFC0288 Network host status
January 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0289 What we hope is an official list of host names
December 1971
Status: UNKNOWN
Autor: R.W. Watson
RFC0290 Computer networks and data sharing: A bibliography
January 1972
Status: UNKNOWN
Autor: A.P. Mullery
RFC0291 Data Management Meeting Announcement
January 1972
Status: UNKNOWN
Autor: D.B. McKay
RFC0292 Graphics Protocol: Level 0 only
January 1972
Status: UNKNOWN
Autor: J.C. Michener, I.W. Cotton, K.C. Kelley, D.E. Liddle, E. Meyer
RFC0293 Network Host Status
January 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0294 The Use of "Set Data Type" Transaction in File Transfer Protocol
January 1972
Status: UNKNOWN
Autor: A.K. Bhushan
RFC0295 Report of the Protocol Workshop, 12 October 1971
January 1972
Status: UNKNOWN
Autor: J. Postel
RFC0296 DS-1 Display System
January 1972
Status: UNKNOWN
Autor: D.E. Liddle
RFC0297 TIP Message Buffers
January 1972
Status: UNKNOWN
Autor: D.C. Walden
RFC0298 Network host status
February 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0299 Information Management System
February 1972
Status: UNKNOWN
Autor: D. Hopkin
RFC0300 ARPA Network mailing lists
January 1972
Status: UNKNOWN
Autor: J.B. North
RFC0301 BBN IMP (#5) and NCC Schedule March 4, 1971
February 1972
Status: UNKNOWN
Autor: R. Alter
RFC0302 Exercising The ARPANET
February 1972
Status: UNKNOWN
Autor: R.F. Bryan
RFC0303 ARPA Network mailing lists
March 1972
Status: UNKNOWN
Autor: Network Information Center. Stanford Research Institute
RFC0304 Data Management System Proposal for the ARPA Network
February 1972
Status: UNKNOWN
Autor: D.B. McKay
RFC0305 Unknown Host Numbers
February 1972
Status: UNKNOWN
Autor: R. Alter
RFC0306 Network host status
February 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0307 Using network Remote Job Entry
February 1972
Status: UNKNOWN
Autor: E. Harslem
RFC0308 ARPANET host availability data
March 1972
Status: UNKNOWN
Autor: M. Seriff
RFC0309 Data and File Transfer Workshop Announcement
March 1972
Status: UNKNOWN
Autor: A.K. Bhushan
RFC0310 Another Look at Data and File Transfer Protocols
April 1972
Status: UNKNOWN
Autor: A.K. Bhushan
RFC0311 New Console Attachments to the USCB Host
February 1972
Status: UNKNOWN
Autor: R.F. Bryan
RFC0312 Proposed Change in IMP-to-Host Protocol
March 1972
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0313 Computer based instruction
March 1972
Status: UNKNOWN
Autor: T.C. O'Sullivan
RFC0314 Network Graphics Working Group Meeting
March 1972
Status: UNKNOWN
Autor: I.W. Cotton
RFC0315 Network Host Status
March 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0316 ARPA Network Data Management Working Group
February 1972
Status: UNKNOWN
Autor: D.B. McKay, A.P. Mullery
RFC0317 Official Host-Host Protocol Modification: Assigned Link Numbers
March 1972
Status: UNKNOWN
Autor: J. Postel
RFC0318 Telnet Protocols
April 1972
Status: UNKNOWN
Autor: J. Postel
RFC0319 Network Host Status
March 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0320 Workshop on Hard Copy Line Graphics
March 1972
Status: UNKNOWN
Autor: R. Reddy
RFC0321 CBI Networking Activity at MITRE
March 1972
Status: UNKNOWN
Autor: P.M. Karp
RFC0322 Well known socket numbers
March 1972
Status: UNKNOWN
Autor: V. Cerf, J. Postel
RFC0323 Formation of Network Measurement Group (NMG)
March 1972
Status: UNKNOWN
Autor: V. Cerf
RFC0324 RJE Protocol meeting
April 1972
Status: UNKNOWN
Autor: J. Postel
RFC0325 Network Remote Job Entry program - NETRJS
April 1972
Status: UNKNOWN
Autor: G. Hicks
RFC0326 Network Host Status
April 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0327 Data and File Transfer workshop notes
April 1972
Status: UNKNOWN
Autor: A.K. Bhushan
RFC0328 Suggested Telnet Protocol Changes
April 1972
Status: UNKNOWN
Autor: J. Postel
RFC0329 ARPA Network Mailing Lists
May 1972
Status: UNKNOWN
Autor: Network Information Center. Stanford Research Institute
RFC0330 Network Host Status
April 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0331 IMP System Change Notification
April 1972
Status: UNKNOWN
Autor: J.M. McQuillan
RFC0332 Network Host Status
April 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0333 Proposed experiment with a Message Switching Protocol
May 1972
Status: UNKNOWN
Autor: R.D. Bressler, D. Murphy, D.C. Walden
RFC0334 Network Use on May 8
May 1972
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0335 New Interface - IMP/360
May 1972
Status: UNKNOWN
Autor: R.F. Bryan
RFC0336 Level 0 Graphic Input Protocol
May 1972
Status: UNKNOWN
Autor: I.W. Cotton
RFC0338 EBCDIC/ASCII Mapping for Network RJE
May 1972
Status: UNKNOWN
Autor: R.T. Braden
RFC0339 MLTNET: A "Multi Telnet" Subsystem for Tenex
May 1972
Status: UNKNOWN
Autor: R. Thomas
RFC0340 Proposed Telnet Changes
May 1972
Status: UNKNOWN
Autor: T.C. O'Sullivan
RFC0342 Network Host Status
May 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0343 IMP System change notification
May 1972
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0344 Network Host Status
May 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0345 Interest in Mixed Integer Programming (MPSX on NIC 360/91 at CCN)
May 1972
Status: UNKNOWN
Autor: K.C. Kelley
RFC0346 Satellite Considerations
May 1972
Status: UNKNOWN
Autor: J. Postel
RFC0347 Echo process
May 1972
Status: UNKNOWN
Autor: J. Postel
RFC0348 Discard Process
May 1972
Status: UNKNOWN
Autor: J. Postel
RFC0349 Proposed Standard Socket Numbers
May 1972
Status: UNKNOWN
Autor: J. Postel
RFC0350 User Accounts for UCSB On-Line System
May 1972
Status: UNKNOWN
Autor: R. Stoughton
RFC0351 Graphics information form for the ARPANET graphics resources notebook
June 1972
Status: UNKNOWN
Autor: D. Crocker
RFC0352 TIP Site Information Form
June 1972
Status: UNKNOWN
Autor: D. Crocker
RFC0353 Network host status
June 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0354 File Transfer Protocol
July 1972
Status: UNKNOWN
Autor: A.K. Bhushan
RFC0355 Response to NWG/RFC 346
June 1972
Status: UNKNOWN
Autor: J. Davidson
RFC0356 ARPA Network Control Center
June 1972
Status: UNKNOWN
Autor: R. Alter
RFC0357 Echoing strategy for satellite links
June 1972
Status: UNKNOWN
Autor: J. Davidson
RFC0359 Status of the Release of the New IMP System (2600)
June 1972
Status: UNKNOWN
Autor: D.C. Walden
RFC0360 Proposed Remote Job Entry Protocol
June 1972
Status: UNKNOWN
Autor: C. Holland
RFC0361 Deamon Processes on Host 106
July 1972
Status: UNKNOWN
Autor: R.D. Bressler
RFC0362 Network Host Status
June 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0363 ARPA Network mailing lists
August 1972
Status: UNKNOWN
Autor: Network Information Center. Stanford Research Institute
RFC0364 Serving remote users on the ARPANET
July 1972
Status: UNKNOWN
Autor: M.D. Abrams
RFC0365 Letter to All TIP Users
July 1972
Status: UNKNOWN
Autor: D.C. Walden
RFC0366 Network Host Status
July 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0367 Network host status
July 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0368 Comments on "Proposed Remote Job Entry Protocol"
July 1972
Status: UNKNOWN
Autor: R.T. Braden
RFC0369 Evaluation of ARPANET services January-March, 1972
July 1972
Status: UNKNOWN
Autor: J.R. Pickens
RFC0370 Network Host Status
July 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0371 Demonstration at International Computer Communications Conference
July 1972
Status: UNKNOWN
Autor: R.E. Kahn
RFC0372 Notes on a Conversation with Bob Kahn on the ICCC
July 1972
Status: UNKNOWN
Autor: R.W. Watson
RFC0373 Arbitrary Character Sets
July 1972
Status: UNKNOWN
Autor: J. McCarthy
RFC0374 IMP System Announcement
July 1972
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0376 Network Host Status
August 1972
Status: UNKNOWN
Autor: E. Westheimer
RFC0377 Using TSO via ARPA Network Virtual Terminal
August 1972
Status: UNKNOWN
Autor: R.T. Braden
RFC0378 Traffic statistics (July 1972)
August 1972
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0379 Using TSO at CCN
August 1972
Status: UNKNOWN
Autor: R. Braden
RFC0381 Three aids to improved network operation
July 1972
Status: UNKNOWN
Autor: J.M. McQuillan
RFC0382 Mathematical Software on the ARPA Network
August 1972
Status: UNKNOWN
Autor: L. McDaniel
RFC0384 Official site idents for organizations in the ARPA Network
August 1972
Status: UNKNOWN
Autor: J.B. North
RFC0385 Comments on the File Transfer Protocol
August 1972
Status: UNKNOWN
Autor: A.K. Bhushan
RFC0386 Letter to TIP users-2
August 1972
Status: UNKNOWN
Autor: B. Cosell, D.C. Walden
RFC0387 Some experiences in implementing Network Graphics Protocol Level 0
August 1972
Status: UNKNOWN
Autor: K.C. Kelley, J. Meir
RFC0388 NCP statistics
August 1972
Status: UNKNOWN
Autor: V. Cerf
RFC0389 UCLA Campus Computing Network Liaison Staff for ARPA Network
August 1972
Status: UNKNOWN
Autor: B. Noble
RFC0390 TSO Scenario
September 1972
Status: UNKNOWN
Autor: R.T. Braden
RFC0391 Traffic statistics (August 1972)
September 1972
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0392 Measurement of host costs for transmitting network data
September 1972
Status: UNKNOWN
Autor: G. Hicks, B.D. Wessler
RFC0393 Comments on Telnet Protocol Changes
October 1972
Status: UNKNOWN
Autor: J.M. Winett
RFC0394 Two Proposed Changes to the IMP-Host Protocol
September 1972
Status: UNKNOWN
Autor: J.M. McQuillan
RFC0395 Switch Settings on IMPs and TIPs
October 1972
Status: UNKNOWN
Autor: J.M. McQuillan
RFC0396 Network Graphics Working Group Meeting - Second Iteration
November 1972
Status: UNKNOWN
Autor: S. Bunch
RFC0398 ICP Sockets
September 1972
Status: UNKNOWN
Autor: J.R. Pickens, E. Faeh
RFC0399 SMFS Login and Logout
September 1972
Status: UNKNOWN
Autor: M. Krilanovich
RFC0400 Traffic Statistics (September 1972)
October 1972
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0401 Conversion of NGP-0 Coordinates to Device Specific Coordinates
October 1972
Status: UNKNOWN
Autor: J. Hansen
RFC0402 ARPA Network Mailing Lists
October 1972
Status: UNKNOWN
Autor: J.B. North
RFC0403 Desirability of a Network 1108 Service
January 1973
Status: UNKNOWN
Autor: G. Hicks
RFC0404 Host Address Changes Involving Rand and ISI
October 1972
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0405 Correction to RFC 404
October 1972
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0406 Scheduled IMP Software Releases
October 1972
Status: UNKNOWN
Autor: J.M. McQuillan
RFC0407 Remote Job Entry Protocol
October 1972
Status: HISTORIC
Autor: R.D. Bressler, R. Guida, A.M. McKenzie
RFC0408 NETBANK
October 1972
Status: UNKNOWN
Autor: A.D. Owen, J. Postel
RFC0409 Tenex interface to UCSB's Simple-Minded File System
December 1972
Status: UNKNOWN
Autor: J.E. White
RFC0410 Removal of the 30-Second Delay When Hosts Come Up
November 1972
Status: UNKNOWN
Autor: J.M. McQuillan
RFC0411 New MULTICS Network Software Features
November 1972
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0412 User FTP Documentation
November 1972
Status: UNKNOWN
Autor: G. Hicks
RFC0413 Traffic statistics (October 1972)
November 1972
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0414 File Transfer Protocol (FTP) status and further comments
December 1972
Status: UNKNOWN
Autor: A.K. Bhushan
RFC0415 Tenex bandwidth
November 1972
Status: UNKNOWN
Autor: H. Murray
RFC0416 ARC System Will Be Unavailable for Use During Thanksgiving Week
November 1972
Status: UNKNOWN
Autor: J.C. Norton
RFC0417 Link usage violation
December 1972
Status: UNKNOWN
Autor: J. Postel, C. Kline
RFC0418 Server File Transfer Under TSS/360 At NASA-Ames Research Center
November 1972
Status: UNKNOWN
Autor: W. Hathaway
RFC0419 To: Network liaisons and station agents
December 1972
Status: UNKNOWN
Autor: A. Vezza
RFC0420 CCA ICCC weather demo
January 1973
Status: UNKNOWN
Autor: H. Murray
RFC0421 Software Consulting Service for Network Users
November 1972
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0422 Traffic statistics (November 1972)
December 1972
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0423 UCLA Campus Computing Network Liaison Staff for ARPANET
December 1972
Status: UNKNOWN
Autor: B. Noble
RFC0425 "But my NCP costs $500 a day"
December 1972
Status: UNKNOWN
Autor: R.D. Bressler
RFC0426 Reconnection Protocol
January 1973
Status: UNKNOWN
Autor: R. Thomas
RFC0429 Character Generator Process
December 1972
Status: UNKNOWN
Autor: J. Postel
RFC0430 Comments on File Transfer Protocol
February 1973
Status: UNKNOWN
Autor: R.T. Braden
RFC0431 Update on SMFS Login and Logout
December 1972
Status: UNKNOWN
Autor: M. Krilanovich
RFC0432 Network logical map
December 1972
Status: UNKNOWN
Autor: N. Neigus
RFC0433 Socket number list
December 1972
Status: UNKNOWN
Autor: J. Postel
RFC0434 IMP/TIP memory retrofit schedule
January 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0435 Telnet issues
January 1973
Status: UNKNOWN
Autor: B. Cosell, D.C. Walden
RFC0436 Announcement of RJS at UCSB
January 1973
Status: UNKNOWN
Autor: M. Krilanovich
RFC0437 Data Reconfiguration Service at UCSB
June 1973
Status: UNKNOWN
Autor: E. Faeh
RFC0438 FTP server-server interaction
January 1973
Status: UNKNOWN
Autor: R. Thomas, R. Clements
RFC0439 PARRY encounters the DOCTOR
January 1973
Status: UNKNOWN
Autor: V. Cerf
RFC0440 Scheduled network software maintenance
January 1973
Status: UNKNOWN
Autor: D.C. Walden
RFC0441 Inter-Entity Communication - an experiment
January 1973
Status: UNKNOWN
Autor: R.D. Bressler, R. Thomas
RFC0442 Current flow-control scheme for IMPSYS
January 1973
Status: UNKNOWN
Autor: V. Cerf
RFC0443 Traffic statistics (December 1972)
January 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0445 IMP/TIP preventive maintenance schedule
January 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0446 Proposal to consider a network program resource notebook
January 1973
Status: UNKNOWN
Autor: L.P. Deutsch
RFC0447 IMP/TIP memory retrofit schedule
January 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0448 Print files in FTP
February 1973
Status: UNKNOWN
Autor: R.T. Braden
RFC0449 Current flow-control scheme for IMPSYS
January 1973
Status: UNKNOWN
Autor: D.C. Walden
RFC0450 MULTICS sampling timeout change
February 1973
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0451 Tentative proposal for a Unified User Level Protocol
February 1973
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0452 TELNET Command at Host LL
February 1973
Status: UNKNOWN
Autor: J. Winett
RFC0453 Meeting announcement to discuss a network mail system
February 1973
Status: UNKNOWN
Autor: M.D. Kudlick
RFC0454 File Transfer Protocol - meeting announcement and a new proposed document
February 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0455 Traffic statistics (January 1973)
February 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0456 Memorandum: Date change of mail meeting
February 1973
Status: UNKNOWN
Autor: M.D. Kudlick
RFC0457 TIPUG
February 1973
Status: UNKNOWN
Autor: D.C. Walden
RFC0458 Mail retrieval via FTP
February 1973
Status: UNKNOWN
Autor: R.D. Bressler, R. Thomas
RFC0459 Network questionnaires
February 1973
Status: UNKNOWN
Autor: W. Kantrowitz
RFC0460 NCP survey
February 1973
Status: UNKNOWN
Autor: C. Kline
RFC0461 Telnet Protocol meeting announcement
February 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0462 Responding to user needs
February 1973
Status: UNKNOWN
Autor: J. Iseli, D. Crocker
RFC0463 FTP comments and response to RFC 430
February 1973
Status: UNKNOWN
Autor: A.K. Bhushan
RFC0464 Resource notebook framework
February 1973
Status: UNKNOWN
Autor: M.D. Kudlick
RFC0466 Telnet logger/server for host LL-67
February 1973
Status: UNKNOWN
Autor: J.M. Winett
RFC0467 Proposed change to Host-Host Protocol: Resynchronization of connection status
February 1973
Status: UNKNOWN
Autor: J.D. Burchfiel, R.S. Tomlinson
RFC0468 FTP data compression
March 1973
Status: UNKNOWN
Autor: R.T. Braden
RFC0469 Network mail meeting summary
March 1973
Status: UNKNOWN
Autor: M.D. Kudlick
RFC0470 Change in socket for TIP news facility
March 1973
Status: UNKNOWN
Autor: R. Thomas
RFC0471 Workshop on multi-site executive programs
March 1973
Status: UNKNOWN
Autor: R. Thomas
RFC0472 Illinois' reply to Maxwell's request for graphics information (NIC 14925)
March 1973
Status: UNKNOWN
Autor: S. Bunch
RFC0473 MIX and MIXAL?
February 1973
Status: UNKNOWN
Autor: D.C. Walden
RFC0474 Announcement of NGWG meeting: Call for papers
March 1973
Status: UNKNOWN
Autor: S. Bunch
RFC0475 FTP and Network Mail System
March 1973
Status: UNKNOWN
Autor: A.K. Bhushan
RFC0476 IMP/TIP memory retrofit schedule (rev 2)
March 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0477 Remote Job Service at UCSB
May 1973
Status: UNKNOWN
Autor: M. Krilanovich
RFC0478 FTP server-server interaction - II
March 1973
Status: UNKNOWN
Autor: R.D. Bressler, R. Thomas
RFC0479 Use of FTP by the NIC Journal
March 1973
Status: UNKNOWN
Autor: J.E. White
RFC0480 Host-dependent FTP parameters
March 1973
Status: UNKNOWN
Autor: J.E. White
RFC0482 Traffic statistics (February 1973)
March 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0483 Cancellation of the resource notebook framework meeting
March 1973
Status: UNKNOWN
Autor: M.D. Kudlick
RFC0485 MIX and MIXAL at UCSB
March 1973
Status: UNKNOWN
Autor: J.R. Pickens
RFC0486 Data transfer revisited
March 1973
Status: UNKNOWN
Autor: R.D. Bressler
RFC0487 Free file transfer
April 1973
Status: UNKNOWN
Autor: R.D. Bressler
RFC0488 NLS classes at network sites
March 1973
Status: UNKNOWN
Autor: M.F. Auerbach
RFC0489 Comment on resynchronization of connection status proposal
March 1973
Status: UNKNOWN
Autor: J. Postel
RFC0490 Surrogate RJS for UCLA-CCN
March 1973
Status: UNKNOWN
Autor: J.R. Pickens
RFC0491 What is "Free"?
April 1973
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0492 Response to RFC 467
April 1973
Status: UNKNOWN
Autor: E. Meyer
RFC0493 GRAPHICS PROTOCOL
April 1973
Status: UNKNOWN
Autor: J.C. Michener, I.W. Cotton, K.C. Kelley, D.E. Liddle, E. Meyer
RFC0494 Availability of MIX and MIXAL in the Network
April 1973
Status: UNKNOWN
Autor: D.C. Walden
RFC0495 Telnet Protocol specifications
May 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0496 TNLS quick reference card is available
April 1973
Status: UNKNOWN
Autor: M.F. Auerbach
RFC0497 Traffic Statistics (March 1973)
April 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0498 On mail service to CCN
April 1973
Status: UNKNOWN
Autor: R.T. Braden
RFC0499 Harvard's network RJE
April 1973
Status: UNKNOWN
Autor: B.R. Reussow
RFC0500 Integration of data management systems on a computer network
April 1973
Status: UNKNOWN
Autor: A. Shoshani, I. Spiegler
RFC0501 Un-muddling "free file transfer"
May 1973
Status: UNKNOWN
Autor: K.T. Pogran
RFC0503 Socket number list
April 1973
Status: UNKNOWN
Autor: N. Neigus, J. Postel
RFC0504 Distributed resources workshop announcement
April 1973
Status: UNKNOWN
Autor: R. Thomas
RFC0505 Two solutions to a file transfer access problem
June 1973
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0506 FTP command naming problem
June 1973
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0508 Real-time data transmission on the ARPANET
May 1973
Status: UNKNOWN
Autor: L. Pfeifer, J. McAfee
RFC0509 Traffic statistics (April 1973)
April 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0510 Request for network mailbox addresses
May 1973
Status: UNKNOWN
Autor: J.E. White
RFC0511 Enterprise phone service to NIC from ARPANET sites
May 1973
Status: UNKNOWN
Autor: J.B. North
RFC0512 More on lost message detection
May 1973
Status: UNKNOWN
Autor: W. Hathaway
RFC0513 Comments on the new Telnet specifications
May 1973
Status: UNKNOWN
Autor: W. Hathaway
RFC0514 Network make-work
June 1973
Status: UNKNOWN
Autor: W. Kantrowitz
RFC0515 Specifications for Datalanguage, Version 0/9
June 1973
Status: UNKNOWN
Autor: R. Winter
RFC0516 Lost message detection
May 1973
Status: UNKNOWN
Autor: J. Postel
RFC0518 ARPANET accounts
June 1973
Status: UNKNOWN
Autor: N. Vaughan, E.J. Feinler
RFC0519 Resource Evaluation
June 1973
Status: UNKNOWN
Autor: J.R. Pickens
RFC0520 Memo to FTP group: Proposal for File Access Protocol
June 1973
Status: UNKNOWN
Autor: J.D. Day
RFC0521 Restricted use of IMP DDT
May 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0522 Traffic Statistics (May 1973)
June 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0523 SURVEY is in operation again
June 1973
Status: UNKNOWN
Autor: A.K. Bhushan
RFC0524 Proposed Mail Protocol
June 1973
Status: UNKNOWN
Autor: J.E. White
RFC0525 MIT-MATHLAB meets UCSB-OLS -an example of resource sharing
June 1973
Status: UNKNOWN
Autor: W. Parrish, J.R. Pickens
RFC0526 Technical meeting: Digital image processing software systems
June 1973
Status: UNKNOWN
Autor: W.K. Pratt
RFC0527 ARPAWOCKY
May 1973
Status: UNKNOWN
Autor: R. Merryman
RFC0528 Software checksumming in the IMP and network reliability
June 1973
Status: UNKNOWN
Autor: J.M. McQuillan
RFC0529 Note on protocol synch sequences
June 1973
Status: UNKNOWN
Autor: A.M. McKenzie, R. Thomas, R.S. Tomlinson, K.T. Pogran
RFC0530 Report on the Survey Project
June 1973
Status: UNKNOWN
Autor: A.K. Bhushan
RFC0531 Feast or famine? A response to two recent RFC's about network information
June 1973
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0532 UCSD-CC Server-FTP facility
July 1973
Status: UNKNOWN
Autor: R.G. Merryman
RFC0533 Message-ID numbers
July 1973
Status: UNKNOWN
Autor: D.C. Walden
RFC0534 Lost message detection
July 1973
Status: UNKNOWN
Autor: D.C. Walden
RFC0535 Comments on File Access Protocol
July 1973
Status: UNKNOWN
Autor: R. Thomas
RFC0537 Announcement of NGG meeting July 16-17
June 1973
Status: UNKNOWN
Autor: S. Bunch
RFC0538 Traffic statistics (June 1973)
July 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0539 Thoughts on the mail protocol proposed in RFC 524
July 1973
Status: UNKNOWN
Autor: D. Crocker, J. Postel
RFC0542 File Transfer Protocol
August 1973
Status: UNKNOWN
Autor: N. Neigus
RFC0543 Network journal submission and delivery
July 1973
Status: UNKNOWN
Autor: N.D. Meyer
RFC0544 Locating on-line documentation at SRI-ARC
July 1973
Status: UNKNOWN
Autor: N.D. Meyer, K. Kelley
RFC0545 Of what quality be the UCSB resources evaluators?
July 1973
Status: UNKNOWN
Autor: J.R. Pickens
RFC0546 Tenex load averages for July 1973
August 1973
Status: UNKNOWN
Autor: R. Thomas
RFC0547 Change to the Very Distant Host specification
August 1973
Status: UNKNOWN
Autor: D.C. Walden
RFC0548 Hosts using the IMP Going Down message
August 1973
Status: UNKNOWN
Autor: D.C. Walden
RFC0549 Minutes of Network Graphics Group meeting, 15-17 July 1973
July 1973
Status: UNKNOWN
Autor: J.C. Michener
RFC0550 NIC NCP experiment
August 1973
Status: UNKNOWN
Autor: L.P. Deutsch
RFC0551 NYU, ANL, and LBL Joining the Net
August 1973
Status: UNKNOWN
Autor: Y. Feinroth, R. Fink
RFC0552 Single access to standard protocols
July 1973
Status: UNKNOWN
Autor: A.D. Owen
RFC0553 Draft design for a text/graphics protocol
July 1973
Status: UNKNOWN
Autor: C.H. Irby, K. Victor
RFC0555 Responses to critiques of the proposed mail protocol
July 1973
Status: UNKNOWN
Autor: J.E. White
RFC0556 Traffic Statistics (July 1973)
August 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0557 REVELATIONS IN NETWORK HOST MEASUREMENTS
August 1973
Status: UNKNOWN
Autor: B.D. Wessler
RFC0559 Comments on The New Telnet Protocol and its Implementation
August 1973
Status: UNKNOWN
Autor: A.K. Bushan
RFC0560 Remote Controlled Transmission and Echoing Telnet option
August 1973
Status: UNKNOWN
Autor: D. Crocker, J. Postel
RFC0561 Standardizing Network Mail Headers
September 1973
Status: UNKNOWN
Autor: A.K. Bhushan, K.T. Pogran, R.S. Tomlinson, J.E. White
RFC0562 Modifications to the TELNET Specification
August 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0563 Comments on the RCTE Telnet option
August 1973
Status: UNKNOWN
Autor: J. Davidson
RFC0565 Storing network survey data at the datacomputer
August 1973
Status: UNKNOWN
Autor: D. Cantor
RFC0566 Traffic statistics (August 1973)
September 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0567 Cross Country Network Bandwidth
September 1973
Status: UNKNOWN
Autor: L.P. Deutsch
RFC0568 Response to RFC 567 - cross country network bandwidth
September 1973
Status: UNKNOWN
Autor: J.M. McQuillan
RFC0569 NETED: A Common Editor for the ARPA Network
October 1973
Status: HISTORIC
Autor: M.A. Padlipsky
RFC0570 Experimental input mapping between NVT ASCII and UCSB On Line System
October 1973
Status: UNKNOWN
Autor: J.R. Pickens
RFC0571 TENEX FTP PROBLEM
November 1973
Status: UNKNOWN
Autor: R. Braden
RFC0573 DATA AND FILE TRANSFER - SOME MEASUREMENT RESULTS
September 1973
Status: UNKNOWN
Autor: A. Bhushan
RFC0574 Announcement of a Mail Facility at UCSB
September 1973
Status: UNKNOWN
Autor: M. Krilanovich
RFC0576 Proposal for modifying linking
September 1973
Status: UNKNOWN
Autor: K. Victor
RFC0577 Mail priority
October 1973
Status: UNKNOWN
Autor: D. Crocker
RFC0578 Using MIT-Mathlab MACSYMA from MIT-DMS Muddle
October 1973
Status: UNKNOWN
Autor: A.K. Bhushan, N.D. Ryan
RFC0579 Traffic statistics (September 1973)
November 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0580 Note to Protocol Designers and Implementers
October 1973
Status: UNKNOWN
Autor: J. Postel
RFC0581 Corrections to RFC 560: Remote Controlled Transmission and Echoing Telnet Option
November 1973
Status: UNKNOWN
Autor: D. Crocker, J. Postel
RFC0582 Comments on RFC 580: Machine readable protocols
November 1973
Status: UNKNOWN
Autor: R. Clements
RFC0584 Charter for ARPANET Users Interest Working Group
November 1973
Status: UNKNOWN
Autor: J. Iseli, D. Crocker, N. Neigus
RFC0585 ARPANET users interest working group meeting
November 1973
Status: UNKNOWN
Autor: D. Crocker, N. Neigus, E.J. Feinler, J. Iseli
RFC0586 Traffic statistics (October 1973)
November 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0587 Announcing New Telnet Options
November 1973
Status: UNKNOWN
Autor: J. Postel
RFC0588 London Node Is Now Up
October 1973
Status: UNKNOWN
Autor: A. Stokes
RFC0589 CCN NETRJS server messages to remote user
November 1973
Status: UNKNOWN
Autor: R.T. Braden
RFC0590 MULTICS address change
November 1973
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0591 Addition to the Very Distant Host specifications
November 1973
Status: UNKNOWN
Autor: D.C. Walden
RFC0592 Some thoughts on system design to facilitate resource sharing
November 1973
Status: UNKNOWN
Autor: R.W. Watson
RFC0593 Telnet and FTP implementation schedule change
November 1973
Status: UNKNOWN
Autor: A.M. McKenzie, J. Postel
RFC0594 Speedup of Host-IMP interface
December 1973
Status: UNKNOWN
Autor: J.D. Burchfiel
RFC0595 Second thoughts in defense of the Telnet Go-Ahead
December 1973
Status: UNKNOWN
Autor: W. Hathaway
RFC0596 Second thoughts on Telnet Go-Ahead
December 1973
Status: UNKNOWN
Autor: E.A. Taft
RFC0597 Host status
December 1973
Status: UNKNOWN
Autor: N. Neigus, E.J. Feinler
RFC0598 RFC index - December 5, 1973
December 1973
Status: UNKNOWN
Autor: Network Information Center. Stanford Research Institute
RFC0599 Update on NETRJS
December 1973
Status: UNKNOWN
Autor: R.T. Braden
RFC0600 Interfacing an Illinois plasma terminal to the ARPANET
Discusses some unusual interface issues for the Plato terminal.
November 1973
Status: UNKNOWN
Autor: A. Berggreen
RFC0601 Traffic statistics (November 1973)
December 1973
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0602 "The stockings were hung by the chimney with care"
Susceptibility of ARPANET to security violations.
December 1973
Status: UNKNOWN
Autor: R.M. Metcalfe
RFC0603 Response to RFC 597: Host status
Questions about the ARPANET topology described in RFC 597.
December 1973
Status: UNKNOWN
Autor: J.D. Burchfiel
RFC0604 Assigned link numbers
Modifies official host-host protocol. Replaces RFC 377.
December 1973
Status: UNKNOWN
Autor: J. Postel
RFC0606 Host names on-line
Resolving differences in hostname-address mappings; see also RFCs 627, 625, 623 and 608.
December 1973
Status: UNKNOWN
Autor: L.P. Deutsch
RFC0607 Comments on the File Transfer Protocol
An old version; see RFC 624; see also RFCs 614, 542 and 640.
January 1974
Status: UNKNOWN
Autor: M. Krilanovich, G. Gregg
RFC0608 Host names on-line
Response to RFC 606; see also RFCs 627, 625 and 623.
January 1974
Status: UNKNOWN
Autor: M.D. Kudlick
RFC0609 Statement of upcoming move of NIC/NLS service
See also RFCs 621 and 620.
January 1974
Status: UNKNOWN
Autor: B. Ferguson
RFC0610 Further datalanguage design concepts
Preliminary results of the language design; a model for data languagea semantics; future considerations.
December 1973
Status: UNKNOWN
Autor: R. Winter, J. Hill, W. Greiff
RFC0611 Two changes to the IMP/Host Protocol to improve user/network communications
Expansion of Host-Going-Down and addition of Dead-Host-Status Message.
February 1974
Status: UNKNOWN
Autor: D.C. Walden
RFC0612 Traffic statistics (December 1973)
January 1974
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0613 Network connectivity: A response to RFC 603
January 1974
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0614 Response to RFC 607: "Comments on the File Transfer Protocol"
See also RFCs 624, 542 and 640.
January 1974
Status: UNKNOWN
Autor: K.T. Pogran, N. Neigus
RFC0615 Proposed Network Standard Data Pathname syntax
March 1974
Status: UNKNOWN
Autor: D. Crocker
RFC0616 LATEST NETWORK MAPS
February 1973
Status: UNKNOWN
Autor: D. Walden
RFC0617 Note on socket number assignment
Danger of imposing more fixed socket number requirements; see also RFCs 542, 503 and 451.
February 1974
Status: UNKNOWN
Autor: E.A. Taft
RFC0618 Few observations on NCP statistics
Distribution of NCP and IMP message types by actual measurement.
February 1974
Status: UNKNOWN
Autor: E.A. Taft
RFC0619 Mean round-trip times in the ARPANET
Actual measurements of round-trip times.
March 1974
Status: UNKNOWN
Autor: W. Naylor, H. Opderbeck
RFC0620 Request for monitor host table updates
In conjunction with moving NIC users to OFFICE-1; see also RFCs 621 and 609.
March 1974
Status: UNKNOWN
Autor: B. Ferguson
RFC0621 NIC user directories at SRI ARC
See also RFCs 620 and 609.
March 1974
Status: UNKNOWN
Autor: M.D. Kudlick
RFC0622 Scheduling IMP/TIP down time
Modification of previous policy.
March 1974
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0623 Comments on on-line host name service
See also RFCs 627, 625, 608 and 606.
February 1974
Status: UNKNOWN
Autor: M. Krilanovich
RFC0624 Comments on the File Transfer Protocol
Design changes and slight modifications. Replaces RFC 607; see also RFCs 614, 542 and 640.
February 1974
Status: UNKNOWN
Autor: M. Krilanovich, G. Gregg, W. Hathaway, J.E. White
RFC0625 On-line hostnames service
See also RFCs 606, 608, 623 and 627.
March 1974
Status: UNKNOWN
Autor: M.D. Kudlick, E.J. Feinler
RFC0626 On a possible lockup condition in IMP subnet due to message sequencing
March 1974
Status: UNKNOWN
Autor: L. Kleinrock, H. Opderbeck
RFC0627 ASCII text file of hostnames
See also RFCs 606, 608, 623 and 625.
March 1974
Status: UNKNOWN
Autor: M.D. Kudlick, E.J. Feinler
RFC0628 Status of RFC numbers and a note on pre-assigned journal numbers
March 1974
Status: UNKNOWN
Autor: M.L. Keeney
RFC0629 Scenario for using the Network Journal
March 1974
Status: UNKNOWN
Autor: J.B. North
RFC0630 FTP error code usage for more reliable mail service
Describes FTP reply-code usage in TENEX mail processing.
April 1974
Status: UNKNOWN
Autor: J. Sussman
RFC0631 International meeting on minicomputers and data communication: Call for papers
April 1974
Status: UNKNOWN
Autor: A. Danthine
RFC0632 Throughput degradations for single packet messages
May 1974
Status: UNKNOWN
Autor: H. Opderbeck
RFC0633 IMP/TIP preventive maintenance schedule
An old version; see RFC 638.
March 1974
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0634 Change in network address for Haskins Lab
April 1974
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0635 Assessment of ARPANET protocols
Theoretical and practical motivation for redesign. Multipacket messages; host retransmission; duplicate detection; sequencing; acknowledgement.
April 1974
Status: UNKNOWN
Autor: V. Cerf
RFC0636 TIP/Tenex reliability improvements
Obtaining/maintaining connections; recovery from lost connections; connection-state changes.
June 1974
Status: UNKNOWN
Autor: J.D. Burchfiel, B. Cosell, R.S. Tomlinson, D.C. Walden
RFC0637 Change of network address for SU-DSL
April 1974
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0638 IMP/TIP preventive maintenance schedule
Corrects RFC 633.
April 1974
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0640 Revised FTP reply codes
Updates RFC 542.
June 1974
Status: UNKNOWN
Autor: J. Postel
RFC0642 Ready line philosophy and implementation
July 1974
Status: UNKNOWN
Autor: J.D. Burchfiel
RFC0643 Network Debugging Protocol
To be used in an implementation of a PDP-11 network bootstrap device and a cross-network debugger.
July 1974
Status: UNKNOWN
Autor: E. Mader
RFC0644 On the problem of signature authentication for network mail
July 1974
Status: UNKNOWN
Autor: R. Thomas
RFC0645 Network Standard Data Specification syntax
Providing a mechanism for specifying all attributes of a collection of bits; see also RFC 615.
June 1974
Status: UNKNOWN
Autor: D. Crocker
RFC0647 Proposed protocol for connecting host computers to ARPA-like networks via front end processors
Approaches to Front-End protocol processing using available hardware and software.
November 1974
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0651 Revised Telnet status option
October 1974
Status: UNKNOWN
Autor: D. Crocker
RFC0652 Telnet output carriage-return disposition option
October 1974
Status: HISTORIC
Autor: D. Crocker
RFC0653 Telnet output horizontal tabstops option
October 1974
Status: HISTORIC
Autor: D. Crocker
RFC0654 Telnet output horizontal tab disposition option
October 1974
Status: HISTORIC
Autor: D. Crocker
RFC0655 Telnet output formfeed disposition option
October 1974
Status: HISTORIC
Autor: D. Crocker
RFC0656 Telnet output vertical tabstops option
October 1974
Status: HISTORIC
Autor: D. Crocker
RFC0657 Telnet output vertical tab disposition option
October 1974
Status: HISTORIC
Autor: D. Crocker
RFC0658 Telnet output linefeed disposition
October 1974
Status: HISTORIC
Autor: D. Crocker
RFC0659 Announcing additional Telnet options
Options defined in RFCs 651-658.
October 1974
Status: UNKNOWN
Autor: J. Postel
RFC0660 Some changes to the IMP and the IMP/Host interface
Decoupling of message number sequences of hosts; host-host access control; message number window; messages outside normal mechanism; see also BBN 1822.
October 1974
Status: UNKNOWN
Autor: D.C. Walden
RFC0661 Protocol information
An old version; see RFC 694.
November 1974
Status: UNKNOWN
Autor: J. Postel
RFC0662 Performance improvement in ARPANET file transfers from Multics
Experimenting with host output buffers to improve throughput.
November 1974
Status: UNKNOWN
Autor: R. Kanodia
RFC0663 Lost message detection and recovery protocol
Proposed extension of host-host protocol; see also RFCs 534, 516, 512, 492 and 467.
November 1974
Status: UNKNOWN
Autor: R. Kanodia
RFC0666 Specification of the Unified User-Level Protocol
Discusses and proposes a common command language.
November 1974
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0667 Host Ports
Approved scheme to connect host ports to the network.
December 1974
Status: UNKNOWN
Autor: S.G. Chipman
RFC0669 November, 1974, survey of New-Protocol Telnet servers
An earlier poll of Telnet server implementation status. Updates RFC 702; see also RFCs 703 and 679.
December 1974
Status: UNKNOWN
Autor: D.W. Dodds
RFC0671 Note on Reconnection Protocol
Experience with implementation in RSEXEC context.
December 1974
Status: UNKNOWN
Autor: R. Schantz
RFC0672 Multi-site data collection facility
Applicability of TIP/TENEX protocols beyond TIP accounting.
December 1974
Status: UNKNOWN
Autor: R. Schantz
RFC0674 Procedure call documents: Version 2
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.
December 1974
Status: UNKNOWN
Autor: J. Postel, J.E. White
RFC0675 Specification of Internet Transmission Control Program
The first detailed specification of TCP; see RFC 793.
December 1974
Status: UNKNOWN
Autor: V. Cerf, Y. Dalal, C. Sunshine
RFC0677 Maintenance of duplicate databases
January 1975
Status: UNKNOWN
Autor: P.R. Johnson, R. Thomas
RFC0678 Standard file formats
For transmission of documents across different environments.
December 1974
Status: UNKNOWN
Autor: J. Postel
RFC0679 February, 1975, survey of New-Protocol Telnet servers
An earlier poll of Telnet server implementation status. Updates RFCs 701, 702 and 669; see also RFC 703.
February 1975
Status: UNKNOWN
Autor: D.W. Dodds
RFC0680 Message Transmission Protocol
Extends message field definition beyond RFC 561 attempts to establish syntactic and semantic standards for ARPANET; see also RFCs 733 and 822.
April 1975
Status: UNKNOWN
Autor: T.H. Myer, D.A. Henderson
RFC0681 Network UNIX
Capabilities as an ARPANET Mini-Host: standard I/O, Telnet, NCP, Hardware/Software requirements, reliability, availability.
March 1975
Status: UNKNOWN
Autor: S. Holmgren
RFC0683 FTPSRV - Tenex extension for paged files
Defines an extension to FTP for page-mode transfers between TENEX systems; also discusses file transfer reliability.
April 1975
Status: UNKNOWN
Autor: R. Clements
RFC0684 Commentary on procedure calling as a network protocol
Issues in designing distributed computing systems. Shortcomings of RFC 674; see also RFCs 542 and 354.
April 1975
Status: UNKNOWN
Autor: R. Schantz
RFC0685 Response time in cross network debugging
The contribution of ARPANET communication to response time.
April 1975
Status: UNKNOWN
Autor: M. Beeler
RFC0686 Leaving well enough alone
Discusses difference between early and later versions of FTP; see also RFCs 691, 640, 630, 542, 454, 448, 414, 385 and 354.
May 1975
Status: UNKNOWN
Autor: B. Harvey
RFC0687 IMP/Host and Host/IMP Protocol changes
Addressing hosts on more than 63 IMPs, and other backwards compatible expansions; see also RFCs 690 and 692.
June 1975
Status: UNKNOWN
Autor: D.C. Walden
RFC0688 Tentative schedule for the new Telnet implementation for the TIP
June 1975
Status: UNKNOWN
Autor: D.C. Walden
RFC0689 Tenex NCP finite state machine for connections
Describes the internal states of an NCP connection in the TENEX implementation.
May 1975
Status: UNKNOWN
Autor: R. Clements
RFC0690 Comments on the proposed Host/IMP Protocol changes
Comments on suggestions in RFC 687; see also RFCs 692 and 696.
June 1975
Status: UNKNOWN
Autor: J. Postel
RFC0691 One more try on the FTP
Slight revision of RFC 686, on the subject of print files; see also RFCs 640, 630, 542, 454, 448, 414, 385 and 354.
June 1975
Status: UNKNOWN
Autor: B. Harvey
RFC0692 Comments on IMP/Host Protocol changes (RFCs 687 and 690)
A proposed solution to the problem of combined length of IMP and Host leaders; see also RFCs 696, 690 and 687.
June 1975
Status: UNKNOWN
Autor: S.M. Wolfe
RFC0694 Protocol information
References to documents and contacts concerning the various protocols used in the ARPANET, as well as recent developments; updates RFC 661.
June 1975
Status: UNKNOWN
Autor: J. Postel
RFC0695 Official change in Host-Host Protocol
Corrects ambiguity concerning the ERR command; changes NIC 8246 and NIC 7104.
July 1975
Status: UNKNOWN
Autor: M. Krilanovich
RFC0696 Comments on the IMP/Host and Host/IMP Protocol changes
Observations on current international standards recommendations from IFIP working group 6.1; see also RFCs 692, 690, 687.
July 1975
Status: UNKNOWN
Autor: V.G. Cerf
RFC0697 CWD command of FTP
Discusses FTP login access to "files only" directories.
July 1975
Status: UNKNOWN
Autor: J. Lieb
RFC0698 Telnet extended ASCII option
Describes an option to allow transmission of a special kind of extended ASCII used at the Stanford AI and MIT AI Labs.
July 1975
Status: PROPOSED STANDARD
Autor: T. Mock
RFC0699 Request For Comments summary notes: 600-699
November 1982
Status: INFORMATIONAL
Autor: J. Postel, J. Vernon
RFC0700 Protocol experiment
August 1974
Status: UNKNOWN
Autor: E. Mader, W.W. Plummer, R.S. Tomlinson
RFC0701 August, 1974, survey of New-Protocol Telnet servers
August 1974
Status: UNKNOWN
Autor: D.W. Dodds
RFC0702 September, 1974, survey of New-Protocol Telnet servers
September 1974
Status: UNKNOWN
Autor: D.W. Dodds
RFC0703 July, 1975, survey of New-Protocol Telnet Servers
July 1975
Status: UNKNOWN
Autor: D.W. Dodds
RFC0704 IMP/Host and Host/IMP Protocol change
September 1975
Status: UNKNOWN
Autor: P.J. Santos
RFC0705 Front-end Protocol B6700 version
November 1975
Status: UNKNOWN
Autor: R.F. Bryan
RFC0706 On the junk mail problem
November 1975
Status: UNKNOWN
Autor: J. Postel
RFC0707 High-level framework for network-based resource sharing
December 1975
Status: UNKNOWN
Autor: J.E. White
RFC0708 Elements of a Distributed Programming System
January 1976
Status: UNKNOWN
Autor: J.E. White
RFC0712 Distributed Capability Computing System (DCCS)
February 1976
Status: UNKNOWN
Autor: J.E. Donnelley
RFC0713 MSDTP-Message Services Data Transmission Protocol
April 1976
Status: UNKNOWN
Autor: J. Haverty
RFC0714 Host-Host Protocol for an ARPANET-Type Network
April 1976
Status: UNKNOWN
Autor: A.M. McKenzie
RFC0716 Interim Revision to Appendix F of BBN 1822
May 1976
Status: UNKNOWN
Autor: D.C. Walden, J. Levin
RFC0717 Assigned Network Numbers
July 1976
Status: HISTORIC
Autor: J. Postel
RFC0718 Comments on RCTE from the Tenex Implementation Experience
June 1976
Status: UNKNOWN
Autor: J. Postel
RFC0719 Discussion on RCTE
July 1976
Status: UNKNOWN
Autor: J. Postel
RFC0720 Address Specification Syntax for Network Mail
August 1976
Status: UNKNOWN
Autor: D. Crocker
RFC0721 Out-of-Band Control Signals in a Host-to-Host Protocol
September 1976
Status: UNKNOWN
Autor: L.L. Garlick
RFC0722 Thoughts on Interactions in Distributed Services
September 1976
Status: UNKNOWN
Autor: J. Haverty
RFC0724 Proposed official standard for the format of ARPA Network messages
May 1977
Status: UNKNOWN
Autor: D. Crocker, K.T. Pogran, J. Vittal, D.A. Henderson
RFC0725 RJE protocol for a resource sharing network
March 1977
Status: UNKNOWN
Autor: J.D. Day, G.R. Grossman
RFC0726 Remote Controlled Transmission and Echoing Telnet option
March 1977
Status: PROPOSED STANDARD
Autor: J. Postel, D. Crocker
RFC0727 Telnet logout option
April 1977
Status: PROPOSED STANDARD
Autor: M.R. Crispin
RFC0728 Minor pitfall in the Telnet Protocol
April 1977
Status: UNKNOWN
Autor: J.D. Day
RFC0729 Telnet byte macro option
May 1977
Status: UNKNOWN
Autor: D. Crocker
RFC0730 Extensible field addressing
May 1977
Status: UNKNOWN
Autor: J. Postel
RFC0731 Telnet Data Entry Terminal option
June 1977
Status: UNKNOWN
Autor: J.D. Day
RFC0732 Telnet Data Entry Terminal option
September 1977
Status: UNKNOWN
Autor: J.D. Day
RFC0733 Standard for the format of ARPA network text messages
November 1977
Status: UNKNOWN
Autor: D. Crocker, J. Vittal, K.T. Pogran, D.A. Henderson
RFC0734 SUPDUP Protocol
October 1977
Status: HISTORIC
Autor: M.R. Crispin
RFC0735 Revised Telnet byte macro option
November 1977
Status: PROPOSED STANDARD
Autor: D. Crocker, R.H. Gumpertz
RFC0736 Telnet SUPDUP option
October 1977
Status: PROPOSED STANDARD
Autor: M.R. Crispin
RFC0737 FTP extension: XSEN
October 1977
Status: UNKNOWN
Autor: K. Harrenstien
RFC0738 Time server
October 1977
Status: UNKNOWN
Autor: K. Harrenstien
RFC0739 Assigned numbers
November 1977
Status: HISTORIC
Autor: J. Postel
RFC0740 NETRJS Protocol
November 1977
Status: HISTORIC
Autor: R.T. Braden
RFC0741 Specifications for the Network Voice Protocol (NVP)
November 1977
Status: UNKNOWN
Autor: D. Cohen
RFC0742 NAME/FINGER Protocol
December 1977
Status: UNKNOWN
Autor: K. Harrenstien
RFC0743 FTP extension: XRSQ/XRCP
December 1977
Status: UNKNOWN
Autor: K. Harrenstien
RFC0744 MARS - a Message Archiving and Retrieval Service
January 1978
Status: UNKNOWN
Autor: J. Sattley
RFC0745 JANUS interface specifications
March 1978
Status: UNKNOWN
Autor: M. Beeler
RFC0746 SUPDUP graphics extension
March 1978
Status: UNKNOWN
Autor: R. Stallman
RFC0747 Recent extensions to the SUPDUP Protocol
March 1978
Status: UNKNOWN
Autor: M.R. Crispin
RFC0748 Telnet randomly-lose option
April 1978
Status: UNKNOWN
Autor: M.R. Crispin
RFC0749 Telnet SUPDUP-Output option
September 1978
Status: PROPOSED STANDARD
Autor: B. Greenberg
RFC0750 Assigned numbers
September 1978
Status: HISTORIC
Autor: J. Postel
RFC0751 Survey of FTP mail and MLFL
December 1978
Status: UNKNOWN
Autor: P.D. Lebling
RFC0752 Universal host table
January 1979
Status: UNKNOWN
Autor: M.R. Crispin
RFC0753 Internet Message Protocol
March 1979
Status: UNKNOWN
Autor: J. Postel
RFC0754 Out-of-net host addresses for mail
April 1979
Status: UNKNOWN
Autor: J. Postel
RFC0755 Assigned numbers
May 1979
Status: HISTORIC
Autor: J. Postel
RFC0756 NIC name server - a datagram-based information utility
July 1979
Status: UNKNOWN
Autor: J.R. Pickens, E.J. Feinler, J.E. Mathis
RFC0757 Suggested solution to the naming, addressing, and delivery problem for ARPANET message systems
September 1979
Status: UNKNOWN
Autor: D.P. Deutsch
RFC0758 Assigned numbers
August 1979
Status: HISTORIC
Autor: J. Postel
RFC0759 Internet Message Protocol
August 1980
Status: HISTORIC
Autor: J. Postel
RFC0760 DoD standard Internet Protocol
January 1980
Status: UNKNOWN
Autor: J. Postel
RFC0761 DoD standard Transmission Control Protocol
January 1980
Status: UNKNOWN
Autor: J. Postel
RFC0762 Assigned numbers
January 1980
Status: HISTORIC
Autor: J. Postel
RFC0763 Role mailboxes
May 1980
Status: UNKNOWN
Autor: M.D. Abrams
RFC0764 Telnet Protocol specification
June 1980
Status: UNKNOWN
Autor: J. Postel
RFC0765 File Transfer Protocol specification
June 1980
Status: UNKNOWN
Autor: J. Postel
RFC0766 Internet Protocol Handbook: Table of contents
July 1980
Status: UNKNOWN
Autor: J. Postel
RFC0767 Structured format for transmission of multi-media documents
August 1980
Status: UNKNOWN
Autor: J. Postel
RFC0768 User Datagram Protocol
August 1980
Status: STANDARD
Autor: J. Postel
RFC0769 Rapicom 450 facsimile file format
September 1980
Status: UNKNOWN
Autor: J. Postel
RFC0770 Assigned numbers
September 1980
Status: HISTORIC
Autor: J. Postel
RFC0771 Mail transition plan
September 1980
Status: UNKNOWN
Autor: V.G. Cerf, J. Postel
RFC0772 Mail Transfer Protocol
September 1980
Status: UNKNOWN
Autor: S. Sluizer, J. Postel
RFC0773 Comments on NCP/TCP mail service transition strategy
October 1980
Status: UNKNOWN
Autor: V.G. Cerf
RFC0774 Internet Protocol Handbook: Table of contents
October 1980
Status: UNKNOWN
Autor: J. Postel
RFC0775 Directory oriented FTP commands
December 1980
Status: UNKNOWN
Autor: D. Mankins, D. Franklin, A.D. Owen
RFC0776 Assigned numbers
January 1981
Status: HISTORIC
Autor: J. Postel
RFC0777 Internet Control Message Protocol
April 1981
Status: UNKNOWN
Autor: J. Postel
RFC0778 DCNET Internet Clock Service
April 1981
Status: HISTORIC
Autor: D.L. Mills
RFC0779 Telnet send-location option
April 1981
Status: PROPOSED STANDARD
Autor: E. Killian
RFC0780 Mail Transfer Protocol
May 1981
Status: UNKNOWN
Autor: S. Sluizer, J. Postel
RFC0781 Specification of the Internet Protocol (IP) timestamp option
May 1981
Status: UNKNOWN
Autor: Z. Su
RFC0782 Virtual Terminal management model
January 1981
Status: UNKNOWN
Autor: J. Nabielsky, A.P. Skelton
RFC0783 TFTP Protocol (revision 2)
June 1981
Status: UNKNOWN
Autor: K.R. Sollins
RFC0784 Mail Transfer Protocol: ISI TOPS20 implementation
July 1981
Status: UNKNOWN
Autor: S. Sluizer, J. Postel
RFC0785 Mail Transfer Protocol: ISI TOPS20 file definitions
July 1981
Status: UNKNOWN
Autor: S. Sluizer, J. Postel
RFC0786 Mail Transfer Protocol: ISI TOPS20 MTP-NIMAIL interface
July 1981
Status: UNKNOWN
Autor: S. Sluizer, J. Postel
RFC0787 Connectionless data transmission survey/tutorial
July 1981
Status: UNKNOWN
Autor: A.L. Chapin
RFC0788 Simple Mail Transfer Protocol
November 1981
Status: UNKNOWN
Autor: J. Postel
RFC0789 Vulnerabilities of network control protocols: An example
July 1981
Status: UNKNOWN
Autor: E.C. Rosen
RFC0790 Assigned numbers
September 1981
Status: HISTORIC
Autor: J. Postel
RFC0791 Internet Protocol
September 1981
Status: STANDARD
Autor: J. Postel
RFC0792 Internet Control Message Protocol
September 1981
Status: STANDARD
Autor: J. Postel
RFC0793 Transmission Control Protocol
September 1981
Status: STANDARD
Autor: J. Postel
RFC0794 Pre-emption
September 1981
Status: UNKNOWN
Autor: V.G. Cerf
RFC0795 Service mappings
September 1981
Status: UNKNOWN
Autor: J. Postel
RFC0796 Address mappings
September 1981
Status: UNKNOWN
Autor: J. Postel
RFC0797 Format for Bitmap files
September 1981
Status: UNKNOWN
Autor: A.R. Katz
RFC0798 Decoding facsimile data from the Rapicom 450
September 1981
Status: UNKNOWN
Autor: A.R. Katz
RFC0799 Internet name domains
September 1981
Status: UNKNOWN
Autor: D.L. Mills
RFC0800 Request For Comments summary notes: 700-799
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.
November 1982
Status: INFORMATIONAL
Autor: J. Postel, J. Vernon
RFC0801 NCP/TCP transition plan
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.
November 1981
Status: UNKNOWN
Autor: J. Postel
RFC0802 ARPANET 1822L Host Access Protocol
This document proposed two major changes to the current ARPANET host access protocol. The first change will allow hosts to use logical addressing (i.e., host addresses that are independent of their physical location on the ARPANET) to communicate with each other, and the second will allow a host to shorten the amount of time that it may be blocked by its IMP after it presents a message to the network (currently, the IMP can block further input from a host for up to 15 seconds). See RFCs 852 and 851.
November 1981
Status: UNKNOWN
Autor: A.G. Malis
RFC0803 Dacom 450/500 facsimile data transcoding
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.
November 1981
Status: UNKNOWN
Autor: A. Agarwal, M.J. O'Connor, D.L. Mills
RFC0804 CCITT draft recommendation T.4
This is the CCITT standard for group 3 facsimile encoding. This is useful for data compression of bit map data.
January 1981
Status: UNKNOWN
Autor: International Telegraph and Telephone Consultative Committee of the International Telecommunication Union
RFC0805 Computer mail meeting notes
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.
February 1982
Status: UNKNOWN
Autor: J. Postel
RFC0806 Proposed Federal Information Processing Standard: Specification for message format for computer based message systems
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.
September 1981
Status: UNKNOWN
Autor: National Bureau of Standards
RFC0807 Multimedia mail meeting notes
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.
February 1982
Status: UNKNOWN
Autor: J. Postel
RFC0808 Summary of computer mail services meeting held at BBN on 10 January 1979
This RFC is a very belated attempt to document a meeting that was held three years earlier to discuss the state of computer mail in the ARPA community and to reach some conclusions to guide the further development of computer mail systems such that a coherent total mail service would continue to be provided.
March 1982
Status: UNKNOWN
Autor: J. Postel
RFC0809 UCL facsimile system
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.
February 1982
Status: UNKNOWN
Autor: T. Chang
RFC0810 DoD Internet host table specification
This RFC specifies a new host table format applicable to both ARPANET and Internet needs. In addition to host name to host address translation and selected protocol information, we have also included network and gateway name to address correspondence, and host operating system information. This RFC obsoletes the host table described in RFC 608.
March 1982
Status: UNKNOWN
Autor: E.J. Feinler, K. Harrenstien, Z. Su, V. White
RFC0811 Hostnames Server
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.
March 1982
Status: UNKNOWN
Autor: K. Harrenstien, V. White, E.J. Feinler
RFC0812 NICNAME/WHOIS
This RFC gives a description of what the NICNAME/WHOIS Server is and how to access it. This server together with the corresponding Identification Data Base provides online directory look-up equivalent to the ARPANET Directory.
March 1982
Status: UNKNOWN
Autor: K. Harrenstien, V. White
RFC0813 Window and Acknowledgement Strategy in TCP
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.
July 1982
Status: UNKNOWN
Autor: D.D. Clark
RFC0814 Name, addresses, ports, and routes
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.
July 1982
Status: UNKNOWN
Autor: D.D. Clark
RFC0815 IP datagram reassembly algorithms
This RFC describes an alternate approach of dealing with reassembly which reduces the bookkeeping problem to a minimum, and requires only one buffer for storage equal in size to the final datagram being reassembled, which can reassemble a datagram from any number of fragments arriving in any order with any possible pattern of overlap and duplication, and which is appropriate for almost any sort of operating system.
July 1982
Status: UNKNOWN
Autor: D.D. Clark
RFC0816 Fault isolation and recovery
This RFC describes the portion of fault isolation and recovery which is the responsibility of the host.
July 1982
Status: UNKNOWN
Autor: D.D. Clark
RFC0817 Modularity and efficiency in protocol implementation
This RFC will discuss some of the commonly encountered reasons why protocol implementations seem to run slowly.
July 1982
Status: UNKNOWN
Autor: D.D. Clark
RFC0818 Remote User Telnet service
This RFC is the specification of an application protocol. Any host that implements this application level service must follow this protocol.
November 1982
Status: HISTORIC
Autor: J. Postel
RFC0819 Domain naming convention for Internet user applications
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.
August 1982
Status: UNKNOWN
Autor: Z. Su, J. Postel
RFC0820 Assigned numbers
This RFC is an old version, see RFC 870.
August 1982
Status: HISTORIC
Autor: J. Postel
RFC0821 Simple Mail Transfer Protocol
The objective of Simple Mail Transfer Protocol (SMTP) is to transfer mail reliably and efficiently. SMTP is independent of the particular transmission subsystem and requires only a reliable ordered data stream channel. Obsoletes RFC 788, 780, and 772.
August 1982
Status: STANDARD
Autor: J. Postel
RFC0822 STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
This document revises the specifications in RFC 733, in order to serve the needs of the larger and more complex ARPA Internet. Some of RFC 733's features failed to gain adequate acceptance. In order to simplify the standard and the software that follows it, these features have been removed. A different addressing scheme is used, to handle the case of internetwork mail; and the concept of re-transmission has been introduced. Obsoletes RFC 733, NIC 41952.
August 1982
Status: STANDARD
Autor: D. Crocker
RFC0823 DARPA Internet gateway
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.
September 1982
Status: HISTORIC
Autor: R.M. Hinden, A. Sheltzer
RFC0824 CRONUS Virtual Local Network
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.
August 1982
Status: UNKNOWN
Autor: W.I. MacGregor, D.C. Tappan
RFC0825 Request for comments on Requests For Comments
This RFC is intended to clarify the status of RFCs and to provide some guidance for the authors of RFCs in the future. It is in a sense a specification for RFCs.
November 1982
Status: UNKNOWN
Autor: J. Postel
RFC0826 Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware
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.
November 1982
Status: STANDARD
Autor: D. Plummer
RFC0827 Exterior Gateway Protocol (EGP)
This RFC is proposed to establish a standard for Gateway to Gateway procedures that allow the Gateways to be mutually suspicious. This document is a DRAFT for that standard. Your comments are strongly encouraged.
October 1982
Status: UNKNOWN
Autor: E.C. Rosen
RFC0828 Data communications: IFIP's international "network" of experts
This RFC is distributed to inform the ARPA Internet community of the activities of the IFIP technical committee on Data Communications, and to encourage participation in those activities.
August 1982
Status: UNKNOWN
Autor: K. Owen
RFC0829 Packet satellite technology reference sources
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.
November 1982
Status: UNKNOWN
Autor: V.G. Cerf
RFC0830 Distributed system for Internet name service
This RFC proposes a distributed name service for DARPA Internet. Its purpose is to focus discussion on the subject. It is hoped that a general consensus will emerge leading eventually to the adoption of standards.
October 1982
Status: UNKNOWN
Autor: Z. Su
RFC0831 Backup access to the European side of SATNET
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.
December 1982
Status: UNKNOWN
Autor: R.T. Braden
RFC0832 Who talks TCP?
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 7-Dec-82.
December 1982
Status: UNKNOWN
Autor: D. Smallberg
RFC0833 Who talks TCP?
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 14-Dec-82.
December 1982
Status: UNKNOWN
Autor: D. Smallberg
RFC0834 Who talks TCP?
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 22-Dec-82.
December 1982
Status: UNKNOWN
Autor: D. Smallberg
RFC0835 Who talks TCP?
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 28-Dec-82 through 5-Jan-83.
December 1982
Status: UNKNOWN
Autor: D. Smallberg
RFC0836 Who talks TCP?
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 20-Dec-82. The tests were run on 4-Jan-83 through 5-Jan-83.
January 1983
Status: UNKNOWN
Autor: D. Smallberg
RFC0837 Who talks TCP?
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 11-Jan-83.
January 1983
Status: UNKNOWN
Autor: D. Smallberg
RFC0838 Who talks TCP?
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 18-Jan-83.
January 1983
Status: UNKNOWN
Autor: D. Smallberg
RFC0839 Who talks TCP?
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 25-Jan-83.
January 1983
Status: UNKNOWN
Autor: D. Smallberg
RFC0840 Official protocols
This RFC has been revised, see RFC 880.
April 1983
Status: HISTORIC
Autor: J. Postel
RFC0841 Specification for message format for Computer Based Message Systems
This RFC is FIPS 98. The purpose of distributing this document as an RFC is to make it easily accessible to the ARPA research community. This RFC does not specify a standard for the ARPA Internet. Obsoletes RFC 806.
January 1983
Status: UNKNOWN
Autor: National Bureau of Standards
RFC0842 Who talks TCP? - survey of 1 February 83
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 28-Jan-83. The tests were run on 1-Feb-83 and on 2-Feb-83 ISI-VAXA.ARPA.
February 1983
Status: UNKNOWN
Autor: D. Smallberg
RFC0843 Who talks TCP? - survey of 8 February 83
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 3-Feb-83. The tests were run on 8-Feb-83 and on 9-Feb-83 from ISI-VAXA.ARPA.
February 1983
Status: UNKNOWN
Autor: D. Smallberg
RFC0844 Who talks ICMP, too? - Survey of 18 February 1983
This survey determines how many hosts are able to respond to TELENET connections from a user at a class C site. This requires, in addition to IP and TCP, participation in gateway routing via ICMP and handling of Class C addresses. The list of hosts was taken from RFC 843, extracting only those hosts which are listed there as accepting TELNET connection. The tests were run on 18-Feb-83.
February 1983
Status: UNKNOWN
Autor: R. Clements
RFC0845 Who talks TCP? - survey of 15 February 1983
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 3-Feb-83. The tests were run on 15-Feb-83 from ISI-VAXA.ARPA.
February 1983
Status: UNKNOWN
Autor: D. Smallberg
RFC0846 Who talks TCP? - survey of 22 February 1983
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 18-Feb-83. The tests were run on 22-Feb-83 from ISI-VAXA.ARPA.
February 1983
Status: UNKNOWN
Autor: D. Smallberg
RFC0847 Summary of Smallberg surveys
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).
February 1983
Status: UNKNOWN
Autor: A. Westine, D. Smallberg, J. Postel
RFC0848 Who provides the "little" TCP services?
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.
March 1983
Status: UNKNOWN
Autor: D. Smallberg
RFC0849 Suggestions for improved host table distribution
This RFC actually is a request for comments. The issue dealt with is that of a naming registry update procedure, both as exists currently and what could exist in the future. None of the proposed solutions are intended as standards at this time; rather it is hoped that a general consensus will emerge as the appropriate solution, leaving eventually to the adoption of standards.
May 1983
Status: UNKNOWN
Autor: M.R. Crispin
RFC0850 Standard for interchange of USENET messages
This memo is distributed as an RFC only to make this information easily accessible to researchers in the ARPA community. It does not specify an Internet standard. This RFC defines the standard format for interchange of Network News articles among USENET sites. It describes the format for articles themselves, and gives partial standards for transmission of news. The news transmission is not entirely standardized in order to give a good deal of flexibility to the individual hosts to choose transmission hardware and software, whether to batch news and so on.
June 1983
Status: UNKNOWN
Autor: M.R. Horton
RFC0851 ARPANET 1822L Host Access Protocol
This RFC specifies the ARPANET 1822L Host Access Protocol, which is a successor to the existing 1822 Host Access Protocol. 1822L allows ARPANET hosts to use logical names as well as 1822's physical port locations to address each other. This RFC is also being presented as a solicitation of comments on 1822L, especially from host network software implementers and maintainers. Obsoletes RFC 802.
April 1983
Status: UNKNOWN
Autor: A.G. Malis
RFC0852 ARPANET short blocking feature
This RFC specifies the ARPANET Short Blocking Feature, which will allow ARPANET hosts to optionally shorten the IMP's host blocking timer. This Feature is a replacement of the ARPANET non-blocking host interface, which was never implemented, and will be available to hosts using either the 1822 or 1822L Host Access Protocol. This RFC is also being presented as a solicitation of comments on the Short Blocking Feature, especially from host network software implementers and maintainers.
April 1983
Status: UNKNOWN
Autor: A.G. Malis
RFC0854 Telnet Protocol Specification
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.
May 1983
Status: STANDARD
Autor: J. Postel, J.K. Reynolds
RFC0855 Telnet Option Specifications
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.
May 1983
Status: STANDARD
Autor: J. Postel, J.K. Reynolds
RFC0856 Telnet Binary Transmission
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.
May 1983
Status: STANDARD
Autor: J. Postel, J. Reynolds
RFC0857 Telnet Echo Option
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.
May 1983
Status: STANDARD
Autor: J. Postel, J. Reynolds
RFC0858 Telnet Suppress Go Ahead Option
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.
May 1983
Status: STANDARD
Autor: J. Postel, J. Reynolds
RFC0859 Telnet Status Option
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).
May 1983
Status: STANDARD
Autor: J. Postel, J. Reynolds
RFC0860 Telnet Timing Mark Option
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.
May 1983
Status: STANDARD
Autor: J. Postel, J. Reynolds
RFC0861 Telnet Extended Options: List Option
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.
May 1983
Status: STANDARD
Autor: J. Postel, J. Reynolds
RFC0862 Echo Protocol
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.
May 1983
Status: STANDARD
Autor: J. Postel
RFC0863 Discard Protocol
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.
May 1983
Status: STANDARD
Autor: J. Postel
RFC0864 Character Generator Protocol
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.
May 1983
Status: STANDARD
Autor: J. Postel
RFC0865 Quote of the Day Protocol
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.
May 1983
Status: STANDARD
Autor: J. Postel
RFC0866 Active users
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.
May 1983
Status: STANDARD
Autor: J. Postel
RFC0867 Daytime Protocol
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.
May 1983
Status: STANDARD
Autor: J. Postel
RFC0868 Time Protocol
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.
May 1983
Status: STANDARD
Autor: J. Postel, K. Harrenstien
RFC0869 Host Monitoring Protocol
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.
December 1983
Status: HISTORIC
Autor: R. Hinden
RFC0870 Assigned numbers
This RFC documents the list of numbers assigned for networks, protocols, etc. Obsoletes RFCs 820, 790, 776, 770, 762, 758, 755, 750, 739, 604.
October 1983
Status: HISTORIC
Autor: J.K. Reynolds, J. Postel
RFC0871 Perspective on the ARPANET reference model
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.
September 1982
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0872 TCP-on-a-LAN
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.
September 1982
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0873 Illusion of vendor support
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.
September 1982
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0874 Critique of X.25
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.
September 1982
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0875 Gateways, architectures, and heffalumps
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.
September 1982
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0876 Survey of SMTP implementations
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.
September 1983
Status: UNKNOWN
Autor: D. Smallberg
RFC0877 Standard for the transmission of IP datagrams over public data networks
This RFC specifies a standard adopted by CSNET, the VAN gateway, and other organizations for the transmission of IP datagrams over the X.25-based public data networks.
September 1983
Status: UNKNOWN
Autor: J.T. Korb
RFC0878 ARPANET 1822L Host Access Protocol
This RFC specifies the ARPANET 1822L Host Access Protocol, which is a successor to the existing 1822 Host Access Protocol. The 1822L procedure allows ARPANET hosts to use logical identifiers as well as 1822 physical interface identifiers to address each other.
December 1983
Status: UNKNOWN
Autor: A.G. Malis
RFC0879 TCP maximum segment size and related topics
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".
November 1983
Status: UNKNOWN
Autor: J. Postel
RFC0880 Official protocols
This RFC identifies the documents specifying the official protocols used in the ARPA Internet. Annotations identify any revisions or changes planned. Obsoletes RFC 840.
October 1983
Status: HISTORIC
Autor: J.K. Reynolds, J. Postel
RFC0881 Domain names plan and schedule
This RFC outlines a plan and schedule for the implementation of domain style names throughout the DDN/ARPA Internet community. The introduction of domain style names will impact all hosts on the DDN/ARPA Internet.
November 1983
Status: UNKNOWN
Autor: J. Postel
RFC0882 Domain names: Concepts and facilities
This RFC introduces domain style names, their use for ARPA Internet mail and host address support, and the protocol and servers used to implement domain name facilities.
November 1983
Status: UNKNOWN
Autor: P.V. Mockapetris
RFC0883 Domain names: Implementation specification
This RFC discusses the implementation of domain name servers and resolvers, specifies the format of transactions, and discusses the use of domain names in the context of existing mail systems and other network software.
November 1983
Status: UNKNOWN
Autor: P.V. Mockapetris
RFC0884 Telnet terminal type option
This RFC specifies a standard for the ARPA Internet community. It specifies a method for exchanging terminal type information in the Telnet protocol.
December 1983
Status: UNKNOWN
Autor: M. Solomon, E. Wimmers
RFC0885 Telnet end of record option
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.
December 1983
Status: PROPOSED STANDARD
Autor: J. Postel
RFC0886 Proposed standard for message header munging
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.
December 1983
Status: UNKNOWN
Autor: M.T. Rose
RFC0887 Resource Location Protocol
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.
December 1983
Status: EXPERIMENTAL
Autor: M. Accetta
RFC0888 "STUB" Exterior Gateway Protocol
This RFC describes the Exterior Gateway Protocol used to connect Stub Gateways to an Autonomous System of core Gateways. This document specifies the working protocol, and defines an ARPA official protocol. All implementers of Gateways should carefully review this document.
January 1984
Status: UNKNOWN
Autor: L. Seamonson, E.C. Rosen
RFC0889 Internet Delay Experiments
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.
December 1983
Status: UNKNOWN
Autor: D.L. Mills
RFC0890 Exterior Gateway Protocol implementation schedule
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.
February 1984
Status: UNKNOWN
Autor: J. Postel
RFC0891 DCN Local-Network Protocols
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.
December 1983
Status: STANDARD
Autor: D.L. Mills
RFC0892 ISO Transport Protocol specification
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.
December 1983
Status: UNKNOWN
Autor: International Organization for Standardization
RFC0893 Trailer encapsulations
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.
April 1984
Status: UNKNOWN
Autor: S. Leffler, M.J. Karels
RFC0894 A Standard for the Transmission of IP Datagrams over Ethernet Networks
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.
April 1984
Status: STANDARD
Autor: C. Hornig
RFC0895 Standard for the transmission of IP datagrams over experimental Ethernet networks
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.
April 1984
Status: STANDARD
Autor: J. Postel
RFC0896 Congestion Control in IP/TCP Internetworks
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.
January 1984
Status: UNKNOWN
Autor: J. Nagle
RFC0897 Domain name system implementation schedule
This memo is a policy statement on the implementation of the Domain Style Naming System in the Internet. This memo is a partial update of RFC 881. The intent of this memo is to detail the schedule for the implementation for the Domain Style Naming System. The names of hosts will be changed to domain style names. Hosts will begin to use domain style names on 14-Mar-84, and the use of old style names will be completely phased out before 2-May-84. This applies to both the ARPA research hosts and the DDN operational hosts. This is an official policy statement of the ICCB and the DARPA.
February 1984
Status: UNKNOWN
Autor: J. Postel
RFC0898 Gateway special interest group meeting notes
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.
April 1984
Status: UNKNOWN
Autor: R.M. Hinden, J. Postel, M. Muuss, J.K. Reynolds
RFC0899 Request For Comments summary notes: 800-899
May 1984
Status: INFORMATIONAL
Autor: J. Postel, A. Westine
RFC0900 Assigned Numbers
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.
June 1984
Status: HISTORIC
Autor: J.K. Reynolds, J. Postel
RFC0901 Official ARPA-Internet protocols
This RFC identifies the documents specifying the official protocols used in the ARPA-Internet. Annotations identify any revisions or changes planned. This memo is an official status report on the protocols used in the DARPA research community. See RFC-991.
June 1984
Status: UNKNOWN
Autor: J.K. Reynolds, J. Postel
RFC0902 ARPA Internet Protocol policy
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.
July 1984
Status: UNKNOWN
Autor: J.K. Reynolds, J. Postel
RFC0903 A Reverse Address Resolution Protocol
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.
June 1984
Status: STANDARD
Autor: R. Finlayson, T. Mann, J.C. Mogul, M. Theimer
RFC0904 Exterior Gateway Protocol formal specification
RFC-904 is the specification of the Exterior Gateway Protocol (EGP). This memo updates portions of RFC-888 and RFC-827. This RFC specifies an official protocol of the DARPA community for use between gateways of different autonomous systems in the ARPA-Internet.
April 1984
Status: HISTORIC
Autor: D.L. Mills
RFC0905 ISO Transport Protocol specification ISO DP 8073
This is the current specification of the ISO Transport Protocol. This document is the text of ISO/TC97/SC16/N1576 as corrected by ISO/TC97/SC16/N1695. This is the specification currently being voted on in ISO as a Draft International Standard (DIS). This document is distributed as an RFC for your information only, it does not specify a standard for the ARPA-Internet or DARPA research community. Our thanks to Alex McKenzie of BBN for making this online version available. Please note the size of this document, the file contains 258,729 characters.
April 1984
Status: UNKNOWN
Autor: ISO
RFC0906 Bootstrap loading using TFTP
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.
June 1984
Status: UNKNOWN
Autor: R. Finlayson
RFC0907 Host Access Protocol specification
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.
July 1984
Status: STANDARD
Autor: Bolt Beranek and Newman Laboratories
RFC0908 Reliable Data Protocol
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.
July 1984
Status: EXPERIMENTAL
Autor: D. Velten, R.M. Hinden, J. Sax
RFC0909 Loader Debugger Protocol
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.
July 1984
Status: EXPERIMENTAL
Autor: C. Welles, W. Milliken
RFC0910 Multimedia mail meeting notes
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.
August 1984
Status: UNKNOWN
Autor: H.C. Forsdick
RFC0911 EGP Gateway under Berkeley UNIX 4.2
This memo describes an implementation of the Exterior Gateway Protocol (EGP) (in that sense it is a status report). The memo also discusses some possible extentions and some design issues (in that sense it is an invitation for further discussion).
August 1984
Status: UNKNOWN
Autor: P. Kirton
RFC0912 Authentication service
This memo describes a proposed authentication protocol for verifying the identity of a user of a TCP connection. Given a TCP port number pair, it returns a character string which identifies the owner of that connection on the server's system. Suggested uses include automatic identification and verification of a user during an FTP session, additional verification of a TAC dial up user, and access verification for a generalized network file server.
September 1984
Status: UNKNOWN
Autor: M. St. Johns
RFC0913 Simple File Transfer Protocol
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.
September 1984
Status: HISTORIC
Autor: M. Lottor
RFC0914 Thinwire protocol for connecting personal computers to the Internet
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.
September 1984
Status: HISTORIC
Autor: D.J. Farber, G. Delp, T.M. Conte
RFC0915 Network mail path service
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.
December 1984
Status: UNKNOWN
Autor: M.A. Elvy, R. Nedved
RFC0916 Reliable Asynchronous Transfer Protocol (RATP)
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.
October 1984
Status: HISTORIC
Autor: G.G. Finn
RFC0917 Internet subnets
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.
October 1984
Status: UNKNOWN
Autor: J.C. Mogul
RFC0918 Post Office Protocol
This RFC suggests a simple method for workstations to dynamically access mail from a mailbox server. The intent of the Post Office Protocol (POP) is to allow a user's workstation to access mail from a mailbox server. It is expected that mail will be posted from the workstation to the mailbox server via the Simple Mail Transfer Protocol (SMTP). This RFC specifies a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvement. The status of this protocol is experimental, and this protocol is dependent upon TCP.
October 1984
Status: UNKNOWN
Autor: J.K. Reynolds
RFC0919 Broadcasting Internet Datagrams
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.
October 1984
Status: STANDARD
Autor: J.C. Mogul
RFC0920 Domain requirements
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.
October 1984
Status: UNKNOWN
Autor: J. Postel, J.K. Reynolds
RFC0921 Domain name system implementation schedule - revised
This memo is a policy statement on the implementation of the Domain Style Naming System in the Internet. This memo is an update of RFC-881, and RFC-897. This is an official policy statement of the IAB and the DARPA. The intent of this memo is to detail the schedule for the implementation for the Domain Style Naming System. The explanation of how this system works is to be found in the references.
October 1984
Status: UNKNOWN
Autor: J. Postel
RFC0922 Broadcasting Internet datagrams in the presence of subnets
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.
October 1984
Status: STANDARD
Autor: J.C. Mogul
RFC0923 Assigned numbers
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.
October 1984
Status: HISTORIC
Autor: J.K. Reynolds, J. Postel
RFC0924 Official ARPA-Internet protocols for connecting personal computers to the Internet
This RFC identifies the documents specifying the official protocols used in the Internet. This edition of Official ARPA-Internet Protocols obsoletes RFC-900 and earlier editions. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991.
October 1984
Status: UNKNOWN
Autor: J.K. Reynolds, J. Postel
RFC0925 Multi-LAN address resolution
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.
October 1984
Status: UNKNOWN
Autor: J. Postel
RFC0926 Protocol for providing the connectionless mode network services
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.
December 1984
Status: UNKNOWN
Autor: International Organization for Standardization
RFC0927 TACACS user identification Telnet option
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.
December 1984
Status: PROPOSED STANDARD
Autor: B.A. Anderson
RFC0928 Introduction to proposed DoD standard H-FP
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.
December 1984
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0929 Proposed Host-Front End Protocol
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.
December 1984
Status: HISTORIC
Autor: J. Lilienkamp, R. Mandell, M.A. Padlipsky
RFC0930 Telnet terminal type option
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that exchange terminal type information within the Telnet protocol are expected to adopt and implement this standard. This standard supersedes RFC-884. The only change is to specify that the TERMINAL-TYPE IS sub-negotiation should be sent only in response to the TERMINAL-TYPE SEND sub-negotiation.
January 1985
Status: UNKNOWN
Autor: M. Solomon, E. Wimmers
RFC0931 Authentication server
This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. This is the second draft of this proposal (superseding RFC-912) and incorporates a more formal description of the syntax for the request and response dialog, as well as a change to specify the type of user identification returned.
January 1985
Status: UNKNOWN
Autor: M. St. Johns
RFC0932 Subnetwork addressing scheme
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.
January 1985
Status: UNKNOWN
Autor: D.D. Clark
RFC0933 Output marking Telnet option
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.
January 1985
Status: PROPOSED STANDARD
Autor: S. Silverman
RFC0934 Proposed standard for message encapsulation
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.
January 1985
Status: UNKNOWN
Autor: M.T. Rose, E.A. Stefferud
RFC0935 Reliable link layer protocols
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.
January 1985
Status: UNKNOWN
Autor: J.G. Robinson
RFC0936 Another Internet subnet addressing scheme
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.
February 1985
Status: UNKNOWN
Autor: M.J. Karels
RFC0937 Post Office Protocol: Version 2
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.
February 1985
Status: HISTORIC
Autor: M. Butler, J. Postel, D. Chase, J. Goldberger, J.K. Reynolds
RFC0938 Internet Reliable Transaction Protocol functional and interface specification
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.
February 1985
Status: EXPERIMENTAL
Autor: T. Miller
RFC0939 Executive summary of the NRC report on transport protocols for Department of Defense data networks
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.
February 1985
Status: UNKNOWN
Autor: National Research Council
RFC0940 Toward an Internet standard scheme for subnetting
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.
April 1985
Status: UNKNOWN
Autor: Gateway Algorithms and Data Structures Task Force
RFC0941 Addendum to the network service definition covering network layer addressing
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.
April 1985
Status: UNKNOWN
Autor: International Organization for Standardization
RFC0942 Transport protocols for Department of Defense data networks
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).
February 1985
Status: UNKNOWN
Autor: National Research Council
RFC0943 Assigned numbers
This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This 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.
April 1985
Status: HISTORIC
Autor: J.K. Reynolds, J. Postel
RFC0944 Official ARPA-Internet protocols
This RFC identifies the documents specifying the official protocols used in the Internet. This edition of Official ARPA-Internet Protocols obsoletes RFC-924 and earlier editions. This RFC will be updated periodically, and current information can be obtained from Joyce Reynolds. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991.
April 1985
Status: UNKNOWN
Autor: J.K. Reynolds, J. Postel
RFC0945 DoD statement on the NRC report
In May 1983 the National Research Council (NRC) was asked jointly by DoD and NBS to study the issues and recommend a course of action. The final report of the NRC committee was published in February 1985 (see RFC-942). The enclosed letter is from Donald C. Latham (ASDC3I) to DCA transmitting the NRC report and requesting specific actions relative to the recommendations of the report. This RFC reproduces a letter from the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASDC3I) to the Director of the Defense Communications Agency (DCA). This letter is distributed for information only.
May 1985
Status: UNKNOWN
Autor: J. Postel
RFC0946 Telnet terminal location number option
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.
May 1985
Status: PROPOSED STANDARD
Autor: R. Nedved
RFC0947 Multi-network broadcasting within the Internet
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.
June 1985
Status: UNKNOWN
Autor: K. Lebowitz, D. Mankins
RFC0948 Two methods for the transmission of IP datagrams over IEEE 802.3 networks
This RFC describes two methods of encapsulating Internet Protocol (IP) datagrams on an IEEE 802.3 network. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
June 1985
Status: UNKNOWN
Autor: I. Winston
RFC0949 FTP unique-named store command
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.
July 1985
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0950 Internet Standard Subnetting Procedure
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.
August 1985
Status: STANDARD
Autor: J.C. Mogul, J. Postel
RFC0951 Bootstrap Protocol
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.
September 1985
Status: DRAFT STANDARD
Autor: W.J. Croft, J. Gilmore
RFC0952 DoD Internet host table specification
This RFC is the official specification of the format of the Internet Host Table. This edition of the specification includes minor revisions to RFC-810 which brings it up to date.
October 1985
Status: UNKNOWN
Autor: K. Harrenstien, M.K. Stahl, E.J. Feinler
RFC0953 Hostname Server
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.
October 1985
Status: HISTORIC
Autor: K. Harrenstien, M.K. Stahl, E.J. Feinler
RFC0954 NICNAME/WHOIS
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.
October 1985
Status: DRAFT STANDARD
Autor: K. Harrenstien, M.K. Stahl, E.J. Feinler
RFC0955 Towards a transport service for transaction processing applications
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.
September 1985
Status: UNKNOWN
Autor: R.T. Braden
RFC0956 Algorithms for synchronizing network clocks
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.
September 1985
Status: UNKNOWN
Autor: D.L. Mills
RFC0957 Experiments in network clock synchronization
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.
September 1985
Status: UNKNOWN
Autor: D.L. Mills
RFC0958 Network Time Protocol (NTP)
This document describes the Network Time Protocol (NTP), a protocol for synchronizing a set of network clocks using a set of distributed clients and servers. NTP is built on the User Datagram Protocol (UDP), which provides a connectionless transport mechanism. It is evolved from the Time Protocol and the ICMP Timestamp message and is a suitable replacement for both. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
September 1985
Status: UNKNOWN
Autor: D.L. Mills
RFC0959 File Transfer Protocol
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.
October 1985
Status: STANDARD
Autor: J. Postel, J. Reynolds
RFC0960 Assigned numbers
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.
December 1985
Status: HISTORIC
Autor: J.K. Reynolds, J. Postel
RFC0961 Official ARPA-Internet protocols
This memo identifies the documents specifying the official protocols used in the Internet, and comments on any revisions or changes planned. This edition of the Official Protocols updates and obsoletes RFC-944. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991.
December 1985
Status: UNKNOWN
Autor: J.K. Reynolds, J. Postel
RFC0962 TCP-4 prime
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.
November 1985
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0963 Some problems with the specification of the Military Standard Internet Protocol
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.
November 1985
Status: UNKNOWN
Autor: D.P. Sidhu
RFC0964 Some problems with the specification of the Military Standard Transmission Control Protocol
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.
November 1985
Status: UNKNOWN
Autor: D.P. Sidhu, T. Blumer
RFC0965 Format for a graphical communication protocol
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.
December 1985
Status: UNKNOWN
Autor: L. Aguilar
RFC0966 Host groups: A multicast extension to the Internet Protocol
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.
December 1985
Status: UNKNOWN
Autor: S.E. Deering, D.R. Cheriton
RFC0967 All victims together
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.
December 1985
Status: UNKNOWN
Autor: M.A. Padlipsky
RFC0968 Twas the night before start-up
This memo discusses problems that arise and debugging techniques used in bringing a new network into operation.
December 1985
Status: UNKNOWN
Autor: V.G. Cerf
RFC0969 NETBLT: A bulk data transfer protocol
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.
December 1985
Status: UNKNOWN
Autor: D.D. Clark, M.L. Lambert, L. Zhang
RFC0970 On Packet Switches With Infinite Storage
The purpose of this RFC is to focus discussion on a particular problem in the ARPA-Internet and possible methods of solution. Most prior work on congestion in datagram systems focuses on buffer management. In this memo the case of a packet switch with infinite storage is considered. 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. An unexpected result is found that shows 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, new solutions applicable to switches with finite storage may be found. No proposed solutions this document are intended as standards for the ARPA-Internet at this time.
December 1985
Status: UNKNOWN
Autor: J. Nagle
RFC0971 Survey of data representation standards
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.
January 1986
Status: UNKNOWN
Autor: A.L. DeSchon
RFC0972 Password Generator Protocol
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.
January 1986
Status: UNKNOWN
Autor: F.J. Wancho
RFC0973 Domain system changes and observations
This RFC documents updates to Domain Name System specifications RFC-882 and RFC-883, suggests some operational guidelines, and discusses some experiences and problem areas in the present system.
January 1986
Status: UNKNOWN
Autor: P.V. Mockapetris
RFC0974 Mail routing and the domain system
This RFC presents a description of how mail systems on the Internet are expected to route messages based on information from the domain system. This involves a discussion of how mailers interpret MX RRs, which are used for message routing.
January 1986
Status: HISTORIC
Autor: C. Partridge
RFC0975 Autonomous confederations
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.
February 1986
Status: UNKNOWN
Autor: D.L. Mills
RFC0976 UUCP mail interchange format standard
This document defines the standard format for the transmission of mail messages between computers in the UUCP Project. It does not however, address the format for storage of messages on one machine, nor the lower level transport mechanisms used to get the date from one machine to the next. It represents a standard for conformance by hosts in the UUCP zone.
February 1986
Status: UNKNOWN
Autor: M.R. Horton
RFC0977 Network News Transfer Protocol
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.
February 1986
Status: PROPOSED STANDARD
Autor: B. Kantor, P. Lapsley
RFC0978 Voice File Interchange Protocol (VFIP)
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.
February 1986
Status: UNKNOWN
Autor: J.K. Reynolds, R. Gillman, W.A. Brackenridge, A. Witkowski, J. Postel
RFC0979 PSN End-to-End functional specification
This memo is an updated version of BBN Report 5775, "End-to-End Functional Specification and describes important changes to the functionality of the interface between a Host and the PSN, and should be carefully reviewed by anyone involved in supporting a host on either the ARPANET or MILNET". The new End-to-End protocol (EE) is being developed in order to correct a number of deficiencies in the old EE, to improve its performance and overall throughput, and to better equip the Packet Switch Node (PSN, also known as the IMP) to support its current and anticipated host population.
March 1986
Status: UNKNOWN
Autor: A.G. Malis
RFC0980 Protocol document order information
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).
March 1986
Status: UNKNOWN
Autor: O.J. Jacobsen, J. Postel
RFC0981 Experimental multiple-path routing algorithm
This document introduces wiretap algorithms, a class of experimental, multiple routing algorithms that compute quasi-optimum routes for stations sharing a packet-radio broadcast channel. The primary route (a minimum-distance path), and additional paths ordered by distance, which serve as alternate routes should the primary route fail, are computed. This prototype is presented as an example of a class of routing algorithms and data-base management techniques that may find wider application in the Internet community. Discussions and suggestions for improvements are welcomed.
March 1986
Status: UNKNOWN
Autor: D.L. Mills
RFC0982 Guidelines for the specification of the structure of the Domain Specific Part (DSP) of the ISO standard NSAP address
This RFC is a draft working document of the ANSI "Guidelines for the Specification of the Structure of the Domain Specific Part (DSP) of the ISO Standard NSAP Address". It provides guidance to private address administration authorities on preferred formats and semantics for the Domain Specific Part (DSP) of an NSAP address. This RFC specifies the way in which the DSP may be constructed so as to facilitate efficient address assignment. This RFC is for informational purposes only and its distribution is unlimited and does not specify a standard of the ARPA-Internet.
April 1986
Status: UNKNOWN
Autor: H.W. Braun
RFC0983 ISO transport arrives on top of the TCP
This memo describes a proposed protocol standard for the ARPA Internet community. The CCITT and the ISO have defined various session, presentation, and application recommendations which have been adopted by the international community and numerous vendors. To the largest extent possible, it is desirable to offer these higher level services directly in the ARPA Internet, without disrupting existing facilities. This permits users to develop expertise with ISO and CCITT applications which previously were not available in the ARPA Internet. The intention is that hosts in the ARPA-Internet that choose to implement ISO TSAP services on top of the TCP be expected to adopt and implement this standard. Suggestions for improvement are encouraged.
April 1986
Status: UNKNOWN
Autor: D.E. Cass, M.T. Rose
RFC0984 PCMAIL: A distributed mail system for personal computers
This document is a preliminary discussion of the design of a personal-computer-based distributed mail system. Pcmail is a distributed mail system that provides mail service to an arbitrary number of users, each of which owns one or more personal computers (PCs). The system is divided into two halves. The first consists of a single entity called the "repository". The repository is a storage center for incoming mail. Mail for a Pcmail user can arrive externally from the Internet or internally from other repository users. The repository also maintains a stable copy of each user's mail state. The repository is therefore typically a computer with a large amount of disk storage. It is published for discussion and comment, and does not constitute a standard. As the proposal may change, implementation of this document is not advised. See RFC-993.
May 1986
Status: UNKNOWN
Autor: D.D. Clark, M.L. Lambert
RFC0985 Requirements for Internet gateways - draft
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.
May 1986
Status: UNKNOWN
Autor: National Science Foundation, Network Technical Advisory Group
RFC0986 Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol
This RFC suggests a method to allow the existing IP addressing, including the IP protocol field, to be used for the ISO Connectionless Network Protocol (CLNP). This is a draft solution to one of the problems inherent in the use of "ISO-grams" in the DOD Internet. Related issues will be discussed in subsequent RFCs. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
June 1986
Status: UNKNOWN
Autor: R.W. Callon, H.W. Braun
RFC0987 Mapping between X.400 and RFC 822
The X.400 series protocols have been defined by CCITT to provide an Interpersonal Messaging Service (IPMS), making use of a store and forward Message Transfer Service. It is expected that this standard will be implemented very widely. This document describes a set of mappings which will enable interworking between systems operating the X.400 protocols and systems using RFC-822 mail protocol or protocols derived from RFC-822. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
June 1986
Status: UNKNOWN
Autor: S.E. Kille
RFC0988 Host extensions for IP multicasting
This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support internetwork multicasting. This specification supersedes that given in RFC-966, and constitutes a proposed protocol standard for IP multicasting in the ARPA-Internet. The reader is directed to RFC-966 for a discussion of the motivation and rationale behind the multicasting extension specified here.
July 1986
Status: UNKNOWN
Autor: S.E. Deering
RFC0989 Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures
This RFC suggests a proposed protocol for the Internet community and requests discussion and suggestions for improvements. This RFC is the outgrowth of a series of IAB Privacy Task Force meetings and of internal working papers distributed for those meetings. This RFC defines message encipherment and authentication procedures, as the initial phase of an effort to provide privacy enhancement services for electronic mail transfer in the Internet. It is intended that the procedures defined here be compatible with a wide range of key management approaches, including both conventional (symmetric) and public-key (asymmetric) approaches for encryption of data encrypting keys. Use of conventional cryptography for message text encryption and/or authentication is anticipated.
February 1987
Status: UNKNOWN
Autor: J. Linn
RFC0990 Assigned numbers
This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-997. Obsoletes RFC-960, 943, 923 and 900.
November 1986
Status: HISTORIC
Autor: J.K. Reynolds, J. Postel
RFC0991 Official ARPA-Internet protocols
This RFC identifies the documents specifying the official protocols used in the Internet. Comments indicate any revisions or changes planned. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. Obsoletes RFC-961, 944 and 924.
November 1986
Status: UNKNOWN
Autor: J.K. Reynolds, J. Postel
RFC0992 On communication support for fault tolerant process groups
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.
November 1986
Status: UNKNOWN
Autor: K.P. Birman, T.A. Joseph
RFC0993 PCMAIL: A distributed mail system for personal computers
This document is a discussion of the Pcmail workstation-based distributed mail system. It is a revision of the design published in NIC RFC-984. The revision is based on discussion and comment fromm a variety of sources, as well as further research into the design of interactive Pcmail clients and the use of client code on machines other than IBM PCs. As this design may change, implementation of this document is not advised. Obsoletes RFC-984.
December 1986
Status: UNKNOWN
Autor: D.D. Clark, M.L. Lambert
RFC0994 Final text of DIS 8473, Protocol for Providing the Connectionless-mode Network Service
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).
March 1986
Status: UNKNOWN
Autor: International Organization for Standardization
RFC0995 End System to Intermediate System Routing Exchange Protocol for use in conjunction with ISO 8473
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.
April 1986
Status: UNKNOWN
Autor: International Organization for Standardization
RFC0996 Statistics server
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.
February 1987
Status: HISTORIC
Autor: D.L. Mills
RFC0997 Internet numbers
This memo is an official status report on the network numbers used in the Internet community. As of 1-Mar-87 the Network Information Center (NIC) at SRI International has assumed responsibility for assignment of Network Numbers and Autonomous System Numbers. This RFC documents the current assignments of these numbers at the time of this transfer of responsibility. Obsoletes RFC-990, 960, 943, 923 and 900.
March 1987
Status: UNKNOWN
Autor: J.K. Reynolds, J. Postel
RFC0998 NETBLT: A bulk data transfer protocol
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.
March 1987
Status: EXPERIMENTAL
Autor: D.D. Clark, M.L. Lambert, L. Zhang
RFC0999 Requests For Comments summary notes: 900-999
April 1987
Status: UNKNOWN
Autor: A. Westine, J. Postel
RFC1000 Request For Comments reference guide
This RFC Reference Guide is intended to provide a historical account by categorizing and summarizing of the Request for Comments numbers 1 through 999 issued between the years 1969-1987. These documents have been crossed referenced to indicate which RFCs are current, obsolete, or revised.
August 1987
Status: UNKNOWN
Autor: J.K. Reynolds, J. Postel
RFC1001 Protocol standard for a NetBIOS service on a TCP/UDP transport: Concepts and methods
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".
March 1987
Status: STANDARD
Autor: NetBIOS Working Group in the Defense Advanced Research Projects Agency, Internet Activities Board, End-to-End Services Task Force
RFC1002 Protocol standard for a NetBIOS service on a TCP/UDP transport: Detailed specifications
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".
March 1987
Status: STANDARD
Autor: NetBIOS Working Group in the Defense Advanced Research Projects Agency, Internet Activities Board, End-to-End Services Task Force
RFC1003 Issues in defining an equations representation standard
This memo is intended to identify and explore issues in defining a standard for the exchange of mathematical equations. No attempt is made at a complete definition and more questions are asked than are answered. Questions about the user interface are only addressed to the extent that they affect interchange issues.
March 1987
Status: UNKNOWN
Autor: A.R. Katz
RFC1004 Distributed-protocol authentication scheme
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.
April 1987
Status: EXPERIMENTAL
Autor: D.L. Mills
RFC1005 ARPANET AHIP-E Host Access Protocol (enhanced AHIP)
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.
May 1987
Status: UNKNOWN
Autor: A. Khanna, A.G. Malis
RFC1006 ISO Transport Service on top of the TCP Version: 3
This memo specifies a standard for the Internet community. Hosts on the Internet that choose to implement ISO transport services on top of the TCP are expected to adopt and implement this standard. TCP port 102 is reserved for hosts which implement this standard. This memo specifies version 3 of the protocol and supersedes RFC-983. Changes between the protocol is described in RFC-983 and this memo are minor, but unfortunately incompatible.
May 1987
Status: STANDARD
Autor: M.T. Rose, D.E. Cass
RFC1007 Military supplement to the ISO Transport Protocol
This document supplements the Transport Service and Protocol of the International Standards Organization (ISO), IS 8072 and IS 8073, respectively, and their formal descriptions by providing conventions, option selections and parameter values. This RFC is being distributed to members of the Internet community in order to solicit comments on the Draft Military Supplement. While this document may not be directly relevant to the research problems of the Internet, it may be of some interest to a number of researchers and implementors.
June 1987
Status: UNKNOWN
Autor: W. McCoy
RFC1008 Implementation guide for the ISO Transport Protocol
This RFC is being distributed to members of the Internet community in order to solicit comments on the Implementors Guide. While this document may not be directly relevant to the research problems of the Internet, it may be of some interest to a number of researchers and implementors.
June 1987
Status: UNKNOWN
Autor: W. McCoy
RFC1009 Requirements for Internet gateways
This RFC summarizes the requirements for gateways to be used between networks supporting the Internet protocols. This document is a formal statement of the requirements to be met by gateways used in the Internet system. As such, it is an official specification for the Internet community.
June 1987
Status: HISTORIC
Autor: R.T. Braden, J. Postel
RFC1010 Assigned numbers
This memo is an official status report on the numbers used in protocols in the Internet community. It documents the currently assigned values from several series of numbers including link, socket, port, and protocol, used in network protocol implementations.
May 1987
Status: HISTORIC
Autor: J.K. Reynolds, J. Postel
RFC1011 Official Internet protocols
This memo is an official status report on the protocols used in the Internet community. It identifies the documents specifying the official protocols used in the Internet. Comments indicate any revisions or changes planned.
May 1987
Status: UNKNOWN
Autor: J.K. Reynolds, J. Postel
RFC1012 Bibliography of Request For Comments 1 through 999
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.
June 1987
Status: INFORMATIONAL
Autor: J.K. Reynolds, J. Postel
RFC1013 X Window System Protocol, version 11: Alpha update April 1987
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.
June 1987
Status: UNKNOWN
Autor: R.W. Scheifler
RFC1014 XDR: External Data Representation standard
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.
June 1987
Status: UNKNOWN
Autor: Sun Microsystems
RFC1015 Implementation plan for interagency research Internet
This RFC proposes an Interagency Research Internet as the natural outgrowth of the current Internet. This is an "idea paper" and discussion is strongly encouraged.
July 1987
Status: UNKNOWN
Autor: B.M. Leiner
RFC1016 Something a Host Could Do with Source Quench: The Source Quench Introduced Delay (SQuID)
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.
July 1987
Status: UNKNOWN
Autor: W. Prue, J. Postel
RFC1017 Network requirements for scientific research: Internet task force on scientific computing
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.
August 1987
Status: UNKNOWN
Autor: B.M. Leiner
RFC1018 Some comments on SQuID
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.
August 1987
Status: UNKNOWN
Autor: A.M. McKenzie
RFC1019 Report of the Workshop on Environments for Computational Mathematics
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.
September 1987
Status: UNKNOWN
Autor: D. Arnon
RFC1020 Internet numbers
This RFC is a list of the Assigned IP Network Numbers and EGP Autonomous System Numbers. This RFC obsoletes RFC-997.
November 1987
Status: UNKNOWN
Autor: S. Romano, M.K. Stahl
RFC1021 High-level Entity Management System (HEMS)
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.
October 1987
Status: HISTORIC
Autor: C. Partridge, G. Trewitt
RFC1022 High-level Entity Management Protocol (HEMP)
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.
October 1987
Status: UNKNOWN
Autor: C. Partridge, G. Trewitt
RFC1023 HEMS monitoring and control language
This RFC specifies the High-Level Entity Management System (HEMS) Monitoring and Control Language. This language defines the requests and replies used in HEMS. This memo assumes knowledge of the HEMS system described in RFC-1021, and of the ISO data encoding standard, ASN.1.
October 1987
Status: UNKNOWN
Autor: G. Trewitt, C. Partridge
RFC1024 HEMS variable definitions
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.
October 1987
Status: UNKNOWN
Autor: C. Partridge, G. Trewitt
RFC1025 TCP and IP bake off
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.
September 1987
Status: UNKNOWN
Autor: J. Postel
RFC1026 Addendum to RFC 987: (Mapping between X.400 and RFC-822)
This memo suggest a proposed protocol for the Internet community, and request discussion and suggestions for improvements.
September 1987
Status: UNKNOWN
Autor: S.E. Kille
RFC1027 Using ARP to implement transparent subnet gateways
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".
October 1987
Status: UNKNOWN
Autor: S. Carl-Mitchell, J.S. Quarterman
RFC1028 Simple Gateway Monitoring Protocol
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.
November 1987
Status: HISTORIC
Autor: J. Davin, J.D. Case, M. Fedor, M.L. Schoffstall
RFC1029 More fault tolerant approach to address resolution for a Multi-LAN system of Ethernets
This memo discusses an extension to a Bridge Protocol to detect and disclose changes in heighbouring host address parameters in a Multi-Lan system of Ethernets. The problem is one which is appearing more and more regularly as the interconnected systems grow larger on Campuses and in Commercial Institutions. This RFC suggests a protocol enhancement for the Internet community, and requests discussion and suggestions for improvements.
May 1988
Status: UNKNOWN
Autor: G. Parr
RFC1030 On testing the NETBLT Protocol over divers networks
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.
November 1987
Status: UNKNOWN
Autor: M.L. Lambert
RFC1031 MILNET name domain transition
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.
November 1987
Status: UNKNOWN
Autor: W.D. Lazear
RFC1032 Domain administrators guide
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.
November 1987
Status: UNKNOWN
Autor: M.K. Stahl
RFC1033 Domain Administrators Operations Guide
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).
November 1987
Status: UNKNOWN
Autor: M. Lottor
RFC1034 Domain names - concepts and facilities
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.
November 1987
Status: STANDARD
Autor: P.V. Mockapetris
RFC1035 Domain names - implementation and specification
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.
November 1987
Status: STANDARD
Autor: P.V. Mockapetris
RFC1036 Standard for interchange of USENET messages
This RFC defines the standard format for the interchange of network News messages among USENET hosts. It updates and replaces RFC-850, reflecting version B2.11 of the News program. This memo is distributed as an RFC to make this information easily accessible to the Internet community. It does not specify an Internet standard.
December 1987
Status: UNKNOWN
Autor: M.R. Horton, R. Adams
RFC1037 NFILE - a file access protocol
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.
December 1987
Status: HISTORIC
Autor: B. Greenberg, S. Keene
RFC1038 Draft revised IP security option
This memo is a pre-publication draft of the revised Internet Protocol Security Option. This RFC reflects the version as approved by the Protocol Standards Steering group, and is provided for informational purposes only. The final version of this document will be available from Navy publications and should not differ from this document in any major fashion. This document will be published as a change to the MIL- STD 1777, "Internet Protocol".
January 1988
Status: UNKNOWN
Autor: M. St. Johns
RFC1039 DoD statement on Open Systems Interconnection protocols
This RFC reproduces a memorandum issued on 2-JUL-87 from the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASDC31) to the Director of the Defense Communications Agency (DCA). This memo is distributed for information only.
January 1988
Status: UNKNOWN
Autor: D. Latham
RFC1040 Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures
This RFC is the Outgrowth of a series of IAB Privacy Task Force meetings and of internal working papers distributed for those meetings. This memo defines message encipherment and authentication procedures, as the initial phase of an effort to provide privacy enhancement services for electronic mail transfer in the Internet. Detailed key management mechanisms to support these procedures will be defined in a subsequent RFC. As a goal of this initial phase, it is intended that the procedures defined here be compatible with a wide range of key management approaches, including both conventional (symmetric) and public-key (asymmetric) approaches for encryption of data encrypting keys. Use of conventional cryptography for message text encryption and/or integrity check computation is anticipated.
January 1988
Status: UNKNOWN
Autor: J. Linn
RFC1041 Telnet 3270 regime option
This RFC specifies a proposed standard for the Internet community. Hosts on the Internet that want to support 3270 data stream within the Telnet protocol, are expected to adopt and implement this standard.
January 1988
Status: PROPOSED STANDARD
Autor: Y. Rekhter
RFC1042 Standard for the transmission of IP datagrams over IEEE 802 networks
This RFC specifies a standard method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on IEEE 802 Networks to allow compatible and interoperable implementations. This RFC specifies a protocol standard for the Internet community.
February 1988
Status: STANDARD
Autor: J. Postel, J.K. Reynolds
RFC1043 Telnet Data Entry Terminal option: DODIIS implementation
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.
February 1988
Status: PROPOSED STANDARD
Autor: A. Yasuda, T. Thompson
RFC1044 Internet Protocol on Network System's HYPERchannel: Protocol Specification
This memo intends to provide a complete discussion of the protocols and techniques used to embed DoD standard Internet Protocol datagrams (and its associated higher level protocols) on Network Systems Corporation's HYPERchannel equipment. This document is directed toward network planners and implementors who are already familiar with the TCP/IP protocol suite and the techniques used to carry TCP/IP traffic on common networks such as the DDN or the Ethernet. No great familiarity with NSC products is assumed; an appendix is devoted to a review of NSC technologies and protocols.
February 1988
Status: STANDARD
Autor: K. Hardwick, J. Lekashman
RFC1045 VMTP: Versatile Message Transaction Protocol: Protocol specification
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.
February 1988
Status: EXPERIMENTAL
Autor: D.R. Cheriton
RFC1046 Queuing algorithm to provide type-of-service for IP links
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.
February 1988
Status: UNKNOWN
Autor: W. Prue, J. Postel
RFC1047 Duplicate messages and SMTP
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.
February 1988
Status: UNKNOWN
Autor: C. Partridge
RFC1048 BOOTP vendor information extensions
This memo proposes an addition to the Bootstrap Protocol (BOOTP). Comments and suggestions for improvements are sought.
February 1988
Status: UNKNOWN
Autor: P.A. Prindeville
RFC1049 Content-type header field for Internet messages
This memo suggests proposed additions to the Internet Mail Protocol, RFC-822, for the Internet community, and requests discussion and suggestions for improvements.
March 1988
Status: HISTORIC
Autor: M.A. Sirbu
RFC1050 RPC: Remote Procedure Call Protocol specification
This memo specifies a message protocol used in implementing Sun's Remote Procedure Call (RPC) package. This RFC describes a standard that Sun Microsystems and others are using and is one they wish to propose for the Internet's consideration. It is not an Internet standard at this time.
April 1988
Status: HISTORIC
Autor: Sun Microsystems
RFC1051 Standard for the transmission of IP datagrams and ARP packets over ARCNET networks
This memo specifies a standard method of encapsulating Internet Protocol (IP) and Address Resolution Protocol (ARP) datagrams on an ARCNET. This RFC is a standard protocol for the Internet community.
March 1988
Status: HISTORIC
Autor: P.A. Prindeville
RFC1052 IAB recommendations for the development of Internet network management standards
This RFC is intended to convey to the Internet community and other interested parties the recommendations of the Internet Activities Board (IAB) for the development of network management protocols for use in the TCP/IP environment. This memo does NOT, in and of itself, define or propose an Official Internet Protocol. It does reflect, however, the policy of the IAB with respect to further network management development in the short and long term.
April 1988
Status: UNKNOWN
Autor: V.G. Cerf
RFC1053 Telnet X.3 PAD option
This RFC proposes a new option to Telnet for the Internet community, and requests discussion and suggestions for improvements.
April 1988
Status: PROPOSED STANDARD
Autor: S. Levy, T. Jacobson
RFC1054 Host extensions for IP multicasting
This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. IP multicasting is the transmission of an IP datagram to a "host group", a set hosts identified by a single IP destination address. A multicast datagram is delivered to all members of its destination host group with the same "best-efforts" reliability as regular unicast IP datagrams. It is proposed as a standard for IP multicasting in the Internet. This specification is a major revision of RFC-988.
May 1988
Status: UNKNOWN
Autor: S.E. Deering
RFC1055 Nonstandard for transmission of IP datagrams over serial lines: SLIP
The TCP/IP protocol family runs over a variety of network media: IEEE 802.3 (ethernet) and 802.5 (token ring) LAN's, X.25 lines, satellite links, and serial lines. There are standard encapsulations for IP packets defined for many of these networks, but there is no standard for serial lines. SLIP, Serial Line IP, is a currently a de facto standard, commonly used for point-to-point serial connections running TCP/IP. It is not an Internet standard.
June 1988
Status: STANDARD
Autor: J.L. Romkey
RFC1056 PCMAIL: A distributed mail system for personal computers
This memo is a discussion of the Pcmail workstation based distributed mail system. It is identical to the discussion in RFC-993, save that a new, much simpler mail transport protocol is described. The new transport protocol is the result of continued research into ease of protocol implementation and use issues.
June 1988
Status: INFORMATIONAL
Autor: M.L. Lambert
RFC1057 RPC: Remote Procedure Call Protocol specification: Version 2
This RFC describes a standard that Sun Microsystems and others are using, and is one we wish to propose for the Internet's consideration. This memo is not an Internet standard at this time.
June 1988
Status: INFORMATIONAL
Autor: Sun Microsystems
RFC1058 Routing Information Protocol
This RFC describes an existing protocol for exchanging routing information among gateways and other hosts. It is intended to be used as a basis for developing gateway software for use in the Internet community.
June 1988
Status: HISTORIC
Autor: C.L. Hedrick
RFC1059 Network Time Protocol (version 1) specification and implementation
This memo describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. NTP provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse internet operating at rates from mundane to lightwave. It uses a returnable-time design in which a distributed subnet of time servers operating in a self- organizing, hierarchical master-slave configuration synchronizes logical clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute reference time via local routing algorithms and time daemons. The NTP architectures, algorithms and protocols which have evolved over several years of implementation and refinement are described in this document. The prototype system, which has been in regular operation in the Internet for the last two years, is described in an Appendix along with performance data which shows that timekeeping accuracy throughout most portions of the Internet can be ordinarily maintained to within a few tens of milliseconds, even the cases of failure or disruption of clocks, time servers or nets. This is a Draft Standard for an Elective protocol.
July 1988
Status: UNKNOWN
Autor: D.L. Mills
RFC1060 Assigned numbers
This memo is a status report on the parameters (i.e., numbers and keywords) used in protocols in the Internet community. Distribution of this memo is unlimited.
March 1990
Status: HISTORIC
Autor: J.K. Reynolds, J. Postel
RFC1062 Internet numbers
This memo is an official status report on the network numbers and gateway autonomous system numbers used in the Internet community.
August 1988
Status: UNKNOWN
Autor: S. Romano, M.K. Stahl, M. Recker
RFC1063 IP MTU discovery options
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.
July 1988
Status: UNKNOWN
Autor: J.C. Mogul, C.A. Kent, C. Partridge, K. McCloghrie
RFC1064 Interactive Mail Access Protocol: Version 2
This memo suggests a method for workstations to dynamically access mail from a mailbox server ("respository"). This RFC specifies a standard for the SUMEX-AIM community and a proposed experimental protocol for the Internet community. Discussion and suggestions for improvement are requested.
July 1988
Status: UNKNOWN
Autor: M.R. Crispin
RFC1065 Structure and identification of management information for TCP/IP-based internets
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.
August 1988
Status: STANDARD
Autor: K. McCloghrie, M.T. Rose
RFC1066 Management Information Base for network management of TCP/IP-based internets
This RFC provides the initial version of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets in the short-term. In particular, together with its companion memos which describe the structure of management information along with the initial network management protocol, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets, and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementations in the Internet which are network manageable are expected to adopt and implement this specification.
August 1988
Status: UNKNOWN
Autor: K. McCloghrie, M.T. Rose
RFC1067 Simple Network Management Protocol
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.
August 1988
Status: UNKNOWN
Autor: J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin
RFC1068 Background File Transfer Program (BFTP)
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.
August 1988
Status: UNKNOWN
Autor: A.L. DeSchon, R.T. Braden
RFC1069 Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol
This RFC suggests an addressing scheme for use with the ISO Connectionless Network Protocol (CLNP) in the Internet. This is a solution to one of the problems inherent in the use of "ISO-grams" in the Internet. This memo is a revision of RFC 986. This RFC suggests a proposed protocol for the Internet community, and requests discussion and suggestions for improvements.
February 1989
Status: UNKNOWN
Autor: R.W. Callon, H.W. Braun
RFC1070 Use of the Internet as a subnetwork for experimentation with the OSI network layer
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.
February 1989
Status: UNKNOWN
Autor: R.A. Hagens, N.E. Hall, M.T. Rose
RFC1071 Computing the Internet checksum
This RFC summarizes techniques and algorithms for efficiently computing the Internet checksum. It is not a standard, but a set of useful implementation techniques.
September 1988
Status: UNKNOWN
Autor: R.T. Braden, D.A. Borman, C. Partridge
RFC1072 TCP extensions for long-delay paths
This RFC proposes a set of extensions to the TCP protocol to provide efficient operation over a path with a high bandwidth*delay product. These extensions are not proposed as an Internet standard at this time. Instead, they are intended as a basis for further experimentation and research on transport protocol performance.
October 1988
Status: HISTORIC
Autor: V. Jacobson, R.T. Braden
RFC1073 Telnet window size option
This RFC describes a proposed Telnet option to allow a client to convey window size to a Telnet server.
October 1988
Status: PROPOSED STANDARD
Autor: D. Waitzman
RFC1074 NSFNET backbone SPF based Interior Gateway Protocol
This RFC is an implementation description of the standard ANSI IS-IS and ISO ES-IS routing protocols within the NSFNET backbone network.
October 1988
Status: UNKNOWN
Autor: J. Rekhter
RFC1075 Distance Vector Multicast Routing Protocol
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.
November 1988
Status: EXPERIMENTAL
Autor: D. Waitzman, C. Partridge, S.E. Deering
RFC1076 HEMS monitoring and control language
This RFC specifies a query language for monitoring and control of network entities. This RFC supercedes RFC 1023, extending the query language and providing more discussion of the underlying issues. This language is a component of the High-Level Entity Monitoring System (HEMS) described in RFC 1021 and RFC 1022. Readers may wish to consult these RFCs when reading this memo. RFC 1024 contains detailed assignments of numbers and structures used in this system. Portions of RFC 1024 that define query language structures are superceded by definitions in this memo. This memo assumes a knowledge of the ISO data encoding standard, ASN.1.
November 1988
Status: UNKNOWN
Autor: G. Trewitt, C. Partridge
RFC1077 Critical issues in high bandwidth networking
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.
November 1988
Status: UNKNOWN
Autor: B.M. Leiner
RFC1078 TCP port service Multiplexer (TCPMUX)
This RFC proposes an Internet standard which can be used by future TCP services instead of using 'well-known ports'.
November 1988
Status: UNKNOWN
Autor: M. Lottor
RFC1079 Telnet terminal speed option
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.
December 1988
Status: PROPOSED STANDARD
Autor: C.L. Hedrick
RFC1080 Telnet remote flow control option
This RFC specifies a standard for the Internet community. Hosts on the Internet that do remote flow control within the Telnet protocol are expected to adopt and implement this standard.
November 1988
Status: UNKNOWN
Autor: C.L. Hedrick
RFC1081 Post Office Protocol: Version 3
This memo suggests a simple method for workstations to dynamically access mail from a mailbox server. This RFC specifies a proposed protocol for the Internet community, and requests discussion and suggestions for improvements.
November 1988
Status: UNKNOWN
Autor: M.T. Rose
RFC1082 Post Office Protocol: Version 3: Extended service offerings
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.
November 1988
Status: UNKNOWN
Autor: M.T. Rose
RFC1083 IAB official protocol standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). 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.
December 1988
Status: HISTORIC
Autor: Defense Advanced Research Projects Agency, Internet Activities Board
RFC1084 BOOTP vendor information extensions
This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville. This memo will be updated as additional tags are are defined. This edition introduces Tag 13 for Boot File Size. Comments and suggestions for improvements are sought.
December 1988
Status: UNKNOWN
Autor: J.K. Reynolds
RFC1085 ISO presentation services on top of TCP/IP based internets
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.
December 1988
Status: UNKNOWN
Autor: M.T. Rose
RFC1086 ISO-TP0 bridge between TCP and X.25
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.
December 1988
Status: UNKNOWN
Autor: J.P. Onions, M.T. Rose
RFC1087 Ethics and the Internet
This memo is a statement of policy by the Internet Activities Board (IAB) concerning the proper use of the resources of the Internet.
January 1989
Status: UNKNOWN
Autor: Defense Advanced Research Projects Agency, Internet Activities Board
RFC1088 Standard for the transmission of IP datagrams over NetBIOS networks
This document specifies a standard method of encapsulating the Internet Protocol (IP) datagrams on NetBIOS networks.
February 1989
Status: STANDARD
Autor: L.J. McLaughlin
RFC1089 SNMP over Ethernet
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.
February 1989
Status: UNKNOWN
Autor: M. Schoffstall, C. Davin, M. Fedor, J. Case
RFC1090 SMTP on X.25
This memo proposes a standard for SMTP on the virtual circuit facility provided by the X.25 standard of the CCITT.
February 1989
Status: UNKNOWN
Autor: R. Ullmann
RFC1091 Telnet terminal-type option
This RFC specifies a standard for the Internet community. Hosts on the Internet that exchange terminal type information within the Telnet protocol are expected to adopt and implement this standard. This standard supersedes RFC 930. A change is made to permit cycling through a list of possible terminal types and selecting the most appropriate
February 1989
Status: PROPOSED STANDARD
Autor: J. VanBokkelen
RFC1092 EGP and policy based routing in the new NSFNET backbone
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.
February 1989
Status: UNKNOWN
Autor: J. Rekhter
RFC1093 NSFNET routing architecture
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.
February 1989
Status: UNKNOWN
Autor: H.W. Braun
RFC1094 NFS: Network File System Protocol specification
This RFC describes a protocol that Sun Microsystems, Inc., and others are using. A new version of the protocol is under development, but others may benefit from the descriptions of the current protocol, and discussion of some of the design issues.
March 1989
Status: INFORMATIONAL
Autor: B. Nowicki
RFC1095 Common Management Information Services and Protocol over TCP/IP (CMOT)
This memo defines a network management architecture that uses the International Organization for Standardization's (ISO) Common Management Information Services/Common Management Information Protocol (CMIS/CMIP) in a TCP/IP environment. This architecture provides a means by which control and monitoring information can be exchanged between a manager and a remote network element. In particular, this memo defines the means for implementing the Draft International Standard (DIS) version of CMIS/CMIP on top of Internet transport protocols for the purpose of carrying management information defined in the Internet-standard management information base. DIS CMIS/CMIP is suitable for deployment in TCP/IP networks while CMIS/CMIP moves toward becoming an International Standard. Together with the relevant ISO standards and the companion RFCs that describe the initial structure of management information and management information base, these documents provide the basis for a comprehensive architecture and system for managing TCP/IP- based internets, and in particular the Internet.
April 1989
Status: UNKNOWN
Autor: U.S. Warrier, L. Besaw
RFC1096 Telnet X display location option
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.
March 1989
Status: PROPOSED STANDARD
Autor: G.A. Marcy
RFC1097 Telnet subliminal-message option
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.
April 1989
Status: UNKNOWN
Autor: B. Miller
RFC1098 Simple Network Management Protocol (SNMP)
This RFC is a re-release of RFC 1067, with a changed "Status of this Memo" section. This memo defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. In particular, together with its companion memos which describe the structure of management information along with the initial management information base, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular the Internet.
April 1989
Status: UNKNOWN
Autor: J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin
RFC1099 Request for Comments Summary: RFC Numbers 1000-1099
December 1991
Status: INFORMATIONAL
Autor: J. Reynolds
RFC1100 IAB official protocol standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). 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.
April 1989
Status: HISTORIC
Autor: Defense Advanced Research Projects Agency, Internet Activities Board
RFC1101 DNS encoding of network names and other types
This RFC proposes two extensions to the Domain Name System: - A specific method for entering and retrieving RRs which map between network names and numbers. - Ideas for a general method for describing mappings between arbitrary identifiers and numbers. The method for mapping between network names and addresses is a proposed standard, the ideas for a general method are experimental.
April 1989
Status: UNKNOWN
Autor: P.V. Mockapetris
RFC1102 Policy routing in Internet protocols
The purpose of this RFC is to focus discussion on particular problems in the Internet and possible methods of solution. No proposed solutions in this document are intended as standards for the Internet.
May 1989
Status: UNKNOWN
Autor: D.D. Clark
RFC1103 Proposed standard for the transmission of IP datagrams over FDDI Networks
This RFC specifies a method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK]
June 1989
Status: UNKNOWN
Autor: D. Katz
RFC1104 Models of policy based routing
The purpose of this RFC is to outline a variety of models for policy based routing. The relative benefits of the different approaches are reviewed. Discussions and comments are explicitly encouraged to move toward the best policy based routing model that scales well within a large internetworking environment.
June 1989
Status: UNKNOWN
Autor: H.W. Braun
RFC1105 Border Gateway Protocol (BGP)
This RFC outlines a specific approach for the exchange of network reachability information between Autonomous Systems. Updated by RFCs 1163 and 1164. [STANDARDS-TRACK]
June 1989
Status: EXPERIMENTAL
Autor: K. Lougheed, Y. Rekhter
RFC1106 TCP big window and NAK options
This memo discusses two extensions to the TCP protocol to provide a more efficient operation over a network with a high bandwidth*delay product. The extensions described in this document have been implemented and shown to work using resources at NASA. This memo describes an Experimental Protocol, these extensions are not proposed as an Internet standard, but as a starting point for further research.
June 1989
Status: HISTORIC
Autor: R. Fox
RFC1107 Plan for Internet directory services
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.
July 1989
Status: INFORMATIONAL
Autor: K.R. Sollins
RFC1108 U.S. Department of Defense Security Options for the Internet Protocol
This RFC specifies the U.S. Department of Defense Basic Security Option 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. [STANDARDS-TRACK]
November 1991
Status: HISTORIC
Autor: S. Kent
RFC1109 Report of the second Ad Hoc Network Management Review Group
This RFC reports an official Internet Activities Board (IAB) policy position on the treatment of Network Management in the Internet. This RFC presents the results and recommendations of the second Ad Hoc Network Management Review on June 12, 1989. The results of the first such meeting were reported in RFC 1052.
August 1989
Status: UNKNOWN
Autor: V.G. Cerf
RFC1110 Problem with the TCP big window option
This memo comments on the TCP Big Window option described in RFC 1106.
August 1989
Status: HISTORIC
Autor: A.M. McKenzie
RFC1111 Request for comments on Request for Comments: Instructions to RFC authors
This RFC specifies a standard for the Internet community. Authors of RFCs are expected to adopt and implement this standard.
August 1989
Status: INFORMATIONAL
Autor: J. Postel
RFC1112 Host extensions for IP multicasting
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]
August 1989
Status: STANDARD
Autor: S.E. Deering
RFC1113 Privacy enhancement for Internet electronic mail: Part I - message encipherment and authentication procedures
This RFC specifies features for private electronic mail based on encryption technology. [STANDARDS-TRACK]
August 1989
Status: HISTORIC
Autor: J. Linn
RFC1114 Privacy enhancement for Internet electronic mail: Part II - certificate-based key management
This RFC specifies the key management aspects of Privacy Enhanced Mail. [STANDARDS-TRACK]
August 1989
Status: HISTORIC
Autor: S.T. Kent, J. Linn
RFC1115 Privacy enhancement for Internet electronic mail: Part III - algorithms, modes, and identifiers
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]
August 1989
Status: HISTORIC
Autor: J. Linn
RFC1116 Telnet Linemode option
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]
August 1989
Status: PROPOSED STANDARD
Autor: D.A. Borman
RFC1117 Internet numbers
This memo is an official status report on the network numbers and the autonomous system numbers used in the Internet community.
August 1989
Status: INFORMATIONAL
Autor: S. Romano, M.K. Stahl, M. Recker
RFC1118 Hitchhikers guide to the Internet
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.
September 1989
Status: INFORMATIONAL
Autor: E. Krol
RFC1119 Network Time Protocol (version 2) specification and implementation
This document describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. NTP provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse internet operating at rates from mundane to lightwave. It uses a returnable-time design in which a distributed subnet of time servers operating in a self- organizing, hierarchical-master-slave configuration synchronizes local clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute reference time via local routing algorithms and time daemons. [STANDARDS-TRACK]
September 1989
Status: STANDARD
Autor: D.L. Mills
RFC1120 Internet Activities Board
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.
September 1989
Status: INFORMATIONAL
Autor: V. Cerf
RFC1121 Act one - the poems
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.
September 1989
Status: INFORMATIONAL
Autor: J. Postel, L. Kleinrock, V.G. Cerf, B. Boehm
RFC1122 Requirements for Internet Hosts - Communication Layers
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]
October 1989
Status: STANDARD
Autor: R. Braden
RFC1123 Requirements for Internet Hosts - Application and Support
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]
October 1989
Status: STANDARD
Autor: R. Braden
RFC1124 Policy issues in interconnecting networks
To support the activities of the Federal Research Internet Coordinating Committee (FRICC) in creating an interconnected set of networks to serve the research community, two workshops were held to address the technical support of policy issues that arise when interconnecting such networks. Held under the suspices of the Internet Activities Board at the request of the FRICC, and sponsored by NASA through RIACS, the workshops addressed the required and feasible technologies and architectures that could be used to satisfy the desired policies for interconnection. The purpose of this RFC is to report the results of these workshops.
September 1989
Status: UNKNOWN
Autor: B.M. Leiner
RFC1125 Policy requirements for inter Administrative Domain routing
The purpose of this memo is to focus discussion on particular problems in the Internet and possible methods of solution. No proposed solutions in this document are intended as standards for the Internet. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to such problems, leading eventually to the development and adoption of standards.
November 1989
Status: UNKNOWN
Autor: D. Estrin
RFC1126 Goals and functional requirements for inter-autonomous system routing
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.
October 1989
Status: UNKNOWN
Autor: M. Little
RFC1127 Perspective on the Host Requirements RFCs
This RFC is for information only; it does not constitute a standard, draft standard, or proposed standard, and it does not define a protocol.
October 1989
Status: INFORMATIONAL
Autor: R.T. Braden
RFC1128 Measured performance of the Network Time Protocol in the Internet system
This paper describes a series of experiments involving over 100,000 hosts of the Internet system and located in the U.S., Europe and the Pacific. The experiments are designed to evaluate the availability, accuracy and reliability of international standard time distribution using the DARPA/NSF Internet and the Network Time Protocol (NTP), which is specified in RFC-1119. NTP is designed specifically for use in a large, diverse internet system operating at speeds from mundane to lightwave. In NTP a distributed subnet of time servers operating in a self-organizing, hierarchical, master-slave configuration exchange precision timestamps in order to synchronize subnet clocks to each other and national time standards via wire or radio. The experiments are designed to locate Internet hosts and gateways that provide time by one of three time distribution protocols and evaluate the accuracy of their indications. For those hosts that support NTP, the experiments determine the distribution of errors and other statistics over paths spanning major portions of the globe. Finally, the experiments evaluate the accuracy and reliability of precision timekeeping using NTP and typical Internet paths involving DARPA, NSFNET and other agency networks. The experiments demonstrate that timekeeping accuracy throughout most portions of the Internet can be ordinarily maintained to within a few tens of milliseconds, even in cases of failure or disruption of clocks, time servers or networks. This memo does not specify a standard.
October 1989
Status: UNKNOWN
Autor: D.L. Mills
RFC1129 Internet Time Synchronization: The Network Time Protocol
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.
October 1989
Status: INFORMATIONAL
Autor: D.L. Mills
RFC1130 IAB official protocol standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB).
October 1989
Status: HISTORIC
Autor: Defense Advanced Research Projects Agency, Internet Activities Board
RFC1131 OSPF specification
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]
October 1989
Status: PROPOSED STANDARD
Autor: J. Moy
RFC1132 Standard for the transmission of 802.2 packets over IPX networks
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.
November 1989
Status: STANDARD
Autor: L.J. McLaughlin
RFC1133 Routing between the NSFNET and the DDN
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.
November 1989
Status: INFORMATIONAL
Autor: J.Y. Yu, H.W. Braun
RFC1134 Point-to-Point Protocol: A proposal for multi-protocol transmission of datagrams over Point-to-Point links
This proposal 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 Point-to-Point Protocol Working Group chair by January 15, 1990. Comments will be reviewed at the February 1990 IETF meeting, with the goal of advancing PPP to draft standard status. [STANDARDS-TRACK]
November 1989
Status: PROPOSED STANDARD
Autor: D. Perkins
RFC1135 Helminthiasis of the Internet
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.
December 1989
Status: INFORMATIONAL
Autor: J.K. Reynolds
RFC1136 Administrative Domains and Routing Domains: A model for routing in the Internet
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.
December 1989
Status: INFORMATIONAL
Autor: S. Hares, D. Katz
RFC1137 Mapping between full RFC 822 and RFC 822 with restricted encoding
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.
December 1989
Status: HISTORIC
Autor: S. Kille
RFC1138 Mapping between X.400(1988) / ISO 10021 and RFC 822
Ths RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. This memo updates RFCs 822, 987, and 1026.
December 1989
Status: EXPERIMENTAL
Autor: S.E. Kille
RFC1139 Echo function for ISO 8473
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. This memo is not intended to compete with an ISO standard. [STANDARDS-TRACK]
January 1990
Status: PROPOSED STANDARD
Autor: R.A. Hagens
RFC1140 IAB official protocol standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo 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.
May 1990
Status: HISTORIC
Autor: Defense Advanced Research Projects Agency, Internet Activities Board
RFC1141 Incremental updating of the Internet checksum
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.
January 1990
Status: INFORMATIONAL
Autor: T. Mallory, A. Kullberg
RFC1142 OSI IS-IS Intra-domain Routing Protocol
This RFC is a republication of ISO DP 10589 as a service to the Internet community. This is not an Internet standard.
February 1990
Status: INFORMATIONAL
Autor: D. Oran
RFC1143 The Q Method of Implementing TELNET Option Negotiation
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.
February 1990
Status: EXPERIMENTAL
Autor: D.J. Bernstein
RFC1144 Compressing TCP/IP Headers for Low-Speed Serial Links
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]
February 1990
Status: PROPOSED STANDARD
Autor: V. Jacobson
RFC1145 TCP alternate checksum options
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.
February 1990
Status: HISTORIC
Autor: J. Zweig, C. Partridge
RFC1146 TCP alternate checksum options
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.
March 1990
Status: HISTORIC
Autor: J. Zweig, C. Partridge
RFC1147 FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices
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.
April 1990
Status: INFORMATIONAL
Autor: R.H. Stine
RFC1148 Mapping between X.400(1988) / ISO 10021 and RFC 822
This RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. This edition includes material lost in editing.
March 1990
Status: EXPERIMENTAL
Autor: S.E. Kille
RFC1149 Standard for the transmission of IP datagrams on avian carriers
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.
April 1990
Status: EXPERIMENTAL
Autor: D. Waitzman
RFC1150 FYI on FYI: Introduction to the FYI Notes
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.]
March 1990
Status: HISTORIC
Autor: G.S. Malkin, J.K. Reynolds
RFC1151 Version 2 of the Reliable Data Protocol (RDP)
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.
April 1990
Status: EXPERIMENTAL
Autor: C. Partridge, R.M. Hinden
RFC1152 Workshop report: Internet research steering group workshop on very-high-speed networks
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.
April 1990
Status: INFORMATIONAL
Autor: C. Partridge
RFC1153 Digest message format
This memo describes the de facto standard Digest Message Format. This is an elective experimental protocol.
April 1990
Status: EXPERIMENTAL
Autor: F.J. Wancho
RFC1154 Encoding header field for internet messages
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).
April 1990
Status: EXPERIMENTAL
Autor: D. Robinson, R. Ullmann
RFC1155 Structure and identification of management information for TCP/IP-based internets
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]
May 1990
Status: STANDARD
Autor: M.T. Rose, K. McCloghrie
RFC1156 Management Information Base for network management of TCP/IP-based internets
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]
May 1990
Status: HISTORIC
Autor: K. McCloghrie, M.T. Rose
RFC1157 Simple Network Management Protocol (SNMP)
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]
May 1990
Status: HISTORIC
Autor: J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin
RFC1158 Management Information Base for network management of TCP/IP-based internets: MIB-II
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]
May 1990
Status: PROPOSED STANDARD
Autor: M.T. Rose
RFC1159 Message Send Protocol
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.
June 1990
Status: EXPERIMENTAL
Autor: R. Nelson
RFC1160 Internet Activities Board
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.
May 1990
Status: INFORMATIONAL
Autor: V. Cerf
RFC1161 SNMP over OSI
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,
June 1990
Status: EXPERIMENTAL
Autor: M.T. Rose
RFC1162 Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) Management Information Base
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.
June 1990
Status: EXPERIMENTAL
Autor: G. Satz
RFC1163 Border Gateway Protocol (BGP)
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]
June 1990
Status: HISTORIC
Autor: K. Lougheed, Y. Rekhter
RFC1164 Application of the Border Gateway Protocol in the Internet
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]
June 1990
Status: HISTORIC
Autor: J.C. Honig, D. Katz, M. Mathis, Y. Rekhter, J.Y. Yu
RFC1165 Network Time Protocol (NTP) over the OSI Remote Operations Service
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.
June 1990
Status: EXPERIMENTAL
Autor: J. Crowcroft, J.P. Onions
RFC1166 Internet numbers
This memo is a status report on the network numbers and autonomous system numbers used in the Internet community.
July 1990
Status: INFORMATIONAL
Autor: S. Kirkpatrick, M.K. Stahl, M. Recker
RFC1167 Thoughts on the National Research and Education Network
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.
July 1990
Status: INFORMATIONAL
Autor: V.G. Cerf
RFC1168 Intermail and Commercial Mail Relay services
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.
July 1990
Status: INFORMATIONAL
Autor: A. Westine, A.L. DeSchon, J. Postel, C.E. Ward
RFC1169 Explaining the role of GOSIP
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.
August 1990
Status: INFORMATIONAL
Autor: V.G. Cerf, K.L. Mills
RFC1170 Public key standards and licenses
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.
January 1991
Status: INFORMATIONAL
Autor: R.B. Fougner
RFC1171 Point-to-Point Protocol for the transmission of multi-protocol datagrams over Point-to-Point links
This memo specifies the Point-to-Point Protocol (PPP) as a Draft Standard Protocol for the Internet community. When it becomes a full Standard, this protocol will be recommended for all TCP/IP implementations that communicate over serial links.
July 1990
Status: DRAFT STANDARD
Autor: D. Perkins
RFC1172 Point-to-Point Protocol (PPP) initial configuration options
This memo specifies the Point-to-Point Protocol (PPP) Initial Configuration Options as a Proposed Standard Protocol for the Internet community. When it becomes a full Standard, this protocol will be recommended for all TCP/IP implementations that communicate over serial links.
July 1990
Status: PROPOSED STANDARD
Autor: D. Perkins, R. Hobby
RFC1173 Responsibilities of host and network managers: A summary of the "oral tradition" of the Internet
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.
August 1990
Status: INFORMATIONAL
Autor: J. VanBokkelen
RFC1174 IAB recommended policy on distributing internet identifier assignment and IAB recommended policy change to internet "connected" status
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.
August 1990
Status: INFORMATIONAL
Autor: V.G. Cerf
RFC1175 FYI on where to start: A bibliography of internetworking information
This FYI RFC is a bibliography of information about TCP/IP internetworking, prepared by the User Services Working Group (USWG) of the Internet Engineering Task Force (IETF). This memo provides information for the Internet community. It does not specify any standard. [Also FYI 3.]
August 1990
Status: INFORMATIONAL
Autor: K.L. Bowers, T.L. LaQuey, J.K. Reynolds, K. Roubicek, M.K. Stahl, A. Yuan
RFC1176 Interactive Mail Access Protocol: Version 2
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.
August 1990
Status: EXPERIMENTAL
Autor: M.R. Crispin
RFC1177 FYI on Questions and Answers: Answers to commonly asked "new internet user" questions
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.]
August 1990
Status: INFORMATIONAL
Autor: G.S. Malkin, A.N. Marine, J.K. Reynolds
RFC1178 Choosing a name for your computer
This FYI RFC is a republication of a Communications of the ACM article on guidelines on what to do and what not to do when naming your computer. This memo provides information for the Internet community. It does not specify any standard. [Also FYI 5.]
August 1990
Status: INFORMATIONAL
Autor: D. Libes
RFC1179 Line printer daemon protocol
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.
August 1990
Status: INFORMATIONAL
Autor: L. McLaughlin
RFC1180 TCP/IP tutorial
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.
January 1991
Status: INFORMATIONAL
Autor: T.J. Socolofsky, C.J. Kale
RFC1181 RIPE Terms of Reference
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.
September 1990
Status: INFORMATIONAL
Autor: R. Blokzijl
RFC1183 New DNS RR Definitions
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.
October 1990
Status: EXPERIMENTAL
Autor: C.F. Everhart, L.A. Mamakos, R. Ullmann, P.V. Mockapetris
RFC1184 Telnet Linemode Option
This RFC specifies a procedure for line at a time terminal interaction based on the Telnet Protocol. It obsoletes RFC 1116. [STANDARDS-TRACK]
October 1990
Status: DRAFT STANDARD
Autor: D.A. Borman
RFC1185 TCP Extension for High-Speed Paths
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.
October 1990
Status: EXPERIMENTAL
Autor: V. Jacobson, R.T. Braden, L. Zhang
RFC1186 MD4 Message Digest Algorithm
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.
October 1990
Status: INFORMATIONAL
Autor: R.L. Rivest
RFC1187 Bulk Table Retrieval with the SNMP
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.
October 1990
Status: EXPERIMENTAL
Autor: M.T. Rose, K. McCloghrie, J.R. Davin
RFC1188 Proposed Standard for the Transmission of IP Datagrams over FDDI Networks
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. [STANDARDS-TRACK]
October 1990
Status: DRAFT STANDARD
Autor: D. Katz
RFC1189 Common Management Information Services and Protocols for the Internet (CMOT and CMIP)
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]
October 1990
Status: HISTORIC
Autor: U.S. Warrier, L. Besaw, L. LaBarre, B.D. Handspicker
RFC1190 Experimental Internet Stream Protocol: Version 2 (ST-II)
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.
October 1990
Status: EXPERIMENTAL
Autor: C. Topolcic
RFC1191 Path MTU discovery
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. [STANDARDS-TRACK]
November 1990
Status: DRAFT STANDARD
Autor: J.C. Mogul, S.E. Deering
RFC1192 Commercialization of the Internet summary report
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.
November 1990
Status: INFORMATIONAL
Autor: B. Kahin
RFC1193 Client requirements for real-time communication services
This memo describes client requirements for real-time communication services. This memo provides information for the Internet community, and requests discussion and suggestions for improvements. It does not specify any standard.
November 1990
Status: INFORMATIONAL
Autor: D. Ferrari
RFC1194 Finger User Information Protocol
This memo describes the Finger User Information Protocol. This is a simple protocol which provides an interface to a remote user information program. Based on RFC 742, a description of the original Finger protocol, this memo attempts to clarify the expected communication between the two ends of a Finger connection. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition. [STANDARDS-TRACK]
November 1990
Status: DRAFT STANDARD
Autor: D.P. Zimmerman
RFC1195 Use of OSI IS-IS for routing in TCP/IP and dual environments
This memo specifies an integrated routing protocol, based on the OSI Intra-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 Task Force. [STANDARDS-TRACK]
December 1990
Status: PROPOSED STANDARD
Autor: R.W. Callon
RFC1196 Finger User Information Protocol
This memo describes the Finger User Information Protocol. This is a simple protocol which provides an interface to a remote user information program. Based on RFC 742, a description of the original Finger protocol, this memo attempts to clarify the expected communication between the two ends of a Finger connection. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition. This edition corrects and clarifies in a minor way, RFC 1194. [STANDARDS-TRACK]
December 1990
Status: DRAFT STANDARD
Autor: D.P. Zimmerman
RFC1197 Using ODA for translating multimedia information
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.
December 1990
Status: INFORMATIONAL
Autor: M. Sherman
RFC1198 FYI on the X window system
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.
January 1991
Status: INFORMATIONAL
Autor: R.W. Scheifler
RFC1199 Request for Comments Summary Notes: 1100-1199
December 1991
Status: INFORMATIONAL
Autor: J. Reynolds
RFC1200 IAB official protocol standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). 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.
April 1991
Status: HISTORIC
Autor: Defense Advanced Research Projects Agency, Internet Activities Board
RFC1201 Transmitting IP traffic over ARCNET networks
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]
February 1991
Status: STANDARD
Autor: D. Provan
RFC1202 Directory Assistance service
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.
February 1991
Status: INFORMATIONAL
Autor: M.T. Rose
RFC1203 Interactive Mail Access Protocol: Version 3
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.
February 1991
Status: HISTORIC
Autor: J. Rice
RFC1204 Message Posting Protocol (MPP)
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.
February 1991
Status: EXPERIMENTAL
Autor: S. Yeh, D. Lee
RFC1205 5250 Telnet interface
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.
February 1991
Status: INFORMATIONAL
Autor: P. Chmielewski
RFC1206 FYI on Questions and Answers: Answers to commonly asked "new Internet user" questions
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]
February 1991
Status: INFORMATIONAL
Autor: G.S. Malkin, A.N. Marine
RFC1207 FYI on Questions and Answers: Answers to commonly asked "experienced Internet user" questions
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.
February 1991
Status: INFORMATIONAL
Autor: G.S. Malkin, A.N. Marine, J.K. Reynolds
RFC1208 A Glossary of Networking Terms
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.
March 1991
Status: INFORMATIONAL
Autor: O.J. Jacobsen, D.C. Lynch
RFC1209 The Transmission of IP Datagrams over the SMDS Service
This memo defines a protocol for the transmission of IP and ARP packets over a Switched Multi-megabit Data Service Network configured as a logical IP subnetwork. [STANDARDS-TRACK]
March 1991
Status: STANDARD
Autor: D. Piscitello, J. Lawrence
RFC1210 Network and infrastructure user requirements for transatlantic research collaboration: Brussels, July 16-18, and Washington July 24-25, 1990
This report complements a shorter printed version which appeared in a summary report of all the committees which met in Brussels and Washington last July, 1990. This memo provides information for the Internet community. It does not specify an Internet standard.
March 1991
Status: INFORMATIONAL
Autor: V.G. Cerf, P.T. Kirstein, B. Randell
RFC1211 Problems with the maintenance of large mailing lists
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.
March 1991
Status: INFORMATIONAL
Autor: A. Westine, J. Postel
RFC1212 Concise MIB definitions
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]
March 1991
Status: STANDARD
Autor: M.T. Rose, K. McCloghrie
RFC1213 Management Information Base for Network Management of TCP/IP-based internets:MIB-II
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]
March 1991
Status: STANDARD
Autor: K. McCloghrie, M. Rose
RFC1214 OSI internet management: Management Information Base
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. [STANDARDS-TRACK]
April 1991
Status: HISTORIC
Autor: L. LaBarre
RFC1215 Convention for defining traps for use with the SNMP
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.
March 1991
Status: INFORMATIONAL
Autor: M.T. Rose
RFC1216 Gigabit network economics and paradigm shifts
This memo proposes a new standard paradigm for the Internet Activities Board (IAB) standardization track. [STANDARDS-TRACK]
April 1991
Status: INFORMATIONAL
Autor: P. Richard, P. Kynikos
RFC1217 Memo from the Consortium for Slow Commotion Research (CSCR)
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.
April 1991
Status: INFORMATIONAL
Autor: V.G. Cerf
RFC1218 Naming scheme for c=US
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.
April 1991
Status: INFORMATIONAL
Autor: North American Directory Forum
RFC1219 On the assignment of subnet numbers
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.
April 1991
Status: INFORMATIONAL
Autor: P.F. Tsuchiya
RFC1220 Point-to-Point Protocol extensions for bridging
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]
April 1991
Status: PROPOSED STANDARD
Autor: F. Baker
RFC1221 Host Access Protocol (HAP) specification: Version 2
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.
April 1991
Status: INFORMATIONAL
Autor: W. Edmond
RFC1222 Advancing the NSFNET routing architecture
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.
May 1991
Status: INFORMATIONAL
Autor: H.W. Braun, Y. Rekhter
RFC1223 OSI CLNS and LLC1 protocols on Network Systems HYPERchannel
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.
May 1991
Status: INFORMATIONAL
Autor: J.M. Halpern
RFC1224 Techniques for managing asynchronously generated alerts
This memo defines common mechanisms for managing asynchronously produced alerts in a manner consistent with current network management protocols. This memo specifies an Experimental Protocol for the Internet community. It does not specify an Internet standard.
May 1991
Status: EXPERIMENTAL
Autor: L. Steinberg
RFC1225 Post Office Protocol: Version 3
This memo suggests a simple method for workstations to dynamically access mail from a mailbox server. [STANDARDS-TRACK]
May 1991
Status: DRAFT STANDARD
Autor: M.T. Rose
RFC1226 Internet protocol encapsulation of AX.25 frames
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.
May 1991
Status: EXPERIMENTAL
Autor: B. Kantor
RFC1227 SNMP MUX protocol and MIB
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.
May 1991
Status: HISTORIC
Autor: M.T. Rose
RFC1228 SNMP-DPI: Simple Network Management Protocol Distributed Program Interface
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.
May 1991
Status: EXPERIMENTAL
Autor: G. Carpenter, B. Wijnen
RFC1229 Extensions to the generic-interface MIB
This RFC contains definitions of managed objects used as experimental extensions to the generic interfaces structure of MIB-II. [STANDARDS-TRACK]
May 1991
Status: PROPOSED STANDARD
Autor: K. McCloghrie
RFC1230 IEEE 802.4 Token Bus MIB
This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, this memo defines managed objects used for managing subnetworks which use the IEEE 802.4 Token Bus technology described in 802.4 Token-Passing Bus Access Method and Physical Layer Specifications, IEEE Standard 802.4. [STANDARDS-TRACK]
May 1991
Status: HISTORIC
Autor: K. McCloghrie, R. Fox
RFC1231 IEEE 802.5 Token Ring MIB
This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, this memo defines managed objects used for managing subnetworks which use the IEEE 802.5 Token Ring technology described in 802.5 Token Ring Access Method and Physical Layer Specifications, IEEE Standard 802.5-1989. [STANDARDS-TRACK]
May 1991
Status: PROPOSED STANDARD
Autor: K. McCloghrie, R. Fox, E. Decker
RFC1232 Definitions of managed objects for the DS1 Interface type
May 1991
Status: PROPOSED STANDARD
Autor: F. Baker, C.P. Kolb
RFC1233 Definitions of managed objects for the DS3 Interface type
This memo defines objects for managing DS3 Interface objects for use with the SNMP protocol. [STANDARDS-TRACK]
May 1991
Status: PROPOSED STANDARD
Autor: T.A. Cox, K. Tesink
RFC1234 Tunneling IPX traffic through IP networks
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]
June 1991
Status: HISTORIC
Autor: D. Provan
RFC1235 Coherent File Distribution Protocol
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.
June 1991
Status: EXPERIMENTAL
Autor: J. Ioannidis, G. Maguire
RFC1236 IP to X.121 address mapping for DDN
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.
June 1991
Status: INFORMATIONAL
Autor: L. Morales, P. Hasse
RFC1237 Guidelines for OSI NSAP Allocation in the Internet
This paper provides guidelines for allocating NSAPs in the Internet.[STANDARDS-TRACK]
July 1991
Status: PROPOSED STANDARD
Autor: R. Colella, E. Gardner, R. Callon
RFC1238 CLNS MIB for use with Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542)
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.
June 1991
Status: EXPERIMENTAL
Autor: G. Satz
RFC1239 Reassignment of experimental MIBs to standard MIBs
This memo specifically updates RFC 1229, RFC 1230, RFC 1231, RFC 1232 and RFC 1233 with new codes. [STANDARDS-TRACK]
June 1991
Status: HISTORIC
Autor: J.K. Reynolds
RFC1240 OSI connectionless transport services on top of UDP: Version 1
This document describes a protocol for running OSI Connectionless service on UDP. [STANDARDS-TRACK]
June 1991
Status: HISTORIC
Autor: C. Shue, W. Haggerty, K. Dobbins
RFC1241 Scheme for an internet encapsulation protocol: Version 1
This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.
July 1991
Status: EXPERIMENTAL
Autor: R.A. Woodburn, D.L. Mills
RFC1242 Benchmarking Terminology for Network Interconnection Devices
This memo discusses and defines a number of terms that are used in describing performance benchmarking tests and the results of such tests. This memo provides information for the Internet community. It does not specify an Internet standard.
July 1991
Status: INFORMATIONAL
Autor: S. Bradner
RFC1243 AppleTalk Management Information Base
This memo defines objects for managing AppleTalk objects for use with the SNMP protocol. [STANDARDS-TRACK]
July 1991
Status: PROPOSED STANDARD
Autor: S. Waldbusser
RFC1244 Site Security Handbook
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]
July 1991
Status: INFORMATIONAL
Autor: J.P. Holbrook, J.K. Reynolds
RFC1245 OSPF Protocol Analysis
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.
July 1991
Status: INFORMATIONAL
Autor: J. Moy
RFC1246 Experience with the OSPF Protocol
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.
July 1991
Status: INFORMATIONAL
Autor: J. Moy
RFC1247 OSPF Version 2
This memo documents version 2 of the OSPF protocol. OSPF is a link- state based routing protocol. [STANDARDS-TRACK]
July 1991
Status: DRAFT STANDARD
Autor: J. Moy
RFC1248 OSPF Version 2 Management Information Base
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]
July 1991
Status: PROPOSED STANDARD
Autor: F. Baker, R. Coltun
RFC1249 DIXIE Protocol Specification
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.
August 1991
Status: INFORMATIONAL
Autor: T. Howes, M. Smith, B. Beecher
RFC1250 IAB Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo provides information for the Internet community. It does not specify an Internet standard.
August 1991
Status: HISTORIC
Autor: J. Postel
RFC1251 Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members
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]
August 1991
Status: INFORMATIONAL
Autor: G. Malkin
RFC1252 OSPF Version 2 Management Information Base
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS-TRACK]
August 1991
Status: PROPOSED STANDARD
Autor: F. Baker, R. Coltun
RFC1253 OSPF Version 2 Management Information Base
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS-TRACK]
August 1991
Status: PROPOSED STANDARD
Autor: F. Baker, R. Coltun
RFC1254 Gateway Congestion Control Survey
The purpose of this paper is to present a 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.
August 1991
Status: INFORMATIONAL
Autor: A. Mankin, K. Ramakrishnan
RFC1255 A Naming Scheme for c=US
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.
September 1991
Status: INFORMATIONAL
Autor: The North American Directory Forum
RFC1256 ICMP Router Discovery Messages
This document specifies an extension of the Internet Control Message Protocol (ICMP) to enable hosts attached to multicast or broadcast networks to discover the IP addresses of their neighboring routers. [STANDARDS-TRACK]
September 1991
Status: PROPOSED STANDARD
Autor: S. Deering
RFC1257 Isochronous applications do not require jitter-controlled networks
This memo argues that jitter control is not required for networks to support isochronous applications. This memo provides information for the Internet community. It does not specify an Internet standard.
September 1991
Status: INFORMATIONAL
Autor: C. Partridge
RFC1258 BSD Rlogin
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.
September 1991
Status: INFORMATIONAL
Autor: B. Kantor
RFC1259 Building the open road: The NREN as test-bed for the national public network
This memo discusses the background and importance of NREN. This memo provides information for the Internet community. It does not specify an Internet standard.
September 1991
Status: INFORMATIONAL
Autor: M. Kapor
RFC1261 Transition of Nic Services
This memo outlines the transition of NIC Services. This memo provides information for the Internet community. It does not specify an Internet standard.
September 1991
Status: INFORMATIONAL
Autor: S. Williamson, L. Nobile
RFC1262 Guidelines for Internet Measurement Activities
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.
October 1991
Status: INFORMATIONAL
Autor: V.G. Cerf
RFC1263 TCP Extensions Considered Harmful
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 the Internet protocol suite. This memo provides information for the Internet community. It does not specify an Internet standard.
October 1991
Status: INFORMATIONAL
Autor: S. O'Malley, L.L. Peterson
RFC1264 Internet Engineering Task Force Internet Routing Protocol Standardization Criteria
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.
October 1991
Status: HISTORIC
Autor: R.M. Hinden
RFC1265 BGP Protocol Analysis
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.
October 1991
Status: INFORMATIONAL
Autor: Y. Rekhter
RFC1266 Experience with the BGP Protocol
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.
October 1991
Status: INFORMATIONAL
Autor: Y. Rekhter
RFC1267 Border Gateway Protocol 3 (BGP-3)
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]
October 1991
Status: HISTORIC
Autor: K. Lougheed, Y. Rekhter
RFC1268 Application of the Border Gateway Protocol in the Internet
This document describes the usage of the BGP in the Internet. [STANDARDS-TRACK]
October 1991
Status: HISTORIC
Autor: Y. Rekhter, P. Gross
RFC1269 Definitions of Managed Objects for the Border Gateway Protocol: Version 3
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]
October 1991
Status: PROPOSED STANDARD
Autor: S. Willis, J.W. Burruss
RFC1270 SNMP Communications Services
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.
October 1991
Status: INFORMATIONAL
Autor: F. Kastenholz
RFC1271 Remote Network Monitoring Management Information Base
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices. [STANDARDS-TRACK]
November 1991
Status: PROPOSED STANDARD
Autor: S. Waldbusser
RFC1272 Internet Accounting: Background
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.
November 1991
Status: INFORMATIONAL
Autor: C. Mills, D. Hirsh, G.R. Ruth
RFC1273 Measurement Study of Changes in Service-Level Reachability in the Global TCP/IP Internet: Goals, Experimental Design, Implementation, and Policy Considerations
This memo describes plans to carry out a longitudinal measurement study of changes in service-level reachability in the global TCP/IP Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
November 1991
Status: INFORMATIONAL
Autor: M.F. Schwartz
RFC1274 The COSINE and Internet X.500 Schema
This document suggests an X.500 Directory Schema, or Naming Architecture, for use in the COSINE and Internet X.500 pilots. [STANDARDS-TRACK]
November 1991
Status: PROPOSED STANDARD
Autor: P. Barker, S. Kille
RFC1275 Replication Requirements to provide an Internet Directory using X.500
This RFC considers certain deficiencies of the 1988 X.500 standard, which need to be addressed before an effective open Internet Directory can be established using these protocols and services [CCI88]. This memo provides information for the Internet community. It does not specify an Internet standard.
November 1991
Status: INFORMATIONAL
Autor: S.E. Hardcastle-Kille
RFC1276 Replication and Distributed Operations extensions to provide an Internet Directory using X.500
Some requirements on extensions to X.500 are described in the RFC[HK91b], in order to build an Internet Directory using X.500(1988). This document specifies a set of solutions to the problems raised. [STANDARDS-TRACK]
November 1991
Status: HISTORIC
Autor: S.E. Hardcastle-Kille
RFC1277 Encoding Network Addresses to Support Operation over Non-OSI Lower Layers
This document defines a new network address format, and rules for using some existing network address formats. [STANDARDS-TRACK]
November 1991
Status: PROPOSED STANDARD
Autor: S.E. Hardcastle-Kille
RFC1278 A string encoding of Presentation Address
There are a number of environments where a simple string encoding of Presentation Address is desirable. This specification defines such a representation. This memo provides information for the Internet community. It does not specify an Internet standard.
November 1991
Status: INFORMATIONAL
Autor: S.E. Hardcastle-Kille
RFC1279 X.500 and Domains
This RFC considers X.500 in relation to Internet and UK Domains. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.
November 1991
Status: EXPERIMENTAL
Autor: S.E. Hardcastle-Kille
RFC1280 IAB Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo provides information for the Internet community. It does not specify an Internet standard.
March 1992
Status: HISTORIC
Autor: J. Postel
RFC1281 Guidelines for the Secure Operation of the Internet
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.
November 1991
Status: INFORMATIONAL
Autor: R. Pethia, S. Crocker, B. Fraser
RFC1282 BSD Rlogin
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.
December 1991
Status: INFORMATIONAL
Autor: B. Kantor
RFC1283 SNMP over OSI
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.
December 1991
Status: EXPERIMENTAL
Autor: M. Rose
RFC1284 Definitions of Managed Objects for the Ethernet-like Interface Types
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]
December 1991
Status: PROPOSED STANDARD
Autor: J. Cook
RFC1285 FDDI Management Information Base
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing devices which implement the FDDI. [STANDARDS-TRACK]
January 1992
Status: HISTORIC
Autor: J. Case
RFC1286 Definitions of Managed Objects for Bridges
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]
December 1991
Status: PROPOSED STANDARD
Autor: E. Decker, P. Langille, A. Rijsinghani, K. McCloghrie
RFC1287 Towards the Future Internet Architecture
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.
December 1991
Status: INFORMATIONAL
Autor: D. Clark, L. Chapin, V. Cerf, R. Braden, R. Hobby
RFC1288 The Finger User Information Protocol
This memo describes the Finger user information protocol.This is a simple protocol which provides an interface to a remote user information program. [STANDARDS-TRACK]
December 1991
Status: DRAFT STANDARD
Autor: D. Zimmerman
RFC1289 DECnet Phase IV MIB Extensions
This memo is an extension to the SNMP MIB. This memo defines a set of DECnet Phase IV extensions that have been created for the Internet MIB. [STANDARDS-TRACK]
December 1991
Status: PROPOSED STANDARD
Autor: J. Saperia
RFC1290 There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places
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. This RFC provides information for the Internet community. It does not specify an Internet standard.
December 1991
Status: INFORMATIONAL
Autor: J. Martin
RFC1291 Mid-Level Networks Potential Technical Services
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. This RFC provides information for the Internet community. It does not specify an Internet standard.
December 1991
Status: INFORMATIONAL
Autor: V. Aggarwal
RFC1292 A Catalog of Available X.500 Implementations
The goal of this document is to provide information regarding the availability and capability of implementations of X.500. This memo provides information for the Internet community. It does not specify an Internet standard.
January 1992
Status: INFORMATIONAL
Autor: R. Lang, R. Wright
RFC1293 Inverse Address Resolution Protocol
This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK]
January 1992
Status: PROPOSED STANDARD
Autor: T. Bradley, C. Brown
RFC1294 Multiprotocol Interconnect over Frame Relay
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]
January 1992
Status: PROPOSED STANDARD
Autor: T. Bradley, C. Brown, A. Malis
RFC1295 User Bill of Rights for entries and listings in the Public Directory
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 Optical Network/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 and RFC1407. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
January 1992
Status: INFORMATIONAL
Autor: The North American Directory Forum
RFC1296 Internet Growth (1981-1991)
This document illustrates the growth of the Internet by examination of entries in the Domain Name System (DNS) and pre-DNS host tables. This memo provides information for the Internet community. It does not specify an Internet 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 Frame Relay Service. [STANDARDS-TRACK]
January 1992
Status: INFORMATIONAL
Autor: M. Lottor
RFC1297 NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist ("NOC TT REQUIREMENTS")
This document explores competing uses, architectures, and desirable features of integrated internal trouble ticket systems for Network and other Operations Centers. This memo provides information for the Internet community. It does not specify an Internet standard.
January 1992
Status: INFORMATIONAL
Autor: D. Johnson
RFC1298 SNMP over IPX
This memo defines a convention for encapsulating Simple Network Management Protocol (SNMP) packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol. This memo provides information for the Internet community. It does not specify an Internet standard.
February 1992
Status: INFORMATIONAL
Autor: R. Wormley, S. Bostock
RFC1299 Summary of 1200-1299
January 1997
Status: INFORMATIONAL
Autor: M. Kennedy
RFC1300 Remembrances of Things Past
Poem. This memo provides information for the Internet community. It does not specify an Internet standard.
February 1992
Status: INFORMATIONAL
Autor: S. Greenfield
RFC1301 Multicast Transport Protocol
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.
February 1992
Status: INFORMATIONAL
Autor: S. Armstrong, A. Freier, K. Marzullo
RFC1302 Building a Network Information Services Infrastructure
This FYI RFC document is intended for existing Internet Network Information 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. This memo provides information for the Internet community. It does not specify an Internet standard.
February 1992
Status: INFORMATIONAL
Autor: D. Sitzler, P. Smith, A. Marine
RFC1303 A Convention for Describing SNMP-based Agents
This memo suggests a straight-forward approach towards describing SNMP- based agents. This memo provides information for the Internet community. It does not specify an Internet standard.
February 1992
Status: INFORMATIONAL
Autor: K. McCloghrie, M. Rose
RFC1304 Definitions of Managed Objects for the SIP Interface Type
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 Interface Protocol) objects. [STANDARDS-TRACK]
February 1992
Status: PROPOSED STANDARD
Autor: T. Cox, K. Tesink
RFC1305 Network Time Protocol (Version 3) Specification, Implementation and Analysis
This document describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. [STANDARDS-TRACK]
March 1992
Status: DRAFT STANDARD
Autor: D. Mills
RFC1306 Experiences Supporting By-Request Circuit-Switched T3 Networks
This memo describes the experiences of a project team at Cray Research, 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. This RFC provides information for the Internet community. It does not specify an Internet standard.
March 1992
Status: INFORMATIONAL
Autor: A. Nicholson, J. Young
RFC1307 Dynamically Switched Link Control Protocol
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. This memo defines an Experimental Protocol for the Internet community.
March 1992
Status: EXPERIMENTAL
Autor: J. Young, A. Nicholson
RFC1308 Executive Introduction to Directory Services Using the X.500 Protocol
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 memo provides information for the Internet community. It does not specify an Internet standard.
March 1992
Status: INFORMATIONAL
Autor: C. Weider, J. Reynolds
RFC1309 Technical Overview of Directory Services Using the X.500 Protocol
This document is an overview of the X.500 standard for people not familiar with the technology. It compares and contrasts Directory Services 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. This memo provides information for the Internet community. It does not specify an Internet standard.
March 1992
Status: INFORMATIONAL
Autor: C. Weider, J. Reynolds, S. Heker
RFC1310 The Internet Standards Process
This memo documents the process currently used for the standardization of Internet protocols and procedures. [STANDARDS-TRACK]
March 1992
Status: INFORMATIONAL
Autor: L. Chapin
RFC1311 Introduction to the STD Notes
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]
March 1992
Status: INFORMATIONAL
Autor: J. Postel
RFC1312 Message Send Protocol 2
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.
April 1992
Status: EXPERIMENTAL
Autor: R. Nelson, G. Arnold
RFC1313 Today's Programming for KRFC AM 1313 Internet Talk Radio
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.
April 1992
Status: INFORMATIONAL
Autor: C. Partridge
RFC1314 A File Format for the Exchange of Images in the Internet
This document defines a standard file format for the exchange of fax- like black and white images within the Internet. [STANDARDS-TRACK]
April 1992
Status: HISTORIC
Autor: A. Katz, D. Cohen
RFC1315 Management Information Base for Frame Relay DTEs
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. [STANDARDS-TRACK]
April 1992
Status: PROPOSED STANDARD
Autor: C. Brown, F. Baker, C. Carvalho
RFC1316 Definitions of Managed Objects for Character Stream Devices
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]
April 1992
Status: PROPOSED STANDARD
Autor: B. Stewart
RFC1317 Definitions of Managed Objects for RS-232-like Hardware Devices
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]
April 1992
Status: PROPOSED STANDARD
Autor: B. Stewart
RFC1318 Definitions of Managed Objects for Parallel-printer-like Hardware Devices
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]
April 1992
Status: PROPOSED STANDARD
Autor: B. Stewart
RFC1319 The MD2 Message-Digest Algorithm
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.
April 1992
Status: HISTORIC
Autor: B. Kaliski
RFC1320 The MD4 Message-Digest Algorithm
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.
April 1992
Status: HISTORIC
Autor: R. Rivest
RFC1321 The MD5 Message-Digest Algorithm
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.
April 1992
Status: INFORMATIONAL
Autor: R. Rivest
RFC1322 A Unified Approach to Inter-Domain Routing
This memo is an informational RFC which outlines one potential approach for inter-domain routing in future global internets. This memo provides information for the Internet community. It does not specify an Internet standard.
May 1992
Status: INFORMATIONAL
Autor: D. Estrin, Y. Rekhter, S. Hotz
RFC1323 TCP Extensions for High Performance
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. [STANDARDS-TRACK]
May 1992
Status: PROPOSED STANDARD
Autor: V. Jacobson, R. Braden, D. Borman
RFC1324 A Discussion on Computer Network Conferencing
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. This memo provides information for the Internet community. It does not specify an Internet standard.
May 1992
Status: INFORMATIONAL
Autor: D. Reed
RFC1325 FYI on Questions and Answers Answers to Commonly asked "New Internet User" Questions
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 an Internet standard.
May 1992
Status: INFORMATIONAL
Autor: G. Malkin, A. Marine
RFC1326 Mutual Encapsulation Considered Dangerous
This memo describes a packet explosion problem that can occur with mutual encapsulation of protocols (A encapsulates B and B encapsulates A). This memo provides information for the Internet community. It does not specify an Internet standard.
May 1992
Status: INFORMATIONAL
Autor: P. Tsuchiya
RFC1327 Mapping between X.400(1988) / ISO 10021 and RFC 822
This document specifies a mapping between two protocols. This specification should be used when this mapping is performed on the DARPA Internet or in the UK Academic Community. This specification may be modified in the light of implementation experience, but no substantial changes are expected. [STANDARDS-TRACK]
May 1992
Status: PROPOSED STANDARD
Autor: S. Hardcastle-Kille
RFC1328 X.400 1988 to 1984 downgrading
This document considers issues of downgrading from X.400(1988) to X.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. [STANDARDS-TRACK]
May 1992
Status: HISTORIC
Autor: S. Hardcastle-Kille
RFC1329 Thoughts on Address Resolution for Dual MAC FDDI Networks
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.
May 1992
Status: INFORMATIONAL
Autor: P. Kuehn
RFC1330 Recommendations for the Phase I Deployment of OSI Directory Services (X.500) and OSI Message Handling Services (X.400) within the ESNET Community
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.
May 1992
Status: INFORMATIONAL
Autor: ESCC X.500/X.400 Task Force, ESnet Site Coordinating Comittee (ESCC), Energy Sciences Network (ESnet)
RFC1331 The Point-to-Point Protocol (PPP) for the Transmission of Multi-protocol Datagrams over Point-to-Point Links
This document defines the PPP encapsulation scheme, together with the PPP 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. [STANDARDS-TRACK]
May 1992
Status: PROPOSED STANDARD
Autor: W. Simpson
RFC1332 The PPP Internet Protocol Control Protocol (IPCP)
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. [STANDARDS-TRACK]
May 1992
Status: PROPOSED STANDARD
Autor: G. McGregor
RFC1333 PPP Link Quality Monitoring
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. [STANDARDS-TRACK]
May 1992
Status: PROPOSED STANDARD
Autor: W. Simpson
RFC1334 PPP Authentication Protocols
This document defines two protocols for Authentication: the Password Authentication Protocol and the Challenge-Handshake Authentication Protocol. [STANDARDS-TRACK]
October 1992
Status: PROPOSED STANDARD
Autor: B. Lloyd, W. Simpson
RFC1335 A Two-Tier Address Structure for the Internet: A Solution to the Problem of Address Space Exhaustion
This RFC presents a solution to problem of address space exhaustion in the Internet. It proposes a two-tier address structure for the Internet. This is an "idea" paper and discussion is strongly encouraged. This memo provides information for the Internet community. It does not specify an Internet standard.
May 1992
Status: INFORMATIONAL
Autor: Z. Wang, J. Crowcroft
RFC1336 Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members
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 any standard.
May 1992
Status: INFORMATIONAL
Autor: G. Malkin
RFC1337 TIME-WAIT Assassination Hazards in TCP
This note describes some theoretically-possible failure modes for TCP connections and discusses possible remedies. In particular, one very simple fix is identified. This memo provides information for the Internet community. It does not specify an Internet standard.
May 1992
Status: INFORMATIONAL
Autor: R. Braden
RFC1338 Supernetting: an Address Assignment and Aggregation Strategy
This memo discusses strategies for address assignment of the existing IP 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. This memo provides information for the Internet community. It does not specify an Internet standard.
June 1992
Status: INFORMATIONAL
Autor: V. Fuller, T. Li, J. Yu, K. Varadhan
RFC1339 Remote Mail Checking Protocol
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. This memo defines an Experimental Protocol for the Internet community.
June 1992
Status: EXPERIMENTAL
Autor: S. Dorner, P. Resnick
RFC1340 Assigned Numbers
This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This memo is a status report on the parameters (i.e., numbers and keywords) used in protocols in the Internet community.
July 1992
Status: HISTORIC
Autor: J. Reynolds, J. Postel
RFC1341 MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies
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]
June 1992
Status: PROPOSED STANDARD
Autor: N. Borenstein, N. Freed
RFC1342 Representation of Non-ASCII Text in Internet Message Headers
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 RFC 822 message headers. [STANDARDS-TRACK]
June 1992
Status: PROPOSED STANDARD
Autor: K. Moore
RFC1343 A User Agent Configuration Mechanism for Multimedia Mail Format Information
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.
June 1992
Status: INFORMATIONAL
Autor: N. Borenstein
RFC1344 Implications of MIME for Internet Mail Gateways
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.
June 1992
Status: INFORMATIONAL
Autor: N. Borenstein
RFC1345 Character Mnemonics and Character Sets
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.
June 1992
Status: INFORMATIONAL
Autor: K. Simonsen
RFC1346 Resource Allocation, Control, and Accounting for the Use of Network Resources
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.
June 1992
Status: INFORMATIONAL
Autor: P. Jones
RFC1347 TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing
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.
June 1992
Status: INFORMATIONAL
Autor: R. Callon
RFC1348 DNS NSAP RRs
This RFC defines the format of two new Resource Records (RRs) for the Domain Name System (DNS), and reserves corresponding DNS type mnemonic and numerical codes. This memo defines an Experimental Protocol for the Internet community.
July 1992
Status: EXPERIMENTAL
Autor: B. Manning
RFC1349 Type of Service in the Internet Protocol Suite
This memo changes and clarifies some aspects of the semantics of the Type of Service octet in the Internet Protocol (IP) header. [STANDARDS-TRACK]
July 1992
Status: PROPOSED STANDARD
Autor: P. Almquist
RFC1350 The TFTP Protocol (Revision 2)
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]
July 1992
Status: STANDARD
Autor: K. Sollins
RFC1351 SNMP Administrative Model
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]
July 1992
Status: HISTORIC
Autor: J. Davin, J. Galvin, K. McCloghrie
RFC1352 SNMP Security Protocols
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]
July 1992
Status: HISTORIC
Autor: J. Galvin, K. McCloghrie, J. Davin
RFC1353 Definitions of Managed Objects for Administration of SNMP Parties
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 Standard SMI [1]. [STANDARDS-TRACK]
July 1992
Status: HISTORIC
Autor: K. McCloghrie, J. Davin, J. Galvin
RFC1354 IP Forwarding Table MIB
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 IP Internet. [STANDARDS-TRACK]
July 1992
Status: PROPOSED STANDARD
Autor: F. Baker
RFC1355 Privacy and Accuracy Issues in Network Information Center Databases
This document provides a set of guidelines for the administration and operation of public Network Information Center (NIC) databases. This memo provides information for the Internet community. It does not specify an Internet standard.
August 1992
Status: INFORMATIONAL
Autor: J. Curran, A. Marine
RFC1356 Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode
This document specifies the encapsulation of IP and other network layer protocols over X.25 networks, in accordance and alignment with ISO/IEC and CCITT standards. It is a replacement for RFC 877, "A Standard for the Transmission of IP Datagrams Over Public Data Networks" [1]. [STANDARDS-TRACK]
August 1992
Status: DRAFT STANDARD
Autor: A. Malis, D. Robinson, R. Ullmann
RFC1357 A Format for E-mailing Bibliographic Records
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). This memo provides information for the Internet community. It does not specify an Internet standard.
July 1992
Status: INFORMATIONAL
Autor: D. Cohen
RFC1358 Charter of the Internet Architecture Board (IAB)
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.
August 1992
Status: INFORMATIONAL
Autor: L. Chapin
RFC1359 Connecting to the Internet - What Connecting Institutions Should Anticipate
This FYI RFC outlines the major issues an institution should consider in the decision and implementation of a campus connection to the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
August 1992
Status: INFORMATIONAL
Autor: ACM SIGUCCS
RFC1360 IAB Official Protocol Standards
September 1992
Status: HISTORIC
Autor: J. Postel
RFC1361 Simple Network Time Protocol (SNTP)
This memorandum describes the Simple Network Time Protocol (SNTP), which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. This memorandum does not obsolete or update any RFC. This memo provides information for the Internet community. It does not specify an Internet standard. Discussion of the standardization process and the RFC document series is presented first, followed by an explanation of the terms. Sections 6.2 - 6.9 contain the lists of protocols in each stage of standardization. Finally come pointers to references and contacts for further information. [STANDARDS-TRACK]
August 1992
Status: INFORMATIONAL
Autor: D. Mills
RFC1362 Novell IPX over Various WAN Media (IPXWAN)
This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocol Novell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This memo provides information for the Internet community. It does not specify an Internet standard.
September 1992
Status: INFORMATIONAL
Autor: M. Allen
RFC1363 A Proposed Flow Specification
September 1992
Status: INFORMATIONAL
Autor: C. Partridge
RFC1364 BGP OSPF Interaction
September 1992
Status: PROPOSED STANDARD
Autor: K. Varadhan
RFC1365 An IP Address Extension Proposal
September 1992
Status: INFORMATIONAL
Autor: K. Siyan
RFC1366 Guidelines for Management of IP Address Space
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. This memo provides information for the Internet community. It does not specify an Internet standard. This RFC suggests an extension to the IP protocol to solve the shortage of IP address problem, and requests discussion and suggestions for improvements. This memo provides information for the Internet community. It does not specify an Internet standard. This memo defines the various criteria to be used when designing Autonomous System Border Routers (ASBR) that will run BGP with other ASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK] 1363 Partridge Spt 92 A Proposed Flow Specification 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). This memo provides information for the Internet community. It does not specify an Internet standard.
October 1992
Status: INFORMATIONAL
Autor: E. Gerich
RFC1367 Schedule for IP Address Space Management Guidelines
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.
October 1992
Status: INFORMATIONAL
Autor: C. Topolcic
RFC1368 Definition of Managed Objects for IEEE 802.3 Repeater Devices
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 10 Mb/second baseband repeaters, sometimes referred to as "hubs". [STANDARDS-TRACK]
October 1992
Status: PROPOSED STANDARD
Autor: D. McMaster, K. McCloghrie
RFC1369 Implementation Notes and Experience for the Internet Ethernet MIB
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.
October 1992
Status: INFORMATIONAL
Autor: F. Kastenholz
RFC1370 Applicability Statement for OSPF
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]
October 1992
Status: HISTORIC
Autor: Internet Architecture Board, L. Chapin
RFC1371 Choosing a Common IGP for the IP Internet
This memo presents motivation, rationale and other surrounding background information leading to the IESG's recommendation to the IAB for a single "common IGP" for the IP portions of the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
October 1992
Status: INFORMATIONAL
Autor: P. Gross
RFC1372 Telnet Remote Flow Control Option
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]
October 1992
Status: PROPOSED STANDARD
Autor: C. Hedrick, D. Borman
RFC1373 Portable DUAs
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.
October 1992
Status: INFORMATIONAL
Autor: T. Tignor
RFC1374 IP and ARP on HIPPI
The ANSI X3T9.3 committee has drafted a proposal for the encapsulation of IEEE 802.2 LLC PDUs and, by implication, IP on HIPPI. 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. This memo is intended to become an Internet Standard. [STANDARDS-TRACK]
October 1992
Status: PROPOSED STANDARD
Autor: J. Renwick, A. Nicholson
RFC1375 Suggestion for New Classes of IP Addresses
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. This memo provides information for the Internet community. It does not specify an Internet standard.
October 1992
Status: INFORMATIONAL
Autor: P. Robinson
RFC1376 The PPP DECnet Phase IV Control Protocol (DNCP)
This document defines the NCP for establishing and configuring Digital'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.). [STANDARDS-TRACK]
November 1992
Status: PROPOSED STANDARD
Autor: S. Senum
RFC1377 The PPP OSI Network Layer Control Protocol (OSINLCP)
This document defines the NCP for establishing and configuring OSI Network Layer Protocols. [STANDARDS-TRACK]
November 1992
Status: PROPOSED STANDARD
Autor: D. Katz
RFC1378 The PPP AppleTalk Control Protocol (ATCP)
This document defines the NCP for establishing and configuring the AppleTalk Protocol [3] over PPP. [STANDARDS-TRACK]
November 1992
Status: HISTORIC
Autor: B. Parker
RFC1379 Extending TCP for Transactions -- Concepts
This memo discusses extension of TCP to provide transaction-oriented service, without altering its virtual-circuit operation. This memo provides information for the Internet community. It does not specify an Internet standard.
November 1992
Status: HISTORIC
Autor: R. Braden
RFC1380 IESG Deliberations on Routing and Addressing
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 Internet Engineering Task Force (IETF). This memo provides information for the Internet community. It does not specify an Internet standard.
November 1992
Status: INFORMATIONAL
Autor: P. Gross, P. Almquist
RFC1381 SNMP MIB Extension for X.25 LAPB
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 of X.25, LAPB. [STANDARDS-TRACK]
November 1992
Status: PROPOSED STANDARD
Autor: D. Throop, F. Baker
RFC1382 SNMP MIB Extension for the X.25 Packet Layer
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. [STANDARDS-TRACK]
November 1992
Status: PROPOSED STANDARD
Autor: D. Throop
RFC1383 An Experiment in DNS Based IP Routing
Potential solutions to the routing explosion. This memo defines an Experimental Protocol for the Internet community.
December 1992
Status: EXPERIMENTAL
Autor: C. Huitema
RFC1384 Naming Guidelines for Directory Pilots
This document defines a number of naming guidelines. Alignment to these guidelines is recommended for directory pilots. This memo provides information for the Internet community. It does not specify an Internet standard.
January 1993
Status: INFORMATIONAL
Autor: P. Barker, S.E. Hardcastle-Kille
RFC1385 EIP: The Extended Internet Protocol
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.
November 1992
Status: INFORMATIONAL
Autor: Z. Wang
RFC1386 The US Domain
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.
December 1992
Status: INFORMATIONAL
Autor: A. Cooper, J. Postel
RFC1387 RIP Version 2 Protocol Analysis
As required by Routing Protocol Criteria (RFC 1264), this report documents the key features of the RIP-2 protocol and the current implementation experience. This memo provides information for the Internet community. It does not specify an Internet standard.
January 1993
Status: INFORMATIONAL
Autor: G. Malkin
RFC1388 RIP Version 2 Carrying Additional Information
This document specifies an extension of the Routing Information Protocol (RIP), as defined in [STANDARDS-TRACK]
January 1993
Status: PROPOSED STANDARD
Autor: G. Malkin
RFC1389 RIP Version 2 MIB Extensions
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. [STANDARDS-TRACK]
January 1993
Status: PROPOSED STANDARD
Autor: G. Malkin, F. Baker
RFC1390 Transmission of IP and ARP over FDDI Networks
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. [STANDARDS-TRACK]
January 1993
Status: STANDARD
Autor: D. Katz
RFC1391 The Tao of the IETF: A Guide for New Attendees of the Internet Engineering Task Force
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 memo provides information for the Internet community. It does not specify an Internet standard.
January 1993
Status: INFORMATIONAL
Autor: G. Malkin
RFC1392 Internet Users' Glossary
There are many networking glossaries in existence. This glossary concentrates on terms which are specific to the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
January 1993
Status: INFORMATIONAL
Autor: G. Malkin, T. LaQuey Parker
RFC1393 Traceroute Using an IP Option
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. This memo defines an Experimental Protocol for the Internet community.
January 1993
Status: EXPERIMENTAL
Autor: G. Malkin
RFC1394 Relationship of Telex Answerback Codes to Internet Domains
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 memo provides information for the Internet community. It does not specify an Internet standard.
January 1993
Status: INFORMATIONAL
Autor: P. Robinson
RFC1395 BOOTP Vendor Information Extensions
This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo. This memo will be updated as additional tags are defined. This edition introduces Tag 14 for Merit Dump File, Tag 15 for Domain Name, Tag 16 for Swap Server and Tag 17 for Root Path. This memo is a status report on the vendor information extensions used int the Bootstrap Protocol (BOOTP).
January 1993
Status: DRAFT STANDARD
Autor: J. Reynolds
RFC1396 The Process for Organization of Internet Standards Working Group (POISED)
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. This memo provides information for the Internet community. It does not specify an Internet standard.
January 1993
Status: INFORMATIONAL
Autor: S. Crocker
RFC1397 Default Route Advertisement In BGP2 and BGP3 Version of The Border Gateway Protocol
This document speficies the recommendation of the BGP Working Group on default route advertisement support in BGP2 [1] and BGP3 [2] versions of the Border Gateway Protocol. [STANDARDS-TRACK]
January 1993
Status: HISTORIC
Autor: D. Haskin
RFC1398 Definitions of Managed Objects for the Ethernet-Like Interface Types
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 ehternet-like objects. [STANDARDS-TRACK]
January 1993
Status: DRAFT STANDARD
Autor: F. Kastenholz
RFC1399 Summary of 1300-1399
January 1997
Status: INFORMATIONAL
Autor: J. Elliott
RFC1400 Transition and Modernization of the Internet Registration Service
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.
March 1993
Status: INFORMATIONAL
Autor: S. Williamson
RFC1401 Correspondence between the IAB and DISA on the use of DNS
This memo reproduces three letters exchanged between the Internet Activities 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". This memo provides information for the Internet community. It does not specify an Internet standard.
January 1993
Status: INFORMATIONAL
Autor: Internet Architecture Board
RFC1402 There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places
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. This RFC provides information for the Internet community. It does not specify an Internet standard.
January 1993
Status: INFORMATIONAL
Autor: J. Martin
RFC1403 BGP OSPF Interaction
This memo defines the various criteria to be used when designing an Autonomous System Border Routers (ASBR) that will run BGP with other ASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK]
January 1993
Status: HISTORIC
Autor: K. Varadhan
RFC1404 A Model for Common Operational Statistics
This memo describes a model for operational statistics in the Internet. It gives recommendations for metrics, measurements, polling periods, storage formats and presentation formats. This memo provides information for the Internet community. It does not specify an Internet standard.
January 1993
Status: INFORMATIONAL
Autor: B. Stockman
RFC1405 Mapping between X.400(1984/1988) and Mail-11 (DECnet mail)
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 the Mail-11 (also known as DECnet mail) protocol. This memo defines an Experimental Protocol for the Internet community.
January 1993
Status: EXPERIMENTAL
Autor: C. Allocchio
RFC1406 Definitions of Managed Objects for the DS1 and E1 Interface Types
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. [STANDARDS-TRACK]
January 1993
Status: PROPOSED STANDARD
Autor: F. Baker, J. Watt
RFC1407 Definitions of Managed Objects for the DS3/E3 Interface Type
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 E3 Interfaces. [STANDARDS-TRACK]
January 1993
Status: PROPOSED STANDARD
Autor: T. Cox, K. Tesink
RFC1408 Telnet Environment Option
This document specifies a mechanism for passing environment information between a telnet client and server. [STANDARDS-TRACK]
January 1993
Status: HISTORIC
Autor: D. Borman
RFC1409 Telnet Authentication Option
This memo defines an Experimental Protocol for the Internet community.
January 1993
Status: EXPERIMENTAL
Autor: D. Borman
RFC1410 IAB Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB).
March 1993
Status: HISTORIC
Autor: J. Postel
RFC1411 Telnet Authentication: Kerberos Version 4
This memo defines an Experimental Protocol for the Internet community.
January 1993
Status: EXPERIMENTAL
Autor: D. Borman
RFC1412 Telnet Authentication: SPX
This memo defines an Experimental Protocol for the Internet community.
January 1993
Status: EXPERIMENTAL
Autor: K. Alagappan
RFC1413 Identification Protocol
The Identification Protocol was formerly called the Authentication Server Protocol. It has been renamed to better reflect its function. [STANDARDS-TRACK]
February 1993
Status: PROPOSED STANDARD
Autor: M. St. Johns
RFC1414 Identification MIB
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]. [STANDARDS-TRACK]
February 1993
Status: HISTORIC
Autor: M. St. Johns, M. Rose
RFC1415 FTP-FTAM Gateway Specification
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. [STANDARDS-TRACK]
January 1993
Status: HISTORIC
Autor: J. Mindel, R. Slaski
RFC1416 Telnet Authentication Option
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.
February 1993
Status: EXPERIMENTAL
Autor: D. Borman
RFC1417 NADF Standing Documents: A Brief Overview
The purpose of this document is to provide a brief overview of the NADF's Standing Document series. This memo provides information for the Internet community. It does not specify an Internet standard.
February 1993
Status: INFORMATIONAL
Autor: The North American Directory Forum
RFC1418 SNMP over OSI
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]
March 1993
Status: HISTORIC
Autor: M. Rose
RFC1419 SNMP over AppleTalk
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]
March 1993
Status: HISTORIC
Autor: G. Minshall, M. Ritter
RFC1420 SNMP over IPX
This document defines a convention for encapsulating Simple Network Management Protocol (SNMP) [1] packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol [2]. [STANDARDS-TRACK]
March 1993
Status: PROPOSED STANDARD
Autor: S. Bostock
RFC1421 Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures
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]
February 1993
Status: HISTORIC
Autor: J. Linn
RFC1422 Privacy Enhancement for Internet Electronic Mail: Part II: Certificate-Based Key Management
This is one of a series of documents defining privacy enhancement mechanisms for electronic mail transferred using Internet mail protocols. [STANDARDS-TRACK]
February 1993
Status: HISTORIC
Autor: S. Kent
RFC1423 Privacy Enhancement for Internet Electronic Mail: Part III: Algorithms, Modes, and Identifiers
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. [STANDARDS-TRACK]
February 1993
Status: HISTORIC
Autor: D. Balenson
RFC1424 Privacy Enhancement for Internet Electronic Mail: Part IV: Key Certification and Related Services
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]
February 1993
Status: HISTORIC
Autor: B. Kaliski
RFC1425 SMTP Service Extensions
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]
February 1993
Status: PROPOSED STANDARD
Autor: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker
RFC1426 SMTP Service Extension for 8bit-MIMEtransport
This memo defines an extension to the SMTP service whereby an SMTP content body containing octets outside of the US ASCII octet range (hex
February 1993
Status: PROPOSED STANDARD
Autor: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker
RFC1427 SMTP Service Extension for Message Size Declaration
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]
February 1993
Status: PROPOSED STANDARD
Autor: J. Klensin, N. Freed, K. Moore
RFC1428 Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIME
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. This RFC provides information for the Internet community. It does not specify an Internet standard.
February 1993
Status: INFORMATIONAL
Autor: G. Vaudreuil
RFC1429 Listserv Distribute Protocol
This memo specifies a subset of the distribution protocol used by the BITNET LISTSERV to deliver mail messages to large amounts of recipients. This memo provides information for the Internet community. It does not specify an Internet standard.
February 1993
Status: INFORMATIONAL
Autor: E. Thomas
RFC1430 A Strategic Plan for Deploying an Internet X.500 Directory Service
This document describes an overall strategy for deploying a Directory Service on the Internet, based on the OSI X.500 Directory Service. This memo provides information for the Internet community. It does not specify an Internet standard.
February 1993
Status: INFORMATIONAL
Autor: S. Hardcastle-Kille, E. Huizer, V. Cerf, R. Hobby, S. Kent
RFC1431 DUA Metrics (OSI-DS 33 (v2))
This document defines a set of criteria by which a DUA implementation, or more precisely a Directory user interface, may be judged. This memo provides information for the Internet community. It does not specify an Internet standard.
February 1993
Status: INFORMATIONAL
Autor: P. Barker
RFC1432 Recent Internet Books
Here is a list of books related to using the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
March 1993
Status: INFORMATIONAL
Autor: J. Quarterman
RFC1433 Directed ARP
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. This memo defines an Experimental Protocol for the Internet community.
March 1993
Status: EXPERIMENTAL
Autor: J. Garrett, J. Hagan, J. Wong
RFC1434 Data Link Switching: Switch-to-Switch Protocol
This RFC describes IBM's support of Data Link Switching over TCP/IP. This memo provides information for the Internet community. It does not specify an Internet standard.
March 1993
Status: INFORMATIONAL
Autor: R. Dixon, D. Kushi
RFC1435 IESG Advice from Experience with Path MTU Discovery
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 MTU Discovery. This memo provides information for the Internet community. It does not specify an Internet standard.
March 1993
Status: INFORMATIONAL
Autor: S. Knowles
RFC1436 The Internet Gopher Protocol (a distributed document search and retrieval protocol)
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 memo provides information for the Internet community. It does not specify an Internet standard.
March 1993
Status: INFORMATIONAL
Autor: F. Anklesaria, M. McCahill, P. Lindner, D. Johnson, D. Torrey, B. Albert
RFC1437 The Extension of MIME Content-Types to a New Medium
This document defines one particular type of MIME data, the matter- transport/sentient-life-form type. This memo provides information for the Internet community. It does not specify an Internet standard.
April 1993
Status: INFORMATIONAL
Autor: N. Borenstein, M. Linimon
RFC1438 Internet Engineering Task Force Statements Of Boredom (SOBs)
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.
April 1993
Status: INFORMATIONAL
Autor: A. Lyman Chapin, C. Huitema
RFC1439 The Uniqueness of Unique Identifiers
This RFC provides information that may be useful when selecting a method to use for assigning unique identifiers to people. This memo provides information for the Internet community. It does not specify an Internet standard.
March 1993
Status: INFORMATIONAL
Autor: C. Finseth
RFC1440 SIFT/UFT: Sender-Initiated/Unsolicited File Transfer
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.
July 1993
Status: EXPERIMENTAL
Autor: R. Troth
RFC1441 Introduction to version 2 of the Internet-standard Network Management Framework
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]
April 1993
Status: HISTORIC
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1442 Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)
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]
April 1993
Status: PROPOSED STANDARD
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1443 Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK]
April 1993
Status: PROPOSED STANDARD
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1444 Conformance Statements for version 2 of the Simple Network Management Protocol (SNMPv2)
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]
April 1993
Status: PROPOSED STANDARD
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1445 Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2)
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]
April 1993
Status: HISTORIC
Autor: J. Galvin, K. McCloghrie
RFC1446 Security Protocols for version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document, Security Protocols for SNMPv2, to define one such authentication and one such privacy protocol. [STANDARDS-TRACK]
April 1993
Status: HISTORIC
Autor: J. Galvin, K. McCloghrie
RFC1447 Party MIB for version 2 of the Simple Network Management Protocol (SNMPv2)
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]
April 1993
Status: HISTORIC
Autor: K. McCloghrie, J. Galvin
RFC1448 Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)
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]
April 1993
Status: PROPOSED STANDARD
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1449 Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document to define how the SNMPv2 maps onto an initial set of transport domains. [STANDARDS-TRACK]
April 1993
Status: PROPOSED STANDARD
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1450 Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity. [STANDARDS-TRACK]
April 1993
Status: PROPOSED STANDARD
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1451 Manager-to-Manager Management Information Base
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]
April 1993
Status: HISTORIC
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1452 Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework
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]
April 1993
Status: PROPOSED STANDARD
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1453 A Comment on Packet Video Remote Conferencing and the Transport/Network Layers
This RFC is a vehicle to inform the Internet community about XTP as it benefits from past Internet activity and targets general-purpose applications and multimedia applications with the emerging ATM networks in mind. This memo provides information for the Internet community. It does not specify an Internet standard.
April 1993
Status: INFORMATIONAL
Autor: W. Chimiak
RFC1454 Comparison of Proposals for Next Version of IP
This is a slightly edited reprint of RARE Technical Report (RTC(93)004). This memo provides information for the Internet community. It does not specify an Internet standard.
May 1993
Status: INFORMATIONAL
Autor: T. Dixon
RFC1455 Physical Link Security Type of Service
This RFC documents an experimental protocol providing a Type of Service (TOS) to request maximum physical link security. This is an addition to the types of service enumerated in RFC 1349: Type of Service in the Internet Protocol Suite. This memo defines an Experimental Protocol for the Internet community.
May 1993
Status: EXPERIMENTAL
Autor: D. Eastlake 3rd
RFC1456 Conventions for Encoding the Vietnamese Language VISCII: VIetnamese Standard Code for Information Interchange VIQR: VIetnamese Quoted-Readable Specification
This document provides information to the Internet community on the currently used conventions for encoding Vietnamese characters into 7-bit US ASCII and in an 8-bit form. This memo provides information for the Internet community. It does not specify an Internet standard.
May 1993
Status: INFORMATIONAL
Autor: Vietnamese Standardization Working Group
RFC1457 Security Label Framework for the Internet
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.
May 1993
Status: INFORMATIONAL
Autor: R. Housley
RFC1458 Requirements for Multicast Protocols
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.
May 1993
Status: INFORMATIONAL
Autor: R. Braudes, S. Zabele
RFC1459 Internet Relay Chat Protocol
The IRC protocol is a text-based protocol, with the simplest client being any socket program capable of connecting to the server. This memo defines an Experimental Protocol for the Internet community.
May 1993
Status: EXPERIMENTAL
Autor: J. Oikarinen, D. Reed
RFC1460 Post Office Protocol - Version 3
This memo is a revision to RFC 1225, a Draft Standard. [STANDARDS-TRACK]
June 1993
Status: DRAFT STANDARD
Autor: M. Rose
RFC1461 SNMP MIB extension for Multiprotocol Interconnect over X.25
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 Multiprotocol Interconnect (including IP) traffic carried over X.25. [STANDARDS-TRACK]
May 1993
Status: HISTORIC
Autor: D. Throop
RFC1462 FYI on "What is the Internet?"
This FYI RFC answers the question, "What is the Internet?" and is produced by the User Services Working Group of the Internet Engineering Task Force (IETF). This memo provides information for the Internet community. It does not specify an Internet standard.
May 1993
Status: INFORMATIONAL
Autor: E. Krol, E. Hoffman
RFC1463 FYI on Introducing the Internet-- A Short Bibliography of Introductory Internetworking Readings
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 memo provides information for the Internet community. It does not specify an Internet standard.
May 1993
Status: INFORMATIONAL
Autor: E. Hoffman, L. Jackson
RFC1464 Using the Domain Name System To Store Arbitrary String Attributes
This paper describes a simple means to associate arbitrary string information (ASCII text) with attributes that have not been defined by the DNS. This memo defines an Experimental Protocol for the Internet community.
May 1993
Status: EXPERIMENTAL
Autor: R. Rosenbaum
RFC1465 Routing Coordination for X.400 MHS Services Within a Multi Protocol / Multi Network Environment Table Format V3 for Static Routing
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.
May 1993
Status: EXPERIMENTAL
Autor: D. Eppenberger
RFC1466 Guidelines for Management of IP Address Space
This document proposes a plan which will forward the implementation of RFC 1174 and which defines the allocation and assignment of the network number space. This memo provides information for the Internet community. It does not specify an Internet standard.
May 1993
Status: INFORMATIONAL
Autor: E. Gerich
RFC1467 Status of CIDR Deployment in the Internet
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. This memo provides information for the Internet community. It does not specify an Internet standard.
August 1993
Status: HISTORIC
Autor: C. Topolcic
RFC1468 Japanese Character Encoding for Internet Messages
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.
June 1993
Status: INFORMATIONAL
Autor: J. Murai, M. Crispin, E. van der Poel
RFC1469 IP Multicast over Token-Ring Local Area Networks
This document specifies a method for the transmission of IP multicast datagrams over Token-Ring Local Area Networks. [STANDARDS-TRACK]
June 1993
Status: HISTORIC
Autor: T. Pusateri
RFC1470 FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices
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. This memo provides information for the Internet community. It does not specify an Internet standard.
June 1993
Status: INFORMATIONAL
Autor: R. Enger, J. Reynolds
RFC1471 The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol
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 Link Control Protocol and Link Quality Monitoring on subnetwork interfaces that use the family of Point-to-Point Protocols [8, 9, 10, 11, & 12]. [STANDARDS-TRACK]
June 1993
Status: PROPOSED STANDARD
Autor: F. Kastenholz
RFC1472 The Definitions of Managed Objects for the Security Protocols of the Point-to-Point Protocol
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 Security Protocols on subnetwork interfaces using the family of Point-to-Point Protocols [8, 9, 10, 11, & 12]. [STANDARDS-TRACK]
June 1993
Status: PROPOSED STANDARD
Autor: F. Kastenholz
RFC1473 The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol
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 IP Network Control Protocol on subnetwork interfaces using the family of Point-to-Point Protocols [8, 9, 10, 11, & 12]. [STANDARDS-TRACK]
June 1993
Status: PROPOSED STANDARD
Autor: F. Kastenholz
RFC1474 The Definitions of Managed Objects for the Bridge Network Control Protocol of the Point-to-Point Protocol
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. [STANDARDS-TRACK]
June 1993
Status: HISTORIC
Autor: F. Kastenholz
RFC1475 TP/IX: The Next Internet
This memo presents the specification for version 7 of the Internet Protocol, as well as version 7 of the TCP and the user datagram protocol. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.
June 1993
Status: EXPERIMENTAL
Autor: R. Ullmann
RFC1476 RAP: Internet Route Access Protocol
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. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.
June 1993
Status: EXPERIMENTAL
Autor: R. Ullmann
RFC1477 IDPR as a Proposed Standard
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.
July 1993
Status: INFORMATIONAL
Autor: M. Steenstrup
RFC1478 An Architecture for Inter-Domain Policy Routing
We present an architecture for inter-domain policy routing (IDPR). [STANDARDS-TRACK]
June 1993
Status: HISTORIC
Autor: M. Steenstrup
RFC1479 Inter-Domain Policy Routing Protocol Specification: Version 1
We present the set of protocols and procedures that constitute Inter- Domain Policy Routing (IDPR). [STANDARDS-TRACK]
July 1993
Status: HISTORIC
Autor: M. Steenstrup
RFC1480 The US Domain
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.
June 1993
Status: INFORMATIONAL
Autor: A. Cooper, J. Postel
RFC1481 IAB Recommendation for an Intermediate Strategy to Address the Issue of Scaling
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.
July 1993
Status: HISTORIC
Autor: C. Huitema
RFC1482 Aggregation Support in the NSFNET Policy-Based Routing Database
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 Network Service. This memo provides information for the Internet community. It does not specify an Internet standard.
June 1993
Status: HISTORIC
Autor: M. Knopper, S. Richardson
RFC1483 Multiprotocol Encapsulation over ATM Adaptation Layer 5
This memo describes two encapsulations methods for carrying network interconnect traffic over ATM AAL5. [STANDARDS-TRACK]
July 1993
Status: PROPOSED STANDARD
Autor: Juha Heinanen
RFC1484 Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2))
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 memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.
July 1993
Status: HISTORIC
Autor: S. Hardcastle-Kille
RFC1485 A String Representation of Distinguished Names (OSI-DS 23 (v5))
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. [STANDARDS-TRACK]
July 1993
Status: HISTORIC
Autor: S. Hardcastle-Kille
RFC1486 An Experiment in Remote Printing
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.
July 1993
Status: EXPERIMENTAL
Autor: M. Rose, C. Malamud
RFC1487 X.500 Lightweight Directory Access Protocol
The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). [STANDARDS-TRACK]
July 1993
Status: HISTORIC
Autor: W. Yeong, T. Howes, S. Kille
RFC1488 The X.500 String Representation of Standard Attribute Syntaxes
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]. [STANDARDS-TRACK]
July 1993
Status: PROPOSED STANDARD
Autor: T. Howes, S. Kille, W. Yeong, C. Robbins
RFC1489 Registration of a Cyrillic Character Set
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.
July 1993
Status: INFORMATIONAL
Autor: A. Chernov
RFC1490 Multiprotocol Interconnect over Frame Relay
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. [STANDARDS-TRACK]
July 1993
Status: DRAFT STANDARD
Autor: T. Bradley, C. Brown, A. Malis
RFC1491 A Survey of Advanced Usages of X.500
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 Integrated Directory Services Working Group of the Application and User Services Areas of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard.
July 1993
Status: INFORMATIONAL
Autor: C. Weider, R. Wright
RFC1492 An Access Control Protocol, Sometimes Called TACACS
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.
July 1993
Status: INFORMATIONAL
Autor: C. Finseth
RFC1493 Definitions of Managed Objects for Bridges
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. [STANDARDS-TRACK]
July 1993
Status: DRAFT STANDARD
Autor: E. Decker, P. Langille, A. Rijsinghani, K. McCloghrie
RFC1494 Equivalences between 1988 X.400 and RFC-822 Message Bodies
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]
August 1993
Status: HISTORIC
Autor: H. Alvestrand, S. Thompson
RFC1495 Mapping between X.400 and RFC-822 Message Bodies
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]
August 1993
Status: PROPOSED STANDARD
Autor: H. Alvestrand, S. Kille, R. Miles, M. Rose, S. Thompson
RFC1496 Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages
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]
August 1993
Status: HISTORIC
Autor: H. Alvestrand, J. Romaguera, K. Jordan
RFC1497 BOOTP Vendor Information Extensions
This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo. This memo is a status report on the vendor information extensions used in the Bootstrap Protocol (BOOTP).
August 1993
Status: DRAFT STANDARD
Autor: J. Reynolds
RFC1498 On the Naming and Binding of Network Destinations
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. This memo provides information for the Internet community. It does not specify an Internet standard.
August 1993
Status: INFORMATIONAL
Autor: J. Saltzer
RFC1499 Summary of 1400-1499
January 1997
Status: INFORMATIONAL
Autor: J. Elliott
RFC1500 Internet Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). [STANDARDS-TRACK]
August 1993
Status: HISTORIC
Autor: J. Postel
RFC1501 OS/2 User Group
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.
August 1993
Status: INFORMATIONAL
Autor: E. Brunsen
RFC1502 X.400 Use of Extended Character Sets
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]
August 1993
Status: HISTORIC
Autor: H. Alvestrand
RFC1503 Algorithms for Automating Administration in SNMPv2 Managers
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.
August 1993
Status: INFORMATIONAL
Autor: K. McCloghrie, M. Rose
RFC1504 Appletalk Update-Based Routing Protocol: Enhanced Appletalk Routing
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.
August 1993
Status: INFORMATIONAL
Autor: A. Oppenheimer
RFC1505 Encoding Header Field for Internet Messages
This document expands upon the elective experimental Encoding header field which permits the mailing of multi-part, multi-structured messages. It replaces RFC 1154. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.
August 1993
Status: EXPERIMENTAL
Autor: A. Costanzo, D. Robinson, R. Ullmann
RFC1506 A Tutorial on Gatewaying between X.400 and Internet Mail
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.
August 1993
Status: INFORMATIONAL
Autor: J. Houttuin
RFC1507 DASS - Distributed Authentication Security Service
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.
September 1993
Status: EXPERIMENTAL
Autor: C. Kaufman
RFC1508 Generic Security Service Application Program Interface
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. [STANDARDS-TRACK]
September 1993
Status: PROPOSED STANDARD
Autor: J. Linn
RFC1509 Generic Security Service API : C-bindings
This document specifies C language bindings for the Generic Security Service Application Program Interface (GSS-API), which is described at a language-independent conceptual level in other documents. [STANDARDS-TRACK]
September 1993
Status: PROPOSED STANDARD
Autor: J. Wray
RFC1510 The Kerberos Network Authentication Service (V5)
This document gives an overview and specification of Version 5 of the protocol for the Kerberos network authentication system. [STANDARDS-TRACK]
September 1993
Status: PROPOSED STANDARD
Autor: J. Kohl, C. Neuman
RFC1511 Common Authentication Technology Overview
This memo provides information for the Internet community. It does not specify an Internet standard.
September 1993
Status: INFORMATIONAL
Autor: J. Linn
RFC1512 FDDI Management Information Base
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing devices which implement the FDDI based on the ANSI FDDI SMT 7.3 draft standard, which has been forwarded for publication by the X3T9.5 committee.
September 1993
Status: HISTORIC
Autor: J. Case, A. Rijsinghani
RFC1513 Token Ring Extensions to the Remote Network Monitoring MIB
This memo defines extensions to the Remote Network Monitoring MIB for managing 802.5 Token Ring networks. [STANDARDS-TRACK]
September 1993
Status: HISTORIC
Autor: S. Waldbusser
RFC1514 Host Resources MIB
This memo defines a MIB for use with managing host systems. [STANDARDS-TRACK]
September 1993
Status: PROPOSED STANDARD
Autor: P. Grillo, S. Waldbusser
RFC1515 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
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.3 Medium Attachment Units (MAUs). [STANDARDS-TRACK]
September 1993
Status: PROPOSED STANDARD
Autor: D. McMaster, K. McCloghrie, S. Roberts
RFC1516 Definitions of Managed Objects for IEEE 802.3 Repeater Devices
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 10 Mb/second baseband repeaters, sometimes referred to as "hubs." [STANDARDS-TRACK]
September 1993
Status: DRAFT STANDARD
Autor: D. McMaster, K. McCloghrie
RFC1517 Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR)
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]
September 1993
Status: HISTORIC
Autor: Internet Engineering Steering Group, R. Hinden
RFC1518 An Architecture for IP Address Allocation with CIDR
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]
September 1993
Status: HISTORIC
Autor: Y. Rekhter, T. Li
RFC1519 Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy
This memo discusses strategies for address assignment of the existing IP address space with a view to conserve the address space and stem the explosive growth of routing tables in default-route-free routers. [STANDARDS-TRACK]
September 1993
Status: PROPOSED STANDARD
Autor: V. Fuller, T. Li, J. Yu, K. Varadhan
RFC1520 Exchanging Routing Information Across Provider Boundaries in the CIDR Environment
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.
September 1993
Status: HISTORIC
Autor: Y. Rekhter, C. Topolcic
RFC1521 MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies
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. [STANDARDS-TRACK]
September 1993
Status: DRAFT STANDARD
Autor: N. Borenstein, N. Freed
RFC1522 MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text
This memo describes an extension to the message format defined in RFC 1521, to allow the representation of character sets other than ASCII 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.
September 1993
Status: DRAFT STANDARD
Autor: K. Moore
RFC1523 The text/enriched MIME Content-type
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. This memo provides information for the Internet community. It does not specify an Internet standard.
September 1993
Status: INFORMATIONAL
Autor: N. Borenstein
RFC1524 A User Agent Configuration Mechanism For Multimedia Mail Format Information
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.
September 1993
Status: INFORMATIONAL
Autor: N. Borenstein
RFC1525 Definitions of Managed Objects for Source Routing Bridges
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]
September 1993
Status: HISTORIC
Autor: E. Decker, K. McCloghrie, P. Langille, A. Rijsinghani
RFC1526 Assignment of System Identifiers for TUBA/CLNP Hosts
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. This memo provides information for the Internet community. It does not specify an Internet standard.
September 1993
Status: INFORMATIONAL
Autor: D. Piscitello
RFC1527 What Should We Plan Given the Dilemma of the Network?
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 for Congress to make? This memo is a shortened version of the suggested policy draft. This memo provides information for the Internet community. It does not specify an Internet standard.
September 1993
Status: INFORMATIONAL
Autor: G. Cook
RFC1528 Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures
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.
October 1993
Status: EXPERIMENTAL
Autor: C. Malamud, M. Rose
RFC1529 Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Administrative Policies
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.
October 1993
Status: INFORMATIONAL
Autor: C. Malamud, M. Rose
RFC1530 Principles of Operation for the TPC.INT Subdomain: General Principles and Policy
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. This memo provides information for the Internet community. It does not specify an Internet standard.
October 1993
Status: INFORMATIONAL
Autor: C. Malamud, M. Rose
RFC1531 Dynamic Host Configuration Protocol
The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network. [STANDARDS-TRACK]
October 1993
Status: PROPOSED STANDARD
Autor: R. Droms
RFC1532 Clarifications and Extensions for the Bootstrap Protocol
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. [STANDARDS-TRACK]
October 1993
Status: PROPOSED STANDARD
Autor: W. Wimer
RFC1533 DHCP Options and BOOTP Vendor Extensions
This document specifies the current set of DHCP options. [STANDARDS-TRACK]
October 1993
Status: PROPOSED STANDARD
Autor: S. Alexander, R. Droms
RFC1534 Interoperation Between DHCP and BOOTP
DHCP provides a superset of the functions provided by BOOTP. This document describes the interactions between DHCP and BOOTP network participants. [STANDARDS-TRACK]
October 1993
Status: DRAFT STANDARD
Autor: R. Droms
RFC1535 A Security Problem and Proposed Correction With Widely Deployed DNS Software
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. This document points out the flaw, a case in point, and a solution. This memo provides information for the Internet community. It does not specify an Internet standard.
October 1993
Status: INFORMATIONAL
Autor: E. Gavron
RFC1536 Common DNS Implementation Errors and Suggested Fixes
This memo describes common errors seen in DNS implementations and suggests some fixes. This memo provides information for the Internet community. It does not specify an Internet standard.
October 1993
Status: INFORMATIONAL
Autor: A. Kumar, J. Postel, C. Neuman, P. Danzig, S. Miller
RFC1537 Common DNS Data File Configuration Errors
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. This memo provides information for the Internet community. It does not specify an Internet standard.
October 1993
Status: INFORMATIONAL
Autor: P. Beertema
RFC1538 Advanced SNA/IP : A Simple SNA Transport Protocol
This RFC provides information for the Internet community about a method for establishing and maintaining SNA sessions over an IP internet. This memo provides information for the Internet community. It does not specify an Internet standard.
October 1993
Status: INFORMATIONAL
Autor: W. Behl, B. Sterling, W. Teskey
RFC1539 The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force
The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This memo provides information for the Internet community. It does not specify an Internet standard. [FYI 17]
October 1993
Status: INFORMATIONAL
Autor: G. Malkin
RFC1540 Internet Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). [STANDARDS-TRACK]
October 1993
Status: HISTORIC
Autor: J. Postel
RFC1541 Dynamic Host Configuration Protocol
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) adding the capability of automatic allocation of reusable network addresses and additional configuration options. [STANDARDS-TRACK]
October 1993
Status: PROPOSED STANDARD
Autor: R. Droms
RFC1542 Clarifications and Extensions for the Bootstrap Protocol
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. [STANDARDS-TRACK]
October 1993
Status: DRAFT STANDARD
Autor: W. Wimer
RFC1543 Instructions to RFC Authors
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.
October 1993
Status: INFORMATIONAL
Autor: J. Postel
RFC1544 The Content-MD5 Header Field
This memo defines the use of an optional header field, Content-MD5, which may be used as a message integrity check (MIC), to verify that the decoded data are the same data that were initially sent. [STANDARDS-TRACK]
November 1993
Status: PROPOSED STANDARD
Autor: M. Rose
RFC1545 FTP Operation Over Big Address Records (FOOBAR)
This RFC specifies a method for assigning long addresses in the HOST- PORT specification for the data port to be used in establishing a data connection for File Transfer Protocol, FTP (STD 9, RFC 959). This is a general solution, applicable for all "next generation" IP alternatives, and can also be extended to allow FTP operation over transport interfaces other than TCP. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind.
November 1993
Status: EXPERIMENTAL
Autor: D. Piscitello
RFC1546 Host Anycasting Service
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. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
November 1993
Status: INFORMATIONAL
Autor: C. Partridge, T. Mendez, W. Milliken
RFC1547 Requirements for an Internet Standard Point-to-Point Protocol
This document discusses the evaluation criteria for an Internet Standard Data Link Layer protocol to be used with point-to-point links. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1993
Status: INFORMATIONAL
Autor: D. Perkins
RFC1548 The Point-to-Point Protocol (PPP)
This document defines the PPP organization and methodology, and the PPP encapsulation, together with an extensible option negotiation mechanism which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. [STANDARDS-TRACK]
December 1993
Status: DRAFT STANDARD
Autor: W. Simpson
RFC1549 PPP in HDLC Framing
This document describes the use of HDLC for framing PPP encapsulated packets. [STANDARDS-TRACK]
December 1993
Status: DRAFT STANDARD
Autor: W. Simpson
RFC1550 IP: Next Generation (IPng) White Paper Solicitation
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.
December 1993
Status: INFORMATIONAL
Autor: S. Bradner, A. Mankin
RFC1551 Novell IPX Over Various WAN Media (IPXWAN)
This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocol Novell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1993
Status: INFORMATIONAL
Autor: M. Allen
RFC1552 The PPP Internetworking Packet Exchange Control Protocol (IPXCP)
This document defines the Network Control Protocol for establishing and configuring the IPX protocol over PPP. [STANDARDS-TRACK]
December 1993
Status: HISTORIC
Autor: W. Simpson
RFC1553 Compressing IPX Headers Over WAN Media (CIPX)
This document describes a method for compressing the headers of IPX datagrams (CIPX). [STANDARDS-TRACK]
December 1993
Status: HISTORIC
Autor: S. Mathur, M. Lewis
RFC1554 ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP
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.
December 1993
Status: INFORMATIONAL
Autor: M. Ohta, K. Handa
RFC1555 Hebrew Character Encoding for Internet Messages
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. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1993
Status: INFORMATIONAL
Autor: H. Nussbacher, Y. Bourvine
RFC1556 Handling of Bi-directional Texts in MIME
This document describes the format and syntax of the "direction" keyword to be used with bi-directional texts in MIME. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1993
Status: INFORMATIONAL
Autor: H. Nussbacher
RFC1557 Korean Character Encoding for Internet Messages
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.
December 1993
Status: INFORMATIONAL
Autor: U. Choi, K. Chon, H. Park
RFC1558 A String Representation of LDAP Search Filters
The Lightweight Directory Access Protocol (LDAP) 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. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1993
Status: INFORMATIONAL
Autor: T. Howes
RFC1559 DECnet Phase IV MIB Extensions
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]
December 1993
Status: DRAFT STANDARD
Autor: J. Saperia
RFC1560 The MultiProtocol Internet
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. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1993
Status: INFORMATIONAL
Autor: B. Leiner, Y. Rekhter
RFC1561 Use of ISO CLNP in TUBA Environments
This memo specifies a profile of the ISO/IEC 8473 Connectionless-mode Network Layer Protocol for use in conjunction with RFC 1347, TCP/UDP over Bigger Addresses. It describes the use of CLNP to provide the lower-level service expected by Transmission Control Protocol and User Datagram Protocol. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind.
December 1993
Status: EXPERIMENTAL
Autor: D. Piscitello
RFC1562 Naming Guidelines for the AARNet X.500 Directory Service
This document is an AARNet (Australian Academic and Research Network) Engineering Note (AEN-001). AARNet Engineering Notes are engineering documents of the AARNet Engineering Working Group, and record current or proposed operational practices related to the provision of Internetworking services within Australia, and AARNet in particular. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1993
Status: INFORMATIONAL
Autor: G. Michaelson, M. Prior
RFC1563 The text/enriched MIME Content-type
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. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
January 1994
Status: INFORMATIONAL
Autor: N. Borenstein
RFC1564 DSA Metrics (OSI-DS 34 (v3))
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. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
January 1994
Status: INFORMATIONAL
Autor: P. Barker, R. Hedberg
RFC1565 Network Services Monitoring MIB
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]
January 1994
Status: PROPOSED STANDARD
Autor: S. Kille, N. Freed
RFC1566 Mail Monitoring MIB
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]
January 1994
Status: PROPOSED STANDARD
Autor: S. Kille, N. Freed
RFC1567 X.500 Directory Monitoring MIB
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. [STANDARDS-TRACK]
January 1994
Status: PROPOSED STANDARD
Autor: G. Mansfield, S. Kille
RFC1568 Simple Network Paging Protocol - Version 1(b)
This RFC suggests a simple way for delivering both alphanumeric and numeric pages (one-way) to radio paging terminals. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
January 1994
Status: INFORMATIONAL
Autor: A. Gwinn
RFC1569 Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures
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.
January 1994
Status: INFORMATIONAL
Autor: M. Rose
RFC1570 PPP LCP Extensions
The Point-to-Point Protocol (PPP) 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. [STANDARDS-TRACK]
January 1994
Status: PROPOSED STANDARD
Autor: W. Simpson
RFC1571 Telnet Environment Option Interoperability Issues
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.
January 1994
Status: INFORMATIONAL
Autor: D. Borman
RFC1572 Telnet Environment Option
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. [STANDARDS-TRACK]
January 1994
Status: PROPOSED STANDARD
Autor: S. Alexander
RFC1573 Evolution of the Interfaces Group of MIB-II
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]
January 1994
Status: PROPOSED STANDARD
Autor: K. McCloghrie, F. Kastenholz
RFC1574 Essential Tools for the OSI Internet
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, and routing table dump function. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1994
Status: INFORMATIONAL
Autor: S. Hares, C. Wittbrodt
RFC1575 An Echo Function for CLNP (ISO 8473)
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 an Echo function to ISO 8473" an integral part of Version 2 of ISO 8473. [STANDARDS-TRACK]
February 1994
Status: DRAFT STANDARD
Autor: S. Hares, C. Wittbrodt
RFC1576 TN3270 Current Practices
This document describes the existing implementation of transferring 3270 display terminal data using currently available telnet capabilities. The name traditionally associated with this implementation is TN3270. This memo provides information for the Internet community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
January 1994
Status: INFORMATIONAL
Autor: J. Penner
RFC1577 Classical IP and ARP over ATM
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). [STANDARDS-TRACK]
January 1994
Status: PROPOSED STANDARD
Autor: M. Laubach
RFC1578 FYI on Questions and Answers - Answers to Commonly Asked "Primary and Secondary School Internet User" Questions
The goal of this FYI RFC 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. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. [FYI 22]
February 1994
Status: INFORMATIONAL
Autor: J. Sellers
RFC1579 Firewall-Friendly FTP
This memo describes a suggested change to the behavior of FTP client programs. This document provides information for the Internet community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1994
Status: INFORMATIONAL
Autor: S. Bellovin
RFC1580 Guide to Network Resource Tools
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]
March 1994
Status: INFORMATIONAL
Autor: EARN Staff
RFC1581 Protocol Analysis for Extensions to RIP to Support Demand Circuits
As required by Routing Protocol Criteria, this report documents the key features of Routing over Demand Circuits on Wide Area Networks - RIP and the current implementation experience. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1994
Status: INFORMATIONAL
Autor: G. Meyer
RFC1582 Extensions to RIP to Support Demand Circuits
This memo defines a generalized modification which can be applied to Bellman-Ford (or distance vector) algorithm information broadcasting protocols. [STANDARDS-TRACK]
February 1994
Status: PROPOSED STANDARD
Autor: G. Meyer
RFC1583 OSPF Version 2
This memo documents version 2 of the OSPF protocol. OSPF is a link- state routing protocol. [STANDARDS-TRACK]
March 1994
Status: DRAFT STANDARD
Autor: J. Moy
RFC1584 Multicast Extensions to OSPF
This memo documents enhancements to the OSPF protocol enabling the routing of IP multicast datagrams. [STANDARDS-TRACK]
March 1994
Status: HISTORIC
Autor: J. Moy
RFC1585 MOSPF: Analysis and Experience
This memo documents how the MOSPF protocol satisfies the requirements imposed on Internet routing protocols by "Internet Engineering Task Force internet routing protocol standardization criteria" ([RFC 1264]). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1994
Status: INFORMATIONAL
Autor: J. Moy
RFC1586 Guidelines for Running OSPF Over Frame Relay Networks
This memo specifies guidelines for implementors and users of the Open Shortest Path First (OSPF) routing protocol to bring about improvements in how the protocol runs over frame relay networks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1994
Status: INFORMATIONAL
Autor: O. deSouza, M. Rodrigues
RFC1587 The OSPF NSSA Option
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]
March 1994
Status: PROPOSED STANDARD
Autor: R. Coltun, V. Fuller
RFC1588 White Pages Meeting Report
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.
February 1994
Status: INFORMATIONAL
Autor: J. Postel, C. Anderson
RFC1589 A Kernel Model for Precision Timekeeping
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.
March 1994
Status: INFORMATIONAL
Autor: D. Mills
RFC1590 Media Type Registration Procedure
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 Media Types to make it appropriate to use the same registrations and specifications with other applications. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1994
Status: INFORMATIONAL
Autor: J. Postel
RFC1591 Domain Name System Structure and Delegation
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.
March 1994
Status: INFORMATIONAL
Autor: J. Postel
RFC1592 Simple Network Management Protocol Distributed Protocol Interface Version 2.0
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.
March 1994
Status: EXPERIMENTAL
Autor: B. Wijnen, G. Carpenter, K. Curran, A. Sehgal, G. Waters
RFC1593 SNA APPN Node MIB
This RFC describes IBM's SNMP support for SNA Advanced Peer-to-Peer Networking (APPN) nodes. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1994
Status: INFORMATIONAL
Autor: W. McKenzie, J. Cheng
RFC1594 FYI on Questions and Answers - Answers to Commonly asked "New Internet User" Questions
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. This memo does not specify an Internet standard of any kind. [FYI 4]
March 1994
Status: INFORMATIONAL
Autor: A. Marine, J. Reynolds, G. Malkin
RFC1595 Definitions of Managed Objects for the SONET/SDH Interface Type
March 1994
Status: PROPOSED STANDARD
Autor: T. Brown, K. Tesink
RFC1596 Definitions of Managed Objects for Frame Relay Service
March 1994
Status: PROPOSED STANDARD
Autor: T. Brown
RFC1597 Address Allocation for Private Internets
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.
March 1994
Status: INFORMATIONAL
Autor: Y. Rekhter, B. Moskowitz, D. Karrenberg, G. de Groot
RFC1598 PPP in X.25
The Point-to-Point Protocol (PPP) 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. [STANDARDS-TRACK]
March 1994
Status: PROPOSED STANDARD
Autor: W. Simpson
RFC1599 Summary of 1500-1599
January 1997
Status: INFORMATIONAL
Autor: M. Kennedy
RFC1600 Internet Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
March 1994
Status: HISTORIC
Autor: J. Postel
RFC1601 Charter of the Internet Architecture Board (IAB)
This memo documents the composition, selection, roles, and organization of the Internet Architecture Board and its subsidiary organizations. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1994
Status: INFORMATIONAL
Autor: C. Huitema
RFC1602 The Internet Standards Process -- Revision 2
This document is a revision of RFC 1310, which defined the official procedures for creating and documenting Internet Standards. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1994
Status: INFORMATIONAL
Autor: Internet Architecture Board, Internet Engineering Steering Group
RFC1603 IETF Working Group Guidelines and Procedures
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 Internet Engineering Steering Group (IESG). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1994
Status: INFORMATIONAL
Autor: E. Huizer, D. Crocker
RFC1604 Definitions of Managed Objects for Frame Relay Service
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 Frame Relay Service. [STANDARDS-TRACK]
March 1994
Status: PROPOSED STANDARD
Autor: T. Brown
RFC1605 SONET to Sonnet Translation
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). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1994
Status: INFORMATIONAL
Autor: W. Shakespeare
RFC1606 A Historical Perspective On The Usage Of IP Version 9
This paper reviews the usages of the old IP version protocol. It considers some of its successes and its failures. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1994
Status: INFORMATIONAL
Autor: J. Onions
RFC1607 A VIEW FROM THE 21ST CENTURY
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.
April 1994
Status: INFORMATIONAL
Autor: V. Cerf
RFC1608 Representing IP Information in the X.500 Directory
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 the Directory by applying it to IP networks. This memo defines an Experimental Protocol for the Internet community.
March 1994
Status: EXPERIMENTAL
Autor: T. Johannsen, G. Mansfield, M. Kosters, S. Sataluri
RFC1609 Charting Networks in the X.500 Directory
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. This memo defines an Experimental Protocol for the Internet community.
March 1994
Status: EXPERIMENTAL
Autor: G. Mansfield, T. Johannsen, M. Knopper
RFC1610 Internet Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
July 1994
Status: HISTORIC
Autor: J. Postel
RFC1611 DNS Server MIB Extensions
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]
May 1994
Status: HISTORIC
Autor: R. Austein, J. Saperia
RFC1612 DNS Resolver MIB Extensions
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]
May 1994
Status: HISTORIC
Autor: R. Austein, J. Saperia
RFC1613 cisco Systems X.25 over TCP (XOT)
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.
May 1994
Status: INFORMATIONAL
Autor: J. Forster, G. Satz, G. Glick, R. Day
RFC1614 Network Access to Multimedia Information
This report summarises the requirements of research and academic network users for network access to multimedia information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1994
Status: INFORMATIONAL
Autor: C. Adie
RFC1615 Migrating from X.400(84) to X.400(88)
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. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1994
Status: INFORMATIONAL
Autor: J. Houttuin, J. Craigie
RFC1616 X.400(1988) for the Academic and Research Community in Europe
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.
May 1994
Status: INFORMATIONAL
Autor: RARE WG-MSG Task Force 88, E. Huizer, J. Romaguera
RFC1617 Naming and Structuring Guidelines for X.500 Directory Pilots
This document defines a number of naming and structuring guidelines focused on White Pages usage. Alignment to these guidelines is recommended for directory pilots. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1994
Status: INFORMATIONAL
Autor: P. Barker, S. Kille, T. Lenggenhager
RFC1618 PPP over ISDN
This document describes the use of PPP over Integrated Services Digital Network (ISDN) switched circuits. [STANDARDS-TRACK]
May 1994
Status: PROPOSED STANDARD
Autor: W. Simpson
RFC1619 PPP over SONET/SDH
This document describes the use of PPP over Synchronous Optical Network (SONET) and Synchronous Digital Heirarchy (SDH) circuits. [STANDARDS-TRACK]
May 1994
Status: PROPOSED STANDARD
Autor: W. Simpson
RFC1620 Internet Architecture Extensions for Shared Media
This memo discusses alternative approaches to extending the Internet architecture to eliminate some or all unnecessary hops. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1994
Status: INFORMATIONAL
Autor: B. Braden, J. Postel, Y. Rekhter
RFC1621 Pip Near-term Architecture
The purpose of this RFC and the companion RFC "Pip Header Processing" are to record the ideas (good and bad) of Pip. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1994
Status: INFORMATIONAL
Autor: P. Francis
RFC1622 Pip Header Processing
The purpose of this RFC and the companion RFC "Pip Near-term Architecture" are to record the ideas (good and bad) of Pip. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1994
Status: INFORMATIONAL
Autor: P. Francis
RFC1623 Definitions of Managed Objects for the Ethernet-like Interface Types
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]
May 1994
Status: HISTORIC
Autor: F. Kastenholz
RFC1624 Computation of the Internet Checksum via Incremental Update
This memo describes an updated technique for incremental computation of the standard Internet checksum. It updates the method described in RFC 1141. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1994
Status: INFORMATIONAL
Autor: A. Rijsinghani
RFC1625 WAIS over Z39.50-1988
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.
June 1994
Status: INFORMATIONAL
Autor: M. St. Pierre, J. Fullton, K. Gamiel, J. Goldman, B. Kahle, J. Kunze, H. Morris, F. Schiettecatte
RFC1626 Default IP MTU for use over ATM AAL5
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]
May 1994
Status: PROPOSED STANDARD
Autor: R. Atkinson
RFC1627 Network 10 Considered Harmful (Some Practices Shouldn't be Codified)
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.
July 1994
Status: INFORMATIONAL
Autor: E. Lear, E. Fair, D. Crocker, T. Kessler
RFC1628 UPS Management Information Base
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]
May 1994
Status: INFORMATIONAL
Autor: J. Case
RFC1629 Guidelines for OSI NSAP Allocation in the Internet
This paper provides guidelines for allocating NSAP 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. [STANDARDS-TRACK]
May 1994
Status: DRAFT STANDARD
Autor: R. Colella, R. Callon, E. Gardner, Y. Rekhter
RFC1630 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
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.
June 1994
Status: INFORMATIONAL
Autor: T. Berners-Lee
RFC1631 The IP Network Address Translator (NAT)
This memo proposes another short-term solution, address reuse, that complements CIDR or even makes it unnecessary. The address reuse solution is to place Network Address Translators (NAT) at the borders of stub domains. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1994
Status: INFORMATIONAL
Autor: K. Egevang, P. Francis
RFC1632 A Revised Catalog of Available X.500 Implementations
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. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1994
Status: INFORMATIONAL
Autor: A. Getchell, S. Sataluri
RFC1633 Integrated Services in the Internet Architecture: an Overview
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 memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1994
Status: INFORMATIONAL
Autor: R. Braden, D. Clark, S. Shenker
RFC1634 Novell IPX Over Various WAN Media (IPXWAN)
This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocol Novell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1994
Status: INFORMATIONAL
Autor: M. Allen
RFC1635 How to Use Anonymous FTP
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. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1994
Status: INFORMATIONAL
Autor: P. Deutsch, A. Emtage, A. Marine
RFC1636 Report of IAB Workshop on Security in the Internet Architecture - February 8-10, 1994
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 memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1994
Status: INFORMATIONAL
Autor: R. Braden, D. Clark, S. Crocker, C. Huitema
RFC1637 DNS NSAP Resource Records
This document defines the format of one new Resource Record (RR) for the DNS for domain name-to-NSAP mapping. This memo defines an Experimental Protocol for the Internet community.
June 1994
Status: EXPERIMENTAL
Autor: B. Manning, R. Colella
RFC1638 PPP Bridging Control Protocol (BCP)
This document defines the Network Control Protocol for establishing and configuring Remote Bridging for PPP links. [STANDARDS-TRACK]
June 1994
Status: PROPOSED STANDARD
Autor: F. Baker, R. Bowen
RFC1639 FTP Operation Over Big Address Records (FOOBAR)
This RFC specifies a method for assigning addresses other than 32-bit IPv4 addresses to data ports through the specification of a "long Port (LPRT)" command and "Long Passive (LPSV)" reply, each having as its argument a <long-host-port>, which allows for additional address families, variable length network addresses and variable length port numbers. This memo defines an Experimental Protocol for the Internet community.
June 1994
Status: EXPERIMENTAL
Autor: D. Piscitello
RFC1640 The Process for Organization of Internet Standards Working Group (POISED)
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. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1994
Status: INFORMATIONAL
Autor: S. Crocker
RFC1641 Using Unicode with MIME
This document specifies the usage of Unicode within MIME. This memo defines an Experimental Protocol for the Internet community.
July 1994
Status: EXPERIMENTAL
Autor: D. Goldsmith, M. Davis
RFC1642 UTF-7 - A Mail-Safe Transformation Format of Unicode
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. This memo defines an Experimental Protocol for the Internet community.
July 1994
Status: EXPERIMENTAL
Autor: D. Goldsmith, M. Davis
RFC1643 Definitions of Managed Objects for the Ethernet-like Interface Types
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]
July 1994
Status: HISTORIC
Autor: F. Kastenholz
RFC1644 T/TCP -- TCP Extensions for Transactions Functional Specification
This memo specifies T/TCP, an experimental TCP extension for efficient transaction-oriented (request/response) service. This memo describes an Experimental Protocol for the Internet community.
July 1994
Status: HISTORIC
Autor: R. Braden
RFC1645 Simple Network Paging Protocol - Version 2
This RFC suggests a simple way for delivering both alphanumeric and numeric pages (one-way) to radio paging terminals. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
July 1994
Status: INFORMATIONAL
Autor: A. Gwinn
RFC1646 TN3270 Extensions for LUname and Printer Selection
This document describes protocol extensions to TN3270. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
July 1994
Status: INFORMATIONAL
Autor: C. Graves, T. Butts, M. Angel
RFC1647 TN3270 Enhancements
This document describes a protocol that more fully supports 3270 devices than do the existing tn3270 practices. [STANDARDS-TRACK]
July 1994
Status: PROPOSED STANDARD
Autor: B. Kelly
RFC1648 Postmaster Convention for X.400 Operations
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. [STANDARDS-TRACK]
July 1994
Status: HISTORIC
Autor: A. Cargille
RFC1649 Operational Requirements for X.400 Management Domains in the GO-MHS Community
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.
July 1994
Status: INFORMATIONAL
Autor: R. Hagens, A. Hansen
RFC1650 Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2
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]
August 1994
Status: PROPOSED STANDARD
Autor: F. Kastenholz
RFC1651 SMTP Service Extensions
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]
July 1994
Status: DRAFT STANDARD
Autor: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker
RFC1652 SMTP Service Extension for 8bit-MIMEtransport
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. [STANDARDS-TRACK]
July 1994
Status: DRAFT STANDARD
Autor: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker
RFC1653 SMTP Service Extension for Message Size Declaration
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]
July 1994
Status: DRAFT STANDARD
Autor: J. Klensin, N. Freed, K. Moore
RFC1654 A Border Gateway Protocol 4 (BGP-4)
This document defines an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK]
July 1994
Status: PROPOSED STANDARD
Autor: Y. Rekhter, T. Li
RFC1655 Application of the Border Gateway Protocol in the Internet
This document, together with its companion document, "A Border Gateway Protocol 4 (BGP-4)", define an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK]
July 1994
Status: PROPOSED STANDARD
Autor: Y. Rekhter, P. Gross
RFC1656 BGP-4 Protocol Document Roadmap and Implementation Experience
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.
July 1994
Status: INFORMATIONAL
Autor: P. Traina
RFC1657 Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2
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]
July 1994
Status: DRAFT STANDARD
Autor: S. Willis, J. Burruss, J. Chu
RFC1658 Definitions of Managed Objects for Character Stream Devices using SMIv2
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]
July 1994
Status: DRAFT STANDARD
Autor: B. Stewart
RFC1659 Definitions of Managed Objects for RS-232-like Hardware Devices using SMIv2
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]
July 1994
Status: DRAFT STANDARD
Autor: B. Stewart
RFC1660 Definitions of Managed Objects for Parallel-printer-like Hardware Devices using SMIv2
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]
July 1994
Status: DRAFT STANDARD
Autor: B. Stewart
RFC1661 The Point-to-Point Protocol (PPP)
This document defines the PPP organization and methodology, and the PPP encapsulation, together with an extensible option negotiation mechanism which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. [STANDARDS-TRACK]
July 1994
Status: STANDARD
Autor: W. Simpson
RFC1662 PPP in HDLC-like Framing
This document describes the use of HDLC-like framing for PPP encapsulated packets. [STANDARDS-TRACK]
July 1994
Status: STANDARD
Autor: W. Simpson
RFC1663 PPP Reliable Transmission
This document defines a method for negotiating and using Numbered-Mode, as defined by ISO 7776 [2], to provide a reliable serial link. [STANDARDS-TRACK]
July 1994
Status: PROPOSED STANDARD
Autor: D. Rand
RFC1664 Using the Internet DNS to Distribute RFC1327 Mail Address Mapping Tables
This memo defines how to store in the Internet Domain Name System the mapping information needed by e-mail gateways and other tools to map RFC822 domain names into X.400 O/R names and vice versa. This memo defines an Experimental Protocol for the Internet community.
August 1994
Status: EXPERIMENTAL
Autor: C. Allocchio, A. Bonito, B. Cole, S. Giordano, R. Hagens
RFC1665 Definitions of Managed Objects for SNA NAUs using SMIv2
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]
July 1994
Status: PROPOSED STANDARD
Autor: Z. Kielczewski, D. Kostick, K. Shih
RFC1666 Definitions of Managed Objects for SNA NAUs using SMIv2
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]
August 1994
Status: HISTORIC
Autor: Z. Kielczewski, D. Kostick, K. Shih
RFC1667 Modeling and Simulation Requirements for IPng
This white paper summarizes the Distributed Interactive Simulation environment that is under development, with regard to its real-time nature, scope and magnitude of networking requirements. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: S. Symington, D. Wood, M. Pullen
RFC1668 Unified Routing Requirements for IPng
The document provides requirements on the IPng from the perspective of the Unified Routing Architecture, as described in RFC 1322. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: D. Estrin, T. Li, Y. Rekhter
RFC1669 Market Viability as a IPng Criteria
"Viability in the Marketplace" is an important requirement for any IPng candidate and this paper is an attempt to summarize some important factors in determing market viability of IPng proposals. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: J. Curran
RFC1670 Input to IPng Engineering Considerations
This white paper expresses some personal opinions on IPng engineering considerations, based on experience with DECnet Phase V transition. It suggests breaking down the IPng decisions and transition tasks into smaller parts so they can be tackled early by the relevant experts. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: D. Heagerty
RFC1671 IPng White Paper on Transition and Other Considerations
This white paper outlines some general requirements for IPng in selected areas. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: B. Carpenter
RFC1672 Accounting Requirements for IPng
This white paper discusses accounting requirements for IPng. It recommends that all IPng packets carry accounting tags, which would vary in size. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: N. Brownlee
RFC1673 Electric Power Research Institute Comments on IPng
This document was submitted to the IETF IPng area in response to RFC 1550. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: R. Skelton
RFC1674 A Cellular Industry View of IPng
This is a draft of the requirements for IPng as envisioned by representatives of the Cellular Digital Packet Data (CDPD) consortium of service providers. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: M. Taylor
RFC1675 Security Concerns for IPng
A number of the candidates for IPng have some features that are somewhat worrisome from a security perspective. While it is not necessary that IPng be an improvement over IPv4, it is mandatory that it not make things worse. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: S. Bellovin
RFC1676 INFN Requirements for an IPng
With this paper we would like to emphasize the key points that we would to consider if charged with IPng plan. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: A. Ghiselli, D. Salomoni, C. Vistoli
RFC1677 Tactical Radio Frequency Communication Requirements for IPng
This paper describes requirements for Internet Protocol next generation (IPng) candidates with respect to their application to military tactical radio frequency (RF) communication networks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: B. Adamson
RFC1678 IPng Requirements of Large Corporate Networks
This draft summarizes some of the requirements of large corporate networks for the next generation of the Internet protcol suite. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: E. Britton, J. Tavs
RFC1679 HPN Working Group Input to the IPng Requirements Solicitation
The purpose of this document is to provide what the HPN working group perceives as requirements for an IPng protocol set. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: D. Green, P. Irey, D. Marlow, K. O'Donoghue
RFC1680 IPng Support for ATM Services
This white paper describes engineering considerations for IPng as solicited by RFC 1550 [1]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: C. Brazdziunas
RFC1681 On Many Addresses per Host
This document was submitted to the IETF IPng area in response to RFC 1550.This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: S. Bellovin
RFC1682 IPng BSD Host Implementation Analysis
This IPng white paper, IPng BSD Host Implementation Analysis, was submitted to the IPng Directorate to provide a BSD host point of reference to assist with the engineering considerations during the IETF process to select an IPng proposal. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: J. Bound
RFC1683 Multiprotocol Interoperability In IPng
In this document, we identify several features that affect a protocol's ability to operate in a multiprotocol environment and propose the incorporation of these features into IPng. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: R. Clark, M. Ammar, K. Calvert
RFC1684 Introduction to White Pages Services based on X.500
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 White Pages Service. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: P. Jurg
RFC1685 Writing X.400 O/R Names
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.
August 1994
Status: INFORMATIONAL
Autor: H. Alvestrand
RFC1686 IPng Requirements: A Cable Television Industry Viewpoint
This paper provides comments on topics related to the IPng requirements and selection criteria from a cable television industry viewpoint. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: M. Vecchi
RFC1687 A Large Corporate User's View of IPng
The goal of this paper is to examine the implications of IPng from the point of view of Fortune 100 corporations which have heavily invested in TCP/IP technology in order to achieve their (non-computer related) business goals.This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: E. Fleischman
RFC1688 IPng Mobility Considerations
This RFC specifies criteria related to mobility for consideration in design and selection of the Next Generation of IP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: W. Simpson
RFC1689 A Status Report on Networked Information Retrieval: Tools and Groups
The purpose of this report is to increase the awareness of Networked Information 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. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: J. Foster
RFC1690 Introducing the Internet Engineering and Planning Group (IEPG)
This memo introduces the IEPG to the Internet Community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: G. Huston
RFC1691 The Document Architecture for the Cornell Digital Library
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. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1994
Status: INFORMATIONAL
Autor: W. Turner
RFC1692 Transport Multiplexing Protocol (TMux)
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.
August 1994
Status: HISTORIC
Autor: P. Cameron, D. Crocker, D. Cohen, J. Postel
RFC1693 An Extension to TCP : Partial Order Service
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. This memo defines an Experimental Protocol for the Internet community.
November 1994
Status: HISTORIC
Autor: T. Connolly, P. Amer, P. Conrad
RFC1694 Definitions of Managed Objects for SMDS Interfaces using SMIv2
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. [STANDARDS-TRACK]
August 1994
Status: DRAFT STANDARD
Autor: T. Brown, K. Tesink
RFC1695 Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2
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]
August 1994
Status: PROPOSED STANDARD
Autor: M. Ahmed, K. Tesink
RFC1696 Modem Management Information Base (MIB) using SMIv2
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]
August 1994
Status: HISTORIC
Autor: J. Barnes, L. Brown, R. Royston, S. Waldbusser
RFC1697 Relational Database Management System (RDBMS) Management Information Base (MIB) using SMIv2
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]
August 1994
Status: PROPOSED STANDARD
Autor: D. Brower, B. Purvy, A. Daniel, M. Sinykin, J. Smith
RFC1698 Octet Sequences for Upper-Layer OSI to Support Basic Communications Applications
This document states particular octet sequences that comprise the OSI upper-layer protocols (Session, Presentation and ACSE) when used to support applications with "basic communications requirements". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1994
Status: INFORMATIONAL
Autor: P. Furniss
RFC1699 Summary of 1600-1699
January 1997
Status: INFORMATIONAL
Autor: J. Elliott
RFC1700 Assigned Numbers
This RFC is a snapshot of the ongoing process of the assignment of protocol parameters for the Internet protocol suite. To make the current information readily available the assignments are kept up-to- date in a set of online text files. This memo is a status report on the parameters (i.e., numbers and keywords) used in protocols in the Internet community.
October 1994
Status: HISTORIC
Autor: J. Reynolds, J. Postel
RFC1701 Generic Routing Encapsulation (GRE)
This document specifies a protocol for performing encapsulation of an arbitrary network layer protocol over another arbitrary network layer protocol. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1994
Status: INFORMATIONAL
Autor: S. Hanks, T. Li, D. Farinacci, P. Traina
RFC1702 Generic Routing Encapsulation over IPv4 networks
This memo addresses the case of using IP as the delivery protocol or the payload protocol and the special case of IP as both the delivery and payload. This memo also describes using IP addresses and autonomous system numbers as part of a GRE source route. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1994
Status: INFORMATIONAL
Autor: S. Hanks, T. Li, D. Farinacci, P. Traina
RFC1703 Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures
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.
October 1994
Status: INFORMATIONAL
Autor: M. Rose
RFC1704 On Internet Authentication
This document describes a spectrum of authentication technologies and provides suggestions to protocol developers on what kinds of authentication might be suitable for some kinds of protocols and applications used in the Internet. This document provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1994
Status: INFORMATIONAL
Autor: N. Haller, R. Atkinson
RFC1705 Six Virtual Inches to the Left: The Problem with IPng
This document was submitted to the IETF IPng area in response to RFC 1550. This RFC suggests that a new version of TCP (TCPng), and UDP, be developed and deployed. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1994
Status: INFORMATIONAL
Autor: R. Carlson, D. Ficarella
RFC1706 DNS NSAP Resource Records
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 any NSAP address format. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1994
Status: INFORMATIONAL
Autor: B. Manning, R. Colella
RFC1707 CATNIP: Common Architecture for the Internet
This document was submitted to the IETF IPng area in response to RFC 1550. This paper describes a common architecture for the network layer protocol. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1994
Status: INFORMATIONAL
Autor: M. McGovern, R. Ullmann
RFC1708 NTP PICS PROFORMA - For the Network Time Protocol Version 3
This RFC describes a PICS Proforma translated into an Internet acceptable form. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1994
Status: INFORMATIONAL
Autor: D. Gowin
RFC1709 K-12 Internetworking Guidelines
The K-12 community traditionally has not had this level of staffing available for telecommunications planning. This document is intended to bridge that gap and provides a recommended technical direction, an introduction to the role the Internet now plays in K-12 education and technical guidelines for building a campus data communications infrastructure that provides internetworking services and connections to the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
November 1994
Status: INFORMATIONAL
Autor: J. Gargano, D. Wasley
RFC1710 Simple Internet Protocol Plus White Paper
This document was submitted to the IETF IPng area in response to RFC 1550. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1994
Status: INFORMATIONAL
Autor: R. Hinden
RFC1711 Classifications in E-mail Routing
This paper presents a classification for e-mail routing issues. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1994
Status: INFORMATIONAL
Autor: J. Houttuin
RFC1712 DNS Encoding of Geographical Location
This document defines the format of a new Resource Record (RR) for the Domain Naming System (DNS), and reserves a corresponding DNS type mnemonic and numerical code. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind.
November 1994
Status: EXPERIMENTAL
Autor: C. Farrell, M. Schulze, S. Pleitner, D. Baldoni
RFC1713 Tools for DNS debugging
Although widely used (and most of the times unnoticed), DNS (Domain Name System) is too much overlooked, in the sense that people, especially administrators, tend to ignore possible anomalies as long as applications that need name-to-address mapping continue to work. This document presents some tools available for domain administrators to detect and correct those anomalies. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
November 1994
Status: INFORMATIONAL
Autor: A. Romao
RFC1714 Referral Whois Protocol (RWhois)
This memo describes version 1.0 of the client/server interaction of RWhois. RWhois provides a distributed system for the display of hierarchical information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
November 1994
Status: INFORMATIONAL
Autor: S. Williamson, M. Kosters
RFC1715 The H Ratio for Address Assignment Efficiency
This document was submitted to the IETF IPng area in response to RFC 1550. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
November 1994
Status: INFORMATIONAL
Autor: C. Huitema
RFC1716 Towards Requirements for IP Routers
The goal of this work is to replace RFC-1009, Requirements for Internet Gateways ([INTRO:1]) with a new document. It defines and discusses requirements for devices which perform the network layer forwarding function of the Internet protocol suite. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
November 1994
Status: INFORMATIONAL
Autor: P. Almquist, F. Kastenholz
RFC1717 The PPP Multilink Protocol (MP)
This document proposes a method for splitting, recombining and sequencing datagrams across multiple logical data links. [STANDARDS-TRACK]
November 1994
Status: PROPOSED STANDARD
Autor: K. Sklower, B. Lloyd, G. McGregor, D. Carr
RFC1718 The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force
The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This memo provides information for the Internet community. It does not specify an Internet standard. [FYI 17]
November 1994
Status: INFORMATIONAL
Autor: IETF Secretariat, G. Malkin
RFC1719 A Direction for IPng
This RFC specifies criteria related to mobility for consideration in design and selection of the Next Generation of IP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1994
Status: INFORMATIONAL
Autor: P. Gross
RFC1720 Internet Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
November 1994
Status: HISTORIC
Autor: J. Postel
RFC1721 RIP Version 2 Protocol Analysis
As required by Routing Protocol Criteria (RFC 1264), this report documents the key features of the RIP-2 protocol and the current implementation experience. This report is a prerequisite to advancing RIP-2 on the standards track. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
November 1994
Status: INFORMATIONAL
Autor: G. Malkin
RFC1722 RIP Version 2 Protocol Applicability Statement
As required by Routing Protocol Criteria (RFC 1264), this report defines the applicability of the RIP-2 protocol within the Internet. This report is a prerequisite to advancing RIP-2 on the standards track. [STANDARDS-TRACK]
November 1994
Status: STANDARD
Autor: G. Malkin
RFC1723 RIP Version 2 - Carrying Additional Information
This document specifies an extension of the Routing Information Protocol (RIP), o expand the amount of useful information carried in RIP messages and to add a measure of security. This memo obsoletes RFC 1388, which specifies an update to the "Routing Information Protocol" STD 34, RFC 1058. [STANDARDS-TRACK]
November 1994
Status: STANDARD
Autor: G. Malkin
RFC1724 RIP Version 2 MIB Extension
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. [STANDARDS-TRACK]
November 1994
Status: DRAFT STANDARD
Autor: G. Malkin, F. Baker
RFC1725 Post Office Protocol - Version 3
This memo is a revision to RFC 1460, a Draft Standard. [STANDARDS-TRACK]
November 1994
Status: STANDARD
Autor: J. Myers, M. Rose
RFC1726 Technical Criteria for Choosing IP The Next Generation (IPng)
This RFC specifies criteria related to mobility for consideration in design and selection of the Next Generation of IP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1994
Status: INFORMATIONAL
Autor: C. Partridge, F. Kastenholz
RFC1727 A Vision of an Integrated Internet Information Service
This paper lays out a vision of how Internet information services might be integrated over the next few years, and discusses in some detail what steps will be needed to achieve this integration. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1994
Status: INFORMATIONAL
Autor: C. Weider, P. Deutsch
RFC1728 Resource Transponders
This paper describes an automatic mechanism, the resource transponder, for maintaining resource location information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1994
Status: INFORMATIONAL
Autor: C. Weider
RFC1729 Using the Z39.50 Information Retrieval Protocol
This memo describes an approach to the implementation of the ANSI/NISO Z39.50-1992 Standard for Information Retrieval in the TCP/IP environment which is currently in wide use by the Z39.50 implementor community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1994
Status: INFORMATIONAL
Autor: C. Lynch
RFC1730 Internet Message Access Protocol - Version 4
The Internet Message Access Protocol, Version 4 (IMAP4) allows a client to access and manipulate electronic mail messages on a server. IMAP4 permits manipulation of remote message folders, called "mailboxes", in a way that is functionally equivalent to local mailboxes. IMAP4 also provides the capability for an offline client to resynchronize with the server. [STANDARDS-TRACK]
December 1994
Status: PROPOSED STANDARD
Autor: M. Crispin
RFC1731 IMAP4 Authentication Mechanisms
The Internet Message Access Protocol, Version 4 [IMAP4] contains the AUTHENTICATE command, for identifying and authenticating a user to an IMAP4 server and for optionally negotiating a protection mechanism for subsequent protocol interactions. This document describes several authentication mechanisms for use by the IMAP4 AUTHENTICATE command. [STANDARDS-TRACK]
December 1994
Status: PROPOSED STANDARD
Autor: J. Myers
RFC1732 IMAP4 Compatibility with IMAP2 and IMAP2bis
This is a summary of hints and recommendations to enable an IMAP4 implementation to interoperate with implementations that conform to earlier specifications. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1994
Status: INFORMATIONAL
Autor: M. Crispin
RFC1733 Distributed Electronic Mail Models in IMAP4
There are three fundamental models of client/server email: offline, online, and disconnected use. IMAP4 can be used in any one of these three models. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1994
Status: INFORMATIONAL
Autor: M. Crispin
RFC1734 POP3 AUTHentication command
This document describes the optional AUTH command, for indicating an authentication mechanism to the server, performing an authentication protocol exchange, and optionally negotiating a protection mechanism for subsequent protocol interactions. [STANDARDS-TRACK]
December 1994
Status: PROPOSED STANDARD
Autor: J. Myers
RFC1735 NBMA Address Resolution Protocol (NARP)
This document describes the NBMA Address Resolution Protocol (NARP). NARP can be used by a source terminal (host or router) connected to a Non-Broadcast, Multi-Access link layer (NBMA) network to find out the NBMA addresses of the a destination terminal provided that the destination terminal is connected to the same NBMA network. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind.
December 1994
Status: EXPERIMENTAL
Autor: J. Heinanen, R. Govindan
RFC1736 Functional Recommendations for Internet Resource Locators
This document specifies a minimum set of requirements for Internet resource locators, which convey location and access information for resources. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1995
Status: INFORMATIONAL
Autor: J. Kunze
RFC1737 Functional Requirements for Uniform Resource Names
This document specifies a minimum set of requirements for a kind of Internet resource identifier known as Uniform Resource Names (URNs). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1994
Status: INFORMATIONAL
Autor: K. Sollins, L. Masinter
RFC1738 Uniform Resource Locators (URL)
This document specifies a Uniform Resource Locator (URL), the syntax and semantics of formalized information for location and access of resources via the Internet. [STANDARDS-TRACK]
December 1994
Status: PROPOSED STANDARD
Autor: T. Berners-Lee, L. Masinter, M. McCahill
RFC1739 A Primer On Internet and TCP/IP Tools
This memo is an introductory guide to some of the TCP/IP and Internet tools and utilities that allow users to access the wide variety of information on the network, from determining if a particular host is up to viewing a multimedia thesis on foreign policy. It also describes discussion lists accessible from the Internet, ways to obtain Internet documents, and resources that help users weave their way through the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1994
Status: INFORMATIONAL
Autor: G. Kessler, S. Shepard
RFC1740 MIME Encapsulation of Macintosh Files - MacMIME
This memo describes the format to use when sending Apple Macintosh files via MIME [BORE93]. [STANDARDS-TRACK]
December 1994
Status: PROPOSED STANDARD
Autor: P. Faltstrom, D. Crocker, E. Fair
RFC1741 MIME Content Type for BinHex Encoded Files
This memo describes the format to use when sending BinHex4.0 files via MIME [BORE93]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1994
Status: INFORMATIONAL
Autor: P. Faltstrom, D. Crocker, E. Fair
RFC1742 AppleTalk Management Information Base II
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 AppleTalk networks. [STANDARDS-TRACK]
January 1995
Status: HISTORIC
Autor: S. Waldbusser, K. Frisa
RFC1743 IEEE 802.5 MIB using SMIv2
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 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]
December 1994
Status: DRAFT STANDARD
Autor: K. McCloghrie, E. Decker
RFC1744 Observations on the Management of the Internet Address Space
This memo examines some of the issues associated with the current management practices of the Internet IPv4 address space, and examines the potential outcomes of these practices as the unallocated address pool shrinks in size. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1994
Status: INFORMATIONAL
Autor: G. Huston
RFC1745 BGP4/IDRP for IP---OSPF Interaction
This memo defines the various criteria to be used when designing an Autonomous System Border Router (ASBR) that will run either BGP4 or IDRP for IP with other ASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK]
December 1994
Status: HISTORIC
Autor: K. Varadhan, S. Hares, Y. Rekhter
RFC1746 Ways to Define User Expectations
This paper covers basic fundamentals that must be understood when one defines, interprets, or implements methods to control user expectations on or over the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1994
Status: INFORMATIONAL
Autor: B. Manning, D. Perkins
RFC1747 Definitions of Managed Objects for SNA Data Link Control (SDLC) using SMIv2
This specification defines an extension to the Management Information Base (MIB) for use with SNMP-based network management. In particular, it defines objects for managing the configuration, monitoring and control of data link controls in an SNA environment. [STANDARDS-TRACK]
January 1995
Status: HISTORIC
Autor: J. Hilgeman, S. Nix, A. Bartky, W. Clark
RFC1748 IEEE 802.5 MIB using SMIv2
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 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]
December 1994
Status: DRAFT STANDARD
Autor: K. McCloghrie, E. Decker
RFC1749 IEEE 802.5 Station Source Routing MIB using SMIv2
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 by IEEE 802.5 end-stations for managing source routes on a Token Ring network where IEEE source- routing is in use. [STANDARDS-TRACK]
December 1994
Status: HISTORIC
Autor: K. McCloghrie, F. Baker, E. Decker
RFC1750 Randomness Recommendations for Security
Choosing random quantities to foil a resourceful and motivated adversary is surprisingly difficult. This paper points out many pitfalls in using traditional pseudo-random number generation techniques for choosing such quantities. It recommends the use of truly random hardware techniques and shows that the existing hardware on many systems can be used for this purpose. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1994
Status: INFORMATIONAL
Autor: D. Eastlake 3rd, S. Crocker, J. Schiller
RFC1751 A Convention for Human-Readable 128-bit Keys
This memo proposes a convention for use with Internet applications & protocols using 128-bit cryptographic keys. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1994
Status: INFORMATIONAL
Autor: D. McDonald
RFC1752 The Recommendation for the IP Next Generation Protocol
This document presents the recommendation of the IPng Area Directors on what should be used to replace the current version of the Internet Protocol. [STANDARDS-TRACK]
January 1995
Status: PROPOSED STANDARD
Autor: S. Bradner, A. Mankin
RFC1753 IPng Technical Requirements Of the Nimrod Routing and Addressing Architecture
This document presents the requirements that the Nimrod routing and addressing architecture has upon the internetwork layer protocol. To be most useful to Nimrod, any protocol selected as the IPng should satisfy these requirements. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1994
Status: INFORMATIONAL
Autor: N. Chiappa
RFC1754 IP over ATM Working Group's Recommendations for the ATM Forum's Multiprotocol BOF Version 1
This document represents an initial list of requirements submitted to the ATM Forum's Multiprotocol BOF for the operation of IP over ATM networks as determined by the IETF IP over ATM Working Group and other working groups. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
January 1995
Status: INFORMATIONAL
Autor: M. Laubach
RFC1755 ATM Signaling Support for IP over ATM
This memo describes the ATM call control signaling exchanges needed to support Classical IP over ATM implementations as described in RFC 1577. [STANDARDS-TRACK]
February 1995
Status: PROPOSED STANDARD
Autor: M. Perez, F. Liaw, A. Mankin, E. Hoffman, D. Grossman, A. Malis
RFC1756 Remote Write Protocol - Version 1.0
This document describes a simple Remote Write Protocol (RWP). This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind.
January 1995
Status: EXPERIMENTAL
Autor: T. Rinne
RFC1757 Remote Network Monitoring Management Information Base
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices. [STANDARDS-TRACK]
February 1995
Status: DRAFT STANDARD
Autor: S. Waldbusser
RFC1758 NADF Standing Documents: A Brief Overview
The purpose of this document is to provide a brief overview of the NADF's Standing Document series. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1995
Status: INFORMATIONAL
Autor: The North American Directory Forum
RFC1759 Printer MIB
A printer is the physical device that takes media from an input source, produces marks on that media according to some page description or page control language and puts the result in some output destination, possibly with finishing applied. The information needed in the management of the physical printer and the management of a printing job overlap highly and many of the tasks in each management area require the same or similar information. [STANDARDS-TRACK]
March 1995
Status: PROPOSED STANDARD
Autor: R. Smith, F. Wright, T. Hastings, S. Zilles, J. Gyllenskog
RFC1760 The S/KEY One-Time Password System
This document describes the S/KEY* One-Time Password system as released for public use by Bellcore. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1995
Status: INFORMATIONAL
Autor: N. Haller
RFC1761 Snoop Version 2 Packet Capture File Format
This paper describes the file format used by "snoop", a packet monitoring and capture program developed by Sun. This paper is provided so that people can write compatible programs to generate and interpret snoop packet capture files. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1995
Status: INFORMATIONAL
Autor: B. Callaghan, R. Gilligan
RFC1762 The PPP DECnet Phase IV Control Protocol (DNCP)
This document defines the NCP for establishing and configuring Digital'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). [STANDARDS-TRACK]
March 1995
Status: DRAFT STANDARD
Autor: S. Senum
RFC1763 The PPP Banyan Vines Control Protocol (BVCP)
This document defines the Network Control Protocol for establishing and configuring the Banyan VINES protocol over PPP. [STANDARDS-TRACK]
March 1995
Status: HISTORIC
Autor: S. Senum
RFC1764 The PPP XNS IDP Control Protocol (XNSCP)
This document defines the Network Control Protocol for establishing and configuring the Xerox Network Systems (XNS) Internet Datagram Protocol (IDP) over PPP. [STANDARDS-TRACK]
March 1995
Status: HISTORIC
Autor: S. Senum
RFC1765 OSPF Database Overflow
This memo details a way of gracefully handling unanticipated database overflows. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind.
March 1995
Status: EXPERIMENTAL
Autor: J. Moy
RFC1766 Tags for the Identification of Languages
This document describes a language tag for use in cases where it is desired to indicate the language used in an information object. [STANDARDS-TRACK]
March 1995
Status: PROPOSED STANDARD
Autor: H. Alvestrand
RFC1767 MIME Encapsulation of EDI Objects
Since there are many different EDI specifications, the current document defines three distinct categories as three different MIME content-types. [STANDARDS-TRACK]
March 1995
Status: PROPOSED STANDARD
Autor: D. Crocker
RFC1768 Host Group Extensions for CLNP Multicasting
This memo provides a specification for multicast extensions to the CLNP protocol similar to those provided to IP by RFC1112. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind.
March 1995
Status: EXPERIMENTAL
Autor: D. Marlow
RFC1769 Simple Network Time Protocol (SNTP)
This memorandum describes the Simple Network Time Protocol (SNTP), which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1995
Status: INFORMATIONAL
Autor: D. Mills
RFC1770 IPv4 Option for Sender Directed Multi-Destination Delivery
This memo defines an IPv4 option to provide a sender directed multi- destination delivery mechanism called Selective Directed Broadcast Mode (SDBM). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1995
Status: INFORMATIONAL
Autor: C. Graff
RFC1771 A Border Gateway Protocol 4 (BGP-4)
This document, 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]
March 1995
Status: DRAFT STANDARD
Autor: Y. Rekhter, T. Li
RFC1772 Application of the Border Gateway Protocol in the Internet
This document, together with its companion document, "A Border Gateway Protocol 4 (BGP-4)", define an inter-autonomous system routing protocol for the Internet. This document describes the usage of the BGP in the Internet. [STANDARDS-TRACK]
March 1995
Status: DRAFT STANDARD
Autor: Y. Rekhter, P. Gross
RFC1773 Experience with the BGP-4 protocol
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 version 4 (BGP-4). This report documents experience with BGP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1995
Status: INFORMATIONAL
Autor: P. Traina
RFC1774 BGP-4 Protocol Analysis
The purpose of this report is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by the Border Gateway Protocol version 4 (BGP-4). This report summarizes the key features of BGP, and analyzes the protocol with respect to scaling and performance. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1995
Status: INFORMATIONAL
Autor: P. Traina
RFC1775 To Be "On" the Internet
The Internet permits different levels of access for consumers and providers of service. The nature of those differences is quite important in the capabilities They afford. Hence, it is appropriate to provide terminology that distinguishes among the range, so that the Internet community can gain some clarity when distinguishing whether a user (or an organization) is "on" the Internet. This document suggests four terms, for distinguishing the major classes of access. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1995
Status: INFORMATIONAL
Autor: D. Crocker
RFC1776 The Address is the Message
Declaring that the address is the message, the IPng WG has selected a packet format which includes 1696 bytes of address space. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1995
Status: INFORMATIONAL
Autor: S. Crocker
RFC1777 Lightweight Directory Access Protocol
The protocol described in this document is designed to provide access to the X.500 Directory while not incurring the resource requirements of the Directory Access Protocol (DAP).This protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive access to the X.500 Directory, and is intended to be a complement to the DAP itself. [STANDARDS-TRACK]
March 1995
Status: HISTORIC
Autor: W. Yeong, T. Howes, S. Kille
RFC1778 The String Representation of Standard Attribute Syntaxes
The Lightweight Directory Access Protocol (LDAP) 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 X.500 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. [STANDARDS-TRACK]
March 1995
Status: HISTORIC
Autor: T. Howes, S. Kille, W. Yeong, C. Robbins
RFC1779 A String Representation of Distinguished Names
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. [STANDARDS-TRACK]
March 1995
Status: HISTORIC
Autor: S. Kille
RFC1780 Internet Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
March 1995
Status: HISTORIC
Autor: J. Postel
RFC1781 Using the OSI Directory to Achieve User Friendly Naming
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. [STANDARDS-TRACK]
March 1995
Status: HISTORIC
Autor: S. Kille
RFC1782 TFTP Option Extension
The Trivial File Transfer Protocol is a simple, lock-step, file transfer protocol which allows a client to get or put a file onto a remote host. This document describes a simple extension to TFTP to allow option negotiation prior to the file transfer.
March 1995
Status: PROPOSED STANDARD
Autor: G. Malkin, A. Harkin
RFC1783 TFTP Blocksize Option
This document describes a TFTP option which allows the client and server to negotiate a blocksize more applicable to the network medium. [STANDARDS-TRACK]
March 1995
Status: PROPOSED STANDARD
Autor: G. Malkin, A. Harkin
RFC1784 TFTP Timeout Interval and Transfer Size Options
This document describes two TFTP options. The first allows the client and server to negotiate the Timeout Interval. The second allows the side receiving the file to determine the ultimate size of the transfer before it begins. [STANDARDS-TRACK]
March 1995
Status: PROPOSED STANDARD
Autor: G. Malkin, A. Harkin
RFC1785 TFTP Option Negotiation Analysis
This document was written to allay concerns that the presence of options in a TFTP Request packet might cause pathological behavior on servers which do not support TFTP option negotiation. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1995
Status: INFORMATIONAL
Autor: G. Malkin, A. Harkin
RFC1786 Representation of IP Routing Policies in a Routing Registry (ripe-81++)
This document is an update to the original `ripe-81' proposal for representing and storing routing polices within the RIPE database. It incorporates several extensions proposed by Merit Inc. and gives details of a generalized IP routing policy representation to be used by all Internet routing registries. It acts as both tutorial and provides details of database objects and attributes that use and make up a routing registry. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1995
Status: INFORMATIONAL
Autor: T. Bates, E. Gerich, L. Joncheray, J-M. Jouanigot, D. Karrenberg, M. Terpstra, J. Yu
RFC1787 Routing in a Multi-provider Internet
This document presents some of the issues related to network layer routing in a multi-provider Internet, and specifically to the unicast routing. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1995
Status: INFORMATIONAL
Autor: Y. Rekhter
RFC1788 ICMP Domain Name Messages
This document specifies ICMP messages for learning the Fully Qualified Domain Name associated with an IP address. This document defines an Experimental Protocol for the Internet community. This does not specify an Internet standard of any kind.
April 1995
Status: EXPERIMENTAL
Autor: W. Simpson
RFC1789 INETPhone: Telephone Services and Servers on Internet
This RFC presents a true telephone service, called INETPhone, which supports voice communication through the Internet. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
April 1995
Status: INFORMATIONAL
Autor: C. Yang
RFC1790 An Agreement between the Internet Society and Sun Microsystems, Inc. in the Matter of ONC RPC and XDR Protocols
This RFC is an official public record of an agreement between SUN Microsystems and the Internet Society. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
April 1995
Status: INFORMATIONAL
Autor: V. Cerf
RFC1791 TCP And UDP Over IPX Networks With Fixed Path MTU
TCP/IPX allows TCP/IP applications to run over IPX networks by letting TCP and UDP run over IPX. And this memo specifies the packet format and operational procedures for running TCP and UDP over IPX. This document defines an Experimental Protocol for the Internet community. This does not specify an Internet standard of any kind.
April 1995
Status: EXPERIMENTAL
Autor: T. Sung
RFC1792 TCP/IPX Connection Mib Specification
New MIB objects, tcpIpxConnTable, udpIpxTable, tcpUnspecConnTable and udpUnspecTable are presented in this paper, to be used in place of tcpConnTable and udpListenerTable when TCP and UDP are running over IPX. This document defines an Experimental Protocol for the Internet community. This does not specify an Internet standard of any kind.
April 1995
Status: EXPERIMENTAL
Autor: T. Sung
RFC1793 Extending OSPF to Support Demand Circuits
This memo defines enhancements to the OSPF protocol that allow efficient operation over "demand circuits". [STANDARDS-TRACK]
April 1995
Status: PROPOSED STANDARD
Autor: J. Moy
RFC1794 DNS Support for Load Balancing
This RFC is meant to first chronicle a foray into the IETF DNS Working Group, discuss other possible alternatives to provide/simulate load balancing support for DNS, and to provide an ultimate, flexible solution for providing DNS support for balancing loads of many types. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1995
Status: INFORMATIONAL
Autor: T. Brisco
RFC1795 Data Link Switching: Switch-to-Switch Protocol AIW DLSw RIG: DLSw Closed Pages, DLSw Standard Version 1
This RFC describes use of Data Link Switching over TCP/IP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1995
Status: INFORMATIONAL
Autor: L. Wells, A. Bartky
RFC1796 Not All RFCs are Standards
This document discusses the relationship of the Request for Comments (RFCs) notes to Internet Standards. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1995
Status: INFORMATIONAL
Autor: C. Huitema, J. Postel, S. Crocker
RFC1797 Class A Subnet Experiment
There appears to be some interest in experimenting with subnetting the class A addresses. It is suggested that conducting an experiment now to identify and fix any software that does not properly handle subnetted class A addresses would be useful and important. This document defines an Experimental Protocol for the Internet community. This does not specify an Internet standard of any kind.
April 1995
Status: EXPERIMENTAL
Autor: Internet Assigned Numbers Authority (IANA)
RFC1798 Connection-less Lightweight X.500 Directory Access Protocol
The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). [STANDARDS-TRACK]
June 1995
Status: HISTORIC
Autor: A. Young
RFC1799 Request for Comments Summary RFC Numbers 1700-1799
January 1997
Status: INFORMATIONAL
Autor: M. Kennedy
RFC1800 Internet Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
July 1995
Status: HISTORIC
Autor: J. Postel
RFC1801 MHS use of the X.500 Directory to support MHS Routing
The key problem in routing is to map from an O/R Address onto an MTA (next hop). This shall be an MTA which in some sense is "nearer" to the destination UA. This is done repeatedly until the message can be directly delivered to the recipient UA. This memo defines an Experimental Protocol for the Internet community.
June 1995
Status: EXPERIMENTAL
Autor: S. Kille
RFC1802 Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 Routing
This memo describes a proposed Internet Pilot Project that seeks to prove the MHS-DS approach on a larger scale. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1995
Status: INFORMATIONAL
Autor: H. Alvestrand, K. Jordan, S. Langlois, J. Romaguera
RFC1803 Recommendations for an X.500 Production Directory Service
This document contains a set of basic recommendations for a country- level X.500 DSA. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
June 1995
Status: INFORMATIONAL
Autor: R. Wright, A. Getchell, T. Howes, S. Sataluri, P. Yee, W. Yeong
RFC1804 Schema Publishing in X.500 Directory
In this document we propose a solution using the existing mechanisms of the directory [1] itself. We present a naming scheme for naming schema objects and a meta-schema for storing schema objects in the directory. This memo defines an Experimental Protocol for the Internet community.
June 1995
Status: EXPERIMENTAL
Autor: G. Mansfield, P. Rajeev, S. Raghavan, T. Howes
RFC1805 Location-Independent Data/Software Integrity Protocol
This memo describes a protocol for adding integrity assurance to files that are distributed across the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1995
Status: INFORMATIONAL
Autor: A. Rubin
RFC1806 Communicating Presentation Information in Internet Messages: The Content-Disposition Header
This memo provides a mechanism whereby messages conforming to the [RFC 1521] ("MIME") specification can convey presentational information. This memo defines an Experimental Protocol for the Internet community.
June 1995
Status: EXPERIMENTAL
Autor: R. Troost, S. Dorner
RFC1807 A Format for Bibliographic Records
This RFC defines a format for bibliographic records describing technical reports. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1995
Status: INFORMATIONAL
Autor: R. Lasher, D. Cohen
RFC1808 Relative Uniform Resource Locators
In situations where the base URL is well-defined and known to the parser (human or machine), it is useful to be able to embed URL references which inherit that context rather than re-specifying it in every instance. This document defines the syntax and semantics for such Relative Uniform Resource Locators. [STANDARDS-TRACK]
June 1995
Status: PROPOSED STANDARD
Autor: R. Fielding
RFC1809 Using the Flow Label Field in IPv6
The purpose of this memo is to distill various opinions and suggestions of the End-to-End Research Group regarding the handling of Flow Labels into a set of suggestions for IPv6. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1995
Status: INFORMATIONAL
Autor: C. Partridge
RFC1810 Report on MD5 Performance
This RFC addresses how fast MD5 can be implemented in software and hardware, and whether it supports currently available IP bandwidth. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1995
Status: INFORMATIONAL
Autor: J. Touch
RFC1811 U.S. Government Internet Domain Names
This document describes the registration policies for the top-level domain ".GOV". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1995
Status: INFORMATIONAL
Autor: Federal Networking Council
RFC1812 Requirements for IP Version 4 Routers
This memo defines and discusses requirements for devices that perform the network layer forwarding function of the Internet protocol suite. [STANDARDS-TRACK]
June 1995
Status: PROPOSED STANDARD
Autor: F. Baker
RFC1813 NFS Version 3 Protocol Specification
This paper describes the NFS version 3 protocol. This paper is provided so that people can write compatible implementations. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1995
Status: INFORMATIONAL
Autor: B. Callaghan, B. Pawlowski, P. Staubach
RFC1814 Unique Addresses are Good
The IAB suggests that while RFC 1597 establishes reserved IP address space for the use of private networks which are isolated and will remain isolated from the Internet, any enterprise which anticipates external connectivity to the Internet should apply for a globally unique address from an Internet registry or service provider. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1995
Status: INFORMATIONAL
Autor: E. Gerich
RFC1815 Character Sets ISO-10646 and ISO-10646-J-1
For the practical use of ISO 10646, a lot of external profiling such as restriction of characters, restriction of combination of characters and addition of language information is necessary. This memo provides information on such profiling, along with charset names to each profiled instance. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
July 1995
Status: INFORMATIONAL
Autor: M. Ohta
RFC1816 U.S. Government Internet Domain Names
This memo provides an update and clarification to RFC 1811. This document describes the registration policies for the top-level domain ".GOV". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1995
Status: INFORMATIONAL
Autor: Federal Networking Council
RFC1817 CIDR and Classful Routing
This document represents the IAB's (Internet Architecture Board) evaluation of the current and near term implications of CIDR on organizations that use Classful routing technology. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1995
Status: HISTORIC
Autor: Y. Rekhter
RFC1818 Best Current Practices
This document describes a new series of documents which describe best current practices for the Internet community. Documents in this series carry the endorsement of the Internet Engineering Steering Group (IESG).
August 1995
Status: HISTORIC
Autor: J. Postel, T. Li, Y. Rekhter
RFC1819 Internet Stream Protocol Version 2 (ST2) Protocol Specification - Version ST2+
This memo contains a revised specification of the Internet STream Protocol Version 2 (ST2). This memo defines an Experimental Protocol for the Internet community.
August 1995
Status: EXPERIMENTAL
Autor: L. Delgrossi, L. Berger
RFC1820 Multimedia E-mail (MIME) User Agent Checklist
This document presents a checklist to facilitate evaluation of MIME capable User Agents. Access to a MIME test-responder, that generates test-messages is described. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1995
Status: INFORMATIONAL
Autor: E. Huizer
RFC1821 Integration of Real-time Services in an IP-ATM Network Architecture
The purpose of this paper is to provide a clear statement of what issues need to be addressed in interfacing the IP integrated services environment with an ATM service environment so as to create a seamless interface between the two in support of end users desiring real-time networking services. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1995
Status: INFORMATIONAL
Autor: M. Borden, E. Crawley, B. Davie, S. Batsell
RFC1822 A Grant of Rights to Use a Specific IBM patent with Photuris
This Request for Comments records a grant by IBM Corporation to permit the conditional free use of one of its patents. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1995
Status: INFORMATIONAL
Autor: J. Lowe
RFC1823 The LDAP Application Program Interface
This document defines a C language application program interface to the lightweight directory access protocol (LDAP). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1995
Status: INFORMATIONAL
Autor: T. Howes, M. Smith
RFC1824 The Exponential Security System TESS: An Identity-Based Cryptographic Protocol for Authenticated Key-Exchange (E.I.S.S.-Report 1995/4)
This informational RFC describes the basic mechanisms and functions of an identity based system for the secure authenticated exchange of cryptographic keys, the generation of signatures, and the authentic distribution of public keys. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1995
Status: INFORMATIONAL
Autor: H. Danisch
RFC1825 Security Architecture for the Internet Protocol
This memo describes the security mechanisms for IP version 4 (IPv4) and IP version 6 (IPv6) and the services that they provide. [STANDARDS-TRACK]
August 1995
Status: PROPOSED STANDARD
Autor: R. Atkinson
RFC1826 IP Authentication Header
This document describes a mechanism for providing cryptographic authentication for IPv4 and IPv6 datagrams. [STANDARDS-TRACK]
August 1995
Status: PROPOSED STANDARD
Autor: R. Atkinson
RFC1827 IP Encapsulating Security Payload (ESP)
This document describes the IP Encapsulating Security Payload (ESP). ESP is a mechanism for providing integrity and confidentiality to IP datagrams. [STANDARDS-TRACK]
August 1995
Status: PROPOSED STANDARD
Autor: R. Atkinson
RFC1828 IP Authentication using Keyed MD5
This document describes the use of keyed MD5 with the IP Authentication Header. [STANDARDS-TRACK]
August 1995
Status: HISTORIC
Autor: P. Metzger, W. Simpson
RFC1829 The ESP DES-CBC Transform
This document describes the DES-CBC security transform for the IP Encapsulating Security Payload (ESP). [STANDARDS-TRACK]
August 1995
Status: PROPOSED STANDARD
Autor: P. Karn, P. Metzger, W. Simpson
RFC1830 SMTP Service Extensions for Transmission of Large and Binary MIME Messages
This memo defines two extensions to the SMTP service. The first service enables a SMTP client and server to negotiate the use of an alternate DATA command "BDAT" for efficiently sending large MIME messages. The second extension takes advantage of the BDAT command to permit the negotiated sending of unencoded binary data. This memo defines an Experimental Protocol for the Internet community.
August 1995
Status: EXPERIMENTAL
Autor: G. Vaudreuil
RFC1831 RPC: Remote Procedure Call Protocol Specification Version 2
This document describes the ONC Remote Procedure Call (ONC RPC Version 2) protocol as it is currently deployed and accepted. [STANDARDS-TRACK]
August 1995
Status: PROPOSED STANDARD
Autor: R. Srinivasan
RFC1832 XDR: External Data Representation Standard
This document describes the External Data Representation Standard (XDR) protocol as it is currently deployed and accepted. [STANDARDS-TRACK]
August 1995
Status: DRAFT STANDARD
Autor: R. Srinivasan
RFC1833 Binding Protocols for ONC RPC Version 2
This document describes the binding protocols used in conjunction with the ONC Remote Procedure Call (ONC RPC Version 2) protocols. [STANDARDS-TRACK]
August 1995
Status: PROPOSED STANDARD
Autor: R. Srinivasan
RFC1834 Whois and Network Information Lookup Service, Whois++
This memo describes new features for WHOIS. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1995
Status: INFORMATIONAL
Autor: J. Gargano, K. Weiss
RFC1835 Architecture of the WHOIS++ service
This document describes WHOIS++, an extension to the trivial WHOIS service described in RFC 954 to permit WHOIS-like servers to make available more structured information to the Internet. [STANDARDS-TRACK]
August 1995
Status: HISTORIC
Autor: P. Deutsch, R. Schoultz, P. Faltstrom, C. Weider
RFC1836 Representing the O/R Address hierarchy in the X.500 Directory Information Tree
This document defines a representation of the O/R Address hierarchy in the Directory Information Tree [6, 1]. This memo defines an Experimental Protocol for the Internet community.
August 1995
Status: EXPERIMENTAL
Autor: S. Kille
RFC1837 Representing Tables and Subtrees in the X.500 Directory
This document defines techniques for representing two types of information mapping in the OSI Directory. This memo defines an Experimental Protocol for the Internet community.
August 1995
Status: EXPERIMENTAL
Autor: S. Kille
RFC1838 Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses
This document defines how to use directory to support the mapping between X.400 O/R Addresses and mailboxes defined in RFC 1327 [2]. This memo defines an Experimental Protocol for the Internet community.
August 1995
Status: EXPERIMENTAL
Autor: S. Kille
RFC1841 PPP Network Control Protocol for LAN Extension
September 1995
Status: INFORMATIONAL
Autor: J. Chapman, D. Coli, A. Harvey, B. Jensen, K. Rowett
RFC1842 ASCII Printable Characters-Based Chinese Character Encoding for Internet Messages
This document describes the encoding used in electronic mail [RFC822] and network news [RFC1036] messages over the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Telecommunications infrastructure is improving to offer higher bandwidth connections at lower cost. Access to the network is changing from modems to more intelligent devices. This informational RFC discusses a PPP Network Control Protocol for one such intelligent device. The protocol is the LAN extension interface protocol. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1995
Status: INFORMATIONAL
Autor: Y. Wei, Y. Zhang, J. Li, J. Ding, Y. Jiang
RFC1843 HZ - A Data Format for Exchanging Files of Arbitrarily Mixed Chinese and ASCII characters
The content of this memo is identical to an article of the same title written by the author on September 4, 1989. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1995
Status: INFORMATIONAL
Autor: F. Lee
RFC1844 Multimedia E-mail (MIME) User Agent Checklist
This document presents a checklist to facilitate evaluation of MIME capable User Agents. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1995
Status: INFORMATIONAL
Autor: E. Huizer
RFC1845 SMTP Service Extension for Checkpoint/Restart
September 1995
Status: EXPERIMENTAL
Autor: D. Crocker, N. Freed, A. Cargille
RFC1846 SMTP 521 Reply Code
September 1995
Status: EXPERIMENTAL
Autor: A. Durand, F. Dupont
RFC1847 Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted
This document defines a framework within which security services may be applied to MIME body parts. [STANDARDS-TRACK] This memo defines a new Simple Mail Transfer Protocol (SMTP) [1] reply code, 521, which one may use to indicate that an Internet host does not accept incoming mail. This memo defines an Experimental Protocol for the Internet community. This memo defines an extension to the SMTP service whereby an interrupted SMTP transaction can be restarted at a later time without having to repeat all of the commands and message content sent prior to the interruption. This memo defines an Experimental Protocol for the Internet community.
October 1995
Status: PROPOSED STANDARD
Autor: J. Galvin, S. Murphy, S. Crocker, N. Freed
RFC1848 MIME Object Security Services
This document defines MIME Object Security Services (MOSS), a protocol that uses the multipart/signed and multipart/encrypted framework [7] to apply digital signature and encryption services to MIME objects. [STANDARDS-TRACK]
October 1995
Status: HISTORIC
Autor: S. Crocker, N. Freed, J. Galvin, S. Murphy
RFC1849 "Son of 1036": News Article Format and Transmission
By the early 1990s, it had become clear that RFC 1036, then the specification for the Interchange of USENET Messages, was badly in need of repair. This "Internet-Draft-to-be", though never formally published at that time, was widely circulated and became the de facto standard for implementors of News Servers and User Agents, rapidly acquiring the nickname "Son of 1036". Indeed, under that name, it could fairly be described as the best-known Internet Draft (n)ever published, and it formed the starting point for the recently adopted Proposed Standards for Netnews.
March 2010
Status: HISTORIC
Autor: H. Spencer
RFC1850 OSPF Version 2 Management Information Base
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Open Shortest Path First Routing Protocol. [STANDARDS-TRACK]
November 1995
Status: DRAFT STANDARD
Autor: F. Baker, R. Coltun
RFC1851 The ESP Triple DES Transform
September 1995
Status: EXPERIMENTAL
Autor: P. Karn, P. Metzger, W. Simpson
RFC1852 IP Authentication using Keyed SHA
September 1995
Status: EXPERIMENTAL
Autor: P. Metzger, W. Simpson
RFC1853 IP in IP Tunneling
This document discusses implementation techniques for using IP Protocol/Payload number 4 Encapsulation for tunneling with IP Security and other protocols. This memo provides information for the Internet community. It does not specify an Internet standard. This document describes the use of keyed SHA with the IP Authentication Header. This document defines an Experimental Protocol for the Internet community. This document describes the Triple DES-CBC security transform for the IP Encapsulating Security Payload (ESP). This document defines an Experimental Protocol for the Internet community.
October 1995
Status: INFORMATIONAL
Autor: W. Simpson
RFC1854 SMTP Service Extension for Command Pipelining
This memo defines an extension to the SMTP service whereby a server can indicate the extent of its ability to accept multiple commands in a single TCP send operation. [STANDARDS-TRACK]
October 1995
Status: PROPOSED STANDARD
Autor: N. Freed
RFC1855 Netiquette Guidelines
This document provides a minimum set of guidelines for Network Etiquette (Netiquette) which organizations may take and adapt for their own use. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1995
Status: INFORMATIONAL
Autor: S. Hambridge
RFC1856 The Opstat Client-Server Model for Statistics Retrieval
September 1995
Status: INFORMATIONAL
Autor: H. Clark
RFC1857 A Model for Common Operational Statistics
This memo describes a model for operational statistics in the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. This document defines a model and protocol for a set of tools which could be used by NSPs and Network Operation Centers (NOCs) to share data among themselves and with customers. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1995
Status: INFORMATIONAL
Autor: M. Lambert
RFC1858 Security Considerations for IP Fragment Filtering
IP fragmentation can be used to disguise TCP packets from IP filters used in routers and hosts. This document describes two methods of attack as well as remedies to prevent them. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1995
Status: INFORMATIONAL
Autor: G. Ziemba, D. Reed, P. Traina
RFC1859 ISO Transport Class 2 Non-use of Explicit Flow Control over TCP RFC1006 extension
This document is an extension to STD35, RFC1006, a standard for the Internet community. The document does not duplicate the protocol definitions contained in RFC1006 and in International Standard ISO 8073. It supplements that information with the description of how to implement ISO Transport Class 2 Non-use of Explicit Flow Control on top of TCP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1995
Status: INFORMATIONAL
Autor: Y. Pouffary
RFC1860 Variable Length Subnet Table For IPv4
This document itemizes the potential values for IPv4 subnets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1995
Status: INFORMATIONAL
Autor: T. Pummill, B. Manning
RFC1861 Simple Network Paging Protocol - Version 3 -Two-Way Enhanced
This RFC suggests a simple way for delivering wireless messages, both one and two-way, to appropriate receiving devices. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1995
Status: INFORMATIONAL
Autor: A. Gwinn
RFC1862 Report of the IAB Workshop on Internet Information Infrastructure, October 12-14, 1994
This document is a report on an Internet architecture workshop, initiated by the IAB and held at MCI on October 12-14, 1994. This workshop generally focused on aspects of the information infrastructure on the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
November 1995
Status: INFORMATIONAL
Autor: M. McCahill, J. Romkey, M. Schwartz, K. Sollins, T. Verschuren, C. Weider
RFC1863 A BGP/IDRP Route Server alternative to a full mesh routing
This document describes the use and detailed design of Route Servers for dissemination of routing information among BGP/IDRP speaking routers. This memo defines an Experimental Protocol for the Internet community.
October 1995
Status: HISTORIC
Autor: D. Haskin
RFC1864 The Content-MD5 Header Field
This memo specifies an optional header field, Content-MD5, for use with MIME-conformant messages. [STANDARDS-TRACK]
October 1995
Status: DRAFT STANDARD
Autor: J. Myers, M. Rose
RFC1865 EDI Meets the Internet Frequently Asked Questions about Electronic Data Interchange (EDI) on the Internet
This memo is targeted towards the EDI community that is unfamiliar with the Internet, including EDI software developers, users, and service providers. The memo introduces the Internet and assumes a basic knowledge of EDI. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
January 1996
Status: INFORMATIONAL
Autor: W. Houser, J. Griffin, C. Hage
RFC1866 Hypertext Markup Language - 2.0
This document defines a HTML 2.0 (to distinguish it from the previous informal specifications). [STANDARDS-TRACK]
November 1995
Status: HISTORIC
Autor: T. Berners-Lee, D. Connolly
RFC1867 Form-based File Upload in HTML
Since file-upload is a feature that will benefit many applications, this proposes an extension to HTML to allow information providers to express file upload requests uniformly, and a MIME compatible representation for file upload responses. This memo defines an Experimental Protocol for the Internet community.
November 1995
Status: HISTORIC
Autor: E. Nebel, L. Masinter
RFC1868 ARP Extension - UNARP
This document specifies a trivial modification to the ARP mechanism, not the packet format, which allows a node to announce that it is leaving the network and that all other nodes should modify their ARP tables accordingly. This memo defines an Experimental Protocol for the Internet community.
November 1995
Status: EXPERIMENTAL
Autor: G. Malkin
RFC1869 SMTP Service Extensions
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]
November 1995
Status: STANDARD
Autor: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker
RFC1870 SMTP Service Extension for Message Size Declaration
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]
November 1995
Status: STANDARD
Autor: J. Klensin, N. Freed, K. Moore
RFC1871 Addendum to RFC 1602 -- Variance Procedure
This document describes a modification to the IETF procedures to allow an escape from a situation where the existing procedures are not working or do not seem to apply. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
November 1995
Status: HISTORIC
Autor: J. Postel
RFC1872 The MIME Multipart/Related Content-type
The Multipart/Related content-type provides a common mechanism for representing objects that are aggregates of related MIME body parts. This document defines the Multipart/Related content-type and provides examples of its use. This memo defines an Experimental Protocol for the Internet community.
December 1995
Status: EXPERIMENTAL
Autor: E. Levinson
RFC1873 Message/External-Body Content-ID Access Type
The existing MIME Content-Type Message/External-Body access-types allow a MIME entity (body-part) to refer to an object that is not in the message by specifying how to access that object. The Content-ID access method described in this document provides the capability to refer to an object within the message. This memo defines an Experimental Protocol for the Internet community.
December 1995
Status: EXPERIMENTAL
Autor: E. Levinson
RFC1874 SGML Media Types
This document proposes new media sub-types of Text/SGML and Application/SGML. This memo defines an Experimental Protocol for the Internet community.
December 1995
Status: EXPERIMENTAL
Autor: E. Levinson
RFC1875 UNINETT PCA Policy Statements
This document provides information about policy statements submitted by the UNINETT Policy Certification Authority (UNINETT PCA). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1995
Status: INFORMATIONAL
Autor: N. Berge
RFC1876 A Means for Expressing Location Information in the Domain Name System
This memo defines a new DNS RR type for experimental purposes. This RFC describes a mechanism to allow the DNS to carry location information about hosts, networks, and subnets. This memo defines an Experimental Protocol for the Internet community.
January 1996
Status: EXPERIMENTAL
Autor: C. Davis, P. Vixie, T. Goodwin, I. Dickinson
RFC1877 PPP Internet Protocol Control Protocol Extensions for Name Server Addresses
This document extends the NCP for establishing and configuring the Internet Protocol over PPP [2], defining the negotiation of primary and secondary Domain Name System (DNS) [3] and NetBIOS Name Server (NBNS) [4] addresses. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1995
Status: INFORMATIONAL
Autor: S. Cobb
RFC1878 Variable Length Subnet Table For IPv4
This memo clarifies issues surrounding subnetting IP networks by providing a standard subnet table. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1995
Status: HISTORIC
Autor: T. Pummill, B. Manning
RFC1879 Class A Subnet Experiment Results and Recommendations
This memo documents some experiences with the RFC 1797 [1] subnet A experiment (performed by the Net39 Test Group (see credits)) and provides a number of recommendations on future direction for both the Internet Registries and the Operations community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
January 1996
Status: INFORMATIONAL
Autor: B. Manning
RFC1880 Internet Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
November 1995
Status: HISTORIC
Autor: J. Postel
RFC1881 IPv6 Address Allocation Management
The IPv6 address space will be managed by the IANA for the good of the Internet community, with advice from the IAB and the IESG, by delegation to the regional registries. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1995
Status: INFORMATIONAL
Autor: IAB, IESG
RFC1882 The 12-Days of Technology Before Christmas
This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1995
Status: INFORMATIONAL
Autor: B. Hancock
RFC1883 Internet Protocol, Version 6 (IPv6) Specification
This document specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng. [STANDARDS-TRACK]
December 1995
Status: PROPOSED STANDARD
Autor: S. Deering, R. Hinden
RFC1884 IP Version 6 Addressing Architecture
This specification defines the addressing architecture of the IP Version 6 protocol [IPV6]. [STANDARDS-TRACK]
December 1995
Status: HISTORIC
Autor: R. Hinden, S. Deering
RFC1885 Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6)
This document specifies a set of Internet Control Message Protocol (ICMP) messages for use with version 6 of the Internet Protocol (IPv6). [STANDARDS-TRACK]
December 1995
Status: PROPOSED STANDARD
Autor: A. Conta, S. Deering
RFC1886 DNS Extensions to support IP version 6
This document defines the changes that need to be made to the Domain Name System to support hosts running IP version 6 (IPv6). [STANDARDS-TRACK]
December 1995
Status: PROPOSED STANDARD
Autor: S. Thomson, C. Huitema
RFC1887 An Architecture for IPv6 Unicast Address Allocation
This document provides an architecture for allocating IPv6 [1] unicast addresses in the Internet. This document provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1995
Status: INFORMATIONAL
Autor: Y. Rekhter, T. Li
RFC1888 OSI NSAPs and IPv6
This document recommends that network implementors who have planned or deployed an OSI NSAP addressing plan, and who wish to deploy or transition to IPv6, should redesign a native IPv6 addressing plan to meet their needs. This memo defines an Experimental Protocol for the Internet community.
August 1996
Status: HISTORIC
Autor: J. Bound, B. Carpenter, D. Harrington, J. Houldsworth, A. Lloyd
RFC1889 RTP: A Transport Protocol for Real-Time Applications
This memorandum describes RTP, the real-time transport protocol. RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services. [STANDARDS-TRACK]
January 1996
Status: PROPOSED STANDARD
Autor: Audio-Video Transport Working Group, H. Schulzrinne, S. Casner, R. Frederick, V. Jacobson
RFC1890 RTP Profile for Audio and Video Conferences with Minimal Control
This memo describes a profile for the use of the real-time transport protocol (RTP), version 2, and the associated control protocol, RTCP, within audio and video multiparticipant conferences with minimal control. [STANDARDS-TRACK]
January 1996
Status: PROPOSED STANDARD
Autor: Audio-Video Transport Working Group, H. Schulzrinne
RFC1891 SMTP Service Extension for Delivery Status Notifications
This memo defines an extension to the SMTP service, which allows an SMTP client to specify (a) that delivery status notifications (DSNs) should be generated under certain conditions, (b) whether such notifications should return the contents of the message, and (c) additional information, to be returned with a DSN, that allows the sender to identify both the recipient(s) for which the DSN was issued, and the transaction in which the original message was sent. [STANDARDS-TRACK]
January 1996
Status: PROPOSED STANDARD
Autor: K. Moore
RFC1892 The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages
The Multipart/Report MIME content-type is a general "family" or "container" type for electronic mail reports of any kind. Although this memo defines only the use of the Multipart/Report content-type with respect to delivery status reports, mail processing programs will benefit if a single content-type is used to for all kinds of reports. [STANDARDS-TRACK]
January 1996
Status: PROPOSED STANDARD
Autor: G. Vaudreuil
RFC1893 Enhanced Mail System Status Codes
There currently is not a standard mechanism for the reporting of mail system errors except for the limited set offered by SMTP and the system specific text descriptions sent in mail messages. There is a pressing need for a rich machine readable status code for use in delivery status notifications [DSN]. This document proposes a new set of status codes for this purpose. [STANDARDS-TRACK]
January 1996
Status: PROPOSED STANDARD
Autor: G. Vaudreuil
RFC1894 An Extensible Message Format for Delivery Status Notifications
This memo defines a MIME content-type that may be used by a message transfer agent (MTA) or electronic mail gateway to report the result of an attempt to deliver a message to one or more recipients. [STANDARDS-TRACK]
January 1996
Status: PROPOSED STANDARD
Autor: K. Moore, G. Vaudreuil
RFC1895 The Application/CALS-1840 Content-type
This memorandum provides guidelines for using the United States Department of Defense Military Standard MIL-STD-1840, "Automated Interchange of Technical Information," with the Internet electronic mail standards, RFC 822 and RFC 1521. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1996
Status: INFORMATIONAL
Autor: E. Levinson
RFC1896 The text/enriched MIME Content-type
This document defines one particular type of MIME data, the text/enriched MIME type. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1996
Status: INFORMATIONAL
Autor: P. Resnick, A. Walker
RFC1897 IPv6 Testing Address Allocation
This document describes an allocation plan for IPv6 addresses to be used in testing IPv6 prototype software. This document specifies an Experimental protocol for the Internet community.
January 1996
Status: EXPERIMENTAL
Autor: R. Hinden, J. Postel
RFC1898 CyberCash Credit Card Protocol Version 0.8
This document covers only the current CyberCash system which is one of the few operational systems in the rapidly evolving area of Internet payments. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1996
Status: INFORMATIONAL
Autor: D. Eastlake 3rd, B. Boesch, S. Crocker, M. Yesil
RFC1899 Request for Comments Summary RFC Numbers 1800-1899
January 1997
Status: INFORMATIONAL
Autor: J. Elliott
RFC1900 Renumbering Needs Work
Hosts in an IP network are identified by IP addresses, and the IP address prefixes of subnets are advertised by routing protocols. A change in such IP addressing information associated with a host or subnet is known as "renumbering". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1996
Status: INFORMATIONAL
Autor: B. Carpenter, Y. Rekhter
RFC1901 Introduction to Community-based SNMPv2
The purpose of this document is to define the Community-based Administrative Framework for the SNMP version 2 framework (SNMPv2). This document specifies an Experimental protocol for the Internet community.
January 1996
Status: HISTORIC
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1902 Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document, the Structure of Management Information (SMI), to define that adapted subset, and to assign a set of associated administrative values. [STANDARDS-TRACK]
January 1996
Status: DRAFT STANDARD
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1903 Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK]
January 1996
Status: DRAFT STANDARD
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1904 Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)
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]
January 1996
Status: DRAFT STANDARD
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1905 Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)
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]
January 1996
Status: DRAFT STANDARD
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1906 Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document to define how the SNMPv2 maps onto an initial set of transport domains. [STANDARDS-TRACK]
January 1996
Status: DRAFT STANDARD
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1907 Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity. [STANDARDS-TRACK]
January 1996
Status: DRAFT STANDARD
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1908 Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework
The purpose of this document is to describe coexistence between version 2 of the Internet-standard Network Management Framework [1-6], termed the SNMP version 2 framework (SNMPv2), and the original Internet- standard Network Management Framework (SNMPv1). [STANDARDS-TRACK]
January 1996
Status: DRAFT STANDARD
Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser
RFC1909 An Administrative Infrastructure for SNMPv2
It is the purpose of this document, An Administrative Infrastructure for SNMPv2, to define an administrative framework which realizes effective management in a variety of configurations and environments. This memo defines an Experimental Protocol for the Internet community.
February 1996
Status: HISTORIC
Autor: K. McCloghrie
RFC1910 User-based Security Model for SNMPv2
In this administrative framework, a security model defines the mechanisms used to achieve an administratively-defined level of security for protocol interactions. Although many such security models might be defined, it is the purpose of this document, User-based Security Model for SNMPv2, to define the first, and, as of this writing, only, security model for this administrative framework. This memo defines an Experimental Protocol for the Internet community.
February 1996
Status: HISTORIC
Autor: G. Waters
RFC1911 Voice Profile for Internet Mail
The following document is a profile of the Internet standard MIME and ESMTP protocols for use as a digital voice networking protocol. This memo defines an Experimental Protocol for the Internet community.
February 1996
Status: EXPERIMENTAL
Autor: G. Vaudreuil
RFC1912 Common DNS Operational and Configuration Errors
This memo describes errors often found in both the operation of Domain Name System (DNS) servers, and in the data that these DNS servers contain. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1996
Status: INFORMATIONAL
Autor: D. Barr
RFC1913 Architecture of the Whois++ Index Service
The authors describe an architecture for indexing in distributed databases, and apply this to the WHOIS++ protocol. [STANDARDS-TRACK]
February 1996
Status: HISTORIC
Autor: C. Weider, J. Fullton, S. Spero
RFC1914 How to Interact with a Whois++ Mesh
In the Whois++ architecture [Deutsch94],[Weider94], mesh traversal is done by the client, since each server 'refers' the client to the next appropriate server(s). [STANDARDS-TRACK]
February 1996
Status: HISTORIC
Autor: P. Faltstrom, R. Schoultz, C. Weider
RFC1915 Variance for The PPP Compression Control Protocol and The PPP Encryption Control Protocol
The PPP Working group has developed two protocols, one to control compression on PPP links; the Compression Control Protocol (CCP), documented in draft-ietf-pppext-compression-04.txt. The second is the Encryption Control Protocol (ECP), used to control encryption on serial links, documented in draft-ietf-pppext-encryption-03.txt. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
February 1996
Status: BEST CURRENT PRACTICE
Autor: F. Kastenholz
RFC1916 Enterprise Renumbering: Experience and Information Solicitation
Because of the urgent need for, and substantial difficulty in, renumbering IP networks, the PIER working group is compiling a series of documents to assist sites in their renumbering efforts. The intent of these documents is to provide both educational and practical information to the Internet community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1996
Status: INFORMATIONAL
Autor: H. Berkowitz, P. Ferguson, W. Leland, P. Nesser
RFC1917 An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANA
This document is an appeal to the Internet community to return unused address space, i.e. any block of consecutive IP prefixes, to the Internet Assigned Numbers Authority (IANA) or any of the delegated registries, for reapportionment. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
February 1996
Status: BEST CURRENT PRACTICE
Autor: P. Nesser II
RFC1918 Address Allocation for Private Internets
This document describes address allocation for private internets. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
February 1996
Status: BEST CURRENT PRACTICE
Autor: Y. Rekhter, B. Moskowitz, D. Karrenberg, G. J. de Groot, E. Lear
RFC1919 Classical versus Transparent IP Proxies
This document explains "classical" and "transparent" proxy techniques and attempts to provide rules to help determine when each proxy system may be used without causing problems. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1996
Status: INFORMATIONAL
Autor: M. Chatel
RFC1920 Internet Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
March 1996
Status: HISTORIC
Autor: J. Postel
RFC1921 TNVIP Protocol
The goal of this document specifies a Telnet profile to support VIP terminal emulation allowing the access to the BULL hosts applications through a TCP/IP network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1996
Status: INFORMATIONAL
Autor: J. Dujonc
RFC1922 Chinese Character Encoding for Internet Messages
This memo describes methods of transporting Chinese characters in Internet services which transport text, such as electronic mail [RFC-822], network news [RFC-1036], telnet [RFC-854] and the World Wide Web [RFC-1866]. This memo provides information for the Internet community. It does not specify an Internet standard.
March 1996
Status: INFORMATIONAL
Autor: HF. Zhu, DY. Hu, ZG. Wang, TC. Kao, WCH. Chang, M. Crispin
RFC1923 RIPv1 Applicability Statement for Historic Status
RIP Version 1 [RFC-1058] has been declared an historic document. This Applicability statement provides the supporting motivation for that declaration. The primary reason, as described below, is the Classful nature of RIPv1. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1996
Status: INFORMATIONAL
Autor: J. Halpern, S. Bradner
RFC1924 A Compact Representation of IPv6 Addresses
This document specifies a more compact representation of IPv6 addresses, which permits encoding in a mere 20 bytes. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1996
Status: INFORMATIONAL
Autor: R. Elz
RFC1925 The Twelve Networking Truths
This memo documents the fundamental truths of networking for the Internet community. This memo does not specify a standard, except in the sense that all standards must implicitly follow the fundamental truths. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1996
Status: INFORMATIONAL
Autor: R. Callon
RFC1926 An Experimental Encapsulation of IP Datagrams on Top of ATM
This RFC describes a method of encapsulating IP datagrams on top of Acoustical Transmission Media (ATM). This is a non-recommended standard. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1996
Status: INFORMATIONAL
Autor: J. Eriksson
RFC1927 Suggested Additional MIME Types for Associating Documents
Seven new types of MIME types are suggested in this document. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1996
Status: INFORMATIONAL
Autor: C. Rogers
RFC1928 SOCKS Protocol Version 5
This memo describes a protocol that is an evolution of the previous version of the protocol, version 4 [1]. This new protocol stems from active discussions and prototype implementations. [STANDARDS-TRACK]
March 1996
Status: PROPOSED STANDARD
Autor: M. Leech, M. Ganis, Y. Lee, R. Kuris, D. Koblas, L. Jones
RFC1929 Username/Password Authentication for SOCKS V5
The protocol specification for SOCKS Version 5 specifies a generalized framework for the use of arbitrary authentication protocols in the initial socks connection setup. This document describes one of those protocols, as it fits into the SOCKS Version 5 authentication "subnegotiation". [STANDARDS-TRACK]
March 1996
Status: PROPOSED STANDARD
Autor: M. Leech
RFC1930 Guidelines for creation, selection, and registration of an Autonomous System (AS)
This memo discusses when it is appropriate to register and utilize an Autonomous System (AS), and lists criteria for such. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
March 1996
Status: BEST CURRENT PRACTICE
Autor: J. Hawkinson, T. Bates
RFC1931 Dynamic RARP Extensions for Automatic Network Address Acquisition
This memo describes extensions to the Reverse Address Resolution Protocol (RARP [2]) and called Dynamic RARP (DRARP, pronounced D-RARP). This memo provides information for the Internet community. This memo does not define an Internet standard of any kind.
April 1996
Status: INFORMATIONAL
Autor: D. Brownell
RFC1932 IP over ATM: A Framework Document
It is hoped that this document, in classifying ATM approaches and issues will help to focus the IP over ATM working group's direction.This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1996
Status: INFORMATIONAL
Autor: R. Cole, D. Shur, C. Villamizar
RFC1933 Transition Mechanisms for IPv6 Hosts and Routers
This document specifies IPv4 compatibility mechanisms that can be implemented by IPv6 hosts and routers. [STANDARDS-TRACK]
April 1996
Status: PROPOSED STANDARD
Autor: R. Gilligan, E. Nordmark
RFC1934 Ascend's Multilink Protocol Plus (MP+)
This document proposes an extension to the PPP Multilink Protocol (MP) [1]. Multilink Protocol Plus (MP+) is a new control protocol for managing multiple data links that are bundled by MP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1996
Status: INFORMATIONAL
Autor: K. Smith
RFC1935 What is the Internet, Anyway?
This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1996
Status: INFORMATIONAL
Autor: J. Quarterman, S. Carl-Mitchell
RFC1936 Implementing the Internet Checksum in Hardware
This memo presents a techniques for efficiently implementing the Internet Checksum in hardware. It includes PLD code for programming a single, low cost part to perform checksumming at 1.26 Gbps. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1996
Status: INFORMATIONAL
Autor: J. Touch, B. Parham
RFC1937 "Local/Remote" Forwarding Decision in Switched Data Link Subnetworks
This document describes extensions to the IP architecture that relaxes these constraints, thus enabling the full utilization of the services provided by SVC-based Data Link subnetworks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1996
Status: INFORMATIONAL
Autor: Y. Rekhter, D. Kandlur
RFC1938 A One-Time Password System
This document describes a one-time password authentication system (OTP). [STANDARDS-TRACK]
May 1996
Status: PROPOSED STANDARD
Autor: N. Haller, C. Metz
RFC1939 Post Office Protocol - Version 3
The Post Office Protocol - Version 3 (POP3) is intended to permit a workstation to dynamically access a maildrop on a server host in a useful fashion. [STANDARDS-TRACK]
May 1996
Status: STANDARD
Autor: J. Myers, M. Rose
RFC1940 Source Demand Routing: Packet Format and Forwarding Specification (Version 1)
The purpose of SDRP is to support source-initiated selection of routes to complement the route selection provided by existing routing protocols for both inter-domain and intra-domain routes. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1996
Status: INFORMATIONAL
Autor: D. Estrin, T. Li, Y. Rekhter, K. Varadhan, D. Zappala
RFC1941 Frequently Asked Questions for Schools
The goal of this FYI document, produced by the Internet School Networking (ISN) group in the User Services Area of the Internet Engineering Task Force (IETF), is to act as an introduction to the Internet for faculty, administration, and other school personnel in primary and secondary schools. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1996
Status: INFORMATIONAL
Autor: J. Sellers, J. Robichaux
RFC1942 HTML Tables
This specification extends HTML to support a wide variety of tables. This memo defines an Experimental Protocol for the Internet community.
May 1996
Status: HISTORIC
Autor: D. Raggett
RFC1943 Building an X.500 Directory Service in the US
This document provides definition and recommends considerations that must be undertaken to operate a X.500 Directory Service in the United States. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1996
Status: INFORMATIONAL
Autor: B. Jennings
RFC1944 Benchmarking Methodology for Network Interconnect Devices
This document discusses and defines a number of tests that may be used to describe the performance characteristics of a network interconnecting device. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1996
Status: INFORMATIONAL
Autor: S. Bradner, J. McQuaid
RFC1945 Hypertext Transfer Protocol -- HTTP/1.0
The Hypertext Transfer Protocol (HTTP) is an application-level protocol with the lightness and speed necessary for distributed, collaborative, hypermedia information systems. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1996
Status: INFORMATIONAL
Autor: T. Berners-Lee, R. Fielding, H. Frystyk
RFC1946 Native ATM Support for ST2+
This memo describes a working implementation which enables applications to directly invoke ATM services in the following environments: ATM to internet, internet to ATM, and internet to internet across ATM. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1996
Status: INFORMATIONAL
Autor: S. Jackowski
RFC1947 Greek Character Encoding for Electronic Mail Messages
This document describes a standard encoding for electronic mail [RFC822] containing Greek text and provides implementation guide-lines. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1996
Status: INFORMATIONAL
Autor: D. Spinellis
RFC1948 Defending Against Sequence Number Attacks
IP spoofing attacks based on sequence number spoofing have become a serious threat on the Internet (CERT Advisory CA-95:01). While ubiquitous crypgraphic authentication is the right answer, we propose a simple modification to TCP implementations that should be a very substantial block to the current wave of attacks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1996
Status: INFORMATIONAL
Autor: S. Bellovin
RFC1949 Scalable Multicast Key Distribution
This memo provides a scalable solution to the multicast key distribution problem. This memo defines an Experimental Protocol for the Internet community.
May 1996
Status: EXPERIMENTAL
Autor: A. Ballardie
RFC1950 ZLIB Compressed Data Format Specification version 3.3
This specification defines a lossless compressed data format. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1996
Status: INFORMATIONAL
Autor: P. Deutsch, J-L. Gailly
RFC1951 DEFLATE Compressed Data Format Specification version 1.3
This specification defines a lossless compressed data format that compresses data using a combination of the LZ77 algorithm and Huffman coding, with efficiency comparable to the best currently available general-purpose compression methods. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1996
Status: INFORMATIONAL
Autor: P. Deutsch
RFC1952 GZIP file format specification version 4.3
This specification defines a lossless compressed data format that is compatible with the widely used GZIP utility. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1996
Status: INFORMATIONAL
Autor: P. Deutsch
RFC1953 Ipsilon Flow Management Protocol Specification for IPv4 Version 1.0
The Ipsilon Flow Management Protocol (IFMP), is a protocol for allowing a node to instruct an adjacent node to attach a layer 2 label to a specified IP flow. This document provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1996
Status: INFORMATIONAL
Autor: P. Newman, W. Edwards, R. Hinden, E. Hoffman, F. Ching Liaw, T. Lyon, G. Minshall
RFC1954 Transmission of Flow Labelled IPv4 on ATM Data Links Ipsilon Version 1.0
This document specifies the manner for transmitting IPv4 datagrams over an ATM data link, both in a default manner and in the presence of flow labelling via Ipsilon Flow Management Protocol [IFMP]. This document provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1996
Status: INFORMATIONAL
Autor: P. Newman, W. Edwards, R. Hinden, E. Hoffman, F. Ching Liaw, T. Lyon, G. Minshall
RFC1955 New Scheme for Internet Routing and Addressing (ENCAPS) for IPNG
This paper proposes a new scheme which I believe is a good medium term solution to the routing and address problems of the internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1996
Status: INFORMATIONAL
Autor: R. Hinden
RFC1956 Registration in the MIL Domain
This RFC describes the policy for the registration of second level domains under the ".MIL" domain. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1996
Status: INFORMATIONAL
Autor: D. Engebretson, R. Plzak
RFC1957 Some Observations on Implementations of the Post Office Protocol (POP3)
This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1996
Status: INFORMATIONAL
Autor: R. Nelson
RFC1958 Architectural Principles of the Internet
The Internet and its architecture have grown in evolutionary fashion from modest beginnings, rather than from a Grand Plan. While this process of evolution is one of the main reasons for the technology's success, it nevertheless seems useful to record a snapshot of the current principles of the Internet architecture. This is intended for general guidance and general interest, and is in no way intended to be a formal or invariant reference model. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1996
Status: INFORMATIONAL
Autor: B. Carpenter
RFC1959 An LDAP URL Format
This document describes a format for an LDAP Uniform Resource Locator which will allow Internet clients to have direct access to the LDAP protocol. [STANDARDS-TRACK]
June 1996
Status: PROPOSED STANDARD
Autor: T. Howes, M. Smith
RFC1960 A String Representation of LDAP Search Filters
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. [STANDARDS-TRACK]
June 1996
Status: PROPOSED STANDARD
Autor: T. Howes
RFC1961 GSS-API Authentication Method for SOCKS Version 5
This document provides the specification for the SOCKS V5 GSS-API authentication protocol, and defines a GSS-API-based encapsulation for provision of integrity, authentication and optional confidentiality. [STANDARDS-TRACK]
June 1996
Status: PROPOSED STANDARD
Autor: P. McMahon
RFC1962 The PPP Compression Control Protocol (CCP)
This document defines a method for negotiating data compression over PPP links. [STANDARDS-TRACK]
June 1996
Status: PROPOSED STANDARD
Autor: D. Rand
RFC1963 PPP Serial Data Transport Protocol (SDTP)
This document describes a new Network level protocol (from the PPP point of view), PPP Serial Data Transport Protocol, that provides encapsulation and an associated control protocol for transporting serial data streams over a PPP link. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1996
Status: INFORMATIONAL
Autor: K. Schneider, S. Venters
RFC1964 The Kerberos Version 5 GSS-API Mechanism
This specification defines protocols, procedures, and conventions to be employed by peers implementing the Generic Security Service Application Program Interface (as specified in RFCs 1508 and 1509) when using Kerberos Version 5 technology (as specified in RFC 1510). [STANDARDS-TRACK]
June 1996
Status: PROPOSED STANDARD
Autor: J. Linn
RFC1965 Autonomous System Confederations for BGP
This document describes an extension to BGP which may be used to create a confederation of autonomous systems which is represented as one single autonomous system to BGP peers external to the confederation. This memo defines an Experimental Protocol for the Internet community.
June 1996
Status: EXPERIMENTAL
Autor: P. Traina
RFC1966 BGP Route Reflection An alternative to full mesh IBGP
This document describes the use and design of a method known as "Route Reflection" to alleviate the the need for "full mesh" IBGP. This memo defines an Experimental Protocol for the Internet community.
June 1996
Status: EXPERIMENTAL
Autor: T. Bates, R. Chandra
RFC1967 PPP LZS-DCP Compression Protocol (LZS-DCP)
This document describes the use of the Stac LZS data compression algorithm for compressing PPP encapsulated packets, using a DCP header [6]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1996
Status: INFORMATIONAL
Autor: K. Schneider, R. Friend
RFC1968 The PPP Encryption Control Protocol (ECP)
This document defines a method for negotiating data encryption over PPP links. [STANDARDS-TRACK]
June 1996
Status: PROPOSED STANDARD
Autor: G. Meyer
RFC1969 The PPP DES Encryption Protocol (DESE)
This document provides specific details for the use of the DES standard [5, 6] for encrypting PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1996
Status: INFORMATIONAL
Autor: K. Sklower, G. Meyer
RFC1970 Neighbor Discovery for IP Version 6 (IPv6)
This document specifies the Neighbor Discovery protocol for IP Version 6. [STANDARDS-TRACK]
August 1996
Status: PROPOSED STANDARD
Autor: T. Narten, E. Nordmark, W. Simpson
RFC1971 IPv6 Stateless Address Autoconfiguration
This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. [STANDARDS-TRACK]
August 1996
Status: PROPOSED STANDARD
Autor: S. Thomson, T. Narten
RFC1972 A Method for the Transmission of IPv6 Packets over Ethernet Networks
This memo specifies the frame format for transmission of IPv6 [IPV6] packets and the method of forming IPv6 link-local addresses on Ethernet networks. [STANDARDS-TRACK]
August 1996
Status: PROPOSED STANDARD
Autor: M. Crawford
RFC1973 PPP in Frame Relay
This document describes the use of Frame Relay for framing PPP encapsulated packets. [STANDARDS-TRACK]
June 1996
Status: PROPOSED STANDARD
Autor: W. Simpson
RFC1974 PPP Stac LZS Compression Protocol
This document describes the use of the Stac LZS data compression algorithm, with single or multiple compression histories, for compressing PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1996
Status: INFORMATIONAL
Autor: R. Friend, W. Simpson
RFC1975 PPP Magnalink Variable Resource Compression
The Magnalink Variable Resource Compression Algorithm (MVRCA) allows a wide range of interoperable compression implementations whose performance characteristics are a function of available CPU and memory resources. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1996
Status: INFORMATIONAL
Autor: D. Schremp, J. Black, J. Weiss
RFC1976 PPP for Data Compression in Data Circuit-Terminating Equipment (DCE)
This document defines a specific set of parameters for these protocols and an LCP extension to define a standard way of using PPP for data compression of serial data in Data Circuit-Terminating Equipment (DCE). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1996
Status: INFORMATIONAL
Autor: K. Schneider, S. Venters
RFC1977 PPP BSD Compression Protocol
This document describes the use of the Unix Compress compression protocol for compressing PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1996
Status: INFORMATIONAL
Autor: V. Schryver
RFC1978 PPP Predictor Compression Protocol
This document describes the use of the Predictor data compression algorithm for compressing PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1996
Status: INFORMATIONAL
Autor: D. Rand
RFC1979 PPP Deflate Protocol
This document describes the use of the PPP Deflate compression protocol for compressing PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1996
Status: INFORMATIONAL
Autor: J. Woods
RFC1980 A Proposed Extension to HTML : Client-Side Image Maps
This document specifies an extension to the HTML language, referred to as "Client-Side Image Maps," which resolves some limitations. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1996
Status: HISTORIC
Autor: J. Seidman
RFC1981 Path MTU Discovery for IP version 6
This document describes Path MTU Discovery for IP version 6. It is largely derived from RFC 1191, which describes Path MTU Discovery for IP version 4. [STANDARDS-TRACK]
August 1996
Status: DRAFT STANDARD
Autor: J. McCann, S. Deering, J. Mogul
RFC1982 Serial Number Arithmetic
The DNS has long relied upon serial number arithmetic, a concept which has never really been defined, certainly not in an IETF document, though which has been widely understood. This memo supplies the missing definition. It is intended to update RFC1034 and RFC1035. [STANDARDS-TRACK]
August 1996
Status: PROPOSED STANDARD
Autor: R. Elz, R. Bush
RFC1983 Internet Users' Glossary
There are many networking glossaries in existence. This glossary concentrates on terms which are specific to the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1996
Status: INFORMATIONAL
Autor: G. Malkin
RFC1984 IAB and IESG Statement on Cryptographic Technology and the Internet
The Internet Architecture Board (IAB) and the Internet Engineering Steering Group (IESG), the bodies which oversee architecture and standards for the Internet, are concerned by the need for increased protection of international commercial transactions on the Internet, and by the need to offer all Internet users an adequate degree of privacy. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1996
Status: INFORMATIONAL
Autor: IAB, IESG
RFC1985 SMTP Service Extension for Remote Message Queue Starting
This memo defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to start the processing of its queues for messages to go to a given host. [STANDARDS-TRACK]
August 1996
Status: PROPOSED STANDARD
Autor: J. De Winter
RFC1986 Experiments with a Simple File Transfer Protocol for Radio Links using Enhanced Trivial File Transfer Protocol (ETFTP)
This document is a description of the Enhanced Trivial File Transfer Protocol (ETFTP). This protocol is an experimental implementation of the NETwork BLock Transfer Protocol (NETBLT), RFC 998 [1], as a file transfer application program. This memo defines an Experimental Protocol for the Internet community.
August 1996
Status: EXPERIMENTAL
Autor: W. Polites, W. Wollman, D. Woo, R. Langan
RFC1987 Ipsilon's General Switch Management Protocol Specification Version 1.1
The General Switch Management Protocol (GSMP), is a general purpose protocol to control an ATM switch. GSMP allows a controller to establish and release connections across the switch; add and delete leaves on a point-to-multipoint connection; manage switch ports; request configuration information; and request statistics. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1996
Status: INFORMATIONAL
Autor: P. Newman, W. Edwards, R. Hinden, E. Hoffman, F. Ching Liaw, T. Lyon, G. Minshall
RFC1988 Conditional Grant of Rights to Specific Hewlett-Packard Patents In Conjunction With the Internet Engineering Task Force's Internet-Standard Network Management Framework
This grant is made to help facilitate inclusion of certain patented search address technology covering network device mapping in IETF standards-track Management Information Base (MIB) modules. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1996
Status: INFORMATIONAL
Autor: G. McAnally, D. Gilbert, J. Flick
RFC1989 PPP Link Quality Monitoring
This document defines a protocol for generating Link-Quality-Reports. [STANDARDS-TRACK]
August 1996
Status: DRAFT STANDARD
Autor: W. Simpson
RFC1990 The PPP Multilink Protocol (MP)
This document proposes a method for splitting, recombining and sequencing datagrams across multiple logical data links. [STANDARDS-TRACK]
August 1996
Status: DRAFT STANDARD
Autor: K. Sklower, B. Lloyd, G. McGregor, D. Carr, T. Coradetti
RFC1991 PGP Message Exchange Formats
This document describes the format of "PGP files", i.e., messages that have been encrypted and/or signed with PGP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1996
Status: INFORMATIONAL
Autor: D. Atkins, W. Stallings, P. Zimmermann
RFC1992 The Nimrod Routing Architecture
Nimrod is a scalable routing architecture designed to accommodate a continually expanding and diversifying internetwork. First suggested by Noel Chiappa, the Nimrod architecture has undergone revision and refinement through the efforts of the Nimrod working group of the IETF. In this document, we present a detailed description of this architecture. This memo provides information for the Internet community. It does not specify an Internet standard.
August 1996
Status: INFORMATIONAL
Autor: I. Castineyra, N. Chiappa, M. Steenstrup
RFC1993 PPP Gandalf FZA Compression Protocol
This document describes the use of the Gandalf FZA data compression algorithm [3] for compressing PPP encapsulated packets. This memo provides information for the Internet community. It does not specify an Internet standard.
August 1996
Status: INFORMATIONAL
Autor: A. Barbir, D. Carr, W. Simpson
RFC1994 PPP Challenge Handshake Authentication Protocol (CHAP)
This document defines a method for Authentication using PPP, which uses a random Challenge, with a cryptographically hashed Response which depends upon the Challenge and a secret key. [STANDARDS-TRACK]
August 1996
Status: DRAFT STANDARD
Autor: W. Simpson
RFC1995 Incremental Zone Transfer in DNS
This document proposes extensions to the DNS protocols to provide an incremental zone transfer (IXFR) mechanism. [STANDARDS-TRACK]
August 1996
Status: PROPOSED STANDARD
Autor: M. Ohta
RFC1996 A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY)
This memo describes the NOTIFY opcode for DNS, by which a master server advises a set of slave servers that the master's data has been changed and that a query should be initiated to discover the new data. [STANDARDS-TRACK]
August 1996
Status: PROPOSED STANDARD
Autor: P. Vixie
RFC1997 BGP Communities Attribute
This document describes an extension to BGP which may be used to pass additional information to both neighboring and remote BGP peers. [STANDARDS-TRACK]
August 1996
Status: PROPOSED STANDARD
Autor: R. Chandra, P. Traina, T. Li
RFC1998 An Application of the BGP Community Attribute in Multi-home Routing
This document presents an application of the BGP community attribute [2] in simplifying the implementation and configuration of routing policies in the multi-provider Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
August 1996
Status: INFORMATIONAL
Autor: E. Chen, T. Bates
RFC1999 Request for Comments Summary RFC Numbers 1900-1999
January 1997
Status: INFORMATIONAL
Autor: J. Elliott
RFC2000 Internet Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). This memo is an Internet Standard.
February 1997
Status: HISTORIC
Autor: J. Postel
RFC2001 TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms
Modern implementations of TCP contain four intertwined algorithms that have never been fully documented as Internet standards: slow start, congestion avoidance, fast retransmit, and fast recovery. [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: W. Stevens
RFC2002 IP Mobility Support
This document specifies protocol enhancements that allow transparent routing of IP datagrams to mobile nodes in the Internet. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: C. Perkins
RFC2003 IP Encapsulation within IP
This document specifies a method by which an IP datagram may be encapsulated (carried as payload) within an IP datagram. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: C. Perkins
RFC2004 Minimal Encapsulation within IP
This document specifies a method by which an IP datagram may be encapsulated (carried as payload) within an IP datagram, with less overhead than "conventional" IP encapsulation that adds a second IP header to each encapsulated datagram. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: C. Perkins
RFC2005 Applicability Statement for IP Mobility Support
As required by [RFC 1264], this report discusses the applicability of Mobile IP to provide host mobility in the Internet. In particular, this document describes the key features of Mobile IP and shows how the requirements for advancement to Proposed Standard RFC have been satisfied. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: J. Solomon
RFC2006 The Definitions of Managed Objects for IP Mobility Support using SMIv2
This memo defines 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 Mobile Node, Foreign Agent and Home Agent of the Mobile IP Protocol. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: D. Cong, M. Hamlen, C. Perkins
RFC2007 Catalogue of Network Training Materials
The purpose of this document is to provide a catalogue of quality Network Training Materials for use by Internet trainers in training their users. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1996
Status: INFORMATIONAL
Autor: J. Foster, M. Isaacs, M. Prior
RFC2008 Implications of Various Address Allocation Policies for Internet Routing
The purpose of this document is to articulate certain relevant fundamental technical issues that must be considered in formulating unicast address allocation and management policies for the Public Internet, and to provide recommendations with respect to these policies. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
October 1996
Status: BEST CURRENT PRACTICE
Autor: Y. Rekhter, T. Li
RFC2009 GPS-Based Addressing and Routing
This document describes a possible experiment with geographic addresses. It uses several specific IP addresses and domain names in the discussion as concrete examples to aid in understanding the concepts. This memo defines an Experimental Protocol for the Internet community.
November 1996
Status: EXPERIMENTAL
Autor: T. Imielinski, J. Navas
RFC2010 Operational Criteria for Root Name Servers
This document specifies the operational requirements of root name servers, including host hardware capacities, name server software revisions, network connectivity, and physical environment. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1996
Status: INFORMATIONAL
Autor: B. Manning, P. Vixie
RFC2011 SNMPv2 Management Information Base for the Internet Protocol using SMIv2
This document is the MIB module which defines managed objects for managing implementations of the Internet Protocol (IP) and its associated Internet Control Message Protocol (ICMP). [STANDARDS-TRACK]
November 1996
Status: PROPOSED STANDARD
Autor: K. McCloghrie
RFC2012 SNMPv2 Management Information Base for the Transmission Control Protocol using SMIv2
This document is the MIB module which defines managed objects for managing implementations of the Transmission Control Protocol (TCP). [STANDARDS-TRACK]
November 1996
Status: PROPOSED STANDARD
Autor: K. McCloghrie
RFC2013 SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2
This document is the MIB module which defines managed objects for managing implementations of the User Datagram Protocol (UDP). [STANDARDS-TRACK]
November 1996
Status: PROPOSED STANDARD
Autor: K. McCloghrie
RFC2014 IRTF Research Group Guidelines and Procedures
This document describes the guidelines and procedures for formation and operation of IRTF Research Groups. It describes the relationship between IRTF participants, Research Groups, the Internet Research Steering Group (IRSG) and the Internet Architecture Board (IAB). This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
October 1996
Status: BEST CURRENT PRACTICE
Autor: A. Weinrib, J. Postel
RFC2015 MIME Security with Pretty Good Privacy (PGP)
This document describes how Pretty Good Privacy (PGP) can be used to provide privacy and authentication using the Multipurpose Internet Mail Extensions (MIME) security content types described in RFC1847. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: M. Elkins
RFC2016 Uniform Resource Agents (URAs)
This paper presents an experimental architecture for an agent system that provides sophisticated Internet information access and management. This memo defines an Experimental Protocol for the Internet community.
October 1996
Status: EXPERIMENTAL
Autor: L. Daigle, P. Deutsch, B. Heelan, C. Alpaugh, M. Maclachlan
RFC2017 Definition of the URL MIME External-Body Access-Type
This memo defines a new access-type for message/external-body MIME parts for Uniform Resource Locators (URLs). [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: N. Freed, K. Moore, A. Cargille
RFC2018 TCP Selective Acknowledgment Options
This memo proposes an implementation of SACK and discusses its performance and related issues. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: M. Mathis, J. Mahdavi, S. Floyd, A. Romanow
RFC2019 Transmission of IPv6 Packets Over FDDI
This memo specifies the MTU and frame format for transmission of IPv6 [IPV6] packets on FDDI networks, including a method for MTU determination in the presence of 802.1d bridges to other media. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: M. Crawford
RFC2020 IEEE 802.12 Interface MIB
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 network interfaces based on IEEE 802.12. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: J. Flick
RFC2021 Remote Network Monitoring Management Information Base Version 2 using SMIv2
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]
January 1997
Status: PROPOSED STANDARD
Autor: S. Waldbusser
RFC2022 Support for Multicast over UNI 3.0/3.1 based ATM Networks
This memo describes a mechanism to support the multicast needs of Layer 3 protocols in general, and describes its application to IP multicasting in particular. [STANDARDS-TRACK]
November 1996
Status: PROPOSED STANDARD
Autor: G. Armitage
RFC2023 IP Version 6 over PPP
This document defines the method for transmission of IP Version 6 [2] packets over PPP links as well as the Network Control Protocol (NCP) for establishing and configuring the IPv6 over PPP. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: D. Haskin, E. Allen
RFC2024 Definitions of Managed Objects for Data Link Switching using SMIv2
This specification defines an extension to the Management Information Base (MIB) for use with SNMP-based network management. In particular, it defines objects for configuring, monitoring, and controlling Data Link Switches (DLSw). [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: D. Chen, P. Gayek, S. Nix
RFC2025 The Simple Public-Key GSS-API Mechanism (SPKM)
This specification defines protocols, procedures, and conventions to be employed by peers implementing the Generic Security Service Application Program Interface (as specified in RFCs 1508 and 1509) when using the Simple Public-Key Mechanism. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: C. Adams
RFC2026 The Internet Standards Process -- Revision 3
This memo documents the process used by the Internet community for the standardization of protocols and procedures. It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
October 1996
Status: BEST CURRENT PRACTICE
Autor: S. Bradner
RFC2027 IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees
The process by which the members of the IAB and IESG are selected, confirmed, and recalled has been exercised four times since its formal creation. The evolution of the process has relied principally on oral tradition as a means by which the lessons learned could be passed on to successive committees. This document is a self-consistent, organized compilation of the process as it is known today. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
October 1996
Status: INFORMATIONAL
Autor: J. Galvin
RFC2028 The Organizations Involved in the IETF Standards Process
This document describes the individuals and organizations involved in the IETF. This includes descriptions of the IESG, the IETF Working Groups and the relationship between the IETF and the Internet Society. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
October 1996
Status: BEST CURRENT PRACTICE
Autor: R. Hovey, S. Bradner
RFC2029 RTP Payload Format of Sun's CellB Video Encoding
This memo describes a packetization scheme for the CellB video encoding. The scheme proposed allows applications to transport CellB video flows over protocols used by RTP. This document is meant for implementors of video applications that want to use RTP and CellB. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: M. Speer, D. Hoffman
RFC2030 Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI
This memorandum describes the Simple Network Time Protocol (SNTP) Version 4, which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1996
Status: INFORMATIONAL
Autor: D. Mills
RFC2031 IETF-ISOC relationship
This memo summarises the issues on IETF - ISOC relationships as the have been discussed by the Poised Working Group. The purpose of the document is to gauge consensus on these issues. And to allow further discussions where necessary. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1996
Status: INFORMATIONAL
Autor: E. Huizer
RFC2032 RTP Payload Format for H.261 Video Streams
This memo describes a scheme to packetize an H.261 video stream for transport using the Real-time Transport Protocol, RTP, with any of the underlying protocols that carry RTP. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: T. Turletti, C. Huitema
RFC2033 Local Mail Transfer Protocol
SMTP [SMTP] [HOST-REQ] and its service extensions [ESMTP] provide a mechanism for transferring mail reliably and efficiently. The design of the SMTP protocol effectively requires the server to manage a mail delivery queue. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1996
Status: INFORMATIONAL
Autor: J. Myers
RFC2034 SMTP Service Extension for Returning Enhanced Error Codes
This memo defines an extension to the SMTP service [RFC-821, RFC-1869] whereby an SMTP server augments its responses with the enhanced mail system status codes defined in RFC 1893. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: N. Freed
RFC2035 RTP Payload Format for JPEG-compressed Video
This memo describes the RTP payload format for JPEG video streams. The packet format is optimized for real-time video streams where codec parameters change rarely from frame to frame. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: L. Berc, W. Fenner, R. Frederick, S. McCanne
RFC2036 Observations on the use of Components of the Class A Address Space within the Internet
This document is a commentary on the recommendation that IANA commence allocation of the presently unallocated components of the Class A address space to registries, for deployment within the Internet as class-less address blocks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1996
Status: HISTORIC
Autor: G. Huston
RFC2037 Entity MIB using SMIv2
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 multiple logical and physical entities managed by a single SNMP agent. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: K. McCloghrie, A. Bierman
RFC2038 RTP Payload Format for MPEG1/MPEG2 Video
This memo describes a packetization scheme for MPEG video and audio streams. The scheme proposed can be used to transport such a video or audio flow over the transport protocols supported by RTP. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: D. Hoffman, G. Fernando, V. Goyal
RFC2039 Applicability of Standards Track MIBs to Management of World Wide Web Servers
This document was produced at the request of the Network Management Area Director following the HTTP-MIB BOF at the 35th IETF meeting to report on the applicability of the existing standards track MIBs to management of WWW servers. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
November 1996
Status: INFORMATIONAL
Autor: C. Kalbfleisch
RFC2040 The RC5, RC5-CBC, RC5-CBC-Pad, and RC5-CTS Algorithms
This document defines four ciphers with enough detail to ensure interoperability between different implementations. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1996
Status: INFORMATIONAL
Autor: R. Baldwin, R. Rivest
RFC2041 Mobile Network Tracing
This RFC argues that mobile network tracing provides both tools to improve our understanding of wireless channels, as well as to build realistic, repeatable testbeds for mobile software and systems. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1996
Status: INFORMATIONAL
Autor: B. Noble, G. Nguyen, M. Satyanarayanan, R. Katz
RFC2042 Registering New BGP Attribute Types
This document describes the process for creating new BGP attribute type codes. Basic attribute type codes are described in RFC 1771, pages 12 through 15. These, and new attribute type codes that are used in the Internet are registered with the IANA. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
January 1997
Status: INFORMATIONAL
Autor: B. Manning
RFC2043 The PPP SNA Control Protocol (SNACP)
This document defines the Network Control Protocols for establishing and configuring Systems Network Architecture (SNA) over PPP and SNA over LLC 802.2 over PPP. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: A. Fuqua
RFC2044 UTF-8, a transformation format of Unicode and ISO 10646
The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993 jointly define a 16 bit character set which encompasses most of the world's writing systems. UTF-8, the object of this memo, has the characteristic of preserving the full US-ASCII range. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1996
Status: INFORMATIONAL
Autor: F. Yergeau
RFC2045 Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
This initial document specifies the various headers used to describe the structure of MIME messages. [STANDARDS-TRACK]
November 1996
Status: DRAFT STANDARD
Autor: N. Freed, N. Borenstein
RFC2046 Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
This second document defines the general structure of the MIME media typing system and defines an initial set of media types. [STANDARDS-TRACK]
November 1996
Status: DRAFT STANDARD
Autor: N. Freed, N. Borenstein
RFC2047 MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
This particular document is the third document in the series. It describes extensions to RFC 822 to allow non-US-ASCII text data in Internet mail header fields. [STANDARDS-TRACK]
November 1996
Status: DRAFT STANDARD
Autor: K. Moore
RFC2048 Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages. This fourth document, RFC 2048, specifies various IANA registration procedures for some MIME facilities. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
November 1996
Status: BEST CURRENT PRACTICE
Autor: N. Freed, J. Klensin, J. Postel
RFC2049 Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages. This fifth and final document describes MIME conformance criteria as well as providing some illustrative examples of MIME message formats, acknowledgements, and the bibliography. [STANDARDS-TRACK]
November 1996
Status: DRAFT STANDARD
Autor: N. Freed, N. Borenstein
RFC2050 Internet Registry IP Allocation Guidelines
This document describes the registry system for the distribution of globally unique Internet address space and registry operations. Particularly this document describes the rules and guidelines governing the distribution of this address space. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
November 1996
Status: BEST CURRENT PRACTICE
Autor: K. Hubbard, M. Kosters, D. Conrad, D. Karrenberg, J. Postel
RFC2051 Definitions of Managed Objects for APPC using SMIv2
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 controlling of network devices with APPC (Advanced Program-to-Program Communications) capabilities. This memo identifies managed objects for the SNA LU6.2 protocols. [STANDARDS-TRACK]
October 1996
Status: PROPOSED STANDARD
Autor: M. Allen, B. Clouston, Z. Kielczewski, W. Kwan, B. Moore
RFC2052 A DNS RR for specifying the location of services (DNS SRV)
This document describes a DNS RR which specifies the location of the server(s) for a specific protocol and domain (like a more general form of MX). This memo defines an Experimental Protocol for the Internet community.
October 1996
Status: EXPERIMENTAL
Autor: A. Gulbrandsen, P. Vixie
RFC2053 The AM (Armenia) Domain
The AM Domain is an official Internet top-level domain of Armenia. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1996
Status: INFORMATIONAL
Autor: E. Der-Danieliantz
RFC2054 WebNFS Client Specification
This document describes a lightweight binding mechanism that allows NFS clients to obtain service from WebNFS-enabled servers with a minimum of protocol overhead. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1996
Status: INFORMATIONAL
Autor: B. Callaghan
RFC2055 WebNFS Server Specification
This document describes the specifications for a server of WebNFS clients. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
October 1996
Status: INFORMATIONAL
Autor: B. Callaghan
RFC2056 Uniform Resource Locators for Z39.50
Z39.50 is an information retrieval protocol that does not fit neatly into a retrieval model designed primarily around the stateless fetch of data. Instead, it models a general user inquiry as a session-oriented, multi-step task, any step of which may be suspended temporarily while the server requests additional parameters from the client before continuing. [STANDARDS-TRACK]
November 1996
Status: PROPOSED STANDARD
Autor: R. Denenberg, J. Kunze, D. Lynch
RFC2057 Source Directed Access Control on the Internet
This memo was developed from a deposition that I submitted as part of a challenge to the Communications Decency Act of 1996, part of the Telecommunications Reform Act of 1996. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
November 1996
Status: INFORMATIONAL
Autor: S. Bradner
RFC2058 Remote Authentication Dial In User Service (RADIUS)
This document describes a protocol for carrying authentication, authorization, and configuration information between a Network Access Server which desires to authenticate its links and a shared Authentication Server. [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: C. Rigney, A. Rubens, W. Simpson, S. Willens
RFC2059 RADIUS Accounting
This document describes a protocol for carrying accounting information between a Network Access Server and a shared Accounting Server. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
January 1997
Status: INFORMATIONAL
Autor: C. Rigney
RFC2060 Internet Message Access Protocol - Version 4rev1
The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1) allows a client to access and manipulate electronic mail messages on a server. [STANDARDS-TRACK]
December 1996
Status: PROPOSED STANDARD
Autor: M. Crispin
RFC2061 IMAP4 Compatibility with IMAP2bis
This document is intended to be read along with RFC 1176 and the most recent IMAP4 specification (RFC 2060) to assist implementors in creating an IMAP4 implementation to interoperate with implementations that conform to earlier specifications. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1996
Status: INFORMATIONAL
Autor: M. Crispin
RFC2062 Internet Message Access Protocol - Obsolete Syntax
This document describes obsolete syntax which may be encountered by IMAP4 implementations which deal with older versions of the Internet Mail Access Protocol. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
December 1996
Status: INFORMATIONAL
Autor: M. Crispin
RFC2063 Traffic Flow Measurement: Architecture
This document describes an architecture for the measurement and reporting of network traffic flows, discusses how this relates to an overall network traffic flow architecture, and describes how it can be used within the Internet. This memo defines an Experimental Protocol for the Internet community.
January 1997
Status: EXPERIMENTAL
Autor: N. Brownlee, C. Mills, G. Ruth
RFC2064 Traffic Flow Measurement: Meter MIB
This memo defines a 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 obtaining traffic flow information from network traffic meters. This memo defines an Experimental Protocol for the Internet community.
January 1997
Status: EXPERIMENTAL
Autor: N. Brownlee
RFC2065 Domain Name System Security Extensions
The Domain Name System (DNS) has become a critical operational part of the Internet infrastructure yet it has no strong security mechanisms to assure data integrity or authentication. Extensions to the DNS are described that provide these services to security aware resolvers or applications through the use of cryptographic digital signatures. [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: D. Eastlake 3rd, C. Kaufman
RFC2066 TELNET CHARSET Option
This document specifies a mechanism for passing character set and translation information between a TELNET client and server. This memo defines an Experimental Protocol for the Internet community.
January 1997
Status: EXPERIMENTAL
Autor: R. Gellens
RFC2067 IP over HIPPI
ANSI Standard X3.218-1993 (HIPPI-LE[3]) defines the encapsulation of IEEE 802.2 LLC PDUs and, by implication, IP on HIPPI. This memo is a revision of RFC 1374, "IP and ARP on HIPPI", and is intended to replace it in the Standards Track. [STANDARDS-TRACK]
January 1997
Status: DRAFT STANDARD
Autor: J. Renwick
RFC2068 Hypertext Transfer Protocol -- HTTP/1.1
The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: R. Fielding, J. Gettys, J. Mogul, H. Frystyk, T. Berners-Lee
RFC2069 An Extension to HTTP : Digest Access Authentication
The protocol referred to as "HTTP/1.0" includes the specification for a Basic Access Authentication scheme. This scheme is not considered to be a secure method of user authentication, as the user name and password are passed over the network as clear text. A specification for a different authentication scheme is needed to address this severe limitation. This document provides specification for such a scheme, referred to as "Digest Access Authentication". [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: J. Franks, P. Hallam-Baker, J. Hostetler, P. Leach, A. Luotonen, E. Sink, L. Stewart
RFC2070 Internationalization of the Hypertext Markup Language
This document is meant to address the issue of the internationalization (i18n, i followed by 18 letters followed by n) of HTML by extending the specification of HTML and giving additional recommendations for proper internationalization support. [STANDARDS-TRACK]
January 1997
Status: HISTORIC
Autor: F. Yergeau, G. Nicol, G. Adams, M. Duerst
RFC2071 Network Renumbering Overview: Why would I want it and what is it anyway?
This document attempts to clearly define the concept of network renumbering and discuss some of the more pertinent reasons why an organization would have a need to do so. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
January 1997
Status: INFORMATIONAL
Autor: P. Ferguson, H. Berkowitz
RFC2072 Router Renumbering Guide
Routers interact with numerous network infrastructure servers, including DNS and SNMP. These interactions, not just the pure addressing and routing structure, must be considered as part of router renumbering. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
January 1997
Status: INFORMATIONAL
Autor: H. Berkowitz
RFC2073 An IPv6 Provider-Based Unicast Address Format
This document defines an IPv6 provider-based unicast address format for use in the Internet. [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: Y. Rekhter, P. Lothberg, R. Hinden, S. Deering, J. Postel
RFC2074 Remote Network Monitoring MIB Protocol Identifiers
This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes the algorithms required to identify different protocol encapsulations managed with the Remote Network Monitoring MIB Version 2 [RMON2]. [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: A. Bierman, R. Iddon
RFC2075 IP Echo Host Service
This memo describes how to implement an IP echo host. IP echo hosts send back IP datagrams after exchanging the source and destination IP addresses. This memo defines an Experimental Protocol for the Internet community.
January 1997
Status: EXPERIMENTAL
Autor: C. Partridge
RFC2076 Common Internet Message Headers
This memo contains a table of commonly occurring headers in headings of e-mail messages. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1997
Status: INFORMATIONAL
Autor: J. Palme
RFC2077 The Model Primary Content Type for Multipurpose Internet Mail Extensions
The purpose of this memo is to propose an update to Internet RFC 2045 to include a new primary content-type to be known as "model". [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: S. Nelson, C. Parks, Mitra
RFC2078 Generic Security Service Application Program Interface, Version 2
The Generic Security Service Application Program Interface (GSS-API), as defined in RFC-1508, 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. [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: J. Linn
RFC2079 Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs)
This document builds on the experimentation to date and defines a new attribute type and an auxiliary object class to allow URIs, including URLs, to be stored in directory entries in a standard way. [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: M. Smith
RFC2080 RIPng for IPv6
This document specifies a routing protocol for an IPv6 internet. It is based on protocols and algorithms currently in wide use in the IPv4 Internet [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: G. Malkin, R. Minnear
RFC2081 RIPng Protocol Applicability Statement
As required by Routing Protocol Criteria (RFC 1264), this report defines the applicability of the RIPng protocol within the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
January 1997
Status: INFORMATIONAL
Autor: G. Malkin
RFC2082 RIP-2 MD5 Authentication
Growth in the Internet has made us aware of the need for improved authentication of routing information. RIP-2 provides for unauthenticated service (as in classical RIP), or password authentication. [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: F. Baker, R. Atkinson
RFC2083 PNG (Portable Network Graphics) Specification Version 1.0
This document describes PNG (Portable Network Graphics), an extensible file format for the lossless, portable, well-compressed storage of raster images. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1997
Status: INFORMATIONAL
Autor: T. Boutell
RFC2084 Considerations for Web Transaction Security
This document specifies the requirements for the provision of security services to the HyperText Transport Protocol. These services include confidentiality, integrity, user authentication, and authentication of servers/services, including proxied or gatewayed services. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
January 1997
Status: INFORMATIONAL
Autor: G. Bossert, S. Cooper, W. Drummond
RFC2085 HMAC-MD5 IP Authentication with Replay Prevention
This document describes a keyed-MD5 transform to be used in conjunction with the IP Authentication Header [RFC-1826]. The particular transform is based on [HMAC-MD5]. An option is also specified to guard against replay attacks. [STANDARDS-TRACK]
February 1997
Status: PROPOSED STANDARD
Autor: M. Oehler, R. Glenn
RFC2086 IMAP4 ACL extension
The ACL extension of the Internet Message Access Protocol [IMAP4] permits access control lists to be manipulated through the IMAP protocol. [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: J. Myers
RFC2087 IMAP4 QUOTA extension
The QUOTA extension of the Internet Message Access Protocol [IMAP4] permits administrative limits on resource usage (quotas) to be manipulated through the IMAP protocol. [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: J. Myers
RFC2088 IMAP4 non-synchronizing literals
The Internet Message Access Protocol [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: J. Myers
RFC2089 V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent
The goal of this memo is to document a common way of mapping an SNMPv2 response into an SNMPv1 response within a bi-lingual SNMP agent (one that supports both SNMPv1 and SNMPv2). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
January 1997
Status: INFORMATIONAL
Autor: B. Wijnen, D. Levi
RFC2090 TFTP Multicast Option
This document describes a new TFTP option. This new option will allow the multiple clients to receive the same file concurrently through the use of Multicast packets. This memo defines an Experimental Protocol for the Internet community.
February 1997
Status: EXPERIMENTAL
Autor: A. Emberson
RFC2091 Triggered Extensions to RIP to Support Demand Circuits
This document defines a modification which can be applied to Bellman- Ford (distance vector) algorithm information broadcasting protocols. [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: G. Meyer, S. Sherry
RFC2092 Protocol Analysis for Triggered RIP
As required by Routing Protocol Criteria [1], this report documents the key features of Triggered Extensions to RIP to Support Demand Circuits [2] and the current implementation experience. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
January 1997
Status: INFORMATIONAL
Autor: S. Sherry, G. Meyer
RFC2093 Group Key Management Protocol (GKMP) Specification
This specification proposes a protocol to create grouped symmetric keys and distribute them amongst communicating peers. This memo defines an Experimental Protocol for the Internet community.
July 1997
Status: EXPERIMENTAL
Autor: H. Harney, C. Muckenhirn
RFC2094 Group Key Management Protocol (GKMP) Architecture
This specification proposes a protocol to create grouped symmetric keys and distribute them amongst communicating peers. This memo defines an Experimental Protocol for the Internet community.
July 1997
Status: EXPERIMENTAL
Autor: H. Harney, C. Muckenhirn
RFC2095 IMAP/POP AUTHorize Extension for Simple Challenge/Response
This specification provides a simple challenge-response authentication protocol that is suitable for use with IMAP4. [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: J. Klensin, R. Catoe, P. Krumviede
RFC2096 IP Forwarding Table MIB
This memo defines an update to RFC 1354. The significant difference between this MIB and RFC 1354 is the recognition (explicitly discussed but by consensus left to future work) that CIDR routes may have the same network number but different network masks. [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: F. Baker
RFC2097 The PPP NetBIOS Frames Control Protocol (NBFCP)
This document defines the Network Control Protocol for establishing and configuring the NBF protocol over PPP. The NBFCP protocol is only applicable for an end system to connect to a peer system or the LAN that peer system is connected to. [STANDARDS-TRACK]
January 1997
Status: PROPOSED STANDARD
Autor: G. Pall
RFC2098 Toshiba's Router Architecture Extensions for ATM : Overview
This memo describes a new internetworking architecture which makes better use of the property of ATM. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1997
Status: INFORMATIONAL
Autor: Y. Katsube, K. Nagami, H. Esaki
RFC2099 Request for Comments Summary RFC Numbers 2000-2099
March 1997
Status: INFORMATIONAL
Autor: J. Elliott
RFC2100 The Naming of Hosts
This RFC is a commentary on the difficulty of deciding upon an acceptably distinctive hostname for one's computer, a problem which grows in direct proportion to the logarithmically increasing size of the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1997
Status: INFORMATIONAL
Autor: J. Ashworth
RFC2101 IPv4 Address Behaviour Today
The main purpose of this note is to clarify the current interpretation of the 32-bit IP version 4 address space, whose significance has changed substantially since it was originally defined. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1997
Status: INFORMATIONAL
Autor: B. Carpenter, J. Crowcroft, Y. Rekhter
RFC2102 Multicast Support for Nimrod : Requirements and Solution Approaches
Nimrod does not specify a particular solution for multicasting. Rather, Nimrod may use any of a number of emerging multicast techniques. We identify the requirements that Nimrod has of a solution for multicast support. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1997
Status: INFORMATIONAL
Autor: R. Ramanathan
RFC2103 Mobility Support for Nimrod : Challenges and Solution Approaches
We discuss the issue of mobility in Nimrod. While a mobility solution is not part of the Nimrod architecture, Nimrod does require that the solution have certain characteristics. We identify the requirements that Nimrod has of any solution for mobility support. We also classify and compare existing approaches for supporting mobility within an internetwork and discuss their advantages and disadvantages. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1997
Status: INFORMATIONAL
Autor: R. Ramanathan
RFC2104 HMAC: Keyed-Hashing for Message Authentication
This document describes HMAC, a mechanism for message authentication using cryptographic hash functions. HMAC can be used with any iterative cryptographic hash function, e.g., MD5, SHA-1, in combination with a secret shared key. The cryptographic strength of HMAC depends on the properties of the underlying hash function. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind
February 1997
Status: INFORMATIONAL
Autor: H. Krawczyk, M. Bellare, R. Canetti
RFC2105 Cisco Systems' Tag Switching Architecture Overview
This document provides an overview of a novel approach to network layer packet forwarding, called tag switching. The two main components of the tag switching architecture - forwarding and control - are described. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1997
Status: INFORMATIONAL
Autor: Y. Rekhter, B. Davie, D. Katz, E. Rosen, G. Swallow
RFC2106 Data Link Switching Remote Access Protocol
This memo describes the Data Link Switching Remote Access Protocol that is used between workstations and routers to transport SNA/ NetBIOS traffic over TCP sessions. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1997
Status: INFORMATIONAL
Autor: S. Chiang, J. Lee, H. Yasuda
RFC2107 Ascend Tunnel Management Protocol - ATMP
This document specifies a generic tunnel management protocol that allows remote dial-in users to access their home network as if they were directly attached to the home network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1997
Status: INFORMATIONAL
Autor: K. Hamzeh
RFC2108 Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2
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 10 and 100 Mb/second baseband repeaters based on IEEE Std 802.3 Section 30, "10 &
February 1997
Status: PROPOSED STANDARD
Autor: K. de Graaf, D. Romascanu, D. McMaster, K. McCloghrie
RFC2109 HTTP State Management Mechanism
This document specifies a way to create a stateful session with HTTP requests and responses. It describes two new headers, Cookie and Set- Cookie, which carry state information between participating origin servers and user agents. The method described here differs from Netscape's Cookie proposal, but it can interoperate with HTTP/1.0 user agents that use Netscape's method. [STANDARDS-TRACK]
February 1997
Status: HISTORIC
Autor: D. Kristol, L. Montulli
RFC2110 MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)
This document describes a set of guidelines that will allow conforming mail user agents to be able to send, deliver and display these objects, such as HTML objects, that can contain links represented by URIs. [STANDARDS-TRACK]
March 1997
Status: PROPOSED STANDARD
Autor: J. Palme, A. Hopmann
RFC2111 Content-ID and Message-ID Uniform Resource Locators
The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow references to messages and the body parts of messages. For example, within a single multipart message, one HTML body part might include embedded references to other parts of the same message. [STANDARDS-TRACK]
March 1997
Status: PROPOSED STANDARD
Autor: E. Levinson
RFC2112 The MIME Multipart/Related Content-type
The Multipart/Related content-type provides a common mechanism for representing objects that are aggregates of related MIME body parts. This document defines the Multipart/Related content-type and provides examples of its use. [STANDARDS-TRACK]
March 1997
Status: PROPOSED STANDARD
Autor: E. Levinson
RFC2113 IP Router Alert Option
This memo describes a new IP Option type that alerts transit routers to more closely examine the contents of an IP packet. [STANDARDS-TRACK]
February 1997
Status: PROPOSED STANDARD
Autor: D. Katz
RFC2114 Data Link Switching Client Access Protocol
This memo describes the Data Link Switching Client Access Protocol that is used between workstations and routers to transport SNA/ NetBIOS traffic over TCP sessions. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
February 1997
Status: INFORMATIONAL
Autor: S. Chiang, J. Lee, H. Yasuda
RFC2115 Management Information Base for Frame Relay DTEs Using SMIv2
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 interfaces on DTEs. [STANDARDS-TRACK]
September 1997
Status: DRAFT STANDARD
Autor: C. Brown, F. Baker
RFC2116 X.500 Implementations Catalog-96
This document is a revision to [RFC 1632]: A Revised Catalog of Available X.500 Implementations and is based on the results of data collection via a WWW home page that enabled implementors to submit new or updated descriptions of currently available implementations of X.500, including commercial products and openly available offerings. [RFC 1632] is a revision of [RFC 1292]. This document contains detailed description of 31 X.500 implementations - DSAs, DUAs, and DUA interfaces. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1997
Status: INFORMATIONAL
Autor: C. Apple, K. Rossen
RFC2117 Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification
This document describes a protocol for efficiently routing to multicast groups that may span wide-area (and inter-domain) internets. This memo defines an Experimental Protocol for the Internet community.
June 1997
Status: EXPERIMENTAL
Autor: D. Estrin, D. Farinacci, A. Helmy, D. Thaler, S. Deering, M. Handley, V. Jacobson, C. Liu, P. Sharma, L. Wei
RFC2118 Microsoft Point-To-Point Compression (MPPC) Protocol
This document describes the use of the Microsoft Point to Point Compression protocol (also referred to as MPPC in this document) for compressing PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1997
Status: INFORMATIONAL
Autor: G. Pall
RFC2119 Key words for use in RFCs to Indicate Requirement Levels
In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
March 1997
Status: BEST CURRENT PRACTICE
Autor: S. Bradner
RFC2120 Managing the X.500 Root Naming Context
This document describes the use of 1993 ISO X.500 Standard protocols for managing the root context. Whilst the ASN.1 is compatible with that of the X.500 Standard, the actual settings of the parameters are supplementary to that of the X.500 Standard. This memo defines an Experimental Protocol for the Internet community.
March 1997
Status: EXPERIMENTAL
Autor: D. Chadwick
RFC2121 Issues affecting MARS Cluster Size
This document provides a qualitative look at the issues constraining a MARS Cluster's size, including the impact of VC limits in switches and NICs, geographical distribution of cluster members, and the use of VC Mesh or MCS modes to support multicast groups. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1997
Status: INFORMATIONAL
Autor: G. Armitage
RFC2122 VEMMI URL Specification
A new URL scheme, "vemmi" is defined. VEMMI is a new international standard for on-line multimedia services, that is both an ITU-T (International Telecommunications Union, ex. CCITT) International Standard (T.107) and an European Standard (ETSI European Telecommunications Standard Institute) standard (ETS 300 382, obsoleted by ETS 300 709). [STANDARDS-TRACK]
March 1997
Status: PROPOSED STANDARD
Autor: D. Mavrakis, H. Layec, K. Kartmann
RFC2123 Traffic Flow Measurement: Experiences with NeTraMet
This memo records experiences in implementing and using the Traffic Flow Measurement Architecture and Meter MIB. It discusses the implementation of NeTraMet (a traffic meter) and NeMaC (a combined manager and meter reader), considers the writing of meter rule sets and gives some guidance on setting up a traffic flow measurement system using NeTraMet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1997
Status: INFORMATIONAL
Autor: N. Brownlee
RFC2124 Cabletron's Light-weight Flow Admission Protocol Specification Version 1.0
This document specifies the protocol between the switch Connection Control Entity (CCE) and the external FAS. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
March 1997
Status: INFORMATIONAL
Autor: P. Amsden, J. Amweg, P. Calato, S. Bensley, G. Lyons
RFC2125 The PPP Bandwidth Allocation Protocol (BAP) / The PPP Bandwidth Allocation Control Protocol (BACP)
This document proposes a method to manage the dynamic bandwidth allocation of implementations supporting the PPP multilink protocol. This is done by defining the Bandwidth Allocation Protocol (BAP), as well as its associated control protocol, the Bandwidth Allocation Control Protocol (BACP). [STANDARDS-TRACK]
March 1997
Status: PROPOSED STANDARD
Autor: C. Richards, K. Smith
RFC2126 ISO Transport Service on top of TCP (ITOT)
This document is a revision to STD35, RFC1006. This document describes the mechanism to allow ISO Transport Services to run over TCP over IPv4 or IPv6. It also defines a number of new features, which are not provided in RFC1006. [STANDARDS-TRACK]
March 1997
Status: PROPOSED STANDARD
Autor: Y. Pouffary, A. Young
RFC2127 ISDN Management Information Base using SMIv2
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 a minimal set of managed objects for SNMP-based management of ISDN terminal interfaces. [STANDARDS-TRACK]
March 1997
Status: PROPOSED STANDARD
Autor: G. Roeck
RFC2128 Dial Control Management Information Base using SMIv2
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 demand access circuits, including ISDN. [STANDARDS-TRACK]
March 1997
Status: PROPOSED STANDARD
Autor: G. Roeck
RFC2129 Toshiba's Flow Attribute Notification Protocol (FANP) Specification
This memo discusses Flow Attribute Notification Protocol (FANP), which is a protocol between neighbor nodes for the management of cut-through packet forwarding functionalities. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1997
Status: INFORMATIONAL
Autor: K. Nagami, Y. Katsube, Y. Shobatake, A. Mogi, S. Matsuzawa, T. Jinmei, H. Esaki
RFC2130 The Report of the IAB Character Set Workshop held 29 February - 1 March, 1996
This report details the conclusions of an IAB-sponsored invitational workshop held 29 February - 1 March, 1996, to discuss the use of character sets on the Internet. It motivates the need to have character set handling in Internet protocols which transmit text, provides a conceptual framework for specifying character sets, recommends the use of MIME tagging for transmitted text, recommends a default character set *without* stating that there is no need for other character sets, and makes a series of recommendations to the IAB, IANA, and the IESG for furthering the integration of the character set framework into text transmission protocols. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1997
Status: INFORMATIONAL
Autor: C. Weider, C. Preston, K. Simonsen, H. Alvestrand, R. Atkinson, M. Crispin, P. Svanberg
RFC2131 Dynamic Host Configuration Protocol
The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCPIP network. DHCP is based on the Bootstrap Protocol (BOOTP), adding the capability of automatic allocation of reusable network addresses and additional configuration options. [STANDARDS-TRACK]
March 1997
Status: DRAFT STANDARD
Autor: R. Droms
RFC2132 DHCP Options and BOOTP Vendor Extensions
This document specifies the current set of DHCP options. Future options will be specified in separate RFCs. The current list of valid options is also available in ftp://ftp.isi.edu/in-notes/iana/assignments. [STANDARDS-TRACK]
March 1997
Status: DRAFT STANDARD
Autor: S. Alexander, R. Droms
RFC2133 Basic Socket Interface Extensions for IPv6
This memo defines a set of extensions to the socket interface to support the larger address size and new features of IPv6. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1997
Status: INFORMATIONAL
Autor: R. Gilligan, S. Thomson, J. Bound, W. Stevens
RFC2134 Articles of Incorporation of Internet Society
These are the articles of incorporation of the Internet Society. They are published for the information of the IETF community at the request of the poisson working group. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1997
Status: INFORMATIONAL
Autor: ISOC Board of Trustees
RFC2135 Internet Society By-Laws
These are the by-laws of the Internet Society, as amended, as of June 1996. They are published for the information of the IETF community at the request of the poisson working group. Please refer to the ISOC web page (www.isoc.org) for the current version of the by-laws. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1997
Status: INFORMATIONAL
Autor: ISOC Board of Trustees
RFC2136 Dynamic Updates in the Domain Name System (DNS UPDATE)
Using this specification of the UPDATE opcode, it is possible to add or delete RRs or RRsets from a specified zone. Prerequisites are specified separately from update operations, and can specify a dependency upon either the previous existence or nonexistence of an RRset, or the existence of a single RR. [STANDARDS-TRACK]
April 1997
Status: PROPOSED STANDARD
Autor: P. Vixie, S. Thomson, Y. Rekhter, J. Bound
RFC2137 Secure Domain Name System Dynamic Update
This memo describes how to use DNSSEC digital signatures covering requests and data to secure updates and restrict updates to those authorized to perform them as indicated by the updater's possession of cryptographic keys. [STANDARDS-TRACK]
April 1997
Status: PROPOSED STANDARD
Autor: D. Eastlake 3rd
RFC2138 Remote Authentication Dial In User Service (RADIUS)
This document describes a protocol for carrying authentication, authorization, and configuration information between a Network Access Server which desires to authenticate its links and a shared Authentication Server. [STANDARDS-TRACK]
April 1997
Status: PROPOSED STANDARD
Autor: C. Rigney, A. Rubens, W. Simpson, S. Willens
RFC2139 RADIUS Accounting
This document describes a protocol for carrying accounting information between a Network Access Server and a shared Accounting Server. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1997
Status: INFORMATIONAL
Autor: C. Rigney
RFC2140 TCP Control Block Interdependence
This memo makes the case for interdependent TCP control blocks, where part of the TCP state is shared among similar concurrent connections, or across similar connection instances. TCP state includes a combination of parameters, such as connection state, current round-trip time estimates, congestion control information, and process information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
April 1997
Status: INFORMATIONAL
Autor: J. Touch
RFC2141 URN Syntax
Uniform Resource Names (URNs) are intended to serve as persistent, location-independent, resource identifiers. This document sets forward the canonical syntax for URNs. [STANDARDS-TRACK]
May 1997
Status: PROPOSED STANDARD
Autor: R. Moats
RFC2142 Mailbox Names for Common Services, Roles and Functions
This specification enumerates and describes Internet mail addresses (mailbox name @ host reference) to be used when contacting personnel at an organization. [STANDARDS-TRACK]
May 1997
Status: PROPOSED STANDARD
Autor: D. Crocker
RFC2143 Encapsulating IP with the Small Computer System Interface
This document outlines a protocol for connecting hosts running the TCP/IP protocol suite over a Small Computer System Interface (SCSI) bus. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind.
May 1997
Status: EXPERIMENTAL
Autor: B. Elliston
RFC2144 The CAST-128 Encryption Algorithm
There is a need in the Internet community for an unencumbered encryption algorithm with a range of key sizes that can provide security for a variety of cryptographic applications and protocols. This document describes an existing algorithm that can be used to satisfy this requirement. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1997
Status: INFORMATIONAL
Autor: C. Adams
RFC2145 Use and Interpretation of HTTP Version Numbers
HTTP request and response messages include an HTTP protocol version number. Some confusion exists concerning the proper use and interpretation of HTTP version numbers, and concerning interoperability of HTTP implementations of different protocol versions. This document is an attempt to clarify the situation. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1997
Status: INFORMATIONAL
Autor: J. C. Mogul, R. Fielding, J. Gettys, H. Frystyk
RFC2146 U.S. Government Internet Domain Names
This memo provides an update and clarification to RFC 1816. This document describes the registration policies for the top-level domain ".GOV". The purpose of the domain is to provide naming conventions that identify US Federal government agencies in order to facilitate access to their electronic resources. This memo provides guidance for registrations by Federal Agencies that avoids name duplication and facilitates responsiveness to the public. It restricts registrations to coincide with the approved structure of the US government and the advice of its Chief Information Officers. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1997
Status: INFORMATIONAL
Autor: Federal Networking Council
RFC2147 TCP and UDP over IPv6 Jumbograms
IPv6 supports datagrams larger than 65535 bytes long, often referred to as jumbograms, through use of the Jumbo Payload hop-by-hop option. The UDP protocol has a 16-bit length field that keeps it from being able to make use of jumbograms, and though TCP does not have a length field, both the MSS option and the Urgent field are constrained by 16-bits. This document describes some simple changes that can be made to allow TCP and UDP to make use of IPv6 jumbograms. [STANDARDS-TRACK]
May 1997
Status: PROPOSED STANDARD
Autor: D. Borman
RFC2148 Deployment of the Internet White Pages Service
This document describes the way in which the Internet White Pages Service is best exploited using today's experience, today's protocols, today's products and today's procedures. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
September 1997
Status: BEST CURRENT PRACTICE
Autor: H. Alvestrand, P. Jurg
RFC2149 Multicast Server Architectures for MARS-based ATM multicasting
This memo provides details on the design and implementation of an MCS, building on the core mechanisms defined in RFC 2022. It also provides a mechanism for using multiple MCSs per group for providing fault tolerance. This approach can be used with RFC 2022 based MARS server and clients, without needing any change in their functionality. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1997
Status: INFORMATIONAL
Autor: R. Talpade, M. Ammar
RFC2150 Humanities and Arts: Sharing Center Stage on the Internet
The purpose of this document is to provide members of the Arts and Humanities communities with an introduction to the Internet as a valuable tool, resource, and medium for the creation, presentation, and preservation of Arts and Humanities-based content. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
October 1997
Status: INFORMATIONAL
Autor: J. Max, W. Stickle
RFC2151 A Primer On Internet and TCP/IP Tools and Utilities
This memo is an introductory guide to many of the most commonly- available TCP/IP and Internet tools and utilities. It also describes discussion lists accessible from the Internet, ways to obtain Internet and TCP/IP documents, and some resources that help users weave their way through the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1997
Status: INFORMATIONAL
Autor: G. Kessler, S. Shepard
RFC2152 UTF-7 A Mail-Safe Transformation Format of Unicode
This document describes a transformation format of Unicode that contains only 7-bit ASCII octets 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 MIME and RFC 1641, "Using Unicode with MIME". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
May 1997
Status: INFORMATIONAL
Autor: D. Goldsmith, M. Davis
RFC2153 PPP Vendor Extensions
The Point-to-Point Protocol (PPP) 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; and a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document provides information for the Internet community. It does not specify an Internet standard of any kind.
May 1997
Status: INFORMATIONAL
Autor: W. Simpson
RFC2154 OSPF with Digital Signatures
This memo describes the extensions to OSPF required to add digital signature authentication to Link State data, and to provide a certification mechanism for router data. Added LSA processing and key management is detailed. A method for migration from, or co-existence with, standard OSPF V2 is described. This memo defines an Experimental Protocol for the Internet community.
June 1997
Status: EXPERIMENTAL
Autor: S. Murphy, M. Badger, B. Wellington
RFC2155 Definitions of Managed Objects for APPN using SMIv2
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 monitoring and controlling network devices with APPN (Advanced Peer-to-Peer Networking) capabilities. This memo identifies managed objects for the APPN protocol. [STANDARDS-TRACK]
June 1997
Status: PROPOSED STANDARD
Autor: B. Clouston, B. Moore
RFC2156 MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME
This document relates primarily to the ITU-T 1988 and 1992 X.400 Series Recommendations / ISO IEC 10021 International Standard. This ISO/ITU-T standard is referred to in this document as "X.400", which is a convenient shorthand. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: S. Kille
RFC2157 Mapping between X.400 and RFC-822/MIME Message Bodies
This document defines how to map body parts of X.400 messages into MIME entities and vice versa, including the handling of multipart messages and forwarded messages. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: H. Alvestrand
RFC2158 X.400 Image Body Parts
This document contains the body parts defined in RFC 1495 for carrying image formats that were originally defined in MIME through an X.400 system. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: H. Alvestrand
RFC2159 A MIME Body Part for FAX
This document contains the definitions, originally contained in RFC 1494, on how to carry CCITT G3Fax in MIME, and how to translate it to its X.400 representation. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: H. Alvestrand
RFC2160 Carrying PostScript in X.400 and MIME
This document describes methods for carrying PostScript information in the two standard mail systems MIME and X.400, and the conversion between them. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: H. Alvestrand
RFC2161 A MIME Body Part for ODA
This document contains the definitions, originally contained in RFC 1495 and RFC 1341, on how to carry ODA in MIME, and how to translate it to its X.400 representation. This memo defines an Experimental Protocol for the Internet community.
January 1998
Status: EXPERIMENTAL
Autor: H. Alvestrand
RFC2162 MaXIM-11 - Mapping between X.400 / Internet mail and Mail-11 mail
The standard referred shortly into this document as "X.400" relates to the ISO/IEC 10021 - CCITT 1984, 1988 and 1992 X.400 Series Recommendations covering the Message Oriented Text Interchange Service (MOTIS). This document covers the Inter Personal Messaging System (IPMS) only. This memo defines an Experimental Protocol for the Internet community.
January 1998
Status: EXPERIMENTAL
Autor: C. Allocchio
RFC2163 Using the Internet DNS to Distribute MIXER Conformant Global Address Mapping (MCGAM)
This memo is the complete technical specification to store in the Internet Domain Name System (DNS) the mapping information (MCGAM) needed by MIXER conformant e-mail gateways and other tools to map RFC822 domain names into X.400 O/R names and vice versa. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: C. Allocchio
RFC2164 Use of an X.500/LDAP directory to support MIXER address mapping
This specification defines how to represent and maintain these mappings (MIXER Conformant Global Address Mappings of MCGAMs) in an X.500 or LDAP directory. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: S. Kille
RFC2165 Service Location Protocol
The Service Location Protocol provides a scalable framework for the discovery and selection of network services. Using this protocol, computers using the Internet no longer need so much static configuration of network services for network based applications. This is especially important as computers become more portable, and users less tolerant or able to fulfill the demands of network system administration. [STANDARDS-TRACK]
June 1997
Status: PROPOSED STANDARD
Autor: J. Veizades, E. Guttman, C. Perkins, S. Kaplan
RFC2166 APPN Implementer's Workshop Closed Pages Document DLSw v2.0 Enhancements
This document specifies a set of extensions to RFC 1795 designed to improve the scalability of DLSw clarifications to RFC 1795 in the light of the implementation experience to-date. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1997
Status: INFORMATIONAL
Autor: D. Bryant, P. Brittain
RFC2167 Referral Whois (RWhois) Protocol V1.5
This memo describes Version 1.5 of the client/server interaction of RWhois. RWhois provides a distributed system for the discovery, retrieval, and maintenance of directory information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1997
Status: INFORMATIONAL
Autor: S. Williamson, M. Kosters, D. Blacka, J. Singh, K. Zeilstra
RFC2168 Resolution of Uniform Resource Identifiers using the Domain Name System
The requirements document for URN resolution systems defines the concept of a "resolver discovery service". This document describes the first, experimental, RDS. It is implemented by a new DNS Resource Record, NAPTR (Naming Authority PoinTeR), that provides rules for mapping parts of URIs to domain names. This memo defines an Experimental Protocol for the Internet community.
June 1997
Status: EXPERIMENTAL
Autor: R. Daniel, M. Mealling
RFC2169 A Trivial Convention for using HTTP in URN Resolution
This document specifies the "THTTP" resolution protocol - a trivial convention for encoding resolution service requests and responses as HTTP 1.0 or 1.1 requests and responses. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested.
June 1997
Status: EXPERIMENTAL
Autor: R. Daniel
RFC2170 Application REQuested IP over ATM (AREQUIPA)
This document specifies a method for allowing ATM-attached hosts that have direct ATM connectivity to set up end-to-end IP over ATM connections within the reachable ATM cloud, on request from applications, and for the exclusive use by the requesting applications. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
July 1997
Status: INFORMATIONAL
Autor: W. Almesberger, J. Le Boudec, P. Oechslin
RFC2171 MAPOS - Multiple Access Protocol over SONET/SDH Version 1
This memo documents a multiple access protocol for transmission of network-protocol datagrams, encapsulated in High-Level Data Link Control (HDLC) frames, over SONET/SDH. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1997
Status: INFORMATIONAL
Autor: K. Murakami, M. Maruyama
RFC2172 MAPOS Version 1 Assigned Numbers
This memo documents the parameters used in the Multiple Access Protocol over SONET/SDH Version 1. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1997
Status: INFORMATIONAL
Autor: M. Maruyama, K. Murakami
RFC2173 A MAPOS version 1 Extension - Node Switch Protocol
This document describes a MAPOS extension, Node Switch Protocol, for automatic node address assignment. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1997
Status: INFORMATIONAL
Autor: K. Murakami, M. Maruyama
RFC2174 A MAPOS version 1 Extension - Switch-Switch Protocol
This memo documents a MAPOS (Multiple Access Protocol over SONET/SDH) version 1 extension, Switch Switch Protocol which provides dynamic routing for unicast, broadcast, and multicast. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1997
Status: INFORMATIONAL
Autor: K. Murakami, M. Maruyama
RFC2175 MAPOS 16 - Multiple Access Protocol over SONET/SDH with 16 Bit Addressing
This memo documents MAPOS 16, a multiple access protocol for transmission of network-protocol datagrams, encapsulated in HDLC frames with 16 bit addressing, over SONET/SDH. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1997
Status: INFORMATIONAL
Autor: K. Murakami, M. Maruyama
RFC2176 IPv4 over MAPOS Version 1
This memo documents a mechanism for supporting Version 4 of the Internet Protocol (IPv4) on Version 1 of the Multiple Access Protocol over SONET/SDH. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1997
Status: INFORMATIONAL
Autor: K. Murakami, M. Maruyama
RFC2177 IMAP4 IDLE command
This document specifies the syntax of an IDLE command, which will allow a client to tell the server that it's ready to accept such real-time updates. [STANDARDS-TRACK]
June 1997
Status: PROPOSED STANDARD
Autor: B. Leiba
RFC2178 OSPF Version 2
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.
July 1997
Status: DRAFT STANDARD
Autor: J. Moy
RFC2179 Network Security For Trade Shows
This document is designed to assist vendors and other participants in trade shows, such as Networld+Interop, in designing effective protection against network and system attacks by unauthorized individuals. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
July 1997
Status: INFORMATIONAL
Autor: A. Gwinn
RFC2180 IMAP4 Multi-Accessed Mailbox Practice
The behavior described in this document reflects the practice of some existing servers or behavior that the consensus of the IMAP mailing list has deemed to be reasonable. The behavior described within this document is believed to be [RFC-2060] compliant. However, this document is not meant to define IMAP4 compliance, nor is it an exhaustive list of valid IMAP4 behavior. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
July 1997
Status: INFORMATIONAL
Autor: M. Gahrns
RFC2181 Clarifications to the DNS Specification
This document considers some areas that have been identified as problems with the specification of the Domain Name System, and proposes remedies for the defects identified. [STANDARDS-TRACK]
July 1997
Status: PROPOSED STANDARD
Autor: R. Elz, R. Bush
RFC2182 Selection and Operation of Secondary DNS Servers
This document discusses the selection of secondary servers for DNS zones.The number of servers appropriate for a zone is also discussed, and some general secondary server maintenance issues considered. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
July 1997
Status: BEST CURRENT PRACTICE
Autor: R. Elz, R. Bush, S. Bradner, M. Patton
RFC2183 Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field
This memo provides a mechanism whereby messages conforming to the MIME specifications [RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049] can convey presentational information. It specifies the "Content- Disposition" header field, which is optional and valid for any MIME entity ("message" or "body part"). [STANDARDS-TRACK]
August 1997
Status: PROPOSED STANDARD
Autor: R. Troost, S. Dorner, K. Moore
RFC2184 MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
This memo defines extensions to the RFC 2045 media type and RFC 2183 disposition parameter value mechanisms. [STANDARDS-TRACK]
August 1997
Status: PROPOSED STANDARD
Autor: N. Freed, K. Moore
RFC2185 Routing Aspects of IPv6 Transition
This document gives an overview of the routing aspects of the IPv6 transition. It is based on the protocols defined in the document "Transition Mechanisms for IPv6 Hosts and Routers." Readers should be familiar with the transition mechanisms before reading this document. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
September 1997
Status: INFORMATIONAL
Autor: R. Callon, D. Haskin
RFC2186 Internet Cache Protocol (ICP), version 2
This document describes version 2 of the Internet Cache Protocol (ICPv2) as currently implemented in two World-Wide Web proxy cache packages. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
September 1997
Status: INFORMATIONAL
Autor: D. Wessels, K. Claffy
RFC2187 Application of Internet Cache Protocol (ICP), version 2
This document describes the application of ICPv2 (Internet Cache Protocol version 2, RFC2186) to Web caching. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
September 1997
Status: INFORMATIONAL
Autor: D. Wessels, K. Claffy
RFC2188 AT&T/Neda's Efficient Short Remote Operations (ESRO) Protocol Specification Version 1.2
This document specifies the service model, the notation and protocol for Efficient Short Remote Operations (ESRO). This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
September 1997
Status: INFORMATIONAL
Autor: M. Banan, M. Taylor, J. Cheng
RFC2189 Core Based Trees (CBT version 2) Multicast Routing -- Protocol Specification --
This document describes the Core Based Tree (CBT version 2) network layer multicast routing protocol. CBT builds a shared multicast distribution tree per group, and is suited to inter- and intra-domain multicast routing. This memo defines an Experimental Protocol for the Internet community.
September 1997
Status: HISTORIC
Autor: A. Ballardie
RFC2190 RTP Payload Format for H.263 Video Streams
This document specifies the payload format for encapsulating an H.263 bitstream in the Real-Time Transport Protocol (RTP). [STANDARDS-TRACK]
September 1997
Status: HISTORIC
Autor: C. Zhu
RFC2191 VENUS - Very Extensive Non-Unicast Service
This document focuses exclusively on the problems associated with extending the MARS model to cover multiple clusters or clusters spanning more than one subnet. It describes a hypothetical solution, dubbed "Very Extensive NonUnicast Service" (VENUS), and shows how complex such a service would be. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
September 1997
Status: INFORMATIONAL
Autor: G. Armitage
RFC2192 IMAP URL Scheme
This document defines a URL scheme for referencing objects on an IMAP server. [STANDARDS-TRACK]
September 1997
Status: PROPOSED STANDARD
Autor: C. Newman
RFC2193 IMAP4 Mailbox Referrals
Mailbox referrals allow clients to seamlessly access mailboxes that are distributed across several IMAP4 servers. [STANDARDS-TRACK]
September 1997
Status: PROPOSED STANDARD
Autor: M. Gahrns
RFC2194 Review of Roaming Implementations
This document reviews the design and functionality of existing roaming implementations. Examples of cases where roaming capability might be required include ISP "confederations" and ISP-provided corporate network access support. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
September 1997
Status: INFORMATIONAL
Autor: B. Aboba, J. Lu, J. Alsop, J. Ding, W. Wang
RFC2195 IMAP/POP AUTHorize Extension for Simple Challenge/Response
This specification provides a simple challenge-response authentication protocol that is suitable for use with IMAP4. [STANDARDS-TRACK]
September 1997
Status: PROPOSED STANDARD
Autor: J. Klensin, R. Catoe, P. Krumviede
RFC2196 Site Security Handbook
This handbook is a guide to developing computer security policies and procedures for sites that have systems on the Internet. The purpose of this handbook is to provide practical guidance to administrators trying to secure their information and services. The subjects covered include policy content and formation, a broad range of technical system and network security topics, and security incident response. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
September 1997
Status: INFORMATIONAL
Autor: B. Fraser
RFC2197 SMTP Service Extension for Command Pipelining
This memo defines an extension to the SMTP service whereby a server can indicate the extent of its ability to accept multiple commands in a single TCP send operation. [STANDARDS-TRACK]
September 1997
Status: DRAFT STANDARD
Autor: N. Freed
RFC2198 RTP Payload for Redundant Audio Data
This document describes a payload format for use with the real-time transport protocol (RTP), version 2, for encoding redundant audio data. [STANDARDS-TRACK]
September 1997
Status: PROPOSED STANDARD
Autor: C. Perkins, I. Kouvelas, O. Hodson, V. Hardman, M. Handley, J.C. Bolot, A. Vega-Garcia, S. Fosse-Parisis
RFC2199 Request for Comments Summary RFC Numbers 2100-2199
January 1998
Status: INFORMATIONAL
Autor: A. Ramos
RFC2200 Internet Official Protocol Standards
A discussion of the standardization process and the RFC document series is presented first, followed by an explanation of the terms. Sections 6.2 - 6.10 contain the lists of protocols in each stage of standardization. Finally are pointers to references and contacts for further information. [STANDARDS-TRACK]
June 1997
Status: HISTORIC
Autor: J. Postel
RFC2201 Core Based Trees (CBT) Multicast Routing Architecture
CBT is a multicast routing architecture that builds a single delivery tree per group which is shared by all of the group's senders and receivers. This memo defines an Experimental Protocol for the Internet community.
September 1997
Status: HISTORIC
Autor: A. Ballardie
RFC2202 Test Cases for HMAC-MD5 and HMAC-SHA-1
This document provides two sets of test cases for HMAC-MD5 and HMAC- SHA-1, respectively. HMAC-MD5 and HMAC-SHA-1 are two constructs of the HMAC [HMAC] message authentication function using the MD5 [MD5] hash function and the SHA-1 [SHA] hash function. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
September 1997
Status: INFORMATIONAL
Autor: P. Cheng, R. Glenn
RFC2203 RPCSEC_GSS Protocol Specification
This memo describes an ONC/RPC security flavor that allows RPC protocols to access the Generic Security Services Application Programming Interface (referred to henceforth as GSS-API). [STANDARDS-TRACK]
September 1997
Status: PROPOSED STANDARD
Autor: M. Eisler, A. Chiu, L. Ling
RFC2204 ODETTE File Transfer Protocol
This memo describes a file transfer protocol to facilitate electronic data interchange between trading partners. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
September 1997
Status: INFORMATIONAL
Autor: D. Nash
RFC2205 Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
This memo describes version 1 of RSVP, a resource reservation setup protocol designed for an integrated services Internet. RSVP provides receiver-initiated setup of resource reservations for multicast or unicast data flows, with good scaling and robustness properties. [STANDARDS-TRACK]
September 1997
Status: PROPOSED STANDARD
Autor: R. Braden, L. Zhang, S. Berson, S. Herzog, S. Jamin
RFC2206 RSVP Management Information Base using SMIv2
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 Resource Reservation Protocol (RSVP) within the interface attributes defined in the Integrated Services Model. [STANDARDS-TRACK]
September 1997
Status: PROPOSED STANDARD
Autor: F. Baker, J. Krawczyk, A. Sastry
RFC2207 RSVP Extensions for IPSEC Data Flows
This document presents extensions to Version 1 of RSVP. These extensions permit support of individual data flows using RFC 1826, IP Authentication Header (AH) or RFC 1827, IP Encapsulating Security Payload (ESP). [STANDARDS-TRACK]
September 1997
Status: PROPOSED STANDARD
Autor: L. Berger, T. O'Malley
RFC2208 Resource ReSerVation Protocol (RSVP) -- Version 1 Applicability Statement Some Guidelines on Deployment
This document describes the applicability of RSVP along with the Integrated Services protocols and other components of resource reservation and offers guidelines for deployment of resource reservation at this time. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
September 1997
Status: INFORMATIONAL
Autor: A. Mankin, F. Baker, B. Braden, S. Bradner, M. O'Dell, A. Romanow, A. Weinrib, L. Zhang
RFC2209 Resource ReSerVation Protocol (RSVP) -- Version 1 Message Processing Rules
This memo contains an algorithmic description of the rules used by an RSVP implementation for processing messages. It is intended to clarify the version 1 RSVP protocol specification. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
September 1997
Status: INFORMATIONAL
Autor: R. Braden, L. Zhang
RFC2210 The Use of RSVP with IETF Integrated Services
This note describes the use of the RSVP resource reservation protocol with the Controlled-Load and Guaranteed QoS control services. [STANDARDS-TRACK]
September 1997
Status: PROPOSED STANDARD
Autor: J. Wroclawski
RFC2211 Specification of the Controlled-Load Network Element Service
This memo specifies the network element behavior required to deliver Controlled-Load service in the Internet. [STANDARDS-TRACK]
September 1997
Status: PROPOSED STANDARD
Autor: J. Wroclawski
RFC2212 Specification of Guaranteed Quality of Service
This memo describes the network element behavior required to deliver a guaranteed service (guaranteed delay and bandwidth) in the Internet. [STANDARDS-TRACK]
September 1997
Status: PROPOSED STANDARD
Autor: S. Shenker, C. Partridge, R. Guerin
RFC2213 Integrated Services Management Information Base using SMIv2
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 the interface attributes defined in the Integrated Services Model. [STANDARDS-TRACK]
September 1997
Status: PROPOSED STANDARD
Autor: F. Baker, J. Krawczyk, A. Sastry
RFC2214 Integrated Services Management Information Base Guaranteed Service Extensions using SMIv2
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 the interface attributes defined in the Guaranteed Service of the Integrated Services Model. [STANDARDS-TRACK]
September 1997
Status: PROPOSED STANDARD
Autor: F. Baker, J. Krawczyk, A. Sastry
RFC2215 General Characterization Parameters for Integrated Service Network Elements
This memo defines a set of general control and characterization parameters for network elements supporting the IETF integrated services QoS control framework. [STANDARDS-TRACK]
September 1997
Status: PROPOSED STANDARD
Autor: S. Shenker, J. Wroclawski
RFC2216 Network Element Service Specification Template
This document defines a framework for specifying services provided by network elements, and available to applications, in an internetwork which offers multiple qualities of service. The document first provides some necessary context -- including relevant definitions and suggested data formats -- and then specifies a "template" which service specification documents should follow. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
September 1997
Status: INFORMATIONAL
Autor: S. Shenker, J. Wroclawski
RFC2217 Telnet Com Port Control Option
This memo proposes a protocol to allow greater use of modems attached to a network for outbound dialing purposes. This memo defines an Experimental Protocol for the Internet community.
October 1997
Status: EXPERIMENTAL
Autor: G. Clark
RFC2218 A Common Schema for the Internet White Pages Service
This document specifies the minimum set of core attributes of a White Pages entry for an individual and describes how new objects with those attributes can be defined and published. [STANDARDS-TRACK]
October 1997
Status: PROPOSED STANDARD
Autor: T. Genovese, B. Jennings
RFC2219 Use of DNS Aliases for Network Services
It has become a common practice to use symbolic names (usually CNAMEs) in the Domain Name Service (DNS - [RFC-1034, RFC-1035]) to refer to network services such as anonymous FTP [RFC-959] servers, Gopher [RFC- 1436] servers, and most notably World-Wide Web HTTP [RFC-1945] servers. This is desirable for a number of reasons. It provides a way of moving services from one machine to another transparently, and a mechanism by which people or agents may programmatically discover that an organization runs, say, a World-Wide Web server. Although this approach has been almost universally adopted, there is no standards document or similar specification for these commonly used names. This document seeks to rectify this situation by gathering together the extant 'folklore' on naming conventions, and proposes a mechanism for accommodating new protocols. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
October 1997
Status: BEST CURRENT PRACTICE
Autor: M. Hamilton, R. Wright
RFC2220 The Application/MARC Content-type
This memorandum provides a mechanism for representing objects which are files of Machine-Readable Cataloging records (MARC). The MARC formats are standards for the representation and communication of bibliographic and related information. A MARC record contains metadata for an information resource following MARC format specifications. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
October 1997
Status: INFORMATIONAL
Autor: R. Guenther
RFC2221 IMAP4 Login Referrals
When dealing with large amounts of users and many IMAP4 [RFC-2060] servers, it is often necessary to move users from one IMAP4 server to another. Login referrals allow clients to transparently connect to an alternate IMAP4 server, if their home IMAP4 server has changed. [STANDARDS-TRACK]
October 1997
Status: PROPOSED STANDARD
Autor: M. Gahrns
RFC2222 Simple Authentication and Security Layer (SASL)
This document describes a method for adding authentication support to connection-based protocols. [STANDARDS-TRACK]
October 1997
Status: PROPOSED STANDARD
Autor: J. Myers
RFC2223 Instructions to RFC Authors
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.
October 1997
Status: INFORMATIONAL
Autor: J. Postel, J. Reynolds
RFC2224 NFS URL Scheme
A new URL scheme, 'nfs' is defined. It is used to refer to files and directories on NFS servers using the general URL syntax defined in RFC 1738, "Uniform Resource Locators (URL)". This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
October 1997
Status: INFORMATIONAL
Autor: B. Callaghan
RFC2225 Classical IP and ARP over ATM
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). [STANDARDS-TRACK]
April 1998
Status: PROPOSED STANDARD
Autor: M. Laubach, J. Halpern
RFC2226 IP Broadcast over ATM Networks
This memo describes how the IP multicast service being developed by the IP over ATM working group may be used to support IP broadcast transmission. [STANDARDS-TRACK]
October 1997
Status: PROPOSED STANDARD
Autor: T. Smith, G. Armitage
RFC2227 Simple Hit-Metering and Usage-Limiting for HTTP
This document proposes a simple extension to HTTP, using a new "Meter" header. [STANDARDS-TRACK]
October 1997
Status: PROPOSED STANDARD
Autor: J. Mogul, P. Leach
RFC2228 FTP Security Extensions
This document defines extensions to the FTP specification STD 9, RFC
October 1997
Status: PROPOSED STANDARD
Autor: M. Horowitz, S. Lunt
RFC2229 A Dictionary Server Protocol
The Dictionary Server Protocol (DICT) is a TCP transaction based query/response protocol that allows a client to access dictionary definitions from a set of natural language dictionary databases. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
October 1997
Status: INFORMATIONAL
Autor: R. Faith, B. Martin
RFC2230 Key Exchange Delegation Record for the DNS
This note describes a mechanism whereby authorisation for one node to act as key exchanger for a second node is delegated and made available via the Secure DNS. This mechanism is intended to be used only with the Secure DNS. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
November 1997
Status: INFORMATIONAL
Autor: R. Atkinson
RFC2231 MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
This memo defines extensions to the RFC 2045 media type and RFC 2183 disposition parameter value mechanisms. This memo also defines an extension to the encoded words defined in RFC 2047 to allow the specification of the language to be used for display as well as the character set. [STANDARDS-TRACK]
November 1997
Status: PROPOSED STANDARD
Autor: N. Freed, K. Moore
RFC2232 Definitions of Managed Objects for DLUR using SMIv2
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 monitoring and controlling network devices with DLUR (Dependent LU Requester) capabilities. This memo identifies managed objects for the DLUR protocol. [STANDARDS-TRACK]
November 1997
Status: PROPOSED STANDARD
Autor: B. Clouston, B. Moore
RFC2233 The Interfaces Group MIB using SMIv2
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. [STANDARDS-TRACK]
November 1997
Status: PROPOSED STANDARD
Autor: K. McCloghrie, F. Kastenholz
RFC2234 Augmented BNF for Syntax Specifications: ABNF
In the early days of the Arpanet, each specification contained its own definition of ABNF. This included the email specifications, RFC733 and then RFC822 which have come to be the common citations for defining ABNF. The current document separates out that definition, to permit selective reference. Predictably, it also provides some modifications and enhancements. [STANDARDS-TRACK]
November 1997
Status: PROPOSED STANDARD
Autor: D. Crocker, P. Overell
RFC2235 Hobbes' Internet Timeline
This document presents a history of the Internet in timeline fashion, highlighting some of the key events and technologies which helped shape the Internet as we know it today. A growth summary of the Internet and some associated technologies is also included. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
November 1997
Status: INFORMATIONAL
Autor: R. Zakon
RFC2236 Internet Group Management Protocol, Version 2
This memo documents IGMPv2, used by IP hosts to report their multicast group memberships to routers. It updates STD 5, RFC 1112. [STANDARDS-TRACK]
November 1997
Status: PROPOSED STANDARD
Autor: W. Fenner
RFC2237 Japanese Character Encoding for Internet Messages
This memo defines an encoding scheme for the Japanese Characters, describes "ISO-2022-JP-1", which is used in electronic mail [RFC-822], and network news [RFC 1036]. Also this memo provides a listing of the Japanese Character Set that can be used in this encoding scheme. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
November 1997
Status: INFORMATIONAL
Autor: K. Tamaru
RFC2238 Definitions of Managed Objects for HPR using SMIv2
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 monitoring and controlling network devices with HPR (High Performance Routing) capabilities. This memo identifies managed objects for the HPR protocol. [STANDARDS-TRACK]
November 1997
Status: PROPOSED STANDARD
Autor: B. Clouston, B. Moore
RFC2239 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2
This memo defines an portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing 10 and 100 Mb/second Medium Attachment Units (MAUs) based on IEEE Std 802.3 Section 30, "10 & 100 Mb/s Management," October 26, 1995. [STANDARDS-TRACK]
November 1997
Status: PROPOSED STANDARD
Autor: K. de Graaf, D. Romascanu, D. McMaster, K. McCloghrie, S. Roberts
RFC2240 A Legal Basis for Domain Name Allocation
The purpose of this memo is to focus discussion on the particular problems with the exhaustion of the top level domain space in the Internet and the possible conflicts that can occur when multiple organisations are vying for the same name. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
November 1997
Status: INFORMATIONAL
Autor: O. Vaughan
RFC2241 DHCP Options for Novell Directory Services
This document defines three new DHCP options for delivering configuration information to clients of the Novell Directory Services. This document defines three new DHCP options for delivering configuration information to clients of the Novell Directory Services. [STANDARDS-TRACK]
November 1997
Status: PROPOSED STANDARD
Autor: D. Provan
RFC2242 NetWare/IP Domain Name and Information
This document defines options that carry NetWare/IP domain name and NetWare/IP sub-options to DHCP clients. [STANDARDS-TRACK]
November 1997
Status: PROPOSED STANDARD
Autor: R. Droms, K. Fong
RFC2243 OTP Extended Responses
This document provides a specification for a type of response to an OTP [RFC 1938] challenge that carries explicit indication of the response's encoding. This document also provides a specification for a response that allows an OTP generator to request that a server re-initialize a sequence and change parameters such as the secret pass phrase. [STANDARDS-TRACK]
November 1997
Status: PROPOSED STANDARD
Autor: C. Metz
RFC2244 ACAP -- Application Configuration Access Protocol
The Application Configuration Access Protocol (ACAP) is designed to support remote storage and access of program option, configuration and preference information. [STANDARDS-TRACK]
November 1997
Status: PROPOSED STANDARD
Autor: C. Newman, J. G. Myers
RFC2245 Anonymous SASL Mechanism
As plaintext login commands are not permitted in new IETF protocols, a new way to provide anonymous login is needed within the context of the SASL [SASL] framework. [STANDARDS-TRACK]
November 1997
Status: PROPOSED STANDARD
Autor: C. Newman
RFC2246 The TLS Protocol Version 1.0
This document specifies Version 1.0 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications privacy over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. [STANDARDS-TRACK]
January 1999
Status: PROPOSED STANDARD
Autor: T. Dierks, C. Allen
RFC2247 Using Domains in LDAP/X.500 Distinguished Names
This document defines an algorithm by which a name registered with the Internet Domain Name Service [2] can be represented as an LDAP distinguished name. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: S. Kille, M. Wahl, A. Grimstad, R. Huber, S. Sataluri
RFC2248 Network Services Monitoring MIB
This MIB may be used on its own for any application, and for most simple applications this will suffice. This MIB is also designed to serve as a building block which can be used in conjunction with application- specific monitoring and management. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: N. Freed, S. Kille
RFC2249 Mail Monitoring MIB
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. Specifically, this memo extends the basic Network Services Monitoring MIB [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: N. Freed, S. Kille
RFC2250 RTP Payload Format for MPEG1/MPEG2 Video
This memo describes a packetization scheme for MPEG video and audio streams. [STANDARDS-TRACK] The purpose of this document is to express the general Internet community's expectations of Computer Security Incident Response Teams (CSIRTs). It is not possible to define a set of requirements that would be appropriate for all teams, but it is possible and helpful to list and describe the general set of topics and issues which are of concern and interest to constituent communities. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
January 1998
Status: PROPOSED STANDARD
Autor: D. Hoffman, G. Fernando, V. Goyal, M. Civanlar
RFC2251 Lightweight Directory Access Protocol (v3)
The protocol described in this document is designed to provide access to directories supporting the X.500 models, while not incurring the resource requirements of the X.500 Directory Access Protocol (DAP). [STANDARDS-TRACK]
December 1997
Status: PROPOSED STANDARD
Autor: M. Wahl, T. Howes, S. Kille
RFC2252 Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions
This document defines a set of syntaxes for LDAPv3, and the rules by which attribute values of these syntaxes are represented as octet strings for transmission in the LDAP protocol. [STANDARDS-TRACK]
December 1997
Status: PROPOSED STANDARD
Autor: M. Wahl, A. Coulbeck, T. Howes, S. Kille
RFC2253 Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names
This specification defines the string format for representing names, which is designed to give a clean representation of commonly used distinguished names, while being able to represent any distinguished name. [STANDARDS-TRACK]
December 1997
Status: PROPOSED STANDARD
Autor: M. Wahl, S. Kille, T. Howes
RFC2254 The String Representation of LDAP Search Filters
This document defines a human-readable string format for representing LDAP search filters. [STANDARDS-TRACK]
December 1997
Status: PROPOSED STANDARD
Autor: T. Howes
RFC2255 The LDAP URL Format
This document describes a format for an LDAP Uniform Resource Locator. [STANDARDS-TRACK]
December 1997
Status: PROPOSED STANDARD
Autor: T. Howes, M. Smith
RFC2256 A Summary of the X.500(96) User Schema for use with LDAPv3
This document provides an overview of the attribute types and object classes defined by the ISO and ITU-T committees in the X.500 documents, in particular those intended for use by directory clients. [STANDARDS-TRACK]
December 1997
Status: PROPOSED STANDARD
Autor: M. Wahl
RFC2257 Agent Extensibility (AgentX) Protocol Version 1
This memo defines a standardized framework for extensible SNMP agents. It defines processing entities called master agents and subagents, a protocol (AgentX) used to communicate between them, and the elements of procedure by which the extensible agent processes SNMP protocol messages. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: M. Daniele, B. Wijnen, D. Francisco
RFC2258 Internet Nomenclator Project
The goal of the Internet Nomenclator Project is to integrate the hundreds of publicly available CCSO servers from around the world. This document provides an overview of the Nomenclator system, describes how to register a CCSO server in the Internet Nomenclator Project, and how to use the Nomenclator search engine to find people on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
January 1998
Status: INFORMATIONAL
Autor: J. Ordille
RFC2259 Simple Nomenclator Query Protocol (SNQP)
The Simple Nomenclator Query Protocol (SNQP) allows a client to communicate with a descriptive name service or other relational-style query service. This memo provides information for the Internet community. It does not specify an Internet standard of any kind
January 1998
Status: INFORMATIONAL
Autor: J. Elliott, J. Ordille
RFC2260 Scalable Support for Multi-homed Multi-provider Connectivity
This document describes addressing and routing strategies for multi- homed enterprises attached to multiple Internet Service Providers (ISPs) that are intended to reduce the routing overhead due to these enterprises in the global Internet routing system. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
January 1998
Status: INFORMATIONAL
Autor: T. Bates, Y. Rekhter
RFC2261 An Architecture for Describing SNMP Management Frameworks
This document describes an architecture for describing SNMP Management Frameworks. The architecture is designed to be modular to allow the evolution of the SNMP protocol standards over time. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: D. Harrington, R. Presuhn, B. Wijnen
RFC2262 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)
This document describes the Message Processing and Dispatching for SNMP messages within the SNMP architecture [RFC2261]. It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP Message Processing Models, and for dispatching PDUs to SNMP applications. This document also describes one Message Processing Model - the SNMPv3 Message Processing Model. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: J. Case, D. Harrington, R. Presuhn, B. Wijnen
RFC2263 SNMPv3 Applications
This memo describes five types of SNMP applications which make use of an SNMP engine as described in [RFC2261]. The types of application described are Command Generators, Command Responders, Notification Originators, Notification Receivers, and Proxy Forwarders. This memo also defines MIB modules for specifying targets of management operations, for notification filtering, and for proxy forwarding. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: D. Levi, P. Meyer, B. Stewart
RFC2264 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)
This document describes the User-based Security Model (USM) for SNMP version 3 for use in the SNMP architecture [RFC2261]. It defines the Elements of Procedure for providing SNMP message level security. This document also includes a MIB for remotely monitoring/managing the configuration parameters for this Security Model. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: U. Blumenthal, B. Wijnen
RFC2265 View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)
This document describes the View-based Access Control Model for use in the SNMP architecture [RFC2261]. It defines the Elements of Procedure for controlling access to management information. This document also includes a MIB for remotely managing the configuration parameters for the View-based Access Control Model. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: B. Wijnen, R. Presuhn, K. McCloghrie
RFC2266 Definitions of Managed Objects for IEEE 802.12 Repeater Devices
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 network repeaters based on IEEE 802.12. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: J. Flick
RFC2267 Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing
This paper discusses a simple, effective, and straightforward method for using ingress traffic filtering to prohibit DoS attacks which use forged IP addresses to be propagated from 'behind' an Internet Service Provider's (ISP) aggregation point. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
January 1998
Status: INFORMATIONAL
Autor: P. Ferguson, D. Senie
RFC2268 A Description of the RC2(r) Encryption Algorithm
This memo describes a conventional (secret-key) block encryption algorithm, called RC2, which may be considered as a proposal for a DES replacement. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
March 1998
Status: INFORMATIONAL
Autor: R. Rivest
RFC2269 Using the MARS Model in non-ATM NBMA Networks
This document is intended to state the obvious equivalences, and explain the less obvious implications. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
January 1998
Status: INFORMATIONAL
Autor: G. Armitage
RFC2270 Using a Dedicated AS for Sites Homed to a Single Provider
With the increased growth of the Internet, the number of customers using BGP4 has grown significantly. RFC1930 outlines a set of guidelines for when one needs and should use an AS. However, the customer and service provider (ISP) are left with a problem as a result of this in that while there is no need for an allocated AS under the guidelines, certain conditions make the use of BGP4 a very pragmatic and perhaps only way to connect a customer homed to a single ISP. This paper proposes a solution to this problem in line with recommendations set forth in RFC1930. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
January 1998
Status: INFORMATIONAL
Autor: J. Stewart, T. Bates, R. Chandra, E. Chen
RFC2271 An Architecture for Describing SNMP Management Frameworks
This document describes an architecture for describing SNMP Management Frameworks. The architecture is designed to be modular to allow the evolution of the SNMP protocol standards over time. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: D. Harrington, R. Presuhn, B. Wijnen
RFC2272 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)
This document describes the Message Processing and Dispatching for SNMP messages within the SNMP architecture [RFC2271]. It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP Message Processing Models, and for dispatching PDUs to SNMP applications. This document also describes one Message Processing Model - the SNMPv3 Message Processing Model. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: J. Case, D. Harrington, R. Presuhn, B. Wijnen
RFC2273 SNMPv3 Applications
This memo describes five types of SNMP applications which make use of an SNMP engine as described in [RFC2261]. The types of application described are Command Generators, Command Responders, Notification Originators, Notification Receivers, and Proxy Forwarders. This memo also defines MIB modules for specifying targets of management operations, for notification filtering, and for proxy forwarding. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: D. Levi, P. Meyer, B. Stewart
RFC2274 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)
This document describes the User-based Security Model (USM) for SNMP version 3 for use in the SNMP architecture [RFC2261]. It defines the Elements of Procedure for providing SNMP message level security. This document also includes a MIB for remotely monitoring/managing the configuration parameters for this Security Model. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: U. Blumenthal, B. Wijnen
RFC2275 View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)
This document describes the View-based Access Control Model for use in the SNMP architecture [RFC2261]. It defines the Elements of Procedure for controlling access to management information. This document also includes a MIB for remotely managing the configuration parameters for the View-based Access Control Model. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: B. Wijnen, R. Presuhn, K. McCloghrie
RFC2276 Architectural Principles of Uniform Resource Name Resolution
This document addresses the issues of the discovery of URN (Uniform Resource Name) resolver services that in turn will directly translate URNs into URLs (Uniform Resource Locators) and URCs (Uniform Resource Characteristics). This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
January 1998
Status: INFORMATIONAL
Autor: K. Sollins
RFC2277 IETF Policy on Character Sets and Languages
This document is the current policies being applied by the Internet Engineering Steering Group (IESG) towards the standardization efforts in the Internet Engineering Task Force (IETF) in order to help Internet protocols fulfill these requirements. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
January 1998
Status: BEST CURRENT PRACTICE
Autor: H. Alvestrand
RFC2278 IANA Charset Registration Procedures
MIME [RFC-2045, RFC-2046, RFC-2047, RFC-2184] and various other modern Internet protocols are capable of using many different charsets. This in turn means that the ability to label different charsets is essential. This registration procedure exists solely to associate a specific name or names with a given charset and to give an indication of whether or not a given charset can be used in MIME text objects. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
January 1998
Status: INFORMATIONAL
Autor: N. Freed, J. Postel
RFC2279 UTF-8, a transformation format of ISO 10646
UTF-8, the object of this memo, has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo updates and replaces RFC 2044, in particular addressing the question of versions of the relevant standards. [STANDARDS-TRACK]
January 1998
Status: DRAFT STANDARD
Autor: F. Yergeau
RFC2280 Routing Policy Specification Language (RPSL)
This memo is the reference document for the Routing Policy Specification Language (RPSL). RPSL allows a network operator to be able to specify routing policies at various levels in the Internet hierarchy; for example at the Autonomous System (AS) level. At the same time, policies can be specified with sufficient detail in RPSL so that low level router configurations can be generated from them. RPSL is extensible; new routing protocols and new protocol features can be introduced at any time. [STANDARDS-TRACK]
January 1998
Status: PROPOSED STANDARD
Autor: C. Alaettinoglu, T. Bates, E. Gerich, D. Karrenberg, D. Meyer, M. Terpstra, C. Villamizar
RFC2281 Cisco Hot Standby Router Protocol (HSRP)
The memo specifies the Hot Standby Router Protocol (HSRP). The goal of the protocol is to allow hosts to appear to use a single router and to maintain connectivity even if the actual first hop router they are using fails. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
March 1998
Status: INFORMATIONAL
Autor: T. Li, B. Cole, P. Morton, D. Li
RFC2282 IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees
The process by which the members of the IAB and IESG are selected, confirmed, and recalled is specified. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
February 1998
Status: INFORMATIONAL
Autor: J. Galvin
RFC2283 Multiprotocol Extensions for BGP-4
This document defines extensions to BGP-4 to enable it to carry routing information for multiple Network Layer protocols (e.g., IPv6, IPX, etc...). The extensions are backward compatible - a router that supports the extensions can interoperate with a router that doesn't support the extensions. [STANDARDS-TRACK]
February 1998
Status: PROPOSED STANDARD
Autor: T. Bates, R. Chandra, D. Katz, Y. Rekhter
RFC2284 PPP Extensible Authentication Protocol (EAP)
The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams 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 the PPP Extensible Authentication Protocol. [STANDARDS-TRACK]
March 1998
Status: PROPOSED STANDARD
Autor: L. Blunk, J. Vollbrecht
RFC2285 Benchmarking Terminology for LAN Switching Devices
This document is intended to provide terminology for the benchmarking of local area network (LAN) switching devices. It extends the terminology already defined for benchmarking network interconnect devices in RFCs 1242 and 1944 to switching devices. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
February 1998
Status: INFORMATIONAL
Autor: R. Mandeville
RFC2286 Test Cases for HMAC-RIPEMD160 and HMAC-RIPEMD128
This document provides two sets of test cases for HMAC-RIPEMD160 and HMAC-RIPEMD128. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
February 1998
Status: INFORMATIONAL
Autor: J. Kapp
RFC2287 Definitions of System-Level Managed Objects for Applications
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 basic set of managed objects for fault, configuration and performance management of applications from a systems perspective. [STANDARDS-TRACK]
February 1998
Status: PROPOSED STANDARD
Autor: C. Krupczak, J. Saperia
RFC2288 Using Existing Bibliographic Identifiers as Uniform Resource Names
This document discusses how three major bibliographic identifiers (the ISBN, ISSN and SICI) can be supported within the URN framework and the currently proposed syntax for URNs. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
February 1998
Status: INFORMATIONAL
Autor: C. Lynch, C. Preston, R. Daniel
RFC2289 A One-Time Password System
This document describes a one-time password authentication system (OTP). The system provides authentication for system access (login) and other applications requiring authentication that is secure against passive attacks based on replaying captured reusable passwords. [STANDARDS-TRACK]
February 1998
Status: STANDARD
Autor: N. Haller, C. Metz, P. Nesser, M. Straw
RFC2290 Mobile-IPv4 Configuration Option for PPP IPCP
Mobile IP [RFC 2002] defines media-independent procedures by which a Mobile Node can maintain existing transport and application-layer connections despite changing its point-of-attachment to the Internet and without changing its IP address. PPP [RFC 1661] provides a standard method for transporting multi-protocol packets over point-to-point links. As currently specified, Mobile IP Foreign Agents which support Mobile Node connections via PPP can do so only by first assigning unique addresses to those Mobile Nodes, defeating one of the primary advantages of Foreign Agents. This documents corrects this problem by defining the Mobile-IPv4 Configuration Option to the Internet Protocol Control Protocol (IPCP) [RFC 1332]. Using this option, two peers can communicate their support for Mobile IP during the IPCP phase of PPP. Familiarity with Mobile IP [RFC 2002], IPCP [RFC 1332], and PPP [RFC 1661] is assumed. [STANDARDS-TRACK]
February 1998
Status: PROPOSED STANDARD
Autor: J. Solomon, S. Glass
RFC2291 Requirements for a Distributed Authoring and Versioning Protocol for the World Wide Web
This document presents a list of features in the form of requirements for a Web Distributed Authoring and Versioning protocol which, if implemented, would improve the efficiency of common remote editing operations, provide a locking mechanism to prevent overwrite conflicts, improve link management support between non-HTML data types, provide a simple attribute-value metadata facility, provide for the creation and reading of container data types, and integrate versioning into the WWW. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
February 1998
Status: INFORMATIONAL
Autor: J. Slein, F. Vitali, E. Whitehead, D. Durand
RFC2292 Advanced Sockets API for IPv6
The current document defines some the "advanced" features of the sockets API that are required for applications to take advantage of additional features of IPv6. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
February 1998
Status: INFORMATIONAL
Autor: W. Stevens, M. Thomas
RFC2293 Representing Tables and Subtrees in the X.500 Directory
This document defines techniques for representing two types of information mapping in the OSI Directory: Mapping from a key to a value (or set of values), as might be done in a table lookup, and mapping from a distinguished name to an associated value (or values), where the values are not defined by the owner of the entry. This is achieved by use of a directory subtree. [STANDARDS-TRCK]
March 1998
Status: PROPOSED STANDARD
Autor: S. Kille
RFC2294 Representing the O/R Address hierarchy in the X.500 Directory Information Tree
This document defines a representation of the O/R Address hierarchy in the Directory Information Tree. [STANDARDS-TRACK]
March 1998
Status: PROPOSED STANDARD
Autor: S. Kille
RFC2295 Transparent Content Negotiation in HTTP
HTTP allows web site authors to put multiple versions of the same information under a single URL. Transparent content negotiation is an extensible negotiation mechanism, layered on top of HTTP, for automatically selecting the best version when the URL is accessed. This enables the smooth deployment of new web data formats and markup tags. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested.
March 1998
Status: EXPERIMENTAL
Autor: K. Holtman, A. Mutz
RFC2296 HTTP Remote Variant Selection Algorithm -- RVSA/1.0
HTTP allows web site authors to put multiple versions of the same information under a single URL. Transparent content negotiation is a mechanism for automatically selecting the best version when the URL is accessed. A remote variant selection algorithm can be used to speed up the transparent negotiation process. This document defines the remote variant selection algorithm with the version number 1.0. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested.
March 1998
Status: EXPERIMENTAL
Autor: K. Holtman, A. Mutz
RFC2297 Ipsilon's General Switch Management Protocol Specification Version 2.0
This memo specifies enhancements to the General Switch Management Protocol (GSMP) [RFC1987]. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
March 1998
Status: INFORMATIONAL
Autor: P. Newman, W. Edwards, R. Hinden, E. Hoffman, F. Ching Liaw, T. Lyon, G. Minshall
RFC2298 An Extensible Message Format for Message Disposition Notifications
This memo defines a MIME content-type that may be used by a mail user agent (UA) or electronic mail gateway to report the disposition of a message after it has been sucessfully delivered to a recipient. [STANDARDS-TRACK]
March 1998
Status: PROPOSED STANDARD
Autor: R. Fajman
RFC2299 Request for Comments Summary
January 1999
Status: INFORMATIONAL
Autor: A. Ramos
RFC2300 Internet Official Protocol Standards
A discussion of the standardization process and the RFC document series is presented first, followed by an explanation of the terms. Sections 6.2 - 6.10 contain the lists of protocols in each stage of standardization. Finally are pointers to references and contacts for further information. [STANDARDS-TRACK]
May 1998
Status: HISTORIC
Autor: J. Postel
RFC2301 File Format for Internet Fax
This document describes the TIFF (Tag Image File Format) representation of image data specified by the ITU-T Recommendations for black-and-white and color facsimile. [STANDARDS-TRACK]
March 1998
Status: PROPOSED STANDARD
Autor: L. McIntyre, S. Zilles, R. Buckley, D. Venable, G. Parsons, J. Rafferty
RFC2302 Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration
This document describes the registration of the MIME sub-type image/tiff. [STANDARDS-TRACK]
March 1998
Status: PROPOSED STANDARD
Autor: G. Parsons, J. Rafferty, S. Zilles
RFC2303 Minimal PSTN address format in Internet Mail
This memo describes the MINIMAL addressing method to encode PSTN addresses into e-mail addresses and the standard extension mechanism to allow definition of further standard elements. [STANDARDS-TRACK]
March 1998
Status: PROPOSED STANDARD
Autor: C. Allocchio
RFC2304 Minimal FAX address format in Internet Mail
This memo describes the MINIMAL addressing method and standard extensions to encode FAX addresses in e-mail addresses. [STANDARDS-TRACK]
March 1998
Status: PROPOSED STANDARD
Autor: C. Allocchio
RFC2305 A Simple Mode of Facsimile Using Internet Mail
This specification provides for "simple mode" carriage of facsimile data over the Internet. [STANDARDS-TRACK]
March 1998
Status: PROPOSED STANDARD
Autor: K. Toyoda, H. Ohno, J. Murai, D. Wing
RFC2306 Tag Image File Format (TIFF) - F Profile for Facsimile
This document describes in detail the definition of TIFF-F that is used to store facsimile images. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
March 1998
Status: INFORMATIONAL
Autor: G. Parsons, J. Rafferty
RFC2307 An Approach for Using LDAP as a Network Information Service
This document describes an experimental mechanism for mapping entities related to TCP/IP and the UNIX system into X.500 entries so that they may be resolved with the Lightweight Directory Access Protocol [RFC2251]. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested.
March 1998
Status: EXPERIMENTAL
Autor: L. Howard
RFC2308 Negative Caching of DNS Queries (DNS NCACHE)
RFC1034 provided a description of how to cache negative responses. It however had a fundamental flaw in that it did not allow a name server to hand out those cached responses to other resolvers, thereby greatly reducing the effect of the caching. This document addresses issues raise in the light of experience and replaces RFC1034 Section 4.3.4. [STANDARDS-TRACK]
March 1998
Status: PROPOSED STANDARD
Autor: M. Andrews
RFC2309 Recommendations on Queue Management and Congestion Avoidance in the Internet
This memo presents two recommendations to the Internet community concerning measures to improve and preserve Internet performance. It presents a strong recommendation for testing, standardization, and widespread deployment of active queue management in routers, to improve the performance of today's Internet. It also urges a concerted effort of research, measurement, and ultimate deployment of router mechanisms to protect the Internet from flows that are not sufficiently responsive to congestion notification. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
April 1998
Status: INFORMATIONAL
Autor: B. Braden, D. Clark, J. Crowcroft, B. Davie, S. Deering, D. Estrin, S. Floyd, V. Jacobson, G. Minshall, C. Partridge, L. Peterson, K. Ramakrishnan, S. Shenker, J. Wroclawski, L. Zhang
RFC2310 The Safe Response Header Field
This document defines a HTTP response header field called Safe, which can be used to indicate that repeating a HTTP request is safe. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested.
April 1998
Status: EXPERIMENTAL
Autor: K. Holtman
RFC2311 S/MIME Version 2 Message Specification
This document describes a protocol for adding cryptographic signature and encryption services to MIME data. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
March 1998
Status: HISTORIC
Autor: S. Dusse, P. Hoffman, B. Ramsdell, L. Lundblade, L. Repka
RFC2312 S/MIME Version 2 Certificate Handling
This memo describes the mechanisms S/MIME uses to create and validate keys using certificates. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
March 1998
Status: HISTORIC
Autor: S. Dusse, P. Hoffman, B. Ramsdell, J. Weinstein
RFC2313 PKCS #1: RSA Encryption Version 1.5
This document describes a method for encrypting data using the RSA public-key cryptosystem. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
March 1998
Status: INFORMATIONAL
Autor: B. Kaliski
RFC2314 PKCS #10: Certification Request Syntax Version 1.5
This document describes a syntax for certification requests. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
March 1998
Status: INFORMATIONAL
Autor: B. Kaliski
RFC2315 PKCS #7: Cryptographic Message Syntax Version 1.5
This document describes a general syntax for data that may have cryptography applied to it, such as digital signatures and digital envelopes. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
March 1998
Status: INFORMATIONAL
Autor: B. Kaliski
RFC2316 Report of the IAB Security Architecture Workshop
On 3-5 March 1997, the IAB held a security architecture workshop at Bell Labs in Murray Hill, NJ. We identified the core security components of the architecture, and specified several documents that need to be written. Most importantly, we agreed that security was not optional, and that it needed to be designed in from the beginning. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
April 1998
Status: INFORMATIONAL
Autor: S. Bellovin
RFC2317 Classless IN-ADDR.ARPA delegation
This document describes a way to do IN-ADDR.ARPA delegation on non-octet boundaries for address spaces covering fewer than 256 addresses. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
March 1998
Status: BEST CURRENT PRACTICE
Autor: H. Eidnes, G. de Groot, P. Vixie
RFC2318 The text/css Media Type
This memo provides information about the text/css Media Type. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
March 1998
Status: INFORMATIONAL
Autor: H. Lie, B. Bos, C. Lilley
RFC2319 Ukrainian Character Set KOI8-U
This document provides information about character encoding KOI8-U (KOI8 Ukrainian) wich is a de-facto standard in Ukrainian Internet community. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
April 1998
Status: INFORMATIONAL
Autor: KOI8-U Working Group
RFC2320 Definitions of Managed Objects for Classical IP and ARP Over ATM Using SMIv2 (IPOA-MIB)
The purpose of this memo is to define the Management Information Base (MIB) for supporting Classical IP and ARP over ATM as specified in Classical IP and ARP over ATM. [STANDARDS-TRACK]
April 1998
Status: PROPOSED STANDARD
Autor: M. Greene, J. Luciani, K. White, T. Kuo
RFC2321 RITA -- The Reliable Internetwork Troubleshooting Agent
A Description of the usage of Nondeterministic Troubleshooting and Diagnostic Methodologies as applied to today's complex nondeterministic networks and environments. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
April 1998
Status: INFORMATIONAL
Autor: A. Bressen
RFC2322 Management of IP numbers by peg-dhcp
This RFC describes a protocol to dynamically hand out ip-numbers on field networks and small events that don't necessarily have a clear organisational body. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
April 1998
Status: INFORMATIONAL
Autor: K. van den Hout, A. Koopal, R. van Mook
RFC2323 IETF Identification and Security Guidelines
This RFC is meant to represent a guideline by which the IETF conferences may run more effeciently with regards to identification and security protocols, with specific attention paid to a particular sub-group within the IETF: "facial hairius extremis". This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
April 1998
Status: INFORMATIONAL
Autor: A. Ramos
RFC2324 Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)
This document describes HTCPCP, a protocol for controlling, monitoring, and diagnosing coffee pots. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
April 1998
Status: INFORMATIONAL
Autor: L. Masinter
RFC2325 Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
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 coffee-brewing and maintenance devices. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
April 1998
Status: INFORMATIONAL
Autor: M. Slavitch
RFC2326 Real Time Streaming Protocol (RTSP)
The Real Time Streaming Protocol, or RTSP, is an application-level protocol for control over the delivery of data with real-time properties. RTSP provides an extensible framework to enable controlled, on-demand delivery of real-time data, such as audio and video. [STANDARDS-TRACK]
April 1998
Status: PROPOSED STANDARD
Autor: H. Schulzrinne, A. Rao, R. Lanphier
RFC2327 SDP: Session Description Protocol
This document defines the Session Description Protocol, SDP. SDP is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. [STANDARDS-TRACK]
April 1998
Status: PROPOSED STANDARD
Autor: M. Handley, V. Jacobson
RFC2328 OSPF Version 2
This memo documents version 2 of the OSPF protocol. OSPF is a link- state routing protocol. [STANDARDS-TRACK]
April 1998
Status: STANDARD
Autor: J. Moy
RFC2329 OSPF Standardization Report
This memo documents how the requirements for advancing a routing protocol to Full Standard have been met for OSPFv2. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
April 1998
Status: INFORMATIONAL
Autor: J. Moy
RFC2330 Framework for IP Performance Metrics
The purpose of this memo is to define a general framework for particular metrics to be developed by the IETF's IP Performance Metrics effort. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
May 1998
Status: INFORMATIONAL
Autor: V. Paxson, G. Almes, J. Mahdavi, M. Mathis
RFC2331 ATM Signalling Support for IP over ATM - UNI Signalling 4.0 Update
This memo describes how to efficiently use the ATM call control signalling procedures defined in UNI Signalling 4.0 to support IP over ATM environments as described in RFC 2225 and in RFC 2332. [STANDARDS-TRACK]
April 1998
Status: PROPOSED STANDARD
Autor: M. Maher
RFC2332 NBMA Next Hop Resolution Protocol (NHRP)
This document describes the NBMA Next Hop Resolution Protocol (NHRP). NHRP can be used by a source station (host or router) connected to a Non-Broadcast, Multi-Access (NBMA) subnetwork to determine the internetworking layer address and NBMA subnetwork addresses of the "NBMA next hop" towards a destination station. [STANDARDS-TRACK]
April 1998
Status: PROPOSED STANDARD
Autor: J. Luciani, D. Katz, D. Piscitello, B. Cole, N. Doraswamy
RFC2333 NHRP Protocol Applicability Statement
As required by the Routing Protocol Criteria [RFC 1264], this memo discusses the applicability of the Next Hop Resolution Protocol (NHRP) in routing of IP datagrams over Non-Broadcast Multiple Access (NBMA) networks, such as ATM, SMDS and X.25. [STANDARDS-TRACK]
April 1998
Status: PROPOSED STANDARD
Autor: D. Cansever
RFC2334 Server Cache Synchronization Protocol (SCSP)
This document describes the Server Cache Synchronization Protocol (SCSP) and is written in terms of SCSP's use within Non Broadcast Multiple Access (NBMA) networks; although, a somewhat straight forward usage is applicable to BMA networks. [STANDARDS-TRACK]
April 1998
Status: PROPOSED STANDARD
Autor: J. Luciani, G. Armitage, J. Halpern, N. Doraswamy
RFC2335 A Distributed NHRP Service Using SCSP
This document describes a method for distributing an NHRP service within a LIS. [STANDARDS-TRACK]
April 1998
Status: PROPOSED STANDARD
Autor: J. Luciani
RFC2336 Classical IP to NHRP Transition
This document describes methods and procedures for the graceful transition from an ATMARP LIS to an NHRP LIS network model over ATM. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
July 1998
Status: INFORMATIONAL
Autor: J. Luciani
RFC2337 Intra-LIS IP multicast among routers over ATM using Sparse Mode PIM
This document describes how intra-LIS IP multicast can be efficiently supported among routers over ATM without using the Multicast Address Resolution Server (MARS). This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested.
April 1998
Status: EXPERIMENTAL
Autor: D. Farinacci, D. Meyer, Y. Rekhter
RFC2338 Virtual Router Redundancy Protocol
This memo defines the Virtual Router Redundancy Protocol (VRRP). VRRP specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. [STANDARDS-TRACK]
April 1998
Status: PROPOSED STANDARD
Autor: S. Knight, D. Weaver, D. Whipple, R. Hinden, D. Mitzel, P. Hunt, P. Higginson, M. Shand, A. Lindem
RFC2339 An Agreement Between the Internet Society, the IETF, and Sun Microsystems, Inc. in the matter of NFS V.4 Protocols
This Request for Comments records an agreement between Sun Microsystems, Inc. and the Internet Society to permit the flow of Sun's Network File System specifications into the Internet Standards process conducted by the Internet Engineering Task Force. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
May 1998
Status: INFORMATIONAL
Autor: The Internet Society, Sun Microsystems
RFC2340 Nortel's Virtual Network Switching (VNS) Overview
This document provides an overview of Virtual Network Switching (VNS). This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
May 1998
Status: INFORMATIONAL
Autor: B. Jamoussi, D. Jamieson, D. Williston, S. Gabe
RFC2341 Cisco Layer Two Forwarding (Protocol) "L2F"
This document describes the Layer Two Forwarding protocol (L2F) which permits the tunneling of the link layer (i.e., HDLC, async HDLC, or SLIP frames) of higher level protocols. This memo describes a historic protocol for the Internet community. It does not specify an Internet standard of any kind.
May 1998
Status: HISTORIC
Autor: A. Valencia, M. Littlewood, T. Kolar
RFC2342 IMAP4 Namespace
This document defines a NAMESPACE command that allows a client to discover the prefixes of namespaces used by a server for personal mailboxes, other users' mailboxes, and shared mailboxes. [STANDARDS-TRACK]
May 1998
Status: PROPOSED STANDARD
Autor: M. Gahrns, C. Newman
RFC2343 RTP Payload Format for Bundled MPEG
This document describes a payload type for bundled, MPEG-2 encoded video and audio data that may be used with RTP, version 2. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested.
May 1998
Status: EXPERIMENTAL
Autor: M. Civanlar, G. Cash, B. Haskell
RFC2344 Reverse Tunneling for Mobile IP
This document proposes backwards-compatible extensions to Mobile IP in order to support topologically correct reverse tunnels. [STANDARDS-TRACK]
May 1998
Status: PROPOSED STANDARD
Autor: G. Montenegro
RFC2345 Domain Names and Company Name Retrieval
This document proposes a company name to URL mapping service based on the oldest and least complex of Internet directory protocols, whois, in order to explore whether an extremely simple and widely-deployed protocol can succeed where more complex and powerful options have failed or been excessively delayed. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested.
May 1998
Status: EXPERIMENTAL
Autor: J. Klensin, T. Wolf, G. Oglesby
RFC2346 Making Postscript and PDF International
Certain text formats, for example Postscript (MIME-Type: application/postscript; file extension .ps) and Portable Document Format (MIME-Type: application/pdf; file extension .pdf) specify exactly the page layout of the printed document. The commonly used paper format is different in North America and the rest of the world. North America uses the 'Letter' format, while the rest of the world mostly uses the ISO-standard 'A4' format. This means that documents formatted on one continent may not be easily printable on another continent. This memo gives advice on how to produce documents which are equally well printable with the Letter and the A4 formats. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
May 1998
Status: INFORMATIONAL
Autor: J. Palme
RFC2347 TFTP Option Extension
The Trivial File Transfer Protocol is a simple, lock-step, file transfer protocol which allows a client to get or put a file onto a remote host. This document describes a simple extension to TFTP to allow option negotiation prior to the file transfer. [STANDARDS-TRACK]
May 1998
Status: DRAFT STANDARD
Autor: G. Malkin, A. Harkin
RFC2348 TFTP Blocksize Option
The Trivial File Transfer Protocol is a simple, lock-step, file transfer protocol which allows a client to get or put a file onto a remote host. This document describes a TFTP option which allows the client and server to negotiate a blocksize more applicable to the network medium. [STANDARDS-TRACK]
May 1998
Status: DRAFT STANDARD
Autor: G. Malkin, A. Harkin
RFC2349 TFTP Timeout Interval and Transfer Size Options
The Trivial File Transfer Protocol is a simple, lock-step, file transfer protocol which allows a client to get or put a file onto a remote host. This document describes two TFTP options. [STANDARDS-TRACK]
May 1998
Status: DRAFT STANDARD
Autor: G. Malkin, A. Harkin
RFC2350 Expectations for Computer Security Incident Response
June 1998
Status: BEST CURRENT PRACTICE
Autor: N. Brownlee, E. Guttman
RFC2351 Mapping of Airline Reservation, Ticketing, and Messaging Traffic over IP
This memo specifies a protocol for the encapsulation of the airline specific protocol over IP. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
May 1998
Status: INFORMATIONAL
Autor: A. Robert
RFC2352 A Convention For Using Legal Names as Domain Names
The purpose of this memo is to focus discussion on the particular problems with the exhaustion of the top level domain space in the Internet and the possible conflicts that can occur when multiple organisations are vying for the same name. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
May 1998
Status: INFORMATIONAL
Autor: O. Vaughan
RFC2353 APPN/HPR in IP Networks APPN Implementers' Workshop Closed Pages Document
This memo defines a method with which HPR nodes can use IP networks for communication, and the enhancements to APPN required by this method. This memo also describes an option set that allows the use of the APPN connection network model to allow HPR nodes to use IP networks for communication without having to predefine link connections. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
May 1998
Status: INFORMATIONAL
Autor: G. Dudley
RFC2354 Options for Repair of Streaming Media
This document summarizes a range of possible techniques for the repair of continuous media streams subject to packet loss. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1998
Status: INFORMATIONAL
Autor: C. Perkins, O. Hodson
RFC2355 TN3270 Enhancements
This document describes a protocol that more fully supports 3270 devices than do traditional tn3270 practices. [STANDARDS-TRACK]
June 1998
Status: DRAFT STANDARD
Autor: B. Kelly
RFC2356 Sun's SKIP Firewall Traversal for Mobile IP
The Mobile IP specification establishes the mechanisms that enable a mobile host to maintain and use the same IP address as it changes its point of attachment to the network. The mechanisms described in this document allow a mobile node out on a public sector of the internet to negotiate access past a SKIP firewall, and construct a secure channel into its home network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
June 1998
Status: INFORMATIONAL
Autor: G. Montenegro, V. Gupta
RFC2357 IETF Criteria for Evaluating Reliable Multicast Transport and Application Protocols
This memo describes the procedures and criteria for reviewing reliable multicast protocols within the Transport Area (TSV) of the IETF. Within today's Internet, important applications exist for a reliable multicast service. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
June 1998
Status: INFORMATIONAL
Autor: A. Mankin, A. Romanow, S. Bradner, V. Paxson
RFC2358 Definitions of Managed Objects for the Ethernet-like Interface Types
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This memo obsoletes RFC 1650 "Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2". This memo extends that specification by including management information useful for the management of 100 Mb/s Ethernet interfaces. [STANDARDS-TRACK]
June 1998
Status: PROPOSED STANDARD
Autor: J. Flick, J. Johnson
RFC2359 IMAP4 UIDPLUS extension
The UIDPLUS extension of the Internet Message Access Protocol [IMAP4] provides a set of features intended to reduce the amount of time and resources used by some client operations. [STANDARDS-TRACK]
June 1998
Status: PROPOSED STANDARD
Autor: J. Myers
RFC2360 Guide for Internet Standards Writers
This document is a guide for Internet standard writers. It defines those characteristics that make standards coherent, unambiguous, and easy to interpret. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
June 1998
Status: BEST CURRENT PRACTICE
Autor: G. Scott
RFC2361 WAVE and AVI Codec Registries
The purpose of this paper is to establish a mechanism by which codecs registered within Microsoft's WAVE and AVI Registries may be referenced within the IANA Namespace by Internet applications. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
June 1998
Status: INFORMATIONAL
Autor: E. Fleischman
RFC2362 Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification
This document describes a protocol for efficiently routing to multicast groups that may span wide-area (and inter-domain) internets. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested.
June 1998
Status: EXPERIMENTAL
Autor: D. Estrin, D. Farinacci, A. Helmy, D. Thaler, S. Deering, M. Handley, V. Jacobson, C. Liu, P. Sharma, L. Wei
RFC2363 PPP Over FUNI
This document describes the use of ATM Frame User Network Interface (FUNI) for framing PPP encapsulated packets. [STANDARDS-TRACK]
July 1998
Status: PROPOSED STANDARD
Autor: G. Gross, M. Kaycee, A. Li, A. Malis, J. Stephens
RFC2364 PPP Over AAL5
This document describes the use of ATM Adaptation Layer 5 (AAL5) for framing PPP encapsulated packets. [STANDARDS-TRACK]
July 1998
Status: PROPOSED STANDARD
Autor: G. Gross, M. Kaycee, A. Li, A. Malis, J. Stephens
RFC2365 Administratively Scoped IP Multicast
This document defines the "administratively scoped IPv4 multicast space" to be the range 239.0.0.0 to 239.255.255.255. In addition, it describes a simple set of semantics for the implementation of Administratively Scoped IP Multicast. Finally, it provides a mapping between the IPv6 multicast address classes [RFC1884] and IPv4 multicast address classes. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
July 1998
Status: BEST CURRENT PRACTICE
Autor: D. Meyer
RFC2366 Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks
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 for IP hosts and routers that use a Multicast Address Resolution Server (MARS) to support IP multicast over ATM, as described in 'Support for Multicast over UNI 3.0/3.1 based ATM Networks'. [STANDARDS-TRACK]
July 1998
Status: PROPOSED STANDARD
Autor: C. Chung, M. Greene
RFC2367 PF_KEY Key Management API, Version 2
A generic key management API that can be used not only for IP Security but also for other network security services is presented in this document. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
July 1998
Status: INFORMATIONAL
Autor: D. McDonald, C. Metz, B. Phan
RFC2368 The mailto URL scheme
This document defines the format of Uniform Resource Locators (URL) for designating electronic mail addresses. [STANDARDS-TRACK]
July 1998
Status: PROPOSED STANDARD
Autor: P. Hoffman, L. Masinter, J. Zawinski
RFC2369 The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields
The mailing list command specification header fields are a set of structured fields to be added to email messages sent by email distribution lists. By including these header fields, list servers can make it possible for mail clients to provide automated tools for users to perform list functions. This could take the form of a menu item, push button, or other user interface element. The intent is to simplify the user experience, providing a common interface to the often cryptic and varied mailing list manager commands. [STANDARDS-TRACK]
July 1998
Status: PROPOSED STANDARD
Autor: G. Neufeld, J. Baer
RFC2370 The OSPF Opaque LSA Option
This memo defines enhancements to the OSPF protocol to support a new class of link-state advertisements (LSA) called Opaque LSAs. [STANDARDS-TRACK]
July 1998
Status: PROPOSED STANDARD
Autor: R. Coltun
RFC2371 Transaction Internet Protocol Version 3.0
In many applications where different nodes cooperate on some work, there is a need to guarantee that the work happens atomically. That is, each node must reach the same conclusion as to whether the work is to be completed, even in the face of failures. This document proposes a simple, easily-implemented protocol for achieving this end. [STANDARDS-TRACK]
July 1998
Status: PROPOSED STANDARD
Autor: J. Lyon, K. Evans, J. Klein
RFC2372 Transaction Internet Protocol - Requirements and Supplemental Information
This document describes the purpose (usage scenarios), and requirements for the Transaction Internet Protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
July 1998
Status: INFORMATIONAL
Autor: K. Evans, J. Klein, J. Lyon
RFC2373 IP Version 6 Addressing Architecture
This specification defines the addressing architecture of the IP Version 6 protocol [IPV6]. [STANDARDS-TRACK]
July 1998
Status: PROPOSED STANDARD
Autor: R. Hinden, S. Deering
RFC2374 An IPv6 Aggregatable Global Unicast Address Format
This document defines an IPv6 aggregatable global unicast address format for use in the Internet. [STANDARDS-TRACK]
July 1998
Status: HISTORIC
Autor: R. Hinden, M. O'Dell, S. Deering
RFC2375 IPv6 Multicast Address Assignments
This document defines the initial assignment of IPv6 multicast addresses. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
July 1998
Status: INFORMATIONAL
Autor: R. Hinden, S. Deering
RFC2376 XML Media Types
This document proposes two new media subtypes, text/xml and application/xml, for use in exchanging network entities which are conforming Extensible Markup Language (XML). This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
July 1998
Status: INFORMATIONAL
Autor: E. Whitehead, M. Murata
RFC2377 Naming Plan for Internet Directory-Enabled Applications
Application of the conventional X.500 approach to naming has heretofore, in the experience of the authors, proven to be an obstacle to the wide deployment of directory-enabled applications on the Internet. We propose a new directory naming plan that leverages the strengths of the most popular and successful Internet naming schemes for naming objects in a hierarchical directory. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
September 1998
Status: INFORMATIONAL
Autor: A. Grimstad, R. Huber, S. Sataluri, M. Wahl
RFC2378 The CCSO Nameserver (Ph) Architecture
The Ph Nameserver from the Computing and Communications Services Office (CCSO), University of Illinois at Urbana-Champaign has for some time now been used by several organizations as their choice of publicly available database for information about people as well as other things. This document provides a formal definition of the client-server protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
September 1998
Status: INFORMATIONAL
Autor: R. Hedberg, P. Pomes
RFC2379 RSVP over ATM Implementation Guidelines
This memo presents specific implementation guidelines for running RSVP over ATM switched virtual circuits (SVCs). This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
August 1998
Status: BEST CURRENT PRACTICE
Autor: L. Berger
RFC2380 RSVP over ATM Implementation Requirements
This memo presents specific implementation requirements for running RSVP over ATM switched virtual circuits (SVCs). It presents requirements that ensure interoperability between multiple implementations and conformance to the RSVP and Integrated Services specifications. [STANDARDS-TRACK]
August 1998
Status: PROPOSED STANDARD
Autor: L. Berger
RFC2381 Interoperation of Controlled-Load Service and Guaranteed Service with ATM
This document provides guidelines for mapping service classes, and traffic management features and parameters between Internet and ATM technologies. [STANDARDS-TRACK]
August 1998
Status: PROPOSED STANDARD
Autor: M. Garrett, M. Borden
RFC2382 A Framework for Integrated Services and RSVP over ATM
This document outlines the issues and framework related to providing IP Integrated Services with RSVP over ATM. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
August 1998
Status: INFORMATIONAL
Autor: E. Crawley, L. Berger, S. Berson, F. Baker, M. Borden, J. Krawczyk
RFC2383 ST2+ over ATM Protocol Specification - UNI 3.1 Version
This document specifies an ATM-based protocol for communication between ST2+ agents. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
August 1998
Status: INFORMATIONAL
Autor: M. Suzuki
RFC2384 POP URL Scheme
This memo defines a URL scheme for referencing a POP mailbox. [STANDARDS-TRACK]
August 1998
Status: PROPOSED STANDARD
Autor: R. Gellens
RFC2385 Protection of BGP Sessions via the TCP MD5 Signature Option
This memo describes a TCP extension to enhance security for BGP. [STANDARDS-TRACK]
August 1998
Status: PROPOSED STANDARD
Autor: A. Heffernan
RFC2386 A Framework for QoS-based Routing in the Internet
This document describes some of the QoS-based routing issues and requirements, and proposes a framework for QoS-based routing in the Internet. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
August 1998
Status: INFORMATIONAL
Autor: E. Crawley, R. Nair, B. Rajagopalan, H. Sandick
RFC2387 The MIME Multipart/Related Content-type
This document defines the Multipart/Related content-type and provides examples of its use. [STANDARDS-TRACK]
August 1998
Status: PROPOSED STANDARD
Autor: E. Levinson
RFC2388 Returning Values from Forms: multipart/form-data
This specification defines an Internet Media Type, multipart/form-data, which can be used by a wide variety of applications and transported by a wide variety of protocols as a way of returning a set of values as the result of a user filling out a form. [STANDARDS-TRACK]
August 1998
Status: PROPOSED STANDARD
Autor: L. Masinter
RFC2389 Feature negotiation mechanism for the File Transfer Protocol
This document provides a mechanism by which clients of the FTP protocol can discover which new features are supported by a particular FTP server. [STANDARDS-TRACK]
August 1998
Status: PROPOSED STANDARD
Autor: P. Hethmon, R. Elz
RFC2390 Inverse Address Resolution Protocol
This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK]
September 1998
Status: DRAFT STANDARD
Autor: T. Bradley, C. Brown, A. Malis
RFC2391 Load Sharing using IP Network Address Translation (LSNAT)
In this document, we extend the use of NATs to offer Load share feature, where session load can be distributed across a pool of servers, instead of directing to a single server. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
August 1998
Status: INFORMATIONAL
Autor: P. Srisuresh, D. Gan
RFC2392 Content-ID and Message-ID Uniform Resource Locators
The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow references to messages and the body parts of messages. For example, within a single multipart message, one HTML body part might include embedded references to other parts of the same message. [STANDARDS-TRACK]
August 1998
Status: PROPOSED STANDARD
Autor: E. Levinson
RFC2393 IP Payload Compression Protocol (IPComp)
This document describes a protocol intended to provide lossless compression for Internet Protocol datagrams in an Internet environment. [STANDARDS-TRACK]
December 1998
Status: PROPOSED STANDARD
Autor: A. Shacham, R. Monsour, R. Pereira, M. Thomas
RFC2394 IP Payload Compression Using DEFLATE
This document describes a compression method based on the DEFLATE compression algorithm. This document defines the application of the DEFLATE algorithm to the IP Payload Compression Protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
December 1998
Status: INFORMATIONAL
Autor: R. Pereira
RFC2395 IP Payload Compression Using LZS
This document describes a compression method based on the LZS compression algorithm. This document defines the application of the LZS algorithm to the IP Payload Compression Protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
December 1998
Status: INFORMATIONAL
Autor: R. Friend, R. Monsour
RFC2396 Uniform Resource Identifiers (URI): Generic Syntax
This document defines a grammar that is a superset of all valid URI, such that an implementation can parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier type. [STANDARDS-TRACK]
August 1998
Status: DRAFT STANDARD
Autor: T. Berners-Lee, R. Fielding, L. Masinter
RFC2397 The "data" URL scheme
A new URL scheme, "data", is defined. It allows inclusion of small data items as "immediate" data, as if it had been included externally. [STANDARDS-TRACK]
August 1998
Status: PROPOSED STANDARD
Autor: L. Masinter
RFC2398 Some Testing Tools for TCP Implementors
This document lists only tools which can evaluate one or more TCP implementations, or which can privde some specific results which describe or evaluate the TCP being tested. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
August 1998
Status: INFORMATIONAL
Autor: S. Parker, C. Schmechel
RFC2399 Request for Comments Summary
January 1999
Status: INFORMATIONAL
Autor: A. Ramos
RFC2400 Internet Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). This memo is an Internet Standard. [STANDARDS-TRACK]
September 1998
Status: HISTORIC
Autor: J. Postel, J. Reynolds
RFC2401 Security Architecture for the Internet Protocol
This memo specifies the base architecture for IPsec compliant systems. [STANDARDS-TRACK]
November 1998
Status: PROPOSED STANDARD
Autor: S. Kent, R. Atkinson
RFC2402 IP Authentication Header
The IP Authentication Header (AH) is used to provide connectionless integrity and data origin authentication for IP datagrams (hereafter referred to as just "authentication"), and to provide protection against replays. [STANDARDS-TRACK]
November 1998
Status: PROPOSED STANDARD
Autor: S. Kent, R. Atkinson
RFC2403 The Use of HMAC-MD5-96 within ESP and AH
This memo describes the use of the HMAC algorithm in conjunction with the MD5 algorithm as an authentication mechanism within the revised IPSEC Encapsulating Security Payload and the revised IPSEC Authentication Header. [STANDARDS-TRACK]
November 1998
Status: PROPOSED STANDARD
Autor: C. Madson, R. Glenn
RFC2404 The Use of HMAC-SHA-1-96 within ESP and AH
This memo describes the use of the HMAC algorithm in conjunction with the SHA-1 algorithm as an authentication mechanism within the revised IPSEC Encapsulating Security Payload and the revised IPSEC Authentication Header. [STANDARDS-TRACK]
November 1998
Status: PROPOSED STANDARD
Autor: C. Madson, R. Glenn
RFC2405 The ESP DES-CBC Cipher Algorithm With Explicit IV
This document describes the use of the DES Cipher algorithm in Cipher Block Chaining Mode, with an explicit IV, as a confidentiality mechanism within the context of the IPSec Encapsulating Security Payload (ESP). [STANDARDS-TRACK]
November 1998
Status: PROPOSED STANDARD
Autor: C. Madson, N. Doraswamy
RFC2406 IP Encapsulating Security Payload (ESP)
The Encapsulating Security Payload (ESP) header is designed to provide a mix of security services in IPv4 and IPv6. [STANDARDS-TRACK]
November 1998
Status: PROPOSED STANDARD
Autor: S. Kent, R. Atkinson
RFC2407 The Internet IP Security Domain of Interpretation for ISAKMP
This document defines the Internet IP Security DOI (IPSEC DOI), which instantiates ISAKMP for use with IP when IP uses ISAKMP to negotiate security associations. [STANDARDS-TRACK]
November 1998
Status: PROPOSED STANDARD
Autor: D. Piper
RFC2408 Internet Security Association and Key Management Protocol (ISAKMP)
This memo describes a protocol utilizing security concepts necessary for establishing Security Associations (SA) and cryptographic keys in an Internet environment. [STANDARDS-TRACK]
November 1998
Status: PROPOSED STANDARD
Autor: D. Maughan, M. Schertler, M. Schneider, J. Turner
RFC2409 The Internet Key Exchange (IKE)
This memo describes a hybrid protocol. The purpose is to negotiate, and provide authenticated keying material for, security associations in a protected manner. [STANDARDS-TRACK]
November 1998
Status: PROPOSED STANDARD
Autor: D. Harkins, D. Carrel
RFC2410 The NULL Encryption Algorithm and Its Use With IPsec
This memo defines the NULL encryption algorithm and its use with the IPsec Encapsulating Security Payload (ESP). [STANDARDS-TRACK]
November 1998
Status: PROPOSED STANDARD
Autor: R. Glenn, S. Kent
RFC2411 IP Security Document Roadmap
This document is intended to provide guidelines for the development of collateral specifications describing the use of new encryption and authentication algorithms with the ESP protocol, described in and new authentication algorithms used with the AH protocol. This memo provides information for the Internet community.
November 1998
Status: INFORMATIONAL
Autor: R. Thayer, N. Doraswamy, R. Glenn
RFC2412 The OAKLEY Key Determination Protocol
This document describes a protocol, named OAKLEY, by which two authenticated parties can agree on secure and secret keying material. The basic mechanism is the Diffie-Hellman key exchange algorithm. This memo provides information for the Internet community.
November 1998
Status: INFORMATIONAL
Autor: H. Orman
RFC2413 Dublin Core Metadata for Resource Discovery
This is the first of a set of Informational RFCs describing the Dublin Core. Its purpose is to introduce the Dublin Core and to describe the consensus reached on the semantics of each of the 15 elements. This memo provides information for the Internet community.
September 1998
Status: INFORMATIONAL
Autor: S. Weibel, J. Kunze, C. Lagoze, M. Wolf
RFC2414 Increasing TCP's Initial Window
This document specifies an increase in the permitted initial window for TCP from one segment to roughly 4K bytes. This memo defines an Experimental Protocol for the Internet community.
September 1998
Status: EXPERIMENTAL
Autor: M. Allman, S. Floyd, C. Partridge
RFC2415 Simulation Studies of Increased Initial TCP Window Size
This document covers some simulation studies of the effects of increasing the initial window size of TCP. This memo provides information for the Internet community.
September 1998
Status: INFORMATIONAL
Autor: K. Poduri, K. Nichols
RFC2416 When TCP Starts Up With Four Packets Into Only Three Buffers
This memo is to document a simple experiment. The experiment showed that in the case of a TCP receiver behind a 9600 bps modem link at the edge of a fast Internet where there are only 3 buffers before the modem (and the fourth packet of a four-packet start will surely be dropped), no significant degradation in performance is experienced by a TCP sending with a four-packet start when compared with a normal slow start (which starts with just one packet). This memo provides information for the Internet community.
September 1998
Status: INFORMATIONAL
Autor: T. Shepard, C. Partridge
RFC2417 Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks
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. [STANDARDS-TRACK]
September 1998
Status: PROPOSED STANDARD
Autor: C. Chung, M. Greene
RFC2418 IETF Working Group Guidelines and Procedures
This document describes the guidelines and procedures for formation and operation of IETF working groups. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
September 1998
Status: BEST CURRENT PRACTICE
Autor: S. Bradner
RFC2419 The PPP DES Encryption Protocol, Version 2 (DESE-bis)
This document provides specific details for the use of the DES standard for encrypting PPP encapsulated packets. [STANDARDS-TRACK]
September 1998
Status: PROPOSED STANDARD
Autor: K. Sklower, G. Meyer
RFC2420 The PPP Triple-DES Encryption Protocol (3DESE)
This document provides specific details for the use of the Triple-DES standard (3DES) for encrypting PPP encapsulated packets. [STANDARDS-TRACK]
September 1998
Status: PROPOSED STANDARD
Autor: H. Kummert
RFC2421 Voice Profile for Internet Mail - version 2
This document profiles Internet mail for voice messaging. [STANDARDS-TRACK]
September 1998
Status: PROPOSED STANDARD
Autor: G. Vaudreuil, G. Parsons
RFC2422 Toll Quality Voice - 32 kbit/s ADPCM MIME Sub-type Registration
This document describes the registration of the MIME sub-type audio/32KADPCM for toll quality audio. [STANDARDS-TRACK]
September 1998
Status: PROPOSED STANDARD
Autor: G. Vaudreuil, G. Parsons
RFC2423 VPIM Voice Message MIME Sub-type Registration
This document describes the registration of the MIME sub-type multipart/voice-message for use with the Voice Profile for Internet Mail (VPIM). [STANDARDS-TRACK]
September 1998
Status: PROPOSED STANDARD
Autor: G. Vaudreuil, G. Parsons
RFC2424 Content Duration MIME Header Definition
This document describes the MIME header Content-Duration that is intended for use with any timed media content (typically audio/* or video/*). [STANDARDS-TRACK]
September 1998
Status: PROPOSED STANDARD
Autor: G. Vaudreuil, G. Parsons
RFC2425 A MIME Content-Type for Directory Information
This document defines a MIME Content-Type for holding directory information. [STANDARDS-TRACK]
September 1998
Status: PROPOSED STANDARD
Autor: T. Howes, M. Smith, F. Dawson
RFC2426 vCard MIME Directory Profile
This memo defines the profile of the MIME Content-Type for directory information for a white-pages person object, based on a vCard electronic business card. [STANDARDS-TRACK]
September 1998
Status: PROPOSED STANDARD
Autor: F. Dawson, T. Howes
RFC2427 Multiprotocol Interconnect over Frame Relay
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]
September 1998
Status: STANDARD
Autor: C. Brown, A. Malis
RFC2428 FTP Extensions for IPv6 and NATs
This paper specifies extensions to FTP that will allow the protocol to work over IPv4 and IPv6. [STANDARDS-TRACK]
September 1998
Status: PROPOSED STANDARD
Autor: M. Allman, S. Ostermann, C. Metz
RFC2429 RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+)
This document specifies an RTP payload header format applicable to the transmission of video streams generated based on the 1998 version of ITU-T Recommendation H.263. [STANDARDS-TRACK]
October 1998
Status: PROPOSED STANDARD
Autor: C. Bormann, L. Cline, G. Deisher, T. Gardos, C. Maciocco, D. Newell, J. Ott, G. Sullivan, S. Wenger, C. Zhu
RFC2430 A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE)
This document describes the Provider Architecture for Differentiated Services and Traffic Engineering (PASTE) for Internet Service Providers (ISPs). This memo provides information for the Internet community.
October 1998
Status: INFORMATIONAL
Autor: T. Li, Y. Rekhter
RFC2431 RTP Payload Format for BT.656 Video Encoding
This document specifies the RTP payload format for encapsulating ITU Recommendation BT.656-3 video streams in the Real-Time Transport Protocol (RTP). [STANDARDS-TRACK]
October 1998
Status: PROPOSED STANDARD
Autor: D. Tynan
RFC2432 Terminology for IP Multicast Benchmarking
The purpose of this document is to define terminology specific to the benchmarking of multicast IP forwarding devices. This memo provides information for the Internet community.
October 1998
Status: INFORMATIONAL
Autor: K. Dubray
RFC2433 Microsoft PPP CHAP Extensions
The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol and a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This memo provides information for the Internet community.
October 1998
Status: INFORMATIONAL
Autor: G. Zorn, S. Cobb
RFC2434 Guidelines for Writing an IANA Considerations Section in RFCs
This document discusses issues that should be considered in formulating a policy for assigning values to a name space and provides guidelines to document authors on the specific text that must be included in documents that place demands on the IANA. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
October 1998
Status: BEST CURRENT PRACTICE
Autor: T. Narten, H. Alvestrand
RFC2435 RTP Payload Format for JPEG-compressed Video
This memo describes the RTP payload format for JPEG video streams. [STANDARDS-TRACK]
October 1998
Status: PROPOSED STANDARD
Autor: L. Berc, W. Fenner, R. Frederick, S. McCanne, P. Stewart
RFC2436 Collaboration between ISOC/IETF and ITU-T
This document describes the collaboration process between the ITU-T and ISOC/IETF. This memo provides information for the Internet community.
October 1998
Status: INFORMATIONAL
Autor: R. Brett, S. Bradner, G. Parsons
RFC2437 PKCS #1: RSA Cryptography Specifications Version 2.0
This memo is the successor to RFC 2313. This document provides recommendations for the implementation of public-key cryptography based on the RSA algorithm. This memo provides information for the Internet community.
October 1998
Status: INFORMATIONAL
Autor: B. Kaliski, J. Staddon
RFC2438 Advancement of MIB specifications on the IETF Standards Track
This document specifies the process which the IESG will use to determine if a MIB specification document meets these requirements. It also discusses the rationale for this process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
October 1998
Status: BEST CURRENT PRACTICE
Autor: M. O'Dell, H. Alvestrand, B. Wijnen, S. Bradner
RFC2439 BGP Route Flap Damping
A usage of the BGP routing protocol is described which is capable of reducing the routing traffic passed on to routing peers and therefore the load on these peers without adversely affecting route convergence time for relatively stable routes. [STANDARDS-TRACK]
November 1998
Status: PROPOSED STANDARD
Autor: C. Villamizar, R. Chandra, R. Govindan
RFC2440 OpenPGP Message Format
This document is maintained in order to publish all necessary information needed to develop interoperable applications based on the OpenPGP format. [STANDARDS-TRACK]
November 1998
Status: PROPOSED STANDARD
Autor: J. Callas, L. Donnerhacke, H. Finney, R. Thayer
RFC2441 Working with Jon, Tribute delivered at UCLA, October 30, 1998
This memo provides information for the Internet community.
November 1998
Status: INFORMATIONAL
Autor: D. Cohen
RFC2442 The Batch SMTP Media Type
This document defines a MIME content type suitable for tunneling an ESMTP transaction through any MIME-capable transport. This memo provides information for the Internet community
November 1998
Status: INFORMATIONAL
Autor: N. Freed, D. Newman, J. Belissent, M. Hoy
RFC2443 A Distributed MARS Service Using SCSP
This document describes a method for distributing a MARS service within a LIS. This method uses the Server Cache Synchronization Protocol (SCSP) to synchronize the MARS Server databases within a LIS. When SCSP is used to synchronize the caches of MARS Servers in a LIS, the LIS defines the boundary of an SCSP Server Group (SG). [STANDARDS-TRACK]
November 1998
Status: EXPERIMENTAL
Autor: J. Luciani, A. Gallo
RFC2444