Internet Documents

RFCs

RFCs All DocumentsSTDs Internet Standards DocumentsBCPs Best Current Practice DocumentsFYIs Informational Documents
 

 
RFC 3 Documentation conventions
 
Authors:S.D. Crocker.
Date:April 1969
Formats:txt pdf
Obsoleted by:RFC 0010
Status:UNKNOWN
DOI:10.17487/RFC 0003
 
 
RFC 10 Documentation conventions
 
Authors:S.D. Crocker.
Date:July 1969
Formats:txt pdf
Obsoletes:RFC 0003
Obsoleted by:RFC 0016
Updated by:RFC 0024, RFC 0027, RFC 0030
Status:UNKNOWN
DOI:10.17487/RFC 0010
 
 
RFC 11 Implementation of the Host - Host Software Procedures in GORDO
 
Authors:G. Deloche.
Date:August 1969
Formats:txt pdf
Obsoleted by:RFC 0033
Status:UNKNOWN
DOI:10.17487/RFC 0011
 
 
RFC 16 M.I.T
 
Authors:S. Crocker.
Date:August 1969
Formats:txt pdf
Obsoletes:RFC 0010
Obsoleted by:RFC 0024
Updated by:RFC 0024, RFC 0027, RFC 0030
Status:UNKNOWN
DOI:10.17487/RFC 0016
 
 
RFC 61 Note on Interprocess Communication in a Resource Sharing Computer Network
 
Authors:D.C. Walden.
Date:July 1970
Formats:txt pdf
Obsoleted by:RFC 0062
Status:UNKNOWN
DOI:10.17487/RFC 0061
 
 
RFC 66 NIC - third level ideas and other noise
 
Authors:S.D. Crocker.
Date:August 1970
Formats:txt pdf
Obsoleted by:RFC 0123
Updated by:RFC 0080, RFC 0093
Status:UNKNOWN
DOI:10.17487/RFC 0066
 
 
RFC 80 Protocols and Data Formats
 
Authors:E. Harslem, J.F. Heafner.
Date:December 1970
Formats:txt pdf
Obsoleted by:RFC 0123
Updates:RFC 0066
Updated by:RFC 0093
Status:UNKNOWN
DOI:10.17487/RFC 0080
 
 
RFC 88 NETRJS: A third level protocol for Remote Job Entry
 
Authors:R.T. Braden, S.M. Wolfe.
Date:January 1971
Formats:txt pdf
Obsoleted by:RFC 0189
Status:UNKNOWN
DOI:10.17487/RFC 0088
 
 
RFC 95 Distribution of NWG/RFC's through the NIC
 
Authors:S. Crocker.
Date:February 1971
Formats:txt pdf
Obsoleted by:RFC 0155
Status:UNKNOWN
DOI:10.17487/RFC 0095
 
 
RFC 123 Proffered Official ICP
 
Authors:S.D. Crocker.
Date:April 1971
Formats:txt pdf
Obsoletes:RFC 0066, RFC 0080
Obsoleted by:RFC 0165
Updates:RFC 0098, RFC 0101
Updated by:RFC 0127, RFC 0143, RFC 0148
Status:UNKNOWN
DOI:10.17487/RFC 0123
 
 
RFC 127 Comments on RFC 123
 
Authors:J. Postel.
Date:April 1971
Formats:txt pdf
Obsoleted by:RFC 0145
Updates:RFC 0123
Updated by:RFC 0151
Status:UNKNOWN
DOI:10.17487/RFC 0127
 
 
RFC 132 Typographical Error in RFC 107
 
Authors:J.E. White.
Date:April 1971
Formats:txt pdf
Obsoleted by:RFC 0154
Updates:RFC 0107
Status:UNKNOWN
DOI:10.17487/RFC 0132
 
 
RFC 143 Regarding proffered official ICP
 
Authors:W. Naylor, J. Wong, C. Kline, J. Postel.
Date:May 1971
Formats:txt pdf
Obsoleted by:RFC 0165
Updates:RFC 0123, RFC 0145
Status:UNKNOWN
DOI:10.17487/RFC 0143
 
 
RFC 145 Initial Connection Protocol Control Commands
 
Authors:J. Postel.
Date:May 1971
Formats:txt ps pdf
Obsoletes:RFC 0127
Obsoleted by:RFC 0165
Updated by:RFC 0143
Status:UNKNOWN
DOI:10.17487/RFC 0145
 
 
RFC 155 ARPA Network mailing lists
 
Authors:J.B. North.
Date:May 1971
Formats:txt pdf
Obsoletes:RFC 0095
Obsoleted by:RFC 0168
Status:UNKNOWN
DOI:10.17487/RFC 0155
 
 
RFC 158 Telnet Protocol: A Proposed Document
 
Authors:T.C. O'Sullivan.
Date:May 1971
Formats:txt pdf
Obsoleted by:RFC 0495
Updates:RFC 0139
Updated by:RFC 0318
Also:RFC 0393
Status:UNKNOWN
DOI:10.17487/RFC 0158
 
 
RFC 160 RFC brief list
 
Authors:Network Information Center. Stanford Research Institute.
Date:May 1971
Formats:txt pdf
Obsoleted by:RFC 0200, RFC 0999
Updates:NIC_6716
Status:UNKNOWN
DOI:10.17487/RFC 0160
 
 
RFC 168 ARPA Network mailing lists
 
Authors:J.B. North.
Date:May 1971
Formats:txt pdf
Obsoletes:RFC 0155
Obsoleted by:RFC 0211
Status:UNKNOWN
DOI:10.17487/RFC 0168
 
 
RFC 170 RFC List by Number
 
Authors:Network Information Center. Stanford Research Institute.
Date:June 1971
Formats:txt pdf
Obsoleted by:RFC 0200
Status:UNKNOWN
DOI:10.17487/RFC 0170
 
 
RFC 171 The Data Transfer Protocol
 
Authors:A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenize, J. Melvin, B. Sundberg, D. Watson, J. White.
Date:June 1971
Formats:txt pdf
Obsoleted by:RFC 0264
Updates:RFC 0114
Updated by:RFC 0238
Status:UNKNOWN
DOI:10.17487/RFC 0171
 
 
RFC 172 The File Transfer Protocol
 
Authors:A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenzie, J. Melvin, B. Sundberg, D. Watson, J. White.
Date:June 1971
Formats:txt pdf
Obsoleted by:RFC 0265
Updates:RFC 0114
Updated by:RFC 0238
Status:UNKNOWN
DOI:10.17487/RFC 0172
 
 
RFC 189 Interim NETRJS specifications
 
Authors:R.T. Braden.
Date:July 1971
Formats:txt pdf
Obsoletes:RFC 0088
Obsoleted by:RFC 0599
Updated by:RFC 0283
Status:UNKNOWN
DOI:10.17487/RFC 0189
 
 
RFC 193 NETWORK CHECKOUT
 
Authors:E. Harslem, J.F. Heafner.
Date:July 1971
Formats:txt pdf
Obsoleted by:RFC 0198
Updated by:RFC 0198
Status:UNKNOWN
DOI:10.17487/RFC 0193
 
 
RFC 196 Mail Box Protocol
 
Authors:R.W. Watson.
Date:July 1971
Formats:txt pdf
Obsoleted by:RFC 0221
Status:UNKNOWN
DOI:10.17487/RFC 0196
 
 
RFC 198 Site Certification - Lincoln Labs 360/67
 
Authors:J.F. Heafner.
Date:July 1971
Formats:txt pdf
Obsoletes:RFC 0193
Obsoleted by:RFC 0214
Updates:RFC 0193
Status:UNKNOWN
DOI:10.17487/RFC 0198
 
 
RFC 200 RFC list by number
 
Authors:J.B. North.
Date:August 1971
Formats:txt pdf
Obsoletes:RFC 0170, RFC 0160
Obsoleted by:NIC_7724
Status:UNKNOWN
DOI:10.17487/RFC 0200
 
 
RFC 207 September Network Working Group meeting
 
Authors:A. Vezza.
Date:August 1971
Formats:txt pdf
Obsoleted by:RFC 0212
Status:UNKNOWN
DOI:10.17487/RFC 0207
 
 
RFC 211 ARPA Network Mailing Lists
 
Authors:J.B. North.
Date:August 1971
Formats:txt pdf
Obsoletes:RFC 0168
Obsoleted by:RFC 0300
Status:UNKNOWN
DOI:10.17487/RFC 0211
 
 
RFC 221 Mail Box Protocol: Version 2
 
Authors:R.W. Watson.
Date:August 1971
Formats:txt pdf
Obsoletes:RFC 0196
Obsoleted by:RFC 0278
Status:UNKNOWN
DOI:10.17487/RFC 0221
 
 
RFC 226 Standardization of host mnemonics
 
Authors:P.M. Karp.
Date:September 1971
Formats:txt pdf
Obsoleted by:RFC 0247
Status:UNKNOWN
DOI:10.17487/RFC 0226
 
 
RFC 229 Standard host names
 
Authors:J. Postel.
Date:September 1971
Formats:txt pdf
Obsoleted by:RFC 0236
Status:UNKNOWN
DOI:10.17487/RFC 0229
 
 
RFC 235 Site status
 
Authors:E. Westheimer.
Date:September 1971
Formats:txt pdf
Obsoleted by:RFC 0240
Status:UNKNOWN
DOI:10.17487/RFC 0235
 
 
RFC 237 NIC view of standard host names
 
Authors:R.W. Watson.
Date:October 1971
Formats:txt pdf
Obsoleted by:RFC 0273
Status:UNKNOWN
DOI:10.17487/RFC 0237
 
 
RFC 240 Site Status
 
Authors:A.M. McKenzie.
Date:September 1971
Formats:txt pdf
Obsoletes:RFC 0235
Obsoleted by:RFC 0252
Status:UNKNOWN
DOI:10.17487/RFC 0240
 
 
RFC 243 Network and data sharing bibliography
 
Authors:A.P. Mullery.
Date:October 1971
Formats:txt pdf
Obsoleted by:RFC 0290
Status:UNKNOWN
DOI:10.17487/RFC 0243
 
 
RFC 252 Network host status
 
Authors:E. Westheimer.
Date:October 1971
Formats:txt pdf
Obsoletes:RFC 0240
Obsoleted by:RFC 0255
Status:UNKNOWN
DOI:10.17487/RFC 0252
 
 
RFC 255 Status of network hosts
 
Authors:E. Westheimer.
Date:October 1971
Formats:txt pdf
Obsoletes:RFC 0252
Obsoleted by:RFC 0266
Status:UNKNOWN
DOI:10.17487/RFC 0255
 
 
RFC 264 The Data Transfer Protocol
 
Authors:A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenize, B. Sundberg, D. Watson, J. White.
Date:January 1972
Formats:txt pdf
Obsoletes:RFC 0171
Obsoleted by:RFC 0354
Updated by:RFC 0310
Also:RFC 0265
Status:UNKNOWN
DOI:10.17487/RFC 0264
 
 
RFC 265 The File Transfer Protocol
 
Authors:A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenzie, J. Melvin, B. Sundberg, D. Watson, J. White.
Date:November 1971
Formats:txt pdf
Obsoletes:RFC 0172
Obsoleted by:RFC 0354
Updated by:RFC 0281, RFC 0294, RFC 0310
Also:RFC 0264
Status:UNKNOWN
DOI:10.17487/RFC 0265
 
 
RFC 266 Network host status
 
Authors:E. Westheimer.
Date:November 1971
Formats:txt pdf
Obsoletes:RFC 0255
Obsoleted by:RFC 0267
Status:UNKNOWN
DOI:10.17487/RFC 0266
 
 
RFC 267 Network Host Status
 
Authors:E. Westheimer.
Date:November 1971
Formats:txt pdf
Obsoletes:RFC 0266
Obsoleted by:RFC 0287
Status:UNKNOWN
DOI:10.17487/RFC 0267
 
 
RFC 287 Status of Network Hosts
 
Authors:E. Westheimer.
Date:December 1971
Formats:txt pdf
Obsoletes:RFC 0267
Obsoleted by:RFC 0288
Status:UNKNOWN
DOI:10.17487/RFC 0287
 
 
RFC 288 Network host status
 
Authors:E. Westheimer.
Date:January 1972
Formats:txt pdf
Obsoletes:RFC 0287
Obsoleted by:RFC 0293
Updated by:RFC 0293
Status:UNKNOWN
DOI:10.17487/RFC 0288
 
 
RFC 289 What we hope is an official list of host names
 
Authors:R.W. Watson.
Date:December 1971
Formats:txt pdf
Obsoleted by:RFC 0384
Status:UNKNOWN
DOI:10.17487/RFC 0289
 
 
RFC 292 Graphics Protocol: Level 0 only
 
Authors:J.C. Michener, I.W. Cotton, K.C. Kelley, D.E. Liddle, E. Meyer.
Date:January 1972
Formats:txt pdf
Obsoleted by:RFC 0493
Status:UNKNOWN
DOI:10.17487/RFC 0292
 
 
RFC 293 Network Host Status
 
Authors:E. Westheimer.
Date:January 1972
Formats:txt pdf
Obsoletes:RFC 0288
Obsoleted by:RFC 0298
Updates:RFC 0288
Status:UNKNOWN
DOI:10.17487/RFC 0293
 
 
RFC 298 Network host status
 
Authors:E. Westheimer.
Date:February 1972
Formats:txt pdf
Obsoletes:RFC 0293
Obsoleted by:RFC 0306
Status:UNKNOWN
DOI:10.17487/RFC 0298
 
 
RFC 300 ARPA Network mailing lists
 
Authors:J.B. North.
Date:January 1972
Formats:txt pdf
Obsoletes:RFC 0211
Obsoleted by:RFC 0303
Status:UNKNOWN
DOI:10.17487/RFC 0300
 
 
RFC 303 ARPA Network mailing lists
 
Authors:Network Information Center. Stanford Research Institute.
Date:March 1972
Formats:txt pdf
Obsoletes:RFC 0300
Obsoleted by:RFC 0329
Status:UNKNOWN
DOI:10.17487/RFC 0303
 
 
RFC 306 Network host status
 
Authors:E. Westheimer.
Date:February 1972
Formats:txt pdf
Obsoletes:RFC 0298
Obsoleted by:RFC 0315
Status:UNKNOWN
DOI:10.17487/RFC 0306
 
 
RFC 315 Network Host Status
 
Authors:E. Westheimer.
Date:March 1972
Formats:txt pdf
Obsoletes:RFC 0306
Obsoleted by:RFC 0319
Status:UNKNOWN
DOI:10.17487/RFC 0315
 
 
RFC 317 Official Host-Host Protocol Modification: Assigned Link Numbers
 
Authors:J. Postel.
Date:March 1972
Formats:txt pdf
Obsoleted by:RFC 0604
Status:UNKNOWN
DOI:10.17487/RFC 0317
 
 
RFC 326 Network Host Status
 
Authors:E. Westheimer.
Date:April 1972
Formats:txt pdf
Obsoleted by:RFC 0330
Updates:RFC 0319
Status:UNKNOWN
DOI:10.17487/RFC 0326
 
 
RFC 329 ARPA Network Mailing Lists
 
Authors:Network Information Center. Stanford Research Institute.
Date:May 1972
Formats:txt pdf
Obsoletes:RFC 0303
Obsoleted by:RFC 0363
Status:UNKNOWN
DOI:10.17487/RFC 0329
 
 
RFC 331 IMP System Change Notification
 
Authors:J.M. McQuillan.
Date:April 1972
Formats:txt pdf
Obsoleted by:RFC 0343
Status:UNKNOWN
DOI:10.17487/RFC 0331
 
 
RFC 332 Network Host Status
 
Authors:E. Westheimer.
Date:April 1972
Formats:txt pdf
Obsoleted by:RFC 0342
Updates:RFC 0330
Status:UNKNOWN
DOI:10.17487/RFC 0332
 
 
RFC 342 Network Host Status
 
Authors:E. Westheimer.
Date:May 1972
Formats:txt pdf
Obsoletes:RFC 0332
Obsoleted by:RFC 0344
Status:UNKNOWN
DOI:10.17487/RFC 0342
 
 
RFC 343 IMP System change notification
 
Authors:A.M. McKenzie.
Date:May 1972
Formats:txt pdf
Obsoletes:RFC 0331
Obsoleted by:RFC 0359
Status:UNKNOWN
DOI:10.17487/RFC 0343
 
 
RFC 344 Network Host Status
 
Authors:E. Westheimer.
Date:May 1972
Formats:txt pdf
Obsoletes:RFC 0342
Obsoleted by:RFC 0353
Status:UNKNOWN
DOI:10.17487/RFC 0344
 
 
RFC 349 Proposed Standard Socket Numbers
 
Authors:J. Postel.
Date:May 1972
Formats:txt pdf
Obsoleted by:RFC 0433
Also:RFC 0204, RFC 0322
Status:UNKNOWN
DOI:10.17487/RFC 0349
 
 
RFC 353 Network host status
 
Authors:E. Westheimer.
Date:June 1972
Formats:txt pdf
Obsoletes:RFC 0344
Obsoleted by:RFC 0362
Status:UNKNOWN
DOI:10.17487/RFC 0353
 
 
RFC 354 File Transfer Protocol
 
Authors:A.K. Bhushan.
Date:July 1972
Formats:txt pdf
Obsoletes:RFC 0264, RFC 0265
Obsoleted by:RFC 0542
Updated by:RFC 0385, RFC 0454, RFC 0683
Status:UNKNOWN
DOI:10.17487/RFC 0354
 
 
RFC 360 Proposed Remote Job Entry Protocol
 
Authors:C. Holland.
Date:June 1972
Formats:txt pdf
Obsoleted by:RFC 0407
Status:UNKNOWN
DOI:10.17487/RFC 0360
 
 
RFC 362 Network Host Status
 
Authors:E. Westheimer.
Date:June 1972
Formats:txt pdf
Obsoletes:RFC 0353
Obsoleted by:RFC 0366
Status:UNKNOWN
DOI:10.17487/RFC 0362
 
 
RFC 363 ARPA Network mailing lists
 
Authors:Network Information Center. Stanford Research Institute.
Date:August 1972
Formats:txt pdf
Obsoletes:RFC 0329
Obsoleted by:RFC 0402
Status:UNKNOWN
DOI:10.17487/RFC 0363
 
 
RFC 366 Network Host Status
 
Authors:E. Westheimer.
Date:July 1972
Formats:txt pdf
Obsoletes:RFC 0362
Obsoleted by:RFC 0367
Status:UNKNOWN
DOI:10.17487/RFC 0366
 
 
RFC 367 Network host status
 
Authors:E. Westheimer.
Date:July 1972
Formats:txt pdf
Obsoletes:RFC 0366
Obsoleted by:RFC 0370
Status:UNKNOWN
DOI:10.17487/RFC 0367
 
 
RFC 378 Traffic statistics (July 1972)
 
Authors:A.M. McKenzie.
Date:August 1972
Formats:txt pdf
Obsoleted by:RFC 0391
Status:UNKNOWN
DOI:10.17487/RFC 0378
 
 
RFC 389 UCLA Campus Computing Network Liaison Staff for ARPA Network
 
Authors:B. Noble.
Date:August 1972
Formats:txt pdf
Obsoleted by:RFC 0423
Status:UNKNOWN
DOI:10.17487/RFC 0389
 
 
RFC 399 SMFS Login and Logout
 
Authors:M. Krilanovich.
Date:September 1972
Formats:txt pdf
Obsoleted by:RFC 0431
Updates:RFC 0122
Status:UNKNOWN
DOI:10.17487/RFC 0399
 
 
RFC 433 Socket number list
 
Authors:J. Postel.
Date:December 1972
Formats:txt pdf
Obsoletes:RFC 0349
Obsoleted by:RFC 0503
Status:UNKNOWN
DOI:10.17487/RFC 0433
 
 
RFC 434 IMP/TIP memory retrofit schedule
 
Authors:A.M. McKenzie.
Date:January 1973
Formats:txt pdf
Obsoleted by:RFC 0447
Status:UNKNOWN
DOI:10.17487/RFC 0434
 
 
RFC 447 IMP/TIP memory retrofit schedule
 
Authors:A.M. McKenzie.
Date:January 1973
Formats:txt pdf
Obsoletes:RFC 0434
Obsoleted by:RFC 0476
Status:UNKNOWN
DOI:10.17487/RFC 0447
 
 
RFC 503 Socket number list
 
Authors:N. Neigus, J. Postel.
Date:April 1973
Formats:txt pdf
Obsoletes:RFC 0433
Obsoleted by:RFC 0739
Status:UNKNOWN
DOI:10.17487/RFC 0503
 
 
RFC 542 File Transfer Protocol
 
Authors:N. Neigus.
Date:August 1973
Formats:txt pdf
Obsoletes:RFC 0354
Obsoleted by:RFC 0765
Updated by:RFC 0614, RFC 0640
Also:RFC 0454, RFC 0495
Status:UNKNOWN
DOI:10.17487/RFC 0542
 
 
RFC 599 Update on NETRJS
 
Authors:R.T. Braden.
Date:December 1973
Formats:txt pdf
Obsoletes:RFC 0189
Obsoleted by:RFC 0740
Status:UNKNOWN
DOI:10.17487/RFC 0599
 
 
RFC 604 Assigned link numbers
 
Authors:J. Postel.
Date:December 1973
Formats:txt pdf
Obsoletes:RFC 0317
Obsoleted by:RFC 0739
Status:UNKNOWN
DOI:10.17487/RFC 0604
Modifies official host-host protocol. Replaces RFC 377.
 
RFC 607 Comments on the File Transfer Protocol
 
Authors:M. Krilanovich, G. Gregg.
Date:January 1974
Formats:txt pdf
Obsoleted by:RFC 0624
Updated by:RFC 0614
Status:UNKNOWN
DOI:10.17487/RFC 0607
An old version; see RFC 624; see also RFCs 614, 542 and 640.
 
RFC 608 Host names on-line
 
Authors:M.D. Kudlick.
Date:January 1974
Formats:txt pdf
Obsoleted by:RFC 0810
Status:UNKNOWN
DOI:10.17487/RFC 0608
Response to RFC 606; see also RFCs 627, 625 and 623.
 
RFC 615 Proposed Network Standard Data Pathname syntax
 
Authors:D. Crocker.
Date:March 1974
Formats:txt pdf
Obsoleted by:RFC 0645
Status:UNKNOWN
DOI:10.17487/RFC 0615
 
 
RFC 633 IMP/TIP preventive maintenance schedule
 
Authors:A.M. McKenzie.
Date:March 1974
Formats:txt pdf
Obsoleted by:RFC 0638
Status:UNKNOWN
DOI:10.17487/RFC 0633
An old version; see RFC 638.
 
RFC 651 Revised Telnet status option
 
Authors:D. Crocker.
Date:October 1974
Formats:txt pdf
Obsoleted by:RFC 0859
Status:UNKNOWN
DOI:10.17487/RFC 0651
 
 
RFC 675 Specification of Internet Transmission Control Program
 
Authors:V. Cerf, Y. Dalal, C. Sunshine.
Date:December 1974
Formats:txt pdf
Obsoleted by:RFC 7805
Status:HISTORIC
DOI:10.17487/RFC 0675
The first detailed specification of TCP; see RFC 793.
 
RFC 687 IMP/Host and Host/IMP Protocol changes
 
Authors:D.C. Walden.
Date:June 1975
Formats:txt pdf
Obsoleted by:RFC 0704
Updated by:RFC 0690
Status:UNKNOWN
DOI:10.17487/RFC 0687
Addressing hosts on more than 63 IMPs, and other backwards compatible expansions; see also RFCs 690 and 692.
 
RFC 698 Telnet extended ASCII option
 
Authors:T. Mock.
Date:July 1975
Formats:txt pdf
Obsoleted by:RFC 5198
Status:PROPOSED STANDARD
DOI:10.17487/RFC 0698
Describes an option to allow transmission of a special kind of extended ASCII used at the Stanford AI and MIT AI Labs.
 
RFC 721 Out-of-Band Control Signals in a Host-to-Host Protocol
 
Authors:L.L. Garlick.
Date:September 1976
Formats:txt pdf
Obsoleted by:RFC 7805
Status:HISTORIC
DOI:10.17487/RFC 0721
 
 
RFC 724 Proposed official standard for the format of ARPA Network messages
 
Authors:D. Crocker, K.T. Pogran, J. Vittal, D.A. Henderson.
Date:May 1977
Formats:txt pdf
Obsoleted by:RFC 0733
Status:UNKNOWN
DOI:10.17487/RFC 0724
 
 
RFC 729 Telnet byte macro option
 
Authors:D. Crocker.
Date:May 1977
Formats:txt pdf
Obsoleted by:RFC 0735
Status:UNKNOWN
DOI:10.17487/RFC 0729
 
 
RFC 731 Telnet Data Entry Terminal option
 
Authors:J.D. Day.
Date:June 1977
Formats:txt pdf
Obsoleted by:RFC 0732
Status:UNKNOWN
DOI:10.17487/RFC 0731
 
 
RFC 733 Standard for the format of ARPA network text messages
 
Authors:D. Crocker, J. Vittal, K.T. Pogran, D.A. Henderson.
Date:November 1977
Formats:txt pdf
Obsoletes:RFC 0724
Obsoleted by:RFC 0822
Status:UNKNOWN
DOI:10.17487/RFC 0733
 
 
RFC 739 Assigned numbers
 
Authors:J. Postel.
Date:November 1977
Formats:txt pdf
Obsoletes:RFC 0604, RFC 0503
Obsoleted by:RFC 0750
Status:HISTORIC
DOI:10.17487/RFC 0739
 
 
RFC 742 NAME/FINGER Protocol
 
Authors:K. Harrenstien.
Date:December 1977
Formats:txt pdf
Obsoleted by:RFC 1288, RFC 1196, RFC 1194
Status:UNKNOWN
DOI:10.17487/RFC 0742
 
 
RFC 750 Assigned numbers
 
Authors:J. Postel.
Date:September 1978
Formats:txt pdf
Obsoletes:RFC 0739
Obsoleted by:RFC 0755
Status:HISTORIC
DOI:10.17487/RFC 0750
 
 
RFC 755 Assigned numbers
 
Authors:J. Postel.
Date:May 1979
Formats:txt pdf
Obsoletes:RFC 0750
Obsoleted by:RFC 0758
Status:HISTORIC
DOI:10.17487/RFC 0755
 
 
RFC 758 Assigned numbers
 
Authors:J. Postel.
Date:August 1979
Formats:txt pdf
Obsoletes:RFC 0755
Obsoleted by:RFC 0762
Status:HISTORIC
DOI:10.17487/RFC 0758
 
 
RFC 760 DoD standard Internet Protocol
 
Authors:J. Postel.
Date:January 1980
Formats:txt pdf
Obsoletes:IEN123
Obsoleted by:RFC 0791
Updated by:RFC 0777
Status:UNKNOWN
DOI:10.17487/RFC 0760
 
 
RFC 761 DoD standard Transmission Control Protocol
 
Authors:J. Postel.
Date:January 1980
Formats:txt pdf
Obsoleted by:RFC 0793, RFC 7805
Status:HISTORIC
DOI:10.17487/RFC 0761
 
 
RFC 762 Assigned numbers
 
Authors:J. Postel.
Date:January 1980
Formats:txt pdf
Obsoletes:RFC 0758
Obsoleted by:RFC 0770
Status:HISTORIC
DOI:10.17487/RFC 0762
 
 
RFC 764 Telnet Protocol specification
 
Authors:J. Postel.
Date:June 1980
Formats:txt pdf
Obsoleted by:RFC 0854
Status:UNKNOWN
DOI:10.17487/RFC 0764
 
 
RFC 765 File Transfer Protocol specification
 
Authors:J. Postel.
Date:June 1980
Formats:txt pdf
Obsoletes:RFC 0542
Obsoleted by:RFC 0959
Status:UNKNOWN
DOI:10.17487/RFC 0765
 
 
RFC 766 Internet Protocol Handbook: Table of contents
 
Authors:J. Postel.
Date:July 1980
Formats:txt pdf
Obsoleted by:RFC 0774
Status:UNKNOWN
DOI:10.17487/RFC 0766
 
 
RFC 770 Assigned numbers
 
Authors:J. Postel.
Date:September 1980
Formats:txt pdf
Obsoletes:RFC 0762
Obsoleted by:RFC 0776
Status:HISTORIC
DOI:10.17487/RFC 0770
 
 
RFC 772 Mail Transfer Protocol
 
Authors:S. Sluizer, J. Postel.
Date:September 1980
Formats:txt pdf
Obsoleted by:RFC 0780
Status:UNKNOWN
DOI:10.17487/RFC 0772
 
 
RFC 776 Assigned numbers
 
Authors:J. Postel.
Date:January 1981
Formats:txt pdf
Obsoletes:RFC 0770
Obsoleted by:RFC 0790
Status:HISTORIC
DOI:10.17487/RFC 0776
 
 
RFC 777 Internet Control Message Protocol
 
Authors:J. Postel.
Date:April 1981
Formats:txt pdf
Obsoleted by:RFC 0792
Updates:RFC 0760
Status:UNKNOWN
DOI:10.17487/RFC 0777
 
 
RFC 780 Mail Transfer Protocol
 
Authors:S. Sluizer, J. Postel.
Date:May 1981
Formats:txt pdf
Obsoletes:RFC 0772
Obsoleted by:RFC 0788
Status:UNKNOWN
DOI:10.17487/RFC 0780
 
 
RFC 783 TFTP Protocol (revision 2)
 
Authors:K.R. Sollins.
Date:June 1981
Formats:txt pdf
Obsoletes:IEN133
Obsoleted by:RFC 1350
Status:UNKNOWN
DOI:10.17487/RFC 0783
 
 
RFC 788 Simple Mail Transfer Protocol
 
Authors:J. Postel.
Date:November 1981
Formats:txt pdf
Obsoletes:RFC 0780
Obsoleted by:RFC 0821
Status:UNKNOWN
DOI:10.17487/RFC 0788
 
 
RFC 790 Assigned numbers
 
Authors:J. Postel.
Date:September 1981
Formats:txt pdf
Obsoletes:RFC 0776
Obsoleted by:RFC 0820
Status:HISTORIC
DOI:10.17487/RFC 0790
 
 
RFC 802 ARPANET 1822L Host Access Protocol
 
Authors:A.G. Malis.
Date:November 1981
Formats:txt pdf
Obsoleted by:RFC 0851
Status:UNKNOWN
DOI:10.17487/RFC 0802
This document proposed two major changes to the current ARPANET host access protocol. The first change will allow hosts to use logical addressing (i.e., host addresses that are independent of their physical location on the ARPANET) to communicate with each other, and the second will allow a host to shorten the amount of time that it may be blocked by its IMP after it presents a message to the network (currently, the IMP can block further input from a host for up to 15 seconds). See RFCs 852 and 851.
 
RFC 806 Proposed Federal Information Processing Standard: Specification for message format for computer based message systems
 
Authors:National Bureau of Standards.
Date:September 1981
Formats:txt pdf
Obsoleted by:RFC 0841
Status:UNKNOWN
DOI:10.17487/RFC 0806
This RFC deals with Computer Based Message systems which provides a basis for interaction between different CBMS by defining the format of messages passed between them. This RFC is replaced by RFC 841.
 
RFC 810 DoD Internet host table specification
 
Authors:E.J. Feinler, K. Harrenstien, Z. Su, V. White.
Date:March 1982
Formats:txt pdf
Obsoletes:RFC 0608
Obsoleted by:RFC 0952
Status:UNKNOWN
DOI:10.17487/RFC 0810
This RFC specifies a new host table format applicable to both ARPANET and Internet needs. In addition to host name to host address translation and selected protocol information, we have also included network and gateway name to address correspondence, and host operating system information. This RFC obsoletes the host table described in RFC 608.
 
RFC 811 Hostnames Server
 
Authors:K. Harrenstien, V. White, E.J. Feinler.
Date:March 1982
Formats:txt pdf
Obsoleted by:RFC 0953
Status:UNKNOWN
DOI:10.17487/RFC 0811
This RFC gives a description of what the Hostnames Server is and how to access it. The function of this particular server is to deliver machine-readable name/address information describing networks, gateways, hosts, and eventually domains, within the internet environment.
 
RFC 812 NICNAME/WHOIS
 
Authors:K. Harrenstien, V. White.
Date:March 1982
Formats:txt pdf
Obsoleted by:RFC 0954, RFC 3912
Status:UNKNOWN
DOI:10.17487/RFC 0812
This RFC gives a description of what the NICNAME/WHOIS Server is and how to access it. This server together with the corresponding Identification Data Base provides online directory look-up equivalent to the ARPANET Directory.
 
RFC 813 Window and Acknowledgement Strategy in TCP
 
Authors:D.D. Clark.
Date:July 1982
Formats:txt pdf
Obsoleted by:RFC 7805
Status:HISTORIC
DOI:10.17487/RFC 0813
This RFC describes implementation strategies to deal with two mechanisms in TCP, the window and the acknowledgement. It also presents a particular set of algorithms which have received testing in the field, and which appear to work properly with each other. With more experience, these algorithms may become part of the formal specification, until such time their use is recommended.
 
RFC 816 Fault isolation and recovery
 
