BCP0001 RFC1818 BCP0002 RFC1871 BCP0003 RFC1915 BCP0004 RFC1917 BCP0005 RFC1918 BCP0006 RFC1930 BCP0007 RFC2008 BCP0008 RFC2014 BCP0009 RFC2026 BCP0010 RFC3777 BCP0011 RFC2028 BCP0012 RFC2050 BCP0013 RFC2048 BCP0014 RFC2119 BCP0015 RFC2148 BCP0016 RFC2182 BCP0017 RFC2219 BCP0018 RFC2277 BCP0019 RFC2978 BCP0020 RFC2317 BCP0021 RFC2350 BCP0022 RFC2360 BCP0023 RFC2365 BCP0024 RFC2379 BCP0025 RFC2418 BCP0026 RFC2434 BCP0027 RFC2438 BCP0028 RFC2488 BCP0029 RFC2489 BCP0030 RFC2505 BCP0031 RFC2506 BCP0032 RFC2606 BCP0033 RFC2611 BCP0034 RFC2644 BCP0035 RFC2717 BCP0036 RFC2736 BCP0037 RFC2780 BCP0038 RFC2827 BCP0039 RFC2850 BCP0040 RFC2870 BCP0041 RFC2914 BCP0042 RFC2929 BCP0043 RFC2939 BCP0044 RFC2964 BCP0045 RFC3005 BCP0046 RFC3013 BCP0047 RFC3066 BCP0048 RFC3150 BCP0049 RFC3152 BCP0050 RFC3155 BCP0051 RFC3171 BCP0052 RFC3172 BCP0053 RFC3180 BCP0054 RFC3184 BCP0055 RFC3227 BCP0056 RFC3205 BCP0057 RFC3228 BCP0058 RFC3233 BCP0059 RFC3349 BCP0060 RFC3360 BCP0061 RFC3365 BCP0062 RFC3366 BCP0063 RFC3372 BCP0064 RFC3383 BCP0065 RFC3405 BCP0066 RFC3406 BCP0067 RFC3427 BCP0068 RFC3438 BCP0069 RFC3449 BCP0070 RFC3470 BCP0071 RFC3481 BCP0072 RFC3552 BCP0073 RFC3553 BCP0074 RFC3584 BCP0075 RFC3665 BCP0076 RFC3666 BCP0077 RFC3677 BCP0078 RFC3978 BCP0079 RFC3979 BCP0080 RFC3681 BCP0081 RFC3688 BCP0082 RFC3692 BCP0083 RFC3683 BCP0084 RFC3704 BCP0085 RFC3725 BCP0086 RFC3766 BCP0087 RFC3785 BCP0088 RFC3818 BCP0089 RFC3819 BCP0090 RFC3864 BCP0091 RFC3901 BCP0092 RFC3932 BCP0093 RFC3933 BCP0094 RFC3934 BCP0095 RFC3935 BCP0096 RFC3936 BCP0097 RFC3967 BCP0098 RFC3968 BCP0099 RFC3969 BCP0100 RFC4020 BCP0101 RFC4071 BCP0102 RFC4052 BCP0103 RFC4053 BCP0104 RFC4084 FYI0001 RFC1150 FYI0002 RFC1470 FYI0003 RFC1175 FYI0004 RFC2664 FYI0005 RFC1178 FYI0006 RFC1198 FYI0007 RFC1207 FYI0008 RFC2196 FYI0009 RFC1336 FYI0010 RFC1402 FYI0011 RFC2116 FYI0012 RFC1302 FYI0013 RFC1308 FYI0014 RFC1309 FYI0015 RFC1355 FYI0016 RFC1359 FYI0017 RFC3160 FYI0018 RFC1983 FYI0019 RFC1463 FYI0020 RFC1462 FYI0021 RFC1491 FYI0022 RFC1941 FYI0023 RFC1580 FYI0024 RFC1635 FYI0025 RFC1689 FYI0026 RFC1709 FYI0027 RFC1713 FYI0028 RFC1855 FYI0029 RFC2007 FYI0030 RFC2151 FYI0031 RFC2150 FYI0032 RFC2235 FYI0033 RFC2398 FYI0034 RFC2504 FYI0035 RFC2635 FYI0036 RFC2828 FYI0037 RFC2901 FYI0038 RFC3098 RFC0001 Host Software S. Crocker April 07 1969 ASCII 21088 11 UNKNOWN UNKNOWN RFC0002 Host software B. Duvall April 09 1969 ASCII 17145 10 UNKNOWN UNKNOWN RFC0003 Documentation conventions S.D. Crocker April 09 1969 ASCII 2323 2 RFC0010 UNKNOWN UNKNOWN RFC0004 Network timetable E.B. Shapiro March 24 1969 ASCII 5933 6 UNKNOWN UNKNOWN RFC0005 Decode Encode Language (DEL) J. Rulifson June 02 1969 ASCII 26408 17 UNKNOWN UNKNOWN RFC0006 Conversation with Bob Kahn S.D. Crocker April 10 1969 ASCII 1568 1 UNKNOWN UNKNOWN RFC0007 Host-IMP interface G. Deloche May 01 1969 ASCII 13408 7 UNKNOWN UNKNOWN RFC0008 Functional specifications for the ARPA Network G. Deloche May 05 1969 Not Available Online. UNKNOWN UNKNOWN RFC0009 Host software G. Deloche May 01 1969 Not Available Online. UNKNOWN UNKNOWN RFC0010 Documentation conventions S.D. Crocker July 29 1969 ASCII 3348 3 RFC0003 RFC0016 RFC0024 RFC0027 RFC0030 UNKNOWN UNKNOWN RFC0011 Implementation of the Host-Host software procedures in GORDO G. Deloche August 01 1969 Not Available Online. RFC0033 UNKNOWN UNKNOWN RFC0012 IMP-Host interface flow diagrams M. Wingfield August 26 1969 ASCII 177 1 PS 1489750 PDF 1163721 UNKNOWN UNKNOWN RFC0013 Zero Text Length EOF Message V. Cerf August 20 1969 ASCII 1070 1 Referring to NWG/RFC 11. UNKNOWN UNKNOWN RFC0014 RFC0015 Network subsystem for time sharing hosts C.S. Carr September 25 1969 ASCII 10695 5 UNKNOWN UNKNOWN RFC0016 M.I.T S. Crocker August 27 1969 ASCII 682 1 RFC0010 RFC0024 RFC0024 RFC0027 RFC0030 UNKNOWN UNKNOWN RFC0017 Some questions re: Host-IMP Protocol J.E. Kreznar August 27 1969 ASCII 6065 4 17a Follows UNKNOWN UNKNOWN RFC0018 IMP-IMP and HOST-HOST Control Links V. Cerf September 01 1969 ASCII 634 1 UNKNOWN UNKNOWN RFC0019 Two protocol suggestions to reduce congestion at swap bound nodes J.E. Kreznar October 07 1969 ASCII 3392 2 UNKNOWN UNKNOWN RFC0020 ASCII format for network interchange V.G. Cerf October 16 1969 ASCII 18504 9 UNKNOWN UNKNOWN RFC0021 Network meeting V.G. Cerf October 17 1969 ASCII 2143 2 UNKNOWN UNKNOWN RFC0022 Host-host control message formats V.G. Cerf October 17 1969 ASCII 4606 2 UNKNOWN UNKNOWN RFC0023 Transmission of Multiple Control Messages G. Gregg October 16 1969 ASCII 690 1 UNKNOWN UNKNOWN RFC0024 Documentation Conventions S.D. Crocker November 21 1969 ASCII 3460 3 RFC0016 RFC0010 RFC0016 RFC0027 RFC0030 UNKNOWN UNKNOWN RFC0025 No High Link Numbers S.D. Crocker October 30 1969 ASCII 479 1 UNKNOWN UNKNOWN RFC0026 RFC0027 Documentation Conventions S.D. Crocker December 09 1969 ASCII 3661 3 RFC0010 RFC0016 RFC0024 RFC0030 UNKNOWN UNKNOWN RFC0028 Time Standards W.K. English January 13 1970 ASCII 557 1 UNKNOWN UNKNOWN RFC0029 Response to RFC 28 R.E. Kahn January 19 1970 ASCII 790 1 RFC0028 UNKNOWN UNKNOWN RFC0030 Documentation Conventions S.D. Crocker February 04 1970 ASCII 4041 3 RFC0010 RFC0016 RFC0024 RFC0027 UNKNOWN UNKNOWN RFC0031 Binary Message Forms in Computer D. Bobrow W.R. Sutherland February 01 1968 ASCII 11191 7 UNKNOWN UNKNOWN RFC0032 Some Thoughts on SRI's Proposed Real Time Clock J. Cole February 05 1970 ASCII 2216 1 UNKNOWN UNKNOWN RFC0033 New Host-Host Protocol S.D. Crocker February 12 1970 ASCII 44167 19 RFC0011 RFC0036 RFC0047 UNKNOWN UNKNOWN RFC0034 Some Brief Preliminary Notes on the Augmentation Research Center Clock W.K. English February 26 1970 ASCII 2534 2 UNKNOWN UNKNOWN RFC0035 Network Meeting S.D. Crocker March 03 1970 ASCII 1282 1 INFORMATIONAL INFORMATIONAL RFC0036 Protocol Notes S.D. Crocker March 16 1970 ASCII 13893 8 RFC0033 RFC0039 RFC0044 UNKNOWN UNKNOWN RFC0037 Network Meeting Epilogue, etc S.D. Crocker March 20 1970 ASCII 9107 5 UNKNOWN UNKNOWN RFC0038 Comments on Network Protocol from NWG/RFC #36 S.M. Wolfe March 20 1970 ASCII 2536 1 UNKNOWN UNKNOWN RFC0039 Comments on Protocol Re: NWG/RFC #36 E. Harslem J.F. Heafner March 25 1970 ASCII 4779 3 RFC0036 UNKNOWN UNKNOWN RFC0040 More Comments on the Forthcoming Protocol E. Harslem J.F. Heafner March 27 1970 ASCII 3825 3 UNKNOWN UNKNOWN RFC0041 IMP-IMP Teletype Communication J.T. Melvin March 30 1970 ASCII 1038 1 UNKNOWN UNKNOWN RFC0042 Message Data Types E. Ancona March 31 1970 ASCII 5247 3 UNKNOWN UNKNOWN RFC0043 Proposed Meeting A.G. Nemeth April 08 1970 ASCII 1600 2 UNKNOWN UNKNOWN RFC0044 Comments on NWG/RFC 33 and 36 A. Shoshani R. Long A. Landsberg April 10 1970 ASCII 7381 3 RFC0036 UNKNOWN UNKNOWN RFC0045 New Protocol is Coming J. Postel S.D. Crocker April 14 1970 ASCII 1130 1 UNKNOWN UNKNOWN RFC0046 ARPA Network protocol notes E. Meyer April 17 1970 ASCII 41338 17 UNKNOWN UNKNOWN RFC0047 BBN's Comments on NWG/RFC #33 J. Postel S. Crocker April 20 1970 ASCII 5343 4 RFC0033 UNKNOWN UNKNOWN RFC0048 Possible protocol plateau J. Postel S.D. Crocker April 21 1970 ASCII 41696 18 UNKNOWN UNKNOWN RFC0049 Conversations with S. Crocker (UCLA) E. Meyer April 25 1970 ASCII 12384 5 UNKNOWN UNKNOWN RFC0050 Comments on the Meyer Proposal E. Harslen J. Heafner April 30 1970 ASCII 4070 2 UNKNOWN UNKNOWN RFC0051 Proposal for a Network Interchange Language M. Elie May 04 1970 Not Available Online UNKNOWN UNKNOWN RFC0052 Updated distribution list J. Postel S.D. Crocker July 01 1970 ASCII 5088 3 RFC0069 UNKNOWN UNKNOWN RFC0053 Official protocol mechanism S.D. Crocker June 09 1970 ASCII 2330 1 UNKNOWN UNKNOWN RFC0054 Official Protocol Proffering S.D. Crocker J. Postel J. Newkirk M. Kraley June 18 1970 ASCII 20131 9 RFC0057 UNKNOWN UNKNOWN RFC0055 Prototypical implementation of the NCP J. Newkirk M. Kraley J. Postel S.D. Crocker June 19 1970 ASCII 48070 23 UNKNOWN UNKNOWN RFC0056 Third Level Protocol: Logger Protocol E. Belove D. Black R. Flegal L.G. Farquar June 01 1970 ASCII 13066 6 UNKNOWN UNKNOWN RFC0057 Thoughts and Reflections on NWG/RFC 54 M. Kraley J. Newkirk June 19 1970 ASCII 8360 5 RFC0054 UNKNOWN UNKNOWN RFC0058 Logical Message Synchronization T.P. Skinner June 26 1970 ASCII 3767 2 UNKNOWN UNKNOWN RFC0059 Flow Control - Fixed Versus Demand Allocation E. Meyer June 27 1970 ASCII 17691 7 UNKNOWN UNKNOWN RFC0060 Simplified NCP Protocol R.B. Kalin July 13 1970 ASCII 18941 8 UNKNOWN UNKNOWN RFC0061 Note on Interprocess Communication in a Resource Sharing Computer Network D.C. Walden July 17 1970 ASCII 43946 18 RFC0062 UNKNOWN UNKNOWN RFC0062 Systems for Interprocess Communication in a Resource Sharing Computer Network D.C. Walden August 03 1970 ASCII 55784 20 RFC0061 UNKNOWN UNKNOWN RFC0063 Belated Network Meeting Report V.G. Cerf July 31 1970 ASCII 2961 2 UNKNOWN UNKNOWN RFC0064 Getting rid of marking M. Elie July 01 1970 ASCII 7556 4 UNKNOWN UNKNOWN RFC0065 Comments on Host/Host Protocol document #1 D.C. Walden August 29 1970 ASCII 5628 2 UNKNOWN UNKNOWN RFC0066 NIC - third level ideas and other noise S.D. Crocker August 26 1970 ASCII 4575 3 RFC0123 RFC0080 RFC0093 UNKNOWN UNKNOWN RFC0067 Proposed Change to Host/IMP Spec to Eliminate Marking W.R. Crowther January 01 1970 ASCII 1534 1 UNKNOWN UNKNOWN RFC0068 Comments on Memory Allocation Control Commands: CEASE, ALL, GVB, RET, and RFNM M. Elie August 31 1970 ASCII 5041 2 UNKNOWN UNKNOWN RFC0069 Distribution List Change for MIT A.K. Bhushan September 22 1970 ASCII 841 1 RFC0052 UNKNOWN UNKNOWN RFC0070 Note on Padding S.D. Crocker October 15 1970 ASCII 12790 9 RFC0228 UNKNOWN UNKNOWN RFC0071 Reallocation in Case of Input Error T. Schipper September 25 1970 ASCII 1265 1 UNKNOWN UNKNOWN RFC0072 Proposed Moratorium on Changes to Network Protocol R.D. Bressler September 28 1970 ASCII 4047 4 UNKNOWN UNKNOWN RFC0073 Response to NWG/RFC 67 S.D. Crocker September 25 1970 ASCII 1268 1 UNKNOWN UNKNOWN RFC0074 Specifications for network use of the UCSB On-Line System J.E. White October 16 1970 Not Available Online RFC0217 RFC0225 UNKNOWN UNKNOWN RFC0075 Network Meeting S.D. Crocker October 14 1970 ASCII 1318 1 UNKNOWN UNKNOWN RFC0076 Connection by name: User oriented protocol J. Bouknight J. Madden G.R. Grossman October 28 1970 ASCII 26504 15 UNKNOWN UNKNOWN RFC0077 Network meeting report J. Postel November 20 1970 ASCII 19196 9 UNKNOWN UNKNOWN RFC0078 NCP Status Report: UCSB/Rand E. Harslem J.F. Heafner J.E. White October 01 1970 ASCII 1303 1 UNKNOWN UNKNOWN RFC0079 Logger Protocol error E. Meyer November 16 1970 ASCII 1515 1 UNKNOWN UNKNOWN RFC0080 Protocols and Data Formats E. Harslem J.F. Heafner December 01 1970 ASCII 17620 9 RFC0123 RFC0066 RFC0093 UNKNOWN UNKNOWN RFC0081 Request for Reference Information J. Bouknight December 03 1970 ASCII 956 1 UNKNOWN UNKNOWN RFC0082 Network Meeting Notes E. Meyer December 09 1970 ASCII 38023 18 UNKNOWN UNKNOWN RFC0083 Language-machine for data reconfiguration R.H. Anderson E. Harslem J.F. Heafner December 18 1970 ASCII 22253 13 UNKNOWN UNKNOWN RFC0084 List of NWG/RFC's 1-80 J.B. North December 23 1970 ASCII 12613 8 UNKNOWN UNKNOWN RFC0085 Network Working Group meeting S.D. Crocker December 28 1970 ASCII 1547 1 N UNKNOWN UNKNOWN RFC0086 Proposal for a Network Standard Format for a Data Stream to Control Graphics Display S.D. Crocker January 05 1971 ASCII 7117 6 RFC0125 UNKNOWN UNKNOWN RFC0087 Topic for Discussion at the Next Network Working Group Meeting A. Vezza January 12 1971 ASCII 3593 3 UNKNOWN UNKNOWN RFC0088 NETRJS: A third level protocol for Remote Job Entry R.T. Braden S.M. Wolfe January 13 1971 ASCII 19691 9 RFC0189 UNKNOWN UNKNOWN RFC0089 Some historic moments in networking R.M. Metcalfe January 19 1971 ASCII 16832 7 UNKNOWN UNKNOWN RFC0090 CCN as a Network Service Center R.T. Braden January 25 1971 ASCII 11929 6 UNKNOWN UNKNOWN RFC0091 Proposed User-User Protocol G.H. Mealy December 27 1970 ASCII 27005 12 UNKNOWN UNKNOWN RFC0092 RFC0093 Initial Connection Protocol A.M. McKenzie January 27 1971 ASCII 1746 1 RFC0066 RFC0080 UNKNOWN UNKNOWN RFC0094 Some thoughts on Network Graphics E. Harslem J.F. Heafner February 03 1971 ASCII 13516 6 UNKNOWN UNKNOWN RFC0095 Distribution of NWG/RFC's through the NIC S.D. Crocker February 04 1971 ASCII 8938 5 RFC0155 UNKNOWN UNKNOWN RFC0096 An Interactive Network Experiment to Study Modes of Access the Network Information Center R.W. Watson February 12 1971 ASCII 11334 5 INFORMATIONAL INFORMATIONAL RFC0097 First Cut at a Proposed Telnet Protocol J.T. Melvin R.W. Watson February 15 1971 Not Available Online UNKNOWN UNKNOWN RFC0098 Logger Protocol Proposal E. Meyer T. Skinner February 11 1971 ASCII 24536 10 RFC0123 UNKNOWN UNKNOWN RFC0099 Network Meeting P.M. Karp February 22 1971 ASCII 1010 1 RFC0116 UNKNOWN UNKNOWN RFC0100 Categorization and guide to NWG/RFCs P.M. Karp February 26 1971 ASCII 62473 37 UNKNOWN UNKNOWN RFC0101 Notes on the Network Working Group meeting, Urbana, Illinois, February 17, 1971 R.W. Watson February 23 1971 ASCII 30343 14 RFC0108 RFC0123 UNKNOWN UNKNOWN RFC0102 Output of the Host-Host Protocol glitch cleaning committee S.D. Crocker February 22 1971 ASCII 8511 4 RFC0107 UNKNOWN UNKNOWN RFC0103 Implementation of Interrupt Keys R.B. Kalin February 24 1971 ASCII 7592 4 UNKNOWN UNKNOWN RFC0104 Link 191 J.B. Postel S.D. Crocker February 25 1971 ASCII 1017 1 UNKNOWN UNKNOWN RFC0105 Network Specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB J.E. White March 22 1971 ASCII 21938 9 RFC0217 UNKNOWN UNKNOWN RFC0106 User/Server Site Protocol Network Host Questionnaire T.C. O'Sullivan March 03 1971 ASCII 6946 5 UNKNOWN UNKNOWN RFC0107 Output of the Host-Host Protocol Glitch Cleaning Committee R.D. Bressler S.D. Crocker W.R. Crowther G.R. Grossman R.S. Tomlinson J.E. White March 23 1971 ASCII 18109 12 RFC0102 RFC0111 RFC0124 RFC0132 RFC0154 RFC0179 UNKNOWN UNKNOWN RFC0108 Attendance list at the Urbana NWG meeting, February 17-19, 1971 R.W. Watson March 25 1971 ASCII 1597 2 RFC0101 UNKNOWN UNKNOWN RFC0109 Level III Server Protocol for the Lincoln Laboratory NIC 360/67 Host J.M. Winett March 24 1971 Not Available Online.. RFC0393 UNKNOWN UNKNOWN RFC0110 Conventions for using an IBM 2741 terminal as a user console for access to network server hosts J.M. Winett March 25 1971 Not Available Online.. RFC0135 UNKNOWN UNKNOWN RFC0111 Pressure from the Chairman S.D. Crocker March 31 1971 ASCII 2098 2 RFC0107 RFC0130 UNKNOWN UNKNOWN RFC0112 User/Server Site Protocol: Network host questionnaire responses T.C. O'Sullivan April 01 1971 Not Available Online.. UNKNOWN UNKNOWN RFC0113 Network activity report: UCSB Rand E. Harslem J.F. Heafner J.E. White April 05 1971 ASCII 3442 2 RFC0227 UNKNOWN UNKNOWN RFC0114 File Transfer Protocol A.K. Bhushan April 10 1971 ASCII 38981 17 FTP RFC0133 RFC0141 RFC0171 RFC0172 UNKNOWN UNKNOWN RFC0115 Some Network Information Center policies on handling documents R.W. Watson J.B. North April 16 1971 ASCII 16775 8 UNKNOWN UNKNOWN RFC0116 Structure of the May NWG Meeting S.D. Crocker April 12 1971 ASCII 2395 1 RFC0099 RFC0131 RFC0156 UNKNOWN UNKNOWN RFC0117 Some comments on the official protocol J. Wong April 07 1971 ASCII 7128 5 UNKNOWN UNKNOWN RFC0118 Recommendations for facility documentation R.W. Watson April 16 1971 ASCII 4573 2 UNKNOWN UNKNOWN RFC0119 Network Fortran subprograms M. Krilanovich April 21 1971 Not Available Online.. UNKNOWN UNKNOWN RFC0120 Network PL1 subprograms M. Krilanovich April 21 1971 ASCII 37192 16 UNKNOWN UNKNOWN RFC0121 Network on-line operators M. Krilanovich April 21 1971 ASCII 29419 13 UNKNOWN UNKNOWN RFC0122 Network specifications for UCSB's Simple-Minded File System J.E. White April 26 1971 ASCII 47638 21 RFC0217 RFC0269 RFC0399 RFC0431 UNKNOWN UNKNOWN RFC0123 Proffered Official ICP S.D. Crocker April 20 1971 ASCII 4812 3 RFC0066 RFC0080 RFC0165 RFC0098 RFC0101 RFC0127 RFC0143 RFC0148 UNKNOWN UNKNOWN RFC0124 Typographical error in RFC 107 J.T. Melvin April 19 1971 ASCII 659 1 RFC0107 UNKNOWN UNKNOWN RFC0125 Response to RFC 86: Proposal for Network Standard Format for a Graphics Data Stream J. McConnell April 18 1971 ASCII 8133 4 RFC0086 RFC0177 UNKNOWN UNKNOWN RFC0126 Graphics Facilities at Ames Research Center J. McConnell April 18 1971 ASCII 1974 1 UNKNOWN UNKNOWN RFC0127 Comments on RFC 123 J. Postel April 20 1971 ASCII 2305 2 RFC0145 RFC0123 RFC0151 UNKNOWN UNKNOWN RFC0128 Bytes J. Postel April 21 1971 ASCII 2745 2 UNKNOWN UNKNOWN RFC0129 Request for comments on socket name structure E. Harslem J. Heafner E. Meyer April 22 1971 ASCII 11175 6 RFC0147 UNKNOWN UNKNOWN RFC0130 Response to RFC 111: Pressure from the chairman J.F. Heafner April 22 1971 ASCII 2580 1 RFC0111 UNKNOWN UNKNOWN RFC0131 Response to RFC 116: May NWG meeting E. Harslem J.F. Heafner April 22 1971 ASCII 5375 3 RFC0116 UNKNOWN UNKNOWN RFC0132 Typographical Error in RFC 107 J.E. White April 28 1971 ASCII 1058 1 RFC0154 RFC0107 UNKNOWN UNKNOWN RFC0133 File Transfer and Error Recovery R.L. Sunberg April 27 1971 ASCII 8322 4 FTP RFC0114 UNKNOWN UNKNOWN RFC0134 Network Graphics meeting A. Vezza April 29 1971 ASCII 2684 2 UNKNOWN UNKNOWN RFC0135 Response to NWG/RFC 110 W. Hathaway April 29 1971 ASCII 5282 3 RFC0110 UNKNOWN UNKNOWN RFC0136 Host accounting and administrative procedures R.E. Kahn April 29 1971 ASCII 8016 4 UNKNOWN UNKNOWN RFC0137 Telnet Protocol - a proposed document T.C. O'Sullivan April 30 1971 ASCII 17606 11 RFC0139 UNKNOWN UNKNOWN RFC0138 Status report on proposed Data Reconfiguration Service R.H. Anderson V.G. Cerf E. Harslem J.F. Heafner J. Madden R.M. Metcalfe A. Shoshani J.E. White D.C.M. Wood April 28 1971 ASCII 46641 23 UNKNOWN UNKNOWN RFC0139 Discussion of Telnet Protocol T.C. O'Sullivan May 07 1971 ASCII 26085 11 RFC0137 RFC0158 RFC0393 UNKNOWN UNKNOWN RFC0140 Agenda for the May NWG meeting S.D. Crocker May 04 1971 ASCII 6934 4 RFC0149 UNKNOWN UNKNOWN RFC0141 Comments on RFC 114: A File Transfer Protocol E. Harslem J.F. Heafner April 29 1971 ASCII 3781 2 FTP RFC0114 UNKNOWN UNKNOWN RFC0142 Time-Out Mechanism in the Host-Host Protocol C. Kline J. Wong May 03 1971 ASCII 4372 2 UNKNOWN UNKNOWN RFC0143 Regarding proffered official ICP W. Naylor J. Wong C. Kline J. Postel May 03 1971 ASCII 6963 4 RFC0165 RFC0123 RFC0145 UNKNOWN UNKNOWN RFC0144 Data sharing on computer networks A. Shoshani April 30 1971 ASCII 13744 6 UNKNOWN UNKNOWN RFC0145 Initial Connection Protocol Control Commands J. Postel May 04 1971 ASCII 2490 2 PS 552114 PDF 15869 RFC0127 RFC0165 RFC0143 UNKNOWN UNKNOWN RFC0146 Views on issues relevant to data sharing on computer networks P.M. Karp D.B. McKay D.C.M. Wood May 12 1971 ASCII 9828 6 UNKNOWN UNKNOWN RFC0147 Definition of a socket J.M. Winett May 07 1971 ASCII 6438 3 RFC0129 UNKNOWN UNKNOWN RFC0148 Comments on RFC 123 A.K. Bhushan May 07 1971 ASCII 1149 1 RFC0123 UNKNOWN UNKNOWN RFC0149 Best Laid Plans S.D. Crocker May 10 1971 ASCII 1057 1 RFC0140 UNKNOWN UNKNOWN RFC0150 Use of IPC Facilities: A Working Paper R.B. Kalin May 05 1971 ASCII 28163 11 UNKNOWN UNKNOWN RFC0151 Comments on a proffered official ICP: RFCs 123, 127 A. Shoshani May 10 1971 ASCII 3623 2 RFC0127 UNKNOWN UNKNOWN RFC0152 SRI Artificial Intelligence status report M. Wilber May 10 1971 ASCII 2726 1 UNKNOWN UNKNOWN RFC0153 SRI ARC-NIC status J.T. Melvin R.W. Watson May 15 1971 ASCII 8573 4 UNKNOWN UNKNOWN RFC0154 Exposition Style S.D. Crocker May 12 1971 ASCII 1293 1 RFC0132 RFC0107 UNKNOWN UNKNOWN RFC0155 ARPA Network mailing lists J.B. North May 01 1971 ASCII 11054 13 RFC0095 RFC0168 UNKNOWN UNKNOWN RFC0156 Status of the Illinois site: Response to RFC 116 J. Bouknight April 26 1971 ASCII 1171 1 RFC0116 UNKNOWN UNKNOWN RFC0157 Invitation to the Second Symposium on Problems in the Optimization of Data Communications Systems V.G. Cerf May 12 1971 ASCII 3159 2 UNKNOWN UNKNOWN RFC0158 Telnet Protocol: A Proposed Document T.C. O'Sullivan May 19 1971 Not Available Online.. RFC0495 RFC0139 RFC0318 RFC0393 UNKNOWN UNKNOWN RFC0159 RFC0160 RFC brief list Network Information Center. Stanford Research Institute May 18 1971 ASCII 12173 4 RFC0200 RFC0999 NIC6716 UNKNOWN UNKNOWN RFC0161 Solution to the race condition in the ICP A. Shoshani May 19 1971 ASCII 2026 1 UNKNOWN UNKNOWN RFC0162 NETBUGGER3 M. Kampe May 22 1971 ASCII 3153 2 UNKNOWN UNKNOWN RFC0163 Data transfer protocols V.G. Cerf May 19 1971 ASCII 5465 3 FTP DTP data manager UNKNOWN UNKNOWN RFC0164 Minutes of Network Working Group meeting, 5/16 through 5/19/71 J.F. Heafner May 25 1971 ASCII 58597 32 UNKNOWN UNKNOWN RFC0165 Proffered official Initial Connection Protocol J. Postel May 25 1971 Not Available Online.. RFC0145 RFC0143 RFC0123 NIC7101 UNKNOWN UNKNOWN RFC0166 Data Reconfiguration Service: An implementation specification R.H. Anderson V.G. Cerf E. Harslem J.F. Heafner J. Madden R.M. Metcalfe A. Shoshani J.E. White D.C.M. Wood May 25 1971 ASCII 42094 20 UNKNOWN UNKNOWN RFC0167 Socket conventions reconsidered A.K. Bhushan R.M. Metcalfe J.M. Winett May 24 1971 ASCII 7643 4 RFC0147 RFC0129 UNKNOWN UNKNOWN RFC0168 ARPA Network mailing lists J.B. North May 26 1971 ASCII 13294 7 RFC0155 RFC0211 UNKNOWN UNKNOWN RFC0169 Computer networks S.D. Crocker May 27 1971 Not Available Online.. UNKNOWN UNKNOWN RFC0170 RFC List by Number Network Information Center. Stanford Research Institute June 01 1971 ASCII 17670 6 RFC0200 UNKNOWN UNKNOWN RFC0171 The Data Transfer Protocol A. Bhushan B. Braden W. Crowther E. Harslem J. Heafner A. McKenize J. Melvin B. Sundberg D. Watson J. White June 01 1971 ASCII 20616 9 FTP DTP RFC0264 RFC0114 RFC0238 UNKNOWN UNKNOWN RFC0172 The File Transfer Protocol A. Bhushan B. Braden W. Crowther E. Harslem J. Heafner A. McKenzie J. Melvin B. Sundberg D. Watson J. White June 23 1971 ASCII 21328 12 FTP RFC0265 RFC0114 RFC0238 UNKNOWN UNKNOWN RFC0173 Network Data Management Committee Meeting Announcement P.M. Karp D.B. McKay June 04 1971 ASCII 4239 2 UNKNOWN UNKNOWN RFC0174 UCLA - Computer Science Graphics Overview J. Postel V.G. Cerf June 08 1971 ASCII 5037 3 UNKNOWN UNKNOWN RFC0175 Comments on "Socket Conventions Reconsidered" E. Harslem J.F. Heafner June 11 1971 ASCII 2225 1 UNKNOWN UNKNOWN RFC0176 Comments on "Byte size for connections" A.K. Bhushan R. Kanodia R.M. Metcalfe J. Postel June 14 1971 ASCII 7269 5 UNKNOWN UNKNOWN RFC0177 Device independent graphical display description J. McConnell June 15 1971 ASCII 20474 9 RFC0125 RFC0181 UNKNOWN UNKNOWN RFC0178 Network graphic attention handling I.W. Cotton June 27 1971 ASCII 24522 11 UNKNOWN UNKNOWN RFC0179 Link Number Assignments A.M. McKenzie June 22 1971 ASCII 1221 1 RFC0107 UNKNOWN UNKNOWN RFC0180 File system questionnaire A.M. McKenzie June 25 1971 ASCII 8154 4 UNKNOWN UNKNOWN RFC0181 Modifications to RFC 177 J. McConnell July 21 1971 ASCII 4892 3 RFC0177 UNKNOWN UNKNOWN RFC0182 Compilation of list of relevant site reports J.B. North June 25 1971 ASCII 2565 1 UNKNOWN UNKNOWN RFC0183 EBCDIC codes and their mapping to ASCII J.M. Winett July 21 1971 Not Available Online.. UNKNOWN UNKNOWN RFC0184 Proposed graphic display modes K.C. Kelley July 06 1971 ASCII 18678 7 UNKNOWN UNKNOWN RFC0185 NIC distribution of manuals and handbooks J.B. North July 07 1971 ASCII 1406 1 UNKNOWN UNKNOWN RFC0186 Network graphics loader J.C. Michener July 12 1971 ASCII 30557 17 UNKNOWN UNKNOWN RFC0187 Network/440 Protocol Concept D.B. McKay D.P. Karp July 01 1971 ASCII 25042 11 UNKNOWN UNKNOWN RFC0188 Data management meeting announcement P.M. Karp D.B. McKay January 28 1971 ASCII 3383 2 UNKNOWN UNKNOWN RFC0189 Interim NETRJS specifications R.T. Braden July 15 1971 ASCII 41383 19 RFC0088 RFC0599 RFC0283 UNKNOWN UNKNOWN RFC0190 DEC PDP-10-IMLAC communications system L.P. Deutsch July 13 1971 ASCII 18752 16 UNKNOWN UNKNOWN RFC0191 Graphics implementation and conceptualization at Augmentation Research Center C.H. Irby July 13 1971 ASCII 8179 4 UNKNOWN UNKNOWN RFC0192 Some factors which a Network Graphics Protocol must consider R.W. Watson July 12 1971 ASCII 48540 19 UNKNOWN UNKNOWN RFC0193 NETWORK CHECKOUT E. Harslem J.F. Heafner July 14 1971 ASCII 3622 2 RFC0198 RFC0198 UNKNOWN UNKNOWN RFC0194 The Data Reconfiguration Service -- Compiler/Interpreter Implementation Notes V. Cerf E. Harslem J. Heafner B. Metcalfe J. White July 14 1971 ASCII 32716 18 UNKNOWN UNKNOWN RFC0195 Data computers-data descriptions and access language G.H. Mealy July 16 1971 ASCII 8704 4 UNKNOWN UNKNOWN RFC0196 Mail Box Protocol R.W. Watson July 20 1971 ASCII 7016 4 RFC0221 UNKNOWN UNKNOWN RFC0197 Initial Connection Protocol - Reviewed A. Shoshani E. Harslem July 14 1971 ASCII 7094 5 UNKNOWN UNKNOWN RFC0198 Site Certification - Lincoln Labs 360/67 J.F. Heafner July 20 1971 ASCII 855 1 RFC0193 RFC0214 RFC0193 UNKNOWN UNKNOWN RFC0199 Suggestions for a network data-tablet graphics protocol T. Williams July 15 1971 Not Available Online.. UNKNOWN UNKNOWN RFC0200 RFC list by number J.B. North August 01 1971 ASCII 19256 7 RFC0170 RFC0160 NIC7724 UNKNOWN UNKNOWN RFC0201 RFC0202 Possible Deadlock in ICP S.M. Wolfe J. Postel July 26 1971 ASCII 2796 2 UNKNOWN UNKNOWN RFC0203 Achieving reliable communication R.B. Kalin August 10 1971 ASCII 9253 4 UNKNOWN UNKNOWN RFC0204 Sockets in use J. Postel August 05 1971 ASCII 1379 1 RFC0234 UNKNOWN UNKNOWN RFC0205 NETCRT - a character display protocol R.T. Braden August 06 1971 ASCII 28272 13 UNKNOWN UNKNOWN RFC0206 User Telnet - description of an initial implementation J.E. White August 09 1971 Not Available Online.. UNKNOWN UNKNOWN RFC0207 September Network Working Group meeting A. Vezza August 09 1971 ASCII 3356 2 RFC0212 UNKNOWN UNKNOWN RFC0208 Address tables A.M. McKenzie August 09 1971 ASCII 5858 3 UNKNOWN UNKNOWN RFC0209 Host/IMP interface documentation B. Cosell August 13 1971 ASCII 2566 1 UNKNOWN UNKNOWN RFC0210 Improvement of Flow Control W. Conrad August 16 1971 ASCII 3329 2 UNKNOWN UNKNOWN RFC0211 ARPA Network mailing lists J.B. North August 18 1971 Not Available Online.. RFC0168 RFC0300 UNKNOWN UNKNOWN RFC0212 NWG meeting on network usage Information Sciences Institute University of Southern California August 23 1971 ASCII 4356 2 RFC0207 RFC0222 UNKNOWN UNKNOWN RFC0213 IMP System change notification B. Cosell August 20 1971 ASCII 1589 1 UNKNOWN UNKNOWN RFC0214 Network checkpoint E. Harslem August 21 1971 ASCII 3047 2 RFC0198 UNKNOWN UNKNOWN RFC0215 NCP, ICP, and Telnet: The Terminal IMP implementation A.M. McKenzie August 30 1971 ASCII 16645 7 UNKNOWN UNKNOWN RFC0216 Telnet access to UCSB's On-Line System J.E. White September 08 1971 Not Available Online.. UNKNOWN UNKNOWN RFC0217 Specifications changes for OLS, RJE/RJOR, and SMFS J.E. White September 08 1971 ASCII 2956 2 RFC0074 RFC0105 RFC0122 UNKNOWN UNKNOWN RFC0218 Changing the IMP status reporting facility B. Cosell September 08 1971 ASCII 1131 1 UNKNOWN UNKNOWN RFC0219 User's view of the datacomputer R. Winter September 03 1971 Not Available Online.. UNKNOWN UNKNOWN RFC0220 RFC0221 Mail Box Protocol: Version 2 R.W. Watson August 27 1971 ASCII 9805 5 RFC0196 RFC0278 UNKNOWN UNKNOWN RFC0222 Subject: System programmer's workshop R.M. Metcalfe September 13 1971 ASCII 4023 2 RFC0212 RFC0234 UNKNOWN UNKNOWN RFC0223 Network Information Center schedule for network users J.T. Melvin R.W. Watson September 14 1971 ASCII 5369 4 UNKNOWN UNKNOWN RFC0224 Comments on Mailbox Protocol A.M. McKenzie September 14 1971 ASCII 3583 2 UNKNOWN UNKNOWN RFC0225 Rand/UCSB network graphics experiment E. Harslem R. Stoughton September 13 1971 ASCII 13573 5 RFC0074 UNKNOWN UNKNOWN RFC0226 Standardization of host mnemonics P.M. Karp September 20 1971 ASCII 2012 1 a RFC0247 UNKNOWN UNKNOWN RFC0227 Data transfer rates (Rand/UCLA) J.F. Heafner E. Harslem September 17 1971 ASCII 2451 2 RFC0113 UNKNOWN UNKNOWN RFC0228 Clarification D.C. Walden September 22 1971 ASCII 715 1 RFC0070 UNKNOWN UNKNOWN RFC0229 Standard host names J. Postel September 22 1971 ASCII 3388 3 RFC0236 UNKNOWN UNKNOWN RFC0230 Toward reliable operation of minicomputer-based terminals on a TIP T. Pyke September 24 1971 ASCII 7040 3 UNKNOWN UNKNOWN RFC0231 Service center standards for remote usage: A user's view J.F. Heafner E. Harslem September 21 1971 ASCII 9692 4 UNKNOWN UNKNOWN RFC0232 Postponement of network graphics meeting A. Vezza September 23 1971 ASCII 899 1 UNKNOWN UNKNOWN RFC0233 Standardization of host call letters A. Bhushan R. Metcalfe September 28 1971 ASCII 3206 2 UNKNOWN UNKNOWN RFC0234 Network Working Group meeting schedule A. Vezza October 05 1971 ASCII 1634 1 RFC0222 RFC0204 UNKNOWN UNKNOWN RFC0235 Site status E. Westheimer September 27 1971 ASCII 7994 5 RFC0240 UNKNOWN UNKNOWN RFC0236 Standard host names J. Postel September 27 1971 ASCII 5112 2 RFC0229 UNKNOWN UNKNOWN RFC0237 NIC view of standard host names R.W. Watson October 05 1971 ASCII 2212 1 RFC0273 UNKNOWN UNKNOWN RFC0238 Comments on DTP and FTP proposals R.T. Braden September 29 1971 ASCII 2735 2 FTP RFC0171 RFC0172 UNKNOWN UNKNOWN RFC0239 Host mnemonics proposed in RFC 226 (NIC 7625) R.T. Braden September 23 1971 ASCII 2236 1 RFC0226 RFC0229 RFC0236 UNKNOWN UNKNOWN RFC0240 Site Status A.M. McKenzie September 30 1971 ASCII 7948 4 RFC0235 RFC0252 UNKNOWN UNKNOWN RFC0241 Connecting computers to MLC ports A.M. McKenzie September 29 1971 ASCII 3739 2 UNKNOWN UNKNOWN RFC0242 Data Descriptive Language for Shared Data L. Haibt A.P. Mullery July 19 1971 ASCII 18151 10 UNKNOWN UNKNOWN RFC0243 Network and data sharing bibliography A.P. Mullery October 05 1971 ASCII 12432 7 RFC0290 UNKNOWN UNKNOWN RFC0244 RFC0245 Reservations for Network Group meeting C. Falls October 05 1971 ASCII 1142 1 UNKNOWN UNKNOWN RFC0246 Network Graphics meeting A. Vezza October 05 1971 ASCII 856 1 UNKNOWN UNKNOWN RFC0247 Proffered set of standard host names P.M. Karp October 12 1971 ASCII 7122 4 RFC0226 UNKNOWN UNKNOWN RFC0248 RFC0249 Coordination of equipment and supplies purchase R.F. Borelli October 08 1971 ASCII 4561 2 UNKNOWN UNKNOWN RFC0250 Some thoughts on file transfer H. Brodie October 07 1971 ASCII 2446 1 UNKNOWN UNKNOWN RFC0251 Weather data D. Stern October 13 1971 ASCII 1907 2 UNKNOWN UNKNOWN RFC0252 Network host status E. Westheimer October 08 1971 ASCII 5531 3 RFC0240 RFC0255 UNKNOWN UNKNOWN RFC0253 Second Network Graphics meeting details J.A. Moorer October 19 1971 ASCII 1981 1 UNKNOWN UNKNOWN RFC0254 Scenarios for using ARPANET computers A. Bhushan October 29 1971 Not Available Online.. UNKNOWN UNKNOWN RFC0255 Status of network hosts E. Westheimer October 26 1971 ASCII 4002 2 RFC0252 RFC0266 UNKNOWN UNKNOWN RFC0256 IMPSYS change notification B. Cosell November 03 1971 ASCII 1240 1 UNKNOWN UNKNOWN RFC0257 RFC0258 RFC0259 RFC0260 RFC0261 RFC0262 RFC0263 "Very Distant" Host interface A.M. McKenzie December 17 1971 ASCII 3914 2 UNKNOWN UNKNOWN RFC0264 The Data Transfer Protocol A. Bhushan B. Braden W. Crowther E. Harslem J. Heafner A. McKenize B. Sundberg D. Watson J. White January 04 1972 ASCII 20907 9 FTP DTP RFC0171 RFC0354 RFC0310 RFC0265 UNKNOWN UNKNOWN RFC0265 The File Transfer Protocol A. Bhushan B. Braden W. Crowther E. Harslem J. Heafner A. McKenzie J. Melvin B. Sundberg D. Watson J. White November 17 1971 ASCII 3914 12 FTP RFC0172 RFC0354 RFC0281 RFC0294 RFC0310 RFC0264 UNKNOWN UNKNOWN RFC0266 Network host status E. Westheimer November 08 1971 ASCII 3174 2 RFC0255 RFC0267 UNKNOWN UNKNOWN RFC0267 Network Host Status E. Westheimer November 22 1971 ASCII 7862 4 RFC0266 RFC0287 UNKNOWN UNKNOWN RFC0268 Graphics facilities information J. Postel November 24 1971 ASCII 1298 1 UNKNOWN UNKNOWN RFC0269 Some Experience with File Transfer H. Brodie December 06 1971 ASCII 5961 3 RFC0122 UNKNOWN UNKNOWN RFC0270 Correction to BBN Report No. 1822 (NIC NO 7958) A.M. McKenzie January 01 1972 ASCII 1371 1 NIC7959 UNKNOWN UNKNOWN RFC0271 IMP System change notifications B. Cosell January 03 1972 ASCII 4022 2 UNKNOWN UNKNOWN RFC0272 RFC0273 More on standard host names R.W. Watson October 18 1971 ASCII 4589 3 RFC0237 UNKNOWN UNKNOWN RFC0274 Establishing a local guide for network usage E. Forman November 01 1971 ASCII 7114 5 UNKNOWN UNKNOWN RFC0275 RFC0276 NIC course R.W. Watson November 08 1971 ASCII 1183 1 UNKNOWN UNKNOWN RFC0277 RFC0278 Revision of the Mail Box Protocol A.K. Bhushan R.T. Braden E. Harslem J.F. Heafner A.M. McKenzie J.T. Melvin R.L. Sundberg R.W. Watson J.E. White November 17 1971 ASCII 7526 4 RFC0221 UNKNOWN UNKNOWN RFC0279 RFC0280 A Draft of Host Names R.W. Watson November 17 1971 ASCII 3629 3 UNKNOWN UNKNOWN RFC0281 Suggested addition to File Transfer Protocol A.M. McKenzie December 08 1971 ASCII 12006 8 FTP RFC0265 UNKNOWN UNKNOWN RFC0282 Graphics meeting report M.A. Padlipsky December 08 1971 ASCII 18100 8 UNKNOWN UNKNOWN RFC0283 NETRJT: Remote Job Service Protocol for TIPS R.T. Braden December 20 1971 ASCII 18771 9 RFC0189 UNKNOWN UNKNOWN RFC0284 RFC0285 Network graphics D. Huff December 15 1971 ASCII 18076 8 UNKNOWN UNKNOWN RFC0286 Network Library Information System E. Forman December 21 1971 ASCII 2079 1 UNKNOWN UNKNOWN RFC0287 Status of Network Hosts E. Westheimer December 22 1971 ASCII 9217 5 RFC0267 RFC0288 UNKNOWN UNKNOWN RFC0288 Network host status E. Westheimer January 06 1972 ASCII 8501 4 RFC0287 RFC0293 RFC0293 UNKNOWN UNKNOWN RFC0289 What we hope is an official list of host names R.W. Watson December 21 1971 ASCII 5069 3 RFC0384 UNKNOWN UNKNOWN RFC0290 Computer networks and data sharing: A bibliography A.P. Mullery January 11 1972 ASCII 34329 15 RFC0243 UNKNOWN UNKNOWN RFC0291 Data Management Meeting Announcement D.B. McKay January 14 1972 ASCII 3375 2 UNKNOWN UNKNOWN RFC0292 Graphics Protocol: Level 0 only J.C. Michener I.W. Cotton K.C. Kelley D.E. Liddle E. Meyer January 12 1972 ASCII 22342 10 UNKNOWN UNKNOWN RFC0293 Network Host Status E. Westheimer January 18 1972 ASCII 7639 4 RFC0288 RFC0298 RFC0288 UNKNOWN UNKNOWN RFC0294 The Use of "Set Data Type" Transaction in File Transfer Protocol A.K. Bhushan January 25 1972 ASCII 3924 2 FTP RFC0265 UNKNOWN UNKNOWN RFC0295 Report of the Protocol Workshop, 12 October 1971 J. Postel January 02 1972 ASCII 5432 4 UNKNOWN UNKNOWN RFC0296 DS-1 display system D.E. Liddle January 27 1972 Not Available Online.. UNKNOWN UNKNOWN RFC0297 TIP Message Buffers D.C. Walden January 31 1972 ASCII 3517 2 UNKNOWN UNKNOWN RFC0298 Network host status E. Westheimer February 11 1972 ASCII 8770 4 RFC0293 RFC0306 UNKNOWN UNKNOWN RFC0299 Information Management System D. Hopkin February 11 1972 ASCII 1825 1 UNKNOWN UNKNOWN RFC0300 ARPA Network mailing lists J.B. North January 25 1972 ASCII 16357 9 RFC0211 RFC0303 UNKNOWN UNKNOWN RFC0301 BBN IMP (#5) and NCC Schedule March 4, 1971 R. Alter February 11 1972 ASCII 1487 1 UNKNOWN UNKNOWN RFC0302 Exercising The ARPANET R.F. Bryan February 08 1972 ASCII 5452 3 UNKNOWN UNKNOWN RFC0303 ARPA Network mailing lists Network Information Center. Stanford Research Institute March 03 1972 ASCII 18193 11 RFC0300 RFC0329 UNKNOWN UNKNOWN RFC0304 Data management system proposal for the ARPA network D.B. McKay February 17 1972 Not Available Online.. UNKNOWN UNKNOWN RFC0305 Unknown Host Numbers R. Alter February 23 1972 ASCII 1998 1 UNKNOWN UNKNOWN RFC0306 Network host status E. Westheimer February 15 1972 ASCII 7485 4 RFC0298 RFC0315 UNKNOWN UNKNOWN RFC0307 Using network Remote Job Entry E. Harslem February 24 1972 ASCII 12032 6 UNKNOWN UNKNOWN RFC0308 ARPANET host availability data M. Seriff March 13 1972 ASCII 5948 4 UNKNOWN UNKNOWN RFC0309 Data and File Transfer Workshop Announcement A.K. Bhushan March 17 1972 ASCII 9404 6 FTP DTP UNKNOWN UNKNOWN RFC0310 Another Look at Data and File Transfer Protocols A.K. Bhushan April 03 1972 ASCII 18593 7 FTP RFC0264 RFC0265 UNKNOWN UNKNOWN RFC0311 New Console Attachments to the USCB Host R.F. Bryan February 29 1972 ASCII 3141 2 UNKNOWN UNKNOWN RFC0312 Proposed Change in IMP-to-Host Protocol A.M. McKenzie March 22 1972 ASCII 3562 2 UNKNOWN UNKNOWN RFC0313 Computer based instruction T.C. O'Sullivan March 06 1972 ASCII 19880 8 UNKNOWN UNKNOWN RFC0314 Network Graphics Working Group Meeting I.W. Cotton March 14 1972 ASCII 1836 1 UNKNOWN UNKNOWN RFC0315 Network Host Status E. Westheimer March 08 1972 ASCII 7818 4 RFC0306 RFC0319 UNKNOWN UNKNOWN RFC0316 ARPA Network Data Management Working Group D.B. McKay A.P. Mullery February 23 1972 ASCII 15494 7 UNKNOWN UNKNOWN RFC0317 Official Host-Host Protocol Modification: Assigned Link Numbers J. Postel March 20 1972 ASCII 1593 1 RFC0604 UNKNOWN UNKNOWN RFC0318 Telnet Protocols J. Postel April 03 1972 ASCII 34928 16 RFC0158 RFC0435 RFC0139 RFC0158 UNKNOWN UNKNOWN RFC0319 Network Host Status E. Westheimer March 21 1972 ASCII 8955 4 RFC0315 RFC0326 UNKNOWN UNKNOWN RFC0320 Workshop on Hard Copy Line Printers R. Reddy March 27 1972 Not Available Online.. UNKNOWN UNKNOWN RFC0321 CBI Networking Activity at MITRE P.M. Karp March 24 1972 ASCII 20500 13 UNKNOWN UNKNOWN RFC0322 Well known socket numbers V. Cerf J. Postel March 26 1972 ASCII 1735 1 UNKNOWN UNKNOWN RFC0323 Formation of Network Measurement Group (NMG) V. Cerf March 23 1972 ASCII 15777 9 RFC0388 UNKNOWN UNKNOWN RFC0324 RJE Protocol meeting J. Postel April 03 1972 ASCII 1176 1 UNKNOWN UNKNOWN RFC0325 Network Remote Job Entry program - NETRJS G. Hicks April 06 1972 ASCII 17499 9 UNKNOWN UNKNOWN RFC0326 Network Host Status E. Westheimer April 03 1972 ASCII 7944 4 RFC0330 RFC0319 UNKNOWN UNKNOWN RFC0327 Data and File Transfer workshop notes A.K. Bhushan April 27 1972 ASCII 11792 5 UNKNOWN UNKNOWN RFC0328 Suggested Telnet Protocol Changes J. Postel April 29 1972 ASCII 2685 2 UNKNOWN UNKNOWN RFC0329 ARPA Network Mailing Lists Network Information Center. Stanford Research Institute May 17 1972 ASCII 23861 13 RFC0303 RFC0363 UNKNOWN UNKNOWN RFC0330 Network Host Status E. Westheimer April 13 1972 ASCII 8085 3 RFC0326 RFC0332 UNKNOWN UNKNOWN RFC0331 IMP System Change Notification J.M. McQuillan April 19 1972 ASCII 2339 1 RFC0343 UNKNOWN UNKNOWN RFC0332 Network Host Status E. Westheimer April 25 1972 ASCII 8427 4 RFC0342 RFC0330 UNKNOWN UNKNOWN RFC0333 Proposed experiment with a Message Switching Protocol R.D. Bressler D. Murphy D.C. Walden May 15 1972 ASCII 62507 26 UNKNOWN UNKNOWN RFC0334 Network Use on May 8 A.M. McKenzie May 01 1972 ASCII 1376 1 UNKNOWN UNKNOWN RFC0335 New Interface - IMP/360 R.F. Bryan May 01 1972 ASCII 934 1 UNKNOWN UNKNOWN RFC0336 Level 0 Graphic Input Protocol I.W. Cotton May 05 1972 ASCII 3787 2 UNKNOWN UNKNOWN RFC0337 RFC0338 EBCDIC/ASCII Mapping for Network RJE R.T. Braden May 17 1972 ASCII 11494 6 PS 2386987 PDF 1871020 UNKNOWN UNKNOWN RFC0339 MLTNET: A "Multi Telnet" Subsystem for Tenex R. Thomas May 05 1972 ASCII 7941 4 UNKNOWN UNKNOWN RFC0340 Proposed Telnet Changes T.C. O'Sullivan May 15 1972 ASCII 2656 2 RFC0328 UNKNOWN UNKNOWN RFC0341 RFC0342 Network Host Status E. Westheimer May 15 1972 ASCII 8382 4 RFC0332 RFC0344 UNKNOWN UNKNOWN RFC0343 IMP System change notification A.M. McKenzie May 19 1972 ASCII 3370 2 RFC0331 RFC0359 UNKNOWN UNKNOWN RFC0344 Network Host Status E. Westheimer May 22 1972 ASCII 8221 4 RFC0342 RFC0353 UNKNOWN UNKNOWN RFC0345 Interest in Mixed Integer Programming (MPSX on NIC 360/91 at CCN) K.C. Kelley May 26 1972 ASCII 1999 1 MIP UNKNOWN UNKNOWN RFC0346 Satellite Considerations J. Postel May 30 1972 ASCII 2778 1 UNKNOWN UNKNOWN RFC0347 Echo process J. Postel May 30 1972 ASCII 1377 1 UNKNOWN UNKNOWN RFC0348 Discard Process J. Postel May 30 1972 ASCII 1181 1 UNKNOWN UNKNOWN RFC0349 Proposed Standard Socket Numbers J. Postel May 30 1972 ASCII 1663 1 RFC0433 RFC0322 RFC0204 UNKNOWN UNKNOWN RFC0350 User Accounts for UCSB On-Line System R. Stoughton May 18 1972 ASCII 5117 3 UNKNOWN UNKNOWN RFC0351 Graphics information form for the ARPANET graphics resources notebook D. Crocker June 05 1972 ASCII 2150 2 UNKNOWN UNKNOWN RFC0352 TIP Site Information Form D. Crocker June 05 1972 ASCII 2266 3 UNKNOWN UNKNOWN RFC0353 Network host status E. Westheimer June 12 1972 ASCII 8747 5 RFC0344 RFC0362 UNKNOWN UNKNOWN RFC0354 File Transfer Protocol A.K. Bhushan July 08 1972 ASCII 58074 25 FTP RFC0264 RFC0265 RFC0542 RFC0385 RFC0454 RFC0683 UNKNOWN UNKNOWN RFC0355 Response to NWG/RFC 346 J. Davidson June 09 1972 ASCII 3717 3 UNKNOWN UNKNOWN RFC0356 ARPA Network Control Center R. Alter June 21 1972 ASCII 1963 1 UNKNOWN UNKNOWN RFC0357 Echoing strategy for satellite links J. Davidson June 26 1972 ASCII 30103 13 UNKNOWN UNKNOWN RFC0358 RFC0359 Status of the Release of the New IMP System (2600) D.C. Walden June 22 1972 ASCII 2015 1 RFC0343 UNKNOWN UNKNOWN RFC0360 Proposed Remote Job Entry Protocol C. Holland June 24 1972 Not Available Online.. RFC0407 UNKNOWN UNKNOWN RFC0361 Deamon Processes on Host 106 R.D. Bressler July 05 1972 ASCII 1480 1 UNKNOWN UNKNOWN RFC0362 Network Host Status E. Westheimer June 28 1972 ASCII 8631 4 RFC0353 RFC0366 UNKNOWN UNKNOWN RFC0363 ARPA Network mailing lists Network Information Center. Stanford Research Institute August 08 1972 ASCII 25356 13 RFC0329 RFC0402 UNKNOWN UNKNOWN RFC0364 Serving remote users on the ARPANET M.D. Abrams July 11 1972 ASCII 11253 6 UNKNOWN UNKNOWN RFC0365 Letter to All TIP Users D.C. Walden July 11 1972 ASCII 10331 5 UNKNOWN UNKNOWN RFC0366 Network Host Status E. Westheimer July 11 1972 ASCII 8278 4 RFC0362 RFC0367 UNKNOWN UNKNOWN RFC0367 Network host status E. Westheimer July 19 1972 ASCII 8057 4 RFC0366 RFC0370 UNKNOWN UNKNOWN RFC0368 Comments on "Proposed Remote Job Entry Protocol" R.T. Braden July 21 1972 ASCII 3883 2 UNKNOWN UNKNOWN RFC0369 Evaluation of ARPANET services January-March, 1972 J.R. Pickens July 25 1972 ASCII 24414 11 UNKNOWN UNKNOWN RFC0370 Network Host Status E. Westheimer July 31 1972 ASCII 8389 5 RFC0367 RFC0376 UNKNOWN UNKNOWN RFC0371 Demonstration at International Computer Communications Conference R.E. Kahn July 12 1972 ASCII 3728 2 UNKNOWN UNKNOWN RFC0372 Notes on a Conversation with Bob Kahn on the ICCC R.W. Watson July 12 1972 ASCII 6040 4 UNKNOWN UNKNOWN RFC0373 Arbitrary Character Sets J. McCarthy July 14 1972 ASCII 7783 4 UNKNOWN UNKNOWN RFC0374 IMP System Announcement A.M. McKenzie July 19 1972 ASCII 3963 2 UNKNOWN UNKNOWN RFC0375 RFC0376 Network Host Status E. Westheimer August 08 1972 ASCII 8861 5 RFC0370 UNKNOWN UNKNOWN RFC0377 Using TSO via ARPA Network Virtual Terminal R.T. Braden August 10 1972 ASCII 7093 4 UNKNOWN UNKNOWN RFC0378 Traffic statistics (July 1972) A.M. McKenzie August 10 1972 ASCII 5730 3 RFC0391 UNKNOWN UNKNOWN RFC0379 Using TSO at CCN R.. Braden August 11 1972 ASCII 8674 5 UNKNOWN UNKNOWN RFC0380 RFC0381 Three aids to improved network operation J.M. McQuillan July 26 1972 ASCII 9305 4 RFC0394 UNKNOWN UNKNOWN RFC0382 Mathematical Software on the ARPA Network L. McDaniel August 03 1972 ASCII 2041 1 UNKNOWN UNKNOWN RFC0383 RFC0384 Official site idents for organizations in the ARPA Network J.B. North August 28 1972 ASCII 10401 4 RFC0289 UNKNOWN UNKNOWN RFC0385 Comments on the File Transfer Protocol A.K. Bhushan August 18 1972 ASCII 13030 6 FTP RFC0354 RFC0414 UNKNOWN UNKNOWN RFC0386 Letter to TIP users-2 B. Cosell D.C. Walden August 16 1972 ASCII 12475 5 UNKNOWN UNKNOWN RFC0387 Some experiences in implementing Network Graphics Protocol Level 0 K.C. Kelley J. Meir August 10 1972 ASCII 9059 5 RFC0401 UNKNOWN UNKNOWN RFC0388 NCP statistics V. Cerf August 23 1972 ASCII 8458 5 RFC0323 UNKNOWN UNKNOWN RFC0389 UCLA Campus Computing Network Liaison Staff for ARPA Network B. Noble August 30 1972 ASCII 2819 2 RFC0423 UNKNOWN UNKNOWN RFC0390 TSO Scenario R.T. Braden September 12 1972 ASCII 6103 4 UNKNOWN UNKNOWN RFC0391 Traffic statistics (August 1972) A.M. McKenzie September 15 1972 ASCII 4695 3 RFC0378 UNKNOWN UNKNOWN RFC0392 Measurement of host costs for transmitting network data G. Hicks B.D. Wessler September 20 1972 ASCII 14462 6 UNKNOWN UNKNOWN RFC0393 Comments on Telnet Protocol Changes J.M. Winett October 03 1972 ASCII 9435 4 RFC0109 RFC0139 RFC0158 RFC0318 RFC0328 UNKNOWN UNKNOWN RFC0394 Two Proposed Changes to the IMP-Host Protocol J.M. McQuillan September 27 1972 ASCII 5780 3 RFC0381 UNKNOWN UNKNOWN RFC0395 Switch Settings on IMPs and TIPs J.M. McQuillan October 03 1972 ASCII 1827 1 UNKNOWN UNKNOWN RFC0396 Network Graphics Working Group Meeting - Second Iteration S. Bunch November 13 1972 ASCII 2224 1 RFC0474 UNKNOWN UNKNOWN RFC0397 RFC0398 ICP Sockets J.R. Pickens E. Faeh September 22 1972 ASCII 3846 2 UNKNOWN UNKNOWN RFC0399 SMFS Login and Logout M. Krilanovich September 26 1972 ASCII 3024 2 RFC0431 RFC0122 UNKNOWN UNKNOWN RFC0400 Traffic Statistics (September 1972) A.M. McKenzie October 18 1972 ASCII 5435 3 UNKNOWN UNKNOWN RFC0401 Conversion of NGP-0 Coordinates to Device Specific Coordinates J. Hansen October 23 1972 ASCII 3894 2 RFC0387 UNKNOWN UNKNOWN RFC0402 ARPA Network Mailing Lists J.B. North October 26 1972 ASCII 28162 16 RFC0363 UNKNOWN UNKNOWN RFC0403 Desirability of a network 1108 service G. Hicks January 10 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0404 Host Address Changes Involving Rand and ISI A.M. McKenzie October 05 1972 ASCII 944 1 RFC0405 UNKNOWN UNKNOWN RFC0405 Correction to RFC 404 A.M. McKenzie October 10 1972 ASCII 1103 1 RFC0404 UNKNOWN UNKNOWN RFC0406 Scheduled IMP Software Releases J.M. McQuillan October 10 1972 ASCII 2468 2 UNKNOWN UNKNOWN RFC0407 Remote Job Entry Protocol R.D. Bressler R. Guida A.M. McKenzie October 16 1972 ASCII 47556 21 RJE RFC0360 HISTORIC HISTORIC RFC0408 NETBANK A.D. Owen J. Postel October 25 1972 ASCII 1645 1 UNKNOWN UNKNOWN RFC0409 Tenex interface to UCSB's Simple-Minded File System J.E. White December 08 1972 ASCII 14231 8 UNKNOWN UNKNOWN RFC0410 Removal of the 30-Second Delay When Hosts Come Up J.M. McQuillan November 10 1972 ASCII 3964 2 UNKNOWN UNKNOWN RFC0411 New MULTICS Network Software Features M.A. Padlipsky November 14 1972 ASCII 3024 2 UNKNOWN UNKNOWN RFC0412 User FTP Documentation G. Hicks November 27 1972 ASCII 17510 10 UNKNOWN UNKNOWN RFC0413 Traffic statistics (October 1972) A.M. McKenzie November 13 1972 ASCII 16145 10 UNKNOWN UNKNOWN RFC0414 File Transfer Protocol (FTP) status and further comments A.K. Bhushan December 29 1972 ASCII 12845 5 RFC0385 UNKNOWN UNKNOWN RFC0415 Tenex bandwidth H. Murray November 29 1972 ASCII 3456 2 UNKNOWN UNKNOWN RFC0416 ARC System Will Be Unavailable for Use During Thanksgiving Week J.C. Norton November 07 1972 ASCII 2205 2 UNKNOWN UNKNOWN RFC0417 Link usage violation J. Postel C. Kline December 06 1972 ASCII 901 1 UNKNOWN UNKNOWN RFC0418 Server file transfer under TSS/360 at NASA Ames W. Hathaway November 27 1972 Not Available Online.. UNKNOWN UNKNOWN RFC0419 To: Network liaisons and station agents A. Vezza December 12 1972 ASCII 1252 1 UNKNOWN UNKNOWN RFC0420 CCA ICCC weather demo H. Murray January 04 1973 ASCII 14752 8 UNKNOWN UNKNOWN RFC0421 Software Consulting Service for Network Users A.M. McKenzie November 27 1972 ASCII 2483 2 UNKNOWN UNKNOWN RFC0422 Traffic statistics (November 1972) A.M. McKenzie December 11 1972 ASCII 5494 4 UNKNOWN UNKNOWN RFC0423 UCLA Campus Computing Network Liaison Staff for ARPANET B. Noble December 12 1972 ASCII 2890 2 RFC0389 UNKNOWN UNKNOWN RFC0424 RFC0425 "But my NCP costs $500 a day" R.D. Bressler December 19 1972 ASCII 1763 1 UNKNOWN UNKNOWN RFC0426 Reconnection Protocol R. Thomas January 26 1973 ASCII 26548 12 UNKNOWN UNKNOWN RFC0427 RFC0428 RFC0429 Character Generator Process J. Postel December 12 1972 ASCII 1319 1 UNKNOWN UNKNOWN RFC0430 Comments on File Transfer Protocol R.T. Braden February 07 1973 ASCII 18696 8 UNKNOWN UNKNOWN RFC0431 Update on SMFS Login and Logout M. Krilanovich December 15 1972 ASCII 4196 3 RFC0399 RFC0122 UNKNOWN UNKNOWN RFC0432 Network logical map N. Neigus December 29 1972 ASCII 1291 1 PDF 148880 PS 1344571 UNKNOWN UNKNOWN RFC0433 Socket number list J. Postel December 22 1972 ASCII 6834 5 RFC0349 RFC0503 UNKNOWN UNKNOWN RFC0434 IMP/TIP memory retrofit schedule A.M. McKenzie January 04 1973 ASCII 2242 2 RFC0447 UNKNOWN UNKNOWN RFC0435 Telnet issues B. Cosell D.C. Walden January 05 1973 ASCII 23019 10 RFC0318 UNKNOWN UNKNOWN RFC0436 Announcement of RJS at UCSB M. Krilanovich January 10 1973 ASCII 2579 1 UNKNOWN UNKNOWN RFC0437 Data Reconfiguration Service at UCSB E. Faeh June 30 1973 ASCII 21562 10 UNKNOWN UNKNOWN RFC0438 FTP server-server interaction R. Thomas R. Clements January 15 1973 ASCII 6514 3 UNKNOWN UNKNOWN RFC0439 PARRY encounters the DOCTOR V. Cerf January 21 1973 ASCII 7066 7 UNKNOWN UNKNOWN RFC0440 Scheduled network software maintenance D.C. Walden January 01 1973 ASCII 1870 1 UNKNOWN UNKNOWN RFC0441 Inter-Entity Communication - an experiment R.D. Bressler R. Thomas January 19 1973 ASCII 12876 7 UNKNOWN UNKNOWN RFC0442 Current flow-control scheme for IMPSYS V. Cerf January 24 1973 ASCII 16315 7 RFC0449 UNKNOWN UNKNOWN RFC0443 Traffic statistics (December 1972) A.M. McKenzie January 18 1973 ASCII 5664 3 UNKNOWN UNKNOWN RFC0444 RFC0445 IMP/TIP preventive maintenance schedule A.M. McKenzie January 22 1973 ASCII 2668 2 UNKNOWN UNKNOWN RFC0446 Proposal to consider a network program resource notebook L.P. Deutsch January 25 1973 ASCII 3053 2 UNKNOWN UNKNOWN RFC0447 IMP/TIP memory retrofit schedule A.M. McKenzie January 29 1973 ASCII 2332 2 RFC0434 RFC0476 UNKNOWN UNKNOWN RFC0448 Print files in FTP R.T. Braden February 27 1973 ASCII 6838 3 UNKNOWN UNKNOWN RFC0449 Current flow-control scheme for IMPSYS D.C. Walden January 06 1973 ASCII 1662 1 RFC0442 UNKNOWN UNKNOWN RFC0450 MULTICS sampling timeout change M.A. Padlipsky February 08 1973 ASCII 924 1 UNKNOWN UNKNOWN RFC0451 Tentative proposal for a Unified User Level Protocol M.A. Padlipsky February 22 1973 ASCII 8114 3 UNKNOWN UNKNOWN RFC0452 TELENET Command at Host LL J. Winett February 08 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0453 Meeting announcement to discuss a network mail system M.D. Kudlick February 07 1973 ASCII 4572 3 UNKNOWN UNKNOWN RFC0454 File Transfer Protocol - meeting announcement and a new proposed document A.M. McKenzie February 16 1973 ASCII 78966 35 FTP RFC0354 UNKNOWN UNKNOWN RFC0455 Traffic statistics (January 1973) A.M. McKenzie February 12 1973 ASCII 5746 3 UNKNOWN UNKNOWN RFC0456 Memorandum: Date change of mail meeting M.D. Kudlick February 13 1973 ASCII 950 1 UNKNOWN UNKNOWN RFC0457 TIPUG D.C. Walden February 15 1973 ASCII 845 1 UNKNOWN UNKNOWN RFC0458 Mail retrieval via FTP R.D. Bressler R. Thomas February 20 1973 ASCII 2705 2 UNKNOWN UNKNOWN RFC0459 Network questionnaires W. Kantrowitz February 26 1973 ASCII 1950 1 UNKNOWN UNKNOWN RFC0460 NCP survey C. Kline February 13 1973 ASCII 10324 7 UNKNOWN UNKNOWN RFC0461 Telnet Protocol meeting announcement A.M. McKenzie February 14 1973 ASCII 1966 1 UNKNOWN UNKNOWN RFC0462 Responding to user needs J. Iseli D. Crocker February 22 1973 ASCII 2808 2 UNKNOWN UNKNOWN RFC0463 FTP comments and response to RFC 430 A.K. Bhushan February 21 1973 ASCII 5729 3 UNKNOWN UNKNOWN RFC0464 Resource notebook framework M.D. Kudlick February 27 1973 ASCII 3684 2 UNKNOWN UNKNOWN RFC0465 RFC0466 Telnet logger/server for host LL-67 J.M. Winett February 27 1973 ASCII 17595 9 UNKNOWN UNKNOWN RFC0467 Proposed change to Host-Host Protocol: Resynchronization of connection status J.D. Burchfiel R.S. Tomlinson February 20 1973 ASCII 14325 7 RFC0492 UNKNOWN UNKNOWN RFC0468 FTP data compression R.T. Braden March 08 1973 ASCII 14909 7 UNKNOWN UNKNOWN RFC0469 Network mail meeting summary M.D. Kudlick March 08 1973 ASCII 17774 10 network mail meeting UNKNOWN UNKNOWN RFC0470 Change in socket for TIP news facility R. Thomas March 13 1973 ASCII 1014 1 UNKNOWN UNKNOWN RFC0471 Workshop on multi-site executive programs R. Thomas March 13 1973 ASCII 3339 2 UNKNOWN UNKNOWN RFC0472 Illinois' reply to Maxwell's request for graphics information (NIC 14925) S. Bunch March 01 1973 ASCII 4780 2 UNKNOWN UNKNOWN RFC0473 MIX and MIXAL? D.C. Walden February 28 1973 ASCII 868 1 UNKNOWN UNKNOWN RFC0474 Announcement of NGWG meeting: Call for papers S. Bunch March 01 1973 ASCII 1170 2 RFC0396 UNKNOWN UNKNOWN RFC0475 FTP and network mail system A.K. Bhushan March 06 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0476 IMP/TIP memory retrofit schedule (rev 2) A.M. McKenzie March 07 1973 ASCII 2281 2 RFC0447 UNKNOWN UNKNOWN RFC0477 Remote Job Service at UCSB M. Krilanovich May 23 1973 ASCII 40535 19 UNKNOWN UNKNOWN RFC0478 FTP server-server interaction - II R.D. Bressler R. Thomas March 26 1973 ASCII 4199 2 UNKNOWN UNKNOWN RFC0479 Use of FTP by the NIC Journal J.E. White March 08 1973 ASCII 11183 5 UNKNOWN UNKNOWN RFC0480 Host-dependent FTP parameters J.E. White March 08 1973 ASCII 2084 1 UNKNOWN UNKNOWN RFC0481 RFC0482 Traffic statistics (February 1973) A.M. McKenzie March 12 1973 ASCII 6162 4 UNKNOWN UNKNOWN RFC0483 Cancellation of the resource notebook framework meeting M.D. Kudlick March 14 1973 ASCII 1021 1 UNKNOWN UNKNOWN RFC0484 RFC0485 MIX and MIXAL at UCSB J.R. Pickens March 19 1973 ASCII 2226 1 UNKNOWN UNKNOWN RFC0486 Data transfer revisited R.D. Bressler March 20 1973 ASCII 4664 2 RJE FTP UNKNOWN UNKNOWN RFC0487 Free file transfer R.D. Bressler April 06 1973 ASCII 3249 2 FTP UNKNOWN UNKNOWN RFC0488 NLS classes at network sites M.F. Auerbach March 23 1973 ASCII 3806 2 UNKNOWN UNKNOWN RFC0489 Comment on resynchronization of connection status proposal J. Postel March 26 1973 ASCII 2010 1 UNKNOWN UNKNOWN RFC0490 Surrogate RJS for UCLA-CCN J.R. Pickens March 06 1973 ASCII 9858 6 UNKNOWN UNKNOWN RFC0491 What is "Free"? M.A. Padlipsky April 12 1973 ASCII 5872 2 UNKNOWN UNKNOWN RFC0492 Response to RFC 467 E. Meyer April 18 1973 ASCII 18791 7 RFC0467 UNKNOWN UNKNOWN RFC0493 Graphics Protocol J.C. Michener I.W. Cotton K.C. Kelley D.E. Liddle E. Meyer April 26 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0494 Availability of MIX and MIXAL in the Network D.C. Walden April 20 1973 ASCII 2007 1 UNKNOWN UNKNOWN RFC0495 Telnet Protocol specifications A.M. McKenzie May 01 1973 ASCII 4260 2 RFC0158 UNKNOWN UNKNOWN RFC0496 TNLS quick reference card is available M.F. Auerbach April 05 1973 ASCII 1110 1 UNKNOWN UNKNOWN RFC0497 Traffic statistics (March 1973) A.M. McKenzie April 10 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0498 On mail service to CCN R.T. Braden April 17 1973 ASCII 5315 3 UNKNOWN UNKNOWN RFC0499 Harvard's network RJE B.R. Reussow April 01 1973 ASCII 12584 6 UNKNOWN UNKNOWN RFC0500 Integration of data management systems on a computer network A. Shoshani I. Spiegler April 16 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0501 Un-muddling "free file transfer" K.T. Pogran May 11 1973 ASCII 13177 5 FTP UNKNOWN UNKNOWN RFC0502 RFC0503 Socket number list N. Neigus J. Postel April 12 1973 ASCII 8690 8 RFC0433 RFC0739 UNKNOWN UNKNOWN RFC0504 Distributed resources workshop announcement R. Thomas April 30 1973 ASCII 9061 5 UNKNOWN UNKNOWN RFC0505 Two solutions to a file transfer access problem M.A. Padlipsky June 25 1973 ASCII 7476 3 FTP free UNKNOWN UNKNOWN RFC0506 FTP command naming problem M.A. Padlipsky June 26 1973 ASCII 1974 1 UNKNOWN UNKNOWN RFC0507 RFC0508 Real-time data transmission on the ARPANET L. Pfeifer J. McAfee May 07 1973 ASCII 25002 10 UNKNOWN UNKNOWN RFC0509 Traffic statistics (April 1973) A.M. McKenzie April 07 1973 ASCII 6538 4 UNKNOWN UNKNOWN RFC0510 Request for network mailbox addresses J.E. White May 30 1973 ASCII 4150 2 UNKNOWN UNKNOWN RFC0511 Enterprise phone service to NIC from ARPANET sites J.B. North May 23 1973 ASCII 4664 4 UNKNOWN UNKNOWN RFC0512 More on lost message detection W. Hathaway May 23 1973 ASCII 3641 2 UNKNOWN UNKNOWN RFC0513 Comments on the new Telnet specifications W. Hathaway May 30 1973 ASCII 7980 3 UNKNOWN UNKNOWN RFC0514 Network make-work W. Kantrowitz June 05 1973 ASCII 8734 4 UNKNOWN UNKNOWN RFC0515 Specifications for datalanguage: Version 0/9 R. Winter June 06 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0516 Lost message detection J. Postel May 18 1973 ASCII 4086 2 UNKNOWN UNKNOWN RFC0517 RFC0518 ARPANET accounts N. Vaughan E.J. Feinler June 19 1973 ASCII 12880 9 UNKNOWN UNKNOWN RFC0519 Resource evaluation J.R. Pickens June 01 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0520 Memo to FTP group: Proposal for File Access Protocol J.D. Day June 25 1973 ASCII 16825 8 UNKNOWN UNKNOWN RFC0521 Restricted use of IMP DDT A.M. McKenzie May 30 1973 ASCII 3724 2 UNKNOWN UNKNOWN RFC0522 Traffic statistics (May 1973) A.M. McKenzie June 05 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0523 SURVEY is in operation again A.K. Bhushan June 05 1973 ASCII 2852 2 UNKNOWN UNKNOWN RFC0524 Proposed Mail Protocol J.E. White June 13 1973 ASCII 75385 40 UNKNOWN UNKNOWN RFC0525 MIT-MATHLAB meets UCSB-OLS -an example of resource sharing W. Parrish J.R. Pickens June 01 1973 ASCII 18501 9 PS 304440 PDF 228274 UNKNOWN UNKNOWN RFC0526 Technical meeting: Digital image processing software systems W.K. Pratt June 25 1973 ASCII 4062 3 UNKNOWN UNKNOWN RFC0527 ARPAWOCKY R. Merryman May 01 1973 ASCII 1857 1 UNKNOWN UNKNOWN RFC0528 Software checksumming in the IMP and network reliability J.M. McQuillan June 20 1973 ASCII 23152 9 UNKNOWN UNKNOWN RFC0529 Note on protocol synch sequences A.M. McKenzie R. Thomas R.S. Tomlinson K.T. Pogran June 29 1973 ASCII 9068 4 UNKNOWN UNKNOWN RFC0530 Report on the Survey project A.K. Bhushan June 22 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0531 Feast or famine? A response to two recent RFC's about network information M.A. Padlipsky June 26 1973 ASCII 5070 2 UNKNOWN UNKNOWN RFC0532 UCSD-CC Server-FTP facility R.G. Merryman July 12 1973 ASCII 7298 4 FTP server UNKNOWN UNKNOWN RFC0533 Message-ID numbers D.C. Walden July 17 1973 ASCII 2102 1 UNKNOWN UNKNOWN RFC0534 Lost message detection D.C. Walden July 17 1973 ASCII 3227 2 UNKNOWN UNKNOWN RFC0535 Comments on File Access Protocol R. Thomas July 25 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0536 RFC0537 Announcement of NGG meeting July 16-17 S. Bunch June 27 1973 ASCII 2695 2 UNKNOWN UNKNOWN RFC0538 Traffic statistics (June 1973) A.M. McKenzie July 05 1973 ASCII 6389 4 UNKNOWN UNKNOWN RFC0539 Thoughts on the mail protocol proposed in RFC 524 D. Crocker J. Postel July 07 1973 ASCII 6213 3 UNKNOWN UNKNOWN RFC0540 RFC0541 RFC0542 File Transfer Protocol N. Neigus August 12 1973 ASCII 100666 40 FTP RFC0354 RFC0765 RFC0614 RFC0640 RFC0454 RFC0495 UNKNOWN UNKNOWN RFC0543 Network journal submission and delivery N.D. Meyer July 24 1973 ASCII 15621 8 UNKNOWN UNKNOWN RFC0544 Locating on-line documentation at SRI-ARC N.D. Meyer K. Kelley July 13 1973 ASCII 1541 1 UNKNOWN UNKNOWN RFC0545 Of what quality be the UCSB resources evaluators? J.R. Pickens July 23 1973 ASCII 3754 2 UNKNOWN UNKNOWN RFC0546 Tenex load averages for July 1973 R. Thomas August 10 1973 ASCII 6632 4 PS 356023 PDF 268918 UNKNOWN UNKNOWN RFC0547 Change to the Very Distant Host specification D.C. Walden August 13 1973 ASCII 6236 3 UNKNOWN UNKNOWN RFC0548 Hosts using the IMP Going Down message D.C. Walden August 16 1973 ASCII 1435 1 UNKNOWN UNKNOWN RFC0549 Minutes of Network Graphics Group meeting, 15-17 July 1973 J.C. Michener July 17 1973 ASCII 23367 12 UNKNOWN UNKNOWN RFC0550 NIC NCP experiment L.P. Deutsch August 24 1973 ASCII 3688 2 UNKNOWN UNKNOWN RFC0551 NYU, ANL, and LBL Joining the Net Feinroth August 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0552 Single access to standard protocols A.D. Owen July 13 1973 ASCII 1404 1 UNKNOWN UNKNOWN RFC0553 Draft design for a text/graphics protocol C.H. Irby K. Victor July 14 1973 ASCII 35414 19 UNKNOWN UNKNOWN RFC0554 RFC0555 Responses to critiques of the proposed mail protocol J.E. White July 27 1973 ASCII 21521 11 UNKNOWN UNKNOWN RFC0556 Traffic statistics (July 1973) A.M. McKenzie August 13 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0557 Revelations in network host measurements B.D. Wessler August 30 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0558 RFC0559 Comments on The New Telnet Protocol and its Implementation A.K. Bushan August 15 1973 ASCII 10643 5 UNKNOWN UNKNOWN RFC0560 Remote Controlled Transmission and Echoing Telnet option D. Crocker J. Postel August 18 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0561 Standardizing Network Mail Headers A.K. Bhushan K.T. Pogran R.S. Tomlinson J.E. White September 05 1973 ASCII 6159 3 RFC0680 UNKNOWN UNKNOWN RFC0562 Modifications to the Telnet specification A.M. McKenzie August 28 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0563 Comments on the RCTE Telnet option J. Davidson August 28 1973 ASCII 10788 5 UNKNOWN UNKNOWN RFC0564 RFC0565 Storing network survey data at the datacomputer D. Cantor August 28 1973 ASCII 9307 5 UNKNOWN UNKNOWN RFC0566 Traffic statistics (August 1973) A.M. McKenzie September 04 1973 ASCII 6674 4 UNKNOWN UNKNOWN RFC0567 Cross Country Network Bandwidth L.P. Deutsch September 06 1973 ASCII 1529 1 RFC0568 UNKNOWN UNKNOWN RFC0568 Response to RFC 567 - cross country network bandwidth J.M. McQuillan September 18 1973 ASCII 3244 3 RFC0567 UNKNOWN UNKNOWN RFC0569 NETED: A Common Editor for the ARPA Network M.A. Padlipsky October 15 1973 ASCII 17717 6 NETED HISTORIC HISTORIC RFC0570 Experimental input mapping between NVT ASCII and UCSB On Line System J.R. Pickens October 30 1973 ASCII 177 1 PS 488023 PDF 375635 UNKNOWN UNKNOWN RFC0571 Tenex FTP problem R.T. Braden November 15 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0572 RFC0573 Data and file transfer: Some measurement results A.K. Bhushan September 14 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0574 Announcement of a mail facility at UCSB M. Krilanovich September 26 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0575 RFC0576 Proposal for modifying linking K. Victor September 26 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0577 Mail priority D. Crocker October 18 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0578 Using MIT-Mathlab MACSYMA from MIT-DMS Muddle A.K. Bhushan N.D. Ryan October 29 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0579 Traffic statistics (September 1973) A.M. McKenzie November 26 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0580 Note to Protocol Designers and Implementers J. Postel October 25 1973 ASCII 1451 1 RFC0582 UNKNOWN UNKNOWN RFC0581 Corrections to RFC 560: Remote Controlled Transmission and Echoing Telnet Option D. Crocker J. Postel November 02 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0582 Comments on RFC 580: Machine readable protocols R. Clements November 05 1973 ASCII 1635 1 RFC0580 UNKNOWN UNKNOWN RFC0583 RFC0584 Charter for ARPANET Users Interest Working Group J. Iseli D. Crocker N. Neigus November 06 1973 ASCII 3461 3 UNKNOWN UNKNOWN RFC0585 ARPANET users interest working group meeting D. Crocker N. Neigus E.J. Feinler J. Iseli November 06 1973 ASCII 18243 9 UNKNOWN UNKNOWN RFC0586 Traffic statistics (October 1973) A.M. McKenzie November 08 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0587 Announcing new Telnet options J. Postel November 13 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0588 London node is now up A.V. Stokes October 29 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0589 CCN NETRJS server messages to remote user R.T. Braden November 26 1973 ASCII 7998 5 UNKNOWN UNKNOWN RFC0590 MULTICS address change M.A. Padlipsky November 19 1973 ASCII 1436 1 UNKNOWN UNKNOWN RFC0591 Addition to the Very Distant Host specifications D.C. Walden November 29 1973 ASCII 901 1 UNKNOWN UNKNOWN RFC0592 Some thoughts on system design to facilitate resource sharing R.W. Watson November 20 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0593 Telnet and FTP implementation schedule change A.M. McKenzie J. Postel November 29 1973 ASCII 2506 1 UNKNOWN UNKNOWN RFC0594 Speedup of Host-IMP interface J.D. Burchfiel December 10 1973 Not Available Online.. UNKNOWN UNKNOWN RFC0595 Second thoughts in defense of the Telnet Go-Ahead W. Hathaway December 12 1973 ASCII 13507 5 UNKNOWN UNKNOWN RFC0596 Second thoughts on Telnet Go-Ahead E.A. Taft December 08 1973 ASCII 11919 5 UNKNOWN UNKNOWN RFC0597 Host status N. Neigus E.J. Feinler December 12 1973 ASCII 11678 6 RFC0603 UNKNOWN UNKNOWN RFC0598 RFC index - December 5, 1973 Network Information Center. Stanford Research Institute December 05 1973 Not Available Online UNKNOWN UNKNOWN RFC0599 Update on NETRJS R.T. Braden December 13 1973 ASCII 16590 9 RFC0189 RFC0740 UNKNOWN UNKNOWN RFC0600 Interfacing an Illinois plasma terminal to the ARPANET A. Berggreen November 26 1973 Discusses some unusual interface issues for the Plato terminal. Not Available Online.. UNKNOWN UNKNOWN RFC0601 Traffic statistics (November 1973) A.M. McKenzie December 14 1973 ASCII 9100 5 UNKNOWN UNKNOWN RFC0602 "The stockings were hung by the chimney with care" R.M. Metcalfe December 27 1973 ASCII 1988 1 security violations TIP arpanet Susceptibility of ARPANET to security violations. UNKNOWN UNKNOWN RFC0603 Response to RFC 597: Host status J.D. Burchfiel December 31 1973 ASCII 1482 1 Questions about the ARPANET topology described in RFC 597. RFC0597 RFC0613 UNKNOWN UNKNOWN RFC0604 Assigned link numbers J. Postel December 26 1973 ASCII 2758 2 Modifies official host-host protocol. Replaces RFC 377. RFC0317 RFC0739 UNKNOWN UNKNOWN RFC0605 RFC0606 Host names on-line L.P. Deutsch December 29 1973 ASCII 6855 3 lists names host addresses Resolving differences in hostname-address mappings; see also RFCs 627, 625, 623 and 608. UNKNOWN UNKNOWN RFC0607 Comments on the File Transfer Protocol M. Krilanovich G. Gregg January 07 1974 ASCII 8652 3 solutions weakness ftp An old version; see RFC 624; see also RFCs 614, 542 and 640. RFC0624 RFC0614 UNKNOWN UNKNOWN RFC0608 Host names on-line M.D. Kudlick January 10 1974 ASCII 7010 4 Response to RFC 606; see also RFCs 627, 625 and 623. RFC0810 UNKNOWN UNKNOWN RFC0609 Statement of upcoming move of NIC/NLS service B. Ferguson January 10 1974 ASCII 1260 2 See also RFCs 621 and 620. UNKNOWN UNKNOWN RFC0610 Further datalanguage design concepts R. Winter J. Hill W. Greiff December 15 1973 ASCII 198692 88 Preliminary results of the language design; a model for data languagea semantics; future considerations. UNKNOWN UNKNOWN RFC0611 Two changes to the IMP/Host Protocol to improve user/network communications D.C. Walden February 14 1974 ASCII 7481 4 Expansion of Host-Going-Down and addition of Dead-Host-Status Message. UNKNOWN UNKNOWN RFC0612 Traffic statistics (December 1973) A.M. McKenzie January 16 1974 ASCII 9667 6 UNKNOWN UNKNOWN RFC0613 Network connectivity: A response to RFC 603 A.M. McKenzie January 21 1974 ASCII 2557 1 RFC0603 UNKNOWN UNKNOWN RFC0614 Response to RFC 607: "Comments on the File Transfer Protocol" K.T. Pogran N. Neigus January 28 1974 ASCII 11409 3 ftp weakness solutions See also RFCs 624, 542 and 640. RFC0542 RFC0607 UNKNOWN UNKNOWN RFC0615 Proposed Network Standard Data Pathname syntax D. Crocker March 01 1974 ASCII 9448 4 UNKNOWN UNKNOWN RFC0616 Latest network maps D.C. Walden February 11 1973 Network maps Not Available Online.. UNKNOWN UNKNOWN RFC0617 Note on socket number assignment E.A. Taft February 19 1974 ASCII 8062 3 telnet Danger of imposing more fixed socket number requirements; see also RFCs 542, 503 and 451. UNKNOWN UNKNOWN RFC0618 Few observations on NCP statistics E.A. Taft February 19 1974 ASCII 4929 3 Distribution of NCP and IMP message types by actual measurement. UNKNOWN UNKNOWN RFC0619 Mean round-trip times in the ARPANET W. Naylor H. Opderbeck March 07 1974 ASCII 30946 14 Actual measurements of round-trip times. UNKNOWN UNKNOWN RFC0620 Request for monitor host table updates B. Ferguson March 01 1974 ASCII 1950 1 tenex In conjunction with moving NIC users to OFFICE-1; see also RFCs 621 and 609. UNKNOWN UNKNOWN RFC0621 NIC user directories at SRI ARC M.D. Kudlick March 06 1974 ASCII 1351 1 See also RFCs 620 and 609. UNKNOWN UNKNOWN RFC0622 Scheduling IMP/TIP down time A.M. McKenzie March 13 1974 ASCII 4367 3 Modification of previous policy. UNKNOWN UNKNOWN RFC0623 Comments on on-line host name service M. Krilanovich February 22 1974 ASCII 3740 2 See also RFCs 627, 625, 608 and 606. UNKNOWN UNKNOWN RFC0624 Comments on the File Transfer Protocol M. Krilanovich G. Gregg W. Hathaway J.E. White February 28 1974 ASCII 10105 3 ftp telnet Design changes and slight modifications. Replaces RFC 607; see also RFCs 614, 542 and 640. RFC0607 UNKNOWN UNKNOWN RFC0625 On-line hostnames service M.D. Kudlick E.J. Feinler March 07 1974 ASCII 2172 1 See also RFCs 606, 608, 623 and 627. UNKNOWN UNKNOWN RFC0626 On a possible lockup condition in IMP subnet due to message sequencing L. Kleinrock H. Opderbeck March 14 1974 ASCII 13150 5 UNKNOWN UNKNOWN RFC0627 ASCII text file of hostnames M.D. Kudlick E.J. Feinler March 25 1974 ASCII 2007 1 See also RFCs 606, 608, 623 and 625. UNKNOWN UNKNOWN RFC0628 Status of RFC numbers and a note on pre-assigned journal numbers M.L. Keeney March 27 1974 ASCII 1036 1 UNKNOWN UNKNOWN RFC0629 Scenario for using the Network Journal J.B. North March 27 1974 ASCII 4504 3 UNKNOWN UNKNOWN RFC0630 FTP error code usage for more reliable mail service J. Sussman April 10 1974 ASCII 4070 3 Describes FTP reply-code usage in TENEX mail processing. UNKNOWN UNKNOWN RFC0631 International meeting on minicomputers and data communication: Call for papers A. Danthine April 17 1974 ASCII 2707 2 UNKNOWN UNKNOWN RFC0632 Throughput degradations for single packet messages H. Opderbeck May 20 1974 ASCII 14563 6 UNKNOWN UNKNOWN RFC0633 IMP/TIP preventive maintenance schedule A.M. McKenzie March 18 1974 ASCII 3733 4 An old version; see RFC 638. RFC0638 UNKNOWN UNKNOWN RFC0634 Change in network address for Haskins Lab A.M. McKenzie April 10 1974 ASCII 1098 1 UNKNOWN UNKNOWN RFC0635 Assessment of ARPANET protocols V. Cerf April 22 1974 Theoretical and practical motivation for redesign. Multipacket messages; host retransmission; duplicate detection; sequencing; acknowledgement. Not Available Online.. UNKNOWN UNKNOWN RFC0636 TIP/Tenex reliability improvements J.D. Burchfiel B. Cosell R.S. Tomlinson D.C. Walden June 10 1974 ASCII 19914 8 Obtaining/maintaining connections; recovery from lost connections; connection-state changes. UNKNOWN UNKNOWN RFC0637 Change of network address for SU-DSL A.M. McKenzie April 23 1974 ASCII 916 1 UNKNOWN UNKNOWN RFC0638 IMP/TIP preventive maintenance schedule A.M. McKenzie April 25 1974 ASCII 4088 4 Corrects RFC 633. RFC0633 UNKNOWN UNKNOWN RFC0639 RFC0640 Revised FTP reply codes J. Postel June 19 1974 ASCII 39670 17 Updates RFC 542. RFC0542 UNKNOWN UNKNOWN RFC0641 RFC0642 Ready line philosophy and implementation J.D. Burchfiel July 05 1974 ASCII 8414 4 UNKNOWN UNKNOWN RFC0643 Network Debugging Protocol E. Mader July 01 1974 ASCII 12563 7 To be used in an implementation of a PDP-11 network bootstrap device and a cross-network debugger. UNKNOWN UNKNOWN RFC0644 On the problem of signature authentication for network mail R. Thomas July 22 1974 ASCII 9501 3 UNKNOWN UNKNOWN RFC0645 Network Standard Data Specification syntax D. Crocker June 26 1974 Providing a mechanism for specifying all attributes of a collection of bits; see also RFC 615. Not Available Online.. UNKNOWN UNKNOWN RFC0646 RFC0647 Proposed protocol for connecting host computers to ARPA-like networks via front end processors M.A. Padlipsky November 12 1974 Approaches to Front-End protocol processing using available hardware and software. Not Available Online.. UNKNOWN UNKNOWN RFC0648 RFC0649 RFC0650 RFC0651 Revised Telnet status option D. Crocker October 25 1974 ASCII 4360 2 RFC0859 UNKNOWN UNKNOWN RFC0652 Telnet output carriage-return disposition option D. Crocker October 25 1974 ASCII 7003 4 TOPT-OCRD HISTORIC PROPOSED STANDARD RFC0653 Telnet output horizontal tabstops option D. Crocker October 25 1974 ASCII 4694 1 TOPT-OHT HISTORIC PROPOSED STANDARD RFC0654 Telnet output horizontal tab disposition option D. Crocker October 25 1974 ASCII 6158 1 TOPT-OHTD HISTORIC PROPOSED STANDARD RFC0655 Telnet output formfeed disposition option D. Crocker October 25 1974 ASCII 5991 1 TOPT-OFD HISTORIC PROPOSED STANDARD RFC0656 Telnet output vertical tabstops option D. Crocker October 25 1974 ASCII 4858 1 TOPT-OVT HISTORIC PROPOSED STANDARD RFC0657 Telnet output vertical tab disposition option D. Crocker October 25 1974 ASCII 5759 1 TOPT-OVTD HISTORIC PROPOSED STANDARD RFC0658 Telnet output linefeed disposition D. Crocker October 25 1974 ASCII 6484 2 TOPT-OLD HISTORIC PROPOSED STANDARD RFC0659 Announcing additional Telnet options J. Postel October 18 1974 ASCII 2016 1 Options defined in RFCs 651-658. UNKNOWN UNKNOWN RFC0660 Some changes to the IMP and the IMP/Host interface D.C. Walden October 23 1974 ASCII 4991 1 Decoupling of message number sequences of hosts; host-host access control; message number window; messages outside normal mechanism; see also BBN 1822. UNKNOWN UNKNOWN RFC0661 Protocol information J. Postel November 23 1974 An old version; see RFC 694. Not Available Online.. UNKNOWN UNKNOWN RFC0662 Performance improvement in ARPANET file transfers from Multics R. Kanodia November 26 1974 ASCII 8872 2 Experimenting with host output buffers to improve throughput. UNKNOWN UNKNOWN RFC0663 Lost message detection and recovery protocol R. Kanodia November 29 1974 ASCII 44702 22 ARPANET Host Proposed extension of host-host protocol; see also RFCs 534, 516, 512, 492 and 467. UNKNOWN UNKNOWN RFC0664 RFC0665 RFC0666 Specification of the Unified User-Level Protocol M.A. Padlipsky November 26 1974 Discusses and proposes a common command language. Not Available Online.. UNKNOWN UNKNOWN RFC0667 BBN host ports S.G. Chipman December 17 1974 Approved scheme to connect host ports to the network. Not Available Online.. UNKNOWN UNKNOWN RFC0668 RFC0669 November, 1974, survey of New-Protocol Telnet servers D.W. Dodds December 04 1974 An earlier poll of Telnet server implementation status. Updates RFC 702; see also RFCs 703 and 679. Not Available Online.. UNKNOWN UNKNOWN RFC0670 RFC0671 Note on Reconnection Protocol R. Schantz December 06 1974 Experience with implementation in RSEXEC context. Not Available Online.. UNKNOWN UNKNOWN RFC0672 Multi-site data collection facility R. Schantz December 06 1974 ASCII 25736 9 Applicability of TIP/TENEX protocols beyond TIP accounting. UNKNOWN UNKNOWN RFC0673 RFC0674 Procedure call documents: Version 2 J. Postel J.E. White December 12 1974 ASCII 12178 6 Host level protocol used in the NSW--a slightly constrained version of ARPANET Host-to-Host protocol, affecting allocation, RFNM wait, and retransmission; see also RFC 684. UNKNOWN UNKNOWN RFC0675 Specification of Internet Transmission Control Program V. Cerf Y. Dalal C. Sunshine December 01 1974 ASCII 156874 70 The first detailed specification of TCP; see RFC 793. UNKNOWN UNKNOWN RFC0676 RFC0677 Maintenance of duplicate databases P.R. Johnson R. Thomas January 27 1975 ASCII 22990 10 UNKNOWN UNKNOWN RFC0678 Standard file formats J. Postel December 19 1974 ASCII 12393 9 For transmission of documents across different environments. UNKNOWN UNKNOWN RFC0679 February, 1975, survey of New-Protocol Telnet servers D.W. Dodds February 21 1975 An earlier poll of Telnet server implementation status. Updates RFCs 701, 702 and 669; see also RFC 703. Not Available Online.. UNKNOWN UNKNOWN RFC0680 Message Transmission Protocol T.H. Myer D.A. Henderson April 30 1975 Extends message field definition beyond RFC 561 attempts to establish syntactic and semantic standards for ARPANET; see also RFCs 733 and 822. Not Available Online.. RFC0561 UNKNOWN UNKNOWN RFC0681 Network UNIX S. Holmgren March 18 1975 ASCII 18874 8 Capabilities as an ARPANET Mini-Host: standard I/O, Telnet, NCP, Hardware/Software requirements, reliability, availability. UNKNOWN UNKNOWN RFC0682 RFC0683 FTPSRV - Tenex extension for paged files R. Clements April 03 1975 ASCII 8806 3 FTP paged file transfer Tenex Defines an extension to FTP for page-mode transfers between TENEX systems; also discusses file transfer reliability. RFC0354 UNKNOWN UNKNOWN RFC0684 Commentary on procedure calling as a network protocol R. Schantz April 15 1975 ASCII 21164 9 Issues in designing distributed computing systems. Shortcomings of RFC 674; see also RFCs 542 and 354. UNKNOWN UNKNOWN RFC0685 Response time in cross network debugging M. Beeler April 16 1975 ASCII 6914 3 The contribution of ARPANET communication to response time. UNKNOWN UNKNOWN RFC0686 Leaving well enough alone B. Harvey May 10 1975 ASCII 24605 9 Discusses difference between early and later versions of FTP; see also RFCs 691, 640, 630, 542, 454, 448, 414, 385 and 354. UNKNOWN UNKNOWN RFC0687 IMP/Host and Host/IMP Protocol changes D.C. Walden June 02 1975 ASCII 6013 2 Addressing hosts on more than 63 IMPs, and other backwards compatible expansions; see also RFCs 690 and 692. RFC0704 RFC0690 UNKNOWN UNKNOWN RFC0688 Tentative schedule for the new Telnet implementation for the TIP D.C. Walden June 04 1975 ASCII 1593 1 UNKNOWN UNKNOWN RFC0689 Tenex NCP finite state machine for connections R. Clements May 23 1975 ASCII 13101 5 Describes the internal states of an NCP connection in the TENEX implementation. UNKNOWN UNKNOWN RFC0690 Comments on the proposed Host/IMP Protocol changes J. Postel June 06 1975 ASCII 7215 3 Comments on suggestions in RFC 687; see also RFCs 692 and 696. RFC0687 RFC0692 UNKNOWN UNKNOWN RFC0691 One more try on the FTP B. Harvey June 06 1975 ASCII 32821 14 Slight revision of RFC 686, on the subject of print files; see also RFCs 640, 630, 542, 454, 448, 414, 385 and 354. UNKNOWN UNKNOWN RFC0692 Comments on IMP/Host Protocol changes (RFCs 687 and 690) S.M. Wolfe June 20 1975 ASCII 2681 2 A proposed solution to the problem of combined length of IMP and Host leaders; see also RFCs 696, 690 and 687. RFC0690 UNKNOWN UNKNOWN RFC0693 RFC0694 Protocol information J. Postel June 18 1975 References to documents and contacts concerning the various protocols used in the ARPANET, as well as recent developments; updates RFC 661. Not Available Online.. UNKNOWN UNKNOWN RFC0695 Official change in Host-Host Protocol M. Krilanovich July 05 1975 ASCII 3425 3 Corrects ambiguity concerning the ERR command; changes NIC 8246 and NIC 7104. UNKNOWN UNKNOWN RFC0696 Comments on the IMP/Host and Host/IMP Protocol changes V.G. Cerf July 13 1975 Observations on current international standards recommendations from IFIP working group 6.1; see also RFCs 692, 690 687. Not Available Online.. UNKNOWN UNKNOWN RFC0697 CWD command of FTP J. Lieb July 14 1975 ASCII 3047 2 Discusses FTP login access to "files only" directories. UNKNOWN UNKNOWN RFC0698 Telnet extended ASCII option T. Mock July 23 1975 ASCII 5086 3 TOPT-EXT Describes an option to allow transmission of a special kind of extended ASCII used at the Stanford AI and MIT AI Labs. PROPOSED STANDARD PROPOSED STANDARD RFC0699 Request For Comments summary notes: 600-699 J. Postel J. Vernon November 01 1982 ASCII 14688 9 INFORMATIONAL INFORMATIONAL RFC0700 Protocol experiment E. Mader W.W. Plummer R.S. Tomlinson August 01 1974 ASCII 14600 7 UNKNOWN UNKNOWN RFC0701 August, 1974, survey of New-Protocol Telnet servers D.W. Dodds August 01 1974 ASCII 3549 1 UNKNOWN UNKNOWN RFC0702 September, 1974, survey of New-Protocol Telnet servers D.W. Dodds September 25 1974 ASCII 5386 3 UNKNOWN UNKNOWN RFC0703 July, 1975, survey of New-Protocol Telnet Servers D.W. Dodds July 11 1975 ASCII 5691 3 UNKNOWN UNKNOWN RFC0704 IMP/Host and Host/IMP Protocol change P.J. Santos September 15 1975 ASCII 7504 2 RFC0687 UNKNOWN UNKNOWN RFC0705 Front-end Protocol B6700 version R.F. Bryan November 05 1975 ASCII 70998 39 UNKNOWN UNKNOWN RFC0706 On the junk mail problem J. Postel November 08 1975 ASCII 2085 1 UNKNOWN UNKNOWN RFC0707 High-level framework for network-based resource sharing J.E. White December 23 1975 ASCII 57254 29 UNKNOWN UNKNOWN RFC0708 Elements of a Distributed Programming System J.E. White January 28 1976 ASCII 57888 30 UNKNOWN UNKNOWN RFC0709 RFC0710 RFC0711 RFC0712 Distributed Capability Computing System (DCCS) J.E. Donnelley February 05 1976 Not Available Online.. UNKNOWN UNKNOWN RFC0713 MSDTP-Message Services Data Transmission Protocol J. Haverty April 06 1976 ASCII 41175 21 UNKNOWN UNKNOWN RFC0714 Host-Host Protocol for an ARPANET-Type Network A.M. McKenzie April 21 1976 Not Available Online. UNKNOWN UNKNOWN RFC0715 RFC0716 Interim Revision to Appendix F of BBN 1822 D.C. Walden J. Levin May 24 1976 ASCII 3345 1 UNKNOWN UNKNOWN RFC0717 Assigned Network Numbers J. Postel July 01 1976 ASCII 2322 1 HISTORIC UNKNOWN RFC0718 Comments on RCTE from the Tenex Implementation Experience J. Postel June 30 1976 ASCII 3829 1 UNKNOWN UNKNOWN RFC0719 Discussion on RCTE J. Postel July 22 1976 ASCII 4708 1 UNKNOWN UNKNOWN RFC0720 Address Specification Syntax for Network Mail D. Crocker August 05 1976 ASCII 6602 3 UNKNOWN UNKNOWN RFC0721 Out-of-Band Control Signals in a Host-to-Host Protocol L.L. Garlick September 01 1976 ASCII 13566 7 UNKNOWN UNKNOWN RFC0722 Thoughts on Interactions in Distributed Services J. Haverty September 16 1976 ASCII 29478 13 UNKNOWN UNKNOWN RFC0723 RFC0724 Proposed official standard for the format of ARPA Network messages D. Crocker K.T. Pogran J. Vittal D.A. Henderson May 12 1977 ASCII 75554 36 RFC0733 UNKNOWN UNKNOWN RFC0725 RJE protocol for a resource sharing network J.D. Day G.R. Grossman March 01 1977 ASCII 44025 27 UNKNOWN UNKNOWN RFC0726 Remote Controlled Transmission and Echoing Telnet option J. Postel D. Crocker March 08 1977 ASCII 38651 16 TOPT-REM PROPOSED STANDARD PROPOSED STANDARD RFC0727 Telnet logout option M.R. Crispin April 27 1977 ASCII 5674 3 TOPT-LOGO PROPOSED STANDARD PROPOSED STANDARD RFC0728 Minor pitfall in the Telnet Protocol J.D. Day April 27 1977 ASCII 2224 1 UNKNOWN UNKNOWN RFC0729 Telnet byte macro option D. Crocker May 13 1977 ASCII 6509 3 RFC0735 UNKNOWN UNKNOWN RFC0730 Extensible field addressing J. Postel May 20 1977 ASCII 9519 5 UNKNOWN UNKNOWN RFC0731 Telnet Data Entry Terminal option J.D. Day June 27 1977 ASCII 61648 28 RFC0732 UNKNOWN UNKNOWN RFC0732 Telnet Data Entry Terminal option J.D. Day September 12 1977 ASCII 57160 30 RFC0731 RFC1043 UNKNOWN UNKNOWN RFC0733 Standard for the format of ARPA network text messages D. Crocker J. Vittal K.T. Pogran D.A. Henderson November 21 1977 ASCII 73006 38 RFC0724 RFC0822 UNKNOWN UNKNOWN RFC0734 SUPDUP Protocol M.R. Crispin October 07 1977 ASCII 33256 13 SUPDUP HISTORIC HISTORIC RFC0735 Revised Telnet byte macro option D. Crocker R.H. Gumpertz November 03 1977 ASCII 10585 5 TOPT-BYTE RFC0729 PROPOSED STANDARD PROPOSED STANDARD RFC0736 Telnet SUPDUP option M.R. Crispin October 31 1977 ASCII 3081 1 TOPT-SUP PROPOSED STANDARD PROPOSED STANDARD RFC0737 FTP extension: XSEN K. Harrenstien October 31 1977 ASCII 2127 1 UNKNOWN UNKNOWN RFC0738 Time server K. Harrenstien October 31 1977 ASCII 1851 1 UNKNOWN UNKNOWN RFC0739 Assigned numbers J. Postel November 11 1977 ASCII 16346 11 RFC0604 RFC0503 RFC0750 HISTORIC UNKNOWN RFC0740 NETRJS Protocol R.T. Braden November 22 1977 ASCII 38833 19 NETRJS RFC0599 HISTORIC HISTORIC RFC0741 Specifications for the Network Voice Protocol (NVP) D. Cohen November 22 1977 ASCII 57581 34 UNKNOWN UNKNOWN RFC0742 NAME/FINGER Protocol K. Harrenstien December 30 1977 ASCII 12321 7 RFC1288 RFC1196 RFC1194 UNKNOWN UNKNOWN RFC0743 FTP extension: XRSQ/XRCP K. Harrenstien December 30 1977 ASCII 16249 8 UNKNOWN UNKNOWN RFC0744 MARS - a Message Archiving and Retrieval Service J. Sattley January 08 1978 ASCII 10984 6 UNKNOWN UNKNOWN RFC0745 JANUS interface specifications M. Beeler March 30 1978 ASCII 21453 10 JANUS interface specifications UNKNOWN UNKNOWN RFC0746 SUPDUP graphics extension R. Stallman March 17 1978 ASCII 30197 15 UNKNOWN UNKNOWN RFC0747 Recent extensions to the SUPDUP Protocol M.R. Crispin March 21 1978 ASCII 2870 1 UNKNOWN UNKNOWN RFC0748 Telnet randomly-lose option M.R. Crispin April 01 1978 ASCII 2741 2 UNKNOWN UNKNOWN RFC0749 Telnet SUPDUP-Output option B. Greenberg September 18 1978 ASCII 8933 4 TOPT-SUPO PROPOSED STANDARD PROPOSED STANDARD RFC0750 Assigned numbers J. Postel September 26 1978 ASCII 19979 12 RFC0739 RFC0755 HISTORIC UNKNOWN RFC0751 Survey of FTP mail and MLFL P.D. Lebling December 10 1978 ASCII 10069 5 UNKNOWN UNKNOWN RFC0752 Universal host table M.R. Crispin January 02 1979 ASCII 33793 12 UNKNOWN UNKNOWN RFC0753 Internet Message Protocol J. Postel March 01 1979 ASCII 93363 62 UNKNOWN UNKNOWN RFC0754 Out-of-net host addresses for mail J. Postel April 06 1979 ASCII 19212 10 UNKNOWN UNKNOWN RFC0755 Assigned numbers J. Postel May 03 1979 ASCII 22039 12 RFC0750 RFC0758 HISTORIC UNKNOWN RFC0756 NIC name server - a datagram-based information utility J.R. Pickens E.J. Feinler J.E. Mathis July 01 1979 ASCII 23491 12 UNKNOWN UNKNOWN RFC0757 Suggested solution to the naming, addressing, and delivery problem for ARPANET message systems D.P. Deutsch September 10 1979 ASCII 35618 19 UNKNOWN UNKNOWN RFC0758 Assigned numbers J. Postel August 01 1979 ASCII 22911 12 RFC0755 RFC0762 HISTORIC UNKNOWN RFC0759 Internet Message Protocol J. Postel August 01 1980 ASCII 123606 77 MPM HISTORIC HISTORIC RFC0760 DoD standard Internet Protocol J. Postel January 01 1980 ASCII 81507 46 IEN123 RFC0791 RFC0777 UNKNOWN UNKNOWN RFC0761 DoD standard Transmission Control Protocol J. Postel January 01 1980 ASCII 167049 88 TCP UNKNOWN UNKNOWN RFC0762 Assigned numbers J. Postel January 01 1980 ASCII 24668 13 RFC0758 RFC0770 HISTORIC UNKNOWN RFC0763 Role mailboxes M.D. Abrams May 07 1980 ASCII 942 1 UNKNOWN UNKNOWN RFC0764 Telnet Protocol specification J. Postel June 01 1980 ASCII 40005 15 RFC0854 UNKNOWN UNKNOWN RFC0765 File Transfer Protocol specification J. Postel June 01 1980 ASCII 146641 70 RFC0542 RFC0959 UNKNOWN UNKNOWN RFC0766 Internet Protocol Handbook: Table of contents J. Postel July 01 1980 ASCII 3465 2 RFC0774 UNKNOWN UNKNOWN RFC0767 Structured format for transmission of multi-media documents J. Postel August 01 1980 ASCII 59971 40 UNKNOWN UNKNOWN RFC0768 User Datagram Protocol J. Postel August 28 1980 ASCII 5896 3 UDP UDP STD0006 STANDARD STANDARD RFC0769 Rapicom 450 facsimile file format J. Postel September 26 1980 ASCII 4079 2 UNKNOWN UNKNOWN RFC0770 Assigned numbers J. Postel September 01 1980 ASCII 26248 15 RFC0762 RFC0776 HISTORIC UNKNOWN RFC0771 Mail transition plan V.G. Cerf J. Postel September 01 1980 ASCII 18623 9 UNKNOWN UNKNOWN RFC0772 Mail Transfer Protocol S. Sluizer J. Postel September 01 1980 ASCII 61061 31 MTP email RFC0780 UNKNOWN UNKNOWN RFC0773 Comments on NCP/TCP mail service transition strategy V.G. Cerf October 01 1980 ASCII 22181 11 UNKNOWN UNKNOWN RFC0774 Internet Protocol Handbook: Table of contents J. Postel October 01 1980 ASCII 3452 3 RFC0766 UNKNOWN UNKNOWN RFC0775 Directory oriented FTP commands D. Mankins D. Franklin A.D. Owen December 01 1980 ASCII 9511 6 UNKNOWN UNKNOWN RFC0776 Assigned numbers J. Postel January 01 1981 ASCII 30311 13 RFC0770 RFC0790 HISTORIC UNKNOWN RFC0777 Internet Control Message Protocol J. Postel April 01 1981 ASCII 19407 14 RFC0792 RFC0760 UNKNOWN UNKNOWN RFC0778 DCNET Internet Clock Service D.L. Mills April 18 1981 ASCII 9464 4 CLOCK HISTORIC HISTORIC RFC0779 Telnet send-location option E. Killian April 01 1981 ASCII 2564 2 TOPT-SNDL PROPOSED STANDARD PROPOSED STANDARD RFC0780 Mail Transfer Protocol S. Sluizer J. Postel May 01 1981 ASCII 80352 47 MTP email RFC0772 RFC0788 UNKNOWN UNKNOWN RFC0781 Specification of the Internet Protocol (IP) timestamp option Z. Su May 01 1981 ASCII 4002 1 UNKNOWN UNKNOWN RFC0782 Virtual Terminal management model J. Nabielsky A.P. Skelton January 01 1981 ASCII 43589 23 UNKNOWN UNKNOWN RFC0783 TFTP Protocol (revision 2) K.R. Sollins June 01 1981 ASCII 23522 18 IEN133 RFC1350 UNKNOWN UNKNOWN RFC0784 Mail Transfer Protocol: ISI TOPS20 implementation S. Sluizer J. Postel July 01 1981 ASCII 5856 3 MTP email UNKNOWN UNKNOWN RFC0785 Mail Transfer Protocol: ISI TOPS20 file definitions S. Sluizer J. Postel July 01 1981 ASCII 7032 3 MTP email UNKNOWN UNKNOWN RFC0786 Mail Transfer Protocol: ISI TOPS20 MTP-NIMAIL interface S. Sluizer J. Postel July 01 1981 ASCII 3129 2 MTP NIMAIL TOPS20 UNKNOWN UNKNOWN RFC0787 Connectionless data transmission survey/tutorial A.L. Chapin July 01 1981 ASCII 84265 40 UNKNOWN UNKNOWN RFC0788 Simple Mail Transfer Protocol J. Postel November 01 1981 ASCII 109001 64 SMTP email RFC0780 RFC0821 UNKNOWN UNKNOWN RFC0789 Vulnerabilities of network control protocols: An example E.C. Rosen July 01 1981 ASCII 25541 16 UNKNOWN UNKNOWN RFC0790 Assigned numbers J. Postel September 01 1981 ASCII 35316 15 RFC0776 RFC0820 HISTORIC UNKNOWN RFC0791 Internet Protocol J. Postel September 01 1981 ASCII 97779 51 IP RFC0760 RFC1349 STD0005 STANDARD STANDARD RFC0792 Internet Control Message Protocol J. Postel September 01 1981 ASCII 30404 21 ICMP RFC0777 RFC0950 STD0005 STANDARD STANDARD RFC0793 Transmission Control Protocol J. Postel September 01 1981 ASCII 172710 91 TCP TCP RFC3168 STD0007 STANDARD STANDARD RFC0794 Pre-emption V.G. Cerf September 01 1981 ASCII 5906 2 IEN125 UNKNOWN UNKNOWN RFC0795 Service mappings J. Postel September 01 1981 ASCII 5228 4 UNKNOWN UNKNOWN RFC0796 Address mappings J. Postel September 01 1981 ASCII 11239 7 IEN115 UNKNOWN UNKNOWN RFC0797 Format for Bitmap files A.R. Katz September 01 1981 ASCII 3067 2 UNKNOWN UNKNOWN RFC0798 Decoding facsimile data from the Rapicom 450 A.R. Katz September 01 1981 ASCII 38867 17 UNKNOWN UNKNOWN RFC0799 Internet name domains D.L. Mills September 01 1981 ASCII 13896 5 UNKNOWN UNKNOWN RFC0800 Request For Comments summary notes: 700-799 J. Postel J. Vernon November 01 1982 ASCII 18354 10 This RFC is a slightly annotated list of the 100 RFCs from RFC 700 through RFC 799. This is a status report on these RFCs. INFORMATIONAL INFORMATIONAL RFC0801 NCP/TCP transition plan J. Postel November 01 1981 ASCII 42041 21 This RFC discusses the conversion of hosts from NCP to TCP. And making available the principle services: Telnet, File Transfer, and Mail. These protocols allow all hosts in the ARPA community to share a common interprocess communication environment. UNKNOWN UNKNOWN RFC0802 ARPANET 1822L Host Access Protocol A.G. Malis November 01 1981 ASCII 62470 45 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. RFC0851 UNKNOWN UNKNOWN RFC0803 Dacom 450/500 facsimile data transcoding A. Agarwal M.J. O'Connor D.L. Mills November 02 1981 ASCII 33826 14 The first part of this RFC describes in detail the Dacom 450 data compression algorithms and is an update and correction to an earlier memorandum. The second part of this RFC describes briefly the Dacom 500 data compression algorithm as used by the INTELPOST electronic-mail network under development by the US Postal Service and several foreign administrators. UNKNOWN UNKNOWN RFC0804 CCITT draft recommendation T.4 International Telegraph and Telephone Consultative Committee of the International Telecommunication Union January 01 1981 ASCII 17025 12 This is the CCITT standard for group 3 facsimile encoding. This is useful for data compression of bit map data. Standardization of Group 3 facsimile apparatus for document transmission. UNKNOWN UNKNOWN RFC0805 Computer mail meeting notes J. Postel February 08 1982 ASCII 12522 6 This RFC consists of notes from a meeting that was held at USC Information Sciences Institute on 11 January 1982, to discuss addressing issues in computer mail. The major conclusion reached at the meeting is to extend the "username@hostname" mailbox format to "username@host.domain", where the domain itself can be further strutured. UNKNOWN UNKNOWN RFC0806 Proposed Federal Information Processing Standard: Specification for message format for computer based message systems National Bureau of Standards September 01 1981 ASCII 216377 107 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. RFC0841 UNKNOWN UNKNOWN RFC0807 Multimedia mail meeting notes J. Postel February 09 1982 ASCII 11633 6 This RFC consists of notes from a meeting held at USC Information Sciences Institute on the 12th of January to discuss common interests in multimedia computer mail issues and to agree on some specific initial experiments. UNKNOWN UNKNOWN RFC0808 Summary of computer mail services meeting held at BBN on 10 January 1979 J. Postel March 01 1982 ASCII 15930 8 This RFC is a very belated attempt to document a meeting that was held three years earlier to discuss the state of computer mail in the ARPA community and to reach some conclusions to guide the further development of computer mail systems such that a coherent total mail service would continue to be provided. UNKNOWN UNKNOWN RFC0809 UCL facsimile system T. Chang February 01 1982 ASCII 171153 99 This RFC describes the features of the computerised facsimile system developed in the Department of Computer Science at UCL. First its functions are considered and the related experimental work are reported. Then the disciplines for system design are discussed. Finally, the implementation of the system are described, while detailed description are given as appendices. UNKNOWN UNKNOWN RFC0810 DoD Internet host table specification E.J. Feinler K. Harrenstien Z. Su V. White March 01 1982 ASCII 14196 8 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. RFC0608 RFC0952 UNKNOWN UNKNOWN RFC0811 Hostnames Server K. Harrenstien V. White E.J. Feinler March 01 1982 ASCII 7771 4 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. RFC0953 UNKNOWN UNKNOWN RFC0812 NICNAME/WHOIS K. Harrenstien V. White March 01 1982 ASCII 5389 2 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. RFC0954 RFC3912 UNKNOWN UNKNOWN RFC0813 Window and Acknowledgement Strategy in TCP D.D. Clark July 01 1982 ASCII 38110 21 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. UNKNOWN UNKNOWN RFC0814 Name, addresses, ports, and routes D.D. Clark July 01 1982 ASCII 24663 13 This RFC gives suggestions and guidance for the design of the tables and algorithms necessary to keep track of these various sorts of identifiers inside a host implementation of TCP/IP. UNKNOWN UNKNOWN RFC0815 IP datagram reassembly algorithms D.D. Clark July 01 1982 ASCII 14575 8 This RFC describes an alternate approach of dealing with reassembly which reduces the bookkeeping problem to a minimum, and requires only one buffer for storage equal in size to the final datagram being reassembled, which can reassemble a datagram from any number of fragments arriving in any order with any possible pattern of overlap and duplication, and which is appropriate for almost any sort of operating system. UNKNOWN UNKNOWN RFC0816 Fault isolation and recovery D.D. Clark July 01 1982 ASCII 20106 11 This RFC describes the portion of fault isolation and recovery which is the responsibility of the host. UNKNOWN UNKNOWN RFC0817 Modularity and efficiency in protocol implementation D.D. Clark July 01 1982 ASCII 45931 25 This RFC will discuss some of the commonly encountered reasons why protocol implementations seem to run slowly. UNKNOWN UNKNOWN RFC0818 Remote User Telnet service J. Postel November 01 1982 ASCII 3693 2 RTELNET This RFC is the specification of an application protocol. Any host that implements this application level service must follow this protocol. HISTORIC HISTORIC RFC0819 Domain naming convention for Internet user applications Z. Su J. Postel August 01 1982 ASCII 35314 18 This RFC is an attempt to clarify the generalization of the Domain Naming Convention, the Internet Naming Convention, and to explore the implications of its adoption for Internet name service and user applications. UNKNOWN UNKNOWN RFC0820 Assigned numbers J. Postel August 14 1982 ASCII 54213 22 This RFC is an old version, see RFC 870. RFC0790 RFC0870 HISTORIC UNKNOWN RFC0821 Simple Mail Transfer Protocol J. Postel August 01 1982 ASCII 124482 72 SMTP 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. RFC0788 RFC2821 STD0010 STANDARD STANDARD RFC0822 Standard for the format of ARPA Internet text messages D. Crocker August 13 1982 ASCII 109200 49 MAIL 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. RFC0733 RFC2822 RFC1123 RFC1138 RFC1148 RFC1327 RFC2156 STD0011 STANDARD STANDARD RFC0823 DARPA Internet gateway R.M. Hinden A. Sheltzer September 01 1982 ASCII 62620 45 GGP This RFC is a status report on the Internet Gateway developed by BBN. It describes the Internet Gateway as of September 1982. This memo presents detailed descriptions of message formats and gateway procedures, however, this is not an implementation specification, and such details are subject to change. IEN109 IEN30 HISTORIC HISTORIC RFC0824 CRONUS Virtual Local Network W.I. MacGregor D.C. Tappan August 25 1982 ASCII 58732 41 The purpose of this note is to describe the CRONUS Virtual Local Network, especially the addressing related features. These features include a method for mapping between Internet Addresses and Local Network addresses. This is a topic of current concern in the ARPA Internet community. This note is intended to stimulate discussion. This is not a specification of an Internet Standard. UNKNOWN UNKNOWN RFC0825 Request for comments on Requests For Comments J. Postel November 01 1982 ASCII 4255 2 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. RFC1111 RFC1543 RFC2223 UNKNOWN UNKNOWN RFC0826 Ethernet Address Resolution Protocol: Or converting network protocol addresses to 48.bit Ethernet address for transmission on Ethernet hardware D.C. Plummer November 01 1982 ASCII 22026 10 ARP The purpose of this RFC is to present a method of Converting Protocol Addresses (e.g., IP addresses) to Local Network Addresses (e.g., Ethernet addresses). This is an issue of general concern in the ARPA Internet Community at this time. The method proposed here is presented for your consideration and comment. This is not the specification of an Internet Standard. STD0037 STANDARD STANDARD RFC0827 Exterior Gateway Protocol (EGP) E.C. Rosen October 01 1982 ASCII 68436 46 This RFC is proposed to establish a standard for Gateway to Gateway procedures that allow the Gateways to be mutually suspicious. This document is a DRAFT for that standard. Your comments are strongly encouraged. RFC0904 UNKNOWN UNKNOWN RFC0828 Data communications: IFIP's international "network" of experts K. Owen August 01 1982 ASCII 29922 11 This RFC is distributed to inform the ARPA Internet community of the activities of the IFIP technical committee on Data Communications, and to encourage participation in those activities. UNKNOWN UNKNOWN RFC0829 Packet satellite technology reference sources V.G. Cerf November 01 1982 ASCII 10919 5 This RFC describes briefly the packet satellite technology developed by the Defense Advanced Research Projects Agency and several other participating organizations in the U.K. and Norway and provides a bibliography of relevant papers for researchers interested in experimental and operational experience with this dynamic satellite-sharing technique. UNKNOWN UNKNOWN RFC0830 Distributed system for Internet name service Z. Su October 01 1982 ASCII 31597 18 This RFC proposes a distributed name service for DARPA Internet. Its purpose is to focus discussion on the subject. It is hoped that a general consensus will emerge leading eventually to the adoption of standards. UNKNOWN UNKNOWN RFC0831 Backup access to the European side of SATNET R.T. Braden December 01 1982 ASCII 11735 6 The purpose of this RFC is to focus discussion on a particular Internet problem: a backup path for software maintenance of the European sector of the Internet, for use when SATNET is partitioned. We propose a mechanism, based upon the Source Routing option of IP, to reach European Internet sites via the VAN Gateway and UCL. This proposal is not intended as a standard at this time. UNKNOWN UNKNOWN RFC0832 Who talks TCP? D. Smallberg December 07 1982 ASCII 42751 13 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. RFC0833 UNKNOWN UNKNOWN RFC0833 Who talks TCP? D. Smallberg December 14 1982 ASCII 42973 13 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. RFC0832 RFC0834 UNKNOWN UNKNOWN RFC0834 Who talks TCP? D. Smallberg December 22 1982 ASCII 42764 13 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. RFC0833 RFC0835 UNKNOWN UNKNOWN RFC0835 Who talks TCP? D. Smallberg December 29 1982 ASCII 42959 13 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. RFC0834 RFC0836 UNKNOWN UNKNOWN RFC0836 Who talks TCP? D. Smallberg January 05 1983 ASCII 43643 13 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. RFC0835 RFC0837 UNKNOWN UNKNOWN RFC0837 Who talks TCP? D. Smallberg January 12 1983 ASCII 44864 13 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. RFC0836 RFC0838 UNKNOWN UNKNOWN RFC0838 Who talks TCP? D. Smallberg January 20 1983 ASCII 45033 13 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. RFC0837 RFC0839 UNKNOWN UNKNOWN RFC0839 Who talks TCP? D. Smallberg January 26 1983 ASCII 45175 14 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. RFC0838 RFC0842 UNKNOWN UNKNOWN RFC0840 Official protocols J. Postel April 13 1983 ASCII 33534 23 This RFC has been revised, see RFC 880. RFC0880 HISTORIC UNKNOWN RFC0841 Specification for message format for Computer Based Message Systems National Bureau of Standards January 27 1983 ASCII 231871 117 This RFC is FIPS 98. The purpose of distributing this document as an RFC is to make it easily accessible to the ARPA research community. This RFC does not specify a standard for the ARPA Internet. Obsoletes RFC 806. RFC0806 UNKNOWN UNKNOWN RFC0842 Who talks TCP? - survey of 1 February 83 D. Smallberg February 03 1983 ASCII 45962 12 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. RFC0839 RFC0843 UNKNOWN UNKNOWN RFC0843 Who talks TCP? - survey of 8 February 83 D. Smallberg February 09 1983 ASCII 46193 13 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. RFC0842 RFC0845 RFC0844 UNKNOWN UNKNOWN RFC0844 Who talks ICMP, too? - Survey of 18 February 1983 R. Clements February 18 1983 ASCII 9078 5 This survey determines how many hosts are able to respond to TELENET connections from a user at a class C site. This requires, in addition to IP and TCP, participation in gateway routing via ICMP and handling of Class C addresses. The list of hosts was taken from RFC 843, extracting only those hosts which are listed there as accepting TELNET connection. The tests were run on 18-Feb-83. RFC0843 UNKNOWN UNKNOWN RFC0845 Who talks TCP? - survey of 15 February 1983 D. Smallberg February 17 1983 ASCII 45983 14 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. RFC0843 RFC0846 UNKNOWN UNKNOWN RFC0846 Who talks TCP? - survey of 22 February 1983 D. Smallberg February 23 1983 ASCII 45597 14 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. RFC0845 RFC0847 UNKNOWN UNKNOWN RFC0847 Summary of Smallberg surveys A. Westine D. Smallberg J. Postel February 01 1983 ASCII 3789 2 This is a summary of the surveys of Telnet, FTP and Mail (SMTP) servers conducted by David Smallberg in December 1982, January and February 1983 as reported in RFC 832-843, 845-846. This memo extracts the number of hosts that accepted the connection to their server for each of Telnet, FTP, and SMTP, and compares it to the total host in the Internet (not counting TACs or ECHOS). RFC0846 UNKNOWN UNKNOWN RFC0848 Who provides the "little" TCP services? D. Smallberg March 14 1983 ASCII 10985 5 This RFC lists those hosts which provide any of these "little" TCP services: The list of hosts were taken from the NIC hostname table of 24-Feb-83. The tests were run on February 23 and 24, and March 3 and 5 from ISI-VAXA.ARPA. UNKNOWN UNKNOWN RFC0849 Suggestions for improved host table distribution M.R. Crispin May 01 1983 ASCII 5178 2 This RFC actually is a request for comments. The issue dealt with is that of a naming registry update procedure, both as exists currently and what could exist in the future. None of the proposed solutions are intended as standards at this time; rather it is hoped that a general consensus will emerge as the appropriate solution, leaving eventually to the adoption of standards. UNKNOWN UNKNOWN RFC0850 Standard for interchange of USENET messages M.R. Horton June 01 1983 ASCII 43871 17 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. RFC1036 UNKNOWN UNKNOWN RFC0851 ARPANET 1822L Host Access Protocol A.G. Malis April 18 1983 ASCII 72042 47 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. RFC0802 RFC0878 UNKNOWN UNKNOWN RFC0852 ARPANET short blocking feature A.G. Malis April 01 1983 ASCII 17151 13 This RFC specifies the ARPANET Short Blocking Feature, which will allow ARPANET hosts to optionally shorten the IMP's host blocking timer. This Feature is a replacement of the ARPANET non-blocking host interface, which was never implemented, and will be available to hosts using either the 1822 or 1822L Host Access Protocol. This RFC is also being presented as a solicitation of comments on the Short Blocking Feature, especially from host network software implementers and maintainers. UNKNOWN UNKNOWN RFC0853 RFC0854 Telnet Protocol Specification J. Postel J.K. Reynolds May 01 1983 ASCII 39371 15 TELNET This is the specification of the Telnet protocol used for remote terminal access in the ARPA Internet. The purpose of the TELNET Protocol is to provide a fairly general, bi-directional, eight-bit byte oriented communications facility. Its primary goal is to allow a standard method of interfacing terminal devices and terminal-oriented processes to each other. It is envisioned that the protocol may also be used for terminal-terminal communication ("linking") and process-process communication (distributed computation). This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 18639. RFC0764 STD0008 STANDARD STANDARD RFC0855 Telnet Option Specifications J. Postel J.K. Reynolds May 01 1983 ASCII 6218 3 TELNET This memo specifies the general form for Telnet options and the directions for their specification. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes RFC 651, NIC 18640. NIC18640 STD0008 STANDARD STANDARD RFC0856 Telnet Binary Transmission J. Postel J.K. Reynolds May 01 1983 ASCII 9192 4 TOPT-BIN This Telnet Option enables a binary data mode between the Telnet modules. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 15389. NIC15389 STD0027 STANDARD STANDARD RFC0857 Telnet Echo Option J. Postel J.K. Reynolds May 01 1983 ASCII 11143 5 TOPT-ECHO This Telnet Option enables remote echoing by the other Telnet module. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 15390. NIC15390 STD0028 STANDARD STANDARD RFC0858 Telnet Suppress Go Ahead Option J. Postel J.K. Reynolds May 01 1983 ASCII 3825 2 TOPT-SUPP This Telnet Option disables the exchange of go-ahead signals between the Telnet modules. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 15392. NIC15392 STD0029 STANDARD STANDARD RFC0859 Telnet Status Option J. Postel J.K. Reynolds May 01 1983 ASCII 4443 3 TOPT-STAT This Telnet Option provides a way to determine the other Telnet module's view of the status of options. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes RFC 651 (NIC 31154). RFC0651 STD0030 STANDARD STANDARD RFC0860 Telnet Timing Mark Option J. Postel J.K. Reynolds May 01 1983 ASCII 8108 4 TOPT-TIM This Telnet Option provides a way to check the roundtrip path between two Telnet modules. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 16238. NIC16238 STD0031 STANDARD STANDARD RFC0861 Telnet Extended Options: List Option J. Postel J.K. Reynolds May 01 1983 ASCII 3181 2 TOPT-EXTOP This Telnet Option provides a mechanism for extending the set of possible options. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 16239. NIC16239 STD0032 STANDARD STANDARD RFC0862 Echo Protocol J. Postel May 01 1983 ASCII 1294 1 ECHO This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Echo Protocol are expected to adopt and implement this standard. The Echo service simply sends back to the originating source any data it receives. STD0020 STANDARD STANDARD RFC0863 Discard Protocol J. Postel May 01 1983 ASCII 1297 1 DISCARD This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Discard Protocol are expected to adopt and implement this standard. The Discard service simply throws away any data it receives. STD0021 STANDARD STANDARD RFC0864 Character Generator Protocol J. Postel May 01 1983 ASCII 7016 3 CHARGEN This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Character Generator Protocol are expected to adopt and implement this standard. The Character Generator service simply sends data without regard to the input. STD0022 STANDARD STANDARD RFC0865 Quote of the Day Protocol J. Postel May 01 1983 ASCII 1734 1 QUOTE This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Quote of the Day Protocol are expected to adopt and implement this standard. The Quote of the Day service simply sends a short message without regard to the input. STD0023 STANDARD STANDARD RFC0866 Active users J. Postel May 01 1983 ASCII 2087 1 USERS This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement an Active Users Protocol are expected to adopt and implement this standard. The Active Users service simply sends a list of the currently active users on the host without regard to the input. STD0024 STANDARD STANDARD RFC0867 Daytime Protocol J. Postel May 01 1983 ASCII 2405 2 DAYTIME This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Daytime Protocol are expected to adopt and implement this standard. The Daytime service simply sends the current date and time as a character string without regard to the input. STD0025 STANDARD STANDARD RFC0868 Time Protocol J. Postel K. Harrenstien May 01 1983 ASCII 3140 2 TIME This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Time Protocol are expected to adopt and implement this standard. This protocol provides a site-independent, machine readable date and time. The Time service sends back to the originating source the time in seconds since midnight on January first 1900. STD0026 STANDARD STANDARD RFC0869 Host Monitoring Protocol R. Hinden December 01 1983 ASCII 94550 72 HMP HMP This RFC specifies the Host Monitoring Protocol used to collect information from various types of hosts in the Internet. Designers of Internet communications software are encouraged to consider this protocol as a means of monitoring the behavior of their creations. HISTORIC HISTORIC RFC0870 Assigned numbers J.K. Reynolds J. Postel October 01 1983 ASCII 56055 26 This RFC documents the list of numbers assigned for networks, protocols, etc. Obsoletes RFCs 820, 790, 776, 770, 762, 758, 755, 750, 739, 604. RFC0820 RFC0900 HISTORIC UNKNOWN RFC0871 Perspective on the ARPANET reference model M.A. Padlipsky September 01 1982 ASCII 74455 29 This RFC is primarily intended as a perspective on the ARM and points out some of the differences between the ARM and the ISORM which were expressed by members in NWG general meetings, NWG protocol design committee meetings, the ARPA Internet Working Group, and private conversations over the intervening years. Originally published as M82-47 by the MITRE Corporation, Bedford, Massachusetts. UNKNOWN UNKNOWN RFC0872 TCP-on-a-LAN M.A. Padlipsky September 01 1982 ASCII 22446 10 TCP LAN This memo attacks the notion that TCP cannot be appropriate for use on a Local Area Network. Originally published as M82-48 by the MITRE Corporation, Bedford Massachusetts. UNKNOWN UNKNOWN RFC0873 Illusion of vendor support M.A. Padlipsky September 01 1982 ASCII 23095 12 This memo takes issue with the claim that international standards in computer protocols presently provide a basis for low cost vendor supported protocol implementations. Originally published as M82-49 by the MITRE Corporation, Bedford, Massachusetts. UNKNOWN UNKNOWN RFC0874 Critique of X.25 M.A. Padlipsky September 01 1982 ASCII 36386 17 This RFC is an analysis of X.25 pointing out some problems in the conceptual model, particularly the conflict between the interface aspects and the end-to-end aspects. The memo also touches on security, and implementation issues. Originally published as M82-50 by the MITRE Corporation, Bedford, Massachusetts. UNKNOWN UNKNOWN RFC0875 Gateways, architectures, and heffalumps M.A. Padlipsky September 01 1982 ASCII 22816 10 This RFC is a discussion about the role of gateways in an internetwork, especially the problems of translating or mapping protocols between different protocol suites. The discussion notes possible functionality mis-matches, undesirable routing "singularity points", flow control issues, and high cost of translating gateways. Originally published as M82-51 by the MITRE Corporation, Bedford, Massachusetts. UNKNOWN UNKNOWN RFC0876 Survey of SMTP implementations D. Smallberg September 01 1983 ASCII 37775 13 This RFC is a survey of implementation status. It does not specify an official protocol, but rather notes the status of implementation of aspects of a protocol. It is expected that the status of the hosts reported on will change. This information must be treated as a snapshot of the state of these implemetations. UNKNOWN UNKNOWN RFC0877 Standard for the transmission of IP datagrams over public data networks J.T. Korb September 01 1983 ASCII 3272 2 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. RFC1356 UNKNOWN UNKNOWN RFC0878 ARPANET 1822L Host Access Protocol A.G. Malis December 01 1983 ASCII 74774 51 This RFC specifies the ARPANET 1822L Host Access Protocol, which is a successor to the existing 1822 Host Access Protocol. The 1822L procedure allows ARPANET hosts to use logical identifiers as well as 1822 physical interface identifiers to address each other. RFC0851 UNKNOWN UNKNOWN RFC0879 TCP maximum segment size and related topics J. Postel November 01 1983 ASCII 22024 11 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". UNKNOWN UNKNOWN RFC0880 Official protocols J.K. Reynolds J. Postel October 01 1983 ASCII 37332 26 This RFC identifies the documents specifying the official protocols used in the ARPA Internet. Annotations identify any revisions or changes planned. Obsoletes RFC 840. RFC0840 RFC0901 HISTORIC UNKNOWN RFC0881 Domain names plan and schedule J. Postel November 01 1983 ASCII 23490 10 This RFC outlines a plan and schedule for the implementation of domain style names throughout the DDN/ARPA Internet community. The introduction of domain style names will impact all hosts on the DDN/ARPA Internet. RFC0897 UNKNOWN UNKNOWN RFC0882 Domain names: Concepts and facilities P.V. Mockapetris November 01 1983 ASCII 79776 31 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. RFC1034 RFC1035 RFC0973 UNKNOWN UNKNOWN RFC0883 Domain names: Implementation specification P.V. Mockapetris November 01 1983 ASCII 175067 74 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. RFC1034 RFC1035 RFC0973 UNKNOWN UNKNOWN RFC0884 Telnet terminal type option M. Solomon E. Wimmers December 01 1983 ASCII 7881 5 This RFC specifies a standard for the ARPA Internet community. It specifies a method for exchanging terminal type information in the Telnet protocol. RFC0930 UNKNOWN UNKNOWN RFC0885 Telnet end of record option J. Postel December 01 1983 ASCII 3232 2 TOPT-EOR This RFC specifies a standard for the ARPA Internet community. It specifies a method for marking the end of records in data transmitted on Telnet connections. PROPOSED STANDARD PROPOSED STANDARD RFC0886 Proposed standard for message header munging M.T. Rose December 15 1983 ASCII 30566 16 This RFC specifies a draft standard for the ARPA Internet community. It describes the rules to be used when transforming mail from the conventions of one message system to those of another message system. In particular, the treatment of header fields, and recipient addresses is specified. UNKNOWN UNKNOWN RFC0887 Resource Location Protocol M. Accetta December 01 1983 ASCII 36770 16 RLP This RFC specifies a draft standard for the ARPA Internet community. It describes a resource location protocol for use in the ARPA Internet. It is most useful on networks employing technologies which support some method of broadcast addressing, however it may also be used on other types of networks. For maximum benefit, all hosts which provide significant resources or services to other hosts on the Internet should implement this protocol. Hosts failing to implement the Resource Location Protocol risk being ignored by other hosts which are attempting to locate resources on the Internet. EXPERIMENTAL EXPERIMENTAL RFC0888 "STUB" Exterior Gateway Protocol L. Seamonson E.C. Rosen January 01 1984 ASCII 53227 39 This RFC describes the Exterior Gateway Protocol used to connect Stub Gateways to an Autonomous System of core Gateways. This document specifies the working protocol, and defines an ARPA official protocol. All implementers of Gateways should carefully review this document. RFC0904 UNKNOWN UNKNOWN RFC0889 Internet delay experiments D.L. Mills December 01 1983 ASCII 27128 12 This memo reports on some measurements of round-trip times in the Internet and suggests some possible improvements to the TCP retransmission timeout calculation. This memo is both a status report on the Internet and advice to TCP implementers. UNKNOWN UNKNOWN RFC0890 Exterior Gateway Protocol implementation schedule J. Postel February 01 1984 ASCII 5899 3 EGP This memo is a policy statement on the implementation of the Exterior Gateway Protocol in the Internet. This is an official policy statement of ICCB and DARPA. After 1-Aug-84 there shall be no dumb gateways in the Internet. Every gateway must be a member of some autonomous system. Some gateway of each autonomous system must exchange routing information with some gateway of the core autonomous system using the Exterior Gateway Protocol. UNKNOWN UNKNOWN RFC0891 DCN local-network protocols D.L. Mills December 01 1983 ASCII 66769 26 IP-DC This RFC provides a description of the DCN protocols for maintaining connectivity, routing, and clock information in a local network. These procedures may be of interest to the designers and implementers of other local networks. STD0044 STANDARD STANDARD RFC0892 ISO Transport Protocol specification International Organization for Standardization December 01 1983 ASCII 158151 82 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. Draft. RFC0905 UNKNOWN UNKNOWN RFC0893 Trailer encapsulations S. Leffler M.J. Karels April 01 1984 ASCII 13353 6 This RFC discusses the motivation for use of "trailer encapsulations" on local-area networks and describes the implementation of such an encapsulation on various media. This document is for information only. This is NOT an official protocol for the ARPA Internet community. UNKNOWN UNKNOWN RFC0894 Standard for the transmission of IP datagrams over Ethernet networks C. Hornig April 01 1984 ASCII 5697 3 IP-E This RFC specifies a standard method of encapsulating Internet Protocol (IP) datagrams on an Ethernet. This RFC specifies a standard protocol for the ARPA-Internet community. STD0041 STANDARD STANDARD RFC0895 Standard for the transmission of IP datagrams over experimental Ethernet networks J. Postel April 01 1984 ASCII 4985 3 IP-EE This RFC specifies a standard method of encapsulating Internet Protocol (IP) datagrams on an Experimental Ethernet. This RFC specifies a standard protocol for the ARPA Internet community. STD0042 STANDARD STANDARD RFC0896 Congestion control in IP/TCP internetworks J. Nagle January 06 1984 ASCII 26782 9 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. UNKNOWN UNKNOWN RFC0897 Domain name system implementation schedule J. Postel February 01 1984 ASCII 15683 8 This memo is a policy statement on the implementation of the Domain Style Naming System in the Internet. This memo is a partial update of RFC 881. The intent of this memo is to detail the schedule for the implementation for the Domain Style Naming System. The names of hosts will be changed to domain style names. Hosts will begin to use domain style names on 14-Mar-84, and the use of old style names will be completely phased out before 2-May-84. This applies to both the ARPA research hosts and the DDN operational hosts. This is an official policy statement of the ICCB and the DARPA. RFC0881 RFC0921 UNKNOWN UNKNOWN RFC0898 Gateway special interest group meeting notes R.M. Hinden J. Postel M. Muuss J.K. Reynolds April 01 1984 ASCII 42112 24 This memo is a report on the Gateway Special Interest Group Meeting that was held at ISI on 28 and 29 February 1984. Robert Hinden of BBNCC chaired, and Jon Postel of ISI hosted the meeting. Approximately 35 gateway designers and implementors attended. These notes are based on the recollections of Jon Postel and Mike Muuss. Under each topic area are Jon Postel's brief notes, and additional details from Mike Muuss. This memo is a report on a meeting. No conclusions, decisions, or policy statements are documented in this note. UNKNOWN UNKNOWN RFC0899 Request For Comments summary notes: 800-899 J. Postel A. Westine May 01 1984 ASCII 39996 18 INFORMATIONAL INFORMATIONAL RFC0900 Assigned Numbers J.K. Reynolds J. Postel June 01 1984 ASCII 82116 43 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. RFC0870 RFC0923 HISTORIC UNKNOWN RFC0901 Official ARPA-Internet protocols J.K. Reynolds J. Postel June 01 1984 ASCII 41058 28 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. RFC0880 RFC0924 UNKNOWN UNKNOWN RFC0902 ARPA Internet Protocol policy J.K. Reynolds J. Postel July 01 1984 ASCII 11027 5 The purpose of this memo is to explain how protocol standards are adopted for the ARPA-Internet and the DARPA research community. There are three important aspects to be discussed: the process, the authority, and the complex relationship between the DARPA community and the DDN community. This memo is a policy statement on how protocols become official standards for the ARPA-Internet and the DARPA research community. This is an official policy statement of the ICCB and the DARPA. UNKNOWN UNKNOWN RFC0903 Reverse Address Resolution Protocol R. Finlayson T. Mann J.C. Mogul M. Theimer June 01 1984 ASCII 9345 4 RARP This RFC suggests a method for workstations to dynamically find their protocol address (e.g., their Internet Address), when they know only their hardware address (e.g., their attached physical network address). This RFC specifies a proposed protocol for the ARPA Internet community, and requests discussion and suggestions for improvements. STD0038 STANDARD STANDARD RFC0904 Exterior Gateway Protocol formal specification D.L. Mills April 01 1984 ASCII 65226 30 EGP RFC-904 is the specification of the Exterior Gateway Protocol (EGP). This memo updates portions of RFC-888 and RFC-827. This RFC specifies an official protocol of the DARPA community for use between gateways of different autonomous systems in the ARPA-Internet. RFC0827 RFC0888 HISTORIC HISTORIC RFC0905 ISO Transport Protocol specification ISO DP 8073 ISO April 01 1984 ASCII 249214 164 This is the current specification of the ISO Transport Protocol. This document is the text of ISO/TC97/SC16/N1576 as corrected by ISO/TC97/SC16/N1695. This is the specification currently being voted on in ISO as a Draft International Standard (DIS). This document is distributed as an RFC for your information only, it does not specify a standard for the ARPA-Internet or DARPA research community. Our thanks to Alex McKenzie of BBN for making this online version available. Please note the size of this document, the file contains 258,729 characters. RFC0892 UNKNOWN UNKNOWN RFC0906 Bootstrap loading using TFTP R. Finlayson June 01 1984 ASCII 10102 4 It is often convenient to be able to bootstrap a computer system from a communications network. This RFC proposes the use of the IP TFTP protocol for bootstrap loading in this case. UNKNOWN UNKNOWN RFC0907 Host Access Protocol specification Bolt Beranek and Newman Inc. July 01 1984 ASCII 129985 78 IP-WB This document specifies the Host Access Protocol (HAP). Although HAP was originally designed as the network-access level protocol for the DARPA/DCA sponsored Wideband Packet Satellite Network, it is intended that it evolve into a standard interface SATNET and TACNET (aka MATNET) as well as the Wideband Network. HAP is an experimental protocol, and will undergo further revision as new capabilities are added and/or different satellite networks are suported. Implementations of HAP should be performed in coordination with satellite network development and operations personnel. RFC1221 STD0040 STANDARD STANDARD RFC0908 Reliable Data Protocol D. Velten R.M. Hinden J. Sax July 01 1984 ASCII 97646 62 RDP The Reliable Data Protocol (RDP) is designed to provide a reliable data transport service for packet-based applications. This RFC specifies a proposed protocol for the ARPA-Internet and DARPA research community, and requests discussion and suggestions for improvemts. RFC1151 EXPERIMENTAL EXPERIMENTAL RFC0909 Loader Debugger Protocol C. Welles W. Milliken July 01 1984 ASCII 209813 135 LDP The Loader Debugger Protocol (LDP) is an application layer protocol for loading, dumping, and debugging target machines from hosts in a network environment. This RFC specifies a proposed protocol for the ARPA-Internet and DARPA research community, and requests discussion and suggestions for improvemts. EXPERIMENTAL EXPERIMENTAL RFC0910 Multimedia mail meeting notes H.C. Forsdick August 01 1984 ASCII 24915 11 This memo is a report on a meeting about the experimental multimedia mail system (and in a sense a status report on that experiment). The meeting was held at Bolt Beranek and Newman on 23-24 July 1984 to discuss recent progress by groups who are building multimedia mail systems and to discuss a variety of issues related to the further development of multimedia systems. Representatives were present from BBN, ISI, SRI and Linkabit. UNKNOWN UNKNOWN RFC0911 EGP Gateway under Berkeley UNIX 4.2 P. Kirton August 22 1984 ASCII 55908 23 This memo describes an implementation of the Exterior Gateway Protocol (EGP) (in that sense it is a status report). The memo also discusses some possible extentions and some design issues (in that sense it is an invitation for further discussion). UNKNOWN UNKNOWN RFC0912 Authentication service M. St. Johns September 01 1984 ASCII 4544 3 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. RFC0931 UNKNOWN UNKNOWN RFC0913 Simple File Transfer Protocol M. Lottor September 01 1984 ASCII 20929 15 SFTP FTP This memo describes a proposed Simple File Transfer Protocol (SFTP). It fills the need of people wanting a protocol that is more useful than TFTP but easier to implement (and less powerful) than FTP. SFTP supports user access control, file transfers, directory listing, directory changing, file renaming and deleting. Discussion of this proposal is encouraged, and suggestions for improvements may be sent to the author. HISTORIC HISTORIC RFC0914 Thinwire protocol for connecting personal computers to the Internet D.J. Farber G. Delp T.M. Conte September 01 1984 ASCII 57288 22 THINWIRE This RFC focuses discussion on the particular problems in the ARPA-Internet of low speed network interconnection with personal computers, and possible methods of solution. None of the proposed solutions in this document are intended as standards for the ARPA-Internet. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to the problems, leading eventually to the adoption of standards. HISTORIC HISTORIC RFC0915 Network mail path service M.A. Elvy R. Nedved December 01 1984 ASCII 21635 11 This RFC proposed a new service for the ARPA-Internet community and requests discussion and suggestions for improvements. The network mail path service fills the current need of people to determine mailbox addresses for hosts that are not part of the ARPA-Internet but can be reached by one or more relay hosts that have Unix to Unix Copy (UUCP) mail, CSNET mail, MAILNET mail, BITNET mail, etc. Anyone can use the service if they have TCP/TELENET to one of the hosts with a mail path server. UNKNOWN UNKNOWN RFC0916 Reliable Asynchronous Transfer Protocol (RATP) G.G. Finn October 01 1984 ASCII 110737 54 RATP This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. This paper proposes and specifies a protocol which allows two programs to reliably communicate over a communication link. It ensures that the data entering one end of the link if received arrives at the other end intact and unaltered. The protocol, named RATP, is designed to operate over a full duplex point-to-point connection. It contains some features which tailor it to the RS-232 links now in common use. HISTORIC HISTORIC RFC0917 Internet subnets J.C. Mogul October 01 1984 ASCII 47072 22 This memo discusses subnets and proposes procedures for the use of subnets, including approaches to solving the problems that arise, particularly that of routing. A subnet of an Internet network is a logically visible sub-section of a single Internet network. For administrative or technical reasons, many organizations have chosen to divide one Internet network into several subnets, instead of acquiring a set of Internet network numbers. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. UNKNOWN UNKNOWN RFC0918 Post Office Protocol J.K. Reynolds October 01 1984 ASCII 9876 5 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. RFC0937 UNKNOWN UNKNOWN RFC0919 Broadcasting Internet Datagrams J.C. Mogul October 01 1984 ASCII 16382 8 This RFC proposes simple rules for broadcasting Internet datagrams on local networks that support broadcast, for addressing broadcasts, and for how gateways should handle them. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. STD0005 STANDARD STANDARD RFC0920 Domain requirements J. Postel J.K. Reynolds October 01 1984 ASCII 27823 14 This memo states the requirements on establishing a Domain, and introduces the limited set of top level domains. This memo is a policy statement on the requirements of establishing a new domain in the ARPA-Internet and the DARPA research community. This is an official policy statement of the IAB and the DARPA. UNKNOWN UNKNOWN RFC0921 Domain name system implementation schedule - revised J. Postel October 01 1984 ASCII 23318 13 This memo is a policy statement on the implementation of the Domain Style Naming System in the Internet. This memo is an update of RFC-881, and RFC-897. This is an official policy statement of the IAB and the DARPA. The intent of this memo is to detail the schedule for the implementation for the Domain Style Naming System. The explanation of how this system works is to be found in the references. RFC0897 UNKNOWN UNKNOWN RFC0922 Broadcasting Internet datagrams in the presence of subnets J.C. Mogul October 01 1984 ASCII 24147 12 We propose simple rules for broadcasting Internet datagrams on local networks that support broadcast, for addressing broadcasts, and for how gateways should handle them. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. STD0005 STANDARD STANDARD RFC0923 Assigned numbers J.K. Reynolds J. Postel October 01 1984 ASCII 96467 47 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. RFC0900 RFC0943 HISTORIC UNKNOWN RFC0924 Official ARPA-Internet protocols for connecting personal computers to the Internet J.K. Reynolds J. Postel October 01 1984 ASCII 48513 35 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. RFC0901 RFC0944 UNKNOWN UNKNOWN RFC0925 Multi-LAN address resolution J. Postel October 01 1984 ASCII 31137 15 The problem of treating a set of local area networks (LANs) as one Internet network has generated some interest and concern. It is inappropriate to give each LAN within an site a distinct Internet network number. It is desirable to hide the details of the interconnections between the LANs within an site from people, gateways, and hosts outside the site. The question arises on how to best do this, and even how to do it at all. In RFC-917 Jeffery Mogul makes a case for the use of "explicit subnets" in a multi-LAN environment. The explicit subnet scheme is a call to recursively apply the mechanisms the Internet uses to manage networks to the problem of managing LANs within one network. In this note I urge another approach: the use of "transparent subnets" supported by a multi-LAN extension of the Address Resolution Protocol. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. UNKNOWN UNKNOWN RFC0926 Protocol for providing the connectionless mode network services International Organization for Standardization December 01 1984 ASCII 165895 107 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. RFC0994 UNKNOWN UNKNOWN RFC0927 TACACS user identification Telnet option B.A. Anderson December 01 1984 ASCII 5474 4 TOPT-TACACS The following is the description of a TELNET option designed to facilitate double login avoidance. It is intended primarily for TAC connections to target hosts on behalf of TAC users, but it can be used between any two consenting hosts. For example, all hosts at one site (e.g., BBN) can use this option to avoid double login when TELNETing to one another. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. PROPOSED STANDARD PROPOSED STANDARD RFC0928 Introduction to proposed DoD standard H-FP M.A. Padlipsky December 01 1984 ASCII 60461 21 The broad outline of the Host-Front End Protocol introduced here and described in RFC-929 is the result of the deliberations of a number of experienced H-FP designers, who sat as a committee of the DoD Protocol Standards Technical Panel. It is the intent of the designers that the protocol be subjected to multiple test implementations and probable iteration before being agreed upon as any sort of "standard". Therefore, the first order of business is to declare that THIS IS A PROPOSAL, NOT A FINAL STANDARD, and the second order of business is to request that any readers of these documents who are able to do test implementations (a) do so and (b) coordinate their efforts with the author. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. UNKNOWN UNKNOWN RFC0929 Proposed Host-Front End Protocol J. Lilienkamp R. Mandell M.A. Padlipsky December 01 1984 ASCII 135042 56 HFEP The Host-Front End Protocol introduced in RFC-928 is described in detail in this memo. The first order of business is to declare that THIS IS A PROPOSAL, NOT A FINAL STANDARD, and the second order of business is to request that any readers of these documents who are able to do test implementations (a) do so and (b) coordinate their efforts with the author. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. HISTORIC HISTORIC RFC0930 Telnet terminal type option M. Solomon E. Wimmers January 01 1985 ASCII 6583 4 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. RFC0884 RFC1091 UNKNOWN UNKNOWN RFC0931 Authentication server M. St. Johns January 01 1985 ASCII 8982 5 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. RFC0912 RFC1413 UNKNOWN UNKNOWN RFC0932 Subnetwork addressing scheme D.D. Clark January 01 1985 ASCII 9283 4 This RFC proposes an alternative addressing scheme for subnets which, in most cases, requires no modification to host software whatsoever. The drawbacks of this scheme are that the total number of subnets in any one network are limited, and that modification is required to all gateways. UNKNOWN UNKNOWN RFC0933 Output marking Telnet option S. Silverman January 01 1985 ASCII 6715 4 TOPT-OM This proposed option would allow a Server-Telnet to send a banner to a User-Telnet so that this banner would be displayed on the workstation screen independently of the application software running in the Server-Telnet. PROPOSED STANDARD PROPOSED STANDARD RFC0934 Proposed standard for message encapsulation M.T. Rose E.A. Stefferud January 01 1985 ASCII 21770 10 This memo concerns itself with message forwarding. Forwarding can be thought of as encapsulating one or more messages inside another. Although this is useful for transfer of past correspondence to new recipients, without a decapsulation process (which this memo terms "bursting"), the forwarded messages are of little use to the recipients because they can not be distributed, forwarded, replied-to, or otherwise processed as separate individual messages. In order to burst a message it is necessary to know how the component messages were encapsulated in the draft. At present there is no unambiguous standard for interest group digests. This RFC proposes a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. UNKNOWN UNKNOWN RFC0935 Reliable link layer protocols J.G. Robinson January 01 1985 ASCII 31625 12 This RFC discusses protocols proposed recently in RFCs 914 and 916, and suggests a proposed protocol that could meet the same needs addressed in those memos. The stated need is reliable communication between two programs over a full-duplex, point-to-point communication link, and in particular the RFCs address the need for such communication over an asynchronous link at relatively low speeds. The suggested protocol uses the methods of existing national and international data link layer standards. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. UNKNOWN UNKNOWN RFC0936 Another Internet subnet addressing scheme M.J. Karels February 01 1985 ASCII 10179 4 There have been several proposals for schemes to allow the use of a single Internet network number to refer to a collection of physical networks under common administration which are reachable from the rest of the Internet by a common route. Such schemes allow a simplified view of an otherwise complicated topology from hosts and gateways outside of this collection. They allow the complexity of the number and type of these networks, and routing to them, to be localized. Additions and changes in configuration thus cause no detectable change, and no interruption of service, due to slow propagation of routing and other information outside of the local environment. These schemes also simplify the administration of the network, as changes do not require allocation of new network numbers for each new cable installed. This proposal discusses an alternative scheme, one that has been in use at the University of California, Berkeley since April 1984. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. UNKNOWN UNKNOWN RFC0937 Post Office Protocol: Version 2 M. Butler J. Postel D. Chase J. Goldberger J.K. Reynolds February 01 1985 ASCII 42370 24 POP2 Post Office Protocol Version 2 This RFC suggests a simple method for workstations to dynamically access mail from a mailbox server. This RFC specifies a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvement. This memo is a revision of RFC-918. RFC0918 HISTORIC HISTORIC RFC0938 Internet Reliable Transaction Protocol functional and interface specification T. Miller February 01 1985 ASCII 39478 19 IRTP This RFC is being distributed to members of the DARPA research community in order to solicit their reactions to the proposals contained in it. While the issues discussed may not be directly relevant to the research problems of the DARPA community, they may be interesting to a number of researchers and implementors. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. EXPERIMENTAL EXPERIMENTAL RFC0939 Executive summary of the NRC report on transport protocols for Department of Defense data networks National Research Council February 01 1985 ASCII 42345 20 This RFC reproduces the material from the "front pages" of the National Research Council report resulting from a study of the DOD Internet Protocol (IP) and Transmission Control Protocol (TCP) in comparison with the ISO Internet Protocol (ISO-IP) and Transport Protocol level 4 (TP-4). The point of this RFC is to make the text of the Executive Summary widely available in a timely way. The order of presentation has been altered, and the pagination changed. This RFC is distributed for information only. This RFC does not establish any policy for the DARPA research community or the DDN operational community. UNKNOWN UNKNOWN RFC0940 Toward an Internet standard scheme for subnetting Gateway Algorithms and Data Structures Task Force April 01 1985 ASCII 6881 3 Several sites now contain a complex of local links connected to the Internet via a gateway. The details of the internal connectivity are of little interest to the rest of the Internet. One way of organizing these local complexes of links is to use the same strategy as the Internet uses to organize networks, that is, to declare each link to be an entity (like a network) and to interconnect the links with devices that perform routing functions (like gateways). This general scheme is called subnetting, the individual links are called subnets, and the connecting devices are called subgateways (or bridges, or gateways). This RFC discusses standardizing the protocol used in subnetted environments in the ARPA-Internet. UNKNOWN UNKNOWN RFC0941 Addendum to the network service definition covering network layer addressing International Organization for Standardization April 01 1985 ASCII 68733 34 This Addendum to the Network Service Definition Standard, ISO 8348, defines the abstract syntax and semantics of the Network Address (Network Service Access Point Address). The Network Address defined in this Addendum is the address that appears in the primitives of the connection-mode Network Service as the calling address, called address, and responding address parameters, and in the primitives of the connectionless-mode Network Service as the source address and destination address parameters. This document is distributed as an RFC for information only. It does not specify a standard for the ARPA-Internet. UNKNOWN UNKNOWN RFC0942 Transport protocols for Department of Defense data networks National Research Council February 01 1985 ASCII 217284 88 This RFC reproduces the National Research Council report resulting from a study of the DoD Internet Protocol (IP) and Transmission Control Protocol (TCP) in comparison with the ISO Internet Protocol (ISO-IP) and Transport Protocol level 4 (TP-4). UNKNOWN UNKNOWN RFC0943 Assigned numbers J.K. Reynolds J. Postel April 01 1985 ASCII 105234 50 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. RFC0923 RFC0960 HISTORIC UNKNOWN RFC0944 Official ARPA-Internet protocols J.K. Reynolds J. Postel April 01 1985 ASCII 61373 40 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. RFC0924 RFC0961 UNKNOWN UNKNOWN RFC0945 DoD statement on the NRC report J. Postel May 01 1985 ASCII 5017 2 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. RFC1039 UNKNOWN UNKNOWN RFC0946 Telnet terminal location number option R. Nedved May 01 1985 ASCII 6285 4 TOPT-TLN Many systems provide a mechanism for finding out where a user is logged in from usually including information about telephone extension and office occupants names. The information is useful for physically locating people and/or calling them on the phone. In 1982 CMU designed and implemented a terminal location database and modified existing network software to handle a 64-bit number called the Terminal Location Number (or TTYLOC). It now seems appropriate to incorporate this mechanism into the TCP-based network protocol family. The mechanism is not viewed as a replacement for the Terminal Location Telnet Option (SEND-LOCATION) but as a shorthand mechansim for communicating terminal location information between hosts in a localized community. This RFC proposes a new option for Telnet for the ARPA-Internet community, and requests discussion and suggestions for improvements. PROPOSED STANDARD PROPOSED STANDARD RFC0947 Multi-network broadcasting within the Internet K. Lebowitz D. Mankins June 01 1985 ASCII 12569 5 This RFC describes the extension of a network's broadcast domain to include more than one physical network through the use of a broadcast packet repeater. UNKNOWN UNKNOWN RFC0948 Two methods for the transmission of IP datagrams over IEEE 802.3 networks I. Winston June 01 1985 ASCII 11495 7 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. RFC1042 UNKNOWN UNKNOWN RFC0949 FTP unique-named store command M.A. Padlipsky July 01 1985 ASCII 4017 2 There are various contexts in which it would be desirable to have an FTP command that had the effect of the present STOR but rather than requiring the sender to specify a file name istead caused the resultant file to have a unique name relative to the current directory. This RFC proposes an extension to the File Transfer Protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. See RFC-959. UNKNOWN UNKNOWN RFC0950 Internet Standard Subnetting Procedure J.C. Mogul J. Postel August 01 1985 ASCII 37985 18 Address This memo discusses the utility of "subnets" of Internet networks, which are logically visible sub-sections of a single Internet network. For administrative or technical reasons, many organizations have chosen to divide one Internet network into several subnets, instead of acquiring a set of Internet network numbers. This memo specifies procedures for the use of subnets. These procedures are for hosts (e.g., workstations). The procedures used in and between subnet gateways are not fully described. Important motivation and background information for a subnetting standard is provided in RFC-940. This RFC specifies a protocol for the ARPA-Internet community. If subnetting is implemented it is strongly recommended that these procedures be followed. RFC0792 STD0005 STANDARD STANDARD RFC0951 Bootstrap Protocol W.J. Croft J. Gilmore September 01 1985 ASCII 28354 12 BOOTP This RFC describes an IP/UDP bootstrap protocol (BOOTP) which allows a diskless client machine to discover its own IP address, the address of a server host, and the name of a file to be loaded into memory and executed. The bootstrap operation can be thought of as consisting of TWO PHASES. This RFC describes the first phase, which could be labeled `address determination and bootfile selection'. After this address and filename information is obtained, control passes to the second phase of the bootstrap where a file transfer occurs. The file transfer will typically use the TFTP protocol, since it is intended that both phases reside in PROM on the client. However BOOTP could also work with other protocols such as SFTP or FTP. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. RFC1395 RFC1497 RFC1532 RFC1542 DRAFT STANDARD DRAFT STANDARD RFC0952 DoD Internet host table specification K. Harrenstien M.K. Stahl E.J. Feinler October 01 1985 ASCII 12388 6 This RFC is the official specification of the format of the Internet Host Table. This edition of the specification includes minor revisions to RFC-810 which brings it up to date. RFC0810 UNKNOWN UNKNOWN RFC0953 Hostname Server K. Harrenstien M.K. Stahl E.J. Feinler October 01 1985 ASCII 8305 5 HOSTNAME This RFC is the official specification of the Hostname Server Protocol. This edition of the specification includes minor revisions to RFC-811 which brings it up to date. RFC0811 HISTORIC HISTORIC RFC0954 NICNAME/WHOIS K. Harrenstien M.K. Stahl E.J. Feinler October 01 1985 ASCII 7397 4 NICNAME 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. RFC0812 RFC3912 DRAFT STANDARD DRAFT STANDARD RFC0955 Towards a transport service for transaction processing applications R.T. Braden September 01 1985 ASCII 22497 10 The DoD Internet protocol suite includes two alternative transport service protocols, TCP and UDP, which provide virtual circuit and datagram service, respectively. These two protocols represent points in the space of possible transport service attributes which are quite "far apart". We want to examine an important class of applications, those which perform what is often called "transaction processing". We will see that the communication needs for these applications fall into the gap "between" TCP and UDP -- neither protocol is very appropriate. This RFC is concerned with the possible design of one or more new protocols for the ARPA-Internet, to support kinds of applications which are not well supported at present. The RFC is intended to spur discussion in the Internet research community towards the development of new protocols and/or concepts, in order to meet these unmet application requirements. It does not represent a standard, nor even a concrete protocol proposal. UNKNOWN UNKNOWN RFC0956 Algorithms for synchronizing network clocks D.L. Mills September 01 1985 ASCII 67387 26 This RFC discussed clock synchronization algorithms for the ARPA-Internet community, and requests discussion and suggestions for improvements. The recent interest within the Internet community in determining accurate time from a set of mutually suspicious network clocks has been prompted by several occasions in which errors were found in usually reliable, accurate clock servers after thunderstorms which disrupted their power supply. To these sources of error should be added those due to malfunctioning hardware, defective software and operator mistakes, as well as random errors in the mechanism used to set and synchronize clocks. This report suggests a stochastic model and algorithms for computing a good estimator from time-offset samples measured between clocks connected via network links. Included in this report are descriptions of certain experiments which give an indication of the effectiveness of the algorithms. UNKNOWN UNKNOWN RFC0957 Experiments in network clock synchronization D.L. Mills September 01 1985 ASCII 68952 27 This RFC discusses some experiments in clock synchronization in the ARPA-Internet community, and requests discussion and suggestions for improvements. One of the services frequently neglected in computer network design is a high-quality, time-of-day clock capable of generating accurate timestamps with small errors compared to one-way network delays. Such a service would be useful for tracing the progress of complex transactions, synchronizing cached data bases, monitoring network performance and isolating problems. In this memo one such clock service design will be described and its performance assessed. This design has been incorporated as an integral part of the network routing and control protocols of the Distributed Computer Network (DCnet) architecture. UNKNOWN UNKNOWN RFC0958 Network Time Protocol (NTP) D.L. Mills September 01 1985 ASCII 30723 14 NTP time clock synchronization 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. RFC1059 RFC1119 RFC1305 UNKNOWN UNKNOWN RFC0959 File Transfer Protocol J. Postel J.K. Reynolds October 01 1985 ASCII 147316 69 FTP This memo is the official specification of the File Transfer Protocol (FTP) for the DARPA Internet community. The primary intent is to clarify and correct the documentation of the FTP specification, not to change the protocol. The following new optional commands are included in this edition of the specification: Change to Parent Directory (CDUP), Structure Mount (SMNT), Store Unique (STOU), Remove Directory (RMD), Make Directory (MKD), Print Directory (PWD), and System (SYST). Note that this specification is compatible with the previous edition. RFC0765 RFC2228 RFC2640 RFC2773 STD0009 STANDARD STANDARD RFC0960 Assigned numbers J.K. Reynolds J. Postel December 01 1985 ASCII 125814 60 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. RFC0943 RFC0990 HISTORIC UNKNOWN RFC0961 Official ARPA-Internet protocols J.K. Reynolds J. Postel December 01 1985 ASCII 52672 38 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. RFC0944 RFC0991 UNKNOWN UNKNOWN RFC0962 TCP-4 prime M.A. Padlipsky November 01 1985 ASCII 2773 2 This memo is in response to Bob Braden's call for a transaction oriented protocol (RFC-955), and continues the discussion of a possible transaction oriented transport protocol. This memo does not propose a standard. UNKNOWN UNKNOWN RFC0963 Some problems with the specification of the Military Standard Internet Protocol D.P. Sidhu November 01 1985 ASCII 44019 19 The purpose of this RFC is to provide helpful information on the Military Standard Internet Protocol (MIL-STD-1777) so that one can obtain a reliable implementation of this protocol. This paper points out several problems in this specification. This note also proposes solutions to these problems. UNKNOWN UNKNOWN RFC0964 Some problems with the specification of the Military Standard Transmission Control Protocol D.P. Sidhu November 01 1985 ASCII 20972 10 The purpose of this RFC is to provide helpful information on the Military Standard Transmission Control Protocol (MIL-STD-1778) so that one can obtain a reliable implementation of this protocol standard. This note points out three errors with this specification. This note also proposes solutions to these problems. UNKNOWN UNKNOWN RFC0965 Format for a graphical communication protocol L. Aguilar December 01 1985 ASCII 105456 51 This RFC describes the requirements for a graphical format on which to base a graphical on-line communication protocol, and proposes an Interactive Graphical Communication Format using the GKSM session metafile. We hope this contribution will encourage the discussion of multimedia data exchange and the proposal of solutions. UNKNOWN UNKNOWN RFC0966 Host groups: A multicast extension to the Internet Protocol S.E. Deering D.R. Cheriton December 01 1985 ASCII 59469 27 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. RFC0988 UNKNOWN UNKNOWN RFC0967 All victims together M.A. Padlipsky December 01 1985 ASCII 4706 2 This RFC proposes a new set of RFCs on how the networking code is integrated with various operating systems. It appears that this topic has not received enough exposure in the literature. Comments and suggestions are encouraged. UNKNOWN UNKNOWN RFC0968 Twas the night before start-up V.G. Cerf December 01 1985 ASCII 2459 2 This memo discusses problems that arise and debugging techniques used in bringing a new network into operation. UNKNOWN UNKNOWN RFC0969 NETBLT: A bulk data transfer protocol D.D. Clark M.L. Lambert L. Zhang December 01 1985 ASCII 40040 15 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. RFC0998 UNKNOWN UNKNOWN RFC0970 On packet switches with infinite storage J. Nagle December 01 1985 ASCII 35316 9 The purpose of this RFC is to focus discussion on a particular problem in the ARPA-Internet and possible methods of solution. Most prior work on congestion in datagram systems focuses on buffer management. In this memo the case of a packet switch with infinite storage is considered. Such a packet switch can never run out of buffers. It can, however, still become congested. The meaning of congestion in an infinite-storage system is explored. An unexpected result is found that shows a datagram network with infinite storage, first-in-first-out queuing, at least two packet switches, and a finite packet lifetime will, under overload, drop all packets. By attacking the problem of congestion for the infinite-storage case, new solutions applicable to switches with finite storage may be found. No proposed solutions this document are intended as standards for the ARPA-Internet at this time. UNKNOWN UNKNOWN RFC0971 Survey of data representation standards A.L. DeSchon January 01 1986 ASCII 22883 9 This RFC is a comparison of several data representation standards that are currently in use. The standards discussed are the CCITT X.409 recommendation, the NBS Computer Based Message System (CBMS) standard, DARPA Multimedia Mail system, the Courier remote procedure call protocol, and the SUN Remote Procedure Call package. No proposals in this document are intended as standards for the ARPA-Internet at this time. Rather, it is hoped that a general consensus will emerge as to the appropriate approach to a data representation standard, leading eventually to the adoption of an ARPA-Internet standard. UNKNOWN UNKNOWN RFC0972 Password Generator Protocol F.J. Wancho January 01 1986 ASCII 3890 2 This RFC specifies a standard for the ARPA Internet community. The Password Generator Service (PWDGEN) provides a set of six randomly generated eight-character "words" with a reasonable level of pronounceability, using a multi-level algorithm. Hosts on the ARPA Internet that choose to implement a password generator service are expected to adopt and implement this standard. UNKNOWN UNKNOWN RFC0973 Domain system changes and observations P.V. Mockapetris January 01 1986 ASCII 22364 10 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. RFC1034 RFC1035 RFC0882 RFC0883 UNKNOWN UNKNOWN RFC0974 Mail routing and the domain system C. Partridge January 01 1986 ASCII 18581 7 DNS-MX 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. RFC2821 STD0010 HISTORIC STANDARD RFC0975 Autonomous confederations D.L. Mills February 01 1986 ASCII 28010 10 This RFC proposes enhancements to the Exterior Gateway Protocol (EGP) to support a simple, multiple-level routing capability while preserving the robustness features of the current EGP model. The enhancements generalize the concept of core system to include multiple communities of autonomous systems, called autonomous confederations. Discussion and suggestions for improvement are requested. UNKNOWN UNKNOWN RFC0976 UUCP mail interchange format standard M.R. Horton February 01 1986 ASCII 26814 12 This document defines the standard format for the transmission of mail messages between computers in the UUCP Project. It does not however, address the format for storage of messages on one machine, nor the lower level transport mechanisms used to get the date from one machine to the next. It represents a standard for conformance by hosts in the UUCP zone. RFC1137 UNKNOWN UNKNOWN RFC0977 Network News Transfer Protocol B. Kantor P. Lapsley February 01 1986 ASCII 55062 27 NNTP 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. PROPOSED STANDARD PROPOSED STANDARD RFC0978 Voice File Interchange Protocol (VFIP) J.K. Reynolds R. Gillman W.A. Brackenridge A. Witkowski J. Postel February 01 1986 ASCII 9223 5 The purpose of the Voice File Interchange Protocol (VFIP) is to permit the interchange of various types of speech files between different systems in the ARPA-Internet community. Suggestions for improvement are encouraged. UNKNOWN UNKNOWN RFC0979 PSN End-to-End functional specification A.G. Malis March 01 1986 ASCII 39472 15 This memo is an updated version of BBN Report 5775, "End-to-End Functional Specification and describes important changes to the functionality of the interface between a Host and the PSN, and should be carefully reviewed by anyone involved in supporting a host on either the ARPANET or MILNET". The new End-to-End protocol (EE) is being developed in order to correct a number of deficiencies in the old EE, to improve its performance and overall throughput, and to better equip the Packet Switch Node (PSN, also known as the IMP) to support its current and anticipated host population. UNKNOWN UNKNOWN RFC0980 Protocol document order information O.J. Jacobsen J. Postel March 01 1986 ASCII 24416 12 This RFC indicates how to obtain various protocol documents used in the DARPA research community. Included is an overview of the new 1985 DDN Protocol Handbook and available sources for obtaining related documents (such as DOD, ISO, and CCITT). UNKNOWN UNKNOWN RFC0981 Experimental multiple-path routing algorithm D.L. Mills March 01 1986 ASCII 59069 22 This document introduces wiretap algorithms, a class of experimental, multiple routing algorithms that compute quasi-optimum routes for stations sharing a packet-radio broadcast channel. The primary route (a minimum-distance path), and additional paths ordered by distance, which serve as alternate routes should the primary route fail, are computed. This prototype is presented as an example of a class of routing algorithms and data-base management techniques that may find wider application in the Internet community. Discussions and suggestions for improvements are welcomed. UNKNOWN UNKNOWN RFC0982 Guidelines for the specification of the structure of the Domain Specific Part (DSP) of the ISO standard NSAP address H.W. Braun April 01 1986 ASCII 22595 11 This RFC is a draft working document of the ANSI "Guidelines for the Specification of the Structure of the Domain Specific Part (DSP) of the ISO Standard NSAP Address". It provides guidance to private address administration authorities on preferred formats and semantics for the Domain Specific Part (DSP) of an NSAP address. This RFC specifies the way in which the DSP may be constructed so as to facilitate efficient address assignment. This RFC is for informational purposes only and its distribution is unlimited and does not specify a standard of the ARPA-Internet. UNKNOWN UNKNOWN RFC0983 ISO transport arrives on top of the TCP D.E. Cass M.T. Rose April 01 1986 ASCII 59819 27 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. RFC1006 UNKNOWN UNKNOWN RFC0984 PCMAIL: A distributed mail system for personal computers D.D. Clark M.L. Lambert May 01 1986 ASCII 69333 31 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. RFC0993 UNKNOWN UNKNOWN RFC0985 Requirements for Internet gateways - draft National Science Foundation Network Technical Advisory Group May 01 1986 ASCII 59221 23 Requirements Internet gateways 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. Draft. RFC1009 UNKNOWN UNKNOWN RFC0986 Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol R.W. Callon H.W. Braun June 01 1986 ASCII 13950 7 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. Working draft. RFC1069 UNKNOWN UNKNOWN RFC0987 Mapping between X.400 and RFC 822 S.E. Kille June 01 1986 ASCII 127540 69 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. RFC1327 RFC2156 RFC1026 RFC1138 RFC1148 UNKNOWN UNKNOWN RFC0988 Host extensions for IP multicasting S.E. Deering July 01 1986 ASCII 45220 20 multicast Internet 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. RFC0966 RFC1054 RFC1112 UNKNOWN UNKNOWN RFC0989 Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures J. Linn February 01 1987 ASCII 63934 23 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. RFC1040 RFC1113 UNKNOWN UNKNOWN RFC0990 Assigned numbers J.K. Reynolds J. Postel November 01 1986 ASCII 174784 75 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. RFC0960 RFC1010 RFC0997 HISTORIC UNKNOWN RFC0991 Official ARPA-Internet protocols J.K. Reynolds J. Postel November 01 1986 ASCII 65205 46 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. RFC0961 RFC1011 UNKNOWN UNKNOWN RFC0992 On communication support for fault tolerant process groups K.P. Birman T.A. Joseph November 01 1986 ASCII 52313 18 This memo describes a collection of multicast communication primitives integrated with a mechanism for handling process failure and recovery. These primitives facilitate the implementation of fault-tolerant process groups, which can be used to provide distributed services in an environment subject to non-malicious crash failures. UNKNOWN UNKNOWN RFC0993 PCMAIL: A distributed mail system for personal computers D.D. Clark M.L. Lambert December 01 1986 ASCII 71725 28 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. RFC0984 RFC1056 UNKNOWN UNKNOWN RFC0994 Final text of DIS 8473, Protocol for Providing the Connectionless-mode Network Service International Organization for Standardization March 01 1986 ASCII 129006 52 This Protocol Standard is one of a set of International Standards produced to facilitate the interconnection of open systems. The set of standards covers the services and protocols required to achieve such interconnection. This Protocol Standard is positioned with respect to other related standards by the layers defined in the Reference Model for Open Systems Interconnection (ISO 7498). In particular, it is a protocol of the Network Layer. This Protocol may be used between network-entities in end systems or in Network Layer relay systems (or both). It provides the Connectionless-mode Network Service as defined in Addendum 1 to the Network Service Definition Covering Connectionless-mode Transmission (ISO 8348/AD1). RFC0926 UNKNOWN UNKNOWN RFC0995 End System to Intermediate System Routing Exchange Protocol for use in conjunction with ISO 8473 International Organization for Standardization April 01 1986 ASCII 94069 41 This Protocol is one of a set of International Standards produced to facilitate the interconnection of open systems. The set of standards covers the services and protocols required to achieve such interconnection. This Protocol is positioned with respect to other related standards by the layers defined in the Reference Model for Open Systems Interconnection (ISO 7498) and by the structure defined in the Internal Organization of the Network Layer (DIS 8648). In particular, it is a protocol of the Network Layer. This Protocol permits End Systems and Intermediate Systems to exchange configuration and routing information to facilitate the operation of the routing and relaying functions of the Network Layer. UNKNOWN UNKNOWN RFC0996 Statistics server D.L. Mills February 01 1987 ASCII 6127 3 STATSRV This RFC specifies a standard for the ARPA Internet community. Hosts and gateways on the DARPA Internet that choose to implement a remote statistics monitoring facility may use this protocol to send statistics data upon request to a monitoring center or debugging host. HISTORIC HISTORIC RFC0997 Internet numbers J.K. Reynolds J. Postel March 01 1987 ASCII 123919 42 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. RFC1020 RFC1117 RFC0990 UNKNOWN UNKNOWN RFC0998 NETBLT: A bulk data transfer protocol D.D. Clark M.L. Lambert L. Zhang March 01 1987 ASCII 57147 21 NETBLT This document is a description of, and a specification for, the NETBLT protocol. It is a revision of the specification published in RFC-969. NETBLT (NETwork BLock Transfer) is a transport level protocol intended for the rapid transfer of a large quantity of data between computers. It provides a transfer that is reliable and flow controlled, and is designed to provide maximum throughput over a wide variety of networks. Although NETBLT currently runs on top of the Internet Protocol (IP), it should be able to operate on top of any datagram protocol similar in function to IP. This document is published for discussion and comment, and does not constitute a standard. The proposal may change and certain parts of the protocol have not yet been specified; implementation of this document is therefore not advised. Obsoletes RFC-969. RFC0969 EXPERIMENTAL EXPERIMENTAL RFC0999 Requests For Comments summary notes: 900-999 A. Westine J. Postel April 01 1987 ASCII 62877 22 RFC0160 RFC1000 UNKNOWN UNKNOWN RFC1000 Request For Comments reference guide J.K. Reynolds J. Postel August 01 1987 ASCII 323960 149 This RFC Reference Guide is intended to provide a historical account by categorizing and summarizing of the Request for Comments numbers 1 through 999 issued between the years 1969-1987. These documents have been crossed referenced to indicate which RFCs are current, obsolete, or revised. RFC0999 UNKNOWN UNKNOWN RFC1001 Protocol standard for a NetBIOS service on a TCP/UDP transport: Concepts and methods NetBIOS Working Group in the Defense Advanced Research Projects Agency Internet Activities Board End-to-End Services Task Force March 01 1987 ASCII 158437 68 NETBIOS This RFC defines a proposed standard protocol to support NetBIOS services in a TCP/IP environment. Both local network and internet operation are supported. Various node types are defined to accommodate local and internet topologies and to allow operation with or without the use of IP broadcast. This RFC describes the NetBIOS-over-TCP protocols in a general manner, emphasizing the underlying ideas and techniques. Detailed specifications are found in a companion RFC, "Protocol Standard For a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications". STD0019 STANDARD STANDARD RFC1002 Protocol standard for a NetBIOS service on a TCP/UDP transport: Detailed specifications NetBIOS Working Group in the Defense Advanced Research Projects Agency Internet Activities Board End-to-End Services Task Force March 01 1987 ASCII 170262 84 NETBIOS This RFC defines a proposed standard protocol to support NetBIOS services in a TCP/IP environment. Both local network and internet operation are supported. Various node types are defined to accommodate local and internet topologies and to allow operation with or without the use of IP broadcast. This RFC gives the detailed specifications of the netBIOS-over-TCP packets, protocols, and defined constants and variables. A more general overview is found in a companion RFC, "Protocol Standard For NetBIOS Service on TCP/UDP Transport: Concepts and Methods". STD0019 STANDARD STANDARD RFC1003 Issues in defining an equations representation standard A.R. Katz March 01 1987 ASCII 19816 7 This memo is intended to identify and explore issues in defining a standard for the exchange of mathematical equations. No attempt is made at a complete definition and more questions are asked than are answered. Questions about the user interface are only addressed to the extent that they affect interchange issues. UNKNOWN UNKNOWN RFC1004 Distributed-protocol authentication scheme D.L. Mills April 01 1987 ASCII 21402 8 COOKIE-JAR The purpose of this RFC is to focus discussion on authentication problems in the Internet and possible methods of solution. The proposed solutions this document are not intended as standards for the Internet at this time. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to authentication problems, leading eventually to the adoption of standards. This document suggests mediated access-control and authentication procedures suitable for those cases when an association is to be set up between users belonging to different trust environments. EXPERIMENTAL EXPERIMENTAL RFC1005 ARPANET AHIP-E Host Access Protocol (enhanced AHIP) A. Khanna A.G. Malis May 01 1987 ASCII 69957 34 This RFC is a proposed specification for the encoding of Class A IP addresses for use on ARPANET-style networks such as the Milnet and Arpanet, and for enhancements to the ARPANET AHIP Host Access Protocol (AHIP; formerly known as 1822). These enhancements increase the size of the PSN field, allow ARPANET hosts to use logical names to address each other, allow for the communication of type-of-service information from the host to the PSN and enable the PSN to provide congestion feedback to the host on a connection basis. UNKNOWN UNKNOWN RFC1006 ISO transport services on top of the TCP: Version 3 M.T. Rose D.E. Cass May 01 1987 ASCII 31935 19 TP-TCP This memo specifies a standard for the Internet community. Hosts on the Internet that choose to implement ISO transport services on top of the TCP are expected to adopt and implement this standard. TCP port 102 is reserved for hosts which implement this standard. This memo specifies version 3 of the protocol and supersedes RFC-983. Changes between the protocol is described in RFC-983 and this memo are minor, but unfortunately incompatible. RFC0983 RFC2126 STD0035 STANDARD STANDARD RFC1007 Military supplement to the ISO Transport Protocol W. McCoy June 01 1987 ASCII 51280 23 This document supplements the Transport Service and Protocol of the International Standards Organization (ISO), IS 8072 and IS 8073, respectively, and their formal descriptions by providing conventions, option selections and parameter values. This RFC is being distributed to members of the Internet community in order to solicit comments on the Draft Military Supplement. While this document may not be directly relevant to the research problems of the Internet, it may be of some interest to a number of researchers and implementors. UNKNOWN UNKNOWN RFC1008 Implementation guide for the ISO Transport Protocol W. McCoy June 01 1987 ASCII 204664 73 This RFC is being distributed to members of the Internet community in order to solicit comments on the Implementors Guide. While this document may not be directly relevant to the research problems of the Internet, it may be of some interest to a number of researchers and implementors. UNKNOWN UNKNOWN RFC1009 Requirements for Internet gateways R.T. Braden J. Postel June 01 1987 ASCII 128173 54 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. RFC0985 RFC1812 HISTORIC HISTORIC RFC1010 Assigned numbers J.K. Reynolds J. Postel May 01 1987 ASCII 78179 44 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. RFC0990 RFC1060 HISTORIC UNKNOWN RFC1011 Official Internet protocols J.K. Reynolds J. Postel May 01 1987 ASCII 74593 52 This memo is an official status report on the protocols used in the Internet community. It identifies the documents specifying the official protocols used in the Internet. Comments indicate any revisions or changes planned. RFC0991 UNKNOWN UNKNOWN RFC1012 Bibliography of Request For Comments 1 through 999 J.K. Reynolds J. Postel June 01 1987 ASCII 129194 64 This RFC is a reference guide for the Internet community which provides a bibliographic summary of the Request for Comments numbers 1 through 999 issued between the years 1969-1987. INFORMATIONAL INFORMATIONAL RFC1013 X Window System Protocol, version 11: Alpha update April 1987 R.W. Scheifler June 01 1987 ASCII 244905 101 This RFC is distributed to the Internet community for information only. It does not establish an Internet standard. The X window system has been widely reviewed and tested. The Internet community is encouraged to experiment with it. UNKNOWN UNKNOWN RFC1014 XDR: External Data Representation standard Sun Microsystems June 01 1987 ASCII 39316 20 XDR is a standard for the description and encoding of data. It is useful for transferring data between different computer architectures. XDR fits into ISO presentation layer, and is roughly analogous in purpose to X.409, ISO Abstract Syntax Notation. The major difference between these two is that XDR uses implicit typing, while X.409 uses explicit typing. This RFC is distributed for information only, it does not establish a Internet standard. UNKNOWN UNKNOWN RFC1015 Implementation plan for interagency research Internet B.M. Leiner July 01 1987 ASCII 63159 24 This RFC proposes an Interagency Research Internet as the natural outgrowth of the current Internet. This is an "idea paper" and discussion is strongly encouraged. UNKNOWN UNKNOWN RFC1016 Something a host could do with source quench: The Source Quench Introduced Delay (SQuID) W. Prue J. Postel July 01 1987 ASCII 47922 18 The memo is intended to explore the issue of what a host could do with a source quench. The proposal is for each source host IP module to introduce some delay between datagrams sent to the same destination host. This is a "crazy idea paper" and discussion is essential. UNKNOWN UNKNOWN RFC1017 Network requirements for scientific research: Internet task force on scientific computing B.M. Leiner August 01 1987 ASCII 49512 19 This RFC identifies the requirements on communication networks for supporting scientific research. It proposes some specific areas for near term work, as well as some long term goals. This is an "idea" paper and discussion is strongly encouraged. UNKNOWN UNKNOWN RFC1018 Some comments on SQuID A.M. McKenzie August 01 1987 ASCII 7931 3 This memo is a discussion of some of the ideas expressed in RFC-1016 on Source Quench. This memo introduces the distinction of the cause of congestion in a gateway between the effects of "Funneling" and Mismatch". It is offered in the same spirit as RFC-1016; to stimulate discussion. The opinions offered are personal, not corporate, opinions. UNKNOWN UNKNOWN RFC1019 Report of the Workshop on Environments for Computational Mathematics D. Arnon September 01 1987 ASCII 21151 8 This memo is a report on the discussion of the representation of equations in a workshop at the ACM SIGGRAPH Conference held in Anaheim, California on 30 July 1987. UNKNOWN UNKNOWN RFC1020 Internet numbers S. Romano M.K. Stahl November 01 1987 ASCII 146864 51 This RFC is a list of the Assigned IP Network Numbers and EGP Autonomous System Numbers. This RFC obsoletes RFC-997. RFC0997 RFC1062 RFC1117 RFC1166 UNKNOWN UNKNOWN RFC1021 High-level Entity Management System (HEMS) C. Partridge G. Trewitt October 01 1987 ASCII 12993 5 HEMS This memo provides a general overview of the High-level Entity management system (HEMS). This system is experimental, and is currently being tested in portions of the Internet. HISTORIC HISTORIC RFC1022 High-level Entity Management Protocol (HEMP) C. Partridge G. Trewitt October 01 1987 ASCII 25348 12 This memo presents an application protocol for managing network entities such as hosts, gateways, and front end machines. This protocol is a component of the High-level Entity Management System HEMS), described is RFC-1021. This memo also assumes a knowledge of the ISO data encoding standard, ASN.1. UNKNOWN UNKNOWN RFC1023 HEMS monitoring and control language G. Trewitt C. Partridge October 01 1987 ASCII 40992 17 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. RFC1076 UNKNOWN UNKNOWN RFC1024 HEMS variable definitions C. Partridge G. Trewitt October 01 1987 ASCII 126536 74 This memo assigns instruction codes, defines object formats and object semantics for use with the High-Level Monitoring and Control Language, defined in RFC-1023. A general system has been described in previous memos (RFC-1021, RFC-1022). This system is called the High-Level Entity Management System (HEMS). This memo is provisional and the definitions are subject to change. Readers should confirm with the authors that they have the most recent version. This RFC assumes a working knowledge of the ISO data encoding standard, ASN.1, and a general understanding of the IP protocol suite. UNKNOWN UNKNOWN RFC1025 TCP and IP bake off J. Postel September 01 1987 ASCII 11648 6 This memo describes some of the procedures, scoring and tests used in the TCP and IP bake offs held in the early development of these protocols. These procedures and tests may still be of use in testing newly implemented TCP and IP modules. UNKNOWN UNKNOWN RFC1026 Addendum to RFC 987: (Mapping between X.400 and RFC-822) S.E. Kille September 01 1987 ASCII 7117 4 This memo suggest a proposed protocol for the Internet community, and request discussion and suggestions for improvements. RFC1327 RFC2156 RFC0987 RFC1138 RFC1148 UNKNOWN UNKNOWN RFC1027 Using ARP to implement transparent subnet gateways S. Carl-Mitchell J.S. Quarterman October 01 1987 ASCII 21297 8 This RFC describes the use of the Address Resolution Protocol (ARP) by subnet gateways to permit hosts on the connected subnets to communicate without being aware of the existence of subnets, using the technique of "Proxy ARP". UNKNOWN UNKNOWN RFC1028 Simple Gateway Monitoring Protocol J. Davin J.D. Case M. Fedor M.L. Schoffstall November 01 1987 ASCII 82440 35 SGMP This memo defines a simple application-layer protocol by which management information for a gateway may be inspected or altered by remote users. This proposal is intended only as an interim response to immediate gateway monitoring needs. HISTORIC HISTORIC RFC1029 More fault tolerant approach to address resolution for a Multi-LAN system of Ethernets G. Parr May 01 1988 ASCII 44019 17 arp This memo discusses an extension to a Bridge Protocol to detect and disclose changes in heighbouring host address parameters in a Multi-Lan system of Ethernets. The problem is one which is appearing more and more regularly as the interconnected systems grow larger on Campuses and in Commercial Institutions. This RFC suggests a protocol enhancement for the Internet community, and requests discussion and suggestions for improvements. UNKNOWN UNKNOWN RFC1030 On testing the NETBLT Protocol over divers networks M.L. Lambert November 01 1987 ASCII 40964 16 This memo describes the results gathered from testing NETBLT over three networks of different bandwidths and round-trip delays. The results are not complete, but the information gathered so far has not been promising. The NETBLT protocol is specified in RFC-998; this document assumes an understanding of the specification as described in RFC-998. UNKNOWN UNKNOWN RFC1031 MILNET name domain transition W.D. Lazear November 01 1987 ASCII 20137 10 This RFC consolidates information necessary for the implementation of domain style names throughout the DDN/MILNET Internet community. The introduction of domain style names will impact all hosts in the DDN/MILNET Internet. This RFC is designed as an aid to implementors and administrators by providing: 1) an overview of the transition process from host tables to domains, 2) a timetable for the transition, and 3) references to documentation and software relating to the domain system. UNKNOWN UNKNOWN RFC1032 Domain administrators guide M.K. Stahl November 01 1987 ASCII 29454 14 Domains are administrative entities that provide decentralized management of host naming and addressing. The domain-naming system is distributed and hierarchical. This memo describes procedures for registering a domain with the Network Information Center (NIC) of Defense Data Network (DDN), and offers guidelines on the establishment and administration of a domain in accordance with the requirements specified in RFC-920. It is recommended that the guidelines described in this document be used by domain administrators in the establishment and control of second-level domains. The role of the domain administrator (DA) is that of coordinator, manager, and technician. If his domain is established at the second level or lower in the tree, the domain administrator must register by interacting with the management of the domain directly above this. UNKNOWN UNKNOWN RFC1033 Domain administrators operations guide M. Lottor November 01 1987 ASCII 37263 22 This RFC provides guidelines for domain administrators in operating a domain server and maintaining their portion of the hierarchical database. Familiarity with the domain system is assumed (see RFCs 1031, 1032, 1034, and 1035). UNKNOWN UNKNOWN RFC1034 Domain names - concepts and facilities P.V. Mockapetris November 01 1987 ASCII 129180 55 DOMAIN This RFC is the revised basic definition of The Domain Name System. It obsoletes RFC-882. This memo describes the domain style names and their used for host address look up and electronic mail forwarding. It discusses the clients and servers in the domain name system and the protocol used between them. RFC0973 RFC0882 RFC0883 RFC1101 RFC1183 RFC1348 RFC1876 RFC1982 RFC2065 RFC2181 RFC2308 RFC2535 RFC4033 RFC4034 RFC4035 STD0013 STANDARD STANDARD RFC1035 Domain names - implementation and specification P.V. Mockapetris November 01 1987 ASCII 125626 55 DOMAIN This RFC is the revised specification of the protocol and format used in the implementation of the Domain Name System. It obsoletes RFC-883. This memo documents the details of the domain name client - server communication. RFC0973 RFC0882 RFC0883 RFC1101 RFC1183 RFC1348 RFC1876 RFC1982 RFC1995 RFC1996 RFC2065 RFC2136 RFC2181 RFC2137 RFC2308 RFC2535 RFC2845 RFC3425 RFC3658 RFC4033 RFC4034 RFC4035 STD0013 STANDARD STANDARD RFC1036 Standard for interchange of USENET messages M.R. Horton R. Adams December 01 1987 ASCII 46891 19 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. RFC0850 UNKNOWN UNKNOWN RFC1037 NFILE - a file access protocol B. Greenberg S. Keene December 01 1987 ASCII 197312 86 NFILE This document includes a specification of the NFILE file access protocol and its underlying levels of protocol, the Token List Transport Layer and Byte Stream with Mark. The goal of this specification is to promote discussion of the ideas described here, and to encourage designers of future file protocols to take advantage of these ideas. A secondary goal is to make the specification available to sites that might benefit from implementing NFILE. HISTORIC HISTORIC RFC1038 Draft revised IP security option M. St. Johns January 01 1988 ASCII 15879 7 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". RFC1108 UNKNOWN UNKNOWN RFC1039 DoD statement on Open Systems Interconnection protocols D. Latham January 01 1988 ASCII 6194 3 This RFC reproduces a memorandum issued on 2-JUL-87 from the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASDC31) to the Director of the Defense Communications Agency (DCA). This memo is distributed for information only. RFC0945 UNKNOWN UNKNOWN RFC1040 Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures J. Linn January 01 1988 ASCII 76276 29 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. RFC0989 RFC1113 UNKNOWN UNKNOWN RFC1041 Telnet 3270 regime option Y. Rekhter January 01 1988 ASCII 11608 6 TOPT-3270 This RFC specifies a proposed standard for the Internet community. Hosts on the Internet that want to support 3270 data stream within the Telnet protocol, are expected to adopt and implement this standard. PROPOSED STANDARD PROPOSED STANDARD RFC1042 Standard for the transmission of IP datagrams over IEEE 802 networks J. Postel J.K. Reynolds February 01 1988 ASCII 34359 15 IP-IEEE This RFC specifies a standard method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on IEEE 802 Networks to allow compatible and interoperable implementations. This RFC specifies a protocol standard for the Internet community. RFC0948 STD0043 STANDARD STANDARD RFC1043 Telnet Data Entry Terminal option: DODIIS implementation A. Yasuda T. Thompson February 01 1988 ASCII 59478 26 TOPT-DATA This RFC suggests a proposed protocol on the TELNET Data Entry Terminal (DET) Option - DODIIS Implementation for the Internet community. It is intended that this specification be capatible with the specification of DET Option in RFC-732. Discussion and suggests for improvements are encouraged. RFC0732 PROPOSED STANDARD PROPOSED STANDARD RFC1044 Internet Protocol on Network System's HYPERchannel: Protocol specification K. Hardwick J. Lekashman February 01 1988 ASCII 103241 43 IP-HC This memo intends to provide a complete discussion of the protocols and techniques used to embed DoD standard Internet Protocol datagrams (and its associated higher level protocols) on Network Systems Corporation's HYPERchannel equipment. This document is directed toward network planners and implementors who are already familiar with the TCP/IP protocol suite and the techniques used to carry TCP/IP traffic on common networks such as the DDN or the Ethernet. No great familiarity with NSC products is assumed; an appendix is devoted to a review of NSC technologies and protocols. STD0045 STANDARD STANDARD RFC1045 VMTP: Versatile Message Transaction Protocol: Protocol specification D.R. Cheriton February 01 1988 ASCII 272058 128 VMTP This memo specifies the Versatile Message Transaction Protocol (VMTP) [Version 0.7 of 19-Feb-88], a transport protocol specifically designed to support the transaction model of communication, as exemplified by remote procedure call (RPC). The full function of VMTP, including support for security, real-time, asynchronous message exchanges, streaming, multicast and idempotency, provides a rich selection to the VMTP user level. Subsettability allows the VMTP module for particular clients and servers to be specialized and simplified to the services actually required. Examples of such simple clients and servers include PROM network bootload programs, network boot servers, data sensors and simple controllers, to mention but a few examples. This RFC describes a protocol proposed as a standard for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1046 Queuing algorithm to provide type-of-service for IP links W. Prue J. Postel February 01 1988 ASCII 30106 11 This memo is intended to explore how Type-of-Service might be implemented in the Internet. The proposal describes a method of queuing which can provide the different classes of service. The technique also prohibits one class of service from consuming excessive resources or excluding other classes of service. This is an "idea paper" and discussion is strongly encouraged. UNKNOWN UNKNOWN RFC1047 Duplicate messages and SMTP C. Partridge February 01 1988 ASCII 5888 3 An examination of a synchronization problem in the Simple Mail Transfer Protocol (SMTP) is presented. This synchronization problem can cause a message to be delivered multiple times. A method for avoiding this problem is suggested. Nodding familiarity with the SMTP specification, RFC-821, is required. UNKNOWN UNKNOWN RFC1048 BOOTP vendor information extensions P.A. Prindeville February 01 1988 ASCII 15423 7 This memo proposes an addition to the Bootstrap Protocol (BOOTP). Comments and suggestions for improvements are sought. RFC1084 RFC1395 RFC1497 RFC1533 UNKNOWN UNKNOWN RFC1049 Content-type header field for Internet messages M.A. Sirbu March 01 1988 ASCII 18923 8 CONTENT This memo suggests proposed additions to the Internet Mail Protocol, RFC-822, for the Internet community, and requests discussion and suggestions for improvements. HISTORIC STANDARD RFC1050 RPC: Remote Procedure Call Protocol specification Sun Microsystems April 01 1988 ASCII 51540 24 SUN-RPC 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. RFC1057 HISTORIC HISTORIC RFC1051 Standard for the transmission of IP datagrams and ARP packets over ARCNET networks P.A. Prindeville March 01 1988 ASCII 7779 4 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. RFC1201 HISTORIC STANDARD RFC1052 IAB recommendations for the development of Internet network management standards V.G. Cerf April 01 1988 ASCII 30569 14 This RFC is intended to convey to the Internet community and other interested parties the recommendations of the Internet Activities Board (IAB) for the development of network management protocols for use in the TCP/IP environment. This memo does NOT, in and of itself, define or propose an Official Internet Protocol. It does reflect, however, the policy of the IAB with respect to further network management development in the short and long term. UNKNOWN UNKNOWN RFC1053 Telnet X.3 PAD option S. Levy T. Jacobson April 01 1988 ASCII 48952 21 TOPT-X.3 This RFC proposes a new option to Telnet for the Internet community, and requests discussion and suggestions for improvements. PROPOSED STANDARD PROPOSED STANDARD RFC1054 Host extensions for IP multicasting S.E. Deering May 01 1988 ASCII 45465 19 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. RFC0988 RFC1112 UNKNOWN UNKNOWN RFC1055 Nonstandard for transmission of IP datagrams over serial lines: SLIP J.L. Romkey June 01 1988 ASCII 12911 6 IP-SLIP The TCP/IP protocol family runs over a variety of network media: IEEE 802.3 (ethernet) and 802.5 (token ring) LAN's, X.25 lines, satellite links, and serial lines. There are standard encapsulations for IP packets defined for many of these networks, but there is no standard for serial lines. SLIP, Serial Line IP, is a currently a de facto standard, commonly used for point-to-point serial connections running TCP/IP. It is not an Internet standard. STD0047 STANDARD STANDARD RFC1056 PCMAIL: A distributed mail system for personal computers M.L. Lambert June 01 1988 ASCII 85368 38 PCMAIL This memo is a discussion of the Pcmail workstation based distributed mail system. It is identical to the discussion in RFC-993, save that a new, much simpler mail transport protocol is described. The new transport protocol is the result of continued research into ease of protocol implementation and use issues. RFC0993 INFORMATIONAL INFORMATIONAL RFC1057 RPC: Remote Procedure Call Protocol specification: Version 2 Sun Microsystems June 01 1988 ASCII 52462 25 SUN-RPC This RFC describes a standard that Sun Microsystems and others are using, and is one we wish to propose for the Internet's consideration. This memo is not an Internet standard at this time. RFC1050 INFORMATIONAL INFORMATIONAL RFC1058 Routing Information Protocol C.L. Hedrick June 01 1988 ASCII 93285 33 RIP This RFC describes an existing protocol for exchanging routing information among gateways and other hosts. It is intended to be used as a basis for developing gateway software for use in the Internet community. RFC1388 RFC1723 HISTORIC HISTORIC RFC1059 Network Time Protocol (version 1) specification and implementation D.L. Mills July 01 1988 ASCII 140890 58 NTP NTPv1 time clock synchronization 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. RFC0958 RFC1119 RFC1305 UNKNOWN UNKNOWN RFC1060 Assigned numbers J.K. Reynolds J. Postel March 01 1990 ASCII 177923 86 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. RFC1010 RFC1340 RFC1349 HISTORIC UNKNOWN RFC1061 RFC1062 Internet numbers S. Romano M.K. Stahl M. Recker August 01 1988 ASCII 198729 65 This memo is an official status report on the network numbers and gateway autonomous system numbers used in the Internet community. RFC1020 RFC1117 RFC1166 UNKNOWN UNKNOWN RFC1063 IP MTU discovery options J.C. Mogul C.A. Kent C. Partridge K. McCloghrie July 01 1988 ASCII 27121 11 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. RFC1191 UNKNOWN UNKNOWN RFC1064 Interactive Mail Access Protocol: Version 2 M.R. Crispin July 01 1988 ASCII 57813 26 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. RFC1176 RFC1203 UNKNOWN UNKNOWN RFC1065 Structure and identification of management information for TCP/IP-based internets K. McCloghrie M.T. Rose August 01 1988 ASCII 38858 21 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. RFC1155 STANDARD STANDARD RFC1066 Management Information Base for network management of TCP/IP-based internets K. McCloghrie M.T. Rose August 01 1988 ASCII 135177 90 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. RFC1156 UNKNOWN UNKNOWN RFC1067 Simple Network Management Protocol J.D. Case M. Fedor M.L. Schoffstall J. Davin August 01 1988 ASCII 69592 33 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. RFC1098 UNKNOWN UNKNOWN RFC1068 Background File Transfer Program (BFTP) A.L. DeSchon R.T. Braden August 01 1988 ASCII 51004 27 FTP This RFC describes an Internet background file transfer service that is built upon the third-party transfer model of FTP. No new protocols are involved. The purpose of this memo is to stimulate discussions on new Internet service modes. UNKNOWN UNKNOWN RFC1069 Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol R.W. Callon H.W. Braun February 01 1989 ASCII 24268 10 This RFC suggests an addressing scheme for use with the ISO Connectionless Network Protocol (CLNP) in the Internet. This is a solution to one of the problems inherent in the use of "ISO-grams" in the Internet. This memo is a revision of RFC 986. This RFC suggests a proposed protocol for the Internet community, and requests discussion and suggestions for improvements. RFC0986 UNKNOWN UNKNOWN RFC1070 Use of the Internet as a subnetwork for experimentation with the OSI network layer R.A. Hagens N.E. Hall M.T. Rose February 01 1989 ASCII 37354 17 This RFC proposes a scenario for experimentation with the International Organization for Standardization (ISO) Open Systems Interconnection (OSI) network layer protocols over the Internet and requests discussion and suggestions for improvements to this scenario. This RFC also proposes the creation of an experimental OSI internet. To participate in the experimental OSI internet, a system must abide by the agreements set forth in this RFC. UNKNOWN UNKNOWN RFC1071 Computing the Internet checksum R.T. Braden D.A. Borman C. Partridge September 01 1988 ASCII 54941 24 This RFC summarizes techniques and algorithms for efficiently computing the Internet checksum. It is not a standard, but a set of useful implementation techniques. RFC1141 UNKNOWN UNKNOWN RFC1072 TCP extensions for long-delay paths V. Jacobson R.T. Braden October 01 1988 ASCII 36000 16 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. RFC1323 RFC2018 UNKNOWN UNKNOWN RFC1073 Telnet window size option D. Waitzman October 01 1988 ASCII 7639 4 TOPT-NAWS This RFC describes a proposed Telnet option to allow a client to convey window size to a Telnet server. PROPOSED STANDARD PROPOSED STANDARD RFC1074 NSFNET backbone SPF based Interior Gateway Protocol J. Rekhter October 01 1988 ASCII 10872 5 This RFC is an implementation description of the standard ANSI IS-IS and ISO ES-IS routing protocols within the NSFNET backbone network. UNKNOWN UNKNOWN RFC1075 Distance Vector Multicast Routing Protocol D. Waitzman C. Partridge S.E. Deering November 01 1988 ASCII 54731 24 IP-DVMRP This RFC describes a distance-vector-style routing protocol for routing multicast datagrams through an internet. It is derived from the Routing Information Protocol (RIP), and implements multicasting as described in RFC-1054. This is an experimental protocol, and its implementation is not recommended at this time. EXPERIMENTAL EXPERIMENTAL RFC1076 HEMS monitoring and control language G. Trewitt C. Partridge November 01 1988 ASCII 98774 42 This RFC specifies a query language for monitoring and control of network entities. This RFC supercedes RFC 1023, extending the query language and providing more discussion of the underlying issues. This language is a component of the High-Level Entity Monitoring System (HEMS) described in RFC 1021 and RFC 1022. Readers may wish to consult these RFCs when reading this memo. RFC 1024 contains detailed assignments of numbers and structures used in this system. Portions of RFC 1024 that define query language structures are superceded by definitions in this memo. This memo assumes a knowledge of the ISO data encoding standard, ASN.1. RFC1023 UNKNOWN UNKNOWN RFC1077 Critical issues in high bandwidth networking B.M. Leiner November 01 1988 ASCII 116464 46 This memo presents the results of a working group on High Bandwidth Networking. This RFC is for your information and you are encouraged to comment on the issues presented. UNKNOWN UNKNOWN RFC1078 TCP port service Multiplexer (TCPMUX) M. Lottor November 01 1988 ASCII 3248 2 This RFC proposes an Internet standard which can be used by future TCP services instead of using 'well-known ports'. UNKNOWN UNKNOWN RFC1079 Telnet terminal speed option C.L. Hedrick December 01 1988 ASCII 4942 3 TOPT-TS This RFC specifies a standard for the Internet community. Hosts on the Internet that exchange terminal speed information within the Telnet protocol are expected to adopt and implement this standard. PROPOSED STANDARD PROPOSED STANDARD RFC1080 Telnet remote flow control option C.L. Hedrick November 01 1988 ASCII 6688 4 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. RFC1372 UNKNOWN UNKNOWN RFC1081 Post Office Protocol: Version 3 M.T. Rose November 01 1988 ASCII 37009 16 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. RFC1225 UNKNOWN UNKNOWN RFC1082 Post Office Protocol: Version 3: Extended service offerings M.T. Rose November 01 1988 ASCII 25423 11 This memo suggests a simple method for workstations to dynamically access mail from a discussion group server, as an extension to an earlier memo which dealt with dynamically accessing mail from a mailbox server using the Post Office Protocol - Version 3 (POP3). This RFC specifies a proposed protocol for the Internet community, and requests discussion and suggestions for improvements. All of the extensions described in this memo to the POP3 are OPTIONAL. UNKNOWN UNKNOWN RFC1083 IAB official protocol standards Defense Advanced Research Projects Agency Internet Activities Board December 01 1988 ASCII 27128 12 IAB official protocol standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures is presented first, followed by discussions of the standardization process and the RFC document series, then the explanation of the terms is presented, the lists of protocols in each stage of standardization follows, and finally pointers to references and contacts for further information. This memo is issued quarterly, please be sure the copy you are reading is dated within the last three months. RFC1100 HISTORIC UNKNOWN RFC1084 BOOTP vendor information extensions J.K. Reynolds December 01 1988 ASCII 16327 8 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. RFC1048 RFC1395 RFC1497 RFC1533 UNKNOWN UNKNOWN RFC1085 ISO presentation services on top of TCP/IP based internets M.T. Rose December 01 1988 ASCII 64643 32 RFC 1006 describes a mechanism for providing the ISO transport service on top of TCP/IP. Once this method is applied, one may implement "real" ISO applications on top of TCP/IP-based internets, by simply implementing OSI session, presentation, and application services on top of the transport service access point which is provided on top of the TCP. Although straight-forward, there are some environments in which the richness provided by the OSI application layer is desired, but it is nonetheless impractical to implement the underlying OSI infrastructure (i.e., the presentation, session, and transport services on top of the TCP). This memo describes an approach for providing "stream-lined" support of OSI application services on top of TCP/IP-based internets for such constrained environments. This memo proposes a standard for the Internet community. UNKNOWN UNKNOWN RFC1086 ISO-TP0 bridge between TCP and X.25 J.P. Onions M.T. Rose December 01 1988 ASCII 19934 9 This memo proposes a standard for the Internet community. Hosts on the Internet that choose to implement ISO TP0 transport connectivity between TCP and X.25 based hosts are expected to experiment with this proposal. TCP port 146 is reserved for this proposal. UNKNOWN UNKNOWN RFC1087 Ethics and the Internet Defense Advanced Research Projects Agency Internet Activities Board January 01 1989 ASCII 4582 2 Ethics Internet This memo is a statement of policy by the Internet Activities Board (IAB) concerning the proper use of the resources of the Internet. UNKNOWN UNKNOWN RFC1088 Standard for the transmission of IP datagrams over NetBIOS networks L.J. McLaughlin February 01 1989 ASCII 5749 3 IP-NETBIOS This document specifies a standard method of encapsulating the Internet Protocol (IP) datagrams on NetBIOS networks. STD0048 STANDARD STANDARD RFC1089 SNMP over Ethernet M.L. Schoffstall J. Davin M. Fedor J.D. Case February 01 1989 ASCII 4458 3 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. UNKNOWN UNKNOWN RFC1090 SMTP on X.25 R. Ullmann February 01 1989 ASCII 6141 4 This memo proposes a standard for SMTP on the virtual circuit facility provided by the X.25 standard of the CCITT. UNKNOWN UNKNOWN RFC1091 Telnet terminal-type option J. VanBokkelen February 01 1989 ASCII 13439 7 TOPT-TERM This RFC specifies a standard for the Internet community. Hosts on the Internet that exchange terminal type information within the Telnet protocol are expected to adopt and implement this standard. This standard supersedes RFC 930. A change is made to permit cycling through a list of possible terminal types and selecting the most appropriate RFC0930 PROPOSED STANDARD PROPOSED STANDARD RFC1092 EGP and policy based routing in the new NSFNET backbone J. Rekhter February 01 1989 ASCII 11865 5 This memo discusses implementation decisions for routing issues in the NSFNET, especially in the NSFNET Backbone. Of special concern is the restriction of routing information to advertize the best route as established by a policy decision. UNKNOWN UNKNOWN RFC1093 NSFNET routing architecture H.W. Braun February 01 1989 ASCII 20629 9 This document describes the routing architecture for the NSFNET centered around the new NSFNET Backbone, with specific emphasis on the interface between the backbone and its attached networks. UNKNOWN UNKNOWN RFC1094 NFS: Network File System Protocol specification Sun Microsystems March 01 1989 ASCII 51454 27 SUN-NFS This RFC describes a protocol that Sun Microsystems, Inc., and others are using. A new version of the protocol is under development, but others may benefit from the descriptions of the current protocol, and discussion of some of the design issues. 10/29/03 - back in June 2002, Matthew Wilcox sent an email stating that RFC 3010 is listed as erronously obsoleting RFCs 1813 and 1094. This was confirmed by Scott Bradner in October 2003. I have removed the Obsoleted by tag for for this entry. RFC1813 INFORMATIONAL INFORMATIONAL RFC1095 Common Management Information Services and Protocol over TCP/IP (CMOT) U.S. Warrier L. Besaw April 01 1989 ASCII 157506 67 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. RFC1189 UNKNOWN UNKNOWN RFC1096 Telnet X display location option G.A. Marcy March 01 1989 ASCII 4634 3 TOPT-XDL This RFC specifies a standard for the Internet community. Hosts on the Internet that transmit the X display location within the Telnet protocol are expected to adopt and implement this standard. PROPOSED STANDARD PROPOSED STANDARD RFC1097 Telnet subliminal-message option B. Miller April 01 1989 ASCII 5490 3 This RFC specifies a standard for the Internet community. Hosts on the Internet that display subliminal messages within the Telnet protocol are expected to adopt and implement this standard. UNKNOWN UNKNOWN RFC1098 Simple Network Management Protocol (SNMP) J.D. Case M. Fedor M.L. Schoffstall J. Davin April 1989 ASCII 71563 34 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. RFC1067 RFC1157 UNKNOWN UNKNOWN RFC1099 Request for Comments Summary: RFC Numbers 1000-1099 J. Reynolds December 1991 ASCII 49108 22 INFORMATIONAL INFORMATIONAL RFC1100 IAB official protocol standards Defense Advanced Research Projects Agency Internet Activities Board April 01 1989 ASCII 30101 14 IAB official protocol standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures is presented first, followed by discussions of the standardization process and the RFC document series, then the explanation of the terms is presented, the lists of protocols in each stage of standardization follows, and finally pointers to references and contacts for further information. This memo is issued quarterly, please be sure the copy you are reading is dated within the last three months. Current copies may be obtained from the Network Information Center or from the Internet Assigned Numbers Authority (see the contact information at the end of this memo). Do not use this memo after 31-July-89. RFC1083 RFC1130 HISTORIC STANDARD RFC1101 DNS encoding of network names and other types P.V. Mockapetris April 01 1989 ASCII 28677 14 This RFC proposes two extensions to the Domain Name System: - A specific method for entering and retrieving RRs which map between network names and numbers. - Ideas for a general method for describing mappings between arbitrary identifiers and numbers. The method for mapping between network names and addresses is a proposed standard, the ideas for a general method are experimental. RFC1034 RFC1035 UNKNOWN UNKNOWN RFC1102 Policy routing in Internet protocols D.D. Clark May 01 1989 ASCII 59664 22 The purpose of this RFC is to focus discussion on particular problems in the Internet and possible methods of solution. No proposed solutions in this document are intended as standards for the Internet. UNKNOWN UNKNOWN RFC1103 Proposed standard for the transmission of IP datagrams over FDDI Networks D. Katz June 01 1989 ASCII 19439 9 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] RFC1188 UNKNOWN UNKNOWN RFC1104 Models of policy based routing H.W. Braun June 01 1989 ASCII 25468 10 The purpose of this RFC is to outline a variety of models for policy based routing. The relative benefits of the different approaches are reviewed. Discussions and comments are explicitly encouraged to move toward the best policy based routing model that scales well within a large internetworking environment. UNKNOWN UNKNOWN RFC1105 Border Gateway Protocol (BGP) K. Lougheed Y. Rekhter June 01 1989 ASCII 37644 17 BGP This RFC outlines a specific approach for the exchange of network reachability information between Autonomous Systems. Updated by RFCs 1163 and 1164. [STANDARDS-TRACK] RFC1163 EXPERIMENTAL EXPERIMENTAL RFC1106 TCP big window and NAK options R. Fox June 01 1989 ASCII 37105 13 This memo discusses two extensions to the TCP protocol to provide a more efficient operation over a network with a high bandwidth*delay product. The extensions described in this document have been implemented and shown to work using resources at NASA. This memo describes an Experimental Protocol, these extensions are not proposed as an Internet standard, but as a starting point for further research. UNKNOWN UNKNOWN RFC1107 Plan for Internet directory services K.R. Sollins July 01 1989 ASCII 51773 19 This memo proposes a program to develop a directory service for the Internet. It reports the results of a meeting held in February 1989, which was convened to review requirements and options for such a service. This proposal is offered for comment, and does not represent a committed research activity of the Internet community. INFORMATIONAL INFORMATIONAL RFC1108 U.S. Department of Defense Security Options for the Internet Protocol S. Kent November 1991 ASCII 41791 17 IPSO This RFC specifies the U.S. Department of Defense Basic Security Option and the top-level description of the Extended Security Option for use with the Internet Protocol. This RFC obsoletes RFC 1038, "Revised IP Security Option", dated January 1988. [STANDARDS-TRACK] RFC1038 HISTORIC HISTORIC RFC1109 Report of the second Ad Hoc Network Management Review Group V.G. Cerf August 01 1989 ASCII 20642 8 This RFC reports an official Internet Activities Board (IAB) policy position on the treatment of Network Management in the Internet. This RFC presents the results and recommendations of the second Ad Hoc Network Management Review on June 12, 1989. The results of the first such meeting were reported in RFC 1052. UNKNOWN UNKNOWN RFC1110 Problem with the TCP big window option A.M. McKenzie August 01 1989 ASCII 5778 3 This memo comments on the TCP Big Window option described in RFC 1106. UNKNOWN UNKNOWN RFC1111 Request for comments on Request for Comments: Instructions to RFC authors J. Postel August 01 1989 ASCII 11793 6 This RFC specifies a standard for the Internet community. Authors of RFCs are expected to adopt and implement this standard. RFC0825 RFC1543 RFC2223 INFORMATIONAL INFORMATIONAL RFC1112 Host extensions for IP multicasting S.E. Deering August 01 1989 ASCII 39904 17 IGMP multicast This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. Recommended procedure for IP multicasting in the Internet. This RFC obsoletes RFCs 998 and 1054. [STANDARDS-TRACK] RFC0988 RFC1054 RFC2236 STD0005 STANDARD STANDARD RFC1113 Privacy enhancement for Internet electronic mail: Part I - message encipherment and authentication procedures J. Linn August 01 1989 ASCII 89293 34 This RFC specifies features for private electronic mail based on encryption technology. [STANDARDS-TRACK] Draft. RFC0989 RFC1040 RFC1421 HISTORIC HISTORIC RFC1114 Privacy enhancement for Internet electronic mail: Part II - certificate-based key management S.T. Kent J. Linn August 01 1989 ASCII 69661 25 This RFC specifies the key management aspects of Privacy Enhanced Mail. [STANDARDS-TRACK] Draft. RFC1422 HISTORIC HISTORIC RFC1115 Privacy enhancement for Internet electronic mail: Part III - algorithms, modes, and identifiers J. Linn August 01 1989 ASCII 18226 8 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] Draft. RFC1423 HISTORIC HISTORIC RFC1116 Telnet Linemode option D.A. Borman August 01 1989 ASCII 47473 21 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] RFC1184 PROPOSED STANDARD PROPOSED STANDARD RFC1117 Internet numbers S. Romano M.K. Stahl M. Recker August 01 1989 ASCII 324666 109 This memo is an official status report on the network numbers and the autonomous system numbers used in the Internet community. RFC1062 RFC1020 RFC0997 RFC1166 INFORMATIONAL INFORMATIONAL RFC1118 Hitchhikers guide to the Internet E. Krol September 01 1989 ASCII 62757 24 This RFC is being distributed to members of the Internet community in order to make available some "hints" which will allow new network participants to understand how the direction of the Internet is set, how to acquire online information and how to be a good Internet neighbor. While the information discussed may not be relevant to the research problems of the Internet, it may be interesting to a number of researchers and implementors. No standards are defined or specified in this memo. INFORMATIONAL INFORMATIONAL RFC1119 Network Time Protocol (version 2) specification and implementation D.L. Mills September 01 1989 ASCII 143 1 PS 518020 PDF 187940 NTP NTPv2 time clock synchronization 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] See also RFC1129 RFC0958 RFC1059 RFC1305 STD0012 STANDARD STANDARD RFC1120 Internet Activities Board V. Cerf September 01 1989 ASCII 26123 11 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. RFC1160 INFORMATIONAL INFORMATIONAL RFC1121 Act one - the poems J. Postel L. Kleinrock V.G. Cerf B. Boehm September 01 1989 ASCII 10644 6 This RFC presents a collection of poems that were presented at "Act One", a symposium held partially in celebration of the 20th anniversary of the ARPANET. INFORMATIONAL INFORMATIONAL RFC1122 Requirements for Internet Hosts - Communication Layers R. Braden Editor October 1989 ASCII 295992 116 applicability This RFC is an official specification for the Internet community. It incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts. [STANDARDS-TRACK] RFC1349 STD0003 STANDARD STANDARD RFC1123 Requirements for Internet Hosts - Application and Support R. Braden Editor October 1989 ASCII 245503 98 applicability This RFC is an official specification for the Internet community. It incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts. [STANDARDS-TRACK] RFC0822 RFC1349 RFC2181 STD0003 STANDARD STANDARD RFC1124 Policy issues in interconnecting networks B.M. Leiner September 01 1989 ASCII 118 1 PS 315692 PDF 143819 To support the activities of the Federal Research Internet Coordinating Committee (FRICC) in creating an interconnected set of networks to serve the research community, two workshops were held to address the technical support of policy issues that arise when interconnecting such networks. Held under the suspices of the Internet Activities Board at the request of the FRICC, and sponsored by NASA through RIACS, the workshops addressed the required and feasible technologies and architectures that could be used to satisfy the desired policies for interconnection. The purpose of this RFC is to report the results of these workshops. UNKNOWN UNKNOWN RFC1125 Policy requirements for inter Administrative Domain routing D. Estrin November 01 1989 ASCII 55248 21 PS 282123 PDF 289862 The purpose of this memo is to focus discussion on particular problems in the Internet and possible methods of solution. No proposed solutions in this document are intended as standards for the Internet. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to such problems, leading eventually to the development and adoption of standards. UNKNOWN UNKNOWN RFC1126 Goals and functional requirements for inter-autonomous system routing M. Little October 01 1989 ASCII 62725 25 This document describes the functional requirements for a routing protocol to be used between autonomous systems. This document is intended as a necessary precursor to the design of a new inter- autonomous system routing protocol and specifies requirements for the Internet applicable for use with the current DoD IP, the ISO IP, and future Internet Protocols. It is intended that these requirements will form the basis for the future development of a new inter-autonomous systems routing architecture and protocol. This memo does not specify a standard. UNKNOWN UNKNOWN RFC1127 Perspective on the Host Requirements RFCs R.T. Braden October 01 1989 ASCII 41267 20 This RFC is for information only; it does not constitute a standard, draft standard, or proposed standard, and it does not define a protocol. INFORMATIONAL INFORMATIONAL RFC1128 Measured performance of the Network Time Protocol in the Internet system D.L. Mills October 01 1989 ASCII 314 1 PS 633742 PDF 197897 This paper describes a series of experiments involving over 100,000 hosts of the Internet system and located in the U.S., Europe and the Pacific. The experiments are designed to evaluate the availability, accuracy and reliability of international standard time distribution using the DARPA/NSF Internet and the Network Time Protocol (NTP), which is specified in RFC-1119. NTP is designed specifically for use in a large, diverse internet system operating at speeds from mundane to lightwave. In NTP a distributed subnet of time servers operating in a self-organizing, hierarchical, master-slave configuration exchange precision timestamps in order to synchronize subnet clocks to each other and national time standards via wire or radio. The experiments are designed to locate Internet hosts and gateways that provide time by one of three time distribution protocols and evaluate the accuracy of their indications. For those hosts that support NTP, the experiments determine the distribution of errors and other statistics over paths spanning major portions of the globe. Finally, the experiments evaluate the accuracy and reliability of precision timekeeping using NTP and typical Internet paths involving DARPA, NSFNET and other agency networks. The experiments demonstrate that timekeeping accuracy throughout most portions of the Internet can be ordinarily maintained to within a few tens of milliseconds, even in cases of failure or disruption of clocks, time servers or networks. This memo does not specify a standard. UNKNOWN UNKNOWN RFC1129 Internet Time Synchronization: The Network Time Protocol D.L. Mills October 01 1989 ASCII 298 1 PS 551697 PDF 197036 NTP This memo describes the Network Time Protocol (NTP) designed to distribute time information in a large, diverse internet system operating at speeds from mundane to lightwave. It uses a returnable- time architecture in which a distributed subnet of time servers operating in a self-organizing, hierarchical, master-slave configuration synchronizes local clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute time information within a network via local routing algorithms and time daemons. The architectures, algorithms and protocols which have evolved to NTP over several years of implementation and refinement are described in this paper. The synchronization subnet which has been in regular operation in the Internet for the last several years is described along with performance data which shows that timekeeping accuracy throughout most portions of the Internet can be ordinarily maintained to within a few tens of milliseconds, even in cases of failure or disruption of clocks, time servers or networks. This memo describes the Network Time Protocol in RFC-1119. RFC1119 INFORMATIONAL INFORMATIONAL RFC1130 IAB official protocol standards Defense Advanced Research Projects Agency Internet Activities Board October 01 1989 ASCII 33858 17 IAB official protocol standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). RFC1100 RFC1140 HISTORIC STANDARD RFC1131 OSPF specification J. Moy October 01 1989 ASCII 268 1 PS 857280 PDF 398863 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] RFC1247 PROPOSED STANDARD PROPOSED STANDARD RFC1132 Standard for the transmission of 802.2 packets over IPX networks L.J. McLaughlin November 01 1989 ASCII 8128 4 IP-IPX This document specifies a standard method of encapsulating 802.2 packets on networks supporting Novell's Internet Packet Exchange Protocol (IPX). It obsoletes earlier documents detailing the transmission of Internet packets over IPX networks. It differs from these earlier documents in that it allows for the transmission of multiple network protocols over IPX and for the transmission of packets through IPX bridges. STD0049 STANDARD STANDARD RFC1133 Routing between the NSFNET and the DDN J.Y. Yu H.W. Braun November 01 1989 ASCII 23169 10 This document is a case study of the implementation of routing between the NSFNET and the DDN components (the MILNET and the ARPANET). We hope that it can be used to expand towards interconnection of other Administrative Domains. We would welcome discussion and suggestions about the methods employed for the interconnections. No standards are specified in this memo. INFORMATIONAL INFORMATIONAL RFC1134 Point-to-Point Protocol: A proposal for multi-protocol transmission of datagrams over Point-to-Point links D. Perkins November 01 1989 ASCII 87352 38 This proposal is the product of the Point-to-Point Protocol Working Group of the Internet Engineering Task Force (IETF). Comments on this memo should be submitted to the IETF Point-to-Point Protocol Working Group chair by January 15, 1990. Comments will be reviewed at the February 1990 IETF meeting, with the goal of advancing PPP to draft standard status. [STANDARDS-TRACK] RFC1171 PROPOSED STANDARD PROPOSED STANDARD RFC1135 Helminthiasis of the Internet J.K. Reynolds December 01 1989 ASCII 77033 33 This memo takes a look back at the helminthiasis (infestation with, or disease caused by parasitic worms) of the Internet that was unleashed the evening of 2 November 1988. This RFC provides information about an event that occurred in the life of the Internet. This memo does not specify any standard. This document provides a glimpse at the infection, its festering, and cure. The impact of the worm on the Internet community, ethics statements, the role of the news media, crime in the computer world, and future prevention is discussed. A documentation review presents four publications that describe in detail this particular parasitic computer program. Reference and bibliography sections are also included. INFORMATIONAL INFORMATIONAL RFC1136 Administrative Domains and Routing Domains: A model for routing in the Internet S. Hares D. Katz December 01 1989 ASCII 22158 10 This RFC proposes a model for describing routing within the Internet. The model is an adaptation of the "OSI Routeing Framework". This memo does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1137 Mapping between full RFC 822 and RFC 822 with restricted encoding S. Kille December 01 1989 ASCII 6266 3 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. RFC0976 HISTORIC HISTORIC RFC1138 Mapping between X.400(1988) / ISO 10021 and RFC 822 S.E. Kille December 01 1989 ASCII 191029 92 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. RFC1327 RFC2156 RFC0822 RFC0987 RFC1026 RFC1148 EXPERIMENTAL EXPERIMENTAL RFC1139 Echo function for ISO 8473 R.A. Hagens January 01 1990 ASCII 14229 6 This memo defines an echo function for the connection-less network layer protocol. Two mechanisms are introduced that may be used to implement the echo function. The first mechanism is recommended as an interim solution for the Internet community. The second mechanism will be progressed to the ANSI X3S3.3 working group for consideration as a work item. When an ISO standard is adopted that provides functionality similar to that described by this memo, then this memo will become obsolete and superceded by the ISO standard. This memo is not intended to compete with an ISO standard. [STANDARDS-TRACK] RFC1574 RFC1575 PROPOSED STANDARD PROPOSED STANDARD RFC1140 IAB official protocol standards Defense Advanced Research Projects Agency Internet Activities Board May 01 1990 ASCII 60501 27 IAB official protocol standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo is issued quarterly, please be sure the copy you are reading is dated within the last three months. Current copies may be obtained from the Network Information Center or from the Internet Assigned Numbers Authority. Do not use this edition after 31-Aug-90. RFC1130 RFC1200 HISTORIC STANDARD RFC1141 Incremental updating of the Internet checksum T. Mallory A. Kullberg January 01 1990 ASCII 3587 2 This memo correctly describes the incremental update procedure for use with the standard Internet checksum. It is intended to replace the description of Incremental Update in RFC 1071. This is not a standard but rather, an implementation technique. RFC1071 RFC1624 INFORMATIONAL INFORMATIONAL RFC1142 OSI IS-IS Intra-domain Routing Protocol D. Oran Editor February 01 1990 ASCII 425379 517 PS 1440951 PDF 490300 Domain Routing ISO This RFC is a republication of ISO DP 10589 as a service to the Internet community. This is not an Internet standard. INFORMATIONAL INFORMATIONAL RFC1143 The Q Method of Implementing TELNET Option Negotiation D.J. Bernstein February 01 1990 ASCII 23331 10 This is RFC discusses an implementation approach to option negotiation in the Telnet protocol (RFC 854). It does not propose any changes to the TELNET protocol. Rather, it discusses the implementation of the protocol of one feature, only. This is not a protocol specification. This is an experimental method of implementing a protocol. EXPERIMENTAL EXPERIMENTAL RFC1144 Compressing TCP/IP headers for low-speed serial links V. Jacobson February 01 1990 ASCII 120959 49 PS 534729 PDF 255616 IP-CMPRS This RFC describes a method for compressing the headers of TCP/IP datagrams to improve performance over low speed serial links. The motivation, implementation and performance of the method are described. C code for a sample implementation is given for reference. [STANDARDS- TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1145 TCP alternate checksum options J. Zweig C. Partridge February 01 1990 ASCII 11052 5 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. RFC1146 EXPERIMENTAL EXPERIMENTAL RFC1146 TCP alternate checksum options J. Zweig C. Partridge March 01 1990 ASCII 10955 5 TCP-ACO 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. RFC1145 EXPERIMENTAL EXPERIMENTAL RFC1147 FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices R.H. Stine April 01 1990 ASCII 336906 177 PS 555225 PDF 308602 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. RFC1470 INFORMATIONAL INFORMATIONAL RFC1148 Mapping between X.400(1988) / ISO 10021 and RFC 822 S.E. Kille March 01 1990 ASCII 194292 94 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. RFC1327 RFC2156 RFC0822 RFC0987 RFC1026 RFC1138 EXPERIMENTAL EXPERIMENTAL RFC1149 Standard for the transmission of IP datagrams on avian carriers D. Waitzman April 01 1990 ASCII 3329 2 avian carrier april fools This memo describes an experimental method for the encapsulation of IP datagrams in avian carriers. This specification is primarily useful in Metropolitan Area Networks. This is an experimental, not recommended standard. RFC2549 EXPERIMENTAL EXPERIMENTAL RFC1150 FYI on FYI: Introduction to the FYI Notes G.S. Malkin J.K. Reynolds March 01 1990 ASCII 7867 4 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.] FYI0001 INFORMATIONAL INFORMATIONAL RFC1151 Version 2 of the Reliable Data Protocol (RDP) C. Partridge R.M. Hinden April 01 1990 ASCII 8293 4 RDP This RFC suggests several updates to the specification of the Reliable Data Protocol (RDP) in RFC-908 based on experience with the protocol. This revised version of the protocol is experimental. RFC0908 EXPERIMENTAL EXPERIMENTAL RFC1152 Workshop report: Internet research steering group workshop on very-high-speed networks C. Partridge April 01 1990 ASCII 64003 23 This memo is a report on a workshop sponsored by the Internet Research Steering Group. This memo is for information only. This RFC does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1153 Digest message format F.J. Wancho April 01 1990 ASCII 6632 4 DMF-MAIL This memo describes the de facto standard Digest Message Format. This is an elective experimental protocol. EXPERIMENTAL EXPERIMENTAL RFC1154 Encoding header field for internet messages D. Robinson R. Ullmann April 01 1990 ASCII 12214 7 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). RFC1505 EXPERIMENTAL EXPERIMENTAL RFC1155 Structure and identification of management information for TCP/IP-based internets M.T. Rose K. McCloghrie May 01 1990 ASCII 40927 22 SMI This RFC is a re-release of RFC 1065, with a changed "Status of this Memo", plus a few minor typographical corrections. The technical content of the document is unchanged from RFC 1065. [STANDARDS-TRACK] RFC1065 STD0016 STANDARD STANDARD RFC1156 Management Information Base for network management of TCP/IP-based internets K. McCloghrie M.T. Rose May 01 1990 ASCII 138781 91 MIB-I This RFC is a re-release of RFC 1066, with a changed "Status of this Memo", "IAB Policy Statement", and "Introduction" sections plus a few minor typographical corrections. The technical content of the document is unchanged from RFC 1066. [STANDARDS-TRACK] RFC1066 HISTORIC HISTORIC RFC1157 Simple Network Management Protocol (SNMP) J.D. Case M. Fedor M.L. Schoffstall J. Davin May 01 1990 ASCII 74894 36 SNMP This RFC is a re-release of RFC 1098, with a changed "Status of this Memo" section plus a few minor typographical corrections. This memo defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. [STANDARDS-TRACK] RFC1098 STD0015 HISTORIC STANDARD RFC1158 Management Information Base for network management of TCP/IP-based internets: MIB-II M.T. Rose May 01 1990 ASCII 212152 133 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] RFC1213 PROPOSED STANDARD PROPOSED STANDARD RFC1159 Message Send Protocol R. Nelson June 01 1990 ASCII 3957 2 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. RFC1312 EXPERIMENTAL EXPERIMENTAL RFC1160 Internet Activities Board V. Cerf May 01 1990 ASCII 28182 11 This RFC provides a history and description of the Internet Activities Board (IAB) and its subsidiary organizations. This memo is for informational use and does not constitute a standard. This is a revision of RFC 1120. RFC1120 INFORMATIONAL INFORMATIONAL RFC1161 SNMP over OSI M.T. Rose June 01 1990 ASCII 16036 8 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, RFC1418 EXPERIMENTAL EXPERIMENTAL RFC1162 Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) Management Information Base G. Satz June 01 1990 ASCII 109893 70 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. RFC1238 EXPERIMENTAL EXPERIMENTAL RFC1163 Border Gateway Protocol (BGP) K. Lougheed Y. Rekhter June 01 1990 ASCII 69404 29 BGP This RFC, together with its companion RFC-1164, "Application of the Border Gateway Protocol in the Internet", specify an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK] RFC1105 RFC1267 HISTORIC HISTORIC RFC1164 Application of the Border Gateway Protocol in the Internet J.C. Honig D. Katz M. Mathis Y. Rekhter J.Y. Yu June 01 1990 ASCII 56278 23 BGP 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] RFC1268 HISTORIC HISTORIC RFC1165 Network Time Protocol (NTP) over the OSI Remote Operations Service J. Crowcroft J.P. Onions June 01 1990 ASCII 18277 10 NTP-OSI This memo suggests an Experimental Protocol for the OSI and Internet communities. Hosts in either community, and in particular those on both are encouraged to experiment with this mechanism. EXPERIMENTAL EXPERIMENTAL RFC1166 Internet numbers S. Kirkpatrick M.K. Stahl M. Recker July 01 1990 ASCII 566778 182 This memo is a status report on the network numbers and autonomous system numbers used in the Internet community. RFC1117 RFC1062 RFC1020 INFORMATIONAL INFORMATIONAL RFC1167 Thoughts on the National Research and Education Network V.G. Cerf July 01 1990 ASCII 20682 8 The memo provides a brief outline of a National Research and Education Network (NREN). This memo provides information for the Internet community. It does not specify any standard. It is not a statement of IAB policy or recommendations. INFORMATIONAL INFORMATIONAL RFC1168 Intermail and Commercial Mail Relay services A. Westine A.L. DeSchon J. Postel C.E. Ward July 01 1990 ASCII 40306 18 PS 149816 PDF 55890 This RFC discusses the history and evolution of the Intermail and Commercial mail systems. The problems encountered in operating a store-and-forward mail relay between commercial systems such as Telemail, MCI Mail and Dialcom are also discussed. This RFC provides information for the Internet community, and does not specify any standard. INFORMATIONAL INFORMATIONAL RFC1169 Explaining the role of GOSIP V.G. Cerf K.L. Mills August 01 1990 ASCII 30255 15 This informational RFC represents the official view of the Internet Activities Board (IAB), after coordination with the Federal Networking Council (FNC). This RFC does not specify a standard. INFORMATIONAL INFORMATIONAL RFC1170 Public key standards and licenses R.B. Fougner January 01 1991 ASCII 3144 2 This RFC is a public statement by Public Key Partners regarding Public Key Standards and Licenses. This memo is for informational use only, and does not constitute an Internet standard. INFORMATIONAL INFORMATIONAL RFC1171 Point-to-Point Protocol for the transmission of multi-protocol datagrams over Point-to-Point links D. Perkins July 01 1990 ASCII 92321 51 This memo specifies the Point-to-Point Protocol (PPP) as a Draft Standard Protocol for the Internet community. When it becomes a full Standard, this protocol will be recommended for all TCP/IP implementations that communicate over serial links. RFC1134 RFC1331 DRAFT STANDARD DRAFT STANDARD RFC1172 Point-to-Point Protocol (PPP) initial configuration options D. Perkins R. Hobby July 01 1990 ASCII 76132 40 This memo specifies the Point-to-Point Protocol (PPP) Initial Configuration Options as a Proposed Standard Protocol for the Internet community. When it becomes a full Standard, this protocol will be recommended for all TCP/IP implementations that communicate over serial links. RFC1331 RFC1332 PROPOSED STANDARD PROPOSED STANDARD RFC1173 Responsibilities of host and network managers: A summary of the "oral tradition" of the Internet J. VanBokkelen August 01 1990 ASCII 12527 5 This informational RFC describes the conventions to be followed by those in charge of networks and hosts in the Internet. It is a summary of the "oral tradition" of the Internet on this subject. [RFC Editor's note: This memo is a contribution by the author of his view of these conventions. It is expected that this RFC will provide a basis for the development of official policies in the future.] These conventions may be supplemented or amended by the policies of specific local and regional components of the Internet. This RFC does not specify a standard, or a policy of the IAB. INFORMATIONAL INFORMATIONAL RFC1174 IAB recommended policy on distributing internet identifier assignment and IAB recommended policy change to internet "connected" status V.G. Cerf August 01 1990 ASCII 21321 9 This informational RFC represents the official view of the Internet Activities Board (IAB), and describes the recommended policies and procedures on distributing Internet identifier assignments and dropping the connected status requirement. This RFC does not specify a standard. INFORMATIONAL INFORMATIONAL RFC1175 FYI on where to start: A bibliography of internetworking information K.L. Bowers T.L. LaQuey J.K. Reynolds K. Roubicek M.K. Stahl A. Yuan August 01 1990 ASCII 67330 43 This FYI RFC is a bibliography of information about TCP/IP internetworking, prepared by the User Services Working Group (USWG) of the Internet Engineering Task Force (IETF). This memo provides information for the Internet community. It does not specify any standard. [Also FYI 3.] FYI0003 INFORMATIONAL INFORMATIONAL RFC1176 Interactive Mail Access Protocol: Version 2 M.R. Crispin August 01 1990 ASCII 67330 30 IMAP2 This RFC suggests a method for personal computers and workstations to dynamically access mail from a mailbox server ("repository"). It obosoletes RFC 1064. This RFC specifies an Experimental Protocol for the Internet community. Discussion and suggestions for improvement are requested. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. RFC1064 EXPERIMENTAL EXPERIMENTAL RFC1177 FYI on Questions and Answers: Answers to commonly asked "new internet user" questions G.S. Malkin A.N. Marine J.K. Reynolds August 01 1990 ASCII 52852 24 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.] RFC1206 INFORMATIONAL INFORMATIONAL RFC1178 Choosing a name for your computer D. Libes August 01 1990 ASCII 18472 8 This FYI RFC is a republication of a Communications of the ACM article on guidelines on what to do and what not to do when naming your computer. This memo provides information for the Internet community. It does not specify any standard. [Also FYI 5.] FYI0005 INFORMATIONAL INFORMATIONAL RFC1179 Line printer daemon protocol L. McLaughlin August 01 1990 ASCII 24324 14 LPDP This RFC describes an existing print server protocol widely used on the Internet for communicating between line printer daemons (both clients and servers). This memo is for informational purposes only, and does not specify an Internet standard. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. INFORMATIONAL INFORMATIONAL RFC1180 TCP/IP tutorial T.J. Socolofsky C.J. Kale January 01 1991 ASCII 65494 28 This RFC is a tutorial on the TCP-IP protocol suite, focusing particularly on the steps in forwarding an IP datagram from source host to destination host through a router. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1181 RIPE Terms of Reference R. Blokzijl September 01 1990 ASCII 2523 2 This RFC describes the Terms of Reference of RIPE (Reseaux IP Europeens), the cooperation of European IP networks. This memo provides information for the Internet community. It does not specify any standard. INFORMATIONAL INFORMATIONAL RFC1182 RFC1183 New DNS RR Definitions C.F. Everhart L.A. Mamakos R. Ullmann P.V. Mockapetris October 01 1990 ASCII 23788 11 DNS-RR This memo defines five new DNS types for experimental purposes. This RFC describes an Experimental Protocol for the Internet community, and requests discussion and suggestions for improvements. RFC1034 RFC1035 EXPERIMENTAL EXPERIMENTAL RFC1184 Telnet Linemode Option D.A. Borman October 01 1990 ASCII 53085 23 TOPT-LINE This RFC specifies a procedure for line at a time terminal interaction based on the Telnet Protocol. It obsoletes RFC 1116. [STANDARDS-TRACK] RFC1116 DRAFT STANDARD DRAFT STANDARD RFC1185 TCP Extension for High-Speed Paths V. Jacobson R.T. Braden L. Zhang October 01 1990 ASCII 49508 21 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. RFC1323 EXPERIMENTAL EXPERIMENTAL RFC1186 MD4 Message Digest Algorithm R.L. Rivest October 01 1990 ASCII 35391 18 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. RFC1320 INFORMATIONAL INFORMATIONAL RFC1187 Bulk Table Retrieval with the SNMP M.T. Rose K. McCloghrie J.R. Davin October 01 1990 ASCII 27220 12 SNMP-BULK This memo reports an interesting family of algorithms for bulk table retrieval using the Simple Network Management Protocol (SNMP). This memo describes an Experimental Protocol for the Internet community, and requests discussion and suggestions for improvements. This memo does not specify a standard for the Internet community. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. EXPERIMENTAL EXPERIMENTAL RFC1188 Proposed Standard for the Transmission of IP Datagrams over FDDI Networks D. Katz October 01 1990 ASCII 22424 11 This memo defines a method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK] RFC1103 DRAFT STANDARD DRAFT STANDARD RFC1189 Common Management Information Services and Protocols for the Internet (CMOT and CMIP) U.S. Warrier L. Besaw L. LaBarre B.D. Handspicker October 01 1990 ASCII 32928 15 CMOT This memo defines a network management architecture that uses the International Organization for Standardization's (ISO) Common Management Information Services/Common Management Information Protocol (CMIS/CMIP) in the Internet. [STANDARDS-TRACK] RFC1095 HISTORIC HISTORIC RFC1190 Experimental Internet Stream Protocol: Version 2 (ST-II) C. Topolcic October 01 1990 ASCII 386909 148 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. IEN119 RFC1819 EXPERIMENTAL EXPERIMENTAL RFC1191 Path MTU discovery J.C. Mogul S.E. Deering November 01 1990 ASCII 47936 19 IP-MTU This memo describes a technique for dynamically discovering the maximum transmission unit (MTU) of an arbitrary internet path. It specifies a small change to the way routers generate one type of ICMP message. For a path that passes through a router that has not been so changed, this technique might not discover the correct Path MTU, but it will always choose a Path MTU as accurate as, and in many cases more accurate than, the Path MTU that would be chosen by current practice. [STANDARDS- TRACK] RFC1063 DRAFT STANDARD DRAFT STANDARD RFC1192 Commercialization of the Internet summary report B. Kahin November 01 1990 ASCII 35253 13 This memo is based on a workshop held by the Science, Technology and Public Policy Program of the John F. Kennedy School of Government, Harvard University, March 1-3, 1990. This memo provides information for the Internet community. It does not specify any standard. INFORMATIONAL INFORMATIONAL RFC1193 Client requirements for real-time communication services D. Ferrari November 01 1990 ASCII 61540 24 This memo describes client requirements for real-time communication services. This memo provides information for the Internet community, and requests discussion and suggestions for improvements. It does not specify any standard. INFORMATIONAL INFORMATIONAL RFC1194 Finger User Information Protocol D.P. Zimmerman November 01 1990 ASCII 24626 12 This memo describes the Finger User Information Protocol. This is a simple protocol which provides an interface to a remote user information program. Based on RFC 742, a description of the original Finger protocol, this memo attempts to clarify the expected communication between the two ends of a Finger connection. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition. [STANDARDS-TRACK] RFC0742 RFC1196 RFC1288 DRAFT STANDARD DRAFT STANDARD RFC1195 Use of OSI IS-IS for routing in TCP/IP and dual environments R.W. Callon December 01 1990 ASCII 187866 85 PS 362052 IS-IS This memo specifies an integrated routing protocol, based on the OSI Intra-Domain IS-IS Routing Protocol, which may be used as an interior gateway protocol (IGP) to support TCP/IP as well as OSI. This allows a single routing protocol to be used to support pure IP environments, pure OSI environments, and dual environments. This specification was developed by the IS-IS working group of the Internet Engineering Task Force. [STANDARDS-TRACK] RFC1349 PROPOSED STANDARD PROPOSED STANDARD RFC1196 Finger User Information Protocol D.P. Zimmerman December 01 1990 ASCII 24799 12 This memo describes the Finger User Information Protocol. This is a simple protocol which provides an interface to a remote user information program. Based on RFC 742, a description of the original Finger protocol, this memo attempts to clarify the expected communication between the two ends of a Finger connection. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition. This edition corrects and clarifies in a minor way, RFC 1194. [STANDARDS-TRACK] RFC1194 RFC0742 RFC1288 DRAFT STANDARD DRAFT STANDARD RFC1197 Using ODA for translating multimedia information M. Sherman December 01 1990 ASCII 3620 2 The purpose of this RFC is to inform implementors of multimedia systems about our experiences using ISO 8613: Office Document Architecture (ODA). Because ODA is being proposed as an encoding format for use in multimedia mail and file exchange, implementors wishing to use ODA in an open systems environment may profit from our experiences. This memo provides information for the Internet community. It does not specify any standard. INFORMATIONAL INFORMATIONAL RFC1198 FYI on the X window system R.W. Scheifler January 01 1991 ASCII 3629 3 This FYI RFC provides pointers to the published standards of the MIT X Consortium. This memo provides information for the Internet community. It does not specify any Internet standard. FYI0006 INFORMATIONAL INFORMATIONAL RFC1199 Request for Comments Summary Notes: 1100-1199 J. Reynolds December 01 1991 ASCII 46443 22 Summary RFC INFORMATIONAL INFORMATIONAL RFC1200 IAB official protocol standards Defense Advanced Research Projects Agency Internet Activities Board April 01 1991 ASCII 67069 31 IAB official protocol standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures is presented first, followed by discussions of the standardization process and the RFC document series, then the explanation of the terms is presented, the lists of protocols in each stage of standardization follows, and finally pointers to references and contacts for further information. RFC1140 RFC1250 HISTORIC STANDARD RFC1201 Transmitting IP traffic over ARCNET networks D. Provan February 01 1991 ASCII 16959 7 IP-ARC This memo defines a protocol for the transmission of IP and ARP packets over the ARCnet Local Area Network.This memo specifies a method of encapsulating Internet Protocol (IP) and Address Resolution Protocol (ARP) datagrams for transmission across ARCNET using the "ARCNET Packet Header Definition Standard". [STANDARDS-TRACK] RFC1051 STD0046 STANDARD STANDARD RFC1202 Directory Assistance service M.T. Rose February 01 1991 ASCII 21645 11 DAS This document defines a mechanism by which a user-interface may access a textual DAP-like interface over a TCP/IP connection. This is a local mechanism. This memo provides information for the Internet community. It does not specify any standard. INFORMATIONAL INFORMATIONAL RFC1203 Interactive Mail Access Protocol: Version 3 J. Rice February 01 1991 ASCII 123325 49 IMAP3 This RFC suggests a method for workstations to access mail dynamically from a mailbox server ("repository"). The following document is a modified version of RFC 1064, the definition of the IMAP2 protocol. This RFC specifies an Experimental Protocol for the Internet community. It does not specify any standard. RFC1064 HISTORIC HISTORIC RFC1204 Message Posting Protocol (MPP) S. Yeh D. Lee February 01 1991 ASCII 11371 6 MPP This memo describes a protocol for posting messages from workstations (e.g., PCs) to a mail service host. This RFC specifies an Experimental Protocol for the Internet community. It does not specify any standard. EXPERIMENTAL EXPERIMENTAL RFC1205 5250 Telnet interface P. Chmielewski February 01 1991 ASCII 27179 12 This RFC is being distributed in order to document the interface to the IBM 5250 Telnet implementation. This memo provides information for the Internet community. It does not specify any standard. RFC2877 INFORMATIONAL INFORMATIONAL RFC1206 FYI on Questions and Answers: Answers to commonly asked "new Internet user" questions G.S. Malkin A.N. Marine February 01 1991 ASCII 72479 32 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] RFC1177 RFC1325 INFORMATIONAL INFORMATIONAL RFC1207 FYI on Questions and Answers: Answers to commonly asked "experienced Internet user" questions G.S. Malkin A.N. Marine J.K. Reynolds February 01 1991 ASCII 33385 15 This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A), produced by the User Services Working Group of the Internet Engineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify any standard. FYI0007 INFORMATIONAL INFORMATIONAL RFC1208 Glossary of networking terms O.J. Jacobsen D.C. Lynch March 01 1991 ASCII 41156 18 This RFC is a glossary adapted from "The INTEROP Pocket Glossary of Networking Terms" distributed at Interop '90. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1209 Transmission of IP datagrams over the SMDS Service D.M. Piscitello J. Lawrence March 01 1991 ASCII 25280 11 IP-SMDS This memo defines a protocol for the transmission of IP and ARP packets over a Switched Multi-megabit Data Service Network configured as a logical IP subnetwork. [STANDARDS-TRACK] STD0052 STANDARD STANDARD RFC1210 Network and infrastructure user requirements for transatlantic research collaboration: Brussels, July 16-18, and Washington July 24-25, 1990 V.G. Cerf P.T. Kirstein B. Randell March 01 1991 ASCII 79048 36 This report complements a shorter printed version which appeared in a summary report of all the committees which met in Brussels and Washington last July, 1990. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1211 Problems with the maintenance of large mailing lists A. Westine J. Postel March 01 1991 ASCII 96167 54 This RFC discusses problems with maintaining large mailing lists, especially the processing of error reports. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1212 Concise MIB definitions M.T. Rose K. McCloghrie March 01 1991 ASCII 43579 19 Concise-MIB This memo describes a straight-forward approach toward producing concise, yet descriptive, MIB modules. This memo defines a format for producing MIB modules. [STANDARDS-TRACK] STD0016 STANDARD STANDARD RFC1213 Management Information Base for Network Management of TCP/IP-based internets:MIB-II K. McCloghrie M.T. Rose March 01 1991 ASCII 146080 70 MIB-II This memo defines the second version of the Management Information Base (MIB-II) for use with network management protocols in TCP/IP-based internets. [STANDARDS-TRACK] RFC1158 RFC2011 RFC2012 RFC2013 STD0017 STANDARD STANDARD RFC1214 OSI internet management: Management Information Base L. LaBarre April 01 1991 ASCII 172564 83 OIM-MIB-II This RFC documents a MIB for use with CMIP, either over pure OSI stacks or with the CMIP over TCP specification. It redefines objects comprised by the second revision of the Management Information Base for Network Management of TCP/IP-based internets: MIB-II so as to conform to the OSI structure of management information. [STANDARDS-TRACK] HISTORIC HISTORIC RFC1215 Convention for defining traps for use with the SNMP M.T. Rose March 01 1991 ASCII 19336 9 SNMP-TRAPS This memo suggests a straight-forward approach towards defining traps used with the SNMP. This memo provides information for the Internet community. It does not specify any standard. INFORMATIONAL INFORMATIONAL RFC1216 Gigabit network economics and paradigm shifts P. Richard P. Kynikos April 01 1991 ASCII 8130 4 This memo proposes a new standard paradigm for the Internet Activities Board (IAB) standardization track. [STANDARDS-TRACK] INFORMATIONAL INFORMATIONAL RFC1217 Memo from the Consortium for Slow Commotion Research (CSCR) V.G. Cerf April 01 1991 ASCII 11079 5 This RFC is in response to RFC 1216, "Gigabit Network Economics and Paradigm Shifts". This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1218 Naming scheme for c=US North American Directory Forum April 01 1991 ASCII 42698 23 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. RFC1255 RFC1417 INFORMATIONAL INFORMATIONAL RFC1219 On the assignment of subnet numbers P.F. Tsuchiya April 01 1991 ASCII 30609 13 SUBNETASGN This memo suggests a new procedure for assigning subnet numbers. Use of this assignment technique within a network would be a purely local matter, and would not effect other networks. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1220 Point-to-Point Protocol extensions for bridging F. Baker April 01 1991 ASCII 38165 18 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] RFC1638 PROPOSED STANDARD PROPOSED STANDARD RFC1221 Host Access Protocol (HAP) specification: Version 2 W. Edmond April 01 1991 ASCII 152740 68 HAP2 This memo describes the Host Access Protocol implemented in the Terrestrial Wideband Network (TWBNET). This memo provides information for the Internet community. It does not specify an Internet standard. RFC0907 INFORMATIONAL INFORMATIONAL RFC1222 Advancing the NSFNET routing architecture H.W. Braun Y. Rekhter May 01 1991 ASCII 15067 6 This RFC suggests improvements in the NSFNET routing architecture to accommodate a more flexible interface to the Backbone clients. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1223 OSI CLNS and LLC1 protocols on Network Systems HYPERchannel J.M. Halpern May 01 1991 ASCII 29601 12 OSI-HYPER The intent of this document is to provide a complete discussion of the protocols and techniques used to transmit OSI CLNS and LLC1 datagrams (and any associated higher level protocols) on Network Systems Corporation's HYPERchannel equipment.This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1224 Techniques for managing asynchronously generated alerts L. Steinberg May 01 1991 ASCII 54303 22 ALERTS This memo defines common mechanisms for managing asynchronously produced alerts in a manner consistent with current network management protocols. This memo specifies an Experimental Protocol for the Internet community. It does not specify an Internet standard. EXPERIMENTAL EXPERIMENTAL RFC1225 Post Office Protocol: Version 3 M.T. Rose May 01 1991 ASCII 37340 16 This memo suggests a simple method for workstations to dynamically access mail from a mailbox server. [STANDARDS-TRACK] RFC1081 RFC1460 DRAFT STANDARD DRAFT STANDARD RFC1226 Internet protocol encapsulation of AX.25 frames B. Kantor May 01 1991 ASCII 2573 2 IP-AX.25 This memo describes a method for the encapsulation of AX.25 (the Amateur Packet-Radio Link-Layer Protocol) frames within IP packets. This technique is an Experimental Protocol for the Internet community. It does not specify an Internet standard. EXPERIMENTAL EXPERIMENTAL RFC1227 SNMP MUX protocol and MIB M.T. Rose May 01 1991 ASCII 25868 13 SNMP-MUX This memo suggests a mechanism by which a user process may associate itself with the local SNMP agent on a host, in order to implement portions of the MIB. This mechanism would be local to the host.This is an Experimental Protocol for the Internet community. It does not specify an Internet standard. HISTORIC HISTORIC RFC1228 SNMP-DPI: Simple Network Management Protocol Distributed Program Interface G. Carpenter B. Wijnen May 01 1991 ASCII 96972 50 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. RFC1592 EXPERIMENTAL EXPERIMENTAL RFC1229 Extensions to the generic-interface MIB K. McCloghrie May 01 1991 ASCII 36022 16 This RFC contains definitions of managed objects used as experimental extensions to the generic interfaces structure of MIB-II. [STANDARDS- TRACK] RFC1573 RFC1239 PROPOSED STANDARD PROPOSED STANDARD RFC1230 IEEE 802.4 Token Bus MIB K. McCloghrie R. Fox May 01 1991 ASCII 53100 23 802.4-MIP This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, this memo defines managed objects used for managing subnetworks which use the IEEE 802.4 Token Bus technology described in 802.4 Token-Passing Bus Access Method and Physical Layer Specifications, IEEE Standard 802.4. [STANDARDS-TRACK] RFC1239 HISTORIC HISTORIC RFC1231 IEEE 802.5 Token Ring MIB K. McCloghrie R. Fox E. Decker May 01 1991 ASCII 53542 23 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] RFC1743 RFC1748 RFC1239 PROPOSED STANDARD PROPOSED STANDARD RFC1232 Definitions of managed objects for the DS1 Interface type F. Baker C.P. Kolb May 01 1991 ASCII 60757 28 RFC1406 RFC1239 PROPOSED STANDARD PROPOSED STANDARD RFC1233 Definitions of managed objects for the DS3 Interface type T.A. Cox K. Tesink May 01 1991 ASCII 49559 23 This memo defines objects for managing DS3 Interface objects for use with the SNMP protocol. [STANDARDS-TRACK] RFC1407 RFC1239 PROPOSED STANDARD PROPOSED STANDARD RFC1234 Tunneling IPX traffic through IP networks D. Provan June 01 1991 ASCII 12333 6 IPX-IP This memo describes a method of encapsulating IPX datagrams within UDP packets so that IPX traffic can travel across an IP internet. [STANDARDS-TRACK] This memo defines objects for managing DS1 Interface objects for use with the SNMP protocol. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1235 Coherent File Distribution Protocol J. Ioannidis G. Maguire June 01 1991 ASCII 29345 12 CFDP This memo describes the Coherent File Distribution Protocol (CFDP). This is an Experimental Protocol for the Internet community. It does not specify an Internet standard. EXPERIMENTAL EXPERIMENTAL RFC1236 IP to X.121 address mapping for DDN L. Morales P. Hasse June 01 1991 ASCII 12626 7 IP-X.121 This memo defines a standard way of converting IP addresses to CCITT X.121 addresses and is the recommended standard for use on the Internet, specifically for the Defense Data Network (DDN). This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1237 Guidelines for OSI NSAP Allocation in the Internet R. Colella E. Gardner R. Callon July 01 1991 ASCII 116989 48 PS 160478 PDF 171423 This paper provides guidelines for allocating NSAPs in the Internet.[STANDARDS-TRACK] RFC1629 PROPOSED STANDARD PROPOSED STANDARD RFC1238 CLNS MIB for use with Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) G. Satz June 01 1991 ASCII 65159 32 CLNS-MIB This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. This is an Experimental Protocol for the Internet community. It does not specify an Internet standard. RFC1162 EXPERIMENTAL EXPERIMENTAL RFC1239 Reassignment of experimental MIBs to standard MIBs J.K. Reynolds June 01 1991 ASCII 3656 2 STD-MIBs This memo specifically updates RFC 1229, RFC 1230, RFC 1231, RFC 1232 and RFC 1233 with new codes. [STANDARDS-TRACK] RFC1229 RFC1230 RFC1231 RFC1232 RFC1233 PROPOSED STANDARD PROPOSED STANDARD RFC1240 OSI connectionless transport services on top of UDP: Version 1 C. Shue W. Haggerty K. Dobbins June 01 1991 ASCII 18140 8 OSI-UDP This document describes a protocol for running OSI Connectionless service on UDP. [STANDARDS-TRACK] HISTORIC PROPOSED STANDARD RFC1241 Scheme for an internet encapsulation protocol: Version 1 R.A. Woodburn D.L. Mills July 01 1991 ASCII 42468 17 PS 128921 PDF 44593 IN-ENCAP This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. EXPERIMENTAL EXPERIMENTAL RFC1242 Benchmarking terminology for network interconnection devices S. Bradner July 01 1991 ASCII 22817 12 This memo discusses and defines a number of terms that are used in describing performance benchmarking tests and the results of such tests. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1243 AppleTalk Management Information Base S. Waldbusser July 01 1991 ASCII 61985 29 This memo defines objects for managing AppleTalk objects for use with the SNMP protocol. [STANDARDS-TRACK] RFC1742 PROPOSED STANDARD PROPOSED STANDARD RFC1244 Site Security Handbook J.P. Holbrook J.K. Reynolds July 01 1991 ASCII 259129 101 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] RFC2196 INFORMATIONAL INFORMATIONAL RFC1245 OSPF Protocol Analysis J. Moy July 01 1991 ASCII 26160 12 PS 33546 PDF 31723 OSPF SPF routing TOS LSA flooding This report attempts to summarize the key features of OSPF V2. It also attempts to analyze how the protocol will perform and scale in the Internet. This memo provides information for the Internet community. It does not specify any Internet standard. RFC1247 RFC1246 INFORMATIONAL INFORMATIONAL RFC1246 Experience with the OSPF Protocol J. Moy July 01 1991 ASCII 70441 31 PS 141924 PDF 84633 OSPF SPF routing MIB experience testing This report documents experience with OSPF V2. This includes reports on interoperability testing, field experience, simulations and the current state of OSPF implementations. This memo provides information for the Internet community. It does not specify any Internet standard. RFC1247 RFC1245 INFORMATIONAL INFORMATIONAL RFC1247 OSPF Version 2 J. Moy July 01 1991 ASCII 433332 189 PS 989724 PDF 490300 equal-cost multipath link state LSA This memo documents version 2 of the OSPF protocol. OSPF is a link- state based routing protocol. [STANDARDS-TRACK] RFC1131 RFC1583 RFC1349 RFC1246 RFC1245 DRAFT STANDARD DRAFT STANDARD RFC1248 OSPF Version 2 Management Information Base F. Baker R. Coltun July 01 1991 ASCII 74347 42 OSPF SPF MIB routing network management 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] RFC1252 RFC1349 PROPOSED STANDARD PROPOSED STANDARD RFC1249 DIXIE Protocol Specification T. Howes M. Smith B. Beecher August 01 1991 ASCII 20028 10 DIXIE DIXIE protocol directory services X.500 DAP This RFC defines a mechanism by which TCP/UDP based clients can access OSI Directory Service without the overhead of the ISO transport and presentation protocols required to implement full-blown DAP. This memo provides information for the Internet community. It does not specify any standard. RFC1202 INFORMATIONAL INFORMATIONAL RFC1250 IAB Official Protocol Standards J. Postel August 01 1991 ASCII 62555 28 standards protocol IAB 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. RFC1200 RFC2200 RFC1280 HISTORIC STANDARD RFC1251 Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members G. Malkin August 01 1991 ASCII 70383 26 IESG IRSG IAB 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] RFC1336 INFORMATIONAL INFORMATIONAL RFC1252 OSPF Version 2 Management Information Base F. Baker R. Coltun August 01 1991 ASCII 74471 42 OSPF SPF MIB routing network management 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] RFC1248 RFC1253 RFC1247 RFC1245 PROPOSED STANDARD PROPOSED STANDARD RFC1253 OSPF Version 2 Management Information Base F. Baker R. Coltun August 01 1991 ASCII 74453 42 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] RFC1252 RFC1850 RFC1247 RFC1245 RFC1246 PROPOSED STANDARD PROPOSED STANDARD RFC1254 Gateway Congestion Control Survey A. Mankin K. Ramakrishnan August 01 1991 ASCII 67609 25 gateway congestion SQ source quench fiar queueing random drop The purpose of this paper is to present a review of the congestion control approaches, as a way of encouraging new discussion and experimentation. Included in the survey are Source Quench, Random Drop, Congestion Indication (DEC Bit), and Fair Queueing. INFORMATIONAL INFORMATIONAL RFC1255 A Naming Scheme for c=US The North American Directory Forum September 01 1991 ASCII 51103 25 naming NADF X.500 directory services c=us This memo documents the NADF's agreement as to how entries are named in the public portions of the North American Directory. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1218 RFC1417 INFORMATIONAL INFORMATIONAL RFC1256 ICMP Router Discovery Messages S. Deering Editor September 01 1991 ASCII 43059 19 ICMP-ROUT ICMP router gateway discovery standard protocol This document specifies an extension of the Internet Control Message Protocol (ICMP) to enable hosts attached to multicast or broadcast networks to discover the IP addresses of their neighboring routers. [STANDARDS-TRACK] RFC0792 PROPOSED STANDARD PROPOSED STANDARD RFC1257 Isochronous applications do not require jitter-controlled networks C. Partridge September 01 1991 ASCII 11075 5 This memo argues that jitter control is not required for networks to support isochronous applications. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1258 BSD Rlogin B. Kantor September 01 1991 ASCII 10763 5 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. INFORMATIONAL INFORMATIONAL RFC1259 Building the open road: The NREN as test-bed for the national public network M. Kapor September 01 1991 ASCII 61654 23 NREN test-bed network policy This memo discusses the background and importance of NREN. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1260 RFC1261 Transition of Nic Services S. Williamson L. Nobile September 01 1991 ASCII 4244 3 NIC transition This memo outlines the transition of NIC Services. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1262 Guidelines for Internet Measurement Activities V.G. Cerf October 01 1991 ASCII 6381 3 This RFC represents IAB guidance for researchers considering measurement experiments on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1263 TCP Extensions Considered Harmful S. O'Malley L.L. Peterson October 01 1991 ASCII 54078 19 This RFC comments on recent proposals to extend TCP. It argues that the backward compatible extensions proposed in RFC's 1072 and 1185 should not be pursued, and proposes an alternative way to evolve the Internet protocol suite. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1264 Internet Engineering Task Force Internet Routing Protocol Standardization Criteria R.M. Hinden October 01 1991 ASCII 17016 8 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. INFORMATIONAL INFORMATIONAL RFC1265 BGP Protocol Analysis Y. Rekhter October 01 1991 ASCII 20728 8 This report summarizes the key feature of BGP, and analyzes the protocol with respect to scaling and performance. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1266 Experience with the BGP Protocol Y. Rekhter October 01 1991 ASCII 21938 9 The purpose of this memo is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by Border Gateway Protocol (BGP). This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1267 Border Gateway Protocol 3 (BGP-3) K. Lougheed Y. Rekhter October 01 1991 ASCII 80724 35 BGP3 This memo, together with its companion document, "Application of the Border Gateway Protocol in the Internet", define an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK] RFC1163 HISTORIC HISTORIC RFC1268 Application of the Border Gateway Protocol in the Internet Y. Rekhter P. Gross October 01 1991 ASCII 31102 13 BGP3 This document describes the usage of the BGP in the Internet. [STANDARDS-TRACK] RFC1164 RFC1655 HISTORIC HISTORIC RFC1269 Definitions of Managed Objects for the Border Gateway Protocol: Version 3 S. Willis J.W. Burruss October 01 1991 ASCII 25717 13 BGP-MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Border Gateway Protocol. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1270 SNMP Communications Services F. Kastenholz October 01 1991 ASCII 26167 11 This document discusses various issues to be considered when determining the underlying communications services to be used by an SNMP implementation. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1271 Remote Network Monitoring Management Information Base S. Waldbusser November 01 1991 ASCII 184111 81 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] RFC1757 RFC1513 PROPOSED STANDARD PROPOSED STANDARD RFC1272 Internet Accounting: Background C. Mills D. Hirsh G.R. Ruth November 01 1991 ASCII 46562 19 This document provides background information for the "Internet Accounting Architecture". This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1273 Measurement Study of Changes in Service-Level Reachability in the Global TCP/IP Internet: Goals, Experimental Design, Implementation, and Policy Considerations M.F. Schwartz November 01 1991 ASCII 19949 8 This memo describes plans to carry out a longitudinal measurement study of changes in service-level reachability in the global TCP/IP Internet. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1274 The COSINE and Internet X.500 Schema P. Barker S. Kille November 1991 ASCII 92827 60 Naming This document suggests an X.500 Directory Schema, or Naming Architecture, for use in the COSINE and Internet X.500 pilots. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1275 Replication Requirements to provide an Internet Directory using X.500 S.E. Hardcastle-Kille November 1991 ASCII 4616 3 PS 83736 PDF 62498 This RFC considers certain deficiencies of the 1988 X.500 standard, which need to be addressed before an effective open Internet Directory can be established using these protocols and services [CCI88]. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1276 Replication and Distributed Operations extensions to provide an Internet Directory using X.500 S.E. Hardcastle-Kille November 1991 ASCII 33731 17 PS 217170 Some requirements on extensions to X.500 are described in the RFC[HK91b], in order to build an Internet Directory using X.500(1988). This document specifies a set of solutions to the problems raised. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1277 Encoding Network Addresses to Support Operation over Non-OSI Lower Layers S.E. Hardcastle-Kille November 1991 ASCII 22254 12 PS 176169 address ISO OSI This document defines a new network address format, and rules for using some existing network address formats. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1278 A string encoding of Presentation Address S.E. Hardcastle-Kille November 1991 ASCII 10256 7 PS 128696 OSI ASN.1 There are a number of environments where a simple string encoding of Presentation Address is desirable. This specification defines such a representation. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1279 X.500 and Domains S.E. Hardcastle-Kille November 1991 ASCII 26669 15 PS 170029 Domain Name naming This RFC considers X.500 in relation to Internet and UK Domains. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. EXPERIMENTAL EXPERIMENTAL RFC1280 IAB Official Protocol Standards J. Postel March 1992 ASCII 70458 32 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. RFC1250 RFC1360 HISTORIC STANDARD RFC1281 Guidelines for the Secure Operation of the Internet R. Pethia S. Crocker B. Fraser November 1991 ASCII 22618 10 security privacy protection guideline The purpose of this document is to provide a set of guidelines to aid in the secure operation of the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1282 BSD Rlogin B. Kantor December 1991 ASCII 10704 5 BSD Login Unix remote-login remote-logon 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. INFORMATIONAL INFORMATIONAL RFC1283 SNMP over OSI M. Rose December 1991 ASCII 16857 8 ISO Management MIB 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. RFC1418 EXPERIMENTAL EXPERIMENTAL RFC1284 Definitions of Managed Objects for the Ethernet-like Interface Types J. Cook Editor December 1991 ASCII 43225 21 SNMP MIB Management 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] RFC1398 PROPOSED STANDARD PROPOSED STANDARD RFC1285 FDDI Management Information Base J. Case January 1992 ASCII 99747 46 FDDI-MIB standard standards MIB SNMP This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing devices which implement the FDDI. [STANDARDS-TRACK] RFC1512 PROPOSED STANDARD PROPOSED STANDARD RFC1286 Definitions of Managed Objects for Bridges E. Decker P. Langille A. Rijsinghani K. McCloghrie December 1991 ASCII 79104 40 SNMP MIB standard standards 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] RFC1493 RFC1525 PROPOSED STANDARD PROPOSED STANDARD RFC1287 Towards the Future Internet Architecture D. Clark L. Chapin V. Cerf R. Braden R. Hobby December 1991 ASCII 59812 29 This informational RFC discusses important directions for possible future evolution of the Internet architecture, and suggests steps towards the desired goals. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1288 The Finger User Information Protocol D. Zimmerman December 1991 ASCII 25161 12 FINGER This memo describes the Finger user information protocol.This is a simple protocol which provides an interface to a remote user information program. [STANDARDS-TRACK] RFC1196 RFC1194 RFC0742 DRAFT STANDARD DRAFT STANDARD RFC1289 DECnet Phase IV MIB Extensions J. Saperia December 1991 ASCII 122272 64 SNMP Management protocol standard standards This memo is an extension to the SNMP MIB. This memo defines a set of DECnet Phase IV extensions that have been created for the Internet MIB. [STANDARDS-TRACK] RFC1559 PROPOSED STANDARD PROPOSED STANDARD RFC1290 There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places J. Martin December 1991 ASCII 46997 27 SIGUCCS User Services Help Internet This paper will present some of the "gold nuggets" of information and file repositories on the network that could be of use to end users. This RFC provides information for the Internet community. It does not specify an Internet standard. RFC1402 INFORMATIONAL INFORMATIONAL RFC1291 Mid-Level Networks Potential Technical Services V. Aggarwal December 1991 ASCII 24314 10 PS 218918 statistics connectivity management This document proposes a set of technical services that each Internet mid-level network can offer within the mid-level network itself and and to its peer networks. This RFC provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1292 A Catalog of Available X.500 Implementations R. Lang R. Wright January 1992 ASCII 129468 103 The goal of this document is to provide information regarding the availability and capability of implementations of X.500. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1632 INFORMATIONAL INFORMATIONAL RFC1293 Inverse Address Resolution Protocol T. Bradley C. Brown January 1992 ASCII 11368 6 standard standards ARP DLCI This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK] RFC2390 PROPOSED STANDARD PROPOSED STANDARD RFC1294 Multiprotocol Interconnect over Frame Relay T. Bradley C. Brown A. Malis January 1992 ASCII 54992 28 standard standards 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] RFC1490 RFC2427 PROPOSED STANDARD PROPOSED STANDARD RFC1295 User Bill of Rights for entries and listings in the Public Directory The North American Directory Forum January 1992 ASCII 3502 2 NADF-265 NADF X.500 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) objects. This document is a companion document with Definitions of Managed Objects for the DS1/E1 and DS3/E3 Interface Types, RFC1406 and RFC1407. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1417 INFORMATIONAL INFORMATIONAL RFC1296 Internet Growth (1981-1991) M. Lottor January 1992 ASCII 20103 9 statistics ZONE This document illustrates the growth of the Internet by examination of entries in the Domain Name System (DNS) and pre-DNS host tables. This memo provides information for the Internet community. It does not specify an Internet standard. This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Frame Relay Service. [STANDARDS-TRACK] INFORMATIONAL INFORMATIONAL RFC1297 NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist ("NOC TT REQUIREMENTS") D. Johnson January 1992 ASCII 32964 12 problems tracking operations NOC This document explores competing uses, architectures, and desirable features of integrated internal trouble ticket systems for Network and other Operations Centers. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1298 SNMP over IPX R. Wormley S. Bostock February 1992 ASCII 7878 5 This memo defines a convention for encapsulating Simple Network Management Protocol (SNMP) packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1420 INFORMATIONAL INFORMATIONAL RFC1299 Summary of 1200-1299 M. Kennedy January 1997 ASCII 36594 20 Index INFORMATIONAL INFORMATIONAL RFC1300 Remembrances of Things Past S. Greenfield February 1992 ASCII 4963 4 poem Poem. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1301 Multicast Transport Protocol S. Armstrong A. Freier K. Marzullo February 1992 ASCII 91976 38 MTP MTP reliable transport multicast broadcast collaboration networking This memo describes a protocol for reliable transport that utilizes the multicast capability of applicable lower layer networking architectures. The transport definition permits an arbitrary number of transport providers to perform realtime collaborations without requiring networking clients (aka, applications) to possess detailed knowledge of the population or geographical dispersion of the participating members. It is not network architectural specific, but does implicitly require some form of multicasting (or broadcasting) at the data link level, as well as some means of communicating that capability up through the layers to the transport. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1302 Building a Network Information Services Infrastructure D. Sitzler P. Smith A. Marine February 1992 ASCII 29135 13 NISI NIC User Services This FYI RFC document is intended for existing Internet Network Information Center (NIC) personnel, people interested in establishing a new NIC, Internet Network Operations Centers (NOCs), and funding agencies interested in contributing to user support facilities. This memo provides information for the Internet community. It does not specify an Internet standard. FYI0012 INFORMATIONAL INFORMATIONAL RFC1303 A Convention for Describing SNMP-based Agents K. McCloghrie M. Rose February 1992 ASCII 22915 12 SNMP MIB Network Management This memo suggests a straight-forward approach towards describing SNMP- based agents. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1155 RFC1212 RFC1213 RFC1157 INFORMATIONAL INFORMATIONAL RFC1304 Definitions of Managed Objects for the SIP Interface Type T. Cox K. Tesink Editors February 1992 ASCII 52491 25 Standard MIB Network Management SMDS This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing SIP (SMDS Interface Protocol) objects. [STANDARDS-TRACK] RFC1694 PROPOSED STANDARD PROPOSED STANDARD RFC1305 Network Time Protocol (Version 3) Specification, Implementation D. Mills March 1992 ASCII 307085 109 PDF 442493 NTPV3 NTP This document describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. [STANDARDS-TRACK] There is a "compressed" "tar" file of three postscript files for this RFC. RFC0958 RFC1059 RFC1119 DRAFT STANDARD DRAFT STANDARD RFC1306 Experiences Supporting By-Request Circuit-Switched T3 Networks A. Nicholson J. Young March 1992 ASCII 25788 10 WAN Wide Area Net FDDI This memo describes the experiences of a project team at Cray Research, Inc., in implementing support for circuit-switched T3 services. While the issues discussed may not be directly relevant to the research problems of the Internet, they may be interesting to a number of researchers and implementers. This RFC provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1307 Dynamically Switched Link Control Protocol J. Young A. Nicholson March 1992 ASCII 24145 13 DSLCP Experimental Protocol T3 FDDI This memo describes an experimental protocol developed by a project team at Cray Research, Inc., in implementing support for circuit-switched T3 services. The protocol is used for the control of network connections external to a host, but known to the host. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1308 Executive Introduction to Directory Services Using the X.500 Protocol C. Weider J. Reynolds March 1992 ASCII 9392 4 This document is an Executive Introduction to Directory Services using the X.500 protocol. It briefly discusses the deficiencies in currently deployed Internet Directory Services, and then illustrates the solutions provided by X.500. This memo provides information for the Internet community. It does not specify an Internet standard. FYI0013 INFORMATIONAL INFORMATIONAL RFC1309 Technical Overview of Directory Services Using the X.500 Protocol C. Weider J. Reynolds S. Heker March 1992 ASCII 35694 16 This document is an overview of the X.500 standard for people not familiar with the technology. It compares and contrasts Directory Services based on X.500 with several of the other Directory services currently in use in the Internet. This paper also describes the status of the standard and provides references for further information on X.500 implementations and technical information. This memo provides information for the Internet community. It does not specify an Internet standard. FYI0014 INFORMATIONAL INFORMATIONAL RFC1310 The Internet Standards Process L. Chapin March 1992 ASCII 54738 23 This memo documents the process currently used for the standardization of Internet protocols and procedures. [STANDARDS-TRACK] RFC1602 INFORMATIONAL INFORMATIONAL RFC1311 Introduction to the STD Notes J. Postel March 1992 ASCII 11308 5 new IAB The STDs are a subseries of notes within the RFC series that are the Internet standards. The intent is to identify clearly for the Internet community those RFCs which document Internet standards. [STANDARDS- TRACK] INFORMATIONAL INFORMATIONAL RFC1312 Message Send Protocol 2 R. Nelson G. Arnold April 1992 ASCII 18037 8 MSP2 MSP talk The Message Send Protocol is used to send a short message to a given user on a given terminal on a given host. This memo defines an Experimental Protocol for the Internet community. RFC1159 EXPERIMENTAL EXPERIMENTAL RFC1313 Today's Programming for KRFC AM 1313 Internet Talk Radio C. Partridge April 01 1992 ASCII 5444 3 Hi and welcome to KRFC Internet Talk Radio, your place on the AM dial for lively talk and just-breaking news on internetworking. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1314 A File Format for the Exchange of Images in the Internet A. Katz D. Cohen April 1992 ASCII 54072 23 NETFAX netfax TIFF facsimile This document defines a standard file format for the exchange of fax- like black and white images within the Internet. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1315 Management Information Base for Frame Relay DTEs C. Brown F. Baker C. Carvalho April 1992 ASCII 33825 19 MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Frame Relay. [STANDARDS- TRACK] RFC2115 PROPOSED STANDARD PROPOSED STANDARD RFC1316 Definitions of Managed Objects for Character Stream Devices B. Stewart April 1992 ASCII 35143 17 MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for the management of character stream devices. [STANDARDS-TRACK] RFC1658 PROPOSED STANDARD PROPOSED STANDARD RFC1317 Definitions of Managed Objects for RS-232-like Hardware Devices B. Stewart April 1992 ASCII 30442 17 MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for the management of RS-232-like devices. [STANDARDS-TRACK] RFC1659 PROPOSED STANDARD PROPOSED STANDARD RFC1318 Definitions of Managed Objects for Parallel-printer-like Hardware Devices B. Stewart April 1992 ASCII 19570 11 MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for the management of parallel-printer- like devices. [STANDARDS-TRACK] RFC1660 PROPOSED STANDARD PROPOSED STANDARD RFC1319 The MD2 Message-Digest Algorithm B. Kaliski April 1992 ASCII 25661 17 security encryption signature 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. INFORMATIONAL INFORMATIONAL RFC1320 The MD4 Message-Digest Algorithm R. Rivest April 1992 ASCII 32407 20 MD4 security encryption signature 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. RFC1186 INFORMATIONAL INFORMATIONAL RFC1321 The MD5 Message-Digest Algorithm R. Rivest April 1992 ASCII 35222 21 security signature eneryption This document describes the MD5 message-digest algorithm. The algorithm takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1322 A Unified Approach to Inter-Domain Routing D. Estrin Y. Rekhter S. Hotz May 1992 ASCII 96934 38 path vector routing source demand routing This memo is an informational RFC which outlines one potential approach for inter-domain routing in future global internets. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1323 TCP Extensions for High Performance V. Jacobson R. Braden D. Borman May 1992 ASCII 84558 37 TCP-EXT options PAWS window scale window This memo presents a set of TCP extensions to improve performance over large bandwidth*delay product paths and to provide reliable operation over very high-speed paths. It defines new TCP options for scaled windows and timestamps, which are designed to provide compatible interworking with TCP's that do not implement the extensions. [STANDARDS-TRACK] RFC1072 RFC1185 PROPOSED STANDARD PROPOSED STANDARD RFC1324 A Discussion on Computer Network Conferencing D. Reed May 1992 ASCII 24988 11 talk real time chat This memo is intended to make more people aware of the present developments in the Computer Conferencing field as well as put forward ideas on what should be done to formalize this work so that there is a common standard for programmers and others who are involved in this field to work with. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1325 FYI on Questions and Answers Answers to Commonly asked "New Internet User" Questions G. Malkin A. Marine May 1992 ASCII 91884 42 documentation help information This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A), produced by the User Services Working Group of the Internet Engineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1206 RFC1594 INFORMATIONAL INFORMATIONAL RFC1326 Mutual Encapsulation Considered Dangerous P. Tsuchiya May 1992 ASCII 11277 5 protocol layering wrapping This memo describes a packet explosion problem that can occur with mutual encapsulation of protocols (A encapsulates B and B encapsulates A). This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1327 Mapping between X.400(1988) / ISO 10021 and RFC 822 S. Hardcastle-Kille May 1992 ASCII 228598 113 Electronic-mail,Message handling systems This document specifies a mapping between two protocols. This specification should be used when this mapping is performed on the DARPA Internet or in the UK Academic Community. This specification may be modified in the light of implementation experience, but no substantial changes are expected. [STANDARDS-TRACK] RFC0987 RFC1026 RFC1138 RFC1148 RFC2156 RFC0822 RFC1495 PROPOSED STANDARD PROPOSED STANDARD RFC1328 X.400 1988 to 1984 downgrading S. Hardcastle-Kille May 1992 ASCII 10006 5 Electronic-mail message handling systems,mail This document considers issues of downgrading from X.400(1988) to X.400(1984) [MHS88a, MHS84]. Annexe B of X.419 specifies some downgrading rules [MHS88b], but these are not sufficient for provision of service in an environment containing both 1984 and 1988 components. This document defines a number of extensions to this annexe. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1329 Thoughts on Address Resolution for Dual MAC FDDI Networks P. Kuehn May 1992 ASCII 58150 28 In this document an idea is submitted how IP and ARP can be used on inhomogeneous FDDI networks (FDDI networks with single MAC and dual MAC stations) by introducing a new protocol layer in the protocol suite of the dual MAC stations. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1330 Recommendations for the Phase I Deployment of OSI Directory Services (X.500) and OSI Message Handling Services (X.400) within the ESNET Community ESCC X.500/X.400 Task Force ESnet Site Coordinating Comittee (ESCC) Energy Sciences Network (ESnet) May 1992 ASCII 192925 87 This RFC is a near verbatim copy of the whitepaper produced by the ESnet Site Coordinating Committee's X.500/X.400 Task Force. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1331 The Point-to-Point Protocol (PPP) for the Transmission of Multi-protocol Datagrams over Point-to-Point Links W. Simpson May 1992 ASCII 129892 69 serial line IP over serial dial-up This document defines the PPP encapsulation scheme, together with the PPP Link Control Protocol (LCP), an extensible option negotiation protocol which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. [STANDARDS- TRACK] RFC1171 RFC1172 RFC1548 PROPOSED STANDARD PROPOSED STANDARD RFC1332 The PPP Internet Protocol Control Protocol (IPCP) G. McGregor May 1992 ASCII 17613 14 PPP-IPCP serial line IP over serial dial-up The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. [STANDARDS-TRACK] RFC1172 RFC3241 PROPOSED STANDARD PROPOSED STANDARD RFC1333 PPP Link Quality Monitoring W. Simpson May 1992 ASCII 29965 17 serial line IP over serial dial-up The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, which allows negotiation of a Quality Protocol for continuous monitoring of the viability of the link. [STANDARDS-TRACK] RFC1989 PROPOSED STANDARD PROPOSED STANDARD RFC1334 PPP Authentication Protocols B. Lloyd W. Simpson October 1992 ASCII 33248 16 point serial line dial-up This document defines two protocols for Authentication: the Password Authentication Protocol and the Challenge-Handshake Authentication Protocol. [STANDARDS-TRACK] RFC1994 PROPOSED STANDARD PROPOSED STANDARD RFC1335 A Two-Tier Address Structure for the Internet: A Solution to the Problem of Address Space Exhaustion Z. Wang J. Crowcroft May 1992 ASCII 15418 7 internet protocol IP This RFC presents a solution to problem of address space exhaustion in the Internet. It proposes a two-tier address structure for the Internet. This is an "idea" paper and discussion is strongly encouraged. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1336 Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members G. Malkin May 1992 ASCII 92119 33 Almquist Braden Braun Callon Cerf Chiappa Chapin Clark Crocker Davin Estrin Hobby Huitema Huizer Kent Lauck Leiner Lynch Piscitello Postel Reynolds Schwartz Stockman Vaudreuil This FYI RFC contains biographical information about members of the Internet Activities Board (IAB), the Internet Engineering Steering Group (IESG) of the Internet Engineering Task Force (IETF), and the the Internet Research Steering Group (IRSG) of the Internet Research Task Force (IRTF). This memo provides information for the Internet community. It does not specify any standard. RFC1251 FYI0009 INFORMATIONAL INFORMATIONAL RFC1337 TIME-WAIT Assassination Hazards in TCP R. Braden May 1992 ASCII 22887 11 TCP protocol protocol state graceful close reset This note describes some theoretically-possible failure modes for TCP connections and discusses possible remedies. In particular, one very simple fix is identified. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1338 Supernetting: an Address Assignment and Aggregation Strategy V. Fuller T. Li J. Yu K. Varadhan June 1992 ASCII 47975 20 internet address routing This memo discusses strategies for address assignment of the existing IP address space with a view to conserve the address space and stem the explosive growth of routing tables in default-route-free routers run by transit routing domain providers. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1519 INFORMATIONAL INFORMATIONAL RFC1339 Remote Mail Checking Protocol S. Dorner P. Resnick June 1992 ASCII 13115 6 RMCP email remote mail This RFC defines a protocol to provide a mail checking service to be used between a client and server pair. Typically, a small program on a client workstation would use the protocol to query a server in order to find out whether new mail has arrived for a specified user. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1340 Assigned Numbers J. Reynolds J. Postel July 1992 ASCII 232974 139 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. RFC1060 RFC1700 HISTORIC STANDARD RFC1341 MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies N. Borenstein N. Freed June 1992 ASCII 211117 80 PS 347082 PDF 192244 EMail Multimedia 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] RFC1521 PROPOSED STANDARD PROPOSED STANDARD RFC1342 Representation of Non-ASCII Text in Internet Message Headers K. Moore June 1992 ASCII 15845 7 EMail Character Sets This memo describes an extension to the message format defined in [1] (known to the IETF Mail Extensions Working Group as "RFC 1341"), to allow the representation of character sets other than ASCII in RFC 822 message headers. [STANDARDS-TRACK] RFC1522 PROPOSED STANDARD PROPOSED STANDARD RFC1343 A User Agent Configuration Mechanism for Multimedia Mail Format Information N. Borenstein June 1992 ASCII 29295 10 PS 59978 PDF 28495 EMail Multimedia This memo suggests a file format to be used to inform multiple mail reading user agent programs about the locally-installed facilities for handling mail in various formats. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1344 Implications of MIME for Internet Mail Gateways N. Borenstein June 1992 ASCII 25872 9 PS 51812 PDF 24430 EMail Forwarding Relaying Fragmentation Multimedia While MIME was carefully designed so that it does not require any changes to Internet electronic message transport facilities, there are several ways in which message transport systems may want to take advantage of MIME. These opportunities are the subject of this memo. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1345 Character Mnemonics and Character Sets K. Simonsen June 1992 ASCII 249737 103 This memo lists a selection of characters and their presence in some coded character sets. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1346 Resource Allocation, Control, and Accounting for the Use of Network Resources P. Jones June 1992 ASCII 13084 6 The purpose of this RFC is to focus discussion on particular challenges in large service networks in general, and the International IP Internet in particular. No solution discussed in this document is intended as a standard. Rather, it is hoped that a general consensus will emerge as to the appropriate solutions, leading eventually to the adoption of standards. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1347 TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing R. Callon June 1992 ASCII 26563 8 PS 42398 PDF 22398 This paper describes a simple proposal which provides a long-term solution to Internet addressing, routing, and scaling. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1348 DNS NSAP RRs B. Manning July 1992 ASCII 6871 4 domain names CLNP resource records 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. RFC1637 RFC1034 RFC1035 EXPERIMENTAL EXPERIMENTAL RFC1349 Type of Service in the Internet Protocol Suite P. Almquist July 1992 ASCII 68949 28 TOS TOS IP This memo changes and clarifies some aspects of the semantics of the Type of Service octet in the Internet Protocol (IP) header. [STANDARDS-TRACK] RFC2474 RFC1248 RFC1247 RFC1195 RFC1123 RFC1122 RFC1060 RFC0791 PROPOSED STANDARD PROPOSED STANDARD RFC1350 The TFTP Protocol (Revision 2) K. Sollins July 1992 ASCII 24599 11 TFTP trivial file transfer booting TFTP is a very simple protocol used to transfer files. It is from this that its name comes, Trivial File Transfer Protocol or TFTP. Each nonterminal packet is acknowledged separately. This document describes the protocol and its types of packets. The document also explains the reasons behind some of the design decisions. [STANDARDS-TRACK] RFC0783 RFC1782 RFC1783 RFC1784 RFC1785 RFC2347 RFC2348 RFC2349 STD0033 STANDARD STANDARD RFC1351 SNMP Administrative Model J. Davin J. Galvin K. McCloghrie July 1992 ASCII 80721 35 SNMP-ADMIN network management authentication This memo presents an elaboration of the SNMP administrative model set forth in [1]. This model provides a unified conceptual basis for administering SNMP protocol entities to support: authenticaiton and integrity, privacy, access control, and cooperation of protocol entities. [STANDARDS-TRACK] HISTORIC PROPOSED STANDARD RFC1352 SNMP Security Protocols J. Galvin K. McCloghrie J. Davin July 1992 ASCII 95732 41 SNMP-SEC network management authentication The Simple Network Management Protocol (SNMP) specification [1] allows for the protection of network management operations by a variety of security protocols. The SNMP administrative model described in [2] provides a framework for securing SNMP network management. In the context of that framework, this memo defines protocols to support the following three security services: data integrity, data origin authentication and data confidentiality. [STANDARDS-TRACK] HISTORIC PROPOSED STANDARD RFC1353 Definitions of Managed Objects for Administration of SNMP Parties K. McCloghrie J. Davin J. Galvin July 1992 ASCII 59556 26 SNMP-PARTY-MIB network management authentication This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes a representation of the SNMP parties defined in [8] as objects defined according to the Internet Standard SMI [1]. [STANDARDS-TRACK] HISTORIC PROPOSED STANDARD RFC1354 IP Forwarding Table MIB F. Baker July 1992 ASCII 24905 12 Network Management Route Table This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing routes in the IP Internet. [STANDARDS-TRACK] RFC2096 PROPOSED STANDARD PROPOSED STANDARD RFC1355 Privacy and Accuracy Issues in Network Information Center Databases J. Curran A. Marine August 1992 ASCII 8858 4 NIC data privacy accuracy This document provides a set of guidelines for the administration and operation of public Network Information Center (NIC) databases. This memo provides information for the Internet community. It does not specify an Internet standard. FYI0015 INFORMATIONAL INFORMATIONAL RFC1356 Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode A. Malis D. Robinson R. Ullmann August 1992 ASCII 32043 14 IP-X.25 IP on X.25 This document specifies the encapsulation of IP and other network layer protocols over X.25 networks, in accordance and alignment with ISO/IEC and CCITT standards. It is a replacement for RFC 877, "A Standard for the Transmission of IP Datagrams Over Public Data Networks" [1]. [STANDARDS-TRACK] RFC0877 DRAFT STANDARD PROPOSED STANDARD RFC1357 A Format for E-mailing Bibliographic Records D. Cohen July 1992 ASCII 25021 13 library technical reports email services This memo defines a format for E-mailing bibliographic records of technical reports. It is intended to accelerate the dissemination of information about new Computer Science Technical Reports (CS-TR). This memo provides information for the Internet community. It does not specify an Internet standard. RFC1807 INFORMATIONAL INFORMATIONAL RFC1358 Charter of the Internet Architecture Board (IAB) L. Chapin August 1992 ASCII 11328 5 ISOC Internet Society IETF IRTF 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. RFC1601 INFORMATIONAL INFORMATIONAL RFC1359 Connecting to the Internet - What Connecting Institutions Should Anticipate ACM SIGUCCS August 1992 ASCII 53449 25 Internet access This FYI RFC outlines the major issues an institution should consider in the decision and implementation of a campus connection to the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. FYI0016 INFORMATIONAL INFORMATIONAL RFC1360 IAB Official Protocol Standards J. Postel September 1992 ASCII 71860 33 proposed draft experimental informational historic full RFC1280 RFC1410 HISTORIC STANDARD RFC1361 Simple Network Time Protocol (SNTP) D. Mills August 1992 ASCII 23812 10 Clocks Synchronization NTP This memorandum describes the Simple Network Time Protocol (SNTP), which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. This memorandum does not obsolete or update any RFC. This memo provides information for the Internet community. It does not specify an Internet standard. Discussion of the standardization process and the RFC document series is presented first, followed by an explanation of the terms. Sections 6.2 - 6.9 contain the lists of protocols in each stage of standardization. Finally come pointers to references and contacts for further information. [STANDARDS-TRACK] RFC1769 RFC1305 INFORMATIONAL INFORMATIONAL RFC1362 Novell IPX over Various WAN Media (IPXWAN) M. Allen September 1992 ASCII 30219 13 IPX on X.25 IPX on PPP IPX on Frame Relay This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocol Novell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1634 INFORMATIONAL INFORMATIONAL RFC1363 A Proposed Flow Specification C. Partridge September 1992 ASCII 59214 20 flow spec resource reservation stream type of service quality of service INFORMATIONAL INFORMATIONAL RFC1364 BGP OSPF Interaction K. Varadhan September 1992 ASCII 32121 14 autonomous system border router open shortest path first routing protocol domain route exchange exporting importing RFC1403 RFC1247 RFC1267 PROPOSED STANDARD PROPOSED STANDARD RFC1365 An IP Address Extension Proposal K. Siyan September 1992 ASCII 12790 6 class F addresses INFORMATIONAL INFORMATIONAL RFC1366 Guidelines for Management of IP Address Space E. Gerich October 1992 ASCII 17793 8 routing tables allocation registry IR IANA This document has been reviewed by the Federal Engineering Task Force (FEPG) on behalf of the Federal Networking Council (FNC), the co-chairs of the International Engineering Planning Group (IEPG), and the Reseaux IP Europeens (RIPE). There was general consensus by those groups to support the recommendations proposed in this document for management of the IP address space. This memo provides information for the Internet community. It does not specify an Internet standard. This RFC suggests an extension to the IP protocol to solve the shortage of IP address problem, and requests discussion and suggestions for improvements. This memo provides information for the Internet community. It does not specify an Internet standard. This memo defines the various criteria to be used when designing Autonomous System Border Routers (ASBR) that will run BGP with other ASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK] 1363 Partridge Spt 92 A Proposed Flow Specification The flow specification defined in this memo is intended for information and possible experimentation (i.e., experimental use by consenting routers and applications only). This RFC is a product of the Internet Research Task Force (IRTF). This memo provides information for the Internet community. It does not specify an Internet standard. RFC1466 INFORMATIONAL INFORMATIONAL RFC1367 Schedule for IP Address Space Management Guidelines C. Topolcic October 1992 ASCII 4780 3 routing tables allocation registry IR IANA 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. RFC1467 INFORMATIONAL INFORMATIONAL RFC1368 Definition of Managed Objects for IEEE 802.3 Repeater Devices D. McMaster K. McCloghrie October 1992 ASCII 83905 40 MIB hub management This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing IEEE 802.3 10 Mb/second baseband repeaters, sometimes referred to as "hubs". [STANDARDS-TRACK] RFC1516 PROPOSED STANDARD PROPOSED STANDARD RFC1369 Implementation Notes and Experience for the Internet Ethernet MIB F. Kastenholz October 1992 ASCII 13961 7 management This document reflects the currently known status of 11 different implementations of the MIB by 7 different vendors on 7 different Ethernet interface chips. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL PROPOSED STANDARD RFC1370 Applicability Statement for OSPF Internet Architecture Board L. Chapin October 1992 ASCII 4303 2 routing open shortest path first This Applicability Statement places a requirement on vendors claiming conformance to this standard, in order to assure that users will have the option of deploying OSPF when they need a multivendor, interoperable IGP in their environment. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1371 Choosing a Common IGP for the IP Internet P. Gross October 1992 ASCII 18168 9 routing recommendation interior gateway protocol This memo presents motivation, rationale and other surrounding background information leading to the IESG's recommendation to the IAB for a single "common IGP" for the IP portions of the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1372 Telnet Remote Flow Control Option C. Hedrick D. Borman October 1992 ASCII 11098 6 TOPT-RFC terminal access This document specifies an extended version of the Telnet Remote Flow Control Option, RFC 1080, with the addition of the RESTART-ANY and RESTART-XON suboptions. [STANDARDS-TRACK] RFC1080 PROPOSED STANDARD PROPOSED STANDARD RFC1373 Portable DUAs T. Tignor October 1992 ASCII 19931 12 directory user agents whois de dixie ud doog ISODE X.500 This document comes in two parts. The first part is for regular people who wish to set up their own DUAs (Directory User Interfaces) to access the Directory. The second part is for ISODE-maintainers wishing to provide portable DUAs to users. This part gives instructions in a similar but longer, step-by-step format. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1374 IP and ARP on HIPPI J. Renwick A. Nicholson October 1992 ASCII 100903 43 The ANSI X3T9.3 committee has drafted a proposal for the encapsulation of IEEE 802.2 LLC PDUs and, by implication, IP on HIPPI. Another X3T9.3 draft describes the operation of HIPPI physical switches. X3T9.3 chose to leave HIPPI networking issues largely outside the scope of their standards; this document discusses methods of using of ANSI standard HIPPI hardware and protocols in the context of the Internet, including the use of HIPPI switches as LANs and interoperation with other networks. This memo is intended to become an Internet Standard. [STANDARDS-TRACK] RFC2834 PROPOSED STANDARD PROPOSED STANDARD RFC1375 Suggestion for New Classes of IP Addresses P. Robinson October 1992 ASCII 16990 7 network numbers This RFC suggests a change in the method of specifying the IP address to add new classes of networks to be called F, G, H, and K, to reduce the amount of wasted address space, and to increase the available IP address number space, especially for smaller organizations or classes of connectors that do not need or do not want a full Class C IP address. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1376 The PPP DECnet Phase IV Control Protocol (DNCP) S. Senum November 1992 ASCII 12448 6 point DNA DDCMP This document defines the NCP for establishing and configuring Digital's DNA Phase IV Routing protocol (DECnet Phase IV) over PPP. This document applies only to DNA Phase IV Routing messages (both data and control), and not to other DNA Phase IV protocols (MOP, LAT, etc.). [STANDARDS- TRACK] RFC1762 PROPOSED STANDARD PROPOSED STANDARD RFC1377 The PPP OSI Network Layer Control Protocol (OSINLCP) D. Katz November 1992 ASCII 22109 10 PPP-OSINLCP point open systems interconnection This document defines the NCP for establishing and configuring OSI Network Layer Protocols. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1378 The PPP AppleTalk Control Protocol (ATCP) B. Parker November 1992 ASCII 28496 16 PPP-ATCP point This document defines the NCP for establishing and configuring the AppleTalk Protocol [3] over PPP. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1379 Extending TCP for Transactions -- Concepts R. Braden November 1992 ASCII 91353 38 transmission control protocol This memo discusses extension of TCP to provide transaction-oriented service, without altering its virtual-circuit operation. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1644 INFORMATIONAL INFORMATIONAL RFC1380 IESG Deliberations on Routing and Addressing P. Gross P. Almquist November 1992 ASCII 49415 22 ROAD This memo summarizes issues surrounding the routing and addressing scaling problems in the IP architecture, and it provides a brief background of the ROAD group and related activities in the Internet Engineering Task Force (IETF). This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1381 SNMP MIB Extension for X.25 LAPB D. Throop F. Baker November 1992 ASCII 71253 33 SNMP-LAPB management This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Link Layer of X.25, LAPB. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1382 SNMP MIB Extension for the X.25 Packet Layer D. Throop Editor November 1992 ASCII 153877 69 SNMP-X.25 management This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1383 An Experiment in DNS Based IP Routing C. Huitema December 1992 ASCII 32680 14 DNS-IP Potential solutions to the routing explosion. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1384 Naming Guidelines for Directory Pilots P. Barker S.E. Hardcastle-Kille January 1993 ASCII 25870 12 PS 175044 PDF 134487 X.500 Multinational This document defines a number of naming guidelines. Alignment to these guidelines is recommended for directory pilots. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1617 RTR0011 INFORMATIONAL INFORMATIONAL RFC1385 EIP: The Extended Internet Protocol Z. Wang November 1992 ASCII 39123 17 addressing 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. INFORMATIONAL INFORMATIONAL RFC1386 The US Domain A. Cooper J. Postel December 1992 ASCII 62310 31 DNS top-level 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. RFC1480 INFORMATIONAL INFORMATIONAL RFC1387 RIP Version 2 Protocol Analysis G. Malkin January 1993 ASCII 5598 3 RIP-2 As required by Routing Protocol Criteria (RFC 1264), this report documents the key features of the RIP-2 protocol and the current implementation experience. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1721 INFORMATIONAL INFORMATIONAL RFC1388 RIP Version 2 Carrying Additional Information G. Malkin January 1993 ASCII 16227 7 RIP-2 This document specifies an extension of the Routing Information Protocol (RIP), as defined in [1], to expand the amount of useful information carried in RIP packets and to add a measure of security. [STANDARDS- TRACK] RFC1723 RFC1058 PROPOSED STANDARD PROPOSED STANDARD RFC1389 RIP Version 2 MIB Extensions G. Malkin F. Baker January 1993 ASCII 23569 13 RIP-2 Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. [STANDARDS-TRACK] RFC1724 PROPOSED STANDARD PROPOSED STANDARD RFC1390 Transmission of IP and ARP over FDDI Networks D. Katz January 1993 ASCII 22077 11 IP-FDDI IEEE 802 MAC This memo defines a method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK] STD0036 STANDARD STANDARD RFC1391 The Tao of the IETF: A Guide for New Attendees of the Internet Engineering Task Force G. Malkin January 1993 ASCII 41892 19 meetings The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This will give them a warm, fuzzy feeling and enable them to make the meeting more productive for everyone. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1539 INFORMATIONAL INFORMATIONAL RFC1392 Internet Users' Glossary G. Malkin T. LaQuey Parker January 1993 ASCII 104624 53 There are many networking glossaries in existence. This glossary concentrates on terms which are specific to the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1983 INFORMATIONAL INFORMATIONAL RFC1393 Traceroute Using an IP Option G. Malkin January 1993 ASCII 13140 7 TRACE-IP ICMP MTU Line Speed This document specifies a new IP option and ICMP message type which duplicates the functionality of the existing traceroute method while generating fewer packets and completing in a shorter time. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1394 Relationship of Telex Answerback Codes to Internet Domains P. Robinson January 1993 ASCII 43776 15 DNS Country This RFC gives the list, as best known, of all common Internet domains and the conversion between specific country telex answerback codes and Internet country domain identifiers. It also lists the telex code and international dialing code, wherever it is available. It will also list major Internet "Public" E-Mail addresses. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1395 BOOTP Vendor Information Extensions J. Reynolds January 1993 ASCII 16314 8 TAGS 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). RFC1084 RFC1048 RFC1497 RFC1533 RFC0951 DRAFT STANDARD DRAFT STANDARD RFC1396 The Process for Organization of Internet Standards Working Group (POISED) S. Crocker January 1993 ASCII 22096 10 IAB IESG ISOC This report provides a summary of the POISED Working Group (WG), starting from the events leading to the formation of the WG to the end of 1992. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1397 Default Route Advertisement In BGP2 and BGP3 Version of The Border Gateway Protocol D. Haskin January 1993 ASCII 4124 2 BGP This document speficies the recommendation of the BGP Working Group on default route advertisement support in BGP2 [1] and BGP3 [2] versions of the Border Gateway Protocol. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1398 Definitions of Managed Objects for the Ethernet-Like Interface Types F. Kastenholz January 1993 ASCII 36684 17 MIB Management This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing ehternet-like objects. [STANDARDS-TRACK] RFC1284 RFC1623 DRAFT STANDARD DRAFT STANDARD RFC1399 Summary of 1300-1399 J. Elliott January 1997 ASCII 43662 22 Index INFORMATIONAL INFORMATIONAL RFC1400 Transition and Modernization of the Internet Registration Service S. Williamson March 1993 ASCII 13008 7 INTERNIC IR As a result of the NREN NIS award by National Science Foundation, non- DDN registration services will soon be transferred from the DDN NIC to the new Internet Registration Service, which is a part of an entity referred to as the InterNIC. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1401 Correspondence between the IAB and DISA on the use of DNS Internet Architecture Board January 1993 ASCII 12528 8 Domain Name Milnet This memo reproduces three letters exchanged between the Internet Activities Board (IAB) and the Defense Information Systems Agency (DISA) regarding the importance of using the Domain Name System (DNS) throughout the Internet, and phasing out the use of older host name to address tables, such as "hosts.txt". This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1402 There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places J. Martin January 1993 ASCII 71176 39 information introduction SIGUCCS User Services Help The ultimate goal is to make the route to these sources of information invisible to you. At present, this is not easy to do. I will explain some of the techniques that can be used to make these nuggets easier to pick up so that we all can be richer. This RFC provides information for the Internet community. It does not specify an Internet standard. RFC1290 FYI0010 INFORMATIONAL INFORMATIONAL RFC1403 BGP OSPF Interaction K. Varadhan January 1993 ASCII 36173 17 BGP-OSPF border gateway protocol open shortest path first routing This memo defines the various criteria to be used when designing an Autonomous System Border Routers (ASBR) that will run BGP with other ASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK] RFC1364 HISTORIC PROPOSED STANDARD RFC1404 A Model for Common Operational Statistics B. Stockman January 1993 ASCII 52814 27 Management Operations This memo describes a model for operational statistics in the Internet. It gives recommendations for metrics, measurements, polling periods, storage formats and presentation formats. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1857 INFORMATIONAL INFORMATIONAL RFC1405 Mapping between X.400(1984/1988) and Mail-11 (DECnet mail) C. Allocchio January 1993 ASCII 33885 19 SMTP EMail 822 This document describes a set of mappings which will enable inter working between systems operating the CCITT X.400 ( 1984 / 1988 ) Recommendations on Message Handling Systems, and systems running the Mail-11 (also known as DECnet mail) protocol. This memo defines an Experimental Protocol for the Internet community. RFC2162 EXPERIMENTAL EXPERIMENTAL RFC1406 Definitions of Managed Objects for the DS1 and E1 Interface Types F. Baker J. Watt Editors January 1993 ASCII 97559 50 DS1/E1-MIB T1 MIB Management SNMP This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing DS1 Interfaces -- including both T1 and E1 (a.k.a., CEPT 2 Mbit/s) links. [STANDARDS-TRACK] RFC1232 RFC2495 PROPOSED STANDARD PROPOSED STANDARD RFC1407 Definitions of Managed Objects for the DS3/E3 Interface Type T. Cox K. Tesink January 1993 ASCII 90682 43 DS3/E3-MIB T3 MIB Management SNMP This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing DS3 and E3 Interfaces. [STANDARDS-TRACK] RFC1233 RFC2496 PROPOSED STANDARD PROPOSED STANDARD RFC1408 Telnet Environment Option D. Borman Editor January 1993 ASCII 13936 7 TOPT-ENVIR Negotiation This document specifies a mechanism for passing environment information between a telnet client and server. [STANDARDS-TRACK] RFC1571 HISTORIC HISTORIC RFC1409 Telnet Authentication Option D. Borman Editor January 1993 ASCII 13119 7 security This memo defines an Experimental Protocol for the Internet community. RFC1416 EXPERIMENTAL EXPERIMENTAL RFC1410 IAB Official Protocol Standards J. Postel Editor March 1993 ASCII 76524 35 proposed draft experimental informational historic full This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). RFC1360 RFC1500 HISTORIC STANDARD RFC1411 Telnet Authentication: Kerberos Version 4 D. Borman Editor January 1993 ASCII 7967 4 TEL-KER Security option This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1412 Telnet Authentication: SPX K. Alagappan January 1993 ASCII 6952 4 TEL-SPX Security option This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1413 Identification Protocol M. St. Johns February 1993 ASCII 16291 8 IDENT Authentication The Identification Protocol was formerly called the Authentication Server Protocol. It has been renamed to better reflect its function. [STANDARDS-TRACK] RFC0931 PROPOSED STANDARD PROPOSED STANDARD RFC1414 Identification MIB M. St. Johns M. Rose February 1993 ASCII 14165 7 IDENT-MIB Management SNMP This memo defines a MIB for use with identifying the users associated with TCP connections. It provides functionality approximately equivalent to that provided by the protocol defined in RFC 1413 [1]. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1415 FTP-FTAM Gateway Specification J. Mindel R. Slaski January 1993 ASCII 128261 58 FTP FTAM transfer ISO OSI This memo describes a dual protocol stack application layer gateway that performs protocol translation, in an interactive environment, between the FTP and FTAM file transfer protocols. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1416 Telnet Authentication Option D. Borman Editor February 1993 ASCII 13270 7 TOPT-AUTH Security 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. RFC1409 RFC2941 EXPERIMENTAL EXPERIMENTAL RFC1417 NADF Standing Documents: A Brief Overview The North American Directory Forum February 1993 ASCII 7270 4 X.500 Directory 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. RFC1295 RFC1255 RFC1218 RFC1758 INFORMATIONAL INFORMATIONAL RFC1418 SNMP over OSI M. Rose March 1993 ASCII 7721 4 SNMP-OSI Management This memo addresses some concerns by defining a framework for running the SNMP in an environment which supports the OSI connectionless-mode transport service. [STANDARDS-TRACK] RFC1161 RFC1283 PROPOSED STANDARD PROPOSED STANDARD RFC1419 SNMP over AppleTalk G. Minshall M. Ritter March 1993 ASCII 16470 7 SNMP-AT Management This memo describes the method by which the Simple Network Management Protocol (SNMP) as specified in [1] can be used over AppleTalk protocols [2] instead of the Internet UDP/IP protocol stack. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1420 SNMP over IPX S. Bostock March 1993 ASCII 6762 4 SNMP-IPX Management This document defines a convention for encapsulating Simple Network Management Protocol (SNMP) [1] packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol [2]. [STANDARDS-TRACK] RFC1298 PROPOSED STANDARD PROPOSED STANDARD RFC1421 Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures J. Linn February 1993 ASCII 103894 42 PEM-ENC PEM This document defines message encryption and authentication procedures, in order to provide privacy-enhanced mail (PEM) services for electronic mail transfer in the Internet. [STANDARDS-TRACK] RFC1113 PROPOSED STANDARD PROPOSED STANDARD RFC1422 Privacy Enhancement for Internet Electronic Mail: Part II: Certificate-Based Key Management S. Kent February 1993 ASCII 86085 32 PEM-CKM PEM This is one of a series of documents defining privacy enhancement mechanisms for electronic mail transferred using Internet mail protocols. [STANDARDS-TRACK] RFC1114 PROPOSED STANDARD PROPOSED STANDARD RFC1423 Privacy Enhancement for Internet Electronic Mail: Part III: Algorithms, Modes, and Identifiers D. Balenson February 1993 ASCII 33277 14 PEM-ALG PEM This document provides definitions, formats, references, and citations for cryptographic algorithms, usage modes, and associated identifiers and parameters used in support of Privacy Enhanced Mail (PEM) in the Internet community. [STANDARDS-TRACK] RFC1115 PROPOSED STANDARD PROPOSED STANDARD RFC1424 Privacy Enhancement for Internet Electronic Mail: Part IV: Key Certification and Related Services B. Kaliski February 1993 ASCII 17537 9 PEM-KEY PEM This document describes three types of service in support of Internet Privacy-Enhanced Mail (PEM) [1-3]: key certification, certificate- revocation list (CRL) storage, and CRL retrieval. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1425 SMTP Service Extensions J. Klensin WG Chair N. Freed Editor M. Rose E. Stefferud D. Crocker February 1993 ASCII 20932 10 Mail 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] RFC1651 PROPOSED STANDARD PROPOSED STANDARD RFC1426 SMTP Service Extension for 8bit-MIMEtransport J. Klensin WG Chair N. Freed Editor M. Rose E. Stefferud D. Crocker February 1993 ASCII 11661 6 Mail This memo defines an extension to the SMTP service whereby an SMTP content body containing octets outside of the US ASCII octet range (hex RFC1652 PROPOSED STANDARD PROPOSED STANDARD RFC1427 SMTP Service Extension for Message Size Declaration J. Klensin WG Chair N. Freed Editor K. Moore February 1993 ASCII 17856 8 Mail 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] RFC1653 PROPOSED STANDARD PROPOSED STANDARD RFC1428 Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIME G. Vaudreuil February 1993 ASCII 12064 6 Mail This document outlines the problems in this environment and an approach to minimizing the cost of transition from current usage of non-MIME 8bit messages to MIME. This RFC provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1429 Listserv Distribute Protocol E. Thomas February 1993 ASCII 17759 8 LISTSERV Mail This memo specifies a subset of the distribution protocol used by the BITNET LISTSERV to deliver mail messages to large amounts of recipients. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1430 A Strategic Plan for Deploying an Internet X.500 Directory Service S. Hardcastle-Kille E. Huizer V. Cerf R. Hobby S. Kent February 1993 ASCII 47587 20 X.500 This document describes an overall strategy for deploying a Directory Service on the Internet, based on the OSI X.500 Directory Service. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1431 DUA Metrics (OSI-DS 33 (v2)) P. Barker February 1993 ASCII 42240 19 Directory User Agent Measurement Statistics Survey X.500 This document defines a set of criteria by which a DUA implementation, or more precisely a Directory user interface, may be judged. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1432 Recent Internet Books J. Quarterman March 1993 ASCII 27089 15 bibiography Here is a list of books related to using the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1433 Directed ARP J. Garrett J. Hagan J. Wong March 1993 ASCII 41028 18 DIR-ARP public networks SMDS Directed ARP is a dynamic address resolution procedure that enables hosts and routers to resolve advertised potential next-hop IP addresses on foreign IP networks to their associated link level addresses. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1434 Data Link Switching: Switch-to-Switch Protocol R. Dixon D. Kushi March 1993 ASCII 80182 33 PS 292006 PDF 181839 IBM SNA DLS SSP NetBIos This RFC describes IBM's support of Data Link Switching over TCP/IP. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1795 INFORMATIONAL INFORMATIONAL RFC1435 IESG Advice from Experience with Path MTU Discovery S. Knowles March 1993 ASCII 2708 2 Maximum Transmission Unit In the course of reviewing the MTU Discovery protocol for possible elevation to Draft Standard, a specific operational problem was uncovered. The problem results from the optional suppression of ICMP messages implemented in some routers. This memo outlines a modification to this practice to allow the correct functioning of MTU Discovery. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1436 The Internet Gopher Protocol (a distributed document search and retrieval protocol) F. Anklesaria M. McCahill P. Lindner D. Johnson D. Torrey B. Albert March 1993 ASCII 36493 16 GOPHER information locating This document describes the protocol, lists some of the implementations currently available, and has an overview of how to implement new client and server applications. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1437 The Extension of MIME Content-Types to a New Medium N. Borenstein M. Linimon April 01 1993 ASCII 13356 6 life form Matter transport Sentient This document defines one particular type of MIME data, the matter- transport/sentient-life-form type. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1438 Internet Engineering Task Force Statements Of Boredom (SOBs) A. Lyman Chapin C. Huitema April 01 1993 ASCII 3044 2 process policy This document creates a new subseries of RFCs, entitled, IETF Statements Of Boredom (SOBs). This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1439 The Uniqueness of Unique Identifiers C. Finseth March 1993 ASCII 20477 11 names This RFC provides information that may be useful when selecting a method to use for assigning unique identifiers to people. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1440 SIFT/UFT: Sender-Initiated/Unsolicited File Transfer R. Troth July 1993 ASCII 17366 9 SIFT UFT Send FTP This document describes a Sender-Initiated File Transfer (SIFT) protocol, also commonly called Unsolicited File Transfer (UFT) protocol. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1441 Introduction to version 2 of the Internet-standard Network Management Framework J. Case K. McCloghrie M. Rose S. Waldbusser April 1993 ASCII 25386 13 SNMPv2 SNMP Management Framework The purpose of this document is to provide an overview of version 2 of the Internet-standard Network Management Framework, termed the SNMP version 2 framework (SNMPv2). [STANDARDS-TRACK] HISTORIC PROPOSED STANDARD RFC1442 Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2) J. Case K. McCloghrie M. Rose S. Waldbusser April 1993 ASCII 95779 56 SNMP Management Framework SMI 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] RFC1902 PROPOSED STANDARD PROPOSED STANDARD RFC1443 Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2) J. Case K. McCloghrie M. Rose S. Waldbusser April 1993 ASCII 60947 31 SNMP Management Framework It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK] RFC1903 PROPOSED STANDARD PROPOSED STANDARD RFC1444 Conformance Statements for version 2 of the Simple Network Management Protocol (SNMPv2) J. Case K. McCloghrie M. Rose S. Waldbusser April 1993 ASCII 57744 33 SNMP Management Framework 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] RFC1904 PROPOSED STANDARD PROPOSED STANDARD RFC1445 Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2) J. Galvin K. McCloghrie April 1993 ASCII 99443 48 SNMP Management Framework It is the purpose of this document, the Administrative Model for SNMPv2, to define how the administrative framework is applied to realize effective network management in a variety of configurations and environments. [STANDARDS-TRACK] HISTORIC HISTORIC RFC1446 Security Protocols for version 2 of the Simple Network Management Protocol (SNMPv2) J. Galvin K. McCloghrie April 1993 ASCII 108733 52 SNMP Management Framework It is the purpose of this document, Security Protocols for SNMPv2, to define one such authentication and one such privacy protocol. [STANDARDS-TRACK] HISTORIC HISTORIC RFC1447 Party MIB for version 2 of the Simple Network Management Protocol (SNMPv2) K. McCloghrie J. Galvin April 1993 ASCII 80762 50 SNMP Management Framework The Administrative Model for SNMPv2 document [3] defines the properties associated with SNMPv2 parties, SNMPv2 contexts, and access control policies. It is the purpose of this document, the Party MIB for SNMPv2, to define managed objects which correspond to these properties. [STANDARDS-TRACK] HISTORIC HISTORIC RFC1448 Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2) J. Case K. McCloghrie M. Rose S. Waldbusser April 1993 ASCII 74224 36 SNMP Management Framework 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] RFC1905 PROPOSED STANDARD PROPOSED STANDARD RFC1449 Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2) J. Case K. McCloghrie M. Rose S. Waldbusser April 1993 ASCII 41161 25 SNMP Management Framework It is the purpose of this document to define how the SNMPv2 maps onto an initial set of transport domains. [STANDARDS-TRACK] RFC1906 PROPOSED STANDARD PROPOSED STANDARD RFC1450 Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2) J. Case K. McCloghrie M. Rose S. Waldbusser April 1993 ASCII 42172 27 SNMP Management Framework It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity. [STANDARDS-TRACK] RFC1907 PROPOSED STANDARD PROPOSED STANDARD RFC1451 Manager-to-Manager Management Information Base J. Case K. McCloghrie M. Rose S. Waldbusser April 1993 ASCII 62935 36 SNMP Management Framework It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity acting in both a manager role and an agent role. [STANDARDS-TRACK] HISTORIC HISTORIC RFC1452 Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework J. Case K. McCloghrie M. Rose S. Waldbusser April 1993 ASCII 32176 17 SNMP Management Framework The purpose of this document is to describe coexistence between version 2 of the Internet-standard Network Management Framework, termed the SNMP version 2 framework (SNMPv2) [1], and the original Internet-standard Network Management Framework (SNMPv1). [STANDARDS-TRACK] RFC1908 PROPOSED STANDARD PROPOSED STANDARD RFC1453 A Comment on Packet Video Remote Conferencing and the Transport/Network Layers W. Chimiak April 1993 ASCII 23563 10 XTP This RFC is a vehicle to inform the Internet community about XTP as it benefits from past Internet activity and targets general-purpose applications and multimedia applications with the emerging ATM networks in mind. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1454 Comparison of Proposals for Next Version of IP T. Dixon May 1993 ASCII 35064 15 IPng PIP TUBA SIP This is a slightly edited reprint of RARE Technical Report (RTC(93)004). This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1455 Physical Link Security Type of Service D. Eastlake 3rd May 1993 ASCII 12391 6 TOS-LS TOS This RFC documents an experimental protocol providing a Type of Service (TOS) to request maximum physical link security. This is an addition to the types of service enumerated in RFC 1349: Type of Service in the Internet Protocol Suite. This memo defines an Experimental Protocol for the Internet community. RFC2474 EXPERIMENTAL EXPERIMENTAL RFC1456 Conventions for Encoding the Vietnamese Language VISCII: VIetnamese Standard Code for Information Interchange VIQR: VIetnamese Quoted-Readable Specification Vietnamese Standardization Working Group May 1993 ASCII 14775 7 Character Set This document provides information to the Internet community on the currently used conventions for encoding Vietnamese characters into 7-bit US ASCII and in an 8-bit form. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1457 Security Label Framework for the Internet R. Housley May 1993 ASCII 35802 14 This memo presents a security labeling framework for the Internet. The framework is intended to help protocol designers determine what, if any, security labeling should be supported by their protocols. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1458 Requirements for Multicast Protocols R. Braudes S. Zabele May 1993 ASCII 48106 19 Real-Time This memo discusses some of these unresolved issues, and provides a high-level design for a new multicast transport protocol, group address and membership authority, and modifications to existing routing protocols. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1459 Internet Relay Chat Protocol J. Oikarinen D. Reed May 1993 ASCII 138964 65 IRCP IRC The IRC protocol is a text-based protocol, with the simplest client being any socket program capable of connecting to the server. This memo defines an Experimental Protocol for the Internet community. RFC2810 RFC2811 RFC2812 RFC2813 EXPERIMENTAL EXPERIMENTAL RFC1460 Post Office Protocol - Version 3 M. Rose June 1993 ASCII 38827 17 Email This memo is a revision to RFC 1225, a Draft Standard. [STANDARDS- TRACK] RFC1225 RFC1725 DRAFT STANDARD DRAFT STANDARD RFC1461 SNMP MIB extension for Multiprotocol Interconnect over X.25 D. Throop May 1993 ASCII 47945 21 X25-MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Multiprotocol Interconnect (including IP) traffic carried over X.25. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1462 FYI on "What is the Internet?" E. Krol E. Hoffman May 1993 ASCII 27811 11 Introduction This FYI RFC answers the question, "What is the Internet?" and is produced by the User Services Working Group of the Internet Engineering Task Force (IETF). This memo provides information for the Internet community. It does not specify an Internet standard. FYI0020 INFORMATIONAL INFORMATIONAL RFC1463 FYI on Introducing the Internet-- A Short Bibliography of Introductory Internetworking Readings E. Hoffman L. Jackson May 1993 ASCII 7116 4 This bibliography offers a short list of recent information resources that will help the network novice become familiar with the Internet, including its associated networks, resources, protocols, and history. This memo provides information for the Internet community. It does not specify an Internet standard. FYI0019 INFORMATIONAL INFORMATIONAL RFC1464 Using the Domain Name System To Store Arbitrary String Attributes R. Rosenbaum May 1993 ASCII 7953 4 DNS TXT This paper describes a simple means to associate arbitrary string information (ASCII text) with attributes that have not been defined by the DNS. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1465 Routing Coordination for X.400 MHS Services Within a Multi Protocol / Multi Network Environment Table Format V3 for Static Routing D. Eppenberger May 1993 ASCII 66833 31 X400 This document proposes short term solutions for maintaining and distributing routing information and shows how messages can travel over different networks by using multi stack MTAs as relays. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1466 Guidelines for Management of IP Address Space E. Gerich May 1993 ASCII 22262 10 CIDR This document proposes a plan which will forward the implementation of RFC 1174 and which defines the allocation and assignment of the network number space. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1366 RFC2050 INFORMATIONAL INFORMATIONAL RFC1467 Status of CIDR Deployment in the Internet C. Topolcic August 1993 ASCII 20720 9 routing tables allocation registry IR IANA classless This document describes the current status of the development and deployment of CIDR technology into the Internet. This document replaces RFC 1367, which was a schedule for the deployment of IP address space management procedures to support route aggregation. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1367 INFORMATIONAL INFORMATIONAL RFC1468 Japanese Character Encoding for Internet Messages J. Murai M. Crispin E. van der Poel June 1993 ASCII 10970 6 Set This document describes the encoding used in electronic mail [RFC822] and network news [RFC1036] messages in several Japanese networks. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1469 IP Multicast over Token-Ring Local Area Networks T. Pusateri June 1993 ASCII 8189 4 IP-TR-MC 802.2 802.5 This document specifies a method for the transmission of IP multicast datagrams over Token-Ring Local Area Networks. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1470 FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices R. Enger J. Reynolds June 1993 ASCII 308528 192 NOCTOOLS The goal of this FYI memo is to provide an update to FYI 2, RFC 1147 [1], which provided practical information to site administrators and network managers. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1147 FYI0002 INFORMATIONAL INFORMATIONAL RFC1471 The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol F. Kastenholz June 1993 ASCII 53558 25 PPP/LCP MIB Management Framework PPP This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the Link Control Protocol and Link Quality Monitoring on subnetwork interfaces that use the family of Point-to-Point Protocols [8, 9, 10, 11, & 12]. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1472 The Definitions of Managed Objects for the Security Protocols of the Point-to-Point Protocol F. Kastenholz June 1993 ASCII 27152 13 PPP/SEC MIB Management Framework PPP This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the Security Protocols on subnetwork interfaces using the family of Point-to-Point Protocols [8, 9, 10, 11, & 12]. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1473 The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol F. Kastenholz June 1993 ASCII 20484 10 PPP/IP MIB Management Framework PPP This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the IP Network Control Protocol on subnetwork interfaces using the family of Point-to-Point Protocols [8, 9, 10, 11, & 12]. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1474 The Definitions of Managed Objects for the Bridge Network Control Protocol of the Point-to-Point Protocol F. Kastenholz June 1993 ASCII 31846 15 PPP/Bridge Management Framework PPP This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the bridge Network Control Protocol [10] on subnetwork interfaces using the family of Point-to-Point Protocols. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1475 TP/IX: The Next Internet R. Ullmann June 1993 ASCII 77854 35 TP-IX IPv7 IPng This memo presents the specification for version 7 of the Internet Protocol, as well as version 7 of the TCP and the user datagram protocol. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. EXPERIMENTAL EXPERIMENTAL RFC1476 RAP: Internet Route Access Protocol R. Ullmann June 1993 ASCII 45560 20 RAP Routing This RFC describes an open distance vector routing protocol for use at all levels of the internet, from isolated LANs to the major routers of an international commercial network provider. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. EXPERIMENTAL EXPERIMENTAL RFC1477 IDPR as a Proposed Standard M. Steenstrup July 1993 ASCII 32238 13 Routing Policy This document contains a discussion of inter-domain policy routing (IDPR), including an overview of functionality and a discussion of experiments. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL PROPOSED STANDARD RFC1478 An Architecture for Inter-Domain Policy Routing M. Steenstrup June 1993 ASCII 90673 35 IDPR-ARCH IDPR We present an architecture for inter-domain policy routing (IDPR). [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1479 Inter-Domain Policy Routing Protocol Specification: Version 1 M. Steenstrup July 1993 ASCII 275823 108 IDPR IDPR We present the set of protocols and procedures that constitute Inter- Domain Policy Routing (IDPR). [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1480 The US Domain A. Cooper J. Postel June 1993 ASCII 100556 47 DNS top-level 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. RFC1386 INFORMATIONAL INFORMATIONAL RFC1481 IAB Recommendation for an Intermediate Strategy to Address the Issue of Scaling C. Huitema July 1993 ASCII 3502 2 CIDR CIDR is proposed as an immediate term strategy to extend the life of the current 32 bit IP address space. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1482 Aggregation Support in the NSFNET Policy-Based Routing Database M. Knopper S. Richardson June 1993 ASCII 25330 11 CIDR This document describes plans for support of route aggregation, as specified in the descriptions of Classless Inter-Domain Routing (CIDR) [1] and the BGP-4 protocol [2], by the NSFNET Backbone Network Service. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1483 Multiprotocol Encapsulation over ATM Adaptation Layer 5 Juha Heinanen July 1993 ASCII 35192 16 ATM-ENCAP IP AAL5 over This memo describes two encapsulations methods for carrying network interconnect traffic over ATM AAL5. [STANDARDS-TRACK] RFC2684 PROPOSED STANDARD PROPOSED STANDARD RFC1484 Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2)) S. Hardcastle-Kille July 1993 ASCII 48974 25 X.500 directory names representing names This proposal sets out some conventions for representing names in a friendly manner, and shows how this can be used to achieve really friendly naming. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. RFC1781 RFC3494 HISTORIC EXPERIMENTAL RFC1485 A String Representation of Distinguished Names (OSI-DS 23 (v5)) S. Hardcastle-Kille July 1993 ASCII 11158 7 X.500 directory names representing names When a distinguished name is communicated between to users not using a directory protocol (e.g., in a mail message), there is a need to have a user-oriented string representation of distinguished name. [STANDARDS- TRACK] RFC1779 RFC3494 HISTORIC PROPOSED STANDARD RFC1486 An Experiment in Remote Printing M. Rose C. Malamud July 1993 ASCII 26373 14 electronic mail facsimile 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. RFC1528 RFC1529 EXPERIMENTAL EXPERIMENTAL RFC1487 X.500 Lightweight Directory Access Protocol W. Yeong T. Howes S. Kille July 1993 ASCII 44947 21 X.500 DAP interactive access 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] RFC1777 RFC3494 HISTORIC PROPOSED STANDARD RFC1488 The X.500 String Representation of Standard Attribute Syntaxes T. Howes S. Kille W. Yeong C. Robbins July 1993 ASCII 17182 11 X.500 LDAP lightweight directory protocol This document defines the requirements that must be satisfied by encoding rules used to render Directory attribute syntaxes into a form suitable for use in the LDAP, then goes on to define the encoding rules for the standard set of attribute syntaxes defined in [1,2] and [3]. [STANDARDS-TRACK] RFC1778 PROPOSED STANDARD PROPOSED STANDARD RFC1489 Registration of a Cyrillic Character Set A. Chernov July 1993 ASCII 7798 5 Though the proposed character set "koi8-r" is not currently an international standard, there is very large user community (including Relcom Net) supporting it. Factually, "koi8-r" is de-facto standard for Unix and global network applications in the former Soviet Union. This is the reason the Society of Unix User Groups (SUUG) believes "koi8-r" should be registered. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1490 Multiprotocol Interconnect over Frame Relay T. Bradley C. Brown A. Malis July 1993 ASCII 75206 35 standard standards IP over This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. Additionally, it describes a simple fragmentation procedure for carrying large frames over a frame relay network with a smaller MTU. [STANDARDS-TRACK] RFC1294 RFC2427 DRAFT STANDARD DRAFT STANDARD RFC1491 A Survey of Advanced Usages of X.500 C. Weider R. Wright July 1993 ASCII 34883 18 directory This document is the result of a survey asking people to detail their advanced usages of X.500. It is intended to show how various organizations are using X.500 in ways which extend the view of X.500 as a "White Pages" service. This RFC is a product of the Integrated Directory Services Working Group of the Application and User Services Areas of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard. FYI0021 INFORMATIONAL INFORMATIONAL RFC1492 An Access Control Protocol, Sometimes Called TACACS C. Finseth July 1993 ASCII 41880 21 TACACS Terminal Server TAC This RFC documents the extended TACACS protocol use by the Cisco Systems terminal servers. This same protocol is used by the University of Minnesota's distributed authentication system. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1493 Definitions of Managed Objects for Bridges E. Decker P. Langille A. Rijsinghani K. McCloghrie July 1993 ASCII 74493 34 BRIDGE-MIB SNMP MIB standard standards This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for managing MAC bridges based on the IEEE 802.1D-1990 standard between Local Area Network (LAN) segments. [STANDARDS-TRACK] RFC1286 DRAFT STANDARD DRAFT STANDARD RFC1494 Equivalences between 1988 X.400 and RFC-822 Message Bodies H. Alvestrand S. Thompson August 1993 ASCII 37273 19 Equiv Mail This document describes the content of the "IANA MHS/MIME Equivalence table", and defines the initial configuration of this table. Mappings for new MIME content-types and/or X.400 body part types should be registered with the IANA to minimize redundancy and promote interoperability. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1495 Mapping between X.400 and RFC-822 Message Bodies H. Alvestrand S. Kille R. Miles M. Rose S. Thompson August 1993 ASCII 20071 11 Mail 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] RFC2156 RFC1327 PROPOSED STANDARD PROPOSED STANDARD RFC1496 Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages H. Alvestrand J. Romaguera K. Jordan August 1993 ASCII 8411 5 HARPOON Mail This document describes how RFC-1328 must be modified in order to provide adequate support for the scenarios: It replaces chapter 6 of RFC-1328. The rest of RFC-1328 is NOT obsoleted. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1497 BOOTP Vendor Information Extensions J. Reynolds August 1993 ASCII 16805 8 TAGS Boot 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). RFC1395 RFC1084 RFC1048 RFC1533 RFC0951 DRAFT STANDARD DRAFT STANDARD RFC1498 On the Naming and Binding of Network Destinations J. Saltzer August 1993 ASCII 24698 10 NAMES Addresses Routes Objects Nodes Paths This brief paper offers a perspective on the subject of names of destinations in data communication networks. It suggests two ideas: First, it is helpful to distinguish among four different kinds of objects that may be named as the destination of a packet in a network. Second, the operating system concept of binding is a useful way to describe the relations among the four kinds of objects. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1499 Summary of 1400-1499 J. Elliott January 1997 ASCII 40923 21 Index INFORMATIONAL INFORMATIONAL RFC1500 Internet Official Protocol Standards J. Postel August 1993 ASCII 79557 36 IAB This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). [STANDARDS-TRACK] RFC1410 RFC1540 HISTORIC STANDARD RFC1501 OS/2 User Group E. Brunsen August 1993 ASCII 3636 2 Memo soliciting reactions to the proposal of a OS/2 User Group. This memo provides information for the Internet community. This memo does not specify an IAB standard of any kind. INFORMATIONAL INFORMATIONAL RFC1502 X.400 Use of Extended Character Sets H. Alvestrand August 1993 ASCII 27976 14 Mail This RFC defines a suggested method of using "GeneralText" in order to harmonize as much as possible the usage of this body part. [STANDARDS- TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1503 Algorithms for Automating Administration in SNMPv2 Managers K. McCloghrie M. Rose August 1993 ASCII 33542 14 Management SNMP When a user invokes an SNMPv2 management application, it may be desirable for the user to specify the minimum amount of information necessary to establish and maintain SNMPv2 communications. This memo suggests an approach to achieve this goal. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1504 Appletalk Update-Based Routing Protocol: Enhanced Appletalk Routing A. Oppenheimer August 1993 ASCII 201553 82 AVRP This document provides detailed information about the AppleTalk Update- based Routing Protocol (AURP) and wide area routing. AURP provides wide area routing enhancements to the AppleTalk routing protocols and is fully compatible with AppleTalk Phase 2. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1505 Encoding Header Field for Internet Messages A. Costanzo D. Robinson R. Ullmann August 1993 ASCII 63796 36 EHF-MAIL Mail This document expands upon the elective experimental Encoding header field which permits the mailing of multi-part, multi-structured messages. It replaces RFC 1154. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. RFC1154 EXPERIMENTAL EXPERIMENTAL RFC1506 A Tutorial on Gatewaying between X.400 and Internet Mail J. Houttuin August 1993 ASCII 85550 39 822 email RTR This tutorial was produced especially to help new gateway managers find their way into the complicated subject of mail gatewaying according to RFC 1327. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1507 DASS - Distributed Authentication Security Service C. Kaufman September 1993 ASCII 287809 119 DASS CAT The goal of DASS is to provide authentication services in a distributed environment which are both more secure and easier to use than existing mechanisms. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. EXPERIMENTAL EXPERIMENTAL RFC1508 Generic Security Service Application Program Interface J. Linn September 1993 ASCII 111228 49 CAT,GSS,API This Generic Security Service Application Program Interface (GSS-API) definition provides security services to callers in a generic fashion, supportable with a range of underlying mechanisms and technologies and hence allowing source-level portability of applications to different environments. [STANDARDS-TRACK] RFC2078 PROPOSED STANDARD PROPOSED STANDARD RFC1509 Generic Security Service API : C-bindings J. Wray September 1993 ASCII 99608 48 GSSAPI CAT,GSS This document specifies C language bindings for the Generic Security Service Application Program Interface (GSS-API), which is described at a language-independent conceptual level in other documents. [STANDARDS- TRACK] RFC2744 PROPOSED STANDARD PROPOSED STANDARD RFC1510 The Kerberos Network Authentication Service (V5) J. Kohl C. Neuman September 1993 ASCII 275395 112 KERBEROS CAT,Security This document gives an overview and specification of Version 5 of the protocol for the Kerberos network authentication system. [STANDARDS- TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1511 Common Authentication Technology Overview J. Linn September 1993 ASCII 4185 2 CAT,Security This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1512 FDDI Management Information Base J. Case A. Rijsinghani September 1993 ASCII 108589 51 FDDI-MIB MIB SNMP This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing devices which implement the FDDI based on the ANSI FDDI SMT 7.3 draft standard, which has been forwarded for publication by the X3T9.5 committee. RFC1285 PROPOSED STANDARD PROPOSED STANDARD RFC1513 Token Ring Extensions to the Remote Network Monitoring MIB S. Waldbusser September 1993 ASCII 121974 55 Monitoring SNMP This memo defines extensions to the Remote Network Monitoring MIB for managing 802.5 Token Ring networks. [STANDARDS-TRACK] RFC1271 PROPOSED STANDARD PROPOSED STANDARD RFC1514 Host Resources MIB P. Grillo S. Waldbusser September 1993 ASCII 63775 33 HOST-MIB Management SNMP This memo defines a MIB for use with managing host systems. [STANDARDS- TRACK] RFC2790 PROPOSED STANDARD PROPOSED STANDARD RFC1515 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) D. McMaster K. McCloghrie S. Roberts September 1993 ASCII 52828 25 MIB Management SNMP This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing IEEE 802.3 Medium Attachment Units (MAUs). [STANDARDS-TRACK] RFC3636 PROPOSED STANDARD PROPOSED STANDARD RFC1516 Definitions of Managed Objects for IEEE 802.3 Repeater Devices D. McMaster K. McCloghrie September 1993 ASCII 82918 40 Management SNMP This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IEEE 802.3 10 Mb/second baseband repeaters, sometimes referred to as "hubs." [STANDARDS-TRACK] RFC1368 RFC2108 DRAFT STANDARD DRAFT STANDARD RFC1517 Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR) Internet Engineering Steering Group R. Hinden September 1993 ASCII 7357 4 CIDR Address Classless Inter-Domain Routing (CIDR) defines a mechanism to slow the growth of routing tables and reduce the need to allocate new IP network numbers. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1518 An Architecture for IP Address Allocation with CIDR Y. Rekhter T. Li September 1993 ASCII 72609 27 CIDR-ARCH Classless Routing This paper provides an architecture and a plan for allocating IP addresses in the Internet. This architecture and the plan are intended to play an important role in steering the Internet towards the Address Assignment and Aggregating Strategy. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1519 Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy V. Fuller T. Li J. Yu K. Varadhan September 1993 ASCII 59998 24 CIDR-STRA This memo discusses strategies for address assignment of the existing IP address space with a view to conserve the address space and stem the explosive growth of routing tables in default-route-free routers. [STANDARDS-TRACK] RFC1338 PROPOSED STANDARD PROPOSED STANDARD RFC1520 Exchanging Routing Information Across Provider Boundaries in the CIDR Environment Y. Rekhter C. Topolcic September 1993 ASCII 20389 9 Classless Routing The purpose of this document is twofold. First, it describes various alternatives for exchanging inter-domain routing information across domain boundaries, where one of the peering domain is CIDR-capable and another is not. Second, it addresses the implications of running CIDR- capable inter-domain routing protocols (e.g., BGP-4, IDRP) on intra- domain routing. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1521 MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies N. Borenstein N. Freed September 1993 ASCII 187424 81 PS 393670 PDF 205091 email multimedia This document redefines the format of message bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information. This is based on earlier work documented in RFC 934 and STD 11, RFC 1049, but extends and revises that work. [STANDARDS-TRACK] RFC1341 RFC2045 RFC2046 RFC2047 RFC2048 RFC2049 RFC1590 DRAFT STANDARD DRAFT STANDARD RFC1522 MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text K. Moore September 1993 ASCII 22502 10 email character This memo describes an extension to the message format defined in RFC 1521, to allow the representation of character sets other than ASCII in RFC 822 (STD 11) message headers. The extensions described were designed to be highly compatible with existing Internet mail handling software, and to be easily implemented in mail readers that support RFC 1521. RFC1342 RFC2045 RFC2046 RFC2047 RFC2048 RFC2049 DRAFT STANDARD DRAFT STANDARD RFC1523 The text/enriched MIME Content-type N. Borenstein September 1993 ASCII 32691 15 email mail richtext MIME [RFC-1341, RFC-1521] defines a format and general framework for the representation of a wide variety of data types in Internet mail. This document defines one particular type of MIME data, the text/enriched type, a refinement of the "text/richtext" type defined in RFC 1341. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1563 RFC1896 INFORMATIONAL INFORMATIONAL RFC1524 A User Agent Configuration Mechanism For Multimedia Mail Format Information N. Borenstein September 1993 ASCII 26464 12 MIME email mailcap This memo suggests a file format to be used to inform multiple mail reading user agent programs about the locally-installed facilities for handling mail in various formats. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1525 Definitions of Managed Objects for Source Routing Bridges E. Decker K. McCloghrie P. Langille A. Rijsinghani September 1993 ASCII 38100 18 SRB-MIB MIB Management SNMP This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for managing source routing and source routing transparent bridges. These bridges are also required to implement relevant groups in the Bridge MIB. [STANDARDS-TRACK] RFC1286 PROPOSED STANDARD PROPOSED STANDARD RFC1526 Assignment of System Identifiers for TUBA/CLNP Hosts D. Piscitello September 1993 ASCII 16848 8 NSAP Address This document describes conventions whereby the system identifier portion of an RFC 1237 style NSAP address may be guaranteed uniqueness within a routing domain for the purpose of autoconfiguration in TUBA/CLNP internets. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1527 What Should We Plan Given the Dilemma of the Network? G. Cook September 1993 ASCII 46935 17 The Internet community needs to be asking what the most important policy issues facing the network are. And given agreement on any particular set of policy issues, the next thing we should be asking is, what would be some of the political choices that would follow for Congress to make? This memo is a shortened version of the suggested policy draft. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1528 Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures C. Malamud M. Rose October 1993 ASCII 18576 12 REM-PRINT FAX Facsimile 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. RFC1486 EXPERIMENTAL EXPERIMENTAL RFC1529 Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Administrative Policies C. Malamud M. Rose October 1993 ASCII 11142 5 FAX Facsimile This document defines the administrative policies for the operation of remote printer facilities within the context of the tpc.int subdomain. The document describes different approaches to resource recovery for remote printer server sites and includes discussions of issues pertaining to auditing, security, and denial of access. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1486 INFORMATIONAL INFORMATIONAL RFC1530 Principles of Operation for the TPC.INT Subdomain: General Principles and Policy C. Malamud M. Rose October 1993 ASCII 15031 7 FAX Facsimile This document defines the initial principles of operation for the tpc.int subdomain, a collection of service listings accessible over the Internet infrastructure through an administered namespace contained within the Domain Name System. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1531 Dynamic Host Configuration Protocol R. Droms October 1993 ASCII 96192 39 DHCP The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network. [STANDARDS-TRACK] RFC1541 PROPOSED STANDARD PROPOSED STANDARD RFC1532 Clarifications and Extensions for the Bootstrap Protocol W. Wimer October 1993 ASCII 51545 22 BOOTP Some aspects of the BOOTP protocol were rather loosely defined in its original specification. In particular, only a general description was provided for the behavior of "BOOTP relay agents" (originally called BOOTP forwarding agents"). The client behavior description also suffered in certain ways. This memo attempts to clarify and strengthen the specification in these areas. [STANDARDS-TRACK] RFC1542 RFC0951 PROPOSED STANDARD PROPOSED STANDARD RFC1533 DHCP Options and BOOTP Vendor Extensions S. Alexander R. Droms October 1993 ASCII 50919 30 Dynamic Host Configuration Bootstrap This document specifies the current set of DHCP options. [STANDARDS- TRACK] RFC1497 RFC1395 RFC1084 RFC1048 RFC2132 PROPOSED STANDARD PROPOSED STANDARD RFC1534 Interoperation Between DHCP and BOOTP R. Droms October 1993 ASCII 6966 4 DHCP-BOOTP Dynamic Host Configuration Bootstrap DHCP provides a superset of the functions provided by BOOTP. This document describes the interactions between DHCP and BOOTP network participants. [STANDARDS-TRACK] DRAFT STANDARD PROPOSED STANDARD RFC1535 A Security Problem and Proposed Correction With Widely Deployed DNS Software E. Gavron October 1993 ASCII 9722 5 Domain Name System This document discusses a flaw in some of the currently distributed name resolver clients. The flaw exposes a security weakness related to the search heuristic invoked by these same resolvers when users provide a partial domain name, and which is easy to exploit. This document points out the flaw, a case in point, and a solution. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1536 Common DNS Implementation Errors and Suggested Fixes A. Kumar J. Postel C. Neuman P. Danzig S. Miller October 1993 ASCII 25476 12 Domain Name System This memo describes common errors seen in DNS implementations and suggests some fixes. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1537 Common DNS Data File Configuration Errors P. Beertema October 1993 ASCII 19825 9 Domain Name System This memo describes errors often found in DNS data files. It points out common mistakes system administrators tend to make and why they often go unnoticed for long periods of time. This memo provides information for the Internet community. It does not specify an Internet standard. RFC1912 INFORMATIONAL INFORMATIONAL RFC1538 Advanced SNA/IP : A Simple SNA Transport Protocol W. Behl B. Sterling W. Teskey October 1993 ASCII 21217 10 ADSNA-IP Domain Name System This RFC provides information for the Internet community about a method for establishing and maintaining SNA sessions over an IP internet. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1539 The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force G. Malkin October 1993 ASCII 48199 22 Introduction The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This memo provides information for the Internet community. It does not specify an Internet standard. [FYI 17] RFC1391 RFC1718 INFORMATIONAL INFORMATIONAL RFC1540 Internet Official Protocol Standards J. Postel October 1993 ASCII 75496 34 status procedure index This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). [STANDARDS-TRACK] RFC1500 RFC1600 HISTORIC STANDARD RFC1541 Dynamic Host Configuration Protocol R. Droms October 1993 ASCII 96950 39 DHCP The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network. DHCP is based on the Bootstrap Protocol (BOOTP) adding the capability of automatic allocation of reusable network addresses and additional configuration options. [STANDARDS-TRACK] RFC1531 RFC2131 PROPOSED STANDARD PROPOSED STANDARD RFC1542 Clarifications and Extensions for the Bootstrap Protocol W. Wimer October 1993 ASCII 52948 23 BOOTP Some aspects of the BOOTP protocol were rather loosely defined in its original specification. In particular, only a general description was provided for the behavior of "BOOTP relay agents" (originally called BOOTP forwarding agents"). The client behavior description also suffered in certain ways. This memo attempts to clarify and strengthen the specification in these areas. [STANDARDS-TRACK] RFC1532 RFC0951 DRAFT STANDARD DRAFT STANDARD RFC1543 Instructions to RFC Authors J. Postel October 1993 ASCII 31383 16 Request For Comment 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. RFC1111 RFC0825 RFC2223 INFORMATIONAL INFORMATIONAL RFC1544 The Content-MD5 Header Field M. Rose November 1993 ASCII 6478 3 MIME EMail Integrity MIC Digest This memo defines the use of an optional header field, Content-MD5, which may be used as a message integrity check (MIC), to verify that the decoded data are the same data that were initially sent. [STANDARDS- TRACK] RFC1864 PROPOSED STANDARD PROPOSED STANDARD RFC1545 FTP Operation Over Big Address Records (FOOBAR) D. Piscitello November 1993 ASCII 8985 5 FTP File Transfer PORT PASV LPRT LPSV This RFC specifies a method for assigning long addresses in the HOST- PORT specification for the data port to be used in establishing a data connection for File Transfer Protocol, FTP (STD 9, RFC 959). This is a general solution, applicable for all "next generation" IP alternatives, and can also be extended to allow FTP operation over transport interfaces other than TCP. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. Related to RFC0959 RFC1639 EXPERIMENTAL EXPERIMENTAL RFC1546 Host Anycasting Service C. Partridge T. Mendez W. Milliken November 1993 ASCII 22263 9 Resource Location Multicasting This RFC describes an internet anycasting service for IP. The primary purpose of this memo is to establish the semantics of an anycasting service within an IP internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1547 Requirements for an Internet Standard Point-to-Point Protocol D. Perkins December 1993 ASCII 49810 21 PPP link serial line This document discusses the evaluation criteria for an Internet Standard Data Link Layer protocol to be used with point-to-point links. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1548 The Point-to-Point Protocol (PPP) W. Simpson December 1993 ASCII 111638 53 link serial line This document defines the PPP organization and methodology, and the PPP encapsulation, together with an extensible option negotiation mechanism which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. [STANDARDS-TRACK] RFC1331 RFC1661 RFC1570 DRAFT STANDARD DRAFT STANDARD RFC1549 PPP in HDLC Framing W. Simpson Editor December 1993 ASCII 36352 18 point link serial line This document describes the use of HDLC for framing PPP encapsulated packets. [STANDARDS-TRACK] RFC1662 DRAFT STANDARD DRAFT STANDARD RFC1550 IP: Next Generation (IPng) White Paper Solicitation S. Bradner A. Mankin December 1993 ASCII 12472 6 This memo solicits white papers on topics related to the IPng requirements and selection criteria. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1551 Novell IPX Over Various WAN Media (IPXWAN) M. Allen December 1993 ASCII 54210 22 Internetworking Packet Exchange This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocol Novell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1634 INFORMATIONAL INFORMATIONAL RFC1552 The PPP Internetworking Packet Exchange Control Protocol (IPXCP) W. Simpson December 1993 ASCII 29173 16 IPXCP IPX point serial line link This document defines the Network Control Protocol for establishing and configuring the IPX protocol over PPP. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1553 Compressing IPX Headers Over WAN Media (CIPX) S. Mathur M. Lewis December 1993 ASCII 47450 23 CIPX Internetworking Packet Exchange This document describes a method for compressing the headers of IPX datagrams (CIPX). [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1554 ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP M. Ohta K. Handa December 1993 ASCII 11449 6 Character Set Japanese This memo describes a text encoding scheme: "ISO-2022-JP-2", which is used experimentally for electronic mail [RFC822] and network news [RFC1036] messages in several Japanese networks. The encoding is a multilingual extension of "ISO-2022-JP", the existing encoding for Japanese [2022JP]. The encoding is supported by an Emacs based multilingual text editor: MULE [MULE]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1555 Hebrew Character Encoding for Internet Messages H. Nussbacher Y. Bourvine December 1993 ASCII 9273 5 Character Set This document describes the encoding used in electronic mail [RFC822] for transferring Hebrew. The standard devised makes use of MIME [RFC1521] and ISO-8859-8. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1556 Handling of Bi-directional Texts in MIME H. Nussbacher December 1993 ASCII 5602 3 Character Set This document describes the format and syntax of the "direction" keyword to be used with bi-directional texts in MIME. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1557 Korean Character Encoding for Internet Messages U. Choi K. Chon H. Park December 1993 ASCII 8736 5 Character Set This document describes the encoding method being used to represent Korean characters in both header and body part of the Internet mail messages [RFC822]. This encoding method was specified in 1991, and has since then been used. It has now widely being used in Korean IP networks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1558 A String Representation of LDAP Search Filters T. Howes December 1993 ASCII 5239 3 X.500 Directory The Lightweight Directory Access Protocol (LDAP) defines a network representation of a search filter transmitted to an LDAP server. Some applications may find it useful to have a common way of representing these search filters in a human-readable form. This document defines a human-readable string format for representing LDAP search filters. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1960 INFORMATIONAL INFORMATIONAL RFC1559 DECnet Phase IV MIB Extensions J. Saperia December 1993 ASCII 125427 69 DECNET-MIB Management SNMP This memo defines a set of DECnet Phase IV extensions that have been created for the Internet MIB. It reflects changes which are the result of operational experience based on RFC 1289. [STANDARDS-TRACK] RFC1289 DRAFT STANDARD DRAFT STANDARD RFC1560 The MultiProtocol Internet B. Leiner Y. Rekhter December 1993 ASCII 16651 7 Architecture Protocol There has recently been considerable discussion on two topics: MultiProtocol approaches in the Internet and the selection of a next generation Internet Protocol. This document suggests a strawman position for goals and approaches for the IETF/IESG/IAB in these areas. It takes the view that these two topics are related, and proposes directions for the IETF/IESG/IAB to pursue. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1561 Use of ISO CLNP in TUBA Environments D. Piscitello December 1993 ASCII 55902 25 CLNP-TUBA OSI IP Internet Protocol This memo specifies a profile of the ISO/IEC 8473 Connectionless-mode Network Layer Protocol for use in conjunction with RFC 1347, TCP/UDP over Bigger Addresses. It describes the use of CLNP to provide the lower-level service expected by Transmission Control Protocol and User Datagram Protocol. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. EXPERIMENTAL EXPERIMENTAL RFC1562 Naming Guidelines for the AARNet X.500 Directory Service G. Michaelson M. Prior December 1993 ASCII 6884 4 Australia This document is an AARNet (Australian Academic and Research Network) Engineering Note (AEN-001). AARNet Engineering Notes are engineering documents of the AARNet Engineering Working Group, and record current or proposed operational practices related to the provision of Internetworking services within Australia, and AARNet in particular. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1563 The text/enriched MIME Content-type N. Borenstein January 1994 ASCII 32913 16 PS 73543 PDF 37459 email mail richtext MIME [RFC-1341, RFC-1521] defines a format and general framework for the representation of a wide variety of data types in Internet mail. This document defines one particular type of MIME data, the text/enriched type, a refinement of the "text/richtext" type defined in RFC 1341. The text/enriched MIME type is intended to facilitate the wider interoperation of simple enriched text across a wide variety of hardware and software platforms. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1523 RFC1896 INFORMATIONAL INFORMATIONAL RFC1564 DSA Metrics (OSI-DS 34 (v3)) P. Barker R. Hedberg January 1994 ASCII 46205 21 x.500 Directory Service Agent This document defines a set of criteria by which a DSA implementation may be judged. Particular issues covered include conformance to standards; performance; demonstrated interoperability. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1565 Network Services Monitoring MIB S. Kille N. Freed January 1994 ASCII 29761 17 Management Information Base 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] RFC2248 PROPOSED STANDARD PROPOSED STANDARD RFC1566 Mail Monitoring MIB S. Kille N. Freed January 1994 ASCII 33136 20 Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, 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] RFC2249 RFC2789 PROPOSED STANDARD PROPOSED STANDARD RFC1567 X.500 Directory Monitoring MIB G. Mansfield S. Kille January 1994 ASCII 33527 18 X500-MIB Management Information Base This document defines a portion of the Management Information Base (MIB). It defines the MIB for monitoring Directory System Agents (DSA), a component of the OSI Directory. This MIB will be used in conjunction with the APPLICATION-MIB for monitoring DSAs. [STANDARDS-TRACK] RFC2605 PROPOSED STANDARD PROPOSED STANDARD RFC1568 Simple Network Paging Protocol - Version 1(b) A. Gwinn January 1994 ASCII 16558 8 Beeper This RFC suggests a simple way for delivering both alphanumeric and numeric pages (one-way) to radio paging terminals. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1645 INFORMATIONAL INFORMATIONAL RFC1569 Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures M. Rose January 1994 ASCII 12597 6 Beeper 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. RFC1703 INFORMATIONAL INFORMATIONAL RFC1570 PPP LCP Extensions W. Simpson Editor January 1994 ASCII 35719 19 PPP-LCP Point-to Point Link Control Protocol serial line The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection. This document defines several additional LCP features which have been suggested over the past few years. [STANDARDS-TRACK] RFC1548 RFC2484 PROPOSED STANDARD PROPOSED STANDARD RFC1571 Telnet Environment Option Interoperability Issues D. Borman January 1994 ASCII 8117 4 This document describes a method for allowing implementors to ensure that their implementation of the Environment option will be interoperable with as many other implementations as possible, by providing a set of heuristics that can be used to help identify which definitions for VAR and VALUE are being used by the other side of the connection. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1408 INFORMATIONAL INFORMATIONAL RFC1572 Telnet Environment Option S. Alexander Editor January 1994 ASCII 14676 7 TOPT-ENVIR This document specifies a mechanism for passing environment information between a telnet client and server. Use of this mechanism enables a telnet user to propagate configuration information to a remote host when connecting. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1573 Evolution of the Interfaces Group of MIB-II K. McCloghrie F. Kastenholz January 1994 ASCII 123057 55 Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing Network Interfaces. [STANARDS-TRACK] RFC1229 RFC2233 PROPOSED STANDARD PROPOSED STANDARD RFC1574 Essential Tools for the OSI Internet S. Hares C. Wittbrodt February 1994 ASCII 27735 13 Echo Traceroute Routing Table CLNP This document specifies the following three necessary tools to debug problems in the deployment and maintenance of networks using ISO 8473 (CLNP): ping or OSI Echo function, traceroute function which uses the OSI Echo function, and routing table dump function. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1139 INFORMATIONAL INFORMATIONAL RFC1575 An Echo Function for CLNP (ISO 8473) S. Hares C. Wittbrodt February 1994 ASCII 22479 9 ISO-TS-ECHO This memo defines an echo function for the connection-less network layer protocol. The mechanism that is mandated here is in the final process of being standardized by ISO as "Amendment X: Addition of an Echo function to ISO 8473" an integral part of Version 2 of ISO 8473. [STANDARDS-TRACK] RFC1139 DRAFT STANDARD DRAFT STANDARD RFC1576 TN3270 Current Practices J. Penner January 1994 ASCII 24477 12 Telnet Option Terminal Type EOR Binary This document describes the existing implementation of transferring 3270 display terminal data using currently available telnet capabilities. The name traditionally associated with this implementation is TN3270. This memo provides information for the Internet community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1577 Classical IP and ARP over ATM M. Laubach January 1994 ASCII 41239 17 Internet Protocol Address Resolution Asynchronous Transmission Mode This memo defines an initial application of classical IP and ARP in an Asynchronous Transfer Mode (ATM) network environment configured as a Logical IP Subnetwork (LIS). [STANDARDS-TRACK] RFC2225 PROPOSED STANDARD PROPOSED STANDARD RFC1578 FYI on Questions and Answers - Answers to Commonly Asked "Primary and Secondary School Internet User" Questions J. Sellers February 1994 ASCII 113646 53 K12 The goal of this FYI RFC is to document the questions most commonly asked about the Internet by those in the primary and secondary school community, and to provide pointers to sources which answer those questions. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. [FYI 22] RFC1941 INFORMATIONAL INFORMATIONAL RFC1579 Firewall-Friendly FTP S. Bellovin February 1994 ASCII 8806 4 file transfer PORT PASV Security This memo describes a suggested change to the behavior of FTP client programs. This document provides information for the Internet community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1580 Guide to Network Resource Tools EARN Staff March 1994 ASCII 235112 107 EARN BITNET Gopher World-Wide Web WWW WAIS Archie Whois X.500 Netfind Trickle BIFTP Listserv Netnews Astra NetServ Mail Base Prospero IRC Relay The purpose of this guide is to supply the basic information that anyone on the network needs to try out and begin using tools. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. [FYI 23] FYI0023 INFORMATIONAL INFORMATIONAL RFC1581 Protocol Analysis for Extensions to RIP to Support Demand Circuits G. Meyer February 1994 ASCII 7536 4 routing Protocol As required by Routing Protocol Criteria, this report documents the key features of Routing over Demand Circuits on Wide Area Networks - RIP and the current implementation experience. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1582 Extensions to RIP to Support Demand Circuits G. Meyer February 1994 ASCII 63271 29 RIP-DC routing Protocol This memo defines a generalized modification which can be applied to Bellman-Ford (or distance vector) algorithm information broadcasting protocols. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1583 OSPF Version 2 J. Moy March 1994 ASCII 532636 216 PS 990794 PDF 465711 equal-cost multipath link state LSA This memo documents version 2 of the OSPF protocol. OSPF is a link- state routing protocol. [STANDARDS-TRACK] RFC1247 RFC2178 DRAFT STANDARD DRAFT STANDARD RFC1584 Multicast Extensions to OSPF J. Moy March 1994 ASCII 262463 102 PS 426358 PDF 243185 OSPF-Multi Open Shortest Path First This memo documents enhancements to the OSPF protocol enabling the routing of IP multicast datagrams. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1585 MOSPF: Analysis and Experience J. Moy March 1994 ASCII 29754 13 Multicast Open Shortest Path First OSPF This memo documents how the MOSPF protocol satisfies the requirements imposed on Internet routing protocols by "Internet Engineering Task Force internet routing protocol standardization criteria" ([RFC 1264]). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1586 Guidelines for Running OSPF Over Frame Relay Networks O. deSouza M. Rodrigues March 1994 ASCII 14968 6 FR Open Shortest Path First This memo specifies guidelines for implementors and users of the Open Shortest Path First (OSPF) routing protocol to bring about improvements in how the protocol runs over frame relay networks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1587 The OSPF NSSA Option R. Coltun V. Fuller March 1994 ASCII 37412 17 OSPF-NSSA Open Shortest Path First not so stubby area routing protocol 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] RFC3101 PROPOSED STANDARD PROPOSED STANDARD RFC1588 White Pages Meeting Report J. Postel C. Anderson February 1994 ASCII 77945 35 X-500 directory This report describes the results of a meeting held at the November IETF (Internet Engineering Task Force) in Houston, TX, on November 2, 1993, to discuss the future of and approaches to a white pages directory services for the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1589 A Kernel Model for Precision Timekeeping D. Mills March 1994 ASCII 88129 37 Time NTP Clock This memorandum describes an engineering model which implements a precision time-of-day function for a generic operating system. The model is based on the principles of disciplined oscillators and phase-lock loops (PLL) often found in the engineering literature. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1590 Media Type Registration Procedure J. Postel March 1994 ASCII 13044 7 email multimedia Several questions have been raised about the requirements and administrative procedure for registering MIME content-type and subtypes, and the use of these Media Types for other applications. This document addresses these issues and specifies a procedure for the registration of new Media Types (content-type/subtypes). It also generalizes the scope of use of these Media Types to make it appropriate to use the same registrations and specifications with other applications. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC2045 RFC2046 RFC2047 RFC2048 RFC2049 RFC1521 INFORMATIONAL INFORMATIONAL RFC1591 Domain Name System Structure and Delegation J. Postel March 1994 ASCII 16481 7 DNS Policy Top-Level TLD This memo provides some information on the structure of the names in the Domain Name System (DNS), specifically the top-level domain names; and on the administration of domains. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1592 Simple Network Management Protocol Distributed Protocol Interface Version 2.0 B. Wijnen G. Carpenter K. Curran A. Sehgal G. Waters March 1994 ASCII 135259 54 SNMP-DPI SNMP DPT IBM This RFC describes version 2.0 of a protocol that International Business Machines Corporation (IBM) has been implementing in most of its SNMP agents to allow dynamic extension of supported MIBs. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. RFC1228 EXPERIMENTAL EXPERIMENTAL RFC1593 SNA APPN Node MIB W. McKenzie J. Cheng March 1994 ASCII 207882 120 IBM Management This RFC describes IBM's SNMP support for SNA Advanced Peer-to-Peer Networking (APPN) nodes. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1594 FYI on Questions and Answers - Answers to Commonly asked "New Internet User" Questions A. Marine J. Reynolds G. Malkin March 1994 ASCII 98753 44 documentation help information FAQ This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. [FYI 4] RFC1325 RFC2664 INFORMATIONAL INFORMATIONAL RFC1595 Definitions of Managed Objects for the SONET/SDH Interface Type T. Brown K. Tesink March 1994 ASCII 121937 59 SONET-MIB MIB Management SNMP RFC2558 PROPOSED STANDARD PROPOSED STANDARD RFC1596 Definitions of Managed Objects for Frame Relay Service T. Brown Editor March 1994 ASCII 88795 46 FR MIB Management SNMP RFC1604 PROPOSED STANDARD PROPOSED STANDARD RFC1597 Address Allocation for Private Internets Y. Rekhter B. Moskowitz D. Karrenberg G. de Groot March 1994 ASCII 17430 8 IP Network Number Local 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. RFC1918 INFORMATIONAL INFORMATIONAL RFC1598 PPP in X.25 W. Simpson March 1994 ASCII 13835 8 PPP-X25 point The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. This document describes the use of X.25 for framing PPP encapsulated packets. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1599 Summary of 1500-1599 M. Kennedy January 1997 ASCII 43761 22 Index INFORMATIONAL INFORMATIONAL RFC1600 Internet Official Protocol Standards J. Postel March 1994 ASCII 80958 36 status procedure index This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK] RFC1540 RFC1610 HISTORIC STANDARD RFC1601 Charter of the Internet Architecture Board (IAB) C. Huitema March 1994 ASCII 12424 6 ISOC Internet Society IETF IRTF This memo documents the composition, selection, roles, and organization of the Internet Architecture Board and its subsidiary organizations. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1358 RFC2850 INFORMATIONAL INFORMATIONAL RFC1602 The Internet Standards Process -- Revision 2 Internet Architecture Board Internet Engineering Steering Group March 1994 ASCII 88465 37 This document is a revision of RFC 1310, which defined the official procedures for creating and documenting Internet Standards. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1310 RFC2026 RFC1871 INFORMATIONAL INFORMATIONAL RFC1603 IETF Working Group Guidelines and Procedures E. Huizer D. Crocker March 1994 ASCII 63900 29 WG This document describes the guidelines and procedures for formation and operation of IETF working groups. It describes the formal relationship between IETF participants WG and the Internet Engineering Steering Group (IESG). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC2418 RFC1871 INFORMATIONAL INFORMATIONAL RFC1604 Definitions of Managed Objects for Frame Relay Service T. Brown Editor March 1994 ASCII 88770 46 FR-MIB MIB Management SNMP Network This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Frame Relay Service. [STANDARDS-TRACK] RFC1596 RFC2954 PROPOSED STANDARD PROPOSED STANDARD RFC1605 SONET to Sonnet Translation W. Shakespeare April 01 1994 ASCII 4451 3 Humor Because Synchronous Optical Network (SONET) transmits data in frames of bytes, it is fairly easy to envision ways to compress SONET frames to yield higher bandwidth over a given fiber optic link. This memo describes a particular method, SONET Over Novel English Translation (SONNET). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1606 A Historical Perspective On The Usage Of IP Version 9 J. Onions April 01 1994 ASCII 8398 4 Humor This paper reviews the usages of the old IP version protocol. It considers some of its successes and its failures. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1607 A VIEW FROM THE 21ST CENTURY V. Cerf April 01 1994 ASCII 28165 14 V. Cerf This document is a composition of letters discussing a possible future. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1608 Representing IP Information in the X.500 Directory T. Johannsen G. Mansfield M. Kosters S. Sataluri March 1994 ASCII 40269 20 X500-DIR Data Structure Schemo This document describes the objects necessary to include information about IP networks and IP numbers in the X.500 Directory. It extends the work "Charting networks in the X.500 Directory" [1] where a general framework is presented for representing networks in the Directory by applying it to IP networks. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1609 Charting Networks in the X.500 Directory G. Mansfield T. Johannsen M. Knopper March 1994 ASCII 30044 15 X500-CHART Data Structure Schemo This document presents a model in which a communication network with all its related details and descriptions can be represented in the X.500 Directory. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1610 Internet Official Protocol Standards J. Postel July 1994 ASCII 81346 36 status procedure index This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK] RFC1600 RFC1720 HISTORIC STANDARD RFC1611 DNS Server MIB Extensions R. Austein J. Saperia May 1994 ASCII 58700 30 DNS-S-MIB Domain Name System Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a set of extensions which instrument DNS name server functions. This memo was produced by the DNS working group. [STANDARDS-TRACK] HISTORIC PROPOSED STANDARD RFC1612 DNS Resolver MIB Extensions R. Austein J. Saperia May 1994 ASCII 61382 32 DNS-R-MIB Domain Name System Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a set of extensions which instrument DNS resolver functions. This memo was produced by the DNS working group. [STANDARDS-TRACK] HISTORIC PROPOSED STANDARD RFC1613 cisco Systems X.25 over TCP (XOT) J. Forster G. Satz G. Glick R. Day May 1994 ASCII 29267 13 Transmission Control Protocol This memo documents a method of sending X.25 packets over IP internets by encapsulating the X.25 Packet Level in TCP packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1614 Network Access to Multimedia Information C. Adie May 1994 ASCII 187253 79 RARE Technical Report This report summarises the requirements of research and academic network users for network access to multimedia information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1615 Migrating from X.400(84) to X.400(88) J. Houttuin J. Craigie May 1994 ASCII 39693 17 RARE Technical Report email This document compares X.400(88) to X.400(84) and describes what problems can be anticipated in the migration, especially considering the migration from the existing X.400(84) infrastructure created by the COSINE MHS project to an X.400(88) infrastructure. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1616 X.400(1988) for the Academic and Research Community in Europe RARE WG-MSG Task Force 88 E. Huizer J. Romaguera Editors May 1994 ASCII 107432 44 RARE Technical Report email The report documents the results of a task force on X.400(1988) deployment of the RARE Mails and Messaging Work Group during the period from November 1992 until October 1993. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1617 Naming and Structuring Guidelines for X.500 Directory Pilots P. Barker S. Kille T. Lenggenhager May 1994 ASCII 56739 28 RARE Technical Report White Pages This document defines a number of naming and structuring guidelines focused on White Pages usage. Alignment to these guidelines is recommended for directory pilots. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1384 INFORMATIONAL INFORMATIONAL RFC1618 PPP over ISDN W. Simpson May 1994 ASCII 14896 7 PPP-ISDN Point Integrated Services Digital Network This document describes the use of PPP over Integrated Services Digital Network (ISDN) switched circuits. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1619 PPP over SONET/SDH W. Simpson May 1994 ASCII 8893 5 PPP-SONET Point Synchronous Optical Network Digital Heirarchy This document describes the use of PPP over Synchronous Optical Network (SONET) and Synchronous Digital Heirarchy (SDH) circuits. [STANDARDS- TRACK] RFC2615 PROPOSED STANDARD PROPOSED STANDARD RFC1620 Internet Architecture Extensions for Shared Media B. Braden J. Postel Y. Rekhter May 1994 ASCII 44999 19 Public data networks ARP address resolution protocol This memo discusses alternative approaches to extending the Internet architecture to eliminate some or all unnecessary hops. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1621 Pip Near-term Architecture P. Francis May 1994 ASCII 128905 51 Internet Protocol IPng The purpose of this RFC and the companion RFC "Pip Header Processing" are to record the ideas (good and bad) of Pip. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1622 Pip Header Processing P. Francis May 1994 ASCII 34837 16 Internet Protocol IPng The purpose of this RFC and the companion RFC "Pip Near-term Architecture" are to record the ideas (good and bad) of Pip. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1623 Definitions of Managed Objects for the Ethernet-like Interface Types F. Kastenholz May 1994 ASCII 38745 19 MIB Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing ethernet-like objects. [STANDARDS-TRACK] RFC1398 RFC1643 HISTORIC STANDARD RFC1624 Computation of the Internet Checksum via Incremental Update A. Rijsinghani Editor May 1994 ASCII 9836 6 This memo describes an updated technique for incremental computation of the standard Internet checksum. It updates the method described in RFC 1141. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1141 INFORMATIONAL INFORMATIONAL RFC1625 WAIS over Z39.50-1988 M. St. Pierre J. Fullton K. Gamiel J. Goldman B. Kahle J. Kunze H. Morris F. Schiettecatte June 1994 ASCII 14694 7 Wide Area Information Servers Library The purpose of this memo is to initiate a discussion for a migration path of the WAIS technology from Z39.50-1988 Information Retrieval Service Definitions and Protocol Specification for Library Applications [1] to Z39.50-1992 [2] and then to Z39.50-1994 [3]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1626 Default IP MTU for use over ATM AAL5 R. Atkinson May 1994 ASCII 11841 5 Maximum Transmission Unit Asynchronous Transfer Mode Adaptation Layer Size Packet 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] RFC2225 PROPOSED STANDARD PROPOSED STANDARD RFC1627 Network 10 Considered Harmful (Some Practices Shouldn't be Codified) E. Lear E. Fair D. Crocker T. Kessler July 1994 ASCII 18823 8 IP Network Number Local 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. RFC1918 INFORMATIONAL INFORMATIONAL RFC1628 UPS Management Information Base J. Case Editor May 1994 ASCII 83439 45 UPS-MIB Uninterruptible Power Supply MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing uninterruptible power supply (UPS) systems. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1629 Guidelines for OSI NSAP Allocation in the Internet R. Colella R. Callon E. Gardner Y. Rekhter May 1994 ASCII 131640 52 OSI-NSAP CLNP Address This paper provides guidelines for allocating NSAP addresses in the Internet. The guidelines provided in this paper have been the basis for initial deployment of CLNP in the Internet, and have proven very valuable both as an aid to scaling of CLNP routing, and for address administration. [STANDARDS-TRACK] RFC1237 DRAFT STANDARD DRAFT STANDARD RFC1630 Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web T. Berners-Lee June 1994 ASCII 57601 28 World Wide Web URI This document defines the syntax used by the World-Wide Web initiative to encode the names and addresses of objects on the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1631 The IP Network Address Translator (NAT) K. Egevang P. Francis May 1994 ASCII 22714 10 Internet Protocol This memo proposes another short-term solution, address reuse, that complements CIDR or even makes it unnecessary. The address reuse solution is to place Network Address Translators (NAT) at the borders of stub domains. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC3022 INFORMATIONAL INFORMATIONAL RFC1632 A Revised Catalog of Available X.500 Implementations A. Getchell S. Sataluri Editors May 1994 ASCII 124111 94 Directory White Pages This document is the result of a survey that gathered new or updated descriptions of currently available implementations of X.500, including commercial products and openly available offerings. This document is a revision of RFC 1292. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1292 RFC2116 INFORMATIONAL INFORMATIONAL RFC1633 Integrated Services in the Internet Architecture: an Overview R. Braden D. Clark S. Shenker June 1994 ASCII 89691 33 PS 207016 PDF 201858 real time Multi-media reservations Protocol This memo discusses a proposed extension to the Internet architecture and protocols to provide integrated services, i.e., to support real-time as well as the current non-real-time service of IP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1634 Novell IPX Over Various WAN Media (IPXWAN) M. Allen May 1994 ASCII 55347 23 wide area network This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocol Novell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1551 RFC1362 INFORMATIONAL INFORMATIONAL RFC1635 How to Use Anonymous FTP P. Deutsch A. Emtage A. Marine May 1994 ASCII 27258 13 File Transfer Protocol This document provides information for the novice Internet user about using the File Transfer Protocol (FTP). It explains what FTP is, what anonymous FTP is, and what an anonymous FTP archive site is. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. FYI0024 INFORMATIONAL INFORMATIONAL RFC1636 Report of IAB Workshop on Security in the Internet Architecture - February 8-10, 1994 R. Braden D. Clark S. Crocker C. Huitema June 1994 ASCII 130761 52 Internet Architecture Board This document is a report on an Internet architecture workshop, initiated by the IAB and held at USC Information Sciences Institute on February 8-10, 1994. This workshop generally focused on security issues in the Internet architecture. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1637 DNS NSAP Resource Records B. Manning R. Colella June 1994 ASCII 21768 11 domain Name System ISO OSI Address This document defines the format of one new Resource Record (RR) for the DNS for domain name-to-NSAP mapping. This memo defines an Experimental Protocol for the Internet community. RFC1348 RFC1706 EXPERIMENTAL EXPERIMENTAL RFC1638 PPP Bridging Control Protocol (BCP) F. Baker R. Bowen June 1994 ASCII 58477 28 PPP-BCP Point to Point This document defines the Network Control Protocol for establishing and configuring Remote Bridging for PPP links. [STANDARDS-TRACK] RFC1220 RFC2878 PROPOSED STANDARD PROPOSED STANDARD RFC1639 FTP Operation Over Big Address Records (FOOBAR) D. Piscitello June 1994 ASCII 10055 5 FOOBAR File Transfer Port This RFC specifies a method for assigning addresses other than 32-bit IPv4 addresses to data ports through the specification of a "long Port (LPRT)" command and "Long Passive (LPSV)" reply, each having as its argument a <long-host-port>, which allows for additional address families, variable length network addresses and variable length port numbers. This memo defines an Experimental Protocol for the Internet community. RFC1545 EXPERIMENTAL EXPERIMENTAL RFC1640 The Process for Organization of Internet Standards Working Group (POISED) S. Crocker June 1994 ASCII 21780 10 IETF IESG IAB ISOC This report, originally prepared in January 1993 provides a summary of the POISED WG, starting from the events leading to the formation of the WG to the end of 1992. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1641 Using Unicode with MIME D. Goldsmith M. Davis July 1994 ASCII 11258 6 PS 20451 PDF 11658 MIME-UNI Multipurpose Internet Mail Extension Character Set This document specifies the usage of Unicode within MIME. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1642 UTF-7 - A Mail-Safe Transformation Format of Unicode D. Goldsmith M. Davis July 1994 ASCII 27770 14 PS 50907 PDF 29573 character Set This document describes a new transformation format of Unicode that contains only 7-bit ASCII characters and is intended to be readable by humans in the limiting case that the document consists of characters from the US-ASCII repertoire. This memo defines an Experimental Protocol for the Internet community. RFC2152 EXPERIMENTAL EXPERIMENTAL RFC1643 Definitions of Managed Objects for the Ethernet-like Interface Types F. Kastenholz July 1994 ASCII 39008 19 ETHER-MIB MIB Network Management SNMP Ethernet 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] RFC1623 RFC3638 STD0050 HISTORIC STANDARD RFC1644 T/TCP -- TCP Extensions for Transactions Functional Specification R. Braden July 1994 ASCII 87362 38 T/TCP Transmission Control Protocol This memo specifies T/TCP, an experimental TCP extension for efficient transaction-oriented (request/response) service. This memo describes an Experimental Protocol for the Internet community. RFC1379 EXPERIMENTAL EXPERIMENTAL RFC1645 Simple Network Paging Protocol - Version 2 A. Gwinn July 1994 ASCII 31243 15 Beeper SNPP Mail This RFC suggests a simple way for delivering both alphanumeric and numeric pages (one-way) to radio paging terminals. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1568 RFC1861 INFORMATIONAL INFORMATIONAL RFC1646 TN3270 Extensions for LUname and Printer Selection C. Graves T. Butts M. Angel July 1994 ASCII 27564 13 Telnet Option This document describes protocol extensions to TN3270. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1647 TN3270 Enhancements B. Kelly July 1994 ASCII 84420 34 Telnet Option This document describes a protocol that more fully supports 3270 devices than do the existing tn3270 practices. [STANDARDS-TRACK] RFC2355 PROPOSED STANDARD PROPOSED STANDARD RFC1648 Postmaster Convention for X.400 Operations A. Cargille July 1994 ASCII 8761 4 Mail This paper extends this concept to X.400 mail domains which have registered RFC 1327 mapping rules, and which therefore appear to have normal RFC822-style addresses. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1649 Operational Requirements for X.400 Management Domains in the GO-MHS Community R. Hagens A. Hansen July 1994 ASCII 28138 14 Mail Global Open Message Handling System The goal of this document is to unite regionally operated X.400 services on the various continents into one GO-MHS Community (as seen from an end-user's point of view). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1650 Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2 F. Kastenholz August 1994 ASCII 40484 20 MIB Management Information Base 802.3 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] RFC2358 PROPOSED STANDARD PROPOSED STANDARD RFC1651 SMTP Service Extensions J. Klensin N. Freed M. Rose E. Stefferud D. Crocker July 1994 ASCII 22153 11 Mail Simple Transfer 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] RFC1425 RFC1869 DRAFT STANDARD DRAFT STANDARD RFC1652 SMTP Service Extension for 8bit-MIMEtransport J. Klensin N. Freed M. Rose E. Stefferud D. Crocker July 1994 ASCII 11842 6 SMTP Mail Simple Transfer This memo defines an extension to the SMTP service whereby an SMTP content body consisting of text containing octets outside of the US- ASCII octet range (hex 00-7F) may be relayed using SMTP. [STANDARDS- TRACK] RFC1426 DRAFT STANDARD DRAFT STANDARD RFC1653 SMTP Service Extension for Message Size Declaration J. Klensin N. Freed K. Moore July 1994 ASCII 17883 8 Mail Simple Transfer Protocol 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] RFC1427 RFC1870 DRAFT STANDARD DRAFT STANDARD RFC1654 A Border Gateway Protocol 4 (BGP-4) Y. Rekhter T. Li Editors July 1994 ASCII 130118 56 routing This document defines an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK] RFC1771 PROPOSED STANDARD PROPOSED STANDARD RFC1655 Application of the Border Gateway Protocol in the Internet Y. Rekhter P. Gross Editors July 1994 ASCII 43664 19 BGP-4 Routing This document, together with its companion document, "A Border Gateway Protocol 4 (BGP-4)", define an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK] RFC1268 RFC1772 PROPOSED STANDARD PROPOSED STANDARD RFC1656 BGP-4 Protocol Document Roadmap and Implementation Experience P. Traina July 1994 ASCII 7705 4 Border Gateway Protocol Routing 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. RFC1773 INFORMATIONAL PROPOSED STANDARD RFC1657 Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 S. Willis J. Burruss J. Chu Editor July 1994 ASCII 45505 21 BGP-4-MIB MIB Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing the Border Gateway Protocol Version 4 or lower [1, 2]. [STANDARDS-TRACK] DRAFT STANDARD DRAFT STANDARD RFC1658 Definitions of Managed Objects for Character Stream Devices using SMIv2 B. Stewart July 1994 ASCII 32579 18 MIB Network Management Base This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for the management of character stream devices. [STANDARDS-TRACK] RFC1316 DRAFT STANDARD DRAFT STANDARD RFC1659 Definitions of Managed Objects for RS-232-like Hardware Devices using SMIv2 B. Stewart July 1994 ASCII 36479 21 MIB Network Management Base This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for the management of RS-232-like devices. [STANDARDS-TRACK] RFC1317 DRAFT STANDARD DRAFT STANDARD RFC1660 Definitions of Managed Objects for Parallel-printer-like Hardware Devices using SMIv2 B. Stewart July 1994 ASCII 16784 10 MIB Network Management Base This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for the management of Parallel-printer- like devices. [STANDARDS-TRACK] RFC1318 DRAFT STANDARD DRAFT STANDARD RFC1661 The Point-to-Point Protocol (PPP) W. Simpson Editor July 1994 ASCII 103026 53 PPP Specification Standard link serial line This document defines the PPP organization and methodology, and the PPP encapsulation, together with an extensible option negotiation mechanism which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. [STANDARDS-TRACK] RFC1548 RFC2153 STD0051 STANDARD STANDARD RFC1662 PPP in HDLC-like Framing W. Simpson Editor July 1994 ASCII 48058 26 PPP-HDLC Point Protocol Specification Standard link serial line This document describes the use of HDLC-like framing for PPP encapsulated packets. [STANDARDS-TRACK] RFC1549 STD0051 STANDARD STANDARD RFC1663 PPP Reliable Transmission D. Rand July 1994 ASCII 17281 8 PPP-TRANS Point Protocol This document defines a method for negotiating and using Numbered-Mode, as defined by ISO 7776 [2], to provide a reliable serial link. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1664 Using the Internet DNS to Distribute RFC1327 Mail Address Mapping Tables C. Allocchio A. Bonito B. Cole S. Giordano R. Hagens August 1994 ASCII 50783 23 domain Name System X.400 Email This memo defines how to store in the Internet Domain Name System the mapping information needed by e-mail gateways and other tools to map RFC822 domain names into X.400 O/R names and vice versa. This memo defines an Experimental Protocol for the Internet community. RFC2163 EXPERIMENTAL EXPERIMENTAL RFC1665 Definitions of Managed Objects for SNA NAUs using SMIv2 Z. Kielczewski D. Kostick K. Shih Editors July 1994 ASCII 133381 67 MIB Management Information Base System Network Architecture Addressable Units 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] RFC1666 PROPOSED STANDARD PROPOSED STANDARD RFC1666 Definitions of Managed Objects for SNA NAUs using SMIv2 Z. Kielczewski D. Kostick K. Shih Editors August 1994 ASCII 134385 68 SNANAU-MIB Network Management SNMP MIB Protocol Units Architecture Addressable Information System 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] RFC1665 PROPOSED STANDARD PROPOSED STANDARD RFC1667 Modeling and Simulation Requirements for IPng S. Symington D. Wood M. Pullen August 1994 ASCII 17291 7 White Paper This white paper summarizes the Distributed Interactive Simulation environment that is under development, with regard to its real-time nature, scope and magnitude of networking requirements. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1668 Unified Routing Requirements for IPng D. Estrin T. Li Y. Rekhter August 1994 ASCII 5106 3 White Paper The document provides requirements on the IPng from the perspective of the Unified Routing Architecture, as described in RFC 1322. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1669 Market Viability as a IPng Criteria J. Curran August 1994 ASCII 8099 4 White Paper "Viability in the Marketplace" is an important requirement for any IPng candidate and this paper is an attempt to summarize some important factors in determing market viability of IPng proposals. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1670 Input to IPng Engineering Considerations D. Heagerty August 1994 ASCII 5350 3 White Paper This white paper expresses some personal opinions on IPng engineering considerations, based on experience with DECnet Phase V transition. It suggests breaking down the IPng decisions and transition tasks into smaller parts so they can be tackled early by the relevant experts. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1671 IPng White Paper on Transition and Other Considerations B. Carpenter August 1994 ASCII 17631 8 This white paper outlines some general requirements for IPng in selected areas. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1672 Accounting Requirements for IPng N. Brownlee August 1994 ASCII 6185 3 White Paper This white paper discusses accounting requirements for IPng. It recommends that all IPng packets carry accounting tags, which would vary in size. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1673 Electric Power Research Institute Comments on IPng R. Skelton August 1994 ASCII 7476 4 White Paper This document was submitted to the IETF IPng area in response to RFC 1550. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1674 A Cellular Industry View of IPng M. Taylor August 1994 ASCII 6157 3 White Paper This is a draft of the requirements for IPng as envisioned by representatives of the Cellular Digital Packet Data (CDPD) consortium of service providers. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1675 Security Concerns for IPng S. Bellovin August 1994 ASCII 8290 4 White Paper A number of the candidates for IPng have some features that are somewhat worrisome from a security perspective. While it is not necessary that IPng be an improvement over IPv4, it is mandatory that it not make things worse. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1676 INFN Requirements for an IPng A. Ghiselli D. Salomoni C. Vistoli August 1994 ASCII 8493 4 White Paper With this paper we would like to emphasize the key points that we would to consider if charged with IPng plan. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1677 Tactical Radio Frequency Communication Requirements for IPng B. Adamson August 1994 ASCII 24065 9 White Paper This paper describes requirements for Internet Protocol next generation (IPng) candidates with respect to their application to military tactical radio frequency (RF) communication networks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1678 IPng Requirements of Large Corporate Networks E. Britton J. Tavs August 1994 ASCII 18650 8 White Paper This draft summarizes some of the requirements of large corporate networks for the next generation of the Internet protcol suite. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1679 HPN Working Group Input to the IPng Requirements Solicitation D. Green P. Irey D. Marlow K. O'Donoghue August 1994 ASCII 22974 10 White Paper The purpose of this document is to provide what the HPN working group perceives as requirements for an IPng protocol set. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1680 IPng Support for ATM Services C. Brazdziunas August 1994 ASCII 17846 7 White Paper This white paper describes engineering considerations for IPng as solicited by RFC 1550 [1]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1681 On Many Addresses per Host S. Bellovin August 1994 ASCII 11964 5 White Paper This document was submitted to the IETF IPng area in response to RFC 1550.This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1682 IPng BSD Host Implementation Analysis J. Bound August 1994 ASCII 22295 10 White Paper Unix This IPng white paper, IPng BSD Host Implementation Analysis, was submitted to the IPng Directorate to provide a BSD host point of reference to assist with the engineering considerations during the IETF process to select an IPng proposal. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1683 Multiprotocol Interoperability In IPng R. Clark M. Ammar K. Calvert August 1994 ASCII 28201 12 White Paper In this document, we identify several features that affect a protocol's ability to operate in a multiprotocol environment and propose the incorporation of these features into IPng. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1684 Introduction to White Pages Services based on X.500 P. Jurg August 1994 ASCII 22985 10 Directory The document provides an introduction to the international ITU-T (formerly CCITT) X.500 and ISO 9594 standard, which is particularly suited for providing an integrated local and global electronic White Pages Service. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1685 Writing X.400 O/R Names H. Alvestrand August 1994 ASCII 21242 11 EMail Mail There is a need for human beings who use X.400 systems to be able to write down O/R names in a uniform way. This memo is a discussion of this topic. This memo provides information for the Internet Community. It does not specify an Internet Standard of any kind. RTR0012 INFORMATIONAL INFORMATIONAL RFC1686 IPng Requirements: A Cable Television Industry Viewpoint M. Vecchi August 1994 ASCII 39052 14 White Paper This paper provides comments on topics related to the IPng requirements and selection criteria from a cable television industry viewpoint. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1687 A Large Corporate User's View of IPng E. Fleischman August 1994 ASCII 34120 13 White Paper The goal of this paper is to examine the implications of IPng from the point of view of Fortune 100 corporations which have heavily invested in TCP/IP technology in order to achieve their (non-computer related) business goals.This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1688 IPng Mobility Considerations W. Simpson August 1994 ASCII 19151 9 White Paper This RFC specifies criteria related to mobility for consideration in design and selection of the Next Generation of IP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1689 A Status Report on Networked Information Retrieval: Tools and Groups J. Foster Editor August 1994 ASCII 375469 226 NIR The purpose of this report is to increase the awareness of Networked Information Retrieval by bringing together in one place information about the various networked information retrieval tools, their developers, interested organisations, and other activities that relate to the production, dissemination, and support of NIR tools. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. See also RTR0013 FYI0025 INFORMATIONAL INFORMATIONAL RFC1690 Introducing the Internet Engineering and Planning Group (IEPG) G. Huston August 1994 ASCII 3013 2 charter This memo introduces the IEPG to the Internet Community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1691 The Document Architecture for the Cornell Digital Library W. Turner August 1994 ASCII 20438 10 This memo defines an architecture for the storage and retrieval of the digital representations for books, journals, photographic images, etc., which are collected in a large organized digital library. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1692 Transport Multiplexing Protocol (TMux) P. Cameron D. Crocker D. Cohen J. Postel August 1994 ASCII 26163 12 TMUX Internet Protocol IP This RFC documents the extended TACACS protocol use by the Cisco Systems terminal servers. This same protocol is used by the University of Minnesota's distributed authentication system. This memo provides information for the Internet community. It does not specify an Internet standard. PROPOSED STANDARD PROPOSED STANDARD RFC1693 An Extension to TCP : Partial Order Service T. Connolly P. Amer P. Conrad November 1994 ASCII 90100 36 TCP-POS Transmission Control Protocol This RFC introduces a new transport mechanism for TCP based upon partial ordering. The aim is to present the concepts of partial ordering and promote discussions on its usefulness in network communications. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1694 Definitions of Managed Objects for SMDS Interfaces using SMIv2 T. Brown K. Tesink Editors August 1994 ASCII 70856 35 SIP-MIB Standard,MIB,Network,Management,Switched,Multimegabit,Data,Service,Informatiom,Base,SMDS This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing objects for SMDS access interfaces. [STANDARDS-TRACK] RFC1304 DRAFT STANDARD DRAFT STANDARD RFC1695 Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2 M. Ahmed K. Tesink Editors August 1994 ASCII 175461 73 ATM-MIB MIB Management,Information,Base,Asychronous,Transmission,Mode 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] RFC2515 PROPOSED STANDARD PROPOSED STANDARD RFC1696 Modem Management Information Base (MIB) using SMIv2 J. Barnes L. Brown R. Royston S. Waldbusser August 1994 ASCII 54054 31 MODEM-MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing dial-up modems and similar dial-up devices. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1697 Relational Database Management System (RDBMS) Management Information Base (MIB) using SMIv2 D. Brower Editor B. Purvy A. Daniel M. Sinykin J. Smith August 1994 ASCII 76202 38 RDBMS-MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing relational database (RDBMS) implementations. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1698 Octet Sequences for Upper-Layer OSI to Support Basic Communications Applications P. Furniss October 1994 ASCII 67433 29 Protocol Headers This document states particular octet sequences that comprise the OSI upper-layer protocols (Session, Presentation and ACSE) when used to support applications with "basic communications requirements". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1699 Summary of 1600-1699 J. Elliott January 1997 ASCII 40674 21 Index INFORMATIONAL INFORMATIONAL RFC1700 Assigned Numbers J. Reynolds J. Postel October 1994 ASCII 458860 230 status procedure index parameters registered allocated 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. RFC1340 RFC3232 STD0002 HISTORIC STANDARD RFC1701 Generic Routing Encapsulation (GRE) S. Hanks T. Li D. Farinacci P. Traina October 1994 ASCII 15460 8 GRE Internet Protocol IP This document specifies a protocol for performing encapsulation of an arbitrary network layer protocol over another arbitrary network layer protocol. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1702 Generic Routing Encapsulation over IPv4 networks S. Hanks T. Li D. Farinacci P. Traina October 1994 ASCII 7288 4 GRE-IPv4 Internet Protocol IP This memo addresses the case of using IP as the delivery protocol or the payload protocol and the special case of IP as both the delivery and payload. This memo also describes using IP addresses and autonomous system numbers as part of a GRE source route. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1703 Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures M. Rose October 1994 ASCII 17985 9 RADIO-PAGE Beepers 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. RFC1569 INFORMATIONAL INFORMATIONAL RFC1704 On Internet Authentication N. Haller R. Atkinson October 1994 ASCII 42269 17 Security Energyption Policy Guidelines This document describes a spectrum of authentication technologies and provides suggestions to protocol developers on what kinds of authentication might be suitable for some kinds of protocols and applications used in the Internet. This document provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1705 Six Virtual Inches to the Left: The Problem with IPng R. Carlson D. Ficarella October 1994 ASCII 65222 27 IPng White paper This document was submitted to the IETF IPng area in response to RFC 1550. This RFC suggests that a new version of TCP (TCPng), and UDP, be developed and deployed. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1706 DNS NSAP Resource Records B. Manning R. Colella October 1994 ASCII 19721 10 DNS-NSAP Domain Name System ISO OSI Address RR Record Resource This document defines the format of one new Resource Record (RR) for the DNS for domain name-to-NSAP mapping. The RR may be used with any NSAP address format. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1637 INFORMATIONAL INFORMATIONAL RFC1707 CATNIP: Common Architecture for the Internet M. McGovern R. Ullmann October 1994 ASCII 37568 16 IPng White Paper IPv7 This document was submitted to the IETF IPng area in response to RFC 1550. This paper describes a common architecture for the network layer protocol. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1708 NTP PICS PROFORMA - For the Network Time Protocol Version 3 D. Gowin October 1994 ASCII 26523 13 This RFC describes a PICS Proforma translated into an Internet acceptable form. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1709 K-12 Internetworking Guidelines J. Gargano D. Wasley November 1994 ASCII 66659 26 PS 662030 PDF 134065 school network education connection The K-12 community traditionally has not had this level of staffing available for telecommunications planning. This document is intended to bridge that gap and provides a recommended technical direction, an introduction to the role the Internet now plays in K-12 education and technical guidelines for building a campus data communications infrastructure that provides internetworking services and connections to the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. FYI0026 INFORMATIONAL INFORMATIONAL RFC1710 Simple Internet Protocol Plus White Paper R. Hinden October 1994 ASCII 56910 23 SIPP IPng This document was submitted to the IETF IPng area in response to RFC 1550. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1711 Classifications in E-mail Routing J. Houttuin October 1994 ASCII 47584 19 Email Electronic Mail This paper presents a classification for e-mail routing issues. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1712 DNS Encoding of Geographical Location C. Farrell M. Schulze S. Pleitner D. Baldoni November 1994 ASCII 13237 7 DNS-ENCODE Domain Names System GPOS This document defines the format of a new Resource Record (RR) for the Domain Naming System (DNS), and reserves a corresponding DNS type mnemonic and numerical code. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. EXPERIMENTAL EXPERIMENTAL RFC1713 Tools for DNS debugging A. Romao November 1994 ASCII 33500 13 Domain Names System Host DNSWalk DOC DDT Checker Although widely used (and most of the times unnoticed), DNS (Domain Name System) is too much overlooked, in the sense that people, especially administrators, tend to ignore possible anomalies as long as applications that need name-to-address mapping continue to work. This document presents some tools available for domain administrators to detect and correct those anomalies. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. FYI0027 INFORMATIONAL INFORMATIONAL RFC1714 Referral Whois Protocol (RWhois) S. Williamson M. Kosters November 1994 ASCII 85395 46 PS 204207 PDF 85556 White Pages Directory This memo describes version 1.0 of the client/server interaction of RWhois. RWhois provides a distributed system for the display of hierarchical information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC2167 INFORMATIONAL INFORMATIONAL RFC1715 The H Ratio for Address Assignment Efficiency C. Huitema November 1994 ASCII 7392 4 IPng White Paper This document was submitted to the IETF IPng area in response to RFC 1550. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC3194 INFORMATIONAL INFORMATIONAL RFC1716 Towards Requirements for IP Routers P. Almquist F. Kastenholz November 1994 ASCII 432330 192 Gateway Internet Protocol 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. RFC1812 INFORMATIONAL INFORMATIONAL RFC1717 The PPP Multilink Protocol (MP) K. Sklower B. Lloyd G. McGregor D. Carr November 1994 ASCII 46264 21 Point This document proposes a method for splitting, recombining and sequencing datagrams across multiple logical data links. [STANDARDS- TRACK] RFC1990 PROPOSED STANDARD PROPOSED STANDARD RFC1718 The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force IETF Secretariat G. Malkin November 1994 ASCII 50458 23 Internet Engineering Task Force Meeting The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This memo provides information for the Internet community. It does not specify an Internet standard. [FYI 17] RFC1539 RFC3160 INFORMATIONAL INFORMATIONAL RFC1719 A Direction for IPng P. Gross December 1994 ASCII 11118 6 IPng White Paper Internet Protocol This RFC specifies criteria related to mobility for consideration in design and selection of the Next Generation of IP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1720 Internet Official Protocol Standards J. Postel November 1994 ASCII 89063 41 status procedure index This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK] RFC1610 RFC1780 HISTORIC STANDARD RFC1721 RIP Version 2 Protocol Analysis G. Malkin November 1994 ASCII 6680 4 RIP-2 As required by Routing Protocol Criteria (RFC 1264), this report documents the key features of the RIP-2 protocol and the current implementation experience. This report is a prerequisite to advancing RIP-2 on the standards track. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1387 INFORMATIONAL INFORMATIONAL RFC1722 RIP Version 2 Protocol Applicability Statement G. Malkin November 1994 ASCII 10236 5 RIP2-APP RIP-2 As required by Routing Protocol Criteria (RFC 1264), this report defines the applicability of the RIP-2 protocol within the Internet. This report is a prerequisite to advancing RIP-2 on the standards track. [STANDARDS-TRACK] STD0057 STANDARD DRAFT STANDARD RFC1723 RIP Version 2 - Carrying Additional Information G. Malkin November 1994 ASCII 18597 9 RIP-2 This document specifies an extension of the Routing Information Protocol (RIP), o expand the amount of useful information carried in RIP messages and to add a measure of security. This memo obsoletes RFC 1388, which specifies an update to the "Routing Information Protocol" STD 34, RFC 1058. [STANDARDS-TRACK] RFC1388 RFC2453 RFC1058 STD0056 STANDARD DRAFT STANDARD RFC1724 RIP Version 2 MIB Extension G. Malkin F. Baker November 1994 ASCII 29645 18 RIP2-MIB RIP-2 Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing RIP Version 2. [STANDARDS- TRACK] RFC1389 DRAFT STANDARD DRAFT STANDARD RFC1725 Post Office Protocol - Version 3 J. Myers M. Rose November 1994 ASCII 35058 18 POP Email Electronic Mail This memo is a revision to RFC 1460, a Draft Standard. [STANDARDS-TRACK] RFC1460 RFC1939 STD0053 STANDARD DRAFT STANDARD RFC1726 Technical Criteria for Choosing IP The Next Generation (IPng) C. Partridge F. Kastenholz December 1994 ASCII 74109 31 IPng White Paper Internet Protocol This RFC specifies criteria related to mobility for consideration in design and selection of the Next Generation of IP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1727 A Vision of an Integrated Internet Information Service C. Weider P. Deutsch December 1994 ASCII 28468 11 Universal Resource Names This paper lays out a vision of how Internet information services might be integrated over the next few years, and discusses in some detail what steps will be needed to achieve this integration. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1728 Resource Transponders C. Weider December 1994 ASCII 12092 6 Universal Resource Names Location System This paper describes an automatic mechanism, the resource transponder, for maintaining resource location information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1729 Using the Z39.50 Information Retrieval Protocol C. Lynch December 1994 ASCII 20927 8 Basic Endcoding Rules ASN1 This memo describes an approach to the implementation of the ANSI/NISO Z39.50-1992 Standard for Information Retrieval in the TCP/IP environment which is currently in wide use by the Z39.50 implementor community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1730 Internet Message Access Protocol - Version 4 M. Crispin December 1994 ASCII 156660 77 IMAP IMAP4 EMail The Internet Message Access Protocol, Version 4 (IMAP4) allows a client to access and manipulate electronic mail messages on a server. IMAP4 permits manipulation of remote message folders, called "mailboxes", in a way that is functionally equivalent to local mailboxes. IMAP4 also provides the capability for an offline client to resynchronize with the server. [STANDARDS-TRACK] RFC2060 RFC2061 PROPOSED STANDARD PROPOSED STANDARD RFC1731 IMAP4 Authentication Mechanisms J. Myers December 1994 ASCII 11433 6 IMAP4-AUTH Internet Message Access Protocol Email The Internet Message Access Protocol, Version 4 [IMAP4] contains the AUTHENTICATE command, for identifying and authenticating a user to an IMAP4 server and for optionally negotiating a protection mechanism for subsequent protocol interactions. This document describes several authentication mechanisms for use by the IMAP4 AUTHENTICATE command. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1732 IMAP4 Compatibility with IMAP2 and IMAP2bis M. Crispin December 1994 ASCII 9276 5 Internet Message Access Protocol Email This is a summary of hints and recommendations to enable an IMAP4 implementation to interoperate with implementations that conform to earlier specifications. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1733 Distributed Electronic Mail Models in IMAP4 M. Crispin December 1994 ASCII 6205 3 Internet Message Access Protocol Email There are three fundamental models of client/server email: offline, online, and disconnected use. IMAP4 can be used in any one of these three models. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1734 POP3 AUTHentication command J. Myers December 1994 ASCII 8499 5 POP3-AUTH Post Office Protocol Email 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] PROPOSED STANDARD PROPOSED STANDARD RFC1735 NBMA Address Resolution Protocol (NARP) J. Heinanen R. Govindan December 1994 ASCII 24485 11 NARP Non-Broadcast Multi Access Address Resolution Protocol This document describes the NBMA Address Resolution Protocol (NARP). NARP can be used by a source terminal (host or router) connected to a Non-Broadcast, Multi-Access link layer (NBMA) network to find out the NBMA addresses of the a destination terminal provided that the destination terminal is connected to the same NBMA network. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. EXPERIMENTAL EXPERIMENTAL RFC1736 Functional Recommendations for Internet Resource Locators J. Kunze February 1995 ASCII 22415 10 Uniform Resource URL This document specifies a minimum set of requirements for Internet resource locators, which convey location and access information for resources. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1737 Functional Requirements for Uniform Resource Names K. Sollins L. Masinter December 1994 ASCII 16337 7 This document specifies a minimum set of requirements for a kind of Internet resource identifier known as Uniform Resource Names (URNs). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1738 Uniform Resource Locators (URL) T. Berners-Lee L. Masinter M. McCahill December 1994 ASCII 51348 25 URL This document specifies a Uniform Resource Locator (URL), the syntax and semantics of formalized information for location and access of resources via the Internet. [STANDARDS-TRACK] RFC1808 RFC2368 RFC2396 RFC3986 PROPOSED STANDARD PROPOSED STANDARD RFC1739 A Primer On Internet and TCP/IP Tools G. Kessler S. Shepard December 1994 ASCII 102676 46 NSlookup PING FINGER TRACEROUTE FTP TELNET WHOIS NICNAME KNOWBOT NETFIND ARCHIE Gopher Email Mailing Lists USENET 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. RFC2151 INFORMATIONAL INFORMATIONAL RFC1740 MIME Encapsulation of Macintosh Files - MacMIME P. Faltstrom D. Crocker E. Fair December 1994 ASCII 31297 16 MacMIME Multipurpose Internet Mail Extensions This memo describes the format to use when sending Apple Macintosh files via MIME [BORE93]. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1741 MIME Content Type for BinHex Encoded Files P. Faltstrom D. Crocker E. Fair December 1994 ASCII 10155 6 BINHEX Multipurpose Internet Mail Extensions This memo describes the format to use when sending BinHex4.0 files via MIME [BORE93]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1742 AppleTalk Management Information Base II S. Waldbusser K. Frisa January 1995 ASCII 168306 84 AT-MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing AppleTalk networks. [STANDARDS-TRACK] RFC1243 PROPOSED STANDARD PROPOSED STANDARD RFC1743 IEEE 802.5 MIB using SMIv2 K. McCloghrie E. Decker December 1994 ASCII 43224 25 Management Information Base SNMP, 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] RFC1231 RFC1748 DRAFT STANDARD DRAFT STANDARD RFC1744 Observations on the Management of the Internet Address Space G. Huston December 1994 ASCII 32411 12 IP Internet Protocol This memo examines some of the issues associated with the current management practices of the Internet IPv4 address space, and examines the potential outcomes of these practices as the unallocated address pool shrinks in size. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1745 BGP4/IDRP for IP---OSPF Interaction K. Varadhan S. Hares Y. Rekhter December 1994 ASCII 43675 19 BGP4/IDRP Internet Inter-Domain Routing Protocol Border Gateway Open Shortest Path First This memo defines the various criteria to be used when designing an Autonomous System Border Router (ASBR) that will run either BGP4 or IDRP for IP with other ASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK] HISTORIC PROPOSED STANDARD RFC1746 Ways to Define User Expectations B. Manning D. Perkins December 1994 ASCII 46164 18 This paper covers basic fundamentals that must be understood when one defines, interprets, or implements methods to control user expectations on or over the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1747 Definitions of Managed Objects for SNA Data Link Control (SDLC) using SMIv2 J. Hilgeman Chair S. Nix A. Bartky W. Clark Editor January 1995 ASCII 147388 67 SDLCSMIv2 This specification defines an extension to the Management Information Base (MIB) for use with SNMP-based network management. In particular, it defines objects for managing the configuration, monitoring and control of data link controls in an SNA environment. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1748 IEEE 802.5 MIB using SMIv2 K. McCloghrie E. Decker December 1994 ASCII 43224 25 802.5-MIB Management Information Base SNMP 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] RFC1743 RFC1231 RFC1749 DRAFT STANDARD DRAFT STANDARD RFC1749 IEEE 802.5 Station Source Routing MIB using SMIv2 K. McCloghrie F. Baker E. Decker December 1994 ASCII 17563 10 802.5-SSR Management Information Base SNMP This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used by IEEE 802.5 end-stations for managing source routes on a Token Ring network where IEEE source- routing is in use. [STANDARDS-TRACK] RFC1748 PROPOSED STANDARD PROPOSED STANDARD RFC1750 Randomness Recommendations for Security D. Eastlake 3rd S. Crocker J. Schiller December 1994 ASCII 73842 30 Random Numbers Seed Choosing random quantities to foil a resourceful and motivated adversary is surprisingly difficult. This paper points out many pitfalls in using traditional pseudo-random number generation techniques for choosing such quantities. It recommends the use of truly random hardware techniques and shows that the existing hardware on many systems can be used for this purpose. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1751 A Convention for Human-Readable 128-bit Keys D. McDonald December 1994 ASCII 31428 15 Security Password This memo proposes a convention for use with Internet applications & protocols using 128-bit cryptographic keys. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1752 The Recommendation for the IP Next Generation Protocol S. Bradner A. Mankin January 1995 ASCII 127784 52 IPNG IPng Internet This document presents the recommendation of the IPng Area Directors on what should be used to replace the current version of the Internet Protocol. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1753 IPng Technical Requirements Of the Nimrod Routing and Addressing Architecture N. Chiappa December 1994 ASCII 46586 18 IPng White Paper Internet Protocol This document presents the requirements that the Nimrod routing and addressing architecture has upon the internetwork layer protocol. To be most useful to Nimrod, any protocol selected as the IPng should satisfy these requirements. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1754 IP over ATM Working Group's Recommendations for the ATM Forum's Multiprotocol BOF Version 1 M. Laubach January 1995 ASCII 13483 7 Internet Asynchromous Transfer Mode This document represents an initial list of requirements submitted to the ATM Forum's Multiprotocol BOF for the operation of IP over ATM networks as determined by the IETF IP over ATM Working Group and other working groups. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1755 ATM Signaling Support for IP over ATM M. Perez F. Liaw A. Mankin E. Hoffman D. Grossman A. Malis February 1995 ASCII 55209 32 ATM Asynchronous Transfer Mode This memo describes the ATM call control signaling exchanges needed to support Classical IP over ATM implementations as described in RFC 1577. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1756 Remote Write Protocol - Version 1.0 T. Rinne January 1995 ASCII 22078 11 RWP Application This document describes a simple Remote Write Protocol (RWP). This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. EXPERIMENTAL EXPERIMENTAL RFC1757 Remote Network Monitoring Management Information Base S. Waldbusser February 1995 ASCII 208117 91 RMON-MIB MIB RMON 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] RFC1271 RFC2819 DRAFT STANDARD DRAFT STANDARD RFC1758 NADF Standing Documents: A Brief Overview The North American Directory Forum February 1995 ASCII 7294 4 X.500 North American Directory Forum Public CCITT Providers The purpose of this document is to provide a brief overview of the NADF's Standing Document series. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1417 INFORMATIONAL INFORMATIONAL RFC1759 Printer MIB R. Smith F. Wright T. Hastings S. Zilles J. Gyllenskog March 1995 ASCII 239228 113 Print-MIB Management Information Base 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] RFC3805 PROPOSED STANDARD PROPOSED STANDARD RFC1760 The S/KEY One-Time Password System N. Haller February 1995 ASCII 31124 12 Security This document describes the S/KEY* One-Time Password system as released for public use by Bellcore. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1761 Snoop Version 2 Packet Capture File Format B. Callaghan R. Gilligan February 1995 ASCII 10761 6 SNOOP Measurement debugging collecting data This paper describes the file format used by "snoop", a packet monitoring and capture program developed by Sun. This paper is provided so that people can write compatible programs to generate and interpret snoop packet capture files. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1762 The PPP DECnet Phase IV Control Protocol (DNCP) S. Senum March 1995 ASCII 12709 7 PPP-DNCP Point Digital Equipment Corporation This document defines the NCP for establishing and configuring Digital's DNA Phase IV Routing protocol (DECnet Phase IV) over PPP. This document applies only to DNA Phase IV Routing messages (both data and control), and not to other DNA Phase IV protocols (MOP, LAT, etc). [STANDARDS- TRACK] RFC1376 DRAFT STANDARD DRAFT STANDARD RFC1763 The PPP Banyan Vines Control Protocol (BVCP) S. Senum March 1995 ASCII 17817 10 BVCP Point This document defines the Network Control Protocol for establishing and configuring the Banyan VINES protocol over PPP. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1764 The PPP XNS IDP Control Protocol (XNSCP) S. Senum March 1995 ASCII 9525 5 XNSCP Point Xerox Network Internetwork Datagram Service This document defines the Network Control Protocol for establishing and configuring the Xerox Network Systems (XNS) Internet Datagram Protocol (IDP) over PPP. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1765 OSPF Database Overflow J. Moy March 1995 ASCII 21613 9 OSPF-OVFL This memo details a way of gracefully handling unanticipated database overflows. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. EXPERIMENTAL EXPERIMENTAL RFC1766 Tags for the Identification of Languages H. Alvestrand March 1995 ASCII 16966 9 Lang-Tag This document describes a language tag for use in cases where it is desired to indicate the language used in an information object. [STANDARDS-TRACK] RFC3066 RFC3282 PROPOSED STANDARD PROPOSED STANDARD RFC1767 MIME Encapsulation of EDI Objects D. Crocker March 1995 ASCII 15293 7 MIME-EDI Electronic Data Interchange Multipurpose Internet Mail Extensions delivery mechanism encapsulation Since there are many different EDI specifications, the current document defines three distinct categories as three different MIME content-types. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1768 Host Group Extensions for CLNP Multicasting D. Marlow March 1995 ASCII 111499 45 CLNP-MULT ISO OSI This memo provides a specification for multicast extensions to the CLNP protocol similar to those provided to IP by RFC1112. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. EXPERIMENTAL EXPERIMENTAL RFC1769 Simple Network Time Protocol (SNTP) D. Mills March 1995 ASCII 34454 14 Clocks Synchronization NTP This memorandum describes the Simple Network Time Protocol (SNTP), which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1361 RFC2030 INFORMATIONAL INFORMATIONAL RFC1770 IPv4 Option for Sender Directed Multi-Destination Delivery C. Graff March 1995 ASCII 11606 6 SDMD This memo defines an IPv4 option to provide a sender directed multi- destination delivery mechanism called Selective Directed Broadcast Mode (SDBM). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1771 A Border Gateway Protocol 4 (BGP-4) Y. Rekhter T. Li March 1995 ASCII 131903 57 BGP-4 routing This document, together with its companion document, "Application of the Border Gateway Protocol in the Internet", define an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK] RFC1654 DRAFT STANDARD DRAFT STANDARD RFC1772 Application of the Border Gateway Protocol in the Internet Y. Rekhter P. Gross March 1995 ASCII 43916 19 BGP-4-APP BGP-4 Routing This document, together with its companion document, "A Border Gateway Protocol 4 (BGP-4)", define an inter-autonomous system routing protocol for the Internet. This document describes the usage of the BGP in the Internet. [STANDARDS-TRACK] RFC1655 DRAFT STANDARD DRAFT STANDARD RFC1773 Experience with the BGP-4 protocol P. Traina March 1995 ASCII 19936 9 BGP-4 Border Gateway Protocol Routing The purpose of this memo is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by Border Gateway Protocol version 4 (BGP-4). This report documents experience with BGP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1656 INFORMATIONAL INFORMATIONAL RFC1774 BGP-4 Protocol Analysis P. Traina Editor March 1995 ASCII 23823 10 Border Gateway Routing The purpose of this report is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by the Border Gateway Protocol version 4 (BGP-4). This report summarizes the key features of BGP, and analyzes the protocol with respect to scaling and performance. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1775 To Be "On" the Internet D. Crocker March 1995 ASCII 8454 4 access full Client Mediated Messaging The Internet permits different levels of access for consumers and providers of service. The nature of those differences is quite important in the capabilities They afford. Hence, it is appropriate to provide terminology that distinguishes among the range, so that the Internet community can gain some clarity when distinguishing whether a user (or an organization) is "on" the Internet. This document suggests four terms, for distinguishing the major classes of access. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1776 The Address is the Message S. Crocker April 01 1995 ASCII 2051 2 IPng Declaring that the address is the message, the IPng WG has selected a packet format which includes 1696 bytes of address space. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1777 Lightweight Directory Access Protocol W. Yeong T. Howes S. Kille March 1995 ASCII 45459 22 X.500 DAP interactive access The protocol described in this document is designed to provide access to the X.500 Directory while not incurring the resource requirements of the Directory Access Protocol (DAP).This protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive access to the X.500 Directory, and is intended to be a complement to the DAP itself. [STANDARDS-TRACK] RFC1487 RFC3494 HISTORIC DRAFT STANDARD RFC1778 The String Representation of Standard Attribute Syntaxes T. Howes S. Kille W. Yeong C. Robbins March 1995 ASCII 19053 12 X.500 LDAP lightweight directory protocol The Lightweight Directory Access Protocol (LDAP) requires that the contents of AttributeValue fields in protocol elements be octet strings. This document defines the requirements that must be satisfied by encoding rules used to render X.500 Directory attribute syntaxes into a form suitable for use in the LDAP, then goes on to define the encoding rules for the standard set of attribute syntaxes. [STANDARDS-TRACK] RFC1488 RFC3494 RFC2559 HISTORIC DRAFT STANDARD RFC1779 A String Representation of Distinguished Names S. Kille March 1995 ASCII 12429 8 STR-REP X.500 directory names representing names The OSI Directory uses distinguished names as the primary keys to entries in the directory. Distinguished Names are encoded in ASN.1. When a distinguished name is communicated between to users not using a directory protocol (e.g., in a mail message), there is a need to have a user-oriented string representation of distinguished name. This specification defines a string format for representing names, which is designed to give a clean representation of commonly used names, whilst being able to represent any distinguished name. [STANDARDS-TRACK] RFC1485 RFC2253 RFC3494 HISTORIC DRAFT STANDARD RFC1780 Internet Official Protocol Standards J. Postel Editor March 1995 ASCII 86594 39 status procedure index This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK] RFC1720 RFC1800 HISTORIC STANDARD RFC1781 Using the OSI Directory to Achieve User Friendly Naming S. Kille March 1995 ASCII 47129 26 OSI-Dir X.500 directory names representing names This proposal sets out some conventions for representing names in a friendly manner, and shows how this can be used to achieve really friendly naming. [STANDARDS-TRACK] RFC1484 RFC3494 HISTORIC PROPOSED STANDARD RFC1782 TFTP Option Extension G. Malkin A. Harkin March 1995 ASCII 11508 6 trivial file transfer booting The Trivial File Transfer Protocol is a simple, lock-step, file transfer protocol which allows a client to get or put a file onto a remote host. This document describes a simple extension to TFTP to allow option negotiation prior to the file transfer. RFC2347 RFC1350 PROPOSED STANDARD PROPOSED STANDARD RFC1783 TFTP Blocksize Option G. Malkin A. Harkin March 1995 ASCII 7814 5 trivial file transfer booting This document describes a TFTP option which allows the client and server to negotiate a blocksize more applicable to the network medium. [STANDARDS-TRACK] RFC2348 RFC1350 PROPOSED STANDARD PROPOSED STANDARD RFC1784 TFTP Timeout Interval and Transfer Size Options G. Malkin A. Harkin March 1995 ASCII 6106 4 trivial file transfer booting This document describes two TFTP options. The first allows the client and server to negotiate the Timeout Interval. The second allows the side receiving the file to determine the ultimate size of the transfer before it begins. [STANDARDS-TRACK] RFC2349 RFC1350 PROPOSED STANDARD PROPOSED STANDARD RFC1785 TFTP Option Negotiation Analysis G. Malkin A. Harkin March 1995 ASCII 3354 2 trivial file transfer booting This document was written to allay concerns that the presence of options in a TFTP Request packet might cause pathological behavior on servers which do not support TFTP option negotiation. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1350 INFORMATIONAL INFORMATIONAL RFC1786 Representation of IP Routing Policies in a Routing Registry (ripe-81++) T. Bates E. Gerich L. Joncheray J-M. Jouanigot D. Karrenberg M. Terpstra J. Yu March 1995 ASCII 133643 83 This document is an update to the original `ripe-81' proposal for representing and storing routing polices within the RIPE database. It incorporates several extensions proposed by Merit Inc. and gives details of a generalized IP routing policy representation to be used by all Internet routing registries. It acts as both tutorial and provides details of database objects and attributes that use and make up a routing registry. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1787 Routing in a Multi-provider Internet Y. Rekhter April 1995 ASCII 20754 8 Internet Protocol Architechure Board IAB This document presents some of the issues related to network layer routing in a multi-provider Internet, and specifically to the unicast routing. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1788 ICMP Domain Name Messages W. Simpson April 1995 ASCII 11722 7 ICMP-DM Internet Control Message Protocol DNS Service This document specifies ICMP messages for learning the Fully Qualified Domain Name associated with an IP address. This document defines an Experimental Protocol for the Internet community. This does not specify an Internet standard of any kind. EXPERIMENTAL EXPERIMENTAL RFC1789 INETPhone: Telephone Services and Servers on Internet C. Yang April 1995 ASCII 14186 6 This RFC presents a true telephone service, called INETPhone, which supports voice communication through the Internet. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1790 An Agreement between the Internet Society and Sun Microsystems, Inc. in the Matter of ONC RPC and XDR Protocols V. Cerf April 1995 ASCII 8226 4 ISOC This RFC is an official public record of an agreement between SUN Microsystems and the Internet Society. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1791 TCP And UDP Over IPX Networks With Fixed Path MTU T. Sung April 1995 ASCII 22347 12 Transmission Control Protocol User Datagram Maxium Unit TCP/IPX allows TCP/IP applications to run over IPX networks by letting TCP and UDP run over IPX. And this memo specifies the packet format and operational procedures for running TCP and UDP over IPX. This document defines an Experimental Protocol for the Internet community. This does not specify an Internet standard of any kind. EXPERIMENTAL EXPERIMENTAL RFC1792 TCP/IPX Connection Mib Specification T. Sung April 1995 ASCII 16389 9 TCP/IPXMIB Transmission Control Protocol Management Information Base New MIB objects, tcpIpxConnTable, udpIpxTable, tcpUnspecConnTable and udpUnspecTable are presented in this paper, to be used in place of tcpConnTable and udpListenerTable when TCP and UDP are running over IPX. This document defines an Experimental Protocol for the Internet community. This does not specify an Internet standard of any kind. EXPERIMENTAL EXPERIMENTAL RFC1793 Extending OSPF to Support Demand Circuits J. Moy April 1995 ASCII 78728 32 OSPF-DC Open Shortest Path First This memo defines enhancements to the OSPF protocol that allow efficient operation over "demand circuits". [STANDARDS-TRACK] RFC3883 PROPOSED STANDARD PROPOSED STANDARD RFC1794 DNS Support for Load Balancing T. Brisco April 1995 ASCII 15494 7 Domain Name System This RFC is meant to first chronicle a foray into the IETF DNS Working Group, discuss other possible alternatives to provide/simulate load balancing support for DNS, and to provide an ultimate, flexible solution for providing DNS support for balancing loads of many types. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1795 Data Link Switching: Switch-to-Switch Protocol AIW DLSw RIG: DLSw Closed Pages, DLSw Standard Version 1 L. Wells Chair A. Bartky Editor April 1995 ASCII 214848 91 IBM SNA DLS SSP NetBIos APPN This RFC describes use of Data Link Switching over TCP/IP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1434 INFORMATIONAL INFORMATIONAL RFC1796 Not All RFCs are Standards C. Huitema J. Postel S. Crocker April 1995 ASCII 7049 4 This document discusses the relationship of the Request for Comments (RFCs) notes to Internet Standards. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1797 Class A Subnet Experiment Internet Assigned Numbers Authority (IANA) April 1995 ASCII 6779 4 Network Address 39 Number There appears to be some interest in experimenting with subnetting the class A addresses. It is suggested that conducting an experiment now to identify and fix any software that does not properly handle subnetted class A addresses would be useful and important. This document defines an Experimental Protocol for the Internet community. This does not specify an Internet standard of any kind. EXPERIMENTAL EXPERIMENTAL RFC1798 Connection-less Lightweight X.500 Directory Access Protocol A. Young June 1995 ASCII 18548 9 CLDAP CLDAP Presentation Address Application Entity Title 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] RFC3352 HISTORIC PROPOSED STANDARD RFC1799 Request for Comments Summary RFC Numbers 1700-1799 M. Kennedy January 1997 ASCII 42038 21 Index INFORMATIONAL INFORMATIONAL RFC1800 Internet Official Protocol Standards J. Postel Editor July 1995 ASCII 83649 36 status procedure index This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK] RFC1780 RFC1880 HISTORIC STANDARD RFC1801 MHS use of the X.500 Directory to support MHS Routing S. Kille June 1995 ASCII 156462 73 Routing Mail EMail Message Handling System X.400 The key problem in routing is to map from an O/R Address onto an MTA (next hop). This shall be an MTA which in some sense is "nearer" to the destination UA. This is done repeatedly until the message can be directly delivered to the recipient UA. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1802 Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 Routing H. Alvestrand K. Jordan S. Langlois J. Romaguera June 1995 ASCII 24637 11 Mail EMail Message Handling System MHS This memo describes a proposed Internet Pilot Project that seeks to prove the MHS-DS approach on a larger scale. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1803 Recommendations for an X.500 Production Directory Service R. Wright A. Getchell T. Howes S. Sataluri P. Yee W. Yeong June 1995 ASCII 14721 8 White Pages DSA Directory User Agent This document contains a set of basic recommendations for a country- level X.500 DSA. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1804 Schema Publishing in X.500 Directory G. Mansfield P. Rajeev S. Raghavan T. Howes June 1995 ASCII 18268 10 In this document we propose a solution using the existing mechanisms of the directory [1] itself. We present a naming scheme for naming schema objects and a meta-schema for storing schema objects in the directory. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1805 Location-Independent Data/Software Integrity Protocol A. Rubin June 1995 ASCII 13352 6 Betsi Security Cryptography This memo describes a protocol for adding integrity assurance to files that are distributed across the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1806 Communicating Presentation Information in Internet Messages: The Content-Disposition Header R. Troost S. Dorner June 1995 ASCII 15548 8 MIME EMail Mail This memo provides a mechanism whereby messages conforming to the [RFC 1521] ("MIME") specification can convey presentational information. This memo defines an Experimental Protocol for the Internet community. RFC2183 EXPERIMENTAL EXPERIMENTAL RFC1807 A Format for Bibliographic Records R. Lasher D. Cohen June 1995 ASCII 29417 15 library technical reports email services This RFC defines a format for bibliographic records describing technical reports. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1357 INFORMATIONAL INFORMATIONAL RFC1808 Relative Uniform Resource Locators R. Fielding June 1995 ASCII 34950 16 URL URL syntax semantics In situations where the base URL is well-defined and known to the parser (human or machine), it is useful to be able to embed URL references which inherit that context rather than re-specifying it in every instance. This document defines the syntax and semantics for such Relative Uniform Resource Locators. [STANDARDS-TRACK] RFC3986 RFC1738 RFC2368 RFC2396 PROPOSED STANDARD PROPOSED STANDARD RFC1809 Using the Flow Label Field in IPv6 C. Partridge June 1995 ASCII 13591 6 The purpose of this memo is to distill various opinions and suggestions of the End-to-End Research Group regarding the handling of Flow Labels into a set of suggestions for IPv6. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1810 Report on MD5 Performance J. Touch June 1995 ASCII 16607 7 IPv6 Message Digest Algorithm Authentication This RFC addresses how fast MD5 can be implemented in software and hardware, and whether it supports currently available IP bandwidth. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1811 U.S. Government Internet Domain Names Federal Networking Council June 1995 ASCII 6641 3 GOV FNC IANA This document describes the registration policies for the top-level domain ".GOV". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1816 INFORMATIONAL INFORMATIONAL RFC1812 Requirements for IP Version 4 Routers F. Baker Editor June 1995 ASCII 415740 175 routing IPv4 This memo defines and discusses requirements for devices that perform the network layer forwarding function of the Internet protocol suite. [STANDARDS-TRACK] RFC1716 RFC1009 RFC2644 PROPOSED STANDARD PROPOSED STANDARD RFC1813 NFS Version 3 Protocol Specification B. Callaghan B. Pawlowski P. Staubach June 1995 ASCII 229793 126 NFSV3 This paper describes the NFS version 3 protocol. This paper is provided so that people can write compatible implementations. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. 10/29/03 - back in June 2002, Matthew Wilcox sent an email stating that RFC 3010 is listed as erronously obsoleting RFCs 1813 and 1094. This was confirmed by Scott Bradner in October 2003. I have removed the Obsoleted by tag for for this entry. RFC1094 INFORMATIONAL INFORMATIONAL RFC1814 Unique Addresses are Good E. Gerich June 1995 ASCII 5936 3 Internet Registries Protocol Private Network Numbers The IAB suggests that while RFC 1597 establishes reserved IP address space for the use of private networks which are isolated and will remain isolated from the Internet, any enterprise which anticipates external connectivity to the Internet should apply for a globally unique address from an Internet registry or service provider. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1815 Character Sets ISO-10646 and ISO-10646-J-1 M. Ohta July 1995 ASCII 11823 6 Japanese Latin For the practical use of ISO 10646, a lot of external profiling such as restriction of characters, restriction of combination of characters and addition of language information is necessary. This memo provides information on such profiling, along with charset names to each profiled instance. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1816 U.S. Government Internet Domain Names Federal Networking Council August 1995 ASCII 17979 8 GOV FNC IANA This memo provides an update and clarification to RFC 1811. This document describes the registration policies for the top-level domain ".GOV". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1811 RFC2146 INFORMATIONAL INFORMATIONAL RFC1817 CIDR and Classful Routing Y. Rekhter August 1995 ASCII 3416 2 Classless Inter Domain Routing This document represents the IAB's (Internet Architecture Board) evaluation of the current and near term implications of CIDR on organizations that use Classful routing technology. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1818 Best Current Practices J. Postel T. Li Y. Rekhter August 1995 ASCII 4114 3 BCP This document describes a new series of documents which describe best current practices for the Internet community. Documents in this series carry the endorsement of the Internet Engineering Steering Group (IESG). BCP0001 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC1819 Internet Stream Protocol Version 2 (ST2) Protocol Specification - Version ST2+ L. Delgrossi L. Berger Editors August 1995 ASCII 266875 109 ST2 This memo contains a revised specification of the Internet STream Protocol Version 2 (ST2). This memo defines an Experimental Protocol for the Internet community. RFC1190 IEN119 EXPERIMENTAL EXPERIMENTAL RFC1820 Multimedia E-mail (MIME) User Agent Checklist E. Huizer August 1995 ASCII 14672 8 Multipurpose Internet Mail Extensions Media Types This document presents a checklist to facilitate evaluation of MIME capable User Agents. Access to a MIME test-responder, that generates test-messages is described. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1844 INFORMATIONAL INFORMATIONAL RFC1821 Integration of Real-time Services in an IP-ATM Network Architecture M. Borden E. Crawley B. Davie S. Batsell August 1995 ASCII 64466 24 Asynchronous Transfer Mode The purpose of this paper is to provide a clear statement of what issues need to be addressed in interfacing the IP integrated services environment with an ATM service environment so as to create a seamless interface between the two in support of end users desiring real-time networking services. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1822 A Grant of Rights to Use a Specific IBM patent with Photuris J. Lowe August 1995 ASCII 2664 2 Internet Key Management Protocol IKMP IETF This Request for Comments records a grant by IBM Corporation to permit the conditional free use of one of its patents. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1823 The LDAP Application Program Interface T. Howes M. Smith August 1995 ASCII 41081 22 lightweight directory access protocol API X.500 This document defines a C language application program interface to the lightweight directory access protocol (LDAP). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1824 The Exponential Security System TESS: An Identity-Based Cryptographic Protocol for Authenticated Key-Exchange (E.I.S.S.-Report 1995/4) H. Danisch August 1995 ASCII 45540 21 TESS public keys This informational RFC describes the basic mechanisms and functions of an identity based system for the secure authenticated exchange of cryptographic keys, the generation of signatures, and the authentic distribution of public keys. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1825 Security Architecture for the Internet Protocol R. Atkinson August 1995 ASCII 56772 22 IPv4 IPv6 IP-layer ipsec This memo describes the security mechanisms for IP version 4 (IPv4) and IP version 6 (IPv6) and the services that they provide. [STANDARDS- TRACK] RFC2401 PROPOSED STANDARD PROPOSED STANDARD RFC1826 IP Authentication Header R. Atkinson August 1995 ASCII 27583 13 ipsec IPV6-AH Internet Protocol AH security IPv4 IPv6 This document describes a mechanism for providing cryptographic authentication for IPv4 and IPv6 datagrams. [STANDARDS-TRACK] RFC2402 PROPOSED STANDARD PROPOSED STANDARD RFC1827 IP Encapsulating Security Payload (ESP) R. Atkinson August 1995 ASCII 30278 12 ESP Internet Protocol IPv4 IPv6 ipsec This document describes the IP Encapsulating Security Payload (ESP). ESP is a mechanism for providing integrity and confidentiality to IP datagrams. [STANDARDS-TRACK] RFC2406 PROPOSED STANDARD PROPOSED STANDARD RFC1828 IP Authentication using Keyed MD5 P. Metzger W. Simpson August 1995 ASCII 9800 6 ipsec Internet Protocol Authentication Header AH Message Digest 5 Security This document describes the use of keyed MD5 with the IP Authentication Header. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1829 The ESP DES-CBC Transform P. Karn P. Metzger W. Simpson August 1995 ASCII 19291 11 Encapsulating Security Payload US Data Encryption Standard Cipher Block Chaining IP Internet Protocol Security ipsec This document describes the DES-CBC security transform for the IP Encapsulating Security Payload (ESP). [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1830 SMTP Service Extensions for Transmission of Large and Binary MIME Messages G. Vaudreuil August 1995 ASCII 16555 8 Simple Mail Transfer Multipurpose Mail Extensions 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. RFC3030 EXPERIMENTAL EXPERIMENTAL RFC1831 RPC: Remote Procedure Call Protocol Specification Version 2 R. Srinivasan August 1995 ASCII 37798 18 RPC ONC Open Network Computing This document describes the ONC Remote Procedure Call (ONC RPC Version 2) protocol as it is currently deployed and accepted. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1832 XDR: External Data Representation Standard R. Srinivasan August 1995 ASCII 47418 24 XDR RPC ONC Open Network Computing This document describes the External Data Representation Standard (XDR) protocol as it is currently deployed and accepted. [STANDARDS-TRACK] DRAFT STANDARD PROPOSED STANDARD RFC1833 Binding Protocols for ONC RPC Version 2 R. Srinivasan August 1995 ASCII 24449 14 ONC Open Network Computing This document describes the binding protocols used in conjunction with the ONC Remote Procedure Call (ONC RPC Version 2) protocols. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1834 Whois and Network Information Lookup Service, Whois++ J. Gargano K. Weiss August 1995 ASCII 14429 7 nicname TCP Transmission Control Protocol directory service server retrieval This memo describes new features for WHOIS. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1835 Architecture of the WHOIS++ service P. Deutsch R. Schoultz P. Faltstrom C. Weider August 1995 ASCII 80581 41 WHOIS++ nicname TCP Transmission Control Protocol directory service server retrieval This document describes WHOIS++, an extension to the trivial WHOIS service described in RFC 954 to permit WHOIS-like servers to make available more structured information to the Internet. [STANDARDS- TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1836 Representing the O/R Address hierarchy in the X.500 Directory Information Tree S. Kille August 1995 ASCII 20175 11 message handling This document defines a representation of the O/R Address hierarchy in the Directory Information Tree [6, 1]. This memo defines an Experimental Protocol for the Internet community. RFC2294 EXPERIMENTAL EXPERIMENTAL RFC1837 Representing Tables and Subtrees in the X.500 Directory S. Kille August 1995 ASCII 10924 7 message handling This document defines techniques for representing two types of information mapping in the OSI Directory. This memo defines an Experimental Protocol for the Internet community. RFC2293 EXPERIMENTAL EXPERIMENTAL RFC1838 Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses S. Kille August 1995 ASCII 12216 8 message handling This document defines how to use directory to support the mapping between X.400 O/R Addresses and mailboxes defined in RFC 1327 [2]. This memo defines an Experimental Protocol for the Internet community. RFC2164 EXPERIMENTAL EXPERIMENTAL RFC1839 RFC1840 RFC1841 PPP Network Control Protocol for LAN Extension J. Chapman D. Coli A. Harvey B. Jensen K. Rowett September 1995 ASCII 146206 66 point-to-point local area interface INFORMATIONAL INFORMATIONAL RFC1842 ASCII Printable Characters-Based Chinese Character Encoding for Internet Messages Y. Wei Y. Zhang J. Li J. Ding Y. Jiang August 1995 ASCII 24143 12 electronic mail HZ-GB-2312 This document describes the encoding used in electronic mail [RFC822] and network news [RFC1036] messages over the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Telecommunications infrastructure is improving to offer higher bandwidth connections at lower cost. Access to the network is changing from modems to more intelligent devices. This informational RFC discusses a PPP Network Control Protocol for one such intelligent device. The protocol is the LAN extension interface protocol. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1843 HZ - A Data Format for Exchanging Files of Arbitrarily Mixed Chinese and ASCII characters F. Lee August 1995 ASCII 8787 5 GB2312-80 electronic mail The content of this memo is identical to an article of the same title written by the author on September 4, 1989. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1844 Multimedia E-mail (MIME) User Agent Checklist E. Huizer August 1995 ASCII 15072 8 Multipurpose Internet Mail Extensions Media Types This document presents a checklist to facilitate evaluation of MIME capable User Agents. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1820 INFORMATIONAL INFORMATIONAL RFC1845 SMTP Service Extension for Checkpoint/Restart D. Crocker N. Freed A. Cargille September 1995 ASCII 15399 7 simple mail transfer transaction EXPERIMENTAL EXPERIMENTAL RFC1846 SMTP 521 Reply Code A. Durand F. Dupont September 1995 ASCII 6558 4 simple mail transfer EXPERIMENTAL EXPERIMENTAL RFC1847 Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted J. Galvin S. Murphy S. Crocker N. Freed October 1995 ASCII 23679 11 MIME-Encyp mail multipurpose extensions This document defines a framework within which security services may be applied to MIME body parts. [STANDARDS-TRACK] This memo defines a new Simple Mail Transfer Protocol (SMTP) [1] reply code, 521, which one may use to indicate that an Internet host does not accept incoming mail. This memo defines an Experimental Protocol for the Internet community. This memo defines an extension to the SMTP service whereby an interrupted SMTP transaction can be restarted at a later time without having to repeat all of the commands and message content sent prior to the interruption. This memo defines an Experimental Protocol for the Internet community. PROPOSED STANDARD PROPOSED STANDARD RFC1848 MIME Object Security Services S. Crocker N. Freed J. Galvin S. Murphy October 1995 ASCII 95010 48 MIME-Sec mail multipurpose extensions This document defines MIME Object Security Services (MOSS), a protocol that uses the multipart/signed and multipart/encrypted framework [7] to apply digital signature and encryption services to MIME objects. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1849 RFC1850 OSPF Version 2 Management Information Base F. Baker R. Coltun November 1995 ASCII 140255 80 OSPF-MIB Open Shortest Path First SPF MIB routing network management This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Open Shortest Path First Routing Protocol. [STANDARDS-TRACK] RFC1253 DRAFT STANDARD DRAFT STANDARD RFC1851 The ESP Triple DES Transform P. Karn P. Metzger W. Simpson September 1995 ASCII 20000 11 ESP3DES encryption encapsulating security payload cipher block chaining EXPERIMENTAL EXPERIMENTAL RFC1852 IP Authentication using Keyed SHA P. Metzger W. Simpson September 1995 ASCII 9367 6 encryption secure hash algorithm RFC2841 EXPERIMENTAL EXPERIMENTAL RFC1853 IP in IP Tunneling W. Simpson October 1995 ASCII 14803 8 internet protocol payload encapsulation This document discusses implementation techniques for using IP Protocol/Payload number 4 Encapsulation for tunneling with IP Security and other protocols. This memo provides information for the Internet community. It does not specify an Internet standard. This document describes the use of keyed SHA with the IP Authentication Header. This document defines an Experimental Protocol for the Internet community. This document describes the Triple DES-CBC security transform for the IP Encapsulating Security Payload (ESP). This document defines an Experimental Protocol for the Internet community. INFORMATIONAL INFORMATIONAL RFC1854 SMTP Service Extension for Command Pipelining N. Freed October 1995 ASCII 14097 7 simple mail transfer protocol 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] RFC2197 PROPOSED STANDARD PROPOSED STANDARD RFC1855 Netiquette Guidelines S. Hambridge October 1995 ASCII 46185 21 Network Etiquette This document provides a minimum set of guidelines for Network Etiquette (Netiquette) which organizations may take and adapt for their own use. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. FYI0028 INFORMATIONAL INFORMATIONAL RFC1856 The Opstat Client-Server Model for Statistics Retrieval H. Clark September 1995 ASCII 29954 17 tools performance utilization INFORMATIONAL INFORMATIONAL RFC1857 A Model for Common Operational Statistics M. Lambert October 1995 ASCII 55314 27 metrics measurements polling periods This memo describes a model for operational statistics in the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. This document defines a model and protocol for a set of tools which could be used by NSPs and Network Operation Centers (NOCs) to share data among themselves and with customers. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1404 INFORMATIONAL INFORMATIONAL RFC1858 Security Considerations for IP Fragment Filtering G. Ziemba D. Reed P. Traina October 1995 ASCII 20468 10 internet protocol tcp transmission control protocol routers hosts IP fragmentation can be used to disguise TCP packets from IP filters used in routers and hosts. This document describes two methods of attack as well as remedies to prevent them. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC3128 INFORMATIONAL INFORMATIONAL RFC1859 ISO Transport Class 2 Non-use of Explicit Flow Control over TCP RFC1006 extension Y. Pouffary October 1995 ASCII 14572 8 International Standard Organizatio This document is an extension to STD35, RFC1006, a standard for the Internet community. The document does not duplicate the protocol definitions contained in RFC1006 and in International Standard ISO 8073. It supplements that information with the description of how to implement ISO Transport Class 2 Non-use of Explicit Flow Control on top of TCP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1860 Variable Length Subnet Table For IPv4 T. Pummill B. Manning October 1995 ASCII 5694 3 values IPv4 subnets This document itemizes the potential values for IPv4 subnets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1878 INFORMATIONAL INFORMATIONAL RFC1861 Simple Network Paging Protocol - Version 3 -Two-Way Enhanced A. Gwinn October 1995 ASCII 49181 23 SNPP SNPP wireless paging This RFC suggests a simple way for delivering wireless messages, both one and two-way, to appropriate receiving devices. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1645 INFORMATIONAL INFORMATIONAL RFC1862 Report of the IAB Workshop on Internet Information Infrastructure, October 12-14, 1994 M. McCahill J. Romkey M. Schwartz K. Sollins T. Verschuren C. Weider November 1995 ASCII 62483 27 Internet Architecture Board This document is a report on an Internet architecture workshop, initiated by the IAB and held at MCI on October 12-14, 1994. This workshop generally focused on aspects of the information infrastructure on the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1863 A BGP/IDRP Route Server alternative to a full mesh routing D. Haskin October 1995 ASCII 37426 16 BGP-IDRP border gateway protocol inter-domain routing This document describes the use and detailed design of Route Servers for dissemination of routing information among BGP/IDRP speaking routers. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1864 The Content-MD5 Header Field J. Myers M. Rose October 1995 ASCII 7216 4 CON-MD5 MIME EMail Integrity MIC Digest This memo specifies an optional header field, Content-MD5, for use with MIME-conformant messages. [STANDARDS-TRACK] RFC1544 DRAFT STANDARD DRAFT STANDARD RFC1865 EDI Meets the Internet Frequently Asked Questions about Electronic Data Interchange (EDI) on the Internet W. Houser J. Griffin C. Hage January 1996 ASCII 98361 41 FAQ This memo is targeted towards the EDI community that is unfamiliar with the Internet, including EDI software developers, users, and service providers. The memo introduces the Internet and assumes a basic knowledge of EDI. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1866 Hypertext Markup Language - 2.0 T. Berners-Lee D. Connolly November 1995 ASCII 146904 77 HTML HTML SGML Standard Generalized Language WWW World Wide Web This document defines a HTML 2.0 (to distinguish it from the previous informal specifications). [STANDARDS-TRACK] RFC2854 HISTORIC PROPOSED STANDARD RFC1867 Form-based File Upload in HTML E. Nebel L. Masinter November 1995 ASCII 26183 13 Hypertext Markup Language MIME Multipurpose Internet Mail Extensions 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. RFC2854 HISTORIC EXPERIMENTAL RFC1868 ARP Extension - UNARP G. Malkin November 1995 ASCII 7681 4 UNARP Address Resolution Protocol delete entry This document specifies a trivial modification to the ARP mechanism, not the packet format, which allows a node to announce that it is leaving the network and that all other nodes should modify their ARP tables accordingly. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1869 SMTP Service Extensions J. Klensin N. Freed M. Rose E. Stefferud D. Crocker November 1995 ASCII 23299 11 ESMTP Simple Mail Transfer Protocol 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] RFC1651 RFC2821 STD0010 STANDARD STANDARD RFC1870 SMTP Service Extension for Message Size Declaration J. Klensin N. Freed K. Moore November 1995 ASCII 18226 9 SMTP-SIZE Simple Mail Transfer Protocol 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] RFC1653 STD0010 STANDARD STANDARD RFC1871 Addendum to RFC 1602 -- Variance Procedure J. Postel November 1995 ASCII 7747 4 BCP WG escape clause procedures This document describes a modification to the IETF procedures to allow an escape from a situation where the existing procedures are not working or do not seem to apply. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC1602 RFC1603 BCP0002 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC1872 The MIME Multipart/Related Content-type E. Levinson December 1995 ASCII 15565 8 multipurpose Internet Mail Extensions The Multipart/Related content-type provides a common mechanism for representing objects that are aggregates of related MIME body parts. This document defines the Multipart/Related content-type and provides examples of its use. This memo defines an Experimental Protocol for the Internet community. RFC2112 EXPERIMENTAL EXPERIMENTAL RFC1873 Message/External-Body Content-ID Access Type E. Levinson December 1995 ASCII 5878 4 CONT-MT Multipurpose Internet Mail Extensions The existing MIME Content-Type Message/External-Body access-types allow a MIME entity (body-part) to refer to an object that is not in the message by specifying how to access that object. The Content-ID access method described in this document provides the capability to refer to an object within the message. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1874 SGML Media Types E. Levinson December 1995 ASCII 12515 6 SGML-MT Multipurpose Internet Mail Extensions This document proposes new media sub-types of Text/SGML and Application/SGML. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1875 UNINETT PCA Policy Statements N. Berge December 1995 ASCII 19089 10 Policy Certification Authority Encryption This document provides information about policy statements submitted by the UNINETT Policy Certification Authority (UNINETT PCA). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1876 A Means for Expressing Location Information in the Domain Name System C. Davis P. Vixie T. Goodwin I. Dickinson January 1996 ASCII 29631 18 DNS-LOC DNS Resource Record (RR) LOC This memo defines a new DNS RR type for experimental purposes. This RFC describes a mechanism to allow the DNS to carry location information about hosts, networks, and subnets. This memo defines an Experimental Protocol for the Internet community. RFC1034 RFC1035 EXPERIMENTAL EXPERIMENTAL RFC1877 PPP Internet Protocol Control Protocol Extensions for Name Server Addresses S. Cobb December 1995 ASCII 10591 6 Point-to-Point Protocol Network Control Domain System NetBIOS This document extends the NCP for establishing and configuring the Internet Protocol over PPP [2], defining the negotiation of primary and secondary Domain Name System (DNS) [3] and NetBIOS Name Server (NBNS) [4] addresses. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1878 Variable Length Subnet Table For IPv4 T. Pummill B. Manning December 1995 ASCII 19414 8 values IPv4 subnets This memo clarifies issues surrounding subnetting IP networks by providing a standard subnet table. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1860 INFORMATIONAL INFORMATIONAL RFC1879 Class A Subnet Experiment Results and Recommendations B. Manning Editor January 1996 ASCII 10589 6 Internet Registry Operations This memo documents some experiences with the RFC 1797 [1] subnet A experiment (performed by the Net39 Test Group (see credits)) and provides a number of recommendations on future direction for both the Internet Registries and the Operations community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1880 Internet Official Protocol Standards J. Postel Editor November 1995 ASCII 89153 38 status procedure index This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK] RFC1800 RFC1920 HISTORIC STANDARD RFC1881 IPv6 Address Allocation Management IAB IESG December 1995 ASCII 3215 2 IANA Internet Assigned Numbers Authority The IPv6 address space will be managed by the IANA for the good of the Internet community, with advice from the IAB and the IESG, by delegation to the regional registries. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1882 The 12-Days of Technology Before Christmas B. Hancock December 1995 ASCII 9130 5 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1883 Internet Protocol, Version 6 (IPv6) Specification S. Deering R. Hinden December 1995 ASCII 82089 37 IP Next Generation IPng This document specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng. [STANDARDS-TRACK] RFC2460 PROPOSED STANDARD PROPOSED STANDARD RFC1884 IP Version 6 Addressing Architecture R. Hinden S. Deering Editors December 1995 ASCII 37860 18 IPV6-Addr IP Next Generation IPng This specification defines the addressing architecture of the IP Version 6 protocol [IPV6]. [STANDARDS-TRACK] RFC2373 HISTORIC PROPOSED STANDARD RFC1885 Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) A. Conta S. Deering December 1995 ASCII 32214 20 IP Next Generation IPng Internet Group Management IGMP This document specifies a set of Internet Control Message Protocol (ICMP) messages for use with version 6 of the Internet Protocol (IPv6). [STANDARDS-TRACK] RFC2463 PROPOSED STANDARD PROPOSED STANDARD RFC1886 DNS Extensions to support IP version 6 S. Thomson C. Huitema December 1995 ASCII 6424 5 DNS-IPV6 IP Next Generation IPng Domain Name System This document defines the changes that need to be made to the Domain Name System to support hosts running IP version 6 (IPv6). [STANDARDS- TRACK] RFC3596 RFC2874 RFC3152 PROPOSED STANDARD PROPOSED STANDARD RFC1887 An Architecture for IPv6 Unicast Address Allocation Y. Rekhter T. Li Editors December 1995 ASCII 66066 26 IP Next Generation IPng, This document provides an architecture for allocating IPv6 [1] unicast addresses in the Internet. This document provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1888 OSI NSAPs and IPv6 J. Bound B. Carpenter D. Harrington J. Houldsworth A. Lloyd August 1996 ASCII 36469 16 Internet Protocol Open Systems Interconnection This document recommends that network implementors who have planned or deployed an OSI NSAP addressing plan, and who wish to deploy or transition to IPv6, should redesign a native IPv6 addressing plan to meet their needs. This memo defines an Experimental Protocol for the Internet community. made historic by rfc4048. HISTORIC EXPERIMENTAL RFC1889 RTP: A Transport Protocol for Real-Time Applications Audio-Video Transport Working Group H. Schulzrinne S. Casner R. Frederick V. Jacobson January 1996 ASCII 188544 75 RTP end-to-end network audio video RTCP This memorandum describes RTP, the real-time transport protocol. RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services. [STANDARDS-TRACK] RFC3550 PROPOSED STANDARD PROPOSED STANDARD RFC1890 RTP Profile for Audio and Video Conferences with Minimal Control Audio-Video Transport Working Group H. Schulzrinne January 1996 ASCII 37509 18 RTP-AV end-to-end network conference This memo describes a profile for the use of the real-time transport protocol (RTP), version 2, and the associated control protocol, RTCP, within audio and video multiparticipant conferences with minimal control. [STANDARDS-TRACK] RFC3551 PROPOSED STANDARD PROPOSED STANDARD RFC1891 SMTP Service Extension for Delivery Status Notifications K. Moore January 1996 ASCII 65192 31 SMTP-DSN simple mail transfer protocol 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] RFC3461 PROPOSED STANDARD PROPOSED STANDARD RFC1892 The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages G. Vaudreuil January 1996 ASCII 7800 4 MIME-RPT Multipurpose Internet Mail Extensions 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] RFC3462 PROPOSED STANDARD PROPOSED STANDARD RFC1893 Enhanced Mail System Status Codes G. Vaudreuil January 1996 ASCII 28218 15 EMS-CODE simple mail transfer protocol SMTP 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] RFC3463 PROPOSED STANDARD PROPOSED STANDARD RFC1894 An Extensible Message Format for Delivery Status Notifications K. Moore G. Vaudreuil January 1996 ASCII 77462 39 DSN Multipurpose Internet Mail Extensions Content Type This memo defines a MIME content-type that may be used by a message transfer agent (MTA) or electronic mail gateway to report the result of an attempt to deliver a message to one or more recipients. [STANDARDS- TRACK] RFC3464 RFC2852 PROPOSED STANDARD PROPOSED STANDARD RFC1895 The Application/CALS-1840 Content-type E. Levinson February 1996 ASCII 10576 6 MIL-STD-1840 MIME Multipurpose Internet Mail Extensions This memorandum provides guidelines for using the United States Department of Defense Military Standard MIL-STD-1840, "Automated Interchange of Technical Information," with the Internet electronic mail standards, RFC 822 and RFC 1521. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1896 The text/enriched MIME Content-type P. Resnick A. Walker February 1996 ASCII 45926 21 PS 81217 MIME Multipurpose Internet Mail Extensions This document defines one particular type of MIME data, the text/enriched MIME type. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1523 RFC1563 INFORMATIONAL INFORMATIONAL RFC1897 IPv6 Testing Address Allocation R. Hinden J. Postel January 1996 ASCII 6643 4 Internet Protocol prototype software 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. RFC2471 EXPERIMENTAL EXPERIMENTAL RFC1898 CyberCash Credit Card Protocol Version 0.8 D. Eastlake 3rd B. Boesch S. Crocker M. Yesil February 1996 ASCII 113633 52 general payments system This document covers only the current CyberCash system which is one of the few operational systems in the rapidly evolving area of Internet payments. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1899 Request for Comments Summary RFC Numbers 1800-1899 J. Elliott January 1997 ASCII 37984 20 Index INFORMATIONAL INFORMATIONAL RFC1900 Renumbering Needs Work B. Carpenter Y. Rekhter February 1996 ASCII 9528 4 IP network number addressing Hosts in an IP network are identified by IP addresses, and the IP address prefixes of subnets are advertised by routing protocols. A change in such IP addressing information associated with a host or subnet is known as "renumbering". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1901 Introduction to Community-based SNMPv2 J. Case K. McCloghrie M. Rose S. Waldbusser January 1996 ASCII 15903 8 SNMPV2CB Simple Network Management Protocol Version 2 The purpose of this document is to define the Community-based Administrative Framework for the SNMP version 2 framework (SNMPv2). This document specifies an Experimental protocol for the Internet community. HISTORIC EXPERIMENTAL RFC1902 Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2) J. Case K. McCloghrie M. Rose S. Waldbusser January 1996 ASCII 77453 40 Simple Network Management Protocol Version 2 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] RFC1442 RFC2578 DRAFT STANDARD DRAFT STANDARD RFC1903 Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2) J. Case K. McCloghrie M. Rose S. Waldbusser January 1996 ASCII 52652 23 Simple Network Management Protocol Version 2 It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK] RFC1443 RFC2579 DRAFT STANDARD DRAFT STANDARD RFC1904 Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2) J. Case K. McCloghrie M. Rose S. Waldbusser January 1996 ASCII 47083 24 Simple Network Management Protocol Version 2 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] RFC1444 RFC2580 DRAFT STANDARD DRAFT STANDARD RFC1905 Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2) J. Case K. McCloghrie M. Rose S. Waldbusser January 1996 ASCII 55526 24 OPS-MIB Simple Network Management Protocol Version 2 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] RFC1448 RFC3416 DRAFT STANDARD DRAFT STANDARD RFC1906 Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2) J. Case K. McCloghrie M. Rose S. Waldbusser January 1996 ASCII 27465 13 TRANS-MIB Simple Network Management Protocol Version 2 It is the purpose of this document to define how the SNMPv2 maps onto an initial set of transport domains. [STANDARDS-TRACK] RFC1449 RFC3417 DRAFT STANDARD DRAFT STANDARD RFC1907 Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2) J. Case K. McCloghrie M. Rose S. Waldbusser January 1996 ASCII 34881 20 SNMPv2-MIB Simple Network Management Protocol Version 2 It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity. [STANDARDS-TRACK] RFC1450 RFC3418 DRAFT STANDARD DRAFT STANDARD RFC1908 Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework J. Case K. McCloghrie M. Rose S. Waldbusser January 1996 ASCII 21463 10 COEX-MIB Simple Network Management Protocol Version 2 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] RFC1452 RFC2576 DRAFT STANDARD DRAFT STANDARD RFC1909 An Administrative Infrastructure for SNMPv2 K. McCloghrie Editor February 1996 ASCII 45773 19 SNMPV2AI Simple Network Management Protocol Version 2 It is the purpose of this document, An Administrative Infrastructure for SNMPv2, to define an administrative framework which realizes effective management in a variety of configurations and environments. This memo defines an Experimental Protocol for the Internet community. HISTORIC EXPERIMENTAL RFC1910 User-based Security Model for SNMPv2 G. Waters Editor February 1996 ASCII 98252 44 SNMPV2SM Simple Network Management Protocol Version 2 In this administrative framework, a security model defines the mechanisms used to achieve an administratively-defined level of security for protocol interactions. Although many such security models might be defined, it is the purpose of this document, User-based Security Model for SNMPv2, to define the first, and, as of this writing, only, security model for this administrative framework. This memo defines an Experimental Protocol for the Internet community. HISTORIC EXPERIMENTAL RFC1911 Voice Profile for Internet Mail G. Vaudreuil February 1996 ASCII 50242 22 MIME Multipurpose Internet Mail Extensions ESMTP SMTP Service Extensions 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. RFC2421 RFC2422 RFC2423 EXPERIMENTAL EXPERIMENTAL RFC1912 Common DNS Operational and Configuration Errors D. Barr February 1996 ASCII 38252 16 Domain Name System This memo describes errors often found in both the operation of Domain Name System (DNS) servers, and in the data that these DNS servers contain. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1537 INFORMATIONAL INFORMATIONAL RFC1913 Architecture of the Whois++ Index Service C. Weider J. Fullton S. Spero February 1996 ASCII 33743 16 WHOIS++A Bunyip Information Systems Inc. MCNC Center for Communications The authors describe an architecture for indexing in distributed databases, and apply this to the WHOIS++ protocol. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1914 How to Interact with a Whois++ Mesh P. Faltstrom R. Schoultz C. Weider February 1996 ASCII 17842 10 WHOIS++M distributed databases directory service In the Whois++ architecture [Deutsch94],[Weider94], mesh traversal is done by the client, since each server 'refers' the client to the next appropriate server(s). [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1915 Variance for The PPP Compression Control Protocol and The PPP Encryption Control Protocol F. Kastenholz February 1996 ASCII 14347 7 Point to Point Protocol The PPP Working group has developed two protocols, one to control compression on PPP links; the Compression Control Protocol (CCP), documented in draft-ietf-pppext-compression-04.txt. The second is the Encryption Control Protocol (ECP), used to control encryption on serial links, documented in draft-ietf-pppext-encryption-03.txt. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Document had been mis-titled Connection Control Protocol. BCP0003 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC1916 Enterprise Renumbering: Experience and Information Solicitation H. Berkowitz P. Ferguson W. Leland P. Nesser February 1996 ASCII 16117 8 tools applications Because of the urgent need for, and substantial difficulty in, renumbering IP networks, the PIER working group is compiling a series of documents to assist sites in their renumbering efforts. The intent of these documents is to provide both educational and practical information to the Internet community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1917 An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANA P. Nesser II February 1996 ASCII 23623 10 address space Internet Assigned Numbers Authority IANA This document is an appeal to the Internet community to return unused address space, i.e. any block of consecutive IP prefixes, to the Internet Assigned Numbers Authority (IANA) or any of the delegated registries, for reapportionment. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP0004 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC1918 Address Allocation for Private Internets Y. Rekhter B. Moskowitz D. Karrenberg G. J. de Groot E. Lear February 1996 ASCII 22270 9 TCP/IP network host This document describes address allocation for private internets. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC1627 RFC1597 BCP0005 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC1919 Classical versus Transparent IP Proxies M. Chatel March 1996 ASCII 87374 35 firewalls security This document explains "classical" and "transparent" proxy techniques and attempts to provide rules to help determine when each proxy system may be used without causing problems. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1920 Internet Official Protocol Standards J. Postel March 1996 ASCII 91936 40 status procedure index This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK] RFC1880 RFC2000 HISTORIC STANDARD RFC1921 TNVIP Protocol J. Dujonc March 1996 ASCII 57475 30 The goal of this document specifies a Telnet profile to support VIP terminal emulation allowing the access to the BULL hosts applications through a TCP/IP network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1922 Chinese Character Encoding for Internet Messages HF. Zhu DY. Hu ZG. Wang TC. Kao WCH. Chang M. Crispin March 1996 ASCII 50995 27 transport electronic mail telnet WWW This memo describes methods of transporting Chinese characters in Internet services which transport text, such as electronic mail [RFC-822], network news [RFC-1036], telnet [RFC-854] and the World Wide Web [RFC-1866]. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1923 RIPv1 Applicability Statement for Historic Status J. Halpern S. Bradner March 1996 ASCII 5560 3 Routing Information Protocol RIP Version 1 [RFC-1058] has been declared an historic document. This Applicability statement provides the supporting motivation for that declaration. The primary reason, as described below, is the Classful nature of RIPv1. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1924 A Compact Representation of IPv6 Addresses R. Elz April 01 1996 ASCII 10409 6 encoding This document specifies a more compact representation of IPv6 addresses, which permits encoding in a mere 20 bytes. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1925 The Twelve Networking Truths R. Callon April 01 1996 ASCII 4294 3 fundamentals This memo documents the fundamental truths of networking for the Internet community. This memo does not specify a standard, except in the sense that all standards must implicitly follow the fundamental truths. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1926 An Experimental Encapsulation of IP Datagrams on Top of ATM J. Eriksson April 01 1996 ASCII 2969 2 Acoustical Transmission Media (ATM) This RFC describes a method of encapsulating IP datagrams on top of Acoustical Transmission Media (ATM). This is a non-recommended standard. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1927 Suggested Additional MIME Types for Associating Documents C. Rogers April 01 1996 ASCII 5254 3 media-type Seven new types of MIME types are suggested in this document. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1928 SOCKS Protocol Version 5 M. Leech M. Ganis Y. Lee R. Kuris D. Koblas L. Jones March 1996 ASCII 19741 9 SOCKSV5 firewalls authentication This memo describes a protocol that is an evolution of the previous version of the protocol, version 4 [1]. This new protocol stems from active discussions and prototype implementations. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1929 Username/Password Authentication for SOCKS V5 M. Leech March 1996 ASCII 3568 2 AUTH-SOCKS firewalls authentication The protocol specification for SOCKS Version 5 specifies a generalized framework for the use of arbitrary authentication protocols in the initial socks connection setup. This document describes one of those protocols, as it fits into the SOCKS Version 5 authentication "subnegotiation". [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1930 Guidelines for creation, selection, and registration of an Autonomous System (AS) J. Hawkinson T. Bates March 1996 ASCII 22073 10 routing policy Exterior Gateway Protocol Border Inter-Domain Domain Identifier EGP BGP IDRP This memo discusses when it is appropriate to register and utilize an Autonomous System (AS), and lists criteria for such. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP0006 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC1931 Dynamic RARP Extensions for Automatic Network Address Acquisition D. Brownell April 1996 ASCII 27544 11 Reverse Address Resolution Protocol This memo describes extensions to the Reverse Address Resolution Protocol (RARP [2]) and called Dynamic RARP (DRARP, pronounced D-RARP). This memo provides information for the Internet community. This memo does not define an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1932 IP over ATM: A Framework Document R. Cole D. Shur C. Villamizar April 1996 ASCII 68031 31 end-to-end connectivity It is hoped that this document, in classifying ATM approaches and issues will help to focus the IP over ATM working group's direction.This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1933 Transition Mechanisms for IPv6 Hosts and Routers R. Gilligan E. Nordmark April 1996 ASCII 47005 22 TRANS-IPV6 IPv4 This document specifies IPv4 compatibility mechanisms that can be implemented by IPv6 hosts and routers. [STANDARDS-TRACK] RFC2893 PROPOSED STANDARD PROPOSED STANDARD RFC1934 Ascend's Multilink Protocol Plus (MP+) K. Smith April 1996 ASCII 87072 47 PPP This document proposes an extension to the PPP Multilink Protocol (MP) [1]. Multilink Protocol Plus (MP+) is a new control protocol for managing multiple data links that are bundled by MP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1935 What is the Internet, Anyway? J. Quarterman S. Carl-Mitchell April 1996 ASCII 30369 11 information tutorial This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1936 Implementing the Internet Checksum in Hardware J. Touch B. Parham April 1996 ASCII 36618 21 PLD code UDP TCP This memo presents a techniques for efficiently implementing the Internet Checksum in hardware. It includes PLD code for programming a single, low cost part to perform checksumming at 1.26 Gbps. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1937 "Local/Remote" Forwarding Decision in Switched Data Link Subnetworks Y. Rekhter D. Kandlur May 1996 ASCII 18302 8 IP subnet This document describes extensions to the IP architecture that relaxes these constraints, thus enabling the full utilization of the services provided by SVC-based Data Link subnetworks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1938 A One-Time Password System N. Haller C. Metz May 1996 ASCII 44844 18 OTP authentication S/KEY This document describes a one-time password authentication system (OTP). [STANDARDS-TRACK] RFC2289 PROPOSED STANDARD PROPOSED STANDARD RFC1939 Post Office Protocol - Version 3 J. Myers M. Rose May 1996 ASCII 47018 23 POP3 POP3 The Post Office Protocol - Version 3 (POP3) is intended to permit a workstation to dynamically access a maildrop on a server host in a useful fashion. [STANDARDS-TRACK] RFC1725 RFC1957 RFC2449 STD0053 STANDARD STANDARD RFC1940 Source Demand Routing: Packet Format and Forwarding Specification (Version 1) D. Estrin T. Li Y. Rekhter K. Varadhan D. Zappala May 1996 ASCII 60858 27 SDRP The purpose of SDRP is to support source-initiated selection of routes to complement the route selection provided by existing routing protocols for both inter-domain and intra-domain routes. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1941 Frequently Asked Questions for Schools J. Sellers J. Robichaux May 1996 ASCII 150980 70 FAQ Internet Education The goal of this FYI document, produced by the Internet School Networking (ISN) group in the User Services Area of the Internet Engineering Task Force (IETF), is to act as an introduction to the Internet for faculty, administration, and other school personnel in primary and secondary schools. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1578 FYI0022 INFORMATIONAL INFORMATIONAL RFC1942 HTML Tables D. Raggett May 1996 ASCII 68705 30 HTML-TBL HyperText Markup Language SGML This specification extends HTML to support a wide variety of tables. This memo defines an Experimental Protocol for the Internet community. RFC2854 HISTORIC EXPERIMENTAL RFC1943 Building an X.500 Directory Service in the US B. Jennings May 1996 ASCII 51266 22 White Pages This document provides definition and recommends considerations that must be undertaken to operate a X.500 Directory Service in the United States. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1944 Benchmarking Methodology for Network Interconnect Devices S. Bradner J. McQuaid May 1996 ASCII 66061 30 testing performance This document discusses and defines a number of tests that may be used to describe the performance characteristics of a network interconnecting device. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC2544 INFORMATIONAL INFORMATIONAL RFC1945 Hypertext Transfer Protocol -- HTTP/1.0 T. Berners-Lee R. Fielding H. Frystyk May 1996 ASCII 137582 60 HTTP-1.0 HTTP World-Wide Web application The Hypertext Transfer Protocol (HTTP) is an application-level protocol with the lightness and speed necessary for distributed, collaborative, hypermedia information systems. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1946 Native ATM Support for ST2+ S. Jackowski May 1996 ASCII 50430 21 integrated services ATM Quality of Service QoS This memo describes a working implementation which enables applications to directly invoke ATM services in the following environments: ATM to internet, internet to ATM, and internet to internet across ATM. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1947 Greek Character Encoding for Electronic Mail Messages D. Spinellis May 1996 ASCII 14428 7 character set ISO MIME This document describes a standard encoding for electronic mail [RFC822] containing Greek text and provides implementation guide-lines. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1948 Defending Against Sequence Number Attacks S. Bellovin May 1996 ASCII 13074 6 crypgraphic authentication spoofing IP spoofing attacks based on sequence number spoofing have become a serious threat on the Internet (CERT Advisory CA-95:01). While ubiquitous crypgraphic authentication is the right answer, we propose a simple modification to TCP implementations that should be a very substantial block to the current wave of attacks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1949 Scalable Multicast Key Distribution A. Ballardie May 1996 ASCII 41853 18 SMKD MBONE security authentication This memo provides a scalable solution to the multicast key distribution problem. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1950 ZLIB Compressed Data Format Specification version 3.3 P. Deutsch J-L. Gailly May 1996 ASCII 20502 11 PS 37768 PDF 36393 ZLIB compressed data format checksum This specification defines a lossless compressed data format. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1951 DEFLATE Compressed Data Format Specification version 1.3 P. Deutsch May 1996 ASCII 36944 17 PS 57408 PDF 56620 DEFLATE compressed data format coding This specification defines a lossless compressed data format that compresses data using a combination of the LZ77 algorithm and Huffman coding, with efficiency comparable to the best currently available general-purpose compression methods. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1952 GZIP file format specification version 4.3 P. Deutsch May 1996 ASCII 25036 12 PS 43337 PDF 43211 GZIP compressed data format redundancy check This specification defines a lossless compressed data format that is compatible with the widely used GZIP utility. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1953 Ipsilon Flow Management Protocol Specification for IPv4 Version 1.0 P. Newman W. Edwards R. Hinden E. Hoffman F. Ching Liaw T. Lyon G. Minshall May 1996 ASCII 43749 20 IFMP IP flow routing information The Ipsilon Flow Management Protocol (IFMP), is a protocol for allowing a node to instruct an adjacent node to attach a layer 2 label to a specified IP flow. This document provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1954 Transmission of Flow Labelled IPv4 on ATM Data Links Ipsilon Version 1.0 P. Newman W. Edwards R. Hinden E. Hoffman F. Ching Liaw T. Lyon G. Minshall May 1996 ASCII 16075 8 datagrams IFMP This document specifies the manner for transmitting IPv4 datagrams over an ATM data link, both in a default manner and in the presence of flow labelling via Ipsilon Flow Management Protocol [IFMP]. This document provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1955 New Scheme for Internet Routing and Addressing (ENCAPS) for IPNG R. Hinden June 1996 ASCII 10115 5 IPNG addressing routing This paper proposes a new scheme which I believe is a good medium term solution to the routing and address problems of the internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1956 Registration in the MIL Domain D. Engebretson R. Plzak June 1996 ASCII 2923 2 DoD Department of Defense This RFC describes the policy for the registration of second level domains under the ".MIL" domain. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1957 Some Observations on Implementations of the Post Office Protocol (POP3) R. Nelson June 1996 ASCII 2325 2 client server This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1939 INFORMATIONAL INFORMATIONAL RFC1958 Architectural Principles of the Internet B. Carpenter Editor June 1996 ASCII 17345 8 IAB The Internet and its architecture have grown in evolutionary fashion from modest beginnings, rather than from a Grand Plan. While this process of evolution is one of the main reasons for the technology's success, it nevertheless seems useful to record a snapshot of the current principles of the Internet architecture. This is intended for general guidance and general interest, and is in no way intended to be a formal or invariant reference model. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC3439 INFORMATIONAL INFORMATIONAL RFC1959 An LDAP URL Format T. Howes M. Smith June 1996 ASCII 7243 4 LDAP-URL Lightweight Directory Access Protocol Uniform Resource Locator 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] RFC2255 PROPOSED STANDARD PROPOSED STANDARD RFC1960 A String Representation of LDAP Search Filters T. Howes June 1996 ASCII 5288 3 LDAP-STR Lightweight Directory Access Protocol 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] RFC1558 RFC2254 PROPOSED STANDARD PROPOSED STANDARD RFC1961 GSS-API Authentication Method for SOCKS Version 5 P. McMahon June 1996 ASCII 16036 9 GSSAPI-SOC Generic Security Service Application Program Interface This document provides the specification for the SOCKS V5 GSS-API authentication protocol, and defines a GSS-API-based encapsulation for provision of integrity, authentication and optional confidentiality. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1962 The PPP Compression Control Protocol (CCP) D. Rand June 1996 ASCII 18005 9 PPP-CCP point-to-point protocol data links This document defines a method for negotiating data compression over PPP links. [STANDARDS-TRACK] RFC2153 PROPOSED STANDARD PROPOSED STANDARD RFC1963 PPP Serial Data Transport Protocol (SDTP) K. Schneider S. Venters August 1996 ASCII 38185 20 Point-to-Point Protocol This document describes a new Network level protocol (from the PPP point of view), PPP Serial Data Transport Protocol, that provides encapsulation and an associated control protocol for transporting serial data streams over a PPP link. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1964 The Kerberos Version 5 GSS-API Mechanism J. Linn June 1996 ASCII 47413 20 GSSAPI-KER Generic Security Service Application Program Interface This specification defines protocols, procedures, and conventions to be employed by peers implementing the Generic Security Service Application Program Interface (as specified in RFCs 1508 and 1509) when using Kerberos Version 5 technology (as specified in RFC 1510). [STANDARDS- TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1965 Autonomous System Confederations for BGP P. Traina June 1996 ASCII 13575 7 BGP-ASC Border Gateway Protocol This document describes an extension to BGP which may be used to create a confederation of autonomous systems which is represented as one single autonomous system to BGP peers external to the confederation. This memo defines an Experimental Protocol for the Internet community. RFC3065 EXPERIMENTAL EXPERIMENTAL RFC1966 BGP Route Reflection An alternative to full mesh IBGP T. Bates R. Chandra June 1996 ASCII 14320 7 BGP-RR Border Gateway Protocol autonomous system This document describes the use and design of a method known as "Route Reflection" to alleviate the the need for "full mesh" IBGP. This memo defines an Experimental Protocol for the Internet community. RFC2796 EXPERIMENTAL EXPERIMENTAL RFC1967 PPP LZS-DCP Compression Protocol (LZS-DCP) K. Schneider R. Friend August 1996 ASCII 40039 18 Point-to-Point Protocol Compression Control CCP This document describes the use of the Stac LZS data compression algorithm for compressing PPP encapsulated packets, using a DCP header [6]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1968 The PPP Encryption Control Protocol (ECP) G. Meyer June 1996 ASCII 20781 11 PPP-ECP Point-to-Point Protocol data This document defines a method for negotiating data encryption over PPP links. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1969 The PPP DES Encryption Protocol (DESE) K. Sklower G. Meyer June 1996 ASCII 20383 10 Point-to-Point Protocol encapsulated packets This document provides specific details for the use of the DES standard [5, 6] for encrypting PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC2419 INFORMATIONAL INFORMATIONAL RFC1970 Neighbor Discovery for IP Version 6 (IPv6) T. Narten E. Nordmark W. Simpson August 1996 ASCII 197632 82 Internet Protocol This document specifies the Neighbor Discovery protocol for IP Version 6. [STANDARDS-TRACK] RFC2461 PROPOSED STANDARD PROPOSED STANDARD RFC1971 IPv6 Stateless Address Autoconfiguration S. Thomson T. Narten August 1996 ASCII 56890 23 Internet Protocol link-local address Duplicate Address Detection procedure This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. [STANDARDS-TRACK] RFC2462 PROPOSED STANDARD PROPOSED STANDARD RFC1972 A Method for the Transmission of IPv6 Packets over Ethernet Networks M. Crawford August 1996 ASCII 6353 4 IPV6-ETHER Internet Protocol frame format transmission 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] RFC2464 PROPOSED STANDARD PROPOSED STANDARD RFC1973 PPP in Frame Relay W. Simpson June 1996 ASCII 14780 10 PPP-FRAME Point-to-Point Protocol encapsulated packets This document describes the use of Frame Relay for framing PPP encapsulated packets. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1974 PPP Stac LZS Compression Protocol R. Friend W. Simpson August 1996 ASCII 45267 20 PPP-STAC Point-to-Point Protocol Compression Control CCP This document describes the use of the Stac LZS data compression algorithm, with single or multiple compression histories, for compressing PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1975 PPP Magnalink Variable Resource Compression D. Schremp J. Black J. Weiss August 1996 ASCII 8655 6 PPP-MAG Point-to-Point Protocol MVRCA The Magnalink Variable Resource Compression Algorithm (MVRCA) allows a wide range of interoperable compression implementations whose performance characteristics are a function of available CPU and memory resources. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1976 PPP for Data Compression in Data Circuit-Terminating Equipment (DCE) K. Schneider S. Venters August 1996 ASCII 19781 10 PPP-DCE Point-to-Point Protocol LCP extension This document defines a specific set of parameters for these protocols and an LCP extension to define a standard way of using PPP for data compression of serial data in Data Circuit-Terminating Equipment (DCE). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1977 PPP BSD Compression Protocol V. Schryver August 1996 ASCII 50747 25 PPP-BSD Point-to-Point Protocol Unix Compress This document describes the use of the Unix Compress compression protocol for compressing PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1978 PPP Predictor Compression Protocol D. Rand August 1996 ASCII 17424 9 PPP-PRED Point-to-Point Protocol This document describes the use of the Predictor data compression algorithm for compressing PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1979 PPP Deflate Protocol J. Woods August 1996 ASCII 18803 10 PPP-DEFL Point-to-Point Protocol Compression Control This document describes the use of the PPP Deflate compression protocol for compressing PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1980 A Proposed Extension to HTML : Client-Side Image Maps J. Seidman August 1996 ASCII 13448 7 HyperText Markup Language Uniform Identifier URI This document specifies an extension to the HTML language, referred to as "Client-Side Image Maps," which resolves some limitations. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC2854 HISTORIC INFORMATIONAL RFC1981 Path MTU Discovery for IP version 6 J. McCann S. Deering J. Mogul August 1996 ASCII 34088 15 MTU-IPV6 Internet Protocol This document describes Path MTU Discovery for IP version 6. It is largely derived from RFC 1191, which describes Path MTU Discovery for IP version 4. [STANDARDS-TRACK] updated to draft standard 8/20/98 DRAFT STANDARD PROPOSED STANDARD RFC1982 Serial Number Arithmetic R. Elz R. Bush August 1996 ASCII 14440 6 SNA domain name system DNS The DNS has long relied upon serial number arithmetic, a concept which has never really been defined, certainly not in an IETF document, though which has been widely understood. This memo supplies the missing definition. It is intended to update RFC1034 and RFC1035. [STANDARDS- TRACK] RFC1034 RFC1035 PROPOSED STANDARD PROPOSED STANDARD RFC1983 Internet Users' Glossary G. Malkin Editor August 1996 ASCII 123008 62 basic terms acronyms There are many networking glossaries in existence. This glossary concentrates on terms which are specific to the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1392 FYI0018 INFORMATIONAL INFORMATIONAL RFC1984 IAB and IESG Statement on Cryptographic Technology and the Internet IAB IESG August 1996 ASCII 10738 5 security privacy The Internet Architecture Board (IAB) and the Internet Engineering Steering Group (IESG), the bodies which oversee architecture and standards for the Internet, are concerned by the need for increased protection of international commercial transactions on the Internet, and by the need to offer all Internet users an adequate degree of privacy. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1985 SMTP Service Extension for Remote Message Queue Starting J. De Winter August 1996 ASCII 14815 7 SMTP-ETRN Simple ETRN Mail Transfer Protocol This memo defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to start the processing of its queues for messages to go to a given host. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1986 Experiments with a Simple File Transfer Protocol for Radio Links using Enhanced Trivial File Transfer Protocol (ETFTP) W. Polites W. Wollman D. Woo R. Langan August 1996 ASCII 49772 21 ETFTP TFTP NETBLT This document is a description of the Enhanced Trivial File Transfer Protocol (ETFTP). This protocol is an experimental implementation of the NETwork BLock Transfer Protocol (NETBLT), RFC 998 [1], as a file transfer application program. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC1987 Ipsilon's General Switch Management Protocol Specification Version 1.1 P. Newman W. Edwards R. Hinden E. Hoffman F. Ching Liaw T. Lyon G. Minshall August 1996 ASCII 105821 44 GSMP ATM switch The General Switch Management Protocol (GSMP), is a general purpose protocol to control an ATM switch. GSMP allows a controller to establish and release connections across the switch; add and delete leaves on a point-to-multipoint connection; manage switch ports; request configuration information; and request statistics. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC2297 INFORMATIONAL INFORMATIONAL RFC1988 Conditional Grant of Rights to Specific Hewlett-Packard Patents In Conjunction With the Internet Engineering Task Force's Internet-Standard Network Management Framework G. McAnally D. Gilbert J. Flick August 1996 ASCII 3821 2 HP This grant is made to help facilitate inclusion of certain patented search address technology covering network device mapping in IETF standards-track Management Information Base (MIB) modules. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1989 PPP Link Quality Monitoring W. Simpson August 1996 ASCII 29289 16 PPP-LINK Point-to-Point Protocol This document defines a protocol for generating Link-Quality-Reports. [STANDARDS-TRACK] RFC1333 DRAFT STANDARD DRAFT STANDARD RFC1990 The PPP Multilink Protocol (MP) K. Sklower B. Lloyd G. McGregor D. Carr T. Coradetti August 1996 ASCII 53271 24 PPP-MP Point-to-Point Protocol datagrams This document proposes a method for splitting, recombining and sequencing datagrams across multiple logical data links. [STANDARDS- TRACK] RFC1717 DRAFT STANDARD DRAFT STANDARD RFC1991 PGP Message Exchange Formats D. Atkins W. Stallings P. Zimmermann August 1996 ASCII 46255 21 PGP-MEF Pretty Good Privacy encryption electronic mail 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. INFORMATIONAL INFORMATIONAL RFC1992 The Nimrod Routing Architecture I. Castineyra N. Chiappa M. Steenstrup August 1996 ASCII 59848 27 scalable internetwork Nimrod is a scalable routing architecture designed to accommodate a continually expanding and diversifying internetwork. First suggested by Noel Chiappa, the Nimrod architecture has undergone revision and refinement through the efforts of the Nimrod working group of the IETF. In this document, we present a detailed description of this architecture. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1993 PPP Gandalf FZA Compression Protocol A. Barbir D. Carr W. Simpson August 1996 ASCII 9811 7 Point-to-Point Protocol This document describes the use of the Gandalf FZA data compression algorithm [3] for compressing PPP encapsulated packets. This memo provides information for the Internet community. It does not specify an Internet standard. INFORMATIONAL INFORMATIONAL RFC1994 PPP Challenge Handshake Authentication Protocol (CHAP) W. Simpson August 1996 ASCII 24094 13 PPP-CHAP Point-to-Point Protocol cryptology This document defines a method for Authentication using PPP, which uses a random Challenge, with a cryptographically hashed Response which depends upon the Challenge and a secret key. [STANDARDS-TRACK] RFC1334 RFC2484 DRAFT STANDARD DRAFT STANDARD RFC1995 Incremental Zone Transfer in DNS M. Ohta August 1996 ASCII 16810 8 DNS-IZT Domain Name System IXFR This document proposes extensions to the DNS protocols to provide an incremental zone transfer (IXFR) mechanism. [STANDARDS-TRACK] RFC1035 PROPOSED STANDARD PROPOSED STANDARD RFC1996 A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY) P. Vixie August 1996 ASCII 15247 7 DNS-NOTIFY Domain Name System This memo describes the NOTIFY opcode for DNS, by which a master server advises a set of slave servers that the master's data has been changed and that a query should be initiated to discover the new data. [STANDARDS-TRACK] RFC1035 PROPOSED STANDARD PROPOSED STANDARD RFC1997 BGP Communities Attribute R. Chandra P. Traina T. Li August 1996 ASCII 8275 5 BGP-COMM Border Gateway Protocol This document describes an extension to BGP which may be used to pass additional information to both neighboring and remote BGP peers. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC1998 An Application of the BGP Community Attribute in Multi-home Routing E. Chen T. Bates August 1996 ASCII 16953 9 Border Gateway Protocol This document presents an application of the BGP community attribute [2] in simplifying the implementation and configuration of routing policies in the multi-provider Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC1999 Request for Comments Summary RFC Numbers 1900-1999 J. Elliott January 1997 ASCII 39819 20 Index INFORMATIONAL INFORMATIONAL RFC2000 Internet Official Protocol Standards J. Postel Editor February 1997 ASCII 121356 56 status procedure index 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. RFC1920 RFC2200 HISTORIC STANDARD RFC2001 TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms W. Stevens January 1997 ASCII 12981 6 TCPSLOWSRT Transmission Control Protocol Modern implementations of TCP contain four intertwined algorithms that have never been fully documented as Internet standards: slow start, congestion avoidance, fast retransmit, and fast recovery. [STANDARDS- TRACK] RFC2581 PROPOSED STANDARD PROPOSED STANDARD RFC2002 IP Mobility Support C. Perkins Editor October 1996 ASCII 193103 79 MOBILEIPSUPIP Internet Protocol This document specifies protocol enhancements that allow transparent routing of IP datagrams to mobile nodes in the Internet. [STANDARDS- TRACK] RFC3220 RFC2290 PROPOSED STANDARD PROPOSED STANDARD RFC2003 IP Encapsulation within IP C. Perkins October 1996 ASCII 30291 14 IPENCAPIP Internet Protocol This document specifies a method by which an IP datagram may be encapsulated (carried as payload) within an IP datagram. [STANDARDS- TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2004 Minimal Encapsulation within IP C. Perkins October 1996 ASCII 12202 6 MINI-IP Internet Protocol This document specifies a method by which an IP datagram may be encapsulated (carried as payload) within an IP datagram, with less overhead than "conventional" IP encapsulation that adds a second IP header to each encapsulated datagram. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2005 Applicability Statement for IP Mobility Support J. Solomon October 1996 ASCII 10509 5 Internet Protocol As required by [RFC 1264], this report discusses the applicability of Mobile IP to provide host mobility in the Internet. In particular, this document describes the key features of Mobile IP and shows how the requirements for advancement to Proposed Standard RFC have been satisfied. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2006 The Definitions of Managed Objects for IP Mobility Support using SMIv2 D. Cong M. Hamlen C. Perkins October 1996 ASCII 95030 52 MOBILEIPMIB Mobile Internet Protocol MIB Managed Information Base This memo defines the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the Mobile Node, Foreign Agent and Home Agent of the Mobile IP Protocol. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2007 Catalogue of Network Training Materials J. Foster M. Isaacs M. Prior October 1996 ASCII 78941 55 TRAINMAT IETF TERENA The purpose of this document is to provide a catalogue of quality Network Training Materials for use by Internet trainers in training their users. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. FYI0029 INFORMATIONAL INFORMATIONAL RFC2008 Implications of Various Address Allocation Policies for Internet Routing Y. Rekhter T. Li October 1996 ASCII 34717 13 IP unicast The purpose of this document is to articulate certain relevant fundamental technical issues that must be considered in formulating unicast address allocation and management policies for the Public Internet, and to provide recommendations with respect to these policies. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP0007 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2009 GPS-Based Addressing and Routing T. Imielinski J. Navas November 1996 ASCII 66229 27 GPS-AR domain names geographic This document describes a possible experiment with geographic addresses. It uses several specific IP addresses and domain names in the discussion as concrete examples to aid in understanding the concepts. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC2010 Operational Criteria for Root Name Servers B. Manning P. Vixie October 1996 ASCII 14870 7 host hardware This document specifies the operational requirements of root name servers, including host hardware capacities, name server software revisions, network connectivity, and physical environment. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC2870 INFORMATIONAL INFORMATIONAL RFC2011 SNMPv2 Management Information Base for the Internet Protocol using SMIv2 K. McCloghrie Editor November 1996 ASCII 31168 18 MIB-IP IP Simple Network Management Protocol MIB 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] RFC1213 PROPOSED STANDARD PROPOSED STANDARD RFC2012 SNMPv2 Management Information Base for the Transmission Control Protocol using SMIv2 K. McCloghrie Editor November 1996 ASCII 16792 10 MIB-TCP TCP Simple Network Management Protocol MIB This document is the MIB module which defines managed objects for managing implementations of the Transmission Control Protocol (TCP). [STANDARDS-TRACK] RFC4022 RFC1213 PROPOSED STANDARD PROPOSED STANDARD RFC2013 SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2 K. McCloghrie Editor November 1996 ASCII 9333 6 MIB-UDP Simple Network Management Protocol MIB UDP This document is the MIB module which defines managed objects for managing implementations of the User Datagram Protocol (UDP). [STANDARDS-TRACK] RFC1213 PROPOSED STANDARD PROPOSED STANDARD RFC2014 IRTF Research Group Guidelines and Procedures A. Weinrib J. Postel October 1996 ASCII 27507 13 Internet Research Task Force This document describes the guidelines and procedures for formation and operation of IRTF Research Groups. It describes the relationship between IRTF participants, Research Groups, the Internet Research Steering Group (IRSG) and the Internet Architecture Board (IAB). This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP0008 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2015 MIME Security with Pretty Good Privacy (PGP) M. Elkins October 1996 ASCII 14223 8 MIME-PGP Authentication Encryption This document describes how Pretty Good Privacy (PGP) can be used to provide privacy and authentication using the Multipurpose Internet Mail Extensions (MIME) security content types described in RFC1847. [STANDARDS-TRACK] RFC3156 PROPOSED STANDARD PROPOSED STANDARD RFC2016 Uniform Resource Agents (URAs) L. Daigle P. Deutsch B. Heelan C. Alpaugh M. Maclachlan October 1996 ASCII 38355 21 URAS This paper presents an experimental architecture for an agent system that provides sophisticated Internet information access and management. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC2017 Definition of the URL MIME External-Body Access-Type N. Freed K. Moore A. Cargille October 1996 ASCII 9000 5 URL-ACC Uniform Resource Locators Multipurpose Internet Message Extensions This memo defines a new access-type for message/external-body MIME parts for Uniform Resource Locators (URLs). [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2018 TCP Selective Acknowledgement Options M. Mathis J. Mahdavi S. Floyd A. Romanow October 1996 ASCII 25671 12 TCP-ACK Transmission Control Protocol SACK This memo proposes an implementation of SACK and discusses its performance and related issues. [STANDARDS-TRACK] RFC1072 PROPOSED STANDARD PROPOSED STANDARD RFC2019 Transmission of IPv6 Packets Over FDDI M. Crawford October 1996 ASCII 12344 6 IPV6-FDDI frame format Fiber Distributed Data Interface 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] RFC2467 PROPOSED STANDARD PROPOSED STANDARD RFC2020 IEEE 802.12 Interface MIB J. Flick October 1996 ASCII 72135 31 802.12-MIB Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing network interfaces based on IEEE 802.12. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2021 Remote Network Monitoring Management Information Base Version 2 using SMIv2 S. Waldbusser January 1997 ASCII 262223 130 RMON-MIB RMON MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2022 Support for Multicast over UNI 3.0/3.1 based ATM Networks G. Armitage November 1996 ASCII 189219 82 MULTI-UNI Asynchronous Transfer Mode This memo describes a mechanism to support the multicast needs of Layer 3 protocols in general, and describes its application to IP multicasting in particular. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2023 IP Version 6 over PPP D. Haskin E. Allen October 1996 ASCII 20275 10 IPV6-PPP Internet Protocol Point IPv6 This document defines the method for transmission of IP Version 6 [2] packets over PPP links as well as the Network Control Protocol (NCP) for establishing and configuring the IPv6 over PPP. [STANDARDS-TRACK] RFC2472 PROPOSED STANDARD PROPOSED STANDARD RFC2024 Definitions of Managed Objects for Data Link Switching using SMIv2 D. Chen Editor P. Gayek S. Nix October 1996 ASCII 173952 90 DLSW-MIB MIB DLSW Management Information Base This specification defines an extension to the Management Information Base (MIB) for use with SNMP-based network management. In particular, it defines objects for configuring, monitoring, and controlling Data Link Switches (DLSw). [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2025 The Simple Public-Key GSS-API Mechanism (SPKM) C. Adams October 1996 ASCII 101692 45 SPKM This specification defines protocols, procedures, and conventions to be employed by peers implementing the Generic Security Service Application Program Interface (as specified in RFCs 1508 and 1509) when using the Simple Public-Key Mechanism. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2026 The Internet Standards Process -- Revision 3 S. Bradner October 1996 ASCII 86731 36 Protocols copyrights intellectual property This memo documents the process used by the Internet community for the standardization of protocols and procedures. It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC1602 RFC3667 RFC3668 RFC3932 RFC3979 RFC3978 BCP0009 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2027 IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees J. Galvin October 1996 ASCII 24207 11 Internet Architecture Board Engineering Steering Group The process by which the members of the IAB and IESG are selected, confirmed, and recalled has been exercised four times since its formal creation. The evolution of the process has relied principally on oral tradition as a means by which the lessons learned could be passed on to successive committees. This document is a self-consistent, organized compilation of the process as it is known today. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC2282 INFORMATIONAL BEST CURRENT PRACTICE RFC2028 The Organizations Involved in the IETF Standards Process R. Hovey S. Bradner October 1996 ASCII 13865 7 Internet Engineering Task Force This document describes the individuals and organizations involved in the IETF. This includes descriptions of the IESG, the IETF Working Groups and the relationship between the IETF and the Internet Society. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC3668 RFC3979 BCP0011 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2029 RTP Payload Format of Sun's CellB Video Encoding M. Speer D. Hoffman October 1996 ASCII 11216 6 RTP-CELLB Real Time Transport Protocol This memo describes a packetization scheme for the CellB video encoding. The scheme proposed allows applications to transport CellB video flows over protocols used by RTP. This document is meant for implementors of video applications that want to use RTP and CellB. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2030 Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI D. Mills October 1996 ASCII 48620 18 NTP SNTP time computer clock synchronization This memorandum describes the Simple Network Time Protocol (SNTP) Version 4, which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1769 INFORMATIONAL INFORMATIONAL RFC2031 IETF-ISOC relationship E. Huizer October 1996 ASCII 8816 4 Internet Society Engineering Task Force This memo summarises the issues on IETF - ISOC relationships as the have been discussed by the Poised Working Group. The purpose of the document is to gauge consensus on these issues. And to allow further discussions where necessary. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2032 RTP Payload Format for H.261 Video Streams T. Turletti C. Huitema October 1996 ASCII 27488 11 RTP-H.261 Real Time Transport Protocol 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] PROPOSED STANDARD PROPOSED STANDARD RFC2033 Local Mail Transfer Protocol J. Myers October 1996 ASCII 14711 7 LMTP SMTP Simple Mail Transfer Protocol SMTP [SMTP] [HOST-REQ] and its service extensions [ESMTP] provide a mechanism for transferring mail reliably and efficiently. The design of the SMTP protocol effectively requires the server to manage a mail delivery queue. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2034 SMTP Service Extension for Returning Enhanced Error Codes N. Freed October 1996 ASCII 10460 6 SMTP-ENH Simple Mail Transfer Protocol This memo defines an extension to the SMTP service [RFC-821, RFC-1869] whereby an SMTP server augments its responses with the enhanced mail system status codes defined in RFC 1893. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2035 RTP Payload Format for JPEG-compressed Video L. Berc W. Fenner R. Frederick S. McCanne October 1996 ASCII 30079 16 RTP-JPEG Real Time Transport Protocol Joint Photographic Experts Group This memo describes the RTP payload format for JPEG video streams. The packet format is optimized for real-time video streams where codec parameters change rarely from frame to frame. [STANDARDS-TRACK] RFC2435 PROPOSED STANDARD PROPOSED STANDARD RFC2036 Observations on the use of Components of the Class A Address Space within the Internet G. Huston October 1996 ASCII 20743 9 Internet Assigned Numbers Authority IANA This document is a commentary on the recommendation that IANA commence allocation of the presently unallocated components of the Class A address space to registries, for deployment within the Internet as class-less address blocks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2037 Entity MIB using SMIv2 K. McCloghrie A. Bierman October 1996 ASCII 74362 35 ENTITY-MIB Management Information Base SNMP 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] RFC2737 PROPOSED STANDARD PROPOSED STANDARD RFC2038 RTP Payload Format for MPEG1/MPEG2 Video D. Hoffman G. Fernando V. Goyal October 1996 ASCII 23266 11 Real Time Transport Protocol This memo describes a packetization scheme for MPEG video and audio streams. The scheme proposed can be used to transport such a video or audio flow over the transport protocols supported by RTP. [STANDARDS- TRACK] RFC2250 PROPOSED STANDARD PROPOSED STANDARD RFC2039 Applicability of Standards Track MIBs to Management of World Wide Web Servers C. Kalbfleisch November 1996 ASCII 31966 14 Management Information Base HTTP This document was produced at the request of the Network Management Area Director following the HTTP-MIB BOF at the 35th IETF meeting to report on the applicability of the existing standards track MIBs to management of WWW servers. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2040 The RC5, RC5-CBC, RC5-CBC-Pad, and RC5-CTS Algorithms R. Baldwin R. Rivest October 1996 ASCII 54598 29 RC5 Cipher Block Chaining CBC This document defines four ciphers with enough detail to ensure interoperability between different implementations. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2041 Mobile Network Tracing B. Noble G. Nguyen M. Satyanarayanan R. Katz October 1996 ASCII 64688 27 IP Internet Protocol This RFC argues that mobile network tracing provides both tools to improve our understanding of wireless channels, as well as to build realistic, repeatable testbeds for mobile software and systems. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2042 Registering New BGP Attribute Types B. Manning January 1997 ASCII 4001 3 Border Gateway Protocol This document describes the process for creating new BGP attribute type codes. Basic attribute type codes are described in RFC 1771, pages 12 through 15. These, and new attribute type codes that are used in the Internet are registered with the IANA. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2043 The PPP SNA Control Protocol (SNACP) A. Fuqua October 1996 ASCII 13719 7 PPP-SNACP Point-to-point protocol systems network architecture This document defines the Network Control Protocols for establishing and configuring Systems Network Architecture (SNA) over PPP and SNA over LLC 802.2 over PPP. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2044 UTF-8, a transformation format of Unicode and ISO 10646 F. Yergeau October 1996 ASCII 11932 6 UCS Transformation Format The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993 jointly define a 16 bit character set which encompasses most of the world's writing systems. UTF-8, the object of this memo, has the characteristic of preserving the full US-ASCII range. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC2279 INFORMATIONAL INFORMATIONAL RFC2045 Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies N. Freed N. Borenstein November 1996 ASCII 72932 31 MIME media types headers This initial document specifies the various headers used to describe the structure of MIME messages. [STANDARDS-TRACK] RFC1521 RFC1522 RFC1590 RFC2184 RFC2231 DRAFT STANDARD DRAFT STANDARD RFC2046 Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types N. Freed N. Borenstein November 1996 ASCII 105854 44 MIME-MEDIA headers structure This second document defines the general structure of the MIME media typing system and defines an initial set of media types. [STANDARDS- TRACK] RFC1521 RFC1522 RFC1590 RFC2646 RFC3798 DRAFT STANDARD DRAFT STANDARD RFC2047 MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text K. Moore November 1996 ASCII 33262 15 MIME-MSG media type This particular document is the third document in the series. It describes extensions to RFC 822 to allow non-US-ASCII text data in Internet mail header fields. [STANDARDS-TRACK] RFC1521 RFC1522 RFC1590 RFC2184 RFC2231 DRAFT STANDARD DRAFT STANDARD RFC2048 Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures N. Freed J. Klensin J. Postel November 1996 ASCII 45033 21 media types external body access content-transfer-encodings This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages. This fourth document, RFC 2048, specifies various IANA registration procedures for some MIME facilities. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC1521 RFC1522 RFC1590 RFC3023 BCP0013 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2049 Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples N. Freed N. Borenstein November 1996 ASCII 51207 24 MIME-CONF media type message formats This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages. This fifth and final document describes MIME conformance criteria as well as providing some illustrative examples of MIME message formats, acknowledgements, and the bibliography. [STANDARDS-TRACK] RFC1521 RFC1522 RFC1590 DRAFT STANDARD DRAFT STANDARD RFC2050 Internet Registry IP Allocation Guidelines K. Hubbard M. Kosters D. Conrad D. Karrenberg J. Postel November 1996 ASCII 28975 13 Internet Addresses Network Numbers This document describes the registry system for the distribution of globally unique Internet address space and registry operations. Particularly this document describes the rules and guidelines governing the distribution of this address space. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC1466 BCP0012 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2051 Definitions of Managed Objects for APPC using SMIv2 M. Allen B. Clouston Z. Kielczewski W. Kwan B. Moore October 1996 ASCII 239359 124 SNANAU-APP This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing the configuration, monitoring and controlling of network devices with APPC (Advanced Program-to-Program Communications) capabilities. This memo identifies managed objects for the SNA LU6.2 protocols. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2052 A DNS RR for specifying the location of services (DNS SRV) A. Gulbrandsen P. Vixie October 1996 ASCII 19257 10 DNS-SRV Domain Name System This document describes a DNS RR which specifies the location of the server(s) for a specific protocol and domain (like a more general form of MX). This memo defines an Experimental Protocol for the Internet community. RFC2782 EXPERIMENTAL EXPERIMENTAL RFC2053 The AM (Armenia) Domain E. Der-Danieliantz October 1996 ASCII 4128 3 Top Level Domain Country Code The AM Domain is an official Internet top-level domain of Armenia. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2054 WebNFS Client Specification B. Callaghan October 1996 ASCII 36354 16 Network Fil System This document describes a lightweight binding mechanism that allows NFS clients to obtain service from WebNFS-enabled servers with a minimum of protocol overhead. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2055 WebNFS Server Specification B. Callaghan October 1996 ASCII 20498 10 Network Fil System This document describes the specifications for a server of WebNFS clients. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2056 Uniform Resource Locators for Z39.50 R. Denenberg J. Kunze D. Lynch November 1996 ASCII 14204 7 URLZ39.50 URL information retrieval Z39.50 is an information retrieval protocol that does not fit neatly into a retrieval model designed primarily around the stateless fetch of data. Instead, it models a general user inquiry as a session-oriented, multi-step task, any step of which may be suspended temporarily while the server requests additional parameters from the client before continuing. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2057 Source Directed Access Control on the Internet S. Bradner November 1996 ASCII 56664 20 content regulation deposition This memo was developed from a deposition that I submitted as part of a challenge to the Communications Decency Act of 1996, part of the Telecommunications Reform Act of 1996. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2058 Remote Authentication Dial In User Service (RADIUS) C. Rigney A. Rubens W. Simpson S. Willens January 1997 ASCII 118880 64 encryption NAS Network Access Server This document describes a protocol for carrying authentication, authorization, and configuration information between a Network Access Server which desires to authenticate its links and a shared Authentication Server. [STANDARDS-TRACK] RFC2138 PROPOSED STANDARD PROPOSED STANDARD RFC2059 RADIUS Accounting C. Rigney January 1997 ASCII 44237 25 remote authentication dial in user service encryption This document describes a protocol for carrying accounting information between a Network Access Server and a shared Accounting Server. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC2139 INFORMATIONAL INFORMATIONAL RFC2060 Internet Message Access Protocol - Version 4rev1 M. Crispin December 1996 ASCII 166513 82 IMAPV4 IMAP electronic mail Internet Message Access Protocol The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1) allows a client to access and manipulate electronic mail messages on a server. [STANDARDS-TRACK] RFC1730 RFC3501 PROPOSED STANDARD PROPOSED STANDARD RFC2061 IMAP4 Compatibility with IMAP2bis M. Crispin December 1996 ASCII 5867 3 IMAP electronic mail Internet Message Access Protocol This document is intended to be read along with RFC 1176 and the most recent IMAP4 specification (RFC 2060) to assist implementors in creating an IMAP4 implementation to interoperate with implementations that conform to earlier specifications. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1730 INFORMATIONAL INFORMATIONAL RFC2062 Internet Message Access Protocol - Obsolete Syntax M. Crispin December 1996 ASCII 14222 8 IMAP electronic mail This document describes obsolete syntax which may be encountered by IMAP4 implementations which deal with older versions of the Internet Mail Access Protocol. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2063 Traffic Flow Measurement: Architecture N. Brownlee C. Mills G. Ruth January 1997 ASCII 89092 37 TFM-ARCH network data This document describes an architecture for the measurement and reporting of network traffic flows, discusses how this relates to an overall network traffic flow architecture, and describes how it can be used within the Internet. This memo defines an Experimental Protocol for the Internet community. RFC2722 EXPERIMENTAL EXPERIMENTAL RFC2064 Traffic Flow Measurement: Meter MIB N. Brownlee January 1997 ASCII 67520 38 METER-MIB Management Information Base Network Data This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, this memo defines managed objects used for obtaining traffic flow information from network traffic meters. This memo defines an Experimental Protocol for the Internet community. RFC2720 EXPERIMENTAL EXPERIMENTAL RFC2065 Domain Name System Security Extensions D. Eastlake 3rd C. Kaufman January 1997 ASCII 97718 41 DNS-SEC DNS authentication encryption The Domain Name System (DNS) has become a critical operational part of the Internet infrastructure yet it has no strong security mechanisms to assure data integrity or authentication. Extensions to the DNS are described that provide these services to security aware resolvers or applications through the use of cryptographic digital signatures. [STANDARDS-TRACK] RFC2535 RFC1034 RFC1035 PROPOSED STANDARD PROPOSED STANDARD RFC2066 TELNET CHARSET Option R. Gellens January 1997 ASCII 26088 12 TOPT-CHARSET character set application This document specifies a mechanism for passing character set and translation information between a TELNET client and server. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC2067 IP over HIPPI J. Renwick January 1997 ASCII 66702 30 IP-HIPPI ANSI High-Performance Parallel Interface Internet Protocol ANSI Standard X3.218-1993 (HIPPI-LE[3]) defines the encapsulation of IEEE 802.2 LLC PDUs and, by implication, IP on HIPPI. This memo is a revision of RFC 1374, "IP and ARP on HIPPI", and is intended to replace it in the Standards Track. [STANDARDS-TRACK] DRAFT STANDARD DRAFT STANDARD RFC2068 Hypertext Transfer Protocol -- HTTP/1.1 R. Fielding J. Gettys J. Mogul H. Frystyk T. Berners-Lee January 1997 ASCII 378114 162 HTTP-1.1 World Wide Web WWW hypermedia The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. [STANDARDS-TRACK] RFC2616 PROPOSED STANDARD PROPOSED STANDARD RFC2069 An Extension to HTTP : Digest Access Authentication J. Franks P. Hallam-Baker J. Hostetler P. Leach A. Luotonen E. Sink L. Stewart January 1997 ASCII 41733 18 DAA Hypertext Transfer Protocol The protocol referred to as "HTTP/1.0" includes the specification for a Basic Access Authentication scheme. This scheme is not considered to be a secure method of user authentication, as the user name and password are passed over the network as clear text. A specification for a different authentication scheme is needed to address this severe limitation. This document provides specification for such a scheme, referred to as "Digest Access Authentication". [STANDARDS-TRACK] RFC2617 PROPOSED STANDARD PROPOSED STANDARD RFC2070 Internationalization of the Hypertext Markup Language F. Yergeau G. Nicol G. Adams M. Duerst January 1997 ASCII 91887 43 HTML-INT HTML WWW World Wide Web This document is meant to address the issue of the internationalization (i18n, i followed by 18 letters followed by n) of HTML by extending the specification of HTML and giving additional recommendations for proper internationalization support. [STANDARDS-TRACK] RFC2854 HISTORIC PROPOSED STANDARD RFC2071 Network Renumbering Overview: Why would I want it and what is it anyway? P. Ferguson H. Berkowitz January 1997 ASCII 33218 14 Internet Enterprise Connecting Routers This document attempts to clearly define the concept of network renumbering and discuss some of the more pertinent reasons why an organization would have a need to do so. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2072 Router Renumbering Guide H. Berkowitz January 1997 ASCII 110591 48 Internet Enterprise Connecting Routers Routers interact with numerous network infrastructure servers, including DNS and SNMP. These interactions, not just the pure addressing and routing structure, must be considered as part of router renumbering. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2073 An IPv6 Provider-Based Unicast Address Format Y. Rekhter P. Lothberg R. Hinden S. Deering J. Postel January 1997 ASCII 15549 7 IPV6-UNI This document defines an IPv6 provider-based unicast address format for use in the Internet. [STANDARDS-TRACK] RFC2374 PROPOSED STANDARD PROPOSED STANDARD RFC2074 Remote Network Monitoring MIB Protocol Identifiers A. Bierman R. Iddon January 1997 ASCII 81262 43 RMON-MIB RMON Management Information Base 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] RFC2895 PROPOSED STANDARD PROPOSED STANDARD RFC2075 IP Echo Host Service C. Partridge January 1997 ASCII 12536 5 IP-Echo Internet Protocol datagram This memo describes how to implement an IP echo host. IP echo hosts send back IP datagrams after exchanging the source and destination IP addresses. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC2076 Common Internet Message Headers J. Palme February 1997 ASCII 47639 27 email This memo contains a table of commonly occurring headers in headings of e-mail messages. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2077 The Model Primary Content Type for Multipurpose Internet Mail Extensions S. Nelson C. Parks Mitra January 1997 ASCII 30158 13 MIME-MODEL MIME Media Type Content Type The purpose of this memo is to propose an update to Internet RFC 2045 to include a new primary content-type to be known as "model". [STANDARDS- TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2078 Generic Security Service Application Program Interface, Version 2 J. Linn January 1997 ASCII 185990 85 GSSAP Authentication Cryptology Data integrity The Generic Security Service Application Program Interface (GSS-API), as defined in RFC-1508, provides security services to callers in a generic fashion, supportable with a range of underlying mechanisms and technologies and hence allowing source-level portability of applications to different environments. [STANDARDS-TRACK] RFC1508 RFC2743 PROPOSED STANDARD PROPOSED STANDARD RFC2079 Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs) M. Smith January 1997 ASCII 8757 5 URI-ATT URL Universal Resource Locators Directory This document builds on the experimentation to date and defines a new attribute type and an auxiliary object class to allow URIs, including URLs, to be stored in directory entries in a standard way. [STANDARDS- TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2080 RIPng for IPv6 G. Malkin R. Minnear January 1997 ASCII 47534 19 RIPNG-IPV6 Routing Information Protocol Internet This document specifies a routing protocol for an IPv6 internet. It is based on protocols and algorithms currently in wide use in the IPv4 Internet [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2081 RIPng Protocol Applicability Statement G. Malkin January 1997 ASCII 6821 4 Routing Information Protocol Internet As required by Routing Protocol Criteria (RFC 1264), this report defines the applicability of the RIPng protocol within the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2082 RIP-2 MD5 Authentication F. Baker R. Atkinson January 1997 ASCII 25436 12 RIP2-MD5 Routing Information Protocol Encryption 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] PROPOSED STANDARD PROPOSED STANDARD RFC2083 PNG (Portable Network Graphics) Specification Version 1.0 T. Boutell March 1997 ASCII 242528 102 PNG file format bitmap This document describes PNG (Portable Network Graphics), an extensible file format for the lossless, portable, well-compressed storage of raster images. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2084 Considerations for Web Transaction Security G. Bossert S. Cooper W. Drummond January 1997 ASCII 9022 6 authentication encryption World Wide Web WWW This document specifies the requirements for the provision of security services to the HyperText Transport Protocol. These services include confidentiality, integrity, user authentication, and authentication of servers/services, including proxied or gatewayed services. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2085 HMAC-MD5 IP Authentication with Replay Prevention M. Oehler R. Glenn February 1997 ASCII 13399 6 HMAC-MD5 ipsec Message Digest Security Internet Protocol Encryption This document describes a keyed-MD5 transform to be used in conjunction with the IP Authentication Header [RFC-1826]. The particular transform is based on [HMAC-MD5]. An option is also specified to guard against replay attacks. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2086 IMAP4 ACL extension J. Myers January 1997 ASCII 13925 8 IMAP4-ACL Internet Message Access Protocol Control List The ACL extension of the Internet Message Access Protocol [IMAP4] permits access control lists to be manipulated through the IMAP protocol. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2087 IMAP4 QUOTA extension J. Myers January 1997 ASCII 8542 5 IMAP4-QUO Internet Message Access Protocol The QUOTA extension of the Internet Message Access Protocol [IMAP4] permits administrative limits on resource usage (quotas) to be manipulated through the IMAP protocol. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2088 IMAP4 non-synchronizing literals J. Myers January 1997 ASCII 4052 2 IMAP4-LIT Internet Message Access Protocol 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] PROPOSED STANDARD PROPOSED STANDARD RFC2089 V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent B. Wijnen D. Levi January 1997 ASCII 23814 12 The goal of this memo is to document a common way of mapping an SNMPv2 response into an SNMPv1 response within a bi-lingual SNMP agent (one that supports both SNMPv1 and SNMPv2). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC2576 INFORMATIONAL INFORMATIONAL RFC2090 TFTP Multicast Option A. Emberson February 1997 ASCII 11857 6 TFTP-MULTI Trivial File Transfer Protocol This document describes a new TFTP option. This new option will allow the multiple clients to receive the same file concurrently through the use of Multicast packets. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC2091 Triggered Extensions to RIP to Support Demand Circuits G. Meyer S. Sherry January 1997 ASCII 44835 22 RIP-TRIG This document defines a modification which can be applied to Bellman- Ford (distance vector) algorithm information broadcasting protocols. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2092 Protocol Analysis for Triggered RIP S. Sherry G. Meyer January 1997 ASCII 10865 6 As required by Routing Protocol Criteria [1], this report documents the key features of Triggered Extensions to RIP to Support Demand Circuits [2] and the current implementation experience. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2093 Group Key Management Protocol (GKMP) Specification H. Harney C. Muckenhirn July 1997 ASCII 48678 23 GKMP-SPEC This specification proposes a protocol to create grouped symmetric keys and distribute them amongst communicating peers. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC2094 Group Key Management Protocol (GKMP) Architecture H. Harney C. Muckenhirn July 1997 ASCII 53097 22 GKMP-ARCH This specification proposes a protocol to create grouped symmetric keys and distribute them amongst communicating peers. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC2095 IMAP/POP AUTHorize Extension for Simple Challenge/Response J. Klensin R. Catoe P. Krumviede January 1997 ASCII 10446 5 Post Office Protocol Internet Message Access This specification provides a simple challenge-response authentication protocol that is suitable for use with IMAP4. [STANDARDS-TRACK] RFC2195 PROPOSED STANDARD PROPOSED STANDARD RFC2096 IP Forwarding Table MIB F. Baker January 1997 ASCII 35930 21 TABLE-MIB Management Information Base Internet Protocol 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] RFC1354 PROPOSED STANDARD PROPOSED STANDARD RFC2097 The PPP NetBIOS Frames Control Protocol (NBFCP) G. Pall January 1997 ASCII 27104 13 PPP-NBFCP Point-to-Point Protocol This document defines the Network Control Protocol for establishing and configuring the NBF protocol over PPP. The NBFCP protocol is only applicable for an end system to connect to a peer system or the LAN that peer system is connected to. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2098 Toshiba's Router Architecture Extensions for ATM : Overview Y. Katsube K. Nagami H. Esaki February 1997 ASCII 43622 18 Asynchronis Transfer Mode datagram IP Internet Protocol This memo describes a new internetworking architecture which makes better use of the property of ATM. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2099 Request for Comments Summary RFC Numbers 2000-2099 J. Elliott March 1997 ASCII 40763 21 INFORMATIONAL INFORMATIONAL RFC2100 The Naming of Hosts J. Ashworth April 01 1997 ASCII 4077 3 April Fool's This RFC is a commentary on the difficulty of deciding upon an acceptably distinctive hostname for one's computer, a problem which grows in direct proportion to the logarithmically increasing size of the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2101 IPv4 Address Behaviour Today B. Carpenter J. Crowcroft Y. Rekhter February 1997 ASCII 31407 13 Internet Protocol Internet Architecture Board The main purpose of this note is to clarify the current interpretation of the 32-bit IP version 4 address space, whose significance has changed substantially since it was originally defined. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2102 Multicast Support for Nimrod : Requirements and Solution Approaches R. Ramanathan February 1997 ASCII 50963 23 scalable routing architecture Nimrod does not specify a particular solution for multicasting. Rather, Nimrod may use any of a number of emerging multicast techniques. We identify the requirements that Nimrod has of a solution for multicast support. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2103 Mobility Support for Nimrod : Challenges and Solution Approaches R. Ramanathan February 1997 ASCII 41352 17 IP Internet Protocol routing addressing We discuss the issue of mobility in Nimrod. While a mobility solution is not part of the Nimrod architecture, Nimrod does require that the solution have certain characteristics. We identify the requirements that Nimrod has of any solution for mobility support. We also classify and compare existing approaches for supporting mobility within an internetwork and discuss their advantages and disadvantages. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2104 HMAC: Keyed-Hashing for Message Authentication H. Krawczyk M. Bellare R. Canetti February 1997 ASCII 22297 11 ipsec Message Digest Internet Protocol Security encryption This document describes HMAC, a mechanism for message authentication using cryptographic hash functions. HMAC can be used with any iterative cryptographic hash function, e.g., MD5, SHA-1, in combination with a secret shared key. The cryptographic strength of HMAC depends on the properties of the underlying hash function. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind INFORMATIONAL INFORMATIONAL RFC2105 Cisco Systems' Tag Switching Architecture Overview Y. Rekhter B. Davie D. Katz E. Rosen G. Swallow February 1997 ASCII 33013 13 network layer packet ATM switches This document provides an overview of a novel approach to network layer packet forwarding, called tag switching. The two main components of the tag switching architecture - forwarding and control - are described. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2106 Data Link Switching Remote Access Protocol S. Chiang J. Lee H. Yasuda February 1997 ASCII 40819 19 DLSRAP NetBios DLSW This memo describes the Data Link Switching Remote Access Protocol that is used between workstations and routers to transport SNA/ NetBIOS traffic over TCP sessions. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC2114 INFORMATIONAL INFORMATIONAL RFC2107 Ascend Tunnel Management Protocol - ATMP K. Hamzeh February 1997 ASCII 44300 21 RADIUS authentication This document specifies a generic tunnel management protocol that allows remote dial-in users to access their home network as if they were directly attached to the home network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2108 Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2 K. de Graaf D. Romascanu D. McMaster K. McCloghrie February 1997 ASCII 166336 82 802.3-MIB MIB Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IEEE 802.3 10 and 100 Mb/second baseband repeaters based on IEEE Std 802.3 Section 30, "10 & RFC1516 PROPOSED STANDARD PROPOSED STANDARD RFC2109 HTTP State Management Mechanism D. Kristol L. Montulli February 1997 ASCII 43469 21 HTTP-STATE Hypertext Transfer Protocol cookie 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] RFC2965 PROPOSED STANDARD PROPOSED STANDARD RFC2110 MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML) J. Palme A. Hopmann March 1997 ASCII 41961 19 MHTML Hyper Text Markup Language Multipurpose Internet Mail Extensions This document describes a set of guidelines that will allow conforming mail user agents to be able to send, deliver and display these objects, such as HTML objects, that can contain links represented by URIs. [STANDARDS-TRACK] RFC2557 PROPOSED STANDARD PROPOSED STANDARD RFC2111 Content-ID and Message-ID Uniform Resource Locators E. Levinson March 1997 ASCII 9099 5 Hyper Text Markup Language URL MIME The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow references to messages and the body parts of messages. For example, within a single multipart message, one HTML body part might include embedded references to other parts of the same message. [STANDARDS- TRACK] RFC2392 PROPOSED STANDARD PROPOSED STANDARD RFC2112 The MIME Multipart/Related Content-type E. Levinson March 1997 ASCII 17052 9 Hyper Text Markup Language Multipurpose Internet,Mail Extensions The Multipart/Related content-type provides a common mechanism for representing objects that are aggregates of related MIME body parts. This document defines the Multipart/Related content-type and provides examples of its use. [STANDARDS-TRACK] RFC1872 RFC1872 RFC2387 PROPOSED STANDARD PROPOSED STANDARD RFC2113 IP Router Alert Option D. Katz February 1997 ASCII 7924 4 ROUT-ALERT This memo describes a new IP Option type that alerts transit routers to more closely examine the contents of an IP packet. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2114 Data Link Switching Client Access Protocol S. Chiang J. Lee H. Yasuda February 1997 ASCII 50872 22 DLSCAP This memo describes the Data Link Switching Client Access Protocol that is used between workstations and routers to transport SNA/ NetBIOS traffic over TCP sessions. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC2106 INFORMATIONAL INFORMATIONAL RFC2115 Management Information Base for Frame Relay DTEs Using SMIv2 C. Brown F. Baker September 1997 ASCII 59950 32 FRAME-MIB MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP- based internets. In particular, it defines objects for managing Frame Relay interfaces on DTEs. [STANDARDS-TRACK] RFC1315 DRAFT STANDARD DRAFT STANDARD RFC2116 X.500 Implementations Catalog-96 C. Apple K. Rossen April 1997 ASCII 243994 164 Directory Services DSA DUA Agent Interfaces This document is a revision to [RFC 1632]: A Revised Catalog of Available X.500 Implementations and is based on the results of data collection via a WWW home page that enabled implementors to submit new or updated descriptions of currently available implementations of X.500, including commercial products and openly available offerings. [RFC 1632] is a revision of [RFC 1292]. This document contains detailed description of 31 X.500 implementations - DSAs, DUAs, and DUA interfaces. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1632 FYI0011 INFORMATIONAL INFORMATIONAL RFC2117 Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification D. Estrin D. Farinacci A. Helmy D. Thaler S. Deering M. Handley V. Jacobson C. Liu P. Sharma L. Wei June 1997 ASCII 151886 66 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. RFC2362 EXPERIMENTAL EXPERIMENTAL RFC2118 Microsoft Point-To-Point Compression (MPPC) Protocol G. Pall March 1997 ASCII 17443 9 Point-to-Point Protocol PPP This document describes the use of the Microsoft Point to Point Compression protocol (also referred to as MPPC in this document) for compressing PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2119 Key words for use in RFCs to Indicate Requirement Levels S. Bradner March 1997 ASCII 4723 3 Standards Track Documents In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP0014 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2120 Managing the X.500 Root Naming Context D. Chadwick March 1997 ASCII 30773 14 X.500-NAME ISO International Standards Organization This document describes the use of 1993 ISO X.500 Standard protocols for managing the root context. Whilst the ASN.1 is compatible with that of the X.500 Standard, the actual settings of the parameters are supplementary to that of the X.500 Standard. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC2121 Issues affecting MARS Cluster Size G. Armitage March 1997 ASCII 26781 12 ATM Asynchronous Transfer Mode Multicast IP Internet Protocol This document provides a qualitative look at the issues constraining a MARS Cluster's size, including the impact of VC limits in switches and NICs, geographical distribution of cluster members, and the use of VC Mesh or MCS modes to support multicast groups. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2122 VEMMI URL Specification D. Mavrakis H. Layec K. Kartmann March 1997 ASCII 25043 11 VEMMI-URL Uniform Resource Locator Enhanced Man-Machine Interface Videotex A new URL scheme, "vemmi" is defined. VEMMI is a new international standard for on-line multimedia services, that is both an ITU-T (International Telecommunications Union, ex. CCITT) International Standard (T.107) and an European Standard (ETSI European Telecommunications Standard Institute) standard (ETS 300 382, obsoleted by ETS 300 709). [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2123 Traffic Flow Measurement: Experiences with NeTraMet N. Brownlee March 1997 ASCII 81874 34 Meter Reader Network This memo records experiences in implementing and using the Traffic Flow Measurement Architecture and Meter MIB. It discusses the implementation of NeTraMet (a traffic meter) and NeMaC (a combined manager and meter reader), considers the writing of meter rule sets and gives some guidance on setting up a traffic flow measurement system using NeTraMet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2124 Cabletron's Light-weight Flow Admission Protocol Specification Version 1.0 P. Amsden J. Amweg P. Calato S. Bensley G. Lyons March 1997 ASCII 47912 21 LFAP This document specifies the protocol between the switch Connection Control Entity (CCE) and the external FAS. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2125 The PPP Bandwidth Allocation Protocol (BAP) / The PPP Bandwidth Allocation Control Protocol (BACP) C. Richards K. Smith March 1997 ASCII 49213 24 BAP-BACP Point-to-Point datagram multilink This document proposes a method to manage the dynamic bandwidth allocation of implementations supporting the PPP multilink protocol. This is done by defining the Bandwidth Allocation Protocol (BAP), as well as its associated control protocol, the Bandwidth Allocation Control Protocol (BACP). [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2126 ISO Transport Service on top of TCP (ITOT) Y. Pouffary A. Young March 1997 ASCII 51032 25 ITOT International Standards Organization Transmission Control Protocol This document is a revision to STD35, RFC1006. This document describes the mechanism to allow ISO Transport Services to run over TCP over IPv4 or IPv6. It also defines a number of new features, which are not provided in RFC1006. [STANDARDS-TRACK] RFC1006 PROPOSED STANDARD PROPOSED STANDARD RFC2127 ISDN Management Information Base using SMIv2 G. Roeck Editor March 1997 ASCII 95994 49 ISDN-MIB MIB ISDN Integrated Services Digital Network This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a minimal set of managed objects for SNMP-based management of ISDN terminal interfaces. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2128 Dial Control Management Information Base using SMIv2 G. Roeck Editor March 1997 ASCII 66153 34 DC-MIB MIB ISDN Integrated Services Digital Network This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing demand access circuits, including ISDN. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2129 Toshiba's Flow Attribute Notification Protocol (FANP) Specification K. Nagami Y. Katsube Y. Shobatake A. Mogi S. Matsuzawa T. Jinmei H. Esaki April 1997 ASCII 41137 19 packet flow datalink mapping This memo discusses Flow Attribute Notification Protocol (FANP), which is a protocol between neighbor nodes for the management of cut-through packet forwarding functionalities. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2130 The Report of the IAB Character Set Workshop held 29 February - 1 March, 1996 C. Weider C. Preston K. Simonsen H. Alvestrand R. Atkinson M. Crispin P. Svanberg April 1997 ASCII 63443 31 Internet Architecture Board interoperability This report details the conclusions of an IAB-sponsored invitational workshop held 29 February - 1 March, 1996, to discuss the use of character sets on the Internet. It motivates the need to have character set handling in Internet protocols which transmit text, provides a conceptual framework for specifying character sets, recommends the use of MIME tagging for transmitted text, recommends a default character set *without* stating that there is no need for other character sets, and makes a series of recommendations to the IAB, IANA, and the IESG for furthering the integration of the character set framework into text transmission protocols. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2131 Dynamic Host Configuration Protocol R. Droms March 1997 ASCII 113738 45 DHCP The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCPIP network. DHCP is based on the Bootstrap Protocol (BOOTP), adding the capability of automatic allocation of reusable network addresses and additional configuration options. [STANDARDS-TRACK] RFC1541 RFC3396 DRAFT STANDARD DRAFT STANDARD RFC2132 DHCP Options and BOOTP Vendor Extensions S. Alexander R. Droms March 1997 ASCII 63670 34 DHCP-BOOTP Dynamic Host Configuration Protocol Bootstrap This document specifies the current set of DHCP options. Future options will be specified in separate RFCs. The current list of valid options is also available in ftp://ftp.isi.edu/in-notes/iana/assignments. [STANDARDS-TRACK] RFC1533 RFC3442 RFC3942 DRAFT STANDARD DRAFT STANDARD RFC2133 Basic Socket Interface Extensions for IPv6 R. Gilligan S. Thomson J. Bound W. Stevens April 1997 ASCII 69737 32 application program interface API Internet Protocol addresses This memo defines a set of extensions to the socket interface to support the larger address size and new features of IPv6. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC2553 INFORMATIONAL INFORMATIONAL RFC2134 Articles of Incorporation of Internet Society ISOC Board of Trustees April 1997 ASCII 9131 5 ISOC These are the articles of incorporation of the Internet Society. They are published for the information of the IETF community at the request of the poisson working group. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2135 Internet Society By-Laws ISOC Board of Trustees April 1997 ASCII 20467 9 ISOC These are the by-laws of the Internet Society, as amended, as of June 1996. They are published for the information of the IETF community at the request of the poisson working group. Please refer to the ISOC web page (www.isoc.org) for the current version of the by-laws. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2136 Dynamic Updates in the Domain Name System (DNS UPDATE) P. Vixie Editor S. Thomson Y. Rekhter J. Bound April 1997 ASCII 56354 26 DNS-UPDATE database opcode zone Using this specification of the UPDATE opcode, it is possible to add or delete RRs or RRsets from a specified zone. Prerequisites are specified separately from update operations, and can specify a dependency upon either the previous existence or nonexistence of an RRset, or the existence of a single RR. [STANDARDS-TRACK] RFC1035 RFC3007 RFC4033 RFC4034 RFC4035 PROPOSED STANDARD PROPOSED STANDARD RFC2137 Secure Domain Name System Dynamic Update D. Eastlake 3rd April 1997 ASCII 24824 11 SDNSDU DNS digital signatures cryptographic This memo describes how to use DNSSEC digital signatures covering requests and data to secure updates and restrict updates to those authorized to perform them as indicated by the updater's possession of cryptographic keys. [STANDARDS-TRACK] RFC3007 RFC1035 PROPOSED STANDARD PROPOSED STANDARD RFC2138 Remote Authentication Dial In User Service (RADIUS) C. Rigney A. Rubens W. Simpson S. Willens April 1997 ASCII 120407 65 RADIUS encryption NAS Network Access Server This document describes a protocol for carrying authentication, authorization, and configuration information between a Network Access Server which desires to authenticate its links and a shared Authentication Server. [STANDARDS-TRACK] RFC2058 RFC2865 PROPOSED STANDARD PROPOSED STANDARD RFC2139 RADIUS Accounting C. Rigney April 1997 ASCII 44919 25 RADIUS-ACC remote authentication dial in user service encryption This document describes a protocol for carrying accounting information between a Network Access Server and a shared Accounting Server. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC2059 RFC2866 INFORMATIONAL INFORMATIONAL RFC2140 TCP Control Block Interdependence J. Touch April 1997 ASCII 26032 11 This memo makes the case for interdependent TCP control blocks, where part of the TCP state is shared among similar concurrent connections, or across similar connection instances. TCP state includes a combination of parameters, such as connection state, current round-trip time estimates, congestion control information, and process information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2141 URN Syntax R. Moats May 1997 ASCII 14077 8 URN-SYNTAX Uniform Resource Names Uniform Resource Names (URNs) are intended to serve as persistent, location-independent, resource identifiers. This document sets forward the canonical syntax for URNs. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2142 Mailbox Names for Common Services, Roles and Functions D. Crocker May 1997 ASCII 12195 6 MAIL-SERV email internet addresses This specification enumerates and describes Internet mail addresses (mailbox name @ host reference) to be used when contacting personnel at an organization. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2143 Encapsulating IP with the Small Computer System Interface B. Elliston May 1997 ASCII 10749 5 IP-SCSI SCSI This document outlines a protocol for connecting hosts running the TCP/IP protocol suite over a Small Computer System Interface (SCSI) bus. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. EXPERIMENTAL EXPERIMENTAL RFC2144 The CAST-128 Encryption Algorithm C. Adams May 1997 ASCII 37532 15 CAST-128 There is a need in the Internet community for an unencumbered encryption algorithm with a range of key sizes that can provide security for a variety of cryptographic applications and protocols. This document describes an existing algorithm that can be used to satisfy this requirement. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2145 Use and Interpretation of HTTP Version Numbers J. C. Mogul R. Fielding J. Gettys H. Frystyk May 1997 ASCII 13659 7 HTTP request and response messages include an HTTP protocol version number. Some confusion exists concerning the proper use and interpretation of HTTP version numbers, and concerning interoperability of HTTP implementations of different protocol versions. This document is an attempt to clarify the situation. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2146 U.S. Government Internet Domain Names Federal Networking Council May 1997 ASCII 26564 12 Gov FED.US This memo provides an update and clarification to RFC 1816. This document describes the registration policies for the top-level domain ".GOV". The purpose of the domain is to provide naming conventions that identify US Federal government agencies in order to facilitate access to their electronic resources. This memo provides guidance for registrations by Federal Agencies that avoids name duplication and facilitates responsiveness to the public. It restricts registrations to coincide with the approved structure of the US government and the advice of its Chief Information Officers. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1816 INFORMATIONAL INFORMATIONAL RFC2147 TCP and UDP over IPv6 Jumbograms D. Borman May 1997 ASCII 1883 3 IPv6-Jumbo User Datagram Protocol Terminal Control Internet 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] RFC2675 PROPOSED STANDARD PROPOSED STANDARD RFC2148 Deployment of the Internet White Pages Service H. Alvestrand P. Jurg September 1997 ASCII 31539 15 X. 500 data structure naming scheme IWPS This document describes the way in which the Internet White Pages Service is best exploited using today's experience, today's protocols, today's products and today's procedures. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP0015 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2149 Multicast Server Architectures for MARS-based ATM multicasting R. Talpade M. Ammar May 1997 ASCII 42007 18 This memo provides details on the design and implementation of an MCS, building on the core mechanisms defined in RFC 2022. It also provides a mechanism for using multiple MCSs per group for providing fault tolerance. This approach can be used with RFC 2022 based MARS server and clients, without needing any change in their functionality. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2150 Humanities and Arts: Sharing Center Stage on the Internet J. Max W. Stickle October 1997 ASCII 154037 62 informational infrastructure guide introduction The purpose of this document is to provide members of the Arts and Humanities communities with an introduction to the Internet as a valuable tool, resource, and medium for the creation, presentation, and preservation of Arts and Humanities-based content. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. FYI0031 INFORMATIONAL INFORMATIONAL RFC2151 A Primer On Internet and TCP/IP Tools and Utilities G. Kessler S. Shepard June 1997 ASCII 114130 52 resource guide user This memo is an introductory guide to many of the most commonly- available TCP/IP and Internet tools and utilities. It also describes discussion lists accessible from the Internet, ways to obtain Internet and TCP/IP documents, and some resources that help users weave their way through the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1739 FYI0030 INFORMATIONAL INFORMATIONAL RFC2152 UTF-7 A Mail-Safe Transformation Format of Unicode D. Goldsmith M. Davis May 1997 ASCII 28065 15 UTF-7 This document describes a transformation format of Unicode that contains only 7-bit ASCII octets and is intended to be readable by humans in the limiting case that the document consists of characters from the US-ASCII repertoire. It also specifies how this transformation format is used in the context of MIME and RFC 1641, "Using Unicode with MIME". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1642 INFORMATIONAL INFORMATIONAL RFC2153 PPP Vendor Extensions W. Simpson May 1997 ASCII 10780 6 PPP-EXT Point-to-Point Protocol The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection; and a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document provides information for the Internet community. It does not specify an Internet standard of any kind. RFC1661 RFC1962 INFORMATIONAL INFORMATIONAL RFC2154 OSPF with Digital Signatures S. Murphy M. Badger B. Wellington June 1997 ASCII 72701 29 OSPF-DIG This memo describes the extensions to OSPF required to add digital signature authentication to Link State data, and to provide a certification mechanism for router data. Added LSA processing and key management is detailed. A method for migration from, or co-existence with, standard OSPF V2 is described. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC2155 Definitions of Managed Objects for APPN using SMIv2 B. Clouston B. Moore June 1997 ASCII 213809 124 APPN-MIB 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] RFC2455 PROPOSED STANDARD PROPOSED STANDARD RFC2156 MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME S. Kille January 1998 ASCII 280385 144 MIXER multipurpose internet mail extensions message transfer protocol This document relates primarily to the ITU-T 1988 and 1992 X.400 Series Recommendations / ISO IEC 10021 International Standard. This ISO/ITU-T standard is referred to in this document as "X.400", which is a convenient shorthand. [STANDARDS-TRACK] RFC0987 RFC1026 RFC1138 RFC1148 RFC1327 RFC1495 RFC0822 PROPOSED STANDARD PROPOSED STANDARD RFC2157 Mapping between X.400 and RFC-822/MIME Message Bodies H. Alvestrand January 1998 ASCII 92554 49 mixer multipurpose internet mail extensions This document defines how to map body parts of X.400 messages into MIME entities and vice versa, including the handling of multipart messages and forwarded messages. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2158 X.400 Image Body Parts H. Alvestrand January 1998 ASCII 5547 4 mixer multipurpose internet mail extensions This document contains the body parts defined in RFC 1495 for carrying image formats that were originally defined in MIME through an X.400 system. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2159 A MIME Body Part for FAX H. Alvestrand January 1998 ASCII 11471 7 mixer multipurpose internet mail extensions This document contains the definitions, originally contained in RFC 1494, on how to carry CCITT G3Fax in MIME, and how to translate it to its X.400 representation. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2160 Carrying PostScript in X.400 and MIME H. Alvestrand January 1998 ASCII 7059 5 mixer multipurpose internet mail extensions This document describes methods for carrying PostScript information in the two standard mail systems MIME and X.400, and the conversion between them. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2161 A MIME Body Part for ODA H. Alvestrand January 1998 ASCII 8009 5 MIME-ODA mixer multipurpose internet mail extensions This document contains the definitions, originally contained in RFC 1495 and RFC 1341, on how to carry ODA in MIME, and how to translate it to its X.400 representation. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC2162 MaXIM-11 - Mapping between X.400 / Internet mail and Mail-11 mail C. Allocchio January 1998 ASCII 58553 34 MAP-MAIL mixer multipurpose internet mail extensions mime The standard referred shortly into this document as "X.400" relates to the ISO/IEC 10021 - CCITT 1984, 1988 and 1992 X.400 Series Recommendations covering the Message Oriented Text Interchange Service (MOTIS). This document covers the Inter Personal Messaging System (IPMS) only. This memo defines an Experimental Protocol for the Internet community. RFC1405 EXPERIMENTAL EXPERIMENTAL RFC2163 Using the Internet DNS to Distribute MIXER Conformant Global Address Mapping (MCGAM) C. Allocchio January 1998 ASCII 58789 26 DNS-MCGAM mime internet enhanced Relay Multipurpose internet mail extensions x.400 mixer This memo is the complete technical specification to store in the Internet Domain Name System (DNS) the mapping information (MCGAM) needed by MIXER conformant e-mail gateways and other tools to map RFC822 domain names into X.400 O/R names and vice versa. [STANDARDS-TRACK] RFC1664 RFC3597 PROPOSED STANDARD PROPOSED STANDARD RFC2164 Use of an X.500/LDAP directory to support MIXER address mapping S. Kille January 1998 ASCII 16701 10 lightweight directory access protocol mime internet x,.400 enhanced relay This specification defines how to represent and maintain these mappings (MIXER Conformant Global Address Mappings of MCGAMs) in an X.500 or LDAP directory. [STANDARDS-TRACK] RFC1838 PROPOSED STANDARD PROPOSED STANDARD RFC2165 Service Location Protocol J. Veizades E. Guttman C. Perkins S. Kaplan June 1997 ASCII 169889 72 SLP The Service Location Protocol provides a scalable framework for the discovery and selection of network services. Using this protocol, computers using the Internet no longer need so much static configuration of network services for network based applications. This is especially important as computers become more portable, and users less tolerant or able to fulfill the demands of network system administration. [STANDARDS-TRACK] RFC2608 RFC2609 PROPOSED STANDARD PROPOSED STANDARD RFC2166 APPN Implementer's Workshop Closed Pages Document DLSw v2.0 Enhancements D. Bryant P. Brittain June 1997 ASCII 75527 34 This document specifies a set of extensions to RFC 1795 designed to improve the scalability of DLSw clarifications to RFC 1795 in the light of the implementation experience to-date. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2167 Referral Whois (RWhois) Protocol V1.5 S. Williamson M. Kosters D. Blacka J. Singh K. Zeilstra June 1997 ASCII 136355 69 RWHOIS This memo describes Version 1.5 of the client/server interaction of RWhois. RWhois provides a distributed system for the discovery, retrieval, and maintenance of directory information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. RFC1714 INFORMATIONAL INFORMATIONAL RFC2168 Resolution of Uniform Resource Identifiers using the Domain Name System R. Daniel M. Mealling June 1997 ASCII 46528 20 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. RFC3401 RFC3402 RFC3403 RFC3404 RFC2915 EXPERIMENTAL EXPERIMENTAL RFC2169 A Trivial Convention for using HTTP in URN Resolution R. Daniel June 1997 ASCII 17763 9 This document specifies the "THTTP" resolution protocol - a trivial convention for encoding resolution service requests and responses as HTTP 1.0 or 1.1 requests and responses. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. EXPERIMENTAL EXPERIMENTAL RFC2170 Application REQuested IP over ATM (AREQUIPA) W. Almesberger J. Le Boudec P. Oechslin July 1997 ASCII 22874 10 Internet Protocol This document specifies a method for allowing ATM-attached hosts that have direct ATM connectivity to set up end-to-end IP over ATM connections within the reachable ATM cloud, on request from applications, and for the exclusive use by the requesting applications. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2171 MAPOS - Multiple Access Protocol over SONET/SDH Version 1 K. Murakami M. Maruyama June 1997 ASCII 17480 9 MAPOS-SONET This memo documents a multiple access protocol for transmission of network-protocol datagrams, encapsulated in High-Level Data Link Control (HDLC) frames, over SONET/SDH. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2172 MAPOS Version 1 Assigned Numbers M. Maruyama K. Murakami June 1997 ASCII 4857 3 This memo documents the parameters used in the Multiple Access Protocol over SONET/SDH Version 1. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2173 A MAPOS version 1 Extension - Node Switch Protocol K. Murakami M. Maruyama June 1997 ASCII 12251 6 This document describes a MAPOS extension, Node Switch Protocol, for automatic node address assignment. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2174 A MAPOS version 1 Extension - Switch-Switch Protocol K. Murakami M. Maruyama June 1997 ASCII 47967 22 This memo documents a MAPOS (Multiple Access Protocol over SONET/SDH) version 1 extension, Switch Switch Protocol which provides dynamic routing for unicast, broadcast, and multicast. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2175 MAPOS 16 - Multiple Access Protocol over SONET/SDH with 16 Bit Addressing K. Murakami M. Maruyama June 1997 ASCII 11677 6 This memo documents MAPOS 16, a multiple access protocol for transmission of network-protocol datagrams, encapsulated in HDLC frames with 16 bit addressing, over SONET/SDH. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2176 IPv4 over MAPOS Version 1 K. Murakami M. Maruyama June 1997 ASCII 12305 6 IPV4-MAPOS This memo documents a mechanism for supporting Version 4 of the Internet Protocol (IPv4) on Version 1 of the Multiple Access Protocol over SONET/SDH. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2177 IMAP4 IDLE command B. Leiba June 1997 ASCII 6770 4 IMAP4-IDLE This document specifies the syntax of an IDLE command, which will allow a client to tell the server that it's ready to accept such real-time updates. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2178 OSPF Version 2 J. Moy July 1997 ASCII 495866 211 Open Shortest Path First routing Autonomous system AS This document considers some areas that have been identified as problems with the specification of the Domain Name System, and proposes remedies for the defects identified. [STANDARDS TRACK] RFC1583 RFC2328 DRAFT STANDARD DRAFT STANDARD RFC2179 Network Security For Trade Shows A. Gwinn July 1997 ASCII 20690 10 network system attacks This document is designed to assist vendors and other participants in trade shows, such as Networld+Interop, in designing effective protection against network and system attacks by unauthorized individuals. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2180 IMAP4 Multi-Accessed Mailbox Practice M. Gahrns July 1997 ASCII 24750 14 Internet Message Access Protocol Client Server The behavior described in this document reflects the practice of some existing servers or behavior that the consensus of the IMAP mailing list has deemed to be reasonable. The behavior described within this document is believed to be [RFC-2060] compliant. However, this document is not meant to define IMAP4 compliance, nor is it an exhaustive list of valid IMAP4 behavior. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2181 Clarifications to the DNS Specification R. Elz R. Bush July 1997 ASCII 36989 14 DNS-CLAR Domain Name System This document considers some areas that have been identified as problems with the specification of the Domain Name System, and proposes remedies for the defects identified. [STANDARDS TRACK] RFC1034 RFC1035 RFC1123 RFC2535 RFC4033 RFC4034 RFC4035 PROPOSED STANDARD PROPOSED STANDARD RFC2182 Selection and Operation of Secondary DNS Servers R. Elz R. Bush S. Bradner M. Patton July 1997 ASCII 27456 11 Domain Name System delegated zone This document discusses the selection of secondary servers for DNS zones.The number of servers appropriate for a zone is also discussed, and some general secondary server maintenance issues considered. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. BCP0016 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2183 Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field R. Troost S. Dorner K. Moore Editor August 1997 ASCII 23150 12 inline attachment MIME Mail Multimedia EMail This memo provides a mechanism whereby messages conforming to the MIME specifications [RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049] can convey presentational information. It specifies the "Content- Disposition" header field, which is optional and valid for any MIME entity ("message" or "body part"). [STANDARDS-TRACK] RFC1806 RFC2184 RFC2231 PROPOSED STANDARD PROPOSED STANDARD RFC2184 MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations N. Freed K. Moore August 1997 ASCII 17635 9 mail Multimedia EMail This memo defines extensions to the RFC 2045 media type and RFC 2183 disposition parameter value mechanisms. [STANDARDS-TRACK] RFC2231 RFC2045 RFC2047 RFC2183 PROPOSED STANDARD PROPOSED STANDARD RFC2185 Routing Aspects of IPv6 Transition R. Callon D. Haskin September 1997 ASCII 31281 13 address network tunneling This document gives an overview of the routing aspects of the IPv6 transition. It is based on the protocols defined in the document "Transition Mechanisms for IPv6 Hosts and Routers." Readers should be familiar with the transition mechanisms before reading this document. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2186 Internet Cache Protocol (ICP), version 2 D. Wessels K. Claffy September 1997 ASCII 18808 9 ICP www web http hypertext transfer protocol This document describes version 2 of the Internet Cache Protocol (ICPv2) as currently implemented in two World-Wide Web proxy cache packages. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2187 Application of Internet Cache Protocol (ICP), version 2 D. Wessels K. Claffy September 1997 ASCII 51662 24 web www url uniform resource identifier This document describes the application of ICPv2 (Internet Cache Protocol version 2, RFC2186) to Web caching. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2188 AT&T/Neda's Efficient Short Remote Operations (ESRO) Protocol Specification Version 1.2 M. Banan M. Taylor J. Cheng September 1997 ASCII 118374 57 ESRO RPC Remote Procedure Call Wireless This document specifies the service model, the notation and protocol for Efficient Short Remote Operations (ESRO). This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2189 Core Based Trees (CBT version 2) Multicast Routing -- Protocol Specification -- A. Ballardie September 1997 ASCII 52043 23 Inter-Domain-Protocol IDMR This document describes the Core Based Tree (CBT version 2) network layer multicast routing protocol. CBT builds a shared multicast distribution tree per group, and is suited to inter- and intra-domain multicast routing. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC2190 RTP Payload Format for H.263 Video Streams C. Zhu September 1997 ASCII 26409 12 real-time transfer This document specifies the payload format for encapsulating an H.263 bitstream in the Real-Time Transport Protocol (RTP). [STANDARDS TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2191 VENUS - Very Extensive Non-Unicast Service G. Armitage September 1997 ASCII 31316 12 multicast IP ATM This document focuses exclusively on the problems associated with extending the MARS model to cover multiple clusters or clusters spanning more than one subnet. It describes a hypothetical solution, dubbed "Very Extensive NonUnicast Service" (VENUS), and shows how complex such a service would be. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2192 IMAP URL Scheme C. Newman September 1997 ASCII 31426 16 IMAP-URL Internet Message Access Protocol Uniform Resource Identifiers This document defines a URL scheme for referencing objects on an IMAP server. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2193 IMAP4 Mailbox Referrals M. Gahrns September 1997 ASCII 16248 9 IMAP4MAIL Internet Mail Access Protocol messages Mailbox referrals allow clients to seamlessly access mailboxes that are distributed across several IMAP4 servers. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2194 Review of Roaming Implementations B. Aboba J. Lu J. Alsop J. Ding W. Wang September 1997 ASCII 81533 35 ISP Internet Server Provider This document reviews the design and functionality of existing roaming implementations. Examples of cases where roaming capability might be required include ISP "confederations" and ISP-provided corporate network access support. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2195 IMAP/POP AUTHorize Extension for Simple Challenge/Response J. Klensin R. Catoe P. Krumviede September 1997 ASCII 10468 5 IMAPPOPAU Post Office Protocol Internet Message Access This specification provides a simple challenge-response authentication protocol that is suitable for use with IMAP4. [STANDARDS TRACK] RFC2095 PROPOSED STANDARD PROPOSED STANDARD RFC2196 Site Security Handbook B. Fraser September 1997 ASCII 191772 75 This handbook is a guide to developing computer security policies and procedures for sites that have systems on the Internet. The purpose of this handbook is to provide practical guidance to administrators trying to secure their information and services. The subjects covered include policy content and formation, a broad range of technical system and network security topics, and security incident response. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. RFC1244 FYI0008 INFORMATIONAL INFORMATIONAL RFC2197 SMTP Service Extension for Command Pipelining N. Freed September 1997 ASCII 15003 8 SMTP-Pipe simple mail transfer TCP transmission control protocol 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] RFC1854 RFC2920 DRAFT STANDARD DRAFT STANDARD RFC2198 RTP Payload for Redundant Audio Data C. Perkins I. Kouvelas O. Hodson V. Hardman M. Handley J.C. Bolot A. Vega-Garcia S. Fosse-Parisis September 1997 ASCII 25166 11 RTP-RAD This document describes a payload format for use with the real-time transport protocol (RTP), version 2, for encoding redundant audio data. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2199 Request for Comments Summary RFC Numbers 2100-2199 A. Ramos January 1998 ASCII 47664 23 INFORMATIONAL INFORMATIONAL RFC2200 Internet Official Protocol Standards J. Postel June 1997 ASCII 94506 39 IAB official protocol standards A discussion of the standardization process and the RFC document series is presented first, followed by an explanation of the terms. Sections 6.2 - 6.10 contain the lists of protocols in each stage of standardization. Finally are pointers to references and contacts for further information. [STANDARDS-TRACK] RFC1250 RFC2000 RFC2300 HISTORIC STANDARD RFC2201 Core Based Trees (CBT) Multicast Routing Architecture A. Ballardie September 1997 ASCII 38040 15 IP Internet Protocol IDMR Inter-Domain CBT is a multicast routing architecture that builds a single delivery tree per group which is shared by all of the group's senders and receivers. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC2202 Test Cases for HMAC-MD5 and HMAC-SHA-1 P. Cheng R. Glenn September 1997 ASCII 11945 9 Hash Message Authentications Codes message digest secure This document provides two sets of test cases for HMAC-MD5 and HMAC- SHA-1, respectively. HMAC-MD5 and HMAC-SHA-1 are two constructs of the HMAC [HMAC] message authentication function using the MD5 [MD5] hash function and the SHA-1 [SHA] hash function. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2203 RPCSEC_GSS Protocol Specification M. Eisler A. Chiu L. Ling September 1997 ASCII 50937 23 RPCSEC-GSS Remote Procedure Call Generic Security Services API Application Programming Interface This memo describes an ONC/RPC security flavor that allows RPC protocols to access the Generic Security Services Application Programming Interface (referred to henceforth as GSS-API). [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2204 ODETTE File Transfer Protocol D. Nash September 1997 ASCII 151857 74 ODETTE FTP Internet Motor Industry data exchange This memo describes a file transfer protocol to facilitate electronic data interchange between trading partners. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2205 Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification R. Braden Editor L. Zhang S. Berson S. Herzog S. Jamin September 1997 ASCII 223974 112 RSVP integrated services multicast unicast QoS signaling This memo describes version 1 of RSVP, a resource reservation setup protocol designed for an integrated services Internet. RSVP provides receiver-initiated setup of resource reservations for multicast or unicast data flows, with good scaling and robustness properties. [STANDARDS-TRACK] RFC2750 RFC3936 PROPOSED STANDARD PROPOSED STANDARD RFC2206 RSVP Management Information Base using SMIv2 F. Baker J. Krawczyk A. Sastry September 1997 ASCII 112937 64 RSVP-MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Resource Reservation Protocol (RSVP) within the interface attributes defined in the Integrated Services Model. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2207 RSVP Extensions for IPSEC Data Flows L. Berger T. O'Malley September 1997 ASCII 30473 14 RSVP-IPSEC resource reservation QoS IP Security This document presents extensions to Version 1 of RSVP. These extensions permit support of individual data flows using RFC 1826, IP Authentication Header (AH) or RFC 1827, IP Encapsulating Security Payload (ESP). [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2208 Resource ReSerVation Protocol (RSVP) -- Version 1 Applicability Statement Some Guidelines on Deployment A. Mankin Editor F. Baker B. Braden S. Bradner M. O`Dell A. Romanow A. Weinrib L. Zhang September 1997 ASCII 14289 6 RSVP This document describes the applicability of RSVP along with the Integrated Services protocols and other components of resource reservation and offers guidelines for deployment of resource reservation at this time. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2209 Resource ReSerVation Protocol (RSVP) -- Version 1 Message Processing Rules R. Braden L. Zhang September 1997 ASCII 51690 25 RSVP-MPR QoS implementation algorithms This memo contains an algorithmic description of the rules used by an RSVP implementation for processing messages. It is intended to clarify the version 1 RSVP protocol specification. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2210 The Use of RSVP with IETF Integrated Services J. Wroclawski September 1997 ASCII 77613 33 RSVP-IS Resource Reservation Controlled Load QOS: Quality of Service This note describes the use of the RSVP resource reservation protocol with the Controlled-Load and Guaranteed QoS control services. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2211 Specification of the Controlled-Load Network Element Service J. Wroclawski September 1997 ASCII 46523 19 QOS: Quality of Service integrated services This memo specifies the network element behavior required to deliver Controlled-Load service in the Internet. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2212 Specification of Guaranteed Quality of Service S. Shenker C. Partridge R. Guerin September 1997 ASCII 52330 20 GQOS QOS quality of service integrated services This memo describes the network element behavior required to deliver a guaranteed service (guaranteed delay and bandwidth) in the Internet. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2213 Integrated Services Management Information Base using SMIv2 F. Baker J. Krawczyk A. Sastry September 1997 ASCII 36147 21 MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the the interface attributes defined in the Integrated Services Model. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2214 Integrated Services Management Information Base Guaranteed Service Extensions using SMIv2 F. Baker J. Krawczyk A. Sastry September 1997 ASCII 15971 9 MIB attributes interface network protocol This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the the interface attributes defined in the Guaranteed Service of the Integrated Services Model. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2215 General Characterization Parameters for Integrated Service Network Elements S. Shenker J. Wroclawski September 1997 ASCII 39552 16 QOS Quality of service This memo defines a set of general control and characterization parameters for network elements supporting the IETF integrated services QoS control framework. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2216 Network Element Service Specification Template S. Shenker J. Wroclawski September 1997 ASCII 53655 22 QOS Quality of Service Control This document defines a framework for specifying services provided by network elements, and available to applications, in an internetwork which offers multiple qualities of service. The document first provides some necessary context -- including relevant definitions and suggested data formats -- and then specifies a "template" which service specification documents should follow. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2217 Telnet Com Port Control Option G. Clark October 1997 ASCII 31664 14 TOPT-COMPORT remote login host This memo proposes a protocol to allow greater use of modems attached to a network for outbound dialing purposes. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC2218 A Common Schema for the Internet White Pages Service T. Genovese B. Jennings October 1997 ASCII 16258 8 IWPS information user This document specifies the minimum set of core attributes of a White Pages entry for an individual and describes how new objects with those attributes can be defined and published. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2219 Use of DNS Aliases for Network Services M. Hamilton R. Wright October 1997 ASCII 17858 8 domain name system symbolic It has become a common practice to use symbolic names (usually CNAMEs) in the Domain Name Service (DNS - [RFC-1034, RFC-1035]) to refer to network services such as anonymous FTP [RFC-959] servers, Gopher [RFC- 1436] servers, and most notably World-Wide Web HTTP [RFC-1945] servers. This is desirable for a number of reasons. It provides a way of moving services from one machine to another transparently, and a mechanism by which people or agents may programmatically discover that an organization runs, say, a World-Wide Web server. Although this approach has been almost universally adopted, there is no standards document or similar specification for these commonly used names. This document seeks to rectify this situation by gathering together the extant 'folklore' on naming conventions, and proposes a mechanism for accommodating new protocols. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP0017 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2220 The Application/MARC Content-type R. Guenther October 1997 ASCII 7025 4 APP-MARC media-type machine readable cataloging records This memorandum provides a mechanism for representing objects which are files of Machine-Readable Cataloging records (MARC). The MARC formats are standards for the representation and communication of bibliographic and related information. A MARC record contains metadata for an information resource following MARC format specifications. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2221 IMAP4 Login Referrals M. Gahrns October 1997 ASCII 9251 5 IMAP4LOGIN Internet Message Access Protocol server When dealing with large amounts of users and many IMAP4 [RFC-2060] servers, it is often necessary to move users from one IMAP4 server to another. Login referrals allow clients to transparently connect to an alternate IMAP4 server, if their home IMAP4 server has changed. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2222 Simple Authentication and Security Layer (SASL) J. Myers October 1997 ASCII 35010 16 SASL encryption protocol specific This document describes a method for adding authentication support to connection-based protocols. [STANDARDS-TRACK] RFC2444 PROPOSED STANDARD PROPOSED STANDARD RFC2223 Instructions to RFC Authors J. Postel J. Reynolds October 1997 ASCII 37948 20 Request For Comment 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. RFC1543 RFC1111 RFC0825 INFORMATIONAL INFORMATIONAL RFC2224 NFS URL Scheme B. Callaghan October 1997 ASCII 22726 11 NFS-URL Universal Resource Locators Network File System syntax directories A new URL scheme, 'nfs' is defined. It is used to refer to files and directories on NFS servers using the general URL syntax defined in RFC 1738, "Uniform Resource Locators (URL)". This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2225 Classical IP and ARP over ATM M. Laubach J. Halpern April 1998 ASCII 65779 28 IP-ATM Internet protocol address resolution asynchronous,transfer mode This memo defines an initial application of classical IP and ARP in an Asynchronous Transfer Mode (ATM) network environment configured as a Logical IP Subnetwork (LIS). [STANDARDS-TRACK] RFC1626 RFC1577 PROPOSED STANDARD PROPOSED STANDARD RFC2226 IP Broadcast over ATM Networks T. Smith G. Armitage October 1997 ASCII 30661 14 Internet Protocol Asynchronous Transfer Mode This memo describes how the IP multicast service being developed by the IP over ATM working group may be used to support IP broadcast transmission. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2227 Simple Hit-Metering and Usage-Limiting for HTTP J. Mogul P. Leach October 1997 ASCII 85127 37 Hypertext Transfer Protocol extension This document proposes a simple extension to HTTP, using a new "Meter" header. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2228 FTP Security Extensions M. Horowitz S. Lunt October 1997 ASCII 58733 27 FTPSECEXT file transfer protocol authentication encoding This document defines extensions to the FTP specification STD 9, RFC RFC0959 PROPOSED STANDARD PROPOSED STANDARD RFC2229 A Dictionary Server Protocol R. Faith B. Martin October 1997 ASCII 59551 30 DSP DICT TCP Transmission Control Protocol database definitions The Dictionary Server Protocol (DICT) is a TCP transaction based query/response protocol that allows a client to access dictionary definitions from a set of natural language dictionary databases. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2230 Key Exchange Delegation Record for the DNS R. Atkinson November 1997 ASCII 25563 11 KEYX-DNS Domain Name System RR Resource Record KX This note describes a mechanism whereby authorisation for one node to act as key exchanger for a second node is delegated and made available via the Secure DNS. This mechanism is intended to be used only with the Secure DNS. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2231 MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations N. Freed K. Moore November 1997 ASCII 19280 10 MIME-EXT Mail Multimedia EMail This memo defines extensions to the RFC 2045 media type and RFC 2183 disposition parameter value mechanisms. This memo also defines an extension to the encoded words defined in RFC 2047 to allow the specification of the language to be used for display as well as the character set. [STANDARDS-TRACK] RFC2184 RFC2045 RFC2047 RFC2183 PROPOSED STANDARD PROPOSED STANDARD RFC2232 Definitions of Managed Objects for DLUR using SMIv2 B. Clouston Editor B. Moore Editor November 1997 ASCII 37955 21 DLUR-MIB Management Information Base MIB Dependent LU Requester APPN Advanced Peek to Peek Networking This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for monitoring and controlling network devices with DLUR (Dependent LU Requester) capabilities. This memo identifies managed objects for the DLUR protocol. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2233 The Interfaces Group MIB using SMIv2 K. McCloghrie F. Kastenholz November 1997 ASCII 148033 66 INTERGRMIB Management Information Base Network 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] RFC1573 RFC2863 PROPOSED STANDARD PROPOSED STANDARD RFC2234 Augmented BNF for Syntax Specifications: ABNF D. Crocker Editor P. Overell November 1997 ASCII 24265 14 ABNF Augmented Backus-Naur Form electronic mail 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] PROPOSED STANDARD PROPOSED STANDARD RFC2235 Hobbes' Internet Timeline R. Zakon November 1997 ASCII 43060 22 events technologies history This document presents a history of the Internet in timeline fashion, highlighting some of the key events and technologies which helped shape the Internet as we know it today. A growth summary of the Internet and some associated technologies is also included. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. FYI0032 INFORMATIONAL INFORMATIONAL RFC2236 Internet Group Management Protocol, Version 2 W. Fenner November 1997 ASCII 51048 24 IGMP IGMP multicast routing IP Internet Protocol This memo documents IGMPv2, used by IP hosts to report their multicast group memberships to routers. It updates STD 5, RFC 1112. [STANDARDS- TRACK] RFC3376 RFC1112 PROPOSED STANDARD PROPOSED STANDARD RFC2237 Japanese Character Encoding for Internet Messages K. Tamaru November 1997 ASCII 11628 6 eletronic mail character set scheme This memo defines an encoding scheme for the Japanese Characters, describes "ISO-2022-JP-1", which is used in electronic mail [RFC-822], and network news [RFC 1036]. Also this memo provides a listing of the Japanese Character Set that can be used in this encoding scheme. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2238 Definitions of Managed Objects for HPR using SMIv2 B. Clouston Editor B. Moore Editor November 1997 ASCII 65498 35 HPR-MIB MIB Management Information Base high performance routing This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for monitoring and controlling network devices with HPR (High Performance Routing) capabilities. This memo identifies managed objects for the HPR protocol. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2239 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2 K. de Graaf D. Romascanu D. McMaster K. McCloghrie S. Roberts November 1997 ASCII 80651 43 MAUS-MIB This memo defines an portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing 10 and 100 Mb/second Medium Attachment Units (MAUs) based on IEEE Std 802.3 Section 30, "10 & 100 Mb/s Management," October 26, 1995. [STANDARDS-TRACK] RFC2668 PROPOSED STANDARD PROPOSED STANDARD RFC2240 A Legal Basis for Domain Name Allocation O. Vaughan November 1997 ASCII 13602 7 DNS 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. RFC2352 INFORMATIONAL INFORMATIONAL RFC2241 DHCP Options for Novell Directory Services D. Provan November 1997 ASCII 8419 5 DHCP-NDS NDS This document defines three new DHCP options for delivering configuration information to clients of the Novell Directory Services. This document defines three new DHCP options for delivering configuration information to clients of the Novell Directory Services. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2242 NetWare/IP Domain Name and Information R. Droms K. Fong November 1997 ASCII 10653 6 NETWAREIP DHCP This document defines options that carry NetWare/IP domain name and NetWare/IP sub-options to DHCP clients. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2243 OTP Extended Responses C. Metz November 1997 ASCII 19730 10 OTP-ER One Time Password This document provides a specification for a type of response to an OTP [RFC 1938] challenge that carries explicit indication of the response's encoding. This document also provides a specification for a response that allows an OTP generator to request that a server re-initialize a sequence and change parameters such as the secret pass phrase. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2244 ACAP -- Application Configuration Access Protocol C. Newman J. G. Myers November 1997 ASCII 154610 71 ACAP URL Uniform Resource Locator The Application Configuration Access Protocol (ACAP) is designed to support remote storage and access of program option, configuration and preference information. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2245 Anonymous SASL Mechanism C. Newman November 1997 ASCII 9974 5 SASL-ANON Simple Authentication Security Layer As plaintext login commands are not permitted in new IETF protocols, a new way to provide anonymous login is needed within the context of the SASL [SASL] framework. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2246 The TLS Protocol Version 1.0 T. Dierks C. Allen January 1999 ASCII 170401 80 transport protocol layer authentication privacy This document specifies Version 1.0 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications privacy over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. [STANDARDS-TRACK] RFC3546 PROPOSED STANDARD PROPOSED STANDARD RFC2247 Using Domains in LDAP/X.500 Distinguished Names S. Kille M. Wahl A. Grimstad R. Huber S. Sataluri January 1998 ASCII 12411 7 lightweight directory access protocol DNS Domain name system This document defines an algorithm by which a name registered with the Internet Domain Name Service [2] can be represented as an LDAP distinguished name. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2248 Network Services Monitoring MIB N. Freed S. Kille January 1998 ASCII 34106 19 NSM-MIB Management Information Base SNMP Simple Network Management Protocol 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] RFC1565 RFC2788 PROPOSED STANDARD PROPOSED STANDARD RFC2249 Mail Monitoring MIB N. Freed S. Kille January 1998 ASCII 52334 28 MAIL-MIB Management Information Base Message Transfer Agents 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] RFC1566 RFC2789 PROPOSED STANDARD PROPOSED STANDARD RFC2250 RTP Payload Format for MPEG1/MPEG2 Video D. Hoffman G. Fernando V. Goyal M. Civanlar January 1998 ASCII 34293 16 RTP-MPEG Real-Time Transport Protocol Audio System Streams This memo describes a packetization scheme for MPEG video and audio streams. [STANDARDS-TRACK] The purpose of this document is to express the general Internet community's expectations of Computer Security Incident Response Teams (CSIRTs). It is not possible to define a set of requirements that would be appropriate for all teams, but it is possible and helpful to list and describe the general set of topics and issues which are of concern and interest to constituent communities. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC2038 PROPOSED STANDARD PROPOSED STANDARD RFC2251 Lightweight Directory Access Protocol (v3) M. Wahl T. Howes S. Kille December 1997 ASCII 114488 50 LDAPV3 LDAv3 x.500 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] RFC3377 RFC3771 PROPOSED STANDARD PROPOSED STANDARD RFC2252 Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions M. Wahl A. Coulbeck T. Howes S. Kille December 1997 ASCII 60204 32 LDAP3-ATD LDAv3 x.500 syntax 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] RFC3377 PROPOSED STANDARD PROPOSED STANDARD RFC2253 Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names M. Wahl S. Kille T. Howes December 1997 ASCII 18226 10 LDAP3-UTF8 LDAPv3 x.500 ASN.1 string format This specification defines the string format for representing names, which is designed to give a clean representation of commonly used distinguished names, while being able to represent any distinguished name. [STANDARDS-TRACK] RFC1779 RFC3377 PROPOSED STANDARD PROPOSED STANDARD RFC2254 The String Representation of LDAP Search Filters T. Howes December 1997 ASCII 13511 8 STR-LDAP LDAPv3 x.500 ASN.1 string format This document defines a human-readable string format for representing LDAP search filters. [STANDARDS-TRACK] RFC1960 RFC3377 PROPOSED STANDARD PROPOSED STANDARD RFC2255 The LDAP URL Format T. Howes M. Smith December 1997 ASCII 20685 10 LDAP-URL Lightweight Directory Access Protocol Universal Resource Locator This document describes a format for an LDAP Uniform Resource Locator. [STANDARDS-TRACK] RFC1959 RFC3377 PROPOSED STANDARD PROPOSED STANDARD RFC2256 A Summary of the X.500(96) User Schema for use with LDAPv3 M. Wahl December 1997 ASCII 32377 20 Lightweight Directory Access Protocol syntax 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] RFC3377 PROPOSED STANDARD PROPOSED STANDARD RFC2257 Agent Extensibility (AgentX) Protocol Version 1 M. Daniele B. Wijnen D. Francisco January 1998 ASCII 177452 80 AGENTX SNMP Simple Network Management Protocol MIB Information Base 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] RFC2741 PROPOSED STANDARD PROPOSED STANDARD RFC2258 Internet Nomenclator Project J. Ordille January 1998 ASCII 34871 15 Database Server CCSO Computer Communications Services Office The goal of the Internet Nomenclator Project is to integrate the hundreds of publicly available CCSO servers from around the world. This document provides an overview of the Nomenclator system, describes how to register a CCSO server in the Internet Nomenclator Project, and how to use the Nomenclator search engine to find people on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2259 Simple Nomenclator Query Protocol (SNQP) J. Elliott J. Ordille January 1998 ASCII 58508 30 SNQP Data Repositories Client Server The Simple Nomenclator Query Protocol (SNQP) allows a client to communicate with a descriptive name service or other relational-style query service. This memo provides information for the Internet community. It does not specify an Internet standard of any kind INFORMATIONAL INFORMATIONAL RFC2260 Scalable Support for Multi-homed Multi-provider Connectivity T. Bates Y. Rekhter January 1998 ASCII 28085 12 ISP Internet Service Provider Routing This document describes addressing and routing strategies for multi- homed enterprises attached to multiple Internet Service Providers (ISPs) that are intended to reduce the routing overhead due to these enterprises in the global Internet routing system. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2261 An Architecture for Describing SNMP Management Frameworks D. Harrington R. Presuhn B. Wijnen January 1998 ASCII 128036 56 Simple Network Management Protocol Message Network Management Protocol security access control snmpv3 This document describes an architecture for describing SNMP Management Frameworks. The architecture is designed to be modular to allow the evolution of the SNMP protocol standards over time. [STANDARDS-TRACK] RFC2271 PROPOSED STANDARD PROPOSED STANDARD RFC2262 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) J. Case D. Harrington R. Presuhn B. Wijnen January 1998 ASCII 88254 39 architecture SNMPv3 multiple versions This document describes the Message Processing and Dispatching for SNMP messages within the SNMP architecture [RFC2261]. It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP Message Processing Models, and for dispatching PDUs to SNMP applications. This document also describes one Message Processing Model - the SNMPv3 Message Processing Model. [STANDARDS-TRACK] RFC2272 PROPOSED STANDARD PROPOSED STANDARD RFC2263 SNMPv3 Applications D. Levi P. Meyer B. Stewart January 1998 ASCII 143493 70 Simple Network Management Protocol operations notification filtering proxy forwarding This memo describes five types of SNMP applications which make use of an SNMP engine as described in [RFC2261]. The types of application described are Command Generators, Command Responders, Notification Originators, Notification Receivers, and Proxy Forwarders. This memo also defines MIB modules for specifying targets of management operations, for notification filtering, and for proxy forwarding. [STANDARDS-TRACK] RFC2273 PROPOSED STANDARD PROPOSED STANDARD RFC2264 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) U. Blumenthal B. Wijnen January 1998 ASCII 168759 76 architecture message level This document describes the User-based Security Model (USM) for SNMP version 3 for use in the SNMP architecture [RFC2261]. It defines the Elements of Procedure for providing SNMP message level security. This document also includes a MIB for remotely monitoring/managing the configuration parameters for this Security Model. [STANDARDS-TRACK] RFC2274 PROPOSED STANDARD PROPOSED STANDARD RFC2265 View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) B. Wijnen R. Presuhn K. McCloghrie January 1998 ASCII 77807 36 SNMPV3 Architecture This document describes the View-based Access Control Model for use in the SNMP architecture [RFC2261]. It defines the Elements of Procedure for controlling access to management information. This document also includes a MIB for remotely managing the configuration parameters for the View-based Access Control Model. [STANDARDS-TRACK] RFC2275 PROPOSED STANDARD PROPOSED STANDARD RFC2266 Definitions of Managed Objects for IEEE 802.12 Repeater Devices J. Flick January 1998 ASCII 134027 56 MIB Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing network repeaters based on IEEE 802.12. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2267 Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing P. Ferguson D. Senie January 1998 ASCII 21032 10 ISP Internet Service Provider Internet Protocol DOS This paper discusses a simple, effective, and straightforward method for using ingress traffic filtering to prohibit DoS attacks which use forged IP addresses to be propagated from 'behind' an Internet Service Provider's (ISP) aggregation point. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. RFC2827 INFORMATIONAL INFORMATIONAL RFC2268 A Description of the RC2(r) Encryption Algorithm R. Rivest March 1998 ASCII 19048 11 RC2-ENCRP encryption secre key rsa This memo describes a conventional (secret-key) block encryption algorithm, called RC2, which may be considered as a proposal for a DES replacement. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2269 Using the MARS Model in non-ATM NBMA Networks G. Armitage January 1998 ASCII 12094 6 Asynchronous Transfer Mode Multicast Address Resolution Server IP Internet Protocol This document is intended to state the obvious equivalences, and explain the less obvious implications. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2270 Using a Dedicated AS for Sites Homed to a Single Provider J. Stewart T. Bates R. Chandra E. Chen January 1998 ASCII 12063 6 Autonomous System BGP4 Border Gateway Protocol ISP Internet Service With the increased growth of the Internet, the number of customers using BGP4 has grown significantly. RFC1930 outlines a set of guidelines for when one needs and should use an AS. However, the customer and service provider (ISP) are left with a problem as a result of this in that while there is no need for an allocated AS under the guidelines, certain conditions make the use of BGP4 a very pragmatic and perhaps only way to connect a customer homed to a single ISP. This paper proposes a solution to this problem in line with recommendations set forth in RFC1930. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2271 An Architecture for Describing SNMP Management Frameworks D. Harrington R. Presuhn B. Wijnen January 1998 ASCII 128227 56 Simple Network Management Protocol Message Network Management Protocol security access control snmpv3 This document describes an architecture for describing SNMP Management Frameworks. The architecture is designed to be modular to allow the evolution of the SNMP protocol standards over time. [STANDARDS-TRACK] RFC2261 RFC2571 PROPOSED STANDARD PROPOSED STANDARD RFC2272 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) J. Case D. Harrington R. Presuhn B. Wijnen January 1998 ASCII 88445 39 SNMPv3 architecture SNMPv3 multiple versions This document describes the Message Processing and Dispatching for SNMP messages within the SNMP architecture [RFC2271]. It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP Message Processing Models, and for dispatching PDUs to SNMP applications. This document also describes one Message Processing Model - the SNMPv3 Message Processing Model. [STANDARDS-TRACK] RFC2262 RFC2572 PROPOSED STANDARD PROPOSED STANDARD RFC2273 SNMPv3 Applications D. Levi P. Meyer B. Stewart January 1998 ASCII 143754 70 Simple Network Management Protocol operations notification filtering proxy forwarding This memo describes five types of SNMP applications which make use of an SNMP engine as described in [RFC2261]. The types of application described are Command Generators, Command Responders, Notification Originators, Notification Receivers, and Proxy Forwarders. This memo also defines MIB modules for specifying targets of management operations, for notification filtering, and for proxy forwarding. [STANDARDS-TRACK] RFC2263 RFC2573 PROPOSED STANDARD PROPOSED STANDARD RFC2274 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) U. Blumenthal B. Wijnen January 1998 ASCII 168950 76 architecture message level This document describes the User-based Security Model (USM) for SNMP version 3 for use in the SNMP architecture [RFC2261]. It defines the Elements of Procedure for providing SNMP message level security. This document also includes a MIB for remotely monitoring/managing the configuration parameters for this Security Model. [STANDARDS-TRACK] RFC2264 RFC2574 PROPOSED STANDARD PROPOSED STANDARD RFC2275 View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) B. Wijnen R. Presuhn K. McCloghrie January 1998 ASCII 77998 36 SNMPV3 Architecture This document describes the View-based Access Control Model for use in the SNMP architecture [RFC2261]. It defines the Elements of Procedure for controlling access to management information. This document also includes a MIB for remotely managing the configuration parameters for the View-based Access Control Model. [STANDARDS-TRACK] RFC2265 RFC2575 PROPOSED STANDARD PROPOSED STANDARD RFC2276 Architectural Principles of Uniform Resource Name Resolution K. Sollins January 1998 ASCII 64811 24 URCs URN URLs Uniform Resource Locators Characteristics This document addresses the issues of the discovery of URN (Uniform Resource Name) resolver services that in turn will directly translate URNs into URLs (Uniform Resource Locators) and URCs (Uniform Resource Characteristics). This memo provides information for the Internet community. It does not specify an Internet standard of any kind. RFC3401 INFORMATIONAL INFORMATIONAL RFC2277 IETF Policy on Character Sets and Languages H. Alvestrand January 1998 ASCII 16622 9 charset This document is the current policies being applied by the Internet Engineering Steering Group (IESG) towards the standardization efforts in the Internet Engineering Task Force (IETF) in order to help Internet protocols fulfill these requirements. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP0018 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2278 IANA Charset Registration Procedures N. Freed J. Postel January 1998 ASCII 18881 10 character set mime multipurpose internet mail extensions MIME [RFC-2045, RFC-2046, RFC-2047, RFC-2184] and various other modern Internet protocols are capable of using many different charsets. This in turn means that the ability to label different charsets is essential. This registration procedure exists solely to associate a specific name or names with a given charset and to give an indication of whether or not a given charset can be used in MIME text objects. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Status changed from BCP for consistency 10Feb01 RFC2978 INFORMATIONAL BEST CURRENT PRACTICE RFC2279 UTF-8, a transformation format of ISO 10646 F. Yergeau January 1998 ASCII 21634 10 UTF-8 UCS Transformation Format UTF-8, the object of this memo, has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo updates and replaces RFC 2044, in particular addressing the question of versions of the relevant standards. [STANDARDS-TRACK] RFC2044 RFC3629 DRAFT STANDARD PROPOSED STANDARD RFC2280 Routing Policy Specification Language (RPSL) C. Alaettinoglu T. Bates E. Gerich D. Karrenberg D. Meyer M. Terpstra C. Villamizar January 1998 ASCII 114985 53 RPSL network operator AS autonomous system database This memo is the reference document for the Routing Policy Specification Language (RPSL). RPSL allows a network operator to be able to specify routing policies at various levels in the Internet hierarchy; for example at the Autonomous System (AS) level. At the same time, policies can be specified with sufficient detail in RPSL so that low level router configurations can be generated from them. RPSL is extensible; new routing protocols and new protocol features can be introduced at any time. [STANDARDS-TRACK] RFC2622 PROPOSED STANDARD PROPOSED STANDARD RFC2281 Cisco Hot Standby Router Protocol (HSRP) T. Li B. Cole P. Morton D. Li March 1998 ASCII 35161 17 HSRP The memo specifies the Hot Standby Router Protocol (HSRP). The goal of the protocol is to allow hosts to appear to use a single router and to maintain connectivity even if the actual first hop router they are using fails. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2282 IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees J. Galvin February 1998 ASCII 29852 14 Internet Architecture Board Engineering Steering Group The process by which the members of the IAB and IESG are selected, confirmed, and recalled is specified. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC2027 RFC2727 INFORMATIONAL BEST CURRENT PRACTICE RFC2283 Multiprotocol Extensions for BGP-4 T. Bates R. Chandra D. Katz Y. Rekhter February 1998 ASCII 18946 9 MEXT-BGP4 Border gateway protocol router network layer This document defines extensions to BGP-4 to enable it to carry routing information for multiple Network Layer protocols (e.g., IPv6, IPX, etc...). The extensions are backward compatible - a router that supports the extensions can interoperate with a router that doesn't support the extensions. [STANDARDS-TRACK] RFC2858 PROPOSED STANDARD PROPOSED STANDARD RFC2284 PPP Extensible Authentication Protocol (EAP) L. Blunk J. Vollbrecht March 1998 ASCII 29452 15 PPP-EAP point-to-point authentication The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP also defines an extensible Link Control Protocol, which allows negotiation of an Authentication Protocol for authenticating its peer before allowing Network Layer protocols to transmit over the link. This document defines the PPP Extensible Authentication Protocol. [STANDARDS-TRACK] RFC3748 RFC2484 PROPOSED STANDARD PROPOSED STANDARD RFC2285 Benchmarking Terminology for LAN Switching Devices R. Mandeville February 1998 ASCII 43130 25 local area network MAC Medium Access Control layer This document is intended to provide terminology for the benchmarking of local area network (LAN) switching devices. It extends the terminology already defined for benchmarking network interconnect devices in RFCs 1242 and 1944 to switching devices. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2286 Test Cases for HMAC-RIPEMD160 and HMAC-RIPEMD128 J. Kapp February 1998 ASCII 11849 7 has authentication message IP Internet Protocol codes This document provides two sets of test cases for HMAC-RIPEMD160 and HMAC-RIPEMD128. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2287 Definitions of System-Level Managed Objects for Applications C. Krupczak J. Saperia February 1998 ASCII 98210 44 SLM-APP mib management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a basic set of managed objects for fault, configuration and performance management of applications from a systems perspective. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2288 Using Existing Bibliographic Identifiers as Uniform Resource Names C. Lynch C. Preston R. Daniel February 1998 ASCII 21628 10 URNs Syntax framework This document discusses how three major bibliographic identifiers (the ISBN, ISSN and SICI) can be supported within the URN framework and the currently proposed syntax for URNs. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2289 A One-Time Password System N. Haller C. Metz P. Nesser M. Straw February 1998 ASCII 56495 25 ONE-PASS authentication OTP replay attach This document describes a one-time password authentication system (OTP). The system provides authentication for system access (login) and other applications requiring authentication that is secure against passive attacks based on replaying captured reusable passwords. [STANDARDS- TRACK] RFC1938 STD0061 STANDARD DRAFT STANDARD RFC2290 Mobile-IPv4 Configuration Option for PPP IPCP J. Solomon S. Glass February 1998 ASCII 39421 17 Internet protocol point-to-point control address Mobile IP [RFC 2002] defines media-independent procedures by which a Mobile Node can maintain existing transport and application-layer connections despite changing its point-of-attachment to the Internet and without changing its IP address. PPP [RFC 1661] provides a standard method for transporting multi-protocol packets over point-to-point links. As currently specified, Mobile IP Foreign Agents which support Mobile Node connections via PPP can do so only by first assigning unique addresses to those Mobile Nodes, defeating one of the primary advantages of Foreign Agents. This documents corrects this problem by defining the Mobile-IPv4 Configuration Option to the Internet Protocol Control Protocol (IPCP) [RFC 1332]. Using this option, two peers can communicate their support for Mobile IP during the IPCP phase of PPP. Familiarity with Mobile IP [RFC 2002], IPCP [RFC 1332], and PPP [RFC 1661] is assumed. [STANDARDS-TRACK] RFC2002 RFC2794 PROPOSED STANDARD PROPOSED STANDARD RFC2291 Requirements for a Distributed Authoring and Versioning Protocol for the World Wide Web J. Slein F. Vitali E. Whitehead D. Durand February 1998 ASCII 44036 21 WWW remote editing locking mechanism This document presents a list of features in the form of requirements for a Web Distributed Authoring and Versioning protocol which, if implemented, would improve the efficiency of common remote editing operations, provide a locking mechanism to prevent overwrite conflicts, improve link management support between non-HTML data types, provide a simple attribute-value metadata facility, provide for the creation and reading of container data types, and integrate versioning into the WWW. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2292 Advanced Sockets API for IPv6 W. Stevens M. Thomas February 1998 ASCII 152077 67 application program interface The current document defines some the "advanced" features of the sockets API that are required for applications to take advantage of additional features of IPv6. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. RFC3542 INFORMATIONAL INFORMATIONAL RFC2293 Representing Tables and Subtrees in the X.500 Directory S. Kille March 1998 ASCII 12539 8 SUBTABLE mapping distinguished name This document defines techniques for representing two types of information mapping in the OSI Directory: Mapping from a key to a value (or set of values), as might be done in a table lookup, and mapping from a distinguished name to an associated value (or values), where the values are not defined by the owner of the entry. This is achieved by use of a directory subtree. [STANDARDS-TRCK] RFC1837 PROPOSED STANDARD PROPOSED STANDARD RFC2294 Representing the O/R Address hierarchy in the X.500 Directory Information Tree S. Kille March 1998 ASCII 22059 13 OR-ADD routing mapping dit This document defines a representation of the O/R Address hierarchy in the Directory Information Tree. [STANDARDS-TRACK] RFC1836 PROPOSED STANDARD PROPOSED STANDARD RFC2295 Transparent Content Negotiation in HTTP K. Holtman A. Mutz March 1998 ASCII 125130 58 TCN-HTTP Hyper Text Transfer protocol URL Uniform Resource Locators HTTP allows web site authors to put multiple versions of the same information under a single URL. Transparent content negotiation is an extensible negotiation mechanism, layered on top of HTTP, for automatically selecting the best version when the URL is accessed. This enables the smooth deployment of new web data formats and markup tags. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. EXPERIMENTAL EXPERIMENTAL RFC2296 HTTP Remote Variant Selection Algorithm -- RVSA/1.0 K. Holtman A. Mutz March 1998 ASCII 26932 13 HTTP-RVSA Hyper Text Transfer protocol URL Uniform Resource Locators HTTP allows web site authors to put multiple versions of the same information under a single URL. Transparent content negotiation is a mechanism for automatically selecting the best version when the URL is accessed. A remote variant selection algorithm can be used to speed up the transparent negotiation process. This document defines the remote variant selection algorithm with the version number 1.0. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. EXPERIMENTAL EXPERIMENTAL RFC2297 Ipsilon's General Switch Management Protocol Specification Version 2.0 P. Newman W. Edwards R. Hinden E. Hoffman F. Ching Liaw T. Lyon G. Minshall March 1998 ASCII 280484 109 GSMP gsmp atm asynchronous transfer mode This memo specifies enhancements to the General Switch Management Protocol (GSMP) [RFC1987]. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. RFC1987 INFORMATIONAL INFORMATIONAL RFC2298 An Extensible Message Format for Message Disposition Notifications R. Fajman March 1998 ASCII 62059 28 EMF-MDN MDN media-type MIME multipurpose internet mail extensions This memo defines a MIME content-type that may be used by a mail user agent (UA) or electronic mail gateway to report the disposition of a message after it has been sucessfully delivered to a recipient. [STANDARDS-TRACK] RFC3798 PROPOSED STANDARD PROPOSED STANDARD RFC2299 Request for Comments Summary A. Ramos January 1999 ASCII 51234 24 INFORMATIONAL INFORMATIONAL RFC2300 Internet Official Protocol Standards J. Postel May 1998 ASCII 128322 59 IAB official protocol standards A discussion of the standardization process and the RFC document series is presented first, followed by an explanation of the terms. Sections 6.2 - 6.10 contain the lists of protocols in each stage of standardization. Finally are pointers to references and contacts for further information. [STANDARDS-TRACK] RFC2200 RFC2400 HISTORIC STANDARD RFC2301 File Format for Internet Fax L. McIntyre S. Zilles R. Buckley D. Venable G. Parsons J. Rafferty March 1998 ASCII 200525 77 FFIF TIFF Tag Image facsimile MIME multipurpose Internet mail extensions This document describes the TIFF (Tag Image File Format) representation of image data specified by the ITU-T Recommendations for black-and-white and color facsimile. [STANDARDS-TRACK] RFC3949 PROPOSED STANDARD PROPOSED STANDARD RFC2302 Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration G. Parsons J. Rafferty S. Zilles March 1998 ASCII 14375 8 TIFF Multipurpose Internet Mail extensions This document describes the registration of the MIME sub-type image/tiff. [STANDARDS-TRACK] RFC3302 PROPOSED STANDARD PROPOSED STANDARD RFC2303 Minimal PSTN address format in Internet Mail C. Allocchio March 1998 ASCII 14625 8 MIN-PSTN e-mail service This memo describes the MINIMAL addressing method to encode PSTN addresses into e-mail addresses and the standard extension mechanism to allow definition of further standard elements. [STANDARDS-TRACK] RFC3191 PROPOSED STANDARD PROPOSED STANDARD RFC2304 Minimal FAX address format in Internet Mail C. Allocchio March 1998 ASCII 13236 8 MINFAX-IM encoding facsimile e-mail This memo describes the MINIMAL addressing method and standard extensions to encode FAX addresses in e-mail addresses. [STANDARDS- TRACK] RFC3192 PROPOSED STANDARD PROPOSED STANDARD RFC2305 A Simple Mode of Facsimile Using Internet Mail K. Toyoda H. Ohno J. Murai D. Wing March 1998 ASCII 24624 13 SMFAX-IM data file format e-mail This specification provides for "simple mode" carriage of facsimile data over the Internet. [STANDARDS-TRACK] RFC3965 PROPOSED STANDARD PROPOSED STANDARD RFC2306 Tag Image File Format (TIFF) - F Profile for Facsimile G. Parsons J. Rafferty March 1998 ASCII 59358 25 file format storage This document describes in detail the definition of TIFF-F that is used to store facsimile images. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2307 An Approach for Using LDAP as a Network Information Service L. Howard March 1998 ASCII 41396 21 LDAP-NIS lightweight directory access protocol unix mapping This document describes an experimental mechanism for mapping entities related to TCP/IP and the UNIX system into X.500 entries so that they may be resolved with the Lightweight Directory Access Protocol [RFC2251]. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. EXPERIMENTAL EXPERIMENTAL RFC2308 Negative Caching of DNS Queries (DNS NCACHE) M. Andrews March 1998 ASCII 41428 19 DNS-NCACHE Domain Name System negative RFC1034 provided a description of how to cache negative responses. It however had a fundamental flaw in that it did not allow a name server to hand out those cached responses to other resolvers, thereby greatly reducing the effect of the caching. This document addresses issues raise in the light of experience and replaces RFC1034 Section 4.3.4. [STANDARDS-TRACK] RFC1034 RFC1035 RFC4033 RFC4034 RFC4035 PROPOSED STANDARD PROPOSED STANDARD RFC2309 Recommendations on Queue Management and Congestion Avoidance in the Internet B. Braden D. Clark J. Crowcroft B. Davie S. Deering D. Estrin S. Floyd V. Jacobson G. Minshall C. Partridge L. Peterson K. Ramakrishnan S. Shenker J. Wroclawski L. Zhang April 1998 ASCII 38079 17 performance router deployment This memo presents two recommendations to the Internet community concerning measures to improve and preserve Internet performance. It presents a strong recommendation for testing, standardization, and widespread deployment of active queue management in routers, to improve the performance of today's Internet. It also urges a concerted effort of research, measurement, and ultimate deployment of router mechanisms to protect the Internet from flows that are not sufficiently responsive to congestion notification. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2310 The Safe Response Header Field K. Holtman April 1998 ASCII 8091 5 http hyper text transfer protocol This document defines a HTTP response header field called Safe, which can be used to indicate that repeating a HTTP request is safe. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. EXPERIMENTAL EXPERIMENTAL RFC2311 S/MIME Version 2 Message Specification S. Dusse P. Hoffman B. Ramsdell L. Lundblade L. Repka March 1998 ASCII 70901 37 SMIME-MSG secure multipurpose internet mail extensions This document describes a protocol for adding cryptographic signature and encryption services to MIME data. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2312 S/MIME Version 2 Certificate Handling S. Dusse P. Hoffman B. Ramsdell J. Weinstein March 1998 ASCII 39829 20 SMIME-CERT secure multipurpose internet mail extensions This memo describes the mechanisms S/MIME uses to create and validate keys using certificates. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2313 PKCS #1: RSA Encryption Version 1.5 B. Kaliski March 1998 ASCII 37777 19 PKCS-1 data public key cryptosystem This document describes a method for encrypting data using the RSA public-key cryptosystem. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. RFC2437 INFORMATIONAL INFORMATIONAL RFC2314 PKCS #10: Certification Request Syntax Version 1.5 B. Kaliski March 1998 ASCII 15814 8 PKCS-10 public key distinguished name encryption data This document describes a syntax for certification requests. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. RFC2986 INFORMATIONAL INFORMATIONAL RFC2315 PKCS #7: Cryptographic Message Syntax Version 1.5 B. Kaliski March 1998 ASCII 69679 32 PKCS-7 data authentication PEM privacy enhanced mail This document describes a general syntax for data that may have cryptography applied to it, such as digital signatures and digital envelopes. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2316 Report of the IAB Security Architecture Workshop S. Bellovin April 1998 ASCII 19733 9 Internet Board protocols tools On 3-5 March 1997, the IAB held a security architecture workshop at Bell Labs in Murray Hill, NJ. We identified the core security components of the architecture, and specified several documents that need to be written. Most importantly, we agreed that security was not optional, and that it needed to be designed in from the beginning. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2317 Classless IN-ADDR.ARPA delegation H. Eidnes G. de Groot P. Vixie March 1998 ASCII 17744 10 routing mapping addresses zone files This document describes a way to do IN-ADDR.ARPA delegation on non-octet boundaries for address spaces covering fewer than 256 addresses. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP0020 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2318 The text/css Media Type H. Lie B. Bos C. Lilley March 1998 ASCII 7819 5 TEXT-CSS MIME multipurpose Internet mail extension This memo provides information about the text/css Media Type. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2319 Ukrainian Character Set KOI8-U KOI8-U Working Group April 1998 ASCII 18042 9 KOI8-U encoding mail information resources This document provides information about character encoding KOI8-U (KOI8 Ukrainian) wich is a de-facto standard in Ukrainian Internet community. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2320 Definitions of Managed Objects for Classical IP and ARP Over ATM Using SMIv2 (IPOA-MIB) M. Greene J. Luciani K. White T. Kuo April 1998 ASCII 102116 52 IPOA-MIB management information base internet protocol address resolution asynchronous transfer mode The purpose of this memo is to define the Management Information Base (MIB) for supporting Classical IP and ARP over ATM as specified in Classical IP and ARP over ATM. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2321 RITA -- The Reliable Internetwork Troubleshooting Agent A. Bressen April 01 1998 ASCII 12302 6 networking environments A Description of the usage of Nondeterministic Troubleshooting and Diagnostic Methodologies as applied to today's complex nondeterministic networks and environments. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2322 Management of IP numbers by peg-dhcp K. van den Hout A. Koopal R. van Mook April 01 1998 ASCII 12665 7 Internet Protocol HIP Hacking in progress This RFC describes a protocol to dynamically hand out ip-numbers on field networks and small events that don't necessarily have a clear organisational body. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2323 IETF Identification and Security Guidelines A. Ramos April 01 1998 ASCII 9257 5 facial hairius extremis FHE This RFC is meant to represent a guideline by which the IETF conferences may run more effeciently with regards to identification and security protocols, with specific attention paid to a particular sub-group within the IETF: "facial hairius extremis". This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2324 Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0) L. Masinter April 01 1998 ASCII 19610 10 controlling monitoring diagnosing This document describes HTCPCP, a protocol for controlling, monitoring, and diagnosing coffee pots. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2325 Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2 M. Slavitch April 01 1998 ASCII 12726 8 MIB management information base coffee brewing This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for the management of coffee-brewing and maintenance devices. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2326 Real Time Streaming Protocol (RTSP) H. Schulzrinne A. Rao R. Lanphier April 1998 ASCII 195010 92 RTSP audio video data delivery application level, The Real Time Streaming Protocol, or RTSP, is an application-level protocol for control over the delivery of data with real-time properties. RTSP provides an extensible framework to enable controlled, on-demand delivery of real-time data, such as audio and video. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2327 SDP: Session Description Protocol M. Handley V. Jacobson April 1998 ASCII 87096 42 SDP mbone internet multicast backbone multimedia This document defines the Session Description Protocol, SDP. SDP is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. [STANDARDS-TRACK] RFC3266 PROPOSED STANDARD PROPOSED STANDARD RFC2328 OSPF Version 2 J. Moy April 1998 ASCII 447367 244 OSPF2 Open Shortest Path First routing Autonomous system AS This memo documents version 2 of the OSPF protocol. OSPF is a link- state routing protocol. [STANDARDS-TRACK] RFC2178 STD0054 STANDARD STANDARD RFC2329 OSPF Standardization Report J. Moy April 1998 ASCII 15130 9 open shortest path first This memo documents how the requirements for advancing a routing protocol to Full Standard have been met for OSPFv2. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2330 Framework for IP Performance Metrics V. Paxson G. Almes J. Mahdavi M. Mathis May 1998 ASCII 94387 40 Internet Protocol measurement statistics The purpose of this memo is to define a general framework for particular metrics to be developed by the IETF's IP Performance Metrics effort. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2331 ATM Signalling Support for IP over ATM - UNI Signalling 4.0 Update M. Maher April 1998 ASCII 61119 26 UNI-SIG asynchronous transfer mode internet protocol This memo describes how to efficiently use the ATM call control signalling procedures defined in UNI Signalling 4.0 to support IP over ATM environments as described in RFC 2225 and in RFC 2332. [STANDARDS- TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2332 NBMA Next Hop Resolution Protocol (NHRP) J. Luciani D. Katz D. Piscitello B. Cole N. Doraswamy April 1998 ASCII 126978 52 NHRP internetworking layer address subnetwork multiprotocol non-broadcast multiple access This document describes the NBMA Next Hop Resolution Protocol (NHRP). NHRP can be used by a source station (host or router) connected to a Non-Broadcast, Multi-Access (NBMA) subnetwork to determine the internetworking layer address and NBMA subnetwork addresses of the "NBMA next hop" towards a destination station. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2333 NHRP Protocol Applicability Statement D. Cansever April 1998 ASCII 20164 9 next hop resolution protocol routing internet protocol As required by the Routing Protocol Criteria [RFC 1264], this memo discusses the applicability of the Next Hop Resolution Protocol (NHRP) in routing of IP datagrams over Non-Broadcast Multiple Access (NBMA) networks, such as ATM, SMDS and X.25. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2334 Server Cache Synchronization Protocol (SCSP) J. Luciani G. Armitage J. Halpern N. Doraswamy April 1998 ASCII 98161 40 SCSP cache synchronization replication NBMA non broadcast multiple access This document describes the Server Cache Synchronization Protocol (SCSP) and is written in terms of SCSP's use within Non Broadcast Multiple Access (NBMA) networks; although, a somewhat straight forward usage is applicable to BMA networks. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2335 A Distributed NHRP Service Using SCSP J. Luciani April 1998 ASCII 14007 7 NHRP-SCSP next hop resolution protocol server cache sychronization protocol This document describes a method for distributing an NHRP service within a LIS. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2336 Classical IP to NHRP Transition J. Luciani July 1998 ASCII 10500 5 This document describes methods and procedures for the graceful transition from an ATMARP LIS to an NHRP LIS network model over ATM. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2337 Intra-LIS IP multicast among routers over ATM using Sparse Mode PIM D. Farinacci D. Meyer Y. Rekhter April 1998 ASCII 16357 8 internet protocol asynchronous transfer mode This document describes how intra-LIS IP multicast can be efficiently supported among routers over ATM without using the Multicast Address Resolution Server (MARS). This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. EXPERIMENTAL EXPERIMENTAL RFC2338 Virtual Router Redundancy Protocol S. Knight D. Weaver D. Whipple R. Hinden D. Mitzel P. Hunt P. Higginson M. Shand A. Lindem April 1998 ASCII 59871 27 VRRP vrrp lan local area network ip internet protocol This memo defines the Virtual Router Redundancy Protocol (VRRP). VRRP specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. [STANDARDS- TRACK] RFC3768 PROPOSED STANDARD PROPOSED STANDARD RFC2339 An Agreement Between the Internet Society, the IETF, and Sun Microsystems, Inc. in the matter of NFS V.4 Protocols The Internet Society Sun Microsystems May 1998 ASCII 10745 5 ISOC network file system internet engineering task force This Request for Comments records an agreement between Sun Microsystems, Inc. and the Internet Society to permit the flow of Sun's Network File System specifications into the Internet Standards process conducted by the Internet Engineering Task Force. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2340 Nortel's Virtual Network Switching (VNS) Overview B. Jamoussi D. Jamieson D. Williston S. Gabe May 1998 ASCII 30731 14 routing packet switching multi-protocol This document provides an overview of Virtual Network Switching (VNS). This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2341 Cisco Layer Two Forwarding (Protocol) "L2F" A. Valencia M. Littlewood T. Kolar May 1998 ASCII 66592 29 L2F tunneling dial-up network This document describes the Layer Two Forwarding protocol (L2F) which permits the tunneling of the link layer (i.e., HDLC, async HDLC, or SLIP frames) of higher level protocols. This memo describes a historic protocol for the Internet community. It does not specify an Internet standard of any kind. HISTORIC HISTORIC RFC2342 IMAP4 Namespace M. Gahrns C. Newman May 1998 ASCII 19489 10 IMAP4NAME internet message access protocol mailbox This document defines a NAMESPACE command that allows a client to discover the prefixes of namespaces used by a server for personal mailboxes, other users' mailboxes, and shared mailboxes. [STANDARDS- TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2343 RTP Payload Format for Bundled MPEG M. Civanlar G. Cash B. Haskell May 1998 ASCII 16557 8 RTP-MPEG real-time transport protocol audio video This document describes a payload type for bundled, MPEG-2 encoded video and audio data that may be used with RTP, version 2. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. EXPERIMENTAL EXPERIMENTAL RFC2344 Reverse Tunneling for Mobile IP G. Montenegro Editor May 1998 ASCII 39468 19 MOBILIPREV internet protocol extensions home foreign agent encapsulating delivery style This document proposes backwards-compatible extensions to Mobile IP in order to support topologically correct reverse tunnels. [STANDARDS- TRACK] RFC3024 PROPOSED STANDARD PROPOSED STANDARD RFC2345 Domain Names and Company Name Retrieval J. Klensin T. Wolf G. Oglesby May 1998 ASCII 29707 14 URL mapping service whois dns This document proposes a company name to URL mapping service based on the oldest and least complex of Internet directory protocols, whois, in order to explore whether an extremely simple and widely-deployed protocol can succeed where more complex and powerful options have failed or been excessively delayed. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. EXPERIMENTAL EXPERIMENTAL RFC2346 Making Postscript and PDF International J. Palme May 1998 ASCII 12382 6 portable document format document Certain text formats, for example Postscript (MIME-Type: application/postscript; file extension .ps) and Portable Document Format (MIME-Type: application/pdf; file extension .pdf) specify exactly the page layout of the printed document. The commonly used paper format is different in North America and the rest of the world. North America uses the 'Letter' format, while the rest of the world mostly uses the ISO-standard 'A4' format. This means that documents formatted on one continent may not be easily printable on another continent. This memo gives advice on how to produce documents which are equally well printable with the Letter and the A4 formats. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2347 TFTP Option Extension G. Malkin A. Harkin May 1998 ASCII 13060 7 TFTP-Ext trivial file transfer booting client server The Trivial File Transfer Protocol is a simple, lock-step, file transfer protocol which allows a client to get or put a file onto a remote host. This document describes a simple extension to TFTP to allow option negotiation prior to the file transfer. [STANDARDS-TRACK] RFC1782 RFC1350 DRAFT STANDARD DRAFT STANDARD RFC2348 TFTP Blocksize Option G. Malkin A. Harkin May 1998 ASCII 9515 5 TFTP-Blk trivial file transfer booting client server extension The Trivial File Transfer Protocol is a simple, lock-step, file transfer protocol which allows a client to get or put a file onto a remote host. This document describes a TFTP option which allows the client and server to negotiate a blocksize more applicable to the network medium. [STANDARDS-TRACK] RFC1783 RFC1350 DRAFT STANDARD DRAFT STANDARD RFC2349 TFTP Timeout Interval and Transfer Size Options G. Malkin A. Harkin May 1998 ASCII 7848 5 TFTP-Opt trivial file transfer booting client server extension The Trivial File Transfer Protocol is a simple, lock-step, file transfer protocol which allows a client to get or put a file onto a remote host. This document describes two TFTP options. [STANDARDS-TRACK] RFC1784 RFC1350 DRAFT STANDARD DRAFT STANDARD RFC2350 Expectations for Computer Security Incident Response N. Brownlee E. Guttman June 1998 ASCII 86545 38 CSIRT guidelines user BCP0021 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2351 Mapping of Airline Reservation, Ticketing, and Messaging Traffic over IP A. Robert May 1998 ASCII 43440 23 internet protocol encapsulation transactional traffic messaging This memo specifies a protocol for the encapsulation of the airline specific protocol over IP. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2352 A Convention For Using Legal Names as Domain Names O. Vaughan May 1998 ASCII 16354 8 DNS 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. RFC2240 INFORMATIONAL INFORMATIONAL RFC2353 APPN/HPR in IP Networks APPN Implementers' Workshop Closed Pages Document G. Dudley May 1998 ASCII 116972 48 internet protocol advanced peer-to-peer networking high performance routing This memo defines a method with which HPR nodes can use IP networks for communication, and the enhancements to APPN required by this method. This memo also describes an option set that allows the use of the APPN connection network model to allow HPR nodes to use IP networks for communication without having to predefine link connections. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2354 Options for Repair of Streaming Media C. Perkins O. Hodson June 1998 ASCII 28876 12 packets UDP user datagram protocol This document summarizes a range of possible techniques for the repair of continuous media streams subject to packet loss. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2355 TN3270 Enhancements B. Kelly June 1998 ASCII 89394 38 TN3270E Telnet option client This document describes a protocol that more fully supports 3270 devices than do traditional tn3270 practices. [STANDARDS-TRACK] RFC1647 DRAFT STANDARD DRAFT STANDARD RFC2356 Sun's SKIP Firewall Traversal for Mobile IP G. Montenegro V. Gupta June 1998 ASCII 53198 24 Internet Protocol security traffic The Mobile IP specification establishes the mechanisms that enable a mobile host to maintain and use the same IP address as it changes its point of attachment to the network. The mechanisms described in this document allow a mobile node out on a public sector of the internet to negotiate access past a SKIP firewall, and construct a secure channel into its home network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2357 IETF Criteria for Evaluating Reliable Multicast Transport and Application Protocols A. Mankin A. Romanow S. Bradner V. Paxson June 1998 ASCII 24130 11 internet engineering task force rmtp procedures This memo describes the procedures and criteria for reviewing reliable multicast protocols within the Transport Area (TSV) of the IETF. Within today's Internet, important applications exist for a reliable multicast service. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2358 Definitions of Managed Objects for the Ethernet-like Interface Types J. Flick J. Johnson June 1998 ASCII 87891 39 MIB Management Information Base 802.3 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This memo obsoletes RFC 1650 "Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2". This memo extends that specification by including management information useful for the management of 100 Mb/s Ethernet interfaces. [STANDARDS-TRACK] RFC1650 RFC2665 PROPOSED STANDARD PROPOSED STANDARD RFC2359 IMAP4 UIDPLUS extension J. Myers June 1998 ASCII 10862 6 IMAP4UIDPL internet message access protocol disconnected operation The UIDPLUS extension of the Internet Message Access Protocol [IMAP4] provides a set of features intended to reduce the amount of time and resources used by some client operations. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2360 Guide for Internet Standards Writers G. Scott June 1998 ASCII 47280 20 specification multiple implementations This document is a guide for Internet standard writers. It defines those characteristics that make standards coherent, unambiguous, and easy to interpret. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP0022 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2361 WAVE and AVI Codec Registries E. Fleischman June 1998 ASCII 97796 71 multimedia parameter audio video microsoft The purpose of this paper is to establish a mechanism by which codecs registered within Microsoft's WAVE and AVI Registries may be referenced within the IANA Namespace by Internet applications. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2362 Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification D. Estrin D. Farinacci A. Helmy D. Thaler S. Deering M. Handley V. Jacobson C. Liu P. Sharma L. Wei June 1998 ASCII 159833 66 PIM-SM routing message type timers flags This document describes a protocol for efficiently routing to multicast groups that may span wide-area (and inter-domain) internets. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. RFC2117 EXPERIMENTAL EXPERIMENTAL RFC2363 PPP Over FUNI G. Gross M. Kaycee A. Li A. Malis J. Stephens July 1998 ASCII 22576 12 PPP-FUNI point-to-point protocol atm synchronous transfer mode frame user network interface This document describes the use of ATM Frame User Network Interface (FUNI) for framing PPP encapsulated packets. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2364 PPP Over AAL5 G. Gross M. Kaycee A. Li A. Malis J. Stephens July 1998 ASCII 23539 12 PPP-AAL point-to-point protocol link control network-layer authentication compression This document describes the use of ATM Adaptation Layer 5 (AAL5) for framing PPP encapsulated packets. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2365 Administratively Scoped IP Multicast D. Meyer July 1998 ASCII 17770 8 internet protocol IPv4 ipv6 address classes This document defines the "administratively scoped IPv4 multicast space" to be the range 239.0.0.0 to 239.255.255.255. In addition, it describes a simple set of semantics for the implementation of Administratively Scoped IP Multicast. Finally, it provides a mapping between the IPv6 multicast address classes [RFC1884] and IPv4 multicast address classes. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP0023 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2366 Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks C. Chung M. Greene July 1998 ASCII 134312 76 MIB management information base asynchronous transfer mode This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for IP hosts and routers that use a Multicast Address Resolution Server (MARS) to support IP multicast over ATM, as described in 'Support for Multicast over UNI 3.0/3.1 based ATM Networks'. [STANDARDS-TRACK] RFC2417 PROPOSED STANDARD PROPOSED STANDARD RFC2367 PF_KEY Key Management API, Version 2 D. McDonald C. Metz B. Phan July 1998 ASCII 146754 68 IP internet protocol security application programming interface A generic key management API that can be used not only for IP Security but also for other network security services is presented in this document. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2368 The mailto URL scheme P. Hoffman L. Masinter J. Zawinski July 1998 ASCII 16502 10 URLMAILTO uniform resource locator electronic mail addresses This document defines the format of Uniform Resource Locators (URL) for designating electronic mail addresses. [STANDARDS-TRACK] RFC1738 RFC1808 PROPOSED STANDARD PROPOSED STANDARD RFC2369 The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields G. Neufeld J. Baer July 1998 ASCII 30853 15 uniform resource locator email header fields The mailing list command specification header fields are a set of structured fields to be added to email messages sent by email distribution lists. By including these header fields, list servers can make it possible for mail clients to provide automated tools for users to perform list functions. This could take the form of a menu item, push button, or other user interface element. The intent is to simplify the user experience, providing a common interface to the often cryptic and varied mailing list manager commands. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2370 The OSPF Opaque LSA Option R. Coltun July 1998 ASCII 33789 15 OSPF-LSA open-shortest path first ink state advertisement This memo defines enhancements to the OSPF protocol to support a new class of link-state advertisements (LSA) called Opaque LSAs. [STANDARDS-TRACK] RFC3630 RFC2328 PROPOSED STANDARD PROPOSED STANDARD RFC2371 Transaction Internet Protocol Version 3.0 J. Lyon K. Evans J. Klein July 1998 ASCII 71399 31 TIPV3 TIP commit protocol electronic commerce In many applications where different nodes cooperate on some work, there is a need to guarantee that the work happens atomically. That is, each node must reach the same conclusion as to whether the work is to be completed, even in the face of failures. This document proposes a simple, easily-implemented protocol for achieving this end. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2372 Transaction Internet Protocol - Requirements and Supplemental Information K. Evans J. Klein J. Lyon July 1998 ASCII 53699 24 TIP commit protocol electronic commerce This document describes the purpose (usage scenarios), and requirements for the Transaction Internet Protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2373 IP Version 6 Addressing Architecture R. Hinden S. Deering July 1998 ASCII 52526 26 internet protocol unicast anycast multicast node This specification defines the addressing architecture of the IP Version 6 protocol [IPV6]. [STANDARDS-TRACK] RFC1884 RFC3513 PROPOSED STANDARD PROPOSED STANDARD RFC2374 An IPv6 Aggregatable Global Unicast Address Format R. Hinden M. O'Dell S. Deering July 1998 ASCII 25068 12 internet protocol architecture routing This document defines an IPv6 aggregatable global unicast address format for use in the Internet. [STANDARDS-TRACK] RFC2073 RFC3587 HISTORIC PROPOSED STANDARD RFC2375 IPv6 Multicast Address Assignments R. Hinden S. Deering July 1998 ASCII 14356 8 internet protocol multicast scope value This document defines the initial assignment of IPv6 multicast addresses. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2376 XML Media Types E. Whitehead M. Murata July 1998 ASCII 32143 15 extensible markup language web authority hypertext transfer protocol This document proposes two new media subtypes, text/xml and application/xml, for use in exchanging network entities which are conforming Extensible Markup Language (XML). This memo provides information for the Internet community. It does not specify an Internet standard of any kind. RFC3023 INFORMATIONAL INFORMATIONAL RFC2377 Naming Plan for Internet Directory-Enabled Applications A. Grimstad R. Huber S. Sataluri M. Wahl September 1998 ASCII 38274 18 x.500 applications iwps white pages service Application of the conventional X.500 approach to naming has heretofore, in the experience of the authors, proven to be an obstacle to the wide deployment of directory-enabled applications on the Internet. We propose a new directory naming plan that leverages the strengths of the most popular and successful Internet naming schemes for naming objects in a hierarchical directory. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2378 The CCSO Nameserver (Ph) Architecture R. Hedberg P. Pomes September 1998 ASCII 38960 22 computing communications services office database The Ph Nameserver from the Computing and Communications Services Office (CCSO), University of Illinois at Urbana-Champaign has for some time now been used by several organizations as their choice of publicly available database for information about people as well as other things. This document provides a formal definition of the client-server protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2379 RSVP over ATM Implementation Guidelines L. Berger August 1998 ASCII 15174 8 asynchronous transfer mode resource reservation protocol switched circuits This memo presents specific implementation guidelines for running RSVP over ATM switched virtual circuits (SVCs). This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP0024 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2380 RSVP over ATM Implementation Requirements L. Berger August 1998 ASCII 31234 14 resource reservation protocol asynchronous transfer mode switched circuits This memo presents specific implementation requirements for running RSVP over ATM switched virtual circuits (SVCs). It presents requirements that ensure interoperability between multiple implementations and conformance to the RSVP and Integrated Services specifications. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2381 Interoperation of Controlled-Load Service and Guaranteed Service with ATM M. Garrett M. Borden August 1998 ASCII 107299 43 asynchronous transfer mode mapping traffic parameters This document provides guidelines for mapping service classes, and traffic management features and parameters between Internet and ATM technologies. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2382 A Framework for Integrated Services and RSVP over ATM E. Crawley Editor L. Berger S. Berson F. Baker M. Borden J. Krawczyk August 1998 ASCII 73865 30 This document outlines the issues and framework related to providing IP Integrated Services with RSVP over ATM. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2383 ST2+ over ATM Protocol Specification - UNI 3.1 Version M. Suzuki August 1998 ASCII 99889 50 asynchronous transfer mode stream resource reservation This document specifies an ATM-based protocol for communication between ST2+ agents. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2384 POP URL Scheme R. Gellens August 1998 ASCII 13649 8 POP-URL post office protocol uniform resource identifier string encapsulation This memo defines a URL scheme for referencing a POP mailbox. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2385 Protection of BGP Sessions via the TCP MD5 Signature Option A. Heffernan August 1998 ASCII 12315 6 border gateway protocol transmission control message digest algorithm This memo describes a TCP extension to enhance security for BGP. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2386 A Framework for QoS-based Routing in the Internet E. Crawley R. Nair B. Rajagopalan H. Sandick August 1998 ASCII 93459 37 quality of service interdomain intradomain This document describes some of the QoS-based routing issues and requirements, and proposes a framework for QoS-based routing in the Internet. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2387 The MIME Multipart/Related Content-type E. Levinson August 1998 ASCII 18864 10 MIME-RELAT multipurpose internet mail extensions body parts media-type This document defines the Multipart/Related content-type and provides examples of its use. [STANDARDS-TRACK] RFC2112 PROPOSED STANDARD PROPOSED STANDARD RFC2388 Returning Values from Forms: multipart/form-data L. Masinter August 1998 ASCII 16531 9 media-type multipurpose internet mail extensions This specification defines an Internet Media Type, multipart/form-data, which can be used by a wide variety of applications and transported by a wide variety of protocols as a way of returning a set of values as the result of a user filling out a form. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2389 Feature negotiation mechanism for the File Transfer Protocol P. Hethmon R. Elz August 1998 ASCII 18536 9 FTP catalogue This document provides a mechanism by which clients of the FTP protocol can discover which new features are supported by a particular FTP server. [STANDARDS-TRACK] RFC0959 PROPOSED STANDARD PROPOSED STANDARD RFC2390 Inverse Address Resolution Protocol T. Bradley C. Brown A. Malis September 1998 ASCII 20849 10 IARP iarp hardware frame relay This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK] RFC1293 DRAFT STANDARD DRAFT STANDARD RFC2391 Load Sharing using IP Network Address Translation (LSNAT) P. Srisuresh D. Gan August 1998 ASCII 44884 18 internet protocol datagram server In this document, we extend the use of NATs to offer Load share feature, where session load can be distributed across a pool of servers, instead of directing to a single server. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2392 Content-ID and Message-ID Uniform Resource Locators E. Levinson August 1998 ASCII 11141 6 CIDMID-URL Hyper Text Markup Language URL MIME The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow references to messages and the body parts of messages. For example, within a single multipart message, one HTML body part might include embedded references to other parts of the same message. [STANDARDS- TRACK] RFC2111 PROPOSED STANDARD PROPOSED STANDARD RFC2393 IP Payload Compression Protocol (IPComp) A. Shacham R. Monsour R. Pereira M. Thomas December 1998 ASCII 20757 10 IPCOMP internet protocol datagram lossless This document describes a protocol intended to provide lossless compression for Internet Protocol datagrams in an Internet environment. [STANDARDS-TRACK] RFC3173 PROPOSED STANDARD PROPOSED STANDARD RFC2394 IP Payload Compression Using DEFLATE R. Pereira December 1998 ASCII 11053 6 internet protocol algorithm datagram format This document describes a compression method based on the DEFLATE compression algorithm. This document defines the application of the DEFLATE algorithm to the IP Payload Compression Protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2395 IP Payload Compression Using LZS R. Friend R. Monsour December 1998 ASCII 14882 9 internet protocol algorithm datagram lossless This document describes a compression method based on the LZS compression algorithm. This document defines the application of the LZS algorithm to the IP Payload Compression Protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. INFORMATIONAL INFORMATIONAL RFC2396 Uniform Resource Identifiers (URI): Generic Syntax T. Berners-Lee R. Fielding L. Masinter August 1998 ASCII 83639 40 URI-GEN characters string absolute relative This document defines a grammar that is a superset of all valid URI, such that an implementation can parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier type. [STANDARDS-TRACK] RFC3986 RFC1808 RFC1738 RFC2732 DRAFT STANDARD DRAFT STANDARD RFC2397 The "data" URL scheme L. Masinter August 1998 ASCII 9514 5 DATA-URL uniform resource identifiers media type A new URL scheme, "data", is defined. It allows inclusion of small data items as "immediate" data, as if it had been included externally. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2398 Some Testing Tools for TCP Implementors S. Parker C. Schmechel August 1998 ASCII 24107 15 transmission control protocol catalogue This document lists only tools which can evaluate one or more TCP implementations, or which can privde some specific results which describe or evaluate the TCP being tested. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. FYI0033 INFORMATIONAL INFORMATIONAL RFC2399 Request for Comments Summary A. Ramos January 1999 ASCII 45853 23 INFORMATIONAL INFORMATIONAL RFC2400 Internet Official Protocol Standards J. Postel J. Reynolds September 1998 ASCII 110969 47 IAB official protocol standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). This memo is an Internet Standard. [STANDARDS-TRACK] RFC2300 RFC2500 HISTORIC STANDARD RFC2401 Security Architecture for the Internet Protocol S. Kent R. Atkinson November 1998 ASCII 168162 66 IPSEC ipsec authentication encapsulation IP IPv4 IPv6 IP-layer This memo specifies the base architecture for IPsec compliant systems. [STANDARDS-TRACK] RFC1825 RFC3168 PROPOSED STANDARD PROPOSED STANDARD RFC2402 IP Authentication Header S. Kent R. Atkinson November 1998 ASCII 52831 22 IP-AUTH ipsec Internet Protocol AH security IPv4 IPv6 The IP Authentication Header (AH) is used to provide connectionless integrity and data origin authentication for IP datagrams (hereafter referred to as just "authentication"), and to provide protection against replays. [STANDARDS-TRACK] RFC1826 PROPOSED STANDARD PROPOSED STANDARD RFC2403 The Use of HMAC-MD5-96 within ESP and AH C. Madson R. Glenn November 1998 ASCII 13578 7 ipsec authentication mechanism header security architecture This memo describes the use of the HMAC algorithm in conjunction with the MD5 algorithm as an authentication mechanism within the revised IPSEC Encapsulating Security Payload and the revised IPSEC Authentication Header. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2404 The Use of HMAC-SHA-1-96 within ESP and AH C. Madson R. Glenn November 1998 ASCII 13089 7 ipsec authentication mechanism header security architecture payload This memo describes the use of the HMAC algorithm in conjunction with the SHA-1 algorithm as an authentication mechanism within the revised IPSEC Encapsulating Security Payload and the revised IPSEC Authentication Header. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2405 The ESP DES-CBC Cipher Algorithm With Explicit IV C. Madson N. Doraswamy November 1998 ASCII 20208 10 ESPDES-CBC ipsec payload security architecture encryption This document describes the use of the DES Cipher algorithm in Cipher Block Chaining Mode, with an explicit IV, as a confidentiality mechanism within the context of the IPSec Encapsulating Security Payload (ESP). [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2406 IP Encapsulating Security Payload (ESP) S. Kent R. Atkinson November 1998 ASCII 54202 22 ESP ipsec internet protocol encapsulating security ipv4 ipv6 The Encapsulating Security Payload (ESP) header is designed to provide a mix of security services in IPv4 and IPv6. [STANDARDS-TRACK] RFC1827 PROPOSED STANDARD PROPOSED STANDARD RFC2407 The Internet IP Security Domain of Interpretation for ISAKMP D. Piper November 1998 ASCII 67878 32 ISAKMPSEC ipsec internet protocol security association key management This document defines the Internet IP Security DOI (IPSEC DOI), which instantiates ISAKMP for use with IP when IP uses ISAKMP to negotiate security associations. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2408 Internet Security Association and Key Management Protocol (ISAKMP) D. Maughan M. Schertler M. Schneider J. Turner November 1998 ASCII 209175 86 ISAKMP ipsec cryptography authentication This memo describes a protocol utilizing security concepts necessary for establishing Security Associations (SA) and cryptographic keys in an Internet environment. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2409 The Internet Key Exchange (IKE) D. Harkins D. Carrel November 1998 ASCII 94949 41 IKE ipsec oakley authentication isakmp internet security key management This memo describes a hybrid protocol. The purpose is to negotiate, and provide authenticated keying material for, security associations in a protected manner. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2410 The NULL Encryption Algorithm and Its Use With IPsec R. Glenn S. Kent November 1998 ASCII 11239 6 ipsec internet protocol security esp encapsulating payload This memo defines the NULL encryption algorithm and its use with the IPsec Encapsulating Security Payload (ESP). [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2411 IP Security Document Roadmap R. Thayer N. Doraswamy R. Glenn November 1998 ASCII 22983 11 ipsec internet protocol privacy authentication This document is intended to provide guidelines for the development of collateral specifications describing the use of new encryption and authentication algorithms with the ESP protocol, described in and new authentication algorithms used with the AH protocol. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2412 The OAKLEY Key Determination Protocol H. Orman November 1998 ASCII 118649 55 ipsec authentication crytographic secure scalable This document describes a protocol, named OAKLEY, by which two authenticated parties can agree on secure and secret keying material. The basic mechanism is the Diffie-Hellman key exchange algorithm. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2413 Dublin Core Metadata for Resource Discovery S. Weibel J. Kunze C. Lagoze M. Wolf September 1998 ASCII 15501 8 workshop electronic librarians network This is the first of a set of Informational RFCs describing the Dublin Core. Its purpose is to introduce the Dublin Core and to describe the consensus reached on the semantics of each of the 15 elements. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2414 Increasing TCP's Initial Window M. Allman S. Floyd C. Partridge September 1998 ASCII 32019 14 TCP-WIN transmission control protocol This document specifies an increase in the permitted initial window for TCP from one segment to roughly 4K bytes. This memo defines an Experimental Protocol for the Internet community. RFC3390 EXPERIMENTAL EXPERIMENTAL RFC2415 Simulation Studies of Increased Initial TCP Window Size K. Poduri K. Nichols September 1998 ASCII 24205 11 transmission control protocol file transfer This document covers some simulation studies of the effects of increasing the initial window size of TCP. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2416 When TCP Starts Up With Four Packets Into Only Three Buffers T. Shepard C. Partridge September 1998 ASCII 12663 7 transmission control protocol performance This memo is to document a simple experiment. The experiment showed that in the case of a TCP receiver behind a 9600 bps modem link at the edge of a fast Internet where there are only 3 buffers before the modem (and the fourth packet of a four-packet start will surely be dropped), no significant degradation in performance is experienced by a TCP sending with a four-packet start when compared with a normal slow start (which starts with just one packet). This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2417 Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks C. Chung M. Greene September 1998 ASCII 134862 76 MIB management information base asynchronous transfer mode This memo specifies a MIB module in a manner that is both compliant to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 definitions. [STANDARDS-TRACK] RFC2366 PROPOSED STANDARD PROPOSED STANDARD RFC2418 IETF Working Group Guidelines and Procedures S. Bradner September 1998 ASCII 62857 26 BCP WG escape clause procedures This document describes the guidelines and procedures for formation and operation of IETF working groups. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC1603 RFC3934 BCP0025 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2419 The PPP DES Encryption Protocol, Version 2 (DESE-bis) K. Sklower G. Meyer September 1998 ASCII 24414 12 DESE-bis point-to-point protocol ecp control This document provides specific details for the use of the DES standard for encrypting PPP encapsulated packets. [STANDARDS-TRACK] RFC1969 PROPOSED STANDARD PROPOSED STANDARD RFC2420 The PPP Triple-DES Encryption Protocol (3DESE) H. Kummert September 1998 ASCII 16729 8 3DESE point-to-point protocol ecp control This document provides specific details for the use of the Triple-DES standard (3DES) for encrypting PPP encapsulated packets. [STANDARDS- TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2421 Voice Profile for Internet Mail - version 2 G. Vaudreuil G. Parsons September 1998 ASCII 123663 56 MIME-VP2 vpim messaging This document profiles Internet mail for voice messaging. [STANDARDS-TRACK] RFC1911 RFC3801 PROPOSED STANDARD PROPOSED STANDARD RFC2422 Toll Quality Voice - 32 kbit/s ADPCM MIME Sub-type Registration G. Vaudreuil G. Parsons September 1998 ASCII 10157 6 MIME-ADPCM multipurpose internet mail extensions audio This document describes the registration of the MIME sub-type audio/32KADPCM for toll quality audio. [STANDARDS-TRACK] RFC1911 RFC3802 PROPOSED STANDARD PROPOSED STANDARD RFC2423 VPIM Voice Message MIME Sub-type Registration G. Vaudreuil G. Parsons September 1998 ASCII 10729 6 MIME-VPIM multipurpose internet mail extensions profiles This document describes the registration of the MIME sub-type multipart/voice-message for use with the Voice Profile for Internet Mail (VPIM). [STANDARDS-TRACK] RFC1911 RFC3801 PROPOSED STANDARD PROPOSED STANDARD RFC2424 Content Duration MIME Header Definition G. Vaudreuil G. Parsons September 1998 ASCII 7116 4 CONT-DUR multipurpose internet mail extensions time media This document describes the MIME header Content-Duration that is intended for use with any timed media content (typically audio/* or video/*). [STANDARDS-TRACK] RFC3803 PROPOSED STANDARD PROPOSED STANDARD RFC2425 A MIME Content-Type for Directory Information T. Howes M. Smith F. Dawson September 1998 ASCII 64478 33 TXT-DIR multipurpose internet mail extensions profiles This document defines a MIME Content-Type for holding directory information. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2426 vCard MIME Directory Profile F. Dawson T. Howes September 1998 ASCII 74646 42 MIME-VCARD multipurpose internet mail extensions white-pages electronic business card This memo defines the profile of the MIME Content-Type for directory information for a white-pages person object, based on a vCard electronic business card. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2427 Multiprotocol Interconnect over Frame Relay C. Brown A. Malis September 1998 ASCII 74671 34 IP-FR standard standards IP over 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] RFC1490 RFC1294 STD0055 STANDARD STANDARD RFC2428 FTP Extensions for IPv6 and NATs M. Allman S. Ostermann C. Metz September 1998 ASCII 16028 8 file transfer protocol internet network address translators This paper specifies extensions to FTP that will allow the protocol to work over IPv4 and IPv6. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2429 RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+) C. Bormann L. Cline G. Deisher T. Gardos C. Maciocco D. Newell J. Ott G. Sullivan S. Wenger C. Zhu October 1998 ASCII 43166 17 real time transport protocol multicast unicast This document specifies an RTP payload header format applicable to the transmission of video streams generated based on the 1998 version of ITU-T Recommendation H.263. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2430 A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE) T. Li Y. Rekhter October 1998 ASCII 40148 16 isp internet service provider packet flow multiprotocol label switching mpls resource reservation protocol rsvp This document describes the Provider Architecture for Differentiated Services and Traffic Engineering (PASTE) for Internet Service Providers (ISPs). This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2431 RTP Payload Format for BT.656 Video Encoding D. Tynan October 1998 ASCII 22323 10 real time transport protocol itu multicast unicast This document specifies the RTP payload format for encapsulating ITU Recommendation BT.656-3 video streams in the Real-Time Transport Protocol (RTP). [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2432 Terminology for IP Multicast Benchmarking K. Dubray October 1998 ASCII 29758 16 internet protocol network forwarding devices The purpose of this document is to define terminology specific to the benchmarking of multicast IP forwarding devices. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2433 Microsoft PPP CHAP Extensions G. Zorn S. Cobb October 1998 ASCII 34502 20 point to point protocol challenge handshake authentication The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol and a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2434 Guidelines for Writing an IANA Considerations Section in RFCs T. Narten H. Alvestrand October 1998 ASCII 25092 11 internet assigned numbers authority values implementations This document discusses issues that should be considered in formulating a policy for assigning values to a name space and provides guidelines to document authors on the specific text that must be included in documents that place demands on the IANA. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC3692 BCP0026 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2435 RTP Payload Format for JPEG-compressed Video L. Berc W. Fenner R. Frederick S. McCanne P. Stewart October 1998 ASCII 54173 27 Real Time Transport Protocol Joint Photographic Experts Group This memo describes the RTP payload format for JPEG video streams. [STANDARDS-TRACK] RFC2035 PROPOSED STANDARD PROPOSED STANDARD RFC2436 Collaboration between ISOC/IETF and ITU-T R. Brett S. Bradner G. Parsons October 1998 ASCII 31154 14 internet society engineering task force This document describes the collaboration process between the ITU-T and ISOC/IETF. This memo provides information for the Internet community. RFC3356 INFORMATIONAL INFORMATIONAL RFC2437 PKCS #1: RSA Cryptography Specifications Version 2.0 B. Kaliski J. Staddon October 1998 ASCII 73529 39 data public key cryptosystem This memo is the successor to RFC 2313. This document provides recommendations for the implementation of public-key cryptography based on the RSA algorithm. This memo provides information for the Internet community. RFC2313 RFC3447 INFORMATIONAL INFORMATIONAL RFC2438 Advancement of MIB specifications on the IETF Standards Track M. O'Dell H. Alvestrand B. Wijnen S. Bradner October 1998 ASCII 13633 7 management information base internet engineering task force This document specifies the process which the IESG will use to determine if a MIB specification document meets these requirements. It also discusses the rationale for this process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP0027 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2439 BGP Route Flap Damping C. Villamizar R. Chandra R. Govindan November 1998 ASCII 86376 37 Border Gateway Protocol IDRP Internet-Domain Routing A usage of the BGP routing protocol is described which is capable of reducing the routing traffic passed on to routing peers and therefore the load on these peers without adversely affecting route convergence time for relatively stable routes. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2440 OpenPGP Message Format J. Callas L. Donnerhacke H. Finney R. Thayer November 1998 ASCII 141371 65 pretty good privacy encryption authentication This document is maintained in order to publish all necessary information needed to develop interoperable applications based on the OpenPGP format. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2441 Working with Jon, Tribute delivered at UCLA, October 30, 1998 D. Cohen November 1998 ASCII 11992 6 Jonathan B Postel This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2442 The Batch SMTP Media Type N. Freed D. Newman J. Belissent M. Hoy November 1998 ASCII 18384 9 simple transfer protocol mime multipurpose internet mail extensions tunneling This document defines a MIME content type suitable for tunneling an ESMTP transaction through any MIME-capable transport. This memo provides information for the Internet community INFORMATIONAL INFORMATIONAL RFC2443 A Distributed MARS Service Using SCSP J. Luciani A. Gallo November 1998 ASCII 41451 18 MARS-SCSP server cache syncronization protocol atm asynchronous transfer mode This document describes a method for distributing a MARS service within a LIS. This method uses the Server Cache Synchronization Protocol (SCSP) to synchronize the MARS Server databases within a LIS. When SCSP is used to synchronize the caches of MARS Servers in a LIS, the LIS defines the boundary of an SCSP Server Group (SG). [STANDARDS-TRACK] EXPERIMENTAL EXPERIMENTAL RFC2444 The One-Time-Password SASL Mechanism C. Newman October 1998 ASCII 13408 7 OTP-SASL otp simple authentication security layer OTP provides a useful authentication mechanism for situations where there is limited client or server trust. Currently, OTP is added to protocols in an ad-hoc fashion with heuristic parsing. This specification defines an OTP SASL mechanism so it can be easily and formally integrated into many application protocols. [STANDARDS-TRACK] RFC2222 PROPOSED STANDARD PROPOSED STANDARD RFC2445 Internet Calendaring and Scheduling Core Object Specification (iCalendar) F. Dawson D. Stenerson November 1998 ASCII 291838 148 ICALENDAR internet interoperable mime multipurpose mail extensions This memo has been defined to provide the definition of a common format for openly exchanging calendaring and scheduling information across the Internet. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2446 iCalendar Transport-Independent Interoperability Protocol (iTIP) Scheduling Events, BusyTime, To-dos and Journal Entries S. Silverberg S. Mansour F. Dawson R. Hopson November 1998 ASCII 225964 109 ITIP internet systems interoperability This document specifies how calendaring systems use iCalendar objects to interoperate with other calendar systems. It does so in a general way so as to allow multiple methods of communication between systems. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2447 iCalendar Message-Based Interoperability Protocol (iMIP) F. Dawson S. Mansour S. Silverberg November 1998 ASCII 33480 18 IMIP internet electronic mail transport This document specifies a binding from the iCalendar Transport- independent Interoperability Protocol (iTIP) to Internet email-based transports. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2448 AT&T's Error Resilient Video Transmission Technique M. Civanlar G. Cash B. Haskell November 1998 ASCII 14655 7 packets network bitstreams This document describes a set of techniques for packet loss resilient transmission of compressed video bitstreams based on reliable delivery of their vital information-carrying segments. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2449 POP3 Extension Mechanism R. Gellens C. Newman L. Lundblade November 1998 ASCII 36017 19 POP3-EXT post office protocol server This memo updates RFC 1939 to define a mechanism to announce support for optional commands, extensions, and unconditional server behavior. [STANDARDS-TRACK] RFC1939 PROPOSED STANDARD PROPOSED STANDARD RFC2450 Proposed TLA and NLA Assignment Rule R. Hinden December 1998 ASCII 24486 11 top-level aggregation identifiers next-level ipv6 internet protocols addresses This document proposes rules for Top-Level Aggregation Identifiers (TLA ID) and Next-Level Aggregation Identifiers (NLA ID). This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2451 The ESP CBC-Mode Cipher Algorithms R. Pereira R. Adams November 1998 ASCII 26400 14 ipsec encapsulating security payload This document describes how to use CBC-mode cipher algorithms with the IPSec ESP (Encapsulating Security Payload) Protocol. It not only clearly states how to use certain cipher algorithms, but also how to use all CBC-mode cipher algorithms. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2452 IP Version 6 Management Information Base for the Transmission Control Protocol M. Daniele December 1998 ASCII 19066 10 mib internet protocol tcp ipv6 This document is one in the series of documents that define various MIB objects for IPv6. Specifically, this document is the MIB module which defines managed objects for implementations of the Transmission Control Protocol (TCP) over IP Version 6 (IPv6). [STANDARDS-TRACK] RFC4022 PROPOSED STANDARD PROPOSED STANDARD RFC2453 RIP Version 2 G. Malkin November 1998 ASCII 98462 39 RIP2 RIP-2 This document specifies an extension of the Routing Information Protocol (RIP) to expand the amount of useful information carried in RIP messages and to add a measure of security. [STANDARDS-TRACK] RFC1723 STD0056 STANDARD STANDARD RFC2454 IP Version 6 Management Information Base for the User Datagram Protocol M. Daniele December 1998 ASCII 15862 9 mib internet protocol udp ipv6 This document is one in the series of documents that define various MIB objects for IPv6. Specifically, this document is the MIB module which defines managed objects for implementations of the User Datagram Protocol (UDP) over IP Version 6 (IPv6). [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2455 Definitions of Managed Objects for APPN B. Clouston B. Moore November 1998 ASCII 251061 140 APPN-MIB mib management information base advanced peer-to-peer networking 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] RFC2155 PROPOSED STANDARD PROPOSED STANDARD RFC2456 Definitions of Managed Objects for APPN TRAPS B. Clouston B. Moore November 1998 ASCII 44023 21 mib management information base advanced peer-to-peer networking 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 receiving notifications from network devices with APPN (Advanced Peer-to-Peer Network) and DLUR (Dependent LU Requester) capabilities. This memo identifies notifications for the APPN and DLUR architecture. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2457 Definitions of Managed Objects for Extended Border Node B. Clouston B. Moore November 1998 ASCII 54380 28 EBN-MIB mib management information base ebn 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 Network) EBN (Extended Border Node) capabilities. This memo identifies managed objects for the EBN architecture. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2458 Toward the PSTN/Internet Inter-Networking--Pre-PINT Implementations H. Lu M. Krishnaswamy L. Conroy S. Bellovin F. Burg A. DeSimone K. Tewani P. Davidson H. Schulzrinne K. Vishwanathan November 1998 ASCII 139100 60 This document contains the information relevant to the development of the inter-networking interfaces underway in the Public Switched Telephone Network (PSTN)/Internet Inter-Networking (PINT) Working Group. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2459 Internet X.509 Public Key Infrastructure Certificate and CRL Profile R. Housley W. Ford W. Polk D. Solo January 1999 ASCII 278438 129 digital signatures encryption authentication This memo profiles the X.509 v3 certificate and X.509 v2 CRL for use in the Internet. [STANDARDS-TRACK] RFC3280 PROPOSED STANDARD PROPOSED STANDARD RFC2460 Internet Protocol, Version 6 (IPv6) Specification S. Deering R. Hinden December 1998 ASCII 85490 39 IPV6 internet protocol next generation ipng This document specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng. [STANDARDS-TRACK] RFC1883 DRAFT STANDARD DRAFT STANDARD RFC2461 Neighbor Discovery for IP Version 6 (IPv6) T. Narten E. Nordmark W. Simpson December 1998 ASCII 222516 93 IPV6-ND internet protocol link-layer This document specifies the Neighbor Discovery protocol for IP Version 6. [STANDARDS-TRACK] RFC1970 DRAFT STANDARD DRAFT STANDARD RFC2462 IPv6 Stateless Address Autoconfiguration S. Thomson T. Narten December 1998 ASCII 61210 25 IPV6-AUTO internet protocol host link-local This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. [STANDARDS-TRACK] RFC1971 DRAFT STANDARD DRAFT STANDARD RFC2463 Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification A. Conta S. Deering December 1998 ASCII 34190 18 ICMPv6 internet protocol link-local autoconfigured addresses This document specifies a set of Internet Control Message Protocol (ICMP) messages for use with version 6 of the Internet Protocol (IPv6). [STANDARDS-TRACK] RFC1885 DRAFT STANDARD DRAFT STANDARD RFC2464 Transmission of IPv6 Packets over Ethernet Networks M. Crawford December 1998 ASCII 12725 7 internet protocol link-local autoconfigured addresses This document specifies the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on Ethernet networks. It also specifies the content of the Source/Target Link-layer Address option used in Router Solicitation, Router Advertisement, Neighbor Solicitation, Neighbor Advertisement and Redirect messages when those messages are transmitted on an Ethernet. [STANDARDS-TRACK] RFC1972 PROPOSED STANDARD PROPOSED STANDARD RFC2465 Management Information Base for IP Version 6: Textual Conventions and General Group D. Haskin S. Onishi December 1998 ASCII 77339 38 mib internet protocol ipv6 This document is one in the series of documents that provide MIB definitions for for IP Version 6. Specifically, the IPv6 MIB textual conventions as well as the IPv6 MIB General group is defined in this document. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2466 Management Information Base for IP Version 6: ICMPv6 Group D. Haskin S. Onishi December 1998 ASCII 27547 16 ICMPv6-MIB mib internet protocol ipv6 This document is one in the series of documents that define various MIB object groups for IPv6. Specifically, the ICMPv6 group is defined in this document. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2467 Transmission of IPv6 Packets over FDDI Networks M. Crawford December 1998 ASCII 16028 9 internet protocol link-local addresses autoconfiguration This document specifies the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on FDDI networks. [STANDARDS- TRACK] RFC2019 PROPOSED STANDARD PROPOSED STANDARD RFC2468 I REMEMBER IANA V. Cerf October 1998 ASCII 8543 4 jonathan b postel A long time ago, in a network, far far away, a great adventure took place!. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2469 A Caution On The Canonical Ordering Of Link-Layer Addresses T. Narten C. Burton December 1998 ASCII 9948 5 address resolution protocol data fields Protocols such as ARP and Neighbor Discovery have data fields that contain link-layer addresses. In order to interoperate properly, a sender setting such a field must insure that the receiver extracts those bits and interprets them correctly. In most cases, such fields must be in "canonical form". Unfortunately, not all LAN adaptors are consistent in their use of canonical form, and implementations may need to explicitly bit swap individual bytes in order to obtain the correct format. This document provides information to implementors to help them avoid the pitfall of using non-canonical forms when canonical forms are required. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2470 Transmission of IPv6 Packets over Token Ring Networks M. Crawford T. Narten S. Thomas December 1998 ASCII 21677 11 internet protocol frame format link-local addresses This memo specifies the MTU and frame format for transmission of IPv6 packets on Token Ring networks. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2471 IPv6 Testing Address Allocation R. Hinden R. Fink J. Postel (deceased) December 1998 ASCII 8031 5 internet protocol protocotype software architecture This document describes an allocation plan for IPv6 addresses to be used in testing IPv6 prototype software. This memo defines an Experimental Protocol for the Internet community. RFC1897 RFC3701 HISTORIC EXPERIMENTAL RFC2472 IP Version 6 over PPP D. Haskin E. Allen December 1998 ASCII 29696 14 IPv6-PPP internet protocol point-to-point ipv6 This document defines the method for transmission of IP Version 6 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. [STANDARDS- TRACK] ietf-snmpv3-mpc-05 RFC2023 PROPOSED STANDARD PROPOSED STANDARD RFC2473 Generic Packet Tunneling in IPv6 Specification A. Conta S. Deering December 1998 ASCII 77956 36 internet protocol encapsulation This document defines the model and generic mechanisms for IPv6 encapsulation of Internet packets, such as IPv6 and IPv4. [STANDARDS- TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2474 Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers K. Nichols S. Blake F. Baker D. Black December 1998 ASCII 50576 20 internet protocol network nodes This document defines the IP header field, called the DS (for differentiated services) field. [STANDARDS-TRACK] RFC1455 RFC1349 RFC3168 RFC3260 PROPOSED STANDARD PROPOSED STANDARD RFC2475 An Architecture for Differentiated Service S. Blake D. Black M. Carlson E. Davies Z. Wang W. Weiss December 1998 ASCII 94786 36 DIFFSRV] scalability IP internet protocol This document defines an architecture for implementing scalable service differentiation in the Internet. This memo provides information for the Internet community. RFC3260 INFORMATIONAL PROPOSED STANDARD RFC2476 Message Submission R. Gellens J. Klensin December 1998 ASCII 30050 15 smtp simple mail transfer protocol user agent This memo describes a low cost, deterministic means for messages to be identified as submissions, and specifies what actions are to be taken by a submission server. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2477 Criteria for Evaluating Roaming Protocols B. Aboba G. Zorn January 1999 ASCII 23530 12 ISP internet service providers operations This document describes requirements for the provisioning of "roaming capability" for dialup Internet users. "Roaming capability" is defined as the ability to use multiple Internet service providers (ISPs), while maintaining a formal, customer-vendor relationship with only one. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2478 The Simple and Protected GSS-API Negotiation Mechanism E. Baize D. Pinkas December 1998 ASCII 35581 18 generic service application security program interface This document specifies a Security Negotiation Mechanism for the Generic Security Service Application Program Interface (GSS-API). [STANDARDS- TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2479 Independent Data Unit Protection Generic Security Service Application Program Interface (IDUP-GSS-API) C. Adams December 1998 ASCII 156070 70 data unit authentication The IDUP-GSS-API extends the GSS-API for applications requiring protection of a generic data unit (such as a file or message) in a way which is independent of the protection of any other data unit and independent of any concurrent contact with designated "receivers" of the data unit. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2480 Gateways and MIME Security Multiparts N. Freed January 1999 ASCII 11751 6 mutltipurpose internet mail extensions This document examines the problems associated with use of MIME security multiparts and gateways to non-MIME environments. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2481 A Proposal to add Explicit Congestion Notification (ECN) to IP K. Ramakrishnan S. Floyd January 1999 ASCII 64559 25 ECN-IP internet protocol tcp transmission control transport This note describes a proposed addition of ECN (Explicit Congestion Notification) to IP. This memo defines an Experimental Protocol for the Internet community. RFC3168 EXPERIMENTAL EXPERIMENTAL RFC2482 Language Tagging in Unicode Plain Text K. Whistler G. Adams January 1999 ASCII 27800 14 characters strings ASCII This document proposed a mechanism for language tagging in plain text. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2483 URI Resolution Services Necessary for URN Resolution M. Mealling R. Daniel January 1999 ASCII 30518 16 uniform resource identifier names locators characteristics Retrieving the resource identified by a Uniform Resource Identifier (URI) is only one of the operations that can be performed on a URI. One might also ask for and get a list of other identifiers that are aliases for the original URI or a bibliographic description of the resource the URI denotes, for example. This applies to both Uniform Resource Names (URNs) and Uniform Resource Locators (URLs). Uniform Resource Characteristics (URCs) are discussed in this document but only as descriptions of resources rather than identifiers. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL EXPERIMENTAL RFC2484 PPP LCP Internationalization Configuration Option G. Zorn January 1999 ASCII 8330 5 point-to-point protocol link control authentication The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP also defines an extensible Link Control Protocol (LCP), which allows negotiation of an Authentication Protocol for authenticating its peer before allowing Network Layer protocols to transmit over the link. [STANDARDS-TRACK] RFC2284 RFC1994 RFC1570 PROPOSED STANDARD PROPOSED STANDARD RFC2485 DHCP Option for The Open Group's User Authentication Protocol S. Drach January 1999 ASCII 7205 4 dynamic host configuration UAP This document defines a DHCP option that contains a list of pointers to User Authentication Protocol servers that provide user authentication services for clients that conform to The Open Group Network Computing Client Technical Standard. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2486 The Network Access Identifier B. Aboba M. Beadles January 1999 ASCII 14261 8 NAI NAI tunneling roaming This document proposes syntax for the Network Access Identifier (NAI), the userID submitted by the client during PPP authentication. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2487 SMTP Service Extension for Secure SMTP over TLS P. Hoffman January 1999 ASCII 15120 8 simple mail transfer protocol transport layer security ssl This document describes an extension to the SMTP service that allows an SMTP server and client to use transport-layer security to provide private, authenticated communication over the Internet. This gives SMTP agents the ability to protect some or all of their communications from eavesdroppers and attackers. [STANDARDS-TRACK] RFC3207 PROPOSED STANDARD PROPOSED STANDARD RFC2488 Enhancing TCP Over Satellite Channels using Standard Mechanisms M. Allman D. Glover L. Sanchez January 1999 ASCII 47857 19 transmission control protocol network The Transmission Control Protocol (TCP) provides reliable delivery of data across any network path, including network paths containing satellite channels. While TCP works over satellite channels there are several IETF standardized mechanisms that enable TCP to more effectively utilize the available capacity of the network path. This document outlines some of these TCP mitigations. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP0028 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2489 Procedure for Defining New DHCP Options R. Droms January 1999 ASCII 10484 5 mutipurpose internet mail extensions This document describes the procedure for defining new DHCP options. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC2939 BCP0029 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2490 A Simulation Model for IP Multicast with RSVP M. Pullen R. Malghan L. Lavu G. Duan J. Ma H. Nah January 1999 ASCII 74936 31 PS 1956365 PDF 135368 internet protocol resource reservation ipv4 This document describes a detailed model of IPv4 multicast with RSVP that has been developed using the OPNET simulation package, with protocol procedures defined in the C language. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2491 IPv6 over Non-Broadcast Multiple Access (NBMA) networks G. Armitage P. Schulter M. Jork G. Harter January 1999 ASCII 100782 44 IPv6-NBMA internet protocol routing host This document describes a general architecture for IPv6 over NBMA networks. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2492 IPv6 over ATM Networks G. Armitage P. Schulter M. Jork January 1999 ASCII 21199 12 IPv6ATMNET internet protocol asynchronous transfer mode host This document is a companion to the ION working group's architecture document, "IPv6 over Non Broadcast Multiple Access (NBMA) networks". It provides specific details on how to apply the IPv6 over NBMA architecture to ATM networks. This architecture allows conventional host-side operation of the IPv6 Neighbor Discovery protocol, while also supporting the establishment of 'shortcut' ATM forwarding paths (when using SVCs). Operation over administratively configured Point to Point PVCs is also supported. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2493 Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals K. Tesink Editor January 1999 ASCII 18749 9 management information base data This document defines a set of Textual Conventions for MIB modules which make use of performance history data based on 15 minute intervals. [STANDARDS-TRACK] RFC3593 PROPOSED STANDARD PROPOSED STANDARD RFC2494 Definitions of Managed Objects for the DS0 and DS0 Bundle Interface Type D. Fowler Editor January 1999 ASCII 47208 25 management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing DS0 and DS0 Bundle interfaces. This document is a companion document with Definitions of Managed Objects for the DS1/E1/DS2/E2 (RFC 2495), DS3/E3 (RFC 2496), and the work in progress, SONET/SDH Interface Types. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2495 Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types D. Fowler Editor January 1999 ASCII 155560 75 management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing DS1, E1, DS2 and E2 interfaces. This document is a companion document with Definitions of Managed Objects for the DS0 (RFC 2494), DS3/E3 (RFC 2496), and the work in progress, SONET/SDH Interface Types. [STANDARDS-TRACK] RFC1406 RFC3895 PROPOSED STANDARD PROPOSED STANDARD RFC2496 Definitions of Managed Object for the DS3/E3 Interface Type D. Fowler Editor January 1999 ASCII 124251 60 DS3-E3-MIB management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing DS3 and E3 interfaces. This document is a companion document with Definitions of Managed Objects for the DS0 (RFC 2494), DS1/E1/DS2/E2 (RFC 2495), and the work in progress SONET/SDH Interface Types. [STANDARDS-TRACK] RFC1407 RFC3896 PROPOSED STANDARD PROPOSED STANDARD RFC2497 Transmission of IPv6 Packets over ARCnet Networks I. Souvatzis January 1999 ASCII 10304 6 internet protocol frame format link-local This memo specifies a frame format for transmission of IPv6 packets and the method of forming IPv6 link-local and statelessly autoconfigured addresses on ARCnet networks. It also specifies the content of the Source/Target Link-layer Address option used by the Router Solicitation, Router Advertisement, Neighbor Solicitation, Neighbor Advertisement and Redirect messages described in, when those messages are transmitted on an ARCnet. [STANDARDS-TRACK] souvatzis-ipv6-arcnet-05 RFC1201 PROPOSED STANDARD PROPOSED STANDARD RFC2498 IPPM Metrics for Measuring Connectivity J. Mahdavi V. Paxson January 1999 ASCII 17869 10 IPPM-MET internet protocol performance metrics This memo defines a series of metrics for connectivity between a pair of Internet hosts. It builds on notions introduced and discussed in RFC 2330, the IPPM framework document. This memo defines an Experimental Protocol for the Internet community. RFC2678 EXPERIMENTAL EXPERIMENTAL RFC2499 Request for Comments Summary A. Ramos July 1999 ASCII 43431 22 INFORMATIONAL INFORMATIONAL RFC2500 Internet Official Protocol Standards J. Reynolds R. Braden June 1999 ASCII 78845 28 IAB official protocol standards This memo summarizes the status of Internet protocols and specifications. [STANDARDS-TRACK] RFC2400 RFC2600 HISTORIC STANDARD RFC2501 Mobile Ad hoc Networking (MANET): Routing Protocol Performance Issues and Evaluation Considerations S. Corson J. Macker January 1999 ASCII 28912 12 MANET packet network hardwire wireless This memo first describes the characteristics of Mobile Ad hoc Networks (MANETs), and their idiosyncrasies with respect to traditional, hardwired packet networks. It then discusses the effect these differences have on the design and evaluation of network control protocols with an emphasis on routing performance evaluation considerations. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2502 Limitations of Internet Protocol Suite for Distributed Simulation the Large Multicast Environment M. Pullen M. Myjak C. Bouwens February 1999 ASCII 28190 11 IP DIS distributed applications This memo defines services that LSMA has found to be required, and aspects of the Internet protocols that LSMA has found to need further development in order to meet these requirements. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2503 MIME Types for Use with the ISO ILL Protocol R. Moulton M. Needleman February 1999 ASCII 9078 6 multipurpose mail internet extensions media type interlibrary loan This memorandum describes a set of MIME types for use with the ISO Interlibrary Loan Protocol (ISO 10160/10161). This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2504 Users' Security Handbook E. Guttman L. Leong G. Malkin February 1999 ASCII 74036 33 encryption networks systems The Users' Security Handbook is the companion to the Site Security Handbook (SSH). It is intended to provide users with the information they need to help keep their networks and systems secure. This memo provides information for the Internet community. FYI0034 INFORMATIONAL INFORMATIONAL RFC2505 Anti-Spam Recommendations for SMTP MTAs G. Lindberg February 1999 ASCII 53597 24 simple mail transfer protocol agents sendmail This memo gives a number of implementation recommendations for SMTP, MTAs (Mail Transfer Agents, e.g. sendmail,) to make them more capable of reducing the impact of spam. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. lindberg-anti-spam-mta-08 BCP0030 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2506 Media Feature Tag Registration Procedure K. Holtman A. Mutz T. Hardie March 1999 ASCII 24892 12 data formats vocabulary negotiation mechanism This document defines a registration procedure which uses the Internet Assigned Numbers Authority (IANA) as a central registry for the media feature vocabulary. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-conneg-feature-reg-03 BCP0031 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2507 IP Header Compression M. Degermark B. Nordgren S. Pink February 1999 ASCII 106292 47 internet protocol tcp transmission control bandwidth This document describes how to compress multiple IP headers and TCP and UDP headers per hop over point to point links. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2508 Compressing IP/UDP/RTP Headers for Low-Speed Serial Links S. Casner V. Jacobson February 1999 ASCII 60474 24 internet protocol user datagram real-timetransport interoperability This document describes a method for compressing the headers of IP/UDP/RTP datagrams to reduce overhead on low-speed serial links. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2509 IP Header Compression over PPP M. Engan S. Casner C. Bormann February 1999 ASCII 18676 10 IPCOM-PPP internet protocol point-to-point datagrams This document describes an option for negotiating the use of header compression on IP datagrams transmitted over the Point-to-Point Protocol. It defines extensions to the PPP Control Protocols for IPv4 and IPv6. [STANDARDS-TRACK] RFC3544 PROPOSED STANDARD PROPOSED STANDARD RFC2510 Internet X.509 Public Key Infrastructure Certificate Management Protocols C. Adams S. Farrell March 1999 ASCII 158178 72 PKICMP pki security cryptographic authentication This document describes the Internet X.509 Public Key Infrastructure (PKI) Certificate Management Protocols. [STANDARDS-TRACK] ietf-pkix-ipki3cmp-09 PROPOSED STANDARD PROPOSED STANDARD RFC2511 Internet X.509 Certificate Request Message Format M. Myers C. Adams D. Solo D. Kemp March 1999 ASCII 48278 25 X.509-CRMF crmf security encryption authenticaion This document describes the Certificate Request Message Format (CRMF). [STANDARDS-TRACK] ietf-pkix-crmf-01 PROPOSED STANDARD PROPOSED STANDARD RFC2512 Accounting Information for ATM Networks K. McCloghrie J. Heinanen W. Greene A. Prasad February 1999 ASCII 29119 15 mib management information base autonomous transfer mode This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This memo defines a set of ATM-specific accounting information which can be collected for connections on ATM networks. [STANDARDS-TRACK] ietf-atommib-atmaact-03 PROPOSED STANDARD PROPOSED STANDARD RFC2513 Managed Objects for Controlling the Collection and Storage of Accounting Information for Connection-Oriented Networks K. McCloghrie J. Heinanen W. Greene A. Prasad February 1999 ASCII 60789 29 mib management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for controlling the collection and storage of accounting information for connection-oriented networks such as ATM. [STANDARDS-TRACK] ietf-atommib-acct-06 PROPOSED STANDARD PROPOSED STANDARD RFC2514 Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management M. Noto E. Spiegel K. Tesink February 1999 ASCII 37583 20 ATM-TC-OID asynchronous transfer mode MIB management information base This memo describes Textual Conventions and OBJECT-IDENTITIES used for managing ATM-based interfaces, devices, networks and services. [STANDARDS-TRACK] ietf-atommib-atm2TC-09 PROPOSED STANDARD PROPOSED STANDARD RFC2515 Definitions of Managed Objects for ATM Management K. Tesink Ed February 1999 ASCII 179993 87 ATM-MIBMAN asynchronous transfer mode MIB management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing ATM-based interfaces, devices, networks and services. [STANDARDS-TRACK] ietf-atommib-atm1ng-06 RFC1695 PROPOSED STANDARD PROPOSED STANDARD RFC2516 A Method for Transmitting PPP Over Ethernet (PPPoE) L. Mamakos K. Lidl J. Evarts D. Carrel D. Simone R. Wheeler February 1999 ASCII 32537 17 PPPOE point-to-point protocol link control network layer This document describes how to build PPP sessions and encapsulate PPP packets over Ethernet. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2517 Building Directories from DNS: Experiences from WWWSeeker R. Moats R. Huber February 1999 ASCII 14001 7 domain name system internet world wide web This memo discusses lessons that were learned during InterNIC Directory and Database Services' development and operation of WWWSeeker, an application that finds a web site given information about the name and location of an organization. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2518 HTTP Extensions for Distributed Authoring -- WEBDAV Y. Goland E. Whitehead A. Faizi S. Carter D. Jensen February 1999 ASCII 202829 94 WEBDAV hypertext transfer protocol web content This document specifies a set of methods, headers, and content-types ancillary to HTTP/1.1 for the management of resource properties, creation and management of resource collections, namespace manipulation, and resource locking (collision avoidance). [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2519 A Framework for Inter-Domain Route Aggregation E. Chen J. Stewart February 1999 ASCII 25394 13 IDRA bgp border gateway protocol address ip internet This document presents a framework for inter-domain route aggregation and shows an example router configuration which 'implements' this framework. This memo provides information for the Internet community ietf-idr-aggregation-framework-04 INFORMATIONAL INFORMATIONAL RFC2520 NHRP with Mobile NHCs J. Luciani H. Suzuki N. Doraswamy D. Horton February 1999 ASCII 16763 8 NHRP-MNHCS next hop resolution protocol authentication extension is document describes an extension to NHRP which would allow Mobile NHCs to perform a registration with and attach to an NHS in their home LIS in an authenticated manner. This memo defines an Experimental Protocol for the Internet community. ietf-ion-nhrp-mobile-nhc-01 EXPERIMENTAL EXPERIMENTAL RFC2521 ICMP Security Failures Messages P. Karn W. Simpson March 1999 ASCII 14637 9 ICMP-SEC internet control message protocol ip This document specifies ICMP messages for indicating failures when using IP Security Protocols (AH and ESP). This document defines an Experimental Protocol for the Internet community. simpson-icmp-ipsec-fail-02 EXPERIMENTAL EXPERIMENTAL RFC2522 Photuris: Session-Key Management Protocol P. Karn W. Simpson March 1999 ASCII 157224 80 PHOTURIS-S ip internet protocol ah esp This document defines the basic protocol mechanisms. This document defines an Experimental Protocol for the Internet community. simpson-photouris-18 EXPERIMENTAL EXPERIMENTAL RFC2523 Photuris: Extended Schemes and Attributes P. Karn W. Simpson March 1999 ASCII 38166 21 PHOTURIS-E ip internet protocol security Photuris is a session-key management protocol. Extensible Exchange- Schemes are provided to enable future implementation changes without affecting the basic protocol. This document defines an Experimental Protocol for the Internet community. simpson-photouris-schemes-05 EXPERIMENTAL EXPERIMENTAL RFC2524 Neda's Efficient Mail Submission and Delivery (EMSD) Protocol Specification Version 1.3 M. Banan February 1999 ASCII 153171 83 EMSD wireless IP internet protocol This specification narrowly focuses on submission and delivery of short mail messages with a clear emphasis on efficiency. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2525 Known TCP Implementation Problems V. Paxson M. Allman S. Dawson W. Fenner J. Griner I. Heavens K. Lahey J. Semke B. Volz March 1999 ASCII 137201 61 transmission control protocol This memo catalogs a number of known TCP implementation problems. This memo provides information for the Internet community. ietf-tcpimpl-prob-05 INFORMATIONAL INFORMATIONAL RFC2526 Reserved IPv6 Subnet Anycast Addresses D. Johnson S. Deering March 1999 ASCII 14555 7 internet protocol routing architecture This document defines a set of reserved anycast addresses within each subnet prefix, and lists the initial allocation of these reserved subnet anycast addresses. [STANDARDS-TRACK] ietf-ipngwg-resv-anycast-02 PROPOSED STANDARD PROPOSED STANDARD RFC2527 Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework S. Chokhani W. Ford March 1999 ASCII 91860 45 pkix encryption security authentication This document presents a framework to assist the writers of certificate policies or certification practice statements for certification authorities and public key infrastructures. In particular, the framework provides a comprehensive list of topics that potentially (at the writer's discretion) need to be covered in a certificate policy definition or a certification practice statement. This memo provides information for the Internet community. ietf-pkix-ipki-part4-03 RFC3647 INFORMATIONAL INFORMATIONAL RFC2528 Internet X.509 Public Key Infrastructure Representation of Key Exchange Algorithm (KEA) Keys in Internet X.509 Public Key Infrastructure Certificates R. Housley W. Polk March 1999 ASCII 18273 9 security authentication cryptology This specification contains guidance on the use of the Internet Public Key Infrastructure certificates to convey Key Exchange Algorithm (KEA) keys. This memo provides information for the Internet community. ietf-pkix-ipki-kea-02 INFORMATIONAL INFORMATIONAL RFC2529 Transmission of IPv6 over IPv4 Domains without Explicit Tunnels B. Carpenter C. Jung March 1999 ASCII 21049 10 link-local link local addresses internet protocol ip This memo specifies the frame format for transmission of IPv6 (IPV6) packets and the method of forming IPv6 link-local addresses over IPv4 domains. It also specifies the content of the Source/Target Link-layer Address option used in the Router Solicitation, Router Advertisement, Neighbor Solicitation, and Neighbor Advertisement and Redirect messages, when those messages are transmitted on an IPv4 multicast network. [STANDARDS-TRACK] ietf-ipngwg-6over4-02 PROPOSED STANDARD PROPOSED STANDARD RFC2530 Indicating Supported Media Features Using Extensions to DSN and MDN D. Wing March 1999 ASCII 7824 5 message disposition notification delivery status This memo describes a format for generating Message Disposition Notifications and Delivery Status Notifications which contain such information. [STANDARDS-TRACK] ietf-fax-reporting-extensions-05 PROPOSED STANDARD PROPOSED STANDARD RFC2531 Content Feature Schema for Internet Fax G. Klyne L. McIntyre March 1999 ASCII 88295 51 media features mechanism This document defines a content feature schema that is a profile of the media feature registration mechanisms for use in performing capability identification between extended Internet fax systems. [STANDARDS-TRACK] ietf-fax-feature-schema-05 RFC2879 PROPOSED STANDARD PROPOSED STANDARD RFC2532 Extended Facsimile Using Internet Mail L. Masinter D. Wing March 1999 ASCII 22717 12 mail user fax This document describes extensions to "Simple Mode of Facsimile Using Internet Mail", and describes additional features, including transmission of enhanced document characteristics (higher resolution, color) and confirmation of delivery and processing. [STANDARDS-TRACK] ietf-fax-eifax-12 PROPOSED STANDARD PROPOSED STANDARD RFC2533 A Syntax for Describing Media Feature Sets G. Klyne March 1999 ASCII 79057 37 message senders recipients file format This document introduces and describes a syntax that can be used to define feature sets which are formed from combinations and relations involving individual media features. [STANDARDS-TRACK] ietf-conneg-feature-syntax-04 RFC2738 RFC2938 PROPOSED STANDARD PROPOSED STANDARD RFC2534 Media Features for Display, Print, and Fax L. Masinter D. Wing A. Mutz K. Holtman March 1999 ASCII 15466 9 data format vocabulary negotiation mechanisms This specification defines some common media features for describing image resolution, size, color, and image representation methods that are common to web browsing, printing, and facsimile applications. [STANDARDS-TRACK] ietf-conneg-media-features-05 PROPOSED STANDARD PROPOSED STANDARD RFC2535 Domain Name System Security Extensions D. Eastlake 3rd March 1999 ASCII 110958 47 DNS-SECEXT dns authentication This document incorporates feedback on RFC 2065 from early implementers and potential users. [STANDARDS-TRACK] ietf-dnssec-secext2-07 RFC2065 RFC4033 RFC4034 RFC4035 RFC2181 RFC1035 RFC1034 RFC2931 RFC3007 RFC3008 RFC3090 RFC3226 RFC3445 RFC3597 RFC3655 RFC3658 RFC3755 RFC3757 RFC3845 PROPOSED STANDARD PROPOSED STANDARD RFC2536 DSA KEYs and SIGs in the Domain Name System (DNS) D. Eastlake 3rd March 1999 ASCII 11121 6 digital signature algorithm signatures cryptology A standard method for storing US Government Digital Signature Algorithm keys and signatures in the Domain Name System is described which utilizes DNS KEY and SIG resource records. [STANDARDS-TRACK] ietf-dnssec-dss-03 PROPOSED STANDARD PROPOSED STANDARD RFC2537 RSA/MD5 KEYs and SIGs in the Domain Name System (DNS) D. Eastlake 3rd March 1999 ASCII 10810 6 message digest signatures cryptology security A standard method for storing RSA keys and and RSA/MD5 based signatures in the Domain Name System is described which utilizes DNS KEY and SIG resource records. [STANDARDS-TRACK] ietf-dnsssec-rsa-01 RFC3110 PROPOSED STANDARD PROPOSED STANDARD RFC2538 Storing Certificates in the Domain Name System (DNS) D. Eastlake 3rd O. Gudmundsson March 1999 ASCII 19857 10 SC-DNS cryptology authenticity Cryptographic public key are frequently published and their authenticity demonstrated by certificates. A CERT resource record (RR) is defined so that such certificates and related certificate revocation lists can be stored in the Domain Name System (DNS). [STANDARDS-TRACK] ietf-dnssec-certs-04 PROPOSED STANDARD PROPOSED STANDARD RFC2539 Storage of Diffie-Hellman Keys in the Domain Name System (DNS) D. Eastlake 3rd March 1999 ASCII 21049 7 DHK-DNS cryptology authentication security signatures digital A standard method for storing Diffie-Hellman keys in the Domain Name System is described which utilizes DNS KEY resource records. [STANDARDS-TRACK] ietf-dnssec-dhk-03 PROPOSED STANDARD PROPOSED STANDARD RFC2540 Detached Domain Name System (DNS) Information D. Eastlake 3rd March 1999 ASCII 12546 6 DNS-INFO security digital signatures authentication A standard format is defined for representing detached DNS information. This is anticipated to be of use for storing information retrieved from the Domain Name System (DNS), including security information, in archival contexts or contexts not connected to the Internet. This memo defines an Experimental Protocol for the Internet community. ietf-dnssec-ddi-06 EXPERIMENTAL EXPERIMENTAL RFC2541 DNS Security Operational Considerations D. Eastlake 3rd March 1999 ASCII 14498 7 DNS-SOC domain name system cryptology resource records rrs This document discusses these operational aspects for keys and signatures used in connection with the KEY and SIG DNS resource records. This memo provides information for the Internet community. ietf-dnssec-secops-02 INFORMATIONAL INFORMATIONAL RFC2542 Terminology and Goals for Internet Fax L. Masinter March 1999 ASCII 46372 20 real-time real time session store forward This document defines a number of terms useful for the discussion of Internet Fax. In addition, it describes the goals of the Internet Fax working group and establishes a baseline of desired functionality against which protocols for Internet Fax can be judged. This memo provides information for the Internet community. ietf-fax-goals-04 INFORMATIONAL INFORMATIONAL RFC2543 SIP: Session Initiation Protocol M. Handley H. Schulzrinne E. Schooler J. Rosenberg March 1999 ASCII 338861 151 SIP application-layer application layer multimedia multicast unicast The Session Initiation Protocol (SIP) is an application-layer control (signaling) protocol for creating, modifying and terminating sessions with one or more participants. [STANDARDS-TRACK] ietf-mmusic-sip-12 RFC3261 RFC3262 RFC3263 RFC3264 RFC3265 PROPOSED STANDARD PROPOSED STANDARD RFC2544 Benchmarking Methodology for Network Interconnect Devices S. Bradner J. McQuaid March 1999 ASCII 66688 31 testing performance This document is a republication of RFC 1944 correcting the values for the IP addresses which were assigned to be used as the default addresses for networking test equipment. This memo provides information for the Internet community. RFC1944 INFORMATIONAL INFORMATIONAL RFC2545 Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing P. Marques F. Dupont March 1999 ASCII 10209 5 border gateway protocol idr internet routing BGP-4 Multiprotocol Extensions (BGP-MP) defines the format of two BGP attributes (MP_REACH_NLRI and MP_UNREACH_NLRI) that can be used to announce and withdraw the announcement of reachability information. This document defines how compliant systems should make use of those attributes for the purpose of conveying IPv6 routing information. [STANDARDS-TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC2546 6Bone Routing Practice A. Durand B. Buclin March 1999 ASCII 17844 10 IPv6 internet protocol This memo identifies guidelines on how 6Bone sites might operate, so that the 6Bone can remain a quality experimentation environment and to avoid pathological situations that have been encountered in the past. It defines the 'best current practice' acceptable in the 6Bone for the configuration of both Interior Gateway Protocols and Exterior Gateway Protocols. This memo provides information for the Internet community. ietf-ngtrans-6bone-routing-01 RFC2772 INFORMATIONAL INFORMATIONAL RFC2547 BGP/MPLS VPNs E. Rosen Y. Rekhter March 1999 ASCII 63270 25 border gateway protocol multiprotocol label switching architecture virtual private networks This document describes a method by which a Service Provider with an IP backbone may provide VPNs (Virtual Private Networks) for its customers. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2548 Microsoft Vendor-specific RADIUS Attributes G. Zorn March 1999 ASCII 80763 41 attributes remote access dialin user service dial-in This document describes the set of Microsoft vendor-specific RADIUS attributes. This memo provides information for the Internet community. ietf-radius-ms-vsa-01 INFORMATIONAL INFORMATIONAL RFC2549 IP over Avian Carriers with Quality of Service D. Waitzman April 01 1999 ASCII 9519 6 avian carrier april fools qos This memo amends RFC 1149, "A Standard for the Transmission of IP Datagrams on Avian Carriers", with Quality of Service information. This is an experimental, not recommended standard. This memo defines an Experimental Protocol for the Internet community. RFC1149 INFORMATIONAL INFORMATIONAL RFC2550 Y10K and Beyond S. Glassman M. Manasse J. Mogul April 01 1999 ASCII 28011 14 years dates formats april fools This specification provides a solution to the "Y10K" problem which has also been called the "YAK" problem (hex) and the "YXK" problem (Roman numerals). This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2551 The Roman Standards Process -- Revision III S. Bradner April 01 1999 ASCII 28054 37 numerals protocols procedures april fools This memo documents the process used by the Roman community for the standardization of protocols and procedures. It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process. It also addresses the intellectual property rights and copyright issues associated with the standards process. INFORMATIONAL INFORMATIONAL RFC2552 Architecture for the Information Brokerage in the ACTS Project GAIA M. Blinov M. Bessonov C. Clissmann April 1999 ASCII 65172 30 electronic systems products This memo introduces a domain and supplier independent generic architecture for information brokerage, designed as part of the ACTS project GAIA (Generic Architecture for Information Availability). This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2553 Basic Socket Interface Extensions for IPv6 R. Gilligan S. Thomson J. Bound W. Stevens March 1999 ASCII 89215 41 internet protocol api application program interface tcp transmission control 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 support IPv6 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. This memo provides information for the Internet community. ietf-ipngwg-bsd-api-new-06 RFC2133 RFC3493 RFC3152 INFORMATIONAL INFORMATIONAL RFC2554 SMTP Service Extension for Authentication J. Myers March 1999 ASCII 20534 11 simple mail transfer protocol security layer sasl This document defines an SMTP service extension [ESMTP] whereby an SMTP client may indicate an authentication mechanism to the server, perform an authentication protocol exchange, and optionally negotiate a security layer for subsequent protocol interactions. [STANDARDS-TRACK] myers-smtp-auth-12 PROPOSED STANDARD PROPOSED STANDARD RFC2555 30 Years of RFCs RFC Editor et al. April 07 1999 ASCII 42902 18 request for comments series documents publication The rest of this document contains a brief recollection from the present RFC Editor Joyce K. Reynolds, followed by recollections from three pioneers: Steve Crocker who wrote RFC 1, Vint Cerf whose long-range vision continues to guide us, and Jake Feinler who played a key role in the middle years of the RFC series. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2556 OSI connectionless transport services on top of UDP Applicability Statement for Historic Status S. Bradner March 1999 ASCII 5864 4 user datagram protocol ISO international organization for standardization RFC 1240, "OSI connectionless transport services on top of UDP", was published as a Proposed Standard in June 1991 but at this time there do not seem to be any implementations which follow RFC 1240. In addition there is a growing concern over using UDP-based transport protocols in environments where congestion is a possibility This memo provides information for the Internet community. bradner-1240.his-01 INFORMATIONAL INFORMATIONAL RFC2557 MIME Encapsulation of Aggregate Documents, such as HTML (MHTML) J. Palme A. Hopmann N. Shelness March 1999 ASCII 61854 28 MHTML multipurpose internet mail extensions multimedia uri uniform resource identifiers This document a) defines the use of a MIME multipart/related structure to aggregate a text/html root resource and the subsidiary resources it references, and b) specifies a MIME content-header (Content-Location) that allow URIs in a multipart/related text/html root body part to reference subsidiary resources in other body parts of the same multipart/related structure. [STANDARDS-TRACK] ietf-mhtml-rev-07 RFC2110 PROPOSED STANDARD PROPOSED STANDARD RFC2558 Definitions of Managed Objects for the SONET/SDH Interface Type K. Tesink March 1999 ASCII 138550 74 MIB Management SNMP This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) interfaces. This document is a companion to the documents that define Managed Objects for the DS1/E1/DS2/E2 and DS3/E3 Interface Types. [STANDARDS-TRACK] ietf-atommib-sonetng-05 RFC1595 RFC3592 PROPOSED STANDARD PROPOSED STANDARD RFC2559 Internet X.509 Public Key Infrastructure Operational Protocols - LDAPv2 S. Boeyen T. Howes P. Richard April 1999 ASCII 22889 13 X.500 LDAP lightweight directory protocol Specifically, this document addresses requirements to provide access to Public Key Infrastructure (PKI) repositories for the purposes of retrieving PKI information and managing that same information. [STANDARDS-TRACK] ietf-pkix-ipki2opp-08 RFC3494 RFC1778 HISTORIC PROPOSED STANDARD RFC2560 X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP M. Myers R. Ankney A. Malpani S. Galperin C. Adams June 1999 ASCII 43243 23 PKIX digital security This document specifies a protocol useful in determining the current status of a digital certificate without requiring CRLs. [STANDARDS- TRACK] ietf-pkix-ocsp-07 PROPOSED STANDARD PROPOSED STANDARD RFC2561 Base Definitions of Managed Objects for TN3270E Using SMIv2 K. White R. Moore April 1999 ASCII 113705 56 MIB management information base structure telnet This memo defines a Management Information Base (MIB) for configuring and managing TN3270E servers. The MIB defined by this memo provides generic support for both host and gateway TN3270E server implementations. [STANDARDS-TRACK] ietf-tn327oe-tn3270-mib-10 PROPOSED STANDARD PROPOSED STANDARD RFC2562 Definitions of Protocol and Managed Objects for TN3270E Response Time Collection Using SMIv2 (TN3270E-RT-MIB) K. White R. Moore April 1999 ASCII 110633 49 TN2370E-RT-MIB MIB management information base structure telnet This memo defines the protocol and the Management Information Base (MIB) for performing response time data collection on TN3270 and TN3270E sessions by a TN3270E server. [STANDARDS-TRACK] ietf-tn327oe-rt-mib-07 PROPOSED STANDARD PROPOSED STANDARD RFC2563 DHCP Option to Disable Stateless Auto-Configuration in IPv4 Clients R. Troll May 1999 ASCII 17838 9 dynamic host configuration protocol internet address This document describes a mechanism by which DHCP servers are able to tell clients that they do not have an IP address to offer, and that the client should not generate an IP address it's own. [STANDARDS-TRACK] ietf-dhc-autoconfig-04 PROPOSED STANDARD PROPOSED STANDARD RFC2564 Application Management MIB C. Kalbfleisch C. Krupczak R. Presuhn J. Saperia May 1999 ASCII 183314 86 APP-MIB management information base This memo defines a standards track portion of the Management Information Base (MIB) for use with network management protocols in the Internet Community. In particular, it defines objects used for the management of applications. [STANDARDS-TRACK] ietf-applmib-mib-11 PROPOSED STANDARD PROPOSED STANDARD RFC2565 Internet Printing Protocol/1.0: Encoding and Transport R. Herriot Editor S. Butler P. Moore R. Turner April 1999 ASCII 80439 37 IPP-E-T IPP application media-type media type This document defines the rules for encoding IPP operations and IPP attributes into a new Internet mime media type called "application/ipp". This document also defines the rules for transporting over HTTP a message body whose Content-Type is "application/ipp". This document defines an Experimental protocol for the Internet community. ietf-ipp-protocol-07 RFC2910 EXPERIMENTAL EXPERIMENTAL RFC2566 Internet Printing Protocol/1.0: Model and Semantics R. deBry T. Hastings R. Herriot S. Isaacson P. Powell April 1999 ASCII 438887 173 IPP-M-S IPP application media-type job This document describes a simplified model consisting of abstract objects, their attributes, and their operations that is independent of encoding and transport. This document also addresses security, internationalization, and directory issues. This memo defines an Experimental Protocol for the Internet community. ietf-ipp-model-11 RFC2911 EXPERIMENTAL EXPERIMENTAL RFC2567 Design Goals for an Internet Printing Protocol F. Wright April 1999 ASCII 90260 43 IPP-DG IPP application media-type media type This document takes a broad look at distributed printing functionality, and it enumerates real-life scenarios that help to clarify the features that need to be included in a printing protocol for the Internet. It identifies requirements for three types of users: end users, operators, and administrators. This memo defines an Experimental Protocol for the Internet community. ietf-ipp-req-03 EXPERIMENTAL EXPERIMENTAL RFC2568 Rationale for the Structure of the Model and Protocol for the Internet Printing Protocol S. Zilles April 1999 ASCII 23547 10 IPP-RAT IPP application media-type media type This document describes IPP from a high level view, defines a roadmap for the various documents that form the suite of IPP specifications, and gives background and rationale for the IETF working group's major decisions. This memo defines an Experimental Protocol for the Internet community. ietf-ipp-rat-04 EXPERIMENTAL EXPERIMENTAL RFC2569 Mapping between LPD and IPP Protocols R. Herriot Editor T. Hastings N. Jacobs J. Martin April 1999 ASCII 57886 28 application media-type media type internet printing protocol line printer daemon This document is one of a set of documents, which together describe all aspects of a new Internet Printing Protocol (IPP). One of the purposes of this document is to compare the functionality of the two protocols. Another purpose is to facilitate implementation of gateways between LPD and IPP. This memo defines an Experimental Protocol for the Internet community. ietf-ipp-lpd-ipp-map-05 EXPERIMENTAL EXPERIMENTAL RFC2570 Introduction to Version 3 of the Internet-standard Network Management Framework J. Case R. Mundy D. Partain B. Stewart April 1999 ASCII 50381 23 snmp simple protocol The purpose of this document is to provide an overview of the third version of the Internet-standard Management Framework, termed the SNMP version 3 Framework (SNMPv3). This memo provides information for the Internet community. ietf-snmpv3-intro-04 RFC3410 INFORMATIONAL INFORMATIONAL RFC2571 An Architecture for Describing SNMP Management Frameworks B. Wijnen D. Harrington R. Presuhn April 1999 ASCII 139260 62 ARCH-SNMP simple protocol network management This document describes an architecture for describing SNMP Management Frameworks. [STANDARDS-TRACK] ietf-snmpv3-arch-05 RFC2271 RFC3411 DRAFT STANDARD DRAFT STANDARD RFC2572 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) J. Case D. Harrington R. Presuhn B. Wijnen April 1999 ASCII 96035 44 MPD-SNMP processing models multiple This document describes the Message Processing and Dispatching for SNMP messages within the SNMP architecture. It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP Message Processing Models, and for dispatching PDUs to SNMP applications. This document also describes one Message Processing Model - the SNMPv3 Message Processing Model. [STANDARDS-TRACK] RFC2272 RFC3412 DRAFT STANDARD DRAFT STANDARD RFC2573 SNMP Applications D. Levi P. Meyer B. Stewart April 1999 ASCII 150427 72 SNMP-APP simple network management protocol proxy operations command This memo describes five types of SNMP applications which make use of an SNMP engine. This memo also defines MIB modules for specifying targets of management operations, for notification filtering, and for proxy fowarding. [STANDARDS-TRACK] ietf-snmpv3-appl-v2-03 RFC2273 RFC3413 DRAFT STANDARD DRAFT STANDARD RFC2574 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) U. Blumenthal B. Wijnen April 1999 ASCII 190755 86 USM-SNMPV3 message level mib information base This document describes the User-based Security Model (USM) for SNMP version 3 for use in the SNMP architecture. It defines the Elements of Procedure for providing SNMP message level security. This document also includes a MIB for remotely monitoring/managing the configuration parameters for this Security Model. [STANDARDS-TRACK] ietf-snmpv3-usm-v2-05 RFC2274 RFC3414 DRAFT STANDARD DRAFT STANDARD RFC2575 View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) B. Wijnen R. Presuhn K. McCloghrie April 1999 ASCII 79642 38 VACM-SNMP mib information base This document describes the View-based Access Control Model for use in the SNMP architecture (RFC2571). It defines the Elements of Procedure for controlling access to management information. This document also includes a MIB for remotely managing the configuration parameters for the View-based Access Control Model. [STANDARDS-TRACK] ietf-snmpv3-vacm-04 RFC2275 RFC3415 DRAFT STANDARD DRAFT STANDARD RFC2576 Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework R. Frye D. Levi S. Routhier B. Wijnen March 2000 ASCII 98589 44 SNMP simple network management protocol mib information base The purpose of this document is to describe coexistence between version 3 of the Internet-standard Network Management Framework, (SNMPv3), version 2 of the Internet-standard Network Management Framework (SNMPv2), and the original Internet-standard Network Management Framework (SNMPv1). [STANDARDS TRACK] ietf-snmpv3-coex-08 RFC1908 RFC2089 RFC3584 PROPOSED STANDARD PROPOSED STANDARD RFC2577 FTP Security Considerations M. Allman S. Ostermann May 1999 ASCII 17870 8 FTP-SEC file transfer protocol bounce attack password server This document provides suggestions for system administrators and those implementing FTP servers that will decrease the security problems associated with FTP. This memo provides information for the Internet community. ietf-ftpext-sec-consider-02 INFORMATIONAL INFORMATIONAL RFC2578 Structure of Management Information Version 2 (SMIv2) K. McCloghrie D. Perkins J. Schoenwaelder April 1999 ASCII 89712 42 SMIv2 Simple Network Management Protocol Version 2 It is the purpose of this document, the Structure of Management Information Version 2 (SMIv2), to define that adapted subset, and to assign a set of associated administrative values. [STANDARDS-TRACK] ops-smiv2-smi-01 RFC1902 STD0058 STANDARD STANDARD RFC2579 Textual Conventions for SMIv2 K. McCloghrie D. Perkins J. Schoenwaelder April 1999 ASCII 59039 25 CONV-MIB Simple Network Management Protocol Version 2 It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK] ops-smiv2-tc-01 RFC1903 STD0058 STANDARD STANDARD RFC2580 Conformance Statements for SMIv2 K. McCloghrie D. Perkins J. Schoenwaelder April 1999 ASCII 54253 29 CONF-MIB simple Network Management Protocol Version 2 Collections of related objects are defined in MIB modules. 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] ops-smiv2-conf-01 RFC1904 STD0058 STANDARD STANDARD RFC2581 TCP Congestion Control M. Allman V. Paxson W. Stevens April 1999 ASCII 31351 14 TCP-CC This document defines TCP's four intertwined congestion control algorithms: slow start, congestion avoidance, fast retransmit, and fast recovery. In addition, the document specifies how TCP should begin transmission after a relatively long idle period, as well as discussing various acknowledgment generation methods. [STANDARDS-TRACK] ietf-tcpimpl-cong-control-05 RFC2001 RFC3390 PROPOSED STANDARD PROPOSED STANDARD RFC2582 The NewReno Modification to TCP's Fast Recovery Algorithm S. Floyd T. Henderson April 1999 ASCII 29393 12 Transmission Control Protocol This document describes a specific algorithm for responding to partial acknowledgments, referred to as NewReno. This memo defines an Experimental Protocol for the Internet community. ietf-tcpimpl-newreno-02 RFC3782 EXPERIMENTAL EXPERIMENTAL RFC2583 Guidelines for Next Hop Client (NHC) Developers R. Carlson L. Winkler May 1999 ASCII 21338 9 NHRP resolution protocol IP internet This document provides guidelines for developers of the Next Hop Resolution Protocol Clients (NHC). The intent is to define the interaction between the NHC code and the TCP/IP protocol stack of the local host operating system. This memo provides information for the Internet community. carlson-nhrp-03 INFORMATIONAL INFORMATIONAL RFC2584 Definitions of Managed Objects for APPN/HPR in IP Networks B. Clouston B. Moore May 1999 ASCII 40187 21 internet protocol MIB management information base high performance routing 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 HPR (High Performance Routing) network devices which have the capability to communicate in IP (Internet Protocol) networks. [STANDARDS-TRACK] ietf-snaunau-hpripmib-02 PROPOSED STANDARD PROPOSED STANDARD RFC2585 Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTP R. Housley P. Hoffman May 1999 ASCII 14813 8 file transfer hypertext PKI The protocol conventions described in this document satisfy some of the operational requirements of the Internet Public Key Infrastructure (PKI). This document specifies the conventions for using the File Transfer Protocol (FTP) and the Hypertext Transfer Protocol (HTTP) to obtain certificates and certificate revocation lists (CRLs) from PKI repositories. [STANDARDS-TRACK] ietf-pkix-opp-ftp-http-04 PROPOSED STANDARD PROPOSED STANDARD RFC2586 The Audio/L16 MIME content type J. Salsman H. Alvestrand May 1999 ASCII 8694 5 AUDIO/L16 media-type application multipurpose internet mail extensions This document defines the audio/L16 MIME type, a reasonable quality audio format for use in Internet applications. This memo provides information for the Internet community. alvestrand-audio-l16-01 INFORMATIONAL INFORMATIONAL RFC2587 Internet X.509 Public Key Infrastructure LDAPv2 Schema S. Boeyen T. Howes P. Richard June 1999 ASCII 15102 8 lightweight directory access protocol pkix The schema defined in this document is a minimal schema to support PKIX in an LDAPv2 environment, as defined in RFC 2559. Only PKIX-specific components are specified here. [STANDARDS-TRACK] ietf-pkix-ldap2-schema-02 PROPOSED STANDARD PROPOSED STANDARD RFC2588 IP Multicast and Firewalls R. Finlayson May 1999 ASCII 28622 12 Internet Protocol security gateway traffic In this document, we discuss the issues surrounding the traversal of IP multicast traffic across a firewall, and describe possible ways in which a firewall can implement and control this traversal. We also explain why some firewall mechanisms - such as SOCKS - that were designed specifically for unicast traffic, are less appropriate for multicast. This memo provides information for the Internet community. ietf-mboned-mcast-firewall-02 INFORMATIONAL INFORMATIONAL RFC2589 Lightweight Directory Access Protocol (v3): Extensions for Dynamic Directory Services Y. Yaacovi M. Wahl T. Genovese May 1999 ASCII 26855 12 LDAPv3 request response operations This document defines the requirements for dynamic directory services and specifies the format of request and response extended operations for supporting client-server interoperation in a dynamic directories environment. [STANDARDS-TRACK] ietf-asid-ldapv3-dynamic-08 PROPOSED STANDARD PROPOSED STANDARD RFC2590 Transmission of IPv6 Packets over Frame Relay Networks Specification A. Conta A. Malis M. Mueller May 1999 ASCII 41817 19 internet Protocol format link-local This memo describes mechanisms for the transmission of IPv6 packets over Frame Relay networks. [STANDARDS-TRACK] ietf-ion-ipv6-fr-02 PROPOSED STANDARD PROPOSED STANDARD RFC2591 Definitions of Managed Objects for Scheduling Management Operations D. Levi J. Schoenwaelder May 1999 ASCII 52920 25 mib information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK] ietf-disman-schedule-mib-06 RFC3231 PROPOSED STANDARD PROPOSED STANDARD RFC2592 Definitions of Managed Objects for the Delegation of Management Script D. Levi J. Schoenwaelder May 1999 ASCII 110629 53 mib information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a set of managed objects that allow the delegation of management scripts to distributed managers. [STANDARDS-TRACK] ietf-disman-script-mib-08 RFC3165 PROPOSED STANDARD PROPOSED STANDARD RFC2593 Script MIB Extensibility Protocol Version 1.0 J. Schoenwaelder J. Quittek May 1999 ASCII 49663 22 management information base smx language specific The Script MIB extensibility protocol (SMX) defined in this memo separates language specific runtime systems from language independent Script MIB implementations. This memo defines an Experimental Protocol for the Internet community. schoenw-smx-00 RFC3179 EXPERIMENTAL EXPERIMENTAL RFC2594 Definitions of Managed Objects for WWW Services H. Hazewinkel C. Kalbfleisch J. Schoenwaelder May 1999 ASCII 88876 43 management information base mib world wide web This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet Community. In particular it describes a set of objects for managing World Wide Web (WWW) services. [STANDARDS-TRACK] ietf-applmib-wwwmib-11 PROPOSED STANDARD PROPOSED STANDARD RFC2595 Using TLS with IMAP, POP3 and ACAP C. Newman June 1999 ASCII 32440 15 application configuration access protocol post office internet message transport layer security Recognizing that such sites will desire simple password authentication in combination with TLS encryption, this specification defines the PLAIN SASL mechanism for use with protocols which lack a simple password authentication command such as ACAP and SMTP. [STANDARDS-TRACK] newman-tls-imappop-09 PROPOSED STANDARD PROPOSED STANDARD RFC2596 Use of Language Codes in LDAP M. Wahl T. Howes May 1999 ASCII 17413 9 lightweight directory access protocol servers This document describes how language codes are carried in LDAP and are to be interpreted by LDAP servers. [STANDARDS-TRACK] ietf-ldapext-lang-01 RFC3866 PROPOSED STANDARD PROPOSED STANDARD RFC2597 Assured Forwarding PHB Group J. Heinanen F. Baker W. Weiss J. Wroclawski June 1999 ASCII 24068 11 per-hop-behaviour differentiated services af assumed forwarding This document defines a general use Differentiated Services (DS) Per-Hop-Behavior (PHB) Group called Assured Forwarding (AF). [STANDARDS-TRACK] ietf-diffserv-af-06 RFC3260 PROPOSED STANDARD PROPOSED STANDARD RFC2598 An Expedited Forwarding PHB V. Jacobson K. Nichols K. Poduri June 1999 ASCII 23656 11 per-hop-forwarding behavior differentiated services ef The definition of PHBs (per-hop forwarding behaviors) is a critical part of the work of the Diffserv Working Group. This document describes a PHB called Expedited Forwarding. [STANDARDS-TRACK] ietf-diffserv-phb-ef-02 RFC3246 PROPOSED STANDARD PROPOSED STANDARD RFC2599 Request for Comments Summary RFC Numbers 2500-2599 A. DeLaCruz March 2000 ASCII 45845 23 INFORMATIONAL INFORMATIONAL RFC2600 Internet Official Protocol Standards J. Reynolds R. Braden March 2000 ASCII 86139 31 IAB official protocol standards This memo is published by the RFC Editor in accordance with Section 2.1 of "The Internet Standards Process -- Revision 3", RFC 2026, which specifies the rules and procedures by which all Internet standards are set. This memo is prepared by the RFC Editor for the IESG and IAB. Please see http://www.rfc-editor.org for later updates to this document. [STANDARDS-TRACK] RFC2500 RFC2700 HISTORIC STANDARD RFC2601 ILMI-Based Server Discovery for ATMARP M. Davison June 1999 ASCII 11820 6 integrated local management interface asynchronous transfer mode address resolution protocol This memo defines how ILMI-based Server Discovery, which provides a method for ATM-attached hosts and routers to dynamically determine the ATM addresses of servers, shall be used to locate ATMARP servers. [STANDARDS-TRACK] ietf-ion-discov-atmarp-05 PROPOSED STANDARD PROPOSED STANDARD RFC2602 ILMI-Based Server Discovery for MARS M. Davison June 1999 ASCII 12031 6 integrated local management interface asynchronous transfer mode address resolution protocol This memo defines how ILMI-based Server Discovery, which provides a method for ATM-attached hosts and routers to dynamically determine the ATM addresses of servers, shall be used to locate MARS servers. [STANDARDS-TRACK] ietf-ion-discov-mars-05 PROPOSED STANDARD PROPOSED STANDARD RFC2603 ILMI-Based Server Discovery for NHRP M. Davison June 1999 ASCII 11865 6 integrated local management interface next hop resolution protocol This memo defines how ILMI-based Server Discovery, which provides a method for ATM-attached hosts and routers to dynamically determine the ATM addresses of servers, shall be used to locate NHRP servers. [STANDARDS-TRACK] ietf-discov-nhrp-05 PROPOSED STANDARD PROPOSED STANDARD RFC2604 Wireless Device Configuration (OTASP/OTAPA) via ACAP R. Gellens June 1999 ASCII 65329 29 over-the-air ota application configuration access protocol This paper describes a viable and attractive means to provide OTASP/OTAPA via IS-707, using the ACAP protocol. This memo provides information for the Internet community. gellens-otasp-acap-01 RFC2636 INFORMATIONAL INFORMATIONAL RFC2605 Directory Server Monitoring MIB G. Mansfield S. Kille June 1999 ASCII 49166 26 management information base network services This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK] ietf-madman-dsa-mib-10 RFC1567 PROPOSED STANDARD PROPOSED STANDARD RFC2606 Reserved Top Level DNS Names D. Eastlake 3rd A. Panitz June 1999 ASCII 8008 5 domain name system private To reduce the likelihood of conflict and confusion, a few top level domain names are reserved for use in private testing, as examples in documentation, and the like. In addition, a few second level domain names reserved for use as examples are documented. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-dnsind-test-tlds-13 BCP0032 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2607 Proxy Chaining and Policy Implementation in Roaming B. Aboba J. Vollbrecht June 1999 ASCII 33271 15 network access server identifier radius This document describes how proxy chaining and policy implementation can be supported in roaming systems. This memo provides information for the Internet community. ietf-roamops-auth-10 INFORMATIONAL INFORMATIONAL RFC2608 Service Location Protocol, Version 2 E. Guttman C. Perkins J. Veizades M. Day June 1999 ASCII 129475 54 SLP network services The Service Location Protocol provides a scalable framework for the discovery and selection of network services. Using this protocol, computers using the Internet need little or no static configuration of network services for network based applications. This is especially important as computers become more portable, and users less tolerant or able to fulfill the demands of network system administration. [STANDARDS-TRACK] ietf-svrloc-protocol-v2-15 RFC2165 RFC3224 PROPOSED STANDARD PROPOSED STANDARD RFC2609 Service Templates and Service: Schemes E. Guttman C. Perkins J. Kempf June 1999 ASCII 72842 33 service location protocol slp url universal resource locator This document describes a formal procedure for defining and standardizing new service types and attributes for use with the "service:" scheme. [STANDARDS-TRACK] ietf-svrloc-service-scheme-14 RFC2165 PROPOSED STANDARD PROPOSED STANDARD RFC2610 DHCP Options for Service Location Protocol C. Perkins E. Guttman June 1999 ASCII 10859 6 slp dynamic host configuration protocol The Dynamic Host Configuration Protocol provides a framework for passing configuration information to hosts on a TCP/IP network. Entities using the Service Location Protocol need to find out the address of Directory Agents in order to transact messages. Another option provides an assignment of scope for configuration of SLP User and Service Agents. [STANDARDS-TRACK] ietf-dhc-slp-07 PROPOSED STANDARD PROPOSED STANDARD RFC2611 URN Namespace Definition Mechanisms L. Daigle D. van Gulik R. Iannella P. Falstrom June 1999 ASCII 26916 14 uniform resource names namespaces syntax This document lays out general definitions of and mechanisms for establishing URN "namespaces". This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-urn-nid-req-08 RFC3406 BCP0033 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2612 The CAST-256 Encryption Algorithm C. Adams J. Gilchrist June 1999 ASCII 37468 19 security cryptology This document describes an existing algorithm that can be used to satisfy this requirement. Included are a description of the cipher and the key scheduling algorithm, the s-boxes, and a set of test vectors (Appendix A). This memo provides information for the Internet community. adams-cast-256-00 INFORMATIONAL INFORMATIONAL RFC2613 Remote Network Monitoring MIB Extensions for Switched Networks Version 1.0 R. Waterman B. Lahaye D. Romascanu S. Waldbusser June 1999 ASCII 88701 44 smon management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices in switched networks environments. [STANDARDS-TRACK] ietf-rmonmib-smon-07 PROPOSED STANDARD PROPOSED STANDARD RFC2614 An API for Service Location J. Kempf E. Guttman June 1999 ASCII 164002 91 slp application program interface This document describes standardized APIs for SLP in C and Java. This memo provides information for the Internet community. ietf-svrloc-api-09 INFORMATIONAL INFORMATIONAL RFC2615 PPP over SONET/SDH A. Malis W. Simpson June 1999 ASCII 18708 10 point-to-point protocol synchronous optical network digital heirarchy This document describes the use of PPP over Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) circuits. [STANDARDS- TRACK] ietf-pppext-pppoversonet-update-04 RFC1619 PROPOSED STANDARD PROPOSED STANDARD RFC2616 Hypertext Transfer Protocol -- HTTP/1.1 R. Fielding J. Gettys J. Mogul H. Frystyk L. Masinter P. Leach T. Berners-Lee June 1999 ASCII 422317 176 PS 5529857 PDF 550558 HTTP World Wide Web WWW hypermedia 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", and is an update to RFC 2068. [STANDARDS-TRACK] ietf-http-v11-spec-rev-06 RFC2068 RFC2817 DRAFT STANDARD DRAFT STANDARD RFC2617 HTTP Authentication: Basic and Digest Access Authentication J. Franks P. Hallam-Baker J. Hostetler S. Lawrence P. Leach A. Luotonen L. Stewart June 1999 ASCII 77638 34 security encryption hypertext transfer protocol This document provides the specification for HTTP's authentication framework, the original Basic authentication scheme and a scheme based on cryptographic hashes, referred to as "Digest Access Authentication". [STANDARDS-TRACK] ietf-http-authentication-03 RFC2069 DRAFT STANDARD DRAFT STANDARD RFC2618 RADIUS Authentication Client MIB B. Aboba G. Zorn June 1999 ASCII 26889 14 management information base security remote access dialin user service This memo defines a set of extensions which instrument RADIUS authentication client functions. [STANDARDS-TRACK] ietf-radius-auth-clientmib-05 PROPOSED STANDARD PROPOSED STANDARD RFC2619 RADIUS Authentication Server MIB G. Zorn B. Aboba June 1999 ASCII 30464 16 management information base security remote access dialin user service This memo defines a set of extensions which instrument RADIUS authentication server functions. [STANDARDS-TRACK] ietf-radius-auth-servmib-05 PROPOSED STANDARD PROPOSED STANDARD RFC2620 RADIUS Accounting Client MIB B. Aboba G. Zorn June 1999 ASCII 23960 13 management information base security remote access dialin user service This memo defines a set of extensions which instrument RADIUS accounting client functions. This memo provides information for the Internet community. ietf-radius-acc-clientmib-05 INFORMATIONAL INFORMATIONAL RFC2621 RADIUS Accounting Server MIB G. Zorn B. Aboba June 1999 ASCII 27768 15 management information base security remote access,dialin user service This memo defines a set of extensions which instrument RADIUS accounting server functions. This memo provides information for the Internet community. ietf-radius-acc-servmib-05 INFORMATIONAL INFORMATIONAL RFC2622 Routing Policy Specification Language (RPSL) C. Alaettinoglu C. Villamizar E. Gerich D. Kessens D. Meyer T. Bates D. Karrenberg M. Terpstra June 1999 ASCII 140811 69 RPSL internet policy hierarchy network configuration RPSL allows a network operator to be able to specify routing policies at various levels in the Internet hierarchy; for example at the Autonomous System (AS) level. At the same time, policies can be specified with sufficient detail in RPSL so that low level router configurations can be generated from them. RPSL is extensible; new routing protocols and new protocol features can be introduced at any time. [STANDARDS-TRACK] ietf-rps-rpsl-v2-03 RFC2280 RFC4012 PROPOSED STANDARD PROPOSED STANDARD RFC2623 NFS Version 2 and Version 3 Security Issues and the NFS Protocol's Use of RPCSEC_GSS and Kerberos V5 M. Eisler June 1999 ASCII 42521 19 network file system remote procedure call architecture This memorandum clarifies various security issues involving the NFS protocol (Version 2 and Version 3 only) and then describes how the Version 2 and Version 3 of the NFS protocol use the RPCSEC_GSS security flavor protocol and Kerberos V5. [STANDARDS-TRACK] ietf-nfsv4-nfssec-01 PROPOSED STANDARD PROPOSED STANDARD RFC2624 NFS Version 4 Design Considerations S. Shepler June 1999 ASCII 52891 22 network file system This design considerations document is meant to present more detail than the working group charter. Specifically, it presents the areas that the working group will investigate and consider while developing a protocol specification for NFS version 4. This memo provides information for the Internet community. ietf-nfsv4-designconsider-03 INFORMATIONAL INFORMATIONAL RFC2625 IP and ARP over Fibre Channel M. Rajagopal R. Bhagwat W. Rickard June 1999 ASCII 137741 63 internet protocal address resolution The purpose of this document is to specify a way of encapsulating IP and Address Resolution Protocol(ARP) over Fibre Channel and also to describe a mechanism(s) for IP address resolution. [STANDARDS-TRACK] ietf-ipfc-fibre-channel-06 PROPOSED STANDARD PROPOSED STANDARD RFC2626 The Internet and the Millennium Problem (Year 2000) P. Nesser II June 1999 ASCII 547560 275 Y2K The Year 2000 Working Group (WG) has conducted an investigation into the millennium problem as it regards Internet related protocols. This investigation only targeted the protocols as documented in the Request For Comments Series (RFCs). This investigation discovered little reason for concern with regards to the functionality of the protocols. A few minor cases of older implementations still using two digit years (ala RFC 850) were discovered, but almost all Internet protocols were given a clean bill of health. Several cases of "period" problems were discovered, where a time field would "roll over" as the size of field was reached. In particular, there are several protocols, which have 32 bit, signed integer representations of the number of seconds since January 1, 1970 which will turn negative at Tue Jan 19 03:14:07 GMT 2038. Areas whose protocols will be effected by such problems have been notified so that new revisions will remove this limitation. This memo provides information for the Internet community. ietf-2000-issue-06 INFORMATIONAL INFORMATIONAL RFC2627 Key Management for Multicast: Issues and Architectures D. Wallner E. Harder R. Agee June 1999 ASCII 59263 23 communication sessions net key rekey This report contains a discussion of the difficult problem of key management for multicast communication sessions. It focuses on two main areas of concern with respect to key management, which are, initializing the multicast group with a common net key and rekeying the multicast group. This memo provides information for the Internet community. wallner-key-arch-01 INFORMATIONAL INFORMATIONAL RFC2628 Simple Cryptographic Program Interface (Crypto API) V. Smyslov June 1999 ASCII 60070 30 application security This document describes a simple Application Program Interface to cryptographic functions. This memo provides information for the Internet community. smyslov-crypto-cpi-00 INFORMATIONAL INFORMATIONAL RFC2629 Writing I-Ds and RFCs using XML M. Rose June 1999 ASCII 48677 31 internet-drafts extensible markup language source format This memo presents a technique for using XML (Extensible Markup Language) as a source format for documents in the Internet-Drafts (I-Ds) and Request for Comments (RFC) series. This memo provides information for the Internet community. mrose-writing-rfcs-02 INFORMATIONAL INFORMATIONAL RFC2630 Cryptographic Message Syntax R. Housley June 1999 ASCII 128599 60 encryption certificate key management This document describes the Cryptographic Message Syntax. This syntax is used to digitally sign, digest, authenticate, or encrypt arbitrary messages. [STANDARDS-TRACK] ietf-smime-cms-13 RFC3369 RFC3370 PROPOSED STANDARD PROPOSED STANDARD RFC2631 Diffie-Hellman Key Agreement Method E. Rescorla June 1999 ASCII 25932 13 encryption management certificate This document standardizes one particular Diffie-Hellman variant, based on the ANSI X9.42 draft, developed by the ANSI X9F1 working group. [STANDARDS-TRACK] ietf-smime-x942-07 PROPOSED STANDARD PROPOSED STANDARD RFC2632 S/MIME Version 3 Certificate Handling B. Ramsdell Editor June 1999 ASCII 27925 13 encryption certificate multipurpose internet mail extensions secure S/MIME (Secure/Multipurpose Internet Mail Extensions), provides a method to send and receive secure MIME messages. Before using a public key to provide security services, the S/MIME agent MUST certify that the public key is valid. S/MIME agents MUST use PKIX certificates to validate public keys as described in the Internet X.509 Public Key Infrastructure (PKIX) Certificate and CRL Profile. [STANDARDS-TRACK] ietf-smime-cert-08 RFC3850 PROPOSED STANDARD PROPOSED STANDARD RFC2633 S/MIME Version 3 Message Specification B. Ramsdell Editor June 1999 ASCII 67870 32 secure multipurpose internet mail extensions encryption This document describes a protocol for adding cryptographic signature and encryption services to MIME data. [STANDARDS-TRACK] ietf-smime-msg-08 RFC3851 PROPOSED STANDARD PROPOSED STANDARD RFC2634 Enhanced Security Services for S/MIME P. Hoffman Editor June 1999 ASCII 131153 58 secure multipurpose internet mail extensions encryption This document describes four optional security service extensions for S/MIME. [STANDARDS-TRACK] ietf-smime-ess-12 PROPOSED STANDARD PROPOSED STANDARD RFC2635 DON'T SPEW A Set of Guidelines for Mass Unsolicited Mailings and Postings (spam*) S. Hambridge A. Lunde June 1999 ASCII 44669 18 electronic mail email users administrators managers This document explains why mass unsolicited electronic mail messages are harmful in the Internetworking community. This memo provides information for the Internet community. ietf-run-spew-08 FYI0035 INFORMATIONAL INFORMATIONAL RFC2636 Wireless Device Configuration (OTASP/OTAPA) via ACAP R. Gellens July 1999 ASCII 65288 29 PS 1120860 PDF 173655 over-the-air ota application configuration access protocol This paper describes a viable and attractive means to provide OTASP/OTAPA via IS-707, using the ACAP protocol. This memo provides information for the Internet community. RFC2604 INFORMATIONAL INFORMATIONAL RFC2637 Point-to-Point Tunneling Protocol K. Hamzeh G. Pall W. Verthein J. Taarud W. Little G. Zorn July 1999 ASCII 132565 57 IP tunnel encapsulation This document specifies a protocol which allows the Point to Point Protocol (PPP) to be tunneled through an IP network. This memo provides information for the Internet community. ietf-pppext-pptp-10 INFORMATIONAL INFORMATIONAL RFC2638 A Two-bit Differentiated Services Architecture for the Internet K. Nichols V. Jacobson L. Zhang July 1999 ASCII 72785 26 PS 1610846 PDF 315195 IP internet protocol header packets This document presents a differentiated services architecture for the internet. This memo provides information for the Internet community. nichols-diff-svc-arch-02 INFORMATIONAL INFORMATIONAL RFC2639 Internet Printing Protocol/1.0: Implementer's Guide T. Hastings C. Manros July 1999 ASCII 145086 64 IPP client object This document contains information that supplements the IPP Model and Semantics and the IPP Transport and Encoding documents. It is intended to help implementers understand IPP/1.0 and some of the considerations that may assist them in the design of their client and/or IPP object implementations. This memo provides information for the Internet community. ietf-ipp-implementers-guide-01 RFC3196 INFORMATIONAL INFORMATIONAL RFC2640 Internationalization of the File Transfer Protocol B. Curtin July 1999 ASCII 57204 27 ftp character sets languages This document addresses the internationalization (I18n) of FTP, which includes supporting the multiple character sets and languages found throughout the Internet community. This is achieved by extending the FTP specification and giving recommendations for proper internationalization support. [STANDARDS-TRACK] ietf-ftpext-intl-ftp-06 RFC0959 PROPOSED STANDARD PROPOSED STANDARD RFC2641 Cabletron's VlanHello Protocol Specification Version 4 D. Hamilton D. Ruffen August 1999 ASCII 34686 17 ISMP inter switch message protocol switches The VlanHello protocol is part of the InterSwitch Message Protocol (ISMP) which provides interswitch communication between switches running Cabletron's SecureFast VLAN (SFVLAN) product. Switches use the VlanHello protocol to discover their neighboring switches and establish the topology of the switch fabric. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2642 Cabletron's VLS Protocol Specification L. Kane August 1999 ASCII 204347 95 Virtual LAN link ISMP inter switch message routing VLSP provides support for equal-cost multipath routing, and recalculates routes quickly in the face of topological changes, utilizing a minimum of routing protocol traffic. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2643 Cabletron's SecureFast VLAN Operational Model D. Ruffen T. Len J. Yanacek August 1999 ASCII 121786 60 SFVLAN switching data packets vitrual LANs Cabletron's SecureFast VLAN (SFVLAN) product implements a distributed connection-oriented switching protocol that provides fast forwarding of data packets at the MAC layer. The product uses the concept of virtual LANs (VLANs) to determine the validity of call connection requests and to scope the broadcast of certain flooded messages. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2644 Changing the Default for Directed Broadcasts in Routers D. Senie August 1999 ASCII 6820 4 smurf amplifiers denial of service 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. This memo provides information for the Internet community. senie-directed-broadcast-03 RFC1812 BCP0034 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2645 ON-DEMAND MAIL RELAY (ODMR) SMTP with Dynamic IP Addresses R. Gellens August 1999 ASCII 16302 9 ODMR-SMTP simple mail transfer protocol internet This memo proposes a new service, On-Demand Mail Relay (ODMR), which is a profile of SMTP, providing for a secure, extensible, easy to implement approach to the problem. [STANDARDS-TRACK] gellens-on-demand-07 PROPOSED STANDARD PROPOSED STANDARD RFC2646 The Text/Plain Format Parameter R. Gellens Editor August 1999 ASCII 29175 14 media type mime multipurpose internet mail extension This memo proposes a new parameter to be used with Text/Plain, and, in the presence of this parameter, the use of trailing whitespace to indicate flowed lines. This results in an encoding which appears as normal Text/Plain in older implementations, since it is in fact normal Text/Plain. [STANDARDS-TRACK] gellens-format-06 RFC3676 RFC2046 PROPOSED STANDARD PROPOSED STANDARD RFC2647 Benchmarking Terminology for Firewall Performance D. Newman August 1999 ASCII 45374 26 routers switches measurement This document defines terms used in measuring the performance of firewalls. It extends the terminology already used for benchmarking routers and switches with definitions specific to firewalls. [STANDARDS-TRACK] ietf-bmwg-secperf-08 INFORMATIONAL INFORMATIONAL RFC2648 A URN Namespace for IETF Documents R. Moats August 1999 ASCII 46826 30 uniform resource names internet engineering task force This document proposes the "ietf" namespace, which consists of the RFC family of documents (RFCs, STDs, FYIs, and BCPs) developed by the IETF and published by the RFC Editor and the minutes of working groups (WG) and birds of a feather (BOF) meetings that occur during IETF conferences. [STANDARDS-TRACK] ietf-urn-ietf-09 INFORMATIONAL INFORMATIONAL RFC2649 An LDAP Control and Schema for Holding Operation Signatures B. Greenblatt P. Richard August 1999 ASCII 20470 10 lightweight directory access protocol client server This document describes an LDAP message control which allows for the retrieval of digitally signed information. This document defines an LDAP v3 based mechanism for signing directory operations in order to create a secure journal of changes that have been made to each directory entry. This memo defines an Experimental Protocol for the Internet community. ietf-ldapext-sigops-04 EXPERIMENTAL EXPERIMENTAL RFC2650 Using RPSL in Practice D. Meyer J. Schmitz C. Orange M. Prior C. Alaettinoglu August 1999 ASCII 55272 26 routing policy specification language IRR internet routing registry configurations This document is a tutorial on using the Routing Policy Specification Language (RPSL) to describe routing policies in the Internet Routing Registry (IRR). This memo provides information for the Internet community. ietf-rps-appl-rpsl-06 INFORMATIONAL INFORMATIONAL RFC2651 The Architecture of the Common Indexing Protocol (CIP) J. Allen M. Mealling August 1999 ASCII 41933 19 CIP query routing database servers This document describes the CIP framework, including its architecture and the protocol specifics of exchanging indices. [STANDARDS-TRACK] ietf-find-cip-arch-02 PROPOSED STANDARD PROPOSED STANDARD RFC2652 MIME Object Definitions for the Common Indexing Protocol (CIP) J. Allen M. Mealling August 1999 ASCII 42464 22 multipurpose internet mail extensions database This document describes the definitions of those objects as well as the methods and requirements needed to define a new index type. [STANDARDS-TRACK] ietf-find-cip-mime-03 PROPOSED STANDARD PROPOSED STANDARD RFC2653 CIP Transport Protocols J. Allen P. Leach R. Hedberg August 1999 ASCII 22999 11 common indexing message formats This document specifies three protocols for transporting CIP requests, responses and index objects, utilizing TCP, mail, and HTTP. [STANDARDS-TRACK] ietf-find-cip-trans-01 PROPOSED STANDARD PROPOSED STANDARD RFC2654 A Tagged Index Object for use in the Common Indexing Protocol R. Hedberg B. Greenblatt R. Moats M. Wahl August 1999 ASCII 46739 24 CIP information servers database This document defines a mechanism by which information servers can exchange indices of information from their databases by making use of the Common Indexing Protocol (CIP). This document defines the structure of the index information being exchanged, as well as the appropriate meanings for the headers that are defined in the Common Indexing Protocol. This memo defines an Experimental Protocol for the Internet community. ietf-find-cip-tagged-07 EXPERIMENTAL EXPERIMENTAL RFC2655 CIP Index Object Format for SOIF Objects T. Hardie M. Bowman D. Hardy M. Schwartz D. Wessels August 1999 ASCII 34285 17 summary object interchange format common indexing protocol This document describes SOIF, the Summary Object Interchange Format, as an index object type in the context of the CIP framework. This memo defines an Experimental Protocol for the Internet community. ietf-find-cip-soif-02 EXPERIMENTAL EXPERIMENTAL RFC2656 Registration Procedures for SOIF Template Types T. Hardie August 1999 ASCII 17409 9 summary object interchange format stream The registration procedure described in this document is specific to SOIF template types. This memo defines an Experimental Protocol for the Internet community. ietf-find-soif-registry-00 EXPERIMENTAL EXPERIMENTAL RFC2657 LDAPv2 Client vs. the Index Mesh R. Hedberg August 1999 ASCII 19251 12 lightweight directory access protocol CIP common indexing LDAPv2 clients as implemented according to RFC 1777 have no notion on referral. The integration between such a client and an Index Mesh, as defined by the Common Indexing Protocol, heavily depends on referrals and therefore needs to be handled in a special way. This document defines one possible way of doing this. This memo defines an Experimental Protocol for the Internet community. ietf-find-cip-ldapv2-02 EXPERIMENTAL EXPERIMENTAL RFC2658 RTP Payload Format for PureVoice(tm) Audio K. McKay August 1999 ASCII 21895 10 real-time transport protocol packet end-to-end This document describes the RTP payload format for PureVoice(tm) Audio. [STANDARDS-TRACK] mckay-qcelp-03 PROPOSED STANDARD PROPOSED STANDARD RFC2659 Security Extensions For HTML E. Rescorla A. Schiffman August 1999 ASCII 8134 4 hyper-text markup language cryptology This memo describes a syntax for embedding S-HTTP negotiation parameters in HTML documents. This memo defines an Experimental Protocol for the Internet community. ietf-wts-shtml-05 EXPERIMENTAL EXPERIMENTAL RFC2660 The Secure HyperText Transfer Protocol E. Rescorla A. Schiffman August 1999 ASCII 95645 45 WWW world wide web http authentication This memo describes a syntax for securing messages sent using the Hypertext Transfer Protocol (HTTP), which forms the basis for the World Wide Web. This memo defines an Experimental Protocol for the Internet community. ietf-wts-shttp-06 EXPERIMENTAL EXPERIMENTAL RFC2661 Layer Two Tunneling Protocol "L2TP" W. Townsley A. Valencia A. Rubens G. Pall G. Zorn B. Palter August 1999 ASCII 168150 80 L2TP ppp point-to-point protocol packets This document describes the Layer Two Tunneling Protocol (L2TP). [STANDARDS-TRACK] ietf-pppext-l2tp-16 PROPOSED STANDARD PROPOSED STANDARD RFC2662 Definitions of Managed Objects for the ADSL Lines G. Bathrick F. Ly August 1999 ASCII 247122 115 MIB management information base This document defines a standard SNMP MIB for ADSL lines based on the ADSL Forum standard data model. [STANDARDS-TRACK] ietf-adslmib-adsllinemib-09 PROPOSED STANDARD PROPOSED STANDARD RFC2663 IP Network Address Translator (NAT) Terminology and Considerations P. Srisuresh M. Holdrege August 1999 ASCII 72265 30 network address translator IP internet protocol addresses This document attempts to describe the operation of NAT devices and the associated considerations in general, and to define the terminology used to identify various flavors of NAT. This memo provides information for the Internet community. ietf-nat-terminology-03 INFORMATIONAL INFORMATIONAL RFC2664 FYI on Questions and Answers - Answers to Commonly Asked "New Internet User" Questions R. Plzak A. Wells E. Krol August 1999 ASCII 23640 11 documentation help information FAQ This memo provides an overview to the new Internet User. The intended audience is the common Internet user of today, thus it attempts to provide a more consumer oriented approach to the Internet rather than going into any depth about a topic. This memo provides information for the Internet community. ietf-uswg-fyi4-bis-01 RFC1594 FYI0004 INFORMATIONAL INFORMATIONAL RFC2665 Definitions of Managed Objects for the Ethernet-like Interface Types J. Flick J. Johnson August 1999 ASCII 110038 47 MIB management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK] ietf-hubmib-etherif-mib-v2-04 RFC2358 RFC3635 PROPOSED STANDARD PROPOSED STANDARD RFC2666 Definitions of Object Identifiers for Identifying Ethernet Chip Sets J. Flick August 1999 ASCII 37699 18 mib management information base This memo defines OBJECT IDENTIFIER values for use with network management protocols in the Internet community. This memo provides information for the Internet community. ietf-hubmib-ether-chipsets-02 INFORMATIONAL INFORMATIONAL RFC2667 IP Tunnel MIB D. Thaler August 1999 ASCII 32770 16 internet protocol management information base This memo defines a Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing tunnels of any type over IPv4 networks. [STANDARDS-TRACK] ietf-ifmib-tunnel-mib-06 PROPOSED STANDARD PROPOSED STANDARD RFC2668 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) A. Smith J. Flick K. de Graaf D. Romascanu D. McMaster K. McCloghrie S. Roberts August 1999 ASCII 121843 56 MAU-MIB management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK] ietf-hubmib-mau-mib-v2-04 RFC2239 RFC3636 PROPOSED STANDARD PROPOSED STANDARD RFC2669 DOCSIS Cable Device MIB Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems M. St. Johns Editor August 1999 ASCII 112880 55 management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP-based management of DOCSIS 1.0 compliant Cable Modems and Cable Modem Termination Systems. [STANDARDS-TRACK] ietf-ipcdn-rf-interface-mib-07 PROPOSED STANDARD PROPOSED STANDARD RFC2670 Radio Frequency (RF) Interface Management Information Base for MCNS/DOCSIS compliant RF interfaces M. St. Johns Editor August 1999 ASCII 141077 72 MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP-based management of MCNS/DOCSIS compliant Radio Frequency (RF) interfaces. [STANDARDS-TRACK] ietf-ipcdn-cable-device-mib-08 PROPOSED STANDARD PROPOSED STANDARD RFC2671 Extension Mechanisms for DNS (EDNS0) P. Vixie August 1999 ASCII 15257 7 EDNS0 domain name system resource records opt The Domain Name System's wire protocol includes a number of fixed fields whose range has been or soon will be exhausted and does not allow clients to advertise their capabilities to servers. This document describes backward compatible mechanisms for allowing the protocol to grow. [STANDARDS-TRACK] ietf-dnsind-edns0-02 PROPOSED STANDARD PROPOSED STANDARD RFC2672 Non-Terminal DNS Name Redirection M. Crawford August 1999 ASCII 18321 9 domain name system dname resource records This document defines a new DNS Resource Record called "DNAME", which provides the capability to map an entire subtree of the DNS name space to another domain. [STANDARDS-TRACK] ietf-dnsind-dname-03 PROPOSED STANDARD PROPOSED STANDARD RFC2673 Binary Labels in the Domain Name System M. Crawford August 1999 ASCII 12379 7 DNS data This document defines a "Bit-String Label" which may appear within domain names. This new label type compactly represents a sequence of "One-Bit Labels" and enables resource records to be stored at any bit- boundary in a binary-named section of the domain name tree. [STANDARDS-TRACK] ietf-dnsind-binary-labels-05 RFC3363 RFC3364 EXPERIMENTAL PROPOSED STANDARD RFC2674 Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions E. Bell A. Smith P. Langille A. Rijhsinghani K. McCloghrie August 1999 ASCII 159971 86 MIB management information base local area network This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. [STANDARDS-TRACK] ietf-bridge-bridgemib-06 PROPOSED STANDARD PROPOSED STANDARD RFC2675 IPv6 Jumbograms D. Borman S. Deering R. Hinden August 1999 ASCII 17320 9 internet protocol packet payload link This document describes the IPv6 Jumbo Payload option, which provides the means of specifying such large payload lengths. It also describes the changes needed to TCP and UDP to make use of jumbograms. [STANDARDS-TRACK] ietf-ipngwg-jumbograms-01 RFC2147 PROPOSED STANDARD PROPOSED STANDARD RFC2676 QoS Routing Mechanisms and OSPF Extensions G. Apostolopoulos S. Kama D. Williams R. Guerin A. Orda T. Przygienda August 1999 ASCII 124563 50 quality of service open shortest path first routing This memo describes extensions to the OSPF protocol to support QoS routes. The focus of this document is on the algorithms used to compute QoS routes and on the necessary modifications to OSPF to support this function, e.g., the information needed, its format, how it is distributed, and how it is used by the QoS path selection process. This memo defines an Experimental Protocol for the Internet community. guerin-qos-routing-ospf-05 EXPERIMENTAL EXPERIMENTAL RFC2677 Definitions of Managed Objects for the NBMA Next Hop Resolution Protocol (NHRP) M. Greene J. Cucchiara J. Luciani August 1999 ASCII 129699 67 NHRP-MIB management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK] ietf-ion-nhrp-mib-09 PROPOSED STANDARD PROPOSED STANDARD RFC2678 IPPM Metrics for Measuring Connectivity J. Mahdavi V. Paxson September 1999 ASCII 18087 10 IPPM-MET internet protocol performance metrics This memo defines a series of metrics for connectivity between a pair of Internet hosts. [STANDARDS-TRACK] RFC2498 PROPOSED STANDARD PROPOSED STANDARD RFC2679 A One-way Delay Metric for IPPM G. Almes S. Kalidindi M. Zekauskas September 1999 ASCII 43542 20 internet protocol performance metrics packets This memo defines a metric for one-way delay of packets across Internet paths. [STANDARDS-TRACK] ietf-ippm-delay-07 PROPOSED STANDARD PROPOSED STANDARD RFC2680 A One-way Packet Loss Metric for IPPM G. Almes S. Kalidindi M. Zekauskas September 1999 ASCII 32266 15 internet protocol performance metrics This memo defines a metric for one-way packet loss across Internet paths. [STANDARDS-TRACK] ietf-ippm-loss-07 PROPOSED STANDARD PROPOSED STANDARD RFC2681 A Round-trip Delay Metric for IPPM G. Almes S. Kalidindi M. Zekauskas September 1999 ASCII 44357 20 internet protocol performance metrics packets This memo defines a metric for round-trip delay of packets across Internet paths. [STANDARDS-TRACK] ietf-ippm-rt-delay-01 PROPOSED STANDARD PROPOSED STANDARD RFC2682 Performance Issues in VC-Merge Capable ATM LSRs I. Widjaja A. Elwalid September 1999 ASCII 29491 12 asynchronous transfer mode routing This document investigates the impact of VC merging on the additional buffer required for the reassembly buffers and other buffers. This memo provides information for the Internet community. widjaja-mpls-vc-merge-01 INFORMATIONAL INFORMATIONAL RFC2683 IMAP4 Implementation Recommendations B. Leiba September 1999 ASCII 56300 23 internet message access protocol clients servers The IMAP4 specification describes a rich protocol for use in building clients and servers for storage, retrieval, and manipulation of electronic mail. Because the protocol is so rich and has so many implementation choices, there are often trade-offs that must be made and issues that must be considered when designing such clients and servers. This document attempts to outline these issues and to make recommendations in order to make the end products as interoperable as possible. This memo provides information for the Internet community. leiba-imap-implement-guide-10 INFORMATIONAL INFORMATIONAL RFC2684 Multiprotocol Encapsulation over ATM Adaptation Layer 5 D. Grossman J. Heinanen September 1999 ASCII 51390 23 asynchronous,transfer mode multiplexing This memo replaces RFC 1483. It describes two encapsulations methods for carrying network interconnect traffic over AAL type 5 over ATM. [STANDARDS-TRACK] ietf-ion-multiprotocol-atm-04 RFC1483 PROPOSED STANDARD PROPOSED STANDARD RFC2685 Virtual Private Networks Identifier B. Fox B. Gleeson September 1999 ASCII 11168 6 VPNI IP internet protocol VPN This document proposes a format for a globally unique VPN identifier. [STANDARDS-TRACK] ietf-ion-vpn-id-02 PROPOSED STANDARD PROPOSED STANDARD RFC2686 The Multi-Class Extension to Multi-Link PPP C. Bormann September 1999 ASCII 24192 11 point-to-point protocol encapsulation This document proposes the fragment-oriented solution for the real-time encapsulation format part of the architecture. [STANDARDS-TRACK] ietf-issll-isslow-mcml-06 PROPOSED STANDARD PROPOSED STANDARD RFC2687 PPP in a Real-time Oriented HDLC-like Framing C. Bormann September 1999 ASCII 28699 13 point-to-point protocol encapsulation high-level data link control This document proposes the suspend/resume-oriented solution for the real-time encapsulation format part of the architecture. [STANDARDS- TRACK] ietf-issll-isslow-rtf-05 PROPOSED STANDARD PROPOSED STANDARD RFC2688 Integrated Services Mappings for Low Speed Networks S. Jackowski D. Putzolu E. Crawley B. Davie September 1999 ASCII 36685 16 controlled load guaranteed services This document defines the service mappings of the IETF Integrated Services for low-bitrate links, specifically the controlled load and guaranteed services. [STANDARDS-TRACK] ietf-issll-isslow-svcmap-08 PROPOSED STANDARD PROPOSED STANDARD RFC2689 Providing Integrated Services over Low-bitrate Links C. Bormann September 1999 ASCII 34345 14 asynchronous synchronous real-time This document describes an architecture for providing integrated services over low-bitrate links, such as modem lines, ISDN B-channels, and sub-T1 links. This memo provides information for the Internet community. ietf-issll-isslow-06 INFORMATIONAL INFORMATIONAL RFC2690 A Proposal for an MOU-Based ICANN Protocol Support Organization S. Bradner September 1999 ASCII 14221 8 pso memorandum of understanding internet corporation for assigned names and numbers This is a copy of the proposal for an MOU-based Protocol Supporting Organization that was submitted to ICANN on April 23, 1999. This memo provides information for the Internet community. ietf-poisson-pso-mou-01 INFORMATIONAL INFORMATIONAL RFC2691 A Memorandum of Understanding for an ICANN Protocol Support Organization S. Bradner September 1999 ASCII 18940 9 mou pso internet corporation for assigned names and numbers This is the text of the Memorandum of Understanding (MoU) that was signed by ICANN, the IETF, the ITU-T, W3C and ETSI on July 14, 1999 in Oslo. This MoU creates the Protocol Support Organization (PSO) within the Internet Corporation for Assigned Names and Numbers (ICANN). This memo provides information for the Internet community. ietf-poisson-mou-pso-00 INFORMATIONAL INFORMATIONAL RFC2692 SPKI Requirements C. Ellison September 1999 ASCII 29569 14 SPKI simple public key infrastructure authentication The SPKI Working Group first established a list of things one might want to do with certificates (attached at the end of this document), and then summarized that list of desires into requirements. This document presents that summary of requirements. This memo defines an Experimental Protocol for the Internet community. ietf-spki-cert-req-03 EXPERIMENTAL EXPERIMENTAL RFC2693 SPKI Certificate Theory C. Ellison B. Frantz B. Lampson R. Rivest B. Thomas T. Ylonen September 1999 ASCII 96699 43 SPKI simple public key infrastructure authentication This document gives the theory behind SPKI certificates and ACLs without going into technical detail about those structures or their uses. This memo defines an Experimental Protocol for the Internet community. ietf-spki-cert-theory-05 EXPERIMENTAL EXPERIMENTAL RFC2694 DNS extensions to Network Address Translators (DNS_ALG) P. Srisuresh G. Tsirtsis P. Akkiraju A. Heffernan September 1999 ASCII 67720 29 domain name system NATs mapping This document identifies the need for DNS extensions to NATs and outlines how a DNS Application Level Gateway (DNS_ALG) can meet the need. This memo provides information for the Internet community. ietf-nat-dns-alg-04 INFORMATIONAL INFORMATIONAL RFC2695 Authentication Mechanisms for ONC RPC A. Chiu September 1999 ASCII 39286 18 remote procedure call open network computing This document describes two authentication mechanisms created by Sun Microsystems that are commonly used in conjunction with the ONC Remote Procedure Call (ONC RPC Version 2) protocol. This memo provides information for the Internet community. ietf-oncrpc-auth-06 INFORMATIONAL INFORMATIONAL RFC2696 LDAP Control Extension for Simple Paged Results Manipulation C. Weider A. Herron A. Anantha T. Howes September 1999 ASCII 12809 7 lightweight directory access protocol client server This document describes an LDAPv3 control extension for simple paging of search results. This memo provides information for the Internet community. ietf-asid-ldapv3-simplepaged-03 INFORMATIONAL INFORMATIONAL RFC2697 A Single Rate Three Color Marker J. Heinanen R. Guerin September 1999 ASCII 10309 6 srtcm stream ip internet protocol packet This document defines a Single Rate Three Color Marker (srTCM), which can be used as component in a Diffserv traffic conditioner. This memo provides information for the Internet community. heinanen-diffserv-srtcm-01 INFORMATIONAL INFORMATIONAL RFC2698 A Two Rate Three Color Marker J. Heinanen R. Guerin September 1999 ASCII 9368 5 trTCM stream ip internet protocol packet This document defines a Two Rate Three Color Marker (trTCM), which can be used as a component in a Diffserv traffic conditioner. This memo provides information for the Internet community. heinanen-diffserv-trtcm-01 INFORMATIONAL INFORMATIONAL RFC2699 Request for Comments Summary RFC Numbers 2600-2699 S. Ginoza May 2000 ASCII 42462 22 INFORMATIONAL INFORMATIONAL RFC2700 Internet Official Protocol Standards J. Reynolds R. Braden August 2000 ASCII 90213 32 This memo describes the current state of standardization of protocols used in the Internet as determined by the Internet Engineering Task Force (IETF). [STANDARDS TRACK] RFC2600 RFC2800 HISTORIC STANDARD RFC2701 Nortel Networks Multi-link Multi-node PPP Bundle Discovery Protocol G. Malkin September 1999 ASCII 17571 9 point-to-point POP presence RAS remote access server This document specifies a standard way for Multi-link PPP to operate across multiple nodes. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2702 Requirements for Traffic Engineering Over MPLS D. Awduche J. Malcolm J. Agogbua M. O'Dell J. McManus September 1999 ASCII 68386 29 multiprotocol label switching This document presents a set of requirements for Traffic Engineering over Multiprotocol Label Switching (MPLS). It identifies the functional capabilities required to implement policies that facilitate efficient and reliable network operations in an MPLS domain. This memo provides information for the Internet community. ietf-mpls-traffic-eng-01 INFORMATIONAL INFORMATIONAL RFC2703 Protocol-independent Content Negotiation Framework G. Klyne September 1999 ASCII 42071 20 feature resource media syntax This memo sets out terminology, an abstract framework and goals for protocol-independent content negotiation, and identifies some technical issues which may need to be addressed. This memo provides information for the Internet community. ietf-conneg-requirements-02 INFORMATIONAL INFORMATIONAL RFC2704 The KeyNote Trust-Management System Version 2 M. Blaze J. Feigenbaum J. Ioannidis A. Keromytis September 1999 ASCII 79998 37 security policy maker system credentials This memo describes version 2 of the KeyNote trust-management system.It specifies the syntax and semantics of KeyNote `assertions', describes `action attribute' processing, and outlines the application architecture into which a KeyNote implementation can be fit. This memo provides information for the Internet community. blaze-ietf-trustmgt-keynote-02 INFORMATIONAL INFORMATIONAL RFC2705 Media Gateway Control Protocol (MGCP) Version 1.0 M. Arango A. Dugan I. Elliott C. Huitema S. Pickett October 1999 ASCII 304056 134 voice IP internet VoIP This document describes an application programming interface and a corresponding protocol (MGCP) for controlling Voice over IP (VoIP) Gateways from external call control elements. MGCP assumes a call control architecture where the call control "intelligence" is outside the gateways and handled by external call control elements. This memo provides information for the Internet community. huitema-megaco-mgcp-v1-00 RFC3435 RFC3660 INFORMATIONAL INFORMATIONAL RFC2706 ECML v1: Field Names for E-Commerce D. Eastlake 3rd T. Goldstein October 1999 ASCII 26135 13 electronic commerce modeling language merchant site. web A standard set of information fields is defined as the first version of an Electronic Commerce Modeling Language (ECML) so that this task can be more easily automated, for example by wallet software that could fill in fields. This memo provides information for the Internet community. eastlake-ecom-fields-01 RFC3106 INFORMATIONAL INFORMATIONAL RFC2707 Job Monitoring MIB - V1.0 R. Bergman T. Hastings S. Isaacson H. Lewis November 1999 ASCII 255685 114 management information base This document provides a printer industry standard SNMP MIB for (1) monitoring the status and progress of print jobs (2) obtaining resource requirements before a job is processed, (3) monitoring resource consumption while a job is being processed and (4) collecting resource accounting data after the completion of a job. This memo provides information for the Internet community. ietf-printmib-job-monitor-08 INFORMATIONAL INFORMATIONAL RFC2708 Job Submission Protocol Mapping Recommendations for the Job Monitoring MIB R. Bergman November 1999 ASCII 57489 26 management information base This document defines the recommended mapping for many currently popular Job submission protocols to objects and attributes in the Job Monitoring MIB. This memo provides information for the Internet community. ietf-printmib-job-protomap-04 INFORMATIONAL INFORMATIONAL RFC2709 Security Model with Tunnel-mode IPsec for NAT Domains P. Srisuresh October 1999 ASCII 24552 11 internet protocol network address translator This document describes a security model by which tunnel-mode IPsec security can be architected on NAT devices. This memo provides information for the Internet community. ietf-nat-security-02 INFORMATIONAL INFORMATIONAL RFC2710 Multicast Listener Discovery (MLD) for IPv6 S. Deering W. Fenner B. Haberman October 1999 ASCII 46838 22 MLD-IPv6 internet protocol routher packets This document specifies the protocol used by an IPv6 router to discover the presence of multicast listeners (that is, nodes wishing to receive multicast packets) on its directly attached links, and to discover specifically which multicast addresses are of interest to those neighboring nodes. [STANDARDS TRACK] ietf-ipngwg-mld-02 RFC3590 RFC3810 PROPOSED STANDARD PROPOSED STANDARD RFC2711 IPv6 Router Alert Option C. Partridge A. Jackson October 1999 ASCII 11973 6 internet protocol datagram routher hop-by-hop This memo describes a new IPv6 Hop-by-Hop Option type that alerts transit routers to more closely examine the contents of an IP datagram. [STANDARDS TRACK] ietf-ipngwg-ipv6router-alert-06 PROPOSED STANDARD PROPOSED STANDARD RFC2712 Addition of Kerberos Cipher Suites to Transport Layer Security (TLS) A. Medvinsky M. Hur October 1999 ASCII 13763 7 TLS authentication cryptography This document proposes the addition of new cipher suites to the TLS protocol to support Kerberos-based authentication. [STANDARDS TRACK] ietf-tls-kerb-cipher-suites-04 PROPOSED STANDARD PROPOSED STANDARD RFC2713 Schema for Representing Java(tm) Objects in an LDAP Directory V. Ryan S. Seligman R. Lee October 1999 ASCII 40745 21 lightweight directory access protocol This document defines the schema for representing Java(tm) objects in an LDAP directory. This memo provides information for the Internet community. ryan-java-schema-02 INFORMATIONAL INFORMATIONAL RFC2714 Schema for Representing CORBA Object References in an LDAP Directory V. Ryan R. Lee S. Seligman October 1999 ASCII 14709 10 lightweight directory access protocol This document defines the schema for representing CORBA object references in an LDAP directory. This memo provides information for the Internet community. ryan-corba-schema-01 INFORMATIONAL INFORMATIONAL RFC2715 Interoperability Rules for Multicast Routing Protocols D. Thaler October 1999 ASCII 49638 22 border router MBRs autonomous The rules described in this document will allow efficient interoperation among multiple independent multicast routing domains. This memo provides information for the Internet community. thaler-multicast-interop-03 INFORMATIONAL INFORMATIONAL RFC2716 PPP EAP TLS Authentication Protocol B. Aboba D. Simon October 1999 ASCII 50108 24 point-to-point link control compression extensible transport level security The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links.The Extensible Authentication Protocol (EAP) is a PPP extension that provides support for additional authentication methods within PPP. This memo defines an Experimental Protocol for the Internet community. ietf-pppext-eaptls-06 EXPERIMENTAL EXPERIMENTAL RFC2717 Registration Procedures for URL Scheme Names R. Petke I. King November 1999 ASCII 19780 10 uniform resource locator syntax semantics This document defines the process by which new URL scheme names are registered. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-urlreg-procedures-08 BCP0035 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2718 Guidelines for new URL Schemes L. Masinter H. Alvestrand D. Zigmond R. Petke November 1999 ASCII 19208 10 uniform resource locator syntax semantics This document provides guidelines for the definition of new URL schemes. This memo provides information for the Internet community. ietf-urlreg-guide-05 INFORMATIONAL INFORMATIONAL RFC2719 Framework Architecture for Signaling Transport L. Ong I. Rytina M. Garcia H. Schwarzbauer L. Coene H. Lin I. Juhasz M. Holdrege C. Sharp October 1999 ASCII 48646 24 IP Internet Protocol gateway media circuit This document defines an architecture framework and functional requirements for transport of signaling information over IP. This memo provides information for the Internet community. ietf-sigtran-framework-arch-03 INFORMATIONAL INFORMATIONAL RFC2720 Traffic Flow Measurement: Meter MIB N. Brownlee October 1999 ASCII 103781 55 management information base This document defines a Management Information Base (MIB) for use in controlling an RTFM Traffic Meter, in particular for specifying the flows to be measured. It also provides an efficient mechanism for retrieving flow data from the meter using SNMP. Security issues concerning the operation of traffic meters are summarised. [STANDARDS TRACK] ietf-rtfm-meter-mib-11 RFC2064 PROPOSED STANDARD PROPOSED STANDARD RFC2721 RTFM: Applicability Statement N. Brownlee October 1999 ASCII 21200 10 real-time traffic flow measurement This document provides an overview covering all aspects of Realtime Traffic Flow Measurement, including its area of applicability and its limitations. This memo provides information for the Internet community. ietf-rtfm-applicability-statement INFORMATIONAL INFORMATIONAL RFC2722 Traffic Flow Measurement: Architecture N. Brownlee C. Mills G. Ruth October 1999 ASCII 114064 48 network meters data This document provides a general framework for describing network traffic flows, presents an architecture for traffic flow measurement and reporting, discusses how this relates to an overall network traffic flow architecture and indicates how it can be used within the Internet. This memo provides information for the Internet community. ietf-rtfm-architecture-08 RFC2063 INFORMATIONAL INFORMATIONAL RFC2723 SRL: A Language for Describing Traffic Flows and Specifying Actions for Flow Groups N. Brownlee October 1999 ASCII 44406 22 simple ruleset RTFM real-time network measurement This document describes a language for specifying rulesets, i.e. configuration files which may be loaded into a traffic flow meter so as to specify which traffic flows are measured by the meter, and the information it will store for each flow. This memo provides information for the Internet community. ietf-rtfm-ruleset-language-07 INFORMATIONAL INFORMATIONAL RFC2724 RTFM: New Attributes for Traffic Flow Measurement S. Handelman S. Stibler N. Brownlee G. Ruth October 1999 ASCII 37951 18 real-time network This document discusses RTFM flows and the attributes which they can have, so as to provide a logical framework for extending the architecture by adding new attributes. This memo defines an Experimental Protocol for the Internet community. ietf-rtfm-new-traffic-flow-10 EXPERIMENTAL EXPERIMENTAL RFC2725 Routing Policy System Security C. Villamizar C. Alaettinoglu D. Meyer S. Murphy December 1999 ASCII 101649 41 RPSL database registry authentication The implementation and deployment of a routing policy system must maintain some degree of integrity to be of any operational use. This document addresses the need to assure integrity of the data by providing an authentication and authorization model. [STANDARDS TRACK] ietf-rps-auth-04 RFC4012 PROPOSED STANDARD PROPOSED STANDARD RFC2726 PGP Authentication for RIPE Database Updates J. Zsako December 1999 ASCII 22594 11 pretty good privacy security digital signatures This document presents the proposal for a stronger authentication method of the updates of the RIPE database based on digital signatures. [STANDARDS TRACK] ietf-rps-dbsec-pgp-authent-02 PROPOSED STANDARD PROPOSED STANDARD RFC2727 IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees J. Galvin February 2000 ASCII 33396 15 Internet Architecture Board Engineering Steering Group The process by which the members of the IAB and IESG are selected, confirmed, and recalled is specified. This document is a self- consistent, organized compilation of the process as it was known at the time of publication. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-poisson-nomcom-v2-01 RFC2282 RFC3777 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2728 The Transmission of IP Over the Vertical Blanking Interval of a Television Signal R. Panabaker S. Wegerif D. Zigmond November 1999 ASCII 49099 23 internet protocol IPVBI This document describes a method for broadcasting IP data in a unidirectional manner using the vertical blanking interval of television signals. [STANDARDS TRACK] ietf-ipvbi-nabts-05 PROPOSED STANDARD PROPOSED STANDARD RFC2729 Taxonomy of Communication Requirements for Large-scale Multicast Applications P. Bagnall R. Briscoe A. Poppitt December 1999 ASCII 53322 27 LSMA dynamic protocol mapping The intention of this memo is to define a classification system for the communication requirements of any large-scale multicast application (LSMA). This memo provides information for the Internet community. ietf-lsma-requirements-04 INFORMATIONAL INFORMATIONAL RFC2730 Multicast Address Dynamic Client Allocation Protocol (MADCAP) S. Hanna B. Patel M. Shah December 1999 ASCII 120341 53 MADCAP client server scope zone host This document defines a protocol, Multicast Address Dynamic Client Allocation Protocol (MADCAP), that allows hosts to request multicast addresses from multicast address allocation servers. [STANDARDS TRACK] ietf-malloc-madcap-07 PROPOSED STANDARD PROPOSED STANDARD RFC2731 Encoding Dublin Core Metadata in HTML J. Kunze December 1999 ASCII 42450 23 hypertext markup language xml extensible The Dublin Core is a small set of metadata elements for describing information resources. This document explains how these elements are expressed using the META and LINK tags of HTML. This memo provides information for the Internet community. kunze-dchtml-02 INFORMATIONAL INFORMATIONAL RFC2732 Format for Literal IPv6 Addresses in URL's R. Hinden B. Carpenter L. Masinter December 1999 ASCII 7984 5 Internet protocol uniform resource identifier www world wide web This document defines the format for literal IPv6 Addresses in URL's for implementation in World Wide Web browsers. [STANDARDS TRACK] ietf-ipngwg-url-literal-04 RFC3986 RFC2396 PROPOSED STANDARD PROPOSED STANDARD RFC2733 An RTP Payload Format for Generic Forward Error Correction J. Rosenberg H. Schulzrinne December 1999 ASCII 53120 26 FEC real-time protocol stream This document specifies a payload format for generic forward error correction of media encapsulated in RTP. [STANDARDS TRACK] ietf-avt-fec-08 PROPOSED STANDARD PROPOSED STANDARD RFC2734 IPv4 over IEEE 1394 P. Johansson December 1999 ASCII 69314 29 internet protocol datagrams packet encapsulation ARP address resolution multicast This document specifies how to use IEEE Std 1394-1995, Standard for a High Performance Serial Bus (and its supplements), for the transport of Internet Protocol Version 4 (IPv4) datagrams; it defines the necessary methods, data structures and codes for that purpose. [STANDARDS TRACK] ietf-ip1394-ipv4-19 PROPOSED STANDARD PROPOSED STANDARD RFC2735 NHRP Support for Virtual Private Networks B. Fox B. Petri December 1999 ASCII 26451 12 next hop resolution protocol VPN addresses The NBMA Next Hop Resolution Protocol (NHRP) is used to determine the NBMA subnetwork addresses of the "NBMA next hop" towards a public internetworking layer address. This document describes the enhancements necessary to enable NHRP to perform the same function for private internetworking layer addresses available within the framework of a Virtual Private Network (VPN) service on a shared NBMA network. [STANDARDS TRACK] ietf-ion-nhrp-vpn-03 PROPOSED STANDARD PROPOSED STANDARD RFC2736 Guidelines for Writers of RTP Payload Format Specifications M. Handley C. Perkins December 1999 ASCII 24143 10 real-time transport protocol data types audio video codecs This document provides general guidelines aimed at assisting the authors of RTP Payload Format specifications in deciding on good formats. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-avt-rtp-format-guidelines-04 BCP0036 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2737 Entity MIB (Version 2) K. McCloghrie A. Bierman December 1999 ASCII 125141 56 management information base SNMP simple network protocol This memo defines a portion of the Management Information Base (M for use with network management protocols in the Internet communi In particular, it describes managed objects used for managing multiple logical and physical entities managed by a single SNMP agent. [STANDARDS TRACK] ietf-entmib-v2-06 RFC2037 PROPOSED STANDARD PROPOSED STANDARD RFC2738 Corrections to "A Syntax for Describing Media Feature Sets" G. Klyne December 1999 ASCII 8353 5 FEC real-time protocol stream In RFC 2533, "A Syntax for Describing Media Feature Sets", an expression format is presented for describing media feature capabilities using simple media feature tags. This memo contains two corrections to that specification: one fixes an error in the formal syntax specification, and the other fixes an error in the rules for reducing feature comparison predicates. [STANDARDS TRACK] ietf-conneg-feature-syntax-er-00 RFC2533 PROPOSED STANDARD PROPOSED STANDARD RFC2739 Calendar Attributes for vCard and LDAP T. Small D. Hennessy F. Dawson January 2000 ASCII 25892 16 lightweight directory access protocol This memo defines three mechanisms for obtaining a URI to a user's calendar and free/busy time. [STANDARDS TRACK] ietf-calsch-locating-03 PROPOSED STANDARD PROPOSED STANDARD RFC2740 OSPF for IPv6 R. Coltun D. Ferguson J. Moy December 1999 ASCII 189810 80 internet protocol open shortest path first This document describes the modifications to OSPF to support version 6 of the Internet Protocol (IPv6). [STANDARDS TRACK] ietf-ispf-ospfv6-08 PROPOSED STANDARD PROPOSED STANDARD RFC2741 Agent Extensibility (AgentX) Protocol Version 1 M. Daniele B. Wijnen M. Ellison D. Francisco January 2000 ASCII 199867 91 SNMP simple network management This memo defines a standardized framework for extensible SNMP agents. [STANDARDS TRACK] ietf-agentx-rfc-update-03 RFC2257 DRAFT STANDARD PROPOSED STANDARD RFC2742 Definitions of Managed Objects for Extensible SNMP Agents L. Heintz S. Gudur M. Ellison January 2000 ASCII 36644 20 SNMP management information base simple network protocol 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 managing SNMP agents that use the Agent Extensibility (AgentX) Protocol. [STANDARDS TRACK] ietf-agentx-mib-05 DRAFT STANDARD PROPOSED STANDARD RFC2743 Generic Security Service Application Program Interface Version 2, Update 1 J. Linn January 2000 ASCII 229418 101 GSS-API portability application authentication cryptology This memo obsoletes [RFC-2078], 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. [STANDARDS TRACK] ietf-cat-rfc2078bis-08 RFC2078 PROPOSED STANDARD PROPOSED STANDARD RFC2744 Generic Security Service API Version 2 : C-bindings J. Wray January 2000 ASCII 218572 101 GSS-API cryptology authentication This document specifies C language bindings for Version 2, Update 1 of the Generic Security Service Application Program Interface (GSS-API), which is described at a language-independent conceptual level in RFC 2743. [STANDARDS TRACK] ietf-cat-gssv2-cbind-09 RFC1509 PROPOSED STANDARD PROPOSED STANDARD RFC2745 RSVP Diagnostic Messages A. Terzis B. Braden S. Vincent L. Zhang January 2000 ASCII 52256 23 resource reservation protocol network management This document specifies the RSVP diagnostic facility, which allows a user to collect information about the RSVP state along a path. [STANDARDS TRACK] ietf-rsvp-diagnostic-msgs-08 PROPOSED STANDARD PROPOSED STANDARD RFC2746 RSVP Operation Over IP Tunnels A. Terzis J. Krawczyk J. Wroclawski L. Zhang January 2000 ASCII 58094 25 resource reservation protocol internet This document describes an approach for providing RSVP protocol services over IP tunnels. [STANDARDS TRACK] ietf-rsvp-tunnel-04 PROPOSED STANDARD PROPOSED STANDARD RFC2747 RSVP Cryptographic Authentication F. Baker B. Lindell M. Talwar January 2000 ASCII 49477 21 resource reservation protocol security This document describes the format and use of RSVP's INTEGRITY object to provide hop-by-hop integrity and authentication of RSVP messages. [STANDARDS TRACK] ietf-rsvp-md5-08 RFC3097 PROPOSED STANDARD PROPOSED STANDARD RFC2748 The COPS (Common Open Policy Service) Protocol D. Durham Editor J. Boyle R. Cohen S. Herzog R. Rajan A. Sastry January 2000 ASCII 90906 38 COPS qos quality of service signaling This document describes a simple client/server model for supporting policy control over QoS signaling protocols. [STANDARDS TRACK] ietf-rap-cops-08 PROPOSED STANDARD PROPOSED STANDARD RFC2749 COPS usage for RSVP S. Herzog Editor J. Boyle R. Cohen D. Durham R. Rajan A. Sastry January 2000 ASCII 33477 17 common open policy resource reservation protocol This document describes usage directives for supporting COPS policy services in RSVP environments. [STANDARDS TRACK] ietf-rap-cops-rsvp-05 PROPOSED STANDARD PROPOSED STANDARD RFC2750 RSVP Extensions for Policy Control S. Herzog January 2000 ASCII 26379 13 resource reservation protocol admission This memo presents a set of extensions for supporting generic policy based admission control in RSVP. [STANDARDS TRACK] ietf-rap-rsvp-ext-06 RFC2205 PROPOSED STANDARD PROPOSED STANDARD RFC2751 Signaled Preemption Priority Policy Element S. Herzog January 2000 ASCII 21451 12 RSVP COPS resource reservation protocol common open service This document describes a preemption priority policy element for use by signaled policy based admission protocols (such as RSVP and COPS). [STANDARDS TRACK] ietf-rap-signaled-priority-04 RFC3181 PROPOSED STANDARD PROPOSED STANDARD RFC2752 Identity Representation for RSVP S. Yadav R. Yavatkar R. Pabbati P. Ford T. Moore S. Herzog January 2000 ASCII 33954 17 resource reservation protocol admission authentication This document describes the representation of identity information in POLICY_DATA object for supporting policy based admission control in RSVP. [STANDARDS TRACK] ietf-rap-rsvp-identity-05 RFC3182 PROPOSED STANDARD PROPOSED STANDARD RFC2753 A Framework for Policy-based Admission Control R. Yavatkar D. Pendarakis R. Guerin January 2000 ASCII 49763 20 This document is concerned with specifying a framework for providing policy-based control over admission control decisions. This memo provides information for the Internet community. ietf-rap-framework-03 INFORMATIONAL INFORMATIONAL RFC2754 RPS IANA Issues C. Alaettinoglu C. Villamizar R. Govindan January 2000 ASCII 11582 7 internet assigned numbers authority routing policy specification system security RPS Security requires certain RPSL objects in the IRR to be hierarchically delegated. The set of objects that are at the root of this hierarchy needs to be created and digitally signed by IANA. This paper presents these seed objects and lists operations required from IANA. This memo provides information for the Internet community. ietf-rps-iana-02 INFORMATIONAL INFORMATIONAL RFC2755 Security Negotiation for WebNFS A. Chiu M. Eisler B. Callaghan January 2000 ASCII 23493 12 RSVP QOS resource reservation protocol quality of service This document describes a protocol for a WebNFS client (RFC2054) to negotiate the desired security mechanism with a WebNFS server (RFC2055) before the WebNFS client falls back to the MOUNT v3 protocol (RFC1813). This document is provided so that people can write compatible implementations. This memo provides information for the Internet community. chiu-network-wnfs-sec-nego-00 INFORMATIONAL INFORMATIONAL RFC2756 Hyper Text Caching Protocol (HTCP/0.0) P. Vixie D. Wessels January 2000 ASCII 32176 15 HTCP hypertext transfer protocol caches data This document describes HTCP, a protocol for discovering HTTP caches and cached data, managing sets of HTTP caches, and monitoring cache activity. This is an experimental protocol, one among several proposals to perform these functions. This memo defines an Experimental Protocol for the Internet community. vixie-htcp-proto-05 EXPERIMENTAL EXPERIMENTAL RFC2757 Long Thin Networks G. Montenegro S. Dawkins M. Kojo V. Magret N. Vaidya January 2000 ASCII 112988 46 wireless WAN wide area networks TCP transmission control protocol Our goal is to identify a TCP that works for all users, including users of long thin networks. This memo provides information for the Internet community. montenegro-pilc-ltn-03 INFORMATIONAL INFORMATIONAL RFC2758 Definitions of Managed Objects for Service Level Agreements Performance Monitoring K. White February 2000 ASCII 145581 71 MIB management information base SLAs This memo defines a Management Information Base (MIB) for performance monitoring of Service Level Agreements (SLAs) defined via policy definitions. This memo defines an Experimental Protocol for the Internet community. white-slapm-mib-06 EXPERIMENTAL EXPERIMENTAL RFC2759 Microsoft PPP CHAP Extensions, Version 2 G. Zorn January 2000 ASCII 34178 20 point-to-point protocol challenge handshake authentication This document describes version two of Microsoft's PPP CHAP dialect (MS-CHAP-V2). MS-CHAP-V2 is similar to, but incompatible with, MS-CHAP version one (MS-CHAP-V1). This memo provides information for the Internet community. ietf-pppext-mschap-v2-04 INFORMATIONAL INFORMATIONAL RFC2760 Ongoing TCP Research Related to Satellites M. Allman Editor S. Dawkins D. Glover J. Griner D. Tran T. Henderson J. Heidemann J. Touch H. Kruse S. Ostermann K. Scott J. Semke February 2000 ASCII 111141 46 transmission control protocol bandwidth network links This document outlines possible TCP enhancements that may allow TCP to better utilize the available bandwidth provided by networks containing satellite links. This memo provides information for the Internet community. ietf-tcpsat-res-issues-12 INFORMATIONAL INFORMATIONAL RFC2761 Terminology for ATM Benchmarking J. Dunn C. Martin February 2000 ASCII 61219 32 asynchronous transfer mode performance This memo discusses and defines terms associated with performance benchmarking tests and the results of these tests in the context of Asynchronous Transfer Mode (ATM) based switching devices. This memo provides information for the Internet community. ietf-bmwg-atm-term-00 INFORMATIONAL INFORMATIONAL RFC2762 Sampling of the Group Membership in RTP J. Rosenberg H. Schulzrinne February 2000 ASCII 25796 12 real-time transport protocol packets This document discusses mechanisms for sampling of this group membership table in order to reduce the memory requirements. This memo defines an Experimental Protocol for the Internet community. ietf-avt-rtpsample-06 EXPERIMENTAL EXPERIMENTAL RFC2763 Dynamic Hostname Exchange Mechanism for IS-IS N. Shen H. Smit February 2000 ASCII 8593 5 intermediate system routers TLV This document defines a new TLV which allows the IS-IS routers to flood their name to system ID mapping information across the IS-IS network. This memo provides information for the Internet community. ietf-isis-dyname-02 INFORMATIONAL INFORMATIONAL RFC2764 A Framework for IP Based Virtual Private Networks B. Gleeson A. Lin J. Heinanen G. Armitage A. Malis February 2000 ASCII 163215 62 VPN internet protocol backbone This document describes a framework for Virtual Private Networks (VPNs) running across IP backbones. This memo provides information for the Internet community. gleeson-vpn-framework-03 INFORMATIONAL INFORMATIONAL RFC2765 Stateless IP/ICMP Translation Algorithm (SIIT) E. Nordmark February 2000 ASCII 59465 26 SIIT internet protocol control message IPv4 IPv6 This document specifies a transition mechanism algorithm in addition to the mechanisms already specified. [STANDARDS TRACK] ietf-ngtrans-siit-08 PROPOSED STANDARD PROPOSED STANDARD RFC2766 Network Address Translation - Protocol Translation (NAT-PT) G. Tsirtsis P. Srisuresh February 2000 ASCII 49836 21 NAT-PT IPv4 IPv6 internet This document specifies an IPv4-to-IPv6 transition mechanism, in addition to those already specified. [STANDARDS TRACK] ietf-ngtrans-natpt-07 RFC3152 PROPOSED STANDARD PROPOSED STANDARD RFC2767 Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS) K. Tsuchiya H. Higuchi Y. Atarashi February 2000 ASCII 26402 13 IPv4 IPv6 internet protocol applications This memo proposes a mechanism of dual stack hosts using the technique called "Bump-in-the-Stack" in the IP security area. This memo provides information for the Internet community. ietf-ngtrans-bis-00 INFORMATIONAL INFORMATIONAL RFC2768 Network Policy and Services: A Report of a Workshop on Middleware B. Aiken J. Strassner B. Carpenter I. Foster C. Lynch J. Mambretti R. Moore B. Teitelbaum February 2000 ASCII 81034 29 protocols internet applications An ad hoc middleware workshop was held at the International Center for Advanced Internet Research in December 1998. The need for a more organized framework for middleware R&D was recognized, and a list of specific topics needing further work was identified. This memo provides information for the Internet community. aiken-middleware-reqndef-01 INFORMATIONAL INFORMATIONAL RFC2769 Routing Policy System Replication C. Villamizar C. Alaettinoglu R. Govindan D. Meyer February 2000 ASCII 95255 42 RPSL database language This document addresses the need to distribute data over multiple repositories and delegate authority for data subsets to other repositories without compromising the authorization model established in Routing Policy System Security RFC. [STANDARDS TRACK] ietf-rsp-dist-06 PROPOSED STANDARD PROPOSED STANDARD RFC2770 GLOP Addressing in 233/8 D. Meyer P. Lothberg February 2000 ASCII 8988 5 multicast allocation global This describes an experimental policy for use of the class D address space using 233/8 as the experimental statically assigned subset of the class D address space. This memo defines an Experimental Protocol for the Internet community. ietf-mboned-glop-addressing-02 RFC3180 EXPERIMENTAL EXPERIMENTAL RFC2771 An Abstract API for Multicast Address Allocation R. Finlayson February 2000 ASCII 20954 11 application programming interfaces service This document describes the "abstract service interface" for the dynamic multicast address allocation service, as seen by applications. This memo provides information for the Internet community. ietf-malloc-api-07 INFORMATIONAL INFORMATIONAL RFC2772 6Bone Backbone Routing Guidelines R. Rockell R. Fink February 2000 ASCII 28565 14 IP internet protocol routing This document provides a set of guidelines for all 6bone routing equipment operators to use as a reference for efficient and stable deployment of 6bone routing systems. This memo provides information for the Internet community. ietf-ngtrans-harden-04 RFC2546 RFC3152 INFORMATIONAL INFORMATIONAL RFC2773 Encryption using KEA and SKIPJACK R. Housley P. Yee W. Nace February 2000 ASCII 20008 9 key exchange algorithm symmetric This document defines a method to encrypt a file transfer using the FTP specification STD 9, RFC 959, "File Transfer Protocol (FTP)", (October ietf-cat-ftpkeasj-01 RFC0959 EXPERIMENTAL EXPERIMENTAL RFC2774 An HTTP Extension Framework H. Nielsen P. Leach S. Lawrence February 2000 ASCII 39719 20 hyper-text transfer protocol This document describes a generic extension mechanism for HTTP, which is designed to address the tension between private agreement and public specification and to accommodate extension of applications using HTTP clients, servers, and proxies. This memo defines an Experimental Protocol for the Internet community. frystyk-http-extensions-03 EXPERIMENTAL EXPERIMENTAL RFC2775 Internet Transparency B. Carpenter February 2000 ASCII 42956 18 end-to-end network layer connectivity This document describes the current state of the Internet from the architectural viewpoint, concentrating on issues of end-to-end connectivity and transparency. carpenter-transparency-04 INFORMATIONAL INFORMATIONAL RFC2776 Multicast-Scope Zone Announcement Protocol (MZAP) M. Handley D. Thaler R. Kermode February 2000 ASCII 61628 27 MZAP packets addresses service location This document defines a protocol, the Multicast-Scope Zone Announcement Protocol (MZAP), for discovering the multicast administrative scope zones that are relevant at a particular location. [STANDARDS TRACK] ietf-mboned-mzap-06 PROPOSED STANDARD PROPOSED STANDARD RFC2777 Publicly Verifiable Nomcom Random Selection D. Eastlake 3rd February 2000 ASCII 30064 16 Internet Engineering Task Force IETF This document describes a method for making random selections in such a way that the unbiased nature of the choice is publicly verifiable. This memo provides information for the Internet community. eastlake-selection-04 RFC3797 INFORMATIONAL INFORMATIONAL RFC2778 A Model for Presence and Instant Messaging M. Day J. Rosenberg H. Sugano February 2000 ASCII 35153 17 service users MIME multipurpose Internet mail extensions This document defines an abstract model for a presence and instant messaging system. It defines the various entities involved, defines terminology, and outlines the services provided by the system. This memo provides information for the Internet community. ietf-impp-model-03 INFORMATIONAL INFORMATIONAL RFC2779 Instant Messaging / Presence Protocol Requirements M. Day S. Aggarwal G. Mohr J. Vincent February 2000 ASCII 47420 26 MIME multipurpose Internet mail extensions service users This document defines a minimal set of requirements that IMPP must meet. This memo provides information for the Internet community. ietf-impp-reqts-04 INFORMATIONAL INFORMATIONAL RFC2780 IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers S. Bradner V. Paxson March 2000 ASCII 18954 10 internet assigned numbers authority IP This memo provides guidance for the IANA to use in assigning parameters for fields in the IPv4, IPv6, ICMP, UDP and TCP protocol headers. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. bradner-iana-allocation-05 BCP0037 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2781 UTF-16, an encoding of ISO 10646 P. Hoffman F. Yergeau February 2000 ASCII 29870 14 unicode character data code point This document describes the UTF-16 encoding of Unicode/ISO-10646, addresses the issues of serializing UTF-16 as an octet stream for transmission over the Internet, discusses MIME charset naming as described in [CHARSET-REG], and contains the registration for three MIME charset parameter values: UTF-16BE (big-endian), UTF-16LE (little- endian), and UTF-16. This memo provides information for the Internet community. hoffman-utf16-05 INFORMATIONAL INFORMATIONAL RFC2782 A DNS RR for specifying the location of services (DNS SRV) A. Gulbrandsen P. Vixie L. Esibov February 2000 ASCII 24013 12 DNS-SRV domain name system resource record This document describes a DNS RR which specifies the location of the server(s) for a specific protocol and domain. [STANDARDS TRACK] ietf-dnsind-rfc2052bis-05 RFC2052 PROPOSED STANDARD PROPOSED STANDARD RFC2783 Pulse-Per-Second API for UNIX-like Operating Systems, Version 1.0 J. Mogul D. Mills J. Brittenson J. Stone U. Windl March 2000 ASCII 61421 31 NTP time clock synchronization RFC 1589 did not define an API for managing the PPS facility, leaving implementors without a portable means for using PPS sources. This document specifies such an API. This memo provides information for the Internet community. mogul-pps-api-06 INFORMATIONAL INFORMATIONAL RFC2784 Generic Routing Encapsulation (GRE) D. Farinacci T. Li S. Hanks D. Meyer P. Traina March 2000 ASCII 16627 9 GRE packet size payload This document specifies a protocol for encapsulation of an arbitrary network layer protocol over another arbitrary network layer protocol. [STANDARDS TRACK] meyer-gre-update-03 PROPOSED STANDARD PROPOSED STANDARD RFC2785 Methods for Avoiding the "Small-Subgroup" Attacks on the Diffie-Hellman Key Agreement Method for S/MIME R. Zuccherato March 2000 ASCII 24415 11 security multipurpose internet mail extensions This document will describe the situations relevant to implementations of S/MIME version 3 in which protection is necessary and the methods that can be used to prevent these attacks. This memo provides information for the Internet community. ietf-smime-small-subgroup-03 INFORMATIONAL INFORMATIONAL RFC2786 Diffie-Helman USM Key Management Information Base and Textual Convention M. St. Johns March 2000 ASCII 43280 20 mib security user-based model Hellman This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols the Internet community. In particular, it defines a textual convention for doing Diffie-Helman key agreement key exchanges an set of objects which extend the usmUserTable to permit the use of DH key exchange in addition to the key change method. This memo defines an Experimental Protocol for the Internet community. stjohns-snmpv3-dhkeychang-mib-02 EXPERIMENTAL EXPERIMENTAL RFC2787 Definitions of Managed Objects for the Virtual Router Redundancy Protocol B. Jewell D. Chuang March 2000 ASCII 56672 31 management information base This specification defines an extension to the Management Information Base (MIB) for use with SNMP-based network management. In particular, it defines objects for configuring, monitoring, and controlling routers that employ the Virtual Router Redundancy Protocol (VRRP). [STANDARDS TRACK] ietf-vrrp-mib-09 PROPOSED STANDARD PROPOSED STANDARD RFC2788 Network Services Monitoring MIB N. Freed S. Kille March 2000 ASCII 43906 22 management information base This document defines a MIB which contains the elements common to the monitoring of any network service application. [STANDARDS TRACK] ietf-madman-netsm-mib-07 RFC2248 PROPOSED STANDARD PROPOSED STANDARD RFC2789 Mail Monitoring MIB N. Freed S. Kille March 2000 ASCII 65671 33 management information base 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 defined in RFC 2788 [16] to allow monitoring of Message Transfer Agents (MTAs). It may also be used to monitor MTA components within gateways. [STANDARDS TRACK] ietf-madman-email-mib-06 RFC2249 RFC1566 PROPOSED STANDARD PROPOSED STANDARD RFC2790 Host Resources MIB S. Waldbusser P. Grillo March 2000 ASCII 95807 50 management information base This memo obsoletes RFC 1514, the "Host Resources MIB". This memo extends that specification by clarifying changes based on implementation and deployment experience and documenting the Host Resources MIB in SMIv2 format while remaining semantically identical to the existing SMIv1-based MIB. [STANDARDS TRACK] ops-hostmib-01 RFC1514 DRAFT STANDARD DRAFT STANDARD RFC2791 Scalable Routing Design Principles J. Yu July 2000 ASCII 63416 26 network packets This document identifies major factors affecting routing scalability as well as basic principles of designing scalable routing for large networks. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2792 DSA and RSA Key and Signature Encoding for the KeyNote Trust Management System M. Blaze J. Ioannidis A. Keromytis March 2000 ASCII 13461 7 cryptology digial signatures This memo describes RSA and DSA key and signature encoding, and binary key encoding for version 2 of the KeyNote trust-management system. This memo provides information for the Internet community. angelos-keynote-dsa-rsa-encoding-01 INFORMATIONAL INFORMATIONAL RFC2793 RTP Payload for Text Conversation G. Hellstrom May 2000 ASCII 20674 10 real-time applications video audio packets This memo describes how to carry text conversation session contents in RTP packets. Text conversation session contents are specified in ITU-T Recommendation T.140. [STANDARDS TRACK] ietf-avt-rtp-text-05 PROPOSED STANDARD PROPOSED STANDARD RFC2794 Mobile IP Network Access Identifier Extension for IPv4 P. Calhoun C. Perkins March 2000 ASCII 16960 9 internet protocol NAI Our proposal defines a way for the mobile node to identify itself, by including the NAI along with the Mobile IP Registration Request. This memo also updates RFC 2290 which specifies the Mobile-IPv4 Configuration option for IPCP, by allowing the Mobile Node's Home Address field of this option to be zero. [STANDARDS TRACK] ietf-mobileip-mn-nai-07 RFC2290 PROPOSED STANDARD PROPOSED STANDARD RFC2795 The Infinite Monkey Protocol Suite (IMPS) S. Christey April 01 2000 ASCII 42902 20 control packet client This memo describes a protocol suite which supports an infinite number of monkeys that sit at an infinite number of typewriters in order to determine when they have either produced the entire works of William Shakespeare or a good television show. This memo provides information for the Internet community. christey-imps-00 INFORMATIONAL INFORMATIONAL RFC2796 BGP Route Reflection - An Alternative to Full Mesh IBGP T. Bates R. Chandra E. Chen April 2000 ASCII 20174 11 border gateway protocol This document describes the use and design of a method known as "Route Reflection" to alleviate the the need for "full mesh" IBGP. [STANDARDS TRACK] ietf-idr-route-reflect-v2-03 RFC1966 PROPOSED STANDARD PROPOSED STANDARD RFC2797 Certificate Management Messages over CMS M. Myers X. Liu J. Schaad J. Weinstein April 2000 ASCII 103357 47 certificate management protocol cryptology syntax This document defines a Certificate Management protocol using CMS (CMC). [STANDARDS TRACK] ietf-pkix-cmc-05 PROPOSED STANDARD PROPOSED STANDARD RFC2798 Definition of the inetOrgPerson LDAP Object Class M. Smith April 2000 ASCII 32929 20 lightweight directory access protocol directory services We define a new object class called inetOrgPerson for use in LDAP and X.500 directory services that extends the X.521 standard organizationalPerson class to meet these needs. This memo provides information for the Internet community. smith-ldap-inetorgperson-03 RFC3698 INFORMATIONAL INFORMATIONAL RFC2799 Request for Comments Summary RFC Numbers 2700-2799 S. Ginoza September 2000 ASCII 42622 23 INFORMATIONAL INFORMATIONAL RFC2800 Internet Official Protocol Standards J. Reynolds R. Braden S. Ginoza May 2001 ASCII 101648 38 This memo contains a snapshot of the state of standardization of protocols used in the Internet as of April 17, 2001. It lists only official protocol standards RFCs; it is not a complete index to the RFC series. [STANDARDS TRACK] RFC2700 RFC2900 HISTORIC STANDARD RFC2801 Internet Open Trading Protocol - IOTP Version 1.0 D. Burdett April 2000 ASCII 598794 290 commerce payment system merchant This document discusses the Internet Open Trading Protocol (IOTP) and its provision of an interoperable framework for Internet commerce. This memo provides information for the Internet community. ietf-trade-iotp-v1.0-protocol-07 INFORMATIONAL INFORMATIONAL RFC2802 Digital Signatures for the v1.0 Internet Open Trading Protocol (IOTP) K. Davidson Y. Kawatsura April 2000 ASCII 52756 29 commerce payment system xml extensible markup language security This document describes the syntax and procedures for the computation and verification of digital signatures for use within Version 1.0 of the Internet Open Trading Protocol (IOTP). This memo provides information for the Internet community. ietf-trade-iotp-v1.0-dsig-05 INFORMATIONAL INFORMATIONAL RFC2803 Digest Values for DOM (DOMHASH) H. Maruyama K. Tamura N. Uramoto April 2000 ASCII 22552 11 xml extensible markup language secruity This memo defines a clear and unambiguous definition of digest (hash) values of the XML objects regardless of the surface string variation of XML. This memo provides information for the Internet community. ietf-trade-hiroshi-dom-hash-03 INFORMATIONAL INFORMATIONAL RFC2804 IETF Policy on Wiretapping IAB IESG May 2000 ASCII 18934 10 internet engineering task force This document describes the position that the Internet Engineering Task Force (IETF) has taken regarding the inclusion into IETF standards-track documents of functionality designed to facilitate wiretapping. This memo explains what the IETF thinks the question means, why its answer is "no", and what that answer means. This memo provides information for the Internet community. iab-raven-01 INFORMATIONAL INFORMATIONAL RFC2805 Media Gateway Control Protocol Architecture and Requirements N. Greene M. Ramalho B. Rosen April 2000 ASCII 88190 45 MG mapping transcoding network This document describes protocol requirements for the Media Gateway Control Protocol between a Media Gateway Controller and a Media Gateway. This memo provides information for the Internet community. ietf-megaco-reqs-10 INFORMATIONAL INFORMATIONAL RFC2806 URLs for Telephone Calls A. Vaha-Sipila April 2000 ASCII 50647 21 uniform resource locator schemes This document specifies URL (Uniform Resource Locator) schemes "tel", "fax" and "modem" for specifying the location of a terminal in the phone network and the connection types (modes of operation) that can be used to connect to that entity. [STANDARDS TRACK] antti-telephony-url-12 RFC3966 PROPOSED STANDARD PROPOSED STANDARD RFC2807 XML Signature Requirements J. Reagle July 2000 ASCII 21973 9 digital extensible markup language This document lists the design principles, scope, and requirements for the XML Digital Signature specification. It includes requirements as they relate to the signature syntax, data model, format, cryptographic processing, and external requirements and coordination. This memo provides information for the Internet community. ietf-xmldsig-requirements-03 INFORMATIONAL INFORMATIONAL RFC2808 The SecurID(r) SASL Mechanism M. Nystrom April 2000 ASCII 20342 11 simple authentication security layer This document defines a SASL (Simple Authentication and Security Layer) authentication mechanism using SecurID (a hardware token card product (or software emulation thereof) produced by RSA Security Inc., which is used for end-user authentication), thereby providing a means for such tokens to be used in SASL environments. This mechanism is only is only for authentication, and has no effect on the protocol encoding and is not designed to provide integrity or confidentiality services. This memo provides information for the Internet community. nystrom-securid-sasl-02 INFORMATIONAL INFORMATIONAL RFC2809 Implementation of L2TP Compulsory Tunneling via RADIUS B. Aboba G. Zorn April 2000 ASCII 47259 23 remote authentication dial-in user service layer two This document discusses implementation issues arising in the provisioning of compulsory tunneling in dial-up networks using the L2TP (Layer Two Tunneling Protocol) protocol. This memo provides information for the Internet community. ietf-radius-tunnel-imp-05 INFORMATIONAL INFORMATIONAL RFC2810 Internet Relay Chat: Architecture C. Kalt April 2000 ASCII 19087 10 IRC text based conferencing This document is an update describing the architecture of the current IRC protocol and the role of its different components. Other documents describe in detail the protocol used between the various components defined here. This memo provides information for the Internet community. kalt-irc-arch-00 RFC1459 INFORMATIONAL INFORMATIONAL RFC2811 Internet Relay Chat: Channel Management C. Kalt April 2000 ASCII 40788 19 IRC text based conferencing This document specifies how channels, their characteristics and properties are managed by IRC servers. This memo provides information for the Internet community. kalt-irc-chan-01 RFC1459 INFORMATIONAL INFORMATIONAL RFC2812 Internet Relay Chat: Client Protocol C. Kalt April 2000 ASCII 122637 63 IRC text based conferencing This document defines the Client Protocol, and assumes that the reader is familiar with the IRC Architecture. This memo provides information for the Internet community. kalt-irc-client-03 RFC1459 INFORMATIONAL INFORMATIONAL RFC2813 Internet Relay Chat: Server Protocol C. Kalt April 2000 ASCII 56681 26 IRC text based conferencing This document defines the protocol used by servers to talk to each other. This memo provides information for the Internet community. kalt-irc-server-02 RFC1459 INFORMATIONAL INFORMATIONAL RFC2814 SBM (Subnet Bandwidth Manager): A Protocol for RSVP-based Admission Control over IEEE 802-style networks R. Yavatkar D. Hoffman Y. Bernet F. Baker M. Speer May 2000 ASCII 141886 60 LAN local area resource reservation This document describes a signaling method and protocol for RSVP-based admission control over IEEE 802-style LANs. [STANDARDS TRACK] ietf-issll-is802-sbm-10 PROPOSED STANDARD PROPOSED STANDARD RFC2815 Integrated Service Mappings on IEEE 802 Networks M. Seaman A. Smith E. Crawley J. Wroclawski May 2000 ASCII 42403 17 LAN local area resource reservation This document describes mappings of IETF Integrated Services over LANs built from IEEE 802 network segments which may be interconnected by IEEE 802.1D MAC Bridges (switches). [STANDARDS TRACK] ietf-issll-is802-svc-mapping-04 PROPOSED STANDARD PROPOSED STANDARD RFC2816 A Framework for Integrated Services Over Shared and Switched IEEE 802 LAN Technologies A. Ghanwani J. Pace V. Srinivasan A. Smith M. Seaman May 2000 ASCII 119043 47 LAN local area network parameter switches This memo describes a framework for supporting IETF Integrated Services on shared and switched LAN infrastructure. This memo provides information for the Internet community. ietf-issll-is802-framework-07 INFORMATIONAL INFORMATIONAL RFC2817 Upgrading to TLS Within HTTP/1.1 R. Khare S. Lawrence May 2000 ASCII 27598 13 hypertext transfer protocol transport layer security This memo explains how to use the Upgrade mechanism in HTTP/1.1 to initiate Transport Layer Security (TLS) over an existing TCP connection. [STANDARDS TRACK] ietf-tls-http-upgrade-05 RFC2616 PROPOSED STANDARD PROPOSED STANDARD RFC2818 HTTP Over TLS E. Rescorla May 2000 ASCII 15170 7 hypertext transfer protocol transport layer security This memo describes how to use Transport Layer Security (TLS) to secure Hypertext Transfer Protocol (HTTP) connections over the Internet. This memo provides information for the Internet community. ietf-tls-https-04 INFORMATIONAL INFORMATIONAL RFC2819 Remote Network Monitoring Management Information Base S. Waldbusser May 2000 ASCII 198676 98 RMON-MIB MIB RMON 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] ietf-rmonmib-rmonfull-02 RFC1757 STD0059 STANDARD STANDARD RFC2820 Access Control Requirements for LDAP E. Stokes D. Byrne B. Blakley P. Behera May 2000 ASCII 18172 9 lightweight directory access protocol This document describes the fundamental requirements of an access control list (ACL) model for the Lightweight Directory Application Protocol (LDAP) directory service. This memo provides information for the Internet community. ietf-ldapext-acl-reqts-03 INFORMATIONAL INFORMATIONAL RFC2821 Simple Mail Transfer Protocol J. Klensin Editor April 2001 ASCII 192504 79 SMTP This document is a self-contained specification of the basic protocol for the Internet electronic mail transport. [STANDARDS TRACK] ietf-drums-smtpupd-13 RFC0821 RFC0974 RFC1869 PROPOSED STANDARD PROPOSED STANDARD RFC2822 Internet Message Format P. Resnick Editor April 2001 ASCII 110695 51 MAIL This document specifies a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages. [STANDARDS TRACK] ietf-drums-msg-fmt-09 RFC0822 PROPOSED STANDARD PROPOSED STANDARD RFC2823 PPP over Simple Data Link (SDL) using SONET/SDH with ATM-like framing J. Carlson P. Langner E. Hernandez-Valencia J. Manchester May 2000 ASCII 60049 28 PPP-SDL point-to-point protocol synchronous optical network digital hierarchy data link simple This document extends methods found in the Point-to-Point Protocol (PPP) and RFCs 1662 and 2615 to include a new encapsulation for PPP called Simple Data Link (SDL). SDL provides a standard method for transporting multi-protocol datagrams over point-to-point links, and RFCs 1662 and 2615 provide a means to carry PPP over Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) circuits. SDL provides a very low overhead alternative to HDLC-like encapsulation, and can also be used on SONET/SDH links. This memo defines an Experimental Protocol for the Internet community. ietf-pppext-sdl-06 EXPERIMENTAL EXPERIMENTAL RFC2824 Call Processing Language Framework and Requirements J. Lennox H. Schulzrinne May 2000 ASCII 58711 25 CPL-F telephony signalling network devices This document describes an architectural framework we call a processing language, as a simple and standardized way for implementing and deploying Internet telephony. A large number of the services we wish to make possible for Internet telephony require fairly elaborate combinations of signalling operations, often in network devices, to complete. It also outlines requirements for such a language. This memo provides information for the Internet community. ietf-iptel-cpl-framework-02 INFORMATIONAL INFORMATIONAL RFC2825 A Tangled Web: Issues of I18N, Domain Names, and the Other Internet protocols IAB L. Daigle Editor May 2000 ASCII 15612 7 character sets e-commerce interoperability This document is a statement by the Internet Architecture Board. It is not a protocol specification, but an attempt to clarify the range of architectural issues that the internationalization of domain names faces. This memo provides information for the Internet community. iab-i18n-dns-01 INFORMATIONAL INFORMATIONAL RFC2826 IAB Technical Comment on the Unique DNS Root Internet Architecture Board May 2000 ASCII 13400 6 Internet Architecture Board domain name system This document discusses the existence of a globally unique public name space in the Internet called the DNS (Domain Name System). This name space is a hierarchical name space derived from a single, globally unique root. It is a technical constraint inherent in the design of the DNS. One root must be supported by a set of coordinated root servers administered by a unique naming authority. It is not technically feasible for there to be more than one root in the public DNS. This memo provides information for the Internet community. iab-unique-dns-root-00 INFORMATIONAL INFORMATIONAL RFC2827 Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing P. Ferguson D. Senie May 2000 ASCII 21258 10 ISP Internet Service Provider Internet Protocol DOS This paper discusses a simple, effective, and straightforward method for using ingress traffic filtering to prohibit DoS (Denial of Service) attacks which use forged IP addresses to be propagated from 'behind' an Internet Service Provider's (ISP) aggregation point. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC2267 RFC3704 BCP0038 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2828 Internet Security Glossary R. Shirey May 2000 ASCII 489292 212 information system ISD internet standard documents This Glossary provides abbreviations, explanations, and recommendations for use of information system security terminology. This memo provides information for the Internet community. shirey-security-glossary-02 FYI0036 INFORMATIONAL INFORMATIONAL RFC2829 Authentication Methods for LDAP M. Wahl H. Alvestrand J. Hodges R. Morgan May 2000 ASCII 33471 16 lightweight directory access protocol security This document specifies particular combinations of security mechanisms which are required and recommended in LDAP implementations. [STANDARDS TRACK] ietf-ldapext-authmeth-04 RFC3377 PROPOSED STANDARD PROPOSED STANDARD RFC2830 Lightweight Directory Access Protocol (v3): Extension for Transport Layer Security J. Hodges R. Morgan M. Wahl May 2000 ASCII 24469 12 LDAP TLS This document defines the "Start Transport Layer Security (TLS) Operation" for LDAP. [STANDARDS TRACK] ietf-ldapext-ldapv3-tls-06 RFC3377 PROPOSED STANDARD PROPOSED STANDARD RFC2831 Using Digest Authentication as a SASL Mechanism P. Leach C. Newman May 2000 ASCII 58124 27 http hypertext transfer protocol security simple layer This specification defines how HTTP Digest Authentication can be used as a SASL mechanism for any protocol that has a SASL (Simple Authentication and Security Layer) profile. [STANDARDS TRACK] leach-digest-sasl-05 PROPOSED STANDARD PROPOSED STANDARD RFC2832 NSI Registry Registrar Protocol (RRP) Version 1.1.0 S. Hollenbeck M. Srivastava May 2000 ASCII 77057 39 RRP shared registration system gLTD ccTLD top level domain This document describes a protocol for the registration and management of second level domain names and associated name servers in both generic Top Level Domains (gTLDs) and country code Top Level Domains (ccTLDs). This memo provides information for the Internet community. hollenbeck-rrp-01 RFC3632 INFORMATIONAL INFORMATIONAL RFC2833 RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals H. Schulzrinne S. Petrack May 2000 ASCII 68786 30 real-time application protocol DTMF dual-tone multifrequency This memo describes how to carry dual-tone multifrequency (DTMF) signaling, other tone signals and telephony events in RTP packets. [STANDARDS TRACK] ietf-avt-tones-07 PROPOSED STANDARD PROPOSED STANDARD RFC2834 ARP and IP Broadcast over HIPPI-800 J.-M. Pittet May 2000 ASCII 76243 34 address resolution protocol internet high-performance internface parallel This document specifies a method for resolving IP addresses to ANSI High-Performance Parallel Interface (HIPPI) hardware addresses and for emulating IP broadcast in a logical IP subnet (LIS) as a direct extension of HARP (hardware addresses). This memo defines a HARP that will interoperate between HIPPI-800 and HIPPI-6400 (also known as Gigabyte System Network, GSN). This document (when combined with RFC 2067 "IP over HIPPI") obsoletes RFC 1374. [STANDARDS TRACK] pittet-hippiarp-05 RFC1374 PROPOSED STANDARD PROPOSED STANDARD RFC2835 IP and ARP over HIPPI-6400 (GSN) J.-M. Pittet May 2000 ASCII 74178 33 GSN address resolution protocol internet high-performance internface parallel This document further specifies a method for resolving IP addresses to HIPPI-6400 (High-Performance Parallel Interface) hardware addresses (HARP) and for emulating IP broadcast in a logical IP subnet (LIS) as a direct extension of HARP. Furthermore, it is the goal of this memo to define a IP and HARP that will allow interoperability for HIPPI-800 and HIPPI-6400 equipment both broadcast and non-broadcast capable networks. [STANDARDS TRACK] pittet-gsnlan-04 PROPOSED STANDARD PROPOSED STANDARD RFC2836 Per Hop Behavior Identification Codes S. Brim B. Carpenter F. Le Faucheur May 2000 ASCII 13399 7 PHB differentiated services codepoint DSCP This document defines a binary encoding to uniquely identify PHBs (Per Hop Behaviors) and/or sets of PHBs in protocol messages. [STANDARDS TRACK] ietf-diffserv-phbid-00 RFC3140 PROPOSED STANDARD PROPOSED STANDARD RFC2837 Definitions of Managed Objects for the Fabric Element in Fibre Channel Standard K. Teow May 2000 ASCII 87860 48 MIB management information base 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 the objects for managing the operations of the Fabric Element portion of the Fibre Channel Standards. [STANDARDS TRACK] ietf-ipfc-fabric-element-mib-07 RFC4044 PROPOSED STANDARD PROPOSED STANDARD RFC2838 Uniform Resource Identifiers for Television Broadcasts D. Zigmond M. Vickers May 2000 ASCII 11405 6 URI TV WWW world wide web This document describes a widely-implemented URI scheme, as World-Wide Web browsers are starting to appear on a variety of consumer electronic devices, such as television sets and television set-top boxes, which are capable of receiving television programming from either terrestrial broadcast, satellite broadcast, or cable. In this context there is a need to reference television broadcasts using the URI format described in RFC 2396. This memo provides information for the Internet community. zigmond-tv-url-04 INFORMATIONAL INFORMATIONAL RFC2839 Internet Kermit Service F. da Cruz J. Altman May 2000 ASCII 42726 20 file transfer management service This document describes a new file transfer service for the Internet based on Telnet Protocol for option negotiation and Kermit Protocol for file transfer and management. This memo provides information for the Internet community. columbia-kermit-service-03 INFORMATIONAL INFORMATIONAL RFC2840 TELNET KERMIT OPTION J. Altman F. da Cruz May 2000 ASCII 22519 12 file transfer management service This document describes an extension to the Telnet protocol to allow the negotiation, coordination, and use of the Kermit file transfer and management protocol over an existing Telnet protocol connection. This memo provides information for the Internet community. altman-telnet-kermit-server-03 INFORMATIONAL INFORMATIONAL RFC2841 IP Authentication using Keyed SHA1 with Interleaved Padding (IP-MAC) P. Metzger W. Simpson November 2000 ASCII 14139 9 IP-MAC encryption secure hash algorithm This document describes the use of keyed SHA1 (Secure Hash Algorithm) with the IP Authentication Header. This memo defines a Historic Document for the Internet community. simpson-ah-sha-kdp-00 RFC1852 HISTORIC HISTORIC RFC2842 Capabilities Advertisement with BGP-4 R. Chandra J. Scudder May 2000 ASCII 8366 5 border gateway protocol This document defines new Optional Parameter, called Capabilities, that is expected to facilitate introduction of new capabilities in BGP by providing graceful capability advertisement without requiring that BGP peering be terminated. [STANDARDS TRACK] ietf-idr-bgp4-cap-neg-06 RFC3392 PROPOSED STANDARD PROPOSED STANDARD RFC2843 Proxy-PAR P. Droz T. Przygienda May 2000 ASCII 27891 13 PNNI augmented Routing ATM asynchronous transfer mode The intention of this document is to provide general information about Proxy-PAR (PNNI Augmented Routing). [STANDARDS TRACK] ietf-ion-proxypar-arch-02 INFORMATIONAL INFORMATIONAL RFC2844 OSPF over ATM and Proxy-PAR T. Przygienda P. Droz R. Haas May 2000 ASCII 32146 14 PNNI augmented Routing asynchronous transfer mode open shortest-path first This memo specifies, for OSPF implementors and users, mechanisms describing how the protocol operates in ATM networks over PVC (Permanent Virtual Connections) and SVC (Switched Virtual Circuit) meshes with the presence of Proxy-PAR (PNNI Augmented Routing). This memo defines an Experimental Protocol for the Internet community. ietf-ospf-atm-04 EXPERIMENTAL EXPERIMENTAL RFC2845 Secret Key Transaction Authentication for DNS (TSIG) P. Vixie O. Gudmundsson D. Eastlake 3rd B. Wellington May 2000 ASCII 32272 15 TSIG domain name system transaction signature This protocol allows for transaction level authentication using shared secrets and one way hashing. It can be used to authenticate dynamic updates as coming from an approved client, or to authenticate responses as coming from an approved recursive name server. [STANDARDS TRACK] ietf-dnsext-tsig-00 RFC1035 RFC3645 PROPOSED STANDARD PROPOSED STANDARD RFC2846 GSTN Address Element Extensions in E-mail Services C. Allocchio June 2000 ASCII 54316 35 global switched telephone network This memo defines a full syntax for a specific application in which there is a need to represent GSTN (Global Switched Telephone Network) addressing and Internet addressing. [STANDARDS TRACK] ietf-fax-fulladdr-06 RFC3191 RFC3192 PROPOSED STANDARD PROPOSED STANDARD RFC2847 LIPKEY - A Low Infrastructure Public Key Mechanism Using SPKM M. Eisler June 2000 ASCII 50045 22 LIPKEY client server simple pubilc key mechanism authentication This memorandum describes a method whereby one can use GSS-API (Generic Security Service Application Program Interface) to supply a secure channel between a client and server, authenticating the client with a password, and a server with a public key certificate. [STANDARDS TRACK] ietf-cat-lipkey-03 PROPOSED STANDARD PROPOSED STANDARD RFC2848 The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services S. Petrack L. Conroy June 2000 ASCII 168851 73 session initiation protocol internet description This document contains the specification of the PINT Service Protocol 1.0, which defines a protocol for invoking certain telephone services from an IP network. [STANDARDS TRACK] ietf-pint-protocol-04 PROPOSED STANDARD PROPOSED STANDARD RFC2849 The LDAP Data Interchange Format (LDIF) - Technical Specification G. Good June 2000 ASCII 26017 14 LDIF lightweight directory access protocol file This document describes a file format suitable for describing directory information or modifications made to directory information. [STANDARDS TRACK] good-ldap-ldif-06 PROPOSED STANDARD PROPOSED STANDARD RFC2850 Charter of the Internet Architecture Board (IAB) Internet Architecture Board B. Carpenter Editor May 2000 ASCII 15984 8 ISOC Internet Society IETF IRTF This memo documents the composition, selection, roles, and organization of the Internet Architecture Board. It replaces RFC 1601. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. iab-rfc1601bis-04 RFC1601 BCP0039 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2851 Textual Conventions for Internet Network Addresses M. Daniele B. Haberman S. Routhier J. Schoenwaelder June 2000 ASCII 32587 16 layer management information base inet address mib This MIB module defines textual conventions to represent commonly used Internet network layer addressing information. [STANDARDS TRACK] ops-endpoint-mib-08 RFC3291 PROPOSED STANDARD PROPOSED STANDARD RFC2852 Deliver By SMTP Service Extension D. Newman June 2000 ASCII 29285 13 simple mail transfer protocol client server This memo defines a mechanism whereby a SMTP client can request, when transmitting a message to a SMTP server, that the server deliver the message within a prescribed period of time. [STANDARDS TRACK] newman-deliver-03 RFC1894 PROPOSED STANDARD PROPOSED STANDARD RFC2853 Generic Security Service API Version 2 : Java Bindings J. Kabat M. Upadhyay June 2000 ASCII 199512 96 GSI application program interface This document specifies the Java bindings for GSS-API (Generic Security Service Application Program Interface) which is described at a language independent conceptual level in RFC 2743. [STANDARDS TRACK] ietf-cat-gssv2-javabind-05 PROPOSED STANDARD PROPOSED STANDARD RFC2854 The 'text/html' Media Type D. Connolly L. Masinter June 2000 ASCII 16135 8 HTML-INT HTML WWW World Wide Web This document summarizes the history of HTML development, and defines the "text/html" MIME type by pointing to the relevant W3C recommendations. This memo provides information for the Internet community. connolly-text-html-02 RFC2070 RFC1980 RFC1942 RFC1867 RFC1866 INFORMATIONAL INFORMATIONAL RFC2855 DHCP for IEEE 1394 K. Fujisawa June 2000 ASCII 8070 5 dynamic host configuration protocol high performance serial bus This memo describes specific usage of some fields of DHCP (Dynamic Host Configuration Protocol) messages. IEEE Std 1394-1995 is a standard for a High Performance Serial Bus. Since 1394 uses a different link-layer addressing method than conventional IEEE802/Ethernet, the usage of some fields must be clarified to achieve interoperability. [STANDARDS TRACK] ietf-ip1394-dhcp-04 PROPOSED STANDARD PROPOSED STANDARD RFC2856 Textual Conventions for Additional High Capacity Data Types A. Bierman K. McCloghrie R. Presuhn June 2000 ASCII 20954 10 SNMP simple network management protocol This memo specifies new textual conventions for additional high capacity data types, intended for SNMP implementations which already support the Counter64 data type. [STANDARDS TRACK] kzm-hcdata-types-05 PROPOSED STANDARD PROPOSED STANDARD RFC2857 The Use of HMAC-RIPEMD-160-96 within ESP and AH A. Keromytis N. Provos June 2000 ASCII 13544 7 ipsec encapsulating security payload authentication This memo describes the use of the HMAC algorithm in conjunction with the RIPEMD-160 algorithm as an authentication mechanism within the revised IPSEC Encapsulating Security Payload (ESP) and the revised IPSEC Authentication Header (AH). [STANDARDS TRACK] ietf-ipsec-auth-hmac-ripemd-160-96-04 PROPOSED STANDARD PROPOSED STANDARD RFC2858 Multiprotocol Extensions for BGP-4 T. Bates Y. Rekhter R. Chandra D. Katz June 2000 ASCII 23305 11 MEXT-BGP4 Border gateway protocol router network layer This document defines extensions to BGP-4 to enable it to carry routing information for multiple Network Layer protocols (e.g., IPv6, IPX, etc...). [STANDARDS TRACK] ietf-idr-bgp4-multiprotocol-v2-05 RFC2283 PROPOSED STANDARD PROPOSED STANDARD RFC2859 A Time Sliding Window Three Colour Marker (TSWTCM) W. Fang N. Seddigh B. Nandy June 2000 ASCII 19203 9 TSWTCM packets traffic stream routers This memo defines a Time Sliding Window Three Colour Marker (TSWTCM), which can be used as a component in a Diff-Serv traffic conditioner. This memo defines an Experimental Protocol for the Internet community. fang-diffserv-tc-tswtcm-01 EXPERIMENTAL EXPERIMENTAL RFC2860 Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority B. Carpenter F. Baker M. Roberts June 2000 ASCII 12361 7 mou iana ietf icann engineering task force corporation names This document places on record the text of the Memorandum of Understanding concerning the technical work of the IANA that was signed on March 1, 2000 between the IETF and ICANN, and ratified by the ICANN Board on March 10, 2000. This memo provides information for the Internet community. iab-iana-mou-00 INFORMATIONAL INFORMATIONAL RFC2861 TCP Congestion Window Validation M. Handley J. Padhye S. Floyd June 2000 ASCII 26993 11 transmission control protocol This document describes a simple modification to TCP's congestion control algorithms to decay the congestion window cwnd after the transition from a sufficiently-long application-limited period, while using the slow-start threshold ssthresh to save information about the previous value of the congestion window. This memo defines an Experimental Protocol for the Internet community. handley-tcp-cwv-02 EXPERIMENTAL EXPERIMENTAL RFC2862 RTP Payload Format for Real-Time Pointers M. Civanlar G. Cash June 2000 ASCII 12031 7 view graphs resolution audio video signals This document describes an RTP payload format for transporting the coordinates of a dynamic pointer that may be used during a presentation. [STANDARDS TRACK] ietf-avt-pointer-02 PROPOSED STANDARD PROPOSED STANDARD RFC2863 The Interfaces Group MIB K. McCloghrie F. Kastenholz June 2000 ASCII 155014 69 INTERGRMIB Management Information Base Network This memo discusses the 'interfaces' group of MIB-II, especially the experience gained from the definition of numerous media-specific MIB modules for use in conjunction with the 'interfaces' group for managing various sub-layers beneath the internetwork-layer. It specifies clarifications to, and extensions of, the architectural issues within the MIB-II model of the 'interfaces' group. [STANDARDS TRACK] ietf-ifmib-ifmib2-03 RFC2233 DRAFT STANDARD DRAFT STANDARD RFC2864 The Inverted Stack Table Extension to the Interfaces Group MIB K. McCloghrie G. Hanson June 2000 ASCII 21445 11 management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects which provide an inverted mapping of the interface stack table used for managing network interfaces. [STANDARDS TRACK] ietf-ifmib-invstackmib-03 PROPOSED STANDARD PROPOSED STANDARD RFC2865 Remote Authentication Dial In User Service (RADIUS) C. Rigney S. Willens A. Rubens W. Simpson June 2000 ASCII 146456 76 RADIUS encryption NAS Network Access Server This document describes a protocol for carrying authentication, authorization, and configuration information between a Network Access Server which desires to authenticate its links and a shared Authentication Server. [STANDARDS TRACK] ietf-radius-radius-v2-06 RFC2138 RFC2868 RFC3575 DRAFT STANDARD DRAFT STANDARD RFC2866 RADIUS Accounting C. Rigney June 2000 ASCII 51135 28 RADIUS-ACC remote authentication dial in user service encryption This document describes a protocol for carrying accounting information between a Network Access Server and a shared Accounting Server. This memo provides information for the Internet community. ietf-radius-accouting-v2-05 RFC2139 RFC2867 INFORMATIONAL INFORMATIONAL RFC2867 RADIUS Accounting Modifications for Tunnel Protocol Support G. Zorn B. Aboba D. Mitton June 2000 ASCII 51135 11 RADIUS] encryption NAS Network Access Server This document defines new RADIUS (Remote Authentication Dial In User Service) accounting Attributes and new values for the existing Acct- Status-Type Attribute designed to support the provision of compulsory tunneling in dial-up networks. This memo provides information for the Internet community. ietf-radius-tunnel-acct-05 RFC2866 INFORMATIONAL INFORMATIONAL RFC2868 RADIUS Attributes for Tunnel Protocol Support G. Zorn D. Leifer A. Rubens J. Shriver M. Holdrege I. Goyret June 2000 ASCII 42609 20 RADIUS encryption NAS Network Access Server This document defines a set of RADIUS (Remote Authentication Dial In User Service) attributes designed to support the provision of compulsory tunneling in dial-up networks. This memo provides information for the Internet community. ietf-radius-tunnel-auth-09 RFC2865 INFORMATIONAL INFORMATIONAL RFC2869 RADIUS Extensions C. Rigney W. Willats P. Calhoun June 2000 ASCII 96854 47 RADIUS encryption NAS Network Access Server This document describes additional attributes for carrying authentication, authorization and accounting information between a Network Access Server (NAS) and a shared Accounting Server using the Remote Authentication Dial In User Service (RADIUS) protocol described in RFC 2865 and RFC 2866. This memo provides information for the Internet community. ietf-radius-ext-07 RFC3579 INFORMATIONAL INFORMATIONAL RFC2870 Root Name Server Operational Requirements R. Bush D. Karrenberg M. Kosters R. Plzak June 2000 ASCII 21133 10 infrastructure domain names security The primary focus of this document is to provide guidelines for operation of the root name servers. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-dnsop-root-opreq-05 RFC2010 BCP0040 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2871 A Framework for Telephony Routing over IP J. Rosenberg H. Schulzrinne June 2000 ASCII 60664 25 internet protocol TRIP gateway This document serves as a framework for Telephony Routing over IP (TRIP), which supports the discovery and exchange of IP telephony gateway routing tables between providers. This memo provides information for the Internet community. ietf-iptel-gwloc-framework-06 INFORMATIONAL INFORMATIONAL RFC2872 Application and Sub Application Identity Policy Element for Use with RSVP Y. Bernet R. Pabbati June 2000 ASCII 10933 6 resource reservation protocol RSVP signaling messages typically include policy data objects, which in turn contain policy elements. Policy elements may describe user and/or application information, which may be used by RSVP aware network elements to apply appropriate policy decisions to a traffic flow. This memo details the usage of policy elements that provide application information. [STANDARDS TRACK] ietf-rap-rsvp-appid-01 PROPOSED STANDARD PROPOSED STANDARD RFC2873 TCP Processing of the IPv4 Precedence Field X. Xiao A. Hannan V. Paxson E. Crabbe June 2000 ASCII 15565 8 transmission control protocol internet This memo describes a conflict between TCP and DiffServ on the use of the three leftmost bits in the TOS octet of an IPv4 header. [STANDARDS TRACK] xiao-tcp-prec-03 PROPOSED STANDARD PROPOSED STANDARD RFC2874 DNS Extensions to Support IPv6 Address Aggregation and Renumbering M. Crawford C. Huitema July 2000 ASCII 44204 20 internet protocol domain name system This document defines changes to the Domain Name System to support renumberable and aggregatable IPv6 addressing. [STANDARDS TRACK] ietf-ipngwg-dns-lookups-08 RFC1886 RFC3152 RFC3226 RFC3363 RFC3364 EXPERIMENTAL PROPOSED STANDARD RFC2875 Diffie-Hellman Proof-of-Possession Algorithms H. Prafullchandra J. Schaad July 2000 ASCII 45231 23 certificate security encryption This document describes two methods for producing an integrity check value from a Diffie-Hellman key pair. [STANDARDS TRACK] ietf-pkix-dhpop-03 PROPOSED STANDARD PROPOSED STANDARD RFC2876 Use of the KEA and SKIPJACK Algorithms in CMS J. Pawling July 2000 ASCII 29265 13 encryption cryptographic message syntax This document describes the conventions for using the Key Exchange Algorithm (KEA) and SKIPJACK encryption algorithm in conjunction with the Cryptographic Message Syntax [CMS] enveloped-data and encrypted- data content types. This memo provides information for the Internet community. ietf-smime-cmskea-05 INFORMATIONAL INFORMATIONAL RFC2877 5250 Telnet Enhancements T. Murphy Jr. P. Rieth J. Stevens July 2000 ASCII 83369 36 client server printer This memo describes the interface to the IBM 5250 Telnet server that allows client Telnet to request a Telnet terminal or printer session using a specific device name. This memo provides information for the Internet community. ietf-tn3270e-tn5250e-05 RFC1205 INFORMATIONAL INFORMATIONAL RFC2878 PPP Bridging Control Protocol (BCP) M. Higashiyama F. Baker July 2000 ASCII 79527 38 PPP-BCP point-to-point datagrams network This document defines the Network Control Protocol for establishing and configuring Remote Bridging for PPP links. [STANDARDS TRACK] ietf-pppext-bcp-04 RFC1638 RFC3518 PROPOSED STANDARD PROPOSED STANDARD RFC2879 Content Feature Schema for Internet Fax (V2) G. Klyne L. McIntyre August 2000 ASCII 104032 58 media features mechanism This document defines a content media feature schema for Internet fax. [STANDARDS TRACK] ietf-fax-feature-schema-v2-01 RFC2531 PROPOSED STANDARD PROPOSED STANDARD RFC2880 Internet Fax T.30 Feature Mapping L. McIntyre G. Klyne August 2000 ASCII 75973 37 schema media tags This document describes how to map Group 3 fax capability identification bits, described in ITU T.30, into the Internet fax feature schema described in "Content feature schema for Internet fax". This memo provides information for the Internet community. ietf-fax-feature-t30-mapping-03 INFORMATIONAL INFORMATIONAL RFC2881 Network Access Server Requirements Next Generation (NASREQNG) NAS Model D. Mitton M. Beadles July 2000 ASCII 45029 20 RADIUS remote authentication dial-up user service This document describes the terminology and gives a model of typical Network Access Server (NAS). This memo provides information for the Internet community. ietf-nasreq-nasmodel-02 INFORMATIONAL INFORMATIONAL RFC2882 Network Access Servers Requirements: Extended RADIUS Practices D. Mitton July 2000 ASCII 31426 16 NAS remote authentication dial-in user service This document describes current practices implemented in NAS products that go beyond the scope of the RADIUS (Remote Authentication Dial In User Service) RFCs 2138, 2139. This memo provides information for the Internet community. ietf-nasreq-ext-radiuspract-03 INFORMATIONAL INFORMATIONAL RFC2883 An Extension to the Selective Acknowledgement (SACK) Option for TCP S. Floyd J. Mahdavi M. Mathis M. Podolsky July 2000 ASCII 35794 17 SACK transmission control protocol packets sender receiver This note defines an extension of the Selective Acknowledgement (SACK) Option for TCP. [STANDARDS TRACK] floyd-sack-00 PROPOSED STANDARD PROPOSED STANDARD RFC2884 Performance Evaluation of Explicit Congestion Notification (ECN) in IP Networks J. Hadi Salim U. Ahmed July 2000 ASCII 44647 18 internet protocol end-to-end TCP transmission control This memo presents a performance study of the Explicit Congestion Notification (ECN) mechanism in the TCP/IP protocol using our implementation on the Linux Operating System. This memo provides information for the Internet community. hadi-jhsua-ecnperf-01 INFORMATIONAL INFORMATIONAL RFC2885 Megaco Protocol version 0.8 F. Cuervo N. Greene C. Huitema A. Rayhan B. Rosen J. Segers August 2000 ASCII 344871 170 H.248 media gateway control This document is common text with Recommendation H.248 as redetermined in Geneva, February 2000. It must be read in conjunction with the Megaco Errata, RFC 2886. [STANDARDS TRACK] ietf-megaco-protocol-08 RFC3015 HISTORIC PROPOSED STANDARD RFC2886 Megaco Errata T. Taylor August 2000 ASCII 41311 21 H.248 media gateway control This document records the errors found in the Megaco/H.248 protocol document, along with the changes proposed in the text of that document to resolve them. [STANDARDS TRACK] ietf-megaco-errata-03 RFC3015 HISTORIC PROPOSED STANDARD RFC2887 The Reliable Multicast Design Space for Bulk Data Transfer M. Handley S. Floyd B. Whetten R. Kermode L. Vicisano M. Luby August 2000 ASCII 51135 22 application RM congestion control data This document provides an overview of the design space and the ways in which application constraints affect possible solutions. This memo provides information for the Internet community. ietf-rmt-design-space-01 INFORMATIONAL INFORMATIONAL RFC2888 Secure Remote Access with L2TP P. Srisuresh August 2000 ASCII 41255 19 layer two tunneling protocol The objective of this document is to extend security characteristics of IPsec to remote access users, as they dial-in through the Internet. This memo provides information for the Internet community. srisuresh-secure-ra-02 INFORMATIONAL INFORMATIONAL RFC2889 Benchmarking Methodology for LAN Switching Devices R. Mandeville J. Perser August 2000 ASCII 73251 35 local area network MAC medium access control This document is intended to provide methodology for the benchmarking of local area network (LAN) switching devices. This memo provides information for the Internet community. ietf-bmwg-mswitch-04 INFORMATIONAL INFORMATIONAL RFC2890 Key and Sequence Number Extensions to GRE G. Dommety September 2000 ASCII 14503 7 generic routing encapsulation This document describes extensions by which two fields, Key and Sequence Number, can be optionally carried in the GRE Header. [STANDARDS TRACK] dommety-gre-ext-04 PROPOSED STANDARD PROPOSED STANDARD RFC2891 LDAP Control Extension for Server Side Sorting of Search Results T. Howes M. Wahl A. Anantha August 2000 ASCII 15833 8 lightweight directory access protocol This document describes two LDAPv3 control extensions for server side sorting of search results. These controls allows a client to specify the attribute types and matching rules a server should use when returning the results to an LDAP search request. [STANDARDS TRACK] ietf-ldapext-sorting-03 PROPOSED STANDARD PROPOSED STANDARD RFC2892 The Cisco SRP MAC Layer Protocol D. Tsiang G. Suwala August 2000 ASCII 107645 52 spatial reuse This document specifies the MAC layer protocol, "Spatial Reuse Protocol" (SRP) for use with ring based media. This is a second version of the protocol (V2). This memo provides information for the Internet community. tsiang-srp-02 INFORMATIONAL INFORMATIONAL RFC2893 Transition Mechanisms for IPv6 Hosts and Routers R. Gilligan E. Nordmark August 2000 ASCII 62731 29 TRANS-IPV6 IPv4 This document specifies IPv4 compatibility mechanisms that can be implemented by IPv6 hosts and routers. [STANDARDS TRACK] ietf-ngtrans-mech-06 RFC1933 PROPOSED STANDARD PROPOSED STANDARD RFC2894 Router Renumbering for IPv6 M. Crawford August 2000 ASCII 69135 32 internet protocol operations scalability applicability This document defines a mechanism called Router Renumbering ("RR") which allows address prefixes on routers to be configured and reconfigured almost as easily as the combination of Neighbor Discovery and Address Autoconfiguration works for hosts. [STANDARDS TRACK] ietf-ipngwg-router-renum-10 PROPOSED STANDARD PROPOSED STANDARD RFC2895 Remote Network Monitoring MIB Protocol Identifier Reference A. Bierman C. Bucci R. Iddon August 2000 ASCII 88094 42 RMON-MIB management information base This memo defines a notation describing protocol layers in a protocol encapsulation, specifically for use in encoding INDEX values for the protocolDirTable, found in the RMON-2 MIB. [STANDARDS TRACK] ietf-rmonmib-rmonprot-ref-01 RFC2074 RFC3395 DRAFT STANDARD PROPOSED STANDARD RFC2896 Remote Network Monitoring MIB Protocol Identifier Macros A. Bierman C. Bucci R. Iddon August 2000 ASCII 135768 84 RMON management information base This memo contains various protocol identifier examples, which can be used to produce valid protocolDirTable INDEX encodings, as defined by the Remote Network Monitoring MIB and the RMON Protocol Identifier Reference. This memo provides information for the Internet community. ietf-rmonmib-rmonprot-mac-02 INFORMATIONAL INFORMATIONAL RFC2897 Proposal for an MGCP Advanced Audio Package D. Cromwell August 2000 ASCII 67459 34 media gateway control protocol IVR interactive voice response This document is a proposal to add a new event/signal package to the MGCP (Media Gateway Control Protocol) protocol to control an ARF (Audio Resource Function) which may reside on a Media Gateway or specialized Audio Server. This memo provides information for the Internet community. cromwell-mgcp-advanced-audio-pkg-00 INFORMATIONAL INFORMATIONAL RFC2898 PKCS #5: Password-Based Cryptography Specification Version 2.0 B. Kaliski September 2000 ASCII 68692 34 public-key authentication encryption This document provides recommendations for the implementation of password-based cryptography, covering key derivation functions, encryption schemes, message-authentication schemes, and ASN.1 syntax identifying the techniques. This memo provides information for the Internet community. kaliski-pcks5-v2-04 INFORMATIONAL INFORMATIONAL RFC2899 Request for Comments Summary RFC Numbers 2800-2899 S. Ginoza May 2001 ASCII 43805 22 INFORMATIONAL INFORMATIONAL RFC2900 Internet Official Protocol Standards J. Reynolds R. Braden S. Ginoza August 2001 ASCII 112809 42 This memo contains a snapshot of the state of standardization of protocols used in the Internet as of July 17, 2001. It lists official protocol standards and Best Current Practice RFCs; it is not a complete index to the RFC series. This memo is an Internet Standard. RFC2800 RFC3000 HISTORIC STANDARD RFC2901 Guide to Administrative Procedures of the Internet Infrastructure Z. Wenzel J. Klensin R. Bush S. Huter August 2000 ASCII 63680 31 address space routing database domain name registration This document describes the administrative procedures for networks seeking to connect to the global Internet. This memo provides information for the Internet community. wenzel-nsrc-02 FYI0037 INFORMATIONAL INFORMATIONAL RFC2902 Overview of the 1998 IAB Routing Workshop S. Deering S. Hares C. Perkins R. Perlman August 2000 ASCII 32773 16 internet architecture board This document is an overview of a Routing workshop held by the Internet Architecture Board (IAB) during March 25-27, 1998. This memo provides information for the Internet community. ietf-iab-rtrws-over-02 INFORMATIONAL INFORMATIONAL RFC2903 Generic AAA Architecture C. de Laat G. Gross L. Gommans J. Vollbrecht D. Spence August 2000 ASCII 60627 26 authentication authorization accounting This memo proposes an Authentication, Authorization, Accounting (AAA) architecture that would incorporate a generic AAA server along with an application interface to a set of Application Specific Modules that could perform application specific AAA functions. This memo defines an Experimental Protocol for the Internet community. irtf-aaaarch-generic-01 EXPERIMENTAL EXPERIMENTAL RFC2904 AAA Authorization Framework J. Vollbrecht P. Calhoun S. Farrell L. Gommans G. Gross B. de Bruijn C. de Laat M. Holdrege D. Spence August 2000 ASCII 78098 35 authentication authorization accounting This memo serves as the base requirements for Authorization of Internet Resources and Services (AIRS). It presents an architectural framework for understanding the authorization of Internet resources and services and derives requirements for authorization protocols. This memo provides information for the Internet community. irtf-aaaarch-authorization-framework-01 INFORMATIONAL INFORMATIONAL RFC2905 AAA Authorization Application Examples J. Vollbrecht P. Calhoun S. Farrell L. Gommans G. Gross B. de Bruijn C. de Laat M. Holdrege D. Spence August 2000 ASCII 118645 53 authentication authorization accounting This memo describes several examples of applications requiring authorization. This memo provides information for the Internet community. irtf-aaaarch-authorization-apps-01 INFORMATIONAL INFORMATIONAL RFC2906 AAA Authorization Requirements S. Farrell J. Vollbrecht P. Calhoun L. Gommans G. Gross B. de Bruijn C. de Laat M. Holdrege D. Spence August 2000 ASCII 48618 23 authentication authorization accounting This document specifies the requirements that Authentication Authorization Accounting (AAA) protocols must meet in order to support authorization services in the Internet. This memo provides information for the Internet community. irtf-aaaarch-authorization-reqs-01 INFORMATIONAL INFORMATIONAL RFC2907 MADCAP Multicast Scope Nesting State Option R. Kermode September 2000 ASCII 27572 13 address dynamic allocation client protocol This document defines a new option to the Multicast Address Dynamic Client Allocation Protocol (MADCAP) to support nested scoping. [STANDARDS TRACK] ietf-malloc-madcap-nest-opt-05 PROPOSED STANDARD PROPOSED STANDARD RFC2908 The Internet Multicast Address Allocation Architecture D. Thaler M. Handley D. Estrin September 2000 ASCII 30515 13 MALLOC host server intra-domain inter-domain This document proposes a multicast address allocation architecture (MALLOC) for the Internet. This memo provides information for the Internet community. ietf-malloc-arch-05 INFORMATIONAL INFORMATIONAL RFC2909 The Multicast Address-Set Claim (MASC) Protocol P. Radoslavov D. Estrin R. Govindan M. Handley S. Kumar D. Thaler September 2000 ASCII 127278 56 MASC inter-domain router This document describes the Multicast Address-Set Claim (MASC) protocol which can be used for inter-domain multicast address set allocation. This memo defines an Experimental Protocol for the Internet community. ietf-malloc-masc-06 EXPERIMENTAL EXPERIMENTAL RFC2910 Internet Printing Protocol/1.1: Encoding and Transport R. Herriot Editor S. Butler P. Moore R. Turner J. Wenn September 2000 ASCII 100599 46 IPP-E-T IPP application media-type media type This document is one of a set of documents, which together describe all aspects of a new Internet Printing Protocol (IPP). [STANDARDS TRACK] ietf-ipp-protocol-v11-06 RFC2565 RFC3380 RFC3381 RFC3382 RFC3510 RFC3995 PROPOSED STANDARD PROPOSED STANDARD RFC2911 Internet Printing Protocol/1.1: Model and Semantics T. Hastings Editor R. Herriot R. deBry S. Isaacson P. Powell September 2000 ASCII 575805 224 IPP-M-S IPP application media-type job This document is one of a set of documents, which together describe all aspects of a new Internet Printing Protocol (IPP). [STANDARDS TRACK] ietf-ipp-model-v11-07 RFC2566 RFC3380 RFC3382 RFC3996 RFC3995 PROPOSED STANDARD PROPOSED STANDARD RFC2912 Indicating Media Features for MIME Content G. Klyne September 2000 ASCII 20618 11 multipurpose mail extensions tag format This memo defines a Multipurpose Internet Mail Extensions (MIME) ' Content-features:' header that can be used to annotate a MIME message part using this expression format, and indicates some ways it might be used. [STANDARDS TRACK] ietf-conneg-content-features-03 PROPOSED STANDARD PROPOSED STANDARD RFC2913 MIME Content Types in Media Feature Expressions G. Klyne September 2000 ASCII 16095 9 multipurpose mail extensions tag format This memo defines a media feature tag whose value is a Multipurpose Internet Mail Extensions (MIME) content type. [STANDARDS TRACK] ietf-conneg-feature-type-03 PROPOSED STANDARD PROPOSED STANDARD RFC2914 Congestion Control Principles S. Floyd September 2000 ASCII 43823 17 end-to-end The goal of this document is to explain the need for congestion control in the Internet, and to discuss what constitutes correct congestion control. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. floyd-cong-04 BCP0041 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2915 The Naming Authority Pointer (NAPTR) DNS Resource Record M. Mealling R. Daniel September 2000 ASCII 41521 18 NAPTR domain name system RR This document describes a Domain Name System (DNS) resource record which specifies a regular expression based rewrite rule that, when applied to an existing string, will produce a new domain label or Uniform Resource Identifier (URI). [STANDARDS TRACK] ietf-urn-naptr-rr-04 RFC3401 RFC3402 RFC3403 RFC3404 RFC2168 PROPOSED STANDARD PROPOSED STANDARD RFC2916 E.164 number and DNS P. Faltstrom September 2000 ASCII 18159 10 domain name system This document discusses the use of the Domain Name System (DNS) for storage of E.164 numbers. [Standards Track] ietf-enum-e164-dns-03 RFC3761 PROPOSED STANDARD PROPOSED STANDARD RFC2917 A Core MPLS IP VPN Architecture K. Muthukrishnan A. Malis September 2000 ASCII 35352 16 internet protocol virtual private networks multiprotocol label switching This memo presents an approach for building core Virtual Private Network (VPN) services in a service provider's MPLS backbone. This memo provides information for the Internet community. muthurkrishnan-mpls-corevpn-arch-03 INFORMATIONAL INFORMATIONAL RFC2918 Route Refresh Capability for BGP-4 E. Chen September 2000 ASCII 7354 4 border gateway protocol This document defines a new Border Gateway Protocol (BGP) capability termed 'Route Refresh Capability', which would allow the dynamic exchange of route refresh request between BGP speakers and subsequent re-advertisement of the respective Adj-RIB-Out. [STANDARDS TRACK] ietf-idr-bgp-route-refresh-01 PROPOSED STANDARD PROPOSED STANDARD RFC2919 List-Id: A Structured Field and Namespace for the Identification of Mailing Lists R. Chandhok G. Wenger March 2001 ASCII 18480 9 server clients user agents Software that handles electronic mailing list messages (servers and user agents) needs a way to reliably identify messages that belong to a particular mailing list. With the advent of list management headers, it has become even more important to provide a unique identifier for a mailing list regardless of the particular host that serves as the list processor at any given time. [STANDARDS TRACK] chandhok-listid-04 PROPOSED STANDARD PROPOSED STANDARD RFC2920 SMTP Service Extension for Command Pipelining N. Freed September 2000 ASCII 17065 9 SMTP-Pipe simple mail transfer protocol TCP transmission control protocol This memo defines an extension to the Simple Mail Transfer Protocol (SMTP) service whereby a server can indicate the extent of its ability to accept multiple commands in a single Transmission Control Protocol (TCP) send operation. [STANDARDS TRACK] freed-smtp-pipe-01 RFC2197 STD0060 STANDARD STANDARD RFC2921 6BONE pTLA and pNLA Formats (pTLA) B. Fink September 2000 ASCII 14218 7 IPv6 internet protocol pseudo top-level next-level aggregation identifiers This memo defines how the 6bone uses the 3FFE::/16 IPv6 address prefix, allocated in RFC 2471, "IPv6 Testing Address Allocation", to create pseudo Top-Level Aggregation Identifiers (pTLA's) and pseudo Next-Level Aggregation Identifiers (pNLA's). This memo provides information for the Internet community. ietf-ngtrans-6bone-ptla-00 INFORMATIONAL INFORMATIONAL RFC2922 Physical Topology MIB A. Bierman K. Jones September 2000 ASCII 66830 32 management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing physical topology identification and discovery. This memo provides information for the Internet community. ietf-ptopomib-mib-05 INFORMATIONAL INFORMATIONAL RFC2923 TCP Problems with Path MTU Discovery K. Lahey September 2000 ASCII 30976 15 transmission control protocol maximum unit This memo catalogs several known Transmission Control Protocol (TCP) implementation problems dealing with Path Maximum Transmission Unit Discovery (PMTUD), including the long-standing black hole problem, stretch acknowlegements (ACKs) due to confusion between Maximum Segment Size (MSS) and segment size, and MSS advertisement based on PMTU. This memo provides information for the Internet community. ietf-tcpimpl-pmtud-04 INFORMATIONAL INFORMATIONAL RFC2924 Accounting Attributes and Record Formats N. Brownlee A. Blount September 2000 ASCII 75561 36 data transport integrated This document summarises Internet Engineering Task Force (IETF) and International Telecommunication Union (ITU-T) documents related to Accounting. This memo provides information for the Internet community. ietf-aaa-accounting-attribute-04 INFORMATIONAL INFORMATIONAL RFC2925 Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations K. White September 2000 ASCII 150691 77 mib management information base This memo defines Management Information Bases (MIBs) for performing remote ping, traceroute and lookup operations at a remote host. [STANDARDS TRACK] ietf-disman-remops-mib-08 PROPOSED STANDARD PROPOSED STANDARD RFC2926 Conversion of LDAP Schemas to and from SLP Templates J. Kempf R. Moats P. St. Pierre September 2000 ASCII 55365 27 service location protocol lightweight directory access This document describes a procedure for mapping between Service Location Protocol (SLP) service advertisements and lightweight directory access protocol (LDAP) descriptions of services. This memo provides information for the Internet community. ietf-svcloc-template-conversion-08 INFORMATIONAL INFORMATIONAL RFC2927 MIME Directory Profile for LDAP Schema M. Wahl September 2000 ASCII 16122 10 lightweight directory access protocol multipurpose internet mail extensions This document defines a multipurpose internet mail extensions (MIME) directory profile for holding a lightweight directory access protocol (LDAP) schema. This memo provides information for the Internet community. ietf-schema-ldap-01 INFORMATIONAL INFORMATIONAL RFC2928 Initial IPv6 Sub-TLA ID Assignments R. Hinden S. Deering R. Fink T. Hain September 2000 ASCII 11882 7 internet protocol sub-top-level aggregation identifiers address registries This document defines initial assignments of IPv6 Sub-Top-Level Aggregation Identifiers (Sub-TLA ID) to the Address Registries. This memo provides information for the Internet community. ietf-ipngwg-iana-tla-03 INFORMATIONAL INFORMATIONAL RFC2929 Domain Name System (DNS) IANA Considerations D. Eastlake 3rd E. Brunner-Williams B. Manning September 2000 ASCII 22454 12 internet assigned numbers authority resource records RRs This document discusses the Internet Assigned Number Authority (IANA) parameter assignment considerations given for the allocation of Domain Name System (DNS) classes, Resource Record (RR) types, operation codes, error codes, etc. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-dnsext-iana-dns-01 BCP0042 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2930 Secret Key Establishment for DNS (TKEY RR) D. Eastlake 3rd September 2000 ASCII 34894 16 TKEY-RR domain name system resource record transaction key This document describes a Transaction Key (TKEY) RR that can be used in a number of different modes to establish shared secret keys between a DNS resolver and server. [STANDARDS TRACK] ietf-dnsext-tkey-04 PROPOSED STANDARD PROPOSED STANDARD RFC2931 DNS Request and Transaction Signatures ( SIG(0)s ) D. Eastlake 3rd September 2000 ASCII 19073 10 domain name system data security This document describes the minor but non-interoperable changes in Request and Transaction signature resource records ( SIG(0)s ) that implementation experience has deemed necessary. [STANDARDS TRACK] ietf-dnsext-sig-zero-02 RFC2535 PROPOSED STANDARD PROPOSED STANDARD RFC2932 IPv4 Multicast Routing MIB K. McCloghrie D. Farinacci D. Thaler October 2000 ASCII 50430 27 internet protocol management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing IP Multicast Routing for IPv4, independent of the specific multicast routing protocol in use. [STANDARDS TRACK] ietf-idmr-multicast-routmib-13 PROPOSED STANDARD PROPOSED STANDARD RFC2933 Internet Group Management Protocol MIB K. McCloghrie D. Farinacci D. Thaler October 2000 ASCII 33406 19 igmp management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing the Internet Group Management Protocol (IGMP). [STANDARDS TRACK] ietf-idmr-igmp-mib-14 PROPOSED STANDARD PROPOSED STANDARD RFC2934 Protocol Independent Multicast MIB for IPv4 K. McCloghrie D. Farinacci D. Thaler B. Fenner October 2000 ASCII 48379 27 internet protocol management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing the Protocol Independent Multicast (PIM) protocol for IPv4. This memo defines an Experimental Protocol for the Internet community. ietf-idmr-pim-mib-11 EXPERIMENTAL EXPERIMENTAL RFC2935 Internet Open Trading Protocol (IOTP) HTTP Supplement D. Eastlake 3rd C. Smith September 2000 ASCII 16168 8 IOTP-HTTP hypertext XML extensible markup language transfer The goal of mapping to the transport layer is to ensure that the underlying XML documents are carried successfully between the various parties. This document describes that mapping for the Hyper Text Transport Protocol (HTTP), Versions 1.0 and 1.1. [STANDARDS TRACK] ietf-trade-iotp-http-07 PROPOSED STANDARD PROPOSED STANDARD RFC2936 HTTP MIME Type Handler Detection D. Eastlake 3rd C. Smith D. Soroka September 2000 ASCII 25238 13 multipurpose internet mail extensions hypertext transfer protocol Entities composing web pages to provide services over the Hypertext Transfer Protocol (HTTP) frequently have the problem of not knowing what Multipurpose Internet Mail Extensions (MIME) types have handlers installed at a user's browser. This document summarizes reasonable techniques to solve this problem for most of the browsers actually deployed on the Internet as of early 2000. This memo provides information for the Internet community. ietf-trade-mime-detector-03 INFORMATIONAL INFORMATIONAL RFC2937 The Name Service Search Option for DHCP C. Smith September 2000 ASCII 8368 5 dynamic host configuration protocol This document defines a new Dynamic Host Configuration Protocol (DHCP) option which is passed from the DHCP Server to the DHCP Client to specify the order in which name services should be consulted when resolving hostnames and other information. [STANDARDS TRACK] ietf-dhc-nsso-05 PROPOSED STANDARD PROPOSED STANDARD RFC2938 Identifying Composite Media Features G. Klyne L. Masinter September 2000 ASCII 34451 18 tags expression hash This document describes an abbreviated format for a composite media feature set, based upon a hash of the feature expression describing that composite. [STANDARDS TRACK] ietf-conneg-feature-hash-05 RFC2533 PROPOSED STANDARD PROPOSED STANDARD RFC2939 Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types R. Droms September 2000 ASCII 13631 7 dynamic host configuration protocol internet assigned numbers authority This document describes the procedure for defining new DHCP options and message types. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-dhc-new-opt-msg-02 RFC2489 BCP0043 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2940 Definitions of Managed Objects for Common Open Policy Service (COPS) Protocol Clients A. Smith D. Partain J. Seligson October 2000 ASCII 52427 27 cops mib management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for managing a client of the Common Open Policy Service (COPS) protocol. [STANDARDS TRACK] ietf-rap-cops-client-mib-03 PROPOSED STANDARD PROPOSED STANDARD RFC2941 Telnet Authentication Option T. Ts'o Editor J. Altman September 2000 ASCII 52427 15 TOPT-AUTH encryption Security This document describes the authentication option to the telnet protocol as a generic method for negotiating an authentication type and mode including whether encryption should be used and if credentials should be forwarded. [STANDARDS TRACK] tso-telnet-auth-enc-05 RFC1416 PROPOSED STANDARD PROPOSED STANDARD RFC2942 Telnet Authentication: Kerberos Version 5 T. Ts'o September 2000 ASCII 14562 7 encryption This document describes how Kerberos Version 5 is used with the telnet protocol. It describes an telnet authentication suboption to be used with the telnet authentication option. [STANDARDS TRACK] tso-telnet-krb5-04 PROPOSED STANDARD PROPOSED STANDARD RFC2943 TELNET Authentication Using DSA R. Housley T. Horting P. Yee September 2000 ASCII 21694 12 digital signature algorithm This document defines a telnet authentication mechanism using the Digital Signature Algorithm (DSA). It relies on the Telnet Authentication Option. [STANDARDS TRACK] housley-telnet-auth-dsa-05 PROPOSED STANDARD PROPOSED STANDARD RFC2944 Telnet Authentication: SRP T. Wu September 2000 ASCII 13933 7 secure remote password protocol This document specifies an authentication scheme for the Telnet protocol under the framework described in RFC 2941, using the Secure Remote Password Protocol (SRP) authentication mechanism. [STANDARDS TRACK] wu-telnet-auth-srp-05 PROPOSED STANDARD PROPOSED STANDARD RFC2945 The SRP Authentication and Key Exchange System T. Wu September 2000 ASCII 17843 8 secure remote password protocol This document describes a cryptographically strong network authentication mechanism known as the Secure Remote Password (SRP) protocol. [STANDARDS TRACK] wu-srp-auth-03 PROPOSED STANDARD PROPOSED STANDARD RFC2946 Telnet Data Encryption Option T. Ts'o September 2000 ASCII 16527 8 stream authentication This document describes a the telnet encryption option as a generic method of providing data confidentiality services for the telnet data stream. [STANDARDS TRACK] tso-telnet-encryption-04 PROPOSED STANDARD PROPOSED STANDARD RFC2947 Telnet Encryption: DES3 64 bit Cipher Feedback J. Altman September 2000 ASCII 11064 6 data encryption standard This document specifies how to use the Triple-DES (data encryption standard) encryption algorithm in cipher feedback mode with the telnet encryption option. [STANDARDS TRACK] altman-telnet-enc-des3-cfb-01 PROPOSED STANDARD PROPOSED STANDARD RFC2948 Telnet Encryption: DES3 64 bit Output Feedback J. Altman September 2000 ASCII 11064 6 data encryption standard This document specifies how to use the Triple-DES (data encryption standard) encryption algorithm in output feedback mode with the telnet encryption option. [STANDARDS TRACK] altman-telnet-enc-des3-ofb-01 PROPOSED STANDARD PROPOSED STANDARD RFC2949 Telnet Encryption: CAST-128 64 bit Output Feedback J. Altman September 2000 ASCII 9240 5 algorithm option This document specifies how to use the CAST-128 encryption algorithm in output feedback mode with the telnet encryption option. Two key sizes are defined: 40 bit and 128 bit. [STANDARDS TRACK] altman-telnet-enc-cast128-ofb-00 PROPOSED STANDARD PROPOSED STANDARD RFC2950 Telnet Encryption: CAST-128 64 bit Cipher Feedback J. Altman September 2000 ASCII 9267 5 algorithm option This document specifies how to use the CAST-128 encryption algorithm in cipher feedback mode with the telnet encryption option. Two key sizes are defined: 40 bit and 128 bit. [STANDARDS TRACK] altman-telnet-enc-cast128-cfb-00 PROPOSED STANDARD PROPOSED STANDARD RFC2951 TELNET Authentication Using KEA and SKIPJACK R. Housley T. Horting P. Yee September 2000 ASCII 20757 11 key exchange algorithm encryption This document defines a method to authenticate TELNET using the Key Exchange Algorithm (KEA), and encryption of the TELNET stream using SKIPJACK. This memo provides information for the Internet community. housely-telnet-auth-keasj-05 INFORMATIONAL INFORMATIONAL RFC2952 Telnet Encryption: DES 64 bit Cipher Feedback T. Ts'o September 2000 ASCII 9064 5 data encryption standard This document specifies how to use the DES encryption algorithm in cipher feedback mode with the telnet encryption option. This memo provides information for the Internet community. tso-telnet-enc-des-cfb-04 INFORMATIONAL INFORMATIONAL RFC2953 Telnet Encryption: DES 64 bit Output Feedback T. Ts'o September 2000 ASCII 8995 5 data encryption standard This document specifies how to use the data encryption standard (DES) encryption algorithm in output feedback mode with the telnet encryption option. This memo provides information for the Internet community. tso-telnet-enc-des-ofb-04 INFORMATIONAL INFORMATIONAL RFC2954 Definitions of Managed Objects for Frame Relay Service K. Rehbehn D. Fowler October 2000 ASCII 164217 76 FR-MIB mib management information base This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in Transmission Control Protocol/Internet Protocol-based (TCP/IP) internets. In particular, it defines objects for managing the frame relay service. [STANDARDS TRACK] ietf-frnetmib-frs-mib-12 RFC1604 PROPOSED STANDARD PROPOSED STANDARD RFC2955 Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function K. Rehbehn O. Nicklass G. Mouradian October 2000 ASCII 83281 39 asynchronous transfer mode permanent virtual connections MIB management information base This memo defines a Management Information Base (MIB) to configure, monitor, and control a service interworking function (IWF) for Permanent Virtual Connections (PVC) between Frame Relay and Asynchronous Transfer Mode (ATM) technologies. [STANDARDS TRACK] ietf-frnetmib-atmiwf-06 PROPOSED STANDARD PROPOSED STANDARD RFC2956 Overview of 1999 IAB Network Layer Workshop M. Kaat October 2000 ASCII 36830 16 intenret architecture board This document is an overview of a workshop held by the Internet Architecture Board (IAB) on the Internet Network Layer architecture hosted by SURFnet in Utrecht, the Netherlands on 7-9 July 1999. The goal of the workshop was to understand the state of the network layer and its impact on continued growth and usage of the Internet. This memo provides information for the Internet community. iab-ntwlyrws-over-02 INFORMATIONAL INFORMATIONAL RFC2957 The application/whoispp-query Content-Type L. Daigle P. Faltstrom October 2000 ASCII 10262 6 mime multipurpose internet mail extensions media-types The intention of this document, in conjunction with RFC 2958, is to enable MIME-enabled mail software, and other systems using Internet media types, to carry out Whois++ transactions. This memo provides information for the Internet community. daigle-wppresp-02 INFORMATIONAL INFORMATIONAL RFC2958 The application/whoispp-response Content-type L. Daigle P. Faltstrom October 2000 ASCII 9995 6 mime multipurpose internet mail extensions media-types The intention of this document, in conjunction with RFC 2957, is to enable MIME-enabled mail software, and other systems using Internet media types, to carry out Whois++ transactions. This memo provides information for the Internet community. daigle-wppquery-02 INFORMATIONAL INFORMATIONAL RFC2959 Real-Time Transport Protocol Management Information Base M. Baugher B. Strahm I. Suconick October 2000 ASCII 62063 31 RTP MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS TRACK] ietf-avt-rtp-mib-13 PROPOSED STANDARD PROPOSED STANDARD RFC2960 Stream Control Transmission Protocol R. Stewart Q. Xie K. Morneault C. Sharp H. Schwarzbauer T. Taylor I. Rytina M. Kalla L. Zhang V. Paxson October 2000 ASCII 297757 134 SCTP IP internet transport packet network This document describes the Stream Control Transmission Protocol (SCTP). [STANDARDS TRACK] ietf-sigtran-sctp-13 RFC3309 PROPOSED STANDARD PROPOSED STANDARD RFC2961 RSVP Refresh Overhead Reduction Extensions L. Berger D. Gan G. Swallow P. Pan F. Tommasi S. Molendini April 2001 ASCII 81675 34 resource reservation protocol messages This document describes a number of mechanisms that can be used to reduce processing overhead requirements of refresh messages, eliminate the state synchronization latency incurred when an RSVP (Resource ReserVation Protocol) message is lost and, when desired, refreshing state without the transmission of whole refresh messages. [STANDARDS TRACK] ietf-rsvp-refresh-reduct-05 PROPOSED STANDARD PROPOSED STANDARD RFC2962 An SNMP Application Level Gateway for Payload Address Translation D. Raz J. Schoenwaelder B. Sugla October 2000 ASCII 46803 20 simple network management protocol This document describes the ALG (Application Level Gateway) for the SNMP (Simple Network Management Protocol) by which IP (Internet Protocol) addresses in the payload of SNMP packets are statically mapped from one group to another. This memo provides information for the Internet community. ietf-nat-snmp-alg-05 INFORMATIONAL INFORMATIONAL RFC2963 A Rate Adaptive Shaper for Differentiated Services O. Bonaventure S. De Cnodder October 2000 ASCII 39895 19 RAS TCP transmission control protocol diffserv This memo describes several Rate Adaptive Shapers (RAS) that can be used in combination with the single rate Three Color Markers (srTCM) and the two rate Three Color Marker (trTCM) described in RFC2697 and RFC2698, respectively. This memo provides information for the Internet community. bonaventure-diffserv-rashaper-02 INFORMATIONAL INFORMATIONAL RFC2964 Use of HTTP State Management K. Moore N. Freed October 2000 ASCII 18899 8 hypertext transfer protocol This memo identifies specific uses of Hypertext Transfer Protocol (HTTP) State Management protocol which are either (a) not recommended by the IETF, or (b) believed to be harmful, and discouraged. This memo also details additional privacy considerations which are not covered by the HTTP State Management protocol specification. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. iesg-http-cookies-03 BCP0044 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2965 HTTP State Management Mechanism D. Kristol L. Montulli October 2000 ASCII 56176 26 hypertext transfer protocol This document specifies a way to create a stateful session with Hypertext Transfer Protocol (HTTP) requests and responses. [STANDARDS TRACK] ietf-http-state-man-mec-12 RFC2109 PROPOSED STANDARD PROPOSED STANDARD RFC2966 Domain-wide Prefix Distribution with Two-Level IS-IS T. Li T. Przygienda H. Smit October 2000 ASCII 32465 14 intermediate system routers loops IP internet protocol This document describes extensions to the Intermediate System to Intermediate System (IS-IS) protocol to support optimal routing within a two-level domain. This memo provides information for the Internet community. ietf-isis-domain-wide-03 INFORMATIONAL INFORMATIONAL RFC2967 TISDAG - Technical Infrastructure for Swedish Directory Access Gateways L. Daigle R. Hedberg October 2000 ASCII 209845 105 single point service The overarching goal of this project is to develop the necessary technical infrastructure to provide a single-access-point service for searching for whitepages information on Swedish Internet users. This memo provides information for the Internet community. daigle-tisdag-02 INFORMATIONAL INFORMATIONAL RFC2968 Mesh of Multiple DAG servers - Results from TISDAG L. Daigle T. Eklof October 2000 ASCII 19306 9 technical infrastructure swedish directory access gateways mesh index This document defines the basic principle for establishing a mesh, that interoperating services should exchange index objects, according to the architecture of the mesh (e.g., hierarchical, or graph-like, preferably without loops!). The Common Indexing Protocol (CIP) is designed to facilitate the creation not only of query referral indexes, but also of meshes of (loosely) affiliated referral indexes. The purpose of such a mesh of servers is to implement some kind of distributed sharing of indexing and/or searching tasks across different servers. So far, the TISDAG (Technical Infrastructure for Swedish Directory Access Gateways) project has focused on creating a single referral index; the obvious next step is to integrate that into a larger set of interoperating services. This memo provides information for the Internet community. daigle-dag-mesh-02 INFORMATIONAL INFORMATIONAL RFC2969 Wide Area Directory Deployment - Experiences from TISDAG T. Eklof L. Daigle October 2000 ASCII 43002 19 technical infrastructure swedish access gateways This document catalogues some of the experiences gained in developing the necessary infrastructure for a national (i.e., multi-organizational) directory service and pilot deployment of the service in an environment with off-the-shelf directory service products. This memo provides information for the Internet community. eklof-dag-experiences-04 INFORMATIONAL INFORMATIONAL RFC2970 Architecture for Integrated Directory Services - Result from TISDAG L. Daigle T. Eklof October 2000 ASCII 40448 18 ids whitepages technical infrastructure swedish access gateways Drawing from experiences with the TISDAG (Technical Infrastructure for Swedish Directory Access Gateways) project, this document outlines an approach to providing the necessary infrastructure for integrating such widely-scattered servers into a single service, rather than attempting to mandate a single protocol and schema set for all participating servers to use. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2971 IMAP4 ID extension T. Showalter October 2000 ASCII 14670 8 internet message access protocol client server This document describes an ID extension which will enable Internet Message Access Protocol - Version 4rev1 (IMAP4rev1) to advertise what program a client or server uses to provide service. The ID extension allows the server and client to exchange identification information on their implementation in order to make bug reports and usage statistics more complete. [STANDARDS TRACK] ietf-isis-wg-mesh-group-01 PROPOSED STANDARD PROPOSED STANDARD RFC2972 Context and Goals for Common Name Resolution N. Popp M. Mealling L. Masinter K. Sollins October 2000 ASCII 26252 11 CNRP This document establishes the context and goals for a Common Name Resolution Protocol. This memo provides information for the Internet community. ietf-cnrp-goals-01 INFORMATIONAL INFORMATIONAL RFC2973 IS-IS Mesh Groups R. Balay D. Katz J. Parker October 2000 ASCII 14846 8 intermediate system PDU protocol data unit This document describes a mechanism to reduce redundant packet transmissions for the Intermediate System to Intermediate System (IS-IS) Routing protocol, as described in ISO 10589. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC2974 Session Announcement Protocol M. Handley C. Perkins E. Whelan October 2000 ASCII 40129 18 SAP This document describes version 2 of the multicast session directory announcement protocol, Session Announcement Protocol (SAP), and the related issues affecting security and scalability that should be taken into account by implementors. This memo defines an Experimental Protocol for the Internet community. ietf-mmusic-sap-v2-06 EXPERIMENTAL EXPERIMENTAL RFC2975 Introduction to Accounting Management B. Aboba J. Arkko D. Harrington October 2000 ASCII 129771 54 resource consumption data cost allocation This document describes and discusses the issues involved in the design of the modern accounting systems. The field of Accounting Management is concerned with the collection the collection of resource consumption data for the purposes of capacity and trend analysis, cost allocation, auditing, and billing. This memo provides information for the Internet community. ietf-aaa-acct-06 INFORMATIONAL INFORMATIONAL RFC2976 The SIP INFO Method S. Donovan October 2000 ASCII 17736 9 session initiation protocol information extension This document proposes an extension to the Session Initiation Protocol (SIP). This extension adds the INFO method to the SIP protocol. The intent of the INFO method is to allow for the carrying of session related control information that is generated during a session. [STANDARDS TRACK] ietf-sip-info-method-05 PROPOSED STANDARD PROPOSED STANDARD RFC2977 Mobile IP Authentication, Authorization, and Accounting Requirements S. Glass T. Hiller S. Jacobs C. Perkins October 2000 ASCII 63520 27 AAA internet protocol This document contains the requirements which would have to be supported by a AAA service to aid in providing Mobile IP services. This memo provides information for the Internet community. ietf-mobileip-aaa-reqs-04 INFORMATIONAL INFORMATIONAL RFC2978 IANA Charset Registration Procedures N. Freed J. Postel October 2000 ASCII 21615 11 character set mime multipurpose internet mail extensions Multipurpose Internet Mail Extensions (MIME) and various other Internet protocols are capable of using many different charsets. This in turn means that the ability to label different charsets is essential. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. freed-charset-regist-03 RFC2278 BCP0019 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC2979 Behavior of and Requirements for Internet Firewalls N. Freed October 2000 ASCII 14350 7 security intranet network This memo defines behavioral characteristics of and interoperability requirements for Internet firewalls. This memo provides information for the Internet community. iab-firewall-req-02 INFORMATIONAL INFORMATIONAL RFC2980 Common NNTP Extensions S. Barber October 2000 ASCII 57165 27 network news transfer protocol In this document, a number of popular extensions to the Network News Transfer Protocol (NNTP) protocol defined in RFC 977 are documented and discussed. While this document is not intended to serve as a standard of any kind, it will hopefully serve as a reference document for future implementers of the NNTP protocol. This memo provides information for the Internet community. ietf-nntpext-imp-04 INFORMATIONAL INFORMATIONAL RFC2981 Event MIB R. Kavasseri (Ed. of this version) October 2000 ASCII 98248 50 management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects that can be used to manage and monitor MIB objects and take action through events. [STANDARDS TRACK] ietf-disman-event-mib-10 PROPOSED STANDARD PROPOSED STANDARD RFC2982 Distributed Management Expression MIB R. Kavasseri (Ed. of this version) October 2000 ASCII 81371 41 information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing expressions of MIB objects. [STANDARDS TRACK] ietf-disman-express-mib-12 PROPOSED STANDARD PROPOSED STANDARD RFC2983 Differentiated Services and Tunnels D. Black October 2000 ASCII 35644 14 internet protocol encapsulation This document considers the interaction of Differentiated Services (diffserv) with IP tunnels of various forms. This memo provides information for the Internet community. ietf-diffserv-tunnels-02 INFORMATIONAL INFORMATIONAL RFC2984 Use of the CAST-128 Encryption Algorithm in CMS C. Adams October 2000 ASCII 11591 6 cryptographic message syntax security cipher This document specifies how to incorporate CAST-128 into the S/MIME Cryptographic Message Syntax (CMS) as an additional algorithm for symmetric encryption. [STANDARDS TRACK] ietf-smime-cast-128-02 PROPOSED STANDARD PROPOSED STANDARD RFC2985 PKCS #9: Selected Object Classes and Attribute Types Version 2.0 M. Nystrom B. Kaliski November 2000 ASCII 70703 42 public-key cryptography standards LDAP lightweight directory access protocol This memo represents a republication of PKCS #9 v2.0 from RSA Laboratories' Public-Key Cryptography Standards (PKCS) series, and change control is retained within the PKCS process. The body of this document, except for the security considerations section, is taken directly from that specification. This memo provides information for the Internet community. nystrom-pkcs9-v2-01 INFORMATIONAL INFORMATIONAL RFC2986 PKCS #10: Certification Request Syntax Specification Version 1.7 M. Nystrom B. Kaliski November 2000 ASCII 27794 14 public-key cryptography standards PKCS-10 public key distinguished name encryption data This memo represents a republication of PKCS #10 v1.7 from RSA Laboratories' Public-Key Cryptography Standards (PKCS) series, and change control is retained within the PKCS process. The body of this document, except for the security considerations section, is taken directly from the PKCS #9 v2.0 or the PKCS #10 v1.7 document. This memo provides information for the Internet community. nystrom-pkcs10-v1-7-00 RFC2314 INFORMATIONAL INFORMATIONAL RFC2987 Registration of Charset and Languages Media Features Tags P. Hoffman November 2000 ASCII 8799 6 character sets human languages devices This document contains the registration for two media feature tags: "charset" and "language". [STANDARDS TRACK] hoffman-char-lang-media-03 PROPOSED STANDARD PROPOSED STANDARD RFC2988 Computing TCP's Retransmission Timer V. Paxson M. Allman November 2000 ASCII 15280 8 transmission control protocol algorithm This document defines the standard algorithm that Transmission Control Protocol (TCP) senders are required to use to compute and manage their retransmission timer. [STANDARDS TRACK] paxson-tcp-rto-01 PROPOSED STANDARD PROPOSED STANDARD RFC2989 Criteria for Evaluating AAA Protocols for Network Access B. Aboba P. Calhoun S. Glass T. Hiller P. McCann H. Shiino G. Zorn G. Dommety C. Perkins B. Patil D. Mitton S. Manning M. Beadles P. Walsh X. Chen S. Sivalingham A. Hameed M. Munson S. Jacobs B. Lim B. Hirschman R. Hsu Y. Xu E. Campbell S. Baba E. Jaques November 2000 ASCII 53197 28 authentication authorization accounting This document represents a summary of Authentication, Authorization, Accounting (AAA) protocol requirements for network access. This memo provides information for the Internet community. ietf-aaa-na-reqts-07 INFORMATIONAL INFORMATIONAL RFC2990 Next Steps for the IP QoS Architecture G. Huston November 2000 ASCII 65450 24 internet protocol quality of service end-to-end This document highlights the outstanding architectural issues relating to the deployment and use of QoS mechanisms within internet networks, noting those areas where further standards work may assist with the deployment of QoS internets. This document is the outcome of a collaborative exercise on the part of the Internet Architecture Board. This memo provides information for the Internet community. iab-qos-02 INFORMATIONAL INFORMATIONAL RFC2991 Multipath Issues in Unicast and Multicast Next-Hop Selection D. Thaler C. Hopps November 2000 ASCII 17796 9 routing forwarding packets ECMP The effect of multipath routing on a forwarder is that the forwarder potentially has several next-hops for any given destination and must use some method to choose which next-hop should be used for a given data packet. This memo summarizes current practices, problems, and solutions. This memo provides information for the Internet community. thaler-multipath-05 INFORMATIONAL INFORMATIONAL RFC2992 Analysis of an Equal-Cost Multi-Path Algorithm C. Hopps November 2000 ASCII 17524 8 ECMP routing packets forwarding Equal-cost multi-path (ECMP) is a routing technique for routing packets along multiple paths of equal cost. The forwarding engine identifies paths by next-hop. When forwarding a packet the router must decide which next-hop (path) to use. This document gives an analysis of one method for making that decision. The analysis includes the performance of the algorithm and the disruption caused by changes to the set of next-hops. This memo provides information for the Internet community. hopps-ecmp-algo-analysis-04 INFORMATIONAL INFORMATIONAL RFC2993 Architectural Implications of NAT T. Hain November 2000 ASCII 74136 29 network address translation This document discusses some of the architectural implications and guidelines for implementations of Network Address Translation (NAT). This memo provides information for the Internet community. iab-nat-implications-09 INFORMATIONAL INFORMATIONAL RFC2994 A Description of the MISTY1 Encryption Algorithm H. Ohta M. Matsui November 2000 ASCII 17803 10 cryptosystem security data stream This document describes a secret-key cryptosystem MISTY1, which is block cipher with a 128-bit key, a 64-bit block and a variable number of rounds. It documents the algorithm description including key scheduling part and data randomizing part. This memo provides information for the Internet community. ohta-misty1desc-02 INFORMATIONAL INFORMATIONAL RFC2995 Pre-Spirits Implementations of PSTN-initiated Services H. Lu Editor I. Faynberg J. Voelker M. Weissman W. Zhang S. Rhim J. Hwang S. Ago S. Moeenuddin S. Hadvani S. Nyckelgard J. Yoakum L. Robart November 2000 ASCII 96427 44 public switched telephone network This document describes four existing implementations of SPIRITS-like services from Korea Telecom, Lucent Technologies, NEC, and Telia in cooperation with Nortel Networks. SPIRITS-like services are those originating in the Public Switched Telephone Network (PSTN) and necessitating the interactions of the Internet and PSTN. This memo provides information for the Internet community. ietf-spirits-implementations-02 INFORMATIONAL INFORMATIONAL RFC2996 Format of the RSVP DCLASS Object Y. Bernet November 2000 ASCII 18929 9 resource reservation protocol QoS Quality of Service This document specifies the format of the DCLASS object and briefly discusses its use. [STANDARDS TRACK] ietf-issll-dclass-01 PROPOSED STANDARD PROPOSED STANDARD RFC2997 Specification of the Null Service Type Y. Bernet A. Smith B. Davie November 2000 ASCII 25071 12 resource reservation protocol QoS Quality of Service The Null Service allows applications to identify themselves to network Quality of Service (QoS) policy agents, using RSVP signaling. However, it does not require them to specify resource requirements. QoS policy agents in the network respond by applying QoS policies appropriate for the application (as determined by the network administrator). This mode of RSVP usage is particularly applicable to networks that combine differentiated service (diffserv) QoS mechanisms with RSVP signaling. In this environment, QoS policy agents may direct the signaled application's traffic to a particular diffserv class of service. [STANDARDS TRACK] ietf-issll-nullservice-00 PROPOSED STANDARD PROPOSED STANDARD RFC2998 A Framework for Integrated Services Operation over Diffserv Networks Y. Bernet P. Ford R. Yavatkar F. Baker L. Zhang M. Speer R. Braden B. Davie J. Wroclawski E. Felstaine November 2000 ASCII 76378 31 intserv QoS Quality of Service end-to-end This document describes a framework by which Integrated Services may be supported over Diffserv networks. This memo provides information for the Internet community. ietf-issll-diffserv-rsvp-05 INFORMATIONAL INFORMATIONAL RFC2999 Request for Comments Summary RFC Numbers 2900-2999 S. Ginoza August 2001 ASCII 45307 23 INFORMATIONAL INFORMATIONAL RFC3000 Internet Official Protocol Standards J. Reynolds R. Braden S. Ginoza L. Shiota November 2001 ASCII 115207 43 This memo contains a snapshot of the state of standardization of protocols used in the Internet as of October 25, 2001. It lists official protocol standards and Best Current Practice RFCs; it is not a complete index to the RFC series. The latest version of this memo is designated STD 1. [STANDARDS TRACK] RFC2900 RFC3300 STANDARD STANDARD RFC3001 A URN Namespace of Object Identifiers M. Mealling November 2000 ASCII 7459 5 uniform resource names OIDs This document describes a Uniform Resource Names (URN) namespace that contains Object Identifiers (OIDs). This memo provides information for the Internet community. mealling-oid-urn-01 RFC3061 INFORMATIONAL INFORMATIONAL RFC3002 Overview of 2000 IAB Wireless Internetworking Workshop D. Mitzel December 2000 ASCII 101466 42 internet architecture board This document provides an overview of a workshop held by the Internet Architecture Board (IAB) on wireless internetworking. This memo provides information for the Internet community. iab-wirelessws-01 INFORMATIONAL INFORMATIONAL RFC3003 The audio/mpeg Media Type M. Nilsson November 2000 ASCII 8381 5 MIME multipurpose internet mail extensions The audio layers of the MPEG-1 and MPEG-2 standards are in frequent use on the internet, but there is no uniform Multipurpose Internet Mail Extension (MIME) type for these files. The intention of this document is to define the media type audio/mpeg to refer to this kind of contents. [STANDARDS TRACK] nilsson-audio-mpeg-03 PROPOSED STANDARD PROPOSED STANDARD RFC3004 The User Class Option for DHCP G. Stump R. Droms Y. Gu R. Vyaghrapuri A. Demirtjis B. Beser J. Privat November 2000 ASCII 10423 6 dynamic host configuration protocol This option is used by a Dynamic Host Configuration Protocol (DHCP) client to optionally identify the type or category of user or applications it represents. The information contained in this option is an opaque field that represents the user class of which the client is a member. Based on this class, a DHCP server selects the appropriate address pool to assign an address to the client and the appropriate configuration parameters. This option should be configurable by a user. [STANDARDS TRACK] ietf-dhc-userclass-10 PROPOSED STANDARD PROPOSED STANDARD RFC3005 IETF Discussion List Charter S. Harris November 2000 ASCII 5682 3 internet engineering task force The Internet Engineering Task Force (IETF) discussion mailing list furthers the development and specification of Internet technology through discussion of technical issues, and hosts discussions of IETF direction, policy, meetings, and procedures. As this is the most general IETF mailing list, considerable latitude is allowed. Advertising, whether to solicit business or promote employment opportunities, falls well outside the range of acceptable topics, as do discussions of a personal nature. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-poisson-listaup-02 BCP0045 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3006 Integrated Services in the Presence of Compressible Flows B. Davie C. Iturralde D. Oran S. Casner J. Wroclawski November 2000 ASCII 31588 13 routing resource allocation int-serv This specification describes an extension to the TSpec which enables a sender of potentially compressible data to provide hints to int-serv routers about the compressibility they may obtain. [STANDARDS TRACK] ietf-intserv-compress-02 PROPOSED STANDARD PROPOSED STANDARD RFC3007 Secure Domain Name System (DNS) Dynamic Update B. Wellington November 2000 ASCII 18056 9 security authentication validation DNSSEC This document proposes a method for performing secure Domain Name System (DNS) dynamic updates. [STANDARDS TRACK] ietf-dnsext-simple-secure-update-02 RFC2137 RFC2535 RFC2136 RFC4033 RFC4034 RFC4035 PROPOSED STANDARD PROPOSED STANDARD RFC3008 Domain Name System Security (DNSSEC) Signing Authority B. Wellington November 2000 ASCII 13484 7 DNSSEC authentication validation SIG signature This document proposes a revised model of Domain Name System Security (DNSSEC) Signing Authority. The revised model is designed to clarify earlier documents and add additional restrictions to simplify the secure resolution process. Specifically, this affects the authorization of keys to sign sets of records. [STANDARDS TRACK] ietf-dnsext-signing-auth-02 RFC4033 RFC4034 RFC4035 RFC2535 RFC3658 PROPOSED STANDARD PROPOSED STANDARD RFC3009 Registration of parityfec MIME types J. Rosenberg H. Schulzrinne November 2000 ASCII 16022 10 media-type multimedia internet mail extensions The RTP (Real-time Transport Protocol) payload format for generic forward error correction allows RTP participants to improve loss resiliency through the use of traditional parity-based channel codes. This payload format requires four new MIME types, audio/parityfec, video/parityfec, text/parityfec and application/parityfec. This document serves as the MIME type registration for those formats. [STANDARDS TRACK] ietf-avt-fecmime-01 PROPOSED STANDARD PROPOSED STANDARD RFC3010 NFS version 4 Protocol S. Shepler B. Callaghan D. Robinson R. Thurlow C. Beame M. Eisler D. Noveck December 2000 ASCII 450434 212 NFSv4 network file system NFS (Network File System) version 4 is a distributed file system protocol which owes heritage to NFS protocol versions 2 [RFC1094] and 3 [RFC1813]. Unlike earlier versions, the NFS version 4 protocol supports traditional file access while integrating support for file locking and the mount protocol. In addition, support for strong security (and its negotiation), compound operations, client caching, and internationalization have been added. Of course, attention has been applied to making NFS version 4 operate well in an Internet environment. [STANDARDS TRACK] ietf-nfsv4-07 10/29/03 - back in June 2002, Matthew Wilcox sent an email stating that RFC 3010 is listed as erronously obsoleting RFCs 1813 and 1094. This was confirmed by Scott Bradner in October 2003. I have removed the Obsoletes tag for for this entry. RFC3530 PROPOSED STANDARD PROPOSED STANDARD RFC3011 The IPv4 Subnet Selection Option for DHCP G. Waters November 2000 ASCII 13967 7 internet protocol dynamic host configuration This memo defines a new Dynamic Host Configuration Protocol (DHCP) option for selecting the subnet on which to allocate an address. [STANDARDS TRACK] ietf-dhc-subnet-option-07 PROPOSED STANDARD PROPOSED STANDARD RFC3012 Mobile IPv4 Challenge/Response Extensions C. Perkins P. Calhoun November 2000 ASCII 37005 17 internet protocol authentication foreign agent In this specification, we define extensions for the Mobile IP Agent Advertisements and the Registration Request that allow a foreign agent to use a challenge/response mechanism to authenticate the mobile node. [STANDARDS TRACK] ietf-mobileip-challenge-13 PROPOSED STANDARD PROPOSED STANDARD RFC3013 Recommended Internet Service Provider Security Services and Procedures T. Killalea November 2000 ASCII 27905 13 ISPs The purpose of this document is to express what the engineering community as represented by the IETF expects of Internet Service Providers (ISPs) with respect to security. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-grip-isp-expectations-06 BCP0046 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3014 Notification Log MIB R. Kavasseri November 2000 ASCII 48287 26 management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for logging Simple Network Management Protocol (SNMP) Notifications. [STANDARDS TRACK] ietf-disman-notif-log-mib-17 PROPOSED STANDARD PROPOSED STANDARD RFC3015 Megaco Protocol Version 1.0 F. Cuervo N. Greene A. Rayhan C. Huitema B. Rosen J. Segers November 2000 ASCII 385432 179 MEGACO H.248 media gateway control This document defines the protocol used between elements of a physically decomposed multimedia gateway, i.e. a Media Gateway and a Media Gateway Controller. [STANDARDS TRACK] ietf-megaco-merged-01 RFC2885 RFC2886 RFC3525 PROPOSED STANDARD PROPOSED STANDARD RFC3016 RTP Payload Format for MPEG-4 Audio/Visual Streams Y. Kikuchi T. Nomura S. Fukunaga Y. Matsui H. Kimata November 2000 ASCII 47070 21 real-time transport protocol media-type This document describes Real-Time Transport Protocol (RTP) payload formats for carrying each of MPEG-4 Audio and MPEG-4 Visual bitstreams without using MPEG-4 Systems. [STANDARDS TRACK] ietf-avt-rtp-mpeg4-es-05 PROPOSED STANDARD PROPOSED STANDARD RFC3017 XML DTD for Roaming Access Phone Book M. Riegel G. Zorn December 2000 ASCII 59762 33 extensible markup language document type declaration This document defines the syntax as well as the semantics of the information to be included in the phone book for roaming applications. [STANDARDS TRACK] ietf-roamops-phonebook-xml-05 PROPOSED STANDARD PROPOSED STANDARD RFC3018 Unified Memory Space Protocol Specification A. Bogdanov December 2000 ASCII 177783 81 UMSP network connection-oriented This document specifies Unified Memory Space Protocol (UMSP), which gives a capability of immediate access to memory of the remote nodes. This memo defines an Experimental Protocol for the Internet community. bogdanov-usmp-00 EXPERIMENTAL EXPERIMENTAL RFC3019 IP Version 6 Management Information Base for The Multicast Listener Discovery Protocol B. Haberman R. Worzella January 2001 ASCII 28293 15 IPv6 MIB MLD This document defines a portion of the Management Information Base (MIB) for use with network management protocols in Internet Protocol Version 6 internets. Specifically, this document is the MIB module that defines managed objects for implementations of the Multicast Listener Discovery Protocol [RFC2710]. [STANDARDS TRACK] ietf-ipngwg-mld-mib-05 PROPOSED STANDARD PROPOSED STANDARD RFC3020 Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function P. Pate B. Lynch K. Rehbehn December 2000 ASCII 67736 36 MIB management information base This memo defines a Management Information Base (MIB) for monitoring and controlling a UNI/NNI Multilink Frame Relay Function as defined in Frame Relay Forum FRF.16. [STANDARDS TRACK] ietf-frnetmib-mfrmib-04 PROPOSED STANDARD PROPOSED STANDARD RFC3021 Using 31-Bit Prefixes on IPv4 Point-to-Point Links A. Retana R. White V. Fuller D. McPherson December 2000 ASCII 19771 10 internet protocol addresses subnet masks With ever-increasing pressure to conserve IP address space on the Internet, it makes sense to consider where relatively minor changes can be made to fielded practice to improve numbering efficiency. One such change, proposed by this document, is to halve the amount of address space assigned to point-to-point links (common throughout the Internet infrastructure) by allowing the use of 31-bit subnet masks in a very limited way. [STANDARDS TRACK] retana-31bits-03 PROPOSED STANDARD PROPOSED STANDARD RFC3022 Traditional IP Network Address Translator (Traditional NAT) P. Srisuresh K. Egevang January 2001 ASCII 37675 16 internet protocol ports private The NAT operation described in this document extends address translation introduced in RFC 1631 and includes a new type of network address and TCP/UDP port translation. In addition, this document corrects the Checksum adjustment algorithm published in RFC 1631 and attempts to discuss NAT operation and limitations in detail. This memo provides information for the Internet community. ietf-nat-traditional-05 RFC1631 INFORMATIONAL INFORMATIONAL RFC3023 XML Media Types M. Murata S. St. Laurent D. Kohn January 2001 ASCII 86011 39 extensible markup language web authority hypertext transfer protocol This document standardizes five new media types -- text/xml, application/xml, text/xml-external-parsed-entity, application/xml- external-parsed-entity, and application/xml-dtd -- for use in exchanging network entities that are related to the Extensible Markup Language (XML). This document also standardizes a convention (using the suffix '+xml') for naming media types outside of these five types when those media types represent XML MIME (Multipurpose Internet Mail Extensions) entities. [STANDARDS TRACK] murata-xml-09 RFC2376 RFC2048 PROPOSED STANDARD PROPOSED STANDARD RFC3024 Reverse Tunneling for Mobile IP, revised G. Montenegro Editor January 2001 ASCII 63929 30 internet protocol node care-of-address This document proposes backwards-compatible extensions to Mobile IP to support topologically correct reverse tunnels. This document does not attempt to solve the problems posed by firewalls located between the home agent and the mobile node's care-of address. [STANDARDS TRACK] ietf-mobileip-rfc2344-bis-02 RFC2344 PROPOSED STANDARD PROPOSED STANDARD RFC3025 Mobile IP Vendor/Organization-Specific Extensions G. Dommety K. Leung February 2001 ASCII 15611 8 internet protocol This document defines two new extensions to Mobile IP. These extensions will facilitate equipment vendors and organizations to make specific use of these extensions as they see fit for research or deployment purposes. [STANDARDS TRACK] ietf-mobileip-vendor-ext-11 RFC3115 PROPOSED STANDARD PROPOSED STANDARD RFC3026 Liaison to IETF/ISOC on ENUM R. Blane January 2001 ASCII 11460 6 dns domain name system internet security engineering task force E.164 number Working Party 1/2, of the International Telecommunication Union Telecommunication Standardization Sector (ITU-T) held a meeting of its collaborators in Berlin Germany 19-26 October 2000. This liaison from WP1/2 to the IETF/ISOC conveys the understandings of the WP1/2 collaborators resulting from the discussions. This memo provides information for the Internet community. itu-sg2-liason-enum-01 INFORMATIONAL INFORMATIONAL RFC3027 Protocol Complications with the IP Network Address Translator M. Holdrege P. Srisuresh January 2001 ASCII 48662 20 IP internet protocol network address translator The purpose of this document is to identify the protocols and applications that break with NAT enroute. The document also attempts to identify any known workarounds. This document attempts to capture as much information as possible, but is by no means a comprehensive coverage. This memo provides information for the Internet community. ietf-nat-protocol-complications-06 INFORMATIONAL INFORMATIONAL RFC3028 Sieve: A Mail Filtering Language T. Showalter January 2001 ASCII 73582 36 client server This document describes a language for filtering e-mail messages at time of final delivery. [STANDARDS TRACK] showalter-sieve-12 PROPOSED STANDARD PROPOSED STANDARD RFC3029 Internet X.509 Public Key Infrastructure Data Validation and Certification Server Protocols C. Adams P. Sylvester M. Zolotarev R. Zuccherato February 2001 ASCII 107347 51 DVCS TTP trusted third party This document describes a general Data Validation and Certification Server (DVCS) and the protocols to be used when communicating with it. This memo defines an Experimental Protocol for the Internet community. ietf-pkix-dcs-07 EXPERIMENTAL EXPERIMENTAL RFC3030 SMTP Service Extensions for Transmission of Large and Binary MIME Messages G. Vaudreuil December 2000 ASCII 23405 12 simple mail transfer protocol multipurpose interent This memo defines two extensions to the SMTP (Simple Mail Transfer Protocol) service. [STANDARDS TRACK] vaudreuil-esmtp-binary2-03 RFC1830 PROPOSED STANDARD PROPOSED STANDARD RFC3031 Multiprotocol Label Switching Architecture E. Rosen A. Viswanathan R. Callon January 2001 ASCII 147175 61 MPLS This document specifies the architecture for Multiprotocol Label Switching (MPLS). [STANDARDS TRACK] ietf-mpls-arch-06 PROPOSED STANDARD PROPOSED STANDARD RFC3032 MPLS Label Stack Encoding E. Rosen D. Tappan G. Fedorkow Y. Rekhter D. Farinacci T. Li A. Conta January 2001 ASCII 48314 23 multi-protocol label switching This document specifies the encoding to be used by an LSR in order to transmit labeled packets on Point-to-Point Protocol (PPP) data links, on LAN data links, and possibly on other data links as well. This document also specifies rules and procedures for processing the various fields of the label stack encoding. [STANDARDS TRACK] ietf-mpls-label-encaps-07 RFC3443 PROPOSED STANDARD PROPOSED STANDARD RFC3033 The Assignment of the Information Field and Protocol Identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet Protocol M. Suzuki January 2001 ASCII 52188 25 IP The purpose of this document is to specify the assignment of the information field and protocol identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet protocol. [STANDARDS TRACK] ietf-mpls-git-uus-04 PROPOSED STANDARD PROPOSED STANDARD RFC3034 Use of Label Switching on Frame Relay Networks Specification A. Conta P. Doolan A. Malis January 2001 ASCII 53176 24 MPLS multi-protocol This document defines the model and generic mechanisms for Multiprotocol Label Switching on Frame Relay networks. [STANDARDS TRACK] ietf-mpls-fr-06 PROPOSED STANDARD PROPOSED STANDARD RFC3035 MPLS using LDP and ATM VC Switching B. Davie J. Lawrence K. McCloghrie E. Rosen G. Swallow Y. Rekhter P. Doolan January 2001 ASCII 46463 20 multi-protocol label switching asynchronous transfer mode distribution protocol This document extends and clarifies the relevant portions of RFC 3031 and RFC 3036 by specifying in more detail the procedures which to be used when distributing labels to or from ATM-LSRs, when those labels represent Forwarding Equivalence Classes (FECs, see RFC 3031) for which the routes are determined on a hop-by-hop basis by network layer routing algorithms. [STANDARDS TRACK] ietf-mpls-atm-04 PROPOSED STANDARD PROPOSED STANDARD RFC3036 LDP Specification L. Andersson P. Doolan N. Feldman A. Fredette B. Thomas January 2001 ASCII 274855 132 label distribution protocol A fundamental concept in MPLS is that two Label Switching Routers (LSRs) must agree on the meaning of the labels used to forward traffic between and through them. This common understanding is achieved by using a set of procedures, called a label distribution protocol, by which one LSR informs another of label bindings it has made. This document defines a set of such procedures called LDP (for Label Distribution Protocol) by which LSRs distribute labels to support MPLS forwarding along normally routed paths. [STANDARDS TRACK] ietf-mpls-ldp-11 PROPOSED STANDARD PROPOSED STANDARD RFC3037 LDP Applicability B. Thomas E. Gray January 2001 ASCII 13601 7 label distribution protocol A fundamental concept in MPLS is that two Label Switching Routers (LSRs) must agree on the meaning of the labels used to forward traffic between and through them. This common understanding is achieved by using a set of procedures, called a label distribution protocol, by which one LSR informs another of label bindings it has made. This document describes the applicability of a set of such procedures called LDP (for Label Distribution Protocol) by which LSRs distribute labels to support MPLS forwarding along normally routed paths. This memo provides information for the Internet community. ietf-mpls-ldp-applic-02 INFORMATIONAL INFORMATIONAL RFC3038 VCID Notification over ATM link for LDP K. Nagami Y. Katsube N. Demizu H. Esaki P. Doolan January 2001 ASCII 39134 19 asynchronous transfer mode label distribution protocol This document specifies the procedures for the communication of VCID values between neighboring ATM-LSRs that must occur in order to ensure this property. [STANDARDS TRACK] ietf-mpls-vcid-atm-05 PROPOSED STANDARD PROPOSED STANDARD RFC3039 Internet X.509 Public Key Infrastructure Qualified Certificates Profile S. Santesson W. Polk P. Barzin M. Nystrom January 2001 ASCII 67619 35 syntax This document forms a certificate profile for Qualified Certificates, based on RFC 2459, for use in the Internet. The goal of this document is to define a general syntax independent of local legal requirements. [STANDARDS TRACK] ietf-pkix-qc-06 RFC3739 PROPOSED STANDARD PROPOSED STANDARD RFC3040 Internet Web Replication and Caching Taxonomy I. Cooper I. Melve G. Tomlinson January 2001 ASCII 63257 32 infrastructure www world wide This memo specifies standard terminology and the taxonomy of web replication and caching infrastructure as deployed today. It introduces standard concepts, and protocols used today within this application domain. This memo provides information for the Internet community. ietf-wrec-taxonomy-06 INFORMATIONAL INFORMATIONAL RFC3041 Privacy Extensions for Stateless Address Autoconfiguration in IPv6 T. Narten R. Draves January 2001 ASCII 44446 17 internet protocol interface identifier This document describes an extension to IPv6 stateless address autoconfiguration for interfaces whose interface identifier is derived from an IEEE identifier. [STANDARDS TRACK] ietf-ipngwg-addrconf-privacy-04 PROPOSED STANDARD PROPOSED STANDARD RFC3042 Enhancing TCP's Loss Recovery Using Limited Transmit M. Allman H. Balakrishnan S. Floyd January 2001 ASCII 19885 9 transmission control protocol This document proposes a new Transmission Control Protocol (TCP) mechanism that can be used to more effectively recover lost segments when a connection's congestion window is small, or when a large number of segments are lost in a single transmission window. [STANDARDS TRACK] ietf-tsvwg-limited-xmit-00 PROPOSED STANDARD PROPOSED STANDARD RFC3043 The Network Solutions Personal Internet Name (PIN): A URN Namespace for People and Organizations M. Mealling January 2001 ASCII 8136 5 uniform resource name This document describes a Uniform Resource Name (URN) namespace that is engineered by Network Solutions, Inc. for naming people and organizations. This memo provides information for the Internet community. mealling-pin-urn-02 INFORMATIONAL INFORMATIONAL RFC3044 Using The ISSN (International Serial Standard Number) as URN (Uniform Resource Names) within an ISSN-URN Namespace S. Rozenfeld January 2001 ASCII 28094 15 serials identifier This document presents how the ISSN - International Standard Serial Number - which is a persistent number for unique identification of serials widely recognised and used in the bibliographic world, can be supported within the Uniform Resource Name (URN) framework as a specific URN namespace identifier. This memo provides information for the Internet community. rozenfeld-urn-lssn-00 INFORMATIONAL INFORMATIONAL RFC3045 Storing Vendor Information in the LDAP root DSE M. Meredith January 2001 ASCII 10518 6 lightweight directory access protocol DSA-specific entry This document specifies two Lightweight Directory Access Protocol (LDAP) attributes, vendorName and vendorVersion that MAY be included in the root DSA-specific Entry (DSE) to advertise vendor-specific information. This memo provides information for the Internet community. mmeredith-rootdse-vendor-info-03 INFORMATIONAL INFORMATIONAL RFC3046 DHCP Relay Agent Information Option M. Patrick January 2001 ASCII 30633 14 dynamic host configuration protocol Newer high-speed public Internet access technologies call for a high- speed modem to have a local area network (LAN) attachment to one or more customer premise hosts. It is advantageous to use the Dynamic Host Configuration Protocol (DHCP) as defined in RFC 2131 to assign customer premise host IP addresses in this environment. However, a number of security and scaling problems arise with such "public" DHCP use. This document describes a new DHCP option to address these issues. This option extends the set of DHCP options as defined in RFC 2132. [STANDARDS TRACK] ietf-dhc-agent-options-12 PROPOSED STANDARD PROPOSED STANDARD RFC3047 RTP Payload Format for ITU-T Recommendation G.722.1 P. Luthi January 2001 ASCII 16292 8 international telecommunication union real-time transport protocol This document describes the payload format for including G.722.1 generated bit streams within an RTP packet. Also included here are the necessary details for the use of G.722.1 with MIME and SDP. [STANDARDS TRACK] ietf-avt-rtp-g7221-01 PROPOSED STANDARD PROPOSED STANDARD RFC3048 Reliable Multicast Transport Building Blocks for One-to-Many Bulk-Data Transfer B. Whetten L. Vicisano R. Kermode M. Handley S. Floyd M. Luby January 2001 ASCII 48965 20 RMT protocol core This document describes a framework for the standardization of bulk-data reliable multicast transport. This memo provides information for the Internet community. ietf-rmt-buildingblocks-03 INFORMATIONAL INFORMATIONAL RFC3049 TN3270E Service Location and Session Balancing J. Naugle K. Kasthurirangan G. Ledford January 2001 ASCII 40743 21 SLP This document discusses the implementation of Service Location Protocol (SLP) and session balancing with a TN3270E emulator in a client server implementation with a TN3270E server. [STANDARDS TRACK] ietf-tn3270e-service-loc-06 PROPOSED STANDARD PROPOSED STANDARD RFC3050 Common Gateway Interface for SIP J. Lennox H. Schulzrinne J. Rosenberg January 2001 ASCII 76652 35 session initiation protocol This document defines a SIP CGI interface for providing SIP services on a SIP server. This memo provides information for the Internet community. lennox-sip-cgi-04 INFORMATIONAL INFORMATIONAL RFC3051 IP Payload Compression Using ITU-T V.44 Packet Method J. Heath J. Border January 2001 ASCII 15845 8 internet protocol international telecommunication union This document describes a compression method based on the data compression algorithm described in International Telecommunication Union (ITU-T) Recommendation V.44. This document defines the application of V.44 Packet Method to the Internet Protocol (IP) Payload Compression Protocol (RFC 2393). This memo provides information for the Internet community. heath-ipcomp-v44-00 INFORMATIONAL INFORMATIONAL RFC3052 Service Management Architectures Issues and Review M. Eder S. Nag January 2001 ASCII 31859 12 framework packets network The purpose of this document is to explore the problems of defining a Service management framework and to examine some of the issues that still need to be resolved. This memo provides information for the Internet community. irtf-nsmrg-sm-issues-00 INFORMATIONAL INFORMATIONAL RFC3053 IPv6 Tunnel Broker A. Durand P. Fasano I. Guardini D. Lento January 2001 ASCII 27336 13 internet protocol infrastructure The motivation for the development of the tunnel broker model is to help early IPv6 adopters to hook up to an existing IPv6 network (e.g., the 6bone) and to get stable, permanent IPv6 addresses and DNS names. The concept of the tunnel broker was first presented at Orlando's IETF in December 1998. Two implementations were demonstrated during the Grenoble IPng & NGtrans interim meeting in February 1999. This memo provides information for the Internet community. ietf-ngtrans-broker-06 INFORMATIONAL INFORMATIONAL RFC3054 Megaco IP Phone Media Gateway Application Profile P. Blatherwick R. Bell P. Holland January 2001 ASCII 31971 14 internet protocol H.248 telephone MG This document specifies a particular application of the Megaco/H.248 Protocol for control of Internet telephones and similar appliances: the Megaco IP Phone Media Gateway. This memo provides information for the Internet community. ietf-megaco-ipphone-03 INFORMATIONAL INFORMATIONAL RFC3055 Management Information Base for the PINT Services Architecture M. Krishnaswamy D. Romascanu February 2001 ASCII 39315 21 MIB PSTN/Internet interworking This memo describes a proposed Management Information Base (MIB) for the PSTN/Internet Interworking (PINT) Services Architecture. [STANDARDS TRACK] ietf-pint-mib-05 PROPOSED STANDARD PROPOSED STANDARD RFC3056 Connection of IPv6 Domains via IPv4 Clouds B. Carpenter K. Moore February 2001 ASCII 54902 23 internet protocol wide area network unicast point-to-point This memo specifies an optional interim mechanism for IPv6 sites to communicate with each other over the IPv4 network without explicit tunnel setup, and for them to communicate with native IPv6 domains via relay routers. [STANDARDS TRACK] ietf-ngtrans-6to4-07 PROPOSED STANDARD PROPOSED STANDARD RFC3057 ISDN Q.921-User Adaptation Layer K. Morneault S. Rengasami M. Kalla G. Sidebottom February 2001 ASCII 13601 66 SCTP signaling media gateway interface This document defines a protocol for backhauling of ISDN Q.921 User messages over IP using the Stream Control Transmission Protocol (SCTP). This protocol would be used between a Signaling Gateway (SG) and Media Gateway Controller (MGC). [STANDARDS TRACK] ietf-sigtran-iua-10 RFC3807 PROPOSED STANDARD PROPOSED STANDARD RFC3058 Use of the IDEA Encryption Algorithm in CMS S. Teiwes P. Hartmann D. Kuenzi February 2001 ASCII 17257 8 international data encryption algorithm cryptic message syntax s/mime multipurpose internet mail extensions This memo specifies how to incorporate International Data Encryption Algorithm (IDEA) into CMS or S/MIME as an additional strong algorithm for symmetric encryption. This memo provides information for the Internet community. ietf-smime-idea-08 INFORMATIONAL INFORMATIONAL RFC3059 Attribute List Extension for the Service Location Protocol E. Guttman February 2001 ASCII 11208 6 SLPv2 messages user agent This document specifies a SLPv2 extension which allows a User Agent (UA) to request a service's attributes be included as an extension to Service Reply messages. This will eliminate the need for multiple round trip messages for a UA to acquire all service information. [STANDARDS TRACK] guttman-svrloc-attrust-ext-05 PROPOSED STANDARD PROPOSED STANDARD RFC3060 Policy Core Information Model -- Version 1 Specification B. Moore E. Ellesson J. Strassner A. Westerinen February 2001 ASCII 240309 100 CIM common schema object-oriented This document presents the object-oriented information model for representing policy information developed jointly in the IETF Policy Framework WG and as extensions to the Common Information Model (CIM) activity in the Distributed Management Task Force (DMTF). [STANDARDS TRACK] ietf-policy-core-info-model-08 RFC3460 PROPOSED STANDARD PROPOSED STANDARD RFC3061 A URN Namespace of Object Identifiers M. Mealling February 2001 ASCII 8387 6 uniform resource names OIDs This document describes a Uniform Resource Name (URN) namespace that contains Object Identifiers (OIDs). This memo provides information for the Internet community. mealling-rfc3001bis-01 RFC3001 INFORMATIONAL INFORMATIONAL RFC3062 LDAP Password Modify Extended Operation K. Zeilenga February 2001 ASCII 11807 6 lightweight directory access protocol This document describes an LDAP extended operation to allow modification of user passwords which is not dependent upon the form of the authentication identity nor the password storage mechanism used. [STANDARDS TRACK] zeilenga-ldap-passwd-exop-05 PROPOSED STANDARD PROPOSED STANDARD RFC3063 MPLS Loop Prevention Mechanism Y. Ohba Y. Katsube E. Rosen P. Doolan February 2001 ASCII 93523 44 multiprotocol label switching path LSPs This paper presents a simple mechanism, based on "threads", which can be used to prevent Multiprotocol Label Switching (MPLS) from setting up label switched path (LSPs) which have loops. This memo defines an Experimental Protocol for the Internet community. ietf-mpls-loop-prevention-03 EXPERIMENTAL EXPERIMENTAL RFC3064 MGCP CAS Packages B. Foster February 2001 ASCII 116818 56 media gateway controllers This document contains a collection of media gateway Channel Associated Signaling (CAS) packages for R1 CAS, North American CAS, CAS PBX interconnect as well as basic FXO support. This memo provides information for the Internet community. foster-mgcp-cas-packages-00 INFORMATIONAL INFORMATIONAL RFC3065 Autonomous System Confederations for BGP P. Traina D. McPherson J. Scudder February 2001 ASCII 20529 11 BGP-ASC AS border gateway protocol This document describes an extension to BGP which may be used to create a confederation of autonomous systems that is represented as a single autonomous system to BGP peers external to the confederation, thereby removing the "full mesh" requirement. The intention of this extension is to aid in policy administration and reduce the management complexity of maintaining a large autonomous system. [STANDARDS TRACK] ietf-idr-bgp-confed-rfc1965bis-01 RFC1965 PROPOSED STANDARD PROPOSED STANDARD RFC3066 Tags for the Identification of Languages H. Alvestrand January 2001 ASCII 26522 13 Lang-Tag This document describes a language tag for use in cases where it is desired to indicate the language used in an information object, how to register values for use in this language tag, and a construct for matching such language tags. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. alvestrand-lang-tag-v2-05 RFC1766 BCP0047 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3067 TERENA'S Incident Object Description and Exchange Format Requirements J. Arvidsson A. Cormack Y. Demchenko J. Meijer February 2001 ASCII 36836 17 IEDEF data archiving The purpose of the Incident Object Description and Exchange Format is to define a common data format for the description, archiving and exchange of information about incidents between CSIRTs (Computer Security Incident Response Teams) (including alert, incident in investigation, archiving, statistics, reporting, etc.). This document describes the high-level requirements for such a description and exchange format, including the reasons for those requirements. This memo provides information for the Internet community. terena-itdwg-iodef-requirements-00 INFORMATIONAL INFORMATIONAL RFC3068 An Anycast Prefix for 6to4 Relay Routers C. Huitema June 2001 ASCII 20120 9 exterior gateway protocol interior IGP EGP This memo introduces a "6to4 anycast address" in order to simplify the configuration of 6to4 routers. It also defines how this address will be used by 6to4 relay routers, how the corresponding "6to4 anycast prefix" will be advertised in the IGP and in the EGP. The memo documents the reservation by IANA (Internet Assigned Numbers Authority) of the "6to4 relay anycast prefix." [STANDARDS TRACK] ietf-ngtrans-6to4anycast-03 PROPOSED STANDARD PROPOSED STANDARD RFC3069 VLAN Aggregation for Efficient IP Address Allocation D. McPherson B. Dykes February 2001 ASCII 14891 7 virtual local area network internet protocol This document introduces the concept of Virtual Local Area Network (VLAN) aggregation as it relates to IPv4 address allocation. This memo provides information for the Internet community. mcpherson-vlan-ipagg-02 INFORMATIONAL INFORMATIONAL RFC3070 Layer Two Tunneling Protocol (L2TP) over Frame Relay V. Rawat R. Tio S. Nanji R. Verma February 2001 ASCII 12940 7 L2TP-FR point-to-point virtual switched circuits PVCs SVCs This document describes how L2TP is implemented over Frame Relay Permanent Virtual Circuits (PVCs) and Switched Virtual Circuits (SVCs). [STANDARDS TRACK] ietf-l2tpext-fr-01 PROPOSED STANDARD PROPOSED STANDARD RFC3071 Reflections on the DNS, RFC 1591, and Categories of Domains J. Klensin February 2001 ASCII 24892 10 DNS Policy Top-Level TLD This document is being published primarily for historical context and comparative purposes, essentially to document some thoughts about how 1591 might have been interpreted and adjusted by the Internet Assigned Numbers Authority (IANA) and ICANN to better reflect today's world while retaining characteristics and policies that have proven to be effective in supporting Internet growth and stability. This memo provides information for the Internet community. klensin-1591-reflections-02 INFORMATIONAL INFORMATIONAL RFC3072 Structured Data Exchange Format (SDXF) M. Wildgrube March 2001 ASCII 48481 26 chunks file datatype This specification describes an all-purpose interchange format for use as a file format or for net-working. This memo provides information for the Internet community. wildgrube-sdxf-08 INFORMATIONAL INFORMATIONAL RFC3073 Portable Font Resource (PFR) - application/font-tdpfr MIME Sub-type Registration J. Collins March 2001 ASCII 9076 6 multipurpose internet mail extensions This document describes the registration of the Multipurpose Internet Mail Extensions (MIME) sub-type application/font-tdpfr. The encoding is defined by the PFR Specification. This memo provides information for the Internet community. collins-pfr-00 INFORMATIONAL INFORMATIONAL RFC3074 DHC Load Balancing Algorithm B. Volz S. Gonczi T. Lemon R. Stevens February 2001 ASCII 19374 10 dynamic host configuration protocol This document proposes a method of algorithmic load balancing. [STANDARDS TRACK] ietf-dhc-loadb-03 PROPOSED STANDARD PROPOSED STANDARD RFC3075 XML-Signature Syntax and Processing D. Eastlake 3rd J. Reagle D. Solo March 2001 ASCII 145520 64 extensible markup language This document specifies XML (Extensible Markup Language) digital signature processing rules and syntax. [STANDARDS TRACK] ietf-xmldsig-core-11 RFC3275 PROPOSED STANDARD PROPOSED STANDARD RFC3076 Canonical XML Version 1.0 J. Boyer March 2001 ASCII 63955 28 extensible markup language This specification describes a method for generating a physical representation, the canonical form, of an XML document that accounts for the permissible changes. This memo provides information for the Internet community. ietf-xmldsig-canonical-01 INFORMATIONAL INFORMATIONAL RFC3077 A Link-Layer Tunneling Mechanism for Unidirectional Links E. Duros W. Dabbous H. Izumiyama N. Fujii Y. Zhang March 2001 ASCII 52410 25 ll udl bidirectional connectivity ip internet protocol This document describes a mechanism to emulate full bidirectional connectivity between all nodes that are directly connected by a unidirectional link. [STANDARDS TRACK] ietf-udlr-lltunnel-06 PROPOSED STANDARD PROPOSED STANDARD RFC3078 Microsoft Point-To-Point Encryption (MPPE) Protocol G. Pall G. Zorn March 2001 ASCII 22952 12 security ppp This document describes the use of the Microsoft Point to Point Encryption (MPPE) to enhance the confidentiality of PPP-encapsulated packets. This memo provides information for the Internet community. ietf-pppext-mppe-05 INFORMATIONAL INFORMATIONAL RFC3079 Deriving Keys for use with Microsoft Point-to-Point Encryption (MPPE) G. Zorn March 2001 ASCII 38905 21 security ppp This document describes the method used to derive initial MPPE session keys from a variety of credential types. It is expected that this memo will be updated whenever Microsoft defines a new key derivation method for MPPE, since its primary purpose is to provide an open, easily accessible reference for third-parties wishing to interoperate with Microsoft products. This memo provides information for the Internet community. ietf-pppext-mppe-keys-03 INFORMATIONAL INFORMATIONAL RFC3080 The Blocks Extensible Exchange Protocol Core M. Rose March 2001 ASCII 82089 58 BEEP text binary messages kernal This memo describes a generic application protocol kernel for connection-oriented, asynchronous interactions called the BEEP (Blocks Extensible Exchange Protocol) core. [STANDARDS TRACK] ietf-beep-framework-11 PROPOSED STANDARD PROPOSED STANDARD RFC3081 Mapping the BEEP Core onto TCP M. Rose March 2001 ASCII 14008 8 transmission control protocol blocks extensible exchange This memo describes how a BEEP (Blocks Extensible Exchange Protocol) session is mapped onto a single TCP (Transmission Control Protocol) connection. [STANDARDS TRACK] ietf-beep-tcpmapping-06 PROPOSED STANDARD PROPOSED STANDARD RFC3082 Notification and Subscription for SLP J. Kempf J. Goldschmidt March 2001 ASCII 33410 14 service location protocol The Service Location Protocol (SLP) provides mechanisms whereby service agent clients can advertise and user agent clients can query for services. The design is very much demand-driven, so that user agents only obtain service information when they specifically ask for it. There exists another class of user agent applications, however, that requires notification when a new service appears or disappears. In the RFC 2608 design, these applications are forced to poll the network to catch changes. In this document, we describe a protocol for allowing such clients to be notified when a change occurs, removing the need for polling. This memo defines an Experimental Protocol for the Internet community. kempf-srvloc-notify-05 EXPERIMENTAL EXPERIMENTAL RFC3083 Baseline Privacy Interface Management Information Base for DOCSIS Compliant Cable Modems and Cable Modem Termination Systems R. Woundy March 2001 ASCII 88318 45 MIB BPI data-over-cable service interface specifications This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP-based (Simple Network Management Protocol) management of the Baseline Privacy Interface (BPI), which provides data privacy for DOCSIS 1.0 (Data-Over- Cable Service Interface Specifications) compliant Cable Modems and Cable Modem Termination Systems. This MIB is defined as an extension to the DOCSIS Radio Frequency Interface MIB, RFC 2670. This memo provides information for the Internet community. ietf-ipcdn-mcns-bpi-mib-02 INFORMATIONAL INFORMATIONAL RFC3084 COPS Usage for Policy Provisioning (COPS-PR) K. Chan J. Seligson D. Durham S. Gai K. McCloghrie S. Herzog F. Reichmeyer R. Yavatkar A. Smith March 2001 ASCII 79341 34 COPS-PR common open service security quality This document describes the use of the Common Open Policy Service (COPS) protocol for support of policy provisioning (COPS-PR). [STANDARDS TRACK] ietf-rap-pr-05 PROPOSED STANDARD PROPOSED STANDARD RFC3085 URN Namespace for NewsML Resources A. Coates D. Allen D. Rivers-Moore March 2001 ASCII 10016 6 uniform resource name newsitems iptc This document describes a URN (Uniform Resource Name) namespace for identifying NewsML NewsItems. This memo provides information for the Internet community. iptc-newsml-urn-01 INFORMATIONAL INFORMATIONAL RFC3086 Definition of Differentiated Services Per Domain Behaviors and Rules for their Specification K. Nichols B. Carpenter April 2001 ASCII 63122 24 diffserv QoS quality of service This document defines and discusses Per-Domain Behaviors in detail and lays out the format and required content for contributions to the Diffserv WG on PDBs and the procedure that will be applied for individual PDB specifications to advance as WG products. This format is specified to expedite working group review of PDB submissions. This memo provides information for the Internet community. ietf-diffserv-pdb-def-03 INFORMATIONAL INFORMATIONAL RFC3087 Control of Service Context using SIP Request-URI B. Campbell R. Sparks April 2001 ASCII 83612 39 session initiation protocol uniform resource identifier This memo describes a useful way to conceptualize the use of the standard SIP (Session Initiation Protocol) Request-URI (Uniform Resource Identifier) that the authors and many members of the SIP community think is suitable as a convention. It does not define any new protocol with respect to RFC 2543. This memo provides information for the Internet community. campbell-sip-service-control-01 INFORMATIONAL INFORMATIONAL RFC3088 OpenLDAP Root Service An experimental LDAP referral service K. Zeilenga April 2001 ASCII 19471 11 lightweight directory access protocol dns domain name system The OpenLDAP Project is operating an experimental LDAP (Lightweight Directory Access Protocol) referral service known as the "OpenLDAP Root Service". The automated system generates referrals based upon service location information published in DNS SRV RRs (Domain Name System location of services resource records). This document describes this service. This memo defines an Experimental Protocol for the Internet community. zeilenga-ldap-root-02 EXPERIMENTAL EXPERIMENTAL RFC3089 A SOCKS-based IPv6/IPv4 Gateway Mechanism H. Kitamura April 2001 ASCII 25193 12 internet protocol application layer This document describes a SOCKS-based IPv6/IPv4 gateway mechanism that enables smooth heterogeneous communications between the IPv6 nodes and IPv4 nodes. This memo provides information for the Internet community. ietf-ngtrans-socks-gateway-06 INFORMATIONAL INFORMATIONAL RFC3090 DNS Security Extension Clarification on Zone Status E. Lewis March 2001 ASCII 24166 11 domain name system rsa dsa The definition of a secured zone is presented, clarifying and updating sections of RFC 2535. RFC 2535 defines a zone to be secured based on a per algorithm basis, e.g., a zone can be secured with RSA keys, and not secured with DSA keys. This document changes this to define a zone to be secured or not secured regardless of the key algorithm used (or not used). To further simplify the determination of a zone's status, "experimentally secure" status is deprecated. [STANDARDS TRACK] ietf-dnsext-zone-status-05 RFC4033 RFC4034 RFC4035 RFC2535 RFC3658 PROPOSED STANDARD PROPOSED STANDARD RFC3091 Pi Digit Generation Protocol H. Kennedy April 01 2001 ASCII 10375 6 This memo defines a protocol to provide the Pi digit generation service (PIgen) used between clients and servers on host computers. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC3092 Etymology of "Foo" D. Eastlake 3rd C. Manros E. Raymond April 01 2001 ASCII 29235 14 Approximately 212 RFCs so far, starting with RFC 269, contain the terms `foo', `bar', or `foobar' as metasyntactic variables without any proper explanation or definition. This document rectifies that deficiency. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC3093 Firewall Enhancement Protocol (FEP) M. Gaynor S. Bradner April 01 2001 ASCII 22405 11 Internet Transparency via the end-to-end architecture of the Internet has allowed vast innovation of new technologies and services [1]. However, recent developments in Firewall technology have altered this model and have been shown to inhibit innovation. We propose the Firewall Enhancement Protocol (FEP) to allow innovation, without violating the security model of a Firewall. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC3094 Tekelec's Transport Adapter Layer Interface D. Sprague R. Benedyk D. Brendes J. Keller April 2001 ASCII 265099 106 signaling gatewa circuit network internet protocol This document proposes the interfaces of a Signaling Gateway, which provides interworking between the Switched Circuit Network (SCN) and an IP network. This memo provides information for the Internet community. benedyk-sigtran-tali-01 INFORMATIONAL INFORMATIONAL RFC3095 RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed C. Bormann C. Burmeister M. Degermark H. Fukushima H. Hannu L-E. Jonsson R. Hakenberg T. Koren K. Le Z. Liu A. Martensson A. Miyazaki K. Svanbro T. Wiebke T. Yoshimura H. Zheng July 2001 ASCII 368746 168 encapsulating security payload real-time transport protocol user datagram This document specifies a highly robust and efficient header compression scheme for RTP/UDP/IP (Real-Time Transport Protocol, User Datagram Protocol, Internet Protocol), UDP/IP, and ESP/IP (Encapsulating Security Payload) headers. [STANDARDS TRACK] ietf-rohc-rtp-09 RFC3759 PROPOSED STANDARD PROPOSED STANDARD RFC3096 Requirements for robust IP/UDP/RTP header compression M. Degermark Editor July 2001 ASCII 15018 8 real-time transport internet protocol user datagram This document contains requirements for robust IP/UDP/RTP (Internet Protocol/User Datagram Protocol/Real-Time Transport Protocol) header compression to be developed by the ROHC (Robust Header Compression) WG. It is based on the ROHC charter, discussions in the WG, the 3GPP document "3GPP TR 23.922", version 1.0.0 of October 1999, as well as contributions from 3G.IP. This memo provides information for the Internet community. ietf-rohc-rtp-requirements-05 INFORMATIONAL INFORMATIONAL RFC3097 RSVP Cryptographic Authentication -- Updated Message Type Value R. Braden L. Zhang April 2001 ASCII 6320 4 RSVP resource reservation protocol security This memo resolves a duplication in the assignment of RSVP Message Types, by changing the Message Types assigned by RFC 2747 to Challenge and Integrity Response messages. [STANDARDS TRACK] ietf-rsvp-fix-iana-00 RFC2747 PROPOSED STANDARD PROPOSED STANDARD RFC3098 How to Advertise Responsibly Using E-Mail and Newsgroups or - how NOT to $$$$$ MAKE ENEMIES FAST! $$$$$ T. Gavin D. Eastlake 3rd S. Hambridge April 2001 ASCII 64687 28 internet marketing users service providers isps This memo offers useful suggestions for responsible advertising techniques that can be used via the internet in an environment where the advertiser, recipients, and the Internet Community can coexist in a productive and mutually respectful fashion. This memo provides information for the Internet community. ietf-run-adverts-02 FYI0038 INFORMATIONAL INFORMATIONAL RFC3099 Request for Comments Summary RFC Numbers 3000-3099 S. Ginoza November 2001 ASCII 48990 25 INFORMATIONAL INFORMATIONAL RFC3100 RFC3101 The OSPF Not-So-Stubby Area (NSSA) Option P. Murphy January 2003 ASCII 76243 33 OSPF-NSSA stub external routes backward compatible This memo documents an optional type of Open Shortest Path First (OSPF) area that is 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. The OSPF NSSA Option was originally defined in RFC 1587. The functional differences between this memo and RFC 1587 are explained in Appendix F. All differences, while expanding capability, are backward-compatible in nature. Implementations of this memo and of RFC 1587 will interoperate. [STANDARDS TRACK] ietf-ospf-nssa-update-11 RFC1587 PROPOSED STANDARD PROPOSED STANDARD RFC3102 Realm Specific IP: Framework M. Borella J. Lo D. Grabelsky G. Montenegro October 2001 ASCII 73856 30 RSIP end-to-end NAT addressing requirements This document examines the general framework of Realm Specific IP (RSIP). RSIP is intended as a alternative to NAT in which the end-to- end integrity of packets is maintained. We focus on implementation issues, deployment scenarios, and interaction with other layer-three protocols. This memo defines an Experimental Protocol for the Internet community. ietf-nat-rsip-framework-05 EXPERIMENTAL EXPERIMENTAL RFC3103 Realm Specific IP: Protocol Specification M. Borella D. Grabelsky J. Lo K. Taniguchi October 2001 ASCII 115855 54 RSIP host gateway NAT requirements This document presents a protocol with which to implement Realm Specific IP (RSIP). The protocol defined herein allows negotiation of resources between an RSIP host and gateway, so that the host can lease some of the gateway's addressing parameters in order to establish a global network presence. This protocol is designed to operate on the application layer and to use its own TCP or UDP port. In particular, the protocol allows a gateway to allocate addressing and control parameters to a host such that a flow policy can be enforced at the gateway. This memo defines an Experimental Protocol for the Internet community. ietf-nat-rsip-protocol-07 EXPERIMENTAL EXPERIMENTAL RFC3104 RSIP Support for End-to-end IPsec G. Montenegro M. Borella October 2001 ASCII 38719 19 realm specific internet protocol NAT addressing requirements This document proposes mechanisms that enable Realm Specific IP (RSIP) to handle end-to-end IPsec (IP Security). This memo defines an Experimental Protocol for the Internet community. ietf-nat-rsip-ipsec-04 EXPERIMENTAL EXPERIMENTAL RFC3105 Finding an RSIP Server with SLP J. Kempf G. Montenegro October 2001 ASCII 21427 11 realm specific internet protocol service location NAT addressing requirements This document contains an SLP service type template that describes the advertisements made by RSIP servers for their services. This memo defines an Experimental Protocol for the Internet community. ietf-nat-rsip-slp-00 EXPERIMENTAL EXPERIMENTAL RFC3106 ECML v1.1: Field Specifications for E-Commerce D. Eastlake 3rd T. Goldstein April 2001 ASCII 40715 20 electronic modeling language Customers are frequently required to enter substantial amounts of information at an Internet merchant site in order to complete a purchase or other transaction, especially the first time they go there. A standard set of information fields is defined as the first version of an Electronic Commerce Modeling Language (ECML) so that this task can be more easily automated, for example by wallet software that could fill in fields. Even for the manual data entry case, customers will be less confused by varying merchant sites if a substantial number adopt these standard fields. In addition, some fields are defined for merchant to consumer communication. This memo provides information for the Internet community. eastlake-ecom-fields2-05 RFC2706 INFORMATIONAL INFORMATIONAL RFC3107 Carrying Label Information in BGP-4 Y. Rekhter E. Rosen May 2001 ASCII 16442 8 SDP asynchronous transfer mode AAL syntax adaption layer This document specifies the way in which the label mapping information for a particular route is piggybacked in the same Border Gateway Protocol (BGP) Update message that is used to distribute the route itself. [STANDARDS TRACK] ietf-mpls-bgp4-mpls-04 PROPOSED STANDARD PROPOSED STANDARD RFC3108 Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer Connections R. Kumar M. Mostafa May 2001 ASCII 248037 110 asynchronous transfer mode AAL syntax adaption layer This document describes conventions for using the Session Description Protocol (SDP) described in RFC 2327 for controlling ATM Bearer Connections, and any associated ATM Adaptation Layer (AAL). The AALs addressed are Type 1, Type 2 and Type 5. [STANDARDS TRACK] ietf-mmusic-sdp-atm-05 PROPOSED STANDARD PROPOSED STANDARD RFC3109 Request to Move STD 39 to Historic Status R. Braden R. Bush J. Klensin May 2001 ASCII 5841 4 BBN 1822 host imp arpanet This memo changes the status of STD 39, BBN Report 1822, "Specification of the Interconnection of a Host and an IMP", from Standard to Historic. This memo provides information for the Internet community. ymbk-std39-historic-02 INFORMATIONAL INFORMATIONAL RFC3110 RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS) D. Eastlake 3rd May 2001 ASCII 14587 7 RRs resource records security This document describes how to produce RSA/SHA1 SIG resource records (RRs) in Section 3 and, so as to completely replace RFC 2537, describes how to produce RSA KEY RRs in Section 2. [STANDARDS TRACK] ietf-dnsext-rsa-03 RFC2537 PROPOSED STANDARD PROPOSED STANDARD RFC3111 Service Location Protocol Modifications for IPv6 E. Guttman May 2001 ASCII 25543 13 SLP internet protocol This document defines the Service Location Protocol Version 2's (SLPv2) use over IPv6 networks. Since this protocol relies on UDP and TCP, the changes to support its use over IPv6 are minor. [STANDARDS TRACK] ietf-svrloc-ipv6-12 PROPOSED STANDARD PROPOSED STANDARD RFC3112 LDAP Authentication Password Schema K. Zeilenga May 2001 ASCII 17116 9 lightweight directory access protocol This document describes schema in support of user/password authentication in a LDAP (Lightweight Directory Access Protocol) directory including the authPassword attribute type. This memo provides information for the Internet community. zeilenga-ldap-authpsswd-05 INFORMATIONAL INFORMATIONAL RFC3113 3GPP-IETF Standardization Collaboration K. Rosenbrock R. Sanmugam S. Bradner J. Klensin June 2001 ASCII 11405 7 internet engineering task force third generation partnership project This document describes the standardization collaboration between 3GPP and IETF. This memo provides information for the Internet community. 3gpp-collaboration-01 INFORMATIONAL INFORMATIONAL RFC3114 Implementing Company Classification Policy with the S/MIME Security Label W. Nicolls May 2002 ASCII 27764 14 data multipurpose internet mail extensions access control information classification security category This document discusses how company security policy for data classification can be mapped to the S/MIME security label. Actual policies from three companies provide worked examples. This memo provides information for the Internet community. ietf-smime-seclabel-03 INFORMATIONAL INFORMATIONAL RFC3115 Mobile IP Vendor/Organization-Specific Extensions G. Dommety K. Leung April 2001 ASCII 16363 9 internet protocol This document defines two new extensions to Mobile IP. These extensions will facilitate equipment vendors and organizations to make specific use of these extensions as they see fit for research or deployment purposes. [STANDARDS TRACK] RFC3025 PROPOSED STANDARD PROPOSED STANDARD RFC3116 Methodology for ATM Benchmarking J. Dunn C. Martin June 2001 ASCII 295052 127 asynchronous transfer mode formats switching This document discusses and defines a number of tests that may be used to describe the performance characteristics of ATM (Asynchronous Transfer Mode) based switching devices. In addition to defining the tests this document also describes specific formats for reporting the results of the tests. This memo provides information for the Internet community. ietf-bmwg-atm-method-03 INFORMATIONAL INFORMATIONAL RFC3117 On the Design of Application Protocols M. Rose November 2001 ASCII 57279 27 beep bxxp blocks extensible exchange text binary This memo describes the design principles for the Blocks eXtensible eXchange Protocol (BXXP). This memo provides information for the Internet community. mrose-beep-design-03 INFORMATIONAL INFORMATIONAL RFC3118 Authentication for DHCP Messages R. Droms W. Arbaugh Editors June 2001 ASCII 35536 17 dynamic host configuration protocol verification This document defines a new Dynamic Host Configuration Protocol (DHCP) option through which authorization tickets can be easily generated and newly attached hosts with proper authorization can be automatically configured from an authenticated DHCP server. [STANDARDS TRACK] ietf-dhc-authentication-16 PROPOSED STANDARD PROPOSED STANDARD RFC3119 A More Loss-Tolerant RTP Payload Format for MP3 Audio R. Finlayson June 2001 ASCII 37796 19 real-time protocol moving picture experts group This document describes a RTP (Real-Time Protocol) payload format for transporting MPEG (Moving Picture Experts Group) 1 or 2, layer III audio (commonly known as "MP3"). This format is an alternative to that described in RFC 2250, and performs better if there is packet loss. [STANDARDS TRACK] ietf-avt-rtp-mp3-06 PROPOSED STANDARD PROPOSED STANDARD RFC3120 A URN Namespace for XML.org K. Best N. Walsh June 2001 ASCII 8068 5 uniform resource name extensible markup language This document describes a URN (Uniform Resource Name) namespace that is engineered by the Organization for the Advancement of Structured Information Standards (OASIS) for naming persistent resources stored in the XML.org repository (such as XML (Extensible Markup Language) Document Type Definitions, XML Schemas, Namespaces, Stylesheets, and other documents). This memo provides information for the Internet community. best-xmlorg-01 INFORMATIONAL INFORMATIONAL RFC3121 A URN Namespace for OASIS K. Best N. Walsh June 2001 ASCII 11074 7 uniform resource name organization for the advancement of structured information standards This document describes a URN (Uniform Resource Name) namespace that is engineered by the Organization for the Advancement of Structured Information Standards (OASIS) for naming persistent resources published by OASIS (such as OASIS Standards, XML (Extensible Markup Language) Document Type Definitions, XML Schemas, Namespaces, Stylesheets, and other documents). This memo provides information for the Internet community. best-urn-oasis-02 INFORMATIONAL INFORMATIONAL RFC3122 Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification A. Conta June 2001 ASCII 40416 20 internet protocol IND link-layer This memo describes extensions to the IPv6 Neighbor Discovery that allow a node to determine and advertise an IPv6 address corresponding to a given link-layer address. [STANDARDS TRACK] ietf-ion-ipv6-ind-05 PROPOSED STANDARD PROPOSED STANDARD RFC3123 A DNS RR Type for Lists of Address Prefixes (APL RR) P. Koch June 2001 ASCII 14648 8 domain name system resource record The Domain Name System (DNS) is primarily used to translate domain names into IPv4 addresses using A RRs (Resource Records). Several approaches exist to describe networks or address ranges. This document specifies a new DNS RR type "APL" for address prefix lists. This memo defines an Experimental Protocol for the Internet community. ietf-dnsext-apl-rr-02 EXPERIMENTAL EXPERIMENTAL RFC3124 The Congestion Manager H. Balakrishnan S. Seshan June 2001 ASCII 53591 22 network stream end-system module This document describes the Congestion Manager (CM), an end-system module that enables an ensemble of multiple concurrent streams from a sender destined to the same receiver and sharing the same congestion properties to perform proper congestion avoidance and control, and allows applications to easily adapt to network congestion. [STANDARDS TRACK] ietf-ecm-cm-04 PROPOSED STANDARD PROPOSED STANDARD RFC3125 Electronic Signature Policies J. Ross D. Pinkas N. Pope September 2001 ASCII 95505 44 signer purchase contract invoice transactions applications This document defines signature policies for electronic signatures. A signature policy is a set of rules for the creation and validation of an electronic signature, under which the validity of signature can be determined. A given legal/contractual context may recognize a particular signature policy as meeting its requirements. This memo defines an Experimental Protocol for the Internet community. ietf-smime-espolicies-00 EXPERIMENTAL EXPERIMENTAL RFC3126 Electronic Signature Formats for long term electronic signatures D. Pinkas J. Ross N. Pope September 2001 ASCII 175886 84 purchase contract invoice application smart cards data This document defines the format of an electronic signature that can remain valid over long periods. This includes evidence as to its validity even if the signer or verifying party later attempts to deny (i.e., repudiates the validity of the signature). This memo provides information for the Internet community. ietf-smime-esformats-03 INFORMATIONAL INFORMATIONAL RFC3127 Authentication, Authorization, and Accounting: Protocol Evaluation D. Mitton M. St.Johns S. Barkley D. Nelson B. Patil M. Stevens B. Wolff June 2001 ASCII 170579 84 AAA network access requirements This memo represents the process and findings of the Authentication, Authorization, and Accounting Working Group (AAA WG) panel evaluating protocols proposed against the AAA Network Access Requirements, RFC 2989. This memo provides information for the Internet community. ietf-aaa-proto-eval-02 INFORMATIONAL INFORMATIONAL RFC3128 Protection Against a Variant of the Tiny Fragment Attack (RFC 1858) I. Miller June 2001 ASCII 8242 5 firewalls internet This document discusses how RFC 1858 compliant filters can be vulnerable to a variant of the "Tiny Fragment Attack" described in section 3.1 of the RFC. This document describes the attack and recommends corrective action. This memo provides information for the Internet community. miller-rfc1858-cmts-00 RFC1858 INFORMATIONAL INFORMATIONAL RFC3129 Requirements for Kerberized Internet Negotiation of Keys M. Thomas June 2001 ASCII 11401 6 KINK cryptographic security authentication The goal of this document is to produce a streamlined, fast, easily managed, and cryptographically sound protocol without requiring public key. This memo provides information for the Internet community. ietf-kink-reqmt-03 INFORMATIONAL INFORMATIONAL RFC3130 Notes from the State-Of-The-Technology: DNSSEC E. Lewis June 2001 ASCII 22291 10 domain name system security extensions report This is a memo of a DNSSEC (Domain Name System Security Extensions) status meeting. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC3131 3GPP2-IETF Standardization Collaboration S. Bradner P. Calhoun H. Cuschieri S. Dennett G. Flynn M. Lipford M. McPheters June 2001 ASCII 13643 8 internet engineering task force third generation partnership project This document describes the standardization collaboration between 3GPP2 and IETF. This memo provides information for the Internet community. bradner-3gpp2-collaboration-01 INFORMATIONAL INFORMATIONAL RFC3132 Dormant Mode Host Alerting ("IP Paging") Problem Statement J. Kempf June 2001 ASCII 34985 14 molulity radio link internet protocl This memo describes paging, assesses the need for IP paging, and presents a list of recommendations for Seamoby charter items regarding work on paging. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC3133 Terminology for Frame Relay Benchmarking J. Dunn C. Martin June 2001 ASCII 44182 24 switching devices signaling This memo discusses and defines terms associated with performance benchmarking tests and the results of these tests in the context of frame relay switching devices. This memo provides information for the Internet community. ietf-bmwg-atm-term-abr-03 INFORMATIONAL INFORMATIONAL RFC3134 Terminology for ATM ABR Benchmarking J. Dunn C. Martin June 2001 ASCII 29542 16 asynchronous transfer mode available bit rate This memo discusses and defines terms associated with performance benchmarking tests and the results of these tests in the context of Asynchronous Transfer Mode (ATM) based switching devices supporting ABR (Available Bit Rate). This memo provides information for the Internet community. ietf-bmwg-atm-term-abr-03 INFORMATIONAL INFORMATIONAL RFC3135 Performance Enhancing Proxies Intended to Mitigate Link-Related Degradations J. Border M. Kojo J. Griner G. Montenegro Z. Shelby June 2001 ASCII 114825 45 PEP PILC TCP transmission control protocol This document is a survey of Performance Enhancing Proxies (PEPs) often employed to improve degraded TCP performance caused by characteristics of specific link environments, for example, in satellite, wireless WAN, and wireless LAN environments. This memo provides information for the Internet community. ietf-pilc-pep-07 INFORMATIONAL INFORMATIONAL RFC3136 The SPIRITS Architecture L. Slutsman Editor I. Faynberg H. Lu M. Weissman June 2001 ASCII 19241 10 PSTN public switched telephone network This document describes the architecture for supporting SPIRITS services, which are those originating in the PSTN (Public Switched Telephone Network)and necessitating the interactions between the PSTN and the Internet. This memo provides information for the Internet community. ietf-spirits-architecture-03 INFORMATIONAL INFORMATIONAL RFC3137 OSPF Stub Router Advertisement A. Retana L. Nguyen R. White A. Zinin D. McPherson June 2001 ASCII 8140 5 open shortest path first This memo describes a backward-compatible technique that may be used by OSPF (Open Shortest Path First) implementations to advertise unavailability to forward transit traffic or to lower the preference level for the paths through such a router. This memo provides information for the Internet community. ietf-ospf-stub-adv-02 INFORMATIONAL INFORMATIONAL RFC3138 Extended Assignments in 233/8 D. Meyer June 2001 ASCII 6776 4 internet address AS autonomous system number This memo provides describes the mapping of the GLOP addresses corresponding to the private AS space. This memo provides information for the Internet community. ietf-mboned-glop-extensions-02 INFORMATIONAL INFORMATIONAL RFC3139 Requirements for Configuration Management of IP-based Networks L. Sanchez K. McCloghrie J. Saperia June 2001 ASCII 23624 11 internet protocol This memo discusses different approaches to configure networks and identifies a set of configuration management requirements for IP-based networks. This memo provides information for the Internet community. ops-ip-config-management-reqmnts-01 INFORMATIONAL INFORMATIONAL RFC3140 Per Hop Behavior Identification Codes D. Black S. Brim B. Carpenter F. Le Faucheur June 2001 ASCII 16586 8 PHB differentiated services codepoint DSCP This document defines a 16 bit encoding mechanism for the identification of differentiated services Per Hop Behaviors in protocol messages. It replaces RFC 2836. [STANDARDS TRACK] ietf-diffserv-2836bis-02 RFC2836 PROPOSED STANDARD PROPOSED STANDARD RFC3141 CDMA2000 Wireless Data Requirements for AAA T. Hiller P. Walsh X. Chen M. Munson G. Dommety S. Sivalingham B. Lim P. McCann H. Shiino B. Hirschman S. Manning R. Hsu H. Koo M. Lipford P. Calhoun C. Lo E. Jaques E. Campbell Y. Xu S. Baba T. Ayaki T. Seki A. Hameed June 2001 ASCII 27998 16 authentication authorization accounting This memo specifies cdma2000 wireless data AAA (Authentication, Authorization, Accounting) requirements associated with third generation wireless architecture that supports roaming among service providers for traditional PPP and Mobile IP services. This memo provides information for the Internet community. hiller-cdma2000-aaa-02 INFORMATIONAL INFORMATIONAL RFC3142 An IPv6-to-IPv4 Transport Relay Translator J. Hagino K. Yamamoto June 2001 ASCII 20864 11 TRT internet protocol The document describes an IPv6-to-IPv4 transport relay translator (TRT). This memo provides information for the Internet community. ietf-ngtrans-tcpudp-relay-04 INFORMATIONAL INFORMATIONAL RFC3143 Known HTTP Proxy/Caching Problems I. Cooper J. Dilley June 2001 ASCII 57117 32 www world wide web hypertext transfer protocol This document catalogs a number of known problems with World Wide Web (WWW) (caching) proxies and cache servers. The goal of the document is to provide a discussion of the problems and proposed workarounds, and ultimately to improve conditions by illustrating problems. This memo provides information for the Internet community. cooper-wrec-known-prob-01 INFORMATIONAL INFORMATIONAL RFC3144 Remote Monitoring MIB Extensions for Interface Parameters Monitoring D. Romascanu August 2001 ASCII 62491 30 management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. The document proposes an extension to the Remote Monitoring MIB with a method of sorting the interfaces of a monitored device according to values of parameters specific to this interface. [STANDARDS TRACK] ietf-rmonmib-iftopn-mib-05 PROPOSED STANDARD PROPOSED STANDARD RFC3145 L2TP Disconnect Cause Information R. Verma M. Verma J. Carlson July 2001 ASCII 17421 10 layer2 tunneling PPP point-to-point accounting debugging This document provides an extension to the Layer 2 Tunneling Protocol ("L2TP"), a mechanism for tunneling Point-to-Point Protocol (PPP) sessions. [STANDARDS TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC3146 Transmission of IPv6 Packets over IEEE 1394 Networks K. Fujisawa A. Onoe October 2001 ASCII 16569 8 link-local addresses statelessly autoconfigured This document describes the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE1394 networks. [STANDARDS TRACK] ietf-ipngwg-1394-02 PROPOSED STANDARD PROPOSED STANDARD RFC3147 Generic Routing Encapsulation over CLNS Networks P. Christian July 2001 ASCII 14125 8 connectionless network service GRE layer protocol This document proposes a method for transporting an arbitrary protocol over a CLNS (Connectionless Network Service) network using GRE (Generic Routing Encapsulation). This may then be used as a method to tunnel IPv4 or IPv6 over CLNS. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC3148 A Framework for Defining Empirical Bulk Transfer Capacity Metrics M. Mathis M. Allman July 2001 ASCII 36041 16 BTC transport data This document defines a framework for standardizing multiple BTC (Bulk Transport Capacity) metrics that parallel the permitted transport diversity. This memo provides information for the Internet community. ietf-ippm-btc-framework-06 INFORMATIONAL INFORMATIONAL RFC3149 MGCP Business Phone Packages A. Srinath G. Levendel K. Fritz R. Kalyanaram September 2001 ASCII 77304 41 media gateway control packages This document describes a collection of MGCP (Media Gateway Control Protocol) packages that can be used to take advantage of the feature keys and displays on digital business phones and IP-Phones. This memo provides information for the Internet community. srinath-mgcp-bus-packages-01 INFORMATIONAL INFORMATIONAL RFC3150 End-to-end Performance Implications of Slow Links S. Dawkins G. Montenegro M. Kojo V. Magret July 2001 ASCII 39942 17 PILC data applications header compression This document makes performance-related recommendations for users of network paths that traverse "very low bit-rate" links. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-pilc-slow-06 BCP0048 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3151 A URN Namespace for Public Identifiers N. Walsh J. Cowan P. Grosso August 2001 ASCII 15595 9 uniform resource name publicid This document describes a URN (Uniform Resource Name) namespace that is designed to allow Public Identifiers to be expressed in URI (Uniform Resource Identifiers) syntax. This memo provides information for the Internet community. walsh-urn-publicid-01 INFORMATIONAL INFORMATIONAL RFC3152 Delegation of IP6.ARPA R. Bush August 2001 ASCII 5727 4 internet protocol domain name system DNS zone This document discusses the need for delegation of the IP6.ARPA DNS zone, and specifies a plan for the technical operation thereof. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ymbk-ip6-arpa-delegation-02 RFC3596 RFC2874 RFC2772 RFC2766 RFC2553 RFC1886 BCP0049 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3153 PPP Multiplexing R. Pazhyannur I. Ali C. Fox August 2001 ASCII 19244 9 point-to-point protocol This document describes a method to reduce the PPP (Point-to-Point Protocol) framing overhead used to transport small packets over slow links. [STANDARDS TRACK] ietf-pppext-pppmux-03 PROPOSED STANDARD PROPOSED STANDARD RFC3154 Requirements and Functional Architecture for an IP Host Alerting Protocol J. Kempf C. Castelluccia P. Mutaf N. Nakajima Y. Ohba R. Ramjee Y. Saifullah B. Sarikaya X. Xu August 2001 ASCII 31534 16 internet protocol paging mobile hosts This document develops an architecture and a set of requirements needed to support alerting of hosts that are in dormant mode. The architecture and requirements are designed to guide development of an IP protocol for alerting dormant IP mobile hosts, commonly called paging. This memo provides information for the Internet community. ietf-seamoby-paging-requirements-01 INFORMATIONAL INFORMATIONAL RFC3155 End-to-end Performance Implications of Links with Errors S. Dawkins G. Montenegro M. Kojo V. Magret N. Vaidya August 2001 ASCII 36388 16 TCP transmission control protocol This document discusses the specific TCP mechanisms that are problematic in environments with high uncorrected error rates, and discusses what can be done to mitigate the problems without introducing intermediate devices into the connection. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-pilc-error-08 BCP0050 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3156 MIME Security with OpenPGP M. Elkins D. Del Torto R. Levien T. Roessler August 2001 ASCII 26809 15 MIME-PGP Authentication Encryption This document describes how the OpenPGP Message Format can be used to provide privacy and authentication using the Multipurpose Internet Mail Extensions (MIME) security content types described in RFC 1847. [STANDARDS TRACK] ietf-openpgp-mime-07 RFC2015 PROPOSED STANDARD PROPOSED STANDARD RFC3157 Securely Available Credentials - Requirements A. Arsenault S. Farrell August 2001 ASCII 46169 20 SACRED trusted roots private keys PSE personal security environment This document describes requirements to be placed on Securely Available Credentials (SACRED) protocols. This memo provides information for the Internet community. ietf-sacred-reqs-03 INFORMATIONAL INFORMATIONAL RFC3158 RTP Testing Strategies C. Perkins J. Rosenberg H. Schulzrinne August 2001 ASCII 48208 22 real-time transport protocol This memo describes a possible testing strategy for RTP (real-time transport protocol) implementations. This memo provides information for the Internet community. ietf-avt-rtptest-06 INFORMATIONAL INFORMATIONAL RFC3159 Structure of Policy Provisioning Information (SPPI) K. McCloghrie M. Fine J. Seligson K. Chan S. Hahn R. Sahita A. Smith F. Reichmeyer August 2001 ASCII 78621 40 PIB base SNMP simple network management information SMI This document, the Structure of Policy Provisioning Information (SPPI), defines the adapted subset of SNMP's Structure of Management Information (SMI) used to write Policy Information Base (PIB) modules. [STANDARDS TRACK] ietf-rap-sppi-07 PROPOSED STANDARD PROPOSED STANDARD RFC3160 The Tao of IETF - A Novice's Guide to the Internet Engineering Task Force S. Harris August 2001 ASCII 98411 38 Internet Engineering Task Force Meeting This document describes the inner workings of IETF meetings and Working Groups, discusses organizations related to the IETF, and introduces the standards process. This memo provides information for the Internet community. ietf-uswg-tao-06 RFC1718 FYI0017 INFORMATIONAL INFORMATIONAL RFC3161 Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP) C. Adams P. Cain D. Pinkas R. Zuccherato August 2001 ASCII 54585 26 TSA authority security request response This document describes the format of a request sent to a Time Stamping Authority (TSA) and of the response that is returned. It also establishes several security-relevant requirements for TSA operation, with regards to processing requests to generate responses. [STANDARDS TRACK] ietf-pkix-time-stamp-15 PROPOSED STANDARD PROPOSED STANDARD RFC3162 RADIUS and IPv6 B. Aboba G. Zorn D. Mitton August 2001 ASCII 20492 12 remote authentication dial in user service attributes This document specifies the operation of RADIUS (Remote Authentication Dial In User Service) when run over IPv6 as well as the RADIUS attributes used to support IPv6 network access. [STANDARDS TRACK] aboba-radius-ipv6-10 PROPOSED STANDARD PROPOSED STANDARD RFC3163 ISO/IEC 9798-3 Authentication SASL Mechanism R. Zuccherato M. Nystrom August 2001 ASCII 32498 17 simple authentication security layer This document defines a SASL (Simple Authentication and Security Layer) authentication mechanism based on ISO/IEC 9798-3 and FIPS PUB 196 entity authentication. This memo defines an Experimental Protocol for the Internet community. zuccherato-9798-3-sasl-03 EXPERIMENTAL EXPERIMENTAL RFC3164 The BSD Syslog Protocol C. Lonvick August 2001 ASCII 72951 29 berkeley software distribution transmission messages This document describes the observed behavior of the syslog protocol. This memo provides information for the Internet community. ietf-syslog-syslog-12 INFORMATIONAL INFORMATIONAL RFC3165 Definitions of Managed Objects for the Delegation of Management Scripts D. Levi J. Schoenwaelder August 2001 ASCII 134479 64 mib information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a set of managed objects that allow the delegation of management scripts to distributed managers. [STANDARDS TRACK] ietf-disman-script-mib-v2-04 RFC2592 PROPOSED STANDARD PROPOSED STANDARD RFC3166 Request to Move RFC 1403 to Historic Status D. Meyer J. Scudder August 2001 ASCII 3740 3 BGP-OSPF Border gateway protocol Open shortest path first routing RFC 1403, "BGP OSPF Interaction", describes technology which is no longer used. This document requests that RFC 1403 be moved to Historic status. This memo provides information for the Internet community. meyer-rfc1403-historic-00 INFORMATIONAL INFORMATIONAL RFC3167 Request to Move RFC 1745 to Historic Status D. Meyer J. Scudder August 2001 ASCII 3825 3 BGP4/IDRP Internet Inter-Domain Routing Protocol Border Gateway Open Shortest Path First RFC 1745, "BGP4/IDRP for IP---OSPF Interaction", describes technology which was never deployed in the public internet. This document requests that RFC 1745 be moved to Historic status. This memo provides information for the Internet community. meyer-rfc1745-historic-00 INFORMATIONAL INFORMATIONAL RFC3168 The Addition of Explicit Congestion Notification (ECN) to IP K. Ramakrishnan S. Floyd D. Black September 2001 ASCII 170966 63 internet protocol header This memo specifies the incorporation of ECN (Explicit Congestion Notification) to TCP and IP, including ECN's use of two bits in the IP header. [STANDARDS TRACK] ietf-tsvwg-ecn-04 RFC2481 RFC2474 RFC2401 RFC0793 PROPOSED STANDARD PROPOSED STANDARD RFC3169 Criteria for Evaluating Network Access Server Protocols M. Beadles D. Mitton September 2001 ASCII 35303 17 NAS network device AAA authentication authorization accounting This document defines requirements for protocols used by Network Access Servers (NAS). This memo provides information for the Internet community. ietf-nasreq-criteria-06 Network Access Server Requirements Working Group INFORMATIONAL INFORMATIONAL RFC3170 IP Multicast Applications: Challenges and Solutions B. Quinn K. Almeroth September 2001 ASCII 67207 28 internet protocol unicast This document describes the challenges involved with designing and implementing multicast applications. It is an introductory guide for application developers that highlights the unique considerations of multicast applications as compared to unicast applications. This memo provides information for the Internet community. ietf-mboned-mcast-apps-02 INFORMATIONAL INFORMATIONAL RFC3171 IANA Guidelines for IPv4 Multicast Address Assignments Z. Albanna K. Almeroth D. Meyer M. Schipper August 2001 ASCII 15389 8 internet assigned numbers authority protocol parameters This memo provides guidance for the Internet Assigned Numbers Authority (IANA) in assigning IPv4 multicast addresses. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-mboned-iana-ipv4-mcast-guidelines-04 BCP0051 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3172 Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa") G. Huston Editor September 2001 ASCII 18097 8 database DNS domain name system This memo describes the management and operational requirements for the address and routing parameter area ("arpa") domain. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. iab-arpa-03 BCP0052 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3173 IP Payload Compression Protocol (IPComp) A. Shacham B. Monsour R. Pereira M. Thomas September 2001 ASCII 15389 13 IPCOMP internet protocol datagram lossless This document describes a protocol intended to provide lossless compression for Internet Protocol datagrams in an Internet environment. [STANDARDS TRACK] shacham-ippcp-rfc2392bis-08 RFC2393 PROPOSED STANDARD PROPOSED STANDARD RFC3174 US Secure Hash Algorithm 1 (SHA1) D. Eastlake 3rd P. Jones September 2001 ASCII 35525 22 FIPS federal information processing standard The purpose of this document is to make the SHA-1 (Secure Hash Algorithm 1) hash algorithm conveniently available to the Internet community. This memo provides information for the Internet community. eastlake-sha1-02 INFORMATIONAL INFORMATIONAL RFC3175 Aggregation of RSVP for IPv4 and IPv6 Reservations F. Baker C. Iturralde F. Le Faucheur B. Davie September 2001 ASCII 88681 36 resource reservation protocol internet ATM asynchronous transfer mode This document describes the use of a single RSVP (Resource ReSerVation Protocol) reservation to aggregate other RSVP reservations across a transit routing region, in a manner conceptually similar to the use of Virtual Paths in an ATM (Asynchronous Transfer Mode) network. It proposes a way to dynamically create the aggregate reservation, classify the traffic for which the aggregate reservation applies, determine how much bandwidth is needed to achieve the requirement, and recover the bandwidth when the sub-reservations are no longer required. It also contains recommendations concerning algorithms and policies for predictive reservations. [STANDARDS TRACK] ietf-issll-rsvp-aggr-04 PROPOSED STANDARD PROPOSED STANDARD RFC3176 InMon Corporation's sFlow: A Method for Monitoring Traffic in Switched and Routed Networks P. Phaal S. Panchen N. McKee September 2001 ASCII 60171 31 agent data MIB management information base This memo defines InMon Corporation's sFlow system. sFlow is a technology for monitoring traffic in data networks containing switches and routers. In particular, it defines the sampling mechanisms implemented in an sFlow Agent for monitoring traffic, the sFlow MIB for controlling the sFlow Agent, and the format of sample data used by the sFlow Agent when forwarding data to a central data collector. This memo provides information for the Internet community. phaal-sflow-montraffic-01 INFORMATIONAL INFORMATIONAL RFC3177 IAB/IESG Recommendations on IPv6 Address Allocations to Sites IAB IESG September 2001 ASCII 23178 10 internet architecture board engineering steering group protocol This document provides recommendations to the addressing registries (APNIC, ARIN and RIPE-NCC) on policies for assigning IPv6 address blocks to end sites. In particular, it recommends the assignment of /48 in the general case, /64 when it is known that one and only one subnet is needed and /128 when it is absolutely known that one and only one device is connecting. iesg-ipv6-addressing-recommendations-03 INFORMATIONAL INFORMATIONAL RFC3178 IPv6 Multihoming Support at Site Exit Routers J. Hagino H. Snyder October 2001 ASCII 24453 12 internet protocol ISP Service Provider Routing The document describes a mechanism for basic IPv6 multihoming support, and its operational requirements. This memo provides information for the Internet community. ietf-ipngwg-ipv6-2260-02 INFORMATIONAL INFORMATIONAL RFC3179 Script MIB Extensibility Protocol Version 1.1 J. Schoenwaelder J. Quittek October 2001 ASCII 56311 25 SMX language management information base The Script MIB extensibility protocol (SMX) defined in this memo separates language specific runtime systems from language independent Script MIB implementations. The IETF Script MIB defines an interface for the delegation of management functions based on the Internet management framework. This memo defines an Experimental Protocol for the Internet community. schoenw-rfc-2593-update-04 RFC2593 EXPERIMENTAL EXPERIMENTAL RFC3180 GLOP Addressing in 233/8 D. Meyer P. Lothberg September 2001 ASCII 8225 5 static multicast This document defines the policy for the use of 233/8 for statically e assigned multicast addresses. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-mboned-glop-update-01 RFC2770 BCP0053 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3181 Signaled Preemption Priority Policy Element S. Herzog October 2001 ASCII 21990 12 rsvp resource reservation protocol cops common open service This document describes a preemption priority policy element for use by signaled policy based admission protocols (such as the Resource ReSerVation Protocol (RSVP) and Common Open Policy Service (COPS). [STANDARDS TRACK] ietf-rap-signaled-priority-v2-00 RFC2751 PROPOSED STANDARD PROPOSED STANDARD RFC3182 Identity Representation for RSVP S. Yadav R. Yavatkar R. Pabbati P. Ford T. Moore S. Herzog R. Hess October 2001 ASCII 36544 18 resource reservation protocol This document describes the representation of identity information in POLICY_DATA object for supporting policy based admission control in the Resource ReSerVation Protocol (RSVP). The goal of identity representation is to allow a process on a system to securely identify the owner and the application of the communicating process (e.g., user id) and convey this information in RSVP messages (PATH or RESV) in a secure manner. We describe the encoding of identities as RSVP policy element. We describe the processing rules to generate identity policy elements for multicast merged flows. [STANDARDS TRACK] ietf-rap-rsvp-newidentity-01 RFC2752 PROPOSED STANDARD PROPOSED STANDARD RFC3183 Domain Security Services using S/MIME T. Dean W. Ottaway October 2001 ASCII 57129 24 secure/multipurpose internet mail extensions This document describes how the S/MIME (Secure/Multipurpose Internet Mail Extensions) protocol can be processed and generated by a number of components of a communication system, such as message transfer agents, guards and gateways to deliver security services. These services are collectively referred to as 'Domain Security Services'. This memo defines an Experimental Protocol for the Internet community. ietf-smime-domsec-09 EXPERIMENTAL EXPERIMENTAL RFC3184 IETF Guidelines for Conduct S. Harris October 2001 ASCII 7413 4 interent engineering task force This document provides a set of guidelines for personal interaction in the Internet Engineering Task Force. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-poisson-code-04 BCP0054 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3185 Reuse of CMS Content Encryption Keys S. Farrell S. Turner October 2001 ASCII 20404 10 cryptographic message syntax data packets This document describes a way to include a key identifier in a CMS (Cryptographic Message Syntax) enveloped data structure, so that the content encryption key can be re-used for further enveloped data packets. [STANDARDS TRACK] ietf-smime-rcek-04 PROPOSED STANDARD PROPOSED STANDARD RFC3186 MAPOS/PPP Tunneling mode S. Shimizu T. Kawano K. Murakami E. Beier December 2001 ASCII 27109 14 multiple access protocol over SONET/SDH point-to-point This document specifies tunneling configuration over MAPOS (Multiple Access Protocol over SONET/SDH) networks. Using this mode, a MAPOS network can provide transparent point-to-point link for PPP over SONET/SDH (Packet over SONET/SDH, POS) without any additional overhead. This memo provides information for the Internet community. shimizu-ppp-mapos-01 INFORMATIONAL INFORMATIONAL RFC3187 Using International Standard Book Numbers as Uniform Resource Names J. Hakala H. Walravens October 2001 ASCII 22620 11 isbn urn bibliographic identifiers This document discusses how International Standard Book Numbers (ISBN) can be supported within the URN (Uniform Resource Names) framework and the syntax for URNs defined in RFC 2141. Much of the discussion below is based on the ideas expressed in RFC 2288. This memo provides information for the Internet community. hakala-isbn-01 INFORMATIONAL INFORMATIONAL RFC3188 Using National Bibliography Numbers as Uniform Resource Names J. Hakala October 2001 ASCII 27923 13 urn nbn national libraries This document discusses how national bibliography numbers (persistent and unique identifiers assigned by the national libraries) can be supported within the URN (Uniform Resource Names) framework and the syntax for URNs defined in RFC 2141. Much of the discussion is based on the ideas expressed in RFC 2288. This memo provides information for the Internet community. hakala-nbn-01 INFORMATIONAL INFORMATIONAL RFC3189 RTP Payload Format for DV (IEC 61834) Video K. Kobayashi A. Ogawa S. Casner C. Bormann January 2002 ASCII 25991 13 real-time transport protocol This document specifies the packetization scheme for encapsulating the compressed digital video data streams commonly known as "DV" into a payload format for the Real-Time Transport Protocol (RTP). [STANDARDS TRACK] ietf-avt-dv-video-04 PROPOSED STANDARD PROPOSED STANDARD RFC3190 RTP Payload Format for 12-bit DAT Audio and 20- and 24-bit Linear Sampled Audio K. Kobayashi A. Ogawa S. Casner C. Bormann January 2002 ASCII 34977 17 real-time transport protocol digital audio tape This document specifies a packetization scheme for encapsulating 12-bit nonlinear, 20-bit linear, and 24-bit linear audio data streams using the Real-time Transport Protocol (RTP). This document also specifies the format of a Session Description Protocol (SDP) parameter to indicate when audio data is preemphasized before sampling. The parameter may be used with other audio payload formats, in particular L16 (16-bit linear). [STANDARDS TRACK] ietf-avt-dv-audio-04 PROPOSED STANDARD PROPOSED STANDARD RFC3191 Minimal GSTN address format in Internet Mail C. Allocchio October 2001 ASCII 24235 13 MIN-PSTN global switched telephone network email This memo describes a simple method of encoding Global Switched Telephone Network (GSTN) addresses (commonly called "telephone numbers") in the local-part of Internet email addresses, along with an extension mechanism to allow encoding of additional standard attributes needed for email gateways to GSTN-based services. [STANDARDS TRACK] ietf-fax-minaddr-v2-04 RFC2303 RFC2846 DRAFT STANDARD DRAFT STANDARD RFC3192 Minimal FAX address format in Internet Mail C. Allocchio October 2001 ASCII 18813 11 MINFAX-IM facsimile GSTN global switched telephone network This memo describes a simple method of encoding Global Switched Telephone Network (GSTN) addresses of facsimile devices in the local- part of Internet email addresses. [STANDARDS TRACK] ietf-fax-faxaddr-v2-04 RFC2304 RFC2846 DRAFT STANDARD DRAFT STANDARD RFC3193 Securing L2TP using IPsec B. Patel B. Aboba W. Dixon G. Zorn S. Booth November 2001 ASCII 63804 28 layer two tunneling protocol authentication This document discusses how L2TP (Layer Two Tunneling Protocol) may utilize IPsec to provide for tunnel authentication, privacy protection, integrity checking and replay protection. Both the voluntary and compulsory tunneling cases are discussed. [STANDARDS TRACK] ietf-l2tpext-security-08 PROPOSED STANDARD PROPOSED STANDARD RFC3194 The H-Density Ratio for Address Assignment Efficiency An Update on the H ratio A. Durand C. Huitema November 2001 ASCII 14539 7 IPng White Paper This document provides an update on the "H ratio" defined in RFC 1715. It defines a new ratio which the authors claim is easier to understand. This memo provides information for the Internet community. durand-huitema-h-density-ratio-01 RFC1715 INFORMATIONAL INFORMATIONAL RFC3195 Reliable Delivery for syslog D. New M. Rose November 2001 ASCII 60960 36 mappings encryption authentication beep blocks extensible exchange The BSD Syslog Protocol describes a number of service options related to propagating event messages. This memo describes two mappings of the syslog protocol to TCP connections, both useful for reliable delivery of event messages. [STANDARDS TRACK] ietf-syslog-reliable-12 PROPOSED STANDARD PROPOSED STANDARD RFC3196 Internet Printing Protocol/1.1: Implementor's Guide T. Hastings C. Manros P. Zehler C. Kugler H. Holst November 2001 ASCII 200720 96 IPP client object This document is one of a set of documents, which together describe all aspects of a new Internet Printing Protocol (IPP). This memo provides information for the Internet community. ietf-ipp-implementers-guide-v11-03 RFC2639 INFORMATIONAL INFORMATIONAL RFC3197 Applicability Statement for DNS MIB Extensions R. Austein November 2001 ASCII 8610 5 DNS-R-MIB Domain Name System Management Information Base This document explains why, after more than six years as proposed standards, the DNS Server and Resolver MIB extensions were never deployed, and recommends retiring these MIB extensions by moving them to Historical status. This memo provides information for the Internet community. ietf-dnsext-dnsmib-historical-00 INFORMATIONAL INFORMATIONAL RFC3198 Terminology for Policy-Based Management A. Westerinen J. Schnizlein J. Strassner M. Scherling B. Quinn S. Herzog A. Huynh M. Carlson J. Perry S. Waldbusser November 2001 ASCII 47806 21 glossary netowrk ISDs internet standard documents This document is a glossary of policy-related terms. It provides abbreviations, explanations, and recommendations for use of these terms. The intent is to improve the comprehensibility and consistency of writing that deals with network policy, particularly Internet Standards documents (ISDs). This memo provides information for the Internet community. ietf-policy-terminology-04 INFORMATIONAL INFORMATIONAL RFC3199 Request for Comments Summary RFC Numbers 3100-3199 S. Ginoza February 2003 ASCII 47287 24 INFORMATIONAL INFORMATIONAL RFC3200 RFC3201 Definitions of Managed Objects for Circuit to Interface Translation R. Steinberger O. Nicklass January 2002 ASCII 45583 23 mib This memo defines an extension 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 insertion of interesting Circuit Interfaces into the ifTable. This is important for circuits that must be used within other MIB modules which require an ifEntry. It allows for integrated monitoring of circuits as well as routing to circuits using unaltered, pre-existing MIB modules. [STANDARDS TRACK] ietf-frnetmib-frsi-04 PROPOSED STANDARD PROPOSED STANDARD RFC3202 Definitions of Managed Objects for Frame Relay Service Level Definitions R. Steinberger O. Nicklass January 2002 ASCII 130816 64 mib This memo defines an extension 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 Frame Relay Service Level Definitions. [STANDARDS TRACK] ietf-frnetmib-frmrelay-service-06 PROPOSED STANDARD PROPOSED STANDARD RFC3203 DHCP reconfigure extension Y. T'Joens C. Hublet P. De Schrijver December 2001 ASCII 11857 6 dynamic host configuration protocol forcerenew This document defines extensions to DHCP (Dynamic Host Configuration Protocol) to allow dynamic reconfiguration of a single host triggered by the DHCP server (e.g., a new IP address and/or local configuration parameters). [STANDARDS TRACK] ietf-dhc-pv4-reconfigure-06 PROPOSED STANDARD PROPOSED STANDARD RFC3204 MIME media types for ISUP and QSIG Objects E. Zimmerer J. Peterson A. Vemuri L. Ong F. Audet M. Watson M. Zonoun December 2001 ASCII 19712 10 multipart internet mail extensions This document describes MIME types for application/ISUP and application/QSIG objects for use in SIP applications, according to the rules defined in RFC 2048. These types can be used to identify ISUP and QSIG objects within a SIP message such as INVITE or INFO, as might be implemented when using SIP in an environment where part of the call involves interworking to the PSTN. [STANDARDS TRACK] ietf-sip-isup-mime-10 RFC3459 PROPOSED STANDARD PROPOSED STANDARD RFC3205 On the use of HTTP as a Substrate K. Moore February 2002 ASCII 34785 14 hypertext transfer protocol layering Recently there has been widespread interest in using Hypertext Transfer Protocol (HTTP) as a substrate for other applications-level protocols. This document recommends technical particulars of such use, including use of default ports, URL schemes, and HTTP security mechanisms. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. moore-using-http-01 BCP0056 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3206 The SYS and AUTH POP Response Codes R. Gellens February 2002 ASCII 9917 6 security authentication This memo proposes two response codes: SYS and AUTH, which enable clients to unambiguously determine an optimal response to an authentication failure. In addition, a new capability (AUTH-RESP-CODE) is defined. [STANDARDS TRACK] gellens-pop-err-01 PROPOSED STANDARD PROPOSED STANDARD RFC3207 SMTP Service Extension for Secure SMTP over Transport Layer Security P. Hoffman February 2002 ASCII 18679 9 simple mail transfer protocol ssl tls This document describes an extension to the SMTP (Simple Mail Transfer Protocol) service that allows an SMTP server and client to use TLS (Transport Layer Security) to provide private, authenticated communication over the Internet. This gives SMTP agents the ability to protect some or all of their communications from eavesdroppers and attackers. [STANDARDS TRACK] hoffman-rfc2487bis-06 RFC2487 PROPOSED STANDARD PROPOSED STANDARD RFC3208 PGM Reliable Transport Protocol Specification T. Speakman J. Crowcroft J. Gemmell D. Farinacci S. Lin D. Leshchiner M. Luby T. Montgomery L. Rizzo A. Tweedly N. Bhaskar R. Edmonstone R. Sumanasekera L. Vicisano December 2001 ASCII 244637 111 pragmatic general multicast Pragmatic General Multicast (PGM) is a reliable multicast transport protocol for applications that require ordered or unordered, duplicate- free, multicast data delivery from multiple sources to multiple receivers. PGM guarantees that a receiver in the group either receives all data packets from transmissions and repairs, or is able to detect unrecoverable data packet loss. PGM is specifically intended as a workable solution for multicast applications with basic reliability requirements. Its central design goal is simplicity of operation with due regard for scalability and network efficiency. This memo defines an Experimental Protocol for the Internet community. speakman-pgm-spec-07 EXPERIMENTAL EXPERIMENTAL RFC3209 RSVP-TE: Extensions to RSVP for LSP Tunnels D. Awduche L. Berger D. Gan T. Li V. Srinivasan G. Swallow December 2001 ASCII 132264 61 resource reservation protocol label switched paths This document describes the use of RSVP (Resource Reservation Protocol), including all the necessary extensions, to establish label-switched paths (LSPs) in MPLS (Multi-Protocol Label Switching). Since the flow along an LSP is completely identified by the label applied at the ingress node of the path, these paths may be treated as tunnels. A key application of LSP tunnels is traffic engineering with MPLS as specified in RFC 2702. [STANDARDS TRACK] ietf-mpls-rsvp-lsp-tunnel-09 RFC3936 PROPOSED STANDARD PROPOSED STANDARD RFC3210 Applicability Statement for Extensions to RSVP for LSP-Tunnels D. Awduche A. Hannan X. Xiao December 2001 ASCII 17691 8 resource reservation protocol label switched paths This memo discusses the applicability of "Extensions to RSVP (Resource ReSerVation Protocol) for LSP Tunnels". It highlights the protocol's principles of operation and describes the network context for which it was designed. Guidelines for deployment are offered and known protocol limitations are indicated. This document is intended to accompany the submission of "Extensions to RSVP for LSP Tunnels" onto the Internet standards track. This memo provides information for the Internet community. ietf-mpls-rsvp-tunnel-applicability-02 INFORMATIONAL INFORMATIONAL RFC3211 Password-based Encryption for CMS P. Gutmann December 2001 ASCII 30527 17 cryptographic message syntax S/MIME key wrap derivation passwordrecipientinfo PWRI This document provides a method of encrypting data using user-supplied passwords and, by extension, any form of variable-length keying material which is not necessarily an algorithm-specific fixed-format key. The Cryptographic Message Syntax data format does not currently contain any provisions for password-based data encryption. [STANDARDS TRACK] ietf-smime-password-06 RFC3369 RFC3370 PROPOSED STANDARD PROPOSED STANDARD RFC3212 Constraint-Based LSP Setup using LDP B. Jamoussi Editor L. Andersson R. Callon R. Dantu L. Wu P. Doolan T. Worster N. Feldman A. Fredette M. Girish E. Gray J. Heinanen T. Kilty A. Malis January 2002 ASCII 87591 42 label switching protocol distribution CR ORGANIZATION: Nortel Networks Utfors AB Juniper Networks Netrake Corporation Cisco Systems OTB Consulting Corp. Unspec. IBM Corp. ANF Consulting Atoga Systems Sandburst Song Networks Inc. Newbridge Networks Inc. Vivace Networks This document specifies mechanisms and TLVs (Type/Length/Value) for support of CR-LSPs (constraint-based routed Label Switched Path) using LDP (Label Distribution Protocol). [STANDARDS TRACK] ietf-mpls-cr-ldp-06 RFC3468 PROPOSED STANDARD PROPOSED STANDARD RFC3213 Applicability Statement for CR-LDP J. Ash M. Girish E. Gray B. Jamoussi G. Wright January 2002 ASCII 14489 7 constraint-based label distribution protocol This document discusses the applicability of Constraint-Based LSP Setup using LDP. It discusses possible network applications, extensions to Label Distribution Protocol (LDP) required to implement constraint-based routing, guidelines for deployment and known limitations of the protocol. This document is a prerequisite to advancing CR-LDP on the standards track. This memo provides information for the Internet community. ietf-mpls-crldp-applic-01 INFORMATIONAL INFORMATIONAL RFC3214 LSP Modification Using CR-LDP J. Ash Y. Lee P. Ashwood-Smith B. Jamoussi D. Fedyk D. Skalecki L. Li January 2002 ASCII 25453 11 label switching protocol constraint-based distribution This document presents an approach to modify the bandwidth and possibly other parameters of an established CR-LSP (Constraint-based Routed Label Switched Paths) using CR-LDP (Constraint-based Routed Label Distribution Protocol) without service interruption. [STANDARDS TRACK] ietf-mpls-crlsp-modify-03 PROPOSED STANDARD PROPOSED STANDARD RFC3215 LDP State Machine C. Boscher P. Cheval L. Wu E. Gray January 2002 ASCII 117278 78 label distribution protocol This document provides state machine tables for ATM (Asynchronous Transfer Mode) switch LSRs. In the current LDP specification, there is no state machine specified for processing LDP messages. We think that defining a common state machine is very important for interoperability between different LDP and CR-LDP implementations. This memo provides information for the Internet community. ietf-mpls-ldp-state-04 INFORMATIONAL INFORMATIONAL RFC3216 SMIng Objectives C. Elliott D. Harrington J. Jason J. Schoenwaelder F. Strauss W. Weiss December 2001 ASCII 58551 33 SNMP simple network management protocol COPS-PR common open policy service provisioning This document describes the objectives for a new data definition language, suitable for the modeling of network management constructs, that can be directly mapped into SNMP and COPS-PR protocol operations. This memo provides information for the Internet community. ietf-sming-reqs-06 INFORMATIONAL INFORMATIONAL RFC3217 Triple-DES and RC2 Key Wrapping R. Housley December 2001 ASCII 19855 9 algorithm data encryption standard This document specifies the algorithm for wrapping one Triple-DES key with another Triple-DES key and the algorithm for wrapping one RC2 key with another RC2 key. This memo provides information for the Internet community. ietf-smime-key-wrap-01 INFORMATIONAL INFORMATIONAL RFC3218 Preventing the Million Message Attack on Cryptographic Message Syntax E. Rescorla January 2002 ASCII 16047 7 cryptographic syntax This memo describes a strategy for resisting the Million Message Attack. This memo provides information for the Internet community. ietf-smime-pkcs1-01 INFORMATIONAL INFORMATIONAL RFC3219 Telephony Routing over IP (TRIP) J. Rosenberg H. Salama M. Squire January 2002 ASCII 184618 79 inter-administrative BGP border gateway protocol This document presents the Telephony Routing over IP (TRIP). TRIP is a policy driven inter-administrative domain protocol for advertising the reachability of telephony destinations between location servers, and for advertising attributes of the routes to those destinations. TRIP's operation is independent of any signaling protocol, hence TRIP can serve as the telephony routing protocol for any signaling protocol. [STANDARDS TRACK] ietf-iptel-trip-09 PROPOSED STANDARD PROPOSED STANDARD RFC3220 IP Mobility Support for IPv4 C. Perkins Editor January 2002 ASCII 238343 98 MOBILEIPSUPIP Internet Protocol 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. [STANDARDS TRACK] ietf-mobileip-rfc2002-bis-08 RFC2002 RFC3344 PROPOSED STANDARD PROPOSED STANDARD RFC3221 Commentary on Inter-Domain Routing in the Internet G. Huston December 2001 ASCII 66580 25 BGP border gateway protocol This document examines the various longer term trends visible within the characteristics of the Internet's BGP table and identifies a number of operational practices and protocol factors that contribute to these trends. The potential impacts of these practices and protocol properties on the scaling properties of the inter-domain routing space are examined. This memo provides information for the Internet community. iab-bgparch-01 INFORMATIONAL INFORMATIONAL RFC3222 Terminology for Forwarding Information Base (FIB) based Router Performance G. Trotter December 2001 ASCII 25483 15 internet protocol routing table benchmark This document describes the terms to be used in a methodology that determines the IP packet forwarding performance of IP routers as a function of the forwarding information base installed within a router. The forwarding performance of an IP router may be dependent upon or may be linked to the composition and size of the forwarding information base installed within a router. This memo provides information for the Internet community. ietf-bmwg-fib-term-04 INFORMATIONAL INFORMATIONAL RFC3223 RFC3224 Vendor Extensions for Service Location Protocol, Version 2 E. Guttman January 2002 ASCII 19618 10 SLP SVRLOC opaque This document specifies how the features of the Service Location Protocol, Version 2 allow for vendor extensibility safely, with no possibility of collisions. The specification introduces a new SLPv2 extension: The Vendor Opaque Extension. While proprietary protocol extensions are not encouraged by IETF standards, it is important that they not hinder interoperability of compliant implementations when they are undertaken. This document udpates RFC 2608, "The Service Location Protocol." [STANDARDS TRACK] RFC2608 PROPOSED STANDARD PROPOSED STANDARD RFC3225 Indicating Resolver Support of DNSSEC D. Conrad December 2001 ASCII 11548 6 domain name system security extensions In order to deploy DNSSEC (Domain Name System Security Extensions) operationally, DNSSEC aware servers should only perform automatic inclusion of DNSSEC RRs when there is an explicit indication that the resolver can understand those RRs. This document proposes the use of a bit in the EDNS0 header to provide that explicit indication and describes the necessary protocol changes to implement that notification. [STANDARDS TRACK] ietf-dnsext-dnssec-okbit-02 RFC4033 RFC4034 RFC4035 PROPOSED STANDARD PROPOSED STANDARD RFC3226 DNSSEC and IPv6 A6 aware server/resolver message size requirements O. Gudmundsson December 2001 ASCII 12078 6 domain name space security extensions dns endso This document mandates support for EDNS0 (Extension Mechanisms for DNS) in DNS entities claiming to support either DNS Security Extensions or A6 records. This requirement is necessary because these new features increase the size of DNS messages. If EDNS0 is not supported fall back to TCP will happen, having a detrimental impact on query latency and DNS server load. This document updates RFC 2535 and RFC 2874, by adding new requirements. [STANDARDS TRACK] ietf-dnsext-message-size-04 RFC2535 RFC2874 RFC4033 RFC4034 RFC4035 PROPOSED STANDARD PROPOSED STANDARD RFC3227 Guidelines for Evidence Collection and Archiving D. Brezinski T. Killalea February 2002 ASCII 18468 10 security incident A "security incident" as defined in the "Internet Security Glossary", RFC 2828, is a security-relevant system event in which the system's security policy is disobeyed or otherwise breached. The purpose of this document is to provide System Administrators with guidelines on the collection and archiving of evidence relevant to such a security incident. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP0055 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3228 IANA Considerations for IPv4 Internet Group Management Protocol (IGMP) B. Fenner February 2002 ASCII 6473 4 assigned numbers authority This memo requests that the IANA create a registry for fields in the IGMP (Internet Group Management Protocol) protocol header, and provides guidance for the IANA to use in assigning parameters for those fields. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-magma-igmp-iana-01 BCP0057 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3229 Delta encoding in HTTP J. Mogul B. Krishnamurthy F. Douglis A. Feldmann Y. Goland A. van Hoff D. Hellerstein January 2002 ASCII 111953 49 hyper text transfer protocol This document describes how delta encoding can be supported as a compatible extension to HTTP/1.1. [STANDARDS TRACK] mogul-http-delta-10 PROPOSED STANDARD PROPOSED STANDARD RFC3230 Instance Digests in HTTP J. Mogul A. Van Hoff January 2002 ASCII 26846 13 hyper text transfer protocol HTTP/1.1 defines a Content-MD5 header that allows a server to include a digest of the response body. However, this is specifically defined to cover the body of the actual message, not the contents of the full file (which might be quite different, if the response is a Content-Range, or uses a delta encoding). Also, the Content-MD5 is limited to one specific digest algorithm; other algorithms, such as SHA-1 (Secure Hash Standard), may be more appropriate in some circumstances. Finally, HTTP/1.1 provides no explicit mechanism by which a client may request a digest. This document proposes HTTP extensions that solve these problems. [STANDARDS TRACK] mogul-http-digest-05 PROPOSED STANDARD PROPOSED STANDARD RFC3231 Definitions of Managed Objects for Scheduling Management Operations D. Levi J. Schoenwaelder January 2002 ASCII 61308 29 mib information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a set of managed objects that are used to schedule management operations periodically or at specified dates and times. [STANDARDS TRACK] ietf-disman-schedule-mib-v2-04 RFC2591 PROPOSED STANDARD PROPOSED STANDARD RFC3232 Assigned Numbers: RFC 1700 is Replaced by an On-line Database J. Reynolds Editor January 2002 ASCII 3849 3 IANA internet assigned numbers authority parameters This memo obsoletes RFC 1700 (STD 2) "Assigned Numbers", which contained an October 1994 snapshot of assigned Internet protocol parameters. This memo provides information for the Internet community. RFC1700 INFORMATIONAL INFORMATIONAL RFC3233 Defining the IETF P. Hoffman S. Bradner February 2002 ASCII 6401 4 internet engineering task force This document gives a more concrete definition of "the IETF" as it understood today. Many RFCs refer to "the IETF". Many important IETF documents speak of the IETF as if it were an already-defined entity. However, no IETF document correctly defines what the IETF is. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. hoffman-what-is-ietf-05 BCP0058 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3234 Middleboxes: Taxonomy and Issues B. Carpenter S. Brim February 2002 ASCII 62329 27 internet protocol router data path host This document is intended as part of an IETF discussion about "middleboxes" - defined as any intermediary box performing functions apart from normal, standard functions of an IP router on the data path between a source host and destination host. This document establishes a catalogue or taxonomy of middleboxes, cites previous and current IETF work concerning middleboxes, and attempts to identify some preliminary conclusions. It does not, however, claim to be definitive. This memo provides information for the Internet community. carpenter-midtax-03 INFORMATIONAL INFORMATIONAL RFC3235 Network Address Translator (NAT)-Friendly Application Design Guidelines D. Senie January 2002 ASCII 29588 13 NAPT ALG firewall This document discusses those things that application designers might wish to consider when designing new protocols. While many common Internet applications will operate cleanly in the presence of Network Address Translators, others suffer from a variety of problems when crossing these devices. Guidelines are presented herein to help ensure new protocols and applications will, to the extent possible, be compatible with NAT (Network Address Translation). This memo provides information for the Internet community. ietf-nat-app-guide-07 INFORMATIONAL INFORMATIONAL RFC3236 The 'application/xhtml+xml' Media Type M. Baker P. Stark January 2002 ASCII 16750 8 mime multipurpose internet mail extensions This document defines the 'application/xhtml+xml' MIME media type for XHTML based markup languages; it is not intended to obsolete any previous IETF documents, in particular RFC 2854 which registers 'text/html'. This memo provides information for the Internet community. baker-xhtml-media-reg-02 INFORMATIONAL INFORMATIONAL RFC3237 Requirements for Reliable Server Pooling M. Tuexen Q. Xie R. Stewart M. Shore L. Ong J. Loughney M. Stillman January 2002 ASCII 16986 10 rserpool application This document defines a basic set of requirements for reliable server pooling. This memo provides information for the Internet community. ietf-rserpool-reqts-03 INFORMATIONAL INFORMATIONAL RFC3238 IAB Architectural and Policy Considerations for Open Pluggable Edge Services S. Floyd L. Daigle January 2002 ASCII 42336 17 OPES internet architecture board This document includes comments and recommendations by the IAB on some architectural and policy issues related to the chartering of Open Pluggable Edge Services (OPES) in the IETF. OPES are services that would be deployed at application-level intermediaries in the network, for example, at a web proxy cache between the origin server and the client. These intermediaries would transform or filter content, with the explicit consent of either the content provider or the end user. This memo provides information for the Internet community. iab-opes-01 INFORMATIONAL INFORMATIONAL RFC3239 Internet Printing Protocol (IPP): Requirements for Job, Printer, and Device Administrative Operations C. Kugler H. Lewis T. Hastings February 2002 ASCII 29532 15 object device This document specifies the requirements and uses cases for some optional administrative operations for use with the Internet Printing Protocol (IPP) version 1.0 and version 1.1. Some of these administrative operations operate on the IPP Job and Printer objects. The remaining operations operate on a new Device object that more closely models a single output device. This memo provides information for the Internet community. ietf-ipp-ops-admin-req-01 INFORMATIONAL INFORMATIONAL RFC3240 Digital Imaging and Communications in Medicine (DICOM) - Application/dicom MIME Sub-type Registration D. Clunie E. Cordonnier February 2002 ASCII 9102 6 multipurpose internet mail extensions This document describes the registration of the MIME sub-type application/dicom (Digital Imaging and Communications in Medicine). The baseline encoding is defined by the DICOM Standards Committee in "Digital Imaging and Communications in Medicine". This memo provides information for the Internet community. dicom-media-type-00 INFORMATIONAL INFORMATIONAL RFC3241 Robust Header Compression (ROHC) over PPP C. Bormann April 2002 ASCII 24424 12 point-to-point protocol datagram packets This document describes an option for negotiating the use of robust header compression (ROHC) on IP datagrams transmitted over the Point- to-Point Protocol (PPP). It defines extensions to the PPP Control Protocols for IPv4 and IPv6. [STANDARDS TRACK] ietf-rohc-over-ppp-04 RFC1332 PROPOSED STANDARD PROPOSED STANDARD RFC3242 RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP L-E. Jonsson G. Pelletier April 2002 ASCII 49007 21 internet protocol user datagram real-time application transport This document defines a ROHC (Robust Header Compression) profile for compression of IP/UDP/RTP (Internet Protocol/User Datagram Protocol/Real-Time Transport Protocol) packets, utilizing functionality provided by the lower layers to increase compression efficiency by completely eliminating the header for most packets during optimal operation. The profile is built as an extension to the ROHC RTP profile. It defines additional mechanisms needed in ROHC, states requirements on the assisting layer to guarantee transparency, and specifies general logic for compression and decompression making use of this header-free packet. [STANDARDS TRACK] ietf-rohc-rtp-lla-03 PROPOSED STANDARD PROPOSED STANDARD RFC3243 RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP Compression L-E. Jonsson April 2002 ASCII 12451 6 internet protocol user datagram real-time application transport applications LLA link-layer assisted This document contains requirements for the 0-byte IP/UDP/RTP (Internet Protocol/User Datagram Protocol/Real-Time Transport Protocol) header compression scheme to be developed by the Robust Header Compression (ROHC) Working Group. It also includes the basic assumptions for the typical link layers over which 0-byte compression may be implemented, and assumptions about its usage in general. ietf-rohc-rtp-0-byte-requirements-02 INFORMATIONAL INFORMATIONAL RFC3244 Microsoft Windows 2000 Kerberos Change Password and Set Password Protocols M. Swift J. Trostle J. Brezak February 2002 ASCII 13334 7 security message codes This memo specifies Microsoft's Windows 2000 Kerberos change password and set password protocols. The Windows 2000 Kerberos change password protocol interoperates with the original Kerberos change password protocol. Change password is a request reply protocol that includes a KRB_PRIV message that contains the new password for the user. This memo provides information for the Internet community. trostle-win2k-cat-kerberos-set-passwd-04 INFORMATIONAL INFORMATIONAL RFC3245 The History and Context of Telephone Number Mapping (ENUM) Operational Decisions: Informational Documents Contributed to ITU-T Study Group 2 (SG2) J. Klensin Editor IAB March 2002 ASCII 23758 10 IAB ARPA RFC 2916 assigned responsibility for a number of administrative and operational details of Telephone Number Mapping (ENUM) to the IAB. It also anticipated that ITU would take responsibility for determining the legitimacy and appropriateness of applicants for delegation of "country code"-level subdomains of the top-level ENUM domain. Recently, three memos have been prepared for the ITU-T Study Group 2 (SG2) to explain the background of, and reasoning for, the relevant decisions. The IAB has also supplied a set of procedural instructions to the RIPE NCC for implementation of their part of the model. The content of the three memos is provided in this document for the information of the IETF community. iab-itu-enum-notes-00 INFORMATIONAL INFORMATIONAL RFC3246 An Expedited Forwarding PHB (Per-Hop Behavior) B. Davie A. Charny J.C.R. Bennet K. Benson J.Y. Le Boudec W. Courtney S. Davari V. Firoiu D. Stiliadis March 2002 ASCII 33896 16 per-hop behavior expedited forwarding differentiated services delay jitter This document defines a PHB (per-hop behavior) called Expedited Forwarding (EF). The PHB is a basic building block in the Differentiated Services architecture. EF is intended to provide a building block for low delay, low jitter and low loss services by ensuring that the EF aggregate is served at a certain configured rate. This document obsoletes RFC 2598. [STANDARDS TRACK] ietf-diffserv-rfc2598bis-02 RFC2598 PROPOSED STANDARD PROPOSED STANDARD RFC3247 Supplemental Information for the New Definition of the EF PHB (Expedited Forwarding Per-Hop Behavior) A. Charny J. Bennet K. Benson J. Boudec A. Chiu W. Courtney S. Davari V. Firoiu C. Kalmanek K. Ramakrishnan March 2002 ASCII 53786 24 differentiated services fifo fair queuing delay jitter This document was written during the process of clarification of RFC2598 "An Expedited Forwarding PHB" that led to the publication of revised specification of EF "An Expedited Forwarding PHB". Its primary motivation is providing additional explanation to the revised EF definition and its properties. The document also provides additional implementation examples and gives some guidance for computation of the numerical parameters of the new definition for several well known schedulers and router architectures. This memo provides information for the Internet community. ietf-diffserv-ef-supplemental-01 INFORMATIONAL INFORMATIONAL RFC3248 A Delay Bound alternative revision of RFC 2598 G. Armitage B. Carpenter A. Casati J. Crowcroft J. Halpern B. Kumar J. Schnizlein March 2002 ASCII 21597 11 per hop behavior phb expedited forwarding ef db For historical interest, this document captures the EF Design Team's proposed solution, preferred by the original authors of RFC 2598 but not adopted by the working group in December 2000. The original definition of EF was based on comparison of forwarding on an unloaded network. This experimental Delay Bound (DB) PHB requires a bound on the delay of packets due to other traffic in the network. At the Pittsburgh IETF meeting in August 2000, the Differentiated Services working group faced serious questions regarding RFC 2598 - the group's standards track definition of the Expedited Forwarding (EF) Per Hop Behavior (PHB). An 'EF Design Team' volunteered to develop a re-expression of RFC 2598, bearing in mind the issues raised in the DiffServ group. At the San Diego IETF meeting in December 2000 the DiffServ working group decided to pursue an alternative re-expression of the EF PHB. This memo provides information for the Internet community. ietf-diffserv-efresolve-01 INFORMATIONAL INFORMATIONAL RFC3249 Implementers Guide for Facsimile Using Internet Mail V. Cancio M. Moldovan H. Tamura D. Wing September 2002 ASCII 40413 21 fax tiff tiff-fx ifax e-mail email esmtp dsn mdn This document is intended for the implementers of software that use email to send to facsimiles using RFC 2305 and 2532. This is an informational document and its guidelines do not supersede the referenced documents. This memo provides information for the Internet community. ietf-fax-implementers-guide-07 INFORMATIONAL INFORMATIONAL RFC3250 Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type Registration L. McIntyre G. Parsons J. Rafferty September 2002 ASCII 17876 7 FFIF TIFF Tag Image facsimile MIME multipurpose Internet mail extensions This document describes the registration of the MIME sub-type image/tiff-fx. The encodings are defined by File Format for Internet Fax and its extensions. [STANDARDS TRACK] ietf-fax-tiff-fx-reg-01 RFC3950 PROPOSED STANDARD PROPOSED STANDARD RFC3251 Electricity over IP B. Rajagopalan April 01 2002 ASCII 18994 9 Internet Protocol Mostly Pointless Lamp Switching (MPLampS) is an architecture for carrying electricity over IP (with an MPLS control plane). According to our marketing department, MPLampS has the potential to dramatically lower the price, ease the distribution and usage, and improve the manageability of delivering electricity. This document is motivated by such work as SONET/SDH over IP/MPLS (with apologies to the authors). Readers of the previous work have been observed scratching their heads and muttering, "What next?". This document answers that question. This memo provides information for the Internet community. bala-mplamps-04 INFORMATIONAL INFORMATIONAL RFC3252 Binary Lexical Octet Ad-hoc Transport H. Kennedy April 01 2002 ASCII 25962 16 bloat This document defines a reformulation of IP and two transport layer protocols (TCP and UDP) as XML applications. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC3253 Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning) G. Clemm J. Amsden T. Ellison C. Kaler J. Whitehead March 2002 ASCII 245514 118 hypertext transfer protocol clients label configuration management This document specifies a set of methods, headers, and resource types that define the WebDAV (Web Distributed Authoring and Versioning) versioning extensions to the HTTP/1.1 protocol. [STANDARDS TRACK] ietf-deltav-versioning-20 PROPOSED STANDARD PROPOSED STANDARD RFC3254 Definitions for talking about directories H. Alvestrand April 2002 ASCII 21541 11 domain name system lightweight access protocol When discussing systems for making information accessible through the Internet in standardized ways, it may be useful if the people who are discussing it have a common understanding of the terms they use. For example, a reference to this document would give one the power to agree that the DNS (Domain Name System) is a global lookup repository with perimeter integrity and loose, converging consistency. On the other hand, a LDAP (Lightweight Directory Access Protocol) directory server is a local, centralized repository with both lookup and search capability. This document discusses one group of such systems which is known under the term, "directories". This memo provides information for the Internet community. alvestrand-directory-defs-02 INFORMATIONAL INFORMATIONAL RFC3255 Extending Point-to-Point Protocol (PPP) over Synchronous Optical NETwork/Synchronous Digital Hierarchy (SONET/SDH) with virtual concatenation, high order and low order payloads N. Jones C. Murton April 2002 ASCII 14192 8 This document describes an extension to the mapping of Point-to-Point Protocol (PPP) into Synchronous Optical NETwork/Synchronous Digital Hierarchy (SONET/SDH) to include the use of SONET/SDH SPE/VC virtual concatenation and the use of both high order and low order payloads. [STANDARDS TRACK] ietf-pppext-posvcholo-06 PROPOSED STANDARD PROPOSED STANDARD RFC3256 The DOCSIS (Data-Over-Cable Service Interface Specifications) Device Class DHCP (Dynamic Host Configuration Protocol) Relay Agent Information Sub-option D. Jones R. Woundy April 2002 ASCII 8551 5 This document proposes a new sub-option to the DHCP (Dynamic Host Configuration Protocol) Relay Agent Information Option. [STANDARDS TRACK] ietf-dhc-agentoptions-device-class-04 PROPOSED STANDARD PROPOSED STANDARD RFC3257 Stream Control Transmission Protocol Applicability Statement L. Coene April 2002 ASCII 24198 13 sctp udp tcp rtp transport security transport nat multihoming This document describes the applicability of the Stream Control Transmission Protocol (SCTP). It also contrasts SCTP with the two dominant transport protocols, User Datagram Protocol (UDP) & Transmission Control Protocol (TCP), and gives some guidelines for when best to use SCTP and when not best to use SCTP. This memo provides information for the Internet community. ietf-sigtran-sctp-applicability-08 INFORMATIONAL INFORMATIONAL RFC3258 Distributing Authoritative Name Servers via Shared Unicast Addresses T. Hardie April 2002 ASCII 22195 11 dns network topology latency This memo describes a set of practices intended to enable an authoritative name server operator to provide access to a single named server in multiple locations. The primary motivation for the development and deployment of these practices is to increase the distribution of Domain Name System (DNS) servers to previously under- served areas of the network topology and to reduce the latency for DNS query responses in those areas. This memo provides information for the Internet community. ietf-dnsop-hardie-shared-root-server-07 INFORMATIONAL INFORMATIONAL RFC3259 A Message Bus for Local Coordination J. Ott C. Perkins D. Kutscher April 2002 ASCII 84125 39 mbus message ip multicast addressing transport syntax The local Message Bus (Mbus) is a light-weight message-oriented coordination protocol for group communication between application components. The Mbus provides automatic location of communication peers, subject based addressing, reliable message transfer and different types of communication schemes. The protocol is layered on top of IP multicast and is specified for IPv4 and IPv6. The IP multicast scope is limited to link-local multicast. This document specifies the Mbus protocol, i.e., message syntax, addressing and transport mechanisms. This memo provides information for the Internet community. ietf-mmusic-mbus-transport-06 INFORMATIONAL INFORMATIONAL RFC3260 New Terminology and Clarifications for Diffserv D. Grossman April 2002 ASCII 21900 10 DIFFSRV scalability IP internet protocol This memo captures Diffserv working group agreements concerning new and improved terminology, and provides minor technical clarifications. It is intended to update RFC 2474, RFC 2475 and RFC 2597. When RFCs 2474 and 2597 advance on the standards track, and RFC 2475 is updated, it is intended that the revisions in this memo will be incorporated, and that this memo will be obsoleted by the new RFCs. This memo provides information for the Internet community. ietf-diffserv-new-terms-08 RFC2474 RFC2475 RFC2597 INFORMATIONAL INFORMATIONAL RFC3261 SIP: Session Initiation Protocol J. Rosenberg H. Schulzrinne G. Camarillo A. Johnston J. Peterson R. Sparks M. Handley E. Schooler June 2002 ASCII 647976 269 SIP application-layer application layer multimedia multicast unicast This document describes Session Initiation Protocol (SIP), an application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants. These sessions include Internet telephone calls, multimedia distribution, and multimedia conferences. [STANDARDS TRACK] ietf-sip-rfc2543bis-09 RFC2543 RFC3265 RFC3853 PROPOSED STANDARD PROPOSED STANDARD RFC3262 Reliability of Provisional Responses in Session Initiation Protocol (SIP) J. Rosenberg H. Schulzrinne June 2002 ASCII 29643 14 SIP application-layer application layer multimedia multicast unicast This document specifies an extension to the Session Initiation Protocol (SIP) providing reliable provisional response messages. This extension uses the option tag 100rel and defines the Provisional Response ACKnowledgement (PRACK) method. [STANDARDS TRACK] ietf-sip-100rel-06 RFC2543 PROPOSED STANDARD PROPOSED STANDARD RFC3263 Session Initiation Protocol (SIP): Locating SIP Servers J. Rosenberg H. Schulzrinne June 2002 ASCII 42310 17 SIP application-layer application layer multimedia multicast unicast The Session Initiation Protocol (SIP) uses DNS procedures to allow a client to resolve a SIP Uniform Resource Identifier (URI) into the IP address, port, and transport protocol of the next hop to contact. It also uses DNS to allow a server to send a response to a backup client if the primary client has failed. This document describes those DNS procedures in detail. [STANDARDS TRACK] ietf-sip-srv-06 RFC2543 PROPOSED STANDARD PROPOSED STANDARD RFC3264 An Offer/Answer Model with Session Description Protocol (SDP) J. Rosenberg H. Schulzrinne June 2002 ASCII 60854 25 SIP application-layer application layer multimedia multicast unicast This document defines a mechanism by which two entities can make use of the Session Description Protocol (SDP) to arrive at a common view of a multimedia session between them. In the model, one participant offers the other a description of the desired session from their perspective, and the other participant answers with the desired session from their perspective. This offer/answer model is most useful in unicast sessions where information from both participants is needed for the complete view of the session. The offer/answer model is used by protocols like the Session Initiation Protocol (SIP). [STANDARDS TRACK] ietf-mmusic-sdp-offer-answer-02 RFC2543 PROPOSED STANDARD PROPOSED STANDARD RFC3265 Session Initiation Protocol (SIP)-Specific Event Notification A. B. Roach June 2002 ASCII 89005 38 SIP application-layer application layer multimedia multicast unicast This document describes an extension to the Session Initiation Protocol (SIP). The purpose of this extension is to provide an extensible framework by which SIP nodes can request notification from remote nodes indicating that certain events have occurred. [STANDARDS TRACK] ietf-sip-events-05 RFC2543 RFC3261 PROPOSED STANDARD PROPOSED STANDARD RFC3266 Support for IPv6 in Session Description Protocol (SDP) S. Olson G. Camarillo A. B. Roach June 2002 ASCII 8693 5 internet addresses syntax This document describes the use of Internet Protocol Version 6 (IPv6) addresses in conjunction with the Session Description Protocol (SDP). Specifically, this document clarifies existing text in SDP with regards to the syntax of IPv6 addresses. [STANDARDS TRACK] ietf-mmusic-sdp-ipv6-03 RFC2327 PROPOSED STANDARD PROPOSED STANDARD RFC3267 Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs J. Sjoberg M. Westerlund A. Lakaniemi Q. Xie June 2002 ASCII 110652 49 interoperate applications This document specifies a real-time transport protocol (RTP) payload format to be used for Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) encoded speech signals. The payload format is designed to be able to interoperate with existing AMR and AMR-WB transport formats on non-IP networks. In addition, a file format is specified for transport of AMR and AMR-WB speech data in storage mode applications such as email. Two separate MIME type registrations are included, one for AMR and one for AMR-WB, specifying use of both the RTP payload format and the storage format. [STANDARDS TRACK] ietf-avt-rtp-amr-13 PROPOSED STANDARD PROPOSED STANDARD RFC3268 Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS) P. Chown June 2002 ASCII 13530 7 idea international data algorithm symmetric This document proposes several new ciphersuites. At present, the symmetric ciphers supported by Transport Layer Security (TLS) are RC2, RC4, International Data Encryption Algorithm (IDEA), Data Encryption Standard (DES), and triple DES. The protocol would be enhanced by the addition of Advanced Encryption Standard (AES) ciphersuites. [STANDARDS TRACK] ietf-tls-ciphersuite-06 PROPOSED STANDARD PROPOSED STANDARD RFC3269 Author Guidelines for Reliable Multicast Transport (RMT) Building Blocks and Protocol Instantiation documents R. Kermode L. Vicisano April 2002 ASCII 25258 12 definitions operation This document provides general guidelines to assist the authors of Reliable Multicast Transport (RMT) building block and protocol instantiation definitions. The purpose of these guidelines is to ensure that any building block and protocol instantiation definitions produced contain sufficient information to fully explain their operation and use. In addition these guidelines provide directions to specify modular and clearly defined RMT building blocks and protocol instantiations that can be refined and augmented to safely create new protocols for use in new scenarios for which any existing protocols were not designed. This memo provides information for the Internet community. ietf-rmt-author-guidelines-03 INFORMATIONAL INFORMATIONAL RFC3270 Multi-Protocol Label Switching (MPLS) Support of Differentiated Services F. Le Faucheur L. Wu B. Davie S. Davari P. Vaananen R. Krishnan P. Cheval J. Heinanen May 2002 ASCII 137960 64 diff-serv ba behaviour aggregate lsp label switched paths This document defines a flexible solution for support of Differentiated Services (Diff-Serv) over Multi-Protocol Label Switching (MPLS) networks. [STANDARDS TRACK] ietf-mpls-diff-ext-09 PROPOSED STANDARD PROPOSED STANDARD RFC3271 The Internet is for Everyone V. Cerf April 2002 ASCII 12345 6 isoc internet society policy issues social impact economic impact international policy use and abuse of the internet This document expresses the Internet Society's ideology that the Internet really is for everyone. However, it will only be such if we make it so. This memo provides information for the Internet community. isoc-internet-for-everyone-01 INFORMATIONAL INFORMATIONAL RFC3272 Overview and Principles of Internet Traffic Engineering D. Awduche A. Chiu A. Elwalid I. Widjaja X. Xiao May 2002 ASCII 190384 71 te ip networks This memo describes the principles of Traffic Engineering (TE) in the Internet. The document is intended to promote better understanding of the issues surrounding traffic engineering in IP networks, and to provide a common basis for the development of traffic engineering capabilities for the Internet. The principles, architectures, and methodologies for performance evaluation and performance optimization of operational IP networks are discussed throughout this document. This memo provides information for the Internet community. ietf-tewg-principles-02 INFORMATIONAL INFORMATIONAL RFC3273 Remote Network Monitoring Management Information Base for High Capacity Networks S. Waldbusser July 2002 ASCII 150924 77 rmon mib high speed networks 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 (RMON) devices for use on high speed networks. This document contains a MIB Module that defines these new objects and also contains definitions of some updated objects from the RMON-MIB in RFC 2819 and the RMON2-MIB in RFC 2021. [PROPOSED STANDARD] ietf-rmonmib-hcrmon-10 PROPOSED STANDARD PROPOSED STANDARD RFC3274 Compressed Data Content Type for Cryptographic Message Syntax (CMS) P. Gutmann June 2002 ASCII 11276 6 content info type This document defines a format for using compressed data as a Cryptographic Message Syntax (CMS) content type. Compressing data before transmission provides a number of advantages, including the elimination of data redundancy which could help an attacker, speeding up processing by reducing the amount of data to be processed by later steps (such as signing or encryption), and reducing overall message size. Although there have been proposals for adding compression at other levels (for example at the MIME or SSL level), these don't address the problem of compression of CMS content unless the compression is supplied by an external means (for example by intermixing MIME and CMS). [STANDARDS TRACK] ietf-smime-compression-07 PROPOSED STANDARD PROPOSED STANDARD RFC3275 (Extensible Markup Language) XML-Signature Syntax and Processing D. Eastlake 3rd J. Reagle D. Solo March 2002 ASCII 164198 73 extensible markup language This document specifies XML (Extensible Markup Language) digital signature processing rules and syntax. [STANDARDS TRACK] ietf-xmldsig-core-2-03 RFC3075 DRAFT STANDARD DRAFT STANDARD RFC3276 Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) Lines Processing B. Ray R. Abbi May 2002 ASCII 122991 66 mib interfaces This document defines a portion of the Management Information Base (MIB) module for use with network management protocols in the Internet community. In particular, it describes objects used for managing High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces. [STANDARDS TRACK] ietf-adslmib-hdsl2-12 PROPOSED STANDARD PROPOSED STANDARD RFC3277 Intermediate System to Intermediate System (IS-IS) Transient Blackhole Avoidance D. McPherson April 2002 ASCII 13077 6 router This document describes a simple, interoperable mechanism that can be employed in Intermediate System to Intermediate System (IS-IS) networks in order to decrease the data loss associated with deterministic blackholing of packets during transient network conditions. The mechanism proposed here requires no IS-IS protocol changes and is completely interoperable with the existing IS-IS specification. This memo provides information for the Internet community. ietf-isis-transient-02 INFORMATIONAL INFORMATIONAL RFC3278 Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS) S. Blake-Wilson D. Brown P. Lambert April 2002 ASCII 33779 16 public key digital signatures authentication This document describes how to use Elliptic Curve Cryptography (ECC) public-key algorithms in the Cryptographic Message Syntax (CMS). The ECC algorithms support the creation of digital signatures and the exchange of keys to encrypt or authenticate content. The definition of the algorithm processing is based on the ANSI X9.62 standard, developed by the ANSI X9F1 working group, the IEEE 1363 standard, and the SEC 1 standard. This memo provides information for the Internet community. ietf-smime-ecc-06 INFORMATIONAL INFORMATIONAL RFC3279 Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile L. Bassham W. Polk R. Housley April 2002 ASCII 53833 27 ASN.1 This document specifies algorithm identifiers and ASN.1 encoding formats for digital signatures and subject public keys used in the Internet X.509 Public Key Infrastructure (PKI). Digital signatures are used to sign certificates and certificate revocation list (CRLs). Certificates include the public key of the named subject. [STANDARDS TRACK] ietf-pkix-ipki-pkalgs-05 PROPOSED STANDARD PROPOSED STANDARD RFC3280 Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile R. Housley W. Polk W. Ford D. Solo April 2002 ASCII 295556 129 This memo profiles the X.509 v3 certificate and X.509 v2 Certificate Revocation List (CRL) for use in the Internet. [STANDARDS TRACK] ietf-pkix-new-part1-12 RFC2459 PROPOSED STANDARD PROPOSED STANDARD RFC3281 An Internet Attribute Certificate Profile for Authorization S. Farrell R. Housley April 2002 ASCII 90580 40 electronic mail email ipsec www security This specification defines a profile for the use of X.509 Attribute Certificates in Internet Protocols. Attribute certificates may be used in a wide range of applications and environments covering a broad spectrum of interoperability goals and a broader spectrum of operational and assurance requirements. The goal of this document is to establish a common baseline for generic applications requiring broad interoperability as well as limited special purpose requirements. The profile places emphasis on attribute certificate support for Internet electronic mail, IPSec, and WWW security applications. [STANDARDS TRACK] ietf-pkix-ac509prof-09 PROPOSED STANDARD PROPOSED STANDARD RFC3282 Content Language Headers H. Alvestrand May 2002 ASCII 14022 8 This document defines a "Content-language:" header, for use in cases where one desires to indicate the language of something that has RFC 822-like headers, like MIME body parts or Web documents, and an "Accept-Language:" header for use in cases where one wishes to indicate one's preferences with regard to language. [STANDARDS TRACK] alvestrand-content-language-03 RFC1766 DRAFT STANDARD DRAFT STANDARD RFC3283 Guide to Internet Calendaring B. Mahoney G. Babics A. Taler June 2002 ASCII 31768 16 scheduling systems cap calendar access protocool itip imip This document describes the various Internet calendaring and scheduling standards and works in progress, and the relationships between them. Its intent is to provide a context for these documents, assist in their understanding, and potentially aid in the design of standards-based calendaring and scheduling systems. The standards addressed are RFC 2445 (iCalendar), RFC 2446 (iTIP), and RFC 2447 (iMIP). The work in progress addressed is "Calendar Access Protocol" (CAP). This document also describes issues and problems that are not solved by these protocols, and that could be targets for future work. This memo provides information for the Internet community. ietf-calsch-inetcal-guide-02 INFORMATIONAL INFORMATIONAL RFC3284 The VCDIFF Generic Differencing and Compression Data Format D. Korn J. MacDonald J. Mogul K. Vo June 2002 ASCII 64035 29 transport portable at&t encoding This memo describes VCDIFF, a general, efficient and portable data format suitable for encoding compressed and/or differencing data so that they can be easily transported among computers. [STANDARDS TRACK] korn-vcdiff-06 PROPOSED STANDARD PROPOSED STANDARD RFC3285 Using Microsoft Word to create Internet Drafts and RFCs M. Gahrns T. Hain May 2002 ASCII 34556 19 This document describes the steps to configure the Microsoft Word application to produce documents in Internet Draft and RFC format. This memo provides information for the Internet community. hain-msword-template-04 INFORMATIONAL INFORMATIONAL RFC3286 An Introduction to the Stream Control Transmission Protocol (SCTP) L. Ong J. Yoakum May 2002 ASCII 22644 10 transport layer telephony signaling This document provides a high level introduction to the capabilities supported by the Stream Control Transmission Protocol (SCTP). It is intended as a guide for potential users of SCTP as a general purpose transport protocol. This memo provides information for the Internet community. ong-sigtran-sctpover-01 INFORMATIONAL INFORMATIONAL RFC3287 Remote Monitoring MIB Extensions for Differentiated Services A. Bierman July 2002 ASCII 249622 120 rmon management information base diffserv 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 monitoring Differentiated Services (DS) Codepoint usage in packets which contain a DS field, utilizing the monitoring framework defined in the RMON-2 (Remote Network Monitoring Management Version 2) MIB. [STANDARDS TRACK] ietf-rmonmib-dsmon-mib-09 PROPOSED STANDARD PROPOSED STANDARD RFC3288 Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP) E. O'Tuathail M. Rose June 2002 ASCII 27434 20 binding markup language xml This memo specifies a Simple Object Access Protocol (SOAP) binding to the Blocks Extensible Exchange Protocol core (BEEP). A SOAP binding describes how SOAP messages are transmitted in the network. [STANDARDS TRACK] etal-beep-soap-06 PROPOSED STANDARD PROPOSED STANDARD RFC3289 Management Information Base for the Differentiated Services Architecture F. Baker K. Chan A. Smith May 2002 ASCII 239041 116 mib diffserv router architecture This memo describes an SMIv2 (Structure of Management Information version 2) MIB for a device implementing the Differentiated Services Architecture. It may be used both for monitoring and configuration of a router or switch capable of Differentiated Services functionality. [STANDARDS TRACK] ietf-diffserv-mib-16 PROPOSED STANDARD PROPOSED STANDARD RFC3290 An Informal Management Model for Diffserv Routers Y. Bernet S. Blake D. Grossman A. Smith May 2002 ASCII 129443 56 differentiated services This document proposes an informal management model of Differentiated Services (Diffserv) routers for use in their management and configuration. This model defines functional datapath elements (e.g., classifiers, meters, actions, marking, absolute dropping, counting, multiplexing), algorithmic droppers, queues and schedulers. It describes possible configuration parameters for these elements and how they might be interconnected to realize the range of traffic conditioning and per-hop behavior (PHB) functionalities described in the Diffserv Architecture. This memo provides information for the Internet community. ietf-diffserv-model-06 INFORMATIONAL INFORMATIONAL RFC3291 Textual Conventions for Internet Network Addresses M. Daniele B. Haberman S. Routhier J. Schoenwaelder May 2002 ASCII 43564 20 tc mib layer management information base This MIB module defines textual conventions to represent commonly used Internet network layer addressing information. The intent is that these textual conventions (TCs) will be imported and used in MIB modules that would otherwise define their own representations. [STANDARDS TRACK] ietf-ops-rfc2851-update-06 RFC2851 RFC4001 PROPOSED STANDARD PROPOSED STANDARD RFC3292 General Switch Management Protocol (GSMP) V3 A. Doria F. Hellstrand K. Sundell T. Worster June 2002 ASCII 318983 137 switch label unicast multicast qos quality of service This document describes the General Switch Management Protocol Version 3 (GSMPv3). The GSMPv3 is an asymmetric protocol that allows one or more external switch controllers to establish and maintain the state of a label switch such as, an ATM, frame relay or MPLS switch. The GSMPv3 allows control of both unicast and multicast switch connection state as well as control of switch system resources and QoS features. [STANDARDS TRACK] ietf-gsmp-11 PROPOSED STANDARD PROPOSED STANDARD RFC3293 General Switch Management Protocol (GSMP) Packet Encapsulations for Asynchronous Transfer Mode (ATM), Ethernet and Transmission Control Protocol (TCP) T. Worster A. Doria J. Buerkle June 2002 ASCII 18206 9 This memo specifies the encapsulation of GSMP (General Switch Management Protocol) packets in ATM (Asynchronous Transfer Mode), Ethernet and TCP (Transmission Control Protocol). [STANDARDS TRACK] ietf-gsmp-encaps-05 PROPOSED STANDARD PROPOSED STANDARD RFC3294 General Switch Management Protocol (GSMP) Applicability A. Doria K. Sundell June 2002 ASCII 18294 9 internet This memo provides an overview of the GSMP (General Switch Management Protocol) and includes information relating to its deployment in a IP network in an MPLS environment. It does not discuss deployment in an ATM (Asynchronous Transfer Mode) network or in a raw ethernet configuration. This memo provides information for the Internet community. ietf-gsmp-applicability-02 INFORMATIONAL INFORMATIONAL RFC3295 Definitions of Managed Objects for the General Switch Management Protocol (GSMP) H. Sjostrand J. Buerkle B. Srinivasan June 2002 ASCII 95516 47 mib management information base controller gsmp-mib This memo defines a portion of the Management Information Base (MIB) for the use with the network management protocols in the Internet community. In particular, it describes managed objects for the General Switch Management Protocol (GSMP). [STANDARDS TRACK] ietf-gsmp-mib-07 PROPOSED STANDARD PROPOSED STANDARD RFC3296 Named Subordinate References in Lightweight Directory Access Protocol (LDAP) Directories K. Zeilenga July 2002 ASCII 27389 14 schema elements description formats This document details schema and protocol elements for representing and managing named subordinate references in Lightweight Directory Access Protocol (LDAP) Directories. [STANDARDS TRACK] zeilenga-ldap-namedref-05 PROPOSED STANDARD PROPOSED STANDARD RFC3297 Content Negotiation for Messaging Services based on Email G. Klyne R. Iwazaki D. Crocker July 2002 ASCII 97094 46 facsimile This memo describes a content negotiation mechanism for facsimile, voice and other messaging services that use Internet email. [STANDARDS TRACK] ietf-fax-content-negotiation-05 PROPOSED STANDARD PROPOSED STANDARD RFC3298 Service in the Public Switched Telephone Network/Intelligent Network (PSTN/IN) Requesting InTernet Service (SPIRITS) Protocol Requirements I. Faynberg J. Gato H. Lu L. Slutsman August 2002 ASCII 36560 17 support This document describes the SPIRITS protocol requirements, based on the architecture presented in RFC 3136. (SPIRITS stands for "Service in the PSTN/IN Requesting InTernet Service".) The purpose of the protocol is to support services that originate in the Public Switched Telephone Network (PSTN) and necessitate the interactions between the PSTN and the Internet. Similarly, such services are called SPIRITS services. (Internet Call Waiting, Internet Caller-ID Delivery, and Internet Call Forwarding are examples of SPIRIT services, but the protocol is to define the building blocks from which many other services can be built.) On the PSTN side, the SPIRITS services are initiated from the Intelligent Network (IN) entities; the earlier IETF work on the PSTN/Internet Interworking (PINT) resulted in the protocol (RFC 2848) in support of the services initiated the other way around--from the Internet to PSTN. To this end, this document lists general requirements for the SPIRITS protocol as well as those pertinent to IN, Wireless IN, and PINT building blocks. The document also presents the SPIRITS WG consensus on the choice of the SPIRITS signaling protocol. This memo provides information for the Internet community. ietf-spirits-reqs-04 INFORMATIONAL INFORMATIONAL RFC3299 Request for Comments Summary RFC Numbers 3200-3299 S. Ginoza December 2003 ASCII 63813 30 INFORMATIONAL INFORMATIONAL RFC3300 Internet Official Protocol Standards J. Reynolds R. Braden S. Ginoza A. De La Cruz November 2002 ASCII 127805 49 RFC3000 RFC3600 STANDARD STANDARD RFC3301 Layer Two Tunnelling Protocol (L2TP): ATM access network extensions Y. T'Joens P. Crivellari B. Sales June 2002 ASCII 42756 19 ietf-l2tpext-atmext-04 PROPOSED STANDARD PROPOSED STANDARD RFC3302 Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration G. Parsons J. Rafferty September 2002 ASCII 15183 8 TIFF Multipurpose Internet Mail extensions ietf-fax-tiff-regbis-05 moved to draft standard 2/7/05; moved when we pub'd 3949 and 3950. RFC2302 DRAFT STANDARD PROPOSED STANDARD RFC3303 Middlebox communication architecture and framework P. Srisuresh J. Kuthan J. Rosenberg A. Molitor A. Rayhan August 2002 ASCII 91209 34 midcom ietf-midcom-framework-07 INFORMATIONAL INFORMATIONAL RFC3304 Middlebox Communications (midcom) Protocol Requirements R. P. Swale P. A. Mart P. Sijben S. Brim M. Shore August 2002 ASCII 16187 9 nat network address protocol firewall middleboxes ietf-midcom-requirements-05 INFORMATIONAL INFORMATIONAL RFC3305 Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations M. Mealling Editor R. Denenberg Editor August 2002 ASCII 21793 11 internet engineering task force mealling-uri-ig-02 INFORMATIONAL INFORMATIONAL RFC3306 Unicast-Prefix-based IPv6 Multicast Addresses B. Haberman D. Thaler August 2002 ASCII 12713 7 internet protocol ietf-ipngwg-uni-based-mcast-03 RFC3956 PROPOSED STANDARD PROPOSED STANDARD RFC3307 Allocation Guidelines for IPv6 Multicast Addresses B. Haberman August 2002 ASCII 15742 8 internet protocol ietf-malloc-ipv6-guide-04 PROPOSED STANDARD PROPOSED STANDARD RFC3308 Layer Two Tunneling Protocol (L2TP) Differentiated Services Extension P. Calhoun W. Luo D. McPherson K. Peirce November 2002 ASCII 21536 10 per hop behavior phb diffserv ietf-l2tpext-ds-05 PROPOSED STANDARD PROPOSED STANDARD RFC3309 Stream Control Transmission Protocol (SCTP) Checksum Change J. Stone R. Stewart D. Otis September 2002 ASCII 34670 17 adler-32 checksum error detection ietf-tsvwg-sctpcsum-07 RFC2960 PROPOSED STANDARD PROPOSED STANDARD RFC3310 Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) A. Niemi J. Arkko V. Torvinen September 2002 ASCII 36985 18 one-time password generation mechanism umts universal mobile telecommunications system ietf-sip-digest-aka-03 INFORMATIONAL INFORMATIONAL RFC3311 The Session Initiation Protocol (SIP) UPDATE Method J. Rosenberg October 2002 ASCII 28125 13 parameters media streams ietf-sip-update-02 PROPOSED STANDARD PROPOSED STANDARD RFC3312 Integration of Resource Management and Session Initiation Protocol (SIP) G. Camarillo Editor W. Marshall Editor J. Rosenberg October 2002 ASCII 65757 30 PS 655218 PDF 130391 qos quality of service precondition ietf-sip-manyfolks-resource-07 RFC4032 PROPOSED STANDARD PROPOSED STANDARD RFC3313 Private Session Initiation Protocol (SIP) Extensions for Media Authorization W. Marshall Editor January 2003 ASCII 36866 16 qos quality of service sip-call-auth-06 INFORMATIONAL INFORMATIONAL RFC3314 Recommendations for IPv6 in Third Generation Partnership Project (3GPP) Standards M. Wasserman Editor September 2002 ASCII 48168 23 internet protocol ietf-ipv6-3gpp-recommend-02 INFORMATIONAL INFORMATIONAL RFC3315 Dynamic Host Configuration Protocol for IPv6 (DHCPv6) R. Droms Editor J. Bound B. Volz T. Lemon C. Perkins M. Carney July 2003 ASCII 231402 101 internet protocol parameters addresses ietf-dhc-dhcpv6-28 PROPOSED STANDARD PROPOSED STANDARD RFC3316 Internet Protocol Version 6 (IPv6) for Some Second and Third Generation Cellular Hosts J. Arkko G. Kuijpers H. Soliman J. Loughney J. Wiljakka April 2003 ASCII 48741 22 links bandwidth ietf-ipv6-cellular-host-03 INFORMATIONAL INFORMATIONAL RFC3317 Differentiated Services Quality of Service Policy Information Base K. Chan R. Sahita S. Hahn K. McCloghrie March 2003 ASCII 188553 96 pib differentiated services architecture ietf-diffserv-pib-08 INFORMATIONAL INFORMATIONAL RFC3318 Framework Policy Information Base R. Sahita Editor S. Hahn K. Chan K. McCloghrie March 2003 ASCII 144530 70 ietf-rap-frameworkpib-09 INFORMATIONAL INFORMATIONAL RFC3319 Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers H. Schulzrinne B. Volz July 2003 ASCII 14444 7 outbound proxy servers ietf-sip-dhcpv6-01 PROPOSED STANDARD PROPOSED STANDARD RFC3320 Signaling Compression (SigComp) R. Price C. Bormann J. Christoffersson H. Hannu Z. Liu J. Rosenberg January 2003 ASCII 137035 62 sip session initiation protocol udvm universal decompressor virtual machine ietf-rohc-sigcomp-07 PROPOSED STANDARD PROPOSED STANDARD RFC3321 Signaling Compression (SigComp) - Extended Operations H. Hannu J. Christoffersson S. Forsgren K.-C. Leung Z. Liu R. Price January 2003 ASCII 39433 19 sip session initiation protocol udvm universal decompressor virtual machine ietf-rohc-sigcomp-extended-04 PROPOSED STANDARD PROPOSED STANDARD RFC3322 Signaling Compression (SigComp) Requirements & Assumptions H. Hannu January 2003 ASCII 27533 13 sip session initiation protocol wireless cellular sdp session description protocol ietf-rohc-signaling-req-assump-06 INFORMATIONAL INFORMATIONAL RFC3323 A Privacy Mechanism for the Session Initiation Protocol (SIP) J. Peterson November 2002 ASCII 54116 22 privacy service ietf-sip-privacy-general-01 PROPOSED STANDARD PROPOSED STANDARD RFC3324 Short Term Requirements for Network Asserted Identity M. Watson November 2002 ASCII 21964 11 session initiation protocol sip ua user agent ietf-sipping-nai-reqs-02 INFORMATIONAL INFORMATIONAL RFC3325 Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks C. Jennings J. Peterson M. Watson November 2002 ASCII 36170 18 trust domain ietf-sip-asserted-identity-01 INFORMATIONAL INFORMATIONAL RFC3326 The Reason Header Field for the Session Initiation Protocol (SIP) H. Schulzrinne D. Oran G. Camarillo December 2002 ASCII 15695 8 heterogeneous error response forking problem herfp The REGISTER function is used in a Session Initiation Protocol (SIP) system primarily to associate a temporary contact address with an address-of-record. This contact is generally in the form of a Uniform Resource Identifier (URI), such as Contact: <sip:alice@pc33.atlanta.com> and is generally dynamic and associated with the IP address or hostname of the SIP User Agent (UA). The problem is that network topology may have one or more SIP proxies between the UA and the registrar, such that any request traveling from the user's home network to the registered UA must traverse these proxies. The REGISTER method does not give us a mechanism to discover and record this sequence of proxies in the registrar for future use. This document defines an extension header field, "Path" which provides such a mechanism. [STANDARDS TRACK] ietf-sip-reason-01 PROPOSED STANDARD PROPOSED STANDARD RFC3327 Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts D. Willis B. Hoeneisen December 2002 ASCII 36493 17 3gpp register contact path registrar user agent ua willis-sip-path-08 PROPOSED STANDARD PROPOSED STANDARD RFC3328 RFC3329 Security Mechanism Agreement for the Session Initiation Protocol (SIP) J. Arkko V. Torvinen G. Camarillo A. Niemi T. Haukka January 2003 ASCII 51503 24 ua user agent ietf-sip-sec-agree-05 PROPOSED STANDARD PROPOSED STANDARD RFC3330 Special-Use IPv4 Addresses IANA September 2002 ASCII 16200 7 internet protocol space assignments iana-special-ipv4-05 INFORMATIONAL INFORMATIONAL RFC3331 Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation Layer K. Morneault R. Dantu G. Sidebottom B. Bidulock J. Heitz September 2002 ASCII 210807 94 sctp stream control transmission protocol sg signaling gateway media gateway controller mgc ietf-sigtran-m2ua-15 PROPOSED STANDARD PROPOSED STANDARD RFC3332 Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA) G. Sidebottom Editor K. Morneault Editor J. Pastor-Balbas Editor September 2002 ASCII 265055 120 isup sccp sctp stream control tranmission protocol mgc media gateway protocol st signalling gateway ietf-sigtran-m3ua-12 PROPOSED STANDARD PROPOSED STANDARD RFC3334 Policy-Based Accounting T. Zseby S. Zander C. Carle October 2002 ASCII 103014 44 measurement metering meter configuration qos auditing aaa aaa architecture inter-domain accounting irtf-aaaarch-pol-acct-05 EXPERIMENTAL EXPERIMENTAL RFC3335 MIME-based Secure Peer-to-Peer Business Data Interchange over the Internet T. Harding R. Drummond C. Shih September 2002 ASCII 59687 29 multipurpose internet mail extensions edi ietf-ediinet-asl-17 PROPOSED STANDARD PROPOSED STANDARD RFC3336 PPP Over Asynchronous Transfer Mode Adaptation Layer 2 (AAL2) B. Thompson T. Koren B. Buffam December 2002 ASCII 33631 16 point-to-point protocol atm aal2 datagram packets ietf-pppext-ppp-over-aal2-03 PROPOSED STANDARD PROPOSED STANDARD RFC3337 Class Extensions for PPP over Asynchronous Transfer Mode Adaptation Layer 2 B. Thompson T. Koren B. Buffam December 2002 ASCII 14911 7 point-to-point protocol atm aal2 encapsulation ietf-pppext-ppp-over-aal2-class-02 PROPOSED STANDARD PROPOSED STANDARD RFC3338 Dual Stack Hosts Using "Bump-in-the-API" (BIA) S. Lee M-K. Shin Y-J. Kim E. Nordmark A. Durand October 2002 ASCII 34480 17 ietf-ngtrans-bia-05 EXPERIMENTAL EXPERIMENTAL RFC3339 Date and Time on the Internet: Timestamps G. Klyne C. Newman July 2002 ASCII 35064 18 gregorian calendar iso ietf-impp-datetime-05 PROPOSED STANDARD PROPOSED STANDARD RFC3340 The Application Exchange Core M. Rose G. Klyne D. Crocker July 2002 ASCII 74266 40 APEX ietf-apex-core-06 PROPOSED STANDARD PROPOSED STANDARD RFC3341 The Application Exchange (APEX) Access Service M. Rose G. Klyne D. Crocker July 2002 ASCII 46675 26 APEX ietf-apex-access-08 PROPOSED STANDARD PROPOSED STANDARD RFC3342 The Application Exchange (APEX) Option Party Pack, Part Deux! E. Dixon H. Franklin J. Kint G. Klyne D. New S. Pead M. Rose M. Schwartz July 2002 ASCII 34300 22 datagram service core relaying mesh ietf-apex-party-04 PROPOSED STANDARD PROPOSED STANDARD RFC3343 The Application Exchange (APEX) Presence Service M. Rose G. Klyne D. Crocker April 2003 ASCII 42043 23 endpoint ietf-apex-presence-06 EXPERIMENTAL EXPERIMENTAL RFC3344 IP Mobility Support for IPv4 C. Perkins Editor August 2002 ASCII 241041 99 MOBILEIPSUPIP Internet Protocol RFC3220 PROPOSED STANDARD PROPOSED STANDARD RFC3345 Border Gateway Protocol (BGP) Persistent Route Oscillation Condition D. McPherson V. Gill D. Walton A. Retana August 2002 ASCII 38137 19 idr ibgp ietf-idr-route-oscillation-01 INFORMATIONAL INFORMATIONAL RFC3346 Applicability Statement for Traffic Engineering with MPLS J. Boyle V. Gill A. Hannan D. Cooper D. Awduche B. Christian W.S. Lai August 2002 ASCII 33754 14 multiprotocol label switching te ietf-tewg-te-applicability-01 INFORMATIONAL INFORMATIONAL RFC3347 Small Computer Systems Interface protocol over the Internet (iSCSI) Requirements and Design Considerations M. Krueger R. Haagens July 2002 ASCII 58097 26 scsi tcp. storage fibre channel ietf-ips-iscsi-reqmts-06 PROPOSED STANDARD PROPOSED STANDARD RFC3348 The Internet Message Action Protocol (IMAP4) Child Mailbox Extension M. Gahrns R. Cheng July 2002 ASCII 11868 6 children gahrns-imap-child-mailbox-04 INFORMATIONAL INFORMATIONAL RFC3349 A Transient Prefix for Identifying Profiles under Development by the Working Groups of the Internet Engineering Task Force M. Rose July 2002 ASCII 7916 6 beep mrose-beep-transientid-02 BCP0059 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3351 User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals N. Charlton M. Gasson G. Gybels M. Spanner A. van Wijk August 2002 ASCII 33894 17 relay service transcoding service textphone ietf-sipping-deaf-req-03 INFORMATIONAL INFORMATIONAL RFC3352 Connection-less Lightweight Directory Access Protocol (CLDAP) to Historic Status K. Zeilenga March 2003 ASCII 7265 4 CLDAP CLDAP Presentation Address Application Entity Title zeilenga-cldap-02 RFC1798 INFORMATIONAL INFORMATIONAL RFC3353 Overview of IP Multicast in a Multi-Protocol Label Switching (MPLS) Environment D. Ooms B. Sales W. Livens A. Acharya F. Griffoul F. Ansari August 2002 ASCII 65860 30 inrternet protocol l2 multicast routing protocoln ietf-mpls-multicast-08 INFORMATIONAL INFORMATIONAL RFC3354 Internet Open Trading Protocol Version 2 Requirements D. Eastlake 3rd August 2002 ASCII 9671 6 payment ecommerce merchant customer delivery signature messaging commerce sale ietf-trade-iotp2-req-02 INFORMATIONAL INFORMATIONAL RFC3355 Layer Two Tunnelling Protocol (L2TP) Over ATM Adaptation Layer 5 (AAL5) A. Singh R. Turner R. Tio S. Nanji August 2002 ASCII 25114 13 link dial-up server asynchronous transfer mode ietf-l2tpext-l2tp-atm-03 PROPOSED STANDARD PROPOSED STANDARD RFC3356 Internet Engineering Task Force and International Telecommunication Union - Telecommunications Standardization Sector Collaboration Guidelines G. Fishman S. Bradner August 2002 ASCII 27149 12 internet society engineering task force fishman-2436bis-02 RFC2436 INFORMATIONAL INFORMATIONAL RFC3357 One-way Loss Pattern Sample Metrics R. Koodli R. Ravikanth August 2002 ASCII 30570 15 packets voice video stream ietf-ippm-loss-pattern-07 INFORMATIONAL INFORMATIONAL RFC3358 Optional Checksums in Intermediate System to Intermediate System (ISIS) R. Koodli R. Ravikanth August 2002 ASCII 8266 4 type length value complete sequence number partial data ietf-isis-wg-snp-checksum-03 INFORMATIONAL INFORMATIONAL RFC3359 Reserved Type, Length and Value (TLV) Codepoints in Intermediate System to Intermediate System T. Przygienda August 2002 ASCII 7843 5 is-is igp osi complete sequence number partial data ietf-isis-wg-tlv-codepoints-01 INFORMATIONAL INFORMATIONAL RFC3360 Inappropriate TCP Resets Considered Harmful S. Floyd August 2002 ASCII 46748 19 transmission control protocol rst bit connection floyd-tcp-reset-04 BCP0060 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3361 Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers H. Schulzrinne August 2002 ASCII 12549 7 proxy servers ietf-sip-dhcp-06 PROPOSED STANDARD PROPOSED STANDARD RFC3362 Real-time Facsimile (T.38) - image/t38 MIME Sub-type Registration G. Parsons August 2002 ASCII 8301 5 parsons-itu-t38-reg-00 PROPOSED STANDARD PROPOSED STANDARD RFC3363 Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System (DNS) R. Bush A. Durand B. Fink O. Gudmundsson T. Hain August 2002 ASCII 11055 6 reverse mapping label binary ietf-dnsext-ipv6-addresses-02 RFC2673 RFC2874 INFORMATIONAL INFORMATIONAL RFC3364 Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6) R. Austein August 2002 ASCII 26544 11 reverse mapping rrs resource records ietf-dnsext-ipv6-dns-tradeoffs-02 RFC2673 RFC2874 INFORMATIONAL INFORMATIONAL RFC3365 Strong Security Requirements for Internet Engineering Task Force Standard Protocols J. Schiller August 2002 ASCII 16411 8 ietf ietf-saag-whyenc-00 BCP0061 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3366 Advice to link designers on link Automatic Repeat reQuest (ARQ) G. Fairhurst L. Wood August 2002 ASCII 66097 27 tcp/ip subnetworks ietf-pilc-link-arq-issues-04 BCP0062 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3367 Common Name Resolution Protocol (CNRP) N. Popp M. Mealling M. Moseley August 2002 ASCII 86889 42 unique resource locators client applications ietf-cnrp-12 PROPOSED STANDARD PROPOSED STANDARD RFC3368 The 'go' URI Scheme for the Common Name Resolution Protocol M. Mealling August 2002 ASCII 12726 8 uniform resource identifier ietf-cnrp-uri-07 PROPOSED STANDARD PROPOSED STANDARD RFC3369 Cryptographic Message Syntax (CMS) R. Housley August 2002 ASCII 113975 52 digitally sign authenticate encrypt arbitrary message content ietf-smime-rfc2630bis-08 RFC2630 RFC3211 RFC3852 PROPOSED STANDARD PROPOSED STANDARD RFC3370 Cryptographic Message Syntax (CMS) Algorithms R. Housley August 2002 ASCII 51001 24 digitally sign authenticate encrypt arbitrary message content ietf-smime-cmsalg-08 RFC2630 RFC3211 PROPOSED STANDARD PROPOSED STANDARD RFC3371 Layer Two Tunneling Protocol "L2TP" Management Information Base E. Caves P. Calhoun R. Wheeler August 2002 ASCII 139974 70 mib ietf-l2tpext-l2tp-mib-04 PROPOSED STANDARD PROPOSED STANDARD RFC3372 Session Initiation Protocol for Telephones (SIP-T): Context and Architectures A. Vemuri J. Peterson September 2002 ASCII 49893 23 pstn public switch telephone network ietf-sipping-sipt-04 BCP0063 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3373 Three-Way Handshake for Intermediate System to Intermediate System (IS-IS) Point-to-Point Adjacencies D. Katz R. Saluja September 2002 ASCII 19522 9 links handshake ietf-isis-3way-06 INFORMATIONAL INFORMATIONAL RFC3374 Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network J. Kempf Editor September 2002 ASCII 28245 14 aaa qos authentication authorization accounting quality of service header compression ietf-seamoby-context-transfer-problem-stat-04 INFORMATIONAL INFORMATIONAL RFC3375 Generic Registry-Registrar Protocol Requirements S. Hollenbeck September 2002 ASCII 46022 21 rrp client server domain names ietf-provreg-grrp-reqs-06 INFORMATIONAL INFORMATIONAL RFC3376 Internet Group Management Protocol, Version 3 B. Cain S. Deering I. Kouvelas B. Fenner A. Thyagarajan October 2002 ASCII 119726 53 IGMP IGMP multicast routing IP Internet Protocol ietf-idmr-igmp-v3-11 RFC2236 PROPOSED STANDARD PROPOSED STANDARD RFC3377 Lightweight Directory Access Protocol (v3): Technical Specification J. Hodges R. Morgan September 2002 ASCII 9981 6 ldap ldapv3 ietf-ldapbis-ldapv3-ts-01 RFC2251 RFC2252 RFC2253 RFC2254 RFC2255 RFC2256 RFC2829 RFC2830 PROPOSED STANDARD PROPOSED STANDARD RFC3378 EtherIP: Tunneling Ethernet Frames in IP Datagrams R. Housley S. Hollenbeck September 2002 ASCII 18803 9 internet protocol ip 97 housley-etherip-04 INFORMATIONAL INFORMATIONAL RFC3379 Delegated Path Validation and Delegated Path Discovery Protocol Requirements D. Pinkas R. Housley September 2002 ASCII 32455 15 dpv dpd public key certificates ietf-pkix-dpv-dpd-req-05 INFORMATIONAL INFORMATIONAL RFC3380 Internet Printing Protocol (IPP): Job and Printer Set Operations T. Hastings R. Herriot C. Kugler H. Lewis September 2002 ASCII 132044 59 IPP-E-T IPP application media-type media type ietf-ipp-job-printer-set-ops-05 RFC2910 RFC2911 PROPOSED STANDARD PROPOSED STANDARD RFC3381 Internet Printing Protocol (IPP): Job Progress Attributes T. Hastings H. Lewis R. Bergman September 2002 ASCII 36595 17 IPP-E-T IPP application media-type media type ietf-ipp-job-prog-02 RFC2910 PROPOSED STANDARD PROPOSED STANDARD RFC3382 Internet Printing Protocol (IPP): The 'collection' attribute syntax R. deBry T. Hastings R. Herriot K. Ocke P. Zehler September 2002 ASCII 78173 38 IPP-E-T IPP application media-type media type ietf-ipp-collection-05 RFC2910 RFC2911 PROPOSED STANDARD PROPOSED STANDARD RFC3383 Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP) K. Zeilenga September 2002 ASCII 45893 23 guidelines extensible values ietf-ldapbis-iana-09 BCP0064 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3384 Lightweight Directory Access Protocol (version 3) Replication Requirements E. Stokes R. Weiser R. Moats R. Huber October 2002 ASCII 66871 31 ldapv3 data interoperability synchronization multi-master ietf-ldup-replica-req-12 INFORMATIONAL INFORMATIONAL RFC3385 Internet Protocol Small Computer System Interface (iSCSI) Cyclic Redundancy Check (CRC)/Checksum Considerations D. Sheinwald J. Satran P. Thaler V. Cavanna September 2002 ASCII 53450 23 error detection code INFORMATIONAL INFORMATIONAL RFC3386 Network Hierarchy and Multilayer Survivability W. Lai Editor D. McDysan Editor November 2002 ASCII 65345 27 service provider packet networks protection restoration recovery ietf-tewg-restore-hierarchy-01 INFORMATIONAL INFORMATIONAL RFC3387 Considerations from the Service Management Research Group (SMRG) on Quality of Service (QoS) in the IP Network M. Eder H. Chaskar S. Nag September 2002 ASCII 52693 19 internet protocol packts fuel-service irtf-smrg-ipsmf-01 INFORMATIONAL INFORMATIONAL RFC3388 Grouping of Media Lines in the Session Description Protocol (SDP) G. Camarillo G. Eriksson J. Holler H. Schulzrinne December 2002 ASCII 39365 11 formats attribute port host interfaces fid flow identification lip synchronization ls ietf-mmusic-fid-06 PROPOSED STANDARD PROPOSED STANDARD RFC3389 Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN) R. Zopf September 2002 ASCII 17018 8 codecs audio multimedia ietf-avt-rtp-cn-06 PROPOSED STANDARD PROPOSED STANDARD RFC3390 Increasing TCP's Initial Window M. Allman S. Floyd C. Partridge October 2002 ASCII 36177 15 transmission control protocol ietf-tsvwg-initwin-04 RFC2414 RFC2581 PROPOSED STANDARD PROPOSED STANDARD RFC3391 The MIME Application/Vnd.pwg-multiplexed Content-Type R. Herriot December 2002 ASCII 54739 25 multipurpose internet mail extensions media type herriot-application-multiplexed-05 INFORMATIONAL INFORMATIONAL RFC3392 Capabilities Advertisement with BGP-4 R. Chandra J. Scudder November 2002 ASCII 9885 6 border gateway protocol ietf-idr-rfc2842bis-02 RFC2842 DRAFT STANDARD DRAFT STANDARD RFC3393 IP Packet Delay Variation Metric for IP Performance Metrics (IPPM) C. Demichelis P. Chimento November 2002 ASCII 47731 21 internet protocol ipdv ietf-ippm-ipdv-10 PROPOSED STANDARD PROPOSED STANDARD RFC3394 Advanced Encryption Standard (AES) Key Wrap Algorithm J. Schaad R. Housley September 2002 ASCII 73072 41 security ietf-smime-aes-keywrap-00 INFORMATIONAL INFORMATIONAL RFC3395 Remote Network Monitoring MIB Protocol Identifier Reference Extensions A. Bierman C. Bucci R. Dietz A. Warth September 2002 ASCII 43862 21 RMON-MIB management information base ietf-rmonmib-appverbs-04 RFC2895 PROPOSED STANDARD PROPOSED STANDARD RFC3396 Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4) T. Lemon S. Cheshire November 2002 ASCII 18779 9 octet packet code ietf-dhc-concat-05 RFC2131 PROPOSED STANDARD PROPOSED STANDARD RFC3397 Dynamic Host Configuration Protocol (DHCP) Domain Search Option B. Aboba S. Cheshire November 2002 ASCII 15446 8 dns client client server aboba-dhc-domsearch-09 PROPOSED STANDARD PROPOSED STANDARD RFC3398 Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping G. Camarillo A. B. Roach J. Peterson L. Ong December 2002 ASCII 166197 68 signaling system no. 7 ss7 pstn public switched telephone network ietf-sipping-isup-06 PROPOSED STANDARD PROPOSED STANDARD RFC3400 RFC3401 Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS M. Mealling October 2002 ASCII 10172 6 NAPTR domain name system RR This document specifies the exact documents that make up the complete Dynamic Delegation Discovery System (DDDS). DDDS is an abstract algorithm for applying dynamically retrieved string transformation rules to an application-unique string. This document along with RFC 3402, RFC 3403 and RFC 3404 obsolete RFC 2168 and RFC 2915, as well as updates RFC 2276. This memo provides information for the Internet community. ietf-urn-ddds-toc-03 RFC2915 RFC2168 RFC2276 INFORMATIONAL INFORMATIONAL RFC3402 Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm M. Mealling October 2002 ASCII 38925 17 NAPTR domain name system RR This document describes the Dynamic Delegation Discovery System (DDDS) algorithm for applying dynamically retrieved string transformation rules to an application-unique string. Well-formed transformation rules will reflect the delegation of management of information associated with the string. This document is also part of a series that is completely specified in "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS" (RFC 3401). It is very important to note that it is impossible to read and understand any document in this series without reading the others. [STANDARDS TRACK] ietf-urn-ddds-07 RFC2915 RFC2168 PROPOSED STANDARD PROPOSED STANDARD RFC3403 Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database M. Mealling October 2002 ASCII 31058 14 NAPTR domain name system RR This document describes a Dynamic Delegation Discovery System (DDDS) Database using the Domain Name System (DNS) as a distributed database of Rules. The Keys are domain-names and the Rules are encoded using the Naming Authority Pointer (NAPTR) Resource Record (RR). Since this document obsoletes RFC 2915, it is the official specification for the NAPTR DNS Resource Record. It is also part of a series that is completely specified in "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS" (RFC 3401). It is very important to note that it is impossible to read and understand any document in this series without reading the others. [STANDARDS TRACK] ietf-urn-dns-ddds-database-09 RFC2915 RFC2168 PROPOSED STANDARD PROPOSED STANDARD RFC3404 Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI) M. Mealling October 2002 ASCII 40124 18 NAPTR domain name system RR This document describes a specification for taking Uniform Resource Identifiers (URI) and locating an authoritative server for information about that URI. The method used to locate that authoritative server is the Dynamic Delegation Discovery System. This document is part of a series that is specified in "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS" (RFC 3401). It is very important to note that it is impossible to read and understand any document in this series without reading the others. [STANDARDS TRACK] ietf-urn-uri-res-ddds-07 RFC2915 RFC2168 PROPOSED STANDARD PROPOSED STANDARD RFC3405 Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures M. Mealling October 2002 ASCII 19469 10 uniform resource identifiers This document is fifth in a series that is completely specified in "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS" (RFC 3401). It is very important to note that it is impossible to read and understand any document in this series without reading the others. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-urn-net-procedures-11 BCP0065 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3406 Uniform Resource Names (URN) Namespace Definition Mechanisms L. Daigle D. van Gulik R. Iannella P. Faltstrom October 2002 ASCII 43707 22 namespaces applications structure This document lays out general definitions of and mechanisms for establishing Uniform Resource Names (URN) "namespaces". The URN WG has defined a syntax for URNs in RFC 2141, as well as some proposed mechanisms for their resolution and use in Internet applications in RFC 3401 and RFC 3405. The whole rests on the concept of individual "namespaces" within the URN structure. Apart from proof-of-concept namespaces, the use of existing identifiers in URNs has been discussed in RFC 2288. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-urn-rfc2611bis-04 RFC2611 BCP0066 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3407 Session Description Protocol (SDP) Simple Capability Declaration F. Andreasen October 2002 ASCII 21133 10 SDPng This document defines a set of Session Description Protocol (SDP) attributes that enables SDP to provide a minimal and backwards compatible capability declaration mechanism. Such capability declarations can be used as input to a subsequent session negotiation, which is done by means outside the scope of this document. This provides a simple and limited solution to the general capability negotiation problem being addressed by the next generation of SDP, also known as SDPng. [STANDARDS TRACK] andreasen-mmusic-sdp-simcap-05 PROPOSED STANDARD PROPOSED STANDARD RFC3408 Zero-byte Support for Bidirectional Reliable Mode (R-mode) in Extended Link-Layer Assisted RObust Header Compression (ROHC) Profile Z. Liu K. Le December 2002 ASCII 14805 7 single-octet packet size This document defines an additional mode of the link-layer assisted RObust Header Compression (ROHC) profile, also known as the zero-byte profile, beyond the two defined in RFC 3242. Zero-byte header compression exists in order to prevent the single-octet ROHC header from pushing a packet voice stream into the next higher fixed packet size for the radio. It is usable in certain widely deployed older air interfaces. This document adds the zero-byte operation for ROHC Bidirectional Reliable mode (R-mode) to the ones specified for Unidirectional (U-mode) and Bidirectional Optimistic (O-mode) modes of header compression in RFC 3242. [STANDARDS TRACK] ietf-rohc-rtp-lla-r-mode-02 PROPOSED STANDARD PROPOSED STANDARD RFC3409 Lower Layer Guidelines for Robust RTP/UDP/IP Header Compression K. Svanbro December 2002 ASCII 25815 11 rohc algorithms This document describes lower layer guidelines for robust header compression (ROHC) and the requirements ROHC puts on lower layers. The purpose of this document is to support the incorporation of robust header compression algorithms, as specified in the ROHC working group, into different systems such as those specified by Third Generation Partnership Project (3GPP), 3GPP Project 2 (3GPP2), European Technical Standards Institute (ETSI), etc. This document covers only lower layer guidelines for compression of RTP/UDP/IP and UDP/IP headers as specified in [RFC3095]. Both general guidelines and guidelines specific for cellular systems are discussed in this document. This memo provides information for the Internet community. ietf-rohc-rtp-lower-layer-guidelines-03 INFORMATIONAL INFORMATIONAL RFC3410 Introduction and Applicability Statements for Internet-Standard Management Framework J. Case R. Mundy D. Partain B. Stewart December 2002 ASCII 61461 27 snmp simple protocol snmpv3 The purpose of this document is to provide an overview of the third version of the Internet-Standard Management Framework, termed the SNMP version 3 Framework (SNMPv3). This Framework is derived from and builds upon both the original Internet-Standard Management Framework (SNMPv1) and the second Internet-Standard Management Framework (SNMPv2). The architecture is designed to be modular to allow the evolution of the Framework over time. The document explains why using SNMPv3 instead of SNMPv1 or SNMPv2 is strongly recommended. The document also recommends that RFCs 1157, 1441, 1901, 1909 and 1910 be retired by moving them to Historic status. This document obsoletes RFC 2570. This memo provides information for the Internet community. ietf-snmpv3-rfc2570bis-03 RFC2570 INFORMATIONAL INFORMATIONAL RFC3411 An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks D. Harrington R. Presuhn B. Wijnen December 2002 ASCII 140096 64 ARCH-SNMP simple protocol network management This document describes an architecture for describing Simple Network Management Protocol (SNMP) Management 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 a Message Processing Subsystem, a Security Subsystem and an Access Control Subsystem, and possibly multiple SNMP applications which provide specific functional processing of management data. This document obsoletes RFC 2571. [STANDARDS TRACK] ietf-snmpv3-arch-v2-02 RFC2571 STD0062 STANDARD STANDARD RFC3412 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) J. Case D. Harrington R. Presuhn B. Wijnen December 2002 ASCII 95710 43 MPD-SNMP processing models multiple This document describes the Message Processing and Dispatching for Simple Network Management Protocol (SNMP) messages within the SNMP architecture. 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. This document obsoletes RFC 2572. [STANDARDS TRACK] ietf-snmpv3-mpd-v2-02 RFC2572 STD0062 STANDARD STANDARD RFC3413 Simple Network Management Protocol (SNMP) Applications D. Levi P. Meyer B. Stewart December 2002 ASCII 153719 74 SNMP-APP simple network management protocol proxy operations command This document describes five types of Simple Network Management Protocol (SNMP) applications which make use of an SNMP engine as described in STD 62, RFC 3411. The types of application described are Command Generators, Command Responders, Notification Originators, Notification Receivers, and Proxy Forwarders. This document also defines Management Information Base (MIB) modules for specifying targets of management operations, for notification filtering, and for proxy forwarding. This document obsoletes RFC 2573. [STANDARDS TRACK] ietf-snmpv3-appl-v3-01 RFC2573 STD0062 STANDARD STANDARD RFC3414 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) U. Blumenthal B. Wijnen December 2002 ASCII 193558 88 USM-SNMPV3 message level mib information base This document describes the User-based Security Model (USM) for Simple Network Management Protocol (SNMP) version 3 for use in the SNMP architecture. It defines the Elements of Procedure for providing SNMP message level security. This document also includes a Management Information Base (MIB) for remotely monitoring/managing the configuration parameters for this Security Model. This document obsoletes RFC 2574. [STANDARDS TRACK] ietf-snmpv3-usm-v2-rfc2574bis-01 RFC2574 STD0062 STANDARD STANDARD RFC3415 View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) B. Wijnen R. Presuhn K. McCloghrie December 2002 ASCII 82046 39 VACM-SNMP mib information base This document describes the View-based Access Control Model (VACM) for use in the Simple Network Management Protocol (SNMP) architecture. It defines the Elements of Procedure for controlling access to management information. This document also includes a Management Information Base (MIB) for remotely managing the configuration parameters for the View- based Access Control Model. This document obsoletes RFC 2575. [STANDARDS TRACK] ietf-snmpv3-vacm-v2-01 RFC2575 STD0062 STANDARD STANDARD RFC3416 Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP) R. Presuhn Editor December 2002 ASCII 70043 31 OPS-MIB Simple Network Management Protocol Version 2 This document defines version 2 of the protocol operations for the Simple Network Management Protocol (SNMP). It defines the syntax and elements of procedure for sending, receiving, and processing SNMP PDUs. This document obsoletes RFC 1905. [STANDARDS TRACK] ietf-snmpv3-update-proto-08 RFC1905 STD0062 STANDARD STANDARD RFC3417 Transport Mappings for the Simple Network Management Protocol (SNMP) R. Presuhn Editor December 2002 ASCII 38650 19 TRANS-MIB Simple Network Management Protocol Version 2 This document defines the transport of Simple Network Management Protocol (SNMP) messages over various protocols. This document obsoletes RFC 1906. [STANDARDS TRACK] ietf-snmpv3-update-transmap-08 RFC1906 STD0062 STANDARD STANDARD RFC3418 Management Information Base (MIB) for the Simple Network Management Protocol (SNMP) R. Presuhn Editor December 2002 ASCII 49096 26 SNMPv2-MIB Simple Network Management Protocol Version 2 This document defines managed objects which describe the behavior of a Simple Network Management Protocol (SNMP) entity. This document obsoletes RFC 1907, Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2). [STANDARDS TRACK] ietf-snmpv3-update-mib-07 RFC1907 STD0062 STANDARD STANDARD RFC3419 Textual Conventions for Transport Addresses M. Daniele J. Schoenwaelder December 2002 ASCII 37466 18 mib management information base This document introduces a Management Information Base (MIB) module that defines textual conventions to represent commonly used transport-layer addressing information. The definitions are compatible with the concept of TAddress/TDomain pairs introduced by the Structure of Management Information version 2 (SMIv2) and support the Internet transport protocols over IPv4 and IPv6. [STANDARDS TRACK] ietf-ops-taddress-mib-05 PROPOSED STANDARD PROPOSED STANDARD RFC3420 Internet Media Type message/sipfrag R. Sparks November 2002 ASCII 14745 8 mime multipurpose internet mail extesions This document registers the message/sipfrag Multipurpose Internet Mail Extensions (MIME) media type. This type is similar to message/sip, but allows certain subsets of well formed Session Initiation Protocol (SIP) messages to be represented instead of requiring a complete SIP message. In addition to end-to-end security uses, message/sipfrag is used with the REFER method to convey information about the status of a referenced request. [STANDARDS TRACK] ietf-sip-sipfrag-00 PROPOSED STANDARD PROPOSED STANDARD RFC3421 Select and Sort Extensions for the Service Location Protocol (SLP) W. Zhao H. Schulzrinne E. Guttman C. Bisdikian W. Jerome November 2002 ASCII 15260 8 user agent url service reply ua svrrply This document defines two extensions (Select and Sort) for the Service Location Protocol (SLP). These extensions allow a User Agent (UA) to request that the Uniform Resource Locator (URL) entries in a Service Reply (SrvRply) be limited to the specified number, or be sorted according to the specified sort key list. Using these two extensions together can facilitate discovering the best match, such as finding a service that has the maximum speed or the minimum load. This memo defines an Experimental Protocol for the Internet community. zhao-slp-customization-05 EXPERIMENTAL EXPERIMENTAL RFC3422 Forwarding Media Access Control (MAC) Frames over Multiple Access Protocol over Synchronous Optical Network/Synchronous Digital Hierarchy (MAPOS) O. Okamoto M. Maruyama T. Sajima November 2002 ASCII 37576 19 tunneling ethernet frames This memo describes a method for forwarding media access control (MAC) frames over Multiple Access Protocol over Synchronous Optical Network/Synchronous Digital Hierarchy (MAPOS), thus providing a way to unify MAPOS network environment and MAC-based Local Area Network (LAN) environment. This memo provides information for the Internet community. okamoto-mac-over-mapos-02 INFORMATIONAL INFORMATIONAL RFC3423 XACCT's Common Reliable Accounting for Network Element (CRANE) Protocol Specification Version 1.0 K. Zhang E. Elkin November 2002 ASCII 97731 45 data delivery message format template-based client/server This document defines the Common Reliable Accounting for Network Element (CRANE) protocol that enables efficient and reliable delivery of any data, mainly accounting data from Network Elements to any systems, such as mediation systems and Business Support Systems (BSS)/ Operations Support Systems (OSS). The protocol is developed to address the critical needs for exporting high volume of accounting data from NE's with efficient use of network, storage, and processing resources. This document specifies the architecture of the protocol and the message format, which MUST be supported by all CRANE protocol implementations. This memo provides information for the Internet community. kzhang-crane-protocol-02 INFORMATIONAL INFORMATIONAL RFC3424 IAB Considerations for UNilateral Self-Address Fixing (UNSAF) Across Network Address Translation L. Daigle Editor IAB November 2002 ASCII 18165 9 nat middleboxes As a result of the nature of Network Address Translation (NAT) Middleboxes, communicating endpoints that are separated by one or more NATs do not know how to refer to themselves using addresses that are valid in the addressing realms of their (current and future) peers. Various proposals have been made for "UNilateral Self-Address Fixing (UNSAF)" processes. These are processes whereby some originating endpoint attempts to determine or fix the address (and port) by which it is known to another endpoint - e.g., to be able to use address data in the protocol exchange, or to advertise a public address from which it will receive connections. This document outlines the reasons for which these proposals can be considered at best as short term fixes to specific problems and the specific issues to be carefully evaluated before creating an UNSAF proposal. This memo provides information for the Internet community. iab-unsaf-considerations-02 INFORMATIONAL INFORMATIONAL RFC3425 Obsoleting IQUERY D. Lawrence November 2002 ASCII 8615 5 dns lookups domain The IQUERY method of performing inverse DNS lookups, specified in RFC 1035, has not been generally implemented and has usually been operationally disabled where it has been implemented. Both reflect a general view in the community that the concept was unwise and that the widely-used alternate approach of using pointer (PTR) queries and reverse-mapping records is preferable. Consequently, this document deprecates the IQUERY operation, declaring it entirely obsolete. This document updates RFC 1035. [STANDARDS TRACK] ietf-dnsext-obsolete-iquery-04 RFC1035 PROPOSED STANDARD PROPOSED STANDARD RFC3426 General Architectural and Policy Considerations S. Floyd November 2002 ASCII 54868 23 internet architecture This document suggests general architectural and policy questions that the IETF community has to address when working on new standards and protocols. We note that this document contains questions to be addressed, as opposed to guidelines or architectural principles to be followed. This memo provides information for the Internet community. iab-considerations-03 INFORMATIONAL INFORMATIONAL RFC3427 Change Process for the Session Initiation Protocol (SIP) A. Mankin S. Bradner R. Mahy D. Willis J. Ott B. Rosen December 2002 ASCII 26234 12 sipping This memo documents a process intended to apply architectural discipline to the future development of the Session Initiation Protocol (SIP). There have been concerns with regards to new SIP proposals. Specifically, that the addition of new SIP features can be damaging towards security and/or greatly increase the complexity of the protocol. The Transport Area directors, along with the SIP and Session Initiation Proposal Investigation (SIPPING) working group chairs, have provided suggestions for SIP modifications and extensions. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. tsvarea-sipchange-03 RFC3968 RFC3969 BCP0067 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3428 Session Initiation Protocol (SIP) Extension for Instant Messaging B. Campbell Editor J. Rosenberg H. Schulzrinne C. Huitema D. Gurle December 2002 ASCII 41475 18 im message method Instant Messaging (IM) refers to the transfer of messages between users in near real-time. These messages are usually, but not required to be, short. IMs are often used in a conversational mode, that is, the transfer of messages back and forth is fast enough for participants to maintain an interactive conversation. This document proposes the MESSAGE method, an extension to the Session Initiation Protocol (SIP) that allows the transfer of Instant Messages. Since the MESSAGE request is an extension to SIP, it inherits all the request routing and security features of that protocol. MESSAGE requests carry the content in the form of MIME body parts. MESSAGE requests do not themselves initiate a SIP dialog; under normal usage each Instant Message stands alone, much like pager messages. MESSAGE requests may be sent in the context of a dialog initiated by some other SIP request. [STANDARDS TRACK] ietf-sip-message-07 PROPOSED STANDARD PROPOSED STANDARD RFC3429 Assignment of the 'OAM Alert Label' for Multiprotocol Label Switching Architecture (MPLS) Operation and Maintenance (OAM) Functions H. Ohta November 2002 ASCII 10903 6 reserved lavel values This document describes the assignment of one of the reserved label values defined in RFC 3032 (MPLS label stack encoding) to the 'Operation and Maintenance (OAM) Alert Label' that is used by user-plane Multiprotocol Label Switching Architecture (MPLS) OAM functions for identification of MPLS OAM packets. This memo provides information for the Internet community. ohta-mpls-label-value-03 INFORMATIONAL INFORMATIONAL RFC3430 Simple Network Management Protocol Over Transmission Control Protocol Transport Mapping J. Schoenwaelder December 2002 ASCII 21527 10 snmp tcp This memo defines a transport mapping for using the Simple Network Management Protocol (SNMP) over TCP. The transport mapping can be used with any version of SNMP. This document extends the transport mappings defined in STD 62, RFC 3417. This memo defines an Experimental Protocol for the Internet community. irtf-nmrg-snmp-tcp-09 EXPERIMENTAL EXPERIMENTAL RFC3431 Sieve Extension: Relational Tests W. Segmuller December 2002 ASCII 12849 8 sieve mail filtering language This document describes the RELATIONAL extension to the Sieve mail filtering language defined in RFC 3028. This extension extends existing conditional tests in Sieve to allow relational operators. In addition to testing their content, it also allows for testing of the number of entities in header and envelope fields. [STANDARDS TRACK] segmuller-sieve-relation-02 PROPOSED STANDARD PROPOSED STANDARD RFC3432 Network performance measurement with periodic streams V. Raisanen G. Grotefeld A. Morton November 2002 ASCII 52493 23 cbr constant bit rate periodic sampling poisson sampling This memo describes a periodic sampling method and relevant metrics for assessing the performance of IP networks. First, the memo motivates periodic sampling and addresses the question of its value as an alternative to the Poisson sampling described in RFC 2330. The benefits include applicability to active and passive measurements, simulation of constant bit rate (CBR) traffic (typical of multimedia communication, or nearly CBR, as found with voice activity detection), and several instances in which analysis can be simplified. The sampling method avoids predictability by mandating random start times and finite length tests. Following descriptions of the sampling method and sample metric parameters, measurement methods and errors are discussed. Finally, we give additional information on periodic measurements, including security considerations. [STANDARDS TRACK] ietf-ippm-npmps-08 PROPOSED STANDARD PROPOSED STANDARD RFC3433 Entity Sensor Management Information Base A. Bierman D. Romascanu K.C. Norseth December 2002 ASCII 31857 17 mib physical sensors snmp This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for extending the Entity MIB (RFC 2737) to provide generalized access to information related to physical sensors, which are often found in networking equipment (such as chassis temperature, fan RPM, power supply voltage). [STANDARDS TRACK] ietf-entmib-sensor-mib-01 PROPOSED STANDARD PROPOSED STANDARD RFC3434 Remote Monitoring MIB Extensions for High Capacity Alarms A. Bierman K. McCloghrie December 2002 ASCII 51072 24 rmon counter64 smiv2 snmp This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for extending the alarm thresholding capabilities found in the Remote Monitoring (RMON) MIB (RFC 2819), to provide similar threshold monitoring of objects based on the Counter64 data type. [STANDARDS TRACK] ietf-rmonmib-hc-alarm-mib-02 PROPOSED STANDARD PROPOSED STANDARD RFC3435 Media Gateway Control Protocol (MGCP) Version 1.0 F. Andreasen B. Foster January 2003 ASCII 467084 210 voice IP internet VoIP This document describes an application programming interface and a corresponding protocol (MGCP) which is used between elements of a decomposed multimedia gateway. The decomposed multimedia gateway consists of a Call Agent, which contains the call control "intelligence", and a media gateway which contains the media functions, e.g., conversion from TDM voice to Voice over IP. Media gateways contain endpoints on which the Call Agent can create, modify and delete connections in order to establish and control media sessions with other multimedia endpoints. Also, the Call Agent can instruct the endpoints to detect certain events and generate signals. The endpoints automatically communicate changes in service state to the Call Agent. Furthermore, the Call Agent can audit endpoints as well as the connections on endpoints. The basic and general MGCP protocol is defined in this document, however most media gateways will need to implement one or more MGCP packages, which define extensions to the protocol suitable for use with specific types of media gateways. Such packages are defined in separate documents. This memo provides information for the Internet community. andreasen-mgcp-rfc2705bis-05 RFC2705 RFC3661 INFORMATIONAL INFORMATIONAL RFC3436 Transport Layer Security over Stream Control Transmission Protocol A. Jungmaier E. Rescorla M. Tuexen December 2002 ASCII 16333 9 sctp tls This document describes the usage of the Transport Layer Security (TLS) protocol, as defined in RFC 2246, over the Stream Control Transmission Protocol (SCTP), as defined in RFC 2960 and RFC 3309. The user of TLS can take advantage of the features provided by SCTP, namely the support of multiple streams to avoid head of line blocking and the support of multi-homing to provide network level fault tolerance. Additionally, discussions of extensions of SCTP are also supported, meaning especially the support of dynamic reconfiguration of IP- addresses. [STANDARDS TRACK] ietf-tsvwg-tls-over-sctp-00 PROPOSED STANDARD PROPOSED STANDARD RFC3437 Layer-Two Tunneling Protocol Extensions for PPP Link Control Protocol Negotiation W. Palter W. Townsley December 2002 ASCII 20820 10 l2tp lcp This document defines extensions to the Layer Two Tunneling Protocol (L2TP) for enhanced support of link-specific Point to Point Protocol (PPP) options. PPP endpoints typically have direct access to the common physical media connecting them and thus have detailed knowledge about the media that is in use. When the L2TP is used, the two PPP peers are no longer directly connected over the same physical media. Instead, L2TP inserts a virtual connection over some or all of the PPP connection by tunneling PPP frames over a packet switched network such as IP. Under some conditions, an L2TP endpoint may need to negotiate PPP Link Control Protocol (LCP) options at a location which may not have access to all of the media information necessary for proper participation in the LCP negotiation. This document provides a mechanism for communicating desired LCP options between L2TP endpoints in advance of PPP LCP negotiation at the far end of an L2TP tunnel, as well as a mechanism for communicating the negotiated LCP options back to where the native PPP link resides. [STANDARDS TRACK] ietf-l2tpext-link-07 PROPOSED STANDARD PROPOSED STANDARD RFC3438 Layer Two Tunneling Protocol (L2TP) Internet Assigned Numbers Authority (IANA) Considerations Update W. Townsley December 2002 ASCII 9135 5 L2TP ppp point-to-point protocol packets This document describes updates to the Internet Assigned Numbers Authority (IANA) considerations for the Layer Two Tunneling Protocol (L2TP). This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-l2tpext-rfc2661-iana-01 BCP0068 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3439 Some Internet Architectural Guidelines and Philosophy R. Bush D. Meyer December 2002 ASCII 70333 28 IAB This document extends RFC 1958 by outlining some of the philosophical guidelines to which architects and designers of Internet backbone networks should adhere. We describe the Simplicity Principle, which states that complexity is the primary mechanism that impedes efficient scaling, and discuss its implications on the architecture, design and engineering issues found in large scale Internet backbones. This memo provides information for the Internet community. ymbk-arch-guidelines-03 RFC1958 INFORMATIONAL INFORMATIONAL RFC3440 Definitions of Extension Managed Objects for Asymmetric Digital Subscriber Lines F. Ly G. Bathrick December 2002 ASCII 76058 36 simple network management protocol mib adsl asymmetric digital subscriber line 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 additional managed objects used for managing Asymmetric Digital Subscriber Line (ADSL) interfaces not covered by the ADSL Line MIB (RFC 2662). [STANDARDS TRACK] ietf-adslmib-adslext-12 PROPOSED STANDARD PROPOSED STANDARD RFC3441 Asynchronous Transfer Mode (ATM) Package for the Media Gateway Control Protocol (MGCP) R. Kumar January 2003 ASCII 122455 50 connection codec profile This document describes an Asynchronous Transfer Mode (ATM) package for the Media Gateway Control Protocol (MGCP). This package includes new Local Connection Options, ATM-specific events and signals, and ATM connection parameters. Also included is a description of codec and profile negotiation. It extends the MGCP that is currently being deployed in a number of products. Implementers should be aware of developments in the IETF Megaco Working Group and ITU SG16, which are currently working on a potential successor to this protocol. This memo provides information for the Internet community. rajeshkumar-mgcp-atm-package-03 INFORMATIONAL INFORMATIONAL RFC3442 The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4 T. Lemon S. Cheshire B. Volz December 2002 ASCII 19370 9 Dynamic Host Configuration Protocol Bootstrap This document defines a new Dynamic Host Configuration Protocol (DHCP) option which is passed from the DHCP Server to the DHCP Client to configure a list of static routes in the client. The network destinations in these routes are classless - each routing table entry includes a subnet mask. [STANDARDS TRACK] ietf-dhc-csr-07 RFC2132 PROPOSED STANDARD PROPOSED STANDARD RFC3443 Time To Live (TTL) Processing in Multi-Protocol Label Switching (MPLS) Networks P. Agarwal B. Akyol January 2003 ASCII 18749 10 label stack encoding uniform model pipe model This document describes Time To Live (TTL) processing in hierarchical Multi-Protocol Label Switching (MPLS) networks and is motivated by the need to formalize a TTL-transparent mode of operation for an MPLS label-switched path. It updates RFC 3032, "MPLS Label Stack Encoding". TTL processing in both Pipe and Uniform Model hierarchical tunnels are specified with examples for both "push" and "pop" cases. The document also complements RFC 3270, "MPLS Support of Differentiated Services" and ties together the terminology introduced in that document with TTL processing in hierarchical MPLS networks. [STANDARDS TRACK] ietf-mpls-ttl-04 RFC3032 PROPOSED STANDARD PROPOSED STANDARD RFC3444 On the Difference between Information Models and Data Models A. Pras J. Schoenwaelder January 2003 ASCII 18596 8 network management There has been ongoing confusion about the differences between Information Models and Data Models for defining managed objects in network management. This document explains the differences between these terms by analyzing how existing network management model specifications (from the IETF and other bodies such as the International Telecommunication Union (ITU) or the Distributed Management Task Force (DMTF)) fit into the universe of Information Models and Data Models. This memo documents the main results of the 8th workshop of the Network Management Research Group (NMRG) of the Internet Research Task Force (IRTF) hosted by the University of Texas at Austin. This memo provides information for the Internet community. irtf-nmrg-im-dm-02 INFORMATIONAL INFORMATIONAL RFC3445 Limiting the Scope of the KEY Resource Record (RR) D. Massey S. Rose December 2002 ASCII 20947 10 DNS-SECEXT dns authentication This document limits the Domain Name System (DNS) KEY Resource Record (RR) to only keys used by the Domain Name System Security Extensions (DNSSEC). The original KEY RR used sub-typing to store both DNSSEC keys and arbitrary application keys. Storing both DNSSEC and application keys with the same record type is a mistake. This document removes application keys from the KEY record by redefining the Protocol Octet field in the KEY RR Data. As a result of removing application keys, all but one of the flags in the KEY record become unnecessary and are redefined. Three existing application key sub-types are changed to reserved, but the format of the KEY record is not changed. This document updates RFC 2535. [STANDARDS TRACK] ietf-dnsext-restrict-key-for-dnssec-04 RFC4033 RFC4034 RFC4035 RFC2535 PROPOSED STANDARD PROPOSED STANDARD RFC3446 Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP) D. Kim D. Meyer H. Kilmer D. Farinacci January 2003 ASCII 14792 7 sparse mode single shared-tree This document describes a mechanism to allow for an arbitrary number of Rendevous Points (RPs) per group in a single shared-tree Protocol Independent Multicast-Sparse Mode (PIM-SM) domain. This memo provides information for the Internet community. ietf-mboned-anycast-rp-08 INFORMATIONAL INFORMATIONAL RFC3447 Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1 J. Jonsson B. Kaliski February 2003 ASCII 143173 72 data public key cryptosystem This memo represents a republication of PKCS #1 v2.1 from RSA Laboratories' Public-Key Cryptography Standards (PKCS) series, and change control is retained within the PKCS process. The body of this document is taken directly from the PKCS #1 v2.1 document, with certain corrections made during the publication process. This memo provides information for the Internet community. jonsson-pkcs1-v2dot1-00 RFC2437 INFORMATIONAL INFORMATIONAL RFC3448 TCP Friendly Rate Control (TFRC): Protocol Specification M. Handley S. Floyd J. Padhye J. Widmer January 2003 ASCII 52657 24 congestion unicast streaming media This document specifies TCP-Friendly Rate Control (TFRC). TFRC is a congestion control mechanism for unicast flows operating in a best- effort Internet environment. It is reasonably fair when competing for bandwidth with TCP flows, but has a much lower variation of throughput over time compared with TCP, making it more suitable for applications such as telephony or streaming media where a relatively smooth sending rate is of importance. [STANDARDS TRACK] ietf-tsvwg-tfrc-05 PROPOSED STANDARD PROPOSED STANDARD RFC3449 TCP Performance Implications of Network Path Asymmetry H. Balakrishnan V. Padmanabhan G. Fairhurst M. Sooriyabandara December 2002 ASCII 108839 41 links sender receiver ack This document describes TCP performance problems that arise because of asymmetric effects. These problems arise in several access networks, including bandwidth-asymmetric networks and packet radio subnetworks, for different underlying reasons. However, the end result on TCP performance is the same in both cases: performance often degrades significantly because of imperfection and variability in the ACK feedback from the receiver to the sender. The document details several mitigations to these effects, which have either been proposed or evaluated in the literature, or are currently deployed in networks. These solutions use a combination of local link- layer techniques, subnetwork, and end-to-end mechanisms, consisting of: (i) techniques to manage the channel used for the upstream bottleneck link carrying the ACKs, typically using header compression or reducing the frequency of TCP ACKs, (ii) techniques to handle this reduced ACK frequency to retain the TCP sender's acknowledgment-triggered self- clocking and (iii) techniques to schedule the data and ACK packets in the reverse direction to improve performance in the presence of two-way traffic. Each technique is described, together with known issues, and recommendations for use. A summary of the recommendations is provided at the end of the document. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-pilc-asym-08 BCP0069 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3450 Asynchronous Layered Coding (ALC) Protocol Instantiation M. Luby J. Gemmell L. Vicisano L. Rizzo J. Crowcroft December 2002 ASCII 86022 34 content delivery congestion control receivers This document describes the Asynchronous Layered Coding (ALC) protocol, a massively scalable reliable content delivery protocol. Asynchronous Layered Coding combines the Layered Coding Transport (LCT) building block, a multiple rate congestion control building block and the Forward Error Correction (FEC) building block to provide congestion controlled reliable asynchronous delivery of content to an unlimited number of concurrent receivers from a single sender. This memo defines an Experimental Protocol for the Internet community. ietf-rmt-pi-alc-08 EXPERIMENTAL EXPERIMENTAL RFC3451 Layered Coding Transport (LCT) Building Block M. Luby J. Gemmell L. Vicisano L. Rizzo M. Handley J. Crowcroft December 2002 ASCII 72594 29 content stream delivery multicast internet protocol Layered Coding Transport (LCT) provides transport level support for reliable content delivery and stream delivery protocols. LCT is specifically designed to support protocols using IP multicast, but also provides support to protocols that use unicast. LCT is compatible with congestion control that provides multiple rate delivery to receivers and is also compatible with coding techniques that provide reliable delivery of content. This memo defines an Experimental Protocol for the Internet community. ietf-rmt-bb-lct-04 EXPERIMENTAL EXPERIMENTAL RFC3452 Forward Error Correction (FEC) Building Block M. Luby L. Vicisano J. Gemmell L. Rizzo M. Handley J. Crowcroft December 2002 ASCII 38368 16 content stream delivery multicast internet protocol This document generally describes how to use Forward Error Correction (FEC) codes to efficiently provide and/or augment reliability for data transport. The primary focus of this document is the application of FEC codes to one-to-many reliable data transport using IP multicast. This document describes what information is needed to identify a specific FEC code, what information needs to be communicated out-of-band to use the FEC code, and what information is needed in data packets to identify the encoding symbols they carry. The procedures for specifying FEC codes and registering them with the Internet Assigned Numbers Authority (IANA) are also described. This document should be read in conjunction with and uses the terminology of the companion document titled, "The Use of Forward Error Correction (FEC) in Reliable Multicast". This memo defines an Experimental Protocol for the Internet community. ietf-rmt-bb-fec-07 EXPERIMENTAL EXPERIMENTAL RFC3453 The Use of Forward Error Correction (FEC) in Reliable Multicast M. Luby L. Vicisano J. Gemmell L. Rizzo M. Handley J. Crowcroft December 2002 ASCII 46853 18 ip internet protocol data transport This memo describes the use of Forward Error Correction (FEC) codes to efficiently provide and/or augment reliability for one-to-many reliable data transport using IP multicast. One of the key properties of FEC codes in this context is the ability to use the same packets containing FEC data to simultaneously repair different packet loss patterns at multiple receivers. Different classes of FEC codes and some of their basic properties are described and terminology relevant to implementing FEC in a reliable multicast protocol is introduced. Examples are provided of possible abstract formats for packets carrying FEC. This memo provides information for the Internet community. ietf-rmt-info-fec-03 INFORMATIONAL INFORMATIONAL RFC3454 Preparation of Internationalized Strings ("stringprep") P. Hoffman M. Blanchet December 2002 ASCII 138684 91 unicode text internationalization This document describes a framework for preparing Unicode text strings in order to increase the likelihood that string input and string comparison work in ways that make sense for typical users throughout the world. The stringprep protocol is useful for protocol identifier values, company and personal names, internationalized domain names, and other text strings. This document does not specify how protocols should prepare text strings. Protocols must create profiles of stringprep in order to fully specify the processing options. [STANDARDS TRACK] hoffman-stringprep-07 PROPOSED STANDARD PROPOSED STANDARD RFC3455 Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP) M. Garcia-Martin E. Henrikson D. Mills January 2003 ASCII 79620 34 This document describes a set of private Session Initiation Protocol (SIP) headers (P-headers) used by the 3rd-Generation Partnership Project (3GPP), along with their applicability, which is limited to particular environments. The P-headers are for a variety of purposes within the networks that the partners use, including charging and information about the networks a call traverses. This memo provides information for the Internet community. garcia-sipping-3gpp-p-headers-02 INFORMATIONAL INFORMATIONAL RFC3456 Dynamic Host Configuration Protocol (DHCPv4) Configuration of IPsec Tunnel Mode B. Patel B. Aboba S. Kelly V. Gupta January 2003 ASCII 40340 18 security internet protocol This memo explores the requirements for host configuration in IPsec tunnel mode, and describes how the Dynamic Host Configuration Protocol (DHCPv4) may be leveraged for configuration. In many remote access scenarios, a mechanism for making the remote host appear to be present on the local corporate network is quite useful. This may be accomplished by assigning the host a "virtual" address from the corporate network, and then tunneling traffic via IPsec from the host's ISP-assigned address to the corporate security gateway. In IPv4, DHCP provides for such remote host configuration. [STANDARDS TRACK] ietf-ipsec-dhcp-13 PROPOSED STANDARD PROPOSED STANDARD RFC3457 Requirements for IPsec Remote Access Scenarios S. Kelly S. Ramamoorthi January 2003 ASCII 75167 31 ipsra common remote access scenarios IPsec offers much promise as a secure remote access mechanism. However, there are a number of differing remote access scenarios, each having some shared and some unique requirements. A thorough understanding of these requirements is necessary in order to effectively evaluate the suitability of a specific set of mechanisms for any particular remote access scenario. This document enumerates the requirements for a number of common remote access scenarios. This memo provides information for the Internet community. ietf-ipsra-reqmts-05 INFORMATIONAL INFORMATIONAL RFC3458 Message Context for Internet Mail E. Burger E. Candell C. Eliot G. Klyne January 2003 ASCII 34181 17 user agent ua This memo describes a new RFC 2822 message header, "Message-Context". This header provides information about the context and presentation characteristics of a message. A receiving user agent (UA) may use this information as a hint to optimally present the message. [STANDARDS TRACK] ietf-vpim-hint-08 RFC3938 PROPOSED STANDARD PROPOSED STANDARD RFC3459 Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter E. Burger January 2003 ASCII 54282 24 body parts content-disposition This document describes the use of a mechanism for identifying body parts that a sender deems critical in a multi-part Internet mail message. The mechanism described is a parameter to Content-Disposition, as described by RFC 3204. By knowing what parts of a message the sender deems critical, a content gateway can intelligently handle multi-part messages when providing gateway services to systems of lesser capability. Critical content can help a content gateway to decide what parts to forward. It can indicate how hard a gateway should try to deliver a body part. It can help the gateway to pick body parts that are safe to silently delete when a system of lesser capability receives a message. In addition, critical content can help the gateway chose the notification strategy for the receiving system. Likewise, if the sender expects the destination to do some processing on a body part, critical content allows the sender to mark body parts that the receiver must process. [STANDARDS TRACK] ietf-vpim-cc-08 RFC3204 PROPOSED STANDARD PROPOSED STANDARD RFC3460 Policy Core Information Model (PCIM) Extensions B. Moore Editor January 2003 ASCII 212453 93 CIM common schema object-oriented This document specifies a number of changes to the Policy Core Information Model (PCIM, RFC 3060). Two types of changes are included. First, several completely new elements are introduced, for example, classes for header filtering, that extend PCIM into areas that it did not previously cover. Second, there are cases where elements of PCIM (for example, policy rule priorities) are deprecated, and replacement elements are defined (in this case, priorities tied to associations that refer to policy rules). Both types of changes are done in such a way that, to the extent possible, interoperability with implementations of the original PCIM model is preserved. This document updates RFC 3060. [STANDARDS TRACK] ietf-policy-pcim-ext-08 RFC3060 PROPOSED STANDARD PROPOSED STANDARD RFC3461 Simple Mail Transfer Protocol (SMTP) Service Extension for Delivery Status Notifications (DSNs) K. Moore January 2003 ASCII 76076 38 SMTP-DSN simple mail transfer protocol This memo defines an extension to the Simple Mail Transfer Protocol (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] moore-rfc1891bis-02 RFC1891 RFC3798 RFC3885 DRAFT STANDARD DRAFT STANDARD RFC3462 The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages G. Vaudreuil January 2003 ASCII 12186 7 MIME-RPT Multipurpose Internet Mail Extensions The Multipart/Report Multipurpose Internet Mail Extensions (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. This document is part of a four document set describing the delivery status report service. This collection includes the Simple Mail Transfer Protocol (SMTP) extensions to request delivery status reports, a MIME content for the reporting of delivery reports, an enumeration of extended status codes, and a multipart container for the delivery report, the original message, and a human-friendly summary of the failure. [STANDARDS TRACK] vaudreuil-1892bis-02 RFC1892 DRAFT STANDARD DRAFT STANDARD RFC3463 Enhanced Mail System Status Codes G. Vaudreuil January 2003 ASCII 31832 16 EMS-CODE simple mail transfer protocol SMTP This document defines a set of extended status codes for use within the mail system for delivery status reports, tracking, and improved diagnostics. In combination with other information provided in the Delivery Status Notification (DSN) delivery report, these codes facilitate media and language independent rendering of message delivery status. [STANDARDS TRACK] vaudreuil-1893bis-03 RFC1893 RFC3886 DRAFT STANDARD DRAFT STANDARD RFC3464 An Extensible Message Format for Delivery Status Notifications K. Moore G. Vaudreuil January 2003 ASCII 83060 40 DSN Multipurpose Internet Mail Extensions Content Type This memo defines a Multipurpose Internet Mail Extensions (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 in Internet electronic mail. Because many messages are sent between the Internet and other messaging systems (such as X.400 or the so-called "Local Area Network (LAN)-based" systems), the Delivery Status Notification (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. [STANDARDS TRACK] vaudreuil-1894bis-02 RFC1894 DRAFT STANDARD DRAFT STANDARD RFC3465 TCP Congestion Control with Appropriate Byte Counting (ABC) M. Allman February 2003 ASCII 23486 10 transmission control protocol security performance This document proposes a small modification to the way TCP increases its congestion window. Rather than the traditional method of increasing the congestion window by a constant amount for each arriving acknowledgment, the document suggests basing the increase on the number of previously unacknowledged bytes each ACK covers. This change improves the performance of TCP, as well as closes a security hole TCP receivers can use to induce the sender into increasing the sending rate too rapidly. This memo defines an Experimental Protocol for the Internet community. allman-tcp-abc-04 EXPERIMENTAL EXPERIMENTAL RFC3466 A Model for Content Internetworking (CDI) M. Day B. Cain G. Tomlinson P. Rzewski February 2003 ASCII 37684 17 distribution peering Content (distribution) internetworking (CDI) is the technology for interconnecting content networks, sometimes previously called "content peering" or "CDN peering". A common vocabulary helps the process of discussing such interconnection and interoperation. This document introduces content networks and content internetworking, and defines elements for such a common vocabulary. This memo provides information for the Internet community. ietf-cdi-model-02 INFORMATIONAL INFORMATIONAL RFC3467 Role of the Domain Name System (DNS) J. Klensin February 2003 ASCII 84570 31 history internationalization unicode ascii multilingual names This document reviews the original function and purpose of the domain name system (DNS). It contrasts that history with some of the purposes for which the DNS has recently been applied and some of the newer demands being placed upon it or suggested for it. A framework for an alternative to placing these additional stresses on the DNS is then outlined. This document and that framework are not a proposed solution, only a strong suggestion that the time has come to begin thinking more broadly about the problems we are encountering and possible approaches to solving them. This memo provides information for the Internet community. klensin-dns-role-03 INFORMATIONAL INFORMATIONAL RFC3468 The Multiprotocol Label Switching (MPLS) Working Group decision on MPLS signaling protocols L. Andersson G. Swallow February 2003 ASCII 22072 11 rsvp-te ldp resource reservation protocol label distribution This document documents the consensus reached by the Multiprotocol Label Switching (MPLS) Working Group within the IETF to focus its efforts on "Resource Reservation Protocol (RSVP)-TE: Extensions to RSVP for Label- Switched Paths (LSP) Tunnels" (RFC 3209) as the MPLS signalling protocol for traffic engineering applications and to undertake no new efforts relating to "Constraint-Based LSP Setup using Label Distribution Protocol (LDP)" (RFC 3212). The recommendations of section 6 have been accepted by the IESG. This memo provides information for the Internet community. andersson-mpls-sig-decision-03 RFC3212 RFC3472 RFC3475 RFC3476 INFORMATIONAL INFORMATIONAL RFC3469 Framework for Multi-Protocol Label Switching (MPLS)-based Recovery V. Sharma Editor F. Hellstrand Editor February 2003 ASCII 89331 40 routing traffic Multi-protocol label switching (MPLS) integrates the label swapping forwarding paradigm with network layer routing. To deliver reliable service, MPLS requires a set of procedures to provide protection of the traffic carried on different paths. This requires that the label switching routers (LSRs) support fault detection, fault notification, and fault recovery mechanisms, and that MPLS signaling support the configuration of recovery. With these objectives in mind, this document specifies a framework for MPLS based recovery. Restart issues are not included in this framework. This memo provides information for the Internet community. ietf-mpls-recovery-frmwrk-08 INFORMATIONAL INFORMATIONAL RFC3470 Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols S. Hollenbeck M. Rose L. Masinter January 2003 ASCII 64252 28 data documents structure The Extensible Markup Language (XML) is a framework for structuring data. While it evolved from Standard Generalized Markup Language (SGML) -- a markup language primarily focused on structuring documents -- XML has evolved to be a widely-used mechanism for representing structured data. There are a wide variety of Internet protocols being developed; many have need for a representation for structured data relevant to their application. There has been much interest in the use of XML as a representation method. This document describes basic XML concepts, analyzes various alternatives in the use of XML, and provides guidelines for the use of XML within IETF standards-track protocols. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. hollenbeck-ietf-xml-guidelines-07 BCP0070 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3471 Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description L. Berger Editor January 2003 ASCII 72105 34 mpls sonet/sdh This document describes extensions to Multi-Protocol Label Switching (MPLS) signaling required to support Generalized MPLS. Generalized MPLS extends the MPLS control plane to encompass time-division (e.g., Synchronous Optical Network and Synchronous Digital Hierarchy, SONET/SDH), wavelength (optical lambdas) and spatial switching (e.g., incoming port or fiber to outgoing port or fiber). This document presents a functional description of the extensions. Protocol specific formats and mechanisms, and technology specific details are specified in separate documents. [STANDARDS TRACK] ietf-mpls-generalized-signaling-09 PROPOSED STANDARD PROPOSED STANDARD RFC3472 Generalized Multi-Protocol Label Switching (GMPLS) Signaling Constraint-based Routed Label Distribution Protocol (CR-LDP) Extensions P. Ashwood-Smith Editor L. Berger Editor January 2003 ASCII 49006 23 mpls sonet/sdh This document describes extensions to Multi-Protocol Label Switching (MPLS) Constraint-based Routed Label Distribution Protocol (CR-LDP) signaling required to support Generalized MPLS. Generalized MPLS extends the MPLS control plane to encompass time-division (e.g., Synchronous Optical Network and Synchronous Digital Hierarchy, SONET/SDH), wavelength (optical lambdas) and spatial switching (e.g., incoming port or fiber to outgoing port or fiber). This document presents a CR-LDP specific description of the extensions. A generic functional description can be found in separate documents. [STANDARDS TRACK] ietf-mpls-generalized-cr-ldp-07 RFC3468 PROPOSED STANDARD PROPOSED STANDARD RFC3473 Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions L. Berger Editor January 2003 ASCII 91808 42 mpls sonet/sdh This document describes extensions to Multi-Protocol Label Switching (MPLS) Resource ReserVation Protocol - Traffic Engineering (RSVP-TE) signaling required to support Generalized MPLS. Generalized MPLS extends the MPLS control plane to encompass time-division (e.g., Synchronous Optical Network and Synchronous Digital Hierarchy, SONET/SDH), wavelength (optical lambdas) and spatial switching (e.g., incoming port or fiber to outgoing port or fiber). This document presents a RSVP-TE specific description of the extensions. A generic functional description can be found in separate documents. [STANDARDS TRACK] ietf-mpls-generalized-rsvp-te-09 RFC4003 PROPOSED STANDARD PROPOSED STANDARD RFC3474 Documentation of IANA assignments for Generalized MultiProtocol Label Switching (GMPLS) Resource Reservation Protocol - Traffic Engineering (RSVP-TE) Usage and Extensions for Automatically Switched Optical Network (ASON) Z. Lin D. Pendarakis March 2003 ASCII 52551 25 sonet sdh The Generalized MultiProtocol Label Switching (GMPLS) suite of protocol specifications has been defined to provide support for different technologies as well as different applications. These include support for requesting TDM connections based on Synchronous Optical NETwork/Synchronous Digital Hierarchy (SONET/SDH) as well as Optical Transport Networks (OTNs). This document concentrates on the signaling aspects of the GMPLS suite of protocols, specifically GMPLS signaling using Resource Reservation Protocol - Traffic Engineering (RSVP-TE). It proposes additional extensions to these signaling protocols to support the capabilities of an ASON network. This document proposes appropriate extensions towards the resolution of additional requirements identified and communicated by the ITU-T Study Group 15 in support of ITU's ASON standardization effort. This memo provides information for the Internet community. lin-ccamp-gmpls-ason-rsvpte-04 INFORMATIONAL INFORMATIONAL RFC3475 Documentation of IANA assignments for Constraint-Based LSP setup using LDP (CR-LDP) Extensions for Automatic Switched Optical Network (ASON) O. Aboul-Magd March 2003 ASCII 29995 13 label switching protocol itu-t Automatic Switched Optical Network (ASON) is an architecture, specified by ITU-T Study Group 15, for the introduction of a control plane for optical networks. The ASON architecture specifies a set of reference points that defines the relationship between the ASON architectural entities. Signaling over interfaces defined in those reference points can make use of protocols that are defined by the IETF in the context of Generalized Multi-Protocol Label Switching (GMPLS) work. This document describes Constraint-Based LSP setup using LDP (CR-LDP) extensions for signaling over the interfaces defined in the ASON reference points. The purpose of the document is to request that the IANA assigns code points necessary for the CR-LDP extensions. The protocol specifications for the use of the CR-LDP extensions are found in ITU-T documents. This memo provides information for the Internet community. aboulmagd-ccamp-crldp-ason-ext-02 RFC3468 INFORMATIONAL INFORMATIONAL RFC3476 Documentation of IANA Assignments for Label Distribution Protocol (LDP), Resource ReSerVation Protocol (RSVP), and Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE) Extensions for Optical UNI Signaling B. Rajagopalan March 2003 ASCII 22009 11 oif optical interworking forum uni user network interface The Optical Interworking Forum (OIF) has defined extensions to the Label Distribution Protocol (LDP) and the Resource ReSerVation Protocol (RSVP) for optical User Network Interface (UNI) signaling. These extensions consist of a set of new data objects and error codes. This document describes these extensions. This memo provides information for the Internet community. bala-uni-ldp-rsvp-extensions-04 RFC3468 INFORMATIONAL INFORMATIONAL RFC3477 Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE) K. Kompella Y. Rekhter January 2003 ASCII 19899 9 mpls-te traffic engineering Current signalling used by Multi-Protocol Label Switching Traffic Engineering (MPLS TE) does not provide support for unnumbered links. This document defines procedures and extensions to Resource ReSerVation Protocol (RSVP) for Label Switched Path (LSP) Tunnels (RSVP-TE), one of the MPLS TE signalling protocols, that are needed in order to support unnumbered links. [STANDARDS TRACK] ietf-mpls-rsvp-unnum-08 PROPOSED STANDARD PROPOSED STANDARD RFC3478 Graceful Restart Mechanism for Label Distribution Protocol M. Leelanivas Y. Rekhter R. Aggarwal February 2003 ASCII 29248 12 ldp mpls This document describes a mechanism that helps to minimize the negative effects on MPLS traffic caused by Label Switching Router's (LSR's) control plane restart, specifically by the restart of its Label Distribution Protocol (LDP) component, on LSRs that are capable of preserving the MPLS forwarding component across the restart. The mechanism described in this document is applicable to all LSRs, both those with the ability to preserve forwarding state during LDP restart and those without (although the latter needs to implement only a subset of the mechanism described in this document). Supporting (a subset of) the mechanism described here by the LSRs that can not preserve their MPLS forwarding state across the restart would not reduce the negative impact on MPLS traffic caused by their control plane restart, but it would minimize the impact if their neighbor(s) are capable of preserving the forwarding state across the restart of their control plane and implement the mechanism described here. The mechanism makes minimalistic assumptions on what has to be preserved across restart - the mechanism assumes that only the actual MPLS forwarding state has to be preserved; the mechanism does not require any of the LDP-related states to be preserved across the restart. The procedures described in this document apply to downstream unsolicited label distribution. Extending these procedures to downstream on demand label distribution is for further study. [STANDARDS TRACK] ietf-mpls-ldp-restart-06 PROPOSED STANDARD PROPOSED STANDARD RFC3479 Fault Tolerance for the Label Distribution Protocol (LDP) A. Farrel Editor February 2003 ASCII 115778 52 mpls multiprotocol label switching cr-ldp high availability restart Multiprotocol Label Switching (MPLS) systems will be used in core networks where system downtime must be kept to an absolute minimum. Many MPLS Label Switching Routers (LSRs) may, therefore, exploit Fault Tolerant (FT) hardware or software to provide high availability of the core networks. The details of how FT is achieved for the various components of an FT LSR, including Label Distribution Protocol (LDP), the switching hardware and TCP, are implementation specific. This document identifies issues in the LDP specification in RFC 3036, "LDP Specification", that make it difficult to implement an FT LSR using the current LDP protocols, and defines enhancements to the LDP specification to ease such FT LSR implementations. The issues and extensions described here are equally applicable to RFC 3212, "Constraint-Based LSP Setup Using LDP" (CR-LDP). [STANDARDS TRACK] ietf-mpls-ldp-ft-06 PROPOSED STANDARD PROPOSED STANDARD RFC3480 Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol) K. Kompella Y. Rekhter A. Kullberg February 2003 ASCII 17076 8 mpls multiprotocol label switching traffic engineering mpls-te Current signalling used by Multi-Protocol Label Switching Traffic Engineering (MPLS TE) does not provide support for unnumbered links. This document defines procedures and extensions to Constraint-Routing Label Distribution Protocol (CR-LDP), one of the MPLS TE signalling protocols that are needed in order to support unnumbered links. [STANDARDS TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC3481 TCP over Second (2.5G) and Third (3G) Generation Wireless Networks H. Inamura Editor G. Montenegro Editor R. Ludwig A. Gurtov F. Khafizov February 2003 ASCII 61528 26 paths algorithm stacks This document describes a profile for optimizing TCP to adapt so that it handles paths including second (2.5G) and third (3G) generation wireless networks. It describes the relevant characteristics of 2.5G and 3G networks, and specific features of example deployments of such networks. It then recommends TCP algorithm choices for nodes known to be starting or ending on such paths, and it also discusses open issues. The configuration options recommended in this document are commonly found in modern TCP stacks, and are widely available standards-track mechanisms that the community considers safe for use on the general Internet. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-pilc-2.5g3g-12 BCP0071 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3482 Number Portability in the Global Switched Telephone Network (GSTN): An Overview M. Foster T. McGarry J. Yu February 2003 ASCII 78552 30 e.164 telephony routing This document provides an overview of E.164 telephone number portability (NP) in the Global Switched Telephone Network (GSTN). NP is a regulatory imperative seeking to liberalize local telephony service competition, by enabling end-users to retain telephone numbers while changing service providers. NP changes the fundamental nature of a dialed E.164 number from a hierarchical physical routing address to a virtual address, thereby requiring the transparent translation of the later to the former. In addition, there are various regulatory constraints that establish relevant parameters for NP implementation, most of which are not network technology specific. Consequently, the implementation of NP behavior consistent with applicable regulatory constraints, as well as the need for interoperation with the existing GSTN NP implementations, are relevant topics for numerous areas of IP telephony works-in-progress with the IETF. This memo provides information for the Internet community. ietf-enum-e164-gstn-np-05 INFORMATIONAL INFORMATIONAL RFC3483 Framework for Policy Usage Feedback for Common Open Policy Service with Policy Provisioning (COPS-PR) D. Rawlins A. Kulkarni M. Bokaemper K. Chan March 2003 ASCII 19869 10 accounting policy decision point bdp Common Open Policy Services (COPS) Protocol (RFC 2748), defines the capability of reporting information to the Policy Decision Point (PDP). The types of report information are success, failure and accounting of an installed state. This document focuses on the COPS Report Type of Accounting and the necessary framework for the monitoring and reporting of usage feedback for an installed state. This memo provides information for the Internet community. ietf-rap-feedback-frwk-04 INFORMATIONAL INFORMATIONAL RFC3484 Default Address Selection for Internet Protocol version 6 (IPv6) R. Draves February 2003 ASCII 55076 24 source address destination This document describes two algorithms, for source address selection and for destination address selection. The algorithms specify default behavior for all Internet Protocol version 6 (IPv6) implementations. They do not override choices made by applications or upper-layer protocols, nor do they preclude the development of more advanced mechanisms for address selection. The two algorithms share a common context, including an optional mechanism for allowing administrators to provide policy that can override the default behavior. In dual stack implementations, the destination address selection algorithm can consider both IPv4 and IPv6 addresses - depending on the available source addresses, the algorithm might prefer IPv6 addresses over IPv4 addresses, or vice-versa. All IPv6 nodes, including both hosts and routers, must implement default address selection as defined in this specification. [STANDARDS TRACK] ietf-ipv6-default-addr-select-09 PROPOSED STANDARD PROPOSED STANDARD RFC3485 The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp) M. Garcia-Martin C. Bormann J. Ott R. Price A. B. Roach February 2003 ASCII 80195 30 algorithm The Session Initiation Protocol (SIP) is a text-based protocol for initiating and managing communication sessions. The protocol can be compressed by using Signaling Compression (SigComp). Similarly, the Session Description Protocol (SDP) is a text-based protocol intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. This memo defines the SIP/SDP-specific static dictionary that SigComp may use in order to achieve higher efficiency. The dictionary is compression algorithm independent. [STANDARDS TRACK] ietf-sipping-sigcomp-sip-dictionary-05 PROPOSED STANDARD PROPOSED STANDARD RFC3486 Compressing the Session Initiation Protocol (SIP) G. Camarillo February 2003 ASCII 24181 12 This document describes a mechanism to signal that compression is desired for one or more Session Initiation Protocol (SIP) messages. It also states when it is appropriate to send compressed SIP messages to a SIP entity. [STANDARDS TRACK] ietf-sip-compression-02 PROPOSED STANDARD PROPOSED STANDARD RFC3487 Requirements for Resource Priority Mechanisms for the Session Initiation Protocol (SIP) H. Schulzrinne February 2003 ASCII 39615 17 circuit switched network resources end system resources proxy resources emergency preparedness communications This document summarizes requirements for prioritizing access to circuit-switched network, end system and proxy resources for emergency preparedness communications using the Session Initiation Protocol (SIP). This memo provides information for the Internet community. ietf-ieprep-sip-reqs-03 INFORMATIONAL INFORMATIONAL RFC3488 Cisco Systems Router-port Group Management Protocol (RGMP) I. Wu T. Eckert February 2003 ASCII 37152 17 multicast switches packet This document describes the Router-port Group Management Protocol (RGMP). This protocol was developed by Cisco Systems and is used between multicast routers and switches to restrict multicast packet forwarding in switches to those routers where the packets may be needed. RGMP is designed for backbone switched networks where multiple, high speed routers are interconnected. This memo provides information for the Internet community. wu-rgmp-01 INFORMATIONAL INFORMATIONAL RFC3489 STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs) J. Rosenberg J. Weinberger C. Huitema R. Mahy March 2003 ASCII 117562 47 lightweight applications firewalls Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs) (STUN) is a lightweight protocol that allows applications to discover the presence and types of NATs and firewalls between them and the public Internet. It also provides the ability for applications to determine the public Internet Protocol (IP) addresses allocated to them by the NAT. STUN works with many existing NATs, and does not require any special behavior from them. As a result, it allows a wide variety of applications to work through existing NAT infrastructure. [STANDARDS TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC3490 Internationalizing Domain Names in Applications (IDNA) P. Faltstrom P. Hoffman A. Costello March 2003 ASCII 51943 22 idn ascii characters Until now, there has been no standard method for domain names to use characters outside the ASCII repertoire. This document defines internationalized domain names (IDNs) and a mechanism called Internationalizing Domain Names in Applications (IDNA) for handling them in a standard fashion. IDNs use characters drawn from a large repertoire (Unicode), but IDNA allows the non-ASCII characters to be represented using only the ASCII characters already allowed in so-called host names today. This backward-compatible representation is required in existing protocols like DNS, so that IDNs can be introduced with no changes to the existing infrastructure. IDNA is only meant for processing domain names, not free text. [STANDARDS TRACK] ietf-idn-idna-14 PROPOSED STANDARD PROPOSED STANDARD RFC3491 Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN) P. Hoffman M. Blanchet March 2003 ASCII 10316 7 idna applications This document describes how to prepare internationalized domain name (IDN) labels in order to increase the likelihood that name input and name comparison work in ways that make sense for typical users throughout the world. This profile of the stringprep protocol is used as part of a suite of on-the-wire protocols for internationalizing the Domain Name System (DNS). [STANDARDS TRACK] ietf-idn-nameprep-11 PROPOSED STANDARD PROPOSED STANDARD RFC3492 Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA) A. Costello March 2003 ASCII 67439 35 syntax string host label Punycode is a simple and efficient transfer encoding syntax designed for use with Internationalized Domain Names in Applications (IDNA). It uniquely and reversibly transforms a Unicode string into an ASCII string. ASCII characters in the Unicode string are represented literally, and non-ASCII characters are represented by ASCII characters that are allowed in host name labels (letters, digits, and hyphens). This document defines a general algorithm called Bootstring that allows a string of basic code points to uniquely represent any string of code points drawn from a larger set. Punycode is an instance of Bootstring that uses particular parameter values specified by this document, appropriate for IDNA. [STANDARDS TRACK] ietf-idn-punycode-03 PROPOSED STANDARD PROPOSED STANDARD RFC3493 Basic Socket Interface Extensions for IPv6 R. Gilligan S. Thomson J. Bound J. McCann W. Stevens February 2003 ASCII 82570 39 internet protocol api application program interface tcp transmission control 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 support IPv6 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 by TCP 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. This memo provides information for the Internet community. RFC2553 INFORMATIONAL INFORMATIONAL RFC3494 Lightweight Directory Access Protocol version 2 (LDAPv2) to Historic Status K. Zeilenga March 2003 ASCII 9225 5 DAP interactive access X.500 LDAP lightweight directory protocol STR-REP directory names representing names This document recommends the retirement of version 2 of the Lightweight Directory Access Protocol (LDAPv2) and other dependent specifications, and discusses the reasons for doing so. This document recommends RFC 1777, 1778, 1779, 1781, and 2559 (as well as documents they superseded) be moved to Historic status. This memo provides information for the Internet community. zeilenga-ldapv2-04 RFC1484 RFC1485 RFC1487 RFC1777 RFC1778 RFC1779 RFC1781 RFC2559 INFORMATIONAL INFORMATIONAL RFC3495 Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration B. Beser P. Duffy Editor March 2003 ASCII 26817 13 packetcable media terminal adapter mta This document defines a Dynamic Host Configuration Protocol (DHCP) option that will be used to configure various devices deployed within CableLabs architectures. Specifically, the document describes DHCP option content that will be used to configure one class of CableLabs client device: a PacketCable Media Terminal Adapter (MTA). The option content defined within this document will be extended as future CableLabs client devices are developed. [STANDARDS TRACK] ietf-dhc-packetable-06 PROPOSED STANDARD PROPOSED STANDARD RFC3496 Protocol Extension for Support of Asynchronous Transfer Mode (ATM) Service Class-aware Multiprotocol Label Switching (MPLS) Traffic Engineering A. G. Malis T. Hsiao March 2003 ASCII 11431 6 diff-serv diffserv rsvp-te resource reservation protocol This document specifies a Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE) signaling extension for support of Asynchronous Transfer Mode (ATM) Service Class-aware Multiprotocol Label Switching (MPLS) Traffic Engineering. This memo provides information for the Internet community. malis-diff-te-serviceclass-04 INFORMATIONAL INFORMATIONAL RFC3497 RTP Payload Format for Society of Motion Picture and Television Engineers (SMPTE) 292M Video L. Gharai C. Perkins G. Goncher A. Mankin March 2003 ASCII 26094 12 real-time transport protocol hdtv high definition television This memo specifies an RTP payload format for encapsulating uncompressed High Definition Television (HDTV) as defined by the Society of Motion Picture and Television Engineers (SMPTE) standard, SMPTE 292M. SMPTE is the main standardizing body in the motion imaging industry and the SMPTE 292M standard defines a bit-serial digital interface for local area HDTV transport. [STANDARDS TRACK] ietf-avt-smpte292-video-08 PROPOSED STANDARD PROPOSED STANDARD RFC3498 Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) Architectures J. Kuhfeld J. Johnson M. Thatcher March 2003 ASCII 78701 43 mib management information base tcp/ip transmission control protocol internet protocol This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for managing networks using Synchronous Optical Network (SONET) linear Automatic Protection Switching (APS) architectures. [STANDARDS TRACK] ietf-atommib-sonetaps-mib-10 PROPOSED STANDARD PROPOSED STANDARD RFC3499 Request for Comments Summary RFC Numbers 3400-3499 S. Ginoza December 2003 ASCII 88033 38 INFORMATIONAL INFORMATIONAL RFC3500 RFC3501 INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 M. Crispin March 2003 ASCII 227640 108 IMAPv4 imap imapv4rev1 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 mailboxes (remote message folders) in a way that is functionally equivalent to local folders. IMAP4rev1 also provides the capability for an offline client to resynchronize with the server. IMAP4rev1 includes operations for creating, deleting, and renaming mailboxes, checking for new messages, permanently removing messages, setting and clearing flags, RFC 2822 and RFC 2045 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 RFC 2244. IMAP4rev1 does not specify a means of posting mail; this function is handled by a mail transfer protocol such as RFC 2821. [STANDARDS TRACK] crispin-imapv-20 RFC2060 PROPOSED STANDARD PROPOSED STANDARD RFC3502 Internet Message Access Protocol (IMAP) - MULTIAPPEND Extension M. Crispin March 2003 ASCII 13379 7 IMAPv4 imap imapv4rev1 This document describes the multiappending extension to the Internet Message Access Protocol (IMAP) (RFC 3501). This extension provides substantial performance improvements for IMAP clients which upload multiple messages at a time to a mailbox on the server. A server which supports this extension indicates this with a capability name of "MULTIAPPEND". [STANDARDS TRACK] crispin-imap-multiappend-07 PROPOSED STANDARD PROPOSED STANDARD RFC3503 Message Disposition Notification (MDN) profile for Internet Message Access Protocol (IMAP) A. Melnikov March 2003 ASCII 16937 9 mua mail user agent imap4 The Message Disposition Notification (MDN) facility defined in RFC 2298 provides a means by which a message can request that message processing by the recipient be acknowledged as well as a format to be used for such acknowledgements. However, it doesn't describe how multiple Mail User Agents (MUAs) should handle the generation of MDNs in an Internet Message Access Protocol (IMAP4) environment. This document describes how to handle MDNs in such an environment and provides guidelines for implementers of IMAP4 that want to add MDN support to their products. [STANDARDS TRACK] melnikov-imap-mdn-05 PROPOSED STANDARD PROPOSED STANDARD RFC3504 Internet Open Trading Protocol (IOTP) Version 1, Errata D. Eastlake March 2003 ASCII 8655 6 commerce payment system merchant system xml extensible markup language security Since the publication of the RFCs specifying Version 1.0 of the Internet Open Trading Protocol (IOTP), some errors have been noted. This informational document lists these errors and provides corrections for them. This memo provides information for the Internet community. ietf-trade-iotp-v1-errata-01 INFORMATIONAL INFORMATIONAL RFC3505 Electronic Commerce Modeling Language (ECML): Version 2 Requirements D. Eastlake March 2003 ASCII 13915 8 xml extensible markup language This document lists the design principles, scope, and requirements for the Electronic Commerce Modeling Language (ECML) version 2 specification. It includes requirements as they relate to Extensible Markup Language (XML) syntax, data model, format, and payment processing. This memo provides information for the Internet community. ietf-trade-ecml2-req-05 INFORMATIONAL INFORMATIONAL RFC3506 Requirements and Design for Voucher Trading System (VTS) K. Fujimura D. Eastlake March 2003 ASCII 30945 15 generic voucher language gvl Crediting loyalty points and collecting digital coupons or gift certificates are common functions in purchasing and trading transactions. These activities can be generalized using the concept of a "voucher", which is a digital representation of the right to claim goods or services. This document presents a Voucher Trading System (VTS) that circulates vouchers securely and its terminology; it lists design principles and requirements for VTS and the Generic Voucher Language (GVL), with which diverse types of vouchers can be described. This memo provides information for the Internet community. ietf-trade-drt-requirements-04 INFORMATIONAL INFORMATIONAL RFC3507 Internet Content Adaptation Protocol (ICAP) J. Elson A. Cerpa April 2003 ASCII 98772 49 http hyper-text markup protocol request response client server ICAP, the Internet Content Adaption Protocol, is a protocol aimed at providing simple object-based content vectoring for HTTP services. ICAP is, in essence, a lightweight protocol for executing a "remote procedure call" on HTTP messages. It allows ICAP clients to pass HTTP messages to ICAP servers for some sort of transformation or other processing ("adaptation"). The server executes its transformation service on messages and sends back responses to the client, usually with modified messages. Typically, the adapted messages are either HTTP requests or HTTP responses. This memo provides information for the Internet community. elson-icap-00 INFORMATIONAL INFORMATIONAL RFC3508 H.323 Uniform Resource Locator (URL) Scheme Registration O. Levin April 2003 ASCII 10983 6 itu-t packet networks ITU-T Recommendation H.323 version 4 introduced an H.323-specific Uniform Resource Locator (URL). This document reproduces the H323-URL definition found in H.323, and is published as an RFC for ease of access and registration with the Internet Assigned Numbers Authority (IANA). This memo provides information for the Internet community. levin-iptel-h323-url-scheme-05 INFORMATIONAL INFORMATIONAL RFC3509 Alternative Implementations of OSPF Area Border Routers A. Zinin A. Lindem D. Yeung April 2003 ASCII 24326 12 traffic backbone Open Shortest Path First (OSPF) is a link-state intra-domain routing protocol used for routing in IP networks. Though the definition of the Area Border Router (ABR) in the OSPF specification does not require a router with multiple attached areas to have a backbone connection, it is actually necessary to provide successful routing to the inter-area and external destinations. If this requirement is not met, all traffic destined for the areas not connected to such an ABR or out of the OSPF domain, is dropped. This document describes alternative ABR behaviors implemented in Cisco and IBM routers. This memo provides information for the Internet community. ietf-ospf-abr-alt-05 INFORMATIONAL INFORMATIONAL RFC3510 Internet Printing Protocol/1.1: IPP URL Scheme R. Herriot I. McDonald April 2003 ASCII 22009 16 IPP-E-T IPP application media-type media type This memo defines the "ipp" URL (Uniform Resource Locator) scheme. This memo updates IPP/1.1: Encoding and Transport (RFC 2910), by expanding and clarifying Section 5, "IPP URL Scheme", of RFC 2910. An "ipp" URL is used to specify the network location of a print service that supports the IPP Protocol (RFC 2910), or of a network resource (for example, a print job) managed by such a print service. [STANDARDS TRACK] ietf-ipp-url-scheme-05 RFC2910 PROPOSED STANDARD PROPOSED STANDARD RFC3511 Benchmarking Methodology for Firewall Performance B. Hickman D. Newman S. Tadjudin T. Martin April 2003 ASCII 67916 34 client server traffic authentication web caching This document discusses and defines a number of tests that may be used to describe the performance characteristics of firewalls. In addition to defining the tests, this document also describes specific formats for reporting the results of the tests. This document is a product of the Benchmarking Methodology Working Group (BMWG) of the Internet Engineering Task Force (IETF). This memo provides information for the Internet community. ietf-bmwg-firewall-08 INFORMATIONAL INFORMATIONAL RFC3512 Configuring Networks and Devices with Simple Network Management Protocol (SNMP) M. MacFaden D. Partain J. Saperia W. Tackabury April 2003 ASCII 196529 83 internet standard framework This document is written for readers interested in the Internet Standard Management Framework and its protocol, the Simple Network Management Protocol (SNMP). In particular, it offers guidance in the effective use of SNMP for configuration management. This information is relevant to vendors that build network elements, management application developers, and those that acquire and deploy this technology in their networks. This memo provides information for the Internet community. ietf-snmpconf-bcp-12 INFORMATIONAL INFORMATIONAL RFC3513 Internet Protocol Version 6 (IPv6) Addressing Architecture R. Hinden S. Deering April 2003 ASCII 53920 26 internet protocol unicast anycast multicast node This specification defines the addressing architecture of the IP Version 6 (IPv6) protocol. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses. [STANDARDS TRACK] ietf-ipngwg-addr-arch-v3-11 RFC2373 PROPOSED STANDARD PROPOSED STANDARD RFC3514 The Security Flag in the IPv4 Header S. Bellovin April 01 2003 ASCII 11211 6 evil evil bit Firewalls, packet filters, intrusion detection systems, and the like often have difficulty distinguishing between packets that have malicious intent and those that are merely unusual. We define a security flag in the IPv4 header as a means of distinguishing the two cases. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC3515 The Session Initiation Protocol (SIP) Refer Method R. Sparks April 2003 ASCII 47788 23 resource request call transfer This document defines the REFER method. This Session Initiation Protocol (SIP) extension requests that the recipient REFER to a resource provided in the request. It provides a mechanism allowing the party sending the REFER to be notified of the outcome of the referenced request. This can be used to enable many applications, including call transfer. In addition to the REFER method, this document defines the refer event package and the Refer-To request header. [STANDARDS TRACK] ietf-sip-refer-07 PROPOSED STANDARD PROPOSED STANDARD RFC3516 IMAP4 Binary Content Extension L. Nerenberg April 2003 ASCII 14598 8 internet message acess procotol This memo defines the Binary extension to the Internet Message Access Protocol (IMAP4). It provides a mechanism for IMAP4 clients and servers to exchange message body data without using a MIME content-transfer- encoding. [STANDARDS TRACK] nerenberg-imap-binary-07 PROPOSED STANDARD PROPOSED STANDARD RFC3517 A Conservative Selective Acknowledgment (SACK)-based Loss Recovery Algorithm for TCP E. Blanton M. Allman K. Fall L. Wang April 2003 ASCII 27855 13 transmission control protocol retransmission congestion control This document presents a conservative loss recovery algorithm for TCP that is based on the use of the selective acknowledgment (SACK) TCP option. The algorithm presented in this document conforms to the spirit of the current congestion control specification (RFC 2581), but allows TCP senders to recover more effectively when multiple segments are lost from a single flight of data. [STANDARDS TRACK] allman-tcp-sack-13 PROPOSED STANDARD PROPOSED STANDARD RFC3518 Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP) M. Higashiyama F. Baker T. Liao April 2003 ASCII 82102 40 PPP-BCP point-to-point datagrams network The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol (LCP) and proposes a family of Network Control Protocols (NCP) for establishing and configuring different network-layer protocols. This document defines the NCP for establishing and configuring Remote Bridging for PPP links. This document obsoletes RFC 2878, which was based on the IEEE 802.1D- 1993 MAC Bridge. This document extends that specification by improving support for bridge control packets. [STANDARDS TRACK] ietf-pppext-rfc2878bis-01 RFC2878 PROPOSED STANDARD PROPOSED STANDARD RFC3519 Mobile IP Traversal of Network Address Translation (NAT) Devices H. Levkowetz S. Vaarala May 2003 ASCII 80522 34 Internet Protocol datagram traffic Mobile IP NAT NAPT traversal tunnelling tunneling UDP private address space keepalives port 434 MIP MIPv4 network address translation Mobile IP's datagram tunnelling is incompatible with Network Address Translation (NAT). This document presents extensions to the Mobile IP protocol and a tunnelling method which permits mobile nodes using Mobile IP to operate in private address networks which are separated from the public internet by NAT devices. The NAT traversal is based on using the Mobile IP Home Agent UDP port for encapsulated data traffic. [STANDARDS TRACK] ietf-mobileip-nat-traversal-07 PROPOSED STANDARD PROPOSED STANDARD RFC3520 Session Authorization Policy Element L-N. Hamer B. Gage B. Kosinski H. Shieh April 2003 ASCII 63445 30 admission control resource reservation This document describes the representation of a session authorization policy element for supporting policy-based per-session authorization and admission control. The goal of session authorization is to allow the exchange of information between network elements in order to authorize the use of resources for a service and to co-ordinate actions between the signaling and transport planes. This document describes how a process on a system authorizes the reservation of resources by a host and then provides that host with a session authorization policy element which can be inserted into a resource reservation protocol (e.g., the Resource ReSerVation Protocol (RSVP) PATH message) to facilitate proper and secure reservation of those resources within the network. We describe the encoding of session authorization information as a policy element conforming to the format of a Policy Data object (RFC 2750) and provide details relating to operations, processing rules and error scenarios. [STANDARDS TRACK] ietf-rap-rsvp-authsession-04 PROPOSED STANDARD PROPOSED STANDARD RFC3521 Framework for Session Set-up with Media Authorization L-N. Hamer B. Gage H. Shieh April 2003 ASCII 59548 25 qos quality of service streams linkage policy control admission theft service resource reservation token Establishing multimedia streams must take into account requirements for end-to-end QoS, authorization of network resource usage and accurate accounting for resources used. During session set up, policies may be enforced to ensure that the media streams being requested lie within the bounds of the service profile established for the requesting host. Similarly, when a host requests resources to provide a certain QoS for a packet flow, policies may be enforced to ensure that the required resources lie within the bounds of the resource profile established for the requesting host. To prevent fraud and to ensure accurate billing, this document describes various scenarios and mechanisms that provide the linkage required to verify that the resources being used to provide a requested QoS are in- line with the media streams requested (and authorized) for the session. This memo provides information for the Internet community. ietf-rap-session-auth-04 INFORMATIONAL INFORMATIONAL RFC3522 The Eifel Detection Algorithm for TCP R. Ludwig M. Meyer April 2003 ASCII 33731 14 transmission control protocol loss recovery timestamps The Eifel detection algorithm allows a TCP sender to detect a posteriori whether it has entered loss recovery unnecessarily. It requires that the TCP Timestamps option defined in RFC 1323 be enabled for a connection. The Eifel detection algorithm makes use of the fact that the TCP Timestamps option eliminates the retransmission ambiguity in TCP. Based on the timestamp of the first acceptable ACK that arrives during loss recovery, it decides whether loss recovery was entered unnecessarily. The Eifel detection algorithm provides a basis for future TCP enhancements. This includes response algorithms to back out of loss recovery by restoring a TCP sender's congestion control state. This memo defines an Experimental Protocol for the Internet community. ietf-tsvwg-tcp-eifel-alg-07 EXPERIMENTAL EXPERIMENTAL RFC3523 Internet Emergency Preparedness (IEPREP) Telephony Topology Terminology J. Polk April 2003 ASCII 10190 6 naming convetions phone This document defines the topology naming conventions that are to be used in reference to Internet Emergency Preparedness (IEPREP) phone calls. These naming conventions should be used to focus the IEPREP Working Group during discussions and when writing requirements, gap analysis and other solutions documents. This memo provides information for the Internet community. polk-ieprep-scenarios-03 INFORMATIONAL INFORMATIONAL RFC3524 Mapping of Media Streams to Resource Reservation Flows G. Camarillo A. Monrad April 2003 ASCII 11249 6 sdp session description protocol srf single This document defines an extension to the Session Description Protocol (SDP) grouping framework. It allows requesting a group of media streams to be mapped into a single resource reservation flow. The SDP syntax needed is defined, as well as a new "semantics" attribute called Single Reservation Flow (SRF). [STANDARDS TRACK] ietf-mmusic-reservation-flows-01 PROPOSED STANDARD PROPOSED STANDARD RFC3525 Gateway Control Protocol Version 1 C. Groves M. Pantaleo T. Anderson T. Taylor Editors June 2003 ASCII 439674 213 MEGACO H.248 media gateway control This document defines the protocol used between elements of a physically decomposed multimedia gateway, i.e., a Media Gateway and a Media Gateway Controller. The protocol presented in this document meets the requirements for a media gateway control protocol as presented in RFC 2805. This document replaces RFC 3015. It is the result of continued cooperation between the IETF Megaco Working Group and ITU-T Study Group 16. It incorporates the original text of RFC 3015, modified by corrections and clarifications discussed on the Megaco E-mail list and incorporated into the Study Group 16 Implementor's Guide for Recommendation H.248. The present version of this document underwent ITU-T Last Call as Recommendation H.248 Amendment 1. Because of ITU-T renumbering, it was published by the ITU-T as Recommendation H.248.1 (03/2002), Gateway Control Protocol Version 1. Users of this specification are advised to consult the H.248 Sub-series Implementors' Guide at http://www.itu.int/itudoc/itu-t/com16/implgd for additional corrections and clarifications. [STANDARDS TRACK] ietf-megaco-3015corr-02 RFC3015 PROPOSED STANDARD PROPOSED STANDARD RFC3526 More Modular Exponential (MODP) Diffie-Hellman groups for Internet Key Exchange (IKE) T. Kivinen M. Kojo May 2003 ASCII 19166 10 bit groups This document defines new Modular Exponential (MODP) Groups for the Internet Key Exchange (IKE) protocol. It documents the well known and used 1536 bit group 5, and also defines new 2048, 3072, 4096, 6144, and 8192 bit Diffie-Hellman groups numbered starting at 14. The selection of the primes for theses groups follows the criteria established by Richard Schroeppel. [STANDARDS TRACK] ietf-ipsec-ike-modp-groups-05 PROPOSED STANDARD PROPOSED STANDARD RFC3527 Link Selection sub-option for the Relay Agent Information Option for DHCPv4 K. Kinnear M. Stapp R. Johnson J. Kumarasamy April 2003 ASCII 16831 9 dynamic host configuration protocol This document describes the link selection sub-option of the relay- agent-information option for the Dynamic Host Configuration Protocol (DHCPv4). The giaddr specifies an IP address which determines both a subnet, and thereby a link on which a Dynamic Host Configuration Protocol (DHCP) client resides as well as an IP address that can be used to communicate with the relay agent. The subnet-selection option allows the functions of the giaddr to be split so that when one entity is performing as a DHCP proxy, it can specify the subnet/link from which to allocate an IP address, which is different from the IP address with which it desires to communicate with the DHCP server. Analogous situations exist where the relay agent needs to specify the subnet/link on which a DHCP client resides, which is different from an IP address that can be used to communicate with the relay agent. [STANDARDS TRACK] ietf-dhc-agent-subnet-selection-04 PROPOSED STANDARD PROPOSED STANDARD RFC3528 Mesh-enhanced Service Location Protocol (mSLP) W. Zhao H. Schulzrinne E. Guttman April 2003 ASCII 35208 15 da directory agent slpda service agent sa slpv2 This document describes the Mesh-enhanced Service Location Protocol (mSLP). mSLP enhances the Service Location Protocol (SLP) with a scope-based fully-meshed peering Directory Agent (DA) architecture. Peer DAs exchange new service registrations in shared scopes via anti- entropy and direct forwarding. mSLP improves the reliability and consistency of SLP DA services, and simplifies Service Agent (SA) registrations in systems with multiple DAs. mSLP is backward compatible with SLPv2 and can be deployed incrementally. This memo defines an Experimental Protocol for the Internet community. zhao-slp-da-interaction-16 EXPERIMENTAL EXPERIMENTAL RFC3529 Using Extensible Markup Language-Remote Procedure Calling (XML-RPC) in Blocks Extensible Exchange Protocol (BEEP) W. Harold April 2003 ASCII 23314 15 format messages clients servers Markup Language-Remote Procedure Calling protocol that works over the Internet. It defines an XML format for messages that are transfered between clients and servers using HTTP. An XML-RPC message encodes either a procedure to be invoked by the server, along with the parameters to use in the invocation, or the result of an invocation. Procedure parameters and results can be scalars, numbers, strings, dates, etc.; they can also be complex record and list structures. This document specifies a how to use the Blocks Extensible Exchange Protocol (BEEP) to transfer messages encoded in the XML-RPC format between clients and servers. This memo defines an Experimental Protocol for the Internet community. harold-beep-xmlrpc-03 EXPERIMENTAL EXPERIMENTAL RFC3530 Network File System (NFS) version 4 Protocol S. Shepler B. Callaghan D. Robinson R. Thurlow C. Beame M. Eisler D. Noveck April 2003 ASCII 600988 275 NFSv4 network file system The Network File System (NFS) version 4 is a distributed filesystem protocol which owes heritage to NFS protocol version 2, RFC 1094, and version 3, RFC 1813. Unlike earlier versions, the NFS version 4 protocol supports traditional file access while integrating support for file locking and the mount protocol. In addition, support for strong security (and its negotiation), compound operations, client caching, and internationalization have been added. Of course, attention has been applied to making NFS version 4 operate well in an Internet environment. This document replaces RFC 3010 as the definition of the NFS version 4 protocol. [STANDARDS TRACK] ietf-nfsv4-rfc3010bis-04 RFC3010 PROPOSED STANDARD PROPOSED STANDARD RFC3531 A Flexible Method for Managing the Assignment of Bits of an IPv6 Address Block M. Blanchet April 2003 ASCII 11314 7 address plan addressing range space internet protocol This document proposes a method to manage the assignment of bits of an IPv6 address block or range. When an organisation needs to make an address plan for its subnets or when an ISP needs to make an address plan for its customers, this method enables the organisation to postpone the final decision on the number of bits to partition in the address space they have. It does it by keeping the bits around the borders of the partition to be free as long as possible. This scheme is applicable to any bits addressing scheme using bits with partitions in the space, but its first intended use is for IPv6. It is a generalization of RFC 1219 and can be used for IPv6 assignments. This memo provides information for the Internet community. ietf-ipb6-ipaddressassign-06 INFORMATIONAL INFORMATIONAL RFC3532 Requirements for the Dynamic Partitioning of Switching Elements T. Anderson J. Buerkle May 2003 ASCII 25119 11 atm asynchronous transfer mode This document identifies a set of requirements for the mechanisms used to dynamically reallocate the resources of a switching element (e.g., an ATM switch) to its partitions. These requirements are particularly critical in the case of an operator creating a switch partition and then leasing control of that partition to a third party. This memo provides information for the Internet community. ietf-gsmp-dyn-part-reqs-03 INFORMATIONAL INFORMATIONAL RFC3533 The Ogg Encapsulation Format Version 0 S. Pfeiffer May 2003 ASCII 32045 15 bitstream media streams video audio xiph.org multimedia media interleading format video bitstream packaging audio bitstream packaging free encapsulation format stream based storage of codec data framed bitstream This document describes the Ogg bitstream format version 0, which is a general, freely-available encapsulation format for media streams. It is able to encapsulate any kind and number of video and audio encoding formats as well as other data streams in a single bitstream. This memo provides information for the Internet community. This memo provides information for the Internet community. pfeiffer-ogg-fileformat-02 INFORMATIONAL INFORMATIONAL RFC3534 The application/ogg Media Type L. Walleij May 2003 ASCII 10013 6 mime multipurpose internet mail extenstions The Ogg Bitstream Format aims at becoming a general, freely-available standard for transporting multimedia content across computing platforms and networks. The intention of this document is to define the MIME media type application/ogg to refer to this kind of content when transported across the Internet. It is the intention of the Ogg Bitstream Format developers that it be usable without intellectual property concerns. [STANDARDS TRACK] walleij-ogg-mediatype-08 PROPOSED STANDARD PROPOSED STANDARD RFC3535 Overview of the 2002 IAB Network Management Workshop J. Schoenwaelder May 2003 ASCII 42566 20 Internet Architecture Board This document provides an overview of a workshop held by the Internet Architecture Board (IAB) on Network Management. The workshop was hosted by CNRI in Reston, VA, USA on June 4 thru June 6, 2002. The goal of the workshop was to continue the important dialog started between network operators and protocol developers, and to guide the IETFs focus on future work regarding network management. This report summarizes the discussions and lists the conclusions and recommendations to the Internet Engineering Task Force (IETF) community. This memo provides information for the Internet community. iab-nm-workshop-02 INFORMATIONAL INFORMATIONAL RFC3536 Terminology Used in Internationalization in the IETF P. Hoffman May 2003 ASCII 64284 30 internet engineering task force This document provides a glossary of terms used in the IETF when discussing internationalization. The purpose is to help frame discussions of internationalization in the various areas of the IETF and to help introduce the main concepts to IETF participants. This memo provides information for the Internet community. hoffman-i18n-terms-11 INFORMATIONAL INFORMATIONAL RFC3537 Wrapping a Hashed Message Authentication Code (HMAC) key with a Triple-Data Encryption Standard (DES) Key or an Advanced Encryption Standard (AES) Key J. Schaad R. Housley May 2003 ASCII 16885 9 This document defines two methods for wrapping an HMAC (Hashed Message Authentication Code) key. The first method defined uses a Triple DES (Data Encryption Standard) key to encrypt the HMAC key. The second method defined uses an AES (Advanced Encryption Standard) key to encrypt the HMAC key. One place that such an algorithm is used is for the Authenticated Data type in CMS (Cryptographic Message Syntax). [PROPOSED STANDARD] ietf-smime-hmac-key-wrap-02 PROPOSED STANDARD PROPOSED STANDARD RFC3538 Secure Electronic Transaction (SET) Supplement for the v1.0 Internet Open Trading Protocol (IOTP) Y. Kawatsura June 2003 ASCII 103475 56 payment input output parameter This document describes detailed Input/Output parameters for the Internet Open Trading Protocol (IOTP) Payment Application Programming Interface (API). It also describes procedures in the Payment Bridge for the use of SET (SET Secure Electronic Transaction) as the payment protocol within Version 1.0 of the IOTP. This memo provides information for the Internet community. ietf-trade-iotp-v1.0-set-02 INFORMATIONAL INFORMATIONAL RFC3539 Authentication, Authorization and Accounting (AAA) Transport Profile B. Aboba J. Wood June 2003 ASCII 93110 41 This document discusses transport issues that arise within protocols for Authentication, Authorization and Accounting (AAA). It also provides recommendations on the use of transport by AAA protocols. This includes usage of standards-track RFCs as well as experimental proposals. [STANDARDS TRACK] ietf-aaa-transport-09 PROPOSED STANDARD PROPOSED STANDARD RFC3540 Robust Explicit Congestion Notification (ECN) Signaling with Nonces N. Spring D. Wetherall D. Ely June 2003 ASCII 30081 13 congestion control tcp traffic control protocol This note describes the Explicit Congestion Notification (ECN)-nonce, an optional addition to ECN that protects against accidental or malicious concealment of marked packets from the TCP sender. It improves the robustness of congestion control by preventing receivers from exploiting ECN to gain an unfair share of network bandwidth. The ECN-nonce uses the two ECN-Capable Transport (ECT)codepoints in the ECN field of the IP header, and requires a flag in the TCP header. It is computationally efficient for both routers and hosts. This memo defines an Experimental Protocol for the Internet community. ietf-tsvwg-tcp-nonce-04 EXPERIMENTAL EXPERIMENTAL RFC3541 A Uniform Resource Name (URN) Namespace for the Web3D Consortium (Web3D) A. Walsh May 2003 ASCII 11358 6 virtual reality monitoring language vrml extensible markup language x3d xml dtd document type definition This document describes a Uniform Resource Name (URN) namespace for the Web3D Consortium (Web3D) for naming persistent resources such as technical documents and specifications, Virtual Reality Modeling Language (VRML) and Extensible 3D (X3D) files and resources, Extensible Markup Language (XML) Document Type Definitions (DTDs), XML Schemas, namespaces, style sheets, media assets, and other resources produced or managed by Web3D. This memo provides information for the Internet community. walsh-urn-web3d-00 INFORMATIONAL INFORMATIONAL RFC3542 Advanced Sockets Application Program Interface (API) for IPv6 W. Stevens M. Thomas E. Nordmark T. Jinmei May 2003 ASCII 173028 77 application program interface This document provides sockets Application Program Interface (API) to support "advanced" IPv6 applications, as a supplement to a separate specification, RFC 3493. The expected applications include Ping, Traceroute, routing daemons and the like, which typically use raw sockets to access IPv6 or ICMPv6 header fields. This document proposes some portable interfaces for applications that use raw sockets under IPv6. There are other features of IPv6 that some applications will need to access: interface identification (specifying the outgoing interface and determining the incoming interface), IPv6 extension headers, and path Maximum Transmission Unit (MTU) information. This document provides API access to these features too. Additionally, some extended interfaces to libraries for the "r" commands are defined. The extension will provide better backward compatibility to existing implementations that are not IPv6-capable. This memo provides information for the Internet community. ietf-ipngwg-rfc2292bis-09 RFC2292 INFORMATIONAL INFORMATIONAL RFC3543 Registration Revocation in Mobile IPv4 S. Glass M. Chandra August 2003 ASCII 81805 33 internet protocol This document defines a Mobile IPv4 Registration Revocation mechanism whereby a mobility agent involved in providing Mobile IP services to a mobile node can notify the other mobility agent providing Mobile IP services to the same mobile node of the termination of this registration. The mechanism is also usable by a home agent to notify a co-located mobile node of the termination of its binding as well. Moreover, the mechanism provides for this notification to be acknowledged. A signaling mechanism already defined by the Mobile IPv4 protocol is leveraged as a way to inform a mobile node of the revocation of its binding. [STANDARDS TRACK] ietf-mobileip-reg-revok-07 PROPOSED STANDARD PROPOSED STANDARD RFC3544 IP Header Compression over PPP M. Engan S. Casner C. Bormann T. Koren July 2003 ASCII 27627 14 IPCOM-PPP internet protocol point-to-point datagrams This document describes an option for negotiating the use of header compression on IP datagrams transmitted over the Point-to-Point Protocol (RFC 1661). It defines extensions to the PPP Control Protocols for IPv4 and IPv6 (RFC 1332, RFC 2472). Header compression may be applied to IPv4 and IPv6 datagrams in combination with TCP, UDP and RTP transport protocols as specified in RFC 2507, RFC 2508 and RFC 3545. [STANDARDS TRACK] koren-pppext-rfc2509bis-03 RFC2509 PROPOSED STANDARD PROPOSED STANDARD RFC3545 Enhanced Compressed RTP (CRTP) for Links with High Delay, Packet Loss and Reordering T. Koren S. Casner J. Geevarghese B. Thompson P. Ruddy July 2003 ASCII 48278 22 point to point header This document describes a header compression scheme for point to point links with packet loss and long delays. It is based on Compressed Real-time Transport Protocol (CRTP), the IP/UDP/RTP header compression described in RFC 2508. CRTP does not perform well on such links: packet loss results in context corruption and due to the long delay, many more packets are discarded before the context is repaired. To correct the behavior of CRTP over such links, a few extensions to the protocol are specified here. The extensions aim to reduce context corruption by changing the way the compressor updates the context at the decompressor: updates are repeated and include updates to full and differential context parameters. With these extensions, CRTP performs well over links with packet loss, packet reordering and long delays. [STANDARDS TRACK] ietf-avt-crtp-enhance-07 PROPOSED STANDARD PROPOSED STANDARD RFC3546 Transport Layer Security (TLS) Extensions S. Blake-Wilson M. Nystrom D. Hopwood J. Mikkelsen T. Wright June 2003 ASCII 63437 29 transport protocol layer authentication privacy This document describes extensions that may be used to add functionality to Transport Layer Security (TLS). It provides both generic extension mechanisms for the TLS handshake client and server hellos, and specific extensions using these generic mechanisms. The extensions may be used by TLS clients and servers. The extensions are backwards compatible - communication is possible between TLS 1.0 clients that support the extensions and TLS 1.0 servers that do not support the extensions, and vice versa. [STANDARDS TRACK] ietf-tls-extensions-06 RFC2246 PROPOSED STANDARD PROPOSED STANDARD RFC3547 The Group Domain of Interpretation M. Baugher B. Weis T. Hardjono H. Harney July 2003 ASCII 108901 48 isamkp doi key management security encryption This document presents an ISAMKP Domain of Interpretation (DOI) for group key management to support secure group communications. The GDOI manages group security associations, which are used by IPSEC and potentially other data security protocols running at the IP or application layers. These security associations protect one or more key-encrypting keys, traffic-encrypting keys, or data shared by group members. [STANDARDS TRACK] ietf-msec-gdoi-07 PROPOSED STANDARD PROPOSED STANDARD RFC3548 The Base16, Base32, and Base64 Data Encodings S. Josefsson Editor July 2003 ASCII 26363 13 schemes data line-feeds alphabets base encoding hex This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds in encoded data, use of padding in encoded data, use of non-alphabet characters in encoded data, and use of different encoding alphabets. This memo provides information for the Internet community. josefsson-base-encoding-04 INFORMATIONAL INFORMATIONAL RFC3549 Linux Netlink as an IP Services Protocol J. Salim H. Khosravi A. Kleen A. Kuznetsov July 2003 ASCII 72161 33 internet protocol messaging system This document describes Linux Netlink, which is used in Linux both as an intra-kernel messaging system as well as between kernel and user space. The focus of this document is to describe Netlink's functionality as a protocol between a Forwarding Engine Component (FEC) and a Control Plane Component (CPC), the two components that define an IP service. As a result of this focus, this document ignores other uses of Netlink, including its use as a intra-kernel messaging system, as an inter- process communication scheme (IPC), or as a configuration tool for other non-networking or non-IP network services (such as decnet, etc.). This document is intended as informational in the context of prior art for the ForCES IETF working group. This memo provides information for the Internet community. ietf-forces-netlink-04 INFORMATIONAL INFORMATIONAL RFC3550 RTP: A Transport Protocol for Real-Time Applications H. Schulzrinne S. Casner R. Frederick V. Jacobson July 2003 ASCII 259985 104 PS 630740 PDF 504117 RTP end-to-end network audio video RTCP 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. Most of the text in this memorandum is identical to RFC 1889 which it obsoletes. There are no changes in the packet formats on the wire, only changes to the rules and algorithms governing how the protocol is used. The biggest change is an enhancement to the scalable timer algorithm for calculating when to send RTCP packets in order to minimize transmission in excess of the intended rate when many participants join a session simultaneously. [STANDARDS TRACK] ietf-avt-rtp-new-12 Upgraded to full standard 5/17/04. RFC1889 STD0064 STANDARD DRAFT STANDARD RFC3551 RTP Profile for Audio and Video Conferences with Minimal Control H. Schulzrinne S. Casner July 2003 ASCII 106621 44 PS 317286 PDF 237831 RTP-AV end-to-end network conference This document describes a profile called "RTP/AVP" 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. This 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. 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. This memorandum obsoletes RFC 1890. It is mostly backwards-compatible except for functions removed because two interoperable implementations were not found. The additions to RFC 1890 codify existing practice in the use of payload formats under this profile and include new payload formats defined since RFC 1890 was published. [STANDARDS TRACK] ietf-avt-profile-new-13 Upgraded to full standard 5/17/04. RFC1890 STD0065 STANDARD DRAFT STANDARD RFC3552 Guidelines for Writing RFC Text on Security Considerations E. Rescorla B. Korver July 2003 ASCII 110393 44 Request for Comment All RFCs are required to have a Security Considerations section. Historically, such sections have been relatively weak. This document provides guidelines to RFC authors on how to write a good Security Considerations section. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. iab-sec-cons-03 BCP0072 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3553 An IETF URN Sub-namespace for Registered Protocol Parameters M. Mealling L. Masinter T. Hardie G. Klyne June 2003 ASCII 14815 8 syntax uniform resource names This document describes a new sub-delegation for the 'ietf' URN namespace for registered protocol items. The 'ietf' URN namespace is defined in RFC 2648 as a root for persistent URIs that refer to IETF- defined resources. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. mealling-iana-urn-04 BCP0073 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3554 On the Use of Stream Control Transmission Protocol (SCTP) with IPsec S. Bellovin J. Ioannidis A. Keromytis R. Stewart July 2003 ASCII 20102 9 ike internet key exchange security This document describes functional requirements for IPsec (RFC 2401) and Internet Key Exchange (IKE) (RFC 2409) to facilitate their use in securing SCTP (RFC 2960) traffic. [STANDARDS TRACK] ietf-ipsec-sctp-06 PROPOSED STANDARD PROPOSED STANDARD RFC3555 MIME Type Registration of RTP Payload Formats S. Casner P. Hoschka July 2003 ASCII 56618 45 real time transport protocol multipurpose internet mail extensions This document defines the procedure to register RTP Payload Formats as audio, video or other MIME subtype names. This is useful in a text- based format or control protocol to identify the type of an RTP transmission. This document also registers all the RTP payload formats defined in the RTP Profile for Audio and Video Conferences as MIME subtypes. Some of these may also be used for transfer modes other than RTP. [STANDARDS TRACK] ietf-avt-rtp-mime-06 RFC3625 PROPOSED STANDARD PROPOSED STANDARD RFC3556 Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth S. Casner July 2003 ASCII 15310 8 real time transport protocol real-time This document defines an extension to the Session Description Protocol (SDP) to specify two additional modifiers for the bandwidth attribute. These modifiers may be used to specify the bandwidth allowed for RTP Control Protocol (RTCP) packets in a Real-time Transport Protocol (RTP) session. [STANDARDS TRACK] ietf-avt-rtcp-bw-05 PROPOSED STANDARD PROPOSED STANDARD RFC3557 RTP Payload Format for European Telecommunications Standards Institute (ETSI) European Standard ES 201 108 Distributed Speech Recognition Encoding Q. Xie Editor July 2003 ASCII 29692 15 real time transport protocol real-time dsr This document specifies an RTP payload format for encapsulating European Telecommunications Standards Institute (ETSI) European Standard (ES) 201 108 front-end signal processing feature streams for distributed speech recognition (DSR) systems. [STANDARDS TRACK] ietf-avt-dsr-05 PROPOSED STANDARD PROPOSED STANDARD RFC3558 RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV) A. Li July 2003 ASCII 49787 23 real time transport protocol real-time bundled interleaved This document describes the RTP payload format for Enhanced Variable Rate Codec (EVRC) Speech and Selectable Mode Vocoder (SMV) Speech. Two sub-formats are specified for different application scenarios. A bundled/interleaved format is included to reduce the effect of packet loss on speech quality and amortize the overhead of the RTP header over more than one speech frame. A non-bundled format is also supported for conversational applications. [STANDARDS TRACK] ietf-avt-evrc-smv-03 PROPOSED STANDARD PROPOSED STANDARD RFC3559 Multicast Address Allocation MIB D. Thaler June 2003 ASCII 68239 37 maas management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multicast address allocation. [STANDARDS TRACK] ietf-malloc-malloc-mib-08 PROPOSED STANDARD PROPOSED STANDARD RFC3560 Use of the RSAES-OAEP Key Transport Algorithm in Cryptographic Message Syntax (CMS) R. Housley July 2003 ASCII 37381 18 security encryption This document describes the conventions for using the RSAES-OAEP key transport algorithm with the Cryptographic Message Syntax (CMS). The CMS specifies the enveloped-data content type, which consists of an encrypted content and encrypted content-encryption keys for one or more recipients. The RSAES-OAEP key transport algorithm can be used to encrypt content-encryption keys for intended recipients. [STANDARDS TRACK] ietf-smime-cms-rsaes-oaep-07 PROPOSED STANDARD PROPOSED STANDARD RFC3561 Ad hoc On-Demand Distance Vector (AODV) Routing C. Perkins E. Belding-Royer S. Das July 2003 ASCII 90356 37 unicast multiple nodes The Ad hoc On-Demand Distance Vector (AODV) routing protocol is intended for use by mobile nodes in an ad hoc network. It offers quick adaptation to dynamic link conditions, low processing and memory overhead, low network utilization, and determines unicast routes to destinations within the ad hoc network. It uses destination sequence numbers to ensure loop freedom at all times (even in the face of anomalous delivery of routing control messages), avoiding problems (such as "counting to infinity") associated with classical distance vector protocols. This memo defines an Experimental Protocol for the Internet community. ietf-manet-aodv-13 EXPERIMENTAL EXPERIMENTAL RFC3562 Key Management Considerations for the TCP MD5 Signature Option M. Leech July 2003 ASCII 14965 7 bgp border gateway protocol security encryption The TCP MD5 Signature Option (RFC 2385), used predominantly by BGP, has seen significant deployment in critical areas of Internet infrastructure. The security of this option relies heavily on the quality of the keying material used to compute the MD5 signature. This document addresses the security requirements of that keying material. This memo provides information for the Internet community. ietf-idr-md5-keys-00 INFORMATIONAL INFORMATIONAL RFC3563 Cooperative Agreement Between the ISOC/IETF and ISO/IEC Joint Technical Committee 1/Sub Committee 6 (JTC1/SC6) on IS-IS Routing Protocol Development A. Zinin July 2003 ASCII 14974 8 This document contains the text of the agreement signed between ISOC/IETF and ISO/IEC JTC1/SC6 regarding cooperative development of the IS-IS routing protocol. The agreement includes definitions of the related work scopes for the two organizations, request for creation and maintenance of an IS-IS registry by IANA, as well as collaboration guidelines. This memo provides information for the Internet community. zinin-ietf-jtc1-aggr-01 INFORMATIONAL INFORMATIONAL RFC3564 Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering F. Le Faucheur W. Lai July 2003 ASCII 50808 22 multi-protocol label switching bandwidth constraints model overbooking This document presents Service Provider requirements for support of Differentiated Services (Diff-Serv)-aware MPLS Traffic Engineering (DS- TE). Its objective is to provide guidance for the definition, selection and specification of a technical solution addressing these requirements. Specification for this solution itself is outside the scope of this document. A problem statement is first provided. Then, the document describes example applications scenarios identified by Service Providers where existing MPLS Traffic Engineering mechanisms fall short and Diff-Serv-aware Traffic Engineering can address the needs. The detailed requirements that need to be addressed by the technical solution are also reviewed. Finally, the document identifies the evaluation criteria that should be considered for selection and definition of the technical solution. This memo provides information for the Internet community. ietf-tewg-diff-te-reqts-07 INFORMATIONAL INFORMATIONAL RFC3565 Use of the Advanced Encryption Standard (AES) Encryption Algorithm in Cryptographic Message Syntax (CMS) J. Schaad July 2003 ASCII 26773 14 security data encoding This document specifies the conventions for using the Advanced Encryption Standard (AES) algorithm for encryption with the Cryptographic Message Syntax (CMS). [STANDARDS TRACK] ietf-smime-aes-alg-07 PROPOSED STANDARD PROPOSED STANDARD RFC3566 The AES-XCBC-MAC-96 Algorithm and Its Use With IPsec S. Frankel H. Herbert September 2003 ASCII 24645 11 authentication hash security A Message Authentication Code (MAC) is a key-dependent one way hash function. One popular way to construct a MAC algorithm is to use a block cipher in conjunction with the Cipher-Block-Chaining (CBC) mode of operation. The classic CBC-MAC algorithm, while secure for messages of a pre-selected fixed length, has been shown to be insecure across messages of varying lengths such as the type found in typical IP datagrams. This memo specifies the use of AES in CBC mode with a set of extensions to overcome this limitation. This new algorithm is named AES-XCBC-MAC-96. [STANDARDS TRACK] ietf-ipsec-ciph-aes-xcbc-mac-04 PROPOSED STANDARD PROPOSED STANDARD RFC3567 Intermediate System to Intermediate System (IS-IS) Cryptographic Authentication T. Li R. Atkinson July 2003 ASCII 13467 6 iso international standards organization This document describes the authentication of Intermediate System to Intermediate System (IS-IS) Protocol Data Units (PDUs) using the Hashed Message Authentication Codes - Message Digest 5 (HMAC-MD5) algorithm as found in RFC 2104. IS-IS is specified in International Standards Organization (ISO) 10589, with extensions to support Internet Protocol version 4 (IPv4) described in RFC 1195. The base specification includes an authentication mechanism that allows for multiple authentication algorithms. The base specification only specifies the algorithm for cleartext passwords. This document proposes an extension to that specification that allows the use of the HMAC-MD5 authentication algorithm to be used in conjunction with the existing authentication mechanisms. This memo provides information for the Internet community. ietf-isis-hmac-04 INFORMATIONAL INFORMATIONAL RFC3568 Known Content Network (CN) Request-Routing Mechanisms A. Barbir B. Cain R. Nair O. Spatscheck July 2003 ASCII 42443 19 metrics routing redirection This document presents a summary of Request-Routing techniques that are used to direct client requests to surrogates based on various policies and a possible set of metrics. The document covers techniques that were commonly used in the industry on or before December 2000. In this memo, the term Request-Routing represents techniques that is commonly called content routing or content redirection. In principle, Request-Routing techniques can be classified under: DNS Request-Routing, Transport-layer Request-Routing, and Application-layer Request-Routing. This memo provides information for the Internet community. ietf-cdi-known-request-routing-03 INFORMATIONAL INFORMATIONAL RFC3569 An Overview of Source-Specific Multicast (SSM) S. Bhattacharyya Editor July 2003 ASCII 29387 14 routing applications deployment interoperability The purpose of this document is to provide an overview of Source-Specific Multicast (SSM) and issues related to its deployment. It discusses how the SSM service model addresses the challenges faced in inter-domain multicast deployment, changes needed to routing protocols and applications to deploy SSM and interoperability issues with current multicast service models. This memo provides information for the Internet community. ietf-ssm-overview-05 INFORMATIONAL INFORMATIONAL RFC3570 Content Internetworking (CDI) Scenarios P. Rzewski M. Day D. Gilletti July 2003 ASCII 42432 20 production networks In describing content internetworking as a technology targeted for use in production networks, it is useful to provide examples of the sequence of events that may occur when two content networks decide to interconnect. The scenarios presented here seek to provide some concrete examples of what content internetworking is, and also to provide a basis for evaluating content internetworking proposals. This memo provides information for the Internet community. ietf-cdi-scenarios-01 INFORMATIONAL INFORMATIONAL RFC3571 Framework Policy Information Base for Usage Feedback D. Rawlins A. Kulkarni K. Ho Chan M. Bokaemper D. Dutt August 2003 ASCII 70894 35 pib This document describes a portion of the Policy Information Base (PIB) to control policy usage collection and reporting in a device. The provisioning classes specified here allow a Policy Decision Point (PDP) to select which policy objects should collect usage information, what information should be collected and when it should be reported. This PIB requires the presence of other PIBs (defined elsewhere) that provide the policy objects from which usage information is collected. This memo provides information for the Internet community. ietf-rap-feedback-fr-pib-06 INFORMATIONAL INFORMATIONAL RFC3572 Internet Protocol Version 6 over MAPOS (Multiple Access Protocol Over SONET/SDH) T. Ogura M. Maruyama T. Yoshida July 2003 ASCII 30607 14 ipv6 synchronous optical network synchronous digital hierarchy Multiple Access Protocol over SONET/SDH (MAPOS) is a high-speed link- layer protocol that provides multiple access capability over a Synchronous Optical NETwork/Synchronous Digital Hierarchy (SONET/SDH). This document specifies the frame format for encapsulating an IPv6 datagram in a MAPOS frame. It also specifies the method of forming IPv6 interface identifiers, the method of detecting duplicate addresses, and the format of the Source/Target Link-layer Addresses option field used in IPv6 Neighbor Discovery messages. This memo provides information for the Internet community. ogura-ipv6-mapos-02 INFORMATIONAL INFORMATIONAL RFC3573 Signalling of Modem-On-Hold status in Layer 2 Tunneling Protocol (L2TP) I. Goyret July 2003 ASCII 22758 13 ppp point to point point-to-point pstn public switched telephone network The Layer 2 Tunneling Protocol (L2TP) defines a mechanism for tunneling Point-to-Point Protocol (PPP) sessions. It is common for these PPP sessions to be established using modems connected over the public switched telephone network. One of the standards governing modem operation defines procedures that enable a client modem to put the call on hold and later, re-establish the modem link with minimal delay and without having to redial. While the modem call is on hold, the client phone line can be used to place or receive other calls. The L2TP base protocol does not provide any means to signal these events from the L2TP Access Controller (LAC), where the modem is physically connected, to the L2TP Network Server (LNS), where the PPP session is handled. This document describes a method to let the LNS know when a client modem connected to a LAC has placed the call on hold. [STANDARDS TRACK] ietf-l2tpext-v92-moh-05 PROPOSED STANDARD PROPOSED STANDARD RFC3574 Transition Scenarios for 3GPP Networks J. Soininen Editor August 2003 ASCII 23359 12 third generation parnership project packet ipv6 ipv4 internet This document describes different scenarios in Third Generation Partnership Project (3GPP) defined packet network, i.e., General Packet Radio Service (GPRS) that would need IP version 6 and IP version 4 transition. The focus of this document is on the scenarios where the User Equipment (UE) connects to nodes in other networks, e.g., in the Internet. GPRS network internal transition scenarios, i.e., between different GPRS elements in the network, are out of scope. The purpose of the document is to list the scenarios for further discussion and study. This memo provides information for the Internet community. ietf-v6ops-3gpp-cases-03 INFORMATIONAL INFORMATIONAL RFC3575 IANA Considerations for RADIUS (Remote Authentication Dial In User Service) B. Aboba July 2003 ASCII 15539 8 internet assigned numbers authority encryption NAS Network Access Server This document describes the IANA considerations for the Remote Authentication Dial In User Service (RADIUS). [STANDARDS TRACK] aboba-radius-iana-07 RFC2865 PROPOSED STANDARD PROPOSED STANDARD RFC3576 Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS) M. Chiba G. Dommety M. Eklund D. Mitton B. Aboba July 2003 ASCII 70027 30 nas network access server This document describes a currently deployed extension to the Remote Authentication Dial In User Service (RADIUS) protocol, allowing dynamic changes to a user session, as implemented by network access server products. This includes support for disconnecting users and changing authorizations applicable to a user session. This memo provides information for the Internet community. chiba-radius-dynamic-authorization-20 INFORMATIONAL INFORMATIONAL RFC3577 Introduction to the Remote Monitoring (RMON) Family of MIB Modules S. Waldbusser R. Cole C. Kalbfleisch D. Romascanu August 2003 ASCII 68551 31 management information base The Remote Monitoring (RMON) Framework consists of a number of interrelated documents. This memo describes these documents and how they relate to one another. This memo provides information for the Internet community. ietf-rmonmib-framework-05 INFORMATIONAL INFORMATIONAL RFC3578 Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP) G. Camarillo A. B. Roach J. Peterson L. Ong August 2003 ASCII 26667 13 pstn public switched telephone network This document describes a way to map Integrated Services Digital Network User Part (ISUP) overlap signalling to Session Initiation Protocol (SIP). This mechanism might be implemented when using SIP in an environment where part of the call involves interworking with the Public Switched Telephone Network (PSTN). [STANDARDS TRACK] ietf-sipping-overlap-04 PROPOSED STANDARD PROPOSED STANDARD RFC3579 RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP) B. Aboba P. Calhoun September 2003 ASCII 104469 46 RADIUS encryption NAS Network Access Server This document defines Remote Authentication Dial In User Service (RADIUS) support for the Extensible Authentication Protocol (EAP), an authentication framework which supports multiple authentication mechanisms. In the proposed scheme, the Network Access Server (NAS) forwards EAP packets to and from the RADIUS server, encapsulated within EAP-Message attributes. This has the advantage of allowing the NAS to support any EAP authentication method, without the need for method- specific code, which resides on the RADIUS server. While EAP was originally developed for use with PPP, it is now also in use with IEEE 802. This memo provides information for the Internet community. aboba-radius-rfc2869bis-22 RFC2869 INFORMATIONAL INFORMATIONAL RFC3580 IEEE 802.1X Remote Authentication Dial In User Service (RADIUS) Usage Guidelines P. Congdon B. Aboba A. Smith G. Zorn J. Roese September 2003 ASCII 66136 30 AAA authentication authorization and accounting This document provides suggestions on Remote Authentication Dial In User Service (RADIUS) usage by IEEE 802.1X Authenticators. The material in this document is also included within a non-normative Appendix within the IEEE 802.1X specification, and is being presented as an IETF RFC for informational purposes. This memo provides information for the Internet community. congdon-radius-8021x-29 INFORMATIONAL INFORMATIONAL RFC3581 An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing J. Rosenberg H. Schulzrinne August 2003 ASCII 66133 13 report client server The Session Initiation Protocol (SIP) operates over UDP and TCP, among others. When used with UDP, responses to requests are returned to the source address the request came from, and to the port written into the topmost Via header field value of the request. This behavior is not desirable in many cases, most notably, when the client is behind a Network Address Translator (NAT). This extension defines a new parameter for the Via header field, called "rport", that allows a client to request that the server send the response back to the source IP address and port from which the request originated. [STANDARDS TRACK] ietf-sip-symmetric-response-01 PROPOSED STANDARD PROPOSED STANDARD RFC3582 Goals for IPv6 Site-Multihoming Architectures J. Abley B. Black V. Gill August 2003 ASCII 17045 9 internet protocol multi6 This document outlines a set of goals for proposed new IPv6 site- multihoming architectures. It is recognised that this set of goals is ambitious and that some goals may conflict with others. The solution or solutions adopted may only be able to satisfy some of the goals presented here. This memo provides information for the Internet community. ietf-multi6-multihoming-requirements-07 INFORMATIONAL INFORMATIONAL RFC3583 Requirements of a Quality of Service (QoS) Solution for Mobile IP H. Chaskar Editor September 2003 ASCII 22541 10 internet protocol routing packets node Mobile IP ensures correct routing of packets to a mobile node as the mobile node changes its point of attachment to the Internet. However, it is also required to provide proper Quality of Service (QoS) forwarding treatment to the mobile node's packet stream at the intermediate nodes in the network, so that QoS-sensitive IP services can be supported over Mobile IP. This document describes requirements for an IP QoS mechanism for its satisfactory operation with Mobile IP. This memo provides information for the Internet community. ietf-nsis-qos-requirements-01 INFORMATIONAL INFORMATIONAL RFC3584 Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework R. Frye D. Levi S. Routhier B. Wijnen August 2003 ASCII 115222 51 SNMP simple network management protocol mib information base The purpose of this document is to describe coexistence between version 3 of the Internet-standard Network Management Framework, (SNMPv3), version 2 of the Internet-standard Network Management Framework (SNMPv2), and the original Internet-standard Network Management Framework (SNMPv1). This document also describes how to convert MIB modules from SMIv1 format to SMIv2 format. This document obsoletes RFC 2576. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-snmpv3-coex-v2-04 RFC2576 BCP0074 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3585 IPsec Configuration Policy Information Model J. Jason L. Rafalow E. Vyncke August 2003 ASCII 187308 88 ike internet key exchange protocol core pcim This document presents an object-oriented information model of IP Security (IPsec) policy designed to facilitate agreement about the content and semantics of IPsec policy, and enable derivations of task- specific representations of IPsec policy such as storage schema, distribution representations, and policy specification languages used to configure IPsec-enabled endpoints. The information model described in this document models the configuration parameters defined by IPSec. The information model also covers the parameters found by the Internet Key Exchange protocol (IKE). Other key exchange protocols could easily be added to the information model by a simple extension. Further extensions can further be added easily due to the object-oriented nature of the model. This information model is based upon the core policy classes as defined in the Policy Core Information Model (PCIM) and in the Policy Core Information Model Extensions (PCIMe). [STANDARDS TRACK] ietf-ipsp-config-policy-model-07 PROPOSED STANDARD PROPOSED STANDARD RFC3586 IP Security Policy (IPSP) Requirements M. Blaze A. Keromytis M. Richardson L. Sanchez August 2003 ASCII 22068 10 data integrity authentication host network This document describes the problem space and solution requirements for developing an IP Security Policy (IPSP) configuration and management framework. The IPSP architecture provides a scalable, decentralized framework for managing, discovering and negotiating the host and network security policies that govern access, authorization, authentication, confidentiality, data integrity, and other IP Security properties. This document highlights such architectural components and presents their functional requirements. [STANDARDS TRACK] ietf-ipsp-requirements-02 PROPOSED STANDARD PROPOSED STANDARD RFC3587 IPv6 Global Unicast Address Format R. Hinden S. Deering E. Nordmark August 2003 ASCII 8783 5 internet protocol architecture routing This document obsoletes RFC 2374, "An IPv6 Aggregatable Global Unicast Address Format". It defined an IPv6 address allocation structure that includes Top Level Aggregator (TLA) and Next Level Aggregator (NLA). This document makes RFC 2374 and the TLA/NLA structure historic. This memo provides information for the Internet community. ietf-ipv6-unicast-aggr-v2-03 RFC2374 INFORMATIONAL INFORMATIONAL RFC3588 Diameter Base Protocol P. Calhoun J. Loughney E. Guttman G. Zorn J. Arkko September 2003 ASCII 341261 147 aaa authentication authorization accounting ip mobility The Diameter base protocol is intended to provide an Authentication, Authorization and Accounting (AAA) framework for applications such as network access or IP mobility. Diameter is also intended to work in both local Authentication, Authorization & Accounting and roaming situations. This document specifies the message format, transport, error reporting, accounting and security services to be used by all Diameter applications. The Diameter base application needs to be supported by all Diameter implementations. [STANDARDS TRACK] ietf-aaa-diameter-17 PROPOSED STANDARD PROPOSED STANDARD RFC3589 Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5 J. Loughney September 2003 ASCII 8010 5 iana allocation This document describes the IANA's allocation of a block of Diameter Command Codes for the Third Generation Partnership Project (3GPP) Release 5. This document does not pass judgment on the usage of these command codes. Further more, these command codes are for use for Release 5. For future releases, these codes cannot be reused, but must be allocated according to the Diameter Base specification. This memo provides information for the Internet community. loughney-aaa-cc-3gpp-01 INFORMATIONAL INFORMATIONAL RFC3590 Source Address Selection for the Multicast Listener Discovery (MLD) Protocol B. Haberman September 2003 ASCII 11554 6 MLD-IPv6 internet protocol routher packets It has come to light that there is an issue with the selection of a suitable IPv6 source address for Multicast Listener Discovery (MLD) messages when a node is performing stateless address autoconfiguration. This document is intended to clarify the rules on selecting an IPv6 address to use for MLD messages. [STANDARDS TRACK] ietf-magma-mld-source-07 RFC2710 PROPOSED STANDARD PROPOSED STANDARD RFC3591 Definitions of Managed Objects for the Optical Interface Type H-K. Lam M. Stewart A. Huynh September 2003 ASCII 310815 174 management information base mib snmp simple network management protocol otn optical transport network itu-t performance monitoring configuration dwdm optical tranmission session optical multiplex section optical channel otuk odukt oduk This memo defines a portion of the Management Information Base (MIB) for use with Simple Network Management Protocol (SNMP) in TCP/IP-based internets. In particular, it defines objects for managing Optical Interfaces associated with WavelengthDivision Multiplexing systems or characterized by the Optical Transport Network (OTN) in accordance with the OTN architecture defined in ITU-T Recommendation G.872. The MIB module defined in this memo can be used for performance monitoring and/or configuration of such optical interface. [STANDARDS TRACK] ietf-atommib-opticalmib-08 PROPOSED STANDARD PROPOSED STANDARD RFC3592 Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Type K. Tesink September 2003 ASCII 143588 73 MIB Management SNMP This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) interfaces. This document is a companion to the documents that define Managed Objects for the DS1/E1/DS2/E2 and DS3/E3 Interface Types. This memo replaces RFC 2558. Changes relative to RFC 2558 are summarized in the MIB module's REVISION clause. [STANDARDS TRACK] ietf-atommib-rfc2558bis-01 RFC2558 DRAFT STANDARD DRAFT STANDARD RFC3593 Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals K. Tesink Editor September 2003 ASCII 20363 10 management information base data This document defines a set of Textual Conventions for MIB modules that make use of performance history data based on 15 minute intervals. This memo replaces RFC 2493. Changes relative to RFC 2493 are summarized in the MIB module's REVISION clause. [STANDARDS TRACK] ietf-atommib-rfc2493bis-01 RFC2493 DRAFT STANDARD DRAFT STANDARD RFC3594 PacketCable Security Ticket Control Sub-Option for the DHCP CableLabs Client Configuration (CCC) Option P. Duffy September 2003 ASCII 12521 7 dynamic host configuration protocol This document defines a new sub-option for the DHCP CableLabs Client Configuration (CCC) Option. This new sub-option will be used to direct CableLabs Client Devices (CCDs) to invalidate security tickets stored in CCD non volatile memory (i.e., locally persisted security tickets). [STANDARDS TRACK] ietf-dhc-pktc-kerb-tckt-03 PROPOSED STANDARD PROPOSED STANDARD RFC3595 Textual Conventions for IPv6 Flow Label B. Wijnen September 2003 ASCII 11746 6 mib management information base This MIB module defines textual conventions to represent the commonly used IPv6 Flow Label. The intent is that these textual conventions (TCs) will be imported and used in MIB modules that would otherwise define their own representations. [STANDARDS TRACK] ietf-ops-ipv6-flowlabel-01 PROPOSED STANDARD PROPOSED STANDARD RFC3596 DNS Extensions to Support IP Version 6 S. Thomson C. Huitema V. Ksinant M. Souissi October 2003 ASCII 14093 8 internet protocol domain name system DNS zone This document defines the changes that need to be made to the Domain Name System (DNS) to support hosts running IP version 6 (IPv6). The changes include a resource record type to store an IPv6 address, a 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. [STANDARDS TRACK] ietf-dnsext-rfc1886bis-03 RFC3152 RFC1886 DRAFT STANDARD DRAFT STANDARD RFC3597 Handling of Unknown DNS Resource Record (RR) Types A. Gustafsson September 2003 ASCII 17559 8 domain name system name server software compression transparency Extending the Domain Name System (DNS) with new Resource Record (RR) types currently requires changes to name server software. This document specifies the changes necessary to allow future DNS implementations to handle new RR types transparently. [STANDARDS TRACK] ietf-dnsext-unknown-rrs-06 RFC2163 RFC2535 RFC4033 RFC4034 RFC4035 PROPOSED STANDARD PROPOSED STANDARD RFC3598 Sieve Email Filtering -- Subaddress Extension K. Murchison September 2003 ASCII 11151 6 users detailed addressing language address part test detail filter mailbox On email systems that allow for "subaddressing" or "detailed addressing" (e.g., "ken+sieve@example.org"), it is sometimes desirable to make comparisons against these sub-parts of addresses. This document defines an extension to the Sieve mail filtering language that allows users to compare against the user and detail parts of an address. [STANDARDS TRACK] murchison-sieve-subaddress-06 PROPOSED STANDARD PROPOSED STANDARD RFC3599 Request for Comments Summary RFC Numbers 3500-3599 S. Ginoza December 2003 ASCII 76893 34 This RFC is a slightly annotated list of the 100 RFCs from RFC 3500 through RFC 3599. This is a status report on these RFCs. INFORMATIONAL INFORMATIONAL RFC3600 Internet Official Protocol Standards J. Reynolds Editor S. Ginoza Editor November 2003 ASCII 134338 50 This memo contains a snapshot of the state of standardization of protocols used in the Internet as of October 2, 2003. It lists official protocol standards and Best Current Practice RFCs; it is not a complete index to the RFC series. The latest version of this memo is designated STD 1. RFC3300 RFC3700 STD0001 STANDARD STANDARD RFC3601 Text String Notation for Dial Sequences and Global Switched Telephone Network (GSTN) / E.164 Addresses C. Allocchio September 2003 ASCII 18572 10 notations dtmf dual tone multifrequency telephony e-mail addresses urls integrated messaging 3gpp This memo describes the full set of notations needed to represent a text string in a Dial Sequence. A Dial Sequence is normally composed of Dual Tone Multi Frequency (DTMF) elements, plus separators and additional "actions" (such as "wait for dialtone", "pause for N secs", etc.) which could be needed to successfully establish the connection with the target service: this includes the cases where subaddresses or DTMF menu navigation apply. allocchio-gstn-05 PROPOSED STANDARD PROPOSED STANDARD RFC3602 The AES-CBC Cipher Algorithm and Its Use with IPsec S. Frankel R. Glenn S. Kelly September 2003 ASCII 30254 15 ipsec encapsulating security payload This document describes the use of the Advanced Encryption Standard (AES) Cipher Algorithm in Cipher Block Chaining (CBC) Mode, with an explicit Initialization Vector (IV), as a confidentiality mechanism within the context of the IPsec Encapsulating Security Payload (ESP). ietf-ipsec-ciph-aes-cbc-05 PROPOSED STANDARD PROPOSED STANDARD RFC3603 Private Session Initiation Protocol (SIP) Proxy-to-Proxy Extensions for Supporting the PacketCable Distributed Call Signaling Architecture W. Marshall Editor F. Andreasen Editor October 2003 ASCII 67509 28 network access coordination In order to deploy a residential telephone service at very large scale across different domains, it is necessary for trusted elements owned by different service providers to exchange trusted information that conveys customer-specific information and expectations about the parties involved in the call. This document describes private extensions to the Session Initiation Protocol (SIP) (RFC3261) for supporting the exchange of customer information and billing information between trusted entities in the PacketCable Distributed Call Signaling Architecture. These extensions provide mechanisms for access network coordination to prevent theft of service, customer originated trace of harassing calls, support for operator services and emergency services, and support for various other regulatory issues. The use of the extensions is only applicable within closed administrative domains, or among federations of administrative domains with previously agreed-upon policies where coordination of charging and other functions is required. dcsgroup-sipping-proxy-proxy-03 INFORMATIONAL INFORMATIONAL RFC3604 Requirements for Adding Optical Support to the General Switch Management Protocol version 3 (GSMPv3) H. Khosravi G. Kullgren S. Shew J. Sadler A. Watanabe October 2003 ASCII 30805 16 controllers routers formats codes This memo provides requirements for adding optical switching support to the General Switch Management Protocol (GSMP). It also contains clarifications and suggested changes to the GSMPv3 specification. ietf-gsmp-reqs-06 INFORMATIONAL INFORMATIONAL RFC3605 Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP) C. Huitema October 2003 ASCII 17270 8 nat network access translation port mapping The Session Description Protocol (SDP) is used to describe the parameters of media streams used in multimedia sessions. When a session requires multiple ports, SDP assumes that these ports have consecutive numbers. However, when the session crosses a network address translation device that also uses port mapping, the ordering of ports can be destroyed by the translation. To handle this, we propose an extension attribute to SDP. ietf-mmusic-sdp4nat-05 PROPOSED STANDARD PROPOSED STANDARD RFC3606 Definitions of Supplemental Managed Objects for ATM Interface F. Ly M. Noto A. Smith E. Spiegel K. Tesink November 2003 ASCII 183610 94 asynchronous transfer mode mib management information base This memo defines objects used for managing ATM-based interfaces, devices, and services, in addition to those defined in RFC 2515, the ATM-MIB, to provide additional support for the management of ATM Switched Virtual Connections (SVCs) and ATM Permanent Virtual Connections (PVCs). ietf-atommib-atm2-19 PROPOSED STANDARD PROPOSED STANDARD RFC3607 Chinese Lottery Cryptanalysis Revisited: The Internet as a Codebreaking Tool M. Leech September 2003 ASCII 14526 8 security encryption des data standard distributed cryptanalysis computer virus network worm codebreaking This document revisits the so-called Chinese Lottery massively-parallel cryptanalytic attack. It explores Internet-based analogues to the Chinese Lottery, and their potentially-serious consequences. leech-chinese-lottery-04 INFORMATIONAL INFORMATIONAL RFC3608 Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration D. Willis B. Hoeneisen October 2003 ASCII 35628 17 user agent domain register This document defines a Session Initiation Protocol (SIP) extension header field used in conjunction with responses to REGISTER requests to provide a mechanism by which a registrar may inform a registering user agent (UA) of a service route that the UA may use to request outbound services from the registrar's domain. ietf-sip-scvrtdicso-04 PROPOSED STANDARD PROPOSED STANDARD RFC3609 Tracing Requirements for Generic Tunnels R. Bonica K. Kompella D. Meyer September 2003 ASCII 17859 9 traceroute application IP internet protocol This document specifies requirements for a generic route-tracing application. It also specifies requirements for a protocol that will support that application. Network operators will use the generic route-tracing application to verify proper operation of the IP forwarding plane. They will also use the application to discover details regarding tunnels that support IP forwarding. The generic route-tracing application, specified herein, supports a superset of the functionality that "traceroute" currently offers. Like traceroute, the generic route-tracing application can discover the forwarding path between two interfaces that are contained by an IP network. Unlike traceroute, this application can reveal details regarding tunnels that support the IP forwarding path. ietf-ccamp-tracereq-05 INFORMATIONAL INFORMATIONAL RFC3610 Counter with CBC-MAC (CCM) D. Whiting R. Housley N. Ferguson September 2003 ASCII 64509 26 authentication encryption security ciphers Counter with CBC-MAC (CCM) is a generic authenticated encryption block cipher mode. CCM is defined for use with 128-bit block ciphers, such as the Advanced Encryption Standard (AES). housley-ccm-mode-02 INFORMATIONAL INFORMATIONAL RFC3611 RTP Control Protocol Extended Reports (RTCP XR) T. Friedman Editor R. Caceres Editor A. Clark Editor November 2003 ASCII 126736 55 real time transport protocol packet type sdp session description blocks This document defines the Extended Report (XR) packet type for the RTP Control Protocol (RTCP), and defines how the use of XR packets can be signaled by an application if it employs the Session Description Protocol (SDP). XR packets are composed of report blocks, and seven block types are defined here. The purpose of the extended reporting format is to convey information that supplements the six statistics that are contained in the report blocks used by RTCP's Sender Report (SR) and Receiver Report (RR) packets. Some applications, such as multicast inference of network characteristics (MINC) or voice over IP (VoIP) monitoring, require other and more detailed statistics. In addition to the block types defined here, additional block types may be defined in the future by adhering to the framework that this document provides. ietf-avt-rtcp-report-extns-06 PROPOSED STANDARD PROPOSED STANDARD RFC3612 Applicability Statement for Restart Mechanisms for the Label Distribution Protocol (LDP) A. Farrel September 2003 ASCII 35677 16 mpls fault tolerence high availability multiprotocol label switching cr-ldp high availability restart This document provides guidance on when it is advisable to implement some form of Label Distribution Protocol (LDP) restart mechanism and which approach might be more suitable. The issues and extensions described in this document are equally applicable to RFC 3212, "Constraint-Based LSP Setup Using LDP". ietf-mpls-ldp-restart-applic-06 INFORMATIONAL INFORMATIONAL RFC3613 Definition of a Uniform Resource Name (URN) Namespace for the Middleware Architecture Committee for Education (MACE) R. Morgan K. Hazelton October 2003 ASCII 14296 8 internet2 middleware This document describes a Uniform Resource Name (URN) namespace for the Internet2 Middleware Architecture Committee for Education (MACE). This namespace is for naming persistent resources defined by MACE, its working groups and other designated subordinates. hazelton-mace-urn-namespace-01 INFORMATIONAL INFORMATIONAL RFC3614 A Uniform Resource Name (URN) Namespace for the Motion Picture Experts Group (MPEG) J. Smith September 2003 ASCII 10457 6 iso international organization standardization multimedia metadata xml classification schemes digital rights management This document describes a Uniform Resource Name (URN) namespace for the Motion Picture Experts Group (MPEG) for naming persistent resources as part of the MPEG standards. Example resources include technical documents and specifications, eXtensible Markup Language (XML) Schemas, classification schemes, XML Document Type Definitions (DTDs), namespaces, style sheets, media assets, and other types of resources produced or managed by MPEG. smith-urn-mpeg-01 INFORMATIONAL INFORMATIONAL RFC3615 A Uniform Resource Name (URN) Namespace for SWIFT Financial Messaging J. Gustin A. Goyens September 2003 ASCII 7352 5 messaging service interface software This document describes a Uniform Resource Name (URN) namespace that is managed by SWIFT for usage within messages standardized by SWIFT. gustin-goyens-urn-01 INFORMATIONAL INFORMATIONAL RFC3616 A Uniform Resource Name (URN) Namespace for Foundation for Intelligent Physical Agents (FIPA) F. Bellifemine I. Constantinescu S. Willmott September 2003 ASCII 13352 8 URN NID Uniform Resource Name Namespace Identification This document describes a Uniform Resource Name Namespace Identification (URN NID) for the Foundation for Intelligent Physical Agents (FIPA). This URN NID will be used for identification of standard components published by the FIPA standards body in the area of Agent technology. bellifemine-urn-fipa-00 INFORMATIONAL INFORMATIONAL RFC3617 Uniform Resource Identifier (URI) Scheme and Applicability Statement for the Trivial File Transfer Protocol (TFTP) E. Lear October 2003 ASCII 11848 7 The Trivial File Transfer Protocol (TFTP) is a very simple TRIVIAL protocol that has been in use on the Internet for quite a long time. While this document discourages its continued use, largely due to security concerns, we do define a Uniform Resource Identifier (URI) scheme, as well as discuss the protocol's applicability. lear-tftp-uri-06 INFORMATIONAL INFORMATIONAL RFC3618 Multicast Source Discovery Protocol (MSDP) B. Fenner Editor D. Meyer Editor October 2003 ASCII 42238 19 ipv4 pim-sm independent multicast sparse-mode rp rendezvous point The Multicast Source Discovery Protocol (MSDP) describes a mechanism to connect multiple IP Version 4 Protocol Independent Multicast Sparse-Mode (PIM-SM) domains together. Each PIM-SM domain uses its own independent Rendezvous Point (RP) and does not have to depend on RPs in other domains. This document reflects existing MSDP implementations. ietf-msdp-spec-20 EXPERIMENTAL EXPERIMENTAL RFC3619 Extreme Networks' Ethernet Automatic Protection Switching (EAPS) Version 1 S. Shah M. Yip October 2003 ASCII 14440 7 ethernet rings robust This document describes the Ethernet Automatic Protection Switching (EAPS) (tm) technology invented by Extreme Networks to increase the availability and robustness of Ethernet rings. An Ethernet ring built using EAPS can have resilience comparable to that provided by SONET rings, at a lower cost and with fewer constraints (e.g., ring size). shah-extreme-eaps-03 INFORMATIONAL INFORMATIONAL RFC3620 The TUNNEL Profile D. New October 2003 ASCII 35365 18 beep blocks extensible exchange protocol firewall application layer This memo describes a Blocks Extensible Exchange Protocol (BEEP) profile that allows a BEEP peer to serve as an application-layer proxy. It allows authorized users to access services through a firewall. ietf-idwg-beep-tunnel-05 PROPOSED STANDARD PROPOSED STANDARD RFC3621 Power Ethernet MIB A. Berger D. Romascanu December 2003 ASCII 37294 20 management information base data terminal equipment power dte power sourcing equipment pse This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This document proposes an extension to the Ethernet-like Interfaces MIB with a set of objects for managing Power Sourcing Equipment (PSE). ietf-hubmib-power-ethernet-mib-08 PROPOSED STANDARD PROPOSED STANDARD RFC3622 A Uniform Resource Name (URN) Namespace for the Liberty Alliance Project M. Mealling February 2004 ASCII 11432 7 federated network identity This document describes a Uniform Resource Name (URN) namespace that will identify various objects within the Liberty Architecture for federated network identity. mealling-liberty-urn-00 INFORMATIONAL INFORMATIONAL RFC3623 Graceful OSPF Restart J. Moy P. Pillay-Esnault A. Lindem November 2003 ASCII 38757 18 open shortest path first non-stop forwarding This memo documents an enhancement to the OSPF routing protocol, whereby an OSPF router can stay on the forwarding path even as its OSPF software is restarted. This is called "graceful restart" or "non-stop forwarding". A restarting router may not be capable of adjusting its forwarding in a timely manner when the network topology changes. In order to avoid the possible resulting routing loops, the procedure in this memo automatically reverts to a normal OSPF restart when such a topology change is detected, or when one or more of the restarting router's neighbors do not support the enhancements in this memo. Proper network operation during a graceful restart makes assumptions upon the operating environment of the restarting router; these assumptions are also documented. ietf-ospf-hitless-restart-08 PROPOSED STANDARD PROPOSED STANDARD RFC3624 The Media Gateway Control Protocol (MGCP) Bulk Audit Package B. Foster D. Auerbach F. Andreasen November 2003 ASCII 34391 19 call agent endpoints naming conventions The base Media Gateway Control Protocol (MGCP) includes audit commands that only allow a Call Agent to audit endpoint and/or connection state one endpoint at a time. This document describes a new MGCP package for bulk auditing of a group of gateway endpoints. It allows a Call Agent to determine the endpoint naming convention, the list of instantiated endpoints as well connection and endpoint state for the group of endpoints. foster-mgcp-bulkaudits-08 INFORMATIONAL INFORMATIONAL RFC3625 The QCP File Format and Media Types for Speech Data R. Gellens H. Garudadri September 2003 ASCII 28603 15 13k qcelp audio multimedia voip real time transport protocol multipurpose internet mail extensions RFC 2658 specifies the streaming format for 3GPP2 13KK vocoder (High Rate Speech Service Option 17 for Wideband Spread Spectrum Communications Systems, also known as QCELP 13K vocoder) data, but does not specify a storage format. Many implementations have been using the "QCP" file format (named for its file extension) for exchanging QCELP 13K data as well as Enhanced Variable Rate Coder (EVRC) and Selectable Mode Vocoders (SMV) data. (For example, Eudora(r), QuickTime(r), and cmda2000(r) handsets). This document specifies the QCP file format and updates the audio/qcelp media registration to specify this format for storage, and registers the audio/evrc-qcp and audio/smv-qcp media types for EVRC and SMV (respectively) data stored in this format. gellens-qcp-01 RFC3555 INFORMATIONAL INFORMATIONAL RFC3626 Optimized Link State Routing Protocol (OLSR) T. Clausen Editor P. Jacquet Editor October 2003 ASCII 161265 75 mobile ad hoc wireless multipoint relays mpr mprs This document describes the Optimized Link State Routing (OLSR) protocol for mobile ad hoc networks. The protocol is an optimization of the classical link state algorithm tailored to the requirements of a mobile wireless LAN. The key concept used in the protocol is that of multipoint relays (MPRs). MPRs are selected nodes which forward broadcast messages during the flooding process. This technique substantially reduces the message overhead as compared to a classical flooding mechanism, where every node retransmits each message when it receives the first copy of the message. In OLSR, link state information is generated only by nodes elected as MPRs. Thus, a second optimization is achieved by minimizing the number of control messages flooded in the network. As a third optimization, an MPR node may chose to report only links between itself and its MPR selectors. Hence, as contrary to the classic link state algorithm, partial link state information is distributed in the network. This information is then used for route calculation. OLSR provides optimal routes (in terms of number of hops). The protocol is particularly suitable for large and dense networks as the technique of MPRs works well in this context. ietf-manet-olsr-11 EXPERIMENTAL EXPERIMENTAL RFC3627 Use of /127 Prefix Length Between Routers Considered Harmful P. Savola September 2003 ASCII 12436 6 address space anycast In some cases, the operational decision may be to use IPv6 /127 prefix lengths, especially on point-to-point links between routers. Under certain situations, this may lead to one router claiming both addresses due to subnet-router anycast being implemented. This document discusses the issue and offers a couple of solutions to the problem; nevertheless, /127 should be avoided between two routers. savola-ipv6-127-prefixlen-04 INFORMATIONAL INFORMATIONAL RFC3628 Policy Requirements for Time-Stamping Authorities (TSAs) D. Pinkas N. Pope J. Ross November 2003 ASCII 92941 43 tokens public key certificates This document defines requirements for a baseline time-stamp policy for Time-Stamping Authorities (TSAs) issuing time-stamp tokens, supported by public key certificates, with an accuracy of one second or better. A TSA may define its own policy which enhances the policy defined in this document. Such a policy shall incorporate or further constrain the requirements identified in this document. ietf-pkix-pr-tsa-05 INFORMATIONAL INFORMATIONAL RFC3629 UTF-8, a transformation format of ISO 10646 F. Yergeau November 2003 ASCII 33856 14 UTF-8 UCS Transformation Format ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo. UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo obsoletes and replaces RFC 2279. yergeau-rfc2279bis-05 RFC2279 STD0063 STANDARD STANDARD RFC3630 Traffic Engineering (TE) Extensions to OSPF Version 2 D. Katz K. Kompella D. Yeung September 2003 ASCII 27717 14 open-shortest path first ink state advertisement This document describes extensions to the OSPF protocol version 2 to support intra-area Traffic Engineering (TE), using Opaque Link State Advertisements. katz-yeung-ospf-traffic-10 RFC2370 PROPOSED STANDARD PROPOSED STANDARD RFC3631 Security Mechanisms for the Internet S. Bellovin Editor J. Schiller Editor C. Kaufman Editor December 2003 ASCII 47064 20 protocol host compromise dos denial of service Security must be built into Internet Protocols for those protocols to offer their services securely. Many security problems can be traced to improper implementations. However, even a proper implementation will have security problems if the fundamental protocol is itself exploitable. Exactly how security should be implemented in a protocol will vary, because of the structure of the protocol itself. However, there are many protocols for which standard Internet security mechanisms, already developed, may be applicable. The precise one that is appropriate in any given situation can vary. We review a number of different choices, explaining the properties of each. iab-secmech-03 INFORMATIONAL INFORMATIONAL RFC3632 VeriSign Registry Registrar Protocol (RRP) Version 2.0.0 S. Hollenbeck S. Veeramachaneni S. Yalamanchilli November 2003 ASCII 13490 8 RRP shared registration system gLTD ccTLD top level domain This document updates version 1.1.0 of the Network Solutions Inc. (NSI) Registry Registrar Protocol (RRP) specified in RFC 2832. The changes described in this document combined with the base specification documented in RFC 2832 specify version 2.0.0 of the VeriSign Registry Registrar Protocol. hollenbeck-rfc2832bis-02 RFC2832 INFORMATIONAL INFORMATIONAL RFC3633 IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6 O. Troan R. Droms December 2003 ASCII 45308 19 automated delegation router The Prefix Delegation options provide a mechanism for automated delegation of IPv6 prefixes using the Dynamic Host Configuration Protocol (DHCP). This mechanism is intended for delegating a long-lived prefix from a delegating router to a requesting router, across an administrative boundary, where the delegating router does not require knowledge about the topology of the links in the network to which the prefixes will be assigned. ietf-dhc-dhcpv6-opt-prefix-delegation-05 PROPOSED STANDARD PROPOSED STANDARD RFC3634 Key Distribution Center (KDC) Server Address Sub-option for the Dynamic Host Configuration Protocol (DHCP) CableLabs Client Configuration (CCC) Option K. Luehrs R. Woundy J. Bevilacqua N. Davoust December 2003 ASCII 13163 7 This document defines a new sub-option for the CableLabs Client Configuration (CCC) Dynamic Host Configuration Protocol (DHCP) option code for conveying the network addresses of Key Distribution Center (KDC) servers. ietf-dhc-suboptions-kdc-serveraddress-04 PROPOSED STANDARD PROPOSED STANDARD RFC3635 Definitions of Managed Objects for the Ethernet-like Interface Types J. Flick September 2003 ASCII 154476 64 MIB management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing Ethernet-like interfaces. This memo obsoletes RFC 2665. It updates that specification by including management information useful for the management of 10 Gigabit per second (Gb/s) Ethernet interfaces. ietf-hubmib-etherif-mib-v3-03 RFC2665 PROPOSED STANDARD PROPOSED STANDARD RFC3636 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) J. Flick September 2003 ASCII 139990 62 MAU-MIB management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IEEE 802.3 Medium Attachment Units (MAUs). This memo obsoletes RFC 2668. This memo extends that specification by including management information useful for the management of 10 gigabit per second (Gb/s) MAUs. This memo also obsoletes RFC 1515. ietf-hubmib-mau-mib-v3-04 RFC2668 RFC1515 PROPOSED STANDARD PROPOSED STANDARD RFC3637 Definitions of Managed Objects for the Ethernet WAN Interface Sublayer C.M. Heard Editor September 2003 ASCII 78785 37 mib management information base 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 the Ethernet Wide Area Network (WAN) Interface Sublayer (WIS). The MIB module defined in this memo is an extension of the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface MIB and is implemented in conjunction with it and with the Ethernet-like Interface MIB, the 802.3 Medium Attachment Unit MIB, the Interfaces Group MIB, and the Inverted Stack Table MIB. ietf-hubmib-wis-mib-07 PROPOSED STANDARD PROPOSED STANDARD RFC3638 Applicability Statement for Reclassification of RFC 1643 to Historic Status J. Flick C. M. Heard September 2003 ASCII 8676 5 ETHER-MIB MIB Network Management SNMP Ethernet This memo recommends that RFC 1643 be reclassified as an Historic document and provides the supporting motivation for that recommendation. ietf-hubmib-1643-to-historic-01 RFC1643 INFORMATIONAL INFORMATIONAL RFC3639 Considerations on the use of a Service Identifier in Packet Headers M. St. Johns Editor G. Huston Editor IAB October 2003 ASCII 15389 8 port fields protocol number This memo describes some considerations relating to the use of IP protocol number fields and payload protocol (e.g., TCP) port fields to identify particular services that may be associated with that port number or protocol number. iab-service-id-considerations-02 INFORMATIONAL INFORMATIONAL RFC3640 RTP Payload Format for Transport of MPEG-4 Elementary Streams J. van der Meer D. Mackie V. Swaminathan D. Singer P. Gentric November 2003 ASCII 102606 43 real time transport protocol audio video streams The Motion Picture Experts Group (MPEG) Committee (ISO/IEC JTC1/SC29 WG11) is a working group in ISO that produced the MPEG-4 standard. MPEG defines tools to compress content such as audio-visual information into elementary streams. This specification defines a simple, but generic RTP payload format for transport of any non-multiplexed MPEG-4 elementary stream. ietf-avt-mpeg4-simple-08 PROPOSED STANDARD PROPOSED STANDARD RFC3641 Generic String Encoding Rules (GSER) for ASN.1 Types S. Legg October 2003 ASCII 34207 16 asn.1 abstract syntax notation This document defines a set of Abstract Syntax Notation One (ASN.1) encoding rules, called the Generic String Encoding Rules (GSER), that produce a human readable text encoding for values of any given ASN.1 data type. legg-ldap-gser-04 PROPOSED STANDARD PROPOSED STANDARD RFC3642 Common Elements of Generic String Encoding Rules (GSER) Encodings S. Legg October 2003 ASCII 27774 13 asn.1 abstract syntax notation The Generic String Encoding Rules (GSER) describe a human readable text encoding for an Abstract Syntax Notation One (ASN.1) value of any ASN.1 type. Specifications making use of GSER may wish to provide an equivalent Augmented Backus-Naur Form (ABNF) description of the GSER encoding for a particular ASN.1 type as a convenience for implementors. This document supports such specifications by providing equivalent ABNF for the GSER encodings for ASN.1 types that commonly occur in Lightweight Directory Access Protocol (LDAP) syntaxes. legg-ldap-gser-abnf-07 PROPOSED STANDARD PROPOSED STANDARD RFC3643 Fibre Channel (FC) Frame Encapsulation R. Weber M. Rajagopal F. Travostino M. O'Donnell C. Monia M. Merhar December 2003 ASCII 39980 20 ips ip storage frame header This document describes the common Fibre Channel (FC) frame encapsulation format and a procedure for the measurement and calculation of frame transit time through the IP network. This specification is intended for use by any IETF protocol that encapsulates FC frames. ietf-ips-fcencapsulation-08 PROPOSED STANDARD PROPOSED STANDARD RFC3644 Policy Quality of Service (QoS) Information Model Y. Snir Y. Ramberg J. Strassner R. Cohen B. Moore November 2003 ASCII 170150 73 integrated differentiated object oriented This document presents an object-oriented information model for representing Quality of Service (QoS) network management policies. This document is based on the IETF Policy Core Information Model and its extensions. It defines an information model for QoS enforcement for differentiated and integrated services using policy. It is important to note that this document defines an information model, which by definition is independent of any particular data storage mechanism and access protocol. ietf-policy-qos-info-model-05 PROPOSED STANDARD PROPOSED STANDARD RFC3645 Generic Security Service Algorithm for Secret Key Transaction Authentication for DNS (GSS-TSIG) S. Kwan P. Garg J. Gilroy L. Esibov J. Westhead R. Hall October 2003 ASCII 56162 26 TSIG domain name system transaction signature The Secret Key Transaction Authentication for DNS (TSIG) protocol provides transaction level authentication for DNS. TSIG is extensible through the definition of new algorithms. This document specifies an algorithm based on the Generic Security Service Application Program Interface (GSS-API) (RFC2743). This document updates RFC 2845. ietf-dnsext-gss-tsig-06 RFC2845 PROPOSED STANDARD PROPOSED STANDARD RFC3646 DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) R. Droms Editor December 2003 ASCII 13312 7 domain name system service server client This document describes Dynamic Host Configuration Protocol for IPv6 (DHCPv6) options for passing a list of available DNS recursive name servers and a domain search list to a client. ietf-dhc-dhcpv6-opt-dnsconfig-04 PROPOSED STANDARD PROPOSED STANDARD RFC3647 Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework S. Chokhani W. Ford R. Sabett C. Merrill S. Wu November 2003 ASCII 228124 94 pkix encryption security authentication This document presents a framework to assist the writers of certificate policies or certification practice statements for participants within public key infrastructures, such as certification authorities, policy authorities, and communities of interest that wish to rely on certificates. In particular, the framework provides a comprehensive list of topics that potentially (at the writer's discretion) need to be covered in a certificate policy or a certification practice statement. This document supersedes RFC 2527. ietf-pkix-ipki-new-rfc2527-02 RFC2527 INFORMATIONAL INFORMATIONAL RFC3648 Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol J. Whitehead J. Reschke Editor December 2003 ASCII 57147 30 server client semantics ordering orderpatch method position header ordering-type header This specification extends the Web Distributed Authoring and Versioning (WebDAV) Protocol to support the server-side ordering of collection members. Of particular interest are orderings that are not based on property values, and so cannot be achieved using a search protocol's ordering option and cannot be maintained automatically by the server. Protocol elements are defined to let clients specify the position in the ordering of each collection member, as well as the semantics governing the ordering. ietf-webdav-ordering-protocol-10 PROPOSED STANDARD PROPOSED STANDARD RFC3649 HighSpeed TCP for Large Congestion Windows S. Floyd December 2003 ASCII 79801 34 transmission control protocol round-trip rate packet The proposals in this document are experimental. While they may be deployed in the current Internet, they do not represent a consensus that this is the best method for high-speed congestion control. In particular, we note that alternative experimental proposals are likely to be forthcoming, and it is not well understood how the proposals in this document will interact with such alternative proposals. This document proposes HighSpeed TCP, a modification to TCP's congestion control mechanism for use with TCP connections with large congestion windows. The congestion control mechanisms of the current Standard TCP constrains the congestion windows that can be achieved by TCP in realistic environments. For example, for a Standard TCP connection with 1500-byte packets and a 100 ms round-trip time, achieving a steady-state throughput of 10 Gbps would require an average congestion window of 83,333 segments, and a packet drop rate of at most one congestion event every 5,000,000,000 packets (or equivalently, at most one congestion event every 1 2/3 hours). This is widely acknowledged as an unrealistic constraint. To address his limitation of TCP, this document proposes HighSpeed TCP, and solicits experimentation and feedback from the wider community. ietf-tsvwg-highspeed-01 EXPERIMENTAL EXPERIMENTAL RFC3650 Handle System Overview S. Sun L. Lannom B. Boesch November 2003 ASCII 54927 21 name service This document provides an overview of the Handle System in terms of its namespace and service architecture, as well as its relationship to other Internet services such as DNS, LDAP/X.500, and URNs. The Handle System is a general-purpose global name service that allows secured name resolution and administration over networks such as the Internet. The Handle System manages handles, which are unique names for digital objects and other Internet resources. sun-handle-system-12 INFORMATIONAL INFORMATIONAL RFC3651 Handle System Namespace and Service Definition S. Sun S. Reilly L. Lannom November 2003 ASCII 104479 41 name service The Handle System is a general-purpose global name service that allows secured name resolution and administration over the public Internet. This document provides a detailed description of the Handle System namespace, and its data, service, and operation models. The namespace definition specifies the handle syntax and its semantic structure. The data model defines the data structures used by the Handle System protocol and any pre-defined data types for carrying out the handle service. The service model provides definitions of various Handle System components and explains how they work together over the network. Finally, the Handle System operation model describes its service operation in terms of messages transmitted between client and server, and the client authentication process based on the Handle System authentication protocol. sun-handle-system-def-08 INFORMATIONAL INFORMATIONAL RFC3652 Handle System Protocol (ver 2.1) Specification S. Sun S. Reilly L. Lannom J. Petrone November 2003 ASCII 124380 53 name service The Handle System is a general-purpose global name service that allows secured name resolution and administration over the public Internet. This document describes the protocol used for client software to access the Handle System for both handle resolution and administration. The protocol specifies the procedure for a client software to locate the responsible handle server of any given handle. It also defines the messages exchanged between the client and server for any handle operation. sun-handle-system-protocol-05 INFORMATIONAL INFORMATIONAL RFC3653 XML-Signature XPath Filter 2.0 J. Boyer M. Hughes J. Reagle December 2003 ASCII 32258 15 extensible markup language digital signature XML Signature recommends a standard means for specifying information content to be digitally signed and for representing the resulting digital signatures in XML. Some applications require the ability to specify a subset of a given XML document as the information content to be signed. The XML Signature specification meets this requirement with the XPath transform. However, this transform can be difficult to implement efficiently with existing technologies. This specification defines a new XML Signature transform to facilitate the development of efficient document subsetting implementations that interoperate under similar performance profiles. This document is the W3C XML Signature XPath-Filter 2.0 Recommendation. This document has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited as a normative reference from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web. ietf-xmldsig-xpf2-01 INFORMATIONAL INFORMATIONAL RFC3654 Requirements for Separation of IP Control and Forwarding H. Khosravi Editor T. Anderson Editor November 2003 ASCII 40418 18 forces forwarding control element separation data This document introduces the Forwarding and Control Element Separation (ForCES) architecture and defines a set of associated terminology. This document also defines a set of architectural, modeling, and protocol requirements to logically separate the control and data forwarding planes of an IP (IPv4, IPv6, etc.) networking device. ietf-forces-requirements-10 INFORMATIONAL INFORMATIONAL RFC3655 Redefinition of DNS Authenticated Data (AD) bit B. Wellington O. Gudmundsson November 2003 ASCII 15646 8 DNS-SECEXT dns authentication This document alters the specification defined in RFC 2535. Based on implementation experience, the Authenticated Data (AD) bit in the DNS header is not useful. This document redefines the AD bit such that it is only set if all answers or records proving that no answers exist in the response has been cryptographically verified or otherwise meets the server's local security policy. ietf-dnsext-ad-is-secure-06 RFC4033 RFC4034 RFC4035 RFC2535 PROPOSED STANDARD PROPOSED STANDARD RFC3656 The Mailbox Update (MUPDATE) Distributed Mailbox Database Protocol R. Siemborski December 2003 ASCII 35509 19 imap pop3 post office protocol internet message access As the demand for high-performance mail delivery agents increases, it becomes apparent that single-machine solutions are inadequate to the task, both because of capacity limits and that the failure of the single machine means a loss of mail delivery for all users. It is preferable to allow many machines to share the responsibility of mail delivery. The Mailbox Update (MUPDATE) protocol allows a group of Internet Message Access Protocol (IMAP) or Post Office Protocol - Version 3 (POP3) servers to function with a unified mailbox namespace. This document is intended to serve as a reference guide to that protocol. siemborski-mupdate-04 EXPERIMENTAL EXPERIMENTAL RFC3657 Use of the Camellia Encryption Algorithm in Cryptographic Message Syntax (CMS) S. Moriai A. Kato January 2004 ASCII 26282 14 security mail content key This document specifies the conventions for using the Camellia encryption algorithm for encryption with the Cryptographic Message Syntax (CMS). ietf-smime-camellia-05 PROPOSED STANDARD PROPOSED STANDARD RFC3658 Delegation Signer (DS) Resource Record (RR) O. Gudmundsson December 2003 ASCII 42120 19 zone cut zone key security dns domain name system The delegation signer (DS) resource record (RR) is inserted at a zone cut (i.e., a delegation point) to indicate that the delegated zone is digitally signed and that the delegated zone recognizes the indicated key as a valid zone key for the delegated zone. The DS RR is a modification to the DNS Security Extensions definition, motivated by operational considerations. The intent is to use this resource record as an explicit statement about the delegation, rather than relying on inference. This document defines the DS RR, gives examples of how it is used and describes the implications on resolvers. This change is not backwards compatible with RFC 2535. This document updates RFC 1035, RFC 2535, RFC 3008 and RFC 3090. ietf-dnsext-delegation-signer-15 RFC4033 RFC4034 RFC4035 RFC3090 RFC3008 RFC2535 RFC1035 RFC3755 PROPOSED STANDARD PROPOSED STANDARD RFC3660 Basic Media Gateway Control Protocol (MGCP) Packages B. Foster F. Andreasen December 2003 ASCII 145147 64 generic line trunk handset dtmf dual tone multifrequency This document provides a basic set of Media Gateway Control Protocol (MGCP) packages. The generic, line, trunk, handset, RTP, DTMF (Dual Tone Multifrequency), announcement server and script packages are updates of packages from RFC 2705 with additional explanation and in some cases new versions of these packages. In addition to these, five new packages are defined here. These are the signal list, resource reservation, media format, supplementary services and digit map extension packages. foster-mgcp-basic-packages-10 RFC2705 INFORMATIONAL INFORMATIONAL RFC3661 Media Gateway Control Protocol (MGCP) Return Code Usage B. Foster C. Sivachelvan December 2003 ASCII 49898 24 guidelines call agent implementation This document provides implementation guidelines for the use of return codes in RFC 3435, Media Gateway Control Protocol (MGCP) Version 1.0. Return codes in RFC 3435 do not cover all possible specific situations that may ever occur in a gateway. That is not possible and not necessary. What is important is to ensure that the Call Agent that receives a return code behaves appropriately and consistently for the given situation. The purpose of this document is to provide implementation guidelines to ensure that consistency. foster-mgcp-returncodes-03 RFC3435 INFORMATIONAL INFORMATIONAL RFC3662 A Lower Effort Per-Domain Behavior (PDB) for Differentiated Services R. Bless K. Nichols K. Wehrle December 2003 ASCII 39029 17 traffic network ds le This document proposes a differentiated services per-domain behavior (PDB) whose traffic may be "starved" (although starvation is not strictly required) in a properly functioning network. This is in contrast to the Internet's "best-effort" or "normal Internet traffic" model, where prolonged starvation indicates network problems. In this sense, the proposed PDB's traffic is forwarded with a "lower" priority than the normal "best-effort" Internet traffic, thus the PDB is called "Lower Effort" (LE). Use of this PDB permits a network operator to strictly limit the effect of its traffic on "best-effort"/"normal" or all other Internet traffic. This document gives some example uses, but does not propose constraining the PDB's use to any particular type of traffic. bless-diffserv-pdb-le-01 INFORMATIONAL INFORMATIONAL RFC3663 Domain Administrative Data in Lightweight Directory Access Protocol (LDAP) A. Newton December 2003 ASCII 42260 21 referral types well-known Domain registration data has typically been exposed to the general public via Nicname/Whois for administrative purposes. This document describes the Referral Lightweight Directory Access Protocol (LDAP) Service, an experimental service using LDAP and well-known LDAP types to make domain administrative data available. newton-ldap-whois-03 EXPERIMENTAL EXPERIMENTAL RFC3664 The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE) P. Hoffman January 2004 ASCII 6711 4 security ipsec advanced encryption standard mac message authentication code Some implementations of IP Security (IPsec) may want to use a pseudo-random function derived from the Advanced Encryption Standard (AES). This document describes such an algorithm, called AES-XCBC-PRF-128. ietf-ipsec-aes-xcbc-prf-01 PROPOSED STANDARD PROPOSED STANDARD RFC3665 Session Initiation Protocol (SIP) Basic Call Flow Examples A. Johnston S. Donovan R. Sparks C. Cunningham K. Summers December 2003 ASCII 163159 94 user agent client proxy redirect This document gives examples of Session Initiation Protocol (SIP) call flows. Elements in these call flows include SIP User Agents and Clients, SIP Proxy and Redirect Servers. Scenarios include SIP Registration and SIP session establishment. Call flow diagrams and message details are shown. ietf-sipping-basic-call-flows-02 BCP0075 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3666 Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows A. Johnston S. Donovan R. Sparks C. Cunningham K. Summers December 2003 ASCII 200478 118 user proxy gateway telephony This document contains best current practice examples of Session Initiation Protocol (SIP) call flows showing interworking with the Public Switched Telephone Network (PSTN). Elements in these call flows include SIP User Agents, SIP Proxy Servers, and PSTN Gateways. Scenarios include SIP to PSTN, PSTN to SIP, and PSTN to PSTN via SIP. PSTN telephony protocols are illustrated using ISDN (Integrated Services Digital Network), ISUP (ISDN User Part), and FGB (Feature Group B) circuit associated signaling. PSTN calls are illustrated using global telephone numbers from the PSTN and private extensions served on by a PBX (Private Branch Exchange). Call flow diagrams and message details are shown. ietf-sipping-pstn-call-flows-02 BCP0076 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3667 IETF Rights in Contributions S. Bradner February 2004 ASCII 43297 18 intellectual property rights copyright ipr The IETF policies about rights in Contributions to the IETF are designed to ensure that such Contributions can be made available to the IETF and Internet communities while permitting the authors to retain as many rights as possible. This memo details the IETF policies on rights in Contributions to the IETF. It also describes the objectives that the policies are designed to meet. This memo updates RFC 2026, and, with RFC 3668, replaces Section 10 of RFC 2026. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-ipr-submission-rights-08 RFC3978 RFC2026 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3668 Intellectual Property Rights in IETF Technology S. Bradner February 2004 ASCII 41365 17 ipr copyright The IETF policies about Intellectual Property Rights (IPR), such as patent rights, relative to technologies developed in the IETF are designed to ensure that IETF working groups and participants have as much information about any IPR constraints on a technical proposal as possible. The policies are also intended to benefit the Internet community and the public at large, while respecting the legitimate rights of IPR holders. This memo details the IETF policies concerning IPR related to technology worked on within the IETF. It also describes the objectives that the policies are designed to meet. This memo updates RFC 2026 and, with RFC 3667, replaces Section 10 of RFC 2026. This memo also updates paragraph 4 of Section 3.2 of RFC 2028, for all purposes, including reference [2] in RFC 2418. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-ipr-technology-rights-12 RFC3979 RFC2026 RFC2028 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3669 Guidelines for Working Groups on Intellectual Property Issues S. Brim February 2004 ASCII 40946 17 ipr copyright This memo lays out a conceptual framework and rules of thumb useful for working groups dealing with Intellectual Property Rights (IPR) issues. It documents specific examples of how IPR issues have been dealt with in the IETF. This memo provides information for the Internet community. ietf-ipr-wg-guidelines-05 INFORMATIONAL INFORMATIONAL RFC3670 Information Model for Describing Network Device QoS Datapath Mechanisms B. Moore D. Durham J. Strassner A. Westerinen W. Weiss January 2004 ASCII 221687 97 quality of service host netowrk devices traffic The purpose of this document is to define an information model to describe the quality of service (QoS) mechanisms inherent in different network devices, including hosts. Broadly speaking, these mechanisms describe the properties common to selecting and conditioning traffic through the forwarding path (datapath) of a network device. This selection and conditioning of traffic in the datapath spans both major QoS architectures: Differentiated Services and Integrated Services. This document should be used with the QoS Policy Information Model (QPIM) to model how policies can be defined to manage and configure the QoS mechanisms (i.e., the classification, marking, metering, dropping, queuing, and scheduling functionality) of devices. Together, these two documents describe how to write QoS policy rules to configure and manage the QoS mechanisms present in the datapaths of devices. This document, as well as QPIM, are information models. That is, they represent information independent of a binding to a specific type of repository ietf-policy-qos-device-info-model-10 PROPOSED STANDARD PROPOSED STANDARD RFC3671 Collective Attributes in the Lightweight Directory Access Protocol (LDAP) K. Zeilenga December 2003 ASCII 17912 10 x.500 information model schema X.500 collective attributes allow common characteristics to be shared between collections of entries. This document summarizes the X.500 information model for collective attributes and describes use of collective attributes in LDAP (Lightweight Directory Access Protocol). This document provides schema definitions for collective attributes for use in LDAP. zeilenga-ldap-collective-08 PROPOSED STANDARD PROPOSED STANDARD RFC3672 Subentries in the Lightweight Directory Access Protocol (LDAP) K. Zeilenga December 2003 ASCII 24447 12 special subtree In X.500 directories, subentries are special entries used to hold information associated with a subtree or subtree refinement. This document adapts X.500 subentries mechanisms for use with the Lightweight Directory Access Protocol (LDAP). zeilenga-ldap-subentry-07 PROPOSED STANDARD PROPOSED STANDARD RFC3673 Lightweight Directory Access Protocol version 3 (LDAPv3): All Operational Attributes K. Zeilenga December 2003 ASCII 10003 5 user mechanisms extension The Lightweight Directory Access Protocol (LDAP) supports a mechanism for requesting the return of all user attributes but not all operational attributes. This document describes an LDAP extension which clients may use to request the return of all operational attributes. zeilenga-ldap-opattrs-05 PROPOSED STANDARD PROPOSED STANDARD RFC3674 Feature Discovery in Lightweight Directory Access Protocol (LDAP) K. Zeilenga December 2003 ASCII 10282 5 elective extensions mechanisms The Lightweight Directory Access Protocol (LDAP) is an extensible protocol with numerous elective features. This document introduces a general mechanism for discovery of elective features and extensions which cannot be discovered using existing mechanisms. zeilenga-ldap-features-05 PROPOSED STANDARD PROPOSED STANDARD RFC3675 .sex Considered Dangerous D. Eastlake 3rd February 2004 ASCII 53211 22 top level domains tld ip addresses internet protocol filters Periodically there are proposals to mandate the use of a special top level name or an IP address bit to flag "adult" or "unsafe" material or the like. This document explains why this is an ill considered idea from the legal, philosophical, and particularly, the technical points of view. eastlake-xxx-05 INFORMATIONAL INFORMATIONAL RFC3676 The Text/Plain Format and DelSp Parameters R. Gellens February 2004 ASCII 42441 20 media type mime multipurpose internet mail extension This specification establishes two parameters (Format and DelSP) to be used with the Text/Plain media type. In the presence of these parameters, trailing whitespace is used to indicate flowed lines and a canonical quote indicator is used to indicate quoted lines. This results in an encoding which appears as normal Text/Plain in older implementations, since it is in fact normal Text/Plain, yet provides for superior wrapping/flowing, and quoting. This document supersedes the one specified in RFC 2646, "The Text/Plain Format Parameter", and adds the DelSp parameter to accommodate languages/coded character sets in which ASCII spaces are not used or appear rarely. [STANDARDS TRACK] gellens-format-bis-04 RFC2646 PROPOSED STANDARD PROPOSED STANDARD RFC3677 IETF ISOC Board of Trustee Appointment Procedures L. Daigle Editor Internet Architecture Board December 2003 ASCII 13008 7 internet society bot engineering task force This memo outlines the process by which the IETF makes a selection of an Internet Society (ISOC) Board of Trustees appointment. iab-isocbot-01 BCP0077 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3678 Socket Interface Extensions for Multicast Source Filters D. Thaler B. Fenner B. Quinn January 2004 ASCII 36320 18 ip internet protocol application program interface apis input output The Internet Group Management Protocol (IGMPv3) for IPv4 and the Multicast Listener Discovery (MLDv2) for IPv6 add the capability for applications to express source filters on multicast group memberships, which allows receiver applications to determine the set of senders (sources) from which to accept multicast traffic. This capability also simplifies support of one-to-many type multicast applications. This document specifies new socket options and functions to manage source filters for IP Multicast group memberships. It also defines the socket structures to provide input and output arguments to these new application program interfaces (APIs). These extensions are designed to provide access to the source filtering features, while introducing a minimum of change into the system and providing complete compatibility for existing multicast applications. ietf-magma-msf-api-05 INFORMATIONAL INFORMATIONAL RFC3679 Unused Dynamic Host Configuration Protocol (DHCP) Option Codes R. Droms January 2004 ASCII 13804 8 dynamic host configuration protocol internet assigned numbers authority Prior to the publication of RFC 2489 (which was updated by RFC 2939), several option codes were assigned to proposed Dynamic Host Configuration Protocol (DHCP) options that were subsequently never used. This document lists those unused option codes and directs IANA to make these option codes available for assignment to other DHCP options in the future. The document also lists several option codes that are not currently documented in an RFC but should not be made available for reassignment to future DHCP options. ietf-dhc-unused-optioncodes-07 INFORMATIONAL INFORMATIONAL RFC3680 A Session Initiation Protocol (SIP) Event Package for Registrations J. Rosenberg March 2004 ASCII 35403 26 REGISTER event package name event package parameters This document defines a Session Initiation Protocol (SIP) event package for registrations. Through its REGISTER method, SIP allows a user agent to create, modify, and delete registrations. Registrations can also be altered by administrators in order to enforce policy. As a result, these registrations represent a piece of state in the network that can change dynamically. There are many cases where a user agent would like to be notified of changes in this state. This event package defines a mechanism by which those user agents can request and obtain such notifications. [STANDARDS TRACK] ietf-sipping-reg-event-00 PROPOSED STANDARD PROPOSED STANDARD RFC3681 Delegation of E.F.F.3.IP6.ARPA R. Bush R. Fink January 2004 ASCII 7137 4 dns domain name system This document discusses the need for delegation of the E.F.F.3.IP6.ARPA DNS zone in order to enable reverse lookups for 6bone addresses, and makes specific recommendations for the process needed to accomplish this. ymbk-6bone-arpa-delegation-01 BCP0080 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3682 The Generalized TTL Security Mechanism (GTSM) V. Gill J. Heasley D. Meyer February 2004 ASCII 23321 11 time to live packet hop limit The use of a packet's Time to Live (TTL) (IPv4) or Hop Limit (IPv6) to protect a protocol stack from CPU-utilization based attacks has been proposed in many settings (see for example, RFC 2461). This document generalizes these techniques for use by other protocols such as BGP (RFC 1771), Multicast Source Discovery Protocol (MSDP), Bidirectional Forwarding Detection, and Label Distribution Protocol (LDP) (RFC 3036). While the Generalized TTL Security Mechanism (GTSM) is most effective in protecting directly connected protocol peers, it can also provide a lower level of protection to multi-hop sessions. GTSM is not directly applicable to protocols employing flooding mechanisms (e.g., multicast), and use of multi-hop GTSM should be considered on a case-by-case basis. This memo defines an Experimental Protocol for the Internet community. gill-gtsh-04 EXPERIMENTAL EXPERIMENTAL RFC3683 A Practice for Revoking Posting Rights to IETF Mailing Lists M. Rose March 2004 ASCII 15698 13 All self-governing bodies have ways of managing the scope of participant interaction. The IETF uses a consensus-driven process for developing computer-communications standards in an open fashion. An important part of this consensus-driven process is the pervasive use of mailing lists for discussion. Notably, in a small number of cases, a participant has engaged in a "denial-of-service" attack to disrupt the consensus-driven process. Regrettably, as these bad faith attacks become more common, the IETF needs to establish a practice that reduces or eliminates these attacks. This memo recommends such a practice for use by the IETF. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. mrose-ietf-posting-04 BCP0083 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3684 Topology Dissemination Based on Reverse-Path Forwarding (TBRPF) R. Ogier F. Templin M. Lewis February 2004 ASCII 107963 46 proactive routing ad-hoc networks neighbor discovery link-state routing mobile ad-hoc network mobile mesh network packet radio network wireless communications Topology Dissemination Based on Reverse-Path Forwarding (TBRPF) is a proactive, link-state routing protocol designed for mobile ad-hoc networks, which provides hop-by-hop routing along shortest paths to each destination. Each node running TBRPF computes a source tree (providing paths to all reachable nodes) based on partial topology information stored in its topology table, using a modification of Dijkstra's algorithm. To minimize overhead, each node reports only *part* of its source tree to neighbors. TBRPF uses a combination of periodic and differential updates to keep all neighbors informed of the reported part of its source tree. Each node also has the option to report additional topology information (up to the full topology), to provide improved robustness in highly mobile networks. TBRPF performs neighbor discovery using "differential" HELLO messages which report only *changes* in the status of neighbors. This results in HELLO messages that are much smaller than those of other link-state routing protocols such as OSPF. This memo defines an Experimental Protocol for the Internet community. ietf-manet-tbrpf-11 EXPERIMENTAL EXPERIMENTAL RFC3685 SIEVE Email Filtering: Spamtest and VirusTest Extensions C. Daboo February 2004 ASCII 17436 9 messages portable commands The SIEVE mail filtering language "spamtest" and "virustest" extensions permit users to use simple, portable commands for spam and virus tests on email messages. Each extension provides a new test using matches against numeric 'scores'. It is the responsibility of the underlying SIEVE implementation to do the actual checks that result in values returned by the tests. [PROPOSED STANDARD] daboo-sieve-spamtest-04 PROPOSED STANDARD PROPOSED STANDARD RFC3686 Using Advanced Encryption Standard (AES) Counter Mode With IPsec Encapsulating Security Payload (ESP) R. Housley January 2004 ASCII 43777 19 authentication vector cipher block This document describes the use of Advanced Encryption Standard (AES) Counter Mode, with an explicit initialization vector, as an IPsec Encapsulating Security Payload (ESP) confidentiality mechanism. ietf-ipsec-ciph-aes-ctr-05 PROPOSED STANDARD PROPOSED STANDARD RFC3687 Lightweight Directory Access Protocol (LDAP) and X.500 Component Matching Rules S. Legg February 2004 ASCII 96256 42 syntax data schema The syntaxes of attributes in a Lightweight Directory Access Protocol (LDAP) or X.500 directory range from simple data types, such as text string, integer, or boolean, to complex structured data types, such as the syntaxes of the directory schema operational attributes. Matching rules defined for the complex syntaxes usually only provide the most immediately useful matching capability. This document defines generic matching rules that can match any user selected component parts in an attribute value of any arbitrarily complex attribute syntax. [PROPOSED STANDARD] legg-ldapext-component-matching-11 PROPOSED STANDARD PROPOSED STANDARD RFC3688 The IETF XML Registry M. Mealling January 2004 ASCII 17325 8 extensible markup language This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas. mealling-iana-xmlns-registry-05 BCP0081 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3689 General Requirements for Emergency Telecommunication Service (ETS) K. Carlberg R. Atkinson February 2004 ASCII 21680 10 This document presents a list of general requirements in support of Emergency Telecommunications Service (ETS). Solutions to these requirements are not presented in this document. Additional requirements pertaining to specific applications, or types of applications, are to be specified in separate document(s). This memo provides information for the Internet community. ietf-ieprep-ets-general-04 INFORMATIONAL INFORMATIONAL RFC3690 IP Telephony Requirements for Emergency Telecommunication Service (ETS) K. Carlberg R. Atkinson February 2004 ASCII 13919 7 This document presents a list of requirements in support of Emergency Telecommunications Service (ETS) within the context of IP telephony. It is an extension to the general requirements presented in RFC 3689. Solutions to these requirements are not presented in this document. This memo provides information for the Internet community. ietf-ieprep-ets-telephony-07 INFORMATIONAL INFORMATIONAL RFC3691 Internet Message Access Protocol (IMAP) UNSELECT command A. Melnikov February 2004 ASCII 8436 5 mailbox session client This document defines an UNSELECT command that can be used to close the current mailbox in an Internet Message Access Protocol - version 4 (IMAP4) session without expunging it. Certain types of IMAP clients need to release resources associated with the selected mailbox without selecting a different mailbox. While IMAP4 provides this functionality (via a SELECT command with a nonexistent mailbox name or reselecting the same mailbox with EXAMINE command), a more clean solution is desirable. [STANDARDS TRACK] melnikov-imap-unselect-01 PROPOSED STANDARD PROPOSED STANDARD RFC3692 Assigning Experimental and Testing Numbers Considered Useful T. Narten January 2004 ASCII 15054 7 iana internet assigned numbers authority values implementations When experimenting with or extending protocols, it is often necessary to use some sort of protocol number or constant in order to actually test or experiment with the new function, even when testing in a closed environment. For example, to test a new DHCP option, one needs an option number to identify the new function. This document recommends that when writing IANA Considerations sections, authors should consider assigning a small range of numbers for experimentation purposes that implementers can use when testing protocol extensions or other new features. This document reserves some ranges of numbers for experimentation purposes in specific protocols where the need to support experimentation has been identified. narten-iana-experimental-allocations-05 RFC2434 BCP0082 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3693 Geopriv Requirements J. Cuellar J. Morris D. Mulligan J. Peterson J. Polk February 2004 ASCII 68881 30 security privacy lo location object Location-based services, navigation applications, emergency services, management of equipment in the field, and other location-dependent services need geographic location information about a Target (such as a user, resource or other entity). There is a need to securely gather and transfer location information for location services, while at the same time protect the privacy of the individuals involved. This document focuses on the authorization, security and privacy requirements for such location-dependent services. Specifically, it describes the requirements for the Geopriv Location Object (LO) and for the protocols that use this Location Object. This LO is envisioned to be the primary data structure used in all Geopriv protocol exchanges to securely transfer location data. This memo provides information for the Internet community. ietf-geopriv-reqs-04 INFORMATIONAL INFORMATIONAL RFC3694 Threat Analysis of the Geopriv Protocol M. Danley D. Mulligan J. Morris J. Peterson February 2004 ASCII 44364 18 privacy security data information This document provides some analysis of threats against the Geopriv protocol architecture. It focuses on protocol threats, threats that result from the storage of data by entities in the architecture, and threats posed by the abuse of information yielded by Geopriv. Some security properties that meet these threats are enumerated as a reference for Geopriv requirements. This memo provides information for the Internet community. ietf-geopriv-threat-analysis-01 INFORMATIONAL INFORMATIONAL RFC3695 Compact Forward Error Correction (FEC) Schemes M. Luby L. Vicisano February 2004 ASCII 32012 13 content stream delivery multicast internet protocol This document introduces some Forward Error Correction (FEC) schemes that supplement the FEC schemes described in RFC 3452. The primary benefits of these additional FEC schemes are that they are designed for reliable bulk delivery of large objects using a more compact FEC Payload ID, and they can be used to sequentially deliver blocks of an object of indeterminate length. Thus, they more flexibly support different delivery models with less packet header overhead. This document also describes the Fully-Specified FEC scheme corresponding to FEC Encoding ID 0. This Fully-Specified FEC scheme requires no FEC coding and is introduced primarily to allow simple interoperability testing between different implementations of protocol instantiations that use the FEC building block. This memo defines an Experimental Protocol for the Internet community. ietf-rmt-bb-fec-supp-compact-01 EXPERIMENTAL EXPERIMENTAL RFC3696 Application Techniques for Checking and Transformation of Names J. Klensin February 2004 ASCII 39238 16 top-level domains tlds Many Internet applications have been designed to deduce top-level domains (or other domain name labels) from partial information. The introduction of new top-level domains, especially non-country-code ones, has exposed flaws in some of the methods used by these applications. These flaws make it more difficult, or impossible, for users of the applications to access the full Internet. This memo discusses some of the techniques that have been used and gives some guidance for minimizing their negative impact as the domain name environment evolves. This document draws summaries of the applicable rules together in one place and supplies references to the actual standards. This memo provides information for the Internet community. klensin-name-filters-03 INFORMATIONAL INFORMATIONAL RFC3697 IPv6 Flow Label Specification J. Rajahalme A. Conta B. Carpenter S. Deering March 2004 ASCII 21296 9 nodes packets This document specifies the IPv6 Flow Label field and the minimum requirements for IPv6 source nodes labeling flows, IPv6 nodes forwarding labeled packets, and flow state establishment methods. Even when mentioned as examples of possible uses of the flow labeling, more detailed requirements for specific use cases are out of scope for this document. The usage of the Flow Label field enables efficient IPv6 flow classification based only on IPv6 main header fields in fixed positions. [STANDARDS TRACK] ietf-ipv6-flow-label-09 PROPOSED STANDARD PROPOSED STANDARD RFC3698 Lightweight Directory Access Protocol (LDAP): Additional Matching Rules K. Zeilenga Editor February 2004 ASCII 17562 9 lightweight directory access protocol directory services This document provides a collection of matching rules for use with the Lightweight Directory Access Protocol (LDAP). As these matching rules are simple adaptations of matching rules specified for use with the X.500 Directory, most are already in wide use. [STANDARDS TRACK] zeilenga-ldap-user-schema-mr-00 RFC2798 PROPOSED STANDARD PROPOSED STANDARD RFC3700 Internet Official Protocol Standards J. Reynolds Editor S. Ginoza Editor July 2004 ASCII 148273 54 This memo contains a snapshot of the state of standardization of protocols used in the Internet as of July 22, 2004. It lists official protocol standards and Best Current Practice RFCs; it is not a complete index to the RFC series. The latest version of this memo is designated STD 1. [STANDARDS TRACK] RFC3600 STD0001 STANDARD STANDARD RFC3701 6bone (IPv6 Testing Address Allocation) Phaseout R. Fink R. Hinden March 2004 ASCII 12019 6 internet protocol protocotype software architecture The 6bone was established in 1996 by the IETF as an IPv6 Testbed network to enable various IPv6 testing as well as to assist in the transitioning of IPv6 into the Internet. It operates under the IPv6 address allocation 3FFE::/16 from RFC 2471. As IPv6 is beginning its production deployment it is appropriate to plan for the phaseout of the 6bone. This document establishes a plan for a multi-year phaseout of the 6bone and its address allocation on the assumption that the IETF is the appropriate place to determine this. This document obsoletes RFC 2471, "IPv6 Testing Address Allocation", December, 1998. RFC 2471 will become historic. This memo provides information for the Internet community. fink-6bone-phaseout-04 RFC2471 INFORMATIONAL INFORMATIONAL RFC3702 Authentication, Authorization, and Accounting Requirements for the Session Initiation Protocol (SIP) J. Loughney G. Camarillo February 2004 ASCII 31243 15 As Session Initiation Protocol (SIP) services are deployed on the Internet, there is a need for authentication, authorization, and accounting of SIP sessions. This document sets out the basic requirements for this work. This memo provides information for the Internet community. ietf-sipping-aaa-req-04 INFORMATIONAL INFORMATIONAL RFC3703 Policy Core Lightweight Directory Access Protocol (LDAP) Schema J. Strassner B. Moore R. Moats E. Ellesson February 2004 ASCII 142983 61 mapping classes This document defines a mapping of the Policy Core Information Model to a form that can be implemented in a directory that uses Lightweight Directory Access Protocol (LDAP) as its access protocol. This model defines two hierarchies of object classes: structural classes representing information for representing and controlling policy data as specified in RFC 3060, and relationship classes that indicate how instances of the structural classes are related to each other. Classes are also added to the LDAP schema to improve the performance of a client's interactions with an LDAP server when the client is retrieving large amounts of policy-related information. These classes exist only to optimize LDAP retrievals: there are no classes in the information model that correspond to them. [STANDARDS TRACK] ietf-policy-core-schema-16 PROPOSED STANDARD PROPOSED STANDARD RFC3704 Ingress Filtering for Multihomed Networks F. Baker P. Savola March 2004 ASCII 35942 16 ISP Internet Service Provider Internet Protocol DOS BCP 38, RFC 2827, is designed to limit the impact of distributed denial of service attacks, by denying traffic with spoofed addresses access to the network, and to help ensure that traffic is traceable to its correct source network. As a side effect of protecting the Internet against such attacks, the network implementing the solution also protects itself from this and other attacks, such as spoofed management access to networking equipment. There are cases when this may create problems, e.g., with multihoming. This document describes the current ingress filtering operational mechanisms, examines generic issues related to ingress filtering, and delves into the effects on multihoming in particular. This memo updates RFC 2827. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. savola-bcp38-multihoming-update-03 RFC2827 BCP0084 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3705 High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals B. Ray R. Abbi February 2004 ASCII 24158 11 management information base This document presents a set of High Capacity Textual Conventions for use in MIB modules which require performance history based upon 15 minute intervals. The Textual Conventions defined in this document extend the conventions presented in RFC 3593 to 64 bit resolution using the conventions presented in RFC 2856. [STANDARDS TRACK] ietf-adslmib-hc-tc-07 PROPOSED STANDARD PROPOSED STANDARD RFC3706 A Traffic-Based Method of Detecting Dead Internet Key Exchange (IKE) Peers G. Huang S. Beaulieu D. Rochefort February 2004 ASCII 30196 13 security authentication dead peer detection dpd keepalive This document describes the method detecting a dead Internet Key Exchange (IKE) peer that is presently in use by a number of vendors. The method, called Dead Peer Detection (DPD) uses IPSec traffic patterns to minimize the number of IKE messages that are needed to confirm liveness. DPD, like other keepalive mechanisms, is needed to determine when to perform IKE peer failover, and to reclaim lost resources. This memo provides information for the Internet community. ietf-ipsec-dpd-04 INFORMATIONAL INFORMATIONAL RFC3707 Cross Registry Internet Service Protocol (CRISP) Requirements A. Newton February 2004 ASCII 52411 26 directory services domain Internet registries expose administrative and operational data via varying directory services. This document defines functional requirements for the directory services of domain registries and the common base requirements for extending the use of these services for other types of Internet registries. This memo provides information for the Internet community. ietf-crisp-requirements-06 INFORMATIONAL INFORMATIONAL RFC3708 Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious Retransmissions E. Blanton M. Allman February 2004 ASCII 20818 9 TCP and Stream Control Transmission Protocol (SCTP) provide notification of duplicate segment receipt through Duplicate Selective Acknowledgement (DSACKs) and Duplicate Transmission Sequence Number (TSN) notification, respectively. This document presents conservative methods of using this information to identify unnecessary retransmissions for various applications. This memo defines an Experimental Protocol for the Internet community. ietf-tsvwg-dsack-use-02 EXPERIMENTAL EXPERIMENTAL RFC3709 Internet X.509 Public Key Infrastructure: Logotypes in X.509 Certificates S. Santesson R. Housley T. Freeman February 2004 ASCII 46453 21 authentication security identification This document specifies a certificate extension for including logotypes in public key certificates and attribute certificates. [STANDARDS TRACK] ietf-pkix-logotypes-13 PROPOSED STANDARD PROPOSED STANDARD RFC3710 An IESG charter H. Alvestrand February 2004 ASCII 24912 12 internet engineering steering group This memo provides a charter for the Internet Engineering Steering Group (IESG), a management function of the Internet Engineering Task Force (IETF). It is meant to document the charter of the IESG as it is presently understood. This memo provides information for the Internet community. iesg-charter-03 RFC3932 INFORMATIONAL INFORMATIONAL RFC3711 The Secure Real-time Transport Protocol (SRTP) M. Baugher D. McGrew M. Naslund E. Carrara K. Norrman March 2004 ASCII 134270 56 authentication traffic cryptographic This document describes the Secure Real-time Transport Protocol (SRTP), a profile of the Real-time Transport Protocol (RTP), which can provide confidentiality, message authentication, and replay protection to the RTP traffic and to the control traffic for RTP, the Real-time Transport Control Protocol (RTCP). [STANDARDS TRACK] ietf-avt-srtp-09 PROPOSED STANDARD PROPOSED STANDARD RFC3712 Lightweight Directory Access Protocol (LDAP): Schema for Printer Services P. Fleming I. McDonald February 2004 ASCII 62301 33 object classes attributes This document defines a schema, object classes and attributes, for printers and printer services, for use with directories that support Lightweight Directory Access Protocol v3 (LDAP-TS). This document is based on the printer attributes listed in Appendix E of Internet Printing Protocol/1.1 (IPP) (RFC 2911). A few additional printer attributes are based on definitions in the Printer MIB (RFC 1759). This memo provides information for the Internet community. fleming-ldap-printer-schema-02 INFORMATIONAL INFORMATIONAL RFC3713 A Description of the Camellia Encryption Algorithm M. Matsui J. Nakajima S. Moriai April 2004 ASCII 25031 15 security key cryptographic This document describes the Camellia encryption algorithm. Camellia is a block cipher with 128-bit block size and 128-, 192-, and 256-bit keys. The algorithm description is presented together with key scheduling part and data randomizing part. This memo provides information for the Internet community. nakajima-camellia-03 INFORMATIONAL INFORMATIONAL RFC3714 IAB Concerns Regarding Congestion Control for Voice Traffic in the Internet S. Floyd J. Kempf Editors March 2004 ASCII 81368 32 end-to-end qos qualify of service voip internet protocol This document discusses IAB concerns about effective end-to-end congestion control for best-effort voice traffic in the Internet. These concerns have to do with fairness, user quality, and with the dangers of congestion collapse. The concerns are particularly relevant in light of the absence of a widespread Quality of Service (QoS) deployment in the Internet, and the likelihood that this situation will not change much in the near term. This document is not making any recommendations about deployment paths for Voice over Internet Protocol (VoIP) in terms of QoS support, and is not claiming that best-effort service can be relied upon to give acceptable performance for VoIP. We are merely observing that voice traffic is occasionally deployed as best-effort traffic over some links in the Internet, that we expect this occasional deployment to continue, and that we have concerns about the lack of effective end-to-end congestion control for this best-effort voice traffic. This memo provides information for the Internet community. iab-congestion-02 INFORMATIONAL INFORMATIONAL RFC3715 IPsec-Network Address Translation (NAT) Compatibility Requirements B. Aboba W. Dixon March 2004 ASCII 43476 18 virtual private networks vpns intranet This document describes known incompatibilities between Network Address Translation (NAT) and IPsec, and describes the requirements for addressing them. Perhaps the most common use of IPsec is in providing virtual private networking capabilities. One very popular use of Virtual Private Networks (VPNs) is to provide telecommuter access to the corporate Intranet. Today, NATs are widely deployed in home gateways, as well as in other locations likely to be used by telecommuters, such as hotels. The result is that IPsec-NAT incompatibilities have become a major barrier in the deployment of IPsec in one of its principal uses. This memo provides information for the Internet community. ietf-ipsec-nat-reqts-06 INFORMATIONAL INFORMATIONAL RFC3716 The IETF in the Large: Administration and Execution IAB Advisory Committee March 2004 ASCII 91326 40 In the fall of 2003, the IETF Chair and the IAB Chair formed an IAB Advisory Committee (AdvComm), with a mandate to review the existing IETF administrative structure and relationships (RFC Editor, IETF Secretariat, IANA) and to propose changes to the IETF management process or structure to improve the overall functioning of the IETF. The AdvComm mandate did not include the standards process itself. This memo provides information for the Internet community. iab-advcomm-01 INFORMATIONAL INFORMATIONAL RFC3717 IP over Optical Networks: A Framework B. Rajagopalan J. Luciani D. Awduche March 2004 ASCII 124421 48 transport infrastructure routers high-speed The Internet transport infrastructure is moving towards a model of high-speed routers interconnected by optical core networks. The architectural choices for the interaction between IP and optical network layers, specifically, the routing and signaling aspects, are maturing. At the same time, a consensus has emerged in the industry on utilizing IP-based protocols for the optical control plane. This document defines a framework for IP over Optical networks, considering both the IP-based control plane for optical networks as well as IP-optical network interactions (together referred to as "IP over optical networks"). This memo provides information for the Internet community. ietf-ipo-framework-05 INFORMATIONAL INFORMATIONAL RFC3718 A Summary of Unicode Consortium Procedures, Policies, Stability, and Public Access R. McGowan February 2004 ASCII 25865 11 This memo describes various internal workings of the Unicode Consortium for the benefit of participants in the IETF. It is intended solely for informational purposes. Included are discussions of how the decision-making bodies of the Consortium work and their procedures, as well as information on public access to the character encoding & standardization processes. rmcgowan-unicode-procs-03 INFORMATIONAL INFORMATIONAL RFC3719 Recommendations for Interoperable Networks using Intermediate System to Intermediate System (IS-IS) J. Parker Editor February 2004 ASCII 33941 15 routing routeing interior gateway protocol igp conformance ip traffic This document discusses a number of differences between the Intermediate System to Intermediate System (IS-IS) protocol as described in ISO 10589 and the protocol as it is deployed today. These differences are discussed as a service to those implementing, testing, and deploying the IS-IS Protocol. A companion document discusses differences between the protocol described in RFC 1195 and the protocol as it is deployed today for routing IP traffic. This memo provides information for the Internet community. ietf-isis-iso-interoperable-02 INFORMATIONAL INFORMATIONAL RFC3720 Internet Small Computer Systems Interface (iSCSI) J. Satran K. Meth C. Sapuntzakis M. Chadalapaka E. Zeidner April 2004 ASCII 578468 257 transport protocol tcp transmission control protocol This document describes a transport protocol for Internet Small Computer Systems Interface (iSCSI) that works on top of TCP. The iSCSI protocol aims to be fully compliant with the standardized SCSI architecture model. SCSI is a popular family of protocols that enable systems to communicate with I/O devices, especially storage devices. SCSI protocols are request/response application protocols with a common standardized architecture model and basic command set, as well as standardized command sets for different device classes (disks, tapes, media-changers etc.). As system interconnects move from the classical bus structure to a network structure, SCSI has to be mapped to network transport protocols. IP networks now meet the performance requirements of fast system interconnects and as such are good candidates to "carry" SCSI. [STANDARDS TRACK] ietf-ips-iscsi-20 RFC3980 PROPOSED STANDARD PROPOSED STANDARD RFC3721 Internet Small Computer Systems Interface (iSCSI) Naming and Discovery M. Bakke J. Hafner J. Hufferd K. Voruganti M. Krueger April 2004 ASCII 47564 22 targets environments scalibilty target initiator scsi device name This document provides examples of the Internet Small Computer Systems Interface (iSCSI; or SCSI over TCP) name construction and discussion of discovery of iSCSI resources (targets) by iSCSI initiators. This document complements the iSCSI protocol document. Flexibility is the key guiding principle behind this document. That is, an effort has been made to satisfy the needs of both small isolated environments, as well as large environments requiring secure/scalable solutions. This memo provides information for the Internet community. ietf-ips-iscsi-name-disc-10 INFORMATIONAL INFORMATIONAL RFC3722 String Profile for Internet Small Computer Systems Interface (iSCSI) Names M. Bakke April 2004 ASCII 14702 8 transport unique global This document describes how to prepare internationalized iSCSI names to increase the likelihood that name input and comparison work in ways that make sense for typical users throughout the world. The Internet Small Computer Systems Interface (iSCSI) protocol provides a way for hosts to access SCSI devices over an IP network. The iSCSI end-points, called initiators and targets, each have a globally-unique name that must be transcribable, as well as easily compared. [STANDARDS TRACK] ietf-ips-iscsi-string-prep-06 PROPOSED STANDARD PROPOSED STANDARD RFC3723 Securing Block Storage Protocols over IP B. Aboba J. Tseng J. Walker V. Rangan F. Travostino April 2004 ASCII 171673 70 internet threat models performance security This document discusses how to secure block storage and storage discovery protocols running over IP (Internet Protocol) using IPsec and IKE (Internet Key Exchange). Threat models and security protocols are developed for iSCSI (Internet Protocol Small Computer System Interface), iFCP (Internet Fibre Channel Storage Networking) and FCIP (Fibre Channel over TCP/IP), as well as the iSNS (Internet Storage Name Server) and SLPv2 (Service Location Protocol v2) discovery protocols. Performance issues and resource constraints are analyzed. [STANDARDS TRACK] ietf-ips-security-19 PROPOSED STANDARD PROPOSED STANDARD RFC3724 The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture J. Kempf R. Austein Editors IAB March 2004 ASCII 37206 14 architectural guideline The end-to-end principle is the core architectural guideline of the Internet. In this document, we briefly examine the development of the end-to-end principle as it has been applied to the Internet architecture over the years. We discuss current trends in the evolution of the Internet architecture in relation to the end-to-end principle, and try to draw some conclusion about the evolution of the end-to-end principle, and thus for the Internet architecture which it supports, in light of these current trends. This memo provides information for the Internet community. iab-e2e-futures-05 INFORMATIONAL INFORMATIONAL RFC3725 Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP) J. Rosenberg J. Peterson H. Schulzrinne G. Camarillo April 2004 ASCII 77308 31 Third party call control refers to the ability of one entity to create a call in which communication is actually between other parties. Third party call control is possible using the mechanisms specified within the Session Initiation Protocol (SIP). However, there are several possible approaches, each with different benefits and drawbacks. This document discusses best current practices for the usage of SIP for third party call control. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-sipping-3pcc-06 BCP0085 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3726 Requirements for Signaling Protocols M. Brunner Editor April 2004 ASCII 98020 42 rsvp resource reservation protocol middleboxes nsis This document defines requirements for signaling across different network environments, such as across administrative and/or technology domains. Signaling is mainly considered for Quality of Service (Qos) such as the Resource Reservation Protocol (RSVP). However, in recent years, several other applications of signaling have been defined. For example, signaling for label distribution in Multiprotocol Label Switching (MPLS) or signaling to middleboxes. To achieve wide applicability of the requirements, the starting point is a diverse set of scenarios/use cases concerning various types of networks and application interactions. This document presents the assumptions before listing the requirements. The requirements are grouped according to areas such as architecture and design goals, signaling flows, layering, performance, flexibility, security, and mobility. This memo provides information for the Internet community. ietf-nsis-req-09 INFORMATIONAL INFORMATIONAL RFC3727 ASN.1 Module Definition for the LDAP and X.500 Component Matching Rules S. Legg February 2004 ASCII 8297 5 lightweight directory access protocol This document updates the specification of the component matching rules for Lightweight Directory Access Protocol (LDAP) and X.500 directories (RFC3687) by collecting the Abstract Syntax Notation One (ASN.1) definitions of the component matching rules into an appropriately identified ASN.1 module so that other specifications may reference the component matching rule definitions from within their own ASN.1 modules. [STANDARDS TRACK] legg-ldap-cmr-module-00 PROPOSED STANDARD PROPOSED STANDARD RFC3728 Definitions of Managed Objects for Very High Speed Digital Subscriber Lines (VDSL) B. Ray R. Abbi February 2004 ASCII 147232 76 management information base mib This document defines a Management Information Base (MIB) module for use with network management protocols in the Internet community. In particular, it describes objects used for managing Very High Speed Digital Subscriber Line (VDSL) interfaces. [STANDARDS TRACK] ietf-adslmib-vdsl-12 PROPOSED STANDARD PROPOSED STANDARD RFC3729 Application Performance Measurement MIB S. Waldbusser March 2004 ASCII 131354 61 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 measuring the application performance as experienced by end-users. [STANDARDS TRACK] ietf-rmonmib-apm-mib-12 PROPOSED STANDARD PROPOSED STANDARD RFC3730 Extensible Provisioning Protocol (EPP) S. Hollenbeck March 2004 ASCII 134337 69 shared framework mapping This document describes an application layer client-server protocol for the provisioning and management of objects stored in a shared central repository. Specified in XML, the protocol defines generic object management operations and an extensible framework that maps protocol operations to objects. This document includes a protocol specification, an object mapping template, and an XML media type registration. [STANDARDS TRACK] ietf-provreg-epp-09 PROPOSED STANDARD PROPOSED STANDARD RFC3731 Extensible Provisioning Protocol (EPP) Domain Name Mapping S. Hollenbeck March 2004 ASCII 92527 45 syntax semantics This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of Internet domain names stored in a shared central repository. Specified in XML, the mapping defines EPP command syntax and semantics as applied to domain names. [STANDARDS TRACK] ietf-provreg-epp-domain-07 PROPOSED STANDARD PROPOSED STANDARD RFC3732 Extensible Provisioning Protocol (EPP) Host Mapping S. Hollenbeck March 2004 ASCII 57082 28 syntax semantics This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of Internet host names stored in a shared central repository. Specified in XML, the mapping defines EPP command syntax and semantics as applied to host names. [STANDARDS TRACK] ietf-provreg-epp-host-07 PROPOSED STANDARD PROPOSED STANDARD RFC3733 Extensible Provisioning Protocol (EPP) Contact Mapping S. Hollenbeck March 2004 ASCII 83091 41 syntax semantics This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of individual or organizational social information identifiers (known as "contacts") stored in a shared central repository. Specified in Extensible Markup Language (XML), the mapping defines EPP command syntax and semantics as applied to contacts. [STANDARDS TRACK] ietf-provreg-epp-contact-07 PROPOSED STANDARD PROPOSED STANDARD RFC3734 Extensible Provisioning Protocol (EPP) Transport Over TCP S. Hollenbeck March 2004 ASCII 19550 9 mapping client server tls transport layer security This document describes how an Extensible Provisioning Protocol (EPP) session is mapped onto a single Transmission Control Protocol (TCP) connection. This mapping requires use of the Transport Layer Security (TLS) protocol to protect information exchanged between an EPP client and an EPP server. [STANDARDS TRACK] ietf-provreg-epp-tcp-06 PROPOSED STANDARD PROPOSED STANDARD RFC3735 Guidelines for Extending the Extensible Provisioning Protocol (EPP) S. Hollenbeck March 2004 ASCII 27326 13 The Extensible Provisioning Protocol (EPP) is an application layer client-server protocol for the provisioning and management of objects stored in a shared central repository. Specified in XML, the protocol defines generic object management operations and an extensible framework that maps protocol operations to objects. This document presents guidelines for use of EPP's extension mechanisms to define new features and object management capabilities. This memo provides information for the Internet community. ietf-provreg-epp-ext-03 INFORMATIONAL INFORMATIONAL RFC3736 Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6 R. Droms April 2004 ASCII 18510 9 Stateless Dynamic Host Configuration Protocol service for IPv6 (DHCPv6) is used by nodes to obtain configuration information, such as the addresses of DNS recursive name servers, that does not require the maintenance of any dynamic state for individual clients. A node that uses stateless DHCP must have obtained its IPv6 addresses through some other mechanism, typically stateless address autoconfiguration. This document explains which parts of RFC 3315 must be implemented in each of the different kinds of DHCP agents so that agent can support stateless DHCP. [STANDARDS TRACK] ietf-dhc-dhcpv6-stateless-04 PROPOSED STANDARD PROPOSED STANDARD RFC3737 IANA Guidelines for the Registry of Remote Monitoring (RMON) MIB modules B. Wijnen A. Bierman April 2004 ASCII 13127 7 management information base internet assigned numbers authority This document defines the procedures for IANA to administer and maintain the Object Identifier (OID) tree under the Remote Monitoring (rmon) root. This memo also documents the currently assigned values. [STANDARDS TRACK] ietf-rmonmib-rmon-oid-assignments-01 PROPOSED STANDARD PROPOSED STANDARD RFC3738 Wave and Equation Based Rate Control (WEBRC) Building Block M. Luby V. Goyal April 2004 ASCII 82584 32 congestion control data delivery multicast ip internet protocol This document specifies Wave and Equation Based Rate Control (WEBRC), which provides rate and congestion control for data delivery. WEBRC is specifically designed to support protocols using IP multicast. It provides multiple-rate, congestion-controlled delivery to receivers, i.e., different receivers joined to the same session may be receiving packets at different rates depending on the bandwidths of their individual connections to the sender and on competing traffic along these connections. WEBRC requires no feedback from receivers to the sender, i.e., it is a completely receiver-driven congestion control protocol. Thus, it is designed to scale to potentially massive numbers of receivers attached to a session from a single sender. Furthermore, because each individual receiver adjusts to the available bandwidth between the sender and that receiver, there is the potential to deliver data to each individual receiver at the fastest possible rate for that receiver, even in a highly heterogeneous network architecture, using a single sender. This memo defines an Experimental Protocol for the Internet community. ietf-rmt-bb-webrc-04 EXPERIMENTAL EXPERIMENTAL RFC3739 Internet X.509 Public Key Infrastructure: Qualified Certificates Profile S. Santesson M. Nystrom T. Polk March 2004 ASCII 67436 34 syntax This document forms a certificate profile, based on RFC 3280, for identity certificates issued to natural persons. The profile defines specific conventions for certificates that are qualified within a defined legal framework, named Qualified Certificates. However, the profile does not define any legal requirements for such Qualified Certificates. The goal of this document is to define a certificate profile that supports the issuance of Qualified Certificates independent of local legal requirements. The profile is however not limited to Qualified Certificates and further profiling may facilitate specific local needs. [STANDARDS TRACK] ietf-pkix-sonof3039-06 RFC3039 PROPOSED STANDARD PROPOSED STANDARD RFC3740 The Multicast Group Security Architecture T. Hardjono B. Weis March 2004 ASCII 65531 26 data packets This document provides an overview and rationale of the multicast security architecture used to secure data packets of large multicast groups. The document begins by introducing a Multicast Security Reference Framework, and proceeds to identify the security services that may be part of a secure multicast solution. This memo provides information for the Internet community. ietf-msec-arch-05 INFORMATIONAL INFORMATIONAL RFC3741 Exclusive XML Canonicalization, Version 1.0 J. Boyer D. Eastlake 3rd J. Reagle March 2004 ASCII 35403 16 extensible markup language namespace Canonical XML specifies a standard serialization of XML that, when applied to a subdocument, includes the subdocument's ancestor context including all of the namespace declarations and attributes in the "xml:" namespace. However, some applications require a method which, to the extent practical, excludes ancestor context from a canonicalized subdocument. For example, one might require a digital signature over an XML payload (subdocument) in an XML message that will not break when that subdocument is removed from its original message and/or inserted into a different context. This requirement is satisfied by Exclusive XML Canonicalization. This memo provides information for the Internet community. ietf-xmldsig-xc14n-02 INFORMATIONAL INFORMATIONAL RFC3742 Limited Slow-Start for TCP with Large Congestion Windows S. Floyd March 2004 ASCII 14840 7 transmission control protocol This document describes an optional modification for TCP's slow-start for use with TCP connections with large congestion windows. For TCP connections that are able to use congestion windows of thousands (or tens of thousands) of MSS-sized segments (for MSS the sender's MAXIMUM SEGMENT SIZE), the current slow-start procedure can result in increasing the congestion window by thousands of segments in a single round-trip time. Such an increase can easily result in thousands of packets being dropped in one round-trip time. This is often counter-productive for the TCP flow itself, and is also hard on the rest of the traffic sharing the congested link. This note describes Limited Slow-Start as an optional mechanism for limiting the number of segments by which the congestion window is increased for one window of data during slow-start, in order to improve performance for TCP connections with large congestion windows. This memo defines an Experimental Protocol for the Internet community. ietf-tsvwg-slowstart-00 EXPERIMENTAL EXPERIMENTAL RFC3743 Joint Engineering Team (JET) Guidelines for Internationalized Domain Names (IDN) Registration and Administration for Chinese, Japanese, and Korean K. Konishi K. Huang H. Qian Y. Ko April 2004 ASCII 74963 33 Achieving internationalized access to domain names raises many complex issues. These are associated not only with basic protocol design, such as how names are represented on the network, compared, and converted to appropriate forms, but also with issues and options for deployment, transition, registration, and administration. The IETF Standards for Internationalized Domain Names, known as "IDNA", focuses on access to domain names in a range of scripts that is broader in scope than the original ASCII. The development process made it clear that use of characters with similar appearances and/or interpretations created potential for confusion, as well as difficulties in deployment and transition. The conclusion was that, while those issues were important, they could best be addressed administratively rather than through restrictions embedded in the protocols. This document defines a set of guidelines for applying restrictions of that type for Chinese, Japanese and Korean (CJK) scripts and the zones that use them and, perhaps, the beginning of a framework for thinking about other zones, languages, and scripts. This memo provides information for the Internet community. jseng-idn-admin-05 INFORMATIONAL INFORMATIONAL RFC3744 Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol G. Clemm J. Reschke E. Sedlar J. Whitehead May 2004 ASCII 146623 72 This document specifies a set of methods, headers, message bodies, properties, and reports that define Access Control extensions to the WebDAV Distributed Authoring Protocol. This protocol permits a client to read and modify access control lists that instruct a server whether to allow or deny operations upon a resource (such as HyperText Transfer Protocol (HTTP) method invocations) by a given principal. A lightweight representation of principals as Web resources supports integration of a wide range of user management repositories. Search operations allow discovery and manipulation of principals using human names. [STANDARDS TRACK] ietf-webdav-acl-13 PROPOSED STANDARD PROPOSED STANDARD RFC3745 MIME Type Registrations for JPEG 2000 (ISO/IEC 15444) D. Singer R. Clark D. Lee April 2004 ASCII 31224 14 multipurpose internet mail extensions joint photographic experts group This document serves to register and document the standard MIME types associated with the ISO/IEC 15444 standards, commonly known as JPEG 2000 (Joint Photographic Experts Group). [STANDARDS TRACK] singer-jp2-02 PROPOSED STANDARD PROPOSED STANDARD RFC3746 Forwarding and Control Element Separation (ForCES) Framework L. Yang R. Dantu T. Anderson R. Gopal April 2004 ASCII 98660 40 network elements This document defines the architectural framework for the ForCES (Forwarding and Control Element Separation) network elements, and identifies the associated entities and their interactions. This is memo provides information for the Internet community. ietf-forces-framework-13 INFORMATIONAL INFORMATIONAL RFC3747 The Differentiated Services Configuration MIB H. Hazewinkel Editor D. Partain Editor April 2004 ASCII 51659 24 management information base diffserv This memo describes a MIB module that provides a conceptual layer between high-level "network-wide" policy definitions that effect configuration of the Differentiated Services (diffserv) subsystem and the instance-specific information that would include such details as the parameters for all the queues associated with each interface in a system. This essentially provides an interface for configuring differentiated services at a conceptually higher layer than that of the Differentiated Services MIB. [PROPOSED STANDARD] ietf-snmpconf-diffpolicy-09 PROPOSED STANDARD PROPOSED STANDARD RFC3748 Extensible Authentication Protocol (EAP) B. Aboba L. Blunk J. Vollbrecht J. Carlson H. Levkowetz Editor June 2004 ASCII 157994 67 PPP-EAP data link layers ppp point-to-point ieee 802 This document defines the Extensible Authentication Protocol (EAP), an authentication framework which supports multiple authentication methods. EAP typically runs directly over data link layers such as Point-to-Point Protocol (PPP) or IEEE 802, without requiring IP. EAP provides its own support for duplicate elimination and retransmission, but is reliant on lower layer ordering guarantees. Fragmentation is not supported within EAP itself; however, individual EAP methods may support this. This document obsoletes RFC 2284. A summary of the changes between this document and RFC 2284 is available in Appendix A. [STANDARDS TRACK] ietf-eap-rfc2284bis-09 RFC2284 PROPOSED STANDARD PROPOSED STANDARD RFC3749 Transport Layer Security Protocol Compression Methods S. Hollenbeck May 2004 ASCII 16411 8 tls lossless data compression handshake protocol The Transport Layer Security (TLS) protocol (RFC 2246) includes features to negotiate selection of a lossless data compression method as part of the TLS Handshake Protocol and to then apply the algorithm associated with the selected method as part of the TLS Record Protocol. TLS defines one standard compression method which specifies that data exchanged via the record protocol will not be compressed. This document describes an additional compression method associated with a lossless data compression algorithm for use with TLS, and it describes a method for the specification of additional TLS compression methods. [STANDARDS TRACK] ietf-tls-compression-07 PROPOSED STANDARD PROPOSED STANDARD RFC3750 Unmanaged Networks IPv6 Transition Scenarios C. Huitema R. Austein S. Satapati R. van der Pol April 2004 ASCII 48153 20 single subnet gateway isp internet service provider This document defines the scenarios in which IPv6 transition mechanisms are to be used in unmanaged networks. In order to evaluate the suitability of these mechanisms, we need to define the scenarios in which these mechanisms have to be used. One specific scope is the "unmanaged network", which typically corresponds to a home or small office network. The scenarios are specific to a single subnet, and are defined in terms of IP connectivity supported by the gateway and the Internet Service Provider (ISP). We first examine the generic requirements of four classes of applications: local, client, peer to peer and server. Then, for each scenario, we infer transition requirements by analyzing the needs for smooth migration of applications from IPv4 to IPv6. This memo provides information for the Internet community. ietf-v6ops-unman-scenarios-03 INFORMATIONAL INFORMATIONAL RFC3751 Omniscience Protocol Requirements S. Bradner April 01 2004 ASCII 20771 9 There have been a number of legislative initiatives in the U.S. and elsewhere over the past few years to use the Internet to actively interfere with allegedly illegal activities of Internet users. This memo proposes a number of requirements for a new protocol, the Omniscience Protocol, that could be used to enable such efforts. This memo provides information for the Internet community. bradner-op-req-01 INFORMATIONAL INFORMATIONAL RFC3752 Open Pluggable Edge Services (OPES) Use Cases and Deployment Scenarios A. Barbir E. Burger R. Chen S. McHenry H. Orman R. Penno April 2004 ASCII 29481 14 This memo provides a discussion of use cases and deployment scenarios for Open Pluggable Edge Services (OPES). The work examines services that could be performed to requests and/or responses. This memo provides information for the Internet community. ietf-opes-scenarios-01 INFORMATIONAL INFORMATIONAL RFC3753 Mobility Related Terminology J. Manner Editor M. Kojo Editor June 2004 ASCII 74143 36 networks ip internet protocol There is a need for common definitions of terminology in the work to be done around IP mobility. This document defines terms for mobility related terminology. The document originated out of work done in the Seamoby Working Group but has broader applicability for terminology used in IETF-wide discourse on technology for mobility and IP networks. Other working groups dealing with mobility may want to take advantage of this terminology. This memo provides information for the Internet community. ietf-seamoby-mobility-terminology-06 INFORMATIONAL INFORMATIONAL RFC3754 IP Multicast in Differentiated Services (DS) Networks R. Bless K. Wehrle April 2004 ASCII 86533 34 internet protocol This document discusses the problems of IP Multicast use in Differentiated Services (DS) networks, expanding on the discussion in RFC 2475 ("An Architecture of Differentiated Services"). It also suggests possible solutions to these problems, describes a potential implementation model, and presents simulation results. This memo provides information for the Internet community. bless-diffserv-multicast-07 INFORMATIONAL INFORMATIONAL RFC3755 Legacy Resolver Compatibility for Delegation Signer (DS) S. Weiler May 2004 ASCII 19812 9 dnssec DNS Security rr resource record DNS-SECEXT dns authentication nsec nextsecure As the DNS Security (DNSSEC) specifications have evolved, the syntax and semantics of the DNSSEC resource records (RRs) have changed. Many deployed nameservers understand variants of these semantics. Dangerous interactions can occur when a resolver that understands an earlier version of these semantics queries an authoritative server that understands the new delegation signer semantics, including at least one failure scenario that will cause an unsecured zone to be unresolvable. This document changes the type codes and mnemonics of the DNSSEC RRs (SIG, KEY, and NXT) to avoid those interactions. [STANDARDS TRACK] ietf-dnsext-dnssec-2535typecode-change-06 RFC4033 RFC4034 RFC4035 RFC3658 RFC2535 RFC3757 RFC3845 PROPOSED STANDARD PROPOSED STANDARD RFC3756 IPv6 Neighbor Discovery (ND) Trust Models and Threats P. Nikander Editor J. Kempf E. Nordmark May 2004 ASCII 56674 23 authentication security key management ietf-send-psreq-04 INFORMATIONAL INFORMATIONAL RFC3757 Domain Name System KEY (DNSKEY) Resource Record (RR) Secure Entry Point (SEP) Flag O. Kolkman J. Schlyter E. Lewis April 2004 ASCII 16868 8 dnssec With the Delegation Signer (DS) resource record (RR), the concept of a public key acting as a secure entry point (SEP) has been introduced. During exchanges of public keys with the parent there is a need to differentiate SEP keys from other public keys in the Domain Name System KEY (DNSKEY) resource record set. A flag bit in the DNSKEY RR is defined to indicate that DNSKEY is to be used as a SEP. The flag bit is intended to assist in operational procedures to correctly generate DS resource records, or to indicate what DNSKEYs are intended for static configuration. The flag bit is not to be used in the DNS verification protocol. This document updates RFC 2535 and RFC 3755. [STANDARDS TRACK] ietf-dnsext-keyrr-key-signing-flag-12 RFC4033 RFC4034 RFC4035 RFC3755 RFC2535 PROPOSED STANDARD PROPOSED STANDARD RFC3758 Stream Control Transmission Protocol (SCTP) Partial Reliability Extension R. Stewart M. Ramalho Q. Xie M. Tuexen P. Conrad May 2004 ASCII 50999 22 init init ack forward tsn This memo describes an extension to the Stream Control Transmission Protocol (SCTP) that allows an SCTP endpoint to signal to its peer that it should move the cumulative ack point forward. When both sides of an SCTP association support this extension, it can be used by an SCTP implementation to provide partially reliable data transmission service to an upper layer protocol. This memo describes the protocol extensions, which consist of a new parameter for INIT and INIT ACK, and a new FORWARD TSN chunk type, and provides one example of a partially reliable service that can be provided to the upper layer via this mechanism. [STANDARDS TRACK] ietf-tsvwg-prsctp-03 PROPOSED STANDARD PROPOSED STANDARD RFC3759 RObust Header Compression (ROHC): Terminology and Channel Mapping Examples L-E. Jonsson April 2004 ASCII 50168 20 encapsulating security payload real-time transport protocol user datagram This document aims to clarify terms and concepts presented in RFC 3095. RFC 3095 defines a Proposed Standard framework with profiles for RObust Header Compression (ROHC). The standard introduces various concepts which might be difficult to understand and especially to relate correctly to the surrounding environments where header compression may be used. This document aims at clarifying these aspects of ROHC, discussing terms such as ROHC instances, ROHC channels, ROHC feedback, and ROHC contexts, and how these terms relate to other terms, like network elements and IP interfaces, commonly used, for example, when addressing MIB issues. This memo provides information for the Internet community. ietf-rohc-terminology-and-examples-02 RFC3095 INFORMATIONAL INFORMATIONAL RFC3760 Securely Available Credentials (SACRED) - Credential Server Framework D. Gustafson M. Just M. Nystrom April 2004 ASCII 49910 22 As the number, and more particularly the number of different types, of devices connecting to the Internet increases, credential mobility becomes an issue for IETF standardization. This document responds to the requirements on protocols for secure exchange of credentials listed in RFC 3157, by presenting an abstract protocol framework. This memo provides information for the Internet community. ietf-sacred-framework-07 INFORMATIONAL INFORMATIONAL RFC3761 The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) P. Faltstrom M. Mealling April 2004 ASCII 41559 18 domain name system This document discusses the use of the Domain Name System (DNS) for storage of E.164 numbers. More specifically, how DNS can be used for identifying available services connected to one E.164 number. It specifically obsoletes RFC 2916 to bring it in line with the Dynamic Delegation Discovery System (DDDS) Application specification found in the document series specified in RFC 3401. It is very important to note that it is impossible to read and understand this document without reading the documents discussed in RFC 3401. [STANDARDS TRACK] ietf-enum-rfc2916bis-07 RFC2916 PROPOSED STANDARD PROPOSED STANDARD RFC3762 Telephone Number Mapping (ENUM) Service Registration for H.323 O. Levin April 2004 ASCII 8450 5 multimedia packet based network The H.323 specification defines a means for building multimedia communication services over an arbitrary Packet Based Network, including the Internet. This document registers a Telephone Number Mapping (ENUM) service for H.323 according to specifications and guidelines in RFC 3761. [STANDARDS TRACK] ietf-enum-h323-01 PROPOSED STANDARD PROPOSED STANDARD RFC3763 One-way Active Measurement Protocol (OWAMP) Requirements S. Shalunov B. Teitelbaum April 2004 ASCII 23360 11 performance metrics delay unidirectional With growing availability of good time sources to network nodes, it becomes increasingly possible to measure one-way IP performance metrics with high precision. To do so in an interoperable manner, a common protocol for such measurements is required. This document specifies requirements for a one-way active measurement protocol (OWAMP) standard. The protocol can measure one-way delay, as well as other unidirectional characteristics, such as one-way loss. This memo provides information for the Internet community. ietf-ippm-owdp-reqs-06 INFORMATIONAL RFC3764 enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record J. Peterson April 2004 ASCII 17604 8 aor electronic number This document registers an Electronic Number (ENUM) service for the Session Initiation Protocol (SIP), pursuant to the guidelines in RFC 3761. Specifically, this document focuses on provisioning SIP addresses-of-record in ENUM. [STANDARDS TRACK] ietf-enum-sip-01 PROPOSED STANDARD PROPOSED STANDARD RFC3765 NOPEER Community for Border Gateway Protocol (BGP) Route Scope Control G. Huston April 2004 ASCII 16500 7 peer connections propagated This document describes the use of a scope control Border Gateway Protocol (BGP) community. This well-known advisory transitive community allows an origin AS to specify the extent to which a specific route should be externally propagated. In particular this community, NOPEER, allows an origin AS to specify that a route with this attribute need not be advertised across bilateral peer connections. This memo provides information for the Internet community. ietf-ptomaine-nopeer-03 INFORMATIONAL INFORMATIONAL RFC3766 Determining Strengths For Public Keys Used For Exchanging Symmetric Keys H. Orman P. Hoffman April 2004 ASCII 55939 23 security cryptography algorithms integers Implementors of systems that use public key cryptography to exchange symmetric keys need to make the public keys resistant to some predetermined level of attack. That level of attack resistance is the strength of the system, and the symmetric keys that are exchanged must be at least as strong as the system strength requirements. The three quantities, system strength, symmetric key strength, and public key strength, must be consistently matched for any network protocol usage. While it is fairly easy to express the system strength requirements in terms of a symmetric key length and to choose a cipher that has a key length equal to or exceeding that requirement, it is harder to choose a public key that has a cryptographic strength meeting a symmetric key strength requirement. This document explains how to determine the length of an asymmetric key as a function of a symmetric key strength requirement. Some rules of thumb for estimating equivalent resistance to large-scale attacks on various algorithms are given. The document also addresses how changing the sizes of the underlying large integers (moduli, group sizes, exponents, and so on) changes the time to use the algorithms for key exchange. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. orman-public-key-lengths-08 BCP0086 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3767 Securely Available Credentials Protocol S. Farrell Editor June 2004 ASCII 49552 25 beep blocks extensible exchange protocol xml extensible mark up language This document describes a protocol whereby a user can acquire cryptographic credentials (e.g., private keys, PKCS #15 structures) from a credential server, using a workstation that has locally trusted software installed, but with no user-specific configuration. The protocol's payloads are described in XML. This memo also specifies a Blocks Extensible Exchange Protocol (BEEP) profile of the protocol. Security requirements are met by mandating support for TLS and/or DIGEST-MD5 (through BEEP). [STANDARDS TRACK] ietf-sacred-protocol-bss-09 PROPOSED STANDARD PROPOSED STANDARD RFC3768 Virtual Router Redundancy Protocol (VRRP) R. Hinden Editor April 2004 ASCII 59969 27 VRRP vrrp lan local area network ip internet protocol This memo defines the Virtual Router Redundancy Protocol (VRRP). VRRP specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. The VRRP router controlling the IP address(es) associated with a virtual router is called the Master, and forwards packets sent to these IP addresses. The election process provides dynamic fail over in the forwarding responsibility should the Master become unavailable. This allows any of the virtual router IP addresses on the LAN to be used as the default first hop router by end-hosts. The advantage gained from using VRRP is a higher availability default path without requiring configuration of dynamic routing or router discovery protocols on every end-host. [STANDARDS TRACK] ietf-vrrp-spec-v2-10 RFC2338 DRAFT STANDARD DRAFT STANDARD RFC3769 Requirements for IPv6 Prefix Delegation S. Miyakawa R. Droms June 2004 ASCII 10287 6 internet protocol version 6 This document describes requirements for how IPv6 address prefixes should be delegated to an IPv6 subscriber's network (or "site"). This memo provides information for the Internet community. ietf-ipv6-prefix-delegation-requirement-04 INFORMATIONAL INFORMATIONAL RFC3770 Certificate Extensions and Attributes Supporting Authentication in Point-to-Point Protocol (PPP) and Wireless Local Area Networks (WLAN) R. Housley T. Moore May 2004 ASCII 18635 9 ssid system service identifiers eap This document defines two EAP extended key usage values and a public key certificate extension to carry Wireless LAN (WLAN) System Service identifiers (SSIDs). [STANDARDS TRACK] ietf-pkix-wlan-extns-05 PROPOSED STANDARD PROPOSED STANDARD RFC3771 The Lightweight Directory Access Protocol (LDAP) Intermediate Response Message R. Harrison K. Zeilenga April 2004 ASCII 17114 8 LDAPv3 LDAv3 x.500 This document defines and describes the IntermediateResponse message, a general mechanism for defining single-request/multiple-response operations in Lightweight Directory Access Protocol (LDAP). The IntermediateResponse message is defined in such a way that the protocol behavior of existing LDAP operations is maintained. This message is intended to be used in conjunction with the LDAP ExtendedRequest and ExtendedResponse to define new single-request/multiple-response operations or in conjunction with a control when extending existing LDAP operations in a way that requires them to return intermediate response information. [STANDARDS TRACK] rharrison-ldap-intermediate-resp-01 RFC2251 PROPOSED STANDARD PROPOSED STANDARD RFC3772 Point-to-Point Protocol (PPP) Vendor Protocol J. Carlson R. Winslow May 2004 ASCII 19846 10 link control protocol lcp The Point-to-Point Protocol (PPP) defines a Link Control Protocol (LCP) and a method for negotiating the use of multi-protocol traffic over point-to-point links. The PPP Vendor Extensions document adds vendor-specific general-purpose Configuration Option and Code numbers. This document extends these features to cover vendor-specific Network, Authentication, and Control Protocols. [STANDARDS TRACK] PROPOSED STANDARD PROPOSED STANDARD RFC3773 High-Level Requirements for Internet Voice Mail E. Candell June 2004 ASCII 19156 9 ivm internet voice messaging voice profile for internet mail vpim This document describes the high-level requirements for Internet Voice Mail (IVM) and establishes a baseline of desired functionality against which proposed MIME profiles for Internet Voice Messaging can be judged. IVM is an extension of the Voice Profile for Internet Mail (VPIM) version 2 designed to support interoperability with desktop clients. Other goals for this version of VPIM include expanded interoperability with unified messaging systems, conformance to Internet standards, and backward compatibility with voice messaging systems currently running in a VPIM enabled environment. This document does not include goals that were met fully by VPIM version 2. This memo provides information for the Internet community. ietf-vpim-ivm-goals-06 INFORMATIONAL INFORMATIONAL RFC3774 IETF Problem Statement E. Davies Editor May 2004 ASCII 55172 22 ietf process problem analysis This memo summarizes perceived problems in the structure, function, and processes of the Internet Engineering Task Force (IETF). We are attempting to identify these problems, so that they can be addressed and corrected by the IETF community. The problems have been digested and categorized from an extensive discussion which took place on the 'problem-statement' mailing list from November 2002 to September 2003. The problem list has been further analyzed in an attempt to determine the root causes at the heart of the perceived problems: The result will be used to guide the next stage of the process in the Problem Statement working group which is to recommend the structures and processes that will carry out the corrections. This memo provides information for the Internet community. ietf-problem-issue-statement-05 INFORMATIONAL INFORMATIONAL RFC3775 Mobility Support in IPv6 D. Johnson C. Perkins J. Arkko June 2004 ASCII 393514 165 internet protocol nodes This document specifies a protocol which allows nodes to remain reachable while moving around in the IPv6 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 the mobile node's current location. IPv6 packets addressed to a mobile node's home address are transparently routed to its care-of address. The protocol enables IPv6 nodes to cache the binding of a mobile node's home address with its care-of address, and to then send any packets destined for the mobile node directly to it at this care-of address. To support this operation, Mobile IPv6 defines a new IPv6 protocol and a new destination option. All IPv6 nodes, whether mobile or stationary, can communicate with mobile nodes. [STANDARDS TRACK] ietf-mobileip-ipv6-24 PROPOSED STANDARD PROPOSED STANDARD RFC3776 Using IPsec to Protect Mobile IPv6 Signaling Between Mobile Nodes and Home Agents J. Arkko V. Devarapalli F. Dupont June 2004 ASCII 87076 40 security internet protocol Mobile IPv6 uses IPsec to protect signaling between the home agent and the mobile node. Mobile IPv6 base document defines the main requirements these nodes must follow. This document discusses these requirements in more depth, illustrates the used packet formats, describes suitable configuration procedures, and shows how implementations can process the packets in the right order. [STANDARDS TRACK] ietf-mobileip-mipv6-ha-ipsec-06 PROPOSED STANDARD PROPOSED STANDARD RFC3777 IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees J. Galvin Editor June 2004 ASCII 76395 34 Internet Architecture Board Engineering Steering Group The process by which the members of the IAB and IESG are selected, confirmed, and recalled is specified. This document is a self-consistent, organized compilation of the process as it was known at the time of publication. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-nomcom-rfc2727bis-09 RFC2727 BCP0010 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3778 The application/pdf Media Type E. Taft J. Pravetz S. Zilles L. Masinter May 2004 ASCII 29891 14 portable document format document exchange digital signatures PDF, the 'Portable Document Format', is a general document representation language that has been in use for document exchange on the Internet since 1993. This document provides an overview of the PDF format, explains the mechanisms for digital signatures and encryption within PDF files, and updates the media type registration of 'application/pdf'. This memo provides information for the Internet community. zilles-pdf-03 INFORMATIONAL INFORMATIONAL RFC3779 X.509 Extensions for IP Addresses and AS Identifiers C. Lynn S. Kent K. Seo June 2004 ASCII 60732 27 allocation atrribute certificate authorization autonomous system number authorization certificate delegation internet registry ip address authorization public key infrastructure right-to-use secure allocation This document defines two X.509 v3 certificate extensions. The first binds a list of IP address blocks, or prefixes, to the subject of a certificate. The second binds a list of autonomous system identifiers to the subject of a certificate. These extensions may be used to convey the authorization of the subject to use the IP addresses and autonomous system identifiers contained in the extensions. [STANDARDS TRACK] ietf-pkix-x509-ipaddr-as-extn-03 PROPOSED STANDARD PROPOSED STANDARD RFC3780 SMIng - Next Generation Structure of Management Information F. Strauss J. Schoenwaelder May 2004 ASCII 141049 64 data definition language This memo defines the base SMIng (Structure of Management Information, Next Generation) language. SMIng is a data definition language that provides a protocol-independent representation for management information. Separate RFCs define mappings of SMIng to specific management protocols, including SNMP. This memo defines an Experimental Protocol for the Internet community. irtf-nmrg-sming-07 EXPERIMENTAL EXPERIMENTAL RFC3781 Next Generation Structure of Management Information (SMIng) Mappings to the Simple Network Management Protocol (SNMP) F. Strauss J. Schoenwaelder May 2004 ASCII 112267 49 data definition language SMIng (Structure of Management Information, Next Generation) (RFC3780), is a protocol-independent data definition language for management information. This memo defines an SMIng language extension that specifies the mapping of SMIng definitions of identities, classes, and their attributes and events to dedicated definitions of nodes, scalar objects, tables and columnar objects, and notifications, for application to the SNMP management framework. This memo defines an Experimental Protocol for the Internet community. irtf-nmrg-sming-snmp-05 EXPERIMENTAL EXPERIMENTAL RFC3782 The NewReno Modification to TCP's Fast Recovery Algorithm S. Floyd T. Henderson A. Gurtov April 2004 ASCII 49603 19 Transmission Control Protocol The purpose of this document is to advance NewReno TCP's Fast Retransmit and Fast Recovery algorithms in RFC 2582 from Experimental to Standards Track status. The main change in this document relative to RFC 2582 is to specify the Careful variant of NewReno's Fast Retransmit and Fast Recovery algorithms. The base algorithm described in RFC 2582 did not attempt to avoid unnecessary multiple Fast Retransmits that can occur after a timeout. However, RFC 2582 also defined "Careful" and "Less Careful" variants that avoid these unnecessary Fast Retransmits, and recommended the Careful variant. This document specifies the previously-named "Careful" variant as the basic version of NewReno TCP. [STANDARDS TRACK] ietf-tsvwg-newreno-02 RFC2582 PROPOSED STANDARD PROPOSED STANDARD RFC3783 Small Computer Systems Interface (SCSI) Command Ordering Considerations with iSCSI M. Chadalapaka R. Elliott May 2004 ASCII 32358 14 Internet Small Computer Systems Interface iscsi Internet Small Computer Systems Interface (iSCSI) is a Small Computer Systems Interface (SCSI) transport protocol designed to run on top of TCP. The iSCSI session abstraction is equivalent to the classic SCSI "I_T nexus", which represents the logical relationship between an Initiator and a Target (I and T) required in order to communicate via the SCSI family of protocols. The iSCSI session provides an ordered command delivery from the SCSI initiator to the SCSI target. This document goes into the design considerations that led to the iSCSI session model as it is defined today, relates the SCSI command ordering features defined in T10 specifications to the iSCSI concepts, and finally provides guidance to system designers on how true command ordering solutions can be built based on iSCSI. This memo provides information for the Internet community. ietf-ips-command-ordering-02 INFORMATIONAL INFORMATIONAL RFC3784 Intermediate System to Intermediate System (IS-IS) Extensions for Traffic Engineering (TE) H. Smit T. Li June 2004 ASCII 27422 13 link state protocol lsp This document describes extensions to the Intermediate System to Intermediate System (IS-IS) protocol to support Traffic Engineering (TE). This document extends the IS-IS protocol by specifying new information that an Intermediate System (router) can place in Link State Protocol (LSP) Data Units. This information describes additional details regarding the state of the network that are useful for traffic engineering computations. This memo provides information for the Internet community. ietf-isis-traffic-05 INFORMATIONAL INFORMATIONAL RFC3785 Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) Metric F. Le Faucheur R. Uppili A. Vedrenne P. Merckx T. Telkamp May 2004 ASCII 17475 8 link bandwidth router This document describes a common practice on how the existing metric of Interior Gateway Protocols (IGP) can be used as an alternative metric to the Traffic Engineering (TE) metric for Constraint Based Routing of MultiProtocol Label Switching (MPLS) Traffic Engineering tunnels. This effectively results in the ability to perform Constraint Based Routing with optimization of one metric (e.g., link bandwidth) for some Traffic Engineering tunnels (e.g., Data Trunks) while optimizing another metric (e.g., propagation delay) for some other tunnels with different requirements (e.g., Voice Trunks). No protocol extensions or modifications are required. This text documents current router implementations and deployment practices. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-tewg-te-metric-igp-02 BCP0087 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3786 Extending the Number of Intermediate System to Intermediate System (IS-IS) Link State PDU (LSP) Fragments Beyond the 256 Limit A. Hermelin S. Previdi M. Shand May 2004 ASCII 29164 14 This document describes a mechanism that allows a system to originate more than 256 Link State PDU (LSP) fragments, a limit set by the original Intermediate System to Intermediate System (IS-IS) Routing protocol, as described in ISO/IEC 10589. This mechanism can be used in IP-only, OSI-only, and dual routers. This memo provides information for the Internet community. ietf-isis-ext-lsp-frags-02 INFORMATIONAL INFORMATIONAL RFC3787 Recommendations for Interoperable IP Networks using Intermediate System to Intermediate System (IS-IS) J. Parker Editor May 2004 ASCII 25426 11 routing traffic This document discusses a number of differences between the Intermediate System to Intermediate System (IS-IS) protocol used to route IP traffic as described in RFC 1195 and the protocol as it is deployed today. These differences are discussed as a service to those implementing, testing, and deploying the IS-IS Protocol to route IP traffic. A companion document describes the differences between the protocol described in ISO 10589 and current practice. This memo provides information for the Internet community. ietf-isis-ip-interoperable-02 INFORMATIONAL INFORMATIONAL RFC3788 Security Considerations for Signaling Transport (SIGTRAN) Protocols J. Loughney M. Tuexen Editor J. Pastor-Balbas June 2004 ASCII 27125 13 This document discusses how Transport Layer Security (TLS) and IPsec can be used to secure communication for SIGTRAN protocols. The main goal is to recommend the minimum security means that a SIGTRAN node must implement in order to attain secured communication. The support of IPsec is mandatory for all nodes running SIGTRAN protocols. TLS support is optional. [STANDARDS TRACK] ietf-sigtran-security-03 PROPOSED STANDARD PROPOSED STANDARD RFC3789 Introduction to the Survey of IPv4 Addresses in Currently Deployed IETF Standards Track and Experimental Documents P. Nesser II A. Bergstrom Editor June 2004 ASCII 22842 10 This document is a general overview and introduction to the v6ops IETF workgroup project of documenting all usage of IPv4 addresses in IETF standards track and experimental RFCs. It is broken into seven documents conforming to the current IETF areas. It also describes the methodology used during documentation, which types of RFCs have been documented, and provides a concatenated summary of results. This memo provides information for the Internet community. ietf-v6ops-ipv4survey-intro-06 INFORMATIONAL INFORMATIONAL RFC3790 Survey of IPv4 Addresses in Currently Deployed IETF Internet Area Standards Track and Experimental Documents C. Mickles Editor P. Nesser II June 2004 ASCII 102694 49 This document seeks to document all usage of IPv4 addresses in currently deployed IETF Internet Area documented standards. In order to successfully transition from an all IPv4 Internet to an all IPv6 Internet, many interim steps will be taken. One of these steps is the evolution of current protocols that have IPv4 dependencies. It is hoped that these protocols (and their implementations) will be redesigned to be network address independent, but failing that will at least dually support IPv4 and IPv6. To this end, all Standards (Full, Draft, and Proposed) as well as Experimental RFCs will be surveyed and any dependencies will be documented. This memo provides information for the Internet community. ietf-v6ops-ipv4survey-int-03 INFORMATIONAL INFORMATIONAL RFC3791 Survey of IPv4 Addresses in Currently Deployed IETF Routing Area Standards Track and Experimental Documents C. Olvera P. Nesser II June 2004 ASCII 27567 15 This investigation work seeks to document all usage of IPv4 addresses in currently deployed IETF Routing Area documented standards. In order to successfully transition from an all IPv4 Internet to an all IPv6 Internet, many interim steps will be taken. One of these steps is the evolution of current protocols that have IPv4 dependencies. It is hoped that these protocols (and their implementations) will be redesigned to be network address independent, but failing that will at least dually support IPv4 and IPv6. To this end, all Standards (Full, Draft, and Proposed) as well as Experimental RFCs will be surveyed and any dependencies will be documented. This memo provides information for the Internet community. ietf-v6ops-ipv4survey-routing-03 INFORMATIONAL INFORMATIONAL RFC3792 Survey of IPv4 Addresses in Currently Deployed IETF Security Area Standards Track and Experimental Documents P. Nesser II A. Bergstrom Editor June 2004 ASCII 46398 25 This document seeks to document all usage of IPv4 addresses in currently deployed IETF Security Area documented standards. In order to successfully transition from an all IPv4 Internet to an all IPv6 Internet, many interim steps will be taken. One of these steps is the evolution of current protocols that have IPv4 dependencies. It is hoped that these protocols (and their implementations) will be redesigned to be network address independent, but failing that will at least dually support IPv4 and IPv6. To this end, all Standards (Full, Draft, and Proposed) as well as Experimental RFCs will be surveyed and any dependencies will be documented. This memo provides information for the Internet community. ietf-v6ops-ipv4survey-sec-04 INFORMATIONAL INFORMATIONAL RFC3793 Survey of IPv4 Addresses in Currently Deployed IETF Sub-IP Area Standards Track and Experimental Documents P. Nesser II A. Bergstrom Editor June 2004 ASCII 11624 6 This document seeks to document all usage of IPv4 addresses in currently deployed IETF Sub-IP Area documented standards. In order to successfully transition from an all IPv4 Internet to an all IPv6 Internet, many interim steps will be taken. One of these steps is the evolution of current protocols that have IPv4 dependencies. It is hoped that these protocols (and their implementations) will be redesigned to be network address independent, but failing that will at least dually support IPv4 and IPv6. To this end, all Standards (Full, Draft, and Proposed) as well as Experimental RFCs will be surveyed and any dependencies will be documented. This memo provides information for the Internet community. ietf-v6ops-ipv4survey-subip-04 INFORMATIONAL INFORMATIONAL RFC3794 Survey of IPv4 Addresses in Currently Deployed IETF Transport Area Standards Track and Experimental Documents P. Nesser II A. Bergstrom Editor June 2004 ASCII 60001 31 This document seeks to document all usage of IPv4 addresses in currently deployed IETF Transport Area documented standards. In order to successfully transition from an all IPv4 Internet to an all IPv6 Internet, many interim steps will be taken. One of these steps is the evolution of current protocols that have IPv4 dependencies. It is hoped that these protocols (and their implementations) will be redesigned to be network address independent, but failing that will at least dually support IPv4 and IPv6. To this end, all Standards (Full, Draft, and Proposed) as well as Experimental RFCs will be surveyed and any dependencies will be documented. This memo provides information for the Internet community. ietf-v6ops-ipv4survey-trans-05 INFORMATIONAL INFORMATIONAL RFC3795 Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents R. Sofia P. Nesser II June 2004 ASCII 92584 50 This document describes IPv4 addressing dependencies in an attempt to clarify the necessary steps in re-designing and re-implementing specifications to become network address independent, or at least, to dually support IPv4 and IPv6. This transition requires several interim steps, one of them being the evolution of current IPv4 dependent specifications to a format independent of the type of IP addressing schema used. Hence, it is hoped that specifications will be re-designed and re-implemented to become network address independent, or at least to dually support IPv4 and IPv6. To achieve that step, it is necessary to survey and document all IPv4 dependencies experienced by current standards (Full, Draft, and Proposed) as well as Experimental RFCs. Hence, this document describes IPv4 addressing dependencies that deployed IETF Application Area documented Standards may experience. This memo provides information for the Internet community. ietf-v6ops-ipv4survey-apps-04 INFORMATIONAL INFORMATIONAL RFC3796 Survey of IPv4 Addresses in Currently Deployed IETF Operations & Management Area Standards Track and Experimental Documents P. Nesser II A. Bergstrom Editor June 2004 ASCII 78400 43 This document seeks to record all usage of IPv4 addresses in currently deployed IETF Operations & Management Area accepted standards. In order to successfully transition from an all IPv4 Internet to an all IPv6 Internet, many interim steps will be taken. One of these steps is the evolution of current protocols that have IPv4 dependencies. It is hoped that these protocols (and their implementations) will be redesigned to be network address independent, but failing that will at least dually support IPv4 and IPv6. To this end, all Standards (Full, Draft, and Proposed), as well as Experimental RFCs, will be surveyed and any dependencies will be documented. This memo provides information for the Internet community. ietf-v6ops-ipv4survey-ops-05 INFORMATIONAL INFORMATIONAL RFC3797 Publicly Verifiable Nominations Committee (NomCom) Random Selection D. Eastlake 3rd June 2004 ASCII 39883 19 Internet Engineering Task Force IETF This document describes a method for making random selections in such a way that the unbiased nature of the choice is publicly verifiable. As an example, the selection of the voting members of the IETF Nominations Committee (NomCom) from the pool of eligible volunteers is used. Similar techniques would be applicable to other cases. This memo provides information for the Internet community. eastlake-rfc2777bis-selection-04 RFC2777 INFORMATIONAL INFORMATIONAL RFC3798 Message Disposition Notification T. Hansen Editor G. Vaudreuil Editor May 2004 ASCII 64049 30 EMF-MDN MDN media-type MIME multipurpose internet mail extensions This memo defines a MIME content-type that may be used by a mail user agent (MUA) or electronic mail gateway to report the disposition of a message after it has been successfully delivered to a recipient. This content-type is intended to be machine-processable. Additional message headers are also defined to permit Message Disposition Notifications (MDNs) to be requested by the sender of a message. The purpose is to extend Internet Mail to support functionality often found in other messaging systems, such as X.400 and the proprietary "LAN-based" systems, and often referred to as "read receipts," "acknowledgements", or "receipt notifications." The intention is to do this while respecting privacy concerns, which have often been expressed when such functions have been discussed in the past. Because many messages are sent between the Internet and other messaging systems (such as X.400 or the proprietary "LAN-based" systems), the MDN 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, in addition to those normally used in Internet Mail. Additional attributes may also be defined to support "tunneling" of foreign notifications through Internet Mail. [STANDARDS TRACK] vaudreuil-mdnbis-05 RFC2298 RFC3461 RFC2046 DRAFT STANDARD DRAFT STANDARD RFC3801 Voice Profile for Internet Mail - version 2 (VPIMv2) G. Vaudreuil G. Parsons June 2004 ASCII 118122 55 MIME-VP2 vpim messaging This document specifies a restricted profile of the Internet multimedia messaging protocols for use between voice processing server platforms. The profile is referred to as the Voice Profile for Internet Mail (VPIM) in this document. These platforms have historically been special-purpose computers and often do not have the same facilities normally associated with a traditional Internet Email-capable computer. As a result, VPIM also specifies additional functionality, as it is needed. This profile is intended to specify the minimum common set of features to allow interworking between conforming systems. This document obsoletes RFC 2421 and describes version 2 of the profile with greater precision. No protocol changes were made in this revision. A list of changes from RFC 2421 are noted in Appendix F. Appendix A summarizes the protocol profiles of this version of VPIM. [STANDARDS TRACK] ietf-vpim-vpimv2r2-05 RFC2421 RFC2423 DRAFT STANDARD DRAFT STANDARD RFC3802 Toll Quality Voice - 32 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM) MIME Sub-type Registration G. Vaudreuil G. Parsons June 2004 ASCII 11686 7 MIME-ADPCM multipurpose internet mail extensions audio This document describes the registration of the MIME sub-type audio/32KADPCM Adaptive Differential Pulse Code Modulation for toll quality audio. This audio encoding is defined by the ITU-T in Recommendation G.726. [STANDARDS TRACK] ietf-vpim-vpimv2r2-32k-03 RFC2422 DRAFT STANDARD DRAFT STANDARD RFC3803 Content Duration MIME Header Definition G. Vaudreuil G. Parsons June 2004 ASCII 8213 5 CONT-DUR multipurpose internet mail extensions time media This document describes the MIME header Content-Duration that is intended for use with any time varying media content (typically audio/* or video/*). [STANDARDS TRACK] ietf-vpim-vpimv2r2-dur-03 RFC2424 DRAFT STANDARD DRAFT STANDARD RFC3804 Voice Profile for Internet Mail (VPIM) Addressing G. Parsons June 2004 ASCII 26122 15 formats This document lists the various Voice Profile for Internet Mail (VPIM) email address formats that are currently in common use and defines several new address formats for special case usage. Requirements are imposed on the formats of addresses used in VPIM submission mode. [STANDARDS TRACK] ietf-vpim-address-03 PROPOSED STANDARD PROPOSED STANDARD RFC3805 Printer MIB v2 R. Bergman H. Lewis I. McDonald June 2004 ASCII 366952 171 Print-MIB Management Information Base snmp management This document provides definitions of models and manageable objects for printing environments. The objects included in this MIB apply to physical, as well as logical entities within a printing device. This document obsoletes RFC 1759. [STANDARDS TRACK] ietf-printmib-mib-info-15 RFC1759 PROPOSED STANDARD PROPOSED STANDARD RFC3806 Printer Finishing MIB R. Bergman H. Lewis I. McDonald June 2004 ASCII 109654 53 finisher snmp This document defines a MIB module for the management of printer finishing device subunits. The finishing device subunits applicable to this MIB are an integral part of the Printer System. This MIB applies only to a Finisher Device that is connected to a Printer System. This memo provides information for the Internet community. ietf-printmib-finishing-16 INFORMATIONAL INFORMATIONAL RFC3807 V5.2-User Adaptation Layer (V5UA) E. Weilandt N. Khanchandani S. Rao June 2004 ASCII 49748 24 v5 v5.1 v5.2 backhauling imap sctp isdn access network c-path c-channel efa envelope function address lapv5 pstn v5ptm mgc gateway controller gateway This document defines a mechanism for the backhauling of V5.2 messages over IP using the Stream Control Transmission Protocol (SCTP). This protocol may be used between a Signaling Gateway (SG) and a Media Gateway controller (MGC). It is assumed that the SG receives V5.2 signaling over a standard V5.2 interface. This document builds on the ISDN User Adaptation Layer Protocol (RFC 3057). It defines all necessary extensions to the IUA Protocol needed for the V5UA protocol implementation. [STANDARDS TRACK] ietf-sigtran-v5ua-04 RFC3057 PROPOSED STANDARD PROPOSED STANDARD RFC3808 IANA Charset MIB I. McDonald June 2004 ASCII 25245 14 management information base IANACharset This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This IANA Charset MIB is now an IANA registry. In particular, a single textual convention 'IANACharset' is defined that may be used to specify charset labels in MIB objects. 'IANACharset' was extracted from Printer MIB v2 (RFC 3805). 'IANACharset' was originally defined (and mis-named) as 'CodedCharSet' in Printer MIB v1 (RFC 1759). A tool has been written in C, that may be used by IANA to regenerate this IANA Charset MIB, when future charsets are registered in accordance with the IANA Charset Registration Procedures (RFC 2978). This memo provides information for the Internet community. mcdonald-iana-charset-mib-02 INFORMATIONAL INFORMATIONAL RFC3809 Generic Requirements for Provider Provisioned Virtual Private Networks (PPVPN) A. Nagarajan Editor June 2004 ASCII 60576 25 service engineering This document describes generic requirements for Provider Provisioned Virtual Private Networks (PPVPN). The requirements are categorized into service requirements, provider requirements and engineering requirements. These requirements are not specific to any particular type of PPVPN technology, but rather apply to all PPVPN technologies. All PPVPN technologies are expected to meet the umbrella set of requirements described in this document. This memo provides information for the Internet community. ietf-l3vpn-generic-reqts-03 INFORMATIONAL INFORMATIONAL RFC3810 Multicast Listener Discovery Version 2 (MLDv2) for IPv6 R. Vida Editor L. Costa Editor June 2004 ASCII 153579 62 ssm source filtering igmp group management mld This document updates RFC 2710, and it specifies Version 2 of the ulticast Listener Discovery Protocol (MLDv2). MLD is used by an IPv6 router to discover the presence of multicast listeners on directly attached links, and to discover which multicast addresses are of interest to those neighboring nodes. MLDv2 is designed to be interoperable with MLDv1. MLDv2 adds the ability for a node to report interest in listening to packets with a particular multicast address only from specific source addresses or from all sources except for specific source addresses. [STANDARDS TRACK] vida-mld-v2-08 RFC2710 PROPOSED STANDARD PROPOSED STANDARD RFC3811 Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management T. Nadeau Editor J. Cucchiara Editor June 2004 ASCII 40353 20 management information base This memo defines a Management Information Base (MIB) module which contains Textual Conventions to represent commonly used Multiprotocol Label Switching (MPLS) management information. The intent is that these TEXTUAL CONVENTIONS (TCs) will be imported and used in MPLS related MIB modules that would otherwise define their own representations. [STANDARDS TRACK] ietf-mpls-tc-mib-10 PROPOSED STANDARD PROPOSED STANDARD RFC3812 Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB) C. Srinivasan A. Viswanathan T. Nadeau June 2004 ASCII 136475 68 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for Multiprotocol Label Switching (MPLS) based traffic engineering (TE). [STANDARDS TRACK] ietf-mpls-te-mib-14 PROPOSED STANDARD PROPOSED STANDARD RFC3813 Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB) C. Srinivasan A. Viswanathan T. Nadeau June 2004 ASCII 116120 60 This memo defines an portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects to configure and/or monitor a Multiprotocol Label Switching (MPLS) Label Switching Router (LSR). [STANDARDS TRACK] ietf-mpls-lsr-mib-14 PROPOSED STANDARD PROPOSED STANDARD RFC3814 Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (MIB) T. Nadeau C. Srinivasan A. Viswanathan June 2004 ASCII 87518 42 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for defining, configuring, and monitoring Forwarding Equivalence Class (FEC) to Next Hop Label Forwarding Entry (NHLFE) mappings and corresponding actions for use with Multiprotocol Label Switching (MPLS). [STANDARDS TRACK] ietf-mpls-ftn-mib-09 PROPOSED STANDARD PROPOSED STANDARD RFC3815 Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP) J. Cucchiara H. Sjostrand J. Luciani June 2004 ASCII 215916 106 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for the Multiprotocol Label Switching, Label Distribution Protocol (LDP). [STANDARDS TRACK] ietf-mpls-ldp-mib-14 PROPOSED STANDARD PROPOSED STANDARD RFC3816 Definitions of Managed Objects for RObust Header Compression (ROHC) J. Quittek M. Stiemerling H. Hartenstein June 2004 ASCII 104947 53 mib management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a set of managed objects that allow monitoring of running instances of RObust Header Compression (ROHC). The managed objects defined in this memo are grouped into three MIB modules. The ROHC-MIB module defines managed objects shared by all ROHC profiles, the ROHC-UNCOMPRESSED-MIB module defines managed objects specific to the ROHC uncompressed profile, the ROHC-RTP-MIB module defines managed objects specific to the ROHC RTP (Real-Time Transport Protocol) profile, the ROHC UDP (User Datagram Protocol) profile, the ROHC ESP (Encapsulating Security Payload) profile, and the ROHC LLA (Link Layer Assisted) profile. [STANDARDS TRACK] ietf-rohc-mib-rtp-09 PROPOSED STANDARD PROPOSED STANDARD RFC3817 Layer 2 Tunneling Protocol (L2TP) Active Discovery Relay for PPP over Ethernet (PPPoE) W. Townsley R. da Silva June 2004 ASCII 37765 17 point-to-point The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. Layer Two Tunneling Protocol (L2TP), facilitates the tunneling of PPP packets across an intervening packet-switched network. And yet a third protocol, PPP over Ethernet (PPPoE) describes how to build PPP sessions and to encapsulate PPP packets over Ethernet. L2TP Active Discovery Relay for PPPoE describes a method to relay Active Discovery and Service Selection functionality from PPPoE over the reliable control channel within L2TP. Two new L2TP control message types and associated PPPoE-specific Attribute Value Pairs (AVPs) for L2TP are defined. This relay mechanism provides enhanced integration of a specific feature in the PPPoE tunneling protocol with L2TP. This memo provides information for the Internet community. dasilva-l2tp-relaysvc-08 INFORMATIONAL INFORMATIONAL RFC3818 IANA Considerations for the Point-to-Point Protocol (PPP) V. Schryver June 2004 ASCII 6321 4 The charter of the Point-to-Point Protocol (PPP) Extensions working group (pppext) includes the responsibility to "actively advance PPP's most useful extensions to full standard, while defending against further enhancements of questionable value." In support of that charter, the allocation of PPP protocol and other assigned numbers will no longer be "first come first served." This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. schryver-pppext-iana-01 BCP0088 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3819 Advice for Internet Subnetwork Designers P. Karn Editor C. Bormann G. Fairhurst D. Grossman R. Ludwig J. Mahdavi G. Montenegro J. Touch L. Wood July 2004 ASCII 152174 60 digital communication equipment link-layer protocols packet-switched local networks This document provides advice to the designers of digital communication equipment, link-layer protocols, and packet-switched local networks (collectively referred to as subnetworks), who wish to support the Internet protocols but may be unfamiliar with the Internet architecture and the implications of their design choices on the performance and efficiency of the Internet. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-pilc-link-design-15 BCP0089 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3820 Internet X.509 Public Key Infrastructure (PKI) Proxy Certificate Profile S. Tuecke V. Welch D. Engert L. Pearlman M. Thompson June 2004 ASCII 86374 37 authentication security credentials restricted delegation single-signon delegation of rights This document forms a certificate profile for Proxy Certificates, based on X.509 Public Key Infrastructure (PKI) certificates as defined in RFC 3280, for use in the Internet. The term Proxy Certificate is used to describe a certificate that is derived from, and signed by, a normal X.509 Public Key End Entity Certificate or by another Proxy Certificate for the purpose of providing restricted proxying and delegation within a PKI based authentication system. [STANDARDS TRACK] ietf-pkix-proxy-10 PROPOSED STANDARD PROPOSED STANDARD RFC3821 Fibre Channel Over TCP/IP (FCIP) M. Rajagopal E. Rodriguez R. Weber July 2004 ASCII 165907 74 storage area networks IP-based networks unified storage area network Fibre Channel Over TCP/IP (FCIP) describes mechanisms that allow the interconnection of islands of Fibre Channel storage area networks over IP-based networks to form a unified storage area network in a single Fibre Channel fabric. FCIP relies on IP-based network services to provide the connectivity between the storage area network islands over local area networks, metropolitan area networks, or wide area networks. [STANDARDS TRACK] ietf-ips-fcovertcpip-12 PROPOSED STANDARD PROPOSED STANDARD RFC3822 Finding Fibre Channel over TCP/IP (FCIP) Entities Using Service Location Protocol version 2 (SLPv2) D. Peterson July 2004 ASCII 22859 11 dynamic discovery This document defines the use of Service Location Protocol version 2 (SLPv2) by Fibre Channel over TCP/IP (FCIP) Entities. [STANDARDS TRACK] ietf-ips-fcip-slp-09 PROPOSED STANDARD PROPOSED STANDARD RFC3823 MIME Media Type for the Systems Biology Markup Language (SBML) B. Kovitz June 2004 ASCII 14577 8 sub-type application/sbml+xml systems biology community This document registers the MIME sub-type application/sbml+xml, a media type for SBML, the Systems Biology Markup Language. SBML is defined by The SBML Team at the California Institute of Technology and interested members of the systems biology community. This memo provides information for the Internet community. sbml-media-type-02 INFORMATIONAL INFORMATIONAL RFC3824 Using E.164 numbers with the Session Initiation Protocol (SIP) J. Peterson H. Liu J. Yu B. Campbell June 2004 ASCII 36535 16 telephone records applications There are a number of contexts in which telephone numbers are employed by Session Initiation Protocol (SIP) applications, many of which can be addressed by ENUM. Although SIP was one of the primary applications for which ENUM was created, there is nevertheless a need to define procedures for integrating ENUM with SIP implementations. This document illustrates how the two protocols might work in concert, and clarifies the authoring and processing of ENUM records for SIP applications. It also provides guidelines for instances in which ENUM, for whatever reason, cannot be used to resolve a telephone number. This memo provides information for the Internet community. ietf-sipping-e164-04 INFORMATIONAL INFORMATIONAL RFC3825 Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information J. Polk J. Schnizlein M. Linsner July 2004 ASCII 31715 15 dhcp lci geographic location This document specifies a Dynamic Host Configuration Protocol Option for the coordinate-based geographic location of the client. The Location Configuration Information (LCI) includes latitude, longitude, and altitude, with resolution indicators for each. The reference datum for these values is also included. [STANDARDS TRACK] ietf-geopriv-dhcp-lci-option-03 PROPOSED STANDARD PROPOSED STANDARD RFC3826 The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model U. Blumenthal F. Maino K. McCloghrie June 2004 ASCII 32821 16 management information base simple network management protocol This document describes a symmetric encryption protocol that supplements the protocols described in the User-based Security Model (USM), which is a Security Subsystem for version 3 of the Simple Network Management Protocol for use in the SNMP Architecture. The symmetric encryption protocol described in this document is based on the Advanced Encryption Standard (AES) cipher algorithm used in Cipher FeedBack Mode (CFB), with a key size of 128 bits. [STANDARDS TRACK] blumenthal-aes-usm-08 PROPOSED STANDARD PROPOSED STANDARD RFC3827 Additional Snoop Datalink Types K. Sarcar June 2004 ASCII 6344 4 The snoop file format provides a way to store and exchange datalink layer packet traces. This document describes extensions to this file format to support new media. This memo provides information for the Internet community. sarcar-snoop-new-types-01 INFORMATIONAL INFORMATIONAL RFC3828 The Lightweight User Datagram Protocol (UDP-Lite) L-A. Larzon M. Degermark S. Pink L-E. Jonsson Editor G. Fairhurst Editor July 2004 ASCII 27193 12 This document describes the Lightweight User Datagram Protocol (UDP-Lite), which is similar to the User Datagram Protocol (UDP) (RFC 768), but can also serve applications in error-prone network environments that prefer to have partially damaged payloads delivered rather than discarded. If this feature is not used, UDP-Lite is semantically identical to UDP. [STANDARDS TRACK] ietf-tsvwg-udp-lite-02 PROPOSED STANDARD PROPOSED STANDARD RFC3829 Lightweight Directory Access Protocol (LDAP) Authorization Identity Request and Response Controls R. Weltman M. Smith M. Wahl July 2004 ASCII 11986 6 bind operation This document extends the Lightweight Directory Access Protocol (LDAP) bind operation with a mechanism for requesting and returning the authorization identity it establishes. Specifically, this document defines the Authorization Identity Request and Response controls for use with the Bind operation. This memo provides information for the Internet community. weltman-ldapv3-auth-response-09 INFORMATIONAL INFORMATIONAL RFC3830 MIKEY: Multimedia Internet KEYing J. Arkko E. Carrara F. Lindholm M. Naslund K. Norrman August 2004 ASCII 145238 66 key management scheme real-time applications This document describes a key management scheme that can be used for real-time applications (both for peer-to-peer communication and group communication). In particular, its use to support the Secure Real-time Transport Protocol is described in detail. Security protocols for real-time multimedia applications have started to appear. This has brought forward the need for a key management solution to support these protocols. [STANDARDS TRACK] ietf-msec-mikey-08 PROPOSED STANDARD PROPOSED STANDARD RFC3831 Transmission of IPv6 Packets over Fibre Channel C. DeSanti July 2004 ASCII 53328 24 addresses link-local internet protocol This document specifies the way of encapsulating IPv6 packets over Fibre Channel, and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on Fibre Channel networks. [STANDARDS TRACK] ietf-imss-ipv6-over-fibre-channel-02 PROPOSED STANDARD PROPOSED STANDARD RFC3832 Remote Service Discovery in the Service Location Protocol (SLP) via DNS SRV W. Zhao H. Schulzrinne E. Guttman C. Bisdikian W. Jerome July 2004 ASCII 15602 8 DNS-SRV domain name system resource record Remote service discovery refers to discovering desired services in given remote (i.e., non-local) DNS domains. This document describes remote service discovery in the Service Location Protocol (SLP) via DNS SRV. It defines the DNS SRV Resource Records for SLP Directory Agent services, discusses various issues in using SLP and DNS SRV together for remote service discovery, and gives the steps for discovering desired services in remote DNS domains. This memo defines an Experimental Protocol for the Internet community. zhao-slp-remote-da-discovery-06 EXPERIMENTAL EXPERIMENTAL RFC3833 Threat Analysis of the Domain Name System (DNS) D. Atkins R. Austein August 2004 ASCII 39303 16 data disclosure security authentication Although the DNS Security Extensions (DNSSEC) have been under development for most of the last decade, the IETF has never written down the specific set of threats against which DNSSEC is designed to protect. Among other drawbacks, this cart-before-the-horse situation has made it difficult to determine whether DNSSEC meets its design goals, since its design goals are not well specified. This note attempts to document some of the known threats to the DNS, and, in doing so, attempts to measure to what extent (if any) DNSSEC is a useful tool in defending against these threats. This memo provides information for the Internet community. ietf-dnsext-dns-threats-07 INFORMATIONAL INFORMATIONAL RFC3834 Recommendations for Automatic Responses to Electronic Mail K. Moore August 2004 ASCII 53119 22 automatic mail responders This memo makes recommendations for software that automatically responds to incoming electronic mail messages, including "out of the office" or "vacation" response generators, mail filtering software, email-based information services, and other automatic responders. The purpose of these recommendations is to discourage undesirable behavior which is caused or aggravated by such software, to encourage uniform behavior (where appropriate) among automatic mail responders, and to clear up some sources of confusion among implementors of automatic email responders. [STANDARDS TRACK] moore-auto-email-response-05 PROPOSED STANDARD PROPOSED STANDARD RFC3835 An Architecture for Open Pluggable Edge Services (OPES) A. Barbir R. Penno R. Chen M. Hofmann H. Orman August 2004 ASCII 36113 17 application service data stream service data consumer data dispatcher architecture This memo defines an architecture that enables the creation of an application service in which a data provider, a data consumer, and zero or more application entities cooperatively implement a data stream service. This memo provides information for the Internet community. ietf-opes-architecture-04 INFORMATIONAL INFORMATIONAL RFC3836 Requirements for Open Pluggable Edge Services (OPES) Callout Protocols A. Beck M. Hofmann H. Orman R. Penno A. Terzis August 2004 ASCII 28438 13 callout protocol remote execution OPES services This document specifies the requirements that the OPES (Open Pluggable Edge Services) callout protocol must satisfy in order to support the remote execution of OPES services. The requirements are intended to help evaluate possible protocol candidates, as well as to guide the development of such protocols. This memo provides information for the Internet community. ietf-opes-protocol-reqs-03 INFORMATIONAL INFORMATIONAL RFC3837 Security Threats and Risks for Open Pluggable Edge Services (OPES) A. Barbir O. Batuner B. Srinivas M. Hofmann H. Orman August 2004 ASCII 31883 14 threat discovery threat analysis The document investigates the security threats associated with the Open Pluggable Edge Services (OPES) and discusses the effects of security threats on the underlying architecture. The main goal of this document is threat discovery and analysis. The document does not specify or recommend any solutions. This memo provides information for the Internet community. ietf-opes-threats-03 INFORMATIONAL INFORMATIONAL RFC3838 Policy, Authorization, and Enforcement Requirements of the Open Pluggable Edge Services (OPES) A. Barbir O. Batuner A. Beck T. Chan H. Orman August 2004 ASCII 38739 17 opes flow This document describes policy, authorization, and enforcement requirements for the selection of the services to be applied to a given Open Pluggable Edge Services (OPES) flow. This memo provides information for the Internet community. ietf-opes-authorization-03 INFORMATIONAL INFORMATIONAL RFC3839 MIME Type Registrations for 3rd Generation Partnership Project (3GPP) Multimedia files R. Castagno D. Singer July 2004 ASCII 15645 7 standard MIME types 3GPP multimedia file format ISO Media File Format This document serves to register and document the standard MIME types associated with the 3GPP multimedia file format, which is part of the family based on the ISO Media File Format. [STANDARDS TRACK] singer-avt-3gpp-mime-01 PROPOSED STANDARD PROPOSED STANDARD RFC3840 Indicating User Agent Capabilities in the Session Initiation Protocol (SIP) J. Rosenberg H. Schulzrinne P. Kyzivat August 2004 ASCII 81360 36 ua contact header field This specification defines mechanisms by which a Session Initiation Protocol (SIP) user agent can convey its capabilities and characteristics to other user agents and to the registrar for its domain. This information is conveyed as parameters of the Contact header field. [STANDARDS TRACK] ietf-sip-callee-caps-03 PROPOSED STANDARD PROPOSED STANDARD RFC3841 Caller Preferences for the Session Initiation Protocol (SIP) J. Rosenberg H. Schulzrinne P. Kyzivat August 2004 ASCII 61382 26 Uniform Resource Identifiers URI Accept-Contact Reject-Contact Request-Disposition This document describes a set of extensions to the Session Initiation Protocol (SIP) which allow a caller to express preferences about request handling in servers. These preferences include the ability to select which Uniform Resource Identifiers (URI) a request gets routed to, and to specify certain request handling directives in proxies and redirect servers. It does so by defining three new request header fields, Accept-Contact, Reject-Contact, and Request-Disposition, which specify the caller's preferences. [STANDARDS TRACK] ietf-sip-callerprefs-10 PROPOSED STANDARD PROPOSED STANDARD RFC3842 A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP) R. Mahy August 2004 ASCII 36877 19 message waiting status message summary This document describes a Session Initiation Protocol (SIP) event package to carry message waiting status and message summaries from a messaging system to an interested User Agent. [STANDARDS TRACK] ietf-sipping-mwi-04 PROPOSED STANDARD PROPOSED STANDARD RFC3843 RObust Header Compression (ROHC): A Compression Profile for IP L-E. Jonsson G. Pelletier June 2004 ASCII 33549 16 compression protocols The original RObust Header Compression (ROHC) RFC (RFC 3095) defines a framework for header compression, along with compression protocols (profiles) for IP/UDP/RTP, IP/ESP (Encapsulating Security Payload), IP/UDP, and also a profile for uncompressed packet streams. However, no profile was defined for compression of IP only, which has been identified as a missing piece in RFC 3095. This document defines a ROHC compression profile for IP, similar to the IP/UDP profile defined by RFC 3095, but simplified to exclude UDP, and enhanced to compress IP header chains of arbitrary length. [STANDARDS TRACK] ietf-rohc-ip-only-05 PROPOSED STANDARD PROPOSED STANDARD RFC3844 IETF Problem Resolution Process E. Davies J. Hofmann Editors August 2004 ASCII 44841 20 ietf process problem analysis This Informational document records the history of discussions in the Problem WG during 2003 of how to resolve the problems described in the IETF Problem Statement. It decomposes each of the problems described into a few areas for improvement and categorizes them as either problems affecting the routine processes used to create standards or problems affecting the fundamental structure and practices of the IETF. Expeditious and non-disruptive solutions are proposed for the problems affecting routine processes. The document also lists suggested ways to handle the development of solutions for the structure and practices problems proposed in IETF discussions. Neither the working group nor the wider IETF has reached consensus on a recommendation for any of the proposals. This document therefore has no alternative but to suggest that the search for structure and practices solutions be handed back to the control of the IESG. While there was working group consensus on the processes for short-term and medium term improvements, there was no working group consensus on the proposals for longer-term improvements. This document therefore includes longer-term improvement proposals only as a matter of record; they must not be regarded as recommendations from the working group. This memo provides information for the Internet community. ietf-problem-process-04 INFORMATIONAL INFORMATIONAL RFC3845 DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format J. Schlyter Editor August 2004 ASCII 14793 7 dnssec DNS Security rr resource record DNS-SECEXT dns authentication nsec nextsecure This document redefines the wire format of the "Type Bit Map" field in the DNS NextSECure (NSEC) resource record RDATA format to cover the full resource record (RR) type space. [STANDARDS TRACK] ietf-dnsext-nsec-rdata-06 RFC4033 RFC4034 RFC4035 RFC3755 RFC2535 PROPOSED STANDARD PROPOSED STANDARD RFC3846 Mobile IPv4 Extension for Carrying Network Access Identifiers F. Johansson T. Johansson June 2004 ASCII 16834 8 nai internet protocol home aaa server ha server home agents When a mobile node moves between two foreign networks, it has to be re-authenticated. If the home network has both multiple Authentication Authorization and Accounting (AAA) servers and Home Agents (HAs) in use, the Home AAA server may not have sufficient information to process the re-authentication correctly (i.e., to ensure that the same HA continues to be used). This document defines a Mobile IP extension that carries identities for the Home AAA and HA servers in the form of Network Access Identifiers (NAIs). The extension allows a Home Agent to pass its identity (and that of the Home AAA server) to the mobile node, which can then pass it on to the local AAA server when changing its point of attachment. This extension may also be used in other situations requiring communication of a NAI between Mobile IP nodes. [STANDARDS TRACK] ietf-mip4-aaa-nai-02 PROPOSED STANDARD PROPOSED STANDARD RFC3847 Restart Signaling for Intermediate System to Intermediate System (IS-IS) M. Shand L. Ginsberg July 2004 ASCII 50023 21 LSP database synchronization transient routing disruption database synchronization This document describes a mechanism for a restarting router to signal to its neighbors that it is restarting, allowing them to reestablish their adjacencies without cycling through the down state, while still correctly initiating database synchronization. This document additionally describes a mechanism for a restarting router to determine when it has achieved LSP database synchronization with its neighbors and a mechanism to optimize LSP database synchronization, while minimizing transient routing disruption when a router starts. This memo provides information for the Internet community. ietf-isis-restart-05 INFORMATIONAL INFORMATIONAL RFC3848 ESMTP and LMTP Transmission Types Registration C. Newman July 2004 ASCII 7916 4 smtp simple mail transfer protocol This registers seven new mail transmission types (ESMTPA, ESMTPS, ESMTPSA, LMTP, LMTPA, LMTPS, LMTPSA) for use in the "with" clause of a Received header in an Internet message. [STANDARDS TRACK] newman-esmtpsa-01 PROPOSED STANDARD PROPOSED STANDARD RFC3849 IPv6 Address Prefix Reserved for Documentation G. Huston A. Lord P. Smith July 2004 ASCII 7872 4 unicast site-local link-local To reduce the likelihood of conflict and confusion when relating documented examples to deployed systems, an IPv6 unicast address prefix is reserved for use in examples in RFCs, books, documentation, and the like. Since site-local and link-local unicast addresses have special meaning in IPv6, these addresses cannot be used in many example situations. The document describes the use of the IPv6 address prefix 2001:DB8::/32 as a reserved prefix for use in documentation. This memo provides information for the Internet community. huston-ipv6-documentation-prefix-03 INFORMATIONAL INFORMATIONAL RFC3850 Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate Handling B. Ramsdell Editor July 2004 ASCII 37446 16 x.509 encryption certificate multipurpose internet mail extensions secure This document specifies conventions for X.509 certificate usage by Secure/Multipurpose Internet Mail Extensions (S/MIME) agents. S/MIME provides a method to send and receive secure MIME messages, and certificates are an integral part of S/MIME agent processing. S/MIME agents validate certificates as described in RFC 3280, the Internet X.509 Public Key Infrastructure Certificate and CRL Profile. S/MIME agents must meet the certificate processing requirements in this document as well as those in RFC 3280. [STANDARDS TRACK] ietf-smime-rfc2632bis-07 RFC2632 PROPOSED STANDARD PROPOSED STANDARD RFC3851 Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification B. Ramsdell Editor July 2004 ASCII 53328 36 secure multipurpose internet mail extensions encryption This document defines Secure/Multipurpose Internet Mail Extensions (S/MIME) version 3.1. S/MIME provides a consistent way to send and receive secure MIME data. Digital signatures provide authentication, message integrity, and non-repudiation with proof of origin. Encryption provides data confidentiality. Compression can be used to reduce data size. This document obsoletes RFC 2633. [STANDARDS TRACK] ietf-smime-rfc2633bis-09 RFC2633 PROPOSED STANDARD PROPOSED STANDARD RFC3852 Cryptographic Message Syntax (CMS) R. Housley July 2004 ASCII 15541 56 digitally sign authenticate encrypt arbitrary message content This document describes the Cryptographic Message Syntax (CMS). This syntax is used to digitally sign, digest, authenticate, or encrypt arbitrary message content. [STANDARDS TRACK] ietf-smime-rfc3369bis-04 RFC3369 PROPOSED STANDARD PROPOSED STANDARD RFC3853 S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP) J. Peterson July 2004 ASCII 10687 6 SIP application-layer application layer multimedia multicast unicast RFC 3261 currently specifies 3DES as the mandatory-to-implement ciphersuite for implementations of S/MIME in the Session Initiation Protocol (SIP). This document updates the normative guidance of RFC 3261 to require the Advanced Encryption Standard (AES) for S/MIME. [STANDARDS TRACK] ietf-sip-smime-aes-01 RFC3261 PROPOSED STANDARD PROPOSED STANDARD RFC3854 Securing X.400 Content with Secure/Multipurpose Internet Mail Extensions (S/MIME) P. Hoffman C. Bonatti A. Eggen July 2004 ASCII 32801 15 encryption cryptographic signature This document describes a protocol for adding cryptographic signature and encryption services to X.400 content with Secure/Multipurpose Internet Mail Extensions (S/MIME). [STANDARDS TRACK] ietf-smime-x400wrap-09 PROPOSED STANDARD PROPOSED STANDARD RFC3855 Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400 P. Hoffman C. Bonatti July 2004 ASCII 25774 12 cms cryptographic message syntax message This document describes protocol options for conveying objects that have been protected using the Cryptographic Message Syntax (CMS) and Secure/Multipurpose Internet Mail Extensions (S/MIME) version 3.1 over an X.400 message transfer system. [STANDARDS TRACK] ietf-smime-x400transport-09 PROPOSED STANDARD PROPOSED STANDARD RFC3856 A Presence Event Package for the Session Initiation Protocol (SIP) J. Rosenberg August 2004 ASCII 62956 27 subscription notification This document describes the usage of the Session Initiation Protocol (SIP) for subscriptions and notifications of presence. Presence is defined as the willingness and ability of a user to communicate with other users on the network. Historically, presence has been limited to "on-line" and "off-line" indicators; the notion of presence here is broader. Subscriptions and notifications of presence are supported by defining an event package within the general SIP event notification framework. This protocol is also compliant with the Common Presence Profile (CPP) framework. [STANDARDS TRACK] ietf-simple-presence-10 PROPOSED STANDARD PROPOSED STANDARD RFC3857 A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP) J. Rosenberg August 2004 ASCII 46221 20 This document defines the watcher information template-package for the Session Initiation Protocol (SIP) event framework. Watcher information refers to the set of users subscribed to a particular resource within a particular event package. Watcher information changes dynamically as users subscribe, unsubscribe, are approved, or are rejected. A user can subscribe to this information, and therefore learn about changes to it. This event package is a template-package because it can be applied to any event package, including itself. [STANDARDS TRACK] ietf-simple-winfo-package-05 PROPOSED STANDARD PROPOSED STANDARD RFC3858 An Extensible Markup Language (XML) Based Format for Watcher Information J. Rosenberg August 2004 ASCII 26416 13 xml Watchers are defined as entities that request (i.e., subscribe to) information about a resource. There is fairly complex state associated with these subscriptions. The union of the state for all subscriptions to a particular resource is called the watcher information for that resource. This state is dynamic, changing as subscribers come and go. As a result, it is possible, and indeed useful, to subscribe to the watcher information for a particular resource. In order to enable this, a format is needed to describe the state of watchers on a resource. This specification describes an Extensible Markup Language (XML) document format for such state. [STANDARDS TRACK] ietf-simple-winfo-format-04 PROPOSED STANDARD PROPOSED STANDARD RFC3859 Common Profile for Presence (CPP) J. Peterson August 2004 ASCII 30537 15 data formats semantics instant messaging At the time this document was written, numerous presence protocols were in use (largely as components of commercial instant messaging services), and little interoperability between services based on these protocols has been achieved. This specification defines common semantics and data formats for presence to facilitate the creation of gateways between presence services. [STANDARDS TRACK] ietf-impp-pres-04 PROPOSED STANDARD PROPOSED STANDARD RFC3860 Common Profile for Instant Messaging (CPIM) J. Peterson August 2004 ASCII 26486 13 data formats semantics instant messaging At the time this document was written, numerous instant messaging protocols were in use, and little interoperability between services based on these protocols has been achieved. This specification defines common semantics and data formats for instant messaging to facilitate the creation of gateways between instant messaging services. [STANDARDS TRACK] ietf-impp-im-04 PROPOSED STANDARD PROPOSED STANDARD RFC3861 Address Resolution for Instant Messaging and Presence J. Peterson August 2004 ASCII 15764 8 uri schemes universal resource identifier impp instant messaging and presence protocol presentity instant inbox Presence and instant messaging are defined in RFC 2778. The Common Profiles for Presence and Instant Messaging define two Universal Resource Identifier (URI) schemes: 'im' for INSTANT INBOXes and 'pres' for PRESENTITIES. This document provides guidance for locating the resources associated with URIs that employ these schemes. [STANDARDS TRACK] ietf-impp-srv-04 PROPOSED STANDARD PROPOSED STANDARD RFC3862 Common Presence and Instant Messaging (CPIM): Message Format G. Klyne D. Atkins August 2004 ASCII 56133 30 instant messaging and presence protocol message/cpim This memo defines the MIME content type 'Message/CPIM', a message format for protocols that conform to the Common Profile for Instant Messaging (CPIM) specification. [STANDARDS TRACK] ietf-impp-cpim-msgfmt-09 PROPOSED STANDARD PROPOSED STANDARD RFC3863 Presence Information Data Format (PIDF) H. Sugano S. Fujimoto G. Klyne A. Bateman W. Carr J. Peterson August 2004 ASCII 56956 28 instant messaging and presence protocol cpp common profile for presence presence data format application/pidf+xml This memo specifies the Common Profile for Presence (CPP) Presence Information Data Format (PIDF) as a common presence data format for CPP-compliant Presence protocols, and also defines a new media type "application/pidf+xml" to represent the XML MIME entity for PIDF. [STANDARDS TRACK] ietf-impp-cpim-pidf-08 PROPOSED STANDARD PROPOSED STANDARD RFC3864 Registration Procedures for Message Header Fields G. Klyne M. Nottingham J. Mogul September 2004 ASCII 36231 17 Internet mail HTTP Netnews This specification defines registration procedures for the message header fields used by Internet mail, HTTP, Netnews and other applications. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. klyne-msghdr-registry-07 BCP0090 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3865 A No Soliciting Simple Mail Transfer Protocol (SMTP) Service Extension C. Malamud September 2004 ASCII 40717 19 unsolicited bulk email ube no soliciting solicitation class keywords solicitation mail header trace fields This document proposes an extension to Soliciting Simple Mail Transfer Protocol (SMTP) for an electronic mail equivalent to the real-world "No Soliciting" sign. In addition to the service extension, a new message header and extensions to the existing "received" message header are described. [STANDARDS TRACK] malamud-no-soliciting-07 PROPOSED STANDARD PROPOSED STANDARD RFC3866 Language Tags and Ranges in the Lightweight Directory Access Protocol (LDAP) K. Zeilenga Editor July 2004 ASCII 31501 15 lightweight directory access protocol servers It is often desirable to be able to indicate the natural language associated with values held in a directory and to be able to query the directory for values which fulfill the user's language needs. This document details the use of Language Tags and Ranges in the Lightweight Directory Access Protocol (LDAP). [STANDARDS TRACK] zeilenga-ldap-rfc2596-05 RFC2596 PROPOSED STANDARD PROPOSED STANDARD RFC3867 Payment Application Programmers Interface (API) for v1.0 Internet Open Trading Protocol (IOTP) Y. Kawatsura M. Hiroya H. Beykirch November 2004 ASCII 234572 106 modules data format exchange The Internet Open Trading Protocol (IOTP) provides a data exchange format for trading purposes while integrating existing pure payment protocols seamlessly. This motivates the multiple layered system architecture which consists of at least some generic IOTP application core and multiple specific payment modules. <br> This document addresses a common interface between the IOTP application core and the payment modules, enabling the interoperability between these kinds of modules. Furthermore, such an interface provides the foundations for a plug-in-mechanism in actual implementations of IOTP application cores. Such interfaces exist at the Consumers', the Merchants' and the Payment Handlers' installations connecting the IOTP application core and the payment software components/legacy systems. This memo provides information for the Internet community. ietf-trade-iotp-v1.0-papi-06a INFORMATIONAL INFORMATIONAL RFC3868 Signalling Connection Control Part User Adaptation Layer (SUA) J. Loughney Editor G. Sidebottom L. Coene G. Verwimp J. Keller B. Bidulock October 2004 ASCII 294116 131 sctp stream control transmission protocol modular symmetric signalling gateway signalling endpoint architecture This document defines a protocol for the transport of any Signalling Connection Control Part-User signalling over IP using the Stream Control Transmission Protocol. The protocol is designed to be modular and symmetric, to allow it to work in diverse architectures, such as a Signalling Gateway to IP Signalling Endpoint architecture as well as a peer-to-peer IP Signalling Endpoint architecture. [STANDARDS TRACK] ietf-sigtran-sua-16 PROPOSED STANDARD PROPOSED STANDARD RFC3869 IAB Concerns and Recommendations Regarding Internet Research and Evolution R. Atkinson Editor S. Floyd Editor Internet Architecture Board August 2004 ASCII 78250 30 internet architecture board internet infrastructure non-commercial funding This document discusses IAB concerns that ongoing research is needed to further the evolution of the Internet infrastructure, and that consistent, sufficient non-commercial funding is needed to enable such research. This memo provides information for the Internet community. iab-research-funding-03 INFORMATIONAL INFORMATIONAL RFC3870 application/rdf+xml Media Type Registration A. Swartz September 2004 ASCII 14195 8 xml extensible markup language mime multipurpose internet mail extensions rdf resource description framework This document describes a media type (application/rdf+xml) for use with the Extensible Markup Language (XML) serialization of the Resource Description Framework (RDF). RDF is a language designed to support the Semantic Web, by facilitating resource description and data exchange on the Web. RDF provides common structures that can be used for interoperable data exchange and follows the World Wide Web Consortium (W3C) design principles of interoperability, evolution, and decentralization. This memo provides information for the Internet community. swartz-rdfcore-rdfxml-mediatype-05 INFORMATIONAL INFORMATIONAL RFC3871 Operational Security Requirements for Large Internet Service Provider (ISP) IP Network Infrastructure G. Jones Editor September 2004 ASCII 151101 81 This document defines a list of operational security requirements for the infrastructure of large Internet Service Provider (ISP) IP networks (routers and switches). A framework is defined for specifying "profiles", which are collections of requirements applicable to certain network topology contexts (all, core-only, edge-only...). The goal is to provide network operators a clear, concise way of communicating their security requirements to vendors. This memo provides information for the Internet community. jones-opsec-06 INFORMATIONAL INFORMATIONAL RFC3872 Management Information Base for Telephony Routing over IP (TRIP) D. Zinman D. Walker J. Jiang September 2004 ASCII 98614 53 mib This memo defines a portion of the Management Information Base (MIB) module for use with network management protocols in the Internet community. In particular, it describes a set of managed objects that are used to manage Telephony Routing over IP (TRIP) devices. [STANDARDS TRACK] ietf-iptel-trip-mib-10 PROPOSED STANDARD PROPOSED STANDARD RFC3873 Stream Control Transmission Protocol (SCTP) Management Information Base (MIB) J. Pastor M. Belinchon September 2004 ASCII 82403 46 The Stream Control Transmission Protocol (SCTP) is a reliable transport protocol operating on top of a connectionless packet network such as IP. It is designed to transport public switched telephone network (PSTN) signaling messages over the connectionless packet network, but is capable of broader applications. <br> This memo defines the Management Information Base (MIB) module which describes the minimum set of objects needed to manage the implementation of the SCTP. [STANDARDS TRACK] ietf-sigtran-sctp-mib-10 PROPOSED STANDARD PROPOSED STANDARD RFC3874 A 224-bit One-way Hash Function: SHA-224 R. Housley September 2004 ASCII 11600 6 secure standard This document specifies a 224-bit one-way hash function, called SHA-224. SHA-224 is based on SHA-256, but it uses a different initial value and the result is truncated to 224 bits. This memo provides information for the Internet community. ietf-pkix-sha224-01 INFORMATIONAL INFORMATIONAL RFC3875 The Common Gateway Interface (CGI) Version 1.1 D. Robinson K. Coar October 2004 ASCII 80728 36 PDF 121026 www world wide web The Common Gateway Interface (CGI) is a simple interface for running external programs, software or gateways under an information server in a platform-independent manner. Currently, the supported information servers are HTTP servers. <br> The interface has been in use by the World-Wide Web (WWW) since 1993. This specification defines the 'current practice' parameters of the 'CGI/1.1' interface developed and documented at the U.S. National Centre for Supercomputing Applications. This document also defines the use of the CGI/1.1 interface on UNIX(R) and other, similar systems. This memo provides information for the Internet community. coar-cgi-v11-04 INFORMATIONAL INFORMATIONAL RFC3876 Returning Matched Values with the Lightweight Directory Access Protocol version 3 (LDAPv3) D. Chadwick S. Mullan September 2004 ASCII 24233 12 attribute filter This document describes a control for the Lightweight Directory Access Protocol version 3 that is used to return a subset of attribute values from an entry. Specifically, only those values that match a "values return" filter. Without support for this control, a client must retrieve all of an attribute's values and search for specific values locally. [STANDARDS TRACK] ietf-ldapext-matchedval-07 PROPOSED STANDARD PROPOSED STANDARD RFC3877 Alarm Management Information Base (MIB) S. Chisholm D. Romascanu September 2004 ASCII 149783 75 alarm mib iana-itu-alarm-tc-mib itu-alarm-tc-mib itu-alarm-mib 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 management objects used for modelling and storing alarms. [STANDARDS TRACK] ietf-disman-alarm-mib-18 PROPOSED STANDARD PROPOSED STANDARD RFC3878 Alarm Reporting Control Management Information Base (MIB) H. Lam A. Huynh D. Perkins September 2004 ASCII 31093 16 alarm condition probably cause 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 controlling the reporting of alarm conditions. [STANDARDS TRACK] ietf-disman-conditionmib-10 PROPOSED STANDARD PROPOSED STANDARD RFC3879 Deprecating Site Local Addresses C. Huitema B. Carpenter September 2004 ASCII 24142 10 ipv6 architecture This document describes the issues surrounding the use of IPv6 site-local unicast addresses in their original form, and formally deprecates them. This deprecation does not prevent their continued use until a replacement has been standardized and implemented. [STANDARDS TRACK] ietf-ipv6-deprecate-site-local-03 PROPOSED STANDARD PROPOSED STANDARD RFC3880 Call Processing Language (CPL): A Language for User Control of Internet Telephony Services J. Lennox X. Wu H. Schulzrinne October 2004 ASCII 154991 74 This document defines the Call Processing Language (CPL), a language to describe and control Internet telephony services. It is designed to be implementable on either network servers or user agents. It is meant to be simple, extensible, easily edited by graphical clients, and independent of operating system or signalling protocol. It is suitable for running on a server where users may not be allowed to execute arbitrary programs, as it has no variables, loops, or ability to run external programs. [STANDARDS TRACK] ietf-iptel-cpl-09 PROPOSED STANDARD PROPOSED STANDARD RFC3881 Security Audit and Access Accountability Message XML Data Definitions for Healthcare Applications G. Marshall September 2004 ASCII 86130 47 marshall-security-audit-12 INFORMATIONAL RFC3882 Configuring BGP to Block Denial-of-Service Attacks D. Turk September 2004 ASCII 19637 8 dos border gateway protocol This document describes an operational technique that uses BGP communities to remotely trigger black-holing of a particular destination network to block denial-of-service attacks. Black-holing can be applied on a selection of routers rather than all BGP-speaking routers in the network. The document also describes a sinkhole tunnel technique using BGP communities and tunnels to pull traffic into a sinkhole router for analysis. This memo provides information for the Internet community. turk-bgp-dos-07 INFORMATIONAL INFORMATIONAL RFC3883 Detecting Inactive Neighbors over OSPF Demand Circuits (DC) S. Rao A. Zinin A. Roy October 2004 ASCII 13100 6 OSPF-DC Open Shortest Path First OSPF is a link-state intra-domain routing protocol used in IP networks. OSPF behavior over demand circuits (DC) is optimized in RFC 1793 to minimize the amount of overhead traffic. A part of the OSPF demand circuit extensions is the Hello suppression mechanism. This technique allows a demand circuit to go down when no interesting traffic is going through the link. However, it also introduces a problem, where it becomes impossible to detect an OSPF-inactive neighbor over such a link. This memo introduces a new mechanism called "neighbor probing" to address the above problem. [STANDARDS TRACK] ietf-ospf-dc-07 RFC1793 PROPOSED STANDARD PROPOSED STANDARD RFC3884 Use of IPsec Transport Mode for Dynamic Routing J. Touch L. Eggert Y. Wang September 2004 ASCII 59437 IPsec can secure the links of a multihop network to protect communication between trusted components, e.g., for a secure virtual network (VN), overlay, or virtual private network (VPN). Virtual links established by IPsec tunnel mode can conflict with routing and forwarding inside VNs because IP routing depends on references to interfaces and next-hop IP addresses. The IPsec tunnel mode specification is ambiguous on this issue, so even compliant implementations cannot be trusted to avoid conflicts. An alternative to tunnel mode uses non-IPsec IPIP encapsulation together with IPsec transport mode, which we call IIPtran. IPIP encapsulation occurs as a separate initial step, as the result of a forwarding lookup of the VN packet. IPsec transport mode processes the resulting (tunneled) IP packet with an SA determined through a security association database (SAD) match on the tunnel header. IIPtran supports dynamic routing inside the VN without changes to the current IPsec architecture. IIPtran demonstrates how to configure any compliant IPsec implementation to avoid the aforementioned conflicts. IIPtran is also compared to several alternative mechanisms for VN routing and their respective impact on IPsec, routing, policy enforcement, and interactions with the Internet Key Exchange (IKE). This memo provides information for the Internet community. touch-ipsec-vpn-07 INFORMATIONAL INFORMATIONAL RFC3885 SMTP Service Extension for Message Tracking E. Allman T. Hansen September 2004 ASCII 17458 9 simple mail transfer protocol This memo defines an extension to the SMTP service whereby a client may mark a message for future tracking. [STANDARDS TRACK] ietf-msgtrk-smtpext-05 RFC3461 PROPOSED STANDARD PROPOSED STANDARD RFC3886 An Extensible Message Format for Message Tracking Responses E. Allman September 2004 ASCII 21746 11 Delivery Status Notifications DSN Message Disposition Notifications MDN Message Tracking is expected to be used to determine the status of undelivered e-mail upon request. Tracking is used in conjunction with Delivery Status Notifications (DSN) and Message Disposition Notifications (MDN); generally, a message tracking request will be issued only when a DSN or MDN has not been received within a reasonable timeout period. <br> This memo defines a MIME content-type for message tracking status in the same spirit as RFC 3464, "An Extensible Message Format for Delivery Status Notifications". It is to be issued upon a request as described in "Message Tracking Query Protocol". This memo defines only the format of the status information. An extension to SMTP to label messages for further tracking and request tracking status is defined in a separate memo. [STANDARDS TRACK] ietf-msgtrk-trkstat-05 RFC3463 PROPOSED STANDARD PROPOSED STANDARD RFC3887 Message Tracking Query Protocol T. Hansen September 2004 ASCII 42763 23 mtqp ESMTP Customers buying enterprise message systems often ask: Can I track the messages? Message tracking is the ability to find out the path that a particular message has taken through a messaging system and the current routing status of that message. This document describes the Message Tracking Query Protocol that is used in conjunction with extensions to the ESMTP protocol to provide a complete message tracking solution for the Internet. [STANDARDS TRACK] ietf-msgtrk-mtqp-12 PROPOSED STANDARD PROPOSED STANDARD RFC3888 Message Tracking Model and Requirements T. Hansen September 2004 ASCII 20950 11 Customers buying enterprise message systems often ask: Can I track the messages? Message tracking is the ability to find out the path that a particular message has taken through a messaging system and the current routing status of that message. This document provides a model of message tracking that can be used for understanding the Internet-wide message infrastructure and to further enhance those capabilities to include message tracking, as well as requirements for proposed message tracking solutions. This memo provides information for the Internet community. ietf-msgtrk-model-07 INFORMATIONAL INFORMATIONAL RFC3890 A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP) M. Westerlund September 2004 ASCII 49894 22 tias application specific maximum ietf-mmusic-sdp-bwparam-06 PROPOSED STANDARD PROPOSED STANDARD RFC3891 The Session Initiation Protocol (SIP) "Replaces" Header R. Mahy B. Biggs R. Dean September 2004 ASCII 34180 16 multi-party applications call control This document defines a new header for use with Session Initiation Protocol (SIP) multi-party applications and call control. The Replaces header is used to logically replace an existing SIP dialog with a new SIP dialog. This primitive can be used to enable a variety of features, for example: "Attended Transfer" and "Call Pickup". Note that the definition of these example features is non-normative. [STANDARDS TRACK] ietf-sip-replaces-05 PROPOSED STANDARD PROPOSED STANDARD RFC3892 The Session Initiation Protocol (SIP) Referred-By Mechanism R. Sparks September 2004 ASCII 52441 25 REFER The Session Initiation Protocol (SIP) REFER method provides a mechanism where one party (the referrer) gives a second party (the referee) an arbitrary URI to reference. If that URI is a SIP URI, the referee will send a SIP request, often an INVITE, to that URI (the refer target). This document extends the REFER method, allowing the referrer to provide information about the REFER request to the refer target using the referee as an intermediary. This information includes the identity of the referrer and the URI to which the referrer referred. The mechanism utilizes S/MIME to help protect this information from a malicious intermediary. This protection is optional, but a recipient may refuse to accept a request unless it is present. [STANDARDS TRACK] ietf-sip-referredby-05 PROPOSED STANDARD PROPOSED STANDARD RFC3893 Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) Format J. Peterson September 2004 ASCII 28500 13 authenticated identity body digitally-signed SIP message message fragment Authenticated Identity Bodies AIB RFC 3261 introduces the concept of adding an S/MIME body to a Session Initiation Protocol (SIP) request or response in order to provide reference integrity over its headers. This document provides a more specific mechanism to derive integrity and authentication properties from an 'authenticated identity body', a digitally-signed SIP message, or message fragment. A standard format for such bodies (known as Authenticated Identity Bodies, or AIBs) is given in this document. Some considerations for the processing of AIBs by recipients of SIP messages with such bodies are also given. [STANDARDS TRACK] ietf-sip-authid-body-03 PROPOSED STANDARD PROPOSED STANDARD RFC3894 Sieve Extension: Copying Without Side Effects J. Degener October 2004 ASCII 9018 5 client server The Sieve scripting language allows users to control handling and disposal of their incoming e-mail. By default, an e-mail message that is processed by a Sieve script is saved in the owner's "inbox". Actions such as "fileinto" and "redirect" cancel this default behavior. <br> This document defines a new keyword parameter, ":copy", to be used with the Sieve "fileinto" and "redirect" actions. Adding ":copy" to an action suppresses cancellation of the default "inbox" save. It allows users to add commands to an existing script without changing the meaning of the rest of the script. [STANDARDS TRACK] degener-sieve-copy-03 PROPOSED STANDARD PROPOSED STANDARD RFC3895 Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types O. Nicklass Editor September 2004 ASCII 163841 84 management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing DS1, E1, DS2 and E2 interfaces. This document is a companion to the documents that define Managed Objects for the DS0, DS3/E3 and Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Types. This document obsoletes RFC 2495. [STANDARDS TRACK] ietf-atommib-rfc2495bis-06 RFC2495 PROPOSED STANDARD PROPOSED STANDARD RFC3896 Definitions of Managed Objects for the DS3/E3 Interface Type O. Nicklass Editor September 2004 ASCII 129547 63 DS3-E3-MIB management information base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing DS3 and E3 interfaces. This document is a companion to the documents that define Managed Objects for the DS0, DS1/E1/DS2/E2 and Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Types. This document obsoletes RFC 2496. [STANDARDS TRACK] ietf-atommib-rfc2496bis-06 RFC2496 PROPOSED STANDARD PROPOSED STANDARD RFC3897 Open Pluggable Edge Services (OPES) Entities and End Points Communication A. Barbir September 2004 ASCII 33890 14 tracing non-blocking bypass This memo documents tracing and non-blocking (bypass) requirements for Open Pluggable Edge Services (OPES). This memo provides information for the Internet community. ietf-opes-end-comm-08 INFORMATIONAL INFORMATIONAL RFC3898 Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) V. Kalusivalingam October 2004 ASCII 13955 7 NIS Servers NIS+ Servers NIS Client Domain Name NIS+ Client Domain name This document describes four options for Network Information Service (NIS) related configuration information in Dynamic Host Configuration Protocol for IPv6 (DHCPv6): NIS Servers, NIS+ Servers, NIS Client Domain Name, NIS+ Client Domain name. [STANDARDS TRACK] ietf-dhc-dhcpv6-opt-nisconfig-05 PROPOSED STANDARD PROPOSED STANDARD RFC3901 DNS IPv6 Transport Operational Guidelines A. Durand J. Ihren September 2004 ASCII 10025 5 domain name system internet protocol This memo provides guidelines and Best Current Practice for operating DNS in a world where queries and responses are carried in a mixed environment of IPv4 and IPv6 networks. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-dnsop-ipv6-transport-guidelines-02 BCP0091 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3902 The "application/soap+xml" media type M. Baker M. Nottingham September 2004 ASCII 10575 5 This document defines the "application/soap+xml" media type which can be used to describe SOAP 1.2 messages serialized as XML 1.0. This memo provides information for the Internet community. baker-soap-media-reg-06 INFORMATIONAL INFORMATIONAL RFC3903 Session Initiation Protocol (SIP) Extension for Event State Publication A. Niemi Editor October 2004 ASCII 72062 32 presence information package This document describes an extension to the Session Initiation Protocol (SIP) for publishing event state used within the SIP Events framework. The first application of this extension is for the publication of presence information. <br> The mechanism described in this document can be extended to support publication of any event state for which there exists an appropriate event package. It is not intended to be a general-purpose mechanism for transport of arbitrary data, as there are better-suited mechanisms for this purpose. [STANDARDS TRACK] ietf-sip-publish-04 PROPOSED STANDARD PROPOSED STANDARD RFC3904 Evaluation of IPv6 Transition Mechanisms for Unmanaged Networks C. Huitema R. Austein S. Satapati R. van der Pol September 2004 ASCII 46844 19 home office internet protocol This document analyzes issues involved in the transition of "unmanaged networks" from IPv4 to IPv6. Unmanaged networks typically correspond to home networks or small office networks. A companion paper analyzes out the requirements for mechanisms needed in various transition scenarios of these networks to IPv6. Starting from this analysis, we evaluate the suitability of mechanisms that have already been specified, proposed, or deployed. This memo provides information for the Internet community. ietf-v6ops-unmaneval-03 INFORMATIONAL INFORMATIONAL RFC3905 A Template for IETF Patent Disclosures and Licensing Declarations V. See Editor September 2004 ASCII 16110 9 ipr This document describes a proposal for one form of a template for IETF patent disclosures and licensing declarations. The optional use of this template is meant to simplify the process of such disclosures and licensing declarations and to assist disclosers in providing the necessary information to meet the obligations documented in RFC 3668. This memo provides information for the Internet community. ietf-ipr-template-09 INFORMATIONAL INFORMATIONAL RFC3906 Calculating Interior Gateway Protocol (IGP) Routes Over Traffic Engineering Tunnels N. Shen H. Smit October 2004 ASCII 18410 8 hop-by-hop link-state routing protocols SPF shortest path first This document describes how conventional hop-by-hop link-state routing protocols interact with new Traffic Engineering capabilities to create Interior Gateway Protocol (IGP) shortcuts. In particular, this document describes how Dijkstra's Shortest Path First (SPF) algorithm can be adapted so that link-state IGPs will calculate IP routes to forward traffic over tunnels that are set up by Traffic Engineering. This memo provides information for the Internet community. ietf-rtgwg-igp-shortcut-01 INFORMATIONAL INFORMATIONAL RFC3909 Lightweight Directory Access Protocol (LDAP) Cancel Operation K. Zeilenga October 2004 ASCII 13423 7 abandon operation outstanding operation This specification describes a Lightweight Directory Access Protocol (LDAP) extended operation to cancel (or abandon) an outstanding operation. Unlike the LDAP Abandon operation, but like the X.511 Directory Access Protocol (DAP) Abandon operation, this operation has a response which provides an indication of its outcome. [STANDARDS TRACK] zeilenga-ldap-cancel-11 PROPOSED STANDARD PROPOSED STANDARD RFC3910 The SPIRITS (Services in PSTN requesting Internet Services) Protocol V. Gurbani Editor A. Brusilovsky I. Faynberg J. Gato H. Lu M. Unmehopa October 2004 ASCII 110515 50 pstn sip services event notification eventpackages internet call waiting xml wireless intelligent network in detection point dp This document describes the Services in PSTN (Public Switched Telephone Network) requesting Internet Services (SPIRITS) protocol. The purpose of the SPIRITS protocol is to support services that originate in the cellular or wireline PSTN and necessitate interactions between the PSTN and the Internet. On the PSTN side, the SPIRITS services are most often initiated from the Intelligent Network (IN) entities. Internet Call Waiting and Internet Caller-ID Delivery are examples of SPIRITS services, as are location-based services on the cellular network. The protocol defines the building blocks from which many other services can be built. [STANDARDS TRACK] ietf-spirits-protocol-08 PROPOSED STANDARD PROPOSED STANDARD RFC3911 The Session Initiation Protocol (SIP) "Join" Header R. Mahy D. Petrie October 2004 ASCII 35373 17 This document defines a new header for use with SIP multi-party applications and call control. The Join header is used to logically join an existing SIP dialog with a new SIP dialog. This primitive can be used to enable a variety of features, for example: "Barge-In", answering-machine-style "Message Screening" and "Call Center Monitoring". Note that definition of these example features is non-normative. [STANDARDS TRACK] ietf-sip-join-03 PROPOSED STANDARD PROPOSED STANDARD RFC3912 WHOIS Protocol Specification L. Daigle September 2004 ASCII 7770 4 NICNAME This document updates the specification of the WHOIS protocol, thereby obsoleting RFC 954. The update is intended to remove the material from RFC 954 that does not have to do with the on-the-wire protocol, and is no longer applicable in today's Internet. This document does not attempt to change or update the protocol per se, or document other uses of the protocol that have come into existence since the publication of RFC 954. [STANDARDS TRACK] daigle-rfc954bis-01 RFC0954 RFC0812 DRAFT STANDARD DRAFT STANDARD RFC3913 Border Gateway Multicast Protocol (BGMP): Protocol Specification D. Thaler September 2004 ASCII 97443 41 enter-domain source-specific multicast ssm This document describes the Border Gateway Multicast Protocol (BGMP), a protocol for inter-domain multicast routing. BGMP builds shared trees for active multicast groups, and optionally allows receiver domains to build source-specific, inter-domain, distribution branches where needed. BGMP natively supports "source-specific multicast" (SSM). To also support "any-source multicast" (ASM), BGMP requires that each multicast group be associated with a single root (in BGMP it is referred to as the root domain). It requires that different ranges of the multicast address space are associated (e.g., with Unicast-Prefix-Based Multicast addressing) with different domains. Each of these domains then becomes the root of the shared domain-trees for all groups in its range. Multicast participants will generally receive better multicast service if the session initiator's address allocator selects addresses from its own domain's part of the space, thereby causing the root domain to be local to at least one of the session participants. This memo provides information for the Internet community. ietf-bgmp-spec-06 INFORMATIONAL INFORMATIONAL RFC3914 Open Pluggable Edge Services (OPES) Treatment of IAB Considerations A. Barbir A. Rousskov October 2004 ASCII 37411 16 IETF Internet Architecture Board (IAB) expressed nine architecture-level considerations for the Open Pluggable Edge Services (OPES) framework. This document describes how OPES addresses those considerations. This memo provides information for the Internet community. ietf-opes-iab-05 INFORMATIONAL INFORMATIONAL RFC3915 Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP) S. Hollenbeck September 2004 ASCII 45467 23 dns name system This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the management of Domain Name System (DNS) domain names subject to "grace period" policies defined by the Internet Corporation for Assigned Names and Numbers (ICANN). Grace period policies exist to allow protocol actions to be reversed or otherwise revoked during a short period of time after the protocol action has been performed. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for grace period processing. [STANDARDS TRACK] hollenbeck-epp-rgp-04 PROPOSED STANDARD PROPOSED STANDARD RFC3916 Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3) X. Xiao Editor D. McPherson Editor P. Pate Editor September 2004 ASCII 43856 19 This document describes base requirements for the Pseudo-Wire Emulation Edge to Edge Working Group (PWE3 WG). It provides guidelines for other working group documents that will define mechanisms for providing pseudo-wire emulation of Ethernet, ATM, and Frame Relay. Requirements for pseudo-wire emulation of TDM (i.e., "synchronous bit streams at rates defined by ITU G.702") are defined in another document. It should be noted that the PWE3 WG standardizes mechanisms that can be used to provide PWE3 services, but not the services themselves. This memo provides information for the Internet community. ietf-pwe3-requirements-08 INFORMATIONAL INFORMATIONAL RFC3917 Requirements for IP Flow Information Export (IPFIX) J. Quittek T. Zseby B. Claise S. Zander October 2004 ASCII 81615 33 ipfix routers measurment middleboxes This memo defines requirements for the export of measured IP flow information out of routers, traffic measurement probes, and middleboxes. This memo provides information for the Internet community. ietf-ipfix-reqs-16 INFORMATIONAL INFORMATIONAL RFC3918 Methodology for IP Multicast Benchmarking D. Stopp B. Hickman October 2004 ASCII 64652 31 The purpose of this document is to describe methodology specific to the benchmarking of multicast IP forwarding devices. It builds upon the tenets set forth in RFC 2544, RFC 2432 and other IETF Benchmarking Methodology Working Group (BMWG) efforts. This document seeks to extend these efforts to the multicast paradigm. <br> The BMWG produces two major classes of documents: Benchmarking Terminology documents and Benchmarking Methodology documents. The Terminology documents present the benchmarks and other related terms. The Methodology documents define the procedures required to collect the benchmarks cited in the corresponding Terminology documents. This memo provides information for the Internet community. ietf-bmwg-mcastm-14 INFORMATIONAL INFORMATIONAL RFC3919 Remote Network Monitoring (RMON) Protocol Identifiers for IPv6 and Multi Protocol Label Switching (MPLS) E. Stephan J. Palet October 2004 ASCII 14228 8 mib This memo defines additional (to those in RFC 2896) protocol identifier examples for IP version 6 and MPLS protocols. These can be used to produce valid protocolDirTable INDEX encodings, as defined by the Remote Network Monitoring MIB (Management Information Base) Version 2 [RFC2021] and the RMON Protocol Identifier Reference [RFC2895]. <br> This document contains additional (to those in RFC 2896) protocol identifier macros for well-known protocols. A conformant implementation of the RMON-2 MIB [RFC2021] can be accomplished without the use of these protocol identifiers, and accordingly, this document does not specify any IETF standard. It is published to encourage better interoperability between RMON-2 agent implementations, by providing RMON related IPv6 and MPLS protocol information. This memo provides information for the Internet community. ietf-rmonmib-pi-ipv6-04 INFORMATIONAL INFORMATIONAL RFC3920 Extensible Messaging and Presence Protocol (XMPP): Core P. Saint-Andre Editor October 2004 ASCII 194313 30 instant messaging im extensible markup language xml jabber This memo defines the core features of the Extensible Messaging and Presence Protocol (XMPP), a protocol for streaming Extensible Markup Language (XML) elements in order to exchange structured information in close to real time between any two network endpoints. While XMPP provides a generalized, extensible framework for exchanging XML data, it is used mainly for the purpose of building instant messaging and presence applications that meet the requirements of RFC 2779. [STANDARDS TRACK] ietf-xmpp-core-24 PROPOSED STANDARD PROPOSED STANDARD RFC3921 Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence P. Saint-Andre Editor October 2004 ASCII 217527 107 instant messaging im extensible markup language xml jabber This memo describes extensions to and applications of the core features of the Extensible Messaging and Presence Protocol (XMPP) that provide the basic instant messaging (IM) and presence functionality defined in RFC 2779. [STANDARDS TRACK] ietf-xmpp-im-22 PROPOSED STANDARD PROPOSED STANDARD RFC3922 Mapping the Extensible Messaging and Presence Protocol (XMPP) to Common Presence and Instant Messaging (CPIM) P. Saint-Andre October 2004 ASCII 70790 34 xml extensible markup language im instant messaging jabber This memo describes a mapping between the Extensible Messaging and Presence Protocol (XMPP) and the Common Presence and Instant Messaging (CPIM) specifications. [STANDARDS TRACK] ietf-xmpp-cpim-05 PROPOSED STANDARD PROPOSED STANDARD RFC3923 End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP) P. Saint-Andre October 2004 ASCII 51828 27 xml extensible markup language im instant messaging jabber This memo defines methods of end-to-end signing and object encryption for the Extensible Messaging and Presence Protocol (XMPP). [STANDARDS TRACK] ietf-xmpp-e2e-09 PROPOSED STANDARD PROPOSED STANDARD RFC3924 Cisco Architecture for Lawful Intercept in IP Networks F. Baker B. Foster C. Sharp October 2004 ASCII 40826 18 For the purposes of this document, lawful intercept is the lawfully authorized interception and monitoring of communications. Service providers are being asked to meet legal and regulatory requirements for the interception of voice as well as data communications in IP networks in a variety of countries worldwide. Although requirements vary from country to country, some requirements remain common even though details such as delivery formats may differ. This document describes Cisco's Architecture for supporting lawful intercept in IP networks. It provides a general solution that has a minimum set of common interfaces. This document does not attempt to address any of the specific legal requirements or obligations that may exist in a particular country. This memo provides information for the Internet community. baker-slem-architecture-02 INFORMATIONAL INFORMATIONAL RFC3925 Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4) J. Littlefield October 2004 ASCII 17999 9 dhc dhcp class vendor-specific The Dynamic Host Configuration Protocol (DHCP) options for Vendor Class and Vendor-Specific Information can be limiting or ambiguous when a DHCP client represents multiple vendors. This document defines two new options, modeled on the IPv6 options for vendor class and vendor-specific information, that contain Enterprise Numbers to remove ambiguity. [STANDARDS TRACK] ietf-dhc-vendor-03 PROPOSED STANDARD PROPOSED STANDARD RFC3926 FLUTE - File Delivery over Unidirectional Transport T. Paila M. Luby R. Lehtonen V. Roca R. Walsh October 2004 ASCII 81224 35 This document defines FLUTE, a protocol for the unidirectional delivery of files over the Internet, which is particularly suited to multicast networks. The specification builds on Asynchronous Layered Coding, the base protocol designed for massively scalable multicast distribution. This memo defines an Experimental Protocol for the Internet community. ietf-rmt-flute-08 EXPERIMENTAL EXPERIMENTAL RFC3928 Lightweight Directory Access Protocol (LDAP) Client Update Protocol (LCUP) R. Megginson Editor M. Smith O. Natkovich J. Parham October 2004 ASCII 36892 30 This document defines the Lightweight Directory Access Protocol (LDAP) Client Update Protocol (LCUP). The protocol is intended to allow an LDAP client to synchronize with the content of a directory information tree (DIT) stored by an LDAP server and to be notified about the changes to that content. [STANDARDS TRACK] ietf-ldup-lcup-06 PROPOSED STANDARD PROPOSED STANDARD RFC3929 Alternative Decision Making Processes for Consensus-Blocked Decisions in the IETF T. Hardie October 2004 ASCII 26493 11 This document proposes an experimental set of alternative decision-making processes for use in IETF working groups. There are a small number of cases in IETF working groups in which the group has come to consensus that a particular decision must be made but cannot agree on the decision itself. This document describes alternative mechanisms for reaching a decision in those cases. This is not meant to provide an exhaustive list, but to provide a known set of tools that can be used when needed. This memo defines an Experimental Protocol for the Internet community. hardie-alt-consensus-02 EXPERIMENTAL EXPERIMENTAL RFC3930 The Protocol versus Document Points of View in Computer Protocols D. Eastlake 3rd October 2004 ASCII 36892 15 This document contrasts two points of view: the "document" point of view, where digital objects of interest are like pieces of paper written and viewed by people, and the "protocol" point of view where objects of interest are composite dynamic network messages. Although each point of view has a place, adherence to a document point of view can be damaging to protocol design. By understanding both points of view, conflicts between them may be clarified and reduced. This memo provides information for the Internet community. eastlake-proto-doc-pov-05 INFORMATIONAL INFORMATIONAL RFC3931 Layer Two Tunneling Protocol - Version 3 (L2TPv3) J. Lau Editor M. Townsley Editor I. Goyret Editor March 2005 ASCII 214407 94 L2TP ppp point-to-point protocol packets This document describes "version 3" of the Layer Two Tunneling Protocol (L2TPv3). L2TPv3 defines the base control protocol and encapsulation for tunneling multiple Layer 2 connections between two IP nodes. Additional documents detail the specifics for each data link type being emulated. [STANDARDS TRACK] draft-ietf-l2tpext-l2tp-base-15 PROPOSED STANDARD PROPOSED STANDARD RFC3932 The IESG and RFC Editor Documents: Procedures H. Alvestrand October 2004 ASCII 17093 8 independent submission This document describes the IESG's procedures for handling documents submitted for RFC publication via the RFC Editor, subsequent to the changes proposed by the IESG at the Seoul IETF, March 2004. <br> This document updates procedures described in RFC 2026 and RFC 3710. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. iesg-rfced-documents-03 RFC3710 RFC2026 BCP0092 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3933 A Model for IETF Process Experiments J. Klensin S. Dawkins November 2004 ASCII 14409 7 The IETF has designed process changes over the last ten years in one of two ways: announcement by the IESG, sometimes based on informal agreements with limited community involvement and awareness, and formal use of the same mechanism used for protocol specification. The first mechanism has often proven to be too lightweight, the second too heavyweight. <br> This document specifies a middle-ground approach to the system of making changes to IETF process, one that relies heavily on a "propose and carry out an experiment, evaluate the experiment, and then establish permanent procedures based on operational experience" model rather than those previously attempted. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. klensin-process-july14-02 BCP0093 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3934 Updates to RFC 2418 Regarding the Management of IETF Mailing Lists M. Wasserman October 2004 ASCII 8488 5 BCP WG escape clause procedures This document is an update to RFC 2418 that gives WG chairs explicit responsibility for managing WG mailing lists. In particular, it gives WG chairs the authority to temporarily suspend the mailing list posting privileges of disruptive individuals. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. wasserman-rfc2418-ml-update-01 RFC2418 BCP0094 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3935 A Mission Statement for the IETF H. Alvestrand October 2004 ASCII 16639 7 This memo gives a mission statement for the IETF, tries to define the terms used in the statement sufficiently to make the mission statement understandable and useful, argues why the IETF needs a mission statement, and tries to capture some of the debate that led to this point. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. alvestrand-ietf-mission-02 BCP0095 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3936 Procedures for Modifying the Resource reSerVation Protocol (RSVP) K. Kompella J. Lang October 2004 ASCII 15314 7 resource reservation protocol label switched paths This memo specifies procedures for modifying the Resource reSerVation Protocol (RSVP). This memo also lays out new assignment guidelines for number spaces for RSVP messages, object classes, class-types, and sub-objects. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. kompella-rsvp-change-02 RFC3209 RFC2205 BCP0096 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3937 A Uniform Resource Name (URN) Namespace for the International Press Telecommunications Council (IPTC) M. Steidl October 2004 ASCII 15458 9 This document describes a URN (Uniform Resource Name) namespace for identifying persistent resources published by the International Press Telecommunications Council (IPTC). These resources include XML Data Type Definition files (DTD), XML Schema, Namespaces in XML, XSL stylesheets, other XML based document and documents of other data formats like PDF documents, Microsoft Office documents and others. This memo provides information for the Internet community. steidl-iptc-urn-00 INFORMATIONAL INFORMATIONAL RFC3938 Video-Message Message-Context T. Hansen October 2004 ASCII 6224 4 user agent ua The Message-Context header defined in RFC 3458 describes the context of a message (for example: fax-message or voice-message). This specification extends the Message-Context header with one additional context value: "video-message". <br> A receiving user agent (UA) may use this information as a hint to optimally present the message. [STANDARDS TRACK] hansen-lemonade-msgctxt-videomsg-01 RFC3458 PROPOSED STANDARD PROPOSED STANDARD RFC3939 Calling Line Identification for Voice Mail Messages G. Parsons J. Maruszak December 2004 ASCII 22739 11 This document describes a method for identifying the originating calling party in the headers of a stored voice mail message. Two new header fields are defined for this purpose: Caller_ID and Called_Name. Caller_id is used to store sufficient information for the recipient to callback, or reply to, the sender of the message. Caller-name provides the name of the person sending the message. [STANDARDS TRACK] ema-vpim-clid-09 PROPOSED STANDARD PROPOSED STANDARD RFC3940 Negative-acknowledgment (NACK)-Oriented Reliable Multicast (NORM) Protocol B. Adamson C. Bormann M. Handley J. Macker November 2004 ASCII 220549 80 This document describes the messages and procedures of the Negative-acknowledgment (NACK) Oriented Reliable Multicast (NORM) protocol. This protocol is designed to provide end-to-end reliable transport of bulk data objects or streams over generic IP multicast routing and forwarding services. NORM uses a selective, negative acknowledgment mechanism for transport reliability and offers additional protocol mechanisms to allow for operation with minimal "a priori" coordination among senders and receivers. A congestion control scheme is specified to allow the NORM protocol to fairly share available network bandwidth with other transport protocols such as Transmission Control Protocol (TCP). It is capable of operating with both reciprocal multicast routing among senders and receivers and with asymmetric connectivity (possibly a unicast return path) between the senders and receivers. The protocol offers a number of features to allow different types of applications or possibly other higher level transport protocols to utilize its service in different ways. The protocol leverages the use of FEC-based repair and other IETF reliable multicast transport (RMT) building blocks in its design. This memo defines an Experimental Protocol for the Internet community. ietf-rmt-pi-norm-10 EXPERIMENTAL EXPERIMENTAL RFC3941 Negative-Acknowledgment (NACK)-Oriented Reliable Multicast (NORM) Building Blocks B. Adamson C. Bormann M. Handley J. Macker November 2004 ASCII 92785 36 This document discusses the creation of negative-acknowledgment (NACK)-oriented reliable multicast (NORM) protocols. The rationale for NORM goals and assumptions are presented. Technical challenges for NACK-oriented (and in some cases general) reliable multicast protocol operation are identified. These goals and challenges are resolved into a set of functional "building blocks" that address different aspects of NORM protocol operation. It is anticipated that these building blocks will be useful in generating different instantiations of reliable multicast protocols. This memo defines an Experimental Protocol for the Internet community. ietf-rmt-bb-norm-09 EXPERIMENTAL EXPERIMENTAL RFC3942 Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) Options B. Volz November 2004 ASCII 13996 DHCP-BOOTP Bootstrap This document updates RFC 2132 to reclassify Dynamic Host Configuration Protocol version 4 (DHCPv4) option codes 128 to 223 (decimal) as publicly defined options to be managed by IANA in accordance with RFC 2939. This document directs IANA to make these option codes available for assignment as publicly defined DHCP options for future options. [STANDARDS TRACK] ietf-dhc-reclassify-options-01 RFC2132 PROPOSED STANDARD PROPOSED STANDARD RFC3943 Transport Layer Security (TLS) Protocol Compression Using Lempel-Ziv-Stac (LZS) R. Friend November 2004 ASCII 28942 13 lossless data compression algorithm TLS Record Protocol The Transport Layer Security (TLS) protocol (RFC 2246) includes features to negotiate selection of a lossless data compression method as part of the TLS Handshake Protocol and then to apply the algorithm associated with the selected method as part of the TLS Record Protocol. TLS defines one standard compression method, which specifies that data exchanged via the record protocol will not be compressed. This document describes an additional compression method associated with the Lempel-Ziv-Stac (LZS) lossless data compression algorithm for use with TLS. This document also defines the application of the LZS algorithm to the TLS Record Protocol. This memo provides information for the Internet community. friend-tls-lzs-compression-04 INFORMATIONAL INFORMATIONAL RFC3944 H.350 Directory Services T. Johnson S. Okubo S. Campos December 2004 ASCII 61160 30 ldap directory services h.350 h.323 h.320 h.235 sip The International Telecommunications Union Standardization Sector (ITU-T) has created the H.350 series of Recommendations that specify directory services architectures in support of multimedia conferencing protocols. The goal of the architecture is to 'directory enable' multimedia conferencing so that these services can leverage existing identity management and enterprise directories. A particular goal is to enable an enterprise or service provider to maintain a canonical source of users and their multimedia conferencing systems, so that multiple call servers from multiple vendors, supporting multiple protocols, can all access the same data store. <br> Because SIP is an IETF standard, the contents of H.350 and H.350.4 are made available via this document to the IETF community. This document contains the entire normative text of ITU-T Recommendations H.350 and H.350.4 in sections 4 and 5, respectively. The remaining sections are included only in this document, not in the ITU-T version. This memo provides information for the Internet community. johnson-h350-directory-serv-02 INFORMATIONAL INFORMATIONAL RFC3945 Generalized Multi-Protocol Label Switching (GMPLS) Architecture E. Mannie Editor October 2004 ASCII 166700 69 Future data and transmission networks will consist of elements such as routers, switches, Dense Wavelength Division Multiplexing (DWDM) systems, Add-Drop Multiplexors (ADMs), photonic cross-connects (PXCs), optical cross-connects (OXCs), etc. that will use Generalized Multi-Protocol Label Switching (GMPLS) to dynamically provision resources and to provide network survivability using protection and restoration techniques. <br> This document describes the architecture of GMPLS. GMPLS extends MPLS to encompass time-division (e.g., SONET/SDH, PDH, G.709), wavelength (lambdas), and spatial switching (e.g., incoming port or fiber to outgoing port or fiber). The focus of GMPLS is on the control plane of these various layers since each of them can use physically diverse data or forwarding planes. The intention is to cover both the signaling and the routing part of that control plane. [STANDARDS TRACK] ietf-ccamp-gmpls-architecture-07 PROPOSED STANDARD PROPOSED STANDARD RFC3946 Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) Control E. Mannie D. Papadimitriou October 2004 ASCII 52205 26 This document is a companion to the Generalized Multi-Protocol Label Switching (GMPLS) signaling. It defines the Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) technology specific information needed when using GMPLS signaling. [STANDARDS TRACK] ietf-ccamp-gmpls-sonet-sdh-08 PROPOSED STANDARD PROPOSED STANDARD RFC3947 Negotiation of NAT-Traversal in the IKE T. Kivinen B. Swander A. Huttunen V. Volpe January 2005 ASCII 34759 16 This document describes how to detect one or more network address translation devices (NATs) between IPsec hosts, and how to negotiate the use of UDP encapsulation of IPsec packets through NAT boxes in Internet Key Exchange (IKE). [STANDARDS TRACK] ietf-ipsec-nat-t-ike-08 PROPOSED STANDARD PROPOSED STANDARD RFC3948 UDP Encapsulation of IPsec ESP Packets A. Huttunen B. Swander V. Volpe L. DiBurro M. Stenberg January 2005 ASCII 30366 15 This protocol specification defines methods to encapsulate and decapsulate IP Encapsulating Security Payload (ESP) packets inside UDP packets for traversing Network Address Translators. ESP encapsulation, as defined in this document, can be used in both IPv4 and IPv6 scenarios. Whenever negotiated, encapsulation is used with Internet Key Exchange (IKE). [STANDARDS TRACK] ietf-ipsec-udp-encaps-09 PROPOSED STANDARD PROPOSED STANDARD RFC3949 File Format for Internet Fax R. Buckley D. Venable L. McIntyre G. Parsons J. Rafferty February 2005 ASCII 204903 84 FFIF TIFF Tag Image facsimile MIME multipurpose Internet mail extensions This document is a revised version of RFC 2301. The revisions, summarized in the list attached as Annex B, are based on discussions and suggestions for improvements that have been made since RFC 2301 was issued in March 1998, and on the results of independent implementations and interoperability testing. <br> This RFC 2301 revision describes the Tag Image File Format (TIFF) representation of image data specified by the International Telecommunication Union (ITU-T) Recommendations for black-and-white and color facsimile. This file format specification is commonly known as TIFF for Fax eXtended (TIFF-FX). It formally defines minimal, extended, and lossless Joint Bi-level Image experts Group (JBIG) profiles (Profiles S, F, J) for black-and-white fax and base JPEG, lossless JBIG, and Mixed Raster Content profiles (Profiles C, L, M) for color and grayscale fax. These profiles correspond to the content of the applicable ITU-T Recommendations. [STANDARDS TRACK] draft-ietf-fax-tiff-fx-14 RFC2301 DRAFT STANDARD DRAFT STANDARD RFC3950 Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type Registration L. McIntyre G. Parsons J. Rafferty February 2005 ASCII 13884 8 FFIF TIFF Tag Image facsimile MIME multipurpose Internet mail extensions This document describes the registration of the MIME sub-type image/tiff-fx. The encodings are defined by File Format for Internet Fax and its extensions. [STANDARDS TRACK] draft-ietf-fax-tiff-fx-reg-v2-01 RFC3250 DRAFT STANDARD DRAFT STANDARD RFC3951 Internet Low Bit Rate Codec (iLBC) S. Andersen A. Duric H. Astrom R. Hagen W. Kleijn J. Linden December 2004 ASCII 373442 194 This document specifies a speech codec suitable for robust voice communication over IP. The codec is developed by Global IP Sound (GIPS). It is designed for narrow band speech and results in a payload bit rate of 13.33 kbit/s for 30 ms frames and 15.20 kbit/s for 20 ms frames. The codec enables graceful speech quality degradation in the case of lost frames, which occurs in connection with lost or delayed IP packets. This memo defines an Experimental Protocol for the Internet community. ietf-avt-ilbc-codec-05 EXPERIMENTAL EXPERIMENTAL RFC3952 Real-time Transport Protocol (RTP) Payload Format for internet Low Bit Rate Codec (iLBC) Speech A. Duric S. Andersen December 2004 ASCII 28655 13 This document describes the Real-time Transport Protocol (RTP) payload format for the internet Low Bit Rate Codec (iLBC) Speech developed by Global IP Sound (GIPS). Also, within the document there are included necessary details for the use of iLBC with MIME and Session Description Protocol (SDP). This memo defines an Experimental Protocol for the Internet community. ietf-avt-rtp-ilbc-05 EXPERIMENTAL EXPERIMENTAL RFC3953 Telephone Number Mapping (ENUM) Service Registration for Presence Services J. Peterson January 2005 ASCII 13875 7 uniform resource identifier uri provisioning pres This document registers a Telephone Number Mapping (ENUM) service for presence. Specifically, this document focuses on provisioning pres URIs in ENUM. [STANDARDS TRACK] draft-ietf-enum-pres-01 PROPOSED STANDARD PROPOSED STANDARD RFC3954 Cisco Systems NetFlow Services Export Version 9 B. Claise Editor October 2004 ASCII 76360 33 This document specifies the data export format for version 9 of Cisco Systems' NetFlow services, for use by implementations on the network elements and/or matching collector programs. The version 9 export format uses templates to provide access to observations of IP packet flows in a flexible and extensible manner. A template defines a collection of fields, with corresponding descriptions of structure and semantics. This memo provides information for the Internet community. claise-netflow-9-08 INFORMATIONAL INFORMATIONAL RFC3955 Evaluation of Candidate Protocols for IP Flow Information Export (IPFIX) S. Leinen October 2004 ASCII 55143 23 This document contains an evaluation of the five candidate protocols for an IP Flow Information Export (IPFIX) protocol, based on the requirements document produced by the IPFIX Working Group. The protocols are characterized and grouped in broad categories, and evaluated against specific requirements. Finally, a recommendation is made to select the NetFlow v9 protocol as the basis for the IPFIX specification. This memo provides information for the Internet community. leinen-ipfix-eval-contrib-03 INFORMATIONAL INFORMATIONAL RFC3956 Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address P. Savola B. Haberman November 2004 ASCII 40136 18 internet protocol This memo defines an address allocation policy in which the address of the Rendezvous Point (RP) is encoded in an IPv6 multicast group address. For Protocol Independent Multicast - Sparse Mode (PIM-SM), this can be seen as a specification of a group-to-RP mapping mechanism. This allows an easy deployment of scalable inter-domain multicast and simplifies the intra-domain multicast configuration as well. This memo updates the addressing format presented in RFC 3306. [STANDARDS TRACK] ietf-mboned-embeddedrp-07 RFC3306 PROPOSED STANDARD PROPOSED STANDARD RFC3957 Authentication, Authorization, and Accounting (AAA) Registration Keys for Mobile IPv4 C. Perkins P. Calhoun March 2005 ASCII 63576 27 Authentication, Authorization, and Accounting (AAA) servers, draft-ietf-mip4-aaa-key-06 PROPOSED STANDARD PROPOSED STANDARD RFC3958 Domain-Based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS) L. Daigle A. Newton January 2005 ASCII 54568 25 This memo defines a generalized mechanism for application service naming that allows service location without relying on rigid domain naming conventions (so-called name hacks). The proposal defines a Dynamic Delegation Discovery System (DDDS) Application to map domain name, application service name, and application protocol dynamically to target server and port. [STANDARDS TRACK] daigle-snaptr-01 PROPOSED STANDARD PROPOSED STANDARD RFC3959 The Early Session Disposition Type for the Session Initiation Protocol (SIP) G. Camarillo December 2004 ASCII 22160 11 This document defines a new disposition type (early-session) for the Content-Disposition header field in the Session Initiation Protocol (SIP). The treatment of "early-session" bodies is similar to the treatment of "session" bodies. That is, they follow the offer/answer model. Their only difference is that session descriptions whose disposition type is "early-session" are used to establish early media sessions within early dialogs, as opposed to regular sessions within regular dialogs. [STANDARDS TRACK] ietf-sipping-early-disposition-03 PROPOSED STANDARD PROPOSED STANDARD RFC3960 Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP) G. Camarillo H. Schulzrinne December 2004 ASCII 31692 13 This document describes how to manage early media in the Session Initiation Protocol (SIP) using two models: the gateway model and the application server model. It also describes the inputs one needs to consider in defining local policies for ringing tone generation. This memo provides information for the Internet community. ietf-sipping-early-media-02 INFORMATIONAL INFORMATIONAL RFC3961 Encryption and Checksum Specifications for Kerberos 5 K. Raeburn February 2005 ASCII 111865 50 This document describes a framework for defining encryption and checksum mechanisms for use with the Kerberos protocol, defining an abstraction layer between the Kerberos protocol and related protocols, and the actual mechanisms themselves. The document also defines several mechanisms. Some are taken from RFC 1510, modified in form to fit this new framework and occasionally modified in content when the old specification was incorrect. New mechanisms are presented here as well. This document does NOT indicate which mechanisms may be considered "required to implement". [STANDARDS TRACK] draft-ietf-krb-wg-crypto-07 PROPOSED STANDARD PROPOSED STANDARD RFC3962 Advanced Encryption Standard (AES) Encryption for Kerberos 5 K. Raeburn February 2005 ASCII 32844 16 kerberos cryptosystem suite The United States National Institute of Standards and Technology (NIST) has chosen a new Advanced Encryption Standard (AES), which is significantly faster and (it is believed) more secure than the old Data Encryption Standard (DES) algorithm. This document is a specification for the addition of this algorithm to the Kerberos cryptosystem suite. [STANDARDS TRACK] draft-raeburn-krb-rijndael-krb-07 PROPOSED STANDARD PROPOSED STANDARD RFC3963 Network Mobility (NEMO) Basic Support Protocol V. Devarapalli R. Wakikawa A. Petrescu P. Thubert January 2005 ASCII 75955 33 mobile ipv6 session continuity This document describes the Network Mobility (NEMO) Basic Support protocol that enables Mobile Networks to attach to different points in the Internet. The protocol is an extension of Mobile IPv6 and allows session continuity for every node in the Mobile Network as the network moves. It also allows every node in the Mobile Network to be reachable while moving around. The Mobile Router, which connects the network to the Internet, runs the NEMO Basic Support protocol with its Home Agent. The protocol is designed so that network mobility is transparent to the nodes inside the Mobile Network. [STANDARDS TRACK] draft-ietf-nemo-basic-support-03 PROPOSED STANDARD PROPOSED STANDARD RFC3964 Security Considerations for 6to4 P. Savola C. Patel December 2004 ASCII 83360 41 The IPv6 interim mechanism 6to4 (RFC3056) uses automatic IPv6-over-IPv4 tunneling to interconnect IPv6 networks. The architecture includes 6to4 routers and 6to4 relay routers, which accept and decapsulate IPv4 protocol-41 ("IPv6-in-IPv4") traffic from any node in the IPv4 internet. This characteristic enables a number of security threats, mainly Denial of Service. It also makes it easier for nodes to spoof IPv6 addresses. This document discusses these issues in more detail and suggests enhancements to alleviate the problems. This memo provides information for the Internet community. ietf-v6ops-6to4-security-04 INFORMATIONAL INFORMATIONAL RFC3965 A Simple Mode of Facsimile Using Internet Mail K. Toyoda H. Ohno J. Murai D. Wing December 2004 ASCII 28157 14 SMFAX-IM data file format e-mail This specification provides for "simple mode" carriage of facsimile data using Internet mail. Extensions to this document will follow. The current specification employs standard protocols and file formats such as TCP/IP, Internet mail protocols, Multipurpose Internet Mail Extensions (MIME), and Tagged Image File Format (TIFF) for Facsimile. It can send images not only to other Internet-aware facsimile devices but also to Internet-native systems, such as PCs with common email readers which can handle MIME mail and TIFF for Facsimile data. The specification facilitates communication among existing facsimile devices, Internet mail agents, and the gateways which connect them. <br> This document is a revision of RFC 2305. There have been no technical changes. [DRAFT STANDARD] ietf-fax-service-v2-05 RFC2305 DRAFT STANDARD DRAFT STANDARD RFC3966 The tel URI for Telephone Numbers H. Schulzrinne December 2004 ASCII 40783 17 uniform resource locator schemes This document specifies the URI (Uniform Resource Identifier) scheme "tel". The "tel" URI describes resources identified by telephone numbers. This document obsoletes RFC 2806. [STANDARDS TRACK] ietf-iptel-rfc2806bis-09 RFC2806 PROPOSED STANDARD PROPOSED STANDARD RFC3967 Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level R. Bush T. Narten December 2004 ASCII 12251 6 IETF procedures generally require that a standards track RFC may not have a normative reference to another standards track document at a lower maturity level or to a non standards track specification (other than specifications from other standards bodies). For example, a standards track document may not have a normative reference to an informational RFC. Exceptions to this rule are sometimes needed as the IETF uses informational RFCs to describe non-IETF standards or IETF-specific modes of use of such standards. This document clarifies and updates the procedure used in these circumstances. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ymbk-downref-03 BCP0097 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3968 The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP) G. Camarillo December 2004 ASCII 20615 8 This document creates an Internet Assigned Number Authority (IANA) registry for the Session Initiation Protocol (SIP) header field parameters and parameter values. It also lists the already existing parameters and parameter values to be used as the initial entries for this registry. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-sip-parameter-registry-02 RFC3427 BCP0098 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3969 The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP) G. Camarillo December 2004 ASCII 12119 6 This document creates an Internet Assigned Number Authority (IANA) registry for the Session Initiation Protocol (SIP) and SIPS Uniform Resource Identifier (URI) parameters, and their values. It also lists the already existing parameters to be used as initial values for that registry. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. ietf-sip-uri-parameter-reg-02 RFC3427 BCP0099 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3970 A Traffic Engineering (TE) MIB K. Kompella January 2005 ASCII 88833 44 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for Traffic Engineered (TE) Tunnels; for example, Multi-Protocol Label Switched Paths. [STANDARDS TRACK] ietf-tewg-mib-08 PROPOSED STANDARD PROPOSED STANDARD RFC3971 SEcure Neighbor Discovery (SEND) J. Arkko Editor J. Kempf B. Zill P. Nikander March 2005 ASCII 123372 56 Neighbor Discovery Protocol NDP IPv6 nodes use the Neighbor Discovery Protocol (NDP) to discover other nodes on the link, to determine their link-layer addresses to find routers, and to maintain reachability information about the paths to active neighbors. If not secured, NDP is vulnerable to various attacks. This document specifies security mechanisms for NDP. Unlike those in the original NDP specifications, these mechanisms do not use IPsec. [STANDARDS TRACK] draft-ietf-send-ndopt-06 PROPOSED STANDARD PROPOSED STANDARD RFC3972 Cryptographically Generated Addresses (CGA) T. Aura March 2005 ASCII 51473 22 Secure Neighbor Discovery SEND This document describes a method for binding a public signature key to an IPv6 address in the Secure Neighbor Discovery (SEND) protocol. Cryptographically Generated Addresses (CGA) are IPv6 addresses for which the interface identifier is generated by computing a cryptographic one-way hash function from a public key and auxiliary parameters. The binding between the public key and the address can be verified by re-computing the hash value and by comparing the hash with the interface identifier. Messages sent from an IPv6 address can be protected by attaching the public key and auxiliary parameters and by signing the message with the corresponding private key. The protection works without a certification authority or any security infrastructure. [STANDARDS TRACK] draft-ietf-send-cga-06 PROPOSED STANDARD PROPOSED STANDARD RFC3973 Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised) A. Adams J. Nicholas W. Siadak January 2005 ASCII 136708 61 multicast routing protocol prune messages This document specifies Protocol Independent Multicast - Dense Mode (PIM-DM). PIM-DM is a multicast routing protocol that uses the underlying unicast routing information base to flood multicast datagrams to all multicast routers. Prune messages are used to prevent future messages from propagating to routers without group membership information. This memo defines an Experimental Protocol for the Internet community. draft-ietf-pim-dm-new-v2-05 EXPERIMENTAL EXPERIMENTAL RFC3974 SMTP Operational Experience in Mixed IPv4/v6 Environments M. Nakamura J. Hagino January 2005 ASCII 22729 10 simple mail transfer protocol dual stack dualstack ipv4 ipv6 This document discusses SMTP operational experiences in IPv4/v6 dual stack environments. As IPv6-capable SMTP servers are deployed, it has become apparent that certain configurations of MX records are necessary for stable dual-stack (IPv4 and IPv6) SMTP operation. This document clarifies the existing problems in the transition period between IPv4 SMTP and IPv6 SMTP. It also defines operational requirements for stable IPv4/v6 SMTP operation. <br> This document does not define any new protocol. This memo provides information for the Internet community. draft-motonori-dualstack-smtp-requirement-01 INFORMATIONAL INFORMATIONAL RFC3975 OMA-IETF Standardization Collaboration G. Huston Editor I. Leuca Editor January 2005 ASCII 16926 9 oopen mobile alliance ietf internet engineering task force This document describes the standardization collaboration between the Open Mobile Alliance (OMA) and the Internet Engineering Task Force (IETF). This memo provides information for the Internet community. draft-iab-oma-liaison-00 INFORMATIONAL INFORMATIONAL RFC3976 Interworking SIP and Intelligent Network (IN) Applications V. K. Gurbani F. Haerens V. Rastogi January 2005 ASCII 60191 25 sip intelligent network call models call model mapping telephony services public switched telephone network pstn Public Switched Telephone Network (PSTN) services such as 800-number routing (freephone), time-and-day routing, credit-card calling, and virtual private network (mapping a private network number into a public number) are realized by the Intelligent Network (IN). This document addresses means to support existing IN services from Session Initiation Protocol (SIP) endpoints for an IP-host-to-phone call. The call request is originated on a SIP endpoint, but the services to the call are provided by the data and procedures resident in the PSTN/IN. To provide IN services in a transparent manner to SIP endpoints, this document describes the mechanism for interworking SIP and Intelligent Network Application Part (INAP). This memo provides information for the Internet community. draft-gurbani-sin-02 INFORMATIONAL INFORMATIONAL RFC3978 IETF Rights in Contributions S. Bradner Editor March 2005 ASCII 43574 18 intellectual property rights copyright ipr The IETF policies about rights in Contributions to the IETF are designed to ensure that such Contributions can be made available to the IETF and Internet communities while permitting the authors to retain as many rights as possible. This memo details the IETF policies on rights in Contributions to the IETF. It also describes the objectives that the policies are designed to meet. This memo updates RFC 2026, and, with RFC 3979, replaces Section 10 of RFC 2026. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. draft-ietf-ipr-subm-rights-fix-00 RFC3667 RFC2026 BCP0078 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3979 Intellectual Property Rights in IETF Technology S. Bradner Editor March 2005 ASCII 41366 17 ipr copyright The IETF policies about Intellectual Property Rights (IPR), such as patent rights, relative to technologies developed in the IETF are designed to ensure that IETF working groups and participants have as much information about any IPR constraints on a technical proposal as possible. The policies are also intended to benefit the Internet community and the public at large, while respecting the legitimate rights of IPR holders. This memo details the IETF policies concerning IPR related to technology worked on within the IETF. It also describes the objectives that the policies are designed to meet. This memo updates RFC 2026 and, with RFC 3978, replaces Section 10 of RFC 2026. This memo also updates paragraph 4 of Section 3.2 of RFC 2028, for all purposes, including reference [2] in RFC 2418. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. there was no internet-draft for this document; iesg requested a republication of rfc3668 with a few corrections. RFC3668 RFC2028 RFC2026 BCP0079 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC3980 T11 Network Address Authority (NAA) Naming Format for iSCSI Node Names M. Krueger M. Chadalapaka R. Elliott February 2005 ASCII 14056 8 internet small computer systems interface scsi transport protocol Internet Small Computer Systems Interface (iSCSI) is a SCSI transport protocol that maps the SCSI family of protocols onto TCP/IP. This document defines an additional iSCSI node name type format to enable use of the "Network Address Authority" (NAA) worldwide naming format defined by the InterNational Committee for Information Technology Standards (INCITS) T11 - Fibre Channel (FC) protocols and used by Serial Attached SCSI (SAS). This document updates RFC 3720. [STANDARDS TRACK] draft-ietf-ips-iscsi-name-ext-05 RFC3720 PROPOSED STANDARD PROPOSED STANDARD RFC3981 IRIS: The Internet Registry Information Service (IRIS) Core Protocol A. Newton M. Sanz January 2005 ASCII 101359 52 This document describes an application layer client-server protocol for a framework to represent the query and result operations of the information services of Internet registries. Specified in the Extensible Markup Language (XML), the protocol defines generic query and result operations and a mechanism for extending these operations for specific registry service needs. [STANDARDS TRACK] ietf-crisp-iris-core-07 PROPOSED STANDARD PROPOSED STANDARD RFC3982 IRIS: A Domain Registry (dreg) Type for the Internet Registry Information Service (IRIS) A. Newton M. Sanz January 2005 ASCII 90901 50 This document describes an Internet Registry Information Service (IRIS) registry schema for registered DNS information. The schema extends the necessary query and result operations of IRIS to provide the functional information service needs for syntaxes and results used by domain registries and registrars. [STANDARDS TRACK] ietf-crisp-iris-dreg-07 PROPOSED STANDARD PROPOSED STANDARD RFC3983 Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP) A. Newton M. Sanz January 2005 ASCII 23466 12 This document specifies how to use the Blocks Extensible Exchange Protocol (BEEP) as the application transport substrate for the Internet Registry Information Service (IRIS). [STANDARDS TRACK] ietf-crisp-iris-beep-07 PROPOSED STANDARD PROPOSED STANDARD RFC3984 RTP Payload Format for H.264 Video S. Wenger M.M. Hannuksela T. Stockhammer M. Westerlund D. Singer February 2005 ASCII 205093 83 ITU-T Recommendation H.264 ISO/IEC International Standard 14496-10 This memo describes an RTP Payload format for the ITU-T Recommendation H.264 video codec and the technically identical ISO/IEC International Standard 14496-10 video codec. The RTP payload format allows for packetization of one or more Network Abstraction Layer Units (NALUs), produced by an H.264 video encoder, in each RTP payload. The payload format has wide applicability, as it supports applications from simple low bit-rate conversational usage, to Internet video streaming with interleaved transmission, to high bit-rate video-on-demand. [STANDARDS TRACK] draft-ietf-avt-rtp-h264-11 PROPOSED STANDARD PROPOSED STANDARD RFC3985 Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture S. Bryant Editor P. Pate Editor March 2005 ASCII 95062 42 This document describes an architecture for Pseudo Wire Emulation Edge-to-Edge (PWE3). It discusses the emulation of services such as Frame Relay, ATM, Ethernet, TDM, and SONET/SDH over packet switched networks (PSNs) using IP or MPLS. It presents the architectural framework for pseudo wires (PWs), defines terminology, and specifies the various protocol elements and their functions. This memo provides information for the Internet community. draft-ietf-pwe3-arch-07 INFORMATIONAL INFORMATIONAL RFC3986 Uniform Resource Identifier (URI): Generic Syntax T. Berners-Lee R. Fielding L. Masinter January 2005 ASCII 141811 61 Internet protocol uniform resource identifier www world wide web A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS TRACK] draft-fielding-uri-rfc2396bis-07 RFC2732 RFC2396 RFC1808 RFC1738 STD0066 STANDARD STANDARD RFC3987 Internationalized Resource Identifiers (IRIs) M. Duerst M. Suignard January 2005 ASCII 111190 46 uri uniform resource identifier Universal Character Set This document defines a new protocol element, the Internationalized Resource Identifier (IRI), as a complement to the Uniform Resource Identifier (URI). An IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646). A mapping from IRIs to URIs is defined, which means that IRIs can be used instead of URIs, where appropriate, to identify resources. <br> The approach of defining a new protocol element was chosen instead of extending or changing the definition of URIs. This was done in order to allow a clear distinction and to avoid incompatibilities with existing software. Guidelines are provided for the use and deployment of IRIs in various protocols, formats, and software components that currently deal with URIs. [STANDARDS TRACK] draft-duerst-iri-11 PROPOSED STANDARD PROPOSED STANDARD RFC3988 Maximum Transmission Unit Signalling Extensions for the Label Distribution Protocol B. Black K. Kompella January 2005 ASCII 18841 9 mtu ldp lsp label switched path label switching router lsr Proper functioning of RFC 1191 path Maximum Transmission Unit (MTU) discovery requires that IP routers have knowledge of the MTU for each link to which they are connected. As currently specified, the Label Distribution Protocol (LDP) does not have the ability to signal the MTU for a Label Switched Path (LSP) to the ingress Label Switching Router (LSR). In the absence of this functionality, the MTU for each LSP must be statically configured by network operators or by equivalent off-line mechanisms. <br> This document specifies experimental extensions to LDP in support of LSP MTU discovery. This memo defines an Experimental Protocol for the Internet community. draft-ietf-mpls-ldp-mtu-extensions-03 EXPERIMENTAL EXPERIMENTAL RFC3989 Middlebox Communications (MIDCOM) Protocol Semantics M. Stiemerling J. Quittek T. Taylor February 2005 ASCII 160606 70 nat network address translator firewall This memo specifies semantics for a Middlebox Communication (MIDCOM) protocol to be used by MIDCOM agents for interacting with middleboxes such as firewalls and Network Address Translators (NATs). The semantics discussion does not include any specification of a concrete syntax or a transport protocol. However, a concrete protocol is expected to implement the specified semantics or, more likely, a superset of it. The MIDCOM protocol semantics is derived from the MIDCOM requirements, from the MIDCOM framework, and from working group decisions. This memo provides information for the Internet community. draft-ietf-midcom-semantics-08 INFORMATIONAL INFORMATIONAL RFC3990 Configuration and Provisioning for Wireless Access Points (CAPWAP) Problem Statement B. O'Hara P. Calhoun J. Kempf February 2005 ASCII 11854 5 This document describes the Configuration and Provisioning for Wireless Access Points (CAPWAP) problem statement. This memo provides information for the Internet community. draft-ietf-capwap-problem-statement-02 INFORMATIONAL INFORMATIONAL RFC3991 Media Gateway Control Protocol (MGCP) Redirect and Reset Package B. Foster F. Andreasen February 2005 ASCII 22951 11 voice IP internet VoIP The base Media Gateway Control Protocol (MGCP) specification (RFC 3435) allows endpoints to be redirected one endpoint at a time. This document provides extensions in the form of a new MGCP package that provides mechanisms for redirecting and resetting a group of endpoints. It also includes the ability to more accurately redirect endpoints by allowing a list of Call Agents to be specified in a preferred order. This memo provides information for the Internet community. draft-foster-mgcp-redirect-05 INFORMATIONAL INFORMATIONAL RFC3992 Media Gateway Control Protocol (MGCP) Lockstep State Reporting Mechanism B. Foster F. Andreasen February 2005 ASCII 9718 5 fault recovery A Media Gateway Control Protocol (MGCP) endpoint that has encountered an adverse failure condition (such as being involved in a transient call when a Call Agent failover occurred) could be left in a lockstep state whereby events are quarantined but not notified. The MGCP package described in this document provides a mechanism for reporting these situations so that the new Call Agent can take the necessary fault recovery procedures. This memo provides information for the Internet community. draft-foster-mgcp-lockstep-01 INFORMATIONAL INFORMATIONAL RFC3993 Subscriber-ID Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option R. Johnson T. Palaniappan M. Stapp March 2005 ASCII 13938 7 This memo defines a new Subscriber-ID suboption for the Dynamic Host Configuration Protocol's (DHCP) relay agent information option. The suboption allows a DHCP relay agent to associate a stable "Subscriber-ID" with DHCP client messages in a way that is independent of the client and of the underlying physical network infrastructure. [STANDARDS TRACK] draft-ietf-dhc-subscriber-id-07 PROPOSED STANDARD PROPOSED STANDARD RFC3994 Indication of Message Composition for Instant Messaging H. Schulzrinne January 2005 ASCII 27472 13 im status message content type xml extensible markup language In instant messaging (IM) systems, it is useful to know during an IM conversation whether the other party is composing a message; e.g., typing or recording an audio message. This document defines a new status message content type and XML namespace that conveys information about a message being composed. The status message can indicate the composition of a message of any type, including text, voice, or video. The status messages are delivered to the instant messaging recipient in the same manner as the instant messages themselves. [STANDARDS TRACK] draft-ietf-simple-iscomposing-03 PROPOSED STANDARD PROPOSED STANDARD RFC3995 Internet Printing Protocol (IPP): Event Notifications and Subscriptions R. Herriot T. Hastings March 2005 ASCII 223294 95 optional subscription events subscription objects asynchronous even notification This document describes an OPTIONAL extension to the Internet Printing Protocol/1.1: Model and Semantics (RFC 2911, RFC 2910). This extension allows a client to subscribe to printing related Events. Subscriptions are modeled as Subscription Objects. The Subscription Object specifies that when one of the specified Events occurs, the Printer delivers an asynchronous Event Notification to the specified Notification Recipient via the specified Push or Pull Delivery Method (i.e., protocol). <br> A client associates Subscription Objects with a particular Job by performing the Create-Job-Subscriptions operation or by submitting a Job with subscription information. A client associates Subscription Objects with the Printer by performing a Create-Printer-Subscriptions operation. Four other operations are defined for Subscription Objects: Get-Subscriptions-Attributes, Get-Subscriptions, Renew-Subscription, and Cancel-Subscription. [STANDARDS TRACK] draft-ietf-ipp-not-spec-12 RFC2911 RFC2910 PROPOSED STANDARD PROPOSED STANDARD RFC3996 Internet Printing Protocol (IPP): The 'ippget' Delivery Method for Event Notifications R. Herriot T. Hastings H. Lewis March 2005 ASCII 73638 31 pull delivery method event notifications event subscriptions This document describes an extension to the Internet Printing Protocol1.1: Model and Semantics (RFC 2911, RFC 2910). This document specifies the 'ippget' Pull Delivery Method for use with the "Internet Printing Protocol (IPP): Event Notifications and Subscriptions" specification (RFC 3995). This IPPGET Delivery Method is REQUIRED for all clients and Printers that support RFC 3995. The Notification Recipient, acting as a client, fetches (pulls) Event Notifications by using the Get-Notifications operation defined in this document. [STANDARDS TRACK] draft-ietf-ipp-notify-get-10 RFC2911 PROPOSED STANDARD PROPOSED STANDARD RFC3997 Internet Printing Protocol (IPP): Requirements for IPP Notifications T. Hastings Editor R. K. deBry H. Lewis March 2005 ASCII 38185 17 model directory services notification requirements This document is one of a set of documents that together describe all aspects of the Internet Printing Protocol (IPP). IPP is an application-level protocol that can be used for distributed printing on the Internet. There are multiple parts to IPP, but the primary architectural components are the Model, the Protocol, and an interface to Directory Services. This document provides a statement of the requirements for notifications as an optional part of an IPP Service. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC3998 Internet Printing Protocol (IPP): Job and Printer Administrative Operations C. Kugler H. Lewis T. Hastings Editor March 2005 ASCII 109658 46 system administration operations Enable-Printer and Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs and Release-Held-New-Jobs Deactivate-Printer and Activate-Printer Restart-Printer Shutdown-Printer and Startup-Printer Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Promote-Job Schedule-Job-After This document specifies the following 16 additional OPTIONAL system administration operations for use with the Internet Printing Protocol/1.1 (IPP), plus a few associated attributes, values, and status codes, and using the IPP Printer object to manage printer fan-out and fan-in. (Printer operations: Enable-Printer and Disable-Printer, Pause-Printer-After-Current-Job, Hold-New-Jobs and Release-Held-New-Jobs, Deactivate-Printer and Activate-Printer, Restart-Printer, Shutdown-Printer and Startup-Printer. Job operations: Reprocess-Job, Cancel-Current-Job, Suspend-Current-Job, Resume-Job, Promote-Job, Schedule-Job-After.) [STANDARDS TRACK] draft-ietf-ipp-ops-set2-04 PROPOSED STANDARD PROPOSED STANDARD RFC4001 Textual Conventions for Internet Network Addresses M. Daniele B. Haberman S. Routhier J. Schoenwaelder February 2005 ASCII 45836 22 MIB management information base internet network layer addressing information This MIB module defines textual conventions to represent commonly used Internet network layer addressing information. The intent is that these textual conventions will be imported and used in MIB modules that would otherwise define their own representations. [STANDARDS TRACK] draft-ietf-ops-rfc3291bis-06 RFC3291 PROPOSED STANDARD PROPOSED STANDARD RFC4002 IANA Registration for Enumservice 'web' and 'ft' R. Brandner L. Conroy R. Stastny February 2005 ASCII 18072 10 URI schemes uniform resource identifier enum This document registers the Enumservices 'web' and 'ft' by using the URI schemes 'http:', 'https:' and 'ftp:' as per the IANA registration process defined in the ENUM specification (RFC 3761). [STANDARDS TRACK] draft-ietf-enum-webft-01 PROPOSED STANDARD PROPOSED STANDARD RFC4003 GMPLS Signaling Procedure for Egress Control L. Berger February 2005 ASCII 10306 5 lsp label switch path gmpls signaling This document clarifies the procedures for the control of the label used on an output/downstream interface of the egress node of a Label Switched Path (LSP). This control is also known as "Egress Control". Support for Egress Control is implicit in Generalized Multi-Protocol Label Switching (GMPLS) Signaling. This document clarifies the specification of GMPLS Signaling and does not modify GMPLS signaling mechanisms and procedures. [STANDARDS TRACK] draft-ietf-enum-webft-01 RFC3473 PROPOSED STANDARD PROPOSED STANDARD RFC4007 IPv6 Scoped Address Architecture S. Deering B. Haberman T. Jinmei E. Nordmark B. Zill March 2005 ASCII 53555 24 architectural characteristics expected behavior textual representation This document specifies the architectural characteristics, expected behavior, textual representation, and usage of IPv6 addresses of different scopes. According to a decision in the IPv6 working group, this document intentionally avoids the syntax and usage of unicast site-local addresses. [STANDARDS TRACK] draft-ietf-ipv6-scoping-arch-02 PROPOSED STANDARD PROPOSED STANDARD RFC4008 Definitions of Managed Objects for Network Address Translators (NAT) R. Rohit P. Srisuresh R. Raghunarayan N. Pai C. Wang March 2005 ASCII 125696 64 mib management information base This memo defines a portion of the Management Information Base (MIB) for devices implementing Network Address Translator (NAT) function. This MIB module may be used for configuration as well as monitoring of a device capable of NAT function. [STANDARDS TRACK] draft-ietf-nat-natmib-09 PROPOSED STANDARD PROPOSED STANDARD RFC4009 The SEED Encryption Algorithm J. Park S. Lee J. Kim J. Lee February 2005 ASCII 32552 17 encryption algorithm seed cbc seed oid This document describes the SEED encryption algorithm, which has been adopted by most of the security systems in the Republic of Korea. Included are a description of the cipher and the key scheduling algorithm (Section 2), the S-boxes (Appendix A), and a set of test vectors (Appendix B). This memo provides information for the Internet community. draft-park-seed-01 INFORMATIONAL INFORMATIONAL RFC4010 Use of the SEED Encryption Algorithm in Cryptographic Message Syntax (CMS) J. Park S. Lee J. Kim J. Lee February 2005 ASCII 22403 13 smime secure/multipurpose internet mail extensions This document specifies the conventions for using the SEED encryption algorithm for encryption with the Cryptographic Message Syntax (CMS). <br> SEED is added to the set of optional symmetric encryption algorithms in CMS by providing two classes of unique object identifiers (OIDs). One OID class defines the content encryption algorithms and the other defines the key encryption algorithms. [STANDARDS TRACK] draft-ietf-smime-cms-seed-02 PROPOSED STANDARD PROPOSED STANDARD RFC4011 Policy Based Management MIB S. Waldbusser J. Saperia T. Hongal March 2005 ASCII 265942 121 management information base Simple Network Management Protocol snmp infrastructures scripting language script execution environment 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 MIB defines objects that enable policy-based monitoring and management of Simple Network Management Protocol (SNMP) infrastructures, a scripting language, and a script execution environment. [STANDARDS TRACK] draft-ietf-snmpconf-pm-15 PROPOSED STANDARD PROPOSED STANDARD RFC4012 Routing Policy Specification Language next generation (RPSLng) L. Blunk J. Damas F. Parent A. Robachevsky March 2005 ASCII 35217 16 This memo introduces a new set of simple extensions to the Routing Policy Specification Language (RPSL), enabling the language to document routing policies for the IPv6 and multicast address families currently used in the Internet. [STANDARDS TRACK] draft-blunk-rpslng-08 RFC2725 RFC2622 PROPOSED STANDARD PROPOSED STANDARD RFC4013 SASLprep: Stringprep Profile for User Names and Passwords K. Zeilenga February 2005 ASCII 13051 6 unicode strings saslprep stringprep sasl simple authentication and security layer This document describes how to prepare Unicode strings representing user names and passwords for comparison. The document defines the "SASLprep" profile of the "stringprep" algorithm to be used for both user names and passwords. This profile is intended to be used by Simple Authentication and Security Layer (SASL) mechanisms (such as PLAIN, CRAM-MD5, and DIGEST-MD5), as well as other protocols exchanging simple user names and/or passwords. [STANDARDS TRACK] draft-ietf-sasl-saslprep-10 PROPOSED STANDARD PROPOSED STANDARD RFC4014 Remote Authentication Dial-In User Service (RADIUS) Attributes Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Information Option R. Droms J. Schnizlein February 2005 ASCII 15416 8 The RADIUS Attributes suboption enables a network element to pass identification and authorization attributes received during RADIUS authentication to a DHCP server. When the DHCP server receives a message from a relay agent containing a RADIUS Attributes suboption, it extracts the contents of the suboption and uses that information in selecting configuration parameters for the client. [STANDARDS TRACK] draft-ietf-dhc-agentopt-radius-08 PROPOSED STANDARD PROPOSED STANDARD RFC4015 The Eifel Response Algorithm for TCP R. Ludwig A. Gurtov February 2005 ASCII 31512 13 transmision control protocol Based on an appropriate detection algorithm, the Eifel response algorithm provides a way for a TCP sender to respond to a detected spurious timeout. It adapts the retransmission timer to avoid further spurious timeouts and (depending on the detection algorithm) can avoid the often unnecessary go-back-N retransmits that would otherwise be sent. In addition, the Eifel response algorithm restores the congestion control state in such a way that packet bursts are avoided. [STANDARDS TRACK] draft-ietf-tsvwg-tcp-eifel-response-06 PROPOSED STANDARD PROPOSED STANDARD RFC4016 Protocol for Carrying Authentication and Network Access (PANA) Threat Analysis and Security Requirements M. Parthasarathy March 2005 ASCII 36104 15 authentication network access This document discusses the threats to protocols used to carry authentication for network access. The security requirements arising from these threats will be used as additional input to the Protocol for Carrying Authentication for Network Access (PANA) Working Group for designing the IP based network access authentication protocol. This memo provides information for the Internet community. draft-ietf-pana-threats-eval-07 INFORMATIONAL INFORMATIONAL RFC4017 Extensible Authentication Protocol (EAP) Method Requirements for Wireless LANs D. Stanley J. Walker B. Aboba March 2005 ASCII 22183 11 IEEE 802.11 wireless lan The IEEE 802.11i MAC Security Enhancements Amendment makes use of IEEE 802.1X, which in turn relies on the Extensible Authentication Protocol (EAP). This document defines requirements for EAP methods used in IEEE 802.11 wireless LAN deployments. The material in this document has been approved by IEEE 802.11 and is being presented as an IETF RFC for informational purposes. This memo provides information for the Internet community. draft-walker-ieee802-req-04 INFORMATIONAL INFORMATIONAL RFC4018 Finding Internet Small Computer Systems Interface (iSCSI) Targets and Name Servers by Using Service Location Protocol version 2 (SLPv2) M. Bakke J. Hufferd K. Voruganti M. Krueger T. Sperry April 2005 ASCII 48498 23 scsi slp The iSCSI protocol provides a way for hosts to access SCSI devices over an IP network. This document defines the use of the Service Location Protocol (SLP) by iSCSI hosts, devices, and management services, along with the SLP service type templates that describe the services they provide. [PROPOSED STANDARD] draft-ietf-ips-iscsi-slp-09 PROPOSED STANDARD PROPOSED STANDARD RFC4019 RObust Header Compression (ROHC): Profiles for User Datagram Protocol (UDP) Lite G. Pelletier April 2005 ASCII 46896 23 rtp udp-lite ip real-time transport protocol user datagram protocol lite internet protocol This document defines Robust Header Compression (ROHC) profiles for compression of Real-Time Transport Protocol, User Datagram Protocol-Lite, and Internet Protocol (RTP/UDP-Lite/IP) packets and UDP-Lite/IP. These profiles are defined based on their differences with the profiles for UDP as specified in RFC 3095. [STANDARDS TRACK] draft-ietf-rohc-udp-lite-04 PROPOSED STANDARD PROPOSED STANDARD RFC4020 Early IANA Allocation of Standards Track Code Points K. Kompella A. Zinin February 2005 ASCII 13706 7 This memo discusses earlier allocation of code points by IANA as a remedy to the problem created by the "Standards Action" IANA policy for protocols for which, by the IETF process, implementation and deployment experience is desired or required prior to publication. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. draft-kompella-zinin-early-allocation-02 BCP0100 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC4021 Registration of Mail and MIME Header Fields G. Klyne J. Palme March 2005 ASCII 75452 54 This document defines the initial IANA registration for permanent mail and MIME message header fields, per RFC 3864. [STANDARDS TRACK] draft-klyne-hdrreg-mail-05 PROPOSED STANDARD PROPOSED STANDARD RFC4022 Management Information Base for the Transmission Control Protocol (TCP) R. Raghunarayan Editor March 2005 ASCII 47360 24 MIB-TCP TCP Simple Network Management Protocol MIB 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 implementations of the Transmission Control Protocol (TCP) in an IP version independent manner. This memo obsoletes RFCs 2452 and 2012. [STANDARDS TRACK] draft-ietf-ipv6-rfc2012-update-06 RFC2452 RFC2012 PROPOSED STANDARD PROPOSED STANDARD RFC4023 Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE) T. Worster Y. Rekhter E. Rosen Editor March 2005 ASCII 31696 14 Various applications of MPLS make use of label stacks with multiple entries. In some cases, it is possible to replace the top label of the stack with an IP-based encapsulation, thereby enabling the application to run over networks that do not have MPLS enabled in their core routers. This document specifies two IP-based encapsulations: MPLS-in-IP and MPLS-in-GRE (Generic Routing Encapsulation). Each of these is applicable in some circumstances. [STANDARDS TRACK] draft-ietf-mpls-in-ip-or-gre-08 PROPOSED STANDARD PROPOSED STANDARD RFC4025 A Method for Storing IPsec Keying Material in DNS M. Richardson March 2005 ASCII 25408 12 This document describes a new resource record for the Domain Name System (DNS). This record may be used to store public keys for use in IP security (IPsec) systems. The record also includes provisions for indicating what system should be contacted when an IPsec tunnel is established with the entity in question. <br> This record replaces the functionality of the sub-type #4 of the KEY Resource Record, which has been obsoleted by RFC 3445. [STANDARDS TRACK] draft-ietf-ipseckey-rr-11 PROPOSED STANDARD PROPOSED STANDARD RFC4026 Provider Provisioned Virtual Private Network (VPN) Terminology L. Andersson T. Madsen March 2005 ASCII 42124 20 l3vpn l2vpn The widespread interest in provider-provisioned Virtual Private Network (VPN) solutions lead to memos proposing different and overlapping solutions. The IETF working groups (first Provider Provisioned VPNs and later Layer 2 VPNs and Layer 3 VPNs) have discussed these proposals and documented specifications. This has lead to the development of a partially new set of concepts used to describe the set of VPN services. <br> To a certain extent, more than one term covers the same concept, and sometimes the same term covers more than one concept. This document seeks to make the terminology in the area clearer and more intuitive. This memo provides information for the Internet community. draft-ietf-l3vpn-ppvpn-terminology-04 INFORMATIONAL INFORMATIONAL RFC4027 Domain Name System Media Types S. Josefsson April 2005 ASCII 11676 6 media type application/dns text/dns This document registers the media types application/dns and text/dns in accordance with RFC 2048. The application/dns media type is used to identify data on the detached Domain Name System (DNS) format described in RFC 2540. The text/dns media type is used to identify master files as described in RFC 1035. This memo provides information for the Internet community. draft-josefsson-mime-dns-02 INFORMATIONAL INFORMATIONAL RFC4028 Session Timers in the Session Initiation Protocol (SIP) S. Donovan J. Rosenberg April 2005 ASCII 65363 27 re-invite request update request session-expires min-se This document defines an extension to the Session Initiation Protocol (SIP). This extension allows for a periodic refresh of SIP sessions through a \%re-INVITE or UPDATE request. The refresh allows both user agents and proxies to determine whether the SIP session is still active. The extension defines two new header fields: \%Session-Expires, which conveys the lifetime of the session, and \%Min-SE, which conveys the minimum allowed value for the session timer. [STANDARDS TRACK] draft-ietf-sip-session-timer-15 PROPOSED STANDARD PROPOSED STANDARD RFC4029 Scenarios and Analysis for Introducing IPv6 into ISP Networks M. Lind V. Ksinant S. Park A. Baudot P. Savola March 2005 ASCII 64388 28 internet service provider internet protocol This document describes different scenarios for the introduction of IPv6 into an ISP's existing IPv4 network without disrupting the IPv4 service. The scenarios for introducing IPv6 are analyzed, and the relevance of already defined transition mechanisms are evaluated. Known challenges are also identified. This memo provides information for the Internet community. draft-ietf-v6ops-isp-scenarios-analysis-03 INFORMATIONAL INFORMATIONAL RFC4030 The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option M. Stapp T. Lemon March 2005 ASCII 34332 15 The Dynamic Host Configuration Protocol (DHCP) Relay Agent Information Option (RFC 3046) conveys information between a DHCP Relay Agent and a DHCP server. This specification defines an authentication suboption for that option, containing a keyed hash in its payload. The suboption supports data integrity and replay protection for relayed DHCP messages. [STANDARDS TRACK] draft-ietf-dhc-auth-suboption-05 PROPOSED STANDARD PROPOSED STANDARD RFC4031 Service Requirements for Layer 3 Provider Provisioned Virtual Private Networks (PPVPNs) M. Carugi Editor D. McDysan Editor April 2005 ASCII 118568 50 l3vpn service provider vpn This document provides requirements for Layer 3 Virtual Private Networks (L3VPNs). It identifies requirements applicable to a number of individual approaches that a Service Provider may use to provision a Virtual Private Network (VPN) service. This document expresses a service provider perspective, based upon past experience with IP-based service offerings and the ever-evolving needs of the customers of such services. Toward this end, it first defines terminology and states general requirements. Detailed requirements are expressed from a customer perspective as well as that of a service provider. This memo provides information for the Internet community. ietf-l3vpn-requirements-02 INFORMATIONAL INFORMATIONAL RFC4032 Update to the Session Initiation Protocol (SIP) Preconditions Framework G. Camarillo P. Kyzivat March 2005 ASCII 20492 10 qos quality of service precondition This document updates RFC 3312, which defines the framework for preconditions in SIP. We provide guidelines for authors of new precondition types and describe how to use SIP preconditions in situations that involve session mobility. [STANDARDS TRACK] draft-ietf-sip-rfc3312-update-03 RFC3312 PROPOSED STANDARD PROPOSED STANDARD RFC4033 DNS Security Introduction and Requirements R. Arends R. Austein M. Larson D. Massey S. Rose March 2005 ASCII 52445 21 domain name system authentication origin integrity dnssec domain name system security extensions The Domain Name System Security Extensions (DNSSEC) add data origin authentication and data integrity to the Domain Name System. This document introduces these extensions and describes their capabilities and limitations. This document also discusses the services that the DNS security extensions do and do not provide. Last, this document describes the interrelationships between the documents that collectively describe DNSSEC. [STANDARDS TRACK] draft-ietf-dnsext-dnssec-intro-13 RFC2535 RFC3008 RFC3090 RFC3445 RFC3655 RFC3658 RFC3755 RFC3757 RFC3845 RFC1034 RFC1035 RFC2136 RFC2181 RFC2308 RFC3225 RFC3007 RFC3597 RFC3226 PROPOSED STANDARD PROPOSED STANDARD RFC4034 Resource Records for the DNS Security Extensions R. Arends R. Austein M. Larson D. Massey S. Rose March 2005 ASCII 63879 29 domain name system authentication origin integrity dnssec domain name system security extensions This document is part of a family of documents that describe the DNS Security Extensions (DNSSEC). The DNS Security Extensions are a collection of resource records and protocol modifications that provide source authentication for the DNS. This document defines the public key (DNSKEY), delegation signer (DS), resource record digital signature (RRSIG), and authenticated denial of existence (NSEC) resource records. The purpose and format of each resource record is described in detail, and an example of each resource record is given. <br> This document obsoletes RFC 2535 and incorporates changes from all updates to RFC 2535. [STANDARDS TRACK] draft-ietf-dnsext-dnssec-records-11 RFC2535 RFC3008 RFC3090 RFC3445 RFC3655 RFC3658 RFC3755 RFC3757 RFC3845 RFC1034 RFC1035 RFC2136 RFC2181 RFC2308 RFC3225 RFC3007 RFC3597 RFC3226 PROPOSED STANDARD PROPOSED STANDARD RFC4035 Protocol Modifications for the DNS Security Extensions R. Arends R. Austein M. Larson D. Massey S. Rose March 2005 ASCII 130589 53 domain name system authentication origin integrity dnssec domain name system security extensions This document is part of a family of documents that describe the DNS Security Extensions (DNSSEC). The DNS Security Extensions are a collection of new resource records and protocol modifications that add data origin authentication and data integrity to the DNS. This document describes the DNSSEC protocol modifications. This document defines the concept of a signed zone, along with the requirements for serving and resolving by using DNSSEC. These techniques allow a security-aware resolver to authenticate both DNS resource records and authoritative DNS error indications. <br> This document obsoletes RFC 2535 and incorporates changes from all updates to RFC 2535. [STANDARDS TRACK] draft-ietf-dnsext-dnssec-protocol-09 RFC2535 RFC3008 RFC3090 RFC3445 RFC3655 RFC3658 RFC3755 RFC3757 RFC3845 RFC1034 RFC1035 RFC2136 RFC2181 RFC2308 RFC3225 RFC3007 RFC3597 RFC3226 PROPOSED STANDARD PROPOSED STANDARD RFC4036 Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modem Termination Systems for Subscriber Management W. Sawyer April 2005 ASCII 57946 27 mib snmp simple network management protocol This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a set of managed objects for Simple Network Management Protocol (SNMP)-based management of Data-over-Cable Service Interface Specification (DOCSIS)-compliant Cable Modem Termination Systems. These managed objects facilitate protection of the cable network from misuse by subscribers. The Differentiated Services MIB (RFC 3289) provides the filtering functions needed here, making use of classification items defined in this specification. [STANDARDS TRACK] draft-ietf-ipcdn-subscriber-mib-16 PROPOSED STANDARD PROPOSED STANDARD RFC4037 Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core A. Rousskov March 2005 ASCII 131487 56 callout server This document specifies the core of the Open Pluggable Edge Services (OPES) Callout Protocol (OCP). OCP marshals application messages from other communication protocols: An OPES intermediary sends original application messages to a callout server; the callout server sends adapted application messages back to the processor. OCP is designed with typical adaptation tasks in mind (e.g., virus and spam management, language and format translation, message anonymization, or advertisement manipulation). As defined in this document, the OCP Core consists of application-agnostic mechanisms essential for efficient support of typical adaptations. [STANDARDS TRACK] draft-ietf-opes-ocp-core-05 PROPOSED STANDARD PROPOSED STANDARD RFC4038 Application Aspects of IPv6 Transition M-K. Shin Editor Y-G. Hong J. Hagino P. Savola E. M. Castro March 2005 ASCII 69727 33 As IPv6 networks are deployed and the network transition is discussed, one should also consider how to enable IPv6 support in applications running on IPv6 hosts, and the best strategy to develop IP protocol support in applications. This document specifies scenarios and aspects of application transition. It also proposes guidelines on how to develop IP version-independent applications during the transition period. This memo provides information for the Internet community. draft-ietf-v6ops-application-transition-03 INFORMATIONAL INFORMATIONAL RFC4039 Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4) S. Park P. Kim B. Volz March 2005 ASCII 22297 10 This document defines a new Dynamic Host Configuration Protocol version 4 (DHCPv4) option, modeled on the DHCPv6 Rapid Commit option, for obtaining IP address and configuration information using a 2-message exchange rather than the usual 4-message exchange, expediting client configuration. [STANDARDS TRACK] draft-ietf-dhc-rapid-commit-opt-05 PROPOSED STANDARD PROPOSED STANDARD RFC4040 RTP Payload Format for a 64 kbit/s Transparent Call R. Kreuter April 2005 ASCII 15363 8 realtime transport protocol This document describes how to carry 64 kbit/s channel data transparently in RTP packets, using a pseudo-codec called "Clearmode". It also serves as registration for a related MIME type called "audio/clearmode". <br> "Clearmode" is a basic feature of VoIP Media Gateways. [STANDARDS TRACK] draft-ietf-avt-rtp-clearmode-05 PROPOSED STANDARD PROPOSED STANDARD RFC4041 Requirements for Morality Sections in Routing Area Drafts A. Farrel April 01 2005 ASCII 15249 8 moral values moral code It has often been the case that morality has not been given proper consideration in the design and specification of protocols produced within the Routing Area. This has led to a decline in the moral values within the Internet and attempts to retrofit a suitable moral code to implemented and deployed protocols has been shown to be sub-optimal. <br> This document specifies a requirement for all new Routing Area Internet-Drafts to include a "Morality Considerations" section, and gives guidance on what that section should contain. This memo provides information for the Internet community. draft-farrel-rtg-morality-requirements-01 INFORMATIONAL INFORMATIONAL RFC4042 UTF-9 and UTF-18 Efficient Transformation Formats of Unicode M. Crispin April 01 2005 ASCII 19123 9 universal character set ucs codeopints unicode utf-7 utf-8 utf-16 ISO-10646 defines a large character set called the Universal Character Set (UCS), which encompasses most of the world's writing systems. The same set of codepoints is defined by Unicode, which further defines additional character properties and other implementation details. By policy of the relevant standardization committees, changes to Unicode and amendments and additions to ISO/IEC 10646 track each other, so that the character repertoires and code point assignments remain in synchronization. <br> The current representation formats for Unicode (UTF-7, UTF-8, UTF-16) are not storage and computation efficient on platforms that utilize the 9 bit nonet as a natural storage unit instead of the 8 bit octet. This document describes a transformation format of Unicode that takes advantage of the nonet so that the format will be storage and computation efficient. This memo provides information for the Internet community. INFORMATIONAL INFORMATIONAL RFC4044 Fibre Channel Management MIB K. McCloghrie May 2005 ASCII 127148 69 management information base fc-mgmt-mib This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for information related to the Fibre Channel. [STANDARDS TRACK] draft-ietf-ips-fcmgmt-mib-06 RFC2837 PROPOSED STANDARD PROPOSED STANDARD RFC4045 Extensions to Support Efficient Carrying of Multicast Traffic in Layer-2 Tunneling Protocol (L2TP) G. Bourdon April 2005 ASCII 59140 28 ppp point-to-point protocol The Layer Two Tunneling Protocol (L2TP) provides a method for tunneling PPP packets. This document describes an extension to L2TP, to make efficient use of L2TP tunnels within the context of deploying multicast services whose data will have to be conveyed by these tunnels. This memo defines an Experimental Protocol for the Internet community. draft-ietf-l2tpext-mcast-05 EXPERIMENTAL EXPERIMENTAL RFC4046 Multicast Security (MSEC) Group Key Management Architecture M. Baugher R. Canetti L. Dondeti F. Lindholm April 2005 ASCII 97885 38 group security association gsa This document defines the common architecture for Multicast Security (MSEC) key management protocols to support a variety of application, transport, and network layer security protocols. It also defines the group security association (GSA), and describes the key management protocols that help establish a GSA. The framework and guidelines described in this document permit a modular and flexible design of group key management protocols for a variety of different settings that are specialized to applications needs. MSEC key management protocols may be used to facilitate secure one-to-many, many-to-many, or one-to-one communication. This memo provides information for the Internet community. draft-ietf-msec-gkmarch-08 INFORMATIONAL INFORMATIONAL RFC4047 MIME Sub-type Registrations for Flexible Image Transport System (FITS) S. Allen D. Wells April 2005 ASCII 53737 23 multipurpose internet mail extensions astronomical observations This document describes the registration of the Multipurpose Internet Mail Extensions (MIME) sub-types to be used by the international astronomical community for the interchange of Flexible Image Transport System (FITS) files. The encoding is defined by the published FITS standard documents. The FITS format has been in use since 1979, and almost all data from astronomical observations are interchanged by using FITS. This memo provides information for the Internet community. draft-allen-fitsmime-00 INFORMATIONAL INFORMATIONAL RFC4048 RFC 1888 Is Obsolete B. Carpenter April 2005 ASCII 7394 4 Internet Protocol Open Systems Interconnection This document recommends that RFC 1888, on Open Systems Interconnection (OSI) Network Service Access Points (NSAPs) and IPv6, be reclassified as Historic, as most of it has no further value, apart from one section, which is faulty. This memo provides information for the Internet community. draft-carpenter-obsolete-1888-01 INFORMATIONAL INFORMATIONAL RFC4049 BinaryTime: An Alternate Format for Representing Date and Time in ASN.1 R. Housley April 2005 ASCII 12302 7 signing-time attribute cryptographic message syntax cms SignedData AuthenticatedData This document specifies a new ASN.1 type for representing time: BinaryTime. This document also specifies an alternate to the signing-time attribute for use with the Cryptographic Message Syntax (CMS) SignedData and AuthenticatedData content types; the binary-signing-time attribute uses BinaryTime. CMS and the signing-time attribute are defined in RFC 3852. This memo defines an Experimental Protocol for the Internet community. draft-housley-binarytime-02 EXPERIMENTAL EXPERIMENTAL RFC4050 Using the Elliptic Curve Signature Algorithm (ECDSA) for XML Digital Signatures S. Blake-Wilson G. Karlinger T. Kobayashi Y. Wang April 2005 ASCII 35327 19 elliptic curve digital signature algorithm ecdsa elliptic curve cryptography ecc xml digital signatures xml dsig xml This document specifies how to use Elliptic Curve Digital Signature Algorithm (ECDSA) with XML Signatures. The mechanism specified provides integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or included by reference. This memo provides information for the Internet community. draft-blake-wilson-xmldsig-ecdsa-09 INFORMATIONAL INFORMATIONAL RFC4051 Additional XML Security Uniform Resource Identifiers (URIs) D. Eastlake 3rd April 2005 ASCII 33368 17 digital signatures encryption canonicalization A number of Uniform Resource Identifiers (URIs) intended for use with XML Digital Signatures, Encryption, and Canonicalization are defined. These URIs identify algorithms and types of keying information. [STANDARDS TRACK] draft-eastlake-xmldsig-uri-09 PROPOSED STANDARD PROPOSED STANDARD RFC4052 IAB Processes for Management of IETF Liaison Relationships L. Daigle Editor Internet Architecture Board April 2005 ASCII 18360 9 internet architecture board sdo standards development organization This document discusses the procedures used by the IAB to establish and maintain liaison relationships between the IETF and other Standards Development Organizations (SDOs), consortia and industry fora. This document also discusses the appointment and responsibilities of IETF liaison managers and representatives, and the expectations of the IAB for organizations with whom liaison relationships are established. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. draft-iab-liaison-mgt-03 BCP0102 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC4053 Procedures for Handling Liaison Statements to and from the IETF S. Trowbridge S. Bradner F. Baker April 2005 ASCII 38816 19 sdo standards develoopment organization This document describes the procedure for proper handling of incoming liaison statements from other standards development organizations (SDOs), consortia, and industry fora, and for generating liaison statements to be transmitted from IETF to other SDOs, consortia and industry fora. This procedure allows IETF to effectively collaborate with other organizations in the international standards community. <br> The IETF expects that liaison statements might come from a variety of organizations, and it may choose to respond to many of those. The IETF is only obligated to respond if there is an agreed liaison relationship, however. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. draft-baker-liaison-statements-04 BCP0103 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC4054 Impairments and Other Constraints on Optical Layer Routing J. Strand Editor A. Chiu Editor May 2005 ASCII 73327 29 diversity routing path selection impariment ase pmd optical control plane gmpls Optical networking poses a number challenges for Generalized Multi-Protocol Label Switching (GMPLS). Fundamentally, optical technology is an analog rather than digital technology whereby the optical layer is lowest in the transport hierarchy and hence has an intimate relationship with the physical geography of the network. This contribution surveys some of the aspects of optical networks that impact routing and identifies possible GMPLS responses for each: (1) Constraints arising from the design of new software controllable network elements, (2) Constraints in a single all-optical domain without wavelength conversion, (3) Complications arising in more complex networks incorporating both all-optical and opaque architectures, and (4) Impacts of diversity constraints. This memo provides information for the Internet community. draft-ietf-ipo-impairments-04 INFORMATIONAL INFORMATIONAL RFC4059 Internet X.509 Public Key Infrastructure Warranty Certificate Extension D. Linsenbardt S. Pontius A. Sturgeon May 2005 ASCII 17904 9 certificate authority ca insurance policy This document describes a certificate extension to explicitly state the warranty offered by a Certificate Authority (CA) for the certificate containing the extension. This memo provides information for the Internet community. draft-ietf-pkix-warranty-extn-04 INFORMATIONAL INFORMATIONAL RFC4060 RTP Payload Formats for European Telecommunications Standards Institute (ETSI) European Standard ES 202 050, ES 202 211, and ES 202 212 Distributed Speech Recognition Encoding Q. Xie D. Pearce May 2005 ASCII 39654 19 real-time transport protocol dsr distributed speeech recognition xfe extended front-end xafe extended advanced front-end This document specifies RTP payload formats for encapsulating European Telecommunications Standards Institute (ETSI) European Standard ES 202 050 DSR Advanced Front-end (AFE), ES 202 211 DSR Extended Front-end (XFE), and ES 202 212 DSR Extended Advanced Front-end (XAFE) signal processing feature streams for distributed speech recognition (DSR) systems. [STANDARDS TRACK] draft-ietf-avt-rtp-dsr-codecs-03 PROPOSED STANDARD PROPOSED STANDARD RFC4061 Benchmarking Basic OSPF Single Router Control Plane Convergence V. Manral R. White A. Shaikh April 2005 ASCII 32706 16 spf time adjacency formation time This document provides suggestions for measuring OSPF single router control plane convergence. Its initial emphasis is on the control plane of a single OSPF router. We do not address forwarding plane performance. <br> NOTE: In this document, the word "convergence" relates to single router control plane convergence only. This memo provides information for the Internet community. draft-ietf-bmwg-ospfconv-intraarea-10 INFORMATIONAL INFORMATIONAL RFC4062 OSPF Benchmarking Terminology and Concepts V. Manral R. White A. Shaikh April 2005 ASCII 15784 9 spf time adjacency formation time This document explains the terminology and concepts used in OSPF benchmarking. Although some of these terms may be defined elsewhere (and we will refer the reader to those definitions in some cases) we include discussions concerning these terms, as they relate specifically to the tasks involved in benchmarking the OSPF protocol. This memo provides information for the Internet community. draft-ietf-bmwg-ospfconv-term-10 INFORMATIONAL INFORMATIONAL RFC4063 Considerations When Using Basic OSPF Convergence Benchmarks V. Manral R. White A. Shaikh April 2005 ASCII 23401 11 spf time adjacency formation time This document discusses the applicability of various tests for measuring single router control plane convergence, specifically in regard to the Open Shortest First (OSPF) protocol. There are two general sections in this document, the first discusses advantages and limitations of specific OSPF convergence tests, and the second discusses more general pitfalls to be considered when routing protocol convergence is tested. This memo provides information for the Internet community. draft-ietf-bmwg-ospfconv-applicability-07 INFORMATIONAL INFORMATIONAL RFC4069 Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Single Carrier Modulation (SCM) Line Coding M. Dodge B. Ray May 2005 ASCII 35712 19 mib management information base VDSL-LINE-MIB VDSL-LINE-EXT-SCM-MIB This document defines a portion of the Management Information Base (MIB) module for use with network management protocols in the Internet community. In particular, it describes objects used for managing the Line Code Specific parameters of Very High Speed Digital Subscriber Line (VDSL) interfaces using Single Carrier Modulation (SCM) Line Coding. It is an optional extension to the VDSL-LINE-MIB, RFC 3728, which handles line code independent objects. [STANDARDS TRACK] draft-ietf-adslmib-vdsl-ext-scm-08 PROPOSED STANDARD PROPOSED STANDARD RFC4070 Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Multiple Carrier Modulation (MCM) Line Coding M. Dodge B. Ray May 2005 ASCII 48561 24 management information base mib VDSL-LINE-MIB VDSL-LINE-EXT-MCM-MIB This document defines a portion of the Management Information Base (MIB) module for use with network management protocols in the Internet community. In particular, it describes objects used for managing the Line Code Specific parameters of Very High Speed Digital Subscriber Line (VDSL) interfaces using Multiple Carrier Modulation (MCM) Line Coding. It is an optional extension to the VDSL-LINE-MIB, RFC 3728, which handles line code independent objects. [PROPOSED STANDARD] draft-ietf-adslmib-vdsl-ext-mcm-06 PROPOSED STANDARD PROPOSED STANDARD RFC4071 Structure of the IETF Administrative Support Activity (IASA) R. Austein Editor B. Wijnen Editor April 2005 ASCII 48614 20 isoc ietf administrative oversight committee IAOC ietf administrative director iad This document describes the structure of the IETF Administrative Support Activity (IASA) as an activity housed within the Internet Society (ISOC). It defines the roles and responsibilities of the IETF Administrative Oversight Committee (IAOC), the IETF Administrative Director (IAD), and ISOC in the fiscal and administrative support of the IETF standards process. It also defines the membership and selection rules for the IAOC. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. draft-ietf-iasa-bcp-07 BCP0101 BEST CURRENT PRACTICE BEST CURRENT PRACTICE RFC4073 Protecting Multiple Contents with the Cryptographic Message Syntax (CMS) R. Housley May 2005 ASCII 17103 9 content collection This document describes a convention for using the Cryptographic Message Syntax (CMS) to protect a content collection. If desired, attributes can be associated with the content. [STANDARDS TRACK] draft-housley-contentcollection-05 PROPOSED STANDARD PROPOSED STANDARD RFC4084 Terminology for Describing Internet Connectivity J. Klensin May 2005 ASCII 24522 11 As the Internet has evolved, many types of arrangements have been advertised and sold as "Internet connectivity". Because these may differ significantly in the capabilities they offer, the range of options, and the lack of any standard terminology, the effort to distinguish between these services has caused considerable consumer confusion. This document provides a list of terms and definitions that may be helpful to providers, consumers, and, potentially, regulators in clarifying the type and character of services being offered. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. draft-klensin-ip-service-terms-04 BCP0104 BEST CURRENT PRACTICE BEST CURRENT PRACTICE STD0001 Internet Official Protocol Standards RFC3700 STD0002 [Reserved for Assigned Numbers. See RFC 1700 and RFC 3232.] RFC1700 STD0003 Requirements for Internet Hosts RFC1122 RFC1123 STD0004 [Reserved for Router Requirements. See RFC 1812.] STD0005 Internet Protocol RFC0791 RFC0792 RFC0919 RFC0922 RFC0950 RFC1112 STD0006 User Datagram Protocol RFC0768 STD0007 Transmission Control Protocol RFC0793 STD0008 Telnet Protocol RFC0854 RFC0855 STD0009 File Transfer Protocol RFC0959 STD0010 Simple Mail Transfer Protocol RFC0821 RFC1869 RFC974 STD0011 STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES RFC0822 STD0012 [Reserved for Network Time Protocol (NTP). See RFC 1305.] STD0013 Domain Name System RFC1034 RFC1035 STD0014 [Was Mail Routing and the Domain System. Now Historic.] STD0015 [Was Simple Network Management Protocol. Now Historic.] STD0016 Structure of Management Information RFC1155 RFC1212 STD0017 Management Information Base RFC1213 STD0018 [Was Exterior Gateway Protocol (RFC 904). Now Historic.] STD0019 NetBIOS Service Protocols RFC1001 RFC1002 STD0020 Echo Protocol RFC0862 STD0021 Discard Protocol RFC0863 STD0022 Character Generator Protocol RFC0864 STD0023 Quote of the Day Protocol RFC0865 STD0024 Active Users Protocol RFC0866 STD0025 Daytime Protocol RFC0867 STD0026 Time Server Protocol RFC0868 STD0027 Binary Transmission Telnet Option RFC0856 STD0028 Echo Telnet Option RFC0857 STD0029 Suppress Go Ahead Telnet Option RFC0858 STD0030 Status Telnet Option RFC0859 STD0031 Timing Mark Telnet Option RFC0860 STD0032 Extended Options List Telnet Option RFC0861 STD0033 Trivial File Transfer Protocol RFC1350 STD0034 [Was Routing Information Protocol (RIP). Replaced by STD 56.] STD0035 ISO Transport Service on top of the TCP (Version: 3) RFC1006 STD0036 Transmission of IP and ARP over FDDI Networks RFC1390 STD0037 An Ethernet Address Resolution Protocol RFC0826 STD0038 A Reverse Address Resolution Protocol RFC0903 STD0039 [Was BBN Report 1822 (IMP/Host Interface). Now Historic.] STD0040 Host Access Protocol specification RFC0907 STD0041 Standard for the transmission of IP datagrams over Ethernet networks RFC0894 STD0042 Standard for the transmission of IP datagrams over experimental Ethernetnetworks RFC0895 STD0043 Standard for the transmission of IP datagrams over IEEE 802 networks RFC1042 STD0044 DCN Local-Network Protocols RFC0891 STD0045 Internet Protocol on Network System's HYPERchannel: Protocol Specification RFC1044 STD0046 Transmitting IP traffic over ARCNET networks RFC1201 STD0047 Nonstandard for transmission of IP datagrams over serial lines: SLIP RFC1055 STD0048 Standard for the transmission of IP datagrams over NetBIOS networks RFC1088 STD0049 Standard for the transmission of 802.2 packets over IPX networks RFC1132 STD0050 [Reserved for Definitions of Managed Objects for the Ethernet-like Interface Types. See RFC 3638.] STD0051 The Point-to-Point Protocol (PPP) RFC1661 RFC1662 STD0052 The Transmission of IP Datagrams over the SMDS Service RFC1209 STD0053 Post Office Protocol - Version 3 RFC1939 STD0054 OSPF Version 2 RFC2328 STD0055 Multiprotocol Interconnect over Frame Relay RFC2427 STD0056 RIP Version 2 RFC2453 STD0057 RIP Version 2 Protocol Applicability Statement RFC1722 STD0058 Structure of Management Information Version 2 (SMIv2) RFC2578 RFC2579 RFC2580 STD0059 Remote Network Monitoring Management Information Base RFC2819 STD0060 SMTP Service Extension for Command Pipelining RFC2920 STD0061 A One-Time Password System RFC2289 STD0062 Simple Network Management Protocol Version 3 (SNMPv3) RFC3411 RFC3412 RFC3413 RFC3414 RFC3415 RFC3416 RFC3417 RFC3418 STD0063 UTF-8, a transformation format of ISO 10646 RFC3629 STD0064 RTP: A Transport Protocol for Real-Time Applications RFC3550 STD0065 RTP Profile for Audio and Video Conferences with Minimal Control RFC3551 STD0066 Uniform Resource Identifier (URI): Generic Syntax RFC3986