Authors:D.D. Clark.
Date:July 1982
Formats:txt pdf
Obsoleted by:RFC 7805
Status:HISTORIC
DOI:10.17487/RFC 0816
This RFC describes the portion of fault isolation and recovery which is the responsibility of the host.
 
RFC 820 Assigned numbers
 
Authors:J. Postel.
Date:August 1982
Formats:txt pdf
Obsoletes:RFC 0790
Obsoleted by:RFC 0870
Status:HISTORIC
DOI:10.17487/RFC 0820
This RFC is an old version, see RFC 870.
 
RFC 821 Simple Mail Transfer Protocol
 
Authors:J. Postel.
Date:August 1982
Formats:txt pdf
Obsoletes:RFC 0788
Obsoleted by:RFC 2821
Also:STD 0010
Status:INTERNET STANDARD
DOI:10.17487/RFC 0821
The objective of Simple Mail Transfer Protocol (SMTP) is to transfer mail reliably and efficiently. SMTP is independent of the particular transmission subsystem and requires only a reliable ordered data stream channel. Obsoletes RFC 788, 780, and 772.
 
RFC 822 STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
 
Authors:D. Crocker.
Date:August 1982
Formats:txt pdf
Obsoletes:RFC 0733
Obsoleted by:RFC 2822
Updated by:RFC 1123, RFC 2156, RFC 1327, RFC 1138, RFC 1148
Also:STD 0011
Status:INTERNET STANDARD
DOI:10.17487/RFC 0822
This document revises the specifications in RFC 733, in order to serve the needs of the larger and more complex ARPA Internet. Some of RFC 733's features failed to gain adequate acceptance. In order to simplify the standard and the software that follows it, these features have been removed. A different addressing scheme is used, to handle the case of internetwork mail; and the concept of re-transmission has been introduced. Obsoletes RFC 733, NIC 41952.
 
RFC 825 Request for comments on Requests For Comments
 
Authors:J. Postel.
Date:November 1982
Formats:txt pdf
Obsoleted by:RFC 1111, RFC 1543, RFC 2223
Status:UNKNOWN
DOI:10.17487/RFC 0825
This RFC is intended to clarify the status of RFCs and to provide some guidance for the authors of RFCs in the future. It is in a sense a specification for RFCs.
 
RFC 832 Who talks TCP?
 
Authors:D. Smallberg.
Date:December 1982
Formats:txt pdf
Obsoleted by:RFC 0833
Status:UNKNOWN
DOI:10.17487/RFC 0832
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 7-Dec-82.
 
RFC 833 Who talks TCP?
 
Authors:D. Smallberg.
Date:December 1982
Formats:txt pdf
Obsoletes:RFC 0832
Obsoleted by:RFC 0834
Status:UNKNOWN
DOI:10.17487/RFC 0833
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 14-Dec-82.
 
RFC 834 Who talks TCP?
 
Authors:D. Smallberg.
Date:December 1982
Formats:txt pdf
Obsoletes:RFC 0833
Obsoleted by:RFC 0835
Status:UNKNOWN
DOI:10.17487/RFC 0834
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 22-Dec-82.
 
RFC 835 Who talks TCP?
 
Authors:D. Smallberg.
Date:December 1982
Formats:txt pdf
Obsoletes:RFC 0834
Obsoleted by:RFC 0836
Status:UNKNOWN
DOI:10.17487/RFC 0835
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 28-Dec-82 through 5-Jan-83.
 
RFC 836 Who talks TCP?
 
Authors:D. Smallberg.
Date:January 1983
Formats:txt pdf
Obsoletes:RFC 0835
Obsoleted by:RFC 0837
Status:UNKNOWN
DOI:10.17487/RFC 0836
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 20-Dec-82. The tests were run on 4-Jan-83 through 5-Jan-83.
 
RFC 837 Who talks TCP?
 
Authors:D. Smallberg.
Date:January 1983
Formats:txt pdf
Obsoletes:RFC 0836
Obsoleted by:RFC 0838
Status:UNKNOWN
DOI:10.17487/RFC 0837
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 11-Jan-83.
 
RFC 838 Who talks TCP?
 
Authors:D. Smallberg.
Date:January 1983
Formats:txt pdf
Obsoletes:RFC 0837
Obsoleted by:RFC 0839
Status:UNKNOWN
DOI:10.17487/RFC 0838
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 18-Jan-83.
 
RFC 839 Who talks TCP?
 
Authors:D. Smallberg.
Date:January 1983
Formats:txt pdf
Obsoletes:RFC 0838
Obsoleted by:RFC 0842
Status:UNKNOWN
DOI:10.17487/RFC 0839
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 25-Jan-83.
 
RFC 840 Official protocols
 
Authors:J. Postel.
Date:April 1983
Formats:txt pdf
Obsoleted by:RFC 0880
Status:HISTORIC
DOI:10.17487/RFC 0840
This RFC has been revised, see RFC 880.
 
RFC 842 Who talks TCP? - survey of 1 February 83
 
Authors:D. Smallberg.
Date:February 1983
Formats:txt pdf
Obsoletes:RFC 0839
Obsoleted by:RFC 0843
Status:UNKNOWN
DOI:10.17487/RFC 0842
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 28-Jan-83. The tests were run on 1-Feb-83 and on 2-Feb-83 ISI-VAXA.ARPA.
 
RFC 843 Who talks TCP? - survey of 8 February 83
 
Authors:D. Smallberg.
Date:February 1983
Formats:txt pdf
Obsoletes:RFC 0842
Obsoleted by:RFC 0845
Updated by:RFC 0844
Status:UNKNOWN
DOI:10.17487/RFC 0843
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 3-Feb-83. The tests were run on 8-Feb-83 and on 9-Feb-83 from ISI-VAXA.ARPA.
 
RFC 845 Who talks TCP? - survey of 15 February 1983
 
Authors:D. Smallberg.
Date:February 1983
Formats:txt pdf
Obsoletes:RFC 0843
Obsoleted by:RFC 0846
Status:UNKNOWN
DOI:10.17487/RFC 0845
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 3-Feb-83. The tests were run on 15-Feb-83 from ISI-VAXA.ARPA.
 
RFC 846 Who talks TCP? - survey of 22 February 1983
 
Authors:D. Smallberg.
Date:February 1983
Formats:txt pdf
Obsoletes:RFC 0845
Obsoleted by:RFC 0847
Status:UNKNOWN
DOI:10.17487/RFC 0846
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 18-Feb-83. The tests were run on 22-Feb-83 from ISI-VAXA.ARPA.
 
RFC 850 Standard for interchange of USENET messages
 
Authors:M.R. Horton.
Date:June 1983
Formats:txt pdf
Obsoleted by:RFC 1036
Status:UNKNOWN
DOI:10.17487/RFC 0850
This memo is distributed as an RFC only to make this information easily accessible to researchers in the ARPA community. It does not specify an Internet standard. This RFC defines the standard format for interchange of Network News articles among USENET sites. It describes the format for articles themselves, and gives partial standards for transmission of news. The news transmission is not entirely standardized in order to give a good deal of flexibility to the individual hosts to choose transmission hardware and software, whether to batch news and so on.
 
RFC 851 ARPANET 1822L Host Access Protocol
 
Authors:A.G. Malis.
Date:April 1983
Formats:txt pdf
Obsoletes:RFC 0802
Obsoleted by:RFC 0878
Status:UNKNOWN
DOI:10.17487/RFC 0851
This RFC specifies the ARPANET 1822L Host Access Protocol, which is a successor to the existing 1822 Host Access Protocol. 1822L allows ARPANET hosts to use logical names as well as 1822's physical port locations to address each other. This RFC is also being presented as a solicitation of comments on 1822L, especially from host network software implementers and maintainers. Obsoletes RFC 802.
 
RFC 870 Assigned numbers
 
Authors:J.K. Reynolds, J. Postel.
Date:October 1983
Formats:txt pdf
Obsoletes:RFC 0820
Obsoleted by:RFC 0900
Status:HISTORIC
DOI:10.17487/RFC 0870
This RFC documents the list of numbers assigned for networks, protocols, etc. Obsoletes RFCs 820, 790, 776, 770, 762, 758, 755, 750, 739, 604.
 
RFC 877 Standard for the transmission of IP datagrams over public data networks
 
Authors:J.T. Korb.
Date:September 1983
Formats:txt pdf
Obsoleted by:RFC 1356
Status:UNKNOWN
DOI:10.17487/RFC 0877
This RFC specifies a standard adopted by CSNET, the VAN gateway, and other organizations for the transmission of IP datagrams over the X.25-based public data networks.
 
RFC 879 The TCP Maximum Segment Size and Related Topics
 
Authors:J. Postel.
Date:November 1983
Formats:txt pdf
Obsoleted by:RFC 7805
Updated by:RFC 6691
Status:HISTORIC
DOI:10.17487/RFC 0879
This RFC discusses the TCP Maximum Segment Size Option and related topics. The purposes is to clarify some aspects of TCP and its interaction with IP. This memo is a clarification to the TCP specification, and contains information that may be considered as "advice to implementers".
 
RFC 880 Official protocols
 
Authors:J.K. Reynolds, J. Postel.
Date:October 1983
Formats:txt pdf
Obsoletes:RFC 0840
Obsoleted by:RFC 0901
Status:HISTORIC
DOI:10.17487/RFC 0880
This RFC identifies the documents specifying the official protocols used in the ARPA Internet. Annotations identify any revisions or changes planned. Obsoletes RFC 840.
 
RFC 882 Domain names: Concepts and facilities
 
Authors:P.V. Mockapetris.
Date:November 1983
Formats:txt pdf
Obsoleted by:RFC 1034, RFC 1035
Updated by:RFC 0973
Status:UNKNOWN
DOI:10.17487/RFC 0882
This RFC introduces domain style names, their use for ARPA Internet mail and host address support, and the protocol and servers used to implement domain name facilities.
 
RFC 883 Domain names: Implementation specification
 
Authors:P.V. Mockapetris.
Date:November 1983
Formats:txt pdf
Obsoleted by:RFC 1034, RFC 1035
Updated by:RFC 0973
Status:UNKNOWN
DOI:10.17487/RFC 0883
This RFC discusses the implementation of domain name servers and resolvers, specifies the format of transactions, and discusses the use of domain names in the context of existing mail systems and other network software.
 
RFC 884 Telnet terminal type option
 
Authors:M. Solomon, E. Wimmers.
Date:December 1983
Formats:txt pdf
Obsoleted by:RFC 0930
Status:UNKNOWN
DOI:10.17487/RFC 0884
This RFC specifies a standard for the ARPA Internet community. It specifies a method for exchanging terminal type information in the Telnet protocol.
 
RFC 892 ISO Transport Protocol specification
 
Authors:International Organization for Standardization.
Date:December 1983
Formats:txt pdf
Obsoleted by:RFC 0905
Status:UNKNOWN
DOI:10.17487/RFC 0892
This is a draft version of the transport protocol being standardized by the ISO. This version also appeared in the ACM SIGCOMM Computer Communication Review (V.12, N.3-4) July-October 1982. This version is now out of date.
 
RFC 896 Congestion Control in IP/TCP Internetworks
 
Authors:J. Nagle.
Date:January 1984
Formats:txt pdf
Obsoleted by:RFC 7805
Status:HISTORIC
DOI:10.17487/RFC 0896
This memo discusses some aspects of congestion control in IP/TCP Internetworks. It is intended to stimulate thought and further discussion of this topic. While some specific suggestions are made for improved congestion control implementation, this memo does not specify any standards.
 
RFC 900 Assigned Numbers
 
Authors:J.K. Reynolds, J. Postel.
Date:June 1984
Formats:txt pdf
Obsoletes:RFC 0870
Obsoleted by:RFC 0923
Status:HISTORIC
DOI:10.17487/RFC 0900
This RFC specifies parameter values use in the Internet family of protocols, such as network numbers, well known ports, protocol types, and version numbers. This memo is an official status report on the protocol parameters used in the Internet protocol system. See RFC-990 and 997.
 
RFC 901 Official ARPA-Internet protocols
 
Authors:J.K. Reynolds, J. Postel.
Date:June 1984
Formats:txt pdf
Obsoletes:RFC 0880
Obsoleted by:RFC 0924
Status:UNKNOWN
DOI:10.17487/RFC 0901
This RFC identifies the documents specifying the official protocols used in the ARPA-Internet. Annotations identify any revisions or changes planned. This memo is an official status report on the protocols used in the DARPA research community. See RFC-991.
 
RFC 912 Authentication service
 
Authors:M. St. Johns.
Date:September 1984
Formats:txt pdf
Obsoleted by:RFC 0931
Status:UNKNOWN
DOI:10.17487/RFC 0912
This memo describes a proposed authentication protocol for verifying the identity of a user of a TCP connection. Given a TCP port number pair, it returns a character string which identifies the owner of that connection on the server's system. Suggested uses include automatic identification and verification of a user during an FTP session, additional verification of a TAC dial up user, and access verification for a generalized network file server.
 
RFC 918 Post Office Protocol
 
Authors:J.K. Reynolds.
Date:October 1984
Formats:txt pdf
Obsoleted by:RFC 0937
Status:UNKNOWN
DOI:10.17487/RFC 0918
This RFC suggests a simple method for workstations to dynamically access mail from a mailbox server. The intent of the Post Office Protocol (POP) is to allow a user's workstation to access mail from a mailbox server. It is expected that mail will be posted from the workstation to the mailbox server via the Simple Mail Transfer Protocol (SMTP). This RFC specifies a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvement. The status of this protocol is experimental, and this protocol is dependent upon TCP.
 
RFC 923 Assigned numbers
 
Authors:J.K. Reynolds, J. Postel.
Date:October 1984
Formats:txt pdf
Obsoletes:RFC 0900
Obsoleted by:RFC 0943
Status:HISTORIC
DOI:10.17487/RFC 0923
This RFC documents the currently assigned values from several series of numbers used in network protocol implementations. This edition of Assigned Numbers obsoletes RFC-900 and earlier editions. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990, and 997.
 
RFC 924 Official ARPA-Internet protocols for connecting personal computers to the Internet
 
Authors:J.K. Reynolds, J. Postel.
Date:October 1984
Formats:txt pdf
Obsoletes:RFC 0901
Obsoleted by:RFC 0944
Status:UNKNOWN
DOI:10.17487/RFC 0924
This RFC identifies the documents specifying the official protocols used in the Internet. This edition of Official ARPA-Internet Protocols obsoletes RFC-900 and earlier editions. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991.
 
RFC 926 Protocol for providing the connectionless mode network services
 
Authors:International Organization for Standardization.
Date:December 1984
Formats:txt pdf
Obsoleted by:RFC 0994
Status:UNKNOWN
DOI:10.17487/RFC 0926
This note is the draft ISO protocol roughly similar to the DOD Internet Protocol. This document has been prepared by retyping the text of ISO DIS 8473 of May 1984, which is currently undergoing voting within ISO as a Draft International Standard (DIS). This document is distributred as an RFC for information only. It does not specify a standard for the ARPA-Internet.
 
RFC 930 Telnet terminal type option
 
Authors:M. Solomon, E. Wimmers.
Date:January 1985
Formats:txt pdf
Obsoletes:RFC 0884
Obsoleted by:RFC 1091
Status:UNKNOWN
DOI:10.17487/RFC 0930
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that exchange terminal type information within the Telnet protocol are expected to adopt and implement this standard. This standard supersedes RFC-884. The only change is to specify that the TERMINAL-TYPE IS sub-negotiation should be sent only in response to the TERMINAL-TYPE SEND sub-negotiation.
 
RFC 931 Authentication server
 
Authors:M. St. Johns.
Date:January 1985
Formats:txt pdf
Obsoletes:RFC 0912
Obsoleted by:RFC 1413
Status:UNKNOWN
DOI:10.17487/RFC 0931
This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. This is the second draft of this proposal (superseding RFC-912) and incorporates a more formal description of the syntax for the request and response dialog, as well as a change to specify the type of user identification returned.
 
RFC 943 Assigned numbers
 
Authors:J.K. Reynolds, J. Postel.
Date:April 1985
Formats:txt pdf
Obsoletes:RFC 0923
Obsoleted by:RFC 0960
Status:HISTORIC
DOI:10.17487/RFC 0943
This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This RFC will be updated periodically, and in any case current information can be obtained from Joyce Reynolds. The assignment of numbers is also handled by Joyce. If you are developing a protocol or application that will require the use of a link, socket, port, protocol, network number, etc., please contact Joyce to receive a number assignment. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990 and 997.
 
RFC 944 Official ARPA-Internet protocols
 
Authors:J.K. Reynolds, J. Postel.
Date:April 1985
Formats:txt pdf
Obsoletes:RFC 0924
Obsoleted by:RFC 0961
Status:UNKNOWN
DOI:10.17487/RFC 0944
This RFC identifies the documents specifying the official protocols used in the Internet. This edition of Official ARPA-Internet Protocols obsoletes RFC-924 and earlier editions. This RFC will be updated periodically, and current information can be obtained from Joyce Reynolds. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991.
 
RFC 945 DoD statement on the NRC report
 
Authors:J. Postel.
Date:May 1985
Formats:txt pdf
Obsoleted by:RFC 1039
Status:UNKNOWN
DOI:10.17487/RFC 0945
In May 1983 the National Research Council (NRC) was asked jointly by DoD and NBS to study the issues and recommend a course of action. The final report of the NRC committee was published in February 1985 (see RFC-942). The enclosed letter is from Donald C. Latham (ASDC3I) to DCA transmitting the NRC report and requesting specific actions relative to the recommendations of the report. This RFC reproduces a letter from the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASDC3I) to the Director of the Defense Communications Agency (DCA). This letter is distributed for information only.
 
RFC 948 Two methods for the transmission of IP datagrams over IEEE 802.3 networks
 
Authors:I. Winston.
Date:June 1985
Formats:txt pdf
Obsoleted by:RFC 1042
Status:UNKNOWN
DOI:10.17487/RFC 0948
This RFC describes two methods of encapsulating Internet Protocol (IP) datagrams on an IEEE 802.3 network. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
 
RFC 954 NICNAME/WHOIS
 
Authors:K. Harrenstien, M.K. Stahl, E.J. Feinler.
Date:October 1985
Formats:txt pdf
Obsoletes:RFC 0812
Obsoleted by:RFC 3912
Status:DRAFT STANDARD
DOI:10.17487/RFC 0954
This RFC is the official specification of the NICNAME/WHOIS protocol. This memo describes the protocol and the service. This is an update of RFC-812.
 
RFC 958 Network Time Protocol (NTP)
 
Authors:D.L. Mills.
Date:September 1985
Formats:txt pdf
Obsoleted by:RFC 1059, RFC 1119, RFC 1305
Status:UNKNOWN
DOI:10.17487/RFC 0958
This document describes the Network Time Protocol (NTP), a protocol for synchronizing a set of network clocks using a set of distributed clients and servers. NTP is built on the User Datagram Protocol (UDP), which provides a connectionless transport mechanism. It is evolved from the Time Protocol and the ICMP Timestamp message and is a suitable replacement for both. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
 
RFC 960 Assigned numbers
 
Authors:J.K. Reynolds, J. Postel.
Date:December 1985
Formats:txt pdf
Obsoletes:RFC 0943
Obsoleted by:RFC 0990
Status:HISTORIC
DOI:10.17487/RFC 0960
This memo documents the currently assigned values from several series of numbers used in network protocol implementations. This edition of Assigned Numbers updates and obsoletes RFC-943. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990 and 997.
 
RFC 961 Official ARPA-Internet protocols
 
Authors:J.K. Reynolds, J. Postel.
Date:December 1985
Formats:txt pdf
Obsoletes:RFC 0944
Obsoleted by:RFC 0991
Status:UNKNOWN
DOI:10.17487/RFC 0961
This memo identifies the documents specifying the official protocols used in the Internet, and comments on any revisions or changes planned. This edition of the Official Protocols updates and obsoletes RFC-944. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991.
 
RFC 966 Host groups: A multicast extension to the Internet Protocol
 
Authors:S.E. Deering, D.R. Cheriton.
Date:December 1985
Formats:txt pdf
Obsoleted by:RFC 0988
Status:UNKNOWN
DOI:10.17487/RFC 0966
This RFC defines a model of service for Internet multicasting and proposes an extension to the Internet Protocol (IP) to support such a multicast service. Discussion and suggestions for improvements are requested. See RFC-988.
 
RFC 969 NETBLT: A bulk data transfer protocol
 
Authors:D.D. Clark, M.L. Lambert, L. Zhang.
Date:December 1985
Formats:txt pdf
Obsoleted by:RFC 0998
Status:UNKNOWN
DOI:10.17487/RFC 0969
This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. This is a preliminary discussion of the Network Block Transfer (NETBLT) protocol. NETBLT is intended for the rapid transfer of a large quantity of data between computers. It provides a transfer that is reliable and flow controlled, and is structured to provide maximum throughput over a wide variety of networks. This description is published for discussion and comment, and does not constitute a standard. As the proposal may change, implementation of this document is not advised. See RFC-998.
 
RFC 973 Domain system changes and observations
 
Authors:P.V. Mockapetris.
Date:January 1986
Formats:txt pdf
Obsoleted by:RFC 1034, RFC 1035
Updates:RFC 0882, RFC 0883
Status:UNKNOWN
DOI:10.17487/RFC 0973
This RFC documents updates to Domain Name System specifications RFC-882 and RFC-883, suggests some operational guidelines, and discusses some experiences and problem areas in the present system.
 
RFC 974 Mail routing and the domain system
 
Authors:C. Partridge.
Date:January 1986
Formats:txt pdf
Obsoleted by:RFC 2821
Also:STD 0010
Status:HISTORIC
DOI:10.17487/RFC 0974
This RFC presents a description of how mail systems on the Internet are expected to route messages based on information from the domain system. This involves a discussion of how mailers interpret MX RRs, which are used for message routing.
 
RFC 977 Network News Transfer Protocol
 
Authors:B. Kantor, P. Lapsley.
Date:February 1986
Formats:txt pdf
Obsoleted by:RFC 3977
Status:PROPOSED STANDARD
DOI:10.17487/RFC 0977
NNTP specifies a protocol for the distribution, inquiry, retrieval, and posting of news articles using a reliable stream-based transmission of news among the ARPA-Internet community. NNTP is designed so that news articles are stored in a central database allowing a subscriber to select only those items he wishes to read. Indexing, cross-referencing, and expiration of aged messages are also provided. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
 
RFC 983 ISO transport arrives on top of the TCP
 
Authors:D.E. Cass, M.T. Rose.
Date:April 1986
Formats:txt pdf
Obsoleted by:RFC 1006
Status:UNKNOWN
DOI:10.17487/RFC 0983
This memo describes a proposed protocol standard for the ARPA Internet community. The CCITT and the ISO have defined various session, presentation, and application recommendations which have been adopted by the international community and numerous vendors. To the largest extent possible, it is desirable to offer these higher level services directly in the ARPA Internet, without disrupting existing facilities. This permits users to develop expertise with ISO and CCITT applications which previously were not available in the ARPA Internet. The intention is that hosts in the ARPA-Internet that choose to implement ISO TSAP services on top of the TCP be expected to adopt and implement this standard. Suggestions for improvement are encouraged.
 
RFC 984 PCMAIL: A distributed mail system for personal computers
 
Authors:D.D. Clark, M.L. Lambert.
Date:May 1986
Formats:txt pdf
Obsoleted by:RFC 0993
Status:UNKNOWN
DOI:10.17487/RFC 0984
This document is a preliminary discussion of the design of a personal-computer-based distributed mail system. Pcmail is a distributed mail system that provides mail service to an arbitrary number of users, each of which owns one or more personal computers (PCs). The system is divided into two halves. The first consists of a single entity called the "repository". The repository is a storage center for incoming mail. Mail for a Pcmail user can arrive externally from the Internet or internally from other repository users. The repository also maintains a stable copy of each user's mail state. The repository is therefore typically a computer with a large amount of disk storage. It is published for discussion and comment, and does not constitute a standard. As the proposal may change, implementation of this document is not advised. See RFC-993.
 
RFC 985 Requirements for Internet gateways - draft
 
Authors:National Science Foundation, Network Technical Advisory Group.
Date:May 1986
Formats:txt pdf
Obsoleted by:RFC 1009
Status:UNKNOWN
DOI:10.17487/RFC 0985
This RFC summarizes the requirements for gateways to be used on networks supporting the DARPA Internet protocols. While it applies specifically to National Science Foundation research programs, the requirements are stated in a general context and are believed applicable throughout the Internet community. The purpose of this document is to present guidance for vendors offering products that might be used or adapted for use in an Internet application. It enumerates the protocols required and gives references to RFCs and other documents describing the current specification.
 
RFC 986 Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol
 
Authors:R.W. Callon, H.W. Braun.
Date:June 1986
Formats:txt pdf
Obsoleted by:RFC 1069
Status:UNKNOWN
DOI:10.17487/RFC 0986
This RFC suggests a method to allow the existing IP addressing, including the IP protocol field, to be used for the ISO Connectionless Network Protocol (CLNP). This is a draft solution to one of the problems inherent in the use of "ISO-grams" in the DOD Internet. Related issues will be discussed in subsequent RFCs. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
 
RFC 987 Mapping between X.400 and RFC 822
 
Authors:S.E. Kille.
Date:June 1986
Formats:txt pdf
Obsoleted by:RFC 2156, RFC 1327
Updated by:RFC 1026, RFC 1138, RFC 1148
Status:UNKNOWN
DOI:10.17487/RFC 0987
The X.400 series protocols have been defined by CCITT to provide an Interpersonal Messaging Service (IPMS), making use of a store and forward Message Transfer Service. It is expected that this standard will be implemented very widely. This document describes a set of mappings which will enable interworking between systems operating the X.400 protocols and systems using RFC-822 mail protocol or protocols derived from RFC-822. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.
 
RFC 988 Host extensions for IP multicasting
 
Authors:S.E. Deering.
Date:July 1986
Formats:txt pdf
Obsoletes:RFC 0966
Obsoleted by:RFC 1054, RFC 1112
Status:UNKNOWN
DOI:10.17487/RFC 0988
This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support internetwork multicasting. This specification supersedes that given in RFC-966, and constitutes a proposed protocol standard for IP multicasting in the ARPA-Internet. The reader is directed to RFC-966 for a discussion of the motivation and rationale behind the multicasting extension specified here.
 
RFC 989 Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures
 
Authors:J. Linn.
Date:February 1987
Formats:txt pdf
Obsoleted by:RFC 1040, RFC 1113
Status:UNKNOWN
DOI:10.17487/RFC 0989
This RFC suggests a proposed protocol for the Internet community and requests discussion and suggestions for improvements. This RFC is the outgrowth of a series of IAB Privacy Task Force meetings and of internal working papers distributed for those meetings. This RFC defines message encipherment and authentication procedures, as the initial phase of an effort to provide privacy enhancement services for electronic mail transfer in the Internet. It is intended that the procedures defined here be compatible with a wide range of key management approaches, including both conventional (symmetric) and public-key (asymmetric) approaches for encryption of data encrypting keys. Use of conventional cryptography for message text encryption and/or authentication is anticipated.
 
RFC 990 Assigned numbers
 
Authors:J.K. Reynolds, J. Postel.
Date:November 1986
Formats:txt pdf
Obsoletes:RFC 0960
Obsoleted by:RFC 1010
Updated by:RFC 0997
Status:HISTORIC
DOI:10.17487/RFC 0990
This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-997. Obsoletes RFC-960, 943, 923 and 900.
 
RFC 991 Official ARPA-Internet protocols
 
Authors:J.K. Reynolds, J. Postel.
Date:November 1986
Formats:txt pdf
Obsoletes:RFC 0961
Obsoleted by:RFC 1011
Status:UNKNOWN
DOI:10.17487/RFC 0991
This RFC identifies the documents specifying the official protocols used in the Internet. Comments indicate any revisions or changes planned. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. Obsoletes RFC-961, 944 and 924.
 
RFC 993 PCMAIL: A distributed mail system for personal computers
 
Authors:D.D. Clark, M.L. Lambert.
Date:December 1986
Formats:txt pdf
Obsoletes:RFC 0984
Obsoleted by:RFC 1056
Status:UNKNOWN
DOI:10.17487/RFC 0993
This document is a discussion of the Pcmail workstation-based distributed mail system. It is a revision of the design published in NIC RFC-984. The revision is based on discussion and comment fromm a variety of sources, as well as further research into the design of interactive Pcmail clients and the use of client code on machines other than IBM PCs. As this design may change, implementation of this document is not advised. Obsoletes RFC-984.
 
RFC 997 Internet numbers
 
Authors:J.K. Reynolds, J. Postel.
Date:March 1987
Formats:txt pdf
Obsoleted by:RFC 1020, RFC 1117
Updates:RFC 0990
Status:UNKNOWN
DOI:10.17487/RFC 0997
This memo is an official status report on the network numbers used in the Internet community. As of 1-Mar-87 the Network Information Center (NIC) at SRI International has assumed responsibility for assignment of Network Numbers and Autonomous System Numbers. This RFC documents the current assignments of these numbers at the time of this transfer of responsibility. Obsoletes RFC-990, 960, 943, 923 and 900.
 
RFC 999 Requests For Comments summary notes: 900-999
 
Authors:A. Westine, J. Postel.
Date:April 1987
Formats:txt pdf
Obsoletes:RFC 0160
Obsoleted by:RFC 1000
Status:UNKNOWN
DOI:10.17487/RFC 0999
 
 
RFC 1009 Requirements for Internet gateways
 
Authors:R.T. Braden, J. Postel.
Date:June 1987
Formats:txt pdf
Obsoletes:RFC 0985
Obsoleted by:RFC 1812
Status:HISTORIC
DOI:10.17487/RFC 1009
This RFC summarizes the requirements for gateways to be used between networks supporting the Internet protocols. This document is a formal statement of the requirements to be met by gateways used in the Internet system. As such, it is an official specification for the Internet community.
 
RFC 1010 Assigned numbers
 
Authors:J.K. Reynolds, J. Postel.
Date:May 1987
Formats:txt pdf
Obsoletes:RFC 0990
Obsoleted by:RFC 1060
Status:HISTORIC
DOI:10.17487/RFC 1010
This memo is an official status report on the numbers used in protocols in the Internet community. It documents the currently assigned values from several series of numbers including link, socket, port, and protocol, used in network protocol implementations.
 
RFC 1020 Internet numbers
 
Authors:S. Romano, M.K. Stahl.
Date:November 1987
Formats:txt pdf
Obsoletes:RFC 0997
Obsoleted by:RFC 1062, RFC 1117, RFC 1166
Status:UNKNOWN
DOI:10.17487/RFC 1020
This RFC is a list of the Assigned IP Network Numbers and EGP Autonomous System Numbers. This RFC obsoletes RFC-997.
 
RFC 1023 HEMS monitoring and control language
 
Authors:G. Trewitt, C. Partridge.
Date:October 1987
Formats:txt pdf
Obsoleted by:RFC 1076
Status:UNKNOWN
DOI:10.17487/RFC 1023
This RFC specifies the High-Level Entity Management System (HEMS) Monitoring and Control Language. This language defines the requests and replies used in HEMS. This memo assumes knowledge of the HEMS system described in RFC-1021, and of the ISO data encoding standard, ASN.1.
 
RFC 1026 Addendum to RFC 987: (Mapping between X.400 and RFC-822)
 
Authors:S.E. Kille.
Date:September 1987
Formats:txt pdf
Obsoleted by:RFC 2156, RFC 1327
Updates:RFC 0987
Updated by:RFC 1138, RFC 1148
Status:UNKNOWN
DOI:10.17487/RFC 1026
This memo suggest a proposed protocol for the Internet community, and request discussion and suggestions for improvements.
 
RFC 1036 Standard for interchange of USENET messages
 
Authors:M.R. Horton, R. Adams.
Date:December 1987
Formats:txt pdf
Obsoletes:RFC 0850
Obsoleted by:RFC 5536, RFC 5537
Status:UNKNOWN
DOI:10.17487/RFC 1036
This RFC defines the standard format for the interchange of network News messages among USENET hosts. It updates and replaces RFC-850, reflecting version B2.11 of the News program. This memo is distributed as an RFC to make this information easily accessible to the Internet community. It does not specify an Internet standard.
 
RFC 1038 Draft revised IP security option
 
Authors:M. St. Johns.
Date:January 1988
Formats:txt pdf
Obsoleted by:RFC 1108
Status:UNKNOWN
DOI:10.17487/RFC 1038
This memo is a pre-publication draft of the revised Internet Protocol Security Option. This RFC reflects the version as approved by the Protocol Standards Steering group, and is provided for informational purposes only. The final version of this document will be available from Navy publications and should not differ from this document in any major fashion. This document will be published as a change to the MIL- STD 1777, "Internet Protocol".
 
RFC 1040 Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures
 
Authors:J. Linn.
Date:January 1988
Formats:txt pdf
Obsoletes:RFC 0989
Obsoleted by:RFC 1113
Status:UNKNOWN
DOI:10.17487/RFC 1040
This RFC is the Outgrowth of a series of IAB Privacy Task Force meetings and of internal working papers distributed for those meetings. This memo defines message encipherment and authentication procedures, as the initial phase of an effort to provide privacy enhancement services for electronic mail transfer in the Internet. Detailed key management mechanisms to support these procedures will be defined in a subsequent RFC. As a goal of this initial phase, it is intended that the procedures defined here be compatible with a wide range of key management approaches, including both conventional (symmetric) and public-key (asymmetric) approaches for encryption of data encrypting keys. Use of conventional cryptography for message text encryption and/or integrity check computation is anticipated.
 
RFC 1048 BOOTP vendor information extensions
 
Authors:P.A. Prindeville.
Date:February 1988
Formats:txt pdf
Obsoleted by:RFC 1084, RFC 1395, RFC 1497, RFC 1533
Status:UNKNOWN
DOI:10.17487/RFC 1048
This memo proposes an addition to the Bootstrap Protocol (BOOTP). Comments and suggestions for improvements are sought.
 
RFC 1050 RPC: Remote Procedure Call Protocol specification
 
Authors:Sun Microsystems.
Date:April 1988
Formats:txt pdf
Obsoleted by:RFC 1057
Status:HISTORIC
DOI:10.17487/RFC 1050
This memo specifies a message protocol used in implementing Sun's Remote Procedure Call (RPC) package. This RFC describes a standard that Sun Microsystems and others are using and is one they wish to propose for the Internet's consideration. It is not an Internet standard at this time.
 
RFC 1051 Standard for the transmission of IP datagrams and ARP packets over ARCNET networks
 
Authors:P.A. Prindeville.
Date:March 1988
Formats:txt pdf
Obsoleted by:RFC 1201
Status:HISTORIC
DOI:10.17487/RFC 1051
This memo specifies a standard method of encapsulating Internet Protocol (IP) and Address Resolution Protocol (ARP) datagrams on an ARCNET. This RFC is a standard protocol for the Internet community.
 
RFC 1054 Host extensions for IP multicasting
 
Authors:S.E. Deering.
Date:May 1988
Formats:txt pdf
Obsoletes:RFC 0988
Obsoleted by:RFC 1112
Status:UNKNOWN
DOI:10.17487/RFC 1054
This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. IP multicasting is the transmission of an IP datagram to a "host group", a set hosts identified by a single IP destination address. A multicast datagram is delivered to all members of its destination host group with the same "best-efforts" reliability as regular unicast IP datagrams. It is proposed as a standard for IP multicasting in the Internet. This specification is a major revision of RFC-988.
 
RFC 1059 Network Time Protocol (version 1) specification and implementation
 
Authors:D.L. Mills.
Date:July 1988
Formats:txt pdf
Obsoletes:RFC 0958
Obsoleted by:RFC 1119, RFC 1305
Status:UNKNOWN
DOI:10.17487/RFC 1059
This memo describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. NTP provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse internet operating at rates from mundane to lightwave. It uses a returnable-time design in which a distributed subnet of time servers operating in a self- organizing, hierarchical master-slave configuration synchronizes logical clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute reference time via local routing algorithms and time daemons. The NTP architectures, algorithms and protocols which have evolved over several years of implementation and refinement are described in this document. The prototype system, which has been in regular operation in the Internet for the last two years, is described in an Appendix along with performance data which shows that timekeeping accuracy throughout most portions of the Internet can be ordinarily maintained to within a few tens of milliseconds, even the cases of failure or disruption of clocks, time servers or nets. This is a Draft Standard for an Elective protocol.
 
RFC 1060 Assigned numbers
 
Authors:J.K. Reynolds, J. Postel.
Date:March 1990
Formats:txt pdf
Obsoletes:RFC 1010
Obsoleted by:RFC 1340
Updated by:RFC 1349
Status:HISTORIC
DOI:10.17487/RFC 1060
This memo is a status report on the parameters (i.e., numbers and keywords) used in protocols in the Internet community. Distribution of this memo is unlimited.
 
RFC 1062 Internet numbers
 
Authors:S. Romano, M.K. Stahl, M. Recker.
Date:August 1988
Formats:txt pdf
Obsoletes:RFC 1020
Obsoleted by:RFC 1117, RFC 1166
Status:UNKNOWN
DOI:10.17487/RFC 1062
This memo is an official status report on the network numbers and gateway autonomous system numbers used in the Internet community.
 
RFC 1063 IP MTU discovery options
 
Authors:J.C. Mogul, C.A. Kent, C. Partridge, K. McCloghrie.
Date:July 1988
Formats:txt pdf
Obsoleted by:RFC 1191
Status:UNKNOWN
DOI:10.17487/RFC 1063
A pair of IP options that can be used to learn the minimum MTU of a path through an internet is described, along with its possible uses. This is a proposal for an Experimental protocol.
 
RFC 1064 Interactive Mail Access Protocol: Version 2
 
Authors:M.R. Crispin.
Date:July 1988
Formats:txt pdf
Obsoleted by:RFC 1176, RFC 1203
Status:UNKNOWN
DOI:10.17487/RFC 1064
This memo suggests a method for workstations to dynamically access mail from a mailbox server ("respository"). This RFC specifies a standard for the SUMEX-AIM community and a proposed experimental protocol for the Internet community. Discussion and suggestions for improvement are requested.
 
RFC 1065 Structure and identification of management information for TCP/IP-based internets
 
Authors:K. McCloghrie, M.T. Rose.
Date:August 1988
Formats:txt pdf
Obsoleted by:RFC 1155
Status:INTERNET STANDARD
DOI:10.17487/RFC 1065
This RFC provides the common definitions for the structure and identification of management information for TCP/IP-based internets. In particular, together with its companion memos, which describe the initial management information base along with the initial network management protocol, these documents provide a simple, working architecture and system for managing TCP/IP-based internets and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementation in the Internet which are network manageable are expected to adopt and implement this specification.
 
RFC 1066 Management Information Base for network management of TCP/IP-based internets
 
Authors:K. McCloghrie, M.T. Rose.
Date:August 1988
Formats:txt pdf
Obsoleted by:RFC 1156
Status:UNKNOWN
DOI:10.17487/RFC 1066
This RFC provides the initial version of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets in the short-term. In particular, together with its companion memos which describe the structure of management information along with the initial network management protocol, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets, and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementations in the Internet which are network manageable are expected to adopt and implement this specification.
 
RFC 1067 Simple Network Management Protocol
 
Authors:J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin.
Date:August 1988
Formats:txt pdf
Obsoleted by:RFC 1098
Status:UNKNOWN
DOI:10.17487/RFC 1067
This RFC defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. In particular, together with its companion memos which describe the structure of management information along with the initial management information base, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementations in the Internet which are network manageable are expected to adopt and implement this specification.
 
RFC 1072 TCP extensions for long-delay paths
 
Authors:V. Jacobson, R.T. Braden.
Date:October 1988
Formats:txt pdf
Obsoleted by:RFC 1323, RFC 2018, RFC 6247
Status:HISTORIC
DOI:10.17487/RFC 1072
This RFC proposes a set of extensions to the TCP protocol to provide efficient operation over a path with a high bandwidth*delay product. These extensions are not proposed as an Internet standard at this time. Instead, they are intended as a basis for further experimentation and research on transport protocol performance.
 
RFC 1078 TCP port service Multiplexer (TCPMUX)
 
Authors:M. Lottor.
Date:November 1988
Formats:txt pdf
Obsoleted by:RFC 7805
Status:HISTORIC
DOI:10.17487/RFC 1078
This RFC proposes an Internet standard which can be used by future TCP services instead of using 'well-known ports'.
 
RFC 1080 Telnet remote flow control option
 
Authors:C.L. Hedrick.
Date:November 1988
Formats:txt pdf
Obsoleted by:RFC 1372
Status:UNKNOWN
DOI:10.17487/RFC 1080
This RFC specifies a standard for the Internet community. Hosts on the Internet that do remote flow control within the Telnet protocol are expected to adopt and implement this standard.
 
RFC 1081 Post Office Protocol: Version 3
 
Authors:M.T. Rose.
Date:November 1988
Formats:txt pdf
Obsoleted by:RFC 1225
Status:UNKNOWN
DOI:10.17487/RFC 1081
This memo suggests a simple method for workstations to dynamically access mail from a mailbox server. This RFC specifies a proposed protocol for the Internet community, and requests discussion and suggestions for improvements.
 
RFC 1083 IAB official protocol standards
 
Authors:Defense Advanced Research Projects Agency, Internet Activities Board.
Date:December 1988
Formats:txt pdf
Obsoleted by:RFC 1100
Status:HISTORIC
DOI:10.17487/RFC 1083
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures is presented first, followed by discussions of the standardization process and the RFC document series, then the explanation of the terms is presented, the lists of protocols in each stage of standardization follows, and finally pointers to references and contacts for further information. This memo is issued quarterly, please be sure the copy you are reading is dated within the last three months.
 
RFC 1084 BOOTP vendor information extensions
 
Authors:J.K. Reynolds.
Date:December 1988
Formats:txt pdf
Obsoletes:RFC 1048
Obsoleted by:RFC 1395, RFC 1497, RFC 1533
Status:UNKNOWN
DOI:10.17487/RFC 1084
This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville. This memo will be updated as additional tags are are defined. This edition introduces Tag 13 for Boot File Size. Comments and suggestions for improvements are sought.
 
RFC 1089 SNMP over Ethernet
 
Authors:M. Schoffstall, C. Davin, M. Fedor, J. Case.
Date:February 1989
Formats:txt pdf
Obsoleted by:RFC 4789
Status:UNKNOWN
DOI:10.17487/RFC 1089
This memo describes an experimental method by which the Simple Network Management Protocol (SNMP) can be used over Ethernet MAC layer framing instead of the Internet UDP/IP protocol stack. This specification is useful for LAN based network elements that support no higher layer protocols beyond the MAC sub-layer.
 
RFC 1095 Common Management Information Services and Protocol over TCP/IP (CMOT)
 
Authors:U.S. Warrier, L. Besaw.
Date:April 1989
Formats:txt pdf
Obsoleted by:RFC 1189
Status:UNKNOWN
DOI:10.17487/RFC 1095
This memo defines a network management architecture that uses the International Organization for Standardization's (ISO) Common Management Information Services/Common Management Information Protocol (CMIS/CMIP) in a TCP/IP environment. This architecture provides a means by which control and monitoring information can be exchanged between a manager and a remote network element. In particular, this memo defines the means for implementing the Draft International Standard (DIS) version of CMIS/CMIP on top of Internet transport protocols for the purpose of carrying management information defined in the Internet-standard management information base. DIS CMIS/CMIP is suitable for deployment in TCP/IP networks while CMIS/CMIP moves toward becoming an International Standard. Together with the relevant ISO standards and the companion RFCs that describe the initial structure of management information and management information base, these documents provide the basis for a comprehensive architecture and system for managing TCP/IP- based internets, and in particular the Internet.
 
RFC 1098 Simple Network Management Protocol (SNMP)
 
Authors:J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin.
Date:April 1989
Formats:txt pdf
Obsoletes:RFC 1067
Obsoleted by:RFC 1157
Status:UNKNOWN
DOI:10.17487/RFC 1098
This RFC is a re-release of RFC 1067, with a changed "Status of this Memo" section. This memo defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. In particular, together with its companion memos which describe the structure of management information along with the initial management information base, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular the Internet.
 
RFC 1100 IAB official protocol standards
 
Authors:Defense Advanced Research Projects Agency, Internet Activities Board.
Date:April 1989
Formats:txt pdf
Obsoletes:RFC 1083
Obsoleted by:RFC 1130
Status:HISTORIC
DOI:10.17487/RFC 1100
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures is presented first, followed by discussions of the standardization process and the RFC document series, then the explanation of the terms is presented, the lists of protocols in each stage of standardization follows, and finally pointers to references and contacts for further information. This memo is issued quarterly, please be sure the copy you are reading is dated within the last three months. Current copies may be obtained from the Network Information Center or from the Internet Assigned Numbers Authority (see the contact information at the end of this memo). Do not use this memo after 31-July-89.
 
RFC 1103 Proposed standard for the transmission of IP datagrams over FDDI Networks
 
Authors:D. Katz.
Date:June 1989
Formats:txt pdf
Obsoleted by:RFC 1188
Status:UNKNOWN
DOI:10.17487/RFC 1103
This RFC specifies a method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK]
 
RFC 1105 Border Gateway Protocol (BGP)
 
Authors:K. Lougheed, Y. Rekhter.
Date:June 1989
Formats:txt pdf
Obsoleted by:RFC 1163
Status:EXPERIMENTAL
DOI:10.17487/RFC 1105
This RFC outlines a specific approach for the exchange of network reachability information between Autonomous Systems. Updated by RFCs 1163 and 1164. [STANDARDS-TRACK]
 
RFC 1106 TCP big window and NAK options
 
Authors:R. Fox.
Date:June 1989
Formats:txt pdf
Obsoleted by:RFC 6247
Status:HISTORIC
DOI:10.17487/RFC 1106
Two extensions to the TCP protocol are described in this RFC in order to provide a more efficient operation over a network with a high bandwidth*delay product. The main issue that still needs to be solved is congestion versus noise. This issue is touched on in this memo, but further research is still needed on the applicability of the extensions in the Internet as a whole infrastructure and not just high bandwidth*delay product networks. Even with this outstanding issue, this document does describe the use of these options in the isolated satellite network environment to help facilitate more efficient use of this special medium to help off load bulk data transfers from links needed for interactive use.
 
RFC 1110 Problem with the TCP big window option
 
Authors:A.M. McKenzie.
Date:August 1989
Formats:txt pdf
Obsoleted by:RFC 6247
Status:HISTORIC
DOI:10.17487/RFC 1110
The TCP Big Window option discussed in RFC 1106 will not work properly in an Internet environment which has both a high bandwidth * delay product and the possibility of disordering and duplicating packets. In such networks, the window size must not be increased without a similar increase in the sequence number space. Therefore, a different approach to big windows should be taken in the Internet.
 
RFC 1111 Request for comments on Request for Comments: Instructions to RFC authors
 
Authors:J. Postel.
Date:August 1989
Formats:txt pdf
Obsoletes:RFC 0825
Obsoleted by:RFC 1543, RFC 2223
Status:INFORMATIONAL
DOI:10.17487/RFC 1111
This RFC specifies a standard for the Internet community. Authors of RFCs are expected to adopt and implement this standard.
 
RFC 1113 Privacy enhancement for Internet electronic mail: Part I - message encipherment and authentication procedures
 
Authors:J. Linn.
Date:August 1989
Formats:txt pdf
Obsoletes:RFC 0989, RFC 1040
Obsoleted by:RFC 1421
Status:HISTORIC
DOI:10.17487/RFC 1113
This RFC specifies features for private electronic mail based on encryption technology. [STANDARDS-TRACK]
 
RFC 1114 Privacy enhancement for Internet electronic mail: Part II - certificate-based key management
 
Authors:S.T. Kent, J. Linn.
Date:August 1989
Formats:txt pdf
Obsoleted by:RFC 1422
Status:HISTORIC
DOI:10.17487/RFC 1114
This RFC specifies the key management aspects of Privacy Enhanced Mail. [STANDARDS-TRACK]
 
RFC 1115 Privacy enhancement for Internet electronic mail: Part III - algorithms, modes, and identifiers
 
Authors:J. Linn.
Date:August 1989
Formats:txt pdf
Obsoleted by:RFC 1423
Status:HISTORIC
DOI:10.17487/RFC 1115
This RFC provides definitions, references, and citations for algorithms, usage modes, and associated identifiers used in RFC-1113 and RFC-1114 in support of privacy-enhanced electronic mail. [STANDARDS-TRACK]
 
RFC 1116 Telnet Linemode option
 
Authors:D.A. Borman.
Date:August 1989
Formats:txt pdf
Obsoleted by:RFC 1184
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1116
Hosts on the Internet that support Linemode within the Telnet protocol are expected to adopt and implement this protocol. Obsoleted by RFC 1184. [STANDARDS-TRACK]
 
RFC 1117 Internet numbers
 
Authors:S. Romano, M.K. Stahl, M. Recker.
Date:August 1989
Formats:txt pdf
Obsoletes:RFC 1062, RFC 1020, RFC 0997
Obsoleted by:RFC 1166
Status:INFORMATIONAL
DOI:10.17487/RFC 1117
This memo is an official status report on the network numbers and the autonomous system numbers used in the Internet community.
 
RFC 1119 Network Time Protocol (version 2) specification and implementation
 
Authors:D.L. Mills.
Date:September 1989
Formats:txt ps pdf
Obsoletes:RFC 0958, RFC 1059
Obsoleted by:RFC 1305
Status:INTERNET STANDARD
DOI:10.17487/RFC 1119
This document describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. NTP provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse internet operating at rates from mundane to lightwave. It uses a returnable-time design in which a distributed subnet of time servers operating in a self- organizing, hierarchical-master-slave configuration synchronizes local clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute reference time via local routing algorithms and time daemons. [STANDARDS-TRACK]
 
RFC 1120 Internet Activities Board
 
Authors:V. Cerf.
Date:September 1989
Formats:txt pdf
Obsoleted by:RFC 1160
Status:INFORMATIONAL
DOI:10.17487/RFC 1120
This RFC provides a history and description of the Internet Activities Board (IAB) and its subsidiary organizations. This memo is for informational use and does not constitute a standard.
 
RFC 1130 IAB official protocol standards
 
Authors:Defense Advanced Research Projects Agency, Internet Activities Board.
Date:October 1989
Formats:txt pdf
Obsoletes:RFC 1100
Obsoleted by:RFC 1140
Status:HISTORIC
DOI:10.17487/RFC 1130
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB).
 
RFC 1131 OSPF specification
 
Authors:J. Moy.
Date:October 1989
Formats:txt ps pdf
Obsoleted by:RFC 1247
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1131
This RFC is the specification of the Open Shortest Path First (OSPF) Internet routing protocol. OSPF is in the class of Internal Gateway Protocols (IGPs) for distributing routing information between gateways of a single Autonomous System. This routing protocol is based on the link-state approach (in contrast to the distance-vector approach). This specification was developed by the OSPF Working Group of the Internet Engineering Task Force. [STANDARDS-TRACK]
 
RFC 1134 Point-to-Point Protocol: A proposal for multi-protocol transmission of datagrams over Point-to-Point links
 
Authors:D. Perkins.
Date:November 1989
Formats:txt pdf
Obsoleted by:RFC 1171
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1134
The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is composed of three parts:

1. A method for encapsulating datagrams over serial links.

2. An extensible Link Control Protocol (LCP).

3. A family of Network Control Protocols (NCP) for establishing and configuring different network-layer protocols.

This document defines the encapsulation scheme, the basic LCP, and anNCP for establishing and configuring the Internet Protocol (IP)(called the IP Control Protocol, IPCP).

The options and facilities used by the LCP and the IPCP are defined in separate documents. Control protocols for configuring and utilizing other network-layer protocols besides IP (e.g., DECNET,OSI) are expected to be developed as needed.

 
RFC 1138 Mapping between X.400(1988) / ISO 10021 and RFC 822
 
Authors:S.E. Kille.
Date:December 1989
Formats:txt pdf
Obsoleted by:RFC 2156, RFC 1327
Updates:RFC 1026, RFC 0987, RFC 0822
Updated by:RFC 1148
Status:EXPERIMENTAL
DOI:10.17487/RFC 1138
Ths RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. This memo updates RFCs 822, 987, and 1026.
 
RFC 1139 Echo function for ISO 8473
 
Authors:R.A. Hagens.
Date:January 1990
Formats:txt pdf
Obsoleted by:RFC 1574, RFC 1575
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1139
This memo defines an echo function for the connection-less network layer protocol. Two mechanisms are introduced that may be used to implement the echo function. The first mechanism is recommended as an interim solution for the Internet community. The second mechanism will be progressed to the ANSI X3S3.3 working group for consideration as a work item.

When an ISO standard is adopted that provides functionality similar to that described by this memo, then this memo will become obsolete and superceded by the ISO standard.

 
RFC 1140 IAB official protocol standards
 
Authors:Defense Advanced Research Projects Agency, Internet Activities Board.
Date:May 1990
Formats:txt pdf
Obsoletes:RFC 1130
Obsoleted by:RFC 1200
Status:HISTORIC
DOI:10.17487/RFC 1140
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo is issued quarterly, please be sure the copy you are reading is dated within the last three months. Current copies may be obtained from the Network Information Center or from the Internet Assigned Numbers Authority. Do not use this edition after 31-Aug-90.
 
RFC 1142 OSI IS-IS Intra-domain Routing Protocol
 
Authors:D. Oran, Ed..
Date:February 1990
Formats:txt ps pdf
Obsoleted by:RFC 7142
Status:HISTORIC
DOI:10.17487/RFC 1142
This RFC is a republication of ISO DP 10589 as a service to the Internet community. This is not an Internet standard.
 
RFC 1145 TCP alternate checksum options
 
Authors:J. Zweig, C. Partridge.
Date:February 1990
Formats:txt pdf
Obsoleted by:RFC 1146, RFC 6247
Status:HISTORIC
DOI:10.17487/RFC 1145
This memo is suggests a pair of TCP options to allow use of alternate data checksum algorithms in the TCP header. The use of these options is experimental, and not recommended for production use.
 
RFC 1146 TCP alternate checksum options
 
Authors:J. Zweig, C. Partridge.
Date:March 1990
Formats:txt pdf
Obsoletes:RFC 1145
Obsoleted by:RFC 6247
Status:HISTORIC
DOI:10.17487/RFC 1146
This memo is suggests a pair of TCP options to allow use of alternate data checksum algorithms in the TCP header. The use of these options is experimental, and not recommended for production use. Note: This RFC corrects errors introduced in the editing process in RFC 1145.
 
RFC 1147 FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices
 
Authors:R.H. Stine.
Date:April 1990
Formats:txt pdf ps
Obsoleted by:RFC 1470
Status:INFORMATIONAL
DOI:10.17487/RFC 1147
The goal of this FYI memo is to provide practical information to site administrators and network managers. This memo provides information for the Internet community. It does not specify any standard. It is not a statement of IAB policy or recommendations. [Also FYI 2.] This catalog contains descriptions of several tools available to assist network managers in debugging and maintaining TCP/IP internets and interconnected communications resources. Entries in the catalog tell what a tool does, how it works, and how it can be obtained.
 
RFC 1148 Mapping between X.400(1988) / ISO 10021 and RFC 822
 
Authors:S.E. Kille.
Date:March 1990
Formats:txt pdf
Obsoleted by:RFC 2156, RFC 1327
Updates:RFC 1026, RFC 0987, RFC 1138, RFC 0822
Status:EXPERIMENTAL
DOI:10.17487/RFC 1148
This RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. This edition includes material lost in editing.
 
RFC 1150 FYI on FYI: Introduction to the FYI Notes
 
Authors:G.S. Malkin, J.K. Reynolds.
Date:March 1990
Formats:txt pdf
Obsoleted by:RFC 6360
Status:HISTORIC
DOI:10.17487/RFC 1150
This memo is the first in a new sub-series of RFCs called FYIs (For Your Information). This memo provides information for the Internet community. It does not specify any standard. [Also FYI 1.]
 
RFC 1154 Encoding header field for internet messages
 
Authors:D. Robinson, R. Ullmann.
Date:April 1990
Formats:txt pdf
Obsoleted by:RFC 1505
Status:EXPERIMENTAL
DOI:10.17487/RFC 1154
This RFC proposes an elective experimental Encoding header field to permit the mailing of multi-part, multi-structured messages. The use of Encoding updates RFC 1049 (Content-Type), and is a suggested update to RFCs 1113, 1114, and 1115 (Privacy Enhancement).
 
RFC 1158 Management Information Base for network management of TCP/IP-based internets: MIB-II
 
Authors:M.T. Rose.
Date:May 1990
Formats:txt pdf
Obsoleted by:RFC 1213
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1158
This memo defines the second version of the Management Information Base (MIB-II) for use with network management protocols in TCP/IP- based internets. In particular, together with its companion memos which describe the structure of management information (RFC 1155) along with the network management protocol (RFC 1157) for TCP/IP- based internets, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular the Internet community. This document on MIB-II incorporates all of the technical content of RFC 1156 on MIB-I and extends it, without loss of compatibilty. [STANDARDS-TRACK]
 
RFC 1159 Message Send Protocol
 
Authors:R. Nelson.
Date:June 1990
Formats:txt pdf
Obsoleted by:RFC 1312
Status:EXPERIMENTAL
DOI:10.17487/RFC 1159
This RFC suggests an Experimental Protocol for the Internet community. Hosts on the Internet that choose to implement a Message Send Protocol may experiment with this protocol.
 
RFC 1161 SNMP over OSI
 
Authors:M.T. Rose.
Date:June 1990
Formats:txt pdf
Obsoleted by:RFC 1418
Status:EXPERIMENTAL
DOI:10.17487/RFC 1161
This memo defines an experimental means for running the Simple Network Management Protocol (SNMP) over OSI transports. This memo does not specify a standard for the Internet community,
 
RFC 1162 Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) Management Information Base
 
Authors:G. Satz.
Date:June 1990
Formats:txt pdf
Obsoleted by:RFC 1238
Status:EXPERIMENTAL
DOI:10.17487/RFC 1162
This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. This memo does not specify a standard for the Internet community.
 
RFC 1163 Border Gateway Protocol (BGP)
 
Authors:K. Lougheed, Y. Rekhter.
Date:June 1990
Formats:txt pdf
Obsoletes:RFC 1105
Obsoleted by:RFC 1267
Status:HISTORIC
DOI:10.17487/RFC 1163
This RFC, together with its companion RFC-1164, "Application of the Border Gateway Protocol in the Internet", specify an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK]
 
RFC 1164 Application of the Border Gateway Protocol in the Internet
 
Authors:J.C. Honig, D. Katz, M. Mathis, Y. Rekhter, J.Y. Yu.
Date:June 1990
Formats:txt pdf
Obsoleted by:RFC 1268
Status:HISTORIC
DOI:10.17487/RFC 1164
This RFC, together with its companion RFC-1163, "A Border Gateway Protocol (BGP)", specify an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK]
 
RFC 1171 Point-to-Point Protocol for the transmission of multi-protocol datagrams over Point-to-Point links
 
Authors:D. Perkins.
Date:July 1990
Formats:txt pdf
Obsoletes:RFC 1134
Obsoleted by:RFC 1331
Status:DRAFT STANDARD
DOI:10.17487/RFC 1171
The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is composed of three parts:

1. A method for encapsulating datagrams over serial links.

2. An extensible Link Control Protocol (LCP).

3. A family of Network Control Protocols (NCP) for establishing and configuring different network-layer protocols.

This document defines the encapsulation scheme, the basic LCP, and anNCP for establishing and configuring the Internet Protocol (IP)(called the IP Control Protocol, IPCP).

The options and facilities used by the LCP and the IPCP are defined in separate documents. Control protocols for configuring and utilizing other network-layer protocols besides IP (e.g., DECNET,OSI) are expected to be developed as needed.

 
RFC 1172 Point-to-Point Protocol (PPP) initial configuration options
 
Authors:D. Perkins, R. Hobby.
Date:July 1990
Formats:txt pdf
Obsoleted by:RFC 1331, RFC 1332
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1172
The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is composed of

1) a method for encapsulating datagrams over serial links,2) an extensible Link Control Protocol (LCP), and3) a family of Network Control Protocols (NCP) for establishing and configuring different network-layer protocols.

The PPP encapsulating scheme, the basic LCP, and an NCP for controlling and establishing the Internet Protocol (IP) (called theIP Control Protocol, IPCP) are defined in The Point-to-Point Protocol(PPP) [1].

This document defines the intial options used by the LCP and IPCP. It also defines a method of Link Quality Monitoring and a simple authentication scheme.

 
RFC 1177 FYI on Questions and Answers: Answers to commonly asked "new internet user" questions
 
Authors:G.S. Malkin, A.N. Marine, J.K. Reynolds.
Date:August 1990
Formats:txt pdf
Obsoleted by:RFC 1206
Status:INFORMATIONAL
DOI:10.17487/RFC 1177
This FYI RFC is one of three FYI's called, "Questions and Answers" (Q/A), produced by the User Services Working Group (USWG) of the Internet Engineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify any standard. [Also FYI 4.]
 
RFC 1185 TCP Extension for High-Speed Paths
 
Authors:V. Jacobson, R.T. Braden, L. Zhang.
Date:October 1990
Formats:txt pdf
Obsoleted by:RFC 1323
Status:EXPERIMENTAL
DOI:10.17487/RFC 1185
This memo describes an Experimental Protocol extension to TCP for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol.
 
RFC 1186 MD4 Message Digest Algorithm
 
Authors:R.L. Rivest.
Date:October 1990
Formats:txt pdf
Obsoleted by:RFC 1320
Status:INFORMATIONAL
DOI:10.17487/RFC 1186
This RFC is the specification of the MD4 Digest Algorithm. If you are going to implement MD4, it is suggested you do it this way. This memo is for informational use and does not constitute a standard.
 
RFC 1190 Experimental Internet Stream Protocol: Version 2 (ST-II)
 
Authors:C. Topolcic.
Date:October 1990
Formats:txt pdf
Obsoletes:IEN119
Obsoleted by:RFC 1819
Status:EXPERIMENTAL
DOI:10.17487/RFC 1190
This memo defines a revised version of the Internet Stream Protocol, originally defined in IEN-119 [8], based on results from experiments with the original version, and subsequent requests, discussion, and suggestions for improvements. This is a Limited-Use Experimental Protocol. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol.
 
RFC 1194 Finger User Information Protocol
 
Authors:D.P. Zimmerman.
Date:November 1990
Formats:txt pdf
Obsoletes:RFC 0742
Obsoleted by:RFC 1196, RFC 1288
Status:DRAFT STANDARD
DOI:10.17487/RFC 1194
This memo describes the Finger User Information Protocol. This is a simple protocol which provides an interface to a remote user information program.

Based on RFC 742, a description of the original Finger protocol, this memo attempts to clarify the expected communication between the two ends of a Finger connection. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition.

 
RFC 1196 Finger User Information Protocol
 
Authors:D.P. Zimmerman.
Date:December 1990
Formats:txt pdf
Obsoletes:RFC 1194, RFC 0742
Obsoleted by:RFC 1288
Status:DRAFT STANDARD
DOI:10.17487/RFC 1196
This memo describes the Finger User Information Protocol. This is a simple protocol which provides an interface to a remote user information program.

Based on RFC 742, a description of the original Finger protocol, this memo attempts to clarify the expected communication between the two ends of a Finger connection. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition. This edition corrects and clarifies in a minor way, RFC 1194.

 
RFC 1200 IAB official protocol standards
 
Authors:Defense Advanced Research Projects Agency, Internet Activities Board.
Date:April 1991
Formats:txt pdf
Obsoletes:RFC 1140
Obsoleted by:RFC 1250
Status:HISTORIC
DOI:10.17487/RFC 1200
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures is presented first, followed by discussions of the standardization process and the RFC document series, then the explanation of the terms is presented, the lists of protocols in each stage of standardization follows, and finally pointers to references and contacts for further information.
 
RFC 1206 FYI on Questions and Answers: Answers to commonly asked "new Internet user" questions
 
Authors:G.S. Malkin, A.N. Marine.
Date:February 1991
Formats:txt pdf
Obsoletes:RFC 1177
Obsoleted by:RFC 1325
Status:INFORMATIONAL
DOI:10.17487/RFC 1206
This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify any standard. [FYI 4]
 
RFC 1218 Naming scheme for c=US
 
Authors:North American Directory Forum.
Date:April 1991
Formats:txt pdf
Obsoleted by:RFC 1255, RFC 1417
Status:INFORMATIONAL
DOI:10.17487/RFC 1218
This RFC is a near-verbatim copy of a document, known as NADF-123, which has been produced by the North American Directory Forum (NADF). As a part of its charter, the NADF must reach agreement as to how entries are named in the public portions of the North American Directory. This memo provides information for the Internet community. It does not specify an Internet standard.
 
RFC 1220 Point-to-Point Protocol extensions for bridging
 
Authors:F. Baker.
Date:April 1991
Formats:txt pdf
Obsoleted by:RFC 1638
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1220
This document defines an extension of the Internet Point-to-Point Protocol (PPP) described in RFC 1171, targeting the use of Point-to- Point lines for Remote Bridging. [STANDARDS-TRACK]
 
RFC 1225 Post Office Protocol: Version 3
 
Authors:M.T. Rose.
Date:May 1991
Formats:txt pdf
Obsoletes:RFC 1081
Obsoleted by:RFC 1460
Status:DRAFT STANDARD
DOI:10.17487/RFC 1225
This memo suggests a simple method for workstations to dynamically access mail from a mailbox server. [STANDARDS-TRACK]
 
RFC 1228 SNMP-DPI: Simple Network Management Protocol Distributed Program Interface
 
Authors:G. Carpenter, B. Wijnen.
Date:May 1991
Formats:txt pdf
Obsoleted by:RFC 1592
Status:EXPERIMENTAL
DOI:10.17487/RFC 1228
This RFC describes a protocol that International Business Machines Corporation (IBM) has been implementing in most of its SNMP agents to allow dynamic extension of supported MIBs. This is an Experimental Protocol for the Internet community. It does not specify an Internet standard.
 
RFC 1229 Extensions to the generic-interface MIB
 
Authors:K. McCloghrie.
Date:May 1991
Formats:txt pdf
Obsoleted by:RFC 1573
Updated by:RFC 1239
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1229
This RFC contains definitions of managed objects used as experimental extensions to the generic interfaces structure of MIB-II. [STANDARDS- TRACK]
 
RFC 1231 IEEE 802.5 Token Ring MIB
 
Authors:K. McCloghrie, R. Fox, E. Decker.
Date:May 1991
Formats:txt pdf
Obsoleted by:RFC 1743, RFC 1748
Updated by:RFC 1239
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1231
This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, this memo defines managed objects used for managing subnetworks which use the IEEE 802.5 Token Ring technology described in 802.5 Token Ring Access Method and Physical Layer Specifications, IEEE Standard 802.5-1989. [STANDARDS-TRACK]
 
RFC 1232 Definitions of managed objects for the DS1 Interface type
 
Authors:F. Baker, C.P. Kolb.
Date:May 1991
Formats:txt pdf
Obsoleted by:RFC 1406
Updated by:RFC 1239
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1232
 
 
RFC 1233 Definitions of managed objects for the DS3 Interface type
 
Authors:T.A. Cox, K. Tesink.
Date:May 1991
Formats:txt pdf
Obsoleted by:RFC 1407
Updated by:RFC 1239
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1233
This memo defines objects for managing DS3 Interface objects for use with the SNMP protocol. [STANDARDS-TRACK]
 
RFC 1237 Guidelines for OSI NSAP Allocation in the Internet
 
Authors:R. Colella, E. Gardner, R. Callon.
Date:July 1991
Formats:txt pdf ps
Obsoleted by:RFC 1629
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1237
This paper provides guidelines for allocating NSAPs in the Internet.[STANDARDS-TRACK]
 
RFC 1243 AppleTalk Management Information Base
 
Authors:S. Waldbusser.
Date:July 1991
Formats:txt pdf
Obsoleted by:RFC 1742
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1243
This memo defines objects for managing AppleTalk objects for use with the SNMP protocol. [STANDARDS-TRACK]
 
RFC 1244 Site Security Handbook
 
Authors:J.P. Holbrook, J.K. Reynolds.
Date:July 1991
Formats:txt pdf
Obsoleted by:RFC 2196
Status:INFORMATIONAL
DOI:10.17487/RFC 1244
This FYI RFC is a first attempt at providing Internet users guidance on how to deal with security issues in the Internet. This FYI RFC provides information for the Internet community. It does not specify an Internet standard. [FYI 8]
 
RFC 1247 OSPF Version 2
 
Authors:J. Moy.
Date:July 1991
Formats:txt pdf ps
Obsoletes:RFC 1131
Obsoleted by:RFC 1583
Updated by:RFC 1349
Also:RFC 1245, RFC 1246
Status:DRAFT STANDARD
DOI:10.17487/RFC 1247
This memo documents version 2 of the OSPF protocol. OSPF is a link- state based routing protocol. [STANDARDS-TRACK]
 
RFC 1248 OSPF Version 2 Management Information Base
 
Authors:F. Baker, R. Coltun.
Date:July 1991
Formats:txt pdf
Obsoleted by:RFC 1252
Updated by:RFC 1349
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1248
This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS-TRACK]
 
RFC 1250 IAB Official Protocol Standards
 
Authors:J. Postel.
Date:August 1991
Formats:txt pdf
Obsoletes:RFC 1200
Obsoleted by:RFC 2200, RFC 1280
Status:HISTORIC
DOI:10.17487/RFC 1250
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo provides information for the Internet community. It does not specify an Internet standard.
 
RFC 1251 Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members
 
Authors:G. Malkin.
Date:August 1991
Formats:txt pdf
Obsoleted by:RFC 1336
Status:INFORMATIONAL
DOI:10.17487/RFC 1251
This FYI RFC contains biographical information about members of the Internet Activities Board (IAB), the Internet Engineering Steering Group (IESG) of the Internet Engineering Task Force (IETF), and the the Internet Research Steering Group (IRSG) of the Internet Research Task Force (IRTF). This memo provides information for the Internet community. It does not specify an Internet standard. [FYI 9]
 
RFC 1252 OSPF Version 2 Management Information Base
 
Authors:F. Baker, R. Coltun.
Date:August 1991
Formats:txt pdf
Obsoletes:RFC 1248
Obsoleted by:RFC 1253
Also:RFC 1245, RFC 1247
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1252
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS- TRACK]
 
RFC 1253 OSPF Version 2 Management Information Base
 
Authors:F. Baker, R. Coltun.
Date:August 1991
Formats:txt pdf
Obsoletes:RFC 1252
Obsoleted by:RFC 1850
Also:RFC 1245, RFC 1246, RFC 1247
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1253
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS- TRACK]
 
RFC 1255 A Naming Scheme for c=US
 
Authors:The North American Directory Forum.
Date:September 1991
Formats:txt pdf
Obsoletes:RFC 1218
Obsoleted by:RFC 1417
Status:INFORMATIONAL
DOI:10.17487/RFC 1255
This memo documents the NADF's agreement as to how entries are named in the public portions of the North American Directory. This memo provides information for the Internet community. It does not specify an Internet standard.
 
RFC 1258 BSD Rlogin
 
Authors:B. Kantor.
Date:September 1991
Formats:txt pdf
Obsoleted by:RFC 1282
Status:INFORMATIONAL
DOI:10.17487/RFC 1258
The rlogin facility provides a remote-echoed, locally flow-controlled virtual terminal with proper flushing of output.This memo documents an existing protocol and common implementation that is extensively used on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
 
RFC 1264 Internet Engineering Task Force Internet Routing Protocol Standardization Criteria
 
Authors:R.M. Hinden.
Date:October 1991
Formats:txt pdf
Obsoleted by:RFC 4794
Status:HISTORIC
DOI:10.17487/RFC 1264
This informational RFC presents procedures for creating and documenting Internet standards on routing protocols. These procedures have been established by the Internet Activities Board (IAB) in consultation with the Internet Engineering Steering Group (IESG). This memo provides information for the Internet community. It does not specifiy an Internet standard.
 
RFC 1268 Application of the Border Gateway Protocol in the Internet
 
Authors:Y. Rekhter, P. Gross.
Date:October 1991
Formats:txt pdf
Obsoletes:RFC 1164
Obsoleted by:RFC 1655
Status:HISTORIC
DOI:10.17487/RFC 1268
This document, together with its companion document, "A BorderGateway Protocol (BGP-3)", define an inter-autonomous system routing protocol for the Internet. "A Border Gateway Protocol (BGP-3)" defines the BGP protocol specification, and this document describes the usage of the BGP in the Internet.

Information about the progress of BGP can be monitored and/or reported on the BGP mailing list (iwg@rice.edu).

 
RFC 1269 Definitions of Managed Objects for the Border Gateway Protocol: Version 3
 
Authors:S. Willis, J.W. Burruss.
Date:October 1991
Formats:txt pdf
Obsoleted by:RFC 4273
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1269
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Border Gateway Protocol. [STANDARDS-TRACK]
 
RFC 1271 Remote Network Monitoring Management Information Base
 
Authors:S. Waldbusser.
Date:November 1991
Formats:txt pdf
Obsoleted by:RFC 1757
Updated by:RFC 1513
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1271
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices. [STANDARDS-TRACK]
 
RFC 1274 The COSINE and Internet X.500 Schema
 
Authors:P. Barker, S. Kille.
Date:November 1991
Formats:txt pdf
Obsoleted by:RFC 4524
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1274
This document suggests an X.500 Directory Schema, or NamingArchitecture, for use in the COSINE and Internet X.500 pilots. The schema is independent of any specific implementation. As well as indicating support for the standard object classes and attributes, a large number of generally useful object classes and attributes are also defined. An appendix to this document includes a machine processable version of the schema.

This document also proposes a mechanism for allowing the schema to evolve in line with emerging requirements. Proformas to support this process are included.

Corrections and additions to the schema should be sent to na- update@cs.ucl.ac.uk list, as described within.

 
RFC 1280 IAB Official Protocol Standards
 
Authors:J. Postel.
Date:March 1992
Formats:txt pdf
Obsoletes:RFC 1250
Obsoleted by:RFC 1360
Status:HISTORIC
DOI:10.17487/RFC 1280
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo provides information for the Internet community. It does not specify an Internet standard.
 
RFC 1283 SNMP over OSI
 
Authors:M. Rose.
Date:December 1991
Formats:txt pdf
Obsoleted by:RFC 1418
Status:EXPERIMENTAL
DOI:10.17487/RFC 1283
This memo describes mappings from the SNMP onto both the COTS and the CLTS. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet Standard.
 
RFC 1284 Definitions of Managed Objects for the Ethernet-like Interface Types
 
Authors:J. Cook, Ed..
Date:December 1991
Formats:txt pdf
Obsoleted by:RFC 1398
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1284
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing ethernet-like objects. [STANDARDS-TRACK]
 
RFC 1286 Definitions of Managed Objects for Bridges
 
Authors:E. Decker, P. Langille, A. Rijsinghani, K. McCloghrie.
Date:December 1991
Formats:txt pdf
Obsoleted by:RFC 1493, RFC 1525
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1286
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for managing bridges based on the IEEE 802.1d draft standard between Local Area Network (LAN) segments. This memo is an extension to the SNMP MIB. [STANDARDS-TRACK]
 
RFC 1289 DECnet Phase IV MIB Extensions
 
Authors:J. Saperia.
Date:December 1991
Formats:txt pdf
Obsoleted by:RFC 1559
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1289
This memo defines a set of DECnet Phase IV extensions that have been created for the Internet MIB. When used in conjunction with the structure of management information (RFC 1155), the management information base for network management of TCP/IP-based internets(RFC 1213) and the Simple Network Management Protocol (RFC 1157), it will be possible to provide integrated network management of combinedTCP/IP and DECnet Phase IV based internets. This document was produced by the DECnet Phase IV MIB working group of the InternetEngineering Task Force (IETF).
 
RFC 1290 There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places
 
Authors:J. Martin.
Date:December 1991
Formats:txt pdf
Obsoleted by:RFC 1402
Status:INFORMATIONAL
DOI:10.17487/RFC 1290
This document was presented at the 1991 ACM SIGUCCS User ServicesConference. It appears here in its updated form.

There is a wealth of information on the network. In fact, so much information, that you could spend your entire life browsing. This paper will present some of the "gold nuggets" of information and file repositories on the network that could be of use to end users.

The ultimate goal is to make the route to these sources of information invisible to the user. At present, this is not easy to do. I will explain some of the techniques that can be used to make these nuggets easier to pick up so that we can all be richer.

 
RFC 1292 A Catalog of Available X.500 Implementations
 
Authors:R. Lang, R. Wright.
Date:January 1992
Formats:txt pdf
Obsoleted by:RFC 1632
Status:INFORMATIONAL
DOI:10.17487/RFC 1292
The goal of this document is to provide information regarding the availability and capability of implementations of X.500. Comments and critiques of this document, and new or updated descriptions ofX.500 implementations are welcome. Send them to the DirectoryInformation Services Infrastructure (DISI) Working Group(disi@merit.edu) or to the editors.
 
RFC 1293 Inverse Address Resolution Protocol
 
Authors:T. Bradley, C. Brown.
Date:January 1992
Formats:txt pdf
Obsoleted by:RFC 2390
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1293
This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK]
 
RFC 1294 Multiprotocol Interconnect over Frame Relay
 
Authors:T. Bradley, C. Brown, A. Malis.
Date:January 1992
Formats:txt pdf
Obsoleted by:RFC 1490, RFC 2427
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1294
This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. [STANDARDS-TRACK]
 
RFC 1295 User Bill of Rights for entries and listings in the Public Directory
 
Authors:The North American Directory Forum.
Date:January 1992
Formats:txt pdf
Obsoleted by:RFC 1417
Status:INFORMATIONAL
DOI:10.17487/RFC 1295
This RFC is a near-verbatim copy of a document, known as NADF-265, which has been produced by the North American Directory Forum (NADF).

User Bill of Rights for entries and listings in the Public Directory

The mission of the North American Directory Forum is to provide interconnected electronic directories which empower users with unprecedented access to public information. To address significant security and privacy issues, the North American Directory Forum introduces the following "User Bill of Rights" for entries in thePublic Directory. As a user, you have:

I. The right not to be listed.

II. The right to have you or your agent informed when your entry is created.

III. The right to examine your entry.

IV. The right to correct inaccurate information in your entry.

V. The right to remove specific information from your entry.

VI. The right to be assured that your listing in thePublic Directory will comply with US or Canadian law regulating privacy or access information.

VII. The right to expect timely fulfillment of these rights.

 
RFC 1298 SNMP over IPX
 
Authors:R. Wormley, S. Bostock.
Date:February 1992
Formats:txt pdf
Obsoleted by:RFC 1420
Status:INFORMATIONAL
DOI:10.17487/RFC 1298
This memo defines a convention for encapsulating Simple NetworkManagement Protocol (SNMP) [1] packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol [2].
 
RFC 1304 Definitions of Managed Objects for the SIP Interface Type
 
Authors:T. Cox, Ed., K. Tesink, Ed..
Date:February 1992
Formats:txt pdf
Obsoleted by:RFC 1694
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1304
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing SIP (SMDS InterfaceProtocol) objects.
 
RFC 1305 Network Time Protocol (Version 3) Specification, Implementation and Analysis
 
Authors:D. Mills.
Date:March 1992
Formats:txt tar pdf
Obsoletes:RFC 0958, RFC 1059, RFC 1119
Obsoleted by:RFC 5905
Status:DRAFT STANDARD
DOI:10.17487/RFC 1305
This document describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. [STANDARDS-TRACK]
 
RFC 1310 The Internet Standards Process
 
Authors:L. Chapin.
Date:March 1992
Formats:txt pdf
Obsoleted by:RFC 1602
Status:INFORMATIONAL
DOI:10.17487/RFC 1310
This memo documents the process currently used for the standardization of Internet protocols and procedures. [STANDARDS-TRACK]
 
RFC 1315 Management Information Base for Frame Relay DTEs
 
Authors:C. Brown, F. Baker, C. Carvalho.
Date:April 1992
Formats:txt pdf
Obsoleted by:RFC 2115
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1315
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing Frame Relay.
 
RFC 1316 Definitions of Managed Objects for Character Stream Devices
 
Authors:B. Stewart.
Date:April 1992
Formats:txt pdf
Obsoleted by:RFC 1658
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1316
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for the management of character stream devices. [STANDARDS-TRACK]
 
RFC 1317 Definitions of Managed Objects for RS-232-like Hardware Devices
 
Authors:B. Stewart.
Date:April 1992
Formats:txt pdf
Obsoleted by:RFC 1659
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1317
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for the management of RS-232-like devices. [STANDARDS-TRACK]
 
RFC 1318 Definitions of Managed Objects for Parallel-printer-like Hardware Devices
 
Authors:B. Stewart.
Date:April 1992
Formats:txt pdf
Obsoleted by:RFC 1660
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1318
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for the management of parallel-printer- like devices. [STANDARDS-TRACK]
 
RFC 1319 The MD2 Message-Digest Algorithm
 
Authors:B. Kaliski.
Date:April 1992
Formats:txt pdf
Obsoleted by:RFC 6149
Status:HISTORIC
DOI:10.17487/RFC 1319
This document describes the MD2 message-digest algorithm. The algorithm takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. This memo provides information for the Internet community. It does not specify an Internet standard.
 
RFC 1320 The MD4 Message-Digest Algorithm
 
Authors:R. Rivest.
Date:April 1992
Formats:txt pdf
Obsoletes:RFC 1186
Obsoleted by:RFC 6150
Status:HISTORIC
DOI:10.17487/RFC 1320
This document describes the MD4 message-digest algorithm [1]. The algorithm takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. This memo provides information for the Internet community. It does not specify an Internet standard.
 
RFC 1323 TCP Extensions for High Performance
 
Authors:V. Jacobson, R. Braden, D. Borman.
Date:May 1992
Formats:txt pdf
Obsoletes:RFC 1072, RFC 1185
Obsoleted by:RFC 7323
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1323
This memo presents a set of TCP extensions to improve performance over large bandwidth*delay product paths and to provide reliable operation over very high-speed paths. It defines new TCP options for scaled windows and timestamps, which are designed to provide compatible interworking with TCP's that do not implement the extensions. The timestamps are used for two distinct mechanisms:RTTM (Round Trip Time Measurement) and PAWS (Protect Against WrappedSequences). Selective acknowledgments are not included in this memo.

This memo combines and supersedes RFC-1072 and RFC-1185, adding additional clarification and more detailed specification. Appendix C summarizes the changes from the earlier RFCs.

 
RFC 1325 FYI on Questions and Answers Answers to Commonly asked "New Internet User" Questions
 
Authors:G. Malkin, A. Marine.
Date:May 1992
Formats:txt pdf
Obsoletes:RFC 1206
Obsoleted by:RFC 1594
Status:INFORMATIONAL
DOI:10.17487/RFC 1325
This FYI RFC is one of two FYI's called, "Questions and Answers"(Q/A), produced by the User Services Working Group of the InternetEngineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet.
 
RFC 1327 Mapping between X.400(1988) / ISO 10021 and RFC 822
 
Authors:S. Hardcastle-Kille.
Date:May 1992
Formats:txt pdf
Obsoletes:RFC 0987, RFC 1026, RFC 1138, RFC 1148
Obsoleted by:RFC 2156
Updates:RFC 0822
Updated by:RFC 1495
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1327
This document describes a set of mappings which will enable interworking between systems operating the CCITT X.400 1988)Recommendations on Message Handling Systems / ISO IEC 10021 MessageOriented Text Interchange Systems (MOTIS) [CCITT/ISO88a], and systems using the RFC 822 mail protocol [Crocker82a] or protocols derived from RFC 822. The approach aims to maximise the services offered across the boundary, whilst not requiring unduly complex mappings.The mappings should not require any changes to end systems. This document is a revision based on RFCs 987, 1026, 1138, and 1148[Kille86a,Kille87a] which it obsoletes.

This document specifies a mapping between two protocols. This specification should be used when this mapping is performed on theDARPA Internet or in the UK Academic Community. This specification may be modified in the light of implementation experience, but no substantial changes are expected.

 
RFC 1331 The Point-to-Point Protocol (PPP) for the Transmission of Multi-protocol Datagrams over Point-to-Point Links
 
Authors:W. Simpson.
Date:May 1992
Formats:txt pdf
Obsoletes:RFC 1171, RFC 1172
Obsoleted by:RFC 1548
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1331
The Point-to-Point Protocol (PPP) provides a method for transmitting datagrams over serial point-to-point links. PPP is comprised of three main components:

1. A method for encapsulating datagrams over serial links.

2. A Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection.

3. A family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols.

This document defines the PPP encapsulation scheme, together with thePPP Link Control Protocol (LCP), an extensible option negotiation protocol which is able to negotiate a rich assortment of configuration parameters and provides additional management functions.

This RFC is a product of the Point-to-Point Protocol Working Group of the Internet Engineering Task Force (IETF). Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu mailing list.

 
RFC 1333 PPP Link Quality Monitoring
 
Authors:W. Simpson.
Date:May 1992
Formats:txt pdf
Obsoleted by:RFC 1989
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1333
The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, which allows negotiation of a Quality Protocol for continuous monitoring of the viability of the link.

This document defines a protocol for generating Link-Quality-Reports.

This RFC is a product of the Point-to-Point Protocol Working Group of the Internet Engineering Task Force (IETF). Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu mailing list.

 
RFC 1334 PPP Authentication Protocols
 
Authors:B. Lloyd, W. Simpson.
Date:October 1992
Formats:txt pdf
Obsoleted by:RFC 1994
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1334
The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, which allows negotiation of an Authentication Protocol for authenticating its peer before allowing Network Layer protocols to transmit over the link.

This document defines two protocols for Authentication: the PasswordAuthentication Protocol and the Challenge-Handshake AuthenticationProtocol. This memo is the product of the Point-to-Point ProtocolWorking Group of the Internet Engineering Task Force (IETF).Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu mailing list.

 
RFC 1338 Supernetting: an Address Assignment and Aggregation Strategy
 
Authors:V. Fuller, T. Li, J. Yu, K. Varadhan.
Date:June 1992
Formats:txt pdf
Obsoleted by:RFC 1519
Status:INFORMATIONAL
DOI:10.17487/RFC 1338
This memo discusses strategies for address assignment of the existingIP address space with a view to conserve the address space and stem the explosive growth of routing tables in default-route-free routers run by transit routing domain providers.
 
RFC 1340 Assigned Numbers
 
Authors:J. Reynolds, J. Postel.
Date:July 1992
Formats:txt pdf
Obsoletes:RFC 1060
Obsoleted by:RFC 1700
Status:HISTORIC
DOI:10.17487/RFC 1340
This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This memo is a status report on the parameters (i.e., numbers and keywords) used in protocols in the Internet community.
 
RFC 1341 MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies
 
Authors:N. Borenstein, N. Freed.
Date:June 1992
Formats:txt pdf ps
Obsoleted by:RFC 1521
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1341
This document redefines the format of message bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information. [STANDARDS-TRACK]
 
RFC 1342 Representation of Non-ASCII Text in Internet Message Headers
 
Authors:K. Moore.
Date:June 1992
Formats:txt pdf
Obsoleted by:RFC 1522
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1342
This memo describes an extension to the message format defined in [1](known to the IETF Mail Extensions Working Group as "RFC 1341"), to allow the representation of character sets other than ASCII in RFC822 message headers. The extensions described were designed to be highly compatible with existing Internet mail handling software, and to be easily implemented in mail readers that support RFC 1341.
 
RFC 1348 DNS NSAP RRs
 
Authors:B. Manning.
Date:July 1992
Formats:txt pdf
Obsoleted by:RFC 1637
Updates:RFC 1034, RFC 1035
Status:EXPERIMENTAL
DOI:10.17487/RFC 1348
This RFC defines the format of two new Resource Records (RRs) for the Domain Name System (DNS), and reserves corresponding DNS type mnemonic and numerical codes. This memo defines an Experimental Protocol for the Internet community.
 
RFC 1349 Type of Service in the Internet Protocol Suite
 
Authors:P. Almquist.
Date:July 1992
Formats:txt pdf
Obsoleted by:RFC 2474
Updates:RFC 1248, RFC 1247, RFC 1195, RFC 1123, RFC 1122, RFC 1060, RFC 0791
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1349
This memo changes and clarifies some aspects of the semantics of the Type of Service octet in the Internet Protocol (IP) header. [STANDARDS-TRACK]
 
RFC 1354 IP Forwarding Table MIB
 
Authors:F. Baker.
Date:July 1992
Formats:txt pdf
Obsoleted by:RFC 2096
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1354
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing routes in the IPInternet.

It is proposed that the ipRouteTable defined by MIB-II (RFC 1213) be deprecated and replaced with this table. This adds the ability to set or display multi-path routes, and varying routes by network management policy.

 
RFC 1357 A Format for E-mailing Bibliographic Records
 
Authors:D. Cohen.
Date:July 1992
Formats:txt pdf
Obsoleted by:RFC 1807
Status:INFORMATIONAL
DOI:10.17487/RFC 1357
This memo defines a format for E-mailing bibliographic records of technical reports. It is intended to accelerate the dissemination of information about new Computer Science Technical Reports (CS-TR).
 
RFC 1358 Charter of the Internet Architecture Board (IAB)
 
Authors:L. Chapin.
Date:August 1992
Formats:txt pdf
Obsoleted by:RFC 1601
Status:INFORMATIONAL
DOI:10.17487/RFC 1358
The Internet Architecture Board (IAB) shall be constituted and shall operate as a technical advisory group of the Internet Society. This memo provides information for the Internet community. It does not specify an Internet standard.
 
RFC 1360 IAB Official Protocol Standards
 
Authors:J. Postel.
Date:September 1992
Formats:txt pdf
Obsoletes:RFC 1280
Obsoleted by:RFC 1410
Status:HISTORIC
DOI:10.17487/RFC 1360
 
 
RFC 1361 Simple Network Time Protocol (SNTP)
 
Authors:D. Mills.
Date:August 1992
Formats:txt pdf
Obsoleted by:RFC 1769
Also:RFC 1305
Status:INFORMATIONAL
DOI:10.17487/RFC 1361
This memorandum describes the Simple Network Time Protocol (SNTP), which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. SNTP can be used when the ultimate performance of the full NTP implementation described inRFC-1305 is not needed or justified. It involves no change to the current or previous NTP specification versions or known implementations, but rather a clarification of certain design features of NTP which allow operation in a simple, stateless RPC mode with accuracy and reliability expectations similar to the UDP/TIME protocol described in RFC-868.

This memorandum does not obsolete or update any RFC. A working knowledge of RFC-1305 is not required for an implementation of SNTP.

 
RFC 1362 Novell IPX over Various WAN Media (IPXWAN)
 
Authors:M. Allen.
Date:September 1992
Formats:txt pdf
Obsoleted by:RFC 1634
Status:INFORMATIONAL
DOI:10.17487/RFC 1362
This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocolNovell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks.
 
RFC 1364 BGP OSPF Interaction
 
Authors:K. Varadhan.
Date:September 1992
Formats:txt pdf
Obsoleted by:RFC 1403
Also:RFC 1247, RFC 1267
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1364
This memo defines the various criteria to be used when designingAutonomous System Border Routers (ASBR) that will run BGP with otherASBRs external to the AS and OSPF as its IGP.
 
RFC 1366 Guidelines for Management of IP Address Space
 
Authors:E. Gerich.
Date:October 1992
Formats:txt pdf
Obsoleted by:RFC 1466
Status:INFORMATIONAL
DOI:10.17487/RFC 1366
This document has been reviewed by the Federal Engineering Task Force(FEPG) on behalf of the Federal Networking Council (FNC), the co- chairs of the International Engineering Planning Group (IEPG), and the Reseaux IP Europeens (RIPE). There was general consensus by those groups to support the recommendations proposed in this document for management of the IP address space.
 
RFC 1367 Schedule for IP Address Space Management Guidelines
 
Authors:C. Topolcic.
Date:October 1992
Formats:txt pdf
Obsoleted by:RFC 1467
Status:INFORMATIONAL
DOI:10.17487/RFC 1367
This memo suggests a schedule for the implementation of the IP network number allocation plan described in RFC 1366. This memo provides information for the Internet community. It does not specify an Internet standard.
 
RFC 1368 Definition of Managed Objects for IEEE 802.3 Repeater Devices
 
Authors:D. McMaster, K. McCloghrie.
Date:October 1992
Formats:txt pdf
Obsoleted by:RFC 1516
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1368
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing IEEE 802.3 10Mb/second baseband repeaters, sometimes referred to as "hubs."
 
RFC 1374 IP and ARP on HIPPI
 
Authors:J. Renwick, A. Nicholson.
Date:October 1992
Formats:txt pdf
Obsoleted by:RFC 2834
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1374
The ANSI X3T9.3 committee has drafted a proposal for the encapsulation of IEEE 802.2 LLC PDUs and, by implication, IP onHIPPI. Another X3T9.3 draft describes the operation of HIPPI physical switches. X3T9.3 chose to leave HIPPI networking issues largely outside the scope of their standards; this document discusses methods of using of ANSI standard HIPPI hardware and protocols in the context of the Internet, including the use of HIPPI switches as LANs and interoperation with other networks.
 
RFC 1376 The PPP DECnet Phase IV Control Protocol (DNCP)
 
Authors:S. Senum.
Date:November 1992
Formats:txt pdf
Obsoleted by:RFC 1762
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1376
The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols.

This document defines the NCP for establishing and configuringDigital's DNA Phase IV Routing protocol (DECnet Phase IV) over PPP.This document applies only to DNA Phase IV Routing messages (both data and control), and not to other DNA Phase IV protocols (MOP, LAT, etc.).

 
RFC 1379 Extending TCP for Transactions -- Concepts
 
Authors:R. Braden.
Date:November 1992
Formats:txt pdf
Obsoleted by:RFC 6247
Updated by:RFC 1644
Status:HISTORIC
DOI:10.17487/RFC 1379
This memo discusses extension of TCP to provide transaction-oriented service, without altering its virtual-circuit operation. This extension would fill the large gap between connection-oriented TCP and datagram-based UDP, allowing TCP to efficiently perform many applications for which UDP is currently used. A separate memo contains a detailed functional specification for this proposed extension.

This work was supported in part by the National Science Foundation under Grant Number NCR-8922231.

 
RFC 1384 Naming Guidelines for Directory Pilots
 
Authors:P. Barker, S.E. Hardcastle-Kille.
Date:January 1993
Formats:txt ps pdf
Obsoleted by:RFC 1617, RTR_0011
Status:INFORMATIONAL
DOI:10.17487/RFC 1384
Deployment of a Directory will benefit from following certain guidelines. This document defines a number of naming guidelines.Alignment to these guidelines is recommended for directory pilots.
 
RFC 1385 EIP: The Extended Internet Protocol
 
Authors:Z. Wang.
Date:November 1992
Formats:txt pdf
Obsoleted by:RFC 6814
Status:HISTORIC
DOI:10.17487/RFC 1385
EIP can substantially reduce the amount of modifications needed to the current Internet systems and greatly ease the difficulties of transition. This is an "idea" paper and discussion is strongly encouraged on Big-Internet@munnari.oz.au. This memo provides information for the Internet community. It does not specify an Internet standard.
 
RFC 1386 The US Domain
 
Authors:A. Cooper, J. Postel.
Date:December 1992
Formats:txt pdf
Obsoleted by:RFC 1480
Status:INFORMATIONAL
DOI:10.17487/RFC 1386
This is a description of the US Top Level Domains on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.
 
RFC 1387 RIP Version 2 Protocol Analysis
 
Authors:G. Malkin.
Date:January 1993
Formats:txt pdf
Obsoleted by:RFC 1721
Status:INFORMATIONAL
DOI:10.17487/RFC 1387
As required by Routing Protocol Criteria (RFC 1264), this report documents the key features of the RIP-2 protocol and the current implementation experience.
 
RFC 1388 RIP Version 2 Carrying Additional Information
 
Authors:G. Malkin.
Date:January 1993
Formats:txt pdf
Obsoleted by:RFC 1723
Updates:RFC 1058
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1388
This document specifies an extension of the Routing InformationProtocol (RIP), as defined in [1], to expand the amount of useful information carried in RIP packets and to add a measure of security.A companion document will define the SNMP MIB objects for RIP-2 [2].
 
RFC 1389 RIP Version 2 MIB Extensions
 
Authors:G. Malkin, F. Baker.
Date:January 1993
Formats:txt pdf
Obsoleted by:RFC 1724
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1389
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing RIP Version 2.
 
RFC 1391 The Tao of the IETF: A Guide for New Attendees of the Internet Engineering Task Force
 
Authors:G. Malkin.
Date:January 1993
Formats:txt pdf
Obsoleted by:RFC 1539
Status:INFORMATIONAL
DOI:10.17487/RFC 1391
Over the last two years, the attendance at Internet Engineering TaskForce (IETF) Plenary meetings has grown phenomenally. Approximately38% of the attendees are new to the IETF at each meeting. About 33% of those go on to become regular attendees. When the meetings were smaller, it wasn't very difficult for a newcomer to get to know people and get into the swing of things. Today, however, a newcomer meets many more new people, some previously known only as the authors of Request For Comments (RFC) documents or thought provoking email messages.

The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This will give them a warm, fuzzy feeling and enable them to make the meeting more productive for everyone. This FYI will also provide the mundane bits of information which everyone who attends an IETF meeting should know.

 
RFC 1392 Internet Users' Glossary
 
Authors:G. Malkin, T. LaQuey Parker.
Date:January 1993
Formats:txt pdf
Obsoleted by:RFC 1983
Status:INFORMATIONAL
DOI:10.17487/RFC 1392
There are many networking glossaries in existence. This glossary concentrates on terms which are specific to the Internet. Naturally, there are entries for some basic terms and acronyms because other entries refer to them.
 
RFC 1393 Traceroute Using an IP Option
 
Authors:G. Malkin.
Date:January 1993
Formats:txt pdf
Obsoleted by:RFC 6814
Status:HISTORIC
DOI:10.17487/RFC 1393
Traceroute serves as a valuable network debugging tool. The way in which it is currently implemented has the advantage of being automatically supported by all of the routers. It's two problems are the number of packets it generates and the amount of time it takes to run.

This document specifies a new IP option and ICMP message type which duplicates the functionality of the existing traceroute method while generating fewer packets and completing in a shorter time.

 
RFC 1395 BOOTP Vendor Information Extensions
 
Authors:J. Reynolds.
Date:January 1993
Formats:txt pdf
Obsoletes:RFC 1084, RFC 1048
Obsoleted by:RFC 1497, RFC 1533
Updates:RFC 0951
Status:DRAFT STANDARD
DOI:10.17487/RFC 1395
This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo. This memo will be updated as additional tags are defined. This edition introduces Tag 14 for Merit Dump File, Tag 15 for Domain Name, Tag 16 for Swap Server and Tag 17 for Root Path. This memo is a status report on the vendor information extensions used int the Bootstrap Protocol (BOOTP).
 
RFC 1398 Definitions of Managed Objects for the Ethernet-Like Interface Types
 
Authors:F. Kastenholz.
Date:January 1993
Formats:txt pdf
Obsoletes:RFC 1284
Obsoleted by:RFC 1623
Status:DRAFT STANDARD
DOI:10.17487/RFC 1398
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing ethernet-like objects.
 
RFC 1404 A Model for Common Operational Statistics
 
Authors:B. Stockman.
Date:January 1993
Formats:txt pdf
Obsoleted by:RFC 1857
Status:INFORMATIONAL
DOI:10.17487/RFC 1404
This memo describes a model for operational statistics in theInternet. It gives recommendations for metrics, measurements, polling periods, storage formats and presentation formats.
 
RFC 1405 Mapping between X.400(1984/1988) and Mail-11 (DECnet mail)
 
Authors:C. Allocchio.
Date:January 1993
Formats:txt pdf
Obsoleted by:RFC 2162
Status:EXPERIMENTAL
DOI:10.17487/RFC 1405
This document describes a set of mappings which will enable inter working between systems operating the CCITT X.400 ( 1984 / 1988 )Recommendations on Message Handling Systems, and systems running theMail-11 (also known as DECnet mail) protocol. The specifications are valid within DECnet Phase IV addressing and routing scheme.

The complete scenario of X.400 / RFC822 / Mail-11 is also considered, in order to cover the possible complex cases arising in multiple gateway translations.

This document covers mainly the O/R address to DECnet from/to address mapping (and vice versa); other mappings are based on RFC 1327 and its eventual future updates.

This is a combined effort of COSINE S2.2, the RARE MSG Working Group, and the IETF X.400 Ops Working Group.

 
RFC 1406 Definitions of Managed Objects for the DS1 and E1 Interface Types
 
Authors:F. Baker, Ed., J. Watt, Ed..
Date:January 1993
Formats:txt pdf
Obsoletes:RFC 1232
Obsoleted by:RFC 2495
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1406
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing DS1 Interfaces -- including both T1 and E1 (a.k.a., CEPT 2 Mbit/s) links.

This document entirely replaces RFC 1232, which contains a fundamental error: many objects are encoded as Counters that must be encoded as INTEGERs or Gauges. The magnitude of the change required is sufficient that virtually every object changed. Therefore, theMIB documented in RFC 1232 should not be implemented.

 
RFC 1407 Definitions of Managed Objects for the DS3/E3 Interface Type
 
Authors:T. Cox, K. Tesink.
Date:January 1993
Formats:txt pdf
Obsoletes:RFC 1233
Obsoleted by:RFC 2496
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1407
This memo defines an extension to the Management Information Base(MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing DS3 and E3Interfaces. This document is a companion document with Definitions of Managed Objects for the DS1 Interface Type.

This document entirely replaces RFC 1233, which contains a fundamental error: many objects are encoded as Counters that must be encoded as INTEGERs or Gauges. The magnitude of the change required is sufficient that virtually every object changed. Therefore, theMIB documented in RFC 1233 should not be implemented.

 
RFC 1409 Telnet Authentication Option
 
Authors:D. Borman, Ed..
Date:January 1993
Formats:txt pdf
Obsoleted by:RFC 1416
Status:EXPERIMENTAL
DOI:10.17487/RFC 1409
This memo defines an Experimental Protocol for the Internet community.
 
RFC 1410 IAB Official Protocol Standards
 
Authors:J. Postel, Ed..
Date:March 1993
Formats:txt pdf
Obsoletes:RFC 1360
Obsoleted by:RFC 1500
Status:HISTORIC
DOI:10.17487/RFC 1410
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB).
 
RFC 1416 Telnet Authentication Option
 
Authors:D. Borman, Ed..
Date:February 1993
Formats:txt pdf
Obsoletes:RFC 1409
Obsoleted by:RFC 2941
Status:EXPERIMENTAL
DOI:10.17487/RFC 1416
This RFC 1416 replaces RFC 1409, which has an important typographical error in the example on page 6 (one occurance of "REPLY" should be "IS"). This memo defines an Experimental Protocol for the Internet community.
 
RFC 1417 NADF Standing Documents: A Brief Overview
 
Authors:The North American Directory Forum.
Date:February 1993
Formats:txt pdf
Obsoletes:RFC 1295, RFC 1255, RFC 1218
Obsoleted by:RFC 1758
Status:INFORMATIONAL
DOI:10.17487/RFC 1417
The purpose of this document is to provide a brief overview of the NADF's Standing Document series. This memo provides information for the Internet community. It does not specify an Internet standard.
 
RFC 1425 SMTP Service Extensions
 
Authors:J. Klensin, N. Freed, Ed., M. Rose, E. Stefferud, D. Crocker.
Date:February 1993
Formats:txt pdf
Obsoleted by:RFC 1651
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1425
This memo defines a framework for extending the SMTP service by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports. [STANDARDS-TRACK]
 
RFC 1426 SMTP Service Extension for 8bit-MIMEtransport
 
Authors:J. Klensin, N. Freed, Ed., M. Rose, E. Stefferud, D. Crocker.
Date:February 1993
Formats:txt pdf
Obsoleted by:RFC 1652
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1426
This memo defines an extension to the SMTP service whereby an SMTP content body containing octets outside of the US ASCII octet range (hex
 
RFC 1427 SMTP Service Extension for Message Size Declaration
 
Authors:J. Klensin, N. Freed, Ed., K. Moore.
Date:February 1993
Formats:txt pdf
Obsoleted by:RFC 1653
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1427
This memo defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to decline to accept a message (perhaps temporarily) based on the client's estimate of the message size. [STANDARDS-TRACK]
 
RFC 1434 Data Link Switching: Switch-to-Switch Protocol
 
Authors:R. Dixon, D. Kushi.
Date:March 1993
Formats:txt ps pdf
Obsoleted by:RFC 1795
Status:INFORMATIONAL
DOI:10.17487/RFC 1434
This RFC describes IBM's support of Data Link Switching over TCP/IP.The RFC is being distributed to members of the Internet community in order to solicit their reactions to the proposals contained in it.While the issues discussed may not be directly relevant to the research problems of the Internet, they may be interesting to a number of researchers and implementors.

Any questions or comments relative to the contents of this RFC should be sent to the following Internet address: dlsw@ralvma.vnet.ibm.com.

 
RFC 1442 Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)
 
Authors:J. Case, K. McCloghrie, M. Rose, S. Waldbusser.
Date:April 1993
Formats:txt pdf
Obsoleted by:RFC 1902
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1442
Management information is viewed as a collection of managed objects, residing in a virtual information store, termed the Management Information Base (MIB). Collections of related objects are defined in MIB modules. These modules are written using a subset of OSI's Abstract Syntax Notation One (ASN.1) [1]. It is the purpose of this document, the Structure of Management Information (SMI), to define that subset. [STANDARDS-TRACK]
 
RFC 1443 Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2)
 
Authors:J. Case, K. McCloghrie, M. Rose, S. Waldbusser.
Date:April 1993
Formats:txt pdf
Obsoleted by:RFC 1903
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1443
It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK]
 
RFC 1444 Conformance Statements for version 2 of the Simple Network Management Protocol (SNMPv2)
 
Authors:J. Case, K. McCloghrie, M. Rose, S. Waldbusser.
Date:April 1993
Formats:txt pdf
Obsoleted by:RFC 1904
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1444
It may be useful to define the acceptable lower-bounds of implementation, along with the actual level of implementation achieved. It is the purpose of this document to define the notation used for these purposes. [STANDARDS-TRACK]
 
RFC 1448 Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)
 
Authors:J. Case, K. McCloghrie, M. Rose, S. Waldbusser.
Date:April 1993
Formats:txt pdf
Obsoleted by:RFC 1905
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1448
It is the purpose of this document, Protocol Operations for SNMPv2, to define the operations of the protocol with respect to the sending and receiving of the PDUs. [STANDARDS-TRACK]
 
RFC 1449 Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2)
 
Authors:J. Case, K. McCloghrie, M. Rose, S. Waldbusser.
Date:April 1993
Formats:txt pdf
Obsoleted by:RFC 1906
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1449
It is the purpose of this document to define how the SNMPv2 maps onto an initial set of transport domains. [STANDARDS-TRACK]
 
RFC 1450 Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)
 
Authors:J. Case, K. McCloghrie, M. Rose, S. Waldbusser.
Date:April 1993
Formats:txt pdf
Obsoleted by:RFC 1907
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1450
It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity. [STANDARDS-TRACK]
 
RFC 1452 Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework
 
Authors:J. Case, K. McCloghrie, M. Rose, S. Waldbusser.
Date:April 1993
Formats:txt pdf
Obsoleted by:RFC 1908
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1452
The purpose of this document is to describe coexistence between version 2 of the Internet-standard Network Management Framework, termed the SNMP version 2 framework (SNMPv2) [1], and the original Internet-standard Network Management Framework (SNMPv1). [STANDARDS-TRACK]
 
RFC 1455 Physical Link Security Type of Service
 
Authors:D. Eastlake 3rd.
Date:May 1993
Formats:txt pdf
Obsoleted by:RFC 2474
Status:EXPERIMENTAL
DOI:10.17487/RFC 1455
This RFC documents an experimental protocol providing a Type ofService (TOS) to request maximum physical link security. This is an addition to the types of service enumerated in RFC 1349: Type ofService in the Internet Protocol Suite. The new TOS requests the network to provide what protection it can against surreptitious observation by outside agents of traffic so labeled. The purpose is protection against traffic analysis and as an additional possible level of data confidentiality. This TOS is consistent with all other defined types of service for IP version 4 in that it is based on link level characteristics and will not provide any particular guaranteed level of service.
 
RFC 1460 Post Office Protocol - Version 3
 
Authors:M. Rose.
Date:June 1993
Formats:txt pdf
Obsoletes:RFC 1225
Obsoleted by:RFC 1725
Status:DRAFT STANDARD
DOI:10.17487/RFC 1460
This memo is a revision to RFC 1225, a Draft Standard. [STANDARDS- TRACK]
 
RFC 1466 Guidelines for Management of IP Address Space
 
Authors:E. Gerich.
Date:May 1993
Formats:txt pdf
Obsoletes:RFC 1366
Obsoleted by:RFC 2050
Status:INFORMATIONAL
DOI:10.17487/RFC 1466
This document has been reviewed by the Federal Engineering PlanningGroup (FEPG) on behalf of the Federal Networking Council (FNC), the co-chairs of the Intercontinental Engineering Planning Group (IEPG), and the Reseaux IP Europeens (RIPE). There was general consensus by those groups to support the recommendations proposed in this document for management of the IP address space.
 
RFC 1475 TP/IX: The Next Internet
 
Authors:R. Ullmann.
Date:June 1993
Formats:txt pdf
Obsoleted by:RFC 6814
Status:HISTORIC
DOI:10.17487/RFC 1475
The first version of this memo, describing a possible next generation of Internet protocols, was written by the present author in the summer and fall of 1989, and circulated informally, including to theIESG, in December 1989. A further informal note on the addressing, called "Toasternet Part II", was circulated on the IETF mail list during March of 1992.
 
RFC 1483 Multiprotocol Encapsulation over ATM Adaptation Layer 5
 
Authors:Juha Heinanen.
Date:July 1993
Formats:txt pdf
Obsoleted by:RFC 2684
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1483
This memo describes two encapsulations methods for carrying network interconnect traffic over ATM AAL5. The first method allows multiplexing of multiple protocols over a single ATM virtual circuit whereas the second method assumes that each protocol is carried over a separate ATM virtual circuit.
 
RFC 1484 Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2))
 
Authors:S. Hardcastle-Kille.
Date:July 1993
Formats:txt pdf
Obsoleted by:RFC 1781, RFC 3494
Status:HISTORIC
DOI:10.17487/RFC 1484
The OSI Directory has user friendly naming as a goal. A simple minded usage of the directory does not achieve this. Two aspects not achieved are: o A user oriented notation o Guessability

This proposal sets out some conventions for representing names in a friendly manner, and shows how this can be used to achieve really friendly naming. This then leads to a specification of a format for representing names, and to procedures to resolve them. This leads to a specification which allows directory names to be communicated between humans. The format in this specification is identical to that defined in [HK93], and it is intended that these specifications are compatible. Please send comments to the author or to the discussion group: <osi-ds@CS.UCL.AC.UK&rt;.

 
RFC 1485 A String Representation of Distinguished Names (OSI-DS 23 (v5))
 
Authors:S. Hardcastle-Kille.
Date:July 1993
Formats:txt pdf
Obsoleted by:RFC 1779, RFC 3494
Status:HISTORIC
DOI:10.17487/RFC 1485
The OSI Directory uses distinguished names as the primary keys to entries in the directory. Distinguished Names are encoded in ASN.1.When a distinguished name is communicated between to users not using a directory protocol (e.g., in a mail message), there is a need to have a user-oriented string representation of distinguished name. This specification defines a string format for representing names, which is designed to give a clean representation of commonly used names, whilst being able to represent any distinguished name. Please send comments to the author or to the discussion group <osi-ds@CS.UCL.AC.UK&rt;.
 
RFC 1486 An Experiment in Remote Printing
 
Authors:M. Rose, C. Malamud.
Date:July 1993
Formats:txt pdf
Obsoleted by:RFC 1528, RFC 1529
Status:EXPERIMENTAL
DOI:10.17487/RFC 1486
This memo describes a technique for "remote printing" using the Internet mail infrastructure. In particular, this memo focuses on the case in which remote printers are connected to the international telephone network. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.
 
RFC 1487 X.500 Lightweight Directory Access Protocol
 
Authors:W. Yeong, T. Howes, S. Kille.
Date:July 1993
Formats:txt pdf
Obsoleted by:RFC 1777, RFC 3494
Status:HISTORIC
DOI:10.17487/RFC 1487
The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of theDirectory Access Protocol (DAP). This protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive access to the Directory, and is intended to be a complement to the DAP itself.

Key aspects of LDAP are:

- Protocol elements are carried directly over TCP or other transport, bypassing much of the session/presentation overhead.

- Many protocol data elements are encoding as ordinary strings (e.g.,Distinguished Names).

- A lightweight BER encoding is used to encode all protocol elements.

 
RFC 1488 The X.500 String Representation of Standard Attribute Syntaxes
 
Authors:T. Howes, S. Kille, W. Yeong, C. Robbins.
Date:July 1993
Formats:txt pdf
Obsoleted by:RFC 1778
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1488
The Lightweight Directory Access Protocol (LDAP) [9] requires that the contents of AttributeValue fields in protocol elements be octet strings. This document defines the requirements that must be satisfied by encoding rules used to render Directory attribute syntaxes into a form suitable for use in the LDAP, then goes on to define the encoding rules for the standard set of attribute syntaxes defined in [1,2] and [3].
 
RFC 1490 Multiprotocol Interconnect over Frame Relay
 
Authors:T. Bradley, C. Brown, A. Malis.
Date:July 1993
Formats:txt pdf
Obsoletes:RFC 1294
Obsoleted by:RFC 2427
Status:DRAFT STANDARD
DOI:10.17487/RFC 1490
This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. Additionally, it describes a simple fragmentation procedure for carrying large frames over a frame relay network with a smaller MTU.

Systems with the ability to transfer both the encapsulation method described in this document, and others must have a priori knowledge of which virtual circuits will carry which encapsulation method and this encapsulation must only be used over virtual circuits that have been explicitly configured for its use.

 
RFC 1493 Definitions of Managed Objects for Bridges
 
Authors:E. Decker, P. Langille, A. Rijsinghani, K. McCloghrie.
Date:July 1993
Formats:txt pdf
Obsoletes:RFC 1286
Obsoleted by:RFC 4188
Status:DRAFT STANDARD
DOI:10.17487/RFC 1493
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets.In particular it defines objects for managing MAC bridges based on the IEEE 802.1D-1990 standard between Local Area Network (LAN) segments. Provisions are made for support of transparent bridging.Provisions are also made so that these objects apply to bridges connected by subnetworks other than LAN segments.
 
RFC 1495 Mapping between X.400 and RFC-822 Message Bodies
 
Authors:H. Alvestrand, S. Kille, R. Miles, M. Rose, S. Thompson.
Date:August 1993
Formats:txt pdf
Obsoleted by:RFC 2156
Updates:RFC 1327
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1495
Since the introduction of X.400(84), there has been work ongoing for defining mappings between MHS and RFC-822. The most recent work in this area is RFC-1327 [3], which focuses primarily on translation of envelope and headers. This document is complimentary to RFC-1327 as it focuses on translation of the message body. [STANDARDS-TRACK]
 
RFC 1497 BOOTP Vendor Information Extensions
 
Authors:J. Reynolds.
Date:August 1993
Formats:txt pdf
Obsoletes:RFC 1395, RFC 1084, RFC 1048
Obsoleted by:RFC 1533
Updates:RFC 0951
Status:DRAFT STANDARD
DOI:10.17487/RFC 1497
This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo. This memo is a status report on the vendor information extensions used in the Bootstrap Protocol (BOOTP).
 
RFC 1500 Internet Official Protocol Standards
 
Authors:J. Postel.
Date:August 1993
Formats:txt pdf
Obsoletes:RFC 1410
Obsoleted by:RFC 1540
Status:HISTORIC
DOI:10.17487/RFC 1500
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). [STANDARDS-TRACK]
 
RFC 1508 Generic Security Service Application Program Interface
 
Authors:J. Linn.
Date:September 1993
Formats:txt pdf
Obsoleted by:RFC 2078
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1508
This Generic Security Service Application Program Interface (GSS-API) definition provides security services to callers in a generic fashion, supportable with a range of underlying mechanisms and technologies and hence allowing source-level portability of applications to different environments. This specification definesGSS-API services and primitives at a level independent of underlying mechanism and programming language environment, and is to be complemented by other, related specifications: documents defining specific parameter bindings for particular language environments documents defining token formats, protocols, and procedures to be implemented in order to realize GSS-API services atop particular security mechanisms
 
RFC 1509 Generic Security Service API : C-bindings
 
Authors:J. Wray.
Date:September 1993
Formats:txt pdf
Obsoleted by:RFC 2744
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1509
This document specifies C language bindings for the Generic SecurityService Application Program Interface (GSS-API), which is described at a language-independent conceptual level in other documents.

The Generic Security Service Application Programming Interface (GSS-API) provides security services to its callers, and is intended for implementation atop alternative underlying cryptographic mechanisms.Typically, GSS-API callers will be application protocols into which security enhancements are integrated through invocation of services provided by the GSS-API. The GSS-API allows a caller application to authenticate a principal identity associated with a peer application, to delegate rights to a peer, and to apply security services such as confidentiality and integrity on a per-message basis.

 
RFC 1510 The Kerberos Network Authentication Service (V5)
 
Authors:J. Kohl, C. Neuman.
Date:September 1993
Formats:txt pdf
Obsoleted by:RFC 4120, RFC 6649
Status:HISTORIC
DOI:10.17487/RFC 1510
This document gives an overview and specification of Version 5 of the protocol for the Kerberos network authentication system. Version 4, described elsewhere [1,2], is presently in production use at MIT'sProject Athena, and at other Internet sites.
 
RFC 1514 Host Resources MIB
 
Authors:P. Grillo, S. Waldbusser.
Date:September 1993
Formats:txt pdf
Obsoleted by:RFC 2790
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1514
This memo defines a MIB for use with managing host systems. The term"host" is construed to mean any computer that communicates with other similar computers attached to the internet and that is directly used by one or more human beings. Although this MIB does not necessarily apply to devices whose primary function is communications services(e.g., terminal servers, routers, bridges, monitoring equipment), such relevance is not explicitly precluded. This MIB instruments attributes common to all internet hosts including, for example, both personal computers and systems that run variants of Unix.
 
RFC 1515 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
 
Authors:D. McMaster, K. McCloghrie, S. Roberts.
Date:September 1993
Formats:txt pdf
Obsoleted by:RFC 3636
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1515
This document defines a portion of the Management Information Base(MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing IEEE 802.3Medium Attachment Units (MAUs).
 
RFC 1516 Definitions of Managed Objects for IEEE 802.3 Repeater Devices
 
Authors:D. McMaster, K. McCloghrie.
Date:September 1993
Formats:txt pdf
Obsoletes:RFC 1368
Obsoleted by:RFC 2108
Status:DRAFT STANDARD
DOI:10.17487/RFC 1516
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community.In particular, it defines objects for managing IEEE 802.3 10Mb/second baseband repeaters, sometimes referred to as "hubs."
 
RFC 1519 Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy
 
Authors:V. Fuller, T. Li, J. Yu, K. Varadhan.
Date:September 1993
Formats:txt pdf
Obsoletes:RFC 1338
Obsoleted by:RFC 4632
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1519
This memo discusses strategies for address assignment of the existingIP address space with a view to conserve the address space and stem the explosive growth of routing tables in default-route-free routers.
 
RFC 1521 MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies
 
Authors:N. Borenstein, N. Freed.
Date:September 1993
Formats:txt pdf ps
Obsoletes:RFC 1341
Obsoleted by:RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049
Updated by:RFC 1590
Status:DRAFT STANDARD
DOI:10.17487/RFC 1521
STD 11, RFC 822 defines a message representation protocol which specifies considerable detail about message headers, but which leaves the message content, or message body, as flat ASCII text. This document redefines the format of message bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information. This is based on earlier work documented in RFC 934 and STD 11, RFC 1049, but extends and revises that work. Because RFC 822 said so little about message bodies, this document is largely orthogonal to (rather than a revision of) RFC822.

In particular, this document is designed to provide facilities to include multiple objects in a single message, to represent body text in character sets other than US-ASCII, to represent formatted multi- font text messages, to represent non-textual material such as images and audio fragments, and generally to facilitate later extensions defining new types of Internet mail for use by cooperating mail agents.

This document does NOT extend Internet mail header fields to permit anything other than US-ASCII text data. Such extensions are the subject of a companion document [RFC-1522].

This document is a revision of RFC 1341. Significant differences from RFC 1341 are summarized in Appendix H.

 
RFC 1522 MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text
 
Authors:K. Moore.
Date:September 1993
Formats:txt pdf
Obsoletes:RFC 1342
Obsoleted by:RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049
Status:DRAFT STANDARD
DOI:10.17487/RFC 1522
This memo describes an extension to the message format defined in RFC1521 [1], to allow the representation of character sets other thanASCII in RFC 822 (STD 11) message headers. The extensions described were designed to be highly compatible with existing Internet mail handling software, and to be easily implemented in mail readers that support RFC 1521.
 
RFC 1523 The text/enriched MIME Content-type
 
Authors:N. Borenstein.
Date:September 1993
Formats:txt pdf
Obsoleted by:RFC 1563, RFC 1896
Status:INFORMATIONAL
DOI:10.17487/RFC 1523
MIME [RFC-1341, RFC-1521] defines a format and general framework for the representation of a wide variety of data types in Internet mail.This document defines one particular type of MIME data, the text/enriched type, a refinement of the "text/richtext" type defined in RFC 1341. The text/enriched MIME type is intended to facilitate the wider interoperation of simple enriched text across a wide variety of hardware and software platforms.
 
RFC 1531 Dynamic Host Configuration Protocol
 
Authors:R. Droms.
Date:October 1993
Formats:txt pdf
Obsoleted by:RFC 1541
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1531
The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network.DHCP is based on the Bootstrap Protocol (BOOTP) [7], adding the capability of automatic allocation of reusable network addresses and additional configuration options [19]. DHCP captures the behavior ofBOOTP relay agents [7, 23], and DHCP participants can interoperate with BOOTP participants [9].
 
RFC 1532 Clarifications and Extensions for the Bootstrap Protocol
 
Authors:W. Wimer.
Date:October 1993
Formats:txt pdf
Obsoleted by:RFC 1542
Updates:RFC 0951
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1532
Some aspects of the BOOTP protocol were rather loosely defined in its original specification. In particular, only a general description was provided for the behavior of "BOOTP relay agents" (originally called BOOTP forwarding agents"). The client behavior description also suffered in certain ways. This memo attempts to clarify and strengthen the specification in these areas.

In addition, new issues have arisen since the original specification was written. This memo also attempts to address some of these.

 
RFC 1533 DHCP Options and BOOTP Vendor Extensions
 
Authors:S. Alexander, R. Droms.
Date:October 1993
Formats:txt pdf
Obsoletes:RFC 1497, RFC 1395, RFC 1084, RFC 1048
Obsoleted by:RFC 2132
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1533
The Dynamic Host Configuration Protocol (DHCP) [1] provides a framework for passing configuration information to hosts on a TCP/IP network. Configuration parameters and other control information are carried in tagged data items that are stored in the "options" field of the DHCP message. The data items themselves are also called"options."

This document specifies the current set of DHCP options. This document will be periodically updated as new options are defined.Each superseding document will include the entire current list of valid options.

All of the vendor information extensions defined in RFC 1497 [2] may be used as DHCP options. The definitions given in RFC 1497 are included in this document, which supersedes RFC 1497. All of theDHCP options defined in this document, except for those specific toDHCP as defined in section 9, may be used as BOOTP vendor information extensions.

 
RFC 1537 Common DNS Data File Configuration Errors
 
Authors:P. Beertema.
Date:October 1993
Formats:txt pdf
Obsoleted by:RFC 1912
Status:INFORMATIONAL
DOI:10.17487/RFC 1537
This memo describes errors often found in DNS data files. It points out common mistakes system administrators tend to make and why they often go unnoticed for long periods of time.
 
RFC 1539 The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force
 
Authors:G. Malkin.
Date:October 1993
Formats:txt pdf
Obsoletes:RFC 1391
Obsoleted by:RFC 1718
Status:INFORMATIONAL
DOI:10.17487/RFC 1539
Over the last two years, the attendance at Internet Engineering TaskForce (IETF) Plenary meetings has grown phenomenally. Approximately38% of the attendees are new to the IETF at each meeting. About 33% of those go on to become regular attendees. When the meetings were smaller, it wasn't very difficult for a newcomer to get to know people and get into the swing of things. Today, however, a newcomer meets many more new people, some previously known only as the authors of Request For Comments (RFC) documents or thought provoking email messages.

The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This will give them a warm, fuzzy feeling and enable them to make the meeting more productive for everyone. This FYI will also provide the mundane bits of information which everyone who attends an IETF meeting should know.

 
RFC 1540 Internet Official Protocol Standards
 
Authors:J. Postel.
Date:October 1993
Formats:txt pdf
Obsoletes:RFC 1500
Obsoleted by:RFC 1600
Status:HISTORIC
DOI:10.17487/RFC 1540
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). [STANDARDS-TRACK]
 
RFC 1541 Dynamic Host Configuration Protocol
 
Authors:R. Droms.
Date:October 1993
Formats:txt pdf
Obsoletes:RFC 1531
Obsoleted by:RFC 2131
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1541
The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network.DHCP is based on the Bootstrap Protocol (BOOTP) [7], adding the capability of automatic allocation of reusable network addresses and additional configuration options [19]. DHCP captures the behavior ofBOOTP relay agents [7, 23], and DHCP participants can interoperate with BOOTP participants [9]. Due to some errors introduced into RFC1531 in the editorial process, this memo is reissued as RFC 1541.
 
RFC 1543 Instructions to RFC Authors
 
Authors:J. Postel.
Date:October 1993
Formats:txt pdf
Obsoletes:RFC 1111, RFC 0825
Obsoleted by:RFC 2223
Status:INFORMATIONAL
DOI:10.17487/RFC 1543
This Request for Comments (RFC) provides information about the preparation of RFCs, and certain policies relating to the publication of RFCs. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
 
RFC 1544 The Content-MD5 Header Field
 
Authors:M. Rose.
Date:November 1993
Formats:txt pdf
Obsoleted by:RFC 1864
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1544
This memo specifies an optional header field, Content-MD5, for use with MIME-conformant messages.
 
RFC 1545 FTP Operation Over Big Address Records (FOOBAR)
 
Authors:D. Piscitello.
Date:November 1993
Formats:txt pdf
Obsoleted by:RFC 1639
Status:EXPERIMENTAL
DOI:10.17487/RFC 1545
This paper describes a convention for specifying longer addresses in the PORT command.
 
RFC 1548 The Point-to-Point Protocol (PPP)
 
Authors:W. Simpson.
Date:December 1993
Formats:txt pdf
Obsoletes:RFC 1331
Obsoleted by:RFC 1661
Updated by:RFC 1570
Status:DRAFT STANDARD
DOI:10.17487/RFC 1548
The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP is comprised of three main components:

1. A method for encapsulating multi-protocol datagrams.

2. A Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection.

3. A family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols.

This document defines the PPP organization and methodology, and thePPP encapsulation, together with an extensible option negotiation mechanism which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. The PPP Link Control Protocol (LCP) is described in terms of this mechanism.

This document is the product of the Point-to-Point Protocol WorkingGroup of the Internet Engineering Task Force (IETF). Comments should be submitted to the ietf-ppp@ucdavis.edu mailing list.

 
RFC 1549 PPP in HDLC Framing
 
Authors:W. Simpson, Ed..
Date:December 1993
Formats:txt pdf
Obsoleted by:RFC 1662
Status:DRAFT STANDARD
DOI:10.17487/RFC 1549
The Point-to-Point Protocol (PPP) [1] provides a standard method for transporting multi-protocol datagrams over point-to-point links.

This document describes the use of HDLC for framing PPP encapsulated packets. This document is the product of the Point-to-Point ProtocolWorking Group of the Internet Engineering Task Force (IETF).Comments should be submitted to the ietf-ppp@ucdavis.edu mailing list.

 
RFC 1551 Novell IPX Over Various WAN Media (IPXWAN)
 
Authors:M. Allen.
Date:December 1993
Formats:txt pdf
Obsoleted by:RFC 1634
Status:INFORMATIONAL
DOI:10.17487/RFC 1551
This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocolNovell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This document supercedes RFC 1362 and adds capability forUnnumbered RIP links, On-demand statically routed links and client to router connectivity.
 
RFC 1558 A String Representation of LDAP Search Filters
 
Authors:T. Howes.
Date:December 1993
Formats:txt pdf
Obsoleted by:RFC 1960
Status:INFORMATIONAL
DOI:10.17487/RFC 1558
The Lightweight Directory Access Protocol (LDAP) [1] defines a network representation of a search filter transmitted to an LDAP server. Some applications may find it useful to have a common way of representing these search filters in a human-readable form. This document defines a human-readable string format for representing LDAP search filters.
 
RFC 1563 The text/enriched MIME Content-type
 
Authors:N. Borenstein.
Date:January 1994
Formats:txt ps pdf
Obsoletes:RFC 1523
Obsoleted by:RFC 1896
Status:INFORMATIONAL
DOI:10.17487/RFC 1563
MIME [RFC-1341, RFC-1521] defines a format and general framework for the representation of a wide variety of data types in Internet mail.This document defines one particular type of MIME data, the text/enriched type, a refinement of the "text/richtext" type defined in RFC 1341. The text/enriched MIME type is intended to facilitate the wider interoperation of simple enriched text across a wide variety of hardware and software platforms.
 
RFC 1565 Network Services Monitoring MIB
 
Authors:S. Kille, N. Freed.
Date:January 1994
Formats:txt pdf
Obsoleted by:RFC 2248
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1565
This document defines a MIB which contains the elements common to the monitoring of any network service application. This information includes a table of all monitorable network service applications, a count of the associations (connections) to each application, and basic information about the parameters and status of each application-related association. [STANDARDS-TRACK]
 
RFC 1566 Mail Monitoring MIB
 
Authors:S. Kille, N. Freed.
Date:January 1994
Formats:txt pdf
Obsoleted by:RFC 2249, RFC 2789
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1566
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, this memo extends the basic Network Services Monitoring MIB to allow monitoring of Message Transfer Agents (MTAs). It may also be used to monitor MTA components within gateways. [STANDARDS-TRACK]
 
RFC 1567 X.500 Directory Monitoring MIB
 
Authors:G. Mansfield, S. Kille.
Date:January 1994
Formats:txt pdf
Obsoleted by:RFC 2605
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1567
This document defines a portion of the Management Information Base(MIB). It defines the MIB for monitoring Directory System Agents(DSA), a component of the OSI Directory. This MIB will be used in conjunction with the APPLICATION-MIB for monitoring DSAs.
 
RFC 1568 Simple Network Paging Protocol - Version 1(b)
 
Authors:A. Gwinn.
Date:January 1994
Formats:txt pdf
Obsoleted by:RFC 1645
Status:INFORMATIONAL
DOI:10.17487/RFC 1568
This RFC suggests a simple way for delivering both alphanumeric and numeric pages (one-way) to radio paging terminals. Gateways supporting this protocol, as well as SMTP, have been in use for several months in one nationwide paging firm. One other paging firm is in the process of adopting it.

Earlier versions of this specification were reviewed by IESG members and the IETF's "822 Extensions" Working Group. They preferred an alternate strategy, as discussed under "Relationship to Other IETFWork", below.

 
RFC 1569 Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures
 
Authors:M. Rose.
Date:January 1994
Formats:txt pdf
Obsoleted by:RFC 1703
Status:INFORMATIONAL
DOI:10.17487/RFC 1569
This memo describes a technique for radio paging using the Internet mail infrastructure. In particular, this memo focuses on the case in which radio pagers are identified via the international telephone network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
 
RFC 1573 Evolution of the Interfaces Group of MIB-II
 
Authors:K. McCloghrie, F. Kastenholz.
Date:January 1994
Formats:txt pdf
Obsoletes:RFC 1229
Obsoleted by:RFC 2233
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1573
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing Network Interfaces. [STANARDS-TRACK]
 
RFC 1577 Classical IP and ARP over ATM
 
Authors:M. Laubach.
Date:January 1994
Formats:txt pdf
Obsoleted by:RFC 2225
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1577
This memo defines an initial application of classical IP and ARP in an Asynchronous Transfer Mode (ATM) network environment configured as a Logical IP Subnetwork (LIS) as described in Section 3. This memo does not preclude the subsequent development of ATM technology into areas other than a LIS; specifically, as single ATM networks grow to replace many ethernet local LAN segments and as these networks become globally connected, the application of IP and ARP will be treated differently. This memo considers only the application of ATM as a direct replacement for the "wires" and local LAN segments connectingIP end-stations ("members") and routers operating in the "classical"LAN-based paradigm. Issues raised by MAC level bridging and LAN emulation are beyond the scope of this paper.

This memo introduces general ATM technology and nomenclature.Readers are encouraged to review the ATM Forum and ITU-TS (formerlyCCITT) references for more detailed information about ATM implementation agreements and standards.

 
RFC 1578 FYI on Questions and Answers - Answers to Commonly Asked "Primary and Secondary School Internet User" Questions
 
Authors:J. Sellers.
Date:February 1994
Formats:txt pdf
Obsoleted by:RFC 1941
Status:INFORMATIONAL
DOI:10.17487/RFC 1578
The goal of this FYI RFC, produced by the Internet School Networking(ISN) group in the User Services Area of the Internet EngineeringTask Force (IETF), is to document the questions most commonly asked about the Internet by those in the primary and secondary school community, and to provide pointers to sources which answer those questions. It is directed at educators, school media specialists, and school administrators who are recently connected to the Internet, who are accessing the Internet via dial-up or another means which is not a direct connection, or who are considering an Internet connection as a resource for their schools.
 
RFC 1583 OSPF Version 2
 
Authors:J. Moy.
Date:March 1994
Formats:txt pdf ps
Obsoletes:RFC 1247
Obsoleted by:RFC 2178
Status:DRAFT STANDARD
DOI:10.17487/RFC 1583
This memo documents version 2 of the OSPF protocol. OSPF is a link-state routing protocol. It is designed to be run internal to a single Autonomous System. Each OSPF router maintains an identical database describing the Autonomous System's topology. From this database, a routing table is calculated by constructing a shortest- path tree.

OSPF recalculates routes quickly in the face of topological changes, utilizing a minimum of routing protocol traffic. OSPF provides support for equal-cost multipath. Separate routes can be calculated for each IP Type of Service. An area routing capability is provided, enabling an additional level of routing protection and a reduction in routing protocol traffic. In addition, all OSPF routing protocol exchanges are authenticated.

OSPF Version 2 was originally documented in RFC 1247. The differences between RFC 1247 and this memo are explained in AppendixE. The differences consist of bug fixes and clarifications, and are backward-compatible in nature. Implementations of RFC 1247 and of this memo will interoperate.

Please send comments to ospf@gated.cornell.edu.

 
RFC 1587 The OSPF NSSA Option
 
Authors:R. Coltun, V. Fuller.
Date:March 1994
Formats:txt pdf
Obsoleted by:RFC 3101
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1587
This document describes a new optional type of OSPF area, somewhat humorously referred to as a "not-so-stubby" area (or NSSA). NSSAs are similar to the existing OSPF stub area configuration option but have the additional capability of importing AS external routes in a limited fashion. [STANDARDS-TRACK]
 
RFC 1590 Media Type Registration Procedure
 
Authors:J. Postel.
Date:March 1994
Formats:txt pdf
Obsoleted by:RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049
Updates:RFC 1521
Status:INFORMATIONAL
DOI:10.17487/RFC 1590
Several protocols allow the use of data representing different"media" such as text, images, audio, and video, and within such media different encoding styles, such as (in video) jpeg, gif, ief, and tiff. The Multimedia Internet Message Extensions (MIME) protocol [1] defined several initial types of multimedia data objects, and a procedure for registering additional types with the Internet AssignedNumbers Authority (IANA). Several questions have been raised about the requirements and administrative procedure for registering MIME content-type and subtypes, and the use of these Media Types for other applications. This document addresses these issues and specifies a procedure for the registration of new Media Types (content- type/subtypes). It also generalizes the scope of use of these MediaTypes to make it appropriate to use the same registrations and specifications with other applications.
 
RFC 1594 FYI on Questions and Answers - Answers to Commonly asked "New Internet User" Questions
 
Authors:A. Marine, J. Reynolds, G. Malkin.
Date:March 1994
Formats:txt pdf
Obsoletes:RFC 1325
Obsoleted by:RFC 2664
Status:INFORMATIONAL
DOI:10.17487/RFC 1594
This FYI RFC is one of two FYI's called, "Questions and Answers"(Q/A), produced by the User Services Working Group of the InternetEngineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet.
 
RFC 1595 Definitions of Managed Objects for the SONET/SDH Interface Type
 
Authors:T. Brown, K. Tesink.
Date:March 1994
Formats:txt pdf
Obsoleted by:RFC 2558
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1595
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets.In particular, it defines objects for managing Synchronous OpticalNetwork/Synchronous Digital Hierarchy (SONET/SDH) objects. This document is a companion document with Definitions of Managed Objects for the DS1/E1 and DS3/E3 Interface Types, RFC1406 [14] and RFC1407[13].

This memo specifies a MIB module in a manner that is both compliant to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 definitions.

 
RFC 1596 Definitions of Managed Objects for Frame Relay Service
 
Authors:T. Brown, Ed..
Date:March 1994
Formats:txt pdf
Obsoleted by:RFC 1604
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1596
This memo defines an extension to the Management Information Base(MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the FrameRelay Service.
 
RFC 1597 Address Allocation for Private Internets
 
Authors:Y. Rekhter, B. Moskowitz, D. Karrenberg, G. de Groot.
Date:March 1994
Formats:txt pdf
Obsoleted by:RFC 1918
Status:INFORMATIONAL
DOI:10.17487/RFC 1597
This RFC describes methods to preserve IP address space by not allocating globally unique IP addresses to hosts private to an enterprise while still permitting full network layer connectivity between all hosts inside an enterprise as well as between all public hosts of different enterprises. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
 
RFC 1600 Internet Official Protocol Standards
 
Authors:J. Postel.
Date:March 1994
Formats:txt pdf
Obsoletes:RFC 1540
Obsoleted by:RFC 1610
Status:HISTORIC
DOI:10.17487/RFC 1600
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
 
RFC 1601 Charter of the Internet Architecture Board (IAB)
 
Authors:C. Huitema.
Date:March 1994
Formats:txt pdf
Obsoletes:RFC 1358
Obsoleted by:RFC 2850
Status:INFORMATIONAL
DOI:10.17487/RFC 1601
This memo documents the composition, selection, roles, and organization of the Internet Architecture Board and its subsidiary organizations.
 
RFC 1602 The Internet Standards Process -- Revision 2
 
Authors:Internet Architecture Board, Internet Engineering Steering Group.
Date:March 1994
Formats:txt pdf
Obsoletes:RFC 1310
Obsoleted by:RFC 2026
Updated by:RFC 1871
Status:INFORMATIONAL
DOI:10.17487/RFC 1602
This document is a revision of RFC 1310, which defined the official procedures for creating and documenting Internet Standards.

This revision (revision 2) includes the following major changes:

(a) The new management structure arising from the POISED WorkingGroup is reflected. These changes were agreed to by the IETF plenary and by the IAB and IESG in November 1992 and accepted by the ISOC Board of Trustees at their December 1992 meeting.

(b) Prototype status is added to the non-standards track maturity levels (Section 2.4.1).

(c) The Intellectual Property Rights section is completely revised, in accordance with legal advice. Section 5 of this document replaces Sections 5 and 6 of RFC-1310. The new section 5 has been reviewed by legal counsel to the Internet Society.

(d) An appeals procedure is added (Section 3.6).

(e) The wording of sections 1 and 1.2 has been changed to clarify the relationships that exist between the Internet Society and the IAB, the IESG, the IETF, and the Internet Standards process.

(f) An Appendix B has been added, listing the contact points for theRFC editor, the IANA, the IESG, the IAB and the ISOC. The"future issues" are now listed in Appendix C.

 
RFC 1603 IETF Working Group Guidelines and Procedures
 
Authors:E. Huizer, D. Crocker.
Date:March 1994
Formats:txt pdf
Obsoleted by:RFC 2418
Updated by:RFC 1871
Status:INFORMATIONAL
DOI:10.17487/RFC 1603
The Internet Engineering Task Force (IETF) has responsibility for developing and reviewing specifications intended as InternetStandards. IETF activities are organized into working groups (WGs).This document describes the guidelines and procedures for formation and operation of IETF working groups. It describes the formal relationship between IETF participants WG and the InternetEngineering Steering Group (IESG). The basic duties of IETF participants, including WG Chair and IESG Area Directors are defined.
 
RFC 1604 Definitions of Managed Objects for Frame Relay Service
 
Authors:T. Brown, Ed..
Date:March 1994
Formats:txt pdf
Obsoletes:RFC 1596
Obsoleted by:RFC 2954
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1604
This memo defines an extension to the Management Information Base(MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the FrameRelay Service.
 
RFC 1610 Internet Official Protocol Standards
 
Authors:J. Postel.
Date:July 1994
Formats:txt pdf
Obsoletes:RFC 1600
Obsoleted by:RFC 1720
Status:HISTORIC
DOI:10.17487/RFC 1610
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
 
RFC 1619 PPP over SONET/SDH
 
Authors:W. Simpson.
Date:May 1994
Formats:txt pdf
Obsoleted by:RFC 2615
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1619
The Point-to-Point Protocol (PPP) [1] provides a standard method for transporting multi-protocol datagrams over point-to-point links.This document describes the use of PPP over Synchronous OpticalNetwork (SONET) and Synchronous Digital Heirarchy (SDH) circuits.

This document is the product of the Point-to-Point Protocol WorkingGroup of the Internet Engineering Task Force (IETF). Comments should be submitted to the ietf-ppp@merit.edu mailing list.

 
RFC 1623 Definitions of Managed Objects for the Ethernet-like Interface Types
 
Authors:F. Kastenholz.
Date:May 1994
Formats:txt pdf
Obsoletes:RFC 1398
Obsoleted by:RFC 1643
Status:HISTORIC
DOI:10.17487/RFC 1623
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing ethernet-like objects. [STANDARDS-TRACK]
 
RFC 1626 Default IP MTU for use over ATM AAL5
 
Authors:R. Atkinson.
Date:May 1994
Formats:txt pdf
Obsoleted by:RFC 2225
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1626
There are a number of good reasons to have a reasonably large default MTU value for IP over ATM AAL5. This paper presents the default IP MIU for use over ATM AAL5. [STANDARDS-TRACK]
 
RFC 1627 Network 10 Considered Harmful (Some Practices Shouldn't be Codified)
 
Authors:E. Lear, E. Fair, D. Crocker, T. Kessler.
Date:July 1994
Formats:txt pdf
Obsoleted by:RFC 1918
Status:INFORMATIONAL
DOI:10.17487/RFC 1627
This document restates the arguments for maintaining a unique address space. Concerns for Internet architecture and operations, as well as IETF procedure, are explored. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
 
RFC 1631 The IP Network Address Translator (NAT)
 
Authors:K. Egevang, P. Francis.
Date:May 1994
Formats:txt pdf
Obsoleted by:RFC 3022
Status:INFORMATIONAL
DOI:10.17487/RFC 1631
The two most compelling problems facing the IP Internet are IP address depletion and scaling in routing. Long-term and short-term solutions to these problems are being developed. The short-term solution is CIDR (Classless InterDomain Routing). The long-term solutions consist of various proposals for new internet protocols with larger addresses.

It is possible that CIDR will not be adequate to maintain the IPInternet until the long-term solutions are in place. This memo proposes another short-term solution, address reuse, that complementsCIDR or even makes it unnecessary. The address reuse solution is to place Network Address Translators (NAT) at the borders of stub domains. Each NAT box has a table consisting of pairs of local IP addresses and globally unique addresses. The IP addresses inside the stub domain are not globally unique. They are reused in other domains, thus solving the address depletion problem. The globally unique IP addresses are assigned according to current CIDR address allocation schemes. CIDR solves the scaling problem. The main advantage of NAT is that it can be installed without changes to routers or hosts. This memo presents a preliminary design for NAT, and discusses its pros and cons.

 
RFC 1632 A Revised Catalog of Available X.500 Implementations
 
Authors:A. Getchell, Ed., S. Sataluri, Ed..
Date:May 1994
Formats:txt pdf
Obsoletes:RFC 1292
Obsoleted by:RFC 2116
Status:INFORMATIONAL
DOI:10.17487/RFC 1632
This document is the result of a survey that gathered new or updated descriptions of currently available implementations of X.500, including commercial products and openly available offerings. This document is a revision of RFC 1292. We contacted each contributor inRFC 1292 and requested an update and published the survey template in several mailing lists and obtained new product descriptions.

This document contains detailed description of twenty six (26) X.500 implementations - DSAs, DUAs, and DUA interfaces.

 
RFC 1637 DNS NSAP Resource Records
 
Authors:B. Manning, R. Colella.
Date:June 1994
Formats:txt pdf
Obsoletes:RFC 1348
Obsoleted by:RFC 1706
Status:EXPERIMENTAL
DOI:10.17487/RFC 1637
The Internet is moving towards the deployment of an OSI lower layers infrastructure. This infrastructure comprises the connectionless network protocol (CLNP) and supporting routing protocols. Also required as part of this infrastructure is support in the Domain NameSystem (DNS) for mapping between names and NSAP addresses.

This document defines the format of one new Resource Record (RR) for the DNS for domain name-to-NSAP mapping. The RR may be used with anyNSAP address format. This document supercedes RFC 1348.

NSAP-to-name translation is accomplished through use of the PTR RR(see STD 13, RFC 1035 for a description of the PTR RR). This paper describes how PTR RRs are used to support this translation.

 
RFC 1638 PPP Bridging Control Protocol (BCP)
 
Authors:F. Baker, R. Bowen.
Date:June 1994
Formats:txt pdf
Obsoletes:RFC 1220
Obsoleted by:RFC 2878
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1638
The Point-to-Point Protocol (PPP) [6] provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol, and proposes a family ofNetwork Control Protocols for establishing and configuring different network-layer protocols.

This document defines the Network Control Protocol for establishing and configuring Remote Bridging for PPP links.

 
RFC 1642 UTF-7 - A Mail-Safe Transformation Format of Unicode
 
Authors:D. Goldsmith, M. Davis.
Date:July 1994
Formats:txt pdf ps
Obsoleted by:RFC 2152
Status:EXPERIMENTAL
DOI:10.17487/RFC 1642
The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993(E) jointly define a 16 bit character set (hereafter referred to asUnicode) which encompasses most of the world's writing systems.However, Internet mail (STD 11, RFC 822) currently supports only 7- bit US ASCII as a character set. MIME (RFC 1521 and RFC 1522) extendsInternet mail to support different media types and character sets, and thus could support Unicode in mail messages. MIME neither definesUnicode as a permitted character set nor specifies how it would be encoded, although it does provide for the registration of additional character sets over time.

This document describes a new transformation format of Unicode that contains only 7-bit ASCII characters and is intended to be readable by humans in the limiting case that the document consists of characters from the US-ASCII repertoire. It also specifies how this transformation format is used in the context of RFC 1521, RFC 1522, and the document "Using Unicode with MIME".

 
RFC 1643 Definitions of Managed Objects for the Ethernet-like Interface Types
 
Authors:F. Kastenholz.
Date:July 1994
Formats:txt pdf
Obsoletes:RFC 1623
Obsoleted by:RFC 3638
Status:HISTORIC
DOI:10.17487/RFC 1643
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing ethernet-like objects. [STANDARDS-TRACK]
 
RFC 1644 T/TCP -- TCP Extensions for Transactions Functional Specification
 
Authors:R. Braden.
Date:July 1994
Formats:txt pdf
Obsoleted by:RFC 6247
Updates:RFC 1379
Status:HISTORIC
DOI:10.17487/RFC 1644
This memo specifies T/TCP, an experimental TCP extension for efficient transaction-oriented (request/response) service. This backwards-compatible extension could fill the gap between the current connection-oriented TCP and the datagram-based UDP.

This work was supported in part by the National Science Foundation under Grant Number NCR-8922231.

 
RFC 1645 Simple Network Paging Protocol - Version 2
 
Authors:A. Gwinn.
Date:July 1994
Formats:txt pdf
Obsoletes:RFC 1568
Obsoleted by:RFC 1861
Status:INFORMATIONAL
DOI:10.17487/RFC 1645
This RFC suggests a simple way for delivering both alphanumeric and numeric pages (one-way) to radio paging terminals. Gateways supporting this protocol, as well as SMTP, have been in use for several months for nationwide paging and messaging. In addition, email filters and SNPP client software for Unix and Windows are available at no cost. Please contact the author for more information.

Earlier versions of this specification were reviewed by IESG members and the "822 Extensions" Working Group. They preferred an alternate strategy, as discussed under "Relationship to Other IETF Work", below.

 
RFC 1647 TN3270 Enhancements
 
Authors:B. Kelly.
Date:July 1994
Formats:txt pdf
Obsoleted by:RFC 2355
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1647
This document describes a protocol that more fully supports 3270 devices than do the existing tn3270 practices. Specifically, it defines a method of emulating both the terminal and printer members of the 3270 family of devices via Telnet; it provides for the ability of a Telnet client to request that it be assigned a specific device- name (also referred to as "LU name" or "network name"); finally, it adds support for a variety of functions such as the ATTN key, theSYSREQ key, and SNA response handling.

This protocol would be negotiated and implemented under a new TelnetOption and would be unrelated to the Telnet 3270 Regime Option as defined in RFC 1041 [1].

 
RFC 1650 Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2
 
Authors:F. Kastenholz.
Date:August 1994
Formats:txt pdf
Obsoleted by:RFC 2358
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1650
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing ethernet-like objects. [STANDARDS-TRACK]
 
RFC 1651 SMTP Service Extensions
 
Authors:J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker.
Date:July 1994
Formats:txt pdf
Obsoletes:RFC 1425
Obsoleted by:RFC 1869
Status:DRAFT STANDARD
DOI:10.17487/RFC 1651
This memo defines a framework for extending the SMTP service by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports. [STANDARDS-TRACK]
 
RFC 1652 SMTP Service Extension for 8bit-MIMEtransport
 
Authors:J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker.
Date:July 1994
Formats:txt pdf
Obsoletes:RFC 1426
Obsoleted by:RFC 6152
Status:DRAFT STANDARD
DOI:10.17487/RFC 1652
This memo defines an extension to the SMTP service whereby an SMTP content body consisting of text containing octets outside of the US-ASCII octet range (hex 00-7F) may be relayed using SMTP.
 
RFC 1653 SMTP Service Extension for Message Size Declaration
 
Authors:J. Klensin, N. Freed, K. Moore.
Date:July 1994
Formats:txt pdf
Obsoletes:RFC 1427
Obsoleted by:RFC 1870
Status:DRAFT STANDARD
DOI:10.17487/RFC 1653
This memo defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to decline to accept a message (perhaps temporarily) based on the client's estimate of the message size.
 
RFC 1654 A Border Gateway Protocol 4 (BGP-4)
 
Authors:Y. Rekhter, Ed., T. Li, Ed..
Date:July 1994
Formats:txt pdf
Obsoleted by:RFC 1771
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1654
This document defines an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK]
 
RFC 1655 Application of the Border Gateway Protocol in the Internet
 
Authors:Y. Rekhter, Ed., P. Gross, Ed..
Date:July 1994
Formats:txt pdf
Obsoletes:RFC 1268
Obsoleted by:RFC 1772
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1655
This document, together with its companion document, "A BorderGateway Protocol 4 (BGP-4)", define an inter-autonomous system routing protocol for the Internet. "A Border Gateway Protocol 4(BGP-4)" defines the BGP protocol specification, and this document describes the usage of the BGP in the Internet.

Information about the progress of BGP can be monitored and/or reported on the BGP mailing list (bgp@ans.net).

 
RFC 1656 BGP-4 Protocol Document Roadmap and Implementation Experience
 
Authors:P. Traina.
Date:July 1994
Formats:txt pdf
Obsoleted by:RFC 1773
Status:INFORMATIONAL
DOI:10.17487/RFC 1656
Border Gateway Protocol v4 (BGP-4) [1] is an inter-Autonomous System routing protocol. It is built on experience gained with BGP as defined in RFC-1267 [2] and BGP usage in the connected Internet as described in RFC-1268 [3]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
 
RFC 1657 Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2
 
Authors:S. Willis, J. Burruss, J. Chu, Ed..
Date:July 1994
Formats:txt pdf
Obsoleted by:RFC 4273
Status:DRAFT STANDARD
DOI:10.17487/RFC 1657
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing the Border Gateway Protocol Version 4 or lower [1, 2]. [STANDARDS-TRACK]
 
RFC 1664 Using the Internet DNS to Distribute RFC1327 Mail Address Mapping Tables
 
Authors:C. Allocchio, A. Bonito, B. Cole, S. Giordano, R. Hagens.
Date:August 1994
Formats:txt pdf
Obsoleted by:RFC 2163
Status:EXPERIMENTAL
DOI:10.17487/RFC 1664
This memo defines how to store in the Internet Domain Name System the mapping information needed by e-mail gateways and other tools to mapRFC822 domain names into X.400 O/R names and vice versa. Mapping information can be managed in a distributed rather than a centralised way. Gateways located on Internet hosts can retrieve the mapping information querying the DNS instead of having fixed tables which need to be centrally updated and distributed. This memo is a joint effort of X400 operation working group (x400ops) and RARE Mail andMessaging working group (WG-MSG).
 
RFC 1665 Definitions of Managed Objects for SNA NAUs using SMIv2
 
Authors:Z. Kielczewski, Ed., D. Kostick, Ed., K. Shih, Ed..
Date:July 1994
Formats:txt pdf
Obsoleted by:RFC 1666
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1665
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing the configuration, monitoring and control of Physical Units (PUs) and Logical Units (LUs) in an SNA environment. [STANDARDS-TRACK]
 
RFC 1693 An Extension to TCP : Partial Order Service
 
Authors:T. Connolly, P. Amer, P. Conrad.
Date:November 1994
Formats:txt pdf
Obsoleted by:RFC 6247
Status:HISTORIC
DOI:10.17487/RFC 1693
This RFC introduces a new transport mechanism for TCP based upon partial ordering. The aim is to present the concepts of partial ordering and promote discussions on its usefulness in network communications. Distribution of this memo is unlimited.
 
RFC 1695 Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2
 
Authors:M. Ahmed, Ed., K. Tesink, Ed..
Date:August 1994
Formats:txt pdf
Obsoleted by:RFC 2515
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1695
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing ATM-based interfaces, devices, networks and services. [STANDARDS-TRACK]
 
RFC 1700 Assigned Numbers
 
Authors:J. Reynolds, J. Postel.
Date:October 1994
Formats:txt pdf
Obsoletes:RFC 1340
Obsoleted by:RFC 3232
Status:HISTORIC
DOI:10.17487/RFC 1700
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.
 
RFC 1714 Referral Whois Protocol (RWhois)
 
Authors:S. Williamson, M. Kosters.
Date:November 1994
Formats:txt ps pdf
Obsoleted by:RFC 2167
Status:INFORMATIONAL
DOI:10.17487/RFC 1714
This memo describes version 1.0 of the client/server interaction ofRWhois. RWhois provides a distributed system for the display of hierarchical information. This system is hierarchical by design, allowing for the reduction of a query, and the referral of the user closer to the maintainer of the information.
 
RFC 1716 Towards Requirements for IP Routers
 
Authors:P. Almquist, F. Kastenholz.
Date:November 1994
Formats:txt pdf
Obsoleted by:RFC 1812
Status:INFORMATIONAL
DOI:10.17487/RFC 1716
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.
 
RFC 1717 The PPP Multilink Protocol (MP)
 
Authors:K. Sklower, B. Lloyd, G. McGregor, D. Carr.
Date:November 1994
Formats:txt pdf
Obsoleted by:RFC 1990
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1717
This document proposes a method for splitting, recombining and sequencing datagrams across multiple logical data links. This work was originally motivated by the desire to exploit multiple bearer channels in ISDN, but is equally applicable to any situation in which multiple PPP links connect two systems, including async links. This is accomplished by means of new PPP [2] options and protocols.
 
RFC 1718 The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force
 
Authors:IETF Secretariat, G. Malkin.
Date:November 1994
Formats:txt pdf
Obsoletes:RFC 1539
Obsoleted by:RFC 3160
Status:INFORMATIONAL
DOI:10.17487/RFC 1718
Over the last two years, the attendance at Internet Engineering TaskForce (IETF) plenary meetings has grown phenomenally. Approximately one third of the attendees are new to the IETF at each meeting, and many of those go on to become regular attendees. When the meetings were smaller, it wasn't very difficult for a newcomer to get into the swing of things. Today, however, a newcomer meets many more new people, some previously known only as the authors of documents or thought provoking e-mail messages.

The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This will give them a warm, fuzzy feeling and enable them to make the meeting more productive for everyone. This FYI will also provide the mundane bits of information which everyone who attends an IETF meeting should know.

 
RFC 1720 Internet Official Protocol Standards
 
Authors:J. Postel.
Date:November 1994
Formats:txt pdf
Obsoletes:RFC 1610
Obsoleted by:RFC 1780
Status:HISTORIC
DOI:10.17487/RFC 1720
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
 
RFC 1723 RIP Version 2 - Carrying Additional Information
 
Authors:G. Malkin.
Date:November 1994
Formats:txt pdf
Obsoletes:RFC 1388
Obsoleted by:RFC 2453
Updates:RFC 1058
Status:INTERNET STANDARD
DOI:10.17487/RFC 1723
This document specifies an extension of the Routing InformationProtocol (RIP), as defined in [1,2], to 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.

The RIP-2 protocol analysis is documented in RFC 1721 [4].

The RIP-2 applicability statement is document in RFC 1722 [5].

The RIP-2 MIB description is defined in RFC 1724 [3]. This memo obsoletes RFC 1389.

 
RFC 1725 Post Office Protocol - Version 3
 
Authors:J. Myers, M. Rose.
Date:November 1994
Formats:txt pdf
Obsoletes:RFC 1460
Obsoleted by:RFC 1939
Status:INTERNET STANDARD
DOI:10.17487/RFC 1725
This memo is a revision to RFC 1460, a Draft Standard. [STANDARDS-TRACK]
 
RFC 1730 Internet Message Access Protocol - Version 4
 
Authors:M. Crispin.
Date:December 1994
Formats:txt pdf
Obsoleted by:RFC 2060, RFC 2061
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1730
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 (see also [IMAP-DISC]).

IMAP4 includes operations for creating, deleting, and renaming mailboxes; checking for new messages; permanently removing messages; setting and clearing flags; RFC 822 and MIME parsing; searching; and selective fetching of message attributes, texts, and portions thereof. Messages in IMAP4 are accessed by the use of numbers.These numbers are either message sequence numbers (relative position from 1 to the number of messages in the mailbox) or unique identifiers (immutable, strictly ascending values assigned to each message, but which are not necessarily contiguous).

IMAP4 supports a single server. A mechanism for supporting multipleIMAP4 servers is discussed in [IMSP].

IMAP4 does not specify a means of posting mail; this function is handled by a mail transfer protocol such as [SMTP].

IMAP4 is designed to be upwards compatible from the [IMAP2] protocol.Compatibility issues are discussed in [IMAP-COMPAT].

 
RFC 1734 POP3 AUTHentication command
 
Authors:J. Myers.
Date:December 1994
Formats:txt pdf
Obsoleted by:RFC 5034
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1734
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]
 
RFC 1738 Uniform Resource Locators (URL)
 
Authors:T. Berners-Lee, L. Masinter, M. McCahill.
Date:December 1994
Formats:txt pdf
Obsoleted by:RFC 4248, RFC 4266
Updated by:RFC 1808, RFC 2368, RFC 2396, RFC 3986, RFC 6196, RFC 6270, RFC 8089
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1738
This document specifies a Uniform Resource Locator (URL), the syntax and semantics of formalized information for location and access of resources via the Internet.
 
RFC 1739 A Primer On Internet and TCP/IP Tools
 
Authors:G. Kessler, S. Shepard.
Date:December 1994
Formats:txt pdf
Obsoleted by:RFC 2151
Status:INFORMATIONAL
DOI:10.17487/RFC 1739
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.
 
RFC 1743 IEEE 802.5 MIB using SMIv2
 
Authors:K. McCloghrie, E. Decker.
Date:December 1994
Formats:txt pdf
Obsoletes:RFC 1231
Obsoleted by:RFC 1748
Status:DRAFT STANDARD
DOI:10.17487/RFC 1743
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]
 
RFC 1750 Randomness Recommendations for Security
 
Authors:D. Eastlake 3rd, S. Crocker, J. Schiller.
Date:December 1994
Formats:txt pdf
Obsoleted by:RFC 4086
Status:INFORMATIONAL
DOI:10.17487/RFC 1750
Security systems today are built on increasingly strong cryptographic algorithms that foil pattern analysis attempts. However, the security of these systems is dependent on generating secret quantities for passwords, cryptographic keys, and similar quantities. The use of pseudo-random processes to generate secret quantities can result in pseudo-security. The sophisticated attacker of these security systems may find it easier to reproduce the environment that produced the secret quantities, searching the resulting small set of possibilities, than to locate the quantities in the whole of the number space.

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. It provides suggestions to ameliorate the problem when a hardware solution is not available. And it gives examples of how large such quantities need to be for some particular applications.

 
RFC 1757 Remote Network Monitoring Management Information Base
 
Authors:S. Waldbusser.
Date:February 1995
Formats:txt pdf
Obsoletes:RFC 1271
Obsoleted by:RFC 2819
Status:DRAFT STANDARD
DOI:10.17487/RFC 1757
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.
 
RFC 1759 Printer MIB
 
Authors:R. Smith, F. Wright, T. Hastings, S. Zilles, J. Gyllenskog.
Date:March 1995
Formats:txt pdf
Obsoleted by:RFC 3805
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1759
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]
 
RFC 1766 Tags for the Identification of Languages
 
Authors:H. Alvestrand.
Date:March 1995
Formats:txt pdf
Obsoleted by:RFC 3066, RFC 3282
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1766
This document describes a language tag for use in cases where it is desired to indicate the language used in an information object.

It also defines a Content-language: header, for use in the case where one desires to indicate the language of something that has RFC-822- like headers, like MIME body parts or Web documents, and a new parameter to the Multipart/Alternative type, to aid in the usage of the Content-Language: header.

 
RFC 1769 Simple Network Time Protocol (SNTP)
 
Authors:D. Mills.
Date:March 1995
Formats:txt pdf
Obsoletes:RFC 1361
Obsoleted by:RFC 2030, RFC 4330
Status:INFORMATIONAL
DOI:10.17487/RFC 1769
This memorandum describes the Simple Network Time Protocol (SNTP), which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. SNTP can be used when the ultimate performance of the full NTP implementation described inRFC-1305 is not needed or justified. It can operate in both unicast modes (point to point) and broadcast modes (point to multipoint). It can also operate in IP multicast mode where this service is available. SNTP involves no change to the current or previous NTP specification versions or known implementations, but rather a clarification of certain design features of NTP which allow operation in a simple, stateless remote-procedure call (RPC) mode with accuracy and reliability expectations similar to the UDP/TIME protocol described in RFC-868.

This memorandum obsoletes RFC-1361 of the same title. Its purpose is to explain the protocol model for operation in broadcast mode, to provide additional clarification in some places and to correct a few typographical errors. A working knowledge of the NTP Version 3 specification RFC-1305 is not required for an implementation of SNTP.Distribution of this memorandum is unlimited.

 
RFC 1770 IPv4 Option for Sender Directed Multi-Destination Delivery
 
Authors:C. Graff.
Date:March 1995
Formats:txt pdf
Obsoleted by:RFC 6814
Status:HISTORIC
DOI:10.17487/RFC 1770
This memo defines an IPv4 option to provide a sender directed multi- destination delivery mechanism called Selective Directed BroadcastMode (SDBM). The SDBM provides unreliable UDP delivery to a set ofIP addresses included in the option field of an IPv4 datagram. Data reliability if required will be provided by the application layer.This approach was developed to support sender directed multi- destination delivery to sparsely populated groups with no additional control traffic. This approach will find application in the extremely bandwidth constrained tactical military environment, as well as in some commercial applications requiring sender control of data delivery.
 
RFC 1771 A Border Gateway Protocol 4 (BGP-4)
 
Authors:Y. Rekhter, T. Li.
Date:March 1995
Formats:txt pdf
Obsoletes:RFC 1654
Obsoleted by:RFC 4271
Status:DRAFT STANDARD
DOI:10.17487/RFC 1771
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.
 
RFC 1777 Lightweight Directory Access Protocol
 
Authors:W. Yeong, T. Howes, S. Kille.
Date:March 1995
Formats:txt pdf
Obsoletes:RFC 1487
Obsoleted by:RFC 3494
Status:HISTORIC
DOI:10.17487/RFC 1777
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.500Directory, and is intended to be a complement to the DAP itself.

Key aspects of LDAP are:

- Protocol elements are carried directly over TCP or other transport, bypassing much of the session/presentation overhead.

- Many protocol data elements are encoding as ordinary strings (e.g.,Distinguished Names).

- A lightweight BER encoding is used to encode all protocol elements.

 
RFC 1778 The String Representation of Standard Attribute Syntaxes
 
Authors:T. Howes, S. Kille, W. Yeong, C. Robbins.
Date:March 1995
Formats:txt pdf
Obsoletes:RFC 1488
Obsoleted by:RFC 3494
Updated by:RFC 2559
Status:HISTORIC
DOI:10.17487/RFC 1778
The Lightweight Directory Access Protocol (LDAP) [9] requires that the contents of AttributeValue fields in protocol elements be octet strings. This document defines the requirements that must be satisfied by encoding rules used to render 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 defined in [1,2] and [3].
 
RFC 1779 A String Representation of Distinguished Names
 
Authors:S. Kille.
Date:March 1995
Formats:txt pdf
Obsoletes:RFC 1485
Obsoleted by:RFC 2253, RFC 3494
Status:HISTORIC
DOI:10.17487/RFC 1779
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.
 
RFC 1780 Internet Official Protocol Standards
 
Authors:J. Postel, Ed..
Date:March 1995
Formats:txt pdf
Obsoletes:RFC 1720
Obsoleted by:RFC 1800
Status:HISTORIC
DOI:10.17487/RFC 1780
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
 
RFC 1781 Using the OSI Directory to Achieve User Friendly Naming
 
Authors:S. Kille.
Date:March 1995
Formats:txt pdf
Obsoletes:RFC 1484
Obsoleted by:RFC 3494
Status:HISTORIC
DOI:10.17487/RFC 1781
The OSI Directory has user friendly naming as a goal. A simple minded usage of the directory does not achieve this. Two aspects not achieved are: o A user oriented notation o Guessability

This proposal sets out some conventions for representing names in a friendly manner, and shows how this can be used to achieve really friendly naming. This then leads to a specification of a standard format for representing names, and to procedures to resolve them.This leads to a specification which allows directory names to be communicated between humans. The format in this specification is identical to that defined in [5], and it is intended that these specifications are compatible.

 
RFC 1782 TFTP Option Extension
 
Authors:G. Malkin, A. Harkin.
Date:March 1995
Formats:txt pdf
Obsoleted by:RFC 2347
Updates:RFC 1350
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1782
The Trivial File Transfer Protocol [1] 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.
 
RFC 1783 TFTP Blocksize Option
 
Authors:G. Malkin, A. Harkin.
Date:March 1995
Formats:txt pdf
Obsoleted by:RFC 2348
Updates:RFC 1350
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1783
The Trivial File Transfer Protocol [1] is a simple, lock-step, file transfer protocol which allows a client to get or put a file onto a remote host. One of its primary uses is the booting of diskless nodes on a Local Area Network. TFTP is used because it is very simple to implement in a small node's limited ROM space. However, the choice of a 512-byte blocksize is not the most efficient for use on a LAN whose MTU may 1500 bytes or greater.

This document describes a TFTP option which allows the client and server to negotiate a blocksize more applicable to the network medium. The TFTP Option Extension mechanism is described in [2].

 
RFC 1784 TFTP Timeout Interval and Transfer Size Options
 
Authors:G. Malkin, A. Harkin.
Date:March 1995
Formats:txt pdf
Obsoleted by:RFC 2349
Updates:RFC 1350
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1784
The Trivial File Transfer Protocol [1] 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. 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. The TFTP Option Extension mechanism is described in [2].

This document assumes that the reader is familiar with the terminology and notation of both [1] and [2].

 
RFC 1788 ICMP Domain Name Messages
 
Authors:W. Simpson.
Date:April 1995
Formats:txt pdf
Obsoleted by:RFC 6918
Status:HISTORIC
DOI:10.17487/RFC 1788
This document specifies ICMP messages for learning the FullyQualified Domain Name associated with an IP address.
 
RFC 1798 Connection-less Lightweight X.500 Directory Access Protocol
 
Authors:A. Young.
Date:June 1995
Formats:txt pdf
Obsoleted by:RFC 3352
Status:HISTORIC
DOI:10.17487/RFC 1798
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]
 
RFC 1800 Internet Official Protocol Standards
 
Authors:J. Postel, Ed..
Date:July 1995
Formats:txt pdf
Obsoletes:RFC 1780
Obsoleted by:RFC 1880
Status:HISTORIC
DOI:10.17487/RFC 1800
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
 
RFC 1806 Communicating Presentation Information in Internet Messages: The Content-Disposition Header
 
Authors:R. Troost, S. Dorner.
Date:June 1995
Formats:txt pdf
Obsoleted by:RFC 2183
Status:EXPERIMENTAL
DOI:10.17487/RFC 1806
This memo provides a mechanism whereby messages conforming to the[RFC 1521] ("MIME") specification can convey presentational information. It specifies a new "Content-Disposition" header, optional and valid for any [RFC 1521] entity ("message" or "body part"). Two values for this header are described in this memo; one for the ordinary linear presentation of the body part, and another to facilitate the use of mail to transfer files. It is expected that more values will be defined in the future, and procedures are defined for extending this set of values.

This document is intended as an extension to [RFC 1521]. As such, the reader is assumed to be familiar with [RFC 1521], and [RFC 822]. The information presented herein supplements but does not replace that found in those documents.

 
RFC 1808 Relative Uniform Resource Locators
 
Authors:R. Fielding.
Date:June 1995
Formats:txt pdf
Obsoleted by:RFC 3986
Updates:RFC 1738
Updated by:RFC 2368, RFC 2396
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1808
A Uniform Resource Locator (URL) is a compact representation of the location and access method for a resource available via the Internet.When embedded within a base document, a URL in its absolute form may contain a great deal of information which is already known from the context of that base document's retrieval, including the scheme, network location, and parts of the url-path. 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 UniformResource Locators.
 
RFC 1811 U.S
 
Authors:Government Internet Domain Names. Federal Networking Council.
Date:June 1995
Formats:txt pdf
Obsoleted by:RFC 1816
Status:INFORMATIONAL
DOI:10.17487/RFC 1811
This document describes the registration policies for the top-level domain ".GOV". Thus far, Federal Agencies and their subsidiaries have registered without any guidance. This has resulted in multiple registrations for Federal Agencies and naming schemes that do not facilitate responsiveness to the public. This document fixes this by restricting registrations to coincide with the approved structure of the US government. The document cited, FIPS 95-1, provides a standard recognized structure into which domain registrations for top-level domains. The IANA requires that an organization/country apply for and get a 2 letter code from ISO/ITU (e.g., US for UnitedStates) for additional top-level registration.

As a side effect, this reduces the number of .GOV level registrations and reduces the workload on the Internic.

 
RFC 1816 U.S
 
Authors:Government Internet Domain Names. Federal Networking Council.
Date:August 1995
Formats:txt pdf
Obsoletes:RFC 1811
Obsoleted by:RFC 2146
Status:INFORMATIONAL
DOI:10.17487/RFC 1816
This memo provides an update and clarification to RFC 1811. This document describes the registration policies for the top-level domain".GOV". Thus far, Federal Agencies and their subsidiaries have registered without any guidance. This has resulted in multiple registrations for Federal Agencies and naming schemes that do not facilitate responsiveness to the public. This document fixes this by restricting registrations to coincide with the approved structure of the US government. The document cited, FIPS 95-1, provides a standard recognized structure into which domain registrations for.GOV can be fit. This policy is exactly comparable to that for the top-level domains. The IANA requires that an organization/country apply for and get a 2 letter code from ISO/ITU (e.g., US for UnitedStates) for additional top-level registration.

As a side effect, this reduces the number of .GOV level registrations and reduces the workload on the Internic.

 
RFC 1820 Multimedia E-mail (MIME) User Agent Checklist
 
Authors:E. Huizer.
Date:August 1995
Formats:txt pdf
Obsoleted by:RFC 1844
Status:INFORMATIONAL
DOI:10.17487/RFC 1820
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.
 
RFC 1825 Security Architecture for the Internet Protocol
 
Authors:R. Atkinson.
Date:August 1995
Formats:txt pdf
Obsoleted by:RFC 2401
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1825
This memo describes the security mechanisms for IP version 4 (IPv4) and IP version 6 (IPv6) and the services that they provide. [STANDARDS- TRACK]
 
RFC 1826 IP Authentication Header
 
Authors:R. Atkinson.
Date:August 1995
Formats:txt pdf
Obsoleted by:RFC 2402
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1826
This document describes a mechanism for providing cryptographic authentication for IPv4 and IPv6 datagrams. [STANDARDS-TRACK]
 
RFC 1827 IP Encapsulating Security Payload (ESP)
 
Authors:R. Atkinson.
Date:August 1995
Formats:txt pdf
Obsoleted by:RFC 2406
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1827
This document describes the IP Encapsulating Security Payload (ESP). ESP is a mechanism for providing integrity and confidentiality to IP datagrams. [STANDARDS-TRACK]
 
RFC 1830 SMTP Service Extensions for Transmission of Large and Binary MIME Messages
 
Authors:G. Vaudreuil.
Date:August 1995
Formats:txt pdf
Obsoleted by:RFC 3030
Status:EXPERIMENTAL
DOI:10.17487/RFC 1830
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.
 
RFC 1831 RPC: Remote Procedure Call Protocol Specification Version 2
 
Authors:R. Srinivasan.
Date:August 1995
Formats:txt pdf
Obsoleted by:RFC 5531
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1831
This document describes the ONC Remote Procedure Call (ONC RPC Version 2) protocol as it is currently deployed and accepted. [STANDARDS-TRACK]
 
RFC 1832 XDR: External Data Representation Standard
 
Authors:R. Srinivasan.
Date:August 1995
Formats:txt pdf
Obsoleted by:RFC 4506
Status:DRAFT STANDARD
DOI:10.17487/RFC 1832
This document describes the External Data Representation Standard (XDR) protocol as it is currently deployed and accepted. [STANDARDS-TRACK]
 
RFC 1836 Representing the O/R Address hierarchy in the X.500 Directory Information Tree
 
Authors:S. Kille.
Date:August 1995
Formats:txt pdf
Obsoleted by:RFC 2294
Status:EXPERIMENTAL
DOI:10.17487/RFC 1836
This document defines a representation of the O/R Address hierarchy in the Directory Information Tree [6, 1]. This is useful for a range of purposes, including:
 
RFC 1837 Representing Tables and Subtrees in the X.500 Directory
 
Authors:S. Kille.
Date:August 1995
Formats:txt pdf
Obsoleted by:RFC 2293
Status:EXPERIMENTAL
DOI:10.17487/RFC 1837
This document defines techniques for representing two types of information mapping in the OSI Directory [1].

1. Mapping from a key to a value (or set of values), as might be done in a table lookup.

2. 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.

These techniques were developed for supporting MHS use of Directory[2], but are specified separately as they have more general applicability.

 
RFC 1838 Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses
 
Authors:S. Kille.
Date:August 1995
Formats:txt pdf
Obsoleted by:RFC 2164
Status:EXPERIMENTAL
DOI:10.17487/RFC 1838
This document defines how to use directory to support the mapping between X.400 O/R Addresses and mailboxes defined in RFC 1327 [2].
 
RFC 1849 "Son of 1036": News Article Format and Transmission
 
Authors:H. Spencer.
Date:March 2010
Formats:txt pdf
Obsoleted by:RFC 5536, RFC 5537
Status:HISTORIC
DOI:10.17487/RFC 1849
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 adoptedProposed Standards for Netnews.

It is being published now in order to provide the historical background out of which those standards have grown. Present-day implementors should be aware that it is NOT NOW APPROPRIATE for use in current implementations.

 
RFC 1850 OSPF Version 2 Management Information Base
 
Authors:F. Baker, R. Coltun.
Date:November 1995
Formats:txt pdf
Obsoletes:RFC 1253
Obsoleted by:RFC 4750
Status:DRAFT STANDARD
DOI:10.17487/RFC 1850
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 PathFirst Routing Protocol.
 
RFC 1852 IP Authentication using Keyed SHA
 
Authors:P. Metzger, W. Simpson.
Date:September 1995
Formats:txt pdf
Obsoleted by:RFC 2841
Status:EXPERIMENTAL
DOI:10.17487/RFC 1852
This document describes the use of keyed SHA with the IPAuthentication Header.
 
RFC 1854 SMTP Service Extension for Command Pipelining
 
Authors:N. Freed.
Date:October 1995
Formats:txt pdf
Obsoleted by:RFC 2197
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1854
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. Using a single TCP send operation for multiple commands can improve SMTP performance significantly.
 
RFC 1860 Variable Length Subnet Table For IPv4
 
Authors:T. Pummill, B. Manning.
Date:October 1995
Formats:txt pdf
Obsoleted by:RFC 1878
Status:INFORMATIONAL
DOI:10.17487/RFC 1860
This document itemizes the potential values for IPv4 subnets.Additional information is provided for Hex and Decmial values, classfull equivalents, and number of addresses available within the indicated block. We appreciate inputs from Bruce Pinsky (cisco) andDaniel Karrenberg (RIPE).
 
RFC 1863 A BGP/IDRP Route Server alternative to a full mesh routing
 
Authors:D. Haskin.
Date:October 1995
Formats:txt pdf
Obsoleted by:RFC 4223
Status:HISTORIC
DOI:10.17487/RFC 1863
This document describes the use and detailed design of Route Servers for dissemination of routing information among BGP/IDRP speaking routers.

The intention of the proposed technique is to reduce overhead and management complexity of maintaining numerous direct BGP/IDRP sessions which otherwise might be required or desired among routers within a single routing domain as well as among routers in different domains that are connected to a common switched fabric (e.g. an ATM cloud).

 
RFC 1866 Hypertext Markup Language - 2.0
 
Authors:T. Berners-Lee, D. Connolly.
Date:November 1995
Formats:txt pdf
Obsoleted by:RFC 2854
Status:HISTORIC
DOI:10.17487/RFC 1866
The Hypertext Markup Language (HTML) is a simple markup language used to create hypertext documents that are platform independent. HTML documents are SGML documents with generic semantics that are appropriate for representing information from a wide range of domains. HTML markup can represent hypertext news, mail, documentation, and hypermedia; menus of options; database query results; simple structured documents with in-lined graphics; and hypertext views of existing bodies of information.

HTML has been in use by the World Wide Web (WWW) global information initiative since 1990. This specification roughly corresponds to the capabilities of HTML in common use prior to June 1994. HTML is an application of ISO Standard 8879:1986 Information Processing Text andOffice Systems; Standard Generalized Markup Language (SGML).

The "text/html" Internet Media Type (RFC 1590) and MIME Content Type(RFC 1521) is defined by this specification.

 
RFC 1867 Form-based File Upload in HTML
 
Authors:E. Nebel, L. Masinter.
Date:November 1995
Formats:txt pdf
Obsoleted by:RFC 2854
Status:HISTORIC
DOI:10.17487/RFC 1867
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.
 
RFC 1869 SMTP Service Extensions
 
Authors:J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker.
Date:November 1995
Formats:txt pdf
Obsoletes:RFC 1651
Obsoleted by:RFC 2821
Also:STD 0010
Status:INTERNET STANDARD
DOI:10.17487/RFC 1869
This memo defines a framework for extending the SMTP service by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports. [STANDARDS-TRACK]
 
RFC 1871 Addendum to RFC 1602 -- Variance Procedure
 
Authors:J. Postel.
Date:November 1995
Formats:txt pdf
Obsoleted by:RFC 2026
Updates:RFC 1602, RFC 1603
Status:HISTORIC
DOI:10.17487/RFC 1871
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 is a modification to the procedures of RFC 1602 and 1603.
 
RFC 1872 The MIME Multipart/Related Content-type
 
Authors:E. Levinson.
Date:December 1995
Formats:txt pdf
Obsoleted by:RFC 2112
Status:EXPERIMENTAL
DOI:10.17487/RFC 1872
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.
 
RFC 1880 Internet Official Protocol Standards
 
Authors:J. Postel, Ed..
Date:November 1995
Formats:txt pdf
Obsoletes:RFC 1800
Obsoleted by:RFC 1920
Status:HISTORIC
DOI:10.17487/RFC 1880
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
 
RFC 1883 Internet Protocol, Version 6 (IPv6) Specification
 
Authors:S. Deering, R. Hinden.
Date:December 1995
Formats:txt pdf
Obsoleted by:RFC 2460
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1883
This document specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng.
 
RFC 1884 IP Version 6 Addressing Architecture
 
Authors:R. Hinden, Ed., S. Deering, Ed..
Date:December 1995
Formats:txt pdf
Obsoleted by:RFC 2373
Status:HISTORIC
DOI:10.17487/RFC 1884
This specification defines the addressing architecture of the IPVersion 6 protocol [IPV6]. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and anIPv6 nodes required addresses.
 
RFC 1885 Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6)
 
Authors:A. Conta, S. Deering.
Date:December 1995
Formats:txt pdf
Obsoleted by:RFC 2463
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1885
This document specifies a set of Internet Control Message Protocol(ICMP) messages for use with version 6 of the Internet Protocol(IPv6). The Internet Group Management Protocol (IGMP) messages specified in STD 5, RFC 1112 have been merged into ICMP, for IPv6, and are included in this document.
 
RFC 1886 DNS Extensions to support IP version 6
 
Authors:S. Thomson, C. Huitema.
Date:December 1995
Formats:txt pdf
Obsoleted by:RFC 3596
Updated by:RFC 2874, RFC 3152
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1886
This document defines the changes that need to be made to the DomainName System to support hosts running IP version 6 (IPv6). The changes include a new resource record type to store an IPv6 address, a new domain to support lookups based on an IPv6 address, and updated definitions of existing query types that return Internet addresses as part of additional section processing. The extensions are designed to be compatible with existing applications and, in particular, DNS implementations themselves.
 
RFC 1888 OSI NSAPs and IPv6
 
Authors:J. Bound, B. Carpenter, D. Harrington, J. Houldsworth, A. Lloyd.
Date:August 1996
Formats:txt pdf
Obsoleted by:RFC 4048
Updated by:RFC 4548
Status:HISTORIC
DOI:10.17487/RFC 1888
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. However, it also defines a set of mechanisms for the support of OSI NSAP addressing in an IPv6 network. These mechanisms are the ones that MUST be used if such support is required. This document also defines a mapping of IPv6 addresses within the OSI address format, should this be required.
 
RFC 1889 RTP: A Transport Protocol for Real-Time Applications
 
Authors:Audio-Video Transport Working Group, H. Schulzrinne, S. Casner, R. Frederick, V. Jacobson.
Date:January 1996
Formats:txt pdf
Obsoleted by:RFC 3550
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1889
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. RTP does not address resource reservation and does not guarantee quality-of- service for real-time services. The data transport is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner scalable to large multicast networks, and to provide minimal control and identification functionality. RTP and RTCP are designed to be independent of the underlying transport and network layers. The protocol supports the use of RTP-level translators and mixers.
 
RFC 1890 RTP Profile for Audio and Video Conferences with Minimal Control
 
Authors:Audio-Video Transport Working Group, H. Schulzrinne.
Date:January 1996
Formats:txt pdf
Obsoleted by:RFC 3551
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1890
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. It provides interpretations of generic fields within the RTP specification suitable for audio and video conferences. In particular, this document defines a set of default mappings from payload type numbers to encodings.

The document also describes how audio and video data may be carried within RTP. It defines a set of standard encodings and their names when used within RTP. However, the encoding definitions are independent of the particular transport mechanism used. The descriptions provide pointers to reference implementations and the detailed standards. This document is meant as an aid for implementors of audio, video and other real-time multimedia applications.

 
RFC 1891 SMTP Service Extension for Delivery Status Notifications
 
Authors:K. Moore.
Date:January 1996
Formats:txt pdf
Obsoleted by:RFC 3461
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1891
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]
 
RFC 1892 The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages
 
Authors:G. Vaudreuil.
Date:January 1996
Formats:txt pdf
Obsoleted by:RFC 3462
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1892
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]
 
RFC 1893 Enhanced Mail System Status Codes
 
Authors:G. Vaudreuil.
Date:January 1996
Formats:txt pdf
Obsoleted by:RFC 3463
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1893
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]
 
RFC 1894 An Extensible Message Format for Delivery Status Notifications
 
Authors:K. Moore, G. Vaudreuil.
Date:January 1996
Formats:txt pdf
Obsoleted by:RFC 3464
Updated by:RFC 2852
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1894
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. This content-type is intended as a machine-processable replacement for the various types of delivery status notifications currently used inInternet electronic mail.

Because many messages are sent between the Internet and other messaging systems (such as X.400 or the so-called "LAN-based" systems), the DSN protocol is designed to be useful in a multi- protocol messaging environment. To this end, the protocol described in this memo provides for the carriage of "foreign" addresses and error codes, in addition to those normally used in Internet mail.Additional attributes may also be defined to support "tunneling" of foreign notifications through Internet mail.

Any questions, comments, and reports of defects or ambiguities in this specification may be sent to the mailing list for the NOTARY working group of the IETF, using the address<notifications@cs.utk.edu&rt;. Requests to subscribe to the mailing list should be addressed to <notifications-request@cs.utk.edu&rt;.Implementors of this specification are encouraged to subscribe to the mailing list, so that they will quickly be informed of any problems which might hinder interoperability.

NOTE: This document is a Proposed Standard. If and when this protocol is submitted for Draft Standard status, any normative text(phrases containing SHOULD, SHOULD NOT, MUST, MUST NOT, or MAY) in this document will be re-evaluated in light of implementation experience, and are thus subject to change.

 
RFC 1897 IPv6 Testing Address Allocation
 
Authors:R. Hinden, J. Postel.
Date:January 1996
Formats:txt pdf
Obsoleted by:RFC 2471
Status:EXPERIMENTAL
DOI:10.17487/RFC 1897
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.
 
RFC 1902 Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)
 
Authors:J. Case, K. McCloghrie, M. Rose, S. Waldbusser.
Date:January 1996
Formats:txt pdf
Obsoletes:RFC 1442
Obsoleted by:RFC 2578
Status:DRAFT STANDARD
DOI:10.17487/RFC 1902
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]
 
RFC 1903 Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)
 
Authors:J. Case, K. McCloghrie, M. Rose, S. Waldbusser.
Date:January 1996
Formats:txt pdf
Obsoletes:RFC 1443
Obsoleted by:RFC 2579
Status:DRAFT STANDARD
DOI:10.17487/RFC 1903
It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK]
 
RFC 1904 Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)
 
Authors:J. Case, K. McCloghrie, M. Rose, S. Waldbusser.
Date:January 1996
Formats:txt pdf
Obsoletes:RFC 1444
Obsoleted by:RFC 2580
Status:DRAFT STANDARD
DOI:10.17487/RFC 1904
It may be useful to define the acceptable lower-bounds of implementation, along with the actual level of implementation achieved. It is the purpose of this document to define the notation used for these purposes. [STANDARDS-TRACK]
 
RFC 1905 Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)
 
Authors:J. Case, K. McCloghrie, M. Rose, S. Waldbusser.
Date:January 1996
Formats:txt pdf
Obsoletes:RFC 1448
Obsoleted by:RFC 3416
Status:DRAFT STANDARD
DOI:10.17487/RFC 1905
It is the purpose of this document, Protocol Operations for SNMPv2, to define the operations of the protocol with respect to the sending and receiving of the PDUs. [STANDARDS-TRACK]
 
RFC 1906 Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)
 
Authors:J. Case, K. McCloghrie, M. Rose, S. Waldbusser.
Date:January 1996
Formats:txt pdf
Obsoletes:RFC 1449
Obsoleted by:RFC 3417
Status:DRAFT STANDARD
DOI:10.17487/RFC 1906
It is the purpose of this document to define how the SNMPv2 maps onto an initial set of transport domains. [STANDARDS-TRACK]
 
RFC 1907 Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)
 
Authors:J. Case, K. McCloghrie, M. Rose, S. Waldbusser.
Date:January 1996
Formats:txt pdf
Obsoletes:RFC 1450
Obsoleted by:RFC 3418
Status:DRAFT STANDARD
DOI:10.17487/RFC 1907
It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity. [STANDARDS-TRACK]
 
RFC 1908 Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework
 
Authors:J. Case, K. McCloghrie, M. Rose, S. Waldbusser.
Date:January 1996
Formats:txt pdf
Obsoletes:RFC 1452
Obsoleted by:RFC 2576
Status:DRAFT STANDARD
DOI:10.17487/RFC 1908
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]
 
RFC 1911 Voice Profile for Internet Mail
 
Authors:G. Vaudreuil.
Date:February 1996
Formats:txt pdf
Obsoleted by:RFC 2421, RFC 2422, RFC 2423
Status:EXPERIMENTAL
DOI:10.17487/RFC 1911
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.
 
RFC 1920 Internet Official Protocol Standards
 
Authors:J. Postel.
Date:March 1996
Formats:txt pdf
Obsoletes:RFC 1880
Obsoleted by:RFC 2000
Status:HISTORIC
DOI:10.17487/RFC 1920
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
 
RFC 1933 Transition Mechanisms for IPv6 Hosts and Routers
 
Authors:R. Gilligan, E. Nordmark.
Date:April 1996
Formats:txt pdf
Obsoleted by:RFC 2893
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1933
This document specifies IPv4 compatibility mechanisms that can be implemented by IPv6 hosts and routers. These mechanisms include providing complete implementations of both versions of the InternetProtocol (IPv4 and IPv6), and tunneling IPv6 packets over IPv4 routing infrastructures. They are designed to allow IPv6 nodes to maintain complete compatibility with IPv4, which should greatly simplify the deployment of IPv6 in the Internet, and facilitate the eventual transition of the entire Internet to IPv6.
 
RFC 1938 A One-Time Password System
 
Authors:N. Haller, C. Metz.
Date:May 1996
Formats:txt pdf
Obsoleted by:RFC 2289
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1938
This document describes a one-time password authentication system (OTP). [STANDARDS-TRACK]
 
RFC 1942 HTML Tables
 
Authors:D. Raggett.
Date:May 1996
Formats:txt pdf
Obsoleted by:RFC 2854
Status:HISTORIC
DOI:10.17487/RFC 1942
The HyperText Markup Language (HTML) is a simple markup language used to create hypertext documents that are portable from one platform to another. HTML documents are SGML documents with generic semantics that are appropriate for representing information from a wide range of applications. This specification extends HTML to support a wide variety of tables. The model is designed to work well with associated style sheets, but does not require them. It also supports rendering to braille, or speech, and exchange of tabular data with databases and spreadsheets. The HTML table model embodies certain aspects of the CALS table model, e.g. the ability to group table rows into thead, tbody and tfoot sections, plus the ability to specify cell alignment compactly for sets of cells according to the context.
 
RFC 1944 Benchmarking Methodology for Network Interconnect Devices
 
Authors:S. Bradner, J. McQuaid.
Date:May 1996
Formats:txt pdf
Obsoleted by:RFC 2544
Status:INFORMATIONAL
DOI:10.17487/RFC 1944
This document discusses and defines a number of tests that may be used to describe the performance characteristics of a network interconnecting device. In addition to defining the tests this document also describes specific formats for reporting the results of the tests. Appendix A lists the tests and conditions that we believe should be included for specific cases and gives additional information about testing practices. Appendix B is a reference listing of maximum frame rates to be used with specific frame sizes on various media and Appendix C gives some examples of frame formats to be used in testing.
 
RFC 1948 Defending Against Sequence Number Attacks
 
Authors:S. Bellovin.
Date:May 1996
Formats:txt pdf
Obsoleted by:RFC 6528
Status:INFORMATIONAL
DOI:10.17487/RFC 1948
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.
 
RFC 1959 An LDAP URL Format
 
Authors:T. Howes, M. Smith.
Date:June 1996
Formats:txt pdf
Obsoleted by:RFC 2255
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1959
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]
 
RFC 1960 A String Representation of LDAP Search Filters
 
Authors:T. Howes.
Date:June 1996
Formats:txt pdf
Obsoletes:RFC 1558
Obsoleted by:RFC 2254
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1960
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]
 
RFC 1965 Autonomous System Confederations for BGP
 
Authors:P. Traina.
Date:June 1996
Formats:txt pdf
Obsoleted by:RFC 3065
Status:EXPERIMENTAL
DOI:10.17487/RFC 1965
Border Gateway Protocol [1] is an inter-autonomous system routing protocol designed for TCP/IP networks.

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.

The intention of this extension is to aid in policy administration and reduce the management complexity of maintaining a large autonomous system.

The extension this document describes is widely deployed in theInternet today.

 
RFC 1966 BGP Route Reflection An alternative to full mesh IBGP
 
Authors:T. Bates, R. Chandra.
Date:June 1996
Formats:txt pdf
Obsoleted by:RFC 4456
Updated by:RFC 2796
Status:EXPERIMENTAL
DOI:10.17487/RFC 1966
The Border Gateway Protocol [1] is an inter-autonomous system routing protocol designed for TCP/IP internets. BGP deployments are configured such that that all BGP speakers within a single AS must be fully meshed so that any external routing information must be re- distributed to all other routers within that AS. This represents a serious scaling problem that has been well documented with several alternatives proposed [2,3].

This document describes the use and design of a method known as"Route Reflection" to alleviate the the need for "full mesh" IBGP.

 
RFC 1969 The PPP DES Encryption Protocol (DESE)
 
Authors:K. Sklower, G. Meyer.
Date:June 1996
Formats:txt pdf
Obsoleted by:RFC 2419
Status:INFORMATIONAL
DOI:10.17487/RFC 1969
The Point-to-Point Protocol (PPP) [1] provides a standard method for transporting multi-protocol datagrams over point-to-point links.

The PPP Encryption Control Protocol (ECP) [2] provides a method to negotiate and utilize encryption protocols over PPP encapsulated links.

This document provides specific details for the use of the DES standard [5, 6] for encrypting PPP encapsulated packets.

 
RFC 1970 Neighbor Discovery for IP Version 6 (IPv6)
 
Authors:T. Narten, E. Nordmark, W. Simpson.
Date:August 1996
Formats:txt pdf
Obsoleted by:RFC 2461
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1970
This document specifies the Neighbor Discovery protocol for IPVersion 6. IPv6 nodes on the same link use Neighbor Discovery to discover each other's presence, to determine each other's link-layer addresses, to find routers and to maintain reachability information about the paths to active neighbors.
 
RFC 1971 IPv6 Stateless Address Autoconfiguration
 
Authors:S. Thomson, T. Narten.
Date:August 1996
Formats:txt pdf
Obsoleted by:RFC 2462
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1971
This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. The autoconfiguration process includes creating a link-local address and verifying its uniqueness on a link, determining what information should be autoconfigured (addresses, other information, or both), and in the case of addresses, whether they should be obtained through the stateless mechanism, the stateful mechanism, or both. This document defines the process for generating a link-local address, the process for generating site-local and global addresses via stateless address autoconfiguration, and the Duplicate Address Detection procedure. The details of autoconfiguration using the stateful protocol are specified elsewhere.
 
RFC 1972 A Method for the Transmission of IPv6 Packets over Ethernet Networks
 
Authors:M. Crawford.
Date:August 1996
Formats:txt pdf
Obsoleted by:RFC 2464
Status:PROPOSED STANDARD
DOI:10.17487/RFC 1972
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]
 
RFC 1980 A Proposed Extension to HTML : Client-Side Image Maps
 
Authors:J. Seidman.
Date:August 1996
Formats:txt pdf
Obsoleted by:RFC 2854
Status:HISTORIC
DOI:10.17487/RFC 1980
The markup language known as "HTML/2.0" provides for image maps.Image maps are document elements which allow clicking different areas of an image to reference different network resources, as specified byUniform Identifier (URIs). The image map capability in HTML/2.0 is limited in several ways, such as the restriction that it only works with documents served via the "HTTP" protocol, and the lack of a viable fallback for users of text-only browsers. This document specifies an extension to the HTML language, referred to as "Client-Side Image Maps," which resolves these limitations.
 
RFC 1981 Path MTU Discovery for IP version 6
 
Authors:J. McCann, S. Deering, J. Mogul.
Date:August 1996
Formats:txt pdf
Obsoleted by:RFC 8201
Status:DRAFT STANDARD
DOI:10.17487/RFC 1981
This document describes Path MTU Discovery for IP version 6. It is largely derived from RFC 1191, which describes Path MTU Discovery forIP version 4.
 
RFC 1991 PGP Message Exchange Formats
 
Authors:D. Atkins, W. Stallings, P. Zimmermann.
Date:August 1996
Formats:txt pdf
Obsoleted by:RFC 4880
Status:INFORMATIONAL
DOI:10.17487/RFC 1991
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.
 
RFC 2000 Internet Official Protocol Standards
 
Authors:J. Postel, Ed..
Date:February 1997
Formats:txt pdf
Obsoletes:RFC 1920
Obsoleted by:RFC 2200
Status:HISTORIC
DOI:10.17487/RFC 2000
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.
 
RFC 2001 TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms
 
Authors:W. Stevens.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 2581
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2001
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. [2] and [3] provide some details on these algorithms, [4] provides examples of the algorithms in action, and [5] provides the source code for the 4.4BSD implementation. RFC 1122 requires that a TCP must implement slow start and congestion avoidance (Section 4.2.2.15 of [1]), citing [2] as the reference, but fast retransmit and fast recovery were implemented after RFC 1122. The purpose of this document is to document these four algorithms for the Internet.
 
RFC 2002 IP Mobility Support
 
Authors:C. Perkins, Ed..
Date:October 1996
Formats:txt pdf
Obsoleted by:RFC 3220
Updated by:RFC 2290
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2002
This document specifies protocol enhancements that allow transparent routing of IP datagrams to mobile nodes in the Internet. Each mobile node is always identified by its home address, regardless of its current point of attachment to the Internet. While situated away from its home, a mobile node is also associated with a care-of address, which provides information about its current point of attachment to the Internet. The protocol provides for registering the care-of address with a home agent. The home agent sends datagrams destined for the mobile node through a tunnel to the care- of address. After arriving at the end of the tunnel, each datagram is then delivered to the mobile node.
 
RFC 2010 Operational Criteria for Root Name Servers
 
Authors:B. Manning, P. Vixie.
Date:October 1996
Formats:txt pdf
Obsoleted by:RFC 2870
Status:INFORMATIONAL
DOI:10.17487/RFC 2010
This document specifies the operational requirements of root name servers, including host hardware capacities, name server software revisions, network connectivity, and physical environment.
 
RFC 2011 SNMPv2 Management Information Base for the Internet Protocol using SMIv2
 
Authors:K. McCloghrie, Ed..
Date:November 1996
Formats:txt pdf
Obsoleted by:RFC 4293
Updates:RFC 1213
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2011
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]
 
RFC 2012 SNMPv2 Management Information Base for the Transmission Control Protocol using SMIv2
 
Authors:K. McCloghrie, Ed..
Date:November 1996
Formats:txt pdf
Obsoleted by:RFC 4022
Updates:RFC 1213
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2012
This document is the MIB module which defines managed objects for managing implementations of the Transmission Control Protocol (TCP). [STANDARDS-TRACK]
 
RFC 2013 SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2
 
Authors:K. McCloghrie, Ed..
Date:November 1996
Formats:txt pdf
Obsoleted by:RFC 4113
Updates:RFC 1213
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2013
This document is the MIB module which defines managed objects for managing implementations of the User Datagram Protocol (UDP). [STANDARDS-TRACK]
 
RFC 2019 Transmission of IPv6 Packets Over FDDI
 
Authors:M. Crawford.
Date:October 1996
Formats:txt pdf
Obsoleted by:RFC 2467
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2019
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]
 
RFC 2021 Remote Network Monitoring Management Information Base Version 2 using SMIv2
 
Authors:S. Waldbusser.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 4502
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2021
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.
 
RFC 2023 IP Version 6 over PPP
 
Authors:D. Haskin, E. Allen.
Date:October 1996
Formats:txt pdf
Obsoleted by:RFC 2472
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2023
The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols.

This document defines the 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. It also specifies the method of forming IPv6 link-local addresses on PPP links.

 
RFC 2027 IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees
 
Authors:J. Galvin.
Date:October 1996
Formats:txt pdf
Obsoleted by:RFC 2282
Status:INFORMATIONAL
DOI:10.17487/RFC 2027
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.
 
RFC 2030 Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI
 
Authors:D. Mills.
Date:October 1996
Formats:txt pdf
Obsoletes:RFC 1769
Obsoleted by:RFC 4330
Status:INFORMATIONAL
DOI:10.17487/RFC 2030
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. SNTP can be used when the ultimate performance of the full NTP implementation described in RFC-1305 is not needed or justified. When operating with current and previous NTP and SNTP versions, SNTP Version 4 involves no changes to the NTP specification or known implementations, but rather a clarification of certain design features of NTP which allow operation in a simple, stateless remote-procedure call (RPC) mode with accuracy and reliability expectations similar to the UDP/TIME protocol described in RFC-868.

The only significant protocol change in SNTP Version 4 over previous versions of NTP and SNTP is a modified header interpretation to accommodate Internet Protocol Version 6 (IPv6) [DEE96] and OSI[COL94] addressing. However, SNTP Version 4 includes certain optional extensions to the basic Version 3 model, including an anycast mode and an authentication scheme designed specifically for multicast and anycast modes. While the anycast mode extension is described in this document, the authentication scheme extension will be described in another document to be published later. Until such time that a definitive specification is published, these extensions should be considered provisional.

This memorandum obsoletes RFC-1769, which describes SNTP Version 3.Its purpose is to correct certain inconsistencies in the previous document and to clarify header formats and protocol operations for current NTP Version 3 (IPv4) and proposed NTP Version 4 (IPv6 andOSI), which are also used for SNTP. A working knowledge of the NTPVersion 3 specification RFC-1305 is not required for an implementation of SNTP.

 
RFC 2032 RTP Payload Format for H.261 Video Streams
 
Authors:T. Turletti, C. Huitema.
Date:October 1996
Formats:txt pdf
Obsoleted by:RFC 4587
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2032
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]
 
RFC 2035 RTP Payload Format for JPEG-compressed Video
 
Authors:L. Berc, W. Fenner, R. Frederick, S. McCanne.
Date:October 1996
Formats:txt pdf
Obsoleted by:RFC 2435
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2035
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.

This document is a product of the Audio-Video Transport working group within the Internet Engineering Task Force. Comments are solicited and should be addressed to the working group's mailing list at rem- conf@es.net and/or the author(s).

 
RFC 2037 Entity MIB using SMIv2
 
Authors:K. McCloghrie, A. Bierman.
Date:October 1996
Formats:txt pdf
Obsoleted by:RFC 2737
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2037
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]
 
RFC 2038 RTP Payload Format for MPEG1/MPEG2 Video
 
Authors:D. Hoffman, G. Fernando, V. Goyal.
Date:October 1996
Formats:txt pdf
Obsoleted by:RFC 2250
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2038
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. Two approaches are described. The first is designed to support maximum interoperability with MPEG System environments. The second is designed to provide maximum compatibility with other RTP-encapsulated media streams and future conference control work of the IETF.
 
RFC 2044 UTF-8, a transformation format of Unicode and ISO 10646
 
Authors:F. Yergeau.
Date:October 1996
Formats:txt pdf
Obsoleted by:RFC 2279
Status:INFORMATIONAL
DOI:10.17487/RFC 2044
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. 16-bit characters, however, are not compatible with many current applications and protocols, and this has led to the development of a few so-called UCS transformation formats (UTF), each with different characteristics. UTF-8, the object of this memo, has the characteristic of preserving the full US-ASCII range: US-ASCII characters are encoded in one octet having the usual US-ASCII value, and any octet with such a value can only be an US-ASCII character.This provides compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values.
 
RFC 2048 Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
 
Authors:N. Freed, J. Klensin, J. Postel.
Date:November 1996
Formats:txt pdf
Obsoletes:RFC 1521, RFC 1522, RFC 1590
Obsoleted by:RFC 4288, RFC 4289
Updated by:RFC 3023
Status:BEST CURRENT PRACTICE
DOI:10.17487/RFC 2048
STD 11, RFC 822, defines a message representation protocol specifying considerable detail about US-ASCII message headers, and leaves the message content, or message body, as flat US-ASCII text. This set of documents, collectively called the Multipurpose Internet MailExtensions, or MIME, redefines the format of messages to allow for

(1) textual message bodies in character sets other thanUS-ASCII,

(2) an extensible set of different formats for non-textual message bodies,

(3) multi-part message bodies, and

(4) textual header information in character sets other thanUS-ASCII.

These documents are based on earlier work documented in RFC 934, STD11, and RFC 1049, but extends and revises them. Because RFC 822 said so little about message bodies, these documents are largely orthogonal to (rather than a revision of) RFC 822.

This fourth document, RFC 2048, specifies various IANA registration procedures for the following MIME facilities:

(1) media types,

(2) external body access types,

(3) content-transfer-encodings.

Registration of character sets for use in MIME is covered elsewhere and is no longer addressed by this document.

These documents are revisions of RFCs 1521 and 1522, which themselves were revisions of RFCs 1341 and 1342. An appendix in RFC 2049 describes differences and changes from previous versions.

 
RFC 2050 Internet Registry IP Allocation Guidelines
 
Authors:K. Hubbard, M. Kosters, D. Conrad, D. Karrenberg, J. Postel.
Date:November 1996
Formats:txt pdf
Obsoletes:RFC 1466
Obsoleted by:RFC 7020
Status:HISTORIC
DOI:10.17487/RFC 2050
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 describes the IP assignment policies currently used by the Regional Registries to implement the guidelines developed by theIANA. The guidelines and these policies are subject to revision at the direction of the IANA. The registry working group (IRE WG) will be discussing these issues and may provide advice to the IANA about possible revisions.

This document replaces RFC 1466, with all the guidelines and procedures updated and modified in the light of experience.

This document does not describe private Internet address space and multicast address space. It also does not describe regional and local refinements of the global rules and guidelines.

This document can be considered the base set of operational guidelines in use by all registries. Additional guidelines may be imposed by a particular registry as appropriate.

 
RFC 2052 A DNS RR for specifying the location of services (DNS SRV)
 
Authors:A. Gulbrandsen, P. Vixie.
Date:October 1996
Formats:txt pdf
Obsoleted by:RFC 2782
Status:EXPERIMENTAL
DOI:10.17487/RFC 2052
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).
 
RFC 2058 Remote Authentication Dial In User Service (RADIUS)
 
Authors:C. Rigney, A. Rubens, W. Simpson, S. Willens.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 2138
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2058
This document describes a protocol for carrying authentication, authorization, and configuration information between a Network AccessServer which desires to authenticate its links and a sharedAuthentication Server.
 
RFC 2059 RADIUS Accounting
 
Authors:C. Rigney.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 2139
Status:INFORMATIONAL
DOI:10.17487/RFC 2059
This document describes a protocol for carrying accounting information between a Network Access Server and a shared AccountingServer.
 
RFC 2060 Internet Message Access Protocol - Version 4rev1
 
Authors:M. Crispin.
Date:December 1996
Formats:txt pdf
Obsoletes:RFC 1730
Obsoleted by:RFC 3501
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2060
The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1) allows a client to access and manipulate electronic mail messages on a server. IMAP4rev1 permits manipulation of remote message folders, called "mailboxes", in a way that is functionally equivalent to local mailboxes. IMAP4rev1 also provides the capability for an offline client to resynchronize with the server (see also [IMAP-DISC]).

IMAP4rev1 includes operations for creating, deleting, and renaming mailboxes; checking for new messages; permanently removing messages; setting and clearing flags; [RFC-822] and [MIME-IMB] parsing; searching; and selective fetching of message attributes, texts, and portions thereof. Messages in IMAP4rev1 are accessed by the use of numbers. These numbers are either message sequence numbers or unique identifiers.

IMAP4rev1 supports a single server. A mechanism for accessing configuration information to support multiple IMAP4rev1 servers is discussed in [ACAP].

IMAP4rev1 does not specify a means of posting mail; this function is handled by a mail transfer protocol such as [SMTP].

IMAP4rev1 is designed to be upwards compatible from the [IMAP2] and unpublished IMAP2bis protocols. In the course of the evolution ofIMAP4rev1, some aspects in the earlier protocol have become obsolete.Obsolete commands, responses, and data formats which an IMAP4rev1 implementation may encounter when used with an earlier implementation are described in [IMAP-OBSOLETE].

Other compatibility issues with IMAP2bis, the most common variant of the earlier protocol, are discussed in [IMAP-COMPAT]. A full discussion of compatibility issues with rare (and presumed extinct) variants of [IMAP2] is in [IMAP-HISTORICAL]; this document is primarily of historical interest.

 
RFC 2063 Traffic Flow Measurement: Architecture
 
Authors:N. Brownlee, C. Mills, G. Ruth.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 2722
Status:EXPERIMENTAL
DOI:10.17487/RFC 2063
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. It is intended to provide a starting point for the Realtime Traffic Flow Measurement Working Group.
 
RFC 2064 Traffic Flow Measurement: Meter MIB
 
Authors:N. Brownlee.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 2720
Status:EXPERIMENTAL
DOI:10.17487/RFC 2064
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.
 
RFC 2065 Domain Name System Security Extensions
 
Authors:D. Eastlake 3rd, C. Kaufman.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 2535
Updates:RFC 1034, RFC 1035
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2065
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. These digital signatures are included in secured zones as resource records. Security can still be provided even through non-security aware DNS servers in many cases.

The extensions also provide for the storage of authenticated public keys in the DNS. This storage of keys can support general public key distribution service as well as DNS security. The stored keys enable security aware resolvers to learn the authenticating key of zones in addition to those for which they are initially configured. Keys associated with DNS names can be retrieved to support other protocols. Provision is made for a variety of key types and algorithms.

In addition, the security extensions provide for the optional authentication of DNS protocol transactions.

 
RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1
 
Authors:R. Fielding, J. Gettys, J. Mogul, H. Frystyk, T. Berners-Lee.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 2616
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2068
The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, object-oriented protocol which can be used for many tasks, such as name servers and distributed object management systems, through extension of its request methods.A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred.

HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as "HTTP/1.1".

 
RFC 2069 An Extension to HTTP : Digest Access Authentication
 
Authors:J. Franks, P. Hallam-Baker, J. Hostetler, P. Leach, A. Luotonen, E. Sink, L. Stewart.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 2617
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2069
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". Like Basic,Digest access authentication verifies that both parties to a communication know a shared secret (a password); unlike Basic, this verification can be done without sending the password in the clear, which is Basic's biggest weakness. As with most other authentication protocols, the greatest sources of risks are usually found not in the core protocol itself but in policies and procedures surrounding its use.
 
RFC 2070 Internationalization of the Hypertext Markup Language
 
Authors:F. Yergeau, G. Nicol, G. Adams, M. Duerst.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 2854
Status:HISTORIC
DOI:10.17487/RFC 2070
The Hypertext Markup Language (HTML) is a markup language used to create hypertext documents that are platform independent. Initially, the application of HTML on the World Wide Web was seriously restricted by its reliance on the ISO-8859-1 coded character set, which is appropriate only for Western European languages. Despite this restriction, HTML has been widely used with other languages, using other coded character sets or character encodings, at the expense of interoperability.

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. A foremost consideration is to make sure that HTML remains a valid application of SGML, while enabling its use with all languages of the world.

 
RFC 2073 An IPv6 Provider-Based Unicast Address Format
 
Authors:Y. Rekhter, P. Lothberg, R. Hinden, S. Deering, J. Postel.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 2374
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2073
This document defines an IPv6 provider-based unicast address format for use in the Internet. [STANDARDS-TRACK]
 
RFC 2074 Remote Network Monitoring MIB Protocol Identifiers
 
Authors:A. Bierman, R. Iddon.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 2895
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2074
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]
 
RFC 2078 Generic Security Service Application Program Interface, Version 2
 
Authors:J. Linn.
Date:January 1997
Formats:txt pdf
Obsoletes:RFC 1508
Obsoleted by:RFC 2743
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2078
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. This specification definesGSS-API services and primitives at a level independent of underlying mechanism and programming language environment, and is to be complemented by other, related specifications: documents defining specific parameter bindings for particular language environments documents defining token formats, protocols, and procedures to be implemented in order to realize GSS-API services atop particular security mechanisms

This memo revises RFC-1508, making specific, incremental changes in response to implementation experience and liaison requests. It is intended, therefore, that this memo or a successor version thereto will become the basis for subsequent progression of the GSS-API specification on the standards track.

 
RFC 2082 RIP-2 MD5 Authentication
 
Authors:F. Baker, R. Atkinson.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 4822
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2082
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]
 
RFC 2086 IMAP4 ACL extension
 
Authors:J. Myers.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 4314
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2086
The ACL extension of the Internet Message Access Protocol [IMAP4] permits access control lists to be manipulated through the IMAP protocol. [STANDARDS-TRACK]
 
RFC 2088 IMAP4 non-synchronizing literals
 
Authors:J. Myers.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 7888
Updated by:RFC 4466
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2088
The Internet Message Access Protocol [IMAP4] contains the "literal" syntactic construct for communicating strings. When sending a literal from client to server, IMAP4 requires the client to wait for the server to send a command continuation request between sending the octet count and the string data. This document specifies an alternate form of literal which does not require this network round trip. [STANDARDS- TRACK]
 
RFC 2089 V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent
 
Authors:B. Wijnen, D. Levi.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 2576
Status:INFORMATIONAL
DOI:10.17487/RFC 2089
The goal of this memo is to document a common way of mapping anSNMPv2 response into an SNMPv1 response within a bi-lingual SNMP agent (one that supports both SNMPv1 and SNMPv2).
 
RFC 2095 IMAP/POP AUTHorize Extension for Simple Challenge/Response
 
Authors:J. Klensin, R. Catoe, P. Krumviede.
Date:January 1997
Formats:txt pdf
Obsoleted by:RFC 2195
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2095
While IMAP4 supports a number of strong authentication mechanisms as described in RFC 1731, it lacks any mechanism that neither passes cleartext, reusable passwords across the network nor requires either a significant security infrastructure or that the mail server update a mail-system-wide user authentication file on each mail access.This specification provides a simple challenge-response authentication protocol that is suitable for use with IMAP4. Since it utilizes Keyed-MD5 digests and does not require that the secret be stored in the clear on the server, it may also constitute an improvement on APOP for POP3 use as specified in RFC 1734.
 
RFC 2096 IP Forwarding Table MIB
 
Authors:F. Baker.
Date:January 1997
Formats:txt pdf
Obsoletes:RFC 1354
Obsoleted by:RFC 4292
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2096
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]
 
RFC 2106 Data Link Switching Remote Access Protocol
 
Authors:S. Chiang, J. Lee, H. Yasuda.
Date:February 1997
Formats:txt pdf
Obsoleted by:RFC 2114
Status:INFORMATIONAL
DOI:10.17487/RFC 2106
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. Any questions or comments should be sent to drap@cisco.com.
 
RFC 2109 HTTP State Management Mechanism
 
Authors:D. Kristol, L. Montulli.
Date:February 1997
Formats:txt pdf
Obsoleted by:RFC 2965
Status:HISTORIC
DOI:10.17487/RFC 2109
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]
 
RFC 2110 MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)
 
Authors:J. Palme, A. Hopmann.
Date:March 1997
Formats:txt pdf
Obsoleted by:RFC 2557
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2110
Although HTML [RFC 1866] was designed within the context of MIME, more than the specification of HTML as defined in RFC 1866 is needed for two electronic mail user agents to be able to interoperate usingHTML as a document format. These issues include the naming of objects that are normally referred to by URIs, and the means of aggregating objects that go together. 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. In order to be able to handle inter-linked objects, the document uses the MIME type multipart/related and specifies the MIME content-headers "Content-Location" and "Content-Base".
 
RFC 2111 Content-ID and Message-ID Uniform Resource Locators
 
Authors:E. Levinson.
Date:March 1997
Formats:txt pdf
Obsoleted by:RFC 2392
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2111
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.
 
RFC 2112 The MIME Multipart/Related Content-type
 
Authors:E. Levinson.
Date:March 1997
Formats:txt pdf
Obsoletes:RFC 1872
Obsoleted by:RFC 2387
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2112
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.
 
RFC 2117 Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification
 
Authors:D. Estrin, D. Farinacci, A. Helmy, D. Thaler, S. Deering, M. Handley, V. Jacobson, C. Liu, P. Sharma, L. Wei.
Date:June 1997
Formats:txt pdf
Obsoleted by:RFC 2362
Status:EXPERIMENTAL
DOI:10.17487/RFC 2117
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.
 
RFC 2133 Basic Socket Interface Extensions for IPv6
 
Authors:R. Gilligan, S. Thomson, J. Bound, W. Stevens.
Date:April 1997
Formats:txt pdf
Obsoleted by:RFC 2553
Status:INFORMATIONAL
DOI:10.17487/RFC 2133
The de facto standard application program interface (API) for TCP/IP applications is the "sockets" interface. Although this API was developed for Unix in the early 1980s it has also been implemented on a wide variety of non-Unix systems. TCP/IP applications written using the sockets API have in the past enjoyed a high degree of portability and we would like the same portability with IPv6 applications. But changes are required to the sockets API to supportIPv6 and this memo describes these changes. These include a new socket address structure to carry IPv6 addresses, new address conversion functions, and some new socket options. These extensions are designed to provide access to the basic IPv6 features required byTCP and UDP applications, including multicasting, while introducing a minimum of change into the system and providing complete compatibility for existing IPv4 applications. Additional extensions for advanced IPv6 features (raw sockets and access to the IPv6 extension headers) are defined in another document [5].
 
RFC 2137 Secure Domain Name System Dynamic Update
 
Authors:D. Eastlake 3rd.
Date:April 1997
Formats:txt pdf
Obsoleted by:RFC 3007
Updates:RFC 1035
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2137
Domain Name System (DNS) protocol extensions have been defined to authenticate the data in DNS and provide key distribution services[RFC2065]. DNS Dynamic Update operations have also been defined[RFC2136], but without a detailed description of security for the update operation. 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.
 
RFC 2138 Remote Authentication Dial In User Service (RADIUS)
 
Authors:C. Rigney, A. Rubens, W. Simpson, S. Willens.
Date:April 1997
Formats:txt pdf
Obsoletes:RFC 2058
Obsoleted by:RFC 2865
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2138
This document describes a protocol for carrying authentication, authorization, and configuration information between a Network AccessServer which desires to authenticate its links and a sharedAuthentication Server.
 
RFC 2139 RADIUS Accounting
 
Authors:C. Rigney.
Date:April 1997
Formats:txt pdf
Obsoletes:RFC 2059
Obsoleted by:RFC 2866
Status:INFORMATIONAL
DOI:10.17487/RFC 2139
This document describes a protocol for carrying accounting information between a Network Access Server and a shared AccountingServer.
 
RFC 2141 URN Syntax
 
Authors:R. Moats.
Date:May 1997
Formats:txt pdf
Obsoleted by:RFC 8141
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2141
Uniform Resource Names (URNs) are intended to serve as persistent, location-independent, resource identifiers. This document sets forward the canonical syntax for URNs. A discussion of both existing legacy and new namespaces and requirements for URN presentation and transmission are presented. Finally, there is a discussion of URN equivalence and how to determine it.
 
RFC 2145 Use and Interpretation of HTTP Version Numbers
 
Authors:J. C. Mogul, R. Fielding, J. Gettys, H. Frystyk.
Date:May 1997
Formats:txt pdf
Obsoleted by:RFC 7230
Status:INFORMATIONAL
DOI:10.17487/RFC 2145
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. It is not a modification of the intended meaning of the existingHTTP/1.0 and HTTP/1.1 documents, but it does describe the intention of the authors of those documents, and can be considered definitive when there is any ambiguity in those documents concerning HTTP version numbers, for all versions of HTTP.
 
RFC 2147 TCP and UDP over IPv6 Jumbograms
 
Authors:D. Borman.
Date:May 1997
Formats:txt pdf
Obsoleted by:RFC 2675
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2147
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]
 
RFC 2155 Definitions of Managed Objects for APPN using SMIv2
 
Authors:B. Clouston, B. Moore.
Date:June 1997
Formats:txt pdf
Obsoleted by:RFC 2455
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2155
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]
 
RFC 2168 Resolution of Uniform Resource Identifiers using the Domain Name System
 
Authors:R. Daniel, M. Mealling.
Date:June 1997
Formats:txt pdf
Obsoleted by:RFC 3401, RFC 3402, RFC 3403, RFC 3404
Updated by:RFC 2915
Status:EXPERIMENTAL
DOI:10.17487/RFC 2168
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.
 
RFC 2178 OSPF Version 2
 
Authors:J. Moy.
Date:July 1997
Formats:txt pdf
Obsoletes:RFC 1583
Obsoleted by:RFC 2328
Status:DRAFT STANDARD
DOI:10.17487/RFC 2178
This memo documents version 2 of the OSPF protocol. OSPF is a link- state routing protocol. It is designed to be run internal to a single Autonomous System. Each OSPF router maintains an identical database describing the Autonomous System's topology. From this database, a routing table is calculated by constructing a shortest- path tree.

OSPF recalculates routes quickly in the face of topological changes, utilizing a minimum of routing protocol traffic. OSPF provides support for equal-cost multipath. An area routing capability is provided, enabling an additional level of routing protection and a reduction in routing protocol traffic. In addition, all OSPF routing protocol exchanges are authenticated.

The differences between this memo and RFC 1583 are explained inAppendix G. All differences are backward-compatible in nature.Implementations of this memo and of RFC 1583 will interoperate.

Please send comments to ospf@gated.cornell.edu.

 
RFC 2184 MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
 
Authors:N. Freed, K. Moore.
Date:August 1997
Formats:txt pdf
Obsoleted by:RFC 2231
Updates:RFC 2045, RFC 2047, RFC 2183
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2184
This memo defines extensions to the RFC 2045 media type and RFC 2183 disposition parameter value mechanisms. [STANDARDS-TRACK]
 
RFC 2192 IMAP URL Scheme
 
Authors:C. Newman.
Date:September 1997
Formats:txt pdf
Obsoleted by:RFC 5092
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2192
IMAP [IMAP4] is a rich protocol for accessing remote message stores. It provides an ideal mechanism for accessing public mailing list archives as well as private and shared message stores.This document defines a URL scheme for referencing objects on anIMAP server.
 
RFC 2197 SMTP Service Extension for Command Pipelining
 
Authors:N. Freed.
Date:September 1997
Formats:txt pdf
Obsoletes:RFC 1854
Obsoleted by:RFC 2920
Status:DRAFT STANDARD
DOI:10.17487/RFC 2197
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]
 
RFC 2200 Internet Official Protocol Standards
 
Authors:J. Postel.
Date:June 1997
Formats:txt pdf
Obsoletes:RFC 1250, RFC 2000
Obsoleted by:RFC 2300
Status:HISTORIC
DOI:10.17487/RFC 2200
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]
 
RFC 2204 ODETTE File Transfer Protocol
 
Authors:D. Nash.
Date:September 1997
Formats:txt pdf
Obsoleted by:RFC 5024
Status:INFORMATIONAL
DOI:10.17487/RFC 2204
This memo describes a file transfer protocol to facilitate electronic data interchange between trading partners.

The protocol, denoted the ODETTE File Transfer Protocol, supports both direct communication between installations and indirect communication via a third party clearing centre. It was developed by the Organisation for Data Exchange by Tele Transmission in Europe to facilitate communication within the European motor industry and is presented here to allow for wider use within the Internet community.

 
RFC 2222 Simple Authentication and Security Layer (SASL)
 
Authors:J. Myers.
Date:October 1997
Formats:txt pdf
Obsoleted by:RFC 4422, RFC 4752
Updated by:RFC 2444
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2222
This document describes a method for adding authentication support to connection-based protocols. [STANDARDS-TRACK]
 
RFC 2223 Instructions to RFC Authors
 
Authors:J. Postel, J. Reynolds.
Date:October 1997
Formats:txt pdf
Obsoletes:RFC 1543, RFC 1111, RFC 0825
Obsoleted by:RFC 7322
Updated by:RFC 5741, RFC 6949
Status:INFORMATIONAL
DOI:10.17487/RFC 2223
This Request for Comments (RFC) provides information about the preparation of RFCs, and certain policies relating to the publication of RFCs. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
 
RFC 2233 The Interfaces Group MIB using SMIv2
 
Authors:K. McCloghrie, F. Kastenholz.
Date:November 1997
Formats:txt pdf
Obsoletes:RFC 1573
Obsoleted by:RFC 2863
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2233
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]
 
RFC 2234 Augmented BNF for Syntax Specifications: ABNF
 
Authors:D. Crocker, Ed., P. Overell.
Date:November 1997
Formats:txt pdf
Obsoleted by:RFC 4234
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2234
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]
 
RFC 2239 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2
 
Authors:K. de Graaf, D. Romascanu, D. McMaster, K. McCloghrie, S. Roberts.
Date:November 1997
Formats:txt pdf
Obsoleted by:RFC 2668
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2239
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/secondMedium Attachment Units (MAUs) based on IEEE Std 802.3 Section 30,"10 & 100 Mb/s Management," October 26, 1995.
 
RFC 2240 A Legal Basis for Domain Name Allocation
 
Authors:O. Vaughan.
Date:November 1997
Formats:txt pdf
Obsoleted by:RFC 2352
Status:INFORMATIONAL
DOI:10.17487/RFC 2240
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.
 
RFC 2245 Anonymous SASL Mechanism
 
Authors:C. Newman.
Date:November 1997
Formats:txt pdf
Obsoleted by:RFC 4505
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2245
It is common practice on the Internet to permit anonymous access to various services. Traditionally, this has been done with a plain text password mechanism using "anonymous" as the user name and optional trace information, such as an email address, as the password. 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.
 
RFC 2246 The TLS Protocol Version 1.0
 
Authors:T. Dierks, C. Allen.
Date:January 1999
Formats:txt pdf
Obsoleted by:RFC 4346
Updated by:RFC 3546, RFC 5746, RFC 6176, RFC 7465, RFC 7507, RFC 7919
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2246
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.
 
RFC 2248 Network Services Monitoring MIB
 
Authors:N. Freed, S. Kille.
Date:January 1998
Formats:txt pdf
Obsoletes:RFC 1565
Obsoleted by:RFC 2788
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2248
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]
 
RFC 2249 Mail Monitoring MIB
 
Authors:N. Freed, S. Kille.
Date:January 1998
Formats:txt pdf
Obsoletes:RFC 1566
Obsoleted by:RFC 2789
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2249
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 [8] to allow monitoring of Message Transfer Agents (MTAs). It may also be used to monitor MTA components within gateways. [STANDARDS- TRACK]
 
RFC 2251 Lightweight Directory Access Protocol (v3)
 
Authors:M. Wahl, T. Howes, S. Kille.
Date:December 1997
Formats:txt pdf
Obsoleted by:RFC 4510, RFC 4511, RFC 4513, RFC 4512
Updated by:RFC 3377, RFC 3771
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2251
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]
 
RFC 2252 Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions
 
Authors:M. Wahl, A. Coulbeck, T. Howes, S. Kille.
Date:December 1997
Formats:txt pdf
Obsoleted by:RFC 4510, RFC 4517, RFC 4523, RFC 4512
Updated by:RFC 3377
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2252
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]
 
RFC 2253 Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names
 
Authors:M. Wahl, S. Kille, T. Howes.
Date:December 1997
Formats:txt pdf
Obsoletes:RFC 1779
Obsoleted by:RFC 4510, RFC 4514
Updated by:RFC 3377
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2253
The X.500 Directory uses distinguished names as the primary keys to entries in the directory. Distinguished Names are encoded in ASN.1 in the X.500 Directory protocols. In the Lightweight DirectoryAccess Protocol, a string representation of distinguished names is transferred. 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.
 
RFC 2254 The String Representation of LDAP Search Filters
 
Authors:T. Howes.
Date:December 1997
Formats:txt pdf
Obsoletes:RFC 1960
Obsoleted by:RFC 4510, RFC 4515
Updated by:RFC 3377
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2254
This document defines a human-readable string format for representing LDAP search filters. [STANDARDS-TRACK]
 
RFC 2255 The LDAP URL Format
 
Authors:T. Howes, M. Smith.
Date:December 1997
Formats:txt pdf
Obsoletes:RFC 1959
Obsoleted by:RFC 4510, RFC 4516
Updated by:RFC 3377
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2255
This document describes a format for an LDAP Uniform Resource Locator. [STANDARDS-TRACK]
 
RFC 2256 A Summary of the X.500(96) User Schema for use with LDAPv3
 
Authors:M. Wahl.
Date:December 1997
Formats:txt pdf
Obsoleted by:RFC 4517, RFC 4519, RFC 4523, RFC 4512, RFC 4510
Updated by:RFC 3377
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2256
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]
 
RFC 2257 Agent Extensibility (AgentX) Protocol Version 1
 
Authors:M. Daniele, B. Wijnen, D. Francisco.
Date:January 1998
Formats:txt pdf
Obsoleted by:RFC 2741
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2257
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]
 
RFC 2261 An Architecture for Describing SNMP Management Frameworks
 
Authors:D. Harrington, R. Presuhn, B. Wijnen.
Date:January 1998
Formats:txt pdf
Obsoleted by:RFC 2271
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2261
This document describes an architecture for describing SNMPManagement Frameworks. The architecture is designed to be modular to allow the evolution of the SNMP protocol standards over time. The major portions of the architecture are an SNMP engine containing aMessage Processing Subsystem, a Security Subsystem and an AccessControl Subsystem, and possibly multiple SNMP applications which provide specific functional processing of management data.
 
RFC 2262 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)
 
Authors:J. Case, D. Harrington, R. Presuhn, B. Wijnen.
Date:January 1998
Formats:txt pdf
Obsoleted by:RFC 2272
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2262
This document describes the Message Processing and Dispatching forSNMP 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.
 
RFC 2263 SNMPv3 Applications
 
Authors:D. Levi, P. Meyer, B. Stewart.
Date:January 1998
Formats:txt pdf
Obsoleted by:RFC 2273
Status:PROPOSED STANDARD
DOI:10.17487/RFC 2263
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, NotificationOriginators, Notification Receivers, and Proxy Forwarders.

This memo also defines MIB modules for specifying targets of management operations, for notification filtering, and for proxy forwarding